Table Of Contents
Cisco Survivable Remote Site Telephony V2.1: New Features for Cisco IOS Release 12.2(11)YT
Specifications for Cisco SRS Telephony V2.1
Restrictions in Cisco IOS Telephony Service V2.1
Information About New Features in Cisco SRS Telephony V.2.1
Additional Language Options for IP Phone Display
Cisco IP Phone Expansion Module 7914 Support
Increase in Directory Number Maximums
How to Configure New Features in Cisco SRS Telephony V2.1
Configuring Language Display for Cisco IP Phone 7940 and Cisco 7960 IP Phone
Integrating DTMF with Legacy Voice-Mail Devices (required)
Configuring DTMF Patterns on the Router
Configuring Integration Files on Legacy Voice-Mail Systems
Configuration Examples for Cisco SRS Telephony V2.1
Local Voice-Mail System Example
Central Location Voice-Mail System Example
pattern direct (vm-integration)
pattern ext-to-ext busy (vm-integration)
pattern ext-to-ext no-answer (vm-integration)
pattern trunk-to-ext busy (vm-integration)
pattern trunk-to-ext no-answer (vm-integration)
Cisco Survivable Remote Site Telephony V2.1: New Features for Cisco IOS Release 12.2(11)YT
Note We are experiencing technical difficulties in displaying all portions of the HTML version of this document. Until these difficulties are resolved, please use the PDF version by clicking the icon at the upper right.
Cisco Survivable Remote Site (SRS) Telephony V2.1 introduces integration with a central-site Unity voice-mail system, additional languages, Cisco IP Phone Expansion Module 7914, and enhancements to the dialplan-pattern command.
Note This document discusses new features only. For information on SRS Telephony installation and basic configuration, refer to Survivable Remote Site Telephony Version 2.01.
Feature Specifications for Cisco Survivable Remote Site Telephony
Note You must purchase a feature license to use Cisco SRS Telephony.
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on 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 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.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
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.
Contents
•Specifications for Cisco SRS Telephony V2.1
•Restrictions in Cisco IOS Telephony Service V2.1
•Information About New Features in Cisco SRS Telephony V.2.1
•How to Configure New Features in Cisco SRS Telephony V2.1
•Configuration Examples for Cisco SRS Telephony V2.1
Note This document discusses new features only. For information on SRS Telephony installation and basic configuration, refer to Survivable Remote Site Telephony Version 2.01.
Specifications for Cisco SRS Telephony V2.1
Table 1 lists the Cisco platforms, maximum number of Cisco IP phones, maximum number of directory numbers (DNs) or virtual voice ports, and memory requirements for Cisco SRS Telephony V2.1 in Cisco IOS Release 12.2(11)YT.
Table 1 Specifications for Version 2.01 Released in 12.2(11)YT
Cisco Platform Maximum Cisco IP Phones Maximum Directory Numbers Minimum DRAM Memory Recommended DRAM Memory Minimum Flash Memory Recommended Flash Memory Cisco IOS ReleaseCisco 1751 router
24
120
64 MB
64 MB
16 MB
32 MB
12.2(11)YT
Cisco 1760 router
24
120
64 MB
64 MB
16 MB
32 MB
12.2(11)YT
Cisco 2600-XM routers1
24
120
96 MB
128 MB
32 MB
—
12.2(11)YT
Cisco 2650 and Cisco 2651 routers
48
192
96 MB
128 MB
16 MB
32 MB
12.2(11)YT
Cisco 2650-XM and Cisco 2651-XM routers
48
192
96 MB
128 MB
32 MB
—
12.2(11)YT
Cisco 2691 router
72
288
96 MB
128 MB
32 MB
—
12.2(11)YT
Cisco 3640 router and Cisco 3640A router
72
288
96 MB
128 MB
32 MB
—
12.2(11)YT
Cisco 3660 router
240
960
96 MB
128 MB
16 MB
32 MB
12.2(11)YT
Cisco 3725 router
144
576
128 MB
—
32 MB
—
12.2(11)YT
Cisco 3745 router
240
960
128 MB
—
32 MB
—
12.2(11)YT
1 Cisco 2610-XM, Cisco 2611-XM, Cisco 2620-XM, and Cisco 2621-XM.
Restrictions in Cisco IOS Telephony Service V2.1
•Voice-mail support does not include a Message Waiting Indicator (MWI).
Information About New Features in Cisco SRS Telephony V.2.1
Note This document discusses new features only. For information on SRS Telephony installation and basic configuration, refer to Survivable Remote Site Telephony Version 2.01.
Cisco SRS Telephony Version 2.1 introduces the new features described in the following sections:
•Additional Language Options for IP Phone Display
•Cisco IP Phone Expansion Module 7914 Support
•Increase in Directory Number Maximums
Additional Language Options for IP Phone Display
Displays for the Cisco IP Phone 7940 and Cisco IP Phone 7960 can be configured with ISO-3166 codes for the following countries:
•Denmark
•France
•Germany
•Italy
•The Netherlands
•Norway
•Portugal
•Spain
•Sweden
•United States
Note This feature is available only in Cisco SRS Telephony running under Cisco CallManager V3.2.
For configuration information, see the "Configuring Language Display for Cisco IP Phone 7940 and Cisco 7960 IP Phone" section.
Cisco IP Phone Expansion Module 7914 Support
SRS Telephony V2.1 supports Cisco 7960 IP phones with one or two Cisco IP Phone 7914 expansion modules. The expansion modules support up to 34 lines or speed-dial keys.
No configuration is necessary.
dialplan-pattern Command
The new dialplan-pattern command is available for creating global prefixes that can be used to expand the abbreviated extension numbers into fully qualified E.164 numbers. This new command provides for the manipulation of IP phone abbreviated extension number prefix digits. See Command Reference
Increase in Directory Number Maximums
Directory numbers were increased for the platforms shown in Table 2.
Unity Voice Mail Integration
Unity voice mail is integrated with Cisco SRS Telephony, introducing six new commands:
•pattern direct (vm-integration)
•pattern ext-to-ext busy (vm-integration)
•pattern ext-to-ext no-answer (vm-integration)
•pattern trunk-to-ext busy (vm-integration)
•pattern trunk-to-ext no-answer (vm-integration)
For further information, see the "Integrating DTMF with Legacy Voice-Mail Devices (required)" section.
How to Configure New Features in Cisco SRS Telephony V2.1
This section describes how to configure a router for the new features in Cisco SRS Telephony V.2.1 described in the following sections:
•Configuring Language Display for Cisco IP Phone 7940 and Cisco 7960 IP Phone (required)
•Integrating DTMF with Legacy Voice-Mail Devices (required) (required)
Configuring Language Display for Cisco IP Phone 7940 and Cisco 7960 IP Phone
Language confutation involves selecting a desired phone display language for the Cisco IP Phone 7940 and Cisco IP Phone 7960 that provides the language's character set and spelling.
Note This configuration option is available to Cisco SRS Telephony running under Cisco CallManager V3.2. Systems running software prior to Cisco CallManager V3.2 can use only the default country, United States (US).
SUMMARY STEPS
1. call-manager-fallback
2. user-locale country-code
DETAILED STEPS
Integrating DTMF with Legacy Voice-Mail Devices (required)
For dual tone multifrequency (DTMF) integrations, information on how to route incoming or forwarded calls is sent by the telephone system in the form of DTMF digits. The DTMF digits are in the form of a pattern and depend on the voice-mail system connected to the Cisco SRS Telephony router. These patterns are required for the DTMF integration with most voice-mail systems. The DTMF integration configuration on the Cisco SRS Telephony router works with any analog voice-mail system. Voice-mail systems are designed to respond to DTMF after the system has answered the incoming calls. The tasks described in the following sections are required:
•Configuring DTMF Patterns on the Router (required)
•Configuring Integration Files on Legacy Voice-Mail Systems (required)
Note Foreign Exchange Office (FXO) hairpin forwarded calls to voice mail must have disconnect supervision from the central office.
Configuring DTMF Patterns on the Router
The Cisco SRS Telephony router provides flexibility for the integration with any legacy voice-mail system. You can configure multiple tags and tokens for each pattern, depending on the voice-mail system and type of access. The tag in the configuration pattern must match the number defined in the voice-mail system's integration file to identify the type of call. The keywords—CGN (calling number), CDN (called number), and FDN (forwarding number)—define the type of call information sent to the voice-mail system.
SUMMARY STEPS
1. vm-integration
2. pattern direct [tag1 {CGN | CDN | FDN}] [tag2 {CGN | CDN | FDN}] [tag3 {CGN | CDN | FDN}] [last-tag]
3. pattern ext-to-ext busy [tag1 {CGN | CDN | FDN}] [tag2 {CGN | CDN | FDN}] [tag3 {CGN | CDN | FDN}] [last-tag]
4. pattern ext-to-ext no-answer [tag1 {CGN | CDN | FDN}] [tag2 {CGN | CDN | FDN}] [tag3 {CGN | CDN | FDN}] [last-tag]
5. pattern trunk-to-ext busy [tag1 {CGN | CDN | FDN}] [tag2 {CGN | CDN | FDN}] [tag3 {CGN | CDN | FDN}] [last-tag]
6. pattern trunk-to-ext no-answer [tag1 {CGN | CDN | FDN}] [tag2 {CGN | CDN | FDN}] [tag3 {CGN | CDN | FDN}] [last-tag]
DETAILED STEPS
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Configuring Integration Files on Legacy Voice-Mail Systems
To configure the integration files for a legacy voice-mail system, follow the instructions in the voice-mail system's analog voice mail integration configuration guide or recommended documents. You must design the DTMF integration patterns appropriately, so that the voice-mail system and the Cisco SRS Telephony router work with each other. For a confutation example, see the "Configuration Examples for Cisco SRS Telephony V2.1" section
Configuration Examples for Cisco SRS Telephony V2.1
The examples in this section show how to configure analog voice-mail integration. They include configuration examples for local and central voice-mail systems.
Local Voice-Mail System Example
The first part of the examples shows a legacy dial-peer configuration for a local voice-mail system. The second part is a compatible Cisco SRS Telephony V2.1 configuration.
! Dial-peer configuration for integration for voice-mail system!dial-peer voice 101 potsdestination-pattern 14011port 3/0/0!dial-peer voice 102 potspreference 1destination-pattern 14011port 3/0/1!dial-peer voice 103 potspreference 2destination-pattern 14011port 3/1/0!dial-peer voice 104 potsdestination-pattern A14012port 3/1/1!! Cisco SRS Telephony configuration!call-manager-fallbackmax-ephones 24max-dn 144ip source-address 1.4.214.104 port 2000voicemail 14011!! Cisco SRS Telephony voice-mail integration pattern configuration!vm-integrationpattern direct 2 CGN *pattern ext-to-ext no-answer 5 FDN * CGN *pattern ext-to-ext busy 7 FDN * CGN *pattern trunk-to-ext no-answer 4 FDN * CGN *pattern trunk-to-ext busy 6 FDN * CGN *Central Location Voice-Mail System Example
The first part of the examples shows a legacy dial-peer configuration for a central voice-mail system. The second part is a compatible Cisco SRS Telephony V2.1 configuration.
Note MWI integration is not supported for PSTN access to voice-mail systems at a central locations.
! Dial-peer configuration for integration with voice-mail system! located in central location!dial-peer voice 101 potsdestination-pattern 14011port 3/0/0!! Cisco SRS Telephony configuration!call-manager-fallbackmax-ephones 24max-dn 144ip source-address 1.4.214.104 port 2000voicemail 14011!! Cisco SRS Telephony voice-mail integration pattern configuration!vm-integrationpattern direct 2 CGN *pattern ext-to-ext no-answer 5 FDN * CGN *pattern ext-to-ext busy 7 FDN * CGN *pattern trunk-to-ext no-answer 4 FDN * CGN *pattern trunk-to-ext busy 6 FDN * CGN *Additional References
The following sections provide additional references related to Cisco SRS Telephony V2.1:
•MIBs
•RFCs
Related Documents
Related Topic Document TitleCisco Survivable Remote Site Telephony
Cisco IP Phones
Command references for voice and telephony commands
Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2 T
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
MIBs
MIBs 1 MIBs Link•
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
1 Not all supported MIBs are listed.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
Technical Assistance
Command Reference
This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 T command reference publications.
•pattern direct (vm-integration)
•pattern ext-to-ext busy (vm-integration)
•pattern ext-to-ext no-answer (vm-integration)
•pattern trunk-to-ext busy (vm-integration)
•pattern trunk-to-ext no-answer (vm-integration)
dialplan-pattern
To create a global prefix that can be used to expand the abbreviated extension numbers into fully qualified E.164 numbers, use the dialplan-pattern command in call-manager-fallback configuration mode. To disable the dialplan-pattern command settings, use the no form of this command.
dialplan-pattern tag pattern extension-length length [extension-pattern extension-pattern] [no-reg]
no dialplan-pattern tag [pattern extension-length length extension-pattern extension-pattern]
Syntax Description
Defaults
No default behavior or values
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
Directory numbers for the Cisco IP phones are expected to be entered in extension number format. The extension number should be greater or equal to the extension length. Otherwise, the extension number cannot be converted to a qualified E.164 number. The dialplan-pattern command creates a global prefix that can be used to expand the abbreviated extension numbers to fully qualified E.164 numbers. The dial-plan pattern is also required to register the Cisco IP phone lines with a gatekeeper. The dialplan-pattern command can resolve an incoming call with a full E.164 number to a Cisco IP phone extension number.
The extension-length keyword enables the system to convert a full E.164 telephone number back to an extension number for the purposes of caller-ID display, received, and missed call lists. For example, a company uses extension number range 5000 to 5099 across several sites, with only the extensions 5000 to 5009 present on the local router. An incoming call from 5044 arrives from the company's internal VoIP H.323 network and this call includes the calling number as 4085555044 in its full E.164 format.
The no-reg keyword provides dialing flexibility. You have the option not to register some specific numbers to the gatekeeper so that those numbers can be used for other telephony services.
When the called number matches the dial-plan pattern, the call is considered a local call and has a distinctive ringing identifying the call as internal. Any call that does not match the dial-plan pattern is considered an external call and has a distinctive ringing different from the internal ringing. The valid dial-plan pattern with the lowest tag is used as a prefix to all local Cisco IP phones.
The number of extension-pattern characters must match the extension length. For example, if the extension length is three, then the extension-pattern can be 8.., 1.., 5.., and so forth.
Examples
The following example shows how to create dial-plan pattern 1 for extension numbers 5001 to 5099 with the telephone prefix starting with 408555. If the following example is set, the routers recognize that the 4085555044 matches dial-plan pattern 1, and uses the extension-length keyword to extract the last four digits of the number 5044 and present this as the caller ID for the incoming call.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 40855550.. extension-length 4 no-regIn the following example the dialplan-pattern command creates dial-plan pattern 1 for extensions 801 to 899 with the telephone prefix starting with 4085559. As each number in the extension pattern is declared with the number command, two POTs dial-peers are created. In the example, they are 801 (an internal office number) and 4085579001 (an external number).
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 40855590.. extension-length 3 extension-pattern 8..Router(config-cm-fallback)# phone-dn 1Router(config-ephone-dn)# number 801
Related Commands
pattern direct (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system when the user presses the messages button on the phone, use the pattern direct command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when the user presses the messages button on the phone, use the no form of this command.
pattern direct tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern direct tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern direct command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Call Transfer and Forward Supplementary Services router through one or more voice ports. When a call is placed directly from a Cisco IP phone attached to the Cisco IOS Call Transfer and Forward Supplementary Services router, the voice-mail system expects to receive a sequence of DTMF digits at the beginning of the call that identify the mailbox of the user calling the voice-mail system accompanied by a string of digits indicating that the caller is attempting to access the designated mailbox in order to retrieve messages.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for a calling number ($CGN) for a direct call to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern direct 2 CGN *Related Commands
pattern ext-to-ext busy (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an internal extension attempts to connect to a busy extension and the call is forwarded to voice mail, use the pattern ext-to-ext busy command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when an internal extension calls a busy extension and the call is forwarded to a voice-mail system, use the no form of this command.
pattern ext-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern ext-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern ext-to-ext busy command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Call Transfer and Forward Supplementary Services router through one or more voice ports. When a call is routed to the voice-mail system by call forward on busy from a Cisco IP phone attached to the Cisco IOS Call Transfer and Forward Supplementary Services router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits that identify the extension number of the calling IP phone.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for a local call forwarded on busy to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern ext-to-ext busy 7 FDN * CGN *Related Commands
pattern ext-to-ext no-answer (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an internal extension fails to connect to an extension and the call is forwarded to voice mail, use the pattern ext-to-ext no-answer command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding, use the no form of this command.
pattern ext-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern ext-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern ext-to-ext no-answer command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Call Transfer and Forward Supplementary Services router through one or more voice ports. When a call is routed to the voice-mail system by call forward on no-answer from an IP phone attached to the Cisco IOS Call Transfer and Forward Supplementary Services router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits that identify the extension number of the calling IP phone.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for a local call forwarded on no-answer to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern ext-to-ext no-answer 5 FDN * CGN *Related Commands
pattern trunk-to-ext busy (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an external trunk call reaches a busy extension and the call is forwarded to voice mail, use the pattern trunk-to-ext busy command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when an external trunk call reaches a busy extension and the call is forwarded to a voice-mail system, use the no form of this command.
pattern trunk-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern trunk-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern trunk-to-ext busy command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Call Transfer and Forward Supplementary Services router through one or more voice ports. When a call is routed to the voice-mail system by call forward on busy from an IP phone attached to the Cisco IOS Call Transfer and Forward Supplementary Services router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits indicating that the call originated from a PSTN or VoIP caller.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for call forwarding when an external trunk call reaches a busy extension and the call is forwarded to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern trunk-to-ext busy 6 FDN * CGN *Related Commands
pattern trunk-to-ext no-answer (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system when an external trunk call reaches an unanswered extension and the call is forwarded to voice mail, use the pattern trunk-to-ext no-answer command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when an external trunk call reaches another extension where the called party does not answer and the call is forwarded to a voice-mail system, use the no form of this command.
pattern trunk-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern trunk-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern trunk-to-ext no-answer command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Call Transfer and Forward Supplementary Services router through one or more voice ports. When a call is routed to the voice-mail system by call forward on no-answer from an IP phone attached to the Cisco IOS Call Transfer and Forward Supplementary Services router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits indicating that the call originated from a PSTN or VoIP caller.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for call forwarding when an external trunk call reaches an unanswered extension and the call is forwarded (FDN) to a voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern trunk-to-ext no-answer 4 FDN * CGN *Related Commands
user-locale
To set language for displays on the Cisco IP Phone 7940 and Cisco IP Phone 7960 by country, use the user-locale command in call-manager-fallback configuration mode. To disable the country selection and use the default country (United State), use the no form of this command.
user-locale country-code
no user locale country-code
Syntax Description
Defaults
The default country code is US (United States).
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
All of the country-code options are available to Cisco Survivable Remote Site Telephony systems running under Cisco CallManager V3.2. Systems running Cisco CallManager prior to V3.2 can use only the default country, United States (US).
To deactivate one country code and activate another, use the no network-locale command.
Examples
The following example shows how to set the user locale the ISO-3166 code for Spain:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# user-locale ESRelated Commands
Command Descriptioncall-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
vm-integration
To enter voice-mail integration configuration mode and enable voice-mail integration with dual tone multifrequency (DTMF) and analog voice-mail systems, use the vm-integration command in global configuration mode. To disable voice-mail integration, use the no form of this command.
vm-integration
no vm-integration
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The vm-integration command allows you to enter voice-mail integration configuration mode and allows integration with DTMF and analog voice-mail systems.
Examples
The following example shows how to enter voice-mail integration configuration mode:
Router(config) vm-integrationRouter(config-vm-integration)Related Commands