IMG 1010 - Overview of SIP to SIP-T or SIP-I

 

 

The information below pertains to Interworking between SIP and SIP-T/SIP-I protocols. Use the information below to get an overview of how this functionality operates on the IMG. For configuration information, see the following links:

IMG 1010 - Configure Interworking between SIP and SIP-T or SIP-I

IMG 1010 - SIP to SIP-T Interworking

An SS7_Base license is required when utilizing the SIP to SIP-T/SIP-I interworking functionality.

Diagram of SIP to SIP-T/SIP-I Interworking:

In the diagram below the IMG 1010/1004 is configured to receive an incoming SIP message on Channel Group A. The message is inter-worked in the IMG and SIP-T/SIP-I messaging is transmitted out Channel Group B. The SIP Endpoint Requiring SIP-T/SIP-I receives the SIP-T/SIP-I messages and processes them. After processing the messages, the SIP Endpoint Requiring SIP-T/SIP-I then sends responses back to the IMG through Channel Group B. The responses are inter-worked in the IMG and transmitted out Channel Group A as SIP messaging. Each individual Channel group must be configured with a SIP Profile (SGP) which has SIP-T enabled. See Call Flow diagram below.

 

The implementation within the IMG for the SIP-T protocol is similar to SIP-I and any information in this documentation refers to both SIP-T and SIP-I.

Call Flow Diagram:

Use diagram above when reading Call Flow Diagram

SIP to SIP-T/SIP-I Message Mapping:

Below is a mapping of SIP to SIP-T messages. The ISUP messages are inserted into the SIP message as a RAW API message.

SIP Message

SIP-T/I Message

INVITE

INVITE (IAM)

180 Ringing

180 Ringing (ACM/CPG)

183 Progress

183 Progress (ACM/CPG)

200 OK

200 OK (ANM/CON)

BYE

BYE (REL)

200 OK BYE

200 OK BYE (RLC)

4xx, 5xx, 6xx

4xx, 5xx, 6xx (REL)

 

Return to Documentation Home I Return to Sangoma Support