No busy tone on VOIPo

[Russell]

Great -- glad to hear it is working for you. That Busy Tone you are hearing is the normal PAP2T response to Busy signal:

480@-19,620@-19;10(.5/.5/1+2).

Again, if anyone else has issues with this please do let me know, thanks!

My child just reported similar symptoms. I think it's the call at 19:02 EDT in my call logs if that'll help.

[VOIPoBrandon]

My child just reported similar symptoms. I think it's the call at 19:02 EDT in my call logs if that'll help.

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!
________
Maryjane

[burris]

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!

Hi, Brandon....

Coincidently, the same problem just showed up here..
Calling from my 305 number to 954-458-xxxx 3 times starting at 7:47pm tonight.
Found out their number was disconnected.

VOIPo line goes nowhere....no intercept...nothing...dead air.
Cell call to same number gets intercept..call cannot be connected...etc.

The busy tone is set up the way you described in a previous post..

[VOIPoTim]

Hi, Brandon....

Coincidently, the same problem just showed up here..
Calling from my 305 number to 954-458-xxxx 3 times starting at 7:47pm tonight.
Found out their number was disconnected.

VOIPo line goes nowhere....no intercept...nothing...dead air.
Cell call to same number gets intercept..call cannot be connected...etc.

The busy tone is set up the way you described in a previous post..

So the busy signal is working fine for you, but the disconnected message you should get isn't?

[burris]

VOIPo call to the disconnected line gets nothing...dead air...no busy-no message.

Cell call to same line gets intercept that call cannot be connected.

[Russell]

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?

[frankd1]

FWIW, I think you're talking about the same issue I posted about last week:

http://forums.voipo.com/showthread.php?t=1413

It'll be nice to have the issue addressed.

[VOIPoBrandon]

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]

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]

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.