Obi202 makes calls but cannot receive
drgeoff:
Quote from: JimboForum on October 07, 2016, 09:22:31 am
To save me having to reset the modem-router - instead I plugged the Obi into a different LAN - (using hotspot on iPhone and internet sharing on Mac - connected to Obi via Ethernet).
Unfortunately same result -
SP1 - GoogleVoice - OK
SP2 - SIP - outgoing only
SP2 - SIP - outgoing only.
I think at this stage I'm going to have to think its an Obi problem - though a strange one.
You don't reset the modem-router.
I've suggested several times that you connect the OBi directly to the modem-router. Why are you so reluctant?
JimboForum:
Not reluctant at all. In fact I had already done that but no joy. I've just done it again to confirm my findings.
For reasons I don't understand the Obi doesn't like being connected directly to the modem - it is as if it is not responding to the ISP's DHCP server. After it has all settled the Obi responds to an outgoing call attempt with "network status: IP address unavailable".
drgeoff:
Two suggestions. Apologies if the first one insults your intelligence.
1. Ensure you are using the 202's WAN port, not its LAN port. I don't have a 202 so don't know what can and can't go through its LAN-WAN barrier.
2. You seem sufficiently tech savvy to be able to fire up a syslog server and point the OBi to it.
drgeoff:
3. Item 7 on https://didlogic.com/support/setup-guides/linksys-pap2-ata ? (The bit about unchecking 'Send didinfo'. The OBi devices are descended from the Sipura/Linksys ATAs through some common engineers on both.)
JimboForum:
Ah, now that fixed it! No idea why it had changed but un-checking send didinfo has cured the problem.
(now I can put all the syslog stuff away again).
Thank you oh Great One.
:)
Navigation
[0] Message Index
[*] Previous page