MGC-25/50/100 MGC+50/100 - Polycom

MGC Release Notes - Version 7.5
62
Table 7: System Limitations (Continued)
No. Category Description ID#
74. Roll Call When Roll Call is in use and a
participant is disconnected, there is a
delay until the MGC Manager indicates
the disconnection.
75. Roll Call Roll Call is not supported when moving
a participant from one conference to
another or from the Operator
conference to the Home Conference.
Roll Call is also not supported in an
Invite session.
76. SIP Cascaded SIP links cannot be
allocated to the same IP+ card.
77. SIP If the VSX endpoint is registered to the
SIP Proxy,you cannot dial-out from the
endpoint to conference on the MCU.
This scenario fails even when the
conference is registered to the proxy.
78. SIP In a SIP environment asymmetric
Payload Type is not supported.
(Incoming and outgoing channels use
different payload type numbers in the
header of the RTP packets).
By setting the flag VIDEO_DRAFT=4
MGC uses static Payload Type and
forces the end point to symmetric
mode. (When flag is VIDEO_DRAFT=5
MGC uses Dynamic Payload Type)
79. SIP Windows Messenger cannot get TCP
call from IPTEL proxy.
80. SIP SIP endpoints connect as Secondary
(audio only) in the following Video
Session settings:
• Software CP
• CP COP (Conference on Port)
• CP - Quad Views
• Video Switching - Highest Common
mechanism (video parameters
must be set to fixed mode)
13661
—
Cascade on two
different cards.
20909 Dialout using the
SIP proxy.
20943
20872
21419
Workaround/
Remarks