ATA 190 Country-Specific Tones and Cadences

Mechanism

The administrator can upload an XML file named g3-tones.xml that describes the tones and cadences to the directory on the Cisco Unified Communications Manager TFTP server. The directory name is actually a locale name, such as Australia.

During provisioning, device knows the network locale setting and tries to download [locale name]/g3-tones.xml from the Cisco Unified CM TFTP server. For example, if network locale is set to Australia, the path is Australia/g3-tones.xml.

Link Tone File With Device

There are two methods to achieve this purpose:

1. In Cisco Unified Communications Manager, navigate to System > Device Pool, and set the Network Locale value to specify locale option.

2. In Cisco Unified Communications Manager, navigate to Device > Phone. On the device window, set the value of Network Locale, which overwrites the value that is set in method 1.

Note For method 2, network locale from Device > Phone is not configurable currently because there are only two choices: none and United States. There is a known issue for Cisco Unified Communications Manager that countries other than the United States cannot be selected from this menu. Method 2 has a higher priority than method 1.

Notes for Tone Configuration

  • Only ATA 190 Line1 network locale setting is applied. This means that the line2 network locale always applies the line1 option, even if the value of line2 network locale configured on the Cisco Unified Communications Manager web page differs from the line1 value.
  • Only these tones can be configured:

– Ringback tone

– Reorder tone

– Dialing tone

– Outside dialing tone

– Busy tone

– Call waiting tone

Any tone specification that appears in the tone profile but is either not supported or has invalid data fields (even if the tone is supported) is ignored.

– Example: A tone profile includes a valid reorder tone specification, an invalid busy tone specification (has invalid data fields) and a recording tone spec (not supported), only the reorder tone spec would be applied.

  • The name of the XML that describes tones and cadences can only be g3-tones.xml now. (New implementations may be added to try other files with different names.)
  • Each tone can specify at most four c/i pairs (about frequency and gain) and four cadence segments (each is an on/off pair). Any additional data gets discarded.