Polycom MGC-25 Release Notes page 55

Table 10: System Limitations (Continued)
No. Category
78. Roll Call
Roll Call
79.
SIP
80.
SIP
81.
SIP
82.
SIP
83.
SIP
84.
85. SIP
SIP
86.
Description
When Roll Call is in use and a
participant is disconnected, there is a
delay until the MGC Manager indicates
the disconnection.
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.
Cascaded SIP links cannot be
allocated to the same IP+ card.
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.
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).
Windows Messenger cannot get TCP
call from IPTEL proxy.
In a Video Switching conference when
the speaker changes, all ISDN parties
accumulate R-Sync Video Loss and
are indicated as "Faulty" in MGC
Manager. On average Video is
impaired for 1 second.
When changing the Refresh SIP
registration in the IP Service to 10
seconds, the LCS proxy rejects the
MGC and registration fails.
LCS proxy does not work with
Automatic SIP-Factory settings.
Corrections, Pending Issues and Limitations
Workaround/
ID#
Remarks
13661
—
Cascade on two
different cards.
20909 Dialout using the
SIP proxy.
20943 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).
20872
21068
21191 Set the Refresh SIP
Registration to
more than 10
seconds.
21319 In the LCS proxy,
define static-route
rules using IP
board (format:
*@IPAddress)
51