I have CME,CUE installed.CME having 60 extensions ..but cue is having only 25 voice mail license..Its working fine.Now i tried to enable autoattendant..its working but because of 25 user liccense for unity ..when caller tries to extensions other than this 25 numbers(voice mail licenced) which configured in cme(its around 60 extension)..it will not happen.
because we need to add users and their extensions in unity for transfering through autoattendant.Because i have only 25 voice mail user license i am not able to add all the users and extension what i have in CME...
Can u guide me ,is there any option to add users without mailbox in Unity..??
Maybe you are running into this CUE default, that allows transfers to Internal (associated to CUE Mailbox) users only. Have a look, it sounds like this problem could be rectified without adding 35 new licenses;
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).
It was very useful.I did it using enabling external transfer.But after that all the extension is reachable after autoattendant greeting.But i have two block 3 extension from reaching after greeting.is it determine by command transfer-pattern .. or system-transfer.. in CME config.
I have to ask about cusomising my greeting using AVT.I have seen that i can access through a number and i can do it.
But i did not get any link to how to enable or configure it(AVT)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...