12.03.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 7: System Limitations (Continued)<br />

No. Category Description ID#<br />

53. IP When entering an empty space in the<br />

Alias field in the Participant Properties<br />

call failure may occur.<br />

54. IP When you delete an IP Network<br />

Service on the MCU, the Card’s<br />

properties still appear as registered in<br />

PathNavigator.<br />

55. ISDN When two different ISDN Network<br />

Services are used for two “Meet Me” or<br />

Meeting Room conferences, and one<br />

dial-in number is contained in the<br />

other, dial-in undefined participants<br />

may be connected to the wrong<br />

conference. For example, if one<br />

Network Service allocates the dial-in<br />

number 397, and the second allocates<br />

the number 8397, participants dialing<br />

8397 will be connected to the<br />

conference assigned the number 397.<br />

56. IVR Faint clicks may be heard when<br />

participants are using DTMF codes.<br />

57. IVR The number of IVR Services defined<br />

for a single <strong>MGC</strong> unit may not exceed<br />

30 Services. When this number is<br />

exceeded it causes high CPU usage.<br />

Corrections, Pending Issues and Limitations<br />

19417<br />

18618<br />

13651 Dial-in numbers<br />

allocated to all<br />

ISDN Services of a<br />

MCU should be of<br />

the same length.<br />

13686<br />

16455<br />

Workaround/<br />

Remarks<br />

59

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!