Service

HiPath 4000 V4
IP Solutions
Service Manual
A31003-H3140-S107-1-7620
www.siemens.com/enterprise

Copyright Siemens Enterprise Communications GmbH & Co. KG 2007

Hofmannstr. 51, D-81359 Mnchen
Reference No.: A31003-H3140-S107-1-7620
The information provided in this document contains merely general
descriptions or characteristics of performance which in case of actual use do
not always apply as described or which may change as a result of further
development of the products. An obligation to provide the respective
characteristics shall only exist if expressly agreed in the terms of contract.
Subject to availability. Right of modification reserved. The trademarks used
are owned by Siemens Enterprise Communications GmbH & Co. KG or their
respective owners.

www.siemens.com/enterprise

sip_trunkingTOC.fm
Nur fr den internen GebrauchService Manual HiPath 4000 V4 - IP Solutions - IP and SIP Trunking - Contents

Service Manual HiPath 4000 V4 - IP Solutions - IP and SIP

Trunking - Contents
0
1 Overview SIP Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 SIP Trunking Communication Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Boards Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5

2 SIP trunking between homogenous HiPath 4000 nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 Restriction for SIP trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Device registration & call address resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.1 Authentication service via DIGEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.2 Registration of Siemens SIP Gateways at HG 3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.3 Gateway-initiated Deregistration of Siemens SIP Gateways at HG 3500 . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.4 Call address resolution at the HG 3500 (SIP) LEGK (local gateway) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.5 Registration of Siemens H.323 gateways at HG 3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.6 Gateway-initiated deregistration of Siemens H.323 gateways at HG 3500 . . . . . . . . . . . . . . . . . . . . . . 9
2.2.7 LEGK-initiated deregistration of Siemens H.323 gateways at HG 3500. . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.8 Call Address Resolution at the HG 3500 LEGK (Local Gateway) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Basic trunking call (voice/fax) between nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.1 SIP-Q signaling at HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.2 SIP-Q on HiPath 4000 with Payload (Local Local Call) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.3 SIP-Q on HiPath 4000 without payload (TSC call, remote local call) . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 End-to-end payload between nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1.1 SIP phone at another HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1.2 HFA phone at another HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4.1.3 TDM phone at another HiPath 4000 remote shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4.1.4 TDM phone at another HiPath 4000 connected via H323 trunking . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.1.5 HFA phone at HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.1.6 SIP phone at HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4.1.7 H323 client at HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4.1.8 TDM Phone at HiPath 3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.2 SIP calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.3 SIP/HFA interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.4 SIP-to-TDM subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.5 HiPath 4000/HiPath 4000 homogenous trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.5.1 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.5.2 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.5.3 Resetting board data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5.4 Trunking configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5.5 Displaying link status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5.6 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3 Configuration example for SIP trunking between homogenous HiPath 4000 nodes . . . . . . . . . . . . . . .
3.1 Configuring an HG 3500 (SIP/H323) as a local gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Configuration in Node 10-69-100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Configuration in Node 10-69-200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.1 Extension in Node 10-69-100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

27
27
28
31
34

sip_trunkingTOC.fm
Service Manual HiPath 4000 V4 - IP Solutions - IP and SIP Trunking - Contents

Nur fr den internen Ge-

3.1.2.2 Call from Node 10-69-100 to Node 10-69-200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Configuration in Node 10-69-200 (without LEGK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Configuration in Node 10-69-100 (with LEGK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Special LCR Features with a Remote Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 LDPLN Extension - Dial Plans for HG 3500 (SIP/H323) Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5 Procedure for Adding Supplementary HG 3500 (SIP/H323) Boards to the Network. . . . . . . . . . . . . .
3.3 H.235 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34
35
35
38
38
40
44
45
45
45

4 Configuration example for SIP trunking between homogenous HiPath 4000 nodes using HiPath 4000
Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.1 Configure Common Gateway HG 3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2 Delete IPGW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3 Modify Board Data of IPGW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5 SIP Trunking Between HiPath 2000/3000/5000 and HiPath 4000 Node. . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.1 Device registration & call address resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.2 Trunking scenarios for HiPath 2000/3000/5000 and HiPath 4000 interworking . . . . . . . . . . . . . . . . . . . . . 53
5.3 Setup for HiPath 3000 and HiPath 4000 interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_01.fm
Overview SIP Trunking
Feature Description

Overview SIP Trunking

1.1

Feature Description

The SIP Trunking feature uses procedures described in the ECMA 355 standard to connect
HiPath 3000/4000/5000 systems via IP-based networks.
Cornet-NQ messages and Cornet-NQ features are tunnelled over SIP (SIP-Q). The SIP Trunking feature once again uses Cornet-NQ trunking over H323 (Cornet-NQ/IP), that is, local node
with SIP registrar on board and remote nodes registering at a local node.
The trunking connection between HiPath 3000, HiPath 4000, and HiPath 5000 is performed via
Cornet-NQ over SIP and H.323.

1.2

SIP Trunking Communication Matrix

Legend for the following tables:

BC

Basic call only

N/I

Not impacted by SIP feature

HiPath
3000

HiPath
4000

HiPath
5000

HiPath
8000

HiQ8k

HiPath 3000

9 (BC)

HiPath 4000

9 (BC)

HiPath 5000

9 (BC)

HiPath 8000

N/I

N/I

9 (BC)

9 (BC)

9 (BC)

N/I

N/I

HiQ8k
Table 1-1

1.3

SIP trunking communication matrix

Boards Used

As of HiPath 4000 V4 the common gateway board HG 3500 is used. Please refer to Gateways
in HiPath 4000 V4, Chapter 2, Overview.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_01.fm

Overview SIP Trunking

Boards Used

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm
SIP trunking between homogenous HiPath 4000 nodes
Restriction for SIP trunking

SIP trunking between homogenous HiPath 4000

nodes

2.1

Restriction for SIP trunking

T38 is not supported with SIP trunking

SRTP is NOT supported for SIP trunking but ONLY for H323 trunking.

Outband signaling and RFC2833 for DTMF are not supported with SIP trunking
Disable the function via the WBM:
WBM -> Explorer -> Payload -> HW-Module

2.2

There are currently no known restrictions for the codec G729.

Device registration & call address resolution

In the case of homogenous HiPath 4000 trunks, each gateway is preconfigured to recognize
whether the gateway is local or remote. Each remote gateway has its gatekeeper preconfigured
in the AMO CGWB. Remote gateway registration is performed by a Large Enterprise
Gatekeeper (LEGK).
Internal gateways are generally registered with the local LEGK. Remote gateways are
registered with the LEGK if the parameter REGGW is entered in the AMO GKREG as a
gateway attribute. If the REGGW gateway attribute is missing from an external gateways
attributes, the gateway is unable to register at the local LEGK and address resolution is not
performed.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

Device registration & call address resolution

Figure 2-1

2.2.1

HiPath-4000-internal SIP trunking

Authentication service via DIGEST

The Digest Access Authentication mechanism described in RFC 2617 is a rather simple challenge/response protocol to authenticate SIP messages. If a SIP message is sent without credentials and the corresponding SIP server is operating in authentication-enabled mode, the SIP
server issues a challenge that requires the client to resend the request, this time with appropriate authentication information: SIP ID, Realm, and Password. This data is checked and validated by the SIP server.
If the check result is positive, the request is confirmed by sending a positive return value (200
OK). However, if the check result is negative, an appropriate response code is returned (401
Unauthorized).
A dedicated challenge is sent depending on the SIP server contacted (user agent or proxy server). The following diagrams illustrate this:
If the user agent client contacts a

user agent server,

registrar server,

redirect server,

response code 401 is used to challenge the client. The response code for the SIP proxy server
contacted must be 407. The SIP header lines WWW-Authenticate/Authorization and
Proxy-Authenticate/Proxy-Authorization must also be used.
The devices supported are always challenged with a 401 response code.

2.2.2

Registration of Siemens SIP Gateways at HG 3500

If authentication requires a realm, this must be added to the gatekeeper parameters.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

Device registration & call address resolution

For digest authentication, all SIP (Siemens) gateways must use the same configured data, user
ID, realm, and password for the gateway. The authentication data is sent by the remote gateway
to the local gateway in the REGISTER message and is checked against the data that is
configured on the local gateway. The data is requested from SSA. If authentication is
successful, the SSA sends the RegisterInd message and registers the SIP gateway at the
LEGK.

2.2.3

Gateway-initiated Deregistration of Siemens SIP Gateways at HG

3500

The digest authentication procedure is performed as described in Section 2.2.2, Registration

of Siemens SIP Gateways at HG 3500. The difference here is that the SIP register message
contains an expiry value = 0 which indicates a deregistration message. If authentication is
successful, the SSA sends the RegisterInd message to deregister the SIP gateway at the
LEGK.

2.2.4

Call address resolution at the HG 3500 (SIP) LEGK (local gateway)

SSA (local) receives an invitation from SSA (remote) which contains the gateway ID and the
parameters ClassMarks, BearerCall, and Teleservice in the non-standard data part. These
parameters are received on the SSA remote side and must be transported to the LEGK at the
local gateway. The local gateway searches the registration objects for IP address and party
number. If an object is found, the SIP subscriber is registered at the local gateway. If there is
no registration object found, LEGK responds with a list of possible destinations. This list ID is
given to the SSA.

2.2.5

Registration of Siemens H.323 gateways at HG 3500

After receiving the RRQ from the remote gateway, the local gateway searches the local
registration objects for the IP address and call number (HG 1500 compatibility reasons). If there
is no object found, a message is sent to the LEGK. LEGK confirms registration to local gateway.

2.2.6

Gateway-initiated deregistration of Siemens H.323 gateways at

HG 3500

After receiving the URQ from the remote gateway, the local gateway searches the local
registration objects for the IP address and call number (HG 1500 compatibility reasons). If there
is no object found, a message is sent to the LEGK. LEGK confirms deregistration to the local
gateway.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

Basic trunking call (voice/fax) between nodes

2.2.7

LEGK-initiated deregistration of Siemens H.323 gateways at HG

3500

If the configuration of an H.323 gateway is deleted in the LEGK than the LEGK sends a
message to HSA. The local gateway clears up its node configuration data and answers the
LEGK.

2.2.8

Call Address Resolution at the HG 3500 LEGK (Local Gateway)

The local gateway receives an ARQ from the remote gateway which contains the gateway ID
and the parameters ClassMarks, BearerCall, and Teleservice in the Oscar NSD. These
parameters are received on the remote side in the MakeCallReq() to HSA and must be
transported to the LEGK at the local gateway. The local gateway searches the registration
objects for IP address and party number. If there is no registration object found, a message is
sent to the LEGK. LEGK answers with a list of possible destination addresses at the local
gateway.

2.3

Basic trunking call (voice/fax) between nodes

2.3.1

SIP-Q signaling at HiPath 4000

This section describes how an SIP-Q call is established and released between HG 3500 cards
on HiPath 4000 nodes.
In general, the Cornet-NQ containers are transported exclusively by the following SIP requests:

INVITE,

INFO, and

BYE.

2.3.2

>

10

SIP-Q on HiPath 4000 with Payload (Local Local Call)

If DMC is activated for an SIP-Q trunking path, Voice Activity Detection (VAD in
WMB) should also be activated. Otherwise the same bandwidth is required for the
master connection as for the slave connection!

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.3.3

SIP-Q on HiPath 4000 without payload (TSC call, remote local

call)

2.4

End-to-end payload between nodes

A non-dmc-enabled endpoint, such as, a TDM phone or an SIP phone behind HiPath 8000
(both connected to the HiPath 4000) calls subscribers in other nodes. A trunking call is therefore initiated via the HG 3500 SIP trunking board to the trunking boards in the other nodes. In
each of these cases, the slave payload terminates at the HG 3500 SIP trunking board in the
node where the TDM subscriber is connected and is then routed through the PBX to the TDM
subscriber.

2.4.1

Scenarios

2.4.1.1

SIP phone at another HiPath 4000

Slave signaling to HG 3500 SIP subscriber board, slave payload to the SIP phone.
HiPath 4000 V4

HiPath 4000 V4
HG3500
SIP-Sub

Master Signalling
connection

HG3500
SIP
Trunk

Master
Signalling & Payload

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

Slave Signalling
connection

e2epc end to end

payload connection

SIP-Phone
SIP-Phone

HiPath 8000

Master Signalling
Master Payload

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

11

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.2

HFA phone at another HiPath 4000

Slave signaling and payload to the HFA phone.

HiPath 4000 V4

HiPath 4000 V4
HG3500
HFA-Sub

Master Signalling
Payload

HG3500
SIP
Trunk

Master
Signalling & Payload

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

Slave Signalling
connection

e2epc end to end

payload connection

SIP-Phone
HFA-Phone

HiPath 8000

Master Signalling
Master Payload

12

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.3

TDM phone at another HiPath 4000 remote shelf

Slave signaling and payload to HG 3575.

HiPath 4000 V4

HiPath 4000 V4
Master
Signalling & Payload

HG3500
HFA-Sub

HG3500
SIP
Trunk

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

Master
Signalling & Payload
Slave Signalling
connection
e2epc end to end
payload connection

SIP-Phone

IPDA
HiPath 8000

HG3575

TDM

Master Signalling
Master Payload

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

13

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.4

TDM phone at another HiPath 4000 connected via H323 trunking

Slave signaling and payload to HG 3500.

HiPath 4000 V4

HiPath 4000 V4

HG3500
H323
Trunk

Master
Signalling & Payload

HG3500
SIP
Trunk

Master
Signalling & Payload

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM
Slave Signalling
connection
e2epc end to end
payload connection

SIP-Phone

HG3500
H323
Trunk

HiPath 8000
HiPath 4000

TDM

Master Signalling
Master Payload

14

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.5

HFA phone at HiPath 3000

Master signaling via HG 1500, master payload between HFA phone and neighboring HG 3500,
slave signaling and payload between HFA phone and initiating HG 3500.

HFA-Phone

HG1500

HiPath 3000 V7

SIP

Slave Signalling
connection
e2epc

HiPath 4000 V4
HG3500
SIP
Trunk

Master
Signalling & Payload

HiPath 4000 V4

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

SIP-Phone

HiPath 8000

Master Signalling
Master Payload

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

15

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.6

SIP phone at HiPath 3000

Master signaling via HG 1500, master payload between SIP phone and neighboring HG 3500
(not shown) gets replaced by slave payload between SIP phone and initiating HG 3500, slave
signaling to HG 1500.

SIP-Phone

HG1500

HiPath 3000 V7

SIP

Slave Signalling
connection
e2epc

HiPath 4000 V4
HG3500
SIP
Trunk

Master
Signalling & Payload

HiPath 4000 V4

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

SIP-Phone

HiPath 8000

Master Signalling
Master Payload

16

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.7

H323 client at HiPath 3000

Master signaling via HG 1500, master payload between H323 client and neighboring HG 3500,
no DMC initiated.

H323
client

HG1500

HiPath 3000 V7

SIP
Master Payload
Master Signalling

HiPath 4000 V4

HiPath 4000 V4
HG3500
SIP
Trunk

Master
Signalling & Payload

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

SIP-Phone

HiPath 8000

Master Signalling
Master Payload

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

17

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.1.8

TDM Phone at HiPath 3000

Master signaling and payload between HG 1500 and neighboring HG 3500, slave signaling and
payload between HG 1500 and initiating HG 3500.

HG1500

HiPath 3000 V7

SIP

Master
Signalling & Payload

TDM

HiPath 4000 V4

HiPath 4000 V4
HG3500
SIP
Trunk

Master
Signalling & Payload

HG3500
SIP
Trunk

HG3500
SIP
Trunk

TDM

SIP-Phone

HiPath 8000

Master Signalling
Master Payload

18

Slave Signalling
Slave Payload

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.2

SIP calls

The following scenario needs to be considered. SIP phone A calls SIP phone B at a remote
HiPath 4000.

Figure 2-2

End-to-end payload between SIP subscriber & SIP subscriber

SIP phone A sets up a connection to HiPath A. HiPath A routes the call via a trunking
connection to HiPath B. HiPath B then sets up a connection to SIP phone B. HiPath B initiates
a DMC between SIP phone B and SIP phone A, resulting in an end-to-end payload connection.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

19

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

2.4.3

SIP/HFA interworking

Figure 2-3

>

20

End-to-end payload between HFA & SIP subscriber (also HG 3575 and SIP
subscriber)

Note that there is no specific action necessary in the HG 3500 SIP trunking boards.
HiPath B initiates a DMC between the SIP phone and HFA phone, resulting in an
end-to-end payload connection. This scenario is described in the SIP subscriber
documentation (see SIP Subscriber, Chapter 4, Direct Media Connect (DMC)).

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

End-to-end payload between nodes

Figure 2-4

End-to-end payload between HFA & SIP trunk (also HG 3575 and SIP trunk)

SIP supports DMC without modification for H.323 (Cornet-IP-NQ) trunking in HG 3500. The
message flows are identical to the SIP-to-TDM flows described in Section 2.4.4, SIP-to-TDM
subscriber, except that the slave setup is issued by HFA or HG 357x and contains their payload
parameters. The slave connection should be handled in the same way as the SIP-to-TDM
connection. The only difference is that in the case of SIP-to-TDM, slave signaling is to the DMC
proxy in the HG 3500 SIP subscriber board.

2.4.4

SIP-to-TDM subscriber

The following scenario needs to be considered. SIP phone A calls TDM phone B at a remote
HiPath 4000.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

21

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

HiPath 4000/HiPath 4000 homogenous trunking

Figure 2-5

HiPath 4000 end-to-end payload between SIP UA and TDM subscriber

SIP phone A sets up a connection to HiPath A. HiPath A routes the call via a trunking
connection to HiPath B. HiPath B then sets up a connection to TDM phone B. HiPath B initiates
a DMC between HG 3500 in HiPath B and the SIP phone.
Note that the DMC payload connection between HG 3500 in HiPath 4000 B and the remote SIP
endpoint is established by the H323 Manager.

2.5

Figure 2-6

22

HiPath 4000/HiPath 4000 homogenous trunking

HiPath 4000 homogenous SIP trunking

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

HiPath 4000/HiPath 4000 homogenous trunking

The HiPath gateway HG 3500 is an integrated, cost-effective IP LAN gateway for HiPath 4000
V4. It offers the following functionality:

Voice-over-IP (VoIP) via the company intranet (backbone for HiPath systems).

Connection-controlled tunneling from CorNet-NQ for connections between HiPath

systems.

Networking via IP between HiPath 4000 V3.0 systems - using the SIP protocol.

Networking via IP between HiPath 4000 V3.0 systems and HiPath 3000/5000 systems >
V4.0 systems using the SIP protocol.

Networking via IP between HiPath 4000 V3.0 systems and HiPath 8000 using the SIP
protocol.

IP access to the HiPath-4000-integrated Large Enterprise Gatekeeper (LEGK) for both

HiPath 4000 V3.0 and HiPath 3000/5000 systems > V6.0.

HiPath 3000/5000 IP payload switching as well as the HiPath 4000 Direct Media
Connection (DMC) approach.

Remote access (RAS/PPP) and firewall functionality to replace the old WAML board for
selected scenarios.

Administration accessible only via HiPath 4000 Assistant.

Support for SIP subscribers

Codecs: G.711, G.729, G.723.

Support for RFC 2833.

Adaptive Jitter Buffer

QoS: IEEE802.1Q, Diffserv.

Fax/Modem-over-IP (FMoIP).

Web-Based Management and SNMP.

2.5.1

User Interface

In order to run AMOs, the user needs to run HiPath Expert Access (ComWin).

2.5.2

Service Information

The HG 3540 gateway is fully integrated in the HiPath 4000 system and is administered by the
system. An upgrade from HG 3550 V2.0 for HiPath 4000 V2.0 to HG 3550 V2.0 for HiPath
4000 V3.0 is only possible by fully deleting the HG 3550 V2.0 for HiPath 4000 V2.0 and
reconfiguring the HG 3550 V2.0 for HiPath 4000 V3.0. It is not possible to migrate data.
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

23

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

HiPath 4000/HiPath 4000 homogenous trunking

2.5.3

Resetting board data

Sometimes it may be useful to reset the board data default settings, for example, if changes to
the HG 3500 settings were not successful. This can be done with the AMO CGWB. However,
these changes are not applied to the mandatory board data which is entered with ADD
command.
Example: Reset all board data except mandatory.
Add parameters must be reset to the default values.
CHANGE-CGWB:MTYPE=INITCGW,LTU=<ltu no>,SLOT=<slot no>,TYPE=ALL;

>

Please note that the parameters MGNTDATA and WBMDATA are considered
feature data and immediately loaded to the board during operation. If the default
values for a certain data type are already enabled, data upload to the board is
suppressed.

INITCGW branch is also used to delete WBM users (not applied to first four -default- users) as
follows:
CHANGE-CGWB:LTU=<ltu no>,SLOT=<slot
no>,MTYPE=INITCGW,TYPE=WBMDATA,LOGINWBM=<string>;
The board must be restarted to upload the reset data to the platform:
RESTART-BSSU:ADDRTYPE=PEN,LTU=<ltu no>,SLOT=<slot no>;

2.5.4

Trunking configuration

The following command adds a HG 3500 IP trunk:

ADD-TDCSU:OPT=NEW,PEN=1-ltu-slot-0,COTNO=<number>,COPNO=<number>,
PROTVAR=ECMAV2,DEV=HG3550IP,LCOSD=<number>,LCOSV=<number>,TGRP=<number>,
BCGR=1,LWPAR=<number>,INS=Y;

>

24

The Loadware parameter block number indicated by the parameter LWPAR must
have MASTER =YES!

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

HiPath 4000/HiPath 4000 homogenous trunking

2.5.5

Displaying link status

The link status of the LAN interface (link signal ethernet, LAN speed, and LAN interface) can
be displayed at each level with the AMO SDSU using the usual commands (PER1, PER2, and
PER3):
DISPLAY-SDSU:TYPE=PEN, LEVEL=PER1, LTG=1, LTU=<ltu no>, SLOT=<slot no>;

2.5.6

Relevant AMOs

AMO

Parameter

Sprache/
Language

Beschreibung/ Description

GKREG

GWATTR=SIP

Gateway Attribut: Gateway untersttzt SIP

GWATTR=SIP

Gateway attribute: Gateway has SIP Capability

WAPLNUM=0

LCR Whlplan Nummer

DIPLNUM=0

LCR dialing plan number

Digest Authentifizierung wird nicht bentigt

GWAUTREQ=NO

Digest authentication is not require

GWREALM

Security Zone des Gateways

GWREALM

Security zone of the gateway

GWSECRET

Gateway Passwort

GWSECRET

Password of the gateway

GWUSERID

Benutzeridentifizierung am Gateway

GWUSERID

User identification of the gateway

REGIP1

IP Adresse des primren SIP Verzeichnisses

REGIP1

IP address of the primary SIP registrar

REGIP2

IP Adresse des sekundren SIP Verzeichnisses

REGIP2

IP address of the secondary SIP registrar

REGPORT1

Port Nummer des primren SIP Verzeichnisses

REGPORT1

Piort number of the primary SIP registrar

REGPORT2

Port Nummer des sekundren SIP Verzeichnisses

REGPORT2

Piort number of the secondary SIP registrar

REGTIME

berwachungszeit in Sekunden fr SIP-Registrierung

REGTIME

Time in seconds the SIP registration is valid

CGWB GWAUTREQ=NEIN

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

25

sip_trunking_02.fm

SIP trunking between homogenous HiPath 4000 nodes

HiPath 4000/HiPath 4000 homogenous trunking

AMO

TDCSU
ZANDE

26

Parameter

Sprache/
Language

Beschreibung/ Description

SIPREG

Registrieren eines Gateways in einem SIP Verzeichnis

SIPREG

Rregister gateway at a SIP registrar

TRPRSIP

LAN Trunk Protokoll: SIP Protokoll ist konfiguriert

TRPRSIP

LAN Trunking Protocol: SIP is configured

TYP=H235DATA

Datentyp: H.235 Sicherheitsdaten

TYPE=H235DATA

Data type: H.235 Security Data

TYP=SIPTRERH

Datentyp: SIP Trunking Daten fr ERH

TYPE=SIPTRERH

Data type: SIP trunking data for ERH

TYP=SIPTRSSA

Datentyp: SIP Trunking Daten fr SSA

TYPE=SIPTRSSA

Data type: SIP trunking data for SSA

DMCERL=NEIN

DMC wird verhindert

DMCALLWD=NO

DMC not allowed

GATEKPR=JA/
NEIN

Gatekeeper Konfigurierung: NEIN=PBX ohne

LEGK

GATEKPR=YES/
NO

Gatekeeper configuration: NO=PBX without gatekeeper

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm
Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

Configuration example for SIP trunking between

homogenous HiPath 4000 nodes

The following example uses a simple constellation to describe the configuration of the SIP
Trunking feature . The aim of this example is to configure IP trunking as simply as possible with
the SIP protocol or the H323 basic settings. For this reason, only the default parameters are
shown at first.
Section 2.5.6, Relevant AMOs provides an explanation of all AMO parameters.
This configuration example is based on a constellation where the LEGK will run on each system
(see Section 3.1, Configuring an HG 3500 (SIP/H323) as a local gateway).
In a subsequent step you will be shown how to configure a remote gateway (see Section 3.2,
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway).

3.1

Configuring an HG 3500 (SIP/H323) as a local gateway

The following diagram shows a HG 3500 (SIP/H323) scenario for a fictitious customer in Frankfurt. It shows node 10-69-100 (Frankfurt-Bockenheim) and node 10-69-200 (Frankfurt-Sachsenhausen). Both systems have an STMI2/4 board that should be configured as HG 3500 (SIP/
H323). LEGK should be active on both systems (two local gateways). This constellation is relatively easy to explain because both nodes can be configured more or less symmetrically. The
figure shows all necessary parameters. Node 10-69-100 is located in IP network 1.69.11.0/24
and node 10-69-200 is located in IP network 1.69.21.0/24. The networks reach each other over
the routers Ra and Rb.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

27

sip_trunking_03.fm

DEFRT

1.69.11.254

HG 3500
(SIP /
H323)

HG 3500

Ra

Rb

(SIP /

Router

Router

H323)

IP Networ k

Kunden-LAN

IPADR:
1.69.11.80
NETMASK
255.255.255.0
GWID:
TEST01
GWNR:
1
GWRNR:
816901

1.69.21.254

HiPath 4000

3.1.1

IPADR:
1.69.21.80
NETMASK:
255.255.255.0
GWID::
TEST02
GWNR:
2
GWRNR:
816902

HiPath 4000
KN 10-69-200

KN 10-69-100

Figure 3-1

STMI 2/4

DEFRT

Kunden-LAN

STMI 2/4

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

Configuration example: both nodes are LEGK

Configuration in Node 10-69-100

Start by configuring the board as HG 3500 (SIP/H323) in node 100. To avoid repeated restarts,
do not insert the board until configuration is complete.
NOTE 1:
Step 0:
Depending on the initial situation (remote gatekeeper or LE gatekeeper), it may be necessary
to set an LE gatekeeper with the AMO ZANDE.
CHANGE-ZANDE:TYPE=ALLDATA,GATEKPR=YES;
Step 1:
Configure STMI2/4 as HG 3500 (SIP/H323). Q2316-X is the version with 60 B channels.

28

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

ADD-BFDAT:FCTBLK=1,FUNCTION=HG3550,BRDBCHL=BCHL60&BCHL120;
CHANGE-BFDAT:CONFIG=CONT,FCTBLK=1,FUNCTION=HG3550,LINECNT=1,LINEUNIT=3; /*
30 b-channels for HG3550 function (IP trunking, SIP trunking, SIP subscribers)
CHANGE-BFDAT:CONFIG=OK,FCTBLK=1,ANSW=YES;
ADD-BCSU:TYP=IPGW,LTG=1,LTU=1,EBT=37,PARTNO=Q2316-X
TID=1,LWVAR=0,FCTBLK=1,BCHL3550=30,ALARMNO=0;

,FC-

Step 2:
The AMO CGWB allows the board to receive the IP address in the customer LAN (LAN1), the
subnet mask and the protocol variants (NONE (board is only configured for SIP subscribers) /
SIP / H323).

>
ADD-CGWB:LTU=1,SLOT=37,SMODE=NORMAL,IPADR=1.69.11.80,NETMASK=255.255.255.0;
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=GLOBIF,TRPRSIP=10; /*10 b-channels for SIP trunking
=> There are 20 b-channels left for SIP subscribers
or
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=GLOBIF,TRPRH323=10; /*10 b-channels for IP trunking
=> There are 20 b-channels left for SIP subscribers
Step 3:
The default router is now set in the customer LAN:
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=GLOBIF,DEFRT=1.69.11.254;
Step 4:
HG 3500 requires a network-unique ID only for H323. This parameter is known as GWID in
the AMO CGWB:
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=GWDATA,GWID1=TEST01;
GWID1 and GWID2 together form a contiguous value consisting of 128 characters. Entries are
case-sensitive.
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

29

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

Step 5:
The gateway also needs a separate directory number (GWDIRNO) for the TSC connection.
The directory number must be unique in the network. The HG 3500 (SIP/H323) boards are also
administered using a gateway number (GWNO). This must also be unique.
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=LEGKDATA,GWNO=1,GWDIRNO=816901;
The following registration parameters are also required for the components SSA and ERH in
for SIP:
ERH:
CHA-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=SIPTRERH,GWAUTREQ=NEIN;
CHANGE-CGWB:MTYPE=CGW,...,TYPE=SIPTRERH,GWAUTREQ=<param>,GWSECRET=<param>,GWUSERID=<param>,GWREALM=<param>;
SSA:
CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=37,TYPE=SIPTRSSA,SIPREG=NO;
CHANGECGWB:CGWB=CGW,LTU=1,SLOT=37,TYPE=SIPTRSSA,SIPREG=<param>,REGIP1=<ip>,REGPOR
T1=<number>,REGIP2=<ip>,REGPORT2=<number>,REGTIME=<sec>;
Step 6:
This step involves multiple configuration commands. The TSC connection addressed should
now be configured. In the case of a local gateway, when an HG 3500 (SIP/H323) is inserted,
the HiPath 4000s DeviceHandler informs the LEGK that a communication connection must be
set up to this HG 3500 (SIP/H323). The LEGK then dials the GWDIRNO to set up this TSC connection. The TSC connection remains open as long as the board is active.
First you need a trunk group:
ADD-BUEND:TGRP=50,NAME=IP TRUNK GWID 1

,NO=30;

A digital trunk is then required (AMO TDCSU). The device type is HG3550IP for IP trunking with
HG 3500 (SIP/H323). If you want to allow DMC, DMCALLWD=Y must be set. COT requires the
TSCS parameter.
ADD-TDCSU:OPT=NEW,PEN=1-01-037-0,COTNO=36,COPNO=32,DPLN=0,ITR=0,
COS=2,LCOSV=1,LCOSD=1,CCT=CIRCUIT from GW2,PROTVAR=ECMAV2,SEGMENT=8,
ISDNIP=00,ISDNNP=0,TRACOUNT=31,SATCOUNT=MANY,NNO=1-69-1499,ALARMNO=12,
COTX=36,CCHDL=SIDEA,CLASSMRK=EC&G711,TCCID=IP RS,TGRP=50,SRCHMODE=DSC,
INS=Y,DEV=HG3550IP,BCHANNEL=1&&30,BCNEG=N,BCGR=1,LWPAR=0(=Master),DMCALLWD=N;
Note: It is recommended to reset the board with

30

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

RESET-BSSU:ADDRTYPE=PEN,LTG=1,LTU=1,SLOT=37;
You can now proceed with the actual configuration of the TSC connection. The gateway directory number (GWDIRNO) from the AMO CGWB is a tie number in the actual system:
ADD-WABE:CD=816901,DAR=TIE;
The tie number is routed to the IP trunking trunk group:
ADD-RICHT:MODE=LRTENEW,LRTE=500,LSVC=ALL,NAME=HG3550 GW1,TGRP=50,DNNO=169-499;
ADD-LODR:ODR=2,CMD=ECHO,FIELD=1;
ADD-LODR:ODR=2,CMD=END;
ADD-LODR:ODR=2,INFO=GW TSC;
ADD-LDAT:LROUTE=500,LSVC=ALL,LVAL=1,ODR=50,LAUTH=2,TGRP=1;
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=816901,LROUTE=500,LAUTH=1;
Note: The command CHANGE-FUNSU can prevent the complete reloading of the STMI board
(duration approx. 8 min). Reloading is only necessary in the case of LW changes.
/* Gateway
CHANGE-FUNSU:PIT=FLASH,PARTNO=Q2316-X

,FCTID=2,ACTION=RESET.

Step 7:
The LEGK now has to be informed about the existence of the HG 3500 (SIP/H323) gateway
using the AMO GKREG. The GWNO must match the entry in the AMO CGWB. In the case of
a local gateway, the AMO GKREG automatically downloads the GWDIRNO and the IP address
(IPADR) from the AMO CGWB. You must also set the attributes INTGW (internal local gateway), REGGW (gateway that logs on to this LEGK), and HG 3500 (SIP/H323) (version ID).
ADD-GKREG:GWNO=1,GWATTR=INTGW&REGGW&HG3550V2&SIP or
H323,DIPLNUM=0,DPLN=0,LAUTH=1;
If you enter DIS-GKREG; now, REGISTERED=YES should appear for this HG 3500 (SIP/
H323).
This indicates that the HG 3500 (SIP/H323) board is working in node 10-69-100 (dont forget
board links) and is communicating with the LEGK. However, the gateway is still missing in the
partner node.

3.1.2

Configuration in Node 10-69-200

An LEGK should also be active in node 10-69-200. As the configuration procedures for nodes
10-69-200 and 10-69-100 are identical, this section only lists the appropriate AMO commands
for the steps described above.
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

31

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

Step 1:
ADD-BFDAT:FCTBLK=1,FUNCTION=HG3550,BRDBCHL=BCHL60&BCHL120;
CHANGE-BFDAT:CONFIG=CONT,FCTBLK=1,FUNCTION=HG3550,LINECNT=1,LINEUNIT=3; /*
30 b-channels for HG3550 function (IP trunking, SIP trunking, SIP subscribers)
CHANGE-BFDAT:CONFIG=OK,FCTBLK=1,ANSW=YES;
ADD-BCSU:TYPE=IPGW,LTG=1,LTU=2,SLOT=49,PARTNO=Q2316-X
TID=1,LWVAR=0,FCTBLK=1,BCHL3550=30,ALARMNO=0;

,FC-

Step 2:
ADD-CGWB:LTU=2,SLOT=49,SMODE=NORMAL,IPADR=1.69.11.80,NETMASK=255.255.255.0;
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GLOBIF,TRPRSIP=10; /*10 b-channels for SIP trunking
=> There are 20 b-channels left for SIP subscribers
or
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GLOBIF,TRPRH323=10; /*10 b-channels for IP trunking
=> There are 20 b-channels left for SIP subscribers
Step 3:
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GLOBIF,DEFRT=1.69.21.254;
Step 4:
Only for H323 gateways
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GWDATA,GWID1=TEST02;
Step 5:
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=LEGKDATA,GWNO=2,GWDIRNO=816902;
The following registration parameters are also required for the components SSA and ERH in
for SIP:
ERH:
CHA-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=SIPTRERH,GWAUTREQ=NO;

32

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=SIPTRERH,GWAUTREQ=<param>,GWSECRET=<param>,GWUSERID=<param>,GWREALM=<param>;
SSA:
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=SIPTRSSA,SIPREG=NO;
CHANGECGWB:MTYPE=CGW,LTU=2,SORT=49,TYPE=SIPTRSSA,SIPREG=<param>,REGIP1=<ip>,REGPO
RT1=<number>,REGIP2=<ip>,REGPORT2=<number>,REGTIME=<sec>;
Step 6:
ADD-BUEND:TGRP=50,NAME=IP TRUNK GWID 2

,NO=30;

ADD-TDCSU:OPT=NEW,PEN=1-02-049-0,COTNO=36,COPNO=32,DPLN=0,ITR=0,
COS=2,LCOSV=1,LCOSD=1,CCT=CIRCUIT from GW2,PROTVAR=ECMAV2,SEGMENT=8,
ISDNIP=00,ISDNNP=0,TRACOUNT=31,SATCOUNT=MANY,NNO=1-69-1499,ALARMNO=12,
COTX=36,CCHDL=SIDEA,CLASSMRK=EC&G711,TCCID=IP RS,TGRP=50,SRCHMODE=DSC,
INS=Y,DEV=HG3550IP,BCHANNEL=1&&30, BCNEG=N,BCGR=1,LWPAR=0(=Master),DMCALLWD=N;

ADD-WABE:CD=816902,DAR=TIE;
ADD-RICHT:MODE=LRTENEW,LRTE=500,LSVC=ALL,NAME=HG3550 GW2,TGRP=50,DNNO=169-499;
ADD-LODR:ODR=2,CMD=ECHO,FIELD=1;
ADD-LODR:ODR=2,CMD=END;
ADD-LODR:ODR=2,INFO=GW TSC;
ADD-LDAT:LROUTE=500,LSVC=ALL,LVAL=1,ODR=50,LAUTH=2,TGRP=1;
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=816902,LROUTE=500,LAUTH=1;
Step 7:
The GKREG now contains the configuration for both HG 3500 (SIP/H323) boards. GWNO=2
is here in node 10-69-200 the local gateway with the attributes INTGW,REGGW und
HG 3500 (SIP/H323), while in this system the GWNO=1 (the partner gateway in node 10-69100) receives the attributes EXTGW, HG 3500 and SIP/H323. The IP address and the GWDIRNO must be specified for the external gateway because the associated AMO CGWB is configured in the partner system.
ADD-GKREG:GWNO=1,GWATTR=EXTGW&HG3550V2&SIP or H323,GWIPADDR=1.69.11.80,
GWDIRNO=816901,DIPLNUM=0,DPLN=0,LAUTH=1;
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

33

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a local gateway

ADD-GKREG:GWNO=2,GWATTR=INTGW&REGGW&HG3550V2&SIP or H323,
DIPLNUM=0,DPLN=0,LAUTH=1;
3.1.2.1

Extension in Node 10-69-100

The HG 3500 (SIP/H323) in node 10-69-200 must be retrofitted in node 10-69-100 for LEGK
(AMO GKREG). For node 10-69-100, this HG 3500 (SIP/H323) (GWNO=2) is an external gateway (attributes EXTGW&HG3550V2&SIP/H323) and is not registered in node 323-10-69.
ADD-GKREG:GWNO=2,GWATTR=EXTGW&HG3550V2&SIP or H323,
GWIPADDR=323.1.69.21,GWDIRNO=816902,DIPLNUM=0,DPLN=0,LAUTH=1;
Now DIS-GKREG; should be displayed in node 10-69-100: GWNO=1 is registered and
GWNO=2 is not registered. GWNO=1 should not be registered and GWNO=2 should be registered in node 10-69-200.
3.1.2.2

Call from Node 10-69-100 to Node 10-69-200

LCR should now be configured for node 10-69-100 in our example so that a station using open
numbering (UNKNOWN) in this node can reach a station in node 10-69-200 over the IP trunk.
Closed numbering or ISDN numbering plans are also supported and configured in the same
way.
A station in node 10-69-100 reaches node 10-69-200 over the tie number 902.
ADD-WABE:CD=902,DAR=TIE;
LRTE 520 should route to node 10-69-200 and use trunk group 50 (see above):
ADD-RICHT:MODE=LRTENEW,LRTE=520,LSVC=ALL,NAME=IP TO KN 69 200,TGRP=50,DNNO=1-69-499;
The following is a simple outdial rule:
ADD-LODR:ODR=520,CMD=ECHO,FIELD=2;
ADD-LODR:ODR=520,CMD=END;
ADD-LODR:ODR=520,INFO=TIE TO GW2;
Enter GW1=2-0 in LRTE 520 now. The 2 refers to the parameter GWNO in the AMO GKREG
(section 3.2.1.3). In the GKREG for node 10-69-100, the HG 3500 (SIP/H323) with GWNO=2
is the IP address 1.69.21.80. The 0 stands for the sector path number and is only of importance
if resource management is configured. Sector path 0 means there is unlimited bandwidth for
this path. If the destination gateway is not reachable, you can use the parameters GW2 to GW5
to configure an alternative route.
ADD-LDAT:LROUTE=520,LSVC=ALL,LVAL=1,TGRP=50,ODR=520,LAUTH=1,GW1=2-0;
The tie number is entered in the LDPLN. The directory number is entered in the default dial plan
with DIPLNUM=0. A profile index can also be used instead of LRTE (AMO LPROF):

34

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=902-X,LROUTE=520,LAUTH=1;
If you want to be able to reach node 10-69-100 from node 10-69-200, perform the following configuration. Naturally, GWNO=1 is entered in the AMO LDAT for this.

3.2

Configuring an HG 3500 (SIP/H323) as a Local and as a Remote

Gateway

DEFRT

1.69.11.254

HG 3500

DEFRT
HG 3500

1.69.21.254

(SIP /

(SIP /
H323)

Ra

Rb

Router

Router

STMI 2/4

STMI 2/4

This section describes a new scenario where an HG 3500 (SIP/H323) is configured in a HiPath
4000 node that does not feature an LEGK. A gateway of this kind is known as a remote gateway.
Our example (from Section 3.1, Configuring an HG 3500 (SIP/H323) as a local gateway)
should be modified accordingly. Node 10-69-100 has an LEGK and a local gateway while node
10-69-200 has no LEGK and a remote gateway.

H323)

remote GW
local GW

IPADR:
1.69.21.80
NETMASK:
255.255.255.0
GWID::
TEST02
GWNR:
2
GWRNR:
806902
PRIGKIP:
1.69.11.80

Kunden-LAN

IPADR:
1.69.11.80
NETMASK
255.255.255.0
GWID:
TEST01
GWNR:
1
GWRNR:
816901

Kunden-LAN

IP Networ k

PRIGKID:
TEST01
WAPLNUM:
2

HiPath 4000

HiPath 4000
KN 10-69-200

KN 10-69-100

Figure 3-2

3.2.1

Constellation with LEGK only in node 10-69-100

Configuration in Node 10-69-200 (without LEGK)

In this case, you should start with 10-69-200 because this is where the major changes are
made.
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

35

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

Step 0:
The LEGK function is disabled in node 10-69-200 (this function is enabled by default).
CHANGE-ZANDE:TYPE=ALLDATA,GATEKPR=NO;
Step 1:
Configuring the board.
ADD-BFDAT:FCTBLK=1,FUNCTION=HG3550,BRDBCHL=BCHL60&BCHL120;
CHANGE-BFDAT:CONFIG=CONT,FCTBLK=1,FUNCTION=HG3550,LINECNT=1,LINEUNIT=3; /*
30 b-channels for HG3550 function (IP trunking, SIP trunking, SIP subscribers)
CHANGE-BFDAT:CONFIG=OK,FCTBLK=1,ANSW=YES;
ADD-BCSU:TYPE=IPGW,LTG=1,LTU=2,SLOT=49,PARTNO=Q2316-X
TID=1,LWVAR=0,FCTBLK=1,BCHL3550=30,ALARMNO=0;

,FC-

Step 2:
The HG 3500 (SIP/H323) receives its settings.
ADD-CGWB:LTU=2,SLOT=49,SMODE=NORMAL,IPADR=1.69.11.80,NETMASK=255.255.255.0;
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GLOBIF,TRPRSIP=10; /*10 b-channels for SIP trunking
=> There are 20 b-channels left for SIP subscribers
or
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GLOBIF,TRPRH323=10; /*10 b-channels for IP trunking
=> There are 20 b-channels left for SIP subscribers
Step 3:
The HG 3500 (SIP/H323) has the following default router.
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GLOBIF,DEFRT=1.69.21.254;
Step 4a:
This is where the HG 3500 (SIP/H323) is told which network-based partner gateway should be
used to reach the LEGK. This partner gateway must be a local gateway in the partner node.
The port number (PRIGKIP) is always 1719. The parameter PRIGKID1 (PRIGKID2) must
match the parameter GWID1 (GWID2) in the local gateways CGWB (entries are case-sensi-

36

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

tive). You can also configure redundancy here. If the gatekeeper entered here as the primary
gatekeeper is not available, you can enter another local gateway as the secondary gatekeeper.
The secondary gatekeeper can be a local gateway in the same node as the primary gatekeeper
or it can be located in another HiPath 4000 node.
For H323 gateways:
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GKDATA,PRIGKIP=1.69.11.80,
PRIGKPN=1719,PRIGKID1=TEST01;
For SIP gateways:
CHA-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=SIPTRSSA,SIPREG=YES,
REGIP1=1.69.11.80,REGPORT1=5060,REGTIME=120;
CHA-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=SIPTRERH,GWAUTREQ=NO;
CHA-CGWB:MTYPE=CGW,....,TYPE=SIPTRSSA,SIPREG=<param>,REGIP1=<ip>,
REGPORT1=<number>,REGIP2=<ip>,REGPORT2=<number>,REGTIME=<sec>;

>

Should an authentication, GWAUTREQ=YES, be activated for the registration of a

remote gateway with the LEGK, all remote gateways and the LEGK (local gateway)
in the network must receive the same authentication data (parameters: GWSECRET, GWUSERID and GWREALM).

CHAE-CGWB:MTYPE=CGW,....,TYPE=SIPTRERH,GWAUTHREQ=<param>,
GWSECRET=<param>,GWUSERID=<param>,GWREALM=<param>;
Step 4b:
Only with H323 must the gateway still have a separate GWID:
CHANGE-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=GWDATA,GWID1=TEST02;
Step 5:
Like a local gateway, the remote gateway also requires a directory number (GWDIRNO). The
GWDIRNO uses the remote gateway to register at the LEGK. A TSC connection is not configured in the system without LEGK. In addition, the remote gateway does not need a gateway
number in its system. This is set in the LEGK systems GKREG.
CHA-CGWB:MTYPE=CGW,LTU=2,SLOT=49,TYPE=LEGKDATA,GWDIRNO=816902;

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

37

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

Step 6:
As in the case of a local gateway, you now have to configure a trunk group (here the number
50) and the IP circuit. However, a TSC connection must not be configured in this node as the
connection from remote to local gateway is one IP connection. Information on the necessary
parts of step 6 can be found in Section 3.1.2, Configuration in Node 10-69-200, Step 6.
Step 7:
Not applicable because node 10-69-200 does not have an LEGK or an AMO GKREG.

3.2.2

Configuration in Node 10-69-100 (with LEGK)

HG 3500 (SIP/H323) is configured in the same way as before because nothing has changed in
this node. The difference for this node here is that a remote gateway wants to log on to this
LEGK. To do this, proceed as follows: first of all, enter DAR=gateway for the gateway directory
number (GWDIRNO) of the remote gateway in the LEGK node. (Note sequence)
ADD-WABE:CD=816902,DAR=GATEWAY;
Then, add the remote gateway to the GKREG. The remote gateway must register at the LEGK
and needs the attribute REGGW for this. The IP address and GWDIRNO must be specified because they are not known in the LEGK system.
ADD-GKREG:GWNO=2,GWATTR=EXTGW&REGGW&HG3550V2&SIP or H323,GWIPADDR=1.69.21.80,GWDIRNO=816902,DIPLNUM=0,DPLN=1,LAUTH=1;
If you have configured the AMO GKREG appropriately, registered=yes should appear for
GWNO=1 and GWNO=2 if you enter DIS-GKREG.

3.2.3

Special LCR Features with a Remote Gateway

Now, lets assume that you have configured open numbering from node 10-69-100 to node 1069-200. In this case, nothing changes because the LRTE in this node first routes to a local gateway that obtains the IP address of the destination gateway from its own nodes LDAT and
GKREG.
This situation is different in node 10-69-200. Lets assume you configured open numbering in
node 10-69-200 as follows:
ADD-WABE:CD=901,DAR=TIE;
ADD-RICHT:MODE=LRTENEW,LRTE=511,LSVC=ALL,NAME=TO KN100 GW1,TGRP=50,DNNO=1-69-499;
ADD-LODR:ODR=511,CMD=ECHO,FIELD=2;
ADD-LODR:ODR=511,CMD=END;

38

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

ADD-LODR:ODR=511,INFO=OPEN REMOTE GW;

ADD-LDAT:LROUTE=511,LSVC=ALL,LVAL=1,TGRP=50,ODR=511,LAUTH=1;
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=901-X,LROUTE=511,LAUTH=1;
The subscriber in node 10-69-200 dials tie number 901 - extension in node 10-69-100. This
subscriber is then forwarded to LROUTE 511 which leads to trunk group 50 in the remote gateway. The remote gateway now sends an admission request over the local gateway to the LEGK
(AMO CGWB, PRIGKIP). The node 10-69-100 extension is specified as the called number in
this admission request but the GWDIRNO from the AMO CGWB is specified as the calling number.
Node 10-69-100 accepts the admission request and resolves the called number in its own
DPLN (it is one of its own stations). In this case, the LEGK returns the IP address of the local
gateway to the remote gateway. The remote gateway in node 10-69-200 then performs call setup with the calling number of the A station and the called number of the B station (as per the
admission request).
The procedure is similar for closed numbering. If the called number to be resolved in the LEGK
system leads to a DPLN entry with a destination number not equal to 0, a search is performed
for a matching LROUTE. This can lead to both a digital or analog tie trunk (result: DID to a third
system) and an LDAT/GKREG combination where the requesting remote gateway is transferred to the IP address of a partner HG 3500.
The following diagram provides a simplified overview of the procedure when the SUB 7240 on
node 200 calls subscriber 7340 on node 7340 (example of closed numbering).
The LCR of node 200 routes the called number to its own remote gateway (RGW). The remote
gateway must then request the IP address for 7340 from the LEGK. It issues an admission request to the LEGK via the local gateway (LGW) (step 1). The admission request consists of the
calling number, the gateway directory number (GWDIRNO), the called number and the SUB
number 7340. The remote gateway is identified by the GWDIRNO and has LAUTH and DPLN
from the AMO GKREG for the admission request. The LEGK must now resolve the phone number. In cases such as this, it finds the called number in the WABE (closed numbering). In the
LDAT, the gateway number for 7340 is found, which can then be assigned an IP address of a
destination gateway via the AMO GKREG (step 2). The LEGK then sends the destination IP
address via LGW to the RGW (step 3).
In step 4, the RGW can continue the call setup stopped before the admission request. It now
sets up a call to the destination gateway. The calling number is now the SUB number 7240 and
called number the SUB number 7340. In node 300, the call is finally assigned to the subscriber
7340.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

39

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

Figure 3-3

Simplified procedure for call number resolution for an RGW.

What would happen if the called number could not be resolved in node 10-69-100s DPLN but
rather as an external directory number in the LDPLN, for example, as in the case of DID to the
CO? In such a case, the node 10-69-100 LEGK would have to resolve the admission request
over the standard LDPLN and lead to the trunk group. But the remote gateway cannot reach
this trunk group - it first needs the IP address of a destination gateway. The LDPLN was consequently extended as explained in the following section.

3.2.4

LDPLN Extension - Dial Plans for HG 3500 (SIP/H323) Boards

This example is based on the constellation with only one LEGK in the network. The node 1069-100 LEGK is the CO access for node 10-69-200. Lets first consider 10-69-200.
Node 10-69-200 has an LRTE to node 10-69-100, for example, in the case of national ISDN
(LRTE=192,TRGP=50):

40

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

ADD-RICHT:MODE=LRTENEW,LRTE=192,LSVC=ALL,NAME=CO NATIONAL,TGRP=50,DNNO=11-0,
For the sake of completeness, outdial rule 92 is provided:
ADD-LODR:92,,,,ECHO,4;
ADD-LODR:92,,,,NPI,ISDN,NATIONAL;
ADD-LODR:92,,,,END;
ADD-LODR:92,,,ICN-CO ISDN NATIONAL;
The LDAT for LROUTE=192:
ADD-LDAT:LROUTE=192,LSVC=ALL,TGRP=50,ODR=92,LAUTH=3;
In the LDPLN, the national ISDN digit pattern is linked to LROUTE 192.
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP=0-W-0-X,LROUTE=192,LAUTH=3;
The remote gateway now needs the IP address of the local gateway. It consequently issues an
admission request in the node 10-69-100 LEGK.
The node 10-69-100 LEGK accepts the called number but its LDPLN in the system leads directly to the trunk group and not to the IP address of the local gateway. In order to evaluate the
digit pattern with another LROUTE, 8*256 LCR dial plans are configured in the LDPLN. These
dial plans can be linked with 2048 dial plan numbers. All stations and circuits select the default
dial plan number 0 in the LDPLN. Only HG 3500 (SIP/H323) boards have access to LCR in the
dial plans numbered 1-2047 that are designed to answer admission requests from remote gateways.
In the LDPLN, dial plans not equal to 0 are only configured if there are remote gateways
in the network and only on the LEGK system.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

41

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

The following table is a schematic representation of the new AMO LDPLN.

LWMPOOL 1 LWMPOOL 2 LWMPOOL 3 LWMPOOL 4 LWMPOOL 5 LWMPOOL 6 LWMPOOL 7 LWMPOOL 8
Diplnum 0,
Dialpln 0

Dialpln 0

Dialpln 0

Dialpln 0

Dialpln 0

Dialpln 0

Dialpln 0

Dialpln 0

Dialpln 255

Dialpln 255

Dialpln 255

Dialpln 255

Dialpln 255

Dialpln 255

Dialpln 255

Dialpln 1

to

Dialpln 255

Table 3-1

Configuring AMO LDPLN

The AMO LDPLN is configured as a matrix in the HiPath 4000 V2. A column is created for each
LWM pool. Up to 8 LWM pools can be configured. LWM pool 1 is prefigured by default. The DIMSU memory must be configured for pools 1-8 (AMO DIMSU, TYPE=NETWORK, Parameter:
LDPLN1...8/LDPLNC1...8). Each pool can contain 64000 digit patterns.
The lines of the LDPLN matrix are determined by the dial plans (LDPLN parameter DIALPLN).
Each LWN pool can contain 256 dial plans. The parameter DIALPLN is not a mandatory parameter. If it is not set by the administrator, HiPath 4000 automatically defines it.
LWM pools and dial plans only define the appearance of LDPLNs. Only the dial plan number
(DIPLNUM) effects the analysis.
The DIPLNUM 0 is prefigured and contains all digit patterns, which were available in earlier LDPLN versions. This is where dialing for all subscribers and circuits is analyzed.
The DIPLNUMs 1-2047 can be assigned by the administrator. The digit patterns, which are
configured here are only relevant to the admission request from remote gateways.
The DIPLNUM must then be configured in LDPLN under LCRADM. Specifying LWMPOOL and
DIPLN only serves to position the dial plan in the LDPLN matrix.
This is illustrated in the following example.
First configure a new dial plan (DIPLNUM=2) in the LDPLN (KN 10-69-100):
ADD-LDPLN:LCRCONF=LCRADM, DIPLNUM=2,LWMPOOL=1,DIALPLN=2;
As mentioned above, DIALPLN can also be left blank. HiPath 4000 then automatically assigns
it an arbitrary value. However, it is more convenient if the DIPLNUM and DIALPLN settings in
LWMPOOL 1 are the same.

42

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

If the number of digit patterns you want to configure in the LEGK system exceeds the number
permitted by the DIMSU memory, you can map the dial plan (in this case, 2) to another LWMPOOL (2-8). You can configure up to 64000 digit patterns in each of these eight pools.
You can now assign dial plan 2 to the remote gateway (GWNO=2) in the AMO GKREG:
CHANGE-GKREG:GWNO=2,DIPLNUM=2,DPLN=0,LAUTH=2;
Important: DPLN and LAUTH are important for the admission request.
A new LRTE (LRTE 292) is now added to the national ISDN digit pattern in the node 10-69-100
LEGK. A trunk group is not configured because this LRTE is only used for IP address resolution.
ADD-RICHT:MODE=LRTENEW,LRTE=292,LSVC=ALL,NAME=ADDR RESOLUTION, DNNO=1-20;
In LDAT, LROUTE 292 is assigned to the IP address of the local gateway (GW1=1-0):
ADD-LDAT:LROUTE=292,LSVC=ALL,ODR=92,LAUTH=2,GW1=1-0;
Finally, the national digit pattern of LROUTE 292 is assigned to dial plan 2:
ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=2,LDP=0-W-0-X,LROUTE=292,LAUTH=2;
The LEGK can therefore respond to the remote gateways admission request with
LROUTE=292. The entry under GW1 is assigned as the first choice circuit group, and the entries under GW2 to GW5 as second to fifth choice circuit group for the remote gateway. In our
example, the remote gateway sets up a call to the local gateway (GWNO=1) with the calling
number of subscriber A and the called number of subscriber B. In the destination system (1069-100) the number dialed is now analyzed in the default dial plan and, if allowed and possible,
a trunk connection is established.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

43

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
Configuring an HG 3500 (SIP/H323) as a Local and as a Remote Gateway

DEFRT

1.69.11.254

HG 3500

1.69.21.254

HG 3500

(SIP /

Ra

Rb

H323)

Router

Router

(SIP /
H323)

STMI 2/4

STMI 2/4

DEFRT

remote GW

IP Networ k

DIUN
HiPath 4000
KN 10-69-100

Figure 3-4

Custo me r LAN

IPADR:
1.69.11.80
NETMASK
255.255.255.0
GWID:
TEST01
GWNR:
1
GWRNR:
816901

Cust omer LAN

local GW

Central
Office

IPADR:
1.69.21.80
NETMASK:
255.255.255.0
GWID::
TEST02
GWNR:
2
GWRNR:
806902
PRIGKIP:
1.69.11.80
PRIGKID:
TEST01

HiPath 4000
KN 10-69-200

Node 10-69-100 is a central LEGK, node 10-69-200 has a remote gateway and
breaks out into the CO over 10-69-100.

Different remote gateways can use the same dial plans in the LEGK system. If you need another LROUTE, however, you must assign another dial plan to the remote gateway.
As soon as a remote gateway uses a specific dial plan other than 0, all digit patterns leading to
an LDAT other than the corresponding entry in dial plan 0, must be entered if open numbering
is used.

3.2.5

Procedure for Adding Supplementary HG 3500 (SIP/H323) Boards

to the Network

Additional remote gateways are added in the same way as the remote gateway described, in
other words, BFDAT, BCSU and CGWB are used for configuration in the own node and GKREG
and LDAT in the LEGK system.

44

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
H.235 Security

Additional LEGKs can be configured in the same way as node 10-69-100. In this case, BFDAT,
BCSU, CGWB, GKREG, and LDAT are in a single node. The GKREG must recognize all HG
3500 (SIP/H323) boards in the network so that it can perform address resolution for its registered local and remote gateways.

3.3

H.235 Security

3.3.1

Feature Description

The H.235 security feature is designed to prevent unauthorized devices setting up connections
to a HG 3500 (SIP/H323) gateway. An example of such a scenario would be a Netmeeting client
that wishes to use a HG 3500 (SIP/H323).
The security concept is based on two mechanisms: When the features are activated, HG 3500
(SIP/H323) sends a token in each signaling packet (consisting of a password and key, defined
in AMO CGWB), to authenticate itself to a receiving HG 3500 (SIP/H323) gateway.
In the AMO CGWB a time frame is set. By default, the difference between the time stamp of an
arriving H.323 signaling packet and the current time of the receiving HG 3500 (SIP/H323) cannot exceed 10 seconds.
A time sever is thus required for this feature. If the gateways are in other time zones, this must
be set on the HG 3500 (SIP/H323) boards.

3.3.2

Generation

To activate the H.235 security feature on the board, you set the security flag using the AMO
ZANDE. This activates H.235 data in the AMO CGWB on the board.
Once you have activated the H.235 security feature with the AMO ZANDE, you must reboot the
board to activate the changes.
CHANGE-ZANDE:ALLDATA,H235SEC=YES;
CHANGE-CGWB: MTYPE=CGW,LTU=<ltu no>,SLOT=<slot
no>,TYPE=H235DATA,GLOBID1=<string>,GLOBID2=<string>,TIMEWIN=10,GLOBPW=<number>;

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

45

sip_trunking_03.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes
H.235 Security

46

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_04.fm
Configuration example for SIP trunking between homogenous HiPath 4000 nodes using
Configure Common Gateway HG 3500

Configuration example for SIP trunking between

homogenous HiPath 4000 nodes using HiPath
4000 Assistant

4.1

Configure Common Gateway HG 3500

>

Configuration of HG 3500 SIP (CGW) board is prerequisite for SIP subscriber support. It can be also done via Assistant application.

In order to configure CGW board do the following:

Step 1: Configure function block

Step 2: Search for a free slot

Step 3: Open Board configuration menu in HiPath 4000 CM Assistant

Step 4: Add new board

Step 5: Filling in the mask

Step 6: Open STMI2-IGW Board Data dialog and fill mandatory fields

Step 1: Configure function block

Start CM -> System Data -> Board -> CGW Function Block
Click Search for searching for a free function block number. Click New for adding a new function
block. Enter the required data and click Save.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

47

sip_trunking_04.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes using
Configure Common Gateway HG 3500

Step 2: Search for a free slot

Before entering LTU and SLOT number it is recommended to check if desired SLOT is free by
CM -> System Data -> Maintenance -> Board Maintenance.
After search is performed in Object list view free LTU and SLOT is marked with NOGEN/NPR/
UNACH under Status Overview column.

48

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_04.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes using
Configure Common Gateway HG 3500

Step 3: Open Board configuration menu in HiPath 4000 CM Assistant

CM -> System Data -> Board -> Board
Step 4: Add new board
Press New button in order to add new board
Step 5: Filling in the mask

Part Number: Q2316-X or Q2316-X10 or Q2324-X500 or Q2324-X510

Function ID: is always 1

Category: IPGW

Board Name: STMI2 or STMI4

CGW Function Block: enter created function block (see Step 1: Configure function block)

LTU and SLOT: select free slot (see Step 2: Search for a free slot)

Step 6: Open STMI2-IGW Board Data dialog and fill mandatory fields
Customer LAN IP Address and Subnet Mask.
Trunk Protocol: number of b-channels (e.g. SIP: 50 and H323: 50).
After all needed data is entered into required fields press Save button.
A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

49

sip_trunking_04.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes using
Delete IPGW

The board is now added and can be found in Board Dialog or in Board Maintenance.

4.2

Delete IPGW

To delete IPGW board do the following:

Step 1: Open Board configuration menu in HiPath 4000 CM Assistant

Step 2: Search for IPGW

Step 3: Select IPGW and delete it

Step 1: Open Board configuration menu in HiPath 4000 CM Assistant

CM -> System Data -> Board -> Board
Step 2: Search for IPGW
Search Criteria -> Category: IPGW
Step 3: Select IPGW and delete it
Choose the board that has to be deleted from the list and cklick Delete. After pressing Delete
button dialog appears that board is removed from system.

4.3

Modify Board Data of IPGW

In order to modify board data follow those steps:

Step 1: Open Board configuration menu in HiPath 4000 CM Assistant

Step 2: Select IPGW

Step 3: Carrying out desired changes

Step 4: Checking the changes

Step 1: Open Board configuration menu in HiPath 4000 CM Assistant

CM -> System Data -> Board -> Board
Step 2: Select IPGW
Select IPGW in Category list and press Search button.

50

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_04.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes using
Modify Board Data of IPGW

Step 3: Carrying out desired changes

Do the needed changes in board dialog (eg. IP address) and save changes with the Save button.
After changes are saved dialog about successful action pops up.
Step 4: Checking the changes
Make new board search in order to check if new data is accepted.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

51

sip_trunking_04.fm

Configuration example for SIP trunking between homogenous HiPath 4000 nodes using
Modify Board Data of IPGW

52

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_05.fm
SIP Trunking Between HiPath 2000/3000/5000 and HiPath 4000 Node
Device registration & call address resolution

SIP Trunking Between HiPath 2000/3000/5000 and

HiPath 4000 Node

5.1

Device registration & call address resolution

In the case of IP trunking, the SIP-Q trunk is statically configured for the HiPath 3000 in the
CAR component of the HG 1500 board via HiPath 3000 Administration Manager or WBM. For
the HiPath 4000, SIP trunking is statically configured in the system. SIP registration of the HG
1500 board at the Large Enterprise Gatekeeper (LEGK) is not supported.

Figure 5-1

5.2

>

SIP trunking between HiPath 3000/5000 and HiPath 4000

Trunking scenarios for HiPath 2000/3000/5000 and HiPath 4000

interworking

If DMC has been activated for an SIP-Q trunking path, Voice Activity Detection (VAD
in WMB) should also be activated. Otherwise the same bandwidth is required for the
master connection as for the slave connection!

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

53

sip_trunking_05.fm

SIP Trunking Between HiPath 2000/3000/5000 and HiPath 4000 Node

Trunking scenarios for HiPath 2000/3000/5000 and HiPath 4000 interworking

Figure 5-2

SIP trunking for HiPath 4000 and HiPath 3000 interworking

Figure 5-3

SIP trunking for HiPath 4000 and HiPath 3000/5000 interworking

54

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_05.fm

SIP Trunking Between HiPath 2000/3000/5000 and HiPath 4000 Node

Setup for HiPath 3000 and HiPath 4000 interworking

Administration tips:

IP trunking - Section , Configuration example for SIP trunking between homogenous

HiPath 4000 nodes

Trunking with 5000RSM:

The trunking protocol towards HiPath 4000 is selected in a new entry for external
administrative domains.

5.3

Setup for HiPath 3000 and HiPath 4000 interworking

Configuring HG 3500 (SIP/H323)

See Chapter 2, SIP trunking between homogenous HiPath 4000 nodes.

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

55

sip_trunking_05.fm

SIP Trunking Between HiPath 2000/3000/5000 and HiPath 4000 Node

Setup for HiPath 3000 and HiPath 4000 interworking

56

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunking_06.fm

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

57

sip_trunking_06.fm

58

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

sip_trunkingSIX.fm
Nur fr den internen Gebrauch

Index

Index

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual

59

sip_trunkingSIX.fm
Index

60

Nur fr den internen Gebrauch

A31003-H3140-S107-1-7620, 05.2007
HiPath 4000 V4, IP Solutions - IP and SIP Trunking, Service Manual