-
Cisco Unified Communications Manager Administration Guide, Release 8.6(1)
-
Preface
- Cisco Unified Communications Manager
-
System Configuration
-
Server Configuration
-
Cisco Unified Communications Manager Configuration
-
Cisco Unified Communications Manager Group Configuration
-
Phone NTP Reference Configuration
-
Date/Time Group Configuration
-
Region Configuration
-
Device Pool Configuration
-
DHCP Server Configuration
-
DHCP Subnet Configuration
-
LDAP System Configuration
-
LDAP Directory Configuration
-
LDAP Authentication Configuration
-
LDAP Custom Filter Configuration
-
Location Configuration
-
Survivable Remote Site Telephony Configuration
-
MLPP Domain Configuration
-
Resource Priority Namespace Network Domain Configuration
-
Resource Priority Namespace List Configuration
-
Enterprise Parameter Configuration
-
Enterprise Phone Configuration
-
Service Parameter Configuration
-
Application Server Configuration
-
Autoregistration Configuration
-
Other System Menu Options
-
-
Call Routing Configuration
-
Automated Alternate Routing Group Configuration
-
Application Dial Rule Configuration
-
Directory Lookup Dial Rule Configuration
-
SIP Dial Rule Configuration
-
Route Filter Configuration
-
Route Group Configuration
-
Route List Configuration
-
Route Pattern Configuration
-
Line Group Configuration
-
Hunt List Configuration
-
Hunt Pilot Configuration
-
SIP Route Pattern Configuration
-
Time Period Configuration
-
Time Schedule Configuration
-
Partition Configuration
-
Calling Search Space Configuration
-
Translation Pattern Configuration
-
Directory Number Configuration
-
Meet-Me Number/Pattern Configuration
-
Dial Plan Installer
-
Route Plan Report
-
Calling Party Transformation Pattern Configuration
-
Called Party Transformation Pattern Configuration
-
Other Call Routing Menu Options
-
- Media Resource Configuration
- Advanced Features Configuration
-
Device Configuration
-
CTI Route Point Configuration
-
Gatekeeper Configuration
-
Gateway Configuration
-
Cisco Unified IP Phone Configuration
-
Trunk Configuration
-
Device Defaults Configuration
-
Device Firmware Load Information
-
Default Device Profile Configuration
-
Device Profile Configuration
-
Phone Button Template Configuration
-
Softkey Template Configuration
-
IP Phone Services Configuration
-
SIP Profile Configuration
-
Common Device Configuration
-
Common Phone Profile Configuration
-
Feature Control Policy Configuration
-
Recording Profile Configuration
-
SIP Normalization Script Configuration
-
Other Device Menu Options
-
- Application Configuration
- User Management Configuration
- Cisco Unified Communications Manager Bulk Administration
- Appendixes
-
Index
-
Feedback
Table Of Contents
Conference Bridge Configuration
Software Conference Bridge Configuration Settings
Hardware Conference Bridge Configuration Settings
Cisco IOS Conference Bridge Configuration Settings
Cisco Video Conference Bridge Configuration Settings
Cisco Conference Bridge (WS-SVC-CMM) Configuration Settings
Cisco IOS Heterogeneous Video Conference Bridge Configuration Settings
Cisco IOS Guaranteed Audio Video Conference Bridge Configuration Settings
Cisco IOS Homogeneous Video Conference Bridge Configuration Settings
Cisco TelePresence MCU Configuration Settings
Synchronizing a Conference Device
Conference Bridge Configuration
In Cisco Unified Communications Manager Administration, use the Media Resources > Conference Bridge menu path to configure conference bridges.
Tips About Configuring Conference Bridges
Make sure that the following prerequisites are met before you proceed with configuration of a conference bridge:
•
Configure the device pools. See the "Tips About Deleting Device Pools" section.
Note•
You may also want to see the following topic:
•
Tips About Deleting Conference Bridges
Keep in mind that you cannot delete Cisco Unified Communications Manager Conference Bridge Software. See the "Conference Bridge Configuration" section.
Cisco Unified Communications Manager allows you to delete devices that may be associated with components such as media resource groups. To find out what dependencies the conference device may have, choose the Dependency Records link from the drop-down list box and click Go from the Conference Bridge Configuration window. If the dependency records are not enabled for the system, the dependency records summary window displays a message. For more information about dependency records, see the "Accessing Dependency Records" section.
Using the GUI
For instructions on how to use the Cisco Unified Communications Manager Administration Graphical User Interface (GUI) to find, delete, configure, or copy records, see the "Navigating the Cisco Unified Communications Manager Administration Application" section and its subsections, which explain how to use the GUI and detail the functions of the buttons and icons.
Configuration Settings Tables
Consult one of the following sections, depending on the type of conference bridge that you are configuring.
•
•
•
•
•
•
•
•
•
Additional Information
See the "Related Topics" section.
Software Conference Bridge Configuration Settings
Conference Bridge for Cisco Unified Communications Manager, a software or hardware application, allows both ad hoc and meet-me voice conferencing. Each conference bridge can host several simultaneous, multiparty conferences.
Be aware that both hardware and software conference bridges can be active at the same time. Software and hardware conference devices differ in the number of streams and the types of codec that they support.
You cannot add software conference bridges to Cisco Unified Communications Manager by using Conference Bridge Configuration. Software conference bridges automatically get added when a Cisco Unified Communications Manager server gets added (see the "Server Configuration Settings" section for more information). After a Cisco Unified Communications Manager server gets added, the software conference bridge gets displayed in the Find/List Conference Bridges window (by default, the first software conference bridge gets configured during Cisco Unified Communications Manager installation) when you perform a search. You can update software conference bridges, but you cannot delete them.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-1 describes the software conference bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-1 Software Conference Bridge Configuration Settings
Conference Bridge Type
This field automatically displays Cisco Conference Bridge Software.
Host Server
This field automatically displays the Cisco Unified Communications Manager server for this software conference bridge.
Conference Bridge Name
This field automatically displays the software conference bridge name. The format of the name specifies CFB_ followed by a digit that represents the value of the software conference bridge; for example, CFB_3 represents the third conference bridge in the Cisco Unified Communications Manager system.
Description
This field automatically displays a description, but the administrator can update this field.
Device Pool
Choose a device pool that has the highest priority within the Cisco Unified Communications Manager group that you are using or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Additional Information
See the "Related Topics" section.
Hardware Conference Bridge Configuration Settings
Conference Bridge for Cisco Unified Communications Manager, a software or hardware application, allows both ad hoc and meet-me voice conferencing. Each conference bridge can host several simultaneous, multiparty conferences.
Be aware that both hardware and software conference bridges can be active at the same time. Software and hardware conference devices differ in the number of streams and the types of codec that they support.
NoteSee the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-2 describes the hardware conference bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-2 Hardware Conference Bridge Configuration Settings
Conference Bridge Type
Choose Cisco Conference Bridge Hardware.
For a description of this type, see the "Conference Bridge Types in Cisco Unified Communications Manager Administration" section of the Cisco Unified Communications Manager System Guide.
MAC Address
Enter a unique device MAC address in this required field. MAC addresses comprise 12 hexadecimal digits (0-9, A-F).
Example
1231123245AB
Description
This field automatically generates from the MAC address that you provide. You can update this field if you choose.
Device Pool
Choose a device pool that has the highest priority within the Cisco Unified Communications Manager group that you are using or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Special Load Information
Enter any special load information or leave blank to use default.
Additional Information
See the "Related Topics" section.
Cisco IOS Conference Bridge Configuration Settings
Conference Bridge for Cisco Unified Communications Manager, a software or hardware application, allows both ad hoc and meet-me voice conferencing. Each conference bridge can host several simultaneous, multiparty conferences.
Be aware that both hardware and software conference bridges can be active at the same time. Software and hardware conference devices differ in the number of streams and the types of codec that they support.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-3 describes the Cisco IOS conference bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-3 Cisco IOS Conference Bridge Configuration Settings
Conference Bridge Type
Choose Cisco IOS Conference Bridge or Cisco IOS Enhanced Conference Bridge.
For a description of these types, see the "Conference Bridge Types in Cisco Unified Communications Manager Administration" section of the Cisco Unified Communications Manager System Guide.
Conference Bridge Name
Enter the same name that exists in the gateway Command Line Interface (CLI).
You can enter up to 15 characters. Valid characters comprise alphanumeric characters (a-z, A-Z, 0-9), as well as dot (.), dash (-),and underscore (_).
Description
This field automatically generates from the conference bridge name that you provide. You can update this field if you choose.
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Device Security Mode
This field displays for Cisco IOS Enhanced Conference Bridge only.
If you choose Non Secure Conference Bridge, the nonsecure conference establishes a TCP port connection to Cisco Unified Communications Manager on port 2000.
TipThe Encrypted Conference Bridge setting supports the secure conference feature. See the Cisco Unified Communications Manager Security Guide for secure conference bridge configuration procedures.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Additional Information
See the "Related Topics" section.
Cisco Video Conference Bridge Configuration Settings
Conference Bridge for Cisco Unified Communications Manager, a software or hardware application, allows both ad hoc and meet-me voice conferencing. Each conference bridge can host several simultaneous, multiparty conferences.
Be aware that both hardware and software conference bridges can be active at the same time. Software and hardware conference devices differ in the number of streams and the types of codec that they support.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-4 describes the Cisco video conference bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-4 Cisco Video Conference Bridge Configuration Settings
Conference Bridge Type
Choose Cisco Video Conference Bridge (IPVC-35xx).
For a description of this type, see "Conference Bridge Types in Cisco Unified Communications Manager Administration" in the Cisco Unified Communications Manager System Guide.
MAC Address
Enter a unique device MAC address in this required field. MAC addresses comprise 12 hexadecimal digits (0-9, A-F).
Example
1231123245AB
Description
This field automatically generates from the conference bridge name that you provide. You can update this field if you choose.
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Model-specific configuration fields that the device manufacturer defines
The device manufacturer specifies the model-specific fields under product-specific configuration. Because they are dynamically configured, they can change without notice.
To view field descriptions and help for product-specific configuration items, click the "?" information icon under the Product Specific Configuration heading to display help in a popup dialog box.
If you need more information, see the documentation for the specific device that you are configuring or contact the manufacturer.
Additional Information
See the "Related Topics" section.
Cisco Conference Bridge (WS-SVC-CMM) Configuration Settings
Conference Bridge for Cisco Unified Communications Manager, a software or hardware application, allows both ad hoc and meet-me voice conferencing. Each conference bridge can host several simultaneous, multiparty conferences.
Be aware that both hardware and software conference bridges can be active at the same time. Software and hardware conference devices differ in the number of streams and the types of codec that they support.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-5 describes the Cisco Conference Bridge (WS-SVC-CMM) configuration settings. For related procedures, see the "Related Topics" section.
Table 51-5 Cisco Conference Bridge (WS-SVC-CMM) Configuration Settings
Conference Bridge Type
Choose Cisco Conference Bridge (WS-SVC-CMM).
For a description of this type, see "Conference Bridge Types in Cisco Unified Communications Manager Administration" in the Cisco Unified Communications Manager System Guide.
Description
Enter a description (up to 50 characters) or leave blank to generate automatically from the MAC address that you provide. Invalid characters comprise quotes ("), angle brackets (<>), backslash (), ampersand,(&), and percent sign (%).
MAC Address
Enter a unique device MAC address in this required field. MAC addresses comprise 12 hexadecimal digits (0-9, A-F).
Example
1231123245AB
Subunit
From the drop-down list box, choose the value for the daughter card for a given slot on the Communication Media Module card.
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See the "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Maximum Capacity
Choose the maximum number of streams for a given service on a daughter card. Possible values include 32, 64, 96, and 128 streams. Ensure that each daughter card has as many ports as the value that you choose.
Model-specific configuration fields that the device manufacturer defines
To view field descriptions and help for product-specific configuration items, click the "?" information icon under the Product Specific Configuration heading to display help in a popup dialog box.
If you need more information, see the documentation for the specific device that you are configuring or contact the manufacturer.
Cisco IOS Heterogeneous Video Conference Bridge Configuration Settings
Cisco Integrated Services Routers Generation 2 (ISR G2) can act as IOS-based conference bridges that support ad hoc and meet-me video conferencing. DSP modules must be installed on the router to enable the router as a conference bridge.
Cisco IOS Heterogeneous Video Conference Bridge specifies the IOS-based conference bridge type that supports heterogeneous video conferences. In a heterogeneous video conference, all the conference participants connect to the conference bridge with phones that use different video format attributes. In heterogeneous conferences, transcoding and transsizing features are required from the DSP to convert the signal between the various formats.
For heterogeneous video conferences, callers connect to the conference as audio participants under either of the following conditions:
•
•
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-6 describes the Cisco IOS Heterogeneous Video Conference Bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-6 Cisco IOS Heterogeneous Video Conference Bridge Settings
Conference Bridge Name
Enter a name for your conference bridge.
Description
Enter a description for your conference bridge
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use location to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint.
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See the "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Cisco IOS Guaranteed Audio Video Conference Bridge Configuration Settings
Cisco Integrated Services Routers Generation 2 (ISR G2) can act as IOS-based conference bridges that support ad hoc and meet-me voice and video conferencing. DSP modules must be installed on the router to enable the router as a conference bridge.
Cisco IOS Guaranteed Audio Video Conference Bridge specifies the IOS-based video conference bridge type where DSP resources are reserved for the audio portion of the conference, and video service is not guaranteed. Callers on video phones may have video service if DSP resources are available at the start of the conference. Otherwise, the callers connect to the conference as audio participants.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-7 describes the Cisco IOS Heterogeneous Video Conference Bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-7 Cisco IOS Guaranteed Audio Video Conference Bridge Settings
Conference Bridge Name
Enter a name for your conference bridge
Description
Enter a description for your conference bridge
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use location to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint.
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See the "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Cisco IOS Homogeneous Video Conference Bridge Configuration Settings
Cisco Integrated Services Routers Generation 2 (ISR G2) can act as IOS-based conference bridges that support ad hoc and meet-me video conferencing. DSP modules must be installed on the router to enable the router as a conference bridge.
Cisco IOS Homogeneous Video Conference Bridge specifies the IOS-based conference bridge type that supports homogeneous video conferences. A homogeneous video conference is a video conference in which all participants connect using the same video format attributes. All the video phones support the same video format and the conference bridge sends the same data stream format to all the video participants.
If the conference bridge is not configured to support the video format of a phone, the caller on that phone connects to the conference as an audio only participant.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-8 describes the Cisco IOS Homogeneous Video Conference Bridge configuration settings. For related procedures, see the "Related Topics" section.
Table 51-8 Cisco IOS Homogeneous Video Conference Bridge Settings
Conference Bridge Name
Enter a name for your conference bridge.
Description
Enter a description for your conference bridge
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use location to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint.
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See the "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
Cisco TelePresence MCU Configuration Settings
Cisco TelePresence MCU refers to 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 trans-coding, 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.
See the "Conference Bridges" chapter of the Cisco Unified Communications Manager System Guide for more information about conference bridges.
Table 51-9 describes the Cisco TelePresence MCU configuration settings. For related procedures, see the "Related Topics" section.
Table 51-9 Cisco TelePresence MCU Configuration Settings
Conference Bridge Name
Enter a name for your conference bridge
Destination Address
Enter the IP Address of the Cisco TelePresence MCU conference bridge
Description
Enter a description for your conference bridge
Device Pool
Choose a device pool or choose Default.
Common Device Configuration
Choose the common device configuration to assign to the conference bridge. The common device configuration includes attributes, such as MOH audio source, that support features and services for phone users.
Device configurations that are configured in the Common Device Configuration window display in the drop-down list. See Common Device Configuration for more information.
Location
Use location to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location for this conference bridge.
A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this conference bridge consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP.
To configure a new location, use the System > Location menu option.
For more details about locations, see the "Location Configuration" section. For an explanation of location-based CAC across intercluster trunks, see "Location-Based Call Admission Control Over Intercluster Trunk" in the Cisco Unified Communications Manager System Guide.
Use Trusted Relay Point
From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint.
•
•
•
A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. See the "TRP Insertion in Cisco Unified Communications Manager" in the Cisco Unified Communications Manager System Guide for details of call behavior.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP.
See "Trusted Relay Point" and its subtopics in the "Media Resource Management" chapter of the Cisco Unified Communications Manager System Guide for a complete discussion of network virtualization and trusted relay points.
SIP Interface Info
Unified CM SIP Port
This is the SIP listening port of Cisco Unified Communications Manager. The default value is 5060.
MCU Conference Bridge SIP Port
This is the SIP listening port of the Cisco TelePresence MCU Conference Bridge. The default value is 5060.
HTTP Interface Info
Username
Enter the Cisco TelePresence MCU administrator username.
Password
Enter the Cisco TelePresence MCU administrator password.
Confirm Password
Enter the Cisco TelePresence MCU administrator password
HTTP Port
Enter the Cisco TelePresence MCU HTTP port. The default port is 80.
NoteSynchronizing a Conference Device
To synchronize a conference device with the most recent configuration changes, perform the following procedure, which applies any outstanding configuration settings in the least-intrusive manner possible. (For example, a reset/restart may not be required on some affected devices.)
Procedure
Step 1
The Find and List Conference Bridges window displays.
Step 2
Step 3
The window displays a list of conference bridges that match the search criteria.
Step 4
Step 5
The Apply Configuration Information dialog displays.
Step 6
Additional Information
See the "Related Topics" section.
Related Topics
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Other Information
•
•
•
