Filter
Top Products
D14324.04—DECEMBER 2009
32
Profile series with Codec C60
Administrator Guide
Contents Introduction Getting started About the menus The settings menu Settings Library Cameras Appendices Contact us
Conference [1..1] DoNotDisturb Mode: <On/Off>
The Do Not Disturb setting determines whether or not there should be an alert on incoming calls.
On: Set to On when you want no alert to incoming calls. The calling side will receive a busy signal when
trying to call the codec.
Off: This is the default setting. The DoNotDisturb is automatically turned Off if the codec receives any IR
signal from the handheld remote control.
Example: DoNotDisturb Mode: Off
Conference [1..1] Encryption Mode: <Off/BestEffort>
BestEffort: The system will use encryption whenever possible.
In Point to point calls: If the far end system supports encryption (AES-128), the call will be encrypted. If not,
the call will proceed without encryption.
In MultiSite calls: In order to have encrypted MultiSite conferences, all sites must support encryption. If not,
the conference will be unencrypted.
Icons on screen: A padlock with the text “Encryption On” displays on screen, for a few seconds, when the
conference starts.
Off: The system will not use encryption.
Example: Conference 1 Encryption Mode: BestEffort
Conference [1..1] FarEndControl Mode: <On/Off>
Lets you decide if the remote side (far end) should be allowed to select your video sources and control your
local camera (pan, tilt, zoom).
On: Set to On when you want the the far end to be able to select your video sources and control your
local camera (pan, tilt, zoom). You will still be able to control your camera and select your video sources as
normal.
Off: When set to Off the far end can not access any of the features above on your system.
Example: Conference 1 FarEndControl Mode: On
Conference [1..1] IncomingMultisiteCall Mode: <Allow/Deny>
The Incoming Multisite Call setting determines whether or not the system should accept incoming calls to an
already active conference.
Allow: When set to Allow, and with an ongoing MCU call/conference, the user can accept another incoming
call. This will result in the incoming call being added to the MCU conference.
Deny: The system will not accept incoming calls when you are in a call. The calling side will receive a busy
signal.
Example: Conference 1 IncomingMultisiteCall Mode: Allow
H323 Profile [1..1] Authentication LoginName: <S: 0, 50>
The system sends the Authentication Login Name and the Authentication Password to a H.323 Gatekeeper
for authentication. The authentication is a one way authentication from the codec to the H.323 Gatekeeper,
i.e. the system is authenticated to the gatekeeper. If the H.323 Gatekeeper indicates that no authentication
is required, the system will still try to register. Requires the H.323 Gatekeeper Authentication Mode to be
enabled.
Format: String with a maximum of 50 characters.
Example: H323 Profile 1 Authentication LoginName: “”
H323 Profile [1..1] Authentication Password: <S: 0, 50>
The system sends the Authentication Login Name and the Authentication Password to a H.323 Gatekeeper
for authentication. The authentication is a one way authentication from the codec to the H.323 Gatekeeper,
i.e. the system is authenticated to the gatekeeper. If the H.323 Gatekeeper indicates that no authentication
is required, the system will still try to register. Requires the H.323 Gatekeeper Authentication Mode to be
enabled.
Format: String with a maximum of 50 characters.
Example: H323 Profile 1 Authentication Password:
H323 Profile [1..1] Authentication Mode: <On/Off>
On: If the H.323 Gatekeeper Authentication Mode is set to On and a H.323 Gatekeeper indicates
that it requires authentication, the system will try to authenticate itself to the gatekeeper. Requires the
Authentication ID and Authentication Password to be defined on both the codec and the Gatekeeper.
Off: If the H.323 Gatekeeper Authentication Mode is set to Off the system will not try to authenticate itself to
a H.323 Gatekeeper, but will still try a normal registration.
Example: H323 Profile 1 Authentication Mode: Off
H323 Profile [1..1] CallSetup Mode: <Direct/Gatekeeper>
The H.323 Call Setup Mode defines whether to use a Gatekeeper or Direct calling when establishing H323
calls.
Direct: An IP-address must be used when dialling in order to make the H323 call.
Gatekeeper: The system will use a Gatekeeper to make a H.323 call. When selecting this option the H323
Profile Gatekeeper Address and H323 Profile Gatekeeper Discovery settings must also be configured.
NOTE! Direct H.323 calls can be made even though the H.323 Call Setup Mode is set to Gatekeeper.
Example: H323 Profile 1 CallSetup Mode: Gatekeeper
H323 Profile [1..1] Gatekeeper Address: <S: 0, 64>
Specifies the IP address of the Gatekeeper. Requires the H.323 Call Setup Mode to be set to Gatekeeper
and the Gatekeeper Discovery to be set to Manual.
Format: String with a maximum of 64 characters.
Example: H323 Profile 1 Gatekeeper Address: “10.47.1.58”
The H323 Profile settingsThe Conference settings, continued...
Contents
Introduction
Getting started
About the menus
The Settings menu
The Settings library
Cameras
Appendices
Contact us
The Settings library