Codian MCU 4500 Series Codian MSE 8510 Series Online help (printable format) Software version 2.
TANDBERG Philip Pedersens vei 20 1366 Lysaker Norway Telephone: +47 67 125 125 Telefax: +47 67 125 234 Video: +47 67 117 777 E-mail: tandberg@tandberg.
1
2
3
4
5
The Codian MCU web interface is used for administering the MCU device, managing conferences, users, and predefined endpoints. You can also perform many conference-related tasks using the web interface that you cannot otherwise do. When connecting to the Codian MCU web interface, you must log in so that the MCU can associate the session with your configured user and a set of access privileges. The MCU has a set of configured users, and each user has an ID and password that are used for logging in. 1.
Depending on how your system administrator has configured the MCU and conferences on it, you might be able to join conferences by simply dialing a phone number. Your system administrator may have configured the MCU to allow you to use your video endpoint to directly dial the conference by dialing a phone number. You will be required to enter the conference ID, and PIN if required. Or you may be able to dial by IP address and connect to the auto attendant. See Using an auto attendant for details.
Your system administrator may have set up an auto attendant for you to use to join conferences. An auto attendant presents you with a series of menus from which you can choose a conference to join. For further information about accessing conferences (including the use of DTMF tones), refer to the document "Accessing Conferences", available in the Documentation area of the web site. There are typically two ways to call an auto attendant using your video endpoint.
When in DTMF navigation mode, you will not be able to use the number keys to enter the numeric ID of a conference. Typically, you will have these options: This option enables you to start a new conference that takes place immediately (an "ad hoc" conference). When creating this conference, you'll need to add a conference ID and optional PIN (to restrict access to the conference).
The streaming interface enables you to enter the ID of a conference and view it in a web browser on your PC. You do not have to have a user account on the MCU to be able to do this. If you do need to log in to the MCU, use the link on the top right of the screen. A name by which you will be identified should you use the text chat facility.
The Codian MCU supports streaming, which involves sending conference media (audio and video) to a remote computer, allowing the user to watch and listen to a conference. The media flows in just one direction, so it is not possible to actually contribute to a conference via streaming. The streaming video may be delayed by approximately 4-10 seconds compared to the real-time video. To view an active conference using streaming: 1. Go to and click next to the conference name. 2. Choose the Streaming rate.
After you join a conference, you can control many conference features directly from your video endpoint. (For information about in-conference features using the web interface, see Controlling in-conference features).
You are scrolling up through the layout views. You are scrolling down through the layout views. You have stopped scrolling through the layout views. When viewing a conference with variable-size panes (see Variable-size panes), you can choose which participant to display in the larger panes on the video screen; when viewing a conference with equal-sized panes, you can choose which participant displays in the top left pane. You do this by selecting the participant following these steps: 1. 2. 3. 4.
During the conference, various icons might appear in the pane of specific participants. Refer to the table below for assistance interpreting these icons. This participant has been given priority in the layout views. A participant is made "important" using controls on the MCU web pages. The audio quality from this participant is poor. The audio quality from this participant is good. The video quality from this participant is poor. The video quality from this participant is good.
During the conference, various icons might appear in top left of the conference display. The appearance of these icons is controlled on the page (refer to Configuring global conference settings). Refer to the table below for assistance interpreting these icons. There are both encrypted and unencrypted participants in this conference or there are streaming viewers of this encrypted conference. This conference is being recorded. There are audio-only participants in this conference.
Depending on how your video endpoint is configured, an incoming video call might come through to your regular phone or to your video endpoint (see Calling into conferences for a brief description of the difference). Note that even if a video call arrives on your regular phone, the video portion of the call will appear on your associated video endpoint (if one is configured). As with any other type of incoming call, you can choose to answer the call or not.
The default behavior of the Codian MCU is to display the "loudest" participants in the most prominent layout panes. If there are more contributors than there are panes available, then the "quietest" participants are not shown. However, different styles of layout introduce slight subtleties to this behavior, and in addition there are a few ways in which participants or conference administrators may change the system used for pane assignment.
When considering which participants to show in which panes, a participant's self view has the lowest priority. This has two main implications: When choosing participants to display, the MCU considers the viewer last. This prevents the participant who is the active speaker from seeing only themselves. In this case, while everyone else will see the active speaker, the active speaker will see the previous active speaker in their biggest view pane.
Both "Changing view focus" and "Important participants" above involve a single specific participant being shown in the biggest pane available, even if that participant is not currently the loudest speaker. This causes a potential conflict, which is resolved dependant on the type of layout. In this type of view (a layout in which all panes are of equal size), the focused participant is shown in the first pane, the one at the top left.
The majority of the conference layouts defined by the Codian MCU, for example: have in common that all of their panes, whether big or small, have the same aspect ratio as the view itself. That is, the panes' widths and heights are in the same proportion as the width and height of the encompassing view. By comparison, there are some defined conference layouts, for example: in which this aspect ratio preservation does not occur.
Some H.323 endpoints support a feature known as floor and chair control that is encompassed by the H.243 protocol. This is not currently supported by SIP. The MCU supports the following H.243 features: a participant can "take the floor" in a conference. On "taking the floor" their video contribution is sent to all conference participants as a "1 x 1 view" (full-screen view).
The Conference List displays information about active, scheduled, and completed conferences. To access this list, choose . Review this information for explanations about the details that display: Active conferences Scheduled conferences Completed conferences Active conferences are currently in progress. The following information is displayed for each conference: Displays the conference streaming page.
The status of a conference with respect to its H.323 gatekeeper and/or SIP registration. Depending on the conference settings, there is a maximum of four registrations for each conference: H.323 numeric ID, H.323 guest numeric ID, SIP numeric ID, and SIP guest numeric ID. The Registration field will show failed if any of the registrations has not completed successfully.
ports for a conference (for instance because of a configuration error), this value will display in red as an error indication. When the conference began. If the conference started before today, the date also displays. How long the conference still has to run. If the conference does not have a limited duration, this column displays as . Scheduled conferences are either in progress or are yet to start.
Completed conferences have finished and are not scheduled to repeat. To remove specific conferences from the list, select the conferences via their associated checkboxes and click . To remove all conferences from the list, click . The name of the conference chosen when the conference was scheduled. Click the conference name to display detailed information about the configuration of the conference. The configured owner of the conference. See Conference ownership for additional information.
The information required to add or update a conference is nearly identical. Refer to these topics for details: Adding a conference Updating a conference Adding configured endpoints Using IDs and PINs To add a conference: 1. Go to . 2. Complete the fields referring to the table below for the most appropriate settings for the conference. 3. Click to add the conference and return to the Conference List.
The name that users will see on auto attendant screens and on the MCU's web interface. Conference names must be unique; conferences cannot share names. Only scheduled conferences have a configurable Name; ad hoc conferences do not have one. Additional information about the conference, which can assist users joining conferences. Use the description to provide more detailed information about the conference than the name alone conveys.
enabled on the page), participants can dial in using this number. Note that the actual number that participants will dial depends on whether prefixes are used in the page. For an active ad hoc conference, you cannot configure the Numeric ID. Provides a level of security to conference access. If a conference has a PIN set, users cannot join the conference or change its configuration without entering the correct PIN.
Provides secure access to conferences for guest participants. If a conference has a PIN set, users cannot join the conference or change its configuration without entering the correct PIN. Participants joining as guests have restricted privileges. For more information, refer to Using IDs and PINs. Ad hoc conferences cannot be configured with Guest numeric IDs or PINs. Enables the MCU to attempt to register the Numeric ID and/or Guest numeric ID with the configured H.323 gatekeeper and/or SIP registrar.
Indicates the visibility of the conference on the auto attendant and the web interface. The options are: : the conference will be listed in the auto attendant and be visible to all users of the web interface : the conference will not be listed in any auto attendant except for auto attendants specifically set to show it.
Select to initially mute audio and/or video from all participants when they join the conference. If you select to mute audio on join, when a participant dials-in to a conference, he will not be able to contribute audio to the conference. If you select to mute video on join, when a participant dials-in to a conference, he will not be able to contribute video to the conference. You can mute both audio and video if required.
Whether, by default, endpoints are permitted to contribute the content channel for a conference through the mechanism of opening a content video channel. There can only be one endpoint contributing content video at any one time, and the MCU arbitrates between them. Therefore, even with this parameter set to Enabled, the ability of the endpoint to contribute content video will be affected by other endpoints' behavior.
Sets the conference start time to the current time The current time on the MCU is determined by on the MCU. the settings in the page, which can only be modified by the administrator. See Displaying general status for additional information. Allows you to retain a conference and its settings for an infinite period of time. Limits the duration of the conference for one instance of the conference. These fields are not available or necessary for conferences set to permanent.
all participants are disconnected (default) all participants may continue the conference until the last one disconnects (take no action) If you set both Numeric ID and PIN, you must set either: both Guest numeric ID and Guest PIN or neither Guest numeric ID nor Guest PIN If you use a Guest PIN, you must use a PIN. If you use a Guest numeric ID, you must use a Numeric ID.
Each scheduled conference (i.e. conferences that are configured via the web interface with a start time and, optionally, a duration and repetition) has an associated owner. This owner is the ID of a configured user, and normally corresponds to the user who scheduled the conference. Conference ownership affects only web interface control of conferences - in particular, it plays no part in validating video conferencing endpoints' attempts to join conferences when they connect to the MCU via H.323.
As described above, a user privilege level confers a certain level of control over a conference, with that level of control possibly depending on whether that user is the conference owner or not. These conference control levels have the following meaning: This level of control permits the following operations: With full conference control, a user is able to disconnect participants, connect new participants to the conference, and end the conference whenever they want to.
Participant custom layout, and whether to send widescreen or standard format video to that endpoint. The web interface can be used to send control commands (e.g. pan and tilt) to a remote participant's camera. Waveforms of audio channels being sent to, and received from, the participant can be viewed, audio gain applied, and participant audio can be muted if required. Textual messages can be sent to an individual participant, and will appear on their displays.
The MCU is able, if required, to allocate its available media ports in advance to specific conferences. This means that it is able to guarantee that a certain number of participants will be able to join that conference, irrespective of how many other people are using the MCU for other conferences at the same time. There are three types of media ports available on the MCU, . , , and For information about the number and type of ports provided by each MCU model, refer to MCU port matrix.
How MCU media ports are allocated, and which options and settings are available, is controlled by the Media port reservation setting on the Conference settings page. This is the mode that the unit runs in when the Media port reservation setting is configured as , and is the mode that the MCU uses by default. With this scheme, you can specify a maximum value for the number of video and audio-only ports each conference is allowed to use on the Conference configuration page.
port reservations are only permitted when the MCU can guarantee them for repetition of a conference. As an example, a conference scheduled to run from 08:00 to 10:00 on the second Monday of each month will be deemed to clash with a conference configured to run from 09:00 to 09:30 every Monday, even though the former will only really clash with the latter every fourth or fifth week.
The Codian MCU supports an additional video channel known as the content channel for each conference. This feature encompasses: H.239 video streams sent from the MCU to viewing H.323 endpoints Sourcing the content channel from a H.323 endpoint's H.239 video stream, a SIP endpoint supporting content using BFCP, or a VNC connection Showing the content as part of the main video channel, where an endpoint cannot, for whatever reason, receive the content channel as an additional video channel.
that use encryption, the MCU can send encrypted and unencrypted content to different participants in the same conference (albeit with the same encryption key for every participant receiving encrypted content). The range of bit rates, resolutions and frame rates available to the MCU for sending the content channel via H.239 to H.323 video conferencing endpoints is potentially as wide as that for the main video channel. However, in general, the main video channel is used for motion video (i.e.
content channel) alongside the main video channel in a video-conferencing call that uses SIP. A SIP conference participant opens a BFCP channel to the MCU and contributes a video stream, such as that supplied by a second camera or an attached PC. Because there can be at most one content channel source, the SIP endpoint needs to make a request to the MCU, and have that request accepted, before actual content channel contribution can start.
Assuming that content is enabled on the MCU unit-wide, each scheduled conference can be independently configured to allow content channel operations or not. If enabled, this has an impact on the conference's port usage - if disabled, then all attempts by participants in that conference to open a content channel to the MCU will be unsuccessful. If the MCU is configured to allow encryption, each individual conference can be configured to either require encryption or to optionally use encryption.
Irrespective of per-conference or per-endpoint configuration parameters, if a conference is configured to allow content channel operations then it is possible to explicitly enable or disable individual conference participants' ability to use content via the web browser interface (assuming a user login with full conference control).
As well as the content stream (used for sending to H.323 endpoints), the MCU also generates a Codian proprietary format version of the content channel video which can be viewed in conjunction with PC-based video streaming. This ensures that, if desired, all participants and viewers for a conference are able to access all of its associated media. Content channel streaming also allows participants using H.323 video conferencing endpoints without H.
The text chat facility provided via web browser-based content streaming is two-way in that any content channel streaming viewer is able to both contribute text and see all messages typed by other viewers. Although there is no mechanism by which endpoints are able to contribute text chat messages, the MCU is able to display the most recent text messages within endpoints' main video channels.
The streaming of the content channel is performed using the port allocated for content rather than the port allocated for streaming. This means that it is possible to stream the content channel (for example, to use the video markup feature) for conferences which do not have streaming enabled.
You can control many conference features from the MCU web browser: Adding participants Viewing the participants list Customizing layout views Displaying conference statistics Sending messages to all participants You can add a participant to a conference in two ways: either as a "one-off" participant in to an active conference now or by adding their endpoint to the conference configuration, in which case the endpoint will be called every time the conference occurs.
To call a participant with a SIP endpoint in to an active conference: 1. Go to to display the Conference List. 2. Click a Conference name and then click . o To add an new endpoint (one that you have not added as a configured endpoint): i. Select the radio button and do one of the following: For , enter the IP address, or SIP URI of the participant's endpoint (in the format 1234@codian.
You can select custom layouts to use for all conference participants. To use this option: 1. Go to . 2. Click a Conference name and then click the tab. 3. Click on the layout you want to use from those shown in the Available layouts. There are different numbers of panes and pane configurations to choose from. The chosen layout is displayed enlarged to the left in the Conference custom layout section of the page and the radio button is selected. 4.
For each pane you can select an alternative setting: : no participant appears in this pane : this pane shows conference participants, automatically changing at the configured "Pane rolling interval" frequency from the page.
There is a setting on the MCU's pane placement behavior page to control this behavior called Loudest speaker 53
You can display statistics about a conference and use the information to quickly see how many participants are currently in the conference. To access this option: 1. Go to . 2. Click a Conference name and then click the tab. If the conference is active, statistics for that conference will be displayed. If the conference is completed only ―No longer active‖ will be displayed. Refer to the table below for information on interpreting this information. When the conference started.
The current number of contributing audio/video participants. The largest number of contributing audio/video participants who have been in the conference at the same time. The current number of contributing audio-only participants. The largest number of contributing audio-only participants who have been in the conference at the same time. The current number of streaming participants watching the conference. The largest number of streaming participants who have been watching the conference at the same time.
You can send messages to all participants in a conference simultaneously. To access this option: 1. Go to . 2. Click a Conference name and then click the tab. This message appears overlaid on each participant's view, including participants viewing the conference via streaming. Enter the message to send to all conference participants. Messages must be fewer than 256 characters, but depending on the viewing screen, messages at the higher-end of this limit might not display properly.
You can view detailed information about conference participants: Viewing the conference participant list Customizing a participant's layout display Controlling the near-end camera Managing a participant's audio signals Creating a custom participant view Displaying statistics for a participant Sending messages to one participant Displaying diagnostics for a participant Moving a participant The Participant list displays information about active and previous participants in the conference.
A locked conference is one where new participants cannot dial in and you cannot start to stream the conference. Existing participants and streaming viewers will maintain their connection to the conference. If a conference is locked, an icon will indicate this on the auto attendant. The auto attendant will also display the text: 'This conference is locked'. Note that participants that are pre-configured via the API will be able to dial in to the conference even if it is locked.
Configured endpoint names only display if the This indicates that this participant corresponds to participant list is being viewed by a user whose a pre-defined endpoint. The shown is privilege level is administrator or conference creation the endpoint's configured name. and full control; only users with these privilege levels have access to the configured endpoint database.
Displays the time at which a participant connected to the conference. If a participant is not yet fully connected (for example, if the MCU has called a participant but it has not yet answered), then that is indicated here. The resolution of the participant's video stream is also displayed. The following additional indications may also be displayed: If this column is selected as the sorting field, the listing is ordered according to when the participants connected to the conference.
Indicates that the MCU was unable to open a media channel to the endpoint because the only possible channels it would be able to open were invalid due to a symmetry clash. This clash occurs when the remote endpoint declared that it is only able to receive certain types of media if it is also sending the same format, and the format in question is one that the MCU is able to send but not receive.
Content is enabled for this conference, but this participant is not allowed to receive it. To enable content for this participant, configure the Content video receive setting for this participant's endpoint (refer to Configuring H.323 endpoints), or use the enable control for an active call. There is a unit-wide setting that determines which video codec is used by the MCU for outgoing content channels. The Outgoing content video codec is on the page.
stopped sending video keyframes in response to Fast Update Requests (FURs) to avoid degrading the content video sent to other conference participants. The MCU will only enter this state if the Video fast update request filtering setting is Enabled (see Configuring content settings). The associated participant is currently supplying the conference's content channel video. Use of this participant's main video source as the content (content channel) source has failed.
Displays a sample still video capture of the participant. Click the picture to update it. Note that conferences that are configured to require encryption do not show previews. Also note that previews can be disabled on the page (refer to Customizing the user interface). See Content channel video support for additional information on H.239 and BFCP. These controls are only available if the conference is configured with content enabled, and if the participant is contributing a main video channel.
audio in the conference (stop muting). Prevents others from seeing all participants' video contribution (mute). The presence of these controls is controlled by the setting on the page (refer to Customizing the user interface). Allows others to see all participants' video contribution (stop muting). Disconnects all participants from the conference. If this conference was created ad hoc, then disconnecting all the participants will terminate the conference as well.
configured endpoint. Note that if the original call to the conference was from the endpoint rather than the endpoint being invited by the MCU, then for the MCU to recognize it, that endpoint must be configured with Call-in match parameters. If the ** ERROR ** did not recognize that the call was from a preconfigured endpoint then the re-connect control will not be available. For more information about configuring endpoints on the MCU refer to Configuring H.323 endpoints and Configuring SIP endpoints.
Every person viewing a conference (whether they are contributing video of their own or using streaming to watch other participants) sees a conference layout view. This view divides the video screen into a collection of panes with participants' video streams displayed in those panes. You can customize this view by choosing this option: 1. Go to . 2. Click a Conference name and then click on a participant's name. 3. Click the tab. Displays static sample of video screen in the currently selected layout.
Click to choose a pre-configured custom See Selecting a custom participant layout. layout for this participant. Prevents this participant from changing their own conference layout using the far-end camera controls on their video endpoint. A participant can still change their layout view using the web interface. Allows this participant to control their own conference view.
You can control the viewing angle, zoom, and focus of the camera on a participant's video endpoint. You can customize this view by choosing this option: 1. Go to . 2. Click a Conference name and then click on a participant's name. 3. Click the tab. Click on one of the directional arrows to change the view direction of the camera. Not all endpoints will respond to these controls. In particular, endpoints with fixed cameras such as most webcams.
In general, the audio settings are for advanced troubleshooting. You can view these settings by selecting this option: 1. Go to . 2. Click a Conference name and then click on a participant's name. 3. Click the tab. These settings can help you resolve audio problems in conferences. For example: Waveforms display a snapshot of the audio waveform received from the participant's endpoint. If the participant is silent or speaking very quietly, the preview displays a horizontal green line.
You can add a custom layout to the choice of layouts available for this participant. You can customize this view by choosing this option: 1. Go to . 2. Click a Conference name and then click on a participant's name. 3. Click the tab. Indicates whether a custom layout can be used for this When you click a new layout from the Available participant. layouts, is automatically chosen with the most recent layout selected.
You can view statistics about the video and audio streams between individual participants (endpoints) and the MCU by choosing this option: 1. Go to . 2. Click a Conference name and then click on a participant's name. 3. Click the tab. If the participant is participating in the conference using audio only, the values for the video settings are not populated. Media statistics provide detailed information about the actual voice and video streams (Realtime Transport Protocol (RTP) packets).
The number of packet errors, including You should expect to see small values for this sequence errors, and packets of the wrong type. setting. Consistently large numbers typically imply potential network problems. Frame errors, as A/B where A is the number of A frame is a unit of audio, the size of which is dependent on codec. frame errors, and B is the total number of frames received. You should expect to see small values for this setting.
The bit rate (in bits per second) that the MCU has requested that the remote endpoint sends. The most-recently measured actual bit rate displays in parentheses.
Whether or not encryption is being used on the This field will only appear if the encryption key video transmit stream to this endpoint. is present on the MCU. The negotiated available bandwidth for the MCU to send video to the endpoint in. The bit rate the MCU is attempting to send at The Transmit bit rate value might be less than the this moment, which may be less than the Channel bit rate if : channel bit rate which is an effective maximum.
Media packet loss reported by receiver reports sent to the MCU by the far end. A count of the number of "sender report" type RTCP packets received by the MCU. These are typically sent by any device that is sending RTP media. A count of the number of reports seen by the MCU that are neither sender nor receiver reports. The IP address and port to which the MCU is sending RTCP packets about this stream. The number of packets sent.
You can send a short text message to a specific participant currently in the conference by choosing: 1. Go to . 2. Click a Conference name and then click on a participant's name. 3. Click the tab. This message appears overlaid on the participant's view, even if the participant is viewing the conference via streaming. Enter the message to send to this participant.
You can view diagnostics for an individual participant's connection to the MCU by choosing this option: 1. Go to . 2. Click a conference name and then click on a participant's name. 3. Click the tab. This page shows various low-level details pertaining to the endpoint's communication with the MCU. You are not likely to need to use any of the information on this page except when troubleshooting specific issues under the guidance of technical support.
You can move participants between conferences. Participants can be moved to any conference, but although participants can be moved from auto attendants they cannot be moved to them. To move a participant: 1. Go to > . 2. Click and drag the name of the participant to the required destination conference. Note that participants dragged and dropped into a conference on the web interface will be chairperson participants.
The Codian MCU allows you to configure auto attendants on it, which allows users to more easily join conferences. Displaying the auto attendant list Adding and updating an auto attendant Adding a custom banner You can display an overview of the configured auto attendants on the MCU: 1. Go to 2. Click the . tab.
attendant with the gatekeeper, it enters these states temporarily before reattempting the registration. The auto attendant has been registered successfully with the gatekeeper and can be contacted using the number indicated. The status of an auto attendant with respect to its For tips on configuring SIP, see SIP settings. SIP registration.
Auto attendants simplify the way participants can join conferences. By calling an auto attendant using their video endpoint, a participant can choose from menu options and join or start conferences. No gateway or gatekeeper is required. (The auto attendant is configured on the MCU.) To add an auto attendant: 1. 2. 3. 4. 5. Go to . Click the tab. Click . Refer to the table below for the most appropriate settings for the auto attendant. After entering the settings, click .
have enabled on the page. When using port reservation mode, there can be no ad hoc conferences. For more information about port reservation, refer to Reservation of MCU media ports. If Enabled, displays ad hoc conferences as well as If disabled, participants can only view scheduled scheduled conferences as options on the auto conferences; ad hoc conferences will not be shown. attendant. Note that this option will not be available if you have enabled on the page.
You can add a custom banner image to any auto attendant configured on the MCU as follows: 1. 2. 3. 4. 5. Go to . Click the tab. Click the name of a configured auto attendant. Click the tab. Refer to the table below to determine the most appropriate settings. Chooses the default Codian MCU graphic to use for your banner. The custom banner identified for this auto attendant. Click to remove this graphic as the banner. Click after uploading a new graphic.
To display the Endpoint List, go to . The Endpoint List displays all endpoints that have been configured within the MCU. To add a new H.323 endpoint, select To add a new SIP endpoint, select . . To add a new VNC endpoint, select . To delete configured endpoints, check the ones you want to delete and select . The name of the endpoint. The IP address, host name, H.323 ID, E.164 number, or SIP URI of the endpoint. Whether it is an H.323, SIP, or VNC endpoint.
You can configure H.323 endpoints to work with the MCU by choosing . This makes it easier to add endpoints to conferences because you can choose names from a list rather than adding network addresses. A Codian IP VCR can be configured as an H.323 endpoint and added as a participant in a conference. If the IP VCR is configured to do so, it will start recording as soon as the conference starts.
Choose whether to use the unit-wide setting for motion/sharpness trade off, or configure an individual setting for use with this endpoint. Choose from: The settings for motion (frames per second) and sharpness (frame size or resolution) are negotiated between the endpoint and the MCU. This setting controls how the MCU will negotiate the settings to be used with this endpoint.
Whether this endpoint is allowed to receive a separate content stream when in a conference. This setting is provided to allow you to individually configure whether or not an endpoint is allowed to receive content from a conference. To use the content channel, the Content status must be enabled at the unit-wide level (on the page) and for any given conference Content channel video must also be enabled in the per-conference configuration.
to the conference. For example, you can mute video from an endpoint if somebody wants to see the conference, but not be seen themselves. You can mute both audio and video if required. This can be altered during the course of the conference by going to and clicking on the name of a conference and altering this participant's settings. When a participant disconnects from a conference and only endpoints set to Automatic disconnection are left, all those participants are disconnected.
To configure the SIP endpoints to work with the MCU, go to . This makes it easier to add endpoints to conferences because you can choose names from a list rather than adding network addresses. Refer to the table below for tips on adding a SIP endpoint to the MCU. After entering the settings, click . The name of the endpoint. The IP address, host name, directory number, or The address of the SIP endpoint can be a SIP URI (in the format 1234@codian.com). directory number if you are using a SIP registrar.
endpoint. In this case, to use call-in match parameters, leave the IP address field blank and enter the correct username. The call will be matched by username. When using LCS, the username that will be matched is the user's display name (e.g. Peter Rabbit) rather than the sign-in name (bluecoat@codian.com). The name that will be displayed in a conference as a label for this endpoint. The name you enter here will override any default name configured on the endpoint.
Whether this endpoint is permitted to contribute This setting is provided to allow you to the conference content channel. Choose from: individually configure whether or not an endpoint is allowed to contribute content to a
seen in the conference, but does not want to contribute verbally. You can mute both audio and video if required. This can be altered during the course of the conference by going to and clicking on the name of a conference and altering this participant's settings. Set the initial video status of an endpoint to be either active or muted. If set to muted, when the endpoint joins a conference, it will not be able to contribute video to the conference.
You can configure a VNC (Virtual Network Computing) endpoint on the MCU by choosing . This makes it easier to add a VNC session to conferences because you can choose its name from a list rather than type its network address. You can add VNC endpoints to the MCU. This enables you to have software applications running on a remote computer added to a conference. For example, if a speaker has a set of slides to present during a conference, you can add them as a VNC endpoint. After entering the settings, click .
You can configure the Codian MCU to work with one or more H.323 gateways. The MCU can then effectively call through these configured gateways to one or more endpoints which are registered with the gateway but would not be reachable directly from the MCU. For example, an IP PBX could be configured as a gateway, and the MCU could then call its registered E.164 numbers. An ISDN gateway can be configured as a gateway on the MCU allowing calls to ISDN endpoints and telephones.
You can configure the Codian MCU with one or more H.323 gateways: To add an H.323 gateway, go to below, click . To update an existing H.323 gateway, go to settings described below, click . After entering the settings described and click on a gateway name. After updating the . The descriptive name of the gateway. All gateways must have a unique name. The IP address or host name of the gateway.
The MCU contains a built-in gatekeeper with which devices can register multiple IDs. IDs can be numbers, H.323 IDs (e.g. Fredsendpoint) or prefixes. Up to 25 devices can be registered without a feature key. Feature keys can be purchased to increase this number. : The MCU can register with its own built-in gatekeeper. The MCU then counts as one registered device. See Configuring gatekeeper settings. To start the gatekeeper, go to and select the H.323 gatekeeper check box to open a port for the gatekeeper.
Configures the built-in gatekeeper to send (or not to send) LRQs regarding unknown IDs to its neighbor(s). Choose from the options: Unless you have selected to Accept LRQs, you cannot configure the MCU to forward any LRQs. This setting enables the built-in gatekeeper to accept LCF message responses from any IP address. This setting is for use in environments with a multiple-level gatekeeper hierarchy.
Below these summary figures is a table showing individual registrations. Registrations can be viewed by registered ID (the "ID view") or by device (the "Registration view"), giving complete and easily searchable lists. Switch between the views by clicking on the appropriate button. The Registration view shows the summary per device (also known as the registrant), while the ID view shows individual registrations.
The MCU is pre-configured with two user accounts ("admin" and "guest"), but you can also add other users (see Adding and updating users). Refer to the table below for descriptions of the pre-configured users. The MCU must have at least one configured user After logging into the MCU for the first time (see with administrator privileges. By default, the Logging into the web interface), you can change User ID is "admin" and no password is required. the User ID and password for this account.
1. 2. 3. 4. Go to . Click . Refer to the table below to determine the most appropriate settings for the user. After entering the settings, click . The log-in name used to access the MCU web browser. This is fixed at "guest" The required password, if any. Verifies the required password. The privilege level, which can be changed to any level except administrator. See User privileges for detailed explanations.
Every configured user in the MCU has an associated privilege level. There are seven defined privilege levels which determine the amount of control the user has over the MCU and its settings. Refer to the table below for details.
Users with this privilege level can: Change their own profile ( ) View the list of active conferences ( ) View conferences via streaming ( ) View participant lists for active conferences ( Schedule new conferences ( ) Fully control and modify conferences they own ( ) ) Users with this privilege level can: Change their own profile ( ) View the list of active conferences ( ) View conferences via streaming ( ) View participant lists for active conferences ( ) Users with this privilege level can: Change the
The User list gives you a quick overview of all configured users on the MCU and provides a brief overview of some of their settings. To display this list, go to . Refer to the table below for assistance. The log-in name that the user needs to use to access the MCU web browser. The full name of the user. The access privileges associated with this user. See User privileges for detailed explanations. The associated E.164 telephone number. The associated video endpoint.
You can add users to and update users on the MCU. Although most information is identical for both tasks, some fields differ. The MCU supports up to 200 users. To add a user: 1. 2. 3. 4. Go to . Click . Complete the fields referring to the table below to determine the most appropriate settings for the user. After entering the settings, click . To update an existing user: 1. Go to . 2. Click a user name. 3.
Associates an E.164 telephone number with a user account. If the MCU receives a call from the E.164 phone number provided, it matches the number to the user account. This allows the MCU to take the appropriate action if one (or both) of the following fields are completed. Associates a configured endpoint with the user. This is used when a participant's video stream is from a separate device such as a web camera on a PC or a recording from a Codian IP VCR.
You can make some changes to your user profile. To do this, go to tips. Your name, which identifies you to other users. . Refer to the table below for Changing this field does not change your log-in User ID. You can enter a new password. Verify the new password. Associates an E.164 telephone number with your This limits the setup you will need to do each user account. time you join a video conference. When the MCU receives a call from this number, it will be recognized as coming from your phone.
You can modify the global conference settings for the MCU choosing by . However, many of these values can be overwritten by other MCU settings, for example individual conference, participant, or endpoint settings. In this section: Conference settings Advanced settings Refer to this table for assistance configuring the conference settings. After making any configuration changes, click . Identifies the greatest video size that the MCU will send and receive when connected to a video endpoint.
Identifies the network capacity (measured in bits per second) used by the media channels established by the MCU to a single participant. When the MCU makes a call to an endpoint, the MCU chooses the maximum bandwidth that is allowed to be used for the media channels which comprise that call. This field sets that maximum bandwidth, and is the total bandwidth of the audio, video, and content channels combined. This setting can be overridden by individual endpoints' Preferred bandwidth from MCU values.
participants join and leave the conference. : audible status messages for example indicating to a participant that he is the only participant in a conference. Allows various in-conference icons to be displayed on participants' endpoints. Depending on the check boxes that are selected, in-conference icons appear: : a crown icon appears on all participants' endpoints in the pane of the participant that has become important.
video port to the participant, or the participant has muted their endpoint's video channel to the MCU. : an icon appears in the top left of the conference display to indicate if there are any streaming participants in the conference. If enabled, the icon will only display if there are one or more streaming participants. Streaming participants are people who are viewing and listening to the conference using a web browser.
This setting controls for how long (if at all) the Codian logo is displayed to participants joining a conference. Choose from: When displayed, the Codian logo appears in the bottom right of a participant's conference display. Allows you to enter a message that will be seen The duration of the message is configured using by participants joining conferences on the MCU. the The message is displayed at the bottom of a control. participant's conference display.
Determines which audio codecs the MCU Note that the Custom codec selection setting for an advertises to remote endpoints, restricting the individual endpoint will override this unit-wide endpoints' choice of channels available for sending setting for calls from that endpoint. audio data to the MCU. Restricts the MCU's choice of video codecs to be When communicating with an endpoint, the used for transmitting video to endpoints. MCU receives a list of supported video codecs from the endpoint.
The MCU will heavily favor sending 448p or w448p video (resolutions of 576 x 448 and 768 x 448 pixels respectively) to those endpoints that are known to work best with these resolutions. Sets the format for video transmitted by the MCU. The MCU will transmit video at 30 frames per second (or a fraction of 30, for example: 15fps) The MCU will transmit video at 25 frames per second (or a fraction of 25, for example: 12.
Enables the MCU to request that the endpoint send lower speed video if it fails to receive all the packets which comprise the far end's video stream. The MCU can send these messages to endpoints requesting that the bandwidth of the video that they are sending be decreased based on the quality of video received by the MCU.
When pane placement is in use, this option affects For more details of view layouts, see the potential duplication of participants that are Understanding how participants display in layout specifically placed in view panes with view panes views. configured to show the conference's current active speaker. A pane set to show the loudest speaker will never show a participant that is specifically configured to be displayed in another layout pane.
Select the delay to be applied to audio relative to A setting used only to rectify some types of 'lip video. sync' issues sometimes found with certain endpoints. Leave at default setting, unless advised to alter it by Codian technical support or a reseller. Controls whether connected endpoints are This option acts as a unit-wide control over allowed to use floor and chair control operations. whether any H.243 floor and chair control operations are permitted.
conference. protected, regardless of how participants connect, ensure you set this option. When this option is set, participants calling into a protected conference will be presented with PINentry screen instead of the normal conference view. The option has no effect for conferences with no PIN set. If this option is checked, ad hoc conferences created using either an auto attendant or via calls to an E.
To configure gatekeeper settings, go to . You can configure the MCU to use a gatekeeper, which can make it easier for end-users to join conferences using directory numbers rather than requiring them to know the IP address or host name of the MCU. The MCU can register up to 100 IDs with the gatekeeper; these IDs comprise conferences' Numeric IDs, the MCU service prefix, and the H.323 ID.
having specific problems using the Cisco Gatekeeper (with or without a service prefix), in which case use Gateway (Cisco GK compatible) using the VCON MXM Gatekeeper (with or without a service prefix), in which case use MCU (compatible) Refer to the list of Frequently Asked Questions (FAQ) in the Support section of the web site for more details about interoperability with gatekeepers. Whether a call involves consultation with the configured gatekeeper also depends on the Port A and Port B settings.
associated numeric identifier. If H.323 gatekeeper usage is disabled, this field will have no effect. Note that if you are also intending to use the MCU service prefix (see below), Codian recommends that you set both prefixes to the same number. If required, specify a group of digits which the H.323 gatekeeper may use to identify calls to be routed to the MCU. This field is optional. If set, users dialing any number beginning with this prefix will have their call directed to the MCU.
page (see Configuring global conference settings). This field will have no effect if H.323 Gatekeeper usage is set to Disabled. Select this option if you want the MCU to inform the gatekeeper about its availability or nonavailability. This information will be used by the gatekeeper when it is selecting where to place ad hoc conferences. Only use this option where multiple MCUs are registered with the same MCU service prefix on the same gatekeeper.
The MCU also displays brief status information about its registrations with the configured gatekeeper. To display a complete list of all IDs that the MCU is attempting to register with the configured H.323 gatekeeper, click the link in the Number of active registrations row of the gatekeeper status table; this takes you to the Active registrations page. Displays the IP address of the gatekeeper currently being used by the MCU.
Displays whether the gatekeeper is configured to The possible statuses are: send resource availability indications and if it is, it displays the current state of the resource availability status of the MCU. Displays the number of E.164 numbers plus H.323 IDs plus prefixes that the MCU has registered with the gatekeeper. It also shows how many registrations are in progress but are not fully registered yet.
To display a complete list of all IDs that the MCU is attempting to register with the configured H.323 gatekeeper, go to and click , shown next to the Number of active registrations status entry. You are taken to the page. This page shows the complete set of IDs that the MCU is attempting to register with the configured H.323 gatekeeper, and includes the H.323 ID, prefixes, and specific E.164 number registrations for active conferences and configured auto attendants.
To configure SIP settings on the MCU, go to . To allow conference participants with SIP endpoints to connect to the MCU by dialing a directory number rather than an IP address, you must configure a SIP registrar. The settings on this page control the MCU's interaction with the SIP registrar and with SIP endpoints.
If you are using Microsoft OCS or LCS, you need to enter the full URI (for example, MCU@mylcs.com). Note that this username will be used anywhere where one is required in a SIP call; for example, it will be used where authentication is required with a SIP server where no registrar is used. The password for the MCU on the SIP registrar. You need to configure the SIP registrar with details of the devices that will register with it and create a login for each device.
encryption. Where encryption is required in the conference configuration, a SIP call must use SRTP. For more information about SIP encryption, refer to Configuring encryption settings. The MCU can accept connections on TCP, UDP, and TLS providing those services are enabled on the page (Configuring network services).
You can configure two streaming options that will be available for users to choose between when streaming conferences. For each streaming option, you must choose a media player and a bit rate. You can configure the MCU to support either (or both of) unicast or multicast streaming. Unicast streaming involves a direct connection between the MCU and the individual user. Multicast streaming involves transmitting a single copy of the video or audio stream to multiple recipients.
Sets the audio and video combination to use, and Typically, when two streaming rates are used, the overall media bit rate. one is set up as a low bit rate combination and the other configured to use a higher bit rate. This enables those users with a low bandwidth connection to achieve useful streaming while at the same time allowing those with a high bandwidth link to take advantage of enhanced video. The available options vary depending on which media player you have chosen.
The content settings affect the behavior of the MCU with regard to H.239 and BFCP (Binary Floor Control Protocol). H.239 is the protocol that allows for an additional video channel (known as the content channel) alongside the main video channel in a video-conferencing call that uses H.323; BFCP is a protocol that allows for an additional video channel (known as the content channel) alongside the main video channel in a video-conferencing call that uses SIP.
This field sets which video codec is used for conferences' content video streams. A single content video stream is used for each conference, and this stream will be sent to all viewing endpoints. If an endpoint is unable to receive content video using the codec configured here, no content channel will be opened to that endpoint.
(see above). In these cases, if this option is set to Enabled, the MCU will display the content channel video within a pane of the currently selected conference layout. In these cases, you might also want to enable the Automatically make content channel important option in the page which will make the content channel important at the same time.
You can configure the MCU to encrypt connections to and from H.323 and SIP endpoints. The encryption technology that the MCU uses for encryption to and from H.323 endpoints is Advanced Encryption Standard (AES). The encryption technology that the MCU uses for encryption to and from SIP endpoints is Secure Real-time Transport Protocol (SRTP). To use encryption, you must have the Encryption feature key present on the MCU. For information about installing feature keys, refer to Upgrading the firmware.
Whether the MCU is able to use encryption or not. When encryption status is Enabled, the MCU advertises itself as being able to use encryption and will use encryption if required to do so by an endpoint. If this setting is Enabled, you can enable or disable the use of encryption on a perconference basis. If this setting is Disabled, no conference will be able to use encryption.
The MCU supports the use of encryption with SIP. When encryption is in use with SIP, the audio and video media are encrypted using Secure Real-time Transport Protocol (SRTP). When using SRTP, the default mechanism for exchanging keys is Session Description Protocol Security Description (SDES). SDES exchanges keys in clear text, so it is a good idea to use SRTP in conjunction with a secure transport for call control messages.
To configure the network settings on the MCU and check the network status, go to . or The MCU has two Ethernet interfaces, Port A and Port B. The configuration pages for the two interfaces look and behave similarly, and so are described together. Differences will be noted as appropriate. Port A can be configured to be allocated its IP address by DHCP. Port B cannot use DHCP. Connect Port A to your local network and connect Port B to a second subnet or the internet depending on your application of the MCU.
Identifies the IP address of the name server. Identifies an optional second name server. The secondary DNS server is only used if the first is unavailable. If the first returns that it does not know an address, the secondary DNS server will not be queried. Specifies an optional suffix to add when performing DNS lookups. This can allow you to use non-fully qualified host names when referring to a device by host name instead of IP address. For example, if the domain name is set to codian.
Identifies the connection duplex mode: The duplex setting must match that of the device to which this port is connected. Both devices can send data to each other You only need to select this option if you have at the same time chosen manual Ethernet settings, as described above. Only one device can send to the other at a time Indicates whether this Ethernet port is connected to or disconnected from the network. Shows the speed (10/100/1000 Mbit/s) of the network connection to the MCU on this port.
If the Video Firewall feature is enabled (see Upgrading the firmware), you will need to set up one or more routing settings to control how IP traffic flows in and out of the MCU. It is important that these settings are configured correctly, or you may be unable to make calls to or from the MCU or access the web interface. To configure the route settings, go to .
In this section you can control how IP packets should be directed out of the MCU. You should only change this configuration if you have a good understanding of the topology of the network(s) to which the MCU is connected. Configuration of routes is divided into two sections: addition of new routes, and the display and removal of existing routes. To add a new route, first enter the details using the table below for reference. When you are satisfied with the details entered, click to make the addition.
The default route is configured automatically in correspondence with the default gateway preference field (see Port preferences) and cannot be deleted. Any packets not covered by manually configured routes will be routed according to this route. Manually configured routes may be deleted by selecting the appropriate checkbox and clicking .
To configure IP services, go to . Use this page to control the type of services that may be accessed via Ethernet Ports A and B. You might use this if one Ethernet port is connected to a network outside your organization's firewall, and you wish to restrict the level of access that external users are entitled to, for example, by disabling FTP access via Port B. Refer to the table below for more details.
Allow/reject incoming calls to the MCU using H.323 or change the port that is used for this service. Disabling this option will not prevent outgoing calls to H.323 devices being made by the MCU. That is, the MCU will need to dial out to conference participants who are using H.323. If a port is disabled, this option will be unavailable. Allow/reject incoming calls to the MCU using SIP over TCP or change the port that is used for this service.
Allow/reject incoming and outgoing calls to the Disabling this option will prevent calls using SIP MCU using SIP over UDP or change the port that over UDP. is used for this service. If a port is disabled, this option will be unavailable. You must use the same port number for both Port A and Port B. The number is automatically refreshed for Port B.
To configure monitoring using SNMP, go to . The MCU sends out an SNMP trap when the device is shut down or started up. The SMNP page allows you to set various parameters; when you are satisfied with the settings, click . Note that: The 'system up time' that appears in the trap is the time since SNMP was initialized on the MCU (and therefore will differ from the Up time reported by the MCU on the > page). The SNMP MIBs are read-only. Identifies the MCU in the SNMP system MIB.
Select this check box to enable the MCU to send If you do not check this box, no traps will be traps. sent. Select this check box to enable authentication failure traps. You cannot select this check box unless you have selected to Enable traps above. Authentication failure traps are generated and sent to the trap receivers when someone tries to read or write a MIB value with an incorrect community string.
To configure Quality of Service (QoS) on the MCU for audio and video, go to . QoS is a term that refers to a network's ability to customize the treatment of specific classes of data. For example, QoS can be used to prioritize audio transmissions and video transmissions over HTTP traffic. These settings affect all audio and video packets to H.323 and SIP endpoints, and to streaming viewers. All other packets are sent with a QoS of 0.
ToS configuration represents a tradeoff between the abstract parameters of precedence, delay, throughput, and reliability. ToS uses six out of a possible eight bits. The MCU allows you to set bits 0 to 5, and will place zeros for bits 6 and 7. Bits 0-2 set IP precedence (the priority of the packet). Bit 3 sets delay: 0 = normal delay, 1 = low delay. Bit 4 sets throughput: 0 = normal throughput, 1 = high throughput. Bit 5 sets reliability: 0 = normal reliability, 1 = high reliability.
The system date and time for the MCU can be set manually or using the Network Time Protocol (NTP). To configure Time settings, go to . Note that changing the time or NTP settings will have an effect on the recorded times in the Call Detail Records log. For more information, refer to Working with Call Detail Records. The current system date and time is displayed. If you do not have NTP enabled and need to update the system date and/or time manually, type the new values and click .
If you need to upgrade the firmware or activate features on the MCU, refer to these topics: Upgrading the main MCU software image Upgrading the loader software image Enabling MCU features Storing user passwords securely The main MCU software image is typically the only firmware component that you will need to upgrade. Follow these steps to upgrade this image: 1. 2. 3. 4. 5. 6. 7. 8. Check the Current version field to verify the currently installed version.
The MCU requires activation before most of its features can be used. (If the MCU has not been activated, the banner at the top of the web interface will show a prominent warning; in every other respect the web interface will look and behave normally.) Advanced MCU features (such as Video Firewall) are not enabled as standard, and require additional activation. For information about configuring the video firewall, refer to the FAQ section in the support pages of the web site.
It is sometimes necessary to shut down the MCU, generally to restart as part of an upgrade (see Upgrading the firmware). You should also shut down the MCU before intentionally removing power from the MCU. Shutting down the MCU will cause all conference participants to be disconnected, and allows the MCU to ensure that all data (such as Call Detail Records) is stored correctly. You will lose network connectivity with the MCU for a few minutes while you restart the unit.
The General Status displays an overview of the MCU status. To access this information, go to Refer to the table below for details of the information displayed The specific Codian MCU model. The unique serial number of the MCU. The installed software version. You will need to provide this information when speaking to Technical support. The build version of installed software. You will need to provide this information when speaking to Technical support. The time since the last restart of the MCU.
The conference status page displays the status of active and completed conferences and video and audio processing. To access this information, go to . Refer to the table below for assistance in interpreting the information displayed: Conference status Video status Audio status For information about the number and type of ports provided by each MCU model, refer to MCU port matrix.
shows the number of video ports in use. This corresponds to the number of connected participants that are either contributing or being sent video, plus the number of conferences for which streaming is active. This value is shown if the MCU is not operating in Port reservation mode, and shows the number of audio-only ports in use. This corresponds to the number of connected participants that are contributing or being sent audio but not video.
Video status displays an overview of current video resource use. The number of video streams being received by the MCU. The number of video streams being sent by the MCU. Unicast indicates video streams sent directly to the MCU (incoming) or directly to the endpoints (outgoing) rather than multicast streams broadcast to the network and captured or sent by the MCU. The total video data rate being received by the MCU. The total video data rate being sent by the MCU.
The this page, go to information and on the page shows various status items related to a conference's content channel. To view click the name of the conference about which you want more tab, click the Content channel link. The displayed information is split into three sections: This section shows a graphical representation of the current content channel. If there is no active content channel, inactive will be shown here.
The Health Status displays information about the hardware components of the MCU. To access this information, go to Note that the Worst status seen conditions are those since the last time the unit was restarted. To reset these values, click . Refer to the table below for assistance in interpreting the information displayed. Displays two possible states: – component is functioning properly – Check with your support provider; component might require service OK Out of spec States indicate both conditions.
The port provision of the various MCU models is shown in the table below. Each video port can be used by one video-conferencing participant. Each audio port can be used by one voice-only participant in a video conference.
If you are experiencing complex issues that require advanced troubleshooting, you may need to collect information from the MCU logs. Typically, you will be working with Technical support who can help you obtain these logs. The last 2000 status messages generated by the MCU are displayed in the Event log page. In general these messages are provided for information, and occasionally Warnings or Errors may be shown in the Event log.
The H.323/SIP log page records every H.323 and SIP message received or transmitted from the MCU. The log can be exported in an .xml file. By default the H.323/SIP log is disabled because it affects performance, but Techincal support may ask you to enable it if there is a problem with a unit in your network. In addition to the logs described above, the MCU can also store Call Detail Records (CDR) which may be used for auditing and billing purposes. Events in the log are displayed in the CDR log page.
You can send the Event log to one or more syslog servers on the network for storage or analysis. To configure the syslog facility, go to In this section: Syslog settings Using syslog Refer to this table for assistance when configuring Syslog settings: Enter the IP addresses of up to four Syslog receiver hosts. The number of packets sent to each configured host will be displayed next to its IP address. A configurable value for the purposes of identifying events from the MCU on the Syslog host.
The events that are forwarded to the syslog receiver hosts are controlled by the event log capture filter. To define a syslog server, simply enter its IP address and then click sent to each configured host is displayed next to its IP address. .
The MCU implements SIP as defined in RFC 3261. Any product wishing to establish SIP calls with the MCU should implement INVITE, ACK, BYE, and CANCEL messages along with responses from 1xx to 6xx. The MCU acts as a client and does not return 5xx and 6xx responses itself; however, proxies and other intermediaries may do so. To use a SIP registrar in conjunction with the MCU, you must register an ID for the MCU with the SIP registrar.
The MCU is able to generate Call Detail Records (CDR) which may be used for auditing and billing purposes. When logging is enabled, records are generated whenever a conference starts or finishes, when participants join and leave conferences and so forth. To use the CDR feature, there must be a 256 Mb compact flash card in the slot in the front of the unit. If there is no compact flash card present, and you have enabled CDR logging, errors will be recorded in the Event log.
This table shows the logged Call Detail Records, subject to any filtering applied (see Call Detail Record log controls, above). The fields displayed and the list's associated controls are described below: Downloading and clearing the log CDR log display The CDR log includes all stored Call Detail Records, and all available details, regardless of the current filtering and display settings. It is possible to download all or part of the CDR log in XML format using the web interface.
The CDR log time stamp is stored in UTC time and not local time like the Event log, but converted to local time when displayed in the CDR log.
In this section: Controlling the auto-refreshing of status pages on the MCU Controlling the display of thumbnail preview images Controlling the confirmation of participant disconnections Controlling the audio and visual muting of conference participants Customizing voice prompts on the MCU The MCU provides you with options for customizing the voice prompts, the viewing of thumbnail previews, and for controlling the auto-refreshing of user interface pages.
The default settings for the MCU allow you to disconnect, without confirmation, individual participants from a conference on the page. On the page, you can configure the MCU to display an "Are you sure?" confirmation box when attempting to disconnect an individual participant. Note that all-participant disconnections always require confirmation. To control the confirmation of individual-participant disconnections: 1. Go to . 2.
The default set of voice prompts is provided in US English and is the standard set of voice prompts supplied with the MCU. These are spoken by a female voice in Americanized English. If your unit is using customized voice prompts and you want to return to using the default set of voice prompts: 1. 2. 3. 4. Go to . In the section, uncheck Use customized voice prompts. If your unit was provided to you as a localized unit, uncheck Use localization package. Click .
To expand any list to show all customizations, click . ; you may subsequently hide it again by clicking In the expanded state, the table shows, for each customization, a description of the file, the standard MCU filename for the customization, and the length and date modified (uploaded) of alternative customizations present.
5. When you have located the file you wish to upload, click . If the upload is successful, a page displaying the size of the file uploaded will be displayed; otherwise an error will be shown. If the upload fails, check your audio file matches the specification above before contacting your support representative. You may wish to review a customization that has been previously uploaded to the MCU. To do this, 1. Go to . 2. In the section, locate the voice prompt file you require. 3.
Below is a complete list of the voice prompts that may be customized. The default wording is shown for each prompt. You do not have to use exactly the same wordings if they are not appropriate for your needs, and are provided only as a guide. I'm sorry, there is already a conference with that number Your conference is now over.
It is important to minimize background noise (hiss) as much as possible. This includes ambient noises such as road noise and slamming doors etc. but also try to keep fan noise and similar to a minimum. When played back by the MCU, samples with background noise are very apparent. If possible, record all voice prompts in one session. This will ensure that all voice and background conditions remain constant and the recorded voice will sound similar from prompt to prompt.
There are three customization levels on the unit (for voice-prompts, web interface, help pages, and text messages): the factory default files that are provided in US English localization files that are sometimes installed by a reseller customized voice prompts files that can be uploaded and downloaded by you For every customizable file: 1. If there is a customization file present and is checked, that file will be used. 2. Otherwise, if is checked, the unit will use the localized file. 3.
You can save the configuration of the MCU to a file that you can store away from the unit. If necessary this file can be used to restore the configuration of the unit. 1. Ensure that the FTP service is enabled on the page. 2. Connect to the MCU using an FTP client. When asked for a user name and password, enter the same ones that you use to log in to the unit's web interface as an administrator. You will see a file called configuration.xml. This contains the complete configuration of your unit. 3.
The page can be used for troubleshooting issues that arise because of problems in the network between the MCU and a remote video conferencing device being called (or a device from which a user is attempting to call the MCU). The page enables you to attempt to 'ping' another device from the MCU's web interface and perform a 'traceroute' of the network path to that device. The results show whether or not you have network connectivity between the MCU and another device.
If the MCU has the Secure management (HTTPS) or Encryption feature key installed, and you enable the secure web service on the page, you will be able to access the web interface of the MCU using HTTPS. The MCU has a local certificate and private key pre-installed and this will be used by default when you access the unit using HTTPS. However, we recommend that you upload your own certificate and private key to ensure security as all MCUs have identical default certificates and keys.
If your organization has bought a certificate, or you have your own way of generating certificates, you can upload it. Browse to find the certificate file. Browse to find the private key file that accompanies your certificate. If your private key is stored in an encrypted format, you must enter the password here so that you can upload the key to the MCU. You can upload a 'trust store' of certificates that the MCU will Note that uploading a use to verify the identity of the other end of a TLS connection.
Please refer to the following sections for details of where to get further help and for additional software license information: Codian Software licenses The Codian MCU firmware is Copyright © Codian 2003-2008 except where specifically mentioned below. All rights reserved. For further assistance and updates please visit the Codian web site: www.codian.com. This product contains an authentication function which uses an encrypted digital signature and a public key infrastructure.
Copyright © 1999-2004 The NetBSD Foundation, Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2.
This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the above disclaimer and the following restrictions: 1.
Permission is NOT granted for the use of any IJG author's name or company name in advertising or publicity relating to this software or products derived from it. This software may be referred to only as "the Independent JPEG Group's software". We specifically permit and encourage the use of this software as the basis of commercial products, provided that all warranty or liability claims are assumed by the product vendor. Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code.
Copyright © 1995-2003, SPIRIT The Codian MCU includes a G.728 audio codec used under license from Spirit Corporation. Copyright (c) 2001, Dr Brian Gladman, Worcester, UK. All rights reserved. The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that: 1. distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer; 2.
This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and/or fitness for purpose. Issue Date: 26/08/2003 Copyright (c) 2002, Dr Brian Gladman, Worcester, UK. All rights reserved. The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that: 1.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Copyright © 2004 Internet Systems Consortium, Inc.
