Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Configuring the MCU
Cisco TelePresence MCU 4.3 Product administration guide
Page 154 of 242
MCU
service
prefix
service
prefix
Displays the identifier that the
gatekeeper has registered for calls to
be routed to the MCU.
gatekeeper has registered for calls to
be routed to the MCU.
For more information about this prefix, refer to the table
above.
above.
Displaying active gatekeeper registrations
To display a complete list of all IDs that the MCU is attempting to register with the configured H.323
gatekeeper, go to
gatekeeper, go to
Settings > H.323
and click
details
, shown next to the Number of active registrations
status entry. You are taken to the
Active registrations
page. This page shows the complete set of IDs that
the MCU is attempting to register with the configured H.323 gatekeeper, and includes the H.323 ID, prefixes,
and specific E.164 number registrations for active conferences and configured auto attendants.
and specific E.164 number registrations for active conferences and configured auto attendants.
Filters
You can configure filters so that only specific registrations are shown in the list. This may help you to find a
registration whose number or name you know if the list is very long.
registration whose number or name you know if the list is very long.
The filtered registration list is automatically updated when you change the ID and Details filters; to stop
filtering the list either delete the filters or click Clear filters. If both the ID filter and the Details filter are
defined, the registration list will show only those entries which match both filters.
filtering the list either delete the filters or click Clear filters. If both the ID filter and the Details filter are
defined, the registration list will show only those entries which match both filters.
Field
Field description
Usage tips
ID filter
Type the ID, or a part of the ID for which you want to see details.
The filtered registration list is
automatically updated when you
change the ID and Details filters.
automatically updated when you
change the ID and Details filters.
Applying a filter will filter all
registrations and display any that
match, even if those registrations
are not on the page currently
displayed.
registrations and display any that
match, even if those registrations
are not on the page currently
displayed.
Details
filter
filter
Type the text, or a part of the text that will appear in the "Details"
column of the Registrations table. For example, type
'Conference' to filter the registrations to show all conferences
that the MCU is attempting to register with the gatekeeper.
column of the Registrations table. For example, type
'Conference' to filter the registrations to show all conferences
that the MCU is attempting to register with the gatekeeper.
Registration list
The registration list shows, for each registered ID, the type of that ID (H.323 ID, prefix or E.164 number), the
object it relates to, and the status of that registration. If you want to modify or remove a specific registered
ID, click on the link in its
object it relates to, and the status of that registration. If you want to modify or remove a specific registered
ID, click on the link in its
Details
column to be taken to the relevant configuration page.
Configuring SIP settings
To configure SIP settings on the MCU, go to
Settings > SIP
.
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. The MCU can register up to 50 URIs with the SIP
Registrar. This limit includes all conference Numeric IDs and the MCU's own URI.
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. The MCU can register up to 50 URIs with the SIP
Registrar. This limit includes all conference Numeric IDs and the MCU's own URI.
If you need to register more than 50 SIP URIs, use prefix based call routing on a SIP proxy (for example, on
Cisco TelePrsence Video Communications Server (VCS)) to route calls to the MCU by prefix, rather than
Cisco TelePrsence Video Communications Server (VCS)) to route calls to the MCU by prefix, rather than