Overview
The figure below shows a typical network topology where the Cisco Unified Border Element (CUBE) is configured to route messages between a call manager system (such as the Cisco Unified Call Manager) and a Next Generation Network (NGN).
Devices that connect to an NGN must comply with the User-Network Interface (UNI) specification. The CUBE supports the NGN UNI specification and can be configured to interconnect NGN with other call manager systems, such us the Cisco Unified Call Manager.
The CUBE supports the following:
-
the use of P-Preferred Identity (PPID), P-Asserted Identity (PAID), Privacy, P-Called Party Identity (PCPID), in INVITE messages
-
the translation of PAID headers to PPID headers and vice versa
-
the translation of RPID headers to PAID or PPID headers and vice versa
-
the configuration and/or pass through of privacy header values
-
the use of the PCPID header to route INVITE messages
-
the use of multiple PAURI headers in the response messages (200 OK) it receives to REGISTER messages
P-Preferred Identity and P-Asserted Identity Headers
NGN servers use the PPID header to identify the preferred number that the caller wants to use. The PPID is part of INVITE messages sent to the NGN. When the NGN receives the PPID, it authorizes the value, generates a PAID based on the preferred number, and inserts it into the outgoing INVITE message towards the called party.
However, some call manager systems, such as Cisco Unified Call Manager 5.0, use the Remote-Party Identity (RPID) value to send calling party information. Therefore, the Cisco Unified Border Element must support building the PPID value for an outgoing INVITE message to the NGN, using the RPID value or the From: value received in the incoming INVITE message. Similarly, CUBE supports building the RPID and/or From: header values for an outgoing INVITE message to the call manager, using the PAID value received in the incoming INVITE message from the NGN.
In non-NGN systems, the CUBE can be configured to translate between PPID and PAID values, and between From: or RPID values and PAID/PPID values, at global and dial-peer levels.
In configurations where all relevant servers support the PPID or PAID headers, the Cisco Unified Border Element can be configured to transparently pass the header.
 Note |
If the NGN sets the From: value to anonymous, the PAID is the only value that identifies the caller. |
The table below describes the types of INVITE message header translations supported by the Cisco Unified Border Element. It also includes information on the configuration commands to use to configure P-header translations.
The table below shows the P-header translation configuration settings only. In addition to configuring these settings, you must configure other system settings (such as the session protocol).
|
Incoming Header |
Outgoing Header |
Configuration Notes |
||
|---|---|---|---|---|
|
From: |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id This is the default system behavior.
|
||
|
PPID |
PAID |
To enable the translation to PAID privacy headers in the outgoing header at a global level, use the asserted-id pai command in voice service VoIP SIP configuration mode. For example: Router(conf-serv-sip)# asserted-id pai To enable the translation to PAID privacy headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id pai command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id pai |
||
|
PPID |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id This is the default system behavior. |
||
|
PAID |
PPID |
To enable the translation to PPID privacy headers in the outgoing header at a global level, use the asserted-id ppi command in voice service VoIP SIP configuration mode. For example: Router(conf-serv-sip)# asserted-id ppi To enable the translation to PPID privacy headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id ppi command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id ppi |
||
|
PAID |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id This is the default system behavior. |
||
|
RPID |
PPID |
To enable the translation to PPID privacy headers in the outgoing header at a global level, use the asserted-id ppi command in voice service VoIP SIP configuration mode. For example: Router(conf-serv-sip)# asserted-id ppi To enable the translation to PPID privacy headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id ppi command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id ppi |
||
|
RPID |
PAID |
To enable the translation to PAID privacy headers in the outgoing header at a global level, use the asserted-id pai command in voice service VoIP SIP configuration mode. For example: Router(conf-serv-sip)# asserted-id pai To enable the translation to PAID privacy headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id pai command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id pai |
||
|
RPID |
From: |
By default, the translation to RPID headers is enabled and the system translates PPID headers in incoming messages to RPID headers in the outgoing messages. To disable the default behavior and enable the translation from PPID to From: headers, use the no remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# no remote-party-id |
Note |
Privacy functions are not initialized on Unified Border Element without configuring asserted-id pai or asserted-id ppi . Ensure that you configure asserted-id pai or asserted-id ppi to support privacy functions on Unified Border Element. Just configuring asserted-id pai in dial-peer or global configuration mode is sufficient to process both PPID and PAID headers. |
The CUBE can be configured to transparently pass the PAID and PPID headers in the incoming and outgoing Session Initiation Protocol (SIP) requests or response messages from end-to-end.
-
Requests include: INVITEs and UPDATEs
-
Responses include:18x and 200OK
Note |
The priority of P-headers are in the following order: PAID, PPID, and RPID. |
|
Incoming Header |
Outgoing Header |
Configuration Notes |
||
|---|---|---|---|---|
|
PAID |
PPID |
To enable the translation to PPID headers in the outgoing header at a global level, use the asserted-id ppi command in voice service VoIP SIP configuration mode. For example: Router(conf-serv-sip)# asserted-id ppi To enable the translation to PPID headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id ppi command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id ppi |
||
|
RPID |
PPID |
To enable the translation to PPID headers in the outgoing header at a global level, use the asserted-id ppi command in voice service VoIP SIP configuration mode. For example: Router(conf-serv-sip)# asserted-id ppi To enable the translation to PPID headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id ppi command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id ppi |
||
|
PPID |
PPID |
To enable the translation to PPID headers in the outgoing header at a global level, use the asserted-id ppi command in voice service VoIP SIP configuration mode. To enable the translation to PPID headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id ppi command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id ppi |
||
|
PAID |
PAID |
To enable the translation to PAID headers in the outgoing header at a global level, use the asserted-id pai command in voice service VoIP SIP configuration mode. To enable the translation to PAID headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id pai command in dial peer voice configuration mode. For example: Router(config-dial-peer)# voice-class sip asserted-id pai |
||
|
RPID |
PAID |
To enable the translation to PAID headers in the outgoing header at a global level, use the asserted-id pai command in voice service VoIP SIP configuration mode. To enable the translation to PAID headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id pai command in dial peer voice configuration mode. |
||
|
PPID |
PAID |
To enable the translation to PAID headers in the outgoing header at a global level, use the asserted-id pai command in voice service VoIP SIP configuration mode. To enable the translation to PAID headers in the outgoing header on a specific dial peer, use the voice-class sip asserted-id pai command in dial peer voice configuration mode. |
||
|
PAID |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id .
|
||
|
RPID |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id .
|
||
|
PPID |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id |
||
|
FROM |
FROM |
No configuration required except for the remote-party-id header. | ||
|
FROM |
RPID |
To enable the translation to RPID headers in the outgoing header, use the remote-party-id command in SIP user-agent configuration mode. For example: Router(config-sip-ua)# remote-party-id |
||
|
PAID |
PAID |
Enables PPID headers on the incoming dial-peer and PAID headers on the outgoing dial-peer. |
||
|
RPID |
PAID |
Enables PPID headers on incoming dial-peer and PAID headers on outgoing dial-peer. |
||
|
PPID |
PAID |
Enables PPID headers on incoming dial-peer and PAID headers on outgoing dial-peer. |
||
|
PAID |
PAID |
Enables RPID headers on incoming dial-peer and PAID headers on outgoing dial-peer. |
||
|
RPID |
PAID |
Enables RPID headers on incoming dial-peer and PAID headers on outgoing dial-peer. |
||
|
PPID |
PAID |
Enables RPID headers on incoming dial-peer and PAID headers on outgoing dial-peer. |
||
|
PAID |
PPID |
Enables PAID headers on incoming dial-peer and PPID headers on outgoing dial-peer. |
||
|
RPID |
PPID |
Enables PAID headers on incoming dial-peer and PPID headers on outgoing dial-peer. |
||
|
PPID |
PPID |
Enables PAID headers on incoming dial-peer and PPID on outgoing dial-peer. |
||
|
PAID |
PPID |
Enables RPID headers on incoming dial-peer and PPID headers on outgoing dial-peer. |
||
|
RPID |
PPID |
Enables RPID headers on incoming dial-peer and PPID headers on outgoing dial-peer. |
||
|
PPID |
PPID |
Enables RPID headers on incoming dial-peer and PPID headers on outgoing dial-peer. |
||
|
PAID |
RPID |
Enables PPID headers on incoming dial-peer and RPID headers on outgoing dial-peer.
|
||
|
RPID |
RPID |
Enables PPID headers on incoming dial-peer and RPID headers on outgoing dial-peer. |
||
|
PPID |
RPID |
Enables PPID headers on incoming dial-peer and RPID headers on outgoing dial-peer.
|
||
|
PAID |
RPID |
Enables PAID headers on incoming dial-peer and RPID headers on outgoing dial-peer.
|
||
|
RPID |
RPID |
Enables PAID headers on incoming dial-peer and RPID headers on outgoing dial-peer. |
||
|
PPID |
RPID |
Enables PAID headers on incoming dial-peer and RPID headers on outgoing dial-peer.
|
Privacy
If the user is subscribed to a privacy service, the Cisco Unified Border Element can support privacy using one of the following methods:
-
Using prefixes
The NGN dial plan can specify prefixes to enable privacy settings. For example, the dial plan may specify that if the caller dials a prefix of 184, the calling number is not sent to the called party.
The dial plan may also specify that the caller can choose to send the calling number to the called party by dialing a prefix of 186. Here, the Cisco Unified Border Element transparently passes the prefix as part of the called number in the INVITE message.
The actual prefixes for the network are specified in the dial plan for the NGN, and can vary from one NGN to another.
-
Using the Privacy header
If the Privacy header is set to None, the calling number is delivered to the called party. If the Privacy header is set to a Privacy:id value, the calling number is not delivered to the called party.
-
Using Privacy values from the peer call leg
If the incoming INVITE has a Privacy header or a RPID with privacy on, the outgoing INVITE can be set to Privacy: id. This behavior is enabled by configuring privacy pstn command globally or voice-class sip privacy pstn command on the selected dial-per.
Incoming INVITE can have multiple privacy header values, id, user, session, and so on. Configure the privacy-policy passthru command globally or voice-class sip privacy-policy passthru command to transparently pass across these multiple privacy header values.
Some NGN servers require a Privacy header to be sent even though privacy is not required. In this case the Privacy header must be set to none. The Cisco Unified Border Element can add a privacy header with the value None while forwarding the outgoing INVITE to NGN. Configure the privacy-policy send-always globally or voice-class sip privacy-policy send-always command in dial-peer to enable this behavior.
If the user is not subscribed to a privacy service, the Cisco Unified Border Element can be configured with no Privacy settings.
Note |
For the Privacy functions to work as intended, the command asserted-id {pai|ppi} must be configured. |
P-Called Party Identity
The Cisco Unified Border Element can be configured to use the PCPID header in an incoming INVITE message to route the call, and to use the PCPID value to set the To: value of outgoing INVITE messages.
The PCPID header is part of the INVITE messages sent by the NGN, and is used by Third Generation Partnership Project (3GPP) networks. The Cisco Unified Border Element uses the PCPID from incoming INVITE messages (from the NGN) to route calls to the Cisco Unified Call Manager.
Note |
The PCPID header supports the use of E.164 numbers only. |
P-Associated URI
The Cisco Unified Border Element supports the use of PAURI headers sent as part of the registration process. After the Cisco Unified Border Element sends REGISTER messages using the configured E.164 number, it receives a 200 OK message with one or more PAURIs. The number in the first PAURI (if present) must match the contract number. The Cisco Unified Border Element supports a maximum of six PAURIs for each registration.
Note |
The Cisco Unified Border Element performs the validation process only when a PAURI is present in the 200 OK response. |
The registration validation process works as follows:
-
The Cisco Unified Border Element receives a REGISTER response message that includes PAURI headers that include the contract number and up to five secondary numbers.
-
The Cisco Unified Border Element validates the contract number against the E.164 number that it is registering:
-
If the values match, the Cisco Unified Border Element completes the registration process and stores the PAURI value. This allows administration tools to view or retrieve the PAURI if needed.
-
If the values do not match, the Cisco Unified Border Element unregisters and then reregisters the contract number. The Cisco Unified Border Element performs this step until the values match.
-
Random Contact Support
The Cisco Unified Border Element can use random-contact information in REGISTER and INVITE messages so that user information is not revealed in the contact header.
To provide random contact support, the Cisco Unified Border Element performs SIP registration based on the random-contact value. The Cisco Unified Border Element then populates outgoing INVITE requests with the random-contact value and validates the association between the called number and the random value in the Request-URI of the incoming INVITE. The Cisco Unified Border Element routes calls based on the PCPID, instead of the Request-URI which contains the random value used in contact header of the REGISTER message.
The default contact header in REGISTER messages is the calling number. The Cisco Unified Border Element can generate a string of 32 random alphanumeric characters to replace the calling number in the REGISTER contact header. A different random character string is generated for each pilot or contract number being registered. All subsequent registration requests will use the same random character string.
The Cisco Unified Border Element uses the random character string in the contact header for INVITE messages that it forwards to the NGN. The NGN sends INVITE messages to the Cisco Unified Border Element with random-contact information in the Request URI. For example: INVITE sip:FefhH3zIHe9i8ImcGjDD1PEc5XfFy51G@10.12.1.46:5060.
The Cisco Unified Border Element will not use the To: value of the incoming INVITE message to route the call because it might not identify the correct user agent if supplementary services are invoked. Therefore, the Cisco Unified Border Element must use the PCPID to route the call to the Cisco Unified Call Manager. You can configure routing based on the PCPID at global and dial-peer levels.
Feature Information
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
PAID and PPID Headers in mid-call re-INVITE and UPDATE request and responses on Cisco Unified Border Element |
Baseline Fuctionality |
This feature enables CUBE platforms to support:
|
Feedback