The Enhanced Generic Number Handling feature enables the Cisco PGW 2200 Softswitch to pass the Generic Number parameter present in a UK ISUP IAM message into the user field of the P-Asserted-ID header in a SIP INVITE message when the Number Qualifier field in the Generic Number is set to “intra-nw-use” (254 in the signaling). This feature introduces a new property called GenNumInclude. The GenNumInclude property enables or disables the feature as follows:
When set to 1, the system maps the Generic Number in an IAM to the user field of the P-ASSERTED-ID Header in a SIP INVITE.
When set to 0, the system does not map the Generic Number to the user field of the P-ASSERTED-ID Header in a SIP INVITE.
Note This feature is restricted to deployments in which the ISUP side is provisioned for the United Kingdom variant (ISUPV3_UK).
The Cisco PGW 2200 Softswitch performs this message conversion when it determines that it must set up a call between an ISUP network on the originating side and a SIP network on the destination side.
The Cisco PGW 2200 Softswitch must be running Release 9.8(1) S10P10. Prerequisites for this release are documented in the Release Notes for the Cisco Media Gateway Controller Software Release 9.8(1) at:
Provisioning Properties to Support Enhanced Generic Number Handling
The following sample MML command sequence provisions the Enhanced Generic Number Handling feature. When provisioned, the Cisco PGW 2200 Softswitch passes a Generic Number received in an IAM to the username of a P-Asserted-ID in a SIP INVITE.
Table 1 describes one existing property that you must provision for this feature and a new property introduced for this feature.
Table 1 Properties
Indicates the mapping from ISUP CLI to the outgoing SIP message. Maps the calling party number to the P-Asserted ID in the privacy header value ID. If an additional calling party number is contained in the Generic Number field, the Cisco PGW 2200 Softswitch maps it to the SIP From header.
Valid values: Integer (0–4)
0—Map the CLI to the SIP From header.
1—Map the CLI to Remote-Party-ID header, in addition to the SIP From header.
2—Map the CLI to Remote-Party-ID header, in addition to the SIP From header only when the CLI presentation is allowed.
3—Map the CLI to P-Asserted-ID header, in addition to the SIP From header.
Note Set this property to 3 to enable the Enhanced Generic Number Handling feature.
4—Map the CLI to P-Asserted-ID header, in addition to the SIP From header, only when the CLI presentation is allowed.
Dynamically reconfigurable: yes.
This property was added in software Release 9.8(1).
Provisioning example to support the Enhanced Generic Number Handling feature:
Note This property is specifically designed for ISUP-SIP call interworking and may not be perfectly applicable for some SIP-SIP rare case scenarios. For eg: If there is A number modification by DialPlan and after that 302 redirect occurs, in that case it might not show the modified A number and displays the original A number, if mapclitosipheader has value other than 0. So for non-interworking call (SIP-SIP), recommended value for mapclitosipheader is "0".
Enables or disables the mapping of the Generic Number to the user field of a P-ASSERTED-ID Header in a SIP INVITE.
1—Map the Generic Number in IAM to the user field of the P-ASSERTED-ID in a SIP INVITE. (Generic Number Handling Enabled)
0—Do not map the Generic Number to the user field of the P-ASSERTED-ID in a SIP INVITE. (Generic Number Handling Disabled)
Note To enable the Generic Number Handling feature, provision the mapclitosipheader property to the value 3.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at:
ISDN (Integrated Services Digital Network) User Part
Session Initiation Protocol
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.