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

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

* [[Cisco IOS Voice Troubleshooting and Monitoring -- Voice Performance Statistics on Cisco Gateways#Configuring the FTP Server to Enable Archiving of Statistics from the Gateway|Configuring the FTP Server to Enable Archiving of Statistics from the Gateway]]

* [[Cisco IOS Voice Troubleshooting and Monitoring -- Voice Performance Statistics on Cisco Gateways#Configuring the FTP Server to Enable Archiving of Statistics from the Gateway|Configuring the FTP Server to Enable Archiving of Statistics from the Gateway]]

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).

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)'

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.

3. Configure xinetd.conf.

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

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.

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:

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.

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

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:

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

2. 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.

3. 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

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

guestgroup group1
realuser user2

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).

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.

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.

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).

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

enable

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

DETAILED STEPS

Command or Action

Purpose

1.

enable
Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

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

enable

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

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

DETAILED STEPS

Command or Action

Purpose

1.

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

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.

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:

Table: 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: