SIP-I/SIP-T
From TBwiki
(Difference between revisions)
m (Removed * ''SIP to SIP-I interworking'' in "not supported" section) |
|||
| Line 1: | Line 1: | ||
| − | Session Initiation Protocol with encapsulated ISUP, which is known as SIP-I | + | 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> | <br><br> | ||
Revision as of 10:10, 29 October 2012
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.
Contents |
Supported SIP-I Specification
TelcoBridges supports the Profile C (SIP-I) of ITU Q.1912.5.
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
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.
- Go to NAP->Edit->SIP-I Params->Check "Enable".
- Save and activate your configuration.
External Sources
- ITU Q.1912.5 Interworking between SIP and BICC/ISUP
