Siemens Hipath 3000 5000 v7 Service Documentation

Documentation
HiPath 3000/5000 V7
IP Systems
Service Manual
A31003-H3570-S100-6-7620
Communication for the open minded
Siemens Enterprise Communications

www.siemens.com/open
Copyright © Siemens Enterprise
Communications GmbH & Co. KG 2008
Hofmannstr. 51, D-80200 München
Reference No.: A31003-H3570-S100-6-7620
The information provided in this document contains
merely general descriptions or characteristics of
performance which in case of actual use do not
always apply as described or which may change as
a result of further development of the products. An
Communication for the open minded obligation to provide the respective characteristics
shall only exist if expressly agreed in the terms of
contract. Subject to availability. Right of modifica-
Siemens Enterprise Communications tion reserved. The trademarks used are owned by
www.siemens.com/open Siemens Enterprise Communications
GmbH & Co. KG or their respective owners.
hp3hp5shTOC.fm
Nur für den internen Gebrauch Contents
Contents 0
1 Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Structure of this Electronic Service Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.3 Electrical Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.4 Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.4.1 Safety Information: Dangers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.4.2 Safety Information: Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.4.3 Safety information: Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.4.4 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
1.4.5 What To Do in an Emergency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.4.6 Reporting Accidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.4.7 Safety Information for Australia (For Australia Only) . . . . . . . . . . . . . . . . . . . . . 1-13
1.4.8 Safety Information for Brazil (for Brazil only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
1.5 Privacy and Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
1.6 Information on the Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
2 System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.2 Design and Dimensions of the HiPath 3000 Systems. . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.2.1 Design and Dimensions of HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.2.2 Design and Dimensions of HiPath 3550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.2.3 System Environment of the HiPath 3000 Systems . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.2.3.1 System Environment HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.2.3.2 System environment HiPath 3550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.3 HiPath 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2.4 System-Specific Capacity Limits for HiPath 3000, HiPath 5000 . . . . . . . . . . . . . . . . 2-17
2.5 Static Configuration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2.5.1 Resources and Capacity Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2.5.2 Gateway Channels (DSP Channels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
2.5.3 ITSP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
2.5.4 MOH Channels (G.711, G.723, G.729) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
2.5.5 IP Networking Channels (PBX Networking Channels) . . . . . . . . . . . . . . . . . . . . 2-24
2.5.6 Bandwidth Control for IP Networking Channels (PBX Networking Channels) . . 2-24
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual 0-1
hp3hp5shTOC.fm
Contents Nur für den internen Gebrauch
2.5.7 DMC (Direct Media Connection) Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

2.5.8 ISDN Routing/PPP Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.5.9 Fax/Modem Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
2.6 Dynamic Configuration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2.6.1 Dynamic Performance Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2.6.2 Thumb Rule for HiPath 3000/5000 V7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2.6.2.1 Procedural Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2.6.2.2 Planning Load for HiPath Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
2.6.2.3 Maximum Permissible Values for E-Doku Version 3.0 . . . . . . . . . . . . . . . . . 2-30
2.6.2.4 Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2.6.2.5 Current Thumb Rule Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
2.6.3 Thumb Rule for HG 1500 V3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
2.6.3.1 Procedural Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
2.6.3.2 Maximum Permissible Values for HG 1500 V3.0. . . . . . . . . . . . . . . . . . . . . . 2-36
2.6.3.3 Current Thumb Rule Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
2.6.4 Example for Using the Thumb Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
2.6.4.1 E-Doku Version 3.0 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
2.6.4.2 HG 1500 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
2.6.4.2.1 IP Trunking with TDM Terminal Points Only . . . . . . . . . . . . . . . . . . . . . . 2-42
2.6.4.2.2 IP Trunking and HFA Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
2.6.4.2.3 IP Trunking via LAN and WAN (ISDN/PPP) . . . . . . . . . . . . . . . . . . . . . . 2-44
2.6.4.2.4 IP Trunking with VPN (Voice Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
2.6.4.2.5 Standalone System with Home Offices connected via VPN . . . . . . . . . . 2-47
2.6.4.2.6 VPN Networking with Data and Voice Connections . . . . . . . . . . . . . . . . 2-49
2.6.4.2.7 IP Workpoint Clients for ISDN and ITSP Connection in HiPath 3800 . . . 2-51
2.6.5 Maximum Number of Devices for Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
2.7 Technical Specifications for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
2.8 Interface-to-Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
2.9 Country-specific ring frequencies for analog subscriber line modules . . . . . . . . . . . . 2-55
2.10 Numbering plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
2.10.1 Default Numbering for HiPath 3000/5000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
2.10.2 Internet Telephony Phone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
2.10.3 Numbering in networked systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
2.11 Technical Specifications and Compliance to HiPath 3000 . . . . . . . . . . . . . . . . . . . . 2-59
2.11.1 CE Compliance (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
2.11.2 Compliance with US and Canadian Standards (for U.S. and Canada only) . . . 2-59
2.11.2.1 FCC Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
2.11.2.1.1 FCC Rules, Part 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
2.11.2.1.2 FCC Rules, Part 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
2.11.2.2 Industry Canada Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
2.11.2.2.1 REN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
2.11.2.2.2 Equipment Attachment Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
2.11.3 SAFETY International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
2.12 Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
A31003-H3570-S100-6-7620, 2008-04-01
0-2 HiPath 3000/5000 V7, Service Manual
hp3hp5shTOC.fm
2.12.1 Electrical Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65

2.12.2 Mechanical Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
3 Boards for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2 Central boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3.2.1 CBCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3.2.2 CBRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
3.2.3 CBSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
3.2.4 CMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
3.2.5 CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
3.2.6 CUC and CUCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
3.2.7 CUP and CUPR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
3.2.8 DBSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
3.2.9 IMODN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
3.2.10 LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
3.2.11 LIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
3.2.12 LUNA2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
3.2.13 MMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
3.2.14 PSUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
3.2.15 RGMOD (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
3.2.16 UPSC-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
3.2.17 UPSC-DR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
3.3 Peripheral boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
3.3.1 CSAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
3.3.2 DIU2U (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
3.3.3 DIUN2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
3.3.4 HXGS3, HXGR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89
3.3.5 IVMNL, IVMN8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
3.3.6 IVMP4, IVMP4R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
3.3.7 IVMP8 (not for U.S.) and IVMP8R (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . 3-107
3.3.8 IVMS8, IVMS8R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
3.3.9 IVMS8N, IVMS8NR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
3.3.10 PBXXX (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
3.3.11 SLA8N (not for U.S.), SLA16N, SLA24N . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-131
3.3.12 SLAD4, SLAD8, SLAD8R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
3.3.13 SLC16N (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140
3.3.14 SLCN (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155
3.3.15 SLMAE8, SLMAE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-162
3.3.16 SLMA, SLMA8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-173
3.3.17 SLMA2 (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-182
3.3.18 SLMO2, SLMO8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-191
3.3.19 SLMO8 (not for U.S.), SLMO24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-201
3.3.20 SLU8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-207
3.3.21 SLU8R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-208
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
3.3.22 STLS2 (not for U.S.), STLS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-209

3.3.23 STLS4R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-216
3.3.24 STLSX2, STLSX4, STLSX4R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-218
3.3.25 STMD3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-223
3.3.26 STMI2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-229
3.3.27 TCAS-2 and TCASR-2 (for selected countries only) . . . . . . . . . . . . . . . . . . . . 3-235
3.3.28 TLA2 (Not for U.S.), TLA4 (Not for U.S.), TLA8 (not for U.S.) . . . . . . . . . . . . . 3-247
3.3.29 TLA4R (not for U.S.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-249
3.3.30 TM2LP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-251
3.3.31 TMAMF (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-258
3.3.32 TLANI2, TLANI4, TLANI8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-262
3.3.33 TLANI4R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-265
3.3.34 TMANI8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-268
3.3.35 TMC16 (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-276
3.3.36 TMCAS (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-281
3.3.37 TMCAS-2 (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-290
3.3.38 TMDID (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-299
3.3.39 TMDID2 (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-304
3.3.40 TMEW2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-312
3.3.41 TMGL4 (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-319
3.3.42 TMGL4R (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-321
3.3.43 TMQ4 (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-323
3.3.44 TST1 (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-325
3.3.45 TS2 (Not for U.S.), TS2R (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-327
3.3.46 4SLA (not for U.S.), 8SLA, 16SLA (Not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . 3-332
3.3.47 8SLAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-335
3.4 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-337
3.4.1 ALUM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-337
3.4.2 AMOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-341
3.4.3 ANI4 (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-343
3.4.4 ANI4R (for selected countries only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-347
3.4.5 Announcement and Music Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-349
3.4.6 EVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-352
3.4.7 EXMNA (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-354
3.4.8 GEE12 (not for U.S.), GEE16 (not for U.S.), GEE50 (not for U.S.) . . . . . . . . . . 3-356
3.4.9 HOPE (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-358
3.4.10 OPAL and OPALR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-360
3.4.11 PFT1 (not for U.S.), PFT4 (not for U.S.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-362
3.4.12 REALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-365
3.4.13 STBG4 (for France only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-370
3.4.14 STRB, STRBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-371
3.4.15 USB V.24 Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-376
3.4.16 V24/1 (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-377
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
3.4.17 V.24 Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-379

3.4.18 V.24 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-380
4 Installing HiPath 3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Installing HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.1 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.2.3 Installing HiPath 3800 (Standalone) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.2.3.1 Selecting the Installation Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.2.3.1.1 For U.S. only: AC outlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.2.3.2 Unpacking the Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.3.3 Setting up the System Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.2.3.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.2.3.3.2 Setting Up a Single Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.2.3.3.3 Stacking Two Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.2.3.3.4 Setting Up a Two-Cabinet System Side by Side . . . . . . . . . . . . . . . . . . 4-12
4.2.3.4 Grounding the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.2.3.4.1 Not for U.S.: Grounding the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.2.3.4.2 For U.S. Only: Grounding the System . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.2.3.5 Checking the Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.2.4 Installing HiPath 3800 (19-Inch Cabinet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.2.4.1 Selecting the Installation Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.2.4.1.1 For U.S. only: AC outlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4.2.4.2 Unpacking the Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4.2.4.3 Mounting System Cabinets in the 19-Inch Cabinet . . . . . . . . . . . . . . . . . . . 4-24
4.2.4.3.1 Mounting a System Cabinet using Support and Angle Brackets . . . . . . 4-24
4.2.4.4 Grounding the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4.2.4.5 Checking the Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.2.5 Installing Boards (Configuration Notes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.2.5.1 System factory default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.2.5.2 Board Slots in the Basic and Expansion Cabinet . . . . . . . . . . . . . . . . . . . . 4-31
4.2.5.3 Inserting or Removing Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.2.5.4 Mounting Connector Panels (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.2.5.5 Installing the SIVAPAC-SIPAC Board Adapter. . . . . . . . . . . . . . . . . . . . . . . 4-42
4.2.5.6 Initializing the Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
4.2.5.7 Distribution of the PCM Highway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
4.2.5.8 Static Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
4.2.6 Connecting the Cable to the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
4.2.6.1 Backplane of the Basic Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
4.2.6.2 Expansion Cabinet Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
4.2.6.3 Connecting Cables Between the Basic and Expansion Cabinet . . . . . . . . . 4-57
4.2.6.4 Connecting Peripherals to the SIVAPAC Connector on the Backplane . . . 4-58
4.2.6.5 Connecting Peripherals to the Connector Panels with RJ45 Jacks . . . . . . . 4-61
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
4.2.6.6 Connecting Peripherals to the Connector Panels

with CHAMP Jack (for U.S. only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
4.2.6.7 Connecting Peripherals to Connector Panels with SIPAC 1 SU Connectors 4-64
4.2.7 Using an External Main Distribution Frame or External Patch Panel . . . . . . . . . . 4-66
4.2.7.1 Using an External Main Distribution Frame MDFU-E S30805-U5283-X . . . . 4-67
4.2.7.1.1 Mounting the Main Distribution Frame (MDFU-E) . . . . . . . . . . . . . . . . . . 4-68
4.2.7.1.2 Laying the Line Network and Jumpers on the MDFU-E . . . . . . . . . . . . . 4-68
4.2.7.2 Inserting the External Patch Panel S30807K6143-X . . . . . . . . . . . . . . . . . . 4-72
4.2.7.2.1 Installing the Patch Panel in a 19-Inch Cabinet. . . . . . . . . . . . . . . . . . . . 4-73
4.2.7.2.2 Connecting the Line Network to the External Patch Panel . . . . . . . . . . . 4-74
4.2.7.3 Inserting External S0 Patch Panel C39104-Z7001-B3 . . . . . . . . . . . . . . . . . 4-76
4.2.7.3.1 Installing the S0 Patch Panel in the 19-Inch Cabinet. . . . . . . . . . . . . . . . 4-77
4.2.7.3.2 Connecting Lines to the External S0 Patch Panel . . . . . . . . . . . . . . . . . . 4-78
4.2.7.4 For U.S. only: Connecting Network Facilities. . . . . . . . . . . . . . . . . . . . . . . . . 4-80
4.2.8 Loading the System Software and Installing Subboards on the CBSAP . . . . . . . 4-81
4.2.9 Connecting Workpoint Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
4.2.10 Making Trunk and Networking Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
4.2.11 Performing a Visual Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
4.3 Installing HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300. . . . . . . . . . . . . 4-85
4.3.1 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
4.3.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
4.3.3 Installing HiPath 3550 and HiPath 3350. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
4.3.3.1 Selecting the Installation Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
4.3.3.1.1 For U.S. only: AC outlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
4.3.3.2 Unpacking the Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
4.3.3.3 Not for U.S.: Mounting the Main Distribution Frame (HiPath 3550 only) . . . . 4-90
4.3.3.4 Removing the System Housing Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
4.3.3.5 Attaching the System to the Wall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
4.3.3.6 Grounding the System and the Main Distribution Frame . . . . . . . . . . . . . . . . 4-95
4.3.3.7 Installing the Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
4.3.3.8 Laying the Line Network and Connection Cables . . . . . . . . . . . . . . . . . . . . . 4-99
4.3.3.9 Attaching Ferrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
4.3.3.10 Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105
4.3.3.11 Connecting Workpoint Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
4.3.3.12 Making trunk connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
4.3.3.13 Performing a Visual Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
4.3.4 Installing HiPath 3500 and HiPath 3300 (19-Inch Housing) . . . . . . . . . . . . . . . . 4-110
4.3.4.1 Installation Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
4.3.4.2 Selecting the Installation Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
4.3.4.2.1 For U.S. only: AC outlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
4.3.4.3 Unpacking the Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
4.3.4.4 Not for U.S.: Attaching a HiPath 3500 and HiPath 3300 to the Wall . . . . . . 4-113
4.3.4.5 Installing a HiPath 3500 or HiPath 3300 in a Cabinet . . . . . . . . . . . . . . . . . 4-114
4.3.4.6 Grounding the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
4.3.4.7 Installing the Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117

4.3.4.8 Connecting Cables and the Line Network . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
4.3.4.9 Configuration notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-120
4.3.4.10 Connecting Workpoint Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
4.3.4.11 Making trunk connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
4.3.4.12 Performing a Visual Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
5 Starting Up HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2 Starting Up HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2.1 Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2.2 Supplying the System with Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2.2.1 Assigning Station Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.2.3 Carrying Out a System Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.2.4 Carrying Out the Country Initialization and Selecting the Password Type . . . . . . 5-7
5.2.5 Not for U.S.: Entering the System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.2.6 Customer-Specific Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.2.7 Performing a System Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.3 Starting Up HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300. . . . . . . . . . . . . . 5-11
5.3.1 Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.3.2 Supplying the System With Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.3.2.1 Assigning Station Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.3.3 Carrying Out a System Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.3.4 Carrying Out the Country Initialization and Selecting the Password Type . . . . . 5-15
5.3.5 Not for U.S.: Entering the System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5.3.6 Customer-Specific Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.3.7 Performing a System Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
6 HiPath 5000 Startup and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.3 Software Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6.4 Notes on Open Numbering in a HiPath 3000/5000 Network . . . . . . . . . . . . . . . . . . . 6-7
6.5 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
6.6 HiPath 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
6.6.1 Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
6.6.2 Integrating the HiPath 5000 Server in the Customer LAN . . . . . . . . . . . . . . . . . 6-12
6.6.3 HiPath 5000 Installing Standard Components . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
6.6.3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
6.6.3.2 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
6.6.3.3 Starting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
6.6.4 Installing HiPath ComScendo Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
6.6.4.1 Checking the Installation of the HiPath ComScendo Service . . . . . . . . . . . 6-29
6.6.5 Installing HiPath Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
6.6.6 Installing the TAPI Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
6.6.7 Installing the HiPath Inventory Server Separately . . . . . . . . . . . . . . . . . . . . . . . 6-36
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
6.6.8 Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41

6.6.8.1 Verifying the Start and Function of HiPath 5000 Services . . . . . . . . . . . . . . . 6-41
6.6.8.2 Checking Entries in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
6.7 Modifying HiPath 5000 Components (Retro-Fitting, Updating, Deleting) . . . . . . . . . . 6-43
6.7.1 Version-Wide Upgrading of a HiPath 5000 Installation . . . . . . . . . . . . . . . . . . . . 6-44
6.8 Performing Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
6.9 Optimizing Operating System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
6.10 Perform HiPath 5000 Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
6.10.1 Configuring HiPath 5000 with HiPath ComScendo Service . . . . . . . . . . . . . . . 6-50
6.10.2 Reloading the HiPath ComScendo Service (if required) . . . . . . . . . . . . . . . . . . 6-51
6.10.3 Configuring HiPath 5000 RSM as a Central Admin. Unit in an IP Network . . . . 6-52
6.10.3.1 Creating a Central Customer Database for IP Networking . . . . . . . . . . . . . 6-52
6.10.3.2 Adding Individual Nodes for IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
6.11 HiPath Manager PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
6.12 GetAccount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
6.12.1 Parameters for Call Data Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
6.13 Connecting an Uninterruptible Power Supply to HiPath 5000 . . . . . . . . . . . . . . . . . 6-61
7 Starting HiPath 3000 as a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.3 Starting HiPath 3800 as a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.3.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.3.2 Procedure for Installation and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.4.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
7.5.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
8 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8.3 Licensing for HiPath 3000 Version 3.0, HiPath 5000 Version 3.0. . . . . . . . . . . . . . . . . 8-4
8.3.1 Products and Components subject to Mandatory Licensing . . . . . . . . . . . . . . . . . 8-4
8.3.2 Grace Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8.3.3 License Failure Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8.3.4 Performing Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
8.4 Licensing Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
8.4.1 HiPath 3000 as a Standalone System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
8.4.2 Networked HiPath 3000 Systems without HiPath 5000 RSM. . . . . . . . . . . . . . . . 8-15
8.4.3 Networked HiPath 3000 Systems with HiPath 5000 RSM . . . . . . . . . . . . . . . . . . 8-15
8.4.4 Upgrading to HiPath 3000 Version 3.0, HiPath 5000 Version 3.0 . . . . . . . . . . . . 8-18
8.4.5 Combining Standalone Systems (HiPath 3000) to Form a Network with HiPath
5000 RSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
8.4.6 Removing a Standalone System from a Network with HiPath 5000 RSM . . . . . 8-23
8.4.7 Replacing License-sensitive Hardware (Changing the MAC Address) . . . . . . . 8-24
8.5 Licensing optiClient Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
8.5.1 optiClient Attendant V8 Connected To HiPath 3000 V7 . . . . . . . . . . . . . . . . . . . 8-27
8.6 Protection Against License Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
9 Expanding and Upgrading HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
9.2 Expanding HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.2.1 Replacing Peripheral Boards for HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.2.2 Connecting a printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
9.2.3 Insert Power Cabinet PB3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
9.2.3.1 PB3000 Control, Display, and Connecting Elements . . . . . . . . . . . . . . . . . . . 9-6
9.2.3.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
9.2.3.3 Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
9.2.3.4 Technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
9.2.3.5 UPS bridging time/charging time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
9.2.3.6 Power Box PB3000 with batteries and LUNA2. . . . . . . . . . . . . . . . . . . . . . . 9-12
9.2.3.6.1 Installing Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
9.2.3.6.2 Install the LUNA2 power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
9.2.3.7 Wall mounting PB3000 (Not for USA:) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
9.2.3.8 PB3000 Cabinet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
9.2.4 Use ECR for HiPath 3500 and 3300 (not for USA and Canada). . . . . . . . . . . . . 9-21
9.2.4.1 ECR Control, Display, and Connecting Elements. . . . . . . . . . . . . . . . . . . . . 9-22
9.2.4.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
9.2.4.3 Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
9.2.4.4 Expansion Cabinet Rack ECR With Batteries . . . . . . . . . . . . . . . . . . . . . . . 9-25
9.2.4.4.1 Installing Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
9.2.4.5 Expansion Cabinet Rack ECR With Batteries and EPSU2-R. . . . . . . . . . . . 9-32
9.2.4.5.1 Connecting a Fan (if needed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
9.2.5 Connecting Special Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
9.2.5.1 Entrance Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
9.2.5.1.1 Information on Third-Party Entrance Telephones . . . . . . . . . . . . . . . . . 9-39
9.2.5.2 Connecting Speakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41
9.2.6 Use DCDR for HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
9.3 Upgrading HiPath 3000 to Version 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
9.3.1 Hardware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
9.3.2 Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
9.3.3 Instructions for Upgrading from V6.0 to V7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
9.3.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
9.3.3.2 Upgrading a HiPath 3000 Standalone System . . . . . . . . . . . . . . . . . . . . . . . 9-57
9.3.3.3 Upgrading a HiPath 5000 RSM Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
9.3.3.4 Upgrading a HiPath 3000 System Networked with Surpass. . . . . . . . . . . . . 9-59
9.3.3.5 Upgrading a HiPath 3000 System Networked with HiPath 2000 . . . . . . . . . 9-60
9.3.3.6 Upgrading a HiPath 3000 System Networked with HiPath 4000 . . . . . . . . . 9-61
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
9.3.4 Upgrade HiPath 3000 for Signalling & Payload encryption (SPE) . . . . . . . . . . . . 9-62
10 Workpoint Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
10.2 OpenStage Product Family (from V7 R3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
10.2.1 Gigabit variant of OpenStage terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
10.2.2 OpenStage terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
10.2.2.1 OpenStage 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
10.2.2.2 OpenStage 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
10.2.2.3 OpenStage 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
10.2.2.4 OpenStage 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
10.2.2.5 OpenStage 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
10.2.2.6 Connection and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
10.2.2.7 Connections on the Bottom of the Telephone . . . . . . . . . . . . . . . . . . . . . . 10-16
10.2.3 OpenStage Add-On Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
10.2.3.1 OpenStage Key Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
10.2.3.2 OpenStage BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
10.2.3.3 Possible Configurations for the Key Modules . . . . . . . . . . . . . . . . . . . . . . 10-23
10.2.4 Power supply of the OpenStage terminals, add-on devices, and adapters . . . 10-24
10.2.5 OpenStage Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
10.2.5.1 External Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
10.2.5.2 OpenStage PhoneAdapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
10.2.5.3 Acoustic Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
10.2.5.4 Headsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
10.2.5.5 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
10.2.5.6 USB Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
10.2.6 Updating Software for the TDM OpenStage Telephone Service . . . . . . . . . . . 10-36
10.2.6.1 Automatic and Manual Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
10.2.6.2 Accessing TDM OpenStage Hardware and Software Version Information 10-36
10.2.6.3 Accessing the TDM OpenStage Update Log File . . . . . . . . . . . . . . . . . . . 10-36
10.3 optiPoint 410 / optiPoint 410 S and optiPoint 420 / optiPoint 420 S . . . . . . . . . . . 10-37
10.3.1 optiPoint 410 and optiPoint 410 S Telephones . . . . . . . . . . . . . . . . . . . . . . . . 10-40
10.3.1.1 optiPoint 410 entry, optiPoint 410 entry S . . . . . . . . . . . . . . . . . . . . . . . . . 10-40
10.3.1.2 optiPoint 410 economy, optiPoint 410 economy S . . . . . . . . . . . . . . . . . . 10-42
10.3.1.3 optiPoint 410 economy plus, optiPoint 410 economy plus S . . . . . . . . . . 10-44
10.3.1.4 optiPoint 410 standard, optiPoint 410 standard S . . . . . . . . . . . . . . . . . . . 10-46
10.3.1.5 optiPoint 410 advance, optiPoint 410 advance S . . . . . . . . . . . . . . . . . . . 10-48
10.3.2 optiPoint 420 and optiPoint 420 S Telephones . . . . . . . . . . . . . . . . . . . . . . . . 10-50
10.3.2.1 optiPoint 420 economy, optiPoint 420 economy S . . . . . . . . . . . . . . . . . . 10-50
10.3.2.2 optiPoint 420 economy plus, optiPoint 420 economy plus S . . . . . . . . . . 10-52
10.3.2.3 optiPoint 420 standard, optiPoint 420 standard S . . . . . . . . . . . . . . . . . . . 10-54
10.3.2.4 optiPoint 420 advance, optiPoint 420 advance S . . . . . . . . . . . . . . . . . . . 10-56
10.3.3 Connection and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-58
10.3.3.1 Connections on the Bottom of the Telephone . . . . . . . . . . . . . . . . . . . . . . 10-59
10.3.4 Key programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
10.3.5 Key modules for optiPoint 410/410 S and 420/420 S . . . . . . . . . . . . . . . . . . . 10-62

10.3.5.1 optiPoint self labeling key module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
10.3.5.2 optiPoint 410 display module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
10.3.5.3 Possible Configurations for the Key Modules . . . . . . . . . . . . . . . . . . . . . 10-65
10.3.6 Use of optiPoint 500 Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-66
10.4 Central Administration of IP Workpoints via the System . . . . . . . . . . . . . . . . . . . . 10-67
10.4.1 Plug’n Play Startup of IP Workpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-68
10.4.2 Software Upgrade of IP Workpoints via the System . . . . . . . . . . . . . . . . . . . 10-69
10.5 optiPoint 150 S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-71
10.6 optiPoint 600 office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-74
10.7 optiPoint 500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-76
10.7.1 optiPoint 500 Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-77
10.7.1.1 optiPoint 500 entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-77
10.7.1.2 optiPoint 500 economy (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-78
10.7.1.3 optiPoint 500 basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-79
10.7.1.4 optiPoint 500 standard, optiPoint 500 standard SL (for U.S. only) . . . . . 10-80
10.7.1.5 optiPoint 500 advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-82
10.7.1.6 Connection Requirements for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . 10-84
10.7.1.7 Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-85
10.7.1.8 Connections on the Bottom of the Telephone . . . . . . . . . . . . . . . . . . . . . 10-86
10.7.1.9 USB 1.1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-87
10.7.1.10 Key programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-88
10.7.2 optiPoint 500 Add-On Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-89
10.7.2.1 optiPoint key module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-89
10.7.2.2 optiPoint BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-90
10.7.2.3 optiPoint application module (V5.0 SMR-06 and later) . . . . . . . . . . . . . . 10-91
10.7.2.4 Possible Configurations for the Key Modules . . . . . . . . . . . . . . . . . . . . . 10-92
10.7.3 optiPoint 500 Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-93
10.7.3.1 optiPoint analog adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-94
10.7.3.2 optiPoint ISDN adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-95
10.7.3.3 optiPoint phone adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-96
10.7.3.4 optiPoint acoustic adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98
10.7.3.5 optiPoint recorder adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-101
10.7.3.6 Possible optiPoint Adapter Configurations . . . . . . . . . . . . . . . . . . . . . . . 10-102
10.7.3.7 Comparison of optiset E adapters and optiPoint 500 adapters . . . . . . . 10-103
10.7.4 optiPoint 500 key modules and adapters power supply . . . . . . . . . . . . . . . . 10-104
10.7.5 Maximum Configuration for UP0/E Workpoint Clients,
Add-On Devices and Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-105
10.8 optiLog 4me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-107
10.9 optiset E privacy module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-108
10.10 optiPoint Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-109
10.10.1 External AC Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-109
10.10.1.1 Local Power Supply for optiset E, optiPoint 500, optiPoint 600 office . 10-109
10.10.1.2 Power supply unit for optiPoint 410/410 S and 420/420 S . . . . . . . . . . 10-111
10.10.2 Headsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-112
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
10.11 optiClient 130 V5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-115

10.12 HiPath AP 1120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-116
10.13 optiPoint WL2 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-117
10.14 Attendant console versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-118
10.14.1 OpenStage Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-118
10.14.2 optiPoint Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-118
10.14.3 optiClient Attendant V8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-119
10.15 Mobile Telephones for HiPath Cordless Office . . . . . . . . . . . . . . . . . . . . . . . . . 10-124
10.15.1 Gigaset SL1 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-124
10.15.2 Gigaset SL2 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-124
10.15.3 Gigaset M1 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-125
10.15.4 Gigaset M2 professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-126
10.15.5 Logging Mobile Telephones On To the System . . . . . . . . . . . . . . . . . . . . . . 10-127
10.15.5.1 Opening the HiPath 3000 Login Window . . . . . . . . . . . . . . . . . . . . . . . 10-127
10.15.5.2 Logging On the Mobile Telephone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-128
10.15.5.3 Checking the Login Status of the Mobile Telephones . . . . . . . . . . . . . . 10-129
10.15.5.4 Replacing, Locking, and Logging Off a Mobile Telephone . . . . . . . . . . 10-129
10.16 Analog Telephones for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-130
10.17 ISDN Term inals for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-131
11 HiPath Cordless Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
11.3 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
11.4 Technical Data for Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
11.5 Power-Related Capacity Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
11.6 Multi-SLC and System-Wide Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
11.7 Planning Notes for Networked HiPath 3000 Systems Featuring
Network-Wide Roaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
12 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12.2 Service and Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
12.2.1 Backing Up the Customer Database (CDB Backup) . . . . . . . . . . . . . . . . . . . . . 12-3
12.2.1.1 Customer Data Backup Without HiPath Software Manager . . . . . . . . . . . . 12-3
12.2.1.1.1 Automatic Customer Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
12.2.1.1.2 Manual Customer Data Backup with HiPath 3000 . . . . . . . . . . . . . . . . 12-5
12.2.1.2 Customer Data Backup with HiPath Software Manager . . . . . . . . . . . . . . . 12-6
12.2.1.3 CDB Treatment When Replacing Central HiPath 3000 Hardware. . . . . . . . 12-6
12.2.2 Effects of Hardware Changes on Customer Data . . . . . . . . . . . . . . . . . . . . . . . 12-8
12.2.2.1 Inserting and Removing HiPath 3000 Boards . . . . . . . . . . . . . . . . . . . . . . . 12-8
12.2.2.2 Exchanging Workpoint Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
12.2.3 Relocate/Transfer Application Processor Software (APS) . . . . . . . . . . . . . . . 12-11
12.2.3.1 APS Replacement/Transfer for HiPath 3000 Systems Without
HiPath Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
12.2.3.1.1 Transferring an APS of HiPath 3000 by Replacing the MMC . . . . . . . 12-11
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
12.2.3.1.2 APS transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

12.2.3.2 APS Transfer for HiPath 3000 Systems With HiPath Software Manager 12-15
12.2.4 Determine current system software version . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
12.2.5 Upgrading HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
12.2.6 Determining System Information and Installed Software Components
(HiPath Inventory Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
12.2.7 Backing Up System Components (Backup Manager) . . . . . . . . . . . . . . . . . . 12-18
12.2.8 HiPath User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
12.3 Guided Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
12.3.1 HG 1500 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
12.3.2 Diagnosis Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
12.3.2.1 Recording HiPath 3000 Board Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
12.3.2.1.1 Central Control Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
12.3.2.1.2 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
12.3.2.1.3 Peripheral Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
12.3.2.2 Recording HiPath 3000 Trunk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
12.3.2.3 Recording Station Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
12.3.2.4 Recording the Status of the HiPath 3000 V.24 Interfaces . . . . . . . . . . . . 12-27
12.3.2.5 Trace Options for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
12.3.2.6 HiPath Manager PCM Trace Monitor for HiPath 5000 . . . . . . . . . . . . . . . 12-29
12.3.2.6.1 HiPath Manager PCM Trace Monitor Applications. . . . . . . . . . . . . . . 12-29
12.3.2.6.2 Starting and Exiting the Trace Monitor. . . . . . . . . . . . . . . . . . . . . . . . 12-30
12.3.2.6.3 The Screen Layout of the Trace Monitor . . . . . . . . . . . . . . . . . . . . . . 12-31
12.3.2.6.4 General Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
12.3.2.6.5 Exporting Trace Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
12.3.2.7 Trace Options and Evaluations in Connection with SRTP . . . . . . . . . . . . 12-36
12.3.2.8 Eventlog for HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
12.3.2.9 Testing Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
12.3.2.10 Event Viewer for HiPath 5000 (Eventlog) . . . . . . . . . . . . . . . . . . . . . . . 12-38
12.3.2.11 HiPath 5000 State Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-40
12.3.2.12 HiPath Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-44
12.3.2.13 Licensing Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-45
12.3.2.13.1 Analysis Using Customer License Manager (CLM) . . . . . . . . . . . . . 12-45
12.3.2.13.2 Analysis Using Customer License Agent (CLA). . . . . . . . . . . . . . . . 12-45
12.3.2.14 Analysis Using HiPath Software Manager and
HiPath Inventory Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
12.3.3 HiPath 3000 Error Messages (Entries in the Eventlog for
HiPath 3000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
12.3.4 HiPath 5000 Error Messages (Event Viewer Entries for
HiPath 5000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73
12.4 Correcting Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87
12.4.1 Automatic Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87
12.4.2 Manual Error Correction Without HiPath 3000/5000 Manager E . . . . . . . . . . 12-87
12.4.3 Manual Error Correction With HiPath 3000/5000 Manager E . . . . . . . . . . . . . 12-88
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
12.5 Remote Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-89

12.5.1 HiPath 3000 Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-90
12.5.2 HiPath 5000 Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-91
12.5.3 Remote System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-91
12.5.3.1 Remote Administration of HiPath 3000 with
HiPath 3000/5000 Manager E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-91
12.5.3.2 DTMF Remote Administration of HiPath 3000. . . . . . . . . . . . . . . . . . . . . . 12-92
12.5.4 Remote Correction of System Software (APS). . . . . . . . . . . . . . . . . . . . . . . . . 12-92
12.5.5 Remote Error Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-93
12.5.6 Controlled Release of a Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . 12-94
12.5.7 Remote Administration and Access Using PPP . . . . . . . . . . . . . . . . . . . . . . . . 12-94
12.5.7.1 Remote System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-94
12.5.7.2 Remote Administration of Plus Products . . . . . . . . . . . . . . . . . . . . . . . . . . 12-94
12.5.7.3 Remote Error Signaling Using SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-95
12.6 Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96
12.6.1 Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96
12.6.1.1 User-Specific Logon for WBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96
12.6.1.2 Password Protection against Brute Force Attacks . . . . . . . . . . . . . . . . . . 12-99
12.6.1.3 Logon With User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
12.6.1.4 Pre-Determined User Groups and Their Access Rights . . . . . . . . . . . . . 12-102
12.6.1.5 System Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-104
12.6.1.6 Customer Data Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-105
12.6.2 Automatic Logging of Administration Procedures. . . . . . . . . . . . . . . . . . . . . . 12-106
12.6.2.1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-106
12.6.2.1.1 Format Identification and Command Entry . . . . . . . . . . . . . . . . . . . . 12-106
12.6.2.2 Issuing and Saving Log Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-109
13 IP Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
13.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
13.2 IP Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
13.2.1 General Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
13.2.2 H.323 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
13.2.3 Standards Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
13.2.4 QoS - Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
13.3 Network analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
A System Programming Codes (Expert Mode Codes) . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A.2 Accessing system administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
B Codes for Activating/Deactivating Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
C IP Protocols and Port Numbers Used with
HiPath 3000/5000 V7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
D Identifying System Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
D.1 HiPath 3800 Board Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

D.5 HiPath 3300 Board Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10
D.6 Workpoint Client, Add-On Device, and Adapter Power Requirements . . . . . . . . . . . D-12
D.7 Checking Whether the Output of a Power Supply Unit is Sufficient . . . . . . . . . . . . . D-15
D.8 Identifying the Primary System Power Requirement. . . . . . . . . . . . . . . . . . . . . . . . . D-18
E Notes for editing the file snmpd.cnf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E.2 Trap Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E.3 Community (Read/Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4
E.4 Consequences for the file snmpd.cnf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W-1
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shTOC.fm
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Nur für den internen Gebrauch Important Information
Overview
1 Important Information
1.1 Overview
Service Manual HiPath 3000/5000 V7: A31003-H3570-S100-6-7620, 2008-04-01
(ESHB.70.010.07.01.31)
Chapter contents
This chapter discusses the topics listed in the following table.
Topic
Structure of this Electronic Service Manual, page 1-2
Electrical Environment, page 1-4
Safety Information, page 1-5
● Safety Information: Dangers
● Safety Information: Warnings
● Safety information: Cautions
● General Information
● What To Do in an Emergency
● Reporting Accidents
● Safety Information for Australia (For Australia Only)
● Safety Information for Brazil (for Brazil only)
Privacy and Data Security, page 1-14
Information on the Intranet, page 1-16
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Important Information Nur für den internen Gebrauch

Structure of this Electronic Service Manual
1.2 Structure of this Electronic Service Manual
You can find information on complex configurations (e.g. the status for Internet tele-
> phony service providers) in the Administrator documentation HiPath 3000/5000,
Configuration Examples.
Content and target group

This Electronic Service Manual (sSHB) provides information about the different systems of Hi-
Path 3000/5000 V6.0 and later. The specifications contained therein only provide accompany-
ing information and do not replace training.
Warning
7 Only authorized service personnel are permitted to work on the system.
The information provided in this document contains merely general descriptions or character-
istics of performance which in case of actual use do not always apply as described or which
may change as a result of further development of the products. An obligation to provide the rel-
evant characteristics shall only exist if expressly agreed in the terms of contract. The trade-
marks used are the property of Siemens Enterprise Communications GmbH & Co. KG or the
respective owner.
Main topics of this manual

● Chapter 2, “System Data” provides information on the current HiPath 3000/5000 version
and associated systems (characteristics, construction, system environment, capacity lim-
its, technical data).
● Chapter 3, “Boards for HiPath 3000” describes all of the boards used for HiPath 3000.
The hardware information (such as connection cables and NT connections) is presented
for each board.
● The actions necessary for the standard installation (part of a standard system) of the dif-
ferent HiPath 3000 systems are described in Chapter 4, “Installing HiPath 3000”.
● The procedures for the startup of the individual HiPath 3000/5000 components are de-
scribed in Chapter 5, “Starting Up HiPath 3000”, Chapter 6, “HiPath 5000 Startup and
Administration” and Chapter 7, “Starting HiPath 3000 as a Gateway”.
● Chapter 8, “Licensing” provides information about the HiPath License Management.
● Information on supplementary equipment and expansions and on the procedure for up-
grading HiPath 3000 systems are part of Chapter 9, “Expanding and Upgrading HiPath
3000”.
● Chapter 10, “Workpoint Clients” contains the description of the workpoint clients sup-
ported.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Structure of this Electronic Service Manual
● Basic information about the operation of the HiPath Cordless Office are part of Chapter 11,
“HiPath Cordless Office”.
● Chapter 12, “Service” describes the optional service and maintenance tasks and pro-
vides support for error detection and troubleshooting.
● Introductory information on the subject of IP can be found in Chapter 13, “IP Fundamen-
tals”.
● The following appendices contain lists with programming codes, IP protocols, port num-
bers: Annex A, “System Programming Codes (Expert Mode Codes)”, Annex B,
“Codes for Activating/Deactivating Features”, and Annex C, “IP Protocols and Port
Numbers Used with HiPath 3000/5000 V7”.
● Annex D, “Identifying System Power Requirements” provides information about the re-
source requirements of the boards and components of the HiPath 3000 systems.
● Annex E, “Notes for editing the file snmpd.cnf” is aimed at users who have sufficient
knowledge of SNMP to modify trap destinations and community names on the HiPath Fault
Management Desktop.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Electrical Environment
1.3 Electrical Environment

HiPath telecommunication systems are approved for connection to TN-S power supply sys-
tems. They can also be connected to a TN-C-S power supply system in which the PEN con-
ductor is divided into a ground wire and a neutral wire. TN-S and TN-C-S systems are defined
in the IEC 60364-3 standard.
If work needs to be done on the low-voltage network, this must be carried out by a qualified
electrician. When installing and connecting the HiPath PABXs, the IEC 60364-1 and IEC
60364-4-41 norms or corresponding legal norms or national requirements must be observed,
e.g. in the USA/Canada.
The device conforms to the EU directive 1999/5/EG, as attested by the CE

mark.
This device has been manufactured in accordance with our certified envi-
ronmental management system (ISO 14001). This process ensures that en-
ergy consumption and the use of primary raw materials are kept to a mini-
mum, thus reducing waste production.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Safety Information
1.4 Safety Information

The following information is intended for authorized service personnel. Only authorized service
personnel are permitted to install and maintain the system.
Observe all safety regulations and read the warnings, cautions, and notes posted on the equip-
ment. Familiarize yourself with emergency numbers.
Always consult a supervisor before starting work in conditions where the necessary safety pre-
cautions do not appear to be in place (such as in humid conditions or situations where there is
a risk of gas explosions).
Safety symbols
This manual uses the following symbols to indicate potential hazards:
Danger
7 This symbol warns that a situation may cause death or serious injury.
Warning
7 This symbol indicates hazards which may lead to serious injury.
Caution
7 This symbol indicates a risk of damage to hardware or software.
This symbol identifies useful information.

>
Additional symbols identifying sources of potential hazard
The following symbols are not generally used in the manual. They explain symbols that may
appear on equipment.
1 5 3 0 6 4 2
Electricity Weight Heat Fire Chemicals ESD* Laser
* electrostatically sensitive devices
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Safety Information
1.4.1 Safety Information: Dangers
Grounding
Never operate systems that require a ground wire connection without a ground wire connected.
Connect the system to the ground wire correctly before starting up and connecting the stations.
Connecting an external battery pack, external batteries

Only use licensed battery packs and batteries.
HiPath 3500 and HiPath 3300 systems

Potentially hazardous circuits are accessible in HiPath 3500 and HiPath 3300 19-inch systems.
These systems should therefore only be operated with closed housing.
Dangerous voltages
Voltages above 30 Vac (alternating current) or 60 Vdc (direct current) are dangerous.
Damage
● Replace the power cable immediately if it shows any signs of damage.
● Replace any damaged safety equipment (covers, labels and protective cables) immediate-
ly.
Accessories
Use only original accessories or components approved for the system. Failure to observe these
instructions may damage the equipment or even violate safety and EMC regulations.
System shutdown during maintenance work

Procedures to be observed are described in the relevant chapters.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Safety Information
Working on electrical circuits

● Work on low-voltage electrical networks (100 to 240 Vac) must only be carried out by qual-
ified personnel or authorized electrical engineers.
● Do not work alone. Work with another person who knows the locations of the power-off
switches.
● Never touch live wires that are not properly insulated.
● Ensure that a machine cannot be powered on from another source or controlled from a dif-
ferent circuit breaker or disconnecting switch.
● Before starting any work, check whether the corresponding circuits are still on power. Nev-
er take it for granted that all circuits have reliably been disconnected from the power supply
when a fuse or a main switch has been switched off.
● Use caution when installing or modifying telephone lines. Never install telephone wiring
during an electrical storm.
● Expect leakage current from the telecommunications network.
● When performing work on an open system, ensure that it is never left unsupervised.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Safety Information
1.4.2 Safety Information: Warnings
Replacing the lithium battery

There is a risk of explosion if a lithium battery is not correctly replaced. It must only be replaced
by an identical battery or one recommended by the manufacturer.
Replacing the batteries (DC power supply)

Procedures to be observed are described in the relevant chapters.
Protective clothing and equipment

● Do not wear loose clothing; tie back your hair while working on machines.
● Never wear rings, watches, and other jewelry or even clothing with metal coating or rivets
when working with electrical circuits and components. These could cause injury and short
circuits.
● Wear eye protection when you are working in any conditions that might be hazardous to
your eyes.
● Always wear a hard hat where there is a risk of injury from falling objects.
General safety
● The surface of a mirror is conductive. Do not touch powered circuits with a mirror. To do so
can cause personal injury and machine damage.
● Disconnect all power before working near power supplies unless otherwise instructed by a
maintenance procedure.
● Do not attempt to lift objects that you think are too heavy for you.
● Never look directly at a laser beam.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Safety Information
1.4.3 Safety information: Cautions
Voltage checks and measurements

● Check the nominal voltage set for the equipment (operating instructions and type plate).
● High voltages capable of causing shock are used in this equipment. Be extremely careful
when measuring high voltages and when servicing cards, panels, and boards while the
system is powered on.
Damage
Only use tools and equipment which are in perfect condition. Do not use equipment with visible
damage.
Protecting electrostatically sensitive devices (ESD)

To protect electrostatically sensitive devices (ESD):
● Wear a wristband before carrying out any work on PC boards and modules.
● Transport PC boards only in electrostatic packaging.
● Always place PC boards on a grounded surface before working on them.
● Only use grounded soldering irons.
Laying cables
Lay cables so as to prevent any risk of them being damaged or causing accidents, such as trip-
ping.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Safety Information
1.4.4 General Information
Connecting lines
● All cables and lines leaving a system cabinet must be shielded between the connection
point in the cabinet and, at the very least, the point at which they leave the cabinet.
Use a clip and pressure screw to contact all braided shields to the cabinet outlet. This also
applies to continuously connected service equipment.
● Connect all cables to the specified connection points only.
Location of safety equipment

When the installation or maintenance is completed, replace all safety equipment in the correct
location.
Checking tools
Check your tools regularly. Only use intact tools.
Closing the housing cover

After maintenance and testing work has been completed, close all housing covers.
Condensation
Condensation may form if equipment is brought onto the operating premises from a cold envi-
ronment. Wait until the temperature of the equipment has adjusted to the ambient temperature
and is completely dry before starting it up.
Wall mounting
Some walls (such as plasterboard walls) have a reduced load-bearing capacity. Before starting
wall mounting, check the load-bearing capacity of the walls.
Fire protection and EMC requirements

To ensure the legal fire protection and EMC requirements, operate the HiPath systems only
when closed. You may open the system only briefly for assembly and maintenance work.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Safety Information
Flammable materials
● Do not store combustible gases or flammable materials in cabinets near the equipment in-
stallation site.
● Do not store documents, descriptions, operating instructions, and similar flammable mate-
rials in the cabinet.
Workplace hazards
● Ensure that the workplace is well lit.
● A neat workplace helps reduce the risk of accidents.
Disposal of electrical/electronic devices and batteries
All electrical and electronic products should be disposed of separately from

the municipal waste stream via designated collection facilities appointed by
the government or the local authorities.
The correct disposal and separate collection of your old appliance will help
prevent potential negative consequences for the environment and human
health. It is a precondition for reuse and recycling of used electrical and elec-
tronic equipment.
For more detailed information about disposal of your old appliance, please
contact your city office, waste disposal service, the shop where you pur-
chased the product or your sales representative.
The statements quoted above are only fully valid for equipment which is in-
stalled and sold in the countries of the European Union and is covered by the
directive 2002/96/EC. Countries outside the European Union may have other
regulations regarding the disposal of electrical and electronic equipment.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Safety Information
1.4.5 What To Do in an Emergency
Actions in emergencies
● Remain calm in the event of an accident.
● Disconnect the power before touching the victim.
● If you do not know how to disconnect the power, use a nonconducting object, such as a
wooden broom handle, to push or pull the victim away from electrical contact.
First aid
● Be familiar with first aid for electrical shock. Familiarity with the various resuscitation meth-
ods required for breathing/heartbeat restoration and burn treatment are essential in emer-
gencies of this kind.
● Administer resuscitation immediately if the person is not breathing (mouth-to-mouth or
mouth-to-nose).
● If you are trained and certified, administer cardiac compression if the heart is not beating.
Calling for help

Immediately call an ambulance or the emergency doctor. Give details of the accident in the fol-
lowing order:
● Where did the accident happen?
● What happened?
● How many people were injured?
● What type of injuries were sustained?
● Be prepared to assist the emergency services with any supplementary information they
may require.
1.4.6 Reporting Accidents

● Report all accidents, “near accidents”, and possible hazards to your manager to ensure
their causes are resolved as soon as possible.
● Report any electric shock, no matter how minor.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Safety Information
1.4.7 Safety Information for Australia (For Australia Only)

● Music on Hold and paging devices must be connected to the HiPath 3000 system via an
ACA approved Line Isolation Unit.
● HiPath 3550 and HiPath 3350 must be installed near the mains socket outlet, which is pow-
ering the system. The mains socket shall be readily accessible. Integrity of the main socket
must be assured.
● HiPath 3000 and HiPath 5000 may only be installed and maintained by authorized service
personnel.
● HiPath 3550 and HiPath 3350 must be earthed with a separate bonding earth, if the sys-
tems are powered by a UPS.
● CE (customer equipment) does not continue to support emergency dialing after loss of
mains power, if battery back up and power fail switchover to emergency analogue phones
is not available.
● HiPath 3000/5000 must always be programmed to allow the dialing of emergency numbers
(for example 000).
1.4.8 Safety Information for Brazil (for Brazil only)

The use of the outlet strip with overvoltage protection with part number C39334-Z7052-C31 is
absolutely mandatory. The AC power of the HiPath 3000 systems must be conducted through
the outlet strip with overvoltage protection.
It is absolutely necessary to use a shielded Ethernet cable for LAN interfaces/ports of the
HXGS3 board.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Privacy and Data Security
1.5 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, including
those 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 privacy
based 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.
The customer is responsible for ensuring that the system is installed, operated, and
> maintained in compliance with the applicable data protection, labor, and labor pro-
tection laws.
Guidelines applicable to employees of

Siemens Enterprise Communications GmbH & Co. KG
Employees of Siemens Enterprise Communications GmbH & Co. KG are bound to safeguard
trade secrets and personal data under the terms of the company’s work rules.
In order to ensure that the statutory requirements during service – whether on-site or remote –
are consistently met, you should always observe the following regulations. This safeguards the
interests of the customer and 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 an
unauthorized person orally or in writing.
● Ensure that no unauthorized person can ever process (store, modify, transmit, disable or
delete) or use customer data.
● Prevent unauthorized persons from gaining access to data media (such as backup dis-
kettes or log printouts). Access should also be prevented during service calls as well as
when storing and transporting data.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Privacy and Data Security
● Ensure that data media which are no longer required are completely destroyed. Ensure
that documents are not generally available.
● Work closely with your customer contact; this promotes trust and reduces your workload.
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

Information on the Intranet
1.6 Information on the Intranet

Up-to-the-minute information on important topics is available on the
Siemens Enterprise Communications GmbH & Co. KG intranet. Here is a selection:
Table 1-1 Information on the Intranet
Contents Languages URL

Product Overview German http://opus1.mchh.siemens.de:8080/
Product descriptions English TopNet/index.html
Electronic Documentation on SEN German https://intranet.com.siemens.de/
ESY Products English techdoc
Selection and download of the fol- French
lowing: Italian
● Operating manuals Dutch
● Administrator documentation Portuguese
● Service documentation Spanish
● Sales documentation
List of “Frequently Asked Ques- German https://vd.icn.siemens.de/cfdocs/faq/
tions (FAQ)” in the VD portal start.cfm
Questions and answers for HiPath
customer scenarios: keyword
"Solutions_Products_Services"
Knowledge Management for Oper- English https://kmoss.icn.siemens.de/
ational Support and Services livelink/livelink.exe
KMOSS
Platform for the provision of service
information (successor to the Service
Information System, SIS):
● Tips & Tricks
● Service information sorted ac-
cording to products
TAC Advisor English http://tac.fld.rolm.com/
Technical Assistance Center for en-
terprise and network partners:
● Downloads
● Software Maintenance Releases
(SMR)
● Configuration notes and alerts
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm
Table 1-1 Information on the Intranet
Contents Languages URL

Back Level Support BLS German https://bls.icn.siemens.at/en/
Product information for the products English service_solutions/
supported by BLS. product_information/
product_information_content.cfm
Setting up tracing for the Feature German https://kmoss.icn.siemens.de/
server English livelink/livelink.exe/view/INF-02-
Configuration notes and procedures 000326
A31003-H3570-S100-6-7620, 2008-04-01
inform.fm

A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Nur für den internen Gebrauch System Data
Overview
2 System Data
2.1 Overview
Chapter contents
Topic
HiPath 3000, page 2-3
● Introduction, page 2-3 (electrical environment, systems)
● Design and Dimensions of the HiPath 3000 Systems, page 2-4:
– Design and Dimensions of HiPath 3800
● System Environment of the HiPath 3000 Systems, page 2-10:
– System Environment HiPath 3800
– System environment HiPath 3550
System-Specific Capacity Limits for HiPath 3000, HiPath 5000, page 2-17
Static Configuration Rules, page 2-19
● Resources and Capacity Limits, page 2-19
● Gateway Channels (DSP Channels), page 2-21
● ITSP Connection, page 2-23
● MOH Channels (G.711, G.723, G.729), page 2-23
● IP Networking Channels (PBX Networking Channels), page 2-24
● Bandwidth Control for IP Networking Channels (PBX Networking Channels), page 2-24
● DMC (Direct Media Connection) Channels, page 2-25
● ISDN Routing/PPP Channels, page 2-25
● Fax/Modem Channels, page 2-26
Dynamic Configuration Rules, page 2-27
● Dynamic Performance Characteristics, page 2-27
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
System Data Nur für den internen Gebrauch

Overview
Topic
● Thumb Rule for HiPath 3000/5000 V7, page 2-27
● Thumb Rule for HG 1500 V3.0, page 2-36
● Example for Using the Thumb Rule, page 2-41
● Maximum Number of Devices for Special Cases, page 2-52
Technical Specifications for HiPath 3000, page 2-53
Interface-to-Interface Ranges, page 2-54
Numbering plan, page 2-57
Technical Specifications and Compliance to HiPath 3000, page 2-59
● CE Compliance (not for U.S.), page 2-59
● Compliance with US and Canadian Standards (for U.S. and Canada only), page 2-59
● SAFETY International, page 2-64
Environmental Conditions, page 2-65
● Electrical Operating Conditions, page 2-65
● Mechanical Operating Conditions, page 2-65
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 3000
2.2 HiPath 3000
2.2.1 Introduction
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.12).
HiPath 3000 systems

This service manual contains information on all HiPath 3000 systems. Information on marketing
individual models in different countries can be obtained at the responsible locations.
● System for standalone installation and for installation in 19-inch cabinets:
– HiPath 3800
● Systems for wall mounting:
– HiPath 3550
– HiPath 3350
● Systems for installation in 19-inch cabinets
– HiPath 3500
– HiPath 3300
Information on the capacity limits of the different HiPath 3000 systems is provided in Table 2-6.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 3000
2.2.2 Design and Dimensions of the HiPath 3000 Systems
2.2.2.1 Design and Dimensions of HiPath 3800
Two configurations
Depending on the requirements, HiPath 3800 can be used as:
● a single-cabinet system (basic cabinet BC)
● a two-cabinet system (BC + expansion cabinet EC)
Design
The basic cabinet BC has nine slots and the expansion cabinet EC has thirteen slots for pe-
ripheral boards. The common control board CBSAP has a fixed slot (slot 6, only in the BC).
Depending on your requirements, up to three LUNA2 power supply units can be used in the
basic cabinet BC and up to four in the expansion cabinet EC.
Peripheral devices can be connected to the HiPath 3800 in a number of different ways:
● SIVAPAC connectors are available on the backplane for connecting the external main dis-
tribution frame MDFU-E using CABLUs (prefabricated cabling units) or to connect external
patch panels.
● Connector panels with RJ45 jacks for connecting the peripheral device directly. The con-
nector panels are clipped onto the SIVAPAC connectors on the backplane.
● For U.S. only: connector panels with CHAMP jack for connecting the peripheral device di-
rectly. The connector panels are clipped onto the SIVAPAC connectors on the backplane.
● Connector panels with SIPAC 1 SU connectors for connecting the external main distribu-
tion frame MDFU-E or external patch panels using CABLUs. The connector panels are
clipped onto the SIVAPAC connectors on the backplane.
The type of connection used will be decided in consultation with the customer on conclusion of
the agreement. The cabinets will be delivered accordingly with or without clipped-on connector
panels.
Two installation options

HiPath 3800 is suitable for installation both as a standalone system and in a 19-inch cabinet.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 3000
Dimensions
approx. 440 mm
EC
approx. 980 mm
BC approx. 430 mm
Figure 2-1 HiPath 3800 Dimensions
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 3000
Design
The housing intended for wall mounting (Figure 2-2) HiPath 3550 contains one shelf with six
slot levels. The slot levels (shown in Figure 4-59), numbered in ascending order from the at-
tachment side, have the following assignments:
● Slot levels 1-3: peripheral boards (two slots per level)
● Slot level 4: CBCC control board only
● Slot level 5: SIPAC slot
● Slot level 6: optional boards (up to 5 modules)
The power supply is on the rear panel of the subrack.
The connection cables to the peripherals (telephones, trunk connections etc.) can be connect-
ed directly. Use an external MDFU in certain situations (CMI).
Dimensions
460 mm Mounting
surface
450 mm
200 mm
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 3000
Design
The housing intended for wall mounting (Figure 2-3)HiPath 3350 contains one shelf with three
slot levels. The slot levels (shown in Figure 4-62), numbered in ascending order from the at-
tachment side, have the following assignments:
● 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 connection cables to
the peripherals (telephones, trunk connections etc.) are directly connected to the boards.
Dimensions
460 mm Mounting
surface
450 mm
128 mm
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 3000
Design
The housing intended for use with 19-inch cabinets (Figure 2-4) HiPath 3500 contains four slot
levels with the following assignments (represented in Figure 4-67):
● Slot levels 1-3: slide-in shelves for peripheral boards (2 boards can be plugged in on each
level)
● Slot level 4: slide-in shelf for CBRC control board
Connection to the peripherals (telephones, trunk connections, etc.) is set up via RJ45 jacks on
the board’s front panel.
Dimensions
440 mm
155 mm
380 mm
Necessary height units for 19-inch cabinet assembly: 4

(one height unit corresponds to approx. 1.7’’=43 mm)
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 3000
Design
The housing intended for use with 19-inch cabinets (Figure 2-5)HiPath 3300 contains three
slots with the following assignments (represented in Figure 4-68):
● Slot level 1: slide-in shelves for two peripheral boards
● Slot level 2: slide-in shelf for CBRC control board
Connection to the peripherals (telephones, trunk connections, etc.) is set up via RJ45 jacks on
the board’s front panel.
Dimensions
440 mm
88 mm
380 mm

A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 3000
2.2.3 System Environment of the HiPath 3000 Systems
2.2.3.1 System Environment HiPath 3800
Table 2-1 Boards for HiPath 3800
HiPath 3800
Subscriber Line Modules Central Boards Trunk Boards
Options
ROW U.S. ROW U.S. ROW U.S.
IVMN8 CBSAP DIU2U
IVMNL CMS DIUN2
SLCN DBSAP PBXXX1
SLMA IMODN STMD3
SLMA21 LIMS STMI2
SLMA8 LUNA2 TMANI8
SLMO2 MMC TMC161
SLMO8 MPPI TMCAS-21
STMD3 PDMX2 TMDID
STMI2 PFT1/PFT4 TMEW2
SLMAE REALS TMDID2
SLMAE8 RGMOD1 TM2LP
1 for selected countries only
2 used on the STMI2 board.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 3000
2.2.3.2 System environment HiPath 3550
HiPath 3550
Options
HXGS3 CBCC HXGS3
IVMS8 CMA STLS2
SLA8N CMS STLS4
SLA16N CUC STLSX2
SLA24N IMODN STLSX4
SLC16N LIM TCAS-21
SLMO24 MMC TLA2
SLU8 UPSC-D TLA4
STLS2 TLA8
STLS4 ALUM4 TMQ4
STLSX2 ANI41 TMCAS1
STLSX4 EVM TLANI2
4SLA EXM TLANI4
TLANI8
8SLA EXMNA TS2
16SLA GEE12 TST1
SLAD4 GEE16
SLAD8 GEE50
UAM
MPPI
OPAL
PDM1
STBG42
STRB
V24/1
2 Only for France
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 3000

HiPath 3350
Options
HXGS3 CBCC HXGS3
IVMP8 CMA STLS2
IVMS8 CMS STLS4
SLU8 CUP STLSX2
STLS2 IMODN STLSX4
STLS4 LIM TLA2
STLSX2 MMC TLA4
STLSX4 PSUP TLA8
4SLA UPSC-D TLANI2
8SLA ALUM4 TLANI4
TLANI8
16SLA ANI41 TMQ4
SLAD4 EVM
SLAD8 EXM
EXMNA
GEE12
GEE16
GEE50
UAM
MPPI
OPAL
PDM1
STBG42
STRB
V24/1
2 Only for France
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 3000
HiPath 3500
Options
HXGR3 CBRC HXGR3
IVMS8R CMA STLS4R
SLU8R CMS STLSX4R
STLS4R CUCR TCASR-21
STLSX4R IMODN TMGL4R
8SLAR LIM TST1
SLAD8R MMC TS2R
UPSC-DR TLA4R
TLANI4R
ANI4R1
EVM
EXMR
MPPI
OPALR
PDM1
STRBR
UAMR
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 3000
HiPath 3300
Subscriber Line Modules Central Board Trunk Boards
Options
HXGR3 CBRC HXGR3
IVMP8R CMA STLS4R
IVMS8R CMS STLSX4R
SLU8R CUPR TLA4R TMGL4R
SLU8R CUPR TLANI4R TLANI4R
STLS4R IMODN
STLSX4R LIM
8SLAR MMC
UPSC-DR
ANI4R1
EVM
EXMR
MPPI
OPALR
PDM1
STRBR
UAMR
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
HiPath 5000
2.3 HiPath 5000

HiPath 5000 Real-Time Services Manager RSM is operated as a central administration unit in
an IP network of HiPath 3000 systems. All participating nodes can be administered from a cen-
tral point through the formation of a "single system image".
HiPath 5000 RSM is the platform for providing applications at a central point and enables them
to be used by all stations in the IP network.
The HiPath ComScendo Service also supports the use of an integrated gatekeeper as well as
features for IP workpoint clients from HiPath ComScendo. Up to 1000 registered IP workpoint
clients and up to 250 CorNet-IP lines (CorNet-NQ protocol tunneled in H.323 via Annex M1)
are supported in this process.
The HiPath ComScendo Service is a complete HiPath 3000 node that is only configured as
software on a PC. Apart from TDM-specific features (for example, the connection of UP0/E sta-
tions, trunks, and special stations, such as, door openers, etc.), all HiPath 3000/5000 features
are available. HiPath ComScendo Service is administered via HiPath 3000/5000 Manager E,
while the HG 1500 resources (see the feature description) are administered via Web-Based
Management (WBM).
Cross-platform use of HiPath ComScendo features (IP networking), for example in conjunction
with HiPath 4000, is implemented via CorNet-IP (CorNet-NQ protocol tunnelled in H.323 via
annex M1). HG 1500 in HiPath 3000 and HG3550 V2.0 in HiPath 4000 are prerequisites for
IP networking over CorNet-IP.
Parts of the following setup for HiPath 5000 are optional and can be installed both on the HiPath
5000 Real-Time Services Manager RSM and on a separate PC.
● Feature Server (central administration service in a HiPath 3000/5000 network)
● Presence Manager (service for LED signaling of call processing station statuses and net-
work-wide DSS keys)
● HiPath ComScendo Service (gatekeeper and HiPath ComScendo features for
IP workpoint clients)
● HiPath 3000/5000 Manager E (MS Windows-based tool for the administration of all service
and customer-specific data by Service)
● HiPath 3000/5000 Manager C (MS Windows-based tool for the administration of customer-
specific data by the customer)
● HiPath Software Manager (Web-based tool for upgrades (Upgrade Manager for HiPath
ComScendo Service and HG 1500) and backups (Backup Manager for HiPath ComScen-
do Service, HG 1500 and databases))
● Inventory Manager (service for detecting software components installed and system infor-
mation in a HiPath 3000/5000 network)
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 5000
● 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 offline
mode)
● Personal Call Manager PCM (Web-based application for the configuration and administra-
tion of personal call forwarding operations)
● HiPath FM Desktop V3.0 (Java-based application for error signaling)
● GetAccount (application that prepares generated call data records for further processing)
The IP network is also available if four ITSPs are connected simultaneously.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
System-Specific Capacity Limits for HiPath 3000, HiPath 5000
2.4 System-Specific Capacity Limits for HiPath 3000, HiPath 5000

The maximum capacity limits are calculated based on the following assumptions:
● HiPath 3800: two board slots are reserved for trunks.
● HiPath 3550, HiPath 3500: Two S0 interfaces on the central board + 1 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 Erlang
Alternative capacity limits may be determined for sales purposes.
Table 10-15 contains the maximum system-specific configurations for UP0/E workpoint clients
and the corresponding add-on modules and adapters. Refer to the section "Capacities" in the
system description for a more detailed data table.
Table 2-6 HiPath 3000/5000 - System-Specific Capacity Limits (Maximum Configuration)
System HiPath HiPath HiPath HiPath HiPath HiPath
38001 3550 3500 3350 3300 Com-
Scendo
Service
Total Number of TDM and IP Stations2 500 1923 1924 965 966 –
Stations/Workpoint Clients
7 8 88 89
IP stations (system clients, H.323 clients) 500 192 192 96 96 1000
2 10 11 11 12 13
Total number of TDM stations 384 96 77 57 41 –
2 14 15 16
Analog stations 384 96 44 36 20 –
TDM Stations
17 18 19 20
UP0/E stations 384 72 48 24 24 –
11 11 21 24
Additional stations via adapter (phone 116 48 29 24 24 –
adapter/analog adapter/ISDN adapter)
Cordless stations 250 64/3222 23 32 16 16 –
Base Stations for HiPath Cordless Office 64 16/7 7 3 3 –

Total Number of Lines 250 60 60 16 16 –
Total number of analog trunks and network 120 60 60 16 8 –
trunks
Lines
Total number of B channels on digital trunks 180 60 60 16 16 –

and digital network trunks (S0, S2M)
CorNet IP network trunks 128 60 60 16 16 250
24 27
HG 1500 boards 8 3 3 1 (2 ) 1 (2 ) –
Gateway channels to the system 128 48 48 16 16 –
1 Testing is not required on stations and lines up to the maximum configuration. Configurations that contain UCD/ACD or
more than one SLCN or groups with more than ten stations should always be checked using the project planning tool (in-
tranet: http://intranet.mch4.siemens.de/syseng/perfeng/tools/hpt/index.htm).
2 Only configurations that do not exceed this limit will be supported.
3 Up to 96 of the 192 stations can be TDM stations.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

System-Specific Capacity Limits for HiPath 3000, HiPath 5000
4 Up to 61 of the 192 stations can be TDM stations (4xa/b + 1xUP0/E + 7xBS/32xHiPath Cordless Office stations at the central
board + 3xSLU8R or 3x8SLAR or 3xSLAD8R).
board + 1x16SLA).
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 EPSU2 power supply unit must be used.
11 4xa/b + 1xUP0/E + 7xBS/32xHiPath Cordless Office stations at the central board + 5xSLU8R or 5x8SLAR or 5xSLAD8R.
12 4xa/b + 5xUP0/E + 3xBS/16xHiPath Cordless Office stations at the central board + 2x16SLA.
13 4xa/b + 5xUP0/E + 3xBS/16xHiPath Cordless Office stations at the central board + 2xSLU8R or 2x8SLAR or 2xSLAD8R.
14 4xa/b at the central board + 5x8SLAR or 5xSLAD8R.
15 4xa/b at the central board + 2x16SLA.
16 4xa/b 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, a 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 Two HG 1500 boards can be installed if PDM1 is not being used.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Static Configuration Rules
2.5 Static Configuration Rules
2.5.1 Resources and Capacity Limits
For information on the configuration of HG 1500 boards, refer to the HG 1500 Ad-
> ministration Manual.
With HiPath 3000/5000, HG 1500 provides the resources listed in Table 2-7 via the HG 1500
boards defined as media gateways (= gateway HG 1500).
Table 2-8 shows the board-specific capacity limits (maximum configuration) for the correspond-
ing functions.
Table 2-7 Technical Specifications (Resources) of the HG 1500 Boards Defined as Me-
dia Gateways
Resource HXGM3 HXGS3 STMI2
HXGR3
without with 1 x with 2 x without with 1 x without
PDM1 PDM1 PDM1 PDM1 PDM1 PDMX1
Routing channels 16 16 16
A routing channel is required, for
example, for making connections
between two IP networks via ISDN
(ISDN routing).
Gateway channels (DSP chan- 16 24 32 8 16 32
nels)
A gateway channel is required, for
example, to connect an IP work-
point client and a TDM workpoint
client (for example, optiPoint 500)
as well as for connections to the
ITSP.
Two gateway channels are re-
quired for connections to an ITSP.
Fax/modem channels (G.711) 16 24 32 8 16 32
Fax channels (T.38) 3 2 3
These are special hardware re-
sources which facilitate fax via
vCAPI and fax via IP functionality
with the T.38 protocol.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

dia Gateways
Resource HXGM3 HXGS3 STMI2
HXGR3
Teleworker with AES encryption 10 8 10
and codec G.711/G.7292 (Sample
rate 20 ms)
Teleworker with AES encryption 16 12 16
and codec G.723 (sample rate
30 msec)
DMC channels 12 18 24 6 12 24
These are the gateway channels
for Direct Media Connection
(DMC) with HiPath 4000 (DMC in-
terworking feature is active).3).
MOH Channels (G.711, G.723, 5 5 5
G.729)
The number of MOH channels
used depends on the configuration
(HiPath 3000/5000 Manager E).
LAN connections 2 2 2
Number of LAN connections that 1 1 1
can be used as DSL connections.
1 PDMX is not currently released.
2 G.729 is not currently supported by optiClient 130 V4.0.
3 The number of gateway channels available (DSP channels) is reduced as soon as the DMC interworking feature is acti-
vated with HiPath 3000/5000 Manager E.
Table 2-8 HG 1500 - Board-Specific Capacity Limits (Maximum Configuration)

Function HXGM3 HXGS3 STMI2
HXGR3
PPP Routing Partner 70 70 70
vCAPI clients 100 100 100
IP workpoint clients that support
vCAPI.
MOH data streams 10 10 10
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.5.2 Gateway Channels (DSP Channels)
From HiPath 3000/5000 V7 R2 "IP/IP e2e payload via enterprise proxy" is supported
> for Internet telephony. This means that, for Internet telephony, data packets do not
need to be processed by the digital signal processors of the system. Calls are routed
via LANs, routers and the Internet Telephony Service Providers (ITSP).
HiPath 3000/5000 sets up a call to the remote station. As a result, gateway channels
(DSP channels) are not required for ITSP connections.
Instead, the maximum number of simultaneous calls depends on the codec used
and the available bandwidth of the Internet telephony connection.
Gateway connections are required for connections to TDM workpoint clients and lines. A gate-
way channel is required on the HG 1500 board for each gateway connection. TDM workpoint
clients and trunks include, for example
● UP0/E stations (Optiset E, optiPoint 500)
● CMI stations
● analog stations
● ISDN stations
● trunk and tie lines (MSI, S0, S2M)
Examples: a consultation call to an optiPoint 500 telephone is set up during an existing con-
nection between two IP workpoint clients. A HG 1500 board gateway channel is necessary for
the consultation call.
An IP workpoint client seizes a trunk. A HG 1500 board gateway channel is necessary for this
trunk.
In the case of conferences, the number of gateway channels seized corresponds to the number
of stations and IP workpoint clients involved.
Channels required for gateway connections

The following table shows the number of gateway channels (HG 1500 boards) necessary
based on the existing IP workpoint clients.
The calculation of the values is based on the following assumptions:
● A station spends 10 % of its working time in call status.
● The average time per call is three minutes.
● The availability loss is limited to 1.2 %.
Provisions should be made for more gateway channels (HG 1500 boards) in high traffic volume
environments (for example, call centers).
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Table 2-9 Number of Required Gateway Channels (HG 1500 Boards)
IP workpoint clients in the system Required number of gateway channels

0–3 2
4 – 12 4
13 – 16 6
17 – 38 8
39 – 54 10
55 – 70 12
71 – 86 14
87 – 96 15
97 – 101 16
102 – 136 20
137 – 172 24
173 – 210 28
211 – 247 32
248 – 324 40
325 – 402 48
403 – 481 56
482 – 562 64
563 – 726 80
727 – 890 96
891 – 1000 112
In a straightforward IP network, the number of gateway channels must be greater than or equal
to the number of TDM lines.
The required number of HG 1500 boards for VoIP is determined by the sum of the gateway
channels, MOH channels, and conference channels.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.5.3 ITSP Connection

HG 1500 supports connections to the Internet telephony service provider (ITSP) and thus the
use of Internet telephony in HiPath 3000/5000 V6.0 SMR-09 or later, particularly DID-enabled
DSL connections with phone number range. HG 1500 supports up to four ITSPs active simul-
taneously.
Gateway channels are required for connections to an ITSP provider. The following table shows
the number of gateway channels (DSP channels) required.
The maximum number of ITSP connections depends on the number of HG 1500 boards and
PDM modules set and the system used.
If you are using Internet telephony, the HG 1500 board is not allowed to be used as a DSL rout-
er. In this case, the connections to the ITSP must be set up over an external router.
Table 2-10 Number of Gateway Channels (DSP Channels) Required for Basic Call Sce-
narios
Calling stations Called stations

ITSP connection
TDM stations (analog stations, ISDN stations) 1
IP stations (system client, H.323 client, SIP client) 2
ISDN trunk and CorNet-N/CorNet-NQ/QSig network 1
CorNet-IP network 2
ITSP connection 2
2.5.4 MOH Channels (G.711, G.723, G.729)

A DSP channel is reserved on an HG 1500 board for each codec used for MOH. Up to five co-
decs can be configured for MOH for every HG 1500 board.
Examples:
● Only the codec G.711 is used for MOH: –> 1 DSP channel is needed.
● Codecs G.711, G.723.1, and G.729AB are used for MOH: –> 3 DSP channels are needed.
The DSP channels needed for MOH are no longer available for voice connections.
MOH can be simultaneously supplied to a maximum of ten IP workpoint clients per HG 1500
board, irrespective of the number of codecs configured. This means that up to ten MOH data
streams are possible for each HG 1500 board. If more than ten MOH data streams are needed
simultaneously, MOH should be activated on other HG 1500 boards.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

HiPath 5000 with HiPath ComScendo Service uses the MOH resources of the gateways logged
on, as described above.
The B channels used for MOH (DSP channels) are not licensed.
2.5.5 IP Networking Channels (PBX Networking Channels)

IP networking channels are used for connections between communication systems. In this
case, a distinction must be made between connections that use a gateway channel and direct
payload connections. Depending on the connection, the following resources are required for
successful connection setup.
Connection type Line Gateway channel

Direct payload connection Required Not required
Gateway connection Required Required
A connection request is rejected if a required resource is unavailable.
HiPath 3000/5000 Manager E is used to define how many of the maximum number of lines are
to be configured as IP networking channels (IP network trunks). The maximum number of IP
network trunks can be found in Table 2-6.
2.5.6 Bandwidth Control for IP Networking Channels (PBX Networking

Channels)
If IP networking channels are routed over the PPP channels (ISDN routing) on an HG 1500
board (see Section 2.6.4.2.3, “IP Trunking via LAN and WAN (ISDN/PPP)”) on HiPath 3750
and HiPath 3700, bandwidth control is only performed if this board is an HG 1500 gatekeeper
(signaling gateway).
Bandwidth control is not performed if the router is located on an HG 1500 gateway (media gate-
way).
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.5.7 DMC (Direct Media Connection) Channels

When the DMC interworking feature is active in an IP network between HiPath 3000 and HiPath
4000, gateway connections are set up over DMC channels. From the user’s perspective, a
DMC channel is a gateway channel that provides a gateway connection between HiPath 3000
and HiPath 4000. The fact that a DMC channel must serve both a master and slave connection
results in a DSP channel reduction.
Note: The number of gateway channels available (DSP channels) is reduced as soon as the
DMC interworking feature is activated with HiPath 3000/5000 Manager E. In this case, a Digital
Signal Processor (DSP) can only provide up to 80% of all possible channels (for example: 6
instead of 8 DSP channels, 12 instead of 16 DSP channels, etc.).
2.5.8 ISDN Routing/PPP Channels

HG 1500 boards can also be used as ISDN routers. The ISDN router can connect two physi-
cally separate IP networks together via an ISDN line. Channel bundling can be used to adjust
the required bandwidth.
The system reserves the B channels required for ISDN routing and thus restricts the available
gateway channels.
Table 2-11 HG 1500 - Board-Specific Sum of PPP Channels and Gateway Channels
(Maximum Numbers)
HXGM3 HXGS3 STMI2

HXGR3
Sum of PPP channels (for ISDN 16 24 32 8 16 32
routing) and gateway channels
If a large number of IP workpoint clients is required, the HG 1500 board may not also be used
as an ISDN router. In this case, ISDN routing functionality must be assigned to an individual
HG 1500 board.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

2.5.9 Fax/Modem Channels

It is possible to transmit faxes with Internet telephony both via G.711 gateway channels and
from V7 R4 or later also T.38 channels.
Although T.38 offers the more reliable method of fax transmission, it can only be used to a max-
imum of 14 Kbps. The number of T.38 channels available is limited by the higher processor
speed required for T.38. Alternatively, E.711 gateway channels can be used for fax transmis-
sions (not for Internet telephony).
Technical restrictions in Internet telephony mean that modem transmissions are not possible.
Note: The number of G.711 gateway channels available is reduced as soon as the DMC inter-
working feature is activated with HiPath 3000/5000 Manager E.
Internet-based fax transmissions that use G.711 frequently fail or incur errors. For this reason,
fax transmission via Internet telephony and G.711 is not supported. If the provider supports the
T.38 protocol, T.38 must be activated on the gateway. Otherwise, transmission must be via IS-
DN. The number of possible fax connections that can be routed simultaneously depends on
the hardware used.
The switchover from G.711 to T.38 takes place in WBM.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Dynamic Configuration Rules
2.6 Dynamic Configuration Rules

This section describes the underlying theoretical principles for the thumb rule by which the con-
trol load, and thus the dynamic performance characteristics, of E-Doku Version 3.0 systems
can be determined. The principles from which this document is derived are the same as those
for the thumb rule for HiPath 4000, i.e., every interface is considered in light of its outgoing and
incoming seizure intensity.
2.6.1 Dynamic Performance Characteristics

The dynamic performance characteristics of E-Doku Version 3.0 are as follows:
Standard Analog Optiset IP Phone ACD CorNet-N CorNet-NQ

BHCA
HiPath 33x0 2,880 1,240 1,250 690 1,650 1,420
HiPath 35x0
HiPath 3800 22,600 9,690 9,820 5,400 13,000 11,200
Table 2-12 Dynamic Performance Characteristics of E-Doku Version 3.0
This thumb rule can also be used to calculate the maximum number of terminals for certain con-
figurations. The method and some sample tables are described in the Section 2.6.5, “Maximum
Number of Devices for Special Cases”.
2.6.2 Thumb Rule for HiPath 3000/5000 V7
2.6.2.1 Procedural Principles

The thumb rule presented below for calculating the dynamic load for HiPath switches is based
on the principle of considering every interface (telephones and trunks) in light of its (incoming
and outgoing) seizure intensity. In the case of an external seizure, for example, the CPU load
is split between the telephone and the trunk.
The thumb rule for determining the manageable load takes multiple factors into account. This
includes not only several parameters, whose values can be determined from the current con-
figuration of the switch being examined, but also a variety of interfaces and performance char-
acteristics. These interfaces are each assigned a specific weight in accordance with their share
of the load to be managed. The basis for this is the average overhead for an Anate seizure
(60% internal-, 20% outgoing external-, and 20% incoming external seizure). This enables all
values to be normalized to Anate seizures. The planned switch configurations are then permis-
sible if the sum of all seizures – normalized to Anate seizures – does not exceed a maximum
value depending on the current switch variant and the computing hardware being used.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

The goal is to detect critical switch configurations early in the planning stage and to then per-
form a more precise analysis. The appropriate project planning tools for this purpose are still
maintained by SEN ESY HS PDT 4 or SEN ESY SME MP 42 and provided to the usual project
planning locations:
● NERT (Network Engineering & Routing Tool for Private Networks) for network planning
http://intranet.mch4.siemens.de/syseng/perfeng/tools/nert/index_en.htm
and
● Project Planning Tools for HiPath Systems
http://intranet.mch4.siemens.de/syseng/perfeng/tools/hpt/index_en.htm
An electronic version of the thumb rule in which all the following calculations are implemented
will also be made available there.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.6.2.2 Planning Load for HiPath Systems

This section describes a dimensioning method for the various systems. In order to provide for
sufficient reserves to handle load fluctuations during operations, a so-called planning load is
defined the systems. This planning load consists of 70 % of the capacity available for call pro-
cessing (switching) transactions (see Figure below).
100%
Basic load
(e.g., polling)
Relative shares Absolute shares

(w/o basic load) Reserves for load fluctua-
tions
70% 70 (1-basic load)%
Planning load for call

processing
HiPath 3000
Figure 2-6 Planning Load for HiPath 3000/5000 Systems
The planning load values described here are taken into account in the following table as the
"maximum permissible points".
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

2.6.2.3 Maximum Permissible Values for E-Doku Version 3.0

For version Version 3.0, the following maximum permissible point totals are used as a basis for
the thumb rule (Norm BHCA):
HiPath 3000 Maximum Points

HiPath 3300/3350/3500/3550 2,880
HiPath 3800 22,600
Table 2-13 E-Doku Version 3.0 Expansion Levels and their Maximum Points
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.6.2.4 Additional Parameters

In order to calculate the number of points for a specific system, several additional parameters
are usually required. These parameters are described below.
● Factor FTln (subscriber traffic factor):
As in Guideline 12TR3 for 700 ports or more, this rule of thumb assumes a station traffic
value PTln = 0.15 Erl and four outgoing seizures per device during busy traffic hours. The
factor FTln is used to achieve some flexibility in the underlying station traffic values and sei-
zures. In the case of international systems, in particular, a factor greater than 1 may be ap-
propriate in some circumstances (e.g. PTln = 0.20 erl results in FTln = 1.33). In general, the
following applies:
PTln BHCATln
FTln = FTln =
0.15 4
If the seizure value per terminal is not directly specified, FTln can be determined via the re-
lationship to the 4 outgoing seizures indicated above (e.g., 3 seizures produce a value of
FTln = 0.75).
● Factor FLtg (trunk traffic factor) for traffic volume on trunks:
As in Guideline 12TR3, this rule of thumb assumes a line traffic value PLtg = 0.8 Erl and
12.5 incoming seizures per B channel during busy traffic hours. The factor FLine is used to
achieve some flexibility in the underlying traffic values and seizures. A factor of less than
1 (for example, PLtg = 0.5 Erl gives FLtg = 0.63) may be appropriate in some cases, espe-
cially for systems that were over-dimensioned to create a virtually blockage-free system.
In general, the following applies:
PLtg BHCALtg
FLtg = FLtg =
0.8 12.5
● Factor FVPL (AC traffic factor) for traffic volume of an attendant console:
This rule of thumb assumes a traffic value at an active attendant PVPL = 0.8 Erl and 144
seizures during busy traffic hours. The factor FVPL is used to achieve some flexibility in the
underlying station traffic values and seizures. A factor of less than 1 may be appropriate,
especially for systems in which the attendant consoles were over-dimensioned. In general,
the following applies:
PVPL BHCAVPL
FVPL = FVPL =
0.8 144
● Factor C for ACD utilization:

For ACD agents, the intensity of the utilization of this feature must also be taken into ac-
count. By default, it is assumed that an ACD agent handles 16 ACD calls per hour. If ap-
plications need to be configured with values that significantly exceed or fall below this de-
fault, the factor C can be used to specify the corresponding multiple of the value 16. For
example, TV advertising campaigns may incur values of up to ten times the norm.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

● Factor g for mobility within a CMI node:

This thumb rule formula is based on the assumption of the mobility level of mobile subscrib-
ers. The factor g determines the probability that a station is not located at its home board
when visiting the radio area of it home system. In the case of homogeneous allocation, the
factor g can be calculated from the number of SLC boards in the system:
1
g=1—
Number of SLC boards
● Factor G for mobility within the CMI network:

This thumb rule formula is based on the assumption of the mobility level of mobile subscrib-
ers. The factor G determines the probability, that a subscriber resides outside the cordless
area of his home system. In branch networks where subscribers rarely reside in other
nodes, G is relatively small (e.g. G = 0.1). A homogeneous allocation can be assumed, if
a location is overlapped from several cordless areas of different nodes. In this case, the
factor G can be calculated from the number of CMI nodes:
1
G=1—
Number of CMI nodes
2.6.2.5 Current Thumb Rule Values

The following tables list the interfaces considered in the thumb rule formula with their respective
meanings and corresponding weights in points (normalized to Anate seizures).
● Table 2-14 on page 2-33: Points for Devices
● Table 2-15 on page 2-33: Points for Mobile Handsets
● Table 2-16 on page 2-34: Points for Special Devices
● Table 2-17 on page 2-34: Points for Trunks
● Table 2-18 on page 2-35: Additional Overhead for Controlling Process Flows at Devices
via CTI Applications
● Table 2-19 on page 2-35: Points for Groups
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Terminal Devices
System Meaning Weight

Interface
Analog Number of devices connected via T/R wires. 3.3 · FTln
Optiset Number of terminal devices connected via UP0/E (for ex- 7.7 · FTln
ample, Optiset, optiPoint 500, OpenStage (TDM connec-
tion variant)), including adapters for data traffic character-
ized by long call durations (for example, Optiset with V.24).
IP phones Number of terminal devices (e.g. optiPoint 410, optiPoint 7.6 · FTln
420, OpenStage (CorNet-IP connection variant)) connect-
ed via IP using HFA functionality.
Note: HG 1500 performance must be considered sepa-
rately.
SIP phones Number of terminal devices (e.g. optiPoint 410 S, optiPoint 3.6 · FTln
420 S) connected via SIP.
rately.
Data Number of devices for data services (for example, data ter- 4.7 · FTln
minals).
ISDN Port Number of ISDN connections; the B channels are used for 12.8 · FTln
voice and data traffic characterized by relatively short call
durations (e.g. S0 bus with several terminal devices but no
Xpression ports).
Table 2-14 Points for Devices
Mobile Stations
System Interface Meaning Weight

Cordless Devices Number of CMI handsets if only one system in 6.8 · FTln
the network is operated in CMI mode and only
one SLC16 is used.
Number of CMI handsets if only one system in (6.8 + 23.0 · g) · FTln
the network is operated in CMI mode.
Number of CMI handsets, if network wide CMI (6.8 + 23.0 · g·(1-G)
mode is operated. + 44.4 · G) · FTln
Table 2-15 Points for Mobile Handsets
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Special Devices

UCD Agent Number of active UCD agents 1controlled by the HPPC 59 · C
(HPCC, HPPC) application.
ACD Agent Number of active ACD agents, where the display of each 179 / T +
(e.g., HPCO) agent is refreshed every T seconds. 65 · C
ACD group Number of ACD groups. 4.8
AC Number of active attendant consoles 252 · FVPL
Automatic AC Number of analog trunks or digital B channels which are 21.9 · FLtg
(IVM) routed from CO to the automatic attendant at IVM.
Table 2-16 Points for Special Devices
1 The associated terminal devices (Optiset or similar) must no longer be considered separately; the same applies to the
incoming trunks provided for the ACD group (at least one B channel per agent).
Trunk Interfaces

Trunk Number of analog trunks or digital B channels to CO 24.6 · FLtg
ITSP Possible number of simultaneous voice channels to the 23.9 · FLtg
lines ITSPs
Networking trunk Number of digital B channels to other nodes or to Xpres- 23.4 · FLtg
(TDM CorNet-N) sions via TDM with CorNet-N
(TDM CorNet-NQ) sions via TDM with CorNet-NQ
(IP) sions via IP
rately.
Table 2-17 Points for Trunks
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Additional Overhead for Features

The additional overhead values listed below are based on the assumption that the correspond-
ing basic overhead for each terminal device involved has already been recorded in Table 2-14.

CTI-control Number of devices operated by means of CTI-controlled 1.7 · FTln
via CSTA connection procedures via CSTA commands
Table 2-18 Additional Overhead for Controlling Process Flows at Devices via CTI Applica-
tions

Call pickup group Overhead per call pickup group with N mem- (0.06 · (N-1)·N +
bers, where Opt refers to digital devices. 0.48 · (N-1)·Opt)·FTln
Group call Overhead per call pickup group with N mem- (0.91 · (N-1)·N +
bers, where Opt refers to digital devices. 0.66 · (N-1)·Opt)·FTln
Table 2-19 Points for Groups
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

2.6.3 Thumb Rule for HG 1500 V3.0
2.6.3.1 Procedural Principles

The thumb rule presented below for calculating the dynamic load for the HG 1500 board is
based on the principle of considering every functionality (HFA phone, IP trunking, gateway
channels, VPN tunnel, etc.) in terms of its CPU load.
2.6.3.2 Maximum Permissible Values for HG 1500 V3.0

For version V3.0, the following maximum permissible point totals are used as a basis for the
thumb rule:
HG 1500 Board Corresponding Systems Maximum

Points
HXGS3, HXGR3 HiPath 3300/3350/3500/3550 780
STMI2 HiPath 3800 980
Table 2-20 HG 1500 V3.0 Boards and Corresponding Maximum Points
2.6.3.3 Current Thumb Rule Values

The following table lists the interfaces taken into account in the thumb rule.
PDM Modules

Interface
PDM1 Number of PDM1 modules on the board 10
Table 2-21 Points for the PDM Modules to Increase the DSP Number
Signaling

Interface
IP phones Number of terminal devices connected via IP using HFA func- 0.68 · FTln
without H.235 tionality or SIP (GK security is deactivated).
IP phones Number of terminal devices connected via IP using HFA func- 0.78 · FTln
with H.235 tionality (full or reduced GK security is activated).
Table 2-22 Points for Signaling
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Interface
PBX networking Number of digital B channels (networking trunk) to other nodes 3.2 · FTln
channel without or to Xpressions via IP (GK security is deactivated).
H.235
PBX networking Number of digital B channels (networking trunk) to other nodes 4.0 · FLtg
channel with or to Xpressions via IP (reduced or full GK security is activat-
H.235 ed).
ITSP lines with- Possible number of simultaneous voice channels to the ITSPs 3.2 · FLtg
out H.235
ITSP lines with Possible number of simultaneous voice channels to the ITSPs 4.0 · FLtg
H.235
Table 2-22 Points for Signaling
Gateway Channels (DSP - LAN)

The following table indicates the HG 1500 gateway channel load (DSP ↔ LAN) required for
connections between TDM and IP, e.g. for calls between CO and IP phones. The size of the
HG 1500 load depends on various features (for example, "Enhanced B Channels", VPN func-
tionality) and on the voice codec used (G.711, G.729, G.723).

Interface
Gateway channels Number of gateway channels (DSP ↔ LAN) if the feature 11
with enhanced B "Enhanced B Channels" is activated in the WBM, that is,
channel firewall and VPN functionality may not be used.
Gateway channels Number of gateway channels (DSP ↔ LAN) if VPN func- 39
without VPN tionality is not used.
Gateway channels Number of gateway channels (DSP ↔ LAN) if VPN and 89
with VPN and AES AES encryption are used.
Gateway channels Number of gateway channels (DSP ↔ LAN) if VPN and 104
with VPN and 3DES 3DES are used.
Gateway channels Number of gateway channels (DSP ↔ LAN) if only the 7.5
with enhanced B voice codec G.723 is used and the feature "Enhanced B
channel Channels" is activated in the WBM.
(G.723 only)
Gateway channels Number of gateway channels (DSP ↔ LAN) if only the 26
without VPN voice codec G.723 and no VPN functionality is used.
(G.723 only)
Table 2-23 Points for Gateway Channels (When Using G.711 or G.729)
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm


Interface
with VPN and AES voice codec G.723 and VPN with AES encryption are used.
(G.723 only)
with VPN and 3DES voice codec G.723, VPN and 3DES are used.
(G.723 only)
Table 2-23 Points for Gateway Channels (When Using G.711 or G.729)
Voice Channels (LAN1 - LAN2)

The following table indicates the HG 1500 voice channel load (LAN1 ↔ LAN2) when voice
packets are routed via the HG 1500, e.g. for calls between IP phones in two different systems
networked via a VPN tunnel. The size of the HG 1500 load depends on the encryption algo-
rithm (AES or 3DES) and on the voice codec used (G.711, G.729, G.723).

Interface
Voice channels Number of voice channels (LAN1 ↔ LAN2) if encryption is 73
without VPN not used.
Voice channels Number of voice channels (LAN1 ↔ LAN2) if VPN and 89
with VPN and AES AES encryption are used.
Voice channels Number of voice channels (LAN1 ↔ LAN2) if VPN and 104
with VPN and 3DES 3DES encryption are used.
Voice channels Number of voice channels (LAN1 ↔ LAN2) if only the voice 49
without VPN codec G.723 and no encryption is used.
(G.723 only)
with VPN and AES codec G.723 and VPN with AES encryption is used.
(G.723 only)
with VPN and 3DES codec G.723 and VPN with 3DES encryption is used.
(G.723 only)
Table 2-24 Points for Voice Channels (When Using G.711 or G.729)
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Data (LAN)
The following table indicates the HG 1500 data routing load (LAN1 ↔ LAN2), e.g. for a DSL
connection to the Internet or a data connection for two locations via VPN. The size of the
HG 1500 load depends on the encryption algorithm used (AES or 3DES), and on the packet
rate and average packet size.

Interface
Data without VPN Number of packets per second if the average packet size is 100 0.72
100 bytes bytes and encryption is not used.
Data with AES Number of packets per second if the average packet size is 100 0.84
100 bytes bytes and VPN with AES encryption is used.
Data with 3DES Number of packets per second if the average packet size is 100 0.93
100 bytes bytes and VPN with 3DES encryption is used.
Data without VPN Number of packets per second if the average packet size is 500 0.79
500 bytes bytes and encryption is not used.
Data with AES Number of packets per second if the average packet size is 500 1.19
500 bytes bytes and VPN with AES encryption is used.
Data with 3DES Number of packets per second if the average packet size is 500 1.66
500 bytes bytes and VPN with 3DES encryption is used.
Data without VPN Number of packets per second if the average packet size is 0.96
1400 bytes 1400 bytes and encryption is not used.
Data with AES Number of packets per second if the average packet size is 1.98
1400 bytes 1400 bytes and VPN with AES encryption is used.
Data with 3DES Number of packets per second if the average packet size is 3.29
1400 bytes 1400 bytes and VPN with 3DES encryption is used.
Table 2-25 Points for Data Routing
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

PPP Channels

Interface
Voice channels Number of voice channels with G.729 and a packet assembly of 150
(G.729 – 1) 1 (20ms) that are routed with PPP via ISDN.
PPP data chan- Number of channels via which data is routed with PPP 55
nels
Table 2-26 Points for PPP Channels
VCAPI Channels

Interface
VCAPI fax Number of VCAPI channels (not the number of clients) used for 11
fax purposes
VCAPI data Number of VCAPI channels (not the number of clients) used for 34
data transfer
Table 2-27 Points for VCAPI Channels
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.6.4 Example for Using the Thumb Rule

Using a standard configuration, the following example illustrates a calculation based on the
thumb rule.
2.6.4.1 E-Doku Version 3.0 Configuration
Number Type
100 Anate
100 Optiset
20 Optiset with CTI-controlled functions
20 IP phones
1 Call pickup group consisting of two analog telephones and eight Optisets
5 Optiset ACD agents with 32 calls per hour and display updates every five seconds
2 Attendant consoles
60 Digital trunks to CO, of which 5 are for ACD application
30 Digital trunks to other systems via TDM (CorNet-N)
The calculations are made using default traffic values. The thumb rule produces the following
results:
100 · 3.4 + Anate
(100 + 20) · 6.3 + Digital devices (Optiset), but without ACD agents
20 · 7.3 + IP phones
5 · (179 / 5 + 65 · 32 / 16) + ACD agents (32 calls per hour and agent, i.e. C = 32/16)
1 · 4.8 + One ACD group
2 · 252 + Attendant consoles
55 · 22.9 Digital trunks minus the 5 ACD trunks
30 · 18.9 + Networking trunk via TDM
20 · 1.7 + Additional overhead for the 20 CTI-controlled terminal devices
1 · (0.06 · 9 · 10 + 0.48 · 9 · 8) Call pickup group
= 4,480 Total number of points
According to Table 2-13, 22,600 points are available for HiPath 3800. Implementation with Hi-
Path 3800 is, consequently, possible.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

2.6.4.2 HG 1500 Configurations
2.6.4.2.1 IP Trunking with TDM Terminal Points Only

A HiPath 3800 system is networked with another system via an IP trunking link with 32 B chan-
nels. The codec G.711 with a sample rate of 20 ms (without encryption) is used for the IP trunk-
ing link. This requires an STMI2 module (2 DSPs on board = 32 voice channels are supported).
Head Office Branch Office
HiPath 3800 ISDN ISDN HiPath 3800
LAN 2 Enhanced B Channels LAN 2

LAN 1 Codec G.711 (20ms) LAN 1
Intranet Intranet
32 Gateway Channels
32 PBX Networking Channels
Figure 2-7 IP Trunking with TDM Terminal Points Only
Calculation:
32 gateway channels via LAN 1 should be included in the calculation. If more than 16 channels
are required, the feature “Enhanced B Channels” must be activated. The signaling load must
also be taken into account.
Function Formula Points

Signaling: PBX networking channels (without H.235) 32 · 3.2 102
Gateway channels: payload (G.711/20ms) 32 · 11 352
Total 474
Table 2-28 IP Trunking Calculated with TDM Terminal Points Only
With a permissible maximum points total of 980, this scenario is feasible. However, this sample
calculation does not apply for HXGS/R3. This is because the static configuration rules only al-
low a maximum of 16 channels per board card.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.6.4.2.2 IP Trunking and HFA Clients

A HiPath 3800 system with 96 HFA clients and additional TDM subscribers is networked with
other nodes via an IP trunking link with 16 B channels. For 96 HFA terminal points, 15 gateway
channels with 0.1 erl per terminal point are required.
The codec G.711 with a sample rate of 20 ms (without encryption) is required both for the IP
trunking link and for the HFA terminal points. This requires an STMI2 module (2 DSPs on
board = 32 voice channels are supported).
Head Office Branch Office
LAN 2 LAN 2
LAN 1 LAN 1
(15 + 16)
32 PBX Networking
31 Gateway
Channels
Channels Intranet Intranet
96 HFA Clients
Figure 2-8 IP Trunking and HFA Clients
Calculation:
Thirty-one gateway channels via LAN 1 should be taken into account. If more than 16 channels
are required, the feature "Enhanced B Channels" must be activated. Firewall and encryption
are not possible in this example. The signaling load (16 PBX networking channels and 96 HFA
clients) must also be taken into account.

Signaling: IP phones (without H.235) 96 · 0.68 65
Total 477
Table 2-29 Calculation for IP Trunking and HFA Clients
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

With a permissible maximum points total of 980, this scenario is feasible. However, this sample
calculation does not apply for HXGS/R3. This is because the static configuration rules only al-
low a maximum of 16 channels per board card.
2.6.4.2.3 IP Trunking via LAN and WAN (ISDN/PPP)

A HiPath 3800 system (head office) is connected to a second system (branch office 1) via an
ISDN connection with 2 PPP channels (S0), and to a third system (branch office 2) via a direct
LAN connection.
Voice over PPP with codec G.729 and a sample rate of 60 ms without encryption is implement-
ed for PBX network connection to the second system. Six voice channels are consequently
supported via the two PPP channels (S0).
8 voice channels are sufficient for the PBX networking connection to the third system (branch
office 2). Codec G.729 with a sample rate of 20 ms without encryption is used for this connec-
tion.
At head office, 6+8=14 PBX networking channels must be configured, while 6 PBX networking
channels must be configured at branch office 1, and 8 PBX networking channels configured at
branch office 2.
One STMI2 (2 DSPs on board supporting up to 32 voice channels) is sufficient for this purpose.
6 Voice Channels, Codec G.729
(Packet Assembly of 3 and 60ms
Head Office Sample Rate) 6 PBX Networking Channels
Branch
Office 1
2 PPP Channels
LAN 2 LAN 2
LAN 1 LAN 1
Branch
14 PBX Networking Office 2
Channels ISDN HiPath 3000
LAN 2
LAN 1
Intranet Intranet
8 Gateway Channels 8 PBX Networking Channels

Codec G.729 (20ms)
Figure 2-9 IP Trunking and Node Connection via ISDN (PPP)
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Calculation for head office:

6 voice channels over PPP must be calculated for branch office 1. The points for G.729 with a
packet assembly of 3 (60ms) must be used. 8 gateway channels via LAN 1 must be calculated
for branch office 2. The signaling load (14 PBX networking channels) must also be taken into
account.

PPP channels: voice with G.729 and a packet assembly of 3 6 · 54 324
Total 681
Table 2-30 Calculation for Head Office
With a permissible maximum points total of 980, this scenario is feasible.
2.6.4.2.4 IP Trunking with VPN (Voice Only)

2 HiPath 3500/3550 systems should be connected via VPN with a HiPath 3800 system. At head
office (HiPath 3800), only TDM telephones are connected. 8 voice channels via LAN2 are avail-
able for the connection to the branch offices.
Each branch office (HiPath 3500/3550 system) is equipped with 30 HFA telephones and 8 gate-
way channels for the connection with the ISDN CO. 4 voice channels are also available for the
connection to head office. The codec G.711 with a sample rate of 20ms is used for the VPN
networking. The connection between the head office and the branch offices should be config-
ured via the Internet using an AES-encrypted VPN tunnel.
For this configuration, the HiPath 3800 requires one STMI2 (2 DSPs on board for 32 channels),
while the HiPath 3500/3550 systems each require one HXGS3 (1 DSP on board for 8 chan-
nels).
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Branch Office 1
ISDN HiPath 35x0
4 Voice PBX/Networking Channels
AES Encryption
Codec G.711 (20ms)
LAN 2
LAN 1 ISDN
Head Office
8 Gateway Channels
8 Voice PBX/Networking Intranet
HiPath 3800 Channels
AES Encryption
Codec G.711 (20ms)
LAN 2
LAN 1 Internet
30 HFA Clients
Encrypted Branch Office 2

Intranet Intranet Traffic HiPath 35x0
(Voice/Data)
via VPN Tunnel
LAN 2
4 Voice PBX/Networking Chan- LAN 1 ISDN
nels
AES Encryption
Codec G.711 (20ms) 8 Gateway Chan-
Intranet
30 HFA Clients
Figure 2-10 VPN Networking (Voice Only)
Calculation for head office (HiPath 3800)

8 gateway channels via LAN2 with AES encryption must be calculated. In order to use the en-
cryption feature, the option "Enhanced B Channels" must be deactivated. The signaling load
must also be taken into account.

Gateway channels: G.711 with VPN and AES 8 · 89 712
Total 738
Table 2-31 Calculation for Head Office (HiPath 3800)
With a permissible maximum points total of 980, this scenario is feasible for head office.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Calculation for each individual branch office (HiPath 3500/3550):

4 gateway channels via LAN2 with AES encryption, and 8 gateway channels from HFA tele-
phones to the local ISDN CO (via LAN1) must be calculated. The signaling load must also be
taken into account.

Voice channels: G.711 with VPN and AES 4 · 89 356
Total 701
Table 2-32 Calculation for Each Individual Branch Office (HiPath 3500/3550):
With a permissible maximum points total of 780, this scenario is feasible for the branch offices.
2.6.4.2.5 Standalone System with Home Offices connected via VPN

8 home offices are to be connected to a HiPath 3800 system. Teleworkers use G.723 with a
sample rate of 30 ms. Data can also be transferred at 512 Kbps in both directions via a 1-Mbps
SDSL connection. The average packet length is 500 bytes. VPN should be used with AES en-
cryption. This configuration requires 1 STMI2 (2 DSPs on board for 32 channels).
ISDN
HiPath 3800
4 Voice Channels
AES Encryption
Codec G.723 (30ms)
LAN 2
LAN 1 Internet
512 kbit/s Data

Encrypted Intranet Traffic 8 x VPN Clients
Head Office SDSL (Voice/Data) via VPN Tunnel Safenet Sentinel
1 Mbit/s optiClient 130 V4.0
Figure 2-11 VPN Voice and Data, Home Office Connection
Performance calculation:
G.723 is generally configured for home offices. As VPN is required for the DSL connection, the
option "Enhanced B Channels" must be deactivated. The HFA terminal point signaling load
must also be taken into account.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

When calculating the data traffic load, the upstream and downstream packet rates must be cal-
culated from the average packet length.
512 · 1000 / 8 byte/s 512 · 1000 / 8 byte/s
= 128 packets/s = 128 packets/s
500 bytes/packet 500 bytes/packet

Data (LAN): VPN and AES with 500 bytes upstream 128 · 1.19 152
Data (LAN): VPN and AES with 500 bytes downstream 128 · 1.19 152
Total 789
Table 2-33 Performance Calculation
Bandwidth calculation:

Voice channels: G.723 with VPN and AES 8 · 44.3 354
Data (LAN): VPN and AES with 500 bytes 512 512
Total 866
Table 2-34 Bandwidth Calculation
A 1Mbit/s connection is sufficient for the customer.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.6.4.2.6 VPN Networking with Data and Voice Connections

A 1000 Kbps duplex data connection between 2 HiPath 3800 systems should be configured via
a 2 Mbps SDSL interface. The average packet size should be 500 bytes. The SDSL connection
should also be used for trunk connections with G.729 and a sample rate of 20ms. The SDSL
line is connected to LAN2. The maximum possible number of additional IP trunking channels
with G.729 should be calculated.
ISDN
Branch Office
HiPath 3800 HiPath 3000

4 Voice PBX/Networking Channels
AES Encryption
Codec G.729 (20ms)
LAN 2 LAN 2
LAN 1 Internet LAN 1
1000 kbit/s Data

Encrypted Intranet Traffic
Head Office SDSL Intranet
(Voice) via VPN Tunnel
2 Mbit/s
Figure 2-12 VPN Networking
Performance calculation:
The required data traffic performance must first be determined. The upstream and downstream
packet rates must therefore first be calculated from the average packet length.
1000 · 1000 / 8 byte/s 1000 · 1000 / 8 byte/s
= 250 packets/s = 250 packets/s
500 bytes/packet 500 bytes/packet

Total 596
Table 2-35 Performance Calculation (1)
With a permissible maximum points total of 980, this leaves 980-596=384 points for IP trunking
channels. For each IP trunking channel, one PBX networking channel and one gateway chan-
nel with VPN and AES is required. In other words, 3.2+89=92.2 points are required per trunking
channel. If the remaining points are divided by the number of points per channel and rounded
off, this results in 384/92.2=4 channels.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm


Gateway channels: G.729 with VPN and AES 4 · 89 356
Total 965
Table 2-36 Performance Calculation (2)
Bandwidth calculation:

Data (LAN): VPN and AES with 500 bytes 1000 1000
Total 1240
Table 2-37 Bandwidth Calculation
A 2Mbit/s connection is sufficient for the customer.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
2.6.4.2.7 IP Workpoint Clients for ISDN and ITSP Connection in HiPath 3800
100 IP workpoint clients (without H.235) should be connected to HiPath 3800. It should be pos-
sible to conduct eight simultaneous calls to the ISDN exchange as well as eight simultaneous
calls to the ITSP. The voice and data traffic to the Internet is relayed via an external router that
also functions as the firewall. This allows the “Enhanced B Channels” feature to be activated.
For this scenario, only an STMI2 board should be implemented.
The IP workpoints as well as the calls to the ITSP must be taken into account for signaling.
Eight gateway channels to the ISDN exchange and sixteen gateway channels to the ITSP are
required (two gateway channels per IP workpoint client to the ITSP).
Head Office
HiPath 3800 ISDN
LAN 2
LAN 1
8 gateway channels to the ISDN 16 gateway channels to the ITSP

(Codec G.711 (20ms)) (Codec G.711 (20ms))
Intranet
Internet
ITSP
100 HFA stations
Figure 2-13 IP Workpoint Clients for ISDN and ITSP Connection in HiPath 3800

Signaling without H.235 se- 100 x IP workpoint clients: 100 x 0.68 68.0
curity (independent of the system client, HFA client,
WBM setting "Enhanced B H.323 client (8 calls per
Channels") hour)
16 x signaling for gateway 16 x 3.2 51.2
channel to ITSP
Table 2-38 Calculation
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm


Payload (additional feature: Voice gateway channel over LAN interface 1
WBM setting "Enhanced B without encryption:
Channels" activated) 24 x G.711 (received: 20 24 x 11 264
ms/sent: 20 ms)
Total 383.2
Table 2-38 Calculation
The calculated required performance of 383.2 points is less than the total performance of 980
points that the STMI2 board can provide. The configuration is feasible.
2.6.5 Maximum Number of Devices for Special Cases

This thumb rule can be used to calculate the maximum number of terminal devices for specific
configurations. The formula for the calculation is as follows:
Max No. of Points — #Trunks · 22.9· FLtg
#Terminal =
PointsTerminal · FTln
First, all resources required for other interfaces (e.g. trunks) are deducted from the maximum
number of points. This value is then divided by the points for a specific terminal device. The
result obtained thus indicates the maximum number of devices of that type.
If all terminal devices have a specific feature (e.g., CTI control), then the points for CTI-con-
trolled devices must be added to the points for the terminal device. The formula for CTI-con-
trolled terminal devices would thus be:
Max No. of Points — #Trunks · 22.9· FLtg
#Terminal =
(PointsTerminal + 1.7)· FTln
It is also possible to conceive of further tables, e.g., for a system with attendant consoles and
ACD agents. In this case, the points required for the trunks, attendant consoles and ACD
agents must be deducted from the maximum number of points. The formula for the calculation
would thus be:
Max No. of Points — #Lines · 22.9· FLtg — #VPL · 252· FVPL — #ACD · 59· C
#Terminal =
PointsTerminal · FTln
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Technical Specifications for HiPath 3000
2.7 Technical Specifications for HiPath 3000
Table 2-39 Technical specifications
Maximum System HiPath 3800 HiPath HiPath HiPath HiPath

Values 3550 3350 3500 3300
Ringer Equivalence Basic cabinet = 2.6 A / 115 – 1.3 A / 115 – 2.6 A / 115 – 1.3 A / 115 –
Number (type plate) 6 A / 110 VAC, 230 VAC 230 VAC 230 VAC 230 VAC
3 A / 230 VAC
Expansion
cabinet =
8 A / 110 VAC,
4 A / 230 VAC
Line frequency 50 – 60 Hz
Power consump- Basic cabinet =
tion1 490 W
Expansion
cabinet =
720 W
Development of heat Basic cabinet =
(without work- 1500 kJ/h
1
points) Expansion
cabinet =
2200 kJ/h
Dimensions 490 x 440 x 430 450 x 460 x 450 x 460 x 155 x 440 x 88 x 440 x
(height x width x 200 128 380 380
depth in mm)
Height units for 19- 11 – – 4 2
inch cabinet assem-
bly
Weight Basic cabinet = 8 kg (17.62 6 kg (13.22 8 kg (17.62 6 kg (13.22
16.5 kg lb.) lb.) lb.) lb.)
Expansion Expansion cabinet rack
cabinet = (ECR): (Not for U.S. and
15.0 kg Canada):
(transport weight,
including backplane
● 6.5 kg without batter-
and cabinet feet) ies
● 17.5 kg with batteries
1 Specified values are worst case values, which are not suitable for estimating operating costs (energy costs). Actual con-
sumption values depend on the configuration and traffic and are generally considerably lower than the worst case values.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Interface-to-Interface Ranges
2.8 Interface-to-Interface Ranges
Telephone interface-to-interface ranges
Table 2-40 Telephone Interface-to-Interface Ranges (with J-Y (ST) 2x2x0.6, 0.6 mm
diameter)
Telephone interfaces Range in m Loop resistance

in ohms
ISDN-S0 point-to-point < 600 156
ISDN S0 extended bus connection < 400 104
ISDN S0 bus connection1 < 60 21
for the HiPath 3800 board STMD3
(Q2217)
< 120
for all other S0 boards
ISDN-S0 wall outlet to terminal < 10 –
Analog users < 2000 520
UP0/E exchange to host (master) < 1000 230
UP0/E host to client (master/slave) < 100 23
1 Board-specific
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 Direct 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-41 Cable Lengths for Trunk Connection and Direct CorNet-N/CorNet-NQ Direct
Wiring
Inter- Cable Diameter Attenuation Max. Cable

face per km Length
S0 ICCS cable 0.51 mm 7.5 dB 800 m
J-2Y(ST)Y4x2x0.51 LG ICCS at 96 kHz
Data5
Installation cable 0.6 mm 6.0 dB 1000 m
J-2Y(ST)Y 10x2x0.6 ST III BD at 96 kHz
S2M A-2Y0F(L)2Y 10x2x0.6 (full PE 0.6 mm 17 dB 350 m
insulation, filled) at 1 MHz
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Country-specific ring frequencies for analog subscriber line modules
2.9 Country-specific ring frequencies for analog subscriber line

modules
The following table contains the ring frequency settings necessary for the implementing analog
subscriber line modules in the various countries listed.
Table 2-42 Country-specific ring frequencies for analog subscriber line modules
Country Abbreviation Ring frequency (Hz)

Algeria ALG 25
Argentina ARG 25
Ethiopia ETH 25
Australia AUS 25
Belgium BEL 25
Brazil BRA 25
Federal Republic of Germany FRG 25
Burundi BUD 25
China CHN 25
Denmark DAN 25
Europe EU 25
Finland FIN 25
France FRA 50
Greece GRE 25
United Kingdom UK 25
Commonwealth of Independent States CIS 25
Hong Kong HGK 25
India IND 25
Indonesia IDS 25
Ireland IRL 25
Italy ITL 25
Cameroon CAM 25
Canada CAN 20
Kenya KEN 25
Congo CGO 25
Croatia CRO 25
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Country-specific ring frequencies for analog subscriber line modules
Table 2-42 Country-specific ring frequencies for analog subscriber line modules
Country Abbreviation Ring frequency (Hz)

Luxembourg LUX 25
Malaysia MAL 20
Morocco MOR 25
Mexico MEX 25
Netherlands NDL 25
Nigeria NIA 25
Oman OMA 25
Austria OES 25
Pakistan PAK 25
Philippines PHI 20
Poland POL 25
Portugal POR 25
Republic of South Africa RSA 25
Sweden SWD 25
Switzerland SWZ 25
Singapore SIN 25
Slovenia SLO 25
Spain SPA 25
South Korea KOR 20
Thailand THA 25
Czech Republic CRE 25
Turkey TRK 25
Hungary HUN 25
U.S. / Canada U.S. 20
Vietnam VIT 25
Zimbabwe ZIM 25
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Numbering plan
2.10 Numbering plan
2.10.1 Default Numbering for HiPath 3000/5000

HiPath 3000/5000 provides one default numbering plan for users.
Table 2-43 Default numbers for HiPath 3000/5000
Type of numbering Default station numbers

HiPath 3800 HiPath 3550 HiPath 3350 HiPath
HiPath 3500 HiPath 3300 ComScendo
Service
User station numbers 100-749 100-287 11-30 1000-1999
500-687 51-70
User direct inward dialing numbers 100-749 100-287 11-30 1000-1999
500-687 51-70
Trunk station number 7801-7920 7801-7920 801-816 7801-7920
Seizure codes 0 = ROW 0 = ROW 0 = ROW 0 = ROW
(external codes) 9 = U.S. 9 = U.S. 9 = U.S. 9 = U.S.
80-84 80-84 82-88 8000-8062
850-859 850-859
USBS station number 891 891 891 –
internal & direct inward dialing
IMOD station number 890 890 890 –
Digital modem 879 879 879 –
Group station numbers 350-499 350-499 31-50 3500-4499
internal & direct inward dialing 8600-8749
Internal attendant code number 9 = ROW 9 = ROW 9 = ROW 9 = ROW
(intercept position) 0 = U.S. 0 = U.S. 0 = U.S. 0 = U.S.
Attendant code extension (intercept 0 = ROW 0 = ROW 0 = ROW 0 = ROW
position) – = USA – = USA – = USA – = USA
Substitution for “*” 75 75 75 75
Substitution for “#” 76 76 76 76
Service codes *xxx *xxx *xxx –
#xxx #xxx #xxx
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Numbering plan
2.10.2 Internet Telephony Phone Numbers

HiPath 3000 supports connection to the Internet telephony service provider (ITSP) and, there-
fore, the use of Internet telephony.
For Internet telephony subscriber lines, each call number must be individually registered at the
ITSP. Up to thirty ITSP client user account IDs can be configured. The ITSP client user IDs and
the Internet telephony phone numbers are supplied by the provider once an Internet telephony
subscriber line is requested.
An Internet telephony system connection with DID is a connection that supports DID and for
which an ITSP, an Internet telephony system phone number, an ITSP system ID (SIP system
account) and a call number range with Internet telephony phone numbers are provided. Up to
30 Internet telephony phone numbers may be configured in the system.
The system is configured for connection to an ITSP via Web-Based Management (WBM) and
Manager E.
2.10.3 Numbering in networked systems

In private networks, station phone numbers, seizure codes, and service codes are assigned ac-
cording to a numbering plan provided by the customer.
HiPath 3000 supports the following numbering schemes:
● Closed numbering
Requires that all station numbers are unique within the network. Each station in the net-
work can reach another station by dialing their phone number.
● Open numbering
This means that stations are identified using a node number (PABX number) and their sta-
tion number. Stations in different nodes (systems) may therefore share the same number.
● M.164 numbering
The numbering can be open or closed. A node number is not required. The stations can
be reached via their public number, i.e. their E.164 number. Each station is represented
by its E.164 number which can be displayed optimally. The advantage of the E.164 num-
bering is that the station can be reached via a number and no node number is required.
The same numbering plan must be selected for all networked systems (nodes).
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Technical Specifications and Compliance to HiPath 3000
2.11 Technical Specifications and Compliance to HiPath 3000
2.11.1 CE Compliance (not for U.S.)

The systems conform to the following guidelines and standards:
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)
2.11.2 Compliance with US and Canadian Standards (for U.S. and

Canada only)
Table 2-44 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 Edition UL 60950-1 First Edition
CAN/CSA C22.2 CAN/CSA C22.2
No. 60950-1-03 No. 60950-1-03
FCC Part 15 Class A Class A Class B
subpart J
FCC Part 68 registra- AY3PF05BHIPATH3K8 AY3USA–25214–MF–E
tion AY3USA–25215–KF–E
Industry Canada CS– 267V-HP3800 267 8782A
03 certification
Ringer Equivalence 0.5B 0.4
Number (REN)
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

2.11.2.1 FCC Compliance
2.11.2.1.1 FCC Rules, Part 15

Each Siemens Enterprise Communications GmbH & Co. KG system discussed in this section,
except HiPath 3350, has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial envi-
ronment. This equipment generates, uses, and can radiate radio frequency energy. If installa-
tion and operation are not in line with the instructions in the manual, this can lead to disruptions
in radio communication. Operation of this equipment in a residential area is likely to cause
harmful interference, in which case the user will be required to correct the interference at his
own expense.
The HiPath 3350 has been tested and found to comply with the limits for a Class B digital de-
vice, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a residential instal-
lation. This equipment generates, uses, and can radiate radio frequency energy. If installation
and handling are incorrect, this can lead to disruptions in radio communication However, there
is no guarantee that interference will not occur in a particular installation. If this equipment does
cause harmful interference to radio or television reception, which can be determined by turning
the equipment off and on, the user is encouraged to try to correct the interference by one or
more of the following measures:
● Reorient or relocate the receiving antenna.
● Increase the distance between the equipment and receiver.
● Connect the equipment to an outlet on a circuit different from that to which the receiver is
connected.
● Consult the dealer or an experienced radio/TV technician for help.
2.11.2.1.2 FCC Rules, Part 68

Each Siemens Enterprise Communications GmbH & Co. KG system discussed in this section
complies with FCC Rules, Part 68. A label on the outside back of the cabinet identifies the FCC
registration number, the ringer equivalence number (REN), and other information. If requested,
this information must be given to the telephone company.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Disruption of the Network and T1

For networked systems using 1.544 Megabits per second (Mbps) T1 service, notify the tele-
communication company when the equipment is disconnected from the network. If any
Siemens Enterprise Communications GmbH & Co. KG system discussed in this section dis-
rupts the telephone network, the telecommunication company can discontinue your service
temporarily. If possible, the telecommunication company will notify you in advance. If this is not
possible, you will receive notification at the earliest possible opportunity. In this context you will
also be informed that you can lodge a complaint with the FCC.
Telephone Company Facility Changes

The telecommunication company is entitled to adapt its own equipment, devices, operating pro-
cedures, and processes as necessary; such modifications may impair the operation of your
equipment. If they do, you should be notified in advance so you can maintain uninterrupted tele-
phone service.
Nonlive Voice Equipment

Nonlive voice equipment, such as, music-on-hold devices and recorded announcements for
systems must be approved by Siemens Enterprise Communications GmbH & Co. KG and reg-
istered in accordance with the rules and regulations of Subpart C of the FCC Rules, Part 68; or
it must be connected through protective circuitry that is approved by
Siemens Enterprise Communications GmbH & Co. KG and registered in accordance with the
rules and regulations in Subpart C of the FCC Rules, Part 68.
REN
The Ringer Equivalence Number (REN) is used to determine the number of devices that can
be connected to a telephone line so that all the devices ring when that telephone number is
called. In most areas, but not all, the sum of the RENs of all devices connected to a line should
not exceed five. Contact the local telecommunication company to determine the maximum
REN for your calling area.
Newly Established Network Area and Exchange Codes

The off-net routing feature, also known as the least-cost routing (LCR) software feature, which
allows user access to the telephone network, must be configured to recognize newly estab-
lished network area codes and exchange codes as soon as they are placed in service.
Failure to reconfigure the customer premises equipment to recognize the new codes as they
are established restricts the customer and the customer’s employees from gaining access to
the network and to these codes.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Hearing Aid Compatibility

Telephones for emergency use and telephones installed in common areas such as lobbies,
hospital rooms, elevators, and hotel rooms must have handsets that are compatible with mag-
netically coupled hearing aids. Persons who are not in common areas also must be provided
with hearing-aid compatible handsets, if needed.
For the hearing impaired, all Siemens Enterprise Communications GmbH & Co. KG digital de-
vices manufactured after August 16, 1989, are hearing-aid-compatible and comply with FCC
Rules, Part 68, Section 68.316.
Programmed dial functions

When you program emergency numbers or make test calls to emergency numbers using
Siemens Enterprise Communications GmbH & Co. KG products with programmed dialer fea-
tures, stay on the line and briefly explain to the dispatcher the reason for the call before hanging
up. Perform these activities in off-peak hours, such as early morning or late evening.
Connecting Off-Premises Station Facilities

Customers who intend to connect off-premises station (OPS) facilities must inform the telecom-
munication company of the OPS class for which the equipment is registered and the connection
desired.
Direct Inward Dialing Answer Supervision

Customers operating any Siemens Enterprise Communications GmbH & Co. KG system dis-
cussed in this section without providing proper answer supervision are in violation of Part 68 of
the FCC rules.
● Each Siemens Enterprise Communications GmbH & Co. KG system discussed in this
section returns proper answer supervision to the public switched telephone network
(PSTN) when DID calls are:
– Answered by the called station.
– Answered by the attendant.
– Routed to a recorded announcement that can be administered by the customer.
● Each Siemens Enterprise Communications GmbH & Co. KG system discussed in this
section returns proper answer supervision on all DID calls forwarded to the PSTN. Permis-
sible exceptions are when:
– A call is unanswered
– A busy tone is received
– A reorder tone is received
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Equal Access Requirements

Call aggregators, such as hotels, hospitals, airports, colleges and universities, and so on, must
provide the end user with equal access to the carriers of the user’s choice. The current equal
access codes (also known as carrier access codes [CACs]) are 10xxx and 101xxxx, and 800/
888 and 950, where xxx or xxxx represents the carrier identification code.
To select the carrier of choice for a call, the user dials the equal access code before dialing the
called party number. Equal access is also obtained by dialing the 800/888 or 950 number of the
carrier of choice.
is capable of providing user access to interstate providers of operator services through the use
of equal access codes. Modifications by aggregators to alter these capabilities are a violation
of the Telephone Operator Consumer Services Improvement Act of 1990 and Part 68 of the
FCC Rules.
Electrical Safety Advisory

is fully compliant with FCC Rules and Regulations. It is nevertheless recommended that an al-
ternating current (AC) surge arrestor of the form and capability suitable for the model pur-
chased be installed in the AC outlet to which the system is connected. Consult your sales part-
ner to determine the surge protector requirements for your system.
2.11.2.2 Industry Canada Compliance

The following paragraphs describe requirements for and present information based on the In-
dustry Canada standards.
2.11.2.2.1 REN
The Ringer Equivalence Number (REN) defines how many devices can be connected to a tele-
phone line at the same time. The termination of an interface may consist of any combination of
devices subject only to the requirement that the sum of the RENs of all the devices does not
exceed five.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

2.11.2.2.2 Equipment Attachment Limitations

The Industry Canada label identifies certified equipment. This certification means that the
equipment meets certain telecommunications network protective, operational, and safety re-
quirements as described in the appropriate Terminal Equipment Technical Requirement docu-
ments. However, the Department offers no assurances that the devices will operate to the cus-
tomer’s complete satisfaction at all times.
Before installing this equipment, users should ensure that it is permissible to be connected to
the facilities of the local telecommunications company. The equipment must also be installed
using an acceptable method of connection. The customer should be aware that compliance
with these conditions may not prevent degradation of performance in some situations.
Repairs to certified equipment should be coordinated by a representative designated by the
supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunc-
tions, may give the telecommunications company cause to request the user to disconnect the
equipment.
Users should ensure, for their own protection, that the electrical ground connections of the pow-
er utility, telephone lines, and internal metallic water pipe system, if present, are connected to-
gether. This precaution may be particularly important in rural areas.
DANGER
7 Users should not attempt to make such connections themselves, but should contact
the electric inspection authority, or electrician, as appropriate.
2.11.3 SAFETY International

IEC 60950-1, first edition 2001, modified
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm
Environmental Conditions
2.12 Environmental Conditions
2.12.1 Electrical Operating Conditions

● Operating limits
Room temperature: + 5 ...+ 40 °C (41 ... 104 °F)
absolute humidity: 2 - 25 g H2O/m3
Relative humidity: 5 - 80%
● System ventilation is by convection only. Automatic ventilation is required when using the
HG 1500 in HiPath 3550 and HiPath 3350.
Caution
7 Avoid exposing the system to direct sunlight and heaters (excessive heat may dam-
age the system).
Systems covered with condensation must be dried before being used. Do not start
up the system until it has thoroughly dried.
2.12.2 Mechanical Operating Conditions

The systems are intended for stationary use.
A31003-H3570-S100-6-7620, 2008-04-01
sysdat.fm

Environmental Conditions
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Nur für den internen Gebrauch Boards for HiPath 3000
3 Boards for HiPath 3000
Caution
7 The system must be powered down and de-energized before removing or inserting
any boards in HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300 and before
removing or inserting the central boards in HiPath 3800.
DANGER (for U.S. only)

7 To protect against surge voltage caused by lightning, the following boards require
secondary protection when their lines leave the building where the main distribution
frame is housed:
● CBCC / CBRC
● DIU2U**
● SLA16N / SLA24N
● SLMA / SLMA8
● SLMAE8/SLMAE
● TIEL*
● TLANI2, TLANI4, TLANI8
● TLANI4R
● TMANI8
● TMC16
● TMDID / TMDID8
● TMDID2
● TMEW2
● TMGL4 / TMGL4R / TMGL8
● TMST1**
● TM2LP
● TST1**
● 8SLA
* If not connected to facility provider terminal equipment.
** When this module is connected to the public network, secondary protection must
be provided by the CSU (CSU: Customer Service Unit).
Caution (for Brazil only)

7 For protection against overvoltage due to lightning, the use of the lightning protection
strip with part number C39334-Z7052-C31 is absolutely mandatory. The power sup-
ply cable of the HiPath 3000 must be plugged into the lightning protection strip. The
lightning protection strip should be connected to the line voltage.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Boards for HiPath 3000 Nur für den internen Gebrauch

Overview
3.1 Overview
Functional overview of all boards used
Table 3-1 HiPath 3000 - Functional Overview of All Boards Used
Board Code number Model

Central Boards
CBCC S30810-Q2935-A401 HiPath 3550/HiPath 3350
CBRC S30810-Q2935-Z301 HiPath 3500/HiPath 3300
CBSAP S30810-Q2314-X HiPath 3800
CMA S30807-Q6931-X HiPath 3550/HiPath 3350/HiPath 3500/
HiPath 3300
CMS S30807-Q6928-X HiPath 3000
CUC S30777-Q750-X HiPath 3550
CUCR S30777-Q750-Z HiPath 3500
CUP S30777-Q751-X HiPath 3350
CUPR S30777-Q751-Z HiPath 3300
DBSAP S30807-Q6722-X HiPath 3800
IMODN S30807-Q6932-X100 HiPath 3000
LIM S30807-Q6930-X HiPath 3000
LIMS S30807-Q6721-X HiPath 3800
LUNA2 S30122-K7686-L1 HiPath 3800
S30122-K7686-M1
MMC S30122-X8002-X10 HiPath 3000
PSUP S30122-K5658-M HiPath 3350
RGMOD S30124-X5109-X HiPath 3800 (for selected countries only)
UPSC-D S30122-K5660-M300 HiPath 3550/HiPath 3350
UPSC-DR S30122-K7373-M900 HiPath 3500/HiPath 3300
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Overview

Peripheral Boards
Note: The HiPath 3550, HiPath 3350, HiPath 3500 and HiPath 3300 peripheral boards must
be firmly inserted into their slots; otherwise contact problems can cause board failure.
16SLA S30810-Q2923-X HiPath 3550/HiPath 3350 (not for U.S.)
4SLA S30810-Q2923-X200 HiPath 3550/HiPath 3350 (not for U.S.)
8SLA S30810-Q2923-X100 HiPath 3550/HiPath 3350
8SLAR S30810-K2925-Z HiPath 3500/HiPath 3300
CSAPE S30807-U6630-X HiPath 3800
DIU2U S30810-Q2216-X HiPath 3800 (for U.S. only)
DIUN2 S30810-Q2196-X HiPath 3800
HXGR3 S30810-K2943-Z HiPath 3500/HiPath 3300
HXGS3 S30810-Q2943-X HiPath 3550/HiPath 3350
IVMN8 S30122-H7688-X100 HiPath 3800
IVMNL S30122-H7688-X HiPath 3800
IVMP8 S30122-Q7379-X100 HiPath 3350 (not for U.S.)
IVMP8R S30122-K7379-Z100 HiPath 3300 (not for U.S.)
IVMS8 S30122-Q7379-X HiPath 3550/HiPath 3350
IVMS8R S30122-K7379-Z HiPath 3500/HiPath 3300
PBXXX S30810-Q6401-X HiPath 3800 (for selected countries only)
SLA16N S30810-Q2929-X100 HiPath 3550
SLA24N S30810-Q2929-X HiPath 3550
SLAD4 S30810-H2956-X100 HiPath 3550/HiPath 3350
SLAD8 S30810-H2956-X200 HiPath 3550/HiPath 3350
SLAD8R S30810-K2956-X300 HiPath 3500/HiPath 3300
SLC16N S30810-Q2193-X100 HiPath 3550 (not for U.S.)
SLCN S30810-Q2193-X300 HiPath 3800 (not for U.S.)
SLMA S30810-Q2191-C300 HiPath 3800
SLMA2 S30810-Q2246-X HiPath 3800 (for selected countries only)
SLMA8 S30810-Q2191-C100 HiPath 3800
SLMAE S30810-Q2225-X200 HiPath 3800
SLMAE8 S30810-Q2225-X100 HiPath 3800
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Overview

SLMO2 S30810-Q2168-X10 HiPath 3800
SLMO24 S30810-Q2901-X HiPath 3550
SLMO8 S30810-Q2168-X100 HiPath 3800
SLU8 S30817-Q922-A301 HiPath 3550/HiPath 3350
SLU8R S30817-K922-Z301 HiPath 3550/HiPath 3300
STLS2 S30817-Q924-B313 HiPath 3550/HiPath 3350 (not for U.S.)
STLS4 S30817-Q924-A313 HiPath 3550/HiPath 3350
STLS4R S30817-K924-Z313 HiPath 3500/HiPath 3300
STLSX2 S30810-Q2944-X100 HiPath 3550/HiPath 3350
STLSX4 S30810-Q2944-X HiPath 3550/HiPath 3350
STLSX4R S30810-K2944-Z HiPath 3500/HiPath 3300
STMD3 S30810-Q2217-X10 HiPath 3800
STMI2 S30810-Q2316-X100 HiPath 3800
TCAS-2 S30810-Q2945-X HiPath 3550 (for selected countries only)
TCASR-2 S30810-K2945-X HiPath 3500 (for selected countries only)
TLA2 S30817-Q923-Bxxx HiPath 3550/HiPath 3350 (not for U.S.)
TLA4 S30817-Q923-Axxx HiPath 3550/HiPath 3350 (not for U.S.)
TLA4R S30817-Q923-Zxxx HiPath 3550/HiPath 3300 (not for U.S.)
TLA8 S30817-Q926-Axxx HiPath 3550/HiPath 3350 (not for U.S.)
TLANI2 S30810-H2953-X1xx HiPath 3550/HiPath 3350
TLANI4 S30810-H2953-Xxx HiPath 3550/HiPath 3350
TLANI8 S30810-H2954-X1xx HiPath 3550/HiPath 3350
TLANI4R S30810-K2953-X2xx HiPath 3500/HiPath 3300
TM2LP S30810-Q2159-Xxxx HiPath 3800
TMANI8 S30810-Q2327-Xxx HiPath 3800
TMC16 S30810-Q2485-X HiPath 3800 (for selected countries only)
TMCAS S30810-Q2938-X HiPath 3550 (for selected countries only)
TMCAS-2 S30810-Q2946-X HiPath 3800 (for selected countries only)
TMDID S30810-Q2452-X HiPath 3800 (for U.S. only)
TMDID2 S30810-Q2197-T HiPath 3800 (for selected countries only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Overview

TMEW2 S30810-Q2292-X100 HiPath 3800
TMGL4 S30810-Q2918-X HiPath 3550/HiPath 3350 (for U.S. only)
TMGL4R S30810-K2918-Z HiPath 3500/HiPath 3300 (for U.S. only)
TMQ4 S30810-Q2917-X HiPath 3550/HiPath 3350 (for U.S. only)
TS2 S30810-Q2913-X300 HiPath 3550 (not for U.S.)
TS2R S30810-K2913-Z300 HiPath 3500 (not for U.S.)
TST1 S30810-Q2919-X HiPath 3550 (for U.S. only)
S30810-K2919-Z HiPath 3500 (for U.S. only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Overview

Options
ALUM4 S30817-Q935-A HiPath 3550/HiPath 3350
ANI4 S30807-Q6917-Axxx HiPath 3550/HiPath 3350 (for selected
countries only)
ANI4R S30807-Q6917-Z103 HiPath 3500/HiPath 3300 (for selected
countries only)
EVM S30807-Q6945-X HiPath 3550/HiPath 3350/HiPath 3500/
HiPath 3300
EXM S30817-Q902-B401 HiPath 3550/HiPath 3350
EXMNA S30817-Q6923-X HiPath 3550/HiPath 3350 (for U.S. only)
EXMR S30122-K7403-Z HiPath 3500/HiPath 3300
GEE12 S30817-Q951-Axxx HiPath 3550/HiPath 3350 (not for U.S.)
HOPE S30122-Q7078-X HiPath 3550/HiPath 3350 (for U.S. only)
S30122-Q7079-X
MPPI S30122-K5380-X200 HiPath 3550/HiPath 3350 (not for U.S.)
MPPI S30122-K7275-B HiPath 3000
OPAL C39195-A7001-B130 HiPath 3550/HiPath 3350
OPALR C39195-A7001-B142 HiPath 3500/HiPath 3300
PDMX S30807-Q5697-X200 HiPath 3800
PFT1/PFT4 S30777-Q539-X HiPath 3800 (not for U.S.)
S30777-Q540-X
PDM1 S30807-Q5692-X100 HiPath 3550/HiPath 3350/HiPath 3500/
HiPath 3300
REALS S30807-Q6629-X HiPath 3800
STBG4 S30817-Q934-A HiPath 3550/HiPath 3350 (France only)
STRB S30817-Q932-A HiPath 3550/HiPath 3350
STRBR S30817-Q932-Z HiPath 3500/HiPath 3300
UAM S30122-X7217-X HiPath 3550/HiPath 3350 (not for U.S.)
UAMR S30122-X7402-Z HiPath 3500/HiPath 3300 (not for U.S.)
V24/1 S30807-Q6916-X100 HiPath 3550/HiPath 3350 (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Overview
Overview of all board models used
Table 3-2 HiPath 3000 - Overview of All Boards Models Used

Board Code number Function
HiPath 3800
AMOM S30807-K5480-Xxxx Opto-electronic converter
CBSAP S30810-Q2314-X Central board
CMS S30807-Q6928-X Central board
CSAPE S30807-U6630-X cPCI cassette
DBSAP S30807-Q6722-X Central board
DIU2U S30810-Q2216-X Peripheral board (for U.S. only)
DIUN2 S30810-Q2196-X Peripheral board
IMODN S30807-Q6932-X100 Central board
IVMN8 S30122-H7688-X100 Peripheral board
IVMNL S30122-H7688-X Peripheral board
LIMS S30807-Q6721-X Central board
LUNA2 S30122-K7686-L1 Central board
S30122-K7686-M1
MMC S30122-X8002-X10 Central board
MPPI S30122-K7275-B Option
PBXXX S30810-Q6401-X Peripheral board (for selected countries
only)
PDMX S30807-Q5697-X200 Option
PFT1/PFT4 S30777-Q539-X Option (not for U.S.)
S30777-Q540-X
REALS S30807-Q6629-X Option
RGMOD S30124-X5109-X Central board (for selected countries
only)
SLCN S30810-Q2193-X300 Peripheral board (not for U.S.)
SLMA S30810-Q2191-C300 Peripheral board
SLMA2 S30810-Q2246-X Peripheral board (for selected countries
only)
SLMA8 S30810-Q2191-C100 Peripheral board
SLMAE S30810-Q2225-X200 Peripheral board
SLMAE8 S30810-Q2225-X100 Peripheral board
SLMO2 S30810-Q2168-X10 Peripheral board
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Overview

SLMO8 S30810-Q2168-X100 Peripheral board
STMD3 S30810-Q2217-X10 Peripheral board
STMI2 S30810-Q2316-X100 Peripheral board
TM2LP S30810-Q2159-Xxxx Peripheral board
TMC16 S30810-Q2485-X Peripheral board (for selected countries
only)
TMCAS-2 S30810-Q2946-X Peripheral board (for selected countries
only)
TMDID S30810-Q2452-X Peripheral board (for U.S. only)
TMDID2 S30810-Q2197-T Peripheral board (for selected countries
only)
TMEW2 S30810-Q2292-X100 Peripheral board
TMANI8 S30810-Q2327-Xxx Peripheral board
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Overview

HiPath 3550
ALUM4 S30817-Q935-A Option
ANI4 S30807-Q6917-Axxx Option (for selected countries only)
CBCC S30810-Q2935-A401 Central board
CMA S30807-Q6931-X Central board
CUC S30777-Q750-X Central board
EVM S30807-Q6945-X Option
EXM S30817-Q902-B401 Option
EXMNA S30817-Q6923-X Option (for U.S. only)
GEE12 S30817-Q951-Axxx Option (not for U.S.)
HOPE S30122-Q7078-X Option (for U.S. only)
S30122-Q7079-X
HXGS3 S30810-Q2943-X Peripheral board
IVMS8 S30122-Q7379-X Peripheral board
LIM S30807-Q6930-X Central board
MPPI S30122-K5380-X200 (not for Option
U.S.)
S30122-K7275-B
OPAL C39195-A7001-B130 Cable
PDM1 S30807-Q5692-X100 Option
SLA8N S30810-Q2929-X200 Peripheral board (not for U.S.)
SLA16N S30810-Q2929-X100 Peripheral board
SLAD4 S30810-H2956-X100 Peripheral board
SLA24N S30810-Q2929-X Peripheral board
SLC16N S30810-Q2193-X100 Peripheral board (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Overview

SLMO24 S30810-Q2901-X Peripheral board
SLU8 S30817-Q922-A301 Peripheral board
STBG4 S30817-Q934-A Option (France only)
STLS2 S30817-Q924-B313 Peripheral board (not for U.S.)
STLS4 S30817-Q924-A313 Peripheral board
STLSX2 S30810-Q2944-X100 Peripheral board
STLSX4 S30810-Q2944-X Peripheral board
STRB S30817-Q932-A Option
TCAS-2 S30810-Q2945-X Peripheral board (for selected countries
only)
TLA2 S30817-Q923-Bxxx Peripheral board (not for U.S.)
TLA4 S30817-Q923-Axxx Peripheral board (not for U.S.)
TLANI2 S30810-H2953-X1xx Peripheral board
TLANI4 S30810-H2953-Xxx Peripheral board
TMAMF S30810-Q2587-A400 Peripheral board (for selected countries
only)
TMCAS S30810-Q2938-X Peripheral board (for selected countries
only)
TMGL4 S30810-Q2918-X Peripheral board (for U.S. only)
TMQ4 S30810-Q2917-X Peripheral board (for U.S. only)
TST1 S30810-Q2919-X Peripheral board (for U.S. only)
TS2 S30810-Q2913-X300 Peripheral board (not for U.S.)
UAM S30122-X7217-X Option (not for U.S.)
UPSC-D S30122-K5660-M300 Central board
V24/1 S30807-Q6916-X100 Option (not for U.S.)
4SLA S30810-Q2923-X200 Peripheral board (not for U.S.)
8SLA S30810-Q2923-X100 Peripheral board
16SLA S30810-Q2923-X Peripheral board (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Overview

HiPath 3350
ALUM4 S30817-Q935-A Option
ANI4 S30807-Q6917-Axxx Option (for selected countries only)
CBCC S30810-Q2935-A401 Central board
CUP S30777-Q751-X Central board
EXM S30817-Q902-B401 Option
EXMNA S30817-Q6923-X Option (for U.S. only)
HOPE S30122-Q7078-X Option (for U.S. only)
S30122-Q7079-X
HXGS3 S30810-Q2943-X Peripheral board
IVMP8 S30122-Q7379-X100 Peripheral board (not for U.S.)
IVMS8 S30122-Q7379-X Peripheral board
MPPI S30122-K5380-X200 (not for Option
U.S.)
S30122-K7275-B
OPAL C39195-A7001-B130 Cable
PSUP S30122-K5658-M Central board
SLU8 S30817-Q922-A301 Peripheral board
STBG4 S30817-Q934-A Option (France only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Overview

STLS2 S30817-Q924-B313 Peripheral board (not for U.S.)
STLS4 S30817-Q924-A313 Peripheral board
STLSX2 S30810-Q2944-X100 Peripheral board
STLSX4 S30810-Q2944-X Peripheral board
STRB S30817-Q932-A Option
TLA2 S30817-Q923-Bxxx Peripheral board (not for U.S.)
TLANI4 S30810-H2953-Xxx Peripheral board
TMGL4 S30810-Q2918-X Peripheral board (for U.S. only)
TMQ4 S30810-Q2917-X Peripheral board (for U.S. only)
UAM S30122-X7217-X Option (not for U.S.)
UPSC-D S30122-K5660-M300 Central board
V24/1 S30807-Q6916-X100 Option (not for U.S.)
4SLA S30810-Q2923-X200 Peripheral board (not for U.S.)
8SLA S30810-Q2923-X100 Peripheral board
16SLA S30810-Q2923-X Peripheral board (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Overview

HiPath 3500
ANI4R S30807-Q6917-Z103 Option (for selected countries only)
CBRC S30810-Q2935-Z401 Central board
CUCR S30777-Q750-Z Central board
EXMR S30122-K7403-Z Option
HXGR3 S30810-K2943-Z Peripheral board
IVMS8R S30122-K7379-Z Peripheral board
OPALR C39195-A7001-B142 Cable
SLAD8R S30810-K2956-X300 Peripheral board
SLU8R S30817-K922-Z301 Peripheral board
STLS4R S30817-K924-Z313 Peripheral board
STLSX4R S30810-K2944-Z Peripheral board
STRBR S30817-Q932-Z Option
TCASR-2 S30810-K2945-X Peripheral board (for selected countries
only)
TLA4R S30817-Q923-Zxxx Peripheral board (not for U.S.)
TLANI4R S30810-K2953-X2xx Peripheral board
TMGL4R S30810-K2918-Z Peripheral board (for U.S. only)
TST1 S30810-K2919-Z Peripheral board (for U.S. only)
TS2R S30810-K2913-Z300 Peripheral board (not for U.S.)
UAMR S30122-X7402-Z Option (not for U.S.)
UPSC-DR S30122-K7373-M900 Central board
8SLAR S30810-K2925-Z Peripheral board
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Overview

HiPath 3300
8SLAR S30810-K2925-Z Peripheral board
ANI4R S30807-Q6917-Z103 Option (for selected countries only)
CBRC S30810-Q2935-Z401 Central board
CUPR S30777-Q751-Z Central board
EXMR S30122-K7403-Z Option
HXGR3 S30810-K2943-Z Peripheral board
IVMP8R S30122-K7379-Z100 Peripheral board (not for U.S.)
IVMS8R S30122-K7379-Z Peripheral board
OPALR C39195-A7001-B142 Cable
SLAD8R S30810-K2956-X300 Peripheral board
SLU8R S30817-K922-Z301 Peripheral board
STLS4R S30817-K924-Z313 Peripheral board
STLSX4R S30810-K2944-Z Peripheral board
STRBR S30817-Q932-Z Option
TLA4R S30817-Q923-Zxxx Peripheral board (not for U.S.)
TLANI4R S30810-K2953-X2xx Peripheral board
TMGL4R S30810-K2918-Z Peripheral board (for U.S. only)
UAMR S30122-X7402-Z Option (not for U.S.)
UPSC-DR S30122-K7373-M900 Central board
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2 Central boards
Caution
3.2.1 CBCC
Introduction
The CBCC board (Central Board with Coldfire Com) performs all central control and switching
functions for HiPath 3550 and HiPath 3350.
This description refers to the following versions of central CBCC board:

> ● CBCC S30810-Q2935-A401: Implemented from V6.0 Rel. 10 or later and V5.0
Rel. 15 or later.
Essential new functions:
– Integration of the function of the LIM submodule
– Increase of the ring voltage of analog station interfaces (T/R) to
approx. 65 Veff
– Discontinuation of the second V.24 interface (Option V24/1)
● CBCC S30810-Q2935-A301: Implemented in V5.0 or later.
Essential new function:
CLIP
Differences between both CBCC versions are indicated at the appropriate point in
the following description.
Subboards
The following subboards can be used depending on the application:
● Clock module CMA or CMS (optional)
● Multimedia card (MMC)
● IMODN integrated modem card new (optional)
● MPPI music on hold (optional)
● EVM entry voice mail (optional)
● LAN Interface Module LIM (optional, for CBCC S30810-Q2935-A301 only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Outputs, interfaces
● Ethernet (10 BaseT)/10 MBit) LAN interface, only in CBCC S30810-Q2935-A401
The interface can be used for administration via HiPath 3000 Manager E and CTI functions
(TAPI 120 V2.0). Bear in mind, however, that the number of BHCAs (Busy Hour Call At-
tempts = 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.
The ETHERNET-LAN interface is deactivated by the system software deactivated as soon
as an HG 1500 board is inserted.
● Eight digital UP0/E subscriber lines
For example, UP0/E workpoint clients or BS3/1 base stations for HiPath Cordless Office can
be connected here.
● Four analog T/R subscriber lines
For U.S. only: These interfaces do not support the connection of external extensions via
OPS (Off-Premises Station) signaling.
CBCC S30810-Q2935-A401: The interfaces supply a ring voltage of approx. 65 Veff.
CBCC S30810-Q2935-A301: The T/R interfaces supply a ring voltage of approx. 35 Veff.
Depending on the terminals connected, we cannot exclude the possibility of errors occur-
ring during 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
Please note that only one MPPI module may be connected. In other words, you
> can connect either MPPI S30122-K5380-X200 via X4 or MPPI S30122-K7275-
B via X19/X20.
● Options bus (O bus)
● V.24 interface
CBCC S30810-Q2935-A301: A second V.24 interface can be realized via the V24/1 option.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Switches and indicators

● Reset/reload switch
– Switch pressed < 5 s = Reset activated
– Switch pressed > 5 s = Reload activated (RUN LED off indicates that a reload is in
progress)
● RUN LED
LED status meaning is explained in the following table.
Table 3-3 CBCC - LED Status Meaning
RUN LED Meaning

Off No power
On Reset switch pressed briefly
Off Reset switch held down for more than 5 seconds (LED is extin-
guished to acknowledge that a reload has begun)
On System boot
Off Load operation: APS in SDRAM, loadware, and card data.
for 0.1 s
Flashing Normal operating state (zero load)1
0.5 s on/0.5 s off
Flashing MMC removed or defective
0.1 s on/0.1 s off
1 The flashing rhythm depends on the load. The higher the system load the slower the flashing rhythm.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Figure CBCC S30810-Q2935-A401
X5 2 X11 2 X6 2
V24/1
X7
X8 O bus
CMA
X14 X20 X15 X16
2
MPPI IMODN
CMS
2
X13 X17
X19
X27
X32
EVM
MMC
X30/31 X18
X1 X2 X12 X4 X3
1 1 2 1
8 x UP0/E 2 x S0, Reset/Reload- 4 x T/R

RJ45 Keys
MPPI or EXM
jacks
RUN LED V.24 interface, 9-pin SUB-D plug
LAN connector, 8-pin RJ45 jack
Figure 3-1 CBCC Board (S30810-Q2935-A401)
Disconnecting the battery buffer by unplugging the X27 jumper is necessary only for
> testing (module test at the factory). Disconnection does not necessarily delete the
customer database (CDB). To delete the CDB, use the reset switch.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Figure CBCC S30810-Q2935-A301
X5 2 X11 2 X6 2
V24/1
X7
X8 O bus
CMA
X14 X20 X15 X16
2
MPPI IMODN
CMS
2
X13 X17
X19
X27
X12
X32
EVM LIM
MMC
X30/31 X18
X1 X2 X4 X3
1 1 2 1
8 x UP0/E 2 x S 0, Reset/reload 4 x T/R

RJ45 switch
MPPI or EXM
jacks
RUN LED V.24 interface, 9-pin SUB-D plug
Figure 3-2 CBCC Board (S30810-Q2935-A301)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
X1 to X4 contact assignments
Table 3-4 CBCC - X1 to X4 Contact Assignments
Contact Connector X1 Connector X2 Connector X3 Connector X4

UP0/E T/R MPPI or EXM
1 UP0/E port 1b UP0/E port 5b T/R port 1a GND
2 UP0/E port 1a UP0/E port 5a T/R port 1b Not used
3 UP0/E port 2b UP0/E port 6b T/R port 2a Not used
4 UP0/E port 2a UP0/E port 6a T/R port 2b EXMCLK (512 kHz data cycle)
5 UP0/E port 3b UP0/E port 7b T/R port 3a EXMDIR (8 kHz frame cycle)
6 UP0/E port 3a UP0/E port 7a T/R port 3b EXMRES (high-active reset)
7 UP0/E port 4b UP0/E port 8b T/R port 4a EXMD (data line)
8 UP0/E port 4a UP0/E port 8a T/R port 4b EXMDET (detect signal)
9 – – – +5 V
10 – – – Not used
S0 interface assignment
Table 3-5 CBCC - S0 Interface Assignment (RJ45 Jacks)
Contact S0
X30 X31
1 – –
2 – –
3 S0 port 1, transmit + S0 port 2, transmit +
4 S0 port 1, receive + S0 port 2, receive +
5 S0 port 1, receive – S0 port 2, receive –
6 S0 port 1, transmit – S0 port 2, transmit –
7 – –
8 – –
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
V.24 interface assignment
Table 3-6 CBCC - V.24 Interface Assignment (SUB-D Plug)
X18, Pin Signal Description

1 – Not used
2 RxD A Receive data, channel A
3 TxD A Transmit data, channel A
4 – Not used
5 0V Ground
6 – Not used
7 RTS A Request to send, channel A
8 CTS A Clear to send, channel A
9 – Not used
LAN connector assignment

CBCC S30810-Q2935-A301: The Ethernet LAN interface is provided by the optional LIM sub-
board.
Table 3-7 CBCC - LAN Connector Assignment (RJ45 Jack)
Pin Signal Description

1 Tx + Transmit +
2 Tx – Transmit –
3 Rx + Receive +
4 – Not used
5 – Not used
6 Rx – Receive –
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Default Numbering Plan When Using CBCC in HiPath 3550
Table 3-8 Default Numbering Plan When Using CBCC in HiPath 3550
Station Int. call no. DID no. Port

UP0/E host 100 100 UP0/E 1
(master) 101 101 UP0/E 2
102 102 UP0/E 3
103 103 UP0/E 4
104 104 UP0/E 5
105 105 UP0/E 6
106 106 UP0/E 7
107 107 UP0/E 8
UP0/E client 500 500 UP0/E 1
(slave) 501 501 UP0/E 2
502 502 UP0/E 3
503 503 UP0/E 4
504 504 UP0/E 5
505 505 UP0/E 6
506 506 UP0/E 7
507 507 UP0/E 8
T/R 108 108 T/R 1
109 109 T/R 2
110 110 T/R 3
111 111 T/R 3
EVM 112 112 EVM-1
113 113 EVM-2
Line Code Port
S0 7801 S0 1-1
CO PP 7802 S0 1-2
7803 S0 2-1
7804 S0 2-2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Default Numbering Plan When Using CBCC in HiPath 3350
Table 3-9 Default Numbering Plan When Using CBCC in HiPath 3350

UP0/E host 11 11 UP0/E 1
(master) 12 12 UP0/E 2
13 13 UP0/E 3
14 14 UP0/E 4
15 15 UP0/E 5
16 16 UP0/E 6
17 17 UP0/E 7
18 18 UP0/E 8
(slave) 52 52 UP0/E 2
53 53 UP0/E 3
54 54 UP0/E 4
55 55 UP0/E 5
56 56 UP0/E 6
57 57 UP0/E 7
58 58 UP0/E 8
T/R 19 19 T/R 1
20 20 T/R 2
21 21 T/R 3
22 22 T/R 3
EVM 23 23 EVM-1
24 24 EVM-2
Line Code Port
S0 801 S0 1-1
CO PP 802 S0 1-2
803 S0 2-1
804 S0 2-2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
3.2.2 CBRC
Introduction
The CBRC board (Central Board Rack Com) performs all central control and switching func-
tions for HiPath 3500 and HiPath 3300.
This description refers to the following versions of central CBRC board:

> ● CBRC S30810-Q2935-Z401: Implemented from V6.0 Rel. 10 or later and V5.0
Rel. 15 or later.
Essential new functions:
– Integration of the function of the LIM submodule
– Increase of the ring voltage of analog station interfaces (T/R) to
approx. 65 Veff
● CBRC S30810-Q2935-Z301: implemented in V5.0 or later.
Essential new function:
CLIP
Differences between both CBRC versions are indicated at the appropriate point in
the following description.
Subboards
● Clock module CMA or CMS (optional)
● MMC multimedia card
● EVM entry voice mail (optional)
● LAN Interface Module LIM (optional, for CBRC S30810-Q2935-Z301 only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Outputs, interfaces
● Ethernet (10 BaseT)/10 MBit) LAN interface, only in CBRC S30810-Q2935-Z40
The interface can be used for administration via HiPath 3000 Manager E and CTI functions
(TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour Call At-
tempts = number of connection attempts during busy traffic hours) is restricted to 400 at a
The ETHERNET-LAN interface is deactivated by the system software deactivated as soon
as an HG 1500 board is inserted.
● Eight digital UP0/E subscriber lines
For example, UP0/E workpoint clients or BS3/1 base stations for HiPath Cordless Office can
be connected here.
● Four analog T/R subscriber lines
For U.S. only: These interfaces do not support the connection of external extensions via
OPS (Off-Premises Station) signaling.
CBRC S30810-Q2935-Z401: The interfaces supply a ring voltage of approx. 65 Veff.
CBRC S30810-Q2935-Z301: The T/R interfaces supply a ring voltage of approx. 35 Veff.
Depending on the terminals connected, we cannot exclude the possibility of errors occur-
ring during 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
● Options bus (O bus)
● V.24 interface
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards

● Reset/reload switch
– Switch pressed > 5 s = Reload activated (RUN LED off indicates that a reload is in
progress)
● RUN LED
LED status meaning is explained in the following table.
Table 3-10 CBRC - LED Status Meaning
RUN LED Meaning

off No power
Off Reset switch held down for more than 5 seconds (LED is extin-
guished to acknowledge that a reload has begun)
On System boot
off Load operation: APS in SDRAM, loadware, and card data.
for 0.1 s
0.5 s on/0.5 s off
0.1 s on/0.1 s off
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Figure CBRC S30810-Q2935-Z401
X5 2 X11 2 X6
X20
X8 O bus
CMA
MPPI/
X14 X15 X16 EXMR
IMODN
CMS X19
2
X13 X17
X27
X32
EVM
1 X3
MMC X18
1 X1 X9 X12
8 x UP0/E 2 x S 0, Reset/Reload- 4 x T/R

RJ45 Keys
jacks
RUN LED V.24 interface, 9-pin
SUB-D plug
Figure 3-3 CBRC Board (S30810-Q2935-Z401)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Figure CBRC S30810-Q2935-Z301
X5 2 X11 2 X6
X20
X8 O bus
CMA
MPPI/
X14 X15 X16 EXMR
IMODN
CMS X19
2
X13 X17
X27
X12
X32
EVM LIM
1 X3
MMC X18
1 X1 X9
8 x UP0/E 2 x S0, Reset/reload 4 x T/R

RJ45 switch
jacks
RUN LED V.24 interface, 9-pin
SUB-D plug
Figure 3-4 CBRC Board (S30810-Q2935-Z301)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
X1 and X3 contact assignments
Table 3-11 CBRC - X1 and X3 Contact Assignments

Contact Connector X1 Connector X3
UP0/E T/R
14 UP0/E port 1a T/R port 1a
15 UP0/E port 1b T/R port 1b
54 UP0/E port 5a –
55 UP0/E port 5b –
Table 3-12 CBRC - S0 Interface Assignment (RJ45 Jacks)

X9 S0 Port 1 X9 S0 Port 2
Pin Pin
11 – 21 –
12 – 22 –
13 S0 port 1, transmit + 23 S0 port 2, transmit +
14 S0 port 1, receive + 24 S0 port 2, receive +
15 S0 port 1, receive – 25 S0 port 2, receive –
16 S0 port 1, transmit – 26 S0 port 2, transmit –
17 – 27 –
18 – 28 –
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Table 3-13 CBRC - V.24 Interface Assignment (SUB-D Plug)
X18, Pin Signal Description

1 – Not used
2 RxD A Receive data, channel A
3 TxD A Transmit data, channel A
4 – Not used
5 0V Ground
6 – Not used
7 RTS A Request to send, channel A
8 CTS A Clear to send, channel A
9 – Not used
LAN connector assignment

CBRC S30810-Q2935-Z301: The Ethernet LAN interface is provided by the optional LIM sub-
board.
Table 3-14 CBRC - LAN Connector Assignment (RJ45 Jack) via LIM

1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Default Numbering Plan When Using CBRC in HiPath 3500
Table 3-15 Default Numbering Plan When Using CBRC in HiPath 3500

UP0/E host 100 100 UP0/E 1
(master) 101 101 UP0/E 2
102 102 UP0/E 3
103 103 UP0/E 4
104 104 UP0/E 5
105 105 UP0/E 6
106 106 UP0/E 7
107 107 UP0/E 8
(slave) 501 501 UP0/E 2
502 502 UP0/E 3
503 503 UP0/E 4
504 504 UP0/E 5
505 505 UP0/E 6
506 506 UP0/E 7
507 507 UP0/E 8
T/R 108 108 T/R 1
109 109 T/R 2
110 110 T/R 3
111 111 T/R 3
EVM 112 112 EVM-1
113 113 EVM-2
Line Code Port
S0 7801 S0 1-1
CO PP 7802 S0 1-2
7803 S0 2-1
7804 S0 2-2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Default Numbering Plan When Using CBRC in HiPath 3300
Table 3-16 Default Numbering Plan When Using CBRC in HiPath 3300

UP0/E host 11 11 UP0/E 1
(master) 12 12 UP0/E 2
13 13 UP0/E 3
14 14 UP0/E 4
15 15 UP0/E 5
16 16 UP0/E 6
17 17 UP0/E 7
18 18 UP0/E 8
(slave) 52 52 UP0/E 2
53 53 UP0/E 3
54 54 UP0/E 4
55 55 UP0/E 5
56 56 UP0/E 6
57 57 UP0/E 7
58 58 UP0/E 8
T/R 19 19 T/R 1
20 20 T/R 2
21 21 T/R 3
22 22 T/R 3
EVM 23 23 EVM-1
24 24 EVM-2
Line Code Port
S0 801 S0 1-1
CO PP 802 S0 1-2
803 S0 2-1
804 S0 2-2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.3 CBSAP
Introduction
The CBSAP board (Central Board Synergy Access Platform) performs all central control and
switching functions for HiPath 3800 (see Figure 3-5).
Capacity
● DTMF transmitters: 12
● DTMF receivers: 12
● Tone generators: 16
● Dial tone receivers: 4
Subboards
● CMS clock module (optional)
● Multimedia card (MMC)
● LIMS LAN interface module (optional)
Contains two Ethernet (10BaseT) LAN connectors (8-pin RJ45 jacks):
– LAN1 (administration via HiPath 3000/5000 Manager E and CTI functions)
– LAN2 (not assigned)
V.24 interfaces (9-pin SUB-D plug)

● Service (X50) = for connecting the service PC
● Application (X51) = for connecting a printer or application
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards

● Reset/reload switch:
– Switch pressed > 5 s = Reload activated (FAIL LED (red) off indicates that a reload is
in progress)
● Two LEDs indicating the board status:
– Run (green) = signals the current status of the CBSAP board (see Table 12-2)
– Fail (red) = error encountered
● Two LEDs for displaying the LAN interface status:
– LED1:
– Green = 100 Mbps online (link)
– Yellow = 10 Mbps online (link)
– Flashing = active
– LED2 (green):
– On = full-duplex (FDX)
– Off = half-duplex
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Diagram of CBSAP board
MMC IMODN
LIMS
CMS
MPPI
Figure 3-5 CBSAP Board (S30810-Q2314-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Front panel
Two LEDs indicating the board status:

● Run (green, flashing: 0.5 s on/0.5 s off) = correct, error-free op-
eration
● Fail (red) = error encountered
Reset/reload switch
Slide-in shelf for MMC
V.24 interfaces (9-pin SUB-D plug):

● Service (X50) = for connecting the service PC
● Application (X51) = for connecting a printer or application
Two Ethernet (10BaseT) LAN connectors (8-pin RJ45 jacks) via LIMS:
● LAN2 (not assigned)
● LAN1 (administration via HiPath 3000/5000 Manager E and CTI
functions)
The LAN interface status is indicated by two LEDs:
● LED1:
● LED2 (green):
Figure 3-6 CBSAP - Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Table 3-17 CBSAP - V.24 Interface Assignment (SUB-D Plug)
X50/X51, Pin Signal Description

1 DCD Data carrier detect (not used)
2 RxD Receive data
3 TxD Transmit data
4 DTR Data terminal ready (not used)
5 0V Ground
6 DSR Data send ready (not used)
7 RTS Request to send
8 CTS Clear to send
9 RI Ring indicator (not used)
LAN connector assignment via LIMS
Table 3-18 CBSAP - LAN Connector Assignment (RJ45 Jack)

1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
3.2.4 CMA
Caution
7 Place the central control board on a flat surface before inserting the CMA subboard.
The spacing bolts supplied guarantee the correct insertion of the subboard, so you
should always mount them (see Figure 3-7).
Otherwise you may damage the board.
Spacing bolts
Figure 3-7 CMA with Spacing Bolts
Introduction
The Clock Module ADPCM CMA (S30807-Q6931-X) is an optional subboard for the CBCC and
CBRC central control boards. The CMA module is needed for special HiPath Cordless Office
configurations.
All clock module small (CMS) functions are available when you insert a CMA module.
Please refer to Page 3-39 for recommendations on CMA module implementation.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.5 CMS
Caution
7 Place the central control board on a flat surface before inserting the CMS subboard.
Introduction
The Clock Module Small CMS (S30807-Q6928-X) is an optional subboard for the HiPath 3000
central control boards and guarantees greater clock accuracy.
Recommendations for CMA and CMS implementation

Table 3-19 provides recommendations for the implementation of CMA and CMS subboards
based on
● the type of network (ISDN S0, ISDN S2M or Ethernet/IP (10/100 BaseT))
● 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.
Trunk connection: Networked via: Trunk connection:

● No trunk or an- ● ISDN S0 ● No trunk or an-
alog trunk HiPath 3000 ● ISDN S2M HiPath 3000 alog trunk
● ISDN S0 ● ISDN S0
● ISDN S2M Master Slave ● ISDN S2M
System System(s)
● Ethernet/IP (10/
100 BaseT)
System 1 System(s)
1+n
Figure 3-8 Networking Options for HiPath 3000 Systems
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Table 3-19 Recommendations for CMA and CMS Implementation
Trunk Reference HiPath Cordless Trunk Reference HiPath Cordless

connec- clock Office connec- clock Office
tion no yes tion no yes
Networking via ISDN S0 lines:
MASTER system SLAVE system(s)
No trunk – – CMS or CMA No trunk Via – CMA2
or analog (see or analog ISDN S0
trunk Table 11-1) trunk networking
line
ISDN S0 Via CMS1 CMS or CMA ISDN S0 Via – CMA2
(not al- ISDN S0 (see (not al- ISDN S0
ways ac- trunk con- Table 11-1) ways ac- networking
tive) nection tive) line
(if active)
ISDN S0 Via CMS1 CMA2 ISDN S0 Via – CMA2
(always ISDN S0 (always ISDN S0
active) trunk con- active) trunk con-
nection nection
ISDN Via CMS1 CMA2 ISDN S2M Via – CMA2
S2M ISDN S2M ISDN S2M
trunk con- trunk con-
nection nection
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards

Networking via ISDN S2M lines:
MASTER system SLAVE system(s)
No trunk – – CMS or CMA No trunk Via – CMA2
or analog (see or analog ISDN S2M
trunk Table 11-1) trunk networking
line
ISDN S0 Via CMS1 CMS or CMA ISDN S0 Via – CMA2
(not al- ISDN S0 (see (not al- ISDN S2M
ways ac- trunk con- Table 11-2) ways ac- networking
tive) nection tive) line
(if active)
ISDN S0 Via CMS1 CMA2 ISDN S0 Via – CMA2
nection nection
ISDN Via CMS1 CMA2 ISDN S2M Via – CMA2
nection nection
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards

Networking via Ethernet/IP (10/100 BaseT) lines:
System 1 System(s) n+1
No trunk – CMS3 CMS or CMA No trunk – CMS3 CMS or CMA
or analog (see or analog (see
trunk Table 11-1) trunk Table 11-1)
ISDN S0 Via CMS3 CMS or CMA ISDN S0 Via CMS3 CMS or CMA
(not al- ISDN S0 (see (not al- ISDN S0 (see
ways ac- trunk con- Table 11-1) ways ac- trunk con- Table 11-1)
tive) nection tive) nection
(if active) (if active)
ISDN S0 Via – CMA2 ISDN S0 Via – CMA2
nection nection
ISDN Via – CMA2 ISDN S2M Via – CMA2
nection nection
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 11-1).
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.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.6 CUC and CUCR

The backplane comes in two versions:
● CUC (Connection Unit Com) S30777-Q750-X (Figure 3-9) - for use in HiPath 3550 (wall
housing)
● CUCR (Connection Unit Com Rack) S30777-Q750-Z (Figure 3-10) - for use in HiPath 3500
(19-inch housing)
CUC connector designations and slot assignments (S30777-Q750-X)
Reserved Slot 10 (X10)
CBCC
Slot 2 (8 x UP0/E) Slot 1 (2 x S0) Slot 3 (4 x T/R)
Peripheral board
Slot 6 (X40) Slot 7 (X50)
CUC
Peripheral board
Peripheral board
Slot 4 (X20) PSU/UPS (X1) Slot 5 (X30)
Figure 3-9 CUC Backplane (S30777-Q750-X)
CUCR connector designations and slot assignments (S30777-Q750-Z)
CBRC
Slot 2 (8 x UP0/E) Slot 1 (2 x S0) Slot 3 (4 x T/R)
Peripheral board
CUCR
Peripheral board
Peripheral board
Slot 4 (X20) PSU/UPS (X1) Slot 5 (X30)
Figure 3-10 CUCR Backplane (S30777-Q750-Z)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
3.2.7 CUP and CUPR

The backplane comes in two versions:
● CUP (Connection Unit Point) S30777-Q751-X (Figure 3-11) - for use in HiPath 3350 (wall
housing)
● CUPR (Connection Unit Point Rack) S30777-Q751-Z (Figure 3-12) - for use in HiPath
3300 (19-inch housing)
CUP connector designations and slot assignments (S30777-Q751-X)
Slot 2 (8 x UP0/E) Slot 1 (2 x S0) Slot 3 (4 x T/R) CBCC
Slot 4 (X20) PSU/UPS (X1) Slot 5 (X30) Peripheral board
CUP
Figure 3-11 CUP Backplane (S30777-Q751-X)
CUPR connector designations and slot assignments (S30777-Q751-Z)
Slot 2 (8 x UP0/E) Slot 1 (2 x S0) Slot 3 (4 x T/R) CBRC
Slot 4 (X20) PSU/UPS (X1) Slot 5 (X30) Peripheral board
CUPR
Figure 3-12 CUPR Backplane (S30777-Q751-Z)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.8 DBSAP
A prerequisite for expanding HiPath 3800 to a two-cabinet system is that the DBSAP (Driver
Board for Synergy Access Platform) board is mounted on the backplane of the expansion cab-
inet.
DBSAP ensures that the expansion cabinet receives HDLC, PCM and clock signals from the
basic cabinet. In addition, an ID signal is created which indicates the availability of an expan-
sion cabinet to the CBSAP.
Front Back
With 68-pin DB68 mini-jack for connect- With four jacks for plugging into the
ing the connection cable to the basic cab- backplane of the expansion cabinet
inet
Figure 3-13 DBSAP (S30807-Q6722-X)
The cable (C39195-Z7611-A10) is used as the connection cable between basic cab-
> inet (X201 jack) and expansion cabinet (DBSAP board). To ensure smooth opera-
tion, use only shielded cables with a maximum length of 1 m.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
DBSAP
Figure 3-14 DBSAP on the Backplane of the Expansion Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.9 IMODN
Caution
7 Place the central control board on a flat surface before inserting the IMODN sub-
board.
Introduction
The Integrated Modem Card New (IMODN - S30807-Q6932-X100) is an optional subboard for
HiPath 3000 central control boards.
It permits the use of remote service (analog mode up to 33.6 Kbps) over analog trunks without
an external modem.
IMODN is the compatible successor of IMODC. Functional differences between both modules
only exist in the higher transmission speed of the IMODN.
Loadable loadware
To avoid exchanging the IMODN subboard during a software upgrade, IMODN loadware is au-
tomatically updated in V4.0 SMR-08 and later.
Updating the IMODN loadware takes approx. 10 minutes beginning with the idle system status.
The red LED on the IMODN lights up repeatedly during the loading procedure. IMODN is ready
as soon as the green LED starts to flash.
If the IMODN loadware is not updated when the system is reset, the green LED starts to flash
approx. 10 seconds after the reset. The green LED continues to flash after the system boot.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
3.2.10 LIM
Caution
7 The LAN interface module must not be plugged in or out when the system is ener-
gized.
Place the central control board on a flat surface before inserting the LIM subboard.
Introduction
The LAN Interface Module LIM (S30807-Q6930-X) is an optional plug-in card for all central con-
trol boards of HiPath 3000 with the exception of the CBSAP (HiPath 3800), the CBCC (HiPath
3550, HiPath 3350) from S30810-Q2935-A401 or later, and the CBRC (HiPath 3500, HiPath
3300) from S30810-Q2935-Z401 or later.
The board provides an Ethernet (10BaseT/10 megabit) LAN connector via an 8-pin RJ45 jack.
The LIM module can be used for administration via HiPath 3000/5000 Manager E and for CTI
functions (TAPI 120 V2.0). Bear in mind, however, that the number of BHCAs (Busy Hour Call
Attempts = number of connection attempts during busy traffic hours) is restricted to 400 at a
In V6.0 or later, the system software deactivates an existing LIM module when an HG 1500
board is inserted. You cannot operate the LIM module and a HG 1500 board simultaneously in
a HiPath 3000.
RJ45 jack assignment
Table 3-20 LIM - RJ45 Jack Assignment

1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.11 LIMS
Caution
7 The LIMS module must not be plugged in or out when the system is energized.
Introduction
The LAN Interface Module for SAPP LIMS (S30807-Q6721-X) is an optional plug-in card for
the CBSAP central control board in HiPath 3800.
The board provides two Ethernet (10BaseT) LAN connectors 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 CTI
functions (TAPI 120 V2.0). However, bear in mind that the number of BHCAs (Busy Hour Call
Attempts = number of connection attempts during busy traffic hours) is restricted to 400 at a
In V6.0 or later, the system software deactivates an existing LIMS module when an STMI2
board is inserted. You cannot operate the LIMS module and an STMI2 board simultaneously in
a HiPath 3800.
Figure 3-15 CBSAP with LIMS Module Plugged In
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Table 3-21 LIMS - RJ45 Jack Assignment

1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.12 LUNA2
Introduction
LUNA2 (Line-powered Unit for Network-based Architecture No. 2) is used as the central power
supply in HiPath 3800. Depending on the system configuration up to three LUNA2 modules can
be used in the basic cabinet and up to four LUNA2 modules can be used in the expansion cab-
inet.
When expanding the HiPath 3800 to a two-cabinet system, two LUNA2 modules in the basic
cabinet and three LUNA2 modules in the expansion cabinet are enough to supply the maximum
configuration in Table 2-6. For information on how to calculate the number of LUNA2 modules
required, see Page 3-58.
You can use a third LUNA2 in the basic cabinet and a fourth in the expansion cabinet to ensure
error-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).
It is not possible to combine both LUNA2 operating modes redundant LUNA2 and
> battery charger LUNA2.
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. The
batteries 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.
● Connection of 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 re-
spective system cabinet.
Note: Only the V39113-W5123-E891 batteries are approved for use with the
Power Box PB3000.
● Connection of the battery cabinet BSG 48/38 using the 38 Ah/48 V battery set and battery
charger per HiPath 3800.
● Connection of 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 use with the
Power Box PB3000.
LUNA2 is used in all countries.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Part numbers
● LUNA2: S30122-K7686-L1, S30122-K7686-M1
For production-related reasons, two different LUNA2 modules with the same functions are
used. Technically identical, the two models have minor mechanical differences and are ful-
ly compatible with each other.
● Battery pack 4 x 12V/7 Ah: S30122-K5950-Y200
Weight (including batteries): 14.1 kg
Dimensions (length x width x height): 280 mm x 160 mm x 140 mm
(the connection cable for LUNA2 is part of the battery pack)
● Battery cabinet BSG 48/38: S30122-K5950-F300 (Page 3-59)
– Battery cable for BSG 48/38: C39195-Z7985-B10
(A battery cable is required for each system cabinet to be connected.)
– Battery 12V/38Ah: S30122-X5950-F320
(Four batteries necessary for each BSG 48/38.)
● Power Cabinet PB3000 (see Page 9-5)
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): up to 2 A
● Bridging times
Table 3-22 lists the maximum possible bridging times (emergency battery operation in
case of power failure) with battery pack S30122-K5950-Y200 ((48 V/7 Ah) and battery
housing BSG 48/38 (S30122-K5950-F300).
The Section 9.2.3.5, “UPS bridging time/charging time” contains details about bridging
times (emergency battery operation in the event of a power cut) of the Power Cabinet
PB3000.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Table 3-22 LUNA2 - Bridging Times with Battery Pack 48 V/7 Ah and Upright Battery
Housing BSG 48/38
System Power supply unit Load levels Maximum bridg-

ing time
HiPath 3800 2 x LUNA2 per system cabinet as 60 % nominal 25 min
PSU load
1 x LUNA2 per system cabinet as
battery charger
1 x battery pack 48 V/7 Ah per sys-
tem cabinet
HiPath 3800 5 x LUNA2 per system 60 % nominal 1 h 30 min
1 x BSG 48/38 upright battery load
housing per system
(LUNA2 is not required as a battery
charger as the BSG 48/38 battery
cabinet features a built-in charger.)
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-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Front view of LUNA2 with indicators and switches
LED for displaying the operating status
ON/OFF switch for secondary operating

voltages (system supply voltages)
LUNA2 can only be plugged in or out when
the system is switched off (switch = DC-OFF)
Switches for setting the operating mode
Removal tab
You can insert a screwdriver here to remove the
LUNA2 from the shelf.
Figure 3-16 LUNA2 Front Panel

● LED for displaying the operating status:
– Illuminated = LUNA2 is operating as power supply unit
– Flashing = LUNA2 is operating as a battery charger
– Off = at least one secondary operating voltage is outside the tolerance zone. In this
case
a) the voltage feed for LUNA2 may not be sufficient (an additional LUNA2 module is
required. For information on how to determine the number of LUNA2 modules re-
quired, see Page 3-58).
b) LUNA2 may be defective (the board must be replaced).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
● ON/OFF switch for secondary operating voltages (system supply voltages)
Caution
7 The switches for deactivating the secondary operating voltage (system supply
voltage) must be set to "DC-OFF" on all LUNA2s during maintenance work that
requires the system to be de-energized (for example, central board replace-
ment). The system is only in de-energized state if the switches on ALL
LUNA2s are set to “DC-OFF” position.
The system is only restarted if all LUNA2 switches are returned to the “DC-ON”
position.
● Switches for setting the operating mode (the operating mode must be set before the outer
panel is mounted):
– Mode 1: For use as power supply (LED illuminated)
– Mode 2a: For use as battery charger (LED flashing) with a charging voltage of
54.7 Vdc
– Mode 2b: For use as battery charger (LED flashing) with a charging voltage of
53.5 Vdc
From a technical viewpoint, there are no differences between the LUNA2 slots.
> A LUNA2 can be used in all slots, regardless of the selected operating mode.
To achieve a uniform LUNA2 system configuration worldwide, the following
rules should be observed:
● The power supplies that are used to supply the system directly should be
plugged in at LUNA2 slots 1, 2, and 3 (expansion cabinet only).
● At the LUNA2 slot marked “4”, the only power supplies that should be
plugged in are those
– used for LUNA2 redundancy (set to mode 1).
– used to charge batteries (set to mode 2a or mode 2b).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Slots
Push the LUNA2 power supply unit into the slots provided in the lower part of the system cab-
inet shelf until you hear a click (see Figure 4-19).
The power supply unit slots must be covered with the outer panel shown in Figure 3-17 (basic
cabinet) and in Figure 3-18 (expansion cabinet) before the system is started up.
Figure 3-17 LUNA2 slots in the basic cabinet (outer panel mounted)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Figure 3-18 LUNA2 Slots in the Expansion Cabinet (With Outer Panel Mounted)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Calculating the number of LUNA2 modules required

The number of LUNA2 modules required in relation to the number and type of peripheral
boards installed can be calculated using the following table.
Table 3-23 Determining the Number of LUNA2 Modules Required Per Cabinet
Number of peripheral PBXXX, STMI2, SLMA Number of

boards per cabinet and/or SLCN available LUNA2s required
per cabinet
Basic cabinet <5 no 1
<5 yes 2
5 no 2
5 yes 2
Expansion cabi- <5 no 1
net <5 yes 2
5 no 2
5 yes 3
10 no 3
10 yes 3
Examples for a one-cabinet system:
a) Basic cabinet with CBSAP and peripheral boards (without PBXXX, STMI2, SLMA or
SLCN)
● A single LUNA2 can supply a 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 PBXXX, STMI2, SLMA and/or
SLCN)
● Two LUNA2s are always required to supply a CBSAP, peripheral boards, and
PBXXX, STMI2, SLMA and/or SLCN.
● A third LUNA2 can be used as a battery charger or as a redundant LUNA2.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
BSG 48/38
You can use a BSG 48/38 battery cabinet instead of the battery pack to extend 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)
Technical specifications for the BSG 48/38 battery cabinet:
● Weight, including batteries: 75.9 kg
● Weight, excluding batteries: 18.3 kg
● Dimensions (length x width x height): 380 mm x 420 mm x 492 mm
The battery cabinet is designed for direct connection to the HiPath 3800 communication sys-
tem. The DC connection cable (C39195-Z7985-B10) included in delivery lets you connect any
system cabinet to the battery cabinet (do not connect to extension cables). Figure 3-20 is a
schematic display of the connections between the battery cabinet BSG 48/38 and HiPath 3800.
For detailed information about safety precautions as well as using and connecting
> the battery cabinet, refer to the installation and startup instructions that came with
the cabinet.
DC output 2:
–48-V special +– +–
outputs
BSG 48/38
DC output 1: 1
–48 V to HiPath 3800
2
AC input
230 V 3
Figure 3-19 Rear View of the BSG 48/38 Battery Cabinet (S30122-K5950-F300)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
HiPath 3800
Basic
cabinet
DC connection cable
100 - 240 Vac DC
BSG 48/38 50 - 60 Hz
AC
with batt.set
(38 Ah/48 V)
Expansion
cabinet
AC input 1
DC
Output 1, 2 DC connection cable
–48 V
3
100 - 240 Vac DC
50 - 60 Hz
AC
100 - 240 Vac

50 - 60 Hz
DC port
(X209)
AC outlet
(X211, X212 (basic cabinet only))
Note: For reasons of clarity, the system cabinets are shown sepa-
rately and without grounding.
Figure 3-20 Connections Between the BSG 48/38 Battery Cabinet and HiPath 3800
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.13 MMC
Introduction
The Multi Media Card (MMC) is a plug-in memory card for the central control boards and con-
tains the CDB backup and the relevant version-specific application processor software (APS).
Please note that the multimedia card (MMC) may only be replaced by another MMC approved
by Siemens Enterprise Communications GmbH & Co. KG. Cards that have not been approved
may have a different internal structure which can affect temporal access and certain features
(for example, CDB backup and APS transfer).
HiPath 3000 V5.0 (or later) only supports 64 MB multimedia cards (MMC64).
> MMC16 (16 MB) cards cannot be used.
The MMC is checked during system startup. If the system detects an MMC16, the
startup is aborted.
Table 3-24 Multimedia Card Models and Applications
MMC Part number Applica- Application in HiPath 3000

tion
HiPath 3550
HiPath 3800
HiPath 3350
HiPath 3350
HiPath 3500
HiPath 3300
HiPath 3300
with CBCC
with CBRC
in
countries
HiPath 3000 Version 4.0

MMC16 S30122-X7424-X ROW X X X X X X
(16 MB) (= empty basic MMC)
P50038-P1009-A816 X X
P50038-P1010-A816 X X X X
P50038-P1011-A816
MMC64 S30122-X8002-X10 ROW X X X X X X
P50038-P1010-A864 X X X X X X
P50038-P1011-A864
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Table 3-24 Multimedia Card Models and Applications
MMC Part number Applica- Application in HiPath 3000

tion
HiPath 3800
HiPath 3350
HiPath 3350
HiPath 3500
HiPath 3300
HiPath 3300
HiPath 3550
with CBCC
with CBRC
in
countries

MMC64 S30122-X8002-X10 ROW X X X X X X X
P50038-P1053-A816 X
P50038-P1054-A816 X X X X X X
MMC64 S30122-X8002-X10 ROW X X X X X X X
P30152-P1205-P2 X
P30152-P1205-P1 X X X X X X
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.14 PSUP
Introduction
The power supply PSUP S30122-K5658-M (Figure 3-21) is used in HiPath 3350 (wall housing).
The device plugs into a special 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 voltage generator 75 Vac, 20/25/50 Hz
● Partial voltages: +5 Vdc, –48 V
● Power consumption: 70 W
Caution
7 System voltage can only be switched on or off by plugging in or out the power
plug.
PSUP interfaces (S30122-K5658-M)
50 Hz
20 Hz Slide switch for setting ring frequency
25 Hz for following country settings:
1
● 50 Hz = France
To CUP X1 ● 20 Hz = U.S.
● 25 Hz = Germany + international
50
Power plug
Figure 3-21 PSUP Interface (S30122-K5658-M)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
3.2.15 RGMOD (for selected countries only)
Introduction
The external ring voltage generator RGMOD (S30124-X5109-X) is required for generating ring
voltages for the HiPath 3800 SLMA2 board. RGMOD is plugged in on the reverse of the back-
plane of the basic and/or expansion cabinet.
Danger
7 RGMOD must not be plugged in or out when the system is energized!
In normal mode, the ring voltage generator operates with voltages ranging from
+75 V to –170 V. The prescribed measures for protection against high voltage must
be taken when working on or close to the board.
When the ring voltage generator is removed, no ring tone is generated for the analog
telephones connected to the SLMA2.
A system cabinet can be fitted with a mix of SLMA, SLMA8 and SLMA2 boards. RG-
> MOD has no effect on SLMA and SLMA8, as these boards generate their own ring
voltage (35 Veff).
Setting the ring voltage and ring frequency

The ring voltage and ring frequency are set using jumpers.
Ring voltage Ring frequency Setting Standard

75 Veff 25 Hz 1 European standard
2
3
4
5
6
7
8
9
Table 3-25 RGMOD (for selected countries only) - Setting the Ring Voltages and Ring Fre-
quencies
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Ring voltage Ring frequency Setting Standard

65 Veff 25 Hz 1 Switzerland
2
3
4
5
6
7
8
9
75 Veff 50 Hz 1 France
2
3
4
5
6
7
8
9
85 Veff 20 Hz 1 U.S.
2
3
4
5
6
7
8
9
quencies
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Installing RGMOD
The RGMOD ring voltage generator is plugged in at the rear of the backplane.
● Basic cabinet
When using one or more SLMA2 boards in the basic cabinet, RGMOD must be plugged
into the 10-pin port X214 of the basic cabinet (see Figure 3-22).
X214
Figure 3-22 HiPath 3800 - Connectors and Jacks on Backplane of Basic Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
● Expansion cabinet
When using one or more SLMA2 boards in the expansion cabinet, RGMOD must be
plugged into the 10-pin port X214 of the expansion cabinet (see Figure 3-23).
X214
Figure 3-23 HiPath 3800 - Connectors and Jacks on Backplane of Expansion Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
3.2.16 UPSC-D
Introduction
The UPSC-D S30122-K5660-M300 board (Figure 3-24) is used in HiPath 3550 and HiPath
3350 (wall housing).
This module supports power supply and battery management functions. No other components
are required if it is operated as an AC power supply. To maintain short-term battery emergency
operation after a power failure (i.e. to use uninterruptible power supply functions), you must
also connect a battery pack.
Warning
7 The 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 (emergency
battery operation).
If a 48-V direct-current system is being used instead of a battery pack for DC power
supply, connection must be performed as for a battery pack. The 48-V direct-current
system must not exceed the limit of 60 V in operating mode, during loading, and
when an error occurs. The direct-current system must not be connected to the
UPSC-D if this cannot be guaranteed.
If the power supplied by the UPSC-D is insufficient, an external EPSU2 power supply can be
installed to provide additional power. For this, the EPSU2’s DC connection needs to be con-
nected to the special –48 Vdc input on the UPSC-D. The UPSC-D’s internal -48-V output is de-
activated when the external power supply is connected.
Licensed battery pack

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.
Danger
7 Do 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.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
● Battery charger: 4 x 12 V (40.8 V - 55.2 V)
● Bridging times
case of power failure) with battery pack S30122-K5928-X (48 V/1.2 Ah), depending on the
system.
Table 3-26 UPSC-D - Bridging Times with Battery Pack S30122-K5928-X (48 V/
1.2 Ah)
System Power sup- Load levels Maximum bridg-

ply unit ing time
HiPath 3350 UPSC-D Normal output load = 5 V: 3 A; 19 min
–48 V: 0.5 A; ringing approx. 2 VA
HiPath 3550 UPSC-D Normal output load 100 % = 5 V: 8 A; 6 min
HiPath 3550 UPSC-D Normal output load 60 % = 5 V: 4.8 A; 15 min
HiPath 3550 UPSC-D with Normal output load 100 % = 5 V: 8 A; 17 min
EPSU2 –48 V: 2.5 A (external via EPSU2);
ringing approx. 4 VA
(73.4°F).
● The batteries were fully charged when the measurement was started.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Diagram of UPSC-D
LED, yellow
Figure 3-24 UPSC-D (S30122-K5660-M300)
Slide switch for setting the ring frequency
LED,
25 Hz
20 Hz
50 Hz
green
Slide switch for activating/deactivating
1 the battery voltage (battery pack):
to ● up = off, battery voltage deactivated
LED, yellow (battery backup off)
CUC/ X1
CUP ● down = on, battery voltage activated
50 (battery backup on)
Ba
EP
Po
tte
we
SU
ry
rp
2
pa
lug
ck
Figure 3-25 UPSC-D (S30122-K5660-M300)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Caution
7 System voltage can only be switched on or off by plugging in or out the power plug.
If using an uninterruptible power supply, switch off the battery voltage first.
● LED, green: +5-V output voltage is available.
● LED, yellow: –48-V output voltage is supplied by the external EPSU2 power supply.
● Slide switch for setting the ring frequency:
– 25 Hz (Germany + international market)
– 20 Hz (U.S.)
– 50 Hz (France)
● Slide switch for activating and deactivating the battery voltage (battery pack):
– up = off, battery voltage deactivated (battery backup off)
– down = on, battery voltage activated (battery backup on)
Slide switch for activating and deac-

tivating the battery voltage (battery
pack)
LED, green: +5-V output voltage is

available
Slide switch for setting the ring fre-

quency
Figure 3-26 UPSC-D - Switches and LEDs
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Connectors
Connector for battery pack
Connector for EPSU2
Power plug
Figure 3-27 UPSC-D - Connectors
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
3.2.17 UPSC-DR
Introduction
The UPSC-DR S30122-K7373-M900 board (Figure 3-28) is used in HiPath 3500 and HiPath
3300 (19-inch housing).
This module supports power supply and battery management functions. No other components
are required if it is operated as an AC power supply. To maintain short-term battery emergency
operation after a power failure (i.e. to use uninterruptible power supply functions), you must
also connect a battery pack (see Section 9.2.4).
Warning
7 The 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 (emergency
battery operation).
If a 48-V direct-current system is being used instead of a battery pack for DC power
supply, connection must be performed as for a battery pack. The 48-V direct-current
system must not exceed the limit of 60 V in operating mode, during loading, and
when an error occurs. The direct-current system must not be connected to the
UPSC-DR if this cannot be guaranteed!
Danger
7 The UPSC-DR board is not insulated.
Consequently, a system using a UPSC-DR may only be operated with a closed
housing.
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 EBR
(see Section 9.2.4.1, “ECR Control, Display, and Connecting Elements”).
● by disconnecting the line cord attached to any connected batteries (installed in
the EBR (see Section 9.2.4, “Use ECR for HiPath 3500 and 3300 (not for USA
and Canada)”).
● by disconnecting the line cord attached to any connected EPSU2-R (installed in
the EBR (see Section 9.2.4, “Use ECR for HiPath 3500 and 3300 (not for USA
and Canada)”)
● by disconnecting the power plug.
If the power supplied by the UPSC-DR is insufficient, an external EPSU2-R power supply can
be installed to provide additional power. To do this, connect the DC port on the EPSU2-R 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.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Licensed batteries
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 the ECR!
Danger
7 Do not use 24-V batteries (S30122-K5403-X) in conjunction with UPSC-DR as an
explosive gas (hydrogen + oxygen) escapes when the battery is overloaded.
● Battery charger: 4 x 12 V (40.8 V - 55.2 V)
● Bridging times
case of power failure) with four batteries V39113-W5123-E891 (4 x 12 V/7 Ah batteries),
depending on the system.
Table 3-27 UPSC-DR - Bridging Times with four Batteries V39113-W5123-E891 (4 x
12 V/7 Ah Batteries)
System Power supply Load levels Maximum bridg-

unit ing time
HiPath 3300 UPSC-DR Normal output load = 5 V: 3 A; 7h 30min
HiPath 3500 UPSC-DR Normal output load 100 % = 5 V: 8 A; 1h 30min
HiPath 3500 UPSC-DR Normal output load 60 % = 5 V: 4.8 A; 2h 20min
HiPath 3500 UPSC-DR with Normal output load 100 % = 5 V: 8 A; 1h 30min
EPSU2-R –48 V: 3 A (external via EPSU2-R);
HiPath 3500 UPSC-DR with Normal output load 60 % = 5 V: 4.8 A; 2h 40min
EPSU2-R –48 V: 1.8 A (external via EPSU2-R);
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Table 3-27 UPSC-DR - Bridging Times with four Batteries V39113-W5123-E891 (4 x

12 V/7 Ah Batteries)
System Power supply Load levels Maximum bridg-

unit ing time
(73.4 °F).
● The batteries were fully charged when the measurement was started.
Diagram of UPSC-DR
LED, green
LED, yellow
Figure 3-28 UPSC-DR (S30122-K7373-M900)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Slide switch for setting the ring frequency

LED,
25 Hz
20 Hz
50 Hz
green
Slide switch for activating and deactivat-
1 ing the battery voltage (batteries):
to ● up = off, battery voltage deactivated
LED, yellow (battery backup off)
CUCR/CUPR X1
● down = on, battery voltage activated
50 (battery backup on)
Caution
The screw marked “ ” performs the
ground connection between UPSC-DR
and the 19-inch housing and must al-
ways be installed.
Battery connector as-

signment:
Connector for batteries +48 VBatt
and EPSU2-R (installed –48 VBatt
in the ECR) –48 V from EPSU2-R
+48 V from EPSU2-R
AC power
19-inch housing for HiPath 3500 and HiPath 3300
Figure 3-29 UPSC-DR (S30122-K7373-M900)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Central boards
Caution
7 System voltage can only be switched on or off by plugging in or out the power plug.
If using an uninterruptible power supply, switch off the battery voltage first.
● LED, green: +5-V output voltage is available.
● LED, yellow: –48-V output voltage is supplied by the external EPSU2-R power supply.
● Slide switch for setting the ring frequency:
– 25 Hz (Germany + international market)
– 20 Hz (U.S.)
– 50 Hz (France)
● Slide switch for activating and deactivating the battery voltage (batteries):
– up = off, battery voltage deactivated (battery backup off)
– down = on, battery voltage activated (battery backup on)
Slide switch for activating and deac-

tivating the battery voltage (batter-
ies)
LED, green: +5-V output voltage is

available
Slide switch for setting the ring fre-

quency
Figure 3-30 UPSC-DR - Switches and LEDs
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Central boards
Connectors
Connector for batteries and Power plug

EPSU2-R (installed in the ECR)
Figure 3-31 UPSC-DR - Connectors
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3 Peripheral boards
Caution
Note
The HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300 peripheral boards must be firmly
inserted into their slots; otherwise contact problems can cause board failure.
3.3.1 CSAPE
Introduction
In V6.0 or later, the cPCI box CSAPE (Central Shelf Access Point Emergency) can be installed
in the HiPath 3800 basic cabinet. The cPCI box contains two fan drawers, the AC power supply
unit ACPCI (part number S30124-X5166-X), and two slide-in shelves for the Embedded Appli-
cation Server EAS.
CSAPE is required when using HiPath All-in-One applications. Information about the supported
applications can be found in the HiPath All-in-One product documentation.
Installation of the cPCI box CSAPE in the system is a purely mechanical operation. There is no
electrical connection between the system and the cPCI box CSAPE. All communication be-
tween HiPath 3800 and HiPath All-in-One takes place over the IP network.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Front panel
Fan drawer
AC power supply unit ACPCI
Slide-in shelves for the Embed-

ded Application Server EAS
Fan drawer
Figure 3-32 CSAPE (S30807-U6630-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Slot
Figure 3-33 shows the slot for the cPCI box CSAPE in the basic cabinet. Please refer to Special
board attachments for installation information.
Figure 3-33 HiPath 3800 - Board Slots in the Basic Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.2 DIU2U (for U.S. only)
Introduction
The DIU2U (Digital Interface Unit 2 Universal) trunk module connects two digital trunks to Hi-
Path 3800 and in this way provides two primary rate interfaces (PRI) ISDN via T1 interfaces.
Connection types
● Fiber optic cable
The fiber optic cable is only connected via the front panel. The opto-electronic converter
AMOM must be used to connect a fiber optic cable to the 15-pin Sub-D jacks on the front
panel.
● Copper cable
The copper cable is connected to T1-CSU (Customer Service Unit) or DSU (Data Service
Unit) via the adapter cable (C39195-A7269-B625) shown in Figure 3-34.
Adapter cable C39195-A7269-B625
Figure 3-34 DIU2U (for U.S. only) Adapter Cable C39195-A7269-B625
Table 3-28 DIU2U (for U.S. only) - adapter cable assignment (C39195-A7269-B625)
15-pin Sub-D 50-pin Amphenol con- Function Color code

connector nector
Pin Pin
9 38 a-wire (T), transmit wht/blu
1 13 b-wire (R), transmit blu/wht
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-28 DIU2U (for U.S. only) - adapter cable assignment (C39195-A7269-B625)
15-pin Sub-D 50-pin Amphenol con- Function Color code

connector nector
Pin Pin
15 41 a-wire (T), receive wht/ora
8 16 b-wire (R), receive ora/wht
Front panel

● LED (green)
● LED (red)
Interface 1
Interface 2
Figure 3-35 DIU2U (for U.S. only) - Front Panel (S30810-Q2216-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
LED statuses and their meanings
Table 3-29 DIU2U (for U.S. only) - LED Statuses
Red LED Green Status Action

LED
Off Off Board not receiving power or not plugged in Check plug contact on
correctly. board.
Board is out of order.
On Off Board is receiving power and board test is
in progress.
Board is defective if status remains un- Replace the board.
changed (board test unsuccessful).
Loadware loading not successfully com- Replace the board.
pleted. Board is faulty.
Error detected on board. Check whether the board
Board is deactivated (not applicable to er- was deactivated using Hi-
rors detected by test loops) or board was Path 3000/5000 Manager
deactivated using HiPath 3000/5000 Man- E. If not, replace board.
ager E.
Flashing Off Loadware is being loaded.
Off On Board test completed successfully. Board is
OK (idle state).
Off Flashing At least one channel is activated.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.3 DIUN2
Introduction
The DIUN2 (Digital Interface Unit ISDN) provides 2 x 30 B channels (voice channels) for HiPath
3800. These are used
● for the S2M trunk connection (via NT).
● for S2M networking via S2M lines.
In HiPath 3000/5000 V5.0 and later, the B channels in the DIUN2 board are subject
> to license. Information on licensing can be found in Chapter 8.
Front panel

● LED (green)
● LED (red)
Interface 1
Interface 2
Figure 3-36 DIUN2 - Front Panel (S30810-Q2196-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-30 DIUN2 - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Connection types
● Fiber optic cable
The fiber optic cable is only connected via the front panel. The opto-electronic converter
AMOM must be used to connect a fiber optic cable to the 15-pin Sub-D jacks on the front
panel.
● Copper cable
The copper cable is only connected via the 15-pin Sub-D jacks on the front panel.
Notes:
● The connection type setting (fiber optic cable = DIUN2 mod., copper cable = DIUN2) is
made in HiPath 3000/5000 Manager E: System Status – System-wide – Card Config. –
Card Data. The connection type setting always applies to both interfaces (line 1 and line 2).
Connection types “DIUN2 mod.” and “DIUN2” cannot be used at the same time.
– Switch over to the connection type “DIUN2 mod.” with an AMOM adapter plugged in
and an existing fiber-optic connection: The fiber-optic path goes into operation imme-
diately if configured correctly.
– Switch over to the connection type “DIUN2 mod.” with an AMOM adapter plugged in
and without an existing fiber-optic connection: The fiber-optic path goes into operation
once the fiber-optic cable is plugged in if configured correctly. This can take up to three
minutes.
– Switch over to the connection type “DIUN2 mod.” without an AMOM adapter plugged
in: If the connection type is switched before the adapter is plugged in, you must per-
form a Reload Card with HiPath 3000/5000 Manager E after plugging in the adapter to
ensure that the adapter is detected by the DIUN2 board.
The DIUN2 board automatically performs a reload after switching from “DIUN2 mod.” to
“DIUN2” or vice versa to load the loadware for the operating mode.
● Both interfaces can be operated with different versions of the AMOM adapter (see AMOM
versions).
● Both interfaces can be operated with different protocols.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Jack assignment
Table 3-31 DIUN2 - 15-Pin Sub-D Jack Assignment
Pin Signal Signal description Direction

1 TTIP0 a-wire 120 ohms/75 ohms Output
4 LWLO0_FRONT Fiber optic (data output) Output
5 GND Ground return path for the +5- Input/output
V power supply
6 SCAN_IN0 Adapter test Input
7 SCAN_IN0 Adapter test Input
8 RTIP0 a-wire 120 ohms/75 ohms Input
9 TRING0 b-wire 120 ohms/75 ohms Output
10 +5V +5-V power supply Output
11 LWLI0_FRONT Fibre optic (data input) Input
V power supply
14 +5V +5-V power supply Output
15 RRING0 b-wire 120 ohms/75 ohms Input
No other pins used.
Assigning the system cable S30267-Z167-Axxx
Table 3-32 DIUN2 - Assigning the System Cable S30267-Z167-Axxx
Pin Function Color code

8 a-wire (T), transmit ora/wht
15 b-wire (R), transmit wht/ora
1 a-wire (T), receive blu/wht
9 b-wire (R), receive wht/blu
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.4 HXGS3, HXGR3
Introduction
HXGS3 and HXGR3 are VoIP gateway boards (VoIP - Voice over IP) that provide the function-
ality of HG 1500 in HiPath 3550, HiPath 3350 (HXGS3), HiPath 3500, and HiPath 3300
(HXGR3):
● Connection of a local LAN to the HiPath 3000 and connection with external LANs via the
ISDN and DSL interfaces of HiPath 3000.
● Support for the conventional functions of an ISDN and DSL router with the additional func-
tionality of a media gateway for the transfer of voice, fax and data.
● Forwarding of calls between IP-supported networks (LAN, intranet, Internet) and circuit-
switched networks (ISDN, PSTN).
Configuration is performed via Web-Based Management (WBM) which enables the administra-
tion of HG 1500 without any special software requirements.
Up to three boards can be used in HiPath 3550 and HiPath 3500.

> A maximum of one board is permitted in HiPath 3350 and HiPath 3300. Two boards
can be installed only if PDM1 is not being used.
When using an HXGS3 in HiPath 3350, pthe ower supply unit PSUP must be re-
placed with UPSC-D.
It is not possible to operate an HXGS3 or HXGR3 and an LIM module simultaneous-
ly in one system.
For information on configuration, refer to the HG1500 Administration Manual.
Caution
7 When using an HXGS3 board in the upper slot row in HiPath 3550 (slots 4, 6, 8) or
HiPath 3350 (slot 4), fan kit C39165-A7021-D3 must be installed for thermal reasons
(see Page 3-96)!
The fan kit is not necessary when using an HXGS3 board in the lower slot row (slots
5, 7, 9 in HiPath 3550 and slot 5 in HiPath 3350).
The fan kit is not longer required in systems equipped with the following modified
housing covers.
● HiPath 3550 with housing cover C39165-A7021-B52 or higher
For information on how to calculate the number of boards required for HG 1500, see
Section 2.6.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Board versions
Table 3-33 HXGS3/HXGR3 Board Versions
Board Part number Services DSPs B channels

DSP channels
HXGS3 S30810-Q2943-X Voice and Data 1 8
HXGR3 S30810-K2943-Z Voice and Data 1 8
Eight simultaneous Voice over IP connections are possible per DSP (Digital Signal Processor).
When using the extension module PDM1, the number of DSP channels for HXGS3
> and HXGR3 boards can be expanded by eight per board.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Extension modules
The HXGS3 and HXGR3 boards each have two HGA (HiPath Gateway Accelerator) slots,
which can be used to connect extension modules.
Table 3-34 HXGS3/HXGR3 - Extension Modules
Extension Part number Function Notes

module
PDM1 S30807-Q5692- Used for expansion for an addi- Maximum of one
(PMC DSP X100 tional eight DSP channels. PDM1 module possi-
modules) ble.
Figure 3-37 HXGS3 (S30810-Q2943-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Figure 3-38 HXGR3 (S30810-K2943-Z)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Interfaces/connectors
The HXGS3 and HXGR3 boards provide the following connectors:
● X1: 50-pin connector (edge connector) to the system
● X2: 8-pin RJ45 jack for LAN interface 1
● X3: 8-pin RJ45 jack for LAN interface 2
Caution
7 It is absolutely necessary to use a shielded Ethernet cable for LAN interfaces/
ports of the HXGS3 board.
Both LAN interfaces allow access to the Ethernet standard (IEEE 802.3) with 10 Mbps or
100 Mbps with automatic configuration. Manual configuration is also possible.
● X4: 9-pin Sub-D plug for V.24 interface
LAN connectors: 50
LAN 1 (X2) HGA slot 1 HGA slot 0
to
LAN 2 (X3) CUC/
X1 CUCR or
CUP/
CUPR
2
V.24 interface X4
Figure 3-39 HXGS3/HXGR3 - Interfaces
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
LAN interfaces
Table 3-35 HXGS3/HXGR3 - LAN Interface Assignment
Pin on Pin of RJ45 con- Signal

HXGS3/HXGR3 nector
(X2 and X3)
1 1 TDP (Transmit Data +)
3 2 TDN (Transmit Data –)
4 3 RDP (Receive Data +)
– 4 TT1 (Transmit Termination 1)
– 5 TT2 (Transmit Termination 2)
6 6 RDN (Receive Data –)
– 7 RT1 (Receive Termination 1)
– 8 RT2 (Receive Termination 2)
Signals TT1/2 and RT1/2 are not needed for transmitting data. They represent a signal termi-
nation of 100 ohms (known as a Bob Smith termination) for the two unused wire pairs in a 4-
pair twisted pair cable.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
V.24 interface
The V.24 cable (C30267-Z355-A25) is used for connecting the service PC.
The following settings must be chosen for a terminal or PC connected to the V.24 interface:
Transmission rate 19.200

Data bits 8
Parity bit None
Stop bits 1
Data flow control none
It is recommended that the local echo be deactivated on the connected terminal or PC.
Table 3-36 HXGS3/HXGR3 - Assignment of V.24 Interface X10
Pin Signal I/O Remark

1
2 RxD I Internal pull-up resistor in level switch (MAX211E)
3 TxD O
4 DTR O
5 0V Ground
6 DSR I Internal pull-up resistor in level switch (MAX211E)
7 RTS O
8 CTS I Internal pull-up resistor in level switch (MAX211E)
9
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Installing the fan kit for HXGS3 in HiPath 3550 or HiPath 3350
Caution
7 When using an HXGS3 board in the upper slot row in HiPath 3550 (slots 4, 6, 8) or
HiPath 3350 (slot 4), fan kit C39165-A7021-D3 must be installed for thermal rea-
sons.
The fan kit is not necessary when using an HXGS3 board in the lower slot row (slots
5, 7, 9 in HiPath 3550 and slot 5 in HiPath 3350).
The fan kit is not longer required in systems equipped with the following modified
housing covers.
Installing the fan kit marks the end of silent system operation. This must be taken
> into consideration when operating the system in an office environment.
When installing and connecting the fan kit, proceed as follows:
Step Activity
1. Disconnect system from power supply.
Caution
System voltage can only be switched off by taking out the power plug. Switch off
the battery voltage first for an uninterruptible power supply.
2. Open the system.
Warning
Grasp the housing cover by its outside walls only.
The shielding plate on the inside of the cover may have sharp edges which can
cause cuts (see Section 4.3.3.4, “Removing the System Housing Cover”).
3. Place fan kit [A] on the system shelf [B] as shown in Figure 3-40.
4. Push the two supplied securing clips over positions [C] illustrated in Figure 3-41
to attach the fan kit to the shelf.
5. Insert the connector of the fan kit cable into the port provided for it on an HXGS3
board as illustrated in Figure 3-42.
6. Close the system.
Warning
7. Start the system by plugging in the power plug. In the case of an uninterruptible
power supply, the battery must then be switched on.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
[A]
[B]
Figure 3-40 HXGS3 - Installation of the Fan Kit in HiPath 3550
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
[C]
Figure 3-41 HXGS3 - Securing Clips for Fan Kit
[D]
Figure 3-42 HXGS3 - Connection of the Fan Kit
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.5 IVMNL, IVMN8
Introduction
The IVMNL and IVMNL8 (Integrated Voice Mail New Large) boards allow you to use the HiPath
Xpressions Compact integrated voice mail functionality in HiPath 3800:
● IVMNL (S30122-H7688-X) = 24 ports
● IVMN8 (S30122-H7688-X100) = 8 ports
Up to 500 mailboxes are available with a total storage capacity of 100 hours. The boards can
also be used for Music on Hold and announcements.
HiPath Xpressions Compact supports a central voice mail functionality in a HiPath

> 3000/5000 network. All stations can use the central voice mail server.
HiPath Xpressions Compact may be used as a central announcement device in a
network system with V6.0 SMR-06 or later.
Optional administration of HiPath Xpressions Compact via the Ethernet (10/100BaseT) inter-
face in the front panel of the board is also possible.
For detailed information on HiPath Xpressions Compact, startup and administration, see the
manual for the product (see Section 1.6, “Information on the Intranet”: Electronic Documenta-
tion on SEN ESY Products).
Caution
7 For thermal reasons the IVMNL board may only be installed in the basic cabinet in
a HiPath 3800 19-inch cabinet installation.
Only one IVMNL or IVMN8 may be installed per HiPath 3800 system.
> In order to avoid inactive IVM channels (due to the slow IVM board boot-up), the fol-
lowing recommendations must be observed:
● IVMNL:
– Installing HiPath 3800 (Standalone): The IVMNL board is to be installed in
the last slot in the last system cabinet. If possible, the two slots in front
should be kept free.
– Installing HiPath 3800 (19-Inch Cabinet): The IVMNL board should be in-
stalled in the last slot in the basic cabinet. If possible, the two slots in front
should be kept free.
● IVMN8:
Standalone installation of the HiPath 3800 or 19" cabinet installation of the Hi-
Path 3800: The IVMN8 board should be installed in the last slot in the last sys-
tem cabinet. If possible, the two slots in front should be kept free.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Front panel

● LED (green)
● LED (yellow)
Lockout switch
Ethernet (10/100BaseT) interface (8-pin RJ45 jack)
Figure 3-43 IVMNL, IVMN8 - Front Panel (S30122-H7688-X -X100)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Lockout switch settings

● Pressed = free (default)
● Not pressed = locked: existing connections remain active, new connections are locked.
– The yellow LED lights up when all connections are ended and the board is effectively
locked.
– The yellow LED flashes when a lockout request is entered (via lockout switch or soft-
ware) but at least one call is still active.
To reset the board to the default state, press the lockout switch four times (off-on-off-on) during
the LED test at startup. This action cancels the LED test and both LEDs flash for approximately
five seconds in confirmation.
Table 3-37 IVMNL, IVMN8 - LED Statuses
LED LED Meaning Action

Yellow Green
During Startup and Initialization
Off Off 1 Boot procedure (lasts approx.
60 s)
On On 2 LED test (lasts approx. 10 s)
On Off 3 Lockout switch state signaling by Possibly check if board was de-
Off yellow LED (lasts approx. 5 s): activated using HiPath 3000/
● blocked = On 5000 Manager E or lockout
● free = Off switch.
Flashing Off 4 Hard disk test, application startup
(500/ (depending on hard disk status,
500 ms) lasts approx. 2 - 9 minutes)
Off On 5a Standby mode after successful
boot
On Off 5b Board locked or board error oc- Check whether board was deac-
curred tivated using HiPath 3000/5000
Manager E or lockout switch.
Change board if faulty.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-37 IVMNL, IVMN8 - LED Statuses

Yellow Green
During Operation
Off On Idle (no call)
Flashing Off At least one active port (call)
(500/
500 ms)
Flashing Flashing Lockout switch activated during a call
(500/ (500/
500 ms) 500 ms)
On Off Board locked or board error occurred Check whether board was deac-
tivated using HiPath 3000/5000
Flashing Off Upgrade process active
(100/
100 ms)
Table 3-38 IVMNL, IVMN8 - RJ45 Jack Assignment

1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.6 IVMP4, IVMP4R
Introduction
The following boards are used for the integrated voice mail functionality in HiPath Xpressions
Compact in V2.5 and later:
● IVMP4 (Integrated Voice Mail Point) S30122-Q7004-X13 - for HiPath 3550 and HiPath
3350 (wall housing)
● IVMP4R (Integrated Voice Mail Point Rack) S30122-K7004-Z13 - for HiPath 3500 and Hi-
Path 3300 (19-inch housing)
Up to 30 mailboxes are available with a total storage capacity of four hours. The boards can

Optional administration of HiPath Xpressions Compact is also possible via the board’s Ether-
net (10/100BaseT) interface.
Only one IVMP4 or IVMP4R may be installed per system.

> For thermal reasons, the IVMP4 board may only be used in slots 5, 7, and 9 (lower
slots) in HiPath 3550 (wall housing).
Only slot 5 can be used for the IVMP4 board in HiPath 3350 (wall housing).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Switches and LEDs
2 50
X4
10
Lockout switch X1 = con-
LED (green) nection to
X1 CUC/
LED (yellow)
X3 = LAN CUCR/
connector, X3 CUP/
8-pin RJ45 CUPR
jack 2
Figure 3-44 IVMP4, IVMP4R

locked.
To reset the board to the default state, activate the lockout switch twice within the first 10 s of
board startup.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Assignment of the RJ45 jack X3

The Ethernet (10/100BaseT) interface is accessed via the 8-pin RJ45 jack X3.
RJ45 Jack X3 Signal Description

Pin
1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
Table 3-39 IVMP4, IVMP4R - Assignment of the RJ45 Jack X3 (LAN Connector)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

Yellow Green
Off Off 1 Boot procedure (lasts approx. 60 s)
Off On 5a Standby mode after successful boot
On Off 5b Board locked or board error oc- Check whether board was de-
curred activated using HiPath 3000/
5000 Manager E or lockout
switch.
During Operation
(500/
500 ms)
(500/ (500/
500 ms) 500 ms)
On Off Board locked or board error occurred Check whether board was de-
activated using HiPath 3000/
switch.
(100/
100 ms)
Table 3-40 IVMP4, IVMP4R - LED Statuses
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.7 IVMP8 (not for U.S.) and IVMP8R (not for U.S.)
Introduction
● IVMP8 (Integrated Voice Mail Point) S30122-Q7379-X100 - for HiPath 3350 (wall housing)
● IVMP8R (Integrated Voice Mail Point Rack) S30122-K7379-Z100 - for HiPath 3300 (19-
inch housing)
Upgrading to HiPath Xpressions Compact V2.5 is not possible.
Music on Hold can be used in V4.0 SMR-7 or later and announcements in V5.0 or later.
In addition, the boards have an Ethernet (10/100BaseT) interface which can be used for HiPath
Xpressions Compact administration (fast APS transfer, backup and restore activities).
Only one IVMP8 or IVMP8R may be installed per system.

> Only slot 5 can be used for the IVMP8 board in HiPath 3350 (wall housing).

A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Packing protection covering

You must remove the red packing protection covering (cardboard block), shown in the following
picture, before starting up the board.
If it is necessary to transport the board again at a later time, for example, for servicing, you must
reattach the packing protection covering.
Figure 3-45 IVMP8 and IVMP8R (not for U.S.) - Packing Protection Covering
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Switches and LEDs
2 50
X4
10
X1 CUP/
LED (yellow)
X3 = LAN CUPR
connector, X3
8-pin RJ45
jack 2
X2 2
10
Figure 3-46 IVMP8, IVMP8R (S30122-Q7379-X100, -K7379-Z100) (not for U.S.)

locked.
board startup.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

The Ethernet (10/100BaseT) interface is accessed via the 8-pin RJ45 jack X3. The signals are
output simultaneously at the printed circuit connector X2.
Table 3-41 IVMP8 and IVMP8R (not for U.S.) - Assignment of the RJ45 Jack X3 (LAN
Connector)
RJ45 Jack X3 Signal Description Printed Circuit Con-

Pin nector X2
Pin
1 Tx + Transmit + 1
2 Tx – Transmit – 3
3 Rx + Receive + 7
4 – Not used
5 – Not used
6 Rx – Receive – 9
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-42 IVMP8 and IVMP8R (not for U.S.) - LED Statuses

Yellow Green
Off Off 1 Boot procedure (lasts approx. 8 -
12 s)
Off On 5a Standby mode after successful boot
On Off 5b Board locked or board error oc- Check whether board was de-
curred activated using HiPath 3000/
switch.
During Operation
Off Flashing At least one active port (call)
(500/
500 ms)
(500/ (500/
500 ms) 500 ms)
On Off Board locked or board error occurred Check whether board was de-
activated using HiPath 3000/
switch.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.8 IVMS8, IVMS8R
Introduction
● IVMS8 (Integrated Voice Mail Small) S30122-Q7379-X - for HiPath 3550 and HiPath 3350
(wall housing)
● IVMS8R (Integrated Voice Mail Small Rack) S30122-K7379-Z - for HiPath 3500 and Hi-
Music on Hold can be used in V4.0 SMR-7 or later and announcements in V5.0 or later.
In addition, the boards have an Ethernet (10/100BaseT) interface which can be used for HiPath
Xpressions Compact administration (fast APS transfer, backup and restore activities).
Only one IVMS8 or IVMS8R may be installed per system.

> For thermal reasons, the IVMS8 board may only be used in slots 5, 7, and 9 (lower
Slot 5 can only be used for the IVMS8 board in HiPath 3350 (wall housing).

A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

You must remove the red packing protection covering (cardboard block), shown in the following
picture, before starting up the board.
Figure 3-47 IVMS8, IVMS8R - Packing Protection Covering
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Switches and LEDs
2 50
X4
10
X1 CUC/
LED (yellow)
X3 = LAN CUCR/
connector, X3 CUP/
8-pin RJ45 CUPR
jack 2
X2 2
10
Figure 3-48 IVMS8, IVMS8R (S30122-Q7379-X, -K7379-Z)

locked.
board startup.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Front view of IVMS8R
X3 = LAN connector, 8-pin RJ45

jack
LED (yellow)
LED (green)
Lockout switch
Figure 3-49 IVMS8R - Front View (S30122-K7379-Z)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

The Ethernet (10/100BaseT) interface is accessed via the 8-pin RJ45 jack X3. The signals are
output simultaneously at the printed circuit connector X2.
Table 3-43 IVMS8, IVMS8R - Assignment of the RJ45 Jack X3 (LAN Connector)
RJ45 Jack X3 Signal Description Printed Circuit Con-

Pin nector X2
Pin
1 Tx + Transmit + 1
2 Tx – Transmit – 3
3 Rx + Receive + 7
4 – Not used
5 – Not used
6 Rx – Receive – 9
7 – Not used
8 – Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-44 IVMS8, IVMS8R - LED Statuses

Yellow Green
Off Off 1 Boot procedure (lasts approx. 8 -
12 s)
boot
During Operation
Off Flashing At least one active port (call)
(500/
500 ms)
(500/ (500/
500 ms) 500 ms)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.9 IVMS8N, IVMS8NR
Introduction
● IVMS8N (Integrated Voice Mail Small New) S30122-Q7379-X200 - for HiPath 3550 and Hi-
Path 3350 (wall housing)
● IVMS8NR (Integrated Voice Mail Small New Rack) S30122-K7379-Z200 - for HiPath 3500
and HiPath 3300 (19-inch housing)
Up to 500 mailboxes are available with a total storage capacity of 100 hours. The boards can

Optional administration of HiPath Xpressions Compact is also possible via the board’s Ether-
net (10/100BaseT) interface.
Only one IVMS8N or IVMS8NR may be installed per system.

> For thermal reasons, the IVMS8N board may only be used in slots 5, 7, and 9 (lower
Slot 5 can only be used for the IVMS8N board in HiPath 3350 (wall housing).

You must remove the red packing protection covering (cardboard block) before starting up the
board.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Switches and LEDs
2 50
X4
10
X1 CUC/
LED (yellow)
X3 = LAN CUCR/
connector, X3 CUP/
8-pin RJ45 CUPR
jack 2
Figure 3-50 IVMS8N, IVMS8NR

locked.
board startup.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

The Ethernet (10/100BaseT) interface is accessed via the 8-pin RJ45 jack X3.
RJ45 Jack X3 Signal Description

Pin
1 Tx + Transmit +
3 Rx + Receive +
4 – Not used
5 – Not used
7 – Not used
8 – Not used
Table 3-45 IVMS8N, IVMS8NR - Assignment of the RJ45 Jack X3 (LAN Connector)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

Yellow Green
Off Off 1 Boot procedure (lasts approx.
60 s)
boot
During Operation
(500/
500 ms)
(500/ (500/
500 ms) 500 ms)
(100/
100 ms)
Table 3-46 IVMS8N, IVMS8NR - LED Statuses
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.10 PBXXX (for selected countries only)
Introduction
The PBXXX (Peripheral Board XXX) module can be used in HiPath 3800 to support country-
specific CAS protocols.
The peripheral board slots on the HiPath 3800 are fitted with SIPAC 9 SU connec-
> tors. Since the PBXXX board has SIVAPAC connector strips, you will have to install
a SIVAPAC-SIPAC board adapter to be able to use it in HiPath 3800.
For information on this procedure, please see Section 4.2.5.5.
The PBXXX board converts the Euro-ISDN protocol on an S2M link into the Channel Associated
Signaling (CAS) protocol. The board functions only in conjunction with a DIUN2. There is no
direct connection between the PBXXX board and the system’s central control unit. The DIUN2
handles all signaling and data traffic.
The following combination options are possible:
● 1 x DIUN2 + 1 x PBXXX (see Page 3-125)
The PBXXX board must be plugged in on the left next to the DIUN2.
● 1 x DIUN2 + 2 x PBXXX (see Page 3-128)
The PBXXX boards must be plugged in on the left and right next to the DIUN2.
Up to four PBXXX boards can be installed in a HiPath 3800. For power supply reasons, a max-
imum of two PBXXX can be installed in a cabinet.
Administration of the CAS protocol converter

Use the ECGM tool for administration. For information on installing the software on the service
PC and on the required settings, see Page 3-288.
The C39195-Z7267-C2 cable can be used with a C39334-Z7080-C2 adapter (9-pin Sub-D jack
– 25-pin Sub-D jack) to connect the PBXXX (port M) and the service PC.
Notes on setup using HiPath 3000/5000 Manager E

Because the PBXXX card is not recognized by the hardware, offline configuration is required
with HiPath 3000/5000 Manager E. Either "DIUN2 + PBXXX" or "DIUN2 + 2PBXXX" should be
specified as the board to be configured. After configuration, the module data can be seen in
HiPath 3000/5000 Manager E. However, this is only visible in the software configuration, as the
PBXXX card was only configured on the software side.
Note: The offline configuration of the PBXXX serves solely to visualize the card with HiPath
3000/5000 Manager E.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Front panel
Seven-segment display
Port A (not used)
Port B (not used)
Port C (not used)
Port D (not used)
Port M (for connecting service PCs with the ECGM tool)
Figure 3-51 PBXXX (S30810-Q6401-X) (for selected countries) – Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
The board statuses listed in the following table are displayed.
Table 3-47 PBXXX (for selected countries only) – Seven-Segment Display
Display Meaning
Waiting for the PBXXX software download
Starting the PBXXX software download
PBXXX software download
Writing the PBXXX software/extender software to the flash memory
Loading the PBXXX software/extender software from the flash memory
Waiting for ECGM command (10 s)
Error while writing the software to flash memory
No software in the flash memory, waiting for reload
Flash memory erased (changing display)
PBXXX card active, Link 1 and Link 2 not active
Link 1 active, Link 2 not active
Link 1 not active, Link 2 active
Link 1 active, Link 2 active
Boot procedure
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Connection 1x DIUN2 + 1 x PBXXX

The figure below shows an example of a DIUN2 with PBXXX in the basic cabinet.
Connection cable DIUN2–

PBXXX: C39195-A7700-B7
Note: The cable must run under
the cabinet.
Cable to service PC
The CAS cable is connected to the backplane using an APPCU adapter (Figure 3-53).
Figure 3-52 HiPath 3800 Basic Cabinet – 1x DIUN2 + 1 x PBXXX
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
APPCU adapter (S30807-K5415-X) on

the backplane
CAS cable connection (see “Assigning

both CAS cables” on page 3-130)
Connection cable DIUN2–PBXXX:

C39195-A7700-B7
Figure 3-53 PBXXX (for selected countries only) – Connecting the CAS Cable using the
APPCU Adapter
The backplane of the PBXXX board must be closed with the adapter panels provided
> (C39165-A7050-C35, Figure 3-54).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Figure 3-54 PBXXX (for selected countries only) – Adapter Panel (C39165-A7050-C35)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Connection 1x DIUN2 + 2 x PBXXX

The figure below shows an example of a DIUN2 with two PBXXXs in the basic cabinet.

PBXXX: C39195-A7700-B7
Note: The cables must run
under the cabinet.
Cable to service PC
The CAS cable is connected to the backplane using two APPCU adapters (Figure 3-56).
Figure 3-55 HiPath 3800 Basic Cabinet – 1x DIUN2 + 2 x PBXXX
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
APPCU adapter (S30807-

K5415-X) on the backplane
CAS cable connections (see

“Assigning both CAS cables” on
page 3-130)

PBXXX: C39195-A7700-B7
Figure 3-56 PBXXX (for selected countries only) – Connecting the CAS Cable using Two
APPCU Adapters
The backplane of both PBXXX boards must be closed with the adapter panels pro-
> vided (C39165-A7050-C35, Figure 3-54).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Assigning both CAS cables

The following CAS cables are connected to the backplane via two APPCU adapters:
● symmetrical line (120 ohms), open end
Table 3-48 Assigning the CAS cable S30267-Z167-A100
15-pin Sub-D connector Function Color code

Pin
9 a-wire (T), transmit wht/blu
1 b-wire (R), transmit blu/wht
15 a-wire (T), receive wht/ora
8 b-wire (R), receive ora/wht
● coaxial line (75 ohms)
Table 3-49 Assigning the CAS cable S30267-Z80-A100
15-pin Sub-D connector Function Wire

Pin
15 a-wire (T), receive BNC line, cable 1
8 b-wire (R), receive BNC shield, cable 1
9 a-wire (T), transmit BNC line, cable 2
1 b-wire (R), transmit BNC shield, cable 2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.11 SLA8N (not for U.S.), SLA16N, SLA24N
Introduction
The following peripheral boards can be used in HiPath 3550:
● SLA8N (Subscriber Line Analog) with eight analog T/R interfaces (not for U.S.)
● SLA16N (16 analog interfaces)
● SLA24N (24 analog interfaces)
Switches and LEDs
H1 (green)
LEDs
H2 (red)
Lockout switch S1
(position = free, factory default)
Figure 3-57 SLA8N (not for U.S.), SLA16N, SLA24N (S30810-Q2929-X200, -X100, -X)
The operating mode (short or long line with the appropriate flash times) can be set up for each
subscriber line interface with HiPath 3000/5000 Manager E (the menu settings: Set up station
–> Station –> Param –> Flags).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-50 SLA8N (not for U.S.), SLA16N, SLA24N - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
Off Flashing At least one station is activated.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Cable and connector assignment (backplane, MDFU/MDFU-E, patch panel)
Table 3-51 SLA8N, SLA16N, SLA24N Assignment Cable 1 (SU Xx8) (not for U.S.)
SU con- SLA8N,
Color a-wire b-wire nector MDFU/ Patch Panel,
Pair SLA16N, Notes
group (tip) (ring) MDFU-E MW8 pin
BP: Xx8 SLA24N
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
red/grn 02 10a 10a 4
10 Port 10
grn/red 22 10b 10b 5
blk/blu 13 11a 11a 4
11 Port 11
blu/blk 33 11b 11b 5
blk/ora 04 12a 12a 4
12 Port 12 not
ora/blk 24 12b 12b 5 used
blk/grn 15 13a 13a 4 in
3 13 Port 13 SLA8N
grn/blk 35 13b 13b 5
blk/brn 06 14a 14a 4
14 Port 14
brn/blk 26 14b 14b 5
blk/grn 17 15a 15a 4
15 Port 15
yel/blu 08 16a 16a 4
4 16 Port 16
blu/yel 28 16b 16b 5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-52 SLA8N, SLA16N, SLA24N - Assignment Cable 2 (SU Xx9) (not for U.S.)
SU con- SLA8N,
Pair SLA16N, Notes
group (tip) (ring) MDFU-E MW8 pin
BP: Xx9 SLA24N
wht/blu
1 Free
blu/wht
wht/ora
2 Free
ora/wht
wht/grn
1 3 Free
grn/wht
wht/brn
4 Free
brn/wht
wht/grn
5 Free
grn/wht
red/blu
6 Free
blu/red
red/ora
7 Free
ora/red
red/grn
2 8 Free
grn/red
red/brn 11 17a 17a 4
9 Port 17
brn/red 31 17b 17b 5
10 Port 18
11 Port 19
blk/ora 04 20a 20a 4 not
12 Port 20 used
ora/blk 24 20b 20b 5
in
blk/grn 15 21a 21a 4 SLA8N,
3 13 Port 21
grn/blk 35 21b 21b 5 16N
14 Port 22
15 Port 23
4 16 Port 24
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-53 SLA16N, SLA24N - Assignment (SU Xx8, Xx9) (for U.S. only)
a-wire b-wire SU connector
# SLA16N, SLA24N CHAMP jack, MDF Notes
(tip) (ring) BP: Xx8 BP: Xx9
wht/blu 19 1a 1 1a
1 Port 1
blu/wht 39 1b 26 1b
wht/ora 38 2a 2 2a
2 Port 2
ora/wht 48 2b 27 2b
wht/grn 27 3a 3 3a
3 Port 3
grn/wht 47 3b 28 3b
wht/brn 16 4a 4 4a
4 Port 4
brn/wht 46 4b 29 4b
wht/grn 05 5a 5 5a
5 Port 5
grn/wht 45 5b 30 5b
red/blu 14 6a 6 6a
6 Port 6
blu/red 44 6b 31 6b
red/ora 23 7a 7 7a
7 Port 7
ora/red 43 7b 32 7b
red/grn 32 8a 8 8a
8 Port 8
grn/red 42 8b 33 8b
red/brn 11 9a 9 9a
9 Port 9
brn/red 31 9b 34 9b
red/grn 02 10a 10 10a
10 Port 10
grn/red 22 10b 35 10b
blk/blu 13 11a 11 11a
11 Port 11
blu/blk 33 11b 36 11b
blk/ora 04 12a 12 12a
12 Port 12
ora/blk 24 12b 37 12b
blk/grn 15 13a 13 13a
13 Port 13
grn/blk 35 13b 38 13b
blk/brn 06 14a 14 14a
14 Port 14
brn/blk 26 14b 39 14b
blk/grn 17 15a 15 15a
15 Port 15
grn/blk 37 15b 40 15b
yel/blu 08 16a 16 16a
16 Port 16
blu/yel 28 16b 41 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-53 SLA16N, SLA24N - Assignment (SU Xx8, Xx9) (for U.S. only)
# SLA16N, SLA24N CHAMP jack, MDF Notes
red/brn 11 17a 9 9a
17 Port 17
brn/red 31 17b 34 9b
red/grn 02 18a 10 10a
18 Port 18
grn/red 22 18b 35 10b
blk/blu 13 19a 11 11a
19 Port 19
blu/blk 33 19b 36 11b
blk/ora 04 20a 12 12a
20 Port 20 not
ora/blk 24 20b 37 12b used
blk/grn 15 21a 13 13a in
21 Port 21 SLA16N
grn/blk 35 21b 38 13b
blk/brn 06 22a 14 14a
22 Port 22
brn/blk 26 22b 39 14b
blk/grn 17 23a 15 15a
23 Port 23
grn/blk 37 23b 40 15b
yel/blu 08 24a 16 16a
24 Port 24
blu/yel 28 24b 41 16b
Technical connection conditions

● Maximum supply current: approximately 34 mA; maximum supply voltage: approximately
40 Vdc
● Ring voltage against negative supply voltage (a-wire (tip)/RING): two telephones maxi-
mum
● Range, see Section 2.8
● Loop current detection > 10 mA
● Ground button detection > 20 mA
● The transmission technology is set according to the specific country through the respec-
tively entered country code (for country initialization, see Chapter 5, “Starting Up HiPath
3000”).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.12 SLAD4, SLAD8, SLAD8R
Introduction
In HiPath 3000/5000 V6 R4 and V7 R4 and later, the following boards can be used to connect
analog subscribers (analog phones, group 3 fax, etc.):
● SLAD4 (Subscriber Line Analog with DuSLIC) S30810-H2956-X100 – for HiPath 3550 and
HiPath 3350
● SLAD8 (Subscriber Line Analog with DuSLIC) S30810-H2956-X200 – for HiPath 3550 and
HiPath 3350
● SLAD8R (Subscriber Line Analog with DuSLIC Rack) S30810-K2956-X300 – for
HiPath 3500 and HiPath 3300
The SLAD boards are compatible successor modules for the following boards:
● 4SLA (S30810-Q2923-X200)
● 8SLA (S30810-Q2923-X100)
● 8SLAR (S30810-K2925-Z).
These are being phased out and can no longer be ordered.
Main features
A DTMF code receiver is available for each analog interface (permits DTMF dialing at analog
telephones. This guarantees that all analog terminals connected are fully accessible.
These boards support calling name identification presentation (CLIP).
The connection of external extensions via OPS (Off-Premises Station) signaling is supported.
Ring voltage is generated by the power supply unit of the relevant system (UPSC-D for SLAD4
and SLAD8, UPSC-DR for SLAD8R). Information about country-specific ring frequency set-
tings is provided in Section 2.9.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
SLAD4, SLAD8 interfaces
1 50
T/R ports1-4 X2
8
to
X1
1 CUP/CUC
T/R ports 5-8
(not SLAD4) X3
8 2
Figure 3-58 SLAD4, SLAD8 – interfaces
Table 3-54 SLAD4, SLAD8 – assigning the ports
X2, Pin T/R ports 1-4 X3, Pin T/R ports 5-8
1 a1 1 a5
2 b1 2 b5
3 a2 3 a6
4 b2 4 b6
5 a3 5 a7
6 b3 6 b7
7 a4 7 a8
8 b4 8 b8
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
SLAD8R interfaces
50
Port 1
X1 to
T/R ports 1-8 CUPR / CUCR
(4-pin MW8
jacks)
2
Port 8
Figure 3-59 SLAD8R – interfaces
Table 3-55 SLAD8R – assigning the ports
RJ45 jack X2, Pin T/R ports 1-4 RJ45 jack X2, Pin T/R ports 5-8
1 14 a1 5 54 a5
15 b1 55 b5
2 24 a2 6 64 a6
25 b2 65 b6
3 34 a3 7 74 a7
35 b3 75 b7
4 44 a4 8 84 a8
45 b4 85 b8
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.13 SLC16N (not for U.S.)
Introduction
The SLC16N board is used in HiPath Cordless Office and connects base stations to
● HiPath 3550 (max. one SLC16N per system).
Chapter 11 contains basic information on the options available for the use of HiPath Cordless
Office.
For initial installation of HiPath Cordless Office, the HiPath cordless system number
> (DECT ID) must be ordered together with the SLC16N board.
Replacement boards are always delivered without a HiPath cordless system num-
ber.
Installing the first SLC16N and entering the HiPath cordless system number releas-
es 16 mobile telephones for use (PIN numbers are assigned). These mobile units
can then be logged on to the system. Other mobile telephones must be released be-
fore they can be used (see Section 10.15.5).
The base stations BS3/1 (S30807-H5482-X), BS3/3 (S30807-H5485-X), and BS3/S

> (X30807-X5482-X100) are being phased out and may no longer be ordered. You
must use the successor product BS4 (S30807-U5491-X) instead of the types
named.
You can still operate the base stations listed in HiPath 3000. Base stations BS3/1,
BS3/3, and BS4 can also be used in mixed mode.
Base stations must be clocked with a high degree of accuracy for HiPath Cordless Office. For
this, the subboard CMA or CMS must be plugged into the CBCC board (HiPath 3550) (see
Table 11-1).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Switches and LEDs
LED (green)
LED (red)
Lockout switch
(not pressed = free,
factory default)
Figure 3-60 SLC16N (S30810-Q2193-X100) (not for U.S.)
When you activate the lockout switch (press the switch), all idle mobile telephones
> are locked. Active mobile telephones are not locked until their release keys are
pressed.
Before unplugging the SLC16N board, always activate the lockout switch and wait
until the green LED stops flashing. This precaution ensures that none of the mobile
telephones are active.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-56 SLC16N (not for U.S.) - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
Off Flashing At least one subscriber line circuit is activat-
ed.
On On Board disabled. Check whether board
was deactivated using
the lockout switch.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-57 SLC16N (not for U.S.) - Cable Assignment

SU con- Patch Pan-
Color a-wire b-wire nector MDFU/
Pair SLC16N el, Notes
group (tip) (ring) MDFU-E
BP: Xx8 MW8 pin
wht/blu 19 1a 1a 4 BS 1:
1 Access 1
blu/wht 39 1b 1b 5 UP0/E port 1
wht/ora 38 2a 2a 4 BS x:
2 Access 2
ora/wht 48 2b 2b 5 UP0/E port x
wht/grn 27 3a 3a 4 BS x:
1 3 Access 3
grn/wht 47 3b 3b 5 UP0/E port x
wht/brn 16 4a 4a 4 BS x:
4 Access 4
brn/wht 46 4b 4b 5 UP0/E port x
wht/grn 05 5a 5a 4 BS x:
5 Access 5
grn/wht 45 5b 5b 5 UP0/E port x
red/blu 14 6a 6a 4 BS x:
6 Access 6
blu/red 44 6b 6b 5 UP0/E port x
red/ora 23 7a 7a 4 BS x:
7 Access 7
ora/red 43 7b 7b 5 UP0/E port x
red/grn 32 8a 8a 4 BS x:
2 8 Access 8
grn/red 42 8b 8b 5 UP0/E port x
red/brn 11 9a 9a 4 BS x:
9 Access 9
brn/red 31 9b 9b 5 UP0/E port x
red/grn 02 10a 10a 4 BS x:
10 Access 10
grn/red 22 10b 10b 5 UP0/E port x
blk/blu 13 11a 11a 4 BS x:
11 Access 11
blu/blk 33 11b 11b 5 UP0/E port x
blk/ora 04 12a 12a 4 BS x:
12 Access 12
ora/blk 24 12b 12b 5 UP0/E port x
blk/grn 15 13a 13a 4 BS x:
3 13 Access 13
grn/blk 35 13b 13b 5 UP0/E port x
blk/brn 06 14a 14a 4 BS x:
14 Access 14
brn/blk 26 14b 14b 5 UP0/E port x
blk/grn 17 15a 15a 4 BS x:
15 Access 15
grn/blk 37 15b 15b 5 UP0/E port x
yel/blu 08 16a 16a 4 BS x:
4 16 Access 16
blu/yel 28 16b 16b 5 UP0/E port x
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
System configuration using SLC16N

For information on the maximum possible system configuration of HiPath Cordless Office with
SLC16N boards, see Table 11-1.
Supplying power to base stations
Power is supplied to the base stations primarily via the internal PSU in the system in question.
● HiPath 3550
Subject to certain prerequisites, the system-internal PSU UPSC-D provides sufficient pow-
er for the operation of sixteen BS3/1s (one UP0/E each) or eight BS3/3s (two UP0/E each).
These prerequisites depend on the
– Line length and line type between SLC16N and base station.
The following specifications are based on line lengths of up to 1000 m and a line type
2x0.6 mm per UP0/E.
– Number and type of corded telephones connected to the system.
Table 3-58 through Table 3-59 show which telephone configurations work without ad-
ditional power supply.
Table 3-58 HiPath 3550 - Maximum Number of Corded Telephones Depending on the
Number of BS3/1 Base Stations Connected to SLC16N and BS4s con-
nected to SLC16N (not for U.S.)
Number Maximum number of corded telephones
of BS3/1s and BS4s
Analog telephones
connected via 1xUP0/E
to A0 1-10 11-20 21-30 31-40 41-50
SLC16N Optiset E and optiPoint 500 telephones
1 66 61 57 53 48 44
2 63 59 54 50 46 41
3 60 56 52 47 43 39
4 58 53 49 45 40 36
5 55 51 47 42 38 33
6 53 48 44 40 35 31
7 50 46 41 37 33 28
8 47 43 39 34 30 26
9 45 40 36 32 27 23
10 42 38 33 29 25 20
11 40 35 31 27 22 18
12 37 33 28 24 20 15
13 34 30 26 21 17 13
14 32 27 23 19 14 10
15 29 25 20 16 12 7
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Number of BS3/1 Base Stations Connected to SLC16N and BS4s con-
of BS3/1s and BS4s Analog telephones
to A0 1-10 11-20 21-30 31-40 41-50
SLC16N Optiset E and optiPoint 500 telephones
16 27 22 18 13 9 5
Number of BS3/3 Base Stations Connected to SLC16N and BS4s Con-
to SLC16N 0 1-10 11-20 21-30 31-40 41-50
Optiset E and optiPoint 500 telephones
1 64 60 56 51 47 42
2 60 56 52 47 43 39
3 57 52 48 43 39 35
4 53 48 44 40 35 31
5 49 44 40 36 31 27
6 45 40 36 32 27 23
7 41 37 32 28 23 19
8 37 33 28 24 20 15
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Options for supplying power to the base stations
For information on connecting the base stations, refer to the HiPath Cordless Office
> service manual.
Each base station must be connected to the SLC16N via the main distribution frame (MDFU or
MDFU-E).
Always route the UP0/E interfaces on the SLC16N via a splitting strip to arrest surges caused
to lightning. To do so, insert the polarized surge protectors (supplied) in the plugging locations
on the splitting strip from above.
The following options are available for supplying power to the base stations:
● Power supply via one UP0/E interface (Page 3-147)
● Power supply via two UP0/E interfaces (Page 3-148)
● Power supply via three UP0/E interfaces (Page 3-149), for BS3/3 only
If the power supplied by the UPSC-D (HiPath 3550) is insufficient, additional power can be sup-
plied by installing the external power supply EPSU2 (Page 3-149).
Signal propagation times differ due to the varying distances between the base stations, the sys-
tem, and the connection cables used (refer to the HiPath Cordless Office service manual). The
SLC16N board automatically balances these propagation times.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Base Station Power Supply via One UP0/E Interface

Connect the base station to a free interface on SLC16N as shown in Figure 3-61. Be careful
not to exceed the maximum connection cable lengths (1000 m for 2x0.6 mm).
HiPath 3550 BS3/1 for in-

doors
1
SLC16N CABLU UP0/E
2
Splitting a
strip b
1
MDFU, MDFU-E
Figure 3-61 Base Station Power Supply via One UP0/E Interface (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Base Station Power Supply via Two UP0/E Interfaces

Connect the base station to two free interfaces on SLC16N as shown in Figure 3-62. Be careful
not to exceed the maximum connection cable lengths (1000 m for 2x0.6 mm).
Using two UP0/E interfaces increases the traffic capacity in BS3/3 base stations.
HiPath 3550 BS3/3 for in-

doors
2
SLC16N CABLU UP0/E1
3
4
UP0/E2
5
Splitting a
strip b
1
MDFU, MDFU-E
Figure 3-62 Base Station Power Supply via Two UP0/E Interfaces (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Base Station Power Supply via Three UP0/E Interfaces

Connect the base station to three free interfaces on SLC16N as shown in Figure 3-63. Be ca-
reful not to exceed the maximum connection cable lengths (1000 m for 2x0.6 mm).
The use of three UP0/E interfaces increases the traffic capacity in the base station.
HiPath 3550 BS3/3, BS4 for indoors
2
SLC16N CABLU UP0/E1
3
4
UP0/E2
5
6
UP0/E3
7
Splitting a
strip b
1
MDFU, MDFU-E
Figure 3-63 Base Station Power Supply via Three P0/E Interfaces (not for U.S.)
Additional UPSC-D power supply via EPSU2

If the power supplied by the UPSC-D (HiPath 3550) is insufficient, additional power can be sup-
plied by installing the external power supply EPSU2. To do this, connect the DC port on the
EPSU2 to the special DC input on the UPSC-D.
As described on the preceding pages, the base stations must be connected to one (BS3/1) two
(BS3/3) or three (BS3/3) free UP0/E interfaces on SLC16N.
If you need an additional external power supply for the 19-inch housing in HiPath 3500 or Hi-
Path 3300, you should use the EPSU2-R power supply. This is mounted in the ECR (see
Section 9.2.4).
Section 11.5, “Power-Related Capacity Limits” shows which telephone configurations manage
without an additional power supply and which configurations require an additional one.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
EPSU2 external power supply

The EPSU2 AC/DC converter is an external power supply unit for use when the UPSC-D is un-
able to provide sufficient power for the base stations and telephones at the HiPath 3550.
The external power supply EPSU2 comes in two versions:
● S30122-K7221-X1 - This version is always supplied with four built-in batteries. These bat-
teries guarantee approx. 30 minutes of bridging time in the event of a power failure.
● S30122-K7221-X2 - This version is supplied without batteries. To use this model’s uninter-
ruptible power supply function, four batteries must be ordered separately and installed.
The new EPSU2 model S30122-K7221-X2 is designed to replace S30122-

> K7221-X1.
Differences between the two models are indicated at the appropriate point in the
following description.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
DC port for UPSC-D

Note polarity. Housing cover
Battery fuse
LED 1 Mounting
screws
LED 2
AC port for 100 – 240 Vac
Figure 3-64 EPSU2 - Indicators and Ports
Table 3-60 EPSU2 - Explanation of Indicators and Ports
LED 1 LED 2 Description

(DC output) (AC input)
On On DC output and AC input voltages are OK.
Off On No DC voltage at output
(for example DC load short-circuited).
On Off No AC voltage at input
(power outage, circuit-breaker panel receiving battery power).
Off Off No AC input voltage (power outage) and batteries are empty, or
the battery fuse is defective or was removed (by turning it to the
left).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-60 EPSU2 - Explanation of Indicators and Ports
LED 1 LED 2 Description

Ports Description
Battery fuse Melting fuse 5 x 20 mm, 2.5 A/slow-blowing
AC port (input) IEC 320/16 (grounding power cable/IEC)
DC port (output) Screw terminal connections for insulated lines (0.5 – 2.5 mm2),
56 V, 140 W
● EPSU2 S30122-K7221-X1 = 2-wire power cable to UPSC-
D, pre-installed, soldered ends. Note polarity.
● EPSU2 S30122-K7221-X2 = 2-wire power cable to UPSC-
D, with Phoenix terminal block.
EPSU2 technical specifications
Table 3-61 EPSU2 - Technical Specifications
EPSU2 EPSU2
S30122-K7221-X1 S30122-K7221-X2
Scope of delivery ● EPSU2 AC/DC converter ● EPSU2 AC/DC converter
with four UPS batteries without batteries
loaded ● Operating instructions
● Operating instructions ● AC connecting cable (pro-
● AC connecting cable (protective grounding plug,
tective grounding plug, IEC-320 socket)
IEC-320 socket) ● DC cable to UPSC-D
● DC cable to UPSC-D (length = 2 m)
(length = 2 m)
AC power cable ● C39195-Z7001-C17 Euro angled
● C39195-Z7001-C20 GBR angled
AC power 100 - 240 Vac
Frequency range 47 to 63 Hz
Connected output 200 W
Output power consumption/ 140 W
nominal output
Mains/nominal voltage 54.2 V
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-61 EPSU2 - Technical Specifications
EPSU2 EPSU2
S30122-K7221-X1 S30122-K7221-X2
UPS batteries V39113-W5123-E891 V39113-W5123-E891
Four batteries are supplied Batteries are not included in
built-in. the scope of supply and must
be ordered separately.
Battery operation:
● Permitted batteries ● CSB/EVX-1270, Hitachi/HP6.5-12, Yuasa/NP6-12, Varta/
Manufacturer/type num- Noack 43720303, Sonnenschein/0719143200, Panasonic/
ber LCR12-7P
● Number of batteries ● 4 units, 12 V each
● Size (Ah) ● 7 Ah
● Nominal voltage ● 48 V (fully charged 54 V, discharge to 44 V)
● Overload protection ● Melting fuse 5 x 20 mm, 2.5 A/slow-blowing
Nominal current 2.5 A
Overload protection Electronic current limiting circuit
Ambient temperature In buildings, +5 to +45 °C (41 to 113 °F)
Humidity 95%, non-condensing
Cooling Natural convection
Protection IP 21 (DIN 40050)
Housing dimensions (W x D 250 x 114 x 317
x H in mm)
Weight approx. 14.1 kg (incl. batteries) approx. 4.1 kg (without batter-
ies)
Symbol CE
Personal safety, insulation EN60950 and IEC950
Grounding, shielding Protection class 1, output is floating against ground
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Installation notes
● The EPSU2 AC/DC converter is designed for installation indoors only.
● The unit is suitable only for mounting on the wall (vertically, with AC port on bottom).
● Always install the units in a dry, dust-free area where there is no danger of vibrations.
● Always make sure there is sufficient air circulation around the units. Do not block the ven-
tilation holes.
● When selecting the location, keep in mind the necessary lengths of the following cables:
– AC cable (grounding plug, IEC 320 socket)
– DC cable to UPSC-D, length = 2 m
Procedure: EPSU2 wall-mounting
Step Activity
1. Drill two holes for anchors (5 mm in diameter) in the wall, as shown in Figure 3-65.
Depending on the wall materials, you may have to use a different kind of attach-
ment, such as wood screws for timber walls.
2. Insert the anchors and insert two screws (3.5 mm in diameter), leaving 5 mm pro-
jecting from the wall.
3. Mount the EPSU2 onto the screws and tighten them all the way.
115 mm 102 mm 33 mm
317 mm
Figure 3-65 EPSU2 - Holes for Mounting on the Wall
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.14 SLCN (not for U.S.)
Introduction
The SLCN (Subscriber Line Module Cordless New) board is used in HiPath 3800 and connects
base stations to HiPath Cordless Office. There are 16 UP0/E ports available for this.
You can install up to four SLCN boards in one system.
Chapter 11 contains basic information on the options available for operating HiPath Cordless
Office.
Base stations must be clocked with a high degree of accuracy for HiPath Cordless Office. For
this, the subboard CMS must be plugged into the CBSAP board (see Table 11-1).
Front panel

● LED (red)
● LED (green)
Figure 3-66 SLCN (not for U.S.) (S30810-Q2193-X300) - LEDs in the Front Panel
To ensure sufficient shielding, provide the board with a shielding panel. For informa-
> tion on mounting the shielding panel, see Section 4.2.5.3.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-62 SLCN (not for U.S.) - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.
Cable and connector assignment

● For connecting to the SIVAPAC connector on the backplane: Table 3-63
● For connecting to the connector panels using RJ45 jacks: Table 3-64
● For connecting to the connector panels using SIPAC 1 SU connectors: Table 3-65
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-63 SLCN (not for U.S.) - SIVAPAC Connector Assignment on the Backplane
a-wire b-wire
Pair SIVAPAC connector SLCN MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17 9a 9a
9 Port 9
brn/red 18 9b 9b
red/grn 19 10a 10a
10 Port 10
grn/red 20 10b 10b
blk/blu 24 11a 11a
11 Port 11
blu/blk 25 11b 11b
blk/ora 26 12a 12a
12 Port 12
ora/blk 27 12b 12b
blk/grn 29 13a 13a
13 Port 13
grn/blk 30 13b 13b
blk/brn 31 14a 14a
14 Port 14
brn/blk 32 14b 14b
blk/grn 34 15a 15a
15 Port 15
grn/blk 35 15b 15b
yel/blu 37 16a 16a
16 Port 16
blu/yel 38 16b 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-64 SLCN (not for U.S.) - Assignment of Connector Panels with RJ45 Jacks
RJ45 jack
SLCN Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
4 8a
8
5 8b
4 9a
9
5 9b
4 10a
10
5 10b
4 11a
11
5 11b
4 12a
12
5 12b
4 13a
13
5 13b
4 14a
14
5 14b
4 15a
15
5 15b
4 16a
16
5 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-64 SLCN (not for U.S.) - Assignment of Connector Panels with RJ45 Jacks
RJ45 jack
SLCN Notes
No. Pin
4
17 Free
5
4
18 Free
5
4
19 Free
5
4
20 Free
5
4
21 Free
5
4
22 Free
5
4
23 Free
5
4
24 Free
5
Table 3-65 SLCN (not for U.S.) - Assignment of Connector Panels with SIPAC 1 SU Con-
nectors (Cable for Ports 1 - 16)
Color a-wire b-wire SU con- Patch Panel,
Pair SLCN MDFU-E Notes
Group (tip) (ring) nector MW8 pin
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Pair SLCN MDFU-E Notes
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
10 Port 10
11 Port 11
12 Port 12
3 13 Port 13
14 Port 14
15 Port 15
4 16 Port 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
System configuration using SLCN

For information on the maximum possible system configuration of HiPath Cordless Office with
the SLCN boards see Table 11-1.
SLCN board distribution in HiPath 3800 cabinets

You can install up to four SLCN boards in HiPath 3800. A system cabinet can be fitted with all
four SLCN boards.
To guarantee uninterrupted operation of the HiPath 3800, not more than two SLCN
> boards should be plugged in to a PCM segment. This condition must always be ob-
served. For information on PCM segment distribution, see Section 4.2.5.7.
One board slot should be kept free between two SCLN boards to prevent overheat-
ing.

Power is supplied to the base stations primarily via the internal PSU in the system in question.
If the correct number of LUNA2 modules was calculated, the system’s internal power supply
unit provides sufficient power to supply the HiPath Cordless Office system configuration spec-
ified in Table 11-1.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.15 SLMAE8, SLMAE
Introduction
The SLMAE8 and SLMAE (Subscriber Line Module Analog Enhanced) boards provide analog
T/R interfaces for use in HiPath 3800 V6.0 SMR-10 or later:
● SLMAE8 (S30810-Q2225-X100) = 8 analog T/R interfaces
● SLMAE (S30810-Q2225-X200) = 24 analog T/R interfaces
A code receiver is available for each analog interface (permits DTMF dialing at analog tele-
phones). This guarantees that all analog terminals connected are fully accessible.
These boards support calling name identification presentation (CLIP).
For U.S. only: The connection of external extensions via OPS (Off-Premises Station) signaling
is not supported.
The boards generate their own ring voltages (65 Veff) and do not require an external ring volt-
age generator.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Touch guard
Caution
7 The boards are fitted with a touch guard because the onboard heat sinks are ener-
gized. Do not remove this touch guard.
Figure 3-67 SLMAE8, SLMAE - Touch Guard
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Front panel

● LED (red)
● LED (green)
Figure 3-68 SLMAE8, SLMAE - LEDs on the Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-66 SLMAE8, SLMAE - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.

● For U.S. only: For connecting to the connector panels with CHAMP jack: Table 3-75
● For connecting to the connector panels using SIPAC 1 SU connectors: Table 3-76 and
Table 3-77
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-67 SLMAE8, SLMAE - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector SLMAE8, SLMAE MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/gry 9 5a 5a
5 Port 5
gry/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17 9a 9a
9 Port 9
brn/red 18 9b 9b
red/gry 19 10a 10a
10 Port 10
gry/red 20 10b 10b
blk/blu 24 11a 11a
11 Port 11
blu/blk 25 11b 11b
blk/ora 26 12a 12a
12 Port 12
ora/blk 27 12b 12b Not used
for
blk/grn 29 13a 13a SLMAE8
13 Port 13
grn/blk 30 13b 13b
blk/brn 31 14a 14a
14 Port 14
brn/blk 32 14b 14b
blk/gry 34 15a 15a
15 Port 15
gry/blk 35 15b 15b
yel/blu 37 16a 16a
16 Port 16
blu/yel 38 16b 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-67 SLMAE8, SLMAE - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector SLMAE8, SLMAE MDFU-E Notes
(tip) (ring)
yel/ora 43 17a 17a
17 Port 17
ora/yel 44 17b 17b
yel/grn 45 18a 18a
18 Port 18
grn/yel 46 18b 18b
yel/brn 47 19a 19a
19 Port 19
brn/yel 48 19b 19b
yel/gry 49 20a 20a
20 Port 20
gry/yel 50 20b 20b Not used
for
vio/blu 51 21a 21a SLMAE8
21 Port 21
blu/vio 52 21b 21b
vio/ora 53 22a 22a
22 Port 22
ora/vio 54 22b 22b
vio/grn 55 23a 23a
23 Port 23
grn/vio 56 23b 23b
vio/brn 57 24a 24a
24 Port 24
brn/vio 58 24b 24b
Table 3-68 SLMAE8, SLMAE - Connector Panel Assignment with RJ45 Jacks
RJ45 jack SLMA8,
Notes
No. Pin SLMAE
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-68 SLMAE8, SLMAE - Connector Panel Assignment with RJ45 Jacks
RJ45 jack SLMA8,
Notes
No. Pin SLMAE
4 8a
8
5 8b
4 9a
9
5 9b
4 10a
10
5 10b
4 11a
11
5 11b
4 12a
12
5 12b not used in
4 13a SLMAE8
13
5 13b
4 14a
14
5 14b
4 15a
15
5 15b
4 16a
16
5 16b
4 17a
17
5 17b
4 18a
18
5 18b
4 19a
19
5 19b
4 20a
20
5 20b not used in
4 21a SLMAE8
21
5 21b
4 22a
22
5 22b
4 23a
23
5 23b
4 24a
24
5 24b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-69 SLMAE8, SLMAE - Connector Panel Assignment with CHAMP Jack (for U.S.
only)
CHAMP jack SLMAE8, SLMAE Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9 9a 9 Ring
Port 9
34 9b 9 Tip
10 10a 10 Ring
Port 10
35 10b 10 Tip
11 11a 11 Ring
Port 11
36 11b 11 Tip
12 12a 12 Ring
Port 12
37 12b 12 Tip Not used for
13 13a 13 Ring SLMAE8
Port 13
38 13b 13 Tip
14 14a 14 Ring
Port 14
39 14b 14 Tip
15 15a 15 Ring
Port 15
40 15b 15 Tip
16 16a 16 Ring
Port 16
41 16b 16 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
only)
CHAMP jack SLMAE8, SLMAE Notes
17 17a 17 Ring
Port 17
42 17b 17 Tip
18 18a 18 Ring
Port 18
43 18b 18 Tip
19 19a 19 Ring
Port 19
44 19b 19 Tip
20 20a 20 Ring
Port 20 not
45 20b 20 Tip used
21 21a 21 Ring in
Port 21 SLMAE8
46 21b 21 Tip
22 22a 22 Ring
Port 22
47 22b 22 Tip
23 23a 23 Ring
Port 23
48 23b 23 Tip
24 24a 24 Ring
Port 24
49 24b 24 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-70 SLMAE8, SLMAE - Connector Panel Assignment with SIPAC 1 SU Connec-
tors (cable for ports 1 - 16)
Color a-wire b-wire SU con- SLMA8, Patch Panel,
Pair MDFU-E Notes
Group (tip) (ring) nector SLMAE MW8 pin
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/gry 05 5a 5a 4
5 Port 5
gry/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
red/gry 02 10a 10a 4
10 Port 10
gry/red 22 10b 10b 5
11 Port 11
12 Port 12 Not used
for
blk/grn 15 13a 13a 4 SLMAE8
3 13 Port 13
14 Port 14
blk/gry 17 15a 15a 4
15 Port 15
gry/blk 37 15b 15b 5
4 16 Port 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
tors (cable for ports 17 - 24)
Color a-wire b-wire SU con- SLMA8, Patch Panel,
Pair MDFU-E Notes
Group (tip) (ring) nector SLMAE MW8 pin
wht/blu
1 Free
blu/wht
wht/ora
2 Free
ora/wht
wht/grn
1 3 Free
grn/wht
wht/brn
4 Free
brn/wht
wht/gry
5 Free
gry/wht
red/blu
6 Free
blu/red
red/ora
7 Free
ora/red
red/grn
2 8 Free
grn/red
9 Port 17
10 Port 18
11 Port 19
12 Port 20 Not used
for
blk/grn 15 21a 21a 4 SLMAE8
3 13 Port 21
14 Port 22
15 Port 23
4 16 Port 24
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.16 SLMA, SLMA8
Introduction
The SLMA and SLMA8 (Subscriber Line Module Analog) boards provide analog T/R interfaces
for use in HiPath 3800:
● SLMA (S30810-Q2191-C300) = 24 analog T/R interfaces
● SLMA8 (S30810-Q2191-C100) = eight analog T/R interfaces
The boards generate their own ring voltages and do not require an external ring voltage gen-
erator.
Caution
7 The ring voltage is 35 Veff. Depending on the connected terminals, malfunctions may
occur (for example the MWI signal may not be recognized).
If a higher ring voltage is required, the SLMA2 board can be used with the RGMOD
ring voltage generator.
Front panel

● LED (red)
● LED (green)
Figure 3-69 SLMA/SLMA8 - LEDs on the Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-72 SLMA/SLMA8 - LED Statuses

LED
correctly. board.
in progress.
Board is deactivated (not applicable to er- was deactivated using
rors detected by test loops) or board was HiPath 3000/5000 Man-
deactivated using HiPath 3000/5000 Man- ager E. If not, replace
ager E. board.
OK (idle state).
ed.

Table 3-77
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-73 SLMA/SLMA8 - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector SLMA, SLMA8 MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17 9a 9a
9 Port 9
brn/red 18 9b 9b
red/grn 19 10a 10a
10 Port 10
grn/red 20 10b 10b
blk/blu 24 11a 11a
11 Port 11
blu/blk 25 11b 11b
blk/ora 26 12a 12a
12 Port 12
for
blk/grn 29 13a 13a SLMA8
13 Port 13
grn/blk 30 13b 13b
blk/brn 31 14a 14a
14 Port 14
brn/blk 32 14b 14b
blk/grn 34 15a 15a
15 Port 15
grn/blk 35 15b 15b
yel/blu 37 16a 16a
16 Port 16
blu/yel 38 16b 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-73 SLMA/SLMA8 - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector SLMA, SLMA8 MDFU-E Notes
(tip) (ring)
yel/ora 43 17a 17a
17 Port 17
ora/yel 44 17b 17b
yel/grn 45 18a 18a
18 Port 18
grn/yel 46 18b 18b
yel/brn 47 19a 19a
19 Port 19
brn/yel 48 19b 19b
yel/grn 49 20a 20a
20 Port 20
grn/yel 50 20b 20b Not used
for
vio/blu 51 21a 21a SLMA8
21 Port 21
blu/vio 52 21b 21b
vio/ora 53 22a 22a
22 Port 22
ora/vio 54 22b 22b
vio/grn 55 23a 23a
23 Port 23
grn/vio 56 23b 23b
vio/brn 57 24a 24a
24 Port 24
brn/vio 58 24b 24b
Table 3-74 SLMA/SLMA8 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
SLMA, SLMA8 Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-74 SLMA/SLMA8 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
SLMA, SLMA8 Notes
No. Pin
4 8a
8
5 8b
4 9a
9
5 9b
4 10a
10
5 10b
4 11a
11
5 11b
4 12a
12
5 12b not used in
4 13a SLMA8
13
5 13b
4 14a
14
5 14b
4 15a
15
5 15b
4 16a
16
5 16b
4 17a
17
5 17b
4 18a
18
5 18b
4 19a
19
5 19b
4 20a
20
5 20b not used in
4 21a SLMA8
21
5 21b
4 22a
22
5 22b
4 23a
23
5 23b
4 24a
24
5 24b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-75 SLMA/SLMA8 - Connector Panel Assignment with CHAMP Jack (for U.S. only)
CHAMP jack SLMA, SLMA8 Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9 9a 9 Ring
Port 9
34 9b 9 Tip
10 10a 10 Ring
Port 10
35 10b 10 Tip
11 11a 11 Ring
Port 11
36 11b 11 Tip
12 12a 12 Ring
Port 12
37 12b 12 Tip Not used for
13 13a 13 Ring SLMA8
Port 13
38 13b 13 Tip
14 14a 14 Ring
Port 14
39 14b 14 Tip
15 15a 15 Ring
Port 15
40 15b 15 Tip
16 16a 16 Ring
Port 16
41 16b 16 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
CHAMP jack SLMA, SLMA8 Notes
17 17a 17 Ring
Port 17
42 17b 17 Tip
18 18a 18 Ring
Port 18
43 18b 18 Tip
19 19a 19 Ring
Port 19
44 19b 19 Tip
20 20a 20 Ring
Port 20 not
45 20b 20 Tip used
21 21a 21 Ring in
Port 21 SLMA8
46 21b 21 Tip
22 22a 22 Ring
Port 22
47 22b 22 Tip
23 23a 23 Ring
Port 23
48 23b 23 Tip
24 24a 24 Ring
Port 24
49 24b 24 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-76 SLMA, SLMA8 - Connector Panel Assignment with SIPAC 1 SU Connectors
(Cable for Ports 1 - 16)
Pair SLMA, SLMA8 MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/gry 05 5a 5a 4
5 Port 5
gry/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
10 Port 10
11 Port 11
12 Port 12 Not used
for
blk/grn 15 13a 13a 4 SLMA8
3 13 Port 13
14 Port 14
15 Port 15
4 16 Port 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
wht/blu
1 Free
blu/wht
wht/ora
2 Free
ora/wht
wht/grn
1 3 Free
grn/wht
wht/brn
4 Free
brn/wht
wht/gry
5 Free
gry/wht
red/blu
6 Free
blu/red
red/ora
7 Free
ora/red
red/grn
2 8 Free
grn/red
9 Port 17
10 Port 18
11 Port 19
12 Port 20 Not used
for
blk/grn 15 21a 21a 4 SLMA8
3 13 Port 21
14 Port 22
15 Port 23
4 16 Port 24
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.17 SLMA2 (for selected countries only)
Introduction
The SLMA2 (Subscriber Line Module Analog) board provides 24 analog T/R interfaces for use
in HiPath 3800.
The external ring voltage generator RGMOD (S30124-X5109-X) is required for generating ring
voltages. RGMOD is plugged in on the reverse of the backplane of the basic and/or expansion
cabinet. The ring voltage and ring frequency are set using jumpers.
A system cabinet can be fitted with a mix of SLMA, SLMA8 and SLMA2 boards. RG-
> MOD has no effect on SLMA and SLMA8, as these boards generate their own ring
voltage (35 Veff).
Front panel

● LED (red)
● LED (green)
Figure 3-70 SLMA2 (S30810-Q2246-X) (for selected countries only) - LEDs on the Front
Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-78 SLMA2 (for selected countries only) - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.

Table 3-77
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-79 SLMA2 (for selected countries only) - SIVAPAC Connector Assignment on the
Backplane
a-wire b-wire
Pair SIVAPAC connector SLMA2 MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17 9a 9a
9 Port 9
brn/red 18 9b 9b
red/grn 19 10a 10a
10 Port 10
grn/red 20 10b 10b
blk/blu 24 11a 11a
11 Port 11
blu/blk 25 11b 11b
blk/ora 26 12a 12a
12 Port 12
ora/blk 27 12b 12b
blk/grn 29 13a 13a
13 Port 13
grn/blk 30 13b 13b
blk/brn 31 14a 14a
14 Port 14
brn/blk 32 14b 14b
blk/grn 34 15a 15a
15 Port 15
grn/blk 35 15b 15b
yel/blu 37 16a 16a
16 Port 16
blu/yel 38 16b 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Backplane
a-wire b-wire
Pair SIVAPAC connector SLMA2 MDFU-E Notes
(tip) (ring)
yel/ora 43 17a 17a
17 Port 17
ora/yel 44 17b 17b
yel/grn 45 18a 18a
18 Port 18
grn/yel 46 18b 18b
yel/brn 47 19a 19a
19 Port 19
brn/yel 48 19b 19b
yel/grn 49 20a 20a
20 Port 20
grn/yel 50 20b 20b
vio/blu 51 21a 21a
21 Port 21
blu/vio 52 21b 21b
vio/ora 53 22a 22a
22 Port 22
ora/vio 54 22b 22b
vio/grn 55 23a 23a
23 Port 23
grn/vio 56 23b 23b
vio/brn 57 24a 24a
24 Port 24
brn/vio 58 24b 24b
Table 3-80 SLMA2 (for selected countries only) - Connector Panel Assignment with RJ45
Jacks
RJ45 jack
SLMA2 Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Jacks
RJ45 jack
SLMA2 Notes
No. Pin
4 7a
7
5 7b
4 8a
8
5 8b
4 9a
9
5 9b
4 10a
10
5 10b
4 11a
11
5 11b
4 12a
12
5 12b
4 13a
13
5 13b
4 14a
14
5 14b
4 15a
15
5 15b
4 16a
16
5 16b
4 17a
17
5 17b
4 18a
18
5 18b
4 19a
19
5 19b
4 20a
20
5 20b
4 21a
21
5 21b
4 22a
22
5 22b
4 23a
23
5 23b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Jacks
RJ45 jack
SLMA2 Notes
No. Pin
4 24a
24
5 24b
Table 3-81 SLMA2 (for selected countries only) - Connector Panel Assignment with
CHAMP Jacks (U.S. only)
CHAMP jack SLMA2 Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9 9a 9 Ring
Port 9
34 9b 9 Tip
10 10a 10 Ring
Port 10
35 10b 10 Tip
11 11a 11 Ring
Port 11
36 11b 11 Tip
12 12a 12 Ring
Port 12
37 12b 12 Tip
13 13a 13 Ring
Port 13
38 13b 13 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
CHAMP Jacks (U.S. only)
CHAMP jack SLMA2 Notes
14 14a 14 Ring
Port 14
39 14b 14 Tip
15 15a 15 Ring
Port 15
40 15b 15 Tip
16 16a 16 Ring
Port 16
41 16b 16 Tip
17 17a 17 Ring
Port 17
42 17b 17 Tip
18 18a 18 Ring
Port 18
43 18b 18 Tip
19 19a 19 Ring
Port 19
44 19b 19 Tip
20 20a 20 Ring
Port 20
45 20b 20 Tip
21 21a 21 Ring
Port 21
46 21b 21 Tip
22 22a 22 Ring
Port 22
47 22b 22 Tip
23 23a 23 Ring
Port 23
48 23b 23 Tip
24 24a 24 Ring
Port 24
49 24b 24 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
SIPAC 1 SU Connectors (Cable for Ports 1-16)
Pair SLMA2 MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
10 Port 10
11 Port 11
12 Port 12
3 13 Port 13
14 Port 14
15 Port 15
4 16 Port 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
SIPAC 1 SU Connectors (Cable for Ports 17-24)
Pair SLMA2 MDFU-E Notes
wht/blu
1 Free
blu/wht
wht/ora
2 Free
ora/wht
wht/grn
1 3 Free
grn/wht
wht/brn
4 Free
brn/wht
wht/grn
5 Free
grn/wht
red/blu
6 Free
blu/red
red/ora
7 Free
ora/red
red/grn
2 8 Free
grn/red
9 Port 17
10 Port 18
11 Port 19
12 Port 20
3 13 Port 21
14 Port 22
15 Port 23
4 16 Port 24
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.18 SLMO2, SLMO8
Introduction
The SLMO2 and SLMO8 boards (Subscriber Line Module Optiset) provide UP0/E interfaces for
use in HiPath 3800:
● SLMO2 (S30810-Q2168-X10) = 24 UP0/E interfaces
● SLMO8 (S30810-Q2168-X100) = eight UP0/E interfaces
Front panel

● LED (red)
● LED (green)
Figure 3-71 SLMO2/SLMO8 - LEDs on the Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-84 SLMO2 and SLMO8 - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

Table 3-89
Table 3-85 SLMO2/SLMO8 - SIVAPAC Connector Assignment on the Backplane
a-wire b-wire
Pair SIVAPAC connector SLMO2, SLMO8 MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-85 SLMO2/SLMO8 - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector SLMO2, SLMO8 MDFU-E Notes
(tip) (ring)
red/brn 17 9a 9a
9 Port 9
brn/red 18 9b 9b
red/grn 19 10a 10a
10 Port 10
grn/red 20 10b 10b
blk/blu 24 11a 11a
11 Port 11
blu/blk 25 11b 11b
blk/ora 26 12a 12a
12 Port 12
blk/grn 29 13a 13a for SLMO8
13 Port 13
grn/blk 30 13b 13b
blk/brn 31 14a 14a
14 Port 14
brn/blk 32 14b 14b
blk/grn 34 15a 15a
15 Port 15
grn/blk 35 15b 15b
yel/blu 37 16a 16a
16 Port 16
blu/yel 38 16b 16b
yel/ora 43 17a 17a
17 Port 17
ora/yel 44 17b 17b
yel/grn 45 18a 18a
18 Port 18
grn/yel 46 18b 18b
yel/brn 47 19a 19a
19 Port 19
brn/yel 48 19b 19b
yel/grn 49 20a 20a
20 Port 20
grn/yel 50 20b 20b Not used
vio/blu 51 21a 21a for SLMO8
21 Port 21
blu/vio 52 21b 21b
vio/ora 53 22a 22a
22 Port 22
ora/vio 54 22b 22b
vio/grn 55 23a 23a
23 Port 23
grn/vio 56 23b 23b
vio/brn 57 24a 24a
24 Port 24
brn/vio 58 24b 24b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-86 SLMO2/SLMO8 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
SLMO2, SLMO8 Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
4 8a
8
5 8b
4 9a
9
5 9b
4 10a
10
5 10b
4 11a
11
5 11b
4 12a
12
5 12b not used in
4 13a SLMO8
13
5 13b
4 14a
14
5 14b
4 15a
15
5 15b
4 16a
16
5 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-86 SLMO2/SLMO8 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
SLMO2, SLMO8 Notes
No. Pin
4 17a
17
5 17b
4 18a
18
5 18b
4 19a
19
5 19b
4 20a
20
5 20b not used in
4 21a SLMO8
21
5 21b
4 22a
22
5 22b
4 23a
23
5 23b
4 24a
24
5 24b
Table 3-87 SLMO2/SLMO8 - Connector Panel Assignment with CHAMP Jack (for U.S.
only)
CHAMP jack SLMO2, SLMO8 Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
only)
8 8a 8 Ring
Port 8
33 8b 8 Tip
9 9a 9 Ring
Port 9
34 9b 9 Tip
10 10a 10 Ring
Port 10
35 10b 10 Tip
11 11a 11 Ring
Port 11
36 11b 11 Tip
12 12a 12 Ring
Port 12
37 12b 12 Tip not used in
13 13a 13 Ring SLMO8
Port 13
38 13b 13 Tip
14 14a 14 Ring
Port 14
39 14b 14 Tip
15 15a 15 Ring
Port 15
40 15b 15 Tip
16 16a 16 Ring
Port 16
41 16b 16 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
only)
17 17a 17 Ring
Port 17
42 17b 17 Tip
18 18a 18 Ring
Port 18
43 18b 18 Tip
19 19a 19 Ring
Port 19
44 19b 19 Tip
20 20a 20 Ring
Port 20
45 20b 20 Tip not used in
21 21a 21 Ring SLMO8
Port 21
46 21b 21 Tip
22 22a 22 Ring
Port 22
47 22b 22 Tip
23 23a 23 Ring
Port 23
48 23b 23 Tip
24 24a 24 Ring
Port 24
49 24b 24 Tip
Table 3-88 SLMO2/SLMO8 - Connector Panel Assignment with SIPAC 1 SU Connectors

Pair SLMO2, SLMO8 MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/gry 05 5a 5a 4
5 Port 5
gry/wht 45 5b 5b 5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

Pair SLMO2, SLMO8 MDFU-E Notes
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
10 Port 10
11 Port 11
12 Port 12 Not used
for
blk/grn 15 13a 13a 4 SLMO8
3 13 Port 13
14 Port 14
blk/gry 17 15a
15
4 16 Port 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
wht/blu
1 Free
blu/wht
wht/ora
2 Free
ora/wht
wht/grn
1 3 Free
grn/wht
wht/brn
4 Free
brn/wht
wht/gry
5 Free
gry/wht
red/blu
6 Free
blu/red
red/ora
7 Free
ora/red
red/grn
2 8 Free
grn/red
9 Port 17
10 Port 18
11 Port 19
12 Port 20 Not used
for
3 13 Port 21
14 Port 22
15 Port 23
4 16 Port 24
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.19 SLMO8 (not for U.S.), SLMO24
Introduction
The SLMO8 and SLMO24 (Subscriber Line Module Cost Optimized UP0/E) boards provide
eight and 24 connections for connecting Optiset E and optiPoint 500 telephones to
HiPath 3550.
Switches and LEDs
Lockout switch S1
(position = free,
factory default)
H1 (green)
LEDs
H2 (red)
Figure 3-72 SLMO8 (not for U.S.), SLMO24 (S30810-Q2901-X100, S30810-Q2901-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-90 SLMO8 (not for U.S.) and SLMO24 - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-91 SLMO8 (not for U.S.), SLMO24 - Cable 1 Assignment (SU Xx8)
SU con-
Color a-wire b-wire nector SLMO8, MDFU/ Patch Panel,
Pair Notes
Group (tip) (ring) SLMO24 MDFU-E MW8 pin
BP: Xx8
wht/blu 19 1a 1a 4
1 Access 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Access 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Access 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Access 4
brn/wht 46 4b 4b 5
wht/gry 05 5a 5a 4
5 Access 5
gry/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Access 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Access 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Access 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Access 9
brn/red 31 9b 9b 5
10 Access 10
11 Access 11
12 Access 12 Not used
for
3 13 Access 13
14 Access 14
15 Access 15
4 16 Access 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-92 SLMO8 (not for U.S.), SLMO24 - Cable 2 Assignment (SU Xx9)
SU con-
Color a-wire b-wire nector SLMO8, MDFU/ Patch Panel,
Pair Notes
Group (tip) (ring) SLMO24 MDFU-E MW8 pin
BP: Xx9
wht/blu
1 Free
blu/wht
wht/ora
2 Free
ora/wht
wht/grn
1 3 Free
grn/wht
wht/brn
4 Free
brn/wht
wht/gry
5 Free
gry/wht
red/blu
6 Free
blu/red
red/ora
7 Free
ora/red
red/grn
2 8 Free
grn/red
9 Access 17
10 Access 18
11 Access 19
12 Access 20 Not used
for
3 13 Access 21
14 Access 22
15 Access 23
4 16 Access 24
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-93 SLMO24 - Assignment (SU Xx8, Xx9) (for U.S. only)

# SLMO24 CHAMP jack, MDF Notes
wht/blu 19 1a 1 1a
1 Port 1
blu/wht 39 1b 26 1b
wht/ora 38 2a 2 2a
2 Port 2
ora/wht 48 2b 27 2b
wht/grn 27 3a 3 3a
3 Port 3
grn/wht 47 3b 28 3b
wht/brn 16 4a 4 4a
4 Port 4
brn/wht 46 4b 29 4b
wht/grn 05 5a 5 5a
5 Port 5
grn/wht 45 5b 30 5b
red/blu 14 6a 6 6a
6 Port 6
blu/red 44 6b 31 6b
red/ora 23 7a 7 7a
7 Port 7
ora/red 43 7b 32 7b
red/grn 32 8a 8 8a
8 Port 8
grn/red 42 8b 33 8b
red/brn 11 9a 9 9a
9 Port 9
brn/red 31 9b 34 9b
red/grn 02 10a 10 10a
10 Port 10
grn/red 22 10b 35 10b
blk/blu 13 11a 11 11a
11 Port 11
blu/blk 33 11b 36 11b
blk/ora 04 12a 12 12a
12 Port 12
ora/blk 24 12b 37 12b
blk/grn 15 13a 13 13a
13 Port 13
grn/blk 35 13b 38 13b
blk/brn 06 14a 14 14a
14 Port 14
brn/blk 26 14b 39 14b
blk/grn 17 15a 15 15a
15 Port 15
grn/blk 37 15b 40 15b
yel/blu 08 16a 16 16a
16 Port 16
blu/yel 28 16b 41 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-93 SLMO24 - Assignment (SU Xx8, Xx9) (for U.S. only)

# SLMO24 CHAMP jack, MDF Notes
red/brn 11 17a 9 9a
17 Port 17
brn/red 31 17b 34 9b
red/grn 02 18a 10 10a
18 Port 18
grn/red 22 18b 35 10b
blk/blu 13 19a 11 11a
19 Port 19
blu/blk 33 19b 36 11b
blk/ora 04 20a 12 12a
20 Port 20
ora/blk 24 20b 37 12b
blk/grn 15 21a 13 13a
21 Port 21
grn/blk 35 21b 38 13b
blk/brn 06 22a 14 14a
22 Port 22
brn/blk 26 22b 39 14b
blk/grn 17 23a 15 15a
23 Port 23
grn/blk 37 23b 40 15b
yel/blu 08 24a 16 16a
24 Port 24
blu/yel 28 24b 41 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.20 SLU8
Introduction
The SLU8 board for HiPath 3550 and HiPath 3350 (wall housing) with 8 digital subscriber line
interfaces allows up to 16 digital telephones to be connected in host-client operation (master-
slave operation).
Interfaces
50
1
X2
UP0/E ports to CUP/CUC
1-4 8
SLU8 X1
1
UP0/E ports X3
5-8
8 2
Figure 3-73 SLU8 Interfaces (S30817-Q922-A301)
Caution
7 After deactivating the power supply, you must wait a short while before plugging the
SLU8 in or out. If you do not wait before doing so, the CBCC/CBCP may be dam-
aged.
Table 3-94 SLU8 Contact Assignments

Contact X2 (UPo/E ports 1-4) X3 (UP0/E ports 5-8)
1 a1 a5
2 b1 b5
3 a2 a6
4 b2 b6
5 a3 a7
6 b3 b7
7 a4 a8
8 b4 b8
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.21 SLU8R
Introduction
The SLU8R (Subscriber Line UP0/E Rack) boards provide eight ports for connecting Optiset E
and optiPoint 500 telephones to HiPath 3500 and HiPath 3300 (19-inch housing).
Interfaces
UP0/E1 11 50
to CUPR /
UP0/E ports X1 CUCR
1–8 X2
(8-pin RJ45
jacks) 2
UP0/E8 88
Figure 3-74 SLU8R Interfaces (S30817-K922-Z301)
Table 3-95 SLU8R Contact Assignments
RJ45 X2, Pin UP0/E ports RJ45 X2, Pin UP0/E ports
jack 1-4 jack 5-8
1 14 a1 5 54 a5
15 b1 55 b5
2 24 a2 6 64 a6
25 b2 65 b6
3 34 a3 7 74 a7
35 b3 75 b7
4 44 a4 8 84 a8
45 b4 85 b8
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.22 STLS2 (not for U.S.), STLS4
Introduction
The STLS4 board for HiPath 3550 and HiPath 3350 (wall housing) has four S0 ports that can
operate as trunk interfaces or as subscriber line interfaces (see Page 3-211).
The STLS2 is an underequipped variant with two S0 ports.
Interfaces
The board does not supply terminals with power. Power must be supplied locally us-
> ing a local plug-in power supply or a bus power supply unit, for example.
50
to CUP /
S0 ports 1 CUC
Mini-Western STLS2/STLS4
X1
2
X2
Not in 3
STLS2
4
2
654321
2 = SX +
3 = SR +
4 = SR -
5 = SX -
SX = Signal transmit
SR = Signal receive
Figure 3-75 STLS2 (not for U.S.), STLS4 Interfaces (S30817-Q924-B313, -A313)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Interface Assignments (for U.S. only)
Table 3-96 STLS4 Module Interface Assignments (for U.S. only)
Pin Port Assignment Pin Port Assignment

2 1 Transmit 2 3 Transmit
3 Receive 3 Receive
4 Receive 4 Receive
5 Transmit 5 Transmit
2 2 Transmit 2 4 Transmit
3 Receive 3 Receive
4 Receive 4 Receive
5 Transmit 5 Transmit
Note: The STLS4 module supports the trunk side in Europe, so the transmit and receive signals
must be reversed before the first device on the S0 bus. In contrast, the Optiset E ISDN adapter
uses a straight-through connection because it is always a station-only device. For information,
see Figure 3-79.
The ISDN terminals must have their own local power supply.
The system only assigns the MSN after the S0 port has been configured on the “Euro bus” (not
for U.S.) and can be read out via administration (Manager T: Code 20 4 3 S0 Bus MSN).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Connecting ISDN (S0) interfaces (not for U.S.)

You can use the MW jacks on the STLS boards to connect between one and four ISDN S0 bus-
es. The interfaces on the STLS boards are freely configurable.
● EURO CO point-to-point
● EURO CO point-to-multipoint
● EURO bus
● CorNet-N/CorNet-NQ slave
● Using HiPath 3000/5000 Manager E, you can also set up configurations for networking and
dedicated lines
Use the S0 interface S01 for connection to the public telecommunications network (ISDN trunk).
You can also connect S0 interfaces S02 to S04 to the ISDN trunk or to ISDN terminals (ISDN
telephone, group 4 fax device, PC, dialing aid) via an S0 bus.
The connection (networking) to HiPath 3000 and HiPath 4000 (CorNet-NQ) can also be set up
via S0 interfaces S01 to S04.
S0 connection options:
● Point-to-point (PP) (default)
● Point-to-multipoint (PMP)
Connecting an ISDN trunk (not for U.S.)

Insert the connection cable supplied in jacks S01 to S04. Insert the other end in the NT of the
carrier.
Networking connection (HiPath 4000/CorNet-NQ (not for U.S.)

Insert the connection cable supplied in jacks S01 to S04. Connect the other end with the HiPath
4000 port.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Connecting ISDN terminals (not for U.S.)

Depending on the system, you can set up a maximum of four internal S0 buses (S01 to S04). A
maximum of eight ISDN terminals can be addressed on each S0 bus.
The system does not assign the MSN until the S0 port is configured on the “Euro bus”; the MSN
can be read out via administration.
When you set up an S0 bus, it is assigned an MSN. This MSN is the first free station number
in the system. The S0 station is immediately available under this MSN, without an outgoing sei-
zure.
If no MSN is entered in the terminal, a default MSN is automatically assigned after

> you change the S0 port to “Euro bus” in system administration.
Configuring an S0 bus with a Mini-Western jack (not for U.S.)

S0 telephones cannot be directly connected to an STLS board’s Mini-Western jack via the cable
supplied. You must first install a jack with cross-connected cables (see Figure 3-77).
Assignment of RJ jack pins 1 - 8:

8-pin 6-pin
8 7 6 5 4 3 2 1 6 5 4 3 2 1
SR SX SX SR SR SX SX SR
4-pin Always establish contact on the

center four pins.
4 3 2 1
SR SX SX SR
Figure 3-76 Sample Pin Assignments in MW Jacks (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
System RJ
S01 to S04 through-jack
(MW8 = 8-pin)
SR.1 Receive 5
SX SR SR SX SX.1 Transmit 3 twisted
To switch from external to inter- SX.2 Transmit 6 pair
nal S0 operation, you must 8 7 6 5 4 3 2 1 SR.2 Receive 4
cross the SR and SX wires
* * = Not crossed in TA-S0
before the first jack.
8 7 6 5 4 3 2 1 1st RJ jack
230 V~ (MW8 = 8-pin)
UAE
connector
6
Additional 5
power sup- 4
ply 3
2nd to 8th RJ jack
The connecting cord of the 8 7 6 5 4 3 2 1 (MW8 = 8-pin)
ISDN telephone must not
exceed 10 m in length.
100 Ω/0.25 W
Terminating resistor in last jack
Maximum ranges:
System 1 2 3 8
Short bus: 150 m (492 ft.)

Long bus: 150 m (492 ft.) 20 m
Figure 3-77 Wiring and Ranges for S0 Bus Jacks (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Connecting ISDN Terminals to HiPath 3550 and HiPath 3350 (for U.S. only)
● S0 Bus With RJ45 jack, connecting S01 to S04:
– Connect the provided, silver-satin connector cord to each port on the STLS4 Module.
Connect the other end to a mounted MW jack, reversing the transmit and receive wires
as shown in Figure 3-79.
– Contact is always established using the center pins of MW jacks. Figure 3-78 shows
the pin assignments for jacks of different sizes.
– The ISDN terminals must have their own local power supply.
– Plug the ISDN terminal (connecting cord) into the MW jack. Connecting an ISDN S0
telephone requires a local power supply (e.g. manufactured by Sedlbauer).
● Pin Assignment of MW Jacks
8-pin MW8 6-pin MW6
8 7 6 5 4 3 2 1 6 5 4 3 2 1
4-pin MW4 SX = Signal transmit

SR = Signal receive
4 3 2 1 With MW cables, contact is always es-
tablished in the center of the connec-
SR SX SX SR tor.
Figure 3-78 MWxx Jack Pin Assignment (for U.S. only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
S 0 Bus wiring from STLS4 port or optiset E ISDN adapter (for U.S. only)
STLS port in system Optiset E

ISDN adapter
Through jack connected to
silver satin colored RJ11 123
ABC
DEF
456
ABC
DEF
connector cable (6-pin)

GHI
JKL
MNO
789
GHIMNO
PQRS
TUV
WXYZ
0
PQRS
TUV
SX SR SR SX
6 5 4 3 2 1
SX SR SR SX
6 5 4 3 2 1
Surface-mounted MW8 jack
8 7 6 5 4 3 2 1
(8-pin)
Cross the transmit and receive
wires from the STLS port (not
required in S0 bus from ISDN
8 7 6 5 4 3 2 1 adapter).
Device jack 1
(8-pin MW8)
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
Device jacks 1 to 7 ’
(8-pin MW8)
Device jack 2
(8-pin MW8)
Last device jack

8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1 (8-pin MW8)
100 ohms, 0.25 W

Figure 3-79 S 0 Bus wiring from STLS4 port or optiset E ISDN adapter (for U.S. only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.23 STLS4R
Introduction
The STLS4R (Subscriber And Trunk Line S0 RACK) board provides four S0 basic rate access-
es for HiPath 3500 and HiPath 3300 (19-inch housing). These are operated either as external
trunk interfaces in TE (terminal equipment) mode or as internal S0 buses (PMP bus) in NT (net-
work terminator) mode with cross-connected RX-TX lines.
The board does not supply terminals with power. In this case, power must be sup-
> plied locally using a local plug-in power supply or a bus power supply unit, for exam-
ple.
Interfaces
S0 port 1 11 50
4 S0 ports
(MW8
(RJ45) X2 STLS4R
X1 to CUPR /
jacks) CUCR
S0 port 4 48
8 ... 1
3 = SX +
4 = SR +
5 = SR –
6 = SX –
SX = Signal transmit
SR = Signal receive
Figure 3-80 STLS4R Interfaces (S30817-K924-Z313)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-97 STLS4R Contact Assignments
MW8 (RJ45) Jack X2, Pin S0 Ports 1-4

1 13 S0 port 1 transmit+
14 S0 port 1 receive+
15 S0 port 1 receive–
16 S0 port 1 transmit–
Refer to Page 3-211 for information on connecting ISDN lines and telephones.
>
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.24 STLSX2, STLSX4, STLSX4R
Introduction
The following boards provide S0 basic connections:
● STLSX4 (Subscriber Trunk Line S0 with ISAC-SX) S30810-Q2944-X = four S0 basic rate
accesses for use in HiPath 3550 and HiPath 3350.
● STLSX2 S30810-Q2944-X100 = two S0 basic rate accesses for use in HiPath 3550 and
HiPath 3350.
● STLSX4R (Subscriber Trunk Line S0 with ISAC-SX Rack) S30810-K2944-Z = four S0 basic
rate accesses for use in HiPath 3500 and HiPath 3300.
These are operated either as external trunk interfaces in TE (terminal equipment) mode or as
internal S0 buses (PMP bus) in NT (network terminator) mode with cross-connected RX-TX
lines.
Interfaces
The board does not supply terminals with power. Power must be supplied locally for
> telephones, for example via a plug-in power supply unit.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
S0 port 1 11 50 CUP/CUC
(for STLSX2/
4 S0 ports
STLSX4)
(MW8 (RJ45) X2
jacks) X1
S0 port 4 48 CUPR/CUCR
(for STLSX4R)
S0 ports 3 and 4 are 2
not assigned in
STLSX2.
8 ... 1
MW8 (RJ45) jack assignment:
3 = Transmit +
4 = Receive +
5 = Receive –
6 = Transmit –
Figure 3-81 STLSX2, STLSX4, STLSX4R - Interfaces
Table 3-98 STLSX2, STLSX4, STLSX4R - S0 Interface Assignment
X2 S0 Port 1 X2 S0 Port 2 X2 S0 Port 31 X2 S0 Port 41

Pin Pin Pin Pin
11 – 21 – 31 – 41 –
12 – 22 – 32 – 42 –
13 Transmit + 23 Transmit + 33 Transmit + 43 Transmit +
14 Receive + 24 Receive + 34 Receive + 44 Receive +
15 Receive – 25 Receive – 35 Receive – 45 Receive –
16 Transmit – 26 Transmit – 36 Transmit – 46 Transmit –
17 – 27 – 37 – 47 –
18 – 28 – 38 – 48 –
1 Not for STLSX2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Configuring S0 interfaces
Depending on how the interfaces are applied, use HiPath 3000/5000 Manager E to define the
relevant protocols for the trunks to be connected. Please note the additional information con-
tained in the protocol templates when selecting a suitable S0 protocol:
● CO = Interfaces to the public CO
● Bus = Interfaces to an internal station
● Master = Interfaces for a master system network
● Slave = Interfaces for a slave system network
● H150/H118 or H300 = Defines the CorNet protocol:
– H150/H118 = Optimized for interconnection with HiPath 3000
This option should also be selected in connection with HiPath ProCenter Office HPCO.
– H300 = Optimized for interconnection with HiPath 4000
● Direct or fixed connection: defines the type of connection for a network and controls the
supply of clock pulses:
– Direct = Communication systems are connected to one another by means of a direct
cable connection. The master system supplies the reference clock pulse for the net-
worked system.
– Fixed connection = Communication systems are connected over lines leased from a
network provider (with clock pulse supply). The master system receives the reference
clock pulse from the network.
A slave system always receives the clock pulse from the master system regardless of
whether the connection is direct or fixed.
Use the S0 interface S0 1 for connection to the public telecommunications network. You can
also connect S0 interfaces S0 2 to S0 4 to the ISDN trunk or to ISDN terminals (ISDN telephone,
group 4 fax device, PC, dialing aid) via an S0 bus.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Connecting ISDN telephones

Depending on the system, you can set up a maximum of four internal S0 buses (S0 1 to S0 4).
A maximum of eight ISDN terminals can be addressed on each S0 bus.
The system does not assign the MSN until the S0 port is configured on the “Euro bus”; the MSN
can be read out via administration.
When you set up an S0 bus, it is assigned an MSN. This MSN is the first free station number
in the system. The S0 station is immediately available under this MSN, without an outgoing sei-
zure.
If no MSN is entered in the terminal, a default MSN is automatically assigned after

> you change the S0 port to “Euro bus” in system administration.
Configuring an S0 bus with a Mini-Western jack

S0 telephones cannot be directly connected to an STLSX board’s Mini-Western jack via the ca-
ble supplied. You must first install a jack with cross-connected cables (see Figure 3-83).
Assignment of RJ jack pins 1 - 8:

8-pin 6-pin
8 7 6 5 4 3 2 1 6 5 4 3 2 1
4-pin Always establish contact on the

center four pins.
4 3 2 1
SR SX SX SR
Figure 3-82 Pin Assignments in MW Jacks
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
System RJ
S01 to S04 through-jack
(MW8 = 8-pin)
SR.1 Receive 5
SX SR SR SX SX.1 Transmit 3 twisted
To switch from external to inter- SX.2 Transmit 6 pair
nal S0 operation, you must 8 7 6 5 4 3 2 1 SR.2 Receive 4
cross the SR and SX wires
* * = Not crossed in TA-S0
before the first jack.
8 7 6 5 4 3 2 1 1st RJ jack
230 V~ (MW8 = 8-pin)
UAE
connector
6
Additional 5
power sup- 4
ply 3
2nd to 8th RJ jack
The connecting cord of the 8 7 6 5 4 3 2 1 (MW8 = 8-pin)
ISDN telephone must not
exceed 10 m in length.
100 Ω/0.25 W
Maximum ranges:
System 1 2 3 8
Short bus: 150 m (492 ft.)

Long bus: 150 m (492 ft.) 20m
Figure 3-83 Wiring and Ranges for S0 Bus Jacks
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.25 STMD3
Introduction
The STMD3 (Subscriber and Trunk Module Digital S0) board contains eight S0 basic rate ac-
cesses for HiPath 3800.
The range of the short S0 bus (up to eight Terminal Equipment Identifiers (TEI)) is
> limited to approximately 60 m.
If longer cables are required, the S0 bus type must be set to "Long" in HiPath 3000/
5000 Manager E developer mode. This provides a range of approximately 160 m.
This setting can be made in V5.0 SMR-05 (CV 5) or later.
Front panel

● LED (red)
● LED (green)
Figure 3-84 STMD3 (S30810-Q2217-X10) - LEDs in the Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-99 STMD3 - LED Statuses

LED
correctly. board.
in progress.
Board is deactivated (not applicable to er- was deactivated using
rors detected by test loops) or board was HiPath 3000/5000 Man-
deactivated using HiPath 3000/5000 Man- ager E. If not, replace
ager E. board.
OK (idle state).

A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-100 STMD3 - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector STMD3 MDFU-E Notes
(tip) (ring)
wht/blu 1 1Ea 1a
1
blu/wht 23 1Eb Basic 1b
wht/ora 3 1Sa rate access 1 2a
2
ora/wht 4 1Sb 2b
wht/grn 5 2Ea 3a
3
grn/wht 6 2Eb Basic 3b
wht/brn 7 2Sa rate access 2 4a
4
brn/wht 8 2Sb 4b
wht/grn 9 3Ea 5a
5
grn/wht 10 3Eb Basic 5b
red/blu 11 3Sa rate access 3 6a
6
blu/red 12 3Sb 6b
red/ora 13 4Ea 7a
7
ora/red 14 4Eb Basic 7b
red/grn 15 4Sa rate access 4 8a
8
grn/red 16 4Sb 8b
red/brn 17 5Ea 9a
9
brn/red 18 5Eb Basic 9b
red/grn 19 5Sa rate access 5 10a
10
grn/red 20 5Sb 10b
blk/blu 24 6Ea 11a
11
blu/blk 25 6Eb Basic 11b
blk/ora 26 6Sa rate access 6 12a
12
ora/blk 27 6Sb 12b
blk/grn 29 7Ea 13a
13
grn/blk 30 7Eb Basic 13b
blk/brn 31 7Sa rate access 7 14a
14
brn/blk 32 7Sb 14b
blk/grn 34 8Ea 15a
15
grn/blk 35 8Eb Basic 15b
yel/blu 37 8Sa rate access 8 16a
16
blu/yel 38 8Sb 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-101 STMD3 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
Subscriber line Trunk connection STMD3 Notes
No.
Pin Pin
3 4 1Ea
6 5 1Eb Basic
1
4 3 1Sa rate access 1
5 6 1Sb
3 4 2Ea
6 5 2Eb Basic
2
5 6 2Sb
3 4 3Ea
6 5 3Eb Basic
3
5 6 3Sb
3 4 4Ea
6 5 4Eb Basic
4
5 6 4Sb
3 4 5Ea
6 5 5Eb Basic
5
5 6 5Sb
3 4 6Ea
6 5 6Eb Basic
6
5 6 6Sb
3 4 7Ea
6 5 7Eb Basic
7
5 6 7Sb
3 4 8Ea
6 5 8Eb Basic
8
5 6 8Sb
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-102 STMD3 - Connector Panel Assignment with CHAMP Jack (for U.S. only)
CHAMP jack STMD3 Notes
1 S0, Receive
26 S0, Receive Basic
2 S0, Transmit rate access 1
27 S0, Transmit
3 S0, Receive
29 S0, Transmit
5 S0, Receive
31 S0, Transmit
7 S0, Receive
33 S0, Transmit
9 S0, Receive
35 S0, Transmit
11 S0, Receive
37 S0, Transmit
13 S0, Receive
39 S0, Transmit
15 S0, Receive
41 S0, Transmit
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-103 STMD3 - Connector Panel Assignment with SIPAC 1 SU Connectors (Cable
for Ports 1 - 16)
S0 patch panel,
Color a-wire b-wire SU MW8 pin
Pair STMD3 MDFU-E
group (tip) (ring) connector Subscriber Trunk
line connection
wht/blu 19 1Ea 1a 3 4
1 Basic
blu/wht 39 1Eb 1b 6 5
rate access
wht/ora 38 1Sa 1 2a 4 3
2
ora/wht 48 1Sb 2b 5 6
wht/grn 27 2Ea 3a 3 4
1 3 Basic
grn/wht 47 2Eb 3b 6 5
rate access
wht/brn 16 2Sa 2 4a 4 3
4
brn/wht 46 2Sb 4b 5 6
wht/grn 05 3Ea 5a 3 4
5 Basic
grn/wht 45 3Eb 5b 6 5
rate access
red/blu 14 3Sa 3 6a 4 3
6
blu/red 44 3Sb 6b 5 6
red/ora 23 4Ea 7a 3 4
7 Basic
ora/red 43 4Eb 7b 6 5
rate access
red/grn 32 4Sa 4 8a 4 3
2 8
grn/red 42 4Sb 8b 5 6
red/brn 11 5Ea 9a 3 4
9 Basic
brn/red 31 5Eb 9b 6 5
rate access
red/grn 02 5Sa 5 10a 4 3
10
grn/red 22 5Sb 10b 5 6
blk/blu 13 6Ea 11a 3 4
11 Basic
blu/blk 33 6Eb 11b 6 5
rate access
blk/ora 04 6Sa 6 12a 4 3
12
ora/blk 24 6Sb 12b 5 6
blk/grn 15 7Ea 13a 3 4
3 13 Basic
grn/blk 35 7Eb 13b 6 5
rate access
blk/brn 06 7Sa 7 14a 4 3
14
brn/blk 26 7Sb 14b 5 6
blk/grn 17 8Ea 15a 3 4
15 Basic
grn/blk 37 8Eb 15b 6 5
rate access
yel/blu 08 8Sa 8 16a 4 3
4 16
blu/yel 28 8Sb 16b 5 6
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.26 STMI2
Introduction
STMI2 (Subscriber Trunk Module IP) is a VoIP gateway board (VoIP - Voice over IP) which pro-
vides the functionality of HG 1500 in HiPath 3800. This includes:
● Connection of a local LAN to the HiPath 3800 and connection with external LANs via the
ISDN and DSL interfaces of HiPath 3800.
● Support for the conventional functions of an ISDN and DSL router with the additional func-
tionality of a media gateway for the transfer of voice, fax and data.
● Forwarding of calls between IP-supported networks (LAN, intranet, Internet) and circuit-
switched networks (ISDN, PSTN).
Configuration is performed via Web-Based Management (WBM) which enables the administra-
tion of HG 1500 without any special software requirements.
A combination of up to eight STMI2 boards can be used per system, but the following
> restrictions must be observed:
● A maximum of four STMI2 boards may be inserted per HiPath 3800 cabinet.
● To allow for future channel expansion with extension modules, the slot between
two STMI2 boards should remain free.
For information on configuration, refer to the HG1500 Administration Manual.
For information on how to calculate the number of boards required for HG 1500, see
Section 2.6.
Board versions
Table 3-104 STMI2 - Board Variants
Board Part number Services DSPs B channels

DSP channels
STMI2 S30810-Q2316-X100 Voice and Data 2 32
Sixteen simultaneous Voice over IP connections are possible per DSP (Digital Signal Proces-
sor).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Extension modules
The STMI2 board has two HGA (HiPath Gateway Accelerator) slots, which can be used to con-
nect the extension modules.
Table 3-105 STMI2 - Extension Modules
Extension Part number Function Notes

module
PDMX S30807-Q5697- The PDMX extension module
(PMC DSP Mo- X200 is not released at present.
dule Extended)
HGA
slot 1
HGA
slot 0
Figure 3-85 STMI2 (S30810-Q2316-X100) - HGA Slots
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Connections
The STMI2 board features the following connections on the front panel:
● Two RJ45 jacks for LAN interfaces. These provide access to the Ethernet standard (IEEE
802.3) with 10 Mbps or 100 Mbps with automatic configuration. Manual configuration is
also possible.
● 9-pin Sub-D plug for V.24 interface
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Front panel

● Run (green)
– on = at least 1 B channel busy
– off = normal operation
● Fail (red) = error encountered
V.24 interface (9-pin Sub-D plug)
Two Ethernet (10/100BaseT) LAN connectors (8-pin RJ45 jacks):

● LAN2 (only released for service applications)
● LAN1
The LAN interface status is indicated by two LEDs:
● LED1:
● LED2 (green):
Figure 3-86 STMI2 - Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
V.24 interface
The V.24 cable (C30267-Z355-A25) is used for connecting the service PC.
The following settings must be chosen for a terminal or PC connected to the V.24 interface:
Transmission rate 38,400 (default)

Data bits 8
Parity bit None
Stop bits 1
Data flow control none
It is recommended that the local echo be deactivated on the connected terminal or PC.
Table 3-106 STMI2 - V.24 Interface Assignment
Pin Signal I/O Remark

1 DCD Not used
2 RxD I Internal pull-up resistor in level switch (MAX211E)
3 TxD O
4 DTR O
5 0V Ground
6 DSR I Internal pull-up resistor in level switch (MAX211E)
7 RTS O
8 CTS I Internal pull-up resistor in level switch (MAX211E)
9 RI Not used
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
LAN interfaces
Table 3-107 STMI2 - LAN Interface Assignment (RJ45 Jacks)
Pin Signal
1 TDP (Transmit Data +)
2 TDN (Transmit Data –)
3 RDP (Receive Data +)
4 TT1 (Transmit Termination 1)
5 TT2 (Transmit Termination 2)
6 RDN (Receive Data –)
7 RT1 (Receive Termination 1)
8 RT2 (Receive Termination 2)
Signals TT1/2 and RT1/2 are not needed for transmitting data. They represent a signal termi-
nation of 100 ohms (known as a Bob Smith termination) for the two unused wire pairs in a 4-
pair twisted pair cable.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.27 TCAS-2 and TCASR-2 (for selected countries only)
Introduction
The following cards - one per system - can be used for V5.0 SMR -10 and later to support coun-
try-specific CAS (Channel Associated Signaling) protocols:
● TCAS-2 (S30810-Q2945-X) in HiPath 3550
● TCASR-2 (S30810-K2945-X) in HiPath 3500
Please note that the cards listed can only be used in slots 7 and 9.
Each of the cards features two E1-CAS interfaces, which together support up to 60 B channels.
Since HiPath 3550 and HiPath 3500 each support a maximum of 30 B channels, a total of up
to 30 B channels can be used per card.
Direct connection to the MINI BNC connectors on each card is only possible for coaxial trunks
(75 ohms). An external impedance converter (F31505-E1-A146) must be used for symmetri-
cal trunks (120 ohms).
TCAS-2 and TCASR-2 function as converters, which convert the Euro-ISDN protocol on an
S2M link to the Channel Associated Signaling protocol CAS. In contrast to the predecessor TM-
CAS board, TCAS-2 and TCASR-2 communicate directly with the central control in the system.
All signaling and data traffic goes through TCAS-2 and TCASR-2. Unlike TMCAS, connection
to an S2M board is therefore not required.
Figure 3-87 TCAS-2 (S30810-Q2945-X) (for selected countries only) – Figure
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Interfaces and jumpers
1 Modem (optional)
CAS interface 1: X910
X909
321
X805: Analog modem
X16
X21 X20
CAS interface 2: X911
X912 X17
X803: V.24 interface
X804: Ethernet (10/ 321 321

100BaseT) interface X13 X11
X14 X12
Figure 3-88 TCAS-2, TCASR-2 (for selected countries only) – Interfaces and Jumpers
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Settings
Table 3-108 TCAS-2, TCASR-2 (for selected countries only) – Jumper Functions
Jumper Function Setting

Pins 1–2 closed Pins 2–3 closed
X11 Sets the V.24 baud rate See Table 3-109
X12
X14
X13 Deletes the flash mem- Flash memory is deleted Flash memory is not de-
ory (all sectors apart from U- leted.
boot (firmware)). (default setting)
X16 Resets card Reset performed. Reset not performed.
(default setting)
X17 Hardware watchdog Watchdog active. Watchdog is not active.
(default setting)
Table 3-109 TCAS-2, TCASR-2 (for selected countries only) – Jumper for Setting the V.24
Baud Rate
V.24 baud rate Jumper

(Kbps) X11 X12 X14
9,6 Open Open Open
(default setting)
19,2 Open Open Closed
38,4 Closed Open Closed
57,6 Open Closed Closed
115,2 Closed Closed Closed
9,6 All other configurations
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Connections
X910 (MINI BNC connector, 75 ohms): Receive (RX)
CAS interface 1:
X909 (MINI BNC connector, 75 ohms): Transmit (TX)
X805 (RJ45 jack): Analog modem (optional)
X911 (MINI BNC connector, 75 ohms): Receive (RX)
CAS interface 2:
X912 (MINI BNC connector, 75 ohms): Transmit (TX)
X803 (9-pin MINI DIN jack): V.24 interface
X804 (RJ45 jack): Ethernet (10/100BaseT) interface

Two LEDs indicate the current interface status:
● Yellow LED = transmitting data
● Green LED = receiving data
Figure 3-89 TCAS-2, TCASR-2 (for selected countries only) – Connections
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
TCASR-2 front panel
Line 1 MODEM Line 2 V.24 ETHERNET
RX TX RX TX
Figure 3-90 TCASR-2 (for selected countries only) – Front Panel
The card’s software status can be ascertained on the basis of the seven-segment display. For
this a distinction is made between the following boot phases:
Power supply unit switched on
The decimal point is flashing to indicate that the U-

U-boot
boot firmware is operational.
(Firmware)
The decimal point is activated (not flashing) to indi-

Linux operating system
cate initialization of the Linux operating system.
initialization
The decimal point is activated when the card sup-

CAS application software
plies the clock reference for the system.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
● U-boot (firmware) states

Table 3-110 TCAS-2, TCASR-2 (for selected countries only) – U-boot (firmware) States
Display Meaning
Initializing hardware
Downloading DSP (Digital Signal Processor) firmware
Downloading FPGA (Field Programmable Gate Array) firmware
Accessing flash EPROM (Save and Delete)
Activating built-in self test BIST (BIST1 or BIST2)
Administration (Service PC connected)
Copying software (from SDRAM to FEPROM)
Downloading image file (Linux and CAS application)
Initializing the Linux operating system
Error
Resetting card
U-boot (firmware) operational (decimal point flashing)
● Linux operating system states

Table 3-111 TCAS-2, TCASR-2 (for selected countries only) – Linux Operating System
States
Display Meaning
Linux kernel boot
User space boot
Check and mount flash
Error found, mounted file system rebuild, reboot
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
States
Display Meaning
Mounting flash file system
Error mounting flash (flashing display)
Configuring network interface
Loading real-time kernel modules
Loading board-specific modules
Core files available
● CAS application software states
Interface 1 (ISDN) active Interface 1 (CAS) active
Interface 2 (CAS) active
CAS application operational (flashing display)
Figure 3-91 TCAS-2, TCASR-2 (for selected countries only) – CAS Application Soft-
ware States
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Modem (optional)
X21: Pin1
Figure 3-92 TCAS-2, TCASR-2 (for selected countries only) – Optional Modem
The analog modem (modem kit F31505-E1-A147) is an optional subboard for the TCAS-2 and
TCASR-2 cards, which is plugged into the X20 and X21 ports. This facilitates remote adminis-
tration of the CAS protocol converter on the TCAS-2 and TCASR-2 cards (see Page 3-243).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

A separate tool, the CAS Manager, is used to download the software and administer the TCAS-
2 and TCASR-2. The CAS Manager software is stored on a CD supplied with the card. For in-
formation on how to install the CAS Manager software on the Service PC, refer to the readme
file.
The following options are available for accessing the cards:
● Via the V.24 interface (9-pin MINI DIN jack X803) and the connection cable C39195-
A9700-B532.
● Via the Ethernet (10/100BaseT) interface (RJ45 jack X804).
● Via the optional analog modem (modem kit F31505-E1-A147). In this case, you will need
to establish a connection from the analog modem (RJ45 jack X805) to a free port in an an-
alog subscriber line module via the RJ45 cable C39195-Z7208-A10 supplied with the mo-
dem kit (see Figure 3-94).
HiPath 3550 / HiPath 3500
TCAS-2 / X803 CAS

TCASR-2 V.24 interface Manager
Analog sub-
scriber line X805 Modem
module (optional)
Establish connec- X804
tion. Ethernet (10/100BaseT) interface
Analog trunk
board
CAS CAS
Manager Manager
PSTN IP Network
Figure 3-93 TCAS-2, TCASR-2 (for selected countries only) – Connection Options for Card
Administration using CAS Manager
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
RJ45 Cable C39195-Z7208-A10 (included in modem kit F31505-E1-A147)
● HiPath 3500
TCASR-2: X805 Plug the RJ45 connector into
the free jack on an analog sub-
scriber line module.
● HiPath 3550
TCAS-2: X805 Disconnect the RJ45 cable and
connect the T/R wires to the
free terminals on an analog
subscriber line module.
Figure 3-94 TCAS-2, TCASR-2 (for selected countries only) – RJ45 Cable C39195-Z7208-
A10
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Assigning the CAS cable

The following options are available for connecting network terminators (NT), multiplexers
(MUX) or modems to the TCAS-2 and TCASR-2 cards (MINI BNC connections):
● Coaxial trunk (75 ohms), length = 10 m
Table 3-112 TCAS-2, TCASR-2 (for selected countries only) – Assignment of the CAS
Cable C39195-A7700-B13
Wire Function MINI BNC connector BNC connector
1 Receive, Tip Conductor Conductor
Receive, Ring Shield Shield
2 Transmit, Tip Conductor Conductor
Transmit, Ring Shield Shield
MINI BNC connector Ferrite core BNC connector
Figure 3-95 TCAS-2, TCASR-2 (for selected countries only) – CAS Cable C39195-
A7700-B13
● Symmetrical trunk (120 ohms)
The impedance converter F31505-E1-A146 must be used for connecting to a symmetrical
trunk.
Figure 3-96 TCAS-2, TCASR-2 (for selected countries only) – Impedance Converter
F31505-E1-A146
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
● CAS cable shield contacts

To ensure sufficient electromagnetic shielding (according to EN 55022), both shielded
CAS cables must be contacted at the appropriate points on the HiPath 3550/HiPath 3350.
Procedure:
Fix the cable shielding (B) for both CAS cables (A) via cable binder (C) to the T tongue (D)
of the housing, so a continuously conductive contact is created between the conductive
tape on the cable shielding and the housing (see figure).
Figure 3-97 CAS cable – shield contacting
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.28 TLA2 (Not for U.S.), TLA4 (Not for U.S.), TLA8 (not for U.S.)
Introduction
The MSI boards TLA2, TLA4 and TLA8 provide 2, 4 and 8 analog trunks (DP and DTMF dialing
method) for HiPath 3550 and HiPath 3350 (wall housing).
Interfaces
T/R ports 1
MSI 1 - 4 X2 50
TLA2/4
to CO 8
(Trunk 3, 4
1 to CUP / CUC
not in X3 (not used)
TLA2!) X1
8
1
to GEE X4 2
Module 10
Figure 3-98 TLA2, TLA4 (not for U.S.) - Interfaces (S30817-Q923-Bxxx, -Axxx)
Table 3-113 TLA2, TLA4 (not for U.S.) - Contact Assignments

1 a trunk 1 GND for GEE50 FKR, otherwise free
2 b trunk 1 b trunk 1
3 a trunk 2 a trunk 1
9 a trunk 41
10 Call charging module assignment (GMZ)
1 Not for TLA2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
The MSI board TLA8 with eight analog trunks for DP and DTMF signalling in HiPath 3550 and
HiPath 3350
.
1
to GEE X3
Module
10
50
1
T/R ports
MSI 1 - 4 X2 TLA8
To CO 8 to CUP/CUC
X1
T/R ports 1
MSI 5 - 8 X4
To CO 8 2
1
to GEE X5
Module
10
Figure 3-99 TLA8 (not for U.S.) - Interfaces (S30817-Q926-Axxx)
Table 3-114 TLA8 (not for U.S.) - Contact Assignments
Contact Connector X3 Connector X2 Connector X4 Connector X5

1 GND a trunk 1 a trunk 5 GND
2 b trunk 1 b trunk 1 b trunk 5 b trunk 5
3 a trunk 1 a trunk 2 a trunk 6 a trunk 5
9 a trunk 4 – – a trunk 8
10 GMZ 1 – – GMZ 2
GMZ= Call charging module assignment
GND= GND for GEE50 FKR, otherwise free
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.29 TLA4R (not for U.S.)
Introduction
The TLA4R (Trunk Line Analog Rack) board provides four ports for the analog trunk connection
(DP and DTMF signaling methods) on HiPath 3500 and HiPath 3300 (19-inch housing). There
are also two ALUM power failure transfers.
The transmission and function-oriented characteristics of the TLA4R are completely identical
to those of the TLA boards that are used in HiPath 3550 and HiPath 3350. The only differences
are
● the two ALUMs which are only available on the TLA4R.
● the call metering receiving equipment interface, which is only on the TLA boards.
Interfaces
11 50
Trunk 1 18
: 21
:
: X1 to CUPR /
Trunk 4 CUCR
8 RJ45 X5
jacks
ALUM 2
1+2
88
Figure 3-100 TLA4R (not for U.S.) - Interfaces (S30817-Q923-Zxxx)
Table 3-115 TLA4R (not for U.S.) - Contact Assignments
RJ45 jack X5, Pin Trunk connections 1-4

1 14 a trunk 1
15 b trunk 1
2 24 a trunk 2
25 b trunk 2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-115 TLA4R (not for U.S.) - Contact Assignments
3 34 a trunk 3
35 b trunk 3
4 44 a trunk 4
45 b trunk 4
RJ45 jack X5, Pin ALUM 1 + 2
5 54 TB1 ALUM1: Stn card connection
55 TA1
6 64 TB2 ALUM2: Stn card connection
65 TA2
7 74 BE1 ALUM1: Analog telephone
75 AE1 connection
8 84 BE2 ALUM2: Analog telephone

85 AE2 connection
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.30 TM2LP
Introduction
The TM2LP (Trunk Module Loop Procedure) board connects up to eight analog trunks to Hi-
Path 3800 using the loop-start protocol.
Front panel

● LED (red)
● LED (green)
Figure 3-101 TM2LP - Front Panel (S30810-Q2159-Xxxx)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-116 TM2LP - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.

A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-117 TM2LP - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector TM2LP MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17
9 Free
brn/red 18
red/grn 19
10 Free
grn/red 20
blk/blu 24
11 Free
blu/blk 25
blk/ora 26
12 Free
ora/blk 27
blk/grn 29
13 Free
grn/blk 30
blk/brn 31
14 Free
brn/blk 32
blk/grn 34
15 Free
grn/blk 35
yel/blu 37
16 Free
blu/yel 38
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-118 TM2LP - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
TM2LP Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
4 8a
8
5 8b
4
9 Free
5
4
10 Free
5
4
11 Free
5
4
12 Free
5
4
13 Free
5
4
14 Free
5
4
15 Free
5
4
16 Free
5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-118 TM2LP - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
TM2LP Notes
No. Pin
4
17 Free
5
4
18 Free
5
4
19 Free
5
4
20 Free
5
4
21 Free
5
4
22 Free
5
4
23 Free
5
4
24 Free
5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-119 TM2LP - Connector Panel Assignment with CHAMP Jack (for U.S. only)
CHAMP jack TM2LP Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9
Free
34
10
Free
35
11
Free
36
12
Free
37
13
Free
38
14
Free
39
15
Free
40
16
Free
41
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-120 TM2LP - Connector Panel Assignment with SIPAC 1 SU Connectors (Cable
for Ports 1 - 16)
Pair TM2LP MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11
9 Free
brn/red 31
red/grn 02
10 Free
grn/red 22
blk/blu 13
11 Free
blu/blk 33
blk/ora 04
12 Free
ora/blk 24
blk/grn 15
3 13 Free
grn/blk 35
blk/brn 06
14 Free
brn/blk 26
blk/grn 17
15 Free
grn/blk 37
yel/blu 08
4 16 Free
blu/yel 28
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.31 TMAMF (for selected countries only)
Introduction
The TMAMF (Trunk Module Analog for MultiFrequency Code Signaling) board contains eight
trunks for analog direct inward dialing. The system supports MFC-R2 signaling (default setting),
MFC-R2 with caller ID, tone dialing, and dial pulsing. It is not possible to use DTMF and MFC-
R2 (with or without caller ID) simultaneously.
The board is implemented in HiPath 3550 and has the part number S30810-Q2587-A400.
Switches and LEDs
LEDs
H0 (green) H100 (yellow)
:
:
:
:
H7
0 On
: Lockout switch S501
: (factory default)
7
Subminiature D connector for

DSP diagnosis
Figure 3-102 TMAMF (S30810-Q2587-Axxx)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Notes on DSP diagnosis

You can use the trace function built into the TMAMF module to diagnose malfunctions or obtain
more precise error analysis. The subminiature D connector provides information about MFC-
R2 signaling. To activate the trace function, you must connect a PC with a terminal emulation
program (such as, Microsoft HyperTerminal).
Terminal configuration:
● Bits per second = 19,200
● Data bits = 8
● Stop bit = 1
● Parity = none
● Flow control = none
Pin assignments of the diagnostic cable
TMAMF: Subminiature D connector PC: RS-232 interface
1 2 3 4 5 5 4 3 2 1
6 7 8 9 9 8 7 6
1 1
2 3
3 2
5 5
Figure 3-103 Pin Assignments of the TMAMF Diagnostic Cable
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

● H100 LED (see Figure 3-102): signal processor status
Table 3-121 TMAMF - LED Statuses (H100)
LED status Meaning Action

(on/off)
Off –
Flashing The DSP (digital signal processor)
(250/250 ms) is waiting for DID digits
On The DSP is being reset
During Operation
Off The DSP is idle
Flashing Error: the DSP has not yet received Replace the board.
(250/250 ms) the DID digits.
On The MFC-R2 filter is on
● LEDs H0 to H7 (see Figure 3-102): trunk status
Table 3-122 TMAMF - LED Statuses (H0 to H7)
LED status Meaning Action

(on/off)
During Operation
Off The trunk is idle; no seizure
On The trunk was seized
Flashing Trunk out of service (e.g. S1/x Check whether the trunk was de-
(500/500 ms) “closed”) activated using HiPath 3000/
5000 Manager E or the lockout
switch.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-123 TMAMF - Cable Assignment

SU con-
Pair TMAMF Notes
Group (tip) (ring) MDFU-E MW8 pin
BP: Xx8
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11
9 Free
brn/red 31
red/grn 02
10 Free
grn/red 22
blk/blu 13
11 Free
blu/blk 33
blk/ora 04
12 Free
ora/blk 24
blk/grn 15
3 13 Free
grn/blk 35
blk/brn 06
14 Free
brn/blk 26
blk/grn 17
15 Free
grn/blk 37
yel/blu 08
4 16 Free
blu/yel 28
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.32 TLANI2, TLANI4, TLANI8
Introduction
TLANI2, TLANI4 and TLANI8 boards provide 2, 4 and 8 interfaces for the analog trunk connec-
tion (MSI: ground start or loop start) for HiPath 3550 and HiPath 3350 (wall housing).
The interfaces for analog trunk connection support the CLIP feature and call detail recording
with 12 kHz and 16 kHz impulses. Call detail recording is automatically selected in the country
setting for the system. Call detail recording with 50 Hz impulses is not supported.
Not all board country variants support call detail recording with 12 kHz and 16 kHz
> impulses.
Call detail recording can be activated and deactivated with HiPath 3000/5000 Manager E (Set-
tings menu: Lines/networking ... -> Trunks -> (double-click) Parameters -> MSI flags -> Flags -
> Charge module activated).
"Silent Reversal" is also supported, which is used to register the beginning and end of an out-
going call in different countries. It can be activated with HiPath 3000/5000 Manager E (Settings
menu: Lines/networking ... -> Trunks -> (double-click) Parameters -> MSI flags -> Flags -> Si-
lent Reversal).
The ÜFS (Supervisory Frequency System) trunks with direct inward dialing used in Austria are
not supported.
Warning
7 According to U.S. and Canadian installation instructions, analog trunks must be con-
nected over fuse elements in compliance with UL 497A or CSA C22.2 No. 226.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Interfaces
T/R ports 1 X106 X105

MSI 1 - 4 X2 123 123 50
(MSI 3, 4 not Jumper
8
for TLANI2)
To CUP /
X3 (free) X1 CUC
1
ALUM 1, 2 X4 TLANI2, TLANI4 2

8
Figure 3-104 TLANI2, TLANI4 – Interfaces (S30810-H2953-X1xx / -Xxx)
1 X106 X105
T/R ports 123 123 50
MSI 1 - 4 X2
Jumper
8
To CUP /
X1 CUC
1
T/R ports X4 TLANI8 2
MSI 5 - 8
8
Figure 3-105 TLANI8 – Interfaces (S30810-H2954-X1xx)
Jumper for setting the process for the analog trunk interfaces
Process settings for the analog trunk interface is via X105 and X106 jumpers.
● Loop start setting = Pins 1 – 2 closed (default)
● Ground start setting = Pins 2 – 3 closed
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Contact assignments
Table 3-124 TLANI2, TLANI4 – Contact Assignments
Contact Connector X2 Connector Connector X4 (ALUM)

X3
1 a, trunk 1 Not used b ALUM1: Subsc. line module con-
2 b, trunk 1 a nection
3 a, trunk 2 b ALUM2: Subsc. line module con-

4 b, trunk 2 a nection
5 a, trunk 3 b ALUM1: Analog telephone connec-

6 b, trunk 3 a tion
7 a, trunk 4 b ALUM2: Analog telephone connec-

8 b, trunk 4 a tion
Table 3-125 TLANI8 – Contact Assignments

1 a, trunk 1 a, trunk 5
2 b, trunk 1 b, trunk 5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.33 TLANI4R
Introduction
The TLANI4R board provides four interfaces for the analog trunk connection (MSI: ground start
or loop start) for HiPath 3500 and HiPath 3300 (19’-inch housing).
> impulses.
lent Reversal).
not supported.
Warning
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Interfaces
11 X106 X105 50
MSI 1 18 123 123
: 21
:
Jumper
: X1
8 MW8 MSI 4 to CUPR/
jacks X5 CUCR
ALUM 2
1+2
TLANI4R
88
Figure 3-106 TLANI4R – Interfaces (S30810-K2953-X2xx)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Contact assignments
Table 3-126 TLANI4R – Contact Assignments
RJ45 jack X5, pin Trunk connections 1-4

1 14 a, trunk 1
15 b, trunk 1
2 24 a, trunk 2
25 b, trunk 2
3 34 a, trunk 3
35 b, trunk 3
4 44 a, trunk 4
45 b, trunk 4
RJ45 jack X5, pin ALUM 1 + 2
5 54 b ALUM1: Subsc. line module connection
55 a
6 64 b ALUM2: Subsc. line module connection
65 a
7 74 b ALUM1: Analog telephone connection
75 a
8 84 b ALUM2: Analog telephone connection
85 a
● Loop start setting = Pins 1–2 closed (default)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.34 TMANI8
Introduction
The TMANI8 board provides eight interfaces for the analog trunk connection (MSI: ground start
or loop start) for HiPath 3800.
> impulses.
lent Reversal).
not supported.
Warning
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Front panel, LEDs
Two LEDs for

displaying the
board states: Jumper
X100
● LED (red) 321 Backplane
1
2 port
● LED (green) 3
X101
Figure 3-107 TMANI8 – Front Panel, LEDs (S30810-Q2327-Xxx)
● Loop start setting = Pins 1–2 closed (default)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-127 TMANI8 – LED States
Red LED Green Status Measure

LED
off off Board not receiving power or not plugged in Check plug contact on
correctly. board.
on off Board is receiving power and board test is
in progress.
Board is defective if status remains un- Replace board.
Loadware loading not successfully com- Replace board.
deactivated using E. If not, replace board.
HiPath 3000/5000 Manager E.
flashing off Loadware is being loaded.
off on Board test completed successfully. Board is
OK (idle state).
off flashing At least one subscriber line circuit is activat-
ed.

Table 3-128 TMANI8 - SIVAPAC Connector Assignment on the Backplane
a-wire b-wire
Pair SIVAPAC connector TMANI8 MDFU-E Notes
(Tip) (Ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-128 TMANI8 - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire
Pair SIVAPAC connector TMANI8 MDFU-E Notes
(Tip) (Ring)
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17
9 Free
brn/red 18
red/grn 19
10 Free
grn/red 20
blk/blu 24
11 Free
blu/blk 25
blk/ora 26
12 Free
ora/blk 27
blk/grn 29
13 Free
grn/blk 30
blk/brn 31
14 Free
brn/blk 32
blk/grn 34
15 Free
grn/blk 35
yel/blu 37
16 Free
blu/yel 38
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-129 TMANI8 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
TMANI8 Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
4 8a
8
5 8b
4
9 Free
5
4
10 Free
5
4
11 Free
5
4
12 Free
5
4
13 Free
5
4
14 Free
5
4
15 Free
5
4
16 Free
5
4
17 Free
5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-129 TMANI8 - Connector Panel Assignment with RJ45 Jacks

RJ45 jack
TMANI8 Notes
No. Pin
4
18 Free
5
4
19 Free
5
4
20 Free
5
4
21 Free
5
4
22 Free
5
4
23 Free
5
4
24 Free
5
Table 3-130 TMANI8 - Connector Panel Assignment with CHAMP Jack (for U.S. only)
CHAMP jack TMANI8 Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-130 TMANI8 - Connector Panel Assignment with CHAMP Jack (for U.S. only)
CHAMP jack TMANI8 Notes
9
Free
34
10
Free
35
11
Free
36
12
Free
37
13
Free
38
14
Free
39
15
Free
40
16
Free
41
Table 3-131 TMANI8 - Connector Panel Assignment with SIPAC 1 SU Connectors (Cable
for Ports 1 - 16)
Pair TMANI8 MDFU-E Notes
Group (Tip) (Ring) nector MW8 pin
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
for Ports 1 - 16)
Pair TMANI8 MDFU-E Notes
Group (Tip) (Ring) nector MW8 pin
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11
9 Free
brn/red 31
red/grn 02
10 Free
grn/red 22
blk/blu 13
11 Free
blu/blk 33
blk/ora 04
12 Free
ora/blk 24
blk/grn 15
3 13 Free
grn/blk 35
blk/brn 06
14 Free
brn/blk 26
blk/grn 17
15 Free
grn/blk 37
yel/blu 08
4 16 Free
blu/yel 28
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.35 TMC16 (for selected countries only)
Introduction
The trunk module TMC16 (Trunk Module Central Office) connects up to 16 analog ground-start
or loop-start trunks with the HiPath 3800.
Front panel

● LED (red)
● LED (green)
Figure 3-108 TMC16 (for selected countries only) (S30810-Q2485-X) - Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-132 TMC16 (for selected countries only) - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.

● For connecting to the connector panels with CHAMP jack: Table 3-134
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-133 TMC16 (for selected countries only) - SIVAPAC Connector Assignment on the
Backplane
a-wire b-wire
Pair SIVAPAC connector TMC16 MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17 9a 9a
9 Port 9
brn/red 18 9b 9b
red/grn 19 10a 10a
10 Port 10
grn/red 20 10b 10b
blk/blu 24 11a 11a
11 Port 11
blu/blk 25 11b 11b
blk/ora 26 12a 12a
12 Port 12
ora/blk 27 12b 12b
blk/grn 29 13a 13a
13 Port 13
grn/blk 30 13b 13b
blk/brn 31 14a 14a
14 Port 14
brn/blk 32 14b 14b
blk/grn 34 15a 15a
15 Port 15
grn/blk 35 15b 15b
yel/blu 37 16a 16a
16 Port 16
blu/yel 38 16b 16b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-134 TMC16 (for selected countries only) - Connector Panel Assignment with
CHAMP Jack
CHAMP jack TMC16 Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9 9a 9 Ring
Port 9
34 9b 9 Tip
10 10a 10 Ring
Port 10
35 10b 10 Tip
11 11a 11 Ring
Port 11
36 11b 11 Tip
12 12a 12 Ring
Port 12
37 12b 12 Tip
13 13a 13 Ring
Port 13
38 13b 13 Tip
14 14a 14 Ring
Port 14
39 14b 14 Tip
15 15a 15 Ring
Port 15
40 15b 15 Tip
16 16a 16 Ring
Port 16
41 16b 16 Tip
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
SIPAC 1 SU Connectors (Cable for Ports 1 - 16)
Pair TMC16 MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11 9a 9a 4
9 Port 9
brn/red 31 9b 9b 5
10 Port 10
11 Port 11
12 Port 12
3 13 Port 13
14 Port 14
15 Port 15
4 16 Port 16
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.36 TMCAS (for selected countries only)
Introduction
For V1.0 and later, TMCAS (Trunk Module Channel Associated Signaling) boards can be used
in HiPath 3550 to support the country-specific CAS protocol.
The board converts the Euro-ISDN protocol on an S2M link into the Channel Associated Signal-
ing (CAS) protocol. The board functions only in connection with a TS2 (HiPath 3550). There is
no direct connection between the TMCAS board and the system’s central control unit. The
TMS2/TS2 handles all signaling and data traffic.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Switches and display
Display H1
25-pin SUB-D jack:

V24 interface for connecting the
X10
service PC with the ECGM tool
Battery
Lockout switch
S1
(position = free, factory default)
Switch S4
1
Off
= default
Jumper
S2
3 2 1
S3
Figure 3-109 TMCAS (S30810-Q2938-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

Use the ECGM tool for administration. For information on installing the software on the service
PC and on the required settings, see Page 3-288.
You can use the C39195-Z7267-C13 cable for the connection between jack X10 and the ser-
vice PC.
Switches S4-1 to S4-4 for setting the impedance

To ensure that the TMCAS works properly, the same impedance must be selected both on the
S2M side of the TMCAS and on the TS2 (HiPath 3550) board.
Impedance on the CAS Side Switch settings

S4-1 S4-2
120 ohms (default) Off Off
100 ohms On Off
75 ohms Off On
No function On On
Impedance on the S2M Side Switches
S4-3 S4-4
120 ohms (default) Off Off
100 ohms On Off
75 ohms Off On
No function On On
Switches S4-5 to S4-8
Switches Function
S4-5 Reserved
S4-6 Flash memory: only for laboratory purposes (the flash memory
is erased when switch is set to “On”).
S4-7 Reserved
S4-8 Battery: Select the “On” switch position to make the connection
to the processor’s real-time clock only after the protocol con-
verter has been configured.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Jumpers S2 and S3 for GND connection

You can set the GND connection (signal ground) of the receiving (Rx) and transmitting (Tx)
lines on the CAS side here.
GND connection Jumper setting

no signal ground (default) S2 = 1 - 2, S3 = 1 - 2
signal ground on receive lines (Rx) on the CAS side S2 = 2 - 3
signal ground on the transmit lines (Tx) on the CAS S3 = 2 - 3
side
Recommendations for the GND connection:
● symmetrical trunk (120 ohms)
Ground the cable’s shield on the side of the connected device (NT, MUX, modem).
Do not ground the shield on both ends of the cable.
– Tx: Ground the cable’s shield on the TMCAS side.
– Rx: Ground the cable’s shield on the side of the connected device (NT, MUX, modem).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Seven-segment display H1
The board statuses listed in the following table are displayed on H1.
Table 3-136 TMCAS - Seven-Segment Display H1
Display Meaning
Waiting for the TMCAS software download
TMCAS software download start
TMCAS software download
Writing the TMCAS software/extender software into the flash memory
Loading the TMCAS software/extender software from the flash memory
Waiting for ECGM command (10 s)
Calculating the checksum
No TMCAS software in the flash memory, waiting for reload
Flash memory erased (changing display)
TMCAS board active
TMCAS board active, boot process completed
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Assignments for the two TMCAS cables for HiPath 3550

You can use one of the following two cables to connect the network terminator NT, multiplexer
MUX, or modem to the TMCAS board:
● symmetrical trunk (120 ohms)
Table 3-137 Assignment of the TMCAS Cable C39195-A9700-B512
SU connector Xx8, pin Function Color code

2 a-wire (T), receive grn
22 b-wire (R), receive blk
6 a-wire (T), transmit red
26 b-wire (R), transmit blk
Table 3-138 Assignment of the TMCAS Cable C39195-A9700-B514
SU connector Xx8, pin Function Wire

2 a-wire (T), receive BNC shield, cable 1
22 b-wire (R), receive BNC signal, cable 1
6 a-wire (T), transmit BNC shield, cable 2
26 b-wire (R), transmit BNC signal, cable 2
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Procedure for retrofitting a TMCAS board
Step Activity
1. Disconnect system from power supply and open system.
2. Insert TS2 (HiPath 3550).
3. ● HiPath 3550 (wall housing): Insert TMCAS in slot 10.
4. Plug in TMS2/TS2-TMCAS connection cable.
5. Connect the NT to the system using the TMCAS cable.
6. Close the system and connect it to the power supply.
7. After the system has booted, both boards are entered in the system’s database
(TMS2 or TS2 and TMCAS).
8. If necessary, configure with HiPath 3000/5000 Manager E.
Possible problems:
● TMCAS not entered in HiPath 3000/5000 Manager E
The TMCAS is displayed automatically after the generation/regeneration of the database
in a system with a correctly inserted and connected TMCAS-TMS2/TS2 combination.
● Missing electrical connection between TMS2/TS2 and TMCAS
No TMCAS entry in the database. If a correctly configured database (with TMCAS insert-
ed offline) is then loaded into the system using generation/regeneration, the TMCAS con-
figured in HiPath 3000/5000 Manager E appears only in the software configuration.
● Incompatible board configuration
There is a correctly inserted TMCAS-TMS2/TS2 combination in the system. If there is a
different board entered in HiPath 3000/5000 Manager E in the HiPath 3550’s large slot,
the generation is rejected.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Installing the ECGM tool and configuring the CAS protocol converter
This section describes how to install the ECGM tool on the service PC and configure the CAS
protocol converter on the TMCAS board.
The ECGM tool supports the following actions:
● Extender, database and software download
● CAS protocol configuration
● Database programming
● Trace options
Procedure
Step Activity
1. Create directory c:\ecginst on the service PC.
2. Set up the connection to the download server (for information on this, contact your
local ITSC) and copy the following files into the directory c:\ecginst:
● e1v0xx.exe (for example, e140ah.exe)
● Ee1v0yy.exe (for example, Ee140am.exe)
● Ecgm_vzz.exe (for example Ecgm_4aa.exe)
Explanation of the variables:
● v = software version
● xx = country version of a file
● yy = file version for channels
● zz = file version for maintenance
3. Run .exe files. This will extract the following files, for example:
● Ecgm.cab (WinZip file)
● Setup.lst (LST file)
● Setup.exe (EXE file)
● 4brazil.iam (IAM file)
● Ecg_edb4.ein (EIN file)
● 4brazil.eam (EAM file)
● E140ah.sin (SIN file)
● E140ah.pnm (PNM file)
● X140pai.pnm (PNM file)
● X130aq.pnm (PNM file)
4. Execute Setup.exe file. This will create the directory ecgm and extract various
files.
5. Copy vbrazil.iyy (for example, 4brazil.iam) to the directory ecgm.
6. Run the file ecgm.exe.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Step Activity
7. Make the following settings in the ECGM tool:
● File/Options menu: Select the service PC’s COM interface (for example:
COM1)
● File/Install Software menu: Select the file E1v0xx.pnm (for exam-
ple, E140ah.pnm from the directory ecginst.
● File/Install Edb menu: Select the file Ecg_edbv.ein (for example
Ecg_edb4.ein) from the directory ecginst.
● File/Update Site menu:
– Under ECG SOFTWARE, select loadware file E1v0xx.pnm.
– Under “ECG EDB”, select file vbrazil.iyy.
– Under “FILE NAME”, select file extension .db for logging TMCAS
events.
– Enter the customer name under “ECG NAME.
8. Close the ECGM tool and then restart (ecgm.exe).
9. Enter the COM interface under “COMM” and the customer name in the Set-
tings/ECG Name menu. All other windows are updated automatically.
10. Channel configuration
Define the channel parameters in the View/Database menu (reserve unused
channels with “Out of Service”):
● Protocol
● Signaling method (incoming and outgoing)
● Clock master (always central office)
● Operator number (corresponds to the number of the attendant console of the
HiPath 3000)
11. Software download
If the seven-segment display H1 on the TMCAS displays “H”, it is necessary to
download the extender software (Download/Extender menu). Otherwise, con-
tinue with the next step.
12. Start the software/database download using the Download/Software and
Database menu. This procedure takes approximately 8 minutes.
The download is complete when the configured channels display the “Idle” status.
The seven-segment display H1 on the TMCAS shows “A” (= active).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.37 TMCAS-2 (for selected countries only)
Introduction
The TMCAS-2 card (Trunk Module Channel Associated Signaling) can be used in HiPath 3800
for V5.0 SMR-10 and later to support country-specific CAS protocols.
The card features two E1-CAS interfaces, which together support up to 60 B channels.
Both coaxial trunks (75 ohms) and symmetrical trunks (120 ohms) can be connected to the 15-
pin sub-D jacks on the card.
TMCAS-2 functions as a converter, which converts the Euro-ISDN protocol on an S2M link to
the Channel Associated Signaling (CAS) protocol. In contrast to the predecessor PBXXX card,
TMCAS-2 communicates directly with the central control in the system. All signaling and data
traffic goes through TMCAS-2. Unlike PBXXX, a connection with an S2M card is therefore not
required.
Up to three TMCAS-2 cards can be used in a HiPath 3800.
Figure 3-110 TMCAS-2 (S30810-Q2946-X) (for selected countries only) – Figure
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Interfaces and jumpers
1 Modem (optional)
X21 X20 321

X24 X16
X909: CAS
interface 1 123
3
X999 X17
2
1
X910: CAS
interface 2 X25
123
X803: V.24 interface 321

X11
X12
X804: Ethernet (10/
100BaseT) X14
interface X13
Figure 3-111 TMCAS-2 (for selected countries only) – Interfaces and Jumpers
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Settings
Table 3-139 TMCAS-2 (for selected countries only) – Jumper Functions

Jumper Function Setting
Pins 1–2 closed Pins 2–3 closed
X11 Sets the V.24 baud rate See Table 3-140
X12
X14
X13 Deletes the flash mem- Flash memory is deleted Flash memory is not de-
ory (all sectors apart from U- leted.
boot (firmware)). (default setting)
X16 Resets card Reset performed. Reset not performed.
(default setting)
X17 Hardware watchdog Watchdog active. Watchdog is not active.
(default setting)
X24 Sets trunk impedance 75 ohms 120 ohms
for CAS interface 1 (default setting)
X25 Sets trunk impedance 75 ohms 120 ohms
for CAS interface 2 (default setting)
X999 Grounding: card / CAS Grounding for the card is Grounding for the card is
cable connected to the ground- not connected to the
ing for the CAS cable. grounding for the CAS
cable.
(default setting)
Table 3-140 TMCAS-2 (for selected countries only) – Jumper for Setting the V.24 Baud
Rate
V.24 baud rate Jumper
(Kbps) X11 X12 X14
9,6 Open Open Open
(default setting)
19,2 Open Open Closed
38,4 Closed Open Closed
57,6 Open Closed Closed
115,2 Closed Closed Closed
9,6 All other configurations
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Front panel
X909 (15-pin Sub-D jack): CAS interface 1
X910 (15-pin Sub-D jack): CAS interface 2
X803 (9-pin MINI DIN jack): V.24 interface
X804 (RJ45 jack): Ethernet (10/100BaseT) interface

Two LEDs indicate the current interface status:
● Yellow LED = transmitting data
● Green LED = receiving data
Figure 3-112 TMCAS-2 (for selected countries only) – Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
The card’s software status can be ascertained on the basis of the seven-segment display. For
this a distinction is made between the following boot phases:
Power supply unit switched on
The decimal point is flashing to indicate that the U-

U-boot
boot firmware is operational.
(Firmware)
The decimal point is activated (not flashing) to indi-

Linux operating system
cate initialization of the Linux operating system.
initialization
The decimal point is activated when the card sup-

CAS application software
plies the clock reference for the system.
● U-boot (firmware) states

Table 3-141 TMCAS-2 (for selected countries only) – U-boot (firmware) States
Display Meaning
Initializing hardware
Downloading DSP (Digital Signal Processor) firmware
Downloading FPGA (Field Programmable Gate Array) firmware
Accessing flash EPROM (Save and Delete)
Activating built-in self test BIST (BIST1 or BIST2)
Administration (Service PC connected)
Copying software (from SDRAM to FEPROM)
Downloading image file (Linux and CAS application)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-141 TMCAS-2 (for selected countries only) – U-boot (firmware) States
Display Meaning
Initializing the Linux operating system
Error
Resetting card
U-boot (firmware) operational (decimal point flashing)
● Linux operating system states

Table 3-142 TMCAS-2 (for selected countries only) – Linux Operating System States
Display Meaning
Linux kernel boot
User space boot
Check and mount flash
Error found, mounted file system rebuild, reboot
Mounting flash file system
Error mounting flash (flashing display)
Configuring network interface
Loading real-time kernel modules
Loading board-specific modules
Core files available
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
● CAS application software states
CAS application operational (flashing display)
Figure 3-113 TMCAS-2 (for selected countries only) – CAS Application Software States
Modem (optional)
X21: Pin1
Figure 3-114 TMCAS-2 (for selected countries only) – Optional Modem

The analog modem (S30122-X8004-X22) is an optional subboard for the TMCAS-2 card, which
is plugged into the X20 and X21 ports. This facilitates remote administration of the CAS proto-
col converter on the TCAS-2 and TCASR-2 cards (see Page 3-297).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards

A separate tool, the CAS Manager, is used to download the software and administer the TM-
CAS-2. The CAS Manager software is stored on a CD supplied with the card. For information
on how to install the CAS Manager software on the Service PC, refer to the readme file.
The following options are available for accessing the card:
● Via the V.24 interface (9-pin MINI DIN jack X803) and the connection cable C39195-
A9700-B532.
● Via the Ethernet (10/100BaseT) interface (RJ45 jack X804).
● Via the optional analog modem (S30122-X8004-X22). In this case, you will need to estab-
lish a connection from the analog modem to a free port on an analog subscriber line mod-
ule. Use a connection cable (open-end cable (24 DA): S30267-Z196-A150 = 15 m long,
S30267-Z196-A250 = 25 m long) (blue in Figure 3-115) to connect the backplane (TM-
CAS-2) to the main distributor frame or patch panel and vice versa. Insert the required
jumpers in the main distributor frame or patch panel (green in Figure 3-115).
HiPath 3800
X803 CAS
Backplane: TMCAS-2 V.24 interface Manager
Analog sub- X1-2
scriber line X1-26 Modem
module (optional)
X804
Ethernet (10/100BaseT) interface
Analog trunk CAS

board Manager
IP Network
CAS
Manager
PSTN
Main distributor frame / patch panel
Figure 3-115 TMCAS-2 (for selected countries only) – Connection Options for Card Admin-
istration using CAS Manager
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Assigning both CAS cables

You can use one of the following two cables to connect network terminators (NT), multiplexers
(MUX), or modems to the TMCAS-2 card (15-pin sub-D jacks X909 and X910):
● Symmetrical trunk (120 ohms), length = 10 m
Table 3-143 TMCAS-2 (for selected countries only) – Assignment of the CAS Cable
S30267-Z167-A100
15-pin Sub-D connector Function Color code

pin
9 a-wire (T), transmit wht/blu
1 b-wire (R), transmit blu/wht
15 a-wire (T), receive wht/ora
8 b-wire (R), receive ora/wht
● Coaxial trunk (75 ohms), length = 10 m
C39195-A7700-B14
Wire Function 15-pin Sub-D con- BNC connector

nector
Pin
1 Receive, Tip 8 Shield
Receive, Ring 15 Conductor
2 Transmit, Tip 1 Shield
Transmit, Ring 9 Conductor
BNC connector
15-pin Sub-D connec-

tor
Figure 3-116 TMCAS-2 (for selected countries only) – CAS Cable C39195-A7700-B14
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.38 TMDID (for U.S. only)
Introduction
The TMDID board (Trunk Module Direct Inward Dialing) provides direct inward dialing from the
central office (CO) to HiPath 3800.
The board has eight trunk circuits that connect to analog trunks.
The circuits can be set up for Immediate Start or Wink Start.
> tors. Since the TMDID board has SIVAPAC connector strips, you will have to install
a SIVAPAC-SIPAC board adapter in order to be able to use it in HiPath 3800.
For information on upgrade procedures, please see Section 4.2.5.5.
Switches
● Switches for manual trunk selection. In this case, all trunks are filtered one after the other
until the LED of the desired trunk flashes.
● Lockout switch which can be used to manually block the selected trunk circuit.
Table 3-145 TMDID (for U.S. only) - LED Statuses
LED status Meaning

0-7
Off The trunk circuit is free.
On The trunk circuit is assigned.
Slow flashing The trunk circuit was deactivated by the software.
Fast flashing The switch was pressed and the trunk circuit was selected for manual acti-
vation or deactivation.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Front panel
LEDs (green) for displaying the trunk status:

● Trunk circuit 0
● Trunk circuit 1
● Trunk circuit 2
● Trunk circuit 3
● Trunk circuit 4
● Trunk circuit 5
● Trunk circuit 6
● Trunk circuit 7
Switch
Lockout switch
Figure 3-117 TMDID (for U.S. only) (S30810-Q2452-X) - Front Panel

A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-146 TMDID (for U.S. only) - SIVAPAC Connector Assignment on the Backplane
a-wire b-wire
Pair SIVAPAC connector TMDID MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17
9 Free
brn/red 18
red/grn 19
10 Free
grn/red 20
blk/blu 24
11 Free
blu/blk 25
blk/ora 26
12 Free
ora/blk 27
blk/grn 29
13 Free
grn/blk 30
blk/brn 31
14 Free
brn/blk 32
blk/grn 34
15 Free
grn/blk 35
yel/blu 37
16 Free
blu/yel 38
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-147 TMDID (for U.S. only) - Connector Panel Assignment with CHAMP Jack
CHAMP jack TMDID Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9
Free
34
10
Free
35
11
Free
36
12
Free
37
13
Free
38
14
Free
39
15
Free
40
16
Free
41
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-148 TMDID (for U.S. only) - Connector Panel Assignment with SIPAC 1 SU Con-
Pair TMDID MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11
9 Free
brn/red 31
red/grn 02
10 Free
grn/red 22
blk/blu 13
11 Free
blu/blk 33
blk/ora 04
12 Free
ora/blk 24
blk/grn 15
3 13 Free
grn/blk 35
blk/brn 06
14 Free
brn/blk 26
blk/grn 17
15 Free
grn/blk 37
yel/blu 08
4 16 Free
blu/yel 28
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.39 TMDID2 (for selected countries only)
Introduction
TMDID2 (Trunk Module Direct Inward Dialing) provides direct inward dialing from the central
office (CO) to HiPath 3800 V6.0 SMR-10 or later.
The board has eight trunk circuits that connect to analog trunks. The board supports the proto-
cols Wink Start, Delay Dial, and Immediate Start.
Figure 3-118 TMDID2 (S30810-Q2197-T) (for selected countries only)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Front panel

● LED (red)
● LED (green)
Figure 3-119 TMDID2 (for selected countries only) - LEDs on the Front Panel
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-149 TMDID2 (for selected countries only) - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.

A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-150 TMDID2 (for selected countries only) - SIVAPAC Connector Assignment on the
Backplane
a-wire b-wire
Pair SIVAPAC connector TMDID2 MDFU-E Notes
(tip) (ring)
wht/blu 1 1a 1a
1 Port 1
blu/wht 23 1b 1b
wht/ora 3 2a 2a
2 Port 2
ora/wht 4 2b 2b
wht/grn 5 3a 3a
3 Port 3
grn/wht 6 3b 3b
wht/brn 7 4a 4a
4 Port 4
brn/wht 8 4b 4b
wht/grn 9 5a 5a
5 Port 5
grn/wht 10 5b 5b
red/blu 11 6a 6a
6 Port 6
blu/red 12 6b 6b
red/ora 13 7a 7a
7 Port 7
ora/red 14 7b 7b
red/grn 15 8a 8a
8 Port 8
grn/red 16 8b 8b
red/brn 17
9 Free
brn/red 18
red/grn 19
10 Free
grn/red 20
blk/blu 24
11 Free
blu/blk 25
blk/ora 26
12 Free
ora/blk 27
blk/grn 29
13 Free
grn/blk 30
blk/brn 31
14 Free
brn/blk 32
blk/grn 34
15 Free
grn/blk 35
yel/blu 37
16 Free
blu/yel 38
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-151 TMDID2 (for selected countries only) - Connector Panel Assignment with RJ45
Jacks
RJ45 jack
TMDID2 Notes
No. Pin
4 1a
1
5 1b
4 2a
2
5 2b
4 3a
3
5 3b
4 4a
4
5 4b
4 5a
5
5 5b
4 6a
6
5 6b
4 7a
7
5 7b
4 8a
8
5 8b
4
9 Free
5
4
10 Free
5
4
11 Free
5
4
12 Free
5
4
13 Free
5
4
14 Free
5
4
15 Free
5
4
16 Free
5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Jacks
RJ45 jack
TMDID2 Notes
No. Pin
4
17 Free
5
4
18 Free
5
4
19 Free
5
4
20 Free
5
4
21 Free
5
4
22 Free
5
4
23 Free
5
4
24 Free
5
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-152 TMDID2 (for selected countries only) - Connector Panel Assignment with
CHAMP Jacks (for U.S. only)
CHAMP jack TMDID2 Notes
1 1a 1 Ring
Port 1
26 1b 1 Tip
2 2a 2 Ring
Port 2
27 2b 2 Tip
3 3a 3 Ring
Port 3
28 3b 3 Tip
4 4a 4 Ring
Port 4
29 4b 4 Tip
5 5a 5 Ring
Port 5
30 5b 5 Tip
6 6a 6 Ring
Port 6
31 6b 6 Tip
7 7a 7 Ring
Port 7
32 7b 7 Tip
8 8a 8 Ring
Port 8
33 8b 8 Tip
9
Free
34
10
Free
35
11
Free
36
12
Free
37
13
Free
38
14
Free
39
15
Free
40
16
Free
41
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
SIPAC 1 SU Connectors (cable for ports 1-16)
Pair TMDID2 MDFU-E Notes
wht/blu 19 1a 1a 4
1 Port 1
blu/wht 39 1b 1b 5
wht/ora 38 2a 2a 4
2 Port 2
ora/wht 48 2b 2b 5
wht/grn 27 3a 3a 4
1 3 Port 3
grn/wht 47 3b 3b 5
wht/brn 16 4a 4a 4
4 Port 4
brn/wht 46 4b 4b 5
wht/grn 05 5a 5a 4
5 Port 5
grn/wht 45 5b 5b 5
red/blu 14 6a 6a 4
6 Port 6
blu/red 44 6b 6b 5
red/ora 23 7a 7a 4
7 Port 7
ora/red 43 7b 7b 5
red/grn 32 8a 8a 4
2 8 Port 8
grn/red 42 8b 8b 5
red/brn 11
9 Free
brn/red 31
red/grn 02
10 Free
grn/red 22
blk/blu 13
11 Free
blu/blk 33
blk/ora 04
12 Free
ora/blk 24
blk/grn 15
3 13 Free
grn/blk 35
blk/brn 06
14 Free
brn/blk 26
blk/grn 17
15 Free
grn/blk 37
yel/blu 08
4 16 Free
blu/yel 28
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.40 TMEW2
Introduction
The TMEW2 board (Trunk Module for E&M World) provides four analog tie trunk circuits for
E&M signaling for HiPath 3800. Each tie trunk circuit has eight connectors: incoming speech
path (2), outgoing speech path (2), incoming signaling (2) and outgoing signaling (2). This al-
lows tie trunk traffic to other private communication systems.
Interface type 1A is released for E&M networking with Immediate Start, Wink Start, and Delay
Dial protocols.
> tors. Since the TMEW2 board has SIVAPAC connector strips, you will have to install
a SIVAPAC-SIPAC board adapter in order to be able to use it in HiPath 3800.
For information on upgrade procedures, please see Section 4.2.5.5.
Note on E&M networking compatibility

TMEW2 does not support E&M interface types 1, 1B, 2, 3, and 5 on the TIEL board.
The following options are available when replacing a HiPath 3750 or HiPath 3700 system with
a HiPath 3800 system:
1. Switch customer-specific E&M networking to interface 1A on the TMEW2 board (Im-
mediate Start, Wink Start or Delay Dial protocols).
2. If option 1 is not possible for technical reasons, HiPath 3750 or HiPath 3700 remains
active as the E&M gateway. Create a TDM network with the CorNet protocol between
the HiPath 3750 or HiPath 3700 system and HiPath 3800.
Speech paths
Speech paths always use four wires (two wires for the incoming speech path and two wires for
the outgoing speech path). The advantage of providing separate speech paths for incoming
and outgoing calls is that it helps maintain call stability (echo). In addition, repeaters in the
transmission equipment compensate for attenuation loss on the line.
Signaling paths
E&M trunks are used for signaling between networked communications systems: E-wire = ear
(receive), M-wire = mouth (transmit).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Protocol settings
TMEW2 supports interface type 1A.
Before starting up the tie trunk, you must ensure that the two participating systems support in-
terface type 1A.
Remote system//transmission
equipment with TMEW2
TMEW2
E E
- 48 V E E
M M
- 48 V
Figure 3-120 E&M Interface Type 1A

The following signaling protocols are supported:
● “Delay Dial” protocol
● “Wink Start” protocol
This is the most widely used protocol internationally.
● “Immediate Start” protocol
HiPath 3000/5000 Manager E is used to set the signaling protocol. Go to the Settings menu
and select Lines/networking –> Trunks –> (double-click) Parameters –> Template Editor:
● Board type = TMDID, TIEL, TMEW2
● Template: the following settings are possible:
– 4. E/M tieline with winkstart/delayed (= “Wink Start” protocol)
– 11. E/M tieline with delayed dialing (= “Delay Dial” protocol)
– 12. E/M tieline with immediate dialing (= “Immediate Start” protocol)
The interface type 1A is used in all cases.
SIVAPAC connector assignment on the backplane with tie trunk traffic over the interface type
1A is shown in Table 3-155.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Connecting the Genius announcement device

The TMEW2 board may be installed on interface type 2 for connecting the Genius announce-
ment device.
Remote system/transmission
equipment with TMEW2
TMEW2
E E
- 48 V E E - 48 V
SG SG
M M
SB SB
Figure 3-121 E&M Interface Type 2

Use HiPath 3000/5000 Manager E to configure the settings for the Genius announcement de-
vice: Go to the Settings menu and select Auxiliary equipment –> Announcement.
SIVAPAC connector assignment on the backplane with a Genius announcement device con-
nected (interface type 2A) is shown in Table 3-156.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Front panel

● LED (red)
● LED (green)
Figure 3-122 TMEW2 - Front Panel (S30810-Q2292-X100)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-154 TMEW2 - LED Statuses

LED
correctly. board.
in progress.
ager E.
OK (idle state).
ed.

SIVAPAC connector assignment on the backplane depends on how the board is used.
● Assignment in the case of tie trunk traffic over interface type 1A: Table 3-155.
● Assignment in the case of Genius announcement device connection (interface type 2):
Table 3-156.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Table 3-155 TMEW2 - SIVAPAC Connector Assignment on the Backplane in Tie Trunk Traf-
fic via Interface Type 1A
a-wire b-wire
Pair SIVAPAC connector TMEW2 MDFU-E Notes
(tip) (ring)
wht/blu 1 1ka 1a Ring
1 Port 1 Transmit
blu/wht 23 1kb 1b Tip
wht/ora 3 1ka 2a Ring
2 Port 2 Transmit
ora/wht 4 1kb 2b Tip
wht/grn 5 1ka 3a Ring
3 Port 3 Transmit
grn/wht 6 1kb 3b Tip
wht/brn 7 1ka 4a Ring
4 Port 4 Transmit
brn/wht 8 1kb 4b Tip
wht/grn 9 1ga 5a Ring
5 Port 1 Receive
grn/wht 10 1gb 5b Tip
red/blu 11 1ga 6a Ring
6 Port 2 Receive
blu/red 12 1gb 6b Tip
red/ora 13 1ga 7a Ring
7 Port 3 Receive
ora/red 14 1gb 7b Tip
red/grn 15 1ga 8a Ring
8 Port 4 Receive
grn/red 16 1gb 8b Tip
red/brn 17 1E 9a Ear
9 Port 1
brn/red 18 1M 9b Mouth
red/grn 19 1E 10a Ear
10 Port 2
grn/red 20 1M 10b Mouth
blk/blu 24 1E 11a Ear
11 Port 3
blu/blk 25 1M 11b Mouth
blk/ora 26 1E 12a Ear
12 Port 4
ora/blk 27 1M 12b Mouth
blk/grn 29 13a System ground, system
13 Port 1
grn/blk 30 13b battery
blk/brn 31 14a System ground, system
14 Port 2
brn/blk 32 14b battery
blk/grn 34 15a System ground, system
15 Port 3
grn/blk 35 15b battery
yel/blu 37 16a System ground, system
16 Port 4
blu/yel 38 16b battery
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Table 3-156 TMEW2 - SIVAPAC Connector Assignment on the Backplane with Genius An-
nouncement Device Connected (Interface Type 2):
a-wire b-wire
Pair SIVAPAC connector TMEW2 MDFU-E Notes
(tip) (ring)
wht/blu 1 1ka 1a Ring
1 Port 1 Transmit
blu/wht 23 1kb 1b Tip
wht/ora 3 1ka 2a Ring
2 Port 2 Transmit
ora/wht 4 1kb 2b Tip
wht/grn 5 1ka 3a Ring
3 Port 3 Transmit
grn/wht 6 1kb 3b Tip
wht/brn 7 1ka 4a Ring
4 Port 4 Transmit
brn/wht 8 1kb 4b Tip
wht/gry 9 1ga 5a
5 Port 1 Free
gry/wht 10 1gb 5b
red/blu 11 1ga 6a
6 Port 2 Free
blu/red 12 1gb 6b
red/ora 13 1ga 7a
7 Port 3 Free
ora/red 14 1gb 7b
red/grn 15 1ga 8a
8 Port 4 Free
grn/red 16 1gb 8b
red/brn 17 1E 9a Ear
9 Port 1
brn/red 18 1M 9b System ground
red/gry 19 1E 10a Ear
10 Port 2
gry/red 20 1M 10b System ground
blk/blu 24 1E 11a Ear
11 Port 3
blu/blk 25 1M 11b System ground
blk/ora 26 1E 12a Ear
12 Port 4
ora/blk 27 1M 12b System ground
blk/grn 29 13a Mouth
13 Port 1
grn/blk 30 13b System battery
blk/brn 31 14a Mouth
14 Port 2
brn/blk 32 14b System battery
blk/gry 34 15a Mouth
15 Port 3
gry/blk 35 15b System battery
yel/blu 37 16a Mouth
16 Port 4
blu/yel 38 16b System battery
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.41 TMGL4 (for U.S. only)
Introduction
A TMGL4 trunk module connects up to four analog ground-start or loop-start trunks to
HiPath 3550 and HiPath 3350.
Ground start is the default.
Warning
7 You must disconnect the power and remove the slip-on connectors from the TMGL4
board before removing it from the system.
Do not connect the slip-on connectors to the TMGL4 board until the board is seated
in its slot and the system power is on.
Failure to follow these instructions may severely damage the system.
Interfaces
50
1 to CUP/
To trunks X2 TMGL4 board X1 CUC
8
2
To ANI4 X3
Figure 3-123 TMGL4 (for U.S. only) - Interfaces (S30810-Q2918-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Contact assignment
Table 3-157 TMGL4 (for U.S. only) - Contact Assignment
Contact Connector X2 Port

1 b-wire (ring), trunk 1 1
2 a-wire (tip), trunk 1
Note: The pinouts shown are on the board itself. The main distribution frame cable (MDF cable)
supplied reverses the signal order before the MDF.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.42 TMGL4R (for U.S. only)
Introduction
A TMGL4R trunk module connects up to four analog ground-start or loop-start trunks to HiPath
3500 and HiPath 3300.
Ground start is the default.
Interfaces
1
To ANI4R X5 (MW10 jack) 50
11
To trunk 1 to CUPR/
X1
: CUCR
: X4 (4 MW4 jacks)
:
To trunk 4 2
44
To GEE X3
Figure 3-124 TMGL4R (for U.S. only) (S30810-K2918-Z)
If ANI4R is installed as option 1 or 2, TMGL4R board must be inserted in slot 4, 6 or

> 8 (slots 6 and 8 are not available with HiPath 3300).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Contact assignment
Table 3-158 TMGL4R (for U.S. only) - Contact Assignment
Port X3 Pin X4 Pin X5 Pin Signal

(To GEE) (To trunks 1-4) (To ANI4R)
1 3 12 3 b-wire (ring), trunk 1
2 13 2 a-wire (tip), trunk 1
– 10 – 10 Call charging module
assignment (GMZ)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.43 TMQ4 (for U.S. only)
Introduction
An TMQ4 (ISDN BRI) trunk module connects up to four digital trunks to the HiPath 3550 and
HiPath 3350.
The TMQ4 board provides basic rate interface (BRI) ISDN via a U2B1Q interface. The interface
supports the following central office protocols:
● AT&T 5Ess NI-1
● AT&T 5ESS Custom
● Nortel DMS100 NI-1
● Siemens EWSD NI-1
Interfaces
50
1
to CUP/
To trunks X2 TMQ4 board CUC
X1
8
Figure 3-125 TMQ4 (for U.S. only) (S30810-Q2917-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Contact assignment
Table 3-159 TMQ4 (for U.S. only) - Contact Assignment
Contact Connector X2 Port Contact Connector X2 Port

1 b-wire (ring), trunk 1 1 5 b-wire (ring), trunk 3
3
2 a-wire (tip), trunk 1 6 a-wire (tip), trunk 3
3 b-wire (ring), trunk 2 2 7 b-wire (ring), trunk 4
4
4 a-wire (tip), trunk 2 8 a-wire (tip), trunk 4
Note: The pinouts shown are on the board itself. The main distribution frame cable (MDF cable)
supplied reverses the signal order before the MDF.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.44 TST1 (for U.S. only)
Introduction
The digital T1/PRI trunk module (TST1) connects the communications server to primary rate
interface (PRI) ISDN via a T1 interface.
There are two versions of this board:
● S30810-Q2919-X - for use in the HiPath 3550 (wall housing)
● S30810-K2919-Z - for use in the HiPath 3500 (19-inch housing)
The board can also be used for the following layer-1 operating modes:
● Super Frame SF
● Extended Super Frame ESF
Board usage is subject to the following restrictions:
● Only one TST1 board allowed (primary multiplex access)
● For slot 7 or 9 only
Rather than connecting to a main distribution frame (MDF), the TST1 connects to a channel
service unit (CSU). The CSU supplies the required secondary protection.
Interfaces
50
To CO 1
to CUC/
X2 TST1 X1 CUCR
8
Figure 3-126 TST1 (for U.S. only) (S30810-Q2919-X/S30810-K2919-Z)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
Contact assignment
Table 3-160 TST1 (for U.S. only) - Contact Assignment
Contact X2 Contact X2
1 b-wire (ring), receive 5 a-wire (tip), transmit
2 a-wire (tip), receive 6 not connected
3 not connected 7 not connected
4 b-wire (ring), transmit 8 not connected
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.45 TS2 (Not for U.S.), TS2R (not for U.S.)
Introduction
The board contains a four-wire interface with S2M code for connection to the public telecommu-
nications network or private networks.
Up to thirty trunk calls can be conducted simultaneously via the S2M interface. The total trans-
mission speed including signaling and synchronization is 2048 Mbps.
Two trace files are available:
● Implemented up to and including V4.0:
– TS2 (Trunk Module S2M) S30810-Q2913-X100 (Figure 3-127) - for use in
HiPath 3550 (wall housing)
– TS2R (Trunk Module S2M Rack) S30810-K2913-Z100 (Figure 3-128) - for use in Hi-
● Implemented in V5.0 and later:
In HiPath 3000/5000 V5.0 and later, the B channels in the TS2 and TS2R boards
> are subject to license. Consequently, the two boards below have been assigned
a new hardware identification code. The new codes prevent the boards from be-
ing used in earlier versions. Functionality and layout of the boards have not
been changed.
– TS2 (Trunk Module S2M) S30810-Q2913-X300 (Figure 3-127) - for use in
– TS2R (Trunk Module S2M Rack) S30810-K2913-Z300 (Figure 3-128) - for use in Hi-
Board usage is subject to the following restrictions:
● Only one TS2/TS2R board allowed (primary multiplex access)
● For slot 7 or 9 only
To support country-specific CAS protocols, you can use the Euro-ISDN CAS gateway ECG.
The ECG cabinet is a protocol converter that converts the Euro-ISDN protocol into the Channel
Associated Signaling CAS protocol. Refer to the installation instructions, which are provided
with each ECG cabinet, for information on the connection and power supply.
For HiPath 3000 V1.0 and later, you can also use the new TMCAS board to support country-
specific CAS protocols.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
TS2 interfaces
S2M interface:
1 TS2 50
● Wieland termi- X2
nal (symm. line)
8 to CUC
X1
1
● MW8 (RJ48C)
jack (MW line) X5
2
Figure 3-127 TS2 (not for U.S.) - Interfaces (S30810-Q2913-X100, -X300)
TS2R interfaces
TS2R 50
to CUCR
S2M interface:
X1
1
● MW8 (RJ48C)
X5
jack (MW line)
2
Figure 3-128 TS2R (not for U.S.) - Interfaces (S30810-K2913-Z100, -Z300)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Network interfaces
The TS2 board is connected to the network transfer point (NT1) via the symmetrical line (120
ohms, four-wire twisted-pair cable) at X2 or via an MW line at X5.
Note: use the connection kits listed on Page 3-331 for NT connections in Spain and Portugal.
● Symmetrical line (120 ohms)
The maximum cable length (approx. 130 m) depends on the quality of the cable used and
its signal attenuation. Use shielded cables only to guarantee proper operation.
Connect the cable to the X2 using an 8-pin Wieland terminal (TS2 only).
Table 3-161 Contact Assignments for X2 Connector
Contact X2 (TS2 only)
1 –48 V (NT1 feeding), max. 15 W
2 0 V (NT1 feeding)
3 GND
4 Board ID for TMCAS
5 a-wire (T), transmit
6 b-wire (R), transmit
7 a-wire (T), receive
8 b-wire (R), receive
● RJ line (MW8 (RJ48C) jack)
The shielded 8-pin MW8 (RJ48C) jack X5 is provided for connecting MW lines. The maxi-
mum cable length (approx. 100 m) depends on the quality of the cable used and its signal
attenuation.
Table 3-162 Contact Assignments for the MW8 (RJ48C) jack X5
Pin X5 Pin X5
1 b-wire (R), receive 6 Free
2 a-wire (T), receive 7 Free
3 Free 8 Free
4 b-wire (R), transmit 11 GND
5 a-wire (T), transmit 12 GND
An additional line must be provided from pins 1 and 2 on the X2 connector to NT1 for NT1
feeding.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
S2M trunk connection
HiPath 3550, HiPath 3500 Public network
TS2/TS2R NT1
Figure 3-129 S2M Trunk Connection

Keep the cable from the NT to HiPath 3550 or HiPath 3500 as short as possible to ensure prop-
er operation.
Caution
7 There should be absolutely no ground connection between the HiPath 3550 wall
housing and the NT. Do not connect the shield of the connection cable you are using
either on the HiPath 3550 side or on the NT side.
If the HiPath 3550 system is separately grounded (such as with the 19-inch housing
of the HiPath 3500), you may make a connection between HiPath 3550 and NT.
NT1 power supply
● TS2 board
The NT1 supply voltage of –48 V can be tapped from the X2 connector (see Table 3-161).
There is a power limit of < 15 W for this voltage, which the system feeds over the CUC.
● TS2R board
The NT1 power supply must come from an S30122-X7321-X (S30122-X7321-X100 with
UPS operation) power supply unit.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
Cable set for NT connections (Spain and Portugal only)
Spain (and in certain cases Portugal)

Public
HiPath 3550, HiPath 3500 network
Cable 1 Interface
TS2/TS2R converter Cable 2 NT
Portugal
Public
HiPath 3550, HiPath 3500 network
Cable 1 Interface
TS2/TS2R converter Cable 2 Cable 3 NT
Figure 3-130 S2M - NT Connections for Spain and Portugal

Connection kit contents and part numbers:
● TS2/TS2R connection kit for Spain and Portugal: F50035-E2-X63
containing the following:
– Interface converter: S30122-X7357-X
– Cable 1 = Patch cable MW8 (RJ48C), 10 m: C39195-Z7208-A100
– Cable 2 (2 units) = coaxial adapter cable, 30 cm: S30267-Z354-A3
● TS2/TS2R upgrade kit for Portugal: L30252-U600-A190
containing the following:
– Cable 3 (2 units) = Mini-coaxial cable, 10 cm: S30267-Z353-A1
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards
3.3.46 4SLA (not for U.S.), 8SLA, 16SLA (Not for U.S.)
Introduction
The 4SLA, 8SLA, and 16SLA (Subscriber Line Analog) modules for analog T/R interfaces con-
nect HiPath 3550 and HiPath 3350 (wall housing) to conventional analog telephones and sup-
plementary equipment (such as, Group 3 fax machines and entrance telephone adapters).
Interfaces
1 50
T/R ports
1-4 X2
Stns. 1 to 4 8 X1
1 to CUP/CUC
4/8SLA
T/R ports
5-8 X3
Stns. 5 to 8 8 2
(not with
4SLA)
Figure 3-131 4SLA (not for U.S.), 8SLA - Interfaces (S30810-Q2923-X200, -X100)
Table 3-163 4SLA (not for U.S.), 8SLA Contact Assignments

Contact X2 (T/R ports 1 to 4) X3 (T/R ports 5 to 8)
1 a1 a5
2 b1 b5
3 a2 a6
4 b2 b6
5 a3 a7
6 b3 b7
7 a4 a8
8 b4 b8
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
1
T/R ports X2
1-4 8 50
Stns. 1 to 4
1
T/R ports
5-8 X3
8 X1 to CUP/
Stns. 5 to 8
16SLA CUC
1
T/R ports
9-12 X4 2
Stns. 9 to 12 8
1
T/R ports
13-16 X5
Stns. 13 to 16 8
Figure 3-132 16SLA (not for U.S.) - Interfaces (S30810-Q2923-X)
Table 3-164 16SLA (not for U.S.) - Contact Assignments
Contact X2 X3 X4 X5
(T/R ports 1 to (T/R ports 5 to (T/R ports 9 to (T/R ports 13-16)
4) 8) 12)
1 a1 a5 a9 a 13
2 b1 b5 b9 b 13
3 a2 a6 a1 a 14
4 b2 b6 b 10 b 14
5 a3 a7 a 11 a 15
6 b3 b7 b 11 b 15
7 a4 a8 a 12 a 16
8 b4 b8 b 12 b 16
The operating mode (short or long line with the appropriate flash times) can be set up for each
subscriber line interface with HiPath 3000/5000 Manager E (the menu settings: Set up station
–> Station –> Param –> Flags).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

40 Vdc
mum
3000”).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Peripheral boards
3.3.47 8SLAR
Introduction
The 8SLAR (Subscriber Line Analog Rack) board provides eight T/R interfaces for connecting
analog telephones and supplementary equipment (such as group 3 fax machines and TFE
adapters) in HiPath 3500 and HiPath 3300 (19-inch housing).
Interfaces
Port 1 11 50
T/R ports X1 to CUPR/

1–8 CUCR
X2
(4-pin RJ45
jacks) 2
Port 8 88
Figure 3-133 8SLAR Interfaces (S30810-K2925-Z)
Table 3-165 8SLAR Contact Assignments

RJ45 jack X2, Pin T/R ports 1-4 RJ45 jack X2, Pin T/R ports 5-8
1 14 a1 5 54 a5
15 b1 55 b5
2 24 a2 6 64 a6
25 b2 65 b6
3 34 a3 7 74 a7
35 b3 75 b7
4 44 a4 8 84 a8
45 b4 85 b8
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Peripheral boards

40 Vdc
mum
3000”).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4 Options
3.4.1 ALUM4
Introduction
In the event that HiPath 3550 or HiPath 3350 experience a voltage drop, voltage dip or unre-
coverable system errors, a trunk failure transfer (ALUM) is activated (MSI only).
The module implements a power failure transfer for four analog telephones. The only kind of
telephone that can be used is an analog telephone. The signaling method of the connected
telephones should be the same as that on the trunk line, otherwise signaling will not be possi-
ble.
When the system is deactivated or if an error occurs, the trunk lines are connected directly to
the telephones. When normal operation is resumed, the transfer represented in the figure be-
low takes place.
ALUM4 module function
X6 KX-X relay interface

9 System 16
8 1
From analog trunks Pins 1-8
To analog trunk board
X3
To analog stations
To central control or
X4
analog station board
Pins 9-16
Figure 3-134 ALUM4 - Function
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Interfaces
CB side
1
X1
from the CO X3 9 ... 16
8 ... 1
8 X6
1
ALUM module
to the X4
X2
telephone 8
Board side
Figure 3-135 ALUM4 - Interfaces (S30817-Q935-A)
The cable that is plugged in by default is split and is connected to the TLA and to the
> 4/8/16SLA board.
ALUM module contact assignments
Table 3-166 ALUM4 - Interface Assignments (not for U.S.)
Contact Connector X3 Connector X4 Connector X6

1 R1 from trunk 1a AE1 to Stn. 1a AT1 to TLA a
2 T1 from trunk 1b BE1 to Stn. 1b BT1 to TLA b
9 – – TA4 to SLA* a
10 – – TB4 to SLA* b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Table 3-166 ALUM4 - Interface Assignments (not for U.S.)

* = or to free analog port
Table 3-167 ALUM4 - Interface Assignments (for U.S. only)
Pin X3 X4 Y-Cable from X6 to Y-Cable from X6 to Ana-

(to MDF) (to MDF) TMGL4 log Ports1
Pin Assignment Pin Assignment
1 R from trunk R to station 1 1 T to TMGL4 port 1 9 T to analog port 4
1
2 T from trunk T to station 1 2 R to TMGL4 port 1 10 R to analog port 4
1
2
2
3
3
4
4
Note: Pinouts shown are at the board itself. The supplied main distribution frame cable (MDF
cable) reverses the signal order for X3 and X4 before the MDF.
1 To the analog station ports on the CBCC (recommended) or to four consecutive ports on an 8SLA board.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
ALUM module block diagram
Trunk
Connector
X3 HiPath 3550
HiPath 3350
ALUM
R1 Relay T1
Connector X6
K1-B K2-B
BT1 Trunk
AT1 board
TA1 Station
TB1 board
K1-C K2-C
AE1 Relay BE1
Connector
X4
Analog telephone
Figure 3-136 ALUM4 - Basic Structure
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.2 AMOM
Introduction
AMOM is an opto-electronic converter that can be used to connect fiber optic cables to the Sub-
D jacks on the front panel of the DIUN2 and DIU2U boards.
HiPath 3800
Optical fiber cable

S
U AMOM
DIUN2 B
D
or
S
U
DIU2U B
D
Figure 3-137 AMOM - Connection to DIUN2 and DIU2U
AMOM variants
AMOM variant Wave length Op.fiber Cable length Cable attenua- Maximum at-
cable (km) tion tenuation1
(dB/km) (dB)
S30807-K5480- 850/820 nm 50 µm 2,5 3 11,5
X100 multimode 62.5 µm 3 3,5 14,5
S30807-K5480- 1300 nm 50 µm and 6 1 10
X200 multimode 62.5 µm
S30807-K5480- 1300 nm 9 µm/125 8 0,5 8
X300 mono mode
1 Maximum optical attenuation in an AMOM to AMOM connection: a reserve of 4 dB attenuation must be included for ageing
and splicing.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Connector assignment
Table 3-168 AMOM - 15-Pin Sub-D Plug Assignment
Pin Signal Signal description Direction

4 LWLO0_FRONT Data output on the optical fiber in- Input
terface
V power supply
6 SCAN_IN0 Adapter test Output
7 SCAN_IN0 Adapter test Output
10 +5V +5-V power supply Input
11 LWLI0_FRONT Data input on the optical fiber inter- Output
face (front)
V power supply
14 +5V +5-V power supply Input
No other pins used.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.3 ANI4 (for selected countries only)
Introduction
The ANI4 (Automatic Number Identification) board is responsible for receiving station numbers
modulated using the CPFSK method, demodulating them, and forwarding them to the base
system HiPath 3550 and HiPath 3350. In V4.0 SMR-7 or later, the station name is analyzed in
addition to the call number and shown on the telephone display.
Each ANI4 can serve four trunks. It contains the external trunk board hardware interfaces
(TMGL4) as well as a trunk and options bus interface. The trunks are transferred directly on the
board between the trunk and the trunk board interfaces.
Interfaces on the ANI4 module
LEDs CB side
2/1
4/3 (green) (red) X1
6/5 X 3 *)
TMGL4
8/7
10/9
ANI4
1
Trunk X4
X2
8
Board side
*) Pins: Component side/solder side
Figure 3-138 ANI4 (for selected countries only) - Interfaces (S30807-Q6917-Axxx)

On the ANI4 board two LEDs are implemented that show the status of trunk channel 1.
After system startup the green LED is on and the red LED is off. This signals that the layer-1
firmware has started correctly.
If ANI4 is recognized properly by the system, the green LED is reset (after all system software
initialization), and the bottom line of the display on the Optiset E or optiPoint 500 phones ap-
pears. This means that the ANI4 has received system software activation for all four channels.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Table 3-169 ANI4 (for selected countries only) - LED Statuses for Trunk 1
LED Meaning Action

Green LED - Firmware Condition
Off No caller ID signals on the line. Call service provider and
ask if feature is available.
Line is not connected to trunk channel 1. Connect line to trunk chan-
nel 1.
The incoming signal is lower than –36 dBm (as de- Call service provider and
fined in Bellcore SR3004 for the lowest caller ID sig- ask if feature is available.
nal (space - signal)): the Mitel chip on ANI4 shows no If so, the signal that appears
reaction. on the customer side is too
low (not Bellcore-compliant).
This must be corrected by
the service provider.
The LED or the microcontroller is defective. Replace ANI4 board.
The system has not yet started. Start up system.
On The Mitel chip interprets the signal on the line as an –
(but FSK carrier signal. However, this could mean that
glowing there is noise or speech on the line, too.
weakly) The firmware is in the state of recognition.
On A valid caller ID signal (correct channel seizure/mark –
(for ap- - bit sequence + valid message byte) on the line is be-
prox. ing recognized at the moment. If a message is not
1 s) displayed on the Optiset E or optiPoint 500 tele-
phone, there may be too much noise on the line. In
other words, some bits in the signal have “tipped
over” into the other logical status. The firmware builds
the checksum for the received caller ID message byte
and compares this checksum with the one received.
Red LED - Checksum Status
On The received caller ID signal has a checksum error. If the red LED is on after ev-
The LED is reset after the next correct caller ID mes- ery call: the FSK signal is
sage is received. provided, but is not Bellcore-
compliant on the customer
side. This must be corrected
by the service provider.
Off Checksum is OK. –
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
ANI4 module contact assignments
Table 3-170 ANI4 (for selected countries only) - Contact Assignments

Component Side Solder Side
1 -- Not assigned a-wire (tip), trunk 1
2 b-wire (ring), trunk 1 -- b-wire (ring), trunk 1
3 -- a-wire (tip), trunk 1 a-wire (tip), trunk 2
9 -- a-wire (tip), trunk 4 –
10 GMZ -- –
GMZ= Call charging module assignment
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
ANI4 installation instructions

Follow the steps below to install ANI4 in the HiPath 3550 or HiPath 3350 system.
Caution
7 Remove the trunk slip-on connectors from the TMGL4 board before starting to work
on the system.
Be sure to reinstall the ANI4 and TMGL4 boards in their slots before reconnecting
the trunks.
1. Disconnect the trunks from theTMGL4 board (Figure 3-139: Figure 1).
2. Unplug the system from the power supply.
3. Install the ANI4 board in the system.
4. Connect the OPAL adapter cable to the ANI4 board.
5. Use the ribbon cable supplied with the board to connect ANI4 and TMGL4, making sure
that the colored markings (pin 1) at both ends of the cable are facing upwards (Figure 3-
139: Figure 2).
6. Connect the trunk slip-on connectors to the ANI4 (Figure 3-139: Figure 3).
7. Restart the system by reconnecting the power plug.
Fig. 1 Fig. 2 Fig. 3

Pin 1
Pin 1
Figure 3-139 ANI4 (for selected countries only) - Installation Steps
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.4 ANI4R (for selected countries only)
Introduction
The ANI4R (Automatic Number Identification Rack) board is responsible for receiving station
numbers modulated using the CPFSK method, demodulating them, and forwarding them to the
HiPath 3500 or HiPath 3300 base system. In V4.0 SMR-7 or later, the station name is analyzed
in addition to the call number and shown on the telephone display.
Each ANI4R module can serve four trunks. It contains the external trunk board hardware inter-
faces (TMGL4R) and the options bus interface.
If ANI4R is installed as option 1 or 2, TMGL4R board must be inserted in slot 4, 6 or

> 8 (slots 6 and 8 not available with HiPath 3300).
Interfaces
To OPALR, or previous option

1
X1
TMGL4R X3 (10-pin MW10 jack)
10
ANI4R
X2
Board side
Figure 3-140 ANI4R (for selected countries only) (S30807-Q6917-Z103)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Contact assignment
Table 3-171 ANI4R (for selected countries only) - Contact Assignment
X3 Pin Signal X3 Pin Signal

1 – 6 a-wire (tip), trunk 3
2 a-wire (tip), trunk 1 7 b-wire (ring), trunk 3
3 b-wire (ring), trunk 1 8 a-wire (tip), trunk 4
4 a-wire (tip), trunk 2 9 b-wire (ring), trunk 4
5 b-wire (ring), trunk 2 10 Call charging module assignment
(GMZ)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.5 Announcement and Music Modules
Caution
7 Place the central control board on a flat surface before inserting a subboard. Other-
wise you may damage the board.
Introduction
The HiPath 3000 systems use different modules or boards for playing announcements and mu-
sic on hold. For details on connecting these boards, refer to the manufacturer’s installation in-
structions.
The following HiPath Xpressions Compact boards support music on hold in V4.0
> SMR-7 or later and announcements in V5.0 or later:
● IVMNL, IVMN8 (HiPath 3800)
● IVMP8 (not for U.S.) and IVMP8R (not for U.S.) (HiPath 3350, HiPath 3300)
● IVMS8, IVMS8R (HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300)
For detailed information on HiPath Xpressions Compact, startup and administration,
see the manual for the product (see Section 1.6, “Information on the Intranet”: Elec-
tronic Documentation on SEN ESY Products).
Overview
Table 3-172 Announcement and Music Modules
Module/ Part number Notes

Board
EXM S30817-Q902- ● Used in HiPath 3550 and HiPath 3350 (wall housing),
B401 see Figure 3-141.
● Connected via cable to X4 connector on CBCC/CBCP.
EXMNA (for S30807-Q6923-X ● Implemented in HiPath 3550, HiPath 3350 (wall hous-
U.S. only) ing), see Section 3.4.7.
EXMR S30122-K7403-Z ● Implemented in HiPath 3550, HiPath 3350 (wall hous-
ing), and HiPath 3500, HiPath 3300 (19" housing).
● Module installed directly on CBCC/CBRC (X19 and
X20).
● Wall housing: Direct connection to external music
source (see Figure 3-142).
● 19" housing: Connected via cable to cinch jack on the
front panel (see Figure 3-143).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Table 3-172 Announcement and Music Modules
Module/ Part number Notes

Board
MPPI S30122-K7275-B ● Used in all HiPath 3000 systems
● Board installed directly on the central control board
(X19 and X20).
MPPI (not S30122-K5380- ● Used in HiPath 3550 and HiPath 3350 (wall housing).
for U.S.) X200 ● Connected via cable to X4 connector on CBCC/CBCP.
UAM (not for S30122-X7217-X ● Used in HiPath 3550 and HiPath 3350 (wall housing).
U.S.) ● Connected to OPAL and analog interface (for the an-
nouncement function)
UAMR (not S30122-X7402-Z ● Used in HiPath 3500 and HiPath 3300 (19-inch hous-
for U.S.) ing).
● Connected to OPALR and analog interface (for the an-
nouncement function).
Notes on displaying options

You can use HiPath 3000/5000 Manager E to display the presence of options. The presence
of MPPI or UAM (HiPath 3550 and HiPath 3350 only) is displayed as “Option 5”.
The ALUM4 module cannot be displayed.
Slot for EXM
Cable duct
Slot for
EXM module
Figure 3-141 EXM Slot for HiPath 3550 and HiPath 3350 Wall Housing
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Connection of EXMR
X1
X2
Direct connection EXMR
of the external music (component side)
source
Note: A cable binder has been provided in the cable duct for
suitable strain relief of the connecting cable.
Figure 3-142 EXMR connection to HiPath 3550 and HiPath 3350
Front panel
X1
of the system
X2
EXMR
Cinch jack (component side)
Cable C39195-Z7001-C79
Figure 3-143 EXMR Connection to HiPath 3500 and HiPath 3300
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.6 EVM
Introduction
The optional EVM (Entry Voice Mail) subboard enables the function of integrated voice mail in
HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300. The prerequisite for this is the use
of the S30810-Q2935-A301/-A401 (CBCC) and S30810-Q2935-Z301/-Z401 (CBRC) central
boards.
The board is plugged directly into the X32 connector on the central control boards CBCC (see
Section 3.2.1) or CBRC (see Section 3.2.2) using the connector strip X2.
Caution
7 The EVM subboard must not be plugged in or out when the system is energized.
Place the central control board on a flat surface before inserting the EVM subboard.
HiPath Entry Voice Mail has capacity to store up to two hours of recorded messages. You can
create up to 24 standard mailboxes and up to four of these can be configured as Auto Attendant
mailboxes (attendant mailboxes with automatic call acceptance, greeting with routing options,
day and night mode, speed dialing).
Information on administering HiPath Entry Voice Mail for HiPath 3000 can be found in the Hi-
Path 3000/5000 Manager E Help.
Caution
7 If using a different voicemail application (such as HiPath Xpressions Compact), the
EVM voice mail ports must be deactivated. To do this, set the ports to the "Standard"
station type and remove them from the active voicemail hunt group. Next set the
number of mailboxes for autoconfiguration to "0". This prevents the user making ac-
cidental changes to Call Management.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Interfaces
Spacing bolts
X2
26-pin socket strip
X1 (not used for HiPath 3000)
Figure 3-144 EVM (S30807-Q6945-X) - Interfaces
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.7 EXMNA (for U.S. only)
Introduction
The EXMNA (external music on hold) module provides a connection for external music on hold
in HiPath 3550 and HiPath 3350.
The EXMNA connects to the CBCC and CBCP board (connector X4) by means of a ribbon ca-
ble.
● Ribbon cable connected = External music
● Ribbon cable not connected = Internal music
Expert mode code 22 11 allows you to choose between music on, music off, ring tone, or music
on unscreened transfer. If the EXMNA module is connected, you must select Music on using
Manager T or HiPath 3000/5000 Manager E. The module is operational as soon as it is plugged
in.
Interfaces
1
Ribbon cable to X1
CB
10 EXMNA
To external music
source X2
Figure 3-145 EXMNA (for U.S. only) (S30807-Q6923-X)
Cable duct
Slot for EXMNA module
Figure 3-146 EXMNA (for U.S. only) - Slot for HiPath 3550 and HiPath 3350
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Contact assignment
Table 3-173 EXMNA (for U.S. only) - Contact Assignments

1 GND Input
2 Not assigned Input
3 Not assigned Not assigned
4 EXMCL Not assigned
5 EXMDIR
6 HRES
7 EXMD
8 EXMDET
9 +5 V
10 Not assigned
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.8 GEE12 (not for U.S.), GEE16 (not for U.S.), GEE50 (not for U.S.)
Introduction
Each of the modules listed below supports four call-metering receiving units for recording and
preprocessing call charge pulses in HiPath 3550 and HiPath 3350.
Table 3-174 GEE12/GEE16/GEE50 (not for U.S.) Modules
Module Frequency Remarks

GEE 12 12 kHz also for Silent Reversal
GEE 16 16 kHz
GEE 50 50 Hz
The call charge detection channel is looped in the trunk and then routed to the TLA
Interfaces
CB side
1 10
1
X1
to the TLA X3
X5
10
1 GEE module
X4
To CO
LS X2
8
Board side
Figure 3-147 GEE12, GEE16, GEE50 (not for U.S.) - Interfaces (S30817-Q951-Axxx)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Contact assignments
Table 3-175 GEE12, GEE16, GEE50 (not for U.S.) - Contact Assignments
Contact Connector X3 Connector Connector

X4 X5
1 a GND * CO 1 (AL1) 0V
2 b CO 1 (BN 1) CO 1 (BL1) 0V
3 a CO 1 (AN 1) CO 2 (AL2) RTS
4 b CO 2 (BN 2) CO 2 (BL2) CTS
5 a CO 2 (AN 2) CO 3 (AL3) RxD
6 b CO 3 (BN 3) CO 3 (BL3) TxD
7 a CO 3 (AN 3) CO 4 (AL4) 0V
8 b CO 4 (BN 4) CO 4 (BL4) +5V
9 a CO 4 (AN 4) – 0V
10 Call charging module as- – +5V
signment
* for GEE 50 in France; otherwise free
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.9 HOPE (for U.S. only)
Introduction
The HOPE (Hicom Office PhoneMail Entry) board provides Hicom Office PhoneMail Entry func-
tions.
The HOPE board does not identify itself to the system and is therefore not visible in
> the HiPath 3000/5000 Manager E card map. When expanding a system (such as
HiPath 3350 or HiPath 3550), ensure that a free slot is available.
Interfaces
LED status indicator

Software load/diagnostic button
Digital station connector
On/off switch
(Off—towards LED
On—towards slot)
PCMCIA slot
Card ejector
Figure 3-148 HOPE (for U.S. only) (S30122-Q7078-X; S30122-Q7079-X)
Board components
The following list describes the purpose of the components on the HOPE board:
● The LED status indicator signals the state of the Hicom Office PhoneMail system
● The software load/diagnostic button is for software loads (for example, loading a specific
language).
● The digital station connector connects the HOPE board to the corresponding digital ports,
using a modular cable
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
● The on/off switch turns the Office PhoneMail system on and off
● The PCMCIA slot is for Office PhoneMail software cards (for example, voice cards).
● The card ejector ejects the software cards from the PMCIA slot
Installation, servicing, and connectivity

For information on installing, connecting, and servicing the HOPE board, refer to the Hicom Of-
fice PhoneMail Entry Installation and System Administration Guide.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.10 OPAL and OPALR
Introduction
The adapter cable for connecting the central board to the first optional board comes in two ver-
sions:
● OPAL (Options Adapter Cable Long) C39195-A7001-B130 (Figure 3-149 - for use in
HiPath 3550 and HiPath 3350 (wall housing).
● OPALR (Options Adapter Cable Long Rack) C39195-A7001-B142 (Figure 3-150) - for use
in HiPath 3500 and HiPath 3300 (19-inch housing).
OPAL interfaces
Option board connection
Ribbon cable
folded and secured
CBCC/CBCP interface
Figure 3-149 OPAL (C39195-A7001-B130)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
OPALR interface
Option board connection
CBRC interface
Figure 3-150 OPALR (C39195-A7001-B142)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.11 PFT1 (not for U.S.), PFT4 (not for U.S.)
Introduction
In the event of a power failure or system error in HiPath 3800, analog trunks can be transferred
(ALUM) to designated analog telephones. These are:
● 1 analog trunk with a PFT1 (Power Failure Transfer) board
● 4 analog trunks with a PFT4 board
When using an analog telephone for outgoing calls, you may need to adapt its signaling method
to match the signaling method of the connected trunk.
ALUM using PFT1/PFT4
TRUNK
PFT a b
R
E TMB Trunk circuit
L
A TMA
Y
S SMA
Analog station board
SMB (optional)
SLA SLB
Analog telephone
Figure 3-151 ALUM Using PFT1/PFT4 (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Installation location of the PFT1 and PFT4 board (MDFU/MDFU-E)

Wire PFT1 or PFT4 into the MDFU or MDFU-E. The boards require -48 V. For the assignments
of both boards, see Figure 3-153.
2 x PFT1
or
1 x PFT4
System side Line network
Figure 3-152 Installation Location of PFT1 and PFT4 (MDFU/MDFU-E) (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
PFT1 and PFT4 board assignment
X1 X2 PFT4 X1
TMA 10 1 TMA 1 TMA
TMB TMB TMB
A A A
B B B
SMA SMA SMA
SMB SMB SMB
SLA SLA SLA
SLB SLB SLB
- 48
PFT
1 10 10
TMA 10 1 TMA
PFT1
TMB TMB
A A
B B
SMA SMA
SMB SMB TMA, TMB = Trunk circuit
SLA SLA A, B = a, b (Telephone company)
SLB SLB SMA, SMB = SLA board
- 48 SLA, SLB = Analog telephone
PFT
1 10
X3 X4
Figure 3-153 PFT1 (S30777-Q539-X) and PFT4 (S30777-Q540-X) Board Assignment
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.12 REALS
Introduction
The REALS (Relay and ALUM for SAPP) board is used in HiPath 3800 to provide the following
functions:
● Four individual, controllable relays are available for special connections, such as door
openers.
The switch contacts for all relays are floating and protected by surge protectors.
Electrical characteristics of the relays are as follows:
– Maximum current drain at – 48 V: 80 mA
– Operating voltage: + 5 V
– Contact current: max. 1.25 A
– Contact power: max. 30 W
● Trunk failure transfer (ALUM)
In the event of a power failure or a system restart or reload, an analog trunk is transferred
from the system to an analog telephone. If the power supply voltage returns after an inter-
ruption and a trunk call is in progress, activation of the trunk failure transfer relay is pre-
vented by optocoupler.
– Default = HiPath 3800 is in normal mode:
PFTALa/b (trunk) is connected to PFTASa/b (trunk module).
PFTTLa/b (terminal) is connected to PFTTSa/b (subscriber line module).
– Error = HiPath 3800 does not have any power
PFTTLa/b (terminal) is connected to PFTALa/b (trunk).
ALUM relay electrical data:
– Operating voltage: + 5 V
– Contact current: max. 1.25 A
– Contact power: max. 30 W
All of the functions are controlled by the CBSAP board.
Two –48-V lines fused using a PTC resistor are available for external applications. The voltage
is picked up via MDFU-E (Table 3-176: M48VF1 / 0V_F and M48VF2 / 0V_F). Each trunk has
a maximum load capacity of 300 mA.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
To the SIPAC 4SU connector X17
Signals are picked up via SIVAPAC con-

nector X116 on the backplane.
Removal tab
You can insert a screwdriver here to remove REALS from the shelf.
Figure 3-154 REALS (S30807-Q6629-X)
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Slot
Insert the REALS board into the slot marked 3 in the lower part of the shelf in the basic cabinet
and apply pressure until you hear a click (see Figure 4-22).
The slots for the power supply units and for the REALS board must be covered with an outer
panel before the system is started up. The outer panel is fixed onto the shelf with screws (see
Figure 3-155).
Figure 3-155 REALS Slots in the Basic Cabinet (With Outer Panel Mounted)

Table 3-176 shows the assignment of the SIVAPAC connector X116 on the backplane and the
assignment of the jumper strip in the MDFU-E.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Table 3-176 REALS - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire SIVAPAC Connec-
Pair REALS MDFU-E Notes
(tip) (ring) tor X116
wht/blu 20 M48VF1 1a – 48 V (max. 300 mA)
1
blu/wht 38 0V_F 1b
wht/ora 18 PFTTLb 2a ALUM: Subscriber line
2
ora/wht 17 PFTTLa 2b (telephone)
wht/grn 16 0V 3a
3
grn/wht 15 – 3b
wht/brn 14 0V_F 4a
4
brn/wht 13 M48VF2 4b – 48 V (max. 300 mA)
wht/grn 12 – 5a
5
grn/wht 11 0V 5b
Relay 1: Normally open
red/blu 10 AK1 6a
contact
6
blu/red 9 AK2 6b
contact
red/ora 8 AK3 7a
contact
7
ora/red 7 AK4 7b
contact
red/grn 6 0V 8a
8
grn/red 5 PFTASa 8b
ALUM: Trunk module
red/brn 4 PFTASb 9a
9
brn/red 3 PFTALa 9b
ALUM: Trunk
red/grn 2 PFTALb 10a
10
grn/red 1 – 10b
blk/blu 37 – 11a
11
blu/blk 36 0V 11b
blk/ora 35 – 12a
12
ora/blk 34 – 12b
blk/grn 32 RK3 13a
13
grn/blk 31 0V 13b
blk/brn 30 RK1 14a
14
brn/blk 29 RK2 14b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
Table 3-176 REALS - SIVAPAC Connector Assignment on the Backplane

a-wire b-wire SIVAPAC Connec-
Pair REALS MDFU-E Notes
(tip) (ring) tor X116
blk/grn 27 RK4 15a
15
grn/blk 26 0V 15b
yel/blu 24 PFTTSb 16a ALUM: Subscriber line
16
blu/yel 23 PFTTSa 16b module
yel/ora 58 – 17a
17
ora/yel 57 S5 17b
yel/grn 56 0V 18a
18
grn/yel 55 – 18b
yel/brn 54 – 19a
19
brn/yel 53 S3 19b
yel/grn 52 S4 20a
20
grn/yel 51 0V 20b
vio/blu 50 UK1 21a Relay 1: Switch contact
21
blu/vio 49 UK2 21b Relay 2: Switch contact
vio/ora 48 UK3 22a Relay 3: Switch contact
22
ora/vio 47 UK4 22b Relay 4: Switch contact
vio/grn 46 0V 23a
23
grn/vio 45 – 23b
vio/brn 44 – 24a
24
brn/vio 43 S6 24b
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.13 STBG4 (for France only)
Introduction
This current-limiting board is for connecting loop start trunks in France (HiPath 3550 and Hi-
Path 3350). It includes the current-limiting components and surge-protection elements required
by law.
No options bus lines are needed.
The slot X3 wiring is polarized.
The STBG4 channel is looped between TLA and the trunk.
CB side
1
TLA X3 X1
10 STBG4
MDF
1
X4
Trunk X2
8
Board side
Figure 3-156 STBG4 (for France only) - Interfaces (S30817-Q934-A)
Table 3-177 STBG4 (for France only) - Contact Assignment

1 Not used AL 1
2 BL 1 BL 1
3 AN 1 AL 2
4 BL 2 BL 2
5 AN 2 AL 3
6 BL 3 BL 3
7 AN 3 AL 4
8 BL 4 BL 4
9 AN 4 –
10 Not used –
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.14 STRB, STRBR
Introduction
This option comes in two versions:
● STRB (Control Relay Board) S30817-Q932-A (Figure 3-157) - for use in HiPath 3550 and
● STRBR (Control Relay Board Rack) S30817-K932-Z (Figure 3-158) - for use in HiPath
3500 and HiPath 3300 (19-inch housing)
The STRB or STRBR has four double-pin, double-throw relays as shown in Figure 3-159).
Actuators and sensors for monitoring, alerting, controlling and regulating can be connected to
the control relay board. Actuators are relays that can be energized from any station by means
of a code (such as a door opener). Sensors (such as thermostats or motion detectors) can de-
tect a change of status in the connected equipment and activate a feature or dial a station num-
ber stored in the system.
The board has a total of four outputs (in the form of two floating switch contacts each) and four
control inputs in the form of optocouplers for externally activating an electrically isolated nor-
mally open (NO) contact.
Caution
7 CDB data is stored on the board. When replacing the board, be sure to store the
CDB data elsewhere. If a used board is used, old data may still be present on the
board.
The "Reset options" procedure should only be used by factory technicians (Expert
Mode code 29-3-3). Using the procedure during operation returns all options to their
factory defaults, and they must be reset before they can accept data again from the
central board.
Example: You can route the +12-V signal for power failure alert to the control input of the opto-
coupler for connector X4 or X6. Route the signal through a normally open (NO) contact that is
electrically isolated from the external device, then program the alert type. For safety, the control
voltage for the optocoupler is electrically isolated from the system’s other partial voltages.
For the manual relay on/off function and door opener, you must enter the desired switching time
(expert mode code 26 2).
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
STRB interfaces
CBCC/CBCP side
1
8 1 8 1 X1
X3
X5 X6
MDF 8
1 STRB
X4
X2
8
Board side
Figure 3-157 STRB Interfaces (S30817-Q932-A)
STRBR interfaces
CBRC side
11
:
18 X1
21
8-pin RJ45 :
jacks 31
28 X3
: STRBR
38
41
: X2
48
Board side
Figure 3-158 STRBR Interfaces (S30817-Q932-Z)
Control relay connection values
Warning
7 The STRB or STRBR interface is an SELV (Safety Extra-Low Voltage Circuit) inter-
face, as defined by IEC 60950.
Do not connect any circuits whose voltages exceed the following limit values:
Maximum: 30 Vac (42 Vpeak) or 60 Vdc.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
STRB and STRBR board relay and sensor functions
STRB or STRBR
K1.21
K1.22
K1.23
Relay
K1.11
K1.12
K1.13
+12 V +12 VI
Short the wires to activate the

sensor.
OPTKP1
Sensor
To system
Figure 3-159 STRB and STRBR Board Relay and Sensor Functions
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
STRB contact assignment
Table 3-178 STRB Contact Assignments
Connector Contact Signal Name Function

1 K 4.21 Relay contact K4.2 (common)
2 K 4.22 Relay contact K4.2 (NO)
3 K 4.23 Relay contact K4.2 (NC)
X3 4 K 3.21 Relay contact K3.2 (common)
X4 4 K 1.23 Relay contact K1.2 (NC)
5 +12VI +12-V control voltage optocoupler
6 OPTKP 2 Control input optocoupler 2
X5 4 K 2.12 Relay contact K2.1 (NO)
X6 4 +12VI +12-V control voltage optocoupler
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
STRBR contact assignments
Table 3-179 STRBR Contact Assignments
X3, Pin Signal Name Function

11 ACT4-2M Relay contact K203 (common) 2
12 ACT4-2B Relay contact K203 (NO) 2
13 ACT4-2A Relay contact K203 (NC) 2
17 P12VI + 12-V optocoupler 4
18 SENSE4 Control input optocoupler 4
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.15 USB V.24 Adapter

The following adapters have been tested for connecting serial devices to the USB interface on
the service PC:
● Serial USB adapter F5U103 from Belkin Corporation (www.belkin.com)
● Serial USB adapter BF-810 from BAFO Technologies (www.bafo.com)
The delivery includes one USB cable, the adapter and a CD-ROM with drivers.
Notes:
● The drivers provided must be used.
● If a connection cannot be established between the PC and the system, close the Transfer
dialog and then reopen it.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.16 V24/1 (not for U.S.)
Introduction
In connection with the CBCC central board (up to and including S30810-Q2935-A301), the
V24/1 module can be used in HiPath 3550 and HiPath 3350. This provides a serial V.24 inter-
face for connecting PCs, printers or applications.
Interfaces
To CBCC/CBCP (X7) via ribbon cable
1 Component side
26 shown
X2
25-pin Sub-D jack
Figure 3-160 V24/1 (not for U.S.) (S30807-Q6916-X100)
Figure 3-161 HiPath 3550 and HiPath 3350 - V.24 Connections
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
Connector assignment
To CB TTL/RS-232 X2: Sub-D jack,

X7: Edge connector Level-converter and 25-pin
25-pin electrical isolation
TxD RxD
RxD TxD
RTS CTS
CTS RTS
DSR DTR
DTR DSR
Vcc
GND 0V
Figure 3-162 V.24 (RS-232) Connector Assignment, HiPath 3550 and HiPath 3350
Table 3-180 Pin Assignments of the V.24 Socket X2
Connector X2 Signal I/O

2 TxD O
3 RxD I
4 RTS O
5 CTS I
6 DSR I
20 DTR O
7 0V -
No other pins in connector X2 are used.
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm
Options
3.4.17 V.24 Adapter

The V.24 adapter is required as an adapter between the 25-pin connector on the cable
(C39195-Z7267-C13) and a 9-pin jack for connection to the V.24 interface on all HiPath 3000
V1.2 (or later) systems.
V.24 adapter assignment
Table 3-181 V.24 Adapter Assignment (C39334-Z7080-C2)
9-pin jack Signal 25-pin jack

Pin Pin
1 DCD 8
2 RxD 3
3 TxD 2
4 DTR 20
5 GND 7
6 DSR 6
7 RTS 4
8 CTS 5
9 RI 22
A31003-H3570-S100-6-7620, 2008-04-01
boards.fm

Options
3.4.18 V.24 Cable

The V.24 cable is used, for example, for connecting a service PC to the V.24 interface on all
HiPath 3000 systems (V1.2 or later).
V.24 cable assignment
9-pin jack 9-pin jack
DCD 1 1 DCD Data Carrier Detect

RxD 2 2 RxD Receive Data
TxD 3 3 TxD Transmit Data
DTR 4 4 DTR Data Terminal Ready
DSR 6 6 DSR Data Send Ready
RTS 7 7 RTS Request to Send
CTS 8 8 CTS Clear to Send
GND 5 5 GND Ground
RI 9 9 RI Ring Indicator
Shield
Figure 3-163 V.24 Cable Assignment (C30267-Z355-A25)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Nur für den internen Gebrauch Installing HiPath 3000
Overview
4 Installing HiPath 3000
4.1 Overview
Chapter contents
Topic
Installing HiPath 3800, page 4-2
● Installation Prerequisites, page 4-2
● Installation Procedure, page 4-3
● Installing HiPath 3800 (Standalone), page 4-4
● Installing HiPath 3800 (19-Inch Cabinet), page 4-20
● Installing Boards (Configuration Notes), page 4-31
● Connecting the Cable to the Backplane, page 4-51
● Using an External Main Distribution Frame or External Patch Panel, page 4-66
● Loading the System Software and Installing Subboards on the CBSAP, page 4-81
● Connecting Workpoint Clients, page 4-82
● Making Trunk and Networking Connections, page 4-82
● Performing a Visual Inspection, page 4-83
Installing HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300, page 4-85
● Installation Prerequisites, page 4-85
● Installation Procedure, page 4-86
● Installing HiPath 3550 and HiPath 3350, page 4-87
● Installing HiPath 3500 and HiPath 3300 (19-Inch Housing), page 4-110
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Installing HiPath 3000 Nur für den internen Gebrauch

Installing HiPath 3800
4.2 Installing HiPath 3800
4.2.1 Installation Prerequisites
Warning
7 Only authorized service personnel should install and start up the system.
Tools and resources needed

The following are needed for installing the HiPath 3800 system:
● Tools:
– Hex or open-end wrench, 8 mm, open-end wrench 13 mm
– Diagonal cutting pliers, telephone pliers, wire stripper, flat-nosed pliers
– Slotted screwdrivers, from 2 to 8 mm (1/4 to 5/16 in.)
– Phillips or cross-point screwdrivers, sizes 1 and 2
– TORX screwdriver
– Wire stripper (for example, from Krone)
– Board wrench (part no. C39300-A7194-B10)
– Electric drill, hammer
– Level, tape measure
– For U.S. only: Punch-down tool suitable for the block used (such as block 66)
● Resources:
– Manager T or HiPath 3000/5000 Manager E
– Digital multimeter for testing ground connections and partial voltages
– Telephone test set for analog interfaces
– Not for U.S.: ISDN tester (such as K3000 or Aurora)
– For U.S. only: AuroraDuet, AuroraExpert, AuroraRemote or similar, ISDN protocol analyz-
er
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.2 Installation Procedure
Table 4-1 HiPath 3800 - Installation Procedure
Step Installation Activity

Installing HiPath 3800 (Standalone) Installing HiPath 3800 (19-Inch Cabi-
net)
1. Selecting the Installation Site, page 4-4 Selecting the Installation Site, page 4-20
(usually predetermined) (generally determined by the existing 19-
inch cabinet)
2. Unpacking the Components, page 4-6 Unpacking the Components, page 4-23
3. Setting up the System Cabinets (from Mounting System Cabinets in the 19-Inch
page 4-7): Cabinet, page 4-24
Single Cabinet
Two cabinets (stacked)
Two cabinets (side by side)
4. Grounding the System, page 4-14 Grounding the System, page 4-27
Checking the Grounding, page 4-19 Checking the Grounding, page 4-30
5. Installing Boards (Configuration Notes), page 4-31
6. Connecting the Cable to the Backplane, page 4-51
7. If required: use an external main distribution frame or external patch panel,
from page 4-66:
● Main Distribution Frame MDFU-E
● Patch Panel S30807-K6143-X
● S0 Patch Panel C39104-Z7001-B3
8. Loading the System Software and Installing Subboards on the CBSAP, page 4-81
9. Connecting Workpoint Clients, page 4-82
10. Making Trunk and Networking Connections, page 4-82
11. Performing a Visual Inspection, page 4-83
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.3 Installing HiPath 3800 (Standalone)

This section contains information on how to install the HiPath 3800 communication system.
This chapter describes the standard installation procedures for the basic system. Refer to
Chapter 9 for information about supplementary equipment or expansions.
4.2.3.1 Selecting the Installation Site
Selecting a site
The customer usually has a preferred installation site in mind.
Make sure that the customer’s site meets the following guidelines:
● To guarantee sufficient system ventilation, allow a minimum of 50 mm clearance between
the base of the cabinet and the ground and between stacked cabinets.
● When cabinets are stacked, the basic cabinet must always be at the bottom of the stack.
● Allow a minimum clearance of 10 cm both at the rear and the front of the cabinets for main-
taining boards and for wiring.
● Do not expose the systems to direct sources of heat (for example sunlight and heaters).
● Do not expose the systems to extremely dusty environments.
● Avoid contact with chemicals.
● Take every precaution to prevent the formation of condensation on the system during op-
eration. Systems covered with condensation must be dried before being used.
● Observe the environmental conditions specified in Section 2.12.
For U.S. Only:
● Install secondary-protection equipment.
● Avoid standard carpeting, as it tends to produce electrostatic charges.
● Ensure the availability of a power source that meets the requirements described in
Section 4.2.3.1.1.
● Ensure that a distance of at least 40 in. (101.6 cm) is left between
Siemens Enterprise Communications GmbH & Co. KG equipment and other electrical
equipment. The National Electrical Code (NEC) requires 36 in. (91.44 cm) of clearance in
front of electrical equipment and 40 in. (101.6 cm) of clearance from other electrical service
equipment.
Information on the design of the HiPath 3800 can be found in Section 2.2.2.1.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.3.1.1 For U.S. only: AC outlet

An AC connection is required for each cabinet. The AC connection must fulfill the requirements
specified in Table 4-2.
Table 4-2 Electrical Connection Values (USA only)
Nominal Nominal voltage range Nominal Frequency Wall Outlet Configura-

voltage Range tions
from to from to
120 V AC/ 110 V AC 130 V AC 47 Hz 63 Hz NEMA 5-15, 2-pin, 3-
60 Hz wire, earth
WARNING
7 Never connect a HiPath 3800 system or a combination of HiPath 3800 systems di-
rectly to a wall socket. Use a UL-listed or CSA-certified surge protector for every two
cabinets.
AC Power Outlet Requirements

● A UL-listed or CSA-certified surge protector must be connected between the socket and
the system. Two cabinets can be connected to each surge protector. Never connect a Hi-
Path 3800 system or a combination of systems directly to a wall socket.
● The power source may not be more than 2.4 m (8 ft.) from the system.
● The power source must provide 120 V AC (single-phase, fused) power at 50-60 Hz and
20 A.
● A warning should be attached to the circuit breaker to prevent accidental removal of power.
● An independent electric circuit with an isolated ground conductor should be used.
The system must be properly grounded before startup (see description in Section 4.2.3.4).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.3.2 Unpacking the Components
Procedure
Step Activity
1. Compare the components with the packing slip or customer receipt to make sure
that they are correct and complete.
2. Determine whether any damage has occurred during transport and report it to the
proper departments.
3. Dispose of the packing materials properly.
Caution
7 Only use tools and equipment that are in perfect condition. Do not use equipment
with visible damage.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.3.3 Setting up the System Cabinets
Introduction
The cabinets are not supplied with pre-installed boards. For information on board installation,
please see Section 4.2.5, “Installing Boards (Configuration Notes)”.
If it has been agreed to provide connector panels for connecting peripherals, these are included
in the delivery. For information on the installation procedure, please see Section 4.2.5.4,
“Mounting Connector Panels (if required)”.
The front plastic cover (for board servicing) and the rear plastic cover (for cable servicing) are
not attached to the system cabinets. Both covers are supplied in separate packages.
Danger
7 Be sure to connect the main protective earthing terminal on all system cabinets to
the grounding point of the electrical building installation before starting the system
and before connecting up the peripherals (for example, potential equalization bus).
The system may only be started (connected to the power supply) if all system cabi-
nets are sealed at the rear with the connection and filler panels provided.
4.2.3.3.1 Overview
System configurations
The following setup options are possible for system cabinets:
● Single cabinet
● Two cabinets (stacked)
● Two cabinets (side by side)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.3.3.2 Setting Up a Single Cabinet
Caution
7 To guarantee sufficient ventilation for the system cabinet, allow a minimum clear-
ance of 50 mm between the base of the cabinet and the ground.
Procedure
Step Activity
1. Place the system cabinet in the installation site and make sure that it is level and
stable.
2. Check that the space between the base of the cabinet and the ground is at least
50 mm.
3. If necessary, set up the basic cabinet in the following way:
● Unscrew lock nut (Figure 4-1, A) on one of the cabinet feet using an open-end
wrench (wrench size = 13 mm).
● Adjust the height of the cabinet foot by turning the screw nut (Figure 4-1, B)
so that the cabinet is steady and the minimum clearance is observed.
● Fix the cabinet foot in position by tightening the lock nut (Figure 4-1, A).
Basic cabinet setup
A
≥ 50 mm
B
Figure 4-1 HiPath 3800 - Setting Up the Basic Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.3.3.3 Stacking Two Cabinets
Caution
7 To guarantee sufficient ventilation for the system cabinets, comply with the following
requirements:
● The basic cabinet must be set up as the bottom cabinet.
● Allow a minimum of 50 mm clearance between the base of the cabinet and the
floor, and between basic and expansion cabinets.
Procedure
Step Activity
stable.
2. Check that the space between the base of the basic cabinet and the ground is at
least 50 mm.
4. Place the expansion cabinet on top of the basic cabinet.
The cabinet feet have indents. When placing the expansion cabinet on top of the
basic cabinet, ensure that these indents are sitting precisely on top of the screw
heads in the four corners of the basic cabinet (Figure 4-2).
least 50 mm.
6. If necessary, set up the expansion cabinet as described in Step 3.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Positioning the cabinet feet
Figure 4-2 HiPath 3800 - Positioning the Cabinet Feet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Installing a stacked two-cabinet system
≥ 50 mm
≥ 50 mm
Figure 4-3 HiPath 3800 - Installing a Stacked Two-Cabinet System (Rear View)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.3.3.4 Setting Up a Two-Cabinet System Side by Side
Caution
7 To guarantee sufficient ventilation in the system cabinets, allow a minimum clear-
ance of 50 mm between the base of the cabinets and the ground.
Procedure
Step Activity
stable.
least 50 mm.
4. Place the expansion cabinet beside the basic cabinet.
Note: The cabinets can be placed directly beside one another.
5. Check that the space between the base of the expansion cabinet and the ground
is at least 50 mm.
6. If necessary, set up the expansion cabinet as described in Step 3 ensuring that
both cabinets are at exactly the same level.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Installing a Two-Cabinet System Side by Side
≥ 50 mm
Figure 4-4 HiPath 3800 - Installing a Two-Cabinet System Side by Side (Rear View)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.3.4 Grounding the System

Ground the system as described.
4.2.3.4.1 Not for U.S.: Grounding the System
Grounding: Grounding options

Implementation guidelines in accordance with IEC 60364 and IEC 60950-1 must be adhered
to during installation.
Danger
7 Each HiPath 3800 system cabinet and all external main distribution frames (for ex-
ample, MDFU-E) must be grounded as shown in Figure 4-5 by a separate ground
conductor (minimum cross-section = 2.5 mm2). Make sure that the ground conductor
is securely installed and strain-relieved.
If external factors can impact on the ground conductor and if protected installation is
not possible, the ground conductor must have a minimum cross-section of 4 mm2.
Failure to follow these instructions can result in electrical shock.
The illustrations starting with Figure 4-6 show different grounding options.
Danger
7 If your personnel are not qualified to work on the low-voltage network (230 Vac), you
must hire a licensed electrician to ground the system separately using option 1b
(Figure 4-7). The Section 1.3, “Electrical Environment” is to be adhered to.
Note on possible ground loops
To avoid ground loops from remotely operated devices (V.24 system peripherals),
> the devices should be connected to the same low-voltage network (sub-distribution
board) if possible.
If the building floor plan does not permit this, you may need a line driver to isolate
the external devices in the event of a malfunction.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Grounding the system(s) and a possible main distribution frame
HiPath 3800, EC (if present)
Attach to the grill us-

ing cable ties to next main distribution frame
(if present)
e. g., MDFU-E
Main distribution frame

(if present)
HiPath 3800, BC
Any color, except for green or

yellow to avoid confusion
green/yellow Min. cross-section ≥ 2.5 mm2
Min. cross-section ≥ 2.5 mm2
Example Potential equalization bus

but not:
- central heating system
- drain channels
- ground conductor for antenna system
Figure 4-5 HiPath 3800 - Grounding the System Cabinets and Main Distribution Frame
(nor for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Grounding option 1a
HiPath 3800
Main grounding terminal
green/yellow
Figure 4-6 HiPath 3800 - Grounding Option 1a (not for USA)
Grounding option 1b
L1 N PE
Grounding outlets
230 V ~
HiPath 3800
Example Connector
socket Main grounding
terminal
green/yellow
Figure 4-7 HiPath 3800 - Grounding Option 1b (not for USA)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.3.4.2 For U.S. Only: Grounding the System

A connecting cable is used for grounding the system cabinets. The system must also be
grounded by a separate ground conductor. Choose a ground connection with less than 2 ohms
of resistance, such as:
● Master ground busbar
● Ground field
● Copper ground rod
Run a separate earth ground conductor from the earth ground to the cabinet frame ground (lo-
cated in the lower right corner of the backplane). The minimum cross-section required is
12 AWG.
Figure 4-8 shows the safety conductor connectors for the basic cabinet. An expansion cabinet
requires a separate earth ground.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Fuse box
HiPath 3800 Connection cable facility
with plug AC outlet 20 A
120 VAC, 60 Hz
Neutral ground
Main grounding ter-

minal
Recommended: 12 AWG solid or stranded copper wire con-

ductor not exceeding 126 feet in length; blank or green/yel-
low.
Grounding point (example: Master

ground busbar) Located in the electrical service
panel providing power to the Hi-
Path 3800 system.
Notes: Single-point ground (SPG) configuration shown.
Figure 4-8 HiPath 3800 - Earth ground connection (for U.S. only)
DANGER
7 This wire installation must be completed by a qualified electrician and must comply
with the national and local electrical codes. The Section 1.3, “Electrical Environ-
ment” is to be adhered to.
Grounding the Main Distribution Frame

Mount and ground the MDF in accordance with the manufacturer’s instructions.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.3.5 Checking the Grounding
Procedure
Perform the tests in the table below to ensure that the system is properly grounded before star-
tup.
Step Activity Target

1. Check the ohmic resistance of the ground connection to < 10 ohms
the system:
Perform measurement between the PE (protective
earth) on a socket in the internal installation (at the sys-
tem’s installation site) and HiPath 3800.
Prerequisites:
● HiPath 3800 is not yet connected to the low-voltage
network via the power cable.
● The system’s separate grounding is connected.
2. Check the ohmic resistance between the individual sys- < 1 ohm
tem parts (basic cabinet, expansion cabinet, main distri-
bution frame).
Prerequisite:
HiPath 3800 is not yet connected to the low-voltage net-
work via the power cable.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.4 Installing HiPath 3800 (19-Inch Cabinet)

This section contains information on how to install the HiPath 3800 communication system in
a 19-inch cabinet. This chapter describes the standard installation procedures for the basic sys-
tem. Refer to Chapter 9 for information about supplementary equipment or expansions.

The installation site is generally determined by the 19-inch cabinet already installed.
The following specifications must be observed when selecting a location:
● The 19-inch cabinets provided for installing the HiPath 3800 components must have the
following characteristics:
– Components installed in the 19-inch cabinet must be accessible from both the front
and the rear.
– It should be possible to install 19-inch components both at the front and at the rear
( four vertical bars).
– It is recommended that the width of the cabinet measure 700 to 800 mm; the depth at
least 600 mm. Deeper cabinets (800 - 900 mm) make installation, cable servicing, and
the installation of additional components in the rear of the cabinet much easier.
– The support brackets required for installing the system cabinets must have a minimum
ultimate load of 40 kg. The support brackets must be purchased from the relevant 19-
inch cabinet supplier.
– The system cabinets must be fixed to the cabinet bars using the angle brackets includ-
ed in the delivery.
● One height unit (one height unit is approx. 1.7” = 43 mm) must be kept clear above the cab-
inet to accommodate the gray plastic cover (Figure 4-9) attached to the top of the system
cabinets. Never remove this plastic cover.
● The following minimum clearance must be provided in order to ensure adequate ventilation
of the system cabinets in the 19-inch cabinet (see Figure 4-10):
– three height units between two stacked system cabinets.
– one height unit above one system cabinet if a patch panel is being installed, for exam-
ple.
● To guarantee sufficient heat dissipation, the basic cabinet must be mounted at the lowest
position in a 19-inch cabinet. In a 19-inch cabinet with active (heat-emitting) components
already installed, the lowest position must be cleared for installation of the basic cabinet.
If inactive components (e.g. patch panel) are involved, the basic cabinet can also be in-
stalled above them.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Figure 4-9 HiPath 3800 - System Cabinet with Plastic Cover

● Do not expose the 19-inch cabinet to direct sources of heat (such as sunlight and heaters.).
● Do not expose the 19-inch cabinet to extremely dusty environments.
Information on the design of the HiPath 3800 can be found in Section 2.2.2.1.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Examples for installation in a 19-inch cabinet
Caution
7 The height units represented in yellow in Figure 4-10 must be kept clear to ensure
adequate ventilation of the system cabinets.
Examples of a 19-inch cabinet height of 1.92 m with 37 height units
Patch Panel
HiPath 3800
Expansion
cabinet
Patch Panel

Basic cabinet Basic cabinet
Figure 4-10 HiPath 3800 - Installation Examples in the 19-Inch Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

An AC connection is required for each cabinet. The AC connection must fulfill the requirements
specified in Table 4-3.
Table 4-3 Electrical Connection Values (USA only)

voltage Range tions
from to from to
60 Hz wire, earth
The system must be properly grounded before startup (see description in Section 4.2.4.4).
Procedure
Step Activity
proper departments.
Caution
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.4.3 Mounting System Cabinets in the 19-Inch Cabinet
Introduction
The cabinets are not supplied with pre-installed boards. For information on board installation,
please see Section 4.2.5, “Installing Boards (Configuration Notes)”.
If it has been agreed to provide connector panels for connecting peripherals, these are included
in the delivery. For information on the installation procedure, please see Section 4.2.5.4,
“Mounting Connector Panels (if required)”.
Danger
the grounding point of the electrical building installation before starting the system
and before connecting up the peripherals (for example, potential equalization bus).
4.2.4.3.1 Mounting a System Cabinet using Support and Angle Brackets

If a two-cabinet system is to be installed in a 19-inch cabinet, each system cabinet should be
installed separately.
The following components are required to install a system cabinet:
● Two cabinet-specific support brackets with an ultimate load > 40 kg, which must be provid-
ed by the 19-inch cabinet supplier.
● Two angle brackets (order no. C39165-A7075-D1), which are supplied with the system
cabinet.
Caution
7 To guarantee sufficient ventilation for the system cabinets, comply with the following
requirements:
● The basic cabinet may only be mounted at the lowest position in a 19-inch cab-
inet. In a 19-inch cabinet with active (heat-emitting) components already in-
stalled, the lowest position must be cleared for installation of the basic cabinet.
If inactive components (e.g. patch panel) are involved, the basic cabinet can
also be installed above them.
● A minimum clearance of three height units must be maintained between two
stacked system cabinets. A minimum clearance of one free height unit above a
system cabinet is sufficient if a patch panel is to be installed, for example.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Procedure
Warning
7 Never attempt to lift a system cabinet into the 19-inch cabinet without assistance.
Step Activity
1. Remove all four cabinet feet from the system cabinet.
To do this, unscrew the lock nuts (Figure 4-11, A) on the cabinet feet using an
open-end wrench (wrench size = 13 mm). Unscrew cabinet feet completely.
2. Attach the two angle brackets (A in Figure 4-12) to the sides of the system cabinet
using the screws that have been supplied (four per bracket).
3. Attach a right-handed and a left-handed support bracket (B in Figure 4-12) in the
19-inch cabinet using the screws provided.
Note: the use of cabinet floors is not permitted to prevent overheating.
4. Lift the system cabinet into the 19-inch cabinet and sit the cabinet on the two sup-
port brackets (B in Figure 4-12). Slide the cabinet into the 19-inch cabinet until the
front edge of the system cabinet is flush with the front of the 19-inch frame.
5. Secure the system cabinet using the two angle brackets (A, in Figure 4-12) on the
frame of the 19-inch cabinet using the screws provided.
Please note that a minimum clearance of three height units must be observed be-
tween two stacked system cabinets. A minimum clearance of one free height unit
above a system cabinet is sufficient if a patch panel is to be installed, for example.
6. Repeat steps 1 to 5 if you want to install an expansion cabinet.
Figure 4-11 HiPath 3800 - Removing Cabinet Feet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Installation in the 19-inch cabinet
Figure 4-12 HiPath 3800 - Installing System Cabinets in 19-Inch Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Ground the system as described.
Grounding: Inspection and Implementation

Preliminary Inspection of the 19-Inch Cabinet:

Is the 19-inch cabinet grounded NO The 19-inch cabinet must be grounded by a sepa-
by a separate ground conduc- rate ground conductor (green/yellow).
tor (green/yellow)? Danger
If your personnel are not qualified to work on the
low-voltage network (230 Vac), you must hire a li-
censed electrician to install the ground. The
Section 1.3, “Electrical Environment” is to be ad-
hered to.
YES
Does the 19-inch cabinet have NO A potential equalization bus must be installed in
a potential equalization bus the 19-inch cabinet and connected to the ground
at which the HiPath 3800 can conductor.
be grounded as shown in Danger
Figure 4-13 ? If your personnel are not qualified to work on the
hered to.
YES
If you answer “Yes” to both questions, the system (system cabinets, patch panels) may be
grounded as described below.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Danger
7 Each HiPath 3800 system cabinet and any patch panel (S30807-K6143-X) that may
be installed must be grounded as shown in Figure 4-13 by a separate ground con-
ductor (minimum cross-section = 2.5 mm2). Make sure that the ground conductor is
securely installed and strain-relieved.
Please note:
The 19-inch cabinet’s potential equalization bus may only be used if it is grounded
by a separate ground conductor.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Grounding the system cabinets and possible patch panels
To other patch panels S30807-K6143-X (if

present)
(A ground conductor is not required for the S0
patch panel S30807-K6143-X.)
HiPath 3800, EC (if present)
Attach to the grill using Patch Panel

cable ties
(if present)
for example, Patch Panel

S30807-K6143-X
HiPath 3800, BC
Any color, except for green or

yellow to avoid confusion
green/yellow Min. cross-section ≥ 2.5 mm2
Min. cross-section ≥ 2.5 mm2
Potential equalization bus,

in 19 cabinet for example
Figure 4-13 HiPath 3800- Grounding the Systems and Patch Panels in a 19-Inch Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Note on possible ground loops
To avoid ground loops from remotely operated devices (V.24 system peripherals),
> the devices should be connected to the same low-voltage network (sub-distribution
board) if possible.
If the building floor plan does not permit this, you may need a line driver to isolate
the external devices in the event of a malfunction.
4.2.4.5 Checking the Grounding
Procedure
Perform the tests in the table below to ensure that the system is properly grounded before star-
tup.
Step Activity Target

1. Check the ohmic resistance of the ground connection to < 10 ohms
the 19-inch cabinet:
Perform measurement between the PE (protective
earth) on a socket in the internal installation (at the sys-
tem’s installation site) and HiPath 3800.
Prerequisites:
● No device in the 19-inch cabinet is connected to the
low-voltage network via the power cable.
● The system’s separate grounding (basic cabinet,
expansion cabinet, patch panel) and the grounding
of the 19-inch cabinet are connected.
2. Check the ohmic resistance between the individual sys- < 1 ohm
tem parts (basic cabinet, expansion cabinet, patch pan-
el).
Prerequisite:
HiPath 3800 is not yet connected to the low-voltage net-
work via the power cable.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.5 Installing Boards (Configuration Notes)
Caution
7 Always wear an antistatic wristband when working on the system (especially when
handling boards).
Caution
7 ● To ensure that the system operates without blocking, you must follow the in-
structions in Section 4.2.5.7 concerning PCM highway distribution.
● In a HiPath 3800 19-inch cabinet configuration, the IVMNL board may only be
installed in the basic cabinet to avoid overheating.
● To avoid inactive IVM channels caused by slow IVM board startup, the recom-
mendations on page 3-99 must be followed.
4.2.5.1 System factory default

According to the sales order, a distinction is made between the following delivery states:
● Pre-configured systems
– The system cabinet(s) is/are supplied with customer-specific boards.
– The current system software (without customer data) is installed.
– The system has passed the startup test.
● Unconfigured systems
The system cabinet(s) is/are not supplied with pre-installed boards. Install the boards as
described in the following information.
4.2.5.2 Board Slots in the Basic and Expansion Cabinet

There are nine slots available in the basic cabinet BC (slots 1 to 5 and slots 7 to 10) and thirteen
in the expansion cabinet EC (slots 1 to 6 and slots 8 to 14) for peripheral boards.
The central control board CBSAP has a fixed slot (slot 6, only in the basic cabinet BC).
Depending on your requirements, up to three LUNA2 power supply units can be used in the
basic cabinet BC and up to four in the expansion cabinet EC.
In V6.0 or later, the cPCI box CSAPE can be used in the basic cabinet.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Figure 4-14 HiPath 3800 - Board Slots in the Basic Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Not used
Figure 4-15 HiPath 3800 - Board Slots in the Expansion Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.5.3 Inserting or Removing Boards
Caution
handling boards).
Observe the measures for protecting electrostatically sensitive devices (see page 1-
9).
Introduction
Peripheral boards can be inserted and removed while the power is connected. Always use the
board wrench provided for removing and inserting boards.
See Section 9.2.1 for information on upgrading peripheral boards.
Procedure for inserting and removing the boards
If Then
Board is to Insert the tip of the board wrench marked “Pull” into the top opening on the front
be recover of the board to be removed.
moved. Lever the board out of the shelf by pushing the board wrench upwards (Figure 4-
16, left).
Then you can pull the module out of the system cabinet over the guide rails.
Board is to Using its guide rails slide the board into the system cabinet until it stops.
be added. Insert the tip of the board wrench marked “Plug In” into the bottom opening in the
front cover of the board.
Lever the board into the shelf of the cabinet by pushing the board wrench up-
wards (Figure 4-16, right).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Removing a board Inserting a board
Figure 4-16 HiPath 3800 - Removing/Inserting the Board Using the Board Wrench
Installing shielding covers

In order to guarantee adequate shielding, a shielding cover (C39165-A7075-B15) must be in-
stalled for boards with no connection options in the front panel. To do this, insert the two bottom
pins on the shielding cover into the openings provided for this purpose on the slide-in shelf.
Then push the shielding cover in the direction of the board until it locks into position (refer to
Figure 4-17).
Empty board slots must also be covered with shielding covers.
Figure 4-17 Installing the Board Shielding Cover
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Boards that can be connected from the front have a specially shielded front cover. An additional
cover is not required.
Special board attachments

● CSAPE
Insert the cPXI box CSAPE into the relevant slot of the basic cabinet and apply pressure
until you hear a click.
The slot must be covered with a panel before the system is started up. The panel is fixed
onto the shelf with four screws (see Figure 4-18).
Fixing screws
Fixing screws
Figure 4-18 HiPath 3800 - cPCI Box CSAPE in the Basic Cabinet with Panel Mounted
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
● DBSAP
The DBSAP board is plugged into four socket contacts on the backplane of the expansion
cabinet and fixed with screws.
● LUNA2
Depending on the system configuration up to three LUNA2 modules can be used in the ba-
sic cabinet and up to four LUNA2 modules can be used in the expansion cabinet. For in-
formation on how to calculate the number of LUNA2 modules required, see the LUNA2
board description.
Push the LUNA2 power supply unit into the slots provided in the lower part of the system
cabinet shelf until you hear a click.
Removal tab
You can use a screw-
driver here to remove
the LUNA2 from the
shelf.
Figure 4-19 HiPath 3800 - Installing the LUNA2 Power Supply Unit
The slots for the power supply units must be covered with an outer panel before the system
is started up. The outer panel is fixed onto the shelf with screws (see Figure 4-20 and
Figure 4-21).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Fixing screws
Figure 4-20 HiPath 3800 - Slots for LUNA2 and REALS in the Basic Cabinet (With Out-
er Panel Mounted)
Fixing screws
Figure 4-21 HiPath 3800 - Slots for LUNA2 in the Expansion Cabinet (With Outer Pan-
el Mounted)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
● REALS
Insert the REALS board into the slot marked 3 in the lower part of the shelf in the basic
cabinet and apply pressure until you hear a click.
Figure 4-22 HiPath 3800 - Installing the REALS Board

The slots for the power supply units and for the REALS board must be covered with an out-
er panel before the system is started up. The outer panel is fixed onto the shelf with screws
(see Figure 4-20).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.5.4 Mounting Connector Panels (if required)

The HiPath 3800 has various connection options for connecting the peripherals. If you intend
to use connector panels, mount the panels supplied as follows:
If Then
Connector panels Slot with Attach a connector panel with 8 RJ45 jacks (S30807-
with RJ45 jacks STMD3 Q6624-X) to the SIVAPAC connector on the back-
(see plane.
Section 4.2.6.5) Slot with Attach a connector panel with 24 RJ45 jacks (S30807-
SLCN Q6622-X) to the SIVAPAC connector on the back-
SLMA plane.
SLMA21
SLMA8
SLMO2
SLMO8
TM2LP
TMC161
TMDID2
different or no as- Use filler panels to cover the backplane sections of
signment other boards and empty board slots.
For U.S. only: Slot with Attach a connector panel with CHAMP jacks (S30807-
Connector panels SLMA Q6626-X) to the SIVAPAC connector on the back-
with CHAMP jack SLMA21 plane.
(see SLMA8
Section 4.2.6.6) SLMO2
SLMO8
STMD3
TM2LP
TMC161
TMDID2
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
If Then
Connector panels Slot with Plug a connector panel with SIPAC 1 SU connectors
with SIPAC 1 SU SLCN (S30807-Q6631-X) into the SIVAPAC connector on
connectors SLMA the backplane.
(see SLMA21
Section 4.2.6.7) SLMA8
SLMO2
SLMO8
STMD3
TM2LP
TMC161
TMDID2
2 for U.S. only
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.5.5 Installing the SIVAPAC-SIPAC Board Adapter

The peripheral board slots on the HiPath 3800 are fitted with SIPAC 9 SU connectors. The
TMEW2 and TMDID (for U.S. only) boards have SIVAPAC connector strips and as a result,
SIVAPAC-SIPAC board adapters have to be installed in order to use them in HiPath 3800.
The SIVAPAC-SIPAC board adapter consists of three individual parts (refer to Figure 4-23):
● two adapter modules
● one startup module
Adapter modules
Startup module
Component
side
board
Figure 4-23 SIVAPAC-SIPAC Board Adapter
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Procedure: Installing the SIVAPAC-SIPAC Board Adapter
Step Activity
1. Rotate the board so that the backplane connector is pointing towards you.
2. Carefully pull the locking hooks (Figure 4-24, A) on an adapter module apart.
3. Align the adapter module on the connector strip (Figure 4-24, B) of the board. The
outside edges of the adapter module must match the outside edges of the connector
strip.
4. Make sure that the outermost row of pins on the adapter module and the outermost
row of jacks on the connector strip are aligned flush with one another and press the
adapter module fully into the connector strip.
5. Close the locking hooks.
6. Repeat steps 2 to 5 to install the second adapter module.
7. Plug the startup module (Figure 4-24, C,) into the hotplug connector on the board.
A A
B B
Figure 4-24 Installing the SIVAPAC-SIPAC Board Adapter
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Replacing the Board Lock

Install the board adapter increases the board length. The boards jut out slightly from the board
shelf. To ensure that these boards can still snap into place in spite of the board adapter, the
upper black lock must be replaced with a gray lock.
Black and gray board locks Remove the black lock

(At the point marked with the arrow press
the lock out of its seating and pull it out of
the shelf.)
Figure 4-25 Replacing the Board Lock
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.5.6 Initializing the Boards

The system software detects the boards in ascending order, starting with the lowest installation
position the first time the system starts up. The system initializes subscriber line circuits and
ports in the sequence indicated by the arrow (Figure 4-26).
The system activates all connected boards in the following situations:
● The maximum configuration has not yet been reached. While sequentially scanning the
slots for each board, the system software checks whether the maximum number of stations
or trunks has been exceeded. If it has, the board is not activated. The board LED shows
the board’s status.
● At least one B channel on line trunk modules is available for the slot (only the available
number of B channels is activated).
Assignment of subscriber line circuits and ports
Expansion cabinet
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Basic cabinet
1 2 3 4 5 6 7 8 9 10
C
B
S
A
P
Figure 4-26 HiPath 3800 - Initialization of Subscriber Line Circuits and Ports
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.5.7 Distribution of the PCM Highway

HiPath 3800 provides PCM highway bundles with 2 x 4 PCM highways for each peripheral
board slot. There are 32 time-division multiplex channels available for each PCM highway.
Blockages occur if these are busy. The system cannot execute any more call requests.
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-division
multiplex channels available. The following figures show the PCM highways for both system
cabinets of the HiPath 3800.
Basic cabinet: PCM highways
PCM highway bundle A

with 2 x 4 PCM highways
PCM highway bundle F

HDLC
Figure 4-27 HiPath 3800 - PCM Highways in the Basic Cabinet

The basic cabinet provides two PCM highway bundles with 2 x 4 PCM highways each. There
are 32 time-division multiplex channels available for each PCM highway.
The PCM highway bundles in the basic cabinet are used by peripheral boards according to the
following rules:
● Single-cabinet system (basic cabinet only)
With the exception of boards DIUN2, DIU2U (for U.S. only) and STMI2, the peripheral
boards only use the PCM highways of bundle A:
– PCM segment for board slots 1 – 5 = 128 time-division multiplex channels (four PCM
highways)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
– PCM segment for board slots 7 – 10 = 128 time-division multiplex channels (four PCM
highways)
DIUN2, DIU2U (for U.S. only) and STMI2 use the PCM highways from bundle F. Thus there
are an additional 128 time-division multiplex channels available for slots 1 – 5 and for slots
7 – 10 for these boards.
If more than the 2 x 128 time-division multiplex channels from bundle F are required be-
cause of the configuration with these boards, the system will automatically resort to time-
division multiplex channels from bundle A. However, only complete boards are activated
on the other trunk group. The remaining time-division multiplex channels remain free.
● Two-cabinet system (basic cabinet + expansion cabinet)
All peripheral boards use the PCM highways from bundle A only.
Expansion cabinet: PCM highways
PCM highway bundle A

Connection to the PCM highway

bundle F in the basic cabinet
PCM highway bundle F
(not used)
HDLC connection to the basic cabinet

HDLC
Figure 4-28 HiPath 3800 - PCM Highways in the Expansion Cabinet

The expansion cabinet provides a PCM highway bundle with 2 x 4 PCM highways. There are
32 time-division multiplex channels available for each PCM highway.
● PCM segment for board slots 1 – 6 = 128 time-division multiplex channels (four PCM high-
ways)
● PCM segment for board slots 8 – 14 = 128 time-division multiplex channels (four PCM
highways)
PCM highway bundle F is not used.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Time-division multiplex channels for peripheral boards

The following table lists the maximum number of time-division multiplex channels that the dif-
ferent boards require. A distinction is made here between:
● static time-division multiplex channels
Time-division multiplex channels are subject to static assignment in trunk boards. This en-
sures that all incoming calls can be processed.
● dynamic time-division multiplex channels
Time-division multiplex channels are subject to dynamic assignment in subscriber line
modules. Channels are seized for each call and released afterwards. This means that the
current number of time-division multiplex channels required is determined by the number
of active stations.
Restrictions for using the TMDID board

7 The TMDID board only uses the first half of a PCM segment. Consequently, a max-
imum of 64 channels is available on each PCM segment for TMDID-specific static
time-division multiplex channels.
To guarantee that the system operates without blocking when using the TMDID, the
boards on a PCM segment must not require more than the 64 static time-division
multiplex channels.
Examples for a PCM segment:
● 2 x TMDID + 1 x DIU2U = 64 static time-division multiplex channels = approved
equipment
● 1 x TMDID + 1 x TMC16 + 1 x DIU2U = 72 static time-division multiplex channels
= unapproved equipment
● 1 x TMDID + 2 x SLMO2 = 8 static and 96 dynamic time-division multiplex chan-
nels = approved equipment
Table 4-4 Maximum Number of Time-Division Multiplex Channels Required Per Board
Board Maximum number of time-division Time-division multiplex

multiplex channels required channel assignment
DIU2U 48 static
DIUN2 60 static
IVMN8 8 dynamic
IVMNL 24 dynamic
1
SLCN 128 dynamic
SLMA 24 dynamic
SLMA2 24 dynamic
SLMA8 8 dynamic
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Table 4-4 Maximum Number of Time-Division Multiplex Channels Required Per Board
Board Maximum number of time-division Time-division multiplex

multiplex channels required channel assignment
SLMO2 482 dynamic
SLMO8 162 dynamic
STMD3 16 static/dynamic3
STMI2 32 dynamic
STMI2 + PDMX4 64 dynamic
TM2LP 8 static
TMC16 16 static
TMCAS-2 60 static
TMDID 8 static
TMEW2 4 static
1 A time-division multiplex channel is required if a call is being conducted over the “home SLCN board” of a mobile tele-
phone. If a call is being conducted over a “Current location SLCN board”, additional time-division multiplex channels will
be required. More information is provided in Section 11.6, “Multi-SLC and System-Wide Networking”.
2 The maximum number of masters and slaves possible is taken into consideration.
3 Static time-division multiplex channel assignment for operation as a trunk board, dynamic assignment for operation as a
subscriber line module.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.5.8 Static Traffic Capacity

The static traffic capacity of the HiPath 3800 system can be determined as follows.
Table 4-5 HiPath 3800 - Static Traffic Capacity
HiPath 3800 Slots per PCM seg- Static traffic capac- Total static traffic
ment ity per PCM seg- capacity of the
ment system
1–5 128 erlangs +
Single-cabinet sys- (128 erlangs1)
tem 512 erlangs
(see page 4-46) 7 – 10 128 erlangs +
(128 erlangs1)
1–5 128 erlangs
Two-cabinet sys- 7 – 10 128 erlangs
tem 512 erlangs
(see page 4-47) 11 – 16 128 erlangs
18 – 24 128 erlangs
1 The basic cabinet provides two PCM highway bundles with 2 x 4 PCM highways each. DIUN2, DIU2U (for U.S.
only) and STMI2 use the PCM highways from bundle F. Thus there are an additional 128 time-division multiplex
channels available for slots 1 – 5 and for slots 7 – 10 for these boards in the basic cabinet. If HiPath 3800 is used
as a two-cabinet system, a use of PCM highway bundle F is not possible.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.6 Connecting the Cable to the Backplane
All cables that leave the system cabinet must be attached to the metal back panel
> using cable ties.
Connection options
Peripheral devices can be connected up to the HiPath 3800 in a number of different ways:
● SIVAPAC connector on the backplane for connecting the external main distribution frame
via CABLUs (prefabricated cabling units) or for connecting external patch panels (see
Section 4.2.6.4).
● Connector panels with RJ45 jacks for direct connection of peripherals (see
Section 4.2.6.5). The connector panels are clipped onto the SIVAPAC connectors on the
backplane.
● For U.S. Only: Connector panels with CHAMP jack for direct connection of peripherals (see
Section 4.2.6.6). The connector panels are clipped onto the SIVAPAC connectors on the
backplane.
● Connector panels each with two SIPAC 1 SU connectors for connecting the external mail
distribution frame MDFU-E or external patch panels using CABLUs (see Section 4.2.6.7).
The connector panels are clipped onto the SIVAPAC connectors on the backplane.
The type of connection used will be decided in consultation with the customer on conclusion of
the agreement. The cabinets will be delivered accordingly with or without clipped-on connector
panels.
Danger
the grounding point of the electrical building installation before connecting up the pe-
ripherals (for example, potential equalization bus).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.6.1 Backplane of the Basic Cabinet
9 SIVAPAC connec-
tor for peripherals
68-pin DB68 mini-

jack (connection to
EC)
DC port
AC port
Figure 4-29 HiPath 3800 - Backplane (S30804-Q5392-X) of the Basic Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
X105
X104
X103
X102
X101
X112
X111
X110
X109
X201
X214
X209
X116
X212
X211
Figure 4-30 HiPath 3800 - Connectors and Jacks on the Backplane of the Basic Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Table 4-6 HiPath 3800 - Assignment of Connectors and Jacks on the Backplane of the
Basic Cabinet
Connector Function
X101 – X105 SIVAPAC connector for connecting peripherals:
X109 – X112 CABLUs and open-end cables are used for connection to the MDFU-E or to
an external patch panel (see Section 4.2.6.4).
Note: The SIVAPAC connectors can have the following connector panels:
● Connector panels with RJ45 jacks for direct connection of peripherals
(see Section 4.2.6.5).
● For U.S. only: Connector panels with CHAMP jack for direct connection
of peripherals (see Section 4.2.6.6).
● Connector panels each with two SIPAC 1 SU connectors for connecting
an external main distribution frame or external patch panel using CABLUs
For selected countries only: PBXXX board: An APPCU adapter (S30807-
K5415-X) is used to connect the CAS cable and the DIUN2 connection cable.
X116 SIVAPAC connectors for picking up the signals from the REALS board.
CABLUs for connection to the MDFU-E (jumper strip for 25 TW):
● C39195-A7267-A372: 3 m in length, short stripped length for MDFU-E
slots 11-21 (see Figure 4-37)
● C39195-A7267-A373: 3 m in length, long stripped length for MDFU-E
Open-end cable (24 TW) for connection to an external patch panel:
● S30267-Z196-A150: 15 m in length
● S30267-Z196-A250: 25 m in length
● S30267-Z196-A350: 35 m in length
● S30267-Z196-A550: 55 m in length
● S30267-Z196-A950: 95 m in length
X201 68-pin DB68 mini-jack for connecting the cable C39195-Z7611-A10 to the ex-
pansion cabinet (for the DBSAP board)
X209 DC port
X211, X212 AC power
X214 10-pin connection for the ring voltage generator RGMOD (for selected coun-
tries only)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.6.2 Expansion Cabinet Backplane
13 SIVAPAC connectors
for peripheral boards
DB68 mini-jack (connec-
DC port
DBSAP with 68-pin
tion to BC)
AC port
Figure 4-31 HiPath 3800 - Expansion Cabinet Backplane (S30804-Q5393-X)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

X115
X114
X113
X112
X111
X110
X109
X106
X105
X104
X103
X102
X101
X214
X209
X223
X220 –
X211
Figure 4-32 HiPath 3800 - Connectors and Jacks on the Backplane of the Expansion Cab-
inet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Expansion Cabinet
Connector Function
X101 – X106 SIVAPAC connector for connecting peripherals:
X109 – X115 CABLUs and open-end cables are used for connection to the MDFU-E or to
an external patch panel (see Section 4.2.6.4).
Note: The SIVAPAC connectors can have the following connector panels:
● Connector panels with RJ45 jacks for direct connection of peripherals
● For U.S. only: Connector panels with CHAMP jack for direct connection
of peripherals (see Section 4.2.6.6).
● Connector panels each with two SIPAC 1 SU connectors for connecting
an external main distribution frame or external patch panel using CABLUs
For selected countries only: PBXXX board: An APPCU adapter (S30807-
K5415-X) is used to connect the CAS cable and the DIUN2 connection cable.
X209 DC port
X211 AC power
X214 10-pin connection for the ring voltage generator RGMOD (for selected coun-
tries only)
X220 – X223 Connections for plugging in the DBSAP board.
DBSAP has a 68-pin DB68 mini-jack for connecting the cable C39195-Z7611-
10 to the basic cabinet (to the jack X201).
4.2.6.3 Connecting Cables Between the Basic and Expansion Cabinet

The connection cable C39195-Z7611-A10 has to be connected up for feeding the HDLC, PCM,
and clock signals from the basic cabinet to the expansion cabinet:
● Basic cabinet = X201 jack
● Expansion cabinet = DBSAP board
To ensure smooth operation, use only shielded cables with a maximum length of
> 1 m.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.6.4 Connecting Peripherals to the SIVAPAC Connector on the Backplane

The boards should be installed in the cabinets as described in Section 4.2.5.
Danger
Use the CABLUs (prefabricated cabling units) that are listed in the following table to establish
the connection with the MDFU-E. Open-end cables must be used if an external patch panel is
being used. See also Section 4.2.7, “Using an External Main Distribution Frame or External
Patch Panel”.
CABLUs and open-end cables for SIVAPAC connectors
If Then
Slot with CABLUs for connection between backplane (SIVAPAC connector) and
SLCN MDFU-E (splitting strip for 16 TW):
SLMA8 ● C39195-A7267-A370: 3 m in length, short stripped length for MDFU-E
SLMO8 slots 11-21 (see Figure 4-37)
STMD3 ● C39195-A7267-A371: 3 m in length, long stripped length for MDFU-E
TM2LP slots 1-10 (see Figure 4-37)
TMC161 CABLU for connection between backplane (SIVAPAC connectors) and ex-
TMDID2 ternal patch panel S30807-K6143-X (SIVAPAC socket terminal strip):
● S30267-Z333-A20: 2 m in length (refer to Figure 4-43)
Open-end cable (24 TW) for connection between backplane (SIVAPAC con-
nector) and external patch panel:
● S30267-Z196-A150: 15 m in length
● S30267-Z196-A250: 25 m in length
● S30267-Z196-A350: 35 m in length
● S30267-Z196-A550: 55 m in length
● S30267-Z196-A950: 95 m in length
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
If Then
Slot with CABLUs for connection between backplane (SIVAPAC connector) and
SLMA MDFU-E (jumper strip for 25 TW):
SLMA21 ● C39195-A7267-A372: 3 m in length, short stripped length for MDFU-E
● C39195-A7267-A373: 3 m in length, long stripped length for MDFU-E
CABLU for connection between backplane (SIVAPAC connectors) and ex-
ternal patch panel S30807-K6143-X (SIVAPAC socket terminal strip):
Open-end cable (24 TW) for connection between backplane (SIVAPAC con-
nector) and external patch panel:
● S30267-Z196-A150: 15 m in length
● S30267-Z196-A250: 25 m in length
● S30267-Z196-A350: 35 m in length
● S30267-Z196-A550: 55 m in length
● S30267-Z196-A950: 95 m in length
Slot with A CAS cable is connected via an APPCU adapter (S30807-K5415-X).
PBXXX1
2 for U.S. only
Information on cable and connector assignment is provided in the board descriptions in

Chapter 3.
Closing the backplane of the system cabinets
After the cable has been connected, the backplane of the basic cabinet and that of
> the expansion cabinet (if applicable) must be closed with the dummy panels provid-
ed (C39165-A7075-C44).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Figure 4-33 HiPath 3800 - Backplane of the Basic Cabinet with Mounted Filler Panels
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.6.5 Connecting Peripherals to the Connector Panels with RJ45 Jacks

The boards should be installed in the cabinets as described in Section 4.2.5. The connector
panels plugged into the SIVAPAC connectors of the backplane are equipped with eight or 24
RJ45 jacks according to the relevant board.
Connector panel with 24 RJ45 jacks
Connector panel with eight RJ45 jacks
8-pin RJ45 jack
8 1
Figure 4-34 HiPath 3800 - connector panels with RJ45 Jacks
Danger
Connect the peripheral directly to the 8-pin RJ45 jacks on the connector panels.
If Then
Slot with Connector panel with eight RJ45 jacks: S30807-Q6624-X
STMD3 The RJ45 jacks are configured with four wires. S0 stations can be directly
connected (1:1 cable). The receive and send lines should be switched for
trunk connections.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

If Then
Slot with Connector panel with 24 RJ45 jacks: S30807-Q6622-X
SLCN The RJ45 jacks are configured with two wires.
SLMA
SLMA21
SLMA8
SLMO2
SLMO8
TM2LP
TMC161
TMDID2
different or no The backplane sections of other boards and empty board slots must be cov-
assignment ered with filler panels.
2 for U.S. only

Chapter 3.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.6.6 Connecting Peripherals to the Connector Panels

with CHAMP Jack (for U.S. only)
The boards should be installed in the cabinets as described in Section 4.2.5. The S30807-
Q6626-X connector panels attached to the SIVAPAC connectors on the backplane are
equipped with a CHAMP jack.
Figure 4-35 HiPath 3800 - Connector Panel with CHAMP Jack (for U.S. only)
Danger
Connect the peripheral directly to the CHAMP jack in the connector panels.
If Then
Slot with periph- A cable with CHAP jack should be used to connect to a main distributor
eral card frame or external patch panel.
No assignment The backplane sections with empty board slots must be covered with filler
panels.
Chapter 3.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.6.7 Connecting Peripherals to Connector Panels with SIPAC 1 SU Connectors

The boards should be installed in the cabinets as described in Section 4.2.5. The S30807-
Q6631-X connector panels attached to the SIVAPAC connectors on the backplane have two
SIPAC 1 SU connectors each.
Cables and connectors for ports 17 - 24
Cables and connectors for ports 1 - 16
Figure 4-36 HiPath 3800 - Connector Panel with Two SIPAC 1 SU Connectors (S30807-
Q6631-X)
Danger
Use the CABLUs that are listed in the following table to establish the connection with the
MDFU-E or an external patch panel. See also Section 4.2.7, “Using an External Main Distribu-
tion Frame or External Patch Panel”.
In special cases where the prefabricated CABLUs cannot be used, open-end cables should be
used.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
CABLUs and open-end cables for SIPAC 1 SU connectors
If Then
Slot with CABLUs for connection between connector panel (SIPAC 1 SU connectors)
SLCN and MDFU-E (splitting strip for 16 TW):
SLMA8 ● S30269-Z100-A11: 3 m in length, short stripped length for MDFU-E
STMD3 ● S30269-Z100-A21: 3 m in length, long stripped length for MDFU-E slots
TM2LP 1-10 (see Figure 4-37)
TMC161 CABLU with 16 TW for connection between connector panel (SIPAC 1 SU
TMDID2 connectors) and external patch panel S30807-K6143-X (SIVAPAC socket
terminal strip):
Open-end cable (16 TW) for connection between backplane (SIPAC 1 SU
connectors) and external patch panel:
● S30267-Z192-A60: Open-end cable with 16 TW, 6 m in length
(Information on the required stripped lengths for open-end cables is
provided in Figure 4-48.)
Slot with CABLUs for connection between connector panel (SIPAC 1 SU connectors)
SLMA and MDFU-E (jumper strip for 25 TW):
SLMA21 ● S30269-Z100-A14: 3 m in length, short stripped length for MDFU-E
● S30269-Z100-A24: 3 m in length, long stripped length for MDFU-E slots
1-10 (see Figure 4-37)
CABLU with 24 TW for connection between connector panel (SIPAC 1 SU
connectors) and external patch panel S30807-K6143-X (SIVAPAC socket
terminal strip):
Open-end cable (16 TW) for connection between backplane (SIPAC 1 SU
connectors) and external patch panel:
(Information on the required stripped lengths for open-end cables is
provided in Figure 4-48.)
different or no The backplane sections of other boards and empty board slots must be cov-
assignment ered with filler panels.
2 for U.S. only

Chapter 3.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7 Using an External Main Distribution Frame or External Patch

Panel
The HiPath 3800 has various connection options for connecting the peripherals. The type of
connection used will be decided in consultation with the customer on conclusion of the agree-
ment. This may involve the implementation of an external main distribution frame or an external
patch panel.
This section contains information on the following external components:
● Main distribution frame MDFU-E, Section 4.2.7.1
● Patch panel S30807-K6143-X, Section 4.2.7.2
● S0 patch panel C39104-Z7001-B3, Section 4.2.7.3
● For U.S. only: Connecting Network Facilities, Section 4.2.7.4
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.7.1 Using an External Main Distribution Frame MDFU-E S30805-U5283-X
For U.S. only:
328.8 mm
4
Jumpering
5 Channel
6 21 slots (9 x 30 mm)
669.0 mm
19
20
21
Special built-in
comps.
2 x PFT1
or
Figure 4-37 MDFU-E - Layout and Dimensions (669.0 x 328.8 x 125.4 mm)
Not more than 21 CABLUs per MDFU-E with one 16-TW strip or 25-TW strip (9 x 30 mm) can
be implemented.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7.1.1 Mounting the Main Distribution Frame (MDFU-E)

The MDFU-E main distribution frame should be installed in the direct vicinity of the system
(note length of connection cable) and at eye level.
The packing material contains a drawing that can be used as a drilling template.
Procedure for wall mounting
Step Activity
1. Use the template to drill the holes.
2. Insert the wall anchors and screw in the screws, leaving 5 mm projecting.
3. Remove the housing cover and mount the MDFU-E on the brackets.
4. Tighten the screws through the holes.
4.2.7.1.2 Laying the Line Network and Jumpers on the MDFU-E
Danger
7 Be sure to connect the main protective earthing terminal on all system cabinets and
all main distribution frames to the grounding point of the electrical building installa-
tion before connecting up the peripherals (for example, potential equalization bus).
Jumpers, external line network

Most main distribution frames do not have an external side. You must jumper them to the in-
coming line network (see jumpering duct, Figure 4-37). Use a standard wiring tool for laying the
cable wires.
Surge protector
To divert surges caused by lightning, insert surge protectors on
● lines that leave the system buildings (outside stations)
● lines > 500 m long.
Connect the polarized surge protectors to the plugging locations on the splitting strip described
above (see Figure 4-39).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Splitting and jumper strips
a
b
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1Ea 1Sa E = Receive

1Eb 1Sb S = Transmit
a
b
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
S0 bus 1 ... S0 bus 8
Splitting strip for 16 TW (C39334-A166-A1)
a
b
1 3 5 7 9 11 13 15 17 19 21 23 25
No. 25 not used
Jumper strip for 25 TW (C39334-A166-A3)
Figure 4-38 Assignment (Numbering) of the Splitting/Jumper Strips (view from above)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Stripping the open-end cable for the MDFU-E
a 1 a
b
1
b
a 2 a
b 2
Example for connecting b
a 3 a
b the wires 3
b
a 4 4 a
b b
a 5 a
b 5
b
a 6 a
b 6 b
a 7 a
b 7 b
a 8 a
b 8 b
a a
9 9 b
b
a 10 a
10 b
b
a 11 a
11 b
b
a 12 a
12 b
b
a 13 a
b
13 b
View from below a
View from above (surge
a 14 14
b b protector plug locations)
a 15 a
b 15 b
a 16 a
b 16 b
Cable with film sheath: No. 6 (conductive copper tape) 1.5 windings. Ground wire
shortened to 25 mm and soldered onto conductive tape (1).
Stripped length
Stripped length = 600 ± 5 mm
250 ± 5
(1) Stripped length = 910 ± 5 mm for
MDFU-E slots 1 to 10
Velcro tape (19 mm wide)

Bundle fastener
Figure 4-39 Stripping an Open-End Cable for the MDFU-E
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Color Codes for the Open-End Cable
Table 4-8 Color Codes for the Open-End Cable

Color Group Pair a-Wire b-Wire Color Group Pair a-Wire b-Wire
(Tip) (Ring) (Tip) (Ring)
1 1 wht/blu 4 16 yel/blu
blu/wht blu/yel
2 wht/ora 17 yel/ora
ora/wht ora/yel
3 wht/grn 18 yel/grn
grn/wht grn/yel
4 wht/brn 19 yel/brn
brn/wht brn/yel
5 wht/gry 20 yel/gry
gry/wht gry/yel
2 6 red/blu 5 21 vio/blu
blu/red blu/vio
7 red/ora 22 vio/ora
ora/red ora/vio
8 red/grn 23 vio/grn
grn/red grn/vio
9 red/brn 24 vio/brn
brn/red brn/vio
10 red/gry Note: In the case of cables with 16 double
gry/red wires, the specifications for pairs 17 to 24 are
not relevant.
3 11 blk/blu
blu/blk
12 blk/ora
ora/blk
13 blk/grn
grn/blk
14 blk/brn
brn/blk
15 blk/gry
gry/blk
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7.2 Inserting the External Patch Panel S30807K6143-X
Structure
All incoming cables must be attached to the patch panel using cable ties.
>
SIVAPAC edge connector: port for
CABLU connection to the backplane
Eight surge protector plug loca-

tions
Front panel with 3 x 16 RJ45 jacks
RJ45 jack assignment:

4 = a-wire
5 = b-wire
8 1

Figure 4-40 Patch Panel S30807-K6143-X
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.7.2.1 Installing the Patch Panel in a 19-Inch Cabinet
Installation procedure
Caution
7 The patch panel must be installed above the system cabinet.
A minimum of one height unit must be kept clear above the cabinet to guarantee suf-
ficient ventilation of the system cabinet. This is achieved by the gray plastic cover
fixed to the top of the system cabinets. Never remove this plastic cover.
Insert the patch panel (A, in Figure 4-41) above the system cabinet and secure it to the 19-inch
frame on both the left and the right using two screws on each side.
A
B
Figure 4-41 Installing the External Patch Panel in the 19-Inch Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7.2.2 Connecting the Line Network to the External Patch Panel
Danger
7 Be sure to connect the main protective earthing terminal on all system cabinets and
all patch panels to the grounding point of the electrical building installation before
connecting up the peripherals (for example, potential equalization bus).
Telephones and trunks are connected directly to the RJ45 jack on the front of the patch panel.
Information on RJ45 jack assignment on the front of the patch panel is provided in the board
descriptions (in the “Cable and Connector Assignment” table) in Chapter 3.
Surge protector
To divert surges caused by lightning, insert surge protectors on
● lines that leave the system buildings (outside stations)
● lines > 500 m long.
Connect the polarized surge protectors to the plugging locations F1 to F8 provided on the patch
panel (see Figure 4-43).
Front panel with 3 x 16 RJ45 jacks each
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47
Example 1
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48
Board with 16 ports Board with 16 ports
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47
Example 2
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47
Example 3
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48
Figure 4-42 Layout of the Patch Panel S30807-K6143-X for Different Peripheral Boards
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
SIVAPAC edge connectors: port for CABLU connection to the backplane
X5 X1
X11
1 X12 1 X9 X9, X10, X11 and PFT1 not
1 X13 1 X10 used in HiPath 3000.
1 X14
1 X15
F1 F4 F6 F8 Slots F1–F8 for PFT1
surge protector
F2 F3 F5 F7
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48
Front panel with 3 x 16 RJ45 jacks
Options for connecting the external line network:

● Connection via the RJ45 jacks on the front of the patch panels. Using jumper wire,
bridges must be inserted between the terminal strips X12 and X14 and between X13
and X15. The contact between the connector X5 and the first eight RJ45 jacks is only
set up when wire bridges are present.
● Direct connector jumpering on the X12/X13 connector. Bridges are not necessary in
this case.
1 2 3 4 5 6 7 8 X12, X14
1 2 3 4 5 6 7 8
X13, X15
1 2 3 4 5 6 7 8
a b a b a b a b a b a b a b a b
Figure 4-43 Assignment of Patch Panel S30807-K6143-X
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7.3 Inserting External S0 Patch Panel C39104-Z7001-B3
Structure
All incoming cables must be attached to the patch panel using cable ties.
>
3 x 8 RJ45 jacks

Figure 4-44 S0 Patch Panel C39104-Z7001-B3
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.7.3.1 Installing the S0 Patch Panel in the 19-Inch Cabinet
Installation Procedure
Caution
7 The patch panel must be installed above the system cabinet.
A minimum of one height unit must be kept clear above the cabinet to guarantee suf-
ficient ventilation of the system cabinet. This is achieved by the gray plastic cover
fixed to the top of the system cabinets. Never remove this plastic cover.
Insert the S0 patch panel (A, in Figure 4-45) above a system cabinet and secure it to the 19-
inch frame on both the left and the right using two screws (B) on each side.
A
B
Figure 4-45 Installing the External S0 Patch Panel in the 19-Inch Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7.3.2 Connecting Lines to the External S0 Patch Panel
24 22 20 18 ... ... 8 6 4 2
23 21 19 17 ... ... 7 5 3 1
3 x 8 RJ45 jacks, numbering

:
RJ45 jack assignment:

Pin
as a subscriber line as a trunk connection
3 Transmit + Receive +
4 Receive + Transmit +
8 1 5 Receive – Transmit –
6 Transmit – Receive –
Figure 4-46 Assignment of the S0 Patch Panel C39104-Z7001-B3

CABLUs must be manually connected to the S0 patch panel (Figure 4-47). You can use the
Krone wiring tool for this.
87632145
Pin assignment of RJ45 jacks
Twist the wire pairs before laying them.
Figure 4-47 Laying Wire Pairs at the S0 Patch Panel
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Stripping the open-end cable for the S0 patch panel
Stripped length
250 ± 5
(1)
Velcro tape (19 mm wide)

Bundle fastener
Cable with film sheath: No. 6 (conductive copper tape) 1.5 windings. Ground wire shortened
to 25 mm and soldered onto conductive tape (1).
Stripped length = 600 mm ± 5 mm
Figure 4-48 Stripping the Open-End Cable for the S0 Patch Panel
The color codes for open-end cables are provided in Table 4-8.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.7.4 For U.S. only: Connecting Network Facilities
DANGER
7 Ground the system properly before connecting the stations.
Connecting to the Point of Demarcation

Most main distribution frames are designed with a network demarcation block. You must cross-
connect the MDF to the incoming trunks. Use a standard wiring tool for laying the cable wires.
Connecting to T1, PRI, or CorNet
Caution
7 The TMST2 Module can only be installed in conjunction with a listed channel service
unit CSU.
Secondary Protection
DANGER
7 To protect against surge voltage caused by lightning, the following boards require
secondary protection when their lines leave the building where the main distribution
frame is housed:
● DIU2U*
● SLMA / SLMA8
● TMC16
● TMDID
● TMEW2
● TM2LP
* When this module is connected to the public network, secondary protection must
be provided by the CSU.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.8 Loading the System Software and Installing Subboards on the

CBSAP
Caution
handling boards). Connect the wristband to the slide-in shelf in the cabinet using the
alligator clip.
The boards should be installed in the cabinets as described in Section 4.2.5.
The central control boards are not always fully equipped when delivered. Optional plug-in
boards are packaged individually.
See Section 3.2.3 for information on slots for subboards on the central control board CBSAP.
Caution
7 Place the central control board on a flat surface before installing subboards.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.2.9 Connecting Workpoint Clients

Refer to Chapter 10 for details.
4.2.10 Making Trunk and Networking Connections

Refer to the following board descriptions for information:
● DIUN2 (S2M)
● STMD3 (S0)
● STMI2 (IP)
● TM2LP (MSI)
● TMEW2 (E&M)
● DIU2U (for U.S. only)
● TMC16 (for selected countries only)
● TMDID (for U.S. only)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.2.11 Performing a Visual Inspection
Introduction
Before starting up the system, you must perform a visual inspection of the hardware, cables,
and the power supply. The procedure is shown in Table 4-9. The visual inspection must be per-
formed while the system is disconnected from the power supply.
Caution
7 Before beginning work, make sure that the system is grounded and disconnected
from the power supply.
Observe the measures for protecting electrostatically sensitive devices (see page
1-9).
Visual Inspection Procedure
Table 4-9 Visual Inspection Procedure
Step Activity Resources/ Action

Remarks
1. Compare the slots of the Board assign- If necessary, correct the board config-
available boards with the ment map uration and notify the sales depart-
component mounting dia- ment.
gram.
2. Check that all boards are See page 4-34 If necessary, plug the boards in again.
secure.
3. Check that a shielding cov- If necessary, replace missing shield-
er has been attached for all ing covers (refer to page 4-35).
boards with no connection
options in the front cover.
4. Check whether the slots for If necessary, attach the outer panel
LUNA2 and for REALS (ba- (see page 4-36).
sic cabinet only) are cov-
ered by an outer panel.
5. Check whether all system Get additional connection and filler
cabinets have been sealed panels where required.
at the rear with the connec-
tion and filler panels provid-
ed.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Table 4-9 Visual Inspection Procedure
Step Activity Resources/ Action

Remarks
6. Check whether a separate If necessary, ground the system as
grounding is connected to described in the following sections:
the main grounding termi- ● Section 4.2.3.4, for installing the
nals of all system cabinets. standalone HiPath 3800
● Section 4.2.4.4, for installing the
HiPath 3800 in the 19-inch cabi-
net.
7. Check the local supply volt- Digital multime-
age. ter
8. Only for installing HiPath Fit the cover into the guides and press
3800 as a standalone sys- down on the cover unit it snaps into
tem: place.
close all system cabinets
with the front and back plas-
tic covers provided.
After finishing the visual inspection, you can begin starting up the HiPath 3800 as
> described in Chapter 5.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Installing HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300
4.3 Installing HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300
4.3.1 Installation Prerequisites
Warning
Tools and resources needed

The following are needed for installing the HiPath 3550, HiPath 3350, HiPath 3500, and HiPath
3300 systems:
● Tools:
– Diagonal cutting pliers, telephone pliers, wire stripper, flat-nosed pliers
– Slotted screwdrivers, from 2 to 8 mm (1/4 to 5/16 in.)
– Phillips or cross-point screwdrivers, sizes 1 and 2
– TORX screwdriver
– Electric drill, hammer
– Level, tape measure
– For U.S. only: Punch-down tool suitable for the block used (such as block 66)
● Resources:
– Manager T or HiPath 3000/5000 Manager E
– Digital multimeter for testing ground connections and partial voltages
– Telephone test set for analog interfaces
– Not for U.S.: ISDN tester (such as K3000 or Aurora)
– For U.S. only: AuroraDuet, AuroraExpert, AuroraRemote or similar, ISDN protocol analyz-
er
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.2 Installation Procedure
Table 4-10 HiPath 3550, 3350, 3500, 3300 - System Installation Procedure
Step Installation Activity

Installing HiPath 3550 and HiPath Installing HiPath 3500 and HiPath 3300
3350 (19-Inch Housing)
1. Selecting the Installation Site, page Selecting the Installation Site, page 4-111
4-87 (usually predetermined)
(usually predetermined)
2. Unpacking the Components, page Unpacking the Components, page 4-112
4-90
3. Not for U.S.: Mounting the Main Dis- Not for U.S.: Attaching a HiPath 3500 and
tribution Frame (HiPath 3550 only), HiPath 3300 to the Wall, page 4-113
page 4-90
4. Removing the System Housing Cov- Installing a HiPath 3500 or HiPath 3300 in a
er, page 4-92 Cabinet, page 4-114
5. Attaching the System to the Wall, Grounding the System, page 4-116
page 4-94
6. Grounding the System and the Main Installing the Boards, page 4-117
Distribution Frame, page 4-95
7. Installing the Boards, page 4-98 Connecting Cables and the Line Network,
page 4-118
8. Laying the Line Network and Con- Configuration notes, page 4-120
nection Cables, page 4-99
9. Attaching Ferrite, page 4-102 Connecting Workpoint Clients, page 4-123
10. Configuration notes, page 4-105 Making trunk connections, page 4-123
11. Connecting Workpoint Clients, page Performing a Visual Inspection, page 4-123
4-109
12. Making trunk connections, page 4-
109
13. Performing a Visual Inspection,
page 4-109
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.3 Installing HiPath 3550 and HiPath 3350

This section contains information on how to install HiPath 3550 and HiPath 3350. This chapter
describes the standard installation procedures for the basic system. Refer to Chapter 9 for in-
formation about supplementary equipment and expansions.
Selecting a site
The customer usually has a preferred installation site in mind.
● To guarantee sufficient system ventilation, keep the area surrounding the housing clear as
follows: allow 30 cm clearance on the left (for board replacement), and 10 cm clearance
on the right, top and bottom of the housing.
For U.S. Only:
● Ensure that the installation site is in the immediate vicinity of an electrical outlet
● Allow space for a main distribution frame or other additional equipment.
● Install lightning and surge arrester equipment.
● Avoid standard carpeting, as it tends to produce electrostatic charges.
● Ensure that a distance of at least 40 in. (101.6 cm) is left between
Siemens Enterprise Communications GmbH & Co. KG equipment and other electrical
equipment. The National Electrical Code (NEC) requires 36 in. (91.44 cm) of clearance in
front of electrical equipment and 40 in. (101.6 cm) of clearance from other electrical service
equipment.
● Ensure that the equipment room for the system provides adequate space for installation
and maintenance activities, including removing and replacing the cover). See Figure 4-49
for space requirements on the sides of the system. We recommend using a plywood back-
board at least 0.5 in. (127 mm) thick and measuring at least 4 ft. (122 cm) by 4 ft. (122 cm.).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Main distribution frame
Leave 46 cm 20.3 cm
(18’’) free HiPath 3550 (8’’)
or
HiPath 3350
Backplane
50.8 cm
122 X 122 cm (4 X 4 ft.)
(20’’)
The system measures 18 by 17.7 inches (46 x 45 cm). The following spaces
should be allowed: 18 in. (46 mm) of clearance on the left, and at least 8 in. (203
mm) of clearance on the top and right. Allow 20 in. (50.8 cm) of clearance on the
bottom (for cables).
Figure 4-49 HiPath 3550 and HiPath 3350 - Space Requirements (for U.S. only)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
You will find information on the design and dimensions in the following section:
● HiPath 3550 Section 2.2.2.2

The AC connection must fulfill the requirements specified in Table 4-11.
Table 4-11 Electrical Connection Values (for U.S. only)

voltage Range tions
from to from to
60 Hz wire, earth
AC Power Outlet Requirements

● The power source may not be more than 2 m (6 ft.) from the system.
● The power source must supply a voltage of 120 V AC (single phase, fused) in 50-60 Hz.
● A warning should be attached to the circuit breaker to prevent accidental removal of power.
● An independent electric circuit with an isolated ground conductor should be used.
● Recommendation: Add a power surge protector between the outlet and the system.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Procedure
Step Activity
proper departments.
Caution
4.3.3.3 Not for U.S.: Mounting the Main Distribution Frame (HiPath 3550 only)
Introduction
MDFU is the main distribution frame used (see Figure 4-50).
Installation notes
The MDFU-E main distribution frame should be installed in the direct vicinity of the system
(note length of connection cable) and at eye level. Mount it on the wall according to the instruc-
tions that came with it. The bag attached to the cover contains a drill template. It also contains
the necessary screws and wall anchors for attaching the MDF to the wall.
The MDFU must be grounded. Refer to Section 4.3.3.6 for an explanation of the procedure.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Procedure for mounting the MDFU on the wall
Step Activity
1. Use the template to drill the holes.
2. Insert the wall anchors and screw in the screws, leaving 5 mm projecting.
3. Remove the housing cover and mount the MDFU-E on the brackets.
4. Tighten the screws through the holes.
Layout and dimensions of the MDFU
328.8
4
Jumpering
5 Channel
367.0
7 9 slots (9 x 30 mm)
Special built-in comps.

2 x PFT1
or
1 x PFT4
Figure 4-50 MDFU - Layout and Dimensions (367.0 x 328.8 x 125.4 mm) (not for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.3.4 Removing the System Housing Cover
Warning
7 To prevent injuries, you must observe the following instructions for the removal and
attachment of the HiPath 3550 and HiPath 3350 housing cover.
Procedure
Step Activity
1. Loosen the two screwed plugs on the housing cover with a slotted screw driver.
Hold the housing cover so that it does not fall.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Step Activity
2. Remove the housing cover.
Warning
The shielding plate on the inside of the cover may have sharp edges which can
cause cuts.
Mounting the housing cover

To close the system housing again, put the cover on and fasten it with the two screwed plugs.
To avoid injuries, grasp the housing cover by its outside walls only when mounting it.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.3.5 Attaching the System to the Wall

Attach the system to the wall as shown in Figure 4-51.
Attaching the HiPath 3550 and HiPath 3350 housing to the wall
This is not an Hang system and

attachment tighten screws
point
Cable PSU/ Attachment of

UPS PSU
duct UPS
Rear wall of hous- to the rear
ing wall of hous-
Oblong holes for ing
wall attachment
30 cm
Minum clearance for replacing boards
Figure 4-51 HiPath 3550 and HiPath 3350 - Wall Attachment
Figure 4-52 HiPath 3550 and HiPath 3350 - Wall Attachment
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.3.6 Grounding the System and the Main Distribution Frame

Danger
7 If your personnel are not qualified to work on the low-voltage network (230Vac)
you must hire a licensed electrician.
The Section 1.3, “Electrical Environment” is to be adhered to.
Not for U.S.: Grounding of the System
Because of their safety class, the HiPath 3550 and HiPath 3350 do not have to be
> grounded.
If grounding is required in certain countries (for example in Finland, Norway, U.S.),
the wall housing HiPath 3550 and HiPath 3350 must be grounded by a separate
ground conductor via the ground connection marked “ ”.
For U.S. and Canada only: Grounding the system
The connector cables of systems HiPath 3550 and HiPath 3350 have a grounding. The system
must also be grounded by a separate ground conductor. This grounding connection must meet
the requirements of the relevant authorities (U.S. National Electrical Code, Canadian Electrical
Code). Lay a separate grounding from the earth to the system’s grounding connector. The
cross-section of the grounding must measure at least 14 AWG.
Grounding for the external main distributor frame
● Not for U.S.:
– HiPath 3550: Shipments always include an MDFU (Germany only) and two grounding
cables. Use one of the cables to ground the MDFU. It is not necessary to ground the
connection between the MDFU and HiPath 3550 (see Figure 4-53).
– HiPath 3350: This system type does not require an external main distribution frame.
The connection cables to the peripherals are attached directly to the boards and rout-
ed to the outside via a cable duct inside the housing.
Danger
7 An external main distribution frame which requires grounding (if the existing
ground connection is marked “ ”) must be grounded by a separate ground
conductor (minimum cross-section = 2.5 mm2)
Refer to Figure 4-53 when replacing a customer system but maintaining the existing exter-
nal main distribution frame.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

● For U.S. only:

The customer supplies a main distribution frame to complete the communications system.
Mount and ground the MDF in accordance with the manufacturer’s instructions.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Grounding an external main distribution frame
O Communication system to be Main distribution frame being

L replaced reused
D
S
Y
S
T
E Grounding
M screw
N External main distribution frame

E (You must install proper grounding,
W HiPath 3550 or HiPath 3350
if required)
(Grounding not required)
S
Y
S
T e. g. MDFU
E
M
green/yellow
Min. cross-section = 2.5 mm2

but not:
- central heating system
- drain channels
- ground conductor for antenna system
Figure 4-53 HiPath 3550, HiPath 3350 - Grounding an External Main Distribution Frame
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.3.7 Installing the Boards

Outside the U.S., the system is already equipped with the boards needed for the customer-spe-
cific requirements when the system is delivered.
In the U.S., you may need to install the boards.
Connecting to T1, PRI, or CorNet (for U.S. only)
Caution
7 The TST1 Module (HiPath 3550) can be installed only in conjunction with a listed
channel service unit (CSU).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.3.8 Laying the Line Network and Connection Cables
HiPath 3550 and HiPath 3350 - CABLU for connection to the external main distribution
frame
Jumper strip (25 TW) for installation in the exter-

nal main distribution frame
6 slip-on connectors (4 TW each) for connection to the

HiPath 3550 and HiPath 3350 boards
Figure 4-54 Layout of CABLU S30269-Z41-A30 (Length = 3 m)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

HiPath 3550 - MDFU ports for peripheral boards
The two arrows on the left mark the con-

nections for the cables coming from the
main distribution frame (MDFU).
Figure 4-55 HiPath 3550 - Backplane port for peripheral board
Not for U.S.: HiPath 3550: Connecting the Cabling
If Then
SLA8N Route the 16 TW to the MDFU via the SU X8 and 8 TW via SU X9 (see
SLA16N Figure 4-55) using a standard cable (with 16 TW). Connect both cables (= 1
SLA24N CABLU with SU connectors labeled 8 and 9) to the same jumper strip (25
SLC16N TW).
SLMO24
Slot with any ● Without an external main distribution frame (MDFU):
other periph- You can attach cables for the peripheral boards directly to the boards (see
eral board Figure 4-56 for the slip-on connectors) and route them to the MDFU
through the cable duct inside the housing.
● With an external main distribution frame (MDFU):
Use CABLU S30269-Z41-A30 (Figure 4-54) to connect the peripheral
boards to the customer’s line network. As shown in Figure 4-56, you can
connect the eight-pin slip-on connectors to the boards directly. The line
network connects directly to the jumper strip.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Not for U.S.: HiPath 3350: Connecting the Cabling

The integrated distribution frame in HiPath 3350 allows you to connect the cable network to
the trunk and the stations using screw connections on slip-on connectors. The slip-on connec-
tors (C39334-Z7089-C13) can be easily removed for easy system connection and disconnec-
tion.
The peripheral boards and optional boards contain a distribution frame component in the form
of edge connectors on the boards.
The slip-on connectors for these edge connectors are supplied with the boards.
Plug connection
to the
HiPath 3550 and
Screw con- HiPath 3350
nections to
the network
Figure 4-56 Integrated Distribution Frame - Slip-On Connector Screw Connections

If you have an external main distribution frame (MDFU), use CABLU S30269-Z41-A30
(Figure 4-54) to connect the peripheral boards to the customer’s line network. As shown in
Figure 4-56, you can connect the 8-pin slip-on connectors directly to the boards. The line net-
work connects directly to the jumper strip.
For U.S. only: HiPath 3550 and HiPath 3350: Connecting the Cabling
If the boards are not already connected to the appropriate cables leaving the system, you need
to connect them.
● The TST1 Module (HiPath 3550) connects to a customer-supplied channel service unit
(CSU) using the supplied cable. The CSU provides the required secondary protection.
● Each port on the STLS4 Module connects to an S0 bus using the supplied, silver-satin con-
nector cord and a surface-mounted RJ21X jack. The surface-mounted RJ21X jack is not
supplied.
The signals must be reversed in the RJ45X jack. See Figure 3-76.
● The board in Slot 10 of HiPath 3550 connects using a special cable from the backplane to
the main distribution frame (MDF).
● The remaining peripheral boards and options are connected by means of a mains distrib-
utor provided on the customer side or a comparable unit. This is where the MDF cables
supplied are used (Octopus cable with Amphenol terminators). You select the output pat-
tern on the Amphenol connector by which slip-on connector you use on each board edge
connector.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

● Note: The MDF cable reverses the signals coming from the board. This means that R/T on
the board interface becomes T/R on the Amphenol connector.
HiPath 3550 and HiPath 3350: connecting the LAN cable for HXGS3
LAN cables are connected to HXGS3 boards in a HiPath ... 3550 or HiPath ... 3350 according
to the description in Section 3.3.4.
● Electromagnetic shielding
To ensure sufficient electromagnetic shielding (according to EN 55022), a shielded LAN
cable must be used, or the LAN cable being used must already be shielded.
● Procedure: LAN cable shield contacts
Step Activity
1. Expose the external shield (D) by stripping the LAN cable sheath (A).
Stripped length = approx. 30 mm.
Stripped length
A B C D
2. Wrap conductive tape (C) around the exposed external shielding at least
1.5 times and use a cable binder (B) to attach it to the housing, maintaining
a continuous conducting contact between the tape and the housing (see
figure).
4.3.3.9 Attaching Ferrite

To keep within the interference limit required by EMC Class B, you must attach ferrite to the
following lines.
HiPath 3550 and HiPath 3350 power cables (wall housing)

The wall housing’s power cable must be guided through the C39022-Z7000-C7 ferrite sleeve
that is included in the accessory pack. Position the ferrite sleeve as shown in Figure 4-57 so
that you will be able to close the housing cover.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
40 +/– 5 mm min. 15 mm
Ferrite sleeve
C39022-Z7000-C7
Power cable
Figure 4-57 HiPath 3550 and HiPath 3350 - Power Cable with Ferrite Sleeve
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Digital and analog trunk and subscriber lines of the HiPath 3550 and HiPath 3350 (wall
housing)
If Then
HiPath 3550 ● Trunk or subscriber line modules in “large” format:
Guide both standard cables from SUX8 and SUX9 (see Fig. 4-55 ) to the
MDFU through two ferrite sleeves (C4-Z55-C39022) each. The ferrite
should be placed as far inside the housing as possible.
● Trunk or subscriber line modules in “small” format:
Guide the trunk and subscriber lines of all ports connected on a board
through a ferrite sleeve (C39022-Z7000-C6) twice, i.e. in a loop.
More than one trunk or subscriber line can be guided through a ferrit
sleeve. You can guide as many lines through a ferrit sleeve as long as
the ferrit sleeve can still be closed properly. These means there can be
no gap between the two ferrit halves.
The ferrit sleeves should where possible be mounted in the cable duct.
If the number of lines makes this impossible, the ferrite can be attached
directly at the output of the cable duct.
HiPath 3350 Guide the trunk and subscriber lines of all ports connected on a board
through a ferrite sleeve (C39022-Z7000-C6) twice, i.e. in a loop.
More than one trunk or subscriber line can be guided through a ferrit sleeve.
You can guide as many lines through a ferrit sleeve as long as the ferrit
sleeve can still be closed properly. These means there can be no gap be-
tween the two ferrit halves.
The ferrit sleeves should where possible be mounted in the cable duct. If the
number of lines makes this impossible, the ferrite can be attached directly at
the output of the cable duct.
If there are insufficient ferrit sleeves supplied in the accessory pack for all trunk and
> subscriber lines, additional ferrit sleeves must be ordered:
● L30460-X1358-X-* (direct sales) / L30251-U600-A229 (export): Contains 5 ferrit

sleeves C39022-Z7000-C6
● L30460-X1359-X-* (direct sales) / L30251-U600-A230 (export): Contains 9 ferrit
sleeves C39022-Z7000-C6
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.3.10 Configuration notes
Restrictions for equipment with IVMP8, IVMS8, TST1 and TS2 boards must be ob-
> served.
HiPath 3550: system overview and slots
PSU
UPS
Cable
duct
1
2
3 Optional boards
4
Slot levels 5 CUC
6
Figure 4-58 HiPath 3550 - Wall Housing System Overview
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

CUC: Connection Unit Com

OPAL
Opt.1
Slot 2
Slot 4
Slot 8
Slot 6
Opt.2
Wall
CBCC
Opt.3
Opt.4
Slot 3
Slot 5
Slot 7
Slot 9
Slot 10
Opt.5
to MDF
V.24
1 2 3 4 5 6
Slot levels
Figure 4-59 HiPath 3550 - Slots in the Wall Housing
The CBCC board is connected to

the optional board via a ribbon ca-
ble (OPAL) (see adjacent figure).
Figure 4-60 HiPath 3550 - Option Adapter Long (OPAL)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
PSU
UPS
Cable
duct
1 Optional boards
2
3
Slot levels CUP
Figure 4-61 HiPath 3350 - Wall Housing System Overview
CUP: Connection Unit Point
OPAL
Opt.1
Slot 4
Slot 2
Opt.2
CBCC
Wall
Opt.3
Opt.4
Slot 5
Slot 3
Opt.5
V.24
1 2 3
Slot levels
Figure 4-62 HiPath 3350 - Slots in the Wall Housing
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Static traffic capacity

The HiPath 3550 and HiPath 3350 systems have the following static traffic capacities.
Table 4-12 HiPath 3550 and HiPath 3350 - Static Traffic Capacity
System Slots Static traffic capac- Total static traffic capacity of

ity the system
2 / 3 (CBCC) 24 erlangs
4 16 erlangs
5 16 erlangs
HiPath 3550 6 16 erlangs
198 erlangs
(see Figure 4-59) 7 16 erlangs
8 16 erlangs
9 30 erlangs1
10 64 erlangs
2 / 3 (CBCC) 24 erlangs
HiPath 3350
4 16 erlangs 56 erlangs
(see Figure 4-62)
5 16 erlangs
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.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.3.11 Connecting Workpoint Clients

For information, see Chapter 10.
4.3.3.12 Making trunk connections

● STLS2 (not for U.S.), STLS4 (S0 trunk connection)
● TS2, HiPath 3550 only (S2M trunk connection)
● TLA2 (Not for U.S.), TLA4 (Not for U.S.), TLA8 (not for U.S.) (MSI)
● TMAMF (for selected countries only), HiPath 3550only
● TMGL4 (for U.S. only)
● TMQ4 (for U.S. only)
● TST1 (for U.S. only), HiPath 3550only
4.3.3.13 Performing a Visual Inspection

and the power supply. The visual inspection must be performed while the system is disconnect-
ed from the power supply.
Caution
7 Conduct the visual inspection only while the system is disconnected from the power
supply.
Always wear an antistatic wristband and observe the measures for protecting elec-
trostatically sensitive devices (see page 1-9).
Step Activity Resources/Remarks Possible remedies

1. Compare the slots for the Board assignment map Correct the board
installed boards with the configuration and no-
board assignment map. tify the sales depart-
ment.
2. Check the local line voltage. Digital multimeter
After finishing the visual inspection, you can begin starting up the system as de-
> scribed in Chapter 5.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.4 Installing HiPath 3500 and HiPath 3300 (19-Inch Housing)

This section contains information on how to install the HiPath 3500 and HiPath 3300 19-inch
housing. This chapter describes the standard installation procedures for the basic system. Re-
fer to Chapter 9 for information about supplementary equipment and expansions.
Danger
7 The HiPath 3500 and HiPath 3300 systems can only be operated with a closed
housing.
Before opening the housing, make sure that the system is de-energized as follows:
● Disconnect the line cord on any connected battery pack (for UPSC-DR only).
● Disconnect the line cord on any connected EPSU2-R (for UPSC-DR only).
● Disconnect the power plug.
4.3.4.1 Installation Versions

HiPath 3500 and HiPath 3300 are designed for the following three installation variants:
● Wall attachment (with assembly kit)
● Desk installation (assembly kit includes adhesive feet)
Stick the adhesive feet to the bottom of the housing.
● Installation into 19" cabinet (with assembly kits for HiPath 3500 and HiPath 3300)
You can also install an ECR expansion cabinet rack in which you can install a battery pack (for
uninterruptible power supply) and/or an additional external power supply unit EPSU3000-R (if
the system’s internal power supply is not sufficient) (see Section 9.2.4).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Selecting a site
The customer usually has a preferred installation site in mind, for example an existing 19-inch
cabinet.
● To guarantee sufficient system ventilation, allow a minimum of 10 cm clearance around the
housing.
You will find information on the design and dimensions in the following section:

The AC connection must fulfill the requirements specified in Table 4-13.
Table 4-13 Electrical Connection Values (for U.S. only)

voltage Range tions
from to from to
60 Hz wire, earth
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Procedure
Step Activity
proper departments.
Caution
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.4.4 Not for U.S.: Attaching a HiPath 3500 and HiPath 3300 to the Wall
Procedure for wall mounting (Figure 4-63)
Step Activity
1. Drill a hole in the selected wall, insert a wall anchor and screw in the screws.
2. Screw the angle brackets (A) and (B) for HiPath 3500 or HiPath 3300 onto the
base of the device.
3. Mount the system with the angle bracket (A) on the screws.
4. Drill a second hole in the wall for the lower angle bracket (B), insert a wall anchor
and attach the angle bracket with a screw.
Wall mounting
HiPath 3500 /
HiPath 3300
B
Figure 4-63 HiPath 3500 and HiPath 3300 - Wall Installation (for U.S.)
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.4.5 Installing a HiPath 3500 or HiPath 3300 in a Cabinet
Procedure for 19-inch cabinets (Figure 4-64)
Step Activity
1. HiPath 3500 only: Attach the two angle brackets (A) to the 19-inch cabinet using
two screws per bracket.
2. Attach the two angle brackets (B) to the left and right of the HiPath 3500 or HiPath
3300 using two screws per bracket.
3. Slide the HiPath 3500 or HiPath 3300 system into the 19-inch cabinet and attach
it to the left and right of the 19-inch frame with screws.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Mounting the 19-inch cabinet
B
B
HiPath 3500
Figure 4-64 HiPath 3500 and HiPath 3300 - Mounting the 19-Inch Cabinet
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm


Grounding: Inspection and Implementation
Preliminary Inspection of the 19-Inch Cabinet:

Is the 19-inch cabinet grounded NO The 19-inch cabinet must be grounded by a sepa-
by a separate ground conduc- rate ground conductor (green/yellow).
tor (green/yellow)? Danger

hered to.
YES
Does the 19-inch cabinet have NO A potential equalization bus must be installed in
a potential equalization bus the 19-inch cabinet and connected to the ground
at which the HiPath 3500 or Hi- conductor.
Path 3300 can be grounded? Danger

hered to.
YES
If you answer “Yes” to both questions, the HiPath 3500 or HiPath 3300 systems may be
grounded as described below.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Procedure: Ground the system

Proceed as follows to ground the HiPath 3500 and HiPath 3300 systems (see also diagram be-
low).
Step Activity
1. Connect the grounding cable to the potential equalization bar on the 19-inch cab-
inet.
2. Connect the grounding cable to the system’s ground connection with the ground-
ing screw supplied (point A).
3. Attach the grounding cable (strain relief) to the system (point B) with a cable tie.
HiPath 3500 and HiPath 3300 sys-

tems
A
Grounding cable B
Potential equalization bar
Figure 4-65 HiPath 3500 and HiPath 3300 - Grounding
Danger
7 The HiPath 3500 and HiPath 3300 housing to be wall-mounted must be grounded
by a separate ground conductor (such as a potential equalization bar). Make sure
that the ground conductor is securely installed and strain-relieved.
4.3.4.7 Installing the Boards

The systems are already equipped with the boards needed for the customer’s specific require-
ments.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.4.8 Connecting Cables and the Line Network

Not for U.S. and Canada: Connection cable for the expansion cabinet rack (ECR) (if
present)
To meet EMC requirements, the braided shields of the connection cable must be connected to
the housing on the HiPath 3500 or HiPath 3300 side and on the ECR side PB3000 side.
● Attaching to the HiPath 3500 or HiPath 3300 side
A clip and a tooth lock washer are enclosed with the ECR mounting set PB3000 mounting
set. Use these and the housing cover mounting screw to attach the braided shield to the
HiPath 3500 or HiPath 3300 housing (as shown in Figure 4-66). The tooth lock washer
must be mounted between the painted surface of the cover and the clip.
Housing cover mounting

screw
Clip
Tooth lock washer
Housing cover
Figure 4-66 HiPath 3500 and HiPath 3300 connection cable for the ECR PB3000
● Attachment to the EBR side PB3000 side (see Section 9.2.4)
Line network
The connecting cords to the peripherals can be connected directly to the relevant RJ45 jacks
on the front panel of the 19-inch housing.
Connecting the LAN cable for HXGR3

LAN cables are connected to HXGR3 boards in a HiPath ... 3500 or HiPath ... 3300 according
to the description in Section 3.3.4.
● Electromagnetic shielding
To ensure sufficient electromagnetic shielding (according to EN 55022), a shielded LAN
cable must be used, or the LAN cable being used must already be shielded.
● Procedure: LAN cable shield contacts
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Step Activity
1. Expose the external shield (D) by stripping the LAN cable sheath (A).
Stripped length = approx. 30 mm.
Stripped length
A B C D
2. Wrap conductive tape (C) around the exposed external shielding at least
1.5 times and use a cable binder (B) to attach it to the housing, maintaining
a continuous conducting contact between the tape and the housing (see
figure).
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

4.3.4.9 Configuration notes
Caution
7 For safety, operate HiPath 3500 only with the housing front closed. Always use dum-
my panels (C39165-A7027-B115) to close slots that are not equipped with boards.
Slot
levels:
5 (options)
Slots 1-3
4 (CBRC)
Slot 6 Slot 7 3 (Peripheralboards)
Figure 4-67 HiPath 3500 - Slot Levels in the 19-Inch Housing
It is imperative that you observe the restrictions regarding TS2R installation.

>
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
Caution
7 For safety, operate HiPath 3300 only with the housing front closed. Always use dum-
my panels (C39165-A7027-B115) to close slots that are not equipped with boards.
Slot
levels:
3 (options)
Slots 1-3
2 (CBRC)
Figure 4-68 HiPath 3300 - Slot Levels in the 19-Inch Housing
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

Static traffic capacity

The HiPath 3500 and HiPath 3300 systems have the following static traffic capacities.
Table 4-14 HiPath 3500 and HiPath 3300 - Static Traffic Capacity
System Slots Static traffic capac- Total static traffic capacity

ity of the system
2/3 (CBRC) 24 erlangs
4 16 erlangs
5 16 erlangs
HiPath 3500
(see Figure 4-67)
7 16 erlangs
8 16 erlangs
9 30 erlangs1
2/3 (CBRC) 24 erlangs
HiPath 3300
(see Figure 4-68)
5 16 erlangs
1 Use of a TS2R board results in a capacity of 30 erlangs. A maximum of one TS2R per HiPath 3500 is possible, and the
board may only be installed in slot 7 or 9, thus resulting in 30 Erlangs for slot 7 or 9.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm
4.3.4.10 Connecting Workpoint Clients

For information, see Chapter 10.
4.3.4.11 Making trunk connections

● STLS4R (S0 trunk connection)
● TS2R, only HiPath 3500 (S2M trunk connection)
● TLA4R (not for U.S.) (MSI)
● TMGL4R (for U.S. only)
● TST1 (for U.S. only), HiPath 3500 only
4.3.4.12 Performing a Visual Inspection

and the power supply. The visual inspection must be performed while the system is disconnect-
ed from the power supply.
Caution
7 Conduct the visual inspection only while the system is disconnected from the power
supply.
Always wear an antistatic wristband and observe the measures for protecting elec-
trostatically sensitive devices (see page 1-9).
Step Activity Resources/Remarks Possible remedies

1. Compare the slots for the Board assignment map Correct the board
installed boards with the configuration and no-
board assignment map. tify the sales depart-
ment.
2. Check the local line voltage. Digital multimeter
After finishing the visual inspection, you can begin starting up the system as de-
> scribed in Chapter 5.
A31003-H3570-S100-6-7620, 2008-04-01
inst_h3.fm

A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
Nur für den internen Gebrauch Starting Up HiPath 3000
Overview
5 Starting Up HiPath 3000
5.1 Overview
Chapter contents
Topic
Starting Up HiPath 3800, page 5-2
Starting Up HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300, page 5-11
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
Starting Up HiPath 3000 Nur für den internen Gebrauch

Starting Up HiPath 3800
5.2 Starting Up HiPath 3800

This section contains information on how to start up the HiPath 3800 communication system.
Warning
7 Only authorized service personnel should start up the system.
Danger
7 The system may only be started (connected to the power supply) if all system cabi-
5.2.1 Startup Procedure
Table 5-1 HiPath 3800 - Startup Procedure
Step Startup Activity (Remarks)

1. Supplying the System with Power, page 5-2
(Plugging in the power supply cable for the system cabinet(s) and positioning the
switches for all LUNA2 power supplies to “DC-ON” –> starting system boot)
2. Carrying Out a System Reload, page 5-6
3. Carrying Out the Country Initialization and Selecting the Password Type, page 5-7
4. Not for U.S.: Entering the System Number, page 5-9
5. Customer-Specific Programming, page 5-10
6. Performing a System Check, page 5-10
5.2.2 Supplying the System with Power

7 The use of the outlet strip with overvoltage protection with part number C39334-
Z7052-C31 is absolutely mandatory. The AC power of the system cabinet(s) must
be conducted through the outlet strip with overvoltage protection.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
Procedure
Step Activity
1. Plug in the power supply cable for the system cabinet(s).
Note (for Brazil only): The AC power of a system cabinet is internally equipped
with transient overvoltage protection up to approx. 2kV. Since additional lightning
protection is prescribed for Brazil, the AC power of the system cabinet(s) must be
conducted through the outlet strip with overvoltage protection (part number
C39334-Z7052-C31). In this way, transient overvoltage protection is guaranteed
up to approx. 4kV.
2. Position all LUNA2 power supply switches to “DC-ON”.
Note: Startup does not begin until the switches on all LUNA2 units are in “DC-ON”
position.
3. Monitor the RUN LED of the CBSAP. The individual steps of the system boot
(Table 5-2) can be observed this way.
RUN LED HiPath 3800

The CBSAP has a RUN LED that indicates the system status.
Table 5-2 RUN LED - LED Status Meaning
RUN LED Meaning

Off No power
Off Reset switch held down for more than 5 seconds (LED is extinguished
to acknowledge that a reload has begun)
On System boot
Off Load operation: APS in SDRAM, loadware, and card data
for 0.1 s
0.5 s on/0.5 s off
0.1 s on/0.1 s off
The HiPath 3800 is ready when the date “1. JAN 00” and the time “00:00” appear in
> the display on the system telephone.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

5.2.2.1 Assigning Station Numbers

The first time the system is initialized, the system determines its capacity and stores the result
in the CDB (customer database). After each system reset, the system accesses this data and
generates a continuous numbering plan.
If the system detects changes to the board configuration during startup, the following action is
taken:
If Then
Missing or defective board No action.
Different board type The system does not automatically activate the board.
Underequipped or same Board is activated. The same station range is used.
board variant
Over-equipped board vari- Board is activated. The old station range is activated and the
ant ports associated with the new board are inserted at the end.
The ports are split if there is no contiguous station range avail-
able.
New board in empty slot ● Board was the last one installed in accordance with the
placement sequence:
All boards are activated and the numbering plan continues
without a gap.
● Board was inserted ahead of another board in the place-
ment sequence:
Board is activated and appended to the last board in the
numbering plan.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
Procedure: Reinitialization
Proceed as follows if measures to expand the system configuration require reinitialization of the
numbering plan:
Step Activity Description

1. Disconnect the system from
the power supply. Check that
the system is de-energized.
Expand as required.
2. Connect system to power sup- A continuous numbering plan is generated (as was
ply the case when the system was first initialized).
Notes:
● Changes to the extension numbers result in
changes to the individual, extension-specific
data.
● Only those ports provided for in accordance
with the maximum configuration are activated if
the maximum line configuration is exceeded
(too many trunk boards).
● A mixture of subscriber line circuits and trunk
lines on one S0 board can result in gaps in line
numbering. This is because all S0 ports are ini-
tially activated as trunks and are only subse-
quently reconfigured.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

5.2.3 Carrying Out a System Reload

After supplying the system with power, you must carry out a system reload.
Procedure
The reset/reload switch is tested by a Field Programmable Gate Array (FPGA). This
> FPGA is loaded by the processor when starting up the HiPath 3800 and is only fully
functional after the loading process is complete. If the reset/reload switch is activat-
ed during loading, then it is not possible to evaluate the cause of the restart. For this
reason, the reset/reload switch may only be activated after the system startup (green
Run LED lights up).
Press and hold down the reset switch for at least 5 seconds (FAIL LED (red) goes out). If you
do not hold down the reset switch for a full 5 seconds, the system may perform a reset rather
than a reload or may not reload properly.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
5.2.4 Carrying Out the Country Initialization and Selecting the

Password Type
Since the system software no longer provides all languages, some systems no long-
> er start up in the customary local language after the country code is entered. You
must now load the local language prior to country initialization, using HiPath
3000/5000 Manager E (see information on multilingual text output in the Feature De-
scription HiPath 3000/5000).
After carrying out the country initialization, but before loading the required local lan-
guage, the displays come up in German.
Carry out the country initialization on the system telephone with internal station number 100
(port 01). This process loads the country-specific language and features and ensures that the
system meets the country’s conditions for approval.
In Germany, no country adaptation is required after a reload because the system boots with the
German country code by default.
The next step involves selecting the password type.
Input procedure
Table 5-3 Entering the Country Code and Selecting the Password Type
Step Input Description

1. *95 Start system administration
2. 31994 Default user name
3. 31994 Default password
4. XXXXX You are prompted to enter a new password (max. 15 digits)
5. XXXXX You are prompted to confirm the password entered in the
previous step.
6. 29-5 Country initialization
7. X You are prompted to select the password type:
1 = Variable password
2 = Fixed password
8. XX You are prompted to enter the country code (see page A-
25). The system then boots up with the country-specific de-
fault information.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

Step Input Description

Notes:
● On step 4 and step 5: If a new password is issued, both steps are omitted when calling
the system again.
● On step 6: No country adjustment is necessary for Germany because the system starts
up with German codes.
● On step 7: When selecting the fixed password, the default password (31994) overwrites
the new password entered in step 4.
Entering the country code starts the system. Any data that has already been stored, such as
system speed-dialing destinations and classes of service, is deleted or reset to the default val-
ue.
For Brazil only: CO call privileges, ringback protection per trunk

7 If the system was initialized with the country code for Brazil, the option for saving the
digits dialed and transmitting them via the system (dial rule 1A) is not activated.
This can lead to dialing problems at DTMF terminals because the system waits for
the dial tone from the analog trunk and does not set up the connection between the
DTMF terminal and the trunk until it recognizes the dial tone. Digits dialed before dial
tone recognition are therefore not recognized by the CO. This in turn can impact CO
call privileges.
To avoid this, Least Cost Routing LCR should be activated for all systems with the
country code for Brazil and with connection to analog trunks with DTMF signaling.
After you enter a country code, the default data is only guaranteed to load correctly
> if the system software has been officially released for that country.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
5.2.5 Not for U.S.: Entering the System Number
Introduction
Corresponding to the configuration, the system station number must be entered (without the
DID number or attendant code) on the system telephone that is assigned 100 as its internal
station number.
The system station number is determined by the network or service provider.
Depending on the configuration type, system station numbers should not be entered for
point-to-multipoint operation or for tie trunks to HiPath 4000, for example.
Example
Port number: 98008
National number: 2302 (prefix without 0)
International number: 49 (country code)
Station number type: international
Input procedure
Table 5-4 Entering the System Number
Step Entry Description

1. *95 System administration code
2. Service User name (identification)
3. XXXXX Enter password
4. Watch the display.
Scroll until “ISDN parameters” and “System station number”
appear.
Confirm your selection.
OR:
Expert mode: Enter the code 20 2 1 to 4.
5. Follow the user prompting on the display.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

5.2.6 Customer-Specific Programming

You can program the system using one of the following tools:
● Manager T (programming telephone, see Annex A)
● HiPath 3000/5000 Manager E (PC tool)
Changes to the system (for example key programming) made using HiPath 3000/
> 5000 Manager E during an offline programming session will be lost when the data-
base is loaded.
When you program the system offline, the assignments of trunk and subscriber ports
depend on the order in which the boards are inserted. Usually, the boards are insert-
ed from the lowest slot to the highest.
Refer to the HiPath 3000/5000 Manager E Help for information on programming individual fea-
tures.
5.2.7 Performing a System Check
Checking the telephones

● The display must be checked on every telephone. The phone number, date and time are
normally shown in the display.
If a different text appears (“Gateway not found”, for example), this means that there is an
error.
Correct the error by following the administration instructions for the relevant telephone.
● Perform random terminal tests as described in Section 12.3.2.9 on all telephones.
Checking for proper system booting

● Set up internal and external calls at random to check if the system is functioning properly.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
Starting Up HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300
5.3 Starting Up HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300
This section contains information on how to start up the HiPath 3550, HiPath 3350, HiPath
3500 and HiPath 3300 communication systems.
Warning
7 Only authorized service personnel should start up the system.
Caution
7 For safety, operate HiPath 3500 and HiPath 3300 only with the housing front closed.
Always use dummy panels (C39165-A7027-B115) to close slots that are not
equipped with boards.
5.3.1 Startup Procedure
Table 5-5 Startup Procedure
Step Startup Activity (Remarks)

1. Supplying the System With Power, page 5-12 (starting system boot).
3. Carrying Out the Country Initialization and Selecting the Password Type, page 5-
15
5. Customer-Specific Programming, page 5-18
6. Performing a System Check, page 5-18
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

5.3.2 Supplying the System With Power

Z7052-C31 is absolutely mandatory. The AC power of the system must be conduct-
ed through the outlet strip with overvoltage protection.
Procedure
Step Activity
1. Plug in the power supply cable and, where applicable, the battery cable.
Note (for Brazil only): The AC power of the HiPath 3550, HiPath 3350, HiPath
3500, and HiPath 3300 systems is internally equipped with transient overvoltage
protection up to approx. 2 kV. Since additional lightning protection is prescribed
for Brazil, the AC power of a system must be conducted through the outlet strip
with overvoltage protection (part number C39334-Z7052-C31). In this way, tran-
sient overvoltage protection is guaranteed up to approx. 4 kV.
2. Monitor the Run LED of the central controller. The individual steps of the system
boot (Table 5-6) can be observed this way.
HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300 RUN LED
The central board has a RUN LED that indicates the system status.
RUN LED Meaning

Off No power
on Reset switch pressed briefly
On System boot
Off Load operation: APS in SDRAM, loadware, and card data.
for 0.1 s
0.5 s on/0.5 s off
0.1 s on/0.1 s off
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
The system is ready when the date “1. JAN 00” and the time “00:00” appear in the
> display on the system telephone.
5.3.2.1 Assigning Station Numbers

The first time the system is initialized, the system determines its capacity and stores the result
in the CDB (customer database). After each system reset, the system accesses this data and
generates a continuous numbering plan.
If the system detects changes to the board configuration during startup, the following action is
taken:
If Then
Missing or defective board No action.
Different board type The system does not automatically activate the board.
Underequipped or same Board is activated. The same station range is used.
board variant
Over-equipped board vari- Board is activated. The old station range is activated and the
ant ports associated with the new board are inserted at the end.
The ports are split if there is no contiguous station range avail-
able.
New board in empty slot ● Board was the last one installed in accordance with the
placement sequence:
All boards are activated and the numbering plan continues
without a gap.
● Board was inserted ahead of another board in the place-
ment sequence:
Board is activated and appended to the last board in the
numbering plan.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

Procedure: Reinitialization
Proceed as follows if measures to expand the system configuration require reinitialization of the
numbering plan:
Step Activity Description

1. Disconnect the system
from the power supply.
Check that the system is
de-energized.
Expand as required.
2. Connect system to pow- A continuous numbering plan is generated (as was the
er supply case when the system was first initialized).
Notes:
● Changes to the extension numbers result in chang-
es to the individual, extension-specific data.
● Only those ports provided for in accordance with
the maximum configuration are activated if the
maximum line configuration is exceeded (too many
trunk boards).
● A mixture of subscriber line circuits and trunk lines
on one S0 board can result in gaps in line number-
ing. This is because all board ports are initially acti-
vated as trunks and are only subsequently reconfig-
ured.
● S0 station: If stations are connected to an S0 board
(S0 bus), their station numbers result from the MSN
programmed in the telephone, regardless of the
connection.
If no MSN is programmed on a telephone or if no
MSN can be programmed, the system uses a de-
fault MSN. The default MSN can be administered
by S0 port (HiPath 3000/5000 Manager E).
● The system does not assign the MSN until the S0
port is configured on the “Euro bus”; the MSN can
be read out via administration.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
5.3.3 Carrying Out a System Reload

After supplying the system with power, you must carry out a system reload. This can be per-
formed during the initial system boot.
Procedure
Press and hold down the reset switch for at least 5 seconds (RUN LED goes out). If you do not
hold down the reset switch for a full 5 seconds, the system may perform a reset rather than a
reload or may not reload properly.
5.3.4 Carrying Out the Country Initialization and Selecting the

Password Type
Since the system software no longer provides all languages, some systems no long-
> er start up in the customary local language after the country code is entered. You
must now load the local language prior to country initialization, using HiPath
3000/5000 Manager E (see information on multilingual text output in the Feature
Description HiPath 3000/5000).
After carrying out the country initialization, but before loading the required local lan-
guage, the displays come up in German.
Carry out the country initialization on the system telephone with the internal station number 100
(HiPath 3550 and HiPath 3500) or 11 for (HiPath 3350 and HiPath 3300) (port 01). This process
loads the country-specific language and features and ensures that the system meets the coun-
try’s conditions for approval.
In Germany, no country adaptation is required after a reload because the system boots with the
German country code by default.
The next step involves selecting the password type.
Input procedure

4. XXXXX You are prompted to enter a new password (max. 15 digits)
5. XXXXX You are prompted to confirm the password entered in step 4.
6. 29 - 5 Country initialization
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm


2 = Fixed password
8. XX You are prompted to enter the country code (see page A-26).
The system then boots up with the country-specific default in-
formation.
Notes:
the system again.
the new password entered under step 4.
Note
Entering the country code starts the system. Any data that has already been stored, such as
system speed-dialing destinations and classes of service, is deleted or reset to the default val-
ue.
For Brazil only: CO call privileges, ringback protection per trunk

7 If the system was initialized with the country code for Brazil, the option for saving the
digits dialed and transmitting them via the system (dial rule 1A) is not activated.
This can lead to dialing problems at DTMF terminals because the system waits for
the dial tone from the analog trunk and does not set up the connection between the
DTMF terminal and the trunk until it recognizes the dial tone. Digits dialed before dial
tone recognition are therefore not recognized by the CO. This in turn can impact CO
call privileges.
To avoid this, Least Cost Routing LCR should be activated for all systems with the
country code for Brazil and with connection to analog trunks with DTMF signaling.
After you enter a country code, the default data is only guaranteed to load correctly
> if the system software has been officially released for that country.
Table A-3, HiPath 3550, HiPath 3350 and HiPath 3500 have not been introduced in
some of the countries listed in HiPath 3300. The correct loading of the default data
is not guaranteed for those countries.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm
5.3.5 Not for U.S.: Entering the System Number
Introduction
Corresponding to the configuration, the system station number must be entered (without the
DID number or attendant code) on the system telephone that is assigned 100 as its internal
station number for HiPath 3550 and HiPath 3500 and 11 in the case of HiPath 3350 and HiPath
3300.
The system station number is determined by the network or service provider.
Depending on the configuration type, system station numbers should not be entered for
point-to-multipoint operation or for tie trunks to HiPath 4000, for example.
Example
● Port number: 98008
● National number: 2302 (prefix without 0)
● International number: 49 (country code)
● Station number type: international
Input procedure
Table 5-8 Entering the System Number

1. *95 System administration code
2. Service User name (identification)
3. XXXXX Enter password
4. Watch the display.
Scroll until “ISDN parameters” and “System station num-
ber” appear.
Confirm your selection.
OR:
Expert mode: Enter the code 20 2 1 to 4.
5. Follow the user prompting on the display.
A31003-H3570-S100-6-7620, 2008-04-01
start_h3.fm

5.3.6 Customer-Specific Programming

You can program the system using one of the following tools:
● Manager T (programming telephone, refer to Annex A)
● HiPath 3000/5000 Manager E (PC tool)
Changes to the system (for example key programming) made using during an Hi-
> Path 3000/5000 Manager E offline programming session will be lost when the data-
base is loaded.
When you program the system offline, the assignments of trunk and subscriber ports
depend on the order in which the boards are inserted. Usually, the boards are insert-
ed from the lowest slot to the highest.
Refer to the HiPath 3000/5000 Manager E Help for information on programming individual fea-
tures.
5.3.7 Performing a System Check
Checking the telephones

● The display must be checked on every telephone. The phone number, date and time are
normally shown in the display.
If a different text appears (“Gateway not found”, for example), this means that there is an
error.
● Perform random terminal tests as described in Section 12.3.2.9 on all telephones.
Checking for proper system booting

● Set up internal and external calls at random to check if the system is functioning properly.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Nur für den internen Gebrauch HiPath 5000 Startup and Administration
Overview
6 HiPath 5000 Startup and Administration
6.1 Overview
Chapter contents
Topic
Introduction, page 6-2
Software Structure, page 6-4
Notes on Open Numbering in a HiPath 3000/5000 Network, page 6-7
Installation Requirements, page 6-8
● Preparing for Installation, page 6-11
● Integrating the HiPath 5000 Server in the Customer LAN, page 6-12
● HiPath 5000 Installing Standard Components, page 6-13
● Installing HiPath ComScendo Service, page 6-21
● Installing HiPath Fault Management, page 6-30
● Installing the TAPI Service Provider, page 6-34
● Installing the HiPath Inventory Server Separately, page 6-36
● Verifying Installation, page 6-41
Modifying HiPath 5000 Components (Retro-Fitting, Updating, Deleting), page 6-43
● Version-Wide Upgrading of a HiPath 5000 Installation, page 6-44
Performing Licensing, page 6-46
Optimizing Operating System Settings, page 6-47
Perform HiPath 5000 Basic Configuration, page 6-49
● Configuring HiPath 5000 with HiPath ComScendo Service, page 6-50
● Reloading the HiPath ComScendo Service (if required), page 6-51
● Configuring HiPath 5000 RSM as a Central Admin. Unit in an IP Network, page 6-52
HiPath Manager PCM, page 6-56
GetAccount, page 6-56
● Parameters for Call Data Export, page 6-56
Connecting an Uninterruptible Power Supply to HiPath 5000, page 6-61
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000 Startup and Administration Nur für den internen Gebrauch
Introduction
6.2 Introduction
HiPath 5000 Real-Time Services Manager RSM is operated as a central administration unit in
an IP network of HiPath 3000 systems. All participating nodes can be administered from a cen-
tral point through the formation of a “single system image”.
HiPath 5000 RSM is the platform for providing applications at a central point and enables them
to be used by all stations in the IP network.
The HiPath ComScendo Service also supports the use of an integrated gatekeeper as well as
features for IP workpoint clients from HiPath ComScendo. Up to 1000 registered IP workpoint
clients and up to 250 CorNet IP lines (CorNet NQ protocol tunneled in H.323 via Annex M1) are
supported in this process.
tions, trunks, and special stations, such as, door openers, etc.), all HiPath 3000/HiPath 5000
features are available. HiPath ComScendo Service is administered via HiPath 3000/5000 Man-
ager E, while the HG 1500 resources (see the feature description) are administered via Web-
Based Management (WBM).
Cross-platform use of HiPath ComScendo features (IP networking), for example in conjunction
with HiPath 4000, is implemented via CorNet-IP (CorNet-NQ protocol tunnelled in H.323 via
annex M1). HG 1500 in HiPath 3000 and HG3550 V2.0 in HiPath 4000 are prerequisites for
IP networking over CorNet IP.
Parts of the following setup for HiPath 5000 are optional and can be installed both on the HiPath
5000 Real-Time Services Manager RSM and on a separate PC.
● Feature Server (central administration service in a HiPath 3000/5000 network)
● Presence Manager (service for LED signaling of call processing station statuses and net-
work-wide DSS keys)
● HiPath ComScendo Service (gatekeeper and HiPath ComScendo features for
IP workpoint clients)
● HiPath 3000/5000 Manager E (MS Windows-based tool for the administration of all service
and customer-specific data by Service)
● HiPath 3000/5000 Manager C (MS Windows-based tool for the administration of customer-
specific data by the customer)
● HiPath Software Manager (Web-based tool for upgrades (Upgrade Manager for HiPath
ComScendo Service and HG 1500) and backups (Backup Manager for HiPath ComScen-
do Service, HG 1500 and databases))
● Inventory Manager (service for detecting software components installed and system infor-
mation in a HiPath 3000/5000 network)
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Introduction
● 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 offline
mode)
● Personal Call Manager PCM (Web-based application for the configuration and administra-
tion of personal call forwarding operations)
● HiPath FM Desktop V3.0 (Java-based application for error signaling)
● GetAccount (application that prepares generated call data records for further processing.)
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Software Structure
6.3 Software Structure
Feature Server
The Feature Server is an essential component in the HiPath 5000 software architecture and
serves 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 data
for digit analysis in a HiPath 3000/5000 network.
The networked HiPath 3000 systems (nodes) are administered over the Feature Server. The
HiPath 3000/5000 Manager E administration tool does not communicate with the individual
systems 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 the
HiPath 5000 RSM.
Communication with the individual HiPath 3000 systems belonging to the network takes place
over their HG 1500 boards.
HiPath 3000 HiPath 3000 HiPath 3000

Node 1 Node 2 Node 3
CDB 1 CDB 2 CDB 3
HG 1500 HG 1500 HG 1500
Feature Server
CDB 1
CDB 2
CDB 3
Figure 6-1 Customer Data Exchange Between the Feature Server and Nodes
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Software Structure
The following figure shows the services and routines associated with the Feature Server.
CDB Synchronization Application Interface Call Address Resolu- HG 1500 Registration

HiPath 3000 –> server tion Update Server Server
vsync.exe vaplx.dll cars.exe regserver.exe
Server Control Layer Event Log Texts

(MS Windows Service)
VEvtLogMsg.dll
AssCkds.dll
vsrv.exe Accs520x.dll
Accs520x.dll
Accs520x.dll
Accs520x.dll
Server Database
vdbaccess.dll
Socket Interface Data Transfer Interface Remote Procedure Call

Interface
vsock.dll vadmtftp.dll FCT.dll
Figure 6-2 Feature Server Services and Routines
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Software Structure
The following table shows the most important features of the Feature Server.
Table 6-1 Feature Server Components
Component Function
vsrv.exe Basic Feature Server component. As an MS Windows service, it starts all
other components.
vaplx.dll Logical interface for applications. Provides read-only and read/write ac-
cess to CDB data.
cars.exe The Call Address Resolution Server provides the HG 1500 boards with the
call numbers of all HiPath 3000 systems (nodes) that belong to the net-
work.
Note: Event 1027 confirms that the corresponding HG 1500 board was
successfully downloaded with the call numbers of all HiPath 3000 systems
associated with the network (see Section 12.3.4).
regserv- Following startup, the HG 1500 boards automatically log on to the Feature
er.exe Server over the Registration Server.
vsync.exe All “node-specific” CDB changes (for example, by key programming, Man-
ager T) are reported by the node to the Feature Server’s VSYNC process.
This ensures the automatic synchronization of the Feature Server with the
new CDB data.
FCT.dll Interface to the systems for direct CDB data access.
Presence Manager
This is a Feature Server service for signaling the call processing station states “free”, “busy”
and “call” using the LEDs on the Optiset E and optiPoint telephones in a HiPath 3000/5000 net-
work. You can pick up a call by pressing the appropriate button.
Call processing states can only be signaled for a station if the Presence Manager can set a
CSTA monitor point on the relevant station. The status of a MULAP call number cannot be sig-
naled, for example, because a CSTA monitor point cannot be set on a call number of this type.
The dssserver.exe service for the Presence Manager is installed with the HiPath 5000 soft-
ware. This is a user-configured service that receives its information from vaplx.dll. The
TAPI Service Provider is required for the Presence Manager to work.
Note for troubleshooting and diagnosis

> The Feature Server and Presence Manager components generate entries in the
Event Viewer (event log) which are used for troubleshooting and diagnosis.
Section 12.3.4 provides information on the possible entries and any necessary user
responses.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Notes on Open Numbering in a HiPath 3000/5000 Network
6.4 Notes on Open Numbering in a HiPath 3000/5000 Network

In contrast to standalone systems, a HiPath 3000/5000 network performs call number evalua-
tion in a number of stages. All station and group numbers for the relevant HiPath 3000 systems
(nodes) are kept on the HG 1500 boards and subject to digit analysis. The Feature Server
sends the IP addresses of the relevant HiPath 3000 systems to the HG 1500 boards. The Fea-
ture Server also assigns every HG 1500 board a call number table in which all call numbers of
the other HiPath 3000 systems are saved. This means that every call number dialed can be
uniquely assigned to a node. These call number tables are also known as CAR (Call Address
Resolution) tables. The call number tables can be displayed using HG 1500’s Web-based man-
agement (WBM). Changes made to tables with the WBM can impact the digit analysis function-
ality and are not permitted. The CAR tables are updated and overwritten by the Feature Server
after every administration activity.
Internal call numbers can be assigned more than once in a network using open numbering.
However, to enable unique call number evaluation, every HiPath 3000 system is assigned a
unique node number. A station in node A always dials a station in node B by entering the node
number + internal call number.
The “Open numbering” system flag in HiPath 3000/5000 Manager E must be set for every Hi-
Path 3000 system involved. This flag must be set to permit the administration of the node num-
ber.
The node number (Settings/System parameters.../Flags: Node number) and the in-
> coming PABX number for route 16 (HG 1500 route) (Settings/Lines / networking.../
Routes: PABX number - incoming) should be identical for every HiPath 3000 system.
In V7 or later, it is possible to administer the node number of each associated HiPath 3000 sys-
tem using HiPath 3000 Manager E, regardless of the status of the system flag “Open number-
ing scheme”.
In V7 or later, the node number (Settings/System parameters.../Flags: Node number) and the
incoming PABX number for route 16 (HG 1500 route) (Settings/Lines / networking.../Routes:
PABX number - incoming) do not need to be identical. With an open numbering scheme only
the node number needs to be administered.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Installation Requirements
6.5 Installation Requirements

To use HiPath 5000, the following minimum requirements must be met:
● Hardware and software
Table 6-2 HW and SW Minimum Requirements for HiPath 5000
Component New system Upgrade an existing system

to Version 3.0
Processor 3 GHz CPU Pentium III 1 GHz
RAM space See Table 6-3 See Table 6-3
Hard disk 80 GB 18 GB
Operating system MS Windows Server 2000 or MS Windows Server 2000
MS Windows Server 2003
Interfaces 2 x serial 2 x serial
Slots free PCI slots (for S0/S2M free PCI slots (for S0/S2M
boards for HPCO and HiPath boards for HPCO and HiPath
Xpressions) Xpressions)
Drives 3.5-inch floppy disk drive 3.5-inch floppy disk drive
CD-ROM/DVD drive CD-ROM/DVD drive
Network card 10/100/1000 Mbps Ethernet net- 10/100 Mbps Ethernet network
work card card
Monitor 17-inch color monitor 17-inch color monitor
● Licenses
Information on features, interfaces, and products subject to mandatory licensing can be
found in Chapter 8, “Licensing”.
● RAM requirements of the HiPath 5000 server
Table 6-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.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Table 6-3 RAM Space of the HiPath 5000 Server
Minimum RAM
Up to Up to Up to Up to Up to
2 nodes 8 nodes 16 nodes 32 nodes 64 nodes1
HiPath 5000 V6.0 512 MB 1 GB 1 GB 1.5 GB 2 GB
+ HiPath FM V3.0
+ Teledata Office V3.0
+ HiPath Software Manag-
er
HiPath ComScendo Ser- + 100 MB + 100 MB + 100 MB + 100 MB not sup-
vice ported
HiPath Manager PCM + 90 MB + 90 MB + 90 MB + 90 MB + 90 MB
V2.0
HiPath ProCenter Office + 400 MB + 400 MB + 600 MB not sup- not sup-
V1.3 with HiPath Xpres- ported ported
sions V3.02
DLS + 250 MB + 250 MB + 250 MB + 250 MB + 250 MB
1 Networks are currently released with up to 32 nodes. Larger configurations can be released on a project-specific ba-
sis.
2 In this special configuration, HiPath Xpressions V3.0 supports up to 248 Unified Messaging users or 400 voice mail
users.
Table 6-4 shows the maximum expansion level permitted for the HiPath ComScendo Service
together with HiPath 5000 RSM (central administration unit in an IP network) and other appli-
cations on a single PC.
Table 6-4 Prerequisites for a Single-PC Solution
Upgrade V6.0 to 2 nodes1 3-6 7 - 16 17 - 32 33 - 642

V7 (3 GHz nodes1 nodes1 nodes1 nodes1
1-node system CPU) (3 GHz (3 GHz (3 GHz (3 GHz
(1 GHz CPU) CPU) CPU) CPU) CPU)
HiPath ComScendo possible possible possible not pos- not pos- not pos-
Service3 sible sible sible
HiPath 5000 RSM possible possible possible possible possible possible
(central administra-
tion unit in an IP
network)
HiPath Software possible possible possible possible possible possible
Manager
DLS3 possible possible possible possible possible possible
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Table 6-4 Prerequisites for a Single-PC Solution
Upgrade V6.0 to 2 nodes1 3-6 7 - 16 17 - 32 33 - 642

V7 (3 GHz nodes1 nodes1 nodes1 nodes1
1-node system CPU) (3 GHz (3 GHz (3 GHz (3 GHz
(1 GHz CPU) CPU) CPU) CPU) CPU)
HiPath Manager possible possible possible possible possible possible
PCM V2.0
HiPath FM possible possible possible possible possible possible
Teledata Office3 possible possible possible possible possible possible
HiPath Xpressions3 up to 248 stations up to 248 up to 248 up to 248 not pos- not pos-
possible stations stations stations sible sible
possible possible possible
1 Every HiPath 3000 gateway, every survivable media gateway, and every HiPath ComScendo service counts as a node.
2 Networks are currently released with up to 32 nodes. Larger configurations can be released on a project-specific basis.
3 We do not recommend installing DLS, Teledata Office, HiPath Xpressions, and HiPath ComScendo Service together on a
PC. Real-time operation of the HiPath ComScendo Service cannot be guaranteed if the lion’s share of processor resources
is required for DLS, Teledata Office, HiPath Xpressions. Software updates, call charge data queries, statistics, etc. must
be performed during off-peak hours when few or no calls are underway.
If the customer is unwilling to accept restrictions, HiPath ComScendo Service must be installed on a separate PC.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6 HiPath 5000
6.6.1 Preparing for Installation

To ensure successful installation, you should check the points listed in the table below before
installing the HiPath 5000 software.
Table 6-5 HiPath 5000 - Preparing for Installation
Component Description
Hard disk parti- The server PC hard disk should be divided into two NTFS partitions. The
tioning main partition C should have a capacity of at least 4 GB and should be re-
served for the operating system and the HiPath 5000 software.
For safety reasons, partitioning with the format FAT 16/32 is not permitted.
Hardware Make sure that no unnecessary hardware is connected to the server PC;
any sound cards should be removed.
Access privileg- To install HiPath 5000, you must log on to the operating system with admin-
es istrator rights or, if necessary, log on as the server domain administrator.
LAN integration Check to ensure that the server PC has been correctly integrated in the cus-
tomer LAN (see Section 6.6.2).
Miscellaneous All applications running in the background must be closed prior to software
installation.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.2 Integrating the HiPath 5000 Server in the Customer LAN
Network analysis must be performed before the relevant systems and applications
> are installed to guarantee smooth operation in the IP customer network. Network
analysis determines the conditions under which the IP customer’s network is suit-
able for a HiPath 3000/5000 network.
The data necessary for integrating the HiPath 5000 server, for example, IP address-
es, is defined as part of network analysis and in consultation with the customer (re-
quirements specifications).
The settings are made under Control Panel - Network - Protocols.
● Modify the IP address
● Adapt the subnet mask, gateway.
● Adapt the DNS entries, WINS entries.
● Once the data has been customized, a reboot is required.
● Test the LAN connection with a “ping” to another computer
● Integrate the HiPath 5000 in the Windows domain under Control Panel - Network - Identi-
fication (a domain administrator account is required here!)
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.3 HiPath 5000 Installing Standard Components
6.6.3.1 Overview
The installation program (Master Setup) enables both the basic installation of a HiPath 5000
system including middleware and components for system administration/analysis and the post-
installation of individual software components and tools (update, see Section 6.7).
HiPath ComScendo Service cannot be operated at the same time as an optiClient

> 130 on a single server.
Table 6-6 Software Components and Master Setup Tools
Component Server PC Client PC Standard component

(default setup)1
HiPath ComScendo service Yes Yes No
(see Section 6.6.4)
MSDE 2000 SQL database with SP3 Yes No Yes
TFTP Server Yes Yes Yes
Common Web Service Yes Yes Yes
HiPath Call Accounting (GetAc- yes, optional No No
count) (see Section 6.12)
HiPath Manager PCM yes, optional network-based No
release (see Section 6.11)
HiPath 3000/5000 Manager E Yes Yes Yes
HiPath 3000/5000 Manager C yes, optional No No
HiPath Inventory Yes Yes Yes
(see Section 6.6.7)
HiPath Software Manager Yes No Yes
Feature Server, Presence Manager Yes No Yes
2
HiPath Fault Management Yes Yes No
(see Section 6.6.5)
Customer License Agent CLA Yes yes Yes
(MS Windows
2000 Pro. or later)
Customer License Manager CLM yes, optional No No
1 Standard components should generally always be installed and are therefore already selected in the master setup
(= default setup).
2 Refer to current information in HiPath Fault Management release documentation.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
HiPath ComScendo Service cannot be operated at the same time as an optiClient

> 130 on a single PC.
6.6.3.2 Licensing
Please refer to Chapter 8, “Licensing” for information on how to proceed.
A grace period of 30 days begins after startup. Licensing must be performed for all features,
interfaces, and products subject to mandatory licensing within this grace period.
HiPath 3000/5000 Manager E comes with a customer-specific file which is used by the Cus-
tomer License Agent CLA to generate a GPCF (Grace Period Configuration File) file. This file
ensures that the maximum expansion of all features subject to mandatory licensing is possible
within the 30-day grace period. The system or systems are not licensed.
The system falls into licensing default if licensing is not performed within the 30-day grace pe-
riod. This means that features which subject to mandatory licensing will suffer from reduced
functionality.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.3.3 Starting the Installation

A TAPI service provider must be installed on the relevant PC to enable the default setup to be
performed. Installation information can be found in Section 6.6.6.
Procedure
1. Insert the installation CD.
The installation program is started via the autorun function. Alternatively you can initiate
Setup via Windows Explorer under <CD-ROM drive letter>:\setup.exe.
2. Select the language you require for the Setup browser. German (Germany) and English
(USA) versions are currently available.
The system is prepared for installation.
3. Click Next to start the installation routine.
Important installation information is displayed.
This includes the latest information on installation. Please read this information carefully.
4. Click Next to proceed with the installation routine.
5. Select destination path.
Select the folder where you want to install the program.
Confirm the default folder c:\program files\siemens\hipath\ with Next or click
Browse and select a different folder.
6. Select program folder.
Select the location where the setup should create the new shortcuts.
Confirm the default folder HiPath with Next or select a different folder.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
7. The Select Features dialog appears.
Mark the components you want to install and unmark the ones you don’t.
The components marked by default (Default Setup) are standard components

> that as a rule should always be installed. For information on the exact compo-
nents to install, refer to your order.
The subsequent description of the installation procedure relates to the default
setup.
Information on installing the HiPath ComScendo Service can be found in
Section 6.6.4.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
8. Then click Next.
At this point your attention is drawn to the fact that a TAPI service provider must
> be installed for the current selection of components.
If this requirement is met, click Yes to continue with the procedure.
If there is no TAPI service provider installed, click No to cancel the procedure.
Install the TAPI service provider on the basis of the information in Section 6.6.6.
Then restart the master setup.
The Start Copying Files dialog appears.
Check if the correct destination directory and program group are specified and if all neces-
sary components are installed.
9. Click Next to start the copy operation.
The PC reboots after installing the MSDE 2000 SQL database.

> The installation procedure is automatically continued after rebooting.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
10. The File Transfer Folder appears.
Select the folder where you want to install the files.

Confirm the default folder c:\program files\siemens\hipath\tftp\files\ with
Next or click Change to select a different folder.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
11. Click Next to proceed with the setup routine.

The Trap Destinations and Communities dialog appears.
Enter the trap destinations (if necessary) and the HiPath Fault Management desktop com-
munity names.
The FM Reporting Client does not have its own user interface. The trap destina-
> tions and community names defined during installation may only be changed by
uninstalling and then reinstalling the FM Reporting Client.
Users with sufficient knowledge of SNMP can change trap destinations and
community names by editing the file snmpd.cnf (see Annex E).
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000

The User Configuration dialog appears.
Configure the user account for the license agents (Customer License Agent CLA).
14. When all selected components are installed, a dialog appears in which you can terminate
the setup with Finish.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.4 Installing HiPath ComScendo Service

tions, trunks, and special stations, such as, door openers, etc.), all HiPath 3000/HiPath 5000
features are available. HiPath ComScendo Service is administered via HiPath 3000/5000 Man-
ager E, while the HG 1500 resources (see the feature description) are administered via Web-
Based Management (WBM).
The HiPath ComScendo service is not a standard component (default setup) of the master set-
up. For this reason, the procedure for a separate installation will be described here.
Procedure
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
Select the HiPath ComScendo Service components you want to install and deselect the
ones you do not want to install.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
8. Then click Next.

Finally, check whether the correct target directory and program group have been specified.
To implement the setup for the HiPath ComScendo service, both a TFTP server and an FM
Reporting client must be installed on the relevant PC. Both components are automatically
selected and installed by the Master Setup.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
9. Click Next to start the copy procedure.

The File Transfer Folder appears.
Note: This dialog only appears if none of the Master Setup components has been installed
on the PC.

Confirm the default folder c:\program files\siemens\hipath\tftp\files\ with
Next or click Change to select a different folder.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000

Note: This dialog only appears if none of the Master Setup components has been installed
on the PC.
munity names.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
11. Continue setup with Next.

The Select Network Card dialog appears.
Note: This dialog only appears if the relevant PC has more than one network card.
Select the network card for HiPath 5000.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
12. Continue setup with Next.

The Country selection dialog appears.
Confirm the default or select a different country to define the international standard settings
for language, currency and date format.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000

The Destination Folder for Data dialog appears.
Select the folder for the HiPath ComScendo service data.

Confirm the default folder c:\program files\siemens\hipath\hipath
5000\pcsdata\ with Next or click Change to select a different folder.
14. When all selected components are installed, a dialog appears in which you can terminate
the installation with Finish.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.4.1 Checking the Installation of the HiPath ComScendo Service
Procedure
1. Open the status display with Start/Program Files/HiPath/HiPath 5000 State
Viewer.
2. The following appears:
Make sure that the server status is “Running” and that all service status indicators are
green.
Section 12.3.2.11 contains information about how to proceed in the event of a

> fault, in other words if one or more service status indicators are red.
Details about configuring the HiPath ComScendo service can be found in Section 6.10.1.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.5 Installing HiPath Fault Management

HiPath Fault Management can read information from the HiPath 3000 and HiPath 5000 system
MIB 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.
Procedure
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
Select the HiPath Fault Management components you want to install and deselect the
ones you do not want to install.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
8. Then click Next.

9. Click Next to start the copy procedure.
The software license agreement is displayed. The license terms must be accepted before
continuing with the setup.
10. Confirm the license agreement with Yes.
11. The Choose Destination Location dialog appears.
Select the folder where you want to install the Java Runtime Environment.
Confirm the default folder c:\program files\javasoft\jre\<version>\ with
Next or click Browse and select a different folder.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
12. The Select Browser dialog appears.

Select one of the available browsers for which the Java plugin is to be used as the standard
runtime environment for Java.
13. Confirm your selection with Next.
The InstallShield Wizard for HiPath Fault Management is started.
The licensing conditions for HiPath Fault Management are displayed. The license
terms must be accepted before continuing with the installation.
Click I accept the terms of the license agreement.
The installation options are displayed.
Select the Server & Client option.
16. Continue installation with Next.
The Directory Name dialog is displayed.
Confirm the name suggested with Next or click Browse to select a different directory.
17. Once installation is complete, a final dialog appears. Close the InstallShield Wizard for Hi-
Path Fault Management with Finish.
18. A message appears indicating that the master setup has been successful. Close the setup
with Finish.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.6 Installing the TAPI Service Provider

This section describes the separate installation of the TAPI 170 Service Provider.
You will find detailed information on how to install and configure the individual installation com-
ponents in the online help for the TAPI 170 Service Provider.
1. Insert the TAPI 170 Service Provider installation CD and run Setup.
2. Confirm the welcome dialog by clicking Next.
3. The Setup Type dialog appears. The following options are available:
● Standalone
For using the TAPI Service Provider in standalone scenarios with no more than one
HiPath 3000 system.
● AllServe
For using the TAPI Service Provider in networked HiPath AllServe scenarios.
● HiPath 3000/5000 V4.0
For using the TAPI Service Provider in networked HiPath 3000/5000 scenarios in V4.0
and later.
● User-defined
In this case you can manually select the components to be installed.
When you select the setup types Standalone, AllServe and HiPath 3000/5000 V4.0, the re-
quired installation components are automatically preselected.
Setup type Installation component

TAPI Service CSTA Mes- CSTA Service Dongle driver1 Central Config-
Provider TSP sage Dispatch- Provider CSP uration Manag-
er CMD er Client CCMC
Standalone X – – – –
AllServe X – – – X
HiPath 3000/ X X X – X
5000 V4.0
1 The dongle driver is only relevant to installations for which a dongle is used for licensing. When reinstalling TAPI 170
Version 2.0 or later, MAC IDs and license codes are used for the licensing procedure. The dongle driver is therefore
not required.
4. Select the appropriate option and confirm with Next.

5. The system starts to install the selected components.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
At the beginning of the installation routine (the precise time will depend on the
> installation components you selected), a dialog is displayed prompting you to
enable ACD support. Confirm this prompt with Yes.
The relevant ACD support utility can also be enabled or disabled at a later stage.
For further information, please refer to the online help for the TAPI 170 Service
Provider.
When a component is successfully installed, the associated configuration dialog opens.
You can set the required parameters here or postpone configuration until a later time.
6. When all of the selected components have been installed, a final dialog is displayed in
which you can conclude installation with Finish.
The TAPI Service Provider is now installed.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.7 Installing the HiPath Inventory Server Separately

The software components and tools of the master setup mentioned in Table 6-6 can be installed
on several PCs. In such a scenario the Inventory Server should be installed on all PCs that are
to support the HiPath Inventory Manager.
Procedure
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
Select the HiPath Inventory components you want to install and deselect the ones you do
not want to install.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
8. Then click Next.

To be able to implement the setup for HiPath Inventory, both an FM Reporting client and a
Common Web Service must be installed on the relevant PC. Both components are auto-
matically selected and installed by the Master Setup.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
9. Click Next to start the copy operation.

munity names.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000

The Inventory Database Location dialog appears.
Enter the IP address and the port number of the PC where the database is installed (MSDE
SQL database server).
11. Confirm your entries with Next.
12. When installation is complete, a dialog appears in which you can terminate the setup with
Finish.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.8 Verifying Installation

Computer Management can be used to verify that all components are correctly installed. This
is included in NT-based operating system packages (MS Windows NT, MS Windows 2000,
MS Windows XP, etc.).
To start this component, select Settings - Control Panel - Administrative Tools
- Computer Management.
This program is a sophisticated desktop tool for performing remote maintenance on computers.
Possible actions include the following:
● monitoring system events, for example, logon times and application errors.
● creating and managing releases
● starting and ending system services, for example task schedulers and spoolers.
● defining properties for memory devices
● displaying device configurations and adding new device drivers
● administering server applications and services, for example, DNS (Domain Name System)
or DHCP (Dynamic Host Configuration Protocol).
Computer Management is displayed in a separate window, like Windows Explorer. The console
structure (for the navigation and service program selection) contains the system programs,
data memory, services, and applications available on the computer. The right pane - the event
area - shows the tool’s attributes and data as well as any subordinate tools available.
Administrator user rights are required to use the full range of Computer Management
> functions.
Working with Computer Management requires an appropriate level of familiarity with
the operating system.
6.6.8.1 Verifying the Start and Function of HiPath 5000 Services

Select Computer Management - Services and Applications - Services to check
if all necessary services were started.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath 5000
6.6.8.2 Checking Entries in the Event Viewer

The Event Viewer (event log) provides status information on the HiPath 5000 server and any
application servers available.
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.).
To open the Event Viewer, select Computer Management - System Tools - Event
Viewer.
For more information, see Section 12.3.2.10, “Event Viewer for HiPath 5000 (Eventlog)”.
Table 12-8 shows the possible entries that may appear in the Event Viewer.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Modifying HiPath 5000 Components (Retro-Fitting, Updating, Deleting)
6.7 Modifying HiPath 5000 Components (Retro-Fitting, Updating,

Deleting)
The Setup maintenance program can be used for
● retro-fitting additional components (features) to the current HiPath 5000 installation.
● updating components (features) in the current HiPath 5000 installation,
Note: When upgrading from one version to another (from V6.0 to V7.0, for example, all
components (features) must first be uninstalled. The components from the new version can
then be installed (for more information, refer to Section 6.7.1).
● deleting all components (features) of the current HiPath 5000 installation.
When activated, the Setup creates the relevant selection lists based on the current HiPath 5000
installation.
The WinAccount software for evaluating call data records is no longer used in HiPath
> 3000/5000 V4.0 or later.
Call data records must be evaluated with WinAccount before starting an update be-
cause updating uninstalls the WinAccount application.
Refer to the WinAccount user manual for information about the procedure
Before starting the Setup maintenance program, note the following information:
7 ● The TAPI Service Provider configuration (configuration and lines - see TAPI 170
Service Provider Help) and the CDB files for all connected systems (refer to Hi-
Path 3000/5000 Manager E Help) should be saved for security reasons.
● The HiPath 5000 server must be stopped (Start/Programs/HiPath/Hi-
Path 5000 State Viewer, Stop Server button).
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
6.7.1 Version-Wide Upgrading of a HiPath 5000 Installation
When upgrading from one version to another (from V6.0 to V7.0, for example), all
> components (features) must first be uninstalled. The components of the new version
can then be installed.
1. Save the current TAPI service provider configuration (configuration and lines - see TAPI
170 Service Provider Help).
2. Save the current CDB files of all connected systems (see HiPath 3000/5000 Manager E
Help).
3. Call up the HiPath 5000 State Viewer with Start/Programs/HiPath/HiPath 5000
State Viewer.
4. Exit the HiPath 5000 server by clicking Stop Server.
6. Select the language you require for the Setup browser.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
7. The Setup maintenance program appears.
Select the option Remove.

8. Then click Next.
9. Confirm the deletion of all installed components (features).
Follow the on-screen user prompts.
10. Delete the following directories (default paths are provided):
c:\Program Files\Microsoft SQL Server\MSSQL\
C:\Program Files\Siemens\HiPath\DB Feature Server\
C:\Program Files\Siemens\HiPath\HiPath5000\
Note: As these directories are not installed via Master Setup, it is not possible to delete
them via the setup maintenance program.
11. Install the components (features) for the new version (refer to the instructions in
Section 6.6.3).
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Performing Licensing
6.8 Performing Licensing

Version 5.0 and later features a new, centralized licensing procedure, called HiPath License
Management. The procedure is used in all HiPath products, for example communication sys-
tems, workpoint clients, and applications.
A grace period of 30 days begins when HiPath 5000 is started up. Licensing must be performed
for all features, interfaces, and products subject to mandatory licensing within this grace period.
HiPath 3000/5000 Manager E comes with a customer-specific file which is used by the Cus-
tomer License Agent CLA to generate a GPCF (Grace Period Configuration File) file. This file
ensures that the maximum expansion of all features subject to mandatory licensing is possible
within the 30-day grace period. The system or systems are not licensed.
functionality.
Please refer to Chapter 8, “Licensing” for information on how to proceed.

>
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Optimizing Operating System Settings
6.9 Optimizing Operating System Settings

This section describes how you can optimize the Windows 2000 Server operating system for
the implementation of HiPath 5000.
No information is available on how to optimize Windows Server 2003.
Table 6-7 Operating System Settings for HiPath 5000
Optimizing the physical Windows 2000 Server is normally optimized for maximum through-
memory put as a file server. For a HiPath 5000 server, however, significantly
less memory is needed for the system-wide disk cache.
For this select the Balance Load option under Start/Settings/
Network and DC Connections/LAN Connection: Proper-
ties – File and Printer Sharing for Microsoft Net-
works: Properties
Optimizing the virtual To optimize the virtual memory, enter 512 MB as the Total paging
memory file size for all drives under Start/Settings/Control Panel/
System: Advanced – Performance Settings: Virtual
Memory: Change.
The same values should be entered for the virtual memory’s upper
and lower thresholds so that the paging file does not have to be ex-
tended during operation.
Optimizing availability If the operating system crashes (blue screen), it creates a file con-
taining debugging information from the paging file the next time the
system starts. If the size of this file is the same size as the system’s
physical memory, almost all of the virtual memory will be used for
generating this file during system startup.
This may cause certain services on the HiPath 5000 server to expe-
rience problems in starting up. To recover this problem, you should
go to Start/Settings/Control Panel – System – Advanced
– Startup and Recovery and select the option none under Write De-
bugging Information.
All other options are viable. The Auto restart option forces an auto-
matic restart in the event of a system crash, thus considerably in-
creasing the server’s availability.
SMTP service The operating system’s SMTP service should always be disabled as
HiPath 5000 provides its own SMTP link which may conflict with the
operating system’s service. To do this, go to Start/Settings/
Control Panel: Software – Add/Remove Windows Com-
ponents : Internet Information Service (IIS) – De-
tails: Remove SMTP Service.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Optimizing Operating System Settings
Table 6-7 Operating System Settings for HiPath 5000
Personal Call Manager and Internet Information Server
The Personal Call Manager software runs within the context of the
IIS user. When a Windows Server system is being installed for the
first time, it must be taken into account that the default security set-
tings for the wwwroot directory do not always grant the Personal
Call Manager the necessary access rights.
You must ensure that the user account used by the Personal Call
Manager (account for “anonymous access” on the standard website
- by default this is the IIS guest account IUSR_<PC name>) has full
access to the wwwroott\PCM directory.
The PCM requires the following local full access rights to the hard
disk: C:\temp and C:\InetPub\wwwroot\PCM\ where C:\In-
etPub\wwwroot means the standard directory of the IIS (in other
installations this may have a completely different name).
The option “Cache ISAPI Applications” must not be disabled. This
option can be found under Standard website – Properties – Home
Directory – Configuration – Application Mapping.
If the option were disabled, the Personal Call Manger would lose its
“memory” of the users currently logged on and the error message
“You are not logged on” would be displayed permanently ...”.
Application protocol Configure the following by right-clicking Properties under System
Log and Application Log in the operating system’s Event Viewer:
'Overwrite events as needed' and set 'Maximum log size' to approxi-
mately 2 MB.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Perform HiPath 5000 Basic Configuration
6.10 Perform HiPath 5000 Basic Configuration

A distinction should be drawn between the basic configuration of a
● HiPath 5000 PC with HiPath ComScendo service
The HiPath ComScendo Service is a complete HiPath 3000 node that is only configured
as software on a PC. Apart from the pure TDM features, all features of HiPath 3000/HiPath
5000 are available.
HiPath ComScendo Service is administered via HiPath 3000/5000 Manager E, while the
HG 1500 resources (see the feature description) are administered via Web-Based Man-
agement (WBM).
● HiPath 5000 RSM as central administration unit in an IP network, with or without HiPath
ComScendo Service .The formation of a “single system image” allows the central admin-
istration of all associated nodes (HiPath 3000 and HiPath 5000 with HiPath ComScendo
Service).
The IP network is administered via the Feature server. The HiPath 3000/5000 Manager E
administration tool does not communicate with the individual nodes but exchanges data
with the Feature server. The Feature server ensures that the networked nodes receive syn-
chronized CDB data. The Feature Server is an MS Windows service that automatically
starts at the same time as the HiPath 5000 RSM.
HG 1500 boards are still administered on a board-specific basis using Web-based man-
agement (WBM).
The administration of IP networking with HiPath 3000/5000 Manager E is divided into the
following steps:
a) Configuring the individual nodes belonging to the network (HiPath 3000 and HiPath
5000 with HiPath ComScendo Service) = Configuration of the individual customer da-
tabases.
b) Configuring the Feature server = Create an empty server net file.
c) Start data transfer = registration of the individual nodes and transfer of the node data
to the server net file.
d) Transfer the central database for IP networking = Load the server net file to the Fea-
ture server. The customer database is then automatically distributed to the various
nodes.
Future administrative node work is then performed by the server.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
6.10.1 Configuring HiPath 5000 with HiPath ComScendo Service

The customer database must be loaded to enable the individual IP workpoint clients, trunks,
etc. to be configured.
Procedure
1. StartHiPath 3000/5000 Manager E.
2. Open the Transfer dialog using the File menu.
3. In the Communication Settings tab select IP-HiPath as the access and enter the IP ad-
dress of the HiPath 5000 with HiPath ComScendo Service in the appropriate field.
Select Read/Write CDB and load the customer database by clicking the System -> PC
button.
During the first login, the system requests the identity of the user and asks for a
> new password (for more information see Section 12.6.1.3, “Logon With User
Name and Password”).
4. Perform the customer-specific system programming.
Refer to the HiPath 3000/5000 Manager E Help for information on programming individual
features.
5. Save the customer database.
6. Then switch to the Transfer dialog.
7. In the Communication Settings tab select IP-HiPath as the access and enter the IP ad-
dress of the HiPath 5000 with HiPath ComScendo Service in the appropriate field.
Select Read/Write Database. Set the Overwrite and Hardware flags and transfer the cus-
tomer database by clicking the PC –> System button.
Once transfer is complete, HiPath 5000 automatically performs a reset and then returns to
operation.
The HG 1500 resources (see the feature description) are administered using Web-
> Based Management (WBM). Information about the procedure can be found in the
Web-based Management WBM Help.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
6.10.2 Reloading the HiPath ComScendo Service (if required)

Reloading the HiPath ComScendo Service means deleting the files hicom.pds and hi-
com.pds.bak.
These files contain the complete data description of the HiPath 5000 with emulated HG 1500
boards. This includes:
● customer data
● trace
● error history
● call charge data
● status data
The directory in which the two PDS files are to be stored is defined when the HiPath 5000 soft-
ware is installed (setup). The two PDS files are created when the HiPath 5000 is started for the
first time.
The PDS files must not be modified, as reading of the files using conventional tools
> and interpretation of the content is not possible without specialist knowledge.
Procedure
1. Call up the HiPath 5000 State Viewer with Start/Programs/HiPath/HiPath 5000
State Viewer.
2. Exit the HiPath 5000 server by clicking Stop Server.
3. Delete the files hicom.pds and hicom.pds.bak.
Note: This restores the default settings for the entire content of the customer database. All
country and customer-specific settings are lost.
4. Start the HiPath 5000 server by clicking Start Server in the HiPath 5000 State Viewer.
When operating correctly, the server state is shown as “Running”; “status indicators are green”
is shown for all services.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
6.10.3 Configuring HiPath 5000 RSM as a Central Admin. Unit in an IP

Network
The IP network is administered via the Feature server. The HiPath 3000/5000 Manager E ad-
ministration tool does not communicate with the individual nodes but exchanges data with the
Feature server. The Feature server ensures that the networked nodes receive synchronized
CDB data. To facilitate this, a central customer database, the so called server net file, must be
created for IP networking.
6.10.3.1 Creating a Central Customer Database for IP Networking

An empty server net file must be created in order to create a central customer database for IP
networking.
Procedure
1. StartHiPath 3000/5000 Manager E.
2. Activate the HiPath 5000 RSM/AllServe server by selecting File - HiPath 5000 RSM/
AllServe - Transfer or via the appropriate button in the toolbar.
The menu item File - HiPath 5000 RSM/AllServe - New - HiPath 5000 RSM/
> AllServe Server is only used to create a CDB memory generated offline.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
3. The Transfer (HiPath 5000 RSM/AllServe Server) dialog appears.
4. The PC to be used as the HiPath 5000 server should be entered in the Server field.
Note: If the required software is not installed on the specified PC, the error message “Hi-
Path 5000 RSM/AllServe Server not Installed on this PC” appears.
5. Click Server –> Manager to create an empty server net file.
6. Then click Close.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
6.10.3.2 Adding Individual Nodes for IP Networking

The next steps in creating a central database for IP Networking are the registration of the indi-
vidual nodes and the transfer of the node data to the server net file. The server net file is now
loaded to the Feature server. The customer database is then automatically distributed to the
various nodes.
The prerequisite for adding nodes (HiPath 3000) to a HiPath 3000/5000 network is the suc-
cessful installation (see Chapter 4, “Installing HiPath 3000”) and startup (see Chapter 5,
“Starting Up HiPath 3000”) of these systems.
Procedure
1. To select the node to be added to the CDB, call File - HiPath 5000 RSM/AllServe - New
- HiPath 3000.
2. The Enter Source dialog appears.
3. Select the appropriate source:

● Customer database file (to open a saved CDB file)
In this case, select the appropriate CDB file in the Open customer database dialog
displayed.
● Create offline (to create a CDB generated offline)
In this case, define the new CDB in the Enter node data dialog displayed. You must
then configure customer-specific data.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
● Load from system (to load a CDB directly from a node)

In this case, select the HiPath 3000 node with the CDB that is to be loaded from the
subsequent Transfer (Communication) dialog that appears. You must then start the
transfer (system -> PC).
If the Copy netwide data in node option is activated, the service and substitution codes
are copied from the CDB firstly created to all other CDB files of the node belonging to IP
networking.
4. Clicking Finish opens the Transfer... dialog. Here, specify the node whose data should be
read.
5. To add the node, invoke File - HiPath 5000 RSM/AllServe - Transfer - HiPath 5000 RSM/
AllServe Server.
6. The Transfer (HiPath 5000 RSM/AllServe Server) dialog appears.
Apply the node data to the server net file by clicking the Add node button.
The number of nodes loaded during previous actions is displayed.
7. Finally, rewrite the data from HiPath 3000/5000 Manager E to the HiPath 5000 server
(Manager –> Server button).
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
HiPath Manager PCM
Refer to the Help for HiPath 3000/5000 Manager E for additional information about
> the procedure.
6.11 HiPath Manager PCM

For information, see the HiPath Manager PCM Installation and Administration Manual.
6.12 GetAccount
Overview
The call data records generated during HiPath 3000/5000 operation can be copied to a text file
for further processing using the GetAccount program.
The WinAccount software for evaluating call data records is no longer used in Hi-
> Path 3000/5000 V4.0 or later.
6.12.1 Parameters for Call Data Export

For HiPath 5000, you can forward the existing call data, for example, for external call charge
calculation. The call data is forwarding in an ASCII file.
Proceed as follows to set the parameters for call data export:
1. Start the GetAccount Administration program.
The following dialog appears.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
GetAccount
2. Enter the following data:
Field name Meaning

Mode Select the call data forwarding mode in this list field. The
following modes are available:
● None save call charge data
The call data is not written to the transfer file. Select
this option.
● Save call charge data
The call data is written to the transfer file.
The modes Export calls with calculation and Export and
save calls with calculation are intended for a future ex-
pansion.
Transfer file Confirm the default file name (gcallserve) or enter a
different file name.
Transfer file folder Confirm the default folder name (C:\coldir) or enter a
different folder name.
The transfer file is stored in the folder set here.
3. Click Save to save your inputs.
The changes you made only become effective after the GetAccount service is restarted.
The ASCII transfer file is automatically saved in the specified folder and extended to in-
clude the new call data. The file is extended by one line for each call data record. Each call
data record (line) is ended with CR+LF.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
GetAccount
Data record structure
Table 6-8 GetAccount - Data Record Structure
No. Pos. Lengt Description

h
1 1-8 8 Date of call end
Format DD.MM.YY, for example “13.09.00”
2 9 - 16 8 Time of call end
Format hh:mm:ss, for example “14:14:00”
3 17 - 19 3 Trunk number
right-aligned with leading blanks, for example “ 1”
4 20 - 22 3 Node ID for HiPath 3000 (matches the configuration in HiPath 3000/
5000 Manager E)
right-aligned with leading blanks
5 23 - 28 6 Internal extension number
6 29 - 33 5 Call duration in seconds
7 34 - 41 8 Call duration
Format hh:mm:ss, for example “00:04:34”
8 42 - 66 25 ● For incoming calls: external caller number
● For outgoing calls: external call number dialed including the call-
by-call number
left-aligned with succeeding blanks
9 67 - 77 11 Number of tariff units
10 78 1 Call type
● 1: incoming
● 2: outgoing (default)
11 79 - 89 11 Account code ACCT
left-aligned with succeeding blanks
12 90 - 100 11 MSN used
13 101 - 5 Trunk
105 right-aligned with leading blanks
14 106 - 4 LCR Selected Route (corresponds to configuration in HiPath 3000/
109 5000 Manager E)
15 110 1 CR
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
GetAccount
Table 6-8 GetAccount - Data Record Structure
No. Pos. Lengt Description

h
16 111 1 LF
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
GetAccount
Copying/renaming the transfer files

Proceed as follows if you want to use the call information in the transfer file for external pro-
cessing:
● Switch to the folder containing the transfer file (default:
C:\coldir).
● Rename the transfer file (default: gcallserve). The renamed file is now available for ex-
ternal processing.
● The transfer file is automatically recreated in the specified folder with the file name saved
in the parameters and can be renamed again at a later point.
To avoid uncontrolled folder growth with the transfer file, an option is available for
> deleting the renamed transfer file after forwarding it for external use in this folder.
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Connecting an Uninterruptible Power Supply to HiPath 5000
6.13 Connecting an Uninterruptible Power Supply to HiPath 5000

Online’s P 500 uninterruptible power supply (UPS) was certified for use with HiPath 5000.
The P 500 UPS is fed through the AC power cord to the HiPath 5000 server. The device bridg-
es power failures lasting 5 - 10 minutes by means of an integrated battery.
Caution
7 For safety reasons and for protection against guarantee claims, changes to the UPS
settings may only be performed by specially trained technicians.
The manufacturer’s safety and operating instructions must be observed.
P 500 UPS - Front and Rear Panel
1 2 3 4 5 6
Figure 6-3 P 500 UPS - Front and Rear Panel
A31003-H3570-S100-6-7620, 2008-04-01
start_h5.fm
Connecting an Uninterruptible Power Supply to HiPath 5000
P 500 UPS - Meaning of Displays, Switches and Jacks
Table 6-9 P 500 UPS - Meaning of Displays, Switches and Jacks
No. Description
1 LED displays the status of the P 500 UPS.
● green = input voltage (line voltage) is functioning
● red = UPS is suppling voltage or fault has been detected
2 Display shows UPS operating status
● NORMAL
● CHARG‘G
● BATTERY
and reports the charging status of the battery (25, 50, 75 or 100%).
3 On/off switch
4 Input (jack for input voltage (line voltage))
There is a cavity under the jack for the input fuse (with spare fuse enclosed).
5 3-pin DIP-FIX switch:
● 1: reduces the response voltage (minimum line voltage value before UPS activa-
tion)
– 10 V with 220/240-V systems
– 5 V with 110/120-V systems.
● 2: increases the response voltage by 5%
● 3: reduces the response voltage by 5%
Switch positions normally: DIP FIX 1 = off, DIP FIX 2 and 3 = on
6 Reset key
● deactivates the acoustic alarm if the input voltage fails, that is, when using the UPS.
This alarm cannot be deactivated if the battery voltage falls under a certain value.
● activates the UPS cold start.
To protect the battery from deep discharging, the UPS can only be activated when
the line voltage is connected. By activating the “on” switch (1) and then pressing the
reset key, the P 500 UPS can also be activated without a network connection (cold
start).
The connected server must be disconnected before a cold start.
The P 500 UPS needs between 5 and 20 s to reach the set output voltage. To avoid
malfunctions the connected server should not be connected immediately.
7 9-pin jack for connection to the communication server
NOT USED IN HiPath 3000/5000.
Special monitoring software can shut down the specified server via this jack, for exam-
ple, in the case of extended power failures.
8 Jacks for power supply to the communication server to be monitored.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm
Nur für den internen Gebrauch Starting HiPath 3000 as a Gateway
Overview
7 Starting HiPath 3000 as a Gateway
7.1 Overview
Chapter contents
Topic
Starting HiPath 3800 as a Gateway, page 7-2
7.2 Introduction
So-called gateways provide the HiPath 5000 with interfaces for trunk and tie trunk connections
to the telecommunications network. In HiPath 3000 Version 3.0, the HiPath 3800, HiPath 3500,
and HiPath 3300 systems can be used as gateways.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm
Starting HiPath 3000 as a Gateway Nur für den internen Gebrauch

Starting HiPath 3800 as a Gateway
7.3 Starting HiPath 3800 as a Gateway
7.3.1 Prerequisites
Warning
Refer to Section 4.2.1 for information on the tools and resources needed to install the HiPath
3800 system.
7.3.2 Procedure for Installation and Startup
To ensure that IP addresses are not assigned more than once in the customer net-
> work, you must ping each new IP address to be configured before each IP address
is assigned. If an IP address responds, then this address cannot be used again.

Z7052-C31 is absolutely mandatory. The AC power of the system cabinet(s) must
be conducted through the outlet strip with overvoltage protection.
Table 7-1 HiPath 3800 as a GW, Procedure for System Installation and Startup
Step Activity (Remarks)

Installing HiPath 3800 (19-Inch Cabinet)
1. Selecting the Installation Site, page 4-20 (generally determined by the existing 19-
inch cabinet)
2. Unpacking the Components, page 4-23
3. Mounting System Cabinets in the 19-Inch Cabinet, page 4-24
4. Grounding the System, page 4-27
Checking the Grounding, page 4-30
5. Connecting the Cable to the Backplane, page 4-51
6. If required: Inserting the External Patch Panel, page 4-66
7. Loading the System Software and Installing Subboards on the CBSAP, page 4-81
8. Installing Boards (Configuration Notes), page 4-31 (cabinet(s) are already
equipped with the boards)
We recommend that you check the board population using the configuration notes.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm

9. Making trunk connections
● STMD3 - for S0 trunk connection
● DIUN2 - for S2M trunk connection
● DIU2U (for U.S. only) - for T1 PRI trunk
10. Making IP connections
Perform the IP connection over the HG 1500 board, STMI2.
For information on configuration, refer to the HG 1500 Administration Manual .
Startup of HiPath 3800 (Section 5.2)
1. Supplying the System with Power, page 5-2
(Plugging in the system cabinet(s) -> starting system boot)
Note (for Brazil only): The AC power of a system cabinet is internally equipped with
transient overvoltage protection up to approx. 2kV. Since additional lightning pro-
tection is prescribed for Brazil, the AC power of the system cabinet(s) must be con-
ducted through the outlet strip with overvoltage protection (part number C39334-
Z7052-C31). In this way, transient overvoltage protection is guaranteed up to ap-
prox. 4 kV.
5. Conducting customer-specific programming with HiPath 3000/5000 Manager E.
Refer to the HiPath 3000/5000 Manager E Help for information on programming in-
dividual features.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm


6. Performing a system check
● The following tests must be performed if telephones are directly connected to
the gateway:
– Check the telephones
Check the time and date display on each telephone. If a display does not
appear, either the telephone or the link is defective. Replace the terminal
or fix the link.
Perform random terminal tests as described in Section 12.3.2.9 on all tele-
phones.
– Check for proper system booting
Set up internal and external calls at random to check if the system is func-
tioning properly.
● Test IP configuration
Ping the HG 1500 IP address in the gateway.
Set up external calls at random (from optiPoints or optiClients on HiPath 5000).
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm
7.4.1 Prerequisites
Warning
3500 system.


HiPath 3500 Installation (19-Inch Cabinet) (Section 4.3)
1. Selecting the Installation Site, page 4-111 (usually predetermined)
3. Not for U.S.: Attaching a HiPath 3500 and HiPath 3300 to the Wall, page 4-113
4. Installing a HiPath 3500 or HiPath 3300 in a Cabinet, page 4-114
6. Connecting Cables and the Line Network, page 4-118
7. Configuration notes, page 4-120
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm


● STLS4R - for S0 trunk connection
● TS2R - for the S2M trunk connection
● TST1 (for U.S. only) - for T1 PRI trunk
Note: Analog workpoint clients can be connected to the CBRC’s T/R ports in emer-
gencies. This ensures telephone operation via the telecommunications network in
the event of IP network failure.
Perform the IP connection over the HG 1500 board, HXGR3.
For information onconfiguration, refer to the HG 1500 Administration Manual .
Note (for Brazil only): The AC power of the system is internally equipped with tran-
sient overvoltage protection up to approx. 2 kV. Since additional lightning protection
is prescribed for Brazil, the AC power of the system must be conducted through the
outlet strip with overvoltage protection (part number C39334-Z7052-C31). In this
way, transient overvoltage protection is guaranteed up to approx. 4 kV.
dividual features.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm

the gateway:
or fix the link.
phones.
tioning properly.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm

7.5.1 Prerequisites
Warning
3300 system.


HiPath 3300 Installation (19-Inch Cabinet) (Section 4.3)
1. Selecting the Installation Site, page 4-111 (usually predetermined)
3. Not for U.S.: Attaching a HiPath 3500 and HiPath 3300 to the Wall, page 4-113
4. Installing a HiPath 3500 or HiPath 3300 in a Cabinet, page 4-114
6. Connecting Cables and the Line Network, page 4-118
7. Configuration notes, page 4-120
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm

● STLS4R - for S0 trunk connection
Note: Analog workpoint clients can be connected to the CBRC’s T/R ports in emer-
gencies. This ensures telephone operation via the telecommunications network in
the event of IP network failure.
Perform the IP connection over the HG 1500 board, HXGR3.
For information onconfiguration, refer to the HG 1500 Administration Manual .
Note (for Brazil only): The AC power of the system is internally equipped with tran-
sient overvoltage protection up to approx. 2 kV. Since additional lightning protection
is prescribed for Brazil, the AC power of the system must be conducted through the
outlet strip with overvoltage protection (part number C39334-Z7052-C31). In this
way, transient overvoltage protection is guaranteed up to approx. 4 kV.
dividual features.
A31003-H3570-S100-6-7620, 2008-04-01
start_3g.fm


the gateway:
or fix the link.
phones.
tioning properly.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Nur für den internen Gebrauch Licensing
Overview
8 Licensing
8.1 Overview
Chapter contents
Topic
Licensing for HiPath 3000 Version 3.0, HiPath 5000 Version 3.0, page 8-4
● Products and Components subject to Mandatory Licensing, page 8-4
● Grace Period, page 8-7
● License Failure Period, page 8-7
● Performing Licensing, page 8-8
Licensing Scenarios, page 8-13
● HiPath 3000 as a Standalone System, page 8-13
● Networked HiPath 3000 Systems without HiPath 5000 RSM, page 8-15
● Networked HiPath 3000 Systems with HiPath 5000 RSM, page 8-15
● Upgrading to HiPath 3000 Version 3.0, HiPath 5000 Version 3.0, page 8-18
● Combining Standalone Systems (HiPath 3000) to Form a Network with HiPath 5000 RSM,
page 8-21
● Removing a Standalone System from a Network with HiPath 5000 RSM, page 8-23
● Replacing License-sensitive Hardware (Changing the MAC Address), page 8-24
Section 8.5, “Licensing optiClient Attendant”
● optiClient Attendant V8 Connected To HiPath 3000 V7, page 8-27
Protection Against License Manipulation, page 8-29
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Nur für den internen Gebrauch

Introduction
8.2 Introduction
Versions 5.0 and later of HiPath 3000 and HiPath 5000 use a new, centralized licensing proce-
dure known as HiPath License Management. 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
to uniquely identify the product configuration for which the relevant license file is to be supplied
in encrypted format. The license file contains the licenses for all products which are subject to
mandatory licensing.
The CLM is responsible for activating the license file and allocating it to the Customer License
Agent (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.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Introduction
1. License file is requested

using customer-specific License Management System
data Central License Server CLS
https://www.central-license-server.com/
2. License file (*.xml) is 2. License file (*.xml) is

downloaded using CLM downloaded without
CLM (license file is
stored manually in the
import directory)
Customer License
Manager (CLM)
or
3. License file is activated
Customer License Customer License Client

Agent (CLA) (CLC)
6. Individual licenses are
for exampleHiPath 3000/ distributed to all products
4. License file is validated 5000 Manager E which are subject to man-
datory licensing
5. License file is analyzed
Figure 8-1 Licensing Process with Central License Server (CLS)
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing for HiPath 3000 Version 3.0, HiPath 5000 Version 3.0
8.3 Licensing for HiPath 3000 Version 3.0, HiPath 5000 Version 3.0
8.3.1 Products and Components subject to Mandatory Licensing

The following products and components used with HiPath 3000 and HiPath 5000 V7 must be
licensed (i.e. are subject to mandatory licensing). The required licenses are combined in a li-
cense file and must be distributed to the relevant products using HiPath 3000/5000 Manager E.
Table 8-1 Features Subject to Mandatory Licensing
Feature sub- Details in license file Default values in Distribution of Licenses with
ject to man- unlicensed state HiPath 3000/5000 Manager E
datory li- Feature Maxi- Mini- During After Net- Per board Per boards
censing name mum mum grace grace work port/ per
number number period period -wide per system
device
HiPath Com- HiPath 3000 2000 0 2000 0 – HiPath – –
Scendo li- V7 Com- 3000: 500
censes (sys- Scendo IP per Gate-
tem clients, Workpoint keeper
H.323 clients, HiPath 3000 HiPath
SIP clients) V7 Com- 5000: 1000
Scendo Se- per Gate-
curity keeper
HiPath 5000 HiPath 3000 1 0 1 0 X – – X
V7 basic V7 Central
package, incl. Admin
administra- H5000
tion, IP net-
working, SN-
MP, PCM
S2M license HiPath 3000 8960 0 8960 TS2/ – TS2/TS2R: – –
for 1 B chan- V7 B chan- TS2R: 2 0 - 28 li-
nel for V7 nel S2M per board censes per
(TS2, TS2R, DIUN2: 2 port
DIUN2) licenses DIUN2: 0 -
port 1, 0 28 licens-
licenses es port 1, 0
port 2 - 30 licens-
es port 2
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

datory li-
Feature Maxi- Mini- During After Net- Per board Per boards
censing
name mum mum grace grace work port/ per
device
HG 1500 V3.0 HiPath 3000 2000 0 2000 2 – 58 per – –
expansion B V7 B chan- HG 1500
channels for nel HG1500 board
V7 V7 Com-
Scendo Se-
curity
Xpressions HiPath 3000 1024 0 1024 0 – Max. 16 – –
Compact An- V7 Xpres- per IVM
nouncements sions Com- board
for V7 pact An-
nouncement
BS4 B chan- HiPath 3000 6420 0 6420 2 B chan- – – 0 - 10 –
nel for V7 (Hi- V7 BS4 nels per licens-
Path Cordless channel One li- BS4 es per
Office) cense = port
one regis-
tration
HG 1500 V3.0 HiPath 3000 1 0 1 0 – Only on – –
VPN (Virtual V7 LWCA one
Private Net- HG 1500 HG 1500
work) LWCA board
package for
HiPath 3000
V7
optiClient At- HiPath 3000 16 0 16 0 – – – Max.
tendant V8 for V7 optiCli- 16 on a
HiPath 3000 ent Atten- central
V7 dant V8 board
optiClient At- HiPath 3000 16 0 16 0 – – – Max.
tendant V8 V7 optiCli- 16 on a
upgrade for ent Atten- central
V7.0 for Hi- dant V8 board
Path 3000
Xpressions HiPath 3000 6 0 6 0 – 6 – –
Compact Mo- V7 Xpres-
bility for Hi- sions Com-
Path 3000 V7 pact Mobility
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm


datory li-
Feature Maxi- Mini- During After Net- Per board Per boards
censing
name mum mum grace grace work port/ per
device
Mobility Entry HiPath 3000 50 0 50 0 – – – X
system li- V7 System
cense for Hi- Mobility En-
Path 3000 V7 try
The following features which are subject to mandatory licensing are licensed using separate
license files:
● VPN Workpoint Clients
● CSTA Service Provider (CSP)
● TAPI Service Provider (TSP)
● HiPath Fault Management
Information on the licensing procedure can be found in the appropriate product documentation.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
8.3.2 Grace Period

A product-specific Grace Period Configuration File (<file name>.gpcf) is installed with Hi-
Path 3000/5000 Manager E. If there is no valid license file (Real License File RLF) for the Cus-
tomer License Agent CLA when the HiPath 3000/5000 Manager E-license dialog is opened,
the CLA automatically generates a grace period license file using the .gpcf file. The grace pe-
riod licenses can be distributed in exactly the same way as RLF licenses. The only difference
is that the validity period of the grace period license is limited to 30 days.
The .gpcf file ensures that the maximum expansion of all features that are subject to mandatory
licensing is possible within the 30-day grace period. The system or systems are not licensed.
The.gpcf file must be stored in the HiPath 3000/5000 Manager E installation directory.
The 30-day grace period begins with the licensing of a standalone system or networked sys-
tems using the .gpcf file. The licensing of all features, interfaces, and products that are subject
to mandatory licensing must take place during this period.
functionality.
The activation of a grace period is recorded by the Customer License Agent (CLA) and in the
system CDB. This ensures that the 30-day period cannot be extended and that a second grace
period cannot be started.
8.3.3 License Failure Period

If a licensing error occurs, there is a period of 30 days (License Failure Period), within which
the error must be rectified.
If the error has not been rectified by the time the 30-day license failure period has expired, the
systems enter system default mode. This means that features which subject to mandatory li-
censing will suffer from reduced functionality.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

8.3.4 Performing Licensing
The details specified below are based on the assumption that valid license files are
> available to the user.
During installation of the Customer License Agent CLA on the service PC or on the HiPath 5000
server (see Figure 8-2), an import subdirectory is created in the installation directory.
If the user has received a valid license file (<license>.xml), there are two options:
● The license file can be stored manually in the specified subdirectory import.
● The Customer License Manager CLM can be activated and used to make the license file
automatically available for the CLA. Information about this can be found in the Customer
License Manager online help.
The license file in XML format contains information about all products that are subject to man-
datory licensing and the MAC address with which these licenses are linked. Feature IDs define
the number of licenses available and the length of time for which they are valid. A signature
ensures that subsequent manipulation of the license file content is always detected. Invalid
changes to the license file are therefore not possible.
Distribution of the licenses to the relevant features, interfaces, and products is performed using
HiPath 3000/5000 Manager E.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Standalone HiPath 3000 system Networked HiPath 3000 systems

with HiPath 5000 RSM
License file (*.xml)
Validation, decryption, and

analysis of the license file
Service PC
with
– HiPath 3000/5000 Manager E HiPath 5000 RSM
– Customer License Agent (CLA) with
– Customer License Client (CLC) – HiPath 3000/5000 Manager E
– Customer License Agent (CLA)
– Customer License Client (CLC)
Customer data-
base CDB with li-
Customer database
censes
CDB with licenses
HiPath 3750
In the case of networked HiPath 3000 sys-

tems without HiPath 5000 RSM, a separate
license file must be requested for each sys-
tem.
Networked HiPath 3000 systems
Figure 8-2 Distribution of Licenses with HiPath 3000/5000 Manager E
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Procedure for distributing licenses

The license distribution procedure described below requires successful installation (see
Chapter 4, “Installing HiPath 3000”) and startup (see Chapter 5, “Starting Up HiPath
3000”) of the HiPath 3000 systems (nodes) and, if available, of the HiPath 5000 RSM (see
Chapter 6, “HiPath 5000 Startup and Administration”).

Standalone or networked HiPath 3000 Networked HiPath 3000 systems with
systems without HiPath 5000 RSM HiPath 5000 RSM
1. Download and save the available CDB for Download and save the available CDB for
the HiPath 3000 to be licensed using Hi- the HiPath 5000 RSM to be licensed us-
Path 3000/5000 Manager E. ing HiPath 3000/5000 Manager E.
2. Open the “Licensing...” dialog in the “Settings” menu.
The Customer License Agent (CLA) installed on the PC opens the license file that
corresponds to the MAC address.
● Licenses: The content of the license ● Licenses: The content of the license
file is displayed. file is displayed.
In a configuration without HiPath In a network with HiPath 5000 RSM,
5000 RSM, these are the licenses for these are the licenses for the server
the open CDB and the corresponding CDB and all of the nodes (HiPath
node (HiPath 3000). 3000) belonging to the network.
Note: When a single CDB is downloaded
from a HiPath 3000/5000 network, only
the license-sensitive CDB content is dis-
played. It is not possible to make any
changes.
– Feature: All features, interfaces, and products which are subject to manda-
tory licensing are displayed.
– Available: The number of licenses purchased for the feature in question is
specified.
– Used: The number of licenses already assigned for the feature in question is
specified. The number of available licenses not yet assigned is the difference
between this number and the number specified under “Number”.
– Expiration date: If licenses are only available for a specific time, the date on
which they expire is specified here.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

● CDB: The license-sensitive data for the open CDB is displayed. You can specify
which data you want to display in the tabs “HXG” (HG 1500 boards HXGM3,
HXGS3, HXGR3, STMI2), “S2M” (S2M boards TS2, TS2R, DIUN2), “IVM” (Hi-
Path Xpressions Compact boards IVML8, IVML24, IVMN8, IVMNL, IVMP8,
IVMP8R, IVMS8, IVMS8R), “Base station” (HiPath Cordless Office base station
BS4), and “System-wide” (the licenses assigned for the system-wide feature
“DBFS” are displayed; no changes can be made.
– Type - Slot: The board type and the slot in which the board is inserted are
displayed.
– Port: The board port used is displayed.
– Feature: The features, interfaces, and products which are subject to manda-
tory licensing are displayed.
– Assigned: The number of licenses assigned for this feature is specified.
– Base: The default value for each feature is displayed.
– Expiration date: The date displayed here specifies when the validity of the
licenses assigned for this feature is due to expire.
For “Base station” tab only:
– Type - Slot - Port: The board type, the slot in which the board is inserted, and
the board port used are displayed.
– BS Type: The base station type is displayed.
– Name: The name of the base station is displayed.
Note: If the right license is not available, only the license-sensitive CDB content is dis-
played. It is not possible to make any changes.
3. Distribute licenses.
You can select the features to be licensed (features, interfaces, and products) in the
“HXG”, “S2M”, “IVM” and “Base station” tabs.
Distribute the licenses defined in the license file to the individual features.
Note that in a network with HiPath 5000 RSM, these are the licenses for all of the
nodes (HiPath 3000) belonging to the network.
Note: The DBFS network-wide feature that may be included is automatically trans-
ferred to the CDB when the licensing dialog is started.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm


4. Save CDB and transfer to HiPath 3000. Save CDB and transfer to HiPath 5000
RSM. The server transfers the CDB files
to the networked systems autonomously.
The HG 1500 boards are then registered
automatically.
Note: Unlike previous versions, this ver-
sion does not require a reset of the
HG 1500 boards. A reset should therefore
not be carried out. as it may disrupt data
transfer.
Note on licensing the Feature Server

> The Feature Server can be started without a license. In this case a message indicat-
ing that licensing needs to be performed is displayed.
Given that the Feature Server receives its license from the CDB of the first node, the
licensing dialog for this node must be opened first and, as a minimum requirement,
licensing must be performed using a .gcpf file. The first node must then be added to
the HiPath 3000/5000 network. The Feature Server now has its (grace period) li-
cense.
If the Feature Server is not licensed through the first node within one hour, the server
automatically stops operating after an hour has elapsed. When the server is restart-
ed there is a new one-hour period in which to perform licensing.
Preconfiguration can be performed in preparation for installation of a HiPath 3000/
5000 network for a customer. Licensing is required for the network at the preconfig-
uration stage. If there is no valid license file available, licensing can also be per-
formed using a GPCF file.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios
8.4 Licensing Scenarios
During production, the HiPath 3000 control boards are assigned a board-specific
> number with a MAC address that is unique worldwide. To guarantee unique licens-
ing, the license file is linked to the MAC address of a HiPath 3000 control board. The
various licensing scenarios are described below.
8.4.1 HiPath 3000 as a Standalone System

The components for this system which require licensing are licensed using one license file. This
file is linked with the MAC address of the HiPath 3000 control board.
Procedure

1. HiPath 3000/5000 Manager E (In cases where the MAC address is not already
available):
Determine the MAC address of the control board of the HiPath 3000 system requiring
licensing.
2. HiPath License Management:
Invoke the Central License Server CLS via:
Select the language version for the License Management Center.
Log on by entering the user name and password.
3. Activate the “Generate and Download License Key” function under “Management of
Available Licenses”.
Various search criteria is displayed for activating the available licenses.
4. In the “LAC” input field, enter the part number and the packing slip number (separated
by a dash).
Click Search to display a list of the features which are subject to mandatory licensing
and for which licenses are available.
5. From this list, select the features which are subject to mandatory licensing and which
you want to generate a license.
Activate the Generate Key button.
In the subsequent dialog, define the number of licenses to be generated and specify
the MAC address to which the license should be linked.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios

6. In the “MAC Address” input field, enter the MAC address for the HiPath 3000 control
board as specified in step 1.
In the “Number” field, define the number of licenses to be generated for each feature.
Click Next.
7. The customer and the user (contact partner) specified for this transaction are dis-
played.
If there are still no entries available, these can be selected using the search mask for
companies and the search mask for users.
Click Next.
8. Before generating a license key, the following content of the displayed dialog must be
observed:
● Legal notice: The licensing conditions must be accepted.
● Notes: Notes on the generation procedure can be entered here. A distinction is
made here between internal notes (only accessible to users authorized to create
licenses) and customer notes (generally accessible).
● Registered company and user: Company and user-specific data is displayed.
● Technical specifications: MAC address of the HiPath 3000 control board.
● Licenses to be used: The outcome of the generation procedure is displayed.
Click the Execute button. A new license key is generated.
9. After successful execution, the message “License Key Generation Complete” ap-
pears The generation information and license key data is displayed.
Click License Key.
10. Details on the selected license key are displayed:
● “Display” tab: Type and number of licensed features, customer-specific informa-
tion.
● “Transactions” tab: Actions performed for each feature
11. Select Download.
In the subsequent dialog, specify the storage location for the license key you want to
download.
Section 8.3.4 describes the procedure for distributing licenses with HiPath 3000/5000
Manager E.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios
8.4.2 Networked HiPath 3000 Systems without HiPath 5000 RSM

Licensing of the components which are subject to mandatory licensing is performed on a sys-
tem-wide basis. This means that a separate license file must be requested for each system.
This file is linked with the MAC address of the control board belonging to the relevant system.
The procedure for generating the various license keys is the same as that in Section 8.4.1.
8.4.3 Networked HiPath 3000 Systems with HiPath 5000 RSM

Licensing of the components which are subject to mandatory licensing is performed on a net-
work-wide basis. This means that a single license file is required for the entire HiPath 3000/
5000 network. This file is linked with the MAC address of the HiPath 3000 control board with
the lowest node number (node ID).
When a single CDB is downloaded from a HiPath 3000/5000 network, only the li-
> cense-sensitive CDB content is displayed. It is not possible to make any changes.
A cyclic check carried out every 24 hours guarantees continuous protection against manipula-
tion. Each node belonging to the network sends a request to the Feature Server to verify wheth-
er the license is still valid. The time at which the daily check takes place depends on the time
at which licensing takes place. The time of the daily check is redefined with each system reset.
Example: Licensing takes place at 5:00 p.m. Based on the 24-hour cycle, this means that the
licensing check begins at 5:00 p.m. every day.
A system reset is performed at 10:00 p.m. The time of the daily check is redefined as a result.
The licensing check begins at 10:00 p.m. every day with immediate effect.
Each additional reset results in the time of the daily check being redefined.
The system distinguishes between the following two types of error:
● The Feature Server is unable to reach the first node needed for licensing. The 30-day Li-
cense Failure Period begins.
● A standalone HiPath 3000 system (node) is unable to reach the Feature Server. The 30-
day License Failure Period begins.
If the error is rectified within 30 days, the system(s) revert(s) to the licensed state. If the error
has not been rectified by the time the 30-day license failure period has expired, the systems
enter system default mode. This means that features which subject to mandatory licensing will
suffer from reduced functionality.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios
Procedure

1. HiPath 3000/5000 Manager E (In cases where the MAC address is not already
available):
The MAC address of the HiPath 3000 system control board with the lowest node
number (node ID) should be determined.
3. Activate the “Generate and Download License Key” function under “Management of
Available Licenses”.
Various search criteria is displayed for activating the available licenses.
4. In the “LAC” input field, enter the part number and the packing slip number (separated
by a dash).
Click Search to display a list of the features which are subject to mandatory licensing
and for which licenses are available.
5. From this list, select the features which are subject to mandatory licensing and which
you want to generate a license.
Activate the Generate Key button.
In the subsequent dialog, define the number of licenses to be generated and specify
the MAC address to which the license should be linked.
6. In the “MAC Address” input field, enter the MAC address for the HiPath 3000 control
board as specified in step 1.
In the “Number” field, define the number of licenses to be generated for each feature.
Click Next.
7. The customer and the user (contact partner) specified for this transaction are dis-
played.
If there are still no entries available, these can be selected using the search mask for
companies and the search mask for users.
Click Next.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios

8. Before generating a license key, the following content of the displayed dialog must be
observed:
● Notes: Notes on the generation procedure can be entered here. A distinction is
made here between internal notes (only accessible to users authorized to create
licenses) and customer notes (generally accessible).
● Technical specifications: MAC address of the HiPath 3000 control board.
● Licenses to be used: The outcome of the generation procedure is displayed.
Click License Key.
10. Details on the selected license key are displayed:
tion.
download.
Manager E.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios
8.4.4 Upgrading to HiPath 3000 Version 3.0, HiPath 5000 Version 3.0
To upgrade from a version earlier than 5.0 to HiPath 3000 Version 3.0 or HiPath 5000 Version
3.0, you must request a new license file and repeat the licensing procedure.
The Central License Server (CLS) enables the old licenses (< V5.0) to be converted into new
licenses that are valid for version 6.0.
The following features that are subject to mandatory licensing are converted:
● HG 1500 B channels (previous designation: max. no. of B channels)
● HiPath ComScendo licenses (previous designation: max. no. of workpoint clients)
● IP Sec
● CA functionality
● Feature Server (previous designation: HiPath 5000 RSM)
Features that were not previously subject to mandatory licensing cannot be migrated. The base
station BS4 is a new product. DIUN2 (S30810-Q2196-X), TS2 (S30810-Q2913-X300) and
TS2R (S30810-K2913-Z300) are new boards. Up to now, no license was required for the IVM
announcement feature. These features are released with the maximum configuration following
an upgrade.
● BS4 (number of B channels per BS4)
● DIUN2, TS2, TS2R (number of B channels per port)
● IVM announcements (IVM boards, number of B channels per port)
Procedure

1. Web-based Management (WBM) (in the event that the MAC addresses are not
already available):
Determine the MAC addresses (locking IDs) of all HG 1500 boards belonging to the
HiPath 3000 system to be upgraded.
If this involves the networking of several HiPath 3000 systems, then the MAC ad-
dresses (locking IDs) of all available HG 1500 boards are to be determined.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios

2. HiPath 3000/5000 Manager E (In cases where the MAC addresses are not al-
ready available.):
A single HiPath 3000 system or several Upgrading involves several networked Hi-
networked HiPath 3000 systems must be Path 3000 systems with HiPath 5000
upgraded without HiPath 5000 RSM: RSM:
The MAC address of the associated con- The MAC address of the control board is
trol board should be determined for every to be determined solely for the HiPath
system. 3000 system with the lowest node number
(node ID).
4. Activate the “View Used Licenses and Certificates” function under “Management of
Used Licenses”.
Different search criteria are displayed in order to invoke the licenses to be converted
(B channels of HG 1500 boards.)
5. The MAC address (locking ID) of a HG 1500 board determined under step 1 should
be entered in the Locking ID input field.
Click the Search button to display a list of the licenses belonging to the MAC address
(locking ID).
6. Click the Show Details button.
Details on the selected license key are displayed:
tion.
7. Click Upgrade License.
Specify the upgrade path in the subsequent dialog.
8. Use the upgrade path selection list to define the required upgrade (for example, HG1
500 -> HiPath 3000 Version 3.0).
Click Next.
In the subsequent dialog, define the MAC address to which the new license should
be linked.
9. The MAC address of the HiPath 3000 control board to which the HG 1500 board
specified under step 5 belongs should be entered in the MAC Address input field.
Click Next.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios

10. Before upgrading a license key, the following content of the displayed dialog must be
observed:
● Notes: Notes on this procedure can be entered here. A distinction is made here
between internal notes (only accessible to users authorized to create licenses)
and customer notes (generally accessible).
● Upgrade details: MAC address of the HiPath 3000 control board.
● Licenses to be used: The outcome of this procedure is displayed.
Example:
HG 1500 V2 & V3:
– 6 features (Licenses) will be upgraded as a result of this transaction.
– 6 features (Licenses) will be disabled as a result of this transaction.
This means that all six available licenses have been linked with the new MAC ad-
dress. The old link with the HG 1500 board MAC address (Locking ID) was dis-
abled for all six licenses.
Click the Execute button. The license key is upgraded.
pears The upgrade information and the information about the license key will be dis-
played.
Note: The number of pre-installed HG 1500-B channels is no longer displayed, nut
only the effective total for the released licenses.
12. Upgrading involves either a single HiPath Upgrading involves several networked Hi-
3000 system or several networked sys- Path 3000systems with HiPath 5000
tems without HiPath 5000 RSM: RSM:
Repeat steps 4 to 11 for all available Repeat steps 4 to 11 for all available
HG 1500 boards. HG 1500 boards.
Note: The new licensing applies on a sys- Note: New licenses apply to the entire
tem-by-system basis. A separate license network. In other words, a single license
key is generated for each HiPath 3000 key is generated for the entire HiPath
system. 3000/5000 network. This file is linked with
the MAC address of the HiPath 3000 con-
trol board with the lowest node number
(node ID).
13. Open the License Management Center home page.
Used Licenses”.
Various search criteria are displayed for calling the recently upgraded license key.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios

15. In the “Locking ID” input field, enter the control board MAC address to which the li-
cense key is linked (see step 6).
Click the Search button to display a list of the license keys belonging to the MAC ad-
dress.
16. Select the relevant license key and click the Display Details button.
tion.
download.
Manager E.
8.4.5 Combining Standalone Systems (HiPath 3000) to Form a Network

with HiPath 5000 RSM
Only one license file is required if combining multiple standalone systems to create a network
with HiPath 5000 RSM.
The “Rehost” function of the Central License Servers (CLS) enables the various license files to
be converted into a new, network-wide overall license file. This file is linked with the MAC ad-
dress of the HiPath 3000 control board with the lowest node number (node ID).
Procedure

1. HiPath 3000/5000 Manager E (In cases where the MAC addresses are not al-
ready available.):
The MAC address of the associated control board should be determined for every Hi-
Path 3000 system.
The new network-wide overall license file is linked to the MAC address of the HiPath
3000 system with the lowest node number (node ID).
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios

3. Call the “Rehost Licenses” function under “Management of Used Licenses”.
Different search criteria are displayed in order to call up the licenses to be converted.
4. The MAC address of a HiPath 3000 control board determined under step 1 should be
entered in the Locking ID input field.
Click Search to show the licenses belonging to the MAC address.
5. Activate the Rehost button.
be linked.
6. The MAC address of the control board whose HiPath 3000 system has the lowest
node number (node ID) should be entered in the MAC address input field.
Click Next.
7. Before you start to generate a new license key, note the following content of the mask
displayed:
● Rehost details: MAC address of the HiPath 3000 control board.
Example:
HG 1500 V2 & V3:
dress. The old link with the HG 1500 board MAC address (Locking ID) was dis-
abled for all six licenses.
9. Steps 4 to 8 should be repeated for all HiPath 3000 systems.
Note: New licenses apply to the entire network. In other words, a single license key
is generated for the entire HiPath 3000/5000 network. This file is linked with the MAC
address of the HiPath 3000 control board with the lowest node number (node ID).
Used Licenses”.
Various search criteria are displayed for invoking the generated license key.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios

dress.
tion.
download.
Manager E.
8.4.6 Removing a Standalone System from a Network with HiPath 5000

RSM
If a standalone node (HiPath 3000) is to be removed from a network with HiPath 5000 RSM, a
new license file is required for the standalone system. A new, network-wide general license file
must also be requested for the rest of the network.
This function can only be triggered via User Support. User Support can split the contents of ex-
isting license files and distribute the licenses to other individual MAC addresses.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios
8.4.7 Replacing License-sensitive Hardware (Changing the MAC

Address)
A new license file is always required if you replace a license-sensitive HiPath 3000 control
board due to a hardware defect. In this case, the MAC address changes and the license be-
comes invalid.
The “Rehost” function of the Central License Server (CLS) enables the licenses to be moved
from the old MAC address (the old HiPath 3000 control board to be replaced) to a new MAC
address (a new HiPath 3000 control board).
Procedure

2. Call the “Rehost Licenses” function under “Management of Used Licenses”.
Different search criteria are displayed in order to call up the licenses to be converted.
3. Enter the MAC address of the HiPath 3000 control board to be replaced (defective)
in the Locking ID input field.
Click Search to show the licenses belonging to the MAC address.
4. Activate the Rehost button.
be linked.
5. In the “MAC Address” input field, enter the MAC address for the new control board.
Click Next.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing Scenarios

6. Before you start to generate a new license key, note the following content of the mask
displayed:
● Rehost details: MAC address of the HiPath 3000 control board.
Example:
HG 1500 V2 & V3:
dress. The old link to the MAC address of the defective HiPath 3000 control
board has been deactivated for all six licenses.
Used Licenses”.
Various search criteria are displayed for invoking the generated license key.
dress.
tion.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing Scenarios

download.
Manager E.
Note on Replacing the HiPath 3000 Control Board:

> When the control board has been successfully replaced, the CDB must be trans-
ferred to HiPath 3000. A warning will appear that the MAC address is invalid. All li-
censes become invalid if the CDB is installed. The system goes into default and fea-
tures that are subject to mandatory licensing will suffer from reduced functionality.
The new license key (see step 12) must be used to achieve valid licensing.
Section 8.3.4 describes the procedure for distributing licenses with HiPath 3000/
5000 Manager E.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Licensing optiClient Attendant
8.5 Licensing optiClient Attendant

In optiClient Attendant, licensing is performed via HiPath License Management.
The following order items are available:
1. optiClient Attendant V8 full version
2. optiClient Attendant upgrade from V7.0 to V8
optiClient Attendant V8 only operates in conjunction with HiPath 3000 V7 and HiPath 2000 V2.
optiClient Attendant V7.0 is no longer supported in HiPath 3000 V7 or later and HiPath 2000
V2.
optiClient Attendant versions < 7.0 cannot be upgraded.
8.5.1 optiClient Attendant V8 Connected To HiPath 3000 V7

Licensing is performed on the associated HiPath 3000 system. In order to ensure unique li-
censing, the license file is linked with the MAC address of the HiPath 3000 control board.
Procedure
1 2
6
optiClient HiPath 3000/
Attendant 1 5000 Manager E 3
V.24,
USB or HiPath 3000 5
TCP/IP V7 CLC
optiClient
CLA
Attendant 6
CLS
4
CLM
Figure 8-3 Procedure for Licensing optiClient Attendant V8 on HiPath 3000 V7

1. Read the HiPath 3000 V7 customer database.
2. Read out the MAC address of the HiPath 3000 control board.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Licensing optiClient Attendant

3. Enter the LAC and MAC address at the CLS in order to generate the license key ei-
ther
● a) via CLM/CLS communication,
or
● b) via direct communication with the CLS via a web browser.
4. Transfer the license key from the CLS via the CLM to the CLA (CLC - HiPath 3000/
5000 Manager E).
● a) via CLM/CLS communication,
or
● b) manually on the CLM (license key is already available, offline activation).
5. Write the CDB to HiPath 3000 V7. (Once the license data has been transferred to Hi-
Path 3000, the CLA is no longer required.)
6. Install optiClient Attendant(s).
“Any” number of optiClient Attendants can be installed. However, HiPath 3000 mon-
itors the number of licensedoptiClient Attendants as part of the logon procedure.
Depending on the model, up to six optiClient Attendants can be started per system.
When the HiPath 3000 is started for the first time, a 30-day grace period begins. Dur-
ing this time, all HiPath 3000 features that require licensing (including optiClient At-
tendant) can be operated without a license. All features that require a license (includ-
ing optiClient Attendants that have been subsequently installed) must be licensed
before the grace period of the HiPath 3000 expires. The 30-day limit cannot be ex-
tended and a second grace period will not be granted.
In this case, the CLS generates a license key for HiPath 3000 V7.
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm
Protection Against License Manipulation
8.6 Protection Against License Manipulation

HiPath License Management guarantees protection against any manipulation of the licenses.
This includes, for example
● editing a license file
● changing the system time
● multiple read-in of licenses
● extension of the grace period
When a Grace Period Configuration File (GPCF) is created, a flag is set in the system CDB
and the Customer License Agent (CLA) to indicate that a GPCF file was created. This en-
sures that the 30-day period cannot be extended and the GPCF file cannot be regenerated.
To guarantee the security and consistency of the product licenses generated, chang-
> es to the system time on the PC of an installed Customer License Agent (CLA) must
not exceed one day.
If the system clock is reset by more than one day, the Customer License Agent stops
functioning and cannot be reactivated. The full functionality of the CLA on this PC
can only be restored by means of a repair or a reinstallation (see the License Agent
Installation Manual).
A31003-H3570-S100-6-7620, 2008-04-01
licensing.fm

Protection Against License Manipulation
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Nur für den internen Gebrauch Expanding and Upgrading HiPath 3000
Overview
9 Expanding and Upgrading HiPath 3000
9.1 Overview
Chapter contents
Topic
Expanding HiPath 3000, page 9-2:
● Replacing Peripheral Boards for HiPath 3800, page 9-2
● Connecting a printer, page 9-4
● Insert Power Cabinet PB3000, page 9-5
● Use ECR for HiPath 3500 and 3300 (not for USA and Canada), page 9-21
● Connecting Special Equipment, page 9-38
Upgrading HiPath 3000 to Version 3.0, page 9-48
● Hardware Upgrade, page 9-48
● Software Upgrade, page 9-50
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Expanding and Upgrading HiPath 3000 Nur für den internen Gebrauch
Expanding HiPath 3000
9.2 Expanding HiPath 3000

The following section provides information on supplementary equipment or extensions that are
not described in Chapter 4, “Installing HiPath 3000”.
9.2.1 Replacing Peripheral Boards for HiPath 3800
Caution
handling boards).
HiPath 3800 lets you remove and insert peripheral boards during operation (hot plugging). The
following startup rules apply.
Rules for removing and inserting boards
Caution
7 To ensure that the system operates without blocking, you must follow the rules in
Section 4.2.5 concerning board configuration.
Table 9-1 Startup Rules for Inserting and Removing Boards
If Then
Inserting new board Board is integrated into the system according to the rules for initial
in free slot startup (Section 4.2.5.6).
● System with default numbering plan
The station numbers from the new board are appended (consecu-
tively and in ascending order) to the numbers already assigned.
● System with modified numbering plan
The station numbers on the new board can be in any order.
Using HiPath 3000/5000 Manager E or Manager T, you can assign a
specific station to a port. If the number is already assigned to a diffe-
rent object, you can switch both numbers.
Replacing board with Board is activated. The same station range is used.
same or underequip-
ped board type
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
If Then
Replacing board with Board is activated. The old station range is activated and the ports as-
over-equipped board sociated with the new board are inserted at the end. The ports are split
of same type if there is no contiguous station range available.
In the case of subscriber line modules, you can use HiPath 3000/5000
Manager E to retain the old station data by copying it to the new board,
or you can delete it and reset the default state. Copying is not possible
for trunk boards.
Replacing with a diffe- The system does not automatically activate the board.
rent board type After removing the old board, you can delete it from the database
using HiPath 3000/5000 Manager E or Manager T.
After you have inserted the new board, the system activates it as if it
had been inserted into a free slot. However, the CDB area used by the
old board is left as a gap.
In the case of subscriber line modules, you can use HiPath 3000/5000
Manager E to retain the old station data by copying it to the new board,
or you can delete it and reset the default state. Copying is not possible
for trunk boards.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.2 Connecting a printer
Caution
7 Follow the safety and operating instructions provided by the printer manufacturer.
Introduction
You can use a printer as a CDR printer (serial data transmission) or as a call charge computer
output device (parallel data transmission).
Connecting a CDR printer
HiPath 3000
Backplane
X7 (“8-slot” cabinets)
Connection cables:
S30267-Z23-A100 = 10m CDR printer
S30267-Z23-A500 = 50m
GND 1 1 GND 1)
TXD 2 2 TXD
RXD 3 3 RXD
25-pin con- RTS 4 4 RTS
nector printer
CTS 5 5 CTS 25-pin connec-
DSR 6 6 DSR tor
DCD 8 8 DCD
DTR 20 20 DTR
GND 7 7 GND 2)
1) Frame ground
2) Signal ground
Figure 9-1 Sample Connection of a CDR Printer to HiPath 3000

Information on assigning V.24 interfaces from other systems is provided in the board descripti-
ons in Chapter 3.
Output formats
For information about the output formats (compressed or uncompressed) for call detail recor-
ding central, see HiPath 3000/5000 Feature Description.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3 Insert Power Cabinet PB3000
Danger
7 The Power Cabinet PB3000 must be operated with a closed housing.
Before opening the housing, disconnect the ECR from the power supply by:
● turning the switch for the line voltage on the front panel of the PB3000 to the
"Off" position.
● turning the switch for the battery voltage on the back side of the PB3000 housing
to the "Off" position.
● removing the battery fuse (back side of the PB3000 housing).
● unplugging all power and connection cables.
Introduction
The Power Cabinet PB3000 is needed in a system:
● for emergency battery operation in the event of power failure; i.e., if an uninterruptible po-
wer supply function is required.
● if the internal system power supply unit for the HiPath 3000 is not sufficient to provide po-
wer to all connected terminals (corded or cordless).
The PB3000 can be equipped with:
● 4 batteries, each 12 V / 7 Ah and/or
● the LUNA2 power supply
The PB3000, the batteries and the LUNA2 power supply are supplied in a separate package.
The batteries should be installed as described in Section 9.2.3.6.1. Only use batteries appro-
ved for HiPath 3000. The LUNA2 power supply should be installed as described in Section
9.2.3.6.2.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.1 PB3000 Control, Display, and Connecting Elements
Front panel (Figure 9-2)

1: Switch for activating and deactivating the line voltage
2: Switch for activating and deactivating the LUNA2 power supply
(ON = left switch position/LED lights up green (for more information on LUNA2, see Section
3.2.12)
3: LED LUNA2
2
3
Figure 9-2 Front Panel of the PB3000
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Rear panel (Figure 9-3)

● Line voltage connections (1 and 2)
– 1: Line output of the power plug of HiPath 3000
– 2: Line input
● S1: Switch FAN, not assigned
● F1 and F2: Fuse 2.5 A/T
● X1 and X2: Output to DECT
● F3: Fuse for battery 16 A/T
● X3: Output for the battery to the external loads (HiPath 3000)
● X7: Output for the battery XBatt. (Power Cabinet Controller (PBC) < > battery connection)
● XBatt.: Input for X7 (battery < > Power Cabinet Controller (PBC) connection)
● 3: Switch for activating and deactivating the battery voltage
● F4: Fuse for the switch (battery voltage) 16 A/T
3
1
F1 F2 F3 F4
2
X7 XBatt.
S1 X1 X2 X3
Figure 9-3 Back of the PB3000
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.2 Components
● Power Cabinet PB3000 housing: C39165-A7027-A5-*
The scope of delivery includes:
– An assembly kit for the installation of the PB3000 into a 19" cabinet:
C39165-A7027-D1
– Assembly kit for the wall attachment or desk installation of the PB3000:
C39165-A7027-D2
● Power cable, according to configuration:
– C39195-Z7001-C11-* (Germany)
– C39195-Z7001-C38 (Switzerland)
– C39195-Z7001-C32 (United Kingdom)
– C39195-Z7001-C57 (Australia)
– C39195-Z7001-C46 (Euro)
– C39195-Z7001-C191 (Brazil)
● 4 batteries, 12 V/7 Ah: 4 X V39113-W5123-E891 (optional)
● Power supply LUNA2: S30122-H7686-X-* (optional)
● According to the system, one of the listed external connection cables is used:
– Cable for HiPath 3300/3500: C39195-A7985-B24-*
Figure 9-4 PB3000 - HiPath 3300/3500
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
– Cable for HiPath 3350/3550: C39195-A7985-B37-1
Figure 9-5 PB3000 - HiPath 3350/3550
– Cable to HiPath 3800: C39195-Z7985-B11-*
Figure 9-6 PB3000 - HiPath 3800
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
● Connection cable C39195-A7985-B38-* between XBatt. and X7 (optional)
Figure 9-7 XBatt. and X7
9.2.3.3 Installation Options
Use the power cable to ground the PB3000 Power Cabinet. Fixed, separate groun-
> ding is not required.
The Power Cabinet PB3000 can be installed as follows:

● in a 19-inch cabinet (see Section 9.2.3.8).
● on a wall (see Section 9.2.3.7).
● it can be set up on a desk using four adhesive mounting feet.
Assembly kit for installation in a 19-inch cabinet, for the wall attachment or desktop installation,
see Section 9.2.3.2.
9.2.3.4 Technical specifications
Table 9-2 Technical specifications
Power Cabinet PB3000 / Components Technical specifications

Power Box PB3000 Weight when empty: 7.0 kg
- including batteries and LUNA2 power supply Total weight: 21.0 kg (13.22
lb.)
Battery compartment - including 4 batteries Weight: 12.0 kg
Single battery (12 V / 7 Ah) Weight: 2.65 kg
LUNA2 (Linepowered Unit for Network based Architecture Weight: 2.0 kg
No. 2) power supply
For further information on
LUNA2 power supply, see
Section 3.2.12
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.5 UPS bridging time/charging time

USP bridging times and charging times when using the PB3000 with 48 V / 7 Ah batteries and
LUNA2 power supply (at maximal continuous current less than 2A, for all loads):
● Example PB3000 - HiPath 3300/3500
– UPS bridging time: >1 h 30 min
– Battery charging time: ~ 2 h
● Example PB3000 - HiPath 3800
– USV bridging time: > 30 min
– Battery charging time: ~ 2 h
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.6 Power Box PB3000 with batteries and LUNA2

The following block diagrams illustrate the cable run between the batteries, the LUNA2 power
supply and the power supply unit of the system:
● Block diagram of PB3000 with batteries
Figure 9-8 PB3000 with batteries
Caution
7 When storing a PB3000 equipped with batteries or if it is inactive for a long period of
time, remove the battery fuse (F3: Fuse for battery 16 A/T) at the rear of the PB3000
housing.
The PB3000 may not be shipped with the batteries installed. The batteries must first
be removed.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
● Block diagram of PB3000 with batteries and LUNA2
Figure 9-9 PB3000 with batteries and LUNA2
Caution
7 When storing a PB3000 equipped with batteries or if it is inactive for a long period of
time, remove the battery fuse (F3: Fuse for battery 16 A/T) on the rear of the PB3000
housing
The PB3000 may not be shipped with the batteries installed. The batteries must first
be removed.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
PB3000 with batteries and LUNA2

The following figure shows the position of the four batteries and the LUNA2 power supply inside
the PB3000.
Figure 9-10 PB3000 expanded with batteries and LUNA2
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.6.1 Installing Batteries
Danger
7 The only batteries approved for connection are V39113-W5123-E891 (12 V/7 Ah).
The use of other battery types is prohibited.
Note on recycling:
Old batteries with this symbol are utilizable economic units and must be re-
cycled. Old batteries that are not recycled are to be disposed of as special
refuse in accordance with all requirements.
The PB3000 and batteries are packaged separately and included in the delivery. Proceed as
follows to install the batteries in the PB3000:
Step Activity
1. Turn the switch for the line voltage on the front of the PB3000 housing and the
switch for the battery voltage on the back of the PB3000 housing to the "Off" po-
sition (see Section 9.2.3.1).
2. Remove the battery fuse on the rear of the PB3000 housing (see Section 9.2.3.1).
3. Unplug all of the power and connection cables of the PB3000.
4. Remove the front panel of the PB3000: to do so, remove the four screws.
5. Pull the plug-in battery module out of the left housing compartment.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Step Activity
6. Remove the mounting screw [A] on the battery retainer [B].
[A]
[B]
7. Remove the battery retainer and set aside.

8. Insert the battery carefully and connect it: To do this, slide the eight cable connec-
tor lugs [D] carefully onto the two connection contacts on each of the four batte-
ries.
[D]
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Step Activity
9. Fix the connection cable into place using cable binders.
10. Replace the battery retainer and secure the mounting screw.
11. Push the plug-in battery module into the left housing compartment up to the limit
stop.
12. Screw on the front panel of the PB3000: To do so, tighten the four screws.
13. Connect all of the power and connection cables of the PB3000.
14. Plug in the connection cable C39195-A7985-B38-* between XBatt. and X7. The
cable must be inserted into X7 with the side of the ferrite sleeve.
15. Insert the battery fuse on the rear of the PB3000 housing (see Section 9.2.3.1).
16. Turn the switch for the line voltage in the front panel of the PB3000 and the switch
for the battery voltage on the back side of the PB3000 housing to the "On" position
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.6.2 Install the LUNA2 power supply
PB3000 and LUNA2 power supply are supplied in a separate package. Proceed as follows to
install the LUNA2 in the PB3000:
Step Activity
1. Set the switches for the line voltage and the LUNA2 voltage on the front of the
PB3000 housing to the "Off" position (see Section 9.2.3.1).
2. Remove the fuse on the rear of the PB3000 housing (see Section 9.2.3.1).
3. Unplug all of the power and connection cables of the PB3000.
4. Remove the front panel of the PB3000: to do so, remove the four screws.
5. Push LUNA2 into the right housing compartment up to the limit stop.
6. Screw on the front panel of the PB3000: To do so, tighten the four screws.
7. Connect all of the power and connection cables of the PB3000.
8. Insert the battery fuse on the rear of the PB3000 housing (see Section 9.2.3.1)
9. Set the switches for the line voltage and the LUNA2 voltage on the front panel of
the PB3000 to the "On" position (see Section 9.2.3.1).
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.7 Wall mounting PB3000 (Not for USA:)
Caution
7 ● If the Power Cabinet PB3000 is wall mounted, you must install it in the proper
direction and sequence.
● The battery compartment including batteries and/or LUNA2 power supply must
be removed before installation!
● Wall anchors and screws (not supplied) must be be selected according to the
wall the device will be mounted on. The head of the screw must be big enough
to to fit securely behind the mounting bracket! The wall mounting point (wall and
screw) must be suitable to support 90kg!
Proceed as follows to wall mount the PB3000:
Step Activity
1. Drill a hole in the selected wall, insert a wall anchor in the hole, and screw in the
respective screw.
2. Screw the angle brackets (A) and (B) for the PB3000 onto the base of the device.
PB3000
B
Note: In the process, pay attention to the precise seat of the angle brackets in the
centering recess. These must lock into each other.
3. Mount the PB3000 with the angle bracket (A) on the screws.
4. Drill a second hole in the wall for the lower angle bracket (B), insert a wall anchor
and attach the angle bracket with a screw.
5. Reinstall the battery compartment and/or the LUNA2 power supply and reattach
the front panel of the PB3000 (see Section 9.2.3.6.1 and Section 9.2.3.6.2).
The PB3000 can now be used.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.3.8 PB3000 Cabinet Installation
Caution
7 The battery compartment including batteries and/or LUNA2 power supply must be
removed before installation!
Proceed as follows to install the PB3000 in a 19-inch cabinet:
Step Activity
1. Attach the angle brackets (A), to attach the PB3000 with two screws on both sides
(left and right) of the frame of the 19-inch cabinet.
C
Note: Necessary height units for 19-inch cabinet assembly: 4 HE
(one height unit (HE) corresponds to approx. 1.7’’=43 mm)
2. Attach both angle brackets (B) to the PB3000 with 2 screws on both sides (left and
right).
3. Insert the PB3000 between the angel brackets in the 19-inch cabinet (to the limit
stop).
4. Secure the two angle brackets of the PB3000 each with 2 screws on the frame of
the 19-cabinet.
5. Reinstall the battery compartment and/or the LUNA2 power supply and reattach
the front panel of the PB3000 (see Section 9.2.3.6.1 and Section 9.2.3.6.2).
The PB3000 can now be used.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.4 Use ECR for HiPath 3500 and 3300 (not for USA and Canada)
Danger
7 An expansion cabinet rack (ECR) equipped with an external power supply unit
(EPSU2-R) must be operated if the housing is closed.
Before opening the housing, disconnect the ECR from the power supply by
● setting the switches for battery voltage and line voltage on the ECR’s front panel
to "Off".
● removing the battery fuse on the ECR front panel and
Introduction
When installing the system, an ECR in the 19’’ cabinet is required if
● emergency battery operation is necessary during a power failure or if the system requires
uninterruptible power.
The necessary batteries are installed in the ECR.
● the internal system power supply unit for HiPath 3500 or HiPath 3300 is not sufficient
enough to provide power to the overall telephone configuration (corded or cordless tele-
phones).
In this case, the EPSU2-R external power supply unit should be installed in the ECR.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.4.1 ECR Control, Display, and Connecting Elements
Front panel (Figure 9-11)

● Top switch for disconnecting battery power
● Bottom switch for disconnecting line power
● 6.3 A/T battery fuse (warning: do not confuse with EPSU2-R fuse)

Figure 9-11 ECR Front Panel (155 x 440 x 380 mm)
Rear panel (Figure 9-12)

● Line voltage connections [1]
– Top: Line output to UPSC-DR connection jack for HiPath 3500 and HiPath 3300
– Below: Line input
● Batteries/EPSU2-R [2] output voltage to UPSC-DR for HiPath 3500 and HiPath 3300
● Clip [3]
Attach the braided screen of the connection cable (to the jack [2]) here.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
If an EPSU2-R external power supply unit is installed in the ECR, the following additional dis-
play and control elements are also included:
● EPSU2-R 2.5 A/T [4] fuse for batteries (warning: do not confuse with battery fuse on the
ECR front panel)
● LED [5] for the -48-V output voltage (DC output) in the EPSU2-R (see Table 9-3)
● LED [6] for the line input voltage (AC input) in the EPSU2-R (see Table 9-3)
[6]
[4] [5]
[2]
[1] [3]
Figure 9-12 ECR Rear Panel With Connecting Elements
Table 9-3 EPSU2-R - Explanation of Display and Connecting Elements
LED [6] LED [7] Description

On On DC output and AC input voltages are OK.
Off On No DC voltage at output
(for example DC load short-circuited).
On Off No AC voltage at input
(power failure or system powered by batteries, including additio-
nal power).
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Table 9-3 EPSU2-R - Explanation of Display and Connecting Elements
LED [6] LED [7] Description

Off Off No AC input voltage (power outage) and batteries are empty, or
the EPSU2-R fuse is defective or was removed (by turning to the
left).
9.2.4.2 Components
● Expansion cabinet rack (ECR): S30777-U711-E901
The scope of delivery includes:
– A mounting set for installing the ECR in a 19-inch cabinet: C39165-A7027-D1
– A mounting clamp: D72571-A80-S3
– A toothed lock washer: D6797-A43-S657
● Mounting set for ECR wall installation or ECR table setup: C39165-A7027-D2
● EPSU2-R: S30122-K7221-X900
A cable for making the ECR – HiPath 3500 or HiPath 3300 electrical connection is included
in the delivery: C39195-Z7001-C14
● 4 batteries, 12 V/7 Ah: 4 x V39113-W5123-E891
● Connection cable, ECR – HiPath 3500 or HiPath 3300: S30267-Z361-A10
Caution
7 The connection cable S30267-Z361-A10 is designed for HiPath 3500 and HiPath
3300 only. Failure to observe the above may damage the power supply unit.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.4.3 Installation Options
Use the power cable to ground the ECR. Fixed, separate grounding is not required.
>
The expansion cabinet rack ECR can be
● installed in a 19-inch cabinet (see Section 4.3.4.5).
● mounted on a wall (see Section 4.3.4.4).
● set up on a table using four adhesive mounting feet.
9.2.4.4 Expansion Cabinet Rack ECR With Batteries
Danger
7 Before opening the housing, disconnect the ECR from the power supply by
to "Off".
When using the UPSM or the UPSC-DR as the uninterruptible power supply unit, you need to
install additional batteries in the ECR.
The ECR and batteries are packaged separately and included in the delivery. The batteries
should be installed as described in Section 9.2.4.4.1. Only use batteries approved for HiPath
3000.
Figure 9-14 shows the position of the four batteries inside the ECR.
The circuit diagram below illustrates the cable run between the batteries in the ECR and the
power supply unit of the system (UPSC-DR for HiPath 3500 and HiPath 3300). The connection
cable between the expansion cabinet rack ECR and the system cabinet is also provided.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
S1
X1 X2
1 L1 L1 1
2 N N 2
3 PE PE 3
PE
X3
3
Housing 4
1
+48 V
4 batteries 2
–48 V UP
12 V / 7 Ah
F1 T6.3 A –48 V BatB
S2
+48 V
Figure 9-13 HiPath 3500, HiPath 3300 - ECR with batteries
Caution
7 When storing an ECR equipped with batteries or if the ECR is inactive for a long pe-
riod of time, remove the battery fuse (6.3 A/T) in the front panel of the ECR.
The ECR may not be shipped with the batteries installed. The batteries must first be
removed.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
1 2 3 4
Figure 9-14 ECR With Built-In Batteries
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.4.4.1 Installing Batteries
Danger
7 Only V39113-W5123-E891 (12 V/7 Ah) batteries are released for connection to the
UPSC-DR/UPSM and installation in the ECR.
The use of other battery types is prohibited.
Note on recycling:
Old batteries with this symbol are utilizable economic units and must be re-
cycled. Old batteries that are not recycled are to be disposed of as special
refuse in accordance with all requirements.
ECR is supplied with four batteries in a separate package. Proceed as follows to install the bat-
teries in the ECR:
Step Activity
1. Set the switches for battery voltage and line voltage on the ECR’s front panel to
"Off" (see Section 9.2.4.1).
2. Remove the battery fuse (ECR front panel) (see Section 9.2.4.1).
3. Unplug all of the ECR’s power and connection cables.
4. Remove the ECR housing cover: To do this, remove the three screws at the rear
and slide the housing cover back.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Step Activity
5. Remove the mounting screw [A] on the battery retainer [B].
[A] [B]
6. Remove the battery retainer and set aside.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Step Activity
7. Insert the batteries carefully in the recesses provided [C].
[C]
8. Replace the battery retainer and secure the mounting screw.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Step Activity
9. Connect the batteries: To do this, slide the eight cable connector lugs [D] carefully
onto the two connection contacts on each of the four batteries.
[D]
10. Replace the ECR’s housing cover and secure the three mounting screws at the
rear.
11. Connect all of the ECR’s power and connection cables.
12. Insert the battery fuse (ECR front panel) (see Section 9.2.4.1).
"On" (see Section 9.2.4.1).
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.4.5 Expansion Cabinet Rack ECR With Batteries and EPSU2-R
Danger
7 An expansion cabinet rack (ECR) equipped with an external power supply unit
(EPSU2-R) may only be operated if the housing is closed.
Before opening the housing, disconnect the ECR from the power supply by
to "Off".
If the internal system power supply unit for HiPath 3500 or HiPath 3300 does not provide
enough power for the overall telephone configuration (corded and cordless telephones), an ad-
ditional power supply is necessary. In this case, the EPSU2-R external power supply unit
should be installed in the ECR.
Figure 9-16 shows the position of the EPSU2-R inside the ECR.
The block diagram below illustrates the cable run between the EPSU2-R and the batteries in-
side the ECR and the power supply unit of the system (UPSC-DR). The connection cable bet-
ween the expansion cabinet rack ECR and the system cabinet is also provided.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
S1
X1 X2
1 L1 L1 1
2 N N 2
3 PE PE 3
PE
Housing
Input
–48 V BatE EPSU2-R

X3
–48 V CD
Batt 3
+48 V Out 4
+48 V +48 V 1
4 batteries –48 V UP 2
F1 12 V / 7 Ah
T6.3 A –48 V BatB
S2 Fan
+48 V (not available with all
systems)
Figure 9-15 HiPath 3500, HiPath 3300 - ECR With Batteries and EPSU2-R
Caution
7 When storing an ECR equipped with batteries or if the ECR is inactive for a long pe-
riod of time, remove the battery fuse (6.3 A/T) in the front panel of the ECR.
The ECR may not be shipped with the batteries installed. The batteries must first be
removed.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
EPSU2-R
Figure 9-16 ECR with Built-In EPSU2-R
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.4.5.1 Connecting a Fan (if needed)

The ECR delivery usually includes a fan that is built in but not connected.
To connect the fan, proceed as follows:
Step Activity
"Off" (see Section 9.2.4.1).
2. Remove the battery fuse (ECR front panel) (see Section 9.2.4.1).
3. Unplug all of the ECR’s power and connection cables.
4. Remove the ECR housing cover: To do this, remove the three screws at the rear
and slide the housing cover back.
5. Cut off the plug on the fan connection line if there is one.
Strip both wire ends and attach wire end sleeves.
6. Connect both connection wires to the EPSU2-R terminal [A] as shown in
Figure 9-17. Connect the red wire (fan) to the white wire (EPSU2-R) and the
black wire (fan) to the black wire (EPSU2-R).
Figure 9-15 shows the cable run between EPSU2-R and the fan.
7. Replace the ECR’s housing cover and secure the three mounting screws at the
rear.
8. Connect all of the ECR’s power and connection cables.
9. Insert the battery fuse (ECR front panel) (see Section 9.2.4.1).
"On" (see Section 9.2.4.1).
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
[A]
Figure 9-17 Connecting the Fan to the EPSU2-R
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
If you install the fan at a later time, you must make sure that the identification ([B] in Figure 9-
18) is in the upper right corner when viewed from outside.
[B]
Figure 9-18 Placement of the Fan in the ECR
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.5 Connecting Special Equipment
9.2.5.1 Entrance Telephones
Connection options
Connection via ET (entrance telephone) adapter and amplifier
HiPath 3000 ET adapter Amplifier Door
Connection over ET/V adapter
HiPath 3000 ET/V Door

adapter
Figure 9-19 Connection Options for Entrance Telephones
The new central control boards CBCC (S30810-Q2935-A301) and CBRC (S30810-
> Q2935-Z301) only support TFE-S-Adapter S30122-K7696-T313.
You can also make a direct connection if needed. In this case, only voice connections to the
entrance telephone are possible, without the support of the opener and signal functions.
if necessary, loop in a capacitor

1 µF/250 V for each
a
Amplifier to the T/R analog port
b
Figure 9-20 Direct Connection of Entrance Telephones
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.5.1.1 Information on Third-Party Entrance Telephones
DoorCom Analog
General information
The plus product DoorCom® Analog is a universal entrance telephone adapter box for Siedle
entrance telephones (such as the Vario TLM 612). It is released for use with all HiPath 3000
systems, V1.2 and later.
It is connected to an analog port in the system. DoorCom Analog behaves like an analog tele-
phone (DTMF tone dialing, detection, and control). It can be operated with DTMF signals.
DoorCom Analog can function only in combination with the following components:
● DoorCom Analog DCA 612-0
● Siedle-Vario TLM 612 entrance telephone
● Switching remote control interface DCSF 600
For the voice connection of an internal user to the entrance telephone: Without this modu-
le, it is not possible to call back to the entrance telephone, for example, if a call was unin-
tentionally cleared down by the entrance telephone.)
● Power supply NG 602-0
Connection
Power supply
NG 602-0
HiPath 3000
Siedle-Vario
TLM 612
T/R
DoorCom Analog
DCA 612-0
Figure 9-21 Connecting DoorCom Analog to HiPath 3000
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Configuration Notes for HiPath 3000/5000 Manager E
DoorCom Analog
Set up station: Stations: Parameters:
Extension Type = Standard
Flags = Call waiting rejection on
System parameters:
Flags = DTMF automatic
Remote station (telephone)
Set up station: Stations: Parameters:
Flags = Call waiting rejection off
Flags = Missed Calls List
Device control features (open doors, select entrance telephone, etc.) can be programmed on
procedure keys. The stored DTMF signal sequence is sent to the application.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.5.2 Connecting Speakers

You have the following options:
● Connection to an analog station port (the amplifier may require level adaptation)
● Connection to an analog station port over an ET adapter
Note: The ET adapter requires a 12V power supply (DC or AC).
● Connection to an analog trunk circuit
Connecting speakers to an analog station port
HiPath 3000 T/R

SLA/SLAS Amplifier
REAL/STRBR/ Starting contact

STRBR
HiPath 3000 12V

power supply
T/R ET Active spea-
SLA/SLAS (without kers only
amplifier
12V
HiPath 3000 power supply
T/R ET T/R
SLA/SLAS Amplifier
Figure 9-22 Connecting Speakers to an Analog Station Port
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Connecting speakers to an analog trunk port
Active speakers
HiPath 3000 T/R only
TML/TLA
HiPath 3000 T/R Amplifier

TML/TLA
Starting contact
REAL/STRB
Figure 9-23 Connecting Speakers to an Analog Trunk Port
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.2.6 Use DCDR for HiPath 3800

Using a DCDR (Direct Current Distribution Rack) enables the permanent operation of a com-
munications system HiPath 3800 on a 48 V-DC power plug.
The DCDR functions as a distributor and fuse element to connect a 48 V-DC
power plug to the system cabinets in a 19-inch cabinet.
Figure 9-24 DCDR – front view
DCDR Technical Specifications

● Dimensions (width x depth x height in mm): 435 x 205 x 90
● Height units for 19-inch cabinet assembly: 2
● Weight (including batteries): approx. 4 kg
● Operational electrical characteristics:
– Operating voltage: 80 VDC (in HiPath 3800 60 VDC, system-specific)
– Total power per DCDR: 80 A
– Max. nominal current, circuit breaker per slot: 25 A
– Cable feed diameter: 35 mm2
– Short circuit current: 3000 A
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
DCDR kit S30122-K7698-X-* supply scope

● DCDR S30122-X8019-X4 (including terminal block S30122-X8018-X2 and connection ca-
bles)
● 4 connection cables C39195-A7944-B56-*
● 10 cable binders
The DCDR and terminal block are secured to the 19-inch rack using rack-specific screws (not
supplied).
Examples for installation in a 19-inch cabinet
Caution
7 The specifications described in the Section 4.2.4.1, “Selecting the Installation Site”
for mounting the 19’-inch cabinet of the HiPath 3800 must be adhered to.
The height units represented in yellow in Figure 9-25 must be kept clear to ensure
adequate ventilation of the system cabinets.
The DCDR must always be mounted above a system cabinet.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Examples of a 19-inch cabinet height of 1.92 m with 37 height units
DCDR
*
HiPath 3800
Expansion
cabinet
DCDR *
*

Basic cabinet Basic cabinet
* leave open for venti-

lation
Figure 9-25 HiPath 3800 - Examples for installation in a DCDT in a 19-inch cabinet
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Grounding
Danger
7 The specifications described in the Section 4.2.4.4, “Grounding the System” must be
adhered to.
Each system cabinet HiPath 3800 and any patch panel (S30807-K6143-X) that may
be installed must be grounded as shown in
Figure 4-13 by a separate ground conductor (minimum cross-section = 2.5 mm
mm2). Make sure that the ground conductor is securely installed and strain-relieved.
Please note:
The 19-inch cabinet’s potential equalization bus may only be used if it is grounded
by a separate ground conductor.
Separate grounding is not required for the DCDR. Proper grounding is ensured by securing the
DCDR cabinet to the 19-inch cabinet.
Connection
X32 X30 X04 X02

X31 X29 X03 X01 (–)
(+)
1 A circuit brea-
ker for HVT 16 A circuit breakers
for HiPath 3800 basic
and expansion cabinet
L1+ L1–
from the
terminal block
Figure 9-26 DCDR – rear view
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
The approved 16 A circuit breaker V39118-Z7180-A6 must always be used to con-

> nect a HiPath 3800 system cabinet.
The approved 1A circuit breaker V39118-Z7180-A8 can be used to connect external
loads via the MDF.
The required circuit breakers must be ordered specially for each customer.
(-) DCDR (-)
Connection between terminal block and DCDR

Connection between DCDR und Hi-
HiPath
Path 3800 system cabinets

DC
Connection
LUNA2 LUNA2 LUNA2 LUNA2
HiPath 3800
Terminal block DC
Connection
LUNA2 LUNA2 LUNA2

PE L2+ L1+ L2- L1-
Note: View without

Terminal block grounding
48 V-DC power plug
Figure 9-27 HiPath 3800 – Example of connecting the DCDR (rear view of the 19-inch ca-
binet)
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Upgrading HiPath 3000 to Version 3.0
9.3 Upgrading HiPath 3000 to Version 3.0

The following information describes the measures that are needed to upgrade the hardware
and software.
It is not possible to upgrade HiPath 3550 to HiPath 3500 or HiPath 3350 to HiPath
> 3300. This would require replacing the complete system.
9.3.1 Hardware Upgrade

The following hardware requirements apply to HiPath 3000/5000 V5.0 and higher.
Control boards
If the control board necessary for operating HiPath 3000/5000 V5.0 and higher is not available,
a replacement must be performed.
System Control board necessary for HiPath 3000/5000 V5.0 and higher
HiPath 3800 CBSAP, S30810-Q2314-X and higher
HiPath 3550 CBCC, S30810-Q2935-A301 and higher
HiPath 3350
HiPath 3500 CBRC, S30810-Q2935-Z301 and higher
HiPath 3300
Note for upgrading from hardware < version 1.2:

> If the following subboards are present, they must be replaced: IMODN (replaces the
IMOD), MMC (replaces the FMC), CMA/CMS (replaces the CGM/CGMC).
For Deutsche Telekom AG only: The CBCP board S30810-Q2935-B201 must be replaced by
a CBCC board S30810-Q2935-A301.
Multimedia card MMC

An MMC with 64 MB is required to run HiPath 3000/5000 V5.0 and higher.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
HG 1500 boards
The HG 1500 boards listed in the following table are necessary for using the HG 1500 functio-
nality with HiPath 3000/5000 V5.0 and higher. Unnamed HG 1500 boards must be replaced.
System HG 1500 board required for HiPath 3000/5000 V5.0 and higher
HiPath 3800 STMI2, S30810-Q2316-X100 and higher
HiPath 3550 HXGS3, S30810-Q2943-X and higher
HiPath 3350
HiPath 3500 HXGR3, S30810-K2943-Z and higher
HiPath 3300
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.2 Software Upgrade

If the software is a version earlier than V3.0, it must first be upgraded to V3.0. Only then is it
possible to upgrade the software to Version 3.0.
CDB conversion is also necessary.
Procedure: Customer database (CDB) conversion
Please note the following:

> S0 stations can be configured as both HFA clients and vCAPI clients in V4.0. In ad-
dition, V4.0 does not have a selected gatekeeper board. This configuration will have
to be re-defined when upgrading V5.0 (see Figure 9-28).
The flowchart on Page 9-51 describes the procedure for converting the CDB from
V4.0 to V5.0. First, you must edit the V4.0 CDB. Then you must convert the CDB
and finally, edit the V5.0 CDB.
No other changes are necessary apart from modifications for IP workpoint clients
and IP lines. Only the gatekeeper and gateway data has to be edited. Telephone
numbers and other properties of the IP workpoint clients are retained. The protocol
has to be modified for the IP lines.
V4.0 configuration onversion From V4.0 to V5.0 or La-

ter (Part 1 of 4)
HG 1500 board System clients System clients HG 1500 board

slot 4 slot 4
S0 station: H.323 clients
HFA clients HG 1500
gatekeeper
S0 station: Lines
vCAPI clients
HG 1500 board System clients S0 station HG 1500 board

slot 6 slot 6
S0 station:
HFA clients HG 1500 gateway
Lines
Figure 9-28 Configuration differences between V4.0 and V5.0 or later
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
CDB Conversion V4.0 –> V5.0
Define which HG 1500 board be-

comes the HG 1500 gatekeeper
and which becomes the HG 1500
gateway.
Make a note of the S0 station

numbers.
More than one HG 1500 board in-

No
stalled?
Yes
Define gatekeeper HG 1500.
Open V4.0 CDB using HiPath Open V4.0 CDB using HiPath
3000/5000 Manager E. 3000/5000 Manager E.
Figure 9-29 CDB Conversion From V4.0 to V5.0 or Later (Part 1 of 4)
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Open “HXG Configuration” dialog. Open “HXG Configuration” dialog.

For all HG 1500 boards installed:
Delete all S0 stations.
Delete all lines.
Convert CDB from V4.0 –>

V5.0 using HiPath 3000/5000
Manager E.
Delete all system clients.
Set “Release gateway resources”

Delete all HFA clients in the S0 flag.
station.
Configure S0 stations.
Delete all vCAPI clients in the S0
station.
Conversion V5.0 finished.

Check whether the number of all Save CDB.
configured stations and lines is 0.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Save the CDB under new name.
Convert CDB from V4.0 –>

V5.0 using HiPath 3000/5000
Manager E.
Define the slot for the HG 1500

gatekeeper.
Enter the number of lines re-

quired.
Configure all V4.0 HFA clients as

H.323 clients.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Configure all V4.0 system clients

as system clients (V4.0 call num-
ber and name are retained).
Define the slot(s) for the HG 1500

gateway.
Configure S0 stations.
Conversion V5.0 finished.

Save CDB.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.3 Instructions for Upgrading from V6.0 to V7
9.3.3.1 Introduction
The following prerequisites must be fulfilled when upgrading software from E-Doku V6.0 to E-
Doku V7:
● There are new licenses for version 7.
● All IP workpoints (HFA) in a system or all IP workpoints (HFA) in a network must be EFC-
enabled.
The CorNet-IP protocol was extended in HiPath 3000/5000 V7 to include the EFC (Exten-
ded Fast Connect) protocol variant.
EFC is an absolute prerequisite to be able to fully use all features. It is only permitted to
deactivate the EFC protocol variant when upgrading a network. Otherwise features can be
interrupted.
EFC is the basis to be able to use for example the following features:
– Signaling & Payload Encryption SPE
Signaling & Payload Encryption is supported from HiPath 3000/5000 V7 R4 and later.
This allows both signaling and payload data to be encrypted at station level.
Signaling Encryption = signaling data encryption: The signaling transmission between
HiPath 3000/5000 V7 and the connected IP workpoints, e.g. OpenStage, optiClient
130, is encrypted using a 128-bit key. The same mechanism is used to encrypt the si-
gnaling data between IP-networked systems (HiPath 2000, HiPath 3000, HiPath 4000,
HiPath 5000).
Payload Encryption = encryption of the payload data (voice data): The payload data is
transmitted using the Secure Real-time Transport Protocol (SRTP) and is encrypted
with a 128-bit key. SRTP is also used to encrypt the payload data between IP-networ-
ked systems (HiPath 2000, HiPath 3000, HiPath 4000, HiPath 5000). The Deployment
Service DLS distributes the commonly used key for a secure domain. The procedure
to swap out the key for SRTP is called Multimedia Internet Keying (Mikey).
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
– IP/IP E2E payload via enterprise proxy for Internet telephony

IP/IP E2E Payload via Enterprise Proxy is supported for Internet telephony from Hi-
Path 3000/5000 V7 R2 or later. This means that, for Internet telephony, data packets
do not need to be processed by the digital signal processors of the system. Calls are
routed via LANs, routers and the Internet Telephony Service Providers (ITSP).
HiPath 3000 sets up a call to the remote station.
Instead, the maximum number of simultaneous calls depends on the codec used and
the available bandwidth of the Internet telephony connection.
The EFC protocol is activated in HiPath 3000/5000 V7 by default.

> This setting should not be modified as this can lead to feature interruptions.
The procedure for upgrading software depending on the various scenarios is described in the
following sections.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.3.2 Upgrading a HiPath 3000 Standalone System
Procedure
1. Check that all connected IP workpoints (HFA) are EFC-enabled:
If Then
optiPoint 400 standard These IP workpoints do not support EFC
optiPoint 400 economy and must be replaced with EFC-enabled IP
optiPocket workpoints.
optiPoint 410 family These IP workpoints are EFC-enabled.
optiPoint 420 family
optiPoint WL2 professional
optiClient 130
optiClient Attendant V8
2. Upgrade all IP workpoints with the current EFC-enabled software.
Refer to the Release Notes and Sales Release for information on the latest software ver-
sions.
3. Upgrade all HG 1500 boards to V7.
4. Convert the customer database (CDB) and reload it together with the V7 system software.
5. Install new licenses.
The upgrade is complete.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.3.3 Upgrading a HiPath 5000 RSM Network
Procedure
1. Check that all IP workpoints (HFA) in the network are EFC-enabled:
If Then
optiClient 130
sions.
3. Dissolve the network:
a) Remove all systems (nodes) belonging to the network from HiPath 5000 RSM.
a) Stop the Feature server service.
4. Upgrade each system that belongs to the network:
a) Upgrade all HG 1500 boards to V7.
b) Convert the customer database (CDB) and reload it together with the V7 system soft-
ware.
5. Once all standalone systems have been upgraded, you can upgrade HiPath 5000 RSM in-
cluding HiPath 5000 ComScendo Service on site. To do this, add all systems (nodes) be-
longing to the network to HiPath 5000 RSM.
6. Put the network into service with HiPath 3000/5000 V7 (commission the Feature server
service).
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.3.4 Upgrading a HiPath 3000 System Networked with Surpass
A Surpass network is only possible with a HiPath 3000 standalone system. The EFC
> protocol variant EFC is not supported here.
Simultaneous connection to Surpass and an ITSP is not supported.
It is not necessary to upgrade the IP workpoints with the latest EFC-enabled softwa-
re.
Procedure
1. Upgrade all HG 1500 boards to V7.
2. Convert the customer database (CDB) and reload it together with the V7 system software.
4. Deactivate the "Extended Fast Connect" protocol variant in the HG 1500 module that ope-
rates as a signaling gateway (= HG 1500 gatekeeper).
WBM: Expert Mode Explorers: Basic Settings – (right-click) Gateway – Modify Gateway
Properties
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.3.5 Upgrading a HiPath 3000 System Networked with HiPath 2000
Procedure
1. Check that all IP workpoints (HFA) in the network are EFC-enabled:
If Then
optiClient 130
sions.
3. Upgrade each system that belongs to the network:
a) Upgrade HiPath 3000 systems to V7.0: Upgrade all HG 1500 boards to V7.
Convert the customer database (CDB) and reload it together with the V7 system soft-
ware.
a) Upgrade HiPath 2000 systems to V2: Convert the customer database (CDB) and re-
load it together with the V2 system software.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.3.6 Upgrading a HiPath 3000 System Networked with HiPath 4000
All IP workpoints (HFA) in the HiPath 3000 system must be EFC-enabled.

> The IP workpoints (HFA) in the relevant HiPath 4000 system remain unchanged.
Procedure
1. Check that all IP workpoints (HFA) in the HiPath 3000 system are EFC-enabled:
If Then
optiClient 130
2. Upgrade all IP workpoints in the HiPath 3000 system with the current EFC-enabled soft-
ware.
sions.
3. Upgrade the HiPath 3000 system:
a) Upgrade all HG 1500 boards to V7.
b) Convert the customer database (CDB) and reload it together with the V7 system soft-
ware.
4. Activate Gateway Call Flag "Always Use DSP" in the direction of HiPath 4000 (HiPath 3000
Manager E: Settings – Lines/networking ... – Special).
Note: As HiPath 4000 is not EFC-enabled, activating this flag sets up gateway connections
to the HiPath 4000 system.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
9.3.4 Upgrade HiPath 3000 for Signalling & Payload encryption (SPE)
Overview
The Signaling & Payload encryption feature is provided with HiPath 3000/5000 from V7 R4 or
later. In software versions earlier than V7 R4, a software upgrade is necessary for this feature
to be used in HiPath 3000. A hardware upgrade is not required. As a result of the increased
demand by SPE for resources further HG 1500 boards might be required.
Upgrading
The following software upgrades are necessary before this feature can be used for without re-
strictions:
● Upgrade of all HFA terminals to an SPE-enabled software version
Due to the introduction of EFC, HiPath 3000 V7 is no longer upwardly compatible with re-
gard to the "Signaling & Payload Encryption" feature, except to HiPath 3000 V6.0 sys-
tems which have an EFC-enabled HG 1500 and EFC-enabled terminals.
● Upgrade of all HG 1500 Gateways to software version 7 R4 or higher
● Upgrade of the HiPath 3000/5000 to software version 7. Before upgrading a HiPath 3000/
5000 V6.0 to HiPath 3000/5000 V7 the "VoIP Security" feature must be deactivated. This
is necessary due to the fact that this feature is not compatible with the "Signaling & Payload
Encryption (SPE) feature described here.
● Upgrade of administration program DLS and HiPath Manager E
● Upgrade of HiPath 5000 ComScendo Service (DB Feature Server) to
software version 7 R4 or higher
● Changes to configuration so that SIP-Q instead of CorNet-IP is used to network
HiPath 3000 with
HiPath 4000 V4.0 systems. The HiPath 4000 supports SPE only via the SIP-Q protocol.
● Changes to the configuration of the "Always use DSP" option if HiPath 4000 networking
should still be achieved using H.323-Q (CorNet-IP). In this case no SPE to the
HiPath 4000 is possible.
● The HiPath 4000 must from HiPath 3000/5000 V7 to connected as an external H.323 gate-
keeper or external SIP registrar.
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Consequences for the system

Activation of the Signalling & Payload Encryption feature has the following consequences for
the HiPath network:
● Higher bandwidth requirement due to continuous TLS sessions for:
– Connections to HFA terminals (CorNet-IP TC/TS, H.225 CS)
– Connections for SIP terminals (SIP including SDP)
– H.323 and SIP trunking connections
● Higher bandwidth requirement:
– Due to the fill and authentication algorithms used by TLS during transmission of user
data
– Due to the proprietary encryption protocols used for IPDA and CTI connections
– Due to SRTP/SRTCP
● Higher network traffic due to periodic downloads of CRL ( Certificate Revocation List) or
delta CRL by each Gateway
● Higher network traffic due to recently introduced protocols
– H.235 Annex D for DMC Slave connections
– MIKEY Messages
● Additional data due to protocol extensions:
– CorNet-TC/TS plus X_Messages
– H.225 RAS (LEGK communication)
– CorNet NQ
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Higher demand for data by SPE

The following table provides an overview of the higher demand for data by the Signaling & Pay-
load Encryption (SPE) feature):
Voice Sample Payload Size of RTP SRTP SRTP

codec duration Ethernet Ethernet Ethernet Increased
data bandwidth bandwidth Ethernet
package including including bandwidth
preamble preamble
(ms) (Bytes) (Bytes) (Kbps) (Kbps) (%)
G.711 20 160 240 92 96 4.3
40 320 400 78 80 2.6
60 480 560 73.3 74.7 1.9
G723.1 30 24 104 25.1 27.7 10.4
G.723.1A 60 48 128 15.7 17.1 8.9
G.729A 20 20 100 36 40 11.1
40 40 120 22 24 9.1
60 60 140 17.3 18.7 8.1
G.729A 100 6 86 6.1 6.9 13.1
DMC
Master
Call
G.711 100 11 91 6.5 7.3 12.3
DMC
Master
Call
G.723 90 6 86 6.8 7.6 11.8
DMC
Master
Call
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
Higher demand for resources by SPE

The following table provides an overview of the higher demand for resources by the Signaling
& Payload Encryption (SPE) feature. Values are automatically transferred by the system. If the
SPE feature is active, a reduced number of channels are indicated on the system.
Feature Maximum number of voice channels (per Loss

DSP)
HG 1500 HG 1500
STMI2 HXGM3
HXGS3
HXGR3
Standard 16 8 0%
QDC 16 8 6%
SRTP 12 6 20%
DMC 12 6 25%
QDC+ SRTP 12 6 24%
QDC+DMC 12 6 28%
SRTP+DMC 10 5 37%
QDC+SRTP+DMC 10 5 39%
A31003-H3570-S100-6-7620, 2008-04-01
exup.fm
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Nur für den internen Gebrauch Workpoint Clients
Overview
10 Workpoint Clients
10.1 Overview
Chapter contents
Topic
OpenStage Product Family (from V7 R3), page 10-4
● OpenStage terminals, page 10-6
– OpenStage 10
– OpenStage 20
– OpenStage 40
– OpenStage 60
– OpenStage 80
– Connection and Startup
● OpenStage Add-On Devices, page 10-22
– OpenStage Key Module
– OpenStage BLF
– Possible Configurations for the Key Modules
● Power supply of the OpenStage terminals, add-on devices, and adapters
● OpenStage Accessories, page 10-29
– OpenStage PhoneAdapter
– Acoustic Unit
– Headsets
– Keyboard
– USB Extension
optiPoint 410 / optiPoint 410 S and optiPoint 420 / optiPoint 420 S, page 10-37
● optiPoint 410 and optiPoint 410 S Telephones, page 10-40
– optiPoint 410 entry, optiPoint 410 entry S
– optiPoint 410 economy, optiPoint 410 economy S
– optiPoint 410 economy plus, optiPoint 410 economy plus S
– optiPoint 410 standard, optiPoint 410 standard S
– optiPoint 410 advance, optiPoint 410 advance S
● optiPoint 420 and optiPoint 420 S Telephones, page 10-50
– optiPoint 420 economy, optiPoint 420 economy S
– optiPoint 420 economy plus, optiPoint 420 economy plus S
– optiPoint 420 standard, optiPoint 420 standard S
– optiPoint 420 advance, optiPoint 420 advance S
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Workpoint Clients Nur für den internen Gebrauch

Overview
Topic
● Connection and Startup, page 10-58
– Connections on the Bottom of the Telephone
● Key programming, page 10-61
● Key modules for optiPoint 410/410 S and 420/420 S, page 10-62
– optiPoint self labeling key module
– optiPoint 410 display module
● Use of optiPoint 500 Adapters, page 10-66
Central Administration of IP Workpoints via the System, page 10-67
● Plug’n Play Startup of IP Workpoints, page 10-68
● Software Upgrade of IP Workpoints via the System, page 10-69
optiPoint 150 S, page 10-71
optiPoint 600 office, page 10-74
optiPoint 500, page 10-76
● optiPoint 500 Telephones, page 10-77
– optiPoint 500 entry
– optiPoint 500 economy (not for U.S.)
– optiPoint 500 basic
– optiPoint 500 standard, optiPoint 500 standard SL (for U.S. only)
– optiPoint 500 advance
– Connection Requirements for HiPath 3000
– Connection
– Connections on the Bottom of the Telephone
– USB 1.1 Interface
– Key programming
● optiPoint 500 Add-On Devices, page 10-89
– optiPoint key module
– optiPoint BLF
– optiPoint application module (V5.0 SMR-06 and later)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Overview
Topic
● optiPoint 500 Adapters, page 10-93
– optiPoint analog adapter
– optiPoint ISDN adapter
– optiPoint phone adapter
– optiPoint acoustic adapter
– optiPoint recorder adapter
– Possible optiPoint Adapter Configurations
– Comparison of optiset E adapters and optiPoint 500 adapters
● optiPoint 500 key modules and adapters power supply, page 10-104
● Maximum Configuration for UP0/E Workpoint Clients, Add-On Devices and Adapters,
page 10-105
optiLog 4me, page 10-107
optiset E privacy module, page 10-108
optiPoint Accessories, page 10-109
● External AC Adapters, page 10-109
● Headsets, page 10-112
optiClient 130 V5.0, page 10-115
HiPath AP 1120, page 10-116
optiPoint WL2 professional, page 10-117
Attendant console versions, page 10-118
● OpenStage Attendant, page 10-118
● optiPoint Attendant, page 10-118
● optiClient Attendant V8, page 10-119
Mobile Telephones for HiPath Cordless Office, page 10-124
● Gigaset SL1 professional, page 10-124
● Gigaset SL2 professional, page 10-124
● Gigaset M1 professional, page 10-125
● Gigaset M2 professional, page 10-126
● Logging Mobile Telephones On To the System, page 10-127
Analog Telephones for HiPath 3000, page 10-130
ISDN Term inals for HiPath 3000, page 10-131
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

OpenStage Product Family (from V7 R3)
10.2 OpenStage Product Family (from V7 R3)

The OpenStage product family represents a new generation of terminals for high-performance
business communication.
The following connection variants are available for selection for terminals in HiPath 3000/5000:
● CorNet-IP connection (also as gigabit version, Page 10-5)
● TDM connection
HiPath 3000/5000 no longer supports the SIP connection variants.

>
The product family includes:
● OpenStage TDM
The OpenStage 10 (without display), 20, 40, 60 and 80 TDM models are available.
● OpenStage CorNet-IP (HFA)
The OpenStage 20, 40, 60 and 80 CorNet-IP (HFA) models are available.
The following control elements and the display guarantee convenient and interactive operation.
● 3-way navigator: OpenStage 20
● Illuminated Touch/Sensor keys for function selection and 5-way navigator: OpenStage 40
● Illuminated touch/sensor keys for function selection and a TouchGuide: OpenStage 60 and
OpenStage 80.
The programmable touch/sensor keys beside the graphic display on the OpenStage 40,
OpenStage 60 und OpenStage 80 terminals can be used as function, quick dial or lines. You
can use the self-labeling function to display the station number or function currently pro-
grammed.
The key module (OpenStage 40, OpenStage 60 and OpenStage 80) and the BLF (OpenStage
40) can be used to expand the number of function keys available.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.2.1 Gigabit variant of OpenStage terminals

The CorNet-IP connection variant is also available in a gigabit version.
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 data
packets (such as, video or audio data packets) can be transferred to the workstation PC that is
connected to the network via the OpenStage terminal. This reduces spending on inhouse ca-
bling and the IP network and at the same time increases network performance.
The gigabit Ethernet switch can only be used to advantage if the entire corporate network sup-
ports gigabit technology. CAT 5M, or even better CAT 6 network cables are essential for con-
necting the terminals. Older cable types can lead to significant speed losses.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.2.2 OpenStage terminals
10.2.2.1 OpenStage 10
Figure 10-1 OpenStage 10
HiPath 3000/5000 V7 R3 supports TDM connection variants of OpenStage 10.
Key features of OpenStage 10 TDM
Table 10-1 OpenStage 10 - Key Features
Feature Connection variant

General fea- 3 pre-programmed function keys:
tures 1 loudspeaker adjustment key (plus/minus)
2 ring tone volume adjustment keys (plus/minus)
3 freely programmable function keys:
Function, speed dial and line keys
Open listening
Suitable for wall mounting
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
HiPath 3000/5000 V7 R3 supports the CorNet-IP (HFA) and TDM connection variants of Open-
Stage 20.
Key Features for OpenStage 20 CorNet-IP (HFA) and OpenStage 20 TDM
Table 10-2 OpenStage 20 CorNet-IP (HFA) and TDM – Key Features

CorNet-IP (HFA) TDM
General fea- Tilt LCD graphics display, 24 x 2 character resolution, monochrome
tures multi-functional 3-way navigator
7 pre-programmed function keys: Disconnect, call forwarding, redial, service/
application menu, voice messages, loudspeaker, mute
Full-duplex speakerphone mode
Open listening
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


CorNet-IP (HFA) TDM
Interfaces Integrated Ethernet switch to connect
a PC
LAN port (10/100 Base-T)
IP features 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 based on DiffServ
VLAN
IEEE 802.3af Power over Ethernet
(PoE)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
HiPath 3000/5000 V7 R3 supports the CorNet-IP (HFA) and TDM connection variants of Open-
Stage 40.

CorNet-IP (HFA) TDM
General fea- Tilt LCD graphics display with background lighting, 40 x 6 character resolu-
tures tion, monochrome
multi-functional 5-way navigator
8 pre-programmed function keys: Disconnect, call forwarding, redial, service/
application menu, voice messages, loudspeaker, mute, headset
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


CorNet-IP (HFA) TDM
General fea- 6 programmable touch/sensor keys: Function, speed dial and line keys
tures Full-duplex speakerphone mode
Open listening
Interfaces Integrated Ethernet switch to connect USB slave
a PC
Port for headset
Port for key module and BLF
802.1x
VLAN
(PoE)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
OpenStage 60 is supported in the CorNet-IP (HFA) connection variant from HiPath 3000/5000
V7 R3 and in the TDM connection variant from HiPath 3000/5000 V7 R4.

CorNet-IP (HFA) TDM
General fea- Tilt TFT graphics display with background lighting, 320 x 240 character reso-
tures lution (QVGA), 16-bit color depth
multi-functional TouchGuide
6 pre-programmed function keys: Disconnect, call forwarding, voice dialing,
loudspeaker, mute, headset
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


CorNet-IP (HFA) TDM
General fea- 8 programmable touch/sensor keys: Function, speed dial and line keys
tures 6 mode keys (e.g. to launch applications)
Voice dialing
Polyphonic and mp3 ring tones supported
Open listening
Not suitable for wall mounting
a PC
USB master
Bluetooth
Port for headset
Port for key module
802.1x
VLAN
(PoE)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Figure 10-5 OpenStage 80 – CorNet-IP (HFA) connection variant pictured

OpenStage 80 is supported in the CorNet-IP (HFA) connection variant from HiPath 3000/5000
V7 R3 and in the TDM connection variant from HiPath 3000/5000 V7 R4.

CorNet-IP TDM
General fea- Tilt TFT graphics display with back- Tilt TFT graphics display with back-
tures ground lighting, 640 x 480 character ground lighting, 320 x 240 character
resolution (VGA), 16-bit color depth resolution (QVGA), 16-bit color depth
multi-functional TouchGuide
6 pre-programmed function keys: Disconnect, call forwarding, voice dialing,
loudspeaker, mute, headset
9 programmable touch/sensor keys: 8 programmable touch/sensor keys:
Function, speed dial and line keys Function, speed dial and line keys
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


CorNet-IP TDM
General fea- 6 mode keys (e.g. to launch applications)
tures Voice dialing
Polyphonic and mp3 ring tones supported
Open listening
Not suitable for wall mounting
a PC
USB master
Bluetooth
Port for headset
Port for key module
Port for OpenStage keyboard
802.1x
VLAN
(PoE)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.2.2.6 Connection and Startup
CorNet-IP connection variant (HFA)

HiPath 3000 together with HiPath Xpressions Compact supports the central administration of
the IP terminals connected to the system. For this purpose a Deployment Tool (DLS Interface
DLI) has been implemented on the HiPath Xpressions Compact boards. The DHCP and FTP
servers integrated in DLI support the following:
● the central configuration of parameters for all IP terminals connected enabling plug&play
operation
● the central software update of all IP terminals connected
For information about the prerequisites for using the DLI function, see Section 10.4.
The DLI function can only be used for standalone systems.

> The Deployment and Licensing service is available for networked HiPath 3000 sys-
tems with or without HiPath 5000 RSM. The Deployment and Licensing service can
also be used for systems that do not satisfy the prerequisites for using the DLI func-
tion. For information on how to use this tool, see the Deployment Service Adminis-
trator Manual.
For information about OpenStage terminal administration, see CorNet-IP Connection Variants
in the OpenStage Administrator Manual.
TDM connection variants

After connecting the terminal, all LEDs on the terminal and all LEDs on any other add-on de-
vices connected light up (the LEDs on add-on device do not have to flash in synchronism with
workpoint LEDs). All pixels on the display also activate briefly.
These indications show that the telephone is starting up and performing a self-test. Download-
ing has finished and the telephone is ready for operation when you see the date and time on
the display.
Use HiPath 3000/5000 to configure the OpenStage terminals for HiPath 3000/5000 Manager E.
Administration and Software Upgrade

For the CorNet-IP connection variant (HFA) the administration and software upgrade is enabled
by the Deployment and Licensing Service. The relevant information is provided in the Deploy-
ment Service Administrator Manual.
Software image releases are available on the MMC for the TDM connection variants.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Download
The manuals and tools mentioned can be downloaded here:
http://www.enterprise-communications.siemens.com/global/Products.aspx (... -> Downloads).
10.2.2.7 Connections on the Bottom of the Telephone
OpenStage 20, OpenStage 40 (CorNet-IP connection variant): Connections
The connections in Figure 10-6 marked with "(*)" are not available for the
> OpenStage 20 (connection variant CorNet-IP) terminal.
(*)
(*)
Figure 10-6 OpenStage 40 (CorNet-IP Connection Variant) – Connections on Telephone

Bottom
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
OpenStage 60, OpenStage 80 (CorNet-IP connection variant): Connections
Figure 10-7 OpenStage 60, OpenStage 80 (CorNet-IP Connection Variant) – Connections

on Telephone Bottom
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

OpenStage 10, OpenStage 20, OpenStage 40 (TDM connection variants): Connections
The connections in Figure 10-8 marked with "(*)" are not available for the
> OpenStage 10 and OpenStage 20 (TDM connection variants).
(*)
(*)
(*)
Figure 10-8 OpenStage 40 (TDM Connection Variant) – Connections on Telephone Bottom
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
OpenStage 60, OpenStage 80 (TDM connection variant): Connections
Figure 10-9 OpenStage 60, OpenStage 80 (TDM Connection Variant) – Connections on

Telephone Bottom
OpenStage-Terminals - Description of Connections
Connection Terminal De- Description

designation vices
OpenStage 40 Connection for add-on device
OpenStage 60
OpenStage 80
Table 10-6 OpenStage-Terminals - Description of Connections
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


designation vices
OpenStage 10 ● CorNet-IP connection variant:
OpenStage 20 Connection for an external power supply unit. Section
OpenStage 40 10.2.4 contains information about the cases in which an
OpenStage 60 external power supply unit is required.
OpenStage 80 ● TDM connection variant:
– Additional power supply not required: Connection
to HiPath 3000
– Additional power supply required: Connection to an
external power supply unit. Section 10.2.4 contains
information about the cases in which an external
power supply unit is required.
– Port on OpenStage PhoneAdapter
OpenStage 60 USB port:
OpenStage 80
OpenStage 60 Connection for external keyboard

OpenStage 80
OpenStage 20 CorNet-IP connection variant: Connection for PC

OpenStage 40
OpenStage 60
OpenStage 80
OpenStage 20 CorNet-IP connection variant: LAN connection

OpenStage 40
OpenStage 60
OpenStage 80
OpenStage 40 Port for headset

OpenStage 60
OpenStage 80
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

designation vices
OpenStage 10 Handset port
OpenStage 20
OpenStage 40
OpenStage 60
OpenStage 80
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.2.3 OpenStage Add-On Devices
Caution
7 Always disconnect the line cord before connecting add-on devices to the terminal.
10.2.3.1 OpenStage Key Module
Figure 10-10 OpenStage Key Module

The OpenStage Key Module is an add-on device that should be mounted on the side of the ter-
minal; it provides an additional 12 programmable function keys. In connection with the integrat-
ed level function, it is possible to use a total of 22 numbers of any key functions.
Section 10.2.4 contains information about the configuration at which an additional power supply
using an external power supply is required.
10.2.3.2 OpenStage BLF
Figure 10-11 OpenStage BLF
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
The OpenStage BLF (Busy Lamp Field) is an add-on device that should be mounted on the
side of the terminal. It has an additional 90 programmable function keys.
An external power supply unit is required to ensure sufficient power is supplied to operate the
BLF. Only use the original power supply unit for this, see Section 10.2.5.1, “External Power
Supply”. The AC adapter port depends on the OpenStage BLF hardware output.
The busy lamp field cannot be combined with the key module.
10.2.3.3 Possible Configurations for the Key Modules

The following table shows the permitted configurations of add-on devices at OpenStage termi-
nals for TDM and CorNet-IP connection variants. Add-on devices cannot be used on tele-
phones that are not listed here.
Table 10-7 OpenStage Terminals - Add-on Device Configurations
Telephone 1. Key module 2. Key module

OpenStage 40 OpenStage Key Module 40
OpenStage BLF –
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.2.4 Power supply of the OpenStage terminals, add-on devices, and

adapters
Both the following tables provide information on the configurations at which a power supply is
required using an external power supply. For the additional power supply, use only the associ-
ated original power supply (see Section 10.2.5.1, “External Power Supply”).
CorNet-IP connection variants
Telephone Configuration Additional pow- Note

er supply re-
quired?
OpenStage 20 – No1
Gigabit variant
1 X OpenStage key No2
module
2 X OpenStage No2
Key Module
1 X OpenStage BLF Yes, for ● OpenStage BLF up to an includ-
OpenStage BLF ing hardware output S30817-
S7406-A101-7/-A103-2: The
external power supply unit is
connected to the BLF. Caution:
The power supply unit used
should only be used for this pur-
pose. Using the free jack of the
power supply unit to power an-
other terminal or device is not
permitted and can lead to the
destruction of the OpenStage
BLF.
● OpenStage BLF from HW out-
put S30817-S7406-A101-8/-
A103-3: The external power
supply unit is connected to the
terminal (see Figure 10-12).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

er supply re-
quired?
Gigabit variant 1 X OpenStage key No3
module
2 X OpenStage No3
Key Module
1 X OpenStage BLF Yes, for ● OpenStage BLF up to an includ-
OpenStage BLF ing hardware output S30817-
S7406-A101-7/-A103-2: The
external power supply unit is
connected to the BLF. Caution:
The power supply unit used
should only be used for this pur-
pose. Using the free jack of the
power supply unit to power an-
other terminal or device is not
permitted and can lead to the
destruction of the OpenStage
BLF.
● OpenStage BLF from HW out-
put S30817-S7406-A101-8/-
A103-3: The external power
supply unit is connected to the
terminal (see Figure 10-12).
module
2 X OpenStage No3
Key Module
module
2 X OpenStage Yes The external power supply unit is
Key Module connected to the terminal
(see Figure 10-12)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


er supply re-
quired?
module
2 X OpenStage No3
Key Module
module
2 X OpenStage Yes The external power supply unit is
Key Module connected to the terminal
(see Figure 10-12)
1 PoE class 1: PD maximum power = 0.44 W through 3.84 W, nominal classification signature current = 10.5 mA
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
TDM connection variants

er supply re-
quired?
OpenStage 10 – No
OpenStage 20 – No
1 x OpenStage Yes The external
PhoneAdapter power supply unit is connected di-
rectly to the OpenStage Phone-
Adapter.
OpenStage 40 – No
1 x OpenStage Yes Connecting an External Power Sup-
Key Modules ply Unit (see Figure 10-13)
2 x OpenStage Yes
Key Modules
1 X OpenStage BLF Yes, for ● OpenStage BLF up to an in-
OpenStage BLF cluding hardware output
S30817- S7406-A101-7/-A103-
2:
The external power supply unit
is connected to the BLF.
Caution: The power supply
unit used should only be used
for this purpose. Using the free
jack of the power supply unit to
power another terminal or de-
vice is not permitted and can
lead to the destruction of the
OpenStage BLF.
● OpenStage BLF from hardware
output S30817-S7406-A101-8/
- A103-3:
The external power supply unit
is connected to the terminal
(see Figure 10-13).
1 x OpenStage Yes
PhoneAdapter
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm


er supply re-
quired?
OpenStage 60 – Yes The external power supply unit is
1 x OpenStage Yes connected to the terminal (see
Key Modules Figure 10-13)
2 x OpenStage Yes
Key Modules
1 X OpenStage USB Yes
Extension
2 x OpenStage Yes
Key Modules +
1 x OpenStage USB
Extension
Adapter.
OpenStage 80 – Yes The external power supply unit is
1 x OpenStage Yes connected to the terminal (see
Key Modules Figure 10-13)
2 x OpenStage Yes
Key Modules
1 X OpenStage USB Yes
Extension
2 x OpenStage Yes
Key Modules +
1 x OpenStage USB
Extension
Adapter.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.2.5 OpenStage Accessories
10.2.5.1 External Power Supply

In case of certain configurations, an external power supply unit is required (see Section 10.2.4).
The AC adapter features two MW6 connectors.
With the additional power supply of the OpenStage BLF, the connection of the power supply
unit depends on the hardware output of the OpenStage BLF:
Caution
7 The power supply unit used for an OpenStage BLF should only be used for this pur-
pose. Using the free jack of the power supply unit to power another terminal or de-
vice is not permitted and can lead to the destruction of the OpenStage BLF.
● OpenStage BLF up to an including hardware output S30817-S7406-A101-7/-A103-2:
The external power supply unit is connected directly to the OpenStage BLF. The left jack
of the power supply unit labelled "Digital" (Figure 10-13 for the TDM connection variant)
must be connected to the BLF.
● OpenStage BLF from hardware output S30817-S7406-A101-8/-A103-3:
The OpenStage BLF is powered by the associated terminal. The power supply unit
(Figure 10-12 for CorNet-IP connection variant) should be connected to the terminal.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

OpenStage terminals with the CorNet-IP connection variant
to the OpenStage
terminal: Connector
socket
Figure 10-12 OpenStage terminals (CorNet-IP Connection Variant) – Connection of the Ex-
ternal Power Supply Unit
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
OpenStage terminals with TDM connection variant
to the system
HiPath 3000
to the OpenStage terminal:

Connector socket
Figure 10-13 OpenStage terminals (TDM Connection Variant) – Connection of the External
Power Supply Unit
Variants
● AC adapter, Euro: C39280-Z4-C510
● AC adapter, UK: C39280-Z4-C512
● AC adapter, 110 V USA: C39280-Z4-C511
Technical specifications AC adapter, Euro: AC adapter, UK: AC adapter, 110 V

C39280-Z4-C510 C39280-Z4-C512 USA:
C39280-Z4-C511
Line voltage 230 Vac 230 Vac 120 VAC
Line frequency 50 Hz 50 Hz 60 Hz
Output voltage max. 43 Vdc, max. 43 Vdc, max. 43 Vdc,
min. 30 Vdc min. 30 Vdc min. 30 Vdc
Output current 480 mA 480 mA 480 mA
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.2.5.2 OpenStage PhoneAdapter
Output Output Input

Analog UP0/E slave UP0/E
Switch Output Power Supply
analog/UP0/E slave UP0/E master
Figure 10-14 OpenStage PhoneAdapter

The OpenStage PhoneAdapter is used to connect a second OpenStage (TDM) terminal (UP0/
E or analog connection) with its own power supply.
The system treats the OpenStage telephone as an independent telephone with a separate
phone number and its own B channel. The OpenStage telephone can send and receive calls
regardless of the connection status of the host telephone.
The OpenStage PhoneAdapter can be operated only in the following combinations:
● An OpenStage TDM phone (UP0/E master)
● Two OpenStage TDM phones (UP0/E master, UP0/E slave)
● One OpenStage TDM telephone and an analog terminal (UP0/E master, a/b).
It is not possible to simultaneously operate two system telephones and an analog

> device.
T/R interface properties

The pin assignment of the modular jacks can be different on analog devices. Compare the pin
assignment below with the pin assignment of your analog terminal.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Pin assignment of the Western Modular jack (RJ12):
Pin Signal
1 Free
2 Free
6 1
3 a
4 b
5 Free
6 Free
Figure 10-15 Western-Modular jack (RJ12)

The properties of the T/T interface are:
● 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 T/R interface, message waiting lamp, dictating
equipment, speaker, announcement device (such as start/stop).
If the pins 3 and 4 are used on your analog device, you can use the supplied connection cable.
10.2.5.3 Acoustic Unit
Figure 10-16 Acoustic Unit
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

The acoustic unit combines a loudspeaker and microphone in a housing designed to blend in
with the OpenStage product family. The acoustic unit features a mute key in addition to a vol-
ume adjuster.
10.2.5.4 Headsets
Figure 10-17 Headsets

The integrated Bluetooth technology supports user-friendly headsets.
The OpenStage 40/60/80 terminals are each equipped with a jack to connect corded (121 TR
9-5) and cordless headsets (121 TR 9-5).
Note: The headset ports for OpenStage terminals are coded RJ45 jacks. The headset connec-
tors have RJ11 or RJ45 connectors. If there are contact problems (RJ45 jack <–> RJ11 con-
nector), swat the RJ11 connector of the affected headset for an RJ45 connector. A coded RJ45
connector can be ordered using the part number C39334- Z93-C350 (normal RJ45 ISDN con-
nectors do not fit).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.2.5.5 Keyboard
Figure 10-18 Keyboard

The OpenStage keyboard is available in two different layouts (QWERTZ and QWERTY).
10.2.5.6 USB Extension
Figure 10-19 USB Extension

The USB extension operates as a USB hub for connecting additional USB devices, such as,
WLAN dongles or USB memory sticks. The integrated Class-D amplifier provides optimized re-
cording and voice transmission quality with a connected microphone. It also improves the
sound quality in connected loudspeakers and speakerphone systems.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.2.6 Updating Software for the TDM OpenStage Telephone Service
10.2.6.1 Automatic and Manual Software Update

TDM OpenStage telephones and TDM OpenStage Extenders that are connected to a HiPath
3000 system can be updated on site or via remote control using a new software application; the
new software application must be loaded onto the system with Manager E and then loaded onto
the system’s MMC.
Once this step is complete, the update operation can be initiated automatically or manually
from Manager E. An entry in the customer database permits or denies automatic software up-
dates. If updates are permitted, you can choose either an immediate or scheduled update. In
the case of the former, the telephones are reset and updated if they are ready to be loaded; in
the case of the latter, they are reset and updated on a specific day.
This automatic procedure only updates telephones with an older software version; telephones
with a newer version remain unchanged.
The manual update is initiated on Manager E using orders; these offer three update options:
immediate, scheduled or during the next reset; they also offer an option for selecting specific
telephones. Downgrading to an older software version can only be performed with orders.
To minimize the impact on ongoing telephone calls, the software update is split into different
stages; first the software is downloaded from the MMC to a telephone and then copied from
telephone to telephone in the B channel. The download operation itself does not affect the tele-
phone user. (Exception: master/slave configurations only support one call during a download
operation.)
The current status of the TDM OpenStage software update can be checked on Manager E. An
update log file is also saved on the MMC and can be read over Manager E.
10.2.6.2 Accessing TDM OpenStage Hardware and Software Version Information

The hardware version (Siemens part number) and the software version of the OpenStage tele-
phones are saved in the customer database and can be accessed by Manager E.
10.2.6.3 Accessing the TDM OpenStage Update Log File

TDM OpenStage telephones and the Extender keep an update log file that can be called up
over Manager E for maintenance purposes.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 410 / optiPoint 410 S and optiPoint 420 / optiPoint 420 S
10.3 optiPoint 410 / optiPoint 410 S and optiPoint 420 / optiPoint 420 S
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 a simple, familiar way over a data network.
Convenient and interactive operation is ensured by the three dialog keys and the display (not
available for optiPoint 410 entry and optiPoint 410 entry S). Furthermore, the key lamp princi-
ple visualizes the activated functions.
The difference between the optiPoint 410/optiPoint 410 S and optiPoint 420/optiPoint 420 S
families lies in the design of the function key panels:
● optiPoint 410/optiPoint 410 S families: the function keys have panels with labeling strips
on which the function or call number currently saved 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 the
function or call number currently saved is shown.
The add-on device optiPoint self-labeling key module allows you to increase the number of
function keys available for the telephone types standard and advance. The add-on devices op-
tiPoint key module and optiPoint BLF can also be used with the optiPoint 410/optiPoint 410 S
and optiPoint 420/optiPoint 420 S families.
The optiPoint 410 display module is used as an add-on device for telephone types standard
and advance. Its graphical LCD display (320 x 240 dots), the touchscreen and the navigation
keys mean that many functions can be used intuitively and therefore more effectively.
The use of different optiPoint 500 adapters allows flexibility for the expansion of the telephone
workstation (not for telephone types entry, economy, and economy plus).
Differences between the optiPoint 410/optiPoint 420 and optiPoint 410 S/optiPoint 420 S fam-
ilies:
● optiPoint 410/optiPoint 420 families: All HiPath 3000/5000 features that are offered inter-
actively on the display, in the service menu, and on function keys are available (except for
Relocate).
● optiPoint 410 S/optiPoint 420 S families: The corresponding telephones support SIP (Ses-
sion Initiation Protocol). SIP is an ASCII-based signal used to set up sessions in an IP net-
work.
Note: The term "Internet telephony" as used in this document refers to making telephone
calls via IP-supported networks (Voice over IP) and signaling via SIP.
The following features for Internet telephony stations are actively supported:
– CLIP (displays the calling party’s station number on the called party’s station)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

– CLIP (suppresses the calling party’s station number on the called party’s station)
– COLP (displays the called party’s station number on the calling party’s station)
– COLR (suppresses the called party’s station number on the calling party’s station)
– Consultation hold
– Hold
– Toggle
– Transfer (transfer after messaging)
– DISA (Direct Inward System Access): No features may be activated for the SIP tele-
phone
– Inband DTMF
Although Internet telephony stations may not activate the following features, they may be
passively 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
telephony 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 (the Internet telephony station can be implemented in au-
tomatic COS changeover)
– Internal traffic restriction (ITR) groups (Internet telephony stations may be implement-
ed in ITR groups)
The following restrictions apply to Internet telephony stations:
– Internet telephony stations are configured in HiPath 3000/5000 Version 3.0 as DSS1
(functional telephone) and therefore cannot be supervised by the system (no monitor-
ing). Internet telephony 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 operat-
ed with codes.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
– Music is played when an Internet telephony station is on hold. Music is not played and
a ring tone is not applied for the Internet telephony station when unscreened transfer
is performed between the Internet telephony station and another station.
– The display on the Internet telephony station is not refreshed if an Internet telephony
station is unparked by a different party to the one who parked it.
– SIP devices are not supported by the Deployment Tool (DLS Interface, DLI) in HiPath
Xpressions Compact boards (HiPath 3000).
– In some situations, you cannot use terminal-specific features in HiPath 3000/5000 Ver-
sion 3.0 This includes features offered via the device’s menu interface. The features
available with the basic system HiPath 3000/5000 Version 3.0 have general release
status.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.1 optiPoint 410 and optiPoint 410 S Telephones
10.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 LEDs
● 2 volume adjustment keys (plus/minus) and pitch
● Suitable for wall mounting
● No modularity (no connecting capability for adapters or key modules), no display
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 410 entry, optiPoint 410 entry S
optiPoint 410 entry

Consultation hold
Redial
Message
Callback
Speed dialing
Microphone on/off
Loudspeaker
Disconnect
optiPoint 410 entry S

Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Cancel
Level
Figure 10-20 optiPoint 410 entry, 410 entry S - Standard Key Assignment
Refer to Section 10.3.3 for information on connection and startup.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.1.2 optiPoint 410 economy, optiPoint 410 economy S
Main features
● Protocols
● CTI (for example, via TAPI 3rd party)
● Alphanumeric LCD display (swivel) with 2 lines, 24 characters each
● 3 dialog keys for interactive user prompts: “Yes”, “Back”, and “Next”
● Open listening
● 2 volume adjustment keys (plus/minus), pitch and display contrast
● No modularity (no connecting capability for adapters or key modules)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 410 economy, optiPoint 410 economy S
optiPoint 410 economy

Service Programmable
Redial Programmable
Microphone on/off Programmable
Loudspeaker Programmable
Programmable
Programmable
Programmable
Disconnect
optiPoint 410 economy S

Redial Programmable
Caller list Programmable
Programmable Programmable
Programmable
Programmable
Cancel
Level
Figure 10-21 optiPoint 410 economy, 410 economy S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.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-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 410 economy plus,

optiPoint 410 economy plus S
optiPoint 410 economy plus

Redial Programmable
Programmable
Programmable
Programmable
Disconnect

Redial Programmable
Programmable
Programmable
Cancel
Level
Figure 10-22 optiPoint 410 economy plus, 410 economy plus S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.1.4 optiPoint 410 standard, optiPoint 410 standard S
Main features
● Protocols
● Full-duplex speakerphone mode with echo suppression for room adaptation
● 2 volume adjustment keys (plus/minus), pitch, speaker quality and display contrast
● Modularity:
– 2 option bays
– 1 interface for up to 2 add-on devices
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 410 standard, optiPoint 410 standard S
optiPoint 410 standard

Redial Programmable
Programmable
Programmable
Programmable
Disconnect
optiPoint 410 standard S

Redial Programmable
Programmable
Programmable
Cancel
Level
Figure 10-23 optiPoint 410 standard, 410 standard S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.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 option bay
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 410 advance, optiPoint 410 advance S
optiPoint 410 advance

Redial Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Disconnect
optiPoint 410 advance S

Redial Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Cancel
Level
Figure 10-24 optiPoint 410 advance, 410 advance S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.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.
10.3.2.1 optiPoint 420 economy, optiPoint 420 economy S
Main features
● Protocols
● 12 function keys with LEDs and self-labeling keys
● Open listening
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 420 economy, optiPoint 420 economy S

Redial Programmable
Mailbox Programmable
Programmable
Disconnect

Redial Programmable
Cancel
Level
Figure 10-25 optiPoint 420 economy, 420 economy S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.2.2 optiPoint 420 economy plus, optiPoint 420 economy plus S
Main features
● Protocols
● Open listening
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 420 economy plus,

optiPoint 420 economy plus

Redial Programmable
Programmable
Disconnect

Redial Programmable
Cancel
Level
Figure 10-26 optiPoint 420 economy plus, economy plus S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.2.3 optiPoint 420 standard, optiPoint 420 standard S
Main features
● Protocols
● Modularity:
– 2 option bays
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 420 standard, optiPoint 420 standard S

Redial Programmable
Programmable
Disconnect

Redial Programmable
Cancel
Level
Figure 10-27 optiPoint 420 standard, 420 standard S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.2.4 optiPoint 420 advance, optiPoint 420 advance S
Main features
● Protocols
● 1 integrated USB 1.1 interface
● Modularity:
– 1 option bay
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Standard key assignment (default) for optiPoint 420 advance, optiPoint 420 advance S

Redial Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Disconnect

Redial Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Cancel
Level
Figure 10-28 optiPoint 420 advance, 420 advance S - Standard Key Assignment
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.3 Connection and Startup
optiPoint 410, optiPoint 420

HiPath 3000 together with HiPath Xpressions Compact supports the central administration of
the IP terminals connected to the system. For this purpose a Deployment Tool (DLS Interface
DLI) has been implemented on the HiPath Xpressions Compact boards. The DHCP and FTP
servers integrated in DLI support the following:
● the central configuration of parameters for all IP terminals connected enabling plug&play
operation
● the central software update of all IP terminals connected
For information about the prerequisites for using the DLI function, see Section 10.4.

> The Deployment and Licensing service is available for networked HiPath 3000 sys-
tems with or without HiPath 5000 RSM. The Deployment and Licensing service can
also be used for systems that do not satisfy the prerequisites for using the DLI func-
tion. For information on how to use this tool, see the Deployment Service Adminis-
trator Manual.
For information on terminal administration, refer to the optiPoint 410/420 Administrator Manual.
optiPoint 410 S, optiPoint 420 S

For information on how to connect and start up terminals, refer to the optiPoint 410 S/420 S
Administrator Manual:
The software can be upgraded over:
● the Deployment and Licensing service
Information on the procedure can be found in the Deployment Service Administration Man-
ual.
● the WBM access at the relevant optiPoint IP telephone.
The optiPoint 410 S/420 S Administrator Manual contains information on this procedure.
Download
The manuals and tools mentioned can be downloaded here:
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 410 entry, optiPoint 410, 420 standard,

optiPoint 410 entry S optiPoint 410, 420 standard S
optiPoint 410, 420 advance,

optiPoint 410, 420 advance S
Figure 10-29 optiPoint 410, 420, 410 S, 420 S - Connection Options
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Table 10-8 optiPoint 410/420, optiPoint 410 S/420 S - Description of Connections
No. Connection
1 Ethernet (10/100BaseT) interface (self-configuring) for the LAN
2 Handset
3 Local power supply (optional)1
4 Key module
5 Ethernet (10/100BaseT) interface (self-configuring) for the PC
6 Headset (121 TR 9-5)
7 Adapter 1
8 Adapter 2
9 USB interface
1 No local power supply is required if power is provided via the Ethernet cable (Power over LAN).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.3.4 Key programming

Double assignment of the programmable function keys on the optiPoint 410 and optiPoint 420
telephones, the optiPoint key module and the optiPoint self labeling key module is possible.
Please note the following differences between the functions:
● Up to and including V6.0 SMR-05:
Double assignment is possible if only phone numbers without LED support are saved on
the first level. It is also possible to program call numbers without LED support on the sec-
ond level. These can be internal station numbers, DID call numbers and call numbers from
a HiPath network.
● V6.0 SMR-06 and later:
One of the two following options can be configured using HiPath 3000/5000 Manager E
(Settings menu: System Parameters (Flags)):
– The "Enhanced key functionality" flag is not activated (default setting).
This will produce the same behavior as in versions up to and including V6.0 SMR-05.
– The "Enhanced key functionality" flag is activated.
Once you have defined a key of your choice as the "Shift key", only phone numbers
without LED support can be saved at the second key level which is now available. You
can program any key functions on the first key level. LED signaling is associated with
the first key level only.
When the Shift function is pressed, the LED associated with the Shift key lights up. This signals
that the phone numbers on the second key level are available. When you switch key levels, the
key labels on telephones with self-labeling keys also change.
The Shift function is deactivated when you press a phone number or if you press the Shift key
again.
The optiPoint BLF function keys cannot have double assignments.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.5 Key modules for optiPoint 410/410 S and 420/420 S
Caution
7 Always disconnect the line cord before connecting add-on devices to the telephone.
The user usually installs the add-on devices. The installation instructions are on the “Electronic
Operating Instructions” CD.
Up to two key modules may be mounted on an optiPoint 410/optiPoint 410 S or op-

> tiPoint 420/optiPoint 420 S terminal (not optiPoint 410 entry, optiPoint 410 entry S,
optiPoint 410 economy, optiPoint 410 economy S, optiPoint 410 economy plus, op-
tiPoint 410 economy plus S, optiPoint 420 economy, optiPoint 420 economy S, op-
tiPoint 420 economy plus or optiPoint 420 economy plus S).
optiPoint key module, optiPoint BLF, and optiPoint application module (V5.0 SMR-
06 and later) can be used in addition to the two add-on devices described below.
Table 10-9 shows the possible add-on device configurations.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.3.5.1 optiPoint self labeling key module

The optiPoint self labeling key module is an add-on device that should be mounted on the side
of the telephone; it provides an additional 13 keys, LEDs, and displays for all purposes. Self-
labeling key means that each key is assigned a display (one line with 12 characters) in which
the function or call number currently saved is shown.
Figure 10-30 optiPoint self labeling key module

Information on double assignment can be found in Section 10.3.4.
The bottom key of the first key module installed on the telephone (optiPoint self-labeling key
module or optiPoint key module) is automatically defined as “Shift key” (default). This is the
case if no Shift key was already programmed.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.5.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.
Figure 10-31 optiPoint 410 display module
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
Connection
The optiPoint 410 display module must always be installed as the first add-on device, in other
words, connected directly to the telephone.
The connection to the telephone is made over an interface cable with the following connectors:
RJ11 input (MW6), RJ45 output (MW8). Power is supplied by the connected telephone.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

The following table shows the possible add-on device configurations for telephones from the
optiPoint 410/optiPoint 410 S and optiPoint 420/optiPoint 420 S families. Add-on devices can-
not be used on telephones that are not listed here.
Table 10-9 Add-On Device Configurations for optiPoint 410/410 S and optiPoint 420/
420 S
optiPoint 410/optiPoint 410 S 1. Key module 2. Key module

telephone
optiPoint 420/optiPoint 420 S
telephone
optiPoint key module –
optiPoint key module optiPoint key module
optiPoint key module optiPoint BLF
optiPoint 410 standard S optiPoint 410 display module –
optiPoint 410 display module optiPoint key module
optiPoint 410 display module optiPoint BLF
optiPoint 410 display module optiPoint self labeling key
optiPoint 420 standard module
optiPoint 420 standard S optiPoint BLF –
optiPoint 420 advance optiPoint BLF optiPoint BLF1

optiPoint 420 advance S optiPoint self labeling key –
module
optiPoint self labeling key optiPoint self labeling key
module module
optiPoint 410 standard optiPoint application module –
optiPoint application module optiPoint key module
optiPoint application module optiPoint BLF
optiPoint 420 standard optiPoint application module optiPoint self labeling key
module
1 Configuration with two optiPoint BLFs only with HiPath 3800
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.3.6 Use of optiPoint 500 Adapters

The following optiPoint 500 adapters are available for use on telephones from the optiPoint
410/optiPoint 410 S and optiPoint 420/optiPoint 420 S families (not optiPoint 410 entry, opti-
Point 410 entry S, optiPoint 410 economy, optiPoint 410 economy S, optiPoint 410 economy
plus, optiPoint 410 economy plus S, optiPoint 420 economy, optiPoint 420 economy S, opti-
Point 420 economy plus or optiPoint 420 economy plus S):
● optiPoint acoustic adapter
Note: Floating contacts are not supported when using the adapter on optiPoint 410/opti-
Point 410 S and optiPoint 420/optiPoint 420 S.
● optiPoint recorder adapter
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Central Administration of IP Workpoints via the System
10.4 Central Administration of IP Workpoints via the System

From V6.0 HiPath 3000 together with HiPath Xpressions Compact supports the central admin-
istration of IP workpoints connected to the system. For this purpose a Deployment Tool (DLS
Interface DLI) has been implemented on the HiPath Xpressions Compact boards listed below.
The DHCP and FTP servers integrated in DLI support the following:
● the central configuration of parameters for all IP workpoints connected enabling plug&play
operation.
● the central software update of all IP workpoints connected.
Prerequisites
● HiPath 3000, V6.0 or later
The following systems support the DLI function:
– HiPath 3800, with the HiPath Xpressions Compact board IVMNL and the HG 1500
board STMI2
– HiPath 3550, with the HiPath Xpressions Compact board IVMS8N or IVMP4 and the
HG 1500 board HXGS3
– HiPath 3500, with the HiPath Xpressions Compact board IVMS8NR or IVMP4N and
the HG 1500 board HXGR3

> The Deployment and Licensing service is available for networked HiPath 3000
systems with or without HiPath 5000 RSM. For information on how to use this
tool, see the Deployment Service Administrator Manual.
● HiPath Xpressions Compact, V2.5 and later
● HG 1500, V3.0 or later
● IP workpoints
Central administration can be performed for the following IP workpoints over the DLI func-
tion:
– OpenStage 20 (HFA), from V1 R0.1.41
– optiClient 130, V5.0 and later
– optiPoint 410 entry V5.0 and later
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

– optiPoint 410 economy V5.0 and later

– optiPoint 410 economy plus V5.0 and later
– optiPoint 410 standard V5.0 and later
– optiPoint 410 advance V5.0 and later
– optiPoint 420 economy V5.0 and later
– optiPoint 420 economy plus V5.0 and later
– optiPoint 420 standard V5.0 and later
– optiPoint 420 advance V5.0 and later
sions.
10.4.1 Plug’n Play Startup of IP Workpoints
Procedure
1. When you connect an IP workpoint, it receives both it’s own IP address as well as that of
the DLI by contacting the DHCP server implemented on the HiPath Xpressions Compact
board.
2. The IP workpoint registers with the Deployment service (DLI) within HiPath Xpressions
Compact.
3. The Deployment Service checks whether it is necessary to configure the default values for
the IP workpoint (for example, if this is the first startup).
Note: For IP workpoint configuration, a template in XML format is defined for each IP work-
point type and stored in the HiPath Xpressions Compact file system. There is exactly one
template per supported IP workpoint type, regardless of the software version.
The first time that an IP workpoint is started, the Deployment Service checks whether there
is a suitable template for this type. If a template exists, the IP workpoint is supported and
the configuration data from the template and the plug&play data (such as, the gatekeeper
address) are supplied to the IP workpoint.
If this is an IP workpoint type for which no template is available, a general template is pro-
vided.
Each additional logon with the Deployment service results in a plug&play-only configura-
tion (supply of gatekeeping address, etc.). In this way, the attributes assigned by template
and changed locally on the IP workpoint are not overwritten by the Deployment service with
each new logon.
4. The Deployment Service sends configuration data from the matching template together
with the Plug’n Play data to the IP workpoint.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
5. The IP workpoint logs on to the gateway and is operational.
HiPath Xpressions Compact does not save local changes to IP workpoint parame-
> ters (for example, those made via the telephone keypad or WBM access on the IP
workpoint).
If an IP workpoint is replaced because of a defect, the local changes must be en-
tered on the replacement device.
Plug’n Play configuration of SIP-based workpoints is not possible.
10.4.2 Software Upgrade of IP Workpoints via the System
Notes
Each of the IP workpoint types supported requires different software (image file).
The image files are usually generated with vxWorks.app. You do not have to rename the im-
age files because the files are assigned a new name when saved on the hard disk on the Hi-
Path Xpressions Compact board.
The HiPath Xpressions Compact board’s hard disk has enough space for a number of black-
and-white images at once. Only IVMP4 and IVMP4N boards generate an error message when
there is not enough space for image files (currently around 200 MB is available).
Procedure
1. The SW images from the new software version are available and are loaded onto the hard
disk on the HiPath Xpressions Compact board. A separate DLI-WBM is available for this.
The DLI WBM is accessed via
https://<IP address of the HiPath Xpressions Compact board>/dli.
2. The HiPath Xpressions Compact’s internal Deployment service checks whether the soft-
ware image is available in a valid format. If this is not the case, an appropriate error mes-
sage is generated for the user by the DLI-WBM.
Note: A software upgrade is only possible within a main version (example: update from
V5.1.0 to V5.3.4).
The HiPath Xpressions Compact’s internal Deployment service does not support main-ver-
sion upgrades or migrations (software type changes).
3. The HiPath Xpressions Compact’s internal Deployment service prompts all registered IP
workpoints that are to be equipped with the new software to start software deployment.
4. The IP workpoints in question download the software image from the HiPath Xpressions
Compact’s internal FTP server and start a reboot.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

5. After booting, the IP workpoints reregister with the HiPath Xpressions Compact’s internal
Deployment service. Based on the registration data, the Deployment service recognizes
whether the new software was successfully installed; it then outputs the appropriate mes-
sage via the DLI-WBM.
You can use Web-based Management to display information on all registered IP workpoints
and their software deployment status.
Software cannot be upgraded for SIP-based workpoints.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 150 S
10.5 optiPoint 150 S

optiPoint 150 S is the cost-effective entry model for Voice over IP telephony using SIP (Session
Initiation Protocol).
Note: The term "Internet telephony" as used in this document refers to making telephone calls
via IP-supported networks (Voice over IP) and signaling via SIP.
The following features for Internet telephony stations are actively supported:
● CLIP (displays the calling party’s station number on the called party’s station); Standalone
systems only.
● COLP (displays the called party’s station number on the calling party’s station)
● Consultation hold
● Hold
● Toggle
● Transfer (transfer before answer and transfer after messaging)
● DISA (Direct Inward System Access): No features may be activated for optiPoint 150 S
● Inband DTMF: optiPoint 150 S only supports the codec G.711
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)
● Automatic COS changeover (the Internet telephony station can be implemented in auto-
matic COS changeover)
● Internal traffic restriction (ITR) groups (Internet telephony stations may be implemented in
ITR groups)
The following telephone-specific optiPoint 150 S features are supported in HiPath 3000/5000
from V6.0 SMR-09 or later:
● Missed Calls List, telephone
● Do Not Disturb (DND)
● Call Duration Display
● Local Numbering Plan
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 150 S
● Microphone on/off
● Select language
The following restrictions apply to Internet telephony stations:
● Internet telephony stations are configured in HiPath 3000/5000 Version 3.0 as DSS1 (func-
tional telephone) and therefore cannot be supervised by the system (no monitoring). Inter-
net telephony 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 operated
with codes.
● Music is played when an Internet telephony station is on hold. Music is not played and a
ring 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 devices are not supported by the Deployment Tool (DLS Interface, DLI) in HiPath
Xpressions Compact boards (HiPath 3000).
● optiPoint 150 S allows you to toggle between two external calls. The active call can be
cleared down by briefly pressing the hookswitch. Simply replace the optiPoint 150 S hand-
set to connect the two external parties to each other (this may incur 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 in HiPath 3000/5000 Version
3.0 This includes features offered via the device’s menu interface. The features available
with the basic system HiPath 3000/5000 Version 3.0 have general release status.
Main features
● Protocols
– SIP
– QoS in accordance with VLAN, TOS, and DiffServ
● Voice compression G.711 µ-law, G.711 a-law, G.723.1, G.729 AB
● Power over LAN in accordance with IEEE802.3af
● One Ethernet (10/100BaseT) interface for LAN connection
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 150 S
● 2-line alphanumeric LCD display with 16 characters per line

● Available display languages: German and English
● Preprogrammed function keys for loudspeaker, redial, hold, menu, and callback.
optiPoint 150 S
Figure 10-32 optiPoint 150 S
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 600 office
10.6 optiPoint 600 office

The optiPoint 600 office phone is the high-end product to complete the optiPoint 500 family and
is the successor of the optiset E memory.
From HiPath 3000/5000 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. Back-
ground lighting with approximately 5 s ghosting.
● Interfaces and slots:
– 1 integrated USB 1.1 interface
– 1 option bay
– 1 headset port (121 TR9-5)
● Software download via PPP
Comparison of optiPoint 600 office and optiset E memory
optiPoint 600 office optiset E memory

19 function keys, no integrated keypad, 12 function keys and integrated alphanumeric
external keypad possible over USB interface keypad
Full-duplex speakerphone mode Half-duplex speakerphone mode
Integrated USB 1.1 interface optiset E data adapter needed for data com-
munication with a PC
Headset port optiset E headset adapter needed for
headset connection
Table 10-10 Comparison of optiPoint 600 office and optiset E memory
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 600 office optiset E memory

Graphic LCD display with background light- LCD display without background lighting, no
ing, touchscreen touchscreen
Supports card reader/writer Supports card reader
Supports cordless adapter –
Wide scope of functions with few adapters Many adapters necessary for using functions
1 option bay 2 option bays
Table 10-10 Comparison of optiPoint 600 office and optiset E memory
Default key assignment for optiPoint 600 office

Redial Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Disconnect
Figure 10-33 optiPoint 600 office - Default Key Assignment
Connection and configuration

Connection of optiPoint 600 office over the UP0/E interface: Refer to Page 10-85 for more infor-
mation.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7 optiPoint 500
The optiPoint 500 telephones described in this section are compatible with the op-
> tiset E telephones. It is possible to operate both telephone families on one UP0/E
board. You can also use telephones from the two families in mixed host-client con-
figurations (earlier called the master-slave or primary-secondary configuration).
You can find information on optiset E telephones, adapters, and key modules in the
Hicom 150 H V1.0/Hicom 150 E Office Rel.2.0-3.0 Service Manual (see Section 1.6,
“Information on the Intranet”: Electronic Documentation on SEN ESY Products).
Introduction
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 optiPoint key module and optiPoint BLF add-on devices increase the number of function
keys available.
The different optiPoint 500 adapters allow flexible expansion of the telephone workstation. Ad-
ditional devices (such as personal computers, fax equipment, telephones, headsets) can be
connected quickly because it is easy to build them on to the bottom of the telephones (not
optiPoint 500 entry and optiPoint 500 economy) and because the adapters are plug "n" play".
You can find information not contained in this chapter in the optiPoint 500 Service Manual.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.1 optiPoint 500 Telephones
10.7.1.1 optiPoint 500 entry
Main features
● 8 function keys (can be modified with HiPath 3000/5000 Manager E) with LEDs (see Sec-
tion 10.7.1.10)
● Open listening
● 2 volume adjustment keys (plus/minus) and pitch
● No modularity (no connecting capability for adapters or key modules), no display
Standard key assignment (default) for optiPoint 500 entry
Consultation hold
Redial
Message
Callback
Speed dialing
Microphone on/off
Loudspeaker
Disconnect
Figure 10-34 optiPoint 500 entry - Standard Key Assignment (Default)

Refer to for connection requirements.Section 10.7.1.6
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.1.2 optiPoint 500 economy (not for U.S.)
Main features
● 12 function keys (4 can be changed using HiPath 3000/5000 Manager E, 8 freely program-
mable) with LEDs (see Section 10.7.1.10)
● Open listening
Standard key assignment (default) for optiPoint 500 economy
Redial Programmable
Programmable
Programmable
Programmable
Disconnect
Figure 10-35 optiPoint 500 economy (not for U.S.) Standard Key Layout
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.1.3 optiPoint 500 basic
Main features
● Open listening
– 1 USB 1.1 interface
– 1 option bay
Standard key assignment (default) for optiPoint 500 basic
Redial Programmable
Programmable
Programmable
Programmable
Disconnect
Figure 10-36 optiPoint 500 basic - Standard Key Assignment (Default)

A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.1.4 optiPoint 500 standard, optiPoint 500 standard SL (for U.S. only)
Note: optiPoint 500 standard and optiPoint 500 standard SL (for U.S. only) function exactly the
same on HiPath 3000 systems.
Main features
– 1 option bay
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
Standard key assignment (default) for optiPoint 500 standard
Redial Programmable
Programmable
Programmable
Programmable
Disconnect
Figure 10-37 optiPoint 500 standard - Standard Key Assignment (Default)

A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.1.5 optiPoint 500 advance
Main features
● 19 function keys (4 can be changed using HiPath 3000/5000 Manager E, 15 freely pro-
grammable) with LEDs (see Section 10.7.1.10)
● Alphanumeric LCD display (swivel) with 2 lines, 24 characters each. Background lighting
that stays lit for approximately 5 s.
– 2 option bays
– 1 headset port (121 TR9-5)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
Standard key assignment (default) for optiPoint 500 advance
Redial Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Programmable
Disconnect
Figure 10-38 optiPoint 500 advance - Standard Key Assignment (Default)

A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.1.6 Connection Requirements for HiPath 3000
Hardware requirements
System HiPath 3800 HiPath 3550 HiPath 3350

Hardware require- free UP0/E port on free UP0/E port on free UP0/E port on
ments SLMO2/8 CBCC CBCC
CBRC CBRC
SLU8 SLU8
SLU8R SLU8R
SLMO24
Connecting as a client telephone
The device can also be connected to an existing optiPoint 500 telephone (except for
> optiPoint 500 entry and optiPoint 500 economy) as a client telephone (using an op-
tiPoint phone adapter).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.1.7 Connection
Procedure: Connecting an optiPoint 500 Telephone
Step Activity
1. Locate a free interface on the main distribution frame or internal distributor for
connecting the telephone.
2. Connect the cable from the main distribution frame or internal distributor to the
wall outlet.
The maximum range for a standalone or host telephone without additional local
> power supply is approximately 1000 m (3280 feet) (for J-Y (ST) 2x2x0.6, ∅ 0.6 mm).
Perform the terminal test in Section 12.3.2.9 to determine whether a local power
supply is needed for additional power (for example, in host-client configurations or
for larger ranges).
3. Label the keys. You have the following options:

● by hand (in writing); label sheets come with each telephone.
● using a PC:
– with the “Key Labeling Tool” (requires MS Word©) which is contained on
the “Electronic Operating Instructions” CD.
– with the “Online Key Labeling Tool” which can be viewed at:
http://www.enterprise-communications.siemens.com/global/Products.aspx
(... -> Downloads).
4. Prepare the telephone for connection:
● Connect the handset cord to the telephone (marked with symbol) and to the
handset.
● Do you plan to connect an add-on device? Refer to Section 10.7.2 on
page 10-89 for more information.
● Do you plan to connect an optiPoint adapter? Refer to Section 10.7.3 on
page 10-93 for more information.
5. Connect the line cord (marked on the telephone by a symbol).
optiPoint 500 telephones are shipped with a 6 m (20 ft.) line cord and an MW6
(RJ11) plug for connection to a modular telephone jack.
The first time the telephone is switched on,
● all LEDs light up briefly
● all LEDs on the add-on devices (AODs), if connected, light up briefly (AOD LEDs do not
necessarily flash at the same time as the LEDs on the telephone)
● all pixels on the display activate briefly.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
These indications show that the telephone is starting up and performing a self-test. Download-
ing has finished and the telephone is ready for operation when you see the date and time on
the display.
USB interface
MW8 (RJ45) connection jack

for optiPoint key module, opti-
Point BLF
MW8 (RJ45) connection jack

for HiPath 3000
MW4 (RJ8) connection jacks:

Upper = headset equipment
Lower = handset
Option bays
(see Figure 10-43)
Figure 10-39 optiPoint 500 Connection Options
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.1.9 USB 1.1 Interface

With the exception of optiPoint 500 entry and optiPoint 500 economy, the optiPoint 500 tele-
phones have a USB 1.1 interface. This forms the basis for:
● PC-supported telephoning (TAPI)
● Data transmission over CAPI (for example, direct Internet access, fax capability, e-mail,
etc.). If the CAPI software is installed, PCs have direct Internet access over the USB inter-
face without any additional adapter. There is a charge for this software.
TAPI and CAPI can be used simultaneously (for example, to receive a large e-mail or download
data while calls are being set up over a CTI application).
optiClient Attendant V8 - the professional PC attendant console is connected over

> the USB 1.1 interface of the optiPoint 500 basic, optiPoint 500 standard or
optiPoint 500 advance.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.1.10 Key programming

Double assignment of the programmable function keys on the optiPoint 500 telephones and
the optiPoint key module is possible. Please note the following differences between the func-
tions:
● Up to and including V6.0 SMR-05:
Double assignment is possible if only phone numbers without LED support are saved on
the first level. It is also possible to program call numbers without LED support on the sec-
ond level. These can be internal station numbers, DID call numbers and call numbers from
a HiPath network.
● V6.0 SMR-06 and later:
One of the two following options can be configured using HiPath 3000/5000 Manager E
(Settings menu: System Parameters (Flags)):
– The "Enhanced key functionality" flag is not activated (default setting).
This will produce the same behavior as in versions up to and including V6.0 SMR-05.
– The "Enhanced key functionality" flag is activated.
Once you have defined a key of your choice as the "Shift key", only phone numbers
without LED support can be saved at the second key level which is now available. You
can program any key functions on the first key level. LED signaling is associated with
the first key level only.
When the Shift function is pressed, the LED associated with the Shift key lights up. This signals
that the phone numbers on the second key level are available.
The Shift function is deactivated when you press a phone number or if you press the Shift key
again.
The optiPoint BLF function keys cannot have double assignments.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.2 optiPoint 500 Add-On Devices

The optiPoint key module and optiPoint BLF add-on devices increase the number of function
keys available.
A color display and an integrated alphanumeric keypad in the optiPoint application module in-
creases user-friendliness when making telephone calls.
The user usually installs the add-on devices. The installation instructions are on the “Electronic
Operating Instructions” CD.
Caution
7 Always disconnect the line cord before connecting add-on devices to the telephone.
Refer to the optiPoint BLF Feature Description for model-specific data for the optiPoint key
module and the HiPath 3000/5000.
The following sections contain information on the possible key module configurations:
● Section 10.7.2.4 for terminals in the optiPoint 500 family
● Section 10.3.5.3 for terminals in the optiPoint 410 and optiPoint 420 family
10.7.2.1 optiPoint key module

The optiPoint key module is an add-on device that should be mounted on the side of the tele-
phone; it provides an additional 16 keys, LEDs and labelling areas for all purposes.
Figure 10-40 optiPoint key module

Information on double assignment can be found in Section 10.7.1.10.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.2.2 optiPoint BLF

This is an add-on device that provides 90 additional keys, LEDs and labeling areas for all pur-
poses.
The device is connected to the telephone or to an optiPoint key module over an interface cable
with the following connectors: RJ11 input (MW6), RJ45 output (MW8).
Power is supplied by a local PSU (see Section 10.10.1.1) that can power up to two optiPoint
BLFs. The power supply unit must be plugged directly into the designated optiPoint BLF port.
Figure 10-41 optiPoint BLF
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.2.3 optiPoint application module (V5.0 SMR-06 and later)

The optiPoint application module is a key module that can be mounted on the side of the tele-
phone; it has a color display and an integrated alphanumeric keypad. It provides a personal
phonebook and other helpful applications for improving user-friendliness when making calls.
Figure 10-42 optiPoint application module

The optiPoint application module can be implemented on the following telephones:
● optiPoint 500 basic, optiPoint 500 standard, optiPoint 500 standard SL (for U.S. only), op-
tiPoint 500 advance
Only the personal phonebook is supported when operating the key module in the TDM en-
vironment.
● optiPoint 410 standard, optiPoint 410 advance, optiPoint 420 standard, optiPoint 420 ad-
vance
In a VoIP environment, the add-on device supports all the functions offered by the current
optiPoint 410 display module (personal phonebook, LDAP, WAP browser, Java application,
voice dialing) but with improved ergonomics.
The optiPoint application module must always be installed as the first key module, in other
words, connected directly to the telephone. Additional add-on devices may be used.
The following sections contain information on the possible key module configurations:
● Section 10.7.2.4 for terminals in the optiPoint 500 family
● Section 10.3.5.3 for terminals in the optiPoint 410 and optiPoint 420 family
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
An external power supply unit is always required to operate the optiPoint application module.
The power supply units for optiPoint 410 and optiPoint 420 described in Section 10.10.1.2 are
used. If you already have this type of power supply unit, the second output can be used to pow-
er the optiPoint application module.

The following table shows the possible configurations for key modules on telephones from the
optiPoint 500 family (not optiPoint 500 entry and optiPoint 500 economy).
Table 10-11 Key module configurations on an optiPoint 500 telephone
optiPoint 500 telephone 1. Key module 2. Key module

optiPoint key module –
optiPoint 500 basic optiPoint key module optiPoint key module

optiPoint key module optiPoint BLF
optiPoint 500 standard, optiPoint application module –
optiPoint 500 standard SL (for
U.S. only) optiPoint application module optiPoint key module
optiPoint application module optiPoint BLF
optiPoint 500 advance optiPoint BLF –
optiPoint BLF optiPoint BLF1
1 Configuration with two optiPoint BLFs only with HiPath 3800
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.3 optiPoint 500 Adapters

The different optiPoint 500 adapters (not optiPoint 500 entry and optiPoint 500 economy) allow
flexible expansion of the telephone workstation by providing additional device connections
(such as personal computers, fax equipment, telephones, headsets).
The adapters, which are connected on the bottom of the telephone, are plug "n" play". When a
new telephone adapter configuration is plugged in, it generates a reset; a setup message no-
tifies the system of the new configuration.
The user usually installs the adapter. The installation instructions are on the “Electronic Oper-
ating Instructions” CD.
Caution
7 Always disconnect the line cord before connecting adapters to the telephone or re-
moving them from the telephone.
Option bays
Option bays:
● 2 x for optiPoint 500
advance (shown
here)
● 1 x for optiPoint 500
basic and optiPoint
500 standard
Figure 10-43 optiPoint 500 Option Bays
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.3.1 optiPoint analog adapter

The optiPoint analog adapter allows an analog device (such as, telephone (DTMF only),
group 3 fax, modem, cordless telephone) to be connected to an optiPoint 500 telephone.
The analog device connected can send and receive calls on the interface to the system regard-
less of the optiPoint telephone’s connection status, as long as a B channel is available.
The adapter must always have a local power supply for operating the connected analog device.
MW6 (RJ11) socket assignments:

Pin Signal
1 Free
2 Free
6 1
3 T (Tip)
4 R (Ring)
5 Free
6 Free
Figure 10-44 optiPoint analog adapter
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 T/R interface, message waiting lamp, dictating
equipment, speaker, announcement device (such as start/stop).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.3.2 optiPoint ISDN adapter

The optiPoint ISDN adapter provides the basic ISDN access for S0 devices (max. 2), such as,
an S0 PC card, group 4 fax equipment or video communication devices (such as, videoset or
videokit).
S0 telephones must have their own power supply for connection.

Pin Signal
1 Free
2 Free
3 SR1 8 1
4 SX1
5 SX2
6 SR2
7 Free
8 Free
Figure 10-45 optiPoint ISDN adapter
S0 interface properties
● Supports point-to-point and passive bus connections
● Wired for short passive bus configurations
● 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.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.3.3 optiPoint phone adapter

The optiPoint phone adapter is used for connecting a second optiPoint 500 telephone (client
telephone) with its own power supply.
The system treats the client telephone as an independent telephone with a separate phone
number and its own B channel. The client telephone can send and receive calls regardless of
the connection status of the host telephone.
The maximum range between the host and client telephones is approximately 100 m (328 feet)
(for J-Y (ST) 2x2x0.6, ∅ 0.6 mm).

Pin Signal
1 Free
2 AUX – (a)
6 1
3 UP0/E –
4 UP0/E +
5 AUX + (b)
6 Free
Figure 10-46 optiPoint phone adapter
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
Example of a Host-Client Configuration
UP0/E to the system,

2-wire, up to 1000 m (3280 feet) UP0/E, 4-wire, up to 100 m (328 feet)
2 4
MW wall outlets MW wall outlet
Local power sup- Local power sup-

ply (optional) ply (optional)
Host Client
optiPoint 500 telephone with optiPoint optiPoint 500 telephone

phone adapter
Figure 10-47 Example of a Host-Client Configuration
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.3.4 optiPoint acoustic adapter

The optiPoint acoustic adapter is used for connecting
● a headset (121 TR 9-5) (see Section 10.10.2)
● 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) via floating contacts (not supported when using the adapter on optiPoint 410 and
optiPoint 420).
Assignment of the three connection jacks:
1 Connecting a headset with the following electrical

values (121 TR 9-5):
● Microphone (electret interface):
– max. power: 400 µA,
– supply voltage: 5 V ± 10%
– series resistor: 5 kΩ ± 10%
● Acoustic transformer:
– Impedance: 150 Ω ± 10%
1 2 3 – EBD: 13 dB ± 2.5 dB
2 Connecting a loudspeaker and microphone using Y
cable (see Figure 10-49)
3 Floating contacts (see Table 10-12), load capacity of
max. 5 W at 24 Vac or 60 Vdc
Figure 10-48 optiPoint acoustic adapter
Notes on the optiPoint acoustic adapter

● Section 10.7.4 contains details on a possible additional external power supply.
● The internal components of the optiPoint terminal are deactivated in speakerphone mode
if 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 external
speakerphone 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.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
● Ring, alarm and key tones are transferred to the internal loudspeaker and not to an exter-
nal loudspeaker 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.
Assignment of the MW4 connection sockets:
Pin Signal
1 sense lead
2 NF+
Y cable
3 Free
4 GND
Loudspeaker
Internal resistance: 0 Ω; 10 µF
Level (for PCM -20 dBm): -4.8 dBm (at volume level 8; 0.775
acoustic adapter V = 0 dBm)
Sense lead to GND: int. loudspeaker deactivated; only active
for tone ringing.
4 1
Pin Signal
1 +5V
microphone 2 GND
3 Free
4 sense lead
Input level -50 dBm: -12 dBm PCM signal
Input resistance: 150 kΩ parallel to 220 nF in series with 36
kΩ
Sense lead to GND: internal microphone deactivated.
Figure 10-49 Y Cable for optiPoint acoustic adapter
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
Table 10-12 Floating contacts on the optiPoint acoustic adapter
Pin Assign- Notes

ment
1 Free –
2 "Busy" con- Signals active telephone states:
3 tact ● handset lifted
● Loudspeaker activated or headset active
These states can be displayed, for example, on external signaling equip-
ment (LED, relay, etc.) The signaling equipment must have its own power
supply.
The contact can be loaded with up to 5 W at 24 Vac or 60 Vdc.
4 "Call" con- Signals the call receipt state.
5 tact This can be used, for example, to control a secondary bell.
The contact can be loaded with up to 5 W at 24 Vac or 60 Vdc.
6 Free –
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.3.5 optiPoint recorder adapter

The optiPoint recorder adapter allows an external recorder or a second headset to be connect-
ed.
Warning: The called party must be informed that the call is being recorded.
Assignment of both connection jacks:
1 MW6 port for recorder
Pin Signal
1 Free
2 NF
3 NF 6 1
4 NF
5 NF
1 2
6 Free
Contacts 2+3 and 4+5 are bridged
internally.
Recorders to be connected must meet the following electrical re-

quirements:
Input impedance: >10 kΩ
Frequency progression: 300 to 3000 Hz ± 3 dB
Beep tone level: -26 dBm to -18 dBm at a 600 Ω load
Max. input level: 650 mVeff from a 600 Ω source
2 MW4 port for second headset
Pin Signal
1 Tx–
2 Rx
3 Rx 4 1
4 Tx+
Figure 10-50 optiPoint recorder adapter
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.3.6 Possible optiPoint Adapter Configurations
Adapter categories
Each UP0/E port in the system provides two B channels. This means that you can connect two
telephones, each with a separate phone number, to one UP0/E port.
Category 1 optiPoint 500 adapters
The following adapters each require a B channel and, therefore, can only be used once on a
host terminal (host terminal requires the second B channel of the
UP0/E port).
● 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 be
operated in the second slot.
Category 2 optiPoint 500 adapters
The 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
Configuration restrictions
The voltage feed test can be used to check whether a local power supply is also nec-
> essary for an adapter configuration. To avoid any doubts, the test should always be
implemented when installing large configurations.
Number of usable adapters and key modules

HiPath 3000/5000 shows the maximum number of adapters and key modules that can be con-
nected to Section 10.7.5. The limits also include the client telephones connected over optiPoint
phone adapters and the analog telephones connected over optiPoint analog adapters.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.3.7 Comparison of optiset E adapters and optiPoint 500 adapters
Table 10-13 Comparison of optiset E and optiPoint 500 adapters
optiset E optiPoint 500

analog adapter analog adapter
phone adapter phone adapter
data adapter integrated USB interface
control adapter
ISDN adapter ISDN adapter
acoustic adapter acoustic adapter
contact adapter
headset adapter
headset plus adapter recorder adapter
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
10.7.4 optiPoint 500 key modules and adapters power supply

Power is generally supplied to optiPoint 500 telephones by the system via the UP0/E interfaces.
When certain optiPoint 500 key modules and adapters are used, the power supply from the
system is not adequate.
Table 10-14 indicates which optiPoint 500 key modules require an additional external power
supply. In this case, the local power supply units described in Section 10.10.1.1 are used.
Table 10-14 Additional External Power Supply for optiPoint 500 Key Modules and Adapters
optiPoint 500 key modules Is an additional external power Plug-in power supply
optiPoint 500 Adapters supply required? unit connection
optiPoint key module generally not required1 series-connected2
optiPoint BLF required connected directly3
optiPoint analog adapter required series-connected2
optiPoint ISDN adapter generally not required1 series-connected2
optiPoint phone adapter generally not required1 series-connected2
optiPoint acoustic adapter required4 series-connected2
optiPoint recorder adapter generally not required1 series-connected2
1 It is assumed that only one key module or adapter is implemented on each optiPoint 500 telephone. An additional external
power supply may be required if several key modules and adapters are implemented on an optiPoint 500 telephone or the
maximum UP0/E interface range is reached by the optiPoint 500 telephone. The telephone test described in Section
12.3.2.9 will establish whether or not additional power is required from a local power supply.
2 The local power supply is series-connected to the optiPoint 500 telephone: the "digital" RJ6 jack on the local power supply
must be connected to the optiPoint 500 telephone. The other RJ6 jack must be connected to the UP0/E interface on the
system.
3 The local power supply is connected directly to the optiPoint BLF: one of the two RJ6 jacks on the local power supply unit
must be connected with the center jack (indicated by the symbol of a power supply unit) on the optiPoint BLF. A local power
supply can supply a maximum of two optiPoint BLFs.
4 An additional external power supply is required if the floating contacts on the optiPoint acoustic adapters are being used.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint 500
10.7.5 Maximum Configuration for UP0/E Workpoint Clients,

Add-On Devices and Adapters
Table 10-15 System-Specific Maximum Configuration for UP0/E Workpoint Clients, Add-On
Devices and Adapters
Workpoint Clients, SYSTEM
Add-On Devices, Adapters HiPath HiPath 3 HiPath HiPath HiPath
38001 550 3500 3350 3300
optiPoint 500 telephones
● Number per system 384 722 483 244 245
● Number per box (the value in 192 – – – –
brackets applies to operation us-
ing a PSUI)
optiPoint acoustic adapters
Number per system No restriction
optiPoint analog adapters
Number per system 116 246 246 87 87
optiPoint recorder adapters
optiPoint ISDN adapters
optiPoint phone adapters
optiPoint key modules
optiPoint BLF:
Number per system 12 6 6 – –
optiPoint application module:
optiset E telephones
● Number per system 384 723 484 245 246
● Number per box (the value in 192 – – – –
brackets applies to operation us-
ing a PSUI)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiPoint 500
Devices and Adapters
Workpoint Clients, SYSTEM
Add-On Devices, Adapters HiPath HiPath 3 HiPath HiPath HiPath
38001 550 3500 3350 3300
optiset E analog adapters
optiset E control adapters
optiset E data adapters
optiset E speech adapters
optiset E privacy modules
optiset E ISDN adapters
optiset E phone adapters
optiset E key modules
optiset E BLFs
Number per system 12 6 6 – –
1 Testing is not required on stations and lines up to the maximum configuration. Configurations that contain UCD/ACD or
more than one SLCN or groups with more than ten stations should always be checked using the project planning tool (in-
tranet: http://intranet.mch4.siemens.de/syseng/perfeng/tools/hpt/index.htm).
2 8xUP0/E at the central board + 5xSLU8 + 1xSLMO24.
4 8xUP0/E at the central board + 2xSLU8.
6 If the total number of UP0/E stations, analog stations and additional stations connected using an adapter is greater than 72,
an external EPSU2 power supply unit must be used.
7 If the total number of UP0/E stations and additional stations connected using an adapter is greater than 24, a UPSC-D/
UPSC-DR must be used.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiLog 4me
10.8 optiLog 4me

optiLog 4me is a digital, single-channel speech recording device designed for operation with
the HiPath 3000/5000. It can record up to 2900 hours of telephone calls.
Figure 10-51 optiLog 4me

You can set the optiLog 4me to the following modes in both digital and analog telephones:
● Start Recorder
Recording begins when you press the Start key.
● Trader Recorder
Records and stores all calls.
● Malicious Call Recorder
Stores calls in their entirety when you press any button during the call.
● Third Party Monitoring (not currently available with HiPath 3000/5000)
optiLog 4me should be installed at the central station of the system. Recording starts when
you press the Monitor key on the telephone.
Furthermore, you can use the recorder to record conference calls using an external micro-
phone.
The optiLog 4me can be connected between the optiPoint 500 telephone and the handset. The
privacy module is supplied complete with a local power supply.
For additional information on this, please refer to the installation and administration instructions
included with the adapter.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

optiset E privacy module
10.9 optiset E privacy module

The optiset E privacy module protects telephone calls from unauthorized monitoring. Both part-
ners need a device like this. The privacy module is connected between the telephone and
handset; you simply need to plug in the handset cord. The privacy module is supplied complete
with a local power supply.
The optiset E privacy module may be subject to import and export regulations.
>
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiPoint Accessories
10.10 optiPoint Accessories

The following data is valid for the telephone families optiset E, optiPoint 410, optiPoint 410 S,
optiPoint 420, optiPoint 420 S, optiPoint 500, and for the optiPoint 600 office telephone. Re-
strictions are indicated in the relevant places.
10.10.1 External AC Adapters

You may need an external AC adapter if you are using large configurations or if you need to
extend the range.
10.10.1.1 Local Power Supply for optiset E, optiPoint 500, optiPoint 600 office
You can connect a local power supply to the line cords of a host or client telephone using two
RJ11 jacks and the connection cable supplied (see Figure 10-52).
Variants
● Local power supply, Euro: AUL:06D1284 (C39280-Z4-C71 = number entered on unit)
● Local power supply, UK: AUL:06D1287 (C39280-Z4-C72 = number entered on unit)
● Local power supply, 110 V USA: AUL:51A4827 (C39280-Z4-C73 = number entered on
unit)
Technical data for local power supply AUL:06D1284 (Euro)

● Line voltage: 220 (230) VAC
● AC line frequency: 47 ... 53 Hz
● Output voltage: max. 50 VDC, min. 30 VDC
● Output current: Max. 250 mA
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Table 10-16 Pin Assignment for Local Power Supply AUL:06D1284 (Euro)
Pin Assignment
1 Not used
2 –
3 a-wire (tip)
4 b-wire (ring)
5 +
6 Not used
Example: External AC Adapter Connection
AC adapter
"MW"
(RJ) jack Analog
jack tele-
"Digital" phone or
device
HiPath 3xx0
From optiPoint 500 adapter
(for example, here the
optiPoint analog adapter)
optiPoint 500
Telephone
Figure 10-52 Example: External AC Adapter Connection
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.10.1.2 Power supply unit for optiPoint 410/410 S and 420/420 S

The AC adapter features two MW6 connectors. Power is supplied to a telephone via the left
board marked "Digital".
Variants
● AC adapter, Euro: C39280-Z4-C510
● AC adapter, UK: C39280-Z4-C512
● AC adapter, 110 V USA: C39280-Z4-C511
Technical specifications AC adapter, Euro: AC adapter, UK: AC adapter, 110 V

C39280-Z4-C510 C39280-Z4-C512 USA:
C39280-Z4-C511
Line voltage 230 Vac 230 Vac 120 VAC
Line frequency 50 Hz 50 Hz 60 Hz
Output voltage max. 43 Vdc, max. 43 Vdc, max. 43 Vdc,
min. 30 VDC min. 30 VDC min. 30 VDC
Output current 480 mA 480 mA 480 mA
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.10.2 Headsets
A headset replaces the telephone handset, which means that the user’s hands are free when
telephoning. Cordless headsets (121 TR 9-5) may also be used.
Note: A headset key can be configured for optiPoint or optiset E telephones. This allows the
user to take calls and to switch between the handset and the headset.
Figure 10-53 Example: Corded and Cordless Headsets
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Connection options
optiPoint and optiset E telephones not included in the table below do not support headset con-
nection.
Table 10-17 Connection Options for Corded and Cordless Headsets
Telephone Connection Options for Corded and Cordless Headsets

Direct Using an Using an Using an
optiPoint optiset E optiset E
1
acoustic adapter headset adapter control adapter
headset plus
adapter
optiPoint 500 basic X
optiPoint 500 standard, X
SL (for U.S. only)
optiPoint 500 advance X X
optiPoint 600 office X X
optiPoint 410 economy X
plus,
plus S
optiPoint 410 standard, X X
S
optiPoint 410 advance, X X
S
optiPoint 420 economy X
plus,
plus S
optiPoint 420 standard, X X
S
optiPoint 420 advance, X X
S
optiset E basic X
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Table 10-17 Connection Options for Corded and Cordless Headsets
Telephone Connection Options for Corded and Cordless Headsets

Direct Using an Using an Using an
optiPoint optiset E optiset E
1
acoustic adapter headset adapter control adapter
headset plus
adapter
optiset E advance plus/ X X
comfort
optiset E advance con- X X
ference/conference
optiset E memory X X
1 Accepting and ending calls using the headset keys is only supported if the connection is established using an optiPoint
acoustic adapter.
Information on connecting the headset is provided in the relevant installation instructions.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
optiClient 130 V5.0
10.11 optiClient 130 V5.0
Definition
The optiClient 130 is a PC-based multimedia application that offers connection services for dif-
ferent communication media over a LAN (network). Voice, video, or chat connections can be
managed and controlled using the optiClient 130. For voice connections, this means that the
optiClient 130 can be used on a PC like a telephone.
Modular structure
The optiClient 130 has a modular structure for the functional elements which can be extended
or replaced to change the scope of functions available.
● The basic module of the optiClient 130 is the main bar. The main bar does not provide any
communication functions itself, but instead serves as a central component that works to-
gether with the various modules to define the communication functions and display of the
optiClient 130.
● Interface modules are the modules that allow the available functions to be operated in win-
dows and dialogs. Interface modules include, for example: telephone windows, directories,
call list management, etc.
● Provider modules determine which communication systems or communication service pro-
viders the optiClient 130 can be connected to.
● Manager modules run in the background and are not visible. They assume general com-
munication control functions. Examples of manager modules include the Keyboard Man-
ager and ScreenSaver Manager.
PC Prerequisites
● Operating system Windows®2000 (SP 4 or later) or Windows®XP (SP 1 or later)
● Processor: 1 GHz or higher recommended
● RAM memory: At least 512 MB
Installation and Configuration

Information on installation can be found in the readme file on the optiClient 130 product soft-
ware CD.
Use HiPath 3000/5000 to configure a workpoint client for HiPath 3000/5000 Manager E.
optiClient 130 software can be upgraded automatically. This can be started on a user-specific
basis during login, cyclically or can be skipped.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

HiPath AP 1120
10.12 HiPath AP 1120

The terminal adapter HiPath AP 1120 connects up to two analog telephones and/or fax ma-
chines with a corporate network or a network provided by a carrier. HiPath 3000/5000 supports
the HiPath AP 1120 variants H.323 and SIP.
The device is capable of dynamically recognizing the most common IP telephony codecs and
fax protocols, including T.38.
Figure 10-54 HiPath AP 1120
Connections
● Ethernet connections:
– 1 x RJ45: 10/100 BaseT Ethernet access
– 1 x RJ45: 10/100 BaseT Ethernet access, power supply over MDI, IEEE 802.3af (Pow-
er over LAN)
● Analog connections:
– 2 x RJ11: analog telephone, fax
● Power supply:
– External 24 Vdc/12 W local power supply
No local power supply is required if power is provided via Ethernet access (Power over
LAN).

Information on connecting and configuring the HiPath AP 1120 terminal adapter can be found
in the Installation Manual (Configuration Tools and Documentation) and the Administration
Manual, see:
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.13 optiPoint WL2 professional

HiPath 3000/5000 makes wireless LAN services available via a connected WLAN access point.
optiPoint WL2 professional enables the use of the HiPath 3000/5000 features (except Relo-
cate) that are offered on the display, in the service menu and on function keys.
Note: Because of the product-specific release of the WLAN access points, take the current in-
formation in the relevant release documentation into account.
Main features of WLAN workpoints

● Interfaces: WLAN, USB
● Standards: WLAN, 802.11b (11 megabits/s), 802.11g (full support for 54 megabits/s), Cor-
Net-IP
● Voice compression G.711, G.722 (optional), G.723, G.729 A/B (G.729 A with Voice Activity
Detection VAD)
● QoS in accordance with ToS, DiffServ, 802.1q, 802.11e (WME subset)
● Color graphical swivel display with six lines, and a resolution of 128 x128 pixels
● Intuitive user prompting
● Speakerphone

Information on connection and on configuring WLAN access points and WLAN workpoints is
provided in the corresponding product documentation.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Attendant console versions
10.14 Attendant console versions
10.14.1 OpenStage Attendant

Switching services can be executed in HiPath 3000/5000 by a specially configured OpenStage
telephone. This OpenStage Attendant is also an intercept position. It is the destination for all
incoming non-DID calls and calls which the call-allocation algorithms are unable to route to us-
ers (intercept calls). The attendant routes these calls to the correct destination.
Configuration as an OpenStage Attendant is possible for the following telephones: OpenStage
40/60/80.
10.14.2 optiPoint Attendant

A specially equipped optiPoint telephone can perform switching services for HiPath 3000/5000.
This optiPoint Attendant simultaneously serves as the intercept position. It is the destination for
all incoming non-DID calls and calls which the call-allocation algorithms are unable to route to
users (intercept calls). The attendant routes these calls to the correct destination.
Configuration as optiPoint Attendant is possible for the following terminals: optiPoint 500 econ-
omy/basic/standard/advance, optiPoint 410 economy/economy plus/standard/advance, opti-
Point 420 economy/economy plus/standard/advance, and optiPoint 600 office.
Standard key assignment (default) for optiPoint Attendant
Service Night service

Redial Internal phonebook
Microphone on/off Queued calls
Loudspeaker Override
Hold
External 1
External 2
Disconnect
Figure 10-55 optiPoint 500 standard: Standard Key Layout optiPoint Attendant
For more information, please refer to the optiPoint Attendant operating instructions (see
Section 1.6, “Information on the Intranet”: Electronic Documentation on SEN ESY Products).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.14.3 optiClient Attendant V8
Definition
optiClient Attendant is a PC-based attendant console and can be connected to HiPath 2000/
3000/5000 systems. Depending on the model, up to six optiClient Attendants can be imple-
mented at each node.
optiClient Attendant can also be implemented as a central attendant console in a network con-
sisting of HiPath 2000/3000/5000 systems.
Version V8 replaces the existing optiClient Attendant V7.0 in all connection variants
> (USB, V24, and LAN).
The sale of existing and new optiClient Attendant V7.0 systems will be discontinued.
Order items are:
1. optiClient Attendant V8, full version
2. optiClient Attendant, upgrade from V7.0 to V8
optiClient Attendant V8 only operates at HiPath 3000/HiPath 5000 V7 and HiPath

> 2000 V2 and is not downwards-compatible.
optiClient Attendant V7.0 is not compatible with HiPath 3000/HiPath 5000 V7 and
HiPath 2000 V2 (no upgrade possible).
Technical changes in comparison to version 7.0:

● optiClient Attendant V8 always needs a telephone for operation (even in the IP connection
version). This telephone should be separately marketed (connection via Soft-OLA no long-
er applicable).
● Headsets are consequently no longer connected to the PC but to the telephone.
● Telephone connectivity is always guaranteed even if the optiClient Attendant PC fails or is
switched off.
Connection variants
1. Connection via TCP/IP to optiPoint 410/420
2. Connection via USB port of the optiPoint 500 and optiPoint 600 office TDM telephones
3. Connection to the control adapter on Optiset E.
For information on OpenStage telephones, refer to the Sales Information.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

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 the
phonebook 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 date
and time
● Additional functions, such as, hold keys, override, callback, conference, paging, speaker
announcements, alarm signaling, view call charges, redial (10 last-dialed destinations)
● No calls are lost because options are provided for intercepting unanswered DID calls and
DID calls to busy stations
● Windows online help
● Convenient configuration of individual features
● Service tools for diagnosis and protocols
● Simple installation routine
● User interface currently available in German, English, Dutch, Portuguese, Italian, French,
and Spanish.
● Connection of a blind attendant console, optional.
● optiClient Attendant may operate as the central attendant console in HiPath networks.
● Import of CSV files into the integrated internal phonebook
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
● Busy lamp fields offer the following features:

– Up to 300 fields per busy lamp field
– Up to two busy lamp fields possible
– Configuration of busy lamp fields to suit individual user requirements
– BLF zoom 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 on or 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
Compatibility of optiClient attendant with HiPath 2000, HiPath 3000, HiPath 5000
HiPath 3000/5000 HiPath 3000/5000 HiPath 3000/5000

V7 V6.0 V5.0
HiPath 2000 V2 HiPath 2000 V1.0
optiClient Attendant V8 Yes No, not ready for No, not ready for
startup startup
optiClient Attendant V7.0 No, not ready for Yes Yes
startup
PC system requirements:
● Pentium IV
● 256 MB RAM space
● Operating systems WIN2000, XP, 2003 Server (Windows Vista Business, see notes in the
Sales Information)
● Microsoft-compatible mouse
● CD-ROM or DVD drive
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

● For operation with a TCP/IP connection:

– Functional operating system with network and sound card configured
– optiPoint 410/420 telephone (OpenStage telephones: see notes in the Sales Informa-
tion)
● For operation via USB:
– optiPoint 500 and optiPoint 600 office TDM terminals with USB port (OpenStage ter-
minals: see notes in the sales information),
USB cable (part number: S30267-Z360-A30-1),
USB driver (included in the CallBridge TU software),
and a free USB port at the PC.
● For operation via optiset E control/data adapters:
Optiset E telephone with adapter slot and a free RS 232 interface on the PC
(COM port 1 – 4).
If the licensing components CLA and CLM are to be installed on the same PC, their system
requirements are also to be taken into account.
Overview of Microsoft operating systems supported for each connection variant
Connection variant Windows 2000 Windows XP Windows Vista

Business
control adapter X X X
USB interface X X 1
TCP/IP X X 1
1 see notes in the Sales Information
Licensing
A license is required for optiClient Attendant V8. The product is licensed centrally via HiPath
License Management.
The first time optiClient Attendant V8 is started on HiPath 3000/5000 V7 or HiPath 2000 V2,
the optiClient Attendant can be operated for a maximum of 30 days as part of the system’s
grace period.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
Model-specific data
Topic HiPath 3000/5000 HiPath 2000

Feature available in x x
Hardware requirements
Software requirements from V7 or later from V2 or later
Maximum number of connectable optiClient At- 6 1
tendant
optiClient Attendant as central attendant console

optiClient Attendant can be used as a central attendant console in an IP network (max. 6 opti-
Client Attendant per network). To enable network-wide BLF functionality, all attendant consoles
must be connected to one of the network’s HiPath 3000 nodes and registered. This functionality
is independent of the optiClient Attendant connection type (V.24, USB or TCP/IP). For the net-
work-wide Busy Lamp Field function all decentralized systems send their station states (e.g.
free or busy) to the central system, to which the optiClient Attendants are connected. Signaling
takes place in the CorNet-IP protocol (CorNet-NQ protocol tunneled in H.323 via annex M1).
In an IP network, up to 100 stations per node can be defined that send their status information
to the central attendant console for display on the busy lamp field. The stations of the central
system in the network (to which the optiClient Attendants are connected) can all be displayed
on the busy lamp field of the central attendant console.
Note: The network-wide busy signal is controlled via the optiClient Attendant independently of
the network-wide busy signal to the workpoints clients via the HiPath 5000 RSM Presence
Manager.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Mobile Telephones for HiPath Cordless Office
10.15 Mobile Telephones for HiPath Cordless Office

The following are examples of the mobile telephones approved for HiPath Cordless Office. For
further information, refer to the appropriate operating instructions and the HiPath Cordless Of-
fice service manual.
10.15.1 Gigaset SL1 professional

Gigaset SL1 professional is a very handy and light (only 100 g) mobile telephone based on the
digital DECT/GAP standard.
● Ranges:
– Outdoors: up to 300 m
– Indoors: up to 50 m
● Operating times:
– Standby: up to 250 hours
– Talk time: up to 15 hours
● Dimensions (L × W × D in mm): 114 × 47 × 22
● Weight (including battery cells): approx. 100 g
● Operating temperature (mobile telephone): +5 °C to +45 °C (41 °F to 113 °F)
10.15.2 Gigaset SL2 professional

Gigaset SL2 professional is a mobile telephone based on the digital DECT/GAP standard.
● Ranges:
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

● Operating temperature (mobile telephone): +5 °C to +45 °C (41 °F to 113 °F)
10.15.3 Gigaset M1 professional

Gigaset M1 professional is a very robust mobile telephone based on the digital DECT/GAP
standard. It is suitable for use in environments requiring telephones to be break- and shock-
proof and dust- and spray-resistant.
Main features
● Housing:
– Spray-resistant (IEC 529 IP64)
– Dustproof
– Break- and shockproof
– Silicon-free interface
– Sturdy carry clip
● Interference resistance conforming to EN 50 082-2 (industry standard)
● Acoustics optimized for industrial environments
● Ranges:
● Operating temperature (mobile telephone): –10 °C to +55 °C (14 °F to 131 °F)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.15.4 Gigaset M2 professional

Gigaset M2 professional is a very robust mobile telephone based on the digital DECT/GAP
standard. It is suitable for use in environments requiring telephones to be break- and shock-
proof and dust- and spray-resistant.
Main features
● IP rating IP 65 (casing protection)
– Protected against splashes and low-pressure jets of water
– dustproof
● shock-proof and robust
● Silicon-free interface
● Sturdy carry clip
● Immunity from electromagnetic radiation in accordance with EN 50 082-2
● Acoustics optimized for industrial environments with five volume settings
● Memory card for device-specific and individual entries
● Emergency key (individual programmable key)
● Headset port (Bluetooth, Mini-Lumberg connector)
● Illuminated graphics display (128 x 160 pixels, 64k colors)
● Ranges:
● Operating temperature (mobile telephone): –10 °C to +55 °C (14 °F to 131 °F)
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.15.5 Logging Mobile Telephones On To the System
Introduction
Sixteen mobile telephones are released for use by entering the HiPath cordless system number
(DECT identification, eight hexadecimal places) and inserting the SLC16N in HiPath 3550, af-
ter which they can be logged on (mobile telephone codes, or PINs, are assigned. Other mobile
telephones must be released before they can be used.
For initial installation of the HiPath Cordless Office, the HiPath cordless system num-
> ber must be ordered together with the SLC16N board. Replacement boards are al-
ways delivered without a HiPath cordless system number.
Before logging on a mobile phone, you must open the login window from a system telephone
(Manager T) by entering the code and password. A maximum of 10 login windows can be open
at a time.
Then type the station numbers of the mobile telephones you want to log on.
10.15.5.1 Opening the HiPath 3000 Login Window
Input Activity Display

*94 2 19970707 Open the login window Number:
124 Type the station number of the handset you Number:
want to log on (such as, 124)
125 Type the station number of the second handset Number:
you want to log on (such as, 125)
: : :
: : :
The login window remains open for ten minutes per station. The handset must log on during
this period (refer to Page 10-128).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

10.15.5.2 Logging On the Mobile Telephone

Example: log the mobile telephone (station number “125”) on to the DECT telephone system 2
using mobile telephone PIN “11112345”.
Step Entry or Key Handset Display

1. Switch on the mobile telephone by holding The first time you log on, the mes-
down the hook key for at least 1 second. sage “Register?” appears on the
You hear a confirmation tone. handset display. The second time
you log on, "Base 1" or a similar
message flashes.
2. Make the following entries within one minute.
Press the menu key.
3. Select a station1 (for example: Base 2) and
confirm.
Base 2
4. Open the add-on menu.

5. Select “Register” and confirm your choice. The following prompt appears:
“Please enter PIN:”
6. Enter the eight-digit PIN (mobile telephone “11112345”
code) “11112345” and confirm.
7. Once you have logged on properly, "Base 2"
or a similar message appears and the bell
symbol " " flashes. Base 2
1 Base = DECT telephone system
After logging on and releasing a handset, always turn on the out-of-range warning signal. For
more information, refer to the operating instructions (see Section 1.6, “Information on the Intra-
net”: Electronic Documentation on SEN ESY Products).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
10.15.5.3 Checking the Login Status of the Mobile Telephones

The current login status of mobile telephones can be checked using HiPath 3000/5000 Manag-
er E in the system view (“Cordless ...” dialog in the “Settings” menu) and the station view.
10.15.5.4 Replacing, Locking, and Logging Off a Mobile Telephone

If you need to replace a handset for servicing, you must change the mobile telephone code
(PIN) of the old handset before logging on the replacement telephone.
When you replace a mobile telephone, the station must be assigned a new mobile
> telephone code (PIN) in the HiPath 3000 system. This automatically logs off the mo-
bile telephone.
This also prevents a person who knows the old PIN to log on an invalid mobile tele-
phone.
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

Analog Telephones for HiPath 3000
10.16 Analog Telephones for HiPath 3000

You can connect dial pulsing (DP) and DTMF telephones (such as group 3 fax machines and
modems, answering machines, or entrance telephones) to the analog ports in the HiPath 3000.
Boards for connecting analog telephones

Hardware require- Free analog port on Free analog port on Free analog port on
ments SLMA/8 CBCC CBCC
CBRC CBRC
4/8/16SLA 4/8SLA
8SLAR 8SLAR
SLA8N/16N/24N
SLAD4/8
SLAD4/8 SLAD8R
SLAD8R
Connecting equipment using an optiPoint analog adapter
It is also possible to connect an analog telephone to an existing optiPoint 500 tele-

> phone with the optiPoint analog adapter (except for optiPoint 500 entry and
optiPoint 500 economy).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm
ISDN Term inals for HiPath 3000
10.17 ISDN Term inals for HiPath 3000

An S0 bus in the HiPath 3000 system family can support up to eight ISDN terminals (maximum
of eight terminal equipment identifiers (TEI). Each terminal can be dialed selectively under its
multiple subscriber number or station number.
It is possible to have a maximum of four Gigaset CX340isdn cordless systems for

> each S0 bus. Because of the call switching functions, at least two mobile phones
must be registered at each Gigaset CX340isdn. Thus, at least two terminal equip-
ment identifiers (TEI) will be required for each Gigaset CX340isdn.
The features that can be activated depend on the type of S0 terminal used. Different ISDN fea-
tures are supported depending on the terminal used. Analog station users can activate system
features by means of code procedures. The telephones support only those system features
which can be activated in the idle state.
The dialing behavior of ISDN terminals corresponds to that of DP terminals. The substitute
codes “75” and “76” can be used for the characters “*” and “#” which cannot be used in the
ISDN protocol.
Boards for connecting ISDN terminals

Hardware require- Free S0 port on Free S0 port on Free S0 port on
ments STMD3 CBCC CBCC
CBRC CBRC
STLS2/4 STLS2/4
STLS4R STLS4R
STLSX2/4 STLSX2/4
STLSX4R STLSX4R
Connecting with an optiPoint ISDN adapter
It is also possible to connect an ISDN device to an existing optiPoint 500 telephone

> using an optiPoint ISDN adapter (except for optiPoint 500 entry and optiPoint 500
economy).
A31003-H3570-S100-6-7620, 2008-04-01
wclient.fm

ISDN Term inals for HiPath 3000
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
Nur für den internen Gebrauch HiPath Cordless Office
Overview
11 HiPath Cordless Office

This chapter contains basic information about the operation of HiPath Cordless Office. For
more detailed information, please refer to the HiPath Cordless Office service manual.
11.1 Overview
Chapter contents
Topic
System Configuration, page 11-3
Technical Data for Base Stations, page 11-4
Power-Related Capacity Limits, page 11-6
Multi-SLC and System-Wide Networking, page 11-9
Planning Notes for Networked HiPath 3000 Systems Featuring Network-Wide Roaming, page
11-11
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
HiPath Cordless Office Nur für den internen Gebrauch

Introduction
11.2 Introduction
For HiPath 3000 V1.2 and later, HiPath Cordless Office can be used on all systems of this prod-
uct 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,
HiPath 3500, and HiPath 3300. The connection must be made via one UP0/E interface each. A
mix of base stations of types BS3/1 and BS4 is supported.
A BS3/S (X30807-X5482-X100) single-cell base station can be used to ensure the operation of
a maximum of one base station at the UP0/E interfaces on central control boards in the
HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300. In this case, it is not possible to ex-
pand with additional base stations.
However, base stations cannot be simultaneously connected to the SLC16/SLC16N board and
the CBCC within one HiPath 3550 system.
The base stations BS3/1 (S30807-H5482-X), BS3/3 (S30807-H5485-X), and BS3/S

> (X30807-X5482-X100) are being phased out and may no longer be ordered. You
must use the successor product BS4 (S30807-U5491-X) instead of the types
named.
You can still operate the base stations listed in HiPath 3000. Base stations BS3/1,
BS3/3, and BS4 can also be used in mixed mode.
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
The SLC16 board (S30810-Q2922-X) is no longer supported in HiPath 3000/5000

> V6.0 or later.
The base stations BS3/1 (S30807-H5482-X), BS3/3 (S30807-H5485-X), and BS4 (S30807-
U5491-X) may be used in mixed mode on the above cordless boards.
You can install up to four SLCN boards in HiPath 3800. All four boards provide full cordless
functionality (roaming and seamless connection handover) because the radio fields on the
cordless boards are synchronized within a single system (see Section 11.6).
The HiPath 3000 product line does not currently support the network-wide handover feature.
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
System Configuration
11.3 System Configuration

The following table indicates the maximum possible system configuration parameters for . It
also shows when
● CMA or CMS is necessary
● analog trunk access is possible.
Table 11-1 HiPath Cordless Office - System Configuration for HiPath 3000 Version 3.0
Max. Max. number of base stations
Clock modules
Simultaneous
Max. number
trunk access
num- (BS) with connection via 1xUP0/
to system
calls per BS
System
Analog
ber E
MTs
SLC16N
BS3/S
BS3/S
BS3/1
BS3/3
BS3/1
BS3/3
SLCN
BS4
BS4
– – CMS – 1 – – – 2 – – 8 No
HiPath 3350
– – CMA – 1 – – – 4 – – 8 Yes
HiPath 3300
– – CMA 3 – – 3 4 – – 4 16 Yes
– – CMS – 1 – – – 2 – – 8 No
HiPath 3550
– – CMA – 1 – – – 4 – – 8 Yes
HiPath 3500
– – CMA 7 – – 7 4 – – 4 32 Yes
HiPath 3550 1 – CMS 16 – 8 16 4 – 12 12 64 Yes
250 (with 4
HiPath 3800 – 4 CMS 64 – 32 64 4 – 12 12 Yes
SLCN)1
Explanations:
● 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 base
stations.
● BS4 (S30807-U5491-X): is a base station that supports a maximum of 12 calls when connected using three
UP0/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 Chapter 8).
1 Up to 128 handsets are possible at an SLCN.
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm

Technical Data for Base Stations
11.4 Technical Data for Base Stations
Table 11-2 Technical Data for Various Base Stations
Parameter BS3/1 and BS3/3 BS4 Outdoor cover

BS3/S
Power supply voltage 42 to 54 V 42 to 54 V 42 to 54 V –
range
Power consumption max. 1.7 W max. 3.2 W max. 3.0 W –
Housing dimensions 181 x 139 x 69 202 x 172 x 43 200 x 176 x 49 296 x 256 x 90
(W x D x H in mm)
Weight approx. 0.3 kg approx. 0.5 kg approx. 0.5 kg approx. 1.0 kg
Temperature range for indoor use: for outdoor use:
- 5 to + 50 oC - 20 to + 45 oC
Relative humidity – – – up to 95%
BS3/1 base station
Figure 11-1 BS3/1 S30807-H5482-X Base Station
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
Technical Data for Base Stations
Outdoor cover
A base station must be installed in a weatherproof outdoor cover to guarantee radio coverage
outdoors, for example on factory premises. The outdoor cover is suitable for mounting on walls
of buildings, roofs, and masts.
The outdoor cover S30122-X7469-X is used for BS3/1 (BS3/S), BS3/3, and BS4. A heater is
not required.
Outdoor cover
with BS3/1 (BS3/S)
The Styrofoam block [1] supplied
should be used to affix the BS3/1
(BS3/S). Outdoor cover
with BS3/3
[1]
Figure 11-2 BS3/1 (BS3/S) and BS3/3 in the Outdoor Cover S30122-X7469-X
For information on the various outdoor cover mounting options, refer to the HiPath Cordless
Office Service Manual.
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm

Power-Related Capacity Limits
11.5 Power-Related Capacity Limits

The number of base stations, their distance from the system, and the overall telephone config-
uration determine whether or not the output from the internal system power supply units is suf-
ficient or whether an additional supply is necessary.
● HiPath 3800
If the correct number of LUNA2 modules was calculated, the system’s internal power sup-
ply unit provides sufficient power to supply the system configuration specified in Table 11-
1.
For information on how to calculate the number of LUNA2 modules required, see page 3-
58.
● HiPath 3550 and HiPath 3500
The following tables show which telephone configurations do not need an additional power
supply:
– Table 11-3, depending on the number of BS3/1 and BS4 base stations connected to
the central CBCC/CBRC control board.
– Table 11-4, depending on the number of BS3/1 base stations connected to SLC16N
and the number of BS4 base stations connected to SLC16N.
– Table 11-5, depending on the number of BS3/3 base stations connected to SLC16N
and the number of BS4 base stations connected to SLC16N.
If extra telephone configurations are added to these, an additional power supply (by
EPSU2 or EPSU2-R) is needed.
Table 11-3 HiPath 3550, HiPath 3500 - Maximum Number of Corded Telephones De-
pending on the Number of BS3/1 and BS4 Base Stations Connected to
CBCC or CBRC
of BS3/1s and BS4s
analog telephones
connected via
1xUP0/E to 0 1 - 10 11 - 20 21 - 30 31 - 40 41 - 50
CBCC or CBRC optiset E and optiPoint 500 telephones
1 66 61 57 53 48 44
2 63 59 54 50 46 41
3 60 56 52 47 43 39
4 58 53 49 45 40 36
5 55 51 47 42 38 33
6 53 48 44 40 35 31
7 50 46 41 37 33 28
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
Table 11-4 HiPath 3550- Maximum Number of Corded Telephones Depending on the
Number of BS3/1 Base Stations Connected to SLC16N and BS4 Base Sta-
tions Connected to SLC16N
of BS3/1s and BS4s analog telephones
connected via
1xUP0/E to 0 1 - 10 11 - 20 21 - 30 31 - 40 41 - 50
SLC16N optiset E and optiPoint 500 telephones
1 66 61 57 53 48 44
2 63 59 54 50 46 41
3 60 56 52 47 43 39
4 58 53 49 45 40 36
5 55 51 47 42 38 33
6 53 48 44 40 35 31
7 50 46 41 37 33 28
8 47 43 39 34 30 26
9 45 40 36 32 27 23
10 42 38 33 29 25 20
11 40 35 31 27 22 18
12 37 33 28 24 20 15
13 34 30 26 21 17 13
14 32 27 23 19 14 10
15 29 25 20 16 12 7
16 27 22 18 13 9 5
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm

Number of BS3/3s Connected to SLC16N and BS4s Connected to
SLC16N
connected via
2xUP0/E to 0 1-10 11-20 21-30 31-40 41-50
SLC16N optiset E and optiPoint 500 telephones
1 64 60 56 51 47 42
2 60 56 52 47 43 39
3 57 52 48 43 39 35
4 53 48 44 40 35 31
5 49 44 40 36 31 27
6 45 40 36 32 27 23
7 41 37 32 28 23 19
8 37 33 28 24 20 15
When using an additional power supply (such as EPSU2 or EPSU2-R),

> HiPath 3550 and HiPath 3500 can be expanded up to the maximum possible
capacity limit specified in Table 2-6.

The internal power supply unit in the respective system is the main power source for the base
stations. For more information on the various power supply options, please refer to page 3-146.
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
Multi-SLC and System-Wide Networking
11.6 Multi-SLC and System-Wide 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 views each mobile telephone (mobile station) as a corded telephone. During ad-
ministration, a fixed port on the system’s “home cordless board” is assigned to the MT; this is
used for addressing the MT.
As soon as an MT moves into the area of a different radio switching location (“current-location
cordless board”), an extension connection is switched using a DSS1 connection initiated by the
cordless board. The home and current-location cordless boards exchange a networking proto-
col (User-to-User Signaling UUS) over this extension connection to support full mobility (see
Figure 11-3).
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 for
the permanent connection paths (CorNet NQ, see Section 11.7). That means full mobility
across the radio fields of the different cordless systems. All handset features (callback, team
functions, voicemail, etc.) remain intact. The network-wide handover feature is only exception
here as it is not currently supported.
Required B channels
Table 11-6 Required B channels for Multi-SLC and System-Wide Networking
Mobile telephone (MT) has set Required B Required B chan- Required B chan-
up a connection channels nels for the home nels for the cur-
cordless board rent-location
cordless board
In the home cordless board range 1 1 –
In the current-location Cordless 3 2 1
board range
Handover from home to home 1 1 –
cordless board
Handover from home to current-lo- 3 2 1
cation cordless board
Handover from current-location to 5 3 2
current-location cordless board (temporary) (1 for each cordless
board)
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm

Multi-SLC and System-Wide Networking

Node ID = 1 Node ID = 2
Home SLC16N Current-location
SLC16N no. = 1 SLC16N no. = 2 CorNet NQ SLC16N
Station no. = 124 Station no. = 141 SLC16N no. = 11
Extension Station no. = 128
SLC16B SLC16N connection SLC16N
BS = BS2/2, BS3/1 or
BS BS BS BS BS BS
BS3/3
A CorNet NQ connection is possible using S0 or S2M lines or IP networking (see HG 1500 Administration
Manual).
Figure 11-3 Example of a Cordless Extension Connection in Networked Systems
Networked HiPath 3000 systems feature

● max. 64 networked systems
● accessible using a shared station number (roaming among the systems/nodes)
● call interruption when changing between systems/nodes
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm
Planning Notes for Networked HiPath 3000 Systems Featuring Network-Wide Roaming
11.7 Planning Notes for Networked HiPath 3000 Systems Featuring

Network-Wide Roaming
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 11.6.
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 11.6.
If the “Network-wide roaming” feature is used, please ensure that there is no overlapping in the
radio areas of individual systems with identical DECT IDs. Handsets treat networked systems
with identical DECT IDs as a single system.
If the radio areas of systems with identical DECT IDs overlap, mobile telephones inadvertently
try to perform network wide handover, which results in communication breakdown.
If networking is required for systems in which the individual radio fields overlap (for example,
to increase capacity limits or through decentralized installation), different DECT IDs must be
configured in the individual systems. Network-wide roaming does not apply in this case.
The following describes three different scenarios for networked HiPath 3000 systems.
Scenario 1: Incorrect DECT Configuration of Networked HiPath 3000Systems

Identical DECT IDs and overlapping radio areas result in incorrect handover causing a break-
down in communication.
PSTN
Networking (S0, S2M, IP)
HiPath 3000 System 1 HiPath 3000 System 2

DECT ID = 4711 DECT ID = 4711
Figure 11-4 Incorrect DECT Configuration of Networked HiPath 3000 Systems
A31003-H3570-S100-6-7620, 2008-04-01
cordless.fm

Planning Notes for Networked HiPath 3000 Systems Featuring Network-Wide Roaming
Scenario 2: Correct DECT Configuration when Networking HiPath 3000 Systems

No incorrect handover due to identical DECT IDs despite overlapping radio areas. Disadvan-
tage: network-wide roaming not possible.
PSTN
Networking (S0, S2M, IP)

Figure 11-5 Correct DECT Configuration when Networking HiPath 3000 Systems
Scenario 3: Correct DECT Configuration when Networking HiPath 3000 Systems

No incorrect handover despite identical DECT IDs as the radio areas do not overlap. Network-
wide roaming possible.
PSTN Networking
(S0, S2M, IP)

Figure 11-6 Correct DECT Configuration when Networking HiPath 3000 Systems
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Nur für den internen Gebrauch Service
Overview
12 Service
12.1 Overview
Introduction
This chapter contains information on the options available to service technicians and custom-
ers for
● performing service and maintenance work.
● recognizing and correcting errors.
Such work can be performed on site or using remote service.
Chapter contents
Topic
Service and Maintenance Tasks, page 12-3:
● Backing Up the Customer Database (CDB Backup), page 12-3
● Effects of Hardware Changes on Customer Data, page 12-8
● Relocate/Transfer Application Processor Software (APS), page 12-11
● Determine current system software version, page 12-16
● Upgrading HiPath 3000, page 12-16
● Determining System Information and Installed Software Components
(HiPath Inventory Manager), page 12-17
● Backing Up System Components (Backup Manager), page 12-18
● HiPath User Management, page 12-20
Guided Maintenance, page 12-22:
● Diagnosis Options, page 12-22
● HiPath 3000 Error Messages (Entries in the Eventlog for HiPath 3000), page 12-47
● HiPath 5000 Error Messages (Event Viewer Entries for HiPath 5000), page 12-73
Correcting Errors, page 12-87:
● Automatic Error Correction, page 12-87
● Manual Error Correction Without HiPath 3000/5000 Manager E, page 12-87
● Manual Error Correction With HiPath 3000/5000 Manager E, page 12-88
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Service Nur für den internen Gebrauch

Overview
Topic
Remote Service, page 12-89:
● HiPath 3000 Connection Options, page 12-90
● HiPath 5000 Connection Options, page 12-91
● Remote System Administration, page 12-91
● Remote Correction of System Software (APS), page 12-92
● Remote Error Signaling, page 12-93
● Controlled Release of a Remote Connection, page 12-94
● Remote Administration and Access Using PPP, page 12-94
Security Features, page 12-96:
● Access Security, page 12-96
● Automatic Logging of Administration Procedures, page 12-106
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Service and Maintenance Tasks
12.2 Service and Maintenance Tasks
12.2.1 Backing Up the Customer Database (CDB Backup)

A distinction is made here between
● backup of customer data without HiPath Software Manager and
● backup of customer data with HiPath Software Manager.
12.2.1.1 Customer Data Backup Without HiPath Software Manager
Definition
CDB backup refers to saving the customer database (CDB) to the multimedia card MMC (Hi-
Path 3000) or copying the cyclic RAM data and saving it in two PDS (Permanent Data Service)
files (HiPath 5000).
Note: The RUN LED flashes repeatedly for a short period to signal that a CDB backup, which
takes about 30 seconds, is in progress on the MMC.
12.2.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 for this backup
are stored in an SRAM area (with battery backup) in the central control board. If the SRAM area
is full, the customer data is automatically backed up. This means that the entire CDB, including
SRAM content, is copied from the SDRAM in the central control board to the MMC. The current
CDB is simultaneously stored on the MMC along with the “old” CDB, which is not deleted 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 re-accessing the CDB backup on the MMC, the system’s database can be re-
stored to the state it was in prior to the power outage.
Regardless of the volume of changes to the database, HiPath 3000 always automatically per-
forms a complete CDB backup at midnight, system-time.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

HiPath 5000
On the communication server, RAM data is copied automatically every three minutes and
stored 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 charge data
● status data
The directory in which the two PDS files are to be stored must be defined when the HiPath 5000
software is installed (setup). The two PDS files are created when the HiPath 5000 is started for
the first time.
The PDS files must not be modified, as reading of the files using conventional tools
> and interpretation of the content is not possible without specialist knowledge.
In the event of an error, the PDS files can be made available to the responsible Ser-
vice Support contact for diagnostic purposes. The *.trc and *.dmp files stored in
the diag subdirectory of the installation directory should also be supplied.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
12.2.1.1.2 Manual Customer Data Backup with HiPath 3000

You can perform a manual CDB backup using HiPath 3000/5000 Manager E (in online mode)
or Manager T.
However, be aware that it is not possible to deliberately abort a manual backup that is initiated
using Manager T. Once the CDB backup process starts, it should be ended because the back-
up continues to run in the background.
You can also manually initiate a CDB restore, including the call detail data, from the MMC.
Procedure: Manual CDB backup, system restore using Manager T
Step Activity
Manual customer data backup on the MMC
1. Manager T: Start system administration
2. Menu 28 -> Edit CDB
3. Menu 28-2 -> Back up CDB data
4. Menu 28-2-1 -> CDB on MMC
Loading the saved customer data from the MMC into the system
1. Manager T: Start system administration
2. Menu 28 -> Edit CDB
3. Menu 28-2 -> Back up CDB data
4. Menu 28-2-2 -> CDB from MMC
Caution: When performing this action, the system performs a hard restart.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

12.2.1.2 Customer Data Backup with HiPath Software Manager
Definition
The HiPath Software Manager supports, among other things, the backup of customer databas-
es (Backup Manager) from all HiPath 3000/5000 systems in t114he same customer network
(see also Section 12.2.7, “Backing Up System Components (Backup Manager)”).
The CDB backups are stored in a directory which must be defined in advance. The data backup
can 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.
Refer to the help provided with the HiPath Software Manager for information on backing up cus-
tomer data with this tool.
12.2.1.3 CDB Treatment When Replacing Central HiPath 3000 Hardware
A new license file is always required if a central control board that requires a license
> has to be replaced. As a result of the replacement, the MAC address changes and
the license becomes invalid.
For information on this procedure, please see Section 8.4.7.
When replacing a central control board due to a hardware defect, for example, the following
options are available for handling the CDB:
● Procedure: After replacing the board, load the “current” CDB to the system
Step Activity
1. Copy the current CDB and save it on the MMC.
2. Disconnect the system from the power supply.
3. Remove the MMC.
4. Replace the central control board.
5. Insert the MMC.
6. Restart the system by plugging in the power plug.
7. The CDB previously stored on the MMC is loaded to the system RAM. The
customer system is now configured:
● The CMI mobile telephones are logged on.
● The V.24 baud rate is set up.
● The ACD login port is configured.
● All telephone options, such as volume and display, are determined per
station.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
● Procedure: After replacing the board, load the “old” CDB from the customer disk to
the system
Step Activity
1. Back up current CDB with HiPath 3000/5000 Manager E.
2. Disconnect the system from the power supply.
3. Remove the MMC.
4. Replace the central control board.
5. Insert the MMC.
7. Reload.
8. If an “older” CDB update is imported, reload the CDB into the system with-
out the Delta mode. The “hardware and CDR switch” remain inactive.
9. Reset. The customer system is now configured. All you have to do now is
● log on the CMI mobile telephones again,
● reset the V.24 baud rate,
● re-configure the ACD login port,
● redefine all telephone configurations, such as volume and display, per
station.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

12.2.2 Effects of Hardware Changes on Customer Data

Any changes to the hardware must be made before creating a copy of the customer database
using HiPath 3000/5000 Manager E. You must ensure that the hardware configuration on the
MMC of HiPath 3000 is always current.
Hardware changes include:
● removing or inserting boards (HiPath 3000 only).
● removing or inserting telephones.
● removing or inserting add-on devices or adapters.
12.2.2.1 Inserting and Removing HiPath 3000 Boards
Caution
7 When using HiPath 3550, HiPath 3350, HiPath 3500, and HiPath 3300, disconnect
the system from the power supply before removing or inserting boards.
Only HiPath 3800 peripheral boards can be removed or inserted during operation.
Startup rules for inserting and removing boards
If Then
Inserting new board in The board is integrated into the system according to the rules for
free slot initial startup (see Chapter 4, “Installing HiPath 3000”).
● System with default numbering plan
The station numbers from the new board are appended (con-
secutively and in ascending order) to the numbers already as-
signed.
● System with modified numbering plan
The station numbers on the new board can be in any order.
Using HiPath 3000/5000 Manager E or Manager T, you can assign
a specific station to a port. If the number is already assigned to a
different object, you can switch both numbers.
Replacing board with Board is activated. The same station range is used.
same or under equipped
board type
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
If Then
Replacing board with Board is activated. The old station range is activated and the ports
over-equipped board of associated with the new board are inserted at the end. The ports
same type are split if there is no contiguous station range available.
In the case of subscriber line modules, you can use HiPath 3000/
5000 Manager E to retain the old station data by copying it to the
new board, or you can delete it and reset the default state. Copying
is not possible for trunk boards.
Replacing with a differ- The system does not automatically activate the board.
ent board type After removing the old board, you can delete it from the database
using HiPath 3000/5000 Manager E or Manager T.
After you have inserted the new board, the system activates it as if
it had been inserted into a free slot. However, the CDB area used
by the old board is left as a gap.
In the case of subscriber line modules, you can use HiPath 3000/
5000 Manager E to retain the old station data by copying it to the
new board, or you can delete it and reset the default state. Copying
is not possible for trunk boards.
If you initiate a system reload on a system updated as described above, the system
> must be reset after the updated CDB has been installed. The reset synchronizes the
port placement sequence in the system with that of the CDB.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Procedure: Exchanging boards
Step Activity
2. Remove the board(s).
4. Delete board slot using user interface (29-4).
6. Insert new board(s).
8. Load customer data from the system.
Adapt customer data to new hardware configuration. Insert new board(s), (sta-
tions, for example).
9. Load new customer data into the system.
12.2.2.2 Exchanging Workpoint Clients

You can add or remove workpoint clients while the system is in operation. The data in the re-
moved workpoint clients is retained.
In case of various optiPoint 500 or optiset E telephone models, meaning ones that have a dif-
ferent number of programmable keys, the keypad layout of the previous model is retained. Add-
on devices that are not plugged in retain their technical features. With the HiPath 3000/5000
Manager E, you can delete the add-on devices that are not plugged in and remove the keys
that are no longer available.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
12.2.3 Relocate/Transfer Application Processor Software (APS)
APS replacement/transfer is not possible with HiPath 5000. You must perform a
> complete software upgrade.
For system software updates, a distinction is made between

● HiPath 3000 systems without HiPath Software Manager and
● HiPath 3000 systems with HiPath Software Manager.
For networked HiPath 3000 systems with HiPath 5000 RSM, an APS update can only be per-
formed with HiPath Software Manager.
12.2.3.1 APS Replacement/Transfer for HiPath 3000 Systems Without

HiPath Software Manager
Two memory areas are reserved for the application processor software on the MMC. To be able
to store two complete APS and to keep the transfer time as low as possible, part of an APS is
stored in a compressed format. The APS is decompressed after it has been transferred from
the MMC to the SDRAM area of the central control board.
12.2.3.1.1 Transferring an APS of HiPath 3000 by Replacing the MMC
APS replacement is only possible within a version and if a logical, compatible CDB
> is available.
Procedure
Step Activity
1. Create a backup of the current CDB and save on a customer disk for security
reasons.
2. Remove MMC with “old” APS.
The flashing Run LED (0.1 s on/0.1 s off) indicates that the MMC is missing.
The system remains active for call processing.
3. Install new MMC with “new” APS.
The system creates an automatic CDB backup and thus saves the current cus-
tomer database (CDB) to the new MMC.
4. An automatic reset is then performed (hard restart for entire system with the
current CDB).
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Step Activity
5. Use the “APS stamp” to verify that the new APS has been activated. Use Hi-
Path 3000/5000 Manager E or Manager T (menu item 29-1-2) to make the
necessary query.
12.2.3.1.2 APS transfer
Options
The APS Transfer feature is available with the HiPath 3000/5000 Manager E. It facilitates
● the on-site replacement of the APS by means of a direct connection via the V.24 interface
or preferably via the integrated analog/digital modem or via LAN.
● an APS transfer via remote service from a central service center using the integrated an-
alog or digital modem or via LAN.
Function
This feature transfers the new APS in its entirety and stores it in the available area of the MMC.
After the transfer, the checksum is analyzed. The system subsequently reports whether or not
● an error was found.
If so, you have to delete the transferred APS.
● the APS transfer was successful.
You can then activate the APS immediately or at a later time.
Resetting the system initiates the changeover from the old APS to the new APS. If problems
occur during this process, the old APS is reactivated. Once the changeover is successful, the
old APS is deleted from the MMC.
In case of power outage, the SDRAM content that has no battery backup and the active APS
are completely lost. By re-accessing the current APS on the MMC, the system can be restored
to the state it was in prior to the power outage.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Procedure
Step Activity
1. Save the existing customer data (for example: as “customer1.kds”).
2. Select “Open CDB” from the HiPath 3000/5000 Manager E file menu and high-
light “APS files (*.fst)”.
Open the fst file using the new system software.
3. Double-click the “Transfer” icon:
Select the appropriate access and enter the PIN code.
4. Highlight “APS Transfer”. A new window appears in the top right of the screen.
You can use this window to select whether
● to change directly to the APS after the transfer is completed.
● to change to the APS at a pre-determined time.
Note: If the “APS Transfer” field has a gray background, then the fst file was
not opened correctly.
5. Start the APS transfer. Transfer time for connection via digital modem (ISDN)
or LAN is approximately 20 to 30 minutes. Connections via the IMODN analog
modem or direct connections (V.24 interface) require longer transfer times.
6. Once the APS transfer is completed, the HiPath 3000/5000 Manager E reports
that the “APS transfer was successful”. Once the set transfer time has been
reached, the system resets and the new version is used for startup.
7. Use the “APS stamp” to verify that the new APS has been activated. Use Hi-
Path 3000/5000 Manager E or Manager T (menu item 29-1-2) to make the
necessary query.
Notes on the APS transfer sequence

● If the transfer connection is interrupted (due to a line interruption, for example), the entire
APS transfer must be manually restarted via HiPath 3000/5000 Manager E. The complete
APS transfer is performed again.
● Since the software is written to the MMC in compressed format during APS transfer, it must
be unpacked after the transfer is complete (this takes about 5 minutes).
● After the APS transfer, the checksum is analyzed. If errors are found in the checksum, de-
lete the transferred APS. You then have to repeat the complete APS transfer.
● Once the APS has been successfully transferred, the message “APS transfer was suc-
cessful” appears. You can then finish the session.
● The system software uses a special system reset (none of the other resets initiate a
changeover) to change over to the new APS.
You cannot use the telephone while the system resets and boots up.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

● After a successful changeover to the new APS, an entry in the error memory is also made
and the old APS on the MMC is deactivated. This does not impede switching traffic. The
deactivated area is now available for a new APS transfer. The positive or negative entry in
the error memory is sent to the service center.
APS stamp: explanation using example
HE620S.10.123
Production number/software binder
Feature package
Note: Service Maintenance Releases
(SMR) are identified by production num-
ber and feature package.
System: ● up to and including V4.0:
T = HiPath 3250/HiPath 3150
U = HiPath 3550/HiPath 3500/Hi-
Path 3350/HiPath 3300
● V5.0 or later:
A = HiPath 5000
P = HiPath 3800
S = all HiPath 3000 systems except
HiPath 3800
Version: 600 = HiPath 3000/5000 V5.0
620 = HiPath 3000/5000 V6.0
Software: A = Manager/Assistant ...
E = System
HiPath ...
Software modifications for the correction of faults and the provision of a small num-
> ber of new features are called software updates or service maintenance releases
(SMR). A CDB conversion is not necessary.
Software upgrades are used for more extensive enhancements to the scope of ser-
vices. An upgrade may also include modifications to hardware as well as error cor-
rections. A software upgrade changes the name of the version, for example, from
V1.0 to V2.0. A CDB conversion may be necessary.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
12.2.3.2 APS Transfer for HiPath 3000 Systems With HiPath Software Manager
Definition
The HiPath Software Manager supports, among other things, updates of the system software
(Upgrade Manager) of all HiPath 3000 systems in the same customer network. An update of
the software of installed HG 1500 boards (HG 1500 V3.0 SMR-3 or later) can also be per-
formed.
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 systems
Note: The file format “*.fli” must be selected for APS transfer using HiPath Software Man-
ager.
The software (APS and/or HG 1500) is updated in two steps. First, the new software is loaded
to a system memory known as the “shadow area”. This occurs in the background independently
of the system status.
In the second step, the new software version must be made available, in other words, the
switch from the current software version to the new software version must take place. The cur-
rent software is replaced by the software in the shadow area and thus deleted. The changeover
can either be started immediately once the software has been loaded or performed at a pre-
defined time.
Caution
7 It is important to make sure that the changeover time for a HG 1500 board does not
coincide with the changeover time for the corresponding HiPath 3000, as this can
render the HG 1500 board unfit for operation. The default setting of the HiPath Soft-
ware Manager therefore incorporates a safety margin of 10 minutes between the
changeovers.
Information about updating the system software and the HG 1500 software using HiPath Soft-
ware Manager can be obtained from the help provided with this tool.
Note: If HiPath Software Manager is not available, the HG 1500 software update must be per-
formed with HiPath 3000 Manager I (up to and including HG 1500 V2.0) or Web-based Man-
agement WBM (HG 1500 V3.0 or later).
For APS transfer using HiPath Software Manager, the HiPath 3000/5000 TFTP server must be
installed on a server in the customer LAN. All HiPath 3000 systems must be able to access this
HiPath 3000/5000 TFTP server over IP. Other TFTP servers cannot be used for HiPath Soft-
ware Manager.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

12.2.4 Determine current system software version

The current version of the software can be determined using:
● HiPath 3000/5000 Manager E (System status: System-wide – System – Software Version)
The current version of the software for the communication system is displayed.
● The first system client (not optiClient 130, 29-1-2 SW part number)
The current version of the software for the communication system is displayed.
Siemens Enterprise Communications GmbH & Co. KG introduced the new "Re-
> lease Management" software in October 2006.
Connected with this software are the following uniform versioning and terminology
for all products and solutions:
Vx Ry.Z.n
● Vx = major release. Corresponds with the release of a new product version.
● Ry = minor release on the basis of a major release with a minor improvement in
functionality.
● z = fix release on the basis of a minor release. Generally only contains the cor-
rection of bugs.
● n
– = 0 in major releases, minor releases, and fix releases (generally available
software editions).
– = max. four-digit number for hotfixes for targeted use in case of a high-pri-
ority error (software editions on the basis of a fix release with limited avail-
ability).
Examples:
● V7 R3 .1.0 = fix release 1 for minor release 3 of major release (version) 7.
● V7 R3.5.1037 = hotfix on the basis of fix releases 5 for minor release 3 of major
release (version) 7.
Software changes for the provision of new features to a smaller extent is called a minor release
(MR). A CDB conversion is not necessary.
Major releases (raising of the version number) are used for more extensive enhancements to
the scope of services. An upgrade may also include modifications to hardware as well as error
corrections. A major release (raising of the version number) results in a change in the name of
the version, for example, from V6.0 to V7. A CDB conversion may also be necessary.
12.2.5 Upgrading HiPath 3000

For information on upgrade procedures, please see Section 9.3, “Upgrading HiPath 3000 to
Version 3.0”.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
12.2.6 Determining System Information and Installed Software

Components (HiPath Inventory Manager)
Definition
HiPath 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 upon
initial start-up of the service.
The relevant information can be displayed in table format by clicking one of the following but-
tons:
● Master Setup
Information including version and installation date of the master setup.
● HiPath 3000
Hardware and software information regarding the HiPath 3000 systems in the network and
the installed HG 1500 boards.
● HiPath Applications
Information 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 System
Information 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 system
information can be queried manually at any time. This should always be done before an update/
upgrade, for example.
Further details on how to determine the system information using HiPath Inventory Manager
can be obtained from the help provided with this tool.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

12.2.7 Backing Up System Components (Backup Manager)
Definition
The HiPath Software Manager allows the following system components and databases of a Hi-
Path 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 the
HiPath 3000/5000 network as well as databases (Feature Server, SQL Server).
● HG 1500 backup
This menu item displays all HG 1500 boards in the HiPath 3000/5000 network in an over-
view. It is possible to back up the data of one or all of the displayed HG 1500 board(s)
(HG 1500 V3.0 SMR-3 or later).
● HiPath 3000 backup
With 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 backup
With 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).
Refer to the help provided with the HiPath Software Manager for information on backup with
this tool.
Setting options
It is possible to specify individually when a backup is to take place and where the backed up
data can be stored.
● Time of data backup
The data backup can either be started manually immediately or performed at a predefined
time. By default, a full backup is performed cyclically, with the data being saved daily at a
specific time.
● Backup path
The path for the directory in which the backup files are to be stored can be specified.
● Backup to a local drive
There is no need to specify a special user account for this type of backup.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
● Backup to a network drive

A user account (user name, password) with write permission for the network drive must be
specified for this type of backup.
If the backup source (for example HiPath 5000) is located on a separate PC, this user ac-
count must have read permission for the shared drive.
The backup path and the type of backup are preset for the HiPath Software Manager during
setup.
Restoring data
The HiPath Software Manager allows damaged databases to be restored with the database
backup.
The other system components are restored using HiPath 3000/5000 Manager E (for HiPath
3000) and HiPath 3000 Manager I (for HG 1500 up to and including V2.0) or Web-based man-
agement WBM (for HG 1500 V3.0 or later).
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

12.2.8 HiPath User Management

HiPath User Management will be implemented in Small Remote Site scenarios in HiPath 3000/
5000 V5.0 and later. These are networks in which HiPath 4000 functions as a central system.
HiPath 3000 systems are used in smaller branch locations (Small Remote Sites, SRS).
IP stations can be “relocated” from one branch (HiPath 3000) to another (HiPath 3000) or from
the central office (HiPath 4000) to a branch (HiPath 3000) and vice versa via HiPath User Man-
agement.
Small Remote Site Concept

In normal mode, all IP workpoint clients (system clients) are registered with the central system
HiPath 4000. In an emergency (failure of the central HiPath 4000 system or the CorNet IP net-
work), the IP workpoint clients in the branch react and automatically register with their branch
HiPath 3000 via the SRS concept. These workpoint clients are then available to users with all
features of HiPath 3000.
The IP workpoint clients (system clients) reregister with the central HiPath 4000 system when
normal mode is resumed.
The Small Remote Site concept requires that branch systems and the central system are con-
nected via an IP network. It is not possible to integrate HiPath 5000 PCs with HiPath ComScen-
do Service. System clients (IP workpoint clients) such as optiPoint 410 (not optiPoint 410 en-
try), optiPoint 420 and optiClient 130 are supported.
For further information on the Small Remote Site concept, refer to the HiPath 3000/5000 Ver-
sion 3.0 Feature Description.
HiPath 3000 Element Manager

The link between HiPath User Management and the HiPath 3000 systems involved is the Hi-
Path 3000 Element Manager. For the central HiPath 4000 system, access is accomplished via
Element Manager in HiPath 4000 Manager.
Element Manager allows the central administration of a Small Remote Site scenario via HiPath
User Management.
After installing HiPath 3000 Element Manager, configure the HiPath 3000 systems to be admin-
istered via HiPath User Management. You can do this via the HiPath 3000 Element Manager
web-based configuration interface. You can add or remove individual systems in the node con-
figuration menu. Once you have added a system (node), any information on its configured IP
workpoint clients (system clients) is retrieved immediately via SNMP.
The basic configuration of HiPath 3000 for an SRS scenario is carried out via HiPath 3000/5000
Manager E (Settings menu: Set up station (emergency mode)). User Management recognizes
the configured system clients and identifies them internally as HiPath 3000 SRS telephones.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
The next procedure depends on customer specifications:

● The IP workpoint clients in the Small Remote Sites (branches) should use the same call
numbers in normal mode (registered with HiPath 4000) and in emergency mode (regis-
tered with HiPath 3000).
In this case, the call numbers are assigned via HiPath User Management.
When configuring the IP workpoint clients (system clients) via HiPath 3000/5000 Manager
E their call numbers should be deleted. Otherwise it is not possible to assign call numbers
via HiPath User Management without taking further steps.
● The IP workpoint clients in the Small Remote Sites (branches) should use different call
numbers in normal mode (registered with HiPath 4000) and in emergency mode (regis-
tered with HiPath 3000).
In this case, the call numbers are assigned via HiPath 3000/5000 Manager E when config-
uring the IP workpoint clients (system clients).
An IP workpoint client configured in this way can then be assigned a HiPath 4000 call num-
ber for normal mode via HiPath User Management.
The following configuration data for an IP workpoint client is modified via HiPath User Manage-
ment:
● Internal call number
● DID number
● Directory name
● CFSS destination
● Access groups
Refer to the HiPath User Management service and administrator documentation for
> information on the installation and configuration procedures for HiPath 3000/5000
and HiPath 3000 Element Manager.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3 Guided Maintenance
12.3.1 HG 1500 Front Panel

The HG 1500 board has a front panel that displays the status of the V24 and the two LAN in-
terfaces, the assignment of the individual resources (H323, D.38, PPP, and VCAPI) as well as
the assignment of the DSP channels.
12.3.2 Diagnosis Options
12.3.2.1 Recording HiPath 3000 Board Status
12.3.2.1.1 Central Control Boards
RUN LED
A RUN LED that displays the system’s operating capacity is located on the central control
board.
RUN LED Meaning

Off No power
On System boot
Off Load operation: APS in SDRAM, loadware, and card data
for 0.1 s
0.5 s on/0.5 s off
0.1 s on/0.1 s off
Options available?
You can call up the following options using the HiPath 3000/5000 Manager E:
● CMA
● CMS
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
● LIM
● IMODN
● MPPI, UAM (only with HiPath 3550, HiPath 3350) or UAMR (only with HiPath 3500, HiPath
3300)
The availability of one of these Announcement and Music Modules is displayed as
“Option 5”.
The ALUM4 module cannot be displayed.
12.3.2.1.2 Power Supplies
Table 12-3 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 or
EPSU2R).
Power Box PB3000 The LED displays the operating status (on or off).
12.3.2.1.3 Peripheral Boards
Viewing peripheral board status

You can use HiPath 3000/5000 Manager E or Manager T to view the status of all peripheral
boards. 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, or
is busy).
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
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 boards
integrated into the system are presented in a table. The status display is updated every 3 sec-
onds.
With Manager T, you can only view the status of one board at a time. You can also update the
status display by pressing a key.
You cannot perform additional activities with the HiPath 3000/5000 Manager E and Manager T
while viewing the status of a board.
Table 12-4 HiPath 3000/5000 Manager E - Example of Status Display of Peripheral
Boards
Slot Board not Defective Blocked Free Res. Clock

inserted source
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
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
Locking out and releasing boards and ports

Using the HiPath 3000/5000 Manager E and Manager T, you can lock out a complete station
or trunk module. The lockout prevents renewed seizure after the current connection has fin-
ished. Release or lockout settings are also retained after a reset.
The first SLMO/SLU board can be blocked. This action does not block the first two ports. You
can block specific ports with the “Block selection” option.
Ports of an IVM or HG 1500 board cannot be locked.
When attempting to lock out the last active trunk, you are subsequently notified that remote ser-
vice through the service center is no longer possible.
12.3.2.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 Contents
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-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.3 Recording Station Status

HiPath 3000 records the current status of each individual station in a table. You can use HiPath
3000/5000 Manager E to view the station status, in which case the following information is pro-
vided.
Data Contents
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
Language 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 second
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
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
Data Contents
Activated features Status of activated features (on or off):
● Do Not Disturb
● Call forwarding (device status)
● Answer text
● Room monitor
● Lock Code
● Suppress calling ID
● Call connection
● Disable incoming ringing
● Out of Hunt group/Group ringing
● Call waiting tone
● Direct Answering
● Call waiting terminating
● Ring transfer (only for MULAP)
● Call forwarding MULAP (only for MULAP)
Stations included List of the stations included
12.3.2.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, in
which 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 3000
DSR = Telephone
RTS = HiPath 3000
CTS = Telephone
This means, for example, that incorrectly connected or damaged cables can be deter-
mined (for more information on this, refer to the HiPath 3000/5000 Manager E Help).
● V.24 Monitoring
The number of sent/received bytes within a selected time period can be recorded and then
displayed/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 a
remote error signal (V.24 failure = “Check printer” error message, V.24 restart = Withdrawal of
error message).
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.5 Trace Options for HiPath 3000
Special user rights are required for activating the Trace setting in the Maintenance
> menu, that are exclusively reserved by the user group Development.
Tracing ISDN activities

This feature allows the user to trace ISDN telephones (subscriber ports) and ISDN trunks (trunk
ports) in real time. ISDN activities are routed to HiPath 3000/5000 Manager E and saved in a
trace file. Only the ISDN sequences are displayed on the monitor, not the content of the ISDN
messages.
The feature is activated in HiPath 3000/5000 Manager E by selecting the “Call Monitoring” tab
under Maintenance. The Start button starts Call Monitoring, whereupon the data of all available
ports in the system is read out.
If the trace session is over, you can start the ISDN Message Decoder (ISDN Tracer) and use
it to convert the trace file into a readable format (English only). You can also read out the trace
data using remote service.
The ISDN Message Decoder is a 32-bit application which converts ISDN layer-3 messages and
information elements into a readable format. Since you cannot find out from the trace file
whether it deals with an information element from a Euro ISDN or a QSig configuration, you
have 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 two
settings, the Hex values are decoded and interpreted for each feature (CC, AOC, etc.).
Tracing call-specific activities

You can trace all activities that were initiated by a call for telephones, trunks, etc. These include
consultation calls, conference calls, and hunt groups, for example.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.2.6 HiPath Manager PCM Trace Monitor for HiPath 5000
12.3.2.6.1 HiPath Manager PCM Trace Monitor Applications

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,
exchanged immediate messages, program and communication messages for the relevant
component in a separate trace window, in other words, a separate window is opened for each
component (application).
The trace windows can be viewed using the Trace Monitor and swapped out for further pro-
cessing.
This documentation does not cover interpretation of the trace window contents by
> the Trace Monitor. Trace files are used for problem analysis and are interpreted by
Service 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.
Trace messages can be displayed for the following HiPath 5000 applications:
● Feature Server
– \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
– \winnt\system32\dssdiagnosefile.txt
– \winnt\system32\dsslogfile.txt
● HiPath Manager PCM Administration
Administration of the configuration parameters for component control by the user, for gen-
eral parameters, for call charge evaluation and analysis.
● HiPath Manager PCM
Configuration of call handling and call forwarding using definable profiles.
● HiPath GetAccount
Internal component that is responsible for evaluating and saving call charges and for im-
mediate printing.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.6.2 Starting and Exiting the Trace Monitor

The HiPath Manager PCM program group was created when installing the HiPath Manager
PCM server. Administration and the trace monitor were integrated here.
To start the Trace Monitor, select Start - Programs - HiPath - HiPath Manager PCM
Trace Monitor for HiPath Applications.
Figure 12-1 Trace Monitor

The Trace Monitor can be closed with Exit in the File menu, with the key combination h +
D or with the Trace Monitor system menu.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.2.6.3 The Screen Layout of the Trace Monitor

When you start the Trace Monitor, an application window with the following layout appears:
Exit
Title bar Maximize

Trace Monitor sys- Minimize
tem menu
Menu bar
Trace window sys-

tem menu
Workspace
(open trace win-
dows)
Status bar
Figure 12-2 The Screen Layout of the Trace Monitor
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
The Trace Monitor menu bar lists the available menus/menu items.
Table 12-5 Trace Monitor Menu Functions
Menu Menu item Function

name
File Print Setup Setup of the printer for the output of trace mes-
sages to the printer.
Exit Closes the Trace Monitor
Trace Use Hex font The output of special trace messages with non-
displaying characters is displayed in a hex font
(option active) or in ANSI font (option not active).
Default messages are always displayed in ANSI
format.
Colored Text Toggles between color (option active) and black-
and-white display (option not active) for trace
messages.
Add Date/Timestamp Inserts a timestamp in each new trace message
when the option is active.
Show Window for new Appli- If this option is active, one of the applications that
cation writes trace messages is immediately displayed
in a separate trace window when it is activated.
If the option is not active, trace windows for ac-
tive applications can be opened or closed manu-
ally by selecting the entry Trace - <Name of Ap-
plication>.
Window Cascade Displays the trace windows in a cascade.
Tile Vertically Displays the trace windows side by side.
Tile Horizontally Displays the trace windows one above the other.
Arrange Icons Arranges the trace windows reduced to an icon.
? About... Activates Trace Monitor program information.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.2.6.4 General Functions
Opening and closing a trace window

The following options are available for opening and closing trace windows:
● Automatic
Select the option Show New Logon Immediately (checkmark visible next to menu item) in
the Trace menu to activate the automatic opening/closure of trace windows when the rel-
evant application is started/exited. To disable this option, select the entry again. The check-
mark is removed.
● Manual
If this option is not set, you can open and close the trace windows for the active applica-
tions manually. The Trace menu should be activated for this purpose. The first entries dis-
played are the available trace windows. Open trace windows are checkmarked.
– To open a closed window you must activate the entry. The checkmark is set and the
trace window is opened.
– To close an open window you must reactivate the entry. The checkmark disappears
and the trace window is closed.
Print trace window content

You also have an option that allows you to output the current status of a trace window to the
configured Trace Monitor printer for documentation purposes. For this, select the Print Mes-
sages entry via the System menu or, alternatively, the Context menu (right click in the Trace
window) of the relevant Trace window. The current contents of the trace window are then sent
to the configured printer.
Deleting the contents of the trace window

To delete the contents of a trace window, select the Delete Messages entry via the system
menu or, alternatively, the Context menu (right click in the Trace window) of the relevant Trace
window. The contents are deleted and the window is empty.
Freezing the contents of a trace window

To stop messages scrolling, you can freeze the current status of the trace window display. For
this, select the Stop Window Scrolling entry via the system menu or, alternatively, the Context
menu (right-click in the Trace window) of the relevant Trace window. The contents of the trace
window are frozen. New trace messages are loaded to the buffer, but are no longer displayed.
To disable this option, select the menu item Stop Window Scrolling again. The option is re-
moved and recent messages are displayed.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
Arranging trace windows

The active Trace Monitor trace windows can be arranged as follows:
● Cascade
Using the key combination < + E or via the Cascade entry in the menu window.
● Tile Horizontally
Using the key combination < + F or via the Tile Horizontally entry in the menu
window.
● Tile Vertically
Using the key combination < + D or via the Tile Vertically entry in the menu win-
dow.
If the Trace windows are minimized as symbols, these can be arranged using the status bar.
For this, select the Arrange Icons entry in the menu window.
12.3.2.6.5 Exporting Trace Windows

Each trace window has a capacity of 1,000 (for the Server PC under Windows 95/98) or 5,000
entries (for the Server PC under Windows NT or Windows 2000). When this capacity is
reached, the oldest entry is deleted from the trace window for each new entry.
To document a current situation from a trace window, you can save the current status of a trace
window to a swap file.
Procedure
1. The Write Messages to File entry should be selected via the system menu or, alternative-
ly, the context menu (right-click in the Trace window) of the relevant Trace window.
A message box containing the path and file name of the swap file for the trace window ap-
pears:
2. Confirm the message with OK.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
The default destination directory for swap files is the Windows 2000 shell user directory:
C:\Documents and Settings
\[Windows User]
\My Documents
\[Application ID]
\[Trace File Name]
The following naming conventions apply to swap files:
<Application ID><Time>.trc
The time is stored in YYYYMMDDhhmm format.
Example of a file name for a swapped-out trace file

Windows User: Meier
Application: GetAccount
Exported on: 06.09.2004
at: 16:57:
C:\Documents and Settings
\Meier
\My Documents
\WACLIENT \WACLIENT200409061657.trc
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.7 Trace Options and Evaluations in Connection with SRTP

The Secure Realtime Transport Protocol (SRTP) is the secure version of the RTP protocol. It
is used in IP telephony for transferring encrypted voice traffic.
Data can be encrypted from:
● gateway to gateway
● gateway to workpoint client
● workpoint client to workpoint client
This results in two scenarios:
● Encrypted signaling from gateway to gateway: CorNet NQ is encrypted.
Firstly, the connection is set up via H.323. The CorNet NQ container is then sent in encrypt-
ed form via the IP network.
Traces can be performed as usual, but do not include data in the CorNet NQ container (for
example, signaling messages, station number information).
● Encrypted payload from workpoint client to workpoint client and from gateway to workpoint
client: CorNet TS is encrypted.
The connection setup via CorNet TC is already partially encrypted. The CorNet TS data
records contained in this setup are completely encrypted. This means that voice data (in-
cluding DTMF tones) is transmitted in encrypted form. In the case of data connections, the
data is encrypted for transmission. If RFC2833 is activated (this must be activated if secu-
rity is activated), information about key actions (user input indication) on the workpoint cli-
ent is also encrypted and transmitted.
The rest of the CorNet TC message is not encrypted. Messages that do not contain CorNet
TS data records are not encrypted either.
During a trace, the RTP data flow can be read out as usual. Voice quality cannot be eval-
uated due to payload encryption.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.2.8 Eventlog for HiPath 3000

HiPath 3000 features an eventlog where accrued errors are classified according to error class
and error number with the date/time of the original error. You can use HiPath 3000/5000 Man-
ager E to read out the eventlog.
Section 12.3.3 contains information on the possible entries.
12.3.2.9 Testing Telephones

After startup and country adaptation, you can activate the terminal test on any
optiPoint 600 office (in UP0/E mode), OpenStage, optiPoint 410 and optiPoint 420 telephone
using a code or the service menu.
It is not possible to perform the terminal test on optiPoint 410 S and optiPoint 420 S telephones.
This test checks the display (your number is displayed), LEDs, and ring tones. The tests ends
automatically after a period of time. The test allows you to perform a visual and acoustic check
of the components to ensure that they are functioning properly.
Test procedure on the system telephone
Table 12-6 Terminal Test

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.
The phone number, date and time are normally shown in the display. If a different text appears
(“Gateway not found”, for example), this means that there is an error.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.10 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 Event
Viewer administers logs that record information on programs, security, and system events on
the 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 any
application 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 validity
of 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/Administrative
Tools/Event Viewer
The Event Viewer associated with other application servers present can be opened via the Hi-
Path 5000 server. To do this, select the relevant server in the network browser under Opera-
tion/Connect to another computer/Other computer.
Configuring the Event Viewer

The Event Viewer has at least three areas:
● System log: information on all operating system components
● Security log: information on changes to the security system and possible system violations
● Application log: application events
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
You can configure these areas independently of one another by marking the area and selecting
Operation/Properties:
● The maximum log size (in KB) and the reaction if this value is exceeded are defined under
“General”. 1.44 MB (= capacity of a floppy disk) is the recommended log size. “Overwrite
events where necessary” is the recommended setting.
● You can select an event source under “Filter” for example, to display only the entries for
the HiPath 5000 server. You can further restrict the output under Category and Event ID.
Evaluating events
Double-click an entry in an Event Viewer area to obtain more precise information on an event.
Use the two arrow buttons to spring from one event to the next.
The HiPath 5000 Server entries in Table 12-8 are currently supported.
Saving the event file (log file)

If problems occur within the customer network, you can save an Event Viewer area as an event
log (log file) and then forward this file to the relevant Service Support personnel for further di-
agnosis.
Always save an eventlog (log file) in evt file format (file extension *.evt). The Event Viewer
can only read and configure the file if it is in this format.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.11 HiPath 5000 State Viewer

The current status of the HiPath ComScendo service and all associated services can be
checked via the State Viewer.
This can be invoked via Start/Program Files/HiPath/HiPath 5000 State Viewer.
Figure 12-3 HiPath 5000 State Viewer

The example in Figure 12-3 illustrates the correct operation of a HiPath ComScendo service.
For the server itself (“= Running”) and all services, the “status indicators are green”.
Menu bar
● Program – Exit: Closes the HiPath 5000 State Viewer.
● Server
– Start: Starts the HiPath 5000 server.
– Stop: Stops the HiPath 5000 server.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
● Configuration
– CPU allocation: In the case of a PC with a multi-processor system or HT processor,
defines whether the operating system may distribute the threads of the Feature Pro-
cessing (FP) and LAN Device Handler (LDH) services may be distributed over different
processors.
– Network card: In the case of a PC with more than one network card, defines which card
is used for HiPath 5000 (may only be changed if the HiPath 5000 server becomes con-
gested).
● About...
– Version information: Shows the version of the installed modules (.dll, .exe).
– About HiPath 5000 State Viewer...: Shows the current APS stamp and code number.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
Procedure in the event of a fault
Administrator rights are required for the following measures.

>
In the event of a fault, in other words if one or more “status indicators are red”, proceed as fol-
lows:
1. Check the status of the services
Select Settings - Control Panel - Administrative Tools - Computer
Management.
All services must be started here (as shown in Figure 12-4, for example). If this is not the
case, invoke log.txt.
Figure 12-4 HiPath 5000 Services
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
2. Open log.txt file

The log.txt file contains detailed information about the services. You can open this file
via <Installation Directory>/PCSData/Debug.
Figure 12-5 log.txt File

3. If a required service has not been started, then the HiPath ComScendo service should be
stopped and restarted using the State Viewer.
If the State Viewer has no connection to the HiPath 5000 server, the “Siemens Service
Monitor Service” should be restarted. To do this, click the “Start Server” button (see
Figure 12-3).
If this does not work either, the HiPath ComScendo Service software must be uninstalled
and then reinstalled using the instructions set out in Section 6.6.4.
If problems arise during operation (crashes, incorrect telephone responses, etc.) contact
the relevant service support organization. The *.trc and *.dmp files stored in the diag
subdirectory of the installation directory should also be supplied to service support for di-
agnostic purposes.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.12 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 system
MIB 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 functions
Simple Network Management Protocol (SNMP) represents a convenient platform within the
TCP/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 HiPath
3000 and HiPath 5000. It is possible to:
● 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 enabling
ports, and determining free ports).
● transmit service-related Class B errors.
● visualize the operating status of a HiPath 3000 and HiPath 5000.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.2.13 Licensing Analysis
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 Support
during servicing.
12.3.2.13.1 Analysis Using Customer License Manager (CLM)

The CLM installation directory (for example, C:\Program Files\licensing\license
manager) contains the Trace directory among other things. Each time the TomCat Web server
is started, a new subdirectory is created to which the trace output is then written. Trace output
can be viewed using MS Internet Explorer.
You can define the size of the trace files as well as the degree of detail of a trace in a configu-
ration file (in the example C:\Program Files\licensing\license manager\Apache
Tomcat\ClmSettings.xml):
<TraceFilesQuantity>3</TraceFilesQuantity>
This value (for example 3) indicates how many trace files are used cyclically.
<TraceFileEntries>1000</TraceFileEntries>
This value (for example 1000) defines the maximum number of trace entries per trace file.
<TraceLevel>4</TraceLevel>
This value (1 – 8) defines the degree of detail: 1 = Low (important events only), 4 = Stan-
dard (including external interfaces), 8 = All.
12.3.2.13.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 are
viewed using the CLM. This provides a good overview of an error situation that helps to narrow
down 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 in
the bin subdirectory of its installation directory. The degree of detail (off, low, standard, all) and
the size (in MB) of this recorded information can be defined using the Customer License Man-
ager (CLM).
Extensive reconstruction of an error is generally made possible by setting 100 MB for the size
and a “standard” degree of detail.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
12.3.2.14 Analysis Using HiPath Software Manager and

HiPath Inventory Manager
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 Support
during servicing.
Trace files
The installation directory of the Common Web Service (default = C:\Program Files\sie-
mens\hipath\commonweb) contains, among other things, the Trace directory, in which the
trace files for the Web applications HiPath Software Manager and HiPath Inventory Manager
are stored.
This directory name is saved in a registry key during installation. If this key cannot be accessed,
the trace files are stored in the temporary system directory (as the Common Web Service is
started as a system service). Under MS Windows 2000, this directory normally has the name
C:\WINNT\temp, while under MS Windows 2003 it is called C:\WINDOWS\temp.
Each time a Web application is started by the Common Web Service (TomCat Web server), a
separate subdirectory is created. This subdirectory contains the trace files in XML format. The
subdirectory name follows the convention date_<DATE>_time_<TIME>.
In order to enable service support to perform diagnosis, the complete Trace directory must be
made available. Adaptations for more detailed traces can be made in consultation with service
support using the CFG files in the config directory. These adaptations refer to the degree of
detail (level) of the trace file and application options for the components of all Web applications.
Inventory diagnosis data

When the HiPath Inventory Manager is operated with the “verbose mode” flag set (on the set-
tings page), the following XML files are saved in the temporary directory of the system (see
above):
● swmreport.xml – contains the information generated during an update of the system in-
formation by the HiPath Software Manager.
● invdataos.xml – contains the data for the operating system for the last update.
● invdatasnmp.xml – contains the data for the HiPath 3000/5000 network from the last
update.
● invdataapps.xml – contains the data for the applications from the last update.
● invdatamaster.xml – contains the data for the master setup from the last update.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.3 HiPath 3000 Error Messages (Entries in the Eventlog for

HiPath 3000)
Classification
Accrued errors are classified according to error class and error number. The three different er-
ror classes are described below:
● Error Class A = Customer-related error
HiPath 3000/5000 Manager E fails to issue a signal/message. Class A errors are indicated
on the optiPoint Attendant display. They can be corrected by the customer without service
support.
The following error messages are implemented at present:
– “Printer Alarm” (caused by paper out, for example)
– “Fan Failure” (caused by failure of the fan with HiPath 3500 or HiPath 3300)
– “Revisor Alarm” (caused by overflow of the log part of the MMC, for example).
– “Too Many Key Modules” (caused by attaching more than the maximum possible num-
ber of optiPoint key modules specified in Table 10-15)
● Error Class B = Service-related errors
Class B errors can be read out via the HiPath 3000/5000 Manager E Event Log, which can
be automatically forwarded to a service center.
Errors of this class are, for example, failure of the boards, individual ports, or trunks. You
can generally correct these errors by replacing the hardware, re-configuring the customer
database, or by working together with the carrier. Table 12-7 lists all Class B errors.
● Error Class C = Development-related errors
HiPath 3000/5000 Manager E fails to issue a signal/message.
Class C errors require diagnosis and problem analysis by specialists.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance
Table 12-7 HiPath 3000 Class B Error Messages
No. HiPath 3000/ Meaning Required Measures Note

5000 Manager E:
Event Log Entry
Error Class 01 - General Messages
01-003 !System Restart Hard restart (reset) None
of entire system
with current CDB.
01-010 !SNMP System Hard restart of en- None
Restart tire system via SN-
MP.
01-014 local DB changes “On site” changes None
to the database.
01-015 remote DB “Remote” changes None
changes to the database.
01-016 !SNMP APSXF APS transfer ac- None
result knowledgement
message via SN-
MP.
01-017 !SNMP authenti- Unauthorized ac- Check firewall settings in Hi-
cation fail cess attempt. Path 3000/5000 Manager E
(Network – Firewall).
01-018 !SNMP 80 % high Changes logged Read out data using HiPath
watermark of log- internally in the 3000/5000 Manager E
file system: 80% of (Transfer – Security – Proto-
write capacity col).
used.
01-019 !Sensor Alarm Temperature in Hi- Check the fan and air supply
Path 3500/HiPath in the 19-inch housing. Note
3300 19-inch hous- the ambient temperature.
ing is too high.
01-020 !CDR buffer limit Overflow in the Check that the interfaces
reached CDR buffer (CDR (V.24, LAN), ports and the
information). connection are functioning or
read out call data.
01-021 !Authentication Unauthorized ac- Check firewall settings in Hi-
Failure cess attempt. Path 3000/5000 Manager E
(Network – Firewall).
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
01-022 !Flash deleted Flash area deleted. None APS transfer
possible again.
01-023 !Process stopped Process stopped. Perform hard restart (reset).
01-024 !unauthorized ap- Attempted access Check firewall settings in Hi-
plication via an unautho- Path 3000/5000 Manager E
rized application. (Network – Firewall).
01-025 !manual switch-
back from HiPath
Manager
Error Class 02 - License Management Messages
02-002 !START Grace HiPath License None The remaining
Period Management: Start license validity
of grace period. period is
shown on the
display.
02-003 !START Reg. Lic HiPath License None
File Management: Start
of regular licens-
ing.
Error Class 09 - Hardware Module Messages
09-000 !microprocessor Microprocessor er- Check power at the power
fault on, common ror. supply unit.
If this error persists, replace
the central control board.
09-001 !microprocessor The microproces- None
fault off, common sor error has been
corrected.
09-002 !loadware memo- Error in loadware Replace the board if neces-
ry fault on, com- memory. sary.
mon
09-003 !loadware memo- Error in loadware None
ry fault off, com- memory has been
mon corrected.
09-029 !line interruption Line interruption Check the line and terminal.
(error on)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
09-030 !short circuit Short circuit on the Check the line, terminal, and
(error on) board specified. port.
09-031 !under voltage Under voltage. Check the power and line at
(error on) the terminal’s power supply
unit.
09-032 !thermal over- The specified Check the fan and air supply
load (error on) board is overheat- in the 19-inch housing. Note
ed. the ambient temperature.
09-036 !slip detected on A bit slip has oc- Check the S0 line. The problem
(STMD) curred on an ISDN If necessary, reload the may be caused
line. board or perform a hard re- by asynchro-
start. nous internal
If the error persists, set up an and external
ISDN trace. clock rates.
Data loss pos-
sible/connec-
tion may be
terminated.
09-037 !slip detected off The bit slip on the None
(STMD) ISDN line has been
corrected.
09-038 !alarm indication Alarm display: An Check the S2M line and
signal error on S2M error has oc- board.
(TMS2M) curred. Replace the board if neces-
Physical line/board sary.
problem (too many If the error persists, set up an
CRC/SLIP errors). ISDN trace.
09-039 !alarm indication Alarm display: The None
signal error S2M error has been
off(TMS2M) corrected.
09-042 !no signal error on Alarm display: An Check the S2M line and
(TMS2M/STMD) S2M error has oc- board.
curred. If necessary, reload the
No physical con- board or perform a hard re-
nection available. start.
If the error persists, set up an
ISDN trace.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
09-043 !no signal error off Alarm display: The None
(TMS2M/STMD) S2M error has been
corrected.
09-044 !receive remote Alarm display: An Check the board and partner
alarm error on S2M error has oc- system or arrange for a tech-
(TMS2M) curred. nician to do so.
Physical problem
with the communi-
cation partner (too
many CRC/SLIP
errors).
09-045 !receive remote Alarm display: The None
alarm error off S2M error has been
(TMS2M) corrected.
09-048 !bitslip error on A bit slip has oc- Check the S2M line. The problem
(TMS2M) curred on an ISDN If necessary, reload the may be caused
line. board or perform a hard re- by asynchro-
Data loss pos-
sible/connec-
tion may be
terminated.
09-049 !bitslip error off The bit slip on the None
(TMS2M) ISDN line has been
corrected.
09-050 !loss of synchro- A synchronization Check the S2M line. The problem
nisation error on error has occurred. If necessary, reload the may be caused
(TMS2M) board or perform a hard re- by asynchro-
Data loss pos-
sible/connec-
tion may be
terminated.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
09-051 !loss of synchro- The synchroniza- None
nisation error off tion error has been
(TMS2M) corrected.
09-058 !Self test error on Error while self- If necessary, replace the
(SLMO) testing the speci- board or change the slot.
fied SLMO board.
09-059 !Self test error off Error while self- None
(SLMO) testing the speci-
fied SLMO board
has been correct-
ed.
09-061 !Overcurrent on Overcurrent on the Check the power and line on
power controller specified SLMO the terminal and power sup-
on (SLMO) board. ply unit.
Replace hardware if neces-
sary.
09-062 !Overcurrent on Overcurrent on the None
power controller specified SLMO
off (SLMO board has been
corrected.
09-065 !Out of buffers for Insufficient pool Check lines and terminals.
card error on capacity on the Set up a default trace.
specified SLMO ● High traffic load: –> Dis-
board. tribute load to several
boards.
● Board is faulty: -> Re-
place board.
09-066 !Out of buffers for Insufficient pool None
card error off capacity on the
specified SLMO
board has been
corrected.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
Error Class 11 – General Messages
11-058 !Too many L1 er- Too many layer 1 Check the lines, terminal,
rors errors. and port.
A short circuit may have oc-
curred.
Error Class 12 – Processor Exceptions
12-000 Initial Stack Ptr Reset: Initial Stack Set up a trace using informa-
Pointer tion from Back Level Support
BLS.
Create a stack dump.
Save a snapshot.
12-001 Initial Prg. Reset: Initial Pro- Set up a trace using informa-
Counter gram Counter tion from Back Level Support
BLS.
Save a snapshot.
12-002 bus_error Interrupt Bus Error Set up a trace using informa-
tion from Back Level Support
BLS.
Save a snapshot.
In the case of HiPath 3550 or
HiPath 3500, this problem
may be caused by a software
error –> Upgrade required.
12-003 adress_error Interrupt Address Set up a trace using informa-
Error tion from Back Level Support
BLS.
Save a snapshot.
12-004 illegal_instruction Interrupt Illegal In- Set up a trace using informa-
struction tion from Back Level Support
BLS.
Save a snapshot.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
12-005 zero_division Interrupt Zero Divi- Set up a trace using informa-
sion tion from Back Level Support
BLS.
Save a snapshot.
12-006 Invalid opcode Invalid Opcode Ex- Set up a trace using informa-
ception tion from Back Level Support
BLS.
Save a snapshot.
12-007 TRAP V Instruc- TRAPcc, TRAP V Set up a trace using informa-
tions Instructions tion from Back Level Support
BLS.
Save a snapshot.
12-008 Privilege Violation Privilege Violation Set up a trace using informa-
BLS.
Save a snapshot.
12-009 Trace Trace Set up a trace using informa-
BLS.
Save a snapshot.
12-010 Line 1010 Emula- Line 1010 Emula- Set up a trace using informa-
tor tor tion from Back Level Support
BLS.
Save a snapshot.
12-011 Line 1111 Emula- Line 1111 Emulator Set up a trace using informa-
tor tion from Back Level Support
BLS.
Save a snapshot.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
12-012 Hardware Break- Hardware Break- Set up a trace using informa-
point point tion from Back Level Support
BLS.
Save a snapshot.
12-013 Reserved Co- Reserved Copro- Set up a trace using informa-
proc. Violation cessor Violation tion from Back Level Support
BLS.
Save a snapshot.
12-014 Format Error Un- Format Error Unini- Set up a trace using informa-
init. Inter. tialized Interrupt tion from Back Level Support
BLS.
Save a snapshot.
12-015 Format Error Un- Format Error Unini- Set up a trace using informa-
init. Inter. tialized Interrupt tion from Back Level Support
BLS.
Save a snapshot.
12-017 critical input inter- HiPath 3800, Off- Set up a trace using informa-
rupt set 0x0100, Critical tion from Back Level Support
Input Interrupt BLS.
Save a snapshot.
12-018 machine check HiPath 3800, Off- Set up a trace using informa-
interrupt set 0x0200, Ma- tion from Back Level Support
chine Check Inter- BLS.
rupt Create a stack dump.
Save a snapshot.
12-019 data storage in- HiPath 3800, Off- Set up a trace using informa-
terrupt set 0x0300, Data tion from Back Level Support
Storage Interrupt BLS.
Save a snapshot.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
12-020 instr. storage in- HiPath 3800, Off- Set up a trace using informa-
terrupt set 0x0400, In- tion from Back Level Support
struction Storage BLS.
Interrupt Create a stack dump.
Save a snapshot.
12-021 alignment inter- HiPath 3800, Off- Set up a trace using informa-
rupt set 0x0600, Align- tion from Back Level Support
ment Interrupt BLS.
Save a snapshot.
12-022 program interrupt HiPath 3800, Off- Set up a trace using informa-
set 0x0700, Pro- tion from Back Level Support
gram Interrupt BLS.
Save a snapshot.
12-023 system call inter- HiPath 3800, Off- Set up a trace using informa-
rupt set 0x0C00, Sys- tion from Back Level Support
tem Call Interrupt BLS.
Save a snapshot.
12-025 watchdog timer HiPath 3800, Off- Set up a trace using informa-
interrupt set 0x1020, tion from Back Level Support
Watchdog Timer BLS.
Interrupt Create a stack dump.
Save a snapshot.
12-026 data TLB interrupt HiPath 3800, Off- Set up a trace using informa-
set 0x1100, Data tion from Back Level Support
TLB Interrupt BLS.
Save a snapshot.
12-027 instruction TLB HiPath 3800, Off- Set up a trace using informa-
interrupt set 0x1200, In- tion from Back Level Support
struction TLB Inter- BLS.
rupt Create a stack dump.
Save a snapshot.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
12-028 debug interrupt HiPath 3800, Off- Set up a trace using informa-
set 0x2000, Debug tion from Back Level Support
Interrupt BLS.
Save a snapshot.
Error Class 15 – Messages Concerning APS Transfer and Saving on Flash
15-000 !Req to switch Request for APS None
over APSXF transfer.
15-001 !APS switched APS transfer was None
over KDS ok successful.
15-002 !APS switched APS transfer was Check CDB version.
over def. KDS not successful.
Default CDB load-
ed.
15-003 !CRC checksum Error in CRC Check APS version.
error checksum. Retransfer APS.
If the error persists, replace
the MMC module.
15-004 !APS switched APS transfer was Load stored CDB into the An error oc-
back def. KDS not successful. system. curred while
Default CDB load- Check APS version. starting up the
ed. Provide snapshot and stack new APS. The
dump for analysis. system has
Restart APS transfer or per- switched back
form a speed upgrade. to the old APS.
If the error persists, replace As a result, the
the MMC module. CDB was set
to “Default”.
15-005 !APS switched APS transfer was Load stored CDB onto the An error oc-
back old KDS not successful. system. curred while
Old CDB loaded. Check APS version. starting up the
Provide snapshot and stack new APS. The
dump for analysis. system has
Restart APS transfer or per- switched back
form a speed upgrade. to the old APS.
the MMC module.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
15-006 !APS Transfer APS transfer inter- Check the transmission link
disconnected rupted. and interface.
Restart APS transfer.
15-007 !Country-text Country-specific None
transfered texts successfully
transferred.
15-008 !Error by deleting Shadow APS can- Check APS version.
MMC not be deleted. Restart APS transfer.
the MMC module.
15-009 !Blck_lenght err Block length error Check the transmission link
apsxf/ctxt during country- and interface.
specific text trans- Retransfer APS.
fer.
15-010 !Rest_length err Remaining length Check the transmission link
apsxf/ctxt error during coun- and interface.
try-specific text Retransfer APS.
transfer.
15-011 !Speed-Upgrade Speed upgrade None Software was
was successful. updated. Pre-
vious CDB is
still used.
15-012 !APSXF aborded APS transfer was None
manually stopped.
Error Class 16 – Operating System Messages
16-001 GET-POOL xx, xx Error in system Set up a trace using informa-
from=xx ad- pool administration from Back Level Support
dr=xxxxxxxx tion. BLS.
Save a snapshot.
16-002 RELPL xxxxxxxxx Error in system Set up a trace using informa-
len=xxxx, pool administration from Back Level Support
from=xx tion. BLS.
Save a snapshot.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
16-004 !Error in Cosmos- COSMOS send er- Set up a trace using informa-
Send ror (software mes- tion from Back Level Support
sage transmis- BLS.
sion). Create a stack dump.
Save a snapshot.
16-005 !Error in Cosmos- COSMOS timer er- Set up a trace using informa-
Timer ror (software timer tion from Back Level Support
administration). BLS.
Save a snapshot.
16-006 !Error in Cosmos- COSMOS receive Set up a trace using informa-
Receive error (software tion from Back Level Support
message receipt). BLS.
Save a snapshot.
16-007 COSMOS ID=xx COSMOS error Set up a trace using informa-
opcode=0xnnnn during restart tion from Back Level Support
ercode=0xnnnn BLS.
Save a snapshot.
16-009 RESTARTED: Overload or contin- Set up a trace using informa- The system
watchdog uous loops during tion from Back Level Support was un able to
software operation. BLS. reach idle sta-
System watchdog Create a stack dump. tus within ap-
restarted the sys- Save a snapshot. proximately
tem. ten minutes.
16-010 RESTARTED: Hard restart (reset) None
manual Reset was manually trig-
gered.
16-011 RESTARTED: Manual reload. None The CDB is re-
manual Reload set to default
status.
16-012 RESTARTED: No power Check line voltage.
Power down Check power supply.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
16-013 !KDS bakkup not Customer data Check the MMC module and
performed was not backed up replace if necessary.
to MMC.
16-014 RESTARTED: un- Hardware reports Check environmental influ-
known rest. HW- an unknown reset ences (for example, ground-
ind. mismatched reason. ing).
Central control board prob-
lem: -> Replace board.
16-015 !general error log- Error while writing Check the MMC module and
ging the log file to the replace if necessary.
MMC module.
16-017 !CTXT take over Country-specific Retransfer country-specific
failed texts cannot be ap- texts and change the lan-
plied. guage again.
16-020 !CSTA: length out CSTA interface: Use the CSTA browser (ap-
of range Required length plication emulation) to check
exceeds the per- the CSTA interface.
mitted range. In- Set up a CSTA trace and a
correct internal pa- default system trace.
rameters. Check whether or not the ap-
plication has been released.
16-021 !CSTA: Alloc() er- CSTA interface: Al- Use the CSTA browser (ap-
ror location fails. plication emulation) to check
the CSTA interface.
Set up a default trace with
CSTA.
16-023 APS x fetched Startup acknowl- None
from MMC edgement after
speed upgrade.
16-024 !idle arrived after System has None
restart reached idle status
after restart.
16-030 !exceed. of CSTA Number of CSTA Check the number of sub-
mon. pts monitor points ex- scribers, lines, and ACD
ceeded. groups configured.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
Error Class 18 – Messages Concerning Database Handling and License Management
18-012 HLM:Start grace HiPath License If necessary, load license The remaining
period Management: from the CLS and relicense license validity
Grace period start- the system. period is
ed. shown on the
display.
18-016 HLM:Feat-ID: xxx HiPath License If the customer still requires The remaining
expiration started Management: The this feature, a new license license validity
specified feature is file must be ordered and period is
still valid for up to loaded to the system. shown on the
30 days. display.
18-017 HLM:Feat-ID: xxx HiPath License If the customer still requires
expired Management: The this feature, a new license
validity period of file must be ordered and
the specified fea- loaded to the system.
ture has expired.
18-018 HLM: set license HiPath License Load license from the CLS This error only
to default Management: All li- and relicense the system. occurs in com-
censes have been bination with
deleted. the following
error messag-
es:
1. HLM: Invalid
license data.
2. HLM: MAC
ID mismatch.
3. HLM: Lic
failure period
stopped de-
fault lic.
4. HLM: Grace
period
stopped, de-
fault license.
All licenses are
deleted in each
of these cases.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
18-019 HLM: Invalid li- HiPath License Check licensing.
cense data Management: The Load the original license file
license file is in- from the CLS and relicense
valid or has been the system.
manipulated.
18-020 HLM:Lic failure HiPath License Check and reestablish the The system
period started Management: The connection to HiPath 5000 was licensed in
system is no longer RSM. a network and
connected to Hi- is now no long-
Path 5000 RSM. er connected
to HiPath 5000
RSM.
You have 30
days to rees-
tablish the con-
nection. All
system licens-
es will be de-
leted after this
period.
18-021 HLM:Lic failure HiPath License None
period stopped li- Management: The
cense ok connection be-
tween the system
and HiPath 5000
RSM is reestab-
lished.
18-022 HLM: Lic failure HiPath License Check and reestablish the
period stopped Management: The connection to HiPath 5000
default lic connection be- RSM.
tween the system Load license from the CLS
and HiPath 5000 and relicense the system.
RSM was not rees-
tablished within 30
days. All licenses
were deleted.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
Error Class 19 – Network Services Messages
19-002 !SNTP-Server not No connection to Check the application and
responding the SNTP server. the connection.
Error Class 20 – Call Processing Messages
20-002 !RS232: DSR not The RS232/V.24 Check the interface, the line,
Ready interface is out of and the application.
order.
20-011 !RS232: DSR The RS232/V.24 None
ready interface is now
operational.
20-013 !not connected The maximum Use the project planning tool
ways number of connec- to test the system configura-
tion paths permit- tion.
ted has been ex- Set up a trace using informa-
ceeded. tion from Back Level Support
BLS.
Save a snapshot.
20-017 !int. charg buf Internal call data Read out call data.
ovflw memory overflow. If the error persists, check
the call data application inter-
face.
20-029 !Forced trunk dis- Manual line re- None
connection lease (for U.S.
only).
20-032 !CDR Mem. alloc. Advanced call data ● System with MMC mod-
failed memory cannot be ule: MMC module is
created. faulty. Replace the
MMC.
● HiPath 2000: File sys-
tem in flash is full or
faulty.
20-033 !CDR Cache al- Read cache for Perform a hard restart (nor- This is caused
loc. failed reading out CDR mally occurs automatically). by insufficient
data cannot be cre- system memo-
ated. ry capacity.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
20-034 !CDR Data write Error while writing MMC module: If necessary,
failed CDR data to the read out call data via TFTP.
advanced call data The internal administration
memory. structure is also corrected, if
this is required.
20-035 !CDR Adm. write Error while writing MMC module: If necessary,
failed the administration read out call data via TFTP.
structure to the ad- After this, replace the MMC
vanced call data module.
memory.
20-036 !CDR Data read Error while reading Set up a trace using informa-
failed CDR data from the tion from Back Level Support
advanced call data BLS.
memory. Create a stack dump.
Save a snapshot.
20-037 !CDR Adm. read Error while reading Set up a trace using informa-
failed administration tion from Back Level Support
structure from the BLS.
advanced call data Create a stack dump.
memory. Save a snapshot.
20-038 !CDR Data de- An advanced call None
tected data memory was
found during sys-
tem startup.
20-039 !CDR Data over- The advanced call Read out call data.
flow data memory is
full.
20-040 !CDR Mem. allo- The advanced call None
cated data memory was
successfully creat-
ed.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
20-041 !CDR Mem. re- The advanced call None This message
leased data memory was is issued after
temporarily re- the call data
leased. memory has
been com-
pletely read
out. It must be
followed by the
“CDR Mem. al-
located” mes-
sage.
20-042 !MMC-size Output of MMC None During system
module size startup, the
size of the
MMC module
is read out and
hexadecimally
output in bytes
1 and 2 of the
info bytes. Val-
ue “00 10” de-
scribes the 16-
MB MMC, val-
ue “00 40” de-
scribes the 64-
MB MMC.
This does not
apply to HiPath
2000.
20-043 !CDR-MMC MMC Memory on the
full MMC module or in
the HiPath 2000
file system is insuf-
ficient for creating
the advanced call
data memory.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
Error Class 21 – Device Handler Messages
21-000 !no dial tone de- No dial tone de- Use headset to check dial
tected tected. tone.
Replace port or terminal if
necessary.
21-001 !dial tone detect- Dial tone detected. None
ed
21-007 !Referenztakt ON ISDN clock found. None
21-008 !Referenztakt ISDN clock lost. Check that the clock is avail-
OFF able on the S0/S2M line.
If necessary, use HiPath
3000/5000 Manager E to cor-
rect the clock’s allowed/de-
nied numbers list (Trunk –
Clock parameters).
If necessary, perform a hard
restart (reset).
21-011 !Fan Alarm ON Fan error. Check the fan and air supply
in the 19-inch housing. Note
the ambient temperature.
21-012 !Fan Alarm OFF The fan error has None
been corrected.
21-013 !no ack from No response from
temp. sensor temperature sen-
sor.
21-014 !overload at co- Not enough DTMF Use a larger system.
dereceiver receivers.
21-015 !overload at code- Not enough DTMF Use a larger system.
transmit. transmitters.
21-019 !Shorten Msg not Internal error: An Set up a trace using informa-
succesfull overlong ISDN tion from Back Level Support
message could not BLS.
be shortened by Create a stack dump.
deleting Facility Save a snapshot.
IEs.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
21-028 !Power Alarm on Emergency battery Check line voltage.
operation due to Note battery capacity.
power outage.
21-029 !Power Alarm off Power supply re- None
stored.
Error Class 23 – Messages from the Device Handler Network
23-060 !system hold, no System hold, no Set up a trace using informa-
buffer available more free buffer tion from Back Level Support
available. BLS.
Save a snapshot.
23-061 !Check config For U.S. only: TM- Check TMDID board config-
rules for TMDID DID boards incor- uration using information
rectly configured. from page 4-48 and correct if
necessary.
Error Class 26 – Board Administration Messages
26-000 !unknown card Unknown board. System does not support the The board may
type board type. Replace the be too old or
board with a valid board type too new for the
or remove it from the system. system.
26-001 !card out of ser- The specified None
vice board is out of or-
der.
26-002 !More than al- The maximum Reduce the number of
lowed amount of number permitted boards of this board type.
cards for a certain board Note the maximum configu-
type is exceeded. ration.
26-003 !other card type Incompatible board Replace the board or use
than old card type type. The slot is al- Manager T to delete the pre-
ready pre-as- assigned board type so that
signed with a dif- the new board is recognized.
ferent board type.
26-004 !card in service The specified None
board is operation-
al.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
26-007 !Reload after The specified If this error persists, replace The board is
load-LW-Code er- board has been re- the board. reloaded due
ror loaded due to a to a load error
startup error. (length, check-
sum error) or a
missing or de-
layed acknowl-
edgement dur-
ing startup.
Error Class 28 – Recovery Messages
28-000 !not possible to Error while trans- Set up a trace using informa-
send a message mitting message tion from Back Level Support
via COSMOS (in- BLS.
sufficient resourc- Create a stack dump.
es). Save a snapshot.
28-004 !SLC-Trace fin- SLC LW trace Trace memory can now be
ished transferred to trace read out.
memory.
28-006 --- tttttttt -> Time stamp set in None A time stamp
hh:mm:ss --- event log B memo- (current time
DD.MM.YY --- ry. and date) is
entered when
the event log B
memory is
copied. This
facilitates anal-
ysis.
28-008 --- APS: Current APS ver- None The current
Hexxxxx.xx.xxx:x sion entered in APS version is
x xxx ---- event log B memo- entered when
ry. the event log B
memory is
copied. This
facilitates anal-
ysis.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
Error Class 29 – Messages Concerning Board Communication
29-000 !error from COS- COSMOS error. Set up a trace using informa-
MOS tion from Back Level Support
BLS.
Save a snapshot.
29-010 !receive buffer not Receive buffer is Set up a trace using informa- The board re-
free not free. tion from Back Level Support ceive buffer
BLS. cannot receive
messages
from the sys-
tem (perfor-
mance prob-
lems).
29-014 !illegal pointer Invalid pointer. Set up IOP trace.
29-024 !polling time out The specified If this error persists, check
board has malfunc- the board and the slot.
tioned.
29-025 !card ist present- Loadware of speci- If this error persists, check
LW has resetted fied board restart- the board and the slot.
itself ed.
29-035 !ELIC deadlock ELIC clock supply Check clock supply. Possible caus-
no Interrupt from malfunction. Check central control board. es:
ELIC ● Faulty
clock sup-
ply
● Environmen-
tal influ-
ences
● Faulty
control
board
Error Class 30 – Board Software Messages
30-006 !XCSEPBC: PBC PBC or ELIC error Replace the board.
error on the specified
board.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
30-016 !HEATER ON - Temperature in Check the HG 1500 fan kit
HXG3 HiPath 3550/Hi- and the air supply in the wall
Path 3350 wall housing. Note the ambient
housing is too high. temperature.
30-017 !HEATER OFF - Temperature in None
HXG3 HiPath 3550/Hi-
Path 3350 wall
housing is normal.
30-061 !short circuit on Short circuit in Check lines.
Upoe Port SLMC base station line. Replace base stations.
on
30-062 !short circuit on Short circuit in None
Upoe Port SLMC base station line
off has been correct-
ed.
Error Class 32 – Messages Concerning IVM (HiPath Xpressions Compact) and EVM (En-
try Voice Mail)
32-000 !Configuration
link up
32-001 !Configuration
link down
32-008 !TIMEOUT during
server-msg
32-010 !IVM: Exception IVM: An unexpect- Set up an IVM trace.
(unexpected ered error has oc-
ror) curred.
32-011 !IVM: SW-error IVM: A software er- Set up an IVM trace.
ror has occurred. Upgrade IVM if necessary.
32-013 !IVM: HD assign- IVM: 80% of hard Search IVM statistics for
ment of memory disk used. mailboxes with too many un-
space 80% deleted messages.
32-014 !IVM: HD full IVM: Hard disk is Search IVM statistics for
full. mailboxes with too many un-
deleted messages.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

5000 Manager E:
Event Log Entry
32-015 !IVM: Mailbox not IVM: Mailbox is not Check whether the subscrib-
available available. er in question is available in
the event log.
Set up IVM system mailbox if
necessary.
32-016 !IVM: IVM: Software up- Reload the board if neces-
SW_Upgrade not grade is not possi- sary.
possible ble. Upgrade software again.
32-017 !IVM: Reload oc- IVM: Reload per- None
cured formed.
32-018 !IVM: Restore IVM: Faulty re- Perform restore again.
faulty store.
32-019 !IVM: HD assign- IVM: Hard disk None
ment of memory load less than
space <70 % 70%.
32-020 !IVM: Unautho- IVM: Unauthorized If the attempt is unintention-
rized call attempt call attempt. al, deactivate the station
number length.
If the attempt is intentional,
create an IVM trace to deter-
mine the subscriber who
made the attempt.
32-030 VMM Cmd-resp EVM: Command Reload the board.
timeout response timeout. If the error persists, replace
the board.
32-032 memory level of EVM: 80% of Check EVM mailboxes for
80% memory used. too many undeleted messag-
es.
32-033 Presence evt EVM: Presence
from EVM Event from EVM.
32-041 VMM msg limit EVM: Message Check EVM mailboxes for
reached limit reached. too many undeleted messag-
es.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

5000 Manager E:
Event Log Entry
32-042 no language EVM: No language Check available languages
available file available. on the EVM.
Load a language if neces-
sary.
32-044 VMM buffer over- EVM: VMM buffer
flow overflow.
32-046 EVM error during EVM: EVM error
DM during Data Mode.
32-049 DH_EVM->reset EVM: System -
EVM DH_EVM -> reset
EVM.
32-052 AM com during EVM: AM Com-
DM mand during Data
Mode.
32-053 Memory Full EVM: Memory Full.
32-055 No Pill File select- EVM: No Pill File Check available languages
ed Selected. on the EVM.
Load a language if neces-
sary.
32-058 Philips API ER- EVM: Philips API
ROR ERROR.
32-059 I2C failure detect- EVM: I2C failure
ed detected.
Error Class 40 – Messages Concerning MMC Module Access
40-000 !MMC not MMC module can- ● MMC module is not con-
plugged or defec- not be accessed nected: –> Connect the
tive during startup. MMC.
● MMC module is faulty: –
> Replace the MMC.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance
12.3.4 HiPath 5000 Error Messages (Event Viewer Entries for

HiPath 5000)
Table 12-8 lists the possible entries for HiPath 5000 in the Event Viewer.
The Source column designates the origin of the possible entries:
● HiPath AllServe = Feature Server events
● GetAccount = GetAccount events
● PCM = HiPath Manager PCM events
The various components of these sources are identified by means of the abbreviations in the
Category column. Section 6.3 contains information about the most important components of
the Feature Server.
Table 12-8 Event Viewer Entries for the HiPath 5000 Server
Event De- Error text Meaning User reaction Cate- Source

fault gory
trap
1000 X Not defined Unidentified adm HiPath
logical TFTP er- AllServe
ror in HiPath
3000/5000
1010 X Socket er- General socket Save event Shut down and re- adm HiPath
ror error file for er- start server. AllServe
ror analy- If error is still
sis present, restart the
PC.
1011 X Udp/tftp: Logical socket Save event Unrecoverable er- adm HiPath
unknown error, unable to file for error. AllServe
service install Winsock ror analy- Restart server and
Library sis report error to ap-
propriate service
support.
1013 X WSA sock- General socket Save event Unrecoverable er- adm/ HiPath
et error error file for error. car AllServe
ror analy- Restart server and
sis report error to ap-
propriate service
support.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
1014 X File open Logical TFTP Wait 5 minutes then adm HiPath
error error; HiPath repeat action. AllServe
3000/5000 dis-
plays a mes-
sage indicating
that frame page
cannot be
opened
1015 X Error while Server problem: Save event Shut down and re- adm HiPath
setsockopt. IP socket could file for er- start server. AllServe
not be initialized ror analy- If error is still
sis present, restart the
PC.
1016 X Error while HiPath 3000/ Save event Connection error, adm HiPath
recvfrom. 5000 no longer file for er- HiPath 3000/5000 AllServe
replies when ror analy- HIP problems.
files are re- sis Check if ping is
ceived working:
If ping is working:
wait 5 mins and re-
start server.
If ping is not work-
ing properly, check
if the “Ping unsuc-
cessful” error mes-
sage appears in the
Event Viewer.
1017 X Error while Logical error Save event Unrecoverable er- adm HiPath
sending to when sending file for error. AllServe
<IP-Adr> data to HiPath ror analy- Restart server and
3000/5000 sis report error to ap-
propriate service
support.
1018 X Transfer No acknowl- Save event Possible connec- adm HiPath
timed out edgement re- file for er- tion interruption or AllServe
ceived/sent ror analy- HiPath 3000/5000
sis HIP problems.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

fault gory
trap
1019 X Discarded TFTP protocol Save event Unrecoverable er- adm HiPath
packets error: data file for error. AllServe
transfer no ror analy- Check if ping is
longer possi- sis working:
ble, transfer If ping is working:
cancelled. wait 5 mins and re-
start server.
If ping is not work-
ing properly, check
if the “Ping unsuc-
cessful” error mes-
sage appears in the
Event Viewer.
1020 Receive CDB page Information adm HiPath
successful frame success- AllServe
ful (read)
1021 Send suc- CDB page Information fct/ HiPath
cessful frame success- adm AllServe
ful (write); Event
Properties con-
tains the corre-
sponding page
frame ID
1022 Connect Positive ack. Information fct/ HiPath
successful from FCT; con- adm AllServe
nection with Hi-
Path 3000/5000
successful;
Event Proper-
ties contains the
corresponding
HIP address
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
1023 X Socket not Connection dif- Save event Check LAN, initiate fct HiPath
connected ficulties - HiPath file for er- HiPath 3000/5000 AllServe
3000/5000 ror analy- ping.
server. TCP sis Restart server if
connection not necessary. Check
available HiPath 3000/5000
HIP.
1024 CDB trans- All frame pages Information vsrv HiPath
fer suc- successfully AllServe
cessful read from Hi-
(read) Path 3000/5000
nodes by the
server
1025 CDB trans- All frame pages Information vsrv HiPath
fer suc- successfully AllServe
cessful written from the
(write) server to all Hi-
Path 3000/5000
nodes
1027 CallAd- Successful Information car HiPath
dressTable transfer of call AllServe
and No- address table
deIpTable and node IP ta-
transfer ble to the sys-
successful tem by the serv-
er
1028 X Venus da- Venus database Information vsrv HiPath
tabase closed AllServe
closed
1029 X Venus Da- Venus database Information vsrv HiPath
tabase started AllServe
started
1030 Data saved Saving the Ve- Information vsrv HiPath
to disk nus database to AllServe
the server hard
drive
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

fault gory
trap
1031 Ping not HiPath 3000/ Save event Check HiPath adm/ HiPath
possible 5000 HIP no file for er- 3000/5000. Check fct/ AllServe
longer available ror analy- HG 1500. Check vsrv/
sis LAN. Initiate HiPath sync
3000/5000 ping, if
necessary
1032 X CDB trans- Writing data to Save event Check HiPath vsrv HiPath
fer to (<IP- HiPath 3000/ file for er- 3000/5000. Check AllServe
Adr>) failed 5000 with speci- ror analy- HG 1500. Check
(write) fied IP address sis LAN. Initiate HiPath
failed 3000/5000 ping, if
necessary.
Load HiPath 3000/
5000 Manager E
data to the server
again. This initiates
data transfer from
the server to HiPath
3000/5000.
1033 Data sync Modification to adm HiPath
tile database in Hi- AllServe
Path 3000/5000
reported to the
server; HiPath
3000/5000 data
loaded and
saved on the
server
1034 Disconnec- sync
tion of ob-
ject recov-
ered (%1)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
1036 X CDB trans- Data reading Save event Check HiPath vsrv HiPath
fer from from HiPath file for er- 3000/5000. Check AllServe
(<IP-Adr>) 3000/5000 (with ror analy- HG 1500. Check
failed specified IP ad- sis LAN. Initiate HiPath
(read) dress in the 3000/5000 ping, if
server) failed necessary.
Activate HiPath
3000/5000 data
loading via HiPath
3000/5000 Manag-
er E.
1037 Interface If 0xzzzzzzz = Save event If an error message reg HiPath
error (_hr= 0x80070057, file for er- appears, RgTrace- AllServe
0xzzzzzzzz this is just inter- ror analy- File.txt and Carlog
z) nal information sis File must be saved.
for Develop-
ment, otherwise
error
1038 User inter- The user inter- Information sync HiPath
face active face is active AllServe
on <IP- during a sync.
Adr> Trials are not
cancelled and
are cyclically re-
peated until
successful.
1039 User: HiPath 3000/ Information vsr- HiPath
“<user- 5000 Manager vad- AllServe
name>” on E information min
PC: about user ac-
“<pc_name tions, user
>”: read reads data from
CDB data the server.
from server
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

fault gory
trap
1039 User: HiPath 3000/ Information vsr- HiPath
“<user- 5000 Manager vad- AllServe
name>” on E information min
PC: about user ac-
“<pc_name tions, user
>”: write writes data to
CDB data the server and
to server. to the systems.
Mode (del-
ta)
1040 Node IP Error HiPath
ADD <IP- AllServe
Adr>
1041 No re- API cannot fct HiPath
sources in open FCT, as AllServe
system %1 there is another
API session ac-
tive (e.g. user
interface).
1042 Regs mes- vsrv HiPath
sage <IP- AllServe
Adr>
1043 Car update Database gen- Information vsrv HiPath
node IP ta- erates the node AllServe
ble entry IP table per
<IP-Adr> CDB for the car
server
1045 X Feature The “Feature Information vd- HiPath
Server: Server” service bast AllServe
Service was started.
Started.
Version
HVxxxB.yy.
nnn.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
1045 X Feature The “Feature Information vd- HiPath
Server: Server” service bast AllServe
Service was stopped.
stopped.
1046 Update CAR assigned a Information car HiPath
CallAd- new call ad- AllServe
dressTable dress and node
(No. = %1) IP table by the
and No- database (event
deIpTable 1027 follows).
(No. = %2)
1047 Registra- The REG server Information reg HiPath
tion re- received a reg- AllServe
quest from istration request
<IP-Adr> from HG 1500.
10000 Wrong re- Wrong UDP Check LAN fct HiPath
quest ID packet se- AllServe
quence, asyn-
chronism.
10001 Unknown Unknown Hi- Information fct HiPath
packet Path 3000/5000 AllServe
IP packet.
10002 X Socket re- TCP socket er- Save event Possible interrupt- fct HiPath
ceive ror. file for ered connection. AllServe
ror analy-
sis
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

fault gory
trap
515 X Error 0x%x Error when sav- GetAc-
in Func ing an outgoing count
\“SaveG- call data record.
eb\”.
Descrip-
tion:
%s”,e.Er-
ror(),
(char*)(e.D
escrip-
tion())
in Func ing an incoming count
\xd2 data record.
SaveKom-
mend\”.
Descrip-
tion:
%s”,e.Er-
ror(),
(char*)(e.D
escrip-
tion())
in Func ing a recalculat- count
\“Save- ed call data
New- record.
Price\”.
Descrip-
tion:
%s”,e.Er-
ror(),
(char*)(e.D
escrip-
tion())
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
515 X Error init Error when GetAc-
HKLM reg- reading start pa- count
istry Stop rameters from
service the HK local
GetAc- machine regis-
count try.
515 X Error init Error when GetAc-
registry reading start pa- count
HKCU Stop rameters from
service the HK Current
GetAc- user registry.
count
515 X Error when Error when GetAc-
starting im- starting immedi- count
mediate ate printout
printout. thread.
Stop ser-
vice GetAc-
count
in Func ing a record for count
\“InsertSo- immediate print-
fortDruck\”. out.
Descrip-
tion:
%s”,e.Er-
ror(),
(char*)(e.D
escrip-
tion())
515 X No CDR TSP does not GetAc-
line found provide any count
CDR lines.
515 X Error TAPI Error when ini- GetAc-
Init tializing the count
TAPI interface.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

fault gory
trap
515 X TapiFunc: Error when call- GetAc-
%s ID: %d ing a TAPI func- count
Error: %s”, tion for a partic-
szTapi- ular line.
Func, lLi-
neID, szEr-
rorMess
515 X TapiFunc: Error when call- GetAc-
%s Error: ing a TAPI func- count
%s”, sz- tion.
TapiFunc,
szEr-
rorMess
515 X Box not Node data has GetAc-
found in not yet been count
database read.
cntBox = 0
SwitchID:
%d, nVNo-
deID: %d
515 X CDR Ser- The CDR ser- GetAc-
vice in vice in the count
PBX: %d switch could not
could not be started.
be started
515 X Error send- Error when GetAc-
ing com- sending the count
mand start CDR ser-
'starting vice command.
CDR Ser-
vice' to
PBX: %d
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
514 X CDR Ser- TSP has al- GetAc-
vice in ready started count
PBX: %d the CDR ser-
by TSP al- vice.
ready start-
ed
515 X Error start- Undefined error GetAc-
ing CDR when starting count
service on the CDR ser-
PBX: %d vice.
dwParam2:
0x%x
515 X Error send- Error when GetAc-
ing com- sending the count
mand 'stop command to
CDR Ser- stop the CDR
vice’ service.
515 X Error stop- Error when GetAc-
ping CDR stopping the count
Service: Il- CDR service.
legal Ac- Access denied.
cess Someone else
already started
the service.
515 X Error stop- Undefined error GetAc-
ping CDR when stopping count
Service: the CDR ser-
ErrorCode: vice.
0x%x”,
dwParam2
513 X TAPI Reinit TAPI was reini- GetAc-
tialized. count
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Guided Maintenance

fault gory
trap
515 X Start ser- Error when PCM
vice error: opening the da-
Database tabase connec-
connect er- tion.
ror
515 X Start ser- Error when PCM
vice error: reading out the
Misc. data- values saved in
base error the database.
515 X LineInitial- Error during PCM
ize: %s”, TAPI LineDevic-
TapiEr- es initialization.
rorMess
515 X PhoneIni- Error during PCM
tialize: %s”, TAPI PhoneDe-
TapiEr- vices initializa-
rorMess tion.
515 X PCM Ser- General error PCM
vice Start when starting
error: the service.
[dynamic
error mes-
sage]
515 X The PCM- Error creating PCM
Conn.clsP object when
CMConn starting the ser-
connection vice.
object
could not
be estab-
lished.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Guided Maintenance

fault gory
trap
515 X The PCM Service cancel- PCM
service lation due to an
was can- unrecoverable
celled be- error during ini-
cause of tialization.
unrecover-
able error
during ini-
tialization.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Correcting Errors
12.4 Correcting Errors
12.4.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 has
to correct the error manually.
12.4.2 Manual Error Correction Without HiPath 3000/5000 Manager E
Manually activating a restart (reset)/reload

Pressing the reset button on the central control board of HiPath 3000
● initiates a Reset (hard restart of the entire system with the current CDB) if the button is
pressed 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 disap-
pears after approximately five seconds as verification that the reload has been initiated.
The entire content of the customer database is replaced by its default version. All country
and customer-specific settings are lost.
If you initiated a system reload, the system must be reset after the CDB has been
> installed. This ensures that all signaling gateways (= HG 1500 gatekeeper) are re-
set.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Correcting Errors

You can lock out and release ports using the lockout switch located on the board. The lockout
prevents 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.
12.4.3 Manual Error Correction With HiPath 3000/5000 Manager E
Initiating Restart (Reset)

This initiates an immediate hard restart of the entire system with the current CDB.
Initiating Reload Card

This the single board (loading Loadware) to reload.

HiPath 3000/5000 Manager E enables you to lock out an entire subscriber line module or line
circuit module and individual ports. The lockout prevents renewed seizure after the current con-
nection has finished. Release or lockout settings are also retained after a reset.
However, you cannot lock out the first SLMO/SLU board because administration through Man-
ager T runs on its first two ports.
When attempting to lock out the last active trunk, you are subsequently notified that remote ser-
vice through the service center is no longer possible.
You cannot use HiPath 3000/5000 Manager E to release boards and ports locked out with the
lockout switch.
ALUM
You cannot initiate a power failure transfer to analog telephones using HiPath 3000/5000 Man-
ager E.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Remote Service
12.5 Remote Service
Definition
Remote service is described as communication between the service center and HiPath 3000
and HiPath 5000 using the public telecommunications network 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.
The connection to HiPath 3000 can be set up via the integrated digital modem (B channel), the
integrated analog modem (IMODN) or the HG 1500.
Special software programs, such as pcANYWHERE, facilitate connections to HiPath 5000. If
the customer agrees, Remote Access Service RAS can also be used, provided this service is
active on the HiPath 5000 server.
HiPath 3000
PSTN
(analog or
digital
Central Board telecommunica-
tions network) Service Center
Modem Service PC
with
LIM HiPath 3000/5000
Manager E
Client
LAN
Plus Products
Figure 12-6 Example of Remote Service with HiPath 3000
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Remote Service
12.5.1 HiPath 3000 Connection Options

● HG 1500
All systems can be accessed remotely with a LAN-LAN link via the HGHiPath 30001500
board. For information on configuration, refer to the HG1500 Administration Manual.
● Integrated analog modem IMODN
This modem enables remote access to all systems in the HiPath 3000 product line. Access
is achieved using any trunks, tie trunks, and all subscriber lines. IMODN is designed as a
plug-in card.
Caution
7 Be sure to disconnect the system from the power supply before removing or in-
serting integrated analog modems (IMODN).
The IMODN is treated as a pseudo port. It receives a number in the system that can be
reached internally through direct internal dialing (DID). You can cancel the DID number
manually to prevent external access.
● Integrated digital modem (B Channel)
An integrated B channel modem is available with all systems in the HiPath 3000 product
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 can
be reached internally and through direct internal dialing. You can cancel the DID number
manually to prevent external access.
Baud rate settings
For information about setting the baud rate for different connection types between HiPath 3000
and HiPath 3000/5000 Manager E, consult the Help for HiPath 3000/5000 Manager E.
Access to the analog/digital modem
The customer must enable the access to both modems by entering a six-digit PIN code. If the
service center is to make a connection to the HiPath 3000 over a modem, it may be necessary
to enter this individual code. It depends on which trunk type is used for the modem access. 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 back
to the default value.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Remote Service
12.5.2 HiPath 5000 Connection Options

In general, the connection to HiPath 5000 is established via special software programs, such
as 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 service
is active on the HiPath 5000 server. Information on configuring the Remote Access Service
(RAS) can be obtained from the HG 1500 Administration Manual.
12.5.3 Remote System Administration
12.5.3.1 Remote Administration of HiPath 3000 with

HiPath 3000/5000 Manager E
To establish a remote connection between HiPath 3000 and the service center (HiPath 3000/
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 can manage up to six different callback indices (callback passwords and their rel-
evant callback numbers), in which case the first callback connection is also the destination of
the automatic error signaling. For each callback connection, you can select either the digital
modem (B channel) or the analog modem (IMODN).
If you have chosen your settings and selected the connection setup option “Callback activated”,
the HiPath 3000/5000 Manager E can dial in to the system. HiPath 3000 registers the callback
destination and saves the callback index. After 10 s, the HiPath 3000 initiates the actual call-
back with the number which is linked using the callback index. As soon as the connection is
established, you can use HiPath 3000/5000 Manager E to manage the system.
If no connection is established, HiPath 3000 will make a total of 20 attempts in intervals of 10 s
after which the callback attempt ends and has to be started up again with HiPath 3000/5000
Manager E.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Remote Service
Service call via code

You can use any telephone to initiate a HiPath 3000 service call to the service center by select-
ing the connection setup option “Service call via code” and activating the feature “Remote ac-
cess immediately after installation”. In contrast to the usual callback procedure, this callback
(service call) is not activated by HiPath 3000/5000 Manager E itself, but by any telephone you
choose. Callback initialization is skipped.
The service call destinations are the six callback indices that also apply to callback. You are not
required to enter the relevant passwords.
The service center wait time for one service call is limited to 15 minutes, though you can end it
manually at any time.
Procedure: Activate the feature “Remote access immediately after installation”.

1. *994 Enter code for “Remote access immediately after installation”
2. X Select callback index (0 ... 6 possible)
3. XXXXXXX Select a suffix number if necessary (up to 11 digits)
The suffix is used for selecting the remote PC in the service
center.
4. or # Press “OK” or the “#” button.
Automatic error signaling

Class B errors can be automatically transferred to a service center. For more information on
this, see Section 12.5.5.
12.5.3.2 DTMF Remote Administration of HiPath 3000

This feature facilitates remote system administration by transmitting DTMF signals. The user
interface (menu prompt) is the same as that of the Manager T for system administration on site.
DTMF remote administration can be performed using either analog or digital trunks.
12.5.4 Remote Correction of System Software (APS)

The service center performs the APS transfer (see Section 12.2.3).
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Remote Service
12.5.5 Remote Error Signaling

Class B errors can be automatically transferred to a service center. For this, the “Error-Signal-
ing” flag must be activated and a number entered under the callback index 1.
To register an error message, the HiPath 3000/5000 Manager E that is dialed at the service
center must be in Receive mode. If an error message is received, the HiPath 3000/5000 Man-
ager E automatically creates a file in which the error is entered. If another error occurs, it is en-
tered in the same file behind the previous entry.
The error report consists of one header and the error information that is transmitted in binary
form. The header contains a unique identifier that recognizes the customer system that sent
the error reports.
Caution
7 In case of a power outage, the not battery-buffered SDRAM content of the MMC is
completely lost. Any individual settings made for the time parameter “error signaling
interval” are also reset to the default value 15 minutes.
When the system is restarted, the automatic recovery action “reload CDB backup”
starts and the customer-individual settings are reloaded. Because this process lasts
longer than 15 minutes, the first error message is always signaled at the end of the
15-minutes default interval. All other errors are then signaled again with the individ-
ually set interval.
Example: The error signaling interval of a HiPath 3550 with activated error signaling
was set to 90 s. After a power outage, the 90 s interval reverts to the default value
of 15 minutes. The first error message “no voltage” is signaled 15 minutes after re-
starting operation of the system. After conclusion of the recovery action “reload CDB
backup”, the original 90 s setting of the error signaling interval is reactivated. All oth-
er errors are signaled after 90 s.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Remote Service
12.5.6 Controlled Release of a Remote Connection

With version 1.2 and later, you can initiate the controlled release of a remote connection (with
analog or digital modem) between the HiPath 3000 and HiPath 3000/5000 Manager E as fol-
lows:
● Disconnect according to action (Default setting)
After completing an action (e.g. CDB backup or APS transfer), the remote connection is
automatically disconnected.
● Disconnect according to release time
After completing an action (CDB backup or APS transfer, for example) and the adjustable
release time sequence (60 ... 9999 s), the remote connection is disconnected.
● “Hang up” button
By pressing this button, you can disconnect the remote connection manually.
Use HiPath 3000/5000 Manager E to select any one of these options.
12.5.7 Remote Administration and Access Using PPP

You can establish a connection between the system/Plus product and the service center using
either the integrated digital modem (B channel) or the integrated analog modem (IMODN). Data
is exchanged in both cases using Point-to-Point-Protocols (PPP).
For further information see “Features via LAN” in the HiPath 3000/5000 Feature Description.
12.5.7.1 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 further information, see “Remote Administration of HiPath 3000 via PPP” in the HiPath
3000/5000 Feature Description.
12.5.7.2 Remote Administration of Plus Products

You can manage Plus products from a central location using HiPath 3000. However, HiPath
3000 only provides the means of transmission. The Plus product is actually administered using
special software programs like pcANYWHERE.
For further information, see “Remote Administration of Plus Products via PPP” in the HiPath
3000/5000 Feature Description.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Remote Service
12.5.7.3 Remote Error Signaling Using SNMP

Plus products and the HiPath 3000 can transmit error messages (SNMP traps) to the service
center.
For further information, see “SNMP Functionality” in the HiPath 3000/5000 Feature Descrip-
tion.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features
12.6 Security Features
12.6.1 Access Security
12.6.1.1 User-Specific Logon for WBM

To ensure that authorized users have access to the E-Doku and to prevent unauthorized ac-
cess, users must be identified by a user name and authorized by a password. This applies to
all local and remote administration and maintenance procedures using Web-Based Manage-
ment (WBM).
The user group determines which data is administered. The following two user groups are per-
manently defined for administration via WBM:
● Customer
● Administrator
Each user group is assigned a fixed user name and password. You need a valid user name and
password to access a user group. Only the data authorized for the relevant user group can be
read and administrated.
The following table provides a breakdown of the two user groups and their rights for each of the
setup wizards.
Table 12-9 WBM User Groups with Associated Rights
Wizard Customer Administrator

Initial Installation X
(for basic system setup)
New Components:
(for configuring new components)
● LAN telephones (for configuring additional IP work- X
points)
● WLAN telephones (for configuring additional WLAN X
workpoints)
● Analog telephones (for configuring additional analog X
workpoints - group 3 fax devices, for example)
● Not for U.S.: S0 interfaces (for configuring additional X
ISDN connections and ISDN workpoints)
● Licensing (for licensing system expansions) X
Change Feature:
(for modifying current system setup data)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features

● LAN/WLAN telephones (for modifying configured work- X
points)
● Analog telephones (for modifying configured analog X
workpoints)
● Not for U.S.: S0 interfaces (for modifying configured X
ISDN connections and ISDN workpoints)
● For U.S. only: T1 board (for configuring and modifying X
the T1 board operating mode)
● Trunk seizure (for modifying the code and prioritization X
for trunk seizure)
● Answer machine (for configuring and modifying the inte- X
grated voice mailboxes)
● Call forwarding no answer/call pickup (for configuring X X
and modifying call forwarding destinations and call pick-
up for incoming calls)
● Call groups (for configuring and modifying call groups X X
(incoming calls are signaled to all members of a call
group))
● Key programming (for configuring and modifying key X X
programming on the workpoints)
● Internal phonebook (for configuring and modifying en- X X
tries in the central phonebook)
● DHCP (for modifying to the DHCP server) X
● Firewall (for configuring and modifying the integrated In- X
ternet firewall)
● DSL (for modifying Internet access) X
● Internet telephony (for configuring and modifying Inter- X
net telephony access)
● VPN (for configuring and modifying virtual private net- X
works)
● Online help (for configuring and modifying the installa- X
tion directories in the online help)
Remote Access X
(for activating and deactivating remote access for remote
system administration)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features

Software Update X
(for checking if software updates are required)
Status:
(for querying the current system status)
● Network interfaces (for querying the current status of X X
network interfaces)
● Dial-up networking (PSTN) (for querying information X X
about existing dial-up connections (PSTN partners))
● Stations (for querying the data of all configured stations) X X
● Events (for querying the last 50 events (trace messag- X X
es))
Expert Mode X
(for configuring and modifying advanced features, such as,
the networking of several E-Doku systems)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features
12.6.1.2 Password Protection against Brute Force Attacks

Brute force attacks are attempts made by a computer program to crack the password of another
program or tool, by trying all possible combinations of letters and numbers.
To protect against unauthorized access, remote access logon to WBM is monitored. Users are
permitted five attempts over five minutes to enter the correct password. If this time expires or
the password is entered incorrectly five times, remote access is blocked.
The system’s event log records the password input attempts.
12.6.1.3 Logon With User Name and Password
Security
To ensure that authorized users have access to the HiPath 3000 and to prevent unauthorized
access, users must be identified by a user name and authorized by a password. This applies
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
Example of first-time login with Manager T

Alphanumeric characters cannot be entered at all workpoints. Therefore, when

> changing the user name or password with Manager T/Assistant TC, you may enter
additional characters as long as you never use an appropriate workpoint.
Alphanumeric characters can only be entered at the following workpoints: Open-
Stage 40, Optiset E memory, optiPoint 600 office (in UP0/E mode), optiPoint 410 ad-
vance, and optiPoint 420 advance. Entry is also possible via the optiPoint applica-
tion module (in connection with optiPoint 500 basic/standard/comfort).

4. XXXXX You are prompted to enter a new password (max.
15 digits)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features

5. XXXXX You are prompted to confirm the password entered in step
4.
6. 29 - 5 Country initialization
2 = Fixed password
8. XX You are prompted to enter the country code (see page A-
26). The system then boots up with the country-specific
default information.
Notes:
the system again.
the new password entered under step 4.
Variable password concept

Up to 16 users can be assigned their own user ID with individual name, password, and a user
group consisting of six pre-determined user groups (in Table 12-10). Only the data authorized
for the relevant user group can be read and administrated.
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 or optiset E character set). This then overwrites the
default user name (31994) and default password (31994). This first user is then automatically
assigned to the user group “System Maintenance”. The system informs the user that no user
is configured in 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 can be configured in the user administration.
If a user forgets a password, it has to be deleted and re-configured by a different authorized
user. If all authorized users forget their passwords, the system must be regenerated.
Fixed password concept

When using a 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-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features
Changing password types

Only with Manager T can you change from a variable password to a fixed password type and
vice versa. To do this, you have to re-initialize the country settings. This switches the entire con-
tent 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 created
user 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 system that was changed to a fixed password
type. Before reading this CDB, you have to set up a user (user name and password) in the sys-
tem 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. With this user name and ID, you can now load the CDB into
the system switched to the fixed password type.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features
12.6.1.4 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 12-10 Variable password concept: Pre-Determined User Groups and Their Access
Rights
No. User groups
Customer admin.
System maint.
accounting
Develop-
(Service)
Charge
admin.
(Cust.)
Audit
ment
User
User rights
1. ● Setting up/deleting users X X1

● Assigning users to user groups
2. ● Assessing and archiving backup-related log X X2
files
● Reader rights to system data (error memory,
for example), not including confidential cus-
tomer information
3. ● Access rights to all system data (not including X
development access rights) as long as no us-
ers are assigned to other user groups.
4. ● Access rights to confidential customer infor- X3 X
mation
● Executing customer actions (printing out cer-
tain lists, for example)
5. ● Access rights to non-confidential customer X X
information
6. ● Access rights to parameters and call detail re- X3, 4 X4 X
cording actions (not including interface pa-
rameters for the output device)
7. ● Access rights of the “System Maintenance” X
user group
● Setting up and reading certain parameters to
which no other user group has access.
1 As long as no user is assigned to the “User Administration” user group.
2 As long as no user is assigned to the “Audit” user group.
3 As long as no user is assigned to the “Customer administration” user group.
4 As long as no user is assigned to the “Accounting” user group.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features
User groups with a fixed password

The following table shows fixed (unchangeable) user groups and their rights.
Table 12-11 Fixed Password: Fixed User Groups and Their Access Rights
No. User groups
– Manager TC=*95/(Password
– Manager C=office/office
Customer admin. (Cust.)
System maint. (Service)
Name/Password=
Name/Password:
not necessary)
Development
31994/31994
User rights
1. ● Assessing and archiving backup-related log files X X
● Reader rights to system data (error memory, for exam-
ple), not including confidential customer information
2. ● Access rights to all system data (not including develop- X X
ment access rights)
3. ● Access rights to confidential customer information X X X
● Executing customer actions (printing out certain lists,
for example)
4. ● Access rights to non-confidential customer information X X X
5. ● Access rights to parameters and call detail recording X
actions (not including interface parameters for the out-
put device)
6. ● Setting up and reading certain parameters to which no X
other user group has access.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features
12.6.1.5 System Access Options

The user’s access rights, meaning the data that the user may read or manage, always depend
on the user group to which the user is assigned.
Service tools
● Manager T and Assistant TC systems
Log on by entering your user name and password (regardless of code lock)
The system can only be accessed using the first two UP0/E connections from the first
SLMO/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 connection
The system can be accessed directly using the integrated digital modem (B channel) or the
integrated analog modem. However, the user is required to establish a 5 digit access code
beforehand.
● HiPath 3000/5000 Manager E (remote), callback connection
The 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 Software Manager
AMHOST
The AMHOST (Administration and Maintenance via HOST) feature allows Plus products to
read 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 default user
administration. Enter “AMHOST” as the user name and “77777” as the default user password.
You can only change this password if the system is configured using a variable password. In
this case, delete the “AMHOST” user and re-configure the system with the same user name
and a new password.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features
12.6.1.6 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 and
password. The data that you enter is compared to the data in the user table. In this case, the
user group verified during this process also determines the access rights.
When loading an offline customer database into HiPath 3000, the user table that goes with it
should not be loaded into the system. Otherwise, the system-specific user administration would
be distorted.
When you generate a default customer database offline, a default user table is also
> set up. If you generate a customer database like this, you can only load it into a de-
fault system.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features
12.6.2 Automatic Logging of Administration Procedures
Definition
All accesses to customer-related data in the HiPath 3000 are automatically logged in an area
of the MMC (LOG area) reserved for this purpose. The information recorded includes who the
user is, the data manipulated by the user, and the time. An authorized user (member of the “Re-
vision” user group) can transfer the system data to a PC and assess it.
12.6.2.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)
12.6.2.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 most
important 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 of whether it is logged using Manager T, HiPath
3000/5000 Manager E, or other systems. Possible command entries are:
A0-1 = Login procedure
A0-2 = Logout procedure
A0-3 = Unauthorized login attempt
● HiPath 3000/5000 Manager E Database (4)
Access to the database is logged using HiPath 3000/5000 Manager E. Possible command
entries are:
A1-1 = Database read
A1-2 = Regeneration of CDB (Load CDB into the system)
A1-3 = Write database
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features
● 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 are
logged:
– 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 activation
C2 = Pseudo area “System timer”
– C2-1 System timer
C3 = Pseudo area “S0 configuration”
– C3-1 Station bus
– C3-2 Line supervision
– C3-3 Mode
C4 = Pseudo area “Lines”
– C4-1 Loop start parameter (Variable Slot/Line#)
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features
C5 = Pseudo area “Digit analysis”

– C5-1 Internal number (Variable Stn#, Grp#)
– C5-2 Service codes
C6 = Pseudo area “Daylight saving time”
– C6-1 Daylight saving time
C7 = Pseudo area “Routes”
– C7-1 Routing flags (Variable Trk Grp#)
C8 = Pseudo area “Door setup”
– C8-1 Door setup (Variable door#)
C9 = Pseudo area “UCD flags”
– C9-1 UCD flags
C10 = Pseudo 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 these
changes “automatically” run simultaneously (Check In and Check Out for hotel solu-
tions, for example), these are not logged. Only the session information (user name
is “amhost”) with the command entries “Login procedure” and “Logout procedure”
are logged.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm
Security Features
12.6.2.2 Issuing and Saving Log Data

Data is automatically logged in an area (LOG area) on the MMC reserved for this purpose (Hi-
Path 3000) or in a special directory (HiPath 5000). It cannot 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 “Revisor
Alarm.”
The log should now be read out and archived, meaning it should be saved in an archive file (file
extension = arc). If an archive is not created, the oldest datablock is overwritten if there is a
danger of overflow.
You can only issue log entries using HiPath 3000/5000 Manager E. You cannot retrieve the log
entries 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 must
match the current customer. In case of a positive result, the system log entries are retrieved
and attached to the existing data in the archive file. At the same time, the data in the system is
deleted.
If malfunctions occur during this procedure (for example, line interruption), the entire procedure
ends 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.
You do not have to log on to the system to use the HiPath 3000/5000 Manager E to check ar-
chive files on the PC monitor. In this case, a password is not required.
Multimedia card
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.
A31003-H3570-S100-6-7620, 2008-04-01
service.fm

Security Features
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.
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
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 system
database, changed 20 station names, and rewritten them to the system.
● The Customer (“pnkm” user in “A” (Administration) user group) has changed two additional
station names.
● The Revisor has retrieved the most recent log entries and printed them out.
A31003-H3570-S100-6-7620, 2008-04-01
ip_.fm
Nur für den internen Gebrauch IP Fundamentals
Overview
13 IP Fundamentals
13.1 Overview
Chapter contents
Topic
IP Network Requirements, page 13-2
● General Introduction, page 13-2
● H.323 Protocol, page 13-2
● Standards Supported, page 13-3
● QoS - Quality of Service, page 13-4
Network analysis, page 13-6
This section provides introductory information only and does not replace IP training.
>
A31003-H3570-S100-6-7620, 2008-04-01
ip_.fm
IP Fundamentals Nur für den internen Gebrauch

IP Network Requirements
13.2 IP Network Requirements
For special requirements regarding bandwidth, delay, QoS, etc. for a HiPath 3000/
> 5000 Version 3.0 customer IP network, please refer to the requirement specifica-
tions in the HiPath 3000/5000 solution contract.
13.2.1 General Introduction

A number of protocols play a role in data communication (X.25, Frame Relay, ATM and TCP/
IP). The IP (Internet Protocol) switching layer is the Internet’s key protocol and permits interop-
erability with other networks and protocols, for example, Ethernet, X.25, Frame Relay and ATM.
IP is consequently often used as a synonym for the technology as a whole. The protocols TCP,
UDP and RTP are used by the various applications and requirements in the Internet, such as
“File Transfer (FTP)”, “e-mail (SMTP)” and “WWW”.
RTP (Real Time Protocol) is used for voice transmission. The term “Voice over IP (VoIP)” indi-
cates that the IP protocol is used to transport voice information.
There are nowadays various protocols that result from the efforts of diverse standardization
bodies and standardization drives.
13.2.2 H.323 Protocol

H.323 encompasses the following subjects:
● Signaling (H.245, etc.)
● Video transmission
● Voice transmission/voice compression, for example
– G.723.1 (5.3/6.3 Kbps)
– G.729A (8 Kbps)
● Data applications (Application Sharing, T.120)
It is clear that this standard offers much more than just what is needed for voice transmission
via data networks. H.323 was developed for multimedia applications.
A31003-H3570-S100-6-7620, 2008-04-01
ip_.fm
13.2.3 Standards Supported

HiPath 3000/5000 Version 3.0 supports the standards listed in the following table.
Table 13-1 Standards Supported
Standard Transmission Notes

rate1
G.711 ITU standard for voice 64 Kbps ISDN voice quality
codecs
G.722 High-quality voice co- 48, 56 or Better voice quality than G.711
dec 64 Kbps
G.723.1 ITU standard for voice 5.3 or 6.3 Kbps Adequate voice quality
codecs
G.729 Group of ITU stan- 8 Kbps Less delay and better voice quality than
dards for voice codecs G.723.1
G.729A ITU standard for voice 8 Kbps Less delay and better voice quality than
codecs, based on G.723.1
G.729
G.729AB ITU standard for voice 8 Kbps Less delay and better voice quality than
codecs, based on G.723.1
G.729A
T.38 ITU standard for fax 14 Kbps Governs communication from group 3
transmission (Realtime fax devices over IP networks
FAX)
1 The bandwidth actually required in the LAN, for example, may be considerably higher. Here are some relevant factors:
– Data Link Layer used: Ethernet (with or without VLAN), PPP, Frame Relay ...
– Protocols with/without compression: RTP, UDP, IP
– Security: VPN tunnel ...
– Redundancy: For example T.38
– Packaging: the number of samples that are transported per package.
“Clear Channel” transmission mode is characterized by the fact that signals are transmitted dig-
itally and the connection is bit-transparent. There is no compression. The transmission rate is
64 Kbps.
A31003-H3570-S100-6-7620, 2008-04-01
ip_.fm

13.2.4 QoS - Quality of Service
Introduction
Data transmission in IP networks can encounter:
● Time problems due to large e-mail attachments and web surfing
● Network bottlenecks as a result of multiple requests for the same web page
● Reduced voice quality due to:
– Delay (decline in voice quality due to delay)
– Variable delays (decline in voice quality due to jitter)
– Packet loss (decline in voice quality due to packet loss)
Quality of Service includes various methods which guarantee certain transmission properties
in packet-orientated 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. When several equal-access applications are operating via
IP, the available transmission link bandwidth (for example, an ISDN B channel, 64K bps) is
shared between these applications. Consequently, packet loss may occur during a voice con-
nection, causing poor voice quality.
HiPath 3000/5000 QoS

In HiPath 3000/5000 networks, different types of traffic are transported via a single IP infra-
structure. It is the aim of Quality of Service to fulfill the data traffic and voice traffic requirements.
To prevent voice traffic from being suppressed by data traffic, the former must be given high
priority. In addition, it must be specified that high-priority traffic is transmitted before traffic with
lower priority. This is specified on layers 2 and 3:
● The three bits in the 802.1p field, which is part of the 802.1Q tag, are used on layer 2.
● On layer 3, the six bits in the DiffServ Code Point (DSCP) field are used in the IP headers’
Type of Service (ToS) byte.
It is also essential that sufficient bandwidth is available within the QoS class in use (Codepoint/
IEEE802.1p User Priority). The following table lists the QoS values used for DiffServ and the
User Priority IEEE802.1p field.
A31003-H3570-S100-6-7620, 2008-04-01
ip_.fm
Table 13-2 Possible QoS Settings
Traffic type DiffServ 802.1p field Traffic class

Code Point (Priority 0 (= lowest) – 7 (=
highest)
Voice payload (RTP/RTCP) AF12 6 Guaranteed service
(001100)
Data payload (fax gateway) AF11 6 Guaranteed service
(001010)
Signaling (H.225, H.245 and AF21 5 Controlled Load
real-time application signaling) (010010)
All other traffic types DE (000000) 0 Best effort
Information on the QoS procedures used for HG 1500 can be found in the HG 1500 Adminis-
tration Manual.
A31003-H3570-S100-6-7620, 2008-04-01
ip_.fm

Network analysis
13.3 Network analysis
Network analysis must be performed before installation of the relevant systems and
> applications to guarantee smooth operation in the customer network.
Network analysis determines the conditions under which the customer’s network is
suitable for HiPath 3000/5000. The result report is an integral component of the re-
quirement specifications in the HiPath 3000/5000 solution contract.
The Network Analysis service module is used to check whether the customer’s communication
network is suitable for business-over-IP solutions from
Siemens Enterprise Communications GmbH & Co. KG (HiPath 3000, HiPath 4000, HiPath
5000 etc.). The assessment is carried out on the basis of parameters preset by the products.
The customer receives a final report in which the network structure and operating parameters
(percentage utilization, delay, jitter) are documented.
Information can be found on the HiPath Network Analysis home page:
https://netinfo.icn.siemens.de/es/products/prod_netzwerk_analyse_v2/product/home_page
Customer benefits and cost-effectiveness

● Preparation of the network for future applications (VoIP)
● Determination of current traffic volume and percentage utilization, baselining
● Decision-making assistance for the introduction of VoIP solutions
Network analysis performance specification

● Examination of the suitability of customer networks for
Siemens Enterprise Communications GmbH & Co. KG Voice-over-IP solutions
● Recording of relevant parameters over a predefined test time
● Assessment on the basis of product specifications
● Interpretation of test results with suggestions of further measures
● Final report with recommendations
Configuration notes
For use when planning Siemens Enterprise Communications GmbH & Co. KG Voice-over-IP
solutions
For use only in SNMP-based IP data networks (routers, IP switches, hubs)
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Nur für den internen Gebrauch System Programming Codes (Expert Mode Codes)
Introduction
A System Programming Codes (Expert Mode Codes)
A.1 Introduction
The workpoints with the two lowest internal station numbers (for example, 11 and 12 or 100 and
101) can be used to administer HiPath 3000 systems.
Programming is conducted in expert mode. This allows you to program features and settings
by inputting defined digit strings.
You must acknowledge error messages. When the system reports an error as a result of enter-
ing a previously used code, a code appears in the second line of the display. You can use this
code to go directly to the desired menu segment.
A.2 Accessing system administration

Users can access system administration by entering a user name (ID) and password (authen-
tication). Depending on the active password concept (refer to Section 12.6.1.3 for more de-
tails), the procedure is as follows:
Table A-1 Starting System Administration (Service)

2. XXXXX Enter user name:
● Fixed password concept: User name = 31994
● Variable password concept: Individual user name
3. XXXXX Enter password:
● Fixed password concept: Password = 31994
● Variable password concept: Individual password
page 12-99 contains an example of initial system administration via Manager T after the system
is booted.
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual A-1
pcodes.fm
System Programming Codes (Expert Mode Codes) Nur für den internen Gebrauch
Accessing system administration
Table A-2 Expert Mode Code Groups
Code Group Function

System maintenance expert mode (previously Manager T)
11 Call detail recording
12 Speed dialing system
13 Account codes
14 Set up station
15 CO call privileges
16 Incoming calls
17 Networking
18 Traffic restriction
19 Displays
20 ISDN parameters
21 Analog CO interface
22 System settings
23 Code
24 Door relay
25 Announcement/Music
26 Relays
27 Sensors (HiPath 3550/HiPath 3350/HiPath 3500/HiPath 3300 only)
28 Edit CDB
29 System details
30 Remote service
31 Call distribution
32 Paging
33 Attendant
34 DISA
35 Least Cost Routing (LCR)
37 Security
51 – 63 Customer administration (previously Assistant TC)
A31003-H3570-S100-6-7620, 2008-04-01
A-2 HiPath 3000/5000 V7, Service Manual
pcodes.fm
Table A-3 Expert Mode Codes
Code Function
11 Call detail recording
11 1 CDR/station (call detail recording at station)
11 1 1 View CDR/station; enter station number
11 1 2 Print CDRS
11 2 CDR per trunk (call detail recording per trunk)
11 2 1 View CDR per trunk; select slot/trunk
11 2 2 Print CDRT
11 3 CDR central (call detail recording central)
11 3 1 Output format: 0 = compressed, 1 = long
11 3 2 Station number format, suppress digits: 0 = no, 1 = yes
11 3 3 Incoming calls: 0 = no, 1 = yes
11 3 4 Call duration 0 = no, 1 = yes
11 3 5 Output MSN: 0 = no, 1 = yes
11 3 6 Call charge display: 1 = Amount, 2 = Pulses
11 3 7 Outgoing without connection: 0 = no, 1 = yes
11 4 Call charge factor
Enter 0 % to 10000 %
11 5 ISDN factor
Enter 0 % to 10000 %
11 6 Currency, alphanumeric entry of max. 3 characters (not for U.S.)
11 7 Call log: 0 = no, 1 = yes
11 8 CDRA (call detail recording, attendant), pay phone, station.
11 9 Computing accuracy, decimal digits (0 to 3)
12 Speed dialing system
12 1 Speed dial numbers, external station numbers
000 to 999 (HiPath 3550/HiPath 3500);
000 to 299 (HiPath 3350, HiPath 3300)
12 2 Speed dial names (alphanumeric entries of up to 16 characters), only if
speed-dialing numbers have been entered1
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
13 Account Code (ACCT)
13 1 Code entries, list 0 to 999
13 2 Checking procedure 0 = Not checked, 1 = Acc. code list, 2 = Number of
digits
13 3 Entry procedure 0 = Optional, 1 = Mandatory
13 4 Code length (1 to 11)
14 Set up station
14 10 Copy station data
14 11 Station type
14 11 0 Standard
14 11 1 Fax
14 11 2 PhoneMail (5 digits)
14 11 3 Loudspeaker
14 11 4 Answer Machine
14 11 5 External MOH
14 11 6 P.O.T MW LED
14 11 7 PhoneMail (6 digits)
14 11 8 Door station with pulsed loop
14 11 9 Memo
14 11 10 Modem
14 12 Station names (alphanumeric), up to 16 character1
14 13 Override: 0 = denied, 1 = allowed
14 14 Associated Dialing: 0 = denied, 1 = allowed
14 15 DISA: 0 = denied, 1 = allowed
14 16 Call waiting rejection: 0 = off, 1 = on
14 17 Headset 0 = off, 1 = on
14 18 Call pickup group:
HiPath 3550/HiPath 3500: Groups 1 to 16, max. 32 stations
HiPath 3350/HiPath 3300: Groups 1 to 8, max. 8 stations
14 19 Reset station PIN: 0 = Reset to 00000
14 20 Override do not disturb 0 = no, 1 = yes
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
14 21 Missed Calls List: 0 = no, 1 = yes
14 22 MCID: 0 = denied, 1 = allowed
14 23 Call FWD, external: 0 = denied, 1 = allowed
14 25 Data compression 0 = no, 1 = yes
14 26 Select language:
11 = German
12 = US English
13 = French
14 = Spanish
15 = English
16 = Italian
17 = Dutch
18 = Portuguese
19 = Finnish
20 = Czech
21 = Danish
22 = Swedish
23 = Norwegian
24 = Turkish
25 = Telekom, German
26 = Polish
27 = Hungarian
28 = Russian
29 = Greek
30 = Slovenian
31 = Serbo-Croatian
32 = Estonian
33 = Latvian
34 = Lithuanian
35 = Chinese
36 = Slovakian
37 = Catalonian
38 = German (2)
39 = English (2)
40 = Romanian
41 = Bulgarian
42 = Macedonian
43 = Serbian (cyr.)
44 = Serbian (lat.)
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
14 27 Do not Disturb: 0 = off, 1 = on
14 28 Telephone lock intercept: 0 = no, 1 = yes
14 29 Dialing method: 1 = DTMF, 2 = DP
14 30 optiPoint BLF (busy lamp field or BLF), Display: No BLF, one BLF, two
BLFs
14 31 Ringback protection per station
14 32 Setup station in internal phonebook: 0 = no, 1 = yes
14 33 Edit tel. number 0 = no, 1 = yes
14 34 Monitoring: 0 = not authorized, 1 = authorized
14 35 Keypad dial: 0 = not authorized, 1 = authorized
14 36 Forwarding CFSS
14 37 Speaker calling
14 38 Bar speaker calling
15 CO call privileges
15 1 Direct trunk access day; specify reference station
Enter new data:
0 = No trunk access except by system speed-dialing
1 = Incoming only
2-7 = Allowed list, Allowed list 1-6
8-13 = Denied list, Denied list 1-6
14 = Full access
15 2 Direct trunk access night; specify reference station
Enter new data:
1 = Incoming only
2-7 = Allowed list, Allowed list 1-6
8-13 = Denied list, Denied list 1-6
14 = Full access
15 3 Allowed lists
15 3 1 Allowed list 1, 100 entries
15 3 2 Allowed 2, 10 entries
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
15 4 Denied lists
15 4 1 Denied list 1, 50 entries
15 4 2 Denied 2, 10 entries
15 5 Number of authorized stations (for verification purposes only)
15 6 Telephone lock
1 = Incoming only
2 - 7 = Allowed lists 1-6 (AL 1 to AL 6)
8 - 13 = Denied lists 1-6 (DL 1 to DL 6)
14 = Full access (full)
15 7 Toll restriction, 0 = Digit-by-digit, 1= En-bloc sending
15 8 Switched trunk authorization
15 9 Toll restriction, private
16 Incoming calls
16 10 Internal station numbers
16 10 1 Station
16 10 1 1 Boards
16 10 1 2 Change station number
16 10 1 3 Find station number
16 10 2 Groups
16 11 DID numbers; (internal) station number is displayed; enter (new) station
number
16 12 Intercept position, day; enter new destination, group or Stn. no., max. 6
digits
16 13 Intercept position, night; enter new destination, group or Stn. no., max. 6
digits
16 14 Intercept criteria
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
16 14 1 on RNA: 0 = no, 1 = yes
16 14 2 on Busy
16 14 2 1 Intercept 0 = no, 1 = yes
16 14 2 2 Call waiting on busy: 0 = no, 1 = yes
16 14 3 on Invalid, intercept: 0 = no, 1 = yes
16 14 4 on Incomplete, intercept: 0 = no, 1 = yes
16 14 5 on Automatic recall, intercept: 0 = no, 1 = yes
16 15 Hunt/group call
16 15 1 Called station no.; select group and assign destination
16 15 2 Ring type; select group and type:
1 = Circular hunt group
2 = Linear hunt group
3 = Group call
4 = Group call, no answer
5 = Basic MULAP
6 = Executive MULAP
7 = Group call, call waiting
16 15 3 Group name, select group and enter name (alphanumeric)1
16 15 4 Select host (master)/executive, group, and station (only stations that are
not the host (master) telephone in another group)
16 16 Call allocation, day; select slot/trunk and assign station no.
16 17 Call allocation, night; select slot/trunk and assign station no.
16 18 Call forwarding
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
16 18 1 Select call destination list and destination index (1 – 4).
Call destination lists:
● up to and including V1.2 = 70
● V3.0 or later =
– 376 for HiPath 3550, HiPath 3500
– 70 for all other systems
Select destination (1 – 4), possible entries:
● targeted call number of a station or a group
● * = identical to called station
● #9 = system search of all stations except for the executive exten-
sions
● #201 – #260 = uniform call distribution group 01 to group 60
● #301 – #316 = announcement device 01 to 16
● an external destination, in other words call numbers in satellites and
in the central office
16 18 2 Internal calls; select station/group:
● up to and including V1.2 = 70
● V3.0 or later =
– 1 – 376 for HiPath 3550, HiPath 3500
– 1 – 70 for all other systems
16 18 3 External calls, day; select station/group:
● up to and including V1.2 = 1 – 70
● V3.0 or later =
16 18 4 External calls, night; select station/group:
● up to and including V1.2 = 1 – 70
● V3.0 or later =
16 18 5 Number of rings (1 to 15) for station/group
16 18 6 Night bell, location for station/group
16 18 7 Night bell, mode:
1 = Immediate connect, 2 = After timeout
16 18 8 Call forwarding (CF) on busy, 0 = Do not forward call, 1 = Forward call
16 19 Ring cadence: 0 = Ring type 1, 1 = Ring type 2, 2 = Ring type 3
16 20 DTMF DID: 0 = denied, 1 = allowed
16 21 Ringback protection (Brazil): 0 = off, 1 = on
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
17 Networking
17 11 Simplified dialing: 0 = Off, 1 = On
17 12 Assign trunk group; select slot/trunk and assign trunk group
Route 1-8 (HiPath 3350, HiPath 3300)
Route 1 - 16 (HiPath 3550/HiPath 3500)
17 13 Overflow route; select route and assign overflow route
17 14 Trunk type CO/CS; select trunk type: 0 = CO, 1 = CS
17 15 Route name, select route and enter name (alphanumeric)1
17 16 Route seizure; Route selection: 0=cyclic, 1= linear
17 17 Rerouting (optimized B channel utilization)
17 17 1 Route optimize active: 0 = No, 1 = If route is known, 2 = Always
17 17 2 Change route: 0 = denied, 1 = allowed
17 18 Central intercept
17 19 Call data routing
17 19 1 Destination system
17 20 Digit repetition; select trunk group: 0 = off, 1 = on
17 21 Path optimization: 0 = no, 1 = yes
17 22 QSig: Voice mail
17 22 1 Callback access number
17 22 2 Callback access name
17 23 QSig: Busy signaling
17 23 1 Stations: 0 = no, 1 = yes
17 23 2 Station number, destination system
17 23 3 System number, destination system
17 24 Station number type: 1 = Internal, 2 = DID, 3 = Internal/DID
18 Traffic restriction
18 1 Configure exec./sec. groups; select group, enter:
1 = Exec. 1. 2 = Exec. 2. 3 = Sec. 1. 4 = Sec. 2
HiPath 3550/HiPath 3500: Group 1-10
HiPath 3350/HiPath 3300: Group 1-4
18 2 Hotline
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
18 2 1 Hotline destinations
HiPath 3550/HiPath 3500 Destination 1-6
HiPath 3350/HiPath 3300: Destination 1
18 2 2 Hotline station number
18 2 2 1 Hotline Mode: 0 = Off, 1 = Hotline, 2 = Off-hook alarm after timeout
18 2 2 2 Hotline assignment
HiPath 3550/HiPath 3500 1-6
HiPath 3350/HiPath 3300 1
18 2 3 Hotline timeout, 1-99 x s
18 3 ITR groups (internal traffic restriction groups)
18 3 1 Group assignment
18 3 1 1 Station
18 3 1 2 Lines, select slot/line
18 3 1 3 Speed-dialing number assignment
18 3 1 3-1 Minimum speed-dialing group, Select group, 0 to 999
18 3 1 3-2 Maximum speed-dialing group, Select group, 0 to 999
18 3 2 Connection groups
18 3 2 1 Matrix, Select Group: 0 = no, 1 = yes
19 Displays
19 11 Text messages: select message no. 0 to 9 and enter a text containing up
to 24 1 characters (alphanumeric)
19 12 Advisory messages: select message no. 0 to 9 and enter a text contain-
ing up to 24 1 characters (alphanumeric)
19 13 Enter 4-digit time in the format HHMM (hour minute)
19 14 Enter 6-digit date in the format DDMMYY (day month year)
19 15 Call duration: 0 = off, 1 = on
19 16 Name, Call numbers: 0 = Calling ID only, 1 = Name, 2 = Name and call-
ing ID
19 17 Automatic recall 1 = Caller, 2 = Transferred destination
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
19 18 Transfer before answer: 1 = Transferred by, 2 = Transferred to
20 ISDN parameters
20 1 Call number suppression 0 = off, 1 = on
20 2 System station number - incoming
20 2 1 Station number; select trunk group
20 2 2 National number; select trunk group
20 2 3 International number; select trunk group
20 2 4 Type, outgoing; select trunk group:
0 = Unknown, 1 = Station, 2 = National, 3 = International, 4 = Internal
20 2 5 National prefix (U.S. = 1)
20 2 6 International prefix (U.S. = 011)
20 3 Reference clock
20 3 1 Allowed nos. list; select position (slot and port)
20 3 2 Denied nos. list; select position (slot and port)
20 4 EU parameters (not for U.S.)
20 4 1 S0 port configuration; select slot/port and determine connection type (not
for U.S.):
1 = Automatic
2 = Euro CO PP
3 = Euro CO PMP
4 = Euro bus
5 = CorNet 1
6 = CorNet 2
7 = ECMA-QSIG
8 = ISO-QSIG
20 4 2 S2M port configuration; select slot/port and determine connection type
(not for U.S.):
1 = Euro CO PP
2 = CorNet 1
3 = CorNet 2
4 = ECMA-QSIG
5 = ISO-QSIG
20 4 3 S0 bus MSN (for verification purposes only)
20 4 4 Call forwarding PMP
20 4 4 1 Multiple subscriber numbers, select index, 1 to 10
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
20 4 4 2 MSN trunks, select index, 1 to 10
20 5 US parameters (for U.S. only)
20 5 1 BRI parameter
20 5 1 1 CO/protocol:
1 = AT&T/NI 1
2 = AT&T/Custom
3 = Siemens/NI 1
4 = NT/NI 1
20 5 1 2 SPID admin, select station, select slot/port
20 5 1 3 CAID admin, stn., select CAID
20 5 1 4 PDID admin, stn., select PDID
20 5 1 5 FIN - for message waiting
20 5 1 6 CACH EKTS, select slot/port: 0 = off, 1 = on
20 5 2 PRI parameters
20 5 2 11 Protocol type:
11 = AT&T/Custom
12 = AT&T/NI2
13 = AT&T/NI2 OSA
14 = AT&T/4ESS
15 = Siemens/Custom
16 = Siemens/Custom OSA
17 = Siemens/NI2
18 = Siemens/NI2 OSA
19 = MCI/DEX600
20 = MCI/DMS250
21 = BELL/DMS100
22 = BELL DMS100 TNS
23 = Nortel/DMS100
24 = Nortel DMS100 TNS
25 = SPRINT/DMS250
26 = Westinghouse
27 = FTS/DMS250
28 = FTS/5ESS
29 = GENERIC/NI2
30 = GENERIC/NI2 OSA
31 = QSIG
32 = IDA-P
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
20 5 2 12 Frame/line/encod, select slot
0 = ESF/B8ZS/Normal
1 = SF/ZCS/Inverted
20 5 2 13 Inwats parameter
20 5 2 13-1 Direction
20 5 2 13-2 DNIS
20 5 2 13-3 Entrance telephone ring destination
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
20 5 2 14 Calling service, select trunk group
11 = NONE
12 = AT&TSDN-GSDN
13 = AT&TSDDN
14 = MCI-VN-VS
15 = SPRINT-VPN
16 = WICN-PV
17 = MEG800-TFM
18 = MCI 800
19 = ULTRA-800
20 = WICN-INWATS
21 = MEG
22 = MCI-PRISIM-WATS
23 = SPR-ULTRA-WATS
24 = WICN-OUTWATS
25 = ACCU-SDS
26 = LDS-WC-TSAA
27 = INTER-800
28 = MULTIQUEST
29 = MCI-900
30 = SDS56
31 = SDS64C
32 = SDS64R
33 = DMS100-PV
34 = DMS100-INWATS
35 = DMS100-OUTWATS
36 = DMS100-FX
37 = 5ESS-INWATS
38 = WATS-MSB
39 = DMS100-TIE
40 = NI2-INWATS
41 = NI2-OUTWATS
42 = NI2-FX
43 = NI2-TIE
44 = NI2-HOTEL
45 = NI2-SCOCS
46 = CALL-BY-CALL 1
47 = CALL-BY-CALL 2
48 = CALL-BY-CALL 3
49 = CALL-BY-CALL 4
50 = WATS-BANDED
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
20 5 2 15 CBC pool:
11 = AT&TSDN-GSDN
12 = AT&TSDDN
13 = MCI-VN-VS
14 = SPRINT-VPN
15 = WICN-PV
16 = MEG800-TFM
17 = MCI 800
18 = ULTRA-800
19 = WICN-INWATS
20 = MEG
21 = MCI-PRISIM-WATS
22 = SPR-ULTRA-WATS
23 = WICN-OUTWATS
24 = ACCU-SDS
25 = LDS-WC-TSAA
26 = INTER-800
27 = MULTIQUEST
28 = MCI-900
29 = SDS56
30 = SDS64C
31 = SDS64R
32 = DMS100-PV
33 = DMS100-INWATS
34 = DMS100-OUTWATS
35 = DMS100-FX
36 = 5ESS-INWATS
37 = WATS-MSB
38 = DMS100-TIE
39 = NI2-INWATS
40 = NI2-OUTWATS
41 = NI2-FX
42 = NI2-TIE
43 = NI2-HOTEL
44 = NI2-SCOCS
20 5 2 16 CBC access code
20 5 3 S0 bus MSN, select slot/port
20 5 4 QSig: S0 parameter
20 6 QSIG parameter
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
20 6 1 System number
20 6 2 Group number
20 7 Keypad dial: 0 = denied, 1 = allowed
20 8 System station number - outgoing
20 8 1 Port number
20 8 2 National number
20 8 3 International number
20 8 4 Suppress station number
21 Analog CO interface
21 1 Dialing method; select slot/trunk:
0 = Automatic,
1 = DTMF,
2 = Dial pulses
3 = MFC-R2,
4 = MFC-R2 with OAD
21 2 Delayed dialing; select trunk group:
0 = No pause, 1 = 1 s, 2 = 3 s, 3 = 6 s, 4 = 9 s
21 3 Trunk call pause; select trunk group: 1 = 6 s, 2 = 13 s
21 4 Line Length; select slot and trunk: 0 = Short 1 = Long
21 5 Charge data module, select slot/trunk: 0 = off, 1 = on
21 6 Silent reversal: 0 = no, 1 = yes
21 7 Port status: 0 = on, 1 = Off (SW), 2 = Off (HW), 3 = Off (HW, SW)
21 8 Allocated without extension
22 System settings
22 11 Music on Hold (MOH): 0= Off, 1 = No ring tone, 2 = Ring tone, 3 = An-
nouncement device 1
22 12 Internal Phonebook: 0 = No, 1 = Internal, 2 = LDAP, 3 = All
22 13 V.24 (RS-232) configuration
22 13 1 Select CB baud rate: 1 = 9600 baud, 2 = 2400 baud, 3 = 19200 baud
22 13 2 Port assignment
22 13 2 1 CSTA/CDRC (call detail recording central), output: 0 = none, 1 = V.24
port, 2 = UPN port, 3 = PC-VPL, 4 = LAN
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
22 13 2 2 Port for CDRS (call detail recording at station), output: 0 = none, 1 = V.24
port, 2 = UPN port
22 13 2 3 Port for CDRT (call detail recording per trunk), output: 0 = none, 1 = V.24
port, 2 = UPN port
22 13 2 4 Port for CDB printout
22 13 2 5 Port for CDR printout
22 13 2 6 Port for CDRA (call detail recording, attendant); if a pay phone is config-
ured, also see code 11 8), output: 0 = none, 1 = V.24 port, 2 = UPN port
22 14 Call FWD, external
22 14 1 Connect call: 0 = On answer, 1 = Immediately.
22 14 2 Call forwarding: 0 = deactivate, 1 = activate
22 15 Caller list mode: 1 = Only external, 2 = External and Internal, 3 = External
ring/call
22 16 Application
22 16 1 Call distribution: 0 = no, 1 = yes
22 17 Tones
22 17 1 Conference, Warning tone: 0 = off, 1 = on
22 17 2 Call pickup, Warning tone: 0 = off, 1 = on
22 18 Transfer key (Retrieve): 1 = Press once, 2 = Press twice
22 19 Class of service
22 19 1 Night answer, Pos. 1-5; enter station
22 19 2 Central telephone lock
22 20 DTMF automatic: 0= no, 1 = yes
22 21 Key click: 0=Off, 1= Volume 1 ... 4 = Volume 4
22 22 DTMF - Pulse/Pause: 1 = 70/70 msec, 2 = 80/80 msec, 3 = 80/250 msec,
4 = 200/200 msec
22 23 Phone lock destination
22 24 Stn. relocate: 0 = denied, 1 = allowed
22 25 Trunk reservation: 0 = off, 1 = on
22 26 Speaking volume: 0 = default, 1 = high
22 27 CO features (Transfer/Conference/Drop): 0 = disabled, 1 = enabled
22 28 Feature Identification Number (FIN) for Transfer (for U.S. only)
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
22 29 Feature Identification Number (FIN) for Conference (for U.S. only)
22 30 Feature Identification Number (FIN) for Drop (for U.S. only)
22 31 MSN default: 0 = off, 1 = on
22 32 DTMF hidden: 0 = off, 1 = on
22 33 Announcement with connection: 0 = denied, 1 = allowed
22 34 MFC-R2 parameters
22 34 1 Ringback protection
22 34 2 DID digits
22 35 Common hold
22 35 1 By hanging up
22 35 2 Without hanging up
22 36 Switch line, DSS: 0 = no, 1 = yes
(Status 1 = U.S., Status 0 = Rest of World (ROW)
22 37 Advisory call 0 = off, 1 = on
22 38 Trace stop facility
22 38 1 Stop trace
22 38 1 01 Assistant: 0 = inactive, 1 = active
22 38 1 09 HW: 0 = inactive, 1 = active
22 38 1 12 Processor: 0 = inactive, 1 = active
22 38 1 15 APSXF: 0 = inactive, 1 = active
22 38 1 16 General: 0 = inactive, 1 = active
(error 19 cannot be set to inactive)
22 38 1 20 CP: 0 = inactive, 1 = active
22 38 1 21 DH: 0 = inactive, 1 = active
22 38 1 23 Network: 0 = inactive, 1 = active
22 38 1 26 Presence 0 = inactive, 1 = active
22 38 1 28 Recovery: 0 = inactive, 1 = active
22 38 1 29 IO Process: 0 = inactive, 1 = active
22 38 1 30 LW: 0 = inactive, 1 = active (0 to n)
22 38 1 11 LW date: 0 = inactive, 1 = active (41 to n)
22 38 2 Reset 1 = Delete all, 2 = System default
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
22 39 IP access
22 39 1 IP interface, mode:
0 = Inactive
1 = HIP Forwarding
2 = LIM
3 = SLIP Routing
22 39 2 IP address, data (7 ... 15): x.x.x.x (x = 0 ... 255)
Use either "*" or "." as a separator.
22 39 3 Subnet mask
22 39 4 Gateway IP address
22 40 Open numbering
22 40 1 Active/inactive
22 40 2 Voice mail node number
22 40 3 Node number
22 41 UCD permanently available: 0 = inactive, 1 = active
23 Code
23 1 Substitute code *, code 75
23 2 Substitute code #, code 76
23 3 Trunk access code; select slot and trunk and enter new code
23 4 Route code; Select route followed by position 1-10 for code and enter
new code
Route 1-8 (HiPath 3350HiPath 3300, )
Direction 1-16 (HiPath 3550/HiPath 3500)
23 5 Attendant code
23 5 1 Attendant code DID
23 5 2 Attendant code internal
23 6 Second trunk access code
23 7 Reset telephone lock code
23 8 Hotel terminal
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
24 Door relay
24 1 Entrance phone; select door, max. 6 digits, door 1-4
24 2 Destination; select door, max. 6 digits, door 1-4
24 3 Door opener; select door: 0 = not available, 1 = available, 2 = available
with DTMF, doors 1-4
24 4 Call forwarding, door, external; select door: 0 = do not run, 1 = run
24 5 Door opener, DTMF, select station: 0 = denied, 1 = allowed
25 Announcement/Music
25 1 Announcement devices
25 1 1 In system (select announcement device 1 ... 16)
25 1 2 Via server (select announcement device 1 ... 16)
25 2 Type of ann., select ann. device: 1 = Ann. type, 2 = Music on hold, 3 =
Internal music
25 3 Announcement prior to answer; select slot and trunk
25 4 External MOH
(Only enter analog line module stations.)
26 Relays
26 1 Type; select relay 1 to 4 and assign function:
11 = Manual on and off
12 = Off after timeout
13 = Door opener
14 = Speaker amplifier (starting contact for amplifier)
15 = Busy display
16 = Music on hold
17 = Call charge pulse
18 = Second bell
19 = Station active
20 = Announcement
26 2 Switching time
Select relay 1 through 4 and enter up to 3 digits (0 to 255)
26 3 Assigned station
Select relay 1 through 4 and enter stations or groups
(up to 5 digits)
26 4 Relay name; select relay 1 to 4, enter a name containing up 16 1 charac-
ters (alphanumeric)
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
27 Sensors (HiPath 3550/HiPath 3350/HiPath 3500/HiPath 3300 only)
27 1 Type: 0 = Alarm, 1 = Call distribution
27 2 Destination station no.; select sensor 1 - 4
External station with seizure code (trunk/direction)
Internal station with station prefix (if programmed)
27 3 Station no. for announ.; select sensor 1 - 4 and enter station or group
number (max. 6 digits)
27 4 Infobox control data; select sensor 1 - 4 and enter control characters 0 -
9, *, #, max. 24 digits
27 5 Call duration; select sensor 1 through 4 and enter 1 to 255
27 6 Call pause; select sensor 1 through 4 and enter 0 to 255
27 7 Number of rings; select sensor 1 through 4 and enter 1 to 255
27 8 Block time; select sensor 1 through 4 and enter 0 to 255
27 9 Sensor text; select sensor 1 to 4, enter text containing up 16 1 characters
(alphanumeric)
28 Edit CDB
28 1 Print CDB data
28 2 Save CDB data
28 2 1 CDB to MMC
28 2 2 CDB from MMC
29 System details
29 1 System
29 1 1 System type (for verification purposes only)
29 1 2 SWversion (for verification purposes only)
29 2 Status display
29 2 1 Call forwarding, external, 0 = Off, 1 = On (for verification purposes only)
29 2 2 Night service, 0 = Off, 1 = On (for verification purposes only)
29 2 3 Trunk, 0 = Inactive, 1 = Active (for verification purposes only)
29 2 4 Ping, 1 = IP address, 2 = Start
29 2 5 MAC address
29 3 Options (HiPath 3550, HiPath 3350, HiPath 3500 and HiPath 3300 only)
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
29 3 1 Type per option (for review only)
1 = Relays
2 = Call detail recording
3 = Fax/DID
4 = ANI
5 = Announcement (Beyer)
29 3 2 Software version for each option (1 to 16) (for verification purposes only)
29 3 3 Reset options
29 4 Boards
29 4 1 Board type, select slot:
11 = TMS2
12 = TMST1 - digital
13 = TIEL
14 = TMDID
15 = TML8W
16 = TMOM
17 = TMGL8
18 = TLA2
19 = TLA4
20 = TLA8
21 = TS2
22 = TMGL2
23 = TMGL4
24 = TMQ2
25 = TMQ4
26 = TST1 - digital
27 = STMD
28 = STLS2
29 = STLS4
30 = SLA16
31 = SLMO8
32 = SLMO24
33 = SLMC8 (CMI V1)
34 = 4SLA / SLAD4
35 = 8SLA / SLAD8
34 = 4SLA
35 = 8SLA
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
36 = 16SLA
37 = SLU8
38 = ILAN
39 = SLC16 (CMI V2.2M)
42 = SLMO8K
43 = SLMO24K
44 = SLA8N
45 = SLA16N
46 = SLA24N
47 = TMAMF
48 = CR8
49 = SLU4 (Octopus E 10)
50 = SLU2 (Octopus E 10)
52 = HXGS (HiPath 3550, HiPath 3350, HiPath 3500, HiPath 3300)
53 = IVMS8
54 = IVML8
55 = IVML24
56 = SLAS16
57 = TMCAS
58 = SLUC8 (UP0/E interfaces on CBCC, CBRC, CBCP)
59 = SLUC4 (UP0/E interfaces on SBSCO)
60 = SLUC2 (UP0/E interfaces on SBSCS)
61 = SLAS4N
62 = SLAS8N
63 = IVMP8
64 = HXGM3
65 = HXGS3
66 = SLC16N
67 = STMD2
68 = STLS2N
69 = STLS4N
70 = SLMO2
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
71 = TMEW2
72 = DIUN2
73 = SLMA8
74 = SLMA3
75 = SLMA2
76 = SLMO8_HP4K
77 = STMD3
78 = SLCN
79 = STMI2
80 = IVMN8
81 = IVMNL
82 = TM2LP
83 = TMDID_HP4K
84 = TMC16
85 = DIU2U
86 = EVM2
87 = TS2
88 = STMD3 (feeding)
29 4 2 xx Reset board (for board no., see 29-4-1)
29 4 3 0-9 Board status
29 4 4 Disable/enable board
29 5 Country initialization
29 5 1 Variable password
29 5 1 00 SeeSelect country code
to
99
29 5 2 Fixed password
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
29 5 2 00 Select country code
to 11 = Germany
99 12 = Netherlands
13 = France
14 = Finland
15 = United Kingdom
16 = Italy
17 = Spain
18 = Portugal
19 = Switzerland
20 = Austria
21 = International
22 = Ireland
23 = Belgium
24 = Brazil
25 = South Africa
26 = China
28 = India
29 = Czech Republic
30 = Denmark
31 = Australia
32 = Argentina
33 = Philippines
35 = Brazil 2
36 = Singapore
37 = Hungary
38 = Malaysia
40 = Indonesia
41 = Russia
42 = Thailand
46 = Poland
47 = Greece
49 = Sweden
50 = Norway
51 = Turkey
52 = U.S.
53 = Pakistan
54 = Hong Kong
55 = New Zealand
56 = Taiwan
57 = Korea
29 6 Virtual subscribers
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
29 6 1 Configure stations
29 6 2 Display stations
30 Remote service
30 1 DTMF access: 0 = No access, 1 = Access as host (primary), 2 = Access
as client (secondary), 3 = Host and client (primary and secondary)
30 2 ISDN trunk access: 0 = Enable procedure, 1 = Logon (DID) without PIN,
2 = Logon (DID) with PIN, 3 = Callback
30 3 Other access: 0 = Enable procedure, 1 = Logon without code, 2 = Logon
(DID) with code, 3 = Callback
30 4 Reset password
30 5 Integrated modem
30 5 1 Station number, remote service, max. 6 digits
30 5 2 DID number, remote service
30 5 3 CAID admin (for U.S. only)
30 6 Digital modem
30 6 1 Station number, remote service, max. 6 digits
30 6 3 CAID admin (for U.S. only)
30 7 Callback connection
30 7 1 Destination; select position (1-6)
30 7 2 Password; select position (1-6)
30 7 3 X.75 protocol: 0 = no, 1 = yes
30 8 Automatic CDB printout: 0 = no, 1 = yes
30 9 USBS D channel access
30 9 1 Station number, remote service
31 Call distribution
31 1 Group assignment; select group ID
31 2 Group parameters
31 2 1 Announcement device; select group
HiPath 3550/HiPath 3350/HiPath 3500/HiPath 3300: Announcement de-
vice 1-4
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
31 2 2 Wait times; select group, time: 1-9 x 30s
31 2 3 Call cycles
31 2 3 1 Primary cycles; select group
31 2 3 2 Secondary cycles; select group
31 2 4 AICC connection; select group 0 = off, 1 = on
31 2 5 Max. waiting calls; select group
31 3 Wrap-up time: 0 = no wrap-up time, 1-20 = wrap-up x 30s
31 4 Call priority external; select slot/trunk
31 5 Call priority internal
32 Paging
32 1 PSE port (slot and trunk)
32 3 Protocol: 1 = ESPA 4.4.5, 2 = ESPA 4.4.3
32 4 Operating mode
32 4 1 Mode urgent
32 4 2 Mode normal
32 4 3 Mode text
32 5 Display
32 5 1 Number
32 5 1 1 Number of digits
32 5 1 2 Display, filler: 0=none, 1=left, 2=right
32 5 1 3 Filler
32 5 2 Text
32 5 2 1 Number of digits
32 5 2 2 Display, filler: 0=none, 1=left, 2=right
32 5 2 3 Filler
32 6 PSE data transfer; select sequence: 1 = Operating mode, 2 = Call no., 3
= Text
32 7 PSE dial assignment; select station (not for U.S.)
32 8 PSE dial numbers; select index
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
33 Attendant
33 1 Queued calls
33 3 Speed extending: 0 = denied, 1 = allowed
33 4 Extend undialed lines : 0 = denied, 1 = allowed
34 DISA
34 1 Day/night. select slot / line: 0 = None, 1 = Only night, 2 = Only day, 3 =
Day and night
34 2 DID number
34 3 Security mode: 0 = by time, 1 = by #
34 4 CAID admin (for U.S. only)
35 Least Cost Routing (LCR)
35 1 LCR on or off: 0 = off, 1 = on
35 2 Digit transmission: 0 = Digit-by-digit, 1= En-bloc sending
35 3 Dial rule
35 3 1 Name; select line
35 3 2 Format; select line
35 3 3 Type, select line: 0 = undefined, 1 = Main network supplier, 2 = 1-level,
3 = 2-level, 4 = CN, 5 = DICS, 6 = PRI
35 4 Authorization code; select index (1-16)
35 5 Schedule
35 5 1 Time limit; select day index (1 = Monday to 7 = Sunday) and time format
(hhmm)
35 5 2 Timezone; select day index (1 = Monday to 7 = Sunday) and time period
1-8
35 6 Class of service (1 to 15); select station
35 7 Route tables
35 7 1 Route; select table/line
35 7 2 Assign dial rule; select table/line
35 7 3 Min. authorization; select table/line
35 7 4 Assign timezone; select table/line
35 7 5 Warning, select table/line: 1 = none, 2 = display, 3 = tone, 4 = display and
tone
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
35 8 Dial plan
35 8 1 Dialed digits; select line
35 8 2 Assign route table; select line
35 8 3 Account codes: 0 = no, 1 = yes
35 8 4 Toll restriction, private: 0 = no, 1 = yes
35 8 5 Toll restriction: 0 = no, 1 = yes
35 8 6 Emergency number
36 1 Log on CMI unit; select device: 1 = inactive
36 2 CMI code; select device
36 3 CMI number; select device, changes not possible
36 4 Reset cordless code
36 5 DECT identification, data:
1. E/ARC
2. EIC
3. FPN
4. FPS
37 Security
37 1 Change password
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
Code Function
51 – 63 Customer administration (previously Assistant TC)
52 Time, hour/minute
53 Date, ddmmyy
55 Station names
56 Text messages
57 Advisory messages
58 Select language
59 Group names
61 Hotline
61 1 Hotline destinations
61 2 Hotline station
61 2 1 Hotline mode, 0 = Off, 1 = Hotline, 2 = Code blue
61 2 2 Hotline assignment
61 3 Hotline timeout
62 Codes, remote service
63 Codes, Cordless
The "bolded" messages only appear on workpoints that support alphanumeric character en-
try.1
1 Alphanumeric characters can only be entered at the following workpoints: optiset E memory, optiPoint 600 office (in UP0/
E mode), optiPoint 410 advance, optiPoint 420 advance, and OpenStage 40/60/80. Entry is also possible via the optiPoint
application module (in connection with optiPoint 500 basic/standard/advance).
A31003-H3570-S100-6-7620, 2008-04-01
pcodes.fm
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm
Nur für den internen Gebrauch Codes for Activating/Deactivating Features
B Codes for Activating/Deactivating Features

This appendix describes the options for activating and deactivating features depending on the
different workpoint clients (WpC).
Table B-1 contains all the activation/deactivation procedures for analog workpoint clients,
TDM workpoint clients without a display and CMI mobile phones. The table only
contains the access codes for TDM workpoint clients with a display, CMI feature
mobile phones and IP workpoint clients. The procedures for S0 workpoint clients
either correspond to procedures for analog workpoint clients or are handled via
the relevant ISDN protocol with the terminal-specific user interface.
The table also contains information about the effect of the telephone lock and
the status-specific locking of features.
Table B-2 contains a description of the various types of workpoint clients.
Table B-1 Codes for Activating/Deactivating Features

Operating procedure for
TDM work-
point clients
TDM workpoint clients with
without dis- optiCli- Locking of
S0 work- display,
play, ent 130 feature
point cli- CMI feature mobile phones,
CMI mobile easy- Supported
ents IP workpoint clients,
phones, Com workpoint
optiClient 130 phone
analog work- clients
Feature point clients1 Note
(see abbrevi-
Key Menu ations in
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Activate relay *90+Relay no. 7590... *90... – V, T – H – AN, DIG, ENT, X RK,
S0, CMI, IPSC BS
Deactivate re- #90+Relay no. 7690... #90... – V, T – H – AN, DIG, ENT, X RK,
lay S0, CMI, IPSC BS
Accept call *55 7555 *55 – V BR, U Mouse AN, DIG, ENT, – – Also possible via
waiting (camp- WA, click, S0, CMI, the DSS, GESP,
on) RG, Drag& IPSC, IPH3 LTG or MUSAP key
GS, Drop
BS
Bar call wait- #490 76490 #490 – V, T RH U1 Fea- AN, DIG, ENT, X RK,
ing (automatic) ture S0, CMI, IPSC BS
key
Abbreviations:
● Call states: RH = idle, BR = ready, WA = digit input, BS = busy, RK = incoming call, RG = outgoing call, GS = call
● Key programming: V = key can be programmed with complete feature, U = key can be programmed to start procedure, T = key with
toggle functionality
● Menu level: H = Main menu, U1 = 1st submenu, U2 = 2nd submenu
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual B-1
fcodes.fm
Codes for Activating/Deactivating Features Nur für den internen Gebrauch

TDM work-
point clients
S0 work- display,
Feature Note
point clients1 (see abbrevi-
ations in
Key Menu
Programmable Table B-2)
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Allow call wait- *490 75490 *490 – V, T RH U1 Fea- AN, DIG, ENT, X RK,
ing (automatic) ture S0, CMI, IPSC BS
key
Silent call wait- *87 7587 *87 – V, T RH U1 Local AN, DIG, ENT, X RK,
ing (camp-on) feature S0, CMI, IPSC BS
on
Silent call wait- #87 7687 #87 – V, T RH U1 Local AN, DIG, ENT, X RK,
ing (camp-on) feature S0, CMI, IPSC BS
off
Logon mode *942+Code – *942 – – – H – DIG, CMI X
(for handset) +Stn. no.
Query caller – – #82... – V RH, U Local DIG, IPSC, X Only if enabled
list BR feature IPSI
menu
Missed calls - – – *82 – – RG, – Local DIG, IPSC X RK, Only if enabled
save number/ GS active BR,
save call num- menu WA
ber
Do not disturb *97 7597 *97 – V, T RH U Fea- AN, DIG, ENT, X RK,
on ture S0, CMI, IPSC BS
key
Do not disturb #97 7697 #97 – V, T RH U Fea- AN, DIG, ENT, X RK,
off ture S0, CMI, IPSC BS
key
Call forward- *1+Type+Stn. 751... *1... – V, U, RH U Fea- AN, DIG, ENT, X RK, Later selection of
ing on, internal no. or T ture S0, CMI, IPSC BS the forwarding type:
or external Call for- key 1 = All calls, 2 = Ex.
warding calls only, 3 = nt.
(local S0 calls only
WpC
function-
ality)
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
B-2 HiPath 3000/5000 V7, Service Manual
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Call forward- #1 761 #1 – V, T RH U1 Fea- AN, DIG, ENT, X RK,

ing off ture S0, CMI, IPSC BS
key
Call forward- – – *64... – V, U, RH U1 – AN, DIG, ENT, X RK, Only for S0 trunk
ing in EDSS1 T S0, CMI, IPSC BS connection and au-
trunk on (not thorized stations.
for tenant ser- Later selection of
vice) the forwarding type:
1 = immediate, 2 =
Call forward- – – #64... – V, T RH U1 – AN, DIG, ENT, X
unanswered calls,
ing in EDSS1 S0, CMI, IPSC
3 = on busy.
trunk off (not
All call forwarding
for tenant ser-
types can be acti-
vice)
vated independent-
ly of each other.
CFSS (Call – – *9411 – V, U, – U1 – IPSC X RK, CFSS (call forward-
forwarding sta- T BS ing station out of
tion out of ser- service) has higher
vice) priority than normal
call forwarding.
CFSS (Call – – #9411 – V, T – U1 – IPSC X
forwarding sta-
tion out of ser-
vice)
Call forward- *501+MU- 75501 *501 – V, T – H – AN, DIG, ENT, Only for MULAP
ing on for each LAP+Type+Stn. S0, CMI, IPSC members
MULAP no.
Call forward- #501+MULAP 76501 #501 V, T – H – AN, DIG, ENT, Only for MULAP
ing off for each S0, CMI, IPSC members
MULAP
UCD (uniform *401+ID – *401.. – V, U, – U2 Fea- AN, DIG, ENT, X RK, Only for UCD group
call distribu- T ture CMI, IPSC BS members
tion), logon key
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
UCD (uniform #401 – #401 – V, T – U2 – AN, DIG, ENT, X RK, Only for logged on
call distribu- CMI, IPSC BS stations
tion), logoff
UCD, avail- *402 – *402 – V, T – U2 – AN, DIG, ENT, X RK, Only for logged on
able CMI, IPSC BS stations
UCD, unavail- #402 – #402 – V, T – U2 – AN, DIG, ENT, X RK, Only for logged on
able CMI, IPSC BS stations
UCD, rework *403 – *403 – V, T – U2 – AN, DIG, ENT, X RK, Only for logged on
on CMI, IPSC BS stations
Call distribu- #403 – #403 – V, T – U2 – AN, DIG, ENT, X RK, Only for logged on
tion, rework off CMI, IPSC BS stations
Call distribu- *404 +* or Stn. – *404 ... – V, U, – U2 – AN, DIG, ENT, X RK, Only for logged on
tion, night des- no. T CMI, IPSC BS stations
tination on
Call distribu- #404 – #404 – V, T – U2 – AN, DIG, ENT, X RK, Only for logged on
tion, night des- CMI, IPSC BS stations
tination off
Call distribu- – – *405 – V – U2 – AN, DIG, ENT, X RK, Only for logged on
tion, queue CMI, IPSC BS stations
Call accep- – – – – V – – Mouse AN, DIG, ENT, X RH, Can only be activat-
tance click, CMI, IPSC BR, ed using key
Drag& WA,
Drop BS,
RG
Advisory mes- – – *69... – V, U, RH U1 Local DIG, CMI, X RK,
sage on T feature IPSC BS
menu
Advisory mes- – – #69... – V, T RH U1 Local DIG, CMI, X RK,
sage off feature IPSC BS
menu
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Associated di- *67+Stn.+Stn. 7567... *67... – U – H – AN, DIG, ENT, X Only for authorized
aling no. S0, CMI, IPSC stations
Associated *83+Stn.+ 7583 *83... – U – H – AN, DIG, ENT, X RK, Only for authorized
services Services proce- S0, CMI, IPSC BS stations
dure...
Override *62 – *62 – V RG U1 – AN, DIG, – – Only for authorized
ENT, CMI, stations
IPSC
Room monitor *88 7588 *88 – V – H – AN, DIG, ENT, X WA, Not possible for
on S0, CMI, IPSC RG,G workpoint clients
S,RK without a speaker-
,BS phone when hand-
set is on-hook
Room monitor – – – – – – – – AN, DIG, ENT, – Room monitor off
off S0, CMI, IPSC by hanging up or
pressing the loud-
speaker or release
key
Telephone *66+Code 7566... *66... – U, T RH U1 Fea- AN, DIG, ENT, – RK,
lock on, indi- ture S0, CMI, IPSC BS
vidual key
Telephone #66+Code 7666... #66... – U, T RH, U1 Fea- AN, DIG, ENT, – RK,
lock off, indi- BR ture S0, CMI, IPSC BS
vidual key
Change tele- *93+Old 7593... *93... – – – H Local AN, DIG, ENT, X RK,
phone lock ac- code+2 x New feature S0, CMI, IPSC BS
cess code code menu
Reset servic- #0 760 #0 – – – H – AN, DIG, ENT, x RK, See feature de-
es/features for S0, CMI, IPSC BS scription: Reset ac-
own workpoint tivated features
client
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Speaker calls *80+Stn. no. 7580 *80 – V, U – H Menu AN, DIG, ENT, – RK, Speaker calls to a
S0, CMI, IPSC BS. group: Paging only
WA, possible if “Speaker
RG call” has been en-
abled for the called
party. The called
party’s microphone
is activated if “Di-
rect Answering”
has been enabled
for this party (not for
paging).
Hands free an- – – *96 – V, T RH U1 – DIG, CMI, X – Only for WpC with
swerback on IPSC speakerphone
Hands free an- – – #96 – V, T RH U1 – DIG, CMI, X – Only for WpC with
swerback off IPSC speakerphone
DISA (Direct – – – – – – – – – – – Activation only pos-
Inward System sible from external
Access) location for autho-
rized stations/lines.
HiPath 5000 does
not support the
DISA feature.
DISA internal *47+DISA stn. – *47... – V, U RH U1 – DIG, ENT, AN, X WA, Within a HiPath
no.+DISA IP RG, 5000 network only.
STN.+service RK, Features cannot be
+Suffix dialing BS activated from ana-
log (DP) or S0
WpC.
Discreet call- *945+Stn. no. *945.. – U – – – AN, DIG, S0, X WA, Only for authorized
ing on IPSC RG, stations
BS,
RK,
GS
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Discreet call- #945+Stn. no. *945.. – U – – – AN, DIG, S0, X WA, Only for authorized
ing off IPSC RG, stations
BS,
RK,
GS
Relocate: *9419 – *9419 – – – – Possi- DIG, ENT X WA, Not for the first two
Save configu- (only TDM WpC ble via RG, station ports
ration without display) central RK,
data- BS,
base GS
Relocate: Re- #9419 – #9419 – – – – – DIG, ENT X WA, Not for the first two
activation, (only TDM WpC RG, station ports
load configura- without display) RK,
tion BS,
GS
Terminal test *940 – *940 – – – U1 – DIG, ENT, – WA,
IPSC RG,
RK,
BS,
GS
MCID *84 MCID *84 – V – H – AN, DIG, ENT, – –
(local S0 S0, CMI, IPSC
WpC
function-
ality)
Flex call *508+Stn. no. 75508 *508 – V – H – AN, DIG, ENT, ––
S0, CMI, IPSC
Emergency *43+Trunk code 7543... *43.. – U – H – AN, DIG, ENT, X RK, Only for attendant
Trunk Access S0, CMI, IPSC BS
View call
charges (see
charge dis-
play)
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Call detail re- – – – – V – – – DIG x RK, Only if appropriate

cording, atten- BS authorization is as-
dant (CDRA) signed
Call recording *493 – – – V, T CMI – Fea- AN, DIG, ENT, X RH, Only for authorized
on TDM WpC with- fea- ture CMI, IPSC BR, stations
out display: pro- ture menu WA,
grammed key han RG,
dset BS,
only. RK
Call recording #493 – – – V, T CMI – Fea- AN, DIG, ENT, X RH, Only for authorized
off TDM WpC with- fea- ture CMI, IPSC BR, stations
out display: pro- ture menu WA,
grammed key han RG,
dset BS,
only. RK
Selective line See numbering See See – V – – See AN, DIG, ENT, X – Only with trunk key
seizure plan number- num- num- S0, CMI, IPSC for prime line
ing plan bering bering Telephone lock for
plan plan outgoing lines only
Group call See numbering See See – V – – See AN, DIG, ENT, – – Group calls can be
plan number- num- num- S0, CMI, IPSC programmed on
ing plan bering bering DSS key
plan plan
Group call, join *85 7585 *85 – V, T RH U1 Fea- AN, DIG, ENT, X RK, All group calls, join
ture S0, CMI, IPSC BS = *85*
menu
Group call, #85 7685 #85 – V, T RH U1 Fea- AN, DIG, ENT, X RK, All group calls,
leave ture S0, CMI, IPSC BS leave = #85#
menu
Hold key – – – – V – – Mouse DIG, ENT – –
click,
Key
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Hardware set- +/– ...(local pro- – +/–... X – – – Local ALL – RK From idle state: Call
tings cedure for CMI) Key parameters, speak-
er mode (if avail-
able)
From talk state: Vol-
ume
Hotel terminal *491+Stn. no. 75491 *491 – – – H – AN, DIG, ENT, X WA, Activate LED
S0, CMI, IPSC RK,
BS,
RG
Hotline – – – – – – – – AN, DIG, ENT, – – Hotline destination
S0, CMI, IPSC is defined for each
individual station in
the CDR.
Send mes- *68+(Stn. 7568... *68 – V, U RH, U1 Local AN, DIG, ENT, X RK, Without dialing call
sage (mes- no.)+Text no. RG feature S0, CMI, IPSC BS number in ringing
sage waiting) menu state
Cancel/an- #68 7668 #68 – – RH U1 – AN, DIG, ENT, X RK, Suffix dialing not
swer/display S0, CMI, IPSC BS permitted for DIG,
message S0.
(message Suffix dialing for
waiting) ENT, AN, CMI: 0 =
delete all sent and
received messag-
es, 1 = delete all
sent messages, 2 =
delete all received
messages, 3 = call
sender.
Fax waiting Only TDM work- – – – V – H – DIG, ENT – – Feature deleted by
message/an- point clients pressing the key
swering ma- with corre-
chine sponding key
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Keypad dial – – X503 – – GS – Can be DIG, CMI, – –

dis- IPSC
played
Conference *3 753 *3 – V GS U1 Local AN, DIG, ENT, – – Initiation from call
(up to 5 sta- active S0, CMI, IPSC
tions) menu
End confer- #3 763 #3 – V GS U1 Local AN, DIG, ENT, – RH, Status as prior to
ence (up to 5 active S0, CMI, IPSC BR, conference call.
stations) menu WA, Dialog menu pro-
RG, vides further op-
BS, tions for ending
RK conference.
Call charge – – *65 – V – H – DIG, IPSC X – Deletion only by
display for own system administra-
station (GET) tor
Save/change *92+ISD 7592 *92... – – – H Local AN, DIG, ENT, X RK, ISD 0 ... 9
speed dialing no.+Stn. no. ETD S0, CMI, BS Mobile phones also
system/indi- feature IPSC, IPSI have an additional
vidual local procedure
Dial station *7+ISD no. 757... *7... – V, U – H Local AN, DIG, ENT, X RK, 000 ... 999
speed-dialing ETD S0, CMI, IPSC BS Mobile phones also
(SSD) feature have an additional
local procedure
Dial system *7+ISD no. 757... *7... – V, U – H Private AN, DIG, ENT, RK, ISD 0 ... 9
speed-dialing ETD S0, CMI, BS
(SSD) feature IPSC, IPSI
Trunk queu- – – – – V – – AN, DIG, ENT, X RH, Automatically after
ing, automatic S0, CMI, IPSC BR, timeout if enabled
RG, in the CDR
RK,
GS
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Trunk queu- – – – – V BS – – AN, DIG, ENT, X RH, Activation by press-

ing, manual S0, CMI, IPSC BR, ing a key if enabled
RG, in the CDR
RK,
GS
Toggle *2 752 *2 – V GS U1 Mouse AN, DIG, ENT, – – Also available us-
click, S0, CMI, ing the DSS, GESP,
Key IPSC, IPSI LTG and MUSAP
key.
DTMF trans- *53 7553 *53 – U – H Menu, AN, DIG, ENT, – RH,
mission key S0, CMI, IPSC BR,
WA,
RG,
RK,
BS
Microphone off *52 – *52 X, V, T GS U1 Local AN, DIG, ENT, – – Unavailable for
(mute on) (if microphone T active CMI, IPSC workpoint clients
available) menu without a speaker-
phone if handset is
on-hook
Microphone on #52 – #52 X, V, T BR, U1 Local AN, DIG, ENT, – –
(mute off) (if microphone T WA, active CMI, IPSC
available) RG, menu
GS,
BS
Mobility/re- – – *9419 – U – U1 Possi- IPSC Only for mobile
place call ble us- phone numbers
numbers ing
central Not for the first two
data- station ports.
base
Night answer *44+ * or Stn. 75... *44... – V, U, RH U1 – AN, DIG, ENT, X RK, Standard night ser-
on no. T S0, CMI, IPSC BS vice with *.
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Night answer #44+ * or Stn. 7644 #44 – V, T RH U1 – AN, DIG, ENT, X RK,
off no. S0, CMI, IPSC BS
Repertory key/ – – – – V – – Speed DIG X – Key can be as-
DSS dialing signed an internal
key or external call
number.
Telephone locking
for external reperto-
ry key only.
Paging, see
speaker call to
a group
Park on *56+Park slot 7556 *56... – U, T – H Key, AN, DIG, ENT, – RH,
Menu S0, CMI, IPSC BR
Retrieve call #56+Park slot 7656 #56... – U, T – H Key, AN, DIG, ENT, – WA,
Menu S0, CMI, IPSC EG,
GS,
RK,
BS
Paging system *45+Stn. no. 7545... *45.. – – – AN, DIG, ENT, – –
(PSE comfort), S0, CMI, IPSC
paging
Paging system #45+Stn. no. 7645... #45.. – – – H – AN, DIG, ENT, – –
(PSE comfort), S0, CMI, IPSC
meet me
Account code *60+ACCT 7560... *60... – U – H –/man- AN, DIG, ENT, X WA, ACCT can also be
datory S0, CMI, IPSC RG, entered without
ACCT RK, service code follow-
possi- BS ing ext. line seizure.
ble
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Route seizure See numbering See See – V – – See AN, DIG, ENT, X – Telephone lock only
plan number- num- num- S0, CMI, IPSC permitted for sei-
ing plan bering bering zure of outgoing
plan plan lines.
Set callback *58 CCBS *58 – V, T RG U1 Local AN, DIG, ENT, – RH,
(local S0 active S0, CMI, IPSC BR,
WpC menu WA,
function- GS,
ality) RK,
BS
View or delete #58 CCBS #58... – U, T RH U1 Local AN, DIG, ENT, X RH,
callback re- (local S0 feature S0, CMI, IPSC BR,
quests WpC menu WA,
function- GS,
ality) RK,
BS
Initiate call- DP: Dial HOLD – – – GS – Drag& AN, DIG, ENT, – –
back (exclu- CMI, DTMF: (local S0 Drop, S0, CMI,
sive hold) Flash WpC menu IPSC, IPSI
TDM WpC with- function-
out display: ality)
Consultation
hold key
Call number *86 CLIR *86 – V, T RH U1 Fea- AN, DIG, ENT, X RK,
suppression (local S0 ture S0, CMI, IPSC BS
on, temp. WpC menu
function-
ality)
Call number #86 CLIP #86 – V, T RH U1 Fea- AN, DIG, ENT, X RK,
suppression (local S0 ture S0, CMI, IPSC BS
off, temp. WpC menu
function-
ality)
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Station num- *41+DID no. 7541... *41... – V – H – AN, DIG, ENT, X – This must be fol-
ber, assign for S0, CMI, IPSC lowed by seizure of
MUSAP external line.
Ring transfer *502+MULAP 75502 *502 – V, T – H – AN, DIG, ENT, X Only for member of
on S0, CMI, IPSC the executive MU-
LAP groups
Ring transfer #502+MULAP 76502 #502 – V, T – H – AN, DIG, ENT, X Only for member of
off S0, CMI, IPSC the executive MU-
LAP groups
Ringing group *81+Stn. no. 7581... *81... – U, V, – H – AN, DIG, ENT, X RK,
on T S0, CMI, IPSC BS
Ringing group #81 7681 #81 – U, V, RH H – AN, DIG, ENT, X RK,
off - all mem- T S0, CMI, IPSC BS
bers removed
Ringer cutoff – – *98 – V, T RH U1 Local DIG, IPSC X RK, A short advisory
on feature BS tone is activated.
The optical signals
are retained.
Ringer cutoff – – #98 – V, T RH U1 Local DIG, IPSC X RK,
off feature BS
Hunt group, *85 7585 *85 – V, T RH U1 Fea- AN, DIG, ENT, X RK, All hunt groups, join
join ture S0, CMI, IPSC BS = *85*
menu
Hunt group, #85 7685 #85 – V, T RH U1 Fea- AN, DIG, ENT, X RK, All hunt groups,
leave ture S0, CMI, IPSC BS leave = #85#
menu
Service menu – – – X, – – – – DIG, IPSC – BS Service key as for
T stopping and start-
ing procedure
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Remote ser- *994+In- 75944 *994 – – – U1 – AN, DIG, ENT, – –

vice call dex+Suffix dial- S0, CMI, IPSC
ing
Silent monitor- *944+Stn. no. *944.. – – – – – AN, DIG, ENT, X WA, Only for selected
ing CMI RG, countries and for
BS, authorized stations
RK
Trunk flash on *51 – *51 – V – H – AN, DIG, ENT, X –
analog trunk CMI, IPSC
Silent ringing, –
see ringer cut-
off
Language se- – – *48 At login IPSC –
lection
Substitution 75 75 75 – – – – – ALL – –
code for ‘*’
Substitution 76 76 76 – – – – – ALL – –
code for ‘#’
System ad- – – *95... – – – H – DIG, IPSC See WA, Only for authorized
ministration notes RG, stations via access
RK, code.
BS User data is pro-
tected via tele-
phone lock feature.
System ad- – – *991... – – – – – DIG, IPSC – WA,
ministration, RG,
remote DTMF RK,
administration BS
and mainte-
nance, enable
(service sys-
tem)
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
System ad- – – *992... – – – – – DIG, IPSC – WA, Only for authorized

ministration, RG, stations via access
remote DTMF RK, code.
administration BS
and mainte-
nance, enable
(customer sys-
tem)
Enable system – – *993 ... – – – – – DIG, IPSC – WA, Only for authorized
administration RG, stations via access
via HOST (al- RK, code.
so remote) BS
Key program- – – *91... – – – H Local DIG, IPSC X RK,
ming GS
Toll fraud mon- – – – – – – – – DIG, IPSC X – Only for attendant,
itoring if enabled
Internal – – *54 – V RH, – Private DIG, IPSC –
phonebook BR, (local
GS directo-
ry on
PC) +
LDAP
inter-
face
Telephone *42 7542 *42 – U,V – H – AN, DIG, ENT, – RK,
data service S0, CMI, IPSC BS
(TDS)
Activate timed *46+time 7546... *46.. – U, V, – H – AN, DIG, ENT, X –
reminder T S0, CMI, IPSC
Deactivate #46+time 7646... #46.. – U, V, – H – AN, DIG, ENT, X
timed remind- T S0, CMI, IPSC
er
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Trace Stop *509 – *509 – V – – – AN, DIG, ENT, – –

S0, CMI, IPSC
Disconnect – – – – V – – Local ALL – –
key active
menu,
key
Enable door *89+Stn. 7589 *89... – U, V, – H – AN, DIG, ENT, X –
opener, DTMF no.+Code T S0, CMI, IPSC
Disable door #89+Stn. 7689 #89... – U, V, – H – AN, DIG, ENT, X –
opener, DTMF no.+Code T S0, CMI, IPSC
Door opener *61+Stn. no. 7561 *61... – U, V GS H – AN, DIG, ENT, – – Only if entrance
via adapter S0, CMI, IPSC telephone is config-
box ured
Transfer – ECT – – – RG, – Drag& AN, DIG, ENT, – – IPSI only support
(screened/un- (local S0 GS Drop, S0, CMI, Transfer after mes-
screened) WpC Menu IPSC, IPSI saging.
function- Key
ality)
Call pickup, di- *59+Stn. no. 7559... *59... – U – H Using AN, DIG, ENT, – WA,
rected status- S0, CMI, IPSC RG,
sup- RK,
ported BS
speed
dialing
keys
Call pickup in *57 7557 *57 – V RH, U – AN, DIG, ENT, – WA,
pickup group BR, S0, CMI, IPSC RG,
GS RK,
BS
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Pick up DTMF: Flash – – – – GS – AN, DIG, ENT, – –

TDM WpC with- S0, CMI, IPSC
out display:
Consultation
hold key
Call forward- *495 75495 *495 – V, T RH U1 Fea- AN, DIG, ENT, X RK,
ing no reply ture S0, CMI, IPSC BS
(CFNR) on key
Call forward- #495 76495 #495 – V, T RH U1 Fea- AN, DIG, ENT, X RK,
ing no reply ture S0, CMI, IPSC BS
(CFNR) off key
Extending un- – – – – – WA – – DIG – – Only for authorized
dialed lines stations
AC call (see 9 (ROW) 9 (ROW) 9 – – – – 9 ALL – –
numbering 0 (USA) 0 (USA) (ROW (ROW)
plan) ) 0
0 (USA)
(USA)
Number redial Redial key – – X – – – Local AN, DIG, ENT, X – Cannot be pro-
feature S0, CMI, grammed under
IPSC, IPSI DSS.
Retrieval of *63+Trunk code 7563.. *63.. – V – H Local AN, DIG, ENT, – – Retrieval also pos-
external call feature S0, CMI, IPSC sible with trunk key
placed on menu
common hold
Central tele- *943+Stn. no.+ 75943.. *943.. – U – H – AN, DIG, ENT, X Only for authorized
phone lock * or # S0, CMI, IPSC stations
Abbreviations:
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm

TDM work-
point clients
S0 work- display,
Feature Note
ations in
Key Menu
Table B-2)
Programmable
locking on
procedure
lock code
Code +
Status
Code
Code
Code
Service
via
Dialog
Fixed
bar
Return to held *0 or Retrieve *0 – – BR, U1 Mouse AN, DIG, ENT,

call (exclusive CMI, DTMF: WA, click, S0, CMI,
hold off) Flash RG, key IPSC, IPSI
TDM WpC with- GS,
out display: BS
Consultation
hold key
Abbreviations:
1 The codes are valid for DTMF telephones. Substitution codes 75 and 76 must be entered instead of “*” and “#” for DP
telephones.
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm
Description of the different workpoint client groups from Table B-1
Table B-2 Description of the Different Workpoint Client Groups
Workpoint client group Description/examples Abbreviation

All workpoint clients All workpoint clients listed below ALL
TDM workpoint clients without dis- ● optiPoint 500 entry ENT
play ● optiset E entry
● optiset E basic
TDM workpoint clients with display ● optiPoint 500 economy (not for U.S.) DIG
● optiPoint 500 basic
● optiPoint 500 standard
● optiPoint 500 advance
● optiPoint 600 office (in UP0/E mode)
● optiset E standard
● optiset E advance plus/comfort
● optiset E advance conference/conference
● optiset E memory
analog workpoint clients DP and DTMF terminals AN
S0 workpoint clients ISDN terminals S0
IP workpoint clients ● System clients: IPSC
– optiClient 130
– optiPoint 400 standard
– optiPoint 400 economy
– optiPoint 410 entry (without display)
– optiPoint 410 economy plus
– optiPoint 420 economy plus
● H323 clients: IPH3
– MS Windows NetMeeting
● SIP clients: IPSI
– optiPoint 410 entry S
– optiPoint 410 economy S
– optiPoint 410 economy plus S
– optiPoint 410 standard S
– optiPoint 410 advance S
– optiPoint 420 economy S
– optiPoint 420 economy plus S
– optiPoint 420 standard S
– optiPoint 420 advance S
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm
Table B-2 Description of the Different Workpoint Client Groups
Workpoint client group Description/examples Abbreviation

CMI mobile phones Gigaset 1000 CMI
CMI feature mobile phones ● Gigaset 3000 Comfort
● Gigaset 3000 Micro
● Gigaset 4000 Comfort
● Gigaset 4000 Micro
● Gigaset S1 professional
● Gigaset SL1 professional
● Gigaset M1 professional
● Gigaset active M
● Gigaset active EX
A31003-H3570-S100-6-7620, 2008-04-01
fcodes.fm
A31003-H3570-S100-6-7620, 2008-04-01
portnos_V7.fm
Nur für den internen GebrauchIP Protocols and Port Numbers Used with HiPath 3000/5000
C IP Protocols and Port Numbers Used with

HiPath 3000/5000 V7
The following tables provide information about the components of HiPath 3000/5000 V7 that
are needed for firewall configuration. Firewalls protect customer-internal intranets against out-
side attacks.
The following tables contain extracts from

> ●
●
Product-Specific Data Sheet for HiPath Network Analysis: HiPath 5000 V7
Product-Specific Data Sheet for HiPath Network Analysis: HG 1500 V7
The tables are only available in English.
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual C-1
Product Specific Attributes
HiPath 5000 V7
2 Services and Ports

2.1 Voice Traffic and Signaling
2.1.1 HiPath 5000
HiPath 5000 uses for communication on the network the following services and ports:
Important: Except the UDP-Ports for the Voice payload the port numbers listed cannot be changed
in the product.
Explanation:
A-Prot. Application-Layer-Protocol
M-Prot. Middleware-Layer-Protocol
T-Prot. Transport-Layer-Protocol
D-Ports Default-Ports are the port numbers or the port range which comes in effect after turning
power on the first time – without administration.
A-Ports Admin-Ports are the alternative port numbers or the port range in which the ports can be
altered by administration.
M- D- A-
Application Function Type A-Prot. T-Prot. Remarks
Prot. Ports Ports
Centralised Administration - Functions provided by the system for DBFS access

Def: FCT
FCT 1-
. server FCT API --- TCP 7100 Adm: Default can be modified within
Interface to DBFS 65535
this range
REG Client
1024 -
. Registration of HG1500 at client REG --- TCP Def: Ephemeral Ports (IANA)
65535
DBFS
Def: SYNC
SYNC 1-
. server SYNC --- TCP 7024 Adm: Default can be modified within
Interface to DBFS 65535
this range
Centralised Ressource Management - Mangement of networkwide Ressources (conference, MOH)

Def: IPNC
IPNC 1-
. server MCP --- TCP 12051 Adm: Default can be modified within
MediaGatewaycontrol 65535
this range
RM client
Resource manager for 1024 -
. client RM API --- TCP Def: Ephemeral Ports (IANA)
networkwide use of MOH 65535
and Conference
RM server
Def: RM
Resource manager for 1-
. server RM API --- TCP 9000 Adm: Default can be modified within
this range
and Conference
CSTA - CSTA access

Def: CSTA
1-
. CSTA Access server CSTA API --- TCP 7001 Adm: Default can be modified within
65535
this range
Customer License Agent (CLA)

CLA Discovery CLA
Def: UDP CLA detection Port on
. multicast listener for CLA server CLADP --- UDP 23232
multicast address 224.0.23.23
detection by CLM
th
Issue: 18 April 2007 Page - 4 -
Siemens Enterprise Communications GmbH & Co KG
HiPath 5000 V7
M- D- A-
Prot. Ports Ports
Def: Port will be discovered by CLM
CLA-Service CLA service TCP -
. server XML --- 61740 through multicast procedure. CLC
port for CLC / CLM SSL
uses port by configuration.
Customer License Client (CLC)

CLA Connectivity (CLC) Def: Port will be discovered by CLM
TCP -
. Used for data transfer client HLP --- 61740 through multicast procedure. CLC
SSL
between CLC / CLM uses port by configuration.
Customer License Manager (CLM) Web basierte Applikation zur Verwaltung von HiPath Lizenzen in der Kundeninfrastruktur
CLA Connectivity (CLM) Def: Port will be discovered by CLM
TCP -
. Used for data transfer client XML --- 61740 through multicast procedure. CLC
SSL
between CLA / CLM uses port by configuration.
CLM Shutdown port Tomcat
Def: Shutdown port (Tomcat) of
. shut down port provided by server TSP --- TCP 8820
License Manager
CLM setup
CLS Connectivity (CLM) Def: Port selected by the TCP/IP-
0-
. Interface to Central License client SOAP HTTPS TCP implementation of the underlying
65535
Server (CLS) operating system
HTTP based Management
Def: HTTP port of License Manager
Access (CLM) Web based 1025 -
. server HTTP --- TCP 8819 Adm: Default can be modified within
Interface of Customer 65535
this range during Setup or later (CLM)
License Manager
HTTPS based Management
Def: HTTPS port of License Manager
Access (CLM) Secured 1025 -
. server HTTPS --- TCP 8818 Adm: Default can be modified within
Web based Interface of 65535
this range during Setup or later (CLM)
Customer License Manager
DBFS - Feature Server for centralized administration

CAR Server (DBFS) CAR Def: CAR Server
1-
. componennt for centralized server CAR --- TCP 12063 Adm: Default can be modified within
65535
administration this range
REG Server Def: REG
1-
. Registration of HG1500 with server REG --- TCP 12061 Adm: Default can be modified within
65535
DBFS this range
VSYNC client (DBFS) Client
for database 1024 -
. client SYNC --- TCP Def: Ephemeral Ports (IANA)
synchronisation betwwen 65535
DBFS and H2/3/5k
H.323 Networking
CAR client
1024 -
. Call address resolution client CAR --- TCP Def: Ephemeral Ports (IANA)
65535
client
CAR-Alive Client 1024 -
. client CAR Alive --- TCP Def: Ephemeral Ports (IANA)
Alivechecks (configurable) 65535
Def: CAR
CAR-alive server 1-
. server CAR Alive --- TCP 12062 Adm: Default can be modified within
Alive checks (configurable) 65535
this range
H.323 Call Signaling H.323 12250 Def: H.323
1-
. active VoIP client (H.225- --- TCP - Adm: Default can be modified within
65535
Verbindungssteuerung Q.931) 12950 this range
H.323 Call Signaling H.323 Def: H.225/Q.931
1-
. passive Voice over IP: server (H.225- --- TCP 1720 Adm: Default can be modified within
65535
Verbindungssteuerung Q.931) this range
RAS client H.323
1024 -
. RAS client for registration at client (H.225- --- UDP Def: Ephemeral Ports (IANA)
65535
external gatekeeper RAS)
RM client
and Conference
H.323 Subscriber
th
HiPath 5000 V7
M- D- A-
Prot. Ports Ports
H.225 RAS H.323 Def: H.225/RAS
1-
. RAS server for H.323 server (H.225- --- UDP 1719 Adm: Default can be modified within
65535
endpoints RAS) this range
H.245 Media Signaling
12250 Def: H.323
active H.245 channel H.323 1-
. client --- TCP - Adm: Default can be modified within
signalling for H.323 (H.245) 65535
12950 this range
endpoints
12250 Def: H.323
passive H.245 channel H.323 1-
. server --- TCP - Adm: Default can be modified within
signalling for H.323 (H.245) 65535
12950 this range
endpoints
H.323
1-
. H.323 Call Signaling server (H.225- --- TCP 4711 Adm: Default can be modified within
65535
Q.931) this range
1-
65535
1-
65535
HFA subscriber
Def: CorNet-TC
1-
. Cornet TC server Cornet-TC --- TCP 4060 Adm: Default can be modified within
65535
this range
1-
65535
1-
65535
MS-SQL Server
MS-SQL_Server-TCP
. server MS-SQL --- TCP 1433
MS-SQL Server
MS-SQL_Server-UDP
. server MS-SQL --- UDP 1434
Microsof SQL Server
SIP networking
CAR client
1024 -
. Call address resolution client CAR --- TCP Def: Ephemeral Ports (IANA)
65535
client
CAR-Alive Client 1024 -
. client CAR Alive --- TCP Def: Ephemeral Ports (IANA)
Alivechecks (configurable) 65535
Def: CAR
CAR-alive server 1-
. server CAR Alive --- TCP 12062 Adm: Default can be modified within
Alive checks (configurable) 65535
this range
SIP Call Signalling active
(symmetric UDP) Call
. client SIP --- UDP 5060 Def: SIP
Signalling for SIP endpoints
and SIP based trunking
(TCP) Call Signalling for 1024 -
. client SIP --- TCP Def: Ephemeral Ports (IANA)
SIP endpoints and SIP 65535
based trunking
SIP Call Signalling passive
Def: SIP
Call Signalling for SIP 1-
. server SIP --- TCP_UDP 5060 Adm: Default can be modified within
endpoints and SIP based 65535
this range
trunking
SIP subscriber
(symmetric UDP) Call
Signalling for SIP endpoints
and SIP based trunking
th
HiPath 5000 V7
M- D- A-
Prot. Ports Ports
(TCP) Call Signalling for 1024 -
. client SIP --- TCP Def: Ephemeral Ports (IANA)
SIP endpoints and SIP 65535
based trunking
SIP Call Signalling passive
Def: SIP
Call Signalling for SIP 1-
. server SIP --- TCP_UDP 5060 Adm: Default can be modified within
endpoints and SIP based 65535
this range
trunking
th
HiPath 5000 V7
2.1.2 IP- Clients
2.1.2.1 optiClient 130 V5.1 R5
M- T- D-
Application Function Type A-Prot. A-Ports Remarks
Prot. Prot. Ports
HFA Client
Def: CorNet-TC
. Cornet TC server Cornet-TC --- TCP 4060 1 - 65535 Adm: Default can be
modified within this range
H.323 Call Signaling H.323 Def: H.323
12250 -
. active VoIP client (H.225- --- TCP 1 - 65535 Adm: Default can be
12950
Verbindungssteuerung Q.931) modified within this range
H.323 Call Signaling
H.323
(MDW_MSA) Voice over
. server (H.225- --- TCP 1720 Def: H.225/Q.931
IP:
Q.931)
Verbindungssteuerung
IP: H.323 12000 - Def: H.245 portnumber is
. server --- TCP
Verbindungssteuerung (H.245) 12100 negotiated via H.225
für Sprachkanäle
(Mediachannels)
Def: RTP portnumber is
negotiated via H.245. Max
RTP Payload Transport 30 connections: RTP
29100 -
. active VoIP client RTP_RTCP --- UDP 1 - 65535 starts at <adr>, RTCP at
29159
Payloadtransport <adr>+1 (=RTP+1).
Adm: Default can be
29100 -
. passive VoIP server RTP_RTCP --- UDP 1 - 65535 starts at <adr>, RTCP at
29159
payloadtransport <adr>+1 (=RTP+1).
Adm: Default can be
LDAP Connectivity (client sided) client sided connectivity to a LDAP Service

LDAP Access Directory 1024 - Def: Ephemeral Ports
. client LDAP --- TCP
access via LDAP 65535 (IANA)
DLC Connectivity (DLS client sided) client sided connectivity to Deployment Licence Service
DLS contact me
request (optiClient
sided) workpoint sided server HTTP --- TCP 8082 Def: HTTP optiClients
DLS contact me
service
DLS Detection (DHCP)
. DLS detection via client DHCP --- UDP 68 Def: DHCP Client Port
DHCP
Def: Unspecified Default
Port(range) values
DLS Detection (DNS) 1024 -
. client DNS --- UDP Adm: PortLow/PortHigh
DLS detection via DNS 65535
can be modified within
this range ()
DLS Workpoint
Interface (optiClient Def: DLS: Communication
. sided) workpoint sided client WPIP HTTPS TCP 18443 interface workpoints –
DLS Communication DLS
interface workpoints
HFA Client (HiPath 3000) HFA client at HiPath 3000
th
HiPath 5000 V7
M- T- D-
Prot. Prot. Ports
Def: CorNet-TC
Cornet TC (HG1500) 1-
server Cornet-TC --- TCP 4060 Adm: Default can be
Cornet TC 65535
H.323 Call Signaling Def: H.323
12250 - 1-
(HG1500) active VoIP client H.323 (H.225-Q.931) --- TCP Adm: Default can be
12950 65535
Verbindungssteuerung modified within this range
(MDW_MSA) Voice
server H.323 (H.225-Q.931) --- TCP 1720 Def: H.225/Q.931
over IP:
(MDW_MSA) Voice
over IP: 12000 - Def: H.245 portnumber is
server H.323 (H.245) --- TCP
Verbindungssteuerung 12100 negotiated via H.225
f?r Sprachkan?le
(Mediachannels)
negotiated via H.245.
RTP Payload
Max 30 connections: RTP
Transport (HG1500) 29100 - 1-
client RTP_RTCP --- UDP starts at <adr>, RTCP at
active VoIP 29159 65535
<adr>+1 (=RTP+1).
Payloadtransport
Adm: Default can be
RTP Payload
Transport (HG1500) 29100 - 1-
server RTP_RTCP --- UDP starts at <adr>, RTCP at
passive VoIP 29159 65535
<adr>+1 (=RTP+1).
payloadtransport
Adm: Default can be
HLM Connectivity (client sided) client sided HiPath Licence Management

TCP -
SSL

LDAP Access Directory 1024 -
. client LDAP --- TCP Def: Ephemeral Ports (IANA)
access via LDAP 65535
th
HiPath 5000 V7
2.1.2.2 optiPoint 410/420 SIP V5 R0
M- D- A-
Prot. Ports Ports
OAM (oP410 SIP) Administration of optiPoint SIP devices

DHCP-Client (op410)
Server of "Dynamic
. client DHCP --- UDP 68 Def: DHCP Client Port
Host Configuration
Protocol"
DHCP-Server (oP410)
Server of "Dynamic
. server DHCP --- UDP 67 Def: DHCP Server Port
Host Configuration
Protocol"
DLS Workpoint
Interface (client sided)
0 - Def: DLS: Communication interface
. workpoint sided DLS client WPIP HTTPS TCP 18443
65535 workpoints – DLS
Communication
. DNS DNS relay server DNS --- TCP_UDP 53 Def: DNS
FTP_Server_Control
. server FTP --- TCP 21 Def: FTP-Server Control Port
(oP410) FTP-Server
HTTPS_Server
(Phones) Secure 0-
. server HTTP --- TCP 443 Def: HTTPS
Embedded Web 65535
Server
HTTP_Server
0-
. (Phones) Web server TFTP --- TCP 8085 Def: HTTP optiPoints, HG1500
65535
Interface
IP-Config (Phones) IP
. server *proprietary* --- UDP 5100
Configuration Services
SNMP (SET/GET)
. (Phones) SNMP server SNMP --- UDP 161 Def: SNMP (Set/Get)
SET/GET-Functionality
SNMP Trap (oP410) 161
. client SNMP --- UDP Def: SNMP Trap (oP410)
SNMP Trap function 162
SNTP (oP410) Simple
. server SNTP --- UDP 123 Def: SNTP
Network Time Protocol
SNTP heartbeat
. (oP410) Simple server SNTP --- UDP 580
QoS Data Collection Unit (QCU) phones Send QoS reports

QCU client 12010
Client application 0-
. client SNMP --- UDP 12010 Def: QCU receiving Port
which sends QDC data 65535
to the QCU
SIP payload transport (op410 SIP) Session Inition Protocol (SIP) payload
Def: Port 5004 .. 5006 for normal usage.
SIP Payload Transport For every line-key you have to add two
(oP410) active Voice 5004 - 0 - channels. The maximum of line keys are
. client RTP_RTCP --- UDP
over IP: Transmission 5027 65534 10 -->. For this the maximum range of
of Payload 5004 .. 5027 is valid
Adm: even port number only
SIP Payload Transport For every line-key you have to add two
(oP410) passive Voice 5004 - 0 - channels. The maximum of line keys are
. server RTP_RTCP --- UDP
over IP: Transmission 5027 65534 10 -->. For this the maximum range of
of Payload 5004 .. 5027 is valid
SIP Signalling (op410 SIP) Session Inition Protocol (SIP) signaling

SIP Signaling (WL2- TCP -
. client SIP --- 5061 Def: SIP
Phone) SIP over TLS TLS
th
HiPath 5000 V7
M- D- A-
Prot. Ports Ports
SIP signaling TCP
(oP410) SIP signalling
. in the case of using client SIP --- TCP 5060 Def: SIP
TCP (configurable
inside the phone)
SIP signaling UDP
(oP410) SIP signalling
. in the case of using client SIP --- UDP 5060 Def: SIP
UDP (configurable
inside the phone)
Def: SIP
SIP-TLS (OP410) SIP TCP - 1 - Adm: Configuration the port value to zero
. client SIP --- 5061
over TLS TLS 65535 will result in the default port value being
used
User Applications (oP410 SIP) bundle of user functions

JAVA (optiPoints)
0-
. JAVA applications in client HTTP --- TCP 9200 Def: Java default port in optiPoint phones
65535
phones
LDAP Access
(optiPoint phones) 0-
. client LDAP --- TCP 389 Def: LDAP
Directory access via 65535
LDAP
WAP client (TCP) for
0 - Def: WAP connectionless session service
. WAP access to WAP client WAP --- TCP 9200
65535 (IANA)
services (server)
th
HiPath 5000 V7
2.1.2.3 optiPoint 410/420 V5 R3
M- T- D- A-
Application Function Type A-Prot. Remarks
Prot. Prot. Ports Ports
H.323 (oP410) General term for H.323 functions

H.323 Call Signaling H.323
1024 -
. (oP410) client (H.225- --- TCP Def: Ephemeral Ports (IANA)
65535
active Voice over IP Q.931)
0-
. (oP410) server (H.225- --- TCP 1720 Def: H.225/Q.931
65535
passive Voice over IP Q.931)
Def: RTP portnumber is negotiated via
H.245. Max 5 connections: RTP starts at
H.323 Payload Transport
5004 - 0 - <adr> port2/max - 1 down to <adr> port
. (oP4x0 at H2k/H3k) client RTP_RTCP --- UDP
5013 65534 1/min , RTCP at <adr> port2/max down to
active Voice over IP
<adr> port 1/min+1
5004 - 0 - H.245. Max 5 connections: RTP starts at
. (oP4x0 at H2k/H3k) server RTP_RTCP --- UDP
5013 65534 <adr>, RTCP at <adr>+1 (=RTP+1).
passive Voice over IP
Def: Attention: The phone is prepared to
handle up to 5 port couples in total. If the
base port is set to 5004 inside the phone,
5008 - 0 - the port range then is 5004 ... 5013. But, in
. (oP4x0 at H4k) client RTP_RTCP --- UDP
5013 65534 H4k scenarios, only the upper three couples
(starting from the top) are used: 5012/5013,
5010/5011 and 5008/5009 .
5008 - 0 - the port range then is 5004 ... 5013. But, in
. (oP4x0 at H4k) server RTP_RTCP --- UDP
5013 65534 H4k scenarios, only the upper three couples
passive Voice over IP
(starting from the top) are used: 5012/5013,
5010/5011 and 5008/5009 .
HFA (oP410) Hicom Feature Access

CorNet TC Logon
. (oP600) CorNet TC client *proprietary* --- TCP 4060 Def: CorNet-TC
Logon Port
OAM (oP410 HFA) Administration of optiPoint HFA devices

DLS Workpoint Interface
(client sided) workpoint
. sided DLS client WPIP HTTPS TCP 18443
Communication interface
workpoints
FTP_Server_Control
(oP410) FTP-Server
HTTPS_Server (Phones)
0-
. Secure Embedded Web server HTTP --- TCP 443 Def: HTTPS
65535
Server
HTTP_Server (Phones) 0-
. server TFTP --- TCP 8085 Def: HTTP optiPoints, HG1500
Web Interface 65535
SNMP (SET/GET)
th
HiPath 5000 V7
M- T- D- A-
QoS Data Collection Unit (QCU) phones Send QoS reports,

QCU client 12010 Client
0-
. application which sends client SNMP --- UDP 12010 Def: QCU receiving Port
65535
QDC data to the QCU
User Applications (oP410 HFA) bundle of user functions of HFA phone oP410
CTI Service (TCP) CTI
. client Cornet TS --- TCP 5105 Def: CTI Service oP410
Service in oP410
JAVA (optiPoints) JAVA 0-
. client HTTP --- TCP 9200 Def: Java default port in optiPoint phones
applications in phones 65535
LDAP Access (optiPoint
0-
. phones) Directory client LDAP --- TCP 389 Def: LDAP
65535
access via LDAP
65535 (IANA)
services (server)
th
HiPath 5000 V7
2.1.2.4 optiPoint WL2 professional V1.0 HFA Variant
M- T- D- A-
H.323 (WL2) General term for H.323 functions

1024 -
. (WL2) client (H.225- --- TCP Def: Ephemeral Ports (IANA)
65535
active Voice over IP Q.931)
1-
. (WL2) server (H.225- --- TCP 1720 Adm: Default can be modified within this
65535
passive Voice over IP Q.931) range
5004 - Def: RTP portnumber : RTP starts at <adr>,
. (WL2) client RTP_RTCP --- UDP
5011 RTCP at <adr>+1 (=RTP+1).
H.323 Payload Transport Def: RTP portnumber is negotiated via
5004 -
. (WL2) passive Voice server RTP_RTCP --- UDP H.245. Max 5 connections: RTP starts at
5013
over IP <adr>, RTCP at <adr>+1 (=RTP+1).
HFA (WL2) Hicom Feature Access

CorNet TC Logon (WL2)
. client *proprietary* --- TCP 4060 Def: CorNet-TC
CorNet TC Logon Port
LDAP WL2 LDAP access for phones

LDAP Access (WL2)
0-
. Directory access via client LDAP --- TCP 389 Def: LDAP
65535
LDAP
OAM (WL2) Administration of optiPoint HFA devices

DHCP-Client (WL2)
. Server of "Dynamic Host client DHCP --- UDP 68 Def: DHCP Client Port
Configuration Protocol"
DHCP-Server (WL2)
. Server of "Dynamic Host server DHCP --- UDP 67 Def: DHCP Server Port
Configuration Protocol"
DLS Workpoint Interface
(WL2) (client sided)
1024 - 0-
. workpoint sided DLS client WPIP HTTPS TCP Def: Ephemeral Ports (IANA)
65535 65535
Communication interface
workpoints
HTTPS Server (WL2)
. Secure Embedded Web server HTTP --- TCP 443 Def: HTTPS
Server
HTTP Server (WL2) Web
Interface
IP-Config (WL2) Service
Agent Reque
SNMP (SET/GET) (WL2)
. SNMP SET/GET- server SNMP --- UDP 161 Def: SNMP (Set/Get)
Functionality
SNMP (Traps) (WL2)
. client SNMP --- UDP 162 Def: SNMP (Traps)
active SNMP Traps
Telnet (WL2) Telnet-
. server Telnet --- TCP 23 Def: Telnet
Server

QCU client 12010 Client
0-
. application which sends client SNMP --- UDP 12010 Def: QCU receiving Port
65535
QDC data to the QCU
th
HiPath 5000 V7
2.2 Administration and Diagnosis
The following services are needed for administration and diagnosis in addition to those listed in
chapter Voice Traffic and Signaling
OAM (H5k) Adminstration and Maintenance HiPath 5000

Def: ADM
ADM 1-
ADM (H2/3/5k) Interface to DBFS server --- TCP 7000 Adm: Default can be modified
API 65535
within this range
HTTP client (HG1500) used for multi
1024 -
gateway administratrion feature client HTTP --- TCP Def: Ephemeral Ports (IANA)
65535
(MGAF)
HTTP Server (HG1500) HTTP
server HTTP --- TCP 8085 Def: HTTP optiPoints, HG1500
Server for WBM access
HTTPS client used for multi gateway HTTP TCP - 1024 -
client --- Def: Ephemeral Ports (IANA)
administration feature (MGAF) S SSL 65535
HTTPS Server (HG1500) Secure HTTP TCP -
server --- 443 Def: HTTPS
Web Server S SSL
LDAP Client LDAP client used for TCP_UD 1024 -
client LDAP --- Def: Ephemeral Ports (IANA)
centraliced directory service P 65535
SNMP (SET/GET) (H2/3/5k/HG1500)
server SNMP --- UDP 161 Def: SNMP (Set/Get)
SNMP Set/Get
SNMP (Traps) (H2/3/5/HG1500) 1024 -
client SNMP --- UDP Def: Ephemeral Ports (IANA)
SNMP Erromessages 65535
SNMP (Traps) (HG1500) Receiving
server SNMP --- UDP 162 Def: SNMP (Traps)
of SNMP-Traps
SNTP Client (H2/3/5k/BizIP) Simple 1024 -
client SNTP --- UDP Def: Ephemeral Ports (IANA)
Network Time Protocol 65535
TFTP Client (H2/3/5k) APS-Transfer/ 1024 -

client TFTP --- UDP Def: Ephemeral Ports (IANA)
KDS-Sicherung mit TFTP 65535
TFTP Server (H2/3/5k,BizIP) TFTP

server TFTP --- UDP 69 Def: TFTP
Server for CDR
SW_Manager (H5k) HiPath Software Manager

Def: HTTPS port of SW-
SW-Man Secured Web Access Manager, DB Feature Server
from a Client Browser HTTPS server HTTPS --- TCP 8443 0 - 65535 Adm: Default can be modified
Interface of SW-Manager within this range via server.xml
file in Tomcat's "conf" directory
Def: Shutdown port of SW-
Manager
SW-Man Tomcat Shutdown Used *proprietar
server --- UDP 8279 0 - 65535 Adm: Default can be modified
to shutdown Tomcat y*
within this range via server.xml
Def: HTTP port of SW-
SW-Man Web Access from a Client Manager
Browser HTTP Interface of SW- server HTTP --- TCP 8280 0 - 65535 Adm: Default can be modified
Manager within this range via server.xml
X-Trace (H2/3/5k) Access for X-Tracer

Online Trace (H2/3/5k) Online
server XTP --- TCP 21965 Def: X-Tracer
Trace Port (X-Tracer)
X-Trace (HG1500) Access for X-Tracer
Online Trace (HG1500) Acces to X- 204

server XTP TCP Def: XTrace
Trace 8
th
HiPath HG 1500 V7
2 Services and Ports

2.1 Voice Traffic and Signaling
2.1.1 HG1500
HiPath HG 1500 uses for communication on the network the following services and ports:
Important: Except the UDP-Ports for the Voice payload the port numbers listed cannot be changed
in the product.
Explanation:
A-Prot. Application-Layer-Protocol
M-Prot. Middleware-Layer-Protocol
T-Prot. Transport-Layer-Protocol
D-Ports Default-Ports are the port numbers or the port range which comes in effect after turning
power on the first time – without administration.
A-Ports Admin-Ports are the alternative port numbers or the port range in which the ports can be
altered by administration.
M- T- D- A-
Accounting Server (HG1500) IP-Accounting
Accounting Server
. server ACP --- TCP 13042 Def: Accounting
IP-Accounting
Decomposed Media Gateway - Signalling for decomposed media gateway in HiPath3000

Def: IPNC
IPNC 1-
. server MCP --- TCP 12051 Adm: Default can be modified
MediaGatewaycontrol 65535
within this range
Def: MPH
MPH 1-
. server MCP --- TCP 12052 Adm: Default can be modified
MediaPayloadHandler 65535
within this range
DSL-Diagnose Server - DSL-Statusanzeige

DSL-Diagnose Server 1- Adm: Default can be modified
. server DSL-D --- UDP 12200
DSL-Statusanzeige 65535 within this range
H.323 Networking
CAR client
1024 -
. Call address client CAR --- TCP Def: Ephemeral Ports (IANA)
65535
resolution client
CAR-Alive Client
1024 -
. Alivechecks client CAR Alive --- TCP Def: Ephemeral Ports (IANA)
65535
(configurable)
CAR-alive server Def: CAR
1-
. Alive checks server CAR Alive --- TCP 12062 Adm: Default can be modified
65535
(configurable) within this range
CAR_Alive w. Ping
. Ping based check peer ICMP-Echo --- ICMP
Port(range) values
alive mechanism
12250 - 1-
. active VoIP client (H.225- --- TCP Adm: Default can be modified
12950 65535
Verbindungssteuerung Q.931) within this range
th
HiPath HG 1500 V7
M- T- D- A-
1-
. passive Voice over IP: server (H.225- --- TCP 1720
65535
Adm: Default can be modified
RAS client
H.323
RAS client for 1024 -
. registration at external
client (H.225- --- UDP
65535
Def: Ephemeral Ports (IANA)
RAS)
gatekeeper
RM client
. networkwide use of
client RM API --- TCP
65535
Def: Ephemeral Ports (IANA)
MOH and Conference
RM server
Def: RM
. networkwide use of
server RM API --- TCP 9000
65535
within this range
MOH and Conference
Def: RTP portnumber is negotiated
RTP Payload via H.245. Max 30 connections:
Transport 29100 - 1- RTP starts at <adr>, RTCP at
. active VoIP
client RTP_RTCP --- UDP
29159 65535 <adr>+1 (=RTP+1).
Payloadtransport Adm: Default can be modified
within this range
via H.245. Max 30 connections:
RTP Payload
29100 - 1- RTP starts at <adr>, RTCP at
. Transport passive server RTP_RTCP --- UDP
29159 65535 <adr>+1 (=RTP+1).
VoIP payloadtransport
within this range
H.323 Subscriber
H.225 RAS H.323 Def: H.225/RAS
1-
. RAS server for H.323 server (H.225- --- UDP 1719
65535
endpoints RAS) within this range
Def: H.323
active H.245 channel H.323 12250 - 1-
. signalling for H.323
client
(H.245)
--- TCP
12950 65535
within this range
endpoints
Def: H.323
passive H.245 H.323 12250 - 1-
. channel signalling for
server
(H.245)
--- TCP
12950 65535
within this range
H.323 endpoints
H.323
1-
. H.323 Call Signalind server (H.225- --- TCP 4711
65535
Q.931) within this range
12250 - 1-
. active VoIP client (H.225- --- TCP
12950 65535
1-
65535
. active VoIP
29159 65535 <adr>+1 (=RTP+1).
within this range
. passive VoIP
server RTP_RTCP --- UDP
29159 65535 <adr>+1 (=RTP+1).
payloadtransport Adm: Default can be modified
within this range
HFA subscriber
Def: CorNet-TC
1-
. Cornet TC server Cornet-TC --- TCP 4060
65535
within this range
th
HiPath HG 1500 V7
M- T- D- A-
12250 - 1-
. active VoIP client (H.225- --- TCP
12950 65535
payloadtransport Q.931) within this range
1-
65535
payloadtransport Q.931) within this range
. active VoIP
29159 65535 <adr>+1 (=RTP+1).
within this range
. passive VoIP
server RTP_RTCP --- UDP
29159 65535 <adr>+1 (=RTP+1).
within this range
SIP networking
CAR client
1024 -
. Call address client CAR --- TCP Def: Ephemeral Ports (IANA)
65535
resolution client
CAR-Alive Client
1024 -
. Alivechecks client CAR Alive --- TCP Def: Ephemeral Ports (IANA)
65535
(configurable)
CAR-alive server Def: CAR
1-
. Alive checks server CAR Alive --- TCP 12062 Adm: Default can be modified
65535
(configurable) within this range
CAR_Alive w. Ping
. Ping based check peer ICMP-Echo --- ICMP
Port(range) values
alive mechanism
RM client
networkwide use of 65535
MOH and Conference
RM server
Def: RM
. server RM API --- TCP 9000 Adm: Default can be modified
networkwide use of 65535
within this range
MOH and Conference
active VoIP 29159 65535 <adr>+1 (=RTP+1).
within this range
passive VoIP 29159 65535 <adr>+1 (=RTP+1).
within this range
SIP Call Signalling
active (symmetric
. UDP) Call Signalling client SIP --- UDP 5060 Def: SIP
for SIP endpoints and
SIP based trunking
SIP Call Signalling
active (TCP) Call
1024 -
. Signalling for SIP client SIP --- TCP Def: Ephemeral Ports (IANA)
65535
endpoints and SIP
based trunking
SIP Call Signalling
Def: SIP
passive Call Signalling 1-
. server SIP --- TCP_UDP 5060 Adm: Default can be modified
for SIP endpoints and 65535
within this range
SIP based trunking
th
HiPath HG 1500 V7
M- T- D- A-
SIP Service Provider Trunk
within this range
within this range
SIP Call Signalling
active (symmetric
SIP based trunking
SIP Call Signalling
active (TCP) Call
1024 -
65535
endpoints and SIP
based trunking
SIP Call Signalling
Def: SIP
within this range
SIP based trunking
STUN (client) STUN Def: STUN client, Port depends on
1-
. client used for SIP client STUN --- UDP the client for which STUN request
65535
Provider access is sent
SIP subscriber
within this range
within this range
SIP Call Signalling
active (symmetric
SIP based trunking
SIP Call Signalling
active (TCP) Call
1024 -
65535
endpoints and SIP
based trunking
SIP Call Signalling
Def: SIP
within this range
SIP based trunking
VCAPI - Virtual Common (ISDN) Application Programming Interface

VCAPI
. server VCAPI --- TCP 12001 Def: VCAPI
VCAPI Server
VPN-IPSEC VPN tunnel
th
HiPath HG 1500 V7
M- T- D- A-
VPN-ESP (client)
IPSEC protocol for Def: NoPort assigned for this
. client IPSEC --- ESP 0
encrypted payload protocol
transport
VPN-ESP (server)
IPSEC protocol for Def: NoPort assigned for this
. server IPSEC --- ESP 0
encrypted payload protocol
transport
VPN-ISAKMP (client)
Internet Security
1024 -
. Association and Key client ISAKMP --- UDP Def: Ephemeral Ports (IANA)
65535
Management Protcol
for IPSEC
VPN-ISAKMP (server)
Internet Security
. Association and Key server ISAKMP --- UDP 500 Def: ISAKMP
Management Protcol
for IPSEC
VPN-NAT-T (client)
NAT treversal, IPSEC 1024 -
. client NAT-T --- UDP Def: Ephemeral Ports (IANA)
protocol for encrypted 65535
payload transport
VPN-NAT-T (server)
NAT treversal, IPSEC
. server NAT-T --- UDP 4500 Def: NAT-T
protocol for encrypted
payload transport
th
HiPath HG 1500 V7
2.1.2 IP- Clients
2.1.2.1 optiClient 130 V5.1 R5
M- T- D-
Prot. Prot. Ports
HFA Client
Def: CorNet-TC
. Cornet TC server Cornet-TC --- TCP 4060 1 - 65535 Adm: Default can be
12250 -
. active VoIP client (H.225- --- TCP 1 - 65535 Adm: Default can be
12950
Verbindungssteuerung Q.931) modified within this range
H.323
IP:
Q.931)
IP: H.323 12000 - Def: H.245 portnumber is
. server --- TCP
Verbindungssteuerung (H.245) 12100 negotiated via H.225
für Sprachkanäle
(Mediachannels)
29100 -
. active VoIP client RTP_RTCP --- UDP 1 - 65535 starts at <adr>, RTCP at
29159
Payloadtransport <adr>+1 (=RTP+1).
Adm: Default can be
29100 -
. passive VoIP server RTP_RTCP --- UDP 1 - 65535 starts at <adr>, RTCP at
29159
payloadtransport <adr>+1 (=RTP+1).
Adm: Default can be

LDAP Access Directory 1024 - Def: Ephemeral Ports
. client LDAP --- TCP
access via LDAP 65535 (IANA)
DLC Connectivity (DLS client sided) client sided connectivity to Deployment Licence Service
DLS contact me
request (optiClient
sided) workpoint sided server HTTP --- TCP 8082 Def: HTTP optiClients
DLS contact me
service
DLS Detection (DHCP)
. DLS detection via client DHCP --- UDP 68 Def: DHCP Client Port
DHCP
Port(range) values
DLS Detection (DNS) 1024 -
. client DNS --- UDP Adm: PortLow/PortHigh
DLS detection via DNS 65535
can be modified within
this range ()
DLS Workpoint
Interface (optiClient Def: DLS: Communication
. sided) workpoint sided client WPIP HTTPS TCP 18443 interface workpoints –
DLS Communication DLS
HFA Client
th
HiPath HG 1500 V7
M- T- D-
Prot. Prot. Ports
Def: CorNet-TC
1-
Cornet TC server Cornet-TC --- TCP 4060 Adm: Default can be
65535
H.323 Call Signaling Def: H.323
12250 - 1-
active VoIP client H.323 (H.225-Q.931) --- TCP Adm: Default can be
12950 65535
Verbindungssteuerung modified within this range
(MDW_MSA) Voice
server H.323 (H.225-Q.931) --- TCP 1720 Def: H.225/Q.931
over IP:
(MDW_MSA) Voice
over IP: 12000 - Def: H.245 portnumber is
server H.323 (H.245) --- TCP
Verbindungssteuerung 12100 negotiated via H.225
f?r Sprachkan?le
(Mediachannels)
RTP Payload
Transport 29100 - 1-
client RTP_RTCP --- UDP starts at <adr>, RTCP at
active VoIP 29159 65535
<adr>+1 (=RTP+1).
Payloadtransport
Adm: Default can be
RTP Payload
Transport 29100 - 1-
server RTP_RTCP --- UDP starts at <adr>, RTCP at
passive VoIP 29159 65535
<adr>+1 (=RTP+1).
payloadtransport
Adm: Default can be
HLM Connectivity (client sided) client sided HiPath Licence Management

TCP -
SSL

LDAP Access Directory 1024 -
. client LDAP --- TCP Def: Ephemeral Ports (IANA)
access via LDAP 65535
th
HiPath HG 1500 V7
2.1.2.2 optiPoint 410/420 SIP V5R0
M- T- D- A-
OAM (oP410 SIP) Administration of optiPoint SIP devices
DHCP-Client (op410)
Server of "Dynamic
Host Configuration
Protocol"
DHCP-Server
(oP410) Server of
. "Dynamic Host server DHCP --- UDP 67 Def: DHCP Server Port
Configuration
Protocol"
DLS Workpoint
Interface (client
sided) workpoint 0 - Def: DLS: Communication interface
. client WPIP HTTPS TCP 18443
sided DLS 65535 workpoints – DLS
Communication
. DNS DNS relay server DNS --- TCP_UDP 53 Def: DNS
FTP_Server_Control
(oP410) FTP-Server
HTTPS_Server
(Phones) Secure 0-
Embedded Web 65535
Server
HTTP_Server
0-
65535
Interface
IP-Config (Phones)
. IP Configuration server *proprietary* --- UDP 5100
Services
SNMP (SET/GET)
(Phones) SNMP
. server SNMP --- UDP 161 Def: SNMP (Set/Get)
SET/GET-
Functionality
SNTP (oP410)
. Simple Network Time server SNTP --- UDP 123 Def: SNTP
Protocol
SNTP heartbeat
(oP410) Simple
. server SNTP --- UDP 580
Network Time
Protocol
QoS Data Collection Unit (QCU) phones Send QoS reports

QCU client 12010
which sends QDC 65535
data to the QCU
SIP payload transport (op410 SIP) Session Inition Protocol (SIP) payload
SIP Payload
For every line-key you have to add two
Transport (oP410)
5004 - 0 - channels. The maximum of line keys are
. active Voice over IP: client RTP_RTCP --- UDP
5027 65534 10 -->. For this the maximum range of
Transmission of
5004 .. 5027 is valid
Payload
th
HiPath HG 1500 V7
M- T- D- A-
SIP Payload
For every line-key you have to add two
Transport (oP410)
5004 - 0 - channels. The maximum of line keys are
. passive Voice over server RTP_RTCP --- UDP
5027 65534 10 -->. For this the maximum range of
IP: Transmission of
5004 .. 5027 is valid
Payload
SIP Signalling (op410 SIP) Session Inition Protocol (SIP) signaling

SIP Signaling (WL2- TCP -
. client SIP --- 5061 Def: SIP
Phone) SIP over TLS TLS
SIP signaling TCP
(oP410) SIP
signalling in the case
. client SIP --- TCP 5060 Def: SIP
of using TCP
(configurable inside
the phone)
SIP signaling UDP
(oP410) SIP
signalling in the case
of using UDP
(configurable inside
the phone)
Def: SIP
SIP-TLS (OP410) TCP - 1 - Adm: Configuration the port value to
. client SIP --- 5061
SIP over TLS TLS 65535 zero will result in the default port value
being used
User Applications (oP410 SIP) bundle of user functions

JAVA (optiPoints)
0 - Def: Java default port in optiPoint
. JAVA applications in client HTTP --- TCP 9200
65535 phones
phones
LDAP Access
LDAP
0 - Def: WAP connectionless session
65535 service (IANA)
services (server)
th
HiPath HG 1500 V7
2.1.2.3 optiPoint 410/420 V5 R3
M- T- D- A-
H.323 (oP410) General term for H.323 functions
H.323
(oP410) active Voice 1024 -
. client (H.225- --- TCP Def: Ephemeral Ports (IANA)
over IP: 65535
Q.931)
H.323
(oP410) passive Voice 0-
over IP: 65535
Q.931)
H.323 Payload
H.245. Max 5 connections: RTP starts at
Transport (oP4x0 at
5004 - 0 - <adr> port2/max - 1 down to <adr> port
. H2k/H3k) active Voice client RTP_RTCP --- UDP
5013 65534 1/min , RTCP at <adr> port2/max down to
over IP: Uebertragung
<adr> port 1/min+1
der Sprachpakete
H.323 Payload
Transport (oP4x0 at Def: RTP portnumber is negotiated via
H2k/H3k) passive 5004 - 0 - H.245. Max 5 connections: RTP starts at
Voice over IP: 5013 65534 <adr>, RTCP at <adr>+1 (=RTP+1).
Uebertragung der Adm: even port number only
Sprachpakete
H.323 Payload
Transport (oP4x0 at
5008 - 0 - the port range then is 5004 ... 5013. But,
. H4k) active Voice over client RTP_RTCP --- UDP
5013 65534 in H4k scenarios, only the upper three
IP: Uebertragung der
couples (starting from the top) are used:
Sprachpakete
5012/5013, 5010/5011 and 5008/5009 .
H.323 Payload
Transport (oP4x0 at
5008 - 0 - the port range then is 5004 ... 5013. But,
. H4k) passive Voice server RTP_RTCP --- UDP
5013 65534 in H4k scenarios, only the upper three
over IP: Uebertragung
couples (starting from the top) are used:
der Sprachpakete
5012/5013, 5010/5011 and 5008/5009 .
HFA (oP410) Hicom Feature Access

CorNet TC Logon
. (oP600) CorNet TC client *proprietary* --- TCP 4060 Def: CorNet-TC
Logon Port
OAM (oP410 HFA) Administration of optiPoint HFA devices

DLS Workpoint
Interface (client sided)
. workpoint sided DLS client WPIP HTTPS TCP 18443
Communication
FTP_Server_Control
(oP410) FTP-Server
HTTPS_Server
(Phones) Secure 0-
Embedded Web 65535
Server
HTTP_Server
0-
65535
Interface
th
HiPath HG 1500 V7
M- T- D- A-
SNMP (SET/GET)

QCU client 12010
to the QCU
User Applications (oP410 HFA) bundle of user functions of HFA phone oP410
CTI Service (TCP) CTI
. client Cornet TS --- TCP 5105 Def: CTI Service oP410
Service in oP410
JAVA (optiPoints)
0-
. JAVA applications in client HTTP --- TCP 9200 Def: Java default port in optiPoint phones
65535
phones
LDAP Access
LDAP
65535 (IANA)
services (server)
th
HiPath HG 1500 V7
2.1.2.4 optiPoint WL2 professional V1.0 HFA Variant
M- T- D- A-
H.323 (WL2) General term for H.323 functions
H.323
(WL2) active Voice 1024 -
. client (H.225- --- TCP Def: Ephemeral Ports (IANA)
over IP: 65535
Q.931)
H.323 Def: H.225/Q.931
(WL2) passive Voice 1-
. server (H.225- --- TCP 1720 Adm: Default can be modified within this
over IP: 65535
Q.931) range
H.323 Payload
Transport (WL2) active
5004 - Def: RTP portnumber : RTP starts at
. Voice over IP: client RTP_RTCP --- UDP
5011 <adr>, RTCP at <adr>+1 (=RTP+1).
Uebertragung der
Sprachpakete
H.323 Payload
Transport (WL2) Def: RTP portnumber is negotiated via
5004 -
. passive Voice over IP: server RTP_RTCP --- UDP H.245. Max 5 connections: RTP starts at
5013
Uebertragung der <adr>, RTCP at <adr>+1 (=RTP+1).
Sprachpakete
HFA (WL2) Hicom Feature Access

CorNet TC Logon
. (WL2) CorNet TC client *proprietary* --- TCP 4060 Def: CorNet-TC
Logon Port
LDAP WL2 LDAP access for phones

LDAP Access (WL2)
0-
. Directory access via client LDAP --- TCP 389 Def: LDAP
65535
LDAP
OAM (WL2) Administration of optiPoint HFA devices

DHCP-Client (WL2)
Server of "Dynamic
Host Configuration
Protocol"
DHCP-Server (WL2)
Server of "Dynamic
. server DHCP --- UDP 67 Def: DHCP Server Port
Host Configuration
Protocol"
DLS Workpoint
Interface (WL2) (client
1024 - 0-
. sided) workpoint sided client WPIP HTTPS TCP Def: Ephemeral Ports (IANA)
65535 65535
DLS Communication
HTTPS_Server (WL2)
. Secure Embedded server HTTP --- TCP 443 Def: HTTPS
Web Server
HTTP_Server (WL2)
Web Interface
IP-Config (WL2)
Service Agent Reque
SNMP (SET/GET)
. (WL2) SNMP server SNMP --- UDP 161 Def: SNMP (Set/Get)
SNMP (Traps) (WL2)
. active Senden SNMP- client SNMP --- UDP 162 Def: SNMP (Traps)
Fehlermeldungen
Telnet (WL2) Telnet-
. server Telnet --- TCP 23 Def: Telnet
Server
th
HiPath HG 1500 V7
M- T- D- A-
QCU client 12010
to the QCU
th
HiPath HG 1500 V7
2.2 Administration and Diagnosis
The following services are needed for administration and diagnosis in addition to those listed in
chapter Voice Traffic and Signaling
OAM (HG1500) Administration and Maintenance

1024 -
DNS client DNS Client client DNS --- TCP_UDP Def: Ephemeral Ports (IANA)
65535
1024 -
DynDNS client DynDNS Client client DynDNS --- UDP Def: Ephemeral Ports (IANA)
65535
Expert Access (HG1500) Debug *propriet
server --- UDP 17185 Def: VxWorks DebugAgent
Agent access ary*
HTTP client (HG1500) used for
1024 -
multi gateway administratrion client HTTP --- TCP Def: Ephemeral Ports (IANA)
65535
feature (MGAF)
HTTP Server (HG1500) HTTP
server HTTP --- TCP 8085 Def: HTTP optiPoints, HG1500
Server for WBM access
HTTPS client used for multi
1024 -
gateway administration feature client HTTPS --- TCP - SSL Def: Ephemeral Ports (IANA)
65535
(MGAF)
HTTPS Server (HG1500)
server HTTPS --- TCP - SSL 443 Def: HTTPS
Secure Web Server
QCU Report (Client) Client
1024 -
application which sends QDC client SNMP --- UDP Def: Ephemeral Ports (IANA)
65535
reports to QCU Server
SNMP (SET/GET)
(H2/3/5k/HG1500) SNMP server SNMP --- UDP 161 Def: SNMP (Set/Get)
Set/Get
SNMP (Traps) (H2/3/5/HG1500) 1024 -
client SNMP --- UDP Def: Ephemeral Ports (IANA)
SNMP Error Messages 65535
SNMP (Traps) (HG1500)
server SNMP --- UDP 162 Def: SNMP (Traps)
Receiving of SNMP-Traps
SNTP Server
(H2/5k/HG1500,BizIP) Simple server SNTP --- UDP 123 Def: SNTP
Telnet (HG1500) CLI server Telnet --- TCP 23 Def: Telnet
Service Center (HG1500) Diagnosis access for development only

ServiceCenter (HG1500) Def: SC-LDH
Interface for diagnosis server SCP --- TCP 5098 1 - 65535 Adm: Default can be modified within
(developmentlevel) this range
X-Trace (HG1500) Access for X-Tracer

s
e
X
Online Trace (HG1500) Acces to r
T --- TCP 2048 Def: XTrace
X-Trace v
P
e
r
th
power_calc.fm
Nur für den internen Gebrauch Identifying System Power Requirements
D Identifying System Power Requirements
The following values are for orientation only, and can vary depending on the traffic
> flow.
This supplement specifies the power requirement of the boards and components of the HiPath
3000 systems. In addition, information is provided on the power requirement of the different
workpoint clients, key modules and adapters.
With this information,
● the individual system power requirement can be identified.
● every system configuration can be checked to see whether the nominal output of the power
supply unit is sufficient or whether an additional power supply may be needed.
Topic
HiPath 3800 Board Power Requirement, page D-2
Workpoint Client, Add-On Device, and Adapter Power Requirements, page D-12
Checking Whether the Output of a Power Supply Unit is Sufficient, page D-15
Identifying the Primary System Power Requirement, page D-18
To ensure that a system’s dynamic capacity limit is not exceeded, the configuration
> can be tested using the project planning tool:
http://intranet.mch4.siemens.de/syseng/perfeng/tools/hpt/index.htm
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual D-1
power_calc.fm
Identifying System Power Requirements Nur für den internen Gebrauch

HiPath 3800 Board Power Requirement
D.1 HiPath 3800 Board Power Requirement
Table D-1 Nominal Output of the HiPath 3800 Power Supply Unit
Power supply unit Code number Max. Nominal Output in W

5V –48 V
Power Box PB3000 C39165-A7027-A5-* with 110
(incl. LUNA2) S30122-K7686-L1
S30122-K7686-M1
LUNA2 S30122-K7686-L1 1401
S30122-K7686-M1
1 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-V output.
* Depending on version
You must check whether the total power requirement of the boards used and the
> connected workpoint clients of a system cabinet exceeds the maximum possible
LUNA2 output. Section D.7 contains a sample calculation.
Table D-2 HiPath 3800 Board Power Requirement
Board or Component Code number Net Power Requirement in

W
5V –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 –
IVMN8 S30122-H7688-X100 10.0 –
IVMNL S30122-H7688-X 10.0 –
PBXXX S30810-Q6401-X 15.0 –
PDMX S30807-Q5697-X200 3.0 –
REALS S30807-Q6629-X 1.5 –
RGMOD S30124-X5109-X – 14.4
SLCN S30810-Q2193-X300 5.0 –
SLMA S30810-Q2191-C300 1.6 12.0
SLMA2 S30810-Q2246-X 2.1 13.3
A31003-H3570-S100-6-7620, 2008-04-01
D-2 HiPath 3000/5000 V7, Service Manual
power_calc.fm

W
5V –48 V
SLMA8 S30810-Q2191-C100 0.6 4.0
SLMO2 S30810-Q2168-X10 1.0 1.2
SLMO8 S30810-Q2168-X100 0.4 0.4
STMD3 S30810-Q2217-X10 4.0 –
STMI2 S30810-Q2316-X100 16.3 –
TM2LP S30810-Q2159-Xxxx 1.8 –
TMC16 S30810-Q2485-X 1.3 –
TMCAS-2 S30810-Q2946-X 4.5 –
TMDID S30810-Q2452-X 2.3 6.6
TMEW2 S30810-Q2292-X100 1.3 3.1
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

Table D-3 Nominal Output of the HiPath 3550 Power Supply Units

5V –48 V
UPSC-D S30122-K5660-M300 40.0 53.0
UPSC-D with EPSU2 S30122-K5660-M300 with 40.0 140.0
S30122-K7221-X2
(incl. LUNA2) S30122-K7686-L1
S30122-K7686-M1
> connected workpoint clients exceeds the maximum possible output of the UPSC-D
with or without EPSU2. Section D.7 contains a sample calculation.

W
5V –48 V
BS3/1 S30807-H5482-X – 2.0
BS3/3 S30807-H5485-X – 3.0
CBCC (including subboards) 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 ventilator S30810-Q2943-X 10.0 2.8
kit)
HXGS3 (excluding ventilator S30810-Q2943-X 10.0 –
kit)
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
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

W
5V –48 V
SLA24N S30810-Q2929-X 4.5 4.5
SLAD4 S30810-H2956-X100 2.0 1.0
SLAD8 S30810-H2956-X200 2.0 1.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 –
TCAS-2 S30810-Q2945-X 4.5 –
TLA2 S30817-Q923-Bxxx 0.1 –
TLA4 S30817-Q923-Axxx 0.2 –
TLA8 S30817-Q926-Axxx 0.4 –
TMAMF S30810-Q2587-A400 1.81 16.91
TMCAS S30810-Q2938-X
TMGL4 S30810-Q2918-X 4.71 0.11
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 Identified at a traffic flow of 0.8 Erlang
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

Table D-5 Nominal Output of the HiPath 3350Power Supply Units

5V –48 V
PSUP S30122-K5658-M 15.0 19.2
UPSC-D S30122-K5660-M300 20.01 53.0
UPSC-D with EPSU2 S30122-K5660-M300 with 40.0 140.0
S30122-K7221-X2
(incl. LUNA2) S30122-K7686-L1
S30122-K7686-M1
1 Nominal output = 40 W. Due to build-up of heat, not more than 20 W may be withdrawn.
> connected workpoint clients exceeds the maximum possible output of the PSUP or
the UPSC-D with or without EPSU2. Section D.7 contains a sample calculation.

W
5V –48 V
BS3/1 S30807-H5482-X – 2.0
BS3/3 S30807-H5485-X – 3.0
CBCC (including subboards) 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 ventilator S30810-Q2943-X 10.0 2.8
kit)
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
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

W
5V –48 V
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 –
TLA8 S30817-Q926-Axxx 0.4 –
TMGL4 S30810-Q2918-X 4.71 0.11
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
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm


5V –48 V
UPSC-DR S30122-K7373-M900 40.0 53.0
UPSC-DR with EPSU2-R1 S30122-K7373-M900 with 40.0 140.0
S30122-K7221-X900
(incl. LUNA2) S30122-K7686-L1
S30122-K7686-M1
1 Mounted in the ECR
> connected workpoint clients exceeds the maximum possible output of the UPSC-DR
with or without EPSU2-R. Section D.7 contains a sample calculation.

W
5V –48 V
BS3/1 S30807-H5482-X – 2.0
BS3/3 S30807-H5485-X – 3.0
CBRC (including subboards) S30810-Q2935-Z301 7.0 0.5
HXGR3 S30810-K2943-Z 10.0 –
IVMS8R S30122-K7379-Z 2.6 0.3
Fan for HiPath 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 –
TCASR-2 S30810-K2945-X 4.5 –
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

W
5V –48 V
TLA4R S30817-Q923-Zxxx 0.2 –
TMGL4R S30810-K2918-Z 5.71 0.11
TST1 S30810-K2919-Z 0.8 –
TS2R S30810-K2913-Z300 0.9 –
8SLAR S30810-K2925-Z 1.3 1.3
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm


5V –48 V
UPSC-DR S30122-K7373-M900 20.01 53.0
UPSC-DR with EPSU2-R S30122-K7373-M900 with 40.0 140.0
S30122-K7221-X900
(incl. LUNA2) S30122-K7686-L1
S30122-K7686-M1
1 Nominal output = 40 W. Due to build-up of heat, not more than 20 W may be withdrawn.
> connected workpoint clients exceeds the maximum possible output of the UPSC-DR
with or without EPSU2-R. A sample calculation is shown in Section D.7.

W
5V –48 V
BS3/1 S30807-H5482-X – 2.0
BS3/3 S30807-H5485-X – 3.0
CBRC (including subboards) S30810-Q2935-Z301 7.0 0.5
HXGR3 S30810-K2943-Z 10.0 –
IVMP8R S30122-K7379-Z100 2.6 0.3
Fan for HiPath 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 –
TMGL4R S30810-K2918-Z 5.71 0.11
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

W
5V –48 V
8SLAR S30810-K2925-Z 1.3 1.3
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

Workpoint Client, Add-On Device, and Adapter Power Requirements
D.6 Workpoint Client, Add-On Device, and Adapter Power

Requirements
An average power requirement is specified, which is identified at a traffic flow of 0.15 Erlang.
Table D-11 Workpoint Client, Add-On Device, and Adapter Power Requirements
Workpoint Client Net Power Requirement in W

(from –48 V input)
OpenStage 20
OpenStage
(CorNet-IP OpenStage 40
0.01
connection OpenStage 60
variant)
OpenStage 80
OpenStage 10
0.85 W
OpenStage OpenStage 20
(TDM connec- OpenStage 40 1.1 W
tion variant) OpenStage 60
0.02
OpenStage 80
OpenStage Key Module 0.02
OpenStage BLF 0.02
OpenStage PhoneAdapter 0.02
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

optiPoint 410 entry, optiPoint 410 entry S
optiPoint 410 economy,
optiPoint 410 standard,
optiPoint 410 advance,
optiPoint 420 economy,
optiPoint 410 optiPoint 420 economy S
0.01
optiPoint 420
optiPoint 420 economy plus,
optiPoint 420 standard,
optiPoint 420 advance,
optiPoint self labeling key module
optiPoint 410 display module
optiPoint 500 entry 0.3
optiPoint 500 economy (not for U.S.) 0.7
optiPoint 500 basic 0.7
optiPoint 500 standard, 0.7
optiPoint 500 standard SL (for U.S. only)
optiPoint 500 advance 0.72
optiPoint 500 optiPoint key module 0.05
optiPoint BLF 0.02
optiPoint analog adapter 0.003
optiPoint ISDN adapter 0.7
optiPoint phone adapter 0.18
optiPoint acoustic adapter 0.25
optiPoint recorder adapter 0.3
optiPoint 600 office 0.01
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm


optiset E entry 0.36
optiset E basic 0.36
optiset E standard 0.41
optiset E advance plus/comfort 0.43
optiset E advance conference/conference 0.85
optiset E memory 0.56
optiset E key module 0.06
Hicom Attendant BLF 0.02
optiset E optiset E acoustic adapter 0.02
optiset E analog adapter 0.03
optiset E contact adapter 0.7
optiset E control adapters 0.34
optiset E data adapter 0.76
optiset E headset adapter 0.03
optiset E headset plus adapter 0.23
optiset E ISDN adapter 0.05
optiset E phone adapter 0.06
Analog telephone (40 mA for short trunk) in active status 0.3
1 Power over Ethernet or power supply via a local plug-in unit.
2 Power is provided by a local power supply.
3 A local power supply provides power to the connected analog telephone.
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm
Checking Whether the Output of a Power Supply Unit is Sufficient
D.7 Checking Whether the Output of a Power Supply Unit is

Sufficient
Apart from the secondary power requirements, the power output must also be checked to en-
sure that the maximum possible output of the system’s power supply unit is sufficient. For this,
the power requirement on the 5-V output format and on the –48-V output format must be ex-
amined separately.
Caution
7 To guarantee smooth system operation, the nominal output of the power supply unit
at the 5-V output and at the –48-V output must be greater than the respective sec-
ondary power requirement.
Procedure
Proceed as follows to identify the secondary power requirement of a system:
1. Determine secondary power requirement at the 5-V output
5 V power requirement of the boards/components used
= secondary power requirement at the 5-V output

2. Determine secondary power requirement at the –48-V output
–48 V power requirement of the boards/components used

+ power requirement of connected workpoint clients (analog and digital telephones),
key modules and adapters
= secondary power requirement at the –48-V output

Using the specified values, check whether the total power requirement exceeds the maximum
possible output of the power supply unit at the 5-V output or at the –48-V output. If this is the
case, you have the following options:
● HiPath 3800
The number of LUNA2 power supply units can be increased.
● HiPath 3550 with USPSC-D
The maximum nominal output at the –48-V output can be increased from 53 W to 140 W
by using the EPSU2 external power supply unit.
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

● HiPath 3350 with USPSC-D

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 EPSU2 external power supply
unit. In addition, the maximum nominal output of the –48-V output increases from 53 W to
140 W.
● HiPath 3500 with UPSC-DR
The maximum nominal output of the –48-V output can be increased from 53 W to 140 W
by using the EPSU2-R external power supply unit.
● HiPath 3300 with USPSC-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 EPSU2-R external power sup-
ply unit. In addition, the maximum nominal output of the –48-V output increases from 53 W
to 140 W.
Sample calculation for a HiPath 3550

1. Determine secondary power requirement at the 5-V output
power requirements of the boards/ 7.00 W 1 x CBCC

components used = 10.00 W 1 x HXGS3 (including ventilator
kit)
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 the 26.60 W

5-V output =
The maximum nominal output of UPSC-D at the 5-V output amounts to 40 W and is
enough to cover the specified power requirement.
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm
2. Determine secondary power requirement at the –48-V output

kit)
0.00 W 1 x TS2
0.00 W 3 x SLU8
1.30 W 1 x 8SLA
0.00 W 1 x SLC16N
24.00 W 12 x BS3/1
+ power requirement of connected 0.56 W 1 x optiset E memory
workpoint clients, key modules and 4.32 W 6 x optiPoint 500 advance
adapters =
0.85 W 1 x optiset E advance confer-
ence/conference
8.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 telephones
= secondary power requirement at the – 47.83 W

48-V output =
The maximum nominal output of UPSC-D at the –48-V output amounts to 53 W and is
enough to cover the specified power requirement.
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

Identifying the Primary System Power Requirement
D.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
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

2. Identifying primary power requirement
overall secondary power requirement

+ requirements of power supply units (UPSM = 30 W, PSUP/UPSC-D/UPSC-DR =
12 W respectively)
+ requirements of EPSU2/EPSU2R (10 W respectively)
= the result should be multiplied by the factor 1.2 to allow for the degree of efficiency of
the power supply.
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm
Sample calculation for a HiPath 3550

1. Determine overall secondary power requirement

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 0.56 W 1 x optiset E memory
workpoint clients, key modules and 4.32 W 6 x optiPoint 500 advance
adapters =
0.85 W 1 x optiset E advance confer-
ence/conference
8.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

=
2. Identifying primary power requirement
overall secondary power requirement 74.43 W

=
+ UPSC-D requirement = 12.00 W
Allow for the degree of efficiency of the 86.43 W x 1.2 = 103.7 W

power supply unit:
The primary power requirement of HiPath 3550 with the expansion mentioned
amounts to approximately 103.7 W.
A31003-H3570-S100-6-7620, 2008-04-01
power_calc.fm

A31003-H3570-S100-6-7620, 2008-04-01
snmpd.fm
Nur für den internen Gebrauch Notes for editing the file snmpd.cnf
Introduction
E Notes for editing the file snmpd.cnf
E.1 Introduction
The SNMP parameters required for HiPath 5000 are defined when installing the FM Reporting
Client (SNMP Master Agent). This refers to the trap destinations and the names of the HiPath
Fault Management desktop communities.
The FM Reporting Client does not have its own user interface. The SNMP parameters defined
during installation may only be changed by uninstalling and then reinstalling the FM Reporting
Client.
Users with sufficient knowledge of SNMP can change trap destinations and community names
by editing the file snmpd.cnf. The file can be found in the installation directory of the FM Re-
porting Client.
The following notes on editing the file snmpd.cnf are intended exclusively for users
> with sufficient knowledge of SNMP.
Note: The syntax of entries in the FM Reporting Client configuration file (SNMP mas-
ter agent) is appended to the element description in the SNMP-TARGET-MIB (RFC
3413 – Chapter 4, cf. http://www.zvon.org).
E.2 Trap Destination
Procedure for sending a trap

1. Testing of the snmpNotifyEntry entries.
2. A trap is sent for all with snmpNotifyTag == snmpTargetAddrTagList.
a) Only one snmpNotifyEntry should exist.
b) The snmpNotifyTag of this entry should be used in all snmpTargetAddrEntries.
3. In addition, there must be an entry with snmpTargetAddrParams == snmpTarget-
ParamsName.
snmpNotifyEntry <snmpNotifyName> <snmpNotifyTag> <snmpNotifyType>
<snmpNotifyStorageType>
● snmpNotifyName
Any unambiguous identifier for the entry.
String with 1-32 characters.
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual E-1
snmpd.fm
Notes for editing the file snmpd.cnf Nur für den internen Gebrauch
Trap Destination
● snmpNotifyTag
Designation that must correspond with the snmpTargetAddrTagList (snmpTagetAd-
drEntry), so that a trap can be sent.
The value is always "hipath".
● snmpNotifyType
Type of traps that are to be sent (trap, about).
For HiPath 5000 always “trap”.
● snmpNotifyStorageType
Always “nonVolatile” (persistent storage necessary).
snmpTargetAddrEntry <snmpTargetAddrName> <snmpTargetAddrTDomain> <sn-
mpTargetAddrTAddress> <snmpTargetAddrTimeout> <snmpTargetAddrRetry-
Count> <snmpTargetAddrTagList> <snmpTargetAddrParams> <snmpTargetAd-
drStorageType> <snmpTargetAddrTMask> <snmpTargetAddrMMS>
● snmpTargetAddrName
● snmpTargetAddrTDomain
Transport type for the entry.
String: snmpUDPDomain or snmpIPXDomain.
● snmpTargetAddrTAddress
Destination address for traps.
The format depends on the entry snmpTargetAddrTDomain.
For snmpUDPDomain: IP address + port (for example 192.132.123.98:162), whereby 0
may also be entered as a port. In this case the default port will be used.
● snmpTargetAddrTimeout
Timeout: Default is 1500. For HiPath 5000, 100 is used.
● snmpTargetAddrRetryCount
Retry count: Default is 3.
● snmpTargetAddrTagList
Designation that must correspond with a snmpNotifyTag (snmpNotifyEntry) so that
a trap can be sent to the given address.
The value is always "hipath".
● snmpTargetAddrParams
Designation that refers to an entry in a snmpTargetParamsEntry (snmpTarget-
ParamsName).
The value is always "v1Params".
● snmpTargetAddrStorageType
A31003-H3570-S100-6-7620, 2008-04-01
E-2 HiPath 3000/5000 V7, Service Manual
snmpd.fm
Trap Destination
● snmpTargetAddrTMask
Transport mask is always 255.255.255.255:0.
● snmpTargetAddrMMS
Maximum message size is always 2048 (bytes).
snmpTargetParamsEntry <snmpTargetParamsName> <snmpTargetParamsMPMod-
el> <snmpTargetParamsSecurityModel> <snmpTargetParamsSecurityName>
<snmpTargetParamsSecurityLevel> <snmpTargetParamsStorageType>
● snmpTargetParamsName
The value is always "v1Params".
● snmpTargetParamsMPModel
Message processing model: 0 (SNMPv1), 1 (SNMPv2c), 2 (SNMPv2u, SNMPv2*),
3 (SNMPv3).
1 for "v1Params".
● snmpTargetParamsSecurityModel
Security Model: snmpv1, snmpv2c, snmpv2s, ...
snmpv1 for "v1Params".
● snmpTargetParamsSecurityName
Security name within the configuration file.
The value is always “public”.
● snmpTargetParamsSecurityLevel
Security level is always “noAuthNoPriv”.
● snmpTargetParamsStorageType
A31003-H3570-S100-6-7620, 2008-04-01
snmpd.fm
Community (Read/Write)
E.3 Community (Read/Write)

snmpCommunityEntry <snmpCommunityIndex> <snmpCommunityName> <snmpCom-
munitySecurityName> <snmpCommunityContextEngineID> <snmpCommunityCon-
textName> <snmpCommunityTransportTag> <snmpCommunityStorageType>
● snmpCommunityIndex
● snmpCommunityName
The incoming snmpv1 community (read or write community).
● snmpCommunitySecurityName
This identifier represents the entry within the entire configuration file (for example in the
snmpTargetParamsSecurityName).
Always “public” (read community and trap destinations) or “private” (write community).
● snmpCommunityContextEngineID
The value is always “localSnmpID”.
● snmpCommunityContextName
Is always empty.
● snmpCommunityTransportTag
Is always empty.
● snmpCommunityStorageType
A31003-H3570-S100-6-7620, 2008-04-01
snmpd.fm
Consequences for the file snmpd.cnf
E.4 Consequences for the file snmpd.cnf

The following entries can be found in the configuration file delivered with the installation.
snmpNotifyEntry icn1 hipath trap nonVolatile
snmpTargetParamsEntry v1Params 0 snmpv1 public noAuthNoPriv nonVolatile
snmpTargetParamsEntry v2Params 1 snmpv2c public noAuthNoPriv nonVolatile
vacmAccessEntry Anyone - snmpv1 noAuthNoPriv prefix CfgProt - CfgProt \
nonVolatile
vacmAccessEntry Anyone - snmpv2c noAuthNoPriv prefix CfgProt - CfgProt \
nonVolatile
vacmAccessEntry SetAnyone - snmpv1 noAuthNoPriv prefix CfgProt CfgProt \
CfgProt nonVolatile
vacmAccessEntry SetAnyone - snmpv2c noAuthNoPriv prefix CfgProt CfgProt \
CfgProt nonVolatile
vacmSecurityToGroupEntry snmpv1 public Anyone nonVolatile
vacmSecurityToGroupEntry snmpv1 private SetAnyone nonVolatile
vacmSecurityToGroupEntry snmpv2c public Anyone nonVolatile
vacmViewTreeFamilyEntry All internet - included nonVolatile
vacmViewTreeFamilyEntry CfgProt internet - included nonVolatile
vacmViewTreeFamilyEntry CfgProt vacmSecurityToGroupTable - excluded \
nonVolatile
vacmViewTreeFamilyEntry CfgProt vacmAccessTable - excluded nonVolatile
vacmViewTreeFamilyEntry CfgProt snmpCommunityTable - excluded nonVolatile
vacmViewTreeFamilyEntry CfgProt usmUserTable - excluded nonVolatile
vacmViewTreeFamilyEntry CfgProt vacmViewTreeFamilyTable - excluded \
nonVolatile
This means that any entries to be made must always be in the following format:
1. Communities
(Definition: There is exactly one read and exactly one write community.)
a) Read Community
snmpCommunityEntry t001 <community-string> public localSnmpID -
- nonVolatile
a) Write Community
snmpCommunityEntry t002 <community-string> public localSnmpID -
- nonVolatile
2. Trap Destinations
snmpTargetAddrEntry <lfd.-Nr.> snmpUDPDomain <IP-Adresse>:<Port>
100 3 hipath v1Params nonVolatile 255.255.255.255:0 2048
A31003-H3570-S100-6-7620, 2008-04-01
snmpd.fm
Consequences for the file snmpd.cnf
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
Nur für den internen Gebrauch Figures
Figures 0
Figure 2-1 HiPath 3800 Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Figure 2-6 Planning Load for HiPath 3000/5000 Systems . . . . . . . . . . . . . . . . . . . . 2-29
Figure 2-7 IP Trunking with TDM Terminal Points Only . . . . . . . . . . . . . . . . . . . . . . 2-42
Figure 2-8 IP Trunking and HFA Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Figure 2-9 IP Trunking and Node Connection via ISDN (PPP) . . . . . . . . . . . . . . . . 2-44
Figure 2-10 VPN Networking (Voice Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Figure 2-11 VPN Voice and Data, Home Office Connection . . . . . . . . . . . . . . . . . . . 2-47
Figure 2-12 VPN Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Figure 2-13 IP Workpoint Clients for ISDN and ITSP Connection in HiPath 3800 . . . 2-51
Figure 3-1 CBCC Board (S30810-Q2935-A401) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Figure 3-2 CBCC Board (S30810-Q2935-A301) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Figure 3-3 CBRC Board (S30810-Q2935-Z401) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Figure 3-4 CBRC Board (S30810-Q2935-Z301) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Figure 3-5 CBSAP Board (S30810-Q2314-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Figure 3-6 CBSAP - Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Figure 3-7 CMA with Spacing Bolts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Figure 3-8 Networking Options for HiPath 3000 Systems . . . . . . . . . . . . . . . . . . . . 3-39
Figure 3-9 CUC Backplane (S30777-Q750-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Figure 3-10 CUCR Backplane (S30777-Q750-Z) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Figure 3-11 CUP Backplane (S30777-Q751-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Figure 3-12 CUPR Backplane (S30777-Q751-Z) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Figure 3-13 DBSAP (S30807-Q6722-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Figure 3-14 DBSAP on the Backplane of the Expansion Cabinet . . . . . . . . . . . . . . . 3-46
Figure 3-15 CBSAP with LIMS Module Plugged In . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Figure 3-16 LUNA2 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Figure 3-17 LUNA2 slots in the basic cabinet (outer panel mounted) . . . . . . . . . . . . 3-56
Figure 3-18 LUNA2 Slots in the Expansion Cabinet (With Outer Panel Mounted) . . . 3-57
Figure 3-19 Rear View of the BSG 48/38 Battery Cabinet (S30122-K5950-F300). . . 3-59
Figure 3-20 Connections Between the BSG 48/38 Battery Cabinet and HiPath 3800 3-60
Figure 3-21 PSUP Interface (S30122-K5658-M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Figure 3-22 HiPath 3800 - Connectors and Jacks on Backplane of Basic Cabinet . . 3-66
Figure 3-23 HiPath 3800 - Connectors and Jacks on Backplane of Expansion Cabinet . . .
3-67
Figure 3-24 UPSC-D (S30122-K5660-M300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Figure 3-25 UPSC-D (S30122-K5660-M300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Figure 3-26 UPSC-D - Switches and LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual W-1
hp3hp5shLOF.fm
Figures Nur für den internen Gebrauch
Figure 3-27 UPSC-D - Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

Figure 3-28 UPSC-DR (S30122-K7373-M900) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Figure 3-29 UPSC-DR (S30122-K7373-M900) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Figure 3-30 UPSC-DR - Switches and LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Figure 3-31 UPSC-DR - Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Figure 3-32 CSAPE (S30807-U6630-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Figure 3-33 HiPath 3800 - Board Slots in the Basic Cabinet . . . . . . . . . . . . . . . . . . . . 3-81
Figure 3-34 DIU2U (for U.S. only) Adapter Cable C39195-A7269-B625. . . . . . . . . . . 3-82
Figure 3-35 DIU2U (for U.S. only) - Front Panel (S30810-Q2216-X) . . . . . . . . . . . . . 3-83
Figure 3-36 DIUN2 - Front Panel (S30810-Q2196-X) . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Figure 3-37 HXGS3 (S30810-Q2943-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Figure 3-38 HXGR3 (S30810-K2943-Z) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92
Figure 3-39 HXGS3/HXGR3 - Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
Figure 3-40 HXGS3 - Installation of the Fan Kit in HiPath 3550 . . . . . . . . . . . . . . . . . 3-97
Figure 3-41 HXGS3 - Securing Clips for Fan Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Figure 3-42 HXGS3 - Connection of the Fan Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Figure 3-43 IVMNL, IVMN8 - Front Panel (S30122-H7688-X -X100) . . . . . . . . . . . . 3-100
Figure 3-44 IVMP4, IVMP4R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Figure 3-45 IVMP8 and IVMP8R (not for U.S.) - Packing Protection Covering . . . . . 3-108
Figure 3-46 IVMP8, IVMP8R (S30122-Q7379-X100, -K7379-Z100) (not for U.S.) . . 3-109
Figure 3-47 IVMS8, IVMS8R - Packing Protection Covering. . . . . . . . . . . . . . . . . . . 3-113
Figure 3-48 IVMS8, IVMS8R (S30122-Q7379-X, -K7379-Z) . . . . . . . . . . . . . . . . . . . 3-114
Figure 3-49 IVMS8R - Front View (S30122-K7379-Z) . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Figure 3-50 IVMS8N, IVMS8NR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
Figure 3-51 PBXXX (S30810-Q6401-X) (for selected countries) – Front Panel . . . . 3-123
Figure 3-52 HiPath 3800 Basic Cabinet – 1x DIUN2 + 1 x PBXXX . . . . . . . . . . . . . . 3-125
Figure 3-53 PBXXX (for selected countries only) – Connecting the CAS Cable using the
APPCU Adapter 3-126
Figure 3-54 PBXXX (for selected countries only) – Adapter Panel (C39165-A7050-C35) .
3-127
Figure 3-55 HiPath 3800 Basic Cabinet – 1x DIUN2 + 2 x PBXXX . . . . . . . . . . . . . . 3-128
Figure 3-56 PBXXX (for selected countries only) – Connecting the CAS Cable using Two
APPCU Adapters 3-129
Figure 3-57 SLA8N (not for U.S.), SLA16N, SLA24N (S30810-Q2929-X200, -X100, -X) . .
3-131
Figure 3-58 SLAD4, SLAD8 – interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138
Figure 3-59 SLAD8R – interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139
Figure 3-60 SLC16N (S30810-Q2193-X100) (not for U.S.) . . . . . . . . . . . . . . . . . . . . 3-141
Figure 3-61 Base Station Power Supply via One UP0/E Interface (not for U.S.) . . . . 3-147
Figure 3-62 Base Station Power Supply via Two UP0/E Interfaces (not for U.S.) . . . 3-148
Figure 3-63 Base Station Power Supply via Three P0/E Interfaces (not for U.S.) . . . 3-149
Figure 3-64 EPSU2 - Indicators and Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
Figure 3-65 EPSU2 - Holes for Mounting on the Wall . . . . . . . . . . . . . . . . . . . . . . . . 3-154
Figure 3-66 SLCN (not for U.S.) (S30810-Q2193-X300) - LEDs in the Front Panel . 3-155
A31003-H3570-S100-6-7620, 2008-04-01
W-2 HiPath 3000/5000 V7, Service Manual
hp3hp5shLOF.fm
Figure 3-67 SLMAE8, SLMAE - Touch Guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-163

Figure 3-68 SLMAE8, SLMAE - LEDs on the Front Panel . . . . . . . . . . . . . . . . . . . . 3-164
Figure 3-69 SLMA/SLMA8 - LEDs on the Front Panel . . . . . . . . . . . . . . . . . . . . . . . 3-173
Figure 3-70 SLMA2 (S30810-Q2246-X) (for selected countries only) - LEDs on the Front
Panel 3-182
Figure 3-71 SLMO2/SLMO8 - LEDs on the Front Panel . . . . . . . . . . . . . . . . . . . . . 3-191
Figure 3-72 SLMO8 (not for U.S.), SLMO24 (S30810-Q2901-X100, S30810-Q2901-X) . . .
3-201
Figure 3-73 SLU8 Interfaces (S30817-Q922-A301) . . . . . . . . . . . . . . . . . . . . . . . . . 3-207
Figure 3-74 SLU8R Interfaces (S30817-K922-Z301) . . . . . . . . . . . . . . . . . . . . . . . . 3-208
Figure 3-75 STLS2 (not for U.S.), STLS4 Interfaces (S30817-Q924-B313, -A313) . 3-209
Figure 3-76 Sample Pin Assignments in MW Jacks (not for U.S.) . . . . . . . . . . . . . . 3-212
Figure 3-77 Wiring and Ranges for S0 Bus Jacks (not for U.S.). . . . . . . . . . . . . . . . 3-213
Figure 3-78 MWxx Jack Pin Assignment (for U.S. only). . . . . . . . . . . . . . . . . . . . . . 3-214
Figure 3-79 S 0 Bus wiring from STLS4 port or optiset E ISDN adapter (for U.S. only) . . . .
3-215
Figure 3-80 STLS4R Interfaces (S30817-K924-Z313) . . . . . . . . . . . . . . . . . . . . . . 3-216
Figure 3-81 STLSX2, STLSX4, STLSX4R - Interfaces . . . . . . . . . . . . . . . . . . . . . . 3-219
Figure 3-82 Pin Assignments in MW Jacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-221
Figure 3-83 Wiring and Ranges for S0 Bus Jacks . . . . . . . . . . . . . . . . . . . . . . . . . . 3-222
Figure 3-84 STMD3 (S30810-Q2217-X10) - LEDs in the Front Panel . . . . . . . . . . . 3-223
Figure 3-85 STMI2 (S30810-Q2316-X100) - HGA Slots . . . . . . . . . . . . . . . . . . . . . 3-230
Figure 3-86 STMI2 - Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-232
Figure 3-87 TCAS-2 (S30810-Q2945-X) (for selected countries only) – Figure. . . . 3-235
Figure 3-88 TCAS-2, TCASR-2 (for selected countries only) – Interfaces and Jumpers . . .
3-236
Figure 3-89 TCAS-2, TCASR-2 (for selected countries only) – Connections . . . . . . 3-238
Figure 3-90 TCASR-2 (for selected countries only) – Front Panel . . . . . . . . . . . . . . 3-239
Figure 3-91 TCAS-2, TCASR-2 (for selected countries only) – CAS Application Software
States 3-241
Figure 3-92 TCAS-2, TCASR-2 (for selected countries only) – Optional Modem. . . 3-242
Figure 3-93 TCAS-2, TCASR-2 (for selected countries only) – Connection Options for Card
Administration using CAS Manager 3-243
Figure 3-94 TCAS-2, TCASR-2 (for selected countries only) – RJ45 Cable C39195-Z7208-
A10 3-244
Figure 3-95 TCAS-2, TCASR-2 (for selected countries only) – CAS Cable C39195-A7700-
B13 3-245
Figure 3-96 TCAS-2, TCASR-2 (for selected countries only) – Impedance Converter
F31505-E1-A146 3-245
Figure 3-97 CAS cable – shield contacting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-246
Figure 3-98 TLA2, TLA4 (not for U.S.) - Interfaces (S30817-Q923-Bxxx, -Axxx). . . 3-247
Figure 3-99 TLA8 (not for U.S.) - Interfaces (S30817-Q926-Axxx) . . . . . . . . . . . . . 3-248
Figure 3-100 TLA4R (not for U.S.) - Interfaces (S30817-Q923-Zxxx) . . . . . . . . . . . . 3-249
Figure 3-101 TM2LP - Front Panel (S30810-Q2159-Xxxx) . . . . . . . . . . . . . . . . . . . . 3-251
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
Figure 3-102 TMAMF (S30810-Q2587-Axxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-258

Figure 3-103 Pin Assignments of the TMAMF Diagnostic Cable. . . . . . . . . . . . . . . . . 3-259
Figure 3-104 TLANI2, TLANI4 – Interfaces (S30810-H2953-X1xx / -Xxx) . . . . . . . . . 3-263
Figure 3-105 TLANI8 – Interfaces (S30810-H2954-X1xx). . . . . . . . . . . . . . . . . . . . . . 3-263
Figure 3-106 TLANI4R – Interfaces (S30810-K2953-X2xx) . . . . . . . . . . . . . . . . . . . . 3-266
Figure 3-107 TMANI8 – Front Panel, LEDs (S30810-Q2327-Xxx) . . . . . . . . . . . . . . . 3-269
Figure 3-108 TMC16 (for selected countries only) (S30810-Q2485-X) - Front Panel . 3-276
Figure 3-109 TMCAS (S30810-Q2938-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-282
Figure 3-110 TMCAS-2 (S30810-Q2946-X) (for selected countries only) – Figure . . . 3-290
Figure 3-111 TMCAS-2 (for selected countries only) – Interfaces and Jumpers . . . . . 3-291
Figure 3-112 TMCAS-2 (for selected countries only) – Front Panel . . . . . . . . . . . . . . 3-293
Figure 3-113 TMCAS-2 (for selected countries only) – CAS Application Software States . .
3-296
Figure 3-114 TMCAS-2 (for selected countries only) – Optional Modem . . . . . . . . . . 3-296
Figure 3-115 TMCAS-2 (for selected countries only) – Connection Options for Card Admin-
istration using CAS Manager 3-297
Figure 3-116 TMCAS-2 (for selected countries only) – CAS Cable C39195-A7700-B14 . . .
3-298
Figure 3-117 TMDID (for U.S. only) (S30810-Q2452-X) - Front Panel . . . . . . . . . . . . 3-300
Figure 3-118 TMDID2 (S30810-Q2197-T) (for selected countries only) . . . . . . . . . . . 3-304
Figure 3-119 TMDID2 (for selected countries only) - LEDs on the Front Panel . . . . . 3-305
Figure 3-120 E&M Interface Type 1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313
Figure 3-121 E&M Interface Type 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-314
Figure 3-122 TMEW2 - Front Panel (S30810-Q2292-X100) . . . . . . . . . . . . . . . . . . . . 3-315
Figure 3-123 TMGL4 (for U.S. only) - Interfaces (S30810-Q2918-X) . . . . . . . . . . . . . 3-319
Figure 3-124 TMGL4R (for U.S. only) (S30810-K2918-Z) . . . . . . . . . . . . . . . . . . . . . 3-321
Figure 3-125 TMQ4 (for U.S. only) (S30810-Q2917-X) . . . . . . . . . . . . . . . . . . . . . . . 3-323
Figure 3-126 TST1 (for U.S. only) (S30810-Q2919-X/S30810-K2919-Z) . . . . . . . . . . 3-325
Figure 3-127 TS2 (not for U.S.) - Interfaces (S30810-Q2913-X100, -X300) . . . . . . . 3-328
Figure 3-128 TS2R (not for U.S.) - Interfaces (S30810-K2913-Z100, -Z300) . . . . . . . 3-328
Figure 3-129 S2M Trunk Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-330
Figure 3-130 S2M - NT Connections for Spain and Portugal . . . . . . . . . . . . . . . . . . . . 3-331
Figure 3-131 4SLA (not for U.S.), 8SLA - Interfaces (S30810-Q2923-X200, -X100) . 3-332
Figure 3-132 16SLA (not for U.S.) - Interfaces (S30810-Q2923-X). . . . . . . . . . . . . . . 3-333
Figure 3-133 8SLAR Interfaces (S30810-K2925-Z). . . . . . . . . . . . . . . . . . . . . . . . . . . 3-335
Figure 3-134 ALUM4 - Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-337
Figure 3-135 ALUM4 - Interfaces (S30817-Q935-A) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-338
Figure 3-136 ALUM4 - Basic Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-340
Figure 3-137 AMOM - Connection to DIUN2 and DIU2U . . . . . . . . . . . . . . . . . . . . . . 3-341
Figure 3-138 ANI4 (for selected countries only) - Interfaces (S30807-Q6917-Axxx) . 3-343
Figure 3-139 ANI4 (for selected countries only) - Installation Steps . . . . . . . . . . . . . . 3-346
Figure 3-140 ANI4R (for selected countries only) (S30807-Q6917-Z103) . . . . . . . . . 3-347
Figure 3-141 EXM Slot for HiPath 3550 and HiPath 3350 Wall Housing. . . . . . . . . . . 3-350
Figure 3-142 EXMR connection to HiPath 3550 and HiPath 3350 . . . . . . . . . . . . . . . 3-351
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
Figure 3-143 EXMR Connection to HiPath 3500 and HiPath 3300 . . . . . . . . . . . . . . 3-351
Figure 3-144 EVM (S30807-Q6945-X) - Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 3-353
Figure 3-145 EXMNA (for U.S. only) (S30807-Q6923-X) . . . . . . . . . . . . . . . . . . . . . 3-354
Figure 3-146 EXMNA (for U.S. only) - Slot for HiPath 3550 and HiPath 3350 . . . . . 3-354
Figure 3-147 GEE12, GEE16, GEE50 (not for U.S.) - Interfaces (S30817-Q951-Axxx) . . . .
3-356
Figure 3-148 HOPE (for U.S. only) (S30122-Q7078-X; S30122-Q7079-X) . . . . . . . . 3-358
Figure 3-149 OPAL (C39195-A7001-B130) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-360
Figure 3-150 OPALR (C39195-A7001-B142) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-361
Figure 3-151 ALUM Using PFT1/PFT4 (not for U.S.) . . . . . . . . . . . . . . . . . . . . . . . . . 3-362
Figure 3-152 Installation Location of PFT1 and PFT4 (MDFU/MDFU-E) (not for U.S.) 3-363
Figure 3-153 PFT1 (S30777-Q539-X) and PFT4 (S30777-Q540-X) Board Assignment . . . .
3-364
Figure 3-154 REALS (S30807-Q6629-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-366
Figure 3-155 REALS Slots in the Basic Cabinet (With Outer Panel Mounted). . . . . . 3-367
Figure 3-156 STBG4 (for France only) - Interfaces (S30817-Q934-A). . . . . . . . . . . . 3-370
Figure 3-157 STRB Interfaces (S30817-Q932-A). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-372
Figure 3-158 STRBR Interfaces (S30817-Q932-Z) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-372
Figure 3-159 STRB and STRBR Board Relay and Sensor Functions . . . . . . . . . . . . 3-373
Figure 3-160 V24/1 (not for U.S.) (S30807-Q6916-X100) . . . . . . . . . . . . . . . . . . . . . 3-377
Figure 3-161 HiPath 3550 and HiPath 3350 - V.24 Connections . . . . . . . . . . . . . . . 3-377
Figure 3-162 V.24 (RS-232) Connector Assignment, HiPath 3550 and HiPath 3350 3-378
Figure 3-163 V.24 Cable Assignment (C30267-Z355-A25) . . . . . . . . . . . . . . . . . . . . 3-380
Figure 4-1 HiPath 3800 - Setting Up the Basic Cabinet . . . . . . . . . . . . . . . . . . . . . . . 4-8
Figure 4-2 HiPath 3800 - Positioning the Cabinet Feet . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-3 HiPath 3800 - Installing a Stacked Two-Cabinet System (Rear View) . . 4-11
Figure 4-4 HiPath 3800 - Installing a Two-Cabinet System Side by Side (Rear View). . . .
4-13
Figure 4-5 HiPath 3800 - Grounding the System Cabinets and Main Distribution Frame
(nor for U.S.) 4-15
Figure 4-6 HiPath 3800 - Grounding Option 1a (not for USA) . . . . . . . . . . . . . . . . . 4-16
Figure 4-7 HiPath 3800 - Grounding Option 1b (not for USA) . . . . . . . . . . . . . . . . . 4-16
Figure 4-8 HiPath 3800 - Earth ground connection (for U.S. only) . . . . . . . . . . . . . 4-18
Figure 4-9 HiPath 3800 - System Cabinet with Plastic Cover . . . . . . . . . . . . . . . . . 4-21
Figure 4-10 HiPath 3800 - Installation Examples in the 19-Inch Cabinet . . . . . . . . . . 4-22
Figure 4-11 HiPath 3800 - Removing Cabinet Feet . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Figure 4-12 HiPath 3800 - Installing System Cabinets in 19-Inch Cabinet. . . . . . . . . 4-26
Figure 4-13 HiPath 3800- Grounding the Systems and Patch Panels in a 19-Inch Cabinet
4-29
Figure 4-14 HiPath 3800 - Board Slots in the Basic Cabinet . . . . . . . . . . . . . . . . . . . 4-32
Figure 4-15 HiPath 3800 - Board Slots in the Expansion Cabinet . . . . . . . . . . . . . . . 4-33
Figure 4-16 HiPath 3800 - Removing/Inserting the Board Using the Board Wrench . 4-35
Figure 4-17 Installing the Board Shielding Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Figure 4-18 HiPath 3800 - cPCI Box CSAPE in the Basic Cabinet with Panel Mounted . . .
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
4-36
Figure 4-19 HiPath 3800 - Installing the LUNA2 Power Supply Unit . . . . . . . . . . . . . . 4-37
Figure 4-20 HiPath 3800 - Slots for LUNA2 and REALS in the Basic Cabinet (With Outer
Panel Mounted) 4-38
Figure 4-21 HiPath 3800 - Slots for LUNA2 in the Expansion Cabinet (With Outer Panel
Mounted) 4-38
Figure 4-22 HiPath 3800 - Installing the REALS Board . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Figure 4-23 SIVAPAC-SIPAC Board Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Figure 4-24 Installing the SIVAPAC-SIPAC Board Adapter. . . . . . . . . . . . . . . . . . . . . 4-43
Figure 4-25 Replacing the Board Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Figure 4-26 HiPath 3800 - Initialization of Subscriber Line Circuits and Ports . . . . . . 4-45
Figure 4-27 HiPath 3800 - PCM Highways in the Basic Cabinet . . . . . . . . . . . . . . . . . 4-46
Figure 4-28 HiPath 3800 - PCM Highways in the Expansion Cabinet . . . . . . . . . . . . . 4-47
Figure 4-29 HiPath 3800 - Backplane (S30804-Q5392-X) of the Basic Cabinet . . . . . 4-52
Figure 4-30 HiPath 3800 - Connectors and Jacks on the Backplane of the Basic Cabinet .
4-53
Figure 4-31 HiPath 3800 - Expansion Cabinet Backplane (S30804-Q5393-X) . . . . . . 4-55
Figure 4-32 HiPath 3800 - Connectors and Jacks on the Backplane of the Expansion Cab-
inet 4-56
Figure 4-33 HiPath 3800 - Backplane of the Basic Cabinet with Mounted Filler Panels . . .
4-60
Figure 4-34 HiPath 3800 - connector panels with RJ45 Jacks . . . . . . . . . . . . . . . . . . 4-61
Figure 4-35 HiPath 3800 - Connector Panel with CHAMP Jack (for U.S. only). . . . . . 4-63
Figure 4-36 HiPath 3800 - Connector Panel with Two SIPAC 1 SU Connectors (S30807-
Q6631-X) 4-64
Figure 4-37 MDFU-E - Layout and Dimensions (669.0 x 328.8 x 125.4 mm) . . . . . . . 4-67
Figure 4-38 Assignment (Numbering) of the Splitting/Jumper Strips (view from above) . . .
4-69
Figure 4-39 Stripping an Open-End Cable for the MDFU-E . . . . . . . . . . . . . . . . . . . . 4-70
Figure 4-40 Patch Panel S30807-K6143-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Figure 4-41 Installing the External Patch Panel in the 19-Inch Cabinet. . . . . . . . . . . . 4-73
Figure 4-42 Layout of the Patch Panel S30807-K6143-X for Different Peripheral Boards .
4-74
Figure 4-43 Assignment of Patch Panel S30807-K6143-X . . . . . . . . . . . . . . . . . . . . . 4-75
Figure 4-44 S0 Patch Panel C39104-Z7001-B3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Figure 4-45 Installing the External S0 Patch Panel in the 19-Inch Cabinet . . . . . . . . . 4-77
Figure 4-46 Assignment of the S0 Patch Panel C39104-Z7001-B3. . . . . . . . . . . . . . . 4-78
Figure 4-47 Laying Wire Pairs at the S0 Patch Panel . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Figure 4-48 Stripping the Open-End Cable for the S0 Patch Panel . . . . . . . . . . . . . . . 4-79
Figure 4-49 HiPath 3550 and HiPath 3350 - Space Requirements (for U.S. only) . . . 4-88
Figure 4-50 MDFU - Layout and Dimensions (367.0 x 328.8 x 125.4 mm) (not for U.S.) . .
4-91
Figure 4-51 HiPath 3550 and HiPath 3350 - Wall Attachment. . . . . . . . . . . . . . . . . . . 4-94
Figure 4-52 HiPath 3550 and HiPath 3350 - Wall Attachment. . . . . . . . . . . . . . . . . . . 4-94
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
Figure 4-53 HiPath 3550, HiPath 3350 - Grounding an External Main Distribution Frame .
4-97
Figure 4-54 Layout of CABLU S30269-Z41-A30 (Length = 3 m) . . . . . . . . . . . . . . . . 4-99
Figure 4-55 HiPath 3550 - Backplane port for peripheral board . . . . . . . . . . . . . . . . 4-100
Figure 4-56 Integrated Distribution Frame - Slip-On Connector Screw Connections 4-101
Figure 4-57 HiPath 3550 and HiPath 3350 - Power Cable with Ferrite Sleeve . . . . 4-103
Figure 4-58 HiPath 3550 - Wall Housing System Overview . . . . . . . . . . . . . . . . . . . 4-105
Figure 4-59 HiPath 3550 - Slots in the Wall Housing . . . . . . . . . . . . . . . . . . . . . . . . 4-106
Figure 4-60 HiPath 3550 - Option Adapter Long (OPAL) . . . . . . . . . . . . . . . . . . . . . 4-106
Figure 4-61 HiPath 3350 - Wall Housing System Overview . . . . . . . . . . . . . . . . . . . 4-107
Figure 4-62 HiPath 3350 - Slots in the Wall Housing . . . . . . . . . . . . . . . . . . . . . . . . 4-107
Figure 4-63 HiPath 3500 and HiPath 3300 - Wall Installation (for U.S.). . . . . . . . . . 4-113
Figure 4-64 HiPath 3500 and HiPath 3300 - Mounting the 19-Inch Cabinet . . . . . . 4-115
Figure 4-65 HiPath 3500 and HiPath 3300 - Grounding. . . . . . . . . . . . . . . . . . . . . . 4-117
Figure 4-66 HiPath 3500 and HiPath 3300 connection cable for the ECR PB3000 . 4-118
Figure 4-67 HiPath 3500 - Slot Levels in the 19-Inch Housing. . . . . . . . . . . . . . . . . 4-120
Figure 4-68 HiPath 3300 - Slot Levels in the 19-Inch Housing. . . . . . . . . . . . . . . . . 4-121
Figure 6-1 Customer Data Exchange Between the Feature Server and Nodes. . . . . 6-4
Figure 6-2 Feature Server Services and Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Figure 6-3 P 500 UPS - Front and Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
Figure 8-1 Licensing Process with Central License Server (CLS) . . . . . . . . . . . . . . . 8-3
Figure 8-2 Distribution of Licenses with HiPath 3000/5000 Manager E . . . . . . . . . . . 8-9
Figure 8-3 Procedure for Licensing optiClient Attendant V8 on HiPath 3000 V7 . . . 8-27
Figure 9-1 Sample Connection of a CDR Printer to HiPath 3000. . . . . . . . . . . . . . . . 9-4
Figure 9-2 Front Panel of the PB3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Figure 9-3 Back of the PB3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Figure 9-4 PB3000 - HiPath 3300/3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Figure 9-5 PB3000 - HiPath 3350/3550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Figure 9-6 PB3000 - HiPath 3800. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Figure 9-7 XBatt. and X7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Figure 9-8 PB3000 with batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Figure 9-9 PB3000 with batteries and LUNA2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Figure 9-10 PB3000 expanded with batteries and LUNA2 . . . . . . . . . . . . . . . . . . . . . 9-14
Figure 9-11 ECR Front Panel (155 x 440 x 380 mm) . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Figure 9-12 ECR Rear Panel With Connecting Elements . . . . . . . . . . . . . . . . . . . . . 9-23
Figure 9-13 HiPath 3500, HiPath 3300 - ECR with batteries . . . . . . . . . . . . . . . . . . . 9-26
Figure 9-14 ECR With Built-In Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Figure 9-15 HiPath 3500, HiPath 3300 - ECR With Batteries and EPSU2-R . . . . . . . 9-33
Figure 9-16 ECR with Built-In EPSU2-R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Figure 9-17 Connecting the Fan to the EPSU2-R . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Figure 9-18 Placement of the Fan in the ECR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Figure 9-19 Connection Options for Entrance Telephones . . . . . . . . . . . . . . . . . . . . 9-38
Figure 9-20 Direct Connection of Entrance Telephones. . . . . . . . . . . . . . . . . . . . . . . 9-38
Figure 9-21 Connecting DoorCom Analog to HiPath 3000. . . . . . . . . . . . . . . . . . . . . 9-39
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
Figure 9-22 Connecting Speakers to an Analog Station Port . . . . . . . . . . . . . . . . . . . 9-41

Figure 9-23 Connecting Speakers to an Analog Trunk Port . . . . . . . . . . . . . . . . . . . . 9-42
Figure 9-24 DCDR – front view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
Figure 9-25 HiPath 3800 - Examples for installation in a DCDT in a 19-inch cabinet . 9-45
Figure 9-26 DCDR – rear view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Figure 9-27 HiPath 3800 – Example of connecting the DCDR (rear view of the 19-inch cab-
inet) 9-47
Figure 9-28 Configuration differences between V4.0 and V5.0 or later . . . . . . . . . . . . 9-50
Figure 9-29 CDB Conversion From V4.0 to V5.0 or Later (Part 1 of 4) . . . . . . . . . . . . 9-51
Figure 10-1 OpenStage 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Figure 10-4 OpenStage 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Figure 10-5 OpenStage 80 – CorNet-IP (HFA) connection variant pictured . . . . . . . 10-13
Figure 10-6 OpenStage 40 (CorNet-IP Connection Variant) – Connections on Telephone
Bottom 10-16
Figure 10-7 OpenStage 60, OpenStage 80 (CorNet-IP Connection Variant) – Connections
on Telephone Bottom 10-17
Figure 10-8 OpenStage 40 (TDM Connection Variant) – Connections on Telephone Bot-
tom 10-18
Figure 10-9 OpenStage 60, OpenStage 80 (TDM Connection Variant) – Connections on
Telephone Bottom 10-19
Figure 10-10 OpenStage Key Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Figure 10-11 OpenStage BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Figure 10-12 OpenStage terminals (CorNet-IP Connection Variant) – Connection of the Ex-
ternal Power Supply Unit 10-30
Figure 10-13 OpenStage terminals (TDM Connection Variant) – Connection of the External
Power Supply Unit 10-31
Figure 10-14 OpenStage PhoneAdapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Figure 10-15 Western-Modular jack (RJ12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Figure 10-16 Acoustic Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Figure 10-17 Headsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Figure 10-18 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Figure 10-19 USB Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Figure 10-20 optiPoint 410 entry, 410 entry S - Standard Key Assignment . . . . . . . . 10-41
Figure 10-21 optiPoint 410 economy, 410 economy S - Standard Key Assignment . . 10-43
Figure 10-22 optiPoint 410 economy plus, 410 economy plus S - Standard Key Assignment
10-45
Figure 10-23 optiPoint 410 standard, 410 standard S - Standard Key Assignment . . 10-47
Figure 10-24 optiPoint 410 advance, 410 advance S - Standard Key Assignment . . . 10-49
Figure 10-25 optiPoint 420 economy, 420 economy S - Standard Key Assignment . . 10-51
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
Figure 10-26 optiPoint 420 economy plus, economy plus S - Standard Key Assignment . . .
10-53
Figure 10-27 optiPoint 420 standard, 420 standard S - Standard Key Assignment . . 10-55
Figure 10-28 optiPoint 420 advance, 420 advance S - Standard Key Assignment . . 10-57
Figure 10-29 optiPoint 410, 420, 410 S, 420 S - Connection Options . . . . . . . . . . . . 10-59
Figure 10-30 optiPoint self labeling key module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-63
Figure 10-31 optiPoint 410 display module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-64
Figure 10-32 optiPoint 150 S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-73
Figure 10-33 optiPoint 600 office - Default Key Assignment . . . . . . . . . . . . . . . . . . . 10-75
Figure 10-34 optiPoint 500 entry - Standard Key Assignment (Default). . . . . . . . . . . 10-77
Figure 10-35 optiPoint 500 economy (not for U.S.) Standard Key Layout. . . . . . . . . 10-78
Figure 10-36 optiPoint 500 basic - Standard Key Assignment (Default) . . . . . . . . . . 10-79
Figure 10-37 optiPoint 500 standard - Standard Key Assignment (Default). . . . . . . . 10-81
Figure 10-38 optiPoint 500 advance - Standard Key Assignment (Default) . . . . . . . . 10-83
Figure 10-39 optiPoint 500 Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-86
Figure 10-40 optiPoint key module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-89
Figure 10-41 optiPoint BLF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-90
Figure 10-42 optiPoint application module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-91
Figure 10-43 optiPoint 500 Option Bays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-93
Figure 10-44 optiPoint analog adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-94
Figure 10-45 optiPoint ISDN adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-95
Figure 10-46 optiPoint phone adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-96
Figure 10-47 Example of a Host-Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . 10-97
Figure 10-48 optiPoint acoustic adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-98
Figure 10-49 Y Cable for optiPoint acoustic adapter . . . . . . . . . . . . . . . . . . . . . . . . . 10-99
Figure 10-50 optiPoint recorder adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-101
Figure 10-51 optiLog 4me. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-107
Figure 10-52 Example: External AC Adapter Connection . . . . . . . . . . . . . . . . . . . . 10-110
Figure 10-53 Example: Corded and Cordless Headsets . . . . . . . . . . . . . . . . . . . . . 10-112
Figure 10-54 HiPath AP 1120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-116
Figure 10-55 optiPoint 500 standard: Standard Key Layout optiPoint Attendant . . . 10-118
Figure 11-1 BS3/1 S30807-H5482-X Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Figure 11-2 BS3/1 (BS3/S) and BS3/3 in the Outdoor Cover S30122-X7469-X . . . . 11-5
Figure 11-3 Example of a Cordless Extension Connection in Networked Systems . 11-10
Figure 11-4 Incorrect DECT Configuration of Networked HiPath 3000 Systems . . . 11-11
Figure 11-5 Correct DECT Configuration when Networking HiPath 3000 Systems . 11-12
Figure 11-6 Correct DECT Configuration when Networking HiPath 3000 Systems . 11-12
Figure 12-1 Trace Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
Figure 12-2 The Screen Layout of the Trace Monitor. . . . . . . . . . . . . . . . . . . . . . . . 12-31
Figure 12-3 HiPath 5000 State Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-40
Figure 12-4 HiPath 5000 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42
Figure 12-5 log.txt File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
Figure 12-6 Example of Remote Service with HiPath 3000 . . . . . . . . . . . . . . . . . . . 12-89
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOF.fm
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Nur für den internen Gebrauch Tables
Tables 0
Table 1-1 Information on the Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Table 2-1 Boards for HiPath 3800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Table 2-6 HiPath 3000/5000 - System-Specific Capacity Limits (Maximum Configuration)
2-17
dia Gateways 2-19
Table 2-8 HG 1500 - Board-Specific Capacity Limits (Maximum Configuration) . . 2-20
Table 2-9 Number of Required Gateway Channels (HG 1500 Boards) . . . . . . . . . 2-22
Table 2-10 Number of Gateway Channels (DSP Channels) Required for Basic Call Sce-
narios 2-23
Table 2-11 HG 1500 - Board-Specific Sum of PPP Channels and Gateway Channels
(Maximum Numbers) 2-25
Table 2-12 Dynamic Performance Characteristics of E-Doku Version 3.0 . . . . . . . . 2-27
Table 2-13 E-Doku Version 3.0 Expansion Levels and their Maximum Points . . . . . 2-30
Table 2-14 Points for Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Table 2-15 Points for Mobile Handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Table 2-16 Points for Special Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Table 2-17 Points for Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Table 2-18 Additional Overhead for Controlling Process Flows at Devices via CTI Applica-
tions 2-35
Table 2-19 Points for Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Table 2-20 HG 1500 V3.0 Boards and Corresponding Maximum Points . . . . . . . . . 2-36
Table 2-21 Points for the PDM Modules to Increase the DSP Number. . . . . . . . . . . 2-36
Table 2-22 Points for Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Table 2-23 Points for Gateway Channels (When Using G.711 or G.729) . . . . . . . . . 2-37
Table 2-24 Points for Voice Channels (When Using G.711 or G.729) . . . . . . . . . . . 2-38
Table 2-25 Points for Data Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Table 2-26 Points for PPP Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Table 2-27 Points for VCAPI Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Table 2-28 IP Trunking Calculated with TDM Terminal Points Only . . . . . . . . . . . . . 2-42
Table 2-29 Calculation for IP Trunking and HFA Clients. . . . . . . . . . . . . . . . . . . . . . 2-43
Table 2-30 Calculation for Head Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Table 2-31 Calculation for Head Office (HiPath 3800) . . . . . . . . . . . . . . . . . . . . . . . 2-46
Table 2-32 Calculation for Each Individual Branch Office (HiPath 3500/3550): . . . . 2-47
Table 2-33 Performance Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Table 2-34 Bandwidth Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual X-1
hp3hp5shLOT.fm
Tables Nur für den internen Gebrauch
Table 2-35 Performance Calculation (1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49

Table 2-36 Performance Calculation (2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Table 2-37 Bandwidth Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Table 2-38 Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Table 2-39 Technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Table 2-40 Telephone Interface-to-Interface Ranges (with J-Y (ST) 2x2x0.6, 0.6 mm di-
ameter) 2-54
Table 2-41 Cable Lengths for Trunk Connection and Direct CorNet-N/CorNet-NQ Direct
Wiring 2-54
Table 2-42 Country-specific ring frequencies for analog subscriber line modules . . . 2-55
Table 2-43 Default numbers for HiPath 3000/5000 . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Table 2-44 Compliance with US and Canadian Standards (for U.S. and Canada only). . .
2-59
Table 3-1 HiPath 3000 - Functional Overview of All Boards Used . . . . . . . . . . . . . . . 3-2
Table 3-2 HiPath 3000 - Overview of All Boards Models Used . . . . . . . . . . . . . . . . . 3-7
Table 3-3 CBCC - LED Status Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Table 3-4 CBCC - X1 to X4 Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Table 3-5 CBCC - S0 Interface Assignment (RJ45 Jacks) . . . . . . . . . . . . . . . . . . . 3-20
Table 3-6 CBCC - V.24 Interface Assignment (SUB-D Plug) . . . . . . . . . . . . . . . . . 3-21
Table 3-7 CBCC - LAN Connector Assignment (RJ45 Jack) . . . . . . . . . . . . . . . . . . 3-21
Table 3-8 Default Numbering Plan When Using CBCC in HiPath 3550 . . . . . . . . . 3-22
Table 3-9 Default Numbering Plan When Using CBCC in HiPath 3350 . . . . . . . . . 3-23
Table 3-10 CBRC - LED Status Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Table 3-11 CBRC - X1 and X3 Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Table 3-12 CBRC - S0 Interface Assignment (RJ45 Jacks) . . . . . . . . . . . . . . . . . . . 3-29
Table 3-13 CBRC - V.24 Interface Assignment (SUB-D Plug) . . . . . . . . . . . . . . . . . 3-30
Table 3-14 CBRC - LAN Connector Assignment (RJ45 Jack) via LIM . . . . . . . . . . . 3-30
Table 3-15 Default Numbering Plan When Using CBRC in HiPath 3500 . . . . . . . . . 3-31
Table 3-16 Default Numbering Plan When Using CBRC in HiPath 3300 . . . . . . . . . 3-32
Table 3-17 CBSAP - V.24 Interface Assignment (SUB-D Plug) . . . . . . . . . . . . . . . . 3-37
Table 3-18 CBSAP - LAN Connector Assignment (RJ45 Jack) . . . . . . . . . . . . . . . . . 3-37
Table 3-19 Recommendations for CMA and CMS Implementation . . . . . . . . . . . . . . 3-40
Table 3-20 LIM - RJ45 Jack Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Table 3-21 LIMS - RJ45 Jack Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Table 3-22 LUNA2 - Bridging Times with Battery Pack 48 V/7 Ah and Upright Battery
Housing BSG 48/38 3-53
Table 3-23 Determining the Number of LUNA2 Modules Required Per Cabinet . . . . 3-58
Table 3-24 Multimedia Card Models and Applications . . . . . . . . . . . . . . . . . . . . . . . . 3-61
quencies 3-64
Table 3-26 UPSC-D - Bridging Times with Battery Pack S30122-K5928-X (48 V/1.2 Ah) .
3-69
Table 3-27 UPSC-DR - Bridging Times with four Batteries V39113-W5123-E891 (4 x 12 V/
7 Ah Batteries) 3-74
Table 3-28 DIU2U (for U.S. only) - adapter cable assignment (C39195-A7269-B625) . . .
A31003-H3570-S100-6-7620, 2008-04-01
X-2 HiPath 3000/5000 V7, Service Manual
hp3hp5shLOT.fm
3-82
Table 3-29 DIU2U (for U.S. only) - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Table 3-30 DIUN2 - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
Table 3-31 DIUN2 - 15-Pin Sub-D Jack Assignment. . . . . . . . . . . . . . . . . . . . . . . . . 3-88
Table 3-32 DIUN2 - Assigning the System Cable S30267-Z167-Axxx . . . . . . . . . . . 3-88
Table 3-33 HXGS3/HXGR3 Board Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
Table 3-34 HXGS3/HXGR3 - Extension Modules . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Table 3-35 HXGS3/HXGR3 - LAN Interface Assignment . . . . . . . . . . . . . . . . . . . . . 3-94
Table 3-36 HXGS3/HXGR3 - Assignment of V.24 Interface X10 . . . . . . . . . . . . . . . 3-95
Table 3-37 IVMNL, IVMN8 - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Table 3-38 IVMNL, IVMN8 - RJ45 Jack Assignment. . . . . . . . . . . . . . . . . . . . . . . . 3-102
Table 3-39 IVMP4, IVMP4R - Assignment of the RJ45 Jack X3 (LAN Connector) 3-105
Table 3-40 IVMP4, IVMP4R - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Table 3-41 IVMP8 and IVMP8R (not for U.S.) - Assignment of the RJ45 Jack X3 (LAN
Connector) 3-110
Table 3-42 IVMP8 and IVMP8R (not for U.S.) - LED Statuses . . . . . . . . . . . . . . . . 3-111
Table 3-43 IVMS8, IVMS8R - Assignment of the RJ45 Jack X3 (LAN Connector) 3-116
Table 3-44 IVMS8, IVMS8R - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-117
Table 3-45 IVMS8N, IVMS8NR - Assignment of the RJ45 Jack X3 (LAN Connector) . . . .
3-120
Table 3-46 IVMS8N, IVMS8NR - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121
Table 3-47 PBXXX (for selected countries only) – Seven-Segment Display. . . . . . 3-124
Table 3-48 Assigning the CAS cable S30267-Z167-A100 . . . . . . . . . . . . . . . . . . . 3-130
Table 3-49 Assigning the CAS cable S30267-Z80-A100 . . . . . . . . . . . . . . . . . . . . 3-130
Table 3-50 SLA8N (not for U.S.), SLA16N, SLA24N - LED Statuses . . . . . . . . . . . 3-132
Table 3-51 SLA8N, SLA16N, SLA24N Assignment Cable 1 (SU Xx8) (not for U.S.). . . . .
3-133
Table 3-52 SLA8N, SLA16N, SLA24N - Assignment Cable 2 (SU Xx9) (not for U.S.) . . . .
3-134
Table 3-53 SLA16N, SLA24N - Assignment (SU Xx8, Xx9) (for U.S. only). . . . . . . 3-135
Table 3-54 SLAD4, SLAD8 – assigning the ports . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138
Table 3-55 SLAD8R – assigning the ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139
Table 3-56 SLC16N (not for U.S.) - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . 3-142
Table 3-57 SLC16N (not for U.S.) - Cable Assignment. . . . . . . . . . . . . . . . . . . . . . 3-143
Number of BS3/1 Base Stations Connected to SLC16N and BS4s connected
to SLC16N (not for U.S.) 3-144
Number of BS3/3 Base Stations Connected to SLC16N and BS4s Connected
to SLC16N (not for U.S.) 3-145
Table 3-60 EPSU2 - Explanation of Indicators and Ports . . . . . . . . . . . . . . . . . . . . 3-151
Table 3-61 EPSU2 - Technical Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152
Table 3-62 SLCN (not for U.S.) - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156
Table 3-63 SLCN (not for U.S.) - SIVAPAC Connector Assignment on the Backplane . . .
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
3-157
Table 3-64 SLCN (not for U.S.) - Assignment of Connector Panels with RJ45 Jacks . . . .
3-158
nectors (Cable for Ports 1 - 16) 3-159
Table 3-66 SLMAE8, SLMAE - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-165
Table 3-67 SLMAE8, SLMAE - SIVAPAC Connector Assignment on the Backplane . . . .
3-166
Table 3-68 SLMAE8, SLMAE - Connector Panel Assignment with RJ45 Jacks . . . 3-167
only) 3-169
tors (cable for ports 1 - 16) 3-171
tors (cable for ports 17 - 24) 3-172
Table 3-72 SLMA/SLMA8 - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-174
Table 3-73 SLMA/SLMA8 - SIVAPAC Connector Assignment on the Backplane . . 3-175
Table 3-74 SLMA/SLMA8 - Connector Panel Assignment with RJ45 Jacks . . . . . . 3-176
3-178
(Cable for Ports 1 - 16) 3-180
Table 3-78 SLMA2 (for selected countries only) - LED Statuses . . . . . . . . . . . . . . . 3-183
Backplane 3-184
Jacks 3-185
CHAMP Jacks (U.S. only) 3-187
SIPAC 1 SU Connectors (Cable for Ports 1-16) 3-189
SIPAC 1 SU Connectors (Cable for Ports 17-24) 3-190
Table 3-84 SLMO2 and SLMO8 - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-192
Table 3-85 SLMO2/SLMO8 - SIVAPAC Connector Assignment on the Backplane . 3-193
Table 3-86 SLMO2/SLMO8 - Connector Panel Assignment with RJ45 Jacks . . . . . 3-195
only) 3-196
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Table 3-90 SLMO8 (not for U.S.) and SLMO24 - LED Statuses . . . . . . . . . . . . . . . 3-202
Table 3-91 SLMO8 (not for U.S.), SLMO24 - Cable 1 Assignment (SU Xx8) . . . . . 3-203
Table 3-92 SLMO8 (not for U.S.), SLMO24 - Cable 2 Assignment (SU Xx9) . . . . . 3-204
Table 3-93 SLMO24 - Assignment (SU Xx8, Xx9) (for U.S. only) . . . . . . . . . . . . . . 3-205
Table 3-94 SLU8 Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-207
Table 3-95 SLU8R Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-208
Table 3-96 STLS4 Module Interface Assignments (for U.S. only). . . . . . . . . . . . . . 3-210
Table 3-97 STLS4R Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-217
Table 3-98 STLSX2, STLSX4, STLSX4R - S0 Interface Assignment . . . . . . . . . . . 3-219
Table 3-99 STMD3 - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-224
Table 3-100 STMD3 - SIVAPAC Connector Assignment on the Backplane . . . . . . . 3-225
Table 3-101 STMD3 - Connector Panel Assignment with RJ45 Jacks . . . . . . . . . . . 3-226
Table 3-102 STMD3 - Connector Panel Assignment with CHAMP Jack (for U.S. only) . . . .
3-227
Table 3-103 STMD3 - Connector Panel Assignment with SIPAC 1 SU Connectors (Cable
for Ports 1 - 16) 3-228
Table 3-104 STMI2 - Board Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-229
Table 3-105 STMI2 - Extension Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-230
Table 3-106 STMI2 - V.24 Interface Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233
Table 3-107 STMI2 - LAN Interface Assignment (RJ45 Jacks). . . . . . . . . . . . . . . . . 3-234
Table 3-108 TCAS-2, TCASR-2 (for selected countries only) – Jumper Functions . 3-237
Table 3-109 TCAS-2, TCASR-2 (for selected countries only) – Jumper for Setting the V.24
Baud Rate 3-237
Table 3-110 TCAS-2, TCASR-2 (for selected countries only) – U-boot (firmware) States . .
3-240
States 3-240
Table 3-112 TCAS-2, TCASR-2 (for selected countries only) – Assignment of the CAS Ca-
ble C39195-A7700-B13 3-245
Table 3-113 TLA2, TLA4 (not for U.S.) - Contact Assignments . . . . . . . . . . . . . . . . 3-247
Table 3-114 TLA8 (not for U.S.) - Contact Assignments . . . . . . . . . . . . . . . . . . . . . . 3-248
Table 3-115 TLA4R (not for U.S.) - Contact Assignments . . . . . . . . . . . . . . . . . . . . 3-249
Table 3-116 TM2LP - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-252
Table 3-117 TM2LP - SIVAPAC Connector Assignment on the Backplane . . . . . . . 3-253
Table 3-118 TM2LP - Connector Panel Assignment with RJ45 Jacks . . . . . . . . . . . 3-254
Table 3-119 TM2LP - Connector Panel Assignment with CHAMP Jack (for U.S. only) . . . .
3-256
Table 3-120 TM2LP - Connector Panel Assignment with SIPAC 1 SU Connectors (Cable
for Ports 1 - 16) 3-257
Table 3-121 TMAMF - LED Statuses (H100) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-260
Table 3-122 TMAMF - LED Statuses (H0 to H7). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-260
Table 3-123 TMAMF - Cable Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261
Table 3-124 TLANI2, TLANI4 – Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . 3-264
Table 3-125 TLANI8 – Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-264
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Table 3-126 TLANI4R – Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-267

Table 3-127 TMANI8 – LED States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-270
Table 3-128 TMANI8 - SIVAPAC Connector Assignment on the Backplane . . . . . . . 3-270
Table 3-129 TMANI8 - Connector Panel Assignment with RJ45 Jacks . . . . . . . . . . . 3-272
Table 3-130 TMANI8 - Connector Panel Assignment with CHAMP Jack (for U.S. only) . . .
3-273
for Ports 1 - 16) 3-274
Table 3-132 TMC16 (for selected countries only) - LED Statuses . . . . . . . . . . . . . . . 3-277
Table 3-133 TMC16 (for selected countries only) - SIVAPAC Connector Assignment on the
Backplane 3-278
CHAMP Jack 3-279
SIPAC 1 SU Connectors (Cable for Ports 1 - 16) 3-280
Table 3-136 TMCAS - Seven-Segment Display H1 . . . . . . . . . . . . . . . . . . . . . . . . . . 3-285
Table 3-137 Assignment of the TMCAS Cable C39195-A9700-B512 . . . . . . . . . . . . 3-286
Table 3-138 Assignment of the TMCAS Cable C39195-A9700-B514 . . . . . . . . . . . . 3-286
Table 3-139 TMCAS-2 (for selected countries only) – Jumper Functions . . . . . . . . . 3-292
Table 3-140 TMCAS-2 (for selected countries only) – Jumper for Setting the V.24 Baud
Rate 3-292
Table 3-141 TMCAS-2 (for selected countries only) – U-boot (firmware) States . . . . 3-294
Table 3-142 TMCAS-2 (for selected countries only) – Linux Operating System States . . . .
3-295
S30267-Z167-A100 3-298
C39195-A7700-B14 3-298
Table 3-145 TMDID (for U.S. only) - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . 3-299
Table 3-146 TMDID (for U.S. only) - SIVAPAC Connector Assignment on the Backplane .
3-301
Table 3-147 TMDID (for U.S. only) - Connector Panel Assignment with CHAMP Jack . . . .
3-302
Table 3-148 TMDID (for U.S. only) - Connector Panel Assignment with SIPAC 1 SU Con-
nectors (Cable for Ports 1 - 16) 3-303
Table 3-149 TMDID2 (for selected countries only) - LED Statuses . . . . . . . . . . . . . . 3-306
Table 3-150 TMDID2 (for selected countries only) - SIVAPAC Connector Assignment on
the Backplane 3-307
Jacks 3-308
CHAMP Jacks (for U.S. only) 3-310
SIPAC 1 SU Connectors (cable for ports 1-16) 3-311
Table 3-154 TMEW2 - LED Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-316
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Table 3-155 TMEW2 - SIVAPAC Connector Assignment on the Backplane in Tie Trunk
Traffic via Interface Type 1A 3-317
Table 3-156 TMEW2 - SIVAPAC Connector Assignment on the Backplane with Genius An-
nouncement Device Connected (Interface Type 2): 3-318
Table 3-157 TMGL4 (for U.S. only) - Contact Assignment . . . . . . . . . . . . . . . . . . . . 3-320
Table 3-158 TMGL4R (for U.S. only) - Contact Assignment . . . . . . . . . . . . . . . . . . 3-322
Table 3-159 TMQ4 (for U.S. only) - Contact Assignment . . . . . . . . . . . . . . . . . . . . . 3-324
Table 3-160 TST1 (for U.S. only) - Contact Assignment . . . . . . . . . . . . . . . . . . . . . 3-326
Table 3-161 Contact Assignments for X2 Connector . . . . . . . . . . . . . . . . . . . . . . . . 3-329
Table 3-162 Contact Assignments for the MW8 (RJ48C) jack X5. . . . . . . . . . . . . . . 3-329
Table 3-163 4SLA (not for U.S.), 8SLA Contact Assignments . . . . . . . . . . . . . . . . . 3-332
Table 3-164 16SLA (not for U.S.) - Contact Assignments. . . . . . . . . . . . . . . . . . . . . 3-333
Table 3-165 8SLAR Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-335
Table 3-166 ALUM4 - Interface Assignments (not for U.S.) . . . . . . . . . . . . . . . . . . . 3-338
Table 3-167 ALUM4 - Interface Assignments (for U.S. only) . . . . . . . . . . . . . . . . . . 3-339
Table 3-168 AMOM - 15-Pin Sub-D Plug Assignment . . . . . . . . . . . . . . . . . . . . . . . 3-342
Table 3-169 ANI4 (for selected countries only) - LED Statuses for Trunk 1 . . . . . . . 3-344
Table 3-170 ANI4 (for selected countries only) - Contact Assignments . . . . . . . . . . 3-345
Table 3-171 ANI4R (for selected countries only) - Contact Assignment . . . . . . . . . 3-348
Table 3-172 Announcement and Music Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-349
Table 3-173 EXMNA (for U.S. only) - Contact Assignments . . . . . . . . . . . . . . . . . . 3-355
Table 3-174 GEE12/GEE16/GEE50 (not for U.S.) Modules . . . . . . . . . . . . . . . . . . . 3-356
Table 3-175 GEE12, GEE16, GEE50 (not for U.S.) - Contact Assignments. . . . . . . 3-357
Table 3-176 REALS - SIVAPAC Connector Assignment on the Backplane . . . . . . . 3-368
Table 3-177 STBG4 (for France only) - Contact Assignment. . . . . . . . . . . . . . . . . . 3-370
Table 3-178 STRB Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-374
Table 3-179 STRBR Contact Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-375
Table 3-180 Pin Assignments of the V.24 Socket X2 . . . . . . . . . . . . . . . . . . . . . . . . 3-378
Table 3-181 V.24 Adapter Assignment (C39334-Z7080-C2) . . . . . . . . . . . . . . . . . . 3-379
Table 4-1 HiPath 3800 - Installation Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Table 4-2 Electrical Connection Values (USA only) . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Table 4-3 Electrical Connection Values (USA only) . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Table 4-4 Maximum Number of Time-Division Multiplex Channels Required Per Board .
4-48
Table 4-5 HiPath 3800 - Static Traffic Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Basic Cabinet 4-54
Expansion Cabinet 4-57
Table 4-8 Color Codes for the Open-End Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Table 4-9 Visual Inspection Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Table 4-10 HiPath 3550, 3350, 3500, 3300 - System Installation Procedure . . . . . . 4-86
Table 4-11 Electrical Connection Values (for U.S. only) . . . . . . . . . . . . . . . . . . . . . . 4-89
Table 4-12 HiPath 3550 and HiPath 3350 - Static Traffic Capacity. . . . . . . . . . . . . 4-108
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Table 4-13 Electrical Connection Values (for U.S. only). . . . . . . . . . . . . . . . . . . . . . 4-111

Table 4-14 HiPath 3500 and HiPath 3300 - Static Traffic Capacity . . . . . . . . . . . . . 4-122
Table 5-1 HiPath 3800 - Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Table 5-2 RUN LED - LED Status Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Table 5-3 Entering the Country Code and Selecting the Password Type . . . . . . . . . 5-7
Table 5-4 Entering the System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Table 5-5 Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Table 5-6 RUN LED - LED Status Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Table 5-7 Entering the Country Code and Selecting the Password Type . . . . . . . . 5-15
Table 5-8 Entering the System Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Table 6-1 Feature Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Table 6-2 HW and SW Minimum Requirements for HiPath 5000. . . . . . . . . . . . . . . . 6-8
Table 6-3 RAM Space of the HiPath 5000 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Table 6-4 Prerequisites for a Single-PC Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Table 6-5 HiPath 5000 - Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Table 6-6 Software Components and Master Setup Tools. . . . . . . . . . . . . . . . . . . . 6-13
Table 6-7 Operating System Settings for HiPath 5000. . . . . . . . . . . . . . . . . . . . . . . 6-47
Table 6-8 GetAccount - Data Record Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
Table 6-9 P 500 UPS - Meaning of Displays, Switches and Jacks. . . . . . . . . . . . . . 6-62
Table 7-1 HiPath 3800 as a GW, Procedure for System Installation and Startup . . . 7-2
Table 8-1 Features Subject to Mandatory Licensing . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Table 9-1 Startup Rules for Inserting and Removing Boards . . . . . . . . . . . . . . . . . . . 9-2
Table 9-2 Technical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Table 9-3 EPSU2-R - Explanation of Display and Connecting Elements . . . . . . . . . 9-23
Table 10-1 OpenStage 10 - Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Table 10-2 OpenStage 20 CorNet-IP (HFA) and TDM – Key Features . . . . . . . . . . . 10-7
Table 10-3 OpenStage 40 CorNet-IP (HFA) and TDM – Key Features . . . . . . . . . . . 10-9
Table 10-4 OpenStage 60 CorNet-IP (HFA) and TDM – Key Features . . . . . . . . . . 10-11
Table 10-5 OpenStage 80 CorNet-IP (HFA) and TDM – Key Features . . . . . . . . . . 10-13
Table 10-6 OpenStage-Terminals - Description of Connections . . . . . . . . . . . . . . . 10-19
Table 10-7 OpenStage Terminals - Add-on Device Configurations . . . . . . . . . . . . . 10-23
Table 10-8 optiPoint 410/420, optiPoint 410 S/420 S - Description of Connections. 10-60
Table 10-9 Add-On Device Configurations for optiPoint 410/410 S and optiPoint 420/
420 S 10-65
Table 10-10 Comparison of optiPoint 600 office and optiset E memory. . . . . . . . . . . 10-74
Table 10-11 Key module configurations on an optiPoint 500 telephone . . . . . . . . . . 10-92
Table 10-12 Floating contacts on the optiPoint acoustic adapter . . . . . . . . . . . . . . . 10-100
Table 10-13 Comparison of optiset E and optiPoint 500 adapters . . . . . . . . . . . . . . 10-103
Table 10-14 Additional External Power Supply for optiPoint 500 Key Modules and Adapters
10-104
Devices and Adapters 10-105
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Table 10-16 Pin Assignment for Local Power Supply AUL:06D1284 (Euro). . . . . . 10-110
Table 10-17 Connection Options for Corded and Cordless Headsets . . . . . . . . . . 10-113
Table 11-1 HiPath Cordless Office - System Configuration for HiPath 3000 Version 3.0 . .
11-3
Table 11-2 Technical Data for Various Base Stations. . . . . . . . . . . . . . . . . . . . . . . . 11-4
Table 11-3 HiPath 3550, HiPath 3500 - Maximum Number of Corded Telephones De-
pending on the Number of BS3/1 and BS4 Base Stations Connected to CBCC
or CBRC 11-6
Table 11-4 HiPath 3550- Maximum Number of Corded Telephones Depending on the
Number of BS3/1 Base Stations Connected to SLC16N and BS4 Base Stations
Connected to SLC16N 11-7
Number of BS3/3s Connected to SLC16N and BS4s Connected to SLC16N
11-8
Table 11-6 Required B channels for Multi-SLC and System-Wide Networking. . . . . 11-9
Table 12-1 Startup Rules for Inserting and Removing Boards . . . . . . . . . . . . . . . . . 12-8
Table 12-2 RUN LED - LED Status Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Table 12-3 Power Supply Status Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
Table 12-4 HiPath 3000/5000 Manager E - Example of Status Display of Peripheral
Boards 12-24
Table 12-5 Trace Monitor Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
Table 12-6 Terminal Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
Table 12-7 HiPath 3000 Class B Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Table 12-8 Event Viewer Entries for the HiPath 5000 Server . . . . . . . . . . . . . . . . . 12-73
Table 12-9 WBM User Groups with Associated Rights . . . . . . . . . . . . . . . . . . . . . . 12-96
Table 12-10 Variable password concept: Pre-Determined User Groups and Their Access
Rights 12-102
Table 12-11 Fixed Password: Fixed User Groups and Their Access Rights. . . . . . 12-103
Table 13-1 Standards Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Table 13-2 Possible QoS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Table A-1 Starting System Administration (Service) . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Table A-2 Expert Mode Code Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Table A-3 Expert Mode Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Table B-1 Codes for Activating/Deactivating Features . . . . . . . . . . . . . . . . . . . . . . . B-1
Table B-2 Description of the Different Workpoint Client Groups . . . . . . . . . . . . . . . B-20
Table D-1 Nominal Output of the HiPath 3800 Power Supply Unit . . . . . . . . . . . . . . D-2
Table D-2 HiPath 3800 Board Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Table D-3 Nominal Output of the HiPath 3550 Power Supply Units . . . . . . . . . . . . . D-4
Table D-5 Nominal Output of the HiPath 3350Power Supply Units . . . . . . . . . . . . . . D-6
Table D-7 Nominal Output of the HiPath 3500Power Supply Units . . . . . . . . . . . . . . D-8
Table D-9 Nominal Output of the HiPath 3300Power Supply Units . . . . . . . . . . . . . D-10
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shLOT.fm
Table D-10 HiPath 3300 Board Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . D-10

Table D-11 Workpoint Client, Add-On Device, and Adapter Power Requirements. . . D-12
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shabb.fm
Nur für den internen Gebrauch Abbreviations
Abbreviations
This list contains the abbreviations used in this manual.
A
ADPCM Adaptive Difference Pulse Code Modulation
AES Advanced Encryption Standard
ALUM Trunk failure transfer
AMHOST Administration and Maintenance via HOST
ANI Automatic Number Identification
ANI4R Automatic Number Identification Rack
APS System Program System
B
BHCA Busy Hour Call Attempts
BSG Upright battery housing
BSG Key module
C
CABLU Cabling Unit
CAS Channel Associated Signaling
CBCC Central Board with Coldfire Com
CBCP Central Board with Coldfire Point
CBCPR Central Board with Coldfire Pro
CBRC Central Board Rack Com
CBSAP Central Board Synergy Access Platform
CCBS Completion of Calls to Busy Subscribers
CDB Customer Database
CLA Customer License Agent
CLC Customer License Client
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
CLM Customer License Manager
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual Y-1
hp3hp5shabb.fm
Abbreviations Nur für den internen Gebrauch
(CLS) Central License Server

CMA ADPCM clock module
CMS Clock Module Small
cPCI Compact Programmable Communication Interface
CPFSK Continuous Phase Frequency Shift Keying
CR Code Receiver
CSAPE Central Shelf Access Point Emergency
CUC Connection Unit Com
CUCR Connection Unit Com Rack
CUP Connection Unit Point
CUPR Connection Unit Point Rack
D
TW Twin Wire
DECT Digital Enhanced Cordless Telecommunications
RDT Remote Data Transfer
DiffServ Differentiated Services
DIU2U Digital Interface Unit 2 Universal
DIUN2 Digital Interface Unit ISDN
DMC Direct Media Connection
DSP Digital Signal Processor
E
EC1 First expansion cabinet
EC2 Second expansion cabinet
EBP Slot (board)
ECG Euro-ISDN–CAS-Gateway
ECGM Euro-ISDN-CAS-Gateway Maintenance
ECT Explicit Call Transfer
ESD Electrostatically Sensitive Devices
EPSU External Power Supply Unit
Erl Erlangs
eSHB Electronic Service Manual
EVM Entry Voice Mail
A31003-H3570-S100-6-7620, 2008-04-01
Y-2 HiPath 3000/5000 V7, Service Manual
hp3hp5shabb.fm
F
FSK Frequency Shift Keying
G
GAP Generic Access Profile
BC Basic cabinet
GEE Call Metering Receiving Equipment
GPCF Grace Period Configuration File
H
HA Handset
LS Loop start
HOPE Hicom Office PhoneMail Entry
HPCO HiPath ProCenter Office
HXGM HiPath Xpress Gateway Medium
HXGR HiPath Xpress Gateway Rack
HXGS HiPath Xpress Gateway Small
I
IMODN Integrated Modem Card New
IP Internet Protocol
IVML Integrated Voice Mail Large
IVMNL Integrated Voice Mail New Large
IVMP Integrated Voice Mail Point
IVMPR Integrated Voice Mail Point Rack
IVMS Integrated Voice Mail Small
IVMSR Integrated Voice Mail Small Rack
K
CDB Customer database
L
LDAP Lightweight Directory Access Protocol
LED Light Emitting Diode
LIM LAN Interface Module
LIMS LAN Interface Module for SAPP
LM Feature
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shabb.fm
M
MCID Malicious Call Identification
MDFU Main Distribution Frame Universal
MDFU-E Main Distribution Frame Universal, Enhanced
MMC Multimedia card
MSN Multiple Subscriber Number
MW Mini-Western
N
NT Network Termination
O
OPAL Option Adapter Long
OPALR Option Adapter Long Rack
P
PCM Personal Call Manager
PCM Pulse Code Modulation
PDM1 PMC DSP modules
PDS Permanent Data Service
PFT Power Failure Transfer
PSE Paging system
PSUP Power Supply Unit Point
Q
QoS Quality of Service
R
REAL Relay and Trunk Failure Transfer
REALS Relay and ALUM (power failure transfer) for SAPP
RJ Registered Jack
RLF Real License File
RSA Resilience Service Application
RSM Real-Time Services Manager
S
SELV Safety Extra-Low Voltage Circuit
SIP Session Initiation Protocol
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shabb.fm
SLA Subscriber Line Analog

SLAR Subscriber Line Analog Rack
SLC Subscriber Line Cordless
SLCN Subscriber Line Cordless New
SLMA Subscriber Line Module Analog
SLMO Subscriber Line Module Cost Optimized UP0/E
SLU Subscriber Line UP0/E
SLUR Subscriber Line UP0/E Rack
SMR Service Maintenance Release
SNG Local power supply
SNMP Simple Network Management Protocol
SP Service Provider
SRTP Secure Realtime Transport Protocol
STLS Subscriber Trunk Line S0
STLSR Subscriber And Trunk Line S0 Rack
STLSX Subscriber Trunk Line S0 with ISAC-SX
STLSXR Subscriber Trunk Line S0 with ISAC-SX Rack
STMD Subscriber And Trunk Module Digital S0
STRB Control Relay Module
STRBR Control Relay Module Rack
T
TAPI Telephony Application Programming Interface
ET Door opener
TIEL Tie Line Ear & Mouth
TLA Trunk Line Analog
TLAR Trunk Line Analog Rack
TM2LP Trunk Module Loop Procedure
TMAMF Trunk Module Analog for Multifrequency Code Signalling
TMC Trunk Modules Central office
TMCAS Trunk Module Channel Associated Signaling
TMDID Direct Inward Dialing
TMEW Trunk Modules for E&M World
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shabb.fm
TMGL4 Trunk Module Ground Start/Loop Start

TMGL4R Trunk Module Ground Start/Loop Start Rack
TML8W Trunk Module Loop Start World
TMOM Trunk Module Outgoing Multipurpose
TMS2 Trunk Module S2M
TMST1 Trunk Modules S1/T1
TS2 Trunk Module S2M
TS2R Trunk Module S2M Rack
U
UAE Universal socket
UPSC-D Uninterruptible Power Supply Com-DECT
UPSC-DR Uninterruptible Power Supply Com-DECT Rack
UPSM Uninterruptible Power Supply Modular
UPSMres Uninterruptible Power Supply Modular Reset Signal
SP Surge protector
USB Universal Serial Bus
V
VPN Virtual Private Network
W
WAP Wireless Application Protocol
WpC Workpoint Client
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
Nur für den internen Gebrauch Index
Index X
ANI4R (for selected countries only)
contact assignment 3-348
Numerics interfaces 3-347
16SLA 3-332 ANl4R (for selected countries only) 3-347
connection conditions 3-334 figure 3-347
contact assignments 3-333 Announcement and music modules 3-349
interfaces 3-333 APPCU adapter 3-125, 3-128
48 V-DC power plug on HiPath 3800 9-43 APS stamp 12-14
4SLA/8SLA 3-332 APS Transfer 12-12
connection conditions 3-334 APS transfer 12-11
contact assignments 3-332 Archive file (.arc) 12-109
interfaces 3-332 Assigning Station Numbers 5-4, 5-13
802.1p field 13-4 Attendant console versions 10-118
8SLAR 3-335
B
contact assignments 3-335
B channel modem 12-90
interfaces 3-335
Backing up system components 12-18
module specifications 3-336
Backplane HiPath 3800
A basic cabinet 4-52
AC outlet (for U.S. only) connector panels with CHAMP jack (for
HiPath 3500/HiPath 3300 4-111 U.S. only) 4-63
HiPath 3550/HiPath 3350 4-89 connector panels with RJ45 jacks 4-61
HiPath 3800 4-5 connector panels with SIPAC 1 SU con-
Access security 12-96 nectors 4-64
Accidents, reporting 1-12 expansion cabinet 4-55
Adapter cable C39195-A7269-B625 3-82 SIVAPAC connector 4-58
ALUM4 3-337 Backup Manager 12-6, 12-18
basic structure 3-340 Bandwidth 13-2
contact assignments 3-338 Bandwidth control 2-24
interfaces 3-338 Base station power supply 3-161
AMHOST 12-104 Base stations 11-2
AMOM 3-341 battery cabinet BSG 48/38 3-59
Assignment 3-342 Battery disposal 1-11
Variants 3-341 Baud rates for HiPath 3000 Manager E 12-90
Analog modem 12-90 Board overview
Analog tie trunk circuits HiPath 3300 3-14
TMEW2 3-312 HiPath 3350 3-11
ANI4 (for selected countries only) 3-343 HiPath 3500 3-13
contact assignments 3-345 HiPath 3550 3-9
installation instructions 3-346 HiPath 3800 3-7
interfaces 3-343 Boards
LED statuses 3-343 power requirement D-1
Boards (HiPath 3800)
A31003-H3570-S100-6-7620, 2008-04-01
HiPath 3000/5000 V7, Service Manual Z-1
hp3hp5shIX.fm
Index Nur für den internen Gebrauch
overview 3-7 LAN connector assignment 3-37

upgrading, replacing 9-2 V.24 interface assignment 3-37
Boards HiPath 3800 CDB backup 12-3
initializing 4-45 CDB conversion 9-50
inserting/removing 4-34 Central board
slots 4-31 HiPath 3300 3-24
Bridging times HiPath 3350 3-15
LUNA2 3-52 HiPath 3500 3-24
UPSC-D 3-69 HiPath 3550 3-15
UPSC-DR 3-74 HiPath 3800 3-33
Brute force attacks 12-99 Central Boards 3-2
BSG 48/38 3-59 Central License Server (CLS) 8-2
Changing the system time 8-29
C Checking services 12-42
Cabinet installation PB3000 9-20 Closed numbering 2-58
CABLU (HiPath 3550/HiPath 3350) 4-99 CMA 3-38
CABLUs (HiPath 3800) for MDFU or -E 4-58 CMS 3-39
Call number tables 6-7 Codecs 13-3
Capacity limits for UP0/E workpoint clients, Codes
key modules, and adapters 10-105 controlling feature B-1
CAR tables 6-7 system programming (expert mode
CAS cable shield contacts 3-246 codes) A-1
CAS protocol 3-122, 3-235, 3-281, 3-290, Common Web Service 6-38
3-327 Compliance 2-59
CBCC 3-15 CE 2-59
figure 3-18, 3-19 US and Canadian standards 2-59
LAN connector assignment via LIM 3-21 Conformity
LED status meaning 3-17 FCC 2-60
numbering plan for HiPath 3350 3-23 Connecting a printer 9-4
numbering plan for HiPath 3550 3-22 Connecting DCDR 9-43
S0 interface assignment 3-20 Connecting Direct Current Distribution Rack
V.24 interface assignment 3-21 DCDR 9-43
X1 to X4 contact assignments 3-20 Correcting errors 12-87
CBRC 3-24 Country code, entering 5-7, 5-15
figure 3-27, 3-28 Country initialization 5-7, 5-15
LAN connector assignment via LIM 3-30 Cover 4-35
LED status meaning 3-26 cPCI box CSAPE 3-79
numbering plan for HiPath 3300 3-32 CSAPE 3-79
numbering plan for HiPath 3500 3-31 Front panel 3-80
S0 interface assignment 3-29 Slot 3-81
V.24 interface assignment 3-30 CSTA/V.24 cable, assignment 3-380
X1 and X3 contact assignments 3-29 CUC 3-43
CBSAP 3-33 CUCR 3-43
diagram 3-35 CUP 3-44
front panel 3-36
A31003-H3570-S100-6-7620, 2008-04-01
Z-2 HiPath 3000/5000 V7, Service Manual
hp3hp5shIX.fm
CUPR 3-44 Emergencies 1-12

Customer data Encryption 9-62
effects due to hardware changes 12-8 Entrance telephones 9-38
Customer data backup 12-3 Environmental conditions 2-65
Customer database (CDB) conversion 9-50 EPSU2 3-150
Customer License Agent (CLA) 8-2, 12-45 EPSU2-R 9-32
Customer License Manager (CLM) 8-2, Error messages
12-45 HiPath 3000 12-47
HiPath 5000 12-73
D
Error signaling interval 12-93
DBSAP 3-45
ET adapter 9-38
figure 3-45
Euro-ISDN–CAS gateway ECG 3-281, 3-327
Delay 13-2
Event Viewer for HiPath 5000 12-38
Deployment and Licensing Service 10-15,
error messages 12-73
10-58, 10-67
Eventlog for HiPath 3000 12-37
Deployment tool 10-67
Determining system information 12-17
Eventlog for HiPath 5000 12-38
Determining system software 12-16
Determining the software image 12-16
EVM 3-352
DHCP server 10-68
interfaces 3-353
Diagnosis options 12-22
Exchanging boards 12-10
DiffServ code point 13-4
Exchanging telephones 12-10
Digital modem 12-90
Exchanging workpoint clients 12-10
Direct Media Connection DMC 2-25
EXM
Disposal of electrical/electronic devices 1-11
slot for HiPath 3550/HiPath 3350 3-350
DIU2U (for U.S. only) 3-82
EXMNA (for U.S. only) 3-354
front panel 3-83
contact assignments 3-355
LED statuses 3-84
figure 3-354
LEDs 3-83 slot in HiPath 3550 and HiPath 3350
DIUN2 3-85
3-354
assigning the system cable 3-88 EXMR
front panel 3-85 connection to HiPath 3500 and HiPath
LED statuses 3-86
3300 3-351
switches, display 3-85 EXMR connection to HiPath 3550 and HiPath
DLI function 10-67 3350 3-351
DoorCom Analog 9-39
Expansion cabinet rack (ECR), installing
Dynamic Configuration Rules 2-27 9-21
E Expert mode codes
E.164 numbering 2-58 account code A-4
ECG cabinet 3-281, 3-327 analog CO interface A-17
ECG protocol converter 3-281, 3-327 announcement/music A-21
ECGM tool 3-122, 3-283, 3-288 attendant A-29
ECR, installing 9-21 call detail recording A-3
Electrical environment 2-3 Call distribution A-27
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
CO call privileges A-6 interfaces 3-356

codes A-20 modules 3-356
configure station A-4 GetAccount 6-56
DISA A-29 Gigaset CX340isdn 10-131
displays A-11 Gigaset M1 professional 10-125
door relays A-21 Gigaset M2 professional 10-126
edit CDB data A-22 Gigaset SL1 professional 10-124
incoming calls A-7 Gigaset SL2 professional 10-124
ISDN parameters A-12 Grace period 8-7
Least Cost Routing (LCR) A-29 Ground loops (HiPath 3800) 4-14, 4-30
networking A-10 Grounding
radio paging equipment A-28 ext. MDF (HiPath 3550) 4-95
relays A-21 HiPath 3500/HiPath 3300 4-116
remote service A-27 HiPath 3800 (19-inch cabinet installation)
sensors A-22 4-27, 4-30
speed dialing system A-3 HiPath 3800 (standalone installation)
system details A-22 4-14, 4-19
system settings A-17
H
traffic restriction A-10
H.323 protocol 13-2
Extended Fast Connect (EFC) 9-55
HDLC highways for HiPath 3800 4-46
Extension connection 11-9
HG 1500
External power supply EPSU2 3-150
boards 3-89, 3-229
External power supply, EPSU2-R 9-32
hardware requirements 9-49
F resetting the signaling gateway 12-87
Fan connection (in ECR) 9-35 techn. data (resources) of boards 2-19
Fan kit for HXGS3 in HiPath 3550/HiPath HG 1500 capacity limits 2-20
3350 3-96 Hicom Office PhoneMail Entry board (for U.S.
Feature Server 6-4 only) 3-358
trace files 12-29 hicom.pds 6-51, 12-4
Ferrite for HiPath 3550/HiPath 3350 4-102 Hidden numbering 2-58
Firewall C-1 HiPath 3000 2-3
Fix Release 12-16 HiPath 3000, upgrading (HW/SW) 9-48
FM Reporting Client 6-19, 6-25, 6-39, E-1 HiPath 3000/5000 capacity limits 2-17
FM Reporting client 6-23, 6-38 HiPath 3300
as a gateway 7-8
G design and dimensions 2-9
Gateway installation 4-85
HiPath 3300 7-8 numbering plan 3-32
HiPath 3500 7-5 startup 5-11
HiPath 3800 7-2 system environment 2-14
Gateway channels (HG 1500) 2-21 HiPath 3350
Gateway functionality (HG 1500) 2-21 CAS cable shield contacts 3-246
GEE12/GEE16/GEE50 (not for U.S.) 3-356 design and dimensions 2-7
Contact assignments 3-357 installation 4-85
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
numbering plan 3-23 HiPath AP 1120 10-116

startup 5-11 HiPath ComScendo Service 2-15, 6-2
system environment 2-12 configuration 6-50
HiPath 3500 reloading 6-51
as a gateway 7-5 State viewer 12-40
design and dimensions 2-8 HiPath Cordless Office 11-1
installation 4-85 Base stations 11-2
numbering plan 3-31 capacity limits 11-6
startup 5-11 configuring 10-127
system environment 2-13 EPSU2 external power supply 3-150
HiPath 3550 extension connection 11-9
CAS cable shield contacts 3-246 login window 10-127
design and dimensions 2-6 Mobile telephones 10-124
installation 4-85 Multi-SLC 11-9
numbering plan 3-22 outdoor cover 11-5
startup 5-11 single-cell BS 11-2, 11-3
system environment 2-11 SLC16N (not for U.S.) 3-140
HiPath 3800 supplying power to base stations 3-146
as a gateway 7-2 system configuration 11-3
design and dimensions 2-4 system numbers 10-127
installation 4-2 system-wide network 11-9
startup 5-2 tech. base station data 11-4
system environment 2-10 HiPath Entry Voice Mail EVM 3-352
HiPath 3800 installation HiPath Fault Management 12-44
installing boards 4-31 installing 6-30
mounting connector panels 4-40 HiPath Inventory Manager 12-17
HiPath 5000 2-15, 6-1 analysis 12-46
basic configuration 6-49 installing 6-36
configuring RSM 6-52 HiPath License Management 6-46, 8-2
deleting all components 6-43 HiPath Manager PCM 6-56
Feature Server 6-4 HiPath Manager PCM Trace Monitor 12-29
HiPath Manager PCM Trace Monitor HiPath Software Manager
12-29 analysis 12-46
operating system settings 6-47 APS transfer 12-15
Presence Manager 6-6 backing up customer data 12-6
RAM requirements 6-8 backing up system components 12-18
requirements 6-8 determining system information 12-17
retrofitting 6-43 HiPath User Management 12-20
software structure 6-4 HiPath Xpressions Compact
startup, installation 6-11 boards 3-99, 3-103, 3-107, 3-112, 3-118
Status viewer 12-40 HOPE (for U.S. only) 3-358
updating 6-43 components 3-358
upgrading 6-44 figure 3-358
HiPath All-in-One 3-79 Hotfix 12-16
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
HXGM3 system overview HiPath 3350 4-107

techn. data (resources) 2-19 system overview HiPath 3550 4-105
HXGR3 3-89 tools and resources 4-85
extension modules 3-91 unpacking the components 4-90
figure 3-92 visual inspection 4-109
interfaces 3-93 Installation HiPath 3800 4-2
LAN interfaces 3-94 19-inch cabinet installation 4-20
techn. data (resources) 2-19 checking the grounding 4-30
V.24 interface 3-95 grounding 4-27
versions 3-90 installation site 4-20
HXGS3 3-89 installing the system cabinet 4-24
extension modules 3-91 unpacking the components 4-23
fan kit for HiPath 3550/HiPath 3350 3-96 connection cable to backplane 4-51
figure 3-91 inserting patch panel 4-72
interfaces 3-93 inserting S0 patch panel 4-76
LAN cable shield contacting 4-102 installing subboards 4-81
LAN interfaces 3-94 loading system software 4-81
techn. data (resources) 2-19 procedure 4-3
V.24 interface 3-95 resources, tools 4-2
versions 3-90 standalone installation 4-4
attaching covers 4-84
I checking grounding 4-19
IMODN 3-47, 12-90 grounding 4-14
Information on the intranet 1-16 installation site 4-4
Installation HiPath 3500/HiPath 3300 4-85 setting up system cabinets 4-7
grounding the system 4-116 single cabinet 4-8
installation in a 19-inch cabinet 4-114 two cabinets (stacked) 4-9
installation site 4-111 two-cabinet system (side by side)
installation versions 4-110 4-12
procedure 4-86 unpacking the components 4-6
slots HiPath 3300 4-121 striping an open-end cable for patch pan-
slots HiPath 3500 4-120 el 4-79
tools and resources 4-85 stripping an open-end cable for the
unpacking the components 4-112 MDFU-E 4-70
visual inspection 4-123 visual inspection 4-83
wall installation 4-113 Installing HiPath ComScendo Service 6-21
Installation HiPath 3550/HiPath 3350 4-85 Installing subboards 4-81
attaching ferrite 4-102 Integrated modem IMODN 3-47, 12-90
attaching the system to the wall 4-94 Internet telephony 2-23, 10-37, 10-71
connecting the cable 4-99 Internet telephony phone numbers 2-58
installation site 4-87 Internet Telephony Service Provider (ITSP)
MDFU 4-95 2-58
procedure 4-86 Internet Telephony Service Provider ITSP
slots HiPath 3350 4-107 2-23
slots HiPath 3550 4-106
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
IP network requirements 13-2 L

IP protocols C-1 License Failure Period 8-7
IP workpoint administration via the system Licensing 6-46, 8-1
10-67 analysis 12-45
IP workpoints, software upgrades 10-69 error 8-7
ISDN Message Decoder 12-28 Feature Server 8-12
ISDN routing (HG 1500) 2-25 features subject to mandatory licensing
ITSP client user account 2-58 8-4
ITSP client user ID 2-58 grace period 8-7
ITSP system ID 2-58 HiPath License Management 6-46, 8-2
IVMNL, IVMN8 License Failure Period 8-7
front panel 3-100 link to MAC address 8-13
LED statuses 3-101 optiClient Attendant 8-27
IVMNL/IVMN8 3-99 procedure with HiPath 3000 Manager E
LEDs 3-100 8-8
lockout switch, reset board 3-101 protection against manipulation 8-29
IVMP4/IVMP4R 3-103 replacing hardware 8-24
figure 3-104 scenarios 8-13
LAN connector assignment 3-105 upgrading 8-18
LED statuses 3-106 Lightning Protection 5-2, 5-12, 7-2, 7-5, 7-8
lockout switch, reset board 3-104 LIM 3-48
IVMP8/IVMP8R (not for U.S.) 3-107 LIMS 3-49
figure 3-109 Local power supply, AC adapters 10-109
LAN connector assignment 3-110 LOG area 12-106, 12-109
LED statuses 3-111 log.txt file 12-43
lockout switch, reset board 3-109 LUNA2 3-51
packing protection covering 3-108 bridging times 3-52
IVMS8/IVMS8R 3-112 calculating number required 3-58
figure 3-114 figure 3-54
LAN connector assignment 3-116 indicators and switches 3-54
LED statuses 3-117
M
lockout switch 3-114
MAC address 8-13
packing protection covering 3-113
Main distribution frame 4-67, 4-90, 4-95
IVMS8N/IVMS8NR 3-118
Main distribution frame (HiPath 3550/ HiPath
figure 3-119
3350)
LAN connector assignment 3-120
installation 4-90
LED statuses 3-121
Major Release 12-16
lockout switch, reset board 3-119
MDFU 4-90, 4-95
packing protection covering 3-118
MDFU-E 4-67
K Minor Release 12-16
Key assignment 10-61, 10-88 MMC 3-61
Key programming 10-61, 10-88 replacing 12-11
Mobile telephones 10-124
check login status 10-129
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
logging on to the system 10-127 accessories 10-109

Multimedia card 3-61 Add-on device configurations 10-65
Multi-SLC 11-9 Connection and startup 10-58
Connection options 10-59
N optiPoint 410 advance 10-48
Network Analysis 13-6 optiPoint 410 display module 10-64
Network Termination NT optiPoint 410 economy 10-42
cable set for Spain/Portugal (HiPath optiPoint 410 economy plus 10-44
3550/HiPath 3500) 3-331 optiPoint 410 entry 10-40
S2M connection (HiPath 3550/HiPath optiPoint 410 standard 10-46
3500 (not for U.S.) optiPoint 500 adapter use 10-66
NT connection 3-330 optiPoint self labeling key module 10-63
Network termination NT optiPoint 410 S 10-37
power supply (S2M, HiPath 3550/HiPath accessories 10-109
3500) 3-330 Add-on device configurations 10-65
Numbering in networked systems 2-58 Connection and startup 10-58
Numbering plan 2-57 Connection options 10-59
O optiPoint 410 advance S 10-48
Offline programming 5-10, 5-18 optiPoint 410 display module 10-64
OPAL 3-360 optiPoint 410 economy plus S 10-44
OPALR 3-360 optiPoint 410 economy S 10-42
Open numbering 2-58, 6-7 optiPoint 410 entry S 10-40
OpenStage 10-4 optiPoint 410 standard S 10-46
accessories 10-29 optiPoint 500 adapter use 10-66
add-on device configurations 10-23 optiPoint self labeling key module 10-63
connection and startup 10-15 optiPoint 420 10-37
gigabit variant 10-5 accessories 10-109
OpenStage 10 10-6 Add-on device configurations 10-65
OpenStage 20 10-7 Connection and startup 10-58
OpenStage 40 10-9 Connection options 10-59
OpenStage 60 10-11 optiPoint 410 display module 10-64
OpenStage 80 10-13 optiPoint 420 advance 10-56
OpenStage BLF 10-22 optiPoint 420 economy 10-50
OpenStage Key Module 10-22 optiPoint 420 economy plus 10-52
OpenStage PhoneAdapter 10-32 optiPoint 420 standard 10-54
OpenStage Attendant 10-118 optiPoint 500 adapter use 10-66
Operating conditions 2-65 optiPoint self labeling key module 10-63
optiClient 130 10-115 optiPoint 420 S 10-37
optiClient Attendant 10-119 accessories 10-109
Licensing 8-27 Add-on device configurations 10-65
optiLog 4me 10-107 Connection and startup 10-58
Options 3-6 Connection options 10-59
optiPoint 150 S 10-71 optiPoint 410 display module 10-64
optiPoint 410 10-37 optiPoint 420 advance S 10-56
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
optiPoint 420 economy plus S 10-52 Password protection 12-99

optiPoint 420 economy S 10-50 Password type, defining 5-7, 5-15
optiPoint 420 standard S 10-54 PB3000
optiPoint 500 adapter use 10-66 Cabinet installation 9-20
optiPoint self labeling key module 10-63 Power cabinet 9-5
optiPoint 500 10-76 Wall mounting 9-19
accessories 10-109 PBXXX 3-122
adapter configurations 10-102 Administration 3-122
connecting 10-85 Connection cable 3-125, 3-128
connection options 10-86 Front panel 3-123
connection requirements 10-84 Setup using HiPath 3000 Manager E
key module configurations 10-92 3-122
notes on power supply 10-104 Seven Segment Display 3-124
option bays 10-93 PCM segments for HiPath 3800 4-46
optiPoint 500 advance 10-82 PDM1 3-91
optiPoint 500 basic 10-79 PDMX 3-230
optiPoint 500 economy 10-78 PDS file 6-51, 12-4
optiPoint 500 entry 10-77 Peripheral Boards 3-3
optiPoint 500 standard 10-80 PFT1/PFT4 (not for U.S.) 3-362
optiPoint 500 standard SL (for U.S. only) assignment 3-364
10-80 installation location 3-363
optiPoint acoustic adapter 10-98 Phone test 12-37
optiPoint analog adapter 10-94 Pin Assignments of the V.24 Sockets 3-378
optiPoint application module 10-91 Plug’n Play startup of IP workpoints 10-68
optiPoint BLF 10-90 Port numbers C-1
optiPoint ISDN adapter 10-95 Power cabinet
optiPoint key module 10-89 Cabinet installation 9-20
optiPoint phone adapter 10-96 Components 9-8
optiPoint recorder adapter 10-101 Control, display, and ports 9-6
USB 1.1 interface 10-87 Installation options 9-10
optiPoint 600 office 10-74 LUNA2 power supply 9-18
accessories 10-109 PB3000 9-5
optiPoint application module 10-91 UPS bridging time/charging time 9-11
optiPoint Attendant 10-118 Wall mounting 9-19
optiPoint WL2 professional 10-117 Power plug (for U.S. only) HiPath 3800 4-23
optiset E privacy module 10-108 Power requirement (boards, workpoint cli-
Outdoor cover 11-5 ents, adapter) D-1
Outlet Strip with Overvoltage Protection 5-2, Power supply
5-12, 7-2, 7-5, 7-8 external applications 3-365
HiPath 3350 3-63
P
NT (HiPath 3550/HiPath 3500) 3-330
Part numbers
Power supply unit
CABLUs, open-end cables (HiPath 3800)
4-58, 4-65
Password 12-96, 12-99
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
HiPath 3800 3-51 Safety symbols 1-5

Presence Manager 6-6 Security 12-99
trace files 12-29 Server net file 6-49, 6-52
Privacy and Data Security 1-14 Service 12-1
Protocols 13-2 Service call via code 12-92
PSUP 3-63 Service maintenance release SMR 12-14
Figure 3-63 Service Manual
Configuration notes 1-2
Q Services, checking 12-42
Quality of Service QoS 13-4 Shift key 10-61, 10-88
R Siemens intranet 1-16
Ranges Signaling & Payload Encryption 9-62
CorNet-N/CorNet-NQ 2-54 Signaling & Payload Encryption SPE 9-55
telephone interfaces 2-54 Single-cell base station 11-2, 11-3
trunk connection 2-54 SIP protocol 10-37, 10-71
REALS 3-365 SIP system account 2-58
cable and connector assignment 3-367 SIVAPAC-SIPAC Board Adapter 3-122
electrical characteristics of relays 3-365 SIVAPAC-SIPAC board adapter 3-299,
slot 3-367 3-312, 4-42
special connections via relays 3-365 SLA8N/SLA16N/SLA24N 3-131
trunk failure transfer 3-365 cable and connector assignment 3-133
Reinitialization 5-5, 5-14 connection conditions 3-136
Reload 5-6, 5-15 LED statuses 3-132
Remote access immediately after installation switches and LEDs 3-131
12-92 SLAD4/SLAD8 3-137
Remote administration 12-91 interfaces 3-138
Remote connection, controlled release 12-94 SLAD8R 3-137
Remote service 12-89 interfaces 3-139
Reset board 3-114 SLC16N (not for U.S.) 3-140
RGMOD 3-64 base station power supply 3-144
Installing 3-66 cable/connector assignment 3-143
Setting 3-64 figures 3-141
Ring frequencies for analog subscriber line LED statuses 3-142
modules 2-55 lockout switch function 3-141
Routing (HG 1500) 2-25 SLCN (not for U.S.) 3-155
base station power supply 3-161
S cable and connector assignment 3-156
Safety Information distribution to HiPath 3800 cabinets
for Brazil 1-13, 5-2, 5-12 3-161
Safety information 1-5 front panel 3-155
caution 1-9 LED statuses 3-156
danger 1-6 LEDs 3-155
warning 1-8 SLMA/SLMA8 3-173
Safety Information for Australia 1-13 cable and connector assignment 3-174
SAFETY International 2-64
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
front panel 3-173 HiPath 3500/HiPath 3300 4-122

LED statuses 3-174 HiPath 3550/HiPath 3350 4-108
LEDs 3-173 HiPath 3800 4-50
SLMA2 3-182 Station diagnosis 12-26
cable and connector assignment 3-183 Station status 12-26
front panel 3-182 STBG4 (for France only) 3-370
LED statuses 3-183 contact assignments 3-370
LEDs 3-182 interfaces 3-370
SLMAE8/SLMAE 3-162 STLS 3-209
cable and connector assignment 3-165 connecting ISDN (S0) interfaces 3-211
front panel 3-164 connecting ISDN telephones 3-212
LED statuses 3-165 connecting ISDN trunk 3-211
LEDs 3-164 interfaces 3-209
touch guard 3-163 STLS4R 3-216
SLMO2/SLMO8 3-191 contact assignments 3-217
cable and connector assignment 3-193 interfaces 3-216
front panel 3-191 STLSX2/STLSX4 3-218
LED statuses 3-192 configuring ISDN (S0) interfaces 3-220
LEDs 3-191 connecting ISDN telephones 3-221
SLMO8/SLMO24 3-201 interfaces 3-219
cable and connector assignment 3-203 S0 interface assignment 3-219
figure 3-201 STLSX4R 3-218
LED statuses 3-202 configuring ISDN (S0) interfaces 3-220
SLU8 3-207 connecting ISDN telephones 3-221
contact assignments 3-207 interfaces 3-219
interfaces 3-207 S0 interface assignment 3-219
SLU8R 3-208 STMD3 3-223
contact assignments 3-208 cable and connector assignment 3-224
interfaces 3-208 front panel 3-223
SMR 12-14 LED statuses 3-224
SNMP 12-44 LEDs 3-223
snmpd.cnf 6-19, 6-25, 6-39, E-1 STMI2 3-229
Software Release Management 12-16 connections 3-231
Software update 12-14 extension modules 3-230
Software upgrade 12-14 figure 3-230
Speech recording device optiLog 4me front panel 3-232
10-107 LAN interfaces 3-234
Standards supported 13-3 techn. data (resources) 2-19
Startup V.24 interface 3-233
HiPath 3550/HiPath 3350/HiPath 3500/ variants 3-229
HiPath 3300 5-11 STRB 3-371
HiPath 3800 5-2 contact assignments 3-374
Static configuration rules 2-19 interfaces 3-372
Static traffic capacity STRBR 3-371
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
contact assignments 3-375 groups 2-35

interfaces 3-372 mobile handsets 2-33
Supplying power to base stations 3-146 special devices 2-34
Surge protector (HiPath 3800) for MDFU-E terminal devices 2-33
4-68 trunks 2-34
Surge protector (HiPath 3800) for Patch Pan- Time-division multiplex channels for HiPath
el 4-74 3800 4-46
Switches and indicators 3-34 TLA2/TLA4 (not for U.S.) 3-247
System factory default 4-31 contact assignments 3-247
System power requirement D-1 TLA4R (not for U.S.) 3-249
System software contact assignments 3-249
Determining 12-16 interfaces 3-249
System software upgrade 12-11 TLA8 (not for U.S.) 3-247
System software, installing 4-81 contact assignments 3-248
interfaces 3-247, 3-248
T TLANI2/TLANI4/TLANI8 3-262
TAPI Service Provider 6-15, 6-34 contact assignments 3-264
TCAS-2 3-235 interfaces 3-263
administration 3-243 jumper 3-263
CAS cable 3-245 TLANI4R 3-265
connections 3-238 contact assignments 3-267
impedance converter 3-245 interfaces 3-266
interfaces 3-236 jumper 3-267
jumpers 3-236 TM2LP 3-251
optional modem 3-242 cable and connector assignment 3-252
settings 3-237 front panel 3-251
seven-segment display 3-239 LED statuses 3-252
TCASR-2 3-235 LEDs 3-251
administration 3-243 TMAMF 3-258
CAS cable 3-245 cable and connector assignment 3-261
connections 3-238 DSP diagnosis, trace 3-259
front panel 3-239 figure 3-258
impedance converter 3-245 LED statuses 3-260
interfaces 3-236 TMANI8 3-268
jumpers 3-236 cable and connector assignment 3-270
optional modem 3-242 front panel 3-269
settings 3-237 jumper 3-269
seven-segment display 3-239 LED states 3-270
Technical base station data 11-4 LEDs 3-269
Technical specifications 2-53, 2-59 TMC16 3-276
Telephones 10-1 cable and connector assignment 3-277
Terminal Equipment Identifier TEI 3-223, front panel 3-276
10-131 LED statuses 3-277
thumb rule values LEDs 3-276
CTI 2-35
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
TMCAS 3-281 HiPath Inventory Manager 12-46

seven-segment display H1 3-285 HiPath Manager PCM Trace Monitor
switches, display 3-282 12-29
TMCAS-2 3-290 HiPath Software Manager 12-46
administration 3-297 in connection with SRTP 12-36
CAS cable 3-298 Traffic capacity (in Erlangs)
Front Panel 3-293 HiPath 3500/HiPath 3300 4-122
interfaces 3-291 HiPath 3550/HiPath 3350 4-108
jumpers 3-291 HiPath 3800 4-50
optional modem 3-296 Trunk diagnostics 12-25
Settings 3-292 Trunk failure transfer 3-337, 3-362, 3-365
seven-segment display 3-294 Trunk status 12-25
TMDID (for U.S. only) 3-299 TS2 (not for U.S.) 3-327
cable and connector assignment 3-300 interface assignments 3-329
front panel 3-300 interfaces 3-328
LED statuses 3-299 NT cable set for Spain/Portugal 3-331
LEDs 3-300 S2M trunk connection 3-330
TMDID2 3-304 TS2R (not for U.S.) 3-327
cable and connector assignment 3-306 interface assignments 3-329
front panel 3-305 interfaces 3-328
LED statuses 3-306 NT cable set for Spain/Portugal 3-331
LEDs 3-305 NT connection 3-330
TMDID8 (for U.S. only) S2M trunk connection 3-330
switches 3-299 TST1 (for U.S. only) 3-325
TMEW2 3-312 contact assignment 3-326
cable and connector assignment 3-316 figure 3-325
front panel 3-315
U
LED statuses 3-316
Uninterruptible power supply unit HiPath
LEDs 3-315
3500/HiPath 3300
TMGL4 (for U.S. only) 3-319
see UPSC-DR 3-73
figure 3-319
3550/HiPath 3350
TMGL4R (for U.S. only) 3-321
see UPSC-D 3-68
figure 3-321
3800
interfaces 3-321
see LUNA2 3-51
TMQ4 (for U.S. only) 3-323
Uninterruptible Power Supply Unit HiPath
5000 6-61
figure 3-323
Updating HG 1500 12-15
Trace options
Updating system software 12-15
Customer License Agent (CLA) 12-45
Upgrade Manager 12-15
Customer License Manager (CLM)
Upgrading HiPath 3000 (HW/SW) 9-48
12-45
Upgrading HiPath 5000 6-44
HiPath 3000 12-28
Upgrading the system software 12-11
A31003-H3570-S100-6-7620, 2008-04-01
hp3hp5shIX.fm
UPS P 500 6-61

UPSC-D 3-68
bridging times 3-69
connectors 3-72
figure 3-70
switches and indicators 3-71
UPSC-DR 3-73
battery pack 9-25
bridging times 3-74
connectors 3-78
figure 3-75
switches and indicators 3-77
UPSM
battery pack 9-25
USB 1.1 interface 10-87
USB V.24 Adapter 3-376
User groups 12-96
User groups and their access rights 12-102
User name 12-96
User-specific logon to WBM 12-96
V
V.24 adapter 3-379
V.24 cable, assignment 3-380
V.24 connector assignment 3-378
V.24 interfaces (HiPath 3550, HiPath 3350)
3-377
V24/1 (not for U.S.) 3-377
figure 3-377
Version hub 12-14
W
Wall mounting PB3000 9-19
Web-Based Management (WBM) 3-89,
3-229
Web-based management (WBM) 6-4
WLAN 10-117
Workpoint client power requirement D-1
Workpoint clients 10-1
A31003-H3570-S100-6-7620, 2008-04-01

Siemens Hipath 3000 5000 v7 Service Documentation

Uploaded by

Copyright:

Available Formats

Siemens Hipath 3000 5000 v7 Service Documentation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Siemens Hipath 3000 5000 v7 Service Documentation

Uploaded by

Copyright:

Available Formats

Documentation

Communication for the open minded

Siemens Enterprise Communications

Nur für den internen Gebrauch Contents

1 Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Contents Nur für den internen Gebrauch

2.5.7 DMC (Direct Media Connection) Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Nur für den internen Gebrauch Contents

2.12.1 Electrical Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65

Contents Nur für den internen Gebrauch

3.3.22 STLS2 (not for U.S.), STLS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-209

Nur für den internen Gebrauch Contents

3.4.17 V.24 Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-379

Contents Nur für den internen Gebrauch

4.2.6.6 Connecting Peripherals to the Connector Panels

Nur für den internen Gebrauch Contents

4.3.4.7 Installing the Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117

Contents Nur für den internen Gebrauch

6.6.8 Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41

Nur für den internen Gebrauch Contents

Contents Nur für den internen Gebrauch

Nur für den internen Gebrauch Contents

10.3.5 Key modules for optiPoint 410/410 S and 420/420 S . . . . . . . . . . . . . . . . . . . 10-62

Contents Nur für den internen Gebrauch

10.11 optiClient 130 V5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-115

Nur für den internen Gebrauch Contents

12.2.3.1.2 APS transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

Contents Nur für den internen Gebrauch

12.5 Remote Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-89

Nur für den internen Gebrauch Contents

D.1 HiPath 3800 Board Power Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Contents Nur für den internen Gebrauch

Important Information Nur für den internen Gebrauch

1.2 Structure of this Electronic Service Manual

Content and target group

Main topics of this manual

Important Information Nur für den internen Gebrauch

1.3 Electrical Environment

The device conforms to the EU directive 1999/5/EG, as attested by the CE

1.4 Safety Information

This symbol identifies useful information.

Important Information Nur für den internen Gebrauch

1.4.1 Safety Information: Dangers

Connecting an external battery pack, external batteries

HiPath 3500 and HiPath 3300 systems

System shutdown during maintenance work

Working on electrical circuits

Important Information Nur für den internen Gebrauch

1.4.2 Safety Information: Warnings

Replacing the lithium battery

Replacing the batteries (DC power supply)

Protective clothing and equipment

1.4.3 Safety information: Cautions

Voltage checks and measurements

Protecting electrostatically sensitive devices (ESD)

Important Information Nur für den internen Gebrauch

1.4.4 General Information

Location of safety equipment

Closing the housing cover

Fire protection and EMC requirements