Cisco CallManager Dialed Number Analyzer Guide, Software Release 3.0 - Analyzing Cisco CallManager Dial Plan Configuration [Cisco Unified Communications Manager (CallManager)]

Table Of Contents

Analyzing Cisco CallManager Dial Plan Configuration

Database Synchronization

Disabling Database Synchronization

Simple Analysis by Using the Analyzer Window

Analysis by Using Phones

Finding a Phone

Choosing a Phone Line

Performing Analysis by Using Phones

Analysis by Using Gateways

Finding a Gateway

Choosing Gateway Endpoints and Entering Analysis Input

Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

Choosing Non-IOS MGCP Gateways

Choosing Cisco IOS H.323 Gateways

Choosing Analog Access Gateways

Choosing Cisco VG248 Analog Phone Gateways

Performing Analysis by Using Gateways

Analysis by Using Trunks

Finding a Trunk

Choosing a Trunk

Performing Analysis by Using Trunks

Understanding Analysis Output

Analysis Results Examples

Example 1

Example 2

Example 3

Example 4

Example 5

Results Summary

Call Flow Details

Translation Pattern

Route Pattern

Hunt Pilot

Directory Number

Device Information

Alternate Matches

Dumping Digit Discard Instructions and Dialing Patterns

Viewing Dialed Number Analyzer Output Files

Viewing Trace Configuration Files

Analyzing Cisco CallManager Dial Plan Configuration

Dialed Number Analyzer allows analysis of a configured Cisco CallManager dial plan and provides details on the call flow of dialed digits. In the predeployment stage, you can use the tool to identify problems in a complex dial plan and fine tune the dial plan. You can also use the tool, after the dial plan is deployed, to identify real-time problems in the call flow of dialed digits.

When you use Dialed Number Analyzer to analyze dial plans for a cluster of Cisco CallManager systems and numerous devices, you may be able to access the windows and enter data for analysis quickly. However, you may not be able to see any results when you perform the analysis. The following message displays:

Check if the DNA service is running. If the DNA service is running, then Dialed Number Analyzer is still initializing. Wait for a few minutes for Dialed Number Analyzer to initialize and try again.
This message displays because Dialed Number Analyzer is registering the devices in the Cisco CallManager system. Clear the message and wait for a few minutes before you perform analysis.

Use the following topics to understand how to use the Service Control window and how to use Dialed Number Analyzer to analyze a Cisco CallManager dial plan configuration:

•Database Synchronization

•Simple Analysis by Using the Analyzer Window

•Analysis by Using Phones

•Analysis by Using Gateways

•Analysis by Using Trunks

•Understanding Analysis Output

•Dumping Digit Discard Instructions and Dialing Patterns

•Viewing Dialed Number Analyzer Output Files

•Viewing Trace Configuration Files

Database Synchronization

Dialed Number Analyzer replicates and uses the Cisco CallManager database configuration to analyze calls in a dial plan. For this reason, make sure that Dialed Number Analyzer is in sync with the Cisco CallManager database before you use the tool to perform any analysis. When changes are made to the Cisco CallManager database, ensure that Dialed Number Analyzer reflects the changes to facilitate analysis by using current data. Examples of database changes include addition or deletion of devices, modification of route patterns, modification of gateway configuration settings, and so on.

You can enable Dialed Number Analyzer to receive database change notifications from Cisco CallManager whenever database changes are made by using Cisco CallManager Administration. Use the following steps to enable database change notifications to Dialed Number Analyzer.

Procedure

Step 1 In Dialed Number Analyzer, choose Service > Control Center.

The Control Center window displays. Database Synchronization displays under the Service Name-Database column.

Step 2 By default, the system enables Database Synchronization when Dialed Number Analyzer is installed. To keep database synchronization enabled, do not modify this setting.

Note Every time that you disable and enable database synchronization again, stop and start the Dialed Number Analyzer service to ensure that Dialed Number Analyzer is in sync with the Cisco CallManager database. For instructions on starting the Dialed Number Analyzer service, see "Starting Dialed Number Analyzer Service" section.

Related Topics

•Disabling Database Synchronization

•Starting Dialed Number Analyzer Service

Disabling Database Synchronization

You can choose not to notify Dialed Number Analyzer of changes that are made to the Cisco CallManager database. Use the following steps to disable notification of database changes.

Procedure

Step 1 Choose Service > Control Center.

The Control Center window displays. Database Synchronization displays under the Service Name-Database column.

Step 2 Click Disable in the corresponding Action column.

Related Topic

•Database Synchronization

Simple Analysis by Using the Analyzer Window

Simple analysis involves entering calling party and called party digits in Dialed Number Analyzer and choosing a calling search space for the analysis. Dialed Number Analyzer uses this calling search space and analyzes the dialed digits. You need not choose specific devices or provide any other input. Dialed Number Analyzer allows analysis of a route pattern, translation pattern, phone DN, or CTI Route Point.

Use this procedure only when you want to perform a quick analysis by entering dialed digits, selecting a calling search space, and entering the time and date of the calling party for analysis. Analysis results that are obtained by using this procedure do not display details, like partitions, AAR calling search space details and so on in the Calling Party Information section. Because you do not choose a specific device to dial digits, instead you enter a calling party number that is not associated with any device that is configured in the Cisco CallManager system.

You can enter numerals, the symbols # and *, and the alphabet letters A, a, B, b, C, c, D, and d in the Dialed Digits and Calling Party fields for analysis.

Access Dialed Number Analyzer and use the following procedure to perform a simple analysis.

Procedure

Step 1 Choose Analysis > Analyzer.

The Analyzer window displays. Enter input for the analyzer in this window.

Step 2 In the Calling Party field, enter the calling party digits. You do not have to Associate this number with a device.

By default, 1000 displays in this field.

Step 3 In the Dialed Digits field, enter the digits that the calling party is to call.

Step 4 From the Calling Search Space drop-down list box, choose the calling search space that is to be used to analyze the dialed digits. A calling search space comprises a collection of partitions that are searched to determine how a dialed number should be routed.

Step 5 From the Device Time Zone drop-down box, choose the time zone of the calling party. The time zone that represents the time zone information from the operating system of the server where Cisco CallManager is installed displays by default.

Note The system uses this time zone for analysis only when the partition time zone setting is configured to Originating Device, in the Partition Configuration window in Cisco CallManager.

Step 6 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled, leave the default settings.

The local time and date, representing the time and date information from the operating system of the server where Cisco CallManager is installed displays by default.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 7 Click Do Analysis to start the analysis or click Clear to clear the fields and to reenter data.

When you click Do Analysis, Dialed Number Analyzer analyzes the dialed digits and displays the results in a new window that is called Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use.

To save the results, use Steps 8, 9, 10, and 11; otherwise skip to Step 12.

Step 8 To save the results, in the upper, right corner of the Analyzer Output window, click the Save Result link.

The File Download dialog displays.

Step 9 Click Save.

The Save As dialog displays. Browse to a location on your PC where you want to save the file.

Step 10 Click Save.

The system saves the results in an XML file on your PC. The saved file has the following naming convention:

DialedNumberAnalyzerOutput_<dialeddigits>.xml

where <dialeddigits> specifies the digits that are entered in the Dialed Digits field.

Step 11 In the Download Complete dialog box, click Close to complete the Save As procedure.

Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section.

Step 12 Close the Analyzer Output window.

Related Topics

•Database Synchronization

•Analysis by Using Phones

•Analysis by Using Gateways

•Analysis by Using Trunks

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Analysis by Using Phones

Dialed Number Analyzer provides a Phones window where you can find and list phones by device name, description, directory number, calling search space device pool, device type, and call pickup group. You can find a phone and choose it as a calling device for the analysis that you want to perform. You can further choose a configured phone line (directory number) and use it as a calling party number.

Use the following topics to choose a phone and a phone line and to carry out analysis by using that phone line:

•Finding a Phone

•Choosing a Phone Line

•Performing Analysis by Using Phones

Related Topics

•Simple Analysis by Using the Analyzer Window

•Analysis by Using Gateways

•Analysis by Using Trunks

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Finding a Phone

Dialed Number Analyzer allows you to locate a phone that you can use to analyze dialed digits from that phone. Use the following procedure to locate a phone.

Procedure

Step 1 Choose Analysis > Phones.

The Find and List Phones window displays.

Step 2 From the first Find Phones where drop-down list box, choose one of the following criteria:

•Device Name

•Description

•Directory Number

•Calling Search Space

•Device Pool

•Device Type

•Call Pickup Group

Note The criterion that you choose in this drop-down list box specifies how the list of phones displays. For example, if you choose Device Name, the Device Name column will display as the left column of the results list.

Note If you choose Directory Number, Calling Search Space, or Call Pickup Group, the options that are available in the database display.

Step 3 From the second Find Phones where drop-down list box, choose one of the following criteria:

•begins with

•contains

•ends with

•is exactly

•is not empty

•is empty

Note If you choose Calling Search Space, Device Pool, Device Type, or Call Pickup Group in the first field, you can choose a value from the drop-down list for this field.

Step 4 Specify how many items per window to display.

Step 5 Specify the appropriate search text, if applicable, and click Find.

Tip To find all phones, click Find without entering any search text or choose Device Name in the first Find Phones where drop-down list box and "is not empty" in the second Find Phones where drop-down list box.

A list of discovered phones that match the criteria displays.

This window also lists the total number of phones and windows in this window.

Step 6 To view the next set of discovered phones, click Next.

Step 7 From the list of records, click the links that are available for the record that matches your search criteria.

The Phone Line Selection window displays.

Step 8 Continue with the procedure that is described in "Choosing a Phone Line" section.

Related Topics

•Choosing a Phone Line

•Performing Analysis by Using Phones

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Choosing a Phone Line

After you have identified a phone to use for analysis, you need to choose a phone line that is configured in the system. Use the following procedure to choose a phone line as the calling party.

Procedure

Step 1 Find the phone that you want to use as a calling party device by using the procedure described in the "Finding a Phone" section.

The Phone Line Selection window displays. The phone ID number, registration details, and IP address of the server on which the phone is registered display.

Under the Phone Configuration column, information on the device displays. The address of the machine, the device pool to which the phone belongs, calling search space, AAR calling search space, and Media Resource Group List details display.

Step 2 From the list of records, choose the phone line by clicking the Line radio button for the phone line that you require.

Note In the upper, right corner or lower, right corner of the window, click the Back to Find/List Phones link to return to the Find and List Phones window.

Step 3 Continue with the procedure in "Performing Analysis by Using Phones" section.

Related Topics

•Finding a Phone

•Performing Analysis by Using Phones

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Performing Analysis by Using Phones

After you have identified a phone and chosen a phone line, you can enter dialed digits for analysis. This section describes how to perform analysis by using the chosen phone line.

Procedure

Step 1 Find the phone that you want to use as a calling party device by using the procedure in the "Finding a Phone" section. The Phone Line Selection window displays.

Note The time zone that is configured for the phone in Cisco CallManager displays in the Device Time Zone field.

Step 2 Choose a phone line by using the procedure in the "Choosing a Phone Line" section.

Step 3 In the Dialed Digits field, enter the digits that are to be dialed from the chosen phone line.

Step 4 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled, leave the default settings.

The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 5 Click Do Analysis.

Dialed Number Analyzer chooses the Calling Search Space of the chosen phone line and device for the analysis. The results display in a new window that is called the Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use.

To save the results, use Steps 6, 7, 8, and 9; otherwise skip to Step 10.

Step 6 To save the results, in the upper, right corner of the window, click the Save Result link.

The File Download dialog displays.

Step 7 Click Save.

The Save As dialog displays. Browse to a location on your PC where you want to save the file.

Step 8 Click Save.

The results get saved in an XML file on your PC. The saved file has the following naming convention:

DialedNumberAnalyzerOutput_<dialeddigits>.xml

where <dialeddigits> specifies the dialed digits that are entered in the Dialed Digits field.

Step 9 Click Close in the Download Complete dialog box to complete the Save As procedure.

Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section.

Step 10 Close the Analyzer Output window.

Note You can use the Analyzer Output window to enter new data in the fields and perform another analysis by using the steps in the "Analysis by Using Phones" section.

Related Topics

•Finding a Phone

•Choosing a Phone Line

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Analysis by Using Gateways

Dialed Number Analyzer allows you to find and list gateways through which Cisco CallManager receives inbound calls. From the list of gateways, you can choose gateway endpoints to dial digits and analyze the call flow of inbound calls to a Cisco CallManager system. You can choose gateway endpoints that are configured in the Cisco CallManager system.

Use the following topics to find gateways, choose gateway endpoints, enter dialed digits, and perform analysis:

•Finding a Gateway

•Choosing Gateway Endpoints and Entering Analysis Input

•Performing Analysis by Using Gateways

Finding a Gateway

You can find and list gateways by device name, description, DN/route pattern, device type, calling search space, route group, and device pool. This section describes the procedure to find gateways.

Procedure

Step 1 Choose Analysis > Gateways.

The Find and List Gateways window displays.

Step 2 From the first Find gateways where drop-down list box, choose one of the following criteria:

•Device Name

•Description

•DN/Route Pattern

•Calling Search Space

•Device Pool

•Route Group

•Device Type

Note The criterion that you choose in this drop-down list box specifies how the list of gateways displays. For example, if you choose Device Name, the Device Name column will display as the left column of the results list.

Note If you choose DN/Route Pattern, Calling Search Space, or Route Group, the options that are available in the database display.

Step 3 From the second Find gateways where drop-down list box, choose one of the following criteria:

•begins with

•contains

•ends with

•is exactly

•is not empty

•is empty

Note If you choose Calling Search Space, Device Pool, Route Group, or Device Type in the first field, you can choose a value from the drop-down list for this field.

Step 4 Specify how many items per window to display.

Step 5 Specify whether endpoints of gateways must be shown or hidden.

Step 6 Specify the appropriate search text, if applicable, and click Find.

Tip To find all gateways, click Find without entering any search text or choose Device Name in the first Find gateways where drop-down list box and "is not empty" in the second Find gateways where drop-down list box.

A list of gateways that matches the criteria displays. The information that displays differs for different gateway models.

This window also lists the total number of devices and windows.

Step 7 To view the next set of discovered gateways, click Next.

Related Topics

•Choosing Gateway Endpoints and Entering Analysis Input

•Performing Analysis by Using Gateways

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Choosing Gateway Endpoints and Entering Analysis Input

After you find gateways that match your search criteria, you need to choose gateway endpoints and enter calling and called party information. Use the following steps to choose gateway endpoints.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

Step 2 From the list of records that displays in the Find and List Gateways window, choose a gateway. Choose from the following types of gateways:

•Cisco IOS MGCP Gateway

•Non-IOS MGCP Gateway

•Cisco IOS H.323 Gateway

•Analog Access Gateway

•Cisco VG248 Analog Phone Gateway

•Cisco IOS SCCP Gateway

Depending on the type of gateway, different information displays.

Use the following topics to choose gateway endpoints for each gateway type:

•Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

•Choosing Non-IOS MGCP Gateways

•Choosing Cisco IOS H.323 Gateways

•Choosing Analog Access Gateways

•Choosing Cisco VG248 Analog Phone Gateways

Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

After you find gateways that match your search criteria, you can choose Cisco IOS MGCP gateway endpoints and Cisco IOS SCCP Gateways. The following list comprises Cisco IOS MGCP gateways:

•Cisco Voice Gateway 200 (VG200)

•Cisco IOS 269X, 26XX, 364X, 366X, 3725, 3745 gateways

•Cisco Catalyst 4000 Access Gateway Module

•Cisco Catalyst 4224 Voice Gateway Switch

•Communication Media Module

•Cisco IAD2400

•Cisco ICS77XX-ASI160, Cisco ICS77XX-ASI81, Cisco ICS77XX-MRP2xx, Cisco ICS77XX-MRP3-16FXS, Cisco ICS77XX-MRP3-8FXO-M1, Cisco ICS77XX-MRP3-8FXS, Cisco ICS77XX-MRP3xx gateways

Use the following steps to choose Cisco IOS MGCP/IOS SCCP gateway endpoints for analysis.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

You can use two ways to access Cisco IOS MGCP/IOS SCCP gateway endpoints. You can directly access the Endpoint Identifiers from the Gateway Information window, or you can first see a list of all the configured endpoints in a new window and then choose one of them.

Use one of the following procedures.

Procedure 1

•From the list of records that displays in the Find and List Gateways window, click the gateway that you want to use.

–The Gateway Information window displays and lists the installed Voice Interface Cards and Endpoint Identifiers for each card. The endpoint identifiers represent configured ports for the chosen devices.

–From the list of endpoint identifiers, click the required endpoint. The appropriate window displays and shows gateway information and port information.

Note The time zone that is configured for the gateway in Cisco CallManager displays in the Device Time Zone field.

–In the Calling Party field, the calling party number that is configured for this endpoint displays.

–In the Dialed Digits field, enter the digits to be dialed.

–Choose the time zone, date, and time settings for analysis, only if Time of Day routing is enabled in Cisco CallManager. If not, leave the default settings.

Note The local time and date, that represents the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time.

From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

–Click Do Analysis to analyze the call flow for the dialed digits.

–Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure.

Procedure 2

•From the list of records that displays in the Find and List Gateways window, click the See Endpoints link in the record that you want to use.

The endpoints display in a new window. You can choose BRI and analog endpoints for analysis.

–From the list of endpoints in the new window, click the record that you want to use. The Gateway Information window displays and shows Gateway Information and Port Information.

Note The time zone that is configured for the endpoint in Cisco CallManager displays in the Device Time Zone field.

–In the Calling Party field, the calling party number that is configured for this endpoint displays.

–In the Dialed Digits field, enter the digits to be dialed.

–If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time.

From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

–Click Do Analysis to analyze the call flow for the dialed digits.

Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure.

Note Gateways include one or more configured ports with multiple endpoints. All ports for the chosen gateway display in the left frame of the Gateway Information window. Click another endpoint to go to that endpoint Gateway Information window.

Note In the upper, right corner or the lower, right corner of the Gateway Information window, click Back to main Gateway Information link to return to the Gateway Information window or Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window.

Related Topics

•Choosing Non-IOS MGCP Gateways

•Choosing Cisco IOS H.323 Gateways

•Choosing Analog Access Gateways

•Choosing Cisco VG248 Analog Phone Gateways

•Performing Analysis by Using Gateways

•Viewing Dialed Number Analyzer Output Files

Choosing Non-IOS MGCP Gateways

After you find gateways that match your search criteria, you can choose Non-IOS MGCP gateway endpoints. The following list comprises Non-IOS MGCP gateways:

•Cisco Catalyst 6000 E1 VoIP Gateway

•Cisco Catalyst 6000 T1 VoIP Gateway

•Cisco DT-24+ or DE-30+ Digital Access Trunk Gateway

Use the following procedure to choose Non-IOS MGCP gateway endpoints for analysis.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

Step 2 From the list of records that displays in the Find and List Gateways window, click the Non-IOS MGCP gateway that you want to use.

The Gateway Information window displays and shows Device Information and Call Routing Information.

Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field.

Step 3 In the Calling Party field, the calling party number that is configured for this endpoint displays.

Step 4 In the Dialed Digits field, enter the digits to be dialed.

Step 5 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 6 Click Do Analysis to analyze the call flow for the dialed digits.

Step 7 Follow the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure.

Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window.

Related Topics

•Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

•Choosing Cisco IOS H.323 Gateways

•Choosing Analog Access Gateways

•Choosing Cisco VG248 Analog Phone Gateways

•Performing Analysis by Using Gateways

•Viewing Dialed Number Analyzer Output Files

Choosing Cisco IOS H.323 Gateways

After you find a list of gateways that match your search criteria, you can choose Cisco IOS H.323 gateway endpoints. Use the following procedure to choose Cisco IOS H.323 gateway endpoints for analysis.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

Step 2 From the list of records that displays in the Find and List Gateways window, click the Cisco IOS H.323 gateway that you want to use. The Gateway Information window displays and shows Device Information and Call Routing Information.

Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field.

Step 3 In the Calling Party field, the calling party number that is configured for this endpoint displays.

Step 4 In the Dialed Digits field, enter the digits to be dialed.

Step 5 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 6 Click Do Analysis to analyze the call flow for the dialed digits.

Step 7 Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure.

Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window.

Related Topics

•Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

•Choosing Non-IOS MGCP Gateways

•Choosing Analog Access Gateways

•Choosing Cisco VG248 Analog Phone Gateways

•Performing Analysis by Using Gateways

•Viewing Dialed Number Analyzer Output Files

Choosing Analog Access Gateways

After you find a list of gateways that match your search criteria, you can choose Analog Access gateway endpoints. The following list comprises Analog Access gateways:

•Cisco Catalyst 6000 24 Port FXS Gateway

•Analog Access AS-2, AS-4, AS-8, AT-2, AT-4, AT-8

Use the following procedure to choose Analog Access gateway endpoints for analysis.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

Step 2 From the list of records that displays in the Find and List Gateways window, click the Analog Access gateway that you want to use.

The Gateway Information window displays and shows all the ports that are configured for the gateway in the left frame.

Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field.

Step 3 Click the port that you require to make a call.

The Gateway Information window displays.

Step 4 In the Calling Party field, the calling party number that is configured for this endpoint displays.

Step 5 In the Dialed Digits field, enter the digits to be dialed.

Step 6 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 7 Click Do Analysis to analyze the call flow for the dialed digits.

Step 8 Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure.

Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window.

Related Topics

•Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

•Choosing Non-IOS MGCP Gateways

•Choosing Cisco IOS H.323 Gateways

•Choosing Cisco VG248 Analog Phone Gateways

•Performing Analysis by Using Gateways

•Viewing Dialed Number Analyzer Output Files

Choosing Cisco VG248 Analog Phone Gateways

After you find a list of gateways that matches your search criteria, you can choose Cisco VG248 Analog Phone gateway endpoints that are applicable to a Cisco VG248 Analog Phone gateway. Use the following procedure to choose Cisco VG248 Analog Phone gateway endpoints for analysis.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

Step 2 From the list of records that displays in the Find and List Gateways window, click the gateway that you want to use.

The Gateway Information window displays and shows all ports that are configured for the selected gateway.

Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field.

Step 3 Choose and click the port that you require.

If you click a port that is not configured, a message displays to inform you that the port is not configured.

If you choose a configured port, the Phone Line Selection window displays.

Step 4 From the list of records, click the Line radio button for the phone line that you require.

Step 5 In the Dialed Digits field, enter the digits to be dialed.

Step 6 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 7 Click Do Analysis to analyze the call flow for the dialed digits.

Step 8 Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure.

Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window.

Related Topics

•Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

•Choosing Non-IOS MGCP Gateways

•Choosing Cisco IOS H.323 Gateways

•Choosing Analog Access Gateways

•Performing Analysis by Using Gateways

•Viewing Dialed Number Analyzer Output Files

Performing Analysis by Using Gateways

After you have chosen a gateway endpoint and entered input for analysis, you can analyze the dialed digits. Use the following procedure to do the analysis.

Procedure

Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section.

Step 2 From the Find and List Gateways window, choose gateway endpoints. In the Gateway Information window, enter calling party or called party information by using the procedures in the following sections for different types of gateways:

•Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways

•Choosing Non-IOS MGCP Gateways

•Choosing Cisco IOS H.323 Gateways

•Choosing Analog Access Gateways

•Choosing Cisco VG248 Analog Phone Gateways

Step 3 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 4 Click Do Analysis.

Dialed Number Analyzer uses the Calling Search Space that is specified for the chosen endpoint and analyzes the dialed digits. The results display in a new window called the Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use.

To save the results, use Steps 5, 6, 7 and 8; otherwise skip to Step 9.

Step 5 To save the result, in the upper, right corner of the window, click the Save Result link.

The File Download dialog displays.

Step 6 Click Save.

The Save As dialog displays. Browse to a location on your PC where you want to save the file.

Step 7 Click Save.

The result gets saved as an XML file on your PC. The saved file has the following naming convention:

DialedNumberAnalyzerOutput_<dialeddigits>.xml

where <dialeddigits> specifies the dialed digits that are entered in the Dialed Digits field.

Step 8 In the Download Complete dialog box, click Close to complete the Save As procedure.

Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section.

Step 9 Close the Analyzer Output window.

Related Topics

•Finding a Gateway

•Choosing Gateway Endpoints and Entering Analysis Input

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Analysis by Using Trunks

Dialed Number Analyzer provides a Trunks window where you can find and list trunks through which inbound dialed digits can be analyzed. Use the following topics to find and choose a trunk and analyze dialed digits:

•Finding a Trunk

•Choosing a Trunk

•Performing Analysis by Using Trunks

Finding a Trunk

You can find and list trunks by device name, description, calling search space, route pattern, device pool, route group, and device type. This section describes the procedure to find trunks.

Procedure

Step 1 Choose Analysis > Trunks.

The Find and List Trunks window displays.

Step 2 From the first Find trunks where drop-down list box, choose one of the following criteria:

•Device Name

•Description

•Calling Search Space

•Route Pattern

•Device Pool

•Route Group

•Device Type

Note The criterion that you choose in this drop-down list box specifies how the list of gateways display. For example, if you choose Device Name, the Device Name column will display as the left column of the results list.

Note If you choose Route Pattern, Calling Search Space, or Route Group, the options that are available in the database display.

Step 3 From the second Find trunks where drop-down list box, choose one of the following criteria:

•begins with

•contains

•ends with

•is exactly

•is not empty

•is empty

Note If you choose Calling Search Space, Device Pool, Route Group, or Device Type in the first field, you can choose a value from the drop-down list for this field.

Step 4 Specify how many items per window to display.

Step 5 Specify the appropriate search text, if applicable, and click Find.

Tip To find all trunks, click Find without entering any search text or choose Device Name in the first Find trunks where drop-down list box and "is not empty" in the second Find trunks where drop-down list box.

A list of trunks that match the search criteria displays.

This window also lists the total number of records in this window.

Step 6 To view the next set of discovered trunks, click Next.

Related Topics

•Choosing a Trunk

•Performing Analysis by Using Trunks

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Choosing a Trunk

After you find the trunks that you require, you need to choose a trunk. Use the following procedure to choose a trunk. You can perform analysis for SIP trunks.

Procedure

Step 1 Find the trunk that you want to use for analysis by using the procedure in the "Finding a Trunk" section.

The Find and List Trunks window displays and shows trunk information.

Step 2 From the list of records, choose a trunk by clicking the required record.

The Trunk Information window displays.

Related Topics

•Finding a Trunk

•Performing Analysis by Using Trunks

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Performing Analysis by Using Trunks

After you have identified and chosen a trunk, you need to enter input for analysis. Use the following procedure to enter input and perform analysis.

Procedure

Step 1 Find the trunk that you require by using the procedure in the "Finding a Trunk" section.

Step 2 From a list of discovered trunks, choose the trunk that you require by using the steps in the "Choosing a Trunk" section.

The Trunk Information window displays. Device and Call Routing information for the chosen trunk displays.

Note The time zone that is configured for the trunk in Cisco CallManager displays in the Device Time Zone field.

Step 3 In the Calling Party field, enter the calling party number.

Step 4 In the Dialed Digits field, enter the digits to be dialed.

Step 5 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings.

Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the default Cisco CallManager system time.

•From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default.

•From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis.

•From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis.

Step 6 Click Do Analysis.

Dialed Number Analyzer uses the Calling Search Space that is specified for the trunk and analyzes the dialed digits. The results display in a new window that is called the Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use.

To save the results, use Steps 7, 8, 9, and 10; otherwise, skip to Step 11.

Step 7 To save the result, in the upper, right corner of the window, click the Save Result link.

The File Download dialog displays.

Step 8 Click Save.

The Save As dialog displays. Browse to a location on your PC where you want to save the file.

Step 9 Click Save.

The result gets saved as an XML file on your PC. The saved file has the following naming convention:

DialedNumberAnalyzerOutput_<dialeddigits>.xml

where <dialeddigits> specifies the dialed digits that are entered in the Dialed Digits field.

Step 10 Click Close in the Download Complete dialog box to complete the Save As procedure.

Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section.

Step 11 Close the Analyzer Output window.

Related Topics

•Finding a Trunk

•Choosing a Trunk

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Understanding Analysis Output

The results of analysis that you perform contain information on the dialed digits call flow. This section provides two examples of analysis results that were obtained by using Dialed Number Analyzer. Each example shows results that were obtained by using different types of inputs and Cisco CallManager configuration data. This section also describes each value in the analysis output.

Three sections provide the description of the results: Results Summary, Call Flow, and Alternate Matches. Use the following topics to understand the information in the analysis output:

•Analysis Results Examples

•Results Summary

•Call Flow Details

•Alternate Matches

Related Topics

•Simple Analysis by Using the Analyzer Window

•Analysis by Using Phones

•Analysis by Using Gateways

•Analysis by Using Trunks

•Viewing Dialed Number Analyzer Output Files

•Analysis Results Examples

Analysis Results Examples

This section provides three examples to help you understand the results that you could obtain with different inputs by using Dialed Number Analyzer. The Results Summary, Call Flow, and Alternate Matches sections describe all the values that could display in analysis results. The sample results may include only values that result from the type of input that is provided to Dialed Number Analyzer.

Example 1

This example assumes the following setup in Cisco CallManager:

Phone—1360064 in partition 'DallasPartition'

Line Calling Search Space—ALL (ALL CSS has DallasPartition and SJPartition)

Route Filter—RF-SJ (LONG-DISTANCE-DIRECT-DIAL EXISTS AND AREA-CODE == 408). This route pattern selects RouteList 'RL1'. RL1 uses RG1, RG2, AND RG3.

RG1 configuration includes an Inter Cluster Trunk as 10.77.31.206, with route group level calling and called party transformations. RG2 configuration includes an Inter Cluster Trunk 10.77.31.231, with QSIG tunneled protocol. RG3 configuration includes one CiscoAT Gateway and one CiscoAS Gateway.

Route Pattern—9.@ in partition 'SJPartition', where:

•Offnet Pattern (Outside Dial Tone) is checked

•Require Forced Authorization Code is checked

•Require Client Matter Code is checked

•Authorization Level = 155

Associate the route pattern with the RL1 route list and route filter RF-SJ.

Configure the Inter Cluster Trunk 10.77.31.206 as follows:

•Tunneled Protocol—QSIG.

•Call Classification—Use System Default.

•Inbound Fast Start—Disabled.

•Outbound Fast Start—Enabled.

•Codec For Outbound FastStart—G711 u-law 64k.

Configure the Inter Cluster Trunk 10.77.31.231 as follows:

•Tunneled Protocol—QSIG.

•Call Classification—Use System Default.

•Inbound Fast Start—Disabled.

•Outbound Fast Start—Disabled.

Use the following procedure to run this example:

Procedure

Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer.

Step 2 In the Analyzer window, enter 1360064 in the Calling Party field.

Step 3 In the Dialed Digits field, enter 914089027872.

Step 4 From the Calling Search Space drop-down list box, choose ALL.

Step 5 Leave the default values in the Device Time Zone field, Cisco CallManager system Time Zone, Date, and Time fields.

Step 6 Click Do Analysis.

The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information.

Step 7 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window.

Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled.

See Example 4-1 for the results.

Example 4-1 Analysis Results for Example 1
Results Summary 
Calling Party Information 
Calling Party = 1360064 
Partition = 
Device CSS = 
Line CSS = ALL 
AAR Group Name = 
AARCSS = 
Dialed Digits = 914089027872 
Match Result = RouteThisPattern 
Matched Pattern Information 
Pattern = 9.@ 
Partition = SJPartition 
Time Schedule = 
Called Party Number = 914089027872 
Time Zone = (GMT+05:30) Bombay, Calcutta, Madras, New Delhi, Colombo 
End Device = RL1 
CallClassification = OffNet 
InterDigit Timeout = NO 
Provide Outside Dial Tone) 
PlayedAfter = 9 
Call Flow 
Route Pattern :Pattern= 9.@ 
Positional Match List = 9:1:408:902:7872 
DialPlan = North American Numbering Plan 
Route Filter 
   Filter Name = RF-SJ 
   Filter Clause = (LONG-DISTANCE-DIRECT-DIAL EXISTS AND AREA-CODE == 408) 
Require Forced Authorization Code = Yes 
Authorization Level = 155 
Require Client Matter Code = Yes 
Network Location = OffNet 
PreTransform Calling Party Number = 1360064 
PreTransform Called Party Number = 914089027872 
Calling Party Transformations 
   External Phone Number Mask = NO 
   Calling Party Mask = 
   Prefix = 
   CallingLineId Presentation = Default 
   CallingName Presentation = Default 
   Calling Party Number = 1360064 
ConnectedParty Transformations 
   ConnectedLineId Presentation = Default 
   ConnectedName Presentation = Default 
Called Party Transformations 
   Called Party Mask = 
   Discard Digits Instruction = 
   Prefix = 
   Called Number = 914089027872 
Route List :Route List Name= RL1 
RouteGroup :RouteGroup Name= RG1 
   PreTransform Calling Party Number = 1360064 
   PreTransform Called Party Number = 914089027872 
   Calling Party Transformations 
      External Phone Number Mask = Default 
      Calling Party Mask = 
      Prefix = 
      Calling Party Number = 1360064 
   Called Party Transformations 
      Called Party Mask = 
      Discard Digits Instructions = 
      Prefix = 
      Called Number = 914089027872 
   Device :Type= InterClusterTrunk-NonGatekeeperControlled 
      End Device Name = 10.77.31.206 
      PortNumber = 0 
      Device Status = UnKnown 
      AAR Group Name = 
      AAR Calling Search Space = 
      AAR Prefix Digits = 
      Inbound Fast Start = Disabled 
      Outbound Fast Start = Enabled 
      Codec For Outbound FastStart = G711 u-law 64K 
      Call Classification = Use System Default 
      Tunneled Protocol = QSIG 
      Calling Party Transformations 
         PreTransform Calling Party Number = 1360064 
         Calling Party Selection = Originator 
         Calling Party Presentation = Default 
         CallerID DN = 
         Calling Party Number = 1360064 
RouteGroup :RouteGroup Name= RG2 
   PreTransform Calling Party Number = 1360064 
   PreTransform Called Party Number = 914089027872 
   Calling Party Transformations 
      External Phone Number Mask = Default 
      Calling Party Mask = 
      Prefix = 
      Calling Party Number = 1360064 
   Called Party Transformations 
      Called Party Mask = 
      Discard Digits Instructions = 
      Prefix = 
      Called Number = 914089027872 
   Device :Type= InterClusterTrunk-NonGatekeeperControlled 
      End Device Name = 10.77.31.231 
      PortNumber = 0 
      Device Status = UnKnown 
      AAR Group Name = 
      AAR Calling Search Space = 
      AAR Prefix Digits = 
      Inbound Fast Start = Disabled 
      Outbound Fast Start = Disabled 
      Call Classification = Use System Default 
      Tunneled Protocol = QSIG 
      Calling Party Transformations 
         PreTransform Calling Party Number = 1360064 
         Calling Party Selection = Originator 
         Calling Party Presentation = Default 
         CallerID DN = 
         Calling Party Number = 1360064 
RouteGroup :RouteGroup Name= RG3 
   PreTransform Calling Party Number = 1360064 
   PreTransform Called Party Number = 914089027872 
   Calling Party Transformations 
      External Phone Number Mask = Default 
      Calling Party Mask = 
      Prefix = 
      Calling Party Number = 1360064 
   Called Party Transformations 
      Called Party Mask = 
      Discard Digits Instructions = 
      Prefix = 
      Called Number = 914089027872 
   Device :Type= CiscoASGateway 
      End Device Name = SAA2433E7636576 
      PortNumber = 0 
      Device Status = UnKnown 
      AAR Group Name = 
      AAR Calling Search Space = 
      AAR Prefix Digits = 
   Device :Type= CiscoATGateway 
      End Device Name = SAA498968343345 
      PortNumber = 0 
      Device Status = UnKnown 
      AAR Group Name = 
      AAR Calling Search Space = 
      AAR Prefix Digits = 
Alternate Matches 
Note: Information Not Available
Example 2

This example assumes the following setup in Cisco CallManager:

Route Pattern—9.@ in partition 'SJPartition'

Route Filter—RF-SJ (LONG-DISTANCE-DIRECT-DIAL EXISTS AND AREA-CODE == 408). This route pattern selects RouteList 'RL1'. RL1 uses RG1.

RG1 configuration includes an Inter Cluster Trunk as 10.77.31.206, with route group level calling and called party transformations. Configure 10.77.31.206 gateway with CSS—ALL. (ALL CSS has DallasPartition and SJPartition)

RG2 configuration includes an Inter Cluster Trunk 10.77.31.231, with QSIG tunneled protocol. RG3 configuration includes one CiscoAT Gateway and one CiscoAS Gateway.

Route Pattern—9.@ in partition 'SJPartition', where:

•Offnet Pattern (Outside Dial Tone) is checked

•Require Forced Authorization Code is checked

•Require Client Matter Code is checked

•Authorization Level = 155

Associate the route pattern with the RL1 route list and route filter RF-SJ.

Configure the Inter Cluster Trunk 10.77.31.206 as follows:

•Tunneled Protocol—QSIG.

•Call Classification—Use System Default.

•InBound Fast Start—Disabled.

•OutBound Fast Start—Enabled.

•Codec For Outbound Fast Start—G711 mu-law 64k.

Configure the Inter Cluster Trunk 10.77.31.231 as follows:

•Tunneled Protocol—QSIG.

•Call Classification—Use System Default.

•InBound Fast Start—Disabled.

•OutBound Fast Start—Disabled.

Configure a phone with DN 254564. The phone's Ignore Presentation Indicators (internal calls only) check box is checked. Translation pattern 972813XXXX exists in partition 'DallasPartition' with Called Party Transformations configured with DN 254564.

Provide Outside dial tone is not checked for the translation pattern.

Use the following procedure to run this example:

Procedure

Step 1 Access Dialed Number Analyzer and choose Analysis > Trunks.

Step 2 Find a list of gateways that are configured by using the procedure in the "Finding a Trunk" section.

Step 3 From the list of records that displays in the Find and List Trunks window, choose gateway 10.77.31.206. The Trunk Information window displays.

Step 4 In the Trunk Information window, enter 9728130064 in the Calling Party field.

Step 5 In the Dialed Digits field, enter 9728135054.

Step 6 Leave the default values in the Time Zone, Date, and Time drop-down list boxes.

Step 7 Click Do Analysis.

The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information.

Step 8 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window.

Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled.

See Example 4-2 for the results.

Example 4-2 Analysis Results for Example 2
Results Summary 
Calling Party Information 
Calling Party = 9728130064 
Partition = 
Device CSS = ALL 
Line CSS = 
AAR Group Name = 
AARCSS = 
Dialed Digits = 9728135054 
Match Result = RouteThisPattern 
Matched Pattern Information 
Pattern = 254564 
Partition = 
Time Schedule = 
Called Party Number = 254564 
Time Zone = 
InterDigit Timeout = NO 
Provide Outside Dial Tone = NO 
Call Flow 
TranslationPattern :Pattern= 972813XXXX 
Positional Match List = 254564 
DialPlan = North American Numbering Plan 
Route Filter 
   Filter Name = 
   Filter Clause = 
PreTransform Calling Party Number = 9728130064 
PreTransform Called Party Number = 9728135054 
Calling Party Transformations 
   External Phone Number Mask = NO 
   Calling Party Mask = 
   Prefix = 
   CallingLineId Presentation = Default 
   CallingName Presentation = Default 
   Calling Party Number = 9728130064 
ConnectedParty Transformations 
   ConnectedLineId Presentation = Default 
   ConnectedName Presentation = Default 
Called Party Transformations 
   Called Party Mask = 254564 
   Discard Digits Instruction = 
   Prefix = 
   Called Number = 254564 
Directory Number :DN= 254564 
Partition = 
Call Classification = OnNet 
Forwarding Information 
   ForwardAll : DN = VoiceMail = No CSS = 
   ForwardBusy 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   ForwardNoAnswer 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   ForwardNoCoverage 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   CFDF : DN = VoiceMail = No CSS = 
   Pickup Group Number = 
Device :Type= Cisco 7960 
Device Status = UnKnown 
Device Name = SEP487698944444 
Ignore Presentation Indicators = Enabled 
Alerting Name = 
AAR Group Name = 
AAR Calling Search Space = 
AAR Prefix Digits = 
Alternate Matches 
Note: Information Not Available
Example 3

This example shows how hunt pilot information displays in the analysis results, if your dial plan configuration includes hunt lists. This sample assumes the following setup in Cisco CallManager:

Hunt pilot—9043.

10 voice mail ports get configured from 90431 through 90440.

Line Group VMLG includes the 10 ports.

Hunt List VMHL includes Line Group VMLG.

Forward Hunt No Answer setup is as follows:

Use Personal Preference is checked.

Destination = 30129.

CSS = None.

Forward Hunt Busy setup is as follows:

Use Personal Preference is checked

Destination = 30139

CSS = None

Maximum Hunt Timer = 5

Use the following procedure to run this example:

Procedure

Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer.

The Analyzer window displays.

Step 2 In the Calling Party field, enter a calling party number (1000 displays by default).

Step 3 In the Dialed Digits field, enter 9043.

Step 4 In the Device Time Zone field, leave the default values.

The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time.

Step 5 In the Time Zone, Date, and Time fields, leave the default settings.

Step 6 Click Do Analysis.

Step 7 The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information.

Step 8 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window.

Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled.

See Example 4-3 for the results. The results section details only the Call Flow section that includes Hunt List information.

Example 4-3 Analysis Results for Example 3
Results Summary 
Calling Party Information 
Calling Party = 1000 
Partition = 
Device CSS = 
Line CSS = 
AAR Group Name = 
AARCSS = 
Dialed Digits = 9043 
Match Result = RouteThisPattern 
Matched Pattern Information 
Pattern = 9043 
Partition = 
Time Schedule = 
Called Party Number = 9043 
Time Zone = 
End Device = VMHL 
Call Classification = OffNet 
InterDigit Timeout = YES 
Provide Outside Dial Tone = NO 
Call Flow 
Hunt Pilot :Pattern= 9043 
Positional Match List = 9043 
DialPlan = North American Numbering Plan 
Route Filter 
   Filter Name = 
   Filter Clause = 
Hunt Forward Settings 
   Forward Hunt No Answer 
      Use Personal Preferences = Yes 
      Destination = 30129 
      Calling Search Space = 
   Forward Hunt Busy 
      Use Personal Preferences = Yes 
      Destination = 30139 
      Calling Search Space = 
   Maximun Hunt Timer = 5 
Network Location = OffNet 
PreTransform Calling Party Number = 1000 
PreTransform Called Party Number = 9043 
Calling Party Transformations 
   External Phone Number Mask = NO 
   Calling Party Mask = 
   Prefix = 
   CallingLineId Presentation = Default 
   CallingName Presentation = Default 
   Calling Party Number = 1000 
ConnectedParty Transformations 
   ConnectedLineId Presentation = Default 
   ConnectedName Presentation = Default 
Called Party Transformations 
   Called Party Mask = 
   Discard Digits Instruction = 
   Prefix = 
   Called Number = 9043 
Hunt List :HuntListName= VMHL 
Line Group :LineGroupName= VMLG 
   Directory Number :DN= 90431 
      Partition = 
      Call Classification = OnNet 
      Device :Type= Cisco Voice Mail Port 
         Device Status = UnKnown 
         Device Name = CiscoUM1-VI1 
         Ignore Presentation Indicators = Disabled 
         Alerting Name = 
         AAR Group Name = 
         AAR Calling Search Space = 
         AAR Prefix Digits = 
   + Directory Number :DN= 90432 
   + Directory Number :DN= 90433 
   + Directory Number :DN= 90434 
   + Directory Number :DN= 90435 
   + Directory Number :DN= 90436 
   + Directory Number :DN= 90437 
   + Directory Number :DN= 90438 
   + Directory Number :DN= 90439 
   + Directory Number :DN= 90440 
Alternate Matches 
Note: Information Not Available 
Note The last section of the preceding sample shows detailed Directory Number information for the first port. Similar information displays for the remaining ports that are configured.

Example 4

This example shows how time-of-day settings information displays in the analysis results, when the time zone settings for a phone is set to a specific time zone in Cisco CallManager Administration. In this example, the analysis uses the time zone, date, and time settings that the Analysis > Analyzer window specifies. This sample assumes the following setup in Cisco CallManager:

Time Period—DNATimePeriod1

Configure DNATimePeriod1 as follows:

•Start Time = 9.00

•End Time = 12.00

•Repeat Every = Year On: Jun 15

Time Schedule—DNATimeSchedule1

Configure DNATimeSchedule1 to DNATimePeriod1

Partition—DNAPartition1

Configure DNAPartition1 to DNATimeSchedule1

DNAPartition1 configuration must be as follows:

•Time Zone = Specific Time Zone, (GMT+5.30) Bombay, Calcutta, Madras, New Delhi, Colombo

Configure DNACSS1 with DNAPartition1.

Phone—Configure an SEP000000036201 with DN 36201

Partition for the SEP000000036201 phone = DNAPartition1

Use the following procedure to run this example:

Procedure

Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer.

The Analyzer window displays.

Step 2 In the Calling Party field, enter a calling party number (1000 displays by default).

Step 3 In the Dialed Digits field, enter 36201.

Step 4 From the Calling Search Space drop-down list, choose DNACSS1.

Step 5 From the Time Zone drop-down list, choose a specific time zone, (GMT+5.30) Bombay, Calcutta, Madras, New Delhi, Colombo.

Step 6 From the Date drop-down list boxes, choose 2004, Jun, and 15 as the Cisco CallManager system date settings.

Step 7 From the Time drop-down list boxes, choose 11:30:0:0 as the Cisco CallManager system time settings.

Step 8 Click Do Analysis.

Step 9 The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information.

Step 10 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window.

Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled.

See Example 4-4 for the results.

Example 4-4 Analysis Results for Example 4
Results Summary 
Calling Party Information 
Calling Party = 1000 
Partition = 
Device CSS = 
Line CSS = DNACSS1 
AAR Group Name = 
AARCSS = 
Dialed Digits = 36201 
Match Result = RouteThisPattern 
Matched Pattern Information 
Pattern = 36201 
Partition = DNAPartition1 
Time Schedule = DNATimeSchedule1 
Called Party Number = 36201 
Time Zone = (GMT+05:30) Bombay, Calcutta, Madras, New Delhi, Colombo 
InterDigit Timeout = NO 
Provide Outside Dial Tone = NO 
Call Flow 
Directory Number :DN= 36201 
Partition = DNAPartition1 
Call Classification = OnNet 
Forwarding Information 
   ForwardAll : DN = VoiceMail = No CSS = 
   ForwardBusy 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   ForwardNoAnswer 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   ForwardNoCoverage 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   CFDF : DN = VoiceMail = No CSS = 
   Pickup Group Number = 
Device :Type= Cisco 7960 
   Device Status = UnKnown 
   Device Name = SEP000000036201 
   Ignore Presentation Indicators = Disabled 
   Alerting Name = 
   AAR Group Name = 
   AAR Calling Search Space = 
   AAR Prefix Digits = 
Alternate Matches 
Note: Information Not Available 
Example 5

This example shows how time-of-day settings information displays when a call is made between two phones in the same time period with the time zone specified as Originating Device. This example assumes the following setup in Cisco CallManager:

Configure a Time Period DNATimePeriod1 as follows:

Start Time=9.00

End Time=12.00

Repeat Every Year=Jun 15

Configure a Time schedule DNATimeSchedule1 as follows:

Time period=DNATimePeriod1

Insert a partition called DNAPartition1.

Configure DNAPartition1 as follows:

•Time Schedule=DNATimeSchedule1

•Time Zone=Originating Device

Insert a Calling Search Space called DNACSS-1. Add the DNAPartition1 partition to this CSS.

Insert a Phone SEP000000036201 and assign a DN, 36201, to it.

Choose DNAPartition1 as the partition for the phone.

Use the following procedure to run this example

Procedure

Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer.

The Analyzer window displays.

Step 2 In the Calling Party field, enter a calling party number (100 0 displays by default).

Step 3 In the Dialed Digits field, enter 36201.

Step 4 From the Calling Search Space drop-down list, choose DNACSS1.

Step 5 From the Device Time Zone drop-down list box, choose Greenwich Mean Time (GMT); Dublin, Edinburgh, London, Lisbon.

Step 6 From the Time Zone drop-down list, choose (GMT+05:30): Bombay, Calcutta, Madras, New Delhi, Colombo.

Step 7 From the Date drop-down list boxes, choose 2004, Jun, and 15.

Step 8 From the Time drop-down list boxes, choose 15:30:0:0.

Step 9 Click Do Analysis.

Step 10 The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information.

Step 11 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window.

Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled.

See Example 4-5 for the results.

Example 4-5 Analysis Results for Example 4
Results Summary 
Calling Party Information 
Calling Party = 1000 
Partition = 
Device CSS = 
Line CSS = DNACSS1 
AAR Group Name = 
AARCSS = 
Dialed Digits = 36201 
Match Result = RouteThisPattern 
Matched Pattern Information 
Pattern = 36201 
Partition = DNAPartition1 
Time Schedule = DNATimeSchedule1 
Called Party Number = 36201 
Time Zone = (GMT) Greenwich Mean Time; Dublin, Edinburgh, London, Lisbon 
InterDigit Timeout = NO 
Provide Outside Dial Tone = NO 
Call Flow 
Directory Number :DN= 36201 
Partition = DNAPartition1 
Call Classification = OnNet 
Forwarding Information 
   ForwardAll : DN = VoiceMail = No CSS = 
   ForwardBusy 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   ForwardNoAnswer 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   ForwardNoCoverage 
      Internal : DN = VoiceMail = No CSS = 
      External : DN = VoiceMail = No CSS = 
   CFDF : DN = VoiceMail = No CSS = 
   Pickup Group Number = 
Device :Type= Cisco 7960 
   Device Status = UnKnown 
   Device Name = SEP000000036201 
   Ignore Presentation Indicators = Disabled 
   Alerting Name = 
   AAR Group Name = 
   AAR Calling Search Space = 
   AAR Prefix Digits = 
Alternate Matches 
Note: Information Not Available 
Related Topics

•Simple Analysis by Using the Analyzer Window

•Analysis by Using Phones

•Analysis by Using Gateways

•Analysis by Using Trunks

•Understanding Analysis Output

•Viewing Dialed Number Analyzer Output Files

Results Summary

The Results Summary section of the analysis results provides a summary of the dialed digits analysis results and displays Calling Party Information and Matched Pattern Information.

Note Fields that do not contain a description in this section display data as specified in Cisco CallManager Administration. For information on these fields, see the Cisco CallManager Administration Guide.

Calling Party Information

Calling Party—The calling party number after all the transformations are applied.

Partition—The Partition to which the final calling party belongs.

Device CSS—The Calling Search Space that is associated with the calling device.

Line CSS—The Calling Search Space that is associated with the calling party number.

AAR Group Name—The automated alternate routing (AAR) group to which this pattern belongs.

AARCSS—The calling search space that the calling party device uses when performing AAR.

Dialed Digits—The digits that the user entered in the Dialed Digits field.

Match Result—Specifies whether the call will be routed or blocked. RouteThisPattern or BlockThisPattern displays.

Note Line and device specific information display in the results when you perform analysis by using Analysis > Phones, Analysis > Gateways and Analysis > Trunks windows because a specific device was chosen as a calling entity. When you perform analysis from the Analysis > Analyzer window, you enter a calling party number that is not linked to any device that is configured in Cisco CallManager. Line and device specific information does not display in the Results Summary section of the analysis results that are obtained by using this procedure.

Matched Pattern Information

•Pattern—Specifies the ultimate pattern matches.

•Partition—The partition where this ultimate pattern exists.

•Time Schedule—The name of the time schedule chosen for the partition where this pattern exists.

Pattern Type—The Meet-Me Conference Number, Call Park Code Number, Call Pickup Number display. This field displays only when the dialed digits match a feature pattern type.

Called Party Number—The final called party number.

Time Zone—Time zone information of the device that is associated with the matched pattern.

Interdigit Timeout—Specifies the time delay in routing the call to the final device.

End Device—The final device to which the call was routed. This field displays only if the dialed digits match a route pattern.

OffNetPattern (OutsideDialTone)—Displays OffNet/OnNet, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

Note For intercept patterns, device-specific information will not display, and instead, a tag that indicates the Pattern Type will display.

Related Topics

•Understanding Analysis Output

•Analysis Results Examples

•Call Flow Details

•Alternate Matches

Call Flow Details

The Call Flow section of the results provides detailed information about all the stages that a call goes through, such as translation patterns, route patterns, route lists, route groups, and end devices.

Use the following topics to understand the results that display in the Call Flow section:

•Translation Pattern

•Route Pattern

•Hunt Pilot

•Directory Number

•Device Information

Note Fields that do not contain a description in this section display data as specified in Cisco CallManager Administration. For information on these fields, see the Cisco CallManager Administration Guide.

–Calling Party Transformation—The transformation that is specific to the end device such as the following transformations:

•Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the End Device are applied.

•Calling Party Selection—The selection that can be Originator/Last Redirect Number, and so on.

•Calling Party Presentation

•Calling Party Number—The calling party number after the calling party transformation settings of the End Device are applied.

Translation Pattern

The Translation Pattern section provides information on dialed digits, if the dialed digits match a configured translation pattern.

The following fields display:

•Hunt Pilot :Pattern—The hunt pilot pattern that is matched.

•Positional Match List—The position of the dialed digits in association with a pattern.

•DialPlan—The Numbering Plan in which this translation pattern resides.

•Route Filter—The route filter that is applied to the dialed digits.

–Filter Name—The Route Filter name that is associated with the Translation Pattern.

–Filter Clause—The Route Filter Clause that is associated with the Translation Pattern.

•Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the Translation Pattern are applied.

•Pretransform Called Party Number—The called party number before the called party transformation settings of the Translation Pattern are applied.

•Calling Party Transformations: This section displays calling party transformation settings of the Translation Pattern.

–External Phone Number Mask—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

–Calling Party Mask

–Prefix

–Calling Party Presentation

–Calling Party Number—The calling party number after the calling party transformation settings of the Translation Pattern are applied.

•Called Party Transformations. This section displays the called party transformation settings of the Translation Pattern, such as the following settings:

–Called Party Mask

–Discard Digit Instructions

–Prefix

–Called Number—The calling party number after the calling party transformation settings of the Translation Pattern are applied.

Route Pattern

The Route Pattern subsection provides information on route pattern details for the dialed digits, if the dialed digits match a route pattern.

•Route pattern :Pattern—The matched route pattern.

•Positional Match List—Displays the position of the dialed digits in association with a pattern.

•DialPlan—The Numbering Plan in which this route pattern resides.

•Route Filter

–Filter Name—The Route Filter name that is associated with the Route Pattern.

–Filter Clause—The Route Filter Clause that is associated with the Route Pattern.

•Require Forced Authorization Code—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

•Authorization Level—Displays the authorization level that is specified in Cisco CallManager Administration.

•Require Client Matter Code—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

•Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the Route Pattern are applied.

•Pretransform Called Party Number—The called party number before the called party transformation settings of the Route Pattern are applied.

•Calling Party Transformations. Displays the calling party transformation settings of the Route Pattern, such as the following settings:

–External Phone Number Mask—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

–Calling Party Mask

–Prefix

–Calling Party Presentation

–Calling Party Number—The calling party number after the calling party transformation settings of the Route Pattern are applied.

•Called Party Transformations. Displays the called party transformation settings of the Route Pattern, such as the following settings:

–Called Party Mask

–Digit Discarding Instructions

–Prefix

–Called Number—The calling party number after the calling party transformation settings of the Route Pattern are applied.

Hunt Pilot

This section includes information on Hunt Lists, Line Groups, and Hunt Forward Settings.

•Hunt List: HuntList Name—The name of the Route List.

•LineGroup: LineGroup Name—The name of the Route Group that is contained within this Route List.

•Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the Route Group are applied.

•Pretransform Called Party Number—The called party number before the called party transformation settings of the Route Group are applied.

•Calling Party Transformations. This section displays the calling party transformation settings of the Route Group, such as the following settings:

–External Phone Number Mask—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

–Calling Party Mask

–Prefix

–Calling Party Number—The calling party number after the calling party transformation settings of the Route Group are applied.

•Called Party Transformations. This section displays the called party transformation settings of the Route Group such as the following settings:

–Called Party Mask

–Discard Digit Instructions

–Prefix

–Called Number—The calling party number after the calling party transformation settings of the Route Group are applied

•Hunt Forward Settings

–Forward Hunt No Answer—The call forwarding settings when a hunt pilot is matched.

Use Personal Preferences—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

Destination—Displays the destination number for the call forward when there is no answer.

Calling Search Space—Displays the Calling Search Space where the forward destination, either Busy or No Answer, whichever is applicable, is present.

–Forward Hunt Busy—

Use Personal Preferences—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration.

Destination—Displays the destination number for the call forward when there is no answer.

Calling Search Space—Displays the Calling Search Space where the forward destination, either Busy or No Answer, whichever is applicable, is present.

•Maximum Hunt Timer—Displays the value that is specified in the Maximum Hunt Timer field in Cisco CallManager Administration.

Directory Number

The Directory Number (DN) subsection provides details about the DN, if the dialed digits match a DN number.

•Directory Number: DN—The directory number.

–Partition—The partition in which the DN resides.

–Device Location

–Forwarding Information—Displays the forwarding settings that are associated with the DN. The forwarding behavior differs depending on whether the call is from an internal or external user. The following forwarding settings display:

–Forward All : DN

–Forward Busy

Internal : DN

External : DN

–Forward No Answer

Internal : DN

External : DN

–Forward No Coverage

Internal : DN

External : DN

Device Information

•Device :Type—The type of device.

–End Device Name—The name of the endpoint device.

–Device Status—Indicates whether the status of the end device is Registered/Unregistered/Unknown.

–AAR Group Name—The AAR Group to which this device belongs.

–AAR Calling Search Space—The AAR Calling Search Space where this end device belongs.

–AAR Prefix Digits—The prefix digits that are used for automated alternate routing within this AAR group.

–Caller ID DN—The mask that is used to format the caller ID on outbound calls from a trunk.

•Inbound Fast Start—Displays Enabled/Disabled depending on whether the Inbound Fast Start field is checked or unchecked in Cisco CallManager Administration.

•Outbound Fast Start—Displays Enabled/Disabled depending on whether the Outbound Fast Start field is checked or unchecked in Cisco CallManager Administration.

•Codec For Outbound FastStart—Displays the value specified in the Codec for Outbound FastStart in Cisco CallManager Administration.

•Call Classification—Displays OffNet/OnNet/Use System Default/None, depending on the value that is chosen in Cisco CallManager Administration.

•Tunneled Protocol—Displays QSIG/none depending on the value that is configured in the Tunneled Protocol field in Cisco CallManager Administration.

•Ignore Presentation Indicators—Indicates if presentation settings of the calling party must be ignored for internal calls.

Alerting Name—Indicates the name of the alerting party that is chosen for a phone in Cisco CallManager.

Related Topics

•Understanding Analysis Output

•Analysis Results Examples

•Results Summary

•Alternate Matches

Alternate Matches

This section provides all the alternate matches that the analysis process looked up while finding the best match for the dialed digits.

Note Fields that do not contain a description in this section display data as specified in Cisco CallManager Administration. For information on these fields, see the Cisco CallManager Administration Guide.

The output displays in the following format:

•Partition : Name—The partition where the route pattern exists.

•Pattern

–Route Pattern—The name of the route pattern.

–Pattern Type—The pattern type, either Translation or Enterprise.

–Network Location—Indicates the network location of the route pattern, either OffNet or OnNet.

–CallManager Device Type—Specifies whether the device matched is an Access Device or a User Device.

Note Other parameters may display, depending on the settings that are associated with the pattern.

Related Topics

•Understanding Analysis Output

•Analysis Results Examples

•Results Summary

•Call Flow Details

Dumping Digit Discard Instructions and Dialing Patterns

Each Cisco CallManager dial plan configuration has called party transformation information that includes discard digit instructions (DDIs). Dialed Number Analyzer allows you to view the DDIs that are specified for the Cisco CallManager dial plan that you are analyzing.

The tool also allows you to view all the dialing patterns that are associated with gateways and phones that are configured in the Cisco CallManager dial plan that you are analyzing. Use the following procedure to view DDIs or dialing pattern information that is specified for a dial plan.

Procedure

Step 1 Choose Analysis > Dump DA Information.

The Dump Options window displays.

Step 2 In the Select Dump Option field, click the Discard Digit Instructions or the Dialing Forest radio button.

Step 3 In the Select Viewing Option field, do one of the following actions:

•To view the discard digit instructions or dialing forest information in the browser window, click the Open File in Browser button.

•To save the discard digit instructions or dialing forest information to a file, click the Save File radio button.

Step 4 Click Finish.

If you chose to view the discard digit instructions or dialing forest information on the browser, the results display in the same window.

If you chose to save the discard digit instructions or dialing forest information to a file, the File Download dialog box displays. Use the following procedure to save the file:

a. Click Save.

The Save As dialog displays. Browse to a location on your PC where you want to save the file.

b. Click Save.

The result gets saved as a text file called DialPlanForest.txt or DiscardDigitInstructions.txt, depending on whether you chose discard digit instructions or dialing forest in Step 2.

Related Topic

•Understanding Analysis Output

Viewing Dialed Number Analyzer Output Files

When you store results of analysis that you have performed by using phones, gateways, or trunks, the results get saved as XML files on your PC. You can retrieve and view these output files on the browser by using Dialed Number Analyzer. Use the following procedure to view output files.

Procedure

Step 1 Choose Analysis > View File.

Step 2 The View File window displays.

Step 3 Click Browse in the Select a File to View field. Browse to the location on your PC where the required output file is located and choose it. An example of an output file follows.

DialedNumberAnalyzerOutput_1001.xml

where 1001 represents the dialed digits that are specified during analysis.

Step 4 Click View File.

The output file displays in a new window called Dialed Number Analyzer Results.

The Results Summary section expands to show the summary. Click the plus icon to expand the required results section to view the details.

Step 5 Close the Dialed Number Analyzer Results window after viewing the results.

Related Topics

•Simple Analysis by Using the Analyzer Window

•Analysis by Using Phones

•Analysis by Using Gateways

•Analysis by Using Trunks

•Understanding Analysis Output

Viewing Trace Configuration Files

Trace files provide a means of tracking problems in the functioning of a tool. The system writes trace files for Dialed Number Analyzer to the server on which Dialed Number Analyzer is installed when you install Dialed Number Analyzer. You can choose to enable or disable the writing of trace files feature from the Service Control window in Dialed Number Analyzer. This section describes the procedure to enable and disable the writing of trace files.

Use the following procedure to enable the feature.

Procedure

Step 1 In Dialed Number Analyzer, choose Service > Control Center.

The Control Center window displays the current status of the Trace Configuration option.

Step 2 If the current status is Disabled, click Enable in the corresponding Action column.

The system enables the feature, and the trace files get written to the following location on your PC:

C:\Program Files\Cisco\Trace\DNA

The file appears in the following format:

DNA_indexNo.txt

where <indexNo> ranges from 1- 250.

Use the following procedure to disable the writing trace files feature.

Procedure

Step 1 In Dialed Number Analyzer, choose Service > Control Center.

The Control Center window displays the current status of the Trace Configuration option. The current status displays as Enabled.

Step 2 In the corresponding Action column, click Disable.

This action means that the feature is disabled.

	Cisco CallManager Dialed Number Analyzer Guide, Software Release 3.0
	Analyzing Cisco CallManager Dial Plan Configuration
Cisco CallManager Dialed Number Analyzer Guide, Software Release 3.0 Index Preface Introduction Installing Cisco CallManager Dialed Number Analyzer Accessing Dialed Number Analyzer Analyzing Cisco CallManager Dial Plan Configuration	Download this chapter Analyzing Cisco CallManager Dial Plan Configuration Download the complete book PDF version of Cisco Dialed Number Analyzer Guide (PDF - 1 MB) Table Of Contents Analyzing Cisco CallManager Dial Plan Configuration Database Synchronization Disabling Database Synchronization Simple Analysis by Using the Analyzer Window Analysis by Using Phones Finding a Phone Choosing a Phone Line Performing Analysis by Using Phones Analysis by Using Gateways Finding a Gateway Choosing Gateway Endpoints and Entering Analysis Input Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways Choosing Non-IOS MGCP Gateways Choosing Cisco IOS H.323 Gateways Choosing Analog Access Gateways Choosing Cisco VG248 Analog Phone Gateways Performing Analysis by Using Gateways Analysis by Using Trunks Finding a Trunk Choosing a Trunk Performing Analysis by Using Trunks Understanding Analysis Output Analysis Results Examples Example 1 Example 2 Example 3 Example 4 Example 5 Results Summary Call Flow Details Translation Pattern Route Pattern Hunt Pilot Directory Number Device Information Alternate Matches Dumping Digit Discard Instructions and Dialing Patterns Viewing Dialed Number Analyzer Output Files Viewing Trace Configuration Files Analyzing Cisco CallManager Dial Plan Configuration Dialed Number Analyzer allows analysis of a configured Cisco CallManager dial plan and provides details on the call flow of dialed digits. In the predeployment stage, you can use the tool to identify problems in a complex dial plan and fine tune the dial plan. You can also use the tool, after the dial plan is deployed, to identify real-time problems in the call flow of dialed digits. When you use Dialed Number Analyzer to analyze dial plans for a cluster of Cisco CallManager systems and numerous devices, you may be able to access the windows and enter data for analysis quickly. However, you may not be able to see any results when you perform the analysis. The following message displays: Check if the DNA service is running. If the DNA service is running, then Dialed Number Analyzer is still initializing. Wait for a few minutes for Dialed Number Analyzer to initialize and try again. This message displays because Dialed Number Analyzer is registering the devices in the Cisco CallManager system. Clear the message and wait for a few minutes before you perform analysis. Use the following topics to understand how to use the Service Control window and how to use Dialed Number Analyzer to analyze a Cisco CallManager dial plan configuration: •Database Synchronization •Simple Analysis by Using the Analyzer Window •Analysis by Using Phones •Analysis by Using Gateways •Analysis by Using Trunks •Understanding Analysis Output •Dumping Digit Discard Instructions and Dialing Patterns •Viewing Dialed Number Analyzer Output Files •Viewing Trace Configuration Files Database Synchronization Dialed Number Analyzer replicates and uses the Cisco CallManager database configuration to analyze calls in a dial plan. For this reason, make sure that Dialed Number Analyzer is in sync with the Cisco CallManager database before you use the tool to perform any analysis. When changes are made to the Cisco CallManager database, ensure that Dialed Number Analyzer reflects the changes to facilitate analysis by using current data. Examples of database changes include addition or deletion of devices, modification of route patterns, modification of gateway configuration settings, and so on. You can enable Dialed Number Analyzer to receive database change notifications from Cisco CallManager whenever database changes are made by using Cisco CallManager Administration. Use the following steps to enable database change notifications to Dialed Number Analyzer. Procedure Step 1 In Dialed Number Analyzer, choose Service > Control Center. The Control Center window displays. Database Synchronization displays under the Service Name-Database column. Step 2 By default, the system enables Database Synchronization when Dialed Number Analyzer is installed. To keep database synchronization enabled, do not modify this setting. Note Every time that you disable and enable database synchronization again, stop and start the Dialed Number Analyzer service to ensure that Dialed Number Analyzer is in sync with the Cisco CallManager database. For instructions on starting the Dialed Number Analyzer service, see "Starting Dialed Number Analyzer Service" section. Related Topics •Disabling Database Synchronization •Starting Dialed Number Analyzer Service Disabling Database Synchronization You can choose not to notify Dialed Number Analyzer of changes that are made to the Cisco CallManager database. Use the following steps to disable notification of database changes. Procedure Step 1 Choose Service > Control Center. The Control Center window displays. Database Synchronization displays under the Service Name-Database column. Step 2 Click Disable in the corresponding Action column. Related Topic •Database Synchronization Simple Analysis by Using the Analyzer Window Simple analysis involves entering calling party and called party digits in Dialed Number Analyzer and choosing a calling search space for the analysis. Dialed Number Analyzer uses this calling search space and analyzes the dialed digits. You need not choose specific devices or provide any other input. Dialed Number Analyzer allows analysis of a route pattern, translation pattern, phone DN, or CTI Route Point. Use this procedure only when you want to perform a quick analysis by entering dialed digits, selecting a calling search space, and entering the time and date of the calling party for analysis. Analysis results that are obtained by using this procedure do not display details, like partitions, AAR calling search space details and so on in the Calling Party Information section. Because you do not choose a specific device to dial digits, instead you enter a calling party number that is not associated with any device that is configured in the Cisco CallManager system. You can enter numerals, the symbols # and , and the alphabet letters A, a, B, b, C, c, D, and d in the Dialed Digits and Calling Party fields for analysis. Access Dialed Number Analyzer and use the following procedure to perform a simple analysis. Procedure Step 1* Choose Analysis > Analyzer. The Analyzer window displays. Enter input for the analyzer in this window. Step 2 In the Calling Party field, enter the calling party digits. You do not have to Associate this number with a device. By default, 1000 displays in this field. Step 3 In the Dialed Digits field, enter the digits that the calling party is to call. Step 4 From the Calling Search Space drop-down list box, choose the calling search space that is to be used to analyze the dialed digits. A calling search space comprises a collection of partitions that are searched to determine how a dialed number should be routed. Step 5 From the Device Time Zone drop-down box, choose the time zone of the calling party. The time zone that represents the time zone information from the operating system of the server where Cisco CallManager is installed displays by default. Note The system uses this time zone for analysis only when the partition time zone setting is configured to Originating Device, in the Partition Configuration window in Cisco CallManager. Step 6 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled, leave the default settings. The local time and date, representing the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 7 Click Do Analysis to start the analysis or click Clear to clear the fields and to reenter data. When you click Do Analysis, Dialed Number Analyzer analyzes the dialed digits and displays the results in a new window that is called Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use. To save the results, use Steps 8, 9, 10, and 11; otherwise skip to Step 12. Step 8 To save the results, in the upper, right corner of the Analyzer Output window, click the Save Result link. The File Download dialog displays. Step 9 Click Save. The Save As dialog displays. Browse to a location on your PC where you want to save the file. Step 10 Click Save. The system saves the results in an XML file on your PC. The saved file has the following naming convention: DialedNumberAnalyzerOutput_<dialeddigits>.xml where <dialeddigits> specifies the digits that are entered in the Dialed Digits field. Step 11 In the Download Complete dialog box, click Close to complete the Save As procedure. Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section. Step 12 Close the Analyzer Output window. Related Topics •Database Synchronization •Analysis by Using Phones •Analysis by Using Gateways •Analysis by Using Trunks •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Analysis by Using Phones Dialed Number Analyzer provides a Phones window where you can find and list phones by device name, description, directory number, calling search space device pool, device type, and call pickup group. You can find a phone and choose it as a calling device for the analysis that you want to perform. You can further choose a configured phone line (directory number) and use it as a calling party number. Use the following topics to choose a phone and a phone line and to carry out analysis by using that phone line: •Finding a Phone •Choosing a Phone Line •Performing Analysis by Using Phones Related Topics •Simple Analysis by Using the Analyzer Window •Analysis by Using Gateways •Analysis by Using Trunks •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Finding a Phone Dialed Number Analyzer allows you to locate a phone that you can use to analyze dialed digits from that phone. Use the following procedure to locate a phone. Procedure Step 1 Choose Analysis > Phones. The Find and List Phones window displays. Step 2 From the first Find Phones where drop-down list box, choose one of the following criteria: •Device Name •Description •Directory Number •Calling Search Space •Device Pool •Device Type •Call Pickup Group Note The criterion that you choose in this drop-down list box specifies how the list of phones displays. For example, if you choose Device Name, the Device Name column will display as the left column of the results list. Note If you choose Directory Number, Calling Search Space, or Call Pickup Group, the options that are available in the database display. Step 3 From the second Find Phones where drop-down list box, choose one of the following criteria: •begins with •contains •ends with •is exactly •is not empty •is empty Note If you choose Calling Search Space, Device Pool, Device Type, or Call Pickup Group in the first field, you can choose a value from the drop-down list for this field. Step 4 Specify how many items per window to display. Step 5 Specify the appropriate search text, if applicable, and click Find. Tip To find all phones, click Find without entering any search text or choose Device Name in the first Find Phones where drop-down list box and "is not empty" in the second Find Phones where drop-down list box. A list of discovered phones that match the criteria displays. This window also lists the total number of phones and windows in this window. Step 6 To view the next set of discovered phones, click Next. Step 7 From the list of records, click the links that are available for the record that matches your search criteria. The Phone Line Selection window displays. Step 8 Continue with the procedure that is described in "Choosing a Phone Line" section. Related Topics •Choosing a Phone Line •Performing Analysis by Using Phones •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Choosing a Phone Line After you have identified a phone to use for analysis, you need to choose a phone line that is configured in the system. Use the following procedure to choose a phone line as the calling party. Procedure Step 1 Find the phone that you want to use as a calling party device by using the procedure described in the "Finding a Phone" section. The Phone Line Selection window displays. The phone ID number, registration details, and IP address of the server on which the phone is registered display. Under the Phone Configuration column, information on the device displays. The address of the machine, the device pool to which the phone belongs, calling search space, AAR calling search space, and Media Resource Group List details display. Step 2 From the list of records, choose the phone line by clicking the Line radio button for the phone line that you require. Note In the upper, right corner or lower, right corner of the window, click the Back to Find/List Phones link to return to the Find and List Phones window. Step 3 Continue with the procedure in "Performing Analysis by Using Phones" section. Related Topics •Finding a Phone •Performing Analysis by Using Phones •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Performing Analysis by Using Phones After you have identified a phone and chosen a phone line, you can enter dialed digits for analysis. This section describes how to perform analysis by using the chosen phone line. Procedure Step 1 Find the phone that you want to use as a calling party device by using the procedure in the "Finding a Phone" section. The Phone Line Selection window displays. Note The time zone that is configured for the phone in Cisco CallManager displays in the Device Time Zone field. Step 2 Choose a phone line by using the procedure in the "Choosing a Phone Line" section. Step 3 In the Dialed Digits field, enter the digits that are to be dialed from the chosen phone line. Step 4 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled, leave the default settings. The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 5 Click Do Analysis. Dialed Number Analyzer chooses the Calling Search Space of the chosen phone line and device for the analysis. The results display in a new window that is called the Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use. To save the results, use Steps 6, 7, 8, and 9; otherwise skip to Step 10. Step 6 To save the results, in the upper, right corner of the window, click the Save Result link. The File Download dialog displays. Step 7 Click Save. The Save As dialog displays. Browse to a location on your PC where you want to save the file. Step 8 Click Save. The results get saved in an XML file on your PC. The saved file has the following naming convention: DialedNumberAnalyzerOutput_<dialeddigits>.xml where <dialeddigits> specifies the dialed digits that are entered in the Dialed Digits field. Step 9 Click Close in the Download Complete dialog box to complete the Save As procedure. Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section. Step 10 Close the Analyzer Output window. Note You can use the Analyzer Output window to enter new data in the fields and perform another analysis by using the steps in the "Analysis by Using Phones" section. Related Topics •Finding a Phone •Choosing a Phone Line •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Analysis by Using Gateways Dialed Number Analyzer allows you to find and list gateways through which Cisco CallManager receives inbound calls. From the list of gateways, you can choose gateway endpoints to dial digits and analyze the call flow of inbound calls to a Cisco CallManager system. You can choose gateway endpoints that are configured in the Cisco CallManager system. Use the following topics to find gateways, choose gateway endpoints, enter dialed digits, and perform analysis: •Finding a Gateway •Choosing Gateway Endpoints and Entering Analysis Input •Performing Analysis by Using Gateways Finding a Gateway You can find and list gateways by device name, description, DN/route pattern, device type, calling search space, route group, and device pool. This section describes the procedure to find gateways. Procedure Step 1 Choose Analysis > Gateways. The Find and List Gateways window displays. Step 2 From the first Find gateways where drop-down list box, choose one of the following criteria: •Device Name •Description •DN/Route Pattern •Calling Search Space •Device Pool •Route Group •Device Type Note The criterion that you choose in this drop-down list box specifies how the list of gateways displays. For example, if you choose Device Name, the Device Name column will display as the left column of the results list. Note If you choose DN/Route Pattern, Calling Search Space, or Route Group, the options that are available in the database display. Step 3 From the second Find gateways where drop-down list box, choose one of the following criteria: •begins with •contains •ends with •is exactly •is not empty •is empty Note If you choose Calling Search Space, Device Pool, Route Group, or Device Type in the first field, you can choose a value from the drop-down list for this field. Step 4 Specify how many items per window to display. Step 5 Specify whether endpoints of gateways must be shown or hidden. Step 6 Specify the appropriate search text, if applicable, and click Find. Tip To find all gateways, click Find without entering any search text or choose Device Name in the first Find gateways where drop-down list box and "is not empty" in the second Find gateways where drop-down list box. A list of gateways that matches the criteria displays. The information that displays differs for different gateway models. This window also lists the total number of devices and windows. Step 7 To view the next set of discovered gateways, click Next. Related Topics •Choosing Gateway Endpoints and Entering Analysis Input •Performing Analysis by Using Gateways •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Choosing Gateway Endpoints and Entering Analysis Input After you find gateways that match your search criteria, you need to choose gateway endpoints and enter calling and called party information. Use the following steps to choose gateway endpoints. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. Step 2 From the list of records that displays in the Find and List Gateways window, choose a gateway. Choose from the following types of gateways: •Cisco IOS MGCP Gateway •Non-IOS MGCP Gateway •Cisco IOS H.323 Gateway •Analog Access Gateway •Cisco VG248 Analog Phone Gateway •Cisco IOS SCCP Gateway Depending on the type of gateway, different information displays. Use the following topics to choose gateway endpoints for each gateway type: •Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways •Choosing Non-IOS MGCP Gateways •Choosing Cisco IOS H.323 Gateways •Choosing Analog Access Gateways •Choosing Cisco VG248 Analog Phone Gateways Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways After you find gateways that match your search criteria, you can choose Cisco IOS MGCP gateway endpoints and Cisco IOS SCCP Gateways. The following list comprises Cisco IOS MGCP gateways: •Cisco Voice Gateway 200 (VG200) •Cisco IOS 269X, 26XX, 364X, 366X, 3725, 3745 gateways •Cisco Catalyst 4000 Access Gateway Module •Cisco Catalyst 4224 Voice Gateway Switch •Communication Media Module •Cisco IAD2400 •Cisco ICS77XX-ASI160, Cisco ICS77XX-ASI81, Cisco ICS77XX-MRP2xx, Cisco ICS77XX-MRP3-16FXS, Cisco ICS77XX-MRP3-8FXO-M1, Cisco ICS77XX-MRP3-8FXS, Cisco ICS77XX-MRP3xx gateways Use the following steps to choose Cisco IOS MGCP/IOS SCCP gateway endpoints for analysis. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. You can use two ways to access Cisco IOS MGCP/IOS SCCP gateway endpoints. You can directly access the Endpoint Identifiers from the Gateway Information window, or you can first see a list of all the configured endpoints in a new window and then choose one of them. Use one of the following procedures. Procedure 1 •From the list of records that displays in the Find and List Gateways window, click the gateway that you want to use. –The Gateway Information window displays and lists the installed Voice Interface Cards and Endpoint Identifiers for each card. The endpoint identifiers represent configured ports for the chosen devices. –From the list of endpoint identifiers, click the required endpoint. The appropriate window displays and shows gateway information and port information. Note The time zone that is configured for the gateway in Cisco CallManager displays in the Device Time Zone field. –In the Calling Party field, the calling party number that is configured for this endpoint displays. –In the Dialed Digits field, enter the digits to be dialed. –Choose the time zone, date, and time settings for analysis, only if Time of Day routing is enabled in Cisco CallManager. If not, leave the default settings. Note The local time and date, that represents the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time. From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. –Click Do Analysis to analyze the call flow for the dialed digits. –Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure. Procedure 2 •From the list of records that displays in the Find and List Gateways window, click the See Endpoints link in the record that you want to use. The endpoints display in a new window. You can choose BRI and analog endpoints for analysis. –From the list of endpoints in the new window, click the record that you want to use. The Gateway Information window displays and shows Gateway Information and Port Information. Note The time zone that is configured for the endpoint in Cisco CallManager displays in the Device Time Zone field. –In the Calling Party field, the calling party number that is configured for this endpoint displays. –In the Dialed Digits field, enter the digits to be dialed. –If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time. From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. –Click Do Analysis to analyze the call flow for the dialed digits. Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure. Note Gateways include one or more configured ports with multiple endpoints. All ports for the chosen gateway display in the left frame of the Gateway Information window. Click another endpoint to go to that endpoint Gateway Information window. Note In the upper, right corner or the lower, right corner of the Gateway Information window, click Back to main Gateway Information link to return to the Gateway Information window or Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window. Related Topics •Choosing Non-IOS MGCP Gateways •Choosing Cisco IOS H.323 Gateways •Choosing Analog Access Gateways •Choosing Cisco VG248 Analog Phone Gateways •Performing Analysis by Using Gateways •Viewing Dialed Number Analyzer Output Files Choosing Non-IOS MGCP Gateways After you find gateways that match your search criteria, you can choose Non-IOS MGCP gateway endpoints. The following list comprises Non-IOS MGCP gateways: •Cisco Catalyst 6000 E1 VoIP Gateway •Cisco Catalyst 6000 T1 VoIP Gateway •Cisco DT-24+ or DE-30+ Digital Access Trunk Gateway Use the following procedure to choose Non-IOS MGCP gateway endpoints for analysis. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. Step 2 From the list of records that displays in the Find and List Gateways window, click the Non-IOS MGCP gateway that you want to use. The Gateway Information window displays and shows Device Information and Call Routing Information. Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field. Step 3 In the Calling Party field, the calling party number that is configured for this endpoint displays. Step 4 In the Dialed Digits field, enter the digits to be dialed. Step 5 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 6 Click Do Analysis to analyze the call flow for the dialed digits. Step 7 Follow the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure. Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window. Related Topics •Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways •Choosing Cisco IOS H.323 Gateways •Choosing Analog Access Gateways •Choosing Cisco VG248 Analog Phone Gateways •Performing Analysis by Using Gateways •Viewing Dialed Number Analyzer Output Files Choosing Cisco IOS H.323 Gateways After you find a list of gateways that match your search criteria, you can choose Cisco IOS H.323 gateway endpoints. Use the following procedure to choose Cisco IOS H.323 gateway endpoints for analysis. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. Step 2 From the list of records that displays in the Find and List Gateways window, click the Cisco IOS H.323 gateway that you want to use. The Gateway Information window displays and shows Device Information and Call Routing Information. Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field. Step 3 In the Calling Party field, the calling party number that is configured for this endpoint displays. Step 4 In the Dialed Digits field, enter the digits to be dialed. Step 5 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 6 Click Do Analysis to analyze the call flow for the dialed digits. Step 7 Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure. Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window. Related Topics •Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways •Choosing Non-IOS MGCP Gateways •Choosing Analog Access Gateways •Choosing Cisco VG248 Analog Phone Gateways •Performing Analysis by Using Gateways •Viewing Dialed Number Analyzer Output Files Choosing Analog Access Gateways After you find a list of gateways that match your search criteria, you can choose Analog Access gateway endpoints. The following list comprises Analog Access gateways: •Cisco Catalyst 6000 24 Port FXS Gateway •Analog Access AS-2, AS-4, AS-8, AT-2, AT-4, AT-8 Use the following procedure to choose Analog Access gateway endpoints for analysis. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. Step 2 From the list of records that displays in the Find and List Gateways window, click the Analog Access gateway that you want to use. The Gateway Information window displays and shows all the ports that are configured for the gateway in the left frame. Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field. Step 3 Click the port that you require to make a call. The Gateway Information window displays. Step 4 In the Calling Party field, the calling party number that is configured for this endpoint displays. Step 5 In the Dialed Digits field, enter the digits to be dialed. Step 6 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 7 Click Do Analysis to analyze the call flow for the dialed digits. Step 8 Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure. Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window. Related Topics •Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways •Choosing Non-IOS MGCP Gateways •Choosing Cisco IOS H.323 Gateways •Choosing Cisco VG248 Analog Phone Gateways •Performing Analysis by Using Gateways •Viewing Dialed Number Analyzer Output Files Choosing Cisco VG248 Analog Phone Gateways After you find a list of gateways that matches your search criteria, you can choose Cisco VG248 Analog Phone gateway endpoints that are applicable to a Cisco VG248 Analog Phone gateway. Use the following procedure to choose Cisco VG248 Analog Phone gateway endpoints for analysis. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. Step 2 From the list of records that displays in the Find and List Gateways window, click the gateway that you want to use. The Gateway Information window displays and shows all ports that are configured for the selected gateway. Note The time zone that is configured for the gateway in Cisco CallManager displays in the Time Zone field. Step 3 Choose and click the port that you require. If you click a port that is not configured, a message displays to inform you that the port is not configured. If you choose a configured port, the Phone Line Selection window displays. Step 4 From the list of records, click the Line radio button for the phone line that you require. Step 5 In the Dialed Digits field, enter the digits to be dialed. Step 6 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 7 Click Do Analysis to analyze the call flow for the dialed digits. Step 8 Use the steps in "Performing Analysis by Using Gateways" section to complete the analysis procedure. Note In the upper, right corner or the lower, right corner of the window, click the Back to Find/List Gateways link to return to the discovered gateways on the Find and List Gateways window. Related Topics •Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways •Choosing Non-IOS MGCP Gateways •Choosing Cisco IOS H.323 Gateways •Choosing Analog Access Gateways •Performing Analysis by Using Gateways •Viewing Dialed Number Analyzer Output Files Performing Analysis by Using Gateways After you have chosen a gateway endpoint and entered input for analysis, you can analyze the dialed digits. Use the following procedure to do the analysis. Procedure Step 1 Find the gateway that you want to use by using the procedure in the "Finding a Gateway" section. Step 2 From the Find and List Gateways window, choose gateway endpoints. In the Gateway Information window, enter calling party or called party information by using the procedures in the following sections for different types of gateways: •Choosing Cisco IOS MGCP / Cisco IOS SCCP Gateways •Choosing Non-IOS MGCP Gateways •Choosing Cisco IOS H.323 Gateways •Choosing Analog Access Gateways •Choosing Cisco VG248 Analog Phone Gateways Step 3 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the Cisco CallManager system time. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 4 Click Do Analysis. Dialed Number Analyzer uses the Calling Search Space that is specified for the chosen endpoint and analyzes the dialed digits. The results display in a new window called the Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use. To save the results, use Steps 5, 6, 7 and 8; otherwise skip to Step 9. Step 5 To save the result, in the upper, right corner of the window, click the Save Result link. The File Download dialog displays. Step 6 Click Save. The Save As dialog displays. Browse to a location on your PC where you want to save the file. Step 7 Click Save. The result gets saved as an XML file on your PC. The saved file has the following naming convention: DialedNumberAnalyzerOutput_<dialeddigits>.xml where <dialeddigits> specifies the dialed digits that are entered in the Dialed Digits field. Step 8 In the Download Complete dialog box, click Close to complete the Save As procedure. Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section. Step 9 Close the Analyzer Output window. Related Topics •Finding a Gateway •Choosing Gateway Endpoints and Entering Analysis Input •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Analysis by Using Trunks Dialed Number Analyzer provides a Trunks window where you can find and list trunks through which inbound dialed digits can be analyzed. Use the following topics to find and choose a trunk and analyze dialed digits: •Finding a Trunk •Choosing a Trunk •Performing Analysis by Using Trunks Finding a Trunk You can find and list trunks by device name, description, calling search space, route pattern, device pool, route group, and device type. This section describes the procedure to find trunks. Procedure Step 1 Choose Analysis > Trunks. The Find and List Trunks window displays. Step 2 From the first Find trunks where drop-down list box, choose one of the following criteria: •Device Name •Description •Calling Search Space •Route Pattern •Device Pool •Route Group •Device Type Note The criterion that you choose in this drop-down list box specifies how the list of gateways display. For example, if you choose Device Name, the Device Name column will display as the left column of the results list. Note If you choose Route Pattern, Calling Search Space, or Route Group, the options that are available in the database display. Step 3 From the second Find trunks where drop-down list box, choose one of the following criteria: •begins with •contains •ends with •is exactly •is not empty •is empty Note If you choose Calling Search Space, Device Pool, Route Group, or Device Type in the first field, you can choose a value from the drop-down list for this field. Step 4 Specify how many items per window to display. Step 5 Specify the appropriate search text, if applicable, and click Find. Tip To find all trunks, click Find without entering any search text or choose Device Name in the first Find trunks where drop-down list box and "is not empty" in the second Find trunks where drop-down list box. A list of trunks that match the search criteria displays. This window also lists the total number of records in this window. Step 6 To view the next set of discovered trunks, click Next. Related Topics •Choosing a Trunk •Performing Analysis by Using Trunks •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Choosing a Trunk After you find the trunks that you require, you need to choose a trunk. Use the following procedure to choose a trunk. You can perform analysis for SIP trunks. Procedure Step 1 Find the trunk that you want to use for analysis by using the procedure in the "Finding a Trunk" section. The Find and List Trunks window displays and shows trunk information. Step 2 From the list of records, choose a trunk by clicking the required record. The Trunk Information window displays. Related Topics •Finding a Trunk •Performing Analysis by Using Trunks •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Performing Analysis by Using Trunks After you have identified and chosen a trunk, you need to enter input for analysis. Use the following procedure to enter input and perform analysis. Procedure Step 1 Find the trunk that you require by using the procedure in the "Finding a Trunk" section. Step 2 From a list of discovered trunks, choose the trunk that you require by using the steps in the "Choosing a Trunk" section. The Trunk Information window displays. Device and Call Routing information for the chosen trunk displays. Note The time zone that is configured for the trunk in Cisco CallManager displays in the Device Time Zone field. Step 3 In the Calling Party field, enter the calling party number. Step 4 In the Dialed Digits field, enter the digits to be dialed. Step 5 If Time of Day routing is enabled in Cisco CallManager, choose the time zone, date, and time settings for analysis. If Time of Day routing is not enabled in Cisco CallManager, leave the default settings. Note The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that are different from the default Cisco CallManager system time. •From the Time Zone drop-down list box, choose the time zone that Dialed Number Analyzer must use for analysis. Greenwich Median Time (GMT) displays by default. •From the Date drop-down list boxes, choose the year, month, and date that Dialed Number Analyzer must use for analysis. •From the Time drop-down list boxes, choose the hour, minute, second, and millisecond that Dialed Number Analyzer must use for analysis. Step 6 Click Do Analysis. Dialed Number Analyzer uses the Calling Search Space that is specified for the trunk and analyzes the dialed digits. The results display in a new window that is called the Analyzer Output window. You can simply view the results or save the results in a file format on your PC for later use. To save the results, use Steps 7, 8, 9, and 10; otherwise, skip to Step 11. Step 7 To save the result, in the upper, right corner of the window, click the Save Result link. The File Download dialog displays. Step 8 Click Save. The Save As dialog displays. Browse to a location on your PC where you want to save the file. Step 9 Click Save. The result gets saved as an XML file on your PC. The saved file has the following naming convention: DialedNumberAnalyzerOutput_<dialeddigits>.xml where <dialeddigits> specifies the dialed digits that are entered in the Dialed Digits field. Step 10 Click Close in the Download Complete dialog box to complete the Save As procedure. Note For instructions on how to view the saved XML file in the browser, see the "Viewing Dialed Number Analyzer Output Files" section. Step 11 Close the Analyzer Output window. Related Topics •Finding a Trunk •Choosing a Trunk •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Understanding Analysis Output The results of analysis that you perform contain information on the dialed digits call flow. This section provides two examples of analysis results that were obtained by using Dialed Number Analyzer. Each example shows results that were obtained by using different types of inputs and Cisco CallManager configuration data. This section also describes each value in the analysis output. Three sections provide the description of the results: Results Summary, Call Flow, and Alternate Matches. Use the following topics to understand the information in the analysis output: •Analysis Results Examples •Results Summary •Call Flow Details •Alternate Matches Related Topics •Simple Analysis by Using the Analyzer Window •Analysis by Using Phones •Analysis by Using Gateways •Analysis by Using Trunks •Viewing Dialed Number Analyzer Output Files •Analysis Results Examples Analysis Results Examples This section provides three examples to help you understand the results that you could obtain with different inputs by using Dialed Number Analyzer. The Results Summary, Call Flow, and Alternate Matches sections describe all the values that could display in analysis results. The sample results may include only values that result from the type of input that is provided to Dialed Number Analyzer. Example 1 This example assumes the following setup in Cisco CallManager: Phone—1360064 in partition 'DallasPartition' Line Calling Search Space—ALL (ALL CSS has DallasPartition and SJPartition) Route Filter—RF-SJ (LONG-DISTANCE-DIRECT-DIAL EXISTS AND AREA-CODE == 408). This route pattern selects RouteList 'RL1'. RL1 uses RG1, RG2, AND RG3. RG1 configuration includes an Inter Cluster Trunk as 10.77.31.206, with route group level calling and called party transformations. RG2 configuration includes an Inter Cluster Trunk 10.77.31.231, with QSIG tunneled protocol. RG3 configuration includes one CiscoAT Gateway and one CiscoAS Gateway. Route Pattern—9.@ in partition 'SJPartition', where: •Offnet Pattern (Outside Dial Tone) is checked •Require Forced Authorization Code is checked •Require Client Matter Code is checked •Authorization Level = 155 Associate the route pattern with the RL1 route list and route filter RF-SJ. Configure the Inter Cluster Trunk 10.77.31.206 as follows: •Tunneled Protocol—QSIG. •Call Classification—Use System Default. •Inbound Fast Start—Disabled. •Outbound Fast Start—Enabled. •Codec For Outbound FastStart—G711 u-law 64k. Configure the Inter Cluster Trunk 10.77.31.231 as follows: •Tunneled Protocol—QSIG. •Call Classification—Use System Default. •Inbound Fast Start—Disabled. •Outbound Fast Start—Disabled. Use the following procedure to run this example: Procedure Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer. Step 2 In the Analyzer window, enter 1360064 in the Calling Party field. Step 3 In the Dialed Digits field, enter 914089027872. Step 4 From the Calling Search Space drop-down list box, choose ALL. Step 5 Leave the default values in the Device Time Zone field, Cisco CallManager system Time Zone, Date, and Time fields. Step 6 Click Do Analysis. The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information. Step 7 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window. Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled. See Example 4-1 for the results. Example 4-1 Analysis Results for Example 1 Results Summary Calling Party Information Calling Party = 1360064 Partition = Device CSS = Line CSS = ALL AAR Group Name = AARCSS = Dialed Digits = 914089027872 Match Result = RouteThisPattern Matched Pattern Information Pattern = 9.@ Partition = SJPartition Time Schedule = Called Party Number = 914089027872 Time Zone = (GMT+05:30) Bombay, Calcutta, Madras, New Delhi, Colombo End Device = RL1 CallClassification = OffNet InterDigit Timeout = NO Provide Outside Dial Tone) PlayedAfter = 9 Call Flow Route Pattern :Pattern= 9.@ Positional Match List = 9:1:408:902:7872 DialPlan = North American Numbering Plan Route Filter Filter Name = RF-SJ Filter Clause = (LONG-DISTANCE-DIRECT-DIAL EXISTS AND AREA-CODE == 408) Require Forced Authorization Code = Yes Authorization Level = 155 Require Client Matter Code = Yes Network Location = OffNet PreTransform Calling Party Number = 1360064 PreTransform Called Party Number = 914089027872 Calling Party Transformations External Phone Number Mask = NO Calling Party Mask = Prefix = CallingLineId Presentation = Default CallingName Presentation = Default Calling Party Number = 1360064 ConnectedParty Transformations ConnectedLineId Presentation = Default ConnectedName Presentation = Default Called Party Transformations Called Party Mask = Discard Digits Instruction = Prefix = Called Number = 914089027872 Route List :Route List Name= RL1 RouteGroup :RouteGroup Name= RG1 PreTransform Calling Party Number = 1360064 PreTransform Called Party Number = 914089027872 Calling Party Transformations External Phone Number Mask = Default Calling Party Mask = Prefix = Calling Party Number = 1360064 Called Party Transformations Called Party Mask = Discard Digits Instructions = Prefix = Called Number = 914089027872 Device :Type= InterClusterTrunk-NonGatekeeperControlled End Device Name = 10.77.31.206 PortNumber = 0 Device Status = UnKnown AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Inbound Fast Start = Disabled Outbound Fast Start = Enabled Codec For Outbound FastStart = G711 u-law 64K Call Classification = Use System Default Tunneled Protocol = QSIG Calling Party Transformations PreTransform Calling Party Number = 1360064 Calling Party Selection = Originator Calling Party Presentation = Default CallerID DN = Calling Party Number = 1360064 RouteGroup :RouteGroup Name= RG2 PreTransform Calling Party Number = 1360064 PreTransform Called Party Number = 914089027872 Calling Party Transformations External Phone Number Mask = Default Calling Party Mask = Prefix = Calling Party Number = 1360064 Called Party Transformations Called Party Mask = Discard Digits Instructions = Prefix = Called Number = 914089027872 Device :Type= InterClusterTrunk-NonGatekeeperControlled End Device Name = 10.77.31.231 PortNumber = 0 Device Status = UnKnown AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Inbound Fast Start = Disabled Outbound Fast Start = Disabled Call Classification = Use System Default Tunneled Protocol = QSIG Calling Party Transformations PreTransform Calling Party Number = 1360064 Calling Party Selection = Originator Calling Party Presentation = Default CallerID DN = Calling Party Number = 1360064 RouteGroup :RouteGroup Name= RG3 PreTransform Calling Party Number = 1360064 PreTransform Called Party Number = 914089027872 Calling Party Transformations External Phone Number Mask = Default Calling Party Mask = Prefix = Calling Party Number = 1360064 Called Party Transformations Called Party Mask = Discard Digits Instructions = Prefix = Called Number = 914089027872 Device :Type= CiscoASGateway End Device Name = SAA2433E7636576 PortNumber = 0 Device Status = UnKnown AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Device :Type= CiscoATGateway End Device Name = SAA498968343345 PortNumber = 0 Device Status = UnKnown AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Alternate Matches Note: Information Not Available Example 2 This example assumes the following setup in Cisco CallManager: Route Pattern—9.@ in partition 'SJPartition' Route Filter—RF-SJ (LONG-DISTANCE-DIRECT-DIAL EXISTS AND AREA-CODE == 408). This route pattern selects RouteList 'RL1'. RL1 uses RG1. RG1 configuration includes an Inter Cluster Trunk as 10.77.31.206, with route group level calling and called party transformations. Configure 10.77.31.206 gateway with CSS—ALL. (ALL CSS has DallasPartition and SJPartition) RG2 configuration includes an Inter Cluster Trunk 10.77.31.231, with QSIG tunneled protocol. RG3 configuration includes one CiscoAT Gateway and one CiscoAS Gateway. Route Pattern—9.@ in partition 'SJPartition', where: •Offnet Pattern (Outside Dial Tone) is checked •Require Forced Authorization Code is checked •Require Client Matter Code is checked •Authorization Level = 155 Associate the route pattern with the RL1 route list and route filter RF-SJ. Configure the Inter Cluster Trunk 10.77.31.206 as follows: •Tunneled Protocol—QSIG. •Call Classification—Use System Default. •InBound Fast Start—Disabled. •OutBound Fast Start—Enabled. •Codec For Outbound Fast Start—G711 mu-law 64k. Configure the Inter Cluster Trunk 10.77.31.231 as follows: •Tunneled Protocol—QSIG. •Call Classification—Use System Default. •InBound Fast Start—Disabled. •OutBound Fast Start—Disabled. Configure a phone with DN 254564. The phone's Ignore Presentation Indicators (internal calls only) check box is checked. Translation pattern 972813XXXX exists in partition 'DallasPartition' with Called Party Transformations configured with DN 254564. Provide Outside dial tone is not checked for the translation pattern. Use the following procedure to run this example: Procedure Step 1 Access Dialed Number Analyzer and choose Analysis > Trunks. Step 2 Find a list of gateways that are configured by using the procedure in the "Finding a Trunk" section. Step 3 From the list of records that displays in the Find and List Trunks window, choose gateway 10.77.31.206. The Trunk Information window displays. Step 4 In the Trunk Information window, enter 9728130064 in the Calling Party field. Step 5 In the Dialed Digits field, enter 9728135054. Step 6 Leave the default values in the Time Zone, Date, and Time drop-down list boxes. Step 7 Click Do Analysis. The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information. Step 8 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window. Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled. See Example 4-2 for the results. Example 4-2 Analysis Results for Example 2 Results Summary Calling Party Information Calling Party = 9728130064 Partition = Device CSS = ALL Line CSS = AAR Group Name = AARCSS = Dialed Digits = 9728135054 Match Result = RouteThisPattern Matched Pattern Information Pattern = 254564 Partition = Time Schedule = Called Party Number = 254564 Time Zone = InterDigit Timeout = NO Provide Outside Dial Tone = NO Call Flow TranslationPattern :Pattern= 972813XXXX Positional Match List = 254564 DialPlan = North American Numbering Plan Route Filter Filter Name = Filter Clause = PreTransform Calling Party Number = 9728130064 PreTransform Called Party Number = 9728135054 Calling Party Transformations External Phone Number Mask = NO Calling Party Mask = Prefix = CallingLineId Presentation = Default CallingName Presentation = Default Calling Party Number = 9728130064 ConnectedParty Transformations ConnectedLineId Presentation = Default ConnectedName Presentation = Default Called Party Transformations Called Party Mask = 254564 Discard Digits Instruction = Prefix = Called Number = 254564 Directory Number :DN= 254564 Partition = Call Classification = OnNet Forwarding Information ForwardAll : DN = VoiceMail = No CSS = ForwardBusy Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = ForwardNoAnswer Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = ForwardNoCoverage Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = CFDF : DN = VoiceMail = No CSS = Pickup Group Number = Device :Type= Cisco 7960 Device Status = UnKnown Device Name = SEP487698944444 Ignore Presentation Indicators = Enabled Alerting Name = AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Alternate Matches Note: Information Not Available Example 3 This example shows how hunt pilot information displays in the analysis results, if your dial plan configuration includes hunt lists. This sample assumes the following setup in Cisco CallManager: Hunt pilot—9043. 10 voice mail ports get configured from 90431 through 90440. Line Group VMLG includes the 10 ports. Hunt List VMHL includes Line Group VMLG. Forward Hunt No Answer setup is as follows: Use Personal Preference is checked. Destination = 30129. CSS = None. Forward Hunt Busy setup is as follows: Use Personal Preference is checked Destination = 30139 CSS = None Maximum Hunt Timer = 5 Use the following procedure to run this example: Procedure Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer. The Analyzer window displays. Step 2 In the Calling Party field, enter a calling party number (1000 displays by default). Step 3 In the Dialed Digits field, enter 9043. Step 4 In the Device Time Zone field, leave the default values. The local time and date that represent the time and date information from the operating system of the server where Cisco CallManager is installed displays by default. You can choose time and date settings that differ from the Cisco CallManager system time. Step 5 In the Time Zone, Date, and Time fields, leave the default settings. Step 6 Click Do Analysis. Step 7 The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information. Step 8 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window. Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled. See Example 4-3 for the results. The results section details only the Call Flow section that includes Hunt List information. Example 4-3 Analysis Results for Example 3 Results Summary Calling Party Information Calling Party = 1000 Partition = Device CSS = Line CSS = AAR Group Name = AARCSS = Dialed Digits = 9043 Match Result = RouteThisPattern Matched Pattern Information Pattern = 9043 Partition = Time Schedule = Called Party Number = 9043 Time Zone = End Device = VMHL Call Classification = OffNet InterDigit Timeout = YES Provide Outside Dial Tone = NO Call Flow Hunt Pilot :Pattern= 9043 Positional Match List = 9043 DialPlan = North American Numbering Plan Route Filter Filter Name = Filter Clause = Hunt Forward Settings Forward Hunt No Answer Use Personal Preferences = Yes Destination = 30129 Calling Search Space = Forward Hunt Busy Use Personal Preferences = Yes Destination = 30139 Calling Search Space = Maximun Hunt Timer = 5 Network Location = OffNet PreTransform Calling Party Number = 1000 PreTransform Called Party Number = 9043 Calling Party Transformations External Phone Number Mask = NO Calling Party Mask = Prefix = CallingLineId Presentation = Default CallingName Presentation = Default Calling Party Number = 1000 ConnectedParty Transformations ConnectedLineId Presentation = Default ConnectedName Presentation = Default Called Party Transformations Called Party Mask = Discard Digits Instruction = Prefix = Called Number = 9043 Hunt List :HuntListName= VMHL Line Group :LineGroupName= VMLG Directory Number :DN= 90431 Partition = Call Classification = OnNet Device :Type= Cisco Voice Mail Port Device Status = UnKnown Device Name = CiscoUM1-VI1 Ignore Presentation Indicators = Disabled Alerting Name = AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = + Directory Number :DN= 90432 + Directory Number :DN= 90433 + Directory Number :DN= 90434 + Directory Number :DN= 90435 + Directory Number :DN= 90436 + Directory Number :DN= 90437 + Directory Number :DN= 90438 + Directory Number :DN= 90439 + Directory Number :DN= 90440 Alternate Matches Note: Information Not Available Note The last section of the preceding sample shows detailed Directory Number information for the first port. Similar information displays for the remaining ports that are configured. Example 4 This example shows how time-of-day settings information displays in the analysis results, when the time zone settings for a phone is set to a specific time zone in Cisco CallManager Administration. In this example, the analysis uses the time zone, date, and time settings that the Analysis > Analyzer window specifies. This sample assumes the following setup in Cisco CallManager: Time Period—DNATimePeriod1 Configure DNATimePeriod1 as follows: •Start Time = 9.00 •End Time = 12.00 •Repeat Every = Year On: Jun 15 Time Schedule—DNATimeSchedule1 Configure DNATimeSchedule1 to DNATimePeriod1 Partition—DNAPartition1 Configure DNAPartition1 to DNATimeSchedule1 DNAPartition1 configuration must be as follows: •Time Zone = Specific Time Zone, (GMT+5.30) Bombay, Calcutta, Madras, New Delhi, Colombo Configure DNACSS1 with DNAPartition1. Phone—Configure an SEP000000036201 with DN 36201 Partition for the SEP000000036201 phone = DNAPartition1 Use the following procedure to run this example: Procedure Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer. The Analyzer window displays. Step 2 In the Calling Party field, enter a calling party number (1000 displays by default). Step 3 In the Dialed Digits field, enter 36201. Step 4 From the Calling Search Space drop-down list, choose DNACSS1. Step 5 From the Time Zone drop-down list, choose a specific time zone, (GMT+5.30) Bombay, Calcutta, Madras, New Delhi, Colombo. Step 6 From the Date drop-down list boxes, choose 2004, Jun, and 15 as the Cisco CallManager system date settings. Step 7 From the Time drop-down list boxes, choose 11:30:0:0 as the Cisco CallManager system time settings. Step 8 Click Do Analysis. Step 9 The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information. Step 10 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window. Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled. See Example 4-4 for the results. Example 4-4 Analysis Results for Example 4 Results Summary Calling Party Information Calling Party = 1000 Partition = Device CSS = Line CSS = DNACSS1 AAR Group Name = AARCSS = Dialed Digits = 36201 Match Result = RouteThisPattern Matched Pattern Information Pattern = 36201 Partition = DNAPartition1 Time Schedule = DNATimeSchedule1 Called Party Number = 36201 Time Zone = (GMT+05:30) Bombay, Calcutta, Madras, New Delhi, Colombo InterDigit Timeout = NO Provide Outside Dial Tone = NO Call Flow Directory Number :DN= 36201 Partition = DNAPartition1 Call Classification = OnNet Forwarding Information ForwardAll : DN = VoiceMail = No CSS = ForwardBusy Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = ForwardNoAnswer Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = ForwardNoCoverage Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = CFDF : DN = VoiceMail = No CSS = Pickup Group Number = Device :Type= Cisco 7960 Device Status = UnKnown Device Name = SEP000000036201 Ignore Presentation Indicators = Disabled Alerting Name = AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Alternate Matches Note: Information Not Available Example 5 This example shows how time-of-day settings information displays when a call is made between two phones in the same time period with the time zone specified as Originating Device. This example assumes the following setup in Cisco CallManager: Configure a Time Period DNATimePeriod1 as follows: Start Time=9.00 End Time=12.00 Repeat Every Year=Jun 15 Configure a Time schedule DNATimeSchedule1 as follows: Time period=DNATimePeriod1 Insert a partition called DNAPartition1. Configure DNAPartition1 as follows: •Time Schedule=DNATimeSchedule1 •Time Zone=Originating Device Insert a Calling Search Space called DNACSS-1. Add the DNAPartition1 partition to this CSS. Insert a Phone SEP000000036201 and assign a DN, 36201, to it. Choose DNAPartition1 as the partition for the phone. Use the following procedure to run this example Procedure Step 1 Access Dialed Number Analyzer and choose Analysis > Analyzer. The Analyzer window displays. Step 2 In the Calling Party field, enter a calling party number (100 0 displays by default). Step 3 In the Dialed Digits field, enter 36201. Step 4 From the Calling Search Space drop-down list, choose DNACSS1. Step 5 From the Device Time Zone drop-down list box, choose Greenwich Mean Time (GMT); Dublin, Edinburgh, London, Lisbon. Step 6 From the Time Zone drop-down list, choose (GMT+05:30): Bombay, Calcutta, Madras, New Delhi, Colombo. Step 7 From the Date drop-down list boxes, choose 2004, Jun, and 15. Step 8 From the Time drop-down list boxes, choose 15:30:0:0. Step 9 Click Do Analysis. Step 10 The results display in a new window that is called Dialed Number Analyzer Results window. The Results Summary section expands and shows summary information. Step 11 Click Expand All to expand all the nodes in the window and view all values or click Collapse All to close all the nodes in the window. Note When the Dialed Number Analyzer Results window first displays, both Expand All and Collapse All buttons are enabled. See Example 4-5 for the results. Example 4-5 Analysis Results for Example 4 Results Summary Calling Party Information Calling Party = 1000 Partition = Device CSS = Line CSS = DNACSS1 AAR Group Name = AARCSS = Dialed Digits = 36201 Match Result = RouteThisPattern Matched Pattern Information Pattern = 36201 Partition = DNAPartition1 Time Schedule = DNATimeSchedule1 Called Party Number = 36201 Time Zone = (GMT) Greenwich Mean Time; Dublin, Edinburgh, London, Lisbon InterDigit Timeout = NO Provide Outside Dial Tone = NO Call Flow Directory Number :DN= 36201 Partition = DNAPartition1 Call Classification = OnNet Forwarding Information ForwardAll : DN = VoiceMail = No CSS = ForwardBusy Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = ForwardNoAnswer Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = ForwardNoCoverage Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = CFDF : DN = VoiceMail = No CSS = Pickup Group Number = Device :Type= Cisco 7960 Device Status = UnKnown Device Name = SEP000000036201 Ignore Presentation Indicators = Disabled Alerting Name = AAR Group Name = AAR Calling Search Space = AAR Prefix Digits = Alternate Matches Note: Information Not Available Related Topics •Simple Analysis by Using the Analyzer Window •Analysis by Using Phones •Analysis by Using Gateways •Analysis by Using Trunks •Understanding Analysis Output •Viewing Dialed Number Analyzer Output Files Results Summary The Results Summary section of the analysis results provides a summary of the dialed digits analysis results and displays Calling Party Information and Matched Pattern Information. Note Fields that do not contain a description in this section display data as specified in Cisco CallManager Administration. For information on these fields, see the Cisco CallManager Administration Guide. Calling Party Information Calling Party—The calling party number after all the transformations are applied. Partition—The Partition to which the final calling party belongs. Device CSS—The Calling Search Space that is associated with the calling device. Line CSS—The Calling Search Space that is associated with the calling party number. AAR Group Name—The automated alternate routing (AAR) group to which this pattern belongs. AARCSS—The calling search space that the calling party device uses when performing AAR. Dialed Digits—The digits that the user entered in the Dialed Digits field. Match Result—Specifies whether the call will be routed or blocked. RouteThisPattern or BlockThisPattern displays. Note Line and device specific information display in the results when you perform analysis by using Analysis > Phones, Analysis > Gateways and Analysis > Trunks windows because a specific device was chosen as a calling entity. When you perform analysis from the Analysis > Analyzer window, you enter a calling party number that is not linked to any device that is configured in Cisco CallManager. Line and device specific information does not display in the Results Summary section of the analysis results that are obtained by using this procedure. Matched Pattern Information •Pattern—Specifies the ultimate pattern matches. •Partition—The partition where this ultimate pattern exists. •Time Schedule—The name of the time schedule chosen for the partition where this pattern exists. Pattern Type—The Meet-Me Conference Number, Call Park Code Number, Call Pickup Number display. This field displays only when the dialed digits match a feature pattern type. Called Party Number—The final called party number. Time Zone—Time zone information of the device that is associated with the matched pattern. Interdigit Timeout—Specifies the time delay in routing the call to the final device. End Device—The final device to which the call was routed. This field displays only if the dialed digits match a route pattern. OffNetPattern (OutsideDialTone)—Displays OffNet/OnNet, depending on whether this field is checked or unchecked in Cisco CallManager Administration. Note For intercept patterns, device-specific information will not display, and instead, a tag that indicates the Pattern Type will display. Related Topics •Understanding Analysis Output •Analysis Results Examples •Call Flow Details •Alternate Matches Call Flow Details The Call Flow section of the results provides detailed information about all the stages that a call goes through, such as translation patterns, route patterns, route lists, route groups, and end devices. Use the following topics to understand the results that display in the Call Flow section: •Translation Pattern •Route Pattern •Hunt Pilot •Directory Number •Device Information Note Fields that do not contain a description in this section display data as specified in Cisco CallManager Administration. For information on these fields, see the Cisco CallManager Administration Guide. –Calling Party Transformation—The transformation that is specific to the end device such as the following transformations: •Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the End Device are applied. •Calling Party Selection—The selection that can be Originator/Last Redirect Number, and so on. •Calling Party Presentation •Calling Party Number—The calling party number after the calling party transformation settings of the End Device are applied. Translation Pattern The Translation Pattern section provides information on dialed digits, if the dialed digits match a configured translation pattern. The following fields display: •Hunt Pilot :Pattern—The hunt pilot pattern that is matched. •Positional Match List—The position of the dialed digits in association with a pattern. •DialPlan—The Numbering Plan in which this translation pattern resides. •Route Filter—The route filter that is applied to the dialed digits. –Filter Name—The Route Filter name that is associated with the Translation Pattern. –Filter Clause—The Route Filter Clause that is associated with the Translation Pattern. •Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the Translation Pattern are applied. •Pretransform Called Party Number—The called party number before the called party transformation settings of the Translation Pattern are applied. •Calling Party Transformations: This section displays calling party transformation settings of the Translation Pattern. –External Phone Number Mask—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. –Calling Party Mask –Prefix –Calling Party Presentation –Calling Party Number—The calling party number after the calling party transformation settings of the Translation Pattern are applied. •Called Party Transformations. This section displays the called party transformation settings of the Translation Pattern, such as the following settings: –Called Party Mask –Discard Digit Instructions –Prefix –Called Number—The calling party number after the calling party transformation settings of the Translation Pattern are applied. Route Pattern The Route Pattern subsection provides information on route pattern details for the dialed digits, if the dialed digits match a route pattern. •Route pattern :Pattern—The matched route pattern. •Positional Match List—Displays the position of the dialed digits in association with a pattern. •DialPlan—The Numbering Plan in which this route pattern resides. •Route Filter –Filter Name—The Route Filter name that is associated with the Route Pattern. –Filter Clause—The Route Filter Clause that is associated with the Route Pattern. •Require Forced Authorization Code—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. •Authorization Level—Displays the authorization level that is specified in Cisco CallManager Administration. •Require Client Matter Code—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. •Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the Route Pattern are applied. •Pretransform Called Party Number—The called party number before the called party transformation settings of the Route Pattern are applied. •Calling Party Transformations. Displays the calling party transformation settings of the Route Pattern, such as the following settings: –External Phone Number Mask—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. –Calling Party Mask –Prefix –Calling Party Presentation –Calling Party Number—The calling party number after the calling party transformation settings of the Route Pattern are applied. •Called Party Transformations. Displays the called party transformation settings of the Route Pattern, such as the following settings: –Called Party Mask –Digit Discarding Instructions –Prefix –Called Number—The calling party number after the calling party transformation settings of the Route Pattern are applied. Hunt Pilot This section includes information on Hunt Lists, Line Groups, and Hunt Forward Settings. •Hunt List: HuntList Name—The name of the Route List. •LineGroup: LineGroup Name—The name of the Route Group that is contained within this Route List. •Pretransform Calling Party Number—The calling party number before the calling party transformation settings of the Route Group are applied. •Pretransform Called Party Number—The called party number before the called party transformation settings of the Route Group are applied. •Calling Party Transformations. This section displays the calling party transformation settings of the Route Group, such as the following settings: –External Phone Number Mask—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. –Calling Party Mask –Prefix –Calling Party Number—The calling party number after the calling party transformation settings of the Route Group are applied. •Called Party Transformations. This section displays the called party transformation settings of the Route Group such as the following settings: –Called Party Mask –Discard Digit Instructions –Prefix –Called Number—The calling party number after the calling party transformation settings of the Route Group are applied •Hunt Forward Settings –Forward Hunt No Answer—The call forwarding settings when a hunt pilot is matched. Use Personal Preferences—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. Destination—Displays the destination number for the call forward when there is no answer. Calling Search Space—Displays the Calling Search Space where the forward destination, either Busy or No Answer, whichever is applicable, is present. –Forward Hunt Busy— Use Personal Preferences—Displays Yes/No, depending on whether this field is checked or unchecked in Cisco CallManager Administration. Destination—Displays the destination number for the call forward when there is no answer. Calling Search Space—Displays the Calling Search Space where the forward destination, either Busy or No Answer, whichever is applicable, is present. •Maximum Hunt Timer—Displays the value that is specified in the Maximum Hunt Timer field in Cisco CallManager Administration. Directory Number The Directory Number (DN) subsection provides details about the DN, if the dialed digits match a DN number. •Directory Number: DN—The directory number. –Partition—The partition in which the DN resides. –Device Location –Forwarding Information—Displays the forwarding settings that are associated with the DN. The forwarding behavior differs depending on whether the call is from an internal or external user. The following forwarding settings display: –Forward All : DN –Forward Busy Internal : DN External : DN –Forward No Answer Internal : DN External : DN –Forward No Coverage Internal : DN External : DN Device Information •Device :Type—The type of device. –End Device Name—The name of the endpoint device. –Device Status—Indicates whether the status of the end device is Registered/Unregistered/Unknown. –AAR Group Name—The AAR Group to which this device belongs. –AAR Calling Search Space—The AAR Calling Search Space where this end device belongs. –AAR Prefix Digits—The prefix digits that are used for automated alternate routing within this AAR group. –Caller ID DN—The mask that is used to format the caller ID on outbound calls from a trunk. •Inbound Fast Start—Displays Enabled/Disabled depending on whether the Inbound Fast Start field is checked or unchecked in Cisco CallManager Administration. •Outbound Fast Start—Displays Enabled/Disabled depending on whether the Outbound Fast Start field is checked or unchecked in Cisco CallManager Administration. •Codec For Outbound FastStart—Displays the value specified in the Codec for Outbound FastStart in Cisco CallManager Administration. •Call Classification—Displays OffNet/OnNet/Use System Default/None, depending on the value that is chosen in Cisco CallManager Administration. •Tunneled Protocol—Displays QSIG/none depending on the value that is configured in the Tunneled Protocol field in Cisco CallManager Administration. •Ignore Presentation Indicators—Indicates if presentation settings of the calling party must be ignored for internal calls. Alerting Name—Indicates the name of the alerting party that is chosen for a phone in Cisco CallManager. Related Topics •Understanding Analysis Output •Analysis Results Examples •Results Summary •Alternate Matches Alternate Matches This section provides all the alternate matches that the analysis process looked up while finding the best match for the dialed digits. Note Fields that do not contain a description in this section display data as specified in Cisco CallManager Administration. For information on these fields, see the Cisco CallManager Administration Guide. The output displays in the following format: •Partition : Name—The partition where the route pattern exists. •Pattern –Route Pattern—The name of the route pattern. –Pattern Type—The pattern type, either Translation or Enterprise. –Network Location—Indicates the network location of the route pattern, either OffNet or OnNet. –CallManager Device Type—Specifies whether the device matched is an Access Device or a User Device. Note Other parameters may display, depending on the settings that are associated with the pattern. Related Topics •Understanding Analysis Output •Analysis Results Examples •Results Summary •Call Flow Details Dumping Digit Discard Instructions and Dialing Patterns Each Cisco CallManager dial plan configuration has called party transformation information that includes discard digit instructions (DDIs). Dialed Number Analyzer allows you to view the DDIs that are specified for the Cisco CallManager dial plan that you are analyzing. The tool also allows you to view all the dialing patterns that are associated with gateways and phones that are configured in the Cisco CallManager dial plan that you are analyzing. Use the following procedure to view DDIs or dialing pattern information that is specified for a dial plan. Procedure Step 1 Choose Analysis > Dump DA Information. The Dump Options window displays. Step 2 In the Select Dump Option field, click the Discard Digit Instructions or the Dialing Forest radio button. Step 3 In the Select Viewing Option field, do one of the following actions: •To view the discard digit instructions or dialing forest information in the browser window, click the Open File in Browser button. •To save the discard digit instructions or dialing forest information to a file, click the Save File radio button. Step 4 Click Finish. If you chose to view the discard digit instructions or dialing forest information on the browser, the results display in the same window. If you chose to save the discard digit instructions or dialing forest information to a file, the File Download dialog box displays. Use the following procedure to save the file: a. Click Save. The Save As dialog displays. Browse to a location on your PC where you want to save the file. b. Click Save. The result gets saved as a text file called DialPlanForest.txt or DiscardDigitInstructions.txt, depending on whether you chose discard digit instructions or dialing forest in Step 2. Related Topic •Understanding Analysis Output Viewing Dialed Number Analyzer Output Files When you store results of analysis that you have performed by using phones, gateways, or trunks, the results get saved as XML files on your PC. You can retrieve and view these output files on the browser by using Dialed Number Analyzer. Use the following procedure to view output files. Procedure Step 1 Choose Analysis > View File. Step 2 The View File window displays. Step 3 Click Browse in the Select a File to View field. Browse to the location on your PC where the required output file is located and choose it. An example of an output file follows. DialedNumberAnalyzerOutput_1001.xml where 1001 represents the dialed digits that are specified during analysis. Step 4 Click View File. The output file displays in a new window called Dialed Number Analyzer Results. The Results Summary section expands to show the summary. Click the plus icon to expand the required results section to view the details. Step 5 Close the Dialed Number Analyzer Results window after viewing the results. Related Topics •Simple Analysis by Using the Analyzer Window •Analysis by Using Phones •Analysis by Using Gateways •Analysis by Using Trunks •Understanding Analysis Output Viewing Trace Configuration Files Trace files provide a means of tracking problems in the functioning of a tool. The system writes trace files for Dialed Number Analyzer to the server on which Dialed Number Analyzer is installed when you install Dialed Number Analyzer. You can choose to enable or disable the writing of trace files feature from the Service Control window in Dialed Number Analyzer. This section describes the procedure to enable and disable the writing of trace files. Use the following procedure to enable the feature. Procedure Step 1 In Dialed Number Analyzer, choose Service > Control Center. The Control Center window displays the current status of the Trace Configuration option. Step 2 If the current status is Disabled, click Enable in the corresponding Action column. The system enables the feature, and the trace files get written to the following location on your PC: C:\Program Files\Cisco\Trace\DNA The file appears in the following format: DNA_indexNo.txt where <indexNo> ranges from 1- 250. Use the following procedure to disable the writing trace files feature. Procedure Step 1 In Dialed Number Analyzer, choose Service > Control Center. The Control Center window displays the current status of the Trace Configuration option. The current status displays as Enabled. Step 2 In the corresponding Action column, click Disable. This action means that the feature is disabled.
	© 1992-2008 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.