AAR and Cisco Unified SRST Issues

This topic describes voice messaging issues together with WAN backup technologies.

WAN backup technologies are in use; the wrong greeting is played:

  • Happens if AAR or Cisco Unified SRST is used in these situations:
    1. Calling to Cisco Unity Connection.
    2. Calls are forwarded to Cisco Unity Connection.
  • In AAR and Cisco Unified SRST mode, the calling number is sent as the complete phone number.
    1. For example, 408 555 1000 instead of 1000.
    2. Solution: Add alternate extensions.
  • AAR-forwarded calls to headquarters are not working.
    1. The gateway AAR CSS is missing.

When AAR and Cisco Unified SRST are used, calls are routed over the PSTN instead of being routed over the WAN. Four-digit numbers are no longer used because the PSTN expects the complete phone number or at least the subscriber number, depending on the PSTN provider.

For example, when a user presses the Messages button, the calling number is recognized as 408 555-1000 instead of 1000, which is the configured extension in Cisco Unity Connection. The user ID does not match, so the standard Opening Greeting is played. The solution is to configure alternate extensions that contain the complete phone number.

During a Call Forward, AAR might be unsuccessful. This issue happens if no AAR CSS is configured on the outgoing branch gateway. That is, the gateway has no access rights to place PSTN calls. Set the AAR CSS to a value that contains a partition with route patterns to the PSTN.

Backup technologies are in use; the wrong greeting is played:

  • Redirected calls in AAR or Cisco Unified SRST mode receive the standard opening greeting.
  • Verify that these check boxes are checked.
  • In addition, verify the interface serial configuration on the originating gateway.
interface Serial0/0/0:23
isdn outgoing ie redirecting-number
  • If the isdn outgoing display-ie command is missing, no redirected number is transmitted at the outgoing gateway.

The cause of a redirected number not being sent can be missing configuration parameters in various places.

When troubleshooting, start with the outgoing gateway. Use the debug isdn q931 command to determine which information the originating gateway sends.

        Calling Party Number i = 0x0081, '442288224001'
                Plan:ISDN, Type:International
        Called Party Number i = 0xA1, '12012012100'
                Plan:ISDN, Type:National
        Redirecting Number i = 0x000081, '4002'
                Plan:Unknown, Type:Unknown

If the redirected number is not shown at the originating gateway, verify that the router is configured to pass the information:

interface Serial0/0/0:23
isdn outgoing ie redirecting-number

For AAR calls, verify that the Redirecting Number IE Delivery—Outbound parameter is set on Cisco Unified Communications Manager in the gateway configuration.

If the originating gateway sends the redirecting number, then use the debug isdn q931 command at the terminating gateway to verify that the redirected number is received. Typically, the PSTN provider does not strip redirected numbers.

If the redirected number is shown on the terminating gateway, then the Redirecting Number IE Delivery—Inbound parameter is not set for the gateway in Cisco Unified Communications Manager.

To correct the issues, check the Display IE Delivery, Redirecting Number IE Delivery—Outbound, and Redirecting Number IE Delivery—Inbound parameters. The Display IE Delivery configuration is necessary only if calls to the PSTN must send the complete phone number and the calling name. The Redirecting Number IE Delivery parameters are required for voicemail integration.


Author: drbabbers

ccieme.wordpress.com - my personal journey to ccie