Table Of Contents
Configuring Basic Settings for the Cisco Unified Videoconferencing 3515 MCU
About Status Information for the Cisco Unified Videoconferencing 3515 MCU
How to Configure Settings for the 3515 MCU
Setting the User Interface Language
Setting the Unit Identifier
Enabling and Disabling High Definition Continuous Presence
Setting an Operator Number
Dialing Directly to the MCU
Configuring DTMF Control
Configuring Themes
Configuring Quality of Service
Configuring MCU Dynamic Layouts
How to Configure MCU Alert Indications
Enabling Cisco Unified Videoconferencing 3515 MCU Alert Indications and Setting Security Levels
Configuring SNMP Trap Servers
Editing SNMP Trap Servers
Deleting SNMP Trap Servers
Media Processor Information for the 3515 MCU
Event Log Information for the 3515 MCU
Saving Configuration Settings for the 3515 MCU
Importing Configuration Settings for the 3515 MCU
Configuring Basic Settings for the Cisco Unified Videoconferencing 3515 MCU
•
About Status Information for the Cisco Unified Videoconferencing 3515 MCU
•How to Configure Settings for the 3515 MCU
•How to Configure MCU Alert Indications
•Media Processor Information for the 3515 MCU
•Event Log Information for the 3515 MCU
•Saving Configuration Settings for the 3515 MCU
•Importing Configuration Settings for the 3515 MCU
About Status Information for the Cisco Unified Videoconferencing 3515 MCU
The Status tab in the MCU interface displays information about MCU resource usage and performance. Table 2-1 lists the information in the Status tab.
Table 2-1 Status Tab Sections
Section Name
|
Description
|
Status
|
Indicates the current operational state of the Cisco Unified Videoconferencing 3515 MCU as follows:
•OK—Indicates at least one of these states:
–The Cisco Unified Videoconferencing 3515 MCU is registered to a gatekeeper.
–The auto-attendant feature is enabled and the Cisco Unified Videoconferencing 3515 MCU is not configured to use a gatekeeper.
•Error—Indicates at least one of these states:
–TheCisco Unified Videoconferencing 3515 MCU is configured to use a gatekeeper, but is not connected to a gatekeeper.
–No gatekeeper or auto-attendant setting is configured.
|
Resource Meter
|
•CPU Usage (%) field—Indicates the percentage of MCU resources currently occupied. We recommend that this value not exceed 90 percent.
|
Conferences
|
•Number of active conferences—Indicates the number of conferences currently hosted on the MCU.
•Number of calls—Indicates the current number of calls on the MCU.
|
How to Configure Settings for the 3515 MCU
•Setting the User Interface Language
•Setting the Unit Identifier
•Setting an Operator Number
•Dialing Directly to the MCU
•Configuring DTMF Control
•Configuring Themes
•Configuring Quality of Service
•Configuring MCU Dynamic Layouts
•How to Configure MCU Alert Indications
•Enabling and Disabling High Definition Continuous Presence
Setting the User Interface Language
In the Basics section of the Settings tab, you can configure the language that the MCU supports. Table 2-2 lists the languages that the MCU supports.
Table 2-2 Supported Languages in the MCU User Interface
Language
|
Administrator Interface
|
Conference Control Interface
|
Text Overlay on Conference Video
|
English
|
*
|
*
|
*
|
Chinese
|
*
|
*
|
*
|
Japanese
|
*
|
*
|
|
Portuguese
|
*
|
*
|
*
|
Spanish
|
*
|
*
|
*
|
Russian
|
*
|
*
|
*
|
Note To view Chinese or Japanese fonts properly in the Administrator interface, the computer (where the web browser is running) should support the appropriate languages. You should set its default language (which you select from the Control Panel > Regional and Language Options menu) accordingly.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Basics.
Step 4 In the User interface language field, select the required language.
Setting the Unit Identifier
In the Basics section of the Settings tab, you can set the Cisco Unified Videoconferencing 3515 MCU identifier. This identifies the MCU in these situations:
•During gatekeeper/SIP registration.
•When inviting endpoints—When inviting endpoints into a conference.
•In text the overlay for the cascaded MCU in cascaded conferences.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Basics (if not already selected).
Step 4 In the MCU Identifier field, enter an identifier (up to a maximum of 15 characters). For example, "London office."
Enabling and Disabling High Definition Continuous Presence
Restrictions
When you enable High Definition Continuous Presence (HDCP) on the Cisco Unified Videoconferencing 3515 MCU24, each EMP registered to the MCU automatically reserves 8 ports for HDCP from its available total of 24 ports.
When HDCP is enabled, only 12 ports are left available for SCCP partitioning on the first EMP. When SCCP port "spanning" over all EMPs is required, select the SCCP "All" formatting option. This option disables all non-SCCP protocols including HDCP functionality.
HDCP is disabled by default. After enabling it, you must change service prefix 81 to 720p resolution. Enabling HDCP alone results in the service limiting the resolution to 4CIF.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Basics (if not already selected).
Step 4 In the General section, select or deselect the Enable High Definition Continuous Presence check box.
Step 5 Reset for changes to take effect.
Setting an Operator Number
During a conference, you can invite an Operator to join and provide consultation and support.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Basics.
Step 4 In the pre-defined endpoints section, in the Operator field, enter an E.164 number for the operator.
Dialing Directly to the MCU
You can allow users to dial directly to the MCU IP address via the "auto-attendant" mechanism without the need to register to an H.323 gatekeeper or SIP registrar.
Users specify the conference they want to create or join via the MCU IVR.
If the MCU is already registered to an H.323 gatekeeper or SIP registrar, you can still allow users to access the auto-attendant mechanism by specifying an auto-attendant number which is registered with the appropriate H.323 gatekeeper or SIP registrar. Any call that the MCU cannot route to a valid conference is sent to the auto-attendant.
Procedure
Step 1 In the Administrator interface, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Auto Attendant to enable the auto-attendant mechanism.
Enabled by default.
Step 4 (Optional) Select Enable Auto Attendant (IVR) and configure an auto-attendant number.
Step 5 Use this option if the MCU is already registered to an H.323 gatekeeper or SIP registrar.
Step 6 (Optional) Select a language from the Auto Attendant Display Messages field.
Burn extended fonts for additional languages on to the MCU during installation.
Step 7 (Optional) Select a default service prefix from the drop-down list for use when the user does not specify a valid service prefix when joining or creating a conference. Set to the default high rate service by default.
Configuring DTMF Control
In the Conference Control section of the Settings tab, you can activate Dual Tone Multi-Frequency (DTMF) and H.243 conference control. DTMF and H.243 conference control allow you to perform these actions on a conference from the remote control or keypad of your endpoint:
•Moderate conference
•Mute or unmute your line
•Control your volume
•Block or unblock admission to a conference (users only)
•Invite new participants (users only)
Procedure
Step 1 In the Administrator interface, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Conference Control.
Step 4 Select Enable DTMF Conference control.
Step 5 In the DTMF Conference Control prefix field, choose a symbol for starting the DTMF conference control session. You can select pound (#) or asterisk (*). The default is *.
Step 6 Select Enable H.243 Conference control.
Configuring Themes
In the Themes section of the Settings tab, you can preview pre-configured video display settings and configure custom themes. You select theme options when configuring services. You can configure a custom theme specifying the text font, color, background color, and border settings for active participants.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Themes.
Step 4 Select one of the themes from the Theme field.
If you select Classic, you can configure the font size, subframe and border color. Follow step 5 to step 10.
If you select Modern, you can configure the font size only. Go to step 6 and then jump to step 10.
If you select any other theme, the font size, subframe and border color are automatically set. Go to step 10.
Step 5 In the Font background transparency field, choose one of the following settings:
•None—A solid background against which the text appears.
•Half—A moderate background against which the text appears.
•Full—A transparent background against which the text appears.
Step 6 In the Font size field, choose a font size:
Step 7 In the Font foreground color, Font background color and Empty subframe color fields, click to select a color for these settings.
Step 8 (Optional) Select Display default border and click to select the default border color.
Step 9 Select Display active speaker border to set a default border for the active speaker.
Step 10 For the Basic font field, select Enable extended Font to enable Asian fonts. By default, this field displays the font currently installed on the MCU
You can view the effects of your settings in the Preview section. This section displays the selected theme settings. This includes a layout with four sub-frames, the theme border highlight colors, active speaker border highlight color, font formatting, screen background color, and text background settings.
Configuring Quality of Service
You can assign a Quality of Service (QoS) priority level to video and voice calls using either pre-configured system settings or by creating your own settings.
Quality of Service settings involve configuring the MCU to add a QoS DiffServ Code Point value in the IP header of outbound packets. Routers on the network that support QoS can give preferential treatment for bandwidth, latency and jitter to such coded packets and facilitate the efficient transmission of packets. You can set QoS parameters on the MCU for voice calls, video calls or both.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Quality of Service.
Step 4 In the Quality of service support field, set the required DiffServ Code Point value for each media type by clicking one of these radio buttons:
•None—Select to disable Quality of Service support
•Default—Select to assign the default DiffServ Code Point value for each media type. The default settings represent Cisco recommendations.
•Custom—Select to assign your own DiffServ Code Point value for each media type.
If you select Default, the system automatically enters Quality of Service settings. If you select Custom, follow the steps below.
Step 5 In the Voice Priority field of the Video Calls section, enter a whole number from 0 to 63 to set the DiffServ Code Point value of voice packets that the MCU sends out. The default value is 34.
Step 6 In the Video Priority field of the Video Calls section, enter a whole number from 0 to 63 to set the DiffServ Code Point value of video packets that the MCU sends out. The default value is 34.
Step 7 In the Voice Priority field of the Voice Calls section, enter a whole number from 0 to 63 to set the DiffServ Code Point value of voice packets that the MCU sends out. The default value is 46.
Configuring MCU Dynamic Layouts
In the Dynamic Layouts section of the Settings tab you can define the exact layout transition order used by conferences.
Dynamic layouts are activated individually for each service. When selected, the conference layout changes automatically as participants join or leave.
Procedure
Step 1 In the Administrator interface, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Dynamic Layouts.
Step 4 Click a layout image to select or deselect that specific layout.
How to Configure MCU Alert Indications
•Enabling Cisco Unified Videoconferencing 3515 MCU Alert Indications and Setting Security Levels
•Configuring SNMP Trap Servers
•Editing SNMP Trap Servers
•Deleting SNMP Trap Servers
Enabling Cisco Unified Videoconferencing 3515 MCU Alert Indications and Setting Security Levels
In the Alert Indications section of the Settings tab, you can select which events trigger Simple Network Management Protocol (SNMP) traps. You can also define multiple SNMP servers to which the MCU sends the SNMP traps and configure which events to display in the Event Log tab.
In the Alert Indications section of the Settings tab, you can configure which alerts will be enabled and set a severity level for each one.
Table 2-3 lists alert indications as well as the SNMP trap associated with them.
Table 2-4 lists the structure of the standard coldStart and warmStart traps (as defined in RFC 1907) and the standard linkDown and linkUp traps (as defined in RFC 1573).
Table 2-3 MCU Alert Indications
Event Type
|
Trap is sent when...
|
Abnormal disconnect
|
A call disconnects for a reason other than normal, busy, or no answer.
|
Authentication failure
|
The conference PIN is incorrect.
|
Call disconnected by remote endpoint
|
A call disconnects normally by a remote endpoint.
|
Corrupt WEB data
|
Corrupt web files are present in the MCU.
|
Gatekeeper registration state change
|
A change occurs in the registration status of the MCU with the gatekeeper.
|
General alarm
|
A system failure is detected.
|
Incompatible software version install
|
An attempt to burn a version of the MCU software onto incompatible hardware occurs.
|
Loss of Ethernet
|
The network returns after going down. Indicates the time at which the network was restored.
|
MP lost
|
Communication with a registered media processor has broken.
|
MP registration failure
|
The media processor registration to the MCU failed.
|
Max resource meter
|
A high CPU level (85%) is reached in the MCU.
|
Network problem
|
A problem occurs on the network.
|
Overheating
|
The configured temperature thresholds for the device are exceeded. Overheating can cause serious damage to the functioning of the device.
|
Power-down
|
The MCU is shutting down.
|
Power-up
|
The MCU has begun operation.
|
Services table is changed
|
The service table has been modified.
|
Table 2-4 Standard SNMP Trap Event Types
Event Type
|
Trap is sent when...
|
Cold start
|
The MCU has been reset using the button on the front panel.
|
Warm start
|
A reset of the MCU has been performed using the Administrator interface.
|
Link down
|
Standard SNMP MIB trap indicating that the network connection is down with details about the cause and time of connection loss.
|
Link up
|
Standard SNMP MIB trap indicating that the network connection has been reestablished.
|
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Alert Indications.
Step 4 In the Events section, select the check boxes in the Enabled in the Event Log column for all the events that you want to display in the event log.
Step 5 For each event you enable, choose one of the following severities in the Severity column:
•Cleared—Enumeration 0. One or more previously reported alarms have been cleared.
•Information—Enumeration 1. Notification of a non-erroneous event.
•Critical—Enumeration 2. A service-affecting event has occurred and requires immediate corrective action.
•Major—Enumeration 3. A service-affecting event has occurred and requires corrective action to prevent the condition becoming more serious.
•Minor—Enumeration 4. A non-service-affecting event has occurred and requires corrective action to prevent the condition becoming more serious.
•
•Warning—Enumeration 5. A potential or impending service-affecting event has been detected, but no significant events have occurred yet. Action should be taken to further diagnose and correct the problems to prevent the condition becoming more serious.
Tip You can click Select All to select all events or Clear All to clear all events.
Configuring SNMP Trap Servers
In the Alert Indications section of the Settings tab, you can define the IP address, port, and enabled traps for multiple SNMP trap servers to which the MCU sends the SNMP traps, and specify which events to display in the Event Log tab.
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Alert Indications.
Step 4 In the SNMP Traps Server section, click Add.
The SNMP Trap Servers Properties dialog box appears.
Step 5 In the SNMP Trap server address field, enter the address for the SNMP trap server.
Step 6 In the Port field, enter the port of the SNMP trap server. The default port for SNMP servers is 162.
Step 7 In the Enabled traps section, select which traps you want to enable:
•To disable a trap, click it in the Enabled traps area and then click Remove.
•To enable a trap, click it in the Disabled traps area and then click Add.
•To enable all traps, click Add All.
•To disable all traps, click Remove All.
Step 8 Click Upload to save your settings.
The configured SNMP trap server appears in the SNMP Trap Servers section.
Editing SNMP Trap Servers
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Alert Indications.
Step 4 In the SNMP Trap Servers section, click the configured SNMP trap server and then click Edit.
Step 5 Click Upload when you finish your edits.
Deleting SNMP Trap Servers
Procedure
Step 1 In the Administrator interface, on the sidebar, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click Alert Indications.
Step 4 In the SNMP Trap Servers section, click the configured SNMP trap server and then click Delete.
Media Processor Information for the 3515 MCU
In the Media Processing tab, you can view the list of data and video processors and servers currently registered with the MCU and access the web interface (if available) of registered devices to modify settings. The Media Processing tab includes these columns and fields:
•Type—This column displays the types of media processors registered with the current MCU. The following types can appear in this column:
MCU—The MCU itself which is responsible for the signaling (H.323/SIP) and audio portions of a call.
EMP—The video processor responsible for the video portion of a call.
•IP Address—This column displays the IP address of the device on which the media processor operates.
•Description—This column displays a user-defined description of the media processor.
•Total—This field displays the total number of media processor units currently registered.
Event Log Information for the 3515 MCU
The Event Log tab displays a list of reported alarm events. These events are configured in the Alert Indications section of the Settings tab.
The Event Log tab displays this information:
•Event ID—Displays the identifier for the specified alarm event.
•Type—Displays the type of event.
•Time—Displays the date and time when the reported event occurred.
•Severity—Displays the severity of the reported event.
•Message—Displays the error message used to report the event
Saving Configuration Settings for the 3515 MCU
You can save MCU configuration settings to a file and then export this file to a storage device on your network. You can use the saved configuration file to restore the settings to the current MCU or to configure a similar MCU.
An exported configuration file saves most of the current Device section settings and all of the current MCU section settings.
You must use the Export button on the toolbar to save the configuration settings to a file. The Export button appears only when MCU section settings are activated. When you save a configuration file, the current Device section settings are saved in the file. If you want to change these settings for export, click Upload on the toolbar to save these settings to configuration memory prior to saving the configuration file.
Procedure
Step 1 In the MCU interface, on the sidebar, click Device.
Step 2 Make sure that the settings in the Basics, Addressing, Web and Users tabs are correct.
Note Date parameters are not saved to the configuration file.
Step 3 Click Upload to save these settings.
Step 4 On the sidebar, click MCU.
Step 5 Review each of the configuration pages to ensure that these are the configuration settings you want to save.
Step 6 Click Upload to save these settings.
Step 7 On the toolbar, click Export.
Note A dialog box appears indicating that you are navigating away from the page without saving the changes. Select the option to continue.
The File Download dialog box appears.
Step 8 Save the configuration settings file to your chosen location. The file extension .ini is automatically appended to the file name.
Importing Configuration Settings for the 3515 MCU
You can import the settings of a saved MCU configuration file from a storage device on your network. You can use the saved configuration file to restore the settings to the current MCU or to configure another MCU.
Procedure
Step 1 In the MCU interface, on the sidebar, click MCU.
Step 2 On the toolbar, click Import.
The Import a Configuration File page appears.
Step 3 Click Browse.
The Choose file dialog box appears.
Step 4 Navigate to and select the configuration file you want to import.
Note The file must have an .ini extension.
Step 5 Click Open.
The file path appears in the File Name field.
Step 6 Click Import.
Note You can verify the settings by clicking MCU or Device on the sidebar. However, to save the settings in either section, you must click Upload to save them before viewing the next section.
Step 7 Click Upload to save the settings in configuration memory.
Note Uploading the file resets the device.
