Page tree
Skip to end of metadata
Go to start of metadata

SIP ISUP CPC (Calling Party Category) Mapping

The CPC (Calling Party Category) parameter is included in either the From: Header or the P-Asserted Identity Header. The fields From: Header and P-Asserted Identity Header were added to the SIP ISUP CPC Mapping object in ClientView. Before software 10.5.1 ER1 only the From: Header could map the CPC parameters between SIP and ISUP and this was accomplished under the 'SIP From Header Tags' object. See information below on how to configure and map the CPC parameter.

Accessing this Pane

Dialogic IMG EMS -> Profiles -> SIP Profile -> SIP ISUP CPC Mapping

Maximum Objects 

1 SIP ISUP CPC Mapping per object per SIP SGP Profile object

Preceding Pane

IMG 1010 - SIP Profile - 10.5.3

IMG 1010 - Calling Party Category

ClientView Pane

Field Descriptions

Support Field

Disable (default)- The Calling Party Category parameter is not interworked between SIP and ISUP. When Support field is set to Disabled the Location field as displayed in screen capture above defaults to Not Used.

From Header- When the value of the From: Header is selected, the Calling Party Category parameters will be interworked from ISUP to SIP and/or SIP to ISUP in the From: Header. The location of the cpc parameter in the From Header will now have the following choices:

  • CPC Placed at the User Part Support
  • CPC Placed at the URI Parameter Support.


P-Asserted Identity- When the value of the P-Asserted Identity Header is selected then the cpc parameters will be passed from ISUP to SIP and from SIP to ISUP in the P-Asserted Identity Header. The location of the cpc parameter in the From Header will now have the following choices:

  • CPC Placed at the User Part Support 
  • CPC Placed at the URI Parameter Support.

Location

CPC Placed at the User Part Support- Where in the From: Header or P-Asserted Identity Header the cpc parameter will be placed. See Example 1 below which displays how cpc parameter will be displayed if 'CPC Placed at User Part Support' is selected.

Example 1

From:unavailable<sip:unavailable;cpc=operator@10.129.39.59>;tag=95ffcd055e0f78f7d5d397020e89288d78a1

 

CPC Placed at the URI Parameter Support- Where in the From: Header or P-Asserted Identity Header the cpc parameter will be placed. See Example 2 below which displays how cpc parameter will be displayed if 'CPC Placed at URI Parameter Support' is selected.

Example 2

From:unavailable<sip:unavailable@10.129.39.59;cpc=operator>;tag=95ffcd055e0f78f7d5d397020e89288d78a1

 

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

Received calling party’s category From: IAM

CPC sent out in a SIP message

Operator, language French (1)

operator

Operator, language English (2)

operator

Operator, language German (3)

operator

Operator, language Russian (4)

operator

Operator, language Spanish (5)

operator

Ordinary calling subscriber (10)

ordinary

Calling subscriber with priority (11)

priority

Data call (voice band data) (12)

data

Test call (13)

test

Payphone (15)

payphone

Unmapped Values

The option is available to either not pass any CPC 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.

Before software 10.5.3 SP9 the Unmapped Values were interworked from SS7 to SIP only. As of software 10.5.3 SP9 the unmapped values will now be interworked from SIP to SS7 as well. For example if the IMG Gateway received a cpc=180 (unknown) in the SIP INVITE message the IMG Gateway would have ignored it and set the CPC=2 in the outbound SS7 message. Now after the feature implementation, the IMG Gateway will modify the CPC parameter on the outbound SS7 message and set it to 180.

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

Pass Value- Any Calling Party Category values received on inbound leg will be passed as its decimal value equivalent to the outbound leg.

 

Example (Unmapped Value): 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.

(CPC Unmapped Value as User Part)

From:unavailable<sip:unavailable@10.129.39.59;cpc=14>;tag=95ffcd055e0f78f7d5d397020e89288d78a1

 

Example: (Emergency case):

The following example is for ANSI. It might be different in other countries and ISUP variants.

SS7 to SIP call- When received ISUP cpc ="Emergency Service Call (0xe0)" -or- cpc="High Priority emergency service call (0xe1)", IMG will include Priority header (w/ value "emergency") and Resource-Priority header (w/ value "ets.0") in the out SIP INVITE.

SIP to SS7 call- When received INVITE contains Resource-Priority header (w/ value "ets.0") or Priority header (w/ value "emergency"), it will be mapped to ISUP Calling Party’s Category = "emergency Service Call (0xe0)"

  • No labels