View source

Session Initiation Protocol with encapsulated ISUP, which is known as SIP-I. It specifies a set of capability for interworking ISUP networks with SIP networks.  SIP-I is an extension to existing SIP protocol to carry ISUP specific messages information on a SIP network.
<br><br>

== Supported SIP-I Specification  ==
TelcoBridges supports the Profile C (SIP-I) of [http://www.itu.int/itudoc/itu-t/aap/sg11aap/history/q1912.5/index.html ITU Q.1912.5].
<br><br>
''The following items are not supported:''
* ''Precondition (RFC3312)''
* ''Reception of INVITE without SDP''
* ''SIP-I digit overlap''
* ''SUS/RES ISUP message to SIP INFO message''
* ''SIP to SIP-I interworking''
<br><br>

== TelcoBridges and SIP-I ==
SIP-I support starts from release 2.6.23. Please refer to
[http://docs.telcobridges.com/mediawiki/index.php/TMG-CONTROL_Version_2.6 TMG-CONTROL version 2.6]
<br><br>

== How do you enable SIP-I support  ==
* SIP-I is enabled in a per-NAP basis. The SIP MIME body will be taken care of for both incoming or outgoing NAPs once it is enabled. 
* Go to NAP->Edit->SIP-I Params->Check "Enable". 
* Save and activate your configuration.
<br>
[[Image:SIP-I_config.jpg|800px ]]
<br><br>

== External Sources ==
* [http://www.itu.int/itudoc/itu-t/aap/sg11aap/history/q1912.5/index.html ITU Q.1912.5] ''Interworking between SIP and BICC/ISUP''
<br><br>