Maintenance Manual
Username The MCU uses this name if it
registers with a SIPregistrar.
The MCU uses this name to
authenticate with the SIPdevice
(registrar, trunk destination, or
endpoint) if that device requires
authentication.
The MCU will use this name to register itself with the
SIPregistrar if you have enabled SIPregistration. It will not
register itself if you do not provide this, but it will still be able
to register individual conferences (assuming they are enabled
to register and have numeric IDs).
If a conference does not have a numeric ID, then it cannot
register. Calls out from such a conference will appear to
come from the MCU's own SIPregistration (this_
username@outbounddomain). It is impossible for a participant to
call into such a conference because it does not have a
numeric ID.
If you enter a full URI here (e.g. host@domain), then the MCU
will ignore the Outbound domain setting.
Password The MCU uses this password to
authenticate with the SIPdevice
(registrar, trunk destination, or
endpoint) if that device requires
authentication.
The SIPdestination may not require authentication; if it does,
you need to configure it to accept a log in from this username
and password combination.
Outbound
transport
Select the protocol that the MCU
will use for outbound calls (and
registrations, if enabled).
One of TCP, UDP, or TLS.
The MCU uses this protocol for communicating with the
SIPregistrar or trunk destination.
If you have the encryption feature key installed and want to
encrypt signaling, select TLS.
The MCU accepts incoming connections on whichever
protocol the connection uses (TCP, UDP or TLS), and will
respond using the same protocol, irrespective of this
Outbound transport setting. Make sure that you enable those
services on the Network > Services page.
Use local
certificate
for outgoing
connections
and
registrations
Check this option to allow the MCU
to present its local certificate
when registering with the SIP
registrar (via TLS) or making
outgoing TLS calls. With this
option unchecked, the MCU will
never present its local certificate,
even if requested to do so.
This option should be checked if TLS is in use.
Allow
numeric ID
registration
for
conferences
This field controls whether any
conferences' configured numeric
IDs are allowed to be registered
with the registrar.
This setting is the global control
that allows or disallows
conferences to be registered with
the SIP registrar.
Individual conferences will be
registered or not depending on the
per-conference Numeric ID
registration setting which is on
the Add conference page for
scheduled conferences and for ad
hoc conferences it is in the ad hoc
conference template.
This would normally be Enabled; by setting it to Disabled, an
administrator can prevent users from adding to the set of IDs
registered with the configured registrar, even if those users
enable the registrar Numeric ID registration setting for
conferences they control. This may be desired when working
with certain types of SIP registrars whose behavior in some
modes is to disconnect active calls when the set of registered
IDs changes.
This setting affects both the registration of numeric IDs
configured for scheduled conferences and the registration of
the numeric IDs of adhoc conferences.
This field will have no effect if SIP registrar usage is set to
Disabled.
175
Cisco TelePresence MCU Series Online Printable Help