No busy tone on VOIPo

[Xponder1]

I was unaware of this until today and I want to share it with you all in case your also unaware of this issue.

Today my wife tried calling a local number. All she gets is dead air. She tried twice. The third time it worked. I submitted a ticket to let support know and this was the response I received.

There are no network or server related issues.

The dead air could imply that the callee was busy on a call and that they dont have call waiting.
Currently there is no busy signal on our end, meaning you'd just get dead air and then it will finally end (this is actively being worked on).

So if the number is busy per support your just going to get dead air. I wish I had known this months ago because every time this happens I submit a ticket so they can look in to it.
Every time it has happened I have tried other numbers and they work. Usually the response from support is there was some network issue and its resolve now. This is a first.

Tim you need to communicate this to the customers lol.

[dswartz]

this behavior seems totally broken, IMO. no-one coming from the pots world would expect this.

[Xponder1]

this behavior seems totally broken, IMO. no-one coming from the pots world would expect this.

Ya thats why I posted it here. Every customer should be told this. I can not imagine how many support tickets have been directly related to this. I mean its great they are working to resolve it but this is kind of important.

[VOIPoTim]

This reason wasn't accurate.

There is a bug where we're not responding to some response codes correctly generating a busy, but it's definitely not ALL cases where the line should be busy.

We're working to isolate the specific scenarios that causes it so we can adjust and generate a busy for them.

See http://forums.voipo.com/showthread.p...hlight=offhook for some info. It's the same issue (we just suppressed the goodbye error since it was confusing).

Regardless, it's a pretty quick fix and I'm not sure why it hasn't been done already. I'll have someone do some more testing with all the possible scenarios and fix it this week.

[Russell]

this behavior seems totally broken, IMO. no-one coming from the pots world would expect this.

I'm glad I read this thread. I experienced dead air yesterday. Called back after about 20+ seconds when I concluded nothing was going to happen and it connected fine. I would agree - this needs to be fixed and nice to note that Tim's comment that it'll be done this week. Tim, please post back when this happens.

[Xponder1]

This reason wasn't accurate.

There is a bug where we're not responding to some response codes correctly generating a busy, but it's definitely not ALL cases where the line should be busy.

We're working to isolate the specific scenarios that causes it so we can adjust and generate a busy for them.

See http://forums.voipo.com/showthread.p...hlight=offhook for some info. It's the same issue (we just suppressed the goodbye error since it was confusing).

Regardless, it's a pretty quick fix and I'm not sure why it hasn't been done already. I'll have someone do some more testing with all the possible scenarios and fix it this week.

Thank you for the update Tim. I appreciate you clearing that up for me. I remember getting that good-bye message. That was confusing but silence is just as confusing lol.

[Xponder1]

Tim I wanted to let you know I just tested this and this was the results.

I have a pots line with no features (no call waiting ect). I took the pots line off the hook and called the number. Dead silence. When I was done hung up both lines and the pots line rang once.

So this made me try again. This time I repeated the process but waited for 30+ seconds of silence then hung up only the pots line. It almost (about a 3 second delay) immediately started ringing. Answered it and they call was there.

So it seems its not giving a busy tone because its trying none stop to complete the call. You may already be aware of this but again I just wanted to share.

Edit- Repeated test again same results.

[VOIPoBrandon]

Hey guys -- this should now be resolved, please do let me know if otherwise, thanks!

[Xponder1]

Hey guys -- this should now be resolved, please do let me know if otherwise, thanks!

Did the same test and it does now give a busy tone. It actually gives one then changes to another and then another lol.

Thanks for taking care of that!

[VOIPoBrandon]

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!