[cisco-voip] GK to GK and CUCM Gatekeeper controller trunk

[Matthew Saskin]

Location-based CAC and bandwidth-based CAC on gatekeepers are two separate
and distinct things without any interaction.

If you have (for example) 256k set in CUCM between two locations (each of
which represents a gatekeeper controlled trunk end) and 512kbps as the
bandwidth settings on the gatekeeper, you will hit the 256k limit in CUCM
first.  Reverse the scenario and at 256k the gatekeeper will stop you.

As for best practice, my .02c is that you want to keep your policies for
managing call admission control consistent.  Whether CUCM or Gatekeeper,
having a single management plane is usually preferable to having multiple
management planes.

Matthew Saskin
msaskin at gmail.com
203-253-9571

July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run
Please support the Leukemia & Lyphoma Society
http://pages.teamintraining.org/nyc/nyctri10/msaskin


On Wed, Apr 7, 2010 at 1:52 PM, Mark Marquez <MMarquez at goldsys.com> wrote:

>  I’ve done preliminary discovery on a customer’s GK to GK setup. They have
> two clusters and for some reason have GK to GK communication taking place
> between the two geographies.   I understand that GK’s have interzone and
> intrazone bandwidth settings.  I also see that CUCM GK controlled trunks can
> have CUCM Location settings.  It seems to me that best practice would be to
> have the CUCM GK controlled trunk Location settings set to Unlimited BW and
> allow the GK Interzone BW settings to take precedence.  Now if the CUCM GK
> controlled trunk has a Location setting how is that taken into account?  I
> assume it will take precedence over what BW the GK may allow?  Is that
> correct?  I can’t recall the relationship between Locations and GK settings
> and if there is any negotiation between CUCM Location settings and the GK BW
> settings.
>
>
>
>
>
> CUCM Cluster 1 <=*(GK Controlled Trunk (Location set to Unlimited BW))=>
>   *GK1   çè  GK2   <=*(GK Controlled Trunk (Location Setting restrictsBW))
> *=> CUCM Cluster 2
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100407/054fce7d/attachment.html>