I have read the CAC section of the SRND and I think I'm still confused on certain sections of the document. Would greatly appreciated anyone help on this :-)
Just assume RSVP is not a feasible option for now...
Re: Diagram 1
i) In this scenario, how many CCM clusters would you have & why? Would you put a cluster to each hub and remote site (i.e. to all sites)?
Ii) If each site has it's own cluster, how many GK would you use and why?
Re: Diagram 2
Iii) Assume it is a "Centralized model" where the HO hosts the only CCM cluster, do you see any problems in terms of CAC?
Iv) What would you configure for the location for the Non-GK controlled trunk between hub office (site D) & HO (site G)?
V) Do you ever configure any locations for the HO site? Or just leave the HO phones and HO Intercluster trunk as "none"?
Vi) Say if site A makes 7 calls to site B, and if site C also makes 8 calls to site B simultenously, can site B still call HO? I think the answer is no. Location CAC is not really designed to support multi-tier environment? anything we can do to fix this problem if the scenario has to be in Centralized model?
(N.B:- I have changed the location to be 'number of calls' rather than 'bandwidth' for simplicity)
Re: Diagram 3
Vi) In the centralized model,.If we have to reserve a certain bandwidth along all links end-to-end by RSVP, how is that differenet from using CAC? Don't we still need to over-pump the links? Say if a certain path along the RSVP path reserves 60 calls, wouldn't we need to RSVP for 60 calls through the whole path just like CAC?
Re: Diagram 4
Vii) For Tail End Hop off, assume all the voip dial peer has been setup on all the VGs, and the Route Pattern at Centralized CCM has been setup to point to the local VG (at site G) as Route List. But If the bandwidth between the hub (site D) & HO (site G) are all used up, but I want the user at site H to still be able to call the PSTN, can I use AAR in this scenario?
I would do independent clusters in this case. Two Callmanagers at each hub (having its own cluster). Remote sites can run SRST. For trunking between the two clusters, all you need is one Gatekeeper.
If RTT between the two Hubs is < 40 ms, you can put callmanagers at both hubs in the same cluster. In this case you dont need GK's. You can use Locations based CAC.
There is a single point of failure between HO and hub. You can use SRST or CME on all the remote sites hanging off the hub and also at the hub. If you use locations based CAC in this scenario, you may end up having problems because its not a true Hub and spoke topology.
I am a rookie when it comes to RSVP. So I would pass that on to somebody else.
Location bandwidth between hub and HO is independent of location bw between HO and site H. So AAR will not kick in.
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.