19 Ted

s
HiPath
HiPath Gateway 3550
HiPath HG 3550
Technical Description
*1PA31003-H3101-C104-1-7620*
1P A31003-H3101-C104-1-7620
The device conforms to the EU guideline 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.
The informaton in this document contains general descriptions of the technical options available, which do not
always have to be present in individual cases.
The required features should therefore be specified in each individual case at the time of closing the contract.
 Siemens AG 2002 Information and Communication Networks, Hofmannstraße 51, D-81359 München, Germany
●
Reference No.: A31003-H3101-C104-1-7620

Printed in the Federal Republic of Germany.
Subject to availability. Right of modification reserved.
HiPath is a trademark of Siemens AG that is registered in several jurisdictions.
tedTOC.fm
Nur für den internen Gebrauch Content
Content 0
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-5

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1 Business advantages of IP telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Summary of features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.3 Contents of this description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.4 Associated documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
2 H.323 IP Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1 Components of H.323 networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.1 H.323 clients (terminals). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.2 Terminal adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.3 Gatekeepers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.4 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.1.5 Multipoint control units (MCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.1.6 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.1.7 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2 H.323 and related protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.1 H.225.0 Annex G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.2 H.225.0 Q.931 call setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.3 H.225.0 RAS control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.4 H.235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.5 H.245 signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.6 H.323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.7 H.341. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.8 H.450. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.9 RTP and RTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.10 TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.2.11 UDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.3 The HiPath HG 3550 as an H.323 gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.4 IP Trunking with the HiPath HG 3550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 Throughput and speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.3 Autodiscovery function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.4 Voice over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.4.1 Voice encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4.2 DTMF handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4.2.1 DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
A31003-H3101-C104-1-7620, 2002-04-25
HG3550, Technical Description 0-1
tedTOC.fm
Content Nur für den internen Gebrauch
3.4.2.2 Supported DTMF functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.4.2.3 Smart DTMF Canceller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4.3 Direct dialing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.3.1 Direct-inward dialing (DID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.3.2 Direct-outward dialing (DOD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.4 Operator zero . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.5 E.164 telephone numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.6 Interoperation with PBXs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.6.1 Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.4.6.2 Fallback to SCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.5 Layer 2 and Layer 3 prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.5.1 Brief description of layer switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.5.2 Layer 3 prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.5.3 Layer 2 prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.6 Voice quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.6.1 Automatic gain control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.6.2 Echo cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.6.3 Dynamic jitter buffering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.6.3.1 HLB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.6.3.2 TIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.6.4 Voice activity detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.7 Implementation of voice activity detection in HiPath HG 3550 . . . . . . . . . . . . . . . . . . . 3-9
3.7.1 VAD during receive and send. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.7.1.1 Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.7.1.2 Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.8 Overview of T.38 and transparent fax modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.8.1 Transparent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.8.2 T.38 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.9 Routing Information Protocol (RIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.10 Support for Hunting Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.11 Bandwidth efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.12 Conferencing using an external MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.13 Clear channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.14 Numbering plan integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
4 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 Web-based configuration and administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.1 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.1.1.1 Front panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.1.1.2 Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.1.1.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.1.1.4 Explorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.1.1.5 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.2 Command line management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.3 Simple Network Management Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
A31003-H3101-C104-1-7620, 2002-04-25
0-2 HG3550, Technical Description
tedTOC.fm
Nur für den internen Gebrauch Content
4.4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

5 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1 LAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.1 10Base-T and 100Base-TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2 Local management port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
6 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1 Board Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1.1 Microcontroller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1.2 Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.1.3 Synchronous DRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.1.4 Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.1.5 DSP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.1.6 Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.1.7 LED Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
7 Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.1 Call processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.2 Software platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.2.1 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.2.2 Real-time operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.2.2.1 Board support package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.2.2.2 DOS file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.2.2.3 True flash file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.2.3 Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.2.4 Audio stream control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.2.5 DSP software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
8 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
A31003-H3101-C104-1-7620, 2002-04-25
tedTOC.fm
Content Nur für den internen Gebrauch
A31003-H3101-C104-1-7620, 2002-04-25
tedLOF.fm
Nur für den internen Gebrauch List of Figures
List of Figures 0
Figure 1-1 Front view of HiPath HG 3550. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Figure 2-1 H.323 protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Figure 4-1 Web-based management home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Figure 4-2 WBM menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Figure 4-3 Front panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Figure 4-4 Example of an initial setup wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Figure 4-5 Explorer data represented by a tree view . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 5-1 Overview of HiPath HG 3550 ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Figure 5-2 10/100Base-TX or 10Base-T LAN interface . . . . . . . . . . . . . . . . . . . . . . . 5-1
Figure 5-3 V.24 local management port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Figure 6-1 Interfaces of the HiPath HG 3550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Figure 6-2 DSP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
A31003-H3101-C104-1-7620, 2002-04-25
tedLOF.fm
List of Figures Nur für den internen Gebrauch
A31003-H3101-C104-1-7620, 2002-04-25
tedLOT.fm
Nur für den internen Gebrauch List of Tables
List of Tables 0
Table 1-1 HiPath HG 3550 feature overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table 1-2 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Table 1-3 Overview of HiPath HG 3550 documentation and target groups . . . . . . . 1-4
Table 3-1 Received Autodiscovery data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Table 3-2 Effect of the VAD flag setting on codec availability . . . . . . . . . . . . . . . . . . 3-9
Table 3-3 Use of VAD in the send direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Table 6-1 LEDs on front of the HiPath HG 3550 board . . . . . . . . . . . . . . . . . . . . . . . 6-3
Table 8-1 List of standards and RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Table 8-2 Internet addresses for telecommunication standards . . . . . . . . . . . . . . . . 8-1
A31003-H3101-C104-1-7620, 2002-04-25
tedLOT.fm
List of Tables Nur für den internen Gebrauch
A31003-H3101-C104-1-7620, 2002-04-25
ted1.fm
Nur für den internen Gebrauch Introduction
Business advantages of IP telephony
1 Introduction
The HiPath HG 3550 is a new-generation Voice over Internet Protocol (VoIP) gateway. It is used
to through-connect connections between IP-based networks (LANs, intranets, Internet) and cir-
cuit-switched networks (ISDN, PSTN).
This Technical Description (TED) describes the functionality and the architecture of the
HiPath HG 3550.
Figure 1-1 Front view of HiPath HG 3550
This chapter gives you a first overview of the HiPath HG 3550 applications and the documen-
tation architecture. It contains the following sections:
Section 1.1, “Business advantages of IP telephony”
Section 1.2, “Summary of features”
Section 1.3, “Contents of this description”
Section 1.4, “Associated documents”
1.1 Business advantages of IP telephony

IP telephony offers companies major advantages in two main areas:
1. IP telephony between different company sites and other communication partners via the
Internet can substantially reduce communications costs.
2. Integration of all types of communication and multimedia such as IP telephony within an
enterprise‘s corporate networks or intranet makes a company’s communications infra-
structure more versatile and at the same time easier to maintain.
In both applications, it is important that sufficient standards of availability, security, and quality
of service are guaranteed.
A31003-H3101-C104-1-7620, 2002-04-25
ted1.fm
Introduction Nur für den internen Gebrauch
Summary of features
1.2 Summary of features

The HiPath HG 3550 provides a state-of-the-art routing technology for small and medium-sized
networks which is easy to deploy and manage. It has an intuitive graphical Web interface, which
provides for easy installation and maintenance.
The major features of the HiPath HG 3550 gateway are listed in Table 1-1 (see the following
chapters for details).
Feature For details see

Services
Autodiscovery Section 3.3
Voice over IP: Section 3.4
● Voice encoding
● DTMF handling
● direct dialing
● E.164 numbering
PBX interoperation: Section 3.4.6
● legacy PBXs
● IP Trunking:
– ISDN voice and data
– Group 3 fax
– Group 4 fax
– H.320 video telephony
– modem
– fallback to SCN
● clear channel
Layer switching and prioritization Section 3.5
Voice quality: Section 3.6
● automatic gain control (AGC)
● echo cancellation
● dynamic jitter buffering
● voice activity detection (VAD)
T.38 and transparent fax modes Section 3.8
Routing Information Protocol Section 3.9
LAN and WAN protocols supported
Switched-circuit network (SCN) and H.323 V2.0 gateway func- see Chapter 2
tionality
Table 1-1 HiPath HG 3550 feature overview
A31003-H3101-C104-1-7620, 2002-04-25
ted1.fm
Nur für den internen Gebrauch Introduction
Contents of this description
Feature For details see

ISDN protocols: see Section 3.4.6
● PRI:
– CorNet-NQ
LAN interfaces
10Base-T see Section 5.1.1
100Base-Tx see Section 5.1.1
Table 1-1 HiPath HG 3550 feature overview
1.3 Contents of this description

This Technical Description contains the following chapters:
No. Chapter Contents

1 Introduction gives a first overview of the HiPath HG 3550 applications, its
features, and the supplied documentation.
2 H.323 IP Telephony describes basic protocols and entities in a H.323 IP telepho-
ny network.
3 Features describes the main features of the HiPath HG 3550.
4 Management gives an overview of the HiPath HG 3550 management tools
for easy administration, configuration and maintenance.
5 Interfaces describes physical interfaces for LAN and WAN connections
to the HiPath HG 3550.
6 Hardware Architecture describes the hardware components of the
HiPath HG 3550.
7 Software Architecture provides an overview of the main software components and
protocols.
8 Standards lists the standards and RFCs related to this document in al-
phabetical order.
9 Glossary lists the technical items used in this document in alphabeti-
cal order
10 Abbreviations lists the abbreviations used in this document in alphabetical
order.
11 Index lists keywords used in this document in alphabetical order.
Table 1-2 Chapter overview
A31003-H3101-C104-1-7620, 2002-04-25
ted1.fm
Introduction Nur für den internen Gebrauch
Associated documents
1.4 Associated documents

The documentation describes how to use the HiPath HG 3550. It consists of the following man-
uals and descriptions:
● Technical Description (TED), this document
● the HiPath 3550 chapter in the Service Manual
● Administration and Maintenance
● Configuration
Each of these documents is intended for a particular target group as described below.
Document type Target group

TED The technical description is intended for everybody with a
(Technical Description) general interest in the HiPath HG 3550. It describes the
system architecture, and provides an overview of the func-
tionality of the HiPath HG 3550.
Administration and Maintenance The operating manuals are intended for those involved
Configuration with the configuration and management of access net-
works and network elements. They contain step-by-step
instructions on how to perform the various configuration
and management tasks.
Table 1-3 Overview of HiPath HG 3550 documentation and target groups
Information on the Web

Up-to-date information about the HiPath HG 3550 and information about the HiPath 4000 prod-
uct platforms is provided on the Web at http://www.hipath.com.
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
Nur für den internen Gebrauch H.323 IP Telephony
2 H.323 IP Telephony
This chapter describes basic protocols and components in an H.323 IP telephony network and
contains the following sections:
Section 2.1, “Components of H.323 networks”
Section 2.2, “H.323 and related protocols”
Section 2.3, “The HiPath HG 3550 as an H.323 gateway”
Section 2.4, “IP Trunking with the HiPath HG 3550”
Abstract
H.323 describes how voice (i.e., telephone) and fax traffic is handled on packet-based networks
such as IP networks. The relevant standards are defined in the H.323 series of ITU-T (Interna-
tional Telecommunication Union – Telecommunication Standardization Sector) recommenda-
tions.
These standards define how participating devices set up calls, exchange compressed audio
and video data, participate in multi-unit conferences, and co-operate with non-H.323 endpoints.
H.323 allows customers to use multimedia applications without changing their network (LAN)
infrastructure.
H.323 provides:
● call control and management for point-to-point and multipoint conferences,
● quality of service (QoS) control with a centralized gatekeeper component to manage media
traffic, bandwidth, and user participation,
● gateway functions enabling calls to be set up between the LAN and the public switched
telephone network (PSTN) and to H.323 standards-based terminals.
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
H.323 IP Telephony Nur für den internen Gebrauch
Components of H.323 networks
2.1 Components of H.323 networks

H.323 networks contain the following functional components:
● H.323 clients (terminals),
● terminal adapters,
● gatekeepers,
● routers,
● multipoint control units (MCU),
● servers,
● gateways.
2.1.1 H.323 clients (terminals).

An H.323 client terminates IP signaling and payload at an end user site. It provides real-time
communication. It supports voice communication and can optionally support video or data com-
munication. Typical H.323 clients are:
● IP telephones,
● videophones,
● multimedia PCs.
2.1.2 Terminal adapters

A terminal adapter connects analog clients, e.g., analog telephones or fax machines, to the
H.323 network.
2.1.3 Gatekeepers
A gatekeeper routes calls to their destinations. It provides address resolution and accounting
services. A gatekeeper provides call control services for H.323 endpoints, such as:
● translation between telephone numbers and IP addresses,
● address translation from LAN aliases for terminals and gateways to IP or IPX addresses,
● bandwidth management to limit the conferencing bandwidth to a fraction of the total avail-
able bandwidth.
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
H.323 and related protocols
2.1.4 Routers
A router forwards data packets over the IP network. Typical data packets travel across several
routers from their source to their destination.
2.1.5 Multipoint control units (MCU)

An MCU is used for multipoint voice and video calls, where a data stream from one source is
forwarded to multiple destinations. It centralizes the distribution of media, mixes voice and vid-
eo, and manages conference resources.The HiPath HG 3550 supports the connection of an
external MCU.
2.1.6 Servers
Supplementary servers may be used for authorization and call-pick up.
2.1.7 Gateways
An H.323 gateway interconnects H.323 endpoints on IP-based networks to non-H.323 entities
(e.g., telephones on public circuit-switched networks). It provides the protocol translation be-
tween different transmission formats, communications procedures, and audio codecs.
The gateway also authenticates the participants. (This function can also be undertaken by the
HiPath 4000 server.) Authentication is a mechanism to verify the identities of endpoints partic-
ipating in a conference.
2.2 H.323 and related protocols

This section is an overview of the signaling and media protocols in the H.323 suite of protocols
which are relevant to the HiPath HG 3550.
2.2.1 H.225.0 Annex G

This protocol defines signaling between edge gatekeepers in different domains to advertise ad-
dresses handled by their domains.
2.2.2 H.225.0 Q.931 call setup

This protocol defines the signaling between two endpoints for basic call setup and release.
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
2.2.3 H.225.0 RAS control

Registration, Admission and Status (RAS) defines the signaling between the client and the
gatekeeper for recognition and registration purposes.
2.2.4 H.235
This protocol defines signaling for the authentication of users and components, as well as for
the encryption of data.
2.2.5 H.245 signaling

This protocol defines detection of capabilities and exchange of control messages between end-
points. It is used to negotiate channel usage and capabilities.
2.2.6 H.323
This is a standard developed for packet-based multimedia communication systems by the In-
ternational Telecommunication Union (ITU).
2.2.7 H.341
This protocol defines the management information base (MIB) for controlling and managing an
H.323 network.
2.2.8 H.450
This protocol series defines signaling between endpoints for supplementary services such as
call transfer. Call transfer allows a call between two endpoints to be rerouted to a third endpoint.
2.2.9 RTP and RTCP

The Real-time Transport Protocol (RTP) defines delivery of real-time audio and video packets
from one endpoint directly to another endpoint or to multiple endpoints.
A header containing a time-stamp and a sequence number is added to each UDP packet. With
appropriate buffering at the receiving station, timing and sequence information allows the ap-
plication to:
● eliminate duplicate packets,
● reorder out-of-sequence packets,
● synchronize sound, video and data,
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
● achieve continuous playback in spite of varying latencies.

The Real-time Control Protocol (RTCP) is used for the control of RTP. RTCP provides for the:
● monitoring of the quality of service,
● conveyance of information about the session participants,
● periodical distribution of control packets containing quality information to all session partic-
ipants.
2.2.10 TCP
The Transmission Control Protocol (TCP) provides a connection-oriented mode for data trans-
mission. TCP guarantees the sequenced, error-free, flow-controlled transmission of data pack-
ets, but can therefore delay transmission and reduce throughput. H.323 uses TCP end-to-end
services for the H.245 control channel, the data channels, and the call signaling channel.
2.2.11 UDP
User Datagram Protocol (UDP) provides a connectionless transmission mode that promises
nothing more than “best-effort” delivery. UDP offers minimal control information. H.323 uses
UDP for the audio, video, and the RAS channel (see RFC 768).
Figure 2-1 H.323 protocol stack
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
The HiPath HG 3550 as an H.323 gateway
2.3 The HiPath HG 3550 as an H.323 gateway

The HiPath HG 3550 interconnects H.323 endpoints on IP-based networks to telephones on
public circuit-switched networks, serving as a gateway.
The HiPath HG 3550 provides:
● processing of incoming and outgoing calls between circuit-switched networks and local-
area networks (LAN),
● protocol translation services between the H.323 and ISDN standards,
● support of trunking via IP networks (i.e. full support for and transparent transmission of all
ISDN features of the configured ISDN protocol).
2.4 IP Trunking with the HiPath HG 3550

The HiPath HG 3550 uses IP Trunking to connect PBXs over an IP-based network for voice and
fax traffic. The network can be either an enterprise or a carrier network and use a LAN or a
switched-circuit network SCN (for more details see Section 3.4.6.1 and Section 3.4.6.2.). The
benefit is that IP Trunking becomes available to Hicom platforms that are already installed.
PBXs are connected over the IP network by using a combination of gateways and gatekeepers.
An important feature of this version of HiPath HG 3550 is that it can be configured to work
through a HiPath IP Trunking gatekeeper, in conjunction with other gateways. The gatekeepers
are used to create address spaces (H.323 zones).
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
IP Trunking with the HiPath HG 3550
Up to 300 HiPath HG 3550s may be linked together. They may be devided into several subdo-
mains, where one subdomain contains two HiPath IP Trunking gatekeepers and up to 30
HiPath HG 3550 gateways. The secondary HiPath IP Trunking gatekeeper of a subdomain pro-
vides a reliability enhancement, as it takes over the operation in case of failure of the primary
gatekeeper.
Three trunking modes are provided:
● Trunking without HiPath IP Trunking gatekeeper
The HiPath HG 3550 provides the point-to-point routing.
● Single Subdomain Trunking
Two HiPath IP Trunking gatekeepers are provided in one subdomain, where each gate-
keeper control its own H.323 zone. Each HiPath HG 3550 is registered either with the pri-
mary or the secondary gatekeeper.
● Multiple Subdomain Trunking
This trunking mode provides for two or more single subdomains. Each HiPath HG 3550 is
registered either with the primary or the secondary gatekeeper. The HiPath HG 3550 gate-
ways of one zone communicate directly among each other.
The multiple subdomain trunking functionality are realized for specific projects
> only.
A31003-H3101-C104-1-7620, 2002-04-25
ted2.fm
IP Trunking with the HiPath HG 3550
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Nur für den internen Gebrauch Features
Throughput and speed
3 Features
This chapter describes the main features of the HiPath HG 3550. These include the following:
Section 3.1, “Throughput and speed”
Section 3.2, “Security”
Section 3.3, “Autodiscovery function”
Section 3.4, “Voice over IP”
Section 3.5, “Layer 2 and Layer 3 prioritization”
Section 3.6, “Voice quality”
Section 3.7, “Implementation of voice activity detection in HiPath HG 3550”
Section 3.8, “Overview of T.38 and transparent fax modes”
Section 3.9, “Routing Information Protocol (RIP)”
Section 3.10, “Support for Hunting Groups”
Section 3.11, “Bandwidth efficiency”
Section 3.12, “Conferencing using an external MCU”
Section 3.13, “Clear channel”
Section 3.14, “Numbering plan integration”
3.1 Throughput and speed

The HiPath HG 3550 supports
● up to 30 simultaneous bidirectional calls
● the setting up of at least 2000 calls per hour
● a call setup time of two seconds for digital connections between the LAN and PSTN or PBX
3.2 Security
The HiPath HG 3550 is designed to be used in a customer’s intranet, which is inherently a se-
cure environment. The HiPath HG 3550 employs the security mechanisms of the gatekeeper
(see Section 2.1) for all of its transmission functions. This includes supporting the HiPath 4000
password transmission mechanisms.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Features Nur für den internen Gebrauch
Autodiscovery function
3.3 Autodiscovery function

HiPath HG 3550 supports the autodiscovery function of the HiPath 5000 product family. The Hi-
Path 4000 server regularly sends a message to all connected devices (IP phones, gateways,
etc.) containing information on the configuration of the server. The devices then use this infor-
mation to automatically update themselves with server configuration data. Therefore, the auto-
discovery function removes the requirement for the user to manually update server information
in the device.
The HiPath HG 3550 accepts data from the message sent by the server, as shown in Table 3-
1 (for more information see the Configuration manual).
Mask name Parameters

Edit Time Synchronization SNTP Server IP Address
Edit HiPath 4000 Authentication Settings Authentication Server IP
Authentication Server Port
Edit H323 Stack Parameters Primary Gatekeeper IP Address
Primary Gatekeeper Identifier
Time to live (TTL)
Edit H235 Parameters Time window for incoming messages (sec-
onds)
Table 3-1 Received Autodiscovery data
3.4 Voice over IP

Voice over IP (VoIP) is a standard which enables telephone calls to be routed over IP-based
data networks.
The HiPath HG 3550 supports VoIP with the following features:
Section 3.4.1, “Voice encoding”
Section 3.4.2, “DTMF handling”
Section 3.4.3, “Direct dialing”
Section 3.4.4, “Operator zero”
Section 3.4.5, “E.164 telephone numbers”
Section 3.4.6, “Interoperation with PBXs”
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Voice over IP
3.4.1 Voice encoding

Audio signals in VoIP applications contain digitized and compressed speech. Compression and
decompression are handled by standardized codecs.
The HiPath HG 3550 supports the following codecs:
● G.711 (A-law and µ-law) voice encoding – this is an International Telecommunication
Union (ITU) standard for speech codecs at 56 or 64 Kbit/s
● G.723.1 voice compression – this is an ITU standard for speech codecs at 5.3 or 6.4 Kbit/s
● G.729A and AB voice compression – G.729 voice compression is the ITU (International
Telecommunication Union) standard that provides toll-quality voice and uses only minimal
bandwidth per voice channel
The HiPath HG 3550 supports G.729A (which does not use voice activity detection)
> and G.729AB (which uses voice activity detection). See Section 3.6.4 for more infor-
mation about voice activity detection (VAD).
3.4.2 DTMF handling
3.4.2.1 DTMF
Dual-tone multifrequency (DTMF) is the type of audio signal used for tone dialing according to
ITU-T standard Q.24. It is used for call setup and post-dial purposes.
3.4.2.2 Supported DTMF functions

● recognition of DTMF digits
● conversion of DTMF digits to H.245 user input indication
● generation of DTMF digits for the PSTN
● speech protection using Bellcore test tapes
3.4.2.3 Smart DTMF Canceller

In its default setting, HiPath HG 3550 recognizes DTMF tones. For details on how to configure
the handling of DTMF, see the Configuration Manual. If the Smart DTMF Canceller is activated,
the gateway recognizes and suppresses DTMF tones transmitted from the switched-circuit net-
work (i.e., DTMF tones are not forwarded to the voice channel).
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Voice over IP
3.4.3 Direct dialing

For SCN interfaces, the HiPath HG 3550 supports direct-inward dialing (DID) and direct-out-
ward dialing (DOD).
3.4.3.1 Direct-inward dialing (DID)

This feature allows a direct connection via the public network to an extension in a communica-
tion server using the ISDN numbering plan. DID is a method for routing incoming calls directly
to H.323 endpoints through default extensions.
One LAN endpoint is defined as a default destination for incoming calls. If the routing method
(e.g., MSN) cannot be identified, the call is forwarded to this default destination.
3.4.3.2 Direct-outward dialing (DOD)

DOD is used to request a PSTN line from the HiPath HG 3550. A configurable service prefix
has to be dialed before the destination telephone number.
3.4.4 Operator zero

The operator zero is supported. The operator zero is only used for routing to a special single
digit number ‘0’, which is used in Germany to reach the operator. See the Configuration Manual
for more details on this feature.
3.4.5 E.164 telephone numbers

E.164 is an ITU (International Telecommunications Union) standard for addressing telephone
network components (it is used, for example, in ISDN networks). The HiPath HG 3550 supports
the E.164 address format.
3.4.6 Interoperation with PBXs

A private branch exchange (PBX) establishes connections between the telephones of a com-
pany and to the public telephone network. The HiPath HG 3550 V1.0 supports basic calling
functions and also supports the transparent transmission of PBX features over an IP network
(see Section 3.4.6.1, “Trunking”).
For basic calling and the trunking functions, the HiPath HG 3550 interoperates with legacy
PBXs.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Voice over IP
The HiPath HG 3550 supports the CorNet-NQ switched-circuit protocols:

CorNet-NQ is a super-set of CorNet-N that supports QSIG. CorNet-NQ is a global framework
for ISDN and ISDN-like connections for private telecommunications networks. CorNet-NQ pro-
vides and supports the following features:
– Availability of features such as name and number display, transfer, conference, call for-
ward and clamp-on queuing across the entire enterprise network in a uniform manner.
– Data transfer capability of up to 64 Kbit/s per channel, which optimizes use of network
facilities, provides performance improvements over basic analog modems, and sup-
ports applications such as whiteboarding and video.
– Full integration of a single shared server to be fully integrated with PBXs throughout
the network enabling cost reductions.
– Shared network resources, such as 800 numbers and automatic numbering identifica-
tion (ANI), so that response centers can share network services regardless of their
geographic location.
– High network throughput using ISDN-based signaling, look-ahead routing and alter-
nate routing assures that calls are set up even under heavy network traffic or trunk fail-
ure conditions.
– Fast call setup for very fast call processing anywhere in the world.
– Uniform call processing performance for all network connections ensuring high quality
links, independent of distance.
3.4.6.1 Trunking
Two or more private branch exchanges (PBXs) can be connected using HiPath HG 3550 gate-
ways in the trunking mode. This is done by using a proprietary tunneling protocol. The services
work transparently over the ‘IP-Trunk’.
The following switched-circuit network (SCN) services are supported in trunking calls:
● ISDN voice
● ISDN data
● Group 4 fax
● Video telephony (H.320)
● Modem (tone detection)
● Group 3 fax (configurable transmission mode G.711 transparent or T.38)
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Layer 2 and Layer 3 prioritization
3.4.6.2 Fallback to SCN

HiPath HG 3550 provides fallback to SCN for PBX trunking on S0,S1 and S2 interfaces with
CorNet-N and -NQ. This feature allows calls to reach the destination through the switched-cir-
cuit network (SCN) if the LAN is not usable.
The conditions that could cause a fallback are
● the LAN link is not available
● the gatekeeper is not working
● the remote gateway is busy or not working
● the quality of the IP connection falls below a level that is satisfactory for voice calls
If a fallback condition occurs when a call is being set up at the SCN interface, the call will be
cleared with an appropriate value (e.g. “trunk not available”). The PBX originating the call can
then re-route the call over the PSTN network. This requires the routing tables to be configured
with appropriate alternative routes in the PBX.
In addition, The Fallback to SCN function monitors the quality of the IP connection by analyzing
data from the RTCP records. A ’smoothing algorithm’ evaluates the packet loss rate of every
RTCP record over a defined time interval to produce an average value, which can be checked
against a configured threshold. If the quality of the voice connection becomes unsatisfactory,
future calls are automatically routed via the SCN connection. Further calls through this IP path
are blocked for a pre-configured duration. When this happens a timer is started, after the expiry
of which further calls can again be established via the IP connection. The parameters of the
Fallback to SCN feature can be configured in the WBM (see the Configuration Manual for more
details) and the list of blocked IP addresses can be displayed.
The fallback to SCN feature is only used for trunking applications (i.e., a PBX is connected to
the SCN interface of the gateway).
Fallback to SCN works only if the connected PBX supports Call Rerouting on Cause
> Value.
3.5 Layer 2 and Layer 3 prioritization
3.5.1 Brief description of layer switching

A virtual local-area network (VLAN) is used to set up an individual ‘virtual’ network (or sub-net-
work) within a larger interconnected network environment. Although the network is divided into
VLANs, packets can still be switched between any computers within the network. Once a route
between sub-networks has been established and any relevant security checks performed,
packets are switched using the faster Layer 2 and Layer 3 switching protocols.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Voice quality
The 802.1q VLAN configuration is a standard that simplifies setting up and defining VLANs in
a frame-based network (e.g., Ethernet). A field (or tag) is added to the frame format so that the
frame can be associated with a specific VLAN.
Layer 2 and 3 prioritization is managed in the WBM (see the Configuration Manual for more
details).
3.5.2 Layer 3 prioritization

In HiPath HG 3550 the Layer 3 prioritization relates to voice and fax payloads. The priority value
can be set between 0 and 63.
3.5.3 Layer 2 prioritization

In HiPath HG 3550 the VLAN tagging of payload traffic takes place within the Layer 2 Ethernet
header. If VLAN tagging is switched on it only becomes active when traffic has a Layer 3 prior-
itization of a value greater than zero.
If the VLAN tag is switched on
● the driver adds the VLAN tag in all outgoing packets
● all incoming packets are checked for the VLAN tag
If the tagging is switched off
● outgoing packets are handled in the normal manner
● all incoming packets with a VLAN tag are discarded
3.6 Voice quality

This section describes the features that ensure optimal audio quality for all voice transmissions.
It is divided into the following subsections:
Section 3.6.1, “Automatic gain control”
Section 3.6.2, “Echo cancellation”
Section 3.6.3, “Dynamic jitter buffering”
Section 3.6.4, “Voice activity detection”
End-to-end delays of less than 180 ms ensure high quality voice connections.
The HiPath HG 3550 also supports the “Type of Service” (TOS) field in IP headers. This field
prioritizes voice and fax packets in the IP network. For a better quality of service, we recom-
mended that routers which support TOS prioritization are used.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Voice quality
3.6.1 Automatic gain control

The HiPath HG 3550 supports automatic gain control (AGC) for voice transmission levels. The
AGC level to which the input signal is scaled can be configured.
3.6.2 Echo cancellation

The HiPath HG 3550 supports echo cancellation compliant to G.165 in order to provide accept-
able voice quality over the WAN. The echo cancellation is effective for round trip delays of up
to 32 ms.
3.6.3 Dynamic jitter buffering

Jitter buffering is used to eliminate the interference created by variations in the sequence in
which voice and video packets arrive. The delay can be caused by busy or congested networks
or by internal packet processing within the LAN endpoints.
The jitter buffer either operates dynamically or operates at a constant depth over the period of
a connection. Dynamic jitter buffering can be enabled in the WBM. See the Configuration Man-
ual for more details.
There are two algorithms for dynamic jitter buffering:
● Hicom LAN Bridge 2 (HLB2)
● Telephony Internet Server (TIS)
3.6.3.1 HLB2
In the HLB2 jitter buffer algorithms, the local DSP statistics are used to sample network jitter in
the LAN. This sample is used to adjust the rate at which Real-time Transport Protocol (RTP)
packets are passed to the switched-circuit network (SCN). The adjustment is made by increas-
ing or decreasing the jitter buffer average delay in the DSP; an adjustment is made only if the
jitter changes significantly.
3.6.3.2 TIS
In the TIS algorithms, the jitter buffer compares the jitter in the current data with the known his-
tory of the destination. The buffer uses the result of the comparison to dynamically adjust the
rate at which packets are passed to the SCN. This results in more accurate jitter buffering from
the beginning of the connection because performance is immediately optimized to both the
destination and the current state of the system.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Implementation of voice activity detection in HiPath HG 3550
3.6.4 Voice activity detection

Voice activity detection (VAD) checks the input signal for voice. If this signal is above a specified
signal level the VAD declares it to be voice, if it is below the threshold the VAD declares it to be
silence (no voice).
The HiPath HG 3550 provides voice activity detection and silence suppression for all supported
codecs. When no voice signal is detected, a comfort noise is inserted at each end to emulate
traditional telephone line conditions. The noise level can be configured.
3.7 Implementation of voice activity detection in HiPath HG 3550

When a call is set up, HiPath HG 3550 determines which codecs to use and whether or not to
use VAD. The VAD flag is one of the DSP parameters and it influences the availability of the
codecs. The VAD flag is managed in the WBM.
The effect of the VAD flag on the availability of codecs is shown in Table 3-2.
Codec type vadEnable set to FALSE vadEnable set to TRUE

G.711 A-law Codec available Codec available
G.711µ-law Codec available Codec available
G.723.1 Codec available (without VAD) Codec available (with VAD)
G.729A Codec available Codec available
G.729AB Codec not available Codec available
Table 3-2 Effect of the VAD flag setting on codec availability
3.7.1 VAD during receive and send
3.7.1.1 Receive
VAD is supported in the receive direction by all codecs in all cases (including G.723 low bit
rate).
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Overview of T.38 and transparent fax modes
3.7.1.2 Send
Whether or not VAD is used in the send direction depends on the codec selected.
Negotiated Codec Use of VAD in send direction

G.711 A-law Proprietary VAD is used when the VAD flag is set
G.711 µ-law Proprietary VAD is used when the VAD flag is set
G.723.1 VAD is used only when the VAD flag is set and the peer
client accepts VAD
G.729A VAD is not used
G.729AB VAD is used
Table 3-3 Use of VAD in the send direction
3.8 Overview of T.38 and transparent fax modes

The HiPath HG 3550 supports Group 3 (V.27ter, V.29 and V.17 standard) fax transmission be-
tween fax machines attached to the LAN and fax machines attached to the switched circuit net-
work. Two modes of operation are possible:
● transparent mode
● T.38 mode
Which mode is used for a specific fax transmission is determined by
● the settings of the HiPath HG 3550
● the capabilities that the LAN endpoint advertises for the connection
3.8.1 Transparent mode

The HiPath HG 3550 can always transmit faxes in transparent mode. In transparent mode, fax
signals are transmitted over a regular voice G.711 connection. The G.711 codec is needed to
preserve the integrity of the transmitted fax tones.
3.8.2 T.38 mode

T.38 is an ITU standard that defines how real-time Group 3 facsimile machines communicate
over IP networks. In T.38 mode, fax signals are encoded into T.38 messages and transmitted
in a dedicated T.38 connection. The advantages of this mode are enhanced reliability and less
bandwidth consumption for the fax transmission. Fax transmissions inT.38 mode are possible
if T.38 mode is enabled.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Routing Information Protocol (RIP)
If T.38 is enabled in the HiPath HG 3550 the following rules apply:

● If the LAN endpoint advertises G.711 and then sends or receives a fax, the fax is transmit-
ted by HiPath HG 3550 in transparent mode.
● If the LAN endpoint advertises T.38 fax mode, the fax transmission by HiPath HG 3550 will
use the T.38 standard.
3.9 Routing Information Protocol (RIP)

The Routing Information Protocol (RIP) is a protocol that automatically creates and maintains
network routes among other routers that support RIP.
Without RIP, routing tables are updated manually each time a routing change is made. This
would be complicated if many routers were involved. With RIP, when one router learns about a
change in routes from a neighbor, the router forwards this information to other neighboring rout-
ers so that they also update their routing tables. In a network with a network component failure
(such as a router or phone line), the other network components calculate how to work around
the failure, if possible. When the faulty component is repaired, the network changes back to the
previous (superior) configuration.
The HiPath HG 3550 does not actively send RIP packets; it only receives RIP packets (V1 and
V2). The routing domain tag is not supported by the HiPath HG 3550.
Static (or fixed) routes can also be set by user command. However, we do not recommend mix-
ing static and dynamic routes. For more information on configuring RIP, see the Configuration
Manual.
3.10 Support for Hunting Groups

Affiliated gateways that may be expected to receive the same communication are gathered into
administrative collections called “hunting groups”.
Each component member in a communications network can reach others by various routes (al-
ternative routing). To achieve this, the addresses of installed network components are set in
routing tables. In the HiPath 5000 product family, the gatekeeper manages routing information.
To assist in the event that a connection is intended for more than one gateway at the same time,
affiliated gateways are gathered together into hunting groups. The support of such hunting
groups means that for each gateway in the network, a list of affiliated gateways is maintained
and any associated connections are made as required.
To optimize system capacity, the function of supporting hunting groups is shared between the
gatekeeper and the gateway. The gatekeeper is responsible for the management of the hunting
groups. The gateway (after receiving the required routing information from the gatekeeper)
makes the connection directly.
There are no configuration tasks associated with hunting groups.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Bandwidth efficiency
3.11 Bandwidth efficiency

● silence suppression
● idle noise detection and removal
● dynamic voice and fax detection
Because every 64 Kbit/s voice call can be compressed to about 16 Kbit/s, dynamic voice and
fax detection is used to conserve bandwidth. After compression, silence suppression, IP fram-
ing and packetization, a single 64 Kbit/s voice call will use approximately 10 Kbit/s.
The HiPath HG 3550 does not support frame packing.
3.12 Conferencing using an external MCU

In HiPath HG 3550 conferencing without an external multipoint control unit (MCU) is not
provided. An MCU is used for multipoint voice and video calls, where a data stream from one
source is forwarded to multiple destinations. It centralizes the distribution of media, mixes voice
and video, and manages conference resources.
3.13 Clear channel

Clear channel is a transmission mode for special services in trunking scenarios (e.g., ISDN da-
ta, group 4 fax and H.320 video).
This transmission mode has the following characteristics
● signals are transported digitally
● bit-transparent operation is required
● there is no G.711 coding
● no A-law or µ-law conversion is possible
All tone detection filters, tone generators, silence suppression and echo cancellation are deac-
tivated.
3.14 Numbering plan integration

This feature converts the called party numbers into a prefixed (implicit) number format for inter-
nal processing. The type of number (TON) value is set to “unknown” and any optional codes of
the number string (except for the prefix) are removed before the call is routed via the dial plan
and before any outdial rules are applied.
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Numbering plan integration
The advantages of this feature are:

● Easier configuration of dial plans and outdial rules. Instead of needing to take account of
several representations of what is, in effect, the same number, you can write the outdial
rule for just one canonic (standardized) representation, which is the lowest possible implicit
format.
● Automatic recognition of implicit or explicit number formats. For further signalling activities
belonging to the respective call, the gateway uses the detected implicit or explicit format.
● All party numbers which are handled by the call processing of the gateway can be modified
to a specific display format. This optional function is provided by the “Type of Numbering”
table, with which a format type for each existing interface port and numbering type (E.164,
PNP, or implicit) can be configured. In addition, the forwarding of party numbers to the
called party may be suppressed.
Working principle
Once a call is received, the format of the number of the called party is analyzed (whether its
format is explicit or implicit). This format must be known for the gateway to be able to transfer
a party number (e.g., when calls are rerouted using the call transfer feature). Thereafter, the
number of the called party is converted to its lowest possible implicit format. The converted
number is used for call routing as defined by the dial plans, and the outdial rules are applied to
this number. The called party number as well as the calling party number are set to the same
format – implicit or explicit, depending on the outdial rule.
Before it is transmitted the calling number is modified according to the type of numbering (TON)
settings of the destination port. If there is no entry in the TON table for the destination port of
the call, the fully qualified format, which consists of country code, area code, location code, and
extension (E.164); or level 2 code, level 1 code, level 0 code, and extension (private numbering
plan) is used as the default for explicit numbers. For implicit numbers the lowest possible format
is used as the default.
For processing in the reversed call direction (e.g. for transmittal of a party number in case of a
call transfer) the number is converted to the format (implicit or explicit) as detected from the
original called party number. Before it is transmitted the number is modified according to the
type of numbering (TON) settings of the source port. If there is no entry in the TON table for the
used source port, the fully qualified format, which consists of country code, area code, location
code, and extension (E.164); or level 2 code, level 1 code, level 0 code, and extension (private
numbering plan) is used as the default for explicit numbers. For implicit numbers the lowest pos-
sible format is used as the default.
How the call numbers are modified thus depends on the settings of all of the following:
– routing parameters
– dial plan
A31003-H3101-C104-1-7620, 2002-04-25
ted3.fm
Numbering plan integration
– routing table
– outdial rule
– type of number table.
Numbering plan integration requires that the entire system use a coordinated num-
> bering plan. Each gateway can support only one E.164 numbering plan and only one
private numbering plan.
Example
Assume that the general routing parameters are set to:
International Prefix = 000 Country Code = 49
National Prefix = 00 Area Code = 89
Subscriber Prefix = 0 Location Code = 722
Then all following called party numbers are converted to the lowest implicit format of “52300”:
International 49 89 722 52300

National 89 722 52300
Subscriber 722 52300
Implicit international 000 49 89 722 52300
Implicit national 00 89 722 52300
Implicit subscriber 0 722 52300
Implicit E.164 extension 52300
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
Nur für den internen Gebrauch Management
4 Management
This chapter gives an overview of HiPath HG 3550 management tools for installation, configu-
ration, administration and maintenance. It contains the following section:
Section 4.1, “Web-based configuration and administration”
Section 4.2, “Command line management”
Section 4.3, “Simple Network Management Protocol”
Section 4.4, “Maintenance”
The HiPath HG 3550 supports three types of management:
● Web-based management (WBM) via an integrated HTTP server
● Command line management via a V.24 serial port or Telnet
● SNMP-based management via an SNMP agent
The HiPath HG 3550 does not require regular maintenance, but managers may want to period-
ically check the performance of the gateway. Other common management requirements may
include network traffic monitoring to ensure that the LAN is not overloaded and system moni-
toring to ensure that the gateway is not overloaded.
Web-based management (WBM)

The WBM is the most accessible management option for these tasks, offering the possibility of
a directed set-up procedure as well as easy access to configuration, administration and main-
tenance.
Command line interface (CLI)

The CLI is intended as a secondary management tool which does not offer the full range of
functions provided by the WBM. The CLI can be used as a set-up manager and subsequently
to modify the basic set-up.
Simple Network Management Protocol (SNMP)

The SNMP-based option is not intended for the stand-alone management of the
HiPath HG 3550, but makes it possible to integrate it into a network management system. Such
systems can integrate the management of gateways and other network devices from different
manufacturers.
The HiPath HG 3550 supports backing up and restoring the configuration data.
For a more detailed description of the management interface, see the Administration and Main-
tenance Manual.
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
Management Nur für den internen Gebrauch
Web-based configuration and administration
4.1 Web-based configuration and administration

Each management station running TCP/IP can access the HiPath HG 3550 with password au-
thorization. The HiPath HG 3550 includes an embedded Web server.
The HiPath HG 3550 Web-based management (WBM) requires:

> ●
●
Windows 98, 2000, and NT 4.0
Internet Explorer 5.01 or 5.5
● The Java plug-ins 1.2.2_005, 1.2.2_008, and 1.3.1 (recommended)
● The XML extension DLL V3.0
The Web-based management is available over any TCP/IP based connection, provided that the
root administrator has activated WBM on the HiPath HG 3550. Such connections can be made
over a LAN.
To use the Web-based management (WBM) a two-button mouse is required.

>
Figure 4-1 shows the WBM home page.
Figure 4-1 Web-based management home page
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
Authentication
The authentication function can be undertaken by both the HiPath HG 3550 and by a HiPath
5000 server. When a client attempts to access a protected page, an authentication server
checks for the presence of a cookie. This cookie records information about the user or admin-
istrator name, authorization level and credential expiration time. If the cookie is not present, the
authorization level indicated by the cookie is insufficient, or access to the central authentication
server fails, the client is redirected to a login page.
The use of cookies for authentication lets a user or administrator log in once for all parts of the
WBM, instead of requiring a separate log-in for each new page.
There is no link to the login page. The client is redirected to the login page as nec-
> essary.
4.1.1 Menu bar

The main sections of the HiPath HG 3550 administration can be selected via the menu bar (see
Figure 4-2).
Figure 4-2 WBM menu bar
This menu bar provides these menu items:

● Logoff: Offers the exit to the WBM.
● Front panel: Displays static data selectable via a picture of the hardware.
● Wizards: Supports the administrator during the initial configuration.
● Maintenance: Supports the administrator in maintenance tasks.
● Explorers: Provides access to the system through a selection of hierarchical views of the
system.
● Traps: Displays all received SNMP traps.
● Help: Offers access to HiPath HG 3550 documentation.
If the administrator selects a menu item, it turns red and italic. An item-specific selection panel
is shown on the left side of the window.
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
4.1.1.1 Front panel

This section of the WBM allows direct access to many status and control interfaces.
Figure 4-3 shows the WBM front panel view.
Figure 4-3 Front panel view
The display of the front panel periodically updates to indicate the current operational status.
The front panel display shows a representation of the actual front panel of the HiPath HG 3550
in the upper part. The front panel LEDs indicate the status of the corresponding interfaces and
hardware. Textual and graphical results are displayed at the bottom of the window.
Some elements of the front panel display act as pop-up menus which offer access to additional
options, e.g., statistical information or commands to switch status elements. Results are shown
in the lower screen part.
4.1.1.2 Wizards
The Web-based management (WBM) wizards are used to simplify the initial configuration of
the HiPath HG 3550. Wizards guide users through particular tasks by presenting them with se-
quences of dialog boxes, thus simplifying standard configuration procedures.
The general form of a wizard is a managed sequence of dialog boxes. The order and type of
dialog boxes depend on the task you select in the wizard function.
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
Basically, the wizards window contains the following areas:

● Menu area
The menu area is for all available wizard functions. Select a function by clicking on it.
● Dialog area
The dialog area is where the dialog boxes appear. Entries have to be made by selecting or
typing in the individual values.
At the bottom of the dialog area navigation buttons are provided for selecting the next or
the previous dialog page, for cancelling the entries or for calling up a help function. On the
first page, the “back” button is not available. On the last page, the “next” button changes to
“finish”.
Figure 4-4 shows an example of a wizard view.
Figure 4-4 Example of an initial setup wizard
The WBM includes four wizards:

● Initial Setup, which is used for:
– Specifying the gateway name and location
– Setting the gateway routing parameters
– Editing the gateway features
– Configuring the HiPath 4000 authentication
– Changing the root password
– Setting H.323 stack parameters and prefixes
– Setting up audio stream control parameters
– Setting up port defaults
– Checking the hardware
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
● Logical Interfaces, which is used for:

– setting up H.323 stack parameters and prefixes,
– setting up audio stream control parameters.
● Hardware, which is used for:
– setting up port defaults,
– checking the hardware.
● Routing, which is used for:
– configuring the dial plan table,
– configuring the routing table,
– creating outdial rule entries.
4.1.1.3 Maintenance
Maintenance is a sequence of dialog boxes to simplify standard maintenance procedures.
The WBM supports the following tasks:
● configure the TFTP server,
● load a configuration,
● store a configuration,
● restore a configuration,
● store a software image,
● activate software,
● load the trace log,
● load the event log.
4.1.1.4 Explorers
The explorers are comprised of hierarchical, tree-oriented directories. Sorted by keywords, all
available pages can be opened. There is no combination of screens in terms of procedures or
tasks and therefore no step-by-step guidance for the administrator in completing those proce-
dures and tasks is provided.
In the explorer function access to all MIB entries is realized using an explorer-like tree display.
Directories containing the desired functions can be selected from the list in the menu area.
Double-clicking a directory symbol in the explorer window opens or closes the directory. Click-
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
ing the right mouse button on an individual function opens up a pop-up menu, from which a spe-
cific activity can be started. The content of the pop-up depends on which icon is clicked and on
the state of the corresponding object.
The explorer window consists of the following areas:
● Function area
with all available functions. Select a desired function by clicking on it.
● Menu area
where the available explorers are listed. Select a desired explorer by clicking on it.
● Contents area
where the directories, functions, pop-up menus and actual data for the selected explorer
appear. Depending on the function selected, data can be displayed, edited or deleted.
The contents area is subdivided into two further frames:
– an overview on the left side
– a details view on the right side.
The overview is always presented as a tree.
● Control buttons
with the buttons for controlling the application of changes:
– “Apply change” button will activate the change(s) made to the entry field(s).
– “Undo change” button to remove all changes.
Navigation is possible by clicking on an individual function, by clicking on an item in the menu
list, or by double-clicking a directory symbol. Each directory containing undisplayed functions
is marked with a “+” sign in front of a directory symbol. Double-clicking this directory displays
the additional functions and the sign changes to “-”. Double-clicking a directory marked “-” clos-
es the directory again.
The WBM supports the following explorers:
● System
This explorer displays MIB data about:
– CPU (central processing unit),
– memory,
– Flash,
– help,
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
– HiPath 4000 authentication,

– trap destinations.
● Management Access
This explorer is used for managing administrator and user accounts.
● Hardware
This explorer displays MIB data about the:
– Ethernet interface,
– ISDN interface,
– digital signal processor.
● Logical interfaces
This explorer displays MIB data about the:
– H.323 parameters,
– call statistics,
– audio stream control,
– quality of service (QoS),
– resource management.
● Routing
This explorer displays MIB data about:
– IP routing,
– call routing.
● Trace
This explorer displays system trace information. Several trace levels are supported.
Figure 4-5 shows an example of an explorer view.
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
Command line management
Figure 4-5 Explorer data represented by a tree view
4.1.1.5 Traps
Using the WBM it is possible to display the current traps. This is important to ensure a quick
response to alarms which have been generated by the HiPath HG 3550.
For a more detailed description of Traps, see the Administration and Maintenance Manual.
4.2 Command line management

The command line interface (CLI) is available on a standard terminal (e.g., VT100) attached to
the V.24 serial port of the HiPath HG 3550, and also (once IP is configured) through a remote
Telnet client (see RFC 854). The manager can be attached locally via a serial connection (V.24)
or remotely via the internal Telnet interface.
The CLI command set is the minimum required to permit system initialization and basic config-
uration activities. It allows system integration and testing. The HiPath HG 3550 supports only a
basic set of commands for performing the following tasks:
● Modifying configuration parameters, e.g., the gateway’s IP address.
● Updating firmware and software.
For file handling on the HiPath HG 3550, a TFTP (Trivial File Transfer Protocol) client is
available. A corresponding TFTP server has to be available on the administrator PC (or
inside the network).
● Diagnosing the system software.
A31003-H3101-C104-1-7620, 2002-04-25
ted4.fm
Simple Network Management Protocol
4.3 Simple Network Management Protocol

The HiPath HG 3550 supports the Simple Network Management Protocol (SNMP) Version 1
for statistics, diagnostics and alarm handling. Currently, only reading of SNMP information is
supported, not writing.
SNMP uses the User Datagram Protocol (UDP) and is designed for use in connection with net-
work management systems (NMS). The NMS uses SNMP to manage the network elements of
different manufacturers connected to a network.
The HiPath HG 3550 contains an SNMP agent, which accesses a standard type 2 manage-
ment information base (MIB) and a HiPath HG 3550-specific proprietary MIB containing the ad-
ministration and configuration data.
SNMP has its own password security, which is set up to ensure that the HiPath HG 3550 can
only be administered by authorized administrators.
SNMP Traps
SNMP can be used to generate traps. When a trap is generated, the HiPath HG 3550 sends a
trap protocol data unit (PDU) to the SNMP manager (see RFC 1215 and RFC 1315), which
then forwards the traps to the NMS.
4.4 Maintenance
The HiPath HG 3550 requires no regular maintenance. If problems unexpectedly occur which
cannot be solved using the available tools, an authorized partner at one of Siemens service
centers should be contacted.
The HiPath HG 3550 supports downloading of software updates (new software images) during
operation. The HiPath HG 3550 stores two separate software images for recovery if it is
equipped with a sufficient amount of flash memory.
The HiPath HG 3550 has an intuitive graphical Web-based interface (see Section 4.1) which
provides for easy maintenance (see also the Administration and Maintenance Manual).
A31003-H3101-C104-1-7620, 2002-04-25
ted5.fm
Nur für den internen Gebrauch Interfaces
LAN interface
5 Interfaces
This chapter describes the physical interfaces for LAN connections to the HiPath HG 3550.
This chapter contains the following sections:
Section 5.1, “LAN interface”
Section 5.2, “Local management port”
Figure 5-1 Overview of HiPath HG 3550 ports
5.1 LAN interface

The HiPath HG 3550 provides one autosensing Ethernet interface. The IEEE 802.3-compliant
Ethernet interface is built around a fast Ethernet controller. The HiPath HG 3550 supports au-
tomatic selection of half- and full-duplex 10Base-T or 100Base-TX.
5.1.1 10Base-T and 100Base-TX

For the LAN connection, an Ethernet controller is provided. On the network communication in-
terface board, an 8-pin shielded modular jack (RJ-45) is provided to connect 10Base-T or
100Base-TX cabling. This interface autosenses the transfer bit rate (10 Mbit/s or 100 Mbit/s).
Figure 5-2 10/100Base-TX or 10Base-T LAN interface
The LAN interface provides 10 Mbit/s or 100 Mbit/s access to standard Ethernet (IEEE 802.3).
A31003-H3101-C104-1-7620, 2002-04-25
ted5.fm
Interfaces Nur für den internen Gebrauch
Local management port
Usage
● Routing and bridging from LAN (Ethernet) to WAN (e.g., ISDN)
● Connecting a Web-based management (WBM) terminal
Limitations
● Ethernet types 10Base2 (BNC connector) and 10Base5 (AUI connector) are not directly
supported.
● If no twisted-pair Ethernet network is available, use an off-the-shelf adapter from 10Base-
T to 10Base2 or 10Base5 cabling.
Related standards
IEEE 802.2 Logical Link Control

IEEE 802.3 CSMA/CD Access
ISO 8802.2 Logical Link Control
ISO 8802.3 CSMA/CD Access
5.2 Local management port

The HiPath HG 3550 provides a serial V.24 interface for service access. The local management
interface is a V.24 port with a maximum transfer rate of 19.2 Kbit/s. When the HiPath HG 3550
is powered-on, basic management tasks can be performed via this interface.
Figure 5-3 V.24 local management port
A PC or standard VT 100 terminal can be connected.
Usage
● Configuring the IP address
● Maintenance
A31003-H3101-C104-1-7620, 2002-04-25
ted5.fm
Nur für den internen Gebrauch Interfaces
Related standards
:
ITU-T V.10 Unbalanced double current interface circuits up to 100 Kbit/s

EIA-574 DB-9 connector
EIA X.3 section 3.12 Inband flow control – Xon /Xoff protocol
A31003-H3101-C104-1-7620, 2002-04-25
ted5.fm
Interfaces Nur für den internen Gebrauch
A31003-H3101-C104-1-7620, 2002-04-25
ted6.fm
Nur für den internen Gebrauch Hardware Architecture
Board Interfaces
6 Hardware Architecture
This chapter describes the hardware components of the HiPath HG 3550.
6.1 Board Interfaces

The following interfaces are provided on the HiPath HG 3550 board.
Figure 6-1 Interfaces of the HiPath HG 3550
6.1.1 Microcontroller
The HiPath HG 3550 is based on the Motorola PowerQUICC (MPC860P) architecture, an en-
hanced version of the MPC8600. The 80 Mhz CPU is a PowerPC implementation with addition-
al embedded functionality:
● embedded PowerPC core
● communication processor module (CPM)
● instruction cache (16 KB)
● data cache size (8 KB)
● dual port RAM (8 KB)
● memory controller for SDRAM (flash and periphery)
● interrupt controller
● timers
● serial communication controllers: UART and Ethernet mode
● Fast Ethernet controller
A31003-H3101-C104-1-7620, 2002-04-25
ted6.fm
Hardware Architecture Nur für den internen Gebrauch
Board Interfaces
6.1.2 Flash Memory

The HiPath HG 3550 contains 16 MB of flash memory connected through a 32-bit memory bus.
This memory is used to store program code and persistent data.
The flash memory is writable to allow updates and permanent configuration data to be stored.
It can be written in blocks while the system is running. Blocks of 64 KB can be protected via the
block lock bit to prevent the overwriting of data.
The media access control (MAC) address of the HiPath HG 3550 is stored in the flash memory.
6.1.3 Synchronous DRAM

The HiPath HG 3550 provides one 25˚ angle dual in-line memory module (DIMM) socket to
support 168-pin PC100 compatible unbuffered SDRAM modules without parity. One 32 MB
SDRAM module is installed.
Resetting the HiPath HG 3550 invalidates the contents of the synchronous DRAM.
7
6.1.4 Ethernet Interfaces

The 10/100 Base-T Fast Ethernet interface is IEEE802.3u compliant. An RJ-45 connector is
mounted on the front panel for connection of 10/100Base-T media.
A Fast Ethernet controller is provided on the board. It supports autonegotiation for automatic
selection of half-duplex and full-duplex 10Base-T or 100Base-TX.
An additional 10Base-T Ethernet interface is provided using the board’s serial communication
controller.
6.1.5 DSP modules

One digital signal processor (DSP) module provides 10 B channels. The three pluggable DSP
modules on the main board provide voice and fax functionality for 30 simultaneous voice chan-
nels (see Section 7.2.5).
For the DSP modules, three 25-degree dual in-line memory module (DIMM) sockets (X7-X9)
are provided on the main board of the HiPath HG 3550.
All three DSP modules must always be installed.

>
A31003-H3101-C104-1-7620, 2002-04-25
ted6.fm
Nur für den internen Gebrauch Hardware Architecture
Board Interfaces
Figure 6-2 DSP modules
Each DSP has its own synchronous DRAM. The power consumption of a DSP module is ap-
proximately 1.9 W. The synchronous DRAM power consumption is typically 0.6 W.
6.1.6 Power Consumption

The total power consumption of the board is typically below 10 W. A power supply of 5V is re-
quired.
6.1.7 LED Indications

The following LEDs are provided at the boards front panel:
LED (color) lit constantly flashing

Run (green) board in service, but no calls at least one call established
Fail (red) error loading (after reset)
Link Status (green) link OK error
Table 6-1 LEDs on front of the HiPath HG 3550 board
A31003-H3101-C104-1-7620, 2002-04-25
ted6.fm
Hardware Architecture Nur für den internen Gebrauch
Board Interfaces
A31003-H3101-C104-1-7620, 2002-04-25
ted7.fm
Nur für den internen Gebrauch Software Architecture
Call processing
7 Software Architecture
This chapter provides a summary of the main software components and protocols of the
HiPath HG 3550.
The software architecture can be described with two blocks:
Section 7.1, “Call processing”
Section 7.2, “Software platform”
7.1 Call processing

The call processing block contains the following components:
● Managers for the signaling functions, such as:
– H.323 manager,
– device manager,
– E-DSS1 signaling manager,
– Belle NI-2 signaling manager,
– AT&T 4ESS signaling manager,
– MCI signaling manager,
– session manager,
– CorNet-NQ manager;
● H.323 stack adapter to prevent other system functions interfering with the H.323 opera-
tions;
● Operation, administration and maintenance (OAM) to allow for diagnosis, configuration, the
collection of statistics, and event handling.
A31003-H3101-C104-1-7620, 2002-04-25
ted7.fm
Software Architecture Nur für den internen Gebrauch
Software platform
7.2 Software platform

The software platform is described in the following sections:
Section 7.2.1, “Firmware”
Section 7.2.2, “Real-time operating system”
Section 7.2.3, “Drivers”
Section 7.2.4, “Audio stream control”
Section 7.2.5, “DSP software”
7.2.1 Firmware
The firmware resides in the flash memory. It is restarted when the HiPath HG 3550 is reset. The
firmware code (boot ROM image) is the first code that is executed after power is applied.
The firmware of the HiPath HG 3550 provides the following functions:
1. Performing the built-in self tests (BIST) and writing the results to a reserved memory area
to make them available to the system.
2. Initializing the hardware components of the board.
3. Supporting the decompression and loading of the operating instructions from the flash file
system to the RAM (random access memory).
4. Starting the operating code in RAM.
5. Installing the drivers.
6. Starting the WAN and the drivers.
7. Starting the management application. It reads and parses the configuration file. If an error
is found, the manager determines from the start-up configuration whether the system
should start with an alternate configuration file (held in the flash) or restarts.
7.2.2 Real-time operating system

The main board uses a real-time operating system (RTOS). The RTOS provides basic functions
such as multi-tasking, inter-process communication, and interrupt services which are required
by the software applications.
A31003-H3101-C104-1-7620, 2002-04-25
ted7.fm
Nur für den internen Gebrauch Software Architecture
Software platform
7.2.2.1 Board support package

The board support package (BSP) serves as a link between the hardware-independent system
call interface and the platform-specific hardware environment. The BSP reflects the specific
hardware structure of the HiPath HG 3550 (e.g., memory layout, interrupt vectors, network de-
vices).
7.2.2.2 DOS file system

The DOS file system provides applications running on the HiPath HG 3550 with a high-level in-
terface to the RAM and the flash memory.
7.2.2.3 True flash file system

The true flash file system (TFFS) provides the interface between the DOS file system and the
flash memory by emulating a hard disk drive.
7.2.3 Drivers
A driver is code that communicates directly with the network interface hardware. In the
HiPath HG 3550 a driver is provided for each hardware device (e.g., ELIC, DRAM, RTC). De-
vices handled by drivers are identified by their file descriptors. The I/O (input or output) system
provides a uniform, device-independent mechanism to access devices through a set of system
calls (e.g., open, close, read, write, input or output control).
7.2.4 Audio stream control

The audio stream control (ASC) controls and monitors audio streams passing through the
HiPath HG 3550. This means that it is responsible for forwarding voice information between the
LAN and ISDN.
7.2.5 DSP software

The digital signal processor (DSP) units provide voice functionality with the help of special DSP
software. This includes the software running on the DSPs as well as the V.42bis compression
routines.
The DSP software is needed for access from the switched-circuit network to the connected
LAN.
A31003-H3101-C104-1-7620, 2002-04-25
ted7.fm
Software Architecture Nur für den internen Gebrauch
Software platform
DSP functionality is provided for:

● Voice codecs:
– G.711 voice encoding, A-law and µ-law on LAN and WAN side,
– G.723.1 voice compression,
– G.729A and AB voice compression.
● DTMF recognition and generation according to ITU-T standard Q.24 (see Section 3.4.2),
● Echo cancellation compliant to G.165 (see Section 3.6.2),
● Automatic gain control (see Section 3.6.1),
● RTP (Real-time Transport Protocol):
– Sending to the LAN.
The DSP module receives an RTP initialisation-header from the system. The DSP
module updates this header and sends it via the host port interface to the LAN.
– Receiving from the LAN.
The DSP module receives RTP packets. It performs jitter buffering (see Section 3.6.3)
and reorders the voice packets according to the Real-time Transport Protocol (RTP).
The flexible architecture of the HiPath HG 3550 enables other algorithms to be implemented in
the future. New algorithms will simply be loaded into the firmware.
A31003-H3101-C104-1-7620, 2002-04-25
ted8.fm
Nur für den internen Gebrauch Standards
8 Standards
This chapter lists the standards and RFCs referred to in this document in alphabetical order.
You can download current versions of these standards and RFCs via the Internet. See the end
of this chapter for addresses.
Name Standard
CSMA/CD Access IEE 802.3 and ISO
8802.3
Ethernet; unbalanced double current interface circuits up to ITU-T V.10
100 Kbit/s
SNMP traps RFC 1215
SNMP traps RFC 1315
Telnet RFC 854
User Datagram Protocol (UDP) RFC 768
V.24; DB-9 connector EIA-574
V.24; inband flow control – Xon/Xoff protocol EIA X.3 section 3.12
Table 8-1 List of standards and RFCs
Internet addresses for telecommunication standards

See the following table for addresses from which telecommunications standards are available.
Some of these sites may charge you for downloading standards; some may allow only online
ordering for physical delivery.
Standard Address
EIA standards http://www.tiaonline.org/standards/search_n_order.cfm
ETS standards http://webapp.etsi.org/pda/
IEEE standards http://shop.ieee.org/store/
ISO standards http://pod.iso.ch/livelink/livelink/643694/home.html
(for ISO members only, requires password)
ITU-T standards http://www.itu.int/itudoc/itu-t/rec/index.html
RFCs http://freesoft.org/CIE/RFC/index.htm
Table 8-2 Internet addresses for telecommunication standards
A31003-H3101-C104-1-7620, 2002-04-25
ted8.fm
Standards Nur für den internen Gebrauch
A31003-H3101-C104-1-7620, 2002-04-25
tedglos.fm
Nur für den internen Gebrauch Glossary
Glossary X
A
ARP
The Address Resolution Protocol is a protocol that maps Layer 3 IP addresses to Layer 2
media access control (MAC) addresses (hardware addresses).
B
B channel
An ISDN bearer channel transmits voice or data at 64 Kbit/s.
bandwidth
The bandwidth of a channel is its data transfer capacity in bits per second (bit/s).
boot
Booting is the start-up process of any computer or similar system.
C
CAS-T1
Channel-associated signaling is a feature that supports Ear and Mouth communication
over a primary T1 interface (see also: Ear & Mouth)
codec
Codecs convert analog audio or video into a digital form (encode) and digitally encoded
audio and video back again into an analog form (decode).
CorNet-N
CorNet-N is a Siemens proprietary signaling protocol used to network different Hicom
nodes. It presents telephony features in a uniform manner across a network.
CorNet-NQ
CorNet-NQ is a superset of CorNet-N that supports QSIG.
D
D channel
A D channel is an ISDN signaling channel which transmits call control messages.
A31003-H3101-C104-1-7620, 2002-04-25
HG3550, Technical Description X-1
tedglos.fm
Glossary Nur für den internen Gebrauch
Denial of service
Denial of service is an attack where the attacker prevents the computer providing a service,
typically involving overloading the system with tasks so that it cannot respond to genuine
requests.
DID
Direct inward dialing is a method for routing incoming calls directly to H.323 endpoints.
DTMF
Dual tone multifrequency (DTMF) consists of two frequencies in the audio spectrum per
number dialed.
E
E-DSS1
European-digital subscriber system no.1 is the standard ISDN transmission protocol used
in Europe.
Ear & Mouth
Ear and Mouth (E&M) is a tie line (see tie line) communication protocol employed in PBX-
to-PBX communications.
encapsulation
Encapsulation is the placing of the frame header and data of one protocol into the data field
of another (see tunneling). One analogy is to think of envelopes placed within envelopes.
Therefore, a letter designed to use the protocols of an internal departmental mailing sys-
tem can traverse the public mailing system by being placed in an envelope addressed to
use the protocols of the public postal system.
endpoint
An endpoint is an H.323 component from which calls can be made or received. It generates
or terminates information streams. Examples for endpoints are clients, gateways or MCUs.
F
fractional T1
A complete T1 carrier contains 24 channels, each of which provides 64 Kbit/s. Most phone
companies, however, also sell fractional T1 lines, which provide less bandwidth but are
also less expensive. Typically, fractional T1 lines are sold in increments of 56 Kbit/s (the
extra 8 Kbit/s per channel is used for data management).
G
G.711
G.711 is an International Telecommunication Union (ITU) standard for speech codecs at
64 Kbit/s.
A31003-H3101-C104-1-7620, 2002-04-25
X-2 HG3550, Technical Description
tedglos.fm
G.723.1
G.723.1 is an International Telecommunication Union (ITU) standard for speech codecs at
5.3 or 6.4 Kbit/s.
G.729 A/AB
G.729 voice compression is the ITU (International Telecommunication Union) standard
that provides toll-quality voice and uses only minimal bandwidth per voice channel. G.729A
does not use voice activity detection; G.729AB uses voice activity detection.
gatekeeper
A gatekeeper is an H.323 component that provides address resolution and access control
to endpoints on an H.323 network.
gateway
A gateway is an H.323 component that interconnects H.323 endpoints on IP-based net-
works to telephones on public switched telephone networks. It provides protocol translation
between the H.323 and ISDN standards.
H
H.235
The H.235 protocol introduces security into H.323 communications (see also H.323)
through the authentication of users, components and by the encryption of data.
H.323
H.323 describes how voice (i.e., telephone) and fax traffic is handled on packet-based net-
works such as IP networks. The relevant standards are defined in the H.323 series of ITU-
T (International Telecommunication Union – Telecommunication Standardization Sector)
recommendations.
H.450
H.450 is a series of protocols which create supplementary telephony related services, for
example: call transfer, call diversion or call hold.
Hicom Xpress
Siemens Hicom (highly integrated communications) Xpress is an innovative strategy which
implements a comprehensive, IP-based migration scheme designed to integrate traditional
voice communications into any existing corporate IP network. Hicom Xpress provides a
peak performance network that increases the effectiveness and efficiency of communica-
tions, centralizes voice and data network administration, lowers costs and increases pro-
ductivity.
HiPath
Siemens HiPath (highly integrated network) is an innovative strategy which implements a
comprehensive, IP-based migration scheme designed to integrate multi-media communi-
cations into any existing corporate IP network.
A31003-H3101-C104-1-7620, 2002-04-25
tedglos.fm
I
Internet Protocol Security (IPSec)
IPSec is a protocol that adds security to the Internet Protocol (IP) by inserting authentica-
tion and encryption information into the IP data.
IP address
An Internet Protocol address is a numeric string that is used to identify a device.
IP addresses have four sets of numbers with values from 0 through 255 in each set, for ex-
ample 0.0.0.0.
ISDN
The Integrated Services Digital Network is a fully-digital public telephone network.
IVR
Interactive voice response is a method for routing incoming calls when a single line does
not possess different numbers allowing direct dialing to different H.323 endpoints. The Hi-
Path RG 2500 does not support IVR.
J
jitter
Jitter is a type of interference. The network causes varying amounts of delay to packets.
This causes some packets to arrive later than others resulting in distortion to audio and
video, both of which need smooth delivery.
jitter buffer
A jitter buffer is a short term store that collects incoming data and holds it briefly, allowing
time for late packets to arrive. The complete information can then be correctly forwarded
without the distortion caused by jitter. In the HiPath HG 3550 the size (or depth) of the buff-
er can be fixed or dynamically variable.
L
LAN
A local-area network connects computers within a company site.
Layer switching
The layering protocol identifies a common standard for the functions within a network. The
Open Systems Interconnection Model (OSI) defines the layers as: Physical (Layer 1), Data
Link (Layer 2), Network (Layer 3), Transport (Layer 4), Session (Layer 5), Presentation (lay-
er 6) and Application (Layer 7). Layer switching uses this model to divide networks into sub-
networks (or VLANs), set up routes and switch data between them.
A31003-H3101-C104-1-7620, 2002-04-25
tedglos.fm
M
MCU
A multipoint controller unit is used for multipoint voice and video calls. It centralizes the dis-
tribution of media and mixes voice and video.
MIB
In a management information base, management characteristics and parameters of net-
work devices are described. It is used by SNMP.
multicast
Multicast is the process of transmitting from one source to many destinations.
N
Network Time Protocol (NTP)
NTP is a an Internet protocol that uses clocks located on the Internet to synchronize the
clocks of client and server computers.
P
PBX
A private branch exchange connects the telephones of a company to each other and to the
public telephone network.
PSTN
The public switched telephone network is the worldwide telephone network.
PRI
An ISDN Primary Rate Interface line consist of 30 (TS2) or 23 (TST1) 64 Kbit/s B channels
transmitting the data and one 16 Kbit/s D channel that is used for call setup and signaling.
Public Key Infrastructure (PKI)
PKI is a structure involving trusted certifying authorities that verify and authenticate users
transacting on the Internet or on intranets.
Q
Q.931
Q.931 is a call signaling protocol for setup and termination of calls.
QSIG
QSIG is the inter-node networking protocol adopted by ITU-T, an international standards
body. QSIG allows PBXs from different vendors to be networked.
A31003-H3101-C104-1-7620, 2002-04-25
tedglos.fm
R
RAS
Registration, Admission and Status is a protocol that defines the signaling between the cli-
ent and the gatekeeper for discovery and registration purposes.
RIP
Route Information Protocol (RIP) automatically creates and maintains network routes
among routers that support this protocol.
router
A router is a network component that connects subnetworks which use different technolo-
gies and forwards packets between them.
RTP
The Real-time Transport Protocol defines delivery of real-time audio and video packets
from one endpoint directly to another endpoint or to multiple endpoints.
S
Secure Sockets Layer (SSL)
SSL is an interface to provide encrypted data between client and server applications.
Simple Network Time Protocol (SNTP)
The Simple Network Time Protocol (SNTP) is an adaptation of the Network Time Protocol
(NTP) used to synchronize computer clocks in the Internet. SNTP is described in RFC
1769.
spoofing
Spoofing is an attack where the attacker logs on to the system pretending to be someone
else.
T
T.38
T.38 is an ITU standard for fax transmissions. It defines how real time Group 3 facsimile
machines can communicate over IP networks.
tie line
A tie line is a private circuit leased from a communications carrier, connecting two or more
points in an organization.
Trunking
Trunking uses tunneling (see tunneling) and encapsulation (see encapsulation) to set up a
toll-free IP-based telephony connection between two PBXs.
A31003-H3101-C104-1-7620, 2002-04-25
tedglos.fm
tunneling
Tunneling is the encapsulating (see encapsulation) one protocol within another so that it
can be transported from LAN to LAN via a connection that does not support the encapsu-
lated protocol. It can also be used to create a “private” connection on the Internet. This is
done by using encryption to place secure packets within IP packets, so allowing secure in-
formation to traverse the Internet in the normal way.
V
Voice activity detection
Voice activity detection (VAD) checks the input signal for voice. If this signal is above a
specified signal level the VAD declares it to be voice, if it is below the threshold the VAD
declares it to be silence (no voice).
VoIP
Voice over Internet Protocol (IP) enables telephone calls over IP-based data networks.
A31003-H3101-C104-1-7620, 2002-04-25
tedglos.fm
A31003-H3101-C104-1-7620, 2002-04-25
tedabb.fm
Nur für den internen Gebrauch List of Abbreviations
List of Abbreviations Y
This table shows some important abbreviations.
Abbreviation Definition
A
AGC automatic gain control
ANI automatic numbering identification
ARP Address Resolution Protocol
ASC audio stream control
B
BIST built-in self tests
BSP board support package
C
CPU central processing unit
CSMA/CD carrier sense multiple access with collision detection
D
DID direct inward dialing
DIMM dual in-line memory module
DOD direct outward dialing
DSP digital signal processor
DTMF dual-tone multifrequency
H
HLB Hicom LAN Bridge
I
IP Internet Protocol
IVR interactive voice response
A31003-H3101-C104-1-7620, 2002-04-25
HG3550, Technical Description Y-1
tedabb.fm
List of Abbreviations Nur für den internen Gebrauch
L
LAN local-area network
M
MAC media access control
MIB management information base
MSN multiple subscriber numbering
N
NMS network management systems
O
OSI Open System Interconnection
P
PDU protocol data unit
R
RAM random access memory
RAS registration/admission/status
RFC request for comments
RIP Routing Information Protocol
RTCP Real-time Control Protocol
RTOS real-time operating system
RTP Real-time Transport Protocol
S
SCN switched-circuit network
T
TED technical description
TFFS True Flash File System
TIS Telephony Internet Server
U
UDP User Datagram Protocol
UDP User Datagram Protocol
A31003-H3101-C104-1-7620, 2002-04-25
Y-2 HG3550, Technical Description
tedabb.fm
Nur für den internen Gebrauch List of Abbreviations
V
VAD voice activity detection
VLAN virtual local-area network
VoIP Voice over Internet Protocol
W
WBM Web-based management
A31003-H3101-C104-1-7620, 2002-04-25
HG3550, Technical Description Y-3
tedabb.fm
List of Abbreviations Nur für den internen Gebrauch
A31003-H3101-C104-1-7620, 2002-04-25
Y-4 HG3550, Technical Description
tedIX.fm
Nur für den internen Gebrauch Index
Index Z
Numbers DSP
100Base-TX 5-1 modules 6-3
10Base-T 5-1 DTMF 3-3, X-2
dual in-line memory module 6-3
A dual-tone multifrequency 3-3
AGC 3-8
ANI 3-5 E
ASC 7-3 Ear and Mouth X-2
audio stream control 7-3 E-DSS1 X-2
AUI connector 5-2 endpoint X-2
automatic gain control 3-8 Ethernet 6-2
interface 5-1
B explorer 4-6
BIST 7-2 functions 4-6
bit rate 5-1 navigation 4-7
BNC connector 5-2 window 4-7
board support package 7-3
BSP 7-3 F
FEC 5-1
C firmware 7-2
chapter overview 1-3 flash memory 6-2
CLI 4-1, 5-2 fractional T1 X-2
codec 3-3, X-1
command line interface 4-9 G
compression 3-3 G.711 3-3, X-2
CorNet-N X-1 G.723.1 3-3, X-3
CorNet-NQ 3-5, X-1
CSMA/CD 5-1, 5-2
H
H.323 2-1
D Hicom Xpress X-3
D channel X-1 HTTP 4-1, 4-2
DID 3-4, X-2 hunting groups 3-11
digital signal processor 7-3
DIMM 6-3
I
sockets 6-3 interactive voice response 3-4
direct inward dialing 3-4, X-2 ISDN X-4
direct outward dialing 3-4 IVR 3-4, X-4
DOD 3-4 L
DOS file system 7-3
LAN 5-1, X-4
driver 7-3
interface 5-1
A31003-H3101-C104-1-7620, 2002-04-25
HG3550, Technical Description Z-1
tedIX.fm
Index Nur für den internen Gebrauch
local management port 5-2 T

T.38 3-10
M T.38 fax mode 3-10
MAC 6-2 TCP 2-5
MCU 3-12, X-5 TCP/IP 4-2
memory 7-2 TFFS 7-3
MIB X-5 TFTP 4-9
MSN 3-4 transparent fax mode 3-10
multipoint control unit 3-12 true flash file system 7-3
N U
NCIB 5-1 UDP 2-5
network communication interface board 5-1
network management systems 4-10 V
NMS 4-10 V.24 interface 5-2
nonvolatile memory 6-2 voice encoding 3-3
Voice over IP 3-2
P VoIP 3-2, X-7
PBX 3-4, X-5
PDU 4-10 W
physical interfaces 5-1 WAN 5-1
PRI X-5 WBM 4-1, 4-2
private branch exchange 3-4 terminal 5-2
proprietary MIB 4-10 wizards 4-4
PSTN X-5 Web-based management 4-2
wizards 4-4
Q window 4-5
QSIG X-5
R
RAS 2-4, X-6
real-time operating system 7-2
RFC 8-1
RIP 3-11
ROM 7-2
RTCP 2-4
RTOS 7-2
RTP 2-4, X-6
S
Simple Network Time Protocol X-6
SNMP 4-1
traps 4-10
Synchronous DRAM 6-2
A31003-H3101-C104-1-7620, 2002-04-25
Z-2 HG3550, Technical Description

19 Ted

Uploaded by

Document Information

Original Title

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

19 Ted

Uploaded by

Copyright:

Available Formats

s

The device conforms to the EU guideline 1999/5/EG, as attested by the CE

Reference No.: A31003-H3101-C104-1-7620

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-5

Content Nur für den internen Gebrauch

3.4.2.2 Supported DTMF functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

4.4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Content Nur für den internen Gebrauch

Figure 1-1 Front view of HiPath HG 3550. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

List of Figures Nur für den internen Gebrauch

Table 1-1 HiPath HG 3550 feature overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 1-1 Front view of HiPath HG 3550

1.1 Business advantages of IP telephony

1.2 Summary of features

Feature For details see

Feature For details see

1.3 Contents of this description

No. Chapter Contents

1.4 Associated documents

Document type Target group

Information on the Web

2.1 Components of H.323 networks

2.1.1 H.323 clients (terminals).

2.1.2 Terminal adapters

2.1.5 Multipoint control units (MCU)

2.2 H.323 and related protocols

2.2.1 H.225.0 Annex G

2.2.2 H.225.0 Q.931 call setup

2.2.3 H.225.0 RAS control

2.2.5 H.245 signaling

2.2.9 RTP and RTCP

● achieve continuous playback in spite of varying latencies.

Figure 2-1 H.323 protocol stack

2.3 The HiPath HG 3550 as an H.323 gateway

2.4 IP Trunking with the HiPath HG 3550

3.1 Throughput and speed

3.3 Autodiscovery function

Mask name Parameters

3.4 Voice over IP

3.4.1 Voice encoding

3.4.2 DTMF handling

3.4.2.2 Supported DTMF functions

3.4.2.3 Smart DTMF Canceller

3.4.3 Direct dialing

3.4.3.1 Direct-inward dialing (DID)

3.4.3.2 Direct-outward dialing (DOD)

3.4.4 Operator zero

3.4.5 E.164 telephone numbers

3.4.6 Interoperation with PBXs

The HiPath HG 3550 supports the CorNet-NQ switched-circuit protocols:

3.4.6.2 Fallback to SCN

3.5 Layer 2 and Layer 3 prioritization

3.5.1 Brief description of layer switching

3.5.2 Layer 3 prioritization

3.5.3 Layer 2 prioritization

3.6 Voice quality

3.6.1 Automatic gain control

3.6.2 Echo cancellation

3.6.3 Dynamic jitter buffering

3.6.4 Voice activity detection

3.7 Implementation of voice activity detection in HiPath HG 3550

Codec type vadEnable set to FALSE vadEnable set to TRUE

3.7.1 VAD during receive and send