Hipath 4000 V2.0 Complex Solutions - Payload Switching DMC: Service Manual

HiPath 4000 V2.
0
Complex Solutions - Payload
Switching DMC
Service Manual
*1PA31003-H3121-K104-2-7620*
1P A31003-H3121-K104-2-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 de-
scribed 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.
The device conforms to the EU directive 1999/5/EG, as attested by the CE

mark.
This device has been manufactured in accordance with our certified envi-
ronmental management system (ISO 14001). This process ensures that
energy consumption and the use of primary raw materials are kept to a min-
imum, thus reducing waste production.
 Siemens AG 2004 ●
Information and Communication Networks,
Hofmannstraße 51, D-81359 München, Germany
Reference No.: A31003-H3121-K104-2-7620 Printed in the Federal Republic of Germany.
Subject to availability. Right of modification reserved.
payloadIVZ.fm
Nur für den internen Gebrauch Service Manual HiPath 4000 V2.0 - Payload Switching DMS -
Service Manual HiPath 4000 V2.0 - Payload Switching DMS

- Content 0
1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.4 Notes concerning Direct Media Connections DMC:. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.5 Bandwidth Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.6 Domain concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.7 DMC Interworking to HiPath 3000/5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
3 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 Devices supporting DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Features with DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.3 Feature activation while DMC is active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
4 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 DMC authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Maximum number of DMC connections on IP boards . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.1 Board with 60 DSP channels (2 DSPs onboard). . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.2 Board with 120 DSP channels (4 DSPs onboard). . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3 Voice Activity Detection (VAD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.4 Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.5 H.323 stack on IPDA boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
5 Relevant AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
A31003-H3121-K104-2-7620, October 2004

HiPath 4000 V2.0, Complex Solutions - Payload Switching DMC, Service Manual 0-1
payloadIVZ.fm
Service Manual HiPath 4000 V2.0 - Payload Switching DMS - ContentNur für den internen Ge-
A31003-H3121-K104-2-7620, October 2004

0-2 HiPath 4000 V2.0, Complex Solutions - Payload Switching DMC, Service Manual
payload_01.fm
Nur für den internen Gebrauch Feature Description
Overview
1 Feature Description
1.1 Overview
To support the Payload Switching feature, the Direct Media Connection DMC feature is used
for Voice over IP connections in HiPath 4000 V2.0.
Direct Media Connections DMC can be described and defined in the following way:
● The payload (voice channel) of a HiPath 4000 internal or networkwide voice connection will
be exchanged within a LAN in which a direct IP connection is possible without conversion
into a TDM data stream.
1.2 Features
By the use of the feature "DMC Any-to-any" payload data is transported within a HiPath 4000
network directly between the IP Endpoints without several IP-TDM conversions of the payload.
This direct payload connection is called Direct Media Connection (DMC).
1.3 Motivation
If two HFA IP phones are connected in a two-party call without the Direct Media Connection
DMC feature, a double IP/TDM conversion of the payload would be performed. This causes a
loss of quality of the voice transmission which results from the multiple conversion of the
payload between IP and TDM and vice versa (status of HiPath 4000 V1.0). To avoid this loss
of quality the IP payload is exchanged directly between the two subscribers if both are in a two
party connection. This example refers to HFA IP phones but the same situation applies also for
other IP endpoints.
IP Endpoints can be:
● HFA IP phones (e.g. optiPoint 400/600 V2.0, optiPoint 410, optiClients 130 > V2.5)
● IP Trunking Gateways (HG 3550 V2.0, HG1500)
● IPDA boards (HG3570 V2.0, HG 3575 V2.0)
The IP endpoints can be the real endpoints of the connection (i.e. there is a Master Connection
between two IP phones) or the IP endpoints are only endpoints of a section within the Master
Connection. E.g. an anate or digite may also profit from a DMC if it is connected to its partner
via IPDA Access Point or IP Trunking Gateway.
The setup of a call is done within several steps.
Steps 1 and 2 are the normal call setup procedures as known in HiPath 4000 V1.0. The result
is called Master Connection. The normal call setup procedure is extended by steps 3 and 4 to
build the optional Direct Media connection.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm
Feature Description Nur für den internen Gebrauch

Notes concerning Direct Media Connections DMC:
1. In a first step, a signaling connection between the users is established.

2. Parallel to that signaling connection a so called Master Connection (MC) for the payload is
established. The payload path of the Master Connection may be segmented into TDM and
IP paths:
● within a TDM network this is a specific B channel
● within an IP network, this is a RTP connection.
The RTP payload connection is established and controlled by H.323 procedures (in
particular by the use of the fast connect procedure).
3. After the Master Connection between the users is established and connected, i.e. both
users are in the talk state, a DMC connection between the IP endpoints of the Master
Connection can be established. The called IP endpoint initiates the setup of the DMC
connection.
4. When the DMC connection is established, the payload is transported using this H.323
connection. However, the Master Connection exists in parallel, but without conveying
payload as long as the DMC connection exists (the Master Connection is on a "stand-by"
mode).
If the talk-state is released (e.g. for the setup of a consultation call) the IP endpoint switchs
back immediately to the Master Connection and releases the DMC connection.
1.4 Notes concerning Direct Media Connections DMC:

● The Direct Media Connection will be switched only in the two-party call state, that means
in the basic call and the simple consultation call. A DMC will also be switched if the call
is set up via a feature like call forwarding or picking up a group call or if a secondary line
answers a keyset call.
● A DMC is not switched for conference calls.
For conferences the delay times can be reduced significantly by using a DAKS server
because the conference members are connected to the server by 2 party basic
connections.
● If the involved parties aren‘t in a two party connection the IP/TDM conversion and the
switching via the TDM switching network (MTS) is executed.
● If a Direct Media Connection is established the connection path via the MTS switching
network for multiple IP/TDM conversion (Master Connection) has to stay switched in
parallel to the direct IP connection so that immediately after termination of the two party
call state the MTS with its capabilities for tones and conferenceing is available for any
feature control by call processing.
● DMCs are established also for Fax/Modem connections.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm
Bandwidth Considerations
1.5 Bandwidth Considerations

While a DMC is active only SID frames (idle frames) are sent on the master connection.
Therefore this master connection needs only a reduced bandwidth.
The following tables show the currently needed bandwidth for the IP endpoints. The actual
values may change in the future.
● IP boards:
Bandwidth needed for DMC master connection in sleep mode:
Codec SID frames Payload Total bytes Bandwidth sleep vs.

per second bytes (bps) active (%)
G.711 10 1 71 5680 6.9
G.729AB 10 2 72 5760 16
G.723 11.11 4 74 6578 26
For comparison: bandwidth needed for active connection:
Codec frames per Payload Total bytes Bandwidth

second bytes (bps)
G.711 33.33 240 310 82667
G.729AB 50 20 90 36000
G.723 33.33 24 94 25067
● IP phones:
Bandwidth needed for DMC master connection in sleep mode:
Codec SID frames Payload Total bytes Bandwidth

per second bytes (bps)
G.711 1.00 1 60 480
G.729AB 1.01 4 60 485
G.723 1.00 2 60 480
The following scenarios are being considered:
Scenario A:
Direct Media Connection DMC within a single HiPath 4000 node.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm

A31003-H3121-K104-2-7620, October 2004

payload_01.fm
Scenario B:
Direct Media Connection DMC between HFA IP phones within a HiPath 4000 network.
This scenario B is supported in HiPath 4000 in conjunction with the IP Gateway HG 3550 V2.0.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm

Scenario C:
Direct Media Connections DMC between HFA IP phone and IPDA shelf within a single HiPath
4000 node.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm
Scenario D:
Direct Media Connections DMC between netwide IPDA-shelves.
DMC in mixed scenarios

In mixed scenarios the DMC is executed in the 2 party call state between the first possible IP
address at the A-side (IP phone or HG 3575 or HG 3570 or HG 3550) and the last possible IP
address at the B-side (i.e. again HG 3550 or HG 3570 or HG 3575 or IP phone).
A31003-H3121-K104-2-7620, October 2004

payload_01.fm

Domain concept
1.6 Domain concept

In very large enterprise networks it may be necessary to subdivide the network into several
socalled domains. Depending on the configuration DMC connections may be allowed only
within these domains or end-to-end over several domains.
Example 1: DMC possible from domain A until domain B:

Note: for this scenario no special configuration is needed (default)
A31003-H3121-K104-2-7620, October 2004

payload_01.fm
DMC Interworking to HiPath 3000/5000
Example 2: DMC not possible from domain A to domain B, DMC only possible within
domains A and B:
In this case both ends of the link between the domains have to be marked as domain end.
This is done with an attribute within LCR (see chapter Generation). This attribute has to be set
in domain I for the LCR route leading to domain II, and in domain II for the LCR route leading
to domain I.
1.7 DMC Interworking to HiPath 3000/5000

Supported scenarios:
● Scenario 1: HG 3550 terminates the HiPath 3000 payload switching
● Scenario 2: HG 1500 terminates HiPath 4000 Direct-Media-Connection
● Scenario 3: Direct-Media-Connection between HFA IP phones end-to-end
● Scenario 4: HiPath 4000 as transit node between two HiPath 3000/5000 nodes
A31003-H3121-K104-2-7620, October 2004

payload_01.fm

Scenario 1
This scenario applies to two cases:
– the endpoint in the HiPath 4000 network is a TDM device or
– DMC interworking between HiPath 4000 and HiPath 3000/5000 is not allowed (this
scenario can be achieved by setting the LCR domain end attribute in the HiPath 4000
for the route leading to the HiPath 3000/5000 network).
In the first case the end-to-end connection consists of a TDM connection on the HiPath 4000
side and an IP connection between the HG 3550 and the IP endpoint on the HiPath 3000/5000
side.
In the second case the connection between the endpoint in the HiPath 4000 network and the
endpoint in the HiPath 3000/5000 network consists of
● a DMC part in the HiPath 4000 network and
● Payload Switching (PLS) in the HiPath 3000/5000 network, i.e. the PLS is terminated by
the HG 3550 on the HiPath 4000 side.
This second case is shown in the following picture:
● DMC within HiPath 4000 network:

From the 1st possible A-side IP adress to 1st possible B-side IP adress. Signaling of A- and
B-IP address takes place via CorNet-NQ (SETUP/CONNECT-messages)
● PLS (Payload Switching) within HiPath 3000/5000 network:
The IP-Gateway HG3550 serves as Payload Switching HFA Proxy of HiPath 3000/5000.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm
Scenario 2
DMC to HG1500 in HiPath 3000/5000
When interworking between HiPath 4000 and HiPath3000/5000 is allowed and the endpoint in
the HiPath 3000/5000 network is a TDM device the HG1500 terminates the DMC.
RTP stream between the HiPath 3000/5000 HG1500 and the HiPath 4000 HG3550 belongs to
the master-connection.
Scenario 3
DMC to HFA Phone in HiPath 3000/5000
When interworking between HiPath 4000 and HiPath3000/5000 is allowed and the endpoint in
the HiPath 3000/5000 network is a HFA phone a DMC can be established end-to-end.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm

RTP stream between the HiPath 3000/5000 HFA phone and HG3550 belongs to the master-
connection.
Scenario 4
HiPath 4000 (network) as transit node between two HiPath 3000/5000 nodes
In this case, no end-to-end DMC connection can be set up between the HiPath 3000 IP devices
(IP phones or HG1500). On the A side, a DMC is established to the most distant HiPath 4000
DMC endpoint (HG3550, HG3570 or HG3575). This DMC overlies a HiPath 3000 PLS
connection (not depicted in the figure) and the IP parts of the HiPath 4000 network.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm
If the HiPath 4000 network has no IP parts, the DMC connection is omitted and the payload is
transmitted on the PLS connection. This applies if, instead of a HiPath network or an IPDA
configuration, an individual HiPath 4000 connected on both sides with HiPath 3000 systems or
networks is involved. So a DMC connection on the A side only exists if an optimization is
necessary.
On the B side, a payload switching connection is established.
So it always involves a connection with 2 IP hops.
A31003-H3121-K104-2-7620, October 2004

payload_01.fm

A31003-H3121-K104-2-7620, October 2004

payload_02.fm
Nur für den internen Gebrauch User Interface
2 User Interface
n.a.
A31003-H3121-K104-2-7620, October 2004

payload_02.fm
User Interface Nur für den internen Gebrauch
A31003-H3121-K104-2-7620, October 2004

payload_03.fm
Nur für den internen Gebrauch Service Information
Devices supporting DMC
3 Service Information
3.1 Devices supporting DMC

The DMC feature is supported starting with the switch software HiPath 4000 V2.0 by the follow-
ing IP devices:
● Phone/client:
IP Phone types and DMC DMC support
optiPoint IP adapter -
optiPoint 400 V1.0 -
optiClient 130 V2.5 -
optiPoint 400 V2.0 on HG 3530 V2.0 +
optiPoint 600 V2.0 on HG 3530 V2.0 +
optiClient 130 > V2.5 on HG 3530 V2.0 +
optiPoint 410 (spirit) on HG 3530 V2.0 +
IP AC-Win -
● Boards:
DMC is supported with the Hardware version V2.0 of the respective boards HG3550/ HG3570
and HG3575.
DMC connections with an IPDA board or IP trunking gateway as originating or terminating end-
point will exist, if the endpoint of the basic connection at the IPDA shelf is an Anate, a Digite
(optiSet E, optiPoint 500), a CMI Cordless phone or an analog or digital trunk, but not for atten-
dant console.
3.2 Features with DMC

The following list shows for which features a DMC is established:
● Basic call
● Basic call with reroute internal
● Basic call with rerouting (NW)
● Consultation call (including toggle, end of consultation (back to held party))
● Transfer talking with or without Path Replacement
A31003-H3121-K104-2-7620, October 2004

payload_03.fm
Service Information Nur für den internen Gebrauch

Feature activation while DMC is active
● Transfer ringing with or without Path Replacement

● Immediate recall
● Centralized attendant transfer
● CFU, CFNR with forwardswitching or with rerouting or mixed (rerouting in transit switch)
● Call back (message waiting, busy, no reply)
● Pickup of a call in a pickup group
● Directed call pickup
● Call to Hunt group
● Application establishes call (ACL make call)
● ACD call
● Reduction of conference to 2-party call
● Call to Keyset (secondary line answers the call)
● executive/secretary (CHESE) (secretary answers the call)
3.3 Feature activation while DMC is active

When a DMC is active for a two party call and a feature is being activated the DMC is released
and the call is switched back to the master connection.
This applies for features that are activated by one of the involved parties and also for features
activated by a third party (e.g. campon, override).
When the feature is finished and the call returns to the normal two party talk state the DMC is
not reactivated except for the features that are listed in the chapter above.
Feature response in exception situations:

● DTMF Handling
A DMC is released if the endpoint requests the sending of DTMF via SIU (signalling unit).
E.g. a HFA phone requests the sending of DTMF via access code.
● DTMF transmission over DMC
DTMF tones are recognized in DMCs and transmitted, e.g. if the tone is received by the
HiPath system at a CO interface or a DTMF enabled anate sends DTMF by itself.
A31003-H3121-K104-2-7620, October 2004

payload_04.fm
Nur für den internen Gebrauch Generation
DMC authorization
4 Generation
4.1 DMC authorization

Possible IP endpoints have to be allowed to switch a DMC.This is done with the following AMO
commands:
● IP phones:
CHANGE-SDAT:STNO=<extension number>,TYPE=ATTRIBUT,AATTR=DMCALLWD;
● NCUI:
CHANGE-STMIB:MTYPE=NCUI2,LTU=xx,TYPE=DMCDATA,DMCALLWD=YES;
● STMI pool for IPDA:
CHANGE-SIPCO:TYPE=DMCDATA,DMCALLWD=YES;
● IP trunking:
CHANGE-TDCSU:PEN=<ltg-ltu-slot-cct),DEV=HG3550IP,DMCALLWD=Y;
4.2 Maximum number of DMC connections on IP boards

Depending on the number of DSPs on a given type of IP board a certain number of DSP chan-
nels is available.
For a board with two DSPs these are 60 channels, for a board with 4 DSPs 120 channels.
The following table shows the IP board types and the number of DSPs:
board type Q number variant HW ID number of number of

DSPs DSP
channels
STMI:
STMI2 Q2316 X 4EXH 2 60
STMI2 Q2316 X10 4FXH 4 120
NCUI:
NCUI2 Q2305 X5 54XH 2 60
NCUI2 Q2305 X10 43XH 4 120
Without DMC the number of DSP channels directly corresponds to the number of possible con-
nections.
A31003-H3121-K104-2-7620, October 2004

payload_04.fm
Generation Nur für den internen Gebrauch

Maximum number of DMC connections on IP boards
When a DMC is established a connection consists of the DMC slave connection and the corre-
sponding master connection. The payload is sent on the DMC slave connection. The master
connection is put into a socalled „sleep mode“ where it needs only a reduced bandwidth. Three
master connections in „sleep mode“ can share the same DSP channel.
Therefore the maximum number of connections on an IP board is the number of DSP channels
minus the number of DSP channels needed for the master connections in „sleep mode“.
This means that on a board with 60 DSP channels only a maximum of 45 connections with
DMC can be established, on a board with 120 DSP channels only 90 connections with DMC.
Since this reduction of the maximum number of connections may not be acceptable at the cus-
tomer site the number of allowed DMC connections has to be configured per IP board. When
this limit is reached no further DMC connections can be established.
This way it is possible to guarantee a minimum number of possible connections. Minimum num-
ber means that more connections without DMC are possible when the DMC resources are not
fully used.
The following tables show for each number of allowed DMC connections
– the minimum number of possible additional master connections without DMC and
– the overall maximum number of connections, consisting of the number of allowed DMC
connections plus the number of additional master connections without DMC when all
DMC resources are used.
Remark 1: Of course the number of allowed master connections for HG3550 is limited by the
number of configured trunks. For each trunk, a maximum of 30 master connections can be
made.
Remark 2: If a HG3550 is operated in mixed mode with IP trunking and WAML, the WAML com-
ponent uses no DSP resources.
4.2.1 Board with 60 DSP channels (2 DSPs onboard)
number of allowed number of overall maximum number of

DMC connections possible additional connections
non-DMC connections
0 60 60
1 58 59
2 57 59
3 56 59
4 54 58
5 53 58
A31003-H3121-K104-2-7620, October 2004

payload_04.fm

non-DMC connections
6 52 58
7 50 57
8 49 57
9 48 57
10 46 56
11 45 56
12 44 56
13 42 55
14 41 55
15 40 55
16 38 54
17 37 54
18 36 54
19 34 53
20 33 53
21 32 53
22 30 52
23 29 52
24 28 52
25 26 51
26 25 51
27 24 51
28 22 50
29 21 50
30 20 50
31 18 49
32 17 49
33 16 49
34 14 48
35 13 48
A31003-H3121-K104-2-7620, October 2004

payload_04.fm


non-DMC connections
36 12 48
37 10 47
38 9 47
39 8 47
40 6 46
41 5 46
42 4 46
43 2 45
44 1 45
45 0 45
4.2.2 Board with 120 DSP channels (4 DSPs onboard)

non-DMC connections
0 120 120
1 118 119
2 117 119
3 116 119
4 114 118
5 113 118
6 112 118
7 110 117
8 109 117
9 108 117
10 106 116
11 105 116
12 104 116
13 102 115
14 101 115
A31003-H3121-K104-2-7620, October 2004

payload_04.fm

non-DMC connections
15 100 115
16 98 114
17 97 114
18 96 114
19 94 113
20 93 113
21 92 113
22 90 112
23 89 112
24 88 112
25 86 111
26 85 111
27 84 111
28 82 110
29 81 110
30 80 110
31 78 109
32 77 109
33 76 109
34 74 108
35 73 108
36 72 108
37 70 107
38 69 107
39 68 107
40 66 106
41 65 106
42 64 106
43 62 105
44 61 105
A31003-H3121-K104-2-7620, October 2004

payload_04.fm


non-DMC connections
45 60 105
46 58 104
47 57 104
48 56 104
49 54 103
50 53 103
51 52 103
52 50 102
53 49 102
54 48 102
55 46 101
56 45 101
57 44 101
58 42 100
59 41 100
60 40 100
61 38 99
62 37 99
63 36 99
64 34 98
65 33 98
66 32 98
67 30 97
68 29 97
79 28 97
70 26 96
71 25 96
72 24 96
73 22 95
74 21 95
A31003-H3121-K104-2-7620, October 2004

payload_04.fm

non-DMC connections
75 20 95
76 18 94
77 17 94
78 16 94
79 14 93
80 13 93
81 12 93
82 10 92
83 9 92
84 8 92
85 6 91
86 5 91
87 4 91
88 2 90
89 1 90
90 0 90
AMO commands:
● NCUI:
CHANGE-STMIB:MTYPE=NCUI2,LTU=xx,TYPE=DMCDATA,DMCCONN=<number of allowed
DMC connections>;
● STMI pool for IPDA:
CHANGE-STMIB:MTYPE=STMI2,LTU=xx,TYPE=DMCDATA,DMCCONN=<number of allowed
DMC connections>;
● IP trunking:
CHANGE-STMIB:MTYPE=STMI2IGW,LTU=xx,TYPE=DMCDATA,DMCCONN=<number of
allowed DMC connections>;
A31003-H3121-K104-2-7620, October 2004

payload_04.fm

Voice Activity Detection (VAD)
4.3 Voice Activity Detection (VAD)

In order to save bandwidth Voice Activity Detection (VAD) has to be activated for IP connec-
tions. When a DMC is established and VAD is set only idle frames are sent on the master con-
nection.
VAD is activated with the following AMO commands:
● Station:
CHANGE-SDAT:STNO=<ext. number>,TYPE=DATA1,CLASSMRK=VAD&EC&G711&G729OPT;
● Digital trunks:
CHANGE-TDCSU:PEN=<ltg-ltu-slot-cct),CLASSMRK=VAD&EC&G711&G729OPT;
● Analog trunks:
CHANGE-TACSU:PEN=<ltg-ltu-slot-cct),CLASSMRK=VAD&EC&G711&G729OPT;
● IP trunking:
VAD has to be activated on the board with the board configuration tool.
● HFA: VAD must be activated at both ends of the HFA master connection.
For IP phones (where available), that can be done in the IP phone’s configuration menu.
For HG3530:
CHANGE-HFAB:MTYPE=STMIHFA2,LTU=x,SLOT=xx,TYPE=DSP,VADEN=YES;
4.4 Domains
It may be necessary to subdivide a very large enterprise network into several areas (domains)
where DMC is only possible within a domain and not between domains.
In order to achieve this an LCR mark has to be set at each domain end. When this mark is set
DMCs are not established beyond this point.
AMO command:
CHANGE-LDAT:LROUTE=<route number>,LATTR=<existing attributes>&DMCEND;
4.5 H.323 stack on IPDA boards

The H.323 stack on IPDA boards has to be configured using the following AMO commands:
● NCUI:
CHANGE-STMIB:MTYPE=NCUI2,TYPE=H323,Q931T1=<number>,Q931T2=<number>,
GWNAME=<string>;
A31003-H3121-K104-2-7620, October 2004

payload_04.fm
H.323 stack on IPDA boards
● STMI:
CHANGE-STMIB:MTYPE=STMI2,TYPE=H323,Q931T1=<number>,Q931T2=<number>,
GWNAME=<string>;
For the correct numerical values please refer to the configuration manual for IPDA boards.
In addition, the codecs used for the DMC must be configured (Master Connection codecs see
SDAT/TACSU/TDCSU).
● NCUI:
CHANGE-STMIB:MTYPE=NCUI2,LTU=xx,TYPE=ASC,CODECLST=G729&G711;
● STMI:
CHANGE-STMIB:MTYPE=STMI2,LTU=xx,SLOT=xx,TYPE=ASC,CODECLST=G729&G711;
A31003-H3121-K104-2-7620, October 2004

payload_04.fm

H.323 stack on IPDA boards
A31003-H3121-K104-2-7620, October 2004

payload_05.fm
Nur für den internen Gebrauch Relevant AMOs
5 Relevant AMOs
AMO Parameter Sprache/ Beschreibung/ Description

Language
HFAB VADEN d VAD erlaubt,Wert = JA/NEIN
VADEN e VAD enabled, value = YES/NO
EMERK & d Teilnehmermerkmal,
SDAT AMERK neuer Wert: DMCERL = DMC erlaubt
AATTR & e subscriber attribute,
DATTR new value: DMCALLWD = DMC allowed
CLASSMRK d Classmark, Wert VAD = Voice Activity Detection
CLASSMRK e Classmark, value VAD = Voice Activity Detection
SIPCO TYP d Datentyp (Verzweigungsparameter),
neuer Wert: DMCDATA
TYPE e type of data (branching parameter),
new value: DMCDATA
DMCERL d DMC erlaubt, Wert = JA/NEIN
DMCALLWD e DMC allowed, value = YES/NO
A31003-H3121-K104-2-7620, October 2004

payload_05.fm
Relevant AMOs Nur für den internen Gebrauch

Language
STMIB MTYP d Baugruppentyp (Verzweigungsparameter),
Wert = NCUI2/STMI2/STMI2IGW
MTYPE e board type (branching parameter),
value = NCUI2/STMI2/STMI2IGW
TYP d Datentyp (Verzweigungsparameter),
Wert = DMCDATA/H323/ASC
TYPE e type of data (branching parameter),
value = DMCDATA/H323/ASC
DMCERL d DMC erlaubt, Wert = JA/NEIN
DMCALLWD e DMC allowed, value = YES/NO
DMCCONN d Anzahl der DMC Verbindungen (numerisch)
DMCCONN e number of DMC connections (numerical)
Q931T1 d Q931 Timer 1 (numerisch)
Q931T1 e Q931 timer 1 (numerical)
Q931T2 d Q931 Timer 1 (numerisch)
Q931T2 e Q931 timer 1 (numerical)
GWNAME d Gateway Name (max. 16 Zeichen)
GWNAME e gateway name (max. 16 char.)
CODECLST d Codecliste für DMC, in der Reihenfolge der abnehmen-
den Preferenz:
Wert: einer oder mehrere von: G711, G729
CODECLST e list of codecs for DMC in order of decreasing preference:
value: one or more of :G711&G729
LDAT LATTR d LCR Attribut,
neuer Wert: DMCENDE = Ende der DMC Domaine
LATTR e LCR attribute,
new value: DMCEND = end of DMC domain
TDCSU GER d Gerät (Verzweigungsparameter), Wert = HG3550IP
DEV e device (branching parameter), value = HG3550IP
DMCERL d DMC erlaubt, Wert = J/N
DMCALLWD e DMC allowed, value = Y/N
CLASSMRK d Classmarks für IP Verbindungen, Wert = VAD
CLASSMRK e classmarks for IP connections, value = VAD
A31003-H3121-K104-2-7620, October 2004

payload_05.fm
Nur für den internen Gebrauch Relevant AMOs

Language
TACSU CLASSMRK d Classmarks für IP Verbindungen, Wert = VAD
CLASSMRK e classmarks for IP connections, value = VAD
A31003-H3121-K104-2-7620, October 2004

payload_05.fm
Relevant AMOs Nur für den internen Gebrauch
A31003-H3121-K104-2-7620, October 2004

payload_hoc.fm
Nur für den internen Gebrauch
A31003-H3121-K104-2-7620, October 2004

HiPath 4000 V2.0, Complex Solutions - Payload Switching DMC, Service Manual -1
payload_hoc.fm
Nur für den internen Gebrauch
A31003-H3121-K104-2-7620, October 2004

-2 HiPath 4000 V2.0, Complex Solutions - Payload Switching DMC, Service Manual
payloadSIX.fm
Nur für den internen Gebrauch Index
Index Z
P
Payload - Devices supporting DMC 3-1
Payload - DMC authorization 4-1
Payload - Domains 4-8
Payload - Feature activation while DMC is ac-
tive 3-2
Payload - Feature Description 1-1
Payload - Features with DMC 3-1
Payload - Generation 4-1
Payload - H.323 stack on IPDA boards 4-8
Payload - Maximum number of DMC connec-
tions on IP boards 4-1
Payload - Relevant AMOs 5-1
Payload - Service Information 3-1
Payload - User Interface 2-1
Payload - Voice Activity Detection (VAD) 4-8
A31003-H3121-K104-2-7620, October 2004

HiPath 4000 V2.0, Complex Solutions - Payload Switching DMC, Service Manual Z-1
payloadSIX.fm
Index Nur für den internen Gebrauch
A31003-H3121-K104-2-7620, October 2004

Z-2 HiPath 4000 V2.0, Complex Solutions - Payload Switching DMC, Service Manual

Hipath 4000 V2.0 Complex Solutions - Payload Switching DMC: Service Manual

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

Hipath 4000 V2.0 Complex Solutions - Payload Switching DMC: Service Manual

Uploaded by

Copyright:

Available Formats

HiPath 4000 V2.

The information provided in this document contains merely general descriptions or

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

Service Manual HiPath 4000 V2.0 - Payload Switching DMS

1 Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

A31003-H3121-K104-2-7620, October 2004

A31003-H3121-K104-2-7620, October 2004

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

1. In a first step, a signaling connection between the users is established.

1.4 Notes concerning Direct Media Connections DMC:

A31003-H3121-K104-2-7620, October 2004

1.5 Bandwidth Considerations

Codec SID frames Payload Total bytes Bandwidth sleep vs.

Codec frames per Payload Total bytes Bandwidth

Codec SID frames Payload Total bytes Bandwidth

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

A31003-H3121-K104-2-7620, October 2004

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

A31003-H3121-K104-2-7620, October 2004

DMC in mixed scenarios

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

1.6 Domain concept

Example 1: DMC possible from domain A until domain B:

A31003-H3121-K104-2-7620, October 2004

1.7 DMC Interworking to HiPath 3000/5000

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

● DMC within HiPath 4000 network:

A31003-H3121-K104-2-7620, October 2004

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

A31003-H3121-K104-2-7620, October 2004

A31003-H3121-K104-2-7620, October 2004

Feature Description Nur für den internen Gebrauch

A31003-H3121-K104-2-7620, October 2004

A31003-H3121-K104-2-7620, October 2004

User Interface Nur für den internen Gebrauch

A31003-H3121-K104-2-7620, October 2004

3.1 Devices supporting DMC

3.2 Features with DMC

A31003-H3121-K104-2-7620, October 2004

Service Information Nur für den internen Gebrauch

● Transfer ringing with or without Path Replacement

3.3 Feature activation while DMC is active

Feature response in exception situations:

A31003-H3121-K104-2-7620, October 2004

4.1 DMC authorization

4.2 Maximum number of DMC connections on IP boards

board type Q number variant HW ID number of number of

A31003-H3121-K104-2-7620, October 2004

Generation Nur für den internen Gebrauch

4.2.1 Board with 60 DSP channels (2 DSPs onboard)

number of allowed number of overall maximum number of

A31003-H3121-K104-2-7620, October 2004

number of allowed number of overall maximum number of

A31003-H3121-K104-2-7620, October 2004

Generation Nur für den internen Gebrauch

number of allowed number of overall maximum number of

4.2.2 Board with 120 DSP channels (4 DSPs onboard)