Gebruiksaanwijzing /service van het product MCU 4500 van de fabrikant TANDBERG
Ga naar pagina of 190
Codian MCU 45 00 Series Codian MSE 8510 Series Online help (printable format) Software version 2.4(1).
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@t andberg.
1.
2.
3.
4.
5.
6 The Codian MCU we b interface is used for administering the MCU devic e, managing conf erences, users , and pre- defined endpoints. You can also perform many c onference-re lated tasks using the w eb interfac e that you cannot otherwise do.
7 Depending on ho w your system adminis trator has config ured the MCU and conference s on it, you might be ab le to join conference s by simply dial ing a phone number . Your system administ rator may have configured the M CU to allow you to use you r video e ndpoint to direc tly dial the conference by dialing a phone number.
8 Your system administ rator may have set up an auto at tendant for you to use to join confe rences. An auto attend ant presents you with a series of menus from which you can ch oose a confe rence to join.
9 When in DTMF navig ation mode , you will not be able to use the numbe r keys to enter the numeric ID of a conference. Typically, you will have these options: This option enables you to star t a new conferenc e that takes p lace immediately ( an "ad hoc" c onference).
10 The streaming inter face enable s you to enter the ID of a conferenc e and view it in a web browser on your PC. You do not have to have a user accoun t on the MCU to be able to do this. If you do need to log in to the MCU, u se the link on the top right o f the screen.
11 The Codian MCU suppo rts stre aming, which involv es sending confe rence media (audio and video) to a remote computer, allowing the user to watch and listen to a confe rence. The me dia flows in just o ne direction, so it i s not possible to actually cont ribute to a confe rence via streaming .
12 After you join a confe rence, you c an control many conferen ce features direc tly from your video endpoint. (For information about in-confe rence features using the web in terface, see Controlling in-confe rence features ).
13 You are scrolling up throug h the layout views. You are scrolling dow n through the layout views. You have stopped scrolling throug h the layout views.
14 During the conferenc e, variou s icons might appear in the pane of specific participants. Refer to the table below for assistance interpreting these icons. This participant has be en given priority in the layout views. A participant is made "impo rtant" using c ontrols on the MC U web pages.
15 During the conferenc e, variou s icons might appear in top left of the conferenc e display. The appearance of the se icons is controlled on the page (refer to Configuring global confe rence settings ). Refer to the table below for assistance interpreting these icons.
16 Depending on ho w your video endpoint is configured, an inc oming video call mig ht come throug h to your regular phone or to your vide o endpoint (see Calling into conference s for a brief desc ription of the diffe rence).
17 The default beh avior of the Co dian MCU is to display the "loude st" participants in the mo st prominent layout panes. If there are more c ontributors than there are panes available, then th e "quietest" par ticipants are not show n.
18 When considering which participants to show in which panes, a participant 's self view has th e lowest priority. This has two main implic ations: When choosing participants to display, the MCU conside rs the vie wer last. This prevents the participant who is the active speaker from seeing only themselve s.
19 Both "Changing view foc us" and "Impo rtant particip ants" above involv e a single specific participant being shown in the biggest pane available, even if th at participant is not currently the loudest speaker. This causes a potential conflic t, which is resolved depe ndant on the type of layout.
20 The majority of the conference layouts define d by the Codi an MCU, for example : have in common th at all of their panes, wh ether big or s mall, have the same a spect ratio as t he view itself. Th at is, the panes' widths and heig hts are in the sa me proportion as the width and heigh t of the encompassing view.
21 Some H.323 endpoin ts support a featu re known as floo r and chair control that is encompass ed by the H.243 protocol. This is not cur rently supported by SIP. The MCU suppor ts the followi ng H.243 features: a participant can "take the floor" in a confe rence.
22 The Conference Li st displays i nformation about active , schedule d, and completed conferen ces. To acce ss this list, choose . Review this info rmation for explanation s about the det ails that display: Active conferenc es Schedule d conferences Completed conferenc es Active conferenc es are currently in progress.
23 The status of a confe rence wit h respect to its H.323 gatekeepe r and/or SIP reg istration. Depending on the conference settings, there is a maximum of four regist rations for e ach conference: H.323 num eric ID, H.323 gue st numeric ID, SIP num eric ID, and S IP guest numeric ID.
24 ports for a conference (for inst ance because of a configuration error ), this value will display in red as an error indication. When the confe rence began. If the conference started before today, the date also displays. How long the confe rence still has to run.
25 Completed conferenc es have fi nished and are not sch eduled to repeat. To remove specific c onference s from the list, selec t the conferenc es via their associated checkbo xes and click . To remove all confere nces from th e list, click . The name of the confe rence chosen wh en the conference w as scheduled.
26 The information requ ired to add or upd ate a conference is nearly identical. Refer to the se topics for details : Adding a conferenc e Updating a conferenc e Adding configured endp oints Using IDs and PINs To add a conferenc e: 1.
27 The name that users will see on auto attendant screens and on the MCU's web inte rface. Conference names mu st be uniqu e; conferences cannot share names. Only schedule d conferences hav e a configurable Name ; ad hoc confe rences do not have one.
28 enabled on the page), participants can di al in using this numbe r. Note that the actual numbe r that par ticipants will dial depends on whethe r prefixes are used in the page. For an active ad hoc c onference, you c annot configure the Numeric ID .
29 Provides secure acc ess to conf erences for guest participants. If a conference h as a PIN set, u sers cannot join the conference or change its c onfiguration without entering the c orrect PIN . Participants joining as guests h ave restricted privile ges.
30 Indicates the visibili ty of the conference on the auto attendant and the we b interface. The o ptions are: : the conferenc e will be listed in the auto attendant and be visible to all users of the web inte rface : the conferenc e will not be listed in any auto attend ant except for auto attendants specific ally set to show it.
31 Select to initially mute audio and/or vide o fro m all participants when the y 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 confe rence.
32 Whether, by default , endpoints are pe rmitted to contribute the content c hannel for a confe rence through the mech anism of opening a content video channel. There can only be one endpoint contributing content video at any one time, and the MCU arbitrates betwee n them.
33 Sets the conferenc e start time to the current time on the MCU. The current time on the MCU is determined by the settings in the page, which can only be modified by the administr ator. See Displaying general status for additional information. Allows you to ret ain a conference and its setting s for an infinite period of time.
34 all participants are di sconnected (default ) all participants may c ontinue the c onference until the la st one disconnec ts ( take no action ) If you set both Numeri c 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 PI N , you must use a PI N .
35 Each scheduled co nference (i.e . conferences that are configured via the web inte rface with a start time and, optionally, a duration and repe tition) has an associ ated owner . This owner is the ID of a confi gured user, and norm ally corresponds to the u ser who sc heduled the c onference.
36 As described above, a user pri vilege lev el confers a certain lev el of control over a c onference, with tha t level of control possibly depe nding on w hether that user is the c onference owner or not.
37 Participant custom layout , and whe ther to send widescree n or standard fo rmat video to that endpoin t. The web interfac e can be used to send control command s (e.
38 The MCU is able, if required, to alloc ate its available media ports in adv ance to specific co nferences. This means that it is able to guarantee that a ce rtain number of pa rticipants will be able to join th at conference, irrespec tive of how many other people are using the MCU for other conferences at the same time.
39 How MCU medi a ports are alloc ated, and which options and setting s are available, is controlled by the Media port reservation setting on the Conference settings page. This is the mode th at the unit r uns in when the Media port reser vation setting is configu red as , and is the mode that the MCU uses by default.
40 port reservations are only permitte d when the MCU c an guarantee them for repetition of a conference. As an example, a conferenc e scheduled to run from 08:00 to 10:00 on the second Monday of each.
41 The Codian MCU suppo rts an additional video channe l known as the content channel for each confe rence. This feature encompasses: H.239 video streams sent from the M CU to viewing H.323 endp oints Sourcing the conte nt channel from a H .323 endpoint's H.
42 that use encryption, the MCU can send encrypted and unencrypted co ntent to different part icipants in the same conference ( albeit with the same enc ryption key fo r every partic ipant receiving encrypted content). The range of bit ra tes, resolutions and frame rates available to the MCU for sending the co ntent channel via H.
43 content channel) along side the main vide o channel in a video-conferencing call that uses SIP. A SIP conference participan t opens a BFCP c hannel to the M CU and contribute s a video stre am, such as th at supplied by a second camera or an attach ed PC.
44 Assuming that conte nt is enable d on the MCU unit-wide, eac h scheduled co nference can be independently c onfigured to allow content ch annel operations or not.
45 Irrespective of pe r-conference or per-endpoint configuration parameters, if a confe rence is configured to allow content channel ope rations then it is possible to explicitly ena ble or disable in.
46 As well as the conte nt stream (used for sendin g to H.323 end points), the M CU also generat es a Codian prop rietary format version of the c ontent c hannel video whic h can be viewed in conju nction with PC-based video s treaming.
47 The text chat facility provided v ia web browser-based conten t streaming is two-w ay in that any content c hannel streaming view er is able to bot h contribute text and see all m essages typed by othe r viewers.
48 The streaming of the content c hannel is performed u sing the port allocated fo r content rather than the port allocated for streaming. This means that it is possible to stream the con tent channel (for ex ample, to use the video markup feature) for confe rences which do not h ave streaming en abled.
49 You can control m any conferenc e features from the M CU web browser: Adding participants Viewing the partic ipants list Customizing layout v iews Displaying conferenc e statistics Sending messages.
50 To call a particip ant with a SIP endpoint in to an activ e conferenc e: 1. Go to to display t he Conference List . 2. Click a Conference n ame and the n click . o To add an new endp oint (one th at you have not added as a co nfigured endpoin t): i.
51 You can select custom l ayouts to use fo r all conference participants. To u se this option: 1. Go to . 2. Click a Conference n ame and the n click the tab. 3. Click on the layout you w ant to use from those shown in the Availa ble layouts . There are diff erent numbers of panes and pane config urations to choose from.
52 For each pane you can select an alternative setting: <blank>: no participan t appears in this p ane <rolling>: this pane show s conferenc e participants, automat ically changing at the configured "P ane rolling interval" frequency from the page.
53 There is a setting on the MCU' s page to control this be havior called Loud est speaker pane placement beha vior.
54 You can display statistic s about a conferenc e and use the information to quic kly see how many participant s are currently in the confe rence. To access this op tion: 1. Go to . 2. Click a Conference n ame and the n click the tab. If the conference is active, stati stics for that confe rence will be displayed.
55 The current numb er of contributing audio/video particip ants. The largest number o f contributing audio/v ideo particip ants who have been in the conferenc e at the same time.
56 You can send message s to all participan ts in a confe rence simultaneously . To access this option: 1. Go to . 2. Click a Conference n ame and the n click the tab. This message appe ars overlaid on e ach participant's view, including particip ants viewing the conference via streaming.
57 You can view detaile d information about conference pa rticipants: Viewing the confe rence participant list Customizing a participan t's layout display Controlling the near-end c amera Managin.
58 A locked conferenc e is one whe re new participants cannot di al in and you cannot s tart to stream the confe rence. Existing participants and streamin g viewers will main tain their connec tion to the conferenc e. If a conference is locked, an icon will indic ate this on the auto attendant.
59 This indicates th at this participant cor responds to a pre-defined endpoin t. The <name > shown is the endpoint's c onfigured name. Configured endpoint names only display if the partici.
60 Displays the time at wh ich a participant connected to the conference. I f a participant is not yet fully connec ted (for example , if the MCU has called a partic ipant but it has not ye t answered), then th at is indicated he re. The resolution of the p articipant's v ideo stream is also displayed.
61 Indicates that the M CU was un able to open a media channel to the endpoint bec ause the only possible channels i t would be able to open were invalid due to a symmetry c lash.
62 Content is enabled for this conferen ce, but this participant is not allow ed to rec eive it. To enable content for this p articipant, configure th e Content video receive setting for this participant's endp oint (refer to Configuring H.323 endpoints ), or use the enable control fo r an active call.
63 stopped sending vide o keyframe s in response to Fast Update Reque sts (FURs) to avoid de grading the content video se nt to other confe rence participants. The M CU will only ente r this state if the Video fast up date request filte ring setting is Enabled (see Configuring content settings ).
64 Displays a sample s till video capture of the participant. Click the picture to update it. Note that conferenc es that are c onfigured to require encryption do not show previe ws. Also note that previews c an be disa bled on the page (refer to Customi zing the user interface ).
65 audio in the confe rence (stop muting). Prevents others f rom seeing all participants' video co ntribution (mute). Allows others to see all partici pants' video contribution ( stop muting ). The presence of these controls is controlled by the setting on the page (refer to Customizing the use r interface ).
66 configured endpoin t. Note that if the o riginal call to the conferenc e was from the endpoint r ather than the endp oint being invited by the MCU , then for the MCU to recognize it, that endpoin t must be config ured with Call -in match para meters .
67 Every person viewing a conferenc e (whether they are contributing video of their own or using streaming to watch other participants) sees a confe rence layout view. Thi s view div ides the video scree n into a colle ction of panes with participants' video st reams displayed in those panes.
68 Click to choose a pre-configured custom layout for this pa rticipant. See Selecting a custom particip ant layout . Prevents this partic ipant from c hanging their own conference layout using the far-end camera controls on the ir video endpo int. A participant can still change their layout vie w using the web interf ace.
69 You can control the vie wing ang le, zoom, and focus of the camera on a participant's v ideo endpoin t. You can customize this view by choosin g this option: 1. Go to . 2. Click a Conference n ame and the n click on a participant's name. 3.
70 In general, the audio settings are for advanced troubleshootin g. You can vie w these settings by selecting this option: 1. Go to . 2. Click a Conference n ame and the n click on a participant's name. 3. Click the ta b. These settings can help y ou resolv e audio problems in confe rences.
71 You can add a custo m layout to the c hoice of layouts av ailable for this pa rticipant. You can customize this vie w by choosing this option: 1. Go to . 2. Click a Conference n ame and the n click on a participant's name. 3. Click the tab. Indicates whether a custom layout can be u sed for this participant.
72 You can view statistic s about th e video and audio streams betwee n individual participants (e ndpoints) and the MCU by choosing this option: 1. Go t o .
73 The number of pack et errors, inc luding sequence errors, and packets o f the wrong type. You should expect to se e small values for thi s setting. Consistently large numb ers typically imply potential netwo rk problems. Frame errors, as A/B whe re A is the number of frame errors, and B is the total numbe r of frames receive d.
74 The bit rate (in bit s per second) that the M CU has requested tha t the remote e ndpoint sends. The most-recently measured actual bit ra te displays in parenthe ses.
75 Whether or not enc ryption is be ing used on the video transmit strea m to this endpoin t. This field will only appe ar if the encryption key is present on the MCU.
76 Media packet loss reported by rec eiver reports sent to the MCU by the far end. A count of the number of "sender repor t" type RTCP packets rece ived by the MCU. These are typically sent by any dev ice that is sending RTP media. A count of the numbe r of repo rts seen by the MCU that are nei ther sender n or receiver reports.
77 You can send a shor t text message to a specific particip ant currently in the confe rence by ch oosing: 1. Go to . 2. Click a Conference n ame and then clic k on a participant's name . 3. Click the tab. This message appe ars overlaid on the participant's v iew, even if the p articipant is view ing the c onference via streaming.
78 You can view diagnostic s for an indiv idual participant's conn ection to the M CU by choosin g this option: 1. Go to . 2. Click a conferenc e name and then cl ick on a participant's name. 3. Click the tab. This page shows va rious low-lev el details pertaining to the endpoint's communic ation with the MCU.
79 You can move partic ipants betwe en conference s. Participants can be moved to any confere nce, but although participants can be mov ed from auto attendants they c annot be mov ed to them. To move a participant : 1. Go to > . 2. Click and drag the name of the partic ipant to the require d destination confe rence.
80 The Codian MCU allows you to configure auto attendants on it, which allows user s to more e asily join conferenc es. Displaying the auto attendant list Adding and updating an auto attendant Adding a custom b anner You can display an ove rview of the c onfigured auto attend ants on the MCU: 1.
81 attendant with the g atekeeper, it ente rs these states tempo rarily before re- attempting the regist ration. The auto attendant h as been registered successfully with the gatekeepe r and can be contacted using the number indicated. The status of an au to attendant with respec t to its SIP registration.
82 Auto attendants simplify the way partic ipants can join confe rences. By calling an auto atten dant using their vide o endpoint, a participant can choose from menu options and join or start confe rences. No gat eway or gatekee per is required. (The au to attendant is c onfigured on the M CU.
83 have enabled on the page. W hen using port reservation mode, the re can be no ad hoc conferences. For mo re inform ation about port reservation, refe r to Reservation of MCU me dia ports . If Enabled, displays ad hoc conferen ces as well as scheduled confe rences as optio ns on the auto attendant.
84 You can add a custo m banner image to any auto attendan t configured on the MCU as follo ws: 1. Go to . 2. Click the tab. 3. Click the name of a configured auto attendant. 4. Click the tab. 5. Refer to the table be low to determine the most appropri ate settings.
85 To display the Endpoin t List, go to . The Endpoint List di splays all endpoints that have bee n configured withi n the MCU. To add a new H.323 e ndpoint, select . To add a new SIP endp oint, sele ct . To add a new VN C endpoint, select . To delete configured endp oints, chec k the ones you w ant to delete and sele ct .
86 You can configure H .323 endpoints to work with the M CU by choosing . This makes it easier to add endpoints to conferenc es because you can c hoose names from a list rather th an adding netwo rk addresses. A Codian IP VCR can be confi gured as an H.
87 Choose whether to use the uni t-wide setting for motion/sharpness tr ade off, or config ure an individual setting for u se with this endpoin t. Choose from: <use box-wide setting > : this is the default value. In this case, the conn ection to the endpoint will use the mo tion / sharpness tradeoff setting from the page.
88 Whether this endpoint is allowed to rece ive a separate content stre am when in a conferenc e. This setting is provide d to allow y ou to individually config ure whether or not an endpoint is allowed to receive c ontent from a conference.
89 to the conference . For example , you can mute video from an endpoint i f somebody wants to see the conference , but not be see n themselves. You can mute both audio and video if requi red. This can be altered during the course of the conference by going to and clicking on the name of a confe rence and altering this participant's setting s.
90 To configure the SIP endpoints to wo rk with the MCU, go to . This makes it e asier to add endpoints to confe rences beca use you can choose n ames from a list rather than adding network addre sses. Refer to the table below for tips on adding a SIP endpoin t to the MCU.
91 endpoint. In this ca se, to use c all-in match parameters, leave the IP addre ss field blank and enter the correc t username. T he call will be matched by username. When using LCS, the username that will be matched is the user 's display name (e.
92 Whether this endpoint is perm itted to contribute the conference content channel. Choose from: < use conference defa ult >: this endpoint will use the Content contribution f rom endpoin ts setting from the per-conference c onfiguration.
93 seen in the conferenc e, but do es not want to contribute verbally. You can mute both audio and video if required. This can be altered during the course of the confe rence by goin g to and clicking on the n ame of a confe rence and altering this participan t's settings.
94 You can configure a VNC (Virtual Netwo rk Computing ) endpoint on the MCU by choosing . This makes it easier to add a V NC session to confe rences because you can choose its name from a list rather than type its network address. You can add VNC e ndpoints to the MCU.
95 You can configure the Codian MCU to work with one or more H .323 gateways. The MCU can then effe ctively call through these configured g atew ays to one or more endpoin ts which are re gistered with the gateway but w ould not be reachable directly from the MCU.
96 You can configure the Codian MCU with one or mo re H.323 gateways: To add an H.323 ga teway, go to . After entering the settings de scribed below, click . To update an existing H .323 gateway, go to and click on a g ateway name. After updating the settings described below, click .
97 The MCU contains a built-in gatekeepe r with which devic es can register multiple IDs. ID s can be numbe rs, H.323 IDs (e.g. Fredsendpoin t) or prefixe s. Up to 25 devices can be registered with out a feature key. Fe ature keys c an be purchased to increase this number .
98 Configures the built-in gatekeepe r to send (or not to send) LRQs regarding unknown IDs to its neig hbor(s). Choose from the op tions: Disabled : The MCU will onl y respond to LRQs about IDs registered with itself. It will not forward LRQs abou t IDs that are not regis tered with itself to neighboring gatekeepers.
99 Below these summ ary figures is a table showing individu al registrations. Registrations can be vie wed by registered ID (the "ID view ") or by device (t he "Registration vie w"), giving com plete and easily search able lists. Switc h betwe en the views by clic king on the appropria te button.
100 The MCU is pre-config ured with two user accounts ("admin " and "guest"), but you can also add o ther users (see Adding and updating users ). Refer to the table below for des criptions of the pre-configu red users. The MCU must h ave at least one configured user with administrator p rivileges.
101 1. Go to . 2. Click . 3. Refer to the table be low to determine the most appropriate setting s for the user. 4. After entering the settings, click . The log-in name used to access the M CU web browser. This is fixed at "guest" The required passwo rd, if any.
102 Every configured user in the MCU h as an associated privile ge leve l. There are seven defin ed privilege levels which determine the amoun t of control the user has over the MCU and its settings .
103 Users with this p rivilege leve l can: Change their own pro file ( ) View the list of active confere nces ( ) View conference s via streamin g ( ) View participant lists for active conferences ( ).
104 The User list gives you a quick overview of all c onfigured users on the MCU and provide s a brief overvie w of some of their settings. To displ ay this list, go to . Refer to the table below for assistance. The log-in name that the user ne eds to use to acce ss the MCU we b browser.
105 You can add users to and update users on the MCU. Althoug h most information is ide ntical for both t asks, some fields differ. The MCU suppo rts up to 200 user s. To add a user: 1. Go to . 2. Click . 3. Complete the fields refer ring to the table below to determine the most app ropriate settings for the user.
106 Associates an E.164 tele phone num ber with a user account. If the MCU rec eives a call from the E.164 phone number provided, i t 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 c ompleted.
107 You can make some changes to your use r profile. To do this , go to . Refer to the table below for tips. Your name, which ide ntifies you to other users. Changing this field doe s not change your log-i n User ID. You can enter a new password. Verify the new p assword.
108 You can modify the glob al conferenc e settings for the MCU choosing by . However, many of these values can be overwritten by othe r MCU settings, for example individual confe rence, participan t, or endpoint settings. In this section: Conference settings Advanced settings Refer to this table for assistance configuring the confe rence settings.
109 Identifies the netwo rk capacity (measu red in bits per second) used by the media channels established by the MCU to a single participant. When the MCU m akes a call to an endpo int, the MCU chooses the maximum bandw idth that is allowed to be used for the media channels whic h comprise that call.
110 participants join and leave the conference. : audible sta tus messages for ex ample indicating to a participant that he i s the only participan t in a conference. Allows various in-confere nce icons to be displayed on particip ants' endpoints.
111 video port to the pa rticipant, or the participant has muted their endpoint's video channel to the M CU. : an icon appea rs in the top left of the conference display to indicate if there are any stre aming participants in the c onference. If enabled, the icon will onl y display if there are one or more streami ng participants.
112 This setting controls for how long (if at all) the Codian logo is displaye d to par ticipants joining a conference. Choose f rom: When displayed, the Codian log o appears in the bottom right of a p articipant's c onference display. Allows you to enter a message that will be seen by participants joinin g confere nces on the MCU.
113 Determines which audio codecs the MCU advertises to remote en dpoints, restricting the endpoints' choice of ch annels available fo r sending audio data to the MCU. Note that the Custom c odec selection setting for an individual endpoint will ov erride this unit-wide setting for calls from that endp oint.
114 The MCU will heavily favor sendi ng 448p or w448p vide o (resolutions of 576 x 448 and 768 x 448 pix els respectively) to those endpoints that are known to work bes t with these resolutions.
115 Enables the MCU to request that the endp oint send lower speed video if it fails to re ceive all t he packets which c omprise the far end's video stream. The MCU can send these messages to endpoin ts requesting that the b andwidth of the video that they are sending be decreased based on the quality of video rec eived by the MCU.
116 When pane placement is in use , this option affects the potential duplic ation of participants that are specifically placed in vie w pane s with view panes configured to show the confere nce's current active speaker.
117 Select the de lay to be applied to audio relative to video. A setting used only t o rectify som e types of 'lip sync' issues sometimes found with c ertain endpoints. Leave at default setting , unless advised to alter it by Codi an technical support o r a reseller.
118 conference. protected, regardless of how participants connect, ensure you set this option . When this option is set , participants c alling into a protected conferenc e will be presen ted with PIN- entry screen instead o f the nor mal conference view.
11 9 To configure gatek eeper settings, go to . You can configure the M CU to use a gateke eper, which can make it easier for end-users to join conferenc es using directory numbers rather than requiring them to know the IP address or host name of the M CU.
120 having specific proble ms using the Cisco Gatek eeper (with or without a service prefix) , in which case use Gateway (Cisco GK compatible) using the VCON MXM Gatekee per (with or without a service.
121 associated numeric ide ntifier. If H.323 gatekeeper usage is disabled, this field w ill have no effect. Note that if you are also inten ding to use the MCU service prefix ( see below ), Codian recommends that you set both prefixes to the same number.
122 page (see Config uring global conference setting s ). This field will have no e ffect if H.323 Ga tekeeper usage is set to Disabled . Select this option if you want the MCU to inform the gatekeepe r about its availabi lity or non- availability.
123 The MCU also displ ays brief status in formation about i ts registrations with the config ured gatekeepe r. To display a comple te list of all ID s that the MCU is attempting to registe r with the configu red H.
124 Displays whether the gatekeeper is config ured to send resource avail ability indications and if it is, it displays the current state of th e resource availability status of the MCU. The possible statuses are: Displays the numbe r of E.164 numbe rs plus H.
125 To display a comple te list of all ID s that the MCU is attempting to register with the configu red H.323 gatek eeper, go to and clic k , shown next to the Number of active registrations status ent ry. You are take n to the page. This page show s the complete se t of IDs that the M CU is attempting to register with the configured H.
126 To configure SIP setting s on the MCU, go to . To allow conferenc e participants with S IP endpoints to conn ect to the MCU by dialing a di rectory number ra ther than an IP address, you must configure a SI P registrar. The settings on this page control the MCU's interaction with the SIP registrar and with SIP e ndpoints.
127 If you are using Mic rosoft OCS or LCS, you need to enter the full UR I (for exa mple, MCU@mylcs.com ). Note that this username will be used anywhere where one is requi red in a SIP call; for example, it will be used where authentication is required with a SIP server where no registr ar is used.
128 encryption. Where encryption is requi red in the conference c onfiguration, a SIP call mus t use SRTP. For more info rmation about SIP encryption, refer to Configuring encry ption settings . The MCU can ac cept connections on T CP, UDP, and TLS providing those service s are enabled on the page ( Configuring network services ).
129 You can configure two streami ng options that will be available for use rs to choose betwe en whe n streaming conferences. For e ach streaming option, you must choose a media player and a bi t rate. You can configure the MCU to support either (or both of) unicast or multic ast streaming.
130 Sets the audio and vide o combination to use, and the overall medi a bit rate. Typically, when two s treaming rates are use d, one is set up as a low bit rate com bination and the other configured to use a higher bit ra te.
131 The content settings affect the be havior of the MCU w ith regard to H.239 and BFCP (Bin ary Floor Control Protocol). H.239 is the protocol th at allows for an additional video ch annel (known as the content channe l) alongside the main video channel in a video-confe rencing call that uses H.
132 This field sets which v ideo code c is used for conferences' conte nt video stre ams. A single content video stream is used fo r each conference, and this stream will be sent to all viewing endp oints. If an endpoint is unable to receive conte nt video using th e codec config ured here, no content channel will be opened to that endpoint.
133 (see above). In these cases, if this option is set to Enabl ed , the MCU will display the content c hannel video within a pane of the currently selected confe rence layout.
134 You can configure the MCU to enc rypt connections to and from H.323 and SIP endpoints. The encryption tec hnology that the M CU uses for enc ryption to and f rom H.
135 Whether the MCU is able to u se encryption or not. When encryption sta tus is Enabled , the MCU advertises itself as being able to use enc ryption and will use encryption if requ ired to do so by an endpoint. If this setting is Enabled , you can en able or disable the use of enc ryption on a pe r- conference basis.
136 The MCU suppor ts the use of encryption with SIP. Whe n encryption is in use with SIP, the audio and vide o media are encrypted using Secure Real-time Transpor t Protocol (S RTP). When using S RTP, the default mec hanism for exchanging ke ys is Session Desc ription Protocol Sec urity Description (SD ES).
137 To configure the netwo rk setti ngs on the MCU and ch eck the network st atus, go to or . The MCU has two E thernet interface s, Port A and Port B . The configuration pages for the tw o interfaces look and behave similarly, and so are described tog ether.
138 Identifies the IP add ress of the name serve r. Identifies an option al second name server . The secondary DNS server is only used if the first is unavailable. If the first returns tha t it does not know an address, the secondary DN S server will not be queried.
139 Identifies the connec tion duplex mode : Both devices can send data to e ach other at the same time Only one device c an send to the oth er at a time The duplex setting mu st match that o f the device to which this port is connected. You only need to sele ct this op tion if you have chosen manua l Ethernet settings, as described above.
140 If the Video Firewall featu re is enabled (see Upgr ading the firmw are ), 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 settin gs are configured cor rectly, or you may be unable to make calls to or from the MCU or access the web interf ace.
141 In this section you can control how IP packe ts should be di rected out of the M CU. You should only change this configuration if you have a good underst anding of the topolog y of the network( s) to which the MCU is conn ected.
142 The default route i s configured autom atically in corresponde nce with the default ga teway preference field (see Po rt preferences ) and cannot be dele ted. Any packets not covered by manually configured rou tes will be routed according to this route.
143 To configure IP service s, go to . Use this page to cont rol the type of servic es that may be accessed via Etherne t Ports A and B. You might use this if one Ethernet port i s connected to a netw.
144 Allow/reject incoming calls to the MCU using H.323 or change the port that is used fo r this service. Disabling this option wil l not preve nt outgoing calls to H.323 devic es being made by the MCU. That is, the MCU will need to dial out to conference participan ts who are using H.
145 Allow/reject incoming and outgo ing calls to the MCU using SIP over UD P or ch ange the port that is used for this service . Disabling this option wil l prevent calls u sing SIP over UDP. If a port is disabled, this option will be unavailable. You must use the same port num ber for both Port A and Port B.
146 To configure monito ring using SNMP, go to . The MCU sends ou t an SNMP trap w hen the device is shut down or s tarted up. The SMNP page allows you to set various parameters; wh en you are satis fied with the settings, click .
147 Select this che ck box to enable the MCU to send traps. If you do not chec k this box, n o traps will be sent. Select this che ck box to enable authentication failure traps. You cannot select this check box unle ss you have selected to Enable tra ps above.
148 To configure Quality of Service (QoS ) on the MCU for audio and video, go to . QoS is a term that refe rs to a ne twork's ability to customi ze the treatment of specific classes of data. For example , QoS can be used to p rioritize audio tr ansmissions and video t ransmissions over HT TP traffic .
149 ToS configuration rep resents a tr adeoff between the abstract parameters of p recedenc e, delay, throughput, and reliability. ToS uses six out of a possible e ight bits. The MCU allow s you to set bits 0 to 5, and will place zeros for bits 6 and 7.
150 The system date and time for the MCU can be set manu ally or using the Network Time Protocol (NTP). To configure Time setting s, go to . Note that changing the time or NTP settings will h ave an effe ct on the recorded times in the Call Detail Records log.
151 If you need to upg rade the firmware o r activate features on the MCU, refer to these topic s: Upgrading the m ain MCU softw are image Upgrading the lo ader software image Enabling MCU fe atures Storing user passwo rds securely The main MCU softw are imag e is typically the only firmware c omponent that you will ne ed to upgr ade.
152 The MCU requires activ ation before most of its features can be used. (If the M CU has not b een activated, the banner at the top of the we b interface will show a prominent w arning; in eve ry other respect the w eb interface will look and behave normally.
153 It is sometimes necess ary to shut down the MCU, gener ally to restart as part of an upgrade (see Upgrading the firmware ). You should also shut down th e MCU befo re intentionally remov ing power fro m the MCU.
154 The General Status displays an ov erview of the M CU status. To access this information, go to Refer to the table below for details o f the information displ ayed The specific Codi an MCU model. The unique serial numb er of the MCU. The installed softw are version.
155 The conference status page displays the status of active and comple ted conferences and vid eo and audio proces sing. To access this info rmation, go to .
156 shows the number of video ports in use. This corresponds to the number of connected participant s that are eithe r contributing or being sent video, plu s the number of conference s for whic h streaming is active . This value is shown i f the MCU is not operating in Port rese rvation m ode , and shows the number of audio-only ports in use.
157 Video status displ ays an overvie w of current video resou rce use. The number of vide o streams being received by the MCU. Unicast indicates vide o streams sent dire ctly to the MCU (incoming ) or directly to the endpoints (outgoing) rather than multicast stream s broadcast to the netwo rk and captured o r sent by the MCU.
158 The page shows v arious status i tems related to a conference's content channel. To view this page, go to click the name of the conference about which you w ant more information and on the tab, click the Content channel link.
159 The Health Status di splays information about the ha rdware comp onents of the MCU. To access this information, go to Note that the Worst status seen conditions are tho se since the l ast time the unit was restarted. To reset these values , click .
160 The port provision of the various M CU models is shown in the table below . Each video por t can be used by one video-conferenc ing participant . Each audio port c an be used by one voice-only participant in a vide o conference.
161 If you are experienc ing compl ex issues that require advanced trouble shooting, you may need to colle ct information from the MCU log s. Typically, you will be working with Te chnical support who can help you ob tain these logs. The last 2000 status mes sages gene rated by the MCU are di splayed in the Eve nt log page.
162 The H.323/SIP log p age records ev ery H.323 and SIP message rec eived or transmitted from the MCU. The log can be exported in an .xml file. By default the H.323/SIP log is disabled because i t affects perfo rmance, but Techinc al support may ask you to enable it if there is a problem with a unit in your netwo rk.
163 You can send the Event log to one or mo re syslog servers on the network for storage o r analysis. To configure the syslog facility, go to In this section: Syslog settings Using syslog Refer to this table for assistance wh en configuring Syslog settings: Enter the IP addresse s of up to four Syslog receiver hosts.
164 The events that are fo rwarded to the syslog rece iver hosts are controlle d by the event log c apture filte r. To define a syslog serve r, simply enter its IP address and then click . The number of packets sent to each config ured host is displayed ne xt to its IP addre ss.
165 The MCU impleme nts SIP as d efined in RFC 3261. Any p roduct wishin g to establish SIP c alls with the MCU should implement INVITE, ACK, BYE, and CAN CEL messages alo ng with responses from 1xx to 6xx. The MCU acts as a client and does not return 5xx and 6xx responses itself; however, proxies and o ther interme diaries may do so.
166 The MCU is able to ge nerate Call Det ail Records (CD R) which may be used fo r auditing a nd billing purposes . When logging is enabled, rec ords are ge nerated wheneve r a conferenc e starts or finishes, wh en participants join and le ave conferences and so forth.
167 This table shows the logged Call De tail Records, subjec t to any filtering applie d (see Call Detail Record log controls , above). The fields displ ayed and the list 's associated cont rols .
168 The CDR log time stamp is stored in UTC ti me and not local time like the Eve nt log, but co nverted to local time when displayed in the CDR log . Changing the time and NTP’s U TC Offset (on the.
169 In this section: Controlling the auto-ref reshing of status pages on the M CU Controlling the displ ay of thumbnail previe w images Controlling the confirm ation of participant disconnections Cont.
170 The default settings for the MCU allow you to disconnec t, without confirm ation, individual participan ts from a conference on the page. On the page, you c an configure the M CU to display an "Are you sure?" confirm ation box when attempting to di sconne ct an individual participant.
171 The default set of voice prompts is provided in US Eng lish and is the standard set of voice p rompts supplied with the MCU. These are spoke n by a f emale voice in Americ anized English. If your unit is using customized voice prompts and you want to retu rn to using the default set of voic e prompts: 1.
172 To expand any list to show all c ustomizations, click ; you may subseque ntly hide it again by clic king . In the expanded sta te, the table show s, for each customiz ation, a description o f the file, the standard MCU filename for the customiz ation, and the length and date modified (uploaded) of alternative customization s present.
173 5. When you have loc ated the file you wish to uplo ad, click . If the upl oad is successful, a page displaying the size of the file upl oaded will be displaye d; otherwise an error will be sho wn. If the upload fails, che ck your audio file match es the specific ation above be fore contacting your support representative.
174 Below is a complete list of the voice prompts that m ay be customized. The default wording is shown for each p rompt. You do not have to use exactly the sa me wordings if they are not appropri ate for your nee ds, and are provide d only as a guide.
175 It is important to minimi ze backg round noise (hiss) as mu ch as possible. This includes ambie nt noises such as road noise and slamming doo rs etc. but also try to keep fan noise and similar to a minimum. When played back by the MCU, samples with backg round noise are ve ry apparent.
176 There are three cus tomization lev els on the unit (for voice-pr ompts, web interface, help page s, and text messages): the factory default files that are provided in US English localization files.
177 You can save the config uration of the M CU to a file th at you can store aw ay from the unit. If necessary this file c an be used to restore the configuration of the unit. 1. Ensure that the FTP service is enabled on the page. 2. Connect to the M CU using an FTP client.
178 The page c an be used for troubleshoo ting issues that arise because of problems in the ne twork between the MCU and a remote vide o conferencing de vice being c alled (or a device from which a user is attempting to call the MCU).
179 If the MCU has the S ecure management ( HTTPS) or Encryption feature key installed, and you enable the secure web service on the page, you will be able to ac cess the web interf ace of the MCU using HTTPS. The MCU has a local c ertificate and private key pre-installed and this will be used by default when you acce ss the unit using HTTPS.
180 If your organization has bought a certificate, or you have your own way of generating certificates, you can upload it. B rowse to find the certificate file.
181 Please refer to the following sec tions for details of where to get further help and for additional software lic ense information: Codian Software licenses The Codian MCU fi rmware is Copyrigh t © Codian 2003-2008 e xcept where spec ifically mentione d below.
182 Copyright © 1999-2004 The NetBSD Foundation, Inc. All rights reserved. Redistribution and use in source and binary fo rms, with or without modification, a re permitted provided th at the following conditions a re met: 1.
183 This software is prov ided "as i s," without warranty of any kind, express or implied. In no e vent shall Info-ZIP or its contributors be held liable for any direct, i ndirect, incident al, special or conse quential dam ages arising out of the use of or inability to use this software.
184 Permission is NO T granted for the use of any IJG autho r's name or company name in adver tising or publicity rela ting to this software o r products deriv ed from it. This softw are may be refer red to only as "the Independe nt JPEG Group's software" .
185 Copyright (C) 1995-1998 Eric Young ( e ay@cryptsoft.com ) All rights reserv ed. This package is an SS L implementation wri tten by Eric Youn g ( eay@cryptsoft.
186 Copyright © 1995-2003, SPIRIT The Codian MCU inc ludes a G.728 audio codec used unde r license from Spiri t Corporation. Copyright (c) 2001, D r Brian Gladman, Worcester , UK. All rights reserve d. The free distribution and use o f this software in bo th source and binary form is allowed (wit h or without c hanges) provided that: 1.
187 This software is prov ided 'as is' with no explicit o r implied wa rranties in respect of its properties, inc luding, but not limited to, correctne ss and/or fitness for purpose. Issue Date: 26/08/2003 Copyright (c) 2002, D r Brian Gladman, Worcester , UK.
188 THE SOFTWARE IS P ROVID ED "AS IS", WITHOU T WARRANT Y OF ANY K IND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANT ABILITY, FI TNESS FOR A PARTICULAR PUR POSE AND NONINFRIN GEMENT.
Een belangrijk punt na aankoop van elk apparaat TANDBERG MCU 4500 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen TANDBERG MCU 4500 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens TANDBERG MCU 4500 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding TANDBERG MCU 4500 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over TANDBERG MCU 4500 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van TANDBERG MCU 4500 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de TANDBERG MCU 4500 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met TANDBERG MCU 4500 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
