Re: [OpenSIPStack] SIP Trunk how to route

[Joegen E. B. <joe...@gm...>]

sales@ER wrote:
> Hi
>
> Is there a doc for SIP Trunk?  When and why to use it and relationship to
> B2Bua etc...?
>
> Warren Kreckler
>
>
>   

Unfortunately not.   SIP Trunking is very new in the arsenal and  would 
be hard to use without a more advanced configuration module.   For now, 
there is a temporary provision to test it using the config pages via 
XML.  I have attached the annoucement i've sent last October 17, 2007

To tell OpenSBC that the call should be processed by the SIP Trunk your B2BUARoute entry shouold include a sip-trunk paramameter.

Example:  
[sip:1212*] sip:mytrunkprovider.com <http://mytrunkprovider.com>;sip-trunk=true 



-------

Hi,

SIP Trunking is not prime time yet but you may already try it using the 
latest CVS copy of OpenSBC/OpenSIPStack.  To Enable Trunking, you must 
provide an XML configuration in "SIP Trunk Config".  Below is a template 
XML config.   In this sample config, sip:win32.opensipstack.org is 
assumed to be the internal domain of OpenSBC while 
sip:opteron.opensipstack.org is the domain of your SIP Provider.  


[SIPTrunk]
* trunk-name:  This is the unique name OpenSBC will use to identify you 
SIP Trunk
* route-set:  This is the DNS resolvable domain or IP address of your 
trunk provider
* sip-domain:  This is the SIP Domain used as the host part of the To 
and From URIs
* expires:  Global expire interval for trunk registrations in seconds

[Trunk-Accounts]
* account - An instance of a virtual UA that will register to the Trunk 
Provider domain
** user-name - The user part of the From-URI
** auth-user-name - User name used for Authorization and Authentication
** auth-password - Password used for Authorization and Authentication
** inbound-route - URI specifying the identity of the UA in the internal 
domain
** expires - If set, this will be the expires used when the virtual UA 
registers to the Trunk Provider

[Transient-Accounts] - Transient accounts are similar to normal 
Trunk-Account in terms of the parameters.  The only difference is that 
they are also meant to be shared (in round robin fashion) by calls which 
are not defined in the normal trunk-accounts.  This is normally used if 
you have a few accounts with a Trunk Provider and is meant to be shared 
by all your external users.



------------------------START OF XML 
CONFIG----------------------------------

<root>
   <siptrunk trunk-name="opteron.opensipstack.org"
             route-set="opteron.opensipstack.org"
             sip-domain="opteron.opensipstack.org"
             expires="10">

      <trunk-accounts>
         <account user-name="1001"
                  auth-user-name="1001"
                  auth-password="1001"
                  inbound-route="sip:90...@wi..."
                  expires="3600" />
         <account user-name="1002"
                  auth-user-name="1002"
                  auth-password="1002"
                  inbound-route="sip:90...@wi..."
                  expires="3600" />
         <account user-name="1003"
                  auth-user-name="1003"
                  auth-password="1003"
                  inbound-route="sip:90...@wi..."
                  expires="3600" />
      </trunk-accounts>

      <transient-accounts>
         <account user-name="1001"
                  auth-user-name="1001"
                  auth-password="1001"
                  inbound-route="sip:90...@wi..." />
         <account user-name="1002"
                  auth-user-name="1002"
                  auth-password="1002"
                  inbound-route="sip:90...@wi..." />
         <account user-name="1003"
                  auth-user-name="1003"
                  auth-password="1003"
                  inbound-route="sip:90...@wi..." />
      </transient-accounts>

   </siptrunk>
</root>

Joegen