Direct connectivity issue (due to SIP "Contact")
oleg:
FWIW, I removed registration and added X_KeepAlive*** settings (exactly as RonR shown above).
Contact had external IP and ipKall session established (and had both way audio).
The OBi admin guide indeed describes this way of NAT traversal, but (once again) why without registration or KeepAlive external IP known to OBi can be used everywhere, but not in "Contact" field ???
And I still vote for flexibility - why not allow user to configure "Contact" with SIP URI (sip:1234@sip.host.com) containing reliable host name rather than IP.
obi-support2:
A transport address includes an address and a port number. Two transport addresses are required per SIP call; one for SIP signaling and one for RTP media. Let's also refer to a private to external transport address map as a "binding". To achieve peer-to-peer communication, the device needs to discover SIP and RTP binding. When your device REGISTER, there is an opportunity for your SP to tell the device what the SIP binding is (try comparing the Via header of the REGISTER request and the corresponding 200 OK response); this solves the SIP binding discovery problem. RTP binding on the other hand has to be discovered with a STUN transaction. However, if you don't REGISTER (or your SP is not co-operative), another STUN transaction is required to discover the SIP binding (the OBi does this using the Keep Alive feature).
We prefer STUN or the equivalent than hard coded EXTERNAL IP configuration (as used in other implementation) since external IP address may change from time to time for most users.
I am sure there will be further enhancements as the demand grows. Thank you.
oleg:
:-[ Well, you are right, I totally forgot about port - in my setup external port never differs from internal (linux based routers normally preserve port number)...
When REGISTER - it perfectly makes sense to take SIP binding from response.
Otherwise it seems much more logical to call STUN for both SIP and RTP when call is being initiated. Why one can be resolved on demand while other requires periodical check in keep-alive manner? Separating them is also counterintuitive - I would never guess that "Contact" included internal address because of lack of STUN resolution when the log shown STUN interaction and RTP endpoint was correct.
Quote from: obi-support2 on May 22, 2011, 04:17:22 pm
We prefer STUN or the equivalent than hard coded EXTERNAL IP configuration
I never suggested configuring external IP. It can be done of course (if someone has static IP), but it makes much more sense to configure SIP URI.
Quote from: oleg on May 21, 2011, 11:58:04 am
... allow user to configure "Contact" with SIP URI (sip:1234@sip.host.com) containing reliable host name rather than IP.
Thank you for the help (now I can retire PAP2T)
Seattleweather:
This is an old post. But I would like to know if you are able to receive the call by using sip:xxx@xxx.no-ip.org to reach your Obitalk directly from outside. If the answer is yes, please show how. Thanks.
Stewart:
This is a complex issue, depending on your router and the capabilities of the external source.
In general, if you forward the UDP port specified by the X_UserAgentPort setting for the SPx in question to the private IP address of the OBi, an external call will look like an incoming call to SPx (though with a different destination number) and you can set the InboundCallRoute to route it as desired.
For more specific advice, post details about your application, e.g. "I'd like calls to my IPKall DID to ring my cell phone via GV."
Navigation
[0] Message Index
[#] Next page
[*] Previous page