We currently have a Unity 4.0.5 box with 32 ports. We've added about two hundred more subscribers to the box over the past year, almost maxing out our user licenses (we're about 60 shy of maxing out). As a result, port traffic has increased, and users have gotten busy signals (I've gotten all ports in use errors on Unity itself) and I would like to go up to 48 ports.
However, I'm not seeing any orderable part number for just 48; all I'm seeing is the part number to order the max of 72, which is overkill for our setup.
I did find this part number hidden on the Dynamic Configuration Tool: UNITY-4PORT
Has anyone tried to order this?...I'm just trying to get the right part number to our purchasing agent...
The following is from the Cisco Unity Ordering Guidelines page:
"For example, a customer with a 24-port Cisco Unity Version 3.1 system should order part number UNITY40-SL32-VERUP to move to a Cisco Unity Version 4.0 32-session server license. For systems with more than 32 ports, customers should order part number UNITY40-SLMAX-UP. Customers with fewer than 16 ports should order part number UNITY40-SL16-VERUP."
I've read the ordering guidlines sheet. The UNITY40-SLMAX-UP maxes us out at 72 ports. We don't need 72 ports, it's overkill (and it's awfully pricey). We just need 16 more, to get us up to 48, that's why I wondered if anyone had used the 4-port upgrade part number...
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...
[toc:faq]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 discusse...