TUI Session Interpretation

This topic describes how to troubleshoot TUI scripts and subscriber input.

  • Verify scripts and subscriber input:
    1. Use the trace voicemail vxml all command for TUI session debugging.
    2. Displays received DTMF and the prompt played in response to it.
  • Use caller ID for differentiating calls to voicemail:
    1. Displays voicemail TUI position.
    2. Shows various levels of prompts and menus within the TUI.

Verify the scripts and subscriber input. The script that is named voicebrowser.aef provides the functionality of the Cisco Unity Express voicemail application. This script uses VXML to implement its functionality. These functions can be viewed by using the trace voicemail vxml all command, which provides the following information:

  • Displays received DTMF and prompts that are played in response to them
  • Uses caller ID for differentiating different calls into voicemail
  • Displays voicemail TUI position
  • Various levels of prompts and menus within the TUI

The caller ID of a user that calls in to voicemail is checked. If there is a mailbox that is associated with that phone number, the user is prompted for the PIN. If there is no matching mailbox, the user is prompted to enter the extension with which the mailbox is associated.

To view a call arriving in voicemail and a message being left for a subscriber in the form of trace command output, enter the trace voicemail vxml all command. The output can include the prompts that are played and any corresponding WAV files that are mapped to those prompts. The input of the caller can also be displayed in the output of the trace command.

Advertisements

Author: drbabbers

ccieme.wordpress.com - my personal journey to ccie