Device not registered

[caseydoug]

Tim, it appears that most of these type of problems are related to the customer's router. Out of curiosity, do you have fewer problems when the ATA is placed in front of the router so that traffic does not have to go through it? Wouldn't that obviate the need to forward ports, etc.?

[VOIPoTim]

Tim, it appears that most of these type of problems are related to the customer's router. Out of curiosity, do you have fewer problems when the ATA is placed in front of the router so that traffic does not have to go through it? Wouldn't that obviate the need to forward ports, etc.?

Yes, that's why we mainly use HT502s now (built in router) and encourage customers to put them in front.

[tritch]

VoIP is highly dependent upon a customer's network setup, ISP and router and not all combinations work well with all providers..

I agree 100% with this statement.

After reading your numerous posts over the past several months, your symptoms are logically pointing to your router as the culprit not Voipo. Since nobody else is having this issue, the logic tree applies. As suggested by another poster in another thread, SIP ALG shoud be turned off in your router because this is likely to cause problems as noted in other VOIP forums, but it appears you have not done so based on your latest posts. If so, then why not?? This may be causing the issue.

Your Cradlepoint MBR900 is a "specialized" router with built-in failover to 3G/4G networks, which in itself requires "specialized" firmware to make it all work. Bugs in router firmware are found all time, so who knows what else may be in play here especially since they just released a new version supporting LTE. Without knowing your full network topology, there may be port issues going on as well. I suspect if you temporarily connected your ATA directly to your cable or DSL modem the problems would permanently go away. Since it appears you need Internet failover router, your options are limited at this point.....

[voipinit]

...
There are TWO PROBLEMS HERE
1. VoIPo does not make any attempt to warn customers that there is some sort of server/registration renewal error in VOIPO's SERVERS such that outgoing calls are normal but incoming calls roll to the backup number. VOIPO's SERVERS KNOW there's a problem because THEY elected to initiate the incoming forwarding. But VoIPo elects to not warn the customer. Nor does the ATA detect a flaw and warn the customer. Let's make this clear: VoIPo's servers NOT ME, elected to invoke forwarding of of incoming calls to the backup/fail-over. That should tell support that something's wrong. The ATA is not reporting a registration error. Outgoing calls normal. ...

Your thinking is a little flawed. VOIPO's servers do not know in advance if the call is going to your ATA or the alternate failover route. When you receive an inbound call, VOIPo servers send an "invite" to your ATA, if your ATA does not respond back, the call is then rerouted to your failover option.

[r111]

Can the Linksys rt31p2 ATA provided by VOIPO (at another location and is rock solid) be configured to be in front of a router? If so, can support swap the provisioning on my two accounts -- so I can swap my pap2t which doesn't seem to work behind a router to the rt31p2 which might?

[VOIPoTim]

Can the Linksys rt31p2 ATA provided by VOIPO (at another location and is rock solid) be configured to be in front of a router? If so, can support swap the provisioning on my two accounts -- so I can swap my pap2t which doesn't seem to work behind a router to the rt31p2 which might?

Sure, just contact support@voipo.com letting us know you'd like to switch them.