IMG 1010 - SIP T Entity
- Kelli Higdon
SIP-T/SIP-I protocol is a mechanism to allow traditional ISUP information originating in the PSTN to be encapsulated into a SIP message sent across a SIP network to a PSTN at the far end. The encapsulated information in the SIP messaging is then translated back into ISUP to be used on the far end PSTN. Two PSTN's are on either side of a SIP network and must communicate with each other using the same ISUP protocol. The SIP-T Entity object is configured on the IMG so the ISUP information coming from a stack on the IMG, is transmitted over SIP-T/SIP-I using the variant name the user selects within the  SIP Variant field of the SIP-T Entity . In essence, the SIP-T Entity pane is used to customize the name of an ISUP variant in an ISUP MIME body sent by the IMG when SIP-T/SIP-I is enabled.
The ISUP information that is transmitted over SIP-T/SIP-I is the ISUP information coming from the stack selected in the SS7 Stack field of the SIP Entity object. The difference is when the ISUP information is transmitted using SIP-T/SIP-I, only the name variable in the SIP-T/SIP-I messaging will change to what is configured in the SIP Variant field of the SIP-T Entity object.
For example:
An SS7 stack on the IMG is configured so any ISUP information is formatted using ANSI-92 standard. The IMG is communicating with a far end PSTN which is configured to transmit/receive ANSI-97 standard. Between the IMG and the PSTN is a SIP network and all ISUP information is transmitted using SIP-T/SIP-I. In order for the IMG to be able to communicate with the PSTN, it must send all ISUP information over SIP using ANSI-97 standard. The SIP-T Entity object allows the IMG to be able to take the ISUP information coming from the SS7 stack and transmit it out SIP-T/SIP-I using the ANSI-92 standard but the name variable sent will display ANSI 97. Because the name variable is ANSI-97, the far end will not reject the call.
Accessing this Pane:
Dialogic IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> SIP Signaling -> SIP T Entity
Maximum Objects:
4 per SIP Signaling object
Related Topics:
IMG 1010 - Overview and Configuration of SIP-T and SIP-I
Note: You must have SIP T Enabled in the SIP Signaling pane to access the SIP T Entity pane. See IMG 1010 - Overview and Configuration of SIP-T and SIP-I
ClientView Pane:
Field Descriptions:
SS7 Stack:
The SS7 Stack field has a drop down menu with a list of all the SS7 stacks configured. Select from drop down menu the SS7 stack that the variant will be assigned to. If there are no SS7 Stacks assigned, then there will be no stacks displayed in the drop down menu.
SIP Variant:
In the SIP Variant field will be a drop down list of all the Variants created. Select a variant from the SIP Variant Drop Down menu. The menu will consist of all the custom SIP-T/SIP-I variants created under the New Signaling Variants object. If Base Only is selected then the name variable in the SIP-T/SIP-I messaging will be what is configured in the stack selected in the SS7 Stack field above. If a separate configured variant is selected from the SIP Variant field then the name variable sent in the SIP-T messaging will be from the selected Variant. All information will be sent in the ISUP MIME body.