SIP Remote Party ID and P-Asserted Support
Document Release History
Publication Date
Comments
July 23, 2009
Updated document to add Figure 1 and Figure 2.
September 20, 2007
Updated version of the document for Release 9.7(3).
June 18, 2007
Updated version of the document for Release 9.7(3).
April 19, 2007
Updated version of the document.
October 6, 2006
Initial version of the document.
Feature History
Release
Modification
9.5(2)
This feature was introduced on the Cisco MGC.
9.7(3)
A new value 4 was added for property InhibitSipFromMapping on the
Cisco MGC.
This document describes the SIP Remote Party ID and P-Asserted Support feature.
This feature is described in the following sections:
•
Feature Overview, page 2
•
Supported Platforms, page 3
•
Supported Standards, MIBs, and RFCs, page 3
•
Prerequisites for Using This Feature, page 3
•
Provisioning Tasks, page 3
•
Provisioning Examples, page 8
•
Reference Information, page 10
•
Obtaining Documentation and Technical Assistance, page 25
•
Glossary, page 25
Cisco MGC Software Release 9.5(2)
1
SIP Remote Party ID and P-Asserted Support
Feature Overview
Feature Overview
This feature provides support on the Cisco MGC of the ISDN User Part (ISUP)-to-Session Initiation
Protocol (SIP) mapping of calling line identity (CLI) to the SIP Remote Party ID header or the
P-Asserted ID header. It also updates the generic handling of the SIP-to-ISUP and ISUP-to-SIP mapping
of CLI, generic number (GN), and redirecting number (RN).
Note
In this document, the term CLI, calling party number, and CgPN are used to refer to the directory number
that is dialed to terminate a call to a phone.
This feature provides the following:
•
Support for the ISUP-to-SIP mapping of CLI to the From header, SIP Remote Party ID, or
P-Asserted ID.
•
An update of the generic handling of the SIP-to-ISUP and ISUP-to-SIP mapping of calling line
identity.
•
An update of ITU ISUPs generic number (containing the additional calling number), and redirecting
number.
Benefits
This feature provides the benefits described in the following paragraphs.
Comprehensive Mapping to All the Defined Containers for Calling Party Number(s)
The calling party number was stored in the SIP From header.in the initial SIP RFC 2543. Later Remote
Party ID was added, and finally P-Asserted was added. This feature allows use of any of the possible
headers where the calling number can be stored.
ISUP-to-SIP Mapping
Although ISUP-to-SIP is the primary focus, mapping also works for calls from Q.931, QSIG, DPNSS,
and H.323 to SIP. The MGC 2200 supports mapping the CLI into the SIP From header, and optionally
into the SIP Remote Party ID leader or the P-Asserted-ID on an outgoing SIP trunk group basis.
Related Documents
This document contains information that is related strictly to this feature. The documents that contain
additional information related to the Cisco MGC are listed below:
•
Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2)
•
Cisco Media Gateway Controller Hardware Installation Guide
•
Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller
•
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
•
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
•
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
•
Cisco Media Gateway Controller Software Release 9 MML Command Reference
•
Cisco Media Gateway Controller Software Release 9 Messages Reference Guide
Cisco MGC Software Release 9.5(2)
2
SIP Remote Party ID and P-Asserted Support
Supported Platforms
•
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
•
Cisco Media Gateway Controller Software Release 9 Management Information Base Guide
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Cisco Media
Gateway Controller Hardware Installation Guide.
Supported Standards, MIBs, and RFCs
No new or modified standards or MIBs are supported by this feature.
New RFCs
RFC 3325 supports the P-Asserted ID header.
The draft (draft-ietf-sip-privacy-04.txt) supports Remote party ID.
The draft (draft-levy-sip-diversion-08.txt) supports the Diversion header.
ITU-T Q.1912.5 Interworking of CLI to P-assert-id
Prerequisites for Using This Feature
You must have Cisco MGC software Release 9.5(2), Patch S39 P32. Prerequisites for this release can be
found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2). Information
on the prerequisites for the implementation of this feature in Cisco IOS software for the Cisco media gateways
can be found in this feature module.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Provisioning Procedures, page 3
Provisioning Procedures
This section covers the following provisioning topics:
•
Provisioning Basics, page 4
•
Modifying Mapping Properties, page 7
Cisco MGC Software Release 9.5(2)
3
SIP Remote Party ID and P-Asserted Support
Provisioning Tasks
Provisioning Basics
Use the procedures in this section to start a provisioning session, save, and activate the changes you have
made.
•
Starting a Provisioning Session, page 4
•
Saving and Activating Your Provisioning Changes, page 5
•
Ending a Provisioning Session Without Activating Your Changes, page 5
•
Retrieving Provisioning Data, page 6
For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You might need to start a provisioning session as part of your system operations. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver=”curr_ver”,dstver=”mod_ver”
Where:
•
curr_ver—The name of the current configuration version. In place of the name of the current
configuration version, you can also enter:
– new—A new default session configuration; no existing source configuration is available.
– active—Selects the active configuration as the source for configuration changes.
Note
•
If you do not know the name of your current configuration session, you can use the procedure
described in the Retrieving Data on the Current Provisioning Session, page 7.
mod_ver—A new configuration version name that contains your provisioning changes.
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you
would enter the following command:
prov-sta::srcver=“ver1”,dstver=“ver2”
Note
The InhibitSipFromMapping, MapCLItoSipHeader, and MapRNtoSipHeader properties could not be
provisioned from an old configuration version before software Release 9.5(2) Patch S039 P032. For
example, if ver1 was a previous configuration generated before the new properties were introduced, you
could not provision the new properties by the MML command prov-sta::srcver=“ver1”,dstver=“ver2”.
Once a provisioning session is underway, you may use the prov-add, prov-ed, or prov-dlt MML
commands to add, modify, and delete components on your system. This document describes how to
provision this feature. For more information on provisioning other components on your Cisco MGC,
refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes,
as described in the “Saving and Activating Your Provisioning Changes” section on page 5, or ending
your provisioning session without saving and activating your changes, as described in the “Ending a
Provisioning Session Without Activating Your Changes” section on page 5.
Cisco MGC Software Release 9.5(2)
4
SIP Remote Party ID and P-Asserted Support
Provisioning Tasks
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to
save and activate your changes. There are two different provisioning MML commands that do this:
prov-cpy and prov-dply.
Caution
Using the prov-cpy or prov-dply MML command can severely impact your system’s call processing
performance, depending on the extent of your provisioning changes. We recommend that these
commands be issued during a maintenance window when traffic is minimal.
Use the prov-cpy MML command to save and activate your changes on simplex Cisco MGC
(single-host) systems.
Note
When you enter the prov-cpy command, your provisioning session is automatically ended. If you want
to make additional provisioning changes, you must start a new provisioning session as described in the
“Starting a Provisioning Session” section on page 4.
Caution
Do not use the prov-cpy command to save and activate your changes on a continuous-service
Cisco MGC system (one with active and standby hosts). Saving and activating with prov-cpy on such a
system would require use of the prov-sync MML command to synchronize the provisioning data on the
active and standby hosts. The system does not indicate when the synchronization process fails, which
would create problems when a switchover operation occurs.
Use the prov-dply MML command to save and activate your changes on the active and standby
Cisco MGCs in a continuous-service system. Do not use his command on a Cisco MGC in a simplex
configuration.
Note
When you enter the prov-dply command, your provisioning session is automatically ended, unless an
error occurs during execution. If you want to make additional provisioning changes, you must start a new
provisioning session, as described in the “Starting a Provisioning Session” section on page 4.
Ending a Provisioning Session Without Activating Your Changes
If you want to end a provisioning session without saving and activating the changes you have entered,
enter the prov-stp MML command. This command ends your current provisioning session and your
changes are not entered.
Cisco MGC Software Release 9.5(2)
5
SIP Remote Party ID and P-Asserted Support
Provisioning Tasks
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning
settings. The ways you can use this command to retrieve provisioning data are described in the following
sections:
•
Retrieving Data for an Individual Component, page 6
•
Retrieving Data for All Components, page 6
•
Retrieving Data for All Components of a Particular Type, page 6
•
Retrieving Data on the Current Provisioning Session, page 7
•
Retrieving Data on Supported Signaling Protocols, page 7
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component in your system. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:name=MML_name
Where:
•
component—The MML component type associated with the desired component. You can find a
complete list of MML component types in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
•
MML_name—The MML name for the desired component. You can determine the MML names for
the various components using the prov-rtrv:all MML command.
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you would enter
the following command:
prov-rtrv:ss7path:name="ss7svc1"
The response to the retrieve command depends on the component type associated with the desired
component. For example, to view the properties for an SUA routing key called suakey1, you would enter
the following command:
prov-rtrv:suakey:name="suakey1"
Retrieving Data for All Components
You can retrieve data on all of the components provisioned on your system. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:all
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log
in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:“all”
Where component is the MML component type associated with the desired component group. You can
find a complete list of MML component types in the Cisco Media Gateway Controller Software
Release 9 Provisioning Guide.
Cisco MGC Software Release 9.5(2)
6
SIP Remote Party ID and P-Asserted Support
Provisioning Tasks
For example, to view the provisioning data for all SS7 signaling services, you would enter the following
command:
prov-rtrv:ss7path:"all"
Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:session
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2005-01-13 13:39:19
M RTRV
"session=jtest:session"
/*
Session ID = mml1
SRCVER = active
DSTVER = jtest
*/
Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:variants
Modifying Mapping Properties
The following sections contain the procedures for modifying the various sigPath properties in your
Cisco MGC provisioning data:
•
Modifying MapCLItoSipHeader, page 7
•
Modifying MapRNMethod, page 8
•
Modifying InhibitSipFromMapping, page 8
Modifying MapCLItoSipHeader
To modify the ISUP CLI mapping to the outgoing SIP message, perform the following steps:
Step 1
Start a provisioning session, as described in the “Starting a Provisioning Session” section on page 4.
Step 2
Enter the following command to change the way the CLI mapping works for ISUP, PRI, DPNSS, Q.931,
SIP, QSIG, or H.323 to the outgoing SIP message:
mml> prov-ed:sigsvcprop:name="sip-path",MapCLItoSipHeader="1"
Where:
Step 3
•
name—MML name of the SIP path for which ISUP CLI-to-SIP header mapping is enabled.
•
MapCLItoSipHeader—1 maps the CLI to the Remote party ID, if the generic number (additional
calling number) is present, map to the From header.
Repeat the above steps for each SIP path you want to modify in your provisioning data.
Cisco MGC Software Release 9.5(2)
7
SIP Remote Party ID and P-Asserted Support
Provisioning Examples
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating Your Provisioning Changes” section on page 5.
Modifying MapRNMethod
To modify the EISUP or ISUP RN mapping to the outgoing SIP message or to the EISUP RN, perform
the following steps:
Step 1
Start a provisioning session, as described in the “Starting a Provisioning Session” section on page 4.
Step 2
Enter the following command to change the way the RN mapping works for EISUP, ISUP, or PRI, when
mapping to the outgoing SIP message:
mml> prov-ed:sigsvcprop:name="sip-path",MapRNMethod="1"
Where:
•
name—MML name of the SIP path for which EISUP or ISUP RN-to-SIP header mapping is enabled.
Step 3
Repeat the above steps for each SIP path you want to modify in your provisioning data.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating Your Provisioning Changes” section on page 5.
Modifying InhibitSipFromMapping
To modify the PGW to inhibit the SIP From header from mapping, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 4.
Step 2
Enter the following command to inhibit the SIP From header mapping to ISUP or other protocol:
mml> prov-ed:sigsvcprop:name="sip-path",InhibitSipFromMapping="0"
Where:
•
name—MML name of the SIP path for which the SIP From header in the SIP-to-ISUP CLI mapping
is enabled.
Step 3
Repeat the above steps for each SIP path you want to modify in your provisioning data.
Step 4
If there are no other components that you need to provision, end your provisioning session as described
in the “Saving and Activating Your Provisioning Changes” section on page 5.
Provisioning Examples
This section provides a provisioning scenarios for this feature. Additional provisioning examples for the
Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
The following provisioning scenarios present different ISUP-to-SIP mapping scenarios:
Cisco MGC Software Release 9.5(2)
8
SIP Remote Party ID and P-Asserted Support
Provisioning Examples
Provisioning Scenario 1
In Scenario 1 the calling party number maps to the SIP From header and ignores the ACgPN if it is
presented in the ISUP message. If Presentation in the calling party number is restricted, the calling party
number maps to the SIP From header as “Anonymous <sip:[email protected]>”.
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="0"
Note
The default value of mapclitosipheader is 0. If this property is not modified, or you are
provisioning from “new”, this command is not needed.
mml> prov-add:PROFILE:NAME="sippro",TYPE="grprofile",cgpninclude="0"
mml> prov-add:TRNKGRPPROF:name="5600",grprofile="sippro"
Note
5600 is the name of the IP outgoing trunk.
Scenario 2
In Scenario 2, the calling party number maps to the SIP From header and ignores the ACgPN if it is
presented in the ISUP message. If Presentation in the calling party number is restricted, map the calling
party number to the SIP From header as “Anonymous <sip:CGPN@PGW_HOST>”.
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="0"
Note
The default value of mapclitosipheader is 0. If this property is not modified, or you are
provisioning from “new”, this command is not needed.
mml> prov-add:PROFILE:NAME="sippro",TYPE="grprofile",cgpninclude="1"
The default value of cgpninclude is 1.
mml> prov-add:TRNKGRPPROF:name="5600",grprofile="sippro"
Note
5600 is the name of the SIP outgoing trunk.
Scenario 3
In Scenario 3, the calling party number maps to the SIP From header and the P-Asserted ID header. If
ACgPN is presented and Presentation is allowed, overwrite the SIP From header with the ACgPN. If
Presentation is restricted in ACgPN, overwrite the SIP From header as “Anonymous
<sip:[email protected]>”. If Presentation is NA in ACgPN, do not overwrite the SIP
From header.
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="3"
mml> prov-add:PROFILE:NAME="sippro",TYPE="grprofile",cgpninclude="0"
mml> prov-add:TRNKGRPPROF:name="5600",grprofile="sippro"
Note
5600 is the name of the SIP outgoing trunk.
Cisco MGC Software Release 9.5(2)
9
SIP Remote Party ID and P-Asserted Support
Reference Information
Scenario 4
In Scenario 4, the calling party number maps to the SIP From header and the Remote Party ID header.
If ACgPN is presented and Presentation is allowed, overwrite the SIP From header with the ACgPN. If
Presentation is restricted in ACgPN, overwrite the SIP From header as “Anonymous
<sip:[email protected]>”. If Presentation is NA in ACgPN, do not overwrite the SIP
From header.
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="1"
mml> prov-add:PROFILE:NAME="sippro",TYPE="grprofile",cgpninclude="0"
mml> prov-add:TRNKGRPPROF:name="5600",grprofile="sippro"
Note
5600 is the name of the SIP outgoing trunk.
Reference Information
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
Properties, page 10
•
CLI Mapping from ISUP to SIP, page 14
•
Mapping EISUP or ISUP RN to SIP Diversion Header, page 18
•
Mapping from SIP to ITU ISUP, page 19
•
Mapping from SIP to ITU ISUP, page 23
Properties
The properties in this section are used for this feature. For information on other properties for the Cisco
MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
The parent objects for the properties involved in this feature are found in Table 1, and the property’s
dynamically provisionable status, which means the property can be modified without requiring a system
restart, is listed in Table 2.
Table 1
Software Properties Related to this Feature
Table 1:
InhibitSipFromMapping
X
MapCLItoSipHeader
X
Cisco MGC Software Release 9.5(2)
10
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SIP
SGCP
SESSION
RLM
MGCP
ISDNPRI
IOCC
EISUP
DPNSS
Property Name
AVM
Parent Object
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 1:
MapRNMethod
X
Table 2
X
Provisionable Properties
Property
Modified Value Takes Effect Without Restart
InhibitSipFromMapping
Yes
MapCLItoSipHeader
Yes
MapRNMethod
Yes
The properties used for this feature are described in Table 3.
Cisco MGC Software Release 9.5(2)
11
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SIP
SGCP
SESSION
RLM
MGCP
ISDNPRI
IOCC
EISUP
Property Name
DPNSS
AVM
Parent Object
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 3
Properties Added for This Feature Module
Property
Definition
MapCLItoSipHeader
Determines the mappings from the ISUP calling party number to the outgoing
SIP message. Valid range: 0 through 4.
Valid Values: 0—The calling party number is put in the outgoing SIP From
header if number presentation is allowed. If the calling party number
presentation is restricted, then the SIP outgoing From header is also
controlled by the cgpnInclude property.
•
If cgpnInclude = 0, and the SIP network is untrusted, the From header has
SIP URI as: Anonymous <sip:[email protected]>
•
If cgpnInclude = 1, and the SIP network is trusted, and honors the
anonymous setting by not passing the CLI to the SIP end point, the From
header has URI as Anonymous <sip:CGPN@PGW_HOST>
1—The calling party number is mapped to the remote party ID, with screen
and privacy values. If an additional calling party number is present in the
generic number, it is mapped to the SIP From header.
2—Map the calling party number to the Remote-Party-ID header only when
the calling party number presentation is allowed. For handling the additional
calling party number in the generic number, the operation is the same as for
a value of 1.
3—The calling party number is mapped to the P-Asserted ID, with privacy
header value ID, if necessary. If an additional calling party number is present
in the generic number, it is mapped to the SIP From header.
Note
If the calling party number presentation is allowed, there is no privacy
header. If the calling party number presentation is restricted, there is
a privacy header with a value ID.
4—Map the calling party number to the P-Asserted ID header only when the
calling party number presentation is allowed. For handling the additional
calling party number in the generic number, the operation is the same as for
a value of 3.
Default Value: 0
Cisco MGC Software Release 9.5(2)
12
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 3
Properties Added for This Feature Module (continued)
Property
Definition
MapRNMethod
Determines the mappings between the EISUP or ISUP RN and the SIP
message headers or EISUP RN. Valid range: 0 through 2.
Valid Values:
0—Do not map the RN to the SIP header. Do not mapthe RN to the EISUP
RN parameter.
1—Map the RN to the Diversion header. Map the RN tothe EISUP RN
parameter.
2—Map the RN to the Diversion header only when RN presentation is
allowed. Map the RN to the EISUP RN parameter only when the RN
presentation is allowed.
Default Value: 1
InhibitSipFromMapping
Determines the mapping from the incoming SIP message to the ISUP CLI. If
the remote party ID or P-Asserted-ID header is present and the
InhibitSipFromMapping property = 1, then disable mapping the SIP From
header to the generic number.
If the remote party ID or P-Asserted-ID header is not present and the
InhibitSipFromMapping property = 1, then disable mapping the SIP From
header to the calling party number. Valid range: 0 through 4.
Valid Values:
0—If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN,
map the E164 number in username in From header to GN (additional CgPN).
If the PAID/RPID E164 number is not present, map the E164 number in
username in From header to CgPN.
1— Ignore the From header, map PAID/RPID E164 number to CgPN.
2—Ignore the PAID/RPID, map the E164 number in username in From
header to CgPN.
3—If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN,
map the E164 number in Display name in From header to GN (additional
CgPN). If the PAID/RPID E164 number is not present, map the E164 number
in username in From header to ISUP CgPN, and map the E164 number in
displayname in From header to GN (additional CgPN)
4—If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN,
map the E164 number in username in From header to GN (additional CgPN).
If the PAID/RPID E164 number is not present, ignore the From header.
Note
The 4 value is only available in Release 9.7(3).
Default Value: 0
Cisco MGC Software Release 9.5(2)
13
SIP Remote Party ID and P-Asserted Support
Reference Information
CLI Mapping from ISUP to SIP
The SIP Remote Party ID and P-Asserted Support feature supports mapping the CLI into the SIP From
header, and optionally supports mapping into the SIP Remote Party ID header or the P-Asserted ID for
calls from ISUP. Table 4 shows the CLI mapping from ISUP to SIP and Table 5 shows the mapping from
ITU ISUP to SIP.
Table 4
CLI Mapping from ISUP to SIP
ISUP
From
Remote Party ID
P-Asserted ID
CLI (CPRI = P SI = NP)
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
No GN-ACgPN)
Screen = yes
CLI (CPRI = R SI = NP)
No GN-ACgPN
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”.
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
Privacy: id
Privacy = full
CLI (CPRI=P SI=UPVP)
No GN-ACgPN
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
CLI (CPRI=R SI=UPVP)
No GN-ACgPN
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
Privacy: id
Privacy = full
Cisco MGC Software Release 9.5(2)
14
SIP Remote Party ID and P-Asserted Support
Reference Information
Figure 1 presents a flowchart that represents the mapping from ISUP to SIP.
Figure 1
Mapping ISUP to SIP
ISUP - SIP
CLI
R/P/NA
R
P
NA
Map FROM display-name to
“Anonymous” & addr-spec to
“[email protected]"
Map CLI Base on
MapCLItoSipHeader=0/1/2/3/4
GN
R/P/NA
R
Overwrite FROM display-name to
“Anonymous” & addr-spec to
“[email protected]"
MAP CLI to FROM
display-name and addr-spec
MAP CLI based on
MapCLItoSipHeader=0/1/2/3/4
Map FROM to
“unavailable@
hostportion”
P
NA
Overwrite FROM displayname and addr-specwith GN
RN
R/P/NA
P
R
Add header based on
MapRNMethod=0/1/2
252649
Add header based on
MapRNMethod=0/1/2
END
Cisco MGC Software Release 9.5(2)
15
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 5
CLI Mapping from ITU ISUP to SIP
ISUP
From
Remote Party ID
P-Asserted ID
CLI (CPRI = P SI = NP)
GN digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
GN (CPRI = P SI = UPNS)
Screen = yes
CLI (CPRI = R SI = NP)
GN (CPRI = P SI = UPNS)
GN digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
Privacy: id
Privacy = full
CLI (CPRI = R SI = NP)
GN (CPRI = R SI = UPNS)
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
Privacy: id
Privacy = full
CLI (CPRI = P SI = NP)
GN (CPRI = R SI = UPNS)
CLI (CPRI = P SI = NP)
GN (CPRI = P SI = UPVP)
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”
CLI digits mapped to
display-name and
address-spec
GN digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
CLI digits mapped to
display-name and
address-spec
Screen = yes
CLI (CPRI = R SI = NP)
GN (CPRI = P SI = UPVP)
GN digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
Privacy: id
Privacy = full
CLI (CPRI = R SI = NP)
GN (CPRI = R SI = UPVP)
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”
CLI digits mapped to
display-name and
address-spec
CLI digits mapped to
display-name and
address-spec
Screen = yes
Privacy: id
Privacy = full
CLI (CPRI = P SI = NP)
GN (CPRI = R SI = UPVP)
No CLI
GN (CPRI = P SI = UPNS)
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous.
invalid”
CLI digits mapped to
display-name and
address-spec
GN digits mapped to
display-name and
address-spec
—
Cisco MGC Software Release 9.5(2)
16
CLI digits mapped to
display-name and
address-spec
Screen = yes
—
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 5
CLI Mapping from ITU ISUP to SIP (continued)
ISUP
From
Remote Party ID
P-Asserted ID
No CLI
GN digits mapped to
display-name and
address-spec
—
—
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”
—
—
Display-name mapped to
“Anonymous” and
address-spec to
“anonymous@anonymous
.invalid”
—
—
unavailable@hostportion
—
—
GN (CPRI = P SI = UPNS)
No CLI
GN (CPRI = R SI = UPVP)
No CLI
GN (CPRI = R SI = UPVP)
No CLI
No GN
Cisco MGC Software Release 9.5(2)
17
SIP Remote Party ID and P-Asserted Support
Reference Information
Mapping EISUP or ISUP RN to SIP Diversion Header
Refer to Table 6 for EISUP or ISUP RN to the SIP Diversion header when the MapRNMethod property
value is set to 1.
Table 6
EISUP or ISUP RN-to-SIP Diversion Header Mapping
ISUP
Diversion
no RDN, RI, OCN
No Diversion
RDN = 404(CPRI = P), OCN = 404(CPRI = P) Diversion: <sip:404@PGW>;
RI(RR = UB, OR = UB, RC = 1)
Reason = “user-busy”; Privacy = off; counter = 1
RDN = 404(CPRI = P), OCN = 404(CPRI = P) Diversion: <sip:404@PGW>;
RI(RR = NA, OR = NA, RC = 1)
Reason = “no-answer”; Privacy = off; counter = 1
RDN = 404(CPRI = P), OCN = 404(CPRI = P) Diversion: <sip:404@PGW>;
RI(RR = UNC, OR = UNC, RC = 1)
Reason = “unconditional”; Privacy = off; counter = 1
RDN = 404(CPRI = P), OCN = 404(CPRI = P) Diversion: <sip:404@PGW>;
RI(RR = DEF, OR = DEF, RC = 1)
Reason = “deflection”; Privacy = off; counter = 1
RDN = 404(CPRI = P), OCN = 404(CPRI = P) Diversion: <sip:404@PGW>; Reason = “unknown”;
RI(RR = UNA, OR = UNA, RC = 1)
Privacy = off; counter = 1
RDN = 404(CPRI = R), OCN = 404(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = NA, OR = NA, RC = 1)
Reason = “no-answer”; Privacy = full; counter = 1
RDN = 404(CPRI = R), OCN = 404(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = 09, OR = 09, RC = 1)
Reason = “unknown”; Privacy = full; counter = 1
RDN = 404(CPRI = R), OCN = 404(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = UNC, OR = UNC, RC = 1)
Reason = “unconditional”; Privacy = full; counter = 1
RDN = 404(CPRI = R), OCN = 404(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = DEF, OR = DEF, RC = 1)
Reason = “deflection”; Privacy = full; counter = 1
RDN = 404(CPRI = R), OCN = 404(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = UNA, OR = UNA, RC = 1)
Reason = “unknown”; Privacy = full; counter = 1
RDN(CPRI = NA), OCN(CPRI = NA) RI(RR =
UB, OR = UB, RC = 1)
—
RDN(CPRI = NA), OCN(CPRI = NA) RI(RR =
NA, OR = NA, RC = 1)
—
RDN(CPRI = NA), OCN(CPRI = NA) RI(RR =
UNC, OR = UNC, RC = 1)
—
RDN(CPRI = NA), OCN(CPRI = NA) RI(RR =
UNA, OR = UNA, RC = 1)
—
RDN = 404(CPRI = P), OCN = 308(CPRI = P) Diversion: <sip:404@PGW>;
RI(RR = UB, OR = NA, RC = 5)
Reason = “user-busy”; Privacy = off; counter = 4
Diversion: <sip:308@PGW>;
Reason = “no-answer”; Privacy = off; counter = 1
RDN(CPRI = R), OCN = 308(CPRI = P) RI(RR Diversion: <sip:404@PGW>;
= NA, OR = UB, RC = 2)
Reason = “no answer”; Privacy = full; counter = 1
Diversion: <sip:308@PGW>;
Reason = “user busy”; Privacy = off; counter = 1
Cisco MGC Software Release 9.5(2)
18
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 6
EISUP or ISUP RN-to-SIP Diversion Header Mapping (continued)
ISUP
Diversion
RDN = 404(CPRI = P), OCN = 308(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = UB, OR = UB, RC = 5)
Reason = “user-busy”; Privacy = off; counter = 4
Diversion: <sip:308@PGW>;
Reason = “user-busy”; Privacy = full; counter = 1
RDN = 404(CPRI = R), OCN = 308(CPRI = R) Diversion: <sip:404@PGW>;
RI(RR = UNC, OR = UNA, RC = 5)
Reason = “unconditional”; Privacy = full; counter = 4
Diversion: <sip:308@PGW>;
Reason = “unknown”; Privacy = full; counter = 1
RDN = 404(CPRI = P), OCN(CPRI = NA)
RI(RR = UB, OR = UNC, RC = 5)
Diversion: <sip:404@PGW>;
Reason = “user-busy”; Privacy = off; counter = 5
RDN(CPRI = NA), OCN = 308(CPRI = P)
RI(RR = UNC, OR = UB, RC = 2)
Diversion: <sip:308@PGW>;
Reason = “user-busy”; Privacy = off; counter = 1
RDN = 404(CPRI = R), OCN(CPRI = NA)
RI(RR = UNA, OR = NA, RC = 2)
Diversion: <sip:404@PGW>;
Reason = “unknown”; Privacy = full; counter = 2
RDN(CPRI = NA), OCN = 308(CPRI = R)
RI(RR = NA, OR = NA, RC = 5)
Diversion: <sip:308@PGW>;
Reason = “no-answer”; Privacy = full; counter = 1
RDN(CPRI = NA), OCN(CPRI = NA)
RI(RR = UNC, OR = UNC, RC = 5)
—
RDN = 404(CPRI = P), no OCN
RI(RR = UB, RC = 5)
Diversion: <sip:404@PGW>;
Reason = “user-busy”; Privacy = off; counter = 5
No RDN, OCN = 308(CPRI = R) RI(RR = UB, Diversion: <sip:308@PGW>;
OR = UB, RC = 5)
Reason = “user-busy”; Privacy = full; counter = 1
Mapping from SIP to ITU ISUP
For mapping information from a SIP-to-ITU ISUP call to the MGC, which is sent out on another
protocol, refer to Table 7. Even though this mapping functionality exists on the PGW, the SIP Remote
Party ID and P-Asserted Support feature provides the ability to set the InhibitSipFromMapping flag per
sigPath. If a From header is received from the SIP trunk and the flag is set to 1, then no CLI information
is sent.
When the Diversion header is present, it is mapped to the Redirecting number. Redirection information
is included in the ISUP message with a default value.
Note
When a diversion header with a “counter=x” value greater than 5 is mapped to the ISUP redirecting
counter, the value is set to 5 (RC=5).
The GN presentation indicator is the same as the CgPN PI as specified in Q.1912.5.
The SI for GN is always set to be UPNV (user provided, not verified) as specified in Q.1912.5.
The privacy header supports “id” and “user”.
Cisco MGC Software Release 9.5(2)
19
SIP Remote Party ID and P-Asserted Support
Reference Information
Remote-Party-ID Mapping of Screening Indicator
If the rpi-token rpi = screen is included with the value of screen = no, then the CLI Screening indicator
is set to UPNV.
If the rpi-token rpi = screen is included with the value of screen = yes, then the CLI Screening indicator
is set to NP.
If the rpi-token rpi = screen is not included, then the CLI screening indicator can be set to UPNV.
Table 7
Mapping SIP From Header Information with P-Asserted ID to ITU ISUP
SIP
ITU ISUP
From (Inhibit SIP from Mapping)
P-Asserted-ID (Token)
Calling Line Identity
Generic Number
Unavailable@hostportion
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (0)
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (1)
Not included
No CLI digits
Not included
CPRI = NA
Present with digits (0)
Not included
CLI digits (from)
Not included
CPRI = P
SI = NP
Present with digits (1)
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (0)
Present with digits
CLI digits (P-assert)
Not included
CPRI = R
SI = NP
[email protected] (1)
Present with digits
CLI digits (P-assert)
Not included
CPRI = R
SI = NP
[email protected] (0)
Present with digits (id/user) CLI digits (P-assert)
Not included
CPRI = R
SI = NP
[email protected] (1)
Present with digits (id/user) CLI digits (P-assert)
Not included
CPRI = R
SI = NP
Present with digits (0)
Cisco MGC Software Release 9.5(2)
20
Present with digits
CLI digits (P-assert)
CLI digits (from)
CPRI = P
CPRI = P
SI = NP
SI = UPNV
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 7
Mapping SIP From Header Information with P-Asserted ID to ITU ISUP (continued)
SIP
ITU ISUP
From (Inhibit SIP from Mapping)
P-Asserted-ID (Token)
Present with digits (0)
Present with digits (id/user) CLI digits (P-assert)
Present with digits (1)
Present with digits
Calling Line Identity
Generic Number
CLI digits (from)
CPRI = R
CPRI = R
SI = NP
SI = UPNV
CLI digits (P-assert)
Not included
CPRI = P
SI = NP
Present with digits (1)
Present with digits (id/user) CLI digits (P-assert)
Not included
CPRI = R
SI = NP
Cisco MGC Software Release 9.5(2)
21
SIP Remote Party ID and P-Asserted Support
Reference Information
Figure 2 presents a flowchart that represents the mapping from SIP to ISUP.
Figure 2
Mapping SIP to ISUP
SIP->ISUP
Start
PAID: P-Asserted-ID
RPID: Remote-Party-ID
InhibitSipFromMapping=2?
N
Y
PAID/RPID E164?
Y
N
RPID
rpi-privacytag
Y
N
Y
PAID
N
Map RPID to
CLI with
Presentation
Restricted
PAID?
Map RPID to
CLI with
Presentation
Allowed
Y
Privacy
Token
N
Map PAID to
CLI with
Presentation
Restricted
Map PAID to
CLI with
Presentation
Allowed
InhibitSipFromMapping?
0
InhibitSipFromMapping?
3
0/4
Map FROM
Username to
GN
3
Map FROM
Username to
CGPN
Map FROM
Displayname
to GN
1/4
Map FROM
Displayname to
GN
END
Cisco MGC Software Release 9.5(2)
22
252650
1
Map FROM
Username to
CGPN
SIP Remote Party ID and P-Asserted Support
Reference Information
Mapping from SIP to ITU ISUP
Table 8 lists the mapping used by the PGW when mapping the SIP From header and remote party ID to
ITU ISUP.
Table 8
Mapping the SIP From Header and Remote Party ID to ITU ISUP
SIP
ITU ISUP
From
Remote Party ID
CLI
GN
unavailable@hostportion
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (0)
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (1)
Not included
No CLI digits
Not included
CPRI = NA
Present with digits (0)
Not included
CLI digits (from)
Not included
CPRI = P
SI = NP
Present with digits (1)
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (0)
[email protected] (0)
Present with digits
CLI digits (RPID)
Screen = yes
CPRI = R
Privacy = full
SI = NP
Present with digits
CLI digits (P-asserted)
Privacy = full
CPRI = R
Not included
Not included
SI = UPNV
[email protected] (0)
Present with digits
CLI digits (P-asserted)
Screen = yes
CPRI = R
Not included
SI = NP
[email protected] (0)
Present with digits
CLI digits (P-asserted)
Not included
CPRI = R
SI = UPNV
[email protected] (1)
[email protected] (1)
Present with digits
CLI digits (RPID)
Screen = yes
CPRI = R
Privacy = full
SI = NP
Present with digits
CLI digits (P-asserted)
Privacy = full
CPRI = R
Not included
Not included
SI = UPNV
Cisco MGC Software Release 9.5(2)
23
SIP Remote Party ID and P-Asserted Support
Reference Information
Table 8
Mapping the SIP From Header and Remote Party ID to ITU ISUP (continued)
SIP
ITU ISUP
From
Remote Party ID
CLI
GN
[email protected] (1)
Present with digits
CLI digits (P-asserted)
Not included
Screen = yes
CPRI = R
SI = NP
[email protected] (1)
Present with digits
CLI digits (P-asserted)
Not included
CPRI = R
SI = UPNV
FROM (InhibitSipFromMapping)
P-asserted-ID (token)
CLI
GN
“[email protected]” (4)
Not included
No CLI digits
Not included
CPRI = NA
[email protected] (4)
Present with digits
CLI digits (P-asserted)
(not included or “none”)
CPRI = R
Not included
SI = NP
“[email protected] (4)”
Present with digits
CLI digits (P-asserted)
(id, header, user)
CPRI = R
Not included
SI = NP
Present with digits (0)
Present with digits (0)
Present with digits (0)
Present with digits (0)
Present with digits (1)
Present with digits (1)
Present with digits
CLI digits (RPID)
CLI digits (from)
Screen = yes
CPRI = R
CPRI = R
Privacy = full
SI = NP
SI = UPNV
Present with digits
CLI digits (P-asserted)
CLI digits (from)
Privacy = full
CPRI = R
CPRI = R
SI = UPNV
SI = UPNV
Present with digits
CLI digits (P-asserted)
CLI digits (from)
Screen = yes
CPRI = P
CPRI = P
SI = NP
SI = UPNV
CLI digits (P-asserted)
CLI digits (from)
CPRI = P
CPRI = P
SI = UPNV
SI = UPNV
Present with digits
CLI digits (RPID)
Not included
Screen = yes
CPRI = R
Privacy = full
SI = NP
Present with digits
CLI digits (P-asserted)
Privacy = full
CPRI = R
Present with digits
SI = UPNV
Cisco MGC Software Release 9.5(2)
24
Not included
SIP Remote Party ID and P-Asserted Support
Obtaining Documentation and Technical Assistance
Table 8
Mapping the SIP From Header and Remote Party ID to ITU ISUP (continued)
SIP
ITU ISUP
From
Remote Party ID
CLI
GN
Present with digits (1)
Present with digits
CLI digits (P-asserted)
Not included
Screen = yes
CPRI = P
SI = NP
Present with digits (1)
Present with digits
CLI digits (P-asserted)
Not included
CPRI = P
SI = UPNV
Present with Digits (4)
Not included
No CLI Digits
Not included
CPRI = NA
Present with Digits (4)
Present with Digits (4)
Present with digits
CLI digits (P-asserted)
CLI digits (from)
(not included or “none”)
CPRI = P
CPRI = P
SI = NP
SI = UPNV
Present with digits
CLI digits (P-asserted)
CLI digits (from)
(id, header, user)
CPRI = R
CPRI = P
SI = NP
SI = UPNV
Obtaining Documentation and Technical Assistance
Cisco provides several ways to obtain documentation, technical assistance, and other technical
resources. To obtain this information, go to What’s New in Cisco Product Documentation at
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Glossary
Table 9 contains expansions of acronyms used in this feature module.
Table 9
Acronym Expansions
Acronym
Expansion
CLI
Calling Line Identity
CPRI
Calling Line Identity Address Presentation Restriction Indicator
GN
Generic Number (Additional Calling Party Number)
ISUP
ISDN User Part
MGC
Cisco Media Gateway Controller
NP
Network Provided
OCN
Original Called Number
PAID
P-Asserted ID
Cisco MGC Software Release 9.5(2)
25
SIP Remote Party ID and P-Asserted Support
Glossary
Table 9
Acronym Expansions (continued)
Acronym
Expansion
PGW
PSTN Gateway
RN
Redirecting Number
RPI
Release Protocol Indicator
RPID
Remote part ID
R/P/NA
Restricted/Presented/Not Available—settings of the Presentation Restriction
Indicator
SC
Signaling Controller
SI
Screening Indicator
SIP
Session Initiation Protocol
UPNV
User Provided, Not Verified
UPVP
User Provided, Verified and Passed
VSC
Virtual Switch Controller
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is
a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS,
iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers,
Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient,
and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (0711R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and
coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco MGC Software Release 9.5(2)
26