Direct connectivity issue (due to SIP "Contact")
RonR:
Quote from: oleg on May 21, 2011, 10:34:23 am
INVITE sip:ipkall@xxxxxxxx.dyndns.org SIP/2.0
IPKALL is set to forward to:
SIP Phone Number: ipkall
SIP Proxy: xxxxxxxx.dyndns.org
The 'SIP Phone Number' is ignored by the OBi. I set it to the DID's name (ipkall, ipcomms, etc.).
Quote from: oleg on May 21, 2011, 10:34:23 am
Contact: "RonR" <sip:u1234500000@192.168.1.140:5060>
u1234500000 is the AuthUserName of the SIP provider configured on SP2. It doesn't have to be registered (in fact, that SIP provider is down this morning and the OBi is trying unsuccessfully to register over and over).
Quote from: oleg on May 21, 2011, 10:34:23 am
- you have never OBi software (OBIHAI/OBi110-1.2.1.2309)...
This is an intermediate version to fix the bug that was introduced in 2286 that causes X_SkipCallScreening to fail on anonymous incoming Google Voice calls.
obi-support2:
oleg,
Port forwarding will not help with this situation.
You want OBi to use external IP in contact, but you don't want to register the main service.
OBi needs to figure out the external transport address. OBi WILL NOT use the one
that is used in the SDP.
Please try the X_KeepAlive ... feature as explained in the OBi admin guide.
It is relevant.
oleg:
RonR,
Quote from: RonR on May 21, 2011, 10:46:21 am
The 'SIP Phone Number' is ignored by the OBi.
that's quite strange. In Linksys ATAs those must be the same, otherwise ATA would disregard incoming call. That makes OBi more open (for both good and bad)...
well, I made both ("Number" on ipKall side and "AuthUserName" on OBi110 side) the same as yours :) - it did not change anything :(
will try to register (as per obi-support2 advise), although I do not see why it may be relevant...
RonR:
Setting:
X_KeepAliveEnable : (checked)
X_KeepAliveServer : stun.ideasip.com
X_KeepAliveServerPort : 3478
X_KeepAliveMsgType : stun
does change the Contact field to the public IP address.
However, with that I get no audio in either direction on IPKall calls.
oleg:
Quote from: obi-support2 on May 21, 2011, 10:50:15 am
Port forwarding will not help with this situation.
I agree. But doesn't KeepAlive serve the same purpose - to keep NAT port open and forwarded to OBi?
Quote from: obi-support2 on May 21, 2011, 10:50:15 am
You want OBi to use external IP in contact, but you don't want to register the main service.
OBi needs to figure out the external transport address. OBi WILL NOT use the one
that is used in the SDP.
I have SP1 registered with GV. SP2 was not registered. OBi had my external address from two sources: GV on SP1 and STUN on SP2. External IP was correctly placed into all places, except "Contact" - why?
But registration did the trick - when I registered SP2 - "Contact" field got external IP address and incoming ipKall call came through. Note that I changed nothing related to KeepAlive and NAT.
Thus two questions:
- why registration is required for correct "Contact"?
- how incoming ipKall worked in RonR case?
Navigation
[0] Message Index
[#] Next page
[*] Previous page