1. BHCC stands for Busy Hour Call Completions and is a measurement of PBX call processing power.
2. 96 ports on an AS5300 would count as 96 H.323 'devices'. This by the way, is effectively 288 consumed units of the Media Convergence Server (MCS).
3-4. Many H.323 gateways should be interoperable with CallManager but double-check yours with your Cisco design engineer. Check with them on your Alternate Automatic Routing design too. I understand Ciscos TAC only supports non-Cisco H.323 gateways after interoperability and performance tests have been performed. Unless you have an existing gateway in place, go end-to-end Cisco. It could save you a lot of headaches.
5. For information on Call Admission Control, look here
Thanks for the pointer! I got couple more questions based on your answer. Hope you don't mind helping me out here.
1. You mentioned 288 consumed units of MCS. How did this come about?
2. So based on CCM's datasheet, one MCS can roughly handles 26 AS5300 (with 96 port each)?
3. Is there anywhere I can get more information about BHCC and how it will effect MCS's performance?
4. My concern about Call Admission Control, is basicly, that authorized gateway, ip phone, etc can connect to our network and terminating gateway. Does CCM do that or do I need a seperate gatekeeper for it?
On point 1 288 is derived beacuse each port has device weight of 3 in the call manager. Depending upon the MCS server you have you will have a maximum loading that the CM can take, the higher the spec MCS the better. For example the Softphone has a weight of 30 so you could not have 2500 soft phones registered with a single CM.
Point 2; Again it would depend upon the MCS being used. If a single AS5300 with 96 ports has a device weight of 288, you couldn't have 26 AS5300 registered on one MCS as this would give a load of 7488. Note even the MCS7835 can have this, I think the max device count for a 7835 is 5000. The max count is derived from all phones, gateways, conferences, uone ports etc connected to the CM
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.