Troubleshooting guide
3-75
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations
Regular Operations
*/
Provisioning a Dial Plan
You can provision dial plans on the Cisco PGW 2200 Softswitch by using the following commands. For
more information on provisioning and maintaining dial plans, see Cisco PGW 2200 Softswitch Release
9.8 Dial Plan Guide.
• numan-add—Adds an element to a dial plan.
• numan-dlt—Deletes an element from a dial plan.
• numan-ed—Edits an existing element in a dial plan.
• numan-rtrv—Displays information pertaining to an element or all elements in a dial plan.
Note You can verify dial plans using the translation verification viewer on the Cisco MGC toolbar. For
information on using the translation verification viewer, see the “Verifying a Dial Plan Translation”
section on page 3-135.
Importing Provisioning Data
You can import provisioning data files (created using the prov-exp MML command) and execute the
MML commands that are contained in those files in batch mode to copy the setup from another system,
or return a system to a baseline configuration. See the “Exporting Provisioning Data” section on
page 3-76 for more information on exporting provisioning data.
To import the provisioning data files and execute the MML commands in batch mode, log in to the active
Cisco PGW 2200 Softswitch, and enter the following UNIX command:
mml -b
export_directory_path
/
filename
Where:
• export_directory_path—Directory path to the location of the exported provisioning data files.
• filename—Name of the provisioning data file you want to import.
The provisioning data files must be provisioned in the following order:
1. config.mml—Contains core configuration data (signaling services, SS7 nodes)
2. export_trunks.dat—Created only when trunks are configured on your system
3. export_trkgrp.dat—Created only when trunk groups are configured on your system)
4. routing.mml—Contains routing plans
5. custGrpID.mml—One of these files is created for each existing dial plan. The file is named with the
associated customer group ID number.
For example, to import the provisioning data that is stored in the config.mml file, which is located in the
/opt/ CiscoMGC/etc/cust_specific/saved_config directory, enter the following command:
mml -b /opt/CiscoMGC/etc/cust_specific/saved_config/config.mml