VG248 Software Configuration Guide v1.3
Troubleshooting the VG248
Downloads: This chapterpdf (PDF - 411.0KB) The complete bookPDF (PDF - 2.07MB) | Feedback

Troubleshooting the VG248

Table Of Contents

Troubleshooting the VG248

Troubleshooting Hardware Errors

Displaying Hardware Status

Identifying Fan Faults

Identifying Power Supply Faults

Monitoring Internal Operating Temperature

Connecting Too Many Phones to the VG248

Resolving Additional Hardware Errors

Troubleshooting Software Errors

Resolving Network and System Errors

Resolving Cisco CallManager Errors

Resolving Analog Errors

Resolving Voice Mail Errors and Warnings

Upgrading or Restoring Software Images

Suspending Voice Mail Port Activity

Upgrading the Main Image

Upgrading the Boot Loader

Resolving an Incomplete Upgrade

Restoring to Factory Defaults

Verifying Connectivity

Verifying Network Connectivity

Validating the SMDI Connection and Configuration

Displaying Status and Configuration Settings

Displaying System Status

Displaying Network Statistics

Displaying Port Status

Displaying Detailed Port Status

Displaying Port Statistics

Displaying Current Configuration

Displaying VG248 Device Configuration

Displaying Port Configuration

Displaying Software Version

Monitoring the CPU Utilization

Monitoring System Status Remotely

Working with the Event Log

Identifying a Syslog Server

Enabling Syslog

Identifying a Specific Syslog Server

Selecting Logging Levels and Logged Ports

Displaying Recent Messages

Understanding Sub-Systems on the VG248

Resolving Incorrect Date and Time in Event Log


Troubleshooting the VG248


The VG248 includes several built-in troubleshooting and diagnostic features. Use these sections for details about troubleshooting:

Troubleshooting Hardware Errors

Troubleshooting Software Errors

Upgrading or Restoring Software Images

Verifying Connectivity

Displaying Status and Configuration Settings

Monitoring System Status Remotely

Working with the Event Log

Troubleshooting Hardware Errors

The VG248 can identify some potential hardware problems with the fans, power supplies, the operating temperature, and other hardware systems.

These sections provide information about how the VG248 identifies these potential problems and how to resolve them:

Displaying Hardware Status

Identifying Fan Faults

Identifying Power Supply Faults

Monitoring Internal Operating Temperature

Connecting Too Many Phones to the VG248

Resolving Additional Hardware Errors

Displaying Hardware Status

If potential hardware failures are detected, warning messages appear on the main interface window. However, you can also proactively monitor the current operating environment on the VG248.

Procedure

To do this, follow these steps:


Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Show environment.

The following information about the VG248 displays:

Internal temperature

1.8 volts supply

3.3 volts supply

5.0 volts supply

12.0 volts supply

48.0 volts supply

96.0 volts supply

Chassis fan state

The voltages and temperatures are indicated with the actual values and "okay", "too high", or "too low" annotating the values. The fan status is identified as "okay" or "faulty".


Identifying Fan Faults

If a fan fault is reported, it indicates that one (or more) of the fans is not functioning. You should verify that nothing is lodged in the holes in the rear of the device, but do not make any attempt to open the device or move the fans. You should contact a technical support representative from Cisco Systems for assistance.

Identifying Power Supply Faults

The internal DC supply voltages are measured continuously (+1.8v, +3.3v, +5.0v, +12.0v, -48v, -96v).

The 1.8v and 3.3v voltages must be within +/- 6% of nominal, and the others must be within +/- 10%. If any of these values are outside this range, then the VG248 reports a power supply fault.

If the phone power supplies (-48v and -96v) fail, it might indicate that the VG248 is overloaded. Verify that you have not exceeded the maximum ringer equivalency number (REN) load for each line. You should only have a maximum REN load of three (3). Because some devices might have a REN load greater than one (1), you cannot necessarily connect three devices to the chain.

If one of the other power supplies fails, you should contact a Cisco technical representative for assistance.

Monitoring Internal Operating Temperature

The VG248 monitors its internal temperature to ensure that it is operating within the specified limits (the ambient operating environment should be 0° to 40° C or 32° to 104° F). If the VG248 identifies internal temperatures too low or too high, it generates warning messages. Continuing to operate at ranges exceeding these limits (either too low or too high) can damage the VG248.

If the operating temperature of the VG248 is too low, there is a risk of condensation forming inside the device. You should move the device to a warmer location to prevent this.

If the operating temperature of the VG248 is too high, you should move the device to a cooler location with improved ventilation. The internal fans on the VG248 maintain the internal temperature consistent with the ambient environment. Therefore, if the device is in a location that is too warm, its internal temperature is more likely to exceed the limits.

There are two levels of high temperature alert:

yellow alert—generates and logs an error, but enables the device to continue functioning

red alert—causes all the phones to be immediately shut down, causing calls to drop and preventing calls from being made. You must manually restart the VG248 either by selecting Configure > Restart or by disconnecting power from the device.

Connecting Too Many Phones to the VG248

The VG248 has a maximum ringer equivalency number (REN) load of three (3) per line (using a shared directory number), and only two devices can be off-hook at any one time. Because some devices might have a REN load greater than one (1), you cannot necessarily connect three devices to the chain. If these requirements are ignored, you might experience reduced quality on these analog phones, including:

Difficulty hearing caller—Users have too many phones off-hook. Do not have more than two phones per line off-hook simultaneously.

Dialing or caller ID on call waiting are not working properly—Users have too many phones off-hook. Do not have more than two phones per line off-hook simultaneously.

Phones not ringing properly or at all—REN load has been exceeded. Do not exceed the REN of three (3) per line.

Phone power supplies (-48v and -96v) fail—REN load has been exceeded. Do not exceed the REN of three (3) per line. See the "Identifying Power Supply Faults" section for additional information.

Resolving Additional Hardware Errors

Table 6-1 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log) which are caused by a hardware fault. Use this information to resolve these errors.

Table 6-1 Hardware Errors and Warnings Explanation 

System
Error
Explanation
Action

DSP

DSP X on SIM Y has failed

One of the Digital Signal Processor (DSP) chips inside the VG248 has failed.

Contact a Cisco technical representative for assistance.

DSP

DSP X, SIM Y failed to boot

OS

Ethernet has gone down

Ethernet has gone down at the physical level.

Verify that the Ethernet cable is properly connected to the VG248 and that the hub or switch to which it is connected is up and running properly.

SCCP

Failed to update real-time clock

The on-board real-time clock in the VG248 has failed to set the time from Cisco CallManager.

Contact a Cisco technical representative for assistance.

SLIC

EDSP failure warning received

A transient fault has been detected in the SLICs (the hardware that drives the analog telephony interfaces).

If these messages persist, contact a Cisco technical representative for assistance.

SLIC

Over-temperature warning received

SLIC

PCM synchronization failure warning received


Troubleshooting Software Errors

The VG248 displays informational messages and errors on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which indicate potential software problems, such as misconfiguration, time-outs, unreachable servers, and so on.

The following sections provide details about resolving these errors:

Resolving Network and System Errors

Resolving Voice Mail Errors and Warnings

Resolving Analog Errors

Resolving Voice Mail Errors and Warnings

Resolving Network and System Errors

Table 6-2 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which are caused by a misconfiguration or miscommunication with the network or system settings. Use this information to resolve these errors.

Table 6-2 Network and System Errors and Warnings Explanation 

System
Error
Explanation
Action

DHCP

Invalid TFTP information received from DHCP server

Although the VG248 received TFTP information from the DHCP server, it was not valid.

The VG248 might not have enough information to retrieve telephony port configuration or register with Cisco CallManager.

Check configuration of DHCP server. If errors persist, assign a static IP address and manually enter settings for the TFTP server. Refer to the "Configuring Network Settings" section for details on assigning a static IP address.

DHCP

IP address cannot be allocated

No DHCP server responded to the request.

Check configuration of DHCP server. If errors persist, assign a static IP address. Refer to the "Configuring Network Settings" section for details on assigning a static IP address.

DHCP

IP address conflict with device <address>

The DHCP server allocated an IP address to the VG248 that is already in use by another device on the network.

1. Check your DHCP server configuration to ensure that addresses allocated are not reserved for static IP use.

2. Check your network for misconfigured devices.

DHCP

IP address refused

The DHCP server rejected the VG248's request for an IP address.

Check configuration of DHCP server. If errors persist, assign a static IP address. Refer to the "Configuring Network Settings" section for details on assigning a static IP address.

DHCP

Network interface will be shut down

A previous error caused the network interface to be shut down.

Check the event log for errors.

DHCP

Static IP address conflict with device <address>

The VG248 has a static IP address that is already assigned to another device on the network.

Assign a different static IP address for either the VG248 or the conflicting device. Refer to the "Configuring Network Settings" section for details on assigning a static IP address.

DNS

No response from primary server

The DNS server failed to respond to one or more requests from the VG248.

1. If the VG248 has a static IP address, verify the DNS server has been configured. Refer to the "Setting the DNS Server" section for details.

2. Verify that the DNS server is working properly.

DNS

Server address not configured

A DNS query has been attempted, but no DNS server has been configured.

1. If the VG248 has a static IP address, verify the DNS server has been configured. Refer to the "Setting the DNS Server" section for details.

2. If you are using DHCP, the DHCP server has not provided a DNS server. Check the DHCP server configuration.

DSP

DTMF tone transmit buffer overflow

There is a finite number of DTMF tones that can be queued up to be played through the VG248's analog ports. Each of these tones takes about 200 milliseconds to be played, and the instructions to play these tones might arrive much faster via the Ethernet interface. Thus, the VG248 might not be able to store all the tones that need to be played.

No action is required. If this situation occurs, the warning appears indicating that some tones have been discarded.

DSP

DTMF tone transmit buffer reactivated

The overflow condition has ceased and DTMF tones are being sent to the attached analog device.

No action is required. This message is informational only.

FTP

Invalid password entered

An attempt was made to connect to the VG248 via FTP with the wrong password.

Verify that you have entered the password for the highest level of security currently set. When using FTP, if you have both a login and an enable password set, you must use the enable password.

Refer to the "Configuring Passwords" section for details.

FTP

Partial download aborted

An attempt to download a file onto the VG248 was interrupted before the entire file was transferred.

The resulting partial file has been deleted from the filing system on the VG248.

Reattempt the file transfer.

FTP

Required password absent

An attempt was made to connect to the VG248 via FTP without a password when one was required.

When using FTP, if you have both a login and an enable password set, you must use the enable password.

Refer to the "Configuring Passwords" section for details.

OS

Ethernet failed to restart

The Ethernet cable is not properly connected to the VG248 or to the hub or switch.

Check the Ethernet cable and reconnect it to the VG248 and the hub or switch. If error persists, replace cable.

OS

Ethernet failed to start

OS

Incorrect password entered

A user attempted to use a telnet, console, or FTP connection to the VG248 but entered an incorrect password.

Check the passwords and verify that you are using the correct one.

Change the password if you suspect an unauthorized login attempt. Refer to the "Configuring Passwords" section for details.

SNMP

Attempt to use Get with invalid community name "<name>"

The VG248 received an SNMP request with an invalid read-only community name (password).

Check the community string setting on the VG248 and ensure that your network management system has the correct password. Refer to the "Configuring SNMP Settings" section for details.

SNMP

Attempt to use Set with invalid community name "<name>"

The VG248 received an SNMP request with an invalid read-write community name (password).

Check the community string setting on the VG248 and ensure that your network management system has the correct password. Refer to the "Configuring SNMP Settings" section for details.

SNMP

Received invalid packet

The SNMP server received an invalid SNMP request.

Verify that your network management system is set up properly.

TFTP

TFTP: Rx error

The VG248 is unable to retrieve a file using TFTP.

These errors might occur if the network is busy. The errors should resolve themselves when the network load reduces.

TFTP

Timeout


Resolving Cisco CallManager Errors

Table 6-3 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which are caused by a misconfiguration or miscommunication with the Cisco CallManager system. Use this information to resolve these errors.

Table 6-3 Cisco CallManager Errors and Warnings Explanation 

System
Error
Explanation
Action

SCCP

Attempt to use; currently disabled

A user has attempted to use a telephone handset attached to a VG248 port, which is currently disabled.

To allow the user to make and receive calls, you must enable the port so it can register with Cisco CallManager.

See "Setting the Port Enable Policy" section for details.

SCCP

SCCP: Failed to connect to SRST provider

You have configured an SRST provider, but the device does not appear to be responding as an SRST server. If you are relying on SRST and see this warning, the VG248 might have difficulty using SRST services if connectivity to Cisco CallManager is lost.

Check the configuration and status of the SRST device.

SCCP

SCCP: Failed to resolve SRST provider host name

An SRST provider name has been configured, but the VG248 is unable to resolve that name to an IP address.

Change the configured name, or (if experiencing DNS problems) change the SRST provider menu entry to be an IP address instead of a host name.

SCCP

No TFTP server address

The TFTP server has not been set.

1. If using DHCP to obtain TFTP server, check your DHCP server configuration.

2. If you want to use a fixed TFTP server, you must configure it on the VG248 Refer to the "Identifying the Cisco CallManager TFTP Server" section to assign a TFTP server for details.

SCCP

Registration failed: X

This message, associated with a particular port (1 - 48), indicates that the port had difficulty registering itself with Cisco CallManager.

If a port is not properly registered, then you cannot make phone calls using it.

The reason that registration with Cisco CallManager failed is indicated in the message.

If the port cannot successfully register, verify that the port is properly configured in Cisco CallManager.

See "Configuring VG248 Ports Using Cisco CallManager" section for details.

SCCP

Registration failures; last reason X

SCCP

SCCP:SRST in use

One or more ports are registered with the SRST provider rather than a normal Cisco CallManager server. Connectivity to the Cisco CallManager cluster has been at least partially lost.

Check the status of the Cisco CallManager cluster and the network connection between it and the VG248.

SCCP

TFTP failed; using last known good configuration

A port on the VG248 has failed to retrieve its configuration using TFTP. Instead, the VG248 is using the configuration stored last time the port successfully registered with Cisco CallManager.

No action is required. However, this message might indicate a potential problem with connectivity to the TFTP server. Verify that the TFTP server is up and running.

SCCP

Unable to resolve TFTP server name

The VG248 was not able to locate the TFTP server.

Verify the name of the TFTP server the VG248 is attempting to locate using Display > System Status.

If using DHCP, check the configuration on the DHCP server to verify that it is returning a valid TFTP server name to the VG248.

If you are using a fixed TFTP server, verify the configured server name using Configure -> Telephony > CallManager TFTP server.


Resolving Analog Errors

Table 6-4 describes errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log), which are caused by a misconfiguration or miscommunication with the analog phones or features. Use this information to resolve these errors.

Table 6-4 Analog Errors and Warnings Explanation 

System
Error
Explanation
Action

POTS

Feature codes: X same as Y

You have configured the telephone feature codes such that the code for one operation (such as speed dial) is the same as for another (such as call forward).

Users will not be able to use one of these operations. You must set unique feature codes for each operation.

To prohibit users from performing an operation, leave the feature code setting empty. See the "Assigning Feature Codes" section.

POTS

Feature codes: X precludes Y

You have configured the telephone feature codes such that the code for one operation masks that for a second operation. For example, if the feature code for speed dial 1 is *** and the code for speed dial 2 is ****, you could never use speed dial 2. Instead, as soon you dial the third *, speed dial 1 activates.

Do not assign features codes that might mask other operations.

See the "Assigning Feature Codes" section for details.


Resolving Voice Mail Errors and Warnings

Table 6-5 describes voice mail errors and warnings that might appear on the VG248 either on-screen or in the event log (see the "Working with the Event Log" section for details on accessing the event log) which are caused by voice mail problems. Use this information to resolve these errors.

Table 6-5 Voice Mail Errors and Warnings Explanation 

System
Message
Explanation
Action

SCCP

CallManager MWI off directory number not defined

These errors are generated when the VG248 attempts to perform a MWI operation on a phone connected to Cisco CallManager, but the required Cisco CallManager directory number has not been configured.

You must enter the MWI set and clear directory numbers for Cisco CallManager. See the "Identifying the Directory Number for Setting MWI on Cisco CallManager" section and "Identifying the Directory Number for Clearing MWI on Cisco CallManager" section.

SCCP

CallManager MWI on directory number not defined

SCCP

MWI off attempt failed-directory number may be incorrect

These messages are generated when the VG248 has attempted to set or clear a Message Waiting Indicator for a particular extension but has failed to do so.

Verify that you have entered the correct MWI set and clear directory numbers for Cisco CallManager. See the "Identifying the Directory Number for Setting MWI on Cisco CallManager" section and "Identifying the Directory Number for Clearing MWI on Cisco CallManager" section.

SCCP

MWI on attempt failed-directory number may be incorrect

VM

Async 1 now active

These messages indicate that the VG248 has detected that it is now connected to another system via the indicated Async port, or the connection has gone down.

These messages are informational only.

VM

Async 1 now inactive

VM

Async 2 now active

VM

Async 2 now inactive

VM

First voice mail port number / Number of VM ports invalid

If a port number configuration problem is detected when generating a voice mail incoming call message, this error appears. For example, the SMDI protocol limits the number of ports to 9999 using a four-digit format. If you set the first voice mail port number to 9990, and the number of voice mail ports to 10, the last VG248 voice mail port would correspond to the voice mail system's port 10000, which is invalid.

Verify that you have configured the number of voice mail ports and the first voice mail port number following the guidelines of the voice mail protocol you are using.

See the "Assigning Number of Voice Mail Ports" section and the "Identifying the First Voice Mail Port Number" section for additional assistance.

VM

Required Async 1 link has gone down

Certain voice mail configuration settings require the use of one or both Async ports. For example, if the Number of Voice mail ports is greater than 0, Async 1 must be active. If Forward MWIs to Async 2 is enabled, Async 2 should be up.

If a required Async port either fails to come up when the box starts up or goes down at some point during its operation, the VG248 generates these messages.

Check the cables on the Async 1 and Async 2 ports to verify that they are still connected.

VM

Required Async 1 link has not come up

VM

Required Async 2 link has gone down

VM

Required Async 2 link has not come up

VM

VM: Suspending Async 1 port transmission due to overflow

The VG248 has too much data to send on one of its Async links, and it has ceased queueing new data for transmission until the backlog clears.

These messages do not typically appear, but they are indicative of a serial communication.

VM

VM: Suspending Async 2 port transmission due to overflow

VM

Voice mail number format too long

The voice mail number format setting allows extra digits to be added to Cisco CallManager voice mail box numbers or directory numbers.

If the VG248 is asked to use a number format that is longer than the length of mail box numbers passed to the voice mail system, this error occurs.

Verify that you set the number format to support the mail box number in your system. See the "Setting the Number Format" section for details.


Upgrading or Restoring Software Images

The VG248 has two software images: a main software image and a boot loader. If necessary, you can upgrade these software images. You can also reset the software settings to their default values.

Suspending Voice Mail Port Activity

Upgrading the Main Image

Upgrading the Boot Loader

Resolving an Incomplete Upgrade

Restoring to Factory Defaults

Suspending Voice Mail Port Activity

If you are using the chained configuration and want to temporarily remove one of the VG248 devices or upgrade software on it, you should suspend activity on the voice mail ports before shutting down or restarting the VG248.

By suspending activity, the VG248 waits for the port to become idle, then it temporarily removes the port from Cisco CallManager and suspends the port, preventing any activity on it. Once all the ports have been suspended, traffic from Aysnc 1 is also suspended on the device. Voice mail traffic from Async 2 from the previous VG248 device in the chain queues up while this device is suspended. Suspending the device does not affect whether ports are enabled or not; if they were enabled before being suspended, they are enabled after being resumed.

Before You Begin

If after following this procedure, the device is not suspended immediately, it is likely that some of the ports still have active calls or there are pending MWI commands on the Cisco CallManager system. You can check individual ports by pressing Esc to exit the "Suspending..." message and choosing Display > Port Status from the main menu.

Procedure

To suspend voice mail activity, follow these steps:


Step 1 From the main menu, choose Configure.

Step 2 Choose Suspend.

A message appears indicating that the device is being suspended.

Step 3 Shut down, restart, or upgrade software on the VG248, as needed. See "Upgrading or Restoring Software Images" section for details.

Step 4 If you are removing a VG248 device from the voice mail chain, you might need to change the voice mail cabling also.

Step 5 To resume activity, choose Configure > Resume.


Upgrading the Main Image

The main software image might need to be updated if a new release is available on CCO as a bug update or feature enhancement.


Caution When you send a new software image to the VG248 using FTP, the current image is automatically deleted. If the FTP transfer terminates before the new file is copied to the VG248, the VG248 might not be able to start up. See the "Resolving an Incomplete Upgrade" section to resolve this problem.

Before You Begin

If you are using the VG248 to integrate with analog voice mail systems, be sure to follow the instructions described in the "Suspending Voice Mail Port Activity" section before upgrading the software image on the VG248.

Procedure

To upgrade the main software image, perform these steps:


Step 1 Obtain a configuration file whose name is in the following format: vgc-main.<version>.tar, where <version> indicates the release number, such as 1-0-1.

Step 2 Connect to the VG248 using FTP.

Step 3 Send the configuration file to the VG248 using FTP.

Step 4 Restart the VG248 for the new image to take effect.

Step 5 From the main menu on the VG248, choose Display.

Step 6 Choose Version to verify the updated version has been installed.


Upgrading the Boot Loader

The boot loader is the initial startup image. You should not upgrade this image unless instructed to do so by a Cisco technical representative.


Caution Only upgrade the boot loader if you are instructed to do so by a Cisco technical representative. If you encounter difficulties during this upgrade, such as a loss of power, the VG248 might not be able to start up.

Procedure

To upgrade the boot loader image, perform these steps:


Step 1 Obtain a configuration file whose name is in the following format: vgc-load.<version>.bin, where <version> indicates the release number, such as 1-0-1.

Step 2 Connect to the VG248 using FTP.

Step 3 Send the configuration file to the VG248 using FTP.

You must use a destination name that begins with "boot:". For example:

put vgc-load.<version>.bin boot:loader

Caution If the VG248 loses power or experiences a failure at this step, the VG248 might not start up. If this occurs, contact a Cisco technical representative for assistance.

Step 4 After the FTP command has completed successfully, restart the VG248 for the changes to take effect.

Step 5 Once the VG248 has restarted, choose Display > Version to verify that the updated version has been installed.


Resolving an Incomplete Upgrade

If you initiated an upgrade to the main software image, but terminated it before the FTP transfer of the new image completed, the VG248 might not start up.

If this occurred, the next time the VG248 starts up, one of the following occurs:

The boot loader loads, but the VG248 waits indefinitely at the Pausing for FTP prompt.

The VG248 partially loads the main image, pauses, and then restarts.

To resolve either of these errors (while connected to the VG248 boot loader), use the console port to establish an FTP session and transfer the main image file again, following the steps in the "Upgrading the Main Image" section.

Restoring to Factory Defaults

Before You Begin

By default, the VG248 uses DHCP to obtain an IP address. If you have assigned a static IP address to the VG248, you are likely to lose network connectivity.

Procedure

Follow these steps to reset the settings on the VG248 to their default values:


Step 1 From the main menu choose, Diagnostics.

Step 2 Choose Restore to factory configuration.


Verifying Connectivity

Use these sections to verify that the VG248 can connect to the network and that the voice mail chain is properly connected:

Verifying Network Connectivity

Validating the SMDI Connection and Configuration

Verifying Network Connectivity

To verify that the VG248 is connected to and communicating with your network, you can attempt to ping another device on the network.

Procedure

Follow these steps to ping another device from the VG248:


Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Ping network host.

Step 3 Enter the IP address or host name of the device.

The VG248 makes an attempt to reach the device once every second.

Step 4 Press Esc to exit.


Validating the SMDI Connection and Configuration

If you are using the SMDI protocol, you can evaluate the status of the SMDI configuration and diagnose misconfiguration on the VG248 and other VG248 devices chained together. However, this diagnosis cannot detect problems in the configuration of Cisco CallManager, legacy PBX, or individual extension's voice mail box numbers.

This diagnosis can identify configuration inconsistencies, such as breaks in the MWI forwarding chain, incorrect wiring of Async 1 and Async 2 ports, and missing configuration items such as the Cisco CallManager MWI directory number strings.

Before You Begin

The diagnostic process requires messages to be sent over the serial links to both the analog voice mail system and any attached legacy PBX. Performing this diagnosis might temporarily interfere with the voice mail system's normal operation.

Procedure

Follow these steps to validate the SMDI configuration:


Step 1 From the main menu, choose Diagnostics.

Step 2 Choose Validate SMDI configuration.

A window displays with the results of the diagnosis, indicating any errors or warnings.


Displaying Status and Configuration Settings

Use these sections to obtain information about the current status and settings of the VG248 and its connections:

Displaying System Status

Displaying Network Statistics

Displaying Port Status

Displaying Detailed Port Status

Displaying Port Statistics

Displaying Current Configuration

Displaying Software Version

Monitoring the CPU Utilization

Displaying System Status

The system status provides an overview of the current network settings on the VG248. Use this procedure to quickly check your network settings and connectivity information.

Procedure

To display system status, perform these steps:


Step 1 From the main screen, choose Display.

Step 2 Choose System status.

The system status displays:

Up time

Real time clock

Serial number

Ethernet MAC address

IP address

Subnet mask

Default router

DNS server

TFTP server

Syslog server

Domain

Ethernet speed and duplex

Async 1

Async 2


Displaying Network Statistics

Use the network statistics to observe the network traffic and packet errors through the IP connection on the VG248.

Procedure

To display network statistics, perform these steps:


Step 1 From the main screen, choose Display.

Step 2 Choose Network statistics.

These statistics display:

Octets

Unicast packets

Nonunicast packets

Discarded packets



Tips Press the Tab key to reset the network statistics while viewing.


Displaying Port Status

The port status provides detailed information about each port on the VG248.

Procedure

To display port status, perform these steps:


Step 1 From the main screen, choose Display.

Step 2 Choose Port status.

Step 3 Use the information in Table 6-6 to interpret the port status.


Table 6-6 Port Status 

Status
Description
Handset Status

OnHook

Not currently in use.

OffHook

User has lifted the handset.

Ringing

Incoming call to this port.

OnCall

A call has been established and voice packets are moving across the network.

Link Status

Up

Link is in its normal operating state (for the voice mail virtual port only).

Down

Link is not up (either because the port is not enabled or because of a temporary failure).

Register

Port is registering with Cisco CallManager

<directory number>

Directory number for the port displays indicating that the port is up and available for use.

Unregister

Unregistering from Cisco CallManager. Displays if port is being disabled or reset.

PeerInUse

The port's directory number is in use by another phone that shares the directory number. The port is not available for use while a call is active on the other phone.

KeepCall

The Cisco CallManager link has gone down, but the call that was in progress is being maintained.


Displaying Detailed Port Status

Port status provides detailed statistics about the Cisco CallManager links.

Procedure

To display detailed port status, follow these steps:


Step 1 From the main screen, choose Display.

Step 2 Choose Port status.

Step 3 Use the arrow keys to select one of the ports and press Enter.

Step 4 Use the information in Table 6-7 to interpret the port status.


Table 6-7 Cisco CallManager Port Status 

Type
Description

CallManager link

Status of the connection to Cisco CallManager

TFTP server

Host name or IP address of the TFTP server

Device name

Device name of the port as it appears in Cisco CallManager

Directory number

Extension number assigned to the analog device connected to this port

Forwarded to

Directory number to which calls are being forwarded

Call state

Status of the port from a user's viewpoint.

Remote party

Directory name and number of caller

Remote address

IP address and port of caller

Codec in use

Codec being used by Cisco CallManager:

G.729A

G.711 mu-law

G.711 a-law.

MWI

Whether the message waiting indicator for this port is on or off

CallManager name

DNS name of the Cisco CallManager host

CallManager IP address

IP address of Cisco CallManager

CallManager state

Status of connection to Cisco CallManager:

Active—connected to this Cisco CallManager and using this connection for SCCP communication.

Connecting—in the process of connecting to this Cisco CallManager

Idle—this Cisco CallManager is not being used

Standby—connected to this Cisco CallManager but not currently using the connection. Can use connection if active connection fails.

Pending—attempting to make this Cisco CallManager the active connection as soon as possible.

CallManager type

Type of Cisco CallManager system:

Normal—typical Cisco CallManager system

Failover—Cisco CallManager system reserved for failover situations


Displaying Port Statistics

Port statistics provide detailed information about the current or most recent call.

Procedure

To display the port statistics, follow these steps:


Step 1 From the main screen, choose Display.

Step 2 Choose Port status.

Step 3 Use the arrow keys to select one of the ports and press Enter.

Step 4 Press the Spacebar on the keyboard.

These statistics display for the current call, or last call if no call is active:

Tx packets

Rx packets

Call time

Rx bad sequence

Rx bad headers

Rx packets late

Rx packets early

These statistics display for the call history:

Incoming calls

Outgoing calls

Connected calls

These MWI statistics display for Cisco CallManager and Async 2:

Completed

Failed

Retries

Queued

Discarded

These Error responses statistics display:

Received

Forwarded

Discarded

These voice mail packet statistics display:

Async 1—Received, Transmitted, and Discarded

Async 2—Received, Transmitted, and discarded


Displaying Current Configuration

You can display the configuration of the VG248 device and its ports to quickly see what settings are enabled.

Displaying VG248 Device Configuration

Using the web-based interface, you can see the current configuration settings for the network, voice mail, and telephony features.

Before You Begin

You can also display the current configuration by choosing Diagnostics > Show configuration from the main VG248 command interface.

Procedure

Follow these steps to display these device-level configuration:


Step 1 Open the VG248 web interface. (See the "Monitoring System Status Remotely" section for details.

Step 2 Click one of the following options and refer to the noted sections for assistance interpreting the information.

Network and System—See the "Displaying System Status" section and the "Configuring Network Settings" section.

Telephony—See "Configuring the Telephony Settings on the VG248."

Voice Mail—See "Configuring Voice Mail Settings."


Displaying Port Configuration

Using the web-based interface, you can see the specific configuration for each port. Ports used for voice mail integration display voice mail specific configuration details, and ports used for analog devices display telephony specific configuration details.

Keep in mind that the voice mail settings are applied at the device level. Therefore, no port-specific voice mail information displays. However, many telephony features are applied on a per port basis. Therefore, you can obtain information about these settings as well.

Procedure

To display the port configuration, follow these steps:


Step 1 Open the VG248 web interface. (See the "Monitoring System Status Remotely" section for details.

Step 2 Click a phone icon to display the configuration for the port.

Step 3 Refer to these sections for assistance interpreting this information:

Voice mail ports display this information:

CallManager status—See "Configuring the Telephony Settings on the VG248."

CallManager list—See the "Displaying Detailed Port Status" section for details.

Voice mail statistics—See the "Displaying Port Statistics" section.

Voice mail configuration—See "Configuring Voice Mail Settings."

Analog ports display this information:

CallManager status—See "Configuring the Telephony Settings on the VG248."

CallManager list—See the "Displaying Detailed Port Status" section for details.

Call statistics—See the "Displaying Detailed Port Status" section for details.

Port configuration—See the "Configuring Port Parameters" section for details.


Displaying Software Version

To display the current software version you are using on the VG248, perform these steps:

Procedure


Step 1 From the main screen, choose Display.

Step 2 Choose Version.


Monitoring the CPU Utilization

You can monitor the processor usage to determine how much is being dedicated to particular tasks. For example, if the VG248 appeared to be running slowly, you could use this diagnostic to determine the culprit.

Procedure

To monitor the CPU utilization, follow these steps:


Step 1 From the main menu choose, Diagnostics.

Step 2 Choose CPU utilization.

Different subsystems appear noting the percentage in use.


Monitoring System Status Remotely

The VG248 includes a web server so you can monitor system status remotely using a web browser application. These options are similar to those accessible via the main VG248 interface, but you cannot change settings from the web interface.

Procedure

Follow these steps to monitor the system status remotely:


Step 1 From a web browser window, enter the IP address or host name of the VG248.

Step 2 If prompted for a password, enter the login password you have assigned. See the "Configuring the Login Password" section for details.

The web interface for the VG248 appears.

Step 3 Click a phone icon to display status for the port. See these sections for information about interpreting this information:

Displaying Port Status

Displaying Detailed Port Status

Displaying Port Statistics

Step 4 See Table 6-8 for information about the other available options.


Table 6-8 VG248 Web Interface Options 

Field
For More Information
Configuration/Status

Network and System

See the "Displaying System Status" section and the "Configuring Network Settings" section.

Telephony

See "Configuring the Telephony Settings on the VG248." and "Displaying Port Configuration" section for details.

Voice Mail

See "Configuring Voice Mail Settings."

SNMP

See "Configuring SNMP Settings" section.

Port Status

"Displaying Port Status" section and the "Displaying Detailed Port Status" section for details.

Statistics

Network

See the "Displaying Network Statistics" section

Voice Mail

See the "Displaying Port Statistics" section.

Version Information

See the "Displaying Software Version" section.

Environment

See the "Monitoring Internal Operating Temperature" section.

Event Log

See the "Working with the Event Log" section.


Working with the Event Log

The event log enables you to capture errors, warnings, and other informational messages from the VG248. Typically, you use these options only when troubleshooting a complex issue, perhaps while working with a Cisco technical representative.

However, using the default settings and these options, you can resolve many errors on your own:

Identifying a Syslog Server

Selecting Logging Levels and Logged Ports

Displaying Recent Messages

Understanding Sub-Systems on the VG248

Resolving Incorrect Date and Time in Event Log

Identifying a Syslog Server

You can identify up to five syslog servers to automatically capture and receive event logs for remote network management.

Enabling Syslog

You assign syslog servers to the VG248 using DHCP or by identifying specific syslog servers.

Procedure

To enable syslog, follow these steps:


Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Event log.

Step 3 Choose Syslog.

Step 4 Choose from the following options:

inactive—syslog disabled

use server from DHCP—syslog server determined by DHCP

use specified server—each syslog server must be specified (see the"Identifying a Specific Syslog Server" section)


Identifying a Specific Syslog Server

If you want to use a specific syslog server, you must enter its IP address by performing these steps:

Procedure


Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Event log.

Step 3 Choose Syslog server.

Step 4 Enter the IP address or host name of the network management system you want to designate as the syslog server.

Enter up to five servers by separating the IP addresses or host names with a comma or semicolon.


Selecting Logging Levels and Logged Ports

You can set the VG248 to log progressively more detail (information, errors, or warnings), or you can restrict logging to specific ports.

Typically, you should configure these options only when working with a Cisco technical representative because the nature of the problem determines the amount of information required to resolve it.

Procedure

To set logging levels or select ports, perform these steps:


Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Event log.

Step 3 Choose Set logging levels or Set logged ports.

Step 4 Work with a Cisco technical representative to determine the best options to select and enter.


Displaying Recent Messages

You can obtain a list of recent messages from the VG248 to help you resolve some configuration issues.

Procedure

To display recent messages, perform these steps:


Step 1 From the main screen, choose Diagnostics.

Step 2 Choose Event log.

Step 3 Choose View recent to display recent messages.

Step 4 See "Understanding Sub-Systems on the VG248" section for information on resolving these errors.


Tips You can also select View all to display all errors, or View new to display new errors only.



Understanding Sub-Systems on the VG248

The VG248 generates informational and warning messages and errors from different sub-systems in its software. Many of these messages do not require any intervention on your part; the device simply notifies you of changes or updates. Other errors and warnings require additional troubleshooting or configuration.

Table 6-9 provides an overview of the different sub-systems on the VG248 that might generate informational or warning messages.

Table 6-9 VG248 Sub-Systems 

System
Description

DHCP

Communicates with DHCP server.

Ethernet

Concerned with low-level network link integrity.

OS

Runs the low-level services of the VG248.

FTP

Used to send new software images to the VG248.

DNS

Resolves host names to IP addresses.

TFTP

Handles retrieval of Cisco CallManager port configuration.

SLIC

Detects events from analog handsets.

DSP

Provides digital signal processing.

POTS

Bridges between analog and IP telephony.

SCCP

Transmits and receives telephony events over the IP network; communicates with Cisco CallManager.

SNMP

Coordinates SNMP communication.

VM

Provides voice mail communication.


Resolving Incorrect Date and Time in Event Log

The VG248 has a built-in real time clock that synchronizes itself periodically with Cisco CallManager to obtain the correct date and time. To ensure that the date is synchronized properly, the VG248 must have at least one port enabled and registered with Cisco CallManager. See the "Enabling a Specific Port" section for assistance on enabling and registering ports in Cisco CallManager.