For Implementation of an IP telephony solution in a building. I want to support Voicemail, Videoconferencing and I need PSTN connectivity for 60 concurrent calls. At least 500 phones need to be supported. All users will require extension mobility.
60 concurrent calls on PSTN will require 3 PRI circuits. Your CallManager server cluster's set up not only depends on the number of phones you are trying to provision, but also the level of redundancy you are looking to support (which is often budget issue.) For voicemail, go with Unity but Unity supports a number of configurations like Unified Messaging or VMO. Do you need redundancy,? Again, these answers can be dictated by budget. Extension mobility is a typical feature supported in 4.x.
Do you need SRST? If so, this will dictate the model gateway that you will use to provision the PRI circuits. This link will explain;
No budget and redundancy would be good, also what router would i use? could you pls recommend a complete list of equipment that would fulfill the criteria and there is no budget. Many thanks in advance
If you are on a limited budget, you can replace the CCM cluster and Unity Server in Majdi's list with the new Unified Communications Manager Business Edition. It is a SMB all-in-one platform. There is no redundancy short of RAID drives.
Just to add a note to the good info you have received already from Shikamaru,Majdi and Scott. Be a little careful with the Cisco Unified Communications Manager Business Edition as it only scales to 500 phones/users and may not offer the room for growth that you desire;
Cisco Unified Communications Manager Business Edition is a designed for medium-sized businesses with up to 500 employees and up to five remote sites.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.