SIP Profile - ISUP CPC Mapping
The CPC (Calling Party Category) Parameter will be included in either the From: or the P-Asserted Identity Header. The fields From: Header and P-Asserted Identity Header were added to the SIP ISUP CPC Mapping object. Refer to the information below on how to configure and map the CPC parameter.
Web GUI Page
Dialogic > Profiles > SIP Profile (SGP) > New SIP ISUP CPC Mapping
Maximum Objects
One SIP ISUP CPC Mapping object per SIP SGP object
Related Topics and Dependencies
To add each of the headers above select enable or disable. See links below.
Field Descriptions
Support
Disable (default) - The Calling Party Category parameter is not inter-worked between SIP and ISUP. When the Support field is set to Disabled the Location field as displayed in screen capture above defaults to Not Used.
From Header - When the support field value is set to From Header, the Calling Party Category parameters will be inter-worked from ISUP to SIP and/or SIP to ISUP. This will be displayed 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
-or-
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/or from SIP to ISUP. This will be displayed 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
-or-
CPC Placed at the URI Parameter Support.
Location
CPC Placed at User Part Support - This parameter dictates 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 URI Parameter Support - This parameter dictates 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 of Received CPC category 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 unmapped values or to pass the CPC parameter value. In order to pass the value, either CPC Placed at the User Part -or- CPC Placed at the 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 (Unmapped Value)
The received Calling Party Parameter in ISUP IAM has a Spare Value of 0x0e. The CPC field is set to CPC Placed at the URI Parameter and the Unmapped CPC Value is set to Pass Value. The IMG 2020 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
SS7 to SIP call - When received ISUP cpc=Emergency Service Call (0xe0) -or- cpc=High Priority emergency service call, the IMG 2020 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).