About#

Describes the reference environment for most of the examples on this site.

Components#

• CUAE servers version 2.5.x or greater
• CUAE development tools version 2.5.x or greater (should match the CUAE server version)
• CUCM version 6.1 or greater
• 2 x 7965 (could replace w/ 7941,7961,7942,7962,7945,7965,7970,7971,7975)
• Windows XP workstation

The Environment#

Note: Insert Diagram of reference network

 [CUCM] <---> [CUAE]

+--> [RP: 4000] --> [CUAE: AnswerAndPlay]

+--> [Phone Services] --> [CUAE: SimleIpPhoneMenuTree]

+--> [Phone Services] --> [CUAE: BasicExtensionMobility]

+--> [7965]

+--> [7965] }}}

To demonstrate Call Control protocol independence, the CUCM and CUAE will be configured with 3 different "routing strategies".

• H.323 Route Point in CUCM directed to the CUAE acting as H.323 gateway.
• CUAE registering a SIP "virtual endpoint" with the CUCM.
• JTAPI/CTI Route Point in CUCM directed to the CUAE acting as a CTI Manager.

Only one of these choices is actually necessary for this application. The point here is to illustrated that any of these choices will work with the application with no change to the application whatsoever.

When we are ready to actually run the application, we will adjust the application's triggering properties in the CUAE Administration Console to work with the different call-control configurations.

Setup H.323 Gateway#

You would need to create the H323 Gateway in cuaeadmin console as well as the CCM. And each will point to other as shown below:

• Access cuaeadmin console.
• Select Connections menu and Add button to add an H323 Gateway to point to your CCM.

• Access your Call Manager console.
• Select Device > Gateway menu.
• Add a gateway to point back to your CUAE server.

Setup SIP Endpoint#

This setup comprises of defining a SIP domain within your cuaeadmin console. This is done by checking the Call Control checkbutton under your CCM cluster configuration page. Secondly, you would need to add a SIP trunk in Call Manager to point to your cuae server. Lastly, you would need to specify SIP as your Call Route Group under configuration options for each individual application which needs to use SIP. These are illustrated below:

Selecting Call Control checkbox will create a SIP domain:

To create a SIP trunk in Call Manager, select Devices > Trunk to create a SIP trunk:

Setup CTI Route Point#

A CTI Route Point setup needs to be defined in cuaeadmin console as well as CCM. To define it in cuaeadmin console, first verify the CTI checkbox is checked in CCM cluster setup in cuaeadmin console page, then use Connections menu and select Device Pool radio button. This will provide leads to following page where the Route Point could be defined:

CTI checkbox is shown selected:

CTI Route Point setup page:

To define a CTI Route Point in CCM, use Device menu through the CCM console: