Just received my new OBi302. I am trying to register it on the OBiTALK portal.
Whenever I attempt the given **5 xxxx the OBi tells me, "There is no call route available to complete your call".
It's getting an IP address, and I can successfully do the **9 222-222-222 echo test. The power LED remains solid for a while after it has obtained an IP address, but goes back to flashing regularly about twice a second. Again (see below) I am confident it's getting an IP address because (a) echo test succeeds, and (b) I've been looking at/doing a lot through the built-in OBi admin page via that IP.
The OBi Internet port is attached to a LAN port on my Netcomm NB9WMAXXn. I don't believe this unit has a SIP ALG feature to disable, but happy to be shown I'm wrong. I was previously using it as the VoIP unit but the VoIP portion went flaky. I've disabled everything VoIP-related in it I can find.
Here's some of the things I've tried:
- Set router DMZ host to to the OBi.
- Enabled the WAN admin ability on the OBi and manually set the DNS servers to 4.2.2.2 and 8.8.8.8.
- Updated the firmware to the latest (at time of writing, 3.1.0 (Build: 5110)).
- Enabled the syslog output and viewed it in a syslog server. During the **5 xxxx sequence you don't get much log output apart from the DTMF detection and eventual ringback tone and sit_1 tone generation.
I would consider bypassing the OBiTALK portal admin of the device and just do it locally, but it looks like this firmware only offers a cut-down admin interface (no ability to set SP1, SP2 etc).
So frustrated. Any help would be appreciated.