Maintenance Manual

Prefix for
MCU
registrations
Specifies an optional group
of digits that are added to the
beginning of each
conference or auto
attendant's numeric identifier
before registering it with the
H.323 gatekeeper.
Conferences and auto attendants registered with a gatekeeper have
a numeric identifier. The numeric identifier is a unique sequence of
digits entered from a video-conferencing endpoint to connect
directly to the conference or auto attendant. This eliminates the
need for users to navigate additional menus or to know the IP
address of the MCU.
To usefully partition the dialing space, you might need to ensure that
all registrations from a single MCU start with the same sequence of
digits.
Using registration prefixes also can benefit large-scale dial plan
changes. For example, you can change all MCU registrations to
begin with "121" instead of "11" by changing a single MCU
configuration field rather than individually amending every
conference or auto attendant's associated numeric identifier.
If H.323 gatekeeper usage is disabled, this field will have no effect.
Note that if you are also intending to use the MCU service prefix (see
below), Cisco recommends that you set both prefixes to the same
number.
MCU
service
prefix
If required, specify a group of
digits which the H.323
gatekeeper may use to
identify calls to be routed to
the MCU.
This field is optional. If set, users dialing any number beginning with
this prefix will have their call directed to the MCU. This might be
useful if you want to create conferences in response to unknown
E.164 numbers.
Any numbers following the prefix will be identified by the MCU as a
conference or auto attendant number. For example, if a conference
has Numeric ID "3333" and you have set the service prefix to be
"121", then a user dialing "1213333" will be connected to that
conference.
This field will have no effect if H.323 gatekeeper usage is disabled.
Note that if you are also intending to use the Prefix for MCU
registrations (see above), Cisco recommends that you set both
prefixes to the same number.
If the MCU is unable to match a call to a conference or auto
attendant, the action for Incoming calls to unknown E.164 number
will be applied. This is a setting on the Settings > Conferences
page (see Configuring global conference settings). This action can
be set to Create new ad hoc conference.
169
Cisco TelePresence MCU Series Online Printable Help