[cisco-voip] Location design and intent in CallManager 4.x

[Jonathan Charles]

I have issues with the word 'monitor' here...

CallManager does not pay attention (much) to the call while it is up
and connected... however, it does collect performance data
afterwards...

The locations-based bandwidth is released when the phones disconnect
and tell CCM that they have done so.

Remember, Cisco IP Phones are very very very stupid.... they don't
even know when to make dial tone (if you look at SCCP traces, you can
see the phone go off hook (and tell CCM) and then watch CCM tell the
phone, 'hey, dumbass, play dial tone...'

So, CCM is involved at the call clearing stage.


Now, to the root of your question, Locations-based bandwidth is
poor-man's CAC for people who don't have a gatekeeper. It basically
does exactly what you suggested, it knows about all calls between each
location and deducts bandwidth from the locations listed total, when a
call clears, it returns that bandwidth to the pool.

It is very easy to implement, but you need to make sure you place
every phone in its specific location.



Jonathan

On Dec 18, 2007 9:23 AM, Leetun, Rob <rleetun at co.boulder.co.us> wrote:
>
>
>
> Greetings,
>
> When a CallManager setups a call between two endpoints, which both parties
> pick up the phone, then the CallManager sort of gets out of the way…does the
> CallManager monitor available bandwidth between two endpoints, does it keep
> a ledger of available bandwidth based on the number of calls based on a
> location of two endpoints, and how does it determine if there is not enough
> bandwidth available between two locations?
>
> What is the design intent of location other than dictionary or Wikipedia
> explanation?
>
> Thanks.
>
> Rob
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>