MGC-50/MGC-100 Getting Started Guide

For example, if the IP Network Service prefix is 27, the conference Numeric ID is 1478 and the conference name is ‘MARKETING’, the participant can dial 271478 or 27MARKETING. IF the Entry Queue name is EQ1 and its numeric ID is 3000, the participant can dial 273000 or 27EQ1 to access the MR. IF only 27 is dialed, participants are be routed to the default Entry Queue (if one is defined).

When no gatekeeper is present, H.323 participants dial the IP address of the MCU’s IP card, followed by ## and the conference/Entry Queue Numeric ID. For example, if the IP card address is 172.22.190.162, participants will enter 172.22.190.162##1478 to access the conference, or 172.22.190.162##3000 to access the Entry Queue.

If no Entry Queue /conference numeric ID or if the wrong numeric ID is entered, participants are be routed to the default Entry Queue (if one is defined). If no default entry queue is defined in the system, the call is disconnected.

SIP participants

When a new conference reservation or Entry Queue is defined the conference or Entry Queue registers with the SIP proxy.

SIP participants dial the conference/Entry Queue URI using the format: Conference or Entry Queue name@domain name.

For example, MRO1@polycom.com, or EQ1@polycom.com.

Usually for SIP conferencing, an Ad Hoc Entry Queue is used. In this scenario, the first participant dials the Entry Queue and creates a new conference, while the other conference participants dial directly to the conference using the conference name or Numeric ID.

When dialing from a Microsoft Windows Messenger endpoint that does not have DTMF capabilities, the first participant (who creates the new conference in Ad Hoc Conferencing) enters the Entry Queue name followed by the target conference name and the numeric ID in the format:

EQ Name (Target Conference Name)(Target Conference Numeric ID).

For example, EQ1(sales)(12345). In this example, the Entry Queue name is EQ1, and a new On Going Conference by the name sales with the Numeric ID 12345 will be created on the MCU.

You do not need to add the domain name to the conference name, as it is automatically added by Microsoft Windows Messenger when the request is sent to the SIP server.

5-6

Page 85 Page 87
Page 86
Image 86
Polycom MGC-50, MGC-100 manual SIP participants
Page 85 Page 87

MGC-50, MGC-100 specifications

The Polycom MGC (Multipoint Gateway Controller) series includes notable models such as MGC-100 and MGC-50, designed to enhance video and audio conferencing capabilities in various organizational setups. These systems are pivotal for facilitating effective communication in a world where remote collaboration is increasingly essential.

The Polycom MGC-100 serves as a powerful multipoint control unit (MCU), allowing multiple concurrent video and audio sessions. It is particularly suitable for larger enterprises and organizations that require sophisticated conferencing capabilities. Supporting both standard definition (SD) and high definition (HD) video, the MGC-100 can manage high-quality video streams seamlessly. Its ability to integrate with different conferencing systems and technologies makes it a versatile tool for enterprises looking to enhance their collaboration efforts.

Some standout features of the MGC-100 include its support for a wide range of protocols, including H.323 and SIP, ensuring compatibility with various endpoint devices. This model can accommodate a substantial number of participants, depending on the configuration, with options for scalability. The system also boasts advanced features such as content sharing, enabling users to present slides, documents, and other materials during conferences.

On the other hand, the Polycom MGC-50 is designed for smaller organizations or departmental use. While it provides fewer simultaneous sessions than the MGC-100, it still offers robust features that make it ideal for moderate conferencing needs. The MGC-50 also supports both H.323 and SIP protocols, ensuring smooth interoperability with various video conferencing endpoints. This model features straightforward management capabilities, allowing administrators to set up and control conferences with ease.

Both models are built with advanced video processing technologies, ensuring high-quality audio and video transmission. The inclusion of error correction and packet loss recovery technologies further enhances user experience, minimizing disruptions during calls. The systems also support a variety of codecs, ensuring optimal performance across different network conditions.

In terms of characteristics, both the MGC-100 and MGC-50 emphasize reliability and ease of use. They come with user-friendly interfaces and remote management capabilities, making it simple for IT professionals to maintain and configure the systems. In conclusion, the Polycom MGC series, with its MGC-100 and MGC-50 models, exemplifies a commitment to quality and performance in multipoint conferencing, catering to diverse organizational needs while facilitating effective communication strategies.
Top Page Image Contents