OK - specifically, the bug I was referring to is related to SIP integrations. The bug is one in which the SIP
protocol for integration works incorrectly and the ports get "stuck" - essentially, CUC ports stay in a connected state even after they have disconnected from a call to CUCM. If you are using SIP, this could be your issue. If not, and you are using SCCP then it would not be related to your situation.
As for your ports - it sounds as if you may have misconfigured the ports for the cluster. CUC is designed to provide 100% failover between each server so if you have 10 ports then you should have then split equally between servers. In other words, 5 on each server. 10 is actually an odd port count. I suspect you would be licensed for 16 ports - in which case, you are not using all of your ports. But, I don't know the specifics of your installation. So, for ports - we'll say you have 10 ports. You would want to take about 25% of those ports and reserve them for message notification, MWI, and TRAP (if your users access Cisco PCA and change their greetings via the Media Master web interface - if they don't, it doesn't hurt to leave this open). So, in your case 25% of 10 is 2.5 so I'd say you would set up 2 ports for MWI. In CUC, what you would do is configure a Phone System then a Port Group and then configure the ports in this manner. Add the Subscriber ports first like so: Add 4 ports that are set to "Answer Calls" only (all other functions unchecked). Then add 1 port that has "Message Notification", "MWI", and "TRAP" enabled but "Answer Calls" is unchecked. This port will be reserved for primarily MWI usage. Then add the Publisher ports in the same manner. 4 ports to answer calls. 1 port for MWI. In total, you'd have 8 voicemail ports that answer calls and 2 that perform MWI function. On the CUCM side, you would configure the Subscriber ports first using the VM Port Wizard and then do the same for the Publisher ports. Then you want 2 Line Groups - ex: CUC-Sub_LG and this would only contain the 1st 4 ports which are configured in CUC to answer calls. Do the same for the Publisher - ex: CUC-Pub_LG and it would contain only the 1st 4 ports that are configured to answer calls. In the associated Hunt List, the Sub LG should be priority and the Pub LG in secondary position.
In the model described above, one port = 1 port that can answer calls OR 1 port that does not answer calls but can dial out to CUCM for MWI (at the most basic level).
Temp solution depends for you. If you are using SIP, you have to upgrade to fix the issue. If you are using SCCP, I would suggest you configure your ports as described above as improper port allocation/configuration on CUC can cause VM to malfunction.
What is a good document to read? Read the CUCM 7x SRND, Cisco Unity Connection Design Guide, Cisco Unity Administration Guide, Cisco Unity Installation Guide, and the supplement on Supported VM Integrations for CUC and CUCM - it will describe how to configure both SCCP or SIP integrations as described above.
Hailey
Please rate helpful posts!
