Getting SIP to work on Obi 202
ianobi:
lk96,
It looks like an RTP problem. I would recheck that you have forwarded the correct UDP range for SP4.
If that's ok, then it might be worth trying STUN:
Service Providers > ITSP Profile D > General:
STUNEnable: check
STUNServer: stun.ideasip.com (or stun server of your choice)
lk96:
ianobi:
thanks. Have cross checked that the appropriate port ranges
are open on the firewall.
And I already had STUN setup (pointing to ekiga.net). Will retry a different STUN server
(just for the heck of it). But I suspect the result wouldn't be much different.
I even put the obi202 device on the DMZ to see if that makes a different: no change either.
So either the Dlink router/firewall is acting up or i have some different type of issue.
thanks again for the suggestions
L.
azrobert:
You can try some config settings discussed here:
http://www.obitalk.com/forum/index.php?topic=5987.0
lk96:
azrobert
thanks for the pointer.
My issue was resolved by entering my actual public IP address, as indicated
in some of the comments in the post you forwarded,
in the X_publicIPAddress manually.
After that, things started working fine. So that was it !
So this is strange given that I tried both STUN and ICE and apparently both of them
were probably sending the internal obi IP address. But apparently others have experienced
this issue before.
L.
hwittenb:
Quote from: lk96 on June 25, 2013, 08:49:41 am
azrobert
My issue was resolved by entering my actual public IP address
So this is strange given that I tried both STUN and ICE and apparently both of them
were probably sending the internal obi IP address. But apparently others have experienced
this issue before.
ik96
The sip protocol has buried in the packet the ip address the caller should use for a contact response. Your problem here has to do with the undocumented OBihai technique they employ as to whether to send a sip response showing an external ip address or a local network address.
You fixed the problem by setting the numeric public IP address. I can also duplicate your problem using an IPKall DID by setting up a voip account in SP4. The voip account doesn't necessarily have anything to do with your Voxbeam DID. If you check the setting to Register the voip account the incoming call using the DynDNS symbolic ip address will work fine. If you uncheck the setting to Register the voip account the incoming call will not have audio due to the OBi sending a local network ip address in the sip 200 OK response when the call is answered.
Using a STUN server shows the OBi adapter the external ip address, but OBi does not use it in certain cases. In fact the Admin manual says:
It should be noted that the STUN feature used in this context is only for RTP packets, not SIP signaling packets (which typically does not require STUN).
Navigation
[0] Message Index
[#] Next page
[*] Previous page