Conference Monitoring/Management; Provisioning; Polycom Mgc Configuration - Polycom ReadiManagerSE200 Release Note

requires that a valid SMTP server configuration is present in the
administration view.
C M
ONFERENCE ONITORING
1. The scheduled conference ID may differ in conference monitoring when calls
become active. The conference ID for active IP calls will be the H.323
conference ID assigned by the gatekeeper. This value may differ from the
scheduled conference ID when the future scheduled conference was created.
The CDR will report the gatekeeper assigned conference ID.
2. Point-to-point scheduled conferences that do not use the MGC will always
show as "FUTURE" conferences in the conference monitoring control in the
operator interface. Even when the conference launches it will remain in a
"FUTURE" state rather than converting to "ACTIVE." In addition, the
participants will be shown as disconnected. However, in the device
monitoring control the correct status information for the endpoints is shown.
3. Conferences running on Polycom MGC's with versions prior to version 7 may
not fully display all details in the conference monitoring control in the
Operator view. With version 7 and higher MGC's all conference details and
full ad-hoc conference management capabilities are present.
4. The level of conference management depends on the version of MGC
installed. Version 6 allows for basic conference management functionality.
Version 7 or higher allows for advanced functionality.
5. Muting participants from the conference monitoring control of the Operator
view will not work. However, participants can be connected and disconnected
from conferences running on MGC's with version 7 or higher by clicking on the
green connection ball.
6. Using the Send Message function on a MGC call from the conference
monitoring control will not send a message to the participant. To send
messages to endpoints in a multi-point call the device monitoring control
should be used.
7. When monitoring active conferences not all parameters will be populated in all
cases. However, the data that is presented accurately represents the ongoing
conference.
P
ROVISIONING
1. Only one scheduled provisioning profile can be scheduled for a device type at
any one time. If a second profile is scheduled for a device type its schedule
will replace any other profile which is scheduled but not yet active.
P MGC C
OLYCOM ONFIGURATION
1. When adding an MGC version 7 or higher all of the configuration details will
be auto-populated based on the current MGC configuration. These details can
be edited from their defaults.
2. If entry queues are not defined on an MGC running version 7 or higher then
the auto-populated details on the MGC will have IVR unchecked. If entry
queues do exist on the MGC when it is added to the ReadiManager then the
IVR option will be checked and the entry queue number will be entered
Copyright (c) 2005 Polycom Incorporated. All rights reserved. Polycom, the Polycom logo design and ViewStation are
2
registered trademarks, V IU, ReadiManager SE200, PathNavigator, Global Management System, and iPower are
trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of
1
respective owners Copyright (c) 2005 Polycom Incorporated. All rights reserved. Polycom, the Polycom logo design and
ViewStation are registered trademarks, PathNavigator, Global Management System, and iPower are trademarks of
Polycom, Inc. in the United States and various other countries. All other trademarks are the property of respective owners
/M
ANAGEMENT