Chapter 6-Meeting Rooms
Polycom, Inc. 6-3
Routing Name The ASCII name that registers conferences, Meeting Rooms, Entry
Queues and SIP Factories in the various gatekeepers and SIP Servers. In
addition, the Routing Name is also:
• The name that endpoints use to connect to conferences.
• The name used by all conferencing devices to connect to conferences
that must be registered with the gatekeeper and SIP Servers.
ID Displays the Meeting Room ID. This number must be communicated to
H.323 conference participants to enable them to dial in.
Duration Displays the duration of the Meeting Room in hours using the format
HH:MM (default 01:00).
Conference
Password
The password to be used by participants to
access the Meeting Room. If blank, no password
is assigned to the conference. This password is
valid only in conferences that are configured to
prompt for a conference password in the IVR
Service.
The RMX can be
configured to
automatically
generate conference
and chairperson
passwords when
these fields are left
blank.
For more information,
see the "Automatic
Password Generation
Flags” on
page 22-45.
Chairperson
Password
Displays the password to be used by the users to
identify themselves as Chairpersons. They are
granted additional privileges. If left blank, no
chairperson password is assigned to the confer-
ence. This password is valid only in conferences
that are configured to prompt for a chairperson
password.
Profile Displays the name of the Profile assigned to the Meeting Room. For more
information, see "Conference Profiles” on page 2-1.
SIP Registration The status of registration with the SIP server:
• Not configured - Registration with the SIP Server was not enabled in
the Conference Profile assigned to this conferencing Entity. In Multiple
Networks configuration, If one service is not configured while others
are configured and registered, the status reflects the registration with
the configured Network Services. The registration status with each SIP
Server can be viewed in the Properties - Network Services dialog box
of each conferencing entity.
When SIP registration is not enabled in the conference profile, the
RMX's registering to SIP Servers will each register with an URL
derived from its own signaling address. This unique URL replaces the
non-unique URL, dummy_tester, used in previous versions.
• Failed - Registration with the SIP Server failed. This may be due to
incorrect definition of the SIP server in the IP Network Service, or the
SIP server may be down, or any other reason the affects the
connection between the RMX or the SIP Server to the network.
• Registered - the conferencing entity is registered with the SIP Server.
• Partially Registered - This status is available only in Multiple
Networks configuration, when the conferencing entity failed to register
to all the required Network Services if more than one Network Service
was selected.
Table 6-2 Meeting Rooms List Columns (Continued)
Field Description