Cisco Unified MeetingPlace Release 8.0 -- Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Configuring Cisco Unified MeetingPlace for Ad-Hoc Conferences Only)
m (1 revision)
 

Latest revision as of 16:54, 2 July 2010

Main page: Cisco Unified MeetingPlace, Release 8.0

Up one level: Configuration



Note: For an overview of and recommendations for ad-hoc conferencing, see the Planning Guide for Cisco Unified MeetingPlace at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.


To configure ad-hoc conferencing, you must set up both Cisco Unified MeetingPlace and Cisco Unified Communications Manager. Once both products are configured, Cisco Unified MeetingPlace registers with Cisco Unified Communications Manager to report the voice and video port configuration, the configured codec to use, and the minimum and maximum video bit rates. Similarly, Cisco Unified Communications Manager sends Cisco Unified MeetingPlace an XML configuration file that contains the parameters that you configured in Cisco Unified Communications Manager.


Contents

Prerequisites for Ad-Hoc Conferencing

  • During the installation of the Cisco Unified MeetingPlace Application Server, you installed the Express Media Server component. Ad-hoc conferencing is not supported with the Hardware Media Server.
  • You must deploy the Cisco Unified MeetingPlace system as a single node. Ad-hoc conferencing is not supported in a reservationless single number access (RSNA) deployment.
  • Install the Cisco Unified MeetingPlace licenses.


Related Topics


Restrictions for Ad-Hoc Conferencing

  • Ad-hoc conferencing is supported only with the Express Media Server.
  • Ad-hoc meetings are not recorded in billing reports.
  • Ad-hoc meetings do not appear in the web user portal.
  • Voice and video recordings of ad-hoc conferences are not supported.
  • Cisco Unified Communications Manager Release 6.0. supports only voice for ad-hoc conferencing. Video is not supported.
  • Cisco Unified Communications Manager Releases 6.1, 7.1, and 8.0 support H.264-AVC and H.263 video for ad-hoc conferencing.
  • For failover restrictions with the Express Media Server, see Restrictions for Application Server Failover in the Configuring Application Server Failover for Cisco Unified MeetingPlace module.


Configuring Cisco Unified MeetingPlace Call Control Features for Ad-Hoc Conferencing

Follow this procedure to configure TFTP server IP addresses so that Cisco Unified MeetingPlace can register with Cisco Unified Communications Manager.


Caution! Changing these configuration parameters causes the Cisco Unified MeetingPlace system to clear all active calls and meetings. The system then cancels the current registration with Cisco Unified Communications Manager and reregisters using the new configuration parameters.


Procedure
  1. Sign in to Cisco Unified MeetingPlace Administration Center.
  2. Select System Configuration > Call Configuration > Ad-Hoc Cisco Unified Communications Manager Configuration.
  3. Enter or change the values in the fields. At a minimum, configure these fields:
    • Enable SCCP-Select Yes.
    • Primary TFTP server-Enter the IP address of the primary Cisco Unified Communications Manager server on which the TFTP service is running.
    • (Optional) Backup TFTP server 1-Enter the IP address of a backup Cisco Unified Communications Manager server on which the TFTP service is running.
  4. Write down or copy the value in the Application server MAC address field, which you need to add the Cisco Unified MeetingPlace server as a conference bridge in Cisco Unified Communications Manager.
  5. Select Save.
Related Topics

Configuring Cisco Unified Communications Manager to Use Cisco Unified MeetingPlace as a Conference Bridge

Follow this procedure to configure Cisco Unified Communications Manager to use Cisco Unified MeetingPlace as a conference bridge, to configure some ad-hoc conferencing settings, and to create meet-me numbers.


This procedure is performed in Cisco Unified Communications Manager Administration. Because the pages and menus vary by Cisco Unified Communications Manager release, you might need to see the Cisco Unified Communications Manager online help for more accurate step-by-step instructions than those provided in this procedure.


Note: This procedure is for Cisco Unified Communications Manager Release 8.0(1). For details on the fields, see the administration guide and system guide for your specific Cisco Unified Communications Manager release at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.


Before You Begin

Complete this procedure: Configuring Cisco Unified MeetingPlace Call Control Features for Ad-Hoc Conferencing. You need the Application server MAC address from this procedure.


Caution! Make sure you configure the DNS entries for both Cisco Unified Communications Manager and Cisco Unified MeetingPlace; otherwise, Cisco Unified MeetingPlace might not be able to register with Cisco Unified Communications Manager after it has downloaded the XML configuration file from the TFTP server. This is because the XML file listing might contain only the DNS host name references to Cisco Unified Communications Manager in the cluster.


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 Communications Manager server.
  2. Sign in to Cisco Unified Communications Manager Administration.
  3. Select Media Resources > Conference Bridge.
  4. Select Add New in the top left corner.
  5. Select Cisco Video Conference Bridge (IPVC-35xx) for the conference bridge type.
  6. Enter the Cisco Unified MeetingPlace MAC address that you obtained in Configuring Cisco Unified MeetingPlace Call Control Features for Ad-Hoc Conferencing.
  7. Select a device pool from the list, or select Default.
  8. (Optional) Configure the fields on the rest of the page.
  9. Select Save.
  10. Select Reset to reset the conference bridge and to apply your changes.
    Cisco Unified MeetingPlace registers with Cisco Unified Communications Manager. Once the Status field displays "Registered" on the Cisco Unified MeetingPlace Administration Center Ad-Hoc Cisco Unified Communications Manager Configuration page, the Cisco Unified MeetingPlace conference bridge becomes available for Cisco Unified Communications Manager ad-hoc meetings.
  11. Configure Cisco Unified Communications Manager clusterwide parameters for ad-hoc conferences.
    1. Select System > Service Parameters.
    2. Select the server.
    3. Select the Cisco CallManager service.
    4. Scroll to Clusterwide Parameters (Feature-Conference) section.
    5. Change the default settings for Maximum Ad-Hoc Conference and for Maximum MeetMe Conference as necessary to increase the limit on participants joining these conferences.
    6. Select True for the Change the Advanced Ad Hoc Conference Enabled field. This means that only the first endpoint that initiates the ad-hoc conference by using the CONF button needs to be in the same media resource group list (MRGL) as the video bridge. Subsequent endpoints already in the ad-hoc conf will also be able to use the CONF button even if they are not in the same MRGL. The latter is not possible if the setting is False.
    7. Set Minimum Video Capable Participants to Allocate Video Conference to 0.
      Setting this to 0 means that the Cisco Unified MeetingPlace ad-hoc bridge is always chosen even if only audio endpoints are in the conference.
  12. Enable Cisco Unified Communications Manager meet-me conferences by configuring the Cisco Unified MeetingPlace conference bridge to be used for meet-me conferences.
    Complete these high-level tasks in Cisco Unified Communications Manager:
    1. Add or update one or more meet-me number patterns.
    2. Add or update a media resource group (MRG) to include the MAC address that you configured in Step 6.
    3. Add or update a MRGL to include the MRG that you configured in Step 12.2.
      Note: Cisco Unified Communications Manager always uses the first resource found in the MRGL. If a voice-only conference bridge is placed at the top of the MRGL, Cisco Unified Communications Manager always uses that conference resource first, even if the call requires video. Therefore, position this MRG at the top (highest-priority position) of the MRGL.
    4. Configure each phone (voice or video endpoint) that will initiate meet-me conferences to the MRGL that you configured in Step 12.3.
      Note: The MRG and MRGL are also used by Cisco Unified Communications Manager or when selecting a bridge for ad-hoc (conference button) meetings.
Troubleshooting
  • If the Status field on the Ad-Hoc Cisco Unified Communications Manager Configuration page does not display "Registered," wait about 30 seconds and reload the ad-hoc configuration page. The page does not automatically refresh.
  • If you reload the page and the Status field still does not display "Registered," restart the Cisco Unified MeetingPlace server.
  • If your ad-hoc video endpoints are conferencing successfully, but not getting video, make sure they are connecting to the Cisco Unified MeetingPlace ad-hoc conference bridge. They might be using some other non-video bridge, such as the softbridge in Cisco Unified MeetingPlace.
What to Do Next

If you want to configure the system for ad-hoc voice and video conferences, proceed to Configuring Cisco Unified MeetingPlace Media Resources for Ad-Hoc Conferencing.


If you want to configure the system for ad-hoc conferences only (no scheduled or reservationless meetings), proceed to Configuring Cisco Unified MeetingPlace for Ad-Hoc Conferences Only.


Configuring Cisco Unified MeetingPlace Media Resources for Ad-Hoc Conferencing

Before You Begin
  • Use the Resource Management Spreadsheet to help you analyze the audio and video requirements of your user base. If you know how many users on the network use video and at what speed, and what type of audio quality, you can determine how many licenses to buy and whether to buy additional licenses to override the system capacity to provide extra features. For details, see the Planning Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ ps5664/ps5669/products_implementation_design_guides_list.html.
  • Install the appropriate licenses. See the Installing and Managing Licenses for Cisco Unified MeetingPlace module.


Procedure
  1. Sign in to Cisco Unified MeetingPlace Administration Center.
  2. Select System Configuration > Media Resource Configuration.
  3. Verify that the Type of media server is set to Express Media Server.
  4. Configure the options in the Ad-Hoc Audio and Video Settings (available only when the Type of media server is set to Express Media Server) section to ensure that there are audio-only or audio plus video resources available for your users.
    For audio-only:
    1. Specify the number of ports to use for Ad-hoc audio ports.
    2. (Optional) Select Yes for Enable ad-hoc G.729 or G.722.
    To include video with audio:
    1. Select Yes for Enable ad-hoc video to enable the remaining ad-hoc video fields.
    2. Configure the remaining settings:
      • Ad-hoc video mode
      Note: The system applies the Ad-hoc video mode selection at the system level so that all ad-hoc conferences on this server use this video mode.
      • Ad-hoc video minimum bit rate (kbps)
      • Ad-hoc video maximum bit rate (kbps)]
      The conference bridge offers the minimum and maximum bit rates to the endpoint during negotiation. The maximum bit rate is the maximum rate that the endpoint can send video to the conference. The minimum bit rate is the minimum rate that the endpoint must receive video from the conference. The minimum bit rate is the minimum video experience; if the system does not have resources to support this rate, video is not offered to the user.
  5. Select Save.
    The page refreshes with your changes.
  6. Check for configuration problems by selecting Services > Alarms.
Related Topics

Configuring Cisco Unified MeetingPlace for Ad-Hoc Conferences Only

Follow this procedure to configure the Cisco Unified MeetingPlace system to provide ports only for ad-hoc conferences and not to provide ports for scheduled or reservationless meetings.


Procedure
  1. Sign in to Cisco Unified MeetingPlace Administration Center.
  2. Select System Configuration > Media Resource Configuration.
  3. Verify that the Type of media server is set to Express Media Server.
  4. Select change next to Ad-hoc audio ports.
  5. Enter a number equal to the number of Audio available ports.
  6. Select OK.
    The page refreshes, and the Scheduled audio ports field is now set to 0.


What To Do Next

Proceed to the Checking Cisco Unified MeetingPlace Registration to Cisco Unified Communications Manager as a Conference Bridge.


Related Topics


Checking Cisco Unified MeetingPlace Registration to Cisco Unified Communications Manager as a Conference Bridge

Before You Begin
In an Application Server Failover deployment, obtain the MAC addresses for both active and standby servers.
  • You perform this procedure in the Cisco Unified Communications Manager Administration pages. Because the pages and menus vary by release, you should check the Cisco Unified Communications Manager Administration online help for step-by-step instructions that are specific to your release.


Procedure
  1. Go to http://cucm-server, where cucm-server is the fully qualified domain name or IP address of the Cisco Unified Communications Manager server.
  2. Sign in to Cisco Unified Communications Manager Administration.
  3. Select Media Resources > Conference Bridge.
  4. Find the conference bridge whose name is VCB<MAC-address>, where <MAC-address> is the Application server MAC address.
    In an Application Server Failover deployment, use the MAC address of the active server.
  5. In the Status column, verify that the Application Server conference bridge is Registered with the Cisco Unified Communications Manager server.
    Proceed only if you have an Application Server Failover deployment.
  6. Find the conference bridge whose name is VCB<MAC-address>, this time using the MAC address of the standby server.
  7. In the Status column, verify that the standby Application Server conference bridge is Unregistered.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools