Corrections, Limitations And Pending Issues; Corrections Between Versions V.7.0.3 And V.7.0.4 - Polycom MGC-25 Release Notes

Video conferencing bridge
Hide thumbs Also See for MGC-25:
Table of Contents

Advertisement

Corrections, Limitations and Pending Issues

Corrections between Versions V.7.0.3 and V.7.0.4

Table 2: Corrections between Versions V.7.0.3 and V.7.04
#.
Category
1.
API
2.
API
3.
Audio
4.
Control Unit
5.
General
6.
General
7.
General
8.
General
9.
General
Description
Compilation error occurs when
compiling 7.0 SDK with third party
application.
CDR retrieval generates two problems:
Memory leak
Corrupted CDR files cause the
CDR application to describe all
events in the CDR as
Unrecognized Events.
There are a lot of ipload.cpp asserts,
taskapi.cpp asserts and audio noise
during the conference starts.
MCU LAN card causes intermittent
disconnections.
Wrong memory allocation, after
months of working in Reservation
mode, results in video freezes and
audio loss.
Conference termination when
participant is moving to the conference
causes double allocation of Audio
Resources. This results in a failure to
successfully mute all participants in a
conference in which double booked
Audio Resources were used.
The MCU got gsegment.cpp,
termsock.cpp asserts & MMGR
exception on V5.16.723.
When you create a Meeting Room with
Entry Queue access and assign a
Numeric ID, change the ID once and
then change back to the original ID
value, the following error message is
generated: "Conference ID occupied".
When running large conferences (120
participants) after 1.5 hours, the MGC
Manager and API applications
disconnect and the connection to the
MCU is lost. The conferences continue
running for about 20 min. and then the
MCU self-reboots.
Corrections, Limitations and Pending Issues
ID#
20831
21471
20877
21327
21110
21555
21589
21614
21808
Remarks
17

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mgc-50Mgc-100

Table of Contents