TANDBERG CODIAN MCU 4500 Manuel D’Utilisation
126
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.
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.
A SIP call will select the audio and video codecs to use from the set of those both allowed on the
page and supported by SIP, unless the call is with an endpoint configured with a Custom codec (refer to
Refer to this table for assistance configuring the SIP settings. After making any configuration changes, click
.
Specifies the level of SIP registration for the
MCU.
MCU.
Can be set to:
No registration: The MCU will not
register with the SIP registrar. This
means that a user with a SIP endpoint
can only connect to the MCU by dialing
its IP address or hostname
means that a user with a SIP endpoint
can only connect to the MCU by dialing
its IP address or hostname
Register MCU only: Enables conference
participants to dial in to the auto
attendant of the MCU
participants to dial in to the auto
attendant of the MCU
Allow conference registration: Enables
conference participants to dial directly in
to conferences. For this to work, you
must configure the SIP registrar with
conference IDs
to conferences. For this to work, you
must configure the SIP registrar with
conference IDs
Identifies the network address of the SIP registrar
to which MCU registrations should be made.
to which MCU registrations should be made.
This can be specified either as a host name or as
an IP address. This field will have no effect if
an IP address. This field will have no effect if
is set to No registration.
Choose between:
Standard SIP: for non-Microsoft SIP
registrars
registrars
Microsoft OCS/LCS: for Microsoft SIP
registrars
registrars
Your choice is dependent on the type of SIP
registrar you are using.
registrar you are using.
If you are using Microsoft OCS or LCS, you will
also need to configure the OCS or LCS to
recognize the IP address of the MCU and treat it
as authenticated.
also need to configure the OCS or LCS to
recognize the IP address of the MCU and treat it
as authenticated.
This field will have no effect if
is set to No registration.
Select this option to force the MCU to present its
local certificate when registering with the SIP
registrar.
local certificate when registering with the SIP
registrar.
Often, the SIP registrar will not require the local
certificate from the MCU. Only select this option
if your environment dictates that the SIP registrar
must receive the local certificate.
certificate from the MCU. Only select this option
if your environment dictates that the SIP registrar
must receive the local certificate.
The login name 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.
create a login for each device.