OpenScape Voice

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Revision as of 21:30, 6 April 2011 by Peter Wellmann (talk | contribs) (System architecture)
Jump to: navigation, search
OpenScape Voice

OpenScape Voice is an IP softswitch for large and very large companies up to 100,000 users. OpenScape Voice was formerly known as HiPath 8000.

Performance features

The OpenScape Voice is a native SIP-based Real-Time IP System that is ideal for both large and very large enterprises and for managed service providers. Designed for data center deployment, OpenScape Voice fits perfectly into the IT world. It allows companies to simply and cost-effectively integrate converged voice, multi-media and multi-modal services.

System architecture

  • Software: SUSE Linux OS
  • Hardware:
    • IBM System x3250 M2
      • One 2.4 GHz Dual-Core Intel Xeon CPU
    • IBM System x3550 M2
      • Two 2.53 GHz Quad-Core Intel Xeon 5540 CPUs
    • IBM 3550 M3 (since OSV V5 R0.17.4)
    • PRIMERGY RX330 S1
      • Two Dual-Core CPUs

Applications and Devices

The following devices can be connected to OpenScape Voice:

Administration and Service

OpenScape Voice is administered via a web based interface, CMP/OpenScape Voice Assistant.

Networking scenarios

Networking Scenarios are discussed in Detail in the Edoku OpenScape Voice Networking Guide (non-public). However, note, that at least the VLAN design will be changed soon. Here, we document the new proposal.

Flat VLAN Design

In a flat VLAN design, the VLANs are extended from one OpenScape Voice node to the other. In case of failure of an active node, the IP addresses of this node is transfered to the other. A drawback of this design is, that high redundancy can only be achieved when using redundant layer 2 networks with the Spanning Tree Protocol being used to remove loops from the network. However, note, that Spanning Tree problems can lead to 100% network load and to the unavailibility of both OpenScape Voice nodes. Also, Spanning Tree problems are easy to troubleshoot. We recommend to a Split Subnet design with a Spanning Tree less design if possible.

Split Subnets

With the Split Subnets design, all VLANs except the cluster interconnect are local to one OpenScape Voice node only. See below a proposal of the VLAN design, which can not be found in the Edoku yet (version 2.2, issue 2):

Loop-less (Spanning Tree-less) VLAN Design for a HiPath 8000 Split Subnet Design

Loop-less (Spanning Tree-less) VLAN Design for a OpenScape Voice Split Subnet Design.

Note, that the Routers SHOULD NOT be attached redundantly. If e.g. Router 1 is attached to Switch 1 and Switch 2 with VLANs 2, 4 and 6 on both links, a layer 2 loop would be created (Router 1 -- Switch 1 -- Switch 2 -- Router 1). To resolve this, we will need Spanning Tree on the Switches as well as on the Router. However, the need for Spanning Tree is to be avoided and Spanning Tree should only be switched on the Switches for decreasing the impact on any erroneous miscabling.

See also