Table Of Contents
Advanced Configuration for the Cisco Unified Videoconferencing 3515 MCU
Configuring Conference Management Settings for the 3515 MCU
Configuring Delimiter Settings for the 3515 MCU
Disconnecting Participants on Communications (ICMP) Failure for the 3515 MCU
Sending Advanced Commands for the 3515 MCU
Opening a Telnet Terminal for the 3515 MCU
Advanced Configuration for the Cisco Unified Videoconferencing 3515 MCU
This section describes the following topics:
•
Configuring Conference Management Settings for the 3515 MCU
•Configuring Delimiter Settings for the 3515 MCU
•Disconnecting Participants on Communications (ICMP) Failure for the 3515 MCU
•Sending Advanced Commands for the 3515 MCU
•Opening a Telnet Terminal for the 3515 MCU
Configuring Conference Management Settings for the 3515 MCU
In the Advanced section of the Settings tab, you can configure settings for conference registration with the gatekeeper and determine how participants can create and join 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 the Advanced button.
Step 4 Select Register conference ID to register existing conference IDs with the gatekeeper and SIP server to enable participants dialing in to a conference from remote locations to connect to the target conference on the MCU. This setting is deselected by default.
Note When working with SIP, you must configure a registrar.
Step 5 In the Conferences can be created using field, choose one of the following methods through which conferences can be created:
–Scheduler only—Enables conference creation only using a conference scheduling application
–Scheduler, Web and Control API—Enables conference creation using a conference scheduling application, the Conference Control interface, or an external application that uses the MCU API.
–Scheduler, Web, Control API and dial-in (default)—Enable all the conference creation methods listed above, as well as dial-in for ad-hoc conference creation.
Step 6 Select When using the web, only operators or administrators can create a conference to grant conference creation authorization only to users with Administrator or Operator privileges. If you want users with all levels of access to be able to create a conference, leave this option deselected.
Step 7 In the Participants can join the conference using field, choose one of the following methods through which participants can join a conference:
–Invite only—Participants can join a conference only when the MCU dials that participant.
–Invite and dial-in—Participants can join a conference either by MCU invitation or by dialing directly using a conference ID.
Step 8 In the Ad hoc conferences terminate when field, choose the method through which dial-in (ad hoc) conferences terminate:
–Last participant leaves—The conference terminates when the last participant leaves the conference.
–Conference creator leaves—The conference terminates when the conference creator leaves the conference.
Step 9 In the External conference authorization policy field, choose one of the following MCU authorization policies for creating or joining conferences:
–None—No authorization required.
–Notify—The MCU notifies an external application such as a conference scheduler that accesses or controls MCU resources about conference creation or joining.
–Authorize—The MCU requests authorization from an external application such as a conference scheduler which accesses or controls MCU resources to create conferences or allow participants to join conferences.
Configuring Delimiter Settings for the 3515 MCU
You can specify a conference PIN or invite multiple participants as part of the string for dialing into the MCU.
In the Advanced section of the Settings tab, you can configure the conference PIN delimiter and the multiple invite delimiter.
Procedure
Step 1 In the Administrator interface, click MCU (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Advanced button.
Step 4 In the PIN delimiter field, enter the characters used as a separator between the conference ID and conference PIN when dialing into a conference. A conference is created with this PIN if no conferences already exist with the specified number. Valid delimiters include the pound sign (#) and asterisk (*). The default PIN delimiter setting is three asterisks (***).
Step 5 In the Invite delimiter field, enter the characters used to separate participant numbers in multiple participant invitation. Valid delimiters include the pound sign (#) and asterisk (*). The default invite delimiter setting is two asterisks (**).
Disconnecting Participants on Communications (ICMP) Failure for the 3515 MCU
When the MCU sends audio or video data to an unreachable endpoint, the network notifies the MCU using the ICMP protocol. The MCU can detect ICMP messages and disconnect the endpoint automatically. You enable automatic endpoint disconnection in the Advanced section of the Settings tab.
If this option is not selected, the MCU ignores ICMP error packets.
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 the Advanced button.
Step 4 Select Disconnect participants on communication (ICMP) failure.
Step 5 In the Disconnect on field, make one of the following sections:
–Audio failure—The call disconnects only if the audio connection fails. The call continues if the video connection fails and the audio connection remains. This is the default setting.
–Audio or video failure—The call disconnects if either the audio or video connection fails.
Sending Advanced Commands for the 3515 MCU
In the Advanced section of the Settings tab, you can send text-based commands used for the enhanced control of the MCU. Advanced commands are not case-sensitive.
Note We recommend that only advanced users or users who have consulted with Cisco Customer Support perform actions involving advanced commands.
Table 3-1 lists all available advanced commands.
Table 3-1 List of Available Advanced Commands
Command
|
Description
|
Parameters
|
Default
|
Conference control Web refresh interval
|
Indicates the length of time (in seconds) after which the Conference Control interface refreshes automatically.
|
|
10
|
DTMF forwarding
|
Indicates the target of DTMF forwarding.
|
to all—All endpoints in the conference.
to gateways—To gateways only.
to none—DTMF is disabled.
|
none
|
Enable in-band DTMF detection
|
Enables support for in-band DTMF signaling.
|
Always or
Only during IVR
|
Always
|
First audio announcement interval (msec)
|
Indicates the length of time (in milliseconds) between the start of the conference and the first audio announcement.
|
|
Disabled
|
Font align
|
Determines whether text overlay (TOL) on a video screen is positioned away from picture borders.
|
All—Text positioned away from horizontal and vertical borders.
Horizontal—Text positioned away from horizontal borders and centered horizontally.
Vertical—Text positioned away from vertical borders and centered vertically.
None—Text is always positioned bottom center.
|
All
|
G.728 mode
|
Determines the form of encoding for the G.728 audio codec RTP header.
|
Non-standard—For use if you experience audio problems when using VCON endpoints with the G.728 audio codec.
Standard—For normal G.728 use with all endpoints except VCON products.
|
|
H323 hide stack
|
Disables H.323 stack prints.
|
|
H.323 Stack printing is disabled by default.
|
H323 show stack
|
Enables H.323 stack prints. These print the protocol stack info and errors and are useful for debugging stack issues
|
|
H323 show status
|
Prints a snapshot of H.323 stack-related information.
|
|
|
Handle DTMF after XML notification
|
Instructs the MCU to send DTMF signals to an external server and other specified destinations.
|
no—MCU sends DTMF signals to the external server only.
yes—MCU sends DTMF signals to the external server and to the destination set by the DTMF forwarding advanced command.
|
|
NTP synchronization period
|
Sets the Network Time Protocol synchronization period (in seconds) between the EMP and the NTP server.
|
|
21600
|
Notify level
|
Sets the MCU log notify level filter
|
Fatal—MCU cannot continue to provide service (unrecoverable error).
Error—User functionality problem (for example, call connect failure or no resources available).
Warning—User functionality problem but the MCU can continue to provide service.
Info—Status prints for Customer Support use.
Advanced—Like Info but more detailed.
Debug 1 through Debug 4—Debug levels.
|
Debug 3
|
QualiVision Settings hide
|
Disables the QualiVision Settings section in the Settings tab.
|
|
The QualiVision Settings section is hidden by default.
|
QualiVision Settings show
|
Enables the QualiVision Settings section in the Settings tab.
|
|
SCCP hide stack
|
Disables SCCP stack prints.
|
|
|
SCCP show status
|
Prints a snapshot of SCCP stack related information.
|
|
|
Set MTU size
|
Determines the maximum packet size across the network.
|
|
1500
|
Set terminal baud rate
|
Sets the baud rate of a serial terminal.
|
High (57600)
Low (9600)
|
Low (9600)
|
Support RFC 2833 capability
|
Enables support for in-band DTMF signaling via packets within the audio channel as defined in the RFC 2833 standard.
|
disable or enable
|
enable
|
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 the Advanced button.
Step 4 Click Commands.
The Advanced Commands dialog box appears.
Step 5 In the Command field, enter a command or choose one from the Available Commands field.
Step 6 In the Parameters field, enter a parameter value for the command (where applicable) or choose one from the Available Parameters field.
Step 7 Click Send.
The results of the advanced command appear in the Response field, indicating whether or not the MCU received and executed the command. If you send an invalid command, a "bad parameter" or "NOT FOUND" message appears.
Opening a Telnet Terminal for the 3515 MCU
In the Advanced section of the Settings tab, you can open a Telnet terminal to log error and troubleshooting information.
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 the Advanced button.
Step 4 Click Telnet.
Step 5 A separate browser opens with a Telnet terminal. When you finish with your Telnet session, click Disconnect.
