Contact header on gateway call

(1/2) > >>

Stewart:
Using an OBi110 running 1.3.0 (Build: 2575), I'm trying to set up a system to make inexpensive calls from a prepaid cell phone (Orange) in Paris.

I have SP1 registered to ippi, SP2 registered to Phonepower, and VG1 set up for Voxbeam.  From the cell, I call the ippi number to trigger a callback.  The AA calls me back on Voxbeam; the call goes through fine.  I send DTMF to the AA and it places an outbound call on Phonepower.  The calls get bridged properly and I can talk.

However, when I hang up the cell, the OBi doesn't get the BYE from Voxbeam, because the contact header in the INVITE has the OBi's private IP.  I don't know why this should be; the STUN request is properly answered and the SDP on that INVITE has the correct public IP in the (o) and (c) entries.  The AccessNumber entry for Voice Gateway1 is SP2(sbc.voxbeam.com;ui=17758301234;op=ns) (I also tried op=s) (Voxbeam does not challenge the original INVITE, as it authenticates by IP address.)

Any ideas on what may be wrong?

Thanks,

Stewart

RonR:
Voice Gateways used with SIP providers have a number of limitations.  The OBi will:

- Not use the outbound proxy, ICE, or STUN regardless the settings on the SP trunk.
- Use only the device’s local address as the SIP Contact, and ignore any natted address discovered by the device.
- Use the gateway’s SIP URL to form the FROM header of the outbound INVITE.
- Use the gateway’s AuthUserID and AuthPassword for authentication.
- Apply the symmetric RTP concept.

Stewart:
Quote

Voice Gateways used with SIP providers have a number of limitations.  The OBi will ...
Yes, I had read that in the (somewhat outdated) manual.  However, the official post at http://www.obitalk.com/forum/index.php?topic=9.0 says:

Quote

- Added options to support NAT traversal for SIP Gateway and URL calls on SP1/2.
  You may now append these URL parameters to speed dial and SIP Gateway VG1-8 access number, separated by ';',
   - ui=userid[:password]
   - ui=user-info, password is optional
   - op=[ i ][ m ][ n ][ s ]        ;option flags, i=ice,  -m=symmetic-rtp, n=natted-address, s=stun
    Examples:
     SpeedDial = sp2(1234@sip.inum.net;ui=1000:xyz;op=sm)
     VG1-8 AccessNumber = SP1(sip.inum.net;user=1000;op=imns)
     Note that if userid or password is specified in VG1-8 AccessNumber, it overwrites the settings in AuthUserID, and AuthPassword in the VG.

RonR:
I hope you find a solution.  A typical answer from Obihai is:

Quote from: OBiSupport on September 27, 2011, 05:44:33 pm

As the suggested work-around does not work for your application, there is no solution.

RonR:
Quote from: Stewart on September 30, 2011, 11:49:31 am

Quote

Voice Gateways used with SIP providers have a number of limitations.  The OBi will ...
Yes, I had read that in the (somewhat outdated) manual.  However, the official post at http://www.obitalk.com/forum/index.php?topic=9.0 says:
.
.
.


The newly updated manual:

OBi Device Administration Guide
Version 28.09.11: 28 September 2011
This Revision: Revised for firmware version 1.3

makes no mention of:

Quote

- Added options to support NAT traversal for SIP Gateway and URL calls on SP1/2.
  You may now append these URL parameters to speed dial and SIP Gateway VG1-8 access number, separated by ';',
   - ui=userid[:password]
   - ui=user-info, password is optional
   - op=[ i ][ m ][ n ][ s ]        ;option flags, i=ice,  -m=symmetic-rtp, n=natted-address, s=stun
    Examples:
     SpeedDial = sp2(1234@sip.inum.net;ui=1000:xyz;op=sm)
     VG1-8 AccessNumber = SP1(sip.inum.net;user=1000;op=imns)
     Note that if userid or password is specified in VG1-8 AccessNumber, it overwrites the settings in AuthUserID, and AuthPassword in the VG.

Navigation

[0] Message Index

[#] Next page