HiPath 3000 5000 V8 System Description

8/15/2019 HiPath 3000 5000 V8 System Description

http://slidepdf.com/reader/full/hipath-3000-5000-v8-system-description 1/485

Communication for the open minded

Siemens Enterprise Communicationswww.siemens-enterprise.com

Documentation

HiPath 3000/5000IP Systems

System Description

A31003-H3580-Y100-10-7618





3000sbTOC.fm

A31003-H3580-Y100-10-7618, 01-2011

HiPath 3000/5000 V8, System Description 0-1

Nur für den internen Gebrauch Table of Contents

Table of Contents 0

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Overview of HiPath 3000/5000 V8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.3 Key Features in Version 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.4 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.4.1 Automatic, Time-Dependent Class-of-Service (COS) Changeover . . . . . . . . . . . 1-51.4.2 Caller-Specific Ringer Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61.4.3 Whisper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71.4.4 Privacy Release Key (MULAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81.4.5 Protocol Extensions for Contact Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

1.4.6 CSTA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91.4.7 OpenScape Office HX – Integrated Applications . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.4.7.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.4.7.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-141.4.7.3 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-161.4.7.4 Simultaneous UCD Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

1.4.8 IP Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-191.4.8.1 Teleworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-191.4.8.2 Desk Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

1.4.9 IP Mobility Enhancement (Emergency Number) . . . . . . . . . . . . . . . . . . . . . . . . . 1-201.4.10 Internet Telephony – ITSP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

1.4.10.1 Features of Internet Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-211.4.10.2 Released ITSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-211.4.10.3 Supported ITSP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-211.4.10.4 Features Supported by HiPath 3000/5000 V8 for Connecting to ITSPs. . . 1-211.4.10.5 ITSP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-231.4.10.6 Network Address Translation (NAT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

1.4.11 Telephones for Internet Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-271.4.11.1 Internet Telephony Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-271.4.11.2 DSL Terminal Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

1.4.12 Signaling and Payload Encryption (SPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

1.4.13 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-321.5 Application and Networking Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-341.5.1 HiPath 3000 Standalone (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-351.5.2 HiPath 3000 Standalone (TDM and IP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-351.5.3 HiPath 3000 Networked With HiPath 5000 via IP . . . . . . . . . . . . . . . . . . . . . . . . 1-361.5.4 HiPath 3000 Networked Over IP with HiPath 5000 (With VPN) . . . . . . . . . . . . . 1-371.5.5 HiPath 3000 Networked With HiPath 2000, HiPath 4000 and HiPath 5000 . . . . 1-381.5.6 HiPath 3000 as a Branch on HiPath 4000 (Small Remote Site) . . . . . . . . . . . . . 1-391.5.7 Virtual Private Networks (Site-to-Site VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41



Table of Contents Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011

0-2 HiPath 3000/5000 V8, System Description

3000sbTOC.fm

1.5.8 IP Networking of Two HiPath 3000 Systems that Support Signaling and PayloadEncryption (SPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42

1.5.9 Networking of HiPath 3000 with OpenScape Voice via SIP-Q V2 . . . . . . . . . . . . 1-441.6 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46

1.6.1 HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-461.6.1.1 Standalone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46

1.6.2 HiPath 33x0 and 35X0 With EVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-461.6.3 HG 1500 V3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-471.6.4 Peripheral Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-481.6.5 OpenScape Personal Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-481.6.6 optiPoint 400/410/420/600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-481.6.7 optiClient Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-481.6.8 CMI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-491.6.9 Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49

1.6.10 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-501.7 Sales-Oriented Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-511.8 Technical Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-521.9 Privacy and Data Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-531.10 Feedback/Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-541.11 Copyright. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54

2 System Overview HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 System-Related Capacity Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.2 HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.1 Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.1.1 Board Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.2.2 Distribution of PCM Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92.2.3 Static Traffic Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132.2.4 Central Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

2.2.4.1 CBSAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.2.4.2 LUNA2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-152.2.4.3 LIMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192.2.4.4 CSAPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

2.2.5 Peripheral Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.2.5.1 Subscriber Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.2.5.2 Trunk Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

2.2.5.3 Boards for Tie Trunk Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.2.5.4 Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

2.2.6 Additional System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-262.2.6.1 Energy Consumption Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-262.2.6.2 Specifications for the Uninterruptible Power Supply LUNA2 . . . . . . . . . . . . . 2-26

2.3 HiPath 3550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-272.3.1 Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-272.3.2 Static Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-292.3.3 Central Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

2.3.3.1 CBCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30



3000sbTOC.fm

A31003-H3580-Y100-10-7618, 01-2011



2.3.3.2 UPSC-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-322.3.3.3 LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

2.3.4 Peripheral Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-352.3.4.1 Subscriber Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

2.3.4.2 Trunk Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-362.3.4.3 Boards for Tie Trunk Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-372.3.4.4 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

2.3.5 Additional System Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-392.3.5.1 Heat Dissipation and Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . 2-392.3.5.2 Specifications for the Uninterruptible Power Supply. . . . . . . . . . . . . . . . . . . 2-39

2.4 HiPath 3350 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-402.4.1 Hardware Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-402.4.2 Static Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-412.4.3 Central Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

2.4.3.1 CBCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-422.4.3.2 PSUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-442.4.3.3 UPSC-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-442.4.3.4 LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45

2.4.4 Peripheral Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-462.4.4.1 Subscriber Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-462.4.4.2 Trunk Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-472.4.4.3 Boards for Tie Trunk Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-482.4.4.4 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48

2.4.5 Additional System Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-502.4.5.1 Heat Dissipation and Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

2.4.5.2 Specifications for the Uninterruptible Power Supply. . . . . . . . . . . . . . . . . . . 2-502.5 HiPath 3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51

2.5.1 Hardware Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-512.5.2 Static Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-522.5.3 Central Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53

2.5.3.1 CBRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-532.5.3.2 TUPSC-DR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-552.5.3.3 LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

2.5.4 Peripheral Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-582.5.4.1 Subscriber Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-582.5.4.2 Trunk Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-592.5.4.3 Boards for Tie Trunk Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-602.5.4.4 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

2.5.5 Additional System Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-612.5.5.1 Heat Dissipation and Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . 2-612.5.5.2 Specifications for the Uninterruptible Power Supply. . . . . . . . . . . . . . . . . . . 2-61

2.6 HiPath 3300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-622.6.1 Hardware Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-622.6.2 Static Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-632.6.3 Central Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64




A31003-H3580-Y100-10-7618, 01-2011


3000sbTOC.fm

2.6.3.1 CBRC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-642.6.3.2 UPSC-DR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-662.6.3.3 LIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67

2.6.4 Peripheral Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-682.6.4.1 Subscriber Line Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-682.6.4.2 Trunk Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-692.6.4.3 Boards for Tie Trunk Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-692.6.4.4 Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70

2.6.5 Additional System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-702.6.5.1 Heat Dissipation and Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . 2-702.6.5.2 Specifications for the Uninterruptible Power Supply . . . . . . . . . . . . . . . . . . . 2-70

2.7 Additional Power Supply by the Powerbox PB3000 . . . . . . . . . . . . . . . . . . . . . . . . . . 2-712.8 Recommendations for CMA and CMS Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-732.9 HiPath Cordless Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77

2.9.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-772.9.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-782.9.3 Multi-SLC and Cross-System Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-792.9.4 Notes on the Planning of Networked HiPath 3000 Systems

With the Network-Wide Roaming Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-812.9.5 Components of HiPath Cordless Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83

2.9.5.1 Mobile Telephones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-832.9.5.2 Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83

2.10 Technical Specifications HiPath 3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-852.11 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-862.12 Interface-to-Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88

2.13 Numbering Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-892.13.1 Default Numbers for HiPath 3000/5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-892.13.2 ISDN Numbering Plan (E.164) V7 or Later. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90

2.14 Technical Specifications and Compliance to HiPath 3000 . . . . . . . . . . . . . . . . . . . . 2-922.14.1 CE Compliance (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-922.14.2 Compliance with US and Canadian Standards (For U.S. and Canada Only). . . 2-922.14.3 SAFETY International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92

2.15 Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-932.15.1 Electrical Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-932.15.2 Mechanical Operating Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93

3 HiPath 5000 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2 Software Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.3 HiPath 5000 Server PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.4 Server Networking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.4.1 Features of IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.4.2 IP Network and Application Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.4.2.1 Adequate Connection Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.4.2.2 Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.4.2.3 Requirements of Delay Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11



3000sbTOC.fm

A31003-H3580-Y100-10-7618, 01-2011



3.4.2.4 Provision of QoS in Data Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113.4.2.5 Quality Assurance Procedures to be Supported. . . . . . . . . . . . . . . . . . . . . . 3-123.4.2.6 Maximum Package Losses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.4.2.7 Minimization of Broadcast/Multicast Traffic . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.4.2.8 Requirements for Standalone Systems: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.4.2.9 Adaptation of QoS Classes to Oscar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

4 HiPath 3000/5000 in the LAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Network Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.1 Network Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.1.1 H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.1.2 SIP / SIP-Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.1.3 CorNet IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4.2 QoS - Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.2.1 Goals of QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

4.2.2 QoS in the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.3 HiPath’s Network Analysis Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.4 LIM Board for LAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.5 HG 1500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

4.5.1 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.5.1.1 Protocols Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

4.5.2 Security/Firewall/Packet Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.5.3 IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.5.4 Voice over IP (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

4.5.4.1 General Parameters for Voice over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.5.4.2 Voice Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.5.4.3 DTMF Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.5.4.4 Voice Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.5.4.5 Environmental Requirements for VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

4.5.5 Fax over IP with HG 1500 V3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.5.6 Fax over vCAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-334.5.7 Modem via IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-344.5.8 HiPath Feature Access (HFA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-344.5.9 Internet Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35

4.5.9.1 PPP, PPPoE and PPTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-364.5.9.2 Network Address Translation (NAT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37

4.5.9.3 Access Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-374.5.9.4 Multilink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-384.5.9.5 Short-Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-384.5.9.6 IP Control Protocol (IPCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-384.5.9.7 Compression of IP Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-384.5.9.8 Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-394.5.9.9 IP Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-394.5.9.10 vCAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40

4.5.10 Virtual Private Network (VPN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41




A31003-H3580-Y100-10-7618, 01-2011


3000sbTOC.fm

4.5.10.1 Secure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-424.5.10.2 Security Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-434.5.10.3 Security Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-444.5.10.4 Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-444.5.10.5 Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

4.5.11 System Client and H.323 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-464.5.11.1 Bandwidth Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46

4.5.12 Displaying, Adding and Configuring PKI Servers . . . . . . . . . . . . . . . . . . . . . . . . 4-464.5.12.1 Telematics Using the vCAPI Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-474.5.12.2 vCAPI and Smartset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-474.5.12.3 vCAPI and TAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-484.5.12.4 vCAPI and Fax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-494.5.12.5 vCAPI and File Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-504.5.12.6 vCAPI and Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50

4.5.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-514.5.14 Call Charge Allocation and Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-524.5.15 Internet Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53

4.5.15.1 HG 1500 V3.0 and Access to the Internet via a Network Provider . . . . . . . 4-544.5.15.2 Internet Access via T-DSL (T-ISDN DSL) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-544.5.15.3 IP Address Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55

4.5.16 Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-564.5.16.1 Safety Mechanisms ("Security"). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-564.5.16.2 Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-574.5.16.3 Alive Monitoring with Keep Alive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-584.5.16.4 Monitoring IP Data Packages with rpcap and Wireshark (Ethereal) . . . . . . 4-58

4.5.17 Overview of Management Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-594.5.17.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-594.5.17.2 Multi-Gateway Administration (MGA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

4.5.18 Quality of Service in HG 1500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-604.6 IP Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64

4.6.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-644.6.2 Features of IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-654.6.3 Network-Wide Features with IP Networking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-684.6.4 Special Features of Windows Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70

4.6.4.1 Routing and Name Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-704.7 IP Payload Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-714.8 Applications over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73

4.8.1 Call Detail Recording Central (CDRC) via IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-734.8.1.1 TFTP Client in HiPath 3000/5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-734.8.1.2 TCP Client in HiPath 3000/5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-744.8.1.3 TFTP Server in HiPath 3000/5000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74

4.8.2 CSTA via IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-754.9 Administration & Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76



3000sbTOC.fm

A31003-H3580-Y100-10-7618, 01-2011



4.9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-764.9.2 SNMP Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77

4.9.2.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-774.9.2.2 Overview of SNMP Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77

4.9.2.3 Using SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-794.9.3 Administering HiPath 3000/5000 via the LAN Interface . . . . . . . . . . . . . . . . . . . 4-84

4.10 Networking Scenarios in the LAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-854.10.1 Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-864.10.2 Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-874.10.3 Scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-884.10.4 Scenario 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-894.10.5 Scenario 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-914.10.6 Scenario 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-924.10.7 Scenario 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93

5 System Administration and Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.2 System Administration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

5.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.2.2 Administration On Site with System Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.2.3 Administration On Site with Service PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.2.4 Remote Administration of HiPath 3000/5000 via PPP . . . . . . . . . . . . . . . . . . . . . 5-65.2.5 Remote Administration of Plus Products via PPP. . . . . . . . . . . . . . . . . . . . . . . . . 5-8

5.3 Options in the Service Department . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125.3.1 Customer Database Backup (CDB Backup) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

5.3.1.1 Customer Data Backup Without HiPath 3000/5000 Software Manager . . . . 5-125.3.1.1.1 Automatic Customer Data Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125.3.1.1.2 Manual Customer Data Backup with HiPath 3000. . . . . . . . . . . . . . . . . 5-13

5.3.1.2 Customer Data Backup with HiPath 3000/5000 Software Manager . . . . . . 5-135.3.2 Relocate/Transfer Application Processor Software (APS) . . . . . . . . . . . . . . . . . 5-14

5.3.2.1 APS Replacement/Transfer for HiPath 3000 Systems Without HiPath 3000/5000Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

5.3.2.1.1 Transferring an APS of HiPath 3000 by Replacing the MMC . . . . . . . . 5-145.3.2.1.2 APS Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

5.3.2.2 APS Transfer for HiPath 3000 Systems WithHiPath 3000/5000 Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

5.3.3 Determining System Information and Installed Software Components (HiPathInventory Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

5.3.4 Backing Up System Components (Backup Manager) . . . . . . . . . . . . . . . . . . . . 5-175.3.5 Diagnostics Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

5.3.5.1 Recording HiPath 3000 Board Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.3.5.1.1 Central Control Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.3.5.1.2 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195.3.5.1.3 Peripheral Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

5.3.5.2 Recording HiPath 3000 Trunk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-215.3.5.3 Recording Station Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22




A31003-H3580-Y100-10-7618, 01-2011


3000sbTOC.fm

5.3.5.4 Recording the Status of the HiPath 3000 V.24 Interfaces . . . . . . . . . . . . . . . 5-235.3.5.5 Trace Options for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-245.3.5.6 HiPath Manager PCM Trace Monitor for HiPath 5000. . . . . . . . . . . . . . . . . . 5-255.3.5.7 Eventlog for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-265.3.5.8 Testing Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-265.3.5.9 Event Viewer for HiPath 5000 (Eventlog) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-275.3.5.10 HiPath Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-285.3.5.11 Licensing Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29

5.3.5.11.1 Analysis Using Customer License Manager (CLM). . . . . . . . . . . . . . . . 5-295.3.5.11.2 Analysis Using Customer License Agent (CLA) . . . . . . . . . . . . . . . . . . 5-29

5.3.5.12 Analysis Using HiPath 3000/5000 Software Manager andHiPath Inventory Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

5.3.6 HiPath 3000 Error Messages (Entries in the Eventlog for HiPath 3000) . . . . . . . 5-315.3.7 HiPath 5000 Error Messages (Event Viewer Entries for HiPath 5000) . . . . . . . . 5-31

5.3.8 Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-325.3.8.1 Automatic Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-325.3.8.2 Manual Error Correction Without HiPath 3000/5000 Manager E. . . . . . . . . . 5-325.3.8.3 Manual Error Correction With HiPath 3000/5000 Manager E . . . . . . . . . . . . 5-33

5.3.9 Remote Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-345.3.9.1 HiPath 3000 Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-355.3.9.2 HiPath 5000 Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-365.3.9.3 Remote System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-365.3.9.4 Remote Correction of System Software (APS) . . . . . . . . . . . . . . . . . . . . . . . 5-375.3.9.5 Remote Error Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-375.3.9.6 Remote Administration and Access Using PPP. . . . . . . . . . . . . . . . . . . . . . . 5-37

5.3.10 Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-395.3.10.1 Logon With User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-395.3.10.2 Pre-determined User Groups and Their Access Rights. . . . . . . . . . . . . . . . 5-415.3.10.3 System Access Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-435.3.10.4 Customer Data Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

5.3.11 Automatic Logging of Administration Procedures. . . . . . . . . . . . . . . . . . . . . . . . 5-455.3.11.1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

5.3.11.1.1 Format Identification and Command Entry . . . . . . . . . . . . . . . . . . . . . . 5-455.3.11.2 Issuing and Saving Log Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48

6 Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 HiPath TAPI 120/170 V2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.1 Configurations and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.2 1st Party Function (Direct Connection). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.1.3 3rd Party Function (Connection Via Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.4 CSTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.5 Functional Framework Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.1.6 Software and Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.1.7 Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66.1.8 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76.1.9 System Connection Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8



3000sbTOC.fm

A31003-H3580-Y100-10-7618, 01-2011



6.1.10 Installation Medium and Order of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2 CSPL Interface for Gadget Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.3 G server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

7 Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.1 HiPath AP 1120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.2 HiPath AP 1120 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

8 Workpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18.1 OpenStage Product Family (HiPath 3000/5000 V7 R3 and Higher) . . . . . . . . . . . . . . 8-3

8.1.1 Gigabit Variant of OpenStage Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.1.2 OpenStage Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

8.1.2.1 OpenStage 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.1.2.2 OpenStage 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.1.2.3 OpenStage 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

8.1.2.4 OpenStage 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.1.2.5 OpenStage 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.1.2.6 OpenStage 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.1.2.7 OpenStage 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-188.1.2.8 Ports on the Underside of the Telephone for the CorNet IP Model . . . . . . . 8-218.1.2.9 Ports on the Underside of the Telephone for the TDM Model . . . . . . . . . . . 8-238.1.2.10 OpenStage Terminals – Description of Ports . . . . . . . . . . . . . . . . . . . . . . . 8-25

8.1.3 Add-on Devices for OpenStage Telephones. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-278.1.3.1 OpenStage Key Module 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-278.1.3.2 OpenStage Key Module 40, 60, 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-288.1.3.3 OpenStage BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28

8.1.3.4 Possible Configurations for the Add-On Devices . . . . . . . . . . . . . . . . . . . . . 8-298.1.4 OpenStage Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

8.1.4.1 External Local Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-308.1.4.2 OpenStage PhoneAdapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-328.1.4.3 Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33

8.2 OpenScape Personal Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-348.3 optiPoint 410 and optiPoint 420 Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36

8.3.1 optiPoint 410 and optiPoint 410 S Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . 8-398.3.1.1 optiPoint 410 entry, optiPoint 410 entry S . . . . . . . . . . . . . . . . . . . . . . . . . . 8-398.3.1.2 optiPoint 410 economy, optiPoint 410 economy S . . . . . . . . . . . . . . . . . . . 8-418.3.1.3 optiPoint 410 economy plus, optiPoint 410 economy plus S . . . . . . . . . . . . 8-438.3.1.4 optiPoint 410 standard, optiPoint 410 standard S . . . . . . . . . . . . . . . . . . . . 8-458.3.1.5 optiPoint 410 advance, optiPoint 410 advance S . . . . . . . . . . . . . . . . . . . . 8-47

8.3.2 optiPoint 420 and optiPoint 420 S Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . 8-498.3.2.1 optiPoint 420 economy, optiPoint 420 economy S . . . . . . . . . . . . . . . . . . . 8-498.3.2.2 optiPoint 420 economy plus, optiPoint 420 economy plus S . . . . . . . . . . . . 8-518.3.2.3 optiPoint 420 standard, optiPoint 420 standard S . . . . . . . . . . . . . . . . . . . . 8-538.3.2.4 optiPoint 420 advance, optiPoint 420 advance S . . . . . . . . . . . . . . . . . . . . 8-55

8.3.3 optiPoint 410 and optiPoint 420 Add-On Devices . . . . . . . . . . . . . . . . . . . . . . . . 8-57




A31003-H3580-Y100-10-7618, 01-2011


3000sbTOC.fm

8.3.3.1 optiPoint self labeling key module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-588.3.3.2 optiPoint 410 display module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-598.3.3.3 Possible Configurations for the Add-On Devices . . . . . . . . . . . . . . . . . . . . . 8-60

8.4 optiPoint 600 office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-618.5 optiPoint 500 Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63

8.5.1 optiPoint 500 Telephones without Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-648.5.2 optiPoint 500 Telephones with Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-658.5.3 Comparison of Features on All optiPoint 500 Telephones . . . . . . . . . . . . . . . . . . 8-688.5.4 optiPoint 500 Add-On Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-69

8.5.4.1 optiPoint key module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-698.5.4.2 optiPoint BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-708.5.4.3 optiPoint application module (V5.0 SMR-06 or later) . . . . . . . . . . . . . . . . . . 8-708.5.4.4 Possible Configurations for the Add-On Devices . . . . . . . . . . . . . . . . . . . . . 8-71

8.5.5 optiPoint 500 Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-72

8.5.6 Restrictions for Using optiPoint Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-778.6 Accessories for optiPoint Telephone Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-788.6.1 Local Power Supply for optiPoint 500 and optiPoint 600 office . . . . . . . . . . . . . . 8-788.6.2 optiPoint 410 and optiPoint 420 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . 8-788.6.3 Headsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-798.6.4 Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-81

8.7 optiPoint 600 office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-838.7.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-838.7.2 optiPoint 600 office as System Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-848.7.3 Advantages at a Glance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-84

8.7.3.1 General Local Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-85

8.7.3.2 Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-868.8 optiPoint WL2 professional/optiPoint WL2 professional S . . . . . . . . . . . . . . . . . . . . . 8-878.9 Mobile Telephones for HiPath Cordless Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-93

8.9.1 Gigaset SL3 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-938.9.2 Gigaset S4 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-948.9.3 Gigaset M2 professional. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-95

8.10 Attendant Consoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-978.10.1 HiPath Attendant B Braille Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-978.10.2 optiClient Attendant V8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98

8.10.2.1 optiClient Attendant as a Central Attendant Console. . . . . . . . . . . . . . . . . 8-1038.10.2.2 optiClient BLF V1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-104

8.10.3 optiPoint Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-106

9 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.2 List of Certified Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

10 Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-110.1 Capacities of HiPath Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-110.2 Overview of Additional Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11



3000sbTOC.fm

A31003-H3580-Y100-10-7618, 01-2011



11 Output Formats for Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

A Identifying System Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1A.1 HiPath 3800 Boards Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

A.2 HiPath 3550 Boards Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4A.3 HiPath 3350 Boards Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6A.4 HiPath 3500 Boards Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8A.5 HiPath 3300 Boards Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10A.6 Workpoint Clients, Key Modules and Adapter Power Requirements . . . . . . . . . . . . A-11A.7 Check Whether the Output of a Power Supply Unit is Sufficient. . . . . . . . . . . . . . . . A-14A.8 Identifying the Primary System Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1




A31003-H3580-Y100-10-7618, 01-2011


3000sbTOC.fm



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Introduction

About This Manual

1 Introduction

HiPath 3000/5000 V8, A31003-H3580-Y100-10-7618

1.1 About This Manual

This manual describes the features and hardware of HiPath 3000/5000, which consists of thefollowing systems:

● HiPath 3000

– HiPath 3350/3300

– HiPath 3550/3500

– HiPath 3800

● HiPath 5000

>Country-specific features and released applications may vary.The Sales Information is therefore the only document that contains a binding de-scription of the available features and the hardware scope for your country.



Introduction Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Overview of HiPath 3000/5000 V8

1.2 Overview of HiPath 3000/5000 V8

The systems included in V8 can be used in the following scenarios:

● HiPath 3000,whose communication systems can be used as standalone systems or as networked sys-tems. Central administration of networks consisting of HiPath 3000 systems is not possible.

● HiPath 5000,is used as a central administration unit in the IP network of HiPath 3000 systems (= multi-node system, see figure 1-2). By creating a "Single System Image", all relevant nodes canbe centrally administered. HiPath 5000 is the platform for the central provision of applica-tions, and facilitates the use of these applications by all IP networking stations.

Figure 1-1 HiPath 3000 as Networked Systems

optiPoint4xx ...OpenScape

Personal Edition HiPath 3000

optiClient

Attendant

HiPath 3000

PSTN

IP Network

HiPath 3000

HiPath CordlessOffice

optiPoint 500 ...OpenStage TDM

optiPoint 600

office (UP0/E)

HiPath 3000

OpenStage

CorNet-IP (HFA)






A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Key Features in Version 8

1.3 Key Features in Version 8

OpenScape Office Unified Communications

● myPortal: User portal for access to Unified Communications functions

● myPortal for Outlook: User portal integrated in Microsoft Outlook for access toUnified Communications functions.

● myPortal web: User portal for mobile access to Unified Communications functions.

● OpenScape Office Fax Printer: Application for sending fax messages from Windows appli-cations such as Microsoft Word with individually customized cover pages.

OpenScape Office Contact Center

● myAgent: Convenient application for call distribution and call processing by OpenScapeOffice Contact Center agents.

● myReports: Application for generating reports on calls, queues, agents, performance, ser-vice level and rework codes by OpenScape Office Contact Center agents.

Enhancements for using stationary and mobile telephones

● Support for dual-mode mobile phones:

– GSM and WLAN-SIP

– SIP standard features

– Roaming

● Xpressions Compact Mobility: Simultaneous call signaling at the stationary and mobilephone

● Mobility Entry: Number of mobile users increased to 100

Feature improvements

● User interface:

– Redial list increased to 10 entries

– Improved user interface for OpenStage 40

– For Gigaset telephones (CMI): Missed calls list and message waiting indication display

● SIP extensions:

– Supports video-enabled SIP end points (OpenStage Personal Edition [SIP])

– Call forwarding

– Message waiting indication



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4 Features

1.4.1 Automatic, Time-Dependent Class-of-Service (COS) Changeover

In the past, class-of-service changeover was only capable of distinguishing between day ser-vice and night answer. This type of changeover applied to all stations

The new automatic class-of-service changeover feature combines stations in so-called profiles(for example, Management, Sales). A schedule can be configured for each profile to definewhich COS should be used for which time period in the week.

Relationship between automatic COS and automatic night answer

The COS feature is related to the automatic/manual day service/night answer. The following re-strictions apply:

● Reaching the call destination via Call ManagementThis takes place via Call Management and does not depend on automatic class-of-servicechangeover. There are different call lists for day and night.

● Intercept destinationsThe intercept destination is only defined by the automatic/manual day service/night an-swer.

● COS group:During the night, the COS group is in a fixed (configured) relationship with the station (au-tomatic class-of-service changeover has no impact on this).During the day, the COS group can either change between day times (if "Automatic COS"is set for the entire system) or be in a fixed (configured) relationship with the station (if "Au-tomatic COS" is not set).

Figure 1-3 Sample Schedule




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

1.4.2 Caller-Specific Ringer Signaling

Different types of caller-specific ringing signals are available in V6.0 or later.

In addition to external ringer signaling, internal ringer signaling can then be configured for everystation. Every internal call set up by this station (calling station) is signaled by a specific ringtype at station B (called station). The ring frequency at the destination is based on the caller’sring frequency. A station is assigned a specific ring frequency for this with Manager E. As in theexisting field for external calls ("ringer signaling"), the new ring frequencies for the internal ringfrequency are controlled via Manager E (not via Manager C).

The various ring frequencies are implemented at the station called if this is a HFA station(Up0/E or IP). Analog stations are always called with frequency 1.

CMI handsets

Only handsets with ringer melodies are supported. The calling number ID is sent to the Gigasetso that the melody selection function in the internal phonebook (VIP) is supported; this dependson whether this feature is supported by the relevant caller.

The various internal ring frequencies only operate between endpoints that are registered in thesame system or node.

Seven additional ring frequencies are added to the existing ring frequency. These frequencieshave different default values and every station is displayed by default with frequency 1.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.3 Whisper

The "Whisper" feature allows a station (station C in the diagram) to monitor an ongoing con-nection between two stations (stations A and B in the diagram) and to communicate with one

of these two stations. In other words, the connection is set up in such a way that station C canonly be heard by station A and station B can only hear station A.

Station C activates this feature by dialing a code. The telephone features a part-programmedkey (only the code is programmed on the key, the station number must be suffix-dialed). TheService menu features a new menu item for this. The Idle/Call menu, on the other hand, hasnot been changed.

The "Whisper" feature is designed for use in call centers or executive/secretary systems, forexample, and enables the user to communicate with one party (A) without the knowledge of theother party (B).

>Although there is no connection between station B and station C, station B may beable to overhear what station C says as a result of feedback from station A’s tele-phone.

>The option for activating the feature is linked to a new user-specific class of service.Station A can block the Whisper feature with a second class of service.

Station C:speaks to Ahears A and B

Station A:speaks to B (and C)hears B and C

Station B:speaks to Ahears A




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

Restrictions

● If neither of the participants in the original call (station A or B) is a TDM station, the HiPathswitching network is not involved at the time of activation and changeover is impossible

without briefly interrupting the connection between A and B.

● Stations A and C must be in the same node.

● Station C can only activate this feature in idle/standby status.

● Destination terminals for the Whisper feature (station A) can only be terminals with displayscontrolled by the system (optiPoint, OpenStage, OpenScape Personal Edition).As in HiPath 4000, CMI is not supported.

1.4.4 Privacy Release Key (MULAP)

Version 6.0 and later incorporates a new status called "Privacy Release". A new key was cre-ated in the database for this. This key is supported by the following workpoint clients:

● optiPoint 500

● optiPoint 600 (TDM only)

● OpenScape Personal Edition

● OpenStage TDM

The Privacy Release (MULAP) feature lets you release a busy MULAP line for a conferenceduring a call simply by pressing the "Privacy Release MULAP" button. This is indicated by aflashing light on the stations of other MULAP members who can then join the call by pressingthe flashing MULAP button. This creates a conference which is signaled by tones and displaymessages.

All members of a MULAP group can program a Privacy Release button on their stations. ThePrivacy Release feature also works when a subscriber is participating in a conference, even ifthe subscriber in question initiated the conference.

The Privacy Release button can be configured via Manager E.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.5 Protocol Extensions for Contact Center

You can use a "multiple pilot station number" to access the same UCD group with different sta-tion numbers. This function is implemented by configuring a virtual station in Call Management.

The "multiple pilot station number" is treated like a "call forwarding" number. Information aboutthe "multiple pilot station number" is "delivered" by the last call forwarding destination and"queued" in the relevant UCD group.

1.4.6 CSTA Interface

Addressing the CSTA application

The station can address the associated CSTA application (if this was previously registered atthe HiPath system) by selecting an application ID. A registered application can address a sta-tion directly (for example, to confirm an action on the display).

I/O sessions

You can start an I/O session with a feature code or function key. You can use the function tostart, resume, and stop an I/O session; the function key LED indicates the status of the I/O ses-sion (standby, active, suspended).

During an I/O session, a subscriber can operate the application using the following navigationkeys:

●

the keypad● plus/minus keys

● the alphanumeric keyboard

● the programmable keys and softkeys (CMI)

A single I/O session can only be used by one station at a time. If a session is interrupted ("sus-pended" status), a second I/O session cannot be started; the interrupted session must first beended.

Internet Telephony Service Provider (ITSP)

ITSP trunks can be integrated in CSTA applications connected to the HiPath system via theCSTA interface. This means that for CSTAs, there are no longer any differences between TDMtrunks and ITSP trunks.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

Connectable CSTA applications

On HiPath 3000, up to 8 CSTA connections are available. A maximum of 4 of these can be usedfor connecting server-based applications or for connection via CMD (only 1 on HiPath 33x0/

35x0 and up to 4 on HiPath 3800). Other non-server-based applications can be connected atthe remaining unused CSTA connections e.g. CTI applications via TAPI 120.

Connection is via HG 1500 or the LIM board, where the board is selected based on the BHCAvalue. The LIM board supports 400 BHCA and is thus not suitable for server-based connec-tions. HG 1500 supports BHCA values of 1200 and higher (dependent on the HiPath 3000 sys-tem type).

Resource monitoring

Each resource monitored via CSTA can be monitored simultaneously up to four times. Exam-

ple: A station is monitored simultaneously by four applications via CSTA.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.7 OpenScape Office HX – Integrated Applications

1.4.7.1 Overview

OpenScape Office HX includes the Unified Communications applications myPortal, myPortalfor Outlook, myPortal web and myAttendant as well as the OpenScape Office Contact Centerwith the applications myAgent and myReports. The administrator can use the web-based ad-ministrator program OpenScape Office Assistant to manage OpenScape Office HX.

Features of the applications

The OpenScape Office HX applications offer the following features. A detailed description ofthese features is provided in the OpenScape Office HX feature description.

● myPortal

myPortal is the user portal for accessing Unified Communication functions. In addition toconvenient dialing aids via directories and favorites as well as information regarding thepresence status of other stations, the station can also access voice and fax messages forexample.

myPortal offers the following features:

– Directories

– List of favorites

– Call journal

– Pop-up windows

– Presence status

– CallMe service

– Status-based call forwarding

– Personal AutoAttendant

– Conference management

– Recording of calls and conferences – Instant messaging

– Voice and fax messaging

The range of functions available for use depends on the licenses used. The fax display isonly possible on Windows operating systems.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

● myPortal for Outlook

myPortal for Outlook is the user portal integrated in Microsoft Outlook for accessing theUnified Communication functions of OpenScape Office HX, similar to myPortal.

myPortal for Outlook offers the following features in addition to myPortal:

– Desktop dialing

– Automatic invitation of conference participants via email and Outlook appointments

The range of functions available for use depends on the licenses used. The fax display isonly possible on Windows operating systems.

● myAttendant

myAttendant is a Unified Communications application for attendant functions. In additionto convenient attendant functions, dialing aids via directories and information on the pres-ence status of stations, it is also possible to access voice and fax messages, for example.Instant Messaging supports communication with internal stations.

myAttendant offers the following features:

– Attendant functions

– Directories

– Journal

– Pop-up windows

– Presence status

– Recording of calls

– Messaging center


– Instant messaging

– Team functions

● OpenScape Office Fax Printer

OpenScape Office Fax Printer is an application for sending fax messages from Windowsapplications such as Microsoft Word with individually customized cover pages.

OpenScape Office Fax Printer comprises the following components:

– OpenScape Office Cover Page Editor

– OpenScape Office Fax Printer Driver



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

Fax operation is established via the T.38 gateway of the HG1500. Up to three simultaneousfax connections can be established using the STMI2 board. Up to two simultaneous faxconnections can be established using the HXGS3/HXGR3 board.

● myAgentmyAgent is a convenient application for call distribution and call processing by OpenScapeOffice Contact Center agents.

myAgent offers the following features:

– Call processing

– Agent callback

– Agent status

– Presence status – Real-time queue monitoring

– Call recording if this is activated in the communication system

– Call monitoring

– Call override


– Directories


– Reports

● myReports

myReports is an application for generating reports on calls, queues, agents, performance,service level and rework codes by OpenScape Office Contact Center agents.

myReports offers the following features:

– Over 80 predefined reports

– BIRT RCP Designer for defining customized reports

– Time-controlled report generation

– Provision via email or as a printout

– Output formats: Excel, PDF, Word and PostScript




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

Supported applications

The following table shows the telephones supported by OpenScape Office HX, as well as theapplications that can be used with these telephones:

1.4.7.2 Installation

The OpenScape Office applications are installed on a separate Linux server. A root account isrequired for installation.

The Linux operating system and the OpenScape Office applications are supplied on DVDs.Once the DVD for the OpenScape Office applications has been inserted, the installation routinebegins automatically (in an X environment with run level 5). Without an X environment (run level3), the installation routine must be started manually by entering "oso_install.sh" in the shell.

Once installation has been successfully completed, entering "y" reboots the PC. The Open-Scape Office applications run as a Linux service and start automatically once the PC has boot-ed.

Hardware requirements

The Linux server must fulfill the following requirements:

● Server PC, designed for 24-hour operation

● At least 1 GB RAM

● Hard disk, at least 300 GB

● 2.4 GHz processor or similar

Telephones myPortal myPortal forOutlook

myAttendant myAgent

OpenStage HFA Yes Yes Yes Yes

OpenStage T Yes Yes Yes Yes

OpenStage SIP No No No No

optiPoint 500 Yes Yes Yes Yes

optiPoint 410/420 HFA Yes Yes Yes Yes

optiPoint 410/420 SIP No No No No

optiPoint WL2 professional Yes Yes Yes Yes

Cordless DECT telephones (CMI) Yes Yes Yes No

Analog telephones (T/R) Yes Yes Yes No

ISDN telephones & cordlessDECT telephones (S0)

No No No No

Table 1-1 Supported applications



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

● Network interface (LAN >= 100MBit/s)

● DVD drive

● Broadband Internet access for software upgrades

● It is recommended to use a PC from an established PC manufacturer.

An overview of the tested server hardware is provided under:http://wiki.siemens-enterprise.com/index.php/OpenScape_Office_with_HiPath_3000.

Software requirements

The Linux server must fulfill the following requirements:

● Linux operating system Suse Linux Enterprise Server 10 - SLES 10 (32-bit)

General configuration

The Linux server for OpenScape Office HX requires a static IP address.

Restrictions

● Internet Protocol version 6 (IPv6) is not supported.

● Virtual machines (e.g. VMware) are not supported.

Virus scanner

Performance issues can occur if a virus scanner is installed and active in the background onthe Linux server for OpenScape Office HX, e.g. if the OpenScape Office Contact Center is inuse. In this case, the virus scanner activities should be scheduled to run at times when theOpenScape Office Contact Center is not in use or only in limited use.

Firewall

On the Linux server of OpenScape Office HX, the firewall available under Linux is deactivatedduring installation. If the customer’s security concept requires a firewall, reactivate the Linuxfirewall after installation has been completed.

Implementation

For the administration of the OpenScape Office applications, a PostgreSQL database is in-stalled on the Linux PC. The configuration data of a HiPath 3000 V8 connected with the LinuxPC is written to this database.

A SQL client implemented in the HiPath 3000 acts as the SQL interface that transfers the con-figuration data to the PostgreSQL database.

http://wiki.siemens-enterprise.com/index.php/OpenScape_Office_with_HiPath_3000

http://wiki.siemens-enterprise.com/index.php/OpenScape_Office_with_HiPath_3000




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

1.4.7.3 Licensing

Licenses are required to use OpenScape Office applications. License management of HiPath3000/5000 has been expanded for this reason from V8. In order to transfer license data, Open-

Scape Office must be connected to HiPath 3000.The licenses for OpenScape Office are available in addition to the existing licenses of the Hi-Path 3000/5000 system. The following licenses are supported for OpenScape Office and forCSP (CSTA service provider):

● Basic license package:

– 1 OpenScape Office basic license

– 10 standard user licenses

● User licenses:

User license DescriptionVoiceMail orVoiceMail-license

Voicemail only The voice mail function can only be operat-ed via the telephone. The VoiceMail license and the "Stan-dard User" license cannot be used simultaneously. Up-grading to the "Standard User" license is not possible andnot necessary.

Standard User myPortal Presence, CTI, voicemail and fax (inbound andoutbound)1 license per user, up to 384 licenses. The VoiceMail li-cense and the "Standard User" license cannot be used si-

multaneously.Standard User (100) myPortal Presence, CTI, voicemail and fax (inbound and

outbound)1 license per user, package with 100 licenses. The Voice-Mail license and the "Standard User" license cannot beused simultaneously.

myPortal for Outlook Integrated in Microsoft Outlook, 1 license per user, up to384 licensesIn order to use myPortal for Outlook, a Standard User li-cense is necessary.

If more myPortal for Outlook licenses are required than thenumber of Standard User licenses available, an additionalStandard User license must also be acquired for each ad-ditional myPortal for Outlook license.

Table 1-2 User licenses






A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

● Evaluation license for OpenScape Office (90 days, free):

This evaluation license is aimed at HiPath 3000 customers that have never used Open-Scape Office before. All OpenScape Office features are enabled for a grace period of 90days, after which they are automatically disabled. If regular licenses for OpenScape Officeare enabled during the grace period, the evaluation license is also disabled. License acti-

vation is performed via the Customer License Agent (CLA) and is only possible once, andonly when no OpenScape Office licenses were previously active.

To be able to use all OpenScape Office features, the number of HG 1500 B-channels foran HG 1500 board is increased to 30 during the grace period.

● Evaluation license for OpenScape Office Contact Center (90 days, free):

This evaluation license is for HiPath 3000 customers already using OpenScape Office butwithout Contact Center. Only the Contact Center is enabled. The grace period is 90 days,after which the license is automatically disabled. If regular licenses are enabled for theContact Center during the grace period, the evaluation license is also disabled. License ac-

tivation is performed via the Customer License Agent (CLA) and is only possible once, andonly when no OpenScape Office Contact Center licenses were previously active.

To be able to use all Contact Center features, the number of HG 1500 B-channels for anHG 1500 board is increased to 30 during the grace period.

Licensing is performed by Manager E, see Manager E Administrator documentation - Licens-ing.

myAgent ● For additional Contact Center agents or inspectors● For HiPath 3800 V8 only

● 1 license per user, max. 64 licenses per systemmyAgent licenses are "floating", meaning that you can definedany number of stations as agents, but only a limited number ofagents may be logged in simultaneously, depending on thenumber of licenses.

myReports ● Generating reports● max. 1 license per system

Contact Center email ● Distribution of e-mail for the contact center● For HiPath 3800 V8 only● max. 1 license per system

Contact Center Fax ● Distribution of fax messages for the contact center● For HiPath 3800 V8 only● max. 1 license per system

Contact center license Description

Table 1-3 Contact center licenses



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.7.4 Simultaneous UCD Login

When an agent logs in to myAgent, they are automatically logged in to "Universal Call Distribu-tion" (UCD) on HiPath 3000. In the event of a failure of OpenScape Office, and thus of myAgent,

incoming calls are handled by UCD, thus guaranteeing the ongoing function of the call center.If myAgent has already failed when an agent wishes to log in, they can log in to UCD on theirtelephone.

1.4.8 IP Mobility

The mobility option integrates mobile terminals in the enterprise’s communication processesand offers users the following basic functions:

● The One Number Service offers availability under a single call number regardless of loca-tion and irrespective of the mobile unit used.

● Mobile staff have access to their familiar telephone features and communication platformregardless of their location and the terminal used.

New features in HiPath 3000/5000 support teleworking and desk sharing concepts.

1.4.8.1 Teleworking

The Teleworking option is the solution for members of staff who work from home using a de-fined workstation outside of the company campus. Using the Teleworking option, both the OneNumber Service, as well as access to HiPath telephony features at a defined telephone are pro-

vided to employees working from home. When working from home, any analog terminal or anoptiPoint/OpenStage telephone can be used.

1.4.8.2 Desk Sharing

The DeskSharing option is the hoteling solution and provides desks for employees whose jobsrequire them to change locations within the company campus. DeskSharing desks can be usedby several employees, ensuring that the best possible use is made of the available desks.

DeskSharing offers the following basic function:

Employees who do not have a fixed desk can reserve a desk and telephone for a specific peri-

od. This reservation is made by means of a Web user interface from any PC or by means of acheck-in station in the foyer of a DeskSharing area. Employees can book themselves in at theirtemporarily reserved desk. Check-in takes place either at the check-in station in the foyer of aDeskSharing area or by check by phone from any phone within the DeskSharing area. Whenemployees check in, the properties and features of their home telephone are automatically re-located to the reserved station.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

1.4.9 IP Mobility Enhancement (Emergency Number)

In an IP network, a mobile station can log on either at home or at any other remote networknode. In the case of an emergency call from a HFA-IP telephone that is registered at a remote

network node, the emergency destination of the remote network node cannot be called. In-stead, only the emergency destination of the HiPath 3000 node where the telephone is physi-cally installed is called.

The emergency number valid for the IP telephone must be a destination in the HiPath network.The emergency destination can either be connected as a standard telephone with the HiPath3000 network node, or as a virtual device in which call forwarding to an emergency destination(e.g. to the CO) is activated.

An emergency prefix must be stored in the HFA-IP telephone. This number can be used toreach the emergency destination from anywhere within the network. Emergency numbers forpolice or fire services (112 or 110 in Germany, for instance) are dialed with a prefix by the sub-scriber.

>

A direct call to an emergency destination in the public network is not possible be-cause telecom providers do not support this type of access.

>It is important that the emergency numbers are configured both in the home systemand in the destination system. In the case of varying emergency numbers in differentcountries (e.g. the emergency number 911 is valid in the U.S., while 112 must be di-aled in Germany), the emergency number of the country in question must also be

configured in the system in the destination country.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.10 Internet Telephony – ITSP Features

1.4.10.1 Features of Internet Telephony

Information about Internet telephony features can be found in the feature description.

1.4.10.2 Released ITSPs

A current list of released Internet Telephony Service Providers (ITSP) is available at the follow-ing link:http://wiki.siemens-enterprise.com/index.php/Collaboration_with_VoIP_Providers

Only the ITSPs named in this list are supported.

1.4.10.3 Supported ITSP Connections

HiPath 3000/5000 V6.0 or later supports:

● ITSP connections with single-number registration. This is currently the provider interfaceoffered most often for the private customer segment and for smaller communication solu-tions for medium-sized companies.

● Internet telephony system connections for larger-scale system configurations. In this case,the customer receives a phone number range from the ITSP.

HiPath platforms and ITSP connections are subject to intensive tests to guarantee secure andhigh-quality communication.

1.4.10.4 Features Supported by HiPath 3000/5000 V8 for Connecting to ITSPs

Standalone and networked systems

HiPath 3000/5000 V8 enables standalone and network systems to be connected to ITSPs.

Networked systems

S0 connections and Internet telephony connections can be used in parallel in all networking so-

lutions (HiPath 3000/5000 systems connected to each other or to HiPath 2000 systems / HiPathOpenOffice EE) to connect to ITSP analog lines. HiPath 3000 V6.0 SMR-9 or later supports thesimultaneous use of connections over CorNet IP and ITSP ports.

http://wiki.siemens-enterprise.com/index.php/Collaboration_with_VoIP_Providers

http://wiki.siemens-enterprise.com/index.php/Collaboration_with_VoIP_Providers




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

In HiPath 3000 V8 and HiPath 4000 V5 and later systems, only SIP-Q V2 protocol is used forIP networking between these systems and only CorNet-NQ is used for TDM networking. H.323protocol is no longer supported.

Up to HiPath 3000/5000 V7, there was a central ITSP connection (one ITSP access point forthe entire network). In HiPath 3000/5000 V8 and later, each node can have an ITSP point.

Internet telephony types

ADSL and SDSL are supported.

ITSP connections with single-number registration

Up to 30 user IDs (SIP client user accounts) can be set up on ITSP connections with single-number registration.

Maximum number of simultaneous calls

The maximum number of simultaneous calls to the ITSP depends on the codec used and onthe available bandwidth of the Internet connection. Up to 30 simultaneous calls are possible.

The maximum number of simultaneous calls is calculated based on the upstream rate and thebandwidth required for each call (128 Kbps).

[Number of calls = upstream rate (in Kbps) / 128 Kbps]

Least Cost Routing (LCR)

Up to four simultaneously active/registered ITSPs are supported by the system for least costrouting (LCR). Depending on the bandwidth, more connections may be possible.

IP/IP e2e payload via enterprise proxy

In HiPath 3000/5000 V7 R2 and later systems, "IP/IP e2e payload via enterprise proxy" is sup-ported for Internet telephony. This means that for Internet telephony no data packets have to

be processed by digital signal processors of the system. Calls are routed via LAN, router andITSP. HiPath 3000/5000 sets up a call to the remote station. This means that no gateway chan-nels (DSP channels) are required for ITSP connections.

>Important: Networking between HiPath 3000 V8 and HiPath 4000 V5 has not yetbeen released and does not work when SPE is activated.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.10.5 ITSP Features

Emergency numbers, special numbers, 0180/0800 services

● Emergency numbers (110, 112) are not fully supported by ITSPs because the local net-work cannot be uniquely assigned during breakout into the public network. These connec-tions must be set up over S0 accesses.

● Special number are not transferred by all ITSPs.We recommend transferring the following special numbers by default over ISDN:


To make trunk calls to selected service providers or services (such as 0180/0800 numbers),the LCR must be adapted.

Bandwidth control

All connections to the ITSP use HiPath 3000/5000 DSP resources, as do connections with ananalog/IP gateway (for example, ISDN connections) or when using music on hold. Please referto the notes in this manual in Section 2.1, "System-Related Capacity Limits" and in the servicemanual under Dynamic configuration rules.

Restrictions in voice quality can occur in connections that are not QoS-capable (in general,ADSL connections). High voice quality is generally achieved if a non-QoS-capable Internet te-lephony connection is used exclusively for voice connections to the ITSP.

Connection can suffer temporary interruptions as a result of the provider’s network availability.Please note the ITSP’s terms and conditions. If connections are not set up over SIP, they canbe established by HiPath 3000/5000 V8 (HG 1500 V3.0) over ISDN.

The router used by the customer must be able to guarantee good voice quality over QoS func-tions and bandwidth control mechanisms.Although four different ITSPs may be registered simultaneously, more connections may be pos-sible depending on bandwidth.

0137 Televoting

0138 Televoting

0900 Premium-rate services

118xy Information services116 116 Emergency cancellation number for EC cards, credit cards, etc.

>Important: If a system is only operated over an Internet telephony connection, rout-ing can also be configured in the ITSP direction for emergency calls and specialnumbers. You must first ensure that the ITSP supports these services.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

Calling party identification

Calling party identification:The CLIP and CLIR features are implemented differently in the individual ITSPs. Restrictions

may occur in call number display or entries may occur in the missed calls list. The CLIP noScreening feature is currently not supported. The B station’s display/missed calls list shows thestation number of the line to the ITSP - not that of the calling A station.

Connections with breakout into the fixed network/mobile telephone system or from thefixed network/mobile telephone system

Connections with breakout into the fixed network/mobile telephone system or from the fixednetwork/mobile telephone system:Provider-internal connections (destination is busy/not registered)Internal connections to a busy or unregistered station are generally signaled correctly.

Calls to other ITSPs

Calls to other ITSPsThese calls are technically feasible, however, the individual providers match the routing func-tions in their network with the relevant business model. For more information, consult the rele-vant ITSP.

Call data evaluation

Call data evaluation

The SIP protocol records itemized call data by time. Evaluation is possible using external ap-plications, such as Teledata Office.

DTMF transmission over IP

DTMF signals are transmitted in the voice channel. The G.711 codec is required for securetransmission to the provider.

Fax transmissions

Fax transmissions are not supported by every provider. We recommend using ISDN for fax

transmissions (default setting).In HiPath 3000/5000, gateway T.38 channels are used for fax transmissions over ITSP connec-tions. Fax transmissions over the Internet using G.711 are often disrupted or do not work prop-erly. Therefore fax transmission over Internet telephony and G.711 is not supported. If the pro-vider supports the T.38 protocol, then T.38 must be activated in the gateway. Otherwise ISDNshould be used for the transmission.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

Modem transmissions and ISDN data services (for example, the use of EC cash devices)are not supported)

These services are not supported.

CSTA Monitoring of Connections to ITSPs

These services are not supported. Applications that provide this feature are consequently not supported (for example, callcenters).

1.4.10.6 Network Address Translation (NAT)

Network Address Translation (NAT)

NAT is the conversion of IP addresses in the LAN for the Internet. NAT can be enabled and dis-abled in HiPath 3000/5000.

Certain services – such as VoIP or video telephony – embed subscribers’ IP addresses in theirdata packets, however, instead of just noting them in the packet headers).These services are only compatible with NAT within a VPN or require the use of additional pro-tocols (for example, STUN) or infrastructure components to bypass problems with NAT (= NATTraversal) for connections to an Internet telephony provider.

Operation behind a router/firewall in NAT traversal

For operation behind a router/firewall: If an ITSP provides a STUN server for NAT traversal,none of the routers implemented supports the "symmetric NAT" variant. The use of STUN pro-tocols is not required and the firewall reconfiguration is not necessary if the ITSPs perform NATtraversal over infrastructure components in the provider network, such as, session border con-trollers (SBC). "SIP-aware" firewalls also feature a NAT traversal function.

Simple Traversal of UDP over NATs (STUN)

STUN is a simple client/server-based network protocol designed to identify the existence ofNAT firewalls and routers. A central STUN client on the first HG 1500 V3.0 (signaling gateway)connects with a STUN server at the ITSP. The STUN server provides information about how

the Internet connection is perceived externally. HiPath 3000/5000 uses this information to sendpackets to an ITSP or called party in the Internet to ensure that even HiPath 3000/5000 systemsbehind a NAT device can be reached from the Internet. The settings for an upstream NAT fire-wall or a NAT router do not have to be changed for this.

A signaling gateway can perform STUN requests on behalf of media gateways. The mechanismthat sends IP packages on behalf of other devices is known as "IP Spoofing".




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

By deliberately using special filters, some network infrastructure components can check the as-signment of incoming packets and take the necessary action if the assignment is incorrect, forexample, trigger an alarm (e-mail), reject the packet or even block the port (for example, bySNMP access to switches). Network administrators must configure exceptions so that the

STUN protocol can be used for NAT traversal even in such an environment.

HG 1500

HG 1500 is operated in the LAN behind external routers with firewall or NAT functionality.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

1.4.11 Telephones for Internet Telephony

1.4.11.1 Internet Telephony Terminals

The HiPath 3000/5000 IP system supports the following DSL terminals:

● optiPoint 410 S

● optiPoint 420 S

1.4.11.2 DSL Terminal Features

Actively supported features

Terminals actively support the following DSL features:

● CLIP (Calling Line Identification Presentation)optiPoint 150 S only supports the feature in standalone systems.

● CLIR (Calling Line Identification Restriction). The optiPoint 150 S phone does not supportthis feature.

● COLP (Connected Line Identification Presentation)

● COLR (Connected Line Identification Restriction). The optiPoint 150 S phone does notsupport this feature.

● Consultation hold

● Call hold

● Toggle

● Transfer (Screened and Unscreened Transfer)The optiPoint 410 S and optiPoint 420 S phone family supports the Unscreened Transferfeature.

● MWI (HiPath 3000/5000 V8 and higher). This feature is supported for SIP telephones inindividual nodes and in the network. If a voicemail system (HiPath Xpressions) receives anew message, it sends an MWI message via HiPath 3000/5000 to the relevant SIP tele-

phone. This activates the MWI display on the SIP telephone.

● DISA (Direct Inward System Access): Features cannot be activated for the SIP telephone.

● Inband DTMFoptiPoint 150 S only supports the G.711 codec.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

Passively supported features

Although Internet telephony stations may not activate the following features, they may be pas-sively involved:

● Call forwarding (forwarding to an Internet telephony station is supported)

● Conference (Internet telephony stations may be passively involved)

● Park (Internet telephony stations may be parked; from the perspective of the Internet tele-phony station, this is similar to "Call hold")

● Live Call Recording (Internet telephony stations may be passively involved)

● Whisper (Internet telephony stations may be passively involved)optiPoint 150 S does not supports this feature.

●

Automatic COS changeover (Internet telephony stations support automatic COSchangeover)

● Internal traffic restriction groups (Internet telephony stations can be entered in ITR groups)

Restrictions for Internet telephony stations

The following restrictions apply to Internet telephony stations:

● Internet telephony stations are configured on HiPath 3000/5000 V8 as DSS1 (functionaltelephones) and therefore cannot be supervised by the system (no monitoring). Internettelephony stations cannot use applications that require monitoring (for example, HiPath

ComAssistant).

● Internet telephony stations cannot be integrated into call pickup groups, hunt groups, team,top or MULAP groups.

● Internet telephony stations cannot activate or use system features that can be operatedwith codes.

● Music is played when an Internet telephony station is on hold. Music is not played and aring tone is not applied for the Internet telephony station when unscreened transfer is per-formed between the Internet telephony station and another station.

●

The display on the Internet telephony station is not refreshed if an Internet telephony sta-tion is unparked by a different party to the one who parked it.

● SIP terminals are not supported by the deployment tool (DLS interface, DLI) in HiPathXpressions Compact boards (HiPath 3000).



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

● optiPoint 150 S allows you to toggle between two external calls. The active call can becleared down by briefly pressing the hookswitch. Simply replace the optiPoint 150 S hand-set to connect the two external parties to each other (this can lead to increased call charg-es). A connection of this kind can only be cleared down at the system by disconnecting the

relevant trunks or by resetting (restarting) the system.

● In some situations, you cannot use terminal-specific features on HiPath 3000/5000 V8.This includes features that are available over the terminal’s menu interface. The featuresavailable with the HiPath 3000/5000 V8 basic system have general release status.

Native SIP only supports:

● Basic call




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

1.4.12 Signaling and Payload Encryption (SPE)

Overview

This section describes the Signaling & Payload Encryption (SPE) feature. This feature is pro-vided in HiPath 3000/5000 V7 R4 and higher.

Both signaling and user data can be encrypted in the company network (LAN) on a user-spe-cific basis.

Signaling & Payload Encryption (SPE):

● Signaling encryption: Signal transmission between the gateway (HG 1500) and clients(e.g. OpenStage CorNet-IP [HFA], OpenScape Personal Edition) is encrypted using a 128-bit key. The same mechanism (AES) is used for IP trunking (HG 1500).

● Payload encryption: User data, also referred to as voice data or payload, is transferred viaSecure Real-time Transport Protocol (SRTP). This data is encrypted with a 128-bit key(AES). SRTP is also used for IP trunking (HG 1500). SPE and SPE CA certificates can beinstalled via the DLS or via the WBM. The procedure for exchanging the keys for SRTP iscalled Multimedia Internet KEYing or short, MIKEY.

Licensing

● Signaling encryption: No licenses are required to encrypt signaling data. This applies toHFA, H.323, SIP and IPDA signaling connections, as well as to the CTI interface.

● Payload encryption: A ComScendo Security license is required per B-channel (gatewaychannel) and per station to encrypt payload data . The ComScendo Security license is gen-erated automatically on the Central License Server (CLS) and does not cause any addi-tional costs.

Upgrade

If the software version is lower than V7 R4 it is necessary to upgrade the software to enable theuse of SPE with HiPath 3000. Hardware does not need to be upgraded.

The Signaling & Payload encryption feature is provided in HiPath 3000/5000 V7 R4 or higher.If a software version lower than V7 R4 is in use, it must be upgraded before the SPE feature

can be used in HiPath 3000. Please refer to the published release notes.

Hardware does not need to be upgraded. As a result of the increased demand by SPE for re-sources further HG 1500 boards might be required.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

Terminal encryption

Signaling & Payload Encryption is only supported by HFA terminals. The following HFA termi-nals support the encryption:

● optiPoint 410 (not optiPoint 410 entry, optiPoint 410 economy)

● optiPoint 420 (not optiPoint 420 economy)

● OpenScape Personal Edition

● OpenStage 20 E, 20, 20 G

● OpenStage 40, 40 G



Analog fax devices or modems can be connected to the company LAN using the IP adapter.AP does not support encryption, but can still be operated in the company network.

Configuration of the IP terminals

An IP terminal can be configured from one of the following types of IP clients:

TDM terminal configuration

A TDM terminal is generally classified as standard client but can also be configured as a se-cure client by activating the "payload security" flag.

Configuring analog and TDM terminals does not influence their behavior. This configuration isaimed only at detecting "IP/IP e2e payload via enterprise proxy" encryption.

Using the "payload security" flag you can set on OpenStage TDM terminals whether to displaywhen part of a connection path to an IP station is encrypted. It is not possible to encrypt sig-naling and voice data along the entire connection path for OpenStage TDM terminals. Settingthe "payload security" flag for all other TDM terminals has no function.

Standard client: Unsecured terminal.SRTP (voice encryption) and signaling encryption (TLS-secured) is notsupported.

Secure client: Full encryption (SRTP and TLS secured)Also supports unsecured terminals and terminals secured only for sig-naling (TLS secured).




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Features

1.4.13 Licensing

Versions 5.0 and later of HiPath 3000 and HiPath 5000 use a new, centralized licensing proce-dure known as the License Management System. The procedure is used in all HiPath products,

for example communication systems, workpoint clients, and applications.

To license a product you must first establish a connection with the Central License Server (CLS)via the Customer License Manager (CLM). The customer-specific data entered is used touniquely identify the product configuration for which the relevant license file is to be supplied inencrypted format. The license file contains the licenses for all licensed products.

The CLM is responsible for activating the license file and allocating it to the Customer LicenseAgent (CLA). This is where the license data is validated. Distribution of the licenses to the indi-vidual products using HiPath 3000/5000 Manager E can then begin.

All licenses that can be ordered for HiPath 3000 V8 are handled by HiPath License Manage-

ment.

The following licenses are available for HiPath 3000 V8:

● optiClient Attendant V8

● ComScendo license for IP workpoints (including SIP)

● ComScendo security license for IP workpoints and B channels

● S2M License for releasing B channels

● HG 1500 B channels

● HG 1500 VPN (Virtual Private Network)

● HG 1500 LWCA (Light Weight Certification Authority)

● BS4 License for releasing traffic channels

● License for an Xpressions Compact-based announcement

● HiPath TAPI 120 V2.0, HiPath TAPI 170 V2.0

Please refer to the relevant sales information for information on licenses for applications and IPclients that can be connected.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Features

Figure 1-4 Licensing Process with Central License Server (CLS)

2. License file (*.xml) isdownloaded using CLM

1. License file is requestedusing customer-specific

data

Customer LicenseAgent CLA

4. License file is validated

5. License file is analyzed

Customer License Client(CLC)

Example: HiPath 3000/ 5000 Manager E

6. Individual licenses aredistributed to the licensedproducts

3. License file is activated

License Management SystemCentral License Server CLS

https://www.central-license-server.com/

Customer LicenseManager (CLM)or

2. License file (*.xml) isdownloaded withoutCLM (license file isstored manually in theimport directory)






A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Application and Networking Scenarios

1.5 Application and Networking Scenarios

Overview

This chapter contains information on key implementation and networking scenarios. The sam-ple configurations describe how networking scenarios are configured.

Content

This chapter covers the following topics:

● Section 1.5.1, "HiPath 3000 Standalone (TDM)"

● Section 1.5.2, "HiPath 3000 Standalone (TDM and IP)"

● Section 1.5.3, "HiPath 3000 Networked With HiPath 5000 via IP"

● Section 1.5.4, "HiPath 3000 Networked Over IP with HiPath 5000 (With VPN)"

● Section 1.5.5, "HiPath 3000 Networked With HiPath 2000, HiPath 4000 and HiPath 5000"

● Section 1.5.6, "HiPath 3000 as a Branch on HiPath 4000 (Small Remote Site)"

● Section 1.5.7, "Virtual Private Networks (Site-to-Site VPN)"

● Section 1.5.8, "IP Networking of Two HiPath 3000 Systems that Support Signaling andPayload Encryption (SPE)"

● Section 1.5.9, "Networking of HiPath 3000 with OpenScape Voice via SIP-Q V2"



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011




1.5.1 HiPath 3000 Standalone (TDM)

Figure 1-5 HiPath 3000 as a Standalone System

In this scenario, HiPath 3000 is implemented as a standalone system in the traditional tele-phone infrastructure environment.

1.5.2 HiPath 3000 Standalone (TDM and IP)

Figure 1-6 HiPath 3000 as a Standalone System (TDM and IP)

In this scenario, HiPath 3000 is implemented as a standalone system in the traditional and IP-based telephone infrastructure environment. The customer’s existing IP network (corporatenetwork) is used to exclude IP workpoints. Existing fax devices are connected to the IP networkvia HiPath AP 1120.

This scenario is suitable for customers who want to protect their existing investments in the tra-ditional telephone infrastructure, but would like to migrate gradually to an IP-based environ-ment.

optiClient Attendant

HiPath 3000 V8Xpressions Compact

HiPath Cordless

TDM Workpoints

HiPath 3000 V8Xpressions Compact

TDM Workpoints

IP WorkpointsTeleworkerOpenScape Personal Edition

PSTN

IP Corporate Network AP 1120and fax




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm


1.5.3 HiPath 3000 Networked With HiPath 5000 via IP

Figure 1-7 HiPath 3000 Networked with HiPath 5000 via IP

In this scenario, HiPath 3000 is used as a gateway to the network operator’s traditional tele-phone infrastructure (PSTN). On the station side however, the IP-based telephone infrastruc-ture is used.

HiPath 5000

PSTN

IP Corporate Networks

HiPath 3000 V8

Xpressions Compact

TeleworkerOpenScape Personal Edition

IP Workpoints

AP 1120and fax



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011




1.5.4 HiPath 3000 Networked Over IP with HiPath 5000 (With VPN)

Figure 1-8 HiPath 3000 Networked over IP with HiPath 5000 (with VPN)

HiPath 5000 PCS is not available in HiPath 3000 V8. Only the use of HiPath 5000 RSM is en-abled.

IPHiPath 5000

Call Center

e.g. HiPath ProCenter

Agents, Supervisor

IP Workpoints

HiPath 3000 V8

IP Workpoints IP Workpoints

IP Workpoints

VPN

VPN

VPN

VPNPSTN




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm


1.5.5 HiPath 3000 Networked With HiPath 2000, HiPath 4000 andHiPath 5000

Scenario

Figure 1-9 Networking HiPath 3000 with HiPath 2000, 4000, 5000

The features transmitted between communication systems are dependent on the protocolused.

Using the protocols

Protocols are used as follows (regardless of version):

● HiPath 3000 V8 or later <-> HiPath 4000 V5 or later <-> HiPath 5000: SIP-Q V2 and Cor-Net-NQ

● HiPath 3000 V8 <-> HiPath 3000 V7 <-> HiPath 2000 (HiPath OpenOffice EE) <->HiPath 4000 V4 <-> HiPath 5000: SIP-Q V2, CorNet IP and CorNet-NQ

>The CorNet IP protocol is not supported in HiPath 3000 V8 and HiPath 4000 V5 andlater systems for networking these systems.

HiPath 5000PC-based ComServer

PSTN

PSTN

PSTN

PSTN

PSTN

IP phones

HiPath 4000

HiPath OpenOffice EE

* HiPath 3000

HiPath 3000

HiPath 3000

*: The networking protocol (SIP-Q V2 [IP], CorNet IP [IP] or CorNet-NQ [TDM]) is dependent on the communication system versions.

**: Only when networking via SIP-Q V2 and CorNet IP.

*

*

*

*

*

IP network**

or HiPath 2000



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011




1.5.6 HiPath 3000 as a Branch on HiPath 4000 (Small Remote Site)

Figure 1-10 Small Remote Site: Normal State

This scenario is a special variant of the networking with HiPath 4000 systems. This configura-tion enhances the failure tolerance of the IP stations.

In the normal state, the IP stations in the branch locations (small remote site) are logged onand registered at the HiPath 4000 system.

Station 4711 at location 2 can be contacted using the number 089/722 4711 via the HiPath4000 system at location 1.

Station 4711 at location 2 can be contacted using the number 040/123 10 via the HiPath 3000system at location 2 (principle: the call is forwarded to station 4711 in HiPath 4000 when youdial IP station 10 in HiPath 3000).

Fax station 20 can be contacted using the number 040/123 20 via the HiPath 3000 system at

location 2.

External outgoing calls from station 4711 are sent, depending on HiPath 4000 administration,either via HiPath 4000 or via the assigned HiPath 3000 gateway.

Boundary conditions for the small remote site:

With the exception of fax stations there must not be any TDM stations in the HiPath 3000 sys-tem on the subscriber side.

Station

Station

IP stations

IP stations

Location 1

Location 2

Location N

Station registered onHiPath 4000

HiPath 3000

HiPath 3000

HiPath 4000

089 / 722 xxxx

030 / 456 xx

040 / 123 xx

Fax: 20

4711




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm


The number of IP stations at the individual locations is defined by the limitations of theHiPath 4000 system and the IP infrastructure, in particular by the available bandwidths.

Bandwidth management performed by HiPath 4000 Resource Manager for IP trunking and IP

stations must be taken into account here.

This networking scenario is not approved for use at the moment in networks with only HiPath3000/5000 systems.

HiPath AllServe is not approved for use.

HiPath 5000 PCS is not approved for use.

Figure 1-11 Small Remote Site: Failure of the IP network

In emergency operation (e.g. if the IP network fails) IP stations lose the connection to the Hi-Path 4000 gateway. The "Small Remote Site Redundancy" function causes the call number andthe gateway to be switched automatically.

Station 4711 at location 2 registers automatically on the HiPath 3000 system at location 2 andis assigned the extension number 10.

An external call to extension 10 in HiPath 3000 reaches extension 10 directly in this case.

An external call to extension 4711 over HiPath 4000 can be routed via trunks within HiPath4000 to HiPath 3000.

Station

Station

IP stations

IP stations

Location 2

Location N

Location 1

Station registered onHiPath 4000

HiPath 3000

HiPath 3000

HiPath 4000

089 / 722 xxxx

Fax: 20

10

030 / 456 xx

040 / 123 xx



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011




1.5.7 Virtual Private Networks (Site-to-Site VPN)

HiPath 3000 provides a secure solution to implement site-to-site VPNs. The solution supportsnetworking sites (headquarters, branches etc.) via the cost-effective infrastructure of the public

Internet. ItIt is possible to network HiPath 3000 systems with HiPath 3000 systems and mixedHiPath 2000/HiPath OpenOffice EE/HiPath 3000 networks from HiPath 3000 V5.0 or later.They can be connected to the Internet for example via a fixed Internet connection or xDSL con-nections which provide a fixed IP address. Even Internet connections with a dynamic IP ad-dress can be used via DynDNS. Data and voice (TDM and VoIP) are tunneled over the Internet.HiPath 3000 checks authentication of the VPN partners, encrypts and decrypts the data pack-ets sent and received by the relevant workpoints and applications, and ensures data confiden-tiality and integrity.

Advantages of VPN site-to-site networking:

●

Secure business processes● Secure integration of external partners in the company network

● Access to company information for field service




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm


1.5.8 IP Networking of Two HiPath 3000 Systems that SupportSignaling and Payload Encryption (SPE)

This section describes the Signaling & Payload Encryption feature. This feature is provided in

HiPath 3000/5000 V7 R4 or later systems.

Figure 1-12 IP Networking of Two HiPath 3000 Systems with SPE

This scenario contains two SPE-ready HiPath 3000 systems whose HG 1500 gateways areconnected via a secure trunk. The signaling data between the HG 1500 and the HFA/SIP

phones is always encrypted using TLS. Several calls are displayed:

R <--> T Gateway call Payload is encrypted by HG 1500, even if a TDM terminalconfigured for HiPath 3000 as a "Traditional client" is in-volved. This is because the remote station supports pay-load encryption from the perspective of HiPath 3000.

N <--> X Gateway call Traditional client: Without signaling and payload encryp-tion.

Standard client

Secure clientSecure client

TDM

HiPath 3000

node 2

Traditional client

HiPath 3000

node 1

TDM TDM

Traditional client

HFA/SIP

HFA/SIP

Secure client

HFA/SIP

Secure client

HFA/SIP

Secure client

HFA/SIP

S e c u r e t r u n k

( V 8 o r l a t e r : S I P - Q

V 2 )

HG 1500

Modem connectionUnencrypted connectionEncrypted connection

Signaling data between HG 1500 and HFA/SIP terminals

HG 1500

1

R

T

N

X

2

M

3 4

Y

S

Z

5

1

2



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011




If SPE is activated on HiPath 3000, signaling & payload encryption is activated by default on allIP trunking connections on this HiPath 3000 system.

Due to the payload switching concept (PLS), the HG 1500 gateway is not involved in transmit-ting payload from a network call between two IP terminals. HG 1500’s payload encryption ca-pability is only relevant in gateway calls.

M <--> T Gateway call Payload is not encrypted by HG 1500, because the re-mote station does not support payload encryption fromthe perspective of HiPath 3000.

S <--> Y Network call Payload is encrypted, because both terminals are "Se-cure clients". Signaling data (such as IP addresses) istransmitted via the HG 1500 gateway.

M <--> Z Network call Payload is not encrypted, because a terminal is config-ured as "Standard client". Signaling data (such as IP ad-dresses) is transmitted via the HG 1500 gateway.Standard client: Without payload encryption.

3

4

5




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm


1.5.9 Networking of HiPath 3000 with OpenScape Voice via SIP-Q V2

Requirements

● HiPath 3000, V8 MR5 and later

● OpenScape Voice, V5 R0 and earlier

Scenario

The following figure shows the principal scenario for networking OpenScape Voice with HiPath3000 in conjunction with other trunking connections. The trunking connection between HiPath3000 and OpenScape Voice is only implemented for SIP-Q V2. SIP-Q V1 is not supported byany version of HiPath 3000.

Figure 1-13 Networking HiPath 3000 with HiPath 8000 via SIP-Q V2

HiPath 3000 only functions as a gateway to the PSTN (public switched telephone network); noend points are configured.

>This functionality is only available on PSR basis.

OpenScape Voice PSTN

HiPath 3000

SIP-Q V2

SIP station

SIP trunking

RG 8700

HiPath 4000

OpenScape Voice

PSTN

SBC

SBC

IP/WAN/SP

Q S i g - N s t A



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011




Networking Features and Limitations

Network:

● Only star networks are supported. In these networks, OpenScape Voice must be the cen-tral node.

● Two HiPath 3000 cannot be networked with each other via an IP connection.

CO:

● HiPath 3000 supports ISDN and CAS (channel associated signaling) interfaces for thetrunk connection.

● Analog trunk lines and SIP providers are not supported.

Terminals:

● TDM terminals (UP0, analog and CMI) can be connected to HiPath 3000.

● IP terminals cannot be connected to HiPath 3000.

Fax:

● T.38 is supported.

● G.711 is supported. The codec is switched on automatically when a fax tone is detected.

OpenScape Branch environment:

● HiPath 3000 is released as a gateway for a branch solution with OpenScape Branch SIP

proxies. Comdasys products are not supported, however.● In an optiPoint telephone, the "low bandwidth only" codec must not be activated.

● MoH is not available in the restricted mode. The connection on hold is muted.

Route optimization:

● Route optimization is not supported and must be deactivated.

● Rerouting is not supported and must be deactivated.

Central voicemail:

A central voicemail can be connected to HiPath 3000 as well as to OpenScape Voice.OpenScape UC application:

HiPath 3000 V8 R4 and earlier: An OpenScape UC user is not permitted to use a HiPath 3000telephone nor an external station reachable via the HiPath 3000 as an OND device.

HiPath 3000 V8 R5 and later: OpenScape UC users can work under their own phone numbereither on their own telephone (ONS device) or on another telephone (OND device). The ONDdevice can be: an internal telephone of HiPath 3000 or an external telephone that can bereached via HiPath 3000.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Migration

1.6 Migration

1.6.1 HiPath 3000

HiPath 3000 V6.0 or later offers new features, such as "Extended Number of CDR Entries".These new features require additional memory which is provided by the new 64-MB MMC card.New control boards are essential to guarantee the function of the 64-MB MMC card.

The new control boards, including the 64-MB MMC card, are included with the upgrade itemsfor HiPath 3000 V8 (HiPath 3300, HiPath 3350, HiPath 3500, HiPath 3550). The control boardsfor HiPath 33x0/35x0 are also equipped with the new Entry Voice Mail (EVM) feature.

1.6.1.1 Standalone

If a gateway is added to a standalone system (e.g. HiPath 3800 V6.0), the alive monitoring mustbe activated. This ensures that the allocation of resources is controlled via the gatekeeper.

1.6.2 HiPath 33x0 and 35X0 With EVMWith V6.0 or later, 33x0 and 35x0 systems are delivered with mainboards equipped with theEntry Voice Mail module (EVM). Xpressions Compact should be marketed for requirementsabove and beyond this. In version 6.0 or later the LIM module is included in the base package.

Only Xpressions Compact is marketed for existing customers.

With Version V5.0, new S2m boards requiring a license are provided for the 35x0 model. Theserequire the marketing of B channel licenses and release over the license server. Existing cus-tomers can continue to use the existing S2m boards that do not require a license by upgradingto version 5.0 (a license is not required for version V5.0). Mixed mode in a single system is pos-

sible.

>Provisions have not been made for a software-only update from an older version toV8. Updates of this kind are not possible.

HiPath 3000 V5.0 or later only supports 64-MB multimedia cards (MMC64).MMC16s (16 MB) are not supported.The system verifies the MMC in the course of booting and aborts the boot operationif it detects an MMC16.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Migration

1.6.3 HG 1500 V3.0

HG1500 V3.0 hardware can be implemented in a HiPath 3000 V8 system environment. TheHG1500 software must be updated for this.

● HXGS3The HXGS3 variant is designed for installation in wall-mounted HiPath 3350 and HiPath3550 systems. The board features two slots for extension modules. However, only one slotis supported and released.

● HXGR3The HXGR3 variant is designed for HiPath 3300 and HiPath 3500 systems installed in 19"racks. This variant features a front panel. The card features two slots for extension mod-ules. However, only one slot is supported and released.

● STMI2

The STMI2 variant can be used with HiPath 3800.

● PDM1 expansion moduleBy means of one PDM1 module each, the HXGS3 and HXGR3 basic boards can be ex-panded by an additional eight B-channels (one DSP and SDRAM pair).

Installing a fan kit for HG 1500 V3.0 in HiPath 3350/3550

A fan must be installed in HiPath 3350 and HiPath 3550 if an HXGS3 board is inserted in thetop slot sequence (slot four in HiPath 3350 and slots four, six, and eight in HiPath 3550).

A fan is not required for the lower slot sequence (slot five for HiPath 3350 and slots five, seven,and nine for HiPath 3550).




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Migration

1.6.4 Peripheral Boards

The following peripheral boards are no longer supported in V6.0 or later:

● SLA16 only in HiPath 37x0 systems● SLC16

● TMS2M

● TMOM

1.6.5 OpenScape Personal Edition

OpenScape Personal Edition can be implemented on HiPath 3000 V8 MR3 or later systems.This product is the successor to optiClient 130.

1.6.6 optiPoint 400/410/420/600

A software update will be required for the upgrade.

The optiPoint 400 standard, economy and optiPoint 600 office (in CorNet-IP mode) are no long-er supported.

1.6.7 optiClient Attendant

Compatibility of the optiClient Attendant with HiPath 3000:

HiPath3000 V8

HiPath3000/5000

V7

HiPath3000/5000

V6.0

HiPath3000/5000

V5.0

HiPath3000 V4.0

HiPath3000 V3.0

HiPath3000 V1.2

optiClient Attendant V8 Yes Yes No No No No No

optiClient Attendant V7.0 No No Yes Yes Yes Yes Yes

optiClient Attendant V6.0 No No No No Yes Yes Yes

optiClient Attendant V5.0 No No No No No Yes Yes



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Migration

1.6.8 CMI

New BS4 base stations that require a license are supplied with Version V5.0. These require themarketing of CMI licenses and release via the license server. Existing customers can continue

to use the existing BS3 base stations that do not require a license by upgrading to Version V5.0.BS3x base stations continue to be supported with Version V5.0. Mixed mode in a single systemis possible.

The base station BS4 operates at HiPath 3000 V5.0 or later with SLC16N, SLCN, and directconnection (not with SLC16).

The cordless telephones Gigaset 3000 Comfort and Micro, Gigaset 4000 Comfort and Microare supported.

1.6.9 Licenses

The following HiPath 3000 licenses can be migrated to the V8 license structure via HiPath Li-cense Management:

● HG 1500: Existing HG 1500 licenses can be upgraded to V8 via CLS. – IP user licenses for workpoints in accordance with ComScendo license for IP work-

points – B Channels – LWCA (Light Weight Certification Authority)

License migration from V7 to V8

The following HiPath 3000 licenses can be migrated to the V8 license structure via HiPath Li-cense Management:

● ComScendo license for IP workpoints

● S2M license for releasing B channels (in Germany, for example: at least 30 B channels foreach S2M)

● HG 1500 B channels

● HG 1500 LWCA (Light Weight Certification Authority)

● Cordless base station BS4

● License for a HiPath Xpressions Compact-based announcement

The license server supports the direct migration of licenses from V4.0 to V8, V5.0 to V8, V6.0to V8, and from V7 to V8.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Migration

1.6.10 Networking

The sample configurations describe how networking scenarios are configured.

With HiPath 3000/5000 V5.0/V6.0:

HiPath 3000 V5.0/V6.0 and V7/V8 cannot be operated in mixed mode via IP trunking. Systemswith V5.0/V6.0 software must be upgraded to V7/V8.

With HiPath 3000 V3.0/V4.0:

The CorNet N protocol can be used in TDM-based networks. This means that HiPath 3000V3.0/V4.0/V5.0/V6.0/V7/V8 and Hicom 150 E/H can be operated in mixed mode.

Only CorNet IP protocol is used for IP networking. All nodes must be upgraded to the same

software version.

With HiPath 4000:

When migrating from TDM-based networks, it is possible to set the CorNet N or CorNet NQ pro-tocol. This means that Hicom 300/HiPath 4000 can be operated in mixed mode with HiPath3000 V3.0/V4.0/V5.0/V6.0/V7/V8 and Hicom 150 E/H.

Only CorNet IP protocol is used for IP networking using HiPath 4000 V2.0/V3.0. All HiPath 3000nodes must be upgraded to at least V5.0.

In HiPath 3000 V8 and HiPath 4000 V5 and later systems, only SIP-Q V2 protocol is used for

IP networking between these systems and only CorNet-NQ is used for TDM networking. Cor-Net IP protocol is no longer supported.



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Sales-Oriented Documentation

1.7 Sales-Oriented Documentation

● Ordering procedure for the following items:

– Via the Intranet:http://c4bs.gss.siemens.com

– Vie the Internet:http://www.click4business-supplies.siemens.de

● Other languages and addressessee list of stores at the following intranet address:https://www.g-dms.com/livelink/livelink.exe/28200122/ Contact_Partners_Localization.pdf?func=doc.Fetch&nodeid=28200122&viewType=1

Documentation Languages

Data sheetsData sheets can be accessed on the Internet at:http://www.enterprise-communications.siemens.com/global/Products.aspx (... -> Downloads).

HiPath 3000/5000 V8 German, English, French

HG 1500 V3 German, English, French

HiPath 3000/5000 Manager C German, English, French

OpenScape Office German, English, French

OpenScape Office Contact Center German, English, FrenchHiPath Xpressions Compact V3 German, English, French

Fixed Mobile Convenience German, English, French

HiPath 3000 V8 optiClient Attendant German, English, French

HiPath Cordless IP German, English, French

HiPath Cordless Office German, English, French

Gigaset professional German, English, French

OpenStage HFA/SIP German, English, French

OpenStage T German, English, French

optiPoint 500 German, English, French

OpenScape UC Application,OpenScape Personal Edition

German, English, French

Brochures and promotional giftsPlease contact Product Marketing / Management.

http://c4bs.gss.siemens.com/

http://www.click4business-supplies.siemens.de/

https://www.g-dms.com/livelink/livelink.exe/28200122/Contact_Partners_Localization.pdf?func=doc.Fetch&nodeid=28200122&viewType=1


http://www.enterprise-communications.siemens.com/global/Products.aspx



http://www.click4business-supplies.siemens.de/

http://c4bs.gss.siemens.com/




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Technical Documentation

1.8 Technical Documentation

You can select and download the following documents (HTML and PDF)

● User documentation● Administrator documentation

● Service documentation

● Sales documentation

from the following website:http://apps.g-dms.com:8081/techdoc

http://apps.g-dms.com:8081/techdoc

http://apps.g-dms.com:8081/techdoc



3000sb1.fm

A31003-H3580-Y100-10-7618, 01-2011



Privacy and Data Security

1.9 Privacy and Data Security

Handling Personal Data

This telephone system uses and processes personal data (as in call detail recording, tele-phone displays and customer data records).

In Germany, the processing and use of such data is subject to various regulations, includingthose of the Federal Data Protection Law (Bundesdatenschutzgesetz, BDSG). Observe all ap-plicable laws in other countries.

The objective of privacy legislation is to prevent infringements of an individual’s right to privacybased on the use or misuse of personal data.

By protecting data against misuse during all stages of processing, privacy legislation also pro-tects the material interests of the individual and of third parties.

Guidelines applicable to employees ofSiemens Enterprise Communications GmbH & Co. KG

Employees of Siemens Enterprise Communications GmbH & Co. KG are bound to safeguardtrade secrets and personal data under the terms of the company’s work rules.

It is imperative to observe the following rules to ensure that the statutory provisions relating toservice (on-site or remote) are strictly followed. This safeguards the interests of the customerand offers added personal protection.

Guidelines Governing the Handling of Data

A conscientious and responsible approach helps protect data and ensure privacy:

● Ensure that only authorized persons have access to customer data.

● Use the password features of the system with no exceptions. Never give passwords to anunauthorized person orally or in writing.

● Ensure that no unauthorized person can ever process (store, modify, transmit, disable ordelete) or use customer data.

● Prevent unauthorized persons from gaining access to data media such as backup copiesor log printouts. This applies to service calls as well as storage and transport.

● Ensure that data media that are no longer needed are completely destroyed and that doc-uments are not stored or left in places which are accessible to the public.

● Work closely with your customer contact; this promotes trust and reduces your workload.




A31003-H3580-Y100-10-7618, 01-2011


3000sb1.fm

Feedback/Comments

1.10 Feedback/Comments

To continually improve this system description, the editorial team welcomes your comments.We would particularly like to know your views on the following:

● Areas that require more detail. Areas that are too detailed.

● Areas that need more graphics to aid understanding.

● Areas that are difficult to understand.

● Issues you would like to include.

Outside of the U.S., please send your comments to:

Siemens Enterprise Communications GmbH & Co. KGDocumentation Center

SEN VA CTO SMC DC2Hofmannstr. 51D-81359 Munich GERMANYFax.: + 49 89 722 61691

Also include your address, telephone and fax number so we can contact you if necessary. Inthe U.S., please refer to the reader comment form at the back of this document for informationon how to submit comments about this manual.

1.11 Copyright

Copyright Siemens Enterprise Communications GmbH & Co. KG. This publication and all of itsparts are protected by copyright laws. Any use of this publication outside of the strict terms de-fined in the copyright laws is not permitted without the prior consent of the publisher and is liableto prosecution. This applies in particular to the reproduction, translation, microfilming or editingof this publication in any form, as well as to saving and processing in electronic systems.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch System Overview HiPath 3000

2 System Overview HiPath 3000

Electrical environment

HiPath 3000 is intended for use in dwellings, businesses, and industry. When the system is op-erated in an industrial environment, additional measures may be necessary for ensuring immu-nity from electromagnetic radiation (refer to Section 2.15).

HiPath 3300

HiPath 3350

HiPath 3550

optiPoint● acoustic adapter● analog adapter● recorder adapter● ISDN adapter● phone adapteroptiPoint BLF

OpenStage BLF

optiPoint Key ModuleOpenStage Key Module

HiPath 3500

optiPoint Appli-cation Module

optiPoint 410/410 S

optiPoint 420/420 S

optiPoint 500

optiPoint 600 office (UP0/E mode)

OpenStage 20 (HFA, TDM)




HiPath 3800

OpenStagePhone Adapter



System Overview HiPath 3000 Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

System Families and Accompanying Models

The individual housing designs and the variable connecting capabilities allow the following Hi-Path 3000 systems to cover a wide customer range.

This system description contains information on all systems. Information on marketing individ-ual models in different countries can be obtained at the responsible locations.

● System for free-standing installation and installation in 19" cabinets:

– HiPath 3800

●

Wall-mountable systems – HiPath 3550

– HiPath 3350

● Systems for installation in 19" cabinets

– HiPath 3500

– HiPath 3300

Refer to HiPath 3000 for information on the capacity limits of the different Section 2.1, "System-Related Capacity Limits" systems.

>All models of the HiPath 3000 system family can be operated as both a conventionalPABX or as a pure IP system. In this case, the IP stations connect directly via theHG 1500 boards.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



System-Related Capacity Limits

2.1 System-Related Capacity Limits

The following assumptions are used as a basis for calculating the maximum capacity limits:

● HiPath 3800: two board slots are reserved for trunks.● HiPath 3550, HiPath 3500: two S0 interfaces on the central board + one board slot are re-

served for trunks.

● HiPath 3350, HiPath 3300: two S0 interfaces on the central board are reserved for trunks.

● Traffic capacity: 0.15 erlangs

Deviating capacity limits can be determined for sales purposes.

Section 10.2 contains the system-specific maximum limits for UP0/E workpoint clients and theassociated key modules and adapters.

Table 2-1 HiPath 3000/5000 - System-Related Capacity Limits (Maximum Numbers)

System HiPath38001

1 System load is greatly dependent on factors such as system configuration and traffic. Static rules on configuration inspec-

tion are therefore not suitable. As a guide, configurations that include UCD/ACD, more than one SLC16N, groups with more

than 10 stations or OpenScape Office connections should always be inspected using the project planning tool

(https://enterprise-businessarea.siemens-enterprise.com/productinfo/document/c9yH1MXx3k8_/

HiPath%203000%20V8%20Planning%20Guide%20Performance%20Calculation%20Tool.xls).

HiPath3550

HiPath3500

HiPath3350

HiPath3300

HiPathCom-

ScendoService

S t a t i o n s / w o r k p o i n t c l i e n t s Total TDM + IP Stations2

2 Only configurations that do not exceed these limits are supported.

500 963 964 965 966 –

IP stations (system clients, H.323 clients) 500 967 967 967 8 967 9 1000

Total number of TDM stations2 384 9610 7710 11 5712 4113 –

T D M s t a t i o n s

Analog stations 384 962 4414 3615 2016 –

UP0/E stations 384 7217 4818 2419 2420 –

Additional stations via adapter (phoneadapter/analog adapter/ISDN adapter )

116 4810 2910 2421 2421 –

Cordless stations 250 64/3222 23 32 16 16 –

Base stations forHiPath Cordless Office 64 16/7 7 3 3 –

T

r u n k s

Total for all Trunks 250 60 60 16 16 –

Total analog CO and network trunks 120 60 60 16 8 –

Total number of digital trunk B channels and

digital network line B channels (S0, S2M)

180 60 60 16 16 –

CorNet-IP network trunks 128 60 60 16 16 250

HG 1500 boards 8 3 3 1 (224) 1 (224) –

Gateway channels to the system 128 48 48 16 16 –

https://enterprise-businessarea.siemens-enterprise.com/productinfo/document/c9yH1MXx3k8_/HiPath%203000%20V8%20Planning%20Guide%20Performance%20Calculation%20Tool.xls







A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

System-Related Capacity Limits

3 Up to 96 stations can be TDM stations.

4 Up to 61 of the 96 stations can be TDM stations (4xanalog T/R + 1xUP0/E + 7xBS/32xHiPath Cordless Office stations at

the central board + 3xSLU8R or 3x8SLAR or 3xSLAD8R).

5 Up to 41 of the 96 stations can be TDM stations (4xanalog T/R + 5xUP0/E + 3xBS/16xHiPath Cordless Office stations at

the central board + 1x16SLA).

6 Up to 33 of the 96 stations can be TDM stations (4xanalog T/R + 5xUP0/E + 3xBS/16xHiPath Cordless Office stations atthe central board + 1xSLU8R or 1x8SLAR or 1xSLAD8R).

7 These are administrative capacity limits.

8 Due to the power consumption of HG 1500, a UPSC-D must be used.

9 Due to the power consumption of HG 1500, a UPSC-DR must be used.

10 If the total number of UP0/E stations, analog stations and additional stations connected using an adapter is greater than 72,

an external power supply unit (Powerbox PB3000 with LUNA2) must be used.

11 4x analog T/R + 1xUP0/E + 7xBS/32xHiPath Cordless Office stations at the central board + 5xSLU8R or 5x8SLAR or

5xSLAD8R.

12 4xanalog T/R + 5xUP0/E + 3xBS/16xHiPath Cordless Office stations at the central board + 2x16SLA.

13 4x analog T/R + 5xUP0/E + 3xBS/16xHiPath Cordless Office stations at the central board + 2xSLU8R or 2x8SLAR or

2xSLAD8R.

14 4xanalog T/R at the central board + 5x8SLAR or 5xSLAD8R.

15 4xanalog T/R at the central board + 2x16SLA.16 4xanalog T/R at the central board + 2x8SLAR or 2xSLAD8R.

17 8xUP0/E at the central board + 5xSLU8 + 1xSLMO24.

18 8xUP0/E at the central board + 5xSLU8R.

19 8xUP0/E at the central board + 2xSLU8.


21 If the total number of UP0/E stations and additional stations connected using an adapter is greater than 24, UPSC-D/UPSC-

DR must be used.

22 Due to the 5-V power supply unit, one SLC16N and a maximum of two HG 1500 V3.0 boards can be used.

23 64 HiPath Cordless Office stations at the SLC16N or 32 HiPath Cordless Office stations at the central board.

24 The system may be configured with two HG 1500 boards if PDM1 is not used.






A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

Figure 2-1 HiPath 3800 with Basic and Expansion Cabinet

BC

approx. 440 mm

a p p r o x . 9 8 0 m m

Slot

approx. 430 mm






A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

Figure 2-3 HiPath 3800 - Slots in the Expansion Cabinet

N o t u s e d



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

2.2.2 Distribution of PCM Segments

HiPath 3800 provides PCM highway trunk groups, each with 2 x 4 PCM highways for the pe-ripheral board slots. There are approximately 32 time-division multiplex channels available for

each PCM highway. Blockages occur when these channels are busy. This prevents the systemfrom performing any more call jobs.

To guarantee that the system operates without blocking, make sure when performing configu-ration that the boards on a PCM segment do not require more than the number of time-divisionmultiplex channels available. The following figures show the PCM highways for both systemcabinets of the HiPath 3800.

Basic cabinet: PCM highways

The basic cabinet provides two PCM highway trunk groups, each with 2 x 4 PCM highways.There are approximately 32 time-division multiplex channels available for each PCM highway.

The basic cabinet’s PCM highway trunk groups are used by peripheral boards according to thefollowing rules:

● Single-cabinet system (basic cabinet only)With the exception of DIUT2, DIUN2, DIU2U (U.S. only) and STMI2 boards, peripheralboards only use the PCM highways of trunk group A:

– PCM segment for the board slots 1 – 5 = 128 time-division multiplex channels (4 PCMhighways)

Figure 2-4 HiPath 3800 - Basic Cabinet PCM Highways

Trunk group A’s PCM highwaywith 2 x 4 PCM highways

Trunk group F’s PCM highwaywith 2 x 4 PCM highways

HDLC




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

– PCM segment for the board slots 7 – 10 = 128 time-division multiplex channels (4 PCMhighways)

DIUT2, DIUN2, DIU2U (U.S. only) and STMI2 use the PCM highways of trunk group F. As

a result, an additional 128 time-division multiplex channels for slots 1 – 5 and slots 7 – 10are provided for these boards.If the installation of these boards necessitates a greater number of time-division multiplexchannels than the 2 x 128 available with trunk group F, the system automatically uses thetime-division multiplex channels available with trunk group A. However, only completeboards are switched to the other trunk group. The remaining time-division multiplex chan-nels are not used.

● Two-cabinet system (basic cabinet + expansion cabinet)All peripheral boards use only the PCM highways of trunk group A.

Expansion cabinet: PCM highways

The expansion cabinet provides a PCM highway trunk group with 2 x 4 PCM highways. Thereare approximately 32 time-division multiplex channels available for each PCM highway.

● PCM segment for the board slots 1 – 6 = 128 time-division multiplex channels (4 PCM high-ways)

● PCM segment for the board slots 8 – 14 = 128 time-division multiplex channels (4 PCMhighways)

Trunk group F’s PCM highway is not used.

Figure 2-5 HiPath 3800 - Expansion Cabinet PCM Highways

Trunk group A’s PCM highwaywith 2 x 4 PCM highways

Connection to PCM highwayTrunk group F of the basic cabinet

Trunk group F’s PCM highway(not in use)

HDLC connection to basic cabinetHDLC



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

Time-division multiplex channels for peripheral boards

The following table lists the maximum number of time-division multiplex channels required bythe different peripheral boards. A distinction is made here between:

● Static time-division multiplex channelsTime-division multiplex channels are assigned statically for trunk boards. This ensures thatall incoming calls can be processed.

● Dynamic time-division multiplex channelsTime-division multiplex channels are assigned dynamically for subscriber line modules.The channels are seized with every incoming call and released at the end of each call. Thismeans that the current number of required time-division multiplex channels depends on thenumber of active stations.

7Restrictions when using the TMDID boardThe TMDID board only uses the first half of a PCM segment, which means that upto 64 channels are available per PCM segment for TMDID static time-division multi-plex channels.To ensure non-blocking operation of the system when using the TMDID, the boardson a PCM segment must not require more than 64 static time-division multiplexchannels.Examples for a PCM segment:● 2 x TMDID + 1 x DIU2U = 64 static time-division multiplex channels = permissi-

ble configuration● 1 x TMDID + 1 x TMC16 + 1 x DIU2U = 72 static time-division multiplex channels

= impermissible configuration● 1 x TMDID + 2 x SLMO2 = 8 static and 96 dynamic time-division multiplex chan-

nels = permissible configuration

Table 2-2 Maximum Number of Time-Division Multiplex Channels Required per Board

Board Maximum Number of Time-DivisionMultiplex Channels Required

Assignment of Time-Divi-sion Multiplex Channels

DIU2U 48 Static

DIUN2 60 Static

DIUT2 60 Static

IVMN8 8 Dynamic

IVMNL 24 Dynamic

SLCN 1281 Dynamic

SLMA 24 Dynamic

SLMA8 8 Dynamic




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

SLMO2 482 Dynamic

SLMO8 162 Dynamic

STMD3 16 Static / dynamic3

STMI2 32 Dynamic

TM2LP 8 Static

TMC16 16 Static

TMDID 8 Static

TMEW2 4 Static

1 A time-division multiplex channel is required if a call is conducted via the "Home SLCN board" of a mobile telephone. If a

call is conducted via a "Location-dependent SLCN board", additional time-division multiplex channels are necessary.

2 The maximum possible number of masters and slaves is taken into account.

3 Static assignment of time-division multiplex channels when using as a trunk board, dynamic assignment when using as a

subscriber line module.

Table 2-2 Maximum Number of Time-Division Multiplex Channels Required per Board

Board Maximum Number of Time-DivisionMultiplex Channels Required

Assignment of Time-Divi-sion Multiplex Channels



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

2.2.3 Static Traffic Capacity

The static traffic capacity of the HiPath 3800 system can be determined as follows.

Table 2-3 HiPath 3800 - Static Traffic Capacity

HiPath 3800 Slots per PCM seg-ment

Static traffic capac-ity per PCM seg-

ment

Total static trafficcapacity of the

system

Single-cabinet sys-tem(see page 2-9)

1 – 5 128 erlangs +(128 erlangs1)

1 The basic cabinet provides two PCM highway trunk groups, each with 2 x 4 PCM highways. DIUT2, DIUN2, DIU2U

(U.S. only), IVMNL, IVMN8 and STMI2 use the PCM highways of trunk group F. As a result, an additional 128 time-

division multiplex channels for slots 1 – 5 and slots 7 – 10 in the basic cabinet are provided for these boards. If Hi-

Path 3800 is used as a two-cabinet system, the PCM highway for trunk group F cannot be used.

512 erlangs7 – 10 128 erlangs +

(128 erlangs1)

Two-cabinet system(see page 2-10)

1 – 5 128 erlangs

512 erlangs7 – 10 128 erlangs

11 – 16 128 erlangs

18 – 24 128 erlangs




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

2.2.4 Central Components

2.2.4.1 CBSAP

Introduction

The (Central Board Synergy Access Platform) board performs all central control and switchingfunctions for HiPath 3800.

Subboards

The following subboards can be used depending on the application:

● CMS clock module (optional)

● MMC multimedia card

● IMODN integrated modem card new (optional)

● LIMS LAN interface module (optional)Includes 2 Ethernet (10BaseT) LAN connections (8-pin RJ45 jacks):

– LAN1 (administration via HiPath 3000/5000 Manager E and CTI functions)

– LAN2 (not assigned)

● MPPI music on hold (optional)

V.24 interfaces (9-pin SUB-D connectors)

● Service (X50) = for connecting the service PC

● Application (X51) = for connecting a printer or application



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

2.2.4.2 LUNA2

Introduction

LUNA2 (Line-powered Unit for Network-based Architecture No. 2) is used as the central powersupply in HiPath 3800. Depending on the system configuration, up to three LUNA2 boards canbe used in the basic cabinet and up to four in the expansion cabinet.

When configuring the HiPath 3800 as a two-cabinet system, two LUNA2 boards in the basiccabinet and three in the expansion cabinet are sufficient to provide the specified maximum con-figuration limits. For information on how to calculate the number of LUNA2 modules required,see page 2-18.

You can use a third LUNA2 in the basic cabinet and a fourth in the expansion cabinet to ensureerror-free operation if one LUNA2 module fails (redundant LUNA2) or to charge a connected

battery pack or a Power Box PB3000 (with 4 batteries 12 V/7 Ah).

LUNA2 integrates the functions of power supply and battery management. No further compo-nents are required for permanent AC power supply operation. The following options are avail-able for emergency battery operation in the event of a power cut, i.e. the function UPS:

● Connection of battery packs 4 x 12 V/7 Ah (S30122-K5950-Y200) per system cabinet. Thebatteries are charged via the redundant LUNA2 in the respective system cabinet.

Note: Only the S30122-K5950-Y200 battery back is approved for use with LUNA2.

● Connecting the Power Box PB3000 with 4 batteries 12 V/7 Ah (4 x V39113-W5123-E891)per system cabinet. The batteries are charged via the redundant LUNA2 in the respectivesystem cabinet.Note: Only the V39113-W5123-E891 batteries are approved for use with thePower Box PB3000.

● Connecting the battery cabinet BSG 48/38 with the battery set 38 Ah/48 V and batterycharger per HiPath 3800 system.

● Connecting the Power Box PB3000 with 4 batteries 12 V/7 Ah (4 x V39113-W5123-E891)

and LUNA2 as battery charger per HiPath 3800 system.Note: Only the V39113-W5123-E891 batteries are approved for operation in the Power BoxPB3000.

LUNA2 is used in models for all countries.

>It is not possible to combine both LUNA2 operating modes redundant LUNA2 andbattery charger LUNA2.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

Part numbers

● LUNA2: S30122-K7686-A1, S30122-K7686-M1For production-related reasons, two different LUNA2 modules with the same functionality

are used. Technically identical, the two models have minor mechanical differences and arefully compatible with each other.

● Battery pack 4 x 12V/7Ah: S30122-K5950-Y200Weight (including batteries): 14.1 kgDimensions (length x width x height): 280 mm x 160 mm x 140 mm(The connecting cable for the LUNA2 is integrated with the battery pack.)

● BSG upright battery housing 48/38: S30122-K5950-F300 (page 2-17)

– Battery cable for BSG 48/38: C39195-Z7985-B10(One battery cable is required for each system cabinet to be connected.)

– Battery 12 V/38 Ah: S30122-X5950-F320(Four batteries necessary for each BSG 48/38.)

● Power Box PB3000 (Section 2.7, "Additional Power Supply by the Powerbox PB3000")

Technical Specifications

● Nominal voltage range: 110 VAC - 240 VAC

● Nominal frequency: 50 Hz - 60 Hz

● Output voltage (battery charging voltage, if a LUNA2 is used as a battery charger): – 54.7 VDC; –53.5 VDC (for gell cell batteries, currently not released)

● Output current (battery charge current, if a LUNA2 is used as a battery charger): max. 2 A

● Bridging times

– Table 2-4 lists the maximum possible bridging times (emergency battery operation incase of power failure) with battery pack S30122-K5950-Y200 ((48V/7Ah) and batteryhousing BSG 48/38 (S30122-K5950-F300).

– Power Box PB3000 (Section 2.7, "Additional Power Supply by the Powerbox PB3000")



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

BSG 48/38

You can use a BSG 48/38 battery cabinet in an upright housing instead of the battery pack toextend the bridging time in the event of a power failure. The BSG 48/38 battery cabinet(S30122-K5950-F300) consists of

● an upright housing

● a charging rectifier

● a battery set (38 Ah/48 V)

The battery cabinet is designed for direct connection to the HiPath 3800 communication sys-tem.

Table 2-4 LUNA2 - Bridging Times with Battery Pack 48 V/7 Ah and Upright BatteryHousing BSG 48/38

System Power supply unit Load levels Maximum bridg-ing time

HiPath 3800 2 x LUNA2 per system cabinet asPSU1 x LUNA2 per system cabinet asbattery charger1 x battery pack 48 V/7 Ah per sys-tem cabinet

60% nominalload

25 min

HiPath 3800 5 x LUNA2 boards per system1 x BSG upright battery housing

48/38 per system(LUNA2 is not required as a batterycharger as the BSG 48/38 batterycabinet features a built-in charger.)

60% nominalload

1 h 30 min

Measurement conditions:● All measurements were performed at a room temperature of approximately 22 °C

(71.6 °F).● The batteries were new and fully charged when measurement started.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

Calculating the number of LUNA2 modules required

Depending on the number and type of peripheral boards installed, the number of LUNA2boards required can be calculated using the following table.

Examples for a single-cabinet system:

a) Basic cabinet with CBSAP and peripheral boards (no STMI2, SLMA or SLCN)● A single LUNA2 can feed one CBSAP and up to four peripheral boards.

● A second LUNA2 is required for five or more peripheral boards.

● A third LUNA2 can be used as a battery charger or as a redundant LUNA2.

b) Basic cabinet with CBSAP and peripheral boards (with STMI2, SLMA and/or SLCN)

● Two LUNA2s are always required to supply a CBSAP, peripheral boards andSTMI2, SLMA and/or SLCN.

●

A third LUNA2 can be used as a battery charger or as a redundant LUNA2.

Table 2-5 Determining the Number of LUNA2 Boards Required per Cabinet

Number of peripheralboards per cabinet

STMI2, SLMA and/orSLCN available

Number ofLUNA2s required

per cabinet

Basic cabinet < 5 No 1

< 5 Yes 2

5 No 2

5 Yes 2

Expansion cabi-net

< 5 No 1

< 5 Yes 2

5 No 2

5 Yes 3

10 No 3

10 Yes 3



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

2.2.4.3 LIMS

The LAN Interface Module for SAPP LIMS (S30807-Q6721-X) is an optional plug-in card forthe CBSAP central control board in HiPath 3800.

The board provides two Ethernet (10BaseT) LAN connections via two 8-pin RJ45 jacks:

● LAN1 (administration via HiPath 3000/5000 Manager E and CTI functions)

● LAN2 (not assigned)

The LIMS module can be used for administration via HiPath 3000/5000 Manager E and for CTIfunctions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour CallAttempts = number of connection attempts during busy traffic hours) is restricted to 400 at amaximum of six TAPI ports. The use of "power dialers" is not approved.

You cannot operate the LIMS module and an STMI2 board simultaneously in a HiPath 3800.

2.2.4.4 CSAPE

The cPCI cassette CSAPE (Central Shelf Access Point Emergency) can be installed in the ba-sic cabinet in HiPath 3800 V6.0 or later. The cPCI cassette features two fan drawers, the ACpower supply ACPCI (part number S30124-X5166-X), and two slide-in shelves for the embed-ded application server (EAS).

CSAPE is required to operate HiPath All-in-One applications. For information on the applica-tions supported, refer to the product documentation for HiPath All-in-One.

The cPCI cassette CSAPE is only mechanically installed in the system, that is, there are noelectrical connections between the system and the cPCI cassette CSAPE. HiPath 3800 com-municates exclusively with HiPath All-in-One over the IP network.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

2.2.5 Peripheral Components

2.2.5.1 Subscriber Line Modules

Table 2-6 Subscriber Line Modules for HiPath 3800

BoardName

Capacity Coun-try

Type/Description

P o r t s p

e r b o a r d

B c h a n

n e l s p e r b o a r d

B o a r d s p e r c a b i n e t

M a x . n

u m b e r o f

b o a r d s

p e r s y s t e m

R O W

U S A

IVMN8 8 8 1 1 x x These boards enable the integrated voicemail func-tionality of HiPath Xpressions Compact.IVMNL 24 24 1 1 x x

SLCN 16 64 4 4 x SLCN board for connecting base stations to thesystem.

SLMA 24 x x Up to 24 analog telephones can be connected tothe system via the SLMA. In addition to telephones,

it is also possible to connect fax machines, mo-dems, radio paging equipment, equipment for exter-nal music on hold, and voicemail systems.For Australia only: The T/R interfaces supply a ringvoltage of 35 Veff. Depending on the terminals con-nected, we cannot exclude the possibility of errorsoccurring during ringing state.

SLMA8 8 x x Board with eight T/R interfaces For Australia only: The T/R interfaces supply a ringvoltage of 35 Veff. Depending on the terminals con-nected, we cannot exclude the possibility of errorsoccurring during ringing state.

SLMAE 24 x x Trunk board for analog stations, 24 ports

SLMAE8 8 x x Trunk board for analog stations, 8 ports

SLMAV8 8 x x The SLMAV boards provide analog T/R interfacesand replace the SLMAE, SLMAE8, SLMAE200,SLMA and SLMA8 boards.

SLMAV24 24 x x



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

SLMO2 24 48 x x This board is used to connect the optiPoint andOpenStage telephones. The SLMO board comes in8- and 24-port versions.SLMO8 8 16 x x

STMD3 8 16 6 8 x x Board for ISDN basic rate interface. Configurationof ISDN trunks, tie trunks, and stations on the sameboard is possible.There are two versions of this board:● S0 interfaces without power supply● S0 interfaces with power supply

STMI2 2 32 4 8 x x HG 1500 board for the direct connection of IP work-point clients.


BoardName

Capacity Coun-try

Type/Description

P o r t s p e r b o a r d

B c h a n n e l s p e r b o a r d


M a x . n u m b e r o f

b o a r d s p e r s y s t e m

R O W

U S A




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

2.2.5.2 Trunk Boards

Table 2-7 Trunk Boards for HiPath 3800

BoardName

Capacity Country

Type/Description






R O W

U . S .

TMCAS-2 2 60 3 x1 - Boards to support country-specific CAS (Channel As-sociated Signaling) protocols

DIUN2 60 60 3 x x Board for primary rate access. Can also be used for tietraffic.In HiPath 3000/HiPath 5000 V5.0 and later, the B chan-nels in the DIUN2 board must be licensed.

DIU2U 48 48 4 - x Boards for T1-PRI trunk connection (PRI: Primary RateInterface)

DIUT2 60/

48

60/

48

3/42 x x Boards for S2M trunk connection, T1-PRI (Primary

Rate Interface) trunk connection (only for USA) and T1analog trunk connection (only for USA).The B channels associated with the DIUT2 board re-quire a license.

STMD3 8 16 x - Board for ISDN basic rate interface. It is possible to mixconfiguration on the same card for ISDN trunk connec-tions, tie lines and stations.There are two versions of this board:● S0 interfaces without power supply● S0 interfaces with power supply

TMANI8 8 x x Analog trunk board that supports the CLIP function.

TMDID 8 - x Analog trunk board for direct inward dialing

TMDID2 8 x3 - Analog trunk board for direct inward dialing



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

2.2.5.3 Boards for Tie Trunk Traffic

TMC16 16 - x Analog trunk board (ground/loop start)

TM2LP 8 x x Board with 8 ports to connect LS trunk connectionsand enables CAS trunk connections

1 TMCAS-2: For selected countries only

2 DIUT2: Up to 3 DIUT2 and/or DIUN2 per system. Up to 4 DIUT2 and/or DIU2U per system when used as T1 trunk con-

nection.

3 TMDID2: For selected countries only

Table 2-8 Tie Trunk Traffic Boards for HiPath 3800

BoardName

Capacity Country

Type/Description






R O W

U . S .

DIUN2 60 60 3 x Board for primary rate access.In HiPath 3000/HiPath 5000 V5.0 and later, the B chan-nels in the DIUN2 board must be licensed.

DIUT2 60 60 3 x x Board for S2M networking.The B channels associated with the DIUT2 board re-quire a license.

TMEW2 4 x x Board for providing four two-way analog tie trunk cir-cuits with E&M signaling.


BoardName

Capacity Country

Type/Description






R O W

U . S .




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

Note on compatibility in E&M networks:

TMEW2 does not support E&M interface types 1, 1B, 2, 3 and 5 or the TIEL board.

STMD3 8 16 x x Board for ISDN basic rate interface. It is possible to mixconfiguration on the same card for ISDN trunk connec-tions, tie lines and stations.There are two versions of this board:● S0 interfaces without power supply● S0 interfaces with power supply

STMI2 2 32 4 8 x x HG 1500 board for connecting the HiPath 3800 systemdirectly to a local IP network (Ethernet).


BoardName

Capacity Country

Type/Description






R O W

U . S .



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3800

2.2.5.4 Options

Table 2-9 Optional Boards for HiPath 3800

BoardName

Capacity Coun-try

Type/Description

R O W

U S A

TMEW2 Ports perboard

4 x x In addition to its tie trunk circuit function, this board canalso be used for connecting announcement equipment(with start/stop signaling for announcement before an-swering).

REALS Relay con-

nections

4 x x The REALS board is located on the basic cabinet’s

backplane. It can be used for connecting relays (dooropener) and trunk switching (ALUM).Trunk fail-

ure trans-fers

1

PFT1 Trunk fail-ure trans-fers

1 x - PFT1 and PFT4 boards can be connected to the maindistribution unit (MDFU-E).They transfer calls from analog trunks to a telephonein a power failure (note the signaling method used).PFT4 Trunk fail-

ure trans-fers

4 x -

LIMS x x Ethernet (10BaseT) interface




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3800

2.2.6 Additional System Data

2.2.6.1 Energy Consumption Information

Chapter A, "Identifying System Power Requirement" contains information on the power require-ments of individual boards and components.

2.2.6.2 Specifications for the Uninterruptible Power Supply LUNA2

Refer to Section 2.2.4.2 for details on LUNA2.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3550

2.3 HiPath 3550

2.3.1 Hardware Overview

Structure

The HiPath 3550 housing intended for wall mounting contains one shelf with six slot levels. Theslot levels, numbered in ascending order from the attachment side, have the following assign-ments:

● Slot levels 1-3: peripheral boards (two slots per level)

● Slot level 4: CBCC control board only

● Slot level 6: optional boards (up to 5 modules)

The power supply unit is located on the back of the subrack.

The connecting cables to the peripherals (telephones, trunk connections) can be connected di-rectly.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3550

Dimensions and Slots

Figure 2-6 Dimensions and Slots in HiPath 3550

Mounting sur-face

460200

450

EB = Slot

Notes:● When mounting the system on the wall, plan for at least 30 cm of clearance

on the board side for replacing the boards.

Slot levels

S l o t 4

S l o t 5

S l o t 8

21 63 4 5

S l o t 9

S l o t 6

S l o t 7

C B C C

P E R I P H E R A L B O A R D

O P T I O N S



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3550


The HiPath 3550 system has the following static traffic capacities.


System Slots Static Traffic Ca-pacity

Total static traffic capacityof the system

HiPath 3550(see figure 2-6)

2 / 3 (CBCC) 24 erlangs

198 erlangs

4 16 erlangs

5 16 erlangs

6 16 erlangs

7 16 erlangs

8 16 erlangs

9 30 erlangs1

1 Use of a TS2 board results in a capacity of 30 erlangs. A maximum of one TS2 per HiPath 3550 is possible, and the board

may only be installed in slot 7 or 9, thus resulting in 30 erlangs for slot 7 or 9.

10 64 erlangs




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3550


2.3.3.1 CBCC

Introduction

The CBCC (Central Board with Coldfire Com) board performs all central control and switchingfunctions for HiPath 3550.

This description relates to the following outputs of the Central Control CBCC:

● CBCC S30810-Q2935-A401: Implemented from V6.0 Rel. 10 or later and V5.0 Rel. 15 orlaterMajor new functions:

– Integration of subboard LIM functionality – Increasing the ringing voltage of the subscriber interfaces (T/R) to approx. 65 V eff

– Removal of the second V.24 interface (option V24/1)

● CBCC S30810-Q2935-A301: Implemented in V5.0 and later:Major new function:CLIP

Subboards

The following subboards (some of which are optional) can be used depending on the applica-tion:

● Clock Module Small CMS [optional]

– supports all two-channel cordless connections to the HiPath 3550, HiPath 3350, Hi-Path 3500, and HiPath 3300 systems.

– supports all 4, 8 and 12-channel CMI connections using the SLC16 board of the Hi-Path 3550 system.

– provides the master clock for digital networking.

Section 2.8 contains additional information on when CMS is used.● Clock Module ADPCM (CMA) [optional]

– supports the four-channel CMI connection over a base station to the HiPath 3550, Hi-Path 3350, HiPath 3500, and HiPath 3300 systems.

– in the same way as the CMS clock module small, provides the master clock for digitalnetworking.

Section 2.8 contains additional information on when CMA is used.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3550

● MMC multimedia cardThis plug-in memory card contains the CDB backup and the version-specific APS. Pleasenote that the multimedia card (MMC) may only be replaced by another MMC approved bySiemens Enterprise Communications GmbH & Co. KG. Non-approved cards can possibly

have a different structure which can have an effect on access times and on some features(e.g. KDS backup and APS transfer).

● IMODN Integrated Modem Card New [optional]This plug-in card allows remote service (analog mode up to 33.6 Kbps), without having touse an external modem.

● MPPI (Music on Hold) [optional]

● Entry Voice Mail (EVM) [optional]

● LIM LAN interface module (option, only for CBCC S30810-Q2935-A301)

This subboard makes available an Ethernet (10BaseT/10 Mbps) LAN connection using an8-pin RJ45 jack (see Section 2.3.3.3).

Interfaces

● Ethernet (10BaseT/10 MBit)-LAN interface, only in CBCC S30810-Q2935-A401The LIM module can be used for administration via HiPath 3000/5000 Manager E and forCTI functions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (BusyHour Call Attempts = number of connection attempts during busy traffic hours) is restrictedto 400 at a maximum of six TAPI ports. The use of "power dialers" is not approved.

The Ethernet LAN interface is deactivated by the system software as soon as an HG 1500board is inserted.

● Eight digital UP0/E subscriber linesFor example, UP0/E workpoint clients or BS3/1 base stations for HiPath Cordless Office canbe connected here.

● Four analog a/b subscriber linesFor U.S. only: These interfaces do not support the connection of external extensions viaOPS (Off-Premises Station) signaling.CBCC S30810-Q2935-A401: The interfaces supply a ring voltage of appr. 65 Veff.CBCC S30810-Q2935-A301: The interfaces supply a ring voltage of appr. 35 Veff. De-

pending on the terminals connected, we cannot exclude the possibility of errors occurringduring ringing state.

● Two digital S0 interfaces (CO (default) or station)

● Backplane (CUC or CUP) connection via slots 1 (X11), 2 (X5) and 3 (X6)




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3550

● Music on hold: MPPI, EXM

● Options bus (O bus)

● V.24 interfaceCBCC S30810-Q2935-A301: A second V.24 interface can be implemented via the optionV24/1.

2.3.3.2 UPSC-D

Introduction

The UPSC-D (S30122-K5660-A300, S30122-K5660-M300) board is used in HiPath 3550 andHiPath 3350 (wall housing).

The board combines the functions of a power supply unit and battery manager. No further com-ponents are required for operation in AC power supply mode. To maintain short-term batteryemergency operation after a power failure, that is, to use uninterruptible power supply func-tions, you must also connect a battery pack.

If the power supplied by the UPSC-D is insufficient, an external power supply(Power Box PB3000 with LUNA2) can be installed to provide additional power. To do this, con-

nect the DC port on the PB3000 to the special –48 Vdc input on the UPSC-D. The UPSC-D’sinternal -48 V output is deactivated when the external power supply is connected. For emer-gency battery operation in the event of power failure, 4 x 12 V/7 Ah batteries (4 x V39113-W5123-E891) must be installed in the Powerbox PB3000.

>

Please note that only one MPPI module may be connected. In other words, youcan connect either MPPI S30122-K5380-X200 via X4 or MPPI S30122-K7275-

B via X19/X20.

7WarningThe UPSC-D power supply unit is only released for permanent AC power supply.

Permanent operation at a direct-current system is not allowed.A DC power supply unit is only connected to bridge an AC power failure (emergencybattery operation).If a 48-V direct-current system is being used instead of a battery pack for DC powersupply, connection must be performed as for a battery pack. The 48-V direct-currentsystem must not exceed the limit of 60 V in operating mode, during loading, andwhen an error occurs. The direct-current system must not be connected to theUPSC-D if this cannot be guaranteed.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3550

Licensed battery pack for UPSC-D

S30122-K5928-X (48 V (4 x 12 V)/1.2 Ah battery pack)This is the only battery pack released for connection to UPSC-D.




● Ring voltage generator 75 VAC, 20/25/50 Hz

● Partial voltages: +5 Vdc, –48 V

● Battery charger: 4 x 12 V (40.8 V-55.2 V)

● Power consumption: 180 W

● Bridging timesTable 2-11 lists the maximum possible bridging times (emergency battery operation in caseof power failure) with the battery pack (48 V/1.2 Ah) and Powerbox PB3000 (S30177-U773-X), depending on the system.

7DangerDo not use 24-V batteries (S30122-K5403-X) in conjunction with UPSC-D as an ex-plosive gas (hydrogen + oxygen) escapes when the battery is overloaded.

Table 2-11 UPSC-D - Bridging Times with Battery Pack S30122-K5928-X (48 V/ 1.2 Ah) and Powerbox PB3000


HiPath 3350 UPSC-D48-V/1.2-Ah battery pack

Normal output load =5 V: 3 A; –48 V: 0.5 A;ringing approx. 2 VA

19 min

HiPath 3350 UPSC-DPowerbox PB3000with 1 x LUNA2 and4 x 12-V/7-Ah batteries


3 h


Normal output load 100 % =5 V: 8 A; –48 V: 1.1 A;ringing approx. 4 VA

6 min


Normal output load 60 % =5 V: 4.8 A; –48 V: 0.66 A;ringing approx. 2 VA

15 min




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3550

2.3.3.3 LIM

The LAN Interface Module (LIM - S30807-Q6930-X) is an optional plug-in card for all HiPath3000 central control boards (see also Section 4.4).

The board provides an Ethernet (10BaseT/10 Mbps) LAN connection via an 8-pin RJ45 jack.

The LIM module can be used for administration via HiPath 3000/5000 Manager E and for CTIfunctions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour CallAttempts = number of connection attempts during busy traffic hours) is restricted to 400 at a

maximum of six TAPI ports. The use of "power dialers" is not approved.You cannot operate the LIM module and a HG 1500 board simultaneously in one system.

HiPath 3550 UPSC-DPowerbox PB3000with 1 x LUNA2 and4 x 12-V/7-Ah batteries


2h 30min


(73.4°F).● The batteries were fully charged when the measurement was started.

Table 2-11 UPSC-D - Bridging Times with Battery Pack S30122-K5928-X (48 V/ 1.2 Ah) and Powerbox PB3000

System Power supply unit Load levels Maximum bridg-

ing time



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3550




BoardName

Capacity Country

Type/Description

P o r t s p

e r b o a r d

B c h a n


M a x . n

u m b e r o f

b o a r d s

p e r s y s t e m

R O W

U . S .

4SLA 4 #1

1 The maximum number is calculated on the basis of the system-specific capacity limits, See Section 2.1, "System-Related

Capacity Limits".

x - Board for connecting analog stations (a/b, T/R)

8SLA 8 #1 x x Board for connecting analog stations (a/b, T/R)

16SLA 16 #1 x - Board for connecting analog stations (a/b, T/R)

HXGS3 2 8 3 x x HG 1500 board for the direct connection of IP workpoint cli-ents.

IVMS8 8 8 1 x x Board for the integrated voice mail functions in HiPath

Xpressions Compact.IVMS8N 8 8 1 x x Board for the integrated voicemail functions in HiPath Xpres-

sions Compact (8 ports).

IVMP4 4 4 1 x x Board for the integrated voicemail functions in HiPath Xpres-sions Compact (4 ports).

SLAD4 4 #1 x x Board for connecting analog stations (a/b, T/R)



SLU8 8 16 #1 x x Board for connecting telephones with the UP0/E

interface(TDM)

STLS2 2 4 #1 x - Board for providing ISDN basic rate access.Configuration of ISDN trunks, tie trunks, and subscribers(no feeding) on the same board is possible.

STLS4 4 8 #1 x x




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3550



BoardName

Capacity Coun-try

Type/Description





R O W

U S A

TCAS-2 2 601

1 TCAS-2 provides two E1 CAS interfaces which, combined, can support up to 60 B channels. As HiPath 3550 supports a

maximum of 30 B channels, a total of up to 30 B channels may be used.

1 x2

2 For selected countries only

- Board for supporting country-specificCAS (Channel Associated Signaling) protocols

TLA 2 #3


Capacity Limits".

x - Trunk board for analog lines

TLA4 4 #3 x - Trunk board for analog lines

TLANI2 2 #3 x x Trunk board for analog lines including ALUM



TLA8 8 #3 x - Trunk board for analog lines

TS2 30 30 1 x - Board for primary rate access; can be used for tie trunktraffic.In HiPath 3000/5000 V5.0 and later, the B channels inthe TS2 board are subject to license. Consequently, theTS2 boards (S30810-Q2913-X300) have been assigneda new hardware identification code. The new code pre-vents the board from being used in earlier versions.Functionality and layout of the board have not beenchanged.

STLS2 2 4 #3 x - Board for ISDN basic rate access.Configuration of ISDN trunks, tie trunks, and stations (nofeeding) on the same board is possible.STLS4 4 8 #

3

x x

TST1 1 24 1 - x PRI board

TMGL4 4 #3 - x Trunk board for analog lines

TMQ4 4 8 #3 - x BRI board



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3550



BoardName

Capacity Coun-try

Type/Description





R O W

U S A

HXGS3 2 8 3 x x HG 1500 board for connecting the HiPath 3550 system di-rectly to a local data network (Ethernet).

STLS2 2 4 #1


Capacity Limits".

x - Board for ISDN basic rate access.Configuration of ISDN trunks, tie trunks, and stations (nofeeding) on the same board is possible.

STLS4 4 8 #1 x x

TS2 30 30 1 x - Board for primary rate access; can be used for tie trunktraffic.In HiPath 3000/5000 V5.0 and later, the B channels in theTS2 board are subject to license. Consequently, the TS2

boards (S30810-Q2913-X300) have been assigned a newhardware identification code. The new code prevents theboard from being used in earlier versions. Functionalityand layout of the board have not been changed.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3550

2.3.4.4 Options


BoardName

Capacity Coun-try

Type/Description

R O W

U S A

ALUM4 Trunk failuretransfers

4 x x Trunk failure transfer lets you transfer loop starttrunks directly to internal analog stations in theevent of a power failure (note the signaling methodused).

ANI4 Analog

trunks

4 - x This board allows calling line identification (caller

ID) in conjunction with TMGL4.GEE12 Number of call

charge receiv-ers

4 x - This optional board records the country-specificcall charge pulses (12 kHz) from the trunk.

GEE16 Number of callcharge receiv-ers



4 x - This optional board records the country-specificcall charge pulses (50 Hz) from the trunk.

V24/1 1 x x One serial V.24 interface for connecting a PC,printer, or Plus Products.

STBG4 x - Current-limiting module for LS interface (Franceonly)

EXM 1 x - External music on hold

EXMNA Ports 1 - x External music on hold (A-LAW)

MPPI x - Music on hold (MOH)

UAM x - Announcement before answering/music on hold/

relay/sensorSTRB Sensors 4 x x Control relay module; provides 4 relays and 4 sen-

sors for controlling external devices or detectingexternal control events.

Relay 4






A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3350

2.4 HiPath 3350


The HiPath 3350 housing intended for wall mounting contains one shelf with three slot levels.The slot levels, numbered in ascending order from the attachment side, have the following as-signments:

● Slot level 1: peripheral boards (two slots)

● Slot level 2: CBCC control board only



The HiPath 3350 does not need an external main distribution frame; the connecting to the pe-ripherals (such as telephones or trunks) connect directly to the boards.



21

Slot levels3

C B

C C

S l o t 4

S l o t 5

O P T I O

N S

Mountingsurface

460

450

128

EB = Slot

Note:When mounting the system on the wall, plan for at least 30 cm of clearance onthe board side for replacing the boards.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3350







2 / 3 (CBCC) 24 erlangs

56 erlangs4 16 erlangs

5 16 erlangs




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3350


2.4.3.1 CBCC

Introduction

The CBCC (Central Board with Coldfire Com) board performs all central control and switchingfunctions for HiPath 3550.

This description relates to the following outputs of the Central Control CBCC:

● CBCC S30810-Q2935-A401: Implemented from V6.0 Rel. 10 or later and V5.0 Rel. 15 orlaterMajor new functions:


– Removal of the second V.24 interface (option V24/1)

● CBCC S30810-Q2935-A301: Implemented in V5.0 and later:Major new function:CLIP

Subboards




– supports all 4, 8 and 12-channel CMI connections using the SLC16 board of the Hi-Path 3550 system.


Section 2.8 contains additional information on when CMS is used.● Clock Module ADPCM (CMA) [optional]

– supports the four-channel CMI connection over a base station to the HiPath 3550, Hi-Path 3350, HiPath 3500, and HiPath 3300 systems.

– in the same way as the CMS clock module small, provides the master clock for digitalnetworking.




3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3350

● MMC multimedia cardThis plug-in memory card contains the CDB backup and the version-specific APS. Pleasenote that the multimedia card (MMC) may only be replaced by another MMC approved bySiemens Enterprise Communications GmbH & Co. KG. Non-approved cards can possibly

have a different structure which can have an effect on access times and on some features(e.g. KDS backup and APS transfer).




● LIM LAN interface module (option, only for CBCC S30810-Q2935-A301)

This subboard makes available an Ethernet (10BaseT/10 Mbps) LAN connection using an8-pin RJ45 jack (see Section 2.3.3.3).

Interfaces

● Ethernet (10BaseT/10 MBit)-LAN interface, only in CBCC S30810-Q2935-A401The LIM module can be used for administration via HiPath 3000/5000 Manager E and forCTI functions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (BusyHour Call Attempts = number of connection attempts during busy traffic hours) is restrictedto 400 at a maximum of six TAPI ports. The use of "power dialers" is not approved.


● Eight digital UP0/E subscriber linesFor example, UP0/E workpoint clients or BS3/1 base stations for HiPath Cordless Office canbe connected here.

● Four analog a/b subscriber linesFor U.S. only: These interfaces do not support the connection of external extensions viaOPS (Off-Premises Station) signaling.CBCC S30810-Q2935-A401: The interfaces supply a ring voltage of appr. 65 Veff.CBCC S30810-Q2935-A301: The interfaces supply a ring voltage of appr. 35 Veff. De-

pending on the terminals connected, we cannot exclude the possibility of errors occurringduring ringing state.

● Two digital S0 interfaces (CO (default) or station)

● Backplane (CUC or CUP) connection via slots 1 (X11), 2 (X5) and 3 (X6)

● Music on hold: MPPI, EXM




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3350


● V.24 interfaceCBCC S30810-Q2935-A301: A second V.24 interface can be implemented via the optionV24/1.

2.4.3.2 PSUP

The power supply point PSUP is intended for use in HiPath 3350. The device plugs into a spe-cial slot and is secured by screws. It connects to the power outlet using a modular power cord.

A monitoring LED indicates the presence of the 5 V output voltage.




● Ring generator: 75 VAC, 20/25/50 Hz



2.4.3.3 UPSC-D

Introduction

This board combines the power supply and battery management functions. No other compo-nents are required if operated as a power supply. To maintain short-term battery emergencyoperation after a power failure, that is, to use uninterruptible power supply functions, you mustalso connect a battery pack.




● Ring generator: 75 VAC, 20/25/50 Hz



>Please note that only one MPPI module may be connected. In other words, youcan connect either MPPI S30122-K5380-X200 via X4 or MPPI S30122-K7275-B via X19/X20.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3350

● Power consumption: approx. 90 W

● Bridging timesThe following table lists the maximum bridging times (battery operation in case of power

failure) available with the battery pack S30122-K5928-X (48 V/1.2 Ah).

2.4.3.4 LIM



The LIM module can be used for administration via HiPath 3000/5000 Manager E and for CTI

functions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour CallAttempts = number of connection attempts during busy traffic hours) is restricted to 400 at amaximum of six TAPI ports. The use of "power dialers" is not approved.

You cannot operate the LIM module and a HG 1500 board simultaneously in one system.

Table 2-17 UPSC-D - Bridging Times with Battery Pack S30122-K5928-X (48 V/ 1.2 Ah)

System Power sup-ply unit

Load levels Maximum bridg-ing time

HiPath 3350 UPSC-D Normal output load = 5 V/3 A; –48 V/0.5 A; ringing approx. 2 VA

19 min


(73.4°F).● The batteries were fully charged when the measurement was started.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3350




BoardName

Capacity Coun-try

Type/Description

P o r t s p

e r b o a r d

B c h a n


M a x . n

u m b e r o f

b o a r d s

p e r s y s t e m

R O W

U S A

4SLA 4 2 x - Board for connecting analog stations (a/b, T/R)

8SLA 8 2 x x Board for connecting analog stations (a/b, T/R)

16SLA 16 2 x - Board for connecting analog stations (a/b, T/R)

HXGS3 2 8 1(21)


x x HG 1500 board for the direct connection of IP workpointclients.

IVMP4 4 4 1 x x Board for the integrated voicemail functions in HiPath

Xpressions Compact (4 ports).IVMP8 8 8 1 x - Board for the integrated voicemail functions in HiPath

Xpressions Compact (8 ports).

IVMS8 8 8 1 x x Board for the integrated voicemail functions in HiPathXpressions Compact (8 ports).

IVMS8N 8 8 1 x x Board for the integrated voicemail functions in HiPathXpressions Compact (8 ports).

SLAD4 4 2 x x Board for connecting analog stations (a/b, T/R)

SLAD8 8 2 x x Board for connecting analog stations (a/b, T/R)

SLU8 8 16 2 x x Board for connecting telephones with the UP0/E interface(TDM)

STLS2 2 4 2 x - Board for ISDN basic rate access.Configuration of ISDN trunks, tie trunks, and stations (nofeeding) on the same board is possible.

STLS4 4 8 2 x x



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3350



BoardName

Capacity Coun-try

Type/Description





R O W

U S A

TLA2 2 2 x - Trunk board for analog lines



TLANI2 2 2 x x Trunk board for analog lines including ALUM



STLS2 2 4 2 x - Board for ISDN basic access. Permits configuration ofISDN trunks, tie trunks, and subscribers (no feeding) on

the same board.STLS4 4 8 1 x x

TMGL4 4 2 - x Board for connecting analog trunks

TMQ4 4 8 2 - x BRI board




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3350


2.4.4.4 Options


BoardName

Capacity Coun-try

Type/Description





R O W

U S A

HXGS3 2 8 1(21)


x x HG 1500 board for connecting the HiPath 3350 systemdirectly to a local data network (Ethernet).

STLS2 2 4 2 x - Board for ISDN basic rate access. Configuration of ISDNtrunks, tie trunks, and stations (no feeding) on the sameboard is possible.

STLS4 4 8 1 x x


BoardName

Capacity Coun-try

Type/Description

R O W

U S A

ALUM4 Trunk failuretransfers

4 x x Trunk failure transfer; this board transfers loop starttrunks directly to internal analog stations in theevent of a power failure (note the signaling methodused).

ANI4 Analog trunks 4 - x This board allows calling line identification (callerID) in conjunction with TMGL4.







3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3350


4 x - This optional board records the country-specificcall charge pulses (50 Hz) from the trunk.

V24/1 Interfaces 1 x x Serial V.24 interface for connecting a PC, printer, orPlus Products

STBG4 x - Current-limiting module for LS interface (Franceonly)

EXM x - External music on hold

EXMNA - x External music on hold (A-LAW)


UAM x - Announcement before answering/music on hold/ relay/sensor

STRB Sensors 4 x x Control relay module; provides 4 relays and 4 sen-sors for controlling external devices or detectingexternal control events.

Relay 4


BoardName

Capacity Coun-try

Type/Description

R O W

U S A




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3350


2.4.5.1 Heat Dissipation and Power Consumption

Figure 2-9 Heat Dissipation and Power Consumption in a HiPath 3350 with PSUP/UP-SC-D

Appendix A, “Identifying System Power Requirement” contains information on the power re-quirements of individual boards and components.

2.4.5.2 Specifications for the Uninterruptible Power Supply

Refer to Section 2.4.3.3 for details on the UPSC-D.

88-264 V ac

● approx. 140 kJ/hfor op. with PSUP

● approx. 180 kJ/hfor op. withUPSC-D

Max. heat dissipation:

max. approx. 90 W

HiPath 3350







3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3500


2.5.3.1 CBRC

Introduction

The CBRC (Central Board Rack with Coldfire Com) board performs all central control andswitching functions for HiPath 3300.

This description relates to the following versions of the Central Control CBRC:

● CBRC S30810-Q2935-Z401: Implemented from V6.0 Rel. 10 or later and V5.0 Rel. 15 orlaterMajor new functions:


● CBRC S30810-Q2935-Z301: Implemented in V5.0 and later:Major new function:CLIP

Subboards





Section 2.8 contains additional information on when CMS is used.

● Clock Module ADPCM (CMA) [optional]

– supports the four-channel CMI connection over a base station to the HiPath 3550, Hi-

Path 3350, HiPath 3500, and HiPath 3300 systems. – in the same way as the CMS clock module small, provides the master clock for digital

networking.


● MMC multimedia cardThis plug-in memory card contains the CDB backup and the version-specific APS. Pleasenote that the multimedia card (MMC) may only be replaced by another MMC approved by




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3500

Siemens Enterprise Communications GmbH & Co. KG. Non-approved cards can possiblyhave a different structure which can have an effect on access times and on some features(e.g. KDS backup and APS transfer).




● LIM LAN interface module [option, only for CBRC S30810-Q2935-Z301]This subboard makes available an Ethernet (10BaseT/10 Mbps) LAN connection using an8-pin RJ45 jack (see Section 2.6.3.3).

Interfaces

● Ethernet (10BaseT/10 MBit)-LAN interface, only in CBRC S30810-Q2935-Z401The LIM module can be used for administration via HiPath 3000/5000 Manager E and forCTI functions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (BusyHour Call Attempts = number of connection attempts during busy traffic hours) is restrictedto 400 at a maximum of six TAPI ports. The use of "power dialers" is not approved.


● Eight digital UP0/E subscriber lines

For example, UP0/E workpoint clients or BS3/1 base stations for HiPath Cordless Office canbe connected here.

● Four analog a/b subscriber linesFor U.S. only: These interfaces do not support the connection of external extensions viaOPS (Off-Premises Station) signaling.CBRC S30810-Q2935-Z401: The interfaces supply a ring voltage of appr. 65 Veff.CBRC S30810-Q2935-Z301: The interfaces supply a ring voltage of appr. 35 Veff. De-pending on the terminals connected, we cannot exclude the possibility of errors occurringduring ringing state.

● Two digital S0 interfaces (CO (default) or station)● Backplane (CUCR or CUPR) connection via slots 1 (X11), 2 (X5) and 3 (X6)

● Music on hold: MPPI, EXMR


● V.24 interface



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3500

2.5.3.2 TUPSC-DR

Introduction

he UPSC-DR (S30122-K7373-M900, S30122-K7373-A900) board is used in HiPath 3500 andHiPath 3300 (19" housing).

The board combines the functions of a power supply unit and battery manager. No further com-ponents are required for operation in AC power supply mode. To maintain short-term batteryemergency operation after a power failure, that is, to use uninterruptible power supply func-tions, you must also connect the powerbox PB3000.

If the power supplied by the UPSC-DR is insufficient, an external power supply(Power Box PB3000 with LUNA2) can be installed to provide additional power. To do this, con-nect the DC port on the PB3000 to the special –48 Vdc input on the UPSC-DR. The UPSC-

DR’s internal -48 V output is deactivated when the external power supply is connected. Foremergency battery operation in the event of power failure, 4 x 12 V/7 Ah batteries (4 x V39113-W5123-E891) must be installed in the Powerbox PB3000.

7WarningThe UPSC-DR power supply unit is only released for permanent AC power supply.Permanent operation at a direct-current system is not allowed.

A DC power supply unit is only connected to bridge an AC power failure (emergencybattery operation).If a 48-V direct-current system is being used instead of a battery pack for DC powersupply, connection must be performed as for a battery pack. The 48-V direct-currentsystem must not exceed the limit of 60 V in operating mode, during loading, andwhen an error occurs. The direct-current system must not be connected to theUPSC-DR if this cannot be guaranteed!

7DangerThe UPSC-DR board is not insulated.

Consequently, a system using a UPSC-DR may only be operated with a closedhousing.Before opening the housing, make sure that the system is de-energized as follows:● by disconnecting the battery voltage and line voltage at any connected PB3000● by disconnecting the line cord attached to any connected batteries (PB3000).● by disconnecting the line cord attached to any connected PB3000.● by disconnecting the power plug.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3500

Licensed batteries for UPSC-DR

4 x V39113-W5123-E891 (4 x 12 V/7 Ah batteries)These are the only batteries released for connection to UPSC-DR and installation in Powerbox

PB3000.




● Ring voltage generator 75 VAC, 20/25/50 Hz




● Bridging timesTable 2-23 lists the maximum possible bridging times (emergency battery operation in caseof power failure) with four batteries (4 x 12-V/7-Ah batteries) and Powerbox PB3000(S30177-U773-X), depending on the system.

7DangerDo not use 24-V batteries (S30122-K5403-X) in conjunction with UPSC-DR as anexplosive gas (hydrogen + oxygen) escapes when the battery is overloaded.

Table 2-23 UPSC-DR - Bridging Times with Four Batteries V39113-W5123-E891(4 x 12 V/7 Ah Batteries and Power Box PB3000)


HiPath 3300 UPSC-DR4 x 12-V/7-Ah batteries


3 h

HiPath 3300 UPSC-DRPowerbox PB3000with 1 x LUNA2 and4 x 12-V/7-Ah batteries


3 h

HiPath 3500 UPSC-DR4 x 12-V/7-Ah batteries


1h 30min



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3500

2.5.3.3 LIM



The LIM module can be used for administration via HiPath 3000/5000 Manager E and for CTIfunctions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour CallAttempts = number of connection attempts during busy traffic hours) is restricted to 400 at amaximum of six TAPI ports. The use of "power dialers" is not approved.


HiPath 3500 UPSC-DR4x 12-V/7-Ah batteries


2h 20min

HiPath 3500 UPSC-DRPowerbox PB3000with 1 x LUNA2 and4 x 12-V/7-Ah batteries


1h 30min


(73.4 °F).● The batteries were fully charged when the measurement was started.

Table 2-23 UPSC-DR - Bridging Times with Four Batteries V39113-W5123-E891(4 x 12 V/7 Ah Batteries and Power Box PB3000)

System Power supply unit Load levels Maximum bridg-

ing time




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3500




BoardName

Capacity Coun-try

Type/Description

P o r t s p

e r b o a r d

B c h a n


M a x . n

u m b e r o f

b o a r d s

p e r s y s t e m

R O W

U S A

8SLAR 8 #1


Capacity Limits".

x x Board for connecting analog stations (a/b, T/R)

HXGR3 2 8 3 x x HG 1500 board for the direct connection of IP workpointclients.

IVMS8NR 8 8 1 x x Board for the integrated voicemail functions in HiPathXpressions Compact (8 ports).

IVMS8R 8 8 1 x x Board for the integrated voicemail functions in HiPath

Xpressions Compact (8 ports).IVMP4R 4 4 1 x x Board for the integrated voicemail functions in HiPath

Xpressions Compact (4 ports).

SLAD8R 8 #1 x x Board for connecting analog stations (a/b, T/R)

SLU8R 8 16 #1 x x Board for connecting telephones with the UP0/E interface(TDM)

STLS4R 4 8 #1 x x Board for ISDN basic rate access.Configuration of ISDN trunks, tie trunks, and stations (nofeeding) on the same board is possible.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3500



BoardName

Capacity Coun-try

Type/Description





R O W

U S A

TCASR-2 2 601

1 TCASR-2 provides two E1 CAS interfaces which, combined, can support up to 60 B channels.

As HiPath 3500 supports a maximum of 30 B channels, a total of up to 30 B channels may be used.

1 x2

2 For selected countries only

- Board for supporting country-specificCAS (Channel Associated Signaling) protocols

STLS4R 4 8 #3


Capacity Limits".

x x Board for ISDN basic rate access. Configuration of ISDNtrunks, tie trunks, and stations (no feeding) on the sameboard is possible.

TLA4R 4 #3 x - Trunk board for analog lines including ALUM and call me-tering receiving equipment board

TLANI4R 4 #3 x x Trunk board for analog lines including ALUM

TMGL4R 4 #3 - x Trunk board for analog lines

TS2R 30 30 1 x - In HiPath 3000/5000 V5.0 and later, the B channels in theTS2R board are subject to license. Consequently, theTS2R board S30810-K2913-Z300 has been assigned anew hardware identification code. The new code pre-vents the board from being used in earlier versions.Functionality and layout of the board have not beenchanged.

TST1 1 24 1 - x PRI board




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3500


2.5.4.4 Options


BoardName

Capacity Coun-try

Type/Description





R O W

U S A

HXGR3 2 8 3 x x HG 1500 board for connecting the HiPath 3500 systemdirectly to a local data network (Ethernet).

TS2R 30 30 1 x - In HiPath 3000/5000 V5.0 and later, the B channels in theTS2R board are subject to license. Consequently, theTS2R board S30810-K2913-Z300 has been assigned anew hardware identification code. The new code pre-vents the board from being used in earlier versions.Functionality and layout of the board have not beenchanged.


BoardName

Capacity Coun-try

Type/Description

R O W

U S A

ANI4R Analog

trunks

4 - x This board allows calling line identification (caller

ID) in conjunction with TMGL4R.EXMR x x External music on hold


UAMR x - Announcement before answering/music on hold/re-lay/sensor

STRBR Sensors 4 x x Control relay module; provides 4 relays and 4 sen-sors for controlling external devices or detecting ex-ternal control events.

Relay 4



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3500



Figure 2-11 Heat Dissipation and Power Consumption in a HiPath 3500



Refer to Section 2.5.3.2 for details on the UPSC-DR.

88-264 V ac

Max. heat dissipation:approx. 180 kJ/h

max. approx. 90 W

HiPath 3500




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3300

2.6 HiPath 3300


Structure

The HiPath 3300 housing intended for use with 19’ cabinets contains three slot levels with thefollowing assignments:

● Slot level 1: slide-in shelves for two peripheral boards

● Slot level 2: slide-in shelf for CBRC control board



The connection to peripherals (telephones, trunks, and others) is set up using MW8 jacks in thefront panels of the boards.



80 mm

440 mm 3 8 0 m

m

Slot 4 Slot 5

Slots 1-3

Slot levels

Necessary height units for 19“ cabinet assembly: 2(one height unit corresponds to approx. 1.7“ = 43 mm)

3 (options)

2 (CBRC)

1 (peripheral boards)



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3300







2 / 3 (CBRC) 24 erlangs

56 erlangs4 16 erlangs

5 16 erlangs




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3300


2.6.3.1 CBRC

Introduction

The CBRC (Central Board Rack with Coldfire Com) board performs all central control andswitching functions for HiPath 3300.

This description relates to the following versions of the Central Control CBRC:

● CBRC S30810-Q2935-Z401: Implemented from V6.0 Rel. 10 or later and V5.0 Rel. 15 orlaterMajor new functions:


● CBRC S30810-Q2935-Z301: Implemented in V5.0 and later:Major new function:CLIP

Subboards





Section 2.8 contains additional information on when CMS is used.

● Clock Module ADPCM (CMA) [optional]

– supports the four-channel CMI connection over a base station to the HiPath 3550, Hi-

Path 3350, HiPath 3500, and HiPath 3300 systems. – in the same way as the CMS clock module small, provides the master clock for digital

networking.


● MMC multimedia cardThis plug-in memory card contains the CDB backup and the version-specific APS. Pleasenote that the multimedia card (MMC) may only be replaced by another MMC approved by



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3300

Siemens Enterprise Communications GmbH & Co. KG. Non-approved cards can possiblyhave a different structure which can have an effect on access times and on some features(e.g. KDS backup and APS transfer).




● LIM LAN interface module [option, only for CBRC S30810-Q2935-Z301]This subboard makes available an Ethernet (10BaseT/10 Mbps) LAN connection using an8-pin RJ45 jack (see Section 2.6.3.3).

Interfaces

● Ethernet (10BaseT/10 MBit)-LAN interface, only in CBRC S30810-Q2935-Z401The LIM module can be used for administration via HiPath 3000/5000 Manager E and forCTI functions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (BusyHour Call Attempts = number of connection attempts during busy traffic hours) is restrictedto 400 at a maximum of six TAPI ports. The use of "power dialers" is not approved.


● Eight digital UP0/E subscriber lines

For example, UP0/E workpoint clients or BS3/1 base stations for HiPath Cordless Office canbe connected here.

● Four analog a/b subscriber linesFor U.S. only: These interfaces do not support the connection of external extensions viaOPS (Off-Premises Station) signaling.CBRC S30810-Q2935-Z401: The interfaces supply a ring voltage of appr. 65 Veff.CBRC S30810-Q2935-Z301: The interfaces supply a ring voltage of appr. 35 Veff. De-pending on the terminals connected, we cannot exclude the possibility of errors occurringduring ringing state.

● Two digital S0 interfaces (CO (default) or station)● Backplane (CUCR or CUPR) connection via slots 1 (X11), 2 (X5) and 3 (X6)

● Music on hold: MPPI, EXMR


● V.24 interface





3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3300

2.6.3.3 LIM



The LIM module can be used for administration via HiPath 3000/5000 Manager E and for CTIfunctions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour CallAttempts = number of connection attempts during busy traffic hours) is restricted to 400 at amaximum of six TAPI ports. The use of "power dialers" is not approved.





A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3300




BoardName

Capacity Coun-try

Type/Description

P o r t s p

e r b o a r d

B c h a n


M a x . n

u m b e r o f

b o a r d s

p e r s y s t e m

R O W

U S A

8SLAR 8 2 x x Board for connecting analog stations (a/b, T/R)

HXGR3 2 8 1(21)


x x HG 1500 board for the direct connection of IP workpointclients.

IVMP4R 4 4 1 x x These boards are for the integrated voicemail functionsin HiPath Xpressions Compact (4 ports).

IVMP8R 8 8 1 x x These boards are for the integrated voicemail functions

in HiPath Xpressions Compact (8 ports).IVMS8NR 8 8 1 x x These boards are for the integrated voicemail functions

in HiPath Xpressions Compact (8 ports).

IVMS8R 8 8 1 x x These boards are for the integrated voicemail functionsof HiPath Xpressions Compact.

SLAD8R 8 2 x x Board for connecting analog stations (a/b, T/R)

SLU8R 8 16 2 x x Board for connecting telephones with the UP0/E interface(TDM)

STLS4R 4 8 2 x x Board for ISDN basic rate access.

Configuration of ISDN trunks, tie trunks, and stations (nofeeding) on the same board is possible.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 3300




BoardName

Capacity Coun-try

Type/Description





R O W

U S A

TLA4R 4 2 x - Trunk board for analog lines including ALUM and call me-tering receiving equipment board

TLANI4R 4 2 x - Trunk board for analog lines including ALUM

TMGL4R 4 2 - x Trunk board for analog lines

STLS4R 4 8 2 x x Board for ISDN basic rate access. Configuration of ISDNtrunks, tie trunks, and stations (no feeding) on the sameboard is possible.


BoardName

Capacity Coun-try

Type/Description

P o r t s p e

r b o a r d

B c h a n n

e l s p e r b o a r d


b o a r d s p

e r s y s t e m

R O W

U S A

HXGR3 2 8 1(21)


x x HG 1500 board for connecting the HiPath 3300 systemdirectly to a local data network (Ethernet).




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

HiPath 3300

2.6.4.4 Options



Figure 2-13 Heat Dissipation and Power Consumption in a HiPath 3300



Refer to Section 2.6.3.2 for details on the UPSC-DR.


BoardName

Capacity Country Type/Description

R O W

U S A

ANI4R Analogtrunks

4 - x This board allows calling line identification (callerID) in conjunction with TMGL4R.

EXMR x x External music on hold


UAMR x - Announcement before answering/music on hold/re-lay/sensor

STRBR Sensors 4 x x Control relay module; provides 4 relays and 4 sen-sors for controlling external devices or detecting ex-ternal control events.

Relay 4

88-264 V ac

Max. heat dissipation:

approx. 180 kJ/h

max. approx. 90 W

HiPath 3300






A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

Additional Power Supply by the Powerbox PB3000

Front panel

The following switches can be found on the front panel of the PB3000:

● Switch to switch the line voltage on and off

● Switch to switch the LUNA2 on and off (on = left switch position / LED illuminated green)

● LED LUNA2

Back

The following can be found on the rear of the unit:

● Line voltage connections

● S1 FAN switch: Not used

● F1 and F2: Fuse 2.5 A/T

● X1 and X2: Output to DECT

● F3: Fuse for battery 16 A/T

● X3: Battery output to external loads (HiPath 3000)

●

X7: Output for battery XBatt. (Power Box Controller (PBC) connection <-> battery)● XBatt.: Input for X7 (battery <-> Power Box Controller (PBC) connection)

● Switch to switch the battery voltage on and off

● F4: Switch fuse (battery voltage) 16 A/T

Further information

The service manual provides further information on the Power Box PB3000.

Weights Weight when empty: 7.0 kg

Total weight (incl. batteries and LUNA2): 21.0 kg (13.22 lb.)Battery compartment with 4 batteries: 12.0 kgSingle battery (12 V / 7 Ah): 2.65 kgLUNA2: 2.0 kg

UPS bridging times Examples:● PB3000 – HiPath 3300/3500: >1 h 30 min● PB3000 – HiPath 3800: > 30 min

Charging times Examples:● PB3000 – HiPath 3300/3500: ~ 2 h● PB3000 – HiPath 3800: ~ 2 h

Table 2-34 Technical specifications for PB 3000

Feature Description



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



Recommendations for CMA and CMS Utilization

2.8 Recommendations for CMA and CMS Utilization

One of the following optional subboards can be used for advanced clock accuracy:

● Clock Module Small CMS (S30807-Q6928-X) for all HiPath 3000 central control boards.● Clock Module ADPCM CMA (S30807-Q6931-X) for the CBCC and CBRC central control

boards.

Table 2-35 provides recommendations for the implementation of CMA and CMS subboardsbased on

● the type of network (ISDN S0, ISDN S2M or Ethernet/IP (10BaseT))

● the trunk connection available (no trunk/analog trunk, ISDN S0 or ISDN S2M) and conse-quently, the possible provision of a digital reference clock.

● HiPath Cordless Office.

Figure 2-14 Networking Options for HiPath 3000 Systems

Trunk connection:

● No trunk or an-alog trunk

● ISDN S 0● ISDN S2M

Trunk connection:

● No trunk or an-alog trunk


Networked via:


● Ethernet/IP(10BaseT)

HiPath 3000

SlaveSystem(s)

HiPath 3000

System(s)1+n

HiPath 3000

System 1

HiPath 3000

MasterSystem




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm


Table 2-35 Recommendations for CMA and CMS Utilization

Trunkconnec-

tion

Referenceclock


Trunkconnec-

tion

Referenceclock


No Yes No Yes

● Networking via ISDN S0 lines:

MASTER system SLAVE system(s)

No trunk/ analogtrunk

– – CMS/CMA(see Table 2-

36)


ViaISDN S0

networkingline

– CMA2

ISDN S0(not al-ways ac-tive)

ViaISDN S0 trunk con-

nection(if active)

CMS

1

CMS/CMA(see Table 2-36)

ISDN S0(not al-ways ac-tive)

ViaISDN S0 networking

line

– CMA

2

ISDN S0(alwaysactive)

ViaISDN S0

trunk con-nection

CMS1 CMA2 ISDN S0(alwaysactive)

ViaISDN S0

trunk con-nection

– CMA2

ISDN

S2M

Via

ISDN S2M trunk con-nection

CMS1 CMA2 ISDN S2M Via

ISDN S2M trunk con-nection

– CMA2



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011




● Networking via ISDN S2M lines:

MASTER system SLAVE system(s)


– – CMS/CMA(see Table 2-

36)


ViaISDN S2M networking

line

– CMA2

ISDN S0(not al-

ways ac-tive)

ViaISDN S0

trunk con-nection

(if active)

CMS1 CMS/CMA(see Table 2-

36)

ISDN S0(not al-

ways ac-tive)

ViaISDN S2M

networkingline

– CMA2


ViaISDN S0

trunk con-nection

CMS1 CMA2 ISDN S0(alwaysactive)

ViaISDN S0

trunk con-nection

– CMA2

ISDNS2M

ViaISDN S2M trunk con-

nection

CMS1 CMA2 ISDN S2M ViaISDN S2M trunk con-

nection

– CMA2


Trunkconnec-

tion

Referenceclock


Trunkconnec-

tion

Referenceclock


No Yes No Yes




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm


● Networking via Ethernet/IP (10BaseT) lines:

System 1 System(s) n+1


– CMS3 CMS/CMA(see Table 2-

36)


– CMS3 CMS/CMA(see Table 2-

36)

ISDN S0(not al-ways ac-

tive)

ViaISDN S0

trunk con-

nection(if active)


36)

ISDN S0(not al-ways ac-

tive)

ViaISDN S0

trunk con-

nection(if active)


36)


ViaISDN S0

trunk con-nection

– CMA2 ISDN S0(alwaysactive)

ViaISDN S0

trunk con-nection

– CMA2

ISDNS2M

ViaISDN S2M trunk con-

nection

– CMA2 ISDN S2M ViaISDN S2M trunk con-

nection

– CMA2

1 CMS is not necessary if the reference clock supplied by the CO is always available via the networking lines (not a trans-

parent clock).

2 CMA is not necessary if ADPCM conversion is not needed for HiPath Cordless Office (see Table 2-36).

3 CMS is not necessary but is recommended for the following reasons: Although an Ethernet link is an asynchronous con-

nection, buffer overflow/underflow can cause transmission errors. To avoid this, the clock difference between the master

and the slave systems should be as small as possible so that the receive and send buffer can be read and addressed at

the same speed on both sides. The more accurate the clock source in the relevant systems, the fewer the faults.


Trunkconnec-

tion

Referenceclock


Trunkconnec-

tion

Referenceclock


No Yes No Yes



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath Cordless Office

2.9 HiPath Cordless Office

2.9.1 Introduction

For Version 1.2 and later of HiPath 3000, HiPath Cordless Office can be used on all systems ofthis product line.

Direct connection

The BS3/1 (S30807-H5482-X) and BS4 (S30807-U5491-X) base stations can be connected di-rectly to the UP0/E interfaces on the central control boards in the HiPath 3550, HiPath 3350, Hi-Path 3500, and HiPath 3300. The connection must be made via one UP0/E interface each. Amix of base stations of types BS3/1 and BS4 is supported.

To ensure the operation of a maximum of one base station on the central control board’s UP0/E

interfaces of the HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300, a BS3/S (X30807-X5482-X100) single-cell base station can be used. In this case, it is not possible to expand withadditional base stations.

However, base stations cannot be simultaneously connected to the SLC16/SLC16N board andthe CBCC within one HiPath 3550 system.

Connecting cordless boards

Base stations can be connected to the UP0/E interfaces of the following cordless boards:

● SLC16N in HiPath 3550

● SLCN in HiPath 3800

A mix of base stations of types BS3/1 (S30807-H5482-X), BS3/3 (S30807-H5485-X) and BS4(S30807-U5491-X) may be used on the above cordless boards.

You can install up to four SLCN boards in HiPath 3800. All four boards provide full cordlessfunctionality (roaming and seamless connection handover) because the radio fields on thecordless boards are synchronized within a single system (see Section 2.9.3).

The HiPath 3000 product line does not currently support the network-wide handover feature.

>The BS3/1 (S30807-H5482-X), BS3/3 (S30807-H5485-X) andBS3/S (X30807-X5482-X100) base stations are being phased out and can not long-er be ordered. Use the successor product BS4 (S30807-U5491-X) instead of thetypes specified.

You can continue to operate the base stations specified in conjunction with HiPath3000. A mix of base stations of types BS3/1, BS3/3, and BS4 is also supported.

>The SLC16 (S30810-Q2922-X) board is no longer supported in HiPath 3000/5000

V6.0 and later systems.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm


2.9.2 System Configuration

The following table indicates the maximum possible system configuration parameters for theHiPath Cordless Office. It also shows when

● CMA or CMS is necessary.

● an analog trunk access is possible.

Tabelle 2-36 HiPath Cordless Office - System Configuration for HiPath 3000 V8

S

y s t e m

Max. no

C l o c k m o d u l e s Maximum number of base sta-

tions BS with connection via1xUP0/E

Simultaneouscalls per BS

M

a x . n o

M T s

A

n a l o g

t r u n

k a c c e s s

o f t h

e s y s t e m

S L C 1 6 N

S L C N

B S 3 / 1

B S 3 /

S

B S 3 / 3

B S 4

B S 3 / 1

B S 3 /

S

B S 3 / 3

B S 4

HiPath 3350HiPath 3300

– – CMS – 1 – 1 – 1/2 – 1/2 8 No

– – CMA 1 – – 1 1/4 – – 1/4 8 Yes

– – CMA 3 – – 3 1/4 – – 1/4 16 Yes


– – CMS – 1 – – – 1/2 – – 8 No

– – CMA 1 – – 1 1/4 – – 1/4 8 Yes

– – CMA 7 – – 7 1/4 – – 1/4 32 Yes

HiPath 3550 1 – CMS 16 – 16 16 1/4 – 3/12 3/1264 (with 1

SLC16N)Yes

HiPath 3800 – 4 CMS 64 – 64 64 1/4 – 3/12 3/12250 (with 4SLCNs)1

1 Up to 128 mobile telephones are possible at an SLCN.

Yes

Comments:● BS3/1 (S30807-H5482-X) is a base station that supports a maximum of 4 calls.● BS3/3 (S30807-H5485-X): is a base station that supports a maximum of 12 calls when connected using

three UP0/E interfaces.● BS3/S (X30807-X5482-X100): The BS3/S single-cell base station guarantees the operation of a maximum

of one base station on the UP0/E interfaces of the central board. It is not possible to operate additional basestations.

● BS4 (S30807-U5491-X): is a base station that supports a maximum of 12 calls when connected using threeU

P0/E

interfaces. In the case of a direct connection, it is only permitted to make the connection via one UP0/

E interface. The B channels in the base station BS4 require a license (see Section 1.4.13, "Licensing").



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011




2.9.3 Multi-SLC and Cross-System Networking

You can install up to four SLCN boards in HiPath 3800. For the total cordless station mobility(roaming and seamless connection handover) within a system, the radio fields of these cord-

less boards are synchronized.

The system treats every handset (mobile station) as a corded device. During administration, afixed port on the system’s "home cordless board" is assigned to the MT; this is used for ad-dressing the mobile telephone.

As soon as a mobile telephone moves into the area of a different radio switching location ("cur-rent-location cordless board"), an extension connection is switched using a DSS1 connectioninitiated by the cordless board. The home and current-location cordless boards exchange a net-working protocol (User-to-User Signaling UUS) over this extension connection to support fullmobility (see figure 2-15).

This function can be used not only within one system, but also among systems (among nodes)because the CorNet NQ used for networking supports the UUS protocol (note: for the system-wide extension connections, you may have to take additional B channels into consideration forthe permanent connection paths (CorNet NQ, see Section 2.9.4). Full mobility is guaranteedacross the various cordless system hops. All handset features (callback, team functions, voice-mail, etc.) remain intact. The network-wide handover feature is only exception here as it is notcurrently supported.

Required B channels

Table 2-37 Required B Channels for Multi-SLC and System-Wide Networking

Mobile telephone (MT) has setup a connection

Required Bchannels

Required B chan-nels for the home

cordless board

Required B chan-nels for the cur-

rent-locationcordless board

In the home cordless board range 1 1 –

In the current-location Cordlessboard range

3 2 1

Handover from home to home

cordless board

1 1 –

Handover from home to current-lo-cation cordless board

3 2 1

Handover from current-location tocurrent-location cordless board

5(temporary)

3 2(1 for each cordless

board)




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm


Networked HiPath 3000 systems feature

● max. 64 networked systems

● accessible using a common station number (roaming among the systems/nodes)

● call interruption when changing between systems/nodes

Figure 2-15 Example of an SLC16 Extended Connection in Networked Systems

BS

SLC

BS

CorNet-NQHome SLC16SLC No. = 1Call no. = 124

Current locationSLCSLC16 no. = 11Call no. = 128

HiPath 3000System 1

HiPath 3000System 2

Extensionconnection

BS

SLC

BS

SLC-No. = 2Call no. = 141

BS

SLC

BSBS = BS3/1 or BS3/3

A CorNet NQ connection is possible using S0 or S2M lines or IP networking (see HG 1500 AdministrationManual.



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011




2.9.4 Notes on the Planning of Networked HiPath 3000 SystemsWith the Network-Wide Roaming Feature

The demand for additional B channels for fixed connection paths (CorNet NQ) must be taken

into account for the system-wide extension connections described in Section 2.9.3.

If using the "network-wide roaming" feature, you must make sure that different systems withidentical DECT IDs do not have overlapping radio ranges. Handsets treat networked systemswith identical DECT IDs as a single system.

When hops overlap in systems with identical DECT IDs, handsets start to perform unintentionalnetwork-wide handover attempts which result in call cleardown.

If networking is required for systems in which the individual radio fields overlap (for example, toincrease capacity limits or through decentralized installation), different DECT IDs must be con-figured in the individual systems. The network-wide roaming feature is not supported in thiscase.

The following diagrams show three different showing HiPath 3000 system networking scenari-os.

Scenario 1: Incorrect DECT Configuration of Networked HiPath 3000 Systems

Identical DECT IDs and overlapping radio areas result in incorrect handover causing a break-down in communication.

Figure 2-16 Incorrect DECT Configuration of Networked HiPath 3000 Systems

PSTN

Networking (S0, S2M, IP)

HiPath 3000 system 1DECT ID = 4711





A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm


Scenario 2: Correct DECT configuration of networked HiPath 3000 systems

Handover works properly because DECT IDs are not identical even though the hops overlap.Disadvantage: No network-wide roaming.

Scenario 3: Correct DECT configuration of networked HiPath 3000 systems

Despite identical DECT IDs, handover works properly because the hops do not overlap. Net-work-wide roaming is possible.

Figure 2-17 Correct DECT configuration of networked HiPath 3000 systems

Figure 2-18 Correct DECT configuration of networked HiPath 3000 systems

PSTN

Networking (S0, S2M, IP)



PSTN



Networking

(S0, S2M, IP)



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011




2.9.5 Components of HiPath Cordless Office

2.9.5.1 Mobile Telephones

The mobile telephones in the Gigaset series can be used from 2000.

2.9.5.2 Base Stations

Types

● BS3/1 (S30807-H5482-X) is a base station that supports a maximum of four calls simulta-neously.

● BS3/3 (S30807-H5485-X): The base station can only be operated on the SLC16 or

SLC16N board. The connection via at least two UP0/E interfaces is essential. It supports amaximum of 12 calls when connected using three UP0/E interfaces.

● BS3/S (X30807-X5482-X100): The BS3/S single-cell base station guarantees the opera-tion of a maximum of one base station on the UP0/E interfaces of the central board. It is notpossible to operate additional base stations.

● BS4 (S30807-U5491-X): is a base station that supports a maximum of 12 calls when con-nected using three UP0/E interfaces. In the case of a direct connection, it is only permittedto make the connection via one UP0/E interface. The B channels in the base station BS4require a license.Cannot be connected to SLC16.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm



Table 2-38 Technical Data for Various Base Stations

Parameter BS3/1 andBS3/S

BS3/3 BS4 Outdoor cover

Power supply voltagerange

42 to 54 V 42 to 54 V 42 to 54 V –

Power consumption max. 1.7 W max. 3.2 W max. 3.0 W –

Housing dimensions(W x D x H in mm)

181 x 139 x 69 202 x 172 x 43 200 x 176 x 49 296 x 256 x 90

Weight approx. 0.3 kg approx. 0.5 kg approx. 0.5 kg approx. 1.0 kg

Temperature range for indoor use: – 5 to + 50 oC

for outdoor use: – 20 to + 45 oC

Relative humidity – – – up to 95 %



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



Technical Specifications HiPath 3000

2.10 Technical Specifications HiPath 3000

Table 2-39 Technical Specifications

Maximum SystemValues

HiPath 3800 HiPath3550

HiPath3350

HiPath3500

HiPath3300

Ringer EquivalenceNumber (type plate)

BC1 =6 A / 110 Vac,3 A / 230 Vac

EC1 =8 A / 110 Vac,4 A / 230 Vac

1 BC: Basic cabinet, EC: Expansion cabinet

2.6 A / 115 –230 Vac

1.3 A / 115 –230 Vac

2.6 A / 115 –230 Vac

1.3 A / 115 –230 Vac

AC line frequency 50 – 60 Hz

Power consumption2

2 The levels specified are worst case values that should not be used to estimate operating costs (energy costs). The realconsumption values are expansion- and traffic-dependant and generally lie far below the worst case values.

BC = 490 WEC = 720 W

Heat build-up (withoutworkpoints)2

BC =1500 kJ/h

Slot2200 kJ/h

Dimensions(height x width x depthin mm)

490 x 440 x430

450 x 460 x200

450 x 460 x128

155 x 440 x380

88 x 440 x380

Height units for 19“cabinet assembly

11 – – 4 2

Weight BC = 16.5 kgEC = 15.0 kg

(transport weight,including back-

plane and cabinetfeet)

8 kg 6 kg 8 kg 6 kg

Powerbox PB3000, incl. 4 batteries and LUNA2: 21 kg(Battery compartment including 4 batteries: 12 kg, LUNA2: 2 kg)




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

Interfaces

2.11 Interfaces

Interfaces for stations

Interfaces for trunk traffic and tie traffic

Subscriber line Interface Connection Protocol

Digital UP0/E(2-channel)

optiPoint 500/600 telephones with adaptersor UP0/E card

CorNet-TS

Analog T/R Analog telephones, group 2, 3 fax, Vtx,voice mail, data via V.24 adapter (modem),announcement devices, MOH

DTMFDP

Cordless UP0/E CMI base station CorNet-TR

Digital (ISDN) S0 (2-channel) S0 PC card, group 4 fax, telephones (no

feeding)

DSS1

Trunk/Tie Traffic

Interface Connection Protocol

Digital S2M FV (30-channel)(FV = dedicatedline)

ISDN trunkTie trunk networking

DSS1CorNet NCorNet-NQQSig

Digital S0 FV (2-chan-nel)(FV = dedicatedline)

ISDN trunkTie trunk networking

DSS1CorNet NCorNet-NQQSig

Analog LS Analog trunk, PSE DTMF/DP

Analog E&M Analog tie trunk DTMF/DP

IP LAN 10BaseT 10/100 TCP/IP



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



Interfaces

Interfaces for options

Option Interface Connection Protocol

Profi-PSE ESPA PSE

Announce-ment beforeanswering

T/RE&M

Announcement device without start/stop control orwith start/stop control

V.24/CSTA V.24 Service PC (first V.24 (RS-232) interface), applica-tions (CSTA) or call detail printer/call charge com-puter (second V.24 (RS-232) interface)

Floating con-tacts

Relay Door opener, messenger call, and others,4 floating contacts

ALUM Relay Analog power failure transfer for 4 trunks




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

Interface-to-Interface Ranges

2.12 Interface-to-Interface Ranges

Telephone interface-to-interface ranges (with J-Y (ST) 2x2x0.6, 0.6 mm diameter)

Trunk connection and CorNet N/CorNet NQ ranges

The table below provides the maximum cable lengths for direct trunk connection and direct Cor-Net N/CorNet NQ wiring. The values apply to ideal conditions, which means there can be no joints, etc. The real conditions must be measured on-site.

Table 2-40 Telephone Interface-to-Interface Ranges (with (ST) 2x2x0.6, 0.6 mm diameter)

Telephone Interfaces Range in m Loop Resistance inOhms

ISDN S0 layer 1 point-to-point connection < 600 156

ISDN S0 extended bus connection < 400 104

ISDN S0 bus connection1

1 Board-specific

< 80for the HiPath 3800 board

STMD3 (Q2217)

< 120for all other S0 boards

21

ISDN-S0 wall outlet to terminal < 10 –

Analog users < 2000 520

UP0/E exchange to primary telephone < 1000 230

UP0/E primary to secondary telephone < 100 23

Table 2-41 Cable Lengths for Trunk Connection and Direct CorNet N/CorNet NQ DirectWiring

Inter-face

Cable Diameter Attenuationper km

Max. cablelength

S0 ICCS cableJ-2Y(ST)Y4x2x0.51 LG ICCSData5

0.51 mm 7.5 dBat 96 kHz

800 m

Installation cableJ-2Y(ST)Y 10x2x0.6 ST III BD

0.6 mm 6.0 dBat 96 kHz

1000 m

S2M A-2Y0F(L)2Y 10x2x0.6 (full PEinsulation, filled)

0.6 mm 17 dBat 1 MHz

350 m






A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

Numbering Plans

2.13.2 ISDN Numbering Plan (E.164) V7 or Later

ISDN numbering plan (E.164)

The ISDN numbering plan (E.164) is a new numbering plan for addressing telephone networks.It specifies the different parts of the telephone number and the number of permissible digits(country code, network area code, system phone number). The ISDN numbering plan (E.164):

● improves integration in networks with HiPath 4000

● connection to Internet telephony service providers

The plan can be configured using Manager E.

When networking with the ISDN numbering plan (E.164), you must ensure that HiPath 3000/ 5000 is permitted to transmit the number of the called station (dialing information) with the Type

Of Number TON = unknown and that the networked system always transmits a fixed Type OfNumber TON (and not another type).

Objective of E.164 networking

The objective of networking with E.164 is to transmit all station numbers in a network in an in-ternational format, in a network with HiPath 4000, for instance. Station numbers, however,should be shown on displays in the most suitable format.

The stations can be reached over a public station number, that is, the E.164 station number innational or international format (for instance, internal calling party number in ISDN format) with-out first dialing a node number. Each station is represented by its E.164 number which can beoptimized for display.

● Telephone numbers in the HiPath 5000 RSM network are shortened to the station number.

● Maintaining the port number list, which contains all ISDN numbers of all nodes in the Hi-Path 5000 RSM network. The numbers of nodes outside the HiPath 5000 RSM network(HiPath 4000, for instance) are not entered. These numbers are shortened to the most suit-able format using the location station number.

SIP

When E.164 numbering is activated, the internal number is transmitted in E.164 format. SIPstations are registered using the full E.164 number (location number + internal number,4923026673665, for instance).

If an Internet telephony service provider is to be used and the Internet telephony service pro-vider’s station number is made available in an E.164 network, the station allocation must be en-tered. The shortest dialable station number is always used for the allocation.

In HG 1500, the SIP station number is allocated to the extension (the internal extension is usu-ally entered here).



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



Numbering Plans

Example: If the Internet telephony service provider is connected to the node at the Witten siteand a subscriber from Munich should use an SIP number, the number 008972212345 is en-tered during allocation in the HG 1500 at the Witten site. The shortest dialable station numberis always entered. This is also the shortest number that the customer would dial on a telephone

(the number the subscriber in Witten uses to call the subscriber in Munich).

Calling party identification:

HiPath 3000/5000 supports correct calling party identification when networking systems thathave the same system phone number.

If nodes with different system phone numbers are used in the network, the full system phonenumber is retained in the calling party’s number.

In networks with different system phone numbers, calling party numbers are displayed correctly

if open numbering is used (different area codes).




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

Technical Specifications and Compliance to HiPath 3000

2.14 Technical Specifications and Compliance to HiPath 3000

2.14.1 CE Compliance (not for U.S.)

The systems conform to the following guidelines and standards:

2.14.2 Compliance with US and Canadian Standards (For U.S. andCanada Only)

2.14.3 SAFETY International

IEC 60950-1, first edition 2001, modified

Guideline Standard

R&TTE Directive 99/5/EEC ● EN 60950-1: 2001 (Safety)● EN61000-6-2 (EMC Immunity Industrial)● EN55024 (EMC Immunity Residential)● ETS 300 329 (DECT Emission/Immunity)● TBR 06, ETS 301489-1/6 (DECT Air Interface)

Table 2-43 Compliance with US and Canadian Standards (For U.S. and Canada Only)

Category HiPath 3800 HiPath 3550 HiPath 3350

Product security UL 60950-1 First EditionCAN/CSA C22.2No. 60950-1-03

UL 60950-1 First EditionCAN/CSA C22.2No. 60950-1-03

FCC Part 15 subpart J Class A Class A Class B

FCC Part 68 registra-tion

AY3PF05BHIPATH3K8 AY3USA–25214–MF–EAY3USA–25215–KF–E

Industry Canada CS– 03 certification

267V-HP3800 267 8782A

Ringer EquivalenceNumber (REN)

0.5B 0.4



3000sb2.fm

A31003-H3580-Y100-10-7618, 01-2011



Environmental Conditions

2.15 Environmental Conditions

2.15.1 Electrical Operating Conditions

● Operating limitsRoom temperature: + 5 ...+ 40 °C (41 ... 104 °F)absolute humidity: 2 ... 25 g H2O/m3

relative humidity: 5 ... 80 %

● System ventilation is by convection. Automatic ventilation is required when using theHG 1500 in HiPath 3550 and HiPath 3350.

2.15.2 Mechanical Operating Conditions

The systems are intended for stationary use.

7CautionAvoid exposing the system to direct sunlight and heaters (excessive heat may dam-

age the system).Systems subject to condensation must be dried off before being put into service.Putting a system into service with condensation still present should be avoided at allcosts.




A31003-H3580-Y100-10-7618, 01-2011


3000sb2.fm

Environmental Conditions



3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch HiPath 5000 System Overview

Introduction

3 HiPath 5000 System Overview

3.1 Introduction

HiPath 5000 is operated as a central administration unit in an IP network of HiPath 3000 sys-tems. By creating a "Single System Image", all relevant nodes can be centrally administered.

HiPath 5000 is the platform for the central provision of applications, and facilitates the use ofthese applications by all IP networking stations.

Parts of the following setup applications for HiPath 5000 are optional and can be installed bothon the HiPath 5000 RSM (RSM: Real-time Services Manager) and on a separate PC.

These applications are:

●

Feature Server (central administration service in a HiPath 3000/5000 network)● Real-time Telephony Presence Manager (service for LED signaling of call processing sta-

tion statuses and network-wide DSS keys)

● Database Synchronization for HiPath 3000

● HiPath 3000/5000 Manager E (MS Windows-based tool for system administration of allservice and customer-specific data by Service)

● HiPath 3000/5000 Manager C (MS Windows-based tool for system administration of cus-tomer-specific data by the customer)

● Inventory Manager (service for detecting software components installed and system infor-mation in a HiPath 3000/5000 network)

● Backup Manager

● Software Update Manager

● Customer License Agent CLA (service for analyzing and decrypting a HiPath License Man-agement license file)

● Central License Manager CLM (CLA front-end for reading in licenses in online and offlinemode)

● Central Fault Management V3.0 (Java-based application for error signaling)

● GetAccount (application that prepares generated call data records for further processing.)



HiPath 5000 System Overview Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb3.fm

Software Structure

3.2 Software Structure

Feature server

The Feature Server is an essential component in the HiPath 5000 software architecture andserves as a central point for administration and as a data interface for applications and middle-ware. In addition, the Feature Server synchronizes the HG 1500 boards with all necessary datafor digit analysis in a HiPath 3000/5000 network.

The networked HiPath 3000 systems (nodes) are administered over the Feature Server. TheHiPath 3000/5000 Manager E administration tool does not communicate with the individualsystems but exchanges data with the Feature Server. The Feature Server ensures that the net-worked HiPath 3000 systems receive synchronized CDB data.

The individual systems are accessed directly by HiPath 3000/5000 Manager E in the course of

maintenance and online functions.HG 1500 boards are still administered on a board-specific basis using Web-based manage-ment (WBM).

The Feature Server is an MS Windows service that automatically starts at the same time as theHiPath 5000 server.

Communication with the individual HiPath 3000 systems belonging to the network takes placeover their HG 1500 boards.

Figure 3-1 Customer Data Exchange Between the Feature Server and Nodes

Feature server

HiPath 3000Node 1

HG 1500

HiPath 3000Node 2

HG 1500

CDB 1 CDB 2

CDB 1CDB 2

CDB 3

HiPath 3000Node 3

HG 1500

CDB 3



3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011



Software Structure

The following figure shows the services and routines associated with the Feature Server.

Figure 3-2 Feature Server Services and Routines

CDB SynchronizationHiPath 3000 –> server

vsync.exe

Application Interface

vaplx.dll

Call Address Resolu-tion Update Server

cars.exe

HG 1500 RegistrationServer

regserver.exe

Server Control Layer(MS Windows Service)

vsrv.exe

Server Database

vdbaccess.dll

Socket Interface

vsock.dll

Data Transfer Interface

vadmtftp.dll

Remote Procedure CallInterface

FCT.dll

Event Log Texts

VEvtLogMsg.dll

AssCkds.dll

Accs520x.dllAccs520x.dllAccs520x.dllAccs520x.dll





3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011



HiPath 5000 Server PC

3.3 HiPath 5000 Server PC

To use HiPath 5000, the following minimum requirements must be met:

● Hardware and software of the HiPath 5000 server

● Licenses

A grace period of 30 days begins after startup. Licensing must be performed for all licensedfeatures, interfaces, and products within this grace period.

Component HiPath 3000/5000 V8 MR5 HiPath 3000/5000 V8 MR4

Processor 3 GHz CPU 3 GHz CPU

RAM space See Table 3-3 See Table 3-3

Hard disk 80 GB 80 GB

Operating system Microsoft Windows Server 2003(32 bit)

Microsoft Windows Server 2003(32 bit)

Slots Optional:

Free PCI slots(for S0 /S2M cards forHiPath Cordless Office andOpenScape Xpressions)

Optional:

Free PCI slots(for S0 /S2M cards forHiPath Cordless Office andOpenScape Xpressions)

Drives 3,5" floppy disk driveCD-ROM/DVD drive

3,5" floppy disk driveCD-ROM/DVD drive

Network card 10/100/1000 Mbps Ethernet net-work card

10/100/1000 Mbps Ethernet net-work card

Monitor 17-inch color monitor 17-inch color monitor

Table 3-2 Hardware and Software Minimum Requirements for HiPath 5000




A31003-H3580-Y100-10-7618, 01-2011


3000sb3.fm

HiPath 5000 Server PC

● RAM requirements of the HiPath 5000 server

Table 3-3 can be used to determine the required RAM expansion (RAM space) of the Hi-Path 5000 server depending on the number of nodes in the HiPath 3000/5000 network and

the applications installed on the server.

Minimum RAM

Up to2 nodes

Up to8 nodes

Up to16 nodes

Up to32 nodes

Up to64 nodes1

1 Networks are currently released with up to 32 nodes. Larger configurations can be released on a project-specific ba-

sis.

HiPath 5000 V5.0+ HiPath FM V3.0+ Teledata Office V3.0+ HiPath 3000/5000 Soft-ware Manager

512 MB 1 GB 1 GB 1.5 GB 2 GB

OpenScape OfficeContact Center withOpenScape Xpressions2

2 In this special configuration, OpenScape Xpressions supports up to 248 Unified Messaging users or 400 voice mail

users.

+ 400 MB + 400 MB + 600 MB not sup-ported

not sup-ported

DLS + 250 MB + 250 MB + 250 MB + 250 MB + 250 MB

Table 3-3 RAM Space of the HiPath 5000 Server



3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011



Server Networking

3.4 Server Networking

3.4.1 Features of IP Networking

Transparent for End Users

● No special telephones are required, as the conversion of voice into IP packets takes placein the LAN gateway rather than in the telephone.

● The transfer of the general network features has no effect on the way the telephones areused, and therefore does not restrict the convenience of the telephone functions in anyway.

● DTMF signals: DTMF signals are supported. It is therefore possible to have suffix dialingor to listen to voice mail over the IP network.

Support of Network-wide Features

HiPath 5000 supports the CorNet NQ protocol; in this process CorNet NQ-specific features aretransmitted over the IP network (tunnelling).

The following applies: The features that are currently transmitted in a HiPath 3000 corporatenetwork are also supported by HiPath 5000 with some enhancements in comparison to con-ventional networking. (see General Features).

Central Attendant Console

A central attendant console may be deployed in HiPath 2000/HiPath OpenOffice EE/HiPath3000/HiPath 5000 networks. Platform-wide busy signaling is also possible.

(See optiClient Attendant)

Automatic Routing

HiPath 5000 can perform automatic routing to a backup or alternative network for new connec-tions. A voice network (such as ISDN dial-up connection) can also be used as a backup net-work. This ensures that the high availability of HiPath is not affected by the use of IP networksfor the transfer of voice and fax connections. Automatic routing is initiated if

● the communication platform selected is not accessible (for example because of an error oroverload in the IP network).

>NoteThe cross-communication platform busy signaling feature is only available with opti-Client Attendant.HiPath 5000 (Presence Manager) is not necessary for this purpose.




A31003-H3580-Y100-10-7618, 01-2011


3000sb3.fm

Server Networking

● there is no more capacity available in LAN accesses (maximum number of B channels forLAN gateway exceeded)

● a connection is explicitly requested (for example a modem connection)

Network Management

All communication platforms are administered using an enhanced version of HiPath 3000 Man-ager E. The HiPath 3000 Manager E tool is included in the scope of delivery and is installed onthe HiPath 5000 server. From here, it is possible to have central administration of all communi-cation platforms in a shared database. An application running permanently on the feature serv-

er is used for the automatic administration and maintenance of the IP routing tables and thetransmission of data to the individual communication platforms (see HiPath 3000 Manager E)

Network management - including troubleshooting and trace activation - can be performed bothlocally and remotely.

>NoteISDN lines are required as a trunk connection for routing data connections/VoIP con-nections over the integrated ISDN router.



3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011



Server Networking

3.4.2 IP Network and Application Server Requirements

3.4.2.1 Adequate Connection Bandwidth

The customer network must fulfill the following requirements to ensure that voice information istransmitted successfully via LAN:

● Switched LAN with 10/100 Mbps

● Fixed IP addresses

● Each component must have its own port at the switch (no HUBs as concentrators)

● Pure Microsoft TCP/IP network (not a Novell network with SPX)

● QoS, ToS and DiffServ (see below)

Although use in shared environments is possible, it is neither approved nor recommended, asthere is no guarantee of quality. The HiPath server can also be operated in networks with rout-ing components

3.4.2.2 Bandwidth

The bandwidth for voice must be available in the network at all times. For this reason, networkmeasurement and analysis is carried out before installing the components.

Why Measure the Network?

The following data is required to calculate the required bandwidth for voice transmission in anIP network in relation to the number of simultaneous connections:

Bandwidth for voice information

All values refer to the lowest packet assembly level. The bandwidths in the WAN are only validif the multilink and segmenting parameters have not been set.

>Because of the data traffic between the HiPath DB server components and the serv-er, routing connections are always open (no short-hold in the WAN).

Type Bandwidth for each connection (full duplex)1

1 All values refer to the lowest packet assembling level for HG 1500 V2. Because of its expanded functionality HG 1500 V3

can differ from this. See HG1500 V3 release note.

Voice with ITU G.711 50 Kbps in LAN

Voice with ITU G.723.1 22 Kbps in LAN; 19 Kbps in the WAN




A31003-H3580-Y100-10-7618, 01-2011


3000sb3.fm

Server Networking

Bandwidth Requirements for Additional Services:

The specified values represent the load in relation to a maximum call volume of 1400 BHCA(this is the maximum traffic with a connected call center solution).

Bandwidth Requirements for Administration (valid only for HPCO):

The specified bandwidth represents the worst case scenario. In other words, an entire CDB is

sent to the server from the HiPath node every 30 seconds (max.) as a result of the synchroni-zation process configured in the system.

It is currently difficult to define a practice-oriented value due to the lack of data from the field.However, the bandwidth requirement will, in practice, be well below 132 kBit/s, or there will betemporary peaks during which this value will be required by the network.

In practice, the most frequent application is the call up of key programming by users. A block of64 KB is transferred in this process. An accepted period of 30 seconds for the transmission pro-cess results in bandwidth requirements of 18 Kbps.

Type Record size Bandwidth requirement

Busy signal(optiClient Attendant)

300 bytes 3 Kbps

Call detail records 200 bytes 1 Kbps

ACD information 3.5 KB 10 Kbps

Type Record size Bandwidth requirementSynch by Hicom per TFTP 607232 bytes 132 Kbps



3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011



Server Networking

Accordingly, the minimum bandwidth required is as follows:

The necessary bandwidth must be calculated using N as the number of simultaneous connec-tions:

N = number of simultaneous voice connections

When configuring fax or modem transmissions using the formula described above (outbandtransmission) the following are also required for each configured connection:

● For fax group 3 (V.17, 14 Kbps): approx. 20 Kbps

● For modem connections (V.34, 33.6 Kbps): approx. 40 Kbps

3.4.2.3 Requirements of Delay Times

For natural communication, the delay should amount to a maximum of 50 ms (one-way delay)for voice connections (network delay). Delays of more than 50 ms in one direction impair natural

communication. The effect is similar to that experienced with voice connections over satellite.The maximum number of 15 buffer stations (HOPs) may not be exceeded.

Priority control is a particularly efficient means of reducing the delay (see next section). Pleaseproceed with caution if the network is operated using lines with a low bit rate (for example, con-nection of a branch to headquarters at a rate of 128 Kbps). The maximum number of trunk linescan be determined by calculating the necessary bandwidth.

3.4.2.4 Provision of QoS in Data Networks

To guarantee the Quality of Service (QoS) described in the two previous sections, the following

standards must be met:● All the components involved in transmitting voice data must support min. IEEE 802.1q (lay-

er 2).

● In addition, all components require routing according to the Diffserv standard RFC 2474and the ToS standard (Type of Service) RFC 791.

Required bandwidth Formula (Kbps) of approximate values

With ITU G.711 .. N x 90 (voice)+ N x 4 (BLF+CDR)+ 10 (ACD/TAPI)

With ITU G723.1 .. N x 22 or 19 (voice)+ N x 4 (BLF+CDR)+ 10 (ACD/TAPI)





3000sb3.fm

A31003-H3580-Y100-10-7618, 01-2011



Server Networking

3.4.2.9 Adaptation of QoS Classes to Oscar

Standardization according to the "HiPath QoS Strategy" involves adjusting the assignment ofQoS classes on HG 1500 and in WBM:

Previous allocation in CDB 2.4:

New allocation in CDB 2.5:

Voice Payload = AF43

Call Signaling = AF31

Data Payload = AF21

Network Cont. = AF12

Voice Payload = AF12

Call Signaling = AF21

Data Payload = AF11

Network Cont. = CS7




A31003-H3580-Y100-10-7618, 01-2011


3000sb3.fm

Server Networking





HiPath 3000/5000 in the LAN Network Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

Network Analysis

4.1.1 Network Protocols

4.1.1.1 H.323

As a collective term, H.323 comprises the following topics:

● Signaling (H.245, ... )

● Video transmission

● Voice data transmission/voice compression such as – G.723.1 (5.3/6.3 Kbps) – G.729A (8 Kbps)

● Data applications (application sharing, T.120)

This shows that this standard comprises considerably more than necessary for pure voice datatransmission via data networks. H.323 was developed for multimedia applications.

4.1.1.2 SIP / SIP-Q

Networks

In HiPath 3000/5000 V7 and later systems, networking is possible via:

● SIP with HiPath 2000 / HiPath OpenOffice EE, HiPath 3000, HiPath 4000 and HiPath 5000

● SIP-Q V2 with HiPath 2000/ HiPath OpenOffice EE, HiPath 3000, HiPath 4000,HiPath 5000 and OpenScape Voice

SIP

SIP (Session Initiation Protocol) is a network protocol for establishing, controlling and ending acommunication sessions between two or more stations. Actual payload is exchanged via other

protocols, such as SDP (Session Description Protocol) and RTP (Realtime Transport Protocol).

SIP-Q

SIP-Q V1 (SIP-QSig) is a network protocol enhanced by the QSig signaling protocol. QSig isin turn enhanced by CorNet-NQ. In SIP-Q V1, QSig (incl. CorNet-NQ) is tunneled via SIP. Thisenables more features to be implemented between the communication systems.

QSig is a signaling protocol based on ISDN for networking communication systems from differ-ent manufacturers.

>In HiPath 3000 V8 and HiPath 4000 V5 and later systems, only SIP-Q V2 protocol isused for IP networking between these systems and only CorNet-NQ is used for TDMnetworking. CorNet IP protocol is no longer supported.






A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

Network Analysis

Payload connections with RTP (Real-Time Transport Protocol) in a LAN environment

The bandwidth required for voice transmission in an IP network can be calculated using the fol-lowing table:

The LAN load is calculated for a single route. The bandwidth must be doubled for payload con-nections in both directions. HG 1500 V3.0 supports VAD with codecs G.7231A and G.729AB.If you use these codecs, bandwidth requirements vary in relation to the length of idle periods

in voice signals.

VLAN tagging based on IEEE 802 1q is also performed as part of the calculation. Packet lengthis shorter by 4 bytes without VLAN tagging.

The overhead is calculated as follows:

Codec type Packetizingparameterswith WBM

Samplesize (ms)

Payload(bytes)

EthernetPacket length

(bytes)

Payloadpacket (over-head in per-

cent)

EthernetLoad (incl.)

header(Kbps)

G.711 20 20 160 230 44% 92

G.711 40 40 320 390 22% 78

G.711 60 60 480 550 15% 73,3

G.723.1 1 30 24 94 292% 25,1

G.723.1 2 60 48 118 146% 15,7

G.729A 1 20 20 90 350% 36

G.729A 2 40 40 110 175% 22

G.729A 3 60 60 130 117% 17,3

RTCP 5000 280 0,4

Table 4-1 Codec-Based Bandwidth Requirements

Protocol Bytes

RTP header 12

UDP header 8

IP header 20802.1Q VLAN tagging 4

MAC (incl. preamble, FCS) 26

Total 70

Table 4-2 Overhead Calculation



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch HiPath 3000/5000 in the LAN Network

Network Analysis

The following values apply to payload connections with RTP (Real-Time Transport Protocol) ina WAN environment:

The WLAN load is calculated for a single route. As WLAN channels usually contain channelsin both directions, this is the same as the bandwidth requirement, for example, for an ISDNchannel.

The overhead is calculated as follows:

Report type Reportinterval (sec)

Average Ethernet packetsize (bytes)

EthernetLoad (incl.)header (Kbps)

Sender report 5 140 0,2

Recipient report 5 140 0,2

Total 0,4

Table 4-3 Payload Connection Check with Parallel RTCP (Real-Time Transport ControlProtocol)

Codec Packetiz-ing

Samplesize (ms)

Payload(bytes)

Packetlength

(bytes)

Payloadpacket

(overheadin %)

WLANload

(Kbps)

Packetlength with

headercompres-

sion(bytes)

WLANload with

headercompres-

sion(Kbps)

G.711 20 20 160 206 29% 82,4

G.711 30 30 240 286 19% 76,3

G.711 40 40 320 366 14% 73,2

G.711 60 60 480 526 10% 70,1

G.723.1 1 30 24 70 192% 18,7 32 8,5

G.723.1 2 60 48 94 96% 12,5 56 7,5

G.729A 1 20 20 66 230% 26,4 28 11,2

G.729A 2 40 40 86 115% 17,2 48 9,6

G.729A 3 60 60 106 77% 14,1 68 9,1

RTCP 5000 230 0,4 0,4

Table 4-4 Codec-Based WLAN Bandwidth Requirements

Protocol Bytes

RTP header 12

UDP header 8

IP header 20

PPP 9





A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

Network Analysis

A "compressed header" is usually used for RTP/UDP/IP Header compression. In addition every5 seconds a full header is sent (total = 46 octets).

The rule of thumb for calculating the bandwidth requirement for n parallel VoIP connections withG.711 (one frame per RTP packet) is:

Bandwidth LAN = n × (180 voice payload + 0.4 RTPC)

Bandwidth WAN = n × (82 voice payload + 0.4 RTPC)

The approximate values for voice payload changes for other codecs or packet values. Thebandwidth for attendant busy signaling, call charge information, and other applications mustalso be taken into account.

Bandwidth requirement for CAR-Alive/Node Survey

There are two different methods for performing CAR-Alive/node survey: either a TCP-basedmechanism or an ICMP ping (configurable with Manage I or WBM).

Total 46

Compressed header 8

NodeNumber

TCP load(Kbps)

Ping load(Kbps)

Time-out

1 0,1 0,1 12

2 0,2 0,3

3 0,5 0,8

4 1,0 1,7

5 1,7 2,8

6 2,5 4,2

Table 4-6 LAN Bandwidth Requirement for CAR-Alive/Node Survey

NodeNumber

TCP load(Kbps)

Ping load(Kbps)

1 0,07 0,11

2 0,14 0,22

3 0,41 0,66

Table 4-7 WAN Bandwidth Requirement for CAR-Alive/Node Survey

Protocol Bytes




3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



Network Analysis

The rule of thumb for calculating the bandwidth requirement for CAR-Alive between n nodes is:

Bandwidth LAN = n × (n-1) × bytes AliveMsg × 8 ÷ 1000 ÷ T timeout between ping

and the rule of thumb for calculating the bandwidth requirement for CAR-Alive between n nodesat the HG 1500 interface is:

Bandwidth LAN = (n-1) × (n-1) × bytes AliveMsg × 8 ÷ 1000 ÷ T timeout between ping

The value for bytesAliveMsg:

in the LAN is 212 with ping or 127 with TCPin the WAN is 188 with ping or 102 with TCP

The default timeout between two pings is 12 seconds.

The following table contains information on additional bandwidth requirements for signals:

4 0,82 1,31

5 1,37 2,19

6 2,06 3,28

Device/application BHCA Load (Kbps)

DSS server, outgoing and incoming calls 1400 2Attendant (busy) 1400 3

Call charge information 1400 1

ACD information 1400 10

Fax over vCAPI, 14400 bauds 2

CDB synchronization system with DBFS (TFTP, burst) 162

Table 4-8 Bandwidth Requirements for Signals

NodeNumber

TCP load(Kbps)

Ping load(Kbps)

Table 4-7 WAN Bandwidth Requirement for CAR-Alive/Node Survey




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

Network Analysis

Bandwidth requirement in LAN environments with encryption:

Encryption requires higher bandwidth. In the following tables, the required bandwidth is listedbased on the possible voice codecs and encryption algorithms for Ethernet packets. Encryption

is carried out via an IPsec protocol stack. Out of the different operating modes possible in IP-sec, only one is described here: the ESP tunnel mode with authentication.

This operating mode offers the highest security for site-to-site VPNs.

ESP header length: The length of the ESP header depends on the encryption algorithm used.If used for cipher block chaining (block encryption), the ESP header contains an initializationvector ("IV" in table above). The initialization vector is the same length as an encryption block.

Protocol Bytes Encoded?

ESP Trailer 12

ESP Padding Varying (y) Encrypted

ESP Padding Header 2 Encrypted

Voice Payload Varying (x) Encrypted

RTP 12 Encrypted

UDP 8 Encrypted

IP (original) 20 Encrypted

ESP Header 8 + IV1

1 IV = Initialization Vector. Explained in text below the table

IP (tunnel) 20

802.1Q VLAN tagging 4

MAC (incl. preamble, FCS) 26

Total 112 + IV + x + y

Table 4-9 Encoded Voice Packet Structure(ESP Tunnel Mode with Authentication)



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



Network Analysis

Padding: Padding with bytes is required as the encryption algorithms are based on block en-cryption. The entire encoded part of the packet (original IP/UDP/RTP header, voice payload,ESP padding header, ESP padding) must be an integer value which is a multiple of the encryp-tion block length.

The number of padding bytes required for voice packets is calculated using the following for-

mula:(42 + x + y) [bytes] = N x (8 or 16 [bytes]) // N is an integer.

Bandwidth calculation for the AES encryption algorithm:

Encryption algorithm Block length Length of the initialization vec-tor

AES 16 bytes (128 Bit) 16 bytes (128 Bit)

DES 8 bytes (64 Bit) 8 bytes (64 Bit)

3DES 8 bytes (64 Bit) 8 bytes (64 Bit)

Table 4-10 Block Lengths of the Encryption Algorithms

Codec Packetizing Sample size(ms)

Payload(bytes)

Padding(bytes)

Ethernetpacketlength

Payload pack-et (overhead

in %)

Ethernet loadincl. preamble

(Kbps)

G.711 20 20 160 6 294 75% 117,6

G.711 30 30 240 6 372 50% 99,2G.711 40 40 320 6 454 38% 90,8

G.711 60 60 480 6 614 25% 81,9

G.723.1 1 30 24 14 166 500% 44,3

G.723.1 2 60 48 6 182 250% 24,3

G.729A 1 20 20 2 150 600% 60,0

G.729A 2 40 40 14 182 300% 36,4

G.729A 3 60 60 10 198 200% 26,4

Table 4-11 LAN Bandwidth Requirement for AES Encryption – According to Codec




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

Network Analysis

Bandwidth calculation for the DES/3DES encryption algorithm:

Codec Packetizing Sample size

(ms)

Payload

(bytes)

Padding

(bytes)

Ethernet

packetlength

Payload pack-

et (overheadin %)

Ethernet load

incl. preamble(Kbps)

G.711 20 20 160 6 286 75% 114,4

G.711 30 30 240 6 366 50% 97,6

G.711 40 40 320 6 446 38% 89,2

G.711 60 60 480 6 606 25% 80,8

G.723.1 1 30 24 6 150 500% 40,0

G.723.1 2 60 48 6 174 250% 23,2

G.723.1 3 90 72 6 198 167% 17,6

G.729A 1 20 20 2 142 600% 56,8

G.729A 2 40 40 6 166 300% 33,2

G.729A 3 60 60 2 182 200% 24,3

Table 4-12 LAN Bandwidth Requirement for DES/3DES Encryption – According to Codec

>Values which differ in both tables are highlighted.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



QoS - Quality of Service

4.2 QoS - Quality of Service

4.2.1 Goals of QoS

4.2.2 QoS in the Router

● QoS functions control router priorities and timing.

● Router queues are optimized for routing and are not suitable for QoS monitoring of voicetransmission

● Fragmentation (if used) takes time and thereby increases the risk of packet loss

● Time-controlled hierarchical policies not available

● No feedback due to insufficient monitoring● Architecture not suitable for specialized VoIP control functions

Subject Cross Reference

Goals of QoS Section 4.2.1 onpage 4-11

QoS in the Router Section 4.2.2 onpage 4-11

Problems: ● IP does not guarantee any bandwidths●

QoS is not part of H.323Consequences ● Time problems due to large E-mail attachments and web surfing

● Network congestion due to multiple requests for the same web page● Reduced voice quality due to

– Delay – Jitter – Packet loss

Goals: ● QoS is required in the WAN/LAN for – Optimum voice quality for every connection – Fewer interruptions




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HiPath’s Network Analysis Service

4.3 HiPath’s Network Analysis Service

Product Description

Network analysis examines whether the customer’s communications network is able to supportSiemens Business over IP solutions. The assessment is carried out on the basis of product-specific parameters. The customer receives a final report which documents not only the net-work structure but also operative parameters (capacity, delay, jitter).

Customer Benefits and Profitability

● Preparation of the network for future applications (VoIP)● Determination of current traffic flows and volumes, baselining● Support in decision-making process when introducing VoIP solutions


Network Analysis features specification

● Inspection of customer networks to determine suitability for Siemens Voice over IP solu-tions

● Recording of the relevant parameters over a defined period.● Assessment based on product specifications● Interpretation of the recorded results with suggestions for further measures● Final report with recommendations

Configuration Instructions

Used for the development of Siemens VoIP solutions

Use only possible in SNMP-based IP data networks (router, IP switches, hubs)

Positioning within the Product Range

HiPath services



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



LIM Board for LAN Connection

4.4 LIM Board for LAN Connection

The LIM module allows the cost-effective connection of all HiPath 3000 models in TCP/IP-based LANs for the central system administration, APS transfer, TeleData Office or HiPath Fault

Management. A 10 MB 10BaseT interface with an RJ45 jack is available for the LAN connec-tion.

Up to 6 TAPI 120 V2.0 can be operated via the LIM module on HiPath 3000 V4.0 SMR6 or later.However, a maximum traffic value of 400 BHCA is permitted.

Power dialers are not released for use.

>Systems which already have a HG 1500 board do not require the use of the LIMboard as the above-mentioned functions are already provided by HG 1500.

HiPath 3000/5000

e.g. PC withHiPath 3000/5000 Manager E

Central Board

LIM

CustomerLAN

e.g. PC forNetwork Management

SNMP




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5 HG 1500

Overview

Voice over IP (VoIP) - the transfer of voice data over IP networks - is enabled in HiPath 3000 bymeans of the HG 1500 boards.

The H.323 communication between networked HiPath 3000 systems (nodes) must be consid-

ered as gatekeeper to gatekeeper communication. Registration between HG 1500 modules ofnetworked systems is not performed. The CorNet-NQ protocol, tunnelled in H.323 via annexM1 is used.

The splitting of HG 1500 resources into signaling and payload resources is an important fea-ture.

HiPath 3000/5000

Central Board

ISDN Board

HG 1500

CustomerLAN

ISDNtelecommunica-tions network)

HiPath 3000/5000

Central Board

HG 1500

CustomerLAN

ISDN Board

Voice over IP Voice over IP

e.g. OpenScape Personal Edition PCs for Internet connection, VoIP,administration etc.

e.g. optiPoint 410



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

Signaling Resources

This includes all node signaling data necessary for Voice over IP for IP-supported (LAN, intra-net, Internet) and line-switched networks (ISDN, PSTN). These resources are centrally provid-

ed by a single HG 1500 board, the signaling gateway (= Gatekeeper HG 1500), regardless ofhow many HG 1500 boards are available at the node. A HG 1500 board is defined as a gate-keeper HG 1500 using HiPath 3000 Manager E.

Payload resources

The node resources required for transferring VoIP voice data (payload) between IP-supportedand circuit-switched networks are provided by the media gateway. One or more HG 1500boards may be used.

Payload resources are not necessary for direct transmission between IP-supported networks.

In the case of systems with only one HG 1500 board, this board operates both as a signalinggateway and as a media gateway when configured appropriately by HiPath 3000 Manager E.

In the case of systems with more than one HG 1500 board, payload resources are monitoredby the node-central resource manager. This is a self-configuring service. Signaling resourcesare centrally provided by the first HG 1500 board. This signaling gateway also accesses othermedia gateway resources (codecs, B channels) and signaling data (for example RTP, RTCP).This gives IP workpoint clients and other gateways access to central payload resources of allHG 1500 boards in a node.

Resources for functions which are not based on H.323 (for example, routing channels, vCAPI

channels), are provided as before by each HG 1500 board. In systems with several HG 1500boards, resources are provided exclusively by media gateways for performance reasons.

Features of HG 1500 V3.0 or later

● Transparent B channel for ISDN B channel protocols

● Flexible port number administration

● Dynamic jitter buffer

● SNTP functionality in the LAN

● Read rights to dynamic parameters of HiPath 3000 Manager in WBM

● Improved firewall function (stateful inspection, DoS, application level gateways)

● T.38 fax protocol standard support

● HFA workpoint support

● Logging of QoS data (Quality of Service)

● Licensing system as for HiPath 3000/5000




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

● Improved software management

● Cooperation with HiPath 4000 V2.0 and later systems, for example, DMC (Direct MediaConnection)

● Full VPN support (Virtual Private Network)

● HG 1500 as a module of a PCS (PC-based communication server)

● STMI2 board with 32 B channels onboard, expandable to 64 channels

DMC

This flag enables or disables the feature "DMC Interworking with HiPath 4000 Systems" (inshort "DMC"). In a network with HiPath 4000, DMC enhances the voice quality between IP com-ponents (endpoints, gateways).

DMC is supported via the networking protocols SIP-Q V2, CorNet-NQ and CorNet-IP. In HiPath3000 V8 and HiPath 4000 V5 and later systems, only SIP-Q V2 protocol is used for IP network-ing between these systems and only CorNet-NQ is used for TDM networking. The CorNet-IPprotocol is no longer supported.

DMC should be disabled in a homogeneous HiPath 3000/5000 network. If a network with Hi-Path 4000 systems (version 2.0 or later) exists in which DMC is configured, the DMC featureshould be enabled in the HiPath 3000/5000 systems.

The HFA endpoints registered at the HiPath 3000/5000 system and the HiPath 3000 systemitself are then in a position to accept DMC connections set up by the HiPath 4000 and its HFA

endpoints. Even if the DMC feature is enabled, DMC is not performed between HiPath 3000/ 5000 systems.

If DMC is enabled, the percentage of available DSP channel resources decreases. In otherwords, in a HiPath 3000 system only 80% of the channels provided for each DSP are availablefor connections (for example, 6 channels instead of 8, 12 channels instead of 16, 48 channelsinstead of 60).

Hardware notes

HG 1500 is:

● the HXGS3 board in HiPath 3550 and HiPath 3350

● the HXGR3 board in HiPath 3500 and HiPath 3300

The power supply comes from the system.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

System requirements for HiPath 3000/5000

● At least one Euro ISDN basic connection(connection to the network or another HiPath system)

● At least one free slot in the basic system

System environment

● Shared/switched LAN 10/1000 Base T

● Client/server and peer-to-peer networks with TCP/IP protocol




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.1 Protocols

This section contains an overview of H.323 standards regarding signaling and media protocolthat are relevant to HG 1500 V3.0.

H.225.0 Q.931 Call Setup

This protocol defines signaling between two endpoints for call setup and cleardown.

H.225.0 RAS Control

RAS (Registration, Admission and Status) defines signaling between client and gatekeeper fordetection and registration purposes.

H.245 Signaling

This protocol defines the declaration of capabilities and exchange of control messages be-tween endpoints. It is used for specifying channel usage and functions.

H.323

This is a standard for packet-oriented multimedia communication systems and was developedby the ITU (International Telecommunication Union. HG 1500 V3.0 uses H.323 V4.0 but canalso communicate with earlier versions of the H.323 protocol (backward compatibility is guar-anteed).

Fast Connect (fast start) is supported. The Fast Connect feature lets HG 1500 V3.0 set up amultimedia channel without waiting for an H.245 connection.

RTP and RTCP

RTP (Real-time Transport Protocol) manages the transfer of real-time packets from an end-point to one or more endpoints.

A header containing a time stamp and a sequence number is added to every UDP packet. Withappropriate buffering at the receiving station, timing and sequence information enables the ap-plication to:

●

eliminate double packets,● rearrange nonsequential packets,

● synchronize data,

● achieve continuous playback despite varying latencies.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

RTCP (Real-time Control Protocol) is used for controlling RTP. It enables:

● Quality of Service (QoS) monitoring,

● transferring of information about session participants,

● regular distribution of control packets containing quality information to all session partici-pants.

TCP

TCP (Transmission Control Protocol) provides a connection-oriented mode for data transmis-sion. TCP guarantees a sequenced, error-free, flow-controlled transmission of data packets.However, this can delay data transfer and reduce throughput. H.323 uses the end-to-end ser-vices of TCP for the H.245 control channel, data channels and the call control channel.

UDP

The UDP (User Datagram Protocol) provides a connectionless transmission mode that prom-ises nothing more than a "best effort" delivery. Only a minimum of control information is trans-ferred with UDP. H.323 uses UDP for audio, video and the RAS channel (see RFC 768).

Control Control ControlData Audio VideoA/V




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.1.1 Protocols Used

PPP Point-to-Point Protocol Transport protocol between LAN and SCN

PAP Password Authentication Protocol Transport protocol for ID and password

CHAP(MSCHAP)

Challenge HandshakeAuthentication Protocol

Transport protocol for encrypted ID and pass-word (MS = Microsoft-specific protocol)

IPCP IP Control Protocol Transport protocol for IP addresses

PPPoE PPP over Ethernet Protocol Transport protocol between LAN and SCNover Ethernet

PPTP Point-to-Point Tunneling Protocol Transport protocol for tunneled PPP connec-tions

IP Internet Protocol Transport protocol for data transfer to IP orMAC addresses without a connection

ICMP Internet Control MessageProtocol

Control protocol that supports IP protocolwith error messages

UDP User Datagram Protocol Transport protocol for data transfer without aconnection

TCP Transmission Control Protocol Transport protocol for connection-orienteddata transfer

DHCP Dynamic Host ConfigurationProtocol

Protocol for dynamic configuration of hostsystems

ARP Address Resolution Protocol Protocol for linking IP addresses with MACaddresses

FTP File Transfer Protocol Protocol for file transport between networknodes

TFTP Trivial File Transfer Protocol Simple file transport protocol

RTP Real-time Transport Protocol Transport protocol for real-time audio and vid-eo packets

RTCP Real-time Control Protocol Control protocol for RTP

HIP HDLC Internet Protocol Control protocol for transferring encapsulateddata in the Internet

Telnet Protocol Dial-in protocol for remote access via the In-ternet

Table 4-13 Protocols Used



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.2 Security/Firewall/Packet Filter

HG 1500 features status-dependent control filters. The status-dependent control checks areperformed over "flows". A "flow" is stream of associated packets and all the error ICMPs (in-cluding path-MTU messages) that affect these packets. In TCP terms, a flow is defined on thebasis of IP addresses and port numbers, and consists of both the TCP packets and all associ-ated error ICMPs. This is similar for UDP.

DoS: HG 1500 offers protection against various Denial-of-Service attacks and other network-level attacks, such as, SYN flooding, various fragmentation attacks, TCP hijacking (different ac-tive attacks, for example, via ARP spoofing), LAND (identical source and destination IPs), so-called "Christmas trees" (all TCP flags set), etc.

H.225.0 Annex G Signaling protocol for edge gatekeepers indifferent domains

Q.931 Signaling protocol for call setup and clear-

down between two endpointsRAS Control Defines signaling between client and gate-

keeper for detection and registration

H.235 Standard Signaling protocol for authentication and en-cryption

H.245 Standard Signaling protocol for defining usage of func-tions and channels

H.323 Standard Transport protocol for packet-oriented multi-media communication systems

H.341 Standard Definition of Management Information Basefor controlling and administering an H.323network

H.450 Standard A series of protocols that define signaling be-tween endpoints for supplementary services

HTTPHTTPS

Hypertext Transfer Protocol (Se-cure)

Transport protocol for transferring text andgraphics in the Web (secure connection)

SNMP Simple Network ManagementProtocol

Connection protocol for network manage-ment systems

Table 4-13 Protocols Used





3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

Available functions

The following functions are available for IP networking:

● Central attendant console

A specific system terminal (subscriber) can be configured as an attendant or intercept po-sition. Any incoming call to the system will arrive here automatically if no subscriber can beassigned to it, although the call may originally have come in on any one of the nodes con-nected via IP networking.

The central attendant console can then forward these calls to the required subscriber.Again it does not matter which node the station is logged on to.

Once the attendant queue reaches a predefined length, calls can be automatically forward-ed to an overflow destination.

Cross-node busy signaling is available when using optiClient Attendant.● Virtual ports

Virtual ports are used for the signaling of statuses and calls on all systems. They are notlinked to physical terminal interfaces. The corresponding boards must not be inserted. Vir-tual ports have their own internal and external phone numbers and can therefore be called.They can be programmed for signaling on DSS keys and be added to call pickup groups.

● DISA Internal (Direct Inward System Access Internal)

When using Internal DISA Intern (not to be confused with External DISA Extern) certainfeatures in a node can be activated by stations of a different node:

● Release of the door opener using the relay option

● Follow me

● Relay on/off

● Night service

● Disconnecting from a hunt group/group call

● System Speed Dialing

A redundant central speed-dial directory is maintained from which the local speed-dial di-

rectories of all nodes is updated. This means that IP telephones connected to the HG 1500V3.0 have access to the speed-dials as TDM phones.

● CO Call Privileges and Toll Restriction

The call privileges configured per node is transferred via CorNet-N in converted format.Permitted and denied lists of a station can only be evaluated in the node in which the sta-tion is configured. The dial plan can be used to specify where the toll restriction is to beexecuted. Please note that in this process all allowed numbers and denied numbers lists




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

are mapped to "Can access local public network". This in turn is mapped to denied num-bers list 1 in a subsequent node. Consequently, it is possible that in a subsequent node atoll restriction with denied numbers list 1 will be set up again or added.

● Least Cost Routing (LCR)LCR is possible via both the trunk connections and the IP connections. The dial plans ofeach node can be configured individually. If so configured, "Fallback to SCN" function canbe used to forward a call automatically to an SCN connection if the IP connection fails.

When an external call is forwarded to another node (transit break-in), the caller’s numberis converted automatically to the international format.

The seizures codes used to date are replaced by port numbers. This type of configurationis better suited for a LAN environment.

● Music on Hold (MOH)

In a HiPath server node, a PCM/IOM channel can be permanently connected to MOH. Thischannel is permanently connected to a DSP channel that forwards MOH unidirectionally toone or more IP clients or other HG 1500 boards. MOH for IP clients always requires onlyone DSP channel. (Normal clients cannot benefit from this; for MOH, they require an addi-tional a PCM/IOM and a DSP channel respectively.)

The channel for MOH is automatically assigned by the system.

● Direct Station Select (DSS) and Busy Lamp Field (BLF)

The DSS functionality - signaling of call-processing station states – is available to all termi-nals in the system, also to those on different nodes. This provides a system-wide call pick-up solution, and is completely transparent to the terminal user programming the DSS keys.

● CorNet IP

The protocol CorNet-IP with which CorNet features are tunneled via IP is supported. Thismakes the functional scope of the CorNet protocol available to IP terminals as well. Moredetails of these functions can be found in "HiPath 5000 RSM System Description", Chapter3, "Features".

● SIP-Q

In HiPath 3000/5000 V7 or later it is possible to network via SIP-Q V2 with HiPath 2000/ HiPath OpenOffice EE, HiPath 3000, HiPath 4000, HiPath 5000 and OpenScape Voice.

>

The CorNet IP protocol is not supported in HiPath 3000 V8 and HiPath 4000 V5or later systems for IP networking these systems.

>In HiPath 3000 V8 and HiPath 4000 V5 and later systems, only SIP-Q V2 proto-col is used for IP networking between these systems and only CorNet-NQ isused for TDM networking. CorNet IP protocol is no longer supported.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.4 Voice over IP (VoIP)

Voice over IP (VoIP) enables voice data to be transmitted over an IP network, both internallyand via the Internet.

Voice over IP (VoIP) is an outstanding feature of HG 1500 V3.0. In combination with the clientsconnected to the LAN, the board makes it possible to use not only VoIP but also the telephonyfeatures of the system. In particular, this feature can be used for teleworking. This means thatfull Voice over IP functionality is available at the teleworking PC. H.323 clients (for example Net-Meeting) can also be used.

As of the HiPath 3000 V3.0 software version in combination with new boards (HXGS3,HXGM3, HXGR3), login is no longer performed under "Voice Gateway" in HiPath 3000 Manag-er I but in HiPath 3000 Manager E.

The following combinations of VoIP connections via the HG 1500 V3.0 are possible:

● IP to IP, for example, subscriber C to subscriber D or subscriber D to subscriber F.

● IP to local SCN, for example, subscriber D to subscriber B.

● Local SCN to IP, for example, subscriber B to subscriber C.

● IP to PSTN, for example, subscriber C to subscriber E.

● PSTN to IP, for example, subscriber E to subscriber D.

Interworking is fully supported.

With the exception of IP to IP connections, one DSP channel per connection is required foreach HG 1500 V3.0 involved. Conferencing requires one DSP channel for each SCN subscrib-er.

This can lead to significant call charge savings if an appropriate IP network is available. Theuser can also avail of telephony features, such as name transmission and callback, in the usualway.

The hardware prerequisite for IP networking is that the systems involved must have at least oneof the following HG 1500 V3.0 boards:

● STMI2: Up to eight boards can be used per system (max. four boards per HiPath 3800 cab-inet).

>Internet telephony features are described in detail in the feature description.

>In IP networking, SCN to SCN connections (local or PST) also can be run transpar-ently via the HG 1500 V3.0. This is described in Section 4.5.3, "IP Networking".




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

● HXGS (wall housing) or HXGR (19" housing): Up to four boards can be installed in HiPath3500/3550 and up to two in HiPath 3300/3350. Both boards can process up to 16 IP chan-nels for voice connections with a single PDM1 expansion module.

The IP networked systems and the HG 1500 V3.0 boards are administered with two differenttools:

● HiPath 3000 Manager E: Extending the existing HiPath 3000 customer database to includeinformation for IP networking.

● HG 1500 V3.0 WBM: Performing HG 1500 V3.0 board settings.

4.5.4.1 General Parameters for Voice over IP

Before configuring system clients and H.323 clients, you must configure the valid parametersfor both variants in HiPath 3000 Manager E:

● Echo:You can define here how to compensate for the echoes that occur in connections to con-ventional telephones via the voice gateway.

● Traffic statistics:This is where you define whether to record traffic statistics which can then be queried via

SNMP.

● Encoding:This parameter is used to select which voice coding will be implemented.

4.5.4.2 Voice Coding

HiPath 3000/5000 supports voice compression according to the G.729 and G723.1 standards.G.723.1 facilitates the use of teleworking via ISDN for example, and reduces the load on theexisting data network. G.723.1 reduces the VoIP bandwidth requirement for voice communica-tion. This enables a bidirectional voice connection via an ISDN B channel. This, in turn, facili-

tates the connection of teleworkstations or branch offices to the company network via a 64 KBconnection. However, it is not advisable to operate other applications (such as ApplicationSharing, File Transfer) in addition to a bidirectional VoIP connection simultaneously via 64 Kbpssince this generally leads to a deterioration in voice quality. It is recommended that both B chan-nels of an S0 connection are used for this purpose.

>The IP address used for IP networking is always that of the first LAN interface. If IPnetworking is routed via another interface, such as LAN2, use IP routing entries toensure that the LAN1 interface can be reached.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

The HG 1500 V3.0 supports codecs for compression and decompression of voice signals in ac-cordance with industry standards G.711 A-law, G.711 µ-law, G.723, G.729A and G.729AB. Thecodecs can be arranged according to their priority. The gateway automatically attempts to usea codec with the highest possible priority for each connection.

The HG 1500 V3.0 supports the following codecs:

● G.711 (A-law and µ-law) voice coding – an ITU (International Telecommunication Union)standard for voice coding at 56 or 64 Kbps

● G.723.1 voice compression – an ITU standard for voice coding at 5.3 or 6.4 Kbps

● G.729A and G.729AB voice compression – an ITU standard for voice coding at 8 Kbps

4.5.4.3 DTMF Handling

DTMF (Dual-Tone Multifrequency) is the type of audio signal used for tone dialing in accor-dance with ITU-T standard Q.24. It can be used for call setup and for signaling during a call.

HG 1500 V3.0 supports the detection and processing of DTMF (Dual Tone Multi Frequency)signals in accordance with Q.24 regarding signaling for VoIP calls. In particular, it supports thefollowing functions:

● Detection of DTMF signals

● Conversion of DTMF signals into user input signals in accordance with H.245

● Generation of DTMF signals for PSTN

● Speech protection using Bellcore test tapes

● Sending and receiving DTMF signals via vCAPI

4.5.4.4 Voice Quality

Various HG 1500 V3.0 functions ensure optimum voice quality during VoIP connections. Fur-ther details are described below.

Quality of Service (QoS)

QoS enables voice packets to be given higher priority than other packets in the IP network sothat voice quality is influenced as little as possible by other data traffic.

To ensure the best possible quality especially for voice connections, the HG 1500 V3.0 sup-ports various QoS protocols:

● IEEE802.1p tags (layer 2)

● Type of Service (ToS) prioritization (RFC 791, layer 3)

● Differentiated Services (DiffServ; RFC 2474, layer 3)




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

The gateway observes these standards for routed packets and makes them available for appli-cations on the gateway, such as vCAPI.

Echo suppression

The HG 1500 V3.0 supports echo suppression in accordance with G.168 to ensure acceptablevoice quality in the WAN. Echo suppression is effective for round trip delays of up to 48 msec.

Dynamic jitter buffer

The dynamic jitter buffer eliminates the distortion caused by fluctuations in the arrival of voiceand video packets. Individual packet delays can be a result of network overload or internal pro-cessing within the LAN endpoints.

The HG 1500 V3.0 jitter buffer can be configured for the connection requirements of a specific

network.

Voice Activity Detection

VAD (Voice Activity Detection) checks all incoming signals for voice signals. If a signal exceedsa preset level, the VAD recognizes it as voice and anything under that level as silence.

The HG 1500 V3.0 provides VAD and silence suppression for all supported codecs. When novoice signal is detected, a background noise is inserted at each end of the line to emulate tra-ditional telephone line conditions.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.4.5 Environmental Requirements for VoIP

To ensure voice transfer quality and avoid unacceptable delays, the networks being used mustmeet certain requirements.

Environmental Requirements in the LAN

LANs used for VoIP must meet the following specifications:

● At least 256 Kbps transmission capacity per networked unit

● Not more than 50 msec delay in one direction (One Way Delay) Not more than 150 msectotal delay

● Not more than 1% packet loss

● QoS support – IEEE 802.1p, DiffServ (RFC 2474) or ToS (RFC 791)

● Every HG 1500 V3.0 must be connected via a switch or a dedicated port of a router.

● It is recommended that the VoIP application be connected via a separate VLAN to reducecollisions with other transmissions. If all involved devices support VLAN (in accordancewith IEEE 802.1q), all VoIP traffic can be placed in a separate VLAN. For administrationaccess in this case, LAN switches must provide individual computers with access to multi-ple VLAN segments.

● Not more than 20% of the available bandwidth should be used.

● Not more than 10% of the total data traffic should be broadcast packets.

● The error rate should not amount to more than 1% of data traffic and should not tend toincrease.

Environmental Requirements in the WAN

LANs that are linked over WANs and share the same VoIP functionality must meet the followingminimum requirements:

● Each LAN must each be connected to the Internet via xDSL with a fixed IP address.

● QoS support – IEEE 802.1p, DiffServ (RFC 2474) or ToS (RFC 791) – over the entire con-

nection● The bandwidth required for the calls must always be available in both directions, to the net-

work and to the user.

● Not more than 50 msec delay in one direction (One Way Delay) Not more than 150 msectotal delay

● Not more than 3% packet loss

● Not more than 3% error rate




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

● Not more than 10% jitter

● As little broadcast and multicast traffic in the network as possible. If necessary this can beachieved by structuring the network – using VPN, for instance – with Layer 3 switches and

routers, or with Layer 2 switches that recognize multicasting.

● Not more than 40% network load (without VoIP traffic)

● Less than 40 broadcast packets per second if possible

Environmental requirements for fax/modem over G.711

Fax/modem over G.711 can be enabled if the IP network satisfies the following requirements:

If the above values are not observed in the IP network, the fax or modem transmission may beinterrupted.

Value Time

Jitter <= 20 msec

Delay (one way) <= 50 msec

Delay (round trip) <= 100 msec

Packet drop <= 0.05%

Table 4-14 Prerequisites for Modem over G.711



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.5 Fax over IP with HG 1500 V3.0

Fax over IP guarantees the compatibility of traditional analog fax devices in IP telephony net-works. The following scenarios must be taken into account when using the real-time communi-

cation system HiPath 3000 with the HG 1500 V3.0 board.

For Fax over IP the IP network must meet certain quality criteria that are determined in the net-work analysis as otherwise interruptions can occur in the fax transmission. Otherwise the con-nection and marketing of separate trunk lines should be provided for each node.

In general, an IP trunking network is when two or more HiPath 3000 systems are networked toeach other over the integrated HG 1500 V3.0 board. The HG 1500 V3.0 board supports twofunctions for transferring the fax information.

● Fax over G.711 ("IP/IP e2e payload via enterprise proxy" connection)

The advantage of E.711 is that (unlike T.38) high speed faxes (in other words faxes with atransmission rate > 14400 bps) can also use this higher transmission rate on a good net-work, while high speed faxes must be slowed down to a speed of 14400 bps when T.38 isused.

● T.38

T.38 is an ITU standard that describes how two fax machines communicate over IP. Thisstandard refers to a real-time transmission of fax documents because the formats for trans-mitting the signalling and user data between two gateways are described here.The image data (T.4 or T.6 format) and control messages (T.30 format) are packed in spe-cial T.38 messages and sent via the IP network. The packets are either used with TCP(Transmission Control Protocol) or UDP (User Datagram Protocol).

The advantage of T.38 is that it is more resistant topacket loss and jitter in less than perfect network conditions. For more information, refer tothe service manual.

The functions were tested on the following devices:

– Siemens HF2323

– Siemens Fax 790

– Canon Fax B155,

– Hewlett-Packard OfficeJet Model 635,

– OKI OKIFAX 4580,

– OKI OKIFAX 4550,

>At present HG 1500 V3.0 only permits transmission with UDP and not with TCP.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

– Samsung SF-350,

– Philips magic 2 primo

UDP

This protocol is an non-secure connection. IP packets are sent without knowing whetherthey are received. Thus, this procedure has a number of disadvantages. If you are not surethat the information has been received, then greater effort is required to secure this infor-mation.

Security mechanisms

● FEC procedure (Forward Error Correction)

In this procedure, every "mandatory message" is given a number of previously com-pressed packets. The number of FEC packets sent with the message is indicated in a

supplementary field that can change at any time. To enable the remote station betterto identify the packet sequence, each "mandatory message" is given a "sequencenumber".

● Redundancy procedure

In this procedure, additional IFP pages are sent with a "mandatory message". Thenumber of "redundancy messages" is defined in advance and cannot change duringtransmission. The "mandatory message" is given a "sequence number" to enable thepackets to be identified clearly.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.6 Fax over vCAPI

In the case of Fax over vCAPI, virtual fax devices are connected to a LAN and the HG 1500V3.0s replace the S0 cards in the customer PCs. These virtual stations are installed at a PC

and exchange their fax information over a separate specially developed interface. The CAPIprotocol was used as a basis to provide the same functionality as a PC card. This informationis then processed in the HG 1500 V3.0, packetized into T.30 messages and converted by a spe-cial component (DSP) into 3.1 kHz audio PCM signals.

vCAPI Connections

The virtual fax device is installed as a software application in a PC. A special driver is used forconnection to the HG 1500 V3.0. Starting up the application activates the PC and the HG 1500V3.0 board and enables the fax functionality.

The only restriction that applies concerns the number of VCapi PCs that can send faxes simul-taneously. The HXGS board supports two simultaneous faxes and the HXGM board supportsthree simultaneous faxes.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.7 Modem via IP

As for the encapsulation of voice transmission on IP routes, the HG 1500 V3.0 can also routeanalog data between modems over an IP connection.

This function enables connections to be made between traditional analog modems in IP net-works. The HG 1500 board supports different functions for transferring the information:

Modem over G.711 Voice Codec (recommended)

Like faxes, modems can be used to switch a transparent connection over two networked sys-tems with the G.711 voice codec.Special limits in terms of delay, jitter, and packet loss network parameters must be taken intoaccount for the IP network. This function does not support compressed transmission (G.723).The transport and security protocols that can be used depend on the modems in operation and

not on the HG 1500

V.90 Standard

The V.90 Standard (56K) is supported in the "modem over G.711" procedure. Please note,however, that an approximate speed of 56 Kbps is only reached in the downstream direction

Bit Rate Adaptation V.110

The HG 1500 supports V.110 bit rate adaptation to guarantee remote access with GSM termi-nals using asynchronous PPP. However, this only supports the conversion of GSM-specific

data transmission speed of 9600 bps into the ISDN bit stream of 64 Kbps.

4.5.8 HiPath Feature Access (HFA)

HiPath Feature Access (HFA) provides telephones and clients connected via IP with all thefunctions that can also be used by TDM telephones in HiPath networks. For this purpose, Cor-Net TS protocol – with which the terminals are addressed – is tunneled over IP.

In connection with a HG 1500 V3.0, IP telephones/clients are then equivalent to the classicTDM telephones on a HiPath system.






A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

The HG 1500 V3.0 can also set up a PPP connection to an ISP via one or more B channels.This connection, too, can be used simultaneously by multiple clients in the IP network.

4.5.9.1 PPP, PPPoE and PPTP

The HG 1500 V3.0 supports PPP (Point-to-Point Protocol) for both incoming and outgoing SCNconnections. PPPoE (PPP over Ethernet) and PPTP (Point-to-Point Tunneling Protocol) aresupported for devices on the second LAN interface (typically an xDSL modem).

Connections from the LAN to the SCN are set up on the basis of the IP address addressed by

the LAN. The IP address is converted to a station number (this requires appropriate configura-tion of the routing and dial tables). A prerequisite is that the remote station has a static IP ad-dress.

After the connection has been set up, the HG 1500 V3.0 can accept a dynamic IP address.Packets for terminals in a local IP network are converted with NAT (see Section 4.5.9.2, "Net-work Address Translation (NAT)").

There are various security and authentication mechanisms for PPP connections. Further de-tails can be found in Section 4.5.9.3, "Access Protection".

Figure 4-3 HG 1500 V3.0 as Internet Gateway (ISDN)

(PC in the LAN) (PC in the LAN)

Switch

HiPath 3000

mit HG 1500

Internet

PSTN



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.9.2 Network Address Translation (NAT)

Network Address Translation (NAT) is the conversion of IP addresses in the LAN for the Inter-net. HG 1500 V3.0 provides NAT for Internet connections via a second Ethernet interface as

well as for PPP connections via B channels.

As far as the Internet is concerned, the entire LAN appears to be a single IP address and cantherefore use a common dial-up connection to an ISP, for example. Additionally, direct IP at-tacks from the Internet on terminals in the LAN are not possible.

NAT can be enabled and disabled in the HG 1500 V3.0. Certain services – such as VoIP or vid-eo telephony – embed subscribers’ IP addresses in their data packets, however, instead of justnoting them in the packet headers. They are only compatible with NAT within a VPN.

4.5.9.3 Access Protection

A variety of security functions are available to prevent unauthorized usage:

Checking Caller Numbers

Connections from the PSTN can be checked against a list of known users using the caller num-ber. Users whose connections do not transmit a caller number (for example analog telephones)can call an MSN that is set up especially for them.

Callback

All users can be configured so that they can be called back. Thus, PPP connections are only

possible from a predefined connection.

User Account and Password

After setting up a connection, the user account and password can be checked using PAP (Pass-word Authentication Protocol), CHAP (Challenge Handshake Authentication Protocol) or MSC-HAP (Microsoft Challenge Handshake Authentication Protocol.

HG 1500 V3.0 also supports these protocols as a client when dialing in to a RAS server (forexample with an ISP).

IP Address Filter for Communication with the LAN

IP address filters can be defined to prevent attacks on devices in the LAN, both from insecure(external) networks and from within the LAN. When IP filtering is activated, access is only pos-sible from address ranges that have explicit permission, and this access is only possible tospecified addresses. Optionally, access can be further limited to a specific protocol port.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

MAC Address Filters for Using the Gateway from within the LAN

MAC address filters can limit access to the router from devices within the LAN. When MAC fil-tering is activated, only devices within the LAN whose IP and MAC addresses have explicit per-

mission to do so may set up a connection via the HG 1500 V3.0. (This function cannot be de-fined with dynamic IP address allocation in the LAN via BootP or DHCP).

Access Protection for Administrative Access

General administrative access and access to accounting data can each be separately limitedto specific IP addresses, regardless of any other IP filters.

4.5.9.4 Multilink

The HG 1500 V3.0 can set up static or dynamic PPP connections with a remote station via sev-

eral B channels simultaneously.

A static multilink uses the same number of B channels for the duration of the connection. A dy-namic multilink adds or removes channels depending on current channel load. These parame-ters can be configured.

4.5.9.5 Short-Hold

After a preconfigured time period with no data transfer over a PPP connection, the HG 1500V3.0 can clear down the connection automatically.

4.5.9.6 IP Control Protocol (IPCP)

The HG 1500 V3.0 supports the IP Control Protocol (IPCP) for dynamic handling of IP address-es during connection setup.

4.5.9.7 Compression of IP Headers

Significant protocol overhead can develop, especially during voice data transmission whereuser data in a packet is typically short. To improve the situations, the HG 1500 V3.0 supportsthe compression of IP headers according to RFC 2507 and RFC 2508. The compression is ne-gotiated during the configuration of the connection with the receiver in accordance withRFC 1332 and RFC 2509.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.9.8 Data Compression

User data in a PPP connection can be compressed with the STAC or the MPPC algorithm. Thecompression for each channel is negotiated separately with the remote station.

4.5.9.9 IP Accounting

HG 1500 V3.0 saves information about transferred data for the purposes of IP connection ac-counting.

Accounting data is saved for:

● PPP connections via SCN

● DSL connections

● Routing via the LAN2 Ethernet interface

The following information is saved:

● Data volume (sent and received)

● IP addresses (sender and recipient)

● Port number of the recipient

● TCP or UDP protocol ID

● Time (start of transfer and last activity)

● For PPP connections: Address and station number of PPP peer

Reading the Accounting Data

The Accounting Server (ACC) saves the data in the gateway. This data can be read out by theIP Accounting Client – an application on a PC – by means of a TCP connection, and then pro-

cessed - for billing, for example. The IP accountingclient is a supplementary product; instructions for its use are described in the accompanyingdocumentation.

The IP Accounting Client must be connected to the gateway via a permanent IP connection.

To ensure data protection, a user name and password must be entered before the read-out. Itaddition, it is also possible to specify that reading is onlypossible from certain IP addresses.

>For poor connections, we recommend using the MPPC algorithm, which is very use-ful for resynchronization.Further information on both algorithms can be found in RFC 1974 (STAC) or RFC2118 (MPPC)




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

IP Accounting must be activated and the connection parameters set for the IP Accounting Cli-ent before it can be used. Both configurations are described in the HG 1500 V3.0 ConfigurationManual.

4.5.9.10 vCAPI

PC software usually accesses ISDN lines via CAPI (Common ISDN Application Interface).CAPI requires an ISDN adapter be directly connected to the relevant computer.

CAPI access is possible via local networks using vCAPI (Virtual CAPI). vCAPI functions ac-cording to the client/server principle: Client software is installed on the PC as a DLL and for-wards all CAPI requests transparently to the server, which is a process on the HG 1500 V3.0.

This way, all PCs connected via a LAN to the gateway can transparently utilize all the CAPI-enabled software (e.g. CAPI-enabled software for Fax Group 3) in order to access the HG 1500

V3.0 ISDN connections, and do not need additional hardware.

Incoming connections can be forwarded directly to a PC’s vCAPI client using up to 100 callnumbers reserved for this purpose. Each station number is assigned to an IP address. To theCAPI software on that PC, these incoming calls appear to be calls on a physical local ISDNadapter.

The HG 1500 V3.0 vCAPI implementation supports CAPI 2.0.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.10 Virtual Private Network (VPN)

Virtual Private Networks (VPN) connect individual computers and local networks via the Inter-net to form a closed virtual network. Communication in a VPN is tunneled through the Internet

(encapsulated) and is protected from tapping and access by third parties such as Internet usersand providers that are not a part of the VPN. A VPN enables an intranet to be extended beyondthe LAN, for example to home workstations or branch offices, without requiring a dedicated line.

Figure 4-4 VPN - Sample Configuration

A VPN provides the following key functions:

● The tunnel endpoints (gateway or teleworker PC) are reliably identified.

● Exchanged data is protected from tapping during transmission.

● Exchanged data is protected from being modified during transmission.

HiPath 3000with HG 1500

HiPath 3000with HG 1500

Teleworker A

VPN tunnel

Switch

Switch

LAN B

LAN C




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

A VPN therefore guarantees that data actually comes from where it appears to have come from.that they are transferred from there unaltered; and that they are not made known to a third partyon the way.

The HG 1500 V3.0 provides this function based on IPsec – a secure implementation of the IPprotocol on level 3. This ensures that the VPN is transparent to applications as well as hard-ware.

The VPN security functions are available for LAN connections (for example LAN B and LAN Cin Figure 4-5). In this case, they are completely transparent to the computers participating inthe LANs. They can also be used for connecting individual computers (teleworkers), for exam-ple, teleworker A in LAN B in Figure 4-5). in this case, the VPN client software installed on theteleworker PC must be compatible with the VPN functions of HG 1500 V3.0.

A VPN (Virtual Private Network) is a network where communication is protected as far as hu-manly possible against tapping, clandestine modification and the misrepresentation of fake tun-nel endpoints.

The required protocols are available in the HG 1500 V3.0. Before a VPN can be created, how-ever, the gateway itself, and especially its administration, must be made secure against attacks.

4.5.10.1 Secure Mode

Unless special measures are taken, HG 1500 V3.0 operates in non-secure mode. This means,among other things, that administration access is not encrypted during transmission over thenetwork.

The gateway recognizes the following security modes:

● Factory mode: has no configuration data.

● Insecure mode: gateway is configured, SSL and VPN are disabled. Insecure data trans-mission is possible.

● Activation of SSL: intermediate status between introduction of secure mode and configu-ration of SSL. Access is only possible via CLI at the V.24 interface; no data transmission isallowed.

● Secure administration: SSL is enabled. Access via CLI at the V.24 interface and WBM (via

HTTPS) are possible. User data is transferred in insecure mode, and configuration dataand software images are transferred in secure mode.

● Secure mode: SSL and VPN are active and configured. Access via CLI at the V.24 interfaceand WBM (via HTTPS) are possible. Secure and insecure data transmission are possibleaccording to the security policy configured.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

Since a gateway in insecure mode would represent a weak point in the VPN, it must be placedin secure mode before the VPN can be configured. This requires a certain degree of effort toprevent any hackers from getting into the system during this phase of the process and under-mining the subsequent steps taken.

The following steps must be taken for the gateway to be in secure mode:

1. Connect a terminal (or a PC with a terminal emulation program) to the V.24 interface of thegateway.

2. Restart the gateway with the CLI command reset secure. When this is done, all usersettings are lost and all user data transmissions are interrupted until the gateway is recon-figured.

At this point, the gateway is in "activation of SSL" mode. In this mode it can only be config-ured using CLI at the V.24 interface – WBM, Telnet, HiPath 3000 Manager E and SNMP

are disabled.

3. The gateway must be set up for SSL mode. First, the CLI command create SSL cer-tificate must be used to generate a server certificate with which the gateway can iden-tify itself to SSL clients. After that, SSL can be activated with the enable ssl command.

At this point, the gateway is in "secure administration" mode and can only be configuredusing CLI at the V.24 interface or WBM via HTTPS – Telnet, HiPath 3000 Manager E andSNMP are disabled.

4. Start the browser for access to WBM and enter the gateway address with the protocol "ht-tps://" (you can enter the port number "443" after the gateway address). The browser dis-

plays the previously configured server certificate which must be manually checked and ap-proved. It can now also be installed in the browser to avoid future requests for it.

Use WBM to set up the VPN as described in the following section.

4.5.10.2 Security Policy

The security policy determines the procedure for IP packets. The following actions are possible:

● rejecting

● forwarding (normal routing without VPN functionality)

● tunneling (forwarding over the VPN)

The handling of IP packets can be specified in the HG 1500 V3.0 according to IP address, portnumber and protocol (TCP or UDP). For tunneled packets, you must determine:

● which algorithms for encryption and authentication are permissible on the connection,

● the period of validity for the security association.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.10.3 Security Associations

A Security Association (SA) combines an encryption algorithm and its parameters with a ses-sion key and the key’s period of validity This ensures the security of a VPN connection session.

VPN connections with the HG 1500 V3.0 always require three SAs: one for initial mutual verifi-cation of identity and exchange of keys, and one for each direction of the connection once it isset up. The SAs are negotiated using the IKE (Internet Key Exchange) in accordance withRFC2409. The required keys are exchanged with the Diffie-Hellman algorithm using OakleyGroup 2 or 5. Hash procedures available are SHA-1 and MD5.

Both the main mode and the aggressive mode are supported for negotiating the IKE securityassociation. HG 1500 uses main mode if the peer also offers main mode. Teleworkers who usepre-shared keys must configure aggressive mode.

The period of validity for negotiated security associations can be limited by time or transmitteddata volumes.

4.5.10.4 Tunnel

HG 1500 V3.0 supports up to 256 tunnels per board.

A tunnel is a secure VPN connection to another VPN gateway or a VPN client. The HG 1500

V3.0 establishes tunnels on level 3 based on IPsec.

Tunnel Configuration

For a tunnel to be set up, each terminal must be authenticated by the device at the other side.Otherwise an LDAP server is used. The HG 1500 V3.0 supports procedures that use publickeys as well as procedures based on shared secrets – similar to passwords.

For authentication using public keys, the HG 1500 V3.0 can have CA (Certificate Authority) au-thentication certificates assigned to it manually. However, it can also obtain CRLs (CertificateRevocation Lists) automatically from an LDAP server.

The HG 1500 V3.0 supports X.509 certificates for authentication of VPN subscribers. TheHG 1500 V3.0 supports DSA and RSA as public key algorithms.

HG 1500 V3.0 as Certification Authority CA

As long as no other CA is available, the HG 1500 V3.0 can, to a certain degree, act as a CA. Itcan generate pairs of public and private keys, issue and sign relevant certificates, and savekeys and their corresponding certificates to files.

>HG 1500 V3.0 also supports key exchange using the Oakley Group 1. However, thisis cryptographically weaker than the other supported groups 2 and 5 so we wouldtherefore advise against using it.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

There is, however, no option to automatically transfer such certificates to clients; every suchtransfer must be manually performed – with disks, for example.

Any subsequent certificate management, such as monitoring the period of validity or allocating

certificates to client data, must also be done manually.

The HG 1500 V3.0 can create CRLs (Certificate Revocation Lists) of certificates that are con-sidered insecure and therefore are declared invalid before the end of the normal period of va-lidity. These lists must be distributed manually.

HG 1500 V3.0 can work with certificates from external CAs. However, they can also issue cer-tificates which can be used by other tunnel endpoints to authenticate themselves in a VPN. Thisfunction is called "Lightweight CA" and requires a separate license.

4.5.10.5 Data Security

The HG 1500 V3.0 supports ESP to protect utility data during transmission over the VPN.

DES, Triple DES (3DES) and AES are available as encryption algorithms.

HMAC-SHA1 and HMAC-MD5 are supported as MAC algorithms (MAC – Message Authenti-cation Code).

The HG 1500 V3.0 supports X.509 certificates as well as DSA and RSA, two public key algo-rithms, and pre-shared keys for authenticating VPN subscribers.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.11 System Client and H.323 Client

System Client

You can configure clients with payload switching capability. While calls are signaled viaHiPath 3000, voice transfer between two payload switching clients occurs directly via the LAN.Using this procedure saves DSP resources. The transfer can occur via HG 1500 V3.0 andacross all nodes provided the required conditions are met by all the stations involved.

H.323 Client

A H.323 client on the network PC provides you with voice services that can also be used overthe Internet (prerequisite: fixed IP addresses for all subscribers and the HG 1500 V3.0). NoHiPath 3000 features are supported.

4.5.11.1 Bandwidth Management

Bandwidth management controls the bandwidth for Voice over IP between two nodes withHG 1500 V3.0 which are routed via ISDN (not usually required for LAN connections).

Five simultaneous calls can be made via one B channel if the audio codec is set to "G.723".However, the standard packetizing setting must be increased from 1 to 3. An additional B chan-nel is automatically set up from the sixth call onwards (prerequisite: two or more channels areentered for the ISDN partner). RTP compression is determined automatically and it cannot beconfigured.

If data is transferred to a routed ISDN channel at the same time as Voice over IP, the "MTU SizeFragmentation" of the relevant ISDN partner must be activated.

The compression of IP headers can be activated and the "PPP Default Header" can be deac-tivated to save additional bytes.

The value for packetizing should be set to three when Voice over IP and data transfer are per-formed simultaneously.

4.5.12 Displaying, Adding and Configuring PKI Servers

If you want to create a PKI (Public Key Infrastructure), you must configure suitable PKI serversin HG 1500 V3.0. PKI server data includes the server’s name and IP address and the servertype (LDAP).

>The entire bandwidth can be split between voice and data or reserved.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.12.1 Telematics Using the vCAPI Client

Principle of Virtual CAPI (vCAPI)

Today all users can access an ISDN card integrated in a network PC or server by installing a"virtual CAPI interface" (vCAPI) in their PCs to emulate the existence of a local ISDN card.

With respect to PC applications, the virtual CAPI interface behaves for the most part like a CAPIinterface supplied with an ISDN card. The difference is that the virtual CAPI does not forwardthe functions activated by the application directly to the card, but rather converts them into adata packet and outputs them to the LAN (client/server principle).

A virtual ISDN card is provided by HiPath 3000 to save one or more ISDN cards. A virtual CAPIinterface with the previously described functionality is installed on all network PCs (CAPI cli-ent). The messages sent by the PCs via the virtual CAPI are evaluated on HG 1500 V3.0 (CAPI

server). This information is subsequently used to set up one or more B channel connections forthe required service and to process the selected protocol.

A number of DID numbers (max. 100) must be made available to HG 1500 V3.0 for incomingcalls. Each of these call numbers must be mapped to a network address to allow an incomingcall to be switched specifically to one of the virtual CAPI interfaces. The virtual CAPI reconvertsthe Ethernet packet into the appropriate CAPI messages.

4.5.12.2 vCAPI and Smartset

Smartset is an optional CTI client which provides your PC with features such as associated di-aling from a telephone directory, caller identification using the telephone directory, answergroups and a caller list. Documents can also be opened automatically for incoming ISDN calls.Smartset exchanges data with your Windows applications using DDE functions.

Figure 4-5 vCAPI and Smartset

LAN

0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF

MNOJKLGHIPQRSTUVWXYZ

0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


PC

ISDN

PC with vCAPI, dialing from PC via HG 1500

V3.0 with Smartset (associated dialing). Incom-

ing call signaling via answer group from terminal

HG 1500 V3.0 vCAPI

server

HiPath 3300/3350, HiPath 3500/3550

or HiPath 3800




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.12.3 vCAPI and TAPI

TAPI clients

Automatic dialing can also be implemented using the vCAPI-based TAPI and an applicationthat supports TAPI. An example of this would be dialing one of the station numbers saved under"Contacts" in Microsoft Outlook.

Note that in Outlook, call numbers must be specified in international format, for example.+49(2302)999420.

TAPI for associated dialing

Associated dialing must be enabled in HiPath 3000 if TAPI functionality is to be used.

The answer group feature must be configured for the TAPI station telephone.

TAPI 120

TAPI 120 is switched on via IP. A CMD (CSTA Message Dispatcher) is required to use morethan six TAPI 120s.

TAPI 120 has more features than TAPI for associated dialing. For example, it allows a TAPI sub-

scriber to hang up.

When planning CSTA connections, one CSTA connection each should be reserved for connect-ing a CMD and a CSP; this avoids resource bottlenecks for subsequent additions.

Figure 4-6 vCAPI and TAPI

LAN

0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


PC

ISDN

PC with vCAPI, dialing from PC via HG 1500 V3.0 with TAPI

(TAPI for associated dialing or TAPI 120). Incoming call sig-

naling via answer group from terminal

HG 1500 V3.0 vCAPI

server

HiPath 3300/3350, HiPath 3500/3550

or HiPath 3800



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.12.4 vCAPI and Fax

You can send and receive faxes via the HG 1500 V3.0 vCAPI. To do this, you need an optionalCAPI-based fax software.

Fax services with HG 1500 V3.0

● Each PC has a separate fax DID number

● Group 3 fax machines send and receive at a speed of 14,400 bauds

● Fax activation in receive direction

● Fax forwarding possible on no answer and busy to analog fax (for example if a PC isswitched off)

● No B channel reservation (the channel can be used by other applications when no fax isbeing sent or received).

● Depending on the system type and the number of boards, up to nine simultaneous faxesare possible.

Figure 4-7 vCAPI and Fax

>If you want to use CTI and fax functions simultaneously at your client PC, an individ-ual station number should be allocated for each service. Otherwise problems couldarise during call pickup.

LAN

0 ABCDEFMNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


PC

ISDN

PC with vCAPI and fax software.

Sending and receiving or

fax activation up to 14,400 baud

HG 1500 V3.0 with fax

module

Fax machine

HiPath 3300/3350, HiPath 3500/3550

or HiPath 3800




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.12.5 vCAPI and File Transfer

File transfer enables direct data exchange with your ISDN peer. This is possible using any soft-ware with the Euro File Transfer standard, or using the same proprietary software on both sides.

4.5.12.6 vCAPI and Internet

Internet access via vCAPI is only necessary if your service provider’s access software requiresthe CAPI interface.

Internet access is also possible via routing.

Figure 4-8 vCAPI and File Transfer

Figure 4-9 vCAPI and Internet

S0

LAN


↵←→↑↓

1234567890 ABCDEF



↵←→↑↓

1234567890 ABCDEF


PC

ISDN

PC with vCAPI, data trans-

fer with file transfer

HG 1500 V3.0 vCAPI server

PC with ISDN card and

File transfer softwareHiPath 3300/3350, HiPath 3500/3550

or HiPath 3800

LAN

HG 1500 V3.0

PC with vCAPI and Internet access software

0 ABCDEFMNOGHI

PQRSTUV

↵←→↑↓

1234567890 ABCDEFMNOJKLGHI

PQRSTUVWXYZ

Service provider InternetISDN

HiPath 3300/3350,

HiPath 3500/3550

or HiPath 3800






A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

● GSM V.110

● V.90 (max. 56,000 bps)

Routing with HG 1500 V3.0

4.5.14 Call Charge Allocation and Callback

If HG 1500 V3.0 establishes an ISDN trunk call, the charges incurred are allocated to the sta-tion number used. As long as this physical connection exists, data can be transferred in bothdirections. If a connection exists between HG 1500 V3.0 A and HG 1500 V3.0 B via the trunk,all HG 1500 V3.0 A and B devices connected to the LAN can avail of the connection. In thiscase, the charges are allocated to the station number of the HG 1500 V3.0 A board port whichestablished the connection.

As is standard with today’s routers, call charges can only be allocated to the router station num-ber and not to specific LAN devices or applications.

Even if the physical connection is cleared down via "short hold", it is reestablished when newmessages are received. If the data from HG 1500 V3.0 is B to A, thisHG 1500 V3.0means thatB initiates the connection and therefore, the call charge allocation for B also changes.

Figure 4-10 Routing with HG 1500 V3.0

LAN

LAN

0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


Third-party router

Channel bundling with PPP

multilink even to third-party

routers or

HiPath 4000 WAML board

HiPath LAN-Bridge 1.x

Database

LANISDN

Teleworking PC

HiPath 3300/3350, HiPath 3500/3550

or HiPath 3800

HiPath 3300/3350, HiPath 3500/3550

or HiPath 3800



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

When the "Callback" function is activated, charges incurred by the called HG 1500 V3.0 are al-located, as this called party rejects the incoming call and actively re-establishes the connection(callback without a connection). In other words, no B channel is set up. Identification is per-formed via the station number entered in Setup or, in the case of analog stations, via the DID

number entered under "ISDN peer".

4.5.15 Internet Access

One or more client PCs can directly access the Internet using a Web browser. The connectionfrom the LAN is set up via ISDN or DSL. In general, access is possible from all PCs. (Please

note that this is not allowed for all tariffs of every provider.)Internet access takes place via the HG 1500 V3.0 to the Internet provider, using the IP trans-port protocol.

All clients use the same provider.

Features

● Static or dynamic IP addresses

● Routing function with NAT/SUA (Network Address Translation/Single User Access)

● PPP multilink (channel bundling)

● PPPoE (for DSL)

● PPTP (for DSL)

● PAP (Password Authentication Protocol)

● CHAP (Challenge Handshake Authentication Protocol)

>In some cases (for example when short hold is deactivated), dial-up connections canbe only be initiated manually.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.15.1 HG 1500 V3.0 and Access to the Internet via a Network Provider

4.5.15.2 Internet Access via T-DSL (T-ISDN DSL)

At the end of 1999, Deutsche Telekom AG launched a new product (T-ISDN DSL, also knownas T-DSL) which combines fast Internet access with enhanced T-ISDN telephony features.

(Other providers, for example, in the Netherlands, use DSL with the PPTP protocol).T-ISDN DSL is first and foremost a normal T-Net or ISDN connection as a multi-device or sys-tem connection.

Over and above the functions of the normal T-Net or ISDN connection, the T-DSL connectionhas a data interface for Internet connections with a speed of 768 Kbps downstream and 128Kbps upstream. The use of this data interface does not seize any T-Net or ISDN channels.

Function

In contrast to T-ISDN, the NTBA is not connected directly to the main station but rather down-

stream of a splitter (BBAE). This device can be seen as a DSL-speed distributor between theISDN connection and data transmission.

The splitter has a TAE jack to which the NTBA is connected. The connection to the HiPath 3000is set up in the conventional manner.

Figure 4-11 Internet Access via a Network Provider

LAN

ISDN network

HG 1500 V3.0 as router and/or router with

NAT (Network Address Translation) and chan-

nel bundling

Client with Internet browser, e-mail client

0 ABCDEF

MNOGHIPQRSTUV

↵←→↑↓

1234567890 ABCDEF


UUNET Internet

HiPath 3300/3350,

HiPath 3500/3550

or HiPath 3800



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

In addition, the splitter features a connection for the T-DSL modem (NTBBA) which providesthe interface for data transmission at T-DSL speed.

The T-DSL modem is connected to the board via a 10BaseT interface. The PPPoE (Point to

Point Protocol over Ethernet) protocol is used for the connection.

4.5.15.3 IP Address Mapping

With the expansion of the Internet, it has become common practice to use the short but globallyunique IP addresses exclusively for the Internet and to revert to private (not public) IP address-es for IP networks within companies.

Consequently, addresses from the same IP network can frequently be used in many compa-nies.

The "IP address mapping" feature was developed to enable users to reach these addresses viaa unique routing entry despite the multiplicity of entries.

When routing to specific partners defined during configuration, HG 1500 V3.0 exchanges theprivate IP addresses used in its own LAN for other IP addresses and can in return be contactedby external users via these IP addresses.

Figure 4-12 Internet Access via T-DSL

LAN

ISDN network

main station

HG 1500 V3.0 as router and/or router with

NAT (Network Address Translation)

Client with Internet browser, e-mail client

Internet

SplitterT-DSL

Modem

(NTBBA)

NTBA

HiPath 3300/3350,HiPath 3500/3550

or HiPath 3800




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.16 Remote Control

Teleworking with HG 1500 V3.0 and pcAnywhere

Symantec’s pcAnywhere software enables remote operation of a PC in the network from an ex-ternal PC.

Prerequisite:

● Windows 98/ME, Windows NT 4.0, 2000 or XP as the operating system

● Connection setup with the IP transport protocol

● PC is operational (if applicable, screen is dark)

4.5.16.1 Safety Mechanisms ("Security")

An access authorization for the routing function is required in order to control access viaHG 1500 V3.0 from the internal LAN to the ISDN and vice versa.

A firewall is not practical for telematic functions. Rules for these functions (for example trunkaccess) and their call numbers can be saved in HiPath 3000.

The following information is intended specifically for the router (HG 1500 V3.0).

Figure 4-13 Telecontrol with pcAnywhere


↵←→↑↓

1234567890 ABCDEF



↵←→↑↓

1234567890 ABCDEF


Client PCs with pcAnywhere

PC with remote soft-

ware and

pcAnywhere

ISDN

(WAN)

Database

Server

LAN

HiPath 3300/3350,

HiPath 3500/3550

or HiPath 3800



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

Station number verification (incoming only)

Verification of the station number of the calling station (station authentication, configurable) andthe IP address to prevent unauthorized external connections via ISDN.

Verification of the IP address (configurable) of internal LAN subscribers.

4.5.16.2 Firewall

A firewall is a barrier which protects against unauthorized access. In this case, the internal LAN(LAN1), for example, is to be protected against external access (such as Internet-based accessvia DSL).

The objective of a firewall configuration is to allow individual, specified computers to access aninsecure network (for example Internet). At the same time, it prevents access in the reverse di-rection (from the Internet to these computers). The board features two different protectionmechanisms for implementing this security.

The firewall in this case is a so-called authorization firewall. In other words, as soon as the fire-wall is activated, only configured components can access board services. All board servicesare automatically denied to unregistered LAN components.

Firewall (Permit Firewall)In the case of a permit firewall, only configured components can access board services (whenthe firewall is activated). All board services are automatically denied to unregistered LAN com-ponents. The board features different protection mechanisms for implementing this security.

● Stateful packet filtering for communication with the LANStateful packet filtering analyzes and, if necessary, rejects packets based on their sourceand target IP address addresses and the ports used (TCP, UDP, and ICMP port firewall).The IP addresses can be network addresses or individual hosts.

● Denial of Service Protection

Denial of Service Protection offers protection against a broad variety of Denial of Serviceattacks (and other attacks on the network gateway) such as SYN flooding, various frag-mentation attacks, TCP hijacking (various active attacks, for example ARP spoofing),LAND (identical source and destination IPs), Christmas Tree attacks (all TCP flags are set),etc.

7WARNING: The activation and deactivation of firewall parameters may severely re-strict the functionality of the board (for example LAN-based administration may notbe possible any more) or may enable access to sensitive data.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

● MAC verification

MAC address filters can limit access from devices within the LAN. If MAC filtering is en-abled, devices such as these can only set up connections from the LAN via HG 1500 V3.0

whose IP and MAC addresses are explicitly released for this purpose.

4.5.16.3 Alive Monitoring with Keep Alive

The Keep Alive Test is used for HXG3 boards located in different network nodes. This testsends a ping signal to the other HXG3 boards and then waits for a return signal. If a return sig-nal is not received from an HXG3 board (for example, because the IP connection is down) thenthe board is considered out of service. If this happens during call setup, a message is sent tothe HiPath 3000 to set the call up again.

The connection is automatically cleared down if the connection exists already and the KeepAlive Test fails. This is especially important for data connections to ensure that the applicationsinvolved can react appropriately and do not stall.

4.5.16.4 Monitoring IP Data Packages with rpcap and Wireshark (Ethereal)

Tracing via the HIP interface

The HIP interface (interface between HiPath 3000 and HG 1500) cannot be traced directly.However, external connections to the HIP interface via the LAN interfaces (LAN1: emac0 orLAN2: emac1) can be traced. When the rpcap service is launched, a server port of theHG 1500 opens. This enables direct access to TCP/IP packets by an IP trace tool such ase.g. Wireshark (Ethereal).

Wireshark is a program for analyzing network communication connections. It records datapackages from HG 1500 and displays them in a table overview.

rpcap (Remote Packet Capture)

The rpcap protocol permits programs, for example, Wireshark to run on the target system as aserver, recording data packages and transmitting them to a client. The client processes, ana-lyzes and archives the data packages.

>An external firewall should be used if the demands for security on the firewall arehigher (for example, if Internet and VPN traffic is being transferred to Internet gate-ways at the same time).



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

4.5.17 Overview of Management Tools

4.5.17.1 Overview

The following tools support administrators in performing their tasks:

● Web-Based Management (WBM) via an integrated HTTP server

Provides a step-by-step configuration and easy access to all management functions. WBMis the primary management tool.

● Command line (CLI) via a serial V.24 interface or Telnet

The command line is designed as the secondary management tool and provides a limitedfunction scope. It can be used to modify certain configuration data, update and restart thesystem and to diagnose the system configuration.

Security-relevant settings (such as SSL configurations) cannot be made via Telnet.

● SNMP-supported management via an SNMP agent

SNMP-supported management enables gateway integration in network management sys-tems. Systems like this can manage devices from other manufacturers.

HG 1500 V3.0 supports SNMP versions 1 and 2. Information such as statistics can be readand some important data can be modified using SNMP. Traps are also supported.

● HTTP applications via a command interface

HG 1500 V3.0 configuration data can be read out and modified and commands can be ex-ecuted via the HTTP port. This applies to insecure (HTTP) and secure (HTTPS) connec-tions.

The Universal Resource Identifier (URI) in the HTTP sequence is recognized by the gate-way board as an administration command. The HTTP header contains information re-quired for authentication.

In addition to the HG 1500 V3.0 management tools, the HiPath 3000 Manager E is available.

● HiPath 3000 Manager E

The HiPath 3000 Manager E is an independent application installed on a PC. It displaysthe relevant parts of the network as a virtual HiPath system. (Some HG 1500 V3.0 settingscan be configured both with this application and HG 1500 V3.0 tools, depending on the ver-sion of the HiPath environment.)




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

4.5.17.2 Multi-Gateway Administration (MGA)

The configuration of a large number of gateways, in particular, can cost administrators consid-erable time and effort, and so can – even only minor – modifications to a configuration.

HG 1500 V3.0 therefore supports the distribution of configurations from a master gateway toany number of slave gateways.

Prerequisites

In order to use Multi-Gateway Administration (MGA), no special hardware or software prereq-uisites are required on the gateways involved. However, the following conditions for configura-tion must be met:

● All slave gateways must be able to be accessed by the master gateway via IP.

●

The port used for WBM must have the same number on each gateway (usually 8085) andmust be accessible from the master gateway. Therefore, access must not be blocked by afirewall, for example.

● All slave gateways must have a user access for MGA. All accesses must have the samename and password. This access must have root access privileges.

● The slave gateways must be entered on the master gateway. (The list of slave gatewayscan also be imported by another master gateway, if necessary)

Using MGA

The administrator first configures the master gateway as required. He then uses a command totransfer this configuration data to slave gateways. The administrator can specify individually towhich slave gateways the data will be transferred and also select which configuration tables willbe transferred.

4.5.18 Quality of Service in HG 1500

Quality of Service encompasses various methods for guaranteeing certain transmission prop-erties in packet-oriented networks (IP).

It is thus important, for example, to ensure a minimum bandwidth for Voice over IP for the entire

duration of the transfer operation. If multiple applications with equal rights are operating via IP,then the available bandwidth for the transmission path (for example an ISDN B channel, 64Kbps) is split. In this case, a voice connection may experience packet losses which can reducevoice quality.

HG 1500 V3.0 uses various different procedures to implement Quality of Service.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

On layer 2 (in accordance with OSI, Ethernet), you can activate an extension (IEEE 802.1p) tothe standard Ethernet format (DIX V2). This adds more information to the Ethernet header in-cluding a 3-bit data field. This field carries priority information on the data packet. For all packetsthat reach the board from the LAN, both Ethernet formats (IEEE 802.1p and DIX V2) are un-

derstood; for all packets that are sent from the board to the LAN, the format can be selected via"Basic Settings > IEEE 802.1p". You should check whether all components in the network sup-port this format before this parameter is activated. Otherwise, it may not be possible to accessHG 1500 V3.0 from the LAN anymore.

The Ethernet header is not transported when switching to another transport medium(for example ISDN). An IP router (like the HG 1500 V3.0’s router) can, however, use the infor-mation contained in the IP header for prioritization. Straightforward IP routers that connect twonetwork segments, for example, can use the IP level prioritization. In the "Type of Service" field,either three bit (IP precedence based on RFC 791, older standard) or six bit (Differentiated Ser-vices or DiffServ, based on RFC 2474) are evaluated for the creation of various classes.

HG 1500 V3.0’s IP router provides various bandwidths for these classes, so that voice packetscan be processed first. The procedure adopted by HG 1500 V3.0 can be set under "Basic set-tings > QoS procedures" (Autodetect is set by default).

For the DiffServ parameter, various so-called codepoints ("Basic Settings > AF/EF Code-points") are defined, and based on these codepoints two different procedures are used for pro-cessing the payload of different marked data flows:

The "Expedited Forwarded (EF)" procedure (based on RFC 2598) guarantees a constantbandwidth for data in this class. If this defined value is reached, all packets that exceed thisbandwidth are rejected. A separate class is defined for EF on HG 1500 V3.0. For this class, the

bandwidth can be defined as a percentage for every ISDN peer (QoS bandwidth for EF).The "Assured Forwarding (AF)" procedure (based on RFC 2597) guarantees a minimum band-width for the data of one (of many) classes. Lower priority classes share the bandwidth not usedby EF or the classes with higher priority. In addition, the speed at which packets are rejected ifthe system is unable to forward them fast enough can be defined for every class by means ofthe Dropping Level setting. Nothing is thus to be gained by buffering voice packages for an ex-tended period of time (this only increases the delay). In the case of secure data transfer(for example file transfer), on the other hand, a large buffer is advantageous as packets are oth-erwise sent repeatedly between the two terminals.

Four classes are reserved for AF on the HG 1500 V3.0: AF1x (high priority), AF2x, AF3x andAF4x (low priority), where "x" stands for one of three dropping levels: low (1), medium (2) andhigh (3). In the case of "low", packets are buffered over an extended period, in the case of"high", packets are promptly rejected if they cannot be forwarded. Unmarked IP packets (ToSfield=00) are handled in the same way as the lowest priority.

If a routing partner can only work with one of the two standards (DiffServ or IP precedence,for example an older router that only works with IP precedence), then HG 1500 V3.0 can trans-late the ToS field accordingly. This can be set for each ISDN partner or DSL/LAN2/PPTP inter-




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

HG 1500

face via "QoS Capability". When the default value is set ("identical"), nothing is translated; withthe values "DiffServ" or "IP Precedence", translation is performed on the basis of the table be-low, if data is not entered in the field in accordance with the standard set.

In the case of IP data traffic, the IP packets that generate HG 1500 V3.0 are split into fivegroups (for example the vCAPI server, H.323 gateway). You can set which codepoint is to beused for marking the packets for four of these groups. This is configured under "Basic Settings> QoS priority classes":

● Voice Payload for H.323 telephony (Voice over IP)

● Call Signaling for connection setup in H.323

● Data Payload, for example, for IP networking with fax or modem

● Network Control, for example, SNMP traps

The remaining data traffic is marked "disabled", that is 00.

The following table shows the relationship between the various codepoints of DiffServ, IP pre-cedence and the "User Priority" field in the Ethernet header.

IP header Ethernetheader

DiffServ vs. IP Precedence IEEE802.1p

Code-point

Default (can bechanged)

Drop level Assignment(fixed)

Binary(bit field)

ToS field(hex)

high med low Binary(bit field)

ToS field(hex)

User Priority(binary, bit

field)

CS7 111000 E0 x <-> 111 E0 111

AF 11 001010 28 x -> 110 C0 110

AF 12 001100 30 x <-> 110 C0 110

AF 13 001110 38 x -> 110 C0 110

AF 21 010010 48 x -> 101 A0 101

AF 22 010100 50 x <-> 101 A0 101AF 23 010110 58 x -> 101 A0 101

AF 31 011010 68 x -> 100 80 100

AF 32 011100 70 x <-> 100 80 100

AF 33 011110 78 x -> 100 80 100

AF 41 100010 88 x <-> 011 60 011

Table 4-15 Codepoint Implementation



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



HG 1500

The "vs." column shows the relationship between the DiffServ and IP precedence standards.Since DiffServ offers more variants, the codepoint is permanently selected when translating IPprecedence into DiffServ: for example, the codepoint for the IP precedence "100", for example,becomes "AF31". In the case of packet that leave HG 1500 V3.0 in the direction of the LAN, theuser priority specified in the last column is set when IEEE 802.1p is active.

QoS can be activated for the second LAN interface as well as for the ISDN partner. For thisinterface, the interface is extended by an additional transmission rate limitation. The function ofthe quality evaluation corresponds to the ISDN peer procedure. The average transmission rateis set in configuration data.

AF 42 100100 90 x <-> 011 60 011

AF 43 100110 98 x <-> 011 60 011

EF 101110 B8 <-> 110 C0 110

DE(default) 000000 00 000001010

002040

000

IP header Ethernetheader

DiffServ vs. IP Precedence IEEE802.1p

Code-point

Default (can bechanged)

Drop level Assignment(fixed)

Binary(bit field)

ToS field(hex)

high med low Binary(bit field)

ToS field(hex)

User Priority(binary, bit

field)

Table 4-15 Codepoint Implementation




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

IP Trunking

4.6 IP Trunking

4.6.1 Overview

The implementation of IP telephony between the HiPath 3000/5000 communications platformshas several advantages for our customers such as saving on expensive leased lines for tele-phony only, the convergence of communications networks for voice and data over several loca-tions, a standard contact partner for the infrastructure and other advantages.

The main advantage for users of IP telephony is a significant saving on costs by using a single infrastructure for data and voice. This advantage can be even further expanded by using thevoice compression procedure, Compression enables existing lines to be used much more ef-fectively. For example, up to three calls can be conducted simultaneously on a single ISDNchannel if an optimized compression algorithm is used. A considerable reduction in costs canbe expected particularly for companies that already have a broad-band intranet. IP trunking isavailable over the integrated ISDN router HG 1500 voice/data (Hicom Xpress@ LAN Data/ Voice).

● max. 16 channels per HG 1500 V2

● max. 64 nodes for 1000 subscribers per network

HiPath 3000/5000

S0 Board

HG 1500

CustomerLAN

ISDNtelecommunica-tions network)

HiPath 3000/5000

HG 1500

S0 Board

CorNet “tunneling” over IP







3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



IP Trunking

Standard Numbering Plan

Telephone numbers are converted into the IP addresses of the remote communications plat-form (HiPath 3000) within the LAN access (HG 1500). A “routing table” which assigns the cor-

rect IP address to each destination call number or destination node number must be created toensure that the IP address of the correct target node is implemented.

A network with either open or closed numbering should be configured for this purpose. Whenusing closed numbering, each station number in the network can have up to seven digits where-as in open numbering, the node number + station number together must not exceed seven dig-its.

Standard Compliance

● Connection protocol

“Voice over IP” to ITU H.323

● Voice transmission - Audio Codecs

– ITU G.711

– ITU G.723.1

– ITU 6.729

● Echo suppression

in accordance with ITU-T G.165

● Prioritization of data – Quality of Service (QoS)

– IEEE 802.1d

– RFC2474 Differentiated Services (DiffServ)

– RFC791 Type of Service (TOS)




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

IP Trunking

4.6.3 Network-Wide Features with IP Networking

New features have been added to the functionality of networking over digital leased lines viaCorNet-N.

Function Name Description of the Function

Network-wide featuresusing CorNet-N/IP net-working

● Connection setup● Direct inward dialing in the network● Different rings (internal/external)● Transmission of number and name● Number or name shown on display● Callback on busy/free● Advice of charges output at subscriber line (AOC-D)● Call forwarding

● Call forwarding(rerouting for optimization of B channel use.)

● Message waiting indicator for callbacks and voicemail mes-sages

● Call waiting● Network-wide class-of-service (max. 4 classes of service)

Additional system servic-es

● Network-wide shared numbering plan● Display of name and number suppressed● Consultation hold (over second B channel)● Transfer (over second B channel with release of tie trunk when

station transferred)● Conference with max. five participants

(no network-wide display function)● Toggle● Hunt group and group call across all nodes)● Directed joining and leaving a group,

cross-nodal● Hunt group overflow● Call detail recording for all nodes

(communication platforms) in the network (central solution)



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



IP Trunking

Outside IP networking, HiPath 3000/5000 provide an option for conventional networking overCorNet-N and QSig (ECMA V1.0 and ECMA V2.0).

Additional system servic-es (continued)

● Transit traffic● Least cost routing (LCR)● Call pickup (call pickup with subscribers from other nodes

(systems))● Follow Me● Chain call forwarding (maximum number of stations monitored

over several nodes)● Enable and disable features in IP-networked communications

platforms with user prompts at optiPoint 500 workpoints (nightanswer, for example).

● Central attendant console (optiClient Attendant) with busy sig-nal (the states free, internal/external busy and faulty are sig-nalled for stations in IP-networked communications platforms.)

● Central attendant console functions (forward, assign, recall,hold)

Use of only one B chan-nel over CorNet N subset

The following features cannot be used over a dedicated line if a Bchannel has already been seized:● Consultation hold● Transfer● Toggle● Conference

Path optimization in net-

worked HiPath 3000/ 5000 systems

Path optimization, in other words transit traffic with identical source

and destination systems (switched or forwarded traffic, for in-stance), is performed in HiPath 3000/5000 systems networkedover IP. This means that channels are no longer blocked.

Function Name Description of the Function




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

IP Trunking

4.6.4 Special Features of Windows Networks

4.6.4.1 Routing and Name Resolution

For example: when routing from HG 1500 V3.0 to HG 1500 V3.0 and for peer-to-peer connec-tions (Windows for Workgroup Network for IP routing), you must create an LMHOSTS/HOSTS file on the client PCs. This is stored in the Windows directory under Windows 95, and in thedirectory WINNT\SYSTEM32\DRIVERS\ETC under Windows NT or 2000. The file LM-

HOSTS.SAM in the directory can be expanded but must not have an extension (LMHOSTS).

Sample entry:

192.168.10.10 HG1500

192.168.10.20 PC1

Do not forget to press Return after the last entry.

Once the LMHOSTS/HOSTS file has been created, a ping command with the name (for examplePing HG 1500) should be transmitted to the partner. Since browsing is not transferred in thecase of routers (broadcast messages), the other PC can only be found by right-clicking the"Network Neighborhood" and "Find Computer" icons. Once the computer has been found, thenetwork resources can be accessed. The other PC cannot be accessed by opening the networkneighborhood.

>

Names should contain no more than eight characters since some operating systemsrun into problems if there are more than eight characters in the name.

Modifications in LMHOSTS/HOSTS are only effective after the computer has been re-booted. Under Windows 95 and 98 you can also use the command NBTSTAT -R.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



IP Payload Switching

4.7 IP Payload Switching

Introduction

IP payload switching optimizes communication between LAN-based IP workpoint clients.

In HiPath 3000 V1.2 and lower, two B-channels (with two DSP resources) in the HiPathHG 1500 and HiPath 3000/5000-internal switching network were seized for internal networkcalls.

In HiPath 3000/5000 V3.0 and later, VoIP voice data (payload) is transferred directly betweentwo IP workpoint clients in the network. When this happens, both IP workpoint clients have fullaccess to all system features.

Payload switching is also implemented for IP networking (PBX routing).

By ceasing to use B-channels, we have managed to preserve HG 1500 resources and facilitatea higher volume of network-internal call traffic.

A B-channel is still required on the HG 1500 for connections to the following stations and lines:

● UP0/E stations

● Analog stations

● ISDN stations

● Trunks and tie lines (MSI, S0, S2M)

Example: a consultation call to an optiPoint 500 telephone is set up during an existing connec-tion between two IP workpoint clients. A HG 1500 B-channel is necessary for this consultationcall.

In the case of conferences, the number of B channels seized corresponds to the number of sta-tions and IP workpoint clients involved.

A HG 1500 DSP resource is permanently reserved for playing music-on-hold.

Example: a license was acquired for two B channels and six clients. Six optiPoint 400 standardswere logged on. The following scenario is possible in this case: two stations can conduct anexternal call, while two stations are listening to Music on Hold and two stations are talking to

each other.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

IP Payload Switching

Prerequisites

The following components are necessary for using payload switching:

● IP telephones and clients:

– OpenStage CorNet IP (HFA), SIP

– optiPoint 410/420 CorNet IP (HFA), SIP

– OpenScape Personal Edition

● HG 1500 boards with Digital Signal Processor DSP (voice and data)



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



Applications over IP

4.8 Applications over IP

4.8.1 Call Detail Recording Central (CDRC) via IP

In HiPath 3000/5000, you can start up the central call data output function only once, whichmeans that it is available to only one application at a time. Three different modes exist to sup-port the various requirements of the different applications.

Model-Specific Data

4.8.1.1 TFTP Client in HiPath 3000/5000

Controlled by a programmable timer and a fixed threshold value determining the call data buffercapacity (around 80 percent of the call data buffer full), the TFTP client (HiPath 3000/5000)sends call data to the TFTP server (external application). If the system cannot set up a con-nection to the TFTP server, it addresses an alternative server. If this server is also unavailable,it outputs an SNMP trap or error message (“Unable to output data”). The system tries to set upanother connection every 60 seconds. A call data buffer overflow causes an error message tobe entered in the error history file.

Subject HiPath 3800 HiPath 3550HiPath 3500


Feature available in x x x

Hardware requirements HG 1500 / LIMS

Software requirements V5.0 or later V1.2 or later V1.2 or later

TFTP client

HiPath 3000/5000 Externalapplication

TFTP protocol TFTPserver

Alternativeserver




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


4.8.1.2 TCP Client in HiPath 3000/5000

When call data records accumulate, the TCP client (HiPath 3000/5000) sets up a TCP/IP con-nection to an external TCP server (external application) and transmits the data. The connectionremains active continuously so that the system can send any further accumulated data, trans-mitting each data record separately.

4.8.1.3 TFTP Server in HiPath 3000/5000

The external application (TFTP client) requests output of the call data records. To do this, theapplication must set up a connection and indicate the service (GET gez.txt), after which it re-ceives all accumulated call data records. It releases the connection after the transfer.

The application’s request for call data can be controlled automatically or using an SNMP trap(see Section 4.9.2). HiPath 3000/5000 sends the SNMP trap (“data available”) to the externalapplication, generating the trap using a programmable threshold value determining the call

data buffer capacity (0 to 80 percent of the call data buffer full).

TCP client

HiPath 3000/5000 External appli-

cation

TCP protocol TCP server

TFTP server

HiPath 3000/5000 External appli-cation

TFTP protocol TFTPclient

TFTPclient



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




4.8.2 CSTA via IP

The Transmission Control Protocol (TCP) is used for CSTA via IP. A permanent connection isset up. Data packet loss is detected and automatically corrected.

For HiPath 3000, the following number of server applications may be connected per system:

● up to one in HiPath 3300/3350, HiPath 3500/3550

● up to four in HiPath 3800

Restrictions may apply to applications that use certain services. For example, only one appli-cation at a time can start the message registration function.

For an external application to address HiPath 3000/5000, it must know the TCP port (7001) ofthe TCP/IP server implemented in HiPath 3000/5000 as well as the IP address. Data packetssent from an application to HiPath 3000/5000 – that is, packets containing the HiPath IP ad-dress, TCP port 7001, and protocol type TCP – are accepted for further processing.

HiPath 3000 V7 and later systems support CSTA monitoring of connections to ITSPs. This en-ables e.g. call center applications to be used, even if SIP trunks are used.

Model-Specific Data

LIM / LIMS

LIM/LIMS is released in HiPath 3800 for administration, fault management and accounting. Noother features or protocols are supported via LIMS!

LIM for HiPath 33x0 and HiPath 35x0 can be used for CTI/CSTA applications in conjunction withTAPI 120 (up to 6 stations). No other features or protocols are supported via LIM!

Dependencies/restrictions

SimplyPhone for Outlook is supported via LIM from Version 6.0 or later.




Hardware requirements HG 1500 HG1500 / LIM





A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm

Administration & Fault Management

4.9 Administration & Fault Management

4.9.1 Overview

HiPath 3000/5000 with a LIM or a HG 1500 board can be administered centrally over a LANconnection from one or more PCs using SNMP. The following functionalities can be implement-ed:

● Administration and fault management of a system (SNMP)

● APS update (TFP)

● CDB backup on TFTP server

● Network management

Figure 4-14 HiPath 3000/5000 - Administration over LAN

e.g. PC withHiPath 3000/5000

Manager E

SNMP

HiPath 3000/5000

Central Board

LIM

CustomerLAN

e.g. PC withNetwork Management

e.g. PC withNetwork Management

e.g. PC withHiPath 3000/5000

Manager E

HiPath 3000/5000

Central Board

LIM

HiPath 3000/5000

Central Board

LIM

HiPath 3000/5000

Central Board

LIM






A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


● a user-specific MIB that processes HiPath-specific statistic data (feature counters) and in-ternal error messages (error history), covering the following areas:

– ControlGroup – status variables, general configuration, supplementary TFTP configu-

ration data

– SystemInfoGroup – system configuration and status

– StatisticsGroup – statistic data on features

– ErrorHistoryGroup – Error history in HiPath formatError messages are forwarded in the form of SNMP traps via the LAN to a specific ex-ternal management application. The SNMP traps form the error history data structure(time stamp, error class, error description).

These components use the IP protocol according to OSI layer 3 and the UDP protocol accord-

ing to layer 4. The SNMP protocol stack uses port numbers. The system supports the SNMPprotocol version 1.0.

SNMP Messages

The following commands control SNMP messages for communication between the SNMPmanagement agent (HiPath 3000/5000) and external applications:

● GET – retrieve data from agent

● GET NEXT – read out data sequentially

● SET – write data

● TRAP – alarm messages issued by the SNMP agent

There is an integrated mechanism for generating SNMP traps in the event of class B errors.The SNMP management agent evaluates the error messages. In the case of defined errors, itgenerates specific traps and transmits them in the form of IP data records to a configurable IPaddress (a total of five SNMP V1.0-compatible applications are supported, including HP OpenView Network Node Manager for example).



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




4.9.2.3 Using SNMP

An MIB browser (available with Hewlett-Packard’s "Network Node Managers") is required forusing SNMP functionality.

SNMP traps

The following HG 1500-specific trap classes are available:

● General traps

● Reboot traps

● Threshold/statistic, resource/diagnostic traps,

● Security traps

● License traps

● Traps for internal errors

The following tables list the individual traps for each of these classes. A distinction is made un-der "Type" between hardware traps (HW) and software traps (SW).

Trap

COLD START

WARM START

INTERFACE UP

INTERFACE DOWN

AUTHENTICATION ERROR (incorrect SNMP community name)Table 4-16 Generic SNMP Traps (MIB-2)

Type(SW/HW)

Trap Message Explanation

SW MSG_GW_SUCCESSFULLY_STARTED Gateway successfully started

Table 4-17 General Traps (HG 1500-Specific)

Type(SW/HW)


SW MSG_CAT_H323_REBOOT Reboot with H.323

SW MSG_CAT_HSA_REBOOT Reboot with HSA

Table 4-18 Reboot Traps (HG 1500-Specific)




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


SW MSG_ADMIN_REBOOT Reboot with WBM/CLI-Admin,

software upgrade or data restoreSW MSG_SYSTEM_REBOOT Automatic reboot, for example with Gar-

bage Collection

SW MSG_EXCEPTION_REBOOT Reboot with SW exception

SW ASSERTION_FAILED_EVENT Reboot following declared exception

SW EXIT_REBOOT_EVENT Reboot following exception on termina-tion

HW MSG_DSP_REBOOT Reboot following DSP error

HW MSG_DELIC_ERROR Reboot following DELIC error

Type(SW/HW)


HW MSG_IP_LINK_FAILURE IP-Link 1 up/down

HW MSG_IP_LINK2_FAILURE IP Link 2 up/down

HW MSG_OAM_HIGH_TEMPERATURE_EXCEPTION Temperature limit reached(too hot)

SW MSG_GW_OBJ_MEMORY_EXHAUSTED Out of memory

SW MSG_GW_OBJ_ALLOC_FAILED Out of memory (signaled byexternal source)

SW MSG_GW_OBJ_MEMORY_INCONSISTENT Memory inconsistency

SW MSG_TLS_POOL_SIZE_EXCEEDED No more internal pools

SW MSG_OAM_RAM_THRESHOLD_REACHED RAM limit reached

SW MSG_OAM_DMA_RAM_THRESHOLD_REACHED DRAM limit reached

SW MSG_OAM_THRESHOLD_REACHED Limit reached, for example,

for flash memory or IP poolsSW MSG_DVMGR_LAYER2_SERVICE_TRAP B channel up/down

Table 4-19 Threshold/Statistic, Resource/Diagnostic Traps (HG 1500-Specific)

Type(SW/HW)


Table 4-18 Reboot Traps (HG 1500-Specific)



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




The weighting of the individual traps can vary depending on the severity of the event or errorand is described by the following categories:

● Cleared (problem already resolved)

● Indeterminate (no classification possible)

● Critical (critical error)

● Major (major error)

● Minor (minor error)

● Warning (warning only)

Type(SW/HW)


SW MSG_HACKER_ON_SNMP_PORT_TRAP Unauthorized access toSNMP port

Table 4-20 Security Traps (HG 1500-Specific)

Type(SW/HW)


SW MSG_LIC_DATA_ACCEPTED License data accepted

SW MSG_LIC_DATA_CORRUPTED License data incomplete

SW MSG_LIC_DATA_NOT_ACCEPTED License data not accepted

Table 4-21 License Traps (HG 1500-Specific)

Type(SW/HW)

Trap Message

SW MSG_WEBSERVER_MAJOR_ERROR

SW MSG_SSM_NUM_OF_CALL_LEGS_2BIG

SW MSG_SSM_SESSION_CREATION_FAILED

SW MSG_IPNCV_STARTUP_ERROR

SW MSG_IPNCV_STARTUP_SHUTDOWNSW MSG_IPNCV_INTERNAL_ERROR

SW MSG_IPNCV_MEMORY_ERROR

SW MSG_IPNCV_SIGNALING_ERROR

Table 4-22 Traps for Internal Errors (HG 1500-Specific)




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


● Information (for information only)

General traps, such as MSG_GW_SUCCESSFULLY_STARTED, are sent as "information".

Reboot traps are always "critical", "major" or "minor" errors.

Threshold/resource traps occur as follows: When an event is received, the trap is sent as either"Warning", "Minor" or "Major". If the trap recurs, reminders are sent (at increasing intervals) witha weighting that is at least the same or higher than the initial trap. If the event was corrected(for example, "Link up" or sufficient RAM was provided), the trap is sent with the category"Cleared".

SNMP Functions

The SNMP functions include:

●

With MIB browser and standard MIB (based on RFC1213): – querying and modifying standard MIB 2 parameters

● With MIB browser and private MIB:

– querying and modifying HG 1500 V3.0’s private MIB parameters

● With HiPath 3000 Manager E:

– defining communities of standard parameters (classes of service)

– defining trap communities and stations to which the traps are sent

– defining the trap level for various trap groups (error sensitivity)

● With trap receiver:

– receiving traps

MIBs also contain a brief commentary explaining the meaning of each parameter.

The following is a list of some parameters:

● mgmt > mib-2 > system > sysUpTime: time since the last HG 1500 V3.0 startup

● HLB2MIB > siemensUnits > pn > hlb2mib > controlGrouphlb20 > sysSoftwareVersion:

board software release

● mgmt->mib-2->ip->ipRouteTable: HG 1500 V3.0 routing table

HG 1500 V3.0 sends SNMP traps (diagnostic and error messages) to the stations configuredunder "SNMP > Trap Communities". These messages are transmitted in accordance with theseverity levels set under "SNMP".



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




Examples of traps generated by HG 1500 V3.0:

1. Generic traps (cannot be deactivated):

● warm start

● cold start

● authentication failure

2. Enterprise traps (can be configured)

● data init (WARNING - forced data reinitialization)

● memory low (WARNING - memory resources below the threshold)

● duplicate mac (MINOR - duplicated MAC address)

● ip firewall (WARNING - IP firewall violation)

● mac firewall (WARNING - MAC firewall violation)

● isdn access (WARNING - ISDN access verification)

SNMP information can also be sent as e-mail to a mail address configured with the WBM.




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


4.9.3 Administering HiPath 3000/5000 via the LAN Interface

You can administer HiPath 3000/5000 via a computer connected to the LAN.

Model-Specific Data




Hardware requirements HG 1500

Software requirements V5.0 V1.2 V1.2

HiPath 3000/5000

PC withHiPath 3000/5000 Manager E

Central Board

LIM *

CustomerLAN

* A HG 1500 board can be used instead of the LIM board.



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011



Networking Scenarios in the LAN Network

4.10 Networking Scenarios in the LAN Network

Scenario Description Closed or open numbering Number-

ing plan

Remark

Scenario 1 IP networking betweentwo HiPath 3000 systems

● Closed: from node tonode via internal num-ber, from PSTN via sub-scriber line + internalnumber

● Open: node code + in-ternal number

Privatenumberingplan

Two nodes in the network

Scenario 2 IP networking betweenHiPath 3000 and HiPath5000

Closed Privatenumberingplan

Two nodes in the network,HiPath 3000 serves as agateway to PSTN

Scenario 3 IP networking betweentwo HiPath 3000/5000systems

Closed numbering per loca-tion


Four nodes at two loca-tions

Scenario 4 IP networking betweenHiPath 3000 andHiPath 4000

● Closed: from node tonode via internal num-ber, from PSTN via sub-scriber line + internalnumber


HiPath 3000 and HiPath4000 are networked via IPand each serve as a gate-way to PSTN

● Open:node code + internalnumber

CO number


ISDN num-bering plan

Scenario 5 Payload switching in an IPnetworking scenario be-tween HiPath 3000/5000and HiPath 4000

Scenario 6 Scenario for Internet tele-phony

Connection to Internet te-lephony service providers(ITSP)

Scenario 7 Networking multipleHiPath 3000 systems,

each equipped with onelocal Linux server withOpenScape Office HX

Closed Privatenumbering

plan

Table 4-23 Networking Scenarios




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


The scenarios are described in the subsequent sections.

4.10.1 Scenario 1

IP Trunking HiPath 3000/3000, 2 Nodes in the Network

●

Functional scope between both HiPath 3000 systems corresponds to CorNet-IP● Closed numbering (private numbering plan):

Dialing from node to node: internal numberDialing from PSTN: subscriber line + internal number

● Open numbering:Dialing from node to node: Dialing of the node code + internal number (private numberingplan)

● Implementation of the HiPath 5000 RSM Feature Server for closed and open numbering ispossible

● Max. 1000 nodes in the network when using the HiPath 5000 RSM Feature Server (incl.TDM)

● Max. 32 nodes in the network when using the HiPath 5000 RSM Feature Server

● Max. 64 nodes in the network without the HiPath 5000 RSM Feature Server

● An optional HPCO V1.3 can be implemented (for max. 16 nodes in the network)

– Alternatively, OpenScape Contact Center at a single node

● An optional Xpressions Compact can be implemented centrally

IP workpoints xx registeredto gateway 1

IP workpoints xxxx regis-tered to gateway 2



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




– Alternatively, central OpenScape Xpressions

4.10.2 Scenario 2

IP Trunking HiPath 3000/5000, 2 Nodes in the Network with Closed Numbering

● Feature scope corresponds to CorNet-IP

● Closed numbering:

Dialing from node to node: internal numberDialing from PSTN: subscriber line + internal number

● Open numbering is not supported by this configuration.(Availability of the PSTN not guaranteed as the node number is not included in the custom-er’s station number block, CCBS not guaranteed, etc.)Exception: where the node number + internal number are contained in the customer’s sta-tion number block.

HiPath 5000




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm




● Max. 64 nodes in the network without the HiPath 5000 RSM Feature Server

● An optional HPCO V1.3 can be implemented (for max. 16 nodes in the network)


● An optional Xpressions Compact can be implemented centrally

– Alternatively, central OpenScape Xpressions

4.10.3 Scenario 3

IP Trunking HiPath 3000/5000, 4 Nodes at 2 Locations

Location 1,closed numbering

Location 2,closed numbering

HiPath 5000 HiPath 5000



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




4.10.4 Scenario 4

IP Trunking HiPath 3000/4000

● Functional scope between HiPath 4000/3000 corresponds to CorNet-IP

● Closed numbering (private numbering plan):Dialing from node to node: internal numberDialing from PSTN: subscriber line + internal number

● Open numbering:Dialing from node to node:

– Variant 1: Dialing of the node code + internal number (private numbering plan)

or

– Variant 2: Dialing of the CO number (ISDN numbering plan)

● Implementation of the HiPath 5000 RSM Feature Server is only possible for closed num-bering


IP workpoint onHiPath 4000

IP workpoint onHiPath 3000




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm



● Max. n times 64 nodes in the network without the HiPath 5000 RSM Feature Server

● An optional HPCO V1.3 can be implemented (for max. 16 nodes in the network) for closednumbering and open numbering as per variant 1 only


● Central Xpressions CompactFor closed numbering and open numbering as per variant 1 only






A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


4.10.6 Scenario 6

Connection to Internet telephony service providers (Internet telephony)

HiPath 3000 supports connection to Internet telephony service providers (ITSPs) as an Internettelephony user connection with registration of individual phone numbers. For larger systemconfigurations, it supports connection as a Internet telephony system connection, for which theITSP provides a phone number range.

● The system supports up to four simultaneously active SIP providers via LCR.

● Four different ITSPs may be registered simultaneously.

● S0 connections and Internet telephony connections can be used in parallel in all network-ing solutions to connect to ITSP analog lines.

● Internet access: ADSL, SDSL: HG 1500 is operated in the LAN behind an external routerwith firewall or NAT function.

Internet

OpenScape Personal Editionand Internet access

ITSPOpenScape Personal Edition

optiPoint 4x0

LAN / WAN

PSTN

HiPath 3800

optiPoint 4x0



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




4.10.7 Scenario 7

Networking multiple HiPath 3000 systems, each equipped with one local Linux server

with OpenScape Office HXThis scenario is possible as of HiPath 3000 V8 MR5 (V8 R5.2.0). The individual HiPath 3000systems are networked in the LAN via the CorNet-NQ protocol, tunneled in H.323. Up to 64HiPath 3000 nodes with a total of 2000 stations can be present in this network. All involvedHiPath 3000 systems must carry the same software version. Only closed numbering is support-ed. SIP and PSTN providers can only be connected locally, i.e.to each HiPath 3000.

To make OpenScape Office HX features available at HiPath 3000 nodes, a separate Open-Scape Office HX Linux server with the OpenScape Office applications must be connected toeach HiPath 3000. A central server is not possible.

Graphical overview

Node A

Node C

Node B

HiPath 3000 HiPath 3000

HiPath 3000

OpenScapeOffice HX

PSTN

LAN CorNet-NQ tun-neled in H.323

OpenScapeOffice HX

OpenScapeOffice HX




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm


Restrictions

The following restrictions apply for an internetwork with OpenScape Office HX:

● Open numbering cannot be used. Only closed numbering is supported.

● It is not possible to cross-link the OpenScape Office applications between the localOpenScape Office HX systems. Consequently, the presence status of users on otherOpenScape Office HX nodes is not visible, for example.

● A linked, multi-node call diversion or forwarding to OpenScape Office HX in a foreignHiPath 3000 node will not be followed.

● OpenScape Office HX is connected to the HiPath 3000 as an external H.323 gateway.Therefore, in this scenario, no additional networking with HiPath 4000 is possible viaH.323-Q.

● Only route 8 of the HiPath 3000 may be used for the connection of theOpenScape Office HX.

● Due to the licensing model, the HiPath 3000 internetwork with the integrated OpenScapeOffice HX cannot be administered with the HiPath 5000 RSM.

Locally supported features

The following features may only be made available locally, not centrally in the HiPath 3000 net-work:

● OpenScape Office:

– Presence: Internal directory, favorites

– Busy status: Internal directory, favorites

– External directory

● myAttendant:


– Adding contacts in an external directory

– Querying voice mails for another station – Automatic recall, intercept, divert display

● myAgent

● TAPI 120, CallBridge IP (TAPI 170 network-wide)

● External CSTA applications

● Mobility entry with DISA access, myPortal Web



3000sb4.fm

A31003-H3580-Y100-10-7618, 01-2011




Non-supported features

The following features are not supported in this scenario:

● Networking via SIP/SIP-Q

● Support of OpenScape Voice (HiPath 8000), HiPath OpenOffice EE, HiPath 4000 and Hi-Path 5000 RSM

● OpenScape Office networking. In HiPath 3000 V8 MR 5.2 and later, it is possible to connecttwo HiPath 3000 V8 that each have a local OpenScape Office HX V2 PC available to them.The CorNet-NQ protocol is used, tunneled in the H.323 protocol.

● HiPath 3000 systems with differing software versions

● Central voice mail

●

Open numbering plan




A31003-H3580-Y100-10-7618, 01-2011


3000sb4.fm




3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch System Administration and Service

Overview

5 System Administration and Service

5.1 Overview

Introduction

This chapter describes the options available to the service technician and the customer for

● performing system administration tasks on site

● performing system administration tasks from a remote location (remote operation)

● performing service and maintenance tasks

● identifying faults

Chapter Contents

This chapter discusses the topics listed in the table.

Subject

System Administration Options Page 5-2

● Administration On Site with System Telephone Page 5-3

● Administration On Site with Service PC Page 5-3

Options in the Service Department Page 5-12

● Customer Database Backup (CDB Backup) Page 5-12

● Relocate/Transfer Application Processor Software (APS) Page 5-14

● Diagnostics Options Page 5-18

● Error Correction Page 5-32

● Remote Service Page 5-34

● Access Security Page 5-39

● Automatic Logging of Administration Procedures Page 5-45



System Administration and Service Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm

System Administration Options

5.2 System Administration Options

5.2.1 Overview

Minor system adjustments bycustomer

Limited range of system adjust-ments by the service technician

Limited system adjustments/ad-

ministration by the customer

Complete system adjustments/ administration by the service

technician

Complete system adjustments/ administration by the service

technician, APS Transfer

0

ABCDEFMNOGHI

PQRSTUV

↵ ←→↑↓

1234567890

ABCDEF

MNOJKLGHI

PQRSTUVWXYZ

Customer

Technician

Technician

Assistant TC

Access with user name and

password

Manager T

Access with user name and

password

HiPath 3000/5000 Manager C

Access with customer ID andpassword

HiPath 3000/5000 Manager E

Access with technician ID and

password

HiPath 3000/5000 Manager E

(customized for remote center)

Access via callback with techni-

cian ID and password

Customer

Technician

Administration on sitewith system telephone

Remote administrationvia service center

Administration on site

with service PC



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.2.2 Administration On Site with System Telephone

All systems in the HiPath 3000/5000 product family can be administered to the full extent via asystem telephone. The rights of the individual user will determine the extent to which he or she

can perform administration tasks. Information on the various user groups and their accessrights is contained in Section 5.3.10.2.

Administration by the Technician using Manager T

This data area is password-protected to limit access to trained service technicians. With just afew exceptions, all system settings are available. Manager T gives you the ability to makechanges spontaneously on site, that is, without requiring any other tools.

You can only enter the service menu with a user ID and password.

Administration by the Customer using Assistant TC

This gives customers the option to perform a defined range of system settings themselves.These include, for example, configuring and changing speed-dialing destinations, and assign-ing names for stations and lines.

To protect individual customer data such as speed-dialing destinations or call detail information,it is not possible to enter the service menu unless you have user ID and password.

5.2.3 Administration On Site with Service PC

Service tools with Windows user interface and integrated help functions are available for theeconomical modification of larger volumes of data and for setting specific system data. Therights of the individual user will determine the extent to which he or she can perform adminis-tration tasks. Information on the various user groups and their access rights is contained inSection 5.3.10.2.

You can access the communications platform using:

● ISDN adapter on the system telephone (64 kbps B-channel access)

● V.24 (RS-232) interface on the system (9600/19200 baud)

● Internal S0 bus (64 kbps/CAPI 2.0)

● Remote access over an ISDN trunk (64 kbps B-channel access)

● Remote access over an analog trunk (integrated 14400 baud modem)




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


Technical Requirements for the Service PC

To implement the different service tools, the PC used must meet the technical listed in the fol-lowing table.

Administration by the Customer using HiPath 3000/5000 Manager C

This allows the customer to administer customer-specific data using a PC. The user interfacehas been adapted from the HiPath 3000/5000 Manager E interface and the help functions havebeen adjusted to the needs of the customer.

Administration by the Technician using HiPath 3000/5000 Manager E

The service tool integrates the following function blocks:

● Acquiring and generating customer data (including off-line generation)

● Copying and backing up customer data

● Loading system software (APS transfer)

● Displaying stored error messages with error history

● Service orders, such as restarting boards, etc.

● Resetting activated features

PC Component Requirement

CPU PC must fulfill the minimum requirements of the operating system.

Monitor VGA

RAM PC must fulfill the minimum requirements of the operating system.

Hard disk 150 MB free capacity (minimum)

Floppy drive 3.5”, 1.44 MB

Serial interface COM1, (COM2)

Mouse Microsoft-compatible mousePrinter Any Windows-compatible printer

Operating system Windows 98/2000/NT/XP



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




● Creation and printing of:

– Key labels for optiPoint 500 telephones

– Customer data printouts

– Main distribution frame layout

● User and password administration for after sales service.

● Database conversion routine.

Access to the system using HiPath 3000/5000 Manager E is only possible with a valid username and associated password that have been entered in the system.

Online mode has been integrated to enable you to perform changes quickly. Its functionalitycorresponds to the Manager T user interface.

Because sensitive system data can be processed, users are required to undergo the relevanttraining course before using the HiPath 3000 Manager.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.2.4 Remote Administration of HiPath 3000/5000 via PPP

You can administer multiple HiPath 3000/5000 systems from a central service center via PPP(point-to-point protocol). Each HiPath 3000/5000 is addressed via its PSTN (public switching

telephone network) interface.

You must enter a router call number (DID number) for every PSTN interface in the service cen-ter for external access to HiPath 3000/5000. This call number is not the number previously usedfor administration via integrated digital modem (B-channel) or integrated analog modem (IMO-DN).

You can establish a connection between the service center and HiPath 3000/5000 using eitherthe integrated digital modem (B channel) or the integrated analog modem (IMODN). Data is ex-changed in both cases using Point-to-Point Protocols (PPP).

If the connection is established via callback, HiPath 3000/5000 first of all denies a connectionrequest from the service center (HiPath 3000/5000 Manager E). A callback is then set up to theservice center’s calling party number transferred via the PSTN connection’s D channel.

Model-specific data




Hardware requirements CBSAP CBCC orCBRC

CBCC orCBRC


HiPath 3000/5000

Service centerservice PC

withHiPath 3000/5000

Manager E

Central Board

Modem

PSTN(analog or

digitaltelecommunica-tions network)

PSTN

interface










A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


Examples:IP data transfer from the customer LAN to the service center via the PSTN interface:IP customer LAN is transformed by HiPath 3000/5000 into an IP vir tual LAN.IP data transfer from the service center to the customer LAN via the PSTN interface:

IP virtual LAN is transformed by HiPath 3000/5000 into an IP customer LAN.

– If “IP mapping = No” is selected, IP address mapping is not available.

● Security mechanisms for connection setupUse the PAP (PPP authentication protocol) and/or CHAP (challenge-handshake authenti-cation protocol) to determine whether

– the Plus Product (client) must be authenticated at HiPath 3000/5000 (host) or

– the HiPath 3000/5000 (host) must be authenticated at the Plus Product (client).

Authentication is based on the user ID and the password.

Model-specific data

● Support for the external gatekeeper

The gatekeeper registers the H.323 clients and administers their rights and services. Itconverts the clients’ call numbers into logical names or IP addresses and vice versa. It alsoregisters the gateways and can be networked with adjacent gatekeepers.

● Quality of Service (QoS)

To guarantee the bandwidth required for Voice over IP, IP packets can be marked and arethereby transported with priority in the LAN/WAN.

● Networking of more than one system via IP

Several HiPath 3000/5000 telephone systems can be connected to each other with Voiceover IP (H.323) for telephony.

● Authentication

If you set up an external connection via HG 1500, you can use the PAP (Password Authen-tication Protocol) and CHAP (Challenge Handshake Authentication Protocol) proceduresto authenticate the other party to increase security in data networks.




Hardware requirements HG 1500




3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




● Second LAN connection (optional)

A second LAN connection is set up to decouple the DSL WAN connection. A routing func-tion is used to connect the first LAN.

● DSL support (optional)

The configuration database is extended to include an additional interface. The informationnecessary for dialing into the DSL network is provided here. The enhanced configurationparameters can be entered over the HiPath 3000 Manager I. The DSL functionality is onlyavailable for the second LAN connection.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm

Options in the Service Department

5.3 Options in the Service Department

5.3.1 Customer Database Backup (CDB Backup)

A distinction is made here between

● backup of customer data without HiPath 3000/5000 Software Manager and

● backup of customer data with HiPath 3000/5000 Software Manager.

5.3.1.1 Customer Data Backup Without HiPath 3000/5000 Software Manager

Definition

CDB backup refers to saving the customer database CDB to the multimedia card MMC (HiPath3000) or copying the cyclic RAM data and saving it in two PDS (Permanent Data Service) files(HiPath 5000).

5.3.1.1.1 Automatic Customer Data Backup

HiPath 3000

A two-stage concept guarantees automatic customer data backup.

A complete CDB backup version can be found on the MMC at any time. Deltas to this backupare stored in an SRAM area (with battery backup) in the central control board. If the SRAMarea is full, the customer data is automatically backed up. This means that the entire CDB, in-cluding SRAM content, is copied from the SDRAM in the central control board to the MMC. Thecurrent CDB is simultaneously stored on the MMC along with the “old” CDB, which is not delet-ed until the current CDB is completely stored on the MMC.

In case of a power outage, the SDRAM content that has no battery backup is completely lost.However, by reaccessing the CDB backup on the MMC, the system’s database can be restoredto the state it was in prior to the power outage.

Regardless of the volume of changes to the database, HiPath 3000 always performs an auto-matic complete CDB backup at midnight, system-time.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




HiPath 5000

On the communication server, RAM data is copied automatically every three minutes andstored in the file hicom.pds. This file contains the complete data description of the HiPath

5000 with emulated HG 1500 boards. This includes:

● Customer data

● Trace

● Error history

● Call detail data

● Status data

5.3.1.1.2 Manual Customer Data Backup with HiPath 3000You can perform a manual CDB backup using HiPath 3000/5000 Manager E (in online mode)or Manager T.

5.3.1.2 Customer Data Backup with HiPath 3000/5000 Software Manager

Definition

The HiPath 3000/5000 Software Manager supports, among other things, the backup of custom-er databases (Backup Manager) from all HiPath 3000/5000 systems in the same customer net-

work (see also Section 5.3.4, “Backing Up System Components (Backup Manager)”).The CDB backups are stored in a directory which must be defined in advance. The data backupcan either be started manually immediately or performed at a predefined time. A cyclic backup,which saves the customer data at a set time every day, is also possible.





3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.2.2 APS Transfer for HiPath 3000 Systems WithHiPath 3000/5000 Software Manager

Definition

The HiPath 3000/5000 Software Manager supports, among other things, updates of the systemsoftware (Upgrade Manager) of all HiPath 3000 systems in the same customer network. An up-date of the software of installed HG 1500 boards (HG 1500 V3.0 SMR-3 or later) can also beperformed.

The following options are available under the menu item “Upgrade”:

● upgrade all HG 1500 boards and HiPath 3000 systems

● upgrade HG 1500 boards (HG 1500 V3.0 SMR-3 or later)

●

upgrade all HiPath 3000 systemsNote: The file format “*.fli” must be selected for APS transfer using HiPath 3000/5000 Soft-ware Manager.

The software (APS and/or HG 1500) is updated in two steps. First, the new software is loadedto a system memory known as the "shadow area". This occurs in the background independentlyof the system status.

In the second step, the new software version must be made available, in other words, the switchfrom the current software version to the new software version must take place. The current soft-ware is replaced by the software in the shadow area and thus deleted. The changeover caneither be started immediately once the software has been loaded or performed at a predefined

time.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.3 Determining System Information and Installed SoftwareComponents (HiPath Inventory Manager)

DefinitionHiPath Inventory Manager is a service for detecting the installed software components and sys-tem information in a HiPath 3000/5000 network. System information is only determined uponinitial start-up of the service.

The relevant information can be displayed in table format by clicking one of the following but-tons:

● Master SetupInformation including version and installation date of the master setup.

● HiPath 3000Hardware and software information regarding the HiPath 3000 systems in the network andthe installed HG 1500 boards.

● HiPath ApplicationsInformation regarding the following software components:

– MS Windows components (MS Internet Explorer, DNS server, DHCP server)

– Media Streaming

– TAPI

– CCMC, CCMS, CMD, CSP

– Administration – HiPath 5000 Server

– GetAccount

– HiPath 3000/5000 Manager E

– Common Software

● Operating SystemInformation regarding the current operating system.

All information can be updated at any time via the "Update data" button.

The system information is automatically determined when the HiPath Inventory Manager ser-vice is started for the first time. A cyclic update can be performed every ≥ 1 days. The systeminformation can be queried manually at any time. This should always be done before an update/ upgrade, for example.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.4 Backing Up System Components (Backup Manager)

Definition

The HiPath 3000/5000 Software Manager allows the following system components and data-bases of a HiPath 3000/5000 network to be backed up:

● Full backup (= default setting)This option creates a data backup for all HiPath 3000 systems and HG 1500 boards in theHiPath 3000/5000 network as well as databases (Feature Server, SQL Server).

● Backup HiPath 3000With this menu item, all HiPath 3000 systems in the HiPath 3000/5000 network are dis-played in an overview. It is possible to back up the data of a specific system or of all dis-played HiPath 3000 systems.

● Database backupWith this menu item, all databases (Feature Server, SQL Server) are displayed in an over-view. It is possible to back up the data of one or of all database(s).




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.5 Diagnostics Options

5.3.5.1 Recording HiPath 3000 Board Status

5.3.5.1.1 Central Control Boards

Run LED

A RUN LED that displays the system’s operating capacity is located on the central controlboard.

Options Available?

You can call up the following options using the HiPath 3000/5000 Manager E:

● CMA

● CMS

● LIM

● IMODN

● MPPI, UAM (only with HiPath 3550, HiPath 3350) or UAMR (only with HiPath 3500, HiPath3300)The presence of one of these announcement and music modules is displayed as"Option 5".The ALUM4 option cannot be displayed.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.5.1.2 Power Supplies

5.3.5.1.3 Peripheral Boards

View Status of Peripheral Boards

You can use HiPath 3000/5000 Manager E or Manager T to view the statuses of all peripheralboards. Display is limited to the following statuses per board:

● Board not inserted

● Board defective (not loaded)

● Board disabled

● Board enabled (active)

● Board busy (at least one station or line from this board is disconnected, is being called, oris busy).

Table 5-1 Power Supply Status Displays

Board Status Display

HiPath 3800

LUNA2 The LED displays the operating status (on or off).

Power Box PB3000 The LED displays the operating status (on or off).

HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300

PSUP The LED displays the 5 V output voltage.

UPSC-D, UPSC-DR ● A green LED displays the 5 V output voltage.● A yellow LED displays the additional power of –48 V output volt-

age provided by an external power supply unit (EPSU2 orEPSU2R).

Power Box PB3000 The LED displays the operating status (on or off).




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


For ISDN boards, the status of the reference clock is displayed:

● No reference clock

● Reference clock for clock generator is created.

When viewing the board status using the HiPath 3000/5000 Manager E, all peripheral boardsintegrated into the system are presented in a table. The status display is updated every 3seconds.

With the Manager T, you can only view the status of one board at a time. You can also updatethe status display by pressing a key.

You cannot perform additional activities with the HiPath 3000/5000 Manager E and Manager Twhile viewing the status of a board.

Table 5-2 HiPath 3000/5000 Manager E - Example of Status Display of Peripheral

Boards

Slot Board Not in-serted

Defective Lockedout

Free Busy Clocksource

1 STLS2 X X X

2 SLU8 X

3 SLA4 X X

4 TLA8 X

5

6

7 TS2 X X

8 16SLA X

9

10 SLMO24 X



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.5.2 Recording HiPath 3000 Trunk Status

HiPath 3000 records the current status of each individual trunk in a table. If the status changes,the new status along with the time stamp is entered. You can use HiPath 3000/5000 Manager

E to view the trunk status, in which case the following information is provided.

Data Content

Date Date of the event (as stored in system)

Time Time of the event (as stored in system)

Trunk number Number of the trunk

Slot/Port Slot and port number

Status ● Trunk status: – Inactive

– Incoming call – Outgoing call – Trunk-to-trunk connection – Trunk disabled (using lockout switch or HiPath 3000/5000

Manager E) – Trunk failure

● Number of the connected station




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.5.3 Recording Station Status

HiPath 3000 records the current status of each individual station in a table. You can use HiPath3000/5000 Manager E to view the station status, in which case the following information is pro-

vided.

Data Content

Station name Name of the selected station

Slot, Port Example: 7-1

Telephone model Example: optiPoint 500 advance

Telephone status Active or inactive

DID number External number of the selected station

Voice Menu language of selected station

Connection status ● Inactive: The telephone is idle.● Busy: The telephone is off the hook, but not yet di-

aled.● Waiting: The telephone call is in the queue.● Connected: The telephone is connected to a sec-

ond telephone with a trunk or a hunt group member.● Holding: The telephone is on hold.● Error: The connection cannot be established due to

an error (for example, invalid telephone number).● Call: The telephone is called.

Connected to The number of the connected station or trunk

Forwarding status ● Off: No call forwarding activated.● Internal: Call forwarding activated only for internal

calls.● External: Call forwarding activated only for external

calls.● All: Call forwarding activated for all calls.

Destination Number of call forwarding destination



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.5.4 Recording the Status of the HiPath 3000 V.24 Interfaces

You can use HiPath 3000/5000 Manager E to view the current status of the V.24 interfaces, inwhich case the following information is provided.

● Status of the trunks (1 = active trunk, 0 = inactive trunk)

The individual trunks are assigned as follows:DTR = HiPath 3000DSR = TelephoneRTS = HiPath 3000CTS = Telephone

This means, for example, that incorrectly connected or damaged cables can be determined(for more information on this, refer to the HiPath 3000/5000 Manager E Help.).

● V.24 MonitoringThe number of sent/received bytes within a selected time period can be recorded and thendisplayed/saved using a text editor (default = MS WordPad ® ).

The failure and restart of a V.24 interface generates an entry in the eventlog and releases aremote error signal (V.24 failure = “Check printer” error message, V.24 restart = Withdrawal oferror message).

Activated features Status of activated features (on or off):● Do not disturb

● Call forwarding (device status)● Advisory text● Room monitor● Code lock● Station number suppression● Group ringing● Ringer connection● Hunt group● Silent call waiting● Handsfree answerback● Call waiting release● Transfer of ringing (only for MULAP)● Call forwarding MULAP (only for MULAP)

Connected station List of the connected stations

Data Content




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.5.5 Trace Options for HiPath 3000

Tracing ISDN Activities

This feature allows the user to trace ISDN telephones (subscriber ports) and ISDN trunks (trunkports) in real time. ISDN activities are routed to HiPath 3000/5000 Manager E and saved in atrace file. Only the ISDN sequences are displayed on the monitor, not the content of the ISDNmessages.

The call is made via HiPath 3000/5000 Manager E: Maintenance, "Call Monitoring" tab. TheStart button starts Call Monitoring, whereupon the data of all available ports in the system isread out.

If the trace session is over, you can start the ISDN Message Decoder (ISDN Tracer) and useit to convert the trace file into a readable format (only English). You can also read out the tracedata using remote service.

The ISDN Message Decoder is a 32 bit application which converts the ISDN layer 3 messagesand information elements into a readable format. Since you cannot find out from the trace filewhether it deals with an information element from a Euro ISDN or a QSig configuration, youhave to select the protocol. You may select the following settings from the main menu:

● Raw (default setting)

● Euro ISDN

● QSig V1

● CorNet-NQ

With the “Raw” setting, the Hex values are only decoded, not interpreted. With the other twosettings, the Hex values are decoded and interpreted per feature (CC, AOC, ...).

Tracing Call-related Activities

You can trace all activities from any telephone, trunk, etc., that is released by a call. These in-clude consultation calls, conference calls, and hunt groups, for example.

>Special user rights are required for activating the Trace setting in the Maintenance

menu, that are exclusively reserved by the user group Development.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.5.6 HiPath Manager PCM Trace Monitor for HiPath 5000

Communication between the different HiPath 5000 applications is organized using various buff-er tables and messages. You can monitor the individual entries in the different buffer tables, ex-

changed immediate messages, program and communication messages for the relevant com-ponent in a separate trace window, in other words, a separate window is opened for eachcomponent (application).

The trace windows can be viewed using the Trace Monitor and swapped out for further process-ing.

Trace messages can be displayed for the following HiPath 5000 applications:

● Feature ServerTwo trace files are available:

– \winnt\system32\carlogfile.txt provides details on which HG 1500 boards have logged on to the network and when.

– \winnt\system32\rgtracefile.txt provides details on when the individual HG 1500 boards were assigned a station num-

ber.● Presence Manager

Two trace files are available:

– \winnt\system32\dssdiagnosefile.txt

– \winnt\system32\dsslogfile.txt

● HiPath Manager PCM AdministrationAdministration of the configuration parameters for component control by the user, for gen-eral parameters, for call charge evaluation and analysis.

● HiPath GetAccountInternal component that is responsible for evaluating and saving call charges and for im-mediate printing.

>This documentation does not cover interpretation of the trace window contents bythe Trace Monitor. Trace files are used for problem analysis and are interpreted byService Support during servicing.The description below can be used to determine the work steps required for Trace

Monitor navigation and control and for swapping out the trace contents to a file.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.5.7 Eventlog for HiPath 3000

HiPath 3000 features an eventlog where accrued errors are classified according to error classand error number with the date/time of the original error. You can use HiPath 3000/5000 Man-

ager E to read out the eventlog.

5.3.5.8 Testing Telephones

After startup and country adaptation, you can activate the telephone test on any optiPoint 500or OpenStage telephone using a code or the service menu. This test checks the display (yournumber is displayed), LEDs, and calls. The tests ends automatically after a period of time.During the test, you can satisfy yourself that the visual and audio components function properly.

Test procedure on the system telephone

If the time and date do not appear in the display after startup, either the system telephone orthe cable path is defective. Either exchange the system telephone or check the cable path.

Table 5-3 Terminal test

Step Entry Explanation

1. *940 Code for terminal test

2. – For approximately five seconds, all LEDs blink quickly (ex-cept for the Service menu LED), all display pixels are acti-vated, and you can hear a tone.

>If the test does not react as described, an additional power supply (plug-in power

supply unit) for the relevant system telephone may be necessary.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.5.9 Event Viewer for HiPath 5000 (Eventlog)

Introduction

The Event Viewer (Eventlog) is one of the tools supplied with NT-based operating systems(Microsoft Windows NT, Microsoft Windows 2000, Microsoft Windows XP, etc.). The EventViewer administers logs that record information on programs, security, and system events onthe computer. You can use it to display and administer eventlogs, to gather information on hard-ware and software problems, and to monitor security events.

You can use this standard tool to obtain status information for the HiPath 5000 server and anyapplication server present.

All events associated with the server(s) and its (their) applications are saved. The events pro-vide a quick and, above all, time-specific overview of all relevant actions (status, information,

warning, error, etc.).The tool itself handles the event entries. You can specify the length of the event file, the validityof events in days, the reaction when the maximum size has been reached, and the display filter,for example.

You can save the resulting event file (log file) under any name.

Starting the Event Viewer

Start the Event Viewer from the Windows Start menu: Start/Programs/AdministrativeTools/Event Viewer




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.5.10 HiPath Fault Management

HiPath 3000 and HiPath 5000 systems have a separate SNMP agent that allows access to var-ious system data that is stored in its MIB or Management Information database. The MIB pro-

vides basic system information, status information, event-related data, and information on in-stalled hardware (slots) and configured connections (ports).

HiPath Fault Management can read information from the HiPath 3000 and HiPath 5000 systemMIB via SNMP requests. This allows the system to permanently monitor the status of the net-work components and to include changes of status in the network administrator information.

A graphic map of the network displays the topology and the current status of the network com-ponents.

For detailed information, refer to the product-specific documentation for HiPath Fault Manage-ment.

SNMP Functionality

Simple Network Management Protocol (SNMP) represents a convenient platform within theTCP/IP protocol family for management tasks in the HiPath 3000 and HiPath 5000 software.SNMP is used more or less as a management agent on HiPath 3000 and HiPath 5000 and han-dles central monitoring and administration of LAN network components, including the HiPath3000 and HiPath 5000. This involves

● address the HiPath 3000 and HiPath 5000 over the TCP/IP protocol family.

● access data from external management applications such as HiPath Fault Management.

● implement remote maintenance jobs (such as online port status, disabling and enablingports, and determining free ports).

● transmitting service-related class B errors

● visualize the operating status of a HiPath 3000 and HiPath 5000.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.5.11 Licensing Analysis

5.3.5.11.1 Analysis Using Customer License Manager (CLM)

The CLM installation directory (for example, C:\Program Files\licensing\licensemanager) contains the Trace directory among other things. Each time the TomCat Web serv-er is started, a new subdirectory is created to which the trace output is then written. Trace out-put can be viewed using MS Internet Explorer.

5.3.5.11.2 Analysis Using Customer License Agent (CLA)The CLA offers two analysis options:

Log files

The Customer License Agent (CLA) manages a configuration log and error log. Both logs areviewed using the CLM. This provides a good overview of an error situation that helps to narrowdown an error to a specific area, for example.

Trace files

The CLA records detailed information about its internal processes in a text file that is stored inthe bin subdirectory of its installation directory. The degree of detail (off, low, standard, all) andthe size (in MB) of this recorded information can be defined using the Customer License Man-ager (CLM).

>This documentation does not cover interpretation of the analysis data. Trace files,

log files, etc. are used for problem analysis and are interpreted by Service Supportduring servicing.





3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.6 HiPath 3000 Error Messages (Entries in the Eventlog for HiPath3000)

ClassificationAccrued errors are classified according to error class and error number. The three different er-ror classes are described below:

● Error Class A = Customer-related errorHiPath 3000/5000 Manager E fails to issue a signal/message. Class A errors are indicatedon the optiPoint Attendant display. The customer can correct them without service support.

The following error messages are implemented at present:

– “Printer Alarm” (caused by empty paper tray, for example)

– “Fan Failure” (caused by failure of the fan with HiPath 3500 or HiPath 3300)

– “Revisor Alarm” (caused by overflow in the MMC log area, for example).

– "Too Many Key Modules" (caused by attaching more than the maximum possible num-ber of optiPoint key modules)

● Error Class B = Service-related errorsClass B errors are signaled to the HiPath 3000/5000 Manager E, and can be automaticallyforwarded to a service center.Errors of this class are, for example, failure of the boards, individual ports, or trunks. Youcan generally correct these errors by replacing the hardware, reconfiguring the customer

database, or by working together with the carrier.

● Error Class C = Development-related errorsHiPath 3000/5000 Manager E fails to issue a signal/message.Class C errors require diagnosis and problem analysis by specialists.

5.3.7 HiPath 5000 Error Messages (Event Viewer Entries for HiPath5000)

Event Viewer Entries for HiPath 5000

● Feature server events

● GetAccount events




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.8 Error Correction

5.3.8.1 Automatic Error Correction

One of the below recovery actions is assigned to each error in the error memory. These recov-ery actions are programmed to automatically correct errors that occur.

● Hard restart

● Reload board

● Reload CDB backup

● Port lockout

● Power failure transfer (loop start)

● None

A watchdog activates continuous loops.

If no recovery measure is assigned or if the one that is assigned fails, a service technician hasto correct the error manually.

5.3.8.2 Manual Error Correction Without HiPath 3000/5000 Manager E

Manually Activating Restart (Reset)/Reload

Pressing the reset button on the central control board

● initiates a Reset (Hard restart of the entire system with the current CDB) if the button ispressed for less than 5 seconds. The Run LED lights up when the Reset button is pressed.

● initiates a Reload if the button is pressed longer than 5 seconds. The Run LED disappearsafter approximately five seconds as verification that the reload has been initiated. The en-tire content of the customer database is replaced by its default version. All country and cus-tomer-specific settings are lost.

Locking out and Releasing Boards and Ports

You can lock out and release ports using the lockout switch located on the board. The lockoutprevents renewed seizure after the current connection has finished. It creates

● a port lockout in an outgoing direction on analog trunk boards.

● a port lockout in outgoing and incoming directions on trunk boards.

● a lockout of the entire board for subscriber line modules.






A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.9 Remote Service

Definition

Remote service is described as communication between the service center and HiPath 3000/ 5000 using public telecommunications networks to fulfill service tasks. These tasks are

● remote system administration,

● remote administration of Plus products via the system,

● remote correction of system software (APS transfer),

● automatic signaling of error messages.

Remote service facilitates the administration and maintenance of various communication sys-tems from a central location. You can establish a connection to the system via an integrateddigital modem (B channel) or an integrated analog modem (IMODC) or via HG 1500.

HiPath 3000/5000

Plus Products

Service centerservice PC

withHiPath 3000/5000

Manager E

Central Board

Modem

LIM

CustomerLAN

PSTN(analog or

digitaltelecommunications

network)



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.9.1 HiPath 3000 Connection Options

● HG 1500All HiPath 3000 systems can be accessed remotely with a LAN-LAN link via the HG 1500

board.

● Integrated analog modem IMODNThis modem enables remote access to all systems in the HiPath 3000 product line. Accessis achieved using any trunks, tie trunks, and all subscriber lines. IMODN is designed as aplug-in card.

The IMODN is treated as a pseudo port. It receives a number in the system that can bereached internally through direct internal dialing (DID). You can cancel the DID numbermanually to prevent external access.

● Integrated digital modem (B channel)An integrated B channel modem is available with all systems in the HiPath 3000/5000 prod-uct line. This type of modem facilitates remote access using both digital trunks, tie trunks,as well as S0 subscriber lines. Data transmission is supported according to Protocol X.75.

The digital modem is treated as a pseudo port. It receives a number in the system that canbe reached internally and through direct internal dialing. You can cancel the DID numbermanually to prevent external access.

Access to the analog/digital modem

The customer must enable the access to both modems by entering a six-digit PIN code. If theservice center is to make a connection to the HiPath 3000/5000 over a modem, it may be nec-essary to enter this individual code. It depends on which trunk type is used for the modem ac-cess. The following applies to the system default:

● Access over ISDN trunk = enable procedure: customer must enter PIN code.

● Access over another trunk = login without code: PIN code is not necessary.

If necessary, the system administration (only by using Manager T) can reset the PIN code backto the default value.

7CautionBe sure to disconnect the system from the power supply before removing or in-serting integrated analog modems (IMODN).




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.9.2 HiPath 5000 Connection Options

In general, the connection to HiPath 5000 is established via special software programs, suchas pcANYWHERE. Please refer to the relevant product documentation for information on pos-

sible applications.

If the customer agrees, Remote Access Service RAS can also be used, provided this serviceis active on the HiPath 5000 server.

5.3.9.3 Remote System Administration

Remote Administration with HiPath 3000/5000 Manager E

To establish a remote connection between HiPath 3000/5000 and the service center (HiPath3000/5000 Manager E), the following options are available:

● Callback

● Service call via code

● Automatic error signaling

Any one of these options establishes a connection using the integrated digital modem (B chan-nel) or the integrated analog modem (IMODN).

Callback

HiPath 3000/5000 can manage up to 6 different callback indices (callback passwords and theirrelevant callback numbers), in which case the first callback connection is also the destinationof the automatic error signaling. For each callback connection, you can select either the digitalmodem (B channel) or the analog modem (IMODN).

Service call via code

You can use any telephone to initiate a HiPath 3000/5000 service call to the service center byselecting the connection setup option “Service call using a code” and activating the feature “Re-mote access immediately after installation”. In contrast to the usual callback procedure, thiscallback (service call) is not activated by HiPath 3000/5000 Manager E itself, but by any tele-phone you choose. Callback initialization is essentially skipped.

The service call destinations are the six callback indices that also apply to callback. You arenot required to enter the relevant passwords.

Automatic error signaling

Error Class B errors can be transferred to a service center automatically. For more informationon this, see Section 5.3.9.5.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




DTMF Remote Administration

This feature facilitates remote system administration by transmitting DTMF signals. The userinterface (menu prompt) is the same as that of the Manager T for system administration on site.

DTMF remote administration can be performed using either the analog or digital trunks.

5.3.9.4 Remote Correction of System Software (APS)

The service center performs the APS transfer.

5.3.9.5 Remote Error Signaling

Error Class B errors can be transferred to a service center automatically. To do this, the “Errorsignaling” flag has to be activated and a number entered under the callback index 1.

The error report consists of one header and the error information that is transmitted in binaryform. The header contains a unique identifier that recognizes the customer system that sentthe error reports.

5.3.9.6 Remote Administration and Access Using PPP

You can establish a connection between the system/Plus product and the service center usingeither the integrated digital modem (B channel) or the integrated analog modem (IMODN). Datais exchanged in both cases using Point-to-Point-Protocols (PPP).

For more detailed information on the possible functions, see Chapter 4, “HiPath 3000/5000 inthe LAN Network”.

Remote system administration

You can also operate HiPath 3000/5000 Manager E in conjunction with the relevant infrastruc-ture (RDT network, router) using PPP.

For more information on this, see Section 5.2.4, “Remote Administration of HiPath 3000/5000via PPP”.

Remote administration of Plus Products

You can use HiPath 3000/5000 to administer Plus Products from a central service center. Hi-Path 3000/5000 merely provides the transmission medium for this. The actual Plus Product ad-ministration is performed via special software programs, such as pcANYWHERE.

For more information on this, see Section 5.2.5, “Remote Administration of Plus Products viaPPP”.





3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.10 Access Security

5.3.10.1 Logon With User Name and Password

Security

To ensure that authorized users have access to the HiPath 3000/5000 and to prevent unautho-rized accesses, users must be identified by a user name and authorized by a password. Thisapplies to all local and remote administration and maintenance procedures using HiPath 3000/ 5000 Manager E, Manager T, HiPath 3000/5000 Manager C, Assistant TC, and AMHOST.

After the first system startup and during country initialization, you can select between the fol-lowing security options:

● variable password (default)

● fixed password concept

Variable Password

Up to 16 users can be assigned their own user ID with individual name, password, and a usergroup consisting of six pre-determined user groups. Only the data authorized for the relevantuser group can be read and administered.

During the first login, the system requests the identity of the user and asks for a new password(max. 15 characters from the optiPoint 500 character set). This then overwrites the default username (31994) and default password (31994). This first user is then automatically assigned tothe user group “System Maintenance”. The system informs the user that no user is configuredin the system and that the user has been assigned with “System Maintenance” authorization.Using HiPath 3000/5000 Manager E or Manager T, additional users and their passwords canbe configured in the user administration.

If a user forgets a password, it has to be deleted and reconfigured by a different authorized user.If all authorized users forget their passwords, the system must be regenerated.

Fixed Password

When using the fixed password, only fixed user groups with unchangeable default user names

and default passwords are used. Also, new users cannot be configured in the user administra-tion.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


Changing Password Types

Only with Manager T can you change from a variable password to a fixed password type andvice versa. To do this, you have to re-initialize the country settings. This switches the entire

content of the customer database (including user names and passwords) to a default state.

If you perform country initialization in a system with a variable password, the previously createduser names and passwords remain intact as long as you do not subsequently change the pass-word type.

If a CDB is read from a system in which the default user names and passwords were changed,this CDB cannot be loaded into a HiPath 3000/5000 system that was changed to a fixed pass-word type. Before reading this CDB, you have to set up a user (user name and password) inthe system that matches a user group with a fixed password. Once this user has been set up,the CDB can be read from the HiPath 3000/5000. With this user name and ID, you can nowload the CDB into the system switched to the fixed password type.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.10.2 Pre-determined User Groups and Their Access Rights

User Groups With a Variable Password

The following table shows the six pre-determined user groups and their access rights.

Table 5-4 Variable Password: Pre-determined User Groups and Their Access Rights

No. User groups

User rights U s e r

a d m i n .

A u d i t

S y s t e m m a i n t .

( S e r v i c e )

C u s t o m e r a d m i n .

( C u s t o m e r )

A c c o u n t i n g

D e v e l o p m e n t

1. ● Setting up/deleting users● Assigning users to user groups

X X1

1 As long as no user is assigned to the “User Administration” user group.

2. ● Assessing and archiving backup-related logfiles

● Reader rights to system data (error memory,for example), not including confidential cus-tomer information

X X2

2 As long as no user is assigned to the “Audit” user group.

3. ● Access rights to all system data (not includingdevelopment access rights) as long as no us-ers are assigned to other user groups.

X

4. ● Access rights to confidential customer infor-mation

● Executing customer actions (printing out cer-tain lists, for example)

X3

3 As long as no user is assigned to the “Customer administration” user group.

X

5. ● Access rights to non-confidential customerinformation

X X

6. ● Access rights to parameters and call detailrecording actions (not including interface pa-rameters for the output device)

X3, 4 X4

4 As long as no user is assigned to the “Accounting” user group.

X

7. ● Access rights of the “System Maintenance”

user group● Setting up and reading certain parameters to

which no other user group has access.

X




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


User Groups With a Fixed Password

The following table shows the unchangeable user groups and their rights.

Table 5-5 Fixed Password Concept: Fixed User Groups and their Access Rights

No. User groups

User rights

S y s t e m m a i n t . ( S e r v i c e )

N a m e / P a s s w o r d =

3 1 9 9 4 / 3 1 9 9 4

C u s t o m e r a d m i n . ( C u s t . )

N a m e / P a s s w o r d :

–

M a n a g e r T C = * 9 5 / ( P a s s w o r d

n o t n e c e s s a r y )

– M a n a g e r C = o f f i c e / o f f i c e

D e v e l o p m e n t

1. ● Assessing and archiving backup-related log files● Reader rights to system data (error memory, for exam-

ple), not including confidential customer information

X X

2. ● Access rights to all system data (not including develop-ment access rights)

X X

3. ● Access rights to confidential customer information● Executing customer actions (printing out certain lists,

for example)

X X X

4. ●

Access rights to non-confidential customer information X X X5. ● Access rights to parameters and call detail recording

actions (not including interface parameters for the out-put device)

X

6. ● Setting up and reading certain parameters to which noother user group has access.

X



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.10.3 System Access Options

The user’s access rights, in other words the data that the user may read or manage, alwaysdepend on the user group to which the user is assigned.

Service Tools

● Manager T and Assistant TCLog on by entering your user name and password(independently of the lock code)The system can only be accessed using the first two UP0/E connections from the firstSLMO/SLU board in the system.

● HiPath 3000/5000 Manager E and HiPath 3000/5000 Manager C (local)Log on by entering your user name and password

● HiPath 3000/5000 Manager E (remote), direct connectionLog on by entering your user name and passwordThe system can be accessed directly using the integrated digital modem (B channel) or theintegrated analog modem. However, the user is required to establish a 5 digit access codebeforehand.

● HiPath 3000/5000 Manager E (remote), callback connectionLog on by entering your user name and passwordThe system can be accessed using the integrated digital modem (B channel) or the inte-grated analog modem. However, you have to set up a callback index beforehand.

●

HiPath 3000/5000 Software ManagerLog on by entering your user name and password

AMHOST

The AMHOST (Administration and Maintenance via HOST) feature allows Plus products toread certain system information and to change it, if necessary. To enable Plus products to ac-cess the system, you have to set up a user without a user group in the HiPath 3000/5000 defaultuser administration. Enter “AMHOST” as the user name and “77777” as the default user pass-word.

You can only change this password if the system is configured using a variable password. Inthis case, delete the “AMHOST” user and reconfigure the system with the same user name anda new password.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.10.4 Customer Data Security

When saving a customer database on the hard disk, a user table (part of the user administra-tion) with user name and encrypted passwords are also saved. This guarantees access secu-

rity when the customer database is opened offline later on.

When opening the customer database offline, you are requested to enter your user name andpassword. The data that you enter is compared to the data in the user table. In this case, theuser group verified during this process also determines the access rights.

When loading an offline customer database into HiPath 3000/5000, the user table that goeswith it should not be loaded into the system. Otherwise, the system-specific user administrationwould be distorted.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




5.3.11 Automatic Logging of Administration Procedures

Definition

All accesses to customer-related data in the HiPath 3000/5000 are automatically logged in anarea of the MMC (LOG area) reserved for this purpose. The information recorded includes whothe user is, the data manipulated by the user, and the time. An authorized user (member of the“Audit” user group) can transfer the system data to a PC and assess it.

5.3.11.1 Logging

A log entry contains the following information:

● Date and time

●

User name and user group● Type of activity (format identification) and activity (command entry)

5.3.11.1.1 Format Identification and Command Entry

The following format information is logged:

● Manager T (1)All activities are logged, regardless of system access. The respective code with the mostimportant parameters is recorded as the command entry (station/number, for example).

● Assistant TC (2)Same as Manager T (1)

● Session Information (3)The system access is logged, regardless whether it is logged using Manager T, HiPath3000/5000 Manager E, or other HiPath systems. Possible command entries are:A0-1 = Login procedureA0-2 = Logout procedureA0-3 = Unauthorized login attempt

● HiPath 3000/5000 Manager E Database (4)Access to the database is logged using HiPath 3000/5000 Manager E. Possible commandentries are:A1-1 = Database readA1-2 = Regeneration of CDB (Load CDB into the system)A1-3 = Write database




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


● Program Systems (5)APS transfers and system boots (first bootup, for example) are recorded. Possible com-mand entries are: – A2-1 = APSXF started

– A2-2 = APSXF ended – A2-3 = APS boot (APS stamp also included)

● HiPath 3000/5000 Manager E Maintenance (6)Maintenance activities which can be assigned with the following command entries arelogged: – B1-1 = Read error memory – B1-2 = Delete error memory – B2-1 = Out of service – B3-1 = Read Direct Memory Access – B3-2 = Write Direct Memory Access

– B4-1 = Delete base station status overload – B4-2 = Delete base station restart – B5-1 = Digital loopback change – B6-1 = Trunk rolling change – B7-1 = Read trunk status – B8-1 = Delete trunk error counter

● Simulated or pseudo Manager T format (7)The HiPath 3000/5000 Manager E records the offline changes of a CDB as a “simulated”Manager T command. For data areas subject to change by HiPath 3000/5000 Manager E,pseudo areas are generated. When loading an offline CDB into the system, the following

simulated commands are logged as command entries:C1 = Pseudo area “System parameter” – C1-1 System fags/CMI – C1-2 System intercept/AC – C1-3 Tones and calls – C1-4 Direction flag special (Variable direction#) – C1-5 System settings – C1-6 Host Link Interface – C1-7 Relocate activationC2 = Pseudo area “System timer”

– C2-1 System timerC3 = Pseudo area “S0 configuration” – C3-1 Station bus – C3-2 Line supervision – C3-3 ModeC4 = Pseudo area “Lines” – C4-1 Loop start parameter (Variable Slot/Line#)C5 = Pseudo area “Digit analysis” – C5-1 Internal number (Variable Stn#, Grp#)



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




– C5-2 Service codesC6 = Pseudo area “Summer time” – C6-1 Summer timeC7 = Pseudo area “Directions”

– C7-1 Direction flags (Variable direction#)C8 = Pseudo area “Door setup” – C8-1 Door setup (Variable door#)C9 = Pseudo area “UCD Flags” – C9-1 UCD FlagsC10 = Pseud area “Delete system counter” – C10-1 Delete system counter

● HiPath 3000/5000 Manager E online (8)Archives from the log file and the user administration are logged. Possible command en-tries are:

– D1-1 = Archive – D2-1 = New user – D2-2 = Delete user – D3-1 = Change password

>Logging External Accesses (Solutions, Applications)Plus products used with “AMHOST” can only make limited changes. Because thesechanges ’automatically’ run simultaneously (Check In and Check Out for hotel solu-tions, for example), these are not logged. Only the session information (user nameis “amhost”) with the command entries “Login procedure” and “Logout procedure”are logged.




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm


5.3.11.2 Issuing and Saving Log Data

Data is automatically logged in an area (LOG area) on the MCC reserved for this purpose. Itcannot be switched off.

If approximately 80 % of the MMC log area capacity is exceeded, a Class A error is issued.This error is dealt with like all Class A errors and is displayed on the optiPoint Attendant as “Re-visor Alarm.”

The log should now be read out and archived, in other words it should be saved in an archive file(file extension = arc). If an archive is not created, the oldest datablock is overwritten if there isa danger of overflow.

You can only issue log entries using HiPath 3000/5000 Manager E. You cannot retrieve the logentries from the system until you have logged on as a user with “Revisor” rights.

Archive

If you request an archive (storage), the system checks whether or not there is already an ar-chive file (file extension = arc). If it is a file with log data from a previous archive, the file mustmatch the current customer. In case of a positive result, the system log entries are retrievedand attached to the existing data in the archive file. At the same time, the data in the systemis deleted.If malfunctions occur during this procedure (for example, line interruption), the entire procedureends and the archive has to be restarted.

If no archive is requested, the revisor can retrieve, view, and print the log entries. However, log

entries remain in the system.

Multimedia Card (MMC)

When replacing the multimedia card, the following applies:

● If the memory area for logging data is empty, logging restarts.

● If the memory area for logging data is not empty, logging continues.



3000sb5.fm

A31003-H3580-Y100-10-7618, 01-2011




Example of a Log Printout

The following assumption applies as an example: The first system boot up has taken place.Customer-specific programming was completed.

The sample printout (without consideration of headers and footers) refers to the following infor-mation concerning administration procedures:

● The Revisor (“rev” user in “R” (Revision) user group) has generated an initial archive.

● The Service (“serv” user in “S” (system maintenance) user group) has read out the systemdatabase, changed 20 station names, and written them again to the system.

● The Customer (“pnkm” user in “A” (Administration) user group) has changed two additionalstation names.

● The Revisor has retrieved the most recent log entries and printed them out.

1050 00-11-25 15:57:10 rev(R) (6)D1-1 Archive

1051 00-11-25 15:58:22 rev(R) (3)A0-2 Logout procedure

1052 00-11-26 09:20:15 serv(S) (3)A0-1 Login procedure

1053 00-11-26 09:21:35 serv(S) (4)A1-1 Database read

1054 00-11-26 09:21:52 serv(S) (7)14-12-*(20) Station name

1055 00-11-26 09:22:45 serv(S) (4)A1-3 Write database

1056 00-11-26 09:23:25 serv(S) (3)A0-2 Logout procedure

1057 00-11-26 10:10:15 pnkm(A) (3)A0-1 Login procedure

1058 00-11-26 10:11:15 pnkm(A) (2)14-12-”30” Station name

1059 00-11-26 10:11:35 pnkm(A) (2)14-12-”31” Station name

1060 00-11-26 10:12:15 pnkm(A) (3)A0-2 Logout procedure

1061 00-11-27 11:20:30 rev(R) (3)A0-1 Login procedure




A31003-H3580-Y100-10-7618, 01-2011


3000sb5.fm




3000sb6.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Middleware

HiPath TAPI 120/170 V2.0

6 Middleware

6.1 HiPath TAPI 120/170 V2.0

6.1.1 Configurations and Restrictions

Configurations

The following TAPI 120/170 configurations are available:

● HiPath TAPI 120 V2.0 (1st party TAPI 3.0), see Section 6.1.2.

● HiPath TAPI 170 V2.0 (3rd party TAPI 3.0), see Section 6.1.3.

●

HiPath TAPI 170 V2.0 CSTA Service Provider (CSTA III), see Section 6.1.4.These configurations are not part of the HiPath 5000 CD.

Restriction

TAPI 120/170 (32-bit) requires HiPath 5000 RSM. HiPath 5000 RSM only operates withMicrosoft Windows Server 2003 (32-bit).



Middleware Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb6.fm


6.1.2 1st Party Function (Direct Connection)

There is a direct CTI connection (V.24 or USB) between the telephone and a workstation PC.The TAPI driver, i.e. the TAPI service provider (TSP) of the telephone is installed on the PC.

This driver provides a TAPI-compliant software access to the telephone functions, e.g. dial,hang up, accept.

The 1st party CTI functionality is available for all HiPath 3000 models in conjunction withHG 1500. Up to six TAPI 120 can be operated without a license. Licenses are mandatory forany additional TAPI 120s installed. The software, installation manual and supplementary infor-mation (datasheet) can be found at:http://www.enterprise-communications.siemens.com/global/Products.aspx (... -> Downloads).

HiPath 3000

TelephonePCCTI connection

LAN

Workstation





3000sb6.fm

A31003-H3580-Y100-10-7618, 01-2011




6.1.3 3rd Party Function (Connection Via Network)

There is no direct connection between the telephone and the PC. A TAPI server is connectedto HiPath 3000 via a CTI connection (V.24, ISDN or TCP/IP). The TAPI driver, i.e. the TAPI ser-

vice provider (TSP) is installed on this TAPI server. The PCs can control the HiPath 3000 tele-phony functions via LAN and the TAPI server, e.g. dial, hang up, accept.

TAPI 170 is activated via a license server. Test software, installation manual and further infor-mation (datasheet) can be found at:http://www.enterprise-communications.siemens.com/global/Products.aspx (... -> Downloads).

6.1.4 CSTA● CSTA interfaces: depending on the model, up to four interfaces are available.

● Applications: several applications can run in parallel, but they cannot send conflicting com-mands or be mutually exclusive.

● Monitor points: 1000

Four monitor points are required, for example, to monitor a station with four applicationsover CSTA.

● CSTA Message Dispatcher: up to 1000 CTI links (CSTA links)

● Call number length: Up to 8 digits (planned: 12 digits)

● Load behavior: incoming calls are rejected (busy) as soon as a traffic volume of 1400BHCA is exceeded. This happens when more than four calls are received within ten sec-onds. This does not affect call traffic within the node

HiPath 3000

Telephone

PC

LAN

Telephone

PC

TAPI serverCTI connection

WorkstationWorkstation






A31003-H3580-Y100-10-7618, 01-2011


3000sb6.fm


● Call center mode: If, as a customer of Siemens Enterprise Communications GmbH & Co.KG, you want to operate a call center with more than 32 agents at the CSTA interface, con-tact your country-specific Siemens organization to inspect additional configurations. For di-rect sales, please use the planning tool to inspect the dynamic performance limit of a Hi-

Path 37x0 configuration.

● CSTA Service Provider (CSP). The CSP component is always configured for:

– up to 64 nodes

– up to 1000 monitor points, system-wide

– theoretically, an unlimited number of CSTA interfaces to the applications. Until now, aCSTA application was tested with up to 10 nodes and up to 150 released agents witha load of 1400 BHCA.

●

From HiPath 3000/5000 V8, MULAP signaling will function on the CSTA interface. If HiPathTAPI 170 has not yet been updated, error messages may be shown when the "MULAPmonitoring" station flag is activated in Manager E; see Manager E administrator documen-tation -> Plus Products Flags/MW.

6.1.5 Functional Framework Conditions

The following framework conditions must be observed when using TAPI 120/170:

● Connection to HiPath platforms is via Ethernet LAN with TCP/IP and CSTA protocols.

● Only Microsoft Windows network clients can operate as TAPI PCs.

● Windows Remote TSP is used for establishing the TAPI connection to the client PCs. Thisis part of the security concept for the operating system.

● All client PCs and the server must be part of the same domain.

● Monitor points are not reserved exclusively for HiPath TAPI 170,; they are available to allconnected applications. This may considerably reduce the number of monitor points thatcan be used for HiPath TAPI 170. The number of configured points is thus dependent onthe entire installation, as well as the expected load and should not exceed 250 TAPI clients.

● The load created by accumulated reports from TAPI applications may lead to longer re-

sponse times in the HiPath platform.

● HiPath TAPI 170 must not necessarily be operated on a single server with multiple networkinterface or load balancing.

● Operation in conjunction with standard H.323 or SIP telephones is not possible.



3000sb6.fm

A31003-H3580-Y100-10-7618, 01-2011




6.1.6 Software and Hardware Requirements

TAPI 120: Software requirements for the server PC

● Operating systems for networking:

– Microsoft Windows Server 2003 (32-bit)

● Operating systems for single nodes:

– Microsoft Windows Terminal Server 2003 (32-bit)

– Citrix XenApp 6

TAPI 170: Software requirements for the server PC

● Operating systems for networking:

– Microsoft Windows Server 2003 (32-bit)

● Operating systems for single nodes:

– Microsoft Windows Terminal Server 2003 (32-bit)

– Citrix XenApp 6

Software requirements for client PCs

● Operating systems (remote TSP):

– Microsoft Windows XP Professional (all versions)

– Microsoft Windows Vista (excl. Home Edition)

– Microsoft Windows 7

● Connection variants: V.24, S0 or LAN

● Maximum number of clients:

The maximum number of TAPI clients is always restricted by the number of monitor pointsavailable on any platform, as well as by the traffic volume expected on these points.

– HiPath 3800: 250 – HiPath 3300: 60

– HiPath 3700: 250 – HiPath 5000 RSM: 1000 (system-wide)

– HiPath 3500: 130




A31003-H3580-Y100-10-7618, 01-2011


3000sb6.fm


6.1.7 Data Synchronization

When using TAPI 170 in the HiPath 3000/5000 network, configuration data is synchronized bythe CCMC (Central Configuration Manager Client) component:

When using TAPI 170 in the HiPath 3000/5000 network, the configuration data are synchro-nized by the CCMC (Central Configuration Manager Client) component:

Feature pro-vider data-

base

TAPI 170 da-tabase

HiPath 3000/5000 server

Synchronization viaCCMC



3000sb6.fm

A31003-H3580-Y100-10-7618, 01-2011




6.1.8 Features

The following features are available depending on the system used and the support of the TAPIapplications:

Features of the Components TSP/CMD

● Outgoing connection setup, incoming call acceptance, ending calls

● Call status display, call number display

● Call logging

● Call pick-up (group), consultation hold, toggle, call transfer, conference

● Speed transfer, redirect and call hold

● Touchtone dialing (DTMF) during conversation

● Call detail information

● Description of display

● Hookswitch status setting/retrieval

● Volume control for handset, speaker and headset

● Set LED mode

● Park/unpark

● Dynamic generation of lines via the application

● Call center features

– Retrieve/set/delete mailbox indicator (message waiting)

– Retrieve/set/delete call forwarding/do not disturb

– Additional information for forwarded/ redirected/switched calls

– Playing Music On Hold and recorded announcements (RCA)

– Trunk and UCD monitoring

– Call detail recording (with respect to call status)

– Unique call identification (in the general domain)

– Call data exchange between TAPI applications (in the general domain)




A31003-H3580-Y100-10-7618, 01-2011


3000sb6.fm


TSP (TAPI Extended Services) Features

● Central recording of call charges

● Support of ACD proxy request handler

● Telephone Data Service (TDS)

● Heartbeat/loopback

● AMHOST

6.1.9 System Connection Hardware

TAPI 170 for HiPath 3000/5000 or in the HiPath Network

The CTI components are usually connected to one another or to the system(s) via TCP/IP.

TAPI 170 as a Standalone Solution

Alternatively, the TSP/CMD components can be connected to one another or to the system asfollows:

● via the DIVA Pro 2.0. ISDN card supplied

● via a V24 interface with a null modem cable (part number: C39195-Z7267-C13); in orderto achieve the best performance possible, the baud rate used can be increased to 19200bauds.

● via TCP/IP (recommended default).



3000sb6.fm

A31003-H3580-Y100-10-7618, 01-2011




6.1.10 Installation Medium and Order of Installation

Depending on the TAPI 170 system variant, the following applies:

Installation of TAPI 170 for HiPath 3000/5000 or HiPath 5000

The installation files for TAPI 170 are included in the installation media for HiPath 5000 orHiPath 3000/5000 software installation.

The order in which the components are installed is automatically selected by the installationprogram. The components to be installed can be specified during installation. After installingthe components, the necessary parameters may be individually configured before carrying outfurther installations. However, the components can also be configured at a later time.

Installation of TAPI 170 (Standalone)

An installation CD entitled "HiPath TAPI 170 V2.0" is provided. Since the installation comprisescomponents from various manufacturers, it is essential that the installation is performed in thefollowing order.

Order of Installation

1. Component installation

2. Component configuration




A31003-H3580-Y100-10-7618, 01-2011


3000sb6.fm

CSPL Interface for Gadget Servers

6.2 CSPL Interface for Gadget Servers

The CSPL interface is a simple application interface for HiPath 3000 V8 or later (CSPL: CSPLight -> CSP: CSTA Service Provider -> CSTA: Computer Supported Telecommunications Ap-

plications). The interface can be operated without a license.

Main function

A gadget server (G server from gebeCom) can be connected to HiPath 3000 via the CSPL in-terface. A gadget server provides various applications such as CTI applications that use thecommunication functions of HiPath 3000.

HiPath 3000 communicates overs the "CSTA III ASN.1" protocol, the gadget server over CSTA-XML. The CSPL interface switches between the two protocols. The following figure illustrateshow this works:

Hardware and software requirements

The CSPL interface runs as a Windows service on a separate server (i386-CPU, 32 bit) oper-ating on the following operating systems:

● Microsoft Windows 2000 Server

● Microsoft Windows 2003 Server

● Microsoft Windows XP Professional

● Microsoft Windows Vista (Business Edition)

CSPL interface

HiPath 3000

Gadget server

SAP

Browser for CTISecurity/video

Actuator/sensor

SMS/IM

CSTA-XML

CSTA III ASN.1



3000sb6.fm

A31003-H3580-Y100-10-7618, 01-2011



CSPL Interface for Gadget Servers

Capacity planning

Only one application per CSPL interface can be connected via CSTA-XML. The CSPL interfacemust be installed on a separate PC for each application. This principle is illustrated in the fol-

lowing figure:

Each CSPL interface uses one of the eight CSTA interfaces associated with HiPath 3000.HiPath 3000 can monitor up to four devices simultaneously. If simultaneous device monitoringis not being performed, up to six devices can be connected. The other two CSTA interfaces arenormally used for HiPath TAPI 170.

CSPL 1

HiPath 3000

Gadgetserver 1

C S T A - X M L

C S T A I I I AS N .1

CSPL 2

Gadgetserver 2

C S T A - X M L

CSPL 3

Gadgetserver 3

C S T A - X M L

CSPL 4

Gadgetserver 4

C S T A - X M L

C S TA I I I A S N. 1

C S T A

I I I A S N. 1

C S T A I I I A S N .1







Access Points Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb55.fm

HiPath AP 1120 SIP

7.2 HiPath AP 1120 SIP

AP1120 SIP is an IP-to-analog adapter for fax/modem. It is used when a fax is required at alocation that only has an IP connection.

AP 1120 SIP features two analog interfaces and is supplied with the Cornet IP softwareHiPath 4000, as well as H323 or SIP software for HiPath 3000/5000, HiPath 4000 andOpenScape Voice.



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Workpoints

8 Workpoints

The following table provides an overview of workpoints. Refer to the service manual, however,

for binding data.

Workpoint Chapter/Section

OpenStage Product Family (HiPath 3000/5000 V7 R3 and Higher) Section 8.1

OpenStage 10 Section 8.1.2.1




OpenStage 40 Section 8.1.2.5OpenStage 60 Section 8.1.2.6


OpenScape Personal Edition Section 8.2

Add-on Devices for OpenStage Telephones Section 8.1.3

OpenStage Key Module 15 Section 8.1.3.1

OpenStage Key Module 40, 60, 80 Section 8.1.3.2

OpenStage BLF Section 8.1.3.3

optiPoint 410 and optiPoint 420 Product Family Section 8.3optiPoint 410 and optiPoint 410 S Telephones Section 8.3.1

optiPoint 410 entry, optiPoint 410 entry S Section 8.3.1.1

optiPoint 410 economy, optiPoint 410 economy S Section 8.3.1.2

optiPoint 410 economy plus, optiPoint 410 economy plus S Section 8.3.1.3

optiPoint 410 standard, optiPoint 410 standard S Section 8.3.1.4

optiPoint 410 advance, optiPoint 410 advance S Section 8.3.1.5

optiPoint 420 and optiPoint 420 S Telephones Section 8.3.2

optiPoint 420 economy, optiPoint 420 economy S Section 8.3.2.1

optiPoint 420 economy plus, optiPoint 420 economy plus S Section 8.3.2.2

optiPoint 420 standard, optiPoint 420 standard S Section 8.3.2.3

optiPoint 420 advance, optiPoint 420 advance S Section 8.3.2.4

optiPoint 410 and optiPoint 420 Add-On Devices Section 8.3.3

optiPoint self labeling key module Section 8.3.3.1

optiPoint 410 display module Section 8.3.3.2



Workpoints Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

optiPoint 600 office Section 8.4

optiPoint 500 Product Family Section 8.5

optiPoint 500 Telephones without Display Section 8.5.1

optiPoint 500 Telephones with Display Section 8.5.2

optiPoint 500 Add-On Devices Section 8.5.4

optiPoint key module Section 8.5.4.1

optiPoint BLF Section 8.5.4.2

optiPoint application module (V5.0 SMR-06 or later) Section 8.5.4.3

optiPoint 600 office Section 8.7

Product Image Section 8.7.1optiPoint WL2 professional/optiPoint WL2 professional S Section 8.8

Gigaset SL3 professional Section 8.9.1

Gigaset S4 professional Section 8.9.2

Gigaset M2 professional Section 8.9.3

optiPoint WL2 professional/optiPoint WL2 professional S Section 8.8

Attendant Consoles Section 8.10

HiPath Attendant B Braille Console Section 8.10.1

optiClient Attendant V8 Section 8.10.2optiPoint Attendant Section 8.10.3

Workpoint Chapter/Section



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



OpenStage Product Family (HiPath 3000/5000 V7 R3 and Higher)

8.1 OpenStage Product Family (HiPath 3000/5000 V7 R3 and Higher)

Connection variants

The following connection variants are available for the terminals with HiPath 3000/5000:

● TDM connection

● CorNet IP connection (also as Gigabit variant, page 8-4)

Product family

The following terminals belong to the OpenStage product family for HiPath 3000/5000:

● OpenStage TDM: 10 T, 15 T, 20 T, 30 T, 40 T, 60 T, 80 T

● OpenStage CorNet IP (HFA): 15, 20 E, 20, 20 G, 40, 40 G, 60, 60 G and 80, 80 G

Control elements

The following elements and the display guarantee convenient and interactive operation.

● 3-way navigator: in OpenStage 20.

●

Programmable keys: in OpenStage 30. The function is displayed to the left of the keys ona paper label.

● Programmable touch/sensor keys next to the display (illuminated) and a 5-way navigator:in OpenStage 40. The function is displayed to the left of the keys on the display.

● Programmable touch/sensor keys next to the display (illuminated) and a TouchGuide: inOpenStage 60, OpenStage 80. The function is displayed to the left of the keys on the dis-play.

Programmable keys can be used as function keys, speed dialing keys or trunk keys.

The number of available programmable keys can be increased by adding:

● OpenStage Key Module 15: in OpenStage 15, OpenStage 30

● OpenStage Key Module: in OpenStage 40, OpenStage 60, OpenStage 80

● OpenStage BLF: in OpenStage 30, OpenStage 40

>Important: The SIP connection variant is not supported by HiPath 3000/5000.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.1.1 Gigabit Variant of OpenStage Terminals

The connection variant CorNet IP is also available in a Gigabit variant.

These OpenStage terminals feature an integrated Ethernet switch which can be used, for in-stance, to connect the workstation PC to the local network. In the gigabit version, larger datapackets (such as, video or audio data packets) can be transferred to the workstation PC that isconnected to the network via the OpenStage terminal. This enables costs to be saved in thearea of inhouse cabling and the IP network and at the same time allows the performance of thenetwork to be increased.

To enable the Gigabit Ethernet switch to be usefully employed, it is vital for the entire corporatenetwork to support Gigabit technology. CAT 5M, or even better CAT 6 network cables are es-sential for connecting the terminals. Older types of cable may under some circumstances causesignificant speed losses.

The OpenStage terminals in the gigabit version are:

● OpenStage 20 G

● OpenStage 40 G

● OpenStage 60 G

● OpenStage 80 G










A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Downward compatibility to earlier systems

OpenStage 15 T can be registered as an optiPoint 500 standard on earlier HiPath communica-tion systems (in other words, on HiPath 3000 V7 systems). OpenStage 15 T can be switched

to optiPoint mode via a simple menu. In HiPath 3000 Manager E, an optiPoint 500 standard isvisible instead of an OpenStage 15 T.

Navigation keys Three keys for:● scrolling forward through the menu or opening the idle menu

● executing actions● scrolling back through the menu or opening the idle menu

Programmable keys ● 8 keys● Each key can be programmed either as a function key or as a

DSS key

Key module "OpenStage Key Module 15":● 18 programmable keys● Each key can be programmed either as a function key or as a

DSS key● A maximum of one "OpenStage Key Module 15" can be connect-

ed to the telephone

Port UP0E

Additional features ● Full duplex speakerphone mode● Open listening● Optional wall mounting

Feature Description



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.1.2.3 OpenStage 20

Product image

Versions

HiPath 3000/5000 V7 R3 and higher supports the CorNet-IP (HFA) and TDM connection vari-ants (OpenStage 20 T). The following telephones are available for the CorNet IP (HFA) connec-tion variant:

● OpenStage 20 E (without full-duplex speakerphone mode)

● OpenStage 20

● OpenStage 20 G (gigabit variant)

Main Features

Figure 8-3 OpenStage 20

Feature Connection variant

CorNet IP (HFA) TDM

General fea-tures

LCD swivel graphics display, resolution 24 X 2 characters, monochrome

Multifunctional 3-way navigator




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


General fea-tures

7 pre-programmed function keys: disconnect, call forwarding, redial, service/ application menu, voicemail messages, loudspeaker, mute

Full-duplex speakerphone mode (not for 20 E)

Open listening

Optional wall mounting

Interfaces Integrated Ethernet switch for con-necting to a PC

LAN port (10/100 Base-T)

IP features CorNet IP (HFA) based on H.323

Security and Encryption for H-SeriesMultimedia Terminals H.235 Annex D

Voice codecs (G.711, G.729, G.722)

DHCP, FTP, HTTP, HTTPS, SNMP

Port Based Network Access Control802.1x

QoS according to DiffServ

VLAN

IEEE 802.3af Power over Ethernet(PoE)


CorNet IP (HFA) TDM



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011





Product image

Versions

HiPath 3000/5000 V8 R4 and higher supports the TDM connection variant (OpenStage 30 T).

Main Features


Feature Description

Display LCD, immobile, two lines, monochrome, 24 x 2 characters

Pre-programmed func-tion keys, first row

● End call (disconnect)● Number redial● Switch call forwarding on/off● Switch headset on/off● Switch microphone on/off




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Downward compatibility to earlier systems

OpenStage 30 T can be registered as an optiPoint 500 advance on earlier HiPath communica-tion systems (in other words, on HiPath 3000 V7 systems). OpenStage 30 T can be switchedto optiPoint mode via a simple menu. In HiPath 3000 Manager E, an optiPoint 500 advance isvisible instead of an OpenStage 30 T.

Pre-programmed func-tion keys, second row

● Three audio keys for: – decreasing the volume and brightening the display contrast

– activating/deactivating the loudspeaker – increasing the volume and darkening the display contrast

● Mailbox key for checking voice mail● Menu key for the communication system’s Service menu

Dialing keypad For entering digits 0 to 9, pound and asterisk symbols, letters, punc-tuation marks and special characters

Navigation keys Three keys for:● scrolling forward through the menu or opening the idle menu● executing actions● scrolling back through the menu or opening the idle menu

Programmable keys 8 keys:● Each key can be programmed either as a function key or as a

DSS key● Labeled with paper label

Key modules 1 "OpenStage Key Module 15":● 18 programmable keys● Each key can be programmed either as a function key or as a

DSS key● A maximum of one "OpenStage Key Module 15" can be connect-

ed to the telephone

Or: 1 "OpenStage BLF" busy lamp field

Connections ● UP0E (CorNet-TS protocol)● USB-B (slave interface) for first-party CTI● 121TR9-5* for headset, 8 pins

Additional features ● Full duplex speakerphone mode● Open listening● Wall mounting● Software download via SLMO● Downward compatibility to earlier systems

Feature Description



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011





Product image

Versions

HiPath 3000/5000 V7 R3 and higher supports the CorNet-IP (HFA) and TDM connection vari-ants (OpenStage 40 T). The following telephones are available for the CorNet IP (HFA) connec-tion variant:

● OpenStage40


Main Features



CorNet IP (HFA) TDM

General fea-tures

LCD swivel graphics display with background lighting, resolution 40 X 6 char-acters, monochrome

Multifunctional 5-way navigator




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


General fea-tures

8 pre-programmed function keys: disconnect, call forwarding, redial, service/ application menu, voicemail messages, loudspeaker,

mute, headset

6 programmable touch/sensor keys: function, speed dialing or trunk keys

Full duplex speakerphone mode

Open listening

Optional wall mounting

Interfaces Integrated Ethernet switch for con-necting to a PC

USB slave

LAN port (10/100 Base-T)Port for headset

Port for key module and BLF

IP features CorNet IP (HFA) based on H.323

Security and Encryption for H-SeriesMultimedia Terminals H.235 Annex D

Voice codecs (G.711, G.729, G.722)

DHCP, FTP, HTTP, HTTPS, SNMP

Port Based Network Access Control802.1x

QoS according to DiffServ

VLAN

IEEE 802.3af Power over Ethernet(PoE)


CorNet IP (HFA) TDM



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011





Product image

Versions

OpenStage 60 is supported in the CorNet-IP (HFA) connection variant by HiPath 3000/5000 V7 R3and higher and in the TDM connection variant (OpenStage 60 T) by HiPath 3000/5000 V7 R4 andhigher. The following telephones are available for the CorNet IP (HFA) connection variant:

● OpenStage 60


Main Features


Feature Description

Display TFT, swivel, background lighting, 320 x 240 pixels, QVGA, 16 bit colordepth, suitable for graphics

Pre-programmed func-tion keys, left

● End call (disconnect)● Switch call forwarding on/off● Switch voice dialing on/off




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Pre-programmed func-tion keys, right

● Activating/deactivating the loudspeaker● Switch headset on/off

● Switch microphone on/offMode keys ● Display telephony interface

(forexample, connection status, connection duration)● Display phonebooks:

– Personal phonebook – LDAP directory – HiPath 3000 phonebook

● Display call lists: – Dialed numbers (internal phone redial) – Missed calls

– Received calls● Display messages:

– Text messages – Voice mail

● Menu key: – Service menu – User menu – Administration menu – Applications tab

● Display Help function

TouchSlider Set the current volume● Ringtone● Handset● Loudspeaker

TouchGuide Navigate in lists, menus and input fields


Programmable sensorkeys

Eight keys:● Each key can be programmed as a function, DSS or trunk key. If

programmed for redial, the key accesses the HiPath 3000 redial

function.● Key labeling on the display

Key modules 2 "OpenStage Key Module 60/80" modules:● 12 programmable keys● Each key can be programmed as a function, DSS or trunk key● Up to two "OpenStage Key Module 60/80" can be connected to

the telephone

Feature Description



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




Connections ● USB-A (master interface) for first-party CTI● 121TR9-5* for headset, 8 pins

● Bluetooth● Connection for key module● For TDM only: USB-B (slave interface) for first-party CTI● For CorNet-IP (HFA) only: LAN port (10/100 Base-T)● For CorNet-IP (HFA) only: Integrated Ethernet switch for connect-

ing to a PC

Additional features ● Full duplex speakerphone mode● Open listening● Voice dialing● Polyphonic and mp3 ring tones supported

● No wall mountingIP features [forCorNet-IP (HFA) only]

● CorNet-IP (HFA) based on H.323● Security and Encryption for H-Series Multimedia Terminals H.235

Annex D● Voice codecs (G.711, G.729, G.722)● DHCP, FTP, HTTP, HTTPS, SNMP● Port Based Network Access Control 802.1x● QoS according to DiffServ● VLAN● IEEE 802.3af Power over Ethernet (PoE)

Feature Description




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm



Product image

Versions

OpenStage 80 is supported in the CorNet-IP (HFA) connection variant by HiPath 3000/5000 V7R3 and higher and in the TDM connection variant (OpenStage 80 T) by HiPath 3000/5000 V7R4 and higher. The following telephones are available for the CorNet IP (HFA) connection vari-ant:

● OpenStage 80


Main Features

Figure 8-7 OpenStage 80 [CorNet-IP (HFA)]

Feature Description

Display TFT, swivel, background lighting● TDM: 320 x 240 pixels, QVGA, 16 bit color depth, suitable for

graphics● CorNet-IP (HFA): 640 x 480 pixels, VGA, 16 bit color depth, suit-

able for graphics



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




Pre-programmed func-tion keys, left

● End call (disconnect)● Switch call forwarding on/off

● Switch voice dialing on/offPre-programmed func-tion keys, right

● Activating/deactivating the loudspeaker● Switch headset on/off● Switch microphone on/off

Mode keys ● Display telephony interface(forexample, connection status, connection duration)

● Display phonebooks: – Personal phonebook – LDAP directory – HiPath 3000 phonebook

● Display call lists: – Dialed numbers (internal phone redial) – Missed calls – Received calls

● Display messages: – Text messages – Voice mail

● Menu key: – Service menu – User menu – Administration menu – Applications tab

● Display Help function

TouchSlider Set the current volume● Ringtone● Handset● Loudspeaker

TouchGuide Navigate in lists, menus and input fields


Programmable sensorkeys

TDM: Eight keys / CorNet-IP (HFA): Nine keys● Each key can be programmed as a function, DSS or trunk key. If

programmed for redial, the key accesses the HiPath 3000 redialfunction.

● Key labeling on the display

Feature Description




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Key modules 2 "OpenStage Key Module 60/80" modules:● 12 programmable keys

● Each key can be programmed as a function, DSS or trunk key● Up to two "OpenStage Key Module 60/80" can be connected to

the telephone

Connections ● USB-A (master interface) for first-party CTI● 121TR9-5* for headset, 8 pins● Bluetooth● Connection for key module● For TDM only: USB-B (slave interface) for first-party CTI● For CorNet-IP (HFA) only: LAN port (10/100 Base-T)● For CorNet-IP (HFA) only: Integrated Ethernet switch for connect-

ing to a PCAdditional features ● Full duplex speakerphone mode

● Open listening● Voice dialing● Polyphonic and mp3 ring tones supported● No wall mounting

IP features [forCorNet-IP (HFA) only]

● CorNet-IP (HFA) based on H.323● Security and Encryption for H-Series Multimedia Terminals H.235

Annex D● Voice codecs (G.711, G.729, G.722)

● DHCP, FTP, HTTP, HTTPS, SNMP● Port Based Network Access Control 802.1x● QoS according to DiffServ● VLAN● IEEE 802.3af Power over Ethernet (PoE)

Feature Description



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.1.2.8 Ports on the Underside of the Telephone for the CorNet IP Model

This section shows the ports on the underside of OpenStage CorNet IP (HFA) telephones.These ports are explained in section 8.1.2.10, “OpenStage Terminals – Description of Ports”.

OpenStage 15 for CorNet IP

Figure 8-8 OpenStage 15 (CorNet IP) – Underside of the Telephone




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


OpenStage 20, OpenStage 40 for CorNet IP

Figure 8-9 OpenStage 20, OpenStage 40 (CorNet IP) – Underside of the Telephone

OpenStage 60, OpenStage 80 for CorNet IP

Figure 8-10 OpenStage 60, OpenStage 80 (CorNet IP) – Underside of the Telephone

*) *)

*) not available in OpenStage 20



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.1.2.9 Ports on the Underside of the Telephone for the TDM Model

This section shows the ports on the underside of OpenStage TDM telephones. These ports areexplained in section 8.1.2.10, “OpenStage Terminals – Description of Ports”.

OpenStage 10 T, OpenStage 20 T

Figure 8-11 OpenStage 10 T, OpenStage 20 T – Underside of the Telephone

OpenStage 15 T

Figure 8-12 OpenStage 15 T – Underside of the Telephone




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm








3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.1.2.10 OpenStage Terminals – Description of Ports

Port Explanation Telephones

CorNet-IP connection variantsConnection for key module

OpenStage 20OpenStage 40OpenStage 60OpenStage 80

TDM connection variantsConnection for key module

OpenStage 15 TOpenStage 30 TOpenStage 40 TOpenStage 60 TOpenStage 80 T

CorNet-IP connection variantsConnection for an external local power supply.

OpenStage 15OpenStage 20OpenStage 40OpenStage 60OpenStage 80

TDM connection variants● Ext. power supply not required:

connection to HiPath 3000● Ext. power supply required: connection to an external

local power supply.● connection to OpenStage PhoneAdapter.

OpenStage 10 TOpenStage 15 TOpenStage 20 TOpenStage 30 TOpenStage 40 TOpenStage 60 T

OpenStage 80 T

CorNet-IP connection variantsFirst USB port; not used.

OpenStage 60OpenStage 80

TDM connection variantsFirst USB port, e.g. for first-party CTI

OpenStage 30 TOpenStage 40 TOpenStage 60 TOpenStage 80 T

CorNet-IP connection variantsSecond USB port, e.g. for USB memory stick


TDM connection variantsSecond USB port, e.g. for USB memory stick

OpenStage 60 TOpenStage 80 T

Table 8-1 OpenStage Terminals – Description of Ports




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


CorNet-IP connection variantsPort for PC, e.g. for OpenStage Manager


OpenStage 40OpenStage 60OpenStage 80

TDM connection variants – –

CorNet-IP connection variantsLAN connection


TDM connection variants – –

CorNet-IP connection variantsPort for headset

OpenStage 40OpenStage 60OpenStage 80

TDM connection variantsPort for headset

OpenStage 30 TOpenStage 40 TOpenStage 60 TOpenStage 80 T

CorNet-IP connection variantsHeadset port


TDM connection variantsHeadset port

OpenStage 10 TOpenStage 15 TOpenStage 20 TOpenStage 30 TOpenStage 40 T

OpenStage 60 TOpenStage 80 T

Port Explanation Telephones

Table 8-1 OpenStage Terminals – Description of Ports






A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.1.3.2 OpenStage Key Module 40, 60, 80

The "OpenStage Key Module" can be connected to the telephones OpenStage 40,OpenStage 60, and OpenStage 80. Up to two key modules can be connected.

Figure 8-16 OpenStage Key Module

The OpenStage Key Module is an add-on device that should be mounted on the side of thetelephone; it provides an additional 12 programmable function keys. In conjunction with the in-tegrated level function there is the option of using a total of 22 call numbers or chosen key func-tions. Keys are labeled automatically on the display.

8.1.3.3 OpenStage BLF

The OpenStage BLF can be connected to OpenStage 30 and OpenStage 40 telephones. OneOpenStage BLF can be connected. It cannot be combined with the OpenStage Key Module.

Figure 8-17 OpenStage BLF

The OpenStage BLF (busy lamp field) is an add-on device that should be mounted on the sideof the telephone; it provides an additional 90 programmable function keys.

To guarantee a sufficient power supply and external ac power supply unit is necessary to op-erate the BLF. Only the local power supply originally supplied must be used for this purpose,see section 8.1.4.1, “External Local Power Supply”. The AC adapter port depends on theOpenStage BLF hardware output.



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.1.3.4 Possible Configurations for the Add-On Devices

The following table shows the permitted configurations of key modules at OpenStage terminalsfor TDM and CorNet-IP connection variants. For telephones which do not appear in the table

no application of key modules is possible.

Table 8-2 OpenStage Terminals - Add-on Device Configurations

Telephone 1st add-on device 2nd add-on device

OpenStage 15 OpenStage Key Module 15 –

OpenStage 30 OpenStage Key Module 15 –

OpenStage BLF –

OpenStage40 40 OpenStage Key Module 40 OpenStage Key Module 40

OpenStage BLF –






A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.1.4 OpenStage Accessories

8.1.4.1 External Local Power Supply

An external local power supply is required with specific configurations.

The power supply unit features two MW6 jacks.

For external power supply of an OpenStage BLF, the AC adapter port depends on the Open-Stage BLF hardware output:

● OpenStage BLF, hardware output S30817-S7406-A101-7/-A103-2 and earlier:The external power supply is connected directly to the OpenStage BLF. To do this, connectthe left jack, labeled "Digital" on the AC adapter (figure 8-19 for TDM connection variants)to the BLF.

● OpenStage BLF, hardware output S30817-S7406-A101-8/-A103-3 and later:

The OpenStage BLF is powered by the associated terminal. The power supply unit(figure 8-18 for CorNet-IP connection variant) should be connected to the terminal.

7CautionThe AC adapter used to supply power to an OpenStage BLF must only be used forthis purpose. Using the free jack of the power supply unit to power another terminalor device is not permitted and can lead to the destruction of the OpenStage BLF.



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




OpenStage terminals with the CorNet-IP connection variant

OpenStage terminals with TDM connection variant

Figure 8-18 OpenStage terminals (CorNet-IP Connection Variant) – Connection of the Ex-ternal Power Supply Unit

Figure 8-19 OpenStage terminals (TDM Connection Variant) – Connection of the ExternalPower Supply Unit

to the OpenStageworkpoint Connectorsocket

to the OpenStage workpoint

Connector socket

To systemHiPath 3000




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Variants

● Euro local power supply C39280-Z4-C510

● UK local power supply C39280-Z4-C512

● 110 V U.S local power supply C39280-Z4-C511


8.1.4.2 OpenStage PhoneAdapter

The OpenStage PhoneAdapter is used to connect a second OpenStage (TDM) terminal (UP0/E or analog connection) with its own power supply.

Technical Specifications Local power sup-ply, Euro

C39280-Z4-C510

Local power sup-ply, UK

C39280-Z4-C512

Local power sup-ply 110 V U.S.

C39280-Z4-C511

Line voltage 230 Vac 230 Vac 120 VAC

AC line frequency 50 Hz 50 Hz 60 Hz

Output voltage max. 43 VDC,min. 30 VDC

max. 43 VDC,min. 30 VDC


Output current 480 mA 480 mA 480 mA

Figure 8-20 OpenStage PhoneAdapter



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




The system treats the OpenStage telephone as an independent telephone with a separatephone number and its own B channel. The OpenStage telephone can send and receive callsregardless of the connection status of the host telephone.

8.1.4.3 Headset

Thanks to integrated Bluetooth technology convenient headsets can be used.

The OpenStage 40/60/80 terminals are each equipped with a jack to connect corded (121 TR9-5) and cordless headsets (121 TR 9-5).

Note: The headset ports for OpenStage terminals are coded RJ45 jacks. The headsets haveRJ11 or RJ45 connectors. If contact problems occur (RJ45 jack <–> RJ11 connector), replacethe RJ11 connector of the affected headset with an RJ45 connector. You can order a codedRJ45 connector using the part number C39334-Z93-C350 (commercial RJ45-ISDN connectorsare not suitable).

Figure 8-21 Headsets




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

OpenScape Personal Edition

8.2 OpenScape Personal Edition

Overview

OpenScape Personal Edition is an IP softphone for installation on laptops and desktop PCs. Itis released without server components. The product is the successor to OpenScape optiClient130/130 S.

OpenScape Personal Edition is available in HFA and SIP versions.

The product has a modular software structure, meaning that functionality can be increased inincrements. The user interface has the same look and feel as the Windows ® Office 2007 inter-face.

Features

● Softphone

● Call control

● HFA or SIP

● CTI

● Groupware and directory access

● Contact management

● Call journal

● Video (in SIP version)

● Desktop client for Windows-based clients

Differences between the HFA and SIP versions

The HFA version can work with HiPath 4000. The SIP variant works with HiPath 3000 andOpenScape Voice and also supports video function.

The HFA version supports all features of the HFA protocol. The SIP variant supports all re-leased SIP features (see sales information).

Prerequisites for the PC

● Operating systems

– Windows XP (SP 2 or later)

– Windows Vista (32-bit)



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



OpenScape Personal Edition

● RAM space

You will need:

– At least 1 GB RAM for Windows XP

– At least 1.5 GB RAM for Windows Vista

– 256 MB RAM for OpenScape Personal Edition

A total of 2 GB RAM is required.

● Processor with a clock frequency of at least 1 GHz

● At least 200 MB free space on the hard disk

● CD-ROM drive

● Ethernet network card with IEEE 802.1p/q support for optimum Quality of Service (QoS)

● USB support for connecting a handset or headset

Available languages

● German

● English

● Chinese (simplified), only in the corresponding operating system

Video camerasA commercial USB camera is suitable for the video function. The system was tested with Log-itech cameras.

A minimum of 1.3 megapixels resolution is required.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

optiPoint 410 and optiPoint 420 Product Family

8.3 optiPoint 410 and optiPoint 420 Product Family

Introduction

The IP telephones in the optiPoint 410/optiPoint 410 S and optiPoint 420/optiPoint 420 S fam-ilies allow users to conduct telephone calls in the simple, familiar way over a data network.

The three dialog keys and the display guarantee convenient and interactive operation (not avail-able for optiPoint 410 entry and optiPoint 410 entry S). Furthermore, the key lamp principle vi-sualizes the activated functions.

The difference between the optiPoint 410/optiPoint 410 S and optiPoint 420/optiPoint 420 Sfamilies lies in the design of the function key panels:

● optiPoint 410/optiPoint 410 S families: the function keys have panels with labeling strips onwhich the function or currently saved phone number can be entered.

● optiPoint 420/optiPoint 420 S families: The function keys are self-labeling keys. Self-label-ing means that each key is assigned a display (one line with 12 characters) in which thefunction or call number currently saved is shown.

You can use the optiPoint self-labeling key module add-on device to increase the number ofavailable function keys for the standard and advance telephones. The optiPoint key module andoptiPoint BLF can also be used together with the optiPoint 410/optiPoint 410 S and optiPoint420/optiPoint 420 S families.

The optiPoint 410 display is used as the key module on the standard and advance telephonetypes. Its graphical LCD display (320 x 240 dots), the touchscreen and the navigation keysmean that many functions can be used intuitively and therefore more effectively.

The use of different optiPoint 500 adapters guarantees flexibility for the expansion of the tele-phone workstation (not for the entry, economy and economy plus telephones).

Differences between the optiPoint 410/optiPoint 420 and optiPoint 410 S/optiPoint 420 S fami-lies:

● optiPoint 410/optiPoint 420 families: All HiPath 3000/5000 features that are offered in thedisplay dialog, in the service menu, and on function keys are available (except for Relo-cate).

● optiPoint 410 S/optiPoint 420 S families: The associated telephones support the SIP (Ses-sion Initiation Protocol). The SIP (Session Initiation Protocol) protocol is an ASCII-basedsignaling protocol used to configure sessions in an IP network.Note: The term "Internet telephony" as used in this document refers to making telephonecalls via IP-supported networks (Voice over IP) and signaling via SIP.



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




Note: The term "Internet telephony" as used in this document refers to making telephone callsvia IP-supported networks (Voice over IP) and signaling via SIP.

The following features for Internet telephony stations are actively supported:

– CLIP (Calling Line Identification Presentation)

– CLIR (Calling Line Identification Restriction)

– COLP (Connected Line Identification Presentation)

– COLR (Connected Line Identification Restriction)

– Consultation hold

– Call hold

– Toggle

– Transfer (Screened transfer)

– DISA (Direct Inward System Access): Features cannot be activated for the SIP tele-phone.

– Inband DTMF

Although Internet telephony stations may not activate the following features, they may bepassively involved:

– Call forwarding (forwarding to an Internet telephony station is supported)

– Conference (Internet telephony stations may be passively involved)

– Park (Internet telephony stations may be parked; from the perspective of the Internettelephony station, this is similar to "Call hold")

– Live Call Recording (Internet telephony stations may be passively involved)

– Whisper (Internet telephony stations may be passively involved)

– Automatic COS changeover (Internet telephony stations support automatic COSchangeover)

– Internal traffic restriction groups (Internet telephony stations can be entered in ITRgroups)

The following restrictions apply to Internet telephony stations:

– Internet telephony stations are configured on HiPath 3000/5000 V8 as DSS1 (function-al telephones) and therefore cannot be supervised by the system (no monitoring). In-ternet telephony stations cannot use applications that require monitoring (for example,HiPath ComAssistant).





3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.1 optiPoint 410 and optiPoint 410 S Telephones

8.3.1.1 optiPoint 410 entry, optiPoint 410 entry S

Main Features

● Protocols

– H.323, HFA/V3 + V4, CorNet IP, SIP

– HTTP, DHCP, SNMP, FTP

– H.235 (security)

– QoS to DIFFSERV and IEEE 802.1 p/Q

● Voice compression G.711, G.722, G.723 and G.729 A/B

● Power over LAN (in accordance with Cisco and standard pre802.3af)

● CTI (for example, via TAPI 3rd party)

● 1 Ethernet (10/100BaseT) interface (self-configuring) for LAN connection

● 8 function keys with LED

● 2 setting keys (plus/minus) for volume and pitch

● Suitable for wall mounting

● No modularity (no connecting capability for adapters or add-on devices), no display




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 410 entry, optiPoint 410 entry S

Figure 8-22 optiPoint 410 entry, 410 entry S - standard key assignment

optiPoint 410 entryConsultation hold

Number redial

Message

Callback

Speed dialing

Microphone on/off

Loudspeaker

Disconnect

optiPoint 410 entry S

Programmable

Programmable

Programmable

Programmable

Programmable

Programmable

Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.1.2 optiPoint 410 economy, optiPoint 410 economy S

Main Features

● Protocols







● CTI (for example, via TAPI 3rd party)



● Alphanumeric LCD swivel display with 2 lines, 24 characters each

● Three dialog keys for interactive prompting “Yes”, “Back”, and “Next”

● Open listening

● 2 setting keys (plus/minus) for volume, pitch and display contrast


● No modularity (no connecting capability for adapters or add-on devices




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 410 economy, optiPoint 410 economy S

Figure 8-23 optiPoint 410 economy, 410 economy S - standard key assignment

optiPoint 410 economyService Programmable

Number redial Programmable

Microphone on/off Programmable

Loudspeaker Programmable

Programmable

Programmable

Programmable

Disconnect

optiPoint 410 economy S



Caller list Programmable

Programmable Programmable

Programmable

Programmable

Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.1.3 optiPoint 410 economy plus, optiPoint 410 economy plus S

Main Features

● Protocols







● CTI (for example, via TAPI 1st Party)


● 1 Ethernet (10/100BaseT) interface (self-configuring) for the PC connection




● Open listening

● Port for headset (121 TR 9-5)







A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 410 economy plus,optiPoint 410 economy plus S

Figure 8-24 optiPoint 410 economy plus, 410 economy plus S - standard key assignment

optiPoint 410 economy plus

Service Programmable




Programmable

Programmable

Programmable

Disconnect

optiPoint 410 economy plus SLoudspeaker Programmable




Programmable

Programmable

Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.1.4 optiPoint 410 standard, optiPoint 410 standard S

Main Features

● Protocols













● Full duplex speakerphone mode with echo suppression for adapting to the room


● 2 setting keys (plus/minus) for volume, pitch, speaker quality and display contrast

● Modularity:

– 2 adapter slots (option bays)

– 1 interface for max. 2 add-on devices





A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 410 standard, optiPoint 410 standard S

Figure 8-25 optiPoint 410 standard, 410 standard S - standard key assignment

optiPoint 410 standardService Programmable




Programmable

Programmable

Programmable

Disconnect

optiPoint 410 standard S





Programmable

Programmable

Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.1.5 optiPoint 410 advance, optiPoint 410 advance S

Main Features

● Protocols










● 1 integrated USB 1.1 interface


● Graphic display (swivel) with 4 lines, 24 characters each





● Modularity:

– 1 adapter slot (option bay)


●

Suitable for wall mounting




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 410 advance, optiPoint 410 advance S

Figure 8-26 optiPoint 410 advance, 410 advance S - standard key assignment

optiPoint 410 advance





Programmable

Programmable

Programmable

Programmable

Programmable

ProgrammableProgrammable

Programmable

Programmable

Programmable

Disconnect

optiPoint 410 advance S





Programmable

Programmable

Programmable

Programmable

Programmable

Programmable

Programmable

Programmable

Programmable

Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.2 optiPoint 420 and optiPoint 420 S Telephones

The IP telephones of the optiPoint 420 and optiPoint 420 S family have self-labeling keys. Self-labeling means that each key is assigned a display (one line with 12 characters) in which the

function or call number currently saved is shown.

8.3.2.1 optiPoint 420 economy, optiPoint 420 economy S

Main Features

● Protocols









● 12 function keys with LED and self-labeling keys



● Open listening







A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 420 economy, optiPoint 420 economy S

Figure 8-27 optiPoint 420 economy, 420 economy S - standard key assignment

optiPoint 420 economyService Programmable


Mailbox Programmable



Programmable

Disconnect

optiPoint 420 economy S






Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.2.2 optiPoint 420 economy plus, optiPoint 420 economy plus S

Main Features

● Protocols













● Open listening








A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 420 economy plus,optiPoint 420 economy plus S

Figure 8-28 optiPoint 420 economy plus, economy plus S - standard key assignment

optiPoint 420 economy plus






Programmable

Disconnect

optiPoint 420 economy plus S






Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.2.3 optiPoint 420 standard, optiPoint 420 standard S

Main Features

● Protocols
















● Modularity:

– 2 adapter slots (option bays)






A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 420 standard, optiPoint 420 standard S

Figure 8-29 optiPoint 420 standard, 420 standard S - standard key assignment

optiPoint 420 standardService Programmable





Programmable

Disconnect

optiPoint 420 standard S






Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.2.4 optiPoint 420 advance, optiPoint 420 advance S

Main Features

● Protocols










● 1 integrated USB 1.1 interface







● Modularity:



●

Suitable for wall mounting




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 420 advance, optiPoint 420 advance S

Figure 8-30 optiPoint 420 advance, 420 advance S - standard key assignment

optiPoint 420 advanceService Programmable





Programmable

Programmable

Programmable

Programmable


Programmable

Disconnect







Programmable

Programmable

Programmable

Programmable

Programmable

Programmable

Cancel

Level



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.3 optiPoint 410 and optiPoint 420 Add-On Devices

The user usually installs the add-on devices. The installation instructions are on the “ElectronicOperating Instructions” CD.

7Caution

Always disconnect the line cord before connecting add-on devices to the telephone.

>A maximum of two add-on device may be fitted to an optiPoint 410/optiPoint 410 Sor optiPoint 420/optiPoint 420 S telephone (not optiPoint 410 entry, optiPoint 410entry S, optiPoint 410 economy, optiPoint 410 economy S, optiPoint 410 economyplus, optiPoint 410 economy plus S, optiPoint 420 economy, optiPoint 420economy S, optiPoint 420 economy plus and optiPoint 420 economy plus S).In addition to the two ad-on device described below, optiPoint key module, optiPointBLF and optiPoint application module (V5.0 SMR-06 or later) can also be used.Table 8-3 shows the possible add-on device configurations.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.3.3.1 optiPoint self labeling key module

The optiPoint module with self-labeling keys is an add-on device that should be mounted on theside of the telephone; it provides an additional 13 keys, LEDs, and displays for all purposes. the

function keys are self-labeling keys. Self-labeling means that each key is assigned a display (1line with 12 characters) in which the function or currently saved phone number is shown.

The bottom key of the first key module installed on the telephone (optiPoint module with self-

labeling keys or optiPoint key module) is automatically defined as the “SHIFT key” (default). AShift key must not already be programmed.

Figure 8-31 optiPoint self labeling key module



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.3.3.2 optiPoint 410 display module

This is an add-on device with a graphic swivel display (240 x 320 pixels) with touchscreen func-tionality, background illumination, and navigation keys.

Main Features

● Graphical user interface

● Local personal telephone directory

● Access to company-wide telephone directory via LDAP

● WAP browser

● Voice-controlled dialing

● Call list containing all incoming and outgoing calls

● Speed-dialing list

● Online help

Port

The optiPoint 410 display module must always be connected as the first key module. In otherwords, it must be directly connected to the telephone.

The connection to the telephone is made over an interface cable with the following connectors:input MW6 (RJ11), output MW8 (RJ45). Power is supplied by the connected telephone.

Figure 8-32 optiPoint 410 display module




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm



The following table shows the possible configurations for add-on devices on telephones fromthe optiPoint 410/optiPoint 410 S and the optiPoint 420/optiPoint 420 S families. For telephones

which do not appear in the table no application of key modules is possible.

Table 8-3 Key module configurations on optiPoint 410/410 S and optiPoint 420/420 S

optiPoint 410/optiPoint 410 Stelephone

optiPoint 420/optiPoint 420 Stelephone

1st add-on device 2nd add-on device

optiPoint 410 standardoptiPoint 410 standard S

optiPoint 410 advanceoptiPoint 410 advance S

optiPoint 420 standardoptiPoint 420 standard S



optiPoint key module –

optiPoint key module optiPoint key module

optiPoint key module optiPoint BLFoptiPoint 410 display module –

optiPoint 410 display module optiPoint key module

optiPoint 410 display module optiPoint BLF

optiPoint 410 display module optiPoint self labeling keymodule

optiPoint BLF –

optiPoint BLF optiPoint BLF1

1 Configuration with two optiPoint BLFs only with HiPath 3800

optiPoint self labeling keymodule –

optiPoint self labeling keymodule

optiPoint self labeling keymodule

optiPoint 410 standard


optiPoint 420 standard


optiPoint application module –

optiPoint application module optiPoint key module

optiPoint application module optiPoint BLF

optiPoint application module optiPoint self labeling keymodule



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



optiPoint 600 office

8.4 optiPoint 600 office

With HiPath 3000/5000 from V7 the optiPoint 600 office can only be connected via the UP0/E port. It is no longer possible to connect it via the IP port.

Main Features


● Graphic LCD display (swivel) with 8 lines, each with 24 characters, touchscreen. backlight-ing, which remains on for around 5 s.



●

2 setting keys (plus/minus) for volume, pitch, speaker quality and display contrast● Interfaces and slots:

– 1 integrated USB 1.1 interface



– 1 headset port (121 TR9-5)


● Software download via PPP




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Standard key assignment (default) for optiPoint 600 office

Figure 8-33 optiPoint 600 office - standard key assignment (default)


Service ProgrammableNumber redial Programmable



Programmable

Programmable

Programmable

Programmable

Programmable

Programmable


Programmable

Programmable

Disconnect



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



optiPoint 500 Product Family

8.5 optiPoint 500 Product Family

optiPoint 500 telephones handle the digital communication of voice and data (voice communi-cation only for optiPoint 500 entry and optiPoint 500 economy). The three dialog keys and the

display guarantee convenient and interactive operation. Furthermore, the key lamp principle vi-sualizes the activated functions.

With the exception of optiPoint 500 entry and optiPoint 500 economy, the optiPoint 500 tele-phones have a USB 1.1 interface. This allows for PC-supported telephoning and Internet ac-cess over the USB interface of a PC.

The add-on devices optiPoint key module and optiPoint BLF allow you to increase the numberof available function keys.

The various optiPoint 500 adapters allow flexible extension of the telephone workstation. Addi-tional devices (such as personal computers, fax equipment, telephones, headsets) can be con-

nected quickly because it is easy to connect them to the underside of the telephones (notoptiPoint 500 entry and optiPoint 500 economy) and because the adapters are "plug’n’play".

The optiPoint 500 product family includes the following telephones:

Key Programming

Telephone (product name) Remark

optiPoint 500 entry Telephone without display

optiPoint 500 economy Telephone with display

optiPoint 500 basic Telephone with display

optiPoint 500 standard Telephone with displayoptiPoint 500 advance Telephone with display

>Double key assignmentThe programmable function keys of the optiPoint 500 telephones and the optiPointkey modules can have double assignments if only numbers without LED support aresaved on the first level. It is also possible to program numbers without LED supporton the second level. These can be internal station numbers, DID numbers and num-

bers from a HiPath network.When the Shift function is pressed, the LED lights the Shift key. This signals that thephone numbers on the second key level are available. The Shift function is deacti-vated after 5 s or after you press a phone number or if the you press the Shift keyagain.The optiPoint BLF function keys cannot have double assignments.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.5.1 optiPoint 500 Telephones without Display

optiPoint 500 entry

The optiPoint 500 entry telephone is an economical entry-level model for access to the digitaltechnology of the HiPath 3000/5000 system. It is designed for common areas and users whorequire minimal features. The optiPoint 500 entry model has:

● Eight preassigned function keys with LEDs (can be reprogrammed with HiPath 3000/5000Manager E)

● Open listening

● Two settings keys (plus/minus) for ringer volume, ringer pitch, alerting tone, open listening


● no modularity (no connecting capability for adapters or add-on devices), no display



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.5.2 optiPoint 500 Telephones with Display

The following telephones include alphanumeric displays and provide interactive promptingwhile a call is in progress. Interactive prompting means that you are offered only functions that

are relevant to the current call status. You can access these features using three optiGuide di-alog keys: OK, Next and Previous.

For clarity, the functions are arranged in submenus.

You can also select the features directly by using the service key to enter their codes.You can also assign functions or function loops (macros) to the specific function keys.

Invoke Conference? >

Peter Parker

Consultation? >

Invoke Transfer? >

Display

Select Display

Dialog keys

Scroll




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


optiPoint 500 economy (not for U.S.)

optiPoint 500 basic

The optiPoint 500 economy is an entry-level dis-play telephone. It has a comprehensive functionpackage, including the following features:● 12 function keys with LEDs (4 that can be

programmed with HiPath 3000/5000 Manag-er E, 8 freely programmable)

● Alphanumeric LCD swivel display with 2lines, 24 characters each

● Three dialog keys for interactive prompting“Yes”, “Back”, and “Next”

● Open listening● Two settings keys (plus/minus) for ringer vol-

ume, ringer pitch, alerting tone, open listen-ing

● Suitable for wall mounting● no modularity (no connecting capability for

adapters or add-on devices)

The optiPoint 500 basic is a professional tele-phone with all the features of the optiPoint 500economy, plus:● Interfaces and slots:

– 1 USB 1.1 interface – 1 adapter slot (option bay) – 1 interface for max. 2 add-on devices



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




optiPoint 500 standard, optiPoint 500 standard SL (only for U.S.)


The optiPoint 500 standard is a professional tele-phone with all the features of the optiPoint 500 ba-sic, plus:● Full duplex speakerphone mode with echo

suppression for adapting to the room

Note: optiPoint 500 standard and optiPoint 500standard SL (U.S. only) function identically whenconnected to HiPath 3000 systems.

The optiPoint 500 advance is a professional tele-phone with all the features of the optiPoint 500standard, plus:● 19 function keys with LEDs (4 that can be pro-

grammed with HiPath 3000/5000 Manager E,15 freely programmable)

● Interfaces and slots: – 1 integrated USB 1.1 interface – 2 adapter slots (option bays) – 1 interface for max. 2 add-on devices – 1 headset connection (121 TR9-5)




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.5.3 Comparison of Features on All optiPoint 500 Telephones

Feature optiPoint 500 telephone

entry economy basic standard advance

Function keys with LEDs:variable using HiPath 3000/5000 Manager E)

8 4 4 4 4

Function keys with LEDs:programmable

– 8 8 8 15

12-element keypad (0 - 9, #, *) x x x x x

Two settings keys (plus/minus) x x x x x

Open listening x x x x x

Full duplex speakerphone mode – – – x x

Adapter slots (bay options) – – 1 1 2

USB interface – – 1 1 1

Three dialog keys – x x x x

Display – 2 x 24 2 x 24 2 x 24 2 x 24

Connection for optiPoint key module – – x x x

Connection for optiPoint BLF – – x x x

Optional wall mounting x x x x x

Dimensions in mm:● Width● Depth● Height

15922064

21422068

21422068

21422068

21422068

Maximum length of the connecting line inmeters:● Without plug-type AC adapter● With plug-type AC adapter

5001000

Maximum length of connecting line between

primary and secondary telephone (throughphone adapter) in meters

100



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.5.4 optiPoint 500 Add-On Devices

You can use the optiPoint key module and optiPoint BLF add-on devices to increase the numberof available function keys on the optiPoint 500 basic, optiPoint 500 standard, and optiPoint 500

advance telephones.

The user usually installs the add-on devices. The installation instructions are on the “ElectronicOperating Instructions” CD.

Refer to optiPoint BLF for model-specific information on the optiPoint key module and theSection 4.9.3.

8.5.4.1 optiPoint key module

7CautionAlways disconnect the line cord before connecting add-on devices to the telephone.

The optiPoint key module is an add-on device (BSG) thatshould be mounted on the side of the telephone; it providesan additional 16 keys, LEDs and labelling areas for all pur-poses.Double assignment can be performed for the keys if onlynumbers without LED support are saved on the first level. Itis also possible to program numbers without LED support onthe second level. These can be internal station numbers, DID

numbers and numbers from a HiPath network (see also page8-63).





3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




The optiPoint application module can be connected to the following telephones:

● optiPoint 500 basic, optiPoint 500 standard, optiPoint 500 standard SL (U.S. only), opti-Point 500 advance

When used in a TDM environment, the key module only supports the personal internalphonebook.

● optiPoint 410 standard, optiPoint 410 advance, optiPoint 420 standard, optiPoint 420 ad-vanceIn VoIP environments, the key module supports functions, such as, personal phonebook,LDAP, WAP browser, Java applications, voice dialing.

The optiPoint application module must always be connected as the first key module. In otherwords, it must be directly connected to the telephone. Another key module can also be at-tached.


The following table shows the possible configurations for add-on devices on telephones fromthe optiPoint 500 family (not optiPoint 500 entry and optiPoint 500 economy).

Table 8-4 Add-On Device Configuration at an optiPoint 500 Telephone

optiPoint 500 telephone 1st add-on device 2nd add-on device

optiPoint 500 basic

optiPoint 500 standard, opti-Point 500 standard SL (onlyfor U.S.)


optiPoint key module –

optiPoint key module optiPoint key module

optiPoint key module optiPoint BLF

optiPoint application module –

optiPoint application module optiPoint key module

optiPoint application module optiPoint BLF

optiPoint BLF –

optiPoint BLF optiPoint BLF1

1 Configuration with two optiPoint BLFs only with HiPath 3800.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.5.5 optiPoint 500 Adapter

The various optiPoint 500 adapters (not optiPoint 500 entry and optiPoint 500 economy) allowflexible expansion of the telephone workstation by providing additional device connections

(such as PC, fax equipment, telephones, headsets).

The adapters, which are to be mounted on the underside of the telephone, are “plug’n’play”.When a new telephone-adapter configuration is plugged in, it generates a reset; a setup mes-sage notifies the system of the new configuration.

Option bays

7CautionAlways disconnect the line cord before connecting adapters to or disconnectingthem from the telephone.

Option bays (adapter slots):● 2 x for optiPoint 500 ad-

vance (shown here)● 1 x for optiPoint 500 ba-

sic and optiPoint 500standard



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




optiPoint analog adapter

The adapter must always have a local power supply for operating the connected analog device.

T/R interface properties:

● Supply current: 30 mA

● Busy signal when both B channels are busy

● Ring sequence: 2.2

● Supports only DTMF with Flash

● No ground signaling allowed

Does not support: VoiceMail server with a/b interface, message waiting lamp, dictating equip-ment, speaker, announcement device (such as start/stop).

The optiPoint analog adapter allows an analog device(such as telephone (DTMF only), group 3 fax, modem,cordless telephone) to be connected to the optiPoint500 telephone.The connected analog device can send and receivecalls to the system on the UP0/E interface regardlessof the connection status of the optiPoint 500 tele-phone, as long as a B channel is available.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


optiPoint acoustic adapter

Notes on the optiPoint acoustic adapter

● The internal components of the optiPoint terminal are deactivated in speakerphone modeif an external microphone and an external loudspeaker are used (sense lead).

● optiPoint 500 basic does not support the connection of an external microphone to the op-tiPoint acoustic adapter.

● The speakerphone mode selection is independent of whether the internal or an externalspeakerphone is used. External speakerphones have precedence over internal speaker-phones with the exception of manual intercom and signaling procedures.

● The internal microphone, the transmitter inset and any microphone connected to the opti-Point acoustic adapter are muted in the “Mute” audio state.

● Ring, alarm and key tones are transferred to the internal loudspeaker and not to an externalloudspeaker connected to the optiPoint acoustic adapter.

● The volume keys on the optiPoint terminal are used to adjust the volume level of the inter-nal loudspeaker and any connected external loudspeaker. The volume of the external loud-speaker can also be adjusted using the external amplifier.

The optiPoint acoustic adapter is used for connecting● a headset (121 TR 9-5) (see Section 8.6.3)● an active loudspeaker box and a desk microphone

via the Y cable● busy display/door opener and secondary bell/light

paging, etc. (each with its own power supply) viafloating contacts (not supported when using theadapter on optiPoint 410 and optiPoint 420).






A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


● Cable lengths – Maximum 100 m (328 feet) with a cable impedance of 75 ohms – Maximum 200 m (656 feet) with a cable impedance of 150 ohms (complies with CCITT

recommendation I.430)

The NT terminating resistors are integrated into the ISDN adapter.

optiPoint phone adapter

The optiPoint phone adapter is used for connecting asecond optiPoint 500 telephone (client telephone) withits own power supply.The system treats the client as an independent tele-phone with its own phone number and B channel whichcan make or receive calls regardless of the host tele-phone’s status.The maximum distance between the host and clienttelephones is approx. 100 m (J-Y (ST) 2x2x0.6,∅ 0.6 mm).



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.5.6 Restrictions for Using optiPoint Adapters

Adapter Categories

Each UP0/E port in the system provides two B channels. This means that you can connect twotelephones, each with a separate phone number, to one UP0/E port.

Category 1 optiPoint 500 adaptersEach of the following adapters needs both B channels and can therefore only be used once ona host telephone.

● optiPoint analog adapter

● optiPoint ISDN adapter

● optiPoint phone adapter

If one of these adapters is used in the optiPoint 500 advance, only a category 2 adapter can beoperated in the second slot.

Category 2 optiPoint 500 adaptersThe following adapters can be used on the host and client telephones. This is also true if a cat-egory 1 optiPoint 500 adapter is already connected.

● optiPoint acoustic adapter

● optiPoint recorder adapter




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Accessories for optiPoint Telephone Solutions

8.6 Accessories for optiPoint Telephone Solutions

8.6.1 Local Power Supply for optiPoint 500 and optiPoint 600 office

You may need a local power supply if you are using large configurations or if you need to extendthe range.

You can connect the local power supply to the line cords of a host or client telephone using twoMW6 jacks and the included connecting cable (part number see Section 8.6.4).

Data for local power supply AUL:06D1284:

● Line voltage: 220 (230) V AC

● AC line frequency: 47 ... 53 Hz

● Output voltage: Max. 50 V, min. 30 V

● Output current: Max. 250 mA

8.6.2 optiPoint 410 and optiPoint 420 Power Supply

The power supply unit features two MW6 jacks. Power is fed to the terminals over the left jacklabelled "Digital".


Technical Specifications Local power sup-ply, Euro

C39280-Z4-C510

Local power sup-ply, UK

C39280-Z4-C512

Local power sup-ply 110 V U.S.

C39280-Z4-C511

Line voltage 230 Vac 230 Vac 120 VAC

AC line frequency 50 Hz 50 Hz 60 Hz

Output voltage max. 43 VDC,min. 30 VDC



Output current 480 mA 480 mA 480 mA



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.6.3 Headsets

A headset replaces the telephone handset, which means that the user’s hands are free whentelephoning. It is also possible to use of a cordless headset (121 TR 9-.5)

Section 8.6.4 provides details on the various headset models together with the correspondingpart numbers.

A headset key can be configured for the optiPoint terminal. This allows the user to take callsand to switch between the handset and the headset.

Figure 8-35 Example of a Corded and a Cordless Headset




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Connection options

optiPoint telephones not included in the table below do not support headset connection.

Information on connecting the headset is provided in the relevant installation instructions.

Table 8-5 Connection Options for Corded and Cordless Headsets

Telephone Connection Options for Corded and Cordless Head-sets

Direct Using an optiPointacoustic adapter1

1 Accepting and ending calls using the headset keys is only supported if the connection is established using an

optiPoint acoustic adapter.

optiPoint 500 basic X

optiPoint 500 standard, optiPoint 500 stan-dard SL (only for U.S.)

X

optiPoint 500 advance X X

optiPoint 600 office X XoptiPoint 410 standard,optiPoint 410 standard S

X X

optiPoint 410 advance,optiPoint 410 advance S

X X

optiPoint 420 economy plus X

optiPoint 420 standard X X

optiPoint 420 advance X X



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.6.4 Part Numbers

The current sales information contains the complete overview of all certified and deliverableproducts.

Telephone / Accessories Color Part Number

optiPoint 500 entry arctic S30817-S7101-A101-*

manganese S30817-S7101-A107-*

optiPoint 500 economy arctic S30817-S7108-A101-*


optiPoint 500 basic arctic S30817-S7102-A101-*


optiPoint 500 standard arctic S30817-S7103-A101-*


optiPoint 500 advance arctic S30817-S7104-A101-*


optiPoint key module arctic S30817-S7105-A101-*


optiPoint BLF arctic S30817-S7107-A101-*


optiPoint phone adapter arsenic S30817-K7110-B108-*

optiPoint analog adapter arsenic S30817-K7110-B208-*

optiPoint ISDN adapter arsenic S30817-K7110-B308-*

optiPoint acoustic adapter arsenic S30817-K7110-B508-*

optiPoint recorder adapter arsenic S30817-K7110-B408-*

optiPoint 500 entry wall bracket arsenic C39363-A328-C338

optiPoint 500 basic wall bracket arsenic C39363-A329-C338

Local power supply AUL:06D1284

Local power supply, UK AUL:06D1287

Local power supply, 110 V USA AUL:51A4827

Local power supply, Euro C39280-Z4-C510

Local power supply, UK C39280-Z4-C512

Local power supply 110 V U.S. C39280-Z4-C511




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


Headset handset interface2001 Vista Supra (with headband)

L30460-X1050-X

Headset handset interface2001 Vista Mirage (no headband)

L30460-X1050-X1

Headset2001 Vista Encore monaural

L30460-X1050-X3

Headset2001 Vista Encore binaural

L30460-X1050-X5

Headset2001 Vista Tristar with headset

L30460-X1050-X7

Headset

2100 FlexBoom NC Mono

L30220-F600-H184

Headset2100 FlexBoom NC Duo

L30220-F600-H185

Telephone / Accessories Color Part Number



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.7 optiPoint 600 office

8.7.1 Features

● UP0/E TDM interface available.

● Extra-large grayscale display with touchscreen functionality, graphics capability, and op-tiGuide user interface, offering the highest degree of user-friendliness through practical,straightforward menu guidance

● Local electronic notebook, allowing for fast, convenient access to personal contact details

● Support for the entire range of HiPath 3000/5000 telephone features, including automaticcallback, executive/security features, conference calls, and group calls

● Integrated 10/100-Mbps mini-switch allowing for the direct connection of a PC workstationto the LAN

● Central power supply over the LAN based on the 802.3a/f standard

● Software updates and feature extensions via FTP

● Easy relocation, as the telephone automatically registers with the system following connec-tion to the LAN

Product Image




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.7.2 optiPoint 600 office as System Telephone

optiPoint 600 office completes the optiPoint 500 system telephone family. It provides all HiPath3000 features quickly and easily.

The integrated USB 1.1 interface can be used for PC connection. TAPI Service Provider Call-Bridge lets you set up calls quickly and easily directly from the PC.

8.7.3 Advantages at a Glance

Cost Reduction

● Cabling costsNo additional wiring necessary for optiPoint 600 office. The PC is connected via the inte-grated switch.

● Infrastructure costs for the data and voice network – one network, – one investment, and – one team for maintenance and service.

Investment Protection

● A single device for the HiPath 3000 and HiPath 4000 communications platforms

● The latest feature releases available as software downloads

Intuitive Operation

● Clear overview with large display and direct selection via touchscreen functionality

● Interactive promting with dialog keys and display via optiGuide

● Programmable direct access keys

● Direct dialing from the PC with CTI (TAPI)

Flexibility

● Upgrades available as software downloads

● Administration with Web browser and SNMP

● Quick configuration with DHCP (plug and call)

● Compatibility with different workstation environments using adapters and key modules



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




Comfort

● Speakerphone for spontaneous inclusion of parties present in call with excellent voicequality

● Full access to all HiPath 3000 and HiPath 4000 telephony features

● Direct dialing from the PC

● Large display with touchscreen functionality

8.7.3.1 General Local Features

● Tilting grayscale graphics display with 320*240 pixels (8*24 characters), touchscreen func-tionality, background lighting and adjustable contrast

● Nineteen programmable function keys with LEDs

● Three dialog keys for interactive user guidance with optiGuide

● Two control key (plus and minus) for setting ringer pitch and volume

● Speakerphone mode and open listening

● Offhook dialing

● Calling party identification

● Key click tone

● Password protection for administrator-specific data

● DTMF/signaling, inband and outband

● Feature updating with software downloads (via FTP)

● Electronic notebook for 640 entries

● Headset interface (121 TR9-5 and Polaris)

● Hearing-aid compatibility

● CTI

● CAPI over USB and CallBridge for Data

● JAVA Virtual Machine (VM) plus JAVA Development Kit (JDK) for generating user-specificJAVA applications

● Virtual key module (speed dialing application) with 40 speed dialing keys

● WAP bookmarks

● Input of WAP/URL addresses

● Resource sharing for optiPoint 600 entries over the PC keyboard




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


8.7.3.2 Accessories

Adapter

● optiPoint acoustic adapter

● optiPoint analog adapter

● optiPoint ISDN adapter

● optiPoint phone adapter

● optiPoint recorder adapter

Add-on devices

● optiPoint key module

● optiPoint signature module

● optiPoint BLF



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



optiPoint WL2 professional/optiPoint WL2 professional S

8.8 optiPoint WL2 professional/optiPoint WL2 professional S

optiPoint WL2 professional uses WLAN to simplify corporate access to data and resources.

WLANs are transparent in IP traffic and therefore create an ideal environment for IP multimediaapplications. The incorporation of real-time IP communication (voice, for instance) is the nextlogical phase because it uses the investments in convergent LANs and extends the range of IPtelephony and multimedia communication systems in a company.

Product image

Figure 8-36 optiPoint WL2 professional

Workpoints used

HiPath 3000/5000 provides wireless LAN services when connected to a WLAN access pointvia a DMZ interface. The following WLAN workpoints are used:

● optiPoint WL2 professionalApart from Relocate, all HiPath 3000/5000 features in the display dialog, service menu,and on function keys are available.

● optiPoint WL2 professional S

Supports SIP (Session Initiation Protocol). SIP is an ASCII-based signal protocol used toset up sessions in an IP network.

Properties

Wireless LAN Voice-over-IP telephone with color graphics display.

optiPoint WL2 professional can be operated with HiPath 3000/5000 V5.0 or later.optiPoint WL2 professional S is developed as a solution for SIP systems and can be operatedwith HiPath 3000/5000 V6.0 and later.




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


● Interfaces: WLAN, USB

● Standards: WLAN, 802.11b (11 Mbps), 802.11g (full support for 54 Mbps), CorNet IP, SIP

Configuration

● Wireless connection with a WLAN access point as a link to a LAN switch

● IP connection to the HG 1500 gateway in the HiPath 3000 system; CorNet-IP registration

● Basic configuration via DHCP

● Advanced configuration over the telephone Web page (standalone telephone) or via theHiPath Deployment Service.

Features

Telephone

● Telephone with color graphics display(six lines, 128 x 128-pixel resolution, 4096 colors, 3.1 x 3.1 cm)

● Call animation and caller display (CLIP)/caller ID for incoming calls

● Illuminated keypad

● Two softkeys for dynamic feature access

● Intuitive user prompting

● Illuminated MWI key● Speakerphone key

● Status display in standby or idle mode shows: date, time, battery status, RF signal strength,access point connected

● Status display during the call shows: battery status, RF signal strength, time per call, off-hook handset, CLIP/caller ID

● Missed calls display

● Speakerphone function

● Answered calls display

● Dialing by means of number entry, SIP-URI (professional S), and IP address (direct IP call)

● Multiline functionality

● Programmable speed dialing keys

● Dial preparation (phone number entry before line seizure) with correction option

● Redial function for the last ten different numbers dialed



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




● Key-activated keypad lock and ring tone deactivation with icon display

● Common user interface for Siemens desktop phones with optiGuide user interface (profes-sional S)

● Access to HiPath features (depending on the HiPath system connected) for call features,such as, callback, conference, consultation hold, etc.

● Local SIP features (professional S): hold, mute, transfer, three-party conference, MWI,DND, etc.

● SIP features with server support: Group Pickup, Priority Alerting, Distinctive Ringing, Key-set, Shared Call Appearance, Bridge Line Appearance, etc.

Local phonebook

● Comprehensive local phonebook/address book

● CLIP replaced by the phonebook entry in the telephone or HiPath system

Audio

● Six polyphonic ring tones (adjustable volume)

● 16 ring tones, 12 of which are managed by the HiPath system and four by the user

● Ring tones can be downloaded

● Volume adjustment (eight settings)

● CLIP-/caller-ID-dependant ring tones

● VIP calls

Added-value applications and features

● Caller announcements(CLIP/caller ID)

● Voice dialing

● Polyphonic ring tones (downloadable)

● Access to LDAP directories● Headset connection via a Slim Lumberg connector

● Vibrating alarm

● Designed for broadband voice transmission (optional, G.722)

● CTI interface




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


● Upgrades and configurations can be performed OTA (Over The Air) using the HiPath De-ployment Service tool (advanced administration application)

● Support for HiPath applications

Codecs

● G.711 (a-law and µ-law)

● G.729ab (G.729a with VAD (Voice Activity Detection))

● G.723

● G.722 (optional)

● Advanced Echo Cancellation (AEC)

QoS

● ToS

● DiffServ

● 802.1q

● 802.11e (WME subset)

Accessories

● Desktop charger● Desktop charger with second battery charging option

● USB data cable

● Broad range of headsets available

● Selection of carry sets available

● Power adapter (suitable for the relevant geographical region)

Additional features

● Web-browser-based administration

● Multilingual user interface

● Date and time synchronization via the NTP server or HiPath system

● Range: indoors: up to 30 m (depending on the environment)Outdoors: up to 300 m (depending on the environment)

● Power supply unit (Li-Ion, 3.7 V, battery)



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




● Operating times: talk time up to 4 hours; standby time up to 80 hours

● Weight: approx. 100 g

● Dimensions:Telephone: 132 x 52 x 22 mm (LxWxH),Charger: 70 x 73 x 35 mm

● Color: Light Cashmere Silver

Wireless Features

● 802.11g (fallback to 802.11b)

● Frequency range: 2.4 – 2.497 GHz

● Number of dialable channels: 13 (ETSI) or 11 (North America)

● Adjustable transmit power: approx. +20 dBm EIRP

● Site Survey Tool integrated in the telephone

● Transmission rates: 54, 48, 36, 24, 18, 12, 11, 9, 6, 5.5, 2, 1 Mbps

● SSID

Security Features

● WEP (64, 128 bits)

● WPA

● Cisco infrastructure support with CCX

● PIN-protection for telephone

● VPN client

● Authentication (login/password)

● 802.11i (optional, if the standard is selected)

Authentication● EAP-TLS

● LEAP

Protocols/Network Features

● DHCP client

● FTP client




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


● VLAN support

● SNMP trap agent

● VoIP (SIP, RTP, RTCP, TLS)

● DNS

● HTTP and HTTPS servers

● PPTP for VPN support

● UPNP (control point and device)

● IP addressing: fixed, DHCP, PPPoE

PC Software

● PC tool for swapping Microsoft Outlook phonebook data with data in the WLAN telephone’slocal phonebook

● Ring tone downloading from the PC to the telephone






A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Mobile Telephones for HiPath Cordless Office

8.9.2 Gigaset S4 professional

Gigaset SL4 professional is a DECT-standard mobile telephone and suitable for HPS.

Product image

Figure 8-38 Gigaset S4 professional


● Mobile telephone operation times

– Standby time (without display illumination): approx. 165 hours

– Talk time: approx. 12 hours

– Charging time: approx. 7,5 hours

● Dimensions (H × W × D in mm)

– Handset: 146 x 49 x 26

– Charger: 39 x 87 x 83

● Weight of the mobile telephone incl. battery: approx. 125 g

● Operating temperature of the mobile telephone: +5 °C to +45 °C (41 °F to 113 °F)



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011




8.9.3 Gigaset M2 professional

Gigaset M2 professional is a very robust mobile telephone based on the digital DECT/GAPstandard. It is suitable for use in environments requiring telephones to be break- and shock-

proof and dust- and spray-resistant.

Product image

Figure 8-39 Gigaset M2 professional

Special features

● IP rating IP 65 (casing protection):

– Protected against splashes and low-pressure jets of water

– Dustproof

● Break- and shockproof

● Silicon-free surface

● Sturdy carry clip

● Immunity from electromagnetic radiation in accordance with EN 50 082-2

● Acoustics optimized for industrial environment with 5 volume levels

● Memory card for device-specific and individual entries

● Emergency key (individual programmable key)


● Operating times:




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm


– Standby time (without display illumination): approx. 200 hours

– Talk time: approx. 10 hours

– Charging time: approx. 6 hours

● Dimensions (H × W × D in mm):

– Handset: 167 × 56 × 35

● Weight of the mobile telephone incl. battery: approx. 176 g

● Operating temperature of the mobile telephone: –10 °C to +55 °C (14 °F to 131 °F)



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



Attendant Consoles

8.10 Attendant Consoles

8.10.1 HiPath Attendant B Braille Console

Definition

For the HiPath 2000 / HiPath OpenOffice EE / HiPath 3000 / HiPath 5000 systems a convenientand user-friendly Braille terminal that can be used as an attendant position for visually-impairedswitchboard personnel.

(PC attendant console) is required to operate the HiPath Attendant BoptiClient Attendantbraille console.

The braille console’s braille output line (40 characters) displays the current optiClient Attendantstatus information. The keys on the braille console provide access to nearly all optiClient Atten-dant functions. So visually impaired users can perform most of the same switching tasks astheir seeing colleagues.

At power-on, the console starts in auto-information mode, providing the user with instructionson the main functions for orientation purposes. For further instructions, the attendant can acti-vate an information mode that provides extensive operating information on the braille outputline.

The braille console automatically uses the language set in optiClient Attendant. The Braille ter-minal is connected via one of the free COM ports on the optiClient Attendant PC.

>

The Attendant B braille console can be ordered directly from:Winkler Kommunikationstechnik

Ahornstrasse 1226180 Rastede/IpwegeGermanyTel.: ++49-4402-929292Fax: ++49-4402-929294http://www.juergen-Winkler.comOrdering designation: BT-H150 Office-PCVF-001-ADelivery time is roughly six weeks after receipt of order.


Braille console

HiPath Attendant B

http://www.juergen-winkler.com/

http://www.juergen-winkler.com/




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Attendant Consoles

8.10.2 optiClient Attendant V8

Definition

optiClient Attendant is a PC-based attendant console and can be connected to HiPath 3000/ HiPath 2000/HiPath OpenOffice EE systems. Depending on the model, up to six optiClient At-tendants can be implemented at each node. The full version of optiClient Attendant V8 is avail-able as an order item.

optiClient Attendant can also be implemented as a central attendant console in a network con-sisting of HiPath 3000/HiPath 2000/HiPath OpenOffice EE systems.

Technical changes compared to version 7.0:

● A device is required to operate optiClient Attendant V8, even when operating the IP con-nection variant. This device is sold separately (no connection via SoftOla).

● Any headsets used should therefore be connected to the telephone instead of the PC.

● If the optiClient Attendant PC experiences a malfunction or is switched off, reachability isguaranteed via the telephone.

Connection Types

● Connection via IP to:optiPoint 410, 420; OpenStage TDM telephones [not connected to CorNet-IP (HFA)]

● Connection via USB interface to:optiPoint 500, OpenStage 40 T

>optiClient Attendant V8 replaces the existing optiClient Attendant V7.0 in all connec-tion variants (USB and LAN).optiClient Attendant V7.0 will no longer be marketed.

>optiClient Attendant V8 only operates in conjunction with HiPath 3000 V8, HiPath3000/5000 V7, HiPath 2000 and higher and HiPath OpenOffice EE and higher andis not downwards-compatible.optiClient Attendant V7.0 is not compatible with HiPath 3000 V8, HiPath 3000/5000V7, HiPath 2000 V2 and higher, and HiPath OpenOffice EE and higher (no upgradepossible).



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



Attendant Consoles

optiClient Attendant V8 features

● Ongoing, waiting or parked calls are displayed with type, name, and phone number.

● Acoustic message signaling with volume control

● Display of the switching state of source and target

● Answering of pending calls

● VIP call flagging for preferred call acceptance

● Selection of telephone directories:

– Outlook contacts

– Lotus Notes

– Internal Attendant telephone directory, based on Microsoft Access

– Open LDAP

● Advanced integration with MS Outlook, featuring direct e-mail transmission using thephonebook entry

● Call statistics for incoming calls with sort function according to various criteria

● Convenient caller list with an almost unlimited number of entries, sorted according to dateand time

● Additional functions such as hold keys, override, callback, conference, paging, speaker an-

nouncements, alarm signaling, view call charges, redial (last 10 dialed destinations)

● No calls are lost: Options are provided for intercepting unanswered DID calls and DID callsto busy stations

● Online help under Windows

● Convenient configuration of individual features

● Service tools for diagnosis and protocols

● Simple installation routine

● User interface currently available in German, English, Dutch, Portuguese, Italian, Frenchand Spanish

● Optional braille console connection

● optiClient Attendant may serve as the central attendant console in HiPath networks

● Import of CSV files to the integrated internal phonebook




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Attendant Consoles

● Busy lamp fields offer the following features:

– Up to 300 fields per BLF

– Up to two BLFs possible

– Configuration of busy lamp fields to suit individual user requirements

– BLF scalability with automatic font adjustment

– Speed dialing via busy lamp field

– Color display of station status: idle, calling, busy internal, busy external

– Call forwarding may be switched on or off for each station

– Do not disturb may be switched off for each station

– Displays "forwarded" and "do not disturb" using symbols

– Name definition for BLFs

– Definition of titles for groups of BLF stations

– Access to public calendar (Exchange)

– Copy/cut and paste on the BLF



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



Attendant Consoles

optiClient Attendant compatibility

PC system requirements:

● Pentium IV

● Memory: 256 MB

● Operating systems: WIN2000, XP, 2003 Server (for Windows Vista Business, see notes insales information)

● Microsoft-compatible mouse

● CD-ROM or DVD drive

● For operation with a TCP/IP connection:

– Functional system with network card configured

– optiPoint 410, optiPoint 420 telephones (for OpenStage telephones, see notes in the

sales information)

● For operation with USB:

– optiPoint 500 with USB port (OpenStage terminals, see notes in the sales information),USB cable (code number: S30267-Z360-A30-1),USB driver (included in CallBridge TU software)and a free USB port on the PC.

HiPath 3000 V8

HiPath 2000 V2/HiPath OpenOffice EE

HiPath 3000/5000 V7

HiPath 2000 V2 /HiPath OpenOffice EE

HiPath 3000/5000

V6.0HiPath 2000 V1.0

HiPath 3000/5000

V5.0

optiClient At-tendant V8

Yes Yes No,not ready for startup

No,not ready for startup

optiClient At-tendant V7.0



Yes Yes




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Attendant Consoles

Overview of supported Microsoft operating systems by connection type

Licensing

A license is required for optiClient Attendant V8. optiClient Attendant is licensed centrally viaHiPath License Management.

When commissioned for the first time, optiClient Attendant V8 can be operated license-free fora maximum of 30 days at HiPath 3000 V8, HiPath 3000/5000 V7, HiPath 2000 V2 and higher,and HiPath OpenOffice EE and higher as part of the grace period offered by these systems.

Model-specific data

Connection type Windows 2000 Windows XP Windows Vista

BusinessUSB interface X X 1

1 See notes in the sales information

TCP/IP X X 1

Subject HiPath 3000 HiPath 3000/5000 HiPath 2000 /HiPath OpenOffice EE


Hardware require-

ments

Software requirements V8 7V V2 or later

Max. no. of optiClientAttendants

6 6 1



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



Attendant Consoles

8.10.2.1 opt iClient Attendant as a Central Attendant Console

The optiClient Attendant can be used as a central attendant console throughout an IP network(max. 6 optiClient Attendants per network). The attendant consoles must be connected to one

of the network’s HiPath 3000 nodes, or registered, to enable network-wide BLF functionality.This functionality is independent of the optiClient Attendant connection type (IP, UP0/E or USBvariants).

>The optiClient Attendant’s control of network-wide busy signaling is independent ofthe network-wide busy signaling to workpoints by the HiPath 5000 Presence Man-ager.

IP-networkedHiPath 3000

HiPath 3000 cen-tral node

TDM terminalsTDM terminals

IP terminals +

IP clients

optiClientAttendant

IP network

Public network




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Attendant Consoles

8.10.2.2 optiClient BLF V1

optiClient BLF is an independent application for displaying the BLF status (for example, free,busy or ringing). optiClient BLF windows are scalable and can display between 25 and 200

BLFs in incremental stages. The application is released for use with Windows XP, Windows2000 and Windows Vista PCs. Up to 100 optiClient BLF applications can be operated per sys-tem or network.

optiClient BLF V1 software is included on the CD shipped with optiClient Attendant V8. Onelicense per active optiClient BLF is required for operation. Licensing is via independent CLA.The license may be installed on the same PC as the optiClient BLF or centrally on the customernetwork.

The following functions are only available on the optiClient Attendant BLF: call setup from BLF,call forwarding activation/deactivation, subscriber-driven DND deactivation.

The optiClient BLF should always be operated with optiClient Attendant V8.

The optiClient BLF and optiClient Attendant BLF server components communicate via TCP/IP.

Each optiClient BLF may be configured individually according to user requirements.

Each optiClient BLF is licensed via HiPath License Management. The necessary license file isloaded onto a local CLA or one on the customer network. All software components required byoptiClient Attendant V8 and optiClient BLF V1 are provided on the optiClient Attendant V8 CDand may be downloaded from the software server.

The main functions are:

● Network-wide busy signaling via BLF server

● Phonebook connection via TAPI: Microsoft Outlook contacts, database connection via Mi-crosoft Access, Lotus Notes

The optiClient BLF can be operated in two variants. Either each HiPath system has its own op-tiClient Attendant or IP-networked systems have a central optiClient Attendant.



3000sb7.fm

A31003-H3580-Y100-10-7618, 01-2011



Attendant Consoles

Function principle:

Note: The BLF server does not necessarily need its own hardware. BLF server software canalso be installed, for example, on an optiClient Attendant PC.Expansion: BLF statuses are not visible from CorNet IP networked systems. This is advanta-geous for example with narrow band IP infrastructure which is not suitable for VoIP.

optiClient BLFBLF status display

BLFstatus

BLFstatus

BLFstatus


BLF server, distri-bution function

BLFstatus




A31003-H3580-Y100-10-7618, 01-2011


3000sb7.fm

Attendant Consoles

8.10.3 optiPoint Attendant

Definition

Switching services can be performed in HiPath 3000/5000 using a specially configured tele-phone. This optiPoint Attendant (AC) also serves as an intercept position at the same time. Atthe AC all calls accumulate if there is no direct inward dialing option, or if a station could not becontacted using the call allocation algorithm in Call Management (intercept). The operator thenforwards the incoming calls to the relevant stations.

The optiPoint 500 basic, optiPoint 500 standard and optiPoint 500 advance system telephonesas well as IP phones can be configured as optiPoint Attendant.

The function keys of the system telephone used for optiPoint Attendant are preset as followsand can be changed by the service technician if necessary:

● Night answer (switches night answer on/off)

● Telephone directory (opens the internal telephone directory)

● Held calls (provides information on the number of held calls)

● Busy override (goes into a busy connection)

● Hold (puts a party on hold)

● External 1 (first external call, incoming/outgoing)

● External 2 (second external call, incoming/outgoing)

● Disconnect (disconnect or connect a call)

optiPoint AttendantDepending on the individual customer’s requirements, optiPoint BLF can beequipped with key modules and/or with busy lamp fields (). The number of function keys (par-ticularly the internal name keys) is increased accordingly (Table 8-6).

When a total of 2 key modules and 2 optiPoint BLFs are connected up a maximum of 212 in-ternal name keys (with internal station number) with busy lamp indicator can be shown.

Total number of keys 16 32 48 64 90 106 122 180 196 212

Number of key modules 1 2 3 4 – 1 2 – 1 2

Keys on key modules 16 32 48 64 – 16 32 – 16 32

Number of BLFs (optiPoint BLF) – – – – 1 1 1 2 2 2Keys on BLFs (optiPoint BLF) – – – – 90 90 90 180 180 180

Table 8-6 optiPoint Attendant - Function key totals for additional key modules and BLFs



3000sb8.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Applications

Overview

9 Applications

9.1 Overview

The scope of features of the systems HiPath 3000/5000 can be expanded by connecting appli-cations. This includes applications such as Automatic Call Distribution (ACD), hotel applica-tions, voice messaging services, charge computing, video conferencing and mobile communi-cations.

Communication between HiPath 3000/5000 and applications (Plus products) running on hostcomputers is possible via

● the V.24 application interface (CSTA protocol, 19200 Baud)

– Plus Products that support the CSTA protocol standardized by ECMA can be connect-

ed directly (for example, Hicom Agentline Office V1.1 CSTA).

● an S0 port configured as a station (ISDN/USBS)

● an ISDN adapter (TA S0) (ISDN/USBS)

● the LAN port (Ethernet).Details on this subject can be found in Kapitel 4.

● the PSTN port.Details on this subject can be found in Kapitel 4.

HiPath 3000/5000 support CSTA Phase II and CSTA Phase III.During call setup the connected application determines whether CSTA Phase II or Phase III isused.



Applications Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb8.fm

List of Certified Applications

9.2 List of Certified Applications

The following eCRM/Mobile Office/Vertical/HiPath Management applications are tested forHiPath 3000 V8. Concrete release information, release dates, country-specific releases andother details are provided in the respective product-specific sales information or can be ob-tained from the relevant product manager.

>Important: Information on the applications listed in the following table is provided in

the corresponding data sheets. Data sheets can be accessed on the Internet at:http://www.siemens-enterprise.com and viahttp://wiki.siemens-enterprise.com

Application HiPath 3000 models

Name Version HiPath 3800 HiPath 3550HiPath 3500


HiPath Xpressions V5 X X X

HiPath ProCenter Agile/Enterprise V7 X X –

HiPath ComAssistant V2 X X X

HHSC V2.0 Business V2.0 X X –

HHSC V2.5 Connect V2.5 X X –

HHSC V2.5 Professional V2.5 X X –

Teledata Office V4.0 X X X

HiPath Accounting Management V1.0/V2.0 X X X

HiPath Fault Management1 V2.0(Release 4)

X X X

HiPath User Management2 V2 X X X

TAPI 170, TAPI 120 V2.0 X X X

HiPath Xpressions Compact V3.0 X X X

DLS V2 X X X

HiPath DAKS V3 X X X

Table 9-1 Certified applications for HiPath 3000 V8

http://www.siemens-enterprise.com/

http://wiki.siemens-enterprise.com/

http://wiki.siemens-enterprise.com/

http://www.siemens-enterprise.com/



3000sb8.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Applications


Third-party applications are certified via the SEN Technology Partner program. Relevant infor-mation is available at:http://www.enterprise-communications.siemens.com/ global/Partner/Partner%20Program.aspx.

HiPath Cordless IP3 V1 X X X

1 Gateways can be integrated in network management systems (e.g. Fault Management) via SNMP-supported

management. The HG 1500 V3.0 cards support SNMP version 1.

2 Support for existing customers. No support for new projects, see HiPath UM V2 sales information.

3 Detailed information on supported features is documented in the HiPath Cordless IP sales release in Chapter 1.2.4.

Application HiPath 3000 models

Name Version HiPath 3800 HiPath 3550HiPath 3500


Table 9-1 Certified applications for HiPath 3000 V8

http://www.enterprise-communications.siemens.com/global/Partner/Partner%20Program.aspx

http://www.enterprise-communications.siemens.com/global/Partner/Partner%20Program.aspx



Applications Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb8.fm




3000sb9.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Capacities

Capacities of HiPath Systems

10 Capacities

10.1 Capacities of HiPath Systems

Guide to the table:

The values listed are maximum values.

The "networked" column refers to systems with 2000 stations.

N/A: not applicable

"=": Not dependant on the size of the network. The capacity of Vulcan standalone systems ap-plies.

"+": The network requirement is the total capacity of the individual nodes or systems in the net-

work.

The numbering format xx/yy/zz means valid for: Pro&ELS&SAPP/Com/Point (= HiPath 3800/ 37x0/35x0/33x0)

The HiPath 3000 capacities outlined in the table apply to HiPath 3800. Capacities for HiPath35x0/33x0 may differ from these values..

Parameter HiPath 3000 standalone HiPath 3000/5000 networked

Agents

Agent IDs in system HiPath 33x0/35x0: 150HiPath 3800: 3001 /3302

=

Agents active simulta-neously in system

HiPath 33x0/35x0: 323

HiPath 3800: 1003=

Agents in OpenScape Contact Center

Agent IDs in system HiPath 3800: 330HiPath 3550/HiPath 3500: 150

N/A

Agents active simulta-neously in system

HiPath 3800: 100HiPath 3550/HiPath 3500: 32 (64 with positive

evaluation with the Performance Tool and project-specific approval)Note: When connecting other call center solutions,the number depends on the evaluation using thePerformance Tool.

N/A

Direct trunk access

Number of allowed lists 6 =

Number of denied lists 6 =



Capacities Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb9.fm


Allowed list, short (10

entries with 32 digitseach)

5 =

Allowed list, long (100entries with 32 digitseach)

1 =

Direct trunk access -denied list, short (10entries with 32 digitseach)

5 =

Denied list, long (50 en-

tries with 32 digitseach)

1 =

trunks

Number (B channels) insystem

250 +

Call waiting

Number of externalwaiting calls per tele-phone

16 N/A

Number of internalwaiting calls per tele-phone

16 N/A

Missed calls list - used by telephones

Number of entries perlist

10 N/A

Number of lists in sys-tem

650 +

Number of lists per tele-

phone with display fieldor user group

1 N/A

Number of digits perentry

25-digit station number + seizure code =

Call pickup groups

Number of stations in agroup

32 =

Number per system 32 1000




3000sb9.fm

A31003-H3580-Y100-10-7618, 01-2011




Call forwarding (CF)

All calls - active simulta-neously in system

150 / 500 +

External - number ofCF keys per telephone

As many as available on the device N/A

External - number ofdigits

25-digit station number + seizure code N/A

Automatic announcement

Number of callers forwhom an announce-

ment can be played si-multaneously

30 +

Announcement devices

Number of devices towhich an announce-ment can be played si-multaneously

30 +

Total in system 16 +


Number of hold keysper optiClient Attendant

4 N/A

Total per group 6 =

Groups in the system 6 =

Overflow - number ofcalls in queue

16 N/A

Number of monitoredPABXs per node for"Busy" monitoring

100 720

Classes of serviceTotal in system 15 =

Matrix size - day andnight - number of trunks

30 =

Allowed and deniedlists

15 =





A31003-H3580-Y100-10-7618, 01-2011


3000sb9.fm


Team/Top

Number of executiveswith personal assis-tants per configuration

3/3 N/A locally only

Configurations in sys-tem

500 +

PIN for telephone lock/mobile PIN

Number of digits in thePIN code

5 N/A

CSTA

Number of applicationsthat can be connectedper system (server)

HiPath 3300/3350, HiPath 3500/3550: 4HiPath 3800: 8

+

Number of simulta-neous tasks

64 =

Number of TDS codes 10 =

Monitor points 700/200/70 +

Number of CTI jobs forCSTA links

980/280/80 +

DSS

Add-on devices persystem

100 +

Add-on devices pertelephone

2 N/A

Number of keys on anadd-on device

16;optiPoint 410 Self-Labeling Key: 13

N/A

Number of keys in abusy lamp field (BLF)

90 N/A

Number of BLFs in sys-tem

12 +

DID numbers

Number of digits 11 =




3000sb9.fm

A31003-H3580-Y100-10-7618, 01-2011




Administration

Number of simulta-neous administratorlogons

1 1

Call detail recording

Number of entries inthe buffer

300 N/A

Station selection keys

Number of station se-lection keys per tele-

phone

10 N/A

Group call

Number of groups 800 +

Hotline/hotline after timeout (=code blue)

Number of destinations 6 =

Conference

Number of participantsper conference

5 +

Number of conferencesin the system 12 +

Number of trunks in aconference

4 =

Station speed dialing (ISD):

Total entries in system 2000 +

Number of entries pertelephone

10 N/A

Number of digits per

entry


System speed dialing (SSD):

Total entries in system 1000 = or +

Number of digits perentry


Number of letters inname

16 N/A





A31003-H3580-Y100-10-7618, 01-2011


3000sb9.fm



Number of digits dialed 32 N/A

Number of digitschecked


Number of dial plans(up to 10 fields)

514 =

No. of outdial rules pertrunk group

254 N/A

Number of routes in apath table

16 N/A

Number of time zonesper day/week

8 N/A

Number of digits peroutdial rule

40 N/A

Line reservations (not S0)

Number of entries inthe system

32 N/A

DTMF DID

Number of simulta-

neous processes

6 N/A

MULAP keys

Number of keys on atelephone

10 N/A

Message texts

Total advisory messag-es in system

250 =

Number of messagesreceived on a tele-

phone with display (+1for voicemail)

5+1 N/A

Number of text mes-sages in the system

150 =

Number of messagesreceived on a tele-phone with display (+1for voicemail)

1+1 N/A




3000sb9.fm

A31003-H3580-Y100-10-7618, 01-2011




Configurable text mes-

sages and advisorymessages in the sys-tem

10+10 =

Length of the text (inwords) in a customer-defined message

24 N/A

Length of the text (inwords) of a generatedmessage

24 N/A

Mailbox: Total messag-

es active simultaneous-ly in system (text mes-sages and advisorymessages)

100 +

Name display

Internal stations andsubscriber groups -length in letters

16 =

Station speed-dialing

(SSD) - length in letters

16 =

Trunk groups: Length inletters

10 =

Stations (terminals)

Number of stations (ex-panded)

500 +

Park slots

Total in system 10 N/A

Account code

Number of testable dig-its

11 N/A

Total in system 1000 =

Trunk groups

Total number in system 16 +

Route overflow

Total per trunk group 1 N/A





A31003-H3580-Y100-10-7618, 01-2011


3000sb9.fm


Callback

Number of entries pertrunk

64 N/A

Number of entries perstation (each sent andreceived per extension)

5 =

Call forwarding (CF) - permanently configured in Call Management

In free or busy state:Total per telephone

1 N/A

Number of CFW desti-

nations per station

1+3 N/A

Number of destinationsin the Call Managementlist

500 +

CFSS destinations persystem

250 +

Call pickup groups (configurable)

Number of extensions 5 N/A

Languages

Number of languagessimultaneously activein the system (perma-nently installed + maybe freely installed)

4+4 N/A

Station groups

Length of group names 16 =

Number of telephonesper group

20 =

Number of groups forgroup call, hunt group,MULAP, announcementzones

800 +

Number of connectionsper group with voice-mail support (only onehunt group per system)

20 +




3000sb9.fm

A31003-H3580-Y100-10-7618, 01-2011




Station numbers

Total number in system(including station andgroup numbers)

1305 +

Number of extensionsin system

500 +

Number of group andhunt group numbers insystem

800 +

Maximum length of sta-

tion numbers

6 6

Length of station num-bers (default setting)

3 N/A

Internal phonebook

Number of simulta-neous logons (practi-cally unlimited)

All devices with display N/A

External phonebook (LDAP)

LDAP directory: num-

ber of simultaneouslogons

20 +

Door opener

Number of attempts toenter an invalid pass-word before deactiva-tion

5 N/A

Number of digits in PIN 5 N/A

Universal Call Distribution (UCD)

Number of priority lev-els per call type 10 N/A

Number of announce-ments per group

7 N/A

Number of groups insystem

60/60/10 +

Number of waiting callsper group

30 N/A





A31003-H3580-Y100-10-7618, 01-2011


3000sb9.fm


Networking

Number of seizurecodes

10 N/A

Number of digits in aseizure code

6 N/A

Last Number Redial (LNR)

Number of entries on atelephone with displayfield

10 N/A

Number of entries on a

telephone without dis-play field

1 N/A

Number of digits stored 25-digit station number + seizure code N/A

Music on hold

Number of externalconnections

6 +

Destination key/ISD

Number of destinationsin system

2000 +

Number of digits perdestination

25-digit station number + seizure code =

Tenant system (see fax and modem numbers below)

Tenants per system 3 =

ITR groups

Number of ITR groups 6 =

Location Identification Number (LIN), U.S. only

Number of digits 11 =

1 to HiPath 3000/5000 V7 R42 from HiPath 3000/5000 V8

3 Dependent on results from the performance tool




3000sb9.fm

A31003-H3580-Y100-10-7618, 01-2011



Overview of Additional Hardware

10.2 Overview of Additional Hardware

Table 10-1 System-Specific Maximum Configuration for UP0/E Workpoint Clients, Key

Modules, and AdaptersWorkpoint Clients, Add-On Devices, Adapt-

ersSYSTEM

HiPath38001

1 System load is greatly dependent on factors such as system configuration and traffic. Static rules on configuration inspec-

tion are therefore not suitable. As a guide, configurations that include UCD/ACD, more than one SLC16N, groups with

more than 10 stations or OpenScape Office connections should always be inspected using the project planning tool(https://enterprise-businessarea.siemens.com/productinfo/producthomepageservice.jsp?

mainTab=documents&view=spp&phase=design&toptPackageId=1030016044&pvid=281200).

HiPath3550

HiPath3500

HiPath3350

HiPath3300

optiPoint 500 telephones

● Number per system 384 722

2 8xUP0/E at the central board + 5xSLU8 + 1xSLMO24.

483


244

4 8xUP0/E at the central board + 2xSLU8.

245


● Number per box (the value in brackets ap-plies to operation using a PSUI)

192 – – – –

optiPoint acoustic adapters

Number per system No limit

optiPoint analog adapters

Number per system 116 246

6 If the total number of UP0/E stations, analog stations and additional stations connected using an adapter is greater than

72, a powerbox PB3000 must be used.

246 87

7 A UPSC-D/UPSC-DR must be used if the total number of UP0/E stations and stations connected using adapters is greater

than 24.

87

optiPoint recorder adapters

Number per system No limit

optiPoint ISDN adapters

Number per system 116 486 486 87 87

optiPoint phone adapters


optiPoint key modules


optiPoint BLF:

Number per system 12 6 6 – –

optiPoint application module:


https://enterprise-businessarea.siemens.com/productinfo/producthomepageservice.jsp?mainTab=documents&view=spp&phase=design&toptPackageId=1030016044&pvid=281200







A31003-H3580-Y100-10-7618, 01-2011


3000sb9.fm

Overview of Additional Hardware



3000sb10.fm

A31003-H3580-Y100-10-7618, 01-2011


Nur für den internen Gebrauch Output Formats for Call Detail Recording

11 Output Formats for Call Detail Recording

While the HiPath 3000/5000 systems are in operation, CDRC call details for each completed

section of a call or for each incoming call can be sent to a connected device on an ongoing ba-sis. This device is normally a PC, which evaluates the data received, or a printer.

Options for Exporting the Data to an External Output Device:

● Application programming interface (V.24)CDRC data is exported to call detail recording applications such as Teledata.

● PC attendant console portUsers can also forward the CDRC data to an optiClient Attendant (PC attendant consoleport). This transfers the call data to the Charge.dat file, which is created or updated when-

ever a new record is entered. You can use software to evaluate this data.● UP0/E port

● LAN interface (Ethernet)CDRC data can be exported to external applications via the LAN interface (Ethernet) (formore information, refer to section 4.8, “Applications over IP”).

Output Formats

The CDRC output can be in two different formats:

● Compressed format (via V.24/via LAN) for PC or call charge computerThe system outputs all data (including ACCT) without separating spaces, without headers,and without form feed. Call charge pulses, call charge amounts or arithmetic units are out-put.

● Long format for printerThe system outputs all data (except ACCT) separated by spaces, with header (in the lan-guage selected for the system) and form feed. The call charge amount is output.



Output Formats for Call Detail Recording Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011


3000sb10.fm





Identifying System Power Requirement Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011

A-2 HiPath 3000/5000 V8, System Description

3000sb11.fm

HiPath 3800 Boards Power Requirement

A.1 HiPath 3800 Boards Power Requirement

Table A-1 Nominal Output of the Power Supply UnitHiPath 3800

Power supply unit Part number Max. Nominal Output in W

5 V –48 V

Power Box PB3000 (incl.LUNA2)

C39165-A7027-A5-*1 withS30122-K7686-A1S30122-K7686-M1

1 Depending on version.

110.0

LUNA2 S30122-K7686-A1S30122-K7686-M1

1402

2 The total max. nominal output at the 5-V and at the –48-V output is 140 W. The 5-V nominal output can vary between 30

and 60 W and the –48-V nominal output can vary between 80 and 110 W. In other words, if 30 W are withdrawn at the 5-V output, a maximum of 110 W is available at the –48-Voutput.

>You must check whether the total power requirement of the boards used and theconnected workpoint clients of a system cabinet exceeds the maximum possibleLUNA2 output. Section A.7 contains a sample calculation.

Table A-2 Board Power Requirement HiPath 3800

Board or Component Part number Net Power Requirement inW

5 V –48 V

CBSAP S30810-Q2314-X 10.0 –

DBSAP S30807-Q6722-X 1.5 –

DIU2U S30810-Q2216-X 5.1 –

DIUN2 S30810-Q2196-X 5.0 –

DIUT2 S30810-Q2226-X100 3,5 –

IVMN8 S30122-H7688-X100 10.0 –

IVMNL S30122-H7688-X 10.0 –

REALS S30807-Q6629-X 1.5 –

SLCN S30810-Q2193-X300 5.0 –

SLMA S30810-Q2191-C300 1.6 12.0

SLMA8 S30810-Q2191-C100 0.6 4.0

SLMO2 S30810-Q2168-X10 1.0 1.2

SLMO8 S30810-Q2168-X100 0.4 0.4



3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011

HiPath 3000/5000 V8, System Description A-3

Nur für den internen Gebrauch Identifying System Power Requirement


STMD3 S30810-Q2217-X10 4.0 –

S30810-Q2217-X110 4.0 1.5

STMI2 S30810-Q2316-X100 16.3 –

TM2LP S30810-Q2159-Xxxx 1.8 –

TMANI8 S30810-Q2327-Xxx 1.8 –

TMC16 S30810-Q2485-X 1.3 –

TMDID S30810-Q2452-X 2.3 6.6

TMEW2 S30810-Q2292-X100 1.3 3.1

Table A-2 Board Power Requirement HiPath 3800


5 V –48 V




A31003-H3580-Y100-10-7618, 01-2011


3000sb11.fm



Nominal Output of the Power Supply Units HiPath 3550


5 V –48 V

UPSC-D S30122-K5660-A300S30122-K5660-M300

40.0 53.0


C39165-A7027-A5-*1 withS30122-K7686-A1S30122-K7686-M1


110.0

>You must check whether the total power requirement of the boards used and theconnected workpoint clients exceeds the maximum possible output of the UPSC-Dwith or without PB3000. Section A.7 contains a sample calculation.

Table A-3 Board Power RequirementHiPath 3550


5 V –48 V

BS3/1 S30807-H5482-X – 2.0

BS3/3 S30807-H5485-X – 3.0

CBCC (including submod-ules)

S30810-Q2935-A301 7.0 0.5

GEE12 S30817-Q951-Axxx 0.5 –

GEE16 S30817-Q951-Axxx 0.5 –

GEE50 S30817-Q951-Axxx 0.5 –

HXGS3 (including ventilatorkit)

S30810-Q2943-X 1 10.0 2.8

HXGS3 (excluding ventilatorkit)

S30810-Q2943-X1 10.0 –

IVMS8 S30122-Q7379-X 2.6 0.3

PDM1 S30807-Q5692-X100 – 5.0

SLA8N S30810-Q2929-X200 0.2 0.5

SLA16N S30810-Q2929-X100 3.0 3.0



3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011




SLA24N S30810-Q2929-X 4.5 4.5

SLAD4 S30810-H2956-X100 2.0 1.0

SLAD8 S30810-H2956-X200 2.0 1.0

SLAD16 S30810-Q2957-X 2.5 1.51

SLC16 S30810-Q2922-X 8.0 –

SLC16N S30810-Q2193-X100 5.0 –

SLMO24 S30810-Q2901-X 1.5 –

SLU8 S30817-Q922-A301 0.8 –

STLS2 S30817-Q924-B313 0.6 –

STLS4 S30817-Q924-A313 1.0 –

STRB S30817-Q932-A 0.5 –

TLA2 S30817-Q923-Bxxx 0.1 –

TLA4 S30817-Q923-Axxx 0.2 –

TLANI2 S30810-H2953-X1xx 0.1 –

TLANI4 S30810-H2953-Xxx 0.2 –

TLANI8 S30810-H2954-X1xx 0.2 –

TLA8 S30817-Q926-Axxx 0.4 –

TMCAS S30810-Q2938-X

TMGL4 S30810-Q2918-X 4.7 0.1

TMQ4 S30810-Q2917-X 3.8 –

TST1 S30810-Q2919-X 0.8 –

TS2 S30810-Q2913-X300 0.9 –

V24/1 S30807-Q6916-X100 0.3 – 4SLA S30810-Q2923-X200 0.7 0.7

8SLA S30810-Q2923-X100 1.3 1.3

16SLA S30810-Q2923-X 2.5 2.5

1 For each active station (off hook), the net resource requirement increases by approx. 1.6 W (dependant on the phone’s

cable length and DC resistance).



5 V –48 V




A31003-H3580-Y100-10-7618, 01-2011


3000sb11.fm



Table A-4 Nominal Output of the Power Supply Units HiPath 3350


5 V –48 V

PSUP S30122-K5658-M 15.0 19.2

UPSC-D S30122-K5660-A300S30122-K5660-M300

20.01

1 Nominal output = 40 W. Due to build-up of heat, not more than 20 W may be withdrawn.

53.0


C39165-A7027-A5-*2 withS30122-K7686-A1S30122-K7686-M1


110.0

>You must check whether the total power requirement of the boards used and theconnected workpoint clients exceeds the maximum possible output of the PSUP orthe UPSC-D with or without PB3000. Section A.7 contains a sample calculation.



5 V –48 V

BS3/1 S30807-H5482-X – 2.0

BS3/3 S30807-H5485-X – 3.0

CBCC (including submod-ules)

S30810-Q2935-A301 7.0 0.5

GEE12 S30817-Q951-Axxx 0.5 –

GEE16 S30817-Q951-Axxx 0.5 –

GEE50 S30817-Q951-Axxx 0.5 –

HXGS3 (including ventilatorkit)

S30810-Q2943-X 1 10.0 2.8

IVMP8 S30122-Q7379-X100 2.6 0.3

PDM1 S30807-Q5692-X100 – 5.0

SLAD4 S30810-H2956-X100 2.0 1.0

SLAD8 S30810-H2956-X200 2.0 1.0

SLAD16 S30810-Q2957-X 2.5 1.51



3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011




SLU8 S30817-Q922-A301 0.8 –

STLS2 S30817-Q924-B313 0.6 –

STLS4 S30817-Q924-A313 1.0 –

STRB S30817-Q932-A 0.5 –

TLA2 S30817-Q923-Bxxx 0.1 –

TLA4 S30817-Q923-Axxx 0.2 –

TLA4 S30817-Q923-Axxx 0.2 –

TLA8 S30817-Q926-Axxx 0.4 –

TLANI2 S30810-H2953-X1xx 0.1 –

TLANI4 S30810-H2953-Xxx 0.2 –

TLANI8 S30810-H2954-X1xx 0.2 –

TMGL4 S30810-Q2918-X 4.72 0.12

TMQ4 S30810-Q2917-X 3.8 –

V24/1 S30807-Q6916-X100 0.3 –

4SLA S30810-Q2923-X200 0.7 0.7

8SLA S30810-Q2923-X100 1.3 1.3

16SLA S30810-Q2923-X 2.5 2.5

1 For each active station (off hook), the net resource requirement increases by approx. 1.6 W (dependant on the phone’s

cable length and DC resistance).

2 Identified at a traffic flow of 0.8 Erlang



5 V –48 V




A31003-H3580-Y100-10-7618, 01-2011


3000sb11.fm





5 V –48 V

UPSC-DR S30122-K7373-A900S30122-K7373-M900

40.0 53.0


C39165-A7027-A5-*1 withS30122-K7686-A1S30122-K7686-M1


110.0

>You must check whether the total power requirement of the boards used and theworkpoint clients connected exceeds the maximum possible output of the UPSC-DRwith or without PB3000. Section A.7 contains a sample calculation.



5 V –48 V

BS3/1 S30807-H5482-X – 2.0

BS3/3 S30807-H5485-X – 3.0

CBRC (including submod-ules)

S30810-K2935-Z301 7.0 0.5

HXGR3 S30810-K2943-Z 10.0 –

IVMS8R S30122-K7379-Z 2.6 0.3

ventilatorHiPath 3500 – – 1.4

PDM1 S30807-Q5692-X100 – 5.0

SLAD8R S30810-K2956-X300 2.0 1.0

SLU8R S30817-K922-Z301 0.8 –

STLS4R S30817-K924-Z313 1.0 –

STRBR S30817-Q932-Z 0.5 –

TLA4R S30817-Q923-Zxxx 0.2 –

TLANI4R S30810-K2953-X2xx 0.2 –

TMGL4R S30810-K2918-Z 5.71 0.1



3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011




TST1 S30810-K2919-Z 0.8 –

TS2R S30810-K2913-Z300 0.9 –

8SLAR S30810-K2925-Z 1.3 1.3




5 V –48 V




A31003-H3580-Y100-10-7618, 01-2011


3000sb11.fm





5 V –48 V

UPSC-DR S30122-K7373-A900S30122-K7373-M900

20.01

1 Nominal output = 40 W. Due to build-up of heat, not more than 20 W may be withdrawn.

53.0

Powerbox PB3000 (incl.LUNA2)

C39165-A7027-A5-*2 withS30122-K7686-A1S30122-K7686-M1


110.0

>You must check whether the total power requirement of the boards used and theworkpoint clients connected exceeds the maximum possible output of the UPSC-DRwith or without PB3000. A sample calculation is shown in Section A.7.



5 V –48 V

BS3/1 S30807-H5482-X – 2.0

BS3/3 S30807-H5485-X – 3.0

CBRC (including submod-ules)

S30810-K2935-Z301 7.0 0.5

HXGR3 S30810-K2943-Z 10.0 –

IVMP8R S30122-K7379-Z100 2.6 0.3

ventilatorHiPath 3300 – – 1.4

PDM1 S30807-Q5692-X100 – 5.0

SLAD8R S30810-K2956-X300 2.0 1.0

SLU8R S30817-K922-Z301 0.8 –

STLS4R S30817-K924-Z313 1.0 –

STRBR S30817-Q932-Z 0.5 –

TLA4R S30817-Q923-Zxxx 0.2 –

TLANI4R S30810-K2953-X2xx 0.2 –



3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011



Workpoint Clients, Key Modules and Adapter Power Requirements

A.6 Workpoint Clients, Key Modules and Adapter PowerRequirements

An average power requirement is specified, which is identified at a traffic flow of 0.15 Erlang.

TMGL4R S30810-K2918-Z 5.71 0.1

8SLAR S30810-K2925-Z 1.3 1.3


Table A-10 Workpoint Clients, Key Modules and Adapter Power Requirements

Workpoint Client Net Power Requirement in W(from –48 V input)

OpenStage(connectionvariant CorNetIP)

OpenStage 20

0.01OpenStage 40

OpenStage 60

OpenStage 80

OpenStage(connectionvariant TDM)

OpenStage 100.85 W

OpenStage 20

OpenStage 40 1.1 W

OpenStage 600.02

OpenStage 80

OpenStage Key Module 0.02

OpenStage BLF 0.02

OpenStage PhoneAdapter 0.02



5 V –48 V




A31003-H3580-Y100-10-7618, 01-2011


3000sb11.fm


optiPoint 410

optiPoint 420

optiPoint 410 entry, optiPoint 410 entry S

0.01

optiPoint 410 economy,optiPoint 410 economy S

optiPoint 410 standard,optiPoint 410 standard S


optiPoint 420 economy,optiPoint 420 economy S

optiPoint 420 economy plus,optiPoint 420 economy plus S

optiPoint 420 standard,optiPoint 420 standard S


optiPoint self labeling key module

optiPoint 410 display module

optiPoint 500

optiPoint 500 entry 0.3optiPoint 500 economy (not for U.S.) 0.7

optiPoint 500 basic 0.7

optiPoint 500 standard,optiPoint 500 standard SL (for U.S. only)

0.7

optiPoint 500 advance 0.72

optiPoint key module 0.05

optiPoint BLF 0.02

optiPoint analog adapter 0.00

3

optiPoint ISDN adapter 0.7

optiPoint phone adapter 0.18

optiPoint acoustic adapter 0.25

optiPoint recorder adapter 0.3





3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011




optiPoint 600 office 0.01

Analog telephone (40 mA for short trunk) in active status 0.3

1 Power over Ethernet or power supplied locally

2 Power is provided by a local power supply.

3 A local power supply provides power to the connected analog telephone.







3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011



Check Whether the Output of a Power Supply Unit is Sufficient

● HiPath 3500 with UPSC-DRThe maximum nominal output at the –48 V output can be increased from 53 W to 140 W.

● HiPath 3300 with UPSC-DR

Due to build-up of heat, the 5 V output format can only be loaded with a maximum of 20 W.A maximum nominal output of 40 W is possible by using the powerbox PB3000. In addition,the maximum nominal output of the –48 V output increases from 53 W to 140 W.

Sample calculation for aHiPath 3550

1. Determine secondary power requirement at the 5 V output

The maximum nominal output of UPSC-D at the –5 V output amounts to 40 W and isenough to cover the specified power requirement.

power requirements of the boards/ components used =

7.00 W 1 x CBCC

10.00 W 1 x HXGS3 (including ventilatorkit)

0.90 W 1 x TS2

2.40 W 3 x SLU8

1.30 W 1 x 8SLA

5.00 W 1 x SLC16N

0.00 W 12 x BS3/1

= secondary power requirement at the5 V output =

26.60 W





3000sb11.fm

A31003-H3580-Y100-10-7618, 01-2011



Identifying the Primary System Power Requirement

A.8 Identifying the Primary System Power Requirement

Procedure

Proceed as follows to identify the primary power requirement of a system:

1. Determine overall secondary power requirement

2. Identifying primary power requirement

power requirements of the boards/components used

+ power requirement of connected workpoint clients (analog and digital telephones),key modules and adapters

= overall secondary power requirement

overall secondary power requirement

+ requirements of power supply units (UPSM = 30 W, PSUP/UPSC-D/UPSC-DR =12 W each)

+ PB3000 requirements (10 W each)

= the result should be multiplied by the factor 1.2 to allow for the degree of efficiency ofthe power supply.




A31003-H3580-Y100-10-7618, 01-2011


3000sb11.fm

Identifying the Primary System Power Requirement

Sample calculation for aHiPath 3550

1. Determine overall secondary power requirement

2. Identifying primary power requirement

The primary power requirement of HiPath 3550 with the expansion mentionedamounts to approximately 103.7 W .

power requirements of the boards/ components used =

7.50 W 1 x CBCC12.80 W 1 x HXGS3 (including ventilator

kit)

0.90 W 1 x TS2

2.40 W 3 x SLU8

2.60 W 1 x 8SLA

5.00 W 1 x SLC16N

24.00 W 12 x BS3/1

+ power requirement of connected work-point clients, key modules and adapt-ers =

4.32 W 6 x optiPoint 500 advance8.40 W 12 x optiPoint 500 basic

2.40 W 8 x optiPoint 500 entry

0.00 W 2 x Hicom Attendant BLF

0.00 W 2 x optiPoint BLF

0.40 W 8 x optiPoint key module

0.50 W 2 x optiPoint acoustic adapter

1.80 W 6 x analog workpoint clients

= overall secondary power requirement=

74.43 W

overall secondary power requirement=

74.43 W

+ UPSC-D requirement = 12.00 W

Allow for the degree of efficiency of thepower supply unit:

86.43 W x 1.2 = 103.7 W



3000sbIX.fm

A31003-H3580-Y100-10-7618, 01-2011

HiPath 3000/5000 V8, System Description Z-1

Nur für den internen Gebrauch Index

Index Z

AAccess points 7-1Access protection 4-56Access security 5-39Additional power supply 2-71Administration of Plus Products via PPP 5-8Administration options 5-2Administration via LAN 4-84Administration via PPP 5-6Alive monitoring 4-58

AMHOST 5-43Analog modem 5-35AP 1120 SIP 7-2AP 11x0 7-1APS transfer 5-14Archive file (.arc) 5-48Authentication 4-44Automatic callback 4-51Automatic time-dependent class-of-servicechangeover 1-5

BB channel modem 5-35Backing up system components 5-17Backup Manager 5-13, 5-17Bandwidth

management 4-46Bandwidth control 4-3Bandwidth requirement 4-3

additional services 3-10voice 3-9

Bandwidth requirementsadministration 3-10

Base stations 2-77battery cabinet BSG 48/38 2-17Board slots

HiPath 3300 2-62HiPath 3350 2-40HiPath 3500 2-51HiPath 3550 2-28

Boardscentral boards


peripheral boardsHiPath 3300 2-68HiPath 3350 2-46HiPath 3500 2-58HiPath 3550 2-35

power requirement A-1Bridging times

LUNA2 2-16

UPSC-D 2-33, 2-45UPSC-DR 2-56, 2-66BSG 48/38 2-17Busy Lamp Field 4-24

CCA 4-44Call charge allocation 4-52Callback 4-51, 4-52Capacities 10-1Capacity limits for UP0/E workpoint clients,

key modules, and adapters 10-11Capacity limits HiPath 3000/5000 2-3CAPI see vCAPI CBCC 2-30, 2-42CBRC 2-53, 2-64CDB backup 5-12CDRC via IP 4-73Central attendant console 4-23Central board


Central License Server (CLS) 1-32Certificates 4-45Certification authority 4-44Certification authority see CACHAP 4-51, 4-53CLI 4-59

see also command line



Index Nur für den internen Gebrauch

A31003-H3580-Y100-10-7618, 01-2011

Z-2 HiPath 3000/5000 V8, System Description

3000sbIX.fm

Clients for SPEsecure client 1-31standard client 1-31

CMA 2-73CMS 2-73CO call privileges 4-23Codecs 4-27Command line

see also CLI Command line interface see CLI Compliance 2-92

CE 2-92US and Canadian standards 2-92

Compression 4-27

data 4-39IP header 4-38CorNet IP 4-3CorNet N 4-24CSPL interface 6-10CSTA III ASN.1 6-10CSTA interface 1-9CSTA via IP 4-75CSTA-XML 6-10Customer database backup 5-12Customer License Agent (CLA) 1-32, 5-29

Customer License Manager (CLM) 1-32, 5-29

DDetermining system information 5-16Diagnostics options 5-18Digital modem 5-35Direct Station Select 4-24DISA internal 4-23Double key assignment 8-63DSA 4-44DSL 4-53, 4-54, 4-62, 5-11DTMF 4-27

EE.164 telephone number 2-90Echo (Voice over IP) 4-26Echo suppression 4-28Emergency number 1-20Emergency number prefix 1-20

Encoding, Voice over IP 4-26Encryption 1-30, 1-42Environmental conditions 2-93Error correction 5-32Error messages

HiPath 3000 5-31HiPath 5000 5-31

ESP 4-45Ethereal 4-58Event Viewer for HiPath 5000 5-27

error messages 5-31Eventlog for HiPath 3000 5-26

error messages 5-31Eventlog for HiPath 5000 5-27

error messages 5-31Extended connection 2-79

FFan kits 1-47Fax

DID number 4-49fax activation 4-49forwarding 4-49TAPI client 4-49vCAPI

faxing 4-49Fax over IP 4-31Fax over vCAPI 4-33Feature Server 3-2

trace files 5-25Features 6-7FEC procedure 4-32Firewall 4-51, 4-57Firewall functions 4-51

G

G server 6-12G servers 6-10G.711 4-27G.723.1 4-27G.729 4-27G.729A 4-27G.729AB 4-27Gadget servers 6-10gebeCom 6-12



3000sbIX.fm

A31003-H3580-Y100-10-7618, 01-2011



Gigaset M2 professional 8-95Gigaset S4 professional 8-94Gigaset SL3 professional 8-93

HH.225.0 4-18H.225.0 Q.931 4-18H.245 4-18H.323 4-2, 4-18H.323 client 4-46H.323 clients 4-46HG 1500

as Internet gateway 4-35management tools 4-59

protocols 4-18Hicom.pds 5-13HIP interface 4-58HiPath 3000 Manager E 4-59HiPath 3300 2-62HiPath 3350 2-40HiPath 3500 2-51HiPath 3550 2-27HiPath 3800 2-5HiPath 5000

Feature Server 3-2

HiPath Manager PCM Trace Monitor 5-25Presence Manager 3-4RAM requirements 3-6software structure 3-2

HiPath Attendant B 8-97HiPath ComScendo Service 1-2HiPath Cordless Office 2-77

base stations 2-77extended connection 2-79mobile telephones 8-93single-cell BS 2-77, 2-78system configuration 2-78tech. base station data 2-83

HiPath Fault Management 5-28HiPath Feature Access 4-34HiPath Inventory Manager 5-16

analysis 5-30HiPath Manager PCM Trace Monitor 5-25

HiPath Software Manageranalysis 5-30APS transfer 5-15backing up customer data 5-13

backing up system components 5-17determining system information 5-16

HTTP management applications 4-59

II/O sessions 1-9IMODC 5-35Insecure mode 4-42Integrated modem 5-35Interface-to-interface ranges 2-88

Internet 4-50Internet access 4-53Internet gateway 4-35Internet telephones 1-27Internet telephony 1-21, 1-27, 8-36, 8-37Internet Telephony Service Provider (ITSP)1-9

IP accounting 4-39IP address filter 4-37IP address mapping 4-55IP Control Protocol 4-38

IP firewall see firewall IP header, compression 4-38IP mobility enhancement 1-20IP networking 4-22, 4-71IP terminals 1-31IP trunking 4-64IP trunking see IP networking IP/IP e2e payload via enterprise proxy 1-22IPCP 4-38ISDN Message Decoder 5-24ITSP 1-9, 1-21

connections 1-21released ~ 1-21

JJitter buffer 4-28

KKeep Alive 4-58




A31003-H3580-Y100-10-7618, 01-2011


3000sbIX.fm

Key assignment 8-63

LLAN connection 4-1, 4-13

LAN connection via LIM 4-13LAN network 4-1LAN2 4-62, 5-11LAN-LAN and teleworking 4-51LAN-LAN connection 4-51Least cost routing 4-24License Management System 1-32Licensing 1-32

analysis 5-29License Management System 1-32

Licensing for SPE 1-30LIMS 2-19Local power supply 8-78LOG area 5-45, 5-48Loss of packets 3-12LUNA2

bridging times 2-16calculating the number required 2-18

MMAC address filter 4-38

Management information bases (MIB) 4-77Management tools 4-59Manager E see HiPath 3000 Manager E Mandatory message 4-32MIB 4-77, 4-79Middleware 6-1Migration 1-46MMC

replace 5-14Mobile telephones 8-93Modem via IP 4-34

Multi-gateway administration 4-60Multilink 4-38, 4-51, 4-53Music on Hold 4-24myAgent 1-13myAttendant 1-12myPortal 1-11myPortal for Outlook 1-12myReports 1-13

NName resolution 4-70NAT 1-25, 4-37

NAT traversal 1-25Network Address Translation (NAT) 1-25Network Address Translation see NAT Network protocols 4-2Networking 4-22Networking see IP networking Numbering plan 2-89Numbering scheme 4-49

OOpenScape Office

installation 1-14OpenScape Office HX 4-93

applications 1-11Fax Printer 1-12myAgent 1-13myAttendant 1-12myPortal 1-11myPortal for Outlook 1-12myReports 1-13

OpenScape Personal Edition 8-34OpenStage

accessories 8-30Gigabit variant 8-4Key Module 15 8-27Key Module 40, 60, 80 8-28OpenStage 10 8-5OpenStage 20 8-9OpenStage 30 8-11OpenStage 40 8-13OpenStage 60 8-15OpenStage 80 8-18

OpenStage BLF 8-28OpenStage PhoneAdapter 8-32Operating conditions 2-93optiClient Attendant 8-98optiPoint 410

add-on device configurations 8-60optiPoint 410 advance 8-47optiPoint 410 display module 8-59optiPoint 410 economy 8-41



3000sbIX.fm

A31003-H3580-Y100-10-7618, 01-2011



optiPoint 410 economy plus 8-43optiPoint 410 entry 8-39optiPoint 410 standard 8-45optiPoint self labeling key module 8-58

optiPoint 410 Sadd-on device configurations 8-60optiPoint 410 advance S 8-47optiPoint 410 display module 8-59optiPoint 410 economy plus S 8-43optiPoint 410 economy S 8-41optiPoint 410 entry S 8-39optiPoint 410 standard S 8-45optiPoint self labeling key module 8-58

optiPoint 420

add-on device configurations 8-60optiPoint 410 display module 8-59optiPoint 420 advance 8-55optiPoint 420 economy 8-49optiPoint 420 economy plus 8-51optiPoint 420 standard 8-53optiPoint self labeling key module 8-58

optiPoint 420 Sadd-on device configurations 8-60optiPoint 410 display module 8-59optiPoint 420 advance S 8-55

optiPoint 420 economy plus S 8-51optiPoint 420 economy S 8-49optiPoint 420 standard S 8-53optiPoint self labeling key module 8-58

optiPoint 500adapter

acoustic adapter 8-74analog adapter 8-73configurations 8-77ISDN adapter 8-75option bays (adapter slots) 8-72phone adapter 8-76recorder adapter 8-75

add-on device configuration 8-71BLF 8-70key module 8-69optiPoint application module 8-70telephones

advance 8-67

basic 8-66economy 8-66entry 8-64standard 8-67

optiPoint 600 office 8-61optiPoint accessories, part numbers 8-78optiPoint application module 8-70optiPoint Attendant 8-106optiPoint BLF 8-70optiPoint key module 8-69optiPoint WL2 professional 8-87Order of installation 6-9Output formats for call detail recording 11-1

PPAP 4-51, 4-53Password 5-39Payload resources 4-15Payload switching 4-46PB3000 2-71PBX routing 4-71PDS file 5-13Permit firewall 4-57PKI servers 4-46Possible configurations for the add-on devic-

es 8-29Power requirement (boards, workpoint cli-ents, adapter) A-1

Power supply 2-71Powerbox PB3000 2-71PPP 4-36

multilink 4-51, 4-53PPP connections 4-51

PPPoE 4-36, 4-53, 4-55PPTP 4-36, 4-53Presence Manager 3-4

trace files 5-25Privacy and Data Security 1-53Privacy Release key 1-8Protocols 4-2PSTN partner 5-9PSUP 2-44

QQoS 4-27, 4-60




A31003-H3580-Y100-10-7618, 01-2011


3000sbIX.fm

Quality assurance procedures 3-12Quality of Service 4-27, 4-60

R

RangesCorNet N/CorNet-NQ 2-88trunk connection 2-88

RAS 4-18Redundancy messages 4-32Redundancy procedure 4-32Remote administration 5-36Remote control 4-56Remote service 5-34Ringer signaling, varying 1-6

Router call number 5-6Routing 4-51, 4-70rpcap 4-58RSA 4-44RTCP 4-18RTP 4-18

SSAFETY International 2-92Second LAN 5-11Secure client 1-31

Security 4-56, 5-39Security associations 4-44Security associations see security associations

Security policy 4-43Service call via code 5-36Shift key 8-63Short-hold 4-38Signaling & Payload Encryption 1-30, 1-42Signaling encryption 1-30Signaling resources 4-15

Single-cell base station 2-77, 2-78SIP networking 4-2SIP protocol 8-87SIP terminals 1-27SIP, SIP-Q 4-2SIP-Q 4-2, 4-24SIRA 5-7Smartset 4-47SNMP 4-59, 4-77, 4-79, 5-28

messages 4-78traps 4-78

SPE upgrade 1-30SSL 4-42Standard client 1-31Static traffic capacity

HiPath 3300 2-63HiPath 3350 2-41HiPath 3500 2-52HiPath 3550 2-29HiPath 3800 2-13

Station diagnosis 5-22Station number verification 4-57Station status 5-22

STUN 1-25System administration, options 5-2System capacities 10-1System client 4-46System power requirement A-1System software upgrade 5-14System Speed Dialing 4-23

TTAPI 4-48TAPI 120/170 V2.0 6-1

TAPI clients 4-48TCP 4-19TDM terminals 1-31T-DSL 4-54Technical base station data 2-83Technical specifications 2-85, 2-92Telematics 4-47Telephones

interface to interface ranges 2-88Teleworking 4-51Terminal encryption 1-31Terminal test 5-26Toll restriction 4-23Trace options

Customer License Agent (CLA) 5-29Customer License Manager (CLM) 5-29HiPath 3000 5-24HiPath Inventory Manager 5-30HiPath Manager PCM Trace Monitor 5-25HiPath Software Manager 5-30



3000sbIX.fm


Traffic capacity (in erlangs)HiPath 3300 2-63HiPath 3350 2-41HiPath 3500 2-52

HiPath 3550 2-29HiPath 3800 2-13

Traffic statistics (Voice over IP) 4-26Traps 4-78Trunk diagnosis 5-21Trunk status 5-21Trunking see IP networking Tunnel 4-44

U

UDP 4-19, 4-32Updating HG1500 5-15Updating system software 5-15Upgrade Manager 5-15Upgrading the system software 5-14UPSC-D 2-32, 2-44

bridging times 2-33, 2-45UPSC DR 2 55 2 66

WWBM 4-59Web-based management 4-59Web-based management (WBM) 3-2Web-based management see WBM Whisper 1-7Wireshark (Ethereal) 4-58WLAN 8-87Workpoint client power requirement A-1

XX.509 4-44