Cisco Unified MeetingPlace Release 8.5 -- Choosing an Audio and Video Deployment for Cisco Unified MeetingPlace Release 8.5

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace Release 8.5

Up one level: Planning Your Deployment


This chapter discusses design considerations and recommendations for Cisco Unified MeetingPlace Release 8.5 deployments that include video. These deployments include audio and may or may not include a web component. If you do not want to use video in your deployment, see Choosing an Audio Without Video Deployment for Cisco Unified MeetingPlace Release 8.5.


This chapter does not include a comprehensive list of all possible audio and video deployments but instead describes common scenarios.


Contents

About Audio and Video Deployments

All Cisco Unified MeetingPlace Release 8.5 systems require Cisco Unified Communications Manager. For audio and video deployments, the minimum release of Cisco Unified Communications Manager that we support is Release 6.1.5.


Cisco Unified MeetingPlace Release 8.5 supports multiple deployments for combined video and audio support. The deployment that you use depends on your endpoints and on whether you use an Express Media Server or a Hardware Media Server. For information about choosing between an Express Media Server or a Hardware Media Server, see the Choosing Between the Hardware Media Server and the Express Media Server

The MeetingPlace 8.5 Audio deployment supports sRTP encrypted audio conferences with either Express or Hardware Media Server options. Enabling sRTP requires UC Manager 7.0 or above to enable SIP trunks with sRTP for audio conferences only. Video is not available for sRTP meetings. Enabling sRTP on MeetingPlace affects capacity.

The recommended setting on the SIP trunk at Cisco Unified Communications Manager (CUCM) is “no-preference” for the DTMF type. By design, the system prefers RFC 2833 automatically.

KPML is not supported natively in the Cisco Unified MeetingPlace Express Media Server (EMS) and the only recommended DTMF signaling method is RFC 2833. If there is a deployment that needs to use KPML, the recommended solution is to use Media Termination Points with CUCM. See http://www.cisco.com/en/US/solutions/ns340/ns414/ns728/networking_solutions_products_genericcontent0900aecd805b561d.html.

KPML is also supported in the Cisco Unified MeetingPlace Hardware Media Server (HMS). However, the system automatically prefers RFC2833, as KPML DTMF packets generally put more pressure on signaling resources.

SCCP and SIP endpoints that support RFC2833 will work in these deployments. The preferred signaling protocol is SIP.

The Cisco Unified MeetingPlace Web Server is required if you need Audio only or Audio/Video Recordings, Lotus Notes Integration or the Cisco Unified MeetingPlace Web scheduling user interface. If you only need Outlook Scheduling without recordings, then the Cisco Unified MeetingPlace Web Server is not required.


Related Topics

Determining which Audio and Video Deployment to Use

You choose the audio and video deployment to use based on the type of endpoints that you offer.


For a list of the video endpoints that Cisco Unified MeetingPlace Release 8.5 supports, see the Compatibility Matrix for Cisco Unified MeetingPlace Release 8.5 at: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_8.5_--_Compatibility_Matrix_for_Cisco_Unified_MeetingPlace_Release_8.5


Audio and Video Deployment Option 1: Using SCCP or SIP Video Endpoints

You integrate SCCP or SIP video endpoints by defining a SIP trunk on Cisco Unified Communications Manager and Cisco Unified MeetingPlace. Cisco Unified MeetingPlace supports SIP delay-offer, thus a static Media Termination Point (MTP) is optional with all calls across a SIP trunk between Cisco Unified Communications Manager and Cisco Unified MeetingPlace. You can also create a separate SIP trunk security profile, with the outbound transport type set to TCP, and associate it with the SIP trunk to Cisco Unified MeetingPlace. The SIP trunk routes all outbound and inbound calls through a single Cisco Unified Communications Manager cluster.


Examples of SCCP and SIP endpoints are as follows:

  • SCCP: Cisco Unified Video Advantage, Cisco Unified IP Phone 7985
  • SIP: Cisco Unified Personal Communicator with Video Camera, Cisco Unified Communications Integration for Microsoft Office Communicator (CUCIMOC) with Video Camera Release 8.x, and Cisco Unified IP Phone 9900 series with Video Camera


This deployment uses Cisco Unified Communications Manager Release 6.1.5 or later. The call path is as follows:

  1. SIP or SCCP (voice or video) endpoint
  2. Cisco Unified Communications Manager Release 6.1.5 or later
  3. Cisco Unified MeetingPlace


Audio and Video Deployment Option 2: Using H.323 Video Endpoints

Cisco Unified MeetingPlace Release 8.5 does not provide native support for H.323 endpoints. If you want to use H.323 endpoints, you must use RAS (Registration, Admission, and Status) and an IOS gatekeeper. The IOS gatekeeper sends all video calls through via Cisco Unified Communications Manager Release 6.1.5 or later to convert the H.323 signaling to SIP. This deployment accommodates existing deployed video solutions. All H.323 video endpoints must register to a IOS gatekeeper. Some video features currently supported by H.323 may not work with SIP. This deployment option also includes support for third party endpoints.


This deployment uses an IOS gatekeeper-controlled call-control domain which integrates with Cisco Unified Communications Manager Release 6.1.5 or later. The call path is as follows:

  1. H.323 endpoint
  2. H.323/RAS signaling
  3. IOS gatekeeper
  4. Cisco Unified Communications Manager Release 6.1.5 or later
  5. SIP
  6. Cisco Unified MeetingPlace


Audio and Video Deployment Option 3: Using SIP, SCCP, and H.323 Video Endpoints

This deployment is for systems that will use SIP, SCCP, and H.323 video endpoints. It is a combination of audio and video deployment options 1 and 2.

Rating: 2.2/5 (9 votes cast)

Personal tools