Table Of Contents
Configuring Locale-Based Multifrequency Tones on Cisco 1751 and Cisco 1760 Routers
Configuring Locale-Based Multifrequency Tones
Using the IP Telephony Locale Installer
Assigning Network Locales to Gateways
Verifying the Voice-Port Configuration
Verifying the Custom Tone Download
Verifying the Custom Tone Parameters for Each Locale
Custom Tone Usage in H.323 mode
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Configuring Locale-Based Multifrequency Tones on Cisco 1751 and Cisco 1760 Routers
This document describes support for locale-based multifrequency tones on Cisco 1751 and Cisco 1760 routers.
Note
Cisco CallManager 3.3(2) is the first Cisco CallManager release that supports this feature.
Contents
This document includes the following sections:
•
•
•
Configuring Locale-Based Multifrequency Tones
Cisco 1751 and Cisco 1760 routers can act as voice gateways, connecting an IP Telephony network to a traditional telephone trunk or to analog devices. Gateways use the Media Gateway Control Protocol (MGCP) or H.323 to communicate with Cisco CallManager.
Cisco IOS gateways typically use pre-defined static tones. The static tones for each country are stored in IOS tone tables. Beginning with Cisco CallManager 3.3(2), locale-specific tones and their associated frequency, amplitude, and cadence information can be stored on a trivial file transfer protocol (TFTP) server and downloaded to gateways in an XML-based configuration file. The country-specific information that is stored in this configuration file is referred to as a network locale. When Cisco CallManager and the gateway are properly configured, the tones with locale-specific frequency, amplitude, and cadence as stored on the TFTP server are used in place of the pre-defined static tones in the IOS tone table.
Using the IP Telephony Locale Installer
Network locale files provide country-specific phone tones and gateway tones, if available. User locale files provide translated text and voice prompts, if available, for phone displays, user applications, and user web pages in the locale that the user chooses. An administrator must first use the Cisco IP Telephony Locale Installer to make network locale files available so that users can view or receive the translated text or tones.
For more information, refer to the document Using the Cisco IP Telephony Locale Installer.
Assigning Network Locales to Gateways
Provided that an administrator has run the IP Telephony Locale Installer to make network locale files available for download, it is possible to begin assigning network locales to gateway voice ports.
Refer to the "Gateway Configuration" chapter in the Cisco CallManager Administration Guide, Release 3.3(2) for instructions on how to configure gateways and gateway ports in Cisco CallManager.
Tip
Configuring Gateways
Your gateway configuration, as well as the configuration of other network devices, must provide connectivity between your target gateway and the TFTP server. When the XML configuration file is received, the local gateway parses the configuration file, converts its contents to IOS commands, and updates the gateway configuration accordingly. The mgcp and ccm-manager mgcp commands are automatically configured on the gateway as part of this process.
Note
If the IOS command ccm-manager download-tones has been entered on the gateway, as described later in this section, when the gateway registers, restarts, or resets, the gateway can download up to two network locale files. Each network locale file includes the supported tones and their associated frequencies and cadences for a particular country.
When an MGCP gateway registers with Cisco CallManager, or if the gateway restarts or resets, the network locale information for each gateway port is downloaded to the gateway.
A typical sequence of IOS commands for configuring a gateway and ensuring that custom tones have been downloaded to it is shown below:
Verifying the Voice-Port Configuration
To verify that the voice ports have custom tones (C1 and C2) assigned, use the show running-config or the show voice-port command.
The following shows a portion of the show running-config command output, both before and after custom tones (C1 and C2) have been downloaded to the gateway. In this sample output, voice port 1/0 initially has cptone HK (Hong Kong) assigned, and voice port 1/1 initially has cptone CN (China) assigned:
! The custom tones, C1 and C2, have not yet been downloaded. HK and CN are assigned to the two interfaces.!voice-port 1/0cptone HK!voice-port 1/1cptone CN!! The custom tones, C1 and C2, have been downloaded.!voice-port 1/0cptone C1!voice-port 1/1cptone C2!
Note
Verifying the Custom Tone Download
To verify that the custom tones have been downloaded, use the show ccm-manager download-tones command. The following sample output shows that custom tone 1 is assigned to France and custom tone 2 is assigned to Spain:
Router# show ccm-manager download-tonesMGCP Download Tones: EnabledCustom Tone 1: FranceCustom Tone 2: SpainYou can also use the show ccm-manager download-tones command to view detailed information about the frequency, impedance, and other values associated with a particular custom tone, as shown here for custom tone 1:
Router# show ccm-manager download-tones C1Custom Tone 1 : FrancePulse dial:normal, Percent make:35%, DTMF low Amp.= 65424, high Amp.= 65446, Pcm:u-LawFXS FXO E&M FXS FXO E&MDual Tone DR NF FOF FOS AOF AOF AOF AOS AOS AOS ONTF OFTF ONTS OFTS ONTT OFTT ONT4 OFT4(optional) FOF2 FOS2 FOF3 FOS3 FOF4 FOS4 FOT FO4 AOT AO4 RCT1 RCT2 RCT3 RCT4BUSY 0 2 480 620 -120 -120 -120 -120 -120 -120 500 500 0 0 0 0 0 0RING_BACK 0 2 440 520 -120 -120 -120 -120 -120 -120 400 200 400 3000CONGESTION 0 2 480 620 -200 -200 -200 -240 -240 -240 250 250 0 0 NUMBER_UNOBTAINABLE 0 2 480 620 -120 -120 -120 -120 -120 -120 65535 0 0 0DIAL_TONE 0 2 350 440 -150 -150 -150 -150 -150 -150 65535 0 0 0 DIAL_TONE2 0 2 350 440 -150 -150 -150 -150 -150 -150 65535 0 0 0OUT_OF_SERVICE 0 1 950 0 -150 -150 -150 0 0 0 330 330 0 0 ADDR_ACK 0 1 600 0 -240 -240 -240 0 0 0 125 125 125 65535 DISCONNECT 0 1 600 0 -150-150 -150 0 0 0 330 330 330 65535 OFF_HOOK_NOTICE 0 2 1400 2040 -240 -240 -240 -240 -240 -240 100 100 0 0 OFF_HOOK_ALERT 0 2 1400 2040 -240-240 -240 -240 -240 -240 100 100 0 0 WAITING 0 0 0 0 0 0 0 0 0 0 0 0 0 0 CONFIRM 0 0 0 0 0 0 0 0 0 0 0 0 0 0CNFWRN_J 0 1 950 0 -170 -170 -190 0 0 0 100 100 100 65535 CNFWRN_D 0 1 600 0 -170 -170 -190 0 0 0 100 100 100 65535 STUTT_DIALTONE 0 2 350440 -150 -150 -150 -150 -150 -150 100 100 100 100 100 100 65535 0PERM_SIG_TONE 0 1 480 0 -170 -170 -170 0 0 0 65535 0 0 0WAITING1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 WAITING2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 WAITING3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 WAITING4 0 0 0 0 0 0 0 0 0 0 00 0 0 MSGWAIT_IND 0 0 0 0 0 0 0 0 0 0 0 0 0 0 OFF_HOOK_WARN 0 0 0 0 0 0 0 0 0 0 0 0 0 0Sequence Tone DR NF F1C1 F2C1 AOF AOS C1ONT C1OFT C2ONT C2OFT C3ONT C3OFT C4ONT C4OFT F1C2 F2C2 F1C3 F2C3 F1C4 F2C4INTERCEPT 0 0 0 0 0 0 0 0 0 0 0 0 TONE_ON_HOLD 0 0 0 0 0 0 0 0 0 0 0 0 NO_CIRCUIT 0 0 0 0 0 0 0 0 0 0 0 0Legend:DR: direction NF: number of frequency FO<F,S,T,4>: frequency of<1st,2nd,3rd,4th> AO<F,S,T,4>: amplitude of<1st,2nd,3rd,4th>FOF<1-4>: frequency of 1st, cadence<1-4> FOS<1-4>: frequency of 2nd, cadence<1-4>RCT<1-4>: repeat count for cadence<l-4> F(1-4>C<1-4> : frequency<1-4> of cadence<1-4>C<1-4>ONT: cadence<1-4> on time C<1-4>OFT: cadence<1-4> off timeVerifying the Custom Tone Parameters for Each Locale
You can use the debug ccm-manager tone command to verify the parameters assigned to each locale. The following sample output shows the locale name as United Kingdom and lists all of the dual-tone parameters for that region:
Router# debug ccm-manager config-download tone00:09:07:cmapp_prefix_process_tag_tones:00:09:07: cmapp_process_tag_trkLocaleName: region = United Kingdom00:09:07: cmapp_process_tag_pulse_ratio: pulse ratio = 4000:09:07: cmapp_process_tag_dtmf_llevel: low frequency level = 6543800:09:07: cmapp_process_tag_dtmf_hlevel: high frequency level = 6546300:09:07: cmapp_process_tag_special_oper: operation = uLaw00:09:07: cmapp_prefix_process_tag_lpig:00:09:07: cmapp_process_tag_fxs: ignore LPIG for fxs00:09:07: cmapp_process_tag_fxo: ignore LPIG for fxo00:09:07: cmapp_process_tag_digital: ignore LPIG for digital00:09:07: cmapp_prefix_process_tag_lpog:00:09:07: cmapp_process_tag_fxs: ignore LPOG for fxsBoth ports are in service00:09:07: cmapp_process_tag_fxo: ignore LPOG for fxo00:09:07: cmapp_process_tag_digital: ignore LPOG for digital00:09:07: cmapp_prefix_process_tag_tonetable_info:00:09:07: cmapp_prefix_process_tag_dualtone: TID=[0:CPTONE_BUSY]00:09:07: cmapp_process_tag_nf: number of frequencies = 100:09:07: cmapp_process_tag_dr: direction = 000:09:07: cmapp_process_tag_fof: frequency 1 = 40000:09:07: cmapp_process_tag_fos: frequency 2 = 000:09:07: cmapp_process_tag_fot: frequency 3 = 000:09:07: cmapp_process_tag_fo4: frequency 4 = 000:09:07: cmapp_prefix_process_tag_aof_level:00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -20000:09:07: cmapp_process_tag_fxo: amplitude of 1st = -20000:09:07: cmapp_process_tag_digital: amplitude of 1st = -24000:09:07: cmapp_prefix_process_tag_aos_level:00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 000:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 000:09:07: cmapp_process_tag_digital: amplitude of 2nd = 000:09:07: cmapp_prefix_process_tag_aot_level:00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 000:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 000:09:07: cmapp_process_tag_digital: amplitude of 3rd = 000:09:07: cmapp_prefix_process_tag_ao4_level:00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 000:09:07: cmapp_process_tag_fxo: amplitude of 4th = 000:09:07: cmapp_process_tag_digital: amplitude of 4th = 000:09:07: cmapp_process_tag_ontf: frequency 1 on time = 37500:09:07: cmapp_process_tag_oftf: frequency 1 off time = 37500:09:07: cmapp_process_tag_onts: frequency 2 on time = 000:09:07: cmapp_process_tag_ofts: frequency 2 off time = 000:09:07: cmapp_process_tag_ontt: frequency 3 on time = 000:09:07: cmapp_process_tag_oftt: frequency 3 off time = 000:09:07: cmapp_process_tag_ont4: frequency 4 on time = 000:09:07: cmapp_process_tag_oft4: frequency 4 off time = 000:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 000:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 000:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 000:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 000:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 000:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 000:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 000:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 000:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 000:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 000:09:07: cmapp_prefix_process_tag_dualtone: TID=[1:CPTONE_RING_BACK]00:09:07: cmapp_process_tag_nf: number of frequencies = 200:09:07: cmapp_process_tag_dr: direction = 000:09:07: cmapp_process_tag_fof: frequency 1 = 40000:09:07: cmapp_process_tag_fos: frequency 2 = 45000:09:07: cmapp_process_tag_fot: frequency 3 = 000:09:07: cmapp_process_tag_fo4: frequency 4 = 000:09:07: cmapp_prefix_process_tag_aof_level:00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -19000:09:07: cmapp_process_tag_fxo: amplitude of 1st = -19000:09:07: cmapp_process_tag_digital: amplitude of 1st = -19000:09:07: cmapp_prefix_process_tag_aos_level:00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = -19000:09:07: cmapp_process_tag_fxo: amplitude of 2nd = -19000:09:07: cmapp_process_tag_digital: amplitude of 2nd = -19000:09:07: cmapp_prefix_process_tag_aot_level:00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 000:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 000:09:07: cmapp_process_tag_digital: amplitude of 3rd = 000:09:07: cmapp_prefix_process_tag_ao4_level:00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 000:09:07: cmapp_process_tag_fxo: amplitude of 4th = 000:09:07: cmapp_process_tag_digital: amplitude of 4th = 000:09:07: cmapp_process_tag_ontf: frequency 1 on time = 40000:09:07: cmapp_process_tag_oftf: frequency 1 off time = 20000:09:07: cmapp_process_tag_onts: frequency 2 on time = 40000:09:07: cmapp_process_tag_ofts: frequency 2 off time = 200000:09:07: cmapp_process_tag_ontt: frequency 3 on time = 000:09:07: cmapp_process_tag_oftt: frequency 3 off time = 000:09:07: cmapp_process_tag_ont4: frequency 4 on time = 000:09:07: cmapp_process_tag_oft4: frequency 4 off time = 000:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 000:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 000:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 000:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 000:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 000:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 000:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 000:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 000:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 000:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 000:09:07: cmapp_prefix_process_tag_dualtone: TID=[2:CPTONE_CONGESTION]00:09:07: cmapp_process_tag_nf: number of frequencies = 100:09:07: cmapp_process_tag_dr: direction = 000:09:07: cmapp_process_tag_fof: frequency 1 = 40000:09:07: cmapp_process_tag_fos: frequency 2 = 000:09:07: cmapp_process_tag_fot: frequency 3 = 000:09:07: cmapp_process_tag_fo4: frequency 4 = 000:09:07: cmapp_prefix_process_tag_aof_level:00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -20000:09:07: cmapp_process_tag_fxo: amplitude of 1st = -20000:09:07: cmapp_process_tag_digital: amplitude of 1st = -20000:09:07: cmapp_prefix_process_tag_aos_level:00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 000:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 000:09:07: cmapp_process_tag_digital: amplitude of 2nd = 000:09:07: cmapp_prefix_process_tag_aot_level:00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 000:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 000:09:07: cmapp_process_tag_digital: amplitude of 3rd = 000:09:07: cmapp_prefix_process_tag_ao4_level:00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 000:09:07: cmapp_process_tag_fxo: amplitude of 4th = 000:09:07: cmapp_process_tag_digital: amplitude of 4th = 000:09:07: cmapp_process_tag_ontf: frequency 1 on time = 40000:09:07: cmapp_process_tag_oftf: frequency 1 off time = 35000:09:07: cmapp_process_tag_onts: frequency 2 on time = 22500:09:07: cmapp_process_tag_ofts: frequency 2 off time = 52500:09:07: cmapp_process_tag_ontt: frequency 3 on time = 000:09:07: cmapp_process_tag_oftt: frequency 3 off time = 000:09:07: cmapp_process_tag_ont4: frequency 4 on time = 000:09:07: cmapp_process_tag_oft4: frequency 4 off time = 000:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 000:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 000:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 000:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 000:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 000:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 000:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 000:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 000:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 000:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0! The rest of the debug output is not shown.Custom Tone Usage in H.323 mode
Provided that the custom tones have been downloaded to the gateway, they can also be used in H.323 mode. For instance, if the MGCP gateway loses connectivity with Cisco CallManager, it can be configured so that it reverts to H.323 control (this feature is known as MGCP gateway fallback). The downloaded custom tone tables continue to be used in H.323 mode.
Note
Note
Related Documentation
For additional information, refer to the following documentation:
•
•
•
•
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•
•
•
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to:
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•
•
•
•
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Guest
