CUE redirect to number

Unanswered Question
Mar 16th, 2009

Our customer has Call manager 5.1 and Unity express 2.3.

Incoming calls to FXO lines (mgcp) need to have direct access to internal directory numbers(3 digits).

I have added an auto attendant that after the greeting message gets a string and redirects the call. But it seems that only numbers registered to users on CUE are accepted as valid.

Is there a way to redirect to any 3 digit numbers? (no user-DN registration on CUE)


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
rob.huffman Mon, 03/16/2009 - 06:10

Hi Viron,

Maybe you are running into this CUE default (which can be changed), that allows transfers to Internal (associated to CUE Mailbox) users only. Have a look;

Internal and External Destinations

Up to Cisco Unity Express 2.0, the system AA allowed for the transfer calls to any destination,it treated the destination merely as a string of digits, and any call dialable on the associated call agent would succeed. To limit the destinations to which the AA can transfer calls (such as no calls to the PSTN), the call agent's features,such as Class of Restriction (COR) on Cisco CME were required.

**As of Cisco Unity Express Release 2.1, the system AA has a parameter to control whether calls are allowed to transfer only to internal numbers (default operation), or to internal and external numbers. Your own custom AA scripts can employ similar mechanisms to limit the valid destinations of calls.*** The system AA script parameter is ***(the value of the allowExternalTransfers parameter).

An internal number is considered to be an extension that exists in Cisco Unity Express's LDAP directory. Information that appears in LDAP includes all extensions defined and associated with a user (Configure > Users) on Cisco Unity Express. This does not include remote user (Configure > Remote Users) definitions entered on Cisco Unity Express for networking spoken name confirmation (these are not stored in LDAP). The validity of a destination number is independent of extension length or dialing plans and is not coordinated with your call agent's dial plan on what might be local extensions versus remote extensions.

Cisco Unity Express considers an extension that appears in an LDAP entry an internal destination. External destinations include everything else, such as the following:

All other extensions that exist at the local site, but do not appear in the Cisco Unity Express configuration, such as local phones/extensions that do not have mailboxes.

All VoIP destinations, such as extensions present at other sites, but a PSTN call is not required to reach them.

All PSTN destinations.

If you want to refine the destinations that the Cisco Unity Express AA can transfer calls to, you have to limit calls either on the call agent (with features such as COR), or write a custom Cisco Unity Express AA script that does the checking based on your requirements (such as perhaps extension length, or numbers starting with certain sequences such as 9).

From this good AA Design doc;

I think you can also use theis capability :)

There might be employees in your office who do not need a voice mailbox, but require the ability to be reached using the dial-by-name feature via the Cisco Unity Express AA. If so, these employees can be entered in the Cisco Unity Express system (as users) without having mailboxes assigned to them. By virtue of the Cisco Unity Express user definition (and associated extension and phone), these employees appear in the Cisco Unity Express LDAP database and therefore are recognized by the Dial-by-Name AA function.

These users do not have a mailbox defined, and therefore do not count against the Cisco Unity Express license (the license counts mailboxes, not users).

Hope this helps!



This Discussion