Appendix H-Setting the MCU for Integration Into Microsoft Environment

Remote - a connection between MCU that resides within the organization and an endpoint that resides outside of the organization (on a WAN). For example, an endpoint on the internet that calls the MCU in Zone A. In such a case, the call has to traverse at least one firewall.

Federation - a connection between MCU that resides within one organization and an endpoint that resides within another organization. For example, an endpoint in Zone A calls the MCU in Zone B. The call has to traverse two or more firewalls.

Dialing Methods

The ICE protocol enables remote and federation connections using the registered user name for dialing. The endpoint connects to the MCU by entering the MCU registered user name in the following format:

[MCU registered user name]@[OCS/Lync server domain name] For example: rmx111@ilsnd.vsg.local

The call reaches the Transit Entry Queue of the MCU and via IVR is routed to the destination conference.

This method is added to the local connections and Matched URI and Numerical Dialing methods available in Microsoft Office Communication environment and the Numerical Dialing method available in the Lync server environment.

The following table summarizes the dialing methods and its availability in the various configurations.

Table H-3Available dialing methods per Connection Type

 

Matched URI Routing

Numerical Dialing

Registered User Name

 

 

 

 

Local

√

√

√

 

 

 

 

Branch office

√∗

X

√

 

 

 

 

Remote

√∗

X

√

 

 

 

 

Federation

√∗

X

√

 

 

 

 

*To enable the Matched URI dialing in the federated environment to be able to connect to the MCU SIP signaling domain, you must also configure the Office Communications Server/Lync Server.

When federating an Office Communications Server/Lync Edge server with another Office Communications Server/Lync server environment, you need to include the FQDN of the Office Communications Server/Lync Edge server as well as the SIP signaling domain for federated environment. The SIP signaling domain is the FQDN of the Polycom DMA system or a Polycom MCU system (when your deployment does not include a DMA system).

For example, if company B wants to set up federation with company A and receive and send SIP calls that will be handled by the Polycom SIP signaling domain in company A, you need to add the FQDN of the company A Office Communications Server domain as well as the SIP signaling domain of company A to the list of internal SIP Server domains supported by the company B Office Communications Server/Lync Server environment.

For more information, see the Microsoft documentation and the Polycom® Unified Communications Deployment Guide for Microsoft® Environments.

Polycom, Inc.

H-5

Page 892 Page 894
Page 893
Image 893
Polycom DOC2702A, RMX 1500 manual Dialing Methods, Table H-3Available dialing methods per Connection Type
Page 892 Page 894

DOC2702A, RMX 1500 specifications

The Polycom RMX 1500, also known by its model number DOC2702A, is a significant player in the realm of video conferencing technology. Designed to enhance collaboration across various platforms, this versatile solution caters to the communication needs of medium to large enterprises, providing high-quality video, voice, and content sharing experiences.

One of the primary features of the RMX 1500 is its unparalleled scalability. The system supports up to 150 simultaneous video endpoints, allowing organizations to expand their video conferencing capabilities as needed. This flexibility makes it an ideal solution for growing businesses that require robust communication tools. The RMX 1500 can also handle a variety of video resolutions, from standard definition to HD, ensuring that users can enjoy clear and crisp visuals during their meetings.

The Polycom RMX 1500 utilizes advanced technologies such as the Polycom RealPresence technology, which significantly enhances video quality and reliability. This technology incorporates features like Adaptive Bandwidth Management, which optimizes video streams based on available bandwidth, thus ensuring a seamless experience even in less-than-ideal network conditions. This ensures that users can engage in meetings without interruptions or quality degradation, regardless of their location.

Another notable characteristic of the RMX 1500 is its robust interoperability with a wide range of video conferencing systems and protocols. This means that businesses can easily connect with partners, clients, and colleagues using different systems, reducing the barriers to effective communication. The RMX 1500 supports various codecs and standards, including H.323 and SIP, making it a versatile choice for organizations that work with multiple platforms.

Furthermore, the RMX 1500 is equipped with tools for content sharing, allowing participants to share presentations, documents, and other materials during meetings. This promotes interactive discussions and enhances collaboration among team members. In addition, the system features an intuitive user interface, making it easy for users to schedule meetings, manage participants, and control audio and video settings.

The product also places a strong emphasis on security, providing encryption options for video and audio streams to protect sensitive information shared during conferences. This commitment to security is essential for organizations that need to meet compliance standards and safeguard intellectual property.

In summary, the Polycom RMX 1500 (DOC2702A) is a powerful video conferencing solution that combines flexibility, scalability, and high-quality performance. With its advanced technologies, interoperability, content sharing capabilities, and emphasis on security, it serves as an invaluable tool for enhancing communication and collaboration in today’s fast-paced business environment.
Top Page Image Contents