TDCSU protocols

[melhabba]

good morning all
we have Hipath4000 v5 connected to Mitel by E1 ( amo TDCSU ) But when we configure digital trunk ( E1 ) the connect propably one way from hipath4000 to mitel ( but connection mitel to hipath4000 ring only ) we use protocol etsi but when we change protocol to CORNV33 the connection lossed ( no connection between to sites ) and try to use the ETSI protocol again but the connection remain loss
how to solve this problem and what is relationship between protocols and AMO prode and what is deferent between PD , PVCD , DB table , HD table and and what is the relation between prode and tdcsu and how to configure prode to work tdcsu probably

and what is LWPAR parameter and what is relation between it to prode and tdcsu


DIS-TDCSU:1-4-25-1;
H500: AMO TDCSU STARTED
+------------------------ DIGITAL TRUNK (FORMAT=L) -------------------------+
| DEV = S2COD PEN = 1-04-025-1 TGRP = 26 |
|---------------------------------------------------------------------------|
| PROTVAR = ETSI INS = Y SRCHMODE = CIR |
| COTNO = 4 COPNO = 4 DPLN = 0 |
| ITR = 0 COS = 200 LCOSV = 2 |
| LCOSD = 1 CCT = TARZIBO DESTNO = 0 |
| SEGMENT = 1 DEDSCC = DEDSVC = NONE |
| FACILITY = DITIDX = SRTIDX = |
| TRTBL = GDTR SIDANI = N ATNTYP = CO |
| CBMATTR = NONE NWMUXTIM = 10 TCHARG = N |
| SUPPRESS = 0 DGTPR = CHIMAP = N |
| ISDNIP = ISDNNP = |
| PNPL2P = PNPL1P = PNPAC = |
| TRACOUNT = 31 SATCOUNT = MANY NNO = |
| ALARMNO = 2 FIDX = 1 CARRIER = 1 |
| ZONE = EMPTY COTX = 4 FWDX = 1 |
| DOMTYPE = DOMAINNO = TPROFNO = |
| INIGHT = CCHDL = |
| UUSCCX = 16 UUSCCY = 8 FNIDX = 1 |
| CLASSMRK = EC & G711 & G729AOPT SRCGRP = |
| TCCID = SECLEVEL = TRADITIO |
|---------------------------------------------------------------------------|
| BCNEG = N BCGR = 1 LWPAR = 5 |
| LWPP = 0 LWLT = 0 LWPS = 0 |
| LWR1 = 0 LWR2 = 0 |
| DMCALLWD = VNNO = |
| SVCDOM = |
| BCHAN = 1 && 30 |
| |
+---------------------------------------------------------------------------+
AMOUNT OF B-CHANNELS IN THIS DISPLAY-OUTPUT: 30



thank you too much

 

[LoPath]

I'm no "expert" but this should help!

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4 & V6, OpenScape Xpressions V7, OpenScape Contact Center V8, OpenScape Voice V9

 

[thepfy]

The prototcols need to match at both ends.
CornetV33 is DPNSS so is the Mitel using DPNSS on this connection?

For DPNSS one side is a master and the other a slave but this needs to be set in the config.
Master end should provide the clock for synchronisation, so should be the end which has the more stable clock.
Some systems can be cranky if they are not the clock provider.

 

[sbcsu]

Cornet - Corporate Net - is not DPNSS - it is for between Siemens's systems same as CORNV33
DPNSS signalling is the newer version of APNSS
Digital Private Network Signalling System.

To use DPNSS you will need a CDG module installed.
(cannot be installed on a remote shelf)

The protocol you need to interact now would be ETSI which is ECMA1 or ECMAV2 - try this out using the equipment you have

 

[melhabba]

THANK you all to reply

Now connection return to one way between hipath4000 v5 to Mitel ( and from mitel to hipath ring only )
we use ETSI PROTOCOL as parameter in TDCSU CAN YOU help me to configure probably in two sites, I try to use ECMA1 protocol and the result as same of ETSI and when use ECMAV2 protocol the link ( E1 ) is dropped
AND can explain me what is relation protocols to AMO prode


thank you

 

[LoPath]

The AMO PRODE can be used to copy, change, display and regenerate tables for the protocol
handler.
Use of this AMO requires well-founded specialized knowledge with respect to protocol
conversion. The protocol handler uses these tables to convert system-specific messages to
external signaling messages in accordance with the D-channel protocol (ISO layer 3, OSI
transport layer) and vice versa. Further details see in example of use ISDN Protocol Variants.
In the system database, the tables consist of general entries, which are used by all protocols,
and protocol-specific entries.
The protocols defined are linked to protocol variants.
When assigning a trunk circuit with the AMO TDCSU, the circuit is allocated one of these
protocol variants.
In addition to the protocol tables (general PRODE entries) the variant also determines the
implementation of the protocol (coding, error handling and interworking).
From SP300-V3.3 onward, the basic initialization of the PD tables is relocated from the
database to the HD itself. The following command is sufficient to initialize the memories for the
PD tables:
COPY-PRODE:PVCD,1;
The above command thus describes the database with the basic initialization data for the PD
tables, initializes the general entries and loads all associated PDs.
The protocol descriptor tables consist of a general section and the PD tables. This applies both
to the database (DB) and the hard disk (HD).
The general part is designated as a table of variants (VARTAB). The relationship between the
protocol descriptors (PD) and the protocol variants is defined in it.
The hard disk contains up to 40 versions of these tables of variants, each of which is assigned
to a country. On the HD the tables of variants are designated protocol variant combination
descriptors (PVCD).
The PVCDs and PDs on the hard disk can be interrogated by way of the following commands:
DISPLAY-PRODE:HD,PVCDSHRT;
DISPLAY-PRODE:HD,PDSHORT;
The PVCDs or PDs are numbered for HD access and are addressed by the PVCDNO or
PDNO.
To inquire the relationship between protocol variant and PD,
DISPLAY-PRODE:HD,PVCDLONG,<pvcdno>;
is used.
Note: the regenerated PRODE commands of a certain system version may not be transferred
to other (newer) versions due to incompatibiliy.
References to protocols stored on the hard disk:
+------+---------------------------+-------+---------------+
| PDNO | PDSTRING | IDENT | VERSION |
+------+---------------------------+-------+---------------+
| 1 | ECMA QSIG BC | H/08 | B0-EJ0.20.002 |
| 2 | SWISSNET 2 BC | H/08 | B0-EG0.10.001 |
| 3 | CORNET HICOM V2.2 / V2.3 | H/08 | B0-EL0.20.001 |
| 4 | CORNET-N 1.3f (IM) | H/08 | B0-EL0.20.004 |
| 5 | 1TR6 N0 REF-T (USER-SIDE) | H/40 | B0-EL0.20.001 |
| 6 | 1TR6 N1 REF-T (USER-SIDE) | H/41 | B0-EL0.20.001 |
| 7 | ANALOG | H/11 | B0-EL0.20.001 |
| 8 | FRANKREICH VN3 NUMERIS | H/08 | B0-EL0.10.001 |
| 9 | S0-BUS DSS1 ETS 300 403 ) | H/08 | B0-EJ0.20.001 |
| 10 | S0-BUS DKZN1 N0 | H/40 | B0-EL0.20.002 |
| 11 | S0-BUS 1TR6 N0 | H/40 | B0-EL0.20.001 |
| 12 | S0-BUS DKZN1 N1 | H/41 | B0-EL0.20.002 |
| 13 | S0-BUS 1TR6 N1 | H/41 | B0-EL0.20.001 |
| 14 | EURO-ISDN REF-T USER-SIDE | H/08 | B0-EJ0.20.004 |
| 15 | EXPO-92 SPANIEN JULIO, 89 | H/08 | B0-EG0.10.002 |
| 16 | PRE-EURO-ISDN FINNLAND | H/08 | B0-EG0.10.001 |
| 17 | PRE-EURO-ISDN PORTUGAL | H/08 | B0-EG0.10.001 |
| 18 | PRE-EURO-ISDN BELGIEN | H/08 | B0-EG0.10.001 |
| 19 | PRE-EURO-ISDN DAENEMARK | H/08 | B0-EG0.10.001 |
| 20 | 1TR6 N1 REF-Q (NET-SIDE) | H/41 | B0-EL0.20.001 |
| 21 | EURO-ISDN 1TR67 REF-T | H/08 | B0-EJ0.20.004 |
+------+---------------------------+-------+---------------+
| PDNO | PDSTRING | IDENT | VERSION |
+------+---------------------------+-------+---------------+
| 22 | EURO-ISDN OESTERREICH | H/08 | B0-EJ0.20.004 |
| 23 | FRANKREICH VN4 NUMERIS | H/08 | B0-EJ0.20.001 |
| 24 | NEDERLAND | H/08 | B0-EG0.10.001 |
| 25 | CHINA CSN-7 REF-T | H/08 | B0-EH0.10.006 |
| 26 | ENGLAND MCL-ISDN | H/08 | B0-EF0.30.004 |
| 27 | BASIC ACCESS T0 AUSTRALIA | H/08 | B0-EF0.30.002 |
| 28 | PRIM. ACCESS T2 AUSTRALIA | H/08 | B0-EF0.30.002 |
| 29 | ECMA QSIG SS | H/08 | B0-EL0.20.001 |
| 30 | SS7-ISUP REF-T USER-SIDE | H/08 | B0-EI0.20.001 |
| 31 | ETSI QSIG Third ed. SS | H/08 | B0-EL0.20.001 |
| 32 | ISO QSIG Second ed. SS | H/08 | B0-EL0.20.001 |
| 33 | EURO-ISDN REF-T NET-SIDE | H/08 | B0-EJ0.20.004 |
| 34 | NI-2 PRI (SR-4619) | H/08 | B0-EL0.20.009 |
| 35 | NI-2 PRI (SR-4619 (NET) | H/08 | B0-EL0.20.003 |
| 36 | NI-2 PRI MAINTENANCE | H/43 | B0-EL0.20.002 |
| 37 | AT&T 4ESS (TR41459) | H/08 | B0-EL0.20.005 |
| 38 | AT&T 4ESS (TR41459) MAINT | H/03 | B0-EL0.20.002 |
| 39 | MCI 014-0018-04.3D-ER | H/08 | B0-EL0.20.004 |
| 40 | CORNET-N 1.3f (US) | H/08 | B0-EL0.20.005 |
| 41 | S0-BUS NI-BRI GR-268-CORE | H/08 | B0-EL0.20.005 |
+------+---------------------------+-------+---------------+

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4 & V6, OpenScape Xpressions V7, OpenScape Contact Center V8, OpenScape Voice V9

 

[Moriendi]

ETSI is a central office protocol. If you use that protvar, you will lose private network features.

You should use a QSIG variant for connection to a private exchange, as sbcsu says, ECMA1, ECMA2, or also PSS1V2.

If you have speech path problems, check if the seized channel is >15. ETSI and ECMA1 work as per ETS 300 102, where the physical channel is used for the CHI in the messaging (1-15,17-31). ECMA2 (ETS 300 172) and PSS1V2 (ISO/IEC 11572) indicate the logical channel (1-30) not the physical.

This means that if you have two PBXs using the different implementations, above channel 15 they seize different physical channels for audio although the signalling is working fine. You will be able to hear the audio on two different channels if you put a tester on it.

So test again and make sure channel 1 is seized. If that works fine, this is the problem and either 4K or Mitel will need reconfiguring. You did say one way not no transmission, but still check it.

LWPAR controls the L2 parameters, master, slave, CRC4 etc. If the circuit comes in service, I would expect LWPAR to be correct.

PRODE is used to copy new protocols into the DB so that they are available for use in TDCSU, and to make minor adjustments to the implementation if required. You would not normally need to do anything in PRODE apart from make sure you are using the right COPY-PRODE to init the table correctly.