This is a good question and has been bothering me too. Is there a good source of information on the exact, detailed call flow for calls to/from UCX for message retrieval/call forwarding to leave messages/mwi on-off calls, including the precise partitions and CSS's used each step of the way? I have looked pretty rigorously, and haven't been able to find anything. Every time I see this explained it seems a little bit different. Similarly, are there any books available/in the pipeline for UCX now that it is an important topic for the CCIE Voice test?
Here are some of my questions, based on the doc referenced in this thread for integrating CUCM/UCX. I don't have access to a CUCM/UCX integration to test right now. I have gotten integrations working in the past pretty easily, but I think I am missing a subtle but important piece of "how things work" so any assistance would be appreciated.
(I don't mean to hijack this thread, so let me know if I should move it so this one can be closed, if appropriate).
Regarding Yao's question, from the document it says:
To Add a Voice Mail Pilot Number for the Voice Mail Ports
CSS; "Click the calling search space that includes partitions containing the user phones and the partition you set up for the voice mail pilot number"
I understand the need for the partition with the VM Pilot Number (which is really the partition of the Hunt Pilot number as mentioned below, and which provides the protection noted in the response), but why does the VM Pilot Number CSS need to contain partitions for the user phones? When would the VM Pilot number need to place a call a "user" phone? Doesn't it only point to the Hunt Pilot, ever?
Some other questions:
1) To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports
Relatively minor nit, here.
When they say "For example, enter "VMPilotNumberPT, Partition for the voice mail pilot number" really it is for the partitition for the Hunt Pilot that the VM Pilot points to, since the VMPilot Number itself does not have a partition field. Just confusing wording since the Hunt Pilot and VM Pilot are the same number, I think. This is actually important when we put the partition with the Hunt Pilot into the CSS of the phone.
2) Regarding the CSS at both the VM Port (Device) and VM Port DN (Line) level, are there any best practices for designing these, particularly with regard to integrating with the overall dialplan design approaches for class of service (Traditional vs Line/Device). Or are they completely orthogonal?
Voice Mail Device Information Page
VM Port CSS
"This calling search space must include partitions that contain all devices Cisco Unity Connection needs to access (for example, during call transfers, message notifications, and MWI activations). "
Makes sense. But just to clarify, the transfers they refer to in this context are not for calls to the Auto Attendant on UCX, which would use the CTI Route Point and associated DN CSS's. The transfers mentioned here would be for things like caller input actions of "transfer to alternate extension number" during a caller greeting. So even ports configured as "Answering Ports" might be placing outbound calls for things like transfer and therefore need a CSS. Is this correct?
Table 6-3 Settings for the Cisco Voice Mail Directory Numbers Page
CSS: "Click the name of a calling search space that you set up to contain the partition with all voice mail port directory numbers"
Why do the voice mail port DN CSS's point to the other VM Port DN's? Doesn't the Hunt List Line Group config cover the hunting functionality? What is this used for?
In terms of the Line/Device question above, it appears that the best practice is:
Dev CSS = communicate with UCM
Line CSS = point to other VM Port DNs, something to do with hunting?
Another minor nit.
Internal Caller ID Display:
"This text appears on the phone when the pilot number is dialed. "
Doesn't the description apply to the Alerting Name? Would the Internal CLID be used to appear on the phone for something like a transfer from a caller's greeting?
5) Table 6-8 and 6-9 MWI DN's
a) Why are they put in the same partition as the VMPilot, which is included in the Phone CSS? Doesn't this give the phone the ability to call the mwi on/off numbers directly, which I believe is not desired?
b) What are the MWI DN CSS's used for? I have always thought they were used in kind of a two-step process, where CUCM receives the inbound call say to the mwi on number, and then uses the MWI on number css to place the call to the phone to activate the light, so the DN of the phone must be in the CSS of the MWI DN, as they state here. Is this correct? What confuses me is that the voice port already has the partitions with the phone DN's in its CSS, so that is what leads me to think it is a two-step process. Am I even close on this one?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...