Multiple Zones with a Single Gatekeeper
Headquarters
Campus
No Local
Gatekeeper
Zone Seattle
Zone Denver Zone Chicago
For example, assume the Denver zone has a significant amount of time-sensitive
traffic other than voice and video calls. For this zone, you would probably
want to limit the voice and video calls to only 512 Kbps or 768 Kbps to leave
sufficient bandwidth for the other time-sensitive applications. However, assume
the Chicago zone does not have a significant amount of time-sensitive traffic. For
this zone, you would probably want to allow the voice and video calls to consume
much more bandwidth, such as 1024 Kbps or 1280 Kbps. Allowing more
calls would save costs (versus using the PSTN) but would still provide some
bandwidth for all other applications.This configuration for all three zones can be
placed in the Seattle gatekeeper.
As you can see in Figure 5.4, remote sites can have their own gatekeeper,
though they are not required to.