A: Some
time back, Jim Patterson with 4CNet requested you allocate an IP address for
the gatekeeper and instruct us what default route and subnet mask to use. Please
connect the gatekeeper to that network.
A: After the gatekeeper is installed and
connected to the network, we'll be logging onto it to perform an upgrade and
full gatekeeper configuration. We didn't do these in advance because we knew
that both the configuration and the firmware version would probably change
between the time we started shipping gatekeepers and the time we were ready
to make them go into production. If we cannot connect to the gatekeeper, we'll
be contacting you for assistance. The most likely problem is that there is
a firewall in place. Any firewalls need to be configured as described in the Firewall
Configuration page .
A: We'll be assigning a forward name based on
the name we used for your campus router. For example, if we called your campus
router "hcoe," we'll call your gatekeeper "hcoe-gk.cenic.net." We'll start
including this information when we contact you and will let you know what DNS
entry to add.
A: We're working
through the backlog of gatekeepers which have been received by sites. We're
giving priority to the sites which have already cut over their data circuits.
Those folks will be hearing from us first. But if you've got your gatekeeper
hooked up and reachable as we describe above, that will speed up the process
a lot. Once we configure the gatekeeper completely, we'll be getting together
with your video folks to start testing CVS for your site.
