We have a group of user ext 5101 to 5109 who want to forward there extensions to a seperate number with a closed greeting voicemail account (ext 5118)
The users want to be able to forward there lines at anytime of the day to this ext 5118 and to be able to update the Closed Greeting as and when it needs be
Obviously when they forward there lines to 5118 the voicemail the caller receives is the orginating number dialled voicemail and not the forwarded option greeting(5118).
We only want this to be avaliable to the specific extension numbers in the range 5101/5109
I configured this for a start :
- Call Routing
- Fowarded Calls:
forwarding stations : (XXXXXXXXX510*) to include the range of users
Send call to : Subscriber : 5118
Conversation : send greeting for
What that did was to send all calls on XXXXXXXXXX510* range to the 5118 closed greeting, but what I am after is to send only the CUCM forwarded calls to the closed greeting ext 5118 and when the forward option is removed back to the users own voicemail
Set up a Call Handler with an extension these users can forward to. Assign the extension directly to the Call Handler - not in routing rules.
Configure the Call Handler with a blank greeting and then after greeting - transfer to a Subscriber's greeting.
Create a new Subscriber that will be used for taking messages for these folks. Since this is as ad-hoc forwarding of calls, you don't need to use the Closed greeting specifically. You can just set a schedule of All Hours All Days and use the standard greeting. Assign this Subscriber a new extension and then make each of your user's extension an alternate extension for this Subscriber. The caveat here is that everyone will receive MWI even if only one user is forwarded to this Subscriber. If the intent is to not actually allow users to leave a message when a phone is forwarded then you could just do this:
Create the Call Handler. Record the standard greeting with whatever this group wants to say. Then the after greeting action can be configured to Hang Up. No alternate extensions, additional subscriber configuration, or MWI issues to consider.
Call Information Exchanged by the Phone System and Cisco Unity
The phone system and Cisco Unity exchange call information to manage calls and to make the integration features possible. With each call, the following call information is typically passed between the phone system and Cisco Unity:
The extension of the called party.
The extension of the calling party (for internal calls) or the phone number of the calling party (if it is an external call and the phone system supports caller ID).
The reason for the forward (the extension is busy, does not answer, or is set to forward all calls). There is also a reason code for Direct Calls.
Cisco Unified Communications Manager SCCP and SIP trunk integrations can also provide the following call information (the choice of first and last redirecting number is set in the Advanced Settings Tool, which is available in Tools Depot):
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...