Actions

SIP-I/SIP-T: Difference between revisions

(Fixed typo)
Line 13: Line 13:


== TelcoBridges and SIP-I ==
== 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
SIP-I support starts from release 2.6.23. Please refer to
[[TMG-CONTROL_Version_2.6|TMG-CONTROL version 2.6]]
[[TMG-CONTROL_Version_2.6|TMG-CONTROL version 2.6]]

Revision as of 10:07, 12 November 2014

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)
  • Reception of INVITE without SDP
  • 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

  • SIP-I is enabled in a per-NAP basis.

Toolpack v2.6: SIP Advanced Features

External Sources