Device not registered

[stevech]

Unfortunately we do not offer monitoring of customer equipment or customer networks. We only monitor our own network.

Please consider:
The ATA is YOUR equipment.
Your server/network equipment elects to invoke fail-over for incoming calls due to some problem with your ATA communicating with your servers. My gripe is that I cannot know the fail-over was invoked because VoIPo does not inform the customer by email or SMS or a robo-call that this has happened. But moreover, VoIPo is imprudently declining responsibility.

Of course I am responsible for the router to be configured to accomodate. But tech support's only cure so far has been to temporarily move the ATA to the WAN side then back again. There needs to be a competent diagnosis of what is actually causing this, so the cure can be developed. The ATA, as I understand, is supposed to notify audibly and/or by flashing LEDs that there is a registration/re-registration fault. It does not do so. But something causes VoIPo's servers to invoke the fail-over for incoming whilst the outgoing calls still work normally. I only ask that someone actually troubleshoot this.

[VOIPoTim]

Please consider:
The ATA is YOUR equipment.
Your server/network equipment elects to invoke fail-over for incoming calls due to some problem with your ATA communicating with your servers. My gripe is that I cannot know the fail-over was invoked because VoIPo does not inform the customer by email or SMS or a robo-call that this has happened. But moreover, VoIPo is imprudently declining responsibility.

While we do own the adapter, it's in your possession and connected to your network. We do not monitor customer equipment or intend to monitor customer equipment. Residential VoIP providers do not monitor anything beyond their own networks. Again, this has been debated over and over in multiple threads and we're not going to continue debating it. We do not monitor customer equipment, customer networks or anything in the customer's possession. We only monitor our network.

Failover has nothing to do with whether a device is registered or not. It kicks in when our packets can't get through to the adapter. If it's not registered, obviously that would be the case and it would kick in. If your device is not saying it lost its registration when you pick up the handset then it's likely still registered but your router is not letting the traffic through which is why this is happening. Many routers have this issue periodically and a reboot resets the NAT table and allows things through again.

Bottom line...ou seem to be having an extraordinary amount of problems and have stated that you've already worked with support and they were unable to resolve your issues. If support has worked with you multiple times and you still have issues, you will continue to have those issues.

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

There is no need to continue to experience problems. We recommend finding an alternative service provider at this time since you appear to be in the 1% of our customer base that has chronic issues.

We also do not offer monitoring of customer devices and based on the fact that you've posted it many many many times, it seems like that is a deal-breaker for you and our service does not offer a feature that sounds like a deal breaker for you.

While we hate to lose a customer, we don't want you to experience chronic service issues and use a service that does not provide the features that are important to you. Another provider may be able to better accommodate you.

[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.....