This topic describes how to follow a voicemail call logically through the system.
- Verify Cisco Unified Communications Manager Express and the phone configuration.
- Troubleshoot the sequence from call or call forward through to voicemail dial peer.
debugcommands for troubleshooting.
dial-peer voice 4500 voip description voicemail CUE destination-pattern 45.. session protocol sipv2 session target ipv4:10.1.130.2 dtmf-relay sip-notify codec g711ulaw no vad
telephony-service voicemail 4500 ephone-dn 1 number 4001 call-forward noan 4500 timeout 10
Verify the Cisco Unified Communications Manager Express configuration and the phone setup. The troubleshooting sequence could begin from the ephone-dn call-forwarding configuration and go to the voicemail dial peer, or a direct call where the user presses the Messages button on the phone.
Troubleshooting can be simplified by following the voicemail sequence of events and the associated Cisco Unified Communications Manager Express configuration. For example, calls are forwarded from an individual phone to the voicemail extension. The voicemail extension is defined as a destination pattern in the voicemail dial peer, which specifies the Cisco Unity Express IP address as the session target.
The most likely reasons for a reorder tone are the following:
- Cisco Unity Express is not set up and initialized.
- The trigger number for the voicemail application is not set or is incorrect.
- No ports are available for the voicemail application.
- The wrong codec is used, or transcoders are not working properly.
show commands to verify the Cisco Unified Communications Manager Express configuration and operation:
The Cisco Unified Communications Manager Express
debug commands can be turned on and off independently for specific modules. Each module has several options that can be turned on individually. For example, the
debug voip module has many options, including the
By default, the debug output is sent to the Cisco Unified Communications Manager Express router console. No debug output will be displayed if the administrator uses Telnet or SSH to access the router. Use the
terminal monitor command to direct debug output to Telnet or SSH. Debug settings return to their default settings if the router reboots. By default, all debugging options are off.
The following are some useful
debug commands for troubleshooting voicemail integration issues in Cisco Unified Communications Manager Express:
debug ephonecommand is useful for troubleshooting IP phones.
debug voicecommand is useful for troubleshooting voice problems.
debug voipcommand is useful for troubleshooting VoIP.
To debug the voice call control API, use the
debug voip ccapi privileged EXEC command. To trace the execution path through the call control API, use the
debug voip ccapi inout command. The call control API serves as the interface between the call session application and the underlying network-specific software. This command shows how a call flows through the system.
debug ccsip command to troubleshoot problems with SIP. The
calls option traces the SIP call details as they are updated in the SIP call control block. The
all option displays all SIP-related debug information. Use the
messages option to view SIP messages.