Voipo Down ?

[fisamo]

Surely rewiring your home is a trivial exercise as a part of troubleshooting your VoIP service... {/sarcasm}

I'm not sure what options support has to monitor individual users' devices when they have frequent reports of misbehavior (such as this), but if there's such an option you should request it. That may point out where the failure is occurring. I usually don't like to jump to the "Replace the TA" solution as an early troubleshooting plan, but maybe you would be better served with a PAP2T. Of course, you could always dig your spare PAP2T out of the closet (doesn't everybody have at least one?) and put the BYOD sip credentials on it to see if it will stay connected to the sip-byod server. I don't know how often you make international calls--outgoing int'l calls are not allowed on the BYOD server.

[burris]

I too, would vote for the PAP2T, but he needs to have a router in order to do so..

[walletless]

I don't have a PAP2T, unfortunately (am I the last person to not have a spare one?)

I have flashed DD-WRT, opened up the required ports, turned off SIP ALG, and turned on IPSec Pasthrough. Let's see if that makes any difference...

[Montano]

outgoing int'l calls are not allowed on the BYOD server.

I can't imagine they have a separate server for the 3 of us BYOD users

[walletless]

Btw, I am using a provisioned RT31P2, not a BYOD.. I am crossing my fingers that tomato was the cultprit, and dd-wrt will make things better. If not, I might have to check with Support on replacing RT31P2 with a PAP2.. but its too early for that IMO.

[fisamo]

To follow up on the BYOD idea, though... If you got a softphone on your PC and left it connected with the SIP credentials available in vPanel, that might be a good test platform. If the calls only 'ring through' on the softphone but not the ATA, you might be able to identify the ATA as the culprit. On the flip side, I'm not sure how much having a second registration to your account would affect the root cause of the problem, whatever it is...