Polycom® Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communications™, Version 2 Version 2 | October 2011 | 3725-62124-002/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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Siemens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Polycom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Supported Versions . . . .
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Video Systems Available in a UC Client's Address Book or Buddy List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6 Presence Information for Video Endpoints . . . . . . . . . . . . . . . . . . . . . 3–6 Connecting Non-SIP Video Systems to SIP Video . . . . . . . . . . . . . . . . 3–6 H.323 Video Endpoints Connected to OpenScape Video V3 . . .
Contents 7 Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape IP Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1 Mandatory System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2 Management Network (Primary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2 Network Service (Conferencing Service) . . . . . . . . . . . . . . . . . . . . . . .
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations vi Polycom, Inc.
1 Introduction This document includes the requirements for the Polycom and Siemens video interoperability that Siemens refers to as OpenScape Video Solution V3 for Siemens Enterprise Communications. The Siemens OpenScape Video V3 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.
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 OpenStage 40 and OpenStage 60 phones OpenStage 10, 15, 20, and 40 phones have the same software. Open Stage 60 and 80 have the same software.
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 6.0 DMA 7000 4.0 Polycom HDX Series Systems 3.0.3 Polycom RMX 1500/2000/4000 7.6 Polycom VVX 1500 4.0 Polycom Telepresence RPX, ATX, OTX 3.0.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Support For Siemens OpenScape Video Solution issues, contact your Siemens support representative. For Polycom product equipment issues, contact Polycom Global Services or 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 V3 deployment solution. Polycom, Inc.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations OpenScape Video V3 Solution Features The OpenScape Video V3 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 can be selected as preferred devices for incoming and outgoing calls. • Simple presence information is supported. • Collaboration is possible with other video devices or audio devices such as OpenStage desktop phones, any mobile handset, and any smartphone including iPhones or Android-based phones. OpenScape Desktop Clients OpenScape Desktop Client PE V3.2 client, OpenScape Desktop Client WE V3.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Enterasys in Combination with OpenScape Video Enterasys allows location services for Polycom video endpoints. It streamlines inventory management and endpoint detection. Enterasys provides a way to authenticate and authorize video room and desktop systems independent from the network vendor.
3 Architecture Overview Unified Video communications for enterprises usually include the following services: • A call control system that is responsible for setting up voice or video connections based on a dialed E.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations OpenScape Video Architecture 3–2 Polycom, Inc.
Architecture Overview Physical Layer SIP Polycom, Inc.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations H.323 DMA System as Gatekeeper XMPP, API, ISDN 3–4 Polycom, Inc.
Architecture Overview Support of Media Escalation Media escalation is supported on Polycom HDX and VVX systems. It is a feature of the OpenScape Desktop Client that allows users to start a video call or video conference as an audio-only connection and then manually switch to video. Participants can call in by audio and join as video participants when they are ready, which can be useful in some situations when a caller is not yet ready to be seen on video.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Video Systems Available in a UC Client's Address Book or Buddy List Video endpoints, as all other audio endpoints, have been given an E.164 number and are members in the dialing plan of an enterprise. Thus, they are entries in the global directory and can be added to any personal address book or buddy lists.
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 Solutions V3 provides SBC-based interdomain video and gateway-based interdomain video.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Another example is a caller using a campus video system who wants to call a salesperson at a customer premise and add him or her to an established conference. Both the on-campus and off-campus parties are registered through the on-campus OpenScape Video.
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 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 1 The Enterasys NMS will import the data of physical infrastructure (Switches, Routers) from the database. 2 The Enterasys NMS will communicate with the Management Appliance to identify on which Switch and on which port of the Switch the HDX system or VVX 1500 is connected.
Use Cases from the Network Perspective Virtual MCUs in OpenScape Video V3 Polycom® Distributed Media Application™ (DMA™) 7000 allows configuration of virtual MCUs. These might consist of two or more physical MCUs, such as Polycom RMX system or others, which can be accessed as one single MCU. One benefit of this solution is better scalability, load balance, and network simplification. The major advantage is support for mission critical video conferencing.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Use Cases Provided for Resilient Video Conferencing Centralized Conference Resource Management A centralized conference resource management application is needed to create a pool of conference servers that behave as one large conference server.
Use Cases from the Network Perspective Automatically Route 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.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 4–12 Polycom, Inc.
5 Configuring Siemens OpenScape Voice to Interoperate with Polycom Products This chapter provides an overview of how to set up and configure Siemens OpenScape Voice to interoperate with Polycom products. Configuring Siemens OpenScape Voice Properties The instructions in this section are for configuring OpenScape Voice properties when setting them up to interoperate in a Polycom environment. OpenScape Voice Subscriber To configure OpenScape Voice Subscriber properties: Polycom, Inc.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations The following dialog box opens: In the General tab of the Subscriber screen you will find the Directory Number. This number will be used in the SIP configuration of the HDX system as the User Name field and in the VVX configuration as the Address field. 5–2 Polycom, Inc.
Configuring Siemens OpenScape Voice to Interoperate with Polycom Products In the Security tab of the Subscriber screen you will find the User Name and Password for HTTP Digest Authentication. These fields will be used in the SIP configuration of the HDX system as the Domain User Name and Password fields and in the VVX configuration as the Authentication User ID and Authentication Password fields.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations In the SIP tab of the Endpoint make sure the following fields are set correctly: — 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 5–4 Polycom, Inc.
6 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: support.polycom.com. Configuring Polycom ATX, OTX and RPX system to interoperate with Siemens OpenScape will be very similar. 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, do one of the following: 6–2 • In the local interface, go to System > Admin Settings > LAN Properties (select if necessary). • In the web interface, go to Admin Settings > LAN Properties. Polycom, Inc.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Configure these settings on the LAN Properties screen: Making changes to any of the settings on this page will cause the system to restart. • IP Address (IPv4) — IP Address: Specifies how the system obtains an IP address. » Obtain IP address automatically — Select if the system gets an IP address from the DHCP server on the LAN. » Enter IP address manually — Select if the IP address will not be assigned automatically.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations — Global Address: Displays the IPv6 internet address. — 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 DNS name. • Domain Name: Displays the domain name currently assigned to the system.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape • Enable PC LAN Port: Specifies whether the PC LAN port is enabled on the back of a Polycom HDX 4000, Polycom HDX 7000, Polycom HDX 8000 series, or Polycom HDX 9006 system. — Disable this setting for increased security. • Enable 802.1p/Q: Specifies whether VLAN and link layer priorities are enabled. The following settings are available only when 802.1p/Q is enabled: — VLAN ID: Specifies the identification of the Virtual LAN.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 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.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Configure the following settings: • Enable SIP: enable • Transport Protocol: TCP or Auto Indicates 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. Auto enables an automatic negotiation of protocols in the following order: TLS, TCP, UDP. This is the recommended setting for most environments.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations An example of an IPv6 address is: [2001:db8:85a3::8a2e:370:7334]:8032:8033 Points to note about SIP: The SIP protocol has been widely adapted for voice over IP communications and basic video conferencing; however, many of the advanced video conferencing capabilities are not yet standardized. Many capabilities also depend on the SIP server. Cascaded multipoint is not supported in SIP calls.
Configuring Polycom HDX Systems to Interoperate with Siemens OpenScape Configure these settings on the H.323 Settings screen: • Enable IP H.323: Box is checked • Display H.323 Extension: Allows users to enter H.323 extensions separately from the gateway ID on the Place a Call screen. If your system is registered with a gatekeeper, this setting also displays your H.323 extension on the home screen.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations • Primary Gatekeeper IP Address: The primary gatekeeper IP address contains the address with which the system registers. As part of the gatekeeper registration process, the gatekeeper might return alternate gatekeepers. If communication with the primary gatekeeper is lost, the HDX system registers with the alternate gatekeeper but continues to poll the primary gatekeeper.
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 6–12 Polycom, Inc.
7 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 a Polycom RMX system, refer to the Polycom RMX documentation on this web site: 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 Network Service (Conferencing Service) The Network Service (Conferencing Service) is used to configure and manage communications between the Polycom RMX system and conferencing devices such as endpoints, gatekeepers, SIP servers, and so forth.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 3 Modify the following fields: Field Description Network Service Name Displays the name of the Management Network. This name cannot be modified. Note: This field is displayed in all Management Network Properties tabs. IP Version IPv6 Configuration Method IPv4 Select this option for IPv4 addressing only. IPv6 Select this option for IPv6 addressing only.
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 4 Click the Routers tab and modify the following fields: Field Description Default Router IP Address IPv4 IPv6 Static Routes IPv4 Only Table Static Routes IPv4 Only Table 7–6 Enter 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.
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 Network Service. The wizard starts automatically if no Network Service is defined. This happens during First Time Power-up before the service has been defined or if the Network Service has been deleted, followed by an RMX system restart.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Modify the following fields: • Network Service Name: The name Default IP Service is assigned to the IP Network Service by the Fast Configuration Wizard. This name can be changed. This field is displayed in all IP Signaling dialog boxes and can contain character sets that use Unicode encoding. • IP Network Type: Displays the network type selected during the First Entry configuration.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape • Subnet Mask: Enter the subnet mask of the MCU. The default value is 255.255.255.0. Click the Routers Tab With the exception of IP Network Type, the field definitions of the Routers tab are the same as for the “Modifying the Management Network” on page 7-3. Click the Gatekeeper Tab The Network Service - Gatekeeper dialog box opens.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations • Primary Gatekeeper — IP Address or Name: Enter either the gatekeeper’s host name as registered in the DNS or IP address. When in IPv4 & IPv6 or in IPv6 mode, it is easier to use Names instead of IP addresses.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape • Aliases: — Alias The alias that identifies the RMX’s Signaling Host within the network. Up to five aliases can be defined for each RMX. When a gatekeeper is specified, at least one prefix or alias must be entered in the table. — Type The type defines the format in which the card’s alias is sent to the gatekeeper. Each alias can be of a different type: » H.323 ID (alphanumeric ID) » E.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Click the Ports Tab The Network Service Ports dialog box opens. Settings in the Ports tab allow specific ports in the firewall to be allocated 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.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape When ICE Environment is enabled, 8 additional ports are allocated to each call. • TCP Port from - to Displays the default settings for port numbers used for signaling and control. To modify the number of TCP ports, enter the first and last port numbers in the range. The number of ports is calculated as follows: Number of simultaneous calls x 2 ports (1 signaling + 1 control).
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations If Required, Click the QoS Tab The Network Service QoS dialog box opens. Quality of Service (QoS) is important when transmitting high bandwidth audio and video information. QoS can be measured and guaranteed in terms of: • Average delay between packets • Variation in delay (jitter) • Transmission error rate DiffServ and Precedence are the two QoS methods that the RMX system supports.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Modify the following fields: • Enable: Select to enable the configuration and use of the QoS settings. When un-checked, the values of the Differentiated Services Code Point (DSCP) bits in the IP packet headers are zero. • Type DiffServ and Precedence are two methods for encoding packet priority. The priority set here for audio and video packets must match the priority set in the router.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations — None No optimization definition is applied. This is a compatibility mode in which routing is based on Precedence priority settings only. Select None if you do not know which standard your router supports. Click the SIP Servers Tab The Network Service SIP Servers dialog box opens.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape • SIP Servers: Primary / Alternate Server Parameter — Server IP Address or Name : SIP IP address or FQDN of the OpenScape Voice Enter the IP address of the preferred SIP server. When in IPv4 & IPv6 or in IPv6 mode, it is easier to use Names instead of IP Addresses.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Click the Security Tab Modify the following fields: Field Description Authentication User Name Enter the conference, Entry Queue, or Meeting Room name as 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.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape To modify the automatic LAN port configuration: On the RMX menu, click Setup > Ethernet Settings. 1 The Ethernet dialog box opens. On the RMX 1500/4000, although the RTM LAN (media card) port is shown as Port 1 in the Ethernet Settings and Hardware Monitor fields, the physical LAN connection is Port 2.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations To monitor signaling status: 1 In the RMX Management pane, click Signaling Monitor. 2 In the Signaling Monitor pane, double-click Default IP Service. The RMX CS IP tab displays the following fields: Field Description Service Name The name assigned to the IP Network Service by the Fast Configuration Wizard. IPv4 IP Address Default Router IP Address The IP address of the default router.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape Click the H.323 tab. 3 The H.323 tab displays the following fields: Field Description 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.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Using IPv6 Network Addresses for RMX Internal and External Entities IPv6 addresses can be assigned to both RMX (Internal) and External Entity addresses.
Configuring Polycom RMX Systems to Interoperate with Siemens OpenScape • Participants that do not use the same IP address version as the RMX system in ongoing conferences launched from Meeting Rooms, Reservations and Conference Templates, and are disconnected. An error message, Bad IP address version, is displayed. • IP Security (IPSec) Protocols are not supported.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations Information Description Polycom Partners The field value indicates that the System Software contains features for the support of specific Polycom Partner environments. Memory Size [MB] This field indicates the RMX system memory size in MBytes. Possible values include the following: Card Configuration Mode • 1024 MB — Version 7.1 requires 1024 Mbytes of memory.
8 Configuring Polycom VVX Phones to Interoperate with Siemens OpenScape This chapter provides an overview of how to set up and configure Polycom VVX phones to interoperate with Siemens OpenScape products. For more detailed information about configuring VVX systems, refer to the documentation on this web site: support.polycom.com. Polycom VVX systems running software version 4.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations The following dialog box opens: Configure these settings on the VVX Configuration screen: SIP Settings — SIP Protocol: Enabled Identification — Address: Directory number of the OpenScape Video — Authentication User ID: Digest Authentication User Name — Authentication Password: Digest Authentication Password SIP Server 1 — Address: OpenScape Video IP or DNS-Name (preferred) — Port:5060 — Transpor
9 Configuring Polycom DMA Systems to Interoperate with Siemens OpenScape This chapter provides an overview of how to set up and configure Polycom DMA Systems to interoperate with Siemens OpenScape products. For more detailed information about configuring DMA systems, refer to the documentation on this web site: support.polycom.com. Polycom DMA systems running software version 4.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations The following dialog box opens: Configure these settings on the DMA Signaling Configuration screen: SIP Settings » Enable SIP signaling: Enabled » Unencrypted SIP port: TCP or UDP/TCP, 5060 » TLS port: 5061, default To configure the Polycom DMA system to add an external SIP Peer: 1 Open Internet Explorer. 2 Type in the IP Address of your DMA System (for example http://10.1.1.24).
Configuring Polycom DMA Systems to Interoperate with Siemens OpenScape The following dialog box opens: Configure these settings on the DMA Add External SIP Peer Configuration screen: — Enabled: Box is checked — Name: Type in a name — Description: Type in a detailed description (can also be blank) — Address: SIP IP address or FQDN of the OpenScape Video — Port: 5060 — Prefix range: Type in a single Prefix # — Type: Others — Transport type: TCP — Register externally: Box is checked Polycom, Inc.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 9–4 Polycom, Inc.
10 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 SI-10 HDX software 3.0.3 When the HDX system receives a call from an OpenScape desktop client on a TLS with MIKEY connection, the call will not be established. Initiate the call from the HDX system. SI-53 RMX V7.1.0.
Polycom Unified Communications Deployment Guide for the OpenScape Solution of Siemens Enterprise Communciations 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.
