No busy tone on VOIPo

**Russell** · 05-11-2009 07:04 PM

Originally Posted by VOIPoBrandon

I took a look at the call from that time, it does look like PSTN responding with 183 Session Progress, i.e. Ringing/Ringback followed by a 200 OK (call answered). What was the report, just complete silence on the call or, how would you best describe it, thanks!

I asked my child - total silence is the report. I know I experienced one other today. And, in both cases working numbers, so I suspect they were either busy or there was some other issue connecting to them. Does the busy signal solution need to be propagated to all servers?

**VOIPoBrandon** · 05-12-2009 12:38 PM

Originally Posted by Russell

I asked my child - total silence is the report. I know I experienced one other today. And, in both cases working numbers, so I suspect they were either busy or there was some other issue connecting to them. Does the busy signal solution need to be propagated to all servers?

Russell,

The busy changes are live and well -- it may be a classic case of one way audio / no audio at all. I do see the call connecting in that call example, perhaps if you guys could get a hold of the callee and ask them if there phone is ringing at their endpoint during that call? If it would be possible to setup a date / time for me to grab a network trace -- please shoot me a PM so we can arrange to do so and look into this further.

Also as for the normal / circuits busy / number disconnected, I will post back in regards to this shortly, thanks!

**Russell** · 05-12-2009 09:05 PM

Originally Posted by VOIPoBrandon

Russell,

The busy changes are live and well -- it may be a classic case of one way audio / no audio at all. I do see the call connecting in that call example, perhaps if you guys could get a hold of the callee and ask them if there phone is ringing at their endpoint during that call? If it would be possible to setup a date / time for me to grab a network trace -- please shoot me a PM so we can arrange to do so and look into this further.

Also as for the normal / circuits busy / number disconnected, I will post back in regards to this shortly, thanks!

Brandon, the callee was a child's baby-sitting client, so it's not possible for me to quiz them as to what happened.

If you have a plain old POTS number at VOIPo (which doesn't default to voicemail or have call-waiting) for me to call, I can try calling that. I presume I can first call using line 1 and then call using line 2 and get a busy signal. Let me know if this is an option for me to try.

I had a tree down over the weekend and was at home yesterday making calls to tree contractors. And, they would call me back ... at least a couple of calls when I picked up the phone I would hear nothing. I'd hang up and a few minutes later the phone would ring again and this time all would be well. Does this follow any classic case (no audio / one way audio)? Thought I'd mention this in case this is related to the no-busy signal being discussed.

**VOIPoTim** · 05-12-2009 09:14 PM

Originally Posted by Russell

I had a tree down over the weekend and was at home yesterday making calls to tree contractors. And, they would call me back ... at least a couple of calls when I picked up the phone I would hear nothing. I'd hang up and a few minutes later the phone would ring again and this time all would be well. Does this follow any classic case (no audio / one way audio)? Thought I'd mention this in case this is related to the no-busy signal being discussed.

Do you have all the audio ports forwarded (35000-65000)? It sounds like maybe some port ranges aren't getting through to you and on the 2nd attempt when on a different port it is. If not, I'd recommend trying that to see if it clears this up for you.

**Russell** · 05-12-2009 09:26 PM

Originally Posted by VOIPoTim

Do you have all the audio ports forwarded (35000-65000)? It sounds like maybe some port ranges aren't getting through to you and on the 2nd attempt when on a different port it is. If not, I'd recommend trying that to see if it clears this up for you.

No, I have no ports forwarded. I've never had to port forward in the past (with ViaTalk using a PAP2T or SunRocket before ViaTalk) and I have a definite preference not to have to port forward. Surely, if it was an issue with port forwarding, I would have noticed this before?

**VOIPoTim** · 05-12-2009 09:41 PM

Originally Posted by Russell

No, I have no ports forwarded. I've never had to port forward in the past (with ViaTalk using a PAP2T or SunRocket before ViaTalk) and I have a definite preference not to have to port forward. Surely, if it was an issue with port forwarding, I would have noticed this before?

Support can do some traces to look into it more, but it's possible that the port ranges you're running into have shifted some since we've grown and maybe that's why they're not getting through. Again, no way to know without watching it happen, but 99% of the time the dead air issues are resolved with port forwarding and disabling any ALG so it sounds pretty close.

**voipinit** · 05-13-2009 03:44 AM

Russell, you also might try enabling UPnP support on your router, if it's not already.

**Russell** · 05-13-2009 05:32 AM

Originally Posted by VOIPoTim

Support can do some traces to look into it more, but it's possible that the port ranges you're running into have shifted some since we've grown and maybe that's why they're not getting through. Again, no way to know without watching it happen, but 99% of the time the dead air issues are resolved with port forwarding and disabling any ALG so it sounds pretty close.

If port ranges have shifted since I joined, it would explain the behavior. Essentially my setup is as follows: wireless router connected to the cable modem. VOIPo PAP2T connected to the wireless router. I also have an old Vonage RT31P2 connected to the wireless router (I have Gizmo5 and Freedigits - voip service - configured on the RTP31P2). Before my port from ViaTalk was complete, the ViaTalk PAP2T was also connected to the wireless router. And, they all happily co-existed. Of course, now that I'm ported there's no ViaTalk PAP2T and so there's one device less in the mix. The wireless router is an older 3-Com Router that has no ALG ability. uPNP is not enabled - I could enable it if it's felt that that would solve the problem. I have another PAP2T in my toolbox and really would like the ability to connect multiple ATA's behind the wireless router. When I had ViaTalk and the above setup, at one point I had the toolbox PAP2T connected with AOL's now defunct free service and Future Nine (I still have an account with them).

**sr98user** · 05-13-2009 05:28 AM

Originally Posted by Russell

I had a tree down over the weekend and was at home yesterday making calls to tree contractors. And, they would call me back ... at least a couple of calls when I picked up the phone I would hear nothing. I'd hang up and a few minutes later the phone would ring again and this time all would be well. Does this follow any classic case (no audio / one way audio)? Thought I'd mention this in case this is related to the no-busy signal being discussed.

I had similar issues yesterday around 11.15am. On incoming call, when I pick up Line1, no audio, Line2 keeps ringing, after few seconds, my cell phone (network down number) rings.. After hanging up everything, my cell phone would ring again after few minutes. I pickup the call, and its dead air. Caller said they heard no rings, only silence.

On outgoing call to my cell phone, I had one way audio to my cell phone. After hanging up, my cell phone would ring after few minutes.. Again I pick up the call and its dead air.

I updated my router's firmware about a day back. Everything was working well until 11am yesterday. During the time I was having problems, I did not have any dropped packets, NAT entries were still there. Not sure what happened. But I went back to my old firmware and everything has been fine. But I still can't explain what happened during that time... Could be the firmware. But it was running fine for close to a day and no dropped packets or NAT entry problems.