Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Managing endpoints
Cisco TelePresence MCU 4.3 Product administration guide
Page 111 of 242
Content
negotiation
negotiation
This field allows the MCU to be
configured so that content can
be exchanged with third party
MCUs in multi-level cascaded
conferences over H.323.
Choose from:
configured so that content can
be exchanged with third party
MCUs in multi-level cascaded
conferences over H.323.
Choose from:
n
As master: The MCU only
acts as master in H.239
token negotiation.
acts as master in H.239
token negotiation.
n
As slave: The MCU acts as
the slave in H.239 token
negotiation and can send
content to a master unit if it
accepts the token request.
the slave in H.239 token
negotiation and can send
content to a master unit if it
accepts the token request.
n
Mimic slave: The MCU
mimics a slave during H.239
token negotiation, but does
not actually act as a slave.
The MCU still tries to send
content to all other
endpoints/units even if the
third party MCU rejects the
token request.
mimics a slave during H.239
token negotiation, but does
not actually act as a slave.
The MCU still tries to send
content to all other
endpoints/units even if the
third party MCU rejects the
token request.
When exchanging content with an endpoint in a H.323
call, the MCU acts as a master unit and the endpoint as a
slave unit for the purpose of H.239 token negotiation.
However, in order for the MCU to exchange content with a
cascaded third party MCU, the MCU must appear to the
third party MCU to be a slave unit. The MCU can be
configured as a true slave, in which case content will only
be sent if the third party MCU master accepts the token
request, or to mimic a slave (content is sent to all other
connected endpoints even if the third party MCU rejects
the token request).
call, the MCU acts as a master unit and the endpoint as a
slave unit for the purpose of H.239 token negotiation.
However, in order for the MCU to exchange content with a
cascaded third party MCU, the MCU must appear to the
third party MCU to be a slave unit. The MCU can be
configured as a true slave, in which case content will only
be sent if the third party MCU master accepts the token
request, or to mimic a slave (content is sent to all other
connected endpoints even if the third party MCU rejects
the token request).
Custom
codec
selection
codec
selection
Can be used to ensure only
specific codecs are permitted
on calls to (and received from)
this endpoint.
specific codecs are permitted
on calls to (and received from)
this endpoint.
If Enabled, you can select which codecs are allowed to be
used when communicating with this endpoint. This setting
overrides the MCU-wide codec selection on the
used when communicating with this endpoint. This setting
overrides the MCU-wide codec selection on the
Settings
> Conference
page.
Configuring SIP endpoints
To configure the SIP endpoints to work with the MCU, go to
Endpoints > Add SIP
. This makes it easier to
add endpoints to conferences because you can choose names from a list rather than adding network
addresses.
addresses.
Refer to the table below for tips on adding a SIP endpoint to the MCU. After entering the settings, click Add
endpoint.
endpoint.
Field
Field description
Usage tips
Name
The name of the endpoint.
Address
The IP address, host name,
directory number, or SIP URI (in
the format 1234@cisco.com).
directory number, or SIP URI (in
the format 1234@cisco.com).
The address of the SIP endpoint can be a directory number
if you are using a SIP registrar. Note that square brackets
are mandatory for IPv6 addresses.
if you are using a SIP registrar. Note that square brackets
are mandatory for IPv6 addresses.