Cisco Unified MeetingPlace Express, Release 2.x -- How to Configure Cisco Unified Communications Manager Integration Without a Gatekeeper

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m
m (Bot: Adding {{Template:Required Metadata}})
 
Line 1: Line 1:
 +
{{Template:Required Metadata}}
'''Main page:'''  [[Cisco Unified MeetingPlace Express, Release 2.x]]
'''Main page:'''  [[Cisco Unified MeetingPlace Express, Release 2.x]]

Latest revision as of 22:44, 17 December 2009

Main page: Cisco Unified MeetingPlace Express, Release 2.x


This topic describes how to integrate Cisco Unified CallManager Release 4.1 with Cisco Unified MeetingPlace Express in an H.323 environment. In this method, Cisco Unified MeetingPlace Express is configured as a gateway to Cisco Unified Communications Manager. No gatekeeper is used in this setup.


Note: If you have a Cisco Unified Communications Manager cluster that provides call-processing redundancy, and if the primary Cisco Unified Communications Manager server goes down, Cisco Unified MeetingPlace Express cannot complete dial-out calls without a gatekeeper. For information about Cisco Unified Communications Manager integration with a gatekeeper, see Configuring Call-Control Integration for Cisco Unified MeetingPlace Express Using a Gatekeeper.


To integrate Cisco Unified MeetingPlace Express with Cisco Unified Communications Manager in an H.323 environment without a gatekeeper, complete the following tasks:


Contents

Configuring Cisco Unified Communications Manager: Adding the Gateway and Route Pattern

This topic describes how to identify Cisco Unified MeetingPlace Express as a gateway in the Cisco Unified Communications Manager configuration database. This topic also describes how to enable Cisco Unified Communications Manager to route calls to Cisco Unified MeetingPlace Express by associating a phone number with the gateway. This association is called a route pattern.


Note: The names for Cisco Unified CallManager Release 4.3, Release 5.1, and Release 6.0 have been changed to Cisco Unified Communications Manager Release 4.3, Release 5.1, and Release 6.0. The names of Cisco Unified CallManager Release 4.0, Release 4.1, Release 4.2, and Release 5.0 have not changed and remain the same.


Before You Begin
  • Verify that your Cisco Unified Communications Manager release and Cisco Unified MeetingPlace Express release are compatible. See the Release Notes for Cisco Unified MeetingPlace Express Release 2.0 or the Release Notes for Cisco Unified MeetingPlace Express Release 2.1.
  • Verify that your IP telephony network is already set up and working properly. For example:
    • Verify that the Cisco Unified IP Phones are properly connected and added to the Cisco Unified Communications Manager database.
    • Verify that you can place and receive internal and external calls on the Cisco Unified IP Phones.


Restrictions
  • This task is performed in the Cisco Unified Communications Manager pages. Because the pages and menus vary by Cisco Unified Communications Manager release, you may need to see the Cisco Unified Communications Manager online help for more accurate step-by-step instructions than those provided in this procedure. The following procedure refers to Cisco Unified CallManager Release 4.1.


Note: In this procedure, the term Cisco Unified CallManager refers to both Cisco Unified CallManager and Cisco Unified Communications Manager.


Procedure
  1. Go to http://ccm-server/ccmadmin/main.asp, where ccm-server is the fully qualified domain name or IP address of the Cisco Unified CallManager server.
  2. Log in with your Cisco Unified CallManager administrator username and password.
  3. Add the gateway to the Cisco Unified CallManager database by completing the following actions:

a. Click Device > Gateway.

b. In the top right corner, click Add a New Gateway.

c. Select the H.323 Gateway type.

d. Select the H.225 device protocol.

e. Click Next.

f. Configure the fields described in Table: Gateway Configuration Fields.


Table: Gateway Configuration Fields
Gateway Configuration Field Action

Device Name

Enter the IP address or hostname for Port 1 (eth0) of the Cisco Unified MeetingPlace Express server. This value was set when you installed Cisco Unified MeetingPlace Express.


If you are using DNS, enter the full server name with the qualifying domain, for example: mpx-server.example.com.

Description

Enter a short description to distinguish this gateway from other gateways to Cisco Unified CallManager.

Device Pool


(The device pool specifies a collection of properties for this device including Cisco Unified CallManager Group, Date/Time Group, and Region.)

If no device pools are defined, select Default.


If the Cisco Unified CallManager deployment uses customer-defined device pools, either create a new device pool or choose an existing device pool for a region with a codec that is compatible with the conferencing gateway (or bridge).


Currently, Cisco Unified MeetingPlace Express supports only the G.711and G.729a audio codecs.

Location


(The location specifies the total bandwidth that is available for calls to and from this location. A location setting of None means that the locations feature does not keep track of the bandwidth that this device consumes.)

If no locations are defined, keep the default value of None.


If the Cisco Unified CallManager deployment uses customer-defined locations, configure this field to avoid conflicts with QoS settings on the WAN. Either create a new location or choose an existing location that represents the conferencing gateway within the corporate WAN.

Signaling Port

Keep the default value of 1720.

Media Termination Point Required


Media Termination Point (MTP) is required only if:

  • You have non-G.711 endpoints, such as G.729a callers, joining your meetings and if you have not configured any G.729a ports.
  • You have callers that use codecs other than G.711 or G.729a calling into the Cisco Unified MeetingPlace Express system. Note that calls using an MTP or transcoder may not use video.


In such circumstances, make sure that the Media Resource Group List (MRGL) associated with the Cisco Unified MeetingPlace Express server has a transcoder and that the inter-region setting between the transcoder and the Cisco Unified MeetingPlace Express server is G.711.

Uncheck this check box if you want video to work. Video will not work if this box is checked. Checking this box prevents calls from supporting video. MTP should only be used when necessary.

Calling Search Space


(A CSS specifies the collection of route partitions that are searched to determine how a collected [originating] number should be routed. Use the CSS to prevent toll fraud by controlling which dial patterns may be dialed out from Cisco Unified MeetingPlace Express. For example, you can use CSS to block international calls.)

If no calling search spaces (CSSs) are defined, keep the default value of None.


If the Cisco Unified CallManager deployment uses customer-defined CSSs, either create a new CSS or choose an existing CSS that allows the conferencing gateway to dial any numbers that are required to join attendees in to conferences and to reach the Help Desk attendant.

AAR Calling Search Space


(The AAR CSS specifies the collection of route partitions that are searched to determine how to route a collected [originating] number that is otherwise blocked due to insufficient bandwidth.)

If no AAR CSSs are defined, keep the default value of None.


If the Cisco Unified CallManager deployment uses customer-defined CSSs, choose the appropriate CSS for the device to use when it performs automated alternate routing (AAR).


g. For all other required fields, configure them appropriately for the current Cisco Unified CallManager deployment. For information about each field, see the Cisco Unified CallManager online help or the administration guide for your specific Cisco Unified CallManager release.

h. Click Insert.

4. Add the route pattern to the Cisco Unified CallManager database by completing the following actions:

a. Click Route Plan > Route/Hunt > Route Pattern.

b. In the top right corner, click Add a New Route Pattern.

c. Configure the fields described in Table: Fields for Adding a New Route Pattern to Cisco Unified CallManager.


Table: Fields for Adding a New Route Pattern to Cisco Unified CallManager
Route Pattern Configuration Field Action

Route Pattern

Enter the phone number that users will use to call in to Cisco Unified MeetingPlace Express. Do not enter any spaces in this field.

Gateway or Route List

Select the value that matches the Device Name you entered for the gateway in Step 3f.


d. Click Insert.

5. If you have multiple Cisco Unified MeetingPlace Express access numbers, repeat Step 4 for each access number, including the following:

  • Meeting phone numbers entered on the Usage Configuration page
  • Direct meeting dial-in numbers

6. Proceed to the Configuring Cisco Unified MeetingPlace Express: Connecting to Cisco Unified Communications Manager.


Configuring Cisco Unified MeetingPlace Express: Connecting to Cisco Unified Communications Manager

Before You Begin


Restrictions
  • When you modify the parameters on the H.323 Configuration page, Cisco Unified MeetingPlace Express reinitializes H.323 signaling with the call-control device, for example, Cisco Unified Communications Manager. During the reinitialization process, which can take up to 2 minutes, calls and voice meetings may be affected.


Procedure
  1. Log in to Cisco Unified MeetingPlace Express and click Administration.
  2. Click System Configuration > Call Configuration > H.323 Configuration.
  3. Configure the fields in Table: Required Configuration for H.323 Configuration Page on Cisco Unified MeetingPlace Express for Cisco Unified Communications Manager Integration Without a Gatekeeper.


Table: Required Configuration for H.323 Configuration Page on Cisco Unified MeetingPlace Express for Cisco Unified Communications Manager Integration Without a Gatekeeper
H.323 Configuration Page Field Required Value

H.323 enabled

Yes

Local H.323 port

1720 (default)

Use gatekeeper

No

H.323 gateway 1

IP address of the Cisco Unified Communications Manager server.


If you have a cluster of Cisco Unified Communications Manager servers, enter the IP address of the primary call-processing server in the cluster.

H.323 gateway 2


H.323 gateway 3


H.323 gateway 4


H.323 gateway 5

IP addresses of other Cisco Unified Communications Manager servers in the cluster that provide call-processing redundancy, if any.

Note: If the primary Cisco Unified Communications Manager server goes down, Cisco Unified MeetingPlace Express cannot complete dialed-out calls without a gatekeeper. These fields enable only incoming calls to be routed by the failover Cisco Unified Communications Manager servers.


4. Click Save.

5. Click System Configuration > Call Configuration > Dial Configuration.

6. Set the Outdials field to H.323.

7. Click Save.

8. Test this integration by placing a call from any phone to the phone number that is used to access the Cisco Unified MeetingPlace Express system. You should hear the "Welcome to Cisco Unified MeetingPlace Express" greeting.


Related Topics

Rating: 5.0/5 (1 vote cast)

Retrieved from "http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Express,_Release_2.x_--_How_to_Configure_Cisco_Unified_Communications_Manager_Integration_Without_a_Gatekeeper"
Personal tools