Filter
Top Products
Chapter 7-Entry Queues, Ad Hoc Conferences and SIP Factories
Polycom, Inc. 7-9
Monitoring Registration Status
The SIP registration status can be viewed in the Entry Queue or SIP Factory list panes.
The following statuses are displayed:
• Not configured - Registration with the SIP Server was not enabled in the Conference
Profile assigned to the Entry Queue or SIP Factory.
When SIP registration is not enabled in the conference profile, the Collaboration
Server's registering to SIP Servers will each register with an URL derived from its own
signaling address.
• 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
Collaboration Server 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 for Registration.
Ad Hoc Conferencing
The Entry Queue can also be used for Ad Hoc conferencing. If the Ad Hoc option is enabled
for the Entry Queue, when the participant enters the target conference ID the system checks
whether a conference with that ID is already running on the MCU. If not, the system
automatically creates a new ongoing conference with that ID. The conference parameters are
based on the Profile linked to the Entry Queue. As opposed to Meeting Rooms, that are
predefined conferences saved on the MCU, Ad Hoc conferences are not stored on the MCU.
Once an Ad Hoc conference is started it becomes an ongoing conference, and it is monitored
and controlled as any standard ongoing conference.
For more information about Ad Hoc conferencing, see Appendix D, "Ad Hoc Conferencing” on
page D-1.