SIP-I/SIP-T
Candy Chan (Talk | contribs) (→TelcoBridges and SIP-I) |
Candy Chan (Talk | contribs) (→Supported SIP-I RFCs) |
||
| Line 2: | Line 2: | ||
| − | === Supported SIP-I | + | === Supported SIP-I Specification === |
| − | TelcoBridges supports the following | + | TelcoBridges supports the following specification for SIP-I: |
{| 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 03:23, 29 February 2012
Session Initiation Protocol – ISUP, which is known as SIP-I, is a session control protocol, which is used to create, modify and terminate IP based communications such as voice and multimedia services. SIP-I is an extension to existing SIP protocol with encapsulated ISUP messages to transport narrowband signalling over SIP based networks.
Supported SIP-I Specification
TelcoBridges supports the following specification for SIP-I:
| 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.
