Cisco Conference Bridge Hardware

This type supports the Cisco Catalyst 4000 and 6000 Voice Gateway Modules and the following number of conference sessions:

Cisco Catalyst 6000

• G.711 or G.729a conference - 32 participants per port; six participants maximum per conference; 256 total participants per module; 10 bridges with three participants.

• GSM - 24 participants per port; six participants maximum per conference; 192 total participants per module.

Cisco Catalyst 4000

G.711 conference only - 24 conference participants; maximum of four conferences with six participants each.

Cisco Conference Bridge Software

Software conference devices support G.711 codecs by default.

The maximum number of callers for this type equals 256. With a setting of 256, the software conference bridge can support 64 conference sessions of 4 parties each. The maximum number of caller parties in a conference session is specified via the Maximum Ad Hoc Conference and Maximum MeetMe Conference Unicast service parameters.

Cisco IOS Conference Bridge

• Uses the NM-HDV or NM-HDV-FARM network modules.

• G.711 a/mu-law, G.729, G.729a, G.729b, and G.729ab participants can join in a single conference call

• Up to six parties can join in a single conference call

Cisco Unified Communications Manager assigns conference resources to calls on a dynamic basis.

For more information about Cisco IOS Conferencing and Transcoding for Voice Gateway Routers, see the Cisco IOS documentation that you received with this product.

Cisco IOS Enhanced Bridges

• Uses the onboard Cisco Packet Voice/Fax Digital Signal Processor Modules (PVDM2) on the Cisco 2800 and 3800 series voice gateway routers or uses the NM-HD or NM-HDV2 network modules.

• G.711 a-law/mu-law, G.729, G.729a, G.729b, G.729ab, GSM FR, and GSM EFR participants can join in a single conference

• Up to eight parties can join in a single call.

Cisco Unified Communications Manager assigns conference resources to calls on a dynamic basis.

For more information about Cisco IOS Enhanced Conferencing and Transcoding for Voice Gateway Routers, see the Cisco IOS documentation that you received with this product.

This conference bridge type supports SRTP media encryption with AES_CM_128_HMAC_SHA1_80 for supported SIP phones where an ISR 4000 series gateway is deployed. SCCP phones and non-supported SIP phones fall back to AES_CM_128_HMAC_SHA1_32 encryption.

Cisco Conference Bridge (WS-SVC-CMM)

This conference bridge type supports the Cisco Catalyst 6500 series and Cisco 7600 series Communication Media Module (CMM).

It supports up to eight parties per conference and up to 64 conferences per port adapter. This conference bridge type supports the following codecs: This conference bridge type supports ad hoc conferencing.

• G.711 a-law/mu-law

• G.729 annex A and annex B

• G.723.1

Cisco Video Conference Bridge (IPVC-35xx)

The Cisco Video Conference Bridge provides audio and video conferencing functions for Cisco IP video phones, H.323 endpoints, and audio-only Cisco Unified IP Phones. The Cisco Video Conference Bridge supports the H.261, H.263, and H.264 codecs for video.

Cisco TelePresence MCU

Cisco TelePresence MCU is a set of hardware conference bridges for Cisco Unified Communications Manager.

The Cisco TelePresence MCU is a high-definition (HD) multipoint video conferencing bridge. It delivers up to 1080p at 30 frames per second, full continuous presence for all conferences, full transcoding, and is ideal for mixed HD endpoint environments.

The Cisco TelePresence MCU supports SIP as the signaling call control protocol. It has a built in Web Server that allows for complete configuration, control, and monitoring of the system and conferences. The Cisco TelePresence MCU provides XML management API over HTTP.

Cisco TelePresence MCU allows both ad hoc and meet-me voice and video conferencing. Each conference bridge can host several simultaneous, multiparty conferences.

Cisco Unified Communications Manager supports presentation sharing with the Binary Floor Control Protocol (BFCP) between Unified Communications Manager and a Cisco TelePresence MCU.

Cisco TelePresence MCU must be configured in Port Reservation mode. For more information, consult the Cisco TelePresence MCU Configuration Guide.

Cisco TelePresence Conductor

Cisco TelePresence Conductor provides intelligent conference administrative controls and is scalable, supporting device clustering for load balancing across MCUs and multiple device availability. Administrators can implement the Cisco TelePresence Conductor as either an appliance or a virtualized application on VMware with support for Cisco Unified Computing System (Cisco UCS) platforms or third-party-based platforms.

Cisco TelePresence Conductor dynamically selects the most appropriate Cisco TelePresence resource for each new conference. Ad hoc, "MeetMe", and scheduled voice and video conferences can dynamically grow and exceed the capacity of individual MCUs. Up to three Cisco TelePresence Conductor appliances or virtualized applications may be clustered to provide greater resilience. One Cisco TelePresence Conductor appliance or Cisco TelePresence Conductor cluster has a system capacity of 30 MCUs or 2400 MCU ports.

Cisco Meeting Server

The Cisco Meeting Server conference bridge solution allows Ad Hoc, Meet-Me, Conference Now, and Rendezvous conferences. This conference bridge offers premises-based audio, video, and web conferencing, and works with third-party on-premises infrastructure. It scales for small or large deployments. You can add capacity incrementally as needed, to ensure that you can support the current and future needs of your organization. This conference bridge provides advanced interoperability. Any number of participants can create and join meetings from:

• Cisco or third-party room or desktop video systems

• Cisco Jabber Client

• Cisco Meeting App (can be native or with a WebRTC compatible browser)

• Skype for Business

A minimum release of Cisco Meeting Server 2.0 is required to use the Cisco Meeting Server conference bridge.

The Cisco Meeting Server supports SIP as the signaling call control protocol. It has a built in Web Server that allows for complete configuration, control, and monitoring of the system and conferences. The Cisco Meeting Server provides XML management API over HTTP.