PARTNER SOLUTION GUIDE Wave 6 | August 2012 | 3725-62124-003 Rev A Polycom® Unified Communications Deployment Guide for Siemens Enterprise Communications® OpenScape® Environments i
Polycom® Unified Communications Deployment Guide for Siemens Enterprise Communications OpenScape Environments Copyright ©2012, Polycom, Inc. All rights reserved. 6001 America Center Drive San Jose, CA 95002 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format.
Contents About This Guide ................................................................................................................. vii Conventions Used in this Guide .................................................................................................... vii Information Elements ......................................................................................................................... vii Typographic Conventions .............................................................
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Connecting Multiple Off-Site Video Endpoints ................................................................................... 18 Understanding OpenScape Location and Identity Assurance (LIA) Network Automation Support for Polycom Video Endpoints .............................................................................................................19 Understanding Quality of Service .......................................
Contents Viewing Licensing and System Information ...................................................................................76 Chapter 8: Integrating Polycom VVX Phones with Siemens OpenScape ................................ 79 Configuring Polycom VVX 1500 SIP Settings...................................................................................79 Chapter 9: Integrating Polycom DMA Systems with Siemens OpenScape ..............................
About This Guide Conventions Used in this Guide This user guide contains terms, graphical elements, and a few typographic conventions. Familiarizing yourself with these terms, elements, and conventions will help you perform phone tasks.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Typographic Conventions A few typographic conventions, listed next, are used in this guide to distinguish types of in-text information. Typographic Conventions Convention Description Bold Highlights interface items such as menus, soft keys, file names, and directories. Also used to represent menu selections and text entry to the phone.
Chapter 1: Introducing Siemens OpenScape Video Solution This partner solution guide explains how to integrate Siemens OpenScape® Video V6 with Polycom Unified Communications (UC). Siemens OpenScape Video includes OpenScape Voice, part of Siemens Enterprise Communications, and combines high-definition (HD) video, voice, and web collaboration tools into a single unified communications and collaboration (UCC) environment.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Siemens This partner solution guide requires you to have the following Siemens hardware components.
Introducing Siemens OpenScape Video Solution Table 1-1: Verified Polycom Product Versions Polycom Product Release Polycom® Converged Management Application™ (CMA™) 5000/4000 6.0.1 Polycom® Distributed Media Application™ (DMA™) 7000 5.0 Polycom® HDX® Series 3.0.5 Polycom® RMX® 1500 | 2000 | 4000 7.7 Polycom® VVX® 1500 Business Media Phone 4.0.2 Polycom® RealPresence® RPX™, OTX™, ATX™ Immersive Theater Solutions 3.0.
Chapter 2: Understanding the OpenScape Video Solution Features This chapter provides an overview of the features offered with Siemens OpenScape® Video solution. OpenScape Video enables you to make video calls by dialing a phone number, and to start or stop video with the press of a single button.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments OpenScape UC Features OpenScape UC supports the following features: • View the status of your contacts while in a video call when using Siemens OpenScape UC Enterprise Web Embedded Client • Select your preferred video endpoints for incoming and outgoing calls • Manage your presence information and assign your presence status to video endpoints • Add entries to your personal address book or to a buddy list • Collaborate with other
Understanding the OpenScape Video Solution Features ○ Polycom® HDX® Series version 3.0.5 ○ Polycom® RMX® 1500/2000/4000 version 7.7 ○ MCUs managed by Polycom® Distributed Media Application™ DMA™ 7000 version 5.0 ○ Polycom® RealPresence® RPX™, OTX™, ATX™ Immersive Theater Solutions version 3.0.5 • Calls between video clients and endpoints by dialing an E.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments SBC-Based Interdomain Video SBC-based video uses Acme Packet Net-Net 3820 to enable voice and video SIP calls between OpenScape endpoints and SIP endpoints in a public or private domain. See Table 1-2: Verified Siemens Product Versions for a list of endpoints that can be connected using an SBC. See SBC at Acme Packet for more information.
Chapter 3: Understanding the OpenScape Video Architecture This chapter provides an overview of the Siemens OpenScape® Video architecture. The OpenScape video architecture includes several layers, each of which is explained in this section. The following figure provides an overview of the architecture of the OpenScape Video solution. Figure 3-1: Overview of OpenScape Video Solution Physical Layer The following diagram illustrates the main connections of the physical layer of the OpenScape Video solution.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Figure 3-2: The Physical Layer Session Initiation Protocol (SIP) Layer The OpenScape Video solution components connected via SIP are shown in the following figure.
Understanding the OpenScape Video Architecture H.323 DMA System as Gatekeeper The following illustration shows how non-SIP and H.323 DMA system components register with the OpenScape Video solution. Non-SIP solutions are explained in more detail in the following section Using Non-SIP Components. Figure 3-4: H.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Overview of the OpenScape Video Solution The following diagram illustrates the physical, SIP, and H.323 DMA system layers combined. Figure 3-5: Overview of Video Architecture Using Non-SIP Components You can connect to OpenScape video solution using non-SIP components and signaling, including H.323 signaling, proprietary signaling, legacy ISDN non-IP systems, and dual video solutions that use H.323 and SIP.
Understanding the OpenScape Video Architecture Connecting non-IP Video Endpoints to OpenScape Video You can connect legacy video endpoints such as H.320 and even some proprietary protocols to the OpenScape video solution using an H.320 to H.323 or SIP gateway. You can make these connections using a Polycom RMX, which offers an H.320 to SIP or H.323 interface and supports an H.323/SIP Gateway.
Chapter 4: Understanding OpenScape Video Use Cases This chapter illustrates several typical use cases you can set up for interdomain video, location and identity assurance (LIA), and virtual multipoint control units (MCUs). Understanding Interdomain Video Solutions The Siemens OpenScape® Video solution provides SBC-based interdomain video, VPN-based interdomain video, and gateway-based interdomain video. Each of these solutions is explained next.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments VPN-Based Interdomain Video Remote or mobile workers in the public domain can use a virtual private network (VPN) to connect to a private domain and participate in a conference. The benefit of using a VPN to connect is that you can use public services and applications just as you do in the in the private domain. The following figure shows a VPN-based interdomain video solution.
Understanding OpenScape Video Use Cases • To establish a video conference between multiple parties each registered with a different SIP registrar. For example, Siemens Enterprise Communications employees are registered to OpenScape Voice with Siemens Enterprise Communications and Polycom employees are registered to an OpenScape Video hosted by Polycom. The following figure illustrates how endpoints registered with different SIP registrars can establish a video conference.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Connecting Multiple On-Site Video Endpoints You can connect multiple video endpoints within the same network for a video conference. The following figure shows an example of multiple video endpoints registered at different SIP registrars with an on-campus MCU.
Understanding OpenScape Video Use Cases Figure 4-5: Connecting Multiple Off-Site Video Endpoints Users A and C call into the MCU in the Siemens network by dialing the gateway number, for example 99 plus the domain name of the partner, 99 77777. After receiving the number the gateway deletes 99 from the string, adds @siemens-enterprise.com, and addresses the MCU with 77777@ siemensenterprise.com. User B can dial domain_name@partner domain, that is, 77777@ siemensenterprise.com, or dial 77777.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments OpenScape LIA also improves the security of video calls and conferences by automatically assigning Quality of Service (QoS) and security profiles called Policies using a network access control (NAC) solution. The following figure shows several Polycom endpoints supporting a location and identity assurance (LIA) network automation, and is followed by more detail on QoS.
Understanding OpenScape Video Use Cases 1 The Enterasys Network Management System (NMS) imports data from the physical infrastructure, such as switches and routers, and from the database. 2 The Enterasys Network Management System (NMS) communicates with the management appliance to identify the switch the port that is connecting the HDX system or VVX 1500 phone.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Use Cases for Resilient Video Conferencing The following section explains use cases for resilient video conferencing. Centralized Conference Resource Management You require a centralized conference resource management application to create a pool of conference servers that behave as one large conference server.
Understanding OpenScape Video Use Cases Automatically Routing Around Outages The Polycom DMA system receives notification if a bridge goes down or becomes full, and responds to prevent loss of service. Only the capacity is reduced during the outage. In the case of a conference call failover, that is, if a connection to a bridge fails during a call, the DMA system automatically holds the call and reestablishes it on another bridge. End users and administrators do not have to intervene.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments The following figure illustrates use of the DMA system as a centralized conference resource management application.
Chapter 5: Configuring Siemens OpenScape Voice This chapter shows you how to configure Siemens OpenScape® Voice. Configuring OpenScape Voice Subscriber This section shows you how to configure OpenScape voice subscriber properties. To configure OpenScape Voice Subscriber properties: 1 Open the Common Management Portal. 2 Go to OpenScape Voice > Business Group > Members > Subscribers. 3 Click on the directory number you want to modify or check.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 4 In the Edit Subscriber dialog, choose the General tab and enter a number in the Directory Number field. The number you enter here is used in the SIP configuration of the HDX system as the User Name field. You can access this number for the HDX in the User Name field of the HDX SIP settings, as shown in Specifying HDX SIP Settings. You can access this number for the VVX 1500 phone in the SIP settings of a registered line.
Configuring Siemens OpenScape Voice The Endpoint dialog displays. 4 In the Endpoint dialog, choose the General tab and check Registered, as shown next.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ Type Static ○ Signaling Address Type IP Address or FQDN ○ Endpoint Address Signaling IP address or FQDN of the RMX system or the DMA system ○ Port 5060 ○ Transport protocol TCP ○ Endpoint Trusted 28
Chapter 6: Integrating Polycom HDX Systems with Siemens OpenScape This chapter provides an overview of how to set up and configure a Polycom® HDX® system and integrate it with Siemens OpenScape® Voice. Once you configure the Polycom HDX system and integrate it with Siemens OpenScape software version 3.0.5, you can place and receive calls with Siemens OpenScape Desktop Client PE, Desktop Client WE, and Siemens OpenScape Voice version 6.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments OR ○ In the address bar of your web browser, type in the IP address of your HDX system, press Enter, and choose Administrator Settings > LAN Properties. If your system is password protect, a login dialog displays when you choose Administrator Settings. The default user name is admin and the default password is the serial number of your HDX system. If you don’t know the password, contact your the system administrator.
Integrating Polycom HDX Systems with Siemens OpenScape Note: Changes to These Settings Require and Cause a System Restart Changes you make to these settings require a system restart. If you make changes to these settings, the system automatically restarts when you accept the changes. 2 On the LAN Properties screen, configure the following fields: • IP Address (Ipv4) ○ IP Address Specify how the system obtains an IP address.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ Default Gateway Displays the gateway currently assigned to the system. If the system does not automatically obtain a gateway IP address, enter one here. ○ Host Name Indicates the system’s Domain Name System (DNS) name. ○ Domain Name Displays the domain name currently assigned to the system. If the system does not automatically obtain a domain name, enter one here.
Integrating Polycom HDX Systems with Siemens OpenScape ○ ICMP Transmission Rate Limit (millisec) Specifies the minimum number of milliseconds between transmitted packets. Enter a number between 0 and 60000. The default value of 1000 signifies that the system sends 1 packet per second. If you enter 0, the transmission rate limit is disabled. This setting applies only to error ICMP packets. This setting has no effect on informational ICMP packets, such as echo requests and replies.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments • SIP SIP Signaling, Far End Camera Control, Binary Floor Control Protocol (BFCP) Specifying HDX SIP Settings Once you have configured the Polycom HDX system LAN properties, specify Session Initiation Protocol (SIP) settings to connect SIP calls using Siemens OpenScape Voice. You can configure SIP settings using the system user interface or the web interface.
Integrating Polycom HDX Systems with Siemens OpenScape OR ○ In the address bar of your web browser, type in the IP address of your HDX system, press Enter, and choose Administrator Settings > Network > IP Network > SIP Settings. Note that if your system is password protected, a dialog displays when you choose Administrator Settings. The IP Network screen display, shown next.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 2 Configure the following settings: ○ Enable SIP Enable ○ Transport Protocol This field determines the protocol the system uses for SIP signaling. The SIP network infrastructure in which your Polycom HDX system is operating determines which protocol is required. You can choose from the following options: » Auto enables an automatic negotiation of protocols in the following order: TLS, TCP, UDP.
Integrating Polycom HDX Systems with Siemens OpenScape Note: Cascaded multipoint is not supported in SIP calls. Cascaded multipoint is not supported in SIP calls. For more information about SIP compatibility issues, refer to the Release Notes for Polycom HDX Systems. Specifying H.323 Settings (Optional) If your network uses a gatekeeper, you can choose to have the HDX system automatically register its H.323 name and extension, enabling others to call the system by entering that H.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments OR ○ In the address bar of your web browser, type in the IP address of your HDX system, press Enter, and choose Administrator Settings > Network > IP Network. Note that if your system is password protected, a dialog displays when you choose Administrator Settings. The IP network screen displays the H.323 settings, as shown next. 2 Configure the following H.323 settings: ○ Enable IP H.323 Check this option to enable IP H.323.
Integrating Polycom HDX Systems with Siemens OpenScape ○ Use Gatekeeper A gatekeeper manages functions such as bandwidth control and admission control. The gatekeeper also handles address translation, which enables users to make calls using static aliases instead of IP addresses that may change each day. You can choose from the following options: » Off Calls do not use a gatekeeper. If you choose Off, the Primary Gatekeeper IP Address field is not displayed.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments • Alternate Gatekeepers This field is not configurable and displays the alternative gatekeeper as a FQDN or by IP address. Using Polycom’s On Demand Conferencing Solution Polycom's on demand conferencing solutions let you hold calls and conferences on the fly without making plans or reservations in advance. Polycom offers a number of collaboration solutions that enable rapid decision making and improved responsiveness.
Chapter 7: Integrating Polycom RMX Systems with Siemens OpenScape This chapter shows you how to configure Polycom® RMX® 1500/2000/4000 systems and integrate the system with Siemens OpenScape® products. For more detailed information about configuring a Polycom RMX system, refer to the Polycom RMX documentation on the Polycom Support site.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Figure 7-1: Management Network and Network Service When using the RMX system with multiple services, you require five IP network services for the RMX 4000 and three IP network services for the RMX 2000 and RMX 1500. Setting Mandatory System Flags Next, you need to set mandatory system flags. To set system flags: 1 Navigate to Setup > System Configuration. The System Flags dialog displays.
Integrating Polycom RMX Systems with Siemens OpenScape 2 Set the following system flags: ○ SIP_FREE_VIDEO_RESOURCES NO This setting is required because the OpenScape Desktop Client escalates from Audio to Video and is mandatory. ○ ENABLE_SIP_PPC_FOR_ALL_USER_AGENT YES This setting is required to enable Binary Floor Control Protocol (BFCP), which enables content over SIP, between the RMX system and the HDX system and is mandatory.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ RMX2000_RTM_LAN YES This flag enables network separation using RTM LAN card for media and is only required when you use RTM LAN card. ○ ALWAYS_FORWARD_DTMF_IN_GW_SESSION_TO_ISDN YES This setting allows you to send DTMF tones through an IP-ISDN gateway call and is mandatory if you use an IP-ISDN Gateway. ○ SEND_SRTP_MKI NO This setting is required and mandatory if you use TLS.
Integrating Polycom RMX Systems with Siemens OpenScape For more information, refer to the Polycom RMX 1500/2000/4000 Administrator’s Guide. Setting Up a Conferencing Network Service You can use the Conferencing Network Service to configure and manage communications between the Polycom RMX system and conferencing devices such as endpoints, gatekeepers, SIP servers, and so forth.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments To view or modify the Management Network Service: 1 In the RMX Management pane, choose IP Network Services, shown next.
Integrating Polycom RMX Systems with Siemens OpenScape 2 In the IP Network Services screen, choose Management Network, shown next. The IP Network Services screen displays, shown next. 3 Modify the following fields: ○ Network Service Name This field displays the name of the management network. You cannot modify this name. Note that this field displays in all Management Network Properties tabs.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ IP Version Choose one of the following versions: » IPv4 Select this option for IPv4 addressing only. » IPv6 Select this option for IPv6 addressing only. » IPv4 & IPv6 Select this option for both IPv4 and IPv6 addressing. ○ IPv6 Configuration Method Choose Auto (Stateless) or Manual.
Integrating Polycom RMX Systems with Siemens OpenScape 4 Click Routers, shown next, and modify the following fields: ○ Default Router IP Address Enter an IPv4 or IPv6 IP address for 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.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ Static Routes IPv4 Only Table Select the type of router connection: » Network Defines a connection to a router segment in another network. » Host Defines a direct connection to an endpoint found on another network. 5 Choose DNS and modify the following fields: ○ MCU Host Name Enter the name of the MCU on the network. The default name is RMX.
Integrating Polycom RMX Systems with Siemens OpenScape » Secondary Server » Tertiary Server 6 If you are using an RMX 2000, choose LAN Ports and modify the following fields: Admin Tip: Configuring RMX 1500/4000 and RMX 2000 LAN Port Modes When configuring 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.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ Speed Choose the speed and transmit/receive mode for each port. The default setting is Auto which starts at 1000 Mbps Full Duplex, proceeding downward to 10 Mbps Half Duplex. To maximize conferencing performance, especially in high bit rate call environments, use a 1Gb connection. 7 Click OK. If you have modified the Management Network Properties, reset the MCU.
Integrating Polycom RMX Systems with Siemens OpenScape 2 In the IP Network Services screen, choose Default, shown next. Note that Default refers to the default network service.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments The Default Properties screen displays the default network service settings. 3 Modify the following fields: ○ Network Service Name Enter the name of the IP network service. The Fast Configuration Wizard assigns Default IP Service as the default value in the Network Service Name field. ○ IP Network Type Displays the network type selected the first time you enter configured this field.
Integrating Polycom RMX Systems with Siemens OpenScape ○ Signaling Host IP Address Enter the address you want IP endpoints to use when dialing in to the MCU. Dial out calls from the RMX system are initiated from this address. This address is used to register the RMX system with a Gatekeeper or a SIP Proxy server. ○ Media Card 1 Port 1 IP Address and Media Card 1 Port 2 IP Address (RMX 4000) If only one network is connected to this media card, it is enough to assign one media card to this Network Service.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Configuring Gatekeeper Settings This section shows you how to configure gatekeeper settings. To configure gatekeeper settings: 1 Click the Gatekeeper Tab. The Gatekeeper settings display, as shown next.
Integrating Polycom RMX Systems with Siemens OpenScape 2 Modify the following fields: ○ Gatekeeper Choose one of the following options: » Specify Enables configuration of the gatekeeper IP address. » Off Disables all gatekeeper options. ○ Primary Gatekeeper Enter an IP Address or the gatekeeper’s host name registered in the DNS. Admin Tip: Use a Hostname in IPv4 & IPv6 or IPv6 Mode When in IPv4 & IPv6 or in IPv6 mode, it is easier to use a hostname instead of an IP address.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ MCU Prefix in Gatekeeper Enter the number that the Network Service registers with in the gatekeeper. H.323 endpoints use this number as the first part of their dial-in string when dialing the MCU. Note that when you use PathNavigator SE200, this prefix automatically registers with the gatekeeper. When another gatekeeper is used, this prefix must also be defined in the gatekeeper.
Integrating Polycom RMX Systems with Siemens OpenScape Configuring Ports Settings in the Ports tab allow you to allocate specific ports in the firewall to multimedia conference calls. The port range recommended by the Internet Assigned Numbers Authority (IANA) is 49152 to 65535. The MCU uses this recommendation along with the number of licensed ports to calculate the port range. To configure ports: 1 Click Ports. The Ports settings display, shown next.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 2 Modify the following fields: ○ Fixed Ports Check this option to manually define the port ranges or to limit the number of ports to be left open. Leave this option cleared if you are defining a Network Service for local calls that do not require configuring the firewall to accept calls from external entities.
Integrating Polycom RMX Systems with Siemens OpenScape • Transmission error rate The RMX system supports two QoS methods: DiffServ and IP Precedence. Each method uses a different way to encode packet priority in the packet header. The RMX system implements QoS per Network Service, not per endpoint. Note: The Routers Must Support QoS Note that the routers must support QoS to allow IP packets to get higher priority. To configure QoS settings: 1 In the RMX Management pane, click QoS.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 2 Modify the following fields: ○ Enable Check this option to enable the configuration and use of the QoS settings. When unchecked, the values of the Differentiated Services Code Point (DSCP) bits in the IP packet headers are zero. ○ Type Choose a method for encoding packet priority. The priority you set here for audio and video packets must match the priority set in the router.
Integrating Polycom RMX Systems with Siemens OpenScape Note: You can use Unicode encoding in all SIP Signaling Dialogs. You can use Unicode encoding and character sets that use Unicode encoding for all SIP Signaling settings. 2 Modify the following fields: ○ IP Network Type Displays the network type selected the first time you enter configured this field. The Default IP Network icon indicates the selected environment.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments » H.323 For an H.323-only Network Service. » SIP For a SIP-only Network Service. » H.323 & SIP For an integrated IP Service. Both H.323 and SIP participants can connect to the MCU using this option. ○ SIP Server Use the default value Specify. ○ SIP Server Type Choose one of the following options: » Generic Choose Generic. ○ Refresh Registration every The time that an inactive RMX will re-register with OpenScape Voice.
Integrating Polycom RMX Systems with Siemens OpenScape ○ SIP Servers You can use one or more primary or alternate servers. » Server IP Address or Name SIP IP address or FQDN of the OpenScape Voice. Enter the IP address of the preferred SIP server. Admin Tip: Use a Hostname in IPv4 & IPv6 or IPv6 Mode When in IPv4 & IPv6 or in IPv6 mode, it is easier to use Names instead of IP addresses.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ Outbound Proxy Servers Primary / Alternate Server Parameter Server IP Address or Name Enter the SIP IP address or Fully Qualified Domain Name (FQDN) of OpenScape Voice. By default, the Outbound Proxy Server is the same as the SIP Server. If they differ, modify the IP address of the Outbound Proxy and the listening port number. Port: 5060 Enter the port number that the outbound proxy is listening to.
Integrating Polycom RMX Systems with Siemens OpenScape 2 Modify the following fields: ○ Authentication User Name Enter the conference, entry queue, or meeting room name that is registered with the proxy. This field can contain up to 20 ASCII characters. ○ Authentication Password Enter the conference, entry queue, or meeting room password as defined in the proxy. This field can contain up to 20 ASCII characters.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Modifying Ethernet Settings When using 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.
Integrating Polycom RMX Systems with Siemens OpenScape To modify the automatic LAN port configuration: 1 On the RMX menu, click Setup > Ethernet Settings, shown next.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments The Ethernet Settings dialog displays. Note: The RTM LAN port on the RMX 1500/4000 is Port 2. Although the RTM LAN (media card) port on the RMX 1500/4000 is shown as Port 1 in the Ethernet Settings and Hardware Monitor fields, the physical LAN connection is Port 2. 2 Modify the following fields: ○ Port Type Indicates the LAN port type. ○ Speed Select the speed and transmit/receive mode for each port.
Integrating Polycom RMX Systems with Siemens OpenScape Monitoring the IP Network The Signaling Monitor is the RMX entity used to monitor the status of external IP network entities such as the gatekeeper, DNS, SIP proxy, and Outbound proxy and their interaction with the MCU. To monitor signaling status: 1 In the RMX Management pane, click Signaling Monitor, shown next. 2 In the Signaling Monitor pane, choose the Default IP Service. The RMX CS IP tab displays.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments The RMX CS IP screen displays the following settings: ○ Service Name The name assigned to the IP Network Service by the Fast Configuration Wizard. ○ IPv4 » IP Address the IP address of the RMX. » 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.
Integrating Polycom RMX Systems with Siemens OpenScape 3 Click H.323. The H.323 settings display. ○ Connection State The state of the connection between the Signaling Host and the gatekeeper: » Discovery The Signaling Host is attempting to locate the gatekeeper. » Registration The Signaling Host is in the process of registering with the gatekeeper. » Registered The Signaling Host is registered with the gatekeeper. » Not Registered The registration of the Signaling Host with the gatekeeper failed.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ IP Address The gatekeeper’s IP address. 4 Click SIP Servers. The SIP Servers settings display. ○ Role » Active The default SIP Server is used for SIP traffic. » Backup The SIP Server is used for SIP traffic if the preferred proxy fails. ○ Name The name of the SIP server. ○ IP The SIP server’s IP address. ○ Status The connection state between the SIP Server and the Signaling Host. » Not Available No SIP server is available.
Integrating Polycom RMX Systems with Siemens OpenScape Using IPv6 Network Addresses for RMX Internal and External Entities Not all IPv6 settings are available. You can assign the following IPv6 addresses to RMX (Internal) and External Entity addresses.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Viewing Licensing and System Information You can view licensing and system information for your RMX. 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: 1 On the RMX menu, click Administration > System Information.
Integrating Polycom RMX Systems with Siemens OpenScape The System Information screen displays the following information: ○ Total Number of CP Resources Total Number of Event Mode Resources Note that event mode is currently not supported and this field will always display zero resources. ○ RMX Version Displays the System Software Version of the RMX. ○ ISDN/PSTN The field value indicates whether RTM ISDN/ PSTN hardware has been detected in the system. You can choose True or False.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments ○ Telepresence Mode The field value indicates whether the system is licensed to work with RPX and TPX Telepresence room systems. You can choose True or False. ○ Serial Number This field displays the serial number of the RMX system. ○ Multiple Services A Multiple Services license is installed.
Chapter 8: Integrating Polycom VVX Phones with Siemens OpenScape This chapter provides an overview of how to set up Polycom® VVX® business media phones for integration with Siemens OpenScape® products. For more detailed information about configuring VVX phones, refer to the documentation on the Polycom Support site. Polycom VVX phones running Polycom UC Software version 4.0.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 2 Choose to log in as Admin and enter the Password (default 456). 3 Go to Settings > Lines, and choose the Line Key you want to configure. The settings for that line display, shown next.
Integrating Polycom VVX Phones with Siemens OpenScape » Display Name Enter the name of the phone user. » Address Enter the directory number of the OpenScape Video. » Label Enter the name you want to display on the line key of another party you call. ○ Authentication » Authentication User ID Enter the digest authentication user name. » Authentication Password Enter the digest authentication user name. ○ SIP Server 1 » Address Enter the OpenScape Video IP or DNS-Name.
Chapter 9: Integrating Polycom DMA Systems with Siemens OpenScape This chapter provides an overview of how to set up and configure Polycom® Distributed Media Application™ (DMA™) Systems to interoperate with Siemens OpenScape® products. For more detailed information about configuring DMA systems, refer to the documentation on the Polycom Support site. Polycom DMA systems running software version 5.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 5 Go to Log in > Admin > Local Cluster > Signaling Settings, as shown next. The DMA Signaling Configuration screen displays.
Integrating Polycom DMA Systems with Siemens OpenScape 6 Configure the following settings on the DMA Signaling Configuration screen: ○ SIP Settings » SIP Signaling Check to enable. » Unencrypted SIP port Choose TCP, 5060. » TLS port 5061 Next, add an external SIP peer. To external SIP peer the DMA system: 1 Launch your web browser and enter the IP Address of your DMA System, for example, http://10.1.1.24 . 2 Click on Continue to this website (not recommended).
Deployment Guide for Siemens Enterprise Communications OpenScape Environments 6 Choose to Add to add a new SIP Peer or choose Edit to modify an existing SIP Peer. 7 The Edit External SIP Peer dialog displays.
Integrating Polycom DMA Systems with Siemens OpenScape 8 Configure the following fields: ○ Enabled Check this option. ○ Name Enter a name for the SIP trunk. ○ Description Enter a detailed description (can also be blank). ○ Next hop address Enter a SIP IP address or the FQDN of the OpenScape Voice. ○ Destination network Enter the OpenScape Domain name (can also be blank). ○ Port 5060 for UDP/TCP or 5061 for TLS ○ Use route header Check this option. ○ Prefix range Type in a single prefix number.
Chapter 10: Known Issues The following table lists known issues for this release. If a workaround is available, it is noted in the table. Table 10-1: Feature Limitations Issue ID Found in Release Description Workaround SI-84 RMX V7.2 If an RMX system is reset while there is an active conference, the conference with its SIP participants is not released. Reset the RMX system after terminating all active conferences. SI-97 RMX 7.
Deployment Guide for Siemens Enterprise Communications OpenScape Environments Issue ID Found in Release Description Workaround SI-197 HDX 3.0.5 The HDX clears H.323 calls after 2-5 minutes (HDX/ACME/OpenScape Voice). H323/SIP GW calls via ACME are currently not supported. Use DMA behind the ACME as H.323 to SIP Gateway.
