Table Of Contents
Configurable PSTN Cause Code to SIP Response Mapping
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Mapping PSTN Codes to SIP Status Codes
Mapping SIP Status Codes to PSTN Cause Codes
Verifying PSTN and SIP Code Mapping
Verifying PSTN Cause Code to SIP Status Code Mapping
Verifying SIP Cause Code to PSTN Status Code Mapping
Configurable PSTN Cause Code to SIP Response Mapping
Document Update Alert
This document was originally produced for Cisco IOS Release 12.2(11)T. This feature has been updated in subsequent releases, and more recent documentation is available.
If you are using Cisco IOS Release 12.2(11)T or higher, refer to the following section in the Configuring SIP Message Components, Session Timers, and Responses chapter of the Cisco IOS SIP Configuration Guide, Cisco IOS Voice Configuration Library, Release 12.3:
•
Configurable PSTN Cause Code to SIP Response Mapping
Feature History
This document describes Configurable PSTN Cause Code to SIP Response Mapping in Cisco IOS Release 12.2(11)T. This feature allows customization of the standard RFC 2543 mappings between the Session Initiation Protocol (SIP) and the Public Switched Telephone Network (PSTN) networks.
•
Supported Standards, MIBs, and RFCs
Feature Overview
For calls to be established between a SIP network and a PSTN network, the two networks must be able to interoperate. One aspect of their interoperation is the mapping of PSTN cause codes, which indicate reasons for PSTN call failure or completion, to SIP status codes or events. The opposite is also true: SIP status codes or events are mapped to PSTN cause codes. Event mapping tables found in this document show the standard or default mappings between SIP and PSTN.
However, you may want to customize the SIP user agent software to override the default mappings between the SIP and PSTN networks. The Configurable PSTN Cause Code to SIP Response Mapping feature allows you to configure specific map settings between the PSTN and SIP networks. Thus, any SIP status code can be mapped to any PSTN cause code, or vice versa.
When set, these settings can be stored in the NVRAM and are restored automatically on bootup.
Default Mappings
The following table lists PSTN cause codes and the corresponding SIP event mappings that are set by default. Any code other than the codes listed are mapped by default to 500 Internal server error.
The following table lists the SIP events and the corresponding PSTN cause codes mappings that are set by default.
Benefits
The Configurable PSTN Cause Code to SIP Response Mapping feature offers control and flexibility. By using command-line interface commands, you can easily customize the default or standard mappings that are currently available between PSTN and SIP networks. This allows for flexibility when setting up deployment sites.
Related Features and Technologies
•
Cisco SIP Proxy Server
•
Cisco VoIP
Related Documents
The following documents contain information related to the Cisco SIP functionality:
•
Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2
•
Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2
•
Cisco IOS IP Configuration Guide, Release 12.2
•
Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
•
Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2
•
Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.2
•
SIP Gateway Support of RSVP and TEL URL, Release 12.2(2)XB
Supported Platforms
•
Cisco 2600 series
•
Cisco 3600 series
•
Cisco AS5300 universal access server
•
Cisco AS5350 universal gateway
•
Cisco AS5400 universal gateway
•
Cisco AS5850 universal gateway
•
Cisco 7200 series
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Note
As of Cisco IOS Release 12.2(2)XB, Cisco Feature Navigator does not support features included in this limited-lifetime release.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
•
CISCO-SIP-UA-MIB
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB web site on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.RFCs
•
RFC 2543, SIP: Session Initiation Protocol
Prerequisites
The following are general prerequisites for SIP deployment:
•
Ensure that your Cisco 2600 series, Cisco 3600 series, or Cisco 7200 series router has 16-MB Flash memory and 64-MB DRAM memory, minimum. A Cisco AS5300 must have a minimum of 16-MB Flash memory and 128-MB DRAM memory. A Cisco AS5400 must have a minimum of 32-MB Flash memory and 256-MB DRAM memory.
•
Ensure that the gateway has voice functionality that is configurable for SIP.
•
Establish a working IP network.
For more information about configuring IP, refer to:
Cisco IOS IP Configuration Guide, Release 12.2•
Configure VoIP.
For more information about configuring VoIP, refer to:
Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2Configuration Tasks
See the following sections for configuration tasks for the Configurable PSTN Cause Code to SIP Response Mapping feature. Each task in the list is identified as either required or optional.
•
Mapping PSTN Codes to SIP Status Codes (optional)
•
Mapping SIP Status Codes to PSTN Cause Codes (optional)
Mapping PSTN Codes to SIP Status Codes
To configure an incoming PSTN cause code to a SIP status code, complete the following steps beginning in global configuration mode:
Mapping SIP Status Codes to PSTN Cause Codes
To configure an incoming SIP status code to a PSTN cause code, complete the following steps beginning in global configuration mode:
Verifying PSTN and SIP Code Mapping
Verifying PSTN Cause Code to SIP Status Code Mapping
The following example shows sample output for the show sip-ua map command:
Router# show sip-ua map pstn-sipPSTN-Cause Configured DefaultSIP-Status SIP-Status1 404 4042 404 4043 404 4044 500 5005 500 5006 500 5007 500 5008 500 5009 500 50015 500 50016 500 50017 486 48618 480 48019 480 48020 480 48021 403 40322 410 41026 404 40427 404 40428 484 48429 501 50130 500 50031 404 40434 503 50335 500 50036 500 50037 500 50038 503 50339 500 50040 500 50041 503 50342 503 50343 500 50044 500 50045 500 50046 500 50047 503 50349 500 50050 500 50053 500 50055 403 40357 403 40358 501 50162 500 50063 500 50065 501 50166 500 50069 500 50070 500 50079 501 50181 500 50082 500 50083 500 50084 500 50085 500 50086 500 50087 503 50388 400 40090 500 50091 500 50093 500 50095 400 40096 500 50097 500 50098 500 50099 500 500100 500 500101 500 500102 408 408103 500 500110 500 500111 400 400126 500 500127 500 500Verifying SIP Cause Code to PSTN Status Code Mapping
The following example shows sample output for the show sip-ua map command:
Router# show sip-ua map sip-pstnSIP-Status Configured DefaultPSTN-Cause PSTN-Cause400 127 127401 57 57402 21 21403 57 57404 1 1405 127 127406 127 127407 21 21408 102 102409 41 41410 1 1411 127 127413 127 127414 127 127415 79 79420 127 127480 18 18481 127 127482 127 127483 127 127484 28 28485 1 1486 17 17487 127 127488 127 127500 41 41501 79 79502 38 38503 63 63504 102 102505 127 127580 47 47600 17 17603 21 21604 1 1606 58 58Troubleshooting Tips
Use the debug ccsip all command to enable all SIP debugging capabilities, or use one of the following SIP debug commands:
–
debug ccsip calls
–
debug ccsip error
–
debug ccsip events
–
debug ccsip messages
–
debug ccsip states
Configuration Examples
This section shows the two commands that change the standard mappings between the SIP and PSTN networks. The commands set sip-status and set pstn-cause are highlighed in the following configuration.
Router# show running configBuilding configuration...Current configuration : 1564 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname 3660-1!!clock timezone GMT 0voice-card 1!ip subnet-zero!!ip domain-name sip.comip name-server 10.10.1.8!isdn switch-type primary-5ess!!voice service voipsip!!!!no voice hpi capture bufferno voice hpi capture destination!fax interface-type fax-mailmta receive maximum-recipients 0!controller T1 1/0framing esflinecode b8zsds0-group 0 timeslots 1-24 type e&m-wink-startds0 busyout 2-24!controller T1 1/1framing sflinecode ami!!!!interface FastEthernet0/0no ip addressshutdownduplex autospeed auto!interface FastEthernet0/1ip address 10.10.1.3 255.255.255.0duplex autospeed autoip rsvp bandwidth 75000 75000!ip classlessip route 0.0.0.0 0.0.0.0 FastEthernet0/1ip http serverip pim bidir-enable!!!!call rsvp-sync!voice-port 1/0:0output attenuation 3!voice-port 2/0/0!voice-port 2/0/1!voice-port 2/1/0!voice-port 2/1/1!!mgcp profile default!dial-peer cor custom!!!dial-peer voice 3640110 voipapplication sessionincoming called-number 3640110destination-pattern 3640110rtp payload-type nte 102session protocol sipv2session target ipv4:10.10.1.4dtmf-relay rtp-ntecodec g711ulaw!dial-peer voice 3660110 potsapplication sessiondestination-pattern 3660110port 2/0/0!sip-uaset sip-status 486 pstn-cause 34set pstn-cause 17 sip-status 503no oli!!line con 0exec-timeout 0 0line aux 0line vty 0 4login!!endCommand Reference
This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
New Commands
set pstn-cause
To map an incoming PSTN cause code to a SIP error status code, use the set pstn-cause command in SIP user agent configuration mode. To achieve default capabilities, use the no form of this command.
set pstn-cause value sip-status value
no set pstn-cause
Syntax Description
Defaults
The default mappings defined in the following table are used:
Command Modes
SIP user agent configuration
Command History
Usage Guidelines
A PSTN cause code can be mapped only to one SIP status code at a time.
Examples
The following example shows how to map a SIP status code to correspond with a PSTN cause code:
Router(config)# sip-uaRouter(config-sip-ua)# set pstn-cause 111 sip-status 400Router(config-sip-ua)# exitRelated Commands
Command Descriptionset sip-status
Sets an incoming SIP error status code to a PSTN release cause code.
set sip-status
To map an incoming SIP error status code to a PSTN cause code, use the set sip-status command in SIP user agent configuration mode. To achieve default capabilities, use the no form of this command.
set sip-status value pstn-cause value
no set sip-status
Syntax Description
Defaults
The default mappings defined in the following table are used:
Command Modes
SIP user agent configuration
Command History
Usage Guidelines
A SIP status code can be mapped to many PSTN cause codes. For example, 503 can be mapped to 34, 38, and 58.
Examples
The following example shows how to map a PSTN cause code to correspond with a SIP status code:
Router(config)# sip-uaRouter(config-sip-ua)# set sip-status 400 pstn-cause 16Related Commands
show sip-ua map
To display the mapping table showing PSTN cause codes and their corresponding SIP error status codes or the mapping table showing SIP-to-PSTN codes, use the show sip-ua map command in privileged EXEC mode.
show sip-ua map {pstn-sip | sip-pstn}
Syntax Description
pstn-sip
Displays PSTN cause code to SIP status code mapping table.
sip-pstn
Displays SIP status code to PSTN cause code mapping table.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is a sample output from the show sip-ua map command:
Router# show sip-ua map pstn-sipPSTN-Cause Configured DefaultSIP-Status SIP-Status1 404 4042 404 4043 404 4044 500 5005 500 5006 500 5007 500 5008 500 5009 500 50015 500 50016 500 50017 486 48618 480 48019 480 48020 480 48021 403 40322 410 41026 404 40427 404 40428 484 48429 501 50130 500 50031 404 40434 503 50335 500 50036 500 50037 500 50038 503 50339 500 50040 500 50041 503 50342 503 50343 500 50044 500 50045 500 50046 500 50047 503 50349 500 50050 500 50053 500 50055 403 40357 403 40358 501 50162 500 50063 500 50065 501 50166 500 50069 500 50070 500 50079 501 50181 500 50082 500 50083 500 50084 500 50085 500 50086 500 50087 503 50388 400 40090 500 50091 500 50093 500 50095 400 40096 500 50097 500 50098 500 50099 500 500100 500 500101 500 500102 408 408103 500 500110 500 500111 400 400126 500 500127 500 500
The following example shows the mapped sip-pstn settings:
Router# show sip-ua map sip-pstnSIP-Status Configured DefaultPSTN-Cause PSTN-Cause400 127 127401 57 57402 21 21403 57 57404 1 1405 127 127406 127 127407 21 21408 102 102409 41 41410 1 1411 127 127413 127 127414 127 127415 79 79420 127 127480

