Cisco IOS Voice Troubleshooting and Monitoring Guide, Release 12.4
Voice Performance Statistics on Cisco Gateways
Downloads: This chapterpdf (PDF - 568.0KB) The complete bookPDF (PDF - 2.89MB) | Feedback

Voice Performance Statistics on Cisco Gateways

Table Of Contents

Voice Performance Statistics on Cisco Gateways

Prerequisites for Voice Performance Statistics on Cisco Gateways

Restrictions for Voice Performance Statistics on Cisco Gateways

Information About Voice Performance Statistics on Cisco Gateways

Basic Terminology and Feature Design

What Are the Types of Accounting Statistics?

What Are the Types of Signaling Statistics and Aggregation Levels?

What Are IECs?

Management of the Statistical Collection

What Are the Allowable Time Ranges?

What Are Thresholds?

What Are the Allowable Storage Capacities?

How Is Memory Used?

Management of the Archive Process

Display of Records and Time Ranges

What Records Are Displayed Since System Reset or Reboot?

What Time Ranges Are Displayed?

Voice Interface Changes During Call-Statistics Collection Periods

Addition or Removal of a Voice Port

Configuration Change of Any Trunk Group

Benefits of Voice Performance Statistics on Cisco Gateways

Configuring Voice Performance Statistics on Cisco Gateways

Summary of Configuration Tasks

Configuring the Duration and Time Periods of Call Statistics on the Gateway

Configuring the Gateway to Collect Call Statistics on a Periodic Basis

Configuring the Gateway to Collect Call Statistics Since the Last Reset

Configuring the Gateway to Collect Call Statistics for a Specific Time Interval

Configuring the Gateway to Collect Signaling Statistics

Enabling the Gateway to Collect Signaling Statistics

Configuring the Minimum Call Duration and Signaling Thresholds

Disabling the Collection of Signaling Statistics

Displaying the Signaling Statistics for Each Aggregation Level

Clearing Signaling Statistics

Configuring the Gateway to Collect VoIP AAA Accounting Statistics

Prerequisites

Restrictions

Enabling the Collection of VoIP AAA Accounting Statistics on the Gateway

Configuring a Designated Server Group for a Broadcast Method List

Disabling the Collection of VoIP AAA Accounting Statistics

Displaying the VoIP AAA Accounting Statistics

Clearing the VoIP AAA Accounting Statistics

Troubleshooting Tips for VoIP AAA Accounting Statistics

Managing the Collection of Voice Statistics

Configuring the FTP Server to Enable Archiving of Statistics from the Gateway

Configuring the Gateway to Archive Statistics to an FTP Server

Configuring the Gateway to Archive Statistics to a Syslog Server

Displaying Memory Usage

Displaying All Statistics and Pushing Them to an FTP or Syslog Server

Clearing the Collected Call Statistics

Monitoring the Statistical Reporting

Configuration Examples for Voice Performance Statistics on Cisco Gateways

User-Specific Configurations for Call Statistic Collection: Example

Manually Clearing Statistics: Example

Collection of Aggregation-Level Statistics: Example

Memory Usage: Example

Collection of Statistics Since System Reset: Examples

Designated Server Group: Example

Location of the FTP Server: Example

Maximum File Size for the Syslog Server: Example

Maximum Duration for Storage: Example


Voice Performance Statistics on Cisco Gateways


The Voice Performance Statistics on Cisco Gateways feature enables the collection of voice call signaling statistics and VoIP AAA accounting statistics based on user-configured time ranges. The statistics can be displayed on your console or formatted and archived to an FTP or syslog server. This feature can assist you in diagnosing performance problems on the network and identifying impaired voice equipment. This chapter contains the following topics:

Prerequisites for Voice Performance Statistics on Cisco Gateways

Restrictions for Voice Performance Statistics on Cisco Gateways

Information About Voice Performance Statistics on Cisco Gateways

Configuring Voice Performance Statistics on Cisco Gateways

Configuration Examples for Voice Performance Statistics on Cisco Gateways

Prerequisites for Voice Performance Statistics on Cisco Gateways

Your gateway must be configured to support VoIP and must be functioning properly.

Restrictions for Voice Performance Statistics on Cisco Gateways

This feature does not support Media Gateway Control Protocol (MGCP).

This feature does not support parsing, presentation, or analysis of syslog files.

The integrity of statistical information in the syslog files is not guaranteed because of unreliable User Datagram Protocol (UDP) transport.

If the gateway clock needs to be synchronized after the gateway is reset or rebooted or during Network Time Protocol (NTP) client synchronization, there may be a problem for collection during the collection intervals.

The call-statistics data is dependent on the start and end time of the interval; that is, the collection is time driven, not event driven. The following two situations will result in erroneous call-statistics data:

Clock reset during a collection interval.

Clock set to a time during an already specified interval.

To avoid any call-statistics data from being collected within an incomplete interval, this feature reports only call-statistics data that is collected during a complete interval. This includes call-statistics data that is pushed to an FTP server or stored on a gateway.

This feature cannot assure accuracy or consistency of the reports generated when large clock updates occur during a batch reporting period.

Call statistics cannot be accessed using RADIUS protocols.

The signaling behavior of two-stage non-Direct-Inward-Dialing (non-DID) ISDN calls using a default session application is not supported.

Digital Signal 0 (DS0) is not supported.

Information About Voice Performance Statistics on Cisco Gateways

To configure the Voice Performance Statistics on Cisco Gateways feature, you should understand the following:

Basic Terminology and Feature Design

Management of the Statistical Collection

Management of the Archive Process

Display of Records and Time Ranges

Voice Interface Changes During Call-Statistics Collection Periods

The benefits of this feature are listed in the "Benefits of Voice Performance Statistics on Cisco Gateways" section.

Basic Terminology and Feature Design

The Voice Performance Statistics on Cisco Gateways feature is designed to include many options for collecting, archiving, and displaying call statistics records, which include PSTN interface/port statistics, IP interface statistics, and counts of RADIUS accounting messages. This feature also enables counts of Cisco IOS generated internal error codes (IECs). The basic terminology that describes the functionality of the feature is explained in the subsections that follow.

The following are feature options:

Counting accounting records (messages to and from RADIUS servers).

Collecting various signal-layer (IP and PSTN interfaces) statistics from individual gateway ports.

Displaying the signaling statistics at different aggregation levels.

Collecting IECs.

Collecting the statistics at user-configured time intervals.

Archiving the statistics to an FTP or syslog server and formatting the output.

Displaying the statistics on a console.

Displaying the available memory and the memory that has been used for the collection of records.

Specifying thresholds for packet jitter, lost packets, and packet latency.

Specifying the length of time to be used as the maximum call duration.

Specifying a maximum time for which to store the statistics in system memory.

This section has the following subsections:

What Are the Types of Accounting Statistics?

What Are the Types of Signaling Statistics and Aggregation Levels?

What Are IECs?

What Are the Types of Accounting Statistics?

Accounting record statistics are counts of RADIUS messages that are transmitted to and received from a RADIUS server. They can be collected by method list, type of RADIUS message (for example, starts, interim updates, and/or stops), and call-leg interface association (PSTN or IP). This feature can be configured to count all of these message types or only a subset of them.

A method list is a sequential list used by the RADIUS client on the gateway that defines the authentication methods used to authenticate a user. For the purposes of the Voice Performance Statistics on Cisco Gateways feature, you are required to specify only the name of the method list on the gateway.

Once enabled and configured, the feature counts RADIUS messages on both inbound and outbound call legs. Each time a RADIUS accounting message is received by the gateway, it is counted as successful if it is accepted and processed by the RADIUS agent on the gateway; each time a RADIUS accounting message is transmitted by the gateway, it is counted as passed if an ACK comes back from the RADIUS server.

You can also specify that accounting messages be collected from a broadcast method list, in which case you can set all the server groups that are in a method list to monitor the server group acknowledgements.

What Are the Types of Signaling Statistics and Aggregation Levels?

The signaling statistics are collected at the port level, but can be displayed at various aggregation levels.

The aggregation levels are hierarchical. The highest level is a summary of total statistics for all aggregation levels on the gateway, whereas the lowest level provides statistics for each voice port. Statistics can also be collected for the following aggregation levels:

Gateway level

VoIP level

PSTN level

Trunk group level

Voice-port level

An example of collected statistics at the different aggregation levels for a PSTN statistic labeled "X" is as follows:

When the aggregation level is gateway: X = 4

When the aggregation level is trunk group:

Trunk group A (configured ports 1 and 3): X = 3

Trunk group B (configured ports 2 and 4): X = 1

When the aggregation level is port:

Port 1: X = 1

Port 2: X = 0

Port 3: X = 2

Port 4: X = 1

The following are supported call-statistics fields that can be collected on Cisco gateways:

Incoming calls—All incoming call attempts, whether successful or not.

Incoming calls answered by the gateway—Incoming calls that were answered.

Incoming calls rejected by the gateway—Incoming calls that, for whatever reason, failed.

Outgoing calls attempted—Outgoing calls regardless of whether they were successful.

Outgoing calls that receive answers—Calls that were answered.

Outgoing calls fail—Calls that failed.

Total duration of all incoming and outgoing calls—Total duration from outgoing seizure to disconnect.

Total duration of incoming and outgoing answered calls—Total connected time: from answer to disconnect.

Originating side disconnected before outgoing calls connected.

Number of incoming and outgoing calls whose connected time is less than the configured minimum call duration (MCD).

Number of answered incoming and outgoing calls terminated with any cause codes other than "normal."

Total duration (after the dial delay) on incoming calls—Defined as "alert sent time-setup in time."

Total duration (after the dial delay) on outgoing calls—Defined as "alert received time-setup out time."

Total setup delay duration—Defined as "setup out time—setup in time."

IP-specific statistic fields (exist only in the IP-level statistics):

Number of calls losing more than the configured number of packets—The default is 1000.

Number of calls encountering more than the configured amount of latency—The default is 250 milliseconds.

Number of calls encountering more than the configured amount of jitter—The default is 250 milliseconds.

Number of incoming and outgoing calls disconnected with each cause code—The cause codes are defined in the Call Control Application Programming Interface (CCAPI) and in the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) standard Q.850.

What Are IECs?

Cisco IOS generated internal error codes (IECs) are gateway-detected errors that cause the gateway to release or refuse a call. IECs enhance troubleshooting for VoIP networks by helping to determine the source and reason for call termination.

Management of the Statistical Collection

The management of statistical collection involves time ranges, thresholds, storage capacities, and memory usage. This section has the following subsections:

What Are the Allowable Time Ranges?

What Are Thresholds?

What Are the Allowable Storage Capacities?

How Is Memory Used?

What Are the Allowable Time Ranges?

The Voice Performance Statistics on Cisco Gateways feature enables you to configure time ranges to capture statistics. The time ranges are as follows:

From the last reset time to the present. You can examine the statistics using the show voice statistics command and reset the statistics using the clear voice statistics csr command.

By specific start and end time. That is, a set amount of minutes after the configuration time for preparation of the resource allocation of the gateway.

By periodic intervals, with an optional total duration. Allowable intervals are 5 minutes, 15 minutes, 30 minutes, 1 hour, and 1 day. The optional total duration is unlimited but must be a multiple of the specified interval. For example, the interval could be 15 minutes, and the total duration could be 3 hours.

What Are Thresholds?

The following three thresholds can be configured to customize how you measure the voice signaling statistics for your network configuration:

Packet jitter

Packet latency

Lost packets

These thresholds are all pre-configured with default settings. The jitter, latency, and lost packets thresholds only apply to IP statistics. In addition, you can configure the minimum call duration (MCD) value for determining which calls are measured during the statistics collection.

Packet Jitter

Jitter is a variation in the delay of received packets. At the sending side, packets are sent in a continuous stream, spaced evenly apart. Because of network congestion, improper queueing, or configuration errors, this steady stream can be interrupted by delays between packets.

You can specify the threshold at which a record will not be collected. For example, if you have set a threshold of 250 milliseconds and a delay exceeds that threshold, the message is not collected.

Packet Latency

Packet latency is the amount of time that it takes a packet to go from its source to its destination. You can specify the threshold at which a record will not be collected. For example, the gateway can be configured to drop messages that take more than 250 milliseconds to reach the destination.

Lost Packets

Lost packets are a result of jitter that is so great that it causes packets to be out of the range of the jitter buffer. These packets are discarded. You can specify the threshold for lost packets in milliseconds.

Minimum Call Duration

Using the minimum call duration (MCD) value, you can configure the gateway to collect statistics for calls that last a minimum amount of time. For example, if you configure the MCD value to 2 milliseconds, the gateway counts the number of incoming or outgoing calls with a connect time less than 2 milliseconds.

What Are the Allowable Storage Capacities?

The Voice Performance Statistics on Cisco Gateways feature allows you to specify how long the gateway will store the statistics. You can specify a number of days, hours, or minutes.

How Is Memory Used?

You can display how much system memory is being used when statistics are being collected, how much system memory is available, and how much system memory is estimated for future use by using the show voice statistics memory-usage command. The command displays all memory usage for accounting and signaling by fixed interval and since a system reset or reboot. The output includes the number of call statistics records per interval, each record size, the approximate memory used, and the allocated memory for future use.

Management of the Archive Process

The FTP or syslog server archive process is used to download statistics to a file on the server for further processing, presentation, and analysis. The download to the server is configured using the command-line interface (CLI). When the specified end time of collection is reached, the gateway downloads the statistics data to the provisioned server. Using FTP, the gateway formats the statistics in an ASCII file and transfers the file to a Cisco Networking Services Performance Engine (CNS-PE). Using the syslog server, gateways send the information in syslog messages, and you can specify the message size.


Note Because of unreliable UDP transport, the integrity and completeness of the call statistics in the syslog files are not guaranteed.


Figure 56 shows the components as used by this feature.

Figure 56 Syslog and FTP Servers and the CNS-PE

You can format the output to display with specified record separators. The separator can be a space, tab, new line, or ASCII character.

Display of Records and Time Ranges

You can display statistics by accounting method lists, by aggregation levels, by numbered intervals (time ranges), and/or since the last system reset or reboot. This section has the following subsections:

What Records Are Displayed Since System Reset or Reboot?

What Time Ranges Are Displayed?

What Records Are Displayed Since System Reset or Reboot?

You can display the collected records since a system reset or reboot including accounting and/or signaling (aggregation level), and intervals (time ranges). There are show commands to display all signaling statistics that were collected since the last reset or reboot of the system. You can specify a concise or verbose display, and you can configure the gateway to push the statistics to the FTP or syslog server.

Displaying Accounting Statistics

You can use the show voice statistics csr since-reset accounting command to display the method list by RADIUS server, PSTN incoming and outgoing records that have passed and failed, and the IP incoming and outgoing records that have passed and failed.

Displaying Aggregation-Level Statistics

You can use the show voice statistics csr since-reset aggregation-level command to display all the collected statistics for every aggregation level or just the statistics for a specific level (gateway, IP, PSTN, trunk group, or voice port).

What Time Ranges Are Displayed?

You can use the show voice statistics interval-tag command to display the start and end times by a numbered interval. To display the time ranges by voice port, you can use the show voice statistics csr interval aggregation command.

Voice Interface Changes During Call-Statistics Collection Periods

It is recommended that you do not change the voice interface configuration during the period when call statistics are being collected. It is also recommended that during the period when call statistics are being collected, the following configuration changes not take place:

Adding or removing a PRI or DS1 group

Adding or removing a trunk group

Adding or removing a trunk in a trunk group


Note It is recommended that any existing call-statistics collection be stopped and set to zero before any configuration modification is made to any of the voice interfaces.


This section has the following subsections:

Addition or Removal of a Voice Port

Configuration Change of Any Trunk Group

Addition or Removal of a Voice Port

The following scenarios apply to a voice port whether or not it is in any trunk group:

The addition of a PRI or DS1 group, Foreign Exchange Station (FXS), Foreign Exchange Office (FXO), or ear and mouth (E&M) device.

The removal of a PRI or DS1 group, FXS, FXO, or E&M device.

If a new voice interface is added during any collection period, new entries that correspond to the new voice interface are added in the statistics collected for that collection period.

If an existing voice interface is removed during any collection period, the statistics that correspond to that voice interface are still kept in the set. The statistics are frozen (that is, nothing more is added) after the time that the voice interface is removed. Gateways still send the statistics for the removed interface to the CNS-PE or syslog server.

In either of the above scenarios, the statistics for PSTN ports include all the collected data at the DS1 or channel associated signaling (CAS) level, except the statistics for interfaces added or removed during the collection period.

Configuration Change of Any Trunk Group

The following scenarios apply when there is a configuration change of any trunk group:

The addition or removal of a DS1 or CAS group into or from a trunk group.

If you are adding a DS1 or CAS group to a trunk group during any collection period, the collection process moves the associated statistics from the upper aggregation level (PSTN) to the trunk-group level. The call statistics before the configuration change time are also totalled to the statistics of the trunk-group level at the end of the collection period. In this case, the statistics of the trunk-group level can exceed the limit. However, the PSTN-level statistic is still accurate.

If you are removing a DS1 or CAS group from a trunk group during any collection period, the collection process removes the trunk-group level of the PSTN aggregation. In contrast to the scenario of adding a DS1 or CAS group, the statistic of the trunk-group level is under the limit.

The addition or removal of a trunk group.

If you are adding a new trunk group (one that contains a trunk or trunks) to a gateway during any collection period, the existing statistics of all member trunks aggregate to the trunk-group level statistic. That is, the statistic of the trunk-group level is over its limit. The PSTN-level call statistics are still accurate.

If you are removing an existing trunk group from a gateway during any collection period, the existing statistics of all member trunks are totaled at the configuration change time. The statistics of the trunk-group level and of the PSTN level are accurate.


Note The inaccurate call statistics that can result from the four scenarios that are listed above are acceptable because the transient information during the configuration change is often unusable.


Benefits of Voice Performance Statistics on Cisco Gateways

Gateway call statistics can be audited or compared against the statistics of other network devices for improved monitoring.

Malfunctioning DSPs (DS1 only) can be discovered.

Discrepancies between RADIUS records sent by the gateway and received and reported on the server can be uncovered.

Potential lost revenue can be highlighted.

Call-success rates and accuracy of reports can be determined.

Configuring Voice Performance Statistics on Cisco Gateways

This section contains the following procedures:

Configuring the Duration and Time Periods of Call Statistics on the Gateway (required)

Configuring the Gateway to Collect Signaling Statistics (required)

Configuring the Gateway to Collect VoIP AAA Accounting Statistics (required)

Configuring the FTP Server to Enable Archiving of Statistics from the Gateway (optional)

Managing the Collection of Voice Statistics

Configuring the Gateway to Archive Statistics to an FTP Server (optional)

Configuring the Gateway to Archive Statistics to a Syslog Server (optional)

Displaying Memory Usage (optional)

Displaying All Statistics and Pushing Them to an FTP or Syslog Server (optional)

Clearing the Collected Call Statistics (optional)

Monitoring the Statistical Reporting (optional)


Note If you need to obtain statistical information since reboot, the configuration should be stored in NVRAM before you restart the gateway.


Summary of Configuration Tasks

There are two general areas of configuration—one for the collection of signaling statistics and one for the collection of accounting statistics. The tasks required will depend on whether you configure the gateway to collect signaling statistics only, accounting statistics only, or both signaling and accounting statistics.

Required Task for Collection of All Call Statistics


Step 1 Configure the duration or time period for when call statistics are collected on the gateway. See the "Configuring the Duration and Time Periods of Call Statistics on the Gateway" section.


Required Task for Signaling Statistics


Step 1 Configure the gateway to support the collection of signaling statistics. See the "Enabling the Gateway to Collect Signaling Statistics" section.


Optional Task for Signaling Statistics

Configure the call statistics record signaling parameters, changing the default values as needed. See the "Configuring the Minimum Call Duration and Signaling Thresholds" section

Required Tasks for Accounting Statistics (Configured in This Order)


Step 1 Configure the gateway to support the collection of accounting statistics. See the "Enabling the Collection of VoIP AAA Accounting Statistics on the Gateway" section.

Step 2 Configure accounting on the gateway. Refer to the gw-accounting aaa command configuration in the Cisco IOS Voice Configuration Library, Release 12.3.

Step 3 Specify that the accounting update is new information. Refer to the aaa accounting update new-info command configuration in the Cisco IOS Security Configuration Guide, Release 12.3, and the Cisco IOS Security Command Reference, Release 12.3 T.

Step 4 Define the AAA RADIUS server group. Refer to the aaa group server radius command configuration in the Cisco IOS Security Configuration Guide, Release 12.3, and the Cisco IOS Security Command Reference, Release 12.3 T.

Step 5 Define a designated broadcast accounting server group (accounting acknowledge broadcast command). See the "Configuring a Designated Server Group for a Broadcast Method List" section.

Step 6 Define the RADIUS server host, port, key, and vendor specific attributes (VSAs). Refer to the Cisco IOS Security Configuration Guide, Release 12.3 and the Cisco IOS Security Command Reference, Release 12.3 T.


Optional Tasks for Both Signaling and Accounting Statistics (Configured in Any Order)

Configure the FTP server or syslog server download. See the "Configuring the Gateway to Archive Statistics to an FTP Server" section and the "Configuring the Gateway to Archive Statistics to a Syslog Server" section.


Note Before configuring the gateway to archive statistics to an FTP server, you must first configure the FTP server to support the archiving process. See the "Configuring the FTP Server to Enable Archiving of Statistics from the Gateway" section.


Configuring the Duration and Time Periods of Call Statistics on the Gateway

Before you configure the gateway to collect call signaling statistics, VoIP AAA accounting statistics, or Cisco VoIP internal error codes (IECs), you must first configure the duration and time periods for when the call statistics are collected. There are three methods for collecting call statistics: periodic, since the last reset, and for specific times.


Note These interval methods are mutually exclusive, meaning that the gateway can be configured for only one collection interval at a time. The collection interval configured applies to all call statistics collected. For example, if you configure the collection interval for a periodic interval, and you configure the gateway to collect both signaling and VoIP AAA accounting statistics, then both types of statistics will be collected on the periodic basis.


To configure the duration and time period of when call statistics will be collected on the gateway, see one of the following sections:

Configuring the Gateway to Collect Call Statistics on a Periodic Basis

Configuring the Gateway to Collect Call Statistics Since the Last Reset

Configuring the Gateway to Collect Call Statistics for a Specific Time Interval

Configuring the Gateway to Collect Call Statistics on a Periodic Basis

This task configures the gateway to collect call statistics on a periodic basis.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics time-range periodic interval start hh:mm {days-of-week {Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | daily | weekdays | weekend}} [end hh:mm {days-of-week {Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday}}]

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics time-range periodic interval 
start hh:mm {days-of-week {Monday | Tuesday | 
Wednesday | Thursday | Friday | Saturday | 
Sunday | daily | weekdays | weekend}} [end 
hh:mm {days-of-week {Monday | Tuesday | 
Wednesday | Thursday | Friday | Saturday | 
Sunday}}]
Example:
Router(config)# voice statistics time-range 
periodic 60minutes start 12:00 days-of-week 
Monday end 12:00 days-of-week Friday

Configures the gateway to collect call statistics on a periodic basis.

Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Configuring the Gateway to Collect Call Statistics Since the Last Reset

This task configures the gateway to collect call statistics since the last time the clear voice statistics command was entered, or since the last time the gateway was rebooted.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics time-range since-reset

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics time-range since-reset
Example:
Router(config)# voice statistics time-range 
since-reset

Configures the gateway to collect call statistics since the last reset or since the last time the gateway was rebooted.

Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Configuring the Gateway to Collect Call Statistics for a Specific Time Interval

This task configures the gateway to collect call statistics for a specific time interval.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics time-range specific start hh:mm day month year end hh:mm day month year

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics time-range specific start 
hh:mm day month year end hh:mm day month year
Example:
Router(config)# voice statistics time-range 
specific start 10:00 1 January 2004 end 12:00 
2 January 2004

Configures the gateway to collect call statistics for a specific configured time period.

Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Configuring the Gateway to Collect Signaling Statistics

This section describes how to configure the gateway to collect signaling statistics. This section documents the following tasks:

Enabling the Gateway to Collect Signaling Statistics

Configuring the Minimum Call Duration and Signaling Thresholds

Disabling the Collection of Signaling Statistics

Displaying the Signaling Statistics for Each Aggregation Level

Clearing Signaling Statistics

Enabling the Gateway to Collect Signaling Statistics

This task describes to how to enable the gateway to collect signaling statistics.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics type csr signaling

4. voice statistics max-storage-duration {day value | hour value | minute value}

5. voice statistics display-format separator {space | tab | new-line | char char}

6. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics type csr signaling

Example:

Router(config)# voice statistics type csr 
signaling

Enables the collection of signaling statistics.


Note To enable the collection of both signaling and VoIP AAA accounting statistics on the gateway, enter the command without the signaling keyword as follows: voice statistics type csr.


Step 4 

voice statistics max-storage-duration {day value | hour value | minute value}

Example:

Router(config)# voice statistics max-storage-duration minute 60

(Optional) Configures the maximum storage time in system memory of the gateway. The keywords and argument are as follows:

day—Number of days. The value argument has a valid range from 0 to 365.

hour—Number of hours. The value argument has a valid range from 0 to 720.

minute—Number of minutes. The value argument has a valid range from 0 to 1440.


Note This command also applies to the collection of VoIP internal error codes (IECs).


Step 5 

voice statistics display-format separator {space | tab | new-line | char char}

Example:

Router(config)# voice statistics display-format separator new-line

(Optional) Specifies the way that displayed information is separated. The default is a comma (,).

Step 6 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Configuring the Minimum Call Duration and Signaling Thresholds

The signaling parameters include minimum call duration, as well as thresholds for lost packet information, packet latency information, and packet jitter information. These parameters have default values so no configuration is required. However, you can customize any or all of these parameters as needed for your network configuration.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics field-params mcd value

4. voice statistics field-params lost-packet value

5. voice statistics field-params packet-latency value

6. voice statistics field-params packet-jitter value

7. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics field-params mcd value

Example:

Router(config)# voice statistics field-params mcd 10

Configures the minimum call duration (MCD) for collecting voice call statistics in milliseconds. Valid values are from 0 to 30 milliseconds. The default is 2 milliseconds. This value applies to both IP and PSTN statistics.

Step 4 

voice statistics field-params lost-packet value

Example:

Router(config)# voice statistics field-params lost-packet 5000

Configures the lost voice packet threshold for collecting voice call statistics in milliseconds. Valid values are from 0 to 65535 milliseconds. The default is 1000 milliseconds. This value applies to IP statistics only.

Step 5 

voice statistics field-params packet-latency value

Example:

Router(config)# voice statistics field-params packet-latency 200

Configures the voice packet-latency threshold parameter for voice call statistics in milliseconds. Valid values are from 0 to 500 milliseconds. The default is 250 milliseconds. This value applies to IP statistics only.

Step 6 

voice statistics field-params packet-jitter value

Example:
Router(config)# voice statistics field-params 
packet-jitter 500

Configures the voice packet-jitter threshold parameter for voice call statistics in milliseconds. Valid values are from 0 to 1000 milliseconds. The default is 250 milliseconds. This value applies to IP statistics only.

Step 7 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Disabling the Collection of Signaling Statistics

This task disables the collection of signaling statistics.

SUMMARY STEPS

1. enable

2. configure terminal

3. no voice statistics type csr signaling

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

no voice statistics type csr signaling

Example:

Router(config)# no voice statistics type csr 
signaling

Disables the collection of signaling statistics.


Note If the gateway is configured to collect both signaling and VoIP AAA accounting statistics, the accounting statistics will continue to be collected after the signaling statistics collection is disabled.


Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Displaying the Signaling Statistics for Each Aggregation Level

Signaling statistics can be collected and displayed for all aggregation levels. To display signaling statistics for the different aggregation levels, see the following sections:

Displaying Signaling Statistics for All Aggregation Levels

Displaying Gateway-Level Signaling Statistics

Displaying VoIP-Level Signaling Statistics

Displaying PSTN-Level Signaling Statistics

Displaying Trunk-Group Level Signaling Statistics

Displaying Voice-Port Level Signaling Statistics

All commands in this section are entered in privileged EXEC mode. The statistics displayed are based on the time range configured using the voice statistics time-range command. For example, if you set the time range to specify that the gateway collects statistics only since the last reset, then these displays show only the statistics since the gateway was last reset or rebooted.

With these commands, you can specify that the display shows either verbose or concise information. The verbose display shows all fields contained in the call statistics records, while the concise display shows only output that contains total calls, answered calls, and answered call duration. The verbose display mode is enabled by default.

In addition, you can specify that the gateway push the statistics display from the console to an FTP or syslog server. To configure the gateway to support pushing statistics to an FTP or syslog server, see the "Managing the Collection of Voice Statistics" section.

Displaying Signaling Statistics for All Aggregation Levels

This task displays signaling statistics for all aggregation levels.

SUMMARY STEPS

1. enable

2. show voice statistics interval-tag

3. show voice statistics csr interval tag-number aggregation all [mode {concise | verbose}] [push {all | ftp | syslog}]

4. show voice statistics csr since-reset aggregation-level all [mode {concise | verbose}] [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics interval-tag
Example:
Router# show voice statistics interval-tag

Displays the configured interval numbers. This command is necessary to obtain the tag number required in the next step.

Step 3 

show voice statistics csr interval tag-number 
aggregation all [mode {concise | verbose}] 
[push {all | ftp | syslog}] 
Example:
Router# show voice statistics csr interval 102 
aggregation all

Displays signaling statistics for all aggregation levels for a given interval.


Note This command is valid only if the voice statistics time-range command is configured to support either periodic statistics collection or statistics collection for a specific time period.


Step 4 

show voice statistics csr since-reset 
aggregation-level all [mode {concise | 
verbose}] [push {all | ftp | syslog}]
Example:
Router# show voice statistics csr since-reset 
aggregation-level all

Displays signaling statistics for all aggregation levels since the last reset or reboot of the gateway.


Note This command is valid only if the voice statistics time-range command is configured to the since-reset value.



Displaying Gateway-Level Signaling Statistics

This task displays gateway-level signaling statistics.

SUMMARY STEPS

1. enable

2. show voice statistics interval-tag

3. show voice statistics csr interval tag-number aggregation gateway [mode {concise | verbose}] [push {all | ftp | syslog}]

4. show voice statistics csr since-reset aggregation-level gateway [mode {concise | verbose}] [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics interval-tag
Example:
Router# show voice statistics interval-tag

Displays the configured interval numbers. This command is necessary to obtain the tag number required in the next step.

Step 3 

show voice statistics csr interval tag-number 
aggregation gateway [mode {concise | verbose}] 
[push {all | ftp | syslog}]
Example:
Router# show voice statistics csr interval 102 
aggregation gateway

Displays the gateway-wide level statistics for a given interval.


Note This command is valid only if the voice statistics time-range command is configured to support either periodic statistics collection or statistics collection for a specific time period.


Step 4 

show voice statistics csr since-reset 
aggregation-level gateway [mode {concise | 
verbose}] [push {all | ftp | syslog}]
Example:
Router# show voice statistics csr since-reset 
aggregation-level gateway

Displays the gateway-wide level statistics since the last reset or reboot of the gateway.


Note This command is valid only if the voice statistics time-range command is configured to the since-reset value.



Displaying VoIP-Level Signaling Statistics

This task displays VoIP-level signaling statistics.

SUMMARY STEPS

1. enable

2. show voice statistics interval-tag

3. show voice statistics csr interval tag-number aggregation ip [mode {concise | verbose}] [push {all | ftp | syslog}]

4. show voice statistics csr since-reset aggregation-level ip [mode {concise | verbose}] [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics interval-tag
Example:
Router# show voice statistics interval-tag

Displays the configured interval numbers. This command is necessary to obtain the tag number required in the next step.

Step 3 

show voice statistics csr interval tag-number 
aggregation ip [mode {concise | verbose}] [push 
{all | ftp | syslog}]
Example:
Router# show voice statistics csr interval 102 
aggregation ip

Displays the VoIP interface-level statistics for a given interval.


Note This command is valid only if the voice statistics time-range command is configured to support either periodic statistics collection or statistics collection for a specific time period.


Step 4 

show voice statistics csr since-reset 
aggregation-level ip [mode {concise | verbose}] 
[push {all | ftp | syslog}]
Example:
Router# show voice statistics csr since-reset 
aggregation-level ip

Displays the VoIP-level statistics since the last reset or reboot of the gateway.


Note This command is valid only if the voice statistics time-range command is configured to the since-reset value.



Displaying PSTN-Level Signaling Statistics

This task displays PSTN-level signaling statistics.

SUMMARY STEPS

1. enable

2. show voice statistics interval-tag

3. show voice statistics csr interval tag-number aggregation pstn [mode {concise | verbose}] [push {all | ftp | syslog}]

4. show voice statistics csr since-reset aggregation-level pstn [mode {concise | verbose}] [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics interval-tag
Example:
Router# show voice statistics interval-tag

Displays the configured interval numbers.

This command is necessary to obtain the tag number required in the next step.

Step 3 

show voice statistics csr interval tag-number 
aggregation pstn [mode {concise | verbose}] 
[push {all | ftp | syslog}]
Example:
Router# show voice statistics csr interval 102 
aggregation pstn

Displays the telephone interface level statistics for a given interval.


Note This command is valid only if the voice statistics time-range command is configured to support either periodic statistics collection or statistics collection for a specific time period.


Step 4 

show voice statistics csr since-reset 
aggregation-level all pstn [mode {concise | 
verbose}] [push {all | ftp | syslog}]
Example:
Router# show voice statistics csr since-reset 
aggregation-level pstn

Displays the PSTN-level statistics since the last reset or reboot of the gateway.


Note This command is valid only if the voice statistics time-range command is configured to the since-reset value.



Displaying Trunk-Group Level Signaling Statistics

This task displays trunk-group level signaling statistics.

SUMMARY STEPS

1. enable

2. show voice statistics interval-tag

3. show voice statistics csr interval tag-number aggregation trunk-group {all | trunk-group-label} [mode {concise | verbose}] [push {all | ftp | syslog}]

4. show voice statistics csr since-reset aggregation-level trunk-group {all | trunk-group-label} [mode {concise | verbose}] [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics interval-tag
Example:
Router# show voice statistics interval-tag

Displays the configured interval numbers. This command is necessary to obtain the tag number required in the next step.

Step 3 

show voice statistics csr interval tag-number 
aggregation trunk-group {all | 
trunk-group-label} [mode {concise | verbose}] 
[push {all | ftp | syslog}]
Example:
Router# show voice statistics csr interval 102 
aggregation trunk-group 20

Displays the trunk-group level statistics for a given interval. Display statistics can be specified for a single trunk group or for all trunk groups.


Note This command is valid only if the voice statistics time-range command is configured to support either periodic statistics collection or statistics collection for a specific time period.


Step 4 

show voice statistics csr since-reset 
aggregation-level trunk-group {all | 
trunk-group-label} [mode {concise | verbose}] 
[push {all | ftp | syslog}]
Example:
Router# show voice statistics csr since-reset 
aggregation-level trunk-group all

Displays the trunk-group level statistics since the last reset or reboot of the gateway. You can display statistics for a specific trunk group or for all trunk groups.


Note This command is valid only if the voice statistics time-range command is configured to the since-reset value.



Displaying Voice-Port Level Signaling Statistics

This task displays voice-port level signaling statistics.

SUMMARY STEPS

1. enable

2. show voice statistics interval-tag

3. show voice statistics csr interval tag-number aggregation voice-port {voice-port-label | all} [mode {concise | verbose}] [push {all | ftp | syslog}]

4. show voice statistics csr since-reset aggregation-level voice-port {all | voice-port-label} [mode {concise | verbose}] [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics interval-tag
Example:
Router# show voice statistics interval-tag

Displays the configured interval numbers. This command is necessary to obtain the tag number required in the next step.

Step 3 

show voice statistics csr interval tag-number 
aggregation voice-port {voice-port-label | all} 
[mode {concise | verbose}] [push {all | ftp | 
syslog}]
Example:
Router# show voice statistics csr interval 102 
aggregation voice-port all

Displays voice-port level statistics for a given interval. You can display statistics for a specific voice port or for all voice ports.


Note This command is valid only if the voice statistics time-range command is configured to support either periodic statistics collection or statistics collection for a specific time period.


Step 4 

show voice statistics csr since-reset 
aggregation-level voice-port {all | 
voice-port-label} [mode {concise | verbose}] 
[push {all | ftp | syslog}
Example:
Router# show voice statistics csr since-reset 
aggregation-level voice-port all

Displays the voice-port level statistics since the last reset or reboot of the gateway. You can display statistics for a specific voice port or for all voice ports.


Note This command is valid only if the voice statistics time-range command is configured to the since-reset value.



Clearing Signaling Statistics

This task clears signaling statistics from the gateway.

SUMMARY STEPS

1. enable

2. clear voice statistics csr signaling

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

clear voice statistics csr signaling
Example:

Router# clear voice statistics csr signaling

Clears all signaling statistics.


Configuring the Gateway to Collect VoIP AAA Accounting Statistics

Using this feature, statistics can be collected to tally accounting records on billing servers (RADIUS) and on voice gateways based on call legs (both inbound and outbound). The statistics collected track whether calls were successfully accounted for based on the acknowledgement messages from designated billing or accounting servers.

This section shows you how to configure the collection of accounting statistics on the gateway. This section documents the following tasks:

Enabling the Collection of VoIP AAA Accounting Statistics on the Gateway

Configuring a Designated Server Group for a Broadcast Method List

Disabling the Collection of VoIP AAA Accounting Statistics

Displaying the VoIP AAA Accounting Statistics

Clearing the VoIP AAA Accounting Statistics

Prerequisites

The definition of the AAA method list for accounting, the server groups, and the RADIUS servers should be configured. For more information, refer to the Configuring AAA for Cisco Voice Gateways document in the Cisco IOS Voice Configuration Library.

Restrictions

You can define "pass" criteria for calls on the basis of method lists but not on the basis of server groups. For broadcast method lists, if the gateway attempts to access multiple server groups simultaneously, additional configuration is needed. See the "Configuring a Designated Server Group for a Broadcast Method List" section.

Enabling the Collection of VoIP AAA Accounting Statistics on the Gateway

This task enables the collection of accounting statistics on the gateway.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics type csr accounting

4. voice statistics accounting method method-list-name pass {start-interim-stop | start-stop | stop-only}

5. voice statistics max-storage-duration {day value | hour value | minute value}

6. voice statistics display-format separator {space | tab | new-line | char char}

7. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics type csr accounting

Example:

Router(config)# voice statistics type csr 
accounting

Enables the collection of VoIP AAA accounting statistics.


Note To enable the collection of both accounting and signaling statistics on the gateway, enter the command without the accounting keyword, as follows: voice statistics type csr.


Step 4 

voice statistics accounting method method-list-name pass {start-interim-stop | start-stop | stop-only}

Example:

Router(config)# voice statistics accounting method h323 pass stop-only

Configures the method-list pass criteria.


Note The method-list-name argument is the same as that configured using the method command in gateway-accounting AAA configuration mode. You can have multiple method lists configured on a gateway at one time.


Step 5 

voice statistics max-storage-duration {day value | hour value | minute value}

Example:

Router(config)# voice statistics max-storage-duration minute 60

(Optional) Configures the maximum storage time in system memory of the gateway. The keywords and argument are as follows:

day—Number of days. The value argument has a valid range from 0 to 365.

hour—Number of hours. The value argument has a valid range from 0 to 720.

minute—Number of minutes. The value argument has a valid range from 0 to 1440.


Note This command also applies to the collection of VoIP internal error codes (IECs).


Step 6 

voice statistics display-format separator {space | tab | new-line | char char}

Example:

Router(config)# voice statistics display-format separator new-line

(Optional) Specifies the way in which displayed information is separated. The default is a comma (,).

Step 7 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Configuring a Designated Server Group for a Broadcast Method List

This task is required if accounting CSRs need to be collected for a gateway that is configured for a broadcast method list. See the "Configuring the Gateway to Collect VoIP AAA Accounting Statistics" section. It is possible to set all the server groups in a method list for monitoring acknowledgements.

Prerequisites

The collection of accounting statistics should be enabled on the gateway. The pass criteria for the method list must already be defined.

SUMMARY STEPS

1. enable

2. configure terminal

3. aaa group server radius name

4. accounting acknowledge broadcast

5. end

6. show voice statistics | begin aaa group server

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

aaa group server radius name

Example:

Router(config)# aaa group server radius billing-grp

Groups different RADIUS server hosts into distinct lists and distinct methods and enters server group RADIUS configuration mode.

Step 4 

accounting acknowledge broadcast

Example:

Router(config-sg-radius)# accounting acknowledge broadcast

Enables the accounting broadcast functionality for the server groups configured in Step 3.

Step 5 

end

Example:

Router(config-sg-radius)# end

Ends the current configuration session and returns to privileged EXEC mode.

Step 6 

show voice statistics | begin aaa group server

Example:

Router# show voice statistics | begin aaa group server

Displays the AAA group server and its configuration.


Troubleshooting Tips

Acknowledgements of only designated server groups are considered when deciding whether the accounting for a given call leg is successful. If more than one server group is configured as designated, the gateway considers the response from all server groups in deciding whether the call leg accounting is successful.

Disabling the Collection of VoIP AAA Accounting Statistics

This task disables the collection of VoIP AAA accounting statistics.

SUMMARY STEPS

1. enable

2. configure terminal

3. no voice statistics type csr accounting

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

no voice statistics type csr accounting

Example:

Router(config)# no voice statistics type csr 
accounting

Disables the collection of accounting statistics.


Note If the gateway is configured to collect both VoIP AAA accounting statistics and signaling statistics, the signaling statistics will continue to be collected after the accounting statistics collection is disabled.


Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Displaying the VoIP AAA Accounting Statistics

After the gateway has been configured to collect VoIP AAA accounting statistics, you can display all accounting statistics or accounting statistics for a specific method list.

All commands in this section are entered in privileged EXEC mode. The statistics displayed are based on the time range configured using the voice statistics time-range command. For example, if you set the time range to specify that the gateway to collect statistics only since the last reset, then these displays will show only the statistics since the gateway was last reset or rebooted.

With these commands, you can specify that the gateway push the statistics display from the console to an FTP or syslog server. To configure the gateway to support pushing statistics to an FTP or syslog server, see the "Managing the Collection of Voice Statistics" section.

SUMMARY STEPS

1. enable

2. show voice accounting method [method-list-name]

3. show voice statistics csr interval tag-number accounting {all | method-list method-list-name} [push {all | ftp | syslog}]

4. show voice statistics csr since-reset accounting {all | method-list method-list-name} [push {all | ftp | syslog}]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice accounting method {method-list-name}
Example:
Router# show voice accounting method mll

Displays connectivity status information for accounting method lists.

Step 3 

show voice statistics csr interval tag-number 
accounting {all | method-list method-list-name} 
[push {all | ftp | syslog}]
Example:
Router# show voice statistics csr interval 10 
accounting all

Displays the VoIP AAA accounting statistics for the specified interval. You can display all accounting statistics or accounting statistics for a specific method list.

Step 4 

show voice statistics csr since-reset 
accounting {all | method-list method-list-name} 
[push {all | ftp | syslog}]
Example:

Router# show voice statistics csr since-reset accounting method-list h323

Displays all VoIP AAA accounting statistics since the last reset or reboot of the gateway. You can display all accounting statistics or accounting statistics for a specific method list.

Step 5 s

show voice accounting response pending
Example:
Router# show voice accounting response pending

Displays information regarding pending VoIP AAA accounting responses.


Clearing the VoIP AAA Accounting Statistics

This task describes how to clear the VoIP AAA accounting statistics.

SUMMARY STEPS

1. enable

2. clear voice statistics csr accounting

3. clear voice accounting method method-list-name

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

clear voice statistics csr accounting
Example:

Router# clear voice statistics csr accounting

Clears all accounting statistics.

Step 3 

clear voice accounting method method-list-name

Example:

Router# clear voice accounting method h323

Clears accounting statistics for a specific accounting method.


Troubleshooting Tips for VoIP AAA Accounting Statistics

If any of the following messages is displayed, proceed with the solution shown.

Message: "Either specific or periodic time-range has existed."

Solution: Delete any previously configured specific or periodic time range.

Message: "Ending time must be greater than starting time."

Solution: Make sure that the configured end time is later than the start time for the time range configured.

Message: "Starting time must be future time."

Solution: Make sure that the configured start time is in the future.

If accounting statistics are not being collected properly, the best place to start troubleshooting is by verifying your configurations as follows:

Router# show running-config | include voice statistics

voice statistics type csr
voice statistics accounting method h323 pass stop-only 
! Specifies the pass criteria.
voice statistics time-range since-reset

Router# show running-config | include aaa

aaa new-model
aaa accounting connection h323 start-stop group radius 
! Specifies the method list.
aaa session-id common
gw-accounting aaa 
! Enables accounting on the gateway.
radius-server host 1.6.10.203 auth-port 1645 acct-port 1646 
! Specifies RADIUS server IP address.

If your configurations are correct, turn on debugging with the following debug commands and check the output. You must turn on all three commands:

debug isdn q931

debug radius accounting

debug voip-aaa

As long as accounting and signaling statistics are being collected, the output from these three debug commands will display on the console.

The following sample output shows that the accounting statistics are not being properly collected by the RADIUS server:

*Nov 22 14:54:49.350: ISDN Se6/0:15 Q931: RX <- SETUP pd = 8  callref = 0x125E 
        Bearer Capability i = 0x8090A3 
                Standard = CCITT 
                Transfer Capability = Speech  
                Transfer Mode = Circuit 
                Transfer Rate = 64 kbit/s 
        Channel ID i = 0xA98381 
                Exclusive, Channel 1 
        Called Party Number i = 0x80, '11' 
                Plan:Unknown, Type:Unknown
!
Router#55:02.366: RADIUS: acct-delay-time for 4067CADC (at 4067CDF6) now 10
*Nov 22 14:55:04.366: RADIUS: Retransmit to (10.6.10.203:1645,1646) for id 21669/117
*Nov 22 14:55:04.366: RADIUS(0000053B): Retransmit id 21669/117
*Nov 22 14:55:04.366: RADIUS: acct-delay-time for 40278B3C (at 40278D04) now 15
*Nov 22 14:55:07.366: RADIUS: Retransmit to (10.6.10.203:1645,1646) for id 21669/118
*Nov 22 14:55:07.366: RADIUS(0000053B): Retransmit id 21669/118
*Nov 22 14:55:07.366: RADIUS: acct-delay-time for 4067CADC (at 4067CDF6) now 15
*Nov 22 14:55:09.366: RADIUS: Tried all servers.
*Nov 22 14:55:09.366: RADIUS: No valid server found. Trying any viable server.

The line above indicates that the RADIUS server is unreachable.

*Nov 22 14:55:09.366: RADIUS: Tried all servers.
*Nov 22 14:55:09.366: RADIUS: No response from (10.6.10.203:1645,1646) for id 21669/119
*Nov 22 14:55:09.366: RADIUS/DECODE: parse response no app start; FAIL
*Nov 22 14:55:09.366: RADIUS/DECODE: parse response; FAIL
*Nov 22 14:55:12.366: RADIUS: Tried all servers.
*Nov 22 14:55:12.366: RADIUS: No valid server found. Trying any viable server.

The line above indicates that the RADIUS server is not found.

*Nov 22 14:55:12.366: RADIUS: Tried all servers.
*Nov 22 14:55:12.366: RADIUS: No response from (10.6.10.203:1645,1646) for id 21669/120
*Nov 22 14:55:12.366: RADIUS/DECODE: parse response no app start; FAIL
*Nov 22 14:55:12.366: RADIUS/DECODE: parse response; FAIL
*Nov 22 14:55:12.366: voip_process_acct_reply(1339):
*Nov 22 14:55:12.366: voip_process_acct_reply(1339): event_message->type=0x210, 
                      msg_t=2, rsp=2
*Nov 22 14:55:12.366: voip_process_acct_reply: acct notification call back for 
                      method=h323
*Nov 22 14:55:12.366: acct_notif_cleanup:
*Nov 22 14:55:12.366: acct_ntf_deregistration:
*Nov 22 14:55:12.366: acct_ntf_deregistration: deregister with AAA EM, rsp_t=0x4, 
                      ev_t=0x210
*Nov 22 14:55:12.366: acct_notif_cleanup: unlock adb
*Nov 22 14:55:12.366: voip_aaa_unlock_adb: uid(1339) count=0
*Nov 22 14:55:12.366: voip_aaa_cleanup_adb: dealloc uid (1339)
*Nov 22 14:55:12.366: voip_aaa_acct_get_dynamic_attrs: No cdb found from cdb tree 

The following sample output shows that the RADIUS server was authenticated:

*Nov 22 14:56:46.006: ISDN Se6/0:15 Q931: RX <- SETUP pd = 8  callref = 0x125F 
        Bearer Capability i = 0x8090A3 
                Standard = CCITT 
                Transfer Capability = Speech  
                Transfer Mode = Circuit 
                Transfer Rate = 64 kbit/s 
        Channel ID i = 0xA98381 
                Exclusive, Channel 1 
        Called Party Number i = 0x80, '11' 
                Plan:Unknown, Type:Unknown
*Nov 22 14:56:46.010: voip_start_ccapi_accounting(784): 
*Nov 22 14:56:46.010: voip_start_accounting_internal: 
*Nov 22 14:56:46.010: voip_start_accounting_internal(784): peer_tag=100
*Nov 22 14:56:46.010: get_acct_params: suppressed=0
*Nov 22 14:56:46.010: get_acct_params(784): Use method "h323" set by global config.
*Nov 22 14:56:46.014:     method:        
*Nov 22 14:56:46.014:     cdrtag:        
*Nov 22 14:56:46.014: voip_start_accounting_internal: Getting new uid
*Nov 22 14:56:46.014: voip_alloc_aaa_uid
*Nov 22 14:56:46.014: voip_aaa_acct_get_retrieved_attrs
*Nov 22 14:56:46.014: voip_aaa_acct_get_nas_port_details:
*Nov 22 14:56:46.014: get_nas_port: avail=1 type=4 nas-port=ISDN 6/0:D:1
*Nov 22 14:56:46.014: voip_aaa_lock_adb: uid(1341) count=1
*Nov 22 14:56:46.014: voip_start_accounting_internal: UID=1341
*Nov 22 14:56:46.014: voip_start_accounting_internal: Telephony Leg
*Nov 22 14:56:46.014: voip_start_accounting_internal(784):
*Nov 22 14:56:46.014:       calling num     :  
*Nov 22 14:56:46.014:       called num      : 11 
*Nov 22 14:56:46.014:       account num     :  
*Nov 22 14:56:46.014:       setup time      : *14:56:46.014 PST Fri
*Nov 22 14:56:46.014:       gateway id      : Router.cisco2.com 
*Nov 22 14:56:46.014:       connection id   : 82831163 FDA411D6 8660B639 91DC0E5F 
*Nov 22 14:56:46.014:       call origin     : answer 
*Nov 22 14:56:46.014:       call type       : Telephony 
*Nov 22 14:56:46.014:       incoming conn id: 82831163 FDA411D6 8660B639 91DC0E5F 

*Nov 22 14:56:46.018: RADIUS(0000053D): sending
*Nov 22 14:56:46.018: RADIUS(0000053D): Send Accounting-Request to 10.6.10.203:1646 id 
                      121, len 462
*Nov 22 14:56:46.018: RADIUS:  authenticator C7 53 14 06 45 F2 49 DF - 53 D8 90 B3 1C 
                      D1 74 03
*Nov 22 14:56:46.018: RADIUS:  Acct-Session-Id     [44]  10  "0000084C"
*Nov 22 14:56:46.018: RADIUS:  Vendor, Cisco       [26]  57
*Nov 22 14:56:46.018: RADIUS:   h323-setup-time    [25]  51 
                      "h323-setup-time=*14:56:46.014 PST
*Nov 22 14:56:46.018: RADIUS:  Vendor, Cisco       [26]  36  
*Nov 22 14:56:46.018: RADIUS:   h323-gw-id         [33]  30  
                      "h323-gw-id=Router.cisco2.com"
*Nov 22 14:56:46.018: RADIUS:  Vendor, Cisco       [26]  56  
*Nov 22 14:56:46.018: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=82831163 
                      FDA411D6 8660B639 91DC0E5F"
*Nov 22 14:56:46.018: RADIUS:  Vendor, Cisco       [26]  31
*Nov 22 14:56:46.018: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
*Nov 22 14:56:46.018: RADIUS:  Vendor, Cisco       [26]  32  
*Nov 22 14:56:46.018: RADIUS:   h323-call-type     [27]  26  
                      "h323-call-type=Telephony"
Accounting-response, len 20
!

Router received response from RADIUS server.

!
**Nov 22 14:56:49.022: RADIUS:  authenticated 08 C6 FC 0F 31 1D FA EA - 68 A7 5D 48 6F 
                      47 96 FA
*Nov 22 14:56:49.022: voip_process_acct_reply(1341):
*Nov 22 14:56:49.022: voip_process_acct_reply(1341): event_message->type=0x210, 
                      msg_t=2, rsp=1
*Nov 22 14:56:49.022: voip_process_acct_reply: acct notification call back for 
                      method=h323
*Nov 22 14:56:49.022: acct_notif_cleanup:
*Nov 22 14:56:49.022: acct_ntf_deregistration:
*Nov 22 14:56:49.022: acct_ntf_deregistration: deregister with AAA EM, rsp_t=0x4, 
                      ev_t=0x210
*Nov 22 14:56:49.022: acct_notif_cleanup: unlock adb
*Nov 22 14:56:49.022: voip_aaa_unlock_adb: uid(1341) count=0
*Nov 22 14:56:49.022: voip_aaa_cleanup_adb: dealloc uid (1341)
*Nov 22 14:56:49.022: voip_aaa_acct_get_dynamic_attrs: No cdb found from cdb tree 

Managing the Collection of Voice Statistics

This section describes how to manage the collection of voice statistics on the gateway and documents the following tasks:

Configuring the FTP Server to Enable Archiving of Statistics from the Gateway

Configuring the Gateway to Archive Statistics to an FTP Server

Configuring the Gateway to Archive Statistics to a Syslog Server

Displaying Memory Usage

Displaying All Statistics and Pushing Them to an FTP or Syslog Server

Clearing the Collected Call Statistics

Monitoring the Statistical Reporting

Configuring the FTP Server to Enable Archiving of Statistics from the Gateway

This task shows how to configure the FTP server to accept archived statistics from a Cisco IOS gateway.

Prerequisites

FTP Server

An FTP server must be configured before you can archive the collected statistics.

FTP Service Port

Normally, the FTP port is a well-known number, such as 21. However, another port number (not well-known) can receive data for specific purposes (for example, security), as long as the FTP client on voice gateways is configured to use the same port number.

User Account and File Directory

In order for the FTP client on the voice gateway to write files on the FTP server, FTP user accounts must be available (or well-known) to the FTP client. The FTP user accounts can be normal UNIX user accounts.

The FTP file upload directory in the FTP servers can also be specified for directory management purposes. System administrators can also restrict the privilege level of the user accounts in the upload directory for security and directory management purposes.


Note For this task, the external devices are assumed to be UNIX-like platforms (for example, Linux).



Step 1 Install the software.

Ensure that both the anonftp package and the wu-ftpd package are installed on the system. The versions installed should, at a minimum, match those below:

anonftp-3.0-9
wu-ftpd-2.6.1-6

Check to see whether the installation can be done with the following command:

rpm -qa | egrep '(wu-ftpd|anonftp)'

Step 2 Configure the IP aliasing for virtual domains.

Configure the IP aliases for the virtual domains so that there is an IP address routed through one of the available network interfaces.

The programs "netcfg" or "linuxconf" can also be used to set up the IP aliases (replacing 10.10.10.10 with your actual IP address for the FTP site).

If the IP address is to resolve to a domain name, you must set up a DNS server.

Step 3 Configure xinetd.conf.

Configure the /etc/xinetd.d/wu-ftpd file to handle FTP access, for example:

[root@wyvern xinetd.d]# cat wu-ftpd 

# default: on 

# description: The wu-ftpd FTP server knows the FTP # connections. It uses \ 
normal,unencrypted # usernames and passwords for authentication.

service ftp 
{
        disable                 = no
        socket_type             = stream
        wait                    = no
        user                    = root
        server                  = /usr/sbin/in.ftpd
        server_args             = -l -a
        log_on_success          += DURATION USERID
        log_on_failure          += USERID
        nice                    = 10
}

Note It is very important that the "-1 -a" is specified in server_args and that the disable line is set to "no." This tells inetd.conf to reference the commands in the /etc/ftpaccess file.

Step 4 Edit /etc/ftpaccess.

Edit the /etc/ftpaccess file. Make the basic changes using Linuxconf as the root. Additional changes must be made in this file manually. The virtual entry in the file should be placed at the bottom of the file and resembles the following:

# Virtual FTP entries for 10.10.10.10
virtual  10.10.10.10   root        /home/domain1
virtual  10.10.10.10   banner      /home/ftp/domain1/banner.msg
virtual  10.10.10.10   logfile     /var/log/virtual/domain1/xferlog

Where /home/domain1 is the root path for the virtual FTP server, /home/ftp/domain1/banner.msg is the path to the banner message to be displayed upon login, and /var/log/virtual/domain1/xferlog is the path to the transfer log.

Step 5 Specify other options.

Specify that all users can have access with the following line:

virtual 10.10.10.10  allow *

If only specific users are to be allowed access, list their usernames, as shown here:

virtual 10.10.10.10 allow user1

If anonymous FTP logins are to be disabled, set the IP address to private as shown here:

virtual 10.10.10.10 private

Step 6 Secure or hide the FTP server.

When FTP users log on to the system, they should be allowed into the directory specified in the root path only. There are several steps as follows:

a. Determine whether or not there is one user or a group of users that will be logging into the virtual FTP site.

b. Specify the home directory in the /etc/passwd file for the user specified in the /etc/ftpaccess/ file, followed by a /./. The entry will look like this:

user1:X:2453:group1::/var/ftp/home/domain1/./:/bin/bash

Include the following line in your FTP access file, if user1 is the only user accessing this virtual FTP site, following the virtual configuration lines:

guestuser user1

When logging into 10.10.10.10, user1 is automatically dropped into /home/domain1 but will see this as the / directory. User1 will not be able to move outside of that directory.

c. Specify a group of users in addition to user1 in /etc/group. You should then add the following line to /etc/ftpaccess following the virtual FTP entry:

guestgroup group1

d. Specify the administrator of the FTP site (user2 in the example and exempt from the group rule) as follows:

guestgroup group1
realuser user2

Step 7 Provide for basic shell access.

Open the /var/ftp (created on the system when the anonftp rpm was installed), and copy /var/ftp/bin, /var/ftp/etc/, and /var/ftp/lib into the root directory of the virtual FTP site (in this case, /var/ftp/home/domain1).

Step 8 Restart services so that the configuration takes effect.

Close the configuration file after making all of the changes, and restart the inet services (where FTP services are specified) by typing the following:

/sbin/service xinetd stop

then:

/sbin/service xinetd start

Configuring the Gateway to Archive Statistics to an FTP Server

This task shows you how to configure the gateway to archive the collected statistics to the specified FTP server and how to configure the maximum allowable file size.


Note This procedure can also be used to archive Cisco VoIP internal error codes (IECs) to an FTP server.


SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics push ftp url ftp-url [max-file-size value]

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics push ftp url ftp-url [max-file-size value]

Example:

Router(config)# voice statistics push ftp url ftp://me:secret@abccompanyhost:23/products max-file-size 3000

Configures the FTP server location where statistics will be archived. The ftp-url argument is expressed in the following form:

ftp://user:password@host:port/path1/path2/

The max-file-size keyword is optional and specifies the maximum FTP file size, in bytes. The value argument has a valid range from 1024 to 4294967295. The default is 400000000 (4 GB).

Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Example

The following sample output is the message that you see on your console when the statistics are being archived to the FTP server:

Writing /ftp_files/vstats.3660-1.2002-04-25T020500Z !
Writing /ftp_files/vstats.3660-1.2002-04-25T020500Z.done ! 
!
01:43:22: %VSTATS-6-VCSR: SEQ=0:
stats_type,version,format,gw_id,start_time,end_time,rec_count
VCSR_SIG,1,asc,3660-1,2002-04-25T02:00:00Z,2002-04-25T02:05:00Z,9
record_type,trunk_group_id,voice_port_id,in_call,in_ans,in_fail,out_call,out_ans,out_fail,
in_szre_d,out_szre_d,in_conn_d,out_conn_d,orig_disconn,in_ans_abnorm,out_ans_abnorm,in_mcd
out_mcd,in_pdd,out_pdd,in_setup_delay,out_setup_delay,lost_pkt,latency,jitter,in_cc_no,
out_cc_no,in_cc_id,in_cc_cntr,out_cc_id,out_cc_cntr
gw,,,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,16,0,16,0
ip,,,0,0,0,0,0,0,0,0,0,0,
01:43:22: %VSTATS-6-VCSR: SEQ=1:
0,0,0,0,0,0,0,0,0,0,0,0,1,1,16,0,16,0
pstn,,,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
vp,,4/0/0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
vp,,4/0/1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
vp,,4/1/0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
vp,,4/1/1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
vp,,2/0:23,0,0,0,0,0,|0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
vp,,2/1:23,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,,,1,1,16,0,16,0
stats_type,version,format,gw_id,start_time,e
01:43:22: %VSTATS-6-VCSR: SEQ=2:
nd_time,rec_count
VCSR_ACC,1,asc,3660-1,2002-04-25T02:00:00Z,2002-04-25T02:05:00Z,2
acct_type,acct_type_name,acct_pass_criteria,pstn_in_pass,pstn_in_fail,pstn_out_pass,
pstn_out_fail,ip_in_pass,ip_in_fail,ip_out_pass,ip_out_fail
ml,h323,1,0,0,0,0,0,0,0,0
ml,h323-1,1,0,0,0,0,0,0,0,0

Configuring the Gateway to Archive Statistics to a Syslog Server

This task shows you how to configure the gateway to archive the call statistics records to a syslog server.


Note This procedure can also be used to archive Cisco VoIP internal error codes (IECs) to a sylog server.


Prerequisites

The external syslog server must be configured to receive voice call statistics from the gateway. For information about enabling a syslog server to receive voice call statistics information from a gateway, refer to Task 2 in Enabling Management Protocols: NTP, SNMP, and Syslog on Cisco.com.

For information about configuring a Solaris syslog server, refer to Task 4 ("Using Syslog, NTP, and Modem Call Records to Isolate and Troubleshoot Faults") in the Basic Dial NMS Implementation Guide on Cisco.com.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice statistics push syslog [max-msg-size value]

4. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

voice statistics push syslog [max-msg-size value]

Example:

Router(config)# voice statistics push syslog

Archives voice statistics to an external syslog server and specifies the maximum syslog message size.

The max-msg-size keyword is optional and specifies the maximum size in bytes of a voice statistics file to be pushed to the syslog server. Valid values are from 1024 to 4294967295. The default value is 4000000000 (4 GB).

Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.


Displaying Memory Usage

This task shows you how to display memory usage either as an absolute value or as a percentage.

SUMMARY STEPS

1. enable

2. show voice statistics memory-usage {all | csr | iec}

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics memory-usage {all | csr | iec}

Example:

Router(config)# show voice statistics memory-usage csr

Displays current memory usage (absolute or percentage).


Displaying All Statistics and Pushing Them to an FTP or Syslog Server

This task shows how to display all statistics and push them to an FTP or syslog server.


Note This procedure can also be used if you are collecting statistics for VoIP internal error codes (IECs).


SUMMARY STEPS

1. enable

2. show voice statistics csr since-reset all [mode {concise | verbose}]

3. show voice statistics csr since-reset all push {all | ftp | syslog}

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics csr since-reset all [mode 
{concise | verbose}]
Example:

Router# show voice statistics csr since-reset all mode concise

Displays all statistics (including both signaling and accounting statistics) since the last reset or reboot of the gateway.

Step 3 

show voice statistics csr since-reset all push 
{all | ftp | syslog}
Example:

Router# show voice statistics csr since-reset all push syslog

Pushes all displayed statistics to either the FTP or syslog server, or to both servers.

The statistics are first displayed on the console before being pushed to the FTP or syslog server.


Clearing the Collected Call Statistics

This task shows you how to clear the collected statistics. The results of the clear voice statistics csr command can be viewed using the show voice statistics command.

Once the clear voice statistics csr command has been issued, all statistics collected using the voice statistics time-range since-reset command are removed and the counters are reset.

Restrictions

Only since-reset counters can be reset. Specific or periodic counts cannot be reset using the clear voice statistics csr command. This command cannot be used in nonprivileged mode.

SUMMARY STEPS

1. enable

2. clear voice statistics csr

3. show voice statistics csr since-reset all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

clear voice statistics csr

Example:

Router# clear voice statistics csr

Clears the collected statistics.

Step 3 

show voice statistics csr since-reset all

Example:

Router# show voice statistics csr since-reset all

Displays the collected statistics since a reset occurred. Enter this command after entering the clear voice statistics csr command to verify that the statistics have been cleared.


Troubleshooting Tips

The gateway does not recognize the clear voice statistics csr command in nonprivileged mode and displays the following message:

Router> clear voice statistics csr
             ^
% Invalid input detected at '^' marker.

If you see this message, enter this command from privileged EXEC mode.

Monitoring the Statistical Reporting

This section contains the following subsections:

Using Debug Commands for Monitoring Gateway Reporting

Using Cause Code Statistics

Displaying Quality of Service Indicators

Using Debug Commands for Monitoring Gateway Reporting

To monitor the statistical reporting and the collection of data by the gateway, you must turn on the following debug commands:

debug radius accounting

debug event-manager

debug voice statistics csr

debug voice statistics accounting

debug voice statistics core

Once the debugging is turned on, you can review the data, evaluate the performance of the network, and identify impaired voice equipment.

The following output examples show a collection of records occurring between intervals and a voice call going through the gateway.

Example of Record Collection Between Intervals

In the following example, the gateway was unable to "push" the data to the FTP server.

vstats_timer_handle_interval_event():Between Intervals!

04:52:37: vstats_acct_interval_end: interval_tag = 4
04:52:37: vstats_acct_interval_end: pushing out, tag=3
04:52:37: vstats_acct_clean_history_stats:
04:52:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted
04:52:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted
04:52:37: vstats_acct_create_empty_stats:
04:52:37: vstats_acct_create_new_rec_list:
04:52:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=2
04:52:37: vstats_acct_create_new_rec:
04:52:37: vstats_acct_add_rec_entry:
04:52:37: vstats_acct_add_stats_entry:
04:52:37: vstat_push_driver_file_open():Cannot open 
ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z. 
errno=65540=Unknown error 65540
vstat_push_drv_activate_ftp_file_tx():open file 
(ftp://sgcp:sgcp@jeremy-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)=(ftp://sgcp:sg
cp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)failed!
vstats_push_api_push_formatted_text():Start CMD error!

Example of a Voice Call Going Through the Gateway

04:55:07: EM: Notify the producer not to produce
04:55:07: RADIUS(00000019): Storing nasport 0 in rad_db
04:55:07: RADIUS(00000019): Config NAS IP: 0.0.0.0
04:55:07: RADIUS(00000019): sending
04:55:07: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.6.10.203
04:55:07: RADIUS(00000019): Send Accounting-Request to 10.6.10.203:1646 id 21645/49,len496
04:55:07: RADIUS:  authenticator C5 B8 AA 2E C3 AF 02 93 - 45 0B AE E5 B6 B2 99 1F
04:55:07: RADIUS:  Acct-Session-Id     [44]  10 "00000020"
04:55:07: RADIUS:  Vendor, Cisco       [26]  57  
04:55:07: RADIUS:   h323-setup-time    [25]  51  "h323-setup-time=*16:22:30.994 UTC
          Thu Feb 13 2003"
04:55:07: RADIUS:  Vendor, Cisco       [26]  27  
04:55:07: RADIUS:   h323-gw-id         [33]  21  "h323-gw-id=5400-GW."
04:55:07: RADIUS:  Vendor, Cisco       [26]  56  
04:55:07: RADIUS:  Conf-Id             [24]  50  "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 
          B935C142"
04:55:07: RADIUS:  Vendor, Cisco       [26]  31  
04:55:07: RADIUS:  h323-call-origin    [26]  25  "h323-call-origin=answer"
04:55:07: RADIUS:  Vendor, Cisco       [26]  32  
04:55:07: RADIUS:   h323-call-type     [27]  26  "h323-call-type=Telephony"
04:55:07: RADIUS:  Vendor, Cisco       [26]  65  
04:55:07: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=2F4ED2E3 3EA611D7 
          800E0002 B935C142"
04:55:07: RADIUS:  Vendor, Cisco       [26]  30  
04:55:07: RADIUS:   Cisco AVpair       [1]   24  "subscriber=RegularLine"
04:55:07: RADIUS:  Vendor, Cisco       [26]  35  
04:55:07: RADIUS:   Cisco AVpair       [1]   29  "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:07: RADIUS:  Vendor, Cisco       [26]  32  
04:55:07: RADIUS:   Cisco AVpair       [1]   26  "calling-party-category=9"
04:55:07: RADIUS:  Vendor, Cisco       [26]  33  
04:55:07: RADIUS:   Cisco AVpair       [1]   27  "transmission-medium-req=0"
04:55:07: RADIUS:  User-Name           [1]   4   "22"
04:55:07: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
04:55:07: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
04:55:07: RADIUS:  Vendor, Cisco       [26]  20  
04:55:07: RADIUS:   cisco-nas-port     [2]   14  "ISDN 6/0:D:1"
04:55:07: RADIUS:  NAS-Port            [5]   6   0                         
04:55:07: RADIUS:  Calling-Station-Id  [31]  4   "22"
04:55:07: RADIUS:  Called-Station-Id   [30]  4   "11"
04:55:07: RADIUS:  Service-Type        [6]   6   Login                     [1]
04:55:07: RADIUS:  NAS-IP-Address      [4]   6   10.6.43.101 
04:55:07: RADIUS:  Acct-Delay-Time     [41]  6   0                         
04:55:07: RADIUS(0000001A): Config NAS IP: 0.0.0.0
04:55:07: RADIUS(0000001A): sending
04:55:07: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.6.10.203
04:55:07: RADIUS(0000001A): Send Accounting-Request to 10.6.10.203:1646 id 21645/50,len427
04:55:07: RADIUS:  authenticator E4 98 06 8C 48 63 4F AA - 56 4F 40 12 33 F0 F5 99
04:55:07: RADIUS:  Acct-Session-Id     [44]  10  "00000021"
04:55:07: RADIUS:  Vendor, Cisco       [26]  57  
04:55:07: RADIUS:   h323-setup-time    [25]  51  "h323-setup-time=*16:22:31.006 UTC 
          Thu Feb 13 2003"
04:55:07: RADIUS:  Vendor, Cisco       [26]  27  
04:55:07: RADIUS:   h323-gw-id         [33]  21  "h323-gw-id=5400-GW."
04:55:07: RADIUS:  Vendor, Cisco       [26]  56  
04:55:07: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 
          B935C142"
04:55:07: RADIUS:  Vendor, Cisco       [26]  34  
04:55:07: RADIUS:   h323-call-origin   [26]  28 "h323-call-origin=originate"
04:55:07: RADIUS:  Vendor, Cisco       [26]  27  
04:55:07: RADIUS:   h323-call-type     [27]  21  "h323-call-type=VoIP"
04:55:07: RADIUS:  Vendor, Cisco       [26]  65  
04:55:07: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=2F4ED2E3 3EA611D7 
          800E0002 B935C142"
04:55:07: RADIUS:  Vendor, Cisco       [26]  30  
04:55:07: RADIUS:   Cisco AVpair       [1]   24  "subscriber=RegularLine"
04:55:07: RADIUS:  Vendor, Cisco       [26]  30  
04:55:07: RADIUS: Cisco AVpair       [1]   24  "session-protocol=cisco"
04:55:07: RADIUS:  Vendor, Cisco       [26]  35  
04:55:07: RADIUS:   Cisco AVpair       [1]   29  "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:07: RADIUS:  User-Name           [1]   4   "22"
04:55:07: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
04:55:07: RADIUS:  Calling-Station-Id  [31]  4   "22"
04:55:07: RADIUS:  Called-Station-Id   [30]  4   "11"
04:55:07: RADIUS:  Service-Type        [6]   6   Login                     [1]
04:55:07: RADIUS:  NAS-IP-Address      [4]   6   10.6.43.101                
04:55:07: RADIUS:  Acct-Delay-Time     [41]  6   0                         
04:55:07: EM: No consumer registered for event type NEWINFO
04:55:07: EM: Notify the producer not to produce
04:55:07: EM: No consumer registered for event type NEWINFO
04:55:07: EM: Notify the producer not to produce
04:55:08: RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x0000
04:55:08: RADIUS: Retransmit to (10.6.10.203:1645,1646) for id 21645/50
04:55:08: RADIUS: acct-delay-time for 403963FC (at 403965A1) now 1
04:55:09: RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x0000
04:55:09: RADIUS: Retransmit to (10.6.10.203:1645,1646) for id 21645/49
04:55:09: RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 1
04:55:10: RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x0000
04:55:10: RADIUS: Fail-over to (10.8.159.105:1645,1645) for id 21645/51
04:55:10: RADIUS: acct-delay-time for 403963FC (at 403965A1) now 2
04:55:10: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.8.159.105
04:55:10: RADIUS: Received from id 21645/53 10.8.159.105:1645, Accounting-response, len 20
04:55:10: RADIUS:  authenticator 57 EF DD 90 0F 88 76 EA - A5 3D A7 44 0D 90 66 16
04:55:10: vstats_acct_rsp_handler:   methodlist=h323, rsp_type=0x1
04:55:10: acct_rsp_status=1 callid= 26, incoming=0, leg=2
04:55:10: vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h323
04:55:10: RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x0000
04:55:10: RADIUS: Fail-over to (10.8.159.105:1645,1645) for id 21645/52
04:55:10: RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 2
04:55:10: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.8.159.105
04:55:10: RADIUS: Received from id 21645/54 10.8.159.105:1645, Accounting-response, len 20
04:55:10: RADIUS:  authenticator 97 88 6C BA DA 22 E7 5E - 73 EC 21 C6 36 1B 93 18
04:55:10: vstats_acct_rsp_handler:   methodlist=h323, rsp_type=0x1
04:55:10: acct_rsp_status=callid= 25, incoming=1, leg=1
04:55:10: vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h323
04:55:13: RADIUS(0000001A): Config NAS IP: 0.0.0.0
04:55:13: RADIUS(0000001A): sending
04:55:13: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.6.10.203
04:55:13: RADIUS(0000001A): Send Accounting-Request to 10.6.10.203:1646 id 21645/55,len885
04:55:13: RADIUS:  authenticator F8 4F F1 30 7E 8B 5B 46 - EF AE 17 2D 5C BA 36 E5
04:55:13: RADIUS:  Acct-Session-Id     [44]  10  "00000021"
04:55:13: RADIUS:  Vendor, Cisco       [26]  57  
04:55:13: RADIUS:   h323-setup-time    [25]  51  "h323-setup-time=*16:22:31.006 UTC 
          Thu Feb 13 2003"
04:55:13: RADIUS:  Vendor, Cisco       [26]  27  
04:55:13: RADIUS:   h323-gw-id         [33]  21  "h323-gw-id=5400-GW."
04:55:13: RADIUS:  Vendor, Cisco       [26]  56  
04:55:13: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 
          B935C142"
04:55:13: RADIUS:  Vendor, Cisco       [26]  34  
04:55:13: RADIUS:   h323-call-origin   [26]  28  "h323-call-origin=originate"
04:55:13: RADIUS:  Vendor, Cisco       [26]  27  
04:55:13: RADIUS:   h323-call-type     [27]  21  "h323-call-type=VoIP"
04:55:13: RADIUS:  Vendor, Cisco       [26]  65  
04:55:13: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=2F4ED2E3 3EA611D7 
          800E0002 B935C142"
04:55:13: RADIUS:  Vendor, Cisco       [26]  30  
04:55:13: RADIUS:   Cisco AVpair       [1]   24  "subscriber=RegularLine"
04:55:13: RADIUS:  Vendor, Cisco       [26]  30  
04:55:13: RADIUS:   Cisco AVpair       [1]   24  "session-protocol=cisco"
04:55:13: RADIUS:  Vendor, Cisco       [26]  35  
04:55:13: RADIUS:   Cisco AVpair       [1]   29  "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:13: RADIUS:  Vendor, Cisco       [26]  59  
04:55:13: RADIUS:   h323-connect-time  [28]  53  "h323-connect-time=*16:22:31.046 UTC 
          Thu Feb 13 2003"
04:55:13: RADIUS:  Acct-Input-Octets   [42]  6   2241                      
04:55:13: RADIUS:  Acct-Output-Octets  [43]  6   81       

04:55:13: RADIUS:  Acct-Input-Packets  [47]  6   113                       
04:55:13: RADIUS:  Acct-Output-Packets [48]  6   5                         
04:55:13: RADIUS:  Acct-Session-Time   [46]  6   5                         
04:55:13: RADIUS:  Vendor, Cisco       [26]  62  
04:55:13: RADIUS:   h323-disconnect-tim[29]  56  "h323-disconnect-time=*16:22:36.070 UTC 
          Thu Feb 13 2003"
04:55:13: RADIUS:  Vendor, Cisco       [26]  32  
04:55:13: RADIUS:   h323-disconnect-cau[30]  26  "h323-disconnect-cause=10"
04:55:13: RADIUS:  Vendor, Cisco       [26]  38  
04:55:13: RADIUS:   h323-remote-address[23]  32  "h323-remote-address=10.0.0.110"
04:55:13: RADIUS:  Vendor, Cisco       [26]  24  
04:55:13: RADIUS:   Cisco AVpair       [1]   18  "release-source=1"
04:55:13: RADIUS:  Vendor, Cisco       [26]  29  
04:55:13: RADIUS:   h323-voice-quality [31]  23  "h323-voice-quality=-1"
04:55:13: RADIUS:  Vendor, Cisco       [26]  57  
04:55:13: RADIUS:   Cisco AVpair       [1]   51  "alert-timepoint=*16:22:31.030 UTC 
          Thu Feb 13 2003"
04:55:13: RADIUS:  Vendor, Cisco       [26]  39  
04:55:13: RADIUS:   Cisco AVpair       [1]   33  "remote-media-address=10.0.0.110"
04:55:13: RADIUS:  Vendor, Cisco       [26]  44  
04:55:13: RADIUS:   Cisco AVpair       [1]   38  "gw-final-xlated-cdn=ton:0,npi:0,#:11"
04:55:13: RADIUS:  Vendor, Cisco       [26]  44  
04:55:13: RADIUS:   Cisco AVpair       [1]   38  "gw-final-xlated-cgn=ton:0,npi:1,#:22"
04:55:13: RADIUS:  User-Name           [1]   4   "22"
04:55:13: RADIUS:  Acct-Status-Type    [40]  6   Stop                      [2]
04:55:13: RADIUS:  Calling-Station-Id  [31]  4   "22"
04:55:13: RADIUS:  Called-Station-Id   [30]  4   "11"
04:55:13: RADIUS:  Service-Type        [6]   6   Login                     [1]
04:55:13: RADIUS:  NAS-IP-Address      [4]   6   10.6.43.101                
04:55:13: RADIUS:  Acct-Delay-Time     [41]  6   0                         
04:55:13: RADIUS(00000019): Using existing nas_port 0
04:55:13: RADIUS(00000019):Config NAS IP: 0.0.0.0
04:55:13: RADIUS(00000019):sending
04:55:13: RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 10.6.10.203
04:55:13: RADIUS(00000019): Send Accounting-Request to 10.6.10.203:1646 id 21645/56,len766
04:55:13: RADIUS:  authenticator 61 60 EB 92 29 5C DE B4 - CE 40 1C AB E3 A1 C8 F7
04:55:13: RADIUS:  Acct-Session-Id     [44]  10  "00000020"
04:55:13: RADIUS:  Vendor, Cisco       [26]  57  
04:55:13: RADIUS:   h323-setup-time    [25]  51  "h323-setup-time=*16:22:30.994 UTC Thu 
          Feb 13 2003"
04:55:13: RADIUS:  Vendor, Cisco       [26]  27  
04:55:13: RADIUS:   h323-gw-id         [33]  21  "h323-gw-id=5400-GW."
04:55:13: RADIUS:  Vendor, Cisco       [26]  56  
04:55:13: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 
          B935C142"
04:55:13: RADIUS:  Vendor, Cisco       [26]  31  
04:55:13: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
04:55:13: RADIUS:  Vendor, Cisco       [26]  32  
04:55:13: RADIUS:   h323-call-type     [27]  26  "h323-call-type=Telephony"
04:55:13: RADIUS:  Vendor, Cisco       [26]  65  
04:55:13: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=2F4ED2E3 3EA611D7 
          800E0002 B935C142"
04:55:13: RADIUS:  Vendor, Cisco       [26]  30  
04:55:13: RADIUS:   Cisco AVpair       [1]   24  "subscriber=RegularLine"
04:55:13: RADIUS:  Vendor, Cisco       [26]  35  
04:55:13: RADIUS:   Cisco AVpair       [1]   29  "gw-rxd-cdn=ton:0,npi:0,#:11"
04:55:13: RADIUS:  Vendor, Cisco       [26]  32  
04:55:13: RADIUS:   Cisco AVpair       [1]   26  "calling-party-category=9"
04:55:13: RADIUS:  Vendor, Cisco       [26]  33  
04:55:13: RADIUS:   Cisco AVpair       [1]   27  "transmission-medium-req=0"
04:55:13: RADIUS:  Vendor, Cisco       [26]  59  
04:55:13: RADIUS:   h323-connect-time  [28]  53  "h323-connect-time=*16:22:31.046 UTC Thu 
          Feb 13 2003"
04:55:13: RADIUS:  Acct-Input-Octets   [42]  6   81                        
04:55:13: RADIUS:  Acct-Output-Octets  [43]  6   2241             

04:55:13: RADIUS:  Acct-Input-Packets  [47]  6   5                         
04:55:13: RADIUS:  Acct-Output-Packets [48]  6   113                       
04:55:13: RADIUS:  Acct-Session-Time   [46]  6   5                         
04:55:13: RADIUS:  Vendor, Cisco       [26]  62  
04:55:13: RADIUS:   h323-disconnect-tim[29]  56  "h323-disconnect-time=*16:22:36.064 UTC 
          Thu Feb 13 2003"
04:55:13: RADIUS:  Vendor, Cisco       [26]  32  
04:55:13: RADIUS:   h323-disconnect-cau[30]  26  "h323-disconnect-cause=10"
04:55:13: RADIUS:  Vendor, Cisco       [26]  35  
04:55:13: RADIUS:   Cisco AVpair       [1]   29  "h323-ivr-out=Tariff:Unknown"
04:55:13: RADIUS:  Vendor, Cisco       [26]  24  
04:55:13: RADIUS:   Cisco AVpair       [1]   18  "release-source=1"
04:55:13: RADIUS:  Vendor, Cisco       [26]  28  
04:55:13: RADIUS:   h323-voice-quality [31]  22  "h323-voice-quality=0"
04:55:13: RADIUS:  User-Name           [1]   4   "22"
04:55:13: RADIUS:  Acct-Status-Type    [40]  6   Stop [2]
04:55:13: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
04:55:13: RADIUS:  Vendor, Cisco       [26]  20  
04:55:13: RADIUS:   cisco-nas-port     [2]   14  "ISDN 6/0:D:1"
04:55:13: RADIUS:  NAS-Port            [5]   6   0                         
04:55:13: RADIUS:  Calling-Station-Id  [31]  4   "22"
04:55:13: RADIUS:  Called-Station-Id   [30]  4   "11"
04:55:13: RADIUS:  Service-Type        [6]   6   Login                     [1]
04:55:13: RADIUS:  NAS-IP-Addres       [4]   6   10.6.43.101                
04:55:13: RADIUS:  Acct-Delay-Time     [41]  6   0                         
04:55:14: RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x0000
04:55:14: RADIUS: Retransmit to (10.6.10.203:1645,1646) for id 21645/55
04:55:14: RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 1
04:55:14: RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x0000
04:55:14: RADIUS: Retransmit to (10.6.10.203:1645,1646) for id 21645/56
04:55:14: RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 1
04:55:15: RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x0000
04:55:15: RADIUS: Fail-over to (10.8.159.105:1645,1645) for id 21645/57
04:55:15: RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 2
04:55:15: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.8.159.105
04:55:15: RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x0000
04:55:15: RADIUS: Fail-over to (10.8.159.105:1645,1645) for id 21645/58
04:55:15: RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 2
04:55:15: RADIUS/ENCODE: Best Local IP-Address 10.6.43.101 for Radius-Server 10.8.159.105
04:55:15: RADIUS: Received from id 21645/59 10.8.159.105:1645, Accounting-response, len 20
04:55:15: RADIUS:  authenticator B1 C4 5E FC DB FA 74 A4 - 05 E2 34 52 1A 11 26 06
04:55:15: vstats_acct_rsp_handler:   methodlist=h323, rsp_type=0x4
04:55:15: acct_rsp_status=1 callid= 26, incoming=0, leg=2
04:55:15: vstats_acct_rsp_handler: increment since-reset counter
04:55:15: vstats_acct_rsp_handler: increment interval counter
04:55:15: RADIUS: Received from id 21645/60 10.8.159.105:1645, Accounting-response, len 20
04:55:15: RADIUS:  authenticator 0E 70 74 2F E5 D8 EE 98 - B9 C0 DA 66 74 ED 84 77
04:55:15: vstats_acct_rsp_handler:   methodlist=h323, rsp_type=0x4
04:55:15: acct_rsp_status=1 callid= 25, incoming=1, leg=1
04:55:15: vstats_acct_rsp_handler: increment since-reset counter
04:55:15: vstats_acct_rsp_handler: increment interval counter

Using Cause Code Statistics

By examining disconnect cause codes, you can understand the distribution of the various cause codes on the voice ports, trunk groups, and gateway, and which can help you determine why the voice calls were disconnected.

The call disconnection cause values are taken from International Telecommunication Union Telecommunication Standardization Sector (ITU-T) standard Q.931 and are as follows:

Private Network-Network Interface (PNNI) references ITU-T standard Q.2931 for the information element (IE) causes.

PNNI R15 6.3.6.3 contains the "crankback" causes.

ITU-T standard Q.2931 references ITU-T standard Q.2610.

ITU-T standard Q.2610 lists a few cause codes and references ITU-T standard Q.850.

ITU-T standard Q.850 lists the bulk of the cause codes.

For specific information on the call disconnection cause values, see the Cisco IOS Voice Troubleshooting and Monitoring Guide.

Prerequisites

CSR configurations must be enabled before you can examine the voice calls that are made through the gateway.

Restrictions

Statistics of non-DID calls are not consistent with those of the underlying ISDN module.

SUMMARY STEPS

1. enable

2. show voice statistics csr since-reset aggregation-level all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics csr since-reset aggregation-level all

Example:

Router# show voice statistics csr since-reset aggregation-level all

Displays all aggregation-level statistics since the last system reset or reboot.


Example

The following sample output shows cause-code statistics since the last reset for all aggregation levels.

Router# show voice statistics csr since-reset aggregation-level all

Client Type: VCSR
        Start Time: 1993-03-01T00:03:15Z        End Time: 1993-03-03T22:02:18Z

record_type=gw,trunk_group_id=,voice_port_id=,in_call=26,in_ans=16,in_fail=10,out_call=26,
out_ans=16,out_fail=10,in_szre_d=387,out_szre_d=380,in_conn_d=330,out_conn_d=323,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=2340,
out_pdd=12340,in_setup_delay=2340,out_setup_delay=3340,lost_pkt=0,latency=0,jitter=0,
in_disc_cc_16=16,in_disc_cc_18=2,in_disc_cc_19=3,in_disc_cc_34=5,out_disc_cc_16=16,
out_disc_cc_18=2,out_disc_cc_19=3,out_disc_cc_34=5
!
record_type=ip,trunk_group_id=,voice_port_id=,in_call=26,in_ans=16,in_fail=10,out_call=0,
out_ans=0,out_fail=0,in_szre_d=387,out_szre_d=0,in_conn_d=330,out_conn_d=0,orig_disconn=0,
in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=2340,out_pdd=0,
in_setup_delay=2340,out_setup_delay=0,lost_pkt=20,latency=15,jitter=10,in_disc_cc_16=16,
in_disc_cc_18=2,in_disc_cc_19=3,in_disc_cc_34=5,out_disc_cc_16=3
!

Table 55 shows two types of cause codes listed in the output above.

Table 55 Significant Fields of the show voice statistics csr since-reset aggregation-level all Command 

Field
Description

in_disc_cc_16=16

Count of incoming calls that are disconnected with a specific cause code number. In this example, the value 16 indicates normal call clearing

out_disc_cc_16=3

Count of outgoing calls that are disconnected with a specific cause code number.


Displaying Quality of Service Indicators

The quality of service (QoS) indicators per voice call are the results of transmitting and receiving voice packets in the IP interface. These results are included in the CSRs and are as follows:

Lost packet value: the number of calls losing more than the configured number of packets. The default lost packet threshold is 1000 milliseconds.

Packet latency value: the number of calls with voice packets encountering more than the configured amount of latency. The default packet latency threshold is 250 milliseconds.

Packet jitter value: the number of calls with voice packets encountering more than the configured amount of jitter. The default packet jitter threshold is 250 milliseconds.

Before you can determine that any voice call with IP voice packets is deviating from the desired level of quality, you must configure the threshold values of lost packets, latency, and jitter. See the following sections:

Configuring the Minimum Call Duration and Signaling Thresholds

Displaying Memory Usage

Restrictions

Call statistics for MGCP calls are not guaranteed to be correct and accurate. In addition, statistics of non-DID ISDN calls are not consistent with those of the underlying ISDN module.

SUMMARY STEPS

1. enable

2. show voice statistics csr since-reset aggregation-level all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show voice statistics csr since-reset aggregation-level all

Example:

Router# show voice statistics csr since-reset aggregation-level all

Displays the voice statistics of the voice calls made through the gateway.


Example

The following sample output displays lost packet, latency, and jitter QoS information:

Router# show voice statistics csr since-reset aggregation-level all

Client Type: VCSR
        Start Time: 1993-03-01T00:03:15Z        End Time: 1993-03-03T22:02:18Z

record_type=gw,trunk_group_id=,voice_port_id=,in_call=26,in_ans=16,in_fail=10,out_call=26,
out_ans=16,out_fail=10,in_szre_d=387,out_szre_d=380,in_conn_d=330,out_conn_d=323,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=2340,
out_pdd=12340,in_setup_delay=2340,out_setup_delay=3340,lost_pkt=10,latency=3,jitter=5,
in_disc_cc_16=16,in_disc_cc_18=2,in_disc_cc_19=3,in_disc_cc_34=5,out_disc_cc_16=16,
out_disc_cc_18=2,out_disc_cc_19=3,out_disc_cc_34=5
!
record_type=ip,trunk_group_id=,voice_port_id=,in_call=26,in_ans=16,in_fail=10,out_call=0,
out_ans=0,out_fail=0,in_szre_d=387,out_szre_d=0,in_conn_d=330,out_conn_d=0,orig_disconn=0,
in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=2340,out_pdd=0,
in_setup_delay=2340,out_setup_delay=0,lost_pkt=10,latency=3,jitter=5,in_disc_cc_16=16,
in_disc_cc_18=2,in_disc_cc_19=3,in_disc_cc_34=5,out_disc_cc_16=0
!

Configuration Examples for Voice Performance Statistics on Cisco Gateways

This section includes the following examples:

User-Specific Configurations for Call Statistic Collection: Example

Manually Clearing Statistics: Example

Collection of Aggregation-Level Statistics: Example

Memory Usage: Example

Collection of Statistics Since System Reset: Examples

Designated Server Group: Example

Location of the FTP Server: Example

Maximum File Size for the Syslog Server: Example

Maximum Duration for Storage: Example

User-Specific Configurations for Call Statistic Collection: Example

The following example shows the user-specific configuration that includes accounting method, time ranges, maximum storage duration, and the archiving of the statistics to an FTP and syslog server:

Router# show running-config | include voice statistics

voice statistics accounting method h323-1 pass start-interim-stop
voice statistics time-range since-reset
voice statistics time-range periodic 5minutes start 00:00 end 00:00 days-of-week daily
voice statistics max-storage-duration minute 40
voice statistics push ftp url ftp://sgcp:sgcp@anyone-pc:21//ftp_files
voice statistics push syslog max-file-size 4000000000
voice statistics display-format separator new-line
voice statistics field-params lost-packet 1000
voice statistics field-params mcd 2
voice statistics field-params packet-jitter 255
voice statistics field-params packet-latency 150

Note The type of statistics is not shown in a running configuration because the voice statistics type csr command activates only the collection of statistics. If you do not specify a type, both signaling and accounting statistics are collected.


Manually Clearing Statistics: Example

The following example shows how to clear all of the voice statistics that have been collected:

Router# clear voice statistics csr

The following example verifies the clearing by showing that all of the parameters have been set to zero:

Router# show voice statistics csr since-reset all

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-04-25T01:49:27Z

record_type=gw,trunk_group_id=,voice_port_id=,in_call=0,in_ans=0,in_fail=0,out_c
all=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,
out_pdd=0,in_setup_delay=0,out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0
out_disc_cc_16=0
!
record_type=ip,trunk_group_id=,voice_port_id=,in_call=0,in_ans=0,in_fail=0,out_c
all=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0,
out_disc_cc_16=0
!
record_type=pstn,trunk_group_id=,voice_port_id=,in_call=0,in_ans=0,in_fail=0,out_call=0,
out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,orig_disconn=0,
in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,in_setup_delay=0,
out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!
record_type=vp,trunk_group_id=,voice_port_id=4/0/0,in_call=0,in_ans=0,in_fail=0,
out_call=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,
out_pdd=0,in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!
Client Type: Voice ACCT Stats
        Start Time: 2002-04-25T01:48:04Z        End Time: 2002-04-25T01:49:30Z

methodlist=h323-1,acc_pass_criteria=0,pstn_in_pass=0,pstn_in_fail=0,pstn_out_pass=0,
pstn_out_fail=0,ip_in_pass=0,ip_in_fail=0,ip_out_pass=0,ip_out_fail=0

Collection of Aggregation-Level Statistics: Example

The following example shows the different levels of signaling statistics that can be collected:

Router# show voice statistics csr since-reset aggregation-level ?

  all          Statistics at all signaling levels
  gateway      Gateway wide
  ip           Voip interface level
  pstn         Telephony interface level
  trunk-group  Trunk group level
  voice-port   Voice-port level

The following example shows the collected statistics:

Router# show voice statistics csr since-reset aggregation-level all

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-04-25T01:50:01Z

record_type=gw,trunk_group_id=12,voice_port_id=1/0,in_call=10,in_ans=10,in_fail=0,
out_call=3,out_ans=0,out_fail=3,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
!
record_type=ip,trunk_group_id=1,voice_port_id=2/0,in_call=1,in_ans=1,in_fail=0
!
record_type=pstn,trunk_group_id=,voice_port_id=,in_call=0,in_ans=0,in_fail=0,out_call=0,
out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,o
!
record_type=vp,trunk_group_id=1,voice_port_id=4/0/0,in_call=0,in_ans=0,in_fail=0,
out_call=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!

The following example shows the intervals at which statistics were collected:

Router# show voice statistics interval-tag

Current Time: 2002-04-25T01:52:11Z

INTERVAL-TAG   START TIME             END TIME
============== ====================== ======================
10             2002-04-25T01:10:00Z   2002-04-25T01:15:00Z
11             2002-04-25T01:15:00Z   2002-04-25T01:20:00Z
12             2002-04-25T01:20:00Z   2002-04-25T01:25:00Z
13             2002-04-25T01:25:00Z   2002-04-25T01:30:00Z
14             2002-04-25T01:30:00Z   2002-04-25T01:35:00Z
15             2002-04-25T01:35:00Z   2002-04-25T01:40:00Z
16             2002-04-25T01:40:00Z   2002-04-25T01:45:00Z
17             2002-04-25T01:45:00Z   2002-04-25T01:50:00Z
18             2002-04-25T01:50:00Z   2002-04-25T01:52:11Z

Memory Usage: Example

The following example shows the amount of memory being used for accounting and signaling CSRs by fixed interval and since a reset or reboot. It also shows the estimated memory allocated for future use.

Router# show voice statistics memory-usage csr

*** Voice Call Statistics Record Memory Usage ***
        Fixed Interval Option -
                CSR size: 136 bytes
                Number of CSR per interval: 9
                Used memory size (proximate): 0
                Estimated future claimed memory size (proximate): 10
        Since Reset Option -
                CSR size: 136 bytes
                Total count of CSR: 9
                Used memory size (proximate): 1224

*** Voice Call Statistics Accounting Record Memory Usage ***
        Fixed Interval Option -
                ACCT REC size: 80 bytes
                Number of ACCT REC per interval: 1
                Used memory size (proximate): 0
                Estimated future claimed memory size (proximate): 25
        Since Reset Option -
                ACCT REC size: 80 bytes
                Total count of ACCT REC: 1
                Used memory size (proximate): 80

Collection of Statistics Since System Reset: Examples

This section provides the following examples:

Example of the show voice statistics csr since-reset accounting all Command

Example of the show voice statistics csr since-reset aggregation-level all Command

Example of the show voice statistics csr since-reset aggregation-level gateway Command

Example of the show voice statistics csr since-reset aggregation-level ip Command

Example of the show voice statistics csr since-reset aggregation-level pstn Command

Example of the show voice statistics csr since-reset aggregation-level trunk-group all Command

Example of the show voice statistics csr since-reset aggregation-level voice-port all Command

Example of the show voice statistics csr since-reset accounting all Command

The following example shows all accounting statistics:

Router# show voice statistics csr since-reset accounting all

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time:2002-04-25T01:50:01Z
methodlist=h323-1,acc_pass_criteria=1,pstn_in_pass=10,pstn_in_fail=0,pstn_out_pass=10
pstn_out_fail=0,ip_in_pass=15,ip_in_fail=0,ip_out_pass=15,ip_out_fail=0

Example of the show voice statistics csr since-reset aggregation-level all Command

The following example shows all aggregation level statistics:

Router# show voice statistics csr since-reset aggregation-level all

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-04-25T01:50:01Z

record_type=gw,trunk_group_id=1,voice_port_id=2,in_call=120,in_ans=120,in_fail=0
out_call=10,out_ans=10,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0,
out_disc_cc_16=0
!
record_type=ip,trunk_group_id=2,voice_port_id=3,in_call=120,in_ans=120,in_fail=0
out_call=10,out_ans=10,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0,
out_disc_cc_16=0
!
record_type=pstn,trunk_group_id=5,voice_port_id=2,in_call=150,in_ans=100,in_fail=50,
out_call=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0

Example of the show voice statistics csr since-reset aggregation-level gateway Command

The following example shows the gateway aggregation level statistics:

Router# show voice statistics csr since-reset aggregation-level gateway

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-05-02T21:21:14Z

record_type=gw,trunk_group_id=1,voice_port_id=1,in_call=10,in_ans=10,in_fail=0,out_call=50
out_ans=10,out_fail=40,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,orig_disconn=0,
in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,in_setup_delay=0,
out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0,out_disc_cc_16=0

Example of the show voice statistics csr since-reset aggregation-level ip Command

The following example shows the IP aggregation level statistics:

Router# show voice statistics csr since-reset aggregation-level ip

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-05-02T21:21:27Z

record_type=ip,trunk_group_id=1,voice_port_id=1,in_call=10,in_ans=10,in_fail=0,out_call=50
out_ans=10,out_fail=40,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,orig_disconn=0,
in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,in_setup_delay=0,
out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0,out_disc_cc_16=0

Example of the show voice statistics csr since-reset aggregation-level pstn Command

The following example shows the PSTN aggregation level statistics:

Router# show voice statistics csr since-reset aggregation-level pstn

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-05-02T21:21:42Z

record_type=pstn,trunk_group_id=1,voice_port_id=1,in_call=10,in_ans=10,in_fail=0,
out_call=50,out_ans=10,out_fail=40,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,lost_pkt=0,latency=0,jitter=0,in_disc_cc_16=0,
out_disc_cc_16=0

Example of the show voice statistics csr since-reset aggregation-level trunk-group all Command

The following example shows the trunk-group aggregation level statistics:

Router# show voice statistics csr since-reset aggregation-level trunk-group all

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-05-02T21:22:08Z

record_type=pstn,trunk_group_id=15,voice_port_id=3,in_call=20,in_ans=20,in_fail=0,
out_call=10,out_ans=10,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!
record_type=pstn,trunk_group_id=16,voice_port_id=4,in_call=20,in_ans=20,in_fail=0,
out_call=10,out_ans=10,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!
record_type=pstn,trunk_group_id=17,voice_port_id=5,in_call=20,in_ans=20,in_fail=0,
out_call=10,out_ans=10,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!
record_type=pstn,trunk_group_id=18,voice_port_id=6,in_call=20,in_ans=20,in_fail=0,
out_call=10,out_ans=10,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0

Example of the show voice statistics csr since-reset aggregation-level voice-port all Command

The following example shows the voice-port aggregation level statistics:

Router# show voice statistics csr since-reset aggregation-level voice-port all

Client Type: VCSR
        Start Time: 2002-04-25T01:48:12Z        End Time: 2002-05-02T21:22:52Z

record_type=vp,trunk_group_id=a,voice_port_id=4/0/0,in_call=22,in_ans=14,in_fail=8,
out_call=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0
!
record_type=vp,trunk_group_id=b,voice_port_id=4/0/1,in_call=22,in_ans=14,in_fail=8,
out_call=0,out_ans=0,out_fail=0,in_szre_d=0,out_szre_d=0,in_conn_d=0,out_conn_d=0,
orig_disconn=0,in_ans_abnorm=0,out_ans_abnorm=0,in_mcd=0,out_mcd=0,in_pdd=0,out_pdd=0,
in_setup_delay=0,out_setup_delay=0,in_disc_cc_16=0,out_disc_cc_16=0

Designated Server Group: Example

The following example shows that a designated server group has been configured for a broadcast method list.

Router# show voice statistics | begin aaa group server

aaa group server radius billing-grp
 server 1.6.37.20 auth-port 1645 acct-port 1646
 accounting acknowledge broadcast

Location of the FTP Server: Example

The following example shows the location of the FTP server:

Router# show running-config

Building configuration...

Current configuration : 5444 bytes
!
version 12.3
!
voice statistics push ftp url ftp://sgcp:sgcp@abc-pc:21//ftp_files
voice statistics push ftp max-file-size 4000000000
!

Maximum File Size for the Syslog Server: Example

The following example shows the maximum file size to be downloaded to the syslog server:

Router# show running-config

Building configuration...

Current configuration : 5444 bytes
!
version 12.3
!
voice statistics push syslog max-msg-size 4000000000

Maximum Duration for Storage: Example

The following configuration example shows a maximum storage of 60 minutes:

Router# show running-config | include voice statistics
!
voice statistics max-storage-duration minute 60