The short answer is it depends on how youre going to be using the system. If youre using it for auto attendant purposes (i.e. the Unity box is answering all incoming calls instead of a human) youre going to need higher port sizes to accommodate that, of course. If youre dealing with a DID environment where calls are forwarded to Unity on busy/RNA conditions and use of audio text is fairly light, your port limits can be lower. If your users are primarily using their desktops to get/send voice mail, you ports can go even lighter.
The old rule of thumb for a voice mail only environment was 25 users per port (which Im sure some folks out here would argue one way or the other I suspect). If it was a heavy audio text application youd bump that down a bit. For a primarily desktop messaging environment (say 2/3 of your folks are getting/sending most of their messages from the desktop) Id say that could be about doubled to around 50 users per port or more.
In most cases Id say 2000 users can be handled by 48 ports of voice if youre in a DID setting. Of course if theyre using paging and telephone notification heavily or theres other special considerations, youre going to have to take that into account. Port sizing a system is more of an art than a science theres no hard and fast formula I can give you that will work for all sites. Some dealers will come back to a site after its been in use for a month or so and run port usage reports to see if more ports are necessary based on how the site is using the system (for whatever reason it never seems to result in FEWER ports I dont know why that would be ;->). This is not a bad strategy to take
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...