Obi200 trouble w/ voip.ms since ~Oct 12
Steve_M:
After months of very stable service, I'm having a sudden issue with my Obi200 and voip.ms service.
Problems Initially manifested as calls ending to a dial tone at the 15 minute mark (+/- 10 seconds).
That continues and now there are two other issues:
* callers receiving dead air (no ring on my end)
* outbound calls receiving a message "<tri-tone> the number you have dialed <states number dialed> did not receive a response from the service provider"
Does still work sometimes, and I've even had 3 calls (out of about 15 attempts) last more than 15 minutes while the other 11-12 ended right at that magic 15 minute mark.
I've reset the Obi, and set it back up via the ObiTalk site - no change.
Hardware 1.4
Firmware 3.1.0 (Build: 5264)
RegisterExpires is set to 300
Appreciate any ideas & expertise!
Mango:
Given that the issue often happens close to the 15 minute mark, the first thing I would suspect is a session timer attempting to refresh the session and failing.
The message "...did not receive a response from the service provider", on a correctly-configured ATA, often indicates corrupted NAT tables. This is probably also causing your calls to drop around 15 minutes.
Did you make any chances to your router around October 12?
Does your router receive a public IP address from your ISP, or do you have multiple routers?
Do you have your router's SIP ALG enabled? If so, try to disable it. If that's not possible, set your ProxyServerPort and RegistrarServerPort for the ITSP Profile configured for VoIP.ms to 42872, and set your X_UserAgentPort for the Voice Service configured for VoIP.ms to a random number between 20000 and 65535, for example 28746. You will need to use OBi Expert Configuration to make this change.
Are your X_KeepAlive settings (from within the Voice Service configured for VoIP.ms) set to defaults?
What router do you use? Do you have access to a different brand of router to test with, to confirm my guess that the router is the problem?
Let us know how things go.
m.
Steve_M:
* no changes on my end, and nothing the ISP told me about (Eastlink, in Canada). Same modem/ISP/Obi I've had for months.
* Obi is connected directly to ISP's cable modem (Surfboard SBG6580). That said, I don't think I have a SIP_ALG setting accessible to me on that modem.
* Obi receives a public IP 76.x.x.x.
* X_Keepalive are all default checked - sharing values here in case the defaults could be somehow wrong
* * X_KeepAliveEnable () - unchecked
* * X_KeepAliveExpires (15)
* * X_KeepAliveServer () - empty/blank value
* * X_KeepAliveServerPort (5060)
* * X_KeepAliveMsgType (keep-alive)
* No alternate router (modem) easily accessible, though if all else fails I'll take the Obi to someone else's house.
I know I have power-cycled the modem since the 12th as a troubleshooting step, but not recently. Will complete that tonight, in case there was an ISP issue that's since been solved.
If issue reoccurs, I'll move on to "set your ProxyServerPort and RegistrarServerPort for the ITSP Profile configured for VoIP.ms to 42872, and set your X_UserAgentPort for the Voice Service configured for VoIP.ms to a random number between 20000 and 65535, for example 28746"
Also, Is there a way to turn on any detailed logging (voip.ms or Obi-side) that would give a more definitive error log?
Thanks much for the reply and ideas so far.
Mango:
Quote from: Steve_M on November 06, 2016, 06:29:09 pm
* Obi receives a public IP 76.x.x.x.
This is a problem. The OBi200 does not contain a firewall. (OBi202 does). The 200 should not be exposed to the internet without a router as it is vulnerable to DoS and other attacks.
Could you describe your network? Does your computer also receive a public IP or is it behind a router? If the computer is behind a router, perhaps you could put your OBi200 behind the same router.
Steve_M:
Ouch, a rookie mistake on my part, thanks!
Currently, everything else on the network sits behind a router w/ DD-WRT loaded. That router gets a public IP WAN-side, and hands out 192.x.x.x on the LAN & WLAN side via DHCP.
I'll shuffle some wires around in the AM, and start reading up on NAT/port forwarding, etc.
Navigation
[0] Message Index
[#] Next page