1. Configure the DPNSS gateway to communicate with the Cisco EGW:

• On the gateway, provision MGCP and DUA/SCTP.

  Refer to Configuring a Media Gateway for Cisco EGW Integration for details.

2. Open Cisco EGW Administration.
3. (If the gateway is on a different subnet from Cisco EGW) In Cisco EGW Administration, add an IP route for the gateway. Refer to Cisco EGW Administration online help for details.
4. In Cisco EGW Administration, provision a DPNSS media gateway:
   1. Add a media gateway and enter the basic gateway configuration. Skip Dial Plan until dial plans have been created later in this procedure. Click Update.

   Adding a gateway creates a route to the gateway, named in the form rt-mgw#-0-1 where mgw# is the name of the media gateway. You can use this route in creating route plans and dial plans.

   2. (If you want to change default MGCP properties) Click Properties and make desired changes.
   3. Add T1 or E1 DPNSS spans.
   4. (If you want to change default DPNSS features) Click Properties and make desired changes.
5. In Cisco EGW Administration, verify connectivity:

• Verify that Signaling Path State for T1 or E1 spans is In Service.

In a fault-tolerant configuration, perform this task on the active Cisco EGW first.

If you are using a gatekeeper:

1. On the H.323 gatekeeper, provision Cisco EGW information.

   Refer to Configuring an H.323 Gatekeeper to Communicate with Cisco EGW.

2. Open Cisco EGW Administration. In Cisco CallManager Interfaces under H.323, select Gatekeeper Mode.
3. Fill in Gatekeeper Details for your gatekeeper.Refer to Cisco EGW Administration online help on this topic for details.
4. Verify connectivity: Log in to the gatekeeper and verify that Cisco EGW is registered.

If you are not using a gatekeeper:

1. Open Cisco EGW Administration. Set up Direct Mode on the active Cisco EGW:
   1. In Cisco CallManager Interfaces under H.323, select Direct Mode.
   2. Fill in Direct Mode Details, a primary IP address and port (and optional secondary IP address and port) for Cisco CallManager. The port default is 1720. Refer to Cisco EGW Administration online help on this topic for details.

   The system restarts. In a fault-tolerant system, the peer becomes active and the system you just set up becomes the standby.

   Note: If you receive an error that provisioning failed because of the absence of the peer standby, go to the Cisco EGW Administration Home page and set the system to Virtual Fault Tolerant mode. The system restarts and you can now set Direct Mode as in Step 1.

2. Repeat step 1 to set up Direct Mode on the newly active Cisco EGW. The system restarts. In a fault-tolerant system, the Cisco EGW you started with is again active.

1. Configure CiscoCallManager to communicate with Cisco EGW. On Cisco CallManager:

• Provision an H.225 gatekeeper-controlled trunk.

  Refer to Configuring the Cisco CallManager for Cisco EGW Integration for details.

• Enter dial plan information.

2. Open Cisco EGW Administration.
3. Provision the Cisco CallManager interfaces:

• Add Cisco CallManager Cluster(s). You need to specify the Cisco CallManager version.
• For each cluster, add CTI Managers and AXL Servers.
• For H.323: Complete the Interface portion of the Cisco CallManager Interfaces > H.323 window.

  Note: In a fault-tolerant system, also provision the H.323 interface on the standby peer.

Refer to Configuring the Cisco CallManager for Cisco EGW Integration for important information about Cisco CallManager CTI managers and AXL servers..

Refer to Cisco EGW Administration online help for details on the interface property windows.

Call Back When Free: Test a call from the DPNSS PBX to IP phone, from IP phone to DPNSS PBX, and from IP phone to IP phone.

Call Back When Next Used: Test a call from the DPNSS PBX to IP phone, from IP phone to DPNSS PBX, and from IP phone to IP phone.