SIP Signaling - SIP-T Entity

Owned by Kelli Higdon
Last updated: Apr 03, 2024
3 min read

 

 

SIP-T protocol is a mechanism to allow traditional ISUP information originating in the PSTN to be encapsulated into a SIP message and 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. The SIP-T Entity object is configured on the IMG 2020 so the ISUP information coming from a stack on the IMG 2020, is transmitted using SIP-T protocol. 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 2020.

The ISUP information that is transmitted over the SIP-T network 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, only the name variable in the SIP-T 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 2020 is configured so any ISUP information is formatted using ANSI-92. The IMG 2020 is communicating with a far end PSTN which is configured to transmit/receive ANSI-97 standard. Between the IMG 2020 and the PSTN is a SIP network and all ISUP information is transmitted using SIP-T. In order for the IMG 2020 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 2020 to be able to take the ISUP information coming from the SS7 stack and transmit it out SIP-T 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.

Web GUI Page

Dialogic > IMG 2020 > Signaling > SIP Signaling > SIP T Entity

Maximum SIP-T Entity objects per SIP Signaling

Up to four SIP-T Entity objects can be created per SIP Signaling object. One SIP Entity object can be created for each SS7 stack created.

Related Topics and Dependencies

The SIP-T Entity object is dependent on other objects being configured. Below is a list of dependencies

  • The SIP-T Entity object needs to be associated with an SS7 stack. Therefore, an SS7 stack must be configured before creating the SIP-T Entity

  • To enable access to the SIP-T Entity object, the SIP-T Enabled field within the SIP Signaling object must be set to Yes. Once this is set, the SIP-T Entity object is selectable by right clicking on the SIP Signaling object.

  • A SIP-T Variant must be configured under the Signaling Variants object. (Variant Type in signaling variant object must be SIP-T)

Configure SIP to SIP-T Interworking

SIP to SIPT Overview

IMG 1010 - Signaling Variant

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-T Variant: (Default: Base Only)

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 variants created under the New SignalingVariants object. If Base Only is selected then the name variable in the SIP-T 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.

Return to Documentation Home I Return to Sangoma Support