The call routing component of CallManager is extensible. In previous sections, the @ wildcard has always been described in the context of the North American numbering plan. As described in the section "@ Wildcard," the @ wildcard is a macro that, based on the numbering plan you select, adds many route patterns on your behalf. By default, CallManager Administration permits you to select only North American Numbering Plan from the Numbering Plan drop-down list.
The list of route patterns that CallManager adds is available in an administrator-accessible file. In the installation directory of CallManager is a subdirectory called dialPlan. (The CallManager service parameter DialPlanPath tells CallManager where to look for the numbering plan file.) When CallManager initializes, it looks in this subdirectory for information about the supported numbering plans. When you configure an @ pattern from the Route Pattern Configuration or Translation Pattern Configuration pages, you are instructing CallManager to expand the @ wildcard according to one of the files in this subdirectory.
You can modify how CallManager interprets the @ pattern by modifying the dial plan file; however, Cisco TAC does not support such modifications of the dial plan file. Furthermore, while changing the file does affect how CallManager expands the @ pattern, it does not affect how CallManager Administration presents other dial plan-related settings, such as digit discarding instructions or route filters. Rather, the administration pages derive this information from tables that exist in the CallManager database schema. Nevertheless, examining the files in the dialPlans subdirectory, you can see exactly how CallManager interprets the @ pattern on a dial-plan-by-dial-plan basis.
The file is a little more complex than just a list of route patterns, however, because for CallManager to correctly apply digit discarding instructions and route filters, you need to tell it what substrings of a given number are meaningful for routing purposes. For example, the seven-digit North American numbering plan route pattern [2-9]XX XXXX contains two meaningful substrings, an office code and a subscriber.
As described in the section "Tags," these meaningful substrings are called tags. The tags defined for a given numbering plan dictate which tags are available on the Route Filter Configuration page and which parts of a dialed number can be discarded using digit discarding instructions.
The following is a short excerpt from the NANP file, which defines the North American numbering plan, that describes a long distance number preceded by a request for a particular long distance carrier:
# 101 XXXX 1 [2-9]XX [2-9]XX [2-9]XX P: 101 TRANSIT-NETWORK-ESCAPE P: XXXX TRANSIT-NETWORK P: 1 LONG-DISTANCE-DIRECT-DIAL P: [2-9]XX AREA-CODE P: [2-9]XX OFFICE-CODE P: XXXX SUBSCRIBER T: N
Each route pattern in a numbering plan is represented as several lines of text followed by a blank line. The first character on each line of text defines one of five types of records:
International Dial Plans
Cisco makes dial plans for other countries available at Cisco.com (http://www.cisco.com/pcgibin/tablebuild.pl/IDP). Users with a Cisco Service Agreement can access these dial plans and install them on CallManager. Following the link grants you access to a tool from which you can download an installer (.exe) for currently supported dial plan files.
Currently, Cisco provides dial plans for Japan, Netherlands, Portugal, Singapore, Australia, Russia, New Zealand, Great Britain, Belgium, and Greece.
Cisco CallManager Architecture
Manageability and Monitoring
Call Detail Records
Appendix A. Feature List
Appendix B. Cisco Integrated Solutions
Appendix C. Protocol Details