Using Cs 1000 As A Gatekeeper

Using CS 1000 as a gatekeeper ________________________________________ Using CS 1000 as a gatekeeper Both the BCM and the CS 1000 must be set to the parameters described in the following information for the gatekeeper to work effectively. Refer to IP Peer Networking: Installation and Configuration (553-3001-213) for detailed information on configuring a CS 1000 gateway. For CS 1000, the Network Routing Service (NRS) can be configured and maintained through a web interface called NRS Manager. NRS Manager replaces the CS 1000 GK admin tool. Review the following information before attempting to use the CS 1000 as a gatekeeper: • Before a Gateway Endpoint registers with the CS 1000 gatekeeper it must first be added to the gatekeeper configuration. • Before a registered Gateway Endpoint makes calls, it must have its routing entry information assigned within the gatekeeper configuration. • Before any of these configuration changes become part of the gatekeeper active configuration, they must be committed to the active database. BCM Requirement Set the BCM Local Gateway IP interface to the following using BCM Element Manager (go to Configuration > Resources > Telephony Resources > {Select IP Trunk} > H323 Settings tab): • Set Call Signaling to GatekeeperRouted or GatekeeperResolved. • Set Primary Gatekeeper IP to the IP address of the NRS. • Set Alias Names to the Alias name that was used when the H.323 Endpoint for the BCM was created on the NRS. In order to make a BCM 3.01 (or later)-to-CS 1000 call, ensure that the BCM routes and dialing plan (used to reach the CS 1000 systems) match the numbering plan entry assigned to the CS 1000 systems through NRS Manager. Similarly, to make a CS 1000 system-to-BCM 3.01 (or later) call, ensure that the numbering plan entry assigned to the BCM (through NRS Manager) matches the dialing plan information configured on the CS 1000 systems. N0060600 BCM 4.0 Device Configuration Guide N0060606 BCM 4.0 Networking Configuration Guide