Call Admission Control 10/11X

[mzajeski]

Real confused on why location based CAC changed and need some help.

I have locations in Lansing, Downers Grove, Phoenix, Springfield, and Denver.  We have Telepresence units in all locations as well as Jabber-enabled video.  I want to limit video bandwidth in/out of Lansing to 6MB on our TP units and 2MB tops for all other video.  Do I create Location links between Lansing-Downers Grove, Lansing-Phoenix, Lansing-Springfield, and Lansing-Denver and set each limit to 6MB???  I'm curious about the audio settings on Locations as well.  Any help appreciated.

[Jaime Valencia]

I suggest you review the SRND which explains CSC, for audio, video and TP calls and how they map to the settings in CUCM, as well as how to manage the locations.

[mzajeski]

Took your suggestion and reviewed the SRND.  It really doesn't make any sense on why they changed CAC from a single location with values to basically "links."  If I want a site, Lansing, for example, to have a maximum of 6MB Immersive Video (In/Out), how can I have CallManager provide CAC on that?  Do I set 6MB as the CAC value for each link between Lansing and other sites???  The old CAC would keep tabs of all voice/video entering/leaving a location and control it based upon a value.  Do you get my point?

[Jaime Valencia]

Yeah, I get your point, but before you were tied to a hub and spoke topology, this new method provides you with a real method to deduct BW if your topology is linear for example, like A - B - C - D, now you can define how the sites are really connected, and deduct the BW as it traverses from A to D, plus, now you differentiate TP calls, from regular video calls, and audio calls.

It's a bit harder to configure, but a lot more flexible.

[mzajeski]

I totally disagree on being more flexible or even usable at all for Multisite offices.

Lansing has (4) Telepresence units and calls can sometimes be made between Lansing and any of the branch offices.  I need CAC to limit the total bandwidth used for Lansing to 6MB.  I see no way that this can be done with the new solution.  Am I missing something?  I was one of the first engineers to implement RSVP with CAC and discovered (with Cisco) the gotcha's to that...