Anveo E911 problems

(1/2) > >>

since83:
Hi All,

Using an Obi 100 with google voice on SP1 and Anveo E911 on SP2.  Google voice is working fine, but for several hours now my Anveo E911 service has been down.  Obitalk portal shows status as:

Register Failed: no response from server - bunch of numbers and dots; retrying

Anyone else having this problem today?  Any hints on how to fix?  Is this problem likely on my end or Anveo's (nothing noted on Anveo's status pages).  Have not had any problems with Anveo since I started with them about 20 months ago.  Money is in the account, so that is not the issue.

Thanks,

Since83

SteveInWA:
Contact Anveo and get them to troubleshoot it.   You're paying them for it.

since83:
Thanks. Did contact Anveo (though a support ticket).  They say nothing wrong on their end.  Told me to reboot cable modem, router, and obi 100.  Did so, but problem remains the same.  E911 service just won't register/connect on SP2 (complete failure after 20 months of perfect operation).  They say to look in obitalk for error relating to the SP2 slot.  Not quite sure what they are referring to, but there are no obvious errors in obitalk that I can see (should I be looking someplace special - I have browsed through the expert configuration pages).  Is it possible that Obi device SP2 slot is broken, but SP1 slot (being used for google voice) is OK?  Been down about 19 hours now.

Can someone suggest what to do next?  Would deleting the Anveo service then adding it back be an approach?  If so, are there any pointers?

Thanks,

Since83

since83:
OK, I think I fixed it.  I followed the standard Obitalk troubleshooting steps.  Changed user agent port on SP2 port from Obitalk default 5081 to 5061.  Service is back up and running.  Does anyone have a reason why the default port would suddenly not work after 20 months?

Since83

Mango:
Typically this happens when your router's NAT tables become corrupted.  This can survive a router reboot.

I would use OBi Expert Configuration to enable X_ProxyServerRedundancy and see if that solves the problem.

What router do you use?

Navigation

[0] Message Index

[#] Next page