SIP-I/SIP-T
From TBwiki
(Difference between revisions)
(add Profile C) |
|||
Line 4: | Line 4: | ||
=== Supported SIP-I Specification === | === Supported SIP-I Specification === | ||
− | TelcoBridges supports | + | TelcoBridges supports SIP-I as described from Profile C of the following specification: |
{| border="1" | {| border="1" | ||
Line 10: | Line 10: | ||
| [http://www.itu.int/itudoc/itu-t/aap/sg11aap/history/q1912.5/index.html ITU Q.1912.5] Interworking between SIP and BICC/ISUP | | [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 == | == TelcoBridges and SIP-I == |
Revision as of 22:55, 10 May 2012
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.
Supported SIP-I Specification
TelcoBridges supports SIP-I as described from Profile C of the following specification:
ITU Q.1912.5 Interworking between SIP and BICC/ISUP |
TelcoBridges and SIP-I
SIP-I support starts from release 2.6.23. Please refer to the TMG-CONTROL version history. TMG-CONTROL version 2.6
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.