Local Gatekeeper Configuration

Basic configuration script for the local gatekeeper:

gatekeeper
 zone local gggg dddd <ethernet ip address>
 zone remote njedge_portal_GK njedge_portal_GK.net 130.156.34.2
 zone prefix gggg 001zzznnnx*
 zone prefix njedge_portal_GK 001*

 no use-proxy gggg default inbound-to terminal
 no use-proxy gggg default outbound-from terminal
 no shutdown
 endpoint ttl 60
 server registration-port 20000

where gggg = name of gatekeeper i.e.: Rutgersgk, fdugk, etc
where dddd = domain of university...i.e.: rutgers.edu, fdu.edu, etc.
where zzznnnx = Endpoint Identifier-  based on main telephone number of school followed by an 
asterisk (i.e.: 0012017822*)



Important Note: Use "underscore" as separator for NJEdge Portal Gatekeeper

(see NJEdge.Net Dialplan for details-
 
http://www.njedge.net/techsection/dialplandetails.html
http://www.njedge.net/techsection/Dialplan_GKMap10.jpg

NJEdge.Net recommends using the "bandwidth" 
command to avoid oversubscribing your Extranet circuit. For 
example:

 bandwidth interzone default bbbb

where bbbb = amount of bandwidth available for H.323 traffic 
(75% of either your full Extranet PVC or the amount of bandwidth allotted to prioritized traffic).
 The value should reflect both sides of video calls in Kbps.
 For example, if your Extranet PVC is 8Mb, and entirely allotted to prioritized traffic,
 the command would be:

 bandwidth interzone default 12000

(75% of 8Mb = 6Mb times 2 = 12000)

This example presumes you have one zone for your campus. For campuses with more than one zone,
 use a separate bandwidth command for each zone, replacing "default" with "zone" and a zone name,
 and the appropriate bandwidth total for each interzone link.

(For more information see:
 http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dt_mcm5t.pdf  )