Siemens HiPath 5000 Real

DPRO-115916
Richard A. Costello
Product Report
27 June 2003
Siemens HiPath 5000 Real-Time IP System
Summary
With its HiPath 5000 Real-Time IP System, Siemens has a plan for enterprises with distributed networking
requirements in IP or mixed-telephony environments. In 2003 the capability will expand to 64 nodes and
2,000 users.
Note
This report is focused on the Siemens HiPath 5000 Real-Time IP System, which is version 4.0 of
Siemens’ next-generation IP softswitch platform.
Table of Contents
Overview
Analysis
Pricing
Competitors
Strengths
Limitations
Recommended Gartner Research
Insight
List Of Tables
Table 1: HiPath 5000 RSM Server Requirements
Table 2: Siemens IP Telephony Platform Summary
Table 3: Stations per Node
Table 4: Supported Devices Overview
Table 5: Supported Applications Overview
Table 6: HiPath 5000 Real-Time IP System List Pricing (US$)
List Of Figures
Figure 1: HiPath 5000 Real-Time IP System Distributed Architecture
Gartner
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.Reproduction of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be
reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations
thereof. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice.
Siemens HiPath 5000 Real-Time IP System
Corporate Headquarters
Siemens AG
Hofmannstrasse 51
81359 Munich, Germany
Tel: +49 89 7220
U.S. Headquarters
Siemens Information and Communication Networks (ICN), Inc.
900 Broken Sound Parkway
Boca Raton, FL 33487, U.S.A.
Tel: +1 561 955 5000
Toll Free: +1 800 765 6123
Internet: www.icn.siemens.com
Overview
Initially positioned as Siemens’ pure IP-switch hardware platform for the emerging IP telephony market
with models such as the HiPath 5300 and HiPath 5500, with version 4.0 the company has evolved the
HiPath 5000 into a real-time, enterprise IP softswitch platform with the availability of the HiPath 5000
Real-Time IP System, its next-generation release.
Existing HiPath 5500 v3.x and earlier systems, and HiPath 5300 v3.0 systems are not supported on
version 4.0. Siemens has, in fact, started the end of life process on the 5500 and 5300 models. The
migration path for HiPath 5500 users is to the HiPath 5000 Real-Time IP System; the migration path for
HiPath 5300 users is to the HiPath 3000 system.
Analysis
Version 4.0 of the HiPath 5000 Real-Time IP System works in conjunction with its network services
element—HiPath 5000 Real-Time Services Manager (RSM) software—and Siemens HiPath 3000
Survivable Media Gateways (SMGs) in support of a modular architecture, IP networking, remote
survivability and centralized management, among other functions, for distributed enterprise environments.
As such, at least one HiPath 3000 SMG is required in a HiPath 5000 RSM configuration to provide
backup (survivability) and media gateway functionality. HiPath 5000 can support a full set of traditional
Siemens PBX features in mixed IP and circuit switched environments.
A Siemens HiPath 5000 Real-Time IP System is comprised of the following basic components:
•
HiPath 5000 RSM v4.0 software
•
HiPath 5000 RSM server platform
•
HiPath 3000 SMG node(s)
The figure, HiPath 5000 Real-Time IP System Distributed Architecture, provides an illustration of the basic
components of a HiPath 5000 Real-Time IP System network solution.
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
2
Siemens HiPath 5000 Real-Time IP System
Figure 1: HiPath 5000 Real-Time IP System Distributed Architecture
Source: Siemens ICN
HiPath 5000 RSM v4.0 Software/Server
HiPath 5000 RSM v4.0 software can be purchased as a software-only package or installed on an industry
standard server (IBM xSeries 205) running the Microsoft Windows 2000 operating system; both software
and hardware platforms are supplied by Siemens. The 5000 RSM software comes pre-installed on the
IBM server. Available HiPath 5000 RSM software packages include the following:
•
HiPath 5000 RSM v4.0 Base Package Software-only (Software + License)
•
HiPath 5000 RSM v4.0 Base Package (Hardware + Software + License) for up to 15 nodes
•
HiPath 5000 RSM v4.0 Base Package (Hardware + Software + License) for up to 45 nodes
•
HiPath 5000 RSM v4.0 Base Package (Hardware + Software + License) for up to 64 nodes
Note: These base packages do not come pre-installed with HiPath ProCenter Office (contact center) or
HiPath Expressions (voice/unified messaging).
A customer-provided server with Microsoft Windows 2000 can be used as the HiPath 5000 RSM server
providing it meets the following hardware requirements.
Table 1: HiPath 5000 RSM Server Requirements
Components
Server
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
Min. Requirement
Intel Pentium III, 1GHz (1)
Recommended
2.4 GHz
DPRO-115916
27 June 2003
3
Siemens HiPath 5000 Real-Time IP System
Table 1: HiPath 5000 RSM Server Requirements
Components
RAM (2)
Min. Requirement
Recommended
Up to 15 nodes: 512MB
Up to 20 nodes: 1GB
Up to 45 nodes: 1.0GB
Up to 35 nodes: 1.5GB
Up to 64 nodes: 1.5GB
Up to 64 nodes: 2.0GB
—Telephony Application
Programming Interface
(TAPI) Service Provider
requires 154KB per
monitored line
Hard Disk
9GB
40GB (3)
Drives
3.5 in., 1.44MB
—
Cards
LAN Adapter 10/100MB
—
LAN interface with quality
of service (QOS)
Card Slots
Five Peripheral Component
—
Interconnect (PCI) slots,
full size
Ports
Two free serial ports
—
Monitor
Color monitor 17 in. Super
—
Video Graphics Array
(SVGA) with 800 x 600
resolution
Operating System
Microsoft Windows 2000
—
Server license with SP2;
Internet Information Server
Browser
Microsoft Internet Explorer
—
4.01 SP2 and later
Backup Medium
Compact disc rewritable
—
(CD-RW)
Remote Access
PcAnywhere and a modem
Manager E allows remote
(28.8Kbps) with direct
configuration and diagnosis
inward dialing (DID)
of all systems in a HiPath
extension or dedicated
5000 RSM network
central office (CO) line
Backup Software
—
Ghost 2002 Personal
Edition (4)
Virus Checker
Not included with Base
Latest version of McAfee
Packages, but considered
(customer provided)
mandatory.
1. With Get Account CDR activated, the minimum processor speed is 2GHz.
2.
Basic packages only without additional applications.
3.
Additional memory may be required if Get Account CDR is used.
4.
Customer is responsible for server data backup.
Approximately 100MB of free disk space is required locally for installation of the HiPath 5000 RSM server
software. An additional 1MB is required for each HiPath 3000 node installed. The processing power
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
4
Siemens HiPath 5000 Real-Time IP System
required by the HiPath 5000 RSM server application depends, on one hand, on the number of 3000
nodes. The number of access operations executed by the applications also determines the actual system
load.
HiPath 5000 RSM v4.0 software enables the administration and configuration of a network of up to 32
HiPath 3000 nodes and 1,000 end users presently for enterprises looking to create a single-system image
for distributed environments. Plans for the fourth quarter of 2003 will expand that capability to 64 nodes
and 2,000 users.
A HiPath 5000 RSM configuration is connected over an IP network via Siemens HG 1500 cards, which
tunnel Siemens’ proprietary networking protocol, called CorNet-N, over the IP network (CorNet IP), and
provide trunk ports to the IP network for connecting other HiPath 3000 nodes. All HG 1500 software and
HiPath 3000 system software must be at the same software release for operational compatibility and QOS
enablement. Each HiPath 3000 node must fulfill the following requirements:
•
Contain at least one HG 1500 V2.0 gateway (SMR 21 or later) for connection to the customer IP
network infrastructure
•
Be a Siemens HiPath 33xx, 35xx or 37xx platform
•
Have a Clock Module Small (CMS) in each HiPath 3000
HiPath 3000 SMG
The HiPath 3000 SMG has the same specifications as the HiPath 3000 product family and is an integral
part of Siemens’ strategy to evolve platforms that will satisfy the requirements of new and existing
customers who want to implement IP telephony capabilities. For example, the HiPath 3000 SMG provides
system backup and media gateway functions for the HiPath 5000 Real-Time IP System platform.
The following table summarizes maximum IP stations supported on the HiPath 3000 functioning as a
stand-alone system, on the HiPath 5000/HiPath 3000 SMG combination, and on the HiPath 4000
platform.
Table 2: Siemens IP Telephony Platform Summary
Maximum IP
Up to 500
Up to 2,000
Up to 4,000
Stations per
System
HiPath 3000
X
(stand-alone)
HiPath
X
5000/HiPath
3000 SMG (1)
HiPath 4000
X
(2)
1. Four nodes required to support up to 2,000 IP stations per system.
2.
Multiple HiPath 4000 systems can be networked to support over 4,000 IP stations.
User interface, system features and networking functionality are the same for the HiPath 3000 and HiPath
5000, but not the HiPath 4000. This means that networking a HiPath 4000 with either a HiPath 5000/3000
SMG or a stand-alone HiPath 3000 will limit user capabilities at remote sites and feature transparency
across the network.
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
5
Siemens HiPath 5000 Real-Time IP System
HiPath HG 1500
The HiPath HG 1500 integrated gateway module, when added to the HiPath 3000, provides connectivity
between the switched, time division multiplexing (TDM) network devices of the HiPath 3000 and the IP
network. The HiPath 3000 adds the ability to provide packet switching between IP devices on the LAN.
This makes the PBX features of the HiPath 3000 available to IP clients and phones located on the data
network.
This approach supports connectivity to 10Base-T or 100Base-T LANs and WANs provided by the
customer, as well as providing a gateway between IP terminals and public switched telephone network
(PSTN) facilities connected to the system.
This enables the HiPath 3000 product platforms to support technology solutions such as IP networking,
mobility, workpoints and voice over IP (VoIP) applications. One benefit is that with CorNet over IP
networking, multiple HiPath 3000 systems can be networked together using the customer’s existing
LAN/WAN infrastructure, eliminating previously required point-to-point, T1/PRI circuits.
The maximum number of calls between IP clients in different 3000 nodes depends on the number of HG
1500 boards active in the node, irrespective of the number of B channels licensed for the system. For
example, in a HiPath 37xx system with two HXGM boards (the HG 1500 gateway card for 37xx), the
maximum number of calls from IP clients to other nodes is 32. In a HiPath 35xx with two HXGS boards
(HG 1500 gateway card for 3350/3550), the maximum number of conversations from IP clients to other
nodes is 16 (2 x 8).
In a pure IP network, the number of gateway channels must be equal to or larger than the number of TDM
trunks. The number of HG 1500 boards required for voice over IP is determined by the number of
gateway channels, plus music-on-hold channels, plus conference channels.
An HG 1500 gateway can also be used as an Integrated Services Digital Network (ISDN) router, an
application more prevalent in Europe, where ISDN is more popular. A remote user, for example, could
connect directly from a home PC via an ISDN connection to the company LAN, to which the HG 1500 is
connected. The complete path must be an ISDN connection.
Stations per Node
The maximum number of stations supported in a HiPath 5000 node (v3.0 and above) are also available to
HiPath 3000 clients, as indicated in the table below.
Table 3: Stations per Node
HiPath 37xx
Max. total # of
HiPath 3550
HiPath 3350
500 (1)
192
96
500 (1)
312 (+2x SLU8)
120
stations
Max. total # of
stations
possible in the
max. system
configuration
with all HG
1500s
activated
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
6
Siemens HiPath 5000 Real-Time IP System
Table 3: Stations per Node
HiPath 37xx
Max. # of
HiPath 3550
HiPath 3350
500 (1)
192
96
96
48
48
HG 1500s per
8 (max. of 6
4
2
system
per cabinet)
TDM
384 (2)/116
188/188
62/62
clients
Clients per HG
1500 gateway
master/slave
ports
1. These capacities can only be reached with HiPath 3000 v3.0 cabinets. A max. of 384 users can be
reached with older version cabinets.
2.
A max. of 250 TDM users can be reached with older version cabinets.
HiPath IP Networking
In a HiPath 5000 RSM network configuration, the HiPath 5000 RSM server and all HiPath 3000 SMG
nodes and client PCs should be located in the same IP network. All 5000 RSM and 3000 SMG
components must be in a “switched” environment—that is, no LAN hubs—with the connections between
the LAN switches being customer-provided. Although possible to have a TDM connection between two
different IP networks or two domains, it is not recommended because the number of IP-to-TDM-to-IP
translations will introduce latency and voice quality degradation.
Telephony over the 5000 RSM IP network is based on the Institute of Electrical and Electronics Engineers
(IEEE) 802.1D QOS standard, which prioritizes voice traffic for transmission over the IP network.
To reduce system administration, the HiPath 5000 RSM system uses a login concept for network nodes
that allows a newly added HiPath 3000 node to register independently on the HiPath 5000 RSM server.
After startup and administration of the 3000 node, it logs into the 5000 RSM server. Once this login
process occurs, basic IP communications between the 3000 node and the 5000 RSM server are
established. If a pre-configured database exists on the 5000 RSM server for this 3000 node, the 5000
RSM server now automatically loads it into the 3000 node. After this has been configured, the node
becomes part of the HiPath 5000 system and is networked with the other nodes over IP.
In addition to the local IP address already available, the IP address of the 5000 RSM server must also be
configured in the 3000s using an enhanced version of HiPath 3000 Manager E or Manager T, which are
Siemens system and database administration tools. The IP address of the HiPath HG 1500 must also be
managed on the 5000 RSM server. An assignment between nodes and the relevant database is possible.
Multiple IP addresses (multiple HiPath HG 1500s in a node) can be assigned to a database.
IP Network Features
Features, functions and applications supported on HiPath 5000 RSM include the following:
•
IP networking—supports HiPath 3000, HiPath 5000 RSM server and client PCs on an IP network
•
A centralized database for all HiPath 3000 nodes
•
Get Account application—a centralized call detail record (CDR) database for consolidating network
call accounting information
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
7
Siemens HiPath 5000 Real-Time IP System
•
HiPath Accounting Management—supported via an export interface from the GetAccount
application; packages for 100, 200, 300 and 400 users are available
•
HiPath Fault Management 2—an optimized version of HiPath Fault Management for monitoring
HiPath 3000 systems in a HiPath 5000 RSM network
•
Presence Server—a centralized Direct Station Select/Busy Lamp Field (DSS/BLF) service for call
status indications on phones and optiClients across nodes
•
Personal Call Manager (PCM)—a TAPI-based, incoming call handling application (call forwarding)
for individual HiPath 3000 stations
General Features Over CorNet IP Network
The general feature set supported in a HiPath 3000 v4.0 corporate network is the feature set supported in
a HiPath 5000 RSM CorNet IP network:
•
Connection setup
•
DID calls in the network
•
Transfer of call number and name
•
Display presentation of call number and name
•
Callback on busy and no answer
•
Call forwarding no reply
•
Call forwarding (calls rerouted to optimize B-channel use)
•
Message waiting display for callback and voice mail messages
•
HiPath 3000 call waiting
•
Networkwide classes of service (a max. of four classes of service)
Additional system features include:
•
Networkwide common numbering plan
•
Call number and name suppression
•
Consultation call (over a second B channel, for example)
•
Switch/transfer (conservation of trunks if the station is transferred)
•
Blind transfer
•
Conference with a max. of five stations (no global display function)
•
Cross-node hunt group and group call
•
Directed joining and leaving of the group across all nodes
•
Hunt group overflow
•
CDR solution for all network nodes (Get Account)
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
8
Siemens HiPath 5000 Real-Time IP System
•
Transit traffic
•
Least cost routing (LCR)
•
Call pickup groups with stations from other nodes
•
Call forward chaining
•
Central attendant console (OptiPoint Attendant) with busy signal for IP stations
•
Central attendant console functions: Forward, assign, automatic recall, hold
•
Announcement devices (configured in the node of its use only)
Key feature descriptions include:
•
Central Attendant Console—A network-wide DSS/BLF feature allows busy signaling for
phones/clients on HiPath 3000s in the network. Up to six Siemens OptiClient Attendants can have
network-wide BLF appearances, but all of them must be registered in the same node.
•
Automatic Routing—Automatic routing to a backup or alternative network for new connections can be
performed. A TDM network (for example, an ISDN dialup connection) can also be used as a backup
network. Automatic routing is initiated when the destination HiPath 3000 is not accessible because of
an error or overload in the IP network; when no additional capacity is available for LAN access (all B
channels of the HG1500 boards are busy); or when a connection via LCR is explicitly requested.
•
Standard Numbering Plan—The phone number of the remote HiPath 3000 is converted to the IP
address in the HG 1500 gateway. To ensure that the IP address of the correct destination node can
be used, a routing table is created. The table assigns the correct IP address to each phone number,
corresponding tie trunk or prefix number. A standard numbering plan is required for this purpose,
meaning that the internal call numbers of each communication platform have the same length and
begin with different digits.
•
Network Management—All network nodes are administered using an enhanced version of HiPath
3000 Manager E, a configuration management tool which is included with HiPath 5000 RSM software
and installed on the server. From there, it is possible to have central administration of all HiPath 3000
nodes in a shared database.
The HiPath 5000 RSM performs the following administration and configuration functions in a network:
•
Administration of all node customer databases in a single, central database
•
Node registration
•
Transfer of the customer databases to the nodes
•
Transfer of the Call Address Resolution (CAR) tables to the HiPath HG 1500 boards (required for
routing in the IP network)
•
Synchronization of the nodes’ customer database files (application of individual settings, such as key
programming)
•
Configuration installation for additional nodes
The HiPath 5000 RSM platform can be integrated with Simple Network Management Protocol-based
(SNMP) management platforms such as HP OpenView.
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
9
Siemens HiPath 5000 Real-Time IP System
IP Network Infrastructure Requirements
Installation of a HiPath 5000 RSM requires a complete network analysis of the proposed customer
environment, including completion of an Electronic System Assurance (ESA) Checklist, Applications
Design Checklist, and a Call Flow Diagram, and submission to Siemens Professional Services for
assistance and approval.
HiPath 5000 RSM and the networked HiPath 3000 systems rely on an enterprise IP network, place
additional load on that network and will not work properly if network problems occur. Some of the
infrastructure requirements of the IP LAN for a HiPath 5000 RSM installation are described below:
•
Switched 10/100 Mbps LAN
•
Fixed IP addresses (no Dynamic Host Configuration Protocol [DHCP])
•
Each component must have its own port at the data switch (no hubs as concentrators)
•
Pure Microsoft TCP/IP network (not a Novell network with IPX/SPX)
•
QOS procedure support in accordance with IEEE 802.1q (Layer 2)
•
Type of Service (TOS) support in accordance with request for comments (RFC) 791 (Layer 3)
package prioritization
•
Differentiated Services (DiffServe) procedure support in accordance with RFC 2474 (Layer 3)
•
The required network bandwidth for International Telecommunication Union (ITU) G.711, or ITU
G.723.1 codecs support
The network delay factor should not be greater than 50 ms (one-way delay), since the natural voice
communications process is impaired if longer delay times are introduced. Priority control is a particularly
efficient means of reducing delay. To combat delays and loss of quality, Siemens recommends the use of
higher bandwidths (reserves), or G.723.1 codecs.
To guarantee QOS, the following standards must be met:
•
All the components involved in transmitting voice data must support IEEE 802.1q (Layer 2) at least.
•
In addition, all components require routing according to DiffServe standard RFC 2474 and TOS
standard RFC 791.
•
(L2) Layer 2/Layer 3 (L3) QoS: In HiPath 3000 v4.0, priorities can be set, but L2 priorities cannot.
Since L3 priorities are typically set according to RFC 2597, this will create an inconsistency for the
voice payload tag, which should be set at five. Configuration of the L2 QOS settings will be
addressed in a future release.
HiPath 5000 Real-Time IP System Supported Devices
Table 4: Supported Devices Overview
Device
AP1100
Description
Connectivity
Notes
IP adapter to
HG 1500, B-channel license, user
For fax only. Uses G.711 codec
one fax
license
only.
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
10
Siemens HiPath 5000 Real-Time IP System
Table 4: Supported Devices Overview
Device
AP1140
Description
Connectivity
Notes
IP adapter to
HG 1500, B-channel license, user
For fax, voice and modem. Uses
four analog
license for each active port
G.711 codec only for fax and
devices
modem, but also recommended
for voice connections as voice
quality may be impacted when
using G.723 codec.
Dual-Tone
Standard
Subscriber-Line Module Analog
—
Multifrequency
analog DTMF
(SLMA) 16/24, or 8 SLAs (Analog
(DTMF) Phone
phone
Device Cards), or one port of
OptiPoint 400
IP phone
HG 1500
—
Digital phone
Subscriber-Line Module Optiset
The OP500 standard SL supports
(SLMO) 24 or 8 Serial Line Units
multiline appearances on the
(SLUs) in HiPath 3000
HiPath 3000
IP or TDM
TDM = SLMO 24 or 8SLU in
—
phone
H3000; IP = HG 1500
90-button BLF
Optiset E
—
Digital phone
SLMO 24 or 8SLU in HiPath 3000
—
Polycom IP
IP audio-
HG 1500, B-channel license, user
The Polycom Soundstation
Sound Station
conferencing
license
IP3000 has been tested with
AP1140
Standard,
Economy
OptiPoint 500
and adapters
OptiPoint 600
Optiset BLF
adjunct unit
Optiset E and
adapters
unit
HiPath 3000 v4.0.
Polycom
Analog audio-
SLMA 16 or 24, or 8 SLAs or one
When connected behind an
Sound Station
conferencing
port of AP1140
AP1140, the analog Polycom
unit
Sound Station only supports
basic call setup and breakdown.
Features such as consultation,
transfer and conferencing are not
supported.
PowerDsine
Power over
6006/12/24
LAN midspan
—
—
—
—
hubs
RedHawk 10,
Power over
20 Ports
LAN mid-span
hubs
Existing Siemens devices not supported on the HiPath 5000 Real-Time IP System include the following:
•
RG 2100 and RG 2500 gateways
•
OptiPoint 300 Basic and Advance IP phones
•
OptiClient 330, 350 and 360 soft clients (replaced by the OptiClient 130)
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
11
Siemens HiPath 5000 Real-Time IP System
The OptiPoint 400 Standard IP phone is supported on v4.0, but requires a software upgrade.
HiPath 5000 Real-Time IP System Supported Applications
Table 5: Supported Applications Overview
Device
CAP 1.0
Description
Connectivity
Notes
Applications
Included in SimplyPhone
Does not run with TAPI 170 v2.0
middleware
(requires own PC)
on one PC.
Deployment
Installation
Can be installed on Manager E
—
Tool
and service
Centralized
Part of the standard feature set in
Does not provide reports; gathers
Call Record for
5000 RSM
the call records in one centralized
tools for
updating
device
software
Get Account
multiple
db.
HiPath 3000
nodes
HiPath
CDR
Requires own server; RS-232 to
Accounting
collection devices or HG 1500 to
Management
LAN
—
(MTS
IntegraTRAK)
HiPath
Uniform call
HG 1500 and B-channel licenses.
Cannot be installed on the HiPath
ProCenter
distribution
Must be installed on a separate
5000 RSM server.
Compact
(UCD) group
server.
reporting
software for
single node
HiPath
Call center
Requires own server; (max. of 32
Plans are to have this software
ProCenter
software
agents across 16 nodes)
co-resident with the 5000 RSM
Inventory
Views the
Part of standard features in
Cannot view software levels of
Manager
software levels
H5000 RSM Manager E
other network devices, such as
Suite
software.
of network
H4000s.
devices (3000
nodes,
OptiPoint
400s/600s,
OptiClient
130s)
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
12
Siemens HiPath 5000 Real-Time IP System
Table 5: Supported Applications Overview
Device
Manager C
Description
Connectivity
Customer-
Installs on local PC (Windows
oriented
2000, NT, XP)
Notes
Is a subset of Manager E
configuration
management
tool for HiPath
3000
Manager E
Configuration
Technician’s tool; part of standard
Cannot be purchased separately;
management
features in H5000 RSM
requires a one-week class in
tool for HiPath
Irving, TX.
3000
Manager T
Native 3000
Part of HiPath 3000 software;
Has limited configuration
configuration
operates via OptiPoint 500 or
capabilities, for example, no
management
Optiset phone
Least Cost Routing (LCR)
tool
OptiClient 130
Softphone
Installs on local PC (Windows
Not the same software as on the
v4.0
client
2000, NT, XP)
HiPath 4000
OptiClient
Soft attendant
Requires that OptiClient 130 be
Downward compatible to HiPath
Attendant v6.0
client
installed on same PC; connects
3000 v3.0
via OptiPoint 500 Universal Serial
Bus (USB) or directly to LAN
OfficeLook 2.0
CDR reporting
Requires own server; connects
—
via RS-232
PCM
Manage call
Part of standard features in
forwarding
HiPath 5000 RSM
—
destinations
from PC on
the Web
PhoneMail
Voice
TDM connection only via
messaging
SLMA/SLA boards
Presence
Manages BLF
Part of standard features in
Manager
indicators
HiPath 5000 RSM
—
—
across nodes
in network of
HiPath 3000s.
SimplyPhone
Personal call
Connects via Microsoft Remote
Cannot reside on the HiPath
for Outlook 3.1
management
TSP, or Callbridge TA or TU
5000 RSM server; requires
software
separate user PC
SimplyPhone
Personal call
Connects via Microsoft Remote
Cannot reside on the HiPath
for Notes 3.1
management
TSP, or Callbridge TA or TU
5000 RSM server; requires
software
TAPI 120 v2
First-party
separate user PC
Local PC
License required per user
computer
telephony
integration
(CTI) software
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
13
Siemens HiPath 5000 Real-Time IP System
Table 5: Supported Applications Overview
Device
Description
TAPI 170 v2
Connectivity
Notes
Third-party
Can be installed on the HiPath
License required for each
CTI software
5000 RSM server
instance.
Telephony
Net access
Own separate server
—
Transformatio
software for
n Gateway
OptiPoint 600
phone
Xpressions
Unified
Connects via TDM interface
For multiple nodes, additional HG
v3.0
messaging for
boards to HiPath 3000; requires
1500 and B-channel licenses are
single or
own server
required. Currently does not
multiple nodes
Xpressions
Voice
Compact v1.0
messaging
support media streaming
Integrated board in HiPath 3000
—
only for single
node
Pricing
Table 6: HiPath 5000 Real-Time IP System List Pricing (US$)
HiPath 5000 RSM v4.0 Software
1,600
HiPath 3700/3750 System
3,000
HiPath 3700/3750 MMC With v4.0 Software
400
HiPath 3700/3750 TMST1 KIT (CD & Automatic Data
2,160
Processing [ADP])
HiPath HG 1500 v2 3700/3750 Voice/Data Package
2,500
HiPath HG 1500 Expansion - 2 Channels Voice/Data
660
Package
HiPath CMS
•
500
Siemens OptiPoint 400 Standard 3.0 Phone
440
Siemens Xpressions Compact 3700/3750 24P
4,000
Note: For the European market, the list prices above are the same based on the dollar-to-Euro
conversion.
GSA Pricing
Yes.
Competitors
•
Alcatel (OmniPCX 4400)
•
Avaya (Definity IP-Enabled, ECLIPS S8300, S8700 Media Servers)
•
Cisco Systems (Cisco AVVID CallManager)
•
Mitel Networks (Mitel 3300 Integrated Communications Platform)
•
NEC America (NEAX 2400 Internet Protocol eXchange)
•
Nortel Networks (Meridian 1 Option 61C, 81C IP-Enabled, Succession CSE 1000)
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
14
Siemens HiPath 5000 Real-Time IP System
Strengths
•
HiPath 5000 v4.0 is a survivable, distributed IP enterprise communication system that can support a
full array of traditional Siemens PBX features in either packet-switched or circuit-switched system
configurations. Its strength is in providing an IP-based solution for a large enterprise looking to
network multiple small locations.
•
HiPath 5000 v4.0 provides a single management platform for centralized administration of multiple
enterprise locations.
•
Minimizing administration work, a login concept defined for the HiPath 5000 RSM allows HiPath 3000
nodes that are added to the network to register independently with the 5000 RSM server.
•
HiPath 5000 RSM supports IP peripherals offered on the HiPath 4000 system including Optiset E
digital phones and adapters, OptiPoint 400 Standard and Economy IP phones, OptiPoint 500 digital
phones and adapters and OptiPoint 600 IP or digital phones.
•
A Lightweight Directory Access Protocol (LDAP) interface to a Microsoft Active Directory server is
supported.
•
Each individual HiPath 3000 node can program its own speed dial entries either locally or via the
Siemens Manager E management tool in a HiPath 5000 RSM configuration.
•
Common dialing plan functionality between HiPath 5000, Hicom 300 and HiPath 4000 systems is
supported.
Limitations
•
HiPath 5500 systems can be upgraded to HiPath 5000 v4.0, but only the existing desktop (phones,
softphones, applications) can be re-used. The migration for HiPath 5300 users is to the HiPath 3000
stand-alone system.
•
To implement HiPath 5000 v4.0, you have to also buy a HiPath 3000 SMG or have existing
investment in one (or more).
•
Only the HiPath 5000 RSM application, plus a virus checker (mandatory) and HiPath Fault
Management may be installed on the server running the 5000 RSM Base Package (Hardware +
Software + License).
•
Siemens AllServe Messaging is not supported on the HiPath 5000 RSM server.
•
Q-Signaling (QSIG) support is not standard. HiPath 5000 RSM v4.0 interoperability with third-party
systems via QSIG requires development support from Siemens.
Recommended Gartner Research
•
Key/Hybrid, PBX and IP-PBX Systems: Comparison Columns, DPRO-89876
•
Siemens HiPath 4000, DPRO-89828)
•
Siemens HiPath 3000, DPRO-90153)
Insight
Although touted by Siemens as an enterprise softswitch platform now, keep in mind that the HiPath 5000
Real-Time IP System does require operation in conjunction with a hardware switch, the Siemens HiPath
3000 SMG.
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
15
Siemens HiPath 5000 Real-Time IP System
A future release of HiPath system software called HiPath ComScendo IP communications software is
expected to provide support across Siemens Real-Time IP systems (HiPath 3000 SMG, HiPath 5000,
HiPath 4000). The user interface, system features and networking functionality will be the same for some,
but not all of these platforms. However, in most standard configurations, this should not limit user
capabilities at remote sites and feature transparency across the network.
Siemens recently announced its system-in-a-package (SIP)-based, OpenScape v.1.0 communications
software for presence-based conferencing and multimedia collaboration tools on Microsoft Windows
Server 2003 and Windows Messenger. Other enterprise communications applications reportedly
supported by OpenScape will include mobility, personal productivity tools and unified messaging.
Siemens indicates that these applications, when combined with OpenScape, will provide the tools for a
unified communications offering. HiPath MobileOffice provides Siemens mobility applications for HiPath
environments; OpenScape is expected to provide mobility, conferencing and collaboration on an open
platform for IT environments.
© 2003 Gartner, Inc. and/or its Affiliates. All Rights Reserved.
DPRO-115916
27 June 2003
16