PREFACE

This manual is valid for SOPHO Call@Net (previously known as SSW 810), running on all
ISPBX models of the SOPHO iS3000 Series. All of these systems will further be referred to as
"ISPBX".

LICENSING AGREEMENT

The licensing agreement for an ISPBX determines which facilities are available. It is therefore
possible that a facility described here will not work, even though it has been correctly
configured. Check the relevant license agreement to determine what is available.

GENERAL NOTE

The facility IMP Networking (formerly called : Fully Integrated Network) is only supported by
the iS3070/iS3090!

NOTICE TO THE USER

Unless stated otherwise (in text and figures), the term :

- ALC-G represents the ALC-G, ALC-GP or ALC-G(R).

- DTX-I represents the DTX-I or DTX-I(R).
- PMC represents the PMC-HR, PMC-MC or PMC-G :
- PMC-HR represents the PMC-HR or PMC-G (with NCC-HR).
- PMC-MC represents the PMC-MC or PMC-G (with or without NCC-MC).

1
 1. ANALOGUE TRUNK TRAFFIC

Difference is made here in the direction of the route and whether DDI is required. The version
of an ATU differs per country, also the signalling groups are usually different per country. Refer
to the Signalling Data Manual for more details.

Examples of commonly used ATUs are :

DDO : ATU-SS (*) Subscriber Signalling

ATU-PD Polarity Detection
ATU-EC Earth calling

DDI : ATU-AS (*) ALS70 signalling

ATU-PD Polarity detection
ATU-ST Special Type

DDO and DDI : ATU-ST (*) Special Type

ATU-LD Loop detection
ATU-AS ALS70 signalling
ATU-EM Ear & Mouth signalling

The ATUs marked with (*) are used as examples on the following pages.

PROCEDURE: HOW TO PROGRAM ANALOGUE ROUTES TO THE PSTN

(ATU-SS DDO)

Preconditions

In the following OM Commands (Italic) the next configuration is assumed :

ISPBX DDO
PSTN
Route 0
2xxx

Actions

1. Assign the ATU-SS.

See the Signalling Data Manual for more details about signalling groups and board types.

2
 ASBRDS : <shelf>,<board>,<board-type>,<sig-group>[,[<hw-type>];
ASBRDS : 1012,14,23,3E04,35;
2. Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1012,14;
3. Project the Trunk Access Code (TAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 0,0,2,21,0;
ASINTN : 1,0,2,21,0;
ASINTN : 2,0,2,21,0;
4. Project the PSTN destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 0,60,10,0;
5. Analyse the numbers after the Trunk Access Code in the outgoing analysis tree :
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
ASEXTN : 60,0,2,4,12,0;
;
6. Create a new route 0.
CRROUT : <route>{,<unit>];
CRROUT : 0;
7. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 0[,,,<unit>];
0,1,3;
;
8. Change the route characteristics as required :
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 0,0111110000000,543444;
CHRTCO : 0,001100,0;
9. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]000,1,1100010000000000,11;
10. Assign the bundle to the PSTN route :

3
 ASBNDL : <route>,<bundle>;
ASBNDL : 0,0;
11. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
ASLINE : 5,1000,1012,14,0;
ASLINE : 5,1001,1012,14,1;
ASLINE : 5,1002,1012,14,2;
ASLINE : 5,1003,1012,14,3;
ASLINE : 5,1004,1012,14,4;
ASLINE : 5,1005,1012,14,5;
12. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
SETINS : 1012,14,0&&5;
Testing

Dial a trunk access code.

PROCEDURE: HOW TO PROGRAM ANALOGUE ROUTES TO THE PSTN

(ATU-AS DDI)

Preconditions

In the following OM Commands (Italic) the next configuration is assumed :

ISPBX
DDI
PSTN
Route 0
2xxx

Actions

1. Assign the ATU-AS.

See the Signalling Data Manual for more details about signalling groups and board types.
ASBRDS : <shelf>,<board>,<board-type>,<sig-group>,<hw-type>;
ASBRDS : 1012,14,22,3304,35;
2. Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1012,14;
3. Create a route :
CRROUT : <route>[,<unit>];

4
 CRROUT : 0[,<unit>];
4. Change the route characteristics as required :
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCG : 0,0111110000000,543444;
CHRTCI : 0,10100001000,010699999,30;
5. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]000,0,1100010000100000,315;
6. Assign the bundle to the PSTN route :
ASBNDL : <route>,<bundle>;
ASBNDL : 0,0;
7. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
ASLINE : 5,1000,1012,14,0;
ASLINE : 5,1001,1012,14,1;
ASLINE : 5,1002,1012,14,2;
ASLINE : 5,1003,1012,14,3;
8. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
SETINS : 1012,14,0&&5;
9. Project the proper result-id's in the incoming tree :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 30,20,3,4,10;
Testing

Make a call from the PSTN.

PROCEDURE: HOW TO PROGRAM ANALOGUE ROUTES TO THE PSTN

(ATU-ST DDI+DDO)

Preconditions

In the following OM Commands (Italic) the next configuration is assumed :

5
 ISPBX
PSTN
Route 0
2xxx

Actions

1. Assign the ATU-ST.

See the Signalling Data Manual for more details about signalling groups and board types.
ASBRDS : <shelf>,<board>,<board-type>,<sig-group>;
ASBRDS : 1012,14,22,3904;
2. Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1012,14;
3. Project the Trunk Access Code (TAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 0,0,2,21,0;
ASINTN : 1,0,2,21,0;
ASINTN : 2,0,2,21,0;
4. Project the PSTN destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 0,60,10,0;
5. Analyse the numbers after the Trunk Access Code in the outgoing analysis tree :
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
ASEXTN : 60,0,2,4,12,0;
;
6. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 0[,<unit>];
7. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 0[,,,<unit>];
0,1,3;

6
 ;
8. Change the route characteristics as required) :
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 0,0111110000000,543444;
CHRTCI : 0,10100001000,010699999,30;
CHRTCO : 0,001100,0;
9. Program the incoming number analysis :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
Additional parameters : <route-table>;
ASBLCK : 30,2,0,4,10;
10. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]000,2,1100010000100000,11;
11. Assign the bundle to the PSTN route :
ASBNDL : <route>,<bundle>;
ASBNDL : 0,0;
12. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
ASLINE : 5,1000,1012,14,0;
ASLINE : 5,1001,1012,14,1;
ASLINE : 5,1002,1012,14,2;
ASLINE : 5,1003,1012,14,3;
13. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
SETINS : 1012,14,0&&3;
Testing

Dial a trunk access code.

7
 2. DIGITAL TRUNK TRAFFIC

2.1. DIGITAL EXCHANGE LINES

2.1.1. DASS2

PROCEDURE: How to program DASS2.

Preconditions

• Check if your system has a license for DPNSS :

DILICS : ;
• Check if the hardware you use has the right firmware (DTU-PH or DTU-PR).
• Check the DIP-switches and/or straps on the boards.

In the following OM Commands (Italic) the next configuration is assumed :

ISPBX
DASS2
PSTN
Route 5
2xxx

Figure 2-1 Example DASS2 Configurarion

Actions

1. Assign the hardware. Possible are :

30B+D : DTU-PH
30B+D : DTU-PU + IPH-A/B
30B+D : DTU-PR + IPH-A/B (used in following example)
See the tables in the 'More Information' part or see the Signalling Data Manual for more
details about signalling groups and board types.
ASBRDS : <shelf>,<board>,<board-type>,<sig-group>;
Assign the DTU-PR in a unit group and the IPH in the first position of the next unit group.
ASBRDS : 1011,1,25,2608;
ASBRDS : 1011,5,31,2508;

8
2. Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1011,1;
SETINS : 1011,5;
3. Project the DASS2 destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 14,60,10,4;
4. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 14[,<unit>];
5. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 14[,,,<unit>];
14,1,3;
;
6. Change the route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 14,0111010000000,553335;
Assign a data BSPT to the route and set the incoming DDI-fail options for data and voice/
possibly voice respectively :
ASBSPR : 14,96;
CHRTCI : 14,10100001000,000602311,30,,96;
CHRTCI : 14,10101101000,000622292,30;
CHRTCO : 14,001000,0;
7. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]14,2,01000100010000,310;
8. Assign the bundle to the DASS2 route :
ASBNDL : <route>,<bundle>;
ASBNDL : 14,14;
9. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
The EHWA in the ASLINE command refers to the DTU-PR
ASLINE : 14,1101,1011,1,0;

9
 ASLINE : 14,1101,1011,1,1;
ASLINE : 14,1102,1011,1,2;
ASLINE : 14,1103,1011,1,3;
ASLINE : 14,1104,1011,1,4;
ASLINE : 14,1105,1011,1,5;
ASLINE : 14,1106,1011,1,6;
ASLINE : 14,1107,1011,1,7;
ASLINE : 14,1108,1011,1,8;
etc.
10. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
On the DTU-PR/PU set also circuit 16 in service.
SETINS : 1011,1,1&&31;
SETINS : 1011,5,0;
11. Project the Trunk Access Code (TAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 0,9,3,21,14;
ASINTN : 1,9,3,21,14;
ASINTN : 2,9,3,21,14;
12. Analyse the number after the Trunk Access Code in the outgoing analysis tree :
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
Additional parameter : [<route-table>];
ASEXTN : 60,0,2,4,12,0;
;
;
13. Program the incoming DASS2 number analysis :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 30,2,0,4,10;
14. Connect a coax cable from the DTU/DTX to the CRU if this is the first digital link to the
PSTN. In case of a DTU-BA or DTX-I the trunk line must be on the first circuit. Assign a
CRU entry by means of :
ASCRUE : <shelf>,<board>,<circuit>;
Set this circuit in service
SETINS : <shelf>,<board>,<circuit>;
The hardware address in these commands refers to the following :
- iS3010/30/50 without CSN-BC : circuit 20/21 of PMC-MC master
- iS3010/30/50 with CSN-BC : circuit 20/21 of CSN-BC
- iS3070 with CPS-A : circuit 0...9 on the CRU board

10
 - iS3070 with CPS-4M : circuit 0/1 on the CSGs
- iS3070/90 CSM : circuit 48/49 on the SNSs
ASCRUE : 1012,7,20;
SETINS : 1012,7,20;

2.1.2. Euro-ISDN (ETSI)

PROCEDURE: HOW TO PROGRAM ETSI

Preconditions

• Check if your system has a license for ISDN trunks :

DILICS : ;
• Check if the hardware you use has the right firmware (DTU-PH or DTU-BA) or that the
right download package is available (DTX-I). In case of a DTX-I used as a DTU-BA the
board must be downloaded first.
• Check the DIP-switches and/or straps on the boards.

In the following OM Commands (Italic) the next configuration is assumed :

ISPBX Integrated
ETSI Services
Digital
Route 0 Network
2xxx

Figure 2-2 Example ETSI Configurarion

Actions

1. Assign the hardware. Possible are :

30B+D : DTU-PH
2B+D : DTU-BA or DTX-I(7) or DTX-I(15)
2. See the tables in the 'More Information' part or see the Signalling Data Manual for more
details about signalling groups and board types.
ASBRDS : <shelf>,<board>,<board-type>,<sig-group>;
ASBRDS : 1012,1,18,5D0D;
or in case of an already assigned DTX-I with combi protocol.
DEPCTB : <shelf>,<board>,<circuit>;
ASPCTB : <shelf>,<board>,<circuit>,<pct-type>,<sig-group>;

11
 3. In case of a DTX-I with downloadable signalling group check the package relation and set
it if necessary.
DIPACK : <shelf>,<board>;
INSTPK : <new-pack>;
DIPACK : 1012,1;
Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1012,1;
4. Project the ETSI destination and the related outgoing number analysis tree and route-
table:
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 0,60,10,0;
5. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 0[,<unit>];
6. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 0[,,,<unit>];
0,1,3;
;
7. Change the route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 0,0111110000000,543444;
CHRTCI : 0,10100001000,010699999,30;
CHRTCO : 0,001100,0;
8. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]000,22,1100010000100000,315;
9. Assign the bundle to the ETSI route :
ASBNDL : <route>,<bundle>;
ASBNDL : 0,0;
10. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
The EHWA in the ASLINE command refers to the following :
30B+D on DTU-PH : circuit 0

12
 2B+D on DTX-I : circuit 2 and/or 4 or ...
2B+D on DTU-BA : circuit 0/1 or 2/3 or ...
ASLINE : 0,1000,1012,1,2;
ASLINE : 0,1001,1012,1,3;
11. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
On the DTU-PR/PU/PH set also circuit 16 in service.
SETINS : 1012,1,2;
SETINS : 1012,1,3;
12. Project the Trunk Access Code (TAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 0,0,2,21,0;
ASINTN : 1,0,2,21,0;
ASINTN : 2,0,2,21,0;
13. Analyse the number after the Trunk Access Code in the outgoing analysis tree :
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
ASEXTN : 60,0,2,4,12,0;
;
14. Program the incoming ETSI number analysis :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 30,2,0,4,10;
15. Connect a coax cable from the DTU/DTX to the CRU if this is the first digital link to the
PSTN. In case of a DTU-BA or DTX-I the trunk line must be on the first circuit.
Assign a CRU entry by means of :
ASCRUE : <shelf>,<board>,<circuit>;
Set this circuit in service
SETINS : <shelf>,<board>,<circuit>;
The hardware address in these commands refers to the following :
- iS3010/30/50 without CSN-BC : Circuit 20/21 of PMC-MC master
- iS3010/30/50 with CSN-BC : Circuit 20/21 of CSN-BC
- iS3070 with CPS-A : Circuit 0...9 on the CRU board
- iS3070 with CPS-4M : Circuit 0/1 on the CSGs
- iS3070/90 CSM : Circuit 48/49 on the SNSs
ASCRUE : 1012,7,20;
SETINS : 1012,7,20;
16. Use the Second Line OM command CHPMFU to program the CNI (Complete Number
Identification).

13
 CHPMFU : 1;
First or second place: 1 (= first)
ISDN protocol types: 1 (= ETSI or QSIG)
BR-MN-PBI : 21
PR-MN-PBI : 22
Type Of Number : 2 (= national)
Trunk Access Code : 0
International Prefix : 00
National Prefix : 0
Own Country Code : 31 (= Netherlands)
Own Area Code : 35 (= Hilversum)
Own Local Prefix : 689 (= Philips)

Alternatively program this using QSIG/ISDN Addressing (since Call@Net 2.6).

Testing

Dial an ETSI trunk access code

Additional Information

Signalling Groups and PSIs

SG HW L2 REMARKS
5D08 DTU-PH User Netherlands, PSI = 31H
5D09 DTU-PH User Belgium, PSI = 33H
5D0A DTU-PH User Switzerland, PSI = 37H
5D0B DTU-PH User Germany, PSI = 67H
5D0C DTU-PH User Italy, PSI = 35H
5D0D DTU-PH User Free numbers, PSI = 6BH
5D0E DTU-PH User PSI = 6DH

Table 2-1 ETSI Signalling groups for DTU-PH

14
SG HW L1 L2 Remarks
5C0D DTX-I15 TE User Netherlands, PSI = 30H
5C0E DTX-I15 TE User Belgium, PSI = 32H
5C0F DTX-I15 TE User Switzerland, PSI = 36H
5C10 DTX-I15 TE User Germany, PSI = 66H
5C11 DTX-I15 TE User Italy, PSI = 34H
5C12 DTX-I15 TE User Free numbers, PSI = 6AH
5C13 DTX-I15 TE User PSI = 6CH

Table 2-2 ETSI Signalling Groups for DTX-I

2.2. DIGITAL TIE LINES

2.2.1. DPNSS

PROCEDURE: HOW TO PROGRAM DPNSS

Preconditions

• Check if your system has a license for DPNSS

DILICS : ;
• Check if the hardware you use has the right firmware (DTU-PH or DTU-BA) or that the
right download package is available (DTX-I or DTU-VC). In case of a DTX-I used as a
DTU-BA the board must be downloaded first.
• Check the DIP-switches and/or straps on the boards.

In the following OM Commands (Italic) the next configuration is assumed :

ISPBX ISPBX
A DPNSS B
Route 5
20xx 30xx

Figure 2-3 Example DPNSS Configuration

Actions

15
 DPNSS Projecting for ISPBX A

1. Assign the hardware. Possible are :

Type Of DPNSS Required Hardware

30B+D : DTU-PR+IPH-A+IPH-B or
DTU-PU+IPH-A+IPH-B or
DTU-PH
2B+D : DTU-BA or
DTX-I(7) or
DTX-I(15)
3B+D : DTU-VC with TRK-VC
2. See the Signalling Data Manual for more details about signalling groups and board types.
ASBRDS : <shelf>,<board>,<board-type>,<sig-group>;
ASBRDS : 1012,9,26,660C;
or in case of an already assigned DTX-I with combi protocol.
DEPCTB : <shelf>,<board>,<circuit>;
ASPCTB : <shelf>,<board>,<circuit>,<pct-type>,<sig-group>;
In case of a DTX-I or DTU-VC with downloadable signalling group check the package
relation and set it if necessary.
DIPACK : <shelf>,<board>;
INSTPK : <new-pack>;
DIPACK : 1012,9;
3. Assign the D-Channel
ASBRVC : <shelf>,<board>,<circuits>,<shelf>,<board>{,<nvct>];
ASBRVC : 1012,9,2&3,1012,9;
4. Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1012,9;
5. Fill in the Cluster-Id of your system (optional for a closed numbering scheme) :
CHCLID : <cluster-id>;
Note that in a closed numbering scheme this must be the same as the first digit(s) of the
DNRs in your system. To determine if your system is programmed for a closed numbering
scheme execute :
DIMDAT : 1,40[,<unit>];
If the answer is YES, you have a closed numbering scheme.
CHCLID : 2;if the DNRs in your system are 2xxx.
6. Project the DPNSS destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-

16
 rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 5,65,00,5;
7. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 5[,<unit>];
8. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 5[,,,<unit>];
5,1,3;
;
9. Change the route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
Do not set option S (traffic class) in the parameter <tone-and-ddi-opts>too low!
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 5,0010000000000,222111;
CHRTCI : 5,10000000000,000599999,35;
CHRTCO : 5,000000,0;
10. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]005,2,0000000000000000,46;
Parameter CON-AND-SIG-TYPE should be set at 47 in the opposite ISPBX.
11. Assign the bundle to the DPNSS route :
ASBNDL : <route>,<bundle>;
ASBNDL : 5,5;
12. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
The EHWA in the ASLINE command refers to the following :
- 30B+D on DTU-PR/PU/PH : circuit 1...15 and 17...31
- 2B+D on DTX-I : circuit 2/3 or 4/5 or ...
- 2B+D on DTX-I : circuit 0/1 or 2/3 or ...
- 3B+D on DTU-VC : circuit 2...4 or 6...8 or 10...12
ASLINE : 5,1000,1012,9,2;
ASLINE : 5,1001,1012,9,3;
13. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
On the DTU-PR/PU/PH set also circuit 16 in service.
SETINS : 1012,9,2;

17
 SETINS : 1012,9,3;
14. Project the Network Access Code (NAC) in the tree for initial extension/enquiry/
operator/alternative destination dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
This network access code (nac) must be the same as the cluster-id of the other ISPBX.
ASINTN : 0,3,3,91,5;
ASINTN : 1,3,3,91,5;
ASINTN : 2,3,3,91,5;
ASINTN : 5,3,3,91,5;
if the DNRs in the opposite ISPBX have the format 30xx.
Analyse the number after the Network Access Code in the outgoing analysis tree as an
internal number :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 65,0,3,3,10;
if the DNRs in the opposite ISPBX have the format 30xx and there is a CLOSED
numbering scheme (ASBLCK : 65,3,3,4,10; for an open numbering scheme).
15. Program the incoming DPNSS number analysis :
For a closed numbering scheme it is possible to do a one-step analysis, i.e. to project the
complete internal DNR (result-id 10) in the incoming tree :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
For an open numbering scheme or if centralized operator on the basis of the cluster-id is
used a two-step analysis is required, this two-step analysis also works for a closed
numbering scheme :
Step 1 :
Analyse the incoming cluster-identity :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
Note that the <dest/number>must be a dummy destination : a destination number not
yet used in the system.
Step 2 :
Analyse the remaining incoming digits :
CHDSTC : <dest>,<tree>,00,0;
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASINTN : 35,2,3,91,19;
CHDSTC : 19,19,00,0;
ASBLCK : 19,0,3,3,10;
(ASBLCK : 19,2,3,4,10; for an open numbering scheme).
16. Connect a coax cable from the DTU/DTX to the CRU in the system that must be
synchronised (usually the B side). In case of a DTU-BA or DTX-I the trunk line must be on
the first circuit.

18
 Assign a CRU entry by means of :
ASCRUE : <shelf>,<board>,<circuit>;
Set this circuit in service
SETINS : <shelf>,<board>,<circuit>;
The hardware address in these commands refers to the following :
- iS3010/30/50 without CSN-BC : circuit 20/21 of PMC-MC master.
- iS3010/30/50 with CSN-BC : circuit 20/21 of CSN-BC.
- iS3070 old HW : circuit 0...9 on the CRU board.
- iS3070 redesign HW : circuit 0/1 on the CSGs.
- iS3070/90 CSM : circuit 48/49 on the SNSs.
ASCRUE : 12,7,20;
SETINS : 12,7,20;
Testing

Dial a Network-DNR.

SG HARDWARE L2 SAT. REMARKS

6704 DTU-PR/PU - No Mode depends on IPH
6705 DTU-PR/PU A No Use 2504 or 2505 for IPH
6706 DTU-PR/PU B No Use 2504 or 2505 for IPH
2504 IPH-B A - IPH-B one Unit Group after DTU
2505 IPH-B A - IPH-B two Unit Groups after DTU
2506 IPH-B B - IPH-B one Unit Group after DTU
2507 IPH-B B - IPH-B two Unit Groups after DTU

Table 2-3 DPNSS Signalling Groups for DTU-PR/PU and IPH

19
 DTU-PR DTU-PR
DTU-PU DTU-PU

L2: DPNSS-A L2: DPNSS-B

Figure 2-4 DPNSS Tie Line

SG HARDWARE L2 SAT. REMARKS

6704 DTU-PH A No CRC4
6705 DTU-PH B No CRC4
6706 DTU-PH A Yes CRC4
6707 DTU-PH B Yes CRC4
670A DTU-PH A Yes C-bit Brasil
670B DTU-PH B Yes C-bit Brasil

Table 2-4 DPNSS Signalling Groups for DTU-PH

DTU-PH DTU-PH

L2: DPNSS-A L2: DPNSS-B

Figure 2-5 DPNSS Tie Line

20
SG HARDWARE L1 L2 SAT. REMARKS
6604 all TE A No No download, no combi protocol
6605 all TE B No No download, no combi protocol
6606 all NT A No No download, no combi protocol
6607 all NT B No No download, no combi protocol
6608 all TE A Yes No download, no combi protocol
6609 all TE B Yes No download, no combi protocol
660A all NT A Yes No download, no combi protocol
660B all NT B Yes No download, no combi protocol
660C DTX-I7/DTU-VC TE A No
660D DTX-I7/DTU-VC TE B No
660E DTX-I15 TE A No
660F DTX-I15 TE B No
6610 all NT A No No download, no combi protocol
6611 all NT B No No download, no combi protocol
6612 DTX-I15 TE A No
6613 DTX-I15 TE B No

Table 2-5 DPNSS Signalling Groups for DTX-I, DTU-BA and DTU-VC

21
 Note: All stands for DTU-BA and DTX-I7 /15 used like a DTU-BA
In case of SG660C/660D used on a DTU-VC the L1 data is not used.

DTU-BA Tie Line (direct) DTU-BA

DTX-I DTX-I

L1: NT L1: TE
L2: DPNSS-A L2: DPNSS-B

Figure 2-6 Basic Rate DPNSS Tie Line (direct)

Tie Line (leased line)

Integrated
DTU-BA Services DTU-BA
DTX-I Digital DTX-I
Network

L1: TE L1: TE
L2: DPNSS-A L2: DPNSS-B

Figure 2-7 Basic Rate DPNSS Tie line (leased line)

2.2.2. DPNSS with Free Numbers

PROCEDURE: HOW TO CHANGE TO DPNSS WITH FREE NUMBERS

Preconditions

• Build either a DPNSS or PVN connection.

22
 Check if your system has a license for Free Numbers
DILICS : ;
• Check if LOSYSOP 106 (Free Numbering Active) is TRUE (= 1) :
DIMDAT : 1,106,1;
If necessary change it with :
CHOPTI : 106,1,1;
• Check if the size of the Free Numbering Table is not equal to zero :
DIMDAT : 0,307,1;
Note that this is not a save boundary. It can only be changed by re-projecting the system
• Check if your system is set up for a closed network (NESYSOP 040):
DIMDAT : 1,40,1;
If necessary change it with :
CHOPTI : 40,1,1;
Actions

DPNSS Projecting for ISPBX A

1. Adapt the Cluster-Id of your system

CHCLID : <cluster-id>;
CHCLID : 6111;
Note that the cluster identity must be disjunct (different) to the DNRs in your ISPBXs.
In this example it is assumed, that ISPBX-B has 6112 as the cluster Identity.
2. Fill in the free number table.
CHFDNR : <fdnr>,<fn-loc>;
If 2001 is an extension number in ISPBX B, fill in the DNR and the Network Access Code
to ISPBX B.
CHFDNR : 2001,6112;
Note that the DNRs on the opposite ISPBX must be analysed as internal numbers in your
own ISPBX. So, if you have DNR 7000 in ISPBX B, you must do OM Command :
ASBLCK : 0,7,1,4,10;to identify it as an internal DNR.
3. Delete the old Network Access Code (NAC) in the tree for initial extension/enquiry/
operator/alternative destination dialling :
MAKENU : <tree>,<number>;
MAKENU : 0,3;
MAKENU : 1,3;
MAKENU : 2,3;
MAKENU : 5,3;
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
This network access code (nac) must be the same as the cluster-id of the other ISPBX.
ASINTN : 0,6112,3,91,5;

23
 ASINTN : 1,6112,3,91,5;
ASINTN : 2,6112,3,91,5;
ASINTN : 5,6112,3,91,5;
The outgoing tree of destination 5 may be empty
4. Program the incoming number analysis by validating the internal DNRs.
ASBLCK : 30,2,1,4,10;
Testing

Dial a Free DNR.

2.2.3. Loop-back Connection with DTU-VC

The loop-back channel of the DTU-VC is used to compress the channels on an existing digital
tie line. Each tie line channel can then be used to transfer the 64 kbps channel(s) which
contains 3 compressed voice channels.

The connection between two loop-back channel in opposite system can be a B-channel in a :

• 30B+D line of a DTU-CA/PU;

• 30B+D line of a DTU-PH (DPNSS/DASS/ETSI/1TR6/QSIG);
• 2B+D line of a DTX-I/DTU-BA (DPNSS/ETSI/1TR6/QSIG);
• a combination of B-channels mentioned above.

Example DPNSS Configuration

DPNSS
ISPBX ISPBX
Route 5
A B
20xx DTU-VC 30xx
Route 20

Figure 2-8 Example DPNSS Configuration

PROCEDURE: HOW TO PROGRAM A LOOP-BACK CONNECTION

WITH DTU-VC

Preconditions

• Check if your system has a license for DPNSS

DILICS : ;
Actions

24
1. The projecting of the board is similar to the TRK-VC connection.
ASBRDS : <shelf>,<brd>,<board-type>sig-group>,<hw-type>;
ASBRDS : 1011,3,17,660C,255;
First delete circuit 5, 9, 13, 14 and 15 using DEPCTB.
DEPCTB : <shelf>,<brd>,<crt>;
DEPCTB : 1011,3,5&9&13;
DEPCTB : 1011,3,14&15;
Assign the loop-back channel (circuit 5, 9, 13) using OM command ASPCTB, using PCT-
TYPE 1 (LCT) and signalling group 6614 (passive side) or signalling group 6615 (active
side). The active side builds up the hotline relation, the passive side is the receiver of the
hotline. Hardware type is 255 (no test).
ASPCTB : <shelf>,<brd>,<crt>,<pct-type>,<sig-group>,<hw-type>;
ASPCTB : 1011,3, 5&9&13,1,6615,255;
2. Check the download package relation for the DTU-VC.
DIPACK : <shelf>,<brd>;
DIPACK : 1011,3;
Download the software to the board (if necessary).
INSTPK : <new-pack>;
INSTPK : F5xxxx;
3. Set the board and the circuits to INS
SETINS : <shelf>,<brd>,<crt>;
SETINS : 1011,3;
SETINS : 1011,3,2&3&4;
4. Program a new (DPNSS) route
CRROUT : <route>,<unit>;
CRROUT : 20,1;
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCG : 20,0010010000000,222555;
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>,<tree>,<a-queue>,<bspt>;
CHRTCI : 20,10100000000,001600000,71;
CHRTCO : <route>,<out-opts>,<atf>,<bspt>;
CHRTCO : 20,001100;
5. Program a new bundle :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : 1020,2,0000000000000000,417;
ASBNDL : <route>,<bundle>;
ASBNDL : 20,20;
6. Program new lines. Lines are circuits 2/3/4, 6/7/8 and 10/11/12 of the DTU-VC.
ASLINE : <bundle>,<line>,<shelf>,<brd>,<crt>,<b-channel>;
ASLINE : 20,9000,1011,3,2;

25
 ASLINE : 20,9000,1011,3,3;
ASLINE : 20,9000,1011,3,4;
7. Add the route number in the routing table of the fixed DPNSS connection :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
CHROTA : 20,,,1;
20,1,2;
5,0,2;
8. Because the relation between the DTU-VC loop-back channel of the opposite DTU-VC
is made using the hot line function the loop-back channels must be projected as extensions
(CHDNRC on circuit 5, 9 and 13).
CHDNRC : <bsp-id>,<shelf>,<brd>,<crt>;
CHDNRC : 2500,1011,3,5;
9. Set the hot line connection from the DNR of the loop-back channel of the active side (2500
in ISPBX A) to the DNR of the loop-back channel of the passive side (3500 in ISPBX B).
This hot line relation may include network access codes and/or trunk access codes. Note
that for each loop-back channel the corresponding loop-back channel has to be given
(circuit 5 to circuit 5, circuit 9 to circuit 9 and circuit 13 to circuit 13). It must be prevented
that the hot line connection chooses a compressed channel of a DTU-VC line which is
already in service. It is possible to choose a channel of the DTX-I.
CHHOTL : <orig-bsp-id>,<dest-number>,<delay>,<post-dial>,<trfc>;
CHHOTL : 2500,3500,0,0,6;
10. Block the bundle for non-voice traffic. Create a BSPT containing all types of traffic you
don't want on the bundle :
CRBSPT : <bspt>;
CRBSPT : 20;
IBSC : 0; (64 kBit/unrestricted)
IBSC : 2; (3.1 kHz audio)
IBSC : 3; (3.1 kHz audio non-ISDN, when used for analogue modems/faxes)
IBSC : 4; (7 kHz audio)
IBSC : 5; (Teletex)
IBSC : 6; (Telefax4)
IBSC : 7; (Mixed mode)
IBSC : 8; (Videotex)
IBSC : 9; (Slow can television)
IBSC : 10;(Fernwirken)
IBSC : 11; (GrafikTelefon)
IBSC : 12; (Bildschirmtext)
IBSC : 13; (Bildtelefon Bild)
IBSC : 15; (SOPHO ISPBX modem data)
IBSC : 16; (X.21)
IBSC : 17; (X.25)

26
 IBSC : 19; (64 kBit/unrestricted non-ISDN)
Assign this BSPT to the bundle :
ASBSPB : <unit+bundle>,<bspt>;
ASBSPB : 1020,20;
And set the number of allowed calls for this BSPT to zero :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : 1020,2,0000000000000000,417,0,20;

Note: More than 4 DTU-VC boards (2 hops) in a network is not advisable because of the increase
in delay time.
Equipment which introduce delay should not use voice compression, because the added
delay time of the DTU-VC could interfere with the echo cancellation circuit in the
equipment (e.g. DECT).
The DTU-VC can handle the following IBSCs :
- 1 : speech
- 3 : 3.1 kHz audio non-ISDN (when used for speech)
- 14 : ISPBX speech
- 18 : Bildtelefon Ton (when used for a fax/modem call from an S0bus)
- 19 : 64 kbps unrestricted non-ISDN (used for digital line with analogue signalling, e.g.
DTU-CA. The actual service profile of the call is unknown. It can only be handled by the
DTU-VC in case of a voice call).

2.2.4. QSIG

Since Call@Net 2.4 one should use the following signalling groups for 'real' QSIG :

- signalling group 5C20 for QSIG Basic Rate User side;

- signalling group 5C21 for QSIG Basic Rate Network side;
- signalling group 5D20 for QSIG Primary Rate User side;
- signalling group 5D21 for QSIG Primary Rate Network side.

In SSW 805 and up to SSW 810.23 use signalling groups 5D0F, 5D10, 5C14, 5C15 and 5C16
for QSIG (ISDN method, no Supplementary Services possible). Do not mix the ISDN method
and 'real' QSIG method in one connection.

27
 QSIG BOARD SIDE SIG GROUP CON-AND-
METHOD SIG-TYPE
ISDN method: DTU-PH User side 5D0F 414 (415)
NO Network side 5D10 415 (414)
Supplementary
Services DTX-I User side 5C14 414 (415)
possible Network side 5C15 415 (414)
(direct)
Network side 5C16 415 (414)
(via public)
QSIG method: DTU-PH User side 5D20 420 (421)
Supplementary Network side 5D21 421 (420)
Services
possible DTX-I User side 5C20 420 (421)
Network side 5C21 421 (420)

Table 2-6 Board Type and CON-AND-SIG-TYPE for QSIG

PROCEDURE: HOW TO PROGRAM QSIG

Preconditions

• Check if your system has a license for ISDN trunks :

DILICS : ;
• Check if the hardware you use has the right firmware (DTU-PH) or that the right
download package is available (DTX-I).
• Check the DIP-switches and/or straps on the boards.
Actions

In the following OM Commands (Italic) the next configuration is assumed :

ISPBX ISPBX
A B

20xx 30xx

Figure 2-9 Example of a QSIG link

1. Assign the hardware. Possible are :
30B+D : DTU-PH

28
 2B+D : DTX-I(15)
ASBRDS : <shelf>,<board>,<board-type>,<sig-group>;
(<sig-group>for the DTU-PH is 5D20 (User side) or 5D21 (Network side))
ASBRDS : 1012,1,18,5D20;
Or in case of an already assigned DTX-I with combi protocol.
DEPCTB : <shelf>,<board>,<circuit>;
ASPCTB : <shelf>,<board>,<circuit>,<pct-type>,<sig-group>;
2. In case of a DTX-I with downloadable signalling group check the package relation and set
it if necessary.
DIPACK : <shelf>,<board>;
INSTPK : <new-pack>;
DIPACK : 1012,1;
3. Set the projected board(s) in service.
SETINS : <shelf>,<board>;
SETINS : 1012,1;
4. Project the QSIG destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 1,61,10,1;
5. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 1[,<unit>];
6. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 1[,,,<unit>];
1,1,1;
;
7. Change the route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 1,0111110000000,543444;
CHRTCI : 1,10100001000,010699999,31;
CHRTCO : 1,001100,0;
8. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]001,22,1100010000100000,421;

29
 9. Assign the bundle to the QSIG route :
ASBNDL : <route>,<bundle>;
ASBNDL : 1,1;
10. Assign the lines to the bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
The EHWA in the ASLINE command refers to the following :
30B+D on DTU-PH : circuit 0
2B+D on DTX-I : circuit 2 or 4 or ...
ASLINE : 1,1000,1012,1,0;
11. Set the hardware addresses of the lines in service.
SETINS : <shelf>,<board>,<circuit>;
SETINS : 1012,1,0;
12. Project the Trunk Access Code (TAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 0,1,2,21,1;
ASINTN : 1,1,2,21,1;
ASINTN : 2,1,2,21,1;
13. Analyse the number after the Trunk Access Code in the outgoing analysis tree :
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
ASEXTN : 61,3,2,4,12,0;
;
14. Program the incoming QSIG number analysis :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 31,2,0,4,10;
15. Connect a coax cable from the DTU/DTX to the CRU if this is the first digital link to the
PSTN. In case of a DTU-BA or DTX-I the trunk line must be on the first circuit.
16. Assign a CRU entry by means of :
ASCRUE : <shelf>,<board>,<circuit>;
Set this circuit in service.
SETINS : <shelf>,<board>,<circuit>;
The hardware address in these commands refers to the following :
- iS3010/30/50 without CSN-BC : circuit 20/21 of PMC-MC master.
- iS3010/30/50 with CSN-BC : circuit 20/21 of CSN-BC.
- iS3070 old HW : circuit 0...9 on the CRU board
- iS3070 redesign HW : circuit 0/1 on the CSGs.
- iS3070/90 CSM : circuit 48/49 on the SNSs.
ASCRUE : 1012,7,20;
SETINS : 1012,7,20;

30
17. Use the Second Line OM command CHPMFU to program the CNI (Complete Number
Identification).

CHPMFU : 1;
First or second place: 2 (= second)
ISDN protocol types: 1 (= ETSI or QSIG)
BR-MN-PBI : 33
PR-MN-PBI : 34
Type Of Number : 4 (= transparent or not applicable)
Trunk Access Code : 1
International Prefix : -
National Prefix : -
Own Country Code : -
Own Area Code : -
Own Local Prefix : -

Alternatively program this using QSIG/ISDN Addressing (since Call@Net 2.6).

Testing

Dial the trunk access code for the QSIG route.

Additional Information

SG HW L2 Sat. Remarks
5D0F DTU-PH U No PSI = 61H
5D10 DTU-PH N No PSI = 63H

Table 2-7 QSIG (phase 0) Signalling Groups for DTU-PH

SG HW L2 Sat. Remarks
5D20 DTU-PH U No PSI = 4DH
5D21 DTU-PH N No PSI = 4FH

Table 2-8 Real QSIG Signalling Groups for DTU-PH

31
 DTU-PH DTU-PH

L2: U L2: N

Figure 2-10 QSIG Primary Rate Configuration

SG HW L1 L2 Remarks
5C14 DTX-I15 TE U Download, Combi protocol, PSI = 60H
5C15 DTX-I15 NT N Download, Combi protocol, PSI = 62H
5C16 DTX-I15 TE N Download, Combi protocol, PSI = 64H

Table 2-9 QSIG (phase 0) Signalling Groups for DTX-I

SG HW L1 L2 Remarks
5C20 DTX-I15 TE U Download, Combi protocol, PSI = 4CH
5C21 DTX-I15 NT N Download, Combi protocol, PSI = 4EH

Table 2-10 Real QSIG Signalling Groups for DTX-I

32
 Tie Line (direct)
DTX-I DTX-I

L1: TE L1: TE
L2: U L2: N

Tie Line (leased line)

Integrated
DTX-I Services DTX-I
Digital
Network

L1: TE L1: TE
L2: U L2: N

Figure 2-11 QSIG Basic Rate Configurations

33
 psi spare L123 Prot. br/pr Remarks PBI values
mp md mn mt
4C 1C UUU real br 0B 01 33 -
QSIG
4D 1D UUU real pr 03 03 34 -
QSIG
4E 1E NNN real br 04 10 35 -
QSIG
4F 1F NNN real pr 02 02 36 -
QSIG
60 70 UUU QSIG br 0B 01 16 -
61 71 UUU QSIG br 03 03 17 -
62 72 NNN QSIG br Direct link 04 10 18 -
63 73 NNN QSIG br 02 02 19 -
64 74 NNN QSIG br via public ISDN 0B 10 18 -
6E 7E UUU QSIG br (sig flow) 0B 01 08 -
6F 7F NNN QSIG br direct link (sig flow) 04 10 09 -

Table 2-11 QSIG PSIs and Corresponding Parameter Blocks

2.3. PRIVATE VIRTUAL NETWORKING (PVN)

2.3.1. PVN As Primary Route

PROCEDURE: HOW TO PROGRAM PVN MODE 0 (PRIMARY ROUTE)

Preconditions

• Check if your system has licenses for DPNSS and PVN :

DILICS : ;
• Check if your system contains at least one PMC.

In the following OM Commands (Italic) the next configuration is assumed :

34
 PSTN

035-689 030-234

ISPBX
ISPBX
Virtual Route 5
A B
20xx 30xx

Figure 2-12 PVN Primary Route Example

Actions

Projecting for ISPBX A.

1. Fill in the Cluster-Id of your system :

CHCLID : <cluster-id>;
Note that in a closed numbering scheme this must be the same as the first digit(s) of the
DNRs in your system. To determine if your system is programmed for a closed numbering
scheme execute :
DIMDAT : 1,40[,<unit>];
If the answer is YES, you have a closed numbering scheme.
CHCLID : 2;
if the DNRs in your system are 2xxx.
2. Project the Network Access Code (NAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
This Network Access Code (NAC) must be the same as the cluster-id of the other ISPBX.
ASINTN : 0,3,3,91,5;
ASINTN : 1,3,3,91,5;
ASINTN : 2,3,3,91,5;
if the DNRs in the opposite ISPBX have the format 30xx.
3. Project the DPNSS destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 5,65,00,5;
4. Analyse the number after the Network Access Code in the outgoing analysis tree as an

35
 internal number :
OPEN numbering scheme : Complete DNR
CLOSED numbering scheme : DNR - NAC
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 65,0,3,3,10;
If the DNRs in the opposite ISPBX have the format 30xx and there is a CLOSED
numbering scheme.
5. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 5[,<unit>];
6. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 5[,,,<unit>]; 5,1,3;
7. Change the route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
Do not set option S (traffic class) in the parameter <tone-and-ddi-opts>too low!
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 5,0010001000000,222111;
CHRTCI : 5,10000000000,000599999,35;
CHRTCO : 5,000000,0;
8. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]005,2,0000000000000000,516;
9. Assign the bundle to the DPNSS route :
ASBNDL : <route>,<bundle>;
ASBNDL : 5,5;
10. Program the incoming DPNSS number analysis :
For a closed numbering scheme it is possible to do a one-step analysis, i.e. to project the
complete internal DNR (result-id 10) in the incoming tree :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
For an open numbering scheme or if centralized operator on the basis of the cluster-id
must be used a two-step analysis is required, this two-step analysis also works for a closed
numbering scheme :
Step 1 :
Analyse the incoming cluster-identity :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];

36
 Note that the <dest/number>must be a dummy destination : a destination number not
yet used in the system.
Step 2 :
Analyse the remaining incoming digits :
CHDSTC : <dest>,<tree>,00,0;
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASINTN : 35,2,3,91,19;
CHDSTC : 19,19,00,0;
ASBLCK : 19,0,3,3,10;
11. Assign the Hatch and set it in service :
ASPCTB : <shelf>,<brd>,<crt>s/r,<pct-type>,<sig-group>;
ASPCTB : [uu]011,17,12,16,6104;
12. Set up the PVN characteristics of the DPNSS route. The Route Identification Number
(RIN) must be the same in both ISPBXs (including leading zeroes), the Main/Sub indication
(m/s) must be 0 on one side and 1 on the other side.
CHPVNR : <route>,<sigch-address>,<uca-prefix>,<rin>,<m/s>;
Additional parameters :
CHPVNR : 5,00302343999,0030234,0001,0;
In this example 0-0302343999 is the number that the system will generate if a signalling
channel must be established. The other system will see incoming number 3999. This
number must lead to result-id 133 in the opposite system. In the opposite ISPBX program :
CHPVNR : 6,00356892999,0035689,0001,1;
13. Set up the incoming number analysis from the PSTN to recognise an incoming signalling
channel :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 30,2999,2,133[,<unit>];
In this example 2999 is the incoming number when the other side wants to establish a
signalling channel.
14. Assign the User Channel Addresses that will be sent to the opposite ISPBX when it
requests a User Channel :
ASPVNU : <uca>[,<unit>];
ASPVNU : 2998[,<unit>];
ASPVNU : 2997[,<unit>];
15. The opposite ISPBX will make a call to these numbers, so they must be projected in the
incoming analysis tree from the PSTN :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 30,2998,2,132[,<unit>];
ASINTN : 30,2997,2,132[,<unit>];
16. Make sure that the outgoing signalling channel address and the user channel addresses are

37
 projected in the outgoing tree for the PSTN connection.
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
Additional parameter : [<route-table>];
ASEXTN : 60,0,3,4,12,0; ;
17. When required, program the timers :
CHPVNT : <route>[,<sequence-table>[,<sigch-tu>][,<sigch-tv>,<usrch-
tu>,<usrch-tv>]];
CHPVNT : 5,1,0,0,0,0;
18. When required change the default PTN-ID and security code. The values must be the
same in both systems :
CHPVNS : [<PTN-ID>];
Enter old Security Code : <SC>;
Enter new Security Code : <SC>;
Verification : <SC>;
CHPVNS : 9999;
899111;
123456;
123456;

2.3.2. iPVN

PROCEDURE: HOW TO PROGRAM iPVN

Preconditions

• iPVN requires a numeric license (license item 29) for the number of routes that are
allowed to be set up via TCP/IP signalling connection. Per unit an iPVN license is required.
If the license is not available, no iPVN calls can be made.
Note that for iPVN, the PVN license (number 11) and DPNSS license (number 5) are
required too.
Check if your system has licenses for DPNSS, PVN and iPVN:
DILICS : ;
• To use iPVN the following hard- and software is required:
- SSW 810.21 and onwards.
- In CCS systems iPVN requires CIE-2 hardware boards with firmware package
FA100.04.01 or later.
- LOSYSOP 120 (iPVN Active) must be set to 'true'.
- Note that it is not possible to combine iPVN with Compressed PVN.
- For iPVN signalling channel connections no FDCR record or toll-ticket can be

38
 generated.
Actions

Execute the following actions in both ISPBXs.

1. Execute STWARM to activate LOSYSOP 120 (iPVN Active).

2. Program PVN exactly the same as described in the previous section.
The only difference is parameter <sigch-address>in OM command CHPVNR.
3. CHPVNR : <route>,<sigch-address>,<uca-prefix>,<rin>,<m/s>;
CHPVNR : 5,192.168.1.20,0030234,0001,0;
In this example 192.168.1.20 is the IP address of the CIE-2/CPU3000 in the opposite
ISPBX.
At ISPBX system start-up, the ISPBX starts to behave as a TCP/IP server, listening for
incoming iPVN requests from other ISPBX systems. The server listens at a TCP port
number defined by LOBOUND 356 : iPVN Listen Port (default value is 2595).

In case of an Ethernet connection failure, it is possible to switch over to normal PVN, when
projected as well.

2.3.3. PVN as Overflow Route

PROCEDURE: HOW TO PROGRAM PVN AS OVERFLOW ROUTE

Preconditions

• Check if your system has licenses for DPNSS and Private Virtual Networking :
DILICS : ;
• Check if your system contains at least one PMC.
Actions

In the following OM Commands (Italic) the next configuration is assumed :

39
 PSTN

035-689 030-234

Virtual Route 6
ISPBX
ISPBX
A B
DPNSS Route 5
20xx 30xx

Figure 2-13 Example PVN Configuration.

Projecting for ISPBX A.

1. Delete one line from the existing DPNSS route and create a new route with this one line
in it. This route will be used to transport the signalling channel to the other side.
Alternatively the signalling channel can be transported via the PSTN, but in this case a
digital PSTN is required. If this is the case, continue with step 9.
DELINE : <shelf>,<board>,<circuit>;
DELINE : 1012,9,2;
2. Create a new route : CRROUT : <route>[,<unit>];
CRROUT : 6[,<unit>];
3. Create a voice CV. This CV will be used on route 6 to guard it against extensions using this
route. CRCVAL : <CV>,<VOICE/DATA>;
CRCVAL : 5,v;
4. Set the CV connection allowance to permit a connection from CV 5 to CV5.
CHCVCA : <cv-a>,<cv-b>,<con-allowance>;
CHCVCA : 5,5,3;
5. Set the route characteristics (copy from existing DPNSS route). This route will carry the
Signalling Channel, so it is protected from normal use by a CV (5).
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 6,0010001000000,222111,5;
CHRTCI : 6,1000000000000,000599999,35;
CHRTCO : 6,000000,0;
6. Assign the bundle characteristics (copy from existing DPNSS bundle 5) :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-

40
 calls>][,<bspt>]];
CHBNDC : [uu]006,2,0000000000000000,46;
7. Assign the bundle to this new route :
ASBNDL : <route>,<bundle>;
ASBNDL : 6,6;
8. Assign the line deleted in step 1 to the new bundle.
ASLINE : <bundle>,<line>,<shelf>,<board>,<circuit>;
ASLINE : 6,1000,1012,9,2;
9. Create a PVN route :
CRROUT : <route>[,<unit>];
CRROUT : 7[,<unit>];
10. Add the PVN route to the routing table of the DPNSS destination :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 5[,,,<unit>];
CHROTA : 5,1,3;
7,0,3;
11. If the signalling channel is transported over the real DPNSS route (6), assign the route with
1 line as priority in the routing table of the DPNSS destination :
CHROTA : 5,2[,,<unit>];
CHROTA : 6,1,3;
12. Change the PVN route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 7,0010010000000,222111;
CHRTCI : 7,10000000000,000599999,35;
CHRTCO : 7,000000,0;
13. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]007,2,0000000000000000,516;
14. Assign the bundle to the PVN route :
ASBNDL : <route>,<bundle>;
ASBNDL : 7,7;
15. Assign the Hatch and set it in service : ASPCTB : <shelf>,<brd>,<crt>,<pct-
type>,<sig-group>;
ASPCTB : 1011,17,12,16,6104;
SETINS : 1012,17,12;
16. Set up the PVN characteristics of the DPNSS route. The Route Identification Number

41
 (RIN) must be the same in both ISPBXs (including leading zeroes), the Main/Sub indication
(m/s) must be 0 on one side and 1 on the other side.
CHPVNR : <route>,<sigch-address>,<uca-prefix>,<rin>,<m/s>;
Additional parameters : [<pvn-mode>][,[<cv>][,<tree>]];
CHPVNR : 7,3099,0030234,0001,0; ,5;
In this example 3099 is the number that the system will generate if a signalling channel
must be established. The opposite system will see incoming number 3099 on the real
DPNSS link. This number must lead to result-id 133 (hatch) in the opposite system. If the
signalling channel must be established over the PSTN change this 3099 to 00302343099
and do not give a CV in the additional parameters. In the opposite ISPBX program :
CHPVNR : 6,2099,0035689,0001,1;
In the additional parameters of the CHPVNR command the tree for initial extension
dialling (0) is indicated and the CV (5) that is used to set op the signalling channel and user
channel.
17. Set up the incoming number analysis on the real DPNSS link (tree 35) to recognise an
incoming signalling channel (If the signalling channel must be established over the PSTN on
the incoming digital PSTN link : tree 30) :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 35,2099,2,133[,<unit>];
In this example 2099 is the incoming number when the other side wants to establish a
signalling channel.
18. Assign the User Channel Addresses that will be sent to the opposite ISPBX when it
requests a User Channel :
ASPVNU : <uca>[,<unit>];
ASPVNU : 2098,<unit>;
ASPVNU : 2097,<unit>;
19. The opposite ISPBX will make a call to these numbers, so they must be projected in the
incoming analysis tree from the PSTN :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
ASINTN : 30,2098,2,132[,<unit>];
ASINTN : 30,2097,2,132[,<unit>];
20. Make sure that the outgoing user channel address (and the signalling channel addresses)
are projected in the outgoing tree for the PSTN destination. If the signalling channel is
transported over the DPNSS route, make sure that the outgoing signalling channel
addresses are projected in the outgoing tree for the DPNSS destination.
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
Additional parameter : [<route-table>];
ASEXTN : 60,0,3,4,12,0;

42
 ;
21. If the signalling channel is transported over the existing DPNSS route, create and set a CV
(e.g. 6) on the PSTN route used to transport the User Channel(s). PVN will setup the User
Channel with CV 5, so a connection allowance from CV 5 to CV 6 and from CV 6 to 5
must be set. If normal extension users should still be able to use the PSTN route, also a
connection allowance from CV 0 to 6 and from CV 6 to 0 should be set.
CRCVAL : 6,v;
DIROUT : 0;
CHRTCG : 0,0010001000000,222111,6;
Copy the general route characteristics from route 0 (PSTN route)
CHCVCA : 5,6,3;
CHCVCA : 6,5,3;
CHCVCA : 0,6,3;
CHCVCA : 6,0,3;
22. When required, program the timers :
CHPVNT : <route>[,<sequence-table>[,<sigch-tu>][,<sigch-tv>,<usrch-
tu>,<usrch-tv>]];
CHPVNT : 5,1,1,5,0,10;
In case the signalling channel is transported over the existing DPNSS route, set the
signalling channel timer to infinite.
CHPVNT : 5,1,1,16383,0,10;
Which sequence table is used, depends on the ASFATI command. If no sequence tables
are projected, sequence table 1 is the default.
23. When required change the default PTN-ID and security code. The values must be the
same in both systems :
CHPVNS : [<PTN-ID>];
Enter old Security Code : <SC>;
Enter new Security Code : <SC>;
Verification : <SC>;
CHPVNS : 9999;
899111;
123456;
123456;

2.3.4. PVN with Voice Compression

PROCEDURE: HOW TO PROGRAM PVN WITH VOICE COMPRESSION

Preconditions

43
 • Check if your system has licenses for DPNSS and PVN :
DILICS : ;
• Check if the following download packages are present :
DTU-VC : F51010.104 or higher.
PMC : F14050.701/F15050.701 or higher.
PPU PROMs : 162.701/262.701 or higher.
• Check if the synchronization to the public network is working correctly :
DICRUE : [<unit>];
Actions

In the following OM Commands (Italic) the next configuration is assumed :

PSTN

035-689 030-234

ISPBX
ISPBX
Virtual Route 10
A B
20xx 30xx

Figure 2-14

Projecting for ISPBX A

1. Fill in the Cluster-Id of your system :

CHCLID : <cluster-id>;
Note that in a closed numbering scheme this must be the same as the first digit(s) of the
DNRs in your system. To determine if your system is programmed for a closed numbering
scheme execute :
DIMDAT : 1,40[,<unit>];
If the answer is YES, you have a closed numbering scheme.
CHCLID : 2;
If the DNRs in your system are 2xxx.
2. Project the Network Access Code (NAC) in the tree for initial extension/enquiry/operator
dialling :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
This Network Access Code (NAC) must be the same as the cluster-id of the other ISPBX.

44
 ASINTN : 0,3,3,91,10;
ASINTN : 1,3,3,91,10;
ASINTN : 2,3,3,91,10;
if the DNRs in the opposite ISPBX have the format 30xx.
3. Project the DPNSS destination and the related outgoing number analysis tree and route-
table :
CHDSTC : <dest>,<tree>,<dialtone-options>,<route-table>[,[<acc-
rep>][,<delayed-seizure>[,<numbering-plan>]]];
CHDSTC : 10,70,00,10;
4. Analyse the number after the Network Access Code in the outgoing analysis tree as an
internal number :
OPEN numbering scheme : Complete DNR
CLOSED numbering scheme : DNR - NAC
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASBLCK : 70,0,3,3,10;
If the DNRs in the opposite ISPBX have the format 30xx and there is a CLOSED
numbering scheme.
5. Create a route :
CRROUT : <route>[,<unit>];
CRROUT : 10[,<unit>];
6. Add the route to the routing table :
CHROTA : <route-table>[,[<user-type>][,<sequence-table>][,<unit>]];
Additional parameters : <route>,<pref-code>,<trfc>[,<smart-box-em>];
CHROTA : 10[,,,<unit>];
10,1,3;
;
7. Change the route characteristics as required.
CHRTCG : <route>,<gen-opts>,<gen-tone>[,[<cv>][,<bspt>][,<cc-table-nr>]]];
CHRTCI : <route>,<inc-opts>,<tone-and-ddi-opts>[,[<tree>][,[<a-
queue>][,<bspt>]]];
Do not set option S (traffic class) in the parameter <tone-and-ddi-opts>too low!
CHRTCO : <route>,<out-opts>,<atf>[,<bspt>];
CHRTCG : 10,0010000100000,222111;
CHRTCI : 10,10000000000,000599999,40;
CHRTCO : 10,000000,0;
8. Assign the bundle characteristics :
CHBNDC : <unit+bundle>,<dir-and-neg>,<options>,<con-and-sig-type>[,[<all-
calls>][,<bspt>]];
CHBNDC : [uu]010,2,0000000000000000,516;
9. Bundle 10 will contain compressed calls, so it can only handle the following IBSCs :
1 : speech

45
 3 : 3.1 kHz audio non-ISDN (when used for a fax/modem call from an S0bus)
14 : ISPBX speech
15 : ISPBX modem (will be slowed down to 2400 bps)
18 : Bildtelefon Ton
19 : 64 kbps unrestricted non-ISDN (Used for digital lines with analogue signalling, e.g.
DTU-CA. The actual service profile of the call is unknown. Can only be handled in case of
a voice call).
This means, that extensions with IBSC 0, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 16 and 17 should
be prohibited from using this bundle. It is therefore necessary to create a BSPT containing
the IBSCs that should not use voice compression.
CRBSPT : 20;
0;
2;
4;
etc.
Assign this new BSPT to the bundle and set the number of allowed calls for this bundle/
BSPT combination to zero.
ASBSPB : [uu]010,20;
CHBNDC : [uu]010,2,0000000000000000,516,0,20;
10. Assign the bundle to the DPNSS route.
ASBNDL : <route>,<bundle>;
ASBNDL : 10,10;
11. Program the incoming DPNSS number analysis : For a closed numbering scheme it is
possible to do a one-step analysis, i.e. to project the complete internal DNR (result-id 10)
in the incoming tree :
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
For an open numbering scheme or if centralized operator on the basis of the cluster-id
must be used a two-step analysis is required, this two-step analysis also works for a closed
numbering scheme :
Step 1 :
Analyse the incoming cluster-identity :
ASINTN : <tree>,<number>,<trfc>,<result-id>[,[<dest/number>][,<number-
length/cv>]];
Note that the <dest/number>must be a dummy destination : a destination number not
yet used in the system.
Step 2 :
Analyse the remaining incoming digits :
CHDSTC : <dest>,<tree>,00,0;
ASBLCK : <tree>,<number>,<trfc>,<number-length>,<result-id>;
ASINTN : 40,2,3,91,19;
CHDSTC : 19,19,00,0;

46
 ASBLCK : 19,0,3,3,10;
12. Assign the DTU-VC without circuits and assign the compressor circuit 5. Note that the
other circuits cannot be used.
ASBRDS : <shelf>,<brd>,<board-type>,<sig-group>,<test-type>,<as-pct>;
ASPCTB : <shelf>,<brd>,<crt>s/r,<pct-type>,<sig-group>;
ASBRDS : 1012,7,17,6504,,0;
ASPCTB : 1012,7,5,1,6504;
13. Check the package relation and set it if necessary.
DIPACK : <shelf>,<board>;
INSTPK : <new-pack>;
DIPACK : 1012,7;
14. Set the DTU-VC and circuit 5 in service.
SETINS : 1012,7;
SETINS : 1012,7,5;
15. Assign a DNR to the compressor circuit and set the IBSC/BSPT of this DNR to '64 kb
unrestricted'.
CHDNRC : 2900,1012,7,5;
CHDNRS : 2900,0,0;
16. Assign facility class marks 3 (break-in protected), 4 (data protected), 35 (call waiting
protected) and 49 (ARB protected) to the compressor DNR.
ASFACM : 3&4&35&49,2900;
The DNR will automatically get FCM 12 (SOPHO SET).
17. Assign COB queue length 0 (no COB) to the compressor DNR.
CHCOBD : 2900,0;
18. Assign the compressor DNR to the unit.
CHPVND : <dnr>,<unit>;
CHPVND : 2900[,<unit>];
19. Set up the PVN characteristics of the DPNSS route. The Route Identification Number
(RIN) must be the same in both ISPBXs (including leading zeroes), the Main/Sub indication
(m/s) must be 0 on one side and 1 on the other side. Give PVN mode 2 (PVN with voice
compression) as an additional parameter.
CHPVNR : <route>,<sigch-address>,<uca-prefix>,<rin>,<m/s>;
CHPVNR : 10,00302343900,[<UCA prefix>],0001,0;
2;
In this example 0-0302343900 is the number that the system will generate if a signalling
channel must be established. The other system will see incoming number 3900. This
number must lead to result-id 133 with PVN mode 2 in the opposite system. In the
opposite ISPBX program :
CHPVNR : 6,00356892900,[<UCA prefix>],0001,1;
The parameter 'UCA prefix' is only required when additional non-compressed user
channels are required when there are more than 3 calls. Due to the lower capacity of the

47
 signalling channel (8 kbps), only 5 additional user channels are available!
20. Set up the incoming number analysis from the PSTN to recognise an incoming signalling
channel :
ASINTN : <tree>,<number>,<trfc>,<result-id>,<unit>,<PVN mode>;
ASINTN : 30,2900,2,133,[<unit>],2;
In this example 2900 is the incoming number when the other side wants to establish a
signalling channel. When more compressor circuits are used (more DTU-VCs), create a
group (group property 17) which contains all compressor DNRs. In this case the incoming
number analysis should lead to the group DNR and not directly to the compressor DNR
itself.
21. If the UCA prefix was assigned with the CHPVNR command, then assign the User Channel
Addresses that will be sent to the opposite ISPBX when it requests a User Channel :
ASPVNU : <uca>[,<unit>];
ASPVNU : 2901[,<unit>];
ASPVNU : 2902[,<unit>];
22. The opposite ISPBX will make a call to these numbers, so they must be projected in the
incoming analysis tree from the PSTN :
ASINTN : <tree>,<number>,<trfc>,<result-id>,<unit>;
ASINTN : 30,2901,2,132[,<unit>];
ASINTN : 30,2902,2,132[,<unit>];
23. Make sure that the outgoing signalling channel address and optionally the user channel
addresses are projected in the outgoing tree for the PSTN connection.
ASEXTN : <tree>,<number>,<trfc>,<min-length>,<max-length>,<dialtone-
place>[,<tariff-class>];
Additional parameter : [<route-table>];
ASEXTN : 60,0,3,4,12,0;
;
24. When required, program the timers :
CHPVNT : <route>[,<sequence-table>[,<sigch-tu>][,<sigch-tv>,<usrch-
tu>,<usrch-tv>]];
CHPVNT : 10,1,0,0,0,0;
Note that the timers for the compressed channels are don't care.
25. When required change the default PTN-ID and security code. The values must be the
same in both systems :
CHPVNS : [<PTN-ID>];
Enter old Security Code : <SC>;
Enter new Security Code : <SC>;
Verification : <SC>;
CHPVNS : 9999;
899111;
123456;

48
 123456;
Testing

Make a PVN call by dialling an NDNR. If this call results in Number Unobtainable, execute the
following steps :

1. Read out all alarms in your system.

2. Test the compressor DNR as follows :
- Assign IBSC/BSPT 0/0 to an analogue extension (CHDNRS : 1000,0,0;)
- Dial an outgoing line, followed by the subscriber code, followed by the compressor
DNR, e.g. 0-035-6892900. The result should be an engine-like sound.
- If this connection ends in Number Unobtainable tone, check the following :
Outgoing number analysis to the public network.
Incoming number analysis from the public network.
The compressor DNR (2900) should lead to result-id 133 with PVN-mode 2.
Alternatively the number you dial should lead to a group DNR, analysed with result-
+id 133 in the incoming tree.
The group should contain one or more compressor DNRs.
Compressor DNR should be defined in the system : check with DIPVND.
- Compressor DNR should be assigned to circuit 5 of a DTU-VC : check with DICDNR.
- Compressor DNR should have IBSC/BSPT 0/0 : check with DIDNRS.
- DTU-VC should have been projected the right way, see step 12 : check with DIBRDS.
- Don't forget to change the IBSC/BSPT of the analogue extensions back to 14/95 when
finished with this test.
3. Check the PVN route characteristics of your own system and the other system.
The signalling channel address should point to the compressor DNR; the UCA-prefix is
optional.
4. Check all DPNSS number analysis and projecting.

2.4. REPLACEMENT DPNSS BY 'ISNET ON TOP OF QSIG'

This section describes how an existing DPNSS network (or part of it) can be replaced by 'iSNet
on top of QSIG'.

2.4.1. General

Use next steps to replace the DPNSS network by 'iSNet on top of QSIG' :

1. Upgrade all Call@Net PINXs in the DPNSS network to release 2.9 or higher.
Upgrade the PMC / PPU packages to the latest releases.
Upgrade PPH packages (DTX-I: 203.11.01 or higher, DTU-PH: 140.29.01 or higher).

49
 2. Upgrade PINXs with SSW 805 to Call@Net 2.9 or higher (when required).
3. Activate the license for 'iSNet on top of QSIG' to the PINXs with Call@Net 2.9 or higher.
4. Project the system boundary NEBOUND 359 (QSIG transit counter) equal to
NEBOUND 14 (DPNSS transit counter).
5. Investigate which bundles must be changed from DPNSS to QSIG.
Important notes :
- All bundles in a route must be QSIG or all bundles must be DPNSS (when not all
bundles in a route must be changed, a route must be split up in two routes).
- 'iSNet on top of QSIG' is only supported on DTX-I and DTU-PH boards.
If necessary replace :
- the DTU-PU (+IPH) boards (used as DTU-PR) by DTU-PH boards
- the DTU-BA boards by DTX-I-boards.
- DPNSS bundles between two Call@Net 2.9 or higher PINXs (and that are accessed
by dialling a NAC) can be changed into QSIG.
6. Change DPNSS bundles into QSIG : see following section.

2.4.2. How to change bundle(s) from DPNSS to QSIG

The actions given below must be executed in the PINXs at both ends of the bundle.

1. Execute DIBNDL to display the bundle characteristics and the line-EHWA relations of the
bundle.
Log or make a note of the displayed data, because the same relations have to be re-
assigned later on (step 11).
2. Execute SETNIN to put the lines of the bundle in NIN.
3. Execute SETNIN to put the boards (of the lines) in NIN.
4. Execute DELINE to delete the lines.
5. Execute DEBRVC to delete the virtual channels.
6. Repeat step 1... 5 for bundles that use the same DTU-PH or DTX-I board.
7. Execute CHBNDC to change the signalling type :
- 6 (DPNSS-x) into 20 (QSIG-A) and
- 7 (DPNSS-y) into 21 (QSIG-B)

WARNING: DO NOT CHANGE THE SIGNALLING TYPE IN THE LL FILE,

UNLESS ALSO SUBCOMMAND S45190 FOR THE ROUTE OF THE
BUNDLE IS CHANGED TO S45190:<ROUTE>,2; IN ALL UNITS !

8. Execute DIBRDS to display the data of the board(s) used by the bundle(s). Be sure to log
or note the displayed data.
9. When the board(s) have a board-type/signalling group data for DPNSS (see next table),
then execute DEBRDS to delete the board and execute ASBRDS to re-assign the board

50
 with the board-type/signalling group for QSIG according to the table below.

BOARD DPNSS QSIG

BRD-TYPE SIG. GRP. BRD-TYPE SIG. GRP.
DTU-PH 19 6704 18 5D20
DTU-PH 19 6705 18 5D21
DTX-I(7) 26 660C 28 5C20
DTX-I(7) 26 660D 28 5C21
DTX-I(15) 27 6610 29 5C20
DTX-I(15) 27 6611 29 5C21

Table 2-12 Board type and signalling groups

10. Check if the board had 'modified PCTs' : see step 9, output of DIBRDS: signalling group of
PCT deviates from signalling group of board.
If so, then execute CHPCTB to change the PCT data (resource type, signalling group) in
such a way that the old situation is restored, except that DPNSS signalling groups are
replaced by QSIG signalling groups : see table below.

DPNSS PCT SIG. GRP. QSIG PCT SIG. GRP.

6704 5D20
6705 5D21
660C, 6610, 6604 5C20
660D, 6611, 6605 5C21

Table 2-13 PCT signalling groups

11. Execute ASLINE to assign the line-circuit and line-bundle relations, according to the
displayed data in step 1 again. Be aware of the different numbering of the circuits in DPNSS
and QSIG, for example :

EHWA in DPNSS EHWA in QSIG

line 0001 13, 1, 2 13, 1, 2, 0
line 0002 13, 1, 3 13, 1, 2, 1
12. Execute SETINS to put the boards and circuits in INS.

51
 2.4.3. How to change over from DPNSS-PVN to QSIG-PVN

Configuring QSIG-PVN is similar to configuring the existing DPNSS-PVN, except for

parameter CON-AND-SIG-TYPE in OM command CHBNDC, signalling type 16 (DPNSS-
PVN) has to be changed into signalling type 22 (QSIG-PVN).

WARNING: DO NOT CHANGE THE SIGNALLING TYPE IN THE LL FILE,

UNLESS ALSO SUBCOMMAND S45190 FOR THE ROUTE OF THE
BUNDLE IS CHANGED TO S45190:<ROUTE>,2; IN ALL UNITS !

52
3. QSIG AND ISDN ADDRESSING (Call@Net 2.6)

3.1. MULTI-TENANT CONFIGURATION

Suppose a multi-tenant configuration with 3 companies on one iS3000 system as illustrated

below :

PSTN Country Code : 31

Area Code : 35
DDI prefix company A : 543
B : 689
C : 721
Route 1 2 3

DNR range company A : 1000 ... 1999

iS3000
B : 2000 ... 2999
C : 3000 ... 3999

Figure 3-1 Multi-tenant Configuration

Furthermore each company has it own route to the PSTN. The number analysis is projected
in the following way :

COMPANY A B C
Trunk Access Code to destination 0 0 0
'PSTN'
Destination number 5 6 7
Outgoing Analysis Tree 65 66 67
Route table 1 2 3
Route 1 2 3

1. Execute OM command CHDSTC to assign the numbering plan :

CHDSTC : 5,65,00,1,,0,1;(for company A)
CHDSTC : 6,66,00,2,,0,1;(for company B)

53
 CHDSTC : 7,67,00,3,,0,1;(for company C)

in which the last parameter '1' indicates the E.164 numbering plan.

2. Execute OM command CHLDOM to define the Local Domain ID (LDI), with numbering
plan E.164, for the three different companies, with the additional parameters given in table
below :
CHLDOM : 1,1;(LDI 1 for company A)
CHLDOM : 2,1;(LDI 2 for company B)
CHLDOM : 3,1;(LDI 3 for company C)

ADDITIONAL PARAMETERS LDI 1 LDI 2 LDI 3

Country/Level 2 Code 31 31 31
Area/Level 1 Code 35 35 35
DDI Prefix 543 689 721
International/Level 2 Prefix 00 00 00
National/Level 1 Prefix 0 0 0
Special Services Prefix 1 1 1
Trunk Access Code 0 0 0
Preferred TON for Called Party Number 2 2 2
Preferred TON for Calling/Connected Party Number 2 2 2
Trunk Access Code for CLI/COL with TON unknown 0 0 0
Route defines call back Trunk Access Code for CLI/ 0 0 0
COL

3. Execute OM command CHDNRL to define the relation between the DNRs and the LDIs :
CHDNRL : 1000&&1999,1;
CHDNRL : 2000&&2999,2;
CHDNRL : 3000&&3999,3;

4. Execute OM command CHRTLD to define the relation between the routes and the LDIs :
CHRTLD : 1,1;(route 1 for company A)
CHRTLD : 2,2;(route 2 for company B)
CHRTLD : 3,3;(route 3 for company C)

5. Execute OM command CHLODD to define the location determination data for the E.164
numbering plan as follows :
CHLODD : 1,1,543%,%;(Subscriber)
CHLODD : 1,2,35543%,%;(National)
CHLODD : 1,3,3135543%,%;(International)

54
 CHLODD : 1,1,689%,%;(Subscriber)
CHLODD : 1,2,35689%,%;(National)
CHLODD : 1,3,3135689%,%;(International)
CHLODD : 1,1,721%,%;(Subscriber)
CHLODD : 1,2,35721%,%;(National)
CHLODD : 1,3,3135721%,%;(International)

3.2. TWO ISPBXS IN DIFFERENT AREAS

Suppose a configuration of one company with two ISPBXs (not a multi-unit configuration)
located in different areas as illustrated below :

Area 020 Area 040

LDI=2

PBX Route 99 PBX

A B

DDI DDI
prefix prefix
693 Route 98 257
LDI=1 LDI=4

LDI=3

Figure 3-2 Two ISPBXs in different Areas

PARAMETERS ISPBX A ISPBX B

Country Code 31 31
Area Code 20 40
DDI Prefix 693 257
International Prefix 00 00
Number range 1000&&2999 3000&&3999
LDI of DNRs LDI = 1 LDI = 4
Destination 19 18
Route table 29 28
Route 99 98
LDI of route LDI = 2 LDI = 3

1. Execute OM command CHLDOM in both ISPBX A and B to define the Local Domain

55
 ID (LDI), with numbering plan E.164 :
CHLDOM : 1,1;(with the additional parameters given in table below)
CHLDOM : 2,1;
CHLDOM : 3,1;
CHLDOM : 4,1;

ADDITIONAL PARAMETERS LDI 1 LDI 2 LDI 3 LDI 4

Country/Level 2 Code 31 31 31 31
Area/Level 1 Code 20 40 20 40
DDI Prefix 693 257 693 257
International/Level 2 Prefix 00 00 00 00
National/Level 1 Prefix 0 0 0 0
Special Services Prefix 1 1 1 1
Trunk Access Code 0 0 0 0
Preferred TON for Called Party Number 2 2 2 2
Preferred TON for Calling/Connected Party 2 2 2 2
Number
Trunk Access Code for CLI/COL with TON 1 1 1 1
unknown
Route defines call back Trunk Access Code for 1 1 1 1
CLI/COL

2. Execute OM command CHDNRL in both ISPBX A and B to define the relation

between the DNRs and the LDIs :
CHDNRL : 1000&&2999,1;
CHDNRL : 3000&&3999,4;

3. Execute OM command CHRTLD in both ISPBX A and B to define the relation between
the routes and the LDIs :
CHRTLD : 99,2;
CHRTLD : 98,3;

4. Execute OM command CHLODD in ISPBX A to define the location determination data

as follows :
CHLODD : 1,1,693%,%;
CHLODD : 1,2,20693%,%;
CHLODD : 1,3,3120693%,%;

5. Execute OM command CHLODD in ISPBX B to define the location determination data

as follows :

56
CHLODD : 1,1,257%,%;
CHLODD : 1,2,40257%,%;
CHLODD : 1,3,3140257%,%;

57
58