Polycom® Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communications™ | June 2011 | 3725-62124-001/A
Trademark Information Polycom®, the Polycom “Triangles” logo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. © 2011 Polycom, Inc.
Contents 1 Introduction Required Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Siemens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Polycom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Contents Mixed Rich-Media Collaboration Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Video Systems Available in a UC Client's Address Book or Buddy List . . . Presence Information for Video Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting Non-SIP Video Systems to SIP Video . . . . . . . . . . . . . . . . . . . . . . H.
Contents Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Using IPv6 Networking Addresses for RMX Internal and External Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RMX Internal Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations vi Contents Polycom, Inc.
1 Introduction This document includes the requirements for the Polycom and Siemens video interoperability that Siemens refers to as Video Solution V2R2 for Siemens Enterprise Communications. The Siemens OpenScape Video V2R2 solution combines high-definition (HD) video room systems, desktop devices, and media control units with state-of-the-art unified voice and communication support by OpenScape Voice V5. OpenScape Video V2R2 also contains OpenScape Voice V4R1.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Required Hardware Siemens • Siemens OpenScape Server that can operate in the single instance: — OpenScape Voice switch — OpenScape UC application — Media Server with G.711 support • Siemens Open Stage 40 and Open Stage 60 phones Open Stage 20 and 40 phones have the same software. Open Stage 60 and 80 have the same software. 20/40 and 60/80 are similar but not the same.
Introduction Supported Versions The following tables list the supported Polycom and Siemens OpenScape versions or releases that have been tested and verified in a lab environment. Polycom Product Release CMA 5000 5.5 and later DMA 7000 2.3 Polycom HDX Series Systems 3.0.1 and later Polycom RMX 1500/2000/4000 7.2.1 Polycom VVX 1500 3.3.1 and later Polycom Telepresence RPX, ATX, OTX. 3.0.1 Note: For this release, Polycom ITP supports H.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Support For Siemens Video solution issues contact your Siemens support representative. For Polycom product equipment issues, contact Polycom Global Services or www.support.polycom.com. 1–4 Polycom, Inc.
2 Getting Started with the OpenScape Solution for Siemens Enterprise Communications Introduction to OpenScape Video Video communications is a key component in unified communication and collaboration (UCC) environments. The term Unified Video Conferencing (UVC) is used to describe the integration of video into UCC. The following figure shows an overview of the OpenScape Video V2R2 deployment solution. Polycom, Inc.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations OpenScape Video V2R2 Solution Features The OpenScape Video V2R2 solution has the same look and feel for video calls and conferences as that of OpenScape UC audio solutions. Video calls are set up in the same way as voice calls — by dialing a phone number. The same clients used for audio can be used for video. The end user can start or stop showing video by pressing a button.
Getting Started with the OpenScape Solution for Siemens Enterprise Communications • Video endpoints show device presence status. All allowed contacts are informed about busy or idle states. • Video endpoints can be selected as preferred devices for incoming and outgoing calls. • Simple presence information is supported.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations VPN-Based Interdomain Video Incoming and outgoing SIP calls between OSV SIP users in the public and in a private domain can be connected to the home private network by VPN, for example, using MobileXpress. Enterasys in Combination with OpenScape Video Enterasys allows location services for Polycom video endpoints. It streamlines inventory management and endpoint detection.
3 Use Cases from the User’s Perspective This chapter describes the major use cases from an end user’s perspective that are supported in OpenScape Video V2. The following figure shows the Network components and User Interface. The Network components area includes these buttons: Web Collaboration, Call Control, and MCU. The User Interface area includes these buttons: Audio, Video, and Collab (Collaboration).
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations • A collaboration application server that supports users in a video or audio conference to share data or presentations or to jointly collaborate on a single document The user interface supports equipment for the following activities: • To listen and speak, for example, phones, mobile phones, loudspeakers, room systems • To show videos or record videos and visuals, for example, webcams, compu
Use Cases from the User’s Perspective Client-based systems with webcams might not be connected to high-end video room systems or to an immersive telepresence environment, although this is changing. Because of advanced technology, individual mobile and desktop interfaces can communicate with high-end room and immersive systems. Video is becoming more affordable for everyone, not only for the executive-level personnel of an organization.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Video Room Systems Video room systems are usually set up in conference or meeting rooms. Depending on the number of chairs, room systems offer smaller or larger video screens and sometimes even multiple screens. Room systems can also be set up and used in non-office settings such as surgical teaching rooms and small classrooms to provide video interaction with remote participants.
Use Cases from the User’s Perspective of the participant’s computers to the Polycom HDX system to integrate the particular content into the video streams. The following figure shows an example room system for 10 or more participants. Room Systems for 3 to 10 Participants This scenario applies to smaller rooms. The room system supports high-quality audio and display control, and a computer is used to support collaboration, such as sharing documents.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Desktop Video Systems In many cases video conference participants sit at their desks in their offices and use a video desktop device such as a Polycom VVX 1500 for voice and video and a laptop to share presentations. The following figure shows an example of a participant using a VVX 1500 phone system. The Polycom VVX 1500 can also be used at home or in a hotel.
Use Cases from the User’s Perspective Centralized Call Control allows point-to-point voice and video calls to be established directly between involved endpoints. During the call the users can also start a collaboration controlled by a centralized server based on http/ https. Similar to point-to-point connections, small video conferences with up to eight participants can be established without the need of a centralized MCU.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations This example illustrates how different video endpoint users can jointly collaborate while having the opportunity to speak to and listen to each other, and to see each other's faces. Multipoint (Three or More) Video Meetings on an MCU (Host or Participant) Small video conferences can also be mixed with a centralized Polycom RMX, as shown in the following figure.
Use Cases from the User’s Perspective The Polycom RMX can mix many more video streams and add audio-only participants, for example cell phone callers, to a large or very large conference. The next figure shows the abstract scenario of a large or very large conference.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Mixed rich-media collaboration sessions including UC clients that support audio and video, room video conferencing systems, desktop video conferencing systems, audio-only systems (telephones and soft clients) can be easily established and managed because of the powerful management systems and one-touch user interfaces. This is shown in the following figure.
Use Cases from the User’s Perspective Mixed Rich-Media Collaboration Sessions Mixed rich-media collaboration sessions are established between UC clients that support audio and video, room video conferencing systems, desktop video conferencing systems, and audio-only systems such as telephones and mobile phones.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Connecting Non-SIP Video Systems to SIP Video The use cases described so far are based on the assumption that all video and audio endpoints and clients support SIP signaling. However, many video solutions are based on H.323 signaling, some on proprietary signaling, and others on legacy ISDN non IP systems. Some video solutions are based on both H.323 and SIP.
4 Use Cases from the Network Perspective This chapter explains specific functions that are required for end-to-end video communication solutions. Interdomain Video Solutions Video solutions are not always isolated domains and need to support interdomain video calls. OpenScape Video V2R2 provides SBC-based interdomain video and gateway-based interdomain video.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations the on-campus OpenScape Video. This scenario requires an SBC to handle the network address translation (NAT) between the two connected domains and is shown in the following figure. 4–2 Polycom, Inc.
Use Cases from the Network Perspective VPN-Based Interdomain Video Using a virtual private network (VPN) is another way to connect remote workers in a video conference from their home offices or those who might be traveling. The following figure shows a VPN-based interdomain video solution. The major benefit for users in scenario B is that they can behave and use services and applications exactly the same as if they were located in the private domain.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations • Multipoint video between video endpoints registered at different SIP registrars with an off-campus MCU, for example, a video partner conference call between an OpenScape product and Polycom on a bridge hosted by Polycom.
Use Cases from the Network Perspective This figure shows a typical video point-to-point call, initiated by an end user in the private domain A, for example, siemens-enterprise.com. It can also be intimated by an endpoint B in a partner company domain, for example, polycom.com. The incoming call, from B to A in the private domain, is established by dialing the domain_name@private domain.com, for example, 27111@siemens-enterprise.com.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations The figure shows an example of another typical video configuration. Two or more partners from two different companies, such as Siemens Enterprise Communications and Polycom, want to meet on an MCU in the private domain, such as siemens-enterprise.com. User A calls into the MCU by using its domain name, for example, 88888. User B dials into the MCU by dialing domain_name@private domain.
Use Cases from the Network Perspective Users A and C call into the MCU at Polycom by dialling the gateway number, for example 99 plus the DN of the called partner, that is 99 77777. After receiving the number the gateway deletes 99 from the string and adds @polycom.com. Hence the MCU is addressed with 77777@polycom.com. User B can either dial domain_name@partner domain, that is, 77777@polycom.com, or just dial 77777.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations This feature helps to reduce operational costs while increasing the productivity of administrators and users. Higher availability and reliability guarantees continuity of business processes for enterprises.
Use Cases from the Network Perspective Mission Critical Video Conferencing Redundant MCUs through the Polycom DMA System The Polycom DMA system, shown in the following illustration, allows control of several MCUs, such as a Polycom RMX or others, as if they were one virtual MCU. The DMA system balances the load to each connected MCU. It prevents loss of service if a bridge is down, and only the capacity of the virtual MCU is reduced.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Cascading a conference across multiple MCUs can conserve bandwidth and is especially useful when using WAN links. Participants can connect to MCUs that are geographically near them, reducing network traffic between sites to a single link to each MCU. Cascading does, however, impact the quality of the conference experience. Cascading is supported only for RMX MCUs and only in H.323.
Use Cases from the Network Perspective Some features of the Polycom DMA system are listed in the following table.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 4–12 Polycom, Inc.
5 Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape This chapter provides an overview of how to set up and configure Polycom HDX systems to interoperate with Siemens OpenScape products. For more detailed information about configuring HDX Systems, refer to the documentation on this web site: www.support.polycom.com. Polycom HDX systems running software version 3.0.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations To configure Polycom HDX LAN properties: 1 Do one of the following: — In the local interface, go to System > Admin Settings > LAN Properties (select if necessary). — In the web interface, go to Admin Settings > LAN Properties. 2 Configure these settings on the LAN Properties screen: Setting Description IP Address (IPv4) Specifies how the system obtains an IP address.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Setting Description Link-Local Displays the IPv6 address used for local communication within a subnet. Site-Local Displays the IPv6 address used for communication within the site or organization. Global Address Displays the IPv6 internet address. Default Gateway (IPv6) Displays the gateway currently assigned to the system. If the system does not automatically obtain a gateway IP address, enter one here.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Setting Description Duplex Mode Specify the duplex mode to use. Note that the Duplex mode you choose must be supported by the switch. Choose Auto to have the network switch negotiate the Duplex mode automatically. Choosing Auto automatically sets LAN Speed to Auto. The duplex settings for both the Polycom HDX system and the switch must be the same. Polycom recommends that you set both to Auto.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Setting Description Audio Priority Sets the priority of audio traffic on the LAN. Audio traffic is any RTP traffic consisting of audio data and any associated RTCP traffic. This setting is available only when 802.1p/Q is enabled. The value can be any number from 0 to 7, although 6 and 7 are not recommended. Control Priority Sets the priority of control traffic on the LAN.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Specifying SIP Settings If your network supports the Session Initiation Protocol (SIP), you can use SIP to connect IP calls. To specify SIP Settings: 1 Do one of the following: — In the local interface, go to System > Admin Settings > Network > IP > SIP Settings (select if necessary). — In the web interface, go to Admin Settings > Network > IP Network > SIP Settings.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Setting Description Password Specifies the password that authenticates the system to the Registrar Server. SIP Registrar Server Specifies the IP address or DNS name of the SIP Registrar Server. By default for TCP, the SIP signaling is sent to port 5060 on the registrar server. By default for TLS, the SIP signaling is sent to port 5061 on the registrar server.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Specifying H.323 Settings If your network uses a gatekeeper, the system can automatically register its H.323 name and extension. This allows others to call the system by entering the H.323 name or extension instead of the IP address. To specify H.323 settings: 1 Do one of the following — In the local interface, go to System > Admin Settings > Network > IP > H.323 Settings.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Configuring the System to Use a Gatekeeper A gatekeeper manages functions such as bandwidth control and admission control. The gatekeeper also handles address translation, which allows users to make calls using static aliases instead of IP addresses that may change each day. To configure the system to use a gatekeeper: 1 Do one of the following: — In the local interface, go to System > Admin Settings > Network > IP > H.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Setting Description Primary Gatekeeper IP Address • If you chose No for the Use Gatekeeper field, the Primary Gatekeeper IP Address field is not displayed. • If you chose to use an automatically selected gatekeeper, this area displays the gatekeeper’s IP address. • If you chose to specify a gatekeeper, enter the gatekeeper’s IP address or name (for example, gatekeeper.companyname.usa.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Points to note about Polycom’s Conference on Demand feature: In order to place calls using Conference on Demand, you need to: • Register your Polycom HDX system with a Polycom gatekeeper. A Polycom RMX® system must be configured with the gatekeeper to provide the Conference on Demand feature. • Enable Use PathNavigator for Multipoint Calls. • Create a group in the directory (recommended).
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Setting Description Gateway Number Type Specifies the number type users enter to call this system: • Direct Inward Dial — Users enter an internal extension to call this system directly. Note: If you choose this setting, you must also register the number with the gatekeeper as an E.164 alias.
6 Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape This chapter provides an overview of how to set up and configure Polycom RMX 1500/2000/4000 systems to interoperate with Siemens OpenScape products. For more detailed information about configuring Polycom RMX, refer to the Polycom RMX documentation on this web site: www.support.polycom.com.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations When IPv4 is selected, IPv6 fields are not displayed and conversely when IPv6 is selected, IPv4 fields are not displayed. When IPv6 & IPv4 is selected both IPv6 and IPv4 fields are displayed. Mandatory System Flags The following mandatory System Flags must be set: • SIP_FREE_VIDEO_RESOURCES NO This setting is required because the OpenScape Desktop Client escalates from Audio to Video.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Conferencing related definitions such as environment (H.323 or SIP) are also defined in this service. Most of the Default IP Service is configured by the Fast Configuration Wizard, which runs automatically if the following occurs: • First time power-up • Deletion of the Default IP Service, followed by a system reset Changes made to any of these parameters only take effect when the Polycom RMX unit is reset.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Field Description IPv6 Configuration Method Auto (Stateless) Manual Select this option to allow automatic generation of the following addresses: • Link-Local (For internal use only) • Site-Local • Global Select this option to enable manual entry of the following addresses: • Site-Local • Global Manual configuration of the following address types is not permitted: Control Unit IP A
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Field Description Shelf Management IP Address IPv4 The IPv4 address of the RMX Shelf Management Server. This IP address is used by the RMX Web Client to monitor hardware. IPv6 The IPv6 address of the RMX Shelf Management Server. This IP address is used by the RMX Web Client to monitor hardware. Note: Internet Explorer 7™ is required for the RMX Web Client to connect to the RMX using IPv6.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Field Description Static Routes IPv4 Only Table Static Routes IPv4 Only Table 6–6 The system uses Static Routes to search other networks for endpoint addresses that are not found on the local LAN. Up to five routers can be defined in addition to the Default Router.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape 5 Click the DNS tab and modify the following fields: Field Description MCU Host Name Enter the name of the MCU on the network. The default name is RMX. DNS Select: Off — if DNS servers are not used in the network. Specify — to enter the IP addresses of the DNS servers. Note: The IP address fields are enabled only if Specify is selected.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations RMX 2000 only: Click the LAN Ports tab and modify the following fields: 6 For the RMX 1500/4000 platforms, you can manually modify automatically identified speed and transmit/receive mode for each LAN port that the system uses if required by the specific switch in the Ethernet Settings dialog box. These settings are not part of the Management Network dialog box as for the RMX 2000.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Fast Configuration Wizard You can use the Fast Configuration Wizard to configure the Default IP Service. The wizard starts automatically if no Default IP Network Service is defined. This happens during First Time Power-up before the service has been defined or if the Default IP Service has been deleted, followed by an RMX restart.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Field Description Media Card 1 IP Address Enter the IP address(es) of the media card (s) as provided by the network administrator: Media Card 2 IP Address RMX1500: MPMx 1 RMX 2000: MPM+/MPMx 1 and MPM+/MPMx 2 (if installed) (RMX 2000/4000) RMX 4000: MPM+/MPMx 1, MPM+/MPMx 2 (if installed), MPM+/MPMx 32 (if installed) and MPM+/MPMx 4 (if installed) Media Card 3 IP Address (RMX 4000) Endpo
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Field Description Register as Gateway Select this check box if the RMX unit is to be seen as a gateway, for example, when using an alternate gatekeeper. Note: Do not select this check box when using the Polycom ReadiManager/CMA 5000 gatekeeper. Refresh Registration every __ seconds The frequency with which the system informs the gatekeeper that it is active by re-sending the IP address and aliases of the IP cards to the gatekeeper.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 8 Modify the following fields: Field Description Fixed Ports Leave this check box cleared if you are defining a Network Service for local calls that do not require configuring the firewall to accept calls from external entities. When cleared, the system uses the default port range and allocates 4 RTP and 4 RTCP ports for media channels (Audio, Video, Content and FECC).
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape — Transmission error rate DiffServ and Precedence are the two QoS methods that the RMX supports. These methods differ in the way the packet's priority is encoded in the packet header. The way RMX implements QoS is defined per Network Service, not per endpoint. Note: The routers must support QoS in order for IP packets to get higher priority.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Field Description TOS Select the type of service (TOS) that defines optimization tagging for routing the conferences’ audio and video packets. Delay — The recommended default for video conferencing. Prioritized audio and video packets tagged with this definition are delivered with minimal delay because the throughput of IP packets minimizes the queue sequence and the delay between packets.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Field Description Server Domain Name Enter the name of the domain that you are using for conferences, for example: user_name@domain name The domain name is used for identifying the SIP server in the appropriate domain according to the host part in the dialed string. For example, when a call to EQ1@polycom.com reaches its outbound proxy, this proxy looks for the SIP server in the polycom.com domain, to which it will forward the call.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Ethernet Settings For the RMX 1500/4000 platforms, you can manually modify the automatically identified speed and transmit/receive mode of each LAN port that the system uses if the specific switch requires it in the Ethernet Settings dialog box. These settings are not part of the Management Network dialog box as for RMX 2000.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Modify the following field: 2 Field Description Speed The RMX has 3 LAN ports on the RTM-IP (Management, Signaling, and Shelf Management), and additional LAN ports on each media card (RTM LAN) and RTM ISDN cards. The administrator can manually set the speed and transmit/receive mode for these ports. Port The LAN port number.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Field Description IPv4 IP Address Default Router IP Address The IP address of the default router. The default router is used whenever the defined static routers are unable to route packets to their destination. The default router is also used when host access is restricted to one default router. Subnet Mask The subnet mask of the MCU. Default value: 255.255.255.0.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Field Description Registration Interval The interval in seconds between the Signaling Host’s registration messages to the gatekeeper. This value is taken from either the IP Network Service or from the gatekeeper during registration. The lesser value of the two is chosen. Role Active — The active gatekeeper. Backup — The backup gatekeeper that can be used if the connection to the preferred gatekeeper fails.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations • MPM1 (Media Card) • MPM2 (Media Card) External Entities • Gatekeepers (Primary & Secondary) • SIP Proxies • DNS Servers • Default Router • Defined participants • Internet Explorer 7™ is required for the RMX Web Client and RMX Manager to connect to the RMX using IPv6. • IPv6 is supported with MPM+ and MPMx media cards only. • The default IP address version is IPv4.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Licensing and System Information System Information includes License Information, and general system information, such as system memory size and Media Card Configuration Mode. To view the System Information properties box: >> On the RMX menu, click Administration > System Information. The System Information properties box is displayed.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Information Description Card Configuration Mode Indicates the MCU configuration as derived from the installed media cards: • MPM+ — Only MPM+ cards are supported. MPMx cards in the system are disabled. • MPMx — Only MPMx cards are supported. MPM+ cards in the system are disabled. When started with Version 7.
7 Feature Limitations The following table lists the known feature limitations for this release. If a workaround is available, it is noted in the table. Issue ID Found in Release Description Workaround VIDEO-89476 HDX software 3.0.1 When an HDX system that is TCP-registered to OpenScape Voice is restarted, it might not delete its registration to OpenScape Voice as it is supposed to. None VIDEO-88989 HDX software 3.0.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Issue ID Found in Release VNGR-20815 Description Workaround RMX 7.2.2 When in a call managed by the RMX 2000 with multiple networks and with HDX systems registered to the Siemens server, the interactive voice response (IVR) feature might not work correctly and content might not be viewable. None. VNGR-20098 RMX 7.
