I've been using an Obi110 with
voip.ms without issue since 2011 (originally setup through Obi Dashboard). I foolishly decided to set it up from scratch via the Obi Dashboard before making a backup of my working cfg. Now
I'm unable to receive inbound calls. When trying to call the device I receive a busy signal.
- Firmware 1.3.0 (Build: 2872)
- According to both the Obi and
voip.ms Dashboards my device is "green" and "registered".
- Outbound calls work.
- Troubleshooting via Obi callback works, the phone rings.
- Only one provider (voip.ms) in use. No GV or analog service.
Steps I've taken to troubleshoot:
- Multiple reboots and setup attempts from scratch (paperclip and delete device via dashboard)
- Placed Obi110 in DMZ of my OpenWRT router.
- Connected Obi110 directly to AT&T Uverse Modem/Router.
- Tried various
voip.ms servers with ports 5060 and 5080.
- Setup manually according to
http://wiki.voip.ms/article/OBi_100/110- InboundCallRoute set to ph instead of {>xxxxxx:ph}
This is definitely a config problem with the Obi110. I still can't believe I didn't make a backup first, completely out of character. Any suggestions would be greatly appreciated.
