Direct connectivity issue (due to SIP "Contact")
oleg:
Obihai,
Thank you for recently added options to support NAT traversal for URL calls. That solved bunch of issues.
Now the only problem prevents me from replacing old PAP2T with OBi - absence of direct connectivity with Linksys devices. I previously described the problem here http://www.obitalk.com/forum/index.php?topic=483.msg2881#msg2881 (see for details)
In short - regardless of NAT/STUN settings OBi device sends local network IP address in SIP "Contact" field. It causes other party to send undeliverable ACK and session never establishes.
The solution would be to make it flexible - give users a choice to send "Contact" with local IP or NAT detected IP or with manually entered SIP URI.
Could you please consider that simple change in following releases?
Thank you
---oleg
RonR:
oleg,
In the original post you referenced, you asked:
Quote from: oleg on March 25, 2011, 05:38:53 pm
P.S. Has anybody success receiving calls via ipKall? That seemed to suffer from the same issue. I can't say ere ipKall sends ACK to, but OBi does not receive it.
I replied at the time that I could not get IPKall to work with the OBi either, even though it worked well with a PAP2.
Since then, there was a firmware update that made some changes to SIP handling. I recently found I no longer have problems with IPKall, IPComms, and others:
http://www.obitalk.com/forum/index.php?topic=895.0
I now also use a PAP2 as an extension off of the OBi:
http://www.obitalk.com/forum/index.php?topic=718.msg5467#msg5467
oleg:
Hi Ron,
I just verified OBi110 (running software 1.2.1 Build: 2286) with ipKall - SIP stuck on the same. The phone rang, when answered - OBi sent "200 OK", and continued repeating "200 OK" (because never received ACK).
A while ago (with previous OBi software release) I tested OBi incoming call from my friend's Linksys - failed to establish session. The log on Linksys side shown that ACK is being sent to my OBi's local IP (undeliverable from Linksys side). The only place where my local IP was exposed to Linksys was the "Contact" header sent by my OBi110.
Your setup with PAP2 as an extension is very interesting indeed, but's that's not my case. In your setup both devices run on the same LAN. In mine - OBi110 works behind NAT and connecting through internet.
RonR:
oleg,
Do you have the appropriate SIP port forwarded in your router to your OBi?
I don't know if this will help you, but here is a Syslog from my OBi for an incoming call from IPComms (it works equally well with IPKall).
obi-support2:
oleg,
You have this issue because you do not REGISTER on your SP1/2 main service.
Have you tried to enable X_KeepAliveEnable and set X_KeepAliveMsgType = stun,
(also set X_KeepAliveServer and X_KeepAliveServerPort to point to a valid stun server)?
Take a look at the NAT Traversal section in OBi Admin Guide. These options should
help with your particular situation.
Thank you.
Navigation
[0] Message Index
[#] Next page