Using OBi Voice Gateways with SIP Providers

<< < (8/16) > >>

RonR:
Does OneSuite support calling without SIP registration?  If OneSuite requires SIP registration, you won't be able to use it on a Voice Gateway.  You will also need a SIP provider provisioned on either SP1 or SP2 in order to be able to use a SIP provider on a Voice Gateway.

daibaan:
I am not sure if onesuite requires registration or not, but I have always enable registration on onesute connection, and that is how X_RegisterEnable in ITSP Profile A (used by SP1) is set.

However, you just reminded me that since I AM using onesuite as SP1 - with registration enable, that may have interfere  with the onesuite VG call using the same SP1 config? maybe I should change SP1 to sipgate  (which is actually the ultimate goal, because I want to use sipgate to provide a backup dial-in number) first and try the onesuite VG again. will get to it tonight

Thanks RonR

daibaan:
Problem solved with 1.2.1 (Build: 2283)

First, I have verified onesuite.com does not require registration.
Second, one thing a little strange about onesuite.com is the username format, the username for user "sam" is in the form of "sam-voip.onesuite.com" with proxy "voip.onesuite.com", so the fully qualified name would be "sam-voip.onesuite.com@voip.onesuite.com", this cause some SIP software/broker to be confused.

However, without changing any config, once the new 2283 firmware is loaded, the onesuite.com VG works like a charm, that is good enough for me I am happy now

daibaan:
Quote from: obi-support2 on May 09, 2011, 09:54:27 pm

Firmware Release 1.2.1(2283) has been posted. One enhancement includes is the
addition of options to support NAT traversal for SIP Gateway and URL calls
on SP1/2: You can now append the following URL parameters to each speed dial and
SIP Gateway VG1-4 access number, separated by ';',
   - ui=userid[:password]   //ui=user-info, password is optional
   - op=[m][n]          //option flags, i=ice, m=symmetric-rtp,
                                    //n=use-natted-address, s=stun


Thanks for the info, 2 questions regarding these enhancement:

Does the "ui" option overlaps the "AuthUserID/AuthPassword" options for VG? or vise versa?
Why is this options limited to VG1-4? can these options not be used for VG5-8?

obi-support2:
Firmware Release 1.2.1(2283) has been posted. One enhancement includes is the
addition of options to support NAT traversal for SIP Gateway and URL calls
on SP1/2: You can now append the following URL parameters to each speed dial and
SIP Gateway VG1-8 access number, separated by ';',
   - ui=userid[:password]  
         user-info, password is optional
   - op=[ i ][ m ][ n ][ s ]
         option flags, i=ice, m=symmetric-rtp,
         n=use-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.
   If stun disabled in the main SP, then stun client is not enabled,
   and may lead to crash when doing URL dialing and stun specified.

Navigation

[0] Message Index

[#] Next page

[*] Previous page