Calls give busy signal after answering

**dteague** · 11-21-2009 06:46 PM

I had a problem today around 4:47 where my wife was calling and both time I picked up the phone to a fast busy. She got home about 45 minutes later and called and it worked fine.

**gavakie** · 11-23-2009 10:10 AM

Its working again. I ran there network test program and the moved me to servers. It was a latency issue. As for vonage I have been with them for years and my brother in law who signed up right after me already has his number ported and I really want to cancel so I don't have to pay for two phone services. I really appreciate these guys' fast response to issues. Sucks when it happens on weekends though. Thanks Voipo.

**bwyatt** · 12-13-2009 11:43 AM

This has been a persistent problem for me that has still not been resolved. Support has been very diligent in helping to resolve it, but just when I think it's going away, it comes back. There is no consistency at all. Below is the support ticket I just submitted:

Everyday I experience one or more incoming calls that do not connect. The caller tells me they dial my number but it never connects on their end. On my end the line rings, but when I answer there is silence for about 3-5 seconds then it goes to a fast-busy sound. The problem is always temporary. It works most of the time and doesn't once in awhile, but often enough to be an issue. I've submitted a ticket on this in the past and support indicated they would "condition" the lines. Whatever was done seemed to improve the performance, but the connection problem is still occurring too frequently for my service to be consistently reliable.

I'm posting here also, because you guys are so good with suggestions and I'm hoping someone reading this has an idea that might work.

I'm using Comcast for my internet service, standard D-Link router with latest firmware. I have both RT31P2 and PAP2 devices with VOIPO and have the same problem on both devices. I have DMZ'd the device temporarily for troubleshooting purposes and experienced the same issue even while it was DMZ'd. I have port forwarding rules set according to support's instructions and the SIP 'ALG' option on the router is turned off.

Any suggestions would be much appreciated.

**chpalmer** · 12-13-2009 03:14 PM

I have not had good luck trying to use two devices on the same number behind the same public IP. Although Ive never had any other issues running an RT31P2 behind my pfSense router.

Try disconnecting and secondary Voipo devices you might have, reset everything including modem and routing device(s) and try it that way for a while.

**fisamo** · 12-13-2009 04:00 PM

Are you able and willing to test for the problem with your RT31P2 placed before your home router? it would be nice if you could take the router completely out of the picture, at least for some troubleshooting time. Granted, I understand if you cannot...

**bwyatt** · 12-14-2009 11:37 AM

My ticket was answered on a SUNDAY! no less... and after "adjusting the devices to make them work better together" I haven't had this issue to occur since.

Not sure what was done, but it appears to have done the trick.

**bwyatt** · 12-16-2009 07:15 PM

Here's an update:

My numbers ported over the weekend. Something about the change apparently reverted some of the conditioning back to the default. All was reworked and everything is again working perfectly. Even with multiple devices behind a router.

I have to say I am very very impressed with the diligence of the voipo support team in resolving a problem. You guys are top-shelf, and first-rate.

I'm proud to be a voipo customer.

**bwyatt** · 12-18-2009 10:49 AM

This off and on problem won't go away. I'm thinking my lines are functional about 3/4ths of the time. As soon as you think it's fixed, the problem returns.

Now, for the first time, the problem has reversed itself. I'm unable to call out. Instead, I get a fast busy on my end trying to dial someone else.

We have a major winter storm approaching and I have no outgoing phone service and marginal incoming.

**bwyatt** · 12-18-2009 06:57 PM

Update:

This is obviously a frustrating problem and working to resolve. I'll post an update tomorrow, but I can't say enough about VOIPO's persistance in helping to resolve.

Thanks for all the help today guys!

**roehrle** · 12-20-2009 08:37 AM

I was having the busy signal problem also but it was only on my 2nd line. Put a ticket in and it appears that removing the security on the ATA "cured" the problem for now. Line 1 worked OK during the problem period.