SIP-I/SIP-T: Difference between revisions
Candy Chan (talk | contribs) No edit summary |
Candy Chan (talk | contribs) No edit summary |
||
| Line 8: | Line 8: | ||
== TelcoBridges and SIP-I == | == TelcoBridges and SIP-I == | ||
SIP-I support starts from release 2.6.23. Please refer to | 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] | |||
Revision as of 00:08, 6 July 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 the Profile C (SIP-I) of 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 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.
