Actions

SIP-I/SIP-T: Difference between revisions

(Reformat.)
(Added link to 3.2 configuration)
 
(17 intermediate revisions by 7 users not shown)
Line 1: Line 1:
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.
Session Initiation Protocol with encapsulated ISUP, which is known as SIP-I, specifies the criteria for enabling ISUP networks to work with SIP networks.  SIP-I is an extension to an existing SIP protocol and transports ISUP specific messages over a SIP network.
<br><br>


=== Supported SIP-I Specification  ===
== 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)''
* ''SIP-I digit overlap''
* ''SUS/RES ISUP message to SIP INFO message''
<br><br>


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] ''Interworking between SIP and BICC/ISUP''
== TelcoBridges and SIP-I ==
ISUP variant supported :
*ANSI-88
*ANSI-92
*ANSI-95
*TELCORDIA
*ITU
*ITU97
*SINGAPORE
*Q767
*NTT
*CHINA
*ETSI
*ETSIV3
*UK
*SPIROU


SIP-I support starts from release 2.6.23. Please refer to
[[TMG-CONTROL_Version_2.6|TMG-CONTROL version 2.6]]
<br><br>


=== TelcoBridges and SIP-I ===
== Configuration  ==
* SIP-I is enabled on a per-[[NAP]] basis.
*[[Enabling_SIP_I_SIP_T_D|Tmedia v3.2: SIP Advanced Features]]
*[[Toolpack:Protocol_Stack_Settings_D#SIP Advanced Features|Tmedia v3.0: SIP Advanced Features]]
<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
*[[Toolpack:Protocol_Stack_Settings_C#SIP Advanced Features|Tmedia v2.10: SIP Advanced Features]]
*[[Toolpack:Protocol_Stack_Settings_B#SIP Advanced Features|Tmedia v2.9: SIP Advanced Features]]
*[[Toolpack:Protocol_Stack_Settings_A#SIP Advanced Features|Tmedia v2.8: SIP Advanced Features]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advanced Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advanced Features]]
</div>


SIP-I support starts from release 2.6.23. Please refer to the TMG-CONTROL version history. [http://docs.telcobridges.com/mediawiki/index.php/TMG-CONTROL_Version_2.6 TMG-CONTROL version 2.6]
== 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>
=== 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. You can go to NAP->SIP NAP->Edit->SIP-I Params->Check "Enable". Save and activate your configuration to apply new changes.
 
 
[[Image:SIP-I_config.jpg|800px ]]

Latest revision as of 09:05, 9 May 2022

Session Initiation Protocol with encapsulated ISUP, which is known as SIP-I, specifies the criteria for enabling ISUP networks to work with SIP networks. SIP-I is an extension to an existing SIP protocol and transports ISUP specific messages over a SIP network.

Supported SIP-I Specification

TelcoBridges supports the Profile C (SIP-I) of ITU Q.1912.5.

The following items are not supported:

  • Precondition (RFC3312)
  • SIP-I digit overlap
  • SUS/RES ISUP message to SIP INFO message



TelcoBridges and SIP-I

ISUP variant supported :

  • ANSI-88
  • ANSI-92
  • ANSI-95
  • TELCORDIA
  • ITU
  • ITU97
  • SINGAPORE
  • Q767
  • NTT
  • CHINA
  • ETSI
  • ETSIV3
  • UK
  • SPIROU

SIP-I support starts from release 2.6.23. Please refer to TMG-CONTROL version 2.6

Configuration

External Sources