Dialogic IMG - IMG 1010 - SIP From: Header Tags (10.3.3 - 10.5.1)

Table of Contents

Description:

Use this pane to configure how the IMG interworks the Originating Line Information and Calling Party Category Parameter. The Originating Line Information Parameter can be interworked from SIP to ISUP and ISUP to SIP. The Calling Party Category Parameter is interworked from ISUP to SIP only. See information below which explains more on what is supported in this object in ClientView.

Accessing this Pane:

Dialogic IMG EMS -> Profiles -> SIP Profile -> SIP From Header Tags

Open

Maximum Objects:  

1 SIP From: Header Tag object per SIP SGP object

Related Topics:

IMG 1010 - ISUP Originating Line Info Support - ANSI

IMG 1010 - Calling Party Category

ClientView Pane:

Open

Field Descriptions:

ISUP Originating Line Information: (ANSI only)

Disable (Default)- The isup-oli value received in the Originating Line Information Parameter from either the SIP 'From:' Header or ISUP 'IAM' message is not passed between the two protocols.

Enable- The isup-oli value received in the Originating Line Information Parameter from either the SIP 'From:' Header or the ISUP 'IAM' message will be passed between the two protocols.

ISUP Calling Party Category:

If the IMG receives a Calling Party Category Parameter, it can be configured to insert the Calling Party Category Parameter in the SIP From: Header as either a User Part or URI Parameter. Below are examples of each.

Disable (Default)- If IMG receives a Calling Party Category Parameter on the inbound TDM leg, the Calling Party Parameter is not interworked from the inbound to the outbound leg of the call.

CPC Placed at User Part Support - If IMG receives a Calling Party Category Parameter on the inbound TDM leg, the Calling Party Category will be interworked into the User Part of the From: Header. See Example 1 below:

CPC Placed at URI Parameter Support- If IMG receives a Calling Party Category Parameter on the inbound TDM leg, the Calling Party Category will be interworked into the URI Part of the From: Header. See Example 2 below

Unmapped Values:

The option is available to either not pass any unmapped values or to pass the CPC parameter value. In order to pass the value, either 'CPC Placed as User Part -or- CPC Placed as URI Parameter' must be set in the Calling Party Category Parameter.

Ignore (Default) - Any Calling Party Category values received on inbound leg will not be passed to the From: Header on the outbound leg.

Pass Value - Any Calling Party Category values received on inbound leg will be passed as its decimal value equivalent on the outbound leg. Where the value is inserted in the From: Header depends on how the ISUP Calling Party Parameter above  is configured.

Example: The received Calling Party Parameter in ISUP IAM has a Spare Value of 0x0e. The CPC field is set to 'CPC Placed as URI Parameter' and the Unmapped CPC Value is set to Pass Value. The IMG will pass the spare value as a decimal number. See portion of call trace below.

Mapping Received CPC category to CPC from IAM to CPC in SIP message: