SUMMARY OF CONTENTS

SOPHO iS3010/iS3030 (SSW300) Customer Engineer Manual (9710)

1.
2.
3.
4.
5.
6.

7.
8.
9.
10.

9710

PREFACE . . . . . . . . . . . . . . . . .
CONTENTS . . . . . . . . . . . . . . .
AMENDMENTS . . . . . . . . . . . .
SOPHO iS3010/3030
CHARACTERISTICS . . . . . . . .
SERVICE CONDITIONS . . . . . .
MAINTENANCE . . . . . . . . . . . .
LOADING AND RETRIEVING
ISPBX SOFTWARE . . . . . . . . .
PROJECT DATA PROTECTION
THE HANDLING OF PRINTED
WIRING BOARDS . . . . . . . . . . .

0-1
0-3
0-13

EQUIPMENT INSTALLATION .
MAIN DISTRIBUTION FRAME .
FINISHING INSTALLATION . . .
DIL SWITCHES AND STRAP
SETTINGS . . . . . . . . . . . . . . .

7-1
8-1
9-1

1-1
2-1
3-1
4-1
5-1
6-1

11.
12.
13.
14.
15.

A.
B.

10-1

CONNECTION OF AUXILIARY
EQUIPMENT . . . . . . . . . . . . . 11-1
DIAGNOSTIC TEST . . . . . . . 12-1
CLEARANCE OF FAULTS . . 13-1
REPLACEMENT PROCEDURES 14-1
POWER SUPPLY
INSTALLATION . . . . . . . . . . . 15-1

FRONT CONNECTOR
ASSEMBLY . . . . . . . . . . . . . . .
S0 INTERFACE . . . . . . . . . . . .

A-1
B-1

DIAGRAMS

ALARM CODES

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1

ALARM CODES
ALARM CODE

ERROR TYPE

1000
1002
1003
1005
1006

10

20

30

40

1008

40

41

42

50

51

60

70

71

80(1) 80(2) 90

1009

80

1010

10

15

30

35

40

50

51

60

61

70

1011

30

35

40

50

51

60

61

70

80

90

1013

10

1014

1

2

3

4

5

6

7

8

9

1040

10

20

30

31

40

50

51

1041

20

21

30

40

1042

10

20

30

40

50

60

61

70

80

90

1043

10

20

30

40

50

60

1044

10

1045

1

2

3

4

5

6

7

8

9

1046

1

2

3

4

5

6

7

8

9

1048

00

01

02

03

05

06

07

08

09

00

10

20

30

80

90

95

80

90

10

11

12

13

10

11

12

13

1015
1023
1030

1049
1050
1051
1052
1060
1065
1066
1080
1081

00

PREFACE
This manual is valid for installing and maintaining the SOPHO iS3010/3030 with System
Software 300.
It is also valid for SOPHO-S55/255 systems. References made in this manual to the
SOPHO iS3010/3030 are also valid for the SOPHO-S55/255.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

0-1

0-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

CONTENTS
0.

CONTENTS

Pages 0-1/0-14

(9710)

1.

SOPHO iS3010/3030 CHARACTERISTICS

Pages 1-1/1-12

(9412)

1.1.

SYSTEM ASSURANCE TEST SOFTWARE . . . . . . . . . . . . . . . . . . . . .

1-2

1.2.

PROJECT DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

1.3.

RETRIEVING THE RUNNING POM DATA . . . . . . . . . . . . . . . . . . . . . .

1-5

1.4.

DATA PACKAGE STORAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5

1.5.

POWER FAIL PROTECTION

................................

1-5

1.6.

SYSTEM STARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6

1.7.

COLD / WARMSTART CHARACTERISTICS . . . . . . . . . . . . . . . . . . . .

1-6

1.8.

TELEPHONE SETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6

1.9.

TRUNK UNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-7

1.10.

EXTERNAL CLOCK SYNCHRONIZATION

.....................

1-7

1.11.

TONE GENERATION AND RHYTHMS . . . . . . . . . . . . . . . . . . . . . . . . .

1-7

1.12.

OPERATOR POSITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8

1.13.

DAY SERVICE - NIGHT SERVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

1.14.

ALARM SIGNAL DISTRIBUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

1.15.

ALARM UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-10

1.16.

POWER SUPPLY FOR SOPHO iS3010/3030 . . . . . . . . . . . . . . . . . . . .

1-10

2.

SERVICE CONDITIONS

2.1.

CIRCUIT CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1

2.2.

CHANGING CIRCUIT CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

2.3.

OWNERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

2.4.

POSSIBLE SERVICE CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

2.5.

PERIPHERAL MODULE SERVICE CONDITIONS . . . . . . . . . . . . . . . .

2-4

9710

Pages 2-1/2-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

(9412)

0-3

3.

MAINTENANCE

3.1.

CONTROL SECTION TESTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1

3.2.
3.2.1.
3.2.2.

SWITCHING SECTION AND PERIPHERAL SECTION TESTING . . . .
Automatic Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1
3-1
3-1

3.3.

SWITCHING SECTION AND PM TEST ROUTINES . . . . . . . . . . . . . . .

3-3

3.4.

MONITORING ROUTINES

..................................

3-3

3.5.
3.5.1.
3.5.2.

ALARM GENERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
History Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4
3-4
3-5

4.

LOADING AND RETRIEVING ISPBX SOFTWARE

Pages 3-1/3-6

Pages 4-1/4-16

(9412)

(9412)

4.1.

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

4.2.

CONNECTING THE MPC TO THE CPU CIRCUIT BOARD . . . . . . . . .

4-2

4.3.

INSTALLING FILES ON THE MPC HARD DISK

4-3

4.4.

PREPARING SOFTWARE AND DATA FOR THE ISPBX

..........

4-3

4.5.
4.5.1.
4.5.2.
4.5.3.
4.5.4.
4.5.5.
4.5.6.
4.5.7.

LOADING SOFTWARE AND DATA INTO THE ISPBX . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading CPU Software (Flowchart) . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading CPU Software (MML Commands) . . . . . . . . . . . . . . . . . . . . .
Loading POM Data and Peripheral Software (Flowchart) . . . . . . . . .
Loading POM Data (MML Commands) . . . . . . . . . . . . . . . . . . . . . . . .
Loading Peripheral Software (MML Commands) . . . . . . . . . . . . . . . .
Downloading Software for Peripheral Circuits DTX-I and DLC-U . .

4-4
4-4
4-5
4-6
4-8
4-9
4-9
4-11

4.6.
4.6.1.
4.6.2.
4.6.3.

RETRIEVING POM DATA FROM THE ISPBX (MAKING A BACK-UP)
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Making a Back-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-13
4-13
4-14
4-14

5.

PROJECT DATA PROTECTION

6.

THE HANDLING OF PRINTED WIRING BOARDS

.................

Pages 5-1/5-2

Pages 6-1/6-2

0-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

(9412)

(9412)

9710

7.

EQUIPMENT INSTALLATION

7.1.

GENERAL REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-1

7.2.

SITE REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-1

7.3.

REQUIRED INSTALLATION EQUIPMENT . . . . . . . . . . . . . . . . . . . . . .

7-1

7.4.

ANTISTATIC HANDLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-1

7.5.

SITE CHECKS AND INSPECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-2

7.6.

UNPACKING, LOCATING AND FIXING THE CABINET . . . . . . . . . . .

7-2

7.7.
7.7.1.
7.7.2.
7.7.3.
7.7.4.
7.7.5.

CABLING THE EMC IMPROVED CABINETS . . . . . . . . . . . . . . . . . . .
EMC in General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabinet Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling the EMC Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Trunk Filters for ATU-SS02/ST02 . . . . . . . . . . . . . . . . .
Required EMC Improved Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-3
7-3
7-3
7-4
7-5
7-6

7.8.

PMC-PMC CABLE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-7

7.9.
7.9.1.
7.9.2.

DIFFERENCES BETWEEN THE EMC AND NON-EMC CABINETS . .
Different Installation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Installation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-7
7-7
7-8

7.10.

FLOORSTAND INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-8

8.

MAIN DISTRIBUTION FRAME

8.1.

CONSTRUCTION

.........................................

8-1

8.2.

MDF BLOCK ASSIGNMENTS AND JUMPERING . . . . . . . . . . . . . . . .

8-1

8.3.

CABLE COLOUR CODE AND CONNECTIONS . . . . . . . . . . . . . . . . . .

8-1

8.4.

FRONT CONNECTORS

....................................

8-2

8.5.

WIRING THE MDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-2

8.6.

LIGHTNING PROTECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-3

8.7.

MUSIC-ON-HOLD INTERFACE

..............................

8-3

8.8.

MODEM LINE UNIT (MLU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-4

8.9.

DTU AND LTU CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-4

8.10.

ASSEMBLING THE COAX CONNECTORS . . . . . . . . . . . . . . . . . . . . .

8-5

9710

Pages 7-1/7-10

Pages 8-1/8-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

(9412)

(9511)

0-5

9.

FINISHING INSTALLATION

9.1.

CONNECTING THE OPERATOR POSITION . . . . . . . . . . . . . . . . . . . .

9-1

9.2.
9.2.1.
9.2.2.

CPU - RS232C/V.24 INTERFACE CONNECTIONS . . . . . . . . . . . . . . .
PR300.10 Interface Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PR300.20 Interface Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-1
9-2
9-2

9.3.

V.24 INTERFACE CARD (VIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-3

9.4.

REMOTE INTERFACES HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . .

9-6

9.5.

IPH-A AND IPH-B INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-6

9.6.

INSERTING AND REMOVING ICs . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-7

9.7.

STRAPPING OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-8

9.8.
9.8.1.
9.8.2.
9.8.3.
9.8.4.
9.8.5.
9.8.6.
9.8.7.

ALARM UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DIL Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
V.24 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-8
9-8
9-10
9-12
9-13
9-13
9-14
9-14

9.9.

START-UP AND JOB COMPLETION . . . . . . . . . . . . . . . . . . . . . . . . . .

9-14

10.

DIL SWITCHES AND STRAP SETTINGS

10.1.

ANALOGUE LINE CIRCUIT-E

...............................

10-2

10.2.
10.2.1.
10.2.2.
10.2.3.
10.2.4.
10.2.5.
10.2.6.
10.2.7.
10.2.8.
10.2.9.
10.2.10.
10.2.11.

ANALOGUE TRUNK UNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-EM (2 Wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-EM (4 Wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-CH02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-ST26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-AS36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-IL01/IL03/IL04/IL13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-IL23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-LB12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-PSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-ST03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-3
10-3
10-6
10-9
10-10
10-12
10-14
10-15
10-17
10-18
10-21
10-24

10.3.
10.3.1.
10.3.2.
10.3.3.

DIGITAL TRUNK UNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTU-CA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTU-PR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTU-PU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-28
10-28
10-29
10-30

0-6

Pages 9-1/9-16

(9412)

Pages 10-1/10-60 (9710)

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.3.4.
10.3.5.
10.3.6.

DTU-PH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTU-BA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTX-I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-33
10-36
10-37

10.4.

LINE TERMINATING UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-40

10.5.
10.5.1.
10.5.2.

KEY TELEPHONE LINE CIRCUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KTLC01/02/03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KTLC-A/E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-43
10-43
10-45

10.6.
10.6.1.
10.6.2.
10.6.3.

METERING CIRCUIT AND SWITCH OVER UNIT . . . . . . . . . . . . . . . .
MC(E)-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MC(E)-F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MC(E)-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-50
10-50
10-50
10-51

10.7.
10.7.1.
10.7.2.
10.7.3.

MODEM LINE UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DIL Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2/4 Wire Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Detection Levels (Answertone) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-53
10-54
10-56
10-57

10.8.
10.8.1.

DIGITAL LINE CIRCUITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DLC-I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-58
10-58

11.

CONNECTION OF AUXILIARY EQUIPMENT Pages 11-1/11-12 (9412)

11.1.
11.1.1.
11.1.2.

PREPARATION OF THE DLC FOR A SOPHO-SET OR LAM . . . . . . .
Manual Assignment of DLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Malfunctioning of the DLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11-1
11-2
11-3

11.2.
11.2.1.
11.2.2.
11.2.3.

SOPHO SystemManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SOPHO SystemManager Configurations . . . . . . . . . . . . . . . . . . . . . .
SOPHO SystemManager Modules . . . . . . . . . . . . . . . . . . . . . . . . . . .
PE and OM Procedures Related to the Management Functions
and SSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11-3
11-4
11-6
11-7

INSTALLATION OF THE SOPHO-SUPERVISOR 30 . . . . . . . . . . . . . .
Hardware Installation of the SOPHO-SUPERVISOR 30 . . . . . . . . . . .
Projecting the SSV30 on a DOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Projecting the SSV30 Connected to a DLC . . . . . . . . . . . . . . . . . . . .
The SSV30 Password Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Projecting of Download Information . . . . . . . . . . . . . . . . . . . . . .
Projecting Transmission Characteristics . . . . . . . . . . . . . . . . . . . . . .
Steps for Changing the Default Language . . . . . . . . . . . . . . . . . . . . .

11-8
11-8
11-9
11-9
11-10
11-10
11-10
11-12

11.3.
11.3.1.
11.3.2.
11.3.3.
11.3.4.
11.3.5.
11.3.5.1.
11.3.5.2.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

0-7

12.

DIAGNOSTIC TEST

12.1.
12.1.1.
12.1.2.

CHECKING EXTERNAL LINES WITH TEST TELEPHONE . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Telephone Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12-1
12-1
12-3

12.2.

CHANGING OF TRAFFIC CLASSES WITH TEST TELEPHONE

....

12-3

12.3.

SWITCHING OFF/ON OF MFC GUARD TIMER . . . . . . . . . . . . . . . . . .

12-4

12.4.

ANALOGUE OPERATOR POSITION SELF TEST . . . . . . . . . . . . . . . .

12-4

12.5.

TERMINATING THE OPERATOR POSITION SELF TEST

12-9

13.

CLEARANCE OF FAULTS

Pages 13-1/13-84 (9707)

13.1.

ACTIONS IN CASE OF TOTAL SYSTEM FAILURE

..............

13-3

13.2.

ACTIONS IN CASE OF ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13-5

13.3.
13.3.1.
13.3.2.

USER COMPLAINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extension Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13-75
13-75
13-79

13.4.

ALARM CODES TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13-82

14.

REPLACEMENT PROCEDURES

Pages 14-1/14-8

(9412)

14.1.

COMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14-1

14.2.

TESTING SPARES HOLDINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14-1

14.3.

TIME OF REPLACEMENT

..................................

14-2

14.4.

RE-TEST AFTER REPLACEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14-2

14.5.

WRITING OF REPAIR FORM (REPAIR CARD) . . . . . . . . . . . . . . . . . .

14-2

14.6.

UPDATING PROJECT RECORDS . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14-3

14.7.
14.7.1.
14.7.2.
14.7.3.
14.7.4.
14.7.5.
14.7.6.
14.7.7.
14.7.8.
14.7.9.
14.7.10.

REPLACEMENT PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of AOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of DOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of the Alarm Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of VPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of the VIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of Peripheral Circuits . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of MC/MCE OR ESU . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of the PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14-3
14-3
14-4
14-4
14-4
14-4
14-4
14-5
14-5
14-6
14-6

0-8

Pages 12-1/12-10 (9412)

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

.........

9710

14.7.11.
14.7.12.
14.7.13.

Replacement of DLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of the IPHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacement of LTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.

POWER SUPPLY INSTALLATION

Pages 15-1/15-8

(9505)

15.1.

EARTH AND POWER CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . .

15-1

15.2.

POWERING THE TWO CABINET SOPHO iS3030 . . . . . . . . . . . . . . . .

15-2

15.3.
15.3.1.
15.3.2.
15.3.3.

INSTALLING THE TRANSFORMER / RECTIFIER UNIT . . . . . . . . . . .
Installing the 300 VA Transformer . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the 500 VA Transformer . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the 660 VA and 800 VA Transformers . . . . . . . . . . . . . . . .

15-3
15-3
15-4
15-4

15.4.

POWER CONSUMPTION AND FUSES . . . . . . . . . . . . . . . . . . . . . . . .

15-5

15.5.

EXTERNAL POWER SUPPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15-6

A.

FRONT CONNECTOR ASSEMBLY

A.1.

PREPARING THE 8X2 TWISTED CABLE . . . . . . . . . . . . . . . . . . . . . .

A-1

A.2.

PREPARING THE MULTI COAX CABLE . . . . . . . . . . . . . . . . . . . . . . .

A-1

A.3.

USING THE PIERCE INSERTION TOOL (Wire insertion) . . . . . . . . . .

A-1

A.4.

USING THE CLAMPING TOOL (Connector assembling) . . . . . . . . . .

A-3

A.5.

WHEN THE INSERTION TOOL GETS STUCK . . . . . . . . . . . . . . . . . . .

A-3

A.6.

RE-ADJUSTING THE INSERTION TOOL . . . . . . . . . . . . . . . . . . . . . . .

A-4

B.

S0 INTERFACE

B.1.

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-1

B.2.

P TERMINALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-1

B.3.

1TR6 TERMINALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-3

B.4.

S0 BUS RESTRICTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-4

B.5.

CABLING S0 BUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-5

B.6.

CONNECTORS AND PIN NUMBERING . . . . . . . . . . . . . . . . . . . . . . . .

B-9

B.7.

LINE POWERING

.........................................

B-11

B.8.

CONFIGURATION ASPECTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-12

9710

Pages A-1/A-4

Pages B-1/B-14

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

14-7
14-8
14-8

(9412)

(9412)

0-9

Z.

LOCAL INFORMATION (NOs)

Pages Z-1/Z-2 (9412)

Diagrams 100 (Common Info)
100
110
120
121
122
123
130
131
140
141
150
152
155
160
161
162
165

PWB Front Connector Identities . . . . . . . . . . . . . . . . . . . . . . . .
Using the Antistatic Bracelet . . . . . . . . . . . . . . . . . . . . . . . . . .
Colours of Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Stripping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting and Removing of a Front Connector . . . . . . . . . . . .
Flat Cable Connecting and Disconnecting . . . . . . . . . . . . . . .
Using Wiring Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fixing Coax Connector to Cable . . . . . . . . . . . . . . . . . . . . . . . .
Inserting an IC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing an IC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assembling of Floorstand 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assembling of Floorstand 1.5 . . . . . . . . . . . . . . . . . . . . . . . . . .
Locating the Two Cabinet SOPHO iS3030 . . . . . . . . . . . . . . . .
Pierce F122 Connector Insertion Tool Parts . . . . . . . . . . . . . .
Connecting the 8x2 Twisted Pair Cable to F122 Connector . .
Connecting the 8x2 Coax Cable to F122 Connector . . . . . . . .
Using the F122 Connector Assembly Tool . . . . . . . . . . . . . . .

A5
A5
A5
A5
A5
A4
A4
A4
A5
A5
A5
A5
A5
A5
A5
A5
A5

(9209)
(9412)
(9412)
(9412)
(9412)
(9412)
(9209)
(9412)
(9209)
(9209)
(9412)
(9412)
(9412)
(9209)
(9209)
(9209)
(9209)

A5
A5

(9412)
(9412)

A5
A5
A5

(9412)
(9412)
(9412)

A5
A5

(9412)
(9209)

A5
A5
A5
A5

(9412)
(9412)
(9412)
(9412)

A5
A5

(9412)
(9412)

Diagrams 300-400 (Typical SOPHO iS3010/3030)
300
310
315
316
317
318
319
320
321
323
324
325
326

0-10

Removing the Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical Shelf Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fastening of the PWB lock in the EMC Cabinets
for SOPHO iS3010/3030 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling of the EMC Cabinets for SOPHO iS3010/3030 . . . . . .
SOPHO iS3010 EMC Cabinet without Rectifier Unit . . . . . . . .
Installing the Trunk Filters for ATU-SS02 and
ATU-ST02 (EMC Cabinet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Mains Cable and the EBU in a NON-EMC Cabinet
Connecting and Mounting the EBU in an EMC Cabinet /
Mounting V.24 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
300 VA Transformer Connecting Diagram . . . . . . . . . . . . . . . .
500 VA Transformer and Rectifier Unit Connecting Diagram (1)
660 VA and 800 VA Transformer and Rectifier Unit
Connecting Diagram (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
500 VA Transformer and Rectifier Unit Connecting Diagram (2)

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

327
330
331
335
340
341
350
351

660 VA and 800 VA Transformer and Rectifier Unit
Connecting Diagram (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Routing Cables and Earth Connection SOPHO iS3010 (non-EMC cabinet) . . . . . . . . . . . . . . . . . . . . . .
Routing Cables and Earth Connection SOPHO iS3030 (non-EMC cabinet) . . . . . . . . . . . . . . . . . . . . . .
Earth Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jumpering MDF - SOPHO iS3010 . . . . . . . . . . . . . . . . . . . . . . .
Jumpering MDF - SOPHO iS3030 . . . . . . . . . . . . . . . . . . . . . . .
Installing the PMC-PMC cable and the Mains Cable
in an EMC Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the PMC-PMC cable in a NON-EMC Cabinet . . . . . .

A5

(9505)

A5

(9412)

A5
A5
A5
A5

(9412)
(9209)
(9412)
(9412)

A5
A5

(9209)
(9209)

A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5
A5

(9304)
(9209)
(9209)
(9209)
(9209)
(9304)
(9209)
(9209)
(9209)
(9209)
(9209)
(9209)
(9209)
(9209)
(9209)
(9209)
(9209)
(9412)
(9412)
(9209)

Diagrams 400-500 (Cabling and MDF)
400
401
402
403
404
405
420.1
420.2
420.3
421
422
423
424
425
430
431
436
440
450
460

9710

Line Circuit Connections at MDF Blocks . . . . . . . . . . . . . . . .
Analog Trunk Circuit Connections at MDF Blocks . . . . . . . . .
MC / DTU / LDC Connections at MDF Blocks . . . . . . . . . . . . . .
MCE Connections at MDF Blocks . . . . . . . . . . . . . . . . . . . . . . .
ESU Connections at MDF Blocks . . . . . . . . . . . . . . . . . . . . . . .
PMC, ACC and KTLC Connections at MDF Blocks . . . . . . . . .
DLC / LDC / DTU / LTU Cabling . . . . . . . . . . . . . . . . . . . . . . . . .
DTU-CA/PR/PU and LTU Interface Connections . . . . . . . . . . .
DTU-PH and LTU Interface Connections . . . . . . . . . . . . . . . . .
ATU / MC Interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU / MCE Interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATU-G ESU Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ESU / ATU / ALC Interconnections . . . . . . . . . . . . . . . . . . . . . .
IPH-A - IPH-B Interconnections . . . . . . . . . . . . . . . . . . . . . . . .
MLU - MODEM - MDF Cabling . . . . . . . . . . . . . . . . . . . . . . . .
MLU - MODEM for MODEM Pool to MDF . . . . . . . . . . . . . . . .
PSU-F (- ATU-LB) Interconnections . . . . . . . . . . . . . . . . . . . . .
Overvoltage Arrestor and Cartridge . . . . . . . . . . . . . . . . . . . . .
Coaxial Connector for MDF . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Connection Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

0-11

AMENDMENTS
The manual update from 9412 to 9505 concerns the following items:
CHAPTER/
SECTION
DIAGRAM

DESCRIPTION

Chapter 0

Administrative changes.

Chapter 8

Section 8.7.: Music-on-Hold figure changed.

Chapter 10

Section 10.3.3.: DTU-PU strap/DIP switch description extended.
Section 13.2.:

Alarm code 1013 type 10 minor change.
Alarm code 1040 type 50 text added.
Alarm code 1042 type 10 text added.
Alarm code 1048 text added.

Chapter 15

Figure 15.2.:

Vertical key changed into 191.

Diagram 327

Wire colours added.

Chapter 13

The manual update from 9505 to 9511 concerns the following items:
CHAPTER/
SECTION
DIAGRAM

DESCRIPTION

Chapter 0

Administrative changes; amendments sheet.

Chapter 8

Section 8.7.: Music-on-Hold description and figure changed.

The manual update from 9511 to 9701 concerns the following items:
CHAPTER/
SECTION
DIAGRAM

DESCRIPTION

Chapter 0

Administrative changes.

Chapter 10

Table 10.2.2.b corrected.

The manual update from 9701 to 9707 concerns the following items:
CHAPTER/
SECTION
DIAGRAM

DESCRIPTION

Chapter 0

Administrative changes.

Chapter 10

Tables 10.2.11 and 10.2.12 corrected.

Chapter 13

Section 13.2.: Alarm codes 1043 and 1044 added.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

0-13

The manual update from 9707 to 9710 concerns the following items:
CHAPTER/
SECTION
DIAGRAM

DESCRIPTION

Chapter 0

Administrative changes.

Chapter 10

Section 10.3.4.: DTU-PH info enhanced.

0-14

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

1.

SOPHO iS3010/3030 CHARACTERISTICS

The SOPHO iS3010 and SOPHO iS3030 are Integrated Services Private Branch
Exchanges (ISPBXs). The maximum number of user ports for each exchange is
respectively:
• SOPHO iS3010
This is a stand alone iS3010 cabinet with 96 user ports.
• SOPHO iS3030
SOPHO iS3030 is available in two versions. These are the single cabinet system and the
two cabinet system.
The single cabinet system contains 256 user ports with additional 32 dedicated user ports
for digital connections only.
The two cabinet system exists of one master and one slave cabinet. Master cabinet
provides 256 user ports with additional 32 dedicated user ports for digital connections only.
Slave cabinet provides 256 user ports with additional 64 dedicated user ports for digital
connections only. Maximum amount of ports is 512 + 96 dedicated ports for digital
connections only.
The EMC charactersitics of the EMC improved cabinets for The Netherlands comply the
EMC standards EN 55022 and EN 55101/1-6, class B. The EMC specifications of the
cabinets for Germany are according to VDE 0839, VDE 0847, VDE 0876, VDE 0877, VDE
0878, FTZ 12 TR 1/6.87, FTZ 12 TR 2/9.88.
In all systems three main functions can be distinguished. These functions are functionally
grouped into a:
- Control Section (housed within the CPU and PMC boards);
- Switching Section (housed within the PMC board);
- Peripheral Section (Peripheral Circuit boards).
The Control Section is divided over the Central Processing Unit (CPU) and the Peripheral
Module Controller (PMC) boards. The CPU contains the Central Processing part (controlled
by a Motorola 68302 microprocessor). The Central Processor does the overall control of the
ISPBX.
The PMC (controlled by a Z80 microprocessor) contains the Peripheral Processing Unit
(PPU). The Peripheral Processor does the real time low level control of the hardware in the
Peripheral Modules (PMs). The PPU is controlled by the CPU on a higher level.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1-1

Other main functions housed within the PMC are:
- Switching Section;
- Tone Sources;
- Receivers and Senders of Tones for Keytone Dialling.
The communication between the CPU and PPU takes place via an Internal Message
Protocol (IMP) channel, via the backpanel.
To route telephone traffic from one extension to another the Switching Section is used. This
Switching Section consists of time-switch ICs located on the PMC board. These ICs provide
a non-blocking switching system throughout the ISPBX.
The Peripheral Module hardware may contain various Peripheral Circuits (PCTs) for
connection to analogue and digital telecommunication lines, including taxmetering circuits
for call-accounting purposes. It may also contain Emergency Switchover Units to directly
connect designated telephones to outside lines in the event of a system failure.
The two cabinet SOPHO iS3030 comprises one master and one slave cabinet. The CPU in
the master cabinet controlls both the PPUs in the master and slave cabinet.
The connection between the master and slave Switching Section is non blocking and it is
accomplished by connecting the two PMCs using two special PMC-PMC cables.
The shelves within SOPHO iS3030 may contain PCT boards with standard PM bus
interface, however some board positions in the lower shelves are dedicated for digital PCTs
only. Refer to the Hardware Configuration Manual for the configuration rules.
Each cabinet is provided with its own Power Supply Unit.

1.1.

SYSTEM ASSURANCE TEST SOFTWARE

Most of the circuit boards in the ISPBX are tested in sequence under the control of a
software program, known as System Assurance (SAS); this is called cyclic testing. In
addition to this some circuit boards are able to signal faults themselves without being under
control of the System Assurance software. If a fault is detected by cyclic testing or if a fault
is signalled by the circuit board itself then this fault will be reported to the System
Assurance program and the details stored in a history buffer, which can be subsequently
read out. A fault report contains a code identifying the type of fault, the hardware address of
the faulty circuit, time of last detection, number of times the fault was detected, plus
information to establish the reason for the fault. Depending on the type of fault an alarm
may be generated.

1-2

DB-A 9150e-35
© Philips Communication Systems B.V.1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

Faults which occur in the ISPBX may be corrected in a number of ways:
- Roll-back

: If a circuit was put in a not defined state by some transient event
the System Assurance software takes the circuit out of service
and then brings it back in. This may correct the fault.
- Isolation
: If the fault is affecting the operation of system parts then the
software may take the faulty circuit out of service permanently,
and put it in the ”autonomously blocked” condition.
- Accelerated testing : After a circuit has been put in the ”autonomously blocked”
condition the software test cycle is accelerated to see if the fault
has disappeared.If the fault is not rediscovered, the circuit
concerned is automatically returned to service.
- Engineer action
: A maintenance engineer may take a circuit out of service before
removing the appropriate circuit board for inspection and
replacement.

1.2.

PROJECT DATA

A SOPHO ISPBX can be adapted to the customer's wishes. This customizing is done with
help of procedures that define the project dependant data. There are two catagories of
project data:
- Project Engineering (PE) data;
- Operational Maintenance (OM) data.
Together these two types of project data form the so called POM database. This POM
database determines the way the system works.
During initial start-up procedure first the POM database should be loaded into the POM
Flash EPROM database memory. Flash EPROMs are electrically programmable ROMs
without removing them from the board. To load the Run Time POM Database RAM memory
with the required POM database the coldstart procedure should be executed.
POM database should be loaded as one file into the POM Flash EPROM database
memory. POM database can be stored in the ISPBX at one time and executed at another. It
is possible to store in an operational ISPBX a second set of POM data, while the
operational Run Time database runs on a different set of POM data. The latest set of POM
data can be loaded in the Run Time POM database by performing a coldstart procedure.
Using a (Remote) Maintenance PC, within a running system a part of the PE data of the
POM database can be changed on-line. Effectuation of the changed PE data is done
afterwards by performing a so called warmstart.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1-3

The remaining part of the PE data of the POM database can only be changed off-line. First
the running POM database should be backed up into the POM Flash EPROM memory.
Next the contents of the POM Flash EPROM memory should be transferred to the
(Remote) Maintenance PC. Using a text editor, which produces straight ASCII files, the
POM database (PE and OM) can be changed. After changing, the POM database should
be stored in the POM Flash EPROM memory. Effectuation of the changed POM database
is done afterwards by performing a so called coldstart. During the coldstart procedure the
POM database is copied into the Running POM database RAM.
PE data includes:
-

Exchange properties (system and operator options etc.);
System time limits (extension, operator, night service etc.);
Number analysis (external numbers, operator access code etc.);
Tone and ringing rhythms (continuous, single burst etc.);
Alarm level definitions (major, minor alarm etc.);
Configuration data (extension types, trunk line types etc.);
Variable signalling data (on-hook recognition time, digit pulse lengths etc).

The ADF part (OM commands) of the running POM database can be changed on-line. OM
data can be loaded and updated at any time. It includes:
-

Extension numbers;
Traffic classes, definitions and assignments;
Facility classes;
Abbreviated numbers;
Night service;
External numbering scheme;
Operator answering priorities;
Trunk group and line numbers;
Circuit conditions.

If required it is possible download an ADF file only. This ADF file can be executed using the
OM command SUBMIT. This command should be used for loading an ADF file on-line into
the running POM database.
The commands to call up the procedures that load the OM-data into the POM database are
coming from one of the following items:
- A file called Administrative Data File (ADF), loaded with help of a Maintenance PC;
- The Operator's Console, loaded in an interactive way;
- A dedicated User Terminal, also loaded in an interactive way.

1-4

DB-A 9150e-35
© Philips Communication Systems B.V.1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

The contents of the ADF is prepared in accordance with a customer completed
questionaire. The ADF can be edited on a PC with any text editor program that produces
straight ASCII files.

1.3.

RETRIEVING THE RUNNING POM DATA

SSW 300 offers the possibility to make a back-up of the complete running POM data base,
using the (Remote) Maintenance PC.
In case the final running POM database might be lost, due to any reason, one should make
always a back-up of the running POM data base, using the Maintenance PC. Backup of the
POM database can be downloaded during initial start-up procedure.
Procedures to make a backup of the running POM data base are given in chapter 4 and the
OM Commands Manual.

1.4.

DATA PACKAGE STORAGE

The CPU and PPU data package memory parts contain also electrically programmable
ROMs called Flash EPROMs. Using the Local Maintenance PC the data package is
downloaded into the CPU and PPU Flash EPROM memory. If a package upgrade is
required the new CPU and/or PPU software can be easily downloaded.
A CPU package can be downloaded at any time. A PPU package can only be downloaded
if the CPU package already has been downloaded. If only the PPU package should be
upgraded within a running system it can be done without downloading the CPU package
first, provided the present CPU package is correct. For detailed information refer to chapter
4.
For SSW 300 and up the CPU and PPU software is supplied on 31/2 inch diskettes.

1.5.

POWER FAIL PROTECTION

A battery charge part in the Power Supply Unit (PSU) is designed to convert 48 V to 4.6 V
to maintain a charge across an Emergency Battery Unit (EBU). The EBU ensures that the
data contained in the various RAMs (including Run Time Database RAM) is kept intact in
the event of a power supply interruption. It will keep the contents of the RAMs intact for at
least 96 hours if the primary power fails.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1-5

1.6.

SYSTEM STARTS

There are three types of system starts: coldstart, warmstart and restart.
A coldstart is activated by the OM command COLDST. During the coldstart procedure the
POM database is copied from the Flash EPROM memory into the Running POM database
RAM. As soon as loading starts, data relevant to the Peripheral Processor is copied into it's
memory.
A warmstart is activated in the event of a Peripheral Processor failure, a Peripheral
Processor to CPU communication failure, a PSU failure or too many restarts. Another way
of invoking a warmstart is by the associated OM command or switching off and on again the
power (EBU must be present).
A restart occurs when a watchdog circuit that guards the processes times out; it may affect
one or two calls. A restart does not affect the Peripheral Processor, thus making it easy to
recover from minor problems. If a second restart is needed within a short period of time, a
warm start is carried out instead.

1.7.

COLD / WARMSTART CHARACTERISTICS

A coldstart always generates an alarm. A warmstart only generates an alarm if a certain
integration level is reached. If the system includes Emergency Switchover Units (ESUs),
designated telephones are directly connected to the public exchange lines under these
conditions, bypassing the system. Normally this situation continues for about 1 minute after
the completion of a cold or warmstart. If the loopguarding process on the ESU detects a
seized line, indicating a call on that line, the switch back to normal will be postponed untill
the call has been finished.

1.8.

TELEPHONE SETS

Impulse, keytone and feature telephones can be connected to the system. Keytone types
are standard. If it is required to use impulse types, they need not to be specified in the PE
data. However, also when keytone telephone sets are used receivers of keytone (RKTs)
should be specified in the project data. Providing that these measures have been taken,
either telephone type can be connected; the system automatically distinguishes between
the two.
Not all telephones are fitted with enquiry buttons. The enquiry facility can, however, also be
realised by a hook-flash, dialling '1' or, if fitted, by pressing a calibrated loop button; the PE
data must be set accordingly.

1-6

DB-A 9150e-35
© Philips Communication Systems B.V.1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

1.9.

TRUNK UNITS

Various analogue and digital trunk circuits can be used. In PE data the type of signalling
plan must be specified to adapt the trunk circuit to local requirements.
Trunk circuits can be assigned to trunk line groups. This must be specified in the OM data.
Trunk lines are cyclically selected for outgoing calls; there is no fixed starting point.
The distant exchange determines the use of incoming trunk lines. The system always tries
to accept a seized incoming line ; it treats in accordance with the PE data.
Trunk units can be equipped to directly connect designated telephones to the exchange
lines in the event of a system failure. The telephones concerned must be compatible with
the (public) exchange (impulse or keytone dialling).
Trunk circuits can be connected to taxmetering circuits (MCs). Where this is the case they
must be specified in the PE data, otherwise the system will not recognize them.

1.10.

EXTERNAL CLOCK SYNCHRONIZATION

The clock for the time switches of the ISPBX is located on the PMC board in the master
cabinet. This clock can be synchronized with an external clock by connecting the clock
reference output of the digital trunk termination board (DTU) to one of both clock
synchronisation input of the PMC-MC. Which clock synchronisation input is to be taken as
the synchronisation input is projectable. In case the projected clock input falls out, due to
any reason, then automatically the other input is selected, if any. If there is not a second
synchronisation clock available, then the internal system clock is selected.
An alarm will be generated as soon as the clock circuit on the PMC-MC has been able to
synchronize with the external clock, or if synchronization is lost.
The synchronization of the PMC-MC with the external clock can continuously be watched
by OM procedure DICLKS (9002).

1.11.

TONE GENERATION AND RHYTHMS

The PMC contains a 16K x 8 RAM to store 32 tones like dial tone, busy tone, ticker tone
etc. These tones are used by the PCTs, each tone is made of 512 samples maximum.
From these 32 tones by default 16 tones are dedicated for DTMF.
The contents of the tone RAM is filled during start up and can be defined by project
engineering procedures. These procedures define the tone frequency, the tone level, and
the on/off rhythm of the tone.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1-7

1.12.

OPERATOR POSITION

There are two types of Operator Positions:
- Analogue;
- Digital.
The Operator Positions are connected to an optional daughter board on the Peripheral
Module Controller board (PMC). These piggyback mounted daughter boards are called:
- Analogue Operator Card (AOC);
- Digital Operator Card (DOC).
Two analogue operator positions can be connected to the AOC simultaneously, one digital
operator position can be connected to the DOC. It is not possible to connect both AOC and
DOC boards at the same time.
Each AOC connection includes the following:
- Power
- Speech
- Data

: 48 V D.C;
: 4-wire speech circuit to connect a telephone handset;
: 2400 bits/s 4-wire data circuit for keyboard/display.

Two types of analogue Operator Position are available, these are:
- SOPHO-SUPERVISOR 20;
- SOPHO-SUPERVISOR 50.
For using the SOPHO-SUPERVISOR 20 refer to the Operator Manual, DB-A 9120. For
using the SOPHO-SUPERVISOR 50 refer to the SOPHO-SUPERVISOR 50 User Guide.
The digital Operator Position is called the SOPHO-SUPERVISOR 30 and uses a 2B+D
interface, hence can either be connected to the DOC or to a Digital Line Circuit (DLC). If the
SOPHO-SUPERVISOR 30 is connected to the DOC, it can be powered by the DOC. If it is
connected to the DLC-C/D, it can be powered by an additional Line Driver Card (LDC) that
can be connected in series with the DLC-C/D. If it is connected to the DLC-U no additional
Line Driver Card (LDC) is required, because DLC-U also provides line power for the
SOPHO-SUPERVISOR 30. For using the SOPHO-SUPERVISOR 30 refer to the SOPHOSUPERVISOR 30 User Guide.
Both types of Operator Position contain a self-test program to test its keyboard and its
display indicators.

1-8

DB-A 9150e-35
© Philips Communication Systems B.V.1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

1.13.

DAY SERVICE - NIGHT SERVICE

Day service is the system condition in which calls needing assistance are routed to the
Operator Position(s). Night service is the system condition in which calls needing
assistance are routed to a designated night service extension(s).
The Operator Position can be in one of the following conditions:
- "Present" and capable of providing call assistance.
- "Present" but in the Administrative Mode (AM), whereby OM data can be displayed. This
mode can only be entered when the console is "present" or the operator is talking to one
party only, with no other party on hold. If there is no speech connection, OM data can
also be changed.
- "Absent" but in the AM mode, where it is still possible to change and display OM data.
- "Absent" and non-operational.

1.14.

ALARM SIGNAL DISTRIBUTION

Alarms are given in the form of visual and audible indications.
The visual indications are given by means of major and minor alarm lamps on the analogue
operator switch board or on the external Alarm Unit. On the digital operator posts an alarm
is shown in display as a triangle. On the Maintenance PC screen an active alarm is
displayed in inverted video.
Visual alarms can only be reset by removing the cause of the alarm or resetting it with the
appropriate OM command.
The audible alarm indications are given by means of a buzzer on the following devices:
- Analogue operator position (SOPHO-SUPERVISOR 20 and 50);
- Digital operator position (SOPHO-SUPERVISOR 30);
- Alarm unit.
An audible alarm on the operator position and on the alarm box, can be silenced with one of
the buttons.
The OM command REROUT (6026) lets you suppress or allow the alarm signalling to the
operator.
The alarms System down, Major alarm and Minor alarm are also presented on the front
connector FAA of the CPU (V.28 levels).

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1-9

1.15.

ALARM UNIT

The alarm unit is an external device carrying five LEDs with five relay contacts connected
parallel, two switches, a buzzer, a CANS relay contact and two alarm inputs. The alarm unit
can directly be connected to the CPU board, by means of a V.24 connection. The LEDs on
the alarm unit signal:
-

Power on Alarm Unit available;
Major Alarm;
Minor Alarm;
System Down;
Emergency Bypass active.

The functions of the switches are to:
- Reset the buzzer on the alarm unit;
- Activate the Emergency Bypass function.
In the alarm unit a connection to an external CANS relay can be made. Also two alarm
inputs can be monitored by the alarm unit. The status of these external alarms is sent to
the CPU. Such an alarm can result in a major or minor alarm, depending on the project data
settings in the POM database.

1.16.

POWER SUPPLY FOR SOPHO iS3010/3030

The system can be supplied from the mains (110, 127, 220, 240 V AC at 48-62 Hz) or from
an external 48 V DC supply, like a rectifier or a battery (positive ground!!). Because the
external 48 V DC supply is not supported by the Philips Communication Systems
organisation, the combination of the SOPHO iS3010/3030 and external power supply is not
tested for EMC and safety specifications. The PABX is tested only with its build in AC mains
supply.
There is no way of changing the input voltage of the mains transformer, hence each mains
voltage requires its own transformer.
Each system is fitted with a mains transformer and a Power Supply Unit (PSU). The
following transformers are available:
-

300 VA for the SOPHO iS3010;
500 VA for the SOPHO iS3010/3030;
660 VA for the SOPHO iS3010/3030, one for each cabinet;
800 VA for the SOPHO iS3030, one for each cabinet.

1-10

DB-A 9150e-35
© Philips Communication Systems B.V.1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

The PSU has it's own place in the exchange, and gets it's supply through the backpanel.
Each mains transformer has it's own place in the mains transformer compartment, and is
connected to the backpanel. Depending on the total dissipation of the PSU a separate
rectifier is placed in the transformer compartment, instead of in the PSU. The Emergency
Battery Unit (EBU) is connected with the backpanel in the rear side of the power
compartment unit, to two fastons marked 'plus' and 'minus'. Also Battery Supply may be
connected to the back panel instead of the mains transformer unit. The fast-on connectors
marked with one hole (=negative voltage) and two holes (=positive voltage) then have to be
used to connect the external 48 V DC box supply.
There are five -48Vdc outputs on the backpanel supplied by the PSU, protected by five
electrically recoverable fuses. LEDs are connected adjacent to each fuse in the PSU. If a
LED is alight, the corresponding fuse is blown. At the bottom side of the PSU a so called
OK LED is mounted. When this LED is alight, all the internal PSU voltages (5V, 12V, 48V)
are within their specified ranges.
Chapter 15. gives more detailed information about powering the SOPHO iS3010/3030.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

1-11

1-12

DB-A 9150e-35
© Philips Communication Systems B.V.1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

2.

SERVICE CONDITIONS

Three system services can "own" a PCT:
- Call Processing (CP) for telephony;
- System Assurance (SAS) for testing;
- Operational Maintenance (OM) for online maintenance.
The System Assurance service makes use of two types of ownership, called SAS1 and
SAS2. Only one service can own a PCT at any one time. Ownership is granted on a priority
basis. The priority levels from high to low are:
-

OM;
SAS1;
CP;
SAS2;
NO.

If a service no longer requires the PCT it withdraws ownership, by handing it over to No
Owner (NO), thus making it available for one of the other services.
PCTs can be set to one of the following circuit conditions:
-

INS
OUT
ABL
NIN

:
:
:
:

IN Service;
Out of Service;
Autonomously Blocked;
Not INstalled.

Ownership state and circuit conditions are described in the next sections. The combination
of ownership and circuit condition provides a PCT with its "service condition". All possible
service conditions are given in section 2.4.

2.1.

CIRCUIT CONDITIONS

• INS
The normal operational condition is INS. PCTs in this condition are available for call
processing and are accessible for tests by SAS.
• OUT
PCTs in circuit condition OUT are only available to OM. As long as at least one PCT is in
the OUT condition, the CIRCUIT BLOCKED indication is given on all Operator's Positions
in the condition "present"; the CIRCUIT BLOCKED alarm on the MPC is shown in
inverted video.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

2-1

The CIRCUIT BLOCKED indications are also active if the automatic system test is
switched off by means of an OM procedure, or if the emergency switch over function is
activated.
A PCT absent alarm is reset when a PCT is set to OUT.
• ABL
The Autonomously Blocked (ABL) condition is assigned to faulty PCTs by the system
assurance service to prevent them being seized for calls and possibly degrading system
service.
• NIN
The Not Installed (NIN) condition should be assigned to PCTs which do not physically
exist in the exchange and also to PCTs not connected to lines, in an exchange with 32
Analogue Trunk Unit (ATU) PCTs and only 30 external lines for example.

2.2.

CHANGING CIRCUIT CONDITIONS

The following OM procedures are used to change and display the circuit conditions of
PCTs.
-

SETINS
SETOUT
SETNIN
DISERV

2.3.

/ 7010 to change circuit condition to INS;
/ 7012 to change circuit condition to OUT;
/ 7014 to change circuit condition to NIN;
/ 7030 to display service condition.

OWNERSHIP

• NO
No Owner. If the PCT condition is in service (INS) and no owner retains the PCT, a
request for ownership from either CP, SAS or OM will always be granted. If the circuit is
in the OUT, ABL or NIN condition, ownership can be granted to OM or SAS.
• OM
If the condition of a PCT is going to be modified by an OM procedure, OM will request the
ownership in order to prevent complex interactions with other services during the
transition of one circuit condition to another.
• SAS1
SAS1 ownership is used during an accelerated version of the test loops which are carried
out on PCTs in the various circuit conditions.
SAS1 ownership is also set when a PCT is unobtainable for some reason e.g. PCT board

2-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

removed or not activated, master PCT not activated or present, line blocked by distant
exchange, terminal removed etc.
• SAS2
SAS2 ownership is used during a test loop carried out on all PCTs in circuit condition INS
in an operational system.
Some SAS processes use the SAS2 owner during transitions.
• CP
As a telephony system is intended to perform telephony functions, Call Processing is the
most frequent owner of a circuit.

2.4.

POSSIBLE SERVICE CONDITIONS

The various possible service conditions are summarized in the following table:
CIRCUIT
CONDITION OWNER CODE

MEANING

NO
OM
SAS1

00
04
03

CP
SAS2

02
01

Normal operational condition (Idle).
Transitional condition during OM.
- Condition when PCT has been blocked by distant exchange or
SOPHO-SET or LAM not connected;
- Condition when PCT is physically absent;
- Condition during manual SAS test;
- Transitional condition (23->03->00);
- Condition when PCT assists (without being test subject) in any SAS
owned test.
Normal operational condition (Call setup, Busy etc.).
Condition during test owned by SAS2 or during transitional conditions.

OUT

NO
OM
SAS1

10
14
13

PCT has been set to OUT.
Transitional condition during OM.
Condition during test loop

ABL

NO
OM
SAS1
SAS2

20
24
23
21

PCT has been autonomously blocked for operation due to malfunction.
Transitional condition during OM.
Condition during test loop (accelerated automatic test on ABL PCTs).
Transitional condition (01->21->20).

NO

30

SAS1
OM

33
34

PCT not physically present or “surplus”; or may not be put into service
after a warmstart when other related hardware is not operational; or no
DNR or route line number assigned.
Condition during manual test loop.
Transitional condition during OM.

INS

NIN

Table 2.1. PCT Service Conditions.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

2-3

The Codes mentioned in table 2.1 have the following meaning:
- First-digit

: 0
1
2
3

=
=
=
=

INS
OUT
ABL
NIN

- Second-digit : 0
1
2
3
4

=
=
=
=
=

NO
SAS2
CP
SAS1
OM

2.5.

PERIPHERAL MODULE SERVICE CONDITIONS

The Peripheral Processor uses circuits and software to control the Peripheral Circuits
(PCTs) in the shelves. These circuits and associated software form the control section of
the Peripheral Module (PM). The control section can be in one of the service conditions
which are given in table 2.2.
CIRCUIT
CONDITION OWNER CODE MEANING
NO
OM
NO

00
04
10

Normal operational condition.
Pre-operational or restarting condition.
Out of service.

ABL

NO
SAS1

20
23

Control Section not connected or no valid package available.
Control Section connected and cannot become operational.

NIN

NO
OM

30
34

Control Section not installed.
Reinitialisation condition.

INS
OUT

Table 2.2. Control Section Service Conditions.

2-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

3.

MAINTENANCE

3.1.

CONTROL SECTION TESTING

The control section hardware is tested properly before leavining factory and therefore not
tested during operation. However, during system start up the CPU and PPU PROM
contents is tested on errors.

3.2.

SWITCHING SECTION AND PERIPHERAL SECTION TESTING

There are two methods of testing the hardware of the switching section and PM:
automatically and manually.

3.2.1.

Automatic Test

The automatic test can be subdivided into the test-loop carried out on Autonomously
Blocked circuits (ABL) and the test loop carried out on In Service Circuits (INS). These tests
commence from the moment the power is applied.
If, during the INS test loop, a fault is found the circuit condition of the PCT concerned is set
to ABL and an alarm report will be stored in the history buffer ("PCT fault"). In this way the
PCT is blocked for call processing.
The ABL test loop now picks up the ABL-PCT and keeps checking it periodically. As soon
as no fault is found the PCT is made available for call processing again. The PCT fault
alarm is withdrawn.

3.2.2.

Manual Test

The Manual Test does a part of the automatic test and is activated by OM-procedures. In
table 3.3 the applicable tests are given. The Manual Test is activated from the Maintenance
PC , from which also the fault reports can be read out.
PCTs to be manually tested can be set to circuit condition INS, OUT or NIN.
DLCs can only be tested manually in the circuit condition NIN.
A fault discovered in a PCT does not cause its circuit condition to change. It is, however,
reported (alarmed). An alarm is also given if a test cannot be carried out.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

3-1

PCT
TEST

AUTOMATIC
TEST

MANUAL
TEST

ABL
TEST

Circuit
condition

INS
TEST

OUT
TEST

NIN
TEST

ABL

INS

OUT

NIN

Figure 3.1. PCT Test Summary.

The Manual Test can be run in an operational system, although a PCT cannot be used for
telephony while it is being tested.
AUTOMATIC TEST
HARDWARE

LOOPBACK
TEST 1)

FUNCTIONAL
TEST

PMC:
- Break in Circuit (BIC)
- Receiver Dialtone (RDT)
- Receiver Keytone (RKT)
RST-KD:
- Receiver Keytone (RKT)
- Receiver Dialtone (RDT)
RST-IMOM:
- Multi frequency receiver (MFC)

MANUAL CONTROLLED
TEST
LOOPBACK
TEST 1)

FUNCTIONAL
TEST

x
x
x

x
x
x

x
x

x
x

x

x

ACC / ALC:
- All PCTs

x

x

x

ATU:
- All PCTs

x

x

x 2)

Table 3.1. Survey of Tests.

Notes: 1) Loopback test: also referred to as CODEC test.
2) Not all ATU types can be tested, because the hybrids of not all ATU types can
be forced in a state that they echo an acoustical signal.

3-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

3.3.

SWITCHING SECTION AND PM TEST ROUTINES

Loopback tests are performed with the aid of an SKT and an RKT. The digits sent are
looped back by the PCT under test, by putting the hybrid in unbalance. When the hybrid is
in unbalance the acoustical signals are echoed.
During the Loopback test, the control hardware for the associated CODEC is fully tested.
In functional tests, where possible, a sending unit is linked through the switching network
with a compatible receiving unit and together completely functionally tested (SDT RDT, SKT
RKT, MFC sender MFC receiver).
If a fault is discovered, the unit under test is linked to another one and tested again to
determine which of the two originally connected units is defective.
Example: A CODEC test of PCTx to be tested is tested with a randomly chosen RKT, e.g.
RKT1. The processor instructs PCTx to successively return all digit codes. The
codes are received by RKT1. If RKT1 fails to pass on a digit to the processor, or
passes it on incorrectly then PCTx is tested again, e.g. with RKT3. If the fault
reoccurs, PCTx is considered as the faulty unit.
The sequence in which PCTs of a given type are tested is equal to the sequence in which
the hardware addresses have been input during PE data load. The sequence algorithm
applies equally to the Automatic INS test, the Automatic ABL Test and the Manual Test.
The circuits to be tested by the manually initiated test should be put into a so called 'target
list' by an OM procedure. After this, the test should be started by another OM procedure.
Finally the test results can be found in the Alarm Buffers.
After a cold or a warm start the automatic test cycle begins again with PCTs of the first type
specified.

3.4.

MONITORING ROUTINES

In addition to the previously mentioned hardware tests, the software executes a number of
checks which enable special situations to be recognized, including:
- PCT permanently busy/idle. A PCT which remains busy, or idle for more than a specified
time, is reported (an alarm is given).
- Masterboard not present or activated. This situation is only monitored when a
masterboard is specified by the associated project engineering procedure.
- Line blocked by distant exchange.
- No SOPHO-SET or LAM connected.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

3-3

- Dial tone time out on a trunk.
- MASTER PCT of PCT not activated.
- Board physically absent or not activated. When a board is removed from the system, it is
recorded almost immediately. Removal of a board with a PCT in circuit condition INS will
generate an alarm.
- An excessive number of unexpected events, arriving from the PM, offered to the garbage
buffer. These are events which:
. Cannot be injected by system users;
. Do not point directly to a routine in the system, and could indicate a software error.
The garbage buffer is slowly leaking. Each day a message is deleted. If more messages
are entered than deleted, overflow is detected. After this detection the buffer is blocked,
hence no more messages will be accepted, and an alarm is generated.

3.5.

ALARM GENERATION

Some faults generate an immediate alarm, others do not generate an alarm unless a fault
reoccurs within a given time period. This is determined in the History Buffer.

3.5.1.

History Buffer

If a fault is detected, it is reported in the History Buffer or an existing report in the Buffer is
updated. A fault report comprises:
-

Hardware address to identify the fault location;
Alarm code (4 digits) to identify the fault type;
Number of detections;
Date and time of the last detection;
Additional information.

There is an integration parameter (PE parameter) which determines whether and when an
alarm will be generated (table 3.3.). More details are given in table 3.4.
VALUE OF INTEGRATION
PARAMETER
0
1...98
99

ALARM GENERATION
No alarm.
After two detections within an interval of
15 x n minutes.
n = parameter value (1...98).
After one detection.

INTEGRATION
CATEGORY
c
b
a

Table 3.3. Alarm Integration.

3-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

INTEGRATION
CATEGORY

FAULT
ALREADY
REPORTED

WITHIN
INTEGRATION
INTERVAL

c

-

-

b
b

no
yes

no

b

yes

yes

a

no

-

a

yes

-

ACTIONS
HISTORY BUFFER
New report.
Old report (if any) is frozen.
New report.
New report.
Old report is frozen.
Update of old report:
- number of detections;
- date and time of latest
detection.
New report
Update of old report:
- number of detections;
- date and time of latest
detection.

FAULT REPORT TO
ANY ALARM BUFFER
no
no
no
yes

yes
yes

Table 3.4. Survey, History Buffer.

3.5.2.

Alarm Buffers

Fault reports may automatically be copied from the history buffer into the Major alarm
buffer, Minor alarm buffer, or Silent alarm buffer. Reports entered into the Major buffer or
Minor buffer are visually indicated on the MPC, operator console and/or an alarm box. A
visual alarm indication will be accompanied by an audible alarm indication if the fault has
not previously been reported.
There are no visual or audible alarm indications in the case of fault reports entered into the
Silent alarm buffer, except for the MPC. On the MPC screen a visual indication is given for
the silent alarm.
The date and time in a report transferred from the History buffer to an alarm buffer does not
change.
A count is maintained of the number of times a given fault report is re-entered into an alarm
buffer. It is reset to zero each time the alarm concerned is reset.
Alarms can be reset as follows:
- Automatically via an automatic recovery mechanism (not applicable to all alarm codes).
In the chapter that describes the actions in case of alarms the automatic recovery is
abbreviated ”AR”.
- In the event of a PCT alarm by setting the circuit condition of the PCT concerned to OUT.
- By resetting all fault reports in all three alarm buffers.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

3-5

A fault report which has been in an alarm buffer for more than 100 days is automatically
reset.
Lamps and buzzer indications associated with alarm reports are supressed as soon as the
alarm buffers concerned are reset.

3-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

4.

LOADING AND RETRIEVING ISPBX SOFTWARE

This chapter describes:
-

Connecting
Installing
Preparing
Loading
Retrieving

:
:
:
:
:

how to connect an MPC to the ISPBX;
how to install software files on the MPC hard disk;
how to prepare software and data for transfer to the ISPBX;
how to transfer software or data from the MPC to the ISPBX;
how to transfer software or data from the ISPBX to the MPC.

ISPBXs that use SSW 300 do not use EPROMs to store the software or information that the
ISPBX uses, except for a small boot PROM that controls initial start-up and loading of the
ISPBX software. The boot PROM is loaded and installed at the factory and other software
or information is stored in Flash-EPROMs. An MPC is used to transfer software to or from
Flash-EPROMs (FEPROMs) on the CPU and peripheral cards; a V.24 serial link is used for
this. Peripheral cards are: PMC, DTX-I, DLC-U.

Notes: 1. Make sure you have the OM Commands Manual (MML, SSW 300), so that you
can look at the details and explanations of each MML command used in this
chapter.
2. Take special care to note the definitions of “Loading” and “Retrieving” used in
this chapter.
3. FEPROMs are never removed from the SSW 300 ISPBXs (except if they are
faulty); also they are never placed in a PROM programmer. (The DATA I/O
PROM PROGRAMMER is no longer used with SSW 300 ISPBXs).
4. The ISPBX power supplies should have been tested before software is
loaded/retrieved.

4.1.

INTRODUCTION

A local OM session must be established before software can be transferred; the MPC User
Guide describes how to set up a local OM session.
Software that is transferred to or from the ISPBX memory consists of three types:
- CPU software
: SSW 300 (the basic ISPBX software package);
- POM data
: PE/OM data (Project Engineering/Operational Maintenance data).
- Peripheral software : software for the peripheral cards.

Notes: 1. CPU software and peripheral software can only be loaded into the ISPBX
(they cannot be retrieved from the ISPBX).
2. The PE data and the OM data are combined into one file - a POM data file.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-1

3. The POM data file can be loaded from the MPC into the ISPBX (OM
command: LDPOMD) or retrieved from the ISPBX to the MPC (OM command:
DUPOMD, DUPOME).
4. For a full description of the OM commands used in this chapter, look in the OM
Commands Manual (MML).

4.2.

CONNECTING THE MPC TO THE CPU CIRCUIT BOARD

Figure 4.1. shows where the CPU circuit board is located in the exchanges.
SOPHO iS3010

Control Shelf

SOPHO iS3030

CPU
Card

Control Shelf
(master cabinet)

104

CPU
Card
108

Figure 4.1. Locating the CPU Circuit Board (CPU-ME in each ISPBX).

Figure 4.2. shows how and where to connect the MPC to the CPU circuit board.
For a local session the MPC should be connected to port 1, 2 or 3
of the CPU-ME. For loading CPU software port 1 must be used.
(The port chosen should not be in use for any other purpose when
software is being transferred.)
If the REBOOT command is used while the MPC is connected to a

0
1
2
3

port other than port 1, then, after the command is completed, the
MPC must be disconnected from that port and connected instead
to port 1.
Parallel
port

Serial
port

CPU-ME

PRINTER
*

*

Shelf

The printer is optional

Figure 4.2. Connecting the MPC to the CPU-ME.

4-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

4.3.

INSTALLING FILES ON THE MPC HARD DISK

The ISPBX is supplied with diskettes that contain software to be loaded into FEPROM. On
diskette number 1 there is a program called “INSTALL.EXE”, which is used to install
software files on the hard disk. Before you load software into the ISPBX make sure those
software files are on the MPC hard disk; use the INSTALL program. Do this as follows:
-

Insert diskette number 1 into a floppy disk drive;
Make sure the screen prompt is the one relating to the drive with the floppy disk in it;
Type INSTALL and press return;
Follow the prompts that appear on the screen.

As you follow the prompts the ISPBX software files will now be copied to the hard disk *
* ISPBX software means CPU, PPU or other peripheral software.

4.4.

PREPARING SOFTWARE AND DATA FOR THE ISPBX

• CPU software
The CPU software does not require preparation; it is bought from the ISPBX supplier,
together with the ISPBX; the CPU software must, of course, be put on the MPC hard disk
before it can be loaded into the ISPBX.
Use INSTALL.EXE to put the CPU software on the MPC hard disk (INSTALL.EXE checks
the hard disk to see if there is enough room on it).
• POM Data
A software program called PG2 (Project Generator 2) is used on the PC to produce the
POM data file.
POM data = PE/OM data (Project Engineering/Operational Maintenance data).
The file contains both PE data and the OM data (POM data); the complete POM data file
is produced in response to a series of questions and can then be stored on floppy disk,
ready for transferring (Loading) to the ISPBX.

Notes: 1. The data created by PG2 is written in Man-Machine Language (MML) and, if
slight changes are thought necessary, they can be made later using a texteditor or word-processor in “non-document” mode, for example, Wordstar ©.
The details of MML can be found in the Operational Maintenance Command
(MML) manual.
2. An ISPBX owner might wish to change the operation of an ISPBX at some
later date, for example, the ISPBX owner might want to change extension

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-3

numbers or the facilities available at an extension. This can be done using
OM on an MPC

• PPU Software
The PPU software does not require preparation; it is bought from the ISPBX supplier,
together with the ISPBX. Use INSTALL.EXE to put the PPU software on the MPC hard
disk. (INSTALL.EXE checks the hard disk to see if there is enough room on it).
PPU software contains definitions related to all the PCTs that it is possible to install in the
ISPBX; the definitions include such things as signalling blocks; this does not mean that all
those PCT definitions are used by the ISPBX. (The POM data defines which PCT
definitions are actually used.)
• PCT Software
DTX-I and DLC-U software is available on 31/2 inch floppy disks, which is to be
downloaded via the MPC. Also an INSTALL.EXE file is present on the floppy disk for
preparing the files by de-compressing the data files and transferring them from floppy
disk to the hard disk. Consequently the prepared data files on the hard disk with .DAT
extension can be downloaded to the DTX-I or DLC-U.

4.5.

LOADING SOFTWARE AND DATA INTO THE ISPBX

4.5.1.

Introduction

Software and data should be loaded into the ISPBX in the following sequence:
1.
2.
3.
4.

CPU software *;
POM data;
PPU software **;
Other peripheral software ***.

*

For loading CPU software, the MPC must be connected to port 1 of the CPU-ME card.

**

PPU software can only be loaded into the ISPBX when PMC cards have been
projected, therefore, PPU software should be loaded after POM data.

***

Other peripheral software can only be transferred if the related PMC is in service. This
means also that the software for the related PMC must already have been transferred.
The peripheral itself must be projected and out of service.

4-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

OM commands are used on the MPC to load software into the FEPROMs. The MPC must
be connected to the CPU-ME card and set to “Local OM”. The OM commands used are
listed in the following section, 4.5.2.
Load CPU
Software

Load POM
Data

Load PPU
software

Load peripheral
software

Figure 4.3. Loading ISPBX Software.

4.5.2.

Loading CPU Software (Flowchart)

Look at figure 4.4. and follow the sequence of OM commands and actions shown in the
figure; look also at the text that follows the figure.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-5

INSTALL *

REBOOT

Operational
ISPBX

Newly installed
ISPBX

Copy CPU
package to
MPC hard disk

Copy CPU
package to
MPC hard disk

Connect MPC
to ISPBX and
start local OM
session

LOADING CPU
SOFTWARE **

Connect MPC
to ISPBX and
start local OM
session

REBOOT

Switch the
ISPBX on

Show CPU
package identity

INSTALL *

DIPACK

No
CPU package
loaded ?
Yes
Is it the
package
required ?

Yes

No
Delete CPU
package from
FEPROMs

*

INSTALL is not an OM command. See
section 4.3.
Other commands shown in the figure are
OM commands.

** Look at the text that follows this figure for
a more detailed explanation of the
sequence shown by the flow-chart.

Load package
from MPC hard
disk to ISPBX

Start package
in ISPBX

DEPACK

LDPACK

STPACK

CPU package
up to date

Figure 4.4. Loading CPU Software.

4.5.3.

Loading CPU Software (MML Commands)

The following explains how to load the CPU software package; it refers to figure 4.4.

4-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

1.

Copy the CPU package to the MPC hard disk. (Look at section 4.3.)

2.

Switch the maintenance PC on; use the MPC menus to select and start a local OM
session. The MPC will try to establish an OM session with the ISPBX but will not
succeed unless the ISPBX is switched on.

3.

Switch the ISPBX on. Now that power is applied to the ISPBX the Maintenance PC
will establish a local OM session with the CPU-ME in the ISPBX.

4.

Start the Boot Program
REBOOT: ;

5.

Display Package Identity
DIPACK: [<HW-ADDR>];

6.

Is there a CPU package loaded in the ISPBX?
Yes - go to step 7.
No - go to step 9.

7.

Is the CPU package identity the one required ?
Yes - go to step 10.
No - go to step 8.

8.

Delete package
DEPACK: [<HW-ADDR>s],[<CLEAR-PROJ-PROM>];

9.

Load the CPU package
LDPACK: [<HW-ADDR>s],<FILE-SPEC>[,<SYSTEM ID>];

10.

Start the CPU package.
STPACK: ;

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-7

4.5.4.

Loading POM Data and Peripheral Software (Flowchart)

LOADING POM DATA *

LOADING PERIPHERAL SOFTWARE *

Ensure POM data
package is on
MPC hard disk

Copy peripheral software
package to
MPC hard disk

INSTALL

INSTALL is not an
OM command. See
section 4.3.
Other commands
shown in the figure
are OM commands.

Load POM data
from the MPC
to the ISPBX **

LDPOMD

No
Peripherals
projected?

Yes

POM files are
loaded

Show peripheral
package identity

Copy POM
data to active
memory

COLDST

Project the
peripherals

No

DIPACK

Peripheral
package present?

THIS IS
OPTIONAL
DUPOME

Yes

Dump
projecting
errors to MPC

No
Old peripheral
package?
For PMC

Proceed to
“LOADING
PERIPHERAL
SOFTWARE”

Set out of
service
Execute
WARMST
(ONLY FOR PMCs)

*

For other peripheral

Yes

Look at the text that follows this
figure for a more detailed
explanation of the sequence
shown by the flow-chart.
POM data can only be loaded if
CPU software has been loaded
before it.

Delete old peripheral
package

SETODS

WARMST

SETOUT

Only if the peripheral
is a PMC

DEPACK

Load peripheral
package

LDPACK

Set the peripheral(s)
in service

**

SETSDS

SETINS

For PMC

For other
peripheral

Peripheral package
up to date

Figure 4.5. Loading POM Data and Peripheral Software.

4-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

4.5.5.

Loading POM Data (MML Commands)

Ensure the CPU package is loaded and started.
Ensure that the POM data you require is on the hard disk (use PG2 to create it if it doesn't
exist already).

Notes: When initialising a system ensure that :
- the POM data correctly projects the PMCs and other peripherals that are to be
loaded;
- the PMCs to be downloaded are out of service (SETODS);
- the peripherals to be loaded are out of service (SETOUT).
Use the following commands to load POM data; refer also to figure 4.5..
1.

Load POM Data
LDPOMD: <FILE-SPEC>;

2.

Bring the POM data into use.
COLDST:

3.

;

Check for Projecting Errors
DUPOME: <FILE-SPEC>;
This step is optional. You can use the command to dump POM data and projecting
error data from the POM memory to the Maintenance PC.

4.5.6.

Loading Peripheral Software (MML Commands)

Use the following commands to load peripheral software; refer also to figure 4.5.
Peripheral software is loaded from the MPC to the CPU card, the CPU card then passes
the software on to the PMC card. If the software just loaded is intended for the PMC it will
be stored in the PMC FEPROM; if the software is intended for another peripheral, the PMC
will route the data to the peripheral indicated. The peripheral will store the software in its
FEPROM.

Notes: 1. Take care that the valid CPU package is downloaded and started.
2. When loading a PMC, the PMC must be “out of service”.
3. When loading a peripheral, the PMC that controls that peripheral must already
be loaded with software and the PMC must be “in service”.
The peripheral must be “projected” and “out of service” before it can be
loaded with software. Look at the command SETODS/SETOUT below.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-9

1.

Copy the Peripheral package to the MPC hard disk. (Look at section 4.3.)

2.

Display Package Identity
DIPACK: [<HW-ADDR>];

Note : In order to be consistent with the MPC Help file the hardware addresses are
identified by <HW-ADDR> or <EHWA>, although they have the same
meaning. The hardware address of the PMC is 11799 or 31799.
3.

Set “Out of Service” and Display Service Condition
SETODS: <EHWA>s;

Notes:
• Operational ISPBX
- The peripheral to be loaded with software or data must be out of service before
loading can take place.
- When the peripheral is a PMC the SETODS command followed by the WARMST
command is required.
- For other peripherals the SETOUT command must be used (does not need the
command WARMST).
- The command SETODS does not take the PMC out of service, it only marks the
PMC with the service condition required. The command “WARMST” implements that
service condition; only then is the PMC “out of service”.
• New ISPBX installation or new software installation
- When an ISPBX system is being initialised the service condition of the PMCs is set
to NIN automatically (NIN = “Not in Service”). To set the service condition to OUT
execute command SETODS. In this case it is not necessary to execute a
WARMSTART (because, in a new system, the PMCs have never been “in service”).
4.

Warmstart
WARMST: ;

5.

Delete Existing Peripheral Package.
DEPACK: [<HW-ADDR>s],[<CLEAR-PROJ-PROM>];

6.

Load Package
LDPACK: [<HW-ADDR>s],<FILE-SPEC>[,<SYSTEM ID>];

4-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

7.

Set and Display Service Condition
SETSDS: <HW-ADDR-PM>s;

4.5.7.

Downloading Software for Peripheral Circuits DTX-I and DLC-U

DTX-I and DLC-U software is available on 31/2 inch floppy disks. Prepare the MPC as
follows:
- Define a directory on the MPC hard disk where the de-compressed data files should be
transferred to and take care that the path settings are correctly. Also an existing MPC
directory can be used, for example C:\USER>. In that case the paths are already set.
- The assumption is made that the floppy drive B will be used. Go to drive B and type:
B:>INSTALL <return>
Example : In case preparing the DTX-I files the system will respond with:
Give source disk or <return> for ”B:\”:<return>
Give destination disk and directory specification :C:\USER> <return>
In case the prompt on the hard disk is still at C:\USER>, then a single <return> is
sufficient.
Creating file C:\USER\220002XX.DAT (XXX kB)
Input file : B:\220002XX.D01 Output file 220002XX.DAT
File C:\USER\220002XX.DAT created (XXX kB).
The data files are ready for downloading the DTX-I or DLC-U. Start the MPC program.
The DTX-I and the DLC-U software can be downloaded using the sequence explained
below.
1.

Set Out of Service
SETOUT: <HW-ADDR>s/r;
Used to set the DTX-I or the DLC-U out of service.
HW-ADDR

9412

:

SCCPP, S = shelf 0 ...3; CC = card position 01 ... 10; PP = port number
00 ... 31, 99 for the complete PCT board.

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-11

2.

Delete Existing PCT Package.
DEPACK: <HW-ADDR>s,;
HW-ADDR

:

SCC99, S = shelf 0 ...3, CC = card position 01 ... 10.

The system will respond with

:

DELETE THE PACKAGE (Y/N) ? Y

Deleting the older PCT package should result in (example valid for DTX-I):
Green LED : On
Red LED
: Blinking
3.

Display Package Identity
DIPACK: [<HW-ADDR>];
HW-ADDR

:

SCC99, S = shelf 0 ...3, CC = card position 01 ... 10.

The following should be displayed (example valid for DTX-I):
Boot-12NC
3522 254 XXXXX
4.

Boot Prom-ID
3900 XX XX

Package-12NC
0000 000 00000

Package-ID
0000 00 00

Load Package
LDPACK: [<HW-ADDR>s],<FILE-SPEC>,;
HW-ADDR
FILE-SPEC

:
:

SCC99, S = shelf 0 ...3, CC = card position 01 ... 10.
XXXXXXXX

Loading the new PCT package should result in:
Green LED : On
Red LED
: Off
5.

Display Package Identity
DIPACK: [<HW-ADDR>];
HW-ADDR

:

SCC99, S = shelf 0 ...3, CC = card position 01 ... 10.

The following should be displayed (example valid for DTX-I):
Boot-12NC
3522 254 14572

4-12

Boot Prom-ID
3900 XX XX

Package-12NC
9562 XXX XXXXX

Package-ID
2200 XX XX

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

6.

Set In Service
SETINS: <EHWA>s/r;
Set in service the DTX-I or the DLC-U.
HW-ADDR

:

SCCPP, S = shelf 0 ...3, CC = card position 01 ... 10; PP = port number
00 ... 31, 99 for the complete PCT board.

4.6.

RETRIEVING POM DATA FROM THE ISPBX (MAKING A BACK-UP)

4.6.1.

Introduction

OM commands can be used on the MPC to retrieve data from the FEPROMs; only POM
data and POM data errors can be retrieved. This facility is useful for making a back-up of
POM data. The MPC can be connected directly to a V.24 port on the CPU-ME card or
remotely via modems; the MPC “SETUP” menu should be used to select a “local OM
session” or a “remote OM session”, whichever is appropriate.
The ISPBX uses two parts of FEPROM for storage and retrieval of POM data; see the parts
of POM memory marked “Part 1” and “Part 2” in figure 4.6.
Flash EPROM

RETRIEVING POM DATA

LDPOMD
Serial
port

RAM
COLDST

Part 1
POM data
loaded from the
MPC

MPC

step

A

Parallel
port

BKPOMD

POM data
of running
system
DUPOMD
Serial
port

RUN-TIME
DATABASE AREA

PE part of
POM data
from Flash
EPROM

step

A

Part 2

BKPOMD

Back-up area

PRINTER

step

step

C

B

OM part of POM data from runtime database area of RAM

Figure 4.6. Making a System Back-up from an Operational ISPBX.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-13

- Part 1 is used during initial software loading; it contains both the PE part of POM data
and the OM part. (If changes are made to a running system then the OM contents of the
“run-time database” in RAM are changed; the contents of part 1 are not changed).
- Part 2 is used during a back-up; after the MML command BKPOMD is executed, it
contains PE data from part 1 of FEPROM memory and OM data from the “run-time
database” (RAM).

4.6.2.

Making a Back-up

Look at figure 4.6. and carry out steps A to C shown in the figure; the MML commands you
should use for each step are shown below.
Step A. Back-up POM Data (within FEPROM)
BKPOMD: ;

Notes: 1. The command BKPOMD only starts the back-up process; use the command
DIPOMS to check whether the process is finished (see step B).
2. After the back-up is completed, part 2 of POM memory will contain two things:
- PE data from part 1 of POM memory;
- the latest OM data from the run-time database of the working ISPBX.
This means that, after the back-up, the POM data contained in part 2, (PE +
OM), is the latest version of POM data that the ISPBX is using. This data can
be downloaded to the MPC as a back-up file (see the command
“DUPOMD”).
Step B. Display the status of POM memory (Check to see if the back-up has finished)
DIPOMS: ;
Step C. Transfer Back-up to MPC (Retrieve POM Data into the MPC)
DUPOMD: <FILE-SPEC>,[<POM-PART>];

4.6.3.

Other Commands

• Check for Projecting Errors
DUPOME: <FILE-SPEC>;
With this command you can dump the stored POM data and the related projecting error
data from the POM memory to the Maintenance PC.

4-14

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

• Clear POM Data
CLPOMD: <POM-PART>;
With this command you can clear one of the POM memory parts.
• Display Date and Time
DIDATI: ;
• Display Exchange Identity
DIEXID: ;

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

4-15

4-16

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

5.

PROJECT DATA PROTECTION

In order to protect the contents of the various RAM memories in the event of the power
being interrupted two conditions must be complied with:
- The RAM memory must have a continuous voltage supply.
- The uncontrolled write actions to be expected from the Motorola 68302 micro processor if
the CPU supply voltage (+5V3) falls off must not affect the RAM.
The first of these conditions is met by the EBU (Emergency RAM back-up Battery Unit). If
the RAM supply voltage (+VCMOS) falls off, then the supply of the RAM is taken over by
this battery (+4V BAT).
The second condition is met by the RAM back-up mechanism. Even before the voltages
concerned have become too low, the PSU gives the signal EPF# which causes the 68302
to be brought into the HALT condition.
When the CPU supply voltage returns to normal, the Motorola 68302 micro processor
restarts after some delay. In the intervening period the RAM is further protected by
disconnecting the supply for the RAM input drivers.
The circuits involved in the RAM back-up mechanism must be supplied normally, both
during fall-off and return of the CPU supply voltage. For this reason these circuits are
connected to the +VCMOS/+4V BAT supply line.

Note: To allow signal EPF# to function properly, the replacement of a PSU must always
be carried out in the following sequence:
-

9412

Disconnect the primary supply for the PSU.
Wait until the capacitors have fully discharged (approximately 30 seconds).
Take out the PSU.
Fit the (new) PSU.
Re-connect the primary supply.

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

5-1

5-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

6.

THE HANDLING OF PRINTED WIRING BOARDS

The following should be observed when handling PWBs:
- Do not store PWBs in a high temperature or high humidity environment;
- Transport PWBs in the original packing;
- Do not hold PWBs by the components mounted on them.

Warning: Most PWBs include one or more Integrated Circuits (ICs) using CMOS
Technology. These ICs have extremely high input and output impedances and
can thus be damaged if exposed to static charges, such as those which can
build up on clothing and body in a dry atmosphere. For protection all CMOS
inputs and outputs on a PWB are linked with "low-ohmic" circuits.
Nonetheless, the following is recommended:
. Wear an anti-static wrist strap and use an anti-static floor mat. Make sure
these anti-static devices are connected to the exchange frame.
- Do not stack PWBs without protection.
- Repair PWBs only in workshops equipped by PHILIPS for that purpose.
- When, in exceptional circumstances, measurements must be made on a PWB or on the
back panel (using the card extender) care must be taken that no short-circuit is made to a
circuit with a different supply voltage (+12 V, +5 V, -5 V, -12 V, -48 V).

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

6-1

6-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

7.

EQUIPMENT INSTALLATION

7.1.

GENERAL REQUIREMENTS

This chapter explains how to install the SOPHO iS3010 and SOPHO iS3030, MDF cabinets
and combined equipment/MDF cabinets. It does not describe the installation of the wiring of
the site. This is normally a separate task from that of installing the equipment. Therefore,
the installation engineer should only have to connect the equipment to already installed
telephone and external line cabling and power cabling. The wiring of the MDF (Main
Distribution Frame) is described in chapter 8 and the installation of the power supply and
earth connections are described in chapter 15.

7.2.

SITE REQUIREMENTS

The system should be installed in an environment which meets the following:
- Temperature range
- Humidity

7.3.

: -5°C to 45°C;
: 10% to 85%.

REQUIRED INSTALLATION EQUIPMENT

Apart from a complete set of tools (spanners, screwdrivers etc.) the following items are
required:
-

Knife for opening packing material.
Spirit level.
Universal wiring tool. This is required for cabling the MDF.
Tie wrap gun.
Drill and 10 mm masonry bit.
A multimeter which should be able to read:
. AC voltage;
. DC voltage;
. DC current;
. Resistance.
- Check the items of equipment to be supplied are according the parts list.
- 13 mm socket with ratched handle or a 13 mm box spanner with bar.

7.4.

ANTISTATIC HANDLING

Static charges can cause serious damage of the equipment, especially on the printed wiring
boards which uses ICs based on CMOS technology. Although special protective measures

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

7-1

have been taken, one should always hold 'ground' during handling the printed wiring boards
in order to protect the components on it. Diagram 330 and 331 show the plugs for
connecting the antistatic bracelet, which has to be used during replacement of PWBs. The
bracelet may also be an antistatic wristwatch with ground connection. Diagram 110 shows
how to use the antistatic bracelet.

7.5.

SITE CHECKS AND INSPECTION

Before commencing work, check that:
- The areas you need to be in have to remain accessible for the duration of the installation
and testing of the system.
- All site wiring has to be completed and correctly identified.
- The power and safety requirements have been met, accordingly the Philips requirements
and the local requirements.
- A connection of a 'clean' earth must be available for the SOPHO iS3010 and the SOPHO
iS3030.
- If local regulations require certain tasks (e.g. connecting the system to telephone
exchange lines) which must be done by specially trained people, these people are
available in time.

7.6.

UNPACKING, LOCATING AND FIXING THE CABINET

The unpacking of the equipment is done accordingly the procedure shown on the packing.
When you have unpacked the equipment check it against the delivery note. If there are
differences immediately report these to the supplier.
For locating the cabinets consult diagram on the template which is inside the packing. If the
system consists of a separate equipment and MDF cabinet, the equipment cabinet is
located normally at the right side of the MDF cabinet. A cabinet is fixed to the wall by
means of a bolt at the left and at the right side. Install the cabinets according following
measurements:
- Minimum distance between the top of the cabinets and the ceiling is 50 cm;
- Minimum distance between the bottom of the cabinet and the floor is 10 cm,
recommended distance is 125 cm.
- Minimum distance between the left/right of the cabinet and the wall is 45 cm;
- Minimum distance between the front of the cabinet and the wall in front is 80 cm.
- Minimum distance between the cabinets of a two cabinet SOPHO iS3030 should be 10
cm, when the cabinets are installed above another.
Diagram 155 shows the measurements for a two cabinet SOPHO iS3030.

7-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

If the cabinet(s) are to be mounted to the floor a floor stand should be used. Mounting
instructions for this stand are inside the packing of the floor stand. See also diagrams 150
and 152.

Note: Floor-mounted types should not be located close to central heating radiators.
Wall mounted cabinets should not be located above central heating radiators.

7.7.

CABLING THE EMC IMPROVED CABINETS

7.7.1.

EMC in General

The Electro Magnetic Compatibility (EMC) Improved cabinets are available for SSW 300
systems SOPHO iS3010/3030. The EMC properties of these cabinet are such that a correct
installed SOPHO iS3010/3030 fulfil the Dutch and German EMC requirements.
The EMC specifications for The Netherlands are according to:
- EN 55022.
- EN 55101/1-6, class B.
The EMC specifications for Germany are according to:
-

VDE 0839;
VDE 0847;
VDE 0876;
VDE 0877;
VDE 0878;
FTZ 12 TR 1/6.87;
FTZ 12 TR 2/9.88.

To be able to comply to the specifications following have been implemented:
- Electro Magnetic closed cage cabinet;
- EMC provisions in cables leaving the system;
- Special way of leading the system cables.

7.7.2.

Cabinet Composition

The SOPHO iS3010/3030 cabinets are a composite of a backpanel, a frame of two shelves,
two metal plates to cover the PCT positions and the backpanel, a metal strip to cover a part
of the power supply cable, an overall cover and the possibility to connect the (optional)
EBU.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

7-3

The cabinet iS3010/MDF is a composite of a SOPHO iS3010 cabinet, an MDF, MDF cover
and the possibility to connect the (optional) EBU. For more detailed information refer to the
Hardware Configuration Manual.

Note: Despite the general EMC provisions, for some boards extra provisions have to be
taken. These boards are ATU-ST02 and ATU-SS02.

7.7.3.

Cabling the EMC Cabinets

SOPHO iS3030 cabinet is illustrated only, the described handling will be the same for the
SOPHO iS3010 cabinet. Install the cables as follows:
1. All the cables leaving or entering the cabinet have to be EMC improved. The system
cables B between the MDF and the front connectors (F122 and Coax) are equipped
with an EMC shield (ferrite). These cables have to be led in a special way from the front
connectors to the MDF, as shown in diagram 315.
2. The mains cable C should be winded 5 turns on the ferrite ring before leaving the
cabinet and is to be led under the metal clamp D, which acts as a capacitor and shunts
the HF currents to the cabinet, see figure 7.1. Position the ferrite ring behind the rectifier
unit, lead the mains cable through the hole at the front of the rectifier unit and fix it to the
tension relief, as illustrated in diagram 315.
Ferrite core (5 windings)

Transformer side

Metal clamp

Mains side

Figure 7.1. Ferrite Core and Metal Clamp combination form a Low-Pass filter.

3. To obtain the best EMC result shift the 2 sets of ferrite shields as far as possible to the
point where the cable exits the EMC enclosure, as illustrated in diagram 315.
4. It is very important to lead the cables according to diagram 315, especially if the cabinet
is full. The EMC shields must be housed within the cabinet and they should not be seen
from the outside with the front panel closed. Therefore, lead the cables in such a way
that no problem will occur when closing the front panel.
5. During replacement of the board in top left position, make sure the screws A (4 x to
fasten the front panel on the left side) do not scratch the board, see diagram 316, this

7-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

may damage the board.
Removing the first PWBs from the most left slot positions is made easier by the two
holes at the left cabinet side. To remove the PWB hold the PWB between your direction
finger and thumb (through the hole) and pull it out.
6. Install the metal lock E for the PWB boards according to diagram 315. During transport
the metal clamp has white foam rubber at the PWB side to protect the PWBs. During
installation remove the foam rubber, insert the metal clamp in the special slots at the
right side, shift the lock at the left end to the left and fasten the two screws.
7. The EBU pack is to be installed according to diagram 320. Connect the red wire to the
+ and black wire to the - on the EBU. The wires should be pushed back in to the shelf
as far as possible.
8. If the SOPHO iS3010 is equipped with a PSU-S, then there is no separate rectifier unit
F present. In this case install the transformer (300 VA) as shown in diagram 317 and
fasten the ferrite ring with a tie-wrap to the cabinet frame as shown.
9. Close the front panel and fasten the 15 screws S to obtain the best EMC result. See
diagram 316.

7.7.4.

Installing the Trunk Filters for ATU-SS02/ST02

A special trunk filter is needed for installing the ATU-SS02 and ATU-ST02. The trunk filters
are installed at the bottom or at the top of the SOPHO iS3010/3030 cabinets according
diagram 318. One trunk filter is necessary per ATU-SS02/ST02 board and a maximum of 8
trunk filters can be used per system. See also figure 7.2.

ATU-SS02
ATU-ST02

F122 Connector

F122 Connector

MDF

Ferrite Rings
Trunk Filter

Figure 7.2. ATU-ST02 and ATU-SS02 installation block diagram.

1. Insert the ATU in the correct slot position.
2. Fasten the trunk filter(s) to the cabinet as shown in diagram 318 by means of 2 tiewraps. If the ATU is positioned in the upper shelf fasten the trunk filter at the top of the

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

7-5

cabinet and if positioned in the lower shelf fasten the trunk filter at the bottom of the
cabinet.
3. To obtain the best EMC result shift the 2 sets of ferrite shields as far as possible to the
point where the cable exits the EMC enclosure, as illustrated in diagram 318.
4. Connect the F122 connector to the trunk filter and lead the cable(s) as illustrated to the
MDF.

7.7.5.

Required EMC Improved Cables

The following EMC Improved cables are available for SOPHO iS3010/3030:
- F122/F122, 6 m, after this cable is cut in two pieces it is used to connect the external
MDF to the PCTs, excl. 10 pair disconnecting sofycom blocks, it also can be used to
support the -48 V (PSU) to the MDF, max current 0.5 A/Core (total 2.5 A max.).
- F122/F122, 20 m, after this cable is cut in two pieces it is used to connect the external
MDF to the PCTs, excl. 10 pair disconnecting sofycom blocks, it also can be used to
support the -48 V (PSU) to the MDF, max current 0.5 A/Core (total 2.5 A max.).
- F122/Sofycom, 1.60 m, this cable is used to connect the internal MDF to the PCTs, incl.
10 pair disc. sofycom blocks, it also can be used to support the -48 V (PSU) to the MDF,
max current 0.5 A/Core (total 2.5 A max.).
- F122/Sofycom, 0.90 m, this cable is used to connect the internal MDF to the PCTs, incl.
10 pair disc. sofycom blocks, it also can be used to support the -48 V (PSU) to the MDF,
max current 0.5 A/Core (total 2.5 A max.).
- F122/D-connector, 1.50 m, this cable is used to connect DTE/DCE equipment (MPC,
SOPHO SystemManager, Alarm Unit, etc.) to the MLU, CPU, APU, etc. F122 at one side
and 25-pin male D-connector at the other side.
- F122/Coax, 1.60 m, 75 Ohm coaxial, it is used to connect a DTU F122 connector to a
coax cable, it is assembled with an F122 at one side and two coax connectors at the
other side. It is possible to connect two DTUs to the MDF with one F122/Coax cable.
- AOC/Sofycom, 1.60 m, it is used to connect an AOC to the internal MDF, it is assembled
with a F122 at one side and a sofycom 10 pair disconnecting block at the other side.
- AOC/Sofycom, 20 m, it is used to connect an AOC to the external MDF, it is assembled
with a F122 at one side and a sofycom 10 pair disconnecting block at the other side.

7-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

- F122/Trunk filter assembly, 0.80 m, it is connected between an ATU-SS02/ST02 and the
external MDF, it is assembled with a F122 at one side and a trunk filter at the other side.

7.8.

PMC-PMC CABLE INSTALLATION

In a two cabinet SOPHO iS3030 system the PMCs communicate to each other using a
special network interconnection. This interconnection is done via a special PMC-PMC front
connector cable. This is a pre-assembled cable existing of 2 shielded F122-F122 cables.
MASTER PMC
connected to
FCA
connected to
FCB

SLAVE PMC
FCC
FCD

• EMC Cabinet
Mount the PMC-PMC cable in the EMC cabinet according diagram 350. Take care that
the blanked shield makes good contact with the bracket and the cabinet and mount the 2
cables and bracket to the cabinet.
• Non-EMC Cabinet
Mount the PMC-PMC cable in the non-EMC cabinet according diagram 351. Take care
that the blanked cable shield makes good contact with the bracket. Assemble the bracket
and the two shielded cables and connect the bracket to the rectifier plate using the
rectifier plate screw as shown.
Lead the cables from the cabinets properly

7.9.

DIFFERENCES BETWEEN THE EMC AND NON-EMC CABINETS

7.9.1.

Different Installation Rules

The EMC and non-EMC cabinets differ from the installation point of view at several points.
1. The EMC improved and the not EMC improved cabinet are different types of cabinets.
2. Installing the PMC-PMC cable in a two cabinet SOPHO iS3030 system is different for
both types of cabinets. See diagrams 350 and 351.
3. Installing the mains cable differs slightly for both types of cabinets. See diagrams 319
and 350.
4. Installing the EBU differs for both types of cabinets. See diagrams 319 and 320.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

7-7

5. In an EMC improved cabinet EMC improved cables are used. Cables used in the nonEMC cabinet are not EMC improved.
6. In the EMC cabinets special trunk filters are used to connect the ATU-SS02/ST02 to the
external MDF. See diagram 318.
7. In the non-EMC cabinet each PWB board position has its own lock, while the EMC
cabinet is equipped with one PWB lock for all the upper and lower PWB board positions,
see diagram 315..
8. In the non-EMC cabinet no cable support bar is present between the upper and the
lower shelf.
9. In the non-EMC cabinet no metal front cover is present and there are no metal top and
bottom covers.

7.9.2.

Common Installation Rules

This section mentions the common installation rules for the EMC and non-EMC cabinets.
1. Installing the transformer and the rectifier unit is the same
2. Cable run to the MDF and the earth connection is the same.
3. The position of the V.24 connector is the same.

7.10.

FLOORSTAND INSTALLATION

A floorstand is required if wall mounting is not possible or not preferred. The floorstands can
be combined side by side and for stability they must be placed against a wall.
The floorstands include materials for mounting the systems to the floorstand.
There are two types of floorstands available, namely:
- Floorstand 1;
- Floorstand 1.5.
The following can be mounted to floorstand 1:
- SOPHO iS3010 (MDF not included);
- SOPHO iS3030 (MDF not included);
- MDF for iS3030.

7-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

Refer to diagram 150 for installing Floorstand 1. Use detail A for combining the floorstands
side by side if necessary.
Floorstand 1.5 can be used in combination with the following systems:
- SOPHO iS3010 (MDF included);
- SOPHO iS3030 with half sized MDF (MDF iS3010).
Refer to diagram 152 for installing Floorstand 1.5. Use detail A for combining the
floorstands side by side if necessary.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

7-9

7-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

8.

MAIN DISTRIBUTION FRAME

8.1.

CONSTRUCTION

The Main Distribution Frame (MDF) is designed to facilitate the connection of Printed Wiring
Boards (PWBs) in the shelves to public and private telephone exhanges and telephone
sets. It is housed in a single cabinet or housed in the system cabinet. The following types of
MDF are distinguished:
- MDF for SOPHO iS3010.
This MDF contains one column of 10-wire-pair disconnecting and connecting blocks.
- MDF for SOPHO iS3030.
This MDF contains two columns of 10-wire-pair blocks. The left column comprises
connecting blocks used to terminate the external cabling. The right column comprises
disconnecting blocks used to terminate the cables from the equipment.
The diagram range 400...500 show, how to terminate the cables of the various PCTs. In
case of a DTU, a coaxial connection can be required (see diagram 420). The coax
connection is made as shown in diagram 450 (for more information see section 8.10.).

8.2.

MDF BLOCK ASSIGNMENTS AND JUMPERING

The assignment of MDF blocks depends on the system configuration. Once you have
decided on a layout, write it down on a form attached to the cabinet.
Jumpering on the MDFs is shown in the following diagrams:
- SOPHO iS3010
- SOPHO iS3030

8.3.

..
..

Diagram 340
Diagram 341

CABLE COLOUR CODE AND CONNECTIONS

The colours of the cables which are delivered with the ISPBX are standard for Philips. If
cables are used which are not Philips, the colours of the wires can differ from country to
country. In that case it is advised to consult local sources for information.
There is a difference in the colour code between a cable for external lines and a cable for
connection to a front connector. These codes are shown in diagram 120. As shown in the
diagram a cable can be connected at one end to one F122 connector, or at one end to two
F122 connectors.

9511

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

8-1

For stripping a cable consult diagram 121. The cable stripping instructions are valid for
Philips cables with eight pairs of wires.

8.4.

FRONT CONNECTORS

The front connectors on the PWBs are of the F122 type. For inserting and removing the
front connectors consult diagram 122.
The identification of the front panel connectors of a standard ISPBX board is shown in
diagram 100. Three front connector positions are identified: FA, FB and FC. Each position
is divided in four positions.
Note that at the daughter board also connectors can be present. The connectors at a
daughter board are also identified with FA, FB and FC, but in this case the connectors are
single (and therefore not subdivided).

8.5.

WIRING THE MDF

The connecting (and in some cases also the disconnecting) blocks are supplied as
separate items. In most cases the disconnecting blocks are supplied with wiring to connect
the PCTs.
It is first necessary to form the wires of all incoming cables (from local and external) across
the blocks (see diagram 130) before locating them in the MDF.
To locate a block, simply push it onto the MDF magazine until it locks into position. Cables
from the PWBs are connected to the uppersides of the blocks while the blocks are in
position.
To remove a block, position your forefinger and tumb at one side of the MDF block in the
way as shown in diagram 130. Pull the block towards you with your forefinger, which is
behind the brackets of the block. Repeat this action for the other side of the block.
• Connecting a Wire to a Block
For connecting a wire to an MDF block consult diagram 130 and carry out the following
steps.
Step

Action

1
2

8-2

Feed the cable to its designated block via the rear of the MDF magazine.
Place the wire (unstripped) on the connecting grooves with leaving at least 30
mm on the other side.

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9511

Step

Action

3

Place the connecting tool in the groove of the element, the cutting blade on the
inner side.

4

Push down firmly on the connecting tool, pressing the wire into the groove. The
wire will be cut automatically.

• Disconnecting a Wire from a Block
For disconnecting a wire from an MDF block consult diagram 130 and carry out the
following steps.
Step

Action

1

Remove the extractor from the body of the tool.

2

Place the extractor onto the MDF block.

3

Turn the head of the extractor towards the wire to be removed; while turning pull
up at the same time.

8.6.

LIGHTNING PROTECTION

A cartridge is designed to be plugged onto a connecting block (not a disconnecting block)
on the MDF (see diagram 440). One arrester is required per line. In practice, arresters
would only be used on those lines most likely to be struck by lightning, i.e. external lines.

Note: The MDF concerned must be directly connected to an earth plate, otherwise the
arresters will not provide any protection.

8.7.

MUSIC-ON-HOLD INTERFACE

The Music-On-Hold Interface is a circuit used to connect a tone source, e.g. cassette
recorder, to a line circuit. Figure 8.1. shows the circuit which is required for that purpose.
Music-On-Hold is a projectable facility. The projected line circuit must be known to the
installation engineer. If MOH is required, each peripheral module (PM) in the system must
have one MOH circuit projected. The circuits as depicted in figure 8.1. can be made on site
but it is also possible to use the MOH-I (Music-On-Hold - Interface) board. This board
houses four interface circuits between the ALC circuits for MOH and a tone source. The
board does not use the back panel and can therefore be used in any empty board position
in the system.

9511

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

8-3

The connection to the line circuit should be made at the termination on the MDF.
MDF
2.2 µF

300 Ω

a

2.2 µF

1 MΩ
300 Ω

b

Tone
source
0dB

ALC (PM 0)

a
ALC (PM 1)
b
To interfaces
for other
shelves

a

Figure 8.1. Music-On-Hold Interface.

8.8.

MODEM LINE UNIT (MLU)

The MLU is used to interface up to four modems to the system. It is a PWB having four
V.24 (digital) and four analogue connections and can be inserted in any pre-defined
position. The connectors can be wired as shown in diagrams 430 and 431.

8.9.

DTU AND LTU CONNECTIONS

The DTU is used for a digital trunk connection which is built up of an incoming and outgoing
coax cable. Diagram 420 shows the coax cabling from/to the front connector of the DTU.
Diagram 450 shows the strip with the coax connectors which are to be applied for the 2
Mbit/s connection at the MDF. For assembling the coax connector and mounting it to the
cable, see section 8.10.
If a DTU with an LTU (Line Terminating Unit) is used for a connection with a symmetrical
wire pair on the MDF, consult diagram 401 and diagram 420.
The DTU derives a clock signal from the incoming signal. If the clock of the ISPBX is to be
synchronised with the clock in the incoming signal, connect the coax connector on the DTU
with the upper or lower coax connector on the PMC (Peripheral Module Controller). If one
coax connector is already used, then a second coax connector can not be used.

8-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9511

8.10.

ASSEMBLING THE COAX CONNECTORS

The trunk line connection at the DTU is an F122 connector (2x8 pins) at the front of the
board. This connector provides a 75 ohm asymmetrical connection. The cable used for this
connection must be coaxial as wel as the connector at the MDF. The cable supplied for this
purpose consists of two coax cables. Both ends of the coax cables are terminated with
F122 connectors. The 'B' connector must be removed and the coax cables must be
terminated at the coax connectors at the MDF. The coax cable which is marked with a '1' is
the incoming link and must be terminated at the left coax connector of a pair (see diagram
420). The cable which is marked with a '2' is the outgoing link and must be terminated at
the right coax connector of a pair. Diagram 131 shows the sequence (and the tools) for
assembling the connector and fixing the cable to it. Note that there are two types of coax
cables possible: a cable with a diameter of 3.7 mm and a cable with a diameter of 5.6 mm.
For fixing both types of cables, materials are supplied with the connector. Choose the
materials required for the applied type of cable.
Mount the connector to the cable by following the instructions in diagram 131. The capital
letters in the diagram which are denoted with an asterisk, are explained in more detail:
A* The plastic tube of the cable may not be cut totally through. This prevents the metal
casing to be damaged.
B* Remove the metal casing according to the dimensions given.
C* Push the metal tube in the direction of the connector until it hits the connector. Mind
that the hole in the metal tube is totally filled with the metal casing of the cable.
If the tube is squeezed at the cable, check the dimension of the metal tube by means of the
adjustment tool (denoted with *) shown in diagram 131. The 4.25 mm hole is used in case
of a cable of 3.7 mm and the 6.6 mm hole is used in case of a cable of 5.6 mm. If the
adjustment tool cannot be placed over the metal tube, the squeezing tool has to be
adjusted.

9511

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

8-5

8-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9511

9.

FINISHING INSTALLATION

9.1.

CONNECTING THE OPERATOR POSITION

The following types of operator positions can be connected.
• The Analogue Operator Position and SOPHO-SUPERVISOR 50.
These positions can be connected directly to the PMC with AOC (Analogue Operator
Card), or by means of the MDF and an operator connection box. See diagram 460 for
operator connection box. The maximum distance between the operator position and the
system is 300 m.
• The SOPHO-SUPERVISOR 30.
The SOPHO-SUPERVISOR 30 is connected to the DOC (Digital Operator Card) by
means of the MDF. Note that the SOPHO-SUPERVISOR 30 also can be connected to a
DLC-C/D - LDC line combination or to a DLC-U (no LDC required), which are projected
for this purpose. The maximum cable length between the system and the operator
position is 1000 m.
• SOPHO-SET S375 (In Supervisor Mode).
If a SOPHO-SET S375 D is used as operator position it has to be connected to a DOC or
DLC/LDC line which is projected for Main Common Night Extension. In this case the
connections to the AOC on the PMC are not used.
• SOPHO-SET K365 (In Supervisor Mode).
A SOPHO-SET K365 can be used as operator position. It has to be connected to a
KTLC-A/E circuit which is projected for Main Common Night Extension. In this case the
connections to the AOC on the PMC are not used.
To a DOC only one SOPHO-SUPERVISOR 30 or one SOPHO-SET S375 can be
connected. To an AOC two operator positions can be connected.

9.2.

CPU - RS232C/V.24 INTERFACE CONNECTIONS

The CPU has an F122 connector block on the front side of which the lower three F122s are
used as RS232C/V.24 interfaces. Following configurations are possible:
-

VDU for logging messages;
Serial printer for toll ticket records/logging messages;
Modem;
PC with Maintenance PC, SOPHO SystemManager or Q-Manager software package;
Alarm Unit.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-1

9.2.1.

SSW 300.10 Interface Connections

For SSW 300.10 following rules should be observed:
- Port 0 is not a V.24 port and it presents the system alarms at V.28 level.
- Local SOPHO SystemManager should be connected to port 1 of CPU-ME. When no
Local SOPHO SystemManager is used port 1 can be used for other applications.
- Remote SOPHO SystemManager or Remote Maintenance PC should be connected to
port 2 of CPU-ME. It is not possible to have both connections at the same time, because
they use the same port. When no Remote SOPHO SystemManager or Remote
Maintenance PC are used, port 2 can be used for other applications.
- When serial Toll-Ticketing or the Logging function is used, the output is always send to
port 3 of CPU-ME. When serial Toll-Ticketing and the logging function are used at the
same time, the output of both functions is send to port 3 of CPU-ME. When these
functions are not used, port 3 can be used for other applications.
- The Local Maintenance PC or the Alarm Unit may be connected to port 1, 2 or 3 of the
CPU-ME. When all the ports are occupied, the optional V.24 Interface Card (VIC)
daughter board may be used to connect the Local Maintenance PC or the Alarm Unit.
Following shows the possible devices which can be connected to CPU-ME:
DEVICE
-

PORT

Local SOPHO SystemManager . . . . . . . . . . . . . . . . . . . . . . . .
Remote SOPHO SystemManager . . . . . . . . . . . . . . . . . . . . . .
Local Maintenance PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Maintenance PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Toll-Ticketing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Port 1
Port 2
Any free port
Port 2
Port 3
Port 3
Any free port

9.2.2.

SSW 300.20 Interface Connections

For SSW 300.20 following rules should be observed:
- Port 0 is not a V.24 port and it presents the system alarms at V.28 level.
- The Local Maintenance PC or the Alarm Unit may be connected to port 1, 2 or 3 of the
CPU-ME. When all the ports are occupied, the optional V.24 Interface Card (VIC)
daughter board may be used to provide 3 additional V.24 interfaces (ports 4, 5 and 6).

9-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

The following shows the possible applications which can be connected to CPU-ME:
-

Local SOPHO SystemManager
Remote SOPHO SystemManager
Q-Manager on SOPHO-SUPERVISOR 50E or stand-alone PC
Local Maintenance PC
Remote Maintenance PC
Serial Toll-Ticketing
Logging function
Alarm Unit

Note: The function and configuration of the CPU-ME or VIC V.24 ports can be defined
using the OM commands shown in Table 9.1. (starting from SSW 300.20).
Commands can be entered via an Operator Terminal or via a PC connected to any
free V.24 port. The details of each command can be found in the OM Commands
Manual.
OM COMMAND
FUNCTION
MML

OM CODE

ASBAUD
DIBAUD
ASPORT
DIPORT

1061
1062
1063
1064

Assign baud-rate of CPU-ME or VIC ports
Display baud-rate of CPU-ME or VIC ports
Assign application of CPU-ME or VIC ports
Display application of CPU-ME or VIC ports

Table 9.1. OM Commands used to configure the Functions of CPU-ME or VIC Ports
(Starting from SSW 300.20).

9.3.

V.24 INTERFACE CARD (VIC)

The V.24 Interface Card (VIC) is an optional board and should be used if the three V.24
interfaces on the CPU-ME are not sufficient. If connected, the VIC provides three additional
galvanicly isolated V.24 interfaces, which can be used for connecting any of the
applications that use a V.24 port on the CPU-ME. Figure 9.1. shows the V.24 ports and how
to position the VIC on the CPU-ME.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-3

CPU Board
Front Edge

FAA

Alarms (V.28)

FAB

LOCAL
SOPHO SystemManager

V.24 / V.28 Port 1
REMOTE

FAC V.24 / V.28 Port 2

MAINTENANCE PC

FAD V.24 / V.28 Port 3
SERIAL TOLLTICKETING

Green
Red
Yellow

Port 6

CPU - VIC
Connectors

Alarm
Unit

Port 5
VIC Board
Front Edge

Port 4
V.24
Connectors

Not Used

LEDs

Figure 9.1. Front View of VIC Card Mounting.

The charteristics of the VIC V.24 ports are identical to the CPU-ME V.24 ports.
The ISPBXs are equipped with standard cables with a F122 connector at the CPU side and
a V.24 connector at the other side of the cable. For mounting the connectors see diagram
320.
The standard cable which is mounted in the system between the CPU and the V.24
connector, is equipped for connecting DCE. The signals on the pins of the V24 connector
are given in figure 9.2.
F 122
Pin number

D-connector male
pin number

302
103
301
307
105
303
107
305

GY
BL / BK
GY / BK
BR / BK
YW / BK
WT / BK
GN / BK
PK / BK

CT 102 - GND
CT 104 - RXD
CT 103 - TXD
CT 109 - DCD
CT 106 - CTS
CT 105 - RTS
CT 108 - DTR
CT 107 - DSR

7
3
2
8
5
4
20
6

Generally
used

101
102
104
106
108
304
306
308

RD / BK
RD
BL
YW
GN
WT
PK
BR

CT 125 - CI
CT 142 - TI
CT 141 - LL
CT 113/114 - TSET
CT 115 - RSET
CT 140 - RIL
CT 111 - DSRS
CT 126 - STX

22
25
18
24
17
21
23
11

Only used for
synchronous
or intelligent
Modems

Figure 9.2. V.24 Cable in the ISPBX.

9-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

If DTE (e.g. the Alarm Unit) is to be connected to a V.24 connector, a NULL-Modem cable
(Modem By-pass cable) is required. An example of NULL-Modem cable is given in figure
9.3.
D-connector female
pin number
7
3
2
8
5
4
20
6

D-connector female
pin number
CT 102 - GND
CT 104 - RXD
CT 103 - TXD
CT 109 - DCD
CT 106 - CTS
CT 105 - RTS
CT 108 - DTR
CT 107 - DSR

7
3
2
8
5
*4
20
6

CT 102 - GND
CT 104 - RXD
CT 103 - TXD
CT 109 - DCD
CT 106 - CTS
CT 105 - RTS
CT 108 - DTR
CT 107 - DSR

*

Some printer devices use
for RTS pin 11 instead of pin 4.

Figure 9.3. Example of a NULL-Modem cable.

Note that there can be minor differences between NULL-Modem cables for various devices.
It is adviced to consult the manual(s) of the devices, which are to be connected to the V.24
connectors.
For EPSON printers with interface board 8143 the NULL-Modem cable as given in figure
9.4. should be used.
D-connector female
pin number.
ISPBX side
7
3
2
8
5
4
20
6

D-connector female
pin number
Printer side
CT 102 - GND
CT 104 - RXD
CT 103 - TXD
CT 109 - DCD
CT 106 - CTS

CT 102 - GND
CT 104 - RXD
CT 103 - TXD

CT 108 - DTR
CT 107 - DSR

CT 108 - DTR
CT 107 - DSR

7
3
2
8
5
11
20
6

Figure 9.4. NULL-Modem cable for EPSON Printer with Interface Board 8143.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-5

9.4.

REMOTE INTERFACES HARDWARE

The remote interfaces allow the ISPBX to be controlled from a greater distance via public or
private telephone lines. Figure 9.5. shows the remote interfaces layout.
The following equipment is required when remote applications are used:
- 2 Hayes or Hayes compatible V21/V22/V22bis modems, one at each end of the remote
link;
- Remote terminal, Remote Maintenance PC, Multi Site (Remote) SOPHO SystemManager or printer at remote location;
- Cables. Two cables are required:
. CPU-ME - Hayes Modem V.24 cable (1);
. Remote Item - Hayes Modem V.24 cable (2).
- Public or private telephone line.
CPU-ME
(mother board)

Alarms
PSTN
or
Private Line

1
V.24 / V.28
ports

(1)

Hayes (compatible)
modem

2

Hayes (compatible)
modem

Full duplex

3

V.21/V.22/V.22bis

V.24 cable

Remote

or

PC with MSSSM*

(2)

or

Terminal

or

Printer

Maintenance PC

*

MSSSM : Multi Site SOPHO SystemManager

Figure 9.5. Remote Interfaces Layout.

9.5.

IPH-A AND IPH-B INSTALLATION

The IPH-A and IPH-B (ISDN Protocol Handler) are used as a pair of boards which has to be
connected together by means of two flat cables (34 pol. each) (see diagram 425 and 123).
Always connect the flat cables after the boards are installed in a shelf.

9-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

9.6.

INSERTING AND REMOVING ICs

During installation it can be necessary to install or change PROMs or other types of ICs. If
these ICs are to be inserted in, or removed from, a package as shown in diagrams 140 and
141, follow the procedures in the following subsections.

Note: ICs are very sensitive to static charges. During handling the ICs (PROMs), always
use the bracelet (or antistatic watch with ground connection) as shown in diagram
110.
• Inserting an IC (See Diagram 140)
Step

Action

1

Mount the brackets which are applicable for the IC to be inserted. Apply the 40
pins brackets for the 40 pins ICs, the 28 pins brackets for the 28 pins ICs and the
24 pins brackets for the 24 pins ICs.

2

Tighten the IC in the tool.

3

Insert the IC in the package.

4

Remove the tool and press the IC home with the fingertips.

5

Turn the tool upside down and set the tool on the package.

6

Press the package (using the tool) onto the PCB.

• Removing an IC (See Diagram 141)
Step
1

2
Step

Action
Adjust the legs in the position according to the size of the IC. Before tighten the
screws, place the adjusting plate between the legs. Tighten the screws and
remove the adjusting plate.
Push the levers from each other.
Action

3

Place the tool on the package. The four legs must hit the PCB.

4

Press the tool at the sides with one hand.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-7

5

Move the levers to each other with the other hand. Now the package moves
upwards.

6

Remove the tool.

7

Take the IC from the package. Mind that no pins of the IC are touched by the
hand. (To take the IC out of the package, it is also possible to use the tool for
inserting an IC. In that case it is not necessary to touch the IC by hand.)

9.7.

STRAPPING OPTIONS

Some PWBs are equipped with straps in order to adapt them to local conditions, e.g.
attenuation, impedance, frequency of received pulses etc. See chapter 10 for details.

9.8.

ALARM UNIT

In this section are described: the Alarm Unit itself and Installation aspects of the Alarm Unit.
In each SOPHO iS3010/3030 exchange only one Alarm Unit can be used.

9.8.1.

General

The Alarm Unit is an interface between the CPU and the external alarm input switches. It
also carries visual and acoustical alarm indicators. The Common Answering Night Service
(CANS) relay can be connected to this device too. Furthermore, two switches are mounted
on the Alarm Unit motherboard, e.g.:
- The Emergency bypass switch;
- The buzzer reset switch.
The Alarm Unit is either mains powered or powered by a 48 Volt external supply. This 48V
supply for the Alarm Unit can either be connected to the exchange or to a 48V emergency
battery (optional).
• Alarm Indications
The Alarm Unit carries the following alarm indications:
- Minor Alarm LED;
- Major Alarm LED;
- System Down LED;
- Power ON LED;
- Internal buzzer.

9-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

The Minor alarm LED, the Major Alarm LED, and the System Down LED reflect the status
of the ISPBX alarms. The System Down LED also is alight if the communication with the
CPU is lost.
The Power On LED indicates the status of the Alarm Unit:
- LED on =power on;
- LED off = power off.
The buzzer is used as an additional alarm indicator. It is switched on if the CPU has sent
a buzzer-on message or if communication with the CPU is lost. The buzzer can be
enabled and disabled by means of a DIL switch in the Alarm Unit.
• Relay Contacts Available for the User
The following relay contacts are provided for use by the customer:
- Minor alarm contact;
- Major alarm contact;
- System down contact;
- Buzzer contact;
- Common Answering Night Service (CANS) contact.
The first three contacts are connected in parallel with the associated alarm LEDs. The
buzzer contact is connected in parallel with the internal buzzer. The CANS contact is
switched by an internal CANS relay (maximum contact load: 100mA at 48V DC).
None of these contacts is connected to any internal voltages.
• Two Switches of the Alarm Unit
The two switches of the Alarm Unit have the following functions:
- Emergency bypass switch: this switch can be used to initiate an emergency situation
whereby trunk lines are directly connected to predefined extensions. The switch is
implemented as a push button that is toggling the emergency state on or off. If the
emergency bypass is activated the associated LED is alight, if the bypass is
deactivated the bypass LED is off.
The emergency bypass switch can be enabled or disabled by means of a DIL switch in
the Alarm Unit.
- Buzzer reset switch: this switch can be used to reset the internal buzzer and the buzzer
contact.
• Sense Inputs on the Alarm Unit
The following Sense Inputs are present on the Alarm Unit:
- External alarm sense input 1;
- External alarm sense input 2;
- Buzzer reset sense input;
- Emergency Bypass sense input.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-9

The external alarm inputs allow the connection of customer defined alarms. Alarm sense
input 1 is related to alarm code 1005, whereas alarm sense input 2 is related to alarm
code 1030.
The buzzer reset input can be used to connect an optional external buzzer reset switch.
The emergency bypass input can be used to connect an optional external emergency
bypass switch. The emergency bypass sense input can be enabled or disabled by means
of a DIL switch in the Alarm Unit.

Note: When the emergency bypass sense input is not used, it must be disabled!

9.8.2.

External Connections

The external connections are eccessible after opening the Alarm Unit.
The alarm unit can be opened on the rear side by gently pulling apart the upper and lower
side of the cover. Be careful with the LEDs when replacing the printed wiring board into the
cover.

Note: Always disconnect the primary supply from the Alarm Unit before opening the
cover.
Figure 9.6. gives the lay out of the Alarm Unit's printed wiring board.
DIL switch
8

V.24
Connector

1

Connector blocks
Cable entry

1

14 15

28 Fuse

Mains cord

WARNING : DO NOT OPEN COVER BEFORE DISCONNECTING THE POWER
SUPPLY

Figure 9.6. Layout of The Alarm Unit.

Table 9.2. gives a survey of the user applicable connections, wheras figure 9.7. gives the
position of the relay contacts when the relay is not energized.

9-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

1

2

(Relay not activated)

3

Figure 9.7. Relay Contact Layout.

PIN NUMBER

DESCRIPTION

REMARK

1
2
3

48 V DC power supply input
48 V DC power supply input
not connected

polarity is free
polarity is free
-

4

external alarm 1

-

5

external alarm 1

-

6
7

external alarm 2
external alarm 2

-

8
9

buzzer reset
buzzer reset

-

10
11
12
13

emergency bypass
emergency bypass
minor alarm relay contact 1
minor alarm relay contact 2

see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.

14
15

minor alarm relay contact 3
major alarm relay contact 1

see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.

16

major alarm relay contact 2

see figure 9.6 / table 9.3.

17
18
19
20

major alarm relay contact 3
system down relay contact 1
system down relay contact 2
system down relay contact 3

see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.

21
22

buzzer relay contact 1
buzzer relay contact 2

see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.

23
24
25
26
27
28

buzzer relay contact 3
CANS relay contact 1
CANS relay contact 2
CANS relay contact 3
supply voltage CANS relay
supply voltage CANS relay

see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.
see figure 9.6 / table 9.3.
only use recommended relay
only use recommended relay

Table 9.2. Connector Block description.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-11

Table 9.3. gives the status of the contacts with its function.
FUNCTION

RELAY ACTIVATED

RELAY NOT ACTIVATED

Minor alarm
Major alarm
System down

Minor alarm . . . . off
Major alarm . . . . off
System down . . . off

Minor alarm . . . . on
Major alarm . . . . on
System down . . . on

Buzzer

Buzzer . . . . . . . . off

Buzzer . . . . . . . . on

CANS

CANS

CANS

. . . . . . . . on

. . . . . . . . off

Table 9.3. Switch Conditions.

Note: The sense inputs may not be connected to any external voltages!
How a sense input is activated, by open or by closed loop is depicted in table 9.4.
SENSE INPUT

FUNCTION ACTIVATED

External alarm 1
External alarm 2
Buzzer reset
Emergency bypass

loop closed
loop closed
loop closed
loop open

Table 9.4. Sense Inputs.

For the loop the characteristics as given in table 9.5. are specified.
PARAMETER

SPECIFICATION

minimum resistance open loop
maximum resistance closed loop
Maximum loop current

1 M Ohms
100 Ohms
0.45 mA

Table 9.5. Characteristics of Sense inputs.

9.8.3.

DIL Switches

The function of the DIL switches located inside the Alarm Unit is given in table 9.6. The
position of the DIL switches on the board is depicted in figure 9.5.

9-12

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

SWITCH
NUMBER

DEFAULT

1

off

2
3

off
off

4

on

5

on

6

on

7

on

8

on

DESCRIPTION
off
on
2
off
off
on
off
on
off
on
off
on
off
on
off
on

: CANS rhythm = 1 second on / 4 seconds off
: CANS rhythm = continuously on
3
off . . . . 300 baud
on . . . . 1200 baud
off . . . . 2400 baud
: Emergency bypass switch (on front of the Alarm Unit) disabled
: Emergency bypass switch (on front of the Alarm Unit) enabled
: Emergency bypass sense input enabled
: Emergency bypass sense input disabled. (If input not used it must
be disabled!)
: Internal buzzer disabled
: Internal buzzer enabled
: Wachtdog timer off (only for factory test purposes).
: Wachtdog timer on. For normal operation always 'on'.
: No function
: No function
Table 9.6. DIL Switch Functions.

9.8.4.

CANS

The external CANS relay can be connected to the connector block inside the Alarm Unit.
The power supply of this CANS relay is internally fused with 315 mA / 250 Volts. The
recommended connection for the CANS relay is given in figure 9.8.

24

CANS
RELAY

25 26 27 28

Polarity free

Figure 9.8. Recommended Connection of CANS Relay.

9.8.5.

V.24 Interface

The serial connection between the Alarm Unit and the CPU is according to the V.24
(RS232C) standard. Any of the V.24 D-connectors in the ISPBX cabinet (which are
connected to the CPU) can be used for this purpose. Note that the upper port on the CPU
board is not used for V.24 connections. The Alarm Unit must be connected to a V.24 Dconnector by means of a Null-Modem (Modem By-pass) cable which can be delivered with
the Alarm Unit. This type of cable is also known as cross cable. The layout of the cable is
given in figure 9.3.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-13

9.8.6.

Power Connections

The Alarm Unit can be powered by means of the Mains power or by means of an external
48V power source. This 48V power source can be the ISPBX. (The 48V termination at the
MDF, from of the Power Supply, should be used, see diagram 321.) If the Alarm Unit is
connected to the ISPBX, there are requirements for the resistance of the cabling. Two
situations are depicted in figure 9.9. with the calculation rules to determine the maximum
allowed resistance of the cables.
ISPBX

V.24 Connection

48V Power Conn. 'a'

Alarm
Unit
Ra < 40 ohm

ISPBX

V.24 Connection

48V Power Conn. 'a'

Alarm
Unit

48V Relay Power 'b'

CANS Relay

10Ra + Rb < 260 ohm

Figure 9.9. Recommended Connection of CANS Relay.

9.8.7.

Power up

After power up the Alarm Unit performs several hardware tests and software tests. After
satisfying completion of these tests the Alarm Unit is initialized. All alarms are switched off
except for system down. When communication with the CPU has been established, the
system down LED is switched off.
If one of the tests fails, an error state is entered. This is indicated by flashing LEDs.

9.9.

START-UP AND JOB COMPLETION

After installing the equipment, carry out the following steps to make the system operational.
Step
1

9-14

Action
Connect the Emergency Battery.
In SOPHO iS3010/3030 the red wire must be connected to the terminal marked
with a '+' and the black wire to the terminal marked with a '-' (see diagram 321).

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

Step

Action

2

Switch on the power to the system. The LEDs on the CPU light.

3

Set the operator position to the AM (Administrative) mode. Key in 6020 <SP><E> to
read out the major alarms and after that 6021 <SP><E> to read out the minor
alarms. If an alarm code appears consult the OM commands manual for the related
meaning and press the AM button again to return to AM mode.

4

Key in 6029 <SP><E> to clear the alarms and after that 6027<SP><E> to clear the
history buffer. The system will be operational.

As soon as you have completed the installation, clear the site of packing materials, surplus
equipment and dust that you may have caused, through drilling for example. The working of
the system should then be demonstrated to the customer's satisfaction.
All necessary paperwork should be completed at this stage.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9-15

9-16

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

10.

DIL SWITCHES AND STRAP SETTINGS

A number of boards in the ISPBX have DIL switches and/or straps. These switches or
straps are set to the correct position in the factory. However it may be necessary to check
the position and, if wrong, to correct the position during installation or replacement of the
boards.
This subject contains all the boards which do have those switches/straps. Also directions
are given how to set those switches/straps to suit a particular mode of application.
In general the PCT boards have more than one circuit mounted; so in that case the
switches/straps have to be set for each circuit individually.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-1

10.1.

ANALOGUE LINE CIRCUIT-E

The analogue Line Circuit-E (ALC-E) is a board that contains 16 peripheral circuits. This
ALC-E carries one strap that determines whether this ALC is actually using 8 or 16 circuits.
In this way an ALC-E can also be used as an ALC-A. Figure 10.1.1. gives the strap
location.
MARK

BP

FAD

FCA

BB

X1-1
103

Note :

101

The strap is drawn in the position for 16 Circuits.
For 8 Line Circuits place the strap on 102-103.

Figure 10.1.1. Strap Location ALC-E.

10-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.2.

ANALOGUE TRUNK UNITS

10.2.1.

ATU-EM (2 Wire)
MARK

X 4.1
X 4.2
X 4.3
X 4.4
X 6.1
X 6.2
X 6.3
X 6.4
X 7.1
X 7.2
X 7.3
X 7.4

X 3.1
X 3.2
X 3.3
X 3.4

X 9.1
X 9.2
X 9.3
X 9.4

BP

X 1.1
X 1.2
X 1.3
X 1.4
X 2.1
X 2.2
X 2.3
X 2.4
FBC

FCA

X 5.1
X 5.2
X 5.3
X 5.4

X 8.1
X 8.2
X 8.3
X 8.4
BB

= Open
= Closed

Figure 10.2.1. Strap Location.

Note: The second identifier of the straps (1... 4) indicates the ATU circuit 0... 3.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-3

E&M

TRANSMITTED ON M-WIRE
IDLE

SIGNALS

SIGNAL

BUSY

RECEIPT

TI

TB

TM

E

B

M

O

E

B

M

O

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

V
V
V
V
°
°
°
°

V
V
°
°
°
°
V
V

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

Y
°
°
Y
°
Y
Y
°

°
Y
Y
°
Y
°
°
Y

BATTERY
MINUS /
OPEN LINE
SIGNALLING

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

V
V
V
V
°
°
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

Y
°
°
Y
°
Y
Y
°

°
Y
Y
°
Y
°
°
Y

CLOSED
M/MM LOOP /
OPEN LINE
SIGNALLING

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

V
V
V
V
°
°
°
°

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

V
V
°
°
°
°
V
V

Y
°
°
Y
°
Y
Y
°

°
Y
Y
°
Y
°
°
Y

OPEN LINE /
EARTH
SIGNALLING

?

HEADER LEGEND
TI
TB
TM
E
B
M
O

=
=
=
=
=
=
=

TONE ON IDLE
TONE ON BUSY
TONE ON MAINS FAIL
EARTH
BATTERY MINUS
M/MM LOOP
OPEN LINE

CARRIER EQUIPMENT
RECEIVES TONE
RECEIVED

EARTH OR E/EE LOOP

ON E-WIRE

OPEN LINE

TABLE LEGEND
V
Y
+
°

=
=
=
=
=

PARAMETER REQUIRED ?
YES
STRAP PRESENT (CLOSED)
STRAP ABSENT (OPEN)
NOT APPLICABLE

CARRIER EQUIPMENT
RECEIVES NO TONE
RECEIVED

OPEN LINE

ON E-WIRE

EARTH OR E/EE LOOP

Table 10.2.1a. ATU-EM (2-WIRE)

Note: Table 10.2.1a. and 10.2.1b. form one table.
In table 10.2.1a one can search for the parameters required; then the corresponding strap setting can be found on the same horizontal line in table 10.2.1b.

10-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

STRAPS X 1...9
1

2

3

4

5

+
+
+
+
+
+
+
+

-

+
+
+
+
-

+
+
+
+

-

-

+
+
+
+
+
+
+
+

+
+
+
+
-

+
+
+
+

-

-

-

+
+
+
+
-

+
+
+
+

+
+
+
+
+
+
+
+

6

7

See
table
below

See
table
below

See
table
below

8

9

+
+
+
+
-

+
+
+
+

+
+
+
+
-

+
+
+
+

BATTERY
MINUS /
OPEN LINE
SIGNALLING

+
+
+
+
-

+
+
+
+

CLOSED
M/MM LOOP /
OPEN LINE
SIGNALLING

OPEN LINE /
EARTH
SIGNALLING

RESISTANCE
(IN Ω )
BETWEEN M AND
EARTH
+

-

-

+

+
+

-

1240
620
620
0

- Vb

MM

1780 1240
1160 620
1160 620
540
0

Table 10.2.1b. ATU-EM (2-WIRE).

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-5

10.2.2.

ATU-EM (4 Wire)
E&M

TRANSMITTED ON M-WIRE
IDLE

SIGNALS

SIGNAL

BUSY

RECEIPT

TI

TB

TM

E

B

M

O

E

B

M

O

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

V
V
V
V
°
°
°
°

V
V
°
°
°
°
V
V

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

Y
°
°
Y
°
Y
Y
°

°
Y
Y
°
Y
°
°
Y

BATTERY
MINUS /
OPEN LINE
SIGNALLING

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

V
V
V
V
°
°
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

Y
°
°
Y
°
Y
Y
°

°
Y
Y
°
Y
°
°
Y

CLOSED
M/MM LOOP /
OPEN LINE
SIGNALLING

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

V
V
V
V
°
°
°
°

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

V
V
°
°
°
°
V
V

°
°
V
V
V
V
°
°

°
°
°
°
°
°
°
°

°
°
°
°
°
°
°
°

°
°
V
V
V
V
°
°

V
V
°
°
°
°
V
V

Y
°
°
Y
°
Y
Y
°

°
Y
Y
°
Y
°
°
Y

OPEN LINE /
EARTH
SIGNALLING

?

HEADER LEGEND
TI
TB
TM
E
B
M
O

=
=
=
=
=
=
=

TONE ON IDLE
TONE ON BUSY
TONE ON MAINS FAIL
EARTH
BATTERY MINUS
M/MM LOOP
OPEN LINE

CARRIER EQUIPMENT
RECEIVES TONE
RECEIVED

EARTH OR E/EE LOOP

ON E-WIRE

OPEN LINE

TABLE LEGEND
V = PARAMETER REQUIRED ?
Y = YES
+ = CLOSED (pos. 101 & 102)
- = OPEN
(pos. 102 & 103)
° = NOT APPLICABLE

CARRIER EQUIPMENT
RECEIVES NO TONE
RECEIVED

OPEN LINE

ON E-WIRE

EARTH OR E/EE LOOP

Table 10.2.2a. ATU-EM (4-WIRE).

10-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

STRAPS X 1...13
1

2

3

4

5

+
+
+
+
+
+
+
+

-

+
+
+
+
-

+
+
+
+

-

-

+
+
+
+
+
+
+
+

+
+
+
+
-

+
+
+
+

-

-

-

+
+
+
+
-

+
+
+
+

+
+
+
+
+
+
+
+

6

7

See
table
below

See
table
below

See
table
below

8

9

+
+
+
+
-

+
+
+
+

+
+
+
+
-

+
+
+
+

+
+
+
+
-

+
+
+
+

10 11 12 13

See
table
below

See
table
below

OPEN LINE /
EARTH
SIGNALLING

See
table
below

See
table
below

BATTERY
MINUS /
OPEN LINE
SIGNALLING

See
table
below

CLOSED
M/MM LOOP /
OPEN LINE
SIGNALLING

-

-

+

-

+

-

UNAMPLIFIED MODE a / b WIRES
AMPLIFIED
MODE a / b WIRES
AMPLIFIED
MODE c / d WIRES
UNAMPLIFIED MODE c / d WIRES

RESISTANCE
(IN Ω )
BETWEEN M AND
EARTH
1240
620
620
0

- Vb

MM

1780 1240
1160 620
1160 620
540
0

+

-

-

+

-

+

+
+

-

+

+

-

-

*)

+

BIT X OF 4-WIRE COMMAND BYTE=0 *)
BIT X OF 4-WIRE COMMAND BYTE=1 *)
STRAP PRESENT WHEN X5 IS PRESENT
NOT ALLOWED

MM-WIRE GOES TO EARTH FOR COMPANDER

Table 10.2.2b. ATU-EM (4-WIRE).

Note: Table 10.2.2a and 10.2.2b form one table.
In table 10.2.2a one can search for the parameters required; then the corresponding strap setting can be found on the same horizontal line in table 10.2.2b.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-7

MARK

101
102
103

X 13.1
101
102
103

BP

X 12.1

X 13.2
X 12.2
X 13.3
X 12.3
X 13.4
FAD
X 12.4

X 7.1
X 6.1
X 2.1

X 1.1
X 5.1

X 4.1
X 3.1
X 10.1
X 11.1

X 7.2
X 6.2
X 2.2

X 1.2
X 5.2

X 4.2
X 3.2
X 10.2
X 11.2

X 7.3
X 6.3
X 2.3

X 1.3
X 5.3

X 8.4
X 8.3
X 8.2
X 8.1

BB

FCA

X 7.4
X 6.4
X 2.4

101
102
103

= Open (-)

X 4.3
X 3.3
X 10.3
X 11.3

X 1.4
X 5.4

101
102
103

X 9.1
X 9.2
X 9.3
X 9.4

X 4.4
X 3.4
X 10.4
X 11.4

= Closed (+)

Figure 10.2.2. Strap Location.

Note: The second identifier of the straps (1... 4) indicates the ATU circuit 0... 3.

10-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.2.3.

ATU-CH02
MARK

BP
X 1-1

X 2-1

X 2-2

X 1-2

FBC
X 1-3

X 2-3
BB

X 2-4

X 1-4

Figure 10.2.3. Strap Location.

Notes: - The second identifier of the straps (1... 4) indicates the ATU circuit 0... 3.
- The straps of ATU 0 and 1 are drawn in the simultaneous signalling position; the
straps of ATU 2 and 3 are drawn in the loop signalling position.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-9

10.2.4.

ATU-ST26

• Long Line Adjustment

CIRCUIT

INSTALLED

OPEN

INSTALLED

1
2
3
4

X1-1
X1-2
X1-3
X1-4

X1-5
X1-6
X1-7
X1-8

X2-1 / 101-102
X2-2 / 101-102
X2-3 / 101-102
X2-4 / 101-102

Table 10.2.3. Long Line Adjustment.

• Short Line Adjustment

CIRCUIT

INSTALLED

OPEN

INSTALLED

1
2
3
4

X1-5
X1-6
X1-7
X1-8

X1-1
X1-2
X1-3
X1-4

X2-1 / 102-103
X2-2 / 102-103
X2-3 / 102-103
X2-4 / 102-103

Table 10.2.4. Short Line Adjustment.

• Test/Hold Current

CIRCUIT

40/23 mA
JUMPER INSTALLED ON

22/12 mA
JUMPER INSTALLED ON

1
2
3
4

X2-5 / 101-102
X2-6 / 101-102
X2-7 / 101-102
X2-8 / 101-102

X2-5 / 102-103
X2-6 / 102-103
X2-7 / 102-103
X2-8 / 102-103

Table 10.2.5. Test/Hold Current.

10-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

103 101 103 101
X2-1

X1-1

X1-2

X1-5

X1-6

BP

X2-5

103 101 103 101
X2-2

X2-6

FBC
103 101 103 101
X2-3

X1-2

X2-7

X1-8

BB
103 101 103 101

X1-3

X1-4

X2-4

X2-8

Figure 10.2.4. Strap Location.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-11

10.2.5.

ATU-AS36

• Long Line Adjustment
CIRCUIT

JUMPER TO BE INSTALLED JUMPER POSITION ”OPEN”

1
2
3
4

X1-13
X1-14
X1-15
X1-16

X1-9
X1-10
X1-11
X1-12

Table 10.2.6. Long Line Adjustment.

• Short Line Adjustment
CIRCUIT

JUMPER TO BE INSTALLED JUMPER POSITION ”OPEN”

1
2
3
4

X1-9
X1-10
X1-11
X1-12

X1-13
X1-14
X1-15
X1-16

Table 10.2.7. Short Line Adjustment.

• Impulse Dialling In
To enable ”impulse dialling in”, install the following jumpers (in case of GSD).
If a jumper position is left open ”impulse dialling in” is disabled (in case of UFS, 12KHz).
CIRCUIT

A-WIRE DETECTION

B-WIRE DETECTION

1
2
3
4

X1-17
X1-18
X1-19
X1-20

X1-5
X1-6
X1-7
X1-8

Table 10.2.8. Impulse Dialling In.

• The Wetting Circuit
If a jumper is installed the ”Wetting circuit” (43 kΩ) is enabled (in case of UFS).
If a jumper is not installed the ”Wetting circuit” is disabled (in case of GSD).
Table 10.2.9 gives the jumpers in relation to the circuits.

10-12

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

CIRCUIT

WETTING CIRCUIT JUMPER

1
2
3
4

X1-1
X1-2
X1-3
X1-4
Table 10.2.9. Wetting Circuit Jumper.
MARK

FAA
BP

X1-5
X1-17
X1-1
X1-9

X1-10

X1-13

X1-14

X1-6
X1-18
X1-2

FBC

X1-7
BB

X1-19
X1-3
X1-16
X1-12

X1-15
X1-11

X1-8
X1-20
X1-4

Figure 10.2.5. Strap Location.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-13

10.2.6.

ATU-IL01/IL03/IL04/IL13
MARK

X1-4
BP

X1-3
X1-1

X1-2
X2-3
X2-4
X2-1

X2-2

FBC

X3-3
X3-4

X3-1

BB

X3-2
X4-4
X4-3

X4-1

X4-2

Figure 10.2.6. Strap Location.

The first identifier of the straps (1... 4) indicates the ATU circuit 0 ... 3.
For all circuits the following applies:
- X . -1 : installed
: Long Line Outgoing
not installed : Short Line Outgoing
- X . -2 : installed
: Long Line Incoming
not installed : Short Line Incoming
- X . -3 : may never be installed
- X . -4 : may never be installed

10-14

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.2.7.

ATU-IL23

To make the software program neutral with respect to the external ATU-IL side, straps
X1-1 (3,5,7) and X1-2 (4,6,8) adapt the attenuation of the transmission paths to the 'short
line' or 'long line' adjustment. See figure 10.2.7. for the strap positions.
There are a number of possibilities for the transmission paths which can be adjusted by
presence or absence of straps. These straps have the following meaning:
X1-1 (3,5,7)

If positioned between 101 and 102:
The outgoing direction (via the a/b wires) works in the 'long line'
adjustment.
If positioned between 102 and 103:
the outgoing direction works in the 'short line' adjustment.

X1-2 (4,6,8)

If positioned between 101 and 102:
The incoming direction (via the c/d wires) works in the 'long line'
adjustment.
If positioned between 102 and 103:
the incoming direction works in the 'short line' adjustment.

The ATU-IL23 mode of operation can be selected as follows:
Mode:

X1-9 between:

X1-10 between:

SSAC15-A
SSAC15-D / CEPT-L1
Selftest
Factory test

101-102
102-103
101-102
102-103

102-103
102-103
101-102
101-102

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-15

101
102
103

X1-2

X1-3

101
102
103

X1-4

101
102
103

X1-5

101
102
103

X1-6

101
102
103

X1-1

101
102
103

BP

LEDs

FBC

101
102
103
X1-10X1-9
BB

X1-7

101
102
103

X1-8

101
102
103

Figure 10.2.7. Strap positions ATU-IL23.

10-16

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.2.8.

ATU-LB12

Figure 10.2.8. shows the straps for 50 Hz Ringing Current of the ATU-LB12.

Note: The straps are drawn in the position for 50 Hz ringing current; the undrawn position
is valid for 25 Hz ringing current.
MARK

BP

FBC

X1-1
103

101

103

101

BB

X1-2

BU2

BU1

Figure 10.2.8. Straps for 50 Hz Ringing Current ATU-LB12.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-17

10.2.9.

ATU-PSI

An ATU-PSI is an 8-wire interface which connects the ISPBX to a front door opening
system or an emergency call signalling system. Distinction of both systems has to be made
by seven straps.
Though the ATU-PSI is not a trunk unit, the control corresponds to that of other ATUs. For
this reason this type of PCT is yet classified to the ATUs. The abbreviation ATU-PSI refers
to the Private Switching Interface function.
The door opening system enables a speech path via the front door intercom and opening of
the front door. The procedure is as follows:
If the external door-bell button is pressed, a speech path to the door intercom can be
established by dialling the ATU-PSI answering number from an extension. Pressing the
enquiry button activates the ALC, fitted to the ATU-PSI for the external signalling, to send
ringing current to the circuitry for external signalling. The front door will be opened by a
continuous or intermittent signal.
The emergency call signalling system can be dialled from an extension, effecting an
acoustic alarm sounding continuously or intermittent. When the answering number of the
ATU-PSI is dialled, a speech path to the caller will be established and the alarm will be
switched off.
The continuous or intermittent signal, used for door opening or alarming, has been derived
from the ringing current rhythm. The pulse time, detected by the call detector, has been
extended by two delay circuits. One circuit lengthens the pulse time by 1,5 s for the
intermittent signal, the other by at least 4 s for the continuous signal.

Note: All straps are drawn in the position for front door opener with intermitting
m - contact after answering.
By means of seven straps discrimination is made between the front door opening system
and the emergency call signalling system, refer to figure 10.2.9. for positions. Care should
be taken that no other connections are made than mentioned below.
- For the front door opening system the following straps have to be fitted:
. X1-1 between 101 and 201;
. X1-1 between 103 and 203;
. X1-1 between 104 and 204;
. X1-1 between 106 and 206;
. X1-2 between 105 and 106.

10-18

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

BP

X1-2
101

106

FBC

101

106

X1-1
201

101
BB

206

106

Figure 10.2.9. Strap Location.

A choice has to be made out of one of the four following manners of door opening (=
operation of the M relay):
- M relay intermitting, only after answering via the intercom:
. X1-2 between 101 and 102;
. X1-2 between 103 and 104.
- M relay intermitting, regardless of answering:
. X1-2 between 101 and 102;
. X1-2 between 103 and 203.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-19

- M relay continuously operating; only after answering via the intercom:
. X1-2 between 101 and 201;
. X1-2 between 103 and 104.
- M relay continuously operating, regardless of answering:
. X1-2 between 101 and 201;
. X1-2 between 103 and 203.
- For the emergency call signalling system the following straps have to be fitted:
. X1-1 between 201 and 202;
. X1-1 between 102 and 103;
. X1-1 between 204 and 205;
. X1-1 between 105 and 106;
. X1-2 between 105 and 205;
. X1-2 between 103 and 203.
A choice has to be made out of one of the two following manners of emergency call
signalling (= operation of the M relay):
- M relay intermitting: X1-2 between 101 and 102;
. M relay continuously operating: X1-2 between 101 and 201.
Figure 10.2.10. shows the possible strappings for control of the speech path and the door
opener or acoustic alarm.
Intermitting
Continuous

102
201
203

101
103
104

MRELAY

FLIPFLOP

205

AND
GATE

STRELAY

106
105

I

Figure 10.2.10. Straps X1-2 for The Speech Path and The External Signal.

10-20

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.2.10.

ATU-ST03

To adapt each of the four ATU-ST03 circuits to the 2-wire or 4-wire mode of operation the
straps has to be set according to table 10.2.10.
In figures 10.2.11. and 10.2.12. the straps LKA ... LKK are given as A ... K; the prefix
indicates the circuit number; e.g. strap 3.D indicates strap LKD of circuit 3.

STRAPS

2-WIRE MODE

4-WIRE MODE

LKA
LKB
LKC

Absent
Pin 1 & 2
Pin 2 & 3

Present
Pin 2 & 3
Pin 1 & 2

LKD
LKE

Pin 2 & 3
Pin 1 & 2

Pin 1 & 2
Pin 2 & 3

LKF
LKG
LKH
LKJ
LKK

Present
Present
Absent/Present
Pin 1 & 2
Pin 1 & 2

Absent
Absent
Absent/Present
Pin 2 & 3
Pin 2 & 3

Table 10.2.10. Settings for 2-wire or 4-wire mode .

The straps LKA ... LKK serve the following:
- LKA and LKB serve for the selection of DC signalling via the a and b wires (2-wire) or the
a/b and c/d wires (4-wire).
- LKC and LKD select the source and terminating impedances.
- LKE selects the transformer DC current cancellation for 2-wire mode.
- LKF selects the duplexor circuit (hybrid) for the 2-wire mode.
- LKG selects the level adaptors for the 2-wire or 4-wire mode.
- LKJ and LKK serve for reversed connection of the polarized seizure detector, which is
necessary for correct functioning due to the cross connected a/b and c/d wires in the 4wire mode.
- LKH determines whether the pads for an unamplified line are included or not in the 4-wire
mode. For long line compensation or in case of an unamplified line the strap is absent,
otherwise present.
In figures 10.2.11. and 10.2.12. the circuits are strapped for unamplified lines.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-21

MARK

1.G

1.K

1.D
1.A 1.B 1.J

BP
1.H

2.B 2.A

2.K 2.J
1.E

1.C

1.F

2.E
2.G

2.H

2.D

2.C
3.G

2.F

3.H

3.D

FBC

3.C
3.E

3.F

4.E
BB

3.B

3.A

3.J

4.K 4.J

3.K

4.A

4.G

4.H

4.C 4.F 4.D

4.B

Figure 10.2.11. 2 - Wire Mode Strap Setting.

10-22

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

1.G

1.K

1.D
1.A 1.B 1.J

BP
1.H

2.B 2.A

2.K 2.J
1.E

1.C

1.F

2.E
2.G

2.H

2.D

2.C
3.G

2.F

3.H

3.D

FBC

3.C
3.E

3.F

4.E
BB

3.B

3.A

3.J

4.K 4.J

3.K

4.A

4.G

4.H

4.C 4.F 4.D

4.B

Figure 10.2.12. 4 - Wire Mode Strap Setting.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-23

10.2.11.

ATU-G

The Analogue Trunk Unit-General (ATU-G) can replace a number of ATUs with signalling
types AS (=ALS70/EO), SS and PD. Additionally the ATU-G provides the metering and
emer-gency switch-over functions and therefore it can replace a number of Metering Circuit
(MC) and Metering Circuit-Emergency Switch-over Unit (MCE) boards.
Table 10.2.11. shows the existing ATU boards which can be replaced by the ATU-G and
the MC(E) functions the ATU-G provides when strapped as a certain ATU.
COUNTRY

ATU

REMARKS

MC(E)

International

AS01
SS01
PD11

Italy

AS21
SS01

Also combination possible:
4×SS01 + 4×AS21

D

Belgium

AS24
SS04

Also combination possible:
4×AS24 + 4×SS02
Extra Long Line adaptation
included

F

Netherlands

AS0B
SS0B

Extra Long Line adaptation
included

A

Switzerland

AS2E
SS0E
PD2E

SS0E replaces the PD2E.

D

A/D/F/G

Table 10.2.11 Boards Replaced by ATU-G.

There are 8 DIP switches (S1.1 ... S1.8) present, which can be used to select the required
signalling type and transmission plan; see table 10.2.12ab. When the DIP switches are
used the information for initialisation of the ATU-G is loaded from a ROM on the board.

Note : For SSW 300 the required signalling type and transmission plan can also be
downloaded from the PPU. Then all 8 switches must be set to OFF.

10-24

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

REMARKS
Initialisation by
PPU

TYPE OF
ATU

METERING

SWITCH S1.
1 2 3 4 5 6 7 8

16 kHz

0 0 0 1 0 0 1 0

no metering

0 0 0 1 0 0 1 1

16 kHz

0 0 1 1 0 0 1 1

ATU-SS04

no metering

0 0 1 0 1 0 1 1

ATU-SS04

16 kHz

0 0 1 0 1 1 0 0

ATU-AS24

no metering

0 0 1 0 1 1 0 1

4×SS04 +
4×AS24

16 kHz

0 0 1 1 0 1 0 1

ATU-SS01

no metering

0 0 0 0 0 0 0 1

ATU-SS01

50 Hz

MD1

0 0 0 0 0 0 1 0

ATU-SS01

50 Hz

MD2

0 0 0 0 0 0 1 1

ATU-SS01

12 kHz

MD1

0 0 0 0 0 1 0 0

ATU-SS01

12 kHz

MD2

0 0 0 0 0 1 0 1

ATU-SS01

16 kHz

MD1

0 0 0 0 0 1 1 0

ATU-SS01

16 kHz

MD2

0 0 0 0 0 1 1 1

ATU-AS01

no metering

ATU-AS01

50 Hz

MD1

0 0 0 0 1 0 0 1

ATU-AS01

50 Hz

MD2

0 0 0 0 1 0 1 0

ATU-AS01

16 kHz

MD1

0 0 0 0 1 0 1 1

ATU-AS01

16 kHz

MD2

0 0 0 0 1 1 0 0

ATU-PD11

no metering

ATU-PD11

50 Hz

MD1

0 0 0 1 0 1 0 1

ATU-PD11

50 Hz

MD2

0 0 0 1 0 1 1 0

ATU-PD11

12 kHz

MD1

0 0 0 1 0 1 1 1

ATU-PD11

12 kHz

MD2

0 0 0 1 1 0 0 0

ATU-PD11

16 kHz

MD1

0 0 0 1 1 0 0 1

ATU-PD11

International

0 0 0 1 0 0 0 1

4×AS24+
4×SS04

International

no metering

ATU-AS24

International

0 0 0 0 0 0 0 0

ATU-SS04

Belgium-ELL

---

ATU-SS04
Belgium

---

16 kHz

MD2

0 0 0 1 1 0 1 0

0 0 0 0 1 0 0 0

0 0 0 1 0 1 0 0

1=ON; 0=OFF.

Continued

Table 10.2.12a Settings for Signalling Type and Transmission Plan.
The metering range indicates the sensitivity of the metering circuit. MD1 = Metering
Detection - high sensitivity, Range 2 = Metering Detection - low sensitivity.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-25

REMARKS
Initialisation by
PPU

TYPE OF
ATU

METERING

SWITCH S1.
1 2 3 4 5 6 7 8

0 0 0 0 0 0 0 1

12 kHz

0 0 0 0 0 1 0 0

no metering

0 1 0 0 0 1 0 0

8×AS21

12 kHz

0 1 0 0 0 1 0 1

4×SS01 +
4×AS21

no metering

0 0 1 0 0 1 1 0

4×SS01 +
4×AS21

12 kHz

0 0 1 0 0 1 1 1

ATU-SS0B

no metering

0 0 0 1 1 0 1 1

ATU-SS0B

50 Hz

0 0 0 1 1 1 0 0

ATU-AS0B

no metering

0 0 0 1 1 1 0 1

ATU-AS0B

50 Hz

0 0 0 1 1 1 1 0

ATU-SS0B

no metering

0 0 1 0 1 1 1 0

ATU-SS0B

50 Hz

0 0 1 0 1 1 1 1

ATU-AS0B

no metering

0 0 1 1 0 0 0 0

ATU-AS0B

50 Hz

0 0 1 1 0 0 0 1

ATU-SS0E

no metering

0 0 1 0 0 0 1 1

ATU-SS0E

12 kHz

0 0 1 0 0 1 0 0

ATU-AS2E

Switzerland

no metering

8×AS21

Netherlands-ELL

0 0 0 0 0 0 0 0

ATU-SS01

Netherlands

---

ATU-SS01

Italy

---

no metering

0 0 1 0 0 1 0 1

1=ON; 0=OFF.
Table 10.2.12b Settings for Signalling Type and Transmission Plan.
The metering range indicates the sensitivity of the metering circuit. MD1 = Metering
Detection - high sensitivity, Range 2 = Metering Detection - low sensitivity.

10-26

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

Factory test
connector

FAD

8 7 6 5 4 3 2 1
S1

BB

FCA

Figure 10.2.13. DIP Switch Location ATU-G.

1

2

3

4

5

6

7

8
Off
On

Black indicates the position of the switch.

Figure 10.2.14. Detail of DIP Switch S1.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-27

10.3.

DIGITAL TRUNK UNITS

10.3.1.

DTU-CA

The straps are used to connect the cable shields of the incoming and outgoing cable to
ground or to leave the cable shields floating.
The cable shields are grounded, when the straps are on the positions as shown in the
diagram below.
MARK

factory
test only

BP

203 201
X1-1
103 101

FBA

BB

FC 101

Figure 10.3.1. Strap Location.

10-28

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.3.2.

DTU-PR

The straps are used to connect the cable shields of the incoming and outgoing cable to
ground or to leave the cable shields floating.
The cable shields are grounded, when the straps are on the positions as shown in the
diagram below.
MARK

factory
test only

BP

203 201
X1-1
103 101

FBA

BB

FC 101

Figure 10.3.2. Strap Location.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-29

10.3.3.

DTU-PU

The Digital Trunk Unit for Primary Rate Universal (DTU-PU) can operate as a DTU-CA or
DTU-PR. There are two versions of the DTU-PU: version 1 and version 2.
The DTU-PU carries a DIP switch block (S.1) and a group of eight straps (X1.1):
- S1. : The functions are given in table 10.3.2. (version 1) and table 10.3.3. (version 2).
- X1.1 : Used to change the impedance of the transmission interface from 75 Ω to 120 Ω
and vice versa: see table 10.3.1.
STRAP X1.1
101-201
102-202
103-203
104-204
105-205
106-206
107-207
108-208

DEFAULT SETTING

CHANGE

not placed: 120 Ω Outgoing

placed: 75 Ω Outgoing

not placed: 120 Ω Incoming

placed: 75 Ω Incoming

placed: 120 Ω Outgoing

not placed: 75 Ω Outgoing

placed: 120 Ω Incoming

not placed: 75 Ω Incoming

Table 10.3.1. Strap Settings X1.1.

The mode of operation (DTU-CA or PR) of the DTU-PU is selected as follows:
- Version 1:
. DTU-CA :
. DTU-PR :
- Version 2:
. DTU-CA :
. DTU-PR :

close switch S1.4 (enable the Channel Associated mode);
open switch S1.4 (disable the Channel Associated mode).

close switch S1.4 (enable the Channel Associated mode) and
open switch S1.5 (disable the Common Channel mode);
open switch S1.4 (disable the Channel Associated mode) and
open switch S1.5 (disable the Common Channel mode).

Note: The setting of the DIS-CRC switch (S1.5 for version 1 or S1.6 for version 2) depends
on the ability of the destination to accept CRC4 (e.g. for APNSS the DIS-CRC switch
should be closed; the ACU does not accept CRC4).

10-30

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

SWITCH

SIGNAL
NAME

S1.1

SH-BER

Determines if French BER detection
levels (shift BER) are used.

Disable shift BER

S1.2

EN-CLK

Determines if backpanel clock
reference is to be used (always clock
signal at frontconnector).

No clock reference at
back panel.
*)

Clock also routed to
back panel.

Disable remote test
loop.
*)

Enable remote test
loop.
Enable Channel
Associated Mode.

MEANING

OPEN / OFF

CLOSED / ON
*) Enable shift BER

S1.3

Offers a remote test loop to the other
SETLOOP side (DTU input connected to DTU
output).

S1.4

CA-MODE

Determines if DTU operates in the
transparent mode or in CA mode.

Disable Channel
Associated Mode. *)

S1.5

DIS-CRC

Determines if 4 bit CRC check is
used on bit 1 of TS0.

Enable CRC4.

Isolation purpose.

-

-

S1.6

*) Disable CRC4.

S1.7

SH-OUT

Determines if outgoing transmission
shield is connected to ground.

Outgoing shield not
connected to GND.

Outgoing shield connected to GND.
*)

S1.8

SH-IN

Determines if incoming transmission
shield is connected to ground.

Incoming shield not
connected to GND.

Incoming shield connected to GND.
*)

*) means 'default setting'.
Table 10.3.2. DIP Switch Settings S1.1 ... S1.8 (DTU-PU version 1).

SWITCH

SIGNAL
NAME

S1.1

SH-BER

MEANING

OPEN / OFF

CLOSED / ON

Disable shift BER

not used.

S1.2

Determines if French BER detection
levels (shift BER) are used.

*) Enable shift BER

-

-

Disable remote test
loop.
*)

Enable remote test
loop.

S1.3

Offers a remote test loop to the other
SETLOOP side (DTU input connected to DTU
output).

S1.4

CA-MODE

Determines if DTU operates in the
transparent mode or in CA mode.

Disable Channel
Associated Mode. *)

Enable Channel
Associated Mode.

S1.5

CC-MODE

Determines if DTU operates in the
transparent mode or in CC mode.

Disable Common
Channel Mode.

*)

Enable Common
Channel Mode.

S1.6

DIS-CRC

Determines if 4 bit CRC check is
used on bit 1 of TS0.

Enable CRC4.

*) Disable CRC4.

S1.7

SH-OUT

Determines if outgoing transmission
shield is connected to ground.

Outgoing shield not
connected to GND.

Outgoing shield connected to GND.
*)

S1.8

SH-IN

Determines if incoming transmission
shield is connected to ground.

Incoming shield not
connected to GND.

Incoming shield connected to GND.
*)

*) means 'default setting'.
Table 10.3.3. DIP Switch Settings S1.1 ... S1.8 (DTU-PU version 2).

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-31

MARK
On Off

S 1 Front view

X1.1
108

201

FC 1013

208

101

FC 1012
BA

FBA

FBB

FBC

FBD

FC 101

BB

Fuse (250 mA)
for connector FCD

FCD

Figure 10.3.3. Strap Location DTU-PU.

10-32

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.3.4.

DTU-PH

The Digital Trunk Unit-Protocol Handler (DTU-PH) converts an Integrated Networking
protocol e.g. DPNSS1, DASS2 or 1TR6 into the Internal Message Protocol (IMP) and vice
versa. The type of protocol that is handled is determined by the PROM package.
The DTU-PH carries a DIP switch block (S1.2), a group of eight straps (X4.1) and a group
of five straps (X5.1).
- S1.2 : the functions are given in table 10.3.4.
- X4.1 : used to change the impedance of the transmission interface from 75 Ohm to 120
Ohm and vice versa; see table 10.3.5.
- X5.1 : used to select the EPROM type; see figure 10.3.6.

SWITCH

SIGNAL
NAME

MEANING

OPEN / OFF

S1.2.1

SETLP32

Offers a remote test loop to the other
side (DTU input connected to DTU
output).

Disable remote test
loop.
*)

Enable remote test
loop.

S1.2.2

SETLP31

Offers a local test loop (TS01 ... 31).

Disable local test
loop.

Enable local test
loop.

S1.2.3

CLKREFB

Determines if backpanel clock
reference is to be used (always clock
signal at frontconnector)

No clock reference at
back panel.
*)

Clock also routed to
back panel.

S1.2.4

No function.

S1.2.5

No function.

S1.2.6

Isolation purpose.

-

-

CLOSED / ON

*)

S1.2.7

SH-OUT

Determines if outgoing transmis-sion
shield is connected to ground.

Outgoing shield not
connected to GND.

Outgoing shield connected to GND.
*)

S1.2.8

SH-IN

Determines if incoming transmis-sion
shield is connected to ground.

Incoming shield not
connected to GND.

Incoming shield connected to GND.
*)

*) means 'default setting'.
Table 10.3.4. DIL Switch Settings S1.2.1 ... S1.2.8.
STRAP X4.1

DEFAULT SETTING

CHANGE

101-201 and 102-202

placed

: 120 Ohm Outgoing

not placed

: 75 Ohm Outgoing

103-203 and 104-204

placed

: 120 Ohm Incoming

not placed

: 75 Ohm Incoming

105-205 and 106-206

not placed

: 120 Ohm Outgoing

placed

: 75 Ohm Outgoing

107-207 and 108-208

not placed

: 120 Ohm Incoming

placed

: 75 Ohm Incoming

Table 10.3.5. Strap Settings X4.1.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-33

MARK

Factory test
connector

S 1.2
1
2
3
4
5
6
7
8

X4.1
201

101

208

108






FC 1013
FC 1012






FBB

X5.1
201

101

204

104

‚
‚

‚
‚

BB

FC 1011

Fuse (250 mA)
for connector FCD

FCD

Figure 10.3.4. Strap Location DTU-PH (strapped for 120 Ohm and 1 Mb EPROM).

1

2

3

4

5

6

7

8
Off
On

Figure 10.3.5. Detail of DIP Switch S1.2.
X5.1

X5.1

1 Mb EPROM
(normal setting)

X5.1

2 Mb EPROM

4 Mb EPROM

Figure 10.3.6. EPROM TypeSelection (strap X5.1).

10-34

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

It is possible to change the DIP switch settings while the board is in service. However it is
recommended to put the board in 'not installed' (OM command SETNIN), change the
settings of S1.2 and put the board back in service again (OM command SETINS).
• Interface between DTU-PH and LTU
The interface between the DTU and the LTU comprises the following signals on front
connector FBB:
- TLI
: Trunk Line Incoming
- TLO
: Trunk Line Outgoing
TLI 120 Ohm
TLI 120 Ohm

109

309

SHIELD

TLO 120 Ohm
TLO 120 Ohm
SHIELD

FBB
TLI 75 Ohm

TLO 75 Ohm

TLI 75 Ohm

TLO 75 Ohm

GND

116

316

Figure 10.3.7. Layout Front Connector FBB.

• Interface between DTU-PH and CRU
The interface between the DTU and the CRU comprises the following signal on front
connector FC1011:
- RCS
: Reference Clock Signal (2,048 MHz)
The coaxial front connectors FC1012 and FC1013 are used to connect the 75 Ohm trunk
lines to the LTU. The connector at position FC1012 is the output of the transmission
interface and the connector at position FC1013 is the input. Note that this input and
output are also available at position FBB (TLI & TLO 75 Ohm).
• Interface between DTU-PH and NT1
The interface between the DTU and NT1 multiplexing equipment comprises the -48V
signal for power feeding to NT1 multiplexing equipment (fuse located above FCD, 250
mA.
GND
-48V
GND
-48V

101

301

FCD

GND
-48V
GND
-48V

GND
-48V
GND
-48V

To NT1 multiplexing equipment

GND
-48V
GND
108

308

-48V

Figure 10.3.8. Layout Front Connector FCD.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-35

10.3.5.

DTU-BA

Depending on the network configuration the DTU-BA can operate either as a master or as a
slave configuration in a network. If the DTU-BA is strapped as a Network Terminator (NT), it
will provide the synchronisation clock for the TE. If two DTU-BAs form one transmission
link, one must be strapped as the NT and the other one as the TE. The maximum
transmission distance is 1000 meters. The strap settings used in factory for test purposes
are not illustrated.
MARK

BP

Terminal
Strap Equipment
(slave)
X4.1

FBA

FBB

X4.2

101-102

101-102

Network
Related
Terminator Ports
(master)
102-103

102-103

Applies to
Connector

0
1
2
3
4
5
6

FBA
FBA
FBA
FBA
FBB
FBB
FBB

FBC

Strap settings for NT or TE mode.
FBD

BB
X4.1
103
102
101

X4.2
103
102
101

Figure 10.3.9. Strap Location DTU-BA.

10-36

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.3.6.

DTX-I

The Digital Trunk eXtension-ISDN (DTX-I) provides 15 four-wire 2B+D accesses to the
ISPBX. Each access contains an S0-interface which can be configured as follows:
- as a network interface to connect ISDN terminal equipment;
- as a trunk/tie line interface to make a connection to the ISDN.
The following S0-line interfaces are supported:
-

an extension interface;
a remote extension interface;
an 1TR6 trunk line interface;
an 1TR6 tie line interface;
a DPNSS tie line interface.

The DTX-I can replace a DLC-I or DTU-BA, however the DLC-I or DTU-BA provide 7
circuits only.

Note: There is also a stripped version of the DTX-I which provides 7 four-wire 2B+D S0interfaces.
Each line of the DTX-I has two straps of 3 pins which connect the power supply to the
center taps of the transmission line transformers for phantom power feeding purposes and
for the selection of master or slave, when used as a trunk connection; see figure 10.3.9.

RECEIVE

101
SYSTEM GROUND
MASTER / SLAVE

102
103

Rn

Rn : odd numbered straps
(X5.1 ... X5.29.)

Tn

Tn : even numbered straps

TRANSMIT

DTX-I

-40V
NOT CONNECTED

101
102
103

(X5.2 ... X5.30.)

Figure 10.3.10. Meaning of strap X5.1 ... X5.30.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-37

The strap at the receiver side has the reference Rn and at the transmit side Tn: R stands
for receiver, T for transmit and n is the related line number.
When the DTX-I is used as a DTU-BA, the DTU-BA can operate either as Terminal
Equipment (TE) or as Network Terminator (NT) in a network. When changing over from TE
to NT (or vice versa) also the projecting data has to be changed. Check the projecting data
to see how the DTU-BA is projected.
• Strap Settings
When the DTX-I is used as a:
- DLC-I

: both straps Rn and Tn must be placed on position 101&102 when
terminals, which require line power from the S0-interface, are
connected to the line.
- DTU-BA as TE : both straps Rn and Tn must be placed on position 102&103 when
the line is used for trunk purposes; the trans-formers are
disconnected from the system ground and -40V.
- DTU-BA as NT : both straps Rn and Tn must be removed when the line is used for
trunk purposes; the transformers are disconnected from the system
ground and -40V.

WARNING: Be sure that both the Rn and Tn straps of a line are mounted on equal
positions. It is not allowed to have one strap mounted on position 101&102
and the other strap on position 102&103.
DO NOT mount a strap on X2.1 and X3.1. This will damage the processor and
power supply.
• Terminal Equipment
When the DTX-I is used as interface to the PSTN or another PABX it operates as a TE.
It expects to receive an external clock reference from an NT to synchronise with. This
means that a clock signal is available on frontconnector FC 101; this clock signal can be
used as the input clock for a CRU, when necessary.
• Network Terminator
When the DTX-I is used as an NT, it operates as the master and it provides the synchronisation clock for the TE. This means that no clock signal is available on frontconnector FC 101.
When two DTX-I (used as DTU-BAs) form one transmission link (max. distance 1000
meters) one DTX-I must be strapped as DTU-BA NT and the other as a TE.

10-38

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK
X5.2
X5.1
X5.4
X5.3
X5.6

2

3

7

X5.15
X5.18

8

X5.17
X5.20

9

X5.19
X5.22

10

X5.21
X5.24

11

X5.23
X5.26

12

X5.25
X5.28

13

X5.27
X5.30

FCC

6

X5.13
X5.16

204
104

5

X5.11
X5.14

Lab/Factory
test only.

201
101

4

X5.9
X5.12

FBD

BP

102

X3.1

X5.7
X5.10

FBA

X2.1

1

X5.5
X5.8

FAB

101

LINE 0

14

FC 101

BB

X5.29

Figure 10.3.11. Strap Location on the DTX-I.

103
102
101
103
102
101
103
102
101
103
102
101

X5.2
LINE 0
X5.1
X5.4
LINE 1
X5.3
etc.

Figure 10.3.12. Details of strap X5.1 ... X5.30.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-39

10.4.

LINE TERMINATING UNIT

1
3 LA
0
Connector in :
Upper position=normal operation
Lower position=test loop

UA

LB

LC

Connector in :
Upper position=test loop
Lower position=normal operation

UB

FCB

L
T
U

Means LED

Socket for connector with pre-set links
FCD
Means Connector Position

Figure 10.4.1. Front Layout of the LTU.

10-40

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

BP

COMPONENT SIDE

BA

See
figure 4.4.

LTU

FCB
LTU MOUNTING UNIT

FCD

Figure 10.4.2. LTU Location on LTU Mounting Unit.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-41

C
A
D E
B

SOLDERING SIDE
OF LTU

STRAPS TO BE SOLDERED
TRANSMIT SIDE
STATION CABLING

G

INPUT
UNBALANCED 75 Ω

F
J K

OUTPUT

A - C and D - E

F - H and J - K

A-B

F-G

BALANCED 120 Ω

H

Figure 10.4.3. Straps to be soldered.

U-LINK IN
POSITION

BINARY ERROR RATE ALARM
U1
TRANSFERRED TO DTU

U1

NOT TRANSFERRED TO DTU

-

U2

ALARM COMMAND

URGENT
ALARM

NON-URGENT
ALARM

LOSS OF INPUT OR BINARY ERROR RATE > 10-3

U6

U5

U4

U3

U3
U4

BINARY ERROR RATE

> 10-5

U5
U6
ALARM INDICATION SIGNAL TO BE DELIVERED

U-LINK IN
POSITION

AT > 10-5 ALARM COMMAND

U2

CONSTANTLY, INDEPENDENT OF AN ALARM COMMAND

U7

U7

Figure 10.4.4. Detail and Settings of U- links.

10-42

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.5.

KEY TELEPHONE LINE CIRCUIT

In this chapter two types of Key Telephone Line Circuits (KTLC) are discussed, the 8
circuits per board versions and the 16 circuits per board version. The 8 circuits per board
KTLCs are:
- KTLC01 : according to transmission plan 01 (e.g. The Netherlands);
- KTLC02 : according to transmission plan 02 (e.g. Germany);
- KTLC03 : according to transmission plan 03 (e.g. United Kingdom).
The 16 circuits per board KTLC is:
- KTLC-E : transmission plan set by the signalling block.
The transmission plans supported by the KTLCs can be applied in a wide variety of
countries next to the ones listed above.

10.5.1.

KTLC01/02/03

Which KTLC board has to be used in a certain country depends on the local transmission
plan.
The transmission levels of the various KTLC01/02/03 boards are selected by means of
strap settings. The location of the straps is given in figure 10.5.1. The function of the straps
is as follows:
• Strap X1.1
The straps of X1.1 are used to set the mode of operation of the KTLC; see table 10.5.1.
For normal operation of the key telephones, all straps of X1.1 must be installed.
X1.1
MODE OF OPERATION

101-201

102-202

103-203

104-204

105-205

Normal Operational Mode (strapped in factory)

Inst.

Inst.

Inst.

Inst.

Inst.

Debug Test Mode

Inst.

Inst.

-

Inst.

Inst.

Terminal Communications Test

-

Inst.

Inst.

Inst.

Inst.

Loopback Test: Control - to Terminal Processor

-

Inst.

-

Inst.

Inst.

Loopback Test: Control Processor to PPU

-

-

Inst.

Inst.

Inst.

Table 10.5.1. KTLC Mode of Operation.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-43

• Strap X2.1
This strap is used to connect or disconnect the back-up battery of the memory circuits on
the KTLC board. Within SSW 300 systems the backup voltage is supplied through the
backpanel. Therefore, this strap should always be removed with these systems. User
defined data is not retained when the board is removed from the system.
- Normal operation: strap on position 102-103.
• Strap X3.1
The straps of X3.1 are used to select the correct transmission levels; the setting of X3.1
depends on the type of KTLC and the local transmission plan.
Table 10.5.2. gives the strap settings for the KTLC input levels; table 10.5.3. gives the
settings for the KTLC output levels.
Both tables indicate the strap settings per transmission plan for the most common
countries. Use the default setting in case of other countries.

Note: Make sure that the strap settings of X3.1 correspond to the local transmission
plan before installing the board.
• Strap Settings of the Input and Output Levels
KTLC INPUT LEVEL (dBr)
KTLC01
- 8.4 *)
- 6.9
- 5.4
- 3.9
- 2.4
- 0.9 1)
0.6 2)
2.1 3)
3.6
5.1
6.6
8.1
9.6
11.1
12.6
14.1

KTLC02
- 7.6 *)
- 6.2
- 4.6
- 3.2
- 1.5
0.0 4)
1.5
2.9
4.5
4.5
6.0
7.5
9.0
12.0
13.5
15.0

KTLC03
- 2.8 *)
- 1.3
0.2
1.7
3.2 5)
4.7
6.2
7.7
9.2
10.7
12.2
13.7
15.2
16.7
18.2
19.7

X3.1
101-201

102-202

103-203

104-204

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Table 10.5.2. KTLC input Levels.

10-44

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

KTLC OUTPUT LEVEL (dBr)
KTLC01
7.8 *)
6.3
4.8
3.3
1.8
0.3
- 1.2
- 2.7 2)
- 4.2 3)
- 5.7
- 7.2 1)
- 8.7
- 10.2
- 11.7
- 13.2
- 14.7

KTLC02
2.0 *)
0.5
-1.1
-2.6
-4.1
-5.5
-7.1 4)
-8.5
-10.1
-11.6
-13.1
-14.6
-16.1
-17.6
-19.1
-20.6

KTLC03
2.2 *)
0.7
- 0.8
- 2.3
- 3.8
- 5.3
- 6.8
- 8.3 5)
- 9.8
- 11.3
- 12.8
- 14.3
- 15.8
- 17.3
- 18.8
- 20.3

X3.1
105-205

106-206

107-207

108-208

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.
Inst.

Table 10.5.3. KTLC Output Levels.

Note 1:

*)
1)
2)
3)
4)
5)

Note 2:

Defaults
KTLC01 : The Netherlands.
KTLC02 : Germany.
KTLC03 : United Kingdom.

9710

Factory setting.
Belgium.
Italy.
The Netherlands.
Germany.
United Kingdom.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-45

MARK

BP

F1.1

F1.2

F1.3

FBA

X 3.1
201

101

208

108

F1.4

X 1.1

F1.5
201

205

FBD

101

105

BB

F1.6

F1.7
X2-1
103

101

F1.8

Fuse per line=0.2A Slow blow

Figure 10.5.1. Strap and Fuse Locations of the KTLC 01/02/03 board.

10-46

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.5.2.

KTLC-A/E

The KTLC-A is a 8 circuit board, consisting of one (mother) board. KTLC-A is delivered with
an on-board memory backup battery. Because the system supplies the RAM backup
voltage (EBU) via the back panel, be sure the on-board battery is removed. Leaving the
battery connected will damage the battery (battery disconnected).
The KTLC-E is a 16 circuit board and is a combination of the KTLC-A (mother board) and a
daughter board. KTLC-E does not have an on-board memory backup battery, because the
system supplies the RAM backup voltage (EBU) via the back panel. Be sure the battery
strap settings are in the correct position. The battery cannot be fitted onto the mother-board
if used as a KTLC-E.
When using the KTLC-A/E in SSW 300 systems, the battery should not be connected. See
table 10.5.5. for strap settings.
The KTLC-A and KTLC-E have electronic 'automatic recovery' fuses, so no replaceble
fuses are used.
The location of the strap settings are given in figure 10.5.2. These straps are used for
factory testing and should for normal operation be in the following position:
- Strap X2.1 :
- Strap X2.2 :
- Strap X3.1 :

Not placed (back-up battery disconnected);
Placed (watchdog active);
Configured as KTLC-A : Only strap 101-201 is not placed, other straps
are placed (table 10.5.5.).
Configured as KTLC-E : All placed;

The transmission plan and the transmission levels are set by the software in the signalling
block. Refer to the Signalling Data Manual for further details concerning the meaning and
possible settings of the signalling group bytes. Refer to the PE Commands Manual for
details related to 'variable signalling data'. In that section of the PE Commands Manual the
procedures are given for adapting the signalling group bytes to the local requirements. The
default value for the KTLC-E signalling block is transmission plan 01, since it is used
everywhere except Germany and Austria.
The transmission characteristics are downloaded to the KTLC-A/E when the board is
started up, ie, during a warm start. These characteristics are determined by the signalling
data block which, for a KTLC-A/E, is 2305. Some of these bytes may need to be changed to
adapt to the local transmission plan. This is done by using PE command 4400.
For the sake of completeness the bytes of signalling block 2305 are given here. For the
information related to the signalling blocks is referred to the Signalling Data Manual.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-47

BOARD

PLAN

IMPEDANCE

KTLC-A01

01

UK Line +600 R

KTLC-A02

02

German Complex

KTLC-E01

01

UK Line +600 R

KTLC-E02

02

German Complex

Table 10.5.4. Impedance Types.

• Software Compatibility Bytes
Bytes 1 and 2 are the Software Compatibility bytes. The contents of these bytes are
suitable for all allowed terminals and should not be altered.
• Transmission Characteristics
Bytes 3 and 4 are used for setting the transmit and receive gains for the local
transmission plan.
The KTLC-A/E combination is available in 2 impedance types to suit the different
transmission plans. See table 10.5.4.
As said, the transmit and receive levels are set by bytes 3 and 4. The contents of these
bytes can be changed to suit the local requirements by PE command 4400.
• Hybrid Balance and Side Tone
Bytes 5, 6 and 7 are used for setting the hybrid balance. At present no standards are
defined, refer to the signalling data manual for details of the various possibilities.
• Language Version
Byte 8 sets the default language version. It is not used by the KTLC-A/E. It canNOT be
changed by using PE command 4400.
BOARD

STRAP X2.1

STRAP X2.2

STRAP X3.1

KTLC-A

Not placed,
battery disconnected.

Placed.

Strap 201-101 only not placed, other straps
are placed.

KTLC-E

Not placed,
battery disconnected.

Placed.

All placed.

Table 10.5.5. KTLC-A/E Strap settings.

10-48

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

BP
X2-2
102 101

FBA

X 3.1

FBD

101

206

Strap 201-101 not placed if
configured as KTLC-A,
placed if configured as KTLC-E.

201

106

BB

X2-1
101
102

Figure 10.5.2. Strap Locations on the KTLC-A/E Motherboard.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-49

10.6.

METERING CIRCUIT AND SWITCH OVER UNIT

The Metering Circuit (MC) is used to detect the metering pulses from the public exchange
and to pass the metering information on via the Analogue Trunk Unit (ATU) to the
Peripheral Control.
The metering circuits are also available in combination with the Emergency Switch over
Units, the so called MCE boards.

10.6.1.

MC(E)-D

The MC(E)-D (16 circuit version) is used to detect the 12 kHz metering pulses sent by the
public exchange.
The sensitivity of the MC(E)-D board can be selected (using strap X3.1) to match the
electrical specifications of the metering pulses as defined by the local PTT; see table
10.6.1. and figure 10.6.1.
STRAP X3.1

LEVEL (mV)

101-201

35

102-202

55

103-203

70

104-204

100

Table 10.6.1. Strap Settings MC(E)-D.

10.6.2.

MC(E)-F

The MC(E)-F board contains 16 metering detection circuits to detect the 16 kHz metering
pulses sent by the public exchange.
The sensitivity of the MC(E)-F board can be selected (using strap X3.1) to match the
electrical specifications of the metering pulses as defined by the local PTT; see table
10.6.2. and figure 10.6.1.
STRAP X3.1

LEVEL (mV)

101-201

46

102-202

75

103-203

not used

104-204

not used

Table 10.6.2. Strap Settings MC(E)-F.

10-50

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.6.3.

MC(E)-G

The MC(E)-G (16 circuit version) is used to detect the 12 kHz metering pulses sent by the
public exchange.
The sensitivity of the MC(E)-G board can be selected (using strap X3.1) to match the
electrical specifications of the metering pulses as defined by the local PTT; see table
10.6.3. and figure 10.6.1.
SENSITIVITY (mV)
STRAP X3.1

101-201
102-202
103-203
104-204

Open circuit

Terminated
circuit
(240 Ohms)

50
110
140
200

25
55
70
100

Table 10.6.3. Strap settings MC(E)-G.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-51

MARK

FAA

BP

FAB

FAC

FAD

204

201

104

FBA

101

X 3.1

FBB

FBC

FBD

BB
FCA

FCB

FCC

FCD

Figure 10.6.1. Strap Location on the MC(E)-D, MC(E)-F and MC(E)-G.

10-52

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.7. MODEM LINE UNIT
On an MLU card the following switches and jumper pads are present (see figure 10.7.2.):
- 8 DIL switches (S1.1... S1.8.), each comprising 8 positions;
- 8 jumper pads (X1.1... X1.8.) for 2 or 4 wire selection;
- 4 jumper pads (X2.1... X2.4.) for the selection of the detection level.
MARK

BP

FBA

FBB

FBC

FBD
X2.1

BB

X1.1
FCA

X1.2
X2.2
X1.3

FCB

X1.4
X1.5

FCC

X2.3

S1.5

S1.6

S1.7

S1.8

X2.4

S1.1

S1.2

S1.3

S1.4

X1.6
X1.7

FCD

X1.8

Figure 10.7.2. Location of DIL Switches and Jumper Pads.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-53

For each of the four MLU channels 2 switches and 2 jumper pads are reserved.
Selection of modem and configuration parameters are done via the DIL switches.
Selection of 2 or 4 wire use is done via the jumper pads.

10.7.1.

DIL Switches

Per MLU channel the following DIL switches are reserved:
-

Channel 0
Channel 1
Channel 2
Channel 3

:
:
:
:

S1.3 and S1.4;
S1.1 and S1.2;
S1.7 and S1.8;
S1.5 and S1.6.

The DIL switches for one MLU channel are arranged according figure 10.7.2.
Switches 13...16 are reserved for future extensions.

On

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

Off

Figure 10.7.2. DIL Switches for One MLU Channel.

For setting the specific parameters like transmission speed, synchronous or asynchronous
data transfer etc. for each MLU channel, consult figure 10.7.1. and 10.7.2. and follow the
flow diagram in figure 10.7.3.

Note:

10-54

Some Modem types require a delayed operation of CT108; this can be selected by
setting switch 12 ON.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MLU
DIP-switches

N
Synchronous

Y
S8 =
S5 =
Speed
600
1200
2400
4800
9600
19200
38400
48000
56000
64000

on
on
S1
on
off
on
on
on
on
off
on
off
on

S8 = off
S2
off
on
on
off
on
on
off
off
on
on

Leased
line

S3
off
off
off
on
on
off
on
on
on
on

S4
off
off
off
off
off
on
on
on
on
on

N

S7 = off
Y
MODEM
sends V.25
answer tone

N

Y
S7 = on

S9 = on
S10 = on

S10 = off

MODEM
sends V.25
calling tone

N

Answer
tone = 2100 Hz

Y

N

Y

S9 = off

S9 = on

CT 106 or
CT 109 = V25
answer

2225Hz
S6 = on

N

Y
S11 = on

S6 = off

S11 = off

Legend
CT 106 - V24 signal CTS
CT 109 - V24 signal DCD

END

Figure 10.7.3. Setting the DIL-switches for One MLU Channel.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-55

10.7.2.

2/4 Wire Selection

Per MLU channel the following jumper pads are reserved:
-

Channel 0
Channel 1
Channel 2
Channel 3

:
:
:
:

X1.1 and X1.2;
X1.3 and X1.4;
X1.5 and X1.6;
X1.7 and X1.8.

Both jumpers for one MLU channel should not be set into the same direction.
- 2 wire selection (see also figure 10.7.4a.):
X1.1, X1.3, X1.5 and X1.7 jumper placed on left hand pins.
X1.2, X1.4, X1.6 and X1.8 jumper placed on right hand pins.
- 4 wire selection (see also figure 10.7.4b.):
X1.1, X1.3, X1.5 and X1.7 jumper placed on right hand pins.
X1.2, X1.4, X1.6 and X1.8 jumper placed on left hand pins.
X1.1

X1.1

X1.2

X1.2

X1.3

X1.3

X1.4

X1.4

X1.5

X1.5

X1.6

X1.6

X1.7

X1.7

X1.8

X1.8

Figure 10.7.4a. 2 - Wire Selection.

10-56

Figure 10.7.4b. 4 - Wire Selection.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

10.7.3.

Detection Levels (Answertone)

The detection levels are adjustable per MLU channel.
The following jumper pads are reserved:
-

Channel 0
Channel 1
Channel 2
Channel 3

:
:
:
:

X2.1;
X2.2;
X2.3;
X2.4.

Jumper placed on top pins
Jumper placed on middle pins
Jumper placed on bottom pins

9710

: detection level = -25 dBr;
: detection level = -28 dBr;
: detection level = -31 dBr.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-57

10.8.

DIGITAL LINE CIRCUITS

10.8.1.

DLC-I

The Digital Line Circuit-ISDN (DLC-I) provides seven digital 2B+D lines to the ISPBX.
These lines are four wire basic rate S0-interfaces between the ISPBX and ISDN terminal
equipment according to CCITT Rec. I.430.
The DLC-I is used as Network Terminator (NT): it operates as the master and it provides
the synchronisation clock for the Terminal Equipment (TE). Therefore straps X4.1 and X4.2
must be placed on positions 102-103.
The maximum transmission distance is 1000 meters. The strap settings used in factory for
test purposes are not illustrated.

10-58

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9710

MARK

FBA

FBB

FBC

FBD

X4.2

X4.1

103
102
101

103
102
101

Network
Strap Terminator
(master)

BB

Related
Ports

Related
Circuits

X4.1

102-103

4...6

10...15

X4.2

102-103

0...3

2...9

Strap settings for DLC-I.
factory
test only

Figure 10.8.1. Strap Location DLC-I.

9710

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

10-59

11.

CONNECTION OF AUXILIARY EQUIPMENT

Apart from the commonly used impulse telephone sets or keytone telephone sets it is
possible to connect various other devices to a SOPHO ISPBX like:
-

Digital telephone sets, the SOPHO-SETs;
Line Adapter Modules, the LAMs;
Private Network Termination 1, the PNT1;
A SOPHO SystemManager (SSM);
An Analogue Operator Position, the SOPHO-SUPERVISOR 50;
A Digital Operator Position, the SOPHO-SUPERVISOR 30.

In this chapter the necessary OM and PE procedures are described to connect one of the
above mentioned devices to an ISPBX.

11.1.

PREPARATION OF THE DLC FOR A SOPHO-SET OR LAM

A SOPHO-SET is a digital voice/data terminal that can be directly connected to a Digital
Line Interface Card (DLC) in the Peripheral Module by means of a single twisted wire pair
telephone line.
A Line Adaptor Module (LAM) is a Data Circuit-terminating Equipment (DCE) for interfacing
two sets of Data Termination Equipment (DTE) with the ISPBX. The LAM can be directly
connected to a Digital Line Interface Card (DLC) in the Peripheral Module by means of a
single twisted pair telephone line.
There are three types of DLC boards: DLC-C, DLC-D and DLC-U.
- A DLC-C board contains the control circuitry for one DLC-D.
- At the extension interface side the DLC-U is downwards compatible with DLC-C/D and
LDC combination, at the system side it is not compatible with the mentioned DLCs. DLCU is available in two versions: 15 x (2B+D) channels and 7 x (2B+D) channels.
For the connection of SOPHO-SETs or LAMs to the ISPBX the following general rules
apply:
- Check the Project Engineering (PE) data;
- Check the wiring;
- Select a suitable site to locate the SOPHO-SET or LAM:
. Near to AC power outlet for LAM, also in case of a mains powered SOPHO-SET;
. Near to a telephone line socket;
. Close to the DTE for convenient connection of the interface cable;
. Isolated from sources of electromagnetic interference.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

11-1

Note: Use a power source that is free from noise and excessive voltage fluctuations.
For detailed information concerning the SOPHO-SET and LAM installation, OM commands
and installation of DLCs reference is made to the following documentation:
-

The SOPHO-SET Customer Engineer Manual;
The LAM Customer Engineer Manual;
The OM Commands Manual (MML);
The System Manager's Guide to OM;
The PE Commands Manual.

The following three possibilities exist:
- A DLC board is projected and physically present.
Check if the status is INS (IN Service); if necessary change the status to INS.
In case of a DLC-D board the controlling DLC-C board must also be present and INS.
- A DLC board is projected and not physically present.
Consult the Office Data Manual (ODM) to find the board position where the DLC board is
to be placed. Install the DLC board(s) in the appropriate position(s) and change the
status to INS, by OM command SETINS (7010).
- No DLC board is projected; it has to be assigned manually, see section 11.1.1.

11.1.1.

Manual Assignment of DLC

When the DLC board is not projected the board has to be assigned manually; the following
procedures should be executed.
1.

Add a DLC board to the PE data in a running system, with aid of ”Modifications of
system data in an operational system”,“PROJPA:4000, PCT type 02”.

2.

Perform a warmstart with aid of OM command ”WARMST:” (9100).

3.

Set the DLC board and circuit in service with OM for Circuit Conditions, if not already
set by PE data.
The status of the DLC circuits remains INS when the SET/LAM is properly connected;
the status is ABL when the SET/LAM is absent or not properly connected.

4.

Assign the DNR of the SET/LAM to the EHWA with OM command ”CHDNRC” (3000).

5.

Connect the SET/LAM to the telephone line socket.

11-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

6.

Connect one or two Data Termination Equipment (DTE) to the SET/LAM.

Notes: 1. If modems are required in a connection, the following OM procedures have to
be executed too:
- CHDTED (1210), if a standard set-up for the DTE parameters of the
SETs/LAMs in a usergroup is required, these parameters
are defined here;
- CHMLUR (1230), defines the modem pool number and modem number that
has to be used when a specified (originating) user group
is connected to a specified (terminating) user group;
- CHMLUP (1240), defines the relation between a modem and its EHWA.
2. If a data connection has to be made through a DPNSS link, the following OM
procedure has to be executed too:
- CHSICD (1220), defines the Service Indicator Code for a user group as
used with the DPNSS protocol.

11.1.2.

Malfunctioning of the DLC

It is possible that the status transition from ABL to INS of the DLC circuit does not function.
In that case the following actions has to be taken:
1.

Check if the SOPHO-SET/LAM is properly connected to the power supply.

2.

In case SOPHO-LAM308 or SOPHO-SET308: Check if the a-b wires are crossed.

11.2.

SOPHO SystemManager

A SOPHO SystemManager (SSM) offers facilities for communication management and
information retrieval. It is designed to optimize the use of a telephone exchange for a
business or hotel. Some services can be provided by just dialling codes, others by
requesting them at an SSM workstation.
An SSM workstation will always comprise a monitor and a keyboard. The monitor shows
the services available, indicates where to enter data and displays it on request. The
keyboard enables a user to communicate with the SSM; some keys have a special
meaning.
A printer will usually be shared by a number of workstations. The printer provides a printout
of information such as telephone costs, the details of any particular call made, which rooms
are available etc. Some printouts are automatically generated, e.g. a wake up alarm when a
guest does not respond to a wake up call, a telephone bill when checking out a guest.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

11-3

The SSM is connected to the CPU board of the ISPBX. Before connecting the SSM to the
ISPBX the following general rules apply:
- Check the ISPBX project engineering data;
In section 11.3. the concerning maintenance actions are described.
For detailed information concerning the SSM installation and OM commands reference is
made to the following documentation:
-

The SSM Cusomer Engineer Manual;
The System Manager's Guide;
The PE Commands Manual;
The Facility Implementation Manual (Management Facilities);

11.2.1.

SOPHO SystemManager Configurations

The SSM is a separate computer system connected to the ISPBX via one or more V.24
links. Via these links the computer system can communicate with the CPU of the ISPBX
and a number of management functions can be transferred between the ISPBX and the
SSM.
A number of facilities, available for ISPBX extensions are supported. The SSM can cooperate with one or more SOPHO-SUPERVISOR 50(E)s when using a common name
directory database.
There are two ways of connecting the SSM to the CPU of SSW 300 systems:
- If only the Accounting Manager is used, the connection can be made to the so-called
printer output of the CPU board. This CPU port is then adapted for local toll ticketing
output and switched on by OM command 1050 (serial output). The default baud rate is
2400.
- If other management modules of the SSM are used, as well as the Accounting Manager,
the connection is made to a CPU port which has been assigned to the SSM, either local
or remote. The default baud rate is 9600.
The first type of connection might be used in heavily loaded SSM configurations where it is
necessary to use a dedicated TT line for call accounting. As this is seldom the case with
SSW 300 systems, the first method of connection has no advantages over the second
method, it is recommended that the second method is always used. See figure 11.1.

11-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

HOST
Printer

SOPHO
SystemManager
System Console
CPU

SSM port
See chapter 9.

User

User

SOPHOSUPERVISOR 50(E)

AOC

ALC

ISPBX
(SSW 300)

Figure 11.1. SOPHO SystemManager connected to ISPBX.

The SSM software is divided into modules that can be ordered separately. Each module
has a special function. Some services that are related to the installed modules can be
invoked by dialling the related SSM-prefixes (projectable) from an ISPBX extension. Other
services must be requested from the SSM workstation.
For the basic configuration of the SSM two options are available:
- PC platform
- UNIX platform

9412

: CDOS Operating System;
: UNIX Operating System.

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

11-5

11.2.2.

SOPHO SystemManager Modules

Table 11.1. gives an overview of the various SSM models.
SOPHO SystemManager
PC (SINGLE USER)

SOPHO SystemManager
UNIX (MULTI USER)

MODEL
150
Users
Extensions

600

1000

5000

1

1

max. 12

max. 12

600

1000

20,000 2)

150

1)

Operating
System

CDOS/386

CDOS/386

UNIX

UNIX

Basic
Software

SSM Manager
for CDOS

SSM Manager
for CDOS

SSM Manager
for UNIX

SSM Manager
for UNIX

Fixed modules:

Application
Modules

- SSM Manager,
- Accounting
Manager,
- Call Manager,
- Hotel Manager,
and Facility
Manager.

All, except the
File Manager,
Performance
Manager & Fault
Manager.
Modules not
relevant:

All except the
following which are
not relevant:

All except the
following which are
not relevant:

- File manager;
- Peripheral Facilty
Manager;
- Access Manager.

- File Manager;
- Peripheral Facilty
Manager;
- Access Manager.

- Peripheral Facilty
Manager;
- Access manager.
Q-Manager4)
Call Statistics
3)

Multi-Site
SSM

yes

yes

no

no

no

yes

yes

yes

no

no

no

yes

1) One additional extension licence of 150 is possible.
2) The SSM 5000 system has a theoretical limitation of 20,000 extensions (DNRs), but the practical
limitation is lower due to performance limitations.
3) Option in the Accounting Manager.
4) Q-manager is specially designed for ISPBXs which use SSW 300.20 and upwards.
Table 11.1. SOPHO SystemManager Models.

The basic configurations contain the following functions:
- A database with three directories (internal, external, guest);
- An extension database with the organisational structure;
- The management and access control facilities of the system itself.

11-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

11.2.3.

PE and OM Procedures Related to the Management Functions and SSM

In this section a survey is given of the PE and OM procedures related to the Management
Functions and SSM configuration. For examples refer to the Facility Implementation Manual
(Management Facilities).
• Survey of Project Engineering Procedures
PE 2004 Are metering pulses received during operator call setup for the extension's
account
PE 2005 Define if metering pulses have to be stored in both operator and individual
extension buffer in case of operator metering
PE 2020 Define if Management Functions is used (SSW 300.10 only)
PE 2021 Define if the Q-Manager is used on a stand alone PC or a SOPHOSUPERVISOR 50 E (SSW 300.20 only).
PE 2027 Define if external control of service display is required
PE 2033 Define if Management Functions is used for SSM services
PE 2035 Define the numbering scheme
PE 2036 Define the toll ticketing output
PE 2390 Define the automatic repeat time for SSM services
PE 2394 Define the SSM ringing time A
PE 2395 Define the SSM connecting time A
PE 2396 Define the SSM ringing time B
PE 2397 Define the SSM connecting time B
PE 2437 Define the SSM ring current rhythm A
PE 2438 Define the SSM ring current rhythm B
PE 3500
PE 3510
PE 3520

Define the device allowance level for OM procedures
Define the device allowance level for facility class assignment
Define the device allowance level for traffic class assignment

PE 4020
PE 4130

Define hardware addresses with special signalling group
Define the use of special ALCs

PE 5022
PE 5028
PE 5053
PE 5054

Define if tax metering pulses are available on the route
Define toll ticketing activation point
Define toll ticketing treshold time in seconds
Define toll ticketing metering pulses treshold value

PE 6095
PE 6095
PE 6095
PE 6095
PE 6095
PE 6095

sequence=080:
sequence=081:
sequence=082:
sequence=083:
sequence=084:
sequence=085:

9412

Define the prefix for Room Status dialling
Define the prefix for Night Watchman dialling
Define the prefix for Automatic Message Entry dialling
Define the prefix to upgrade traffic class
Define the prefix to downgrade traffic class
Define the prefix to activate message waiting

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

11-7

PE 6095

sequence=086: Define the prefix to deactivate message waiting

• Survey of OM Procedures
OM ASGNTT (1050) Start/Stop dumping toll ticketing messages
OM ASBAUD (1061) Set baud rate
OM ASPORT (1063) Assign port to application (SSW 300.20)
OM CHTTCR (1080) Define toll ticketing output format options
OM SEDATI (2100) Set Date and Time
OM CHFATI (2110) Change facility timing
OM ASPORE (3400) Assign/Erase relation between Port-id, Port-type and Port type
address
OM ASDARE (3410) Assign data related to a service
OM CHTRFD (3027) Assign traffic classes to DNR
OM ACFACM (3030) Assign facility class marks
OM ASPINP (3430) Set properties of input parameters

11.3.

INSTALLATION OF THE SOPHO-SUPERVISOR 30

11.3.1

Hardware Installation of the SOPHO-SUPERVISOR 30

The SOPHO-SUPERVISOR 30 (SSV30) has a 2-wire interface and it is connected to the
ISPBX by means of a standard 4-wire cable, which provides a full duplex 2B + D interface.
It is on the ISPBX side connected to a standard DLC-U, DLC-C/D and LDC board
combination, or to the Digital Operator Card (DOC) located on the PMC board.
The DOC or the LDC supply the power for the SSV30.
The maximum number of SSV30s is eight. This means that one SSV30 is connected to the
DOC and the rest to a DLC/LDC combination. Max. number of SSV30s on one DLC is 3. In
diagram 420 is shown how the DLC and LDC should be interconnected.
PMC

CPU
PPU

SSV30
DOC

Figure 11.2. SSV30 with a DOC .

11-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

PMC

CPU

or
DLC-U

PPU

*

DLC-C/D

LDC *

SSV30

LDC not required when using a DLC-U.
Figure 11.3. SSV30 with a DLC-U or DLC-C/D - LDC Combination.

11.3.2.

Projecting the SSV30 on a DOC

The SSV30 can be connected to a DOC, a board that is mounted on the PMC.
The Operator Circuit (OCT) has a different signalling group with respect to the other PMC
circuits. This means that the OCT has to be defined with PROJPA 4020 instead of 4000.
• Specify the Operator Circuit
PROJPA:4020,<EHWA>,,01,2807;
EHWA

: External HardWare Address:
10710 or 30710 . . . . . . . . . . . . . . . . . . . . .

SOPHO iS3030

11.3.3. Projecting the SSV30 Connected to a DLC
If the SSV30 is connected to a DLC port, in PROJPA 4020 a signalling group must be
assigned to the EHWA of this DLC port.
• Specify the Operator Circuit
PROJPA:4020,<EHWA>,,01,<SIG-GROUP>;
EHWA
SIG-GROUP

9412

: External HardWare Address of the SSV30 B-channel (the last
two digits of this address must be even!)
: Signalling Group . . . . . . . . . . . . . . . . . . . . 2807 for DLC-C
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2808 for DLC-D
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 090C for DLC-U

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

11-9

11.3.4. The SSV30 Password Mode
With OM command ASPSWD (3139) a password can be (re-)assigned to a USIN or a DNR.
• Assign Password to DNR or USIN
ASPSWD:<DNR or USIN>,<PASSWORD>
DNR or USIN
PASSWORD

11.3.5

: DNR of the SSV30 or the Identity Number of the user
: Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (2...12 digits)

The Projecting of Download Information

The transmission levels are software adjustable. This applies for the transmit, receive and
side tone levels in softspeaking mode of operation and for transmit and receive levels in
handsfree mode of operation. The values are downloaded from the ISPBX.
Also by means of downloading the ISPBX determines if the loudspeaking and/or handsfree
mode of operation is allowed or not.
Next to this, the default language of the SSV30 can be chosen with the help of a projecting
parameter.

11.3.5.1.

Projecting Transmission Characteristics

The transmission levels of the SSV30 can be adjusted with projecting parameters. This is
done with PROJPA 4400 (Define Variable Byte Items).
• Specify the Transmission Characteristics
PROJPA:4400,<SIG-GROUP>,<BYTE-NO>,<BYTE-VAL>;
SIG-GROUP

BYTE-NO
BYTE-VAL

: Signalling Group . . . . . . . . . . . . . . . . . . . . 2807 for DLC-C
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2808 for DLC-D
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 090C for DLC-U
: Byte Number . . . . . . . . . . . . . . . . . . . . . . . . see table 11.2.
: Byte Value . . . . . . . . . . . . . . . . . . . . . . . . . . see table 11.2.

In table 11.2. is shown what the range is of a byte value belonging to a certain byte
number.

11-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

BYTE NUMBER
03
04
05
06

DESCRIPTION

BYTE VALUE RANGE

Transmit level Microphone
Receive Level Telephone
Side Tone Level
Transmit Level Microphone Handsfree

07

Receive Level Loudspeaker Handsfree

000...015
000...015
000...015
000...015
016
000...015
016...031

(=handsfree not allowed)
(=loudspeaking not
allowed)

Table 11.2. Byte Numbers and their Byte Value Range .

Table 11.3. shows the adjustable transmission levels belonging to a certain byte value.

BYTE VALUE

TRANSMIT LEVEL (TL)
(dBr)

RECEIVE LEVEL (RL)
(dBr)

SIDE TONE (ST)
(dB)

00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15

16.5
18
19.5
21
22.5
24
25.5
27
28.5
30
31.5
33
34.5
36
37.5
39

-21
-19.5
-18
-16.5
-15
-13.5
-12
-10.5
-9
-7.5
-6
-4.5
-3
-1.5
0
1.5

-18
-16
-14
-12
-10
-8
-6
-4
-2
0
2
4
6
8
10
12

Table 11.3. Transmission Levels.

With PROJPA 4401 the downloading of transmission characteristics must be enabled.
• Enable downloading of the Transmission Characteristics
PROJPA:4401,<SIG-GROUP>,02,1;
SIG-GROUP

9412

: Signalling Group . . . . . . . . . . . . . . . . . . . .
..................................
..................................

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

2807 for DLC-C
2808 for DLC-D
090C for DLC-U

11-11

11.3.5.2.

Steps for Changing the Default Language

The default language of the SSV30 is English. If necessary an other default language
setting can be downloaded from the ISPBX and should therefore be projected.
• Specify the Default Language
PROJPA:4400,<SIG-GROUP>,08,<BYTE-VAL>;
SIG-GROUP

BYTE-VAL

: Signalling Group . . . . . . . . . . . . . . . . . . . . 2807 for DLC-C
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2808 for DLC-D
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 090C for DLC-U
: Byte Value:
0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . English
1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dutch
2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . French
3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . German

• Effectuate the Default Language
PROJPA:4401,<SIG-GROUP>,02,1;
SIG-GROUP

11-12

: Signalling Group . . . . . . . . . . . . . . . . . . . .
..................................
..................................

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

2807 for DLC-C
2808 for DLC-D
090C for DLC-U

9412

12.

DIAGNOSTIC TEST

The internal part of a SOPHO ISPBX is automatically tested with help of the System
Assurance software.
Apart from these automatic tests one can also manually initiate diagnostic tests. For the test
of external lines a test telephone can be used. A description of the test procedures with a
test telephone is included in this chapter.
To test an analogue operator position a self-test program in this switch board can be
activated, a description of this procedure is included in this chapter. For the test of a digital
operatorposition is referred to the documentation supplied with this type of switch board.

12.1.

CHECKING EXTERNAL LINES WITH TEST TELEPHONE

The test telephone is an ordinary extension with the facility class mark "test call entitled". It
enables the following:
- Checking of the external lines;
- Changing of traffic classes;
- Switching off/on of MFC guarding time.
More than one extension can be assigned as a test telephone.
For convenience a test telephone is normally located in the vicinity of the exchange.
Test telephones can also be used as normal extensions.

12.1.1.

General

The external line check is primarily a check on the correct operation of the interface with the
distant exchange, i.e. the line interface hardware part of the Trunk Unit, the line itself and
line interface equipment at the distant exchange.
The check consists of:
- Dialling the test telephone prefix, which is acknowledged by internal dial tone.
- Dialling the 5 digit hardware address code of the Trunk Unit to specify the required
external line:
S BB PP
Circuit within board
Position of Trunk Unit board in shelf
Shelf number

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

12-1

The Trunk Unit specified must be in one of the following service conditions:
00 - In Service,
01 - In Service,
02 - In Service,

No Owner;
System Assurance2;
Call Processing.

When in 00 (idle), the system will respond with the relevant (Direct Dialling Out) dial tone.
When in 01 or 02 (busy) the call is set in a waiting condition until the Trunk Unit becomes
free (service condition 00). During this period no tone is given. When the Trunk Unit
becomes free, the relevant DDO dial tone is given by the system.
The call is continued as an external call by dialling the digits to be transmitted over the line
(within the limits imposed by the traffic class).
In all cases, the traffic class assigned to the test telephone extension remains valid.
Displaying or changing the traffic class is possible with OM procedures.
The test telephone prefix is fixed in the project data (PE parameter). The test telephone
extension number(s) can be assigned and changed by means of OM procedures.

12-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

12.1.2.

Test Telephone Procedure

ACTION

RESPONSE

Lift handset

Internal dial tone

Dial test telephone prefix

Internal dial tone
- NU tone indicates wrong prefix (or extension
does not have the test telephone facility class
mark).

Dial hardware address code of required external
line circuit:

DDO dial tone

circuit within board
board position within shelf

S

BB

- No tone:
Circuit is busy (INS-CP or INS-SAS2).
Wait for DDO tone.
Hold-on awaiting dial tone.
- Congestion tone:
Replace handset, try again.

PP

shelf number

- Busy tone:
Trunk Unit is in one of the following
conditions:
03
04
1x
2x

-

INS SAS1
INS OM
OUT . . .
ABL
...

In case of OUT, check why.
In case of ABL, set the ATU to INS.
- NU tone:
Non-existing Trunk Unit or address or circuit
condition is NIN.
Check address.
Continue, by dialling required number e.g. for
automatic answering equipment in the PE or own
ISPBX. (In the latter case another incoming trunk
line is checked simultaneously.)

12.2.

CHANGING OF TRAFFIC CLASSES WITH TEST TELEPHONE

The test telephone can be used as a traffic class switch for collectively lowering or raising
the traffic class of extensions, e.g. from day class to night class and vice versa.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

12-3

For this purpose two codes are laid down in the project data:
- One for lowering the traffic class;
- One for raising the traffic class.
By means of the confirmation tone the system acknowledges that the change has taken
place.

12.3.

SWITCHING OFF/ON OF MFC GUARD TIMER

The test telephone can also be used to switch off the Multi-Frequency Code (MFC) guard
timer, enabling the MFC units present in the ISPBX to be tested from the public exchange.
The on/off state of the timer can be defined in the project data.
To this end a specific code is defined in the project data. Using a different code, which is
also laid down in the project data, the timer can be switched on again.

12.4.

ANALOGUE OPERATOR POSITION SELF TEST

The test of the analogue Operator Position is done by means of an internal test program in
the analogue Operator Postition. This test program requires:
- An analogue Operator Postition;
- An analogue Operator Postition test box.
This test program checks the following on the analogue Operator Postition:
-

The keys;
The display;
The lamps;
The handset;
Data transmission path;
Buzzer (6 digit OP);

To test the analogue Operator Position, carry out the following steps.
Step

Description/Action

1

Connect the test box between the analogue Operator Postition and the ISPBX.

2

If buffer sounds, press ZA.
Response : Buzzer stops.

12-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

Step

Description/Action

4

Remove the key, then put it back and turn it.

3

Press # and after that press "1" for a few seconds.
Response : None.
Remarks : Data transmission test. Failure indicated by continuous buzzer.

4

Press 2 for one second.
Response : Buzzer sounds during pressing the button.
Remarks : Buzzer test. If 2 is pressed the buzzer sounds.

5

Successively press keys 3 and 5.
Remarks : Microphone switched on and telephone switched on.

6

Blow into microphone.
Response : Blowing heard in telephone.

7

Successively press keys 4 and 5.
Response : Microphone switched off.

8

Blow into microphone.
Response : No response in telephone.

9

Successively press keys 6 and 3.
Remarks : Microphone switched on. Telephone switched off.

10

Blow into microphone.
Response : No response in telephone.

11

Remove the handset.

12

Press 7 and after that the Z key.
Response : Alarm lamp extinguishes. Lamps and decimal points light in the
sequence given in figure 1.4.
Remarks : If Z key pressed, test is suspended. If pressed again, test is
resumed.

13

Press the keys indicated in figure 1.5.
Display
: The responses should be as indicated.

14

Insert handset and turn key.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

12-5

Step

Description/Action

15

Remove the test box and reconnect the Operator Postition to the system. The Minor
Alarm lamp should extinguish.

16

Turn key.

17

Repeat these procedures for each Operator Postition.
AOC

PLUG

TEST BOX

OPERATOR
POSITION

PLUG

Microphone

MA
MB

103 (111)*
104 (112)*

MA
MB

Microphone

TA
TB

101 (109)*
102 (110)*

TA
TB

OPC

Data

DOA
DOB

305 (313)*
306 (314)*

DOA
DOB

Data from 8048

Data

DIA
DIB

303 (311)*
304 (312)*

DIA
DIB

Data to 8048

-48V OP

105 / 107 / 307
(113 / 115 / 315) *
106 / 108 / 308
(114 / 116 / 316) *

-48V OP

UART

48V DC

GND

48V Supply

GND

48V Supply

* Interfaces for second
operator position

Figure 12.1. Test Box Connections.

1
2
3
4

PA

8
9
10
15

16

PB

17

21

22

27
28
29
30
31

23

34
35
36
37

11
A

C

M

UA

W

AM

A1

A2

A3

PA

PB

5

6

7

12

13

14

18

19

20

24

25

B1
26

B2

B3

32

33

38

Figure 12.2. Lamp Test Sequence.

Notes: If required, the microphone supply can be measured on the operator console
socket (see figure 12.3.):
- ON is 12 V between a and b (a = positive, b = ground).
- OFF is 0 V (plug in the handset into the other socket to discharge the
capacitors).

12-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

a

b

a
b

EB

Microphone line

Telephone line
EB

Figure 12.3. Operator Position Socket.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

12-7

DISPLAY CODES
PA
PB

KEY
A
C
M
UA
W
AM
Z (PRESS AGAIN TO CONTINUE)
S
K
U
WI
ZA
1
2
3
4
5
6
7
8
9
0
*
#
PA
PB
BLANK
B1
B2
B3
V
D
SP (BLANK)
O
L
E
HP CONTACT - LEFT
HP CONTACT - RIGHT

Figure 12.4. Key Test Sequence - 6 Digit Display.

12-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

12.5.

TERMINATING THE OPERATOR POSITION SELF TEST

When the self-test has been completed, restore the console to normal operation as follows:
- Remove test box;
- Re-establish the connection between the console and the system (Major Alarm lamp
should extinguish);
- Plug in the handset. The console will be set to condition “present”. If this is the only
console “present” the system will go to day service.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

12-9

12-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

13.

CLEARANCE OF FAULTS

Faults in the system manifest themselves in one of the following ways:
a.

Total System Failure; Reading out of fault reports no longer possible (from the
Maintenance PC or the Operator Position).

b.

By means of Fault Reports.
b.1. Faults are indicated through the alarm system: Operator Position, or external
alarm unit, or MPC. The fault reports can be read out from the Operator Position,
or from the MPC by reading the Major and Minor alarm buffer.
b.2. Some faults trigger silent alarms; the associated fault reports can be read out
from the Silent alarm buffer.

c.

System Users, including the operator, detect a fault for which there is no automatic
alarm.

Type a, points to a failure in the central part of the system, which consists of a limited
number of units: CPU, associated memory and the PSU.
Type b, comprises the vast majority of possible faults. They are divided in the three
categories: MAJOR ALARM, MINOR ALARM and SILENT ALARM. Which fault leads to
which alarm is determined by PE parameters. The associated fault reports can be displayed
using OM procedures DIMAJA (6020), DIMINA (6021) and DISILA (6022) respectively. In
these reports the system gives detailed information concerning the faults, as follows:
- Hardware
Address

: Shelf number, slot number and circuit on board numbers,
identifying the location of the fault. (00000 means: not attributable to a
particular address).
- Alarm code
: 4 digits, giving the nature of the fault.
- Date and Time : Moment that the alarm became activated or re-activated. (Re-activation
might be with or without buzzer signal.)
- Number of
: Number of times that the problem has been alarmed by System
Occurrence
Asssurance Software.
- Additional
: Additional information (not for all alarm codes): 4 digits, giving extra
information
information about the cause of the alarm. These digits have the
following format:

Note: Some hardware addresses in this chapter contain also references to SOPHO
iS3050 ISPBXs as well as SOPHO-S250/S1000 PABXs; this is done in order to
retain consistency with descriptions of the same parameters that appear in other
books.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-1

XX

or:

XX

X

XXX

“ZZ”: further information.

“ZZZ”: further information.

error type.

error type.

Where there is no additional information, the display is left blank. For detailed information
concerning these digits is referred to the section ”Actions in Case of Alarm”.

Notes: 1. For a number of the PCT-orientated faults the elapsed time between on-set of
the fault and the alarm can be as much as 1.5 hours for every (full) shelf
installed.
2. A large proportion of the alarms are automatically reset as soon as the problem
is no longer detected. In the instructions detailed in "Actions in Case of Alarm",
this situation is indicated by "AR" (Automatic Recovery).
Type c, User Complaints. In the case of simultaneous existence of user complaints and
alarms, the alarms must be dealt with first. In many instances user complaints can be
traced back to parts of the ISPBX which are not automatically tested, viz:
- The individual line-interface hardware in ALCs, MDF connections, lines, extensions.
- The individual line-interface hardware in ATUs, MDF connections, lines to (and
equipment in) the distant exchange.
- The operator's speech circuits (AOC/DOC on a PMC and associated part in operator
console).
- Lamps (LEDs) on keys at an analogue operator console.
Directions for the localization of faults arising from user's complaints are given in the
section ”USER'S COMPLAINTS”.
The maintenance engineer has to take into account another two items which are not
automatically tested:
- The Alarm Unit hardware, and its interface on the CPU board;
- The MPC interface on the CPU board (V.24).
In most cases, the investigation of faults in each of the three categories (a, b and c) will
lead to the replacement of hardware units (printed wiring boards, etc.). Detailed instructions
for replacement and related testing are given in the Chapter ”Replacement Procedures”.

13-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

13.1.

ACTIONS IN CASE OF TOTAL SYSTEM FAILURE

Total system failure is a situation in which the central control part of system is faulty in such
a way that communication with system from the MPC is also not possible.

Note: Possible replacements of printed wiring boards etc., should take place in
accordance with the directions given in Chapter 14 .
Before removing or fitting a PSU always switch off the PSU primary supply! (External 48 V DC box or
Mains). When a PSU is removed or placed with the primary supply switched on the PSU will be damaged.

- Action A: Check and/or repair the power supply system as follows.
1. Check the OK LED on the PSU, this is the lower LED. If this LED is alight
all the internal voltages of the PSU are in order. Proceed with action B.
2. If the OK LED is off, check the mains supply. If there is no mains supply
check and/or repair mains supply. Continue with step 1.
3. If mains supply is in order, check the fuse LEDs.
4. If any fuse LED is alight, replace the associated fuse and continue with
step 1, else continue with step 5.
5. Remove the mains connector, wait for 10 seconds and replace the mains
connector. If the OK LED is alight continue with action B. If not continue
with step 6.
6. Measure the voltage on the F122 connector mounted on the PSU. The
voltage between the left pin-column and the right pin-column should be
between 42 and 60 Volts DC.
If the voltage on the F122 connector is out of specification, check/repair
the mains transformer and rectifier bridge (bridge only on the iS3030).
Maybe the thermo fuse of the mains transformer is blown. Continue with
step 1.
If the voltage on the F122 connector is within specification, the mains
transformer and rectifier bridge are working properly. Continue with step 6.
7. Remove one of the wires of the EBU. If the OK LED is alight now, the EBU
is suspect. If the EBU is empty during initial installation reconnect the EBU
wire. It will take approximately 10 hours to charge the EBU, after that
period the OK LED should lit.
In all other cases replace the EBU.
8. If both the OK LED and the fuse LEDs are off, pull out PCT boards for
approximately three centimetres one by one. DO NOT PULL THE PSU
BOARD!! Leave the PMC and CPU board to the last. If the OK LED lits,
the last pulled board is suspect. Replace and check this board, push back
the other boards and continue with step 1. If the OK LED is still off after
the last board has been pulled out, remove the mains supply, wait at least
5 (!) minutes and replace the PSU.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-3

9. Power up. If the OK LED is alight proceed with action B. If the OK LED is
off replace the exchange, probably a fault in the backplane.
As soon as a possible supply fault has been corrected, the CPU starts up again (LED on). If
it does not, force a WARM START or COLD START by interrupting the primary supply to
the PSU for 10 seconds.
If MPC-CPU communication is again possible, proceed with Action D. Otherwise proceed
with Action B.
- Action B: If it is certain that the power supply system is correct:
1. Replace the CPU.
Communication between MPC and CPU should now be possible again. If
yes, proceed with Action D. If not, see Action C.
- Action C: If the previous actions to check the supply or replace PSU, or replace CPU
have not resulted in the restoration of communication between MPC and
CPU, then repeat these steps in more detail and with greater precision as
follows:
-

-

Pull out from the back panel connectors all printed wiring boards which are
currently not strictly necessary.
Set up a minimum central control configuration comprising: PSU, CPU and
PMC.
Inspect all connectors (including earth contacts).
Clean (dry!) the back panel connectors.
Use another MPC and another MPC-to-system cable or check the MPC
with another exchange.
Use another set of spare units (see the minimum configuration).

If none of this helps, it has to be assumed that the back panel of the CPU shelf is defective.
Change the back panel or exchange.
- Action D: Communication between MPC and CPU is restored. Deal with any remaining
alarms. Reset all alarms using OM CLALRM (6029).
1. If the system is not equipped with a parameter PROM reload the Project
Engineering data, using the MPC.
2. Deal with any occurring alarms. Reset all alarms using OM CLALRM
(6029).
3. Verify that telephony is possible again.

13-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

4. If the CPU has been replaced, test the CPU interface with the Alarm Unit
and the CPU alarm interface with the MPC.
5. In the case of permanent replacements, note the remarks. (Updating
Project Records).

13.2

ACTIONS IN CASE OF ALARM

The alarms MAJOR, MINOR and CIRCUIT BLOCKED are available at the FAA front
connector of the CPU-ME at V.28 level, the function of the connector pins can be changed
using the command ASALRS (OM 6050). DIALRS (OM 6052) displays the current function
of how the connector pins present the alarms. See figure 13.1.
MAJOR
MINOR
CIRCUIT BLOCKED

101

301

GND
GND
GND

FAA

108

308

Figure 13.1. Front Connector Layout of Alarms.

In case of a major alarm, display the fault reports using DIMAJA (OM6020). In case of a
minor alarm, display fault reports using DIMINA (OM6021). These OM procedures display
the fault reports in order of the alarm codes (lowest code first). Deal with the alarms in the
order in which they appear, unless otherwise stated in the alarm instruction.
New alarms will be signalled by the alarm buzzer. There is no buzzer if an alarm reoccurs.
Any printed wiring board replacements should be effected in accordance with the
instructions given in chapters 14 and 15.
Re-insert the original board as soon as it becomes apparent that a board replacement has
not led to any improvement.

Warning: Always switch OFF or disconnect the PSU primary supply (-48V DC or 220 V
AC) of the exchange before removing or fitting a PSU.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-5

In the EHWA a discrimination is made what function is meant, when alarming functions on a
control board (CPU or PMC board). General an External Hardware Address (EHWA)
consists of 5 digits, grouped SBBPP, meaning:
S = Shelf number;
BB = Board position;
PP = Circuit position on board.
With an alarm on a control board the ”PP” in the hardware address points at the possible
cause. The meaning of the PPs is as follows:
In the Central Module (CM), table 13.1:
PP

POINTS AT

99

CPU board (general)
Table 13.1. Central Module.

In the Peripheral Module (PM), table 13.2:
PP

POINTS AT

00...09

Break in Circuit

10
11
12...17
18...21
30...45

Analogue or Digital Operator Circuit
Analogue Operator Circuit
Receiver of keytone
Receiver of Dial tone
Peripheral Circuit Processor

60

Clock Signal Generator

99

PMC board (general)
Table 13.2. Peripheral Module.

13-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1000
--

Major Alarm Overflow
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
No

There are too many major alarm fault reports for the Major Alarm Buffer. A fault report with
the highest alarm code (=lowest priority) has been deleted from the Major Alarm Buffer to
make space for this overflow fault report.
MAINTENANCE ACTIONS:
1. Take prompt action to clear the Major Alarms.
2. Read out and deal with remaining alarms (Minor and Silent).
3. Reset the alarms with OM procedure CLALRM (6029).

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-7

ALARM CODE:
ERROR TYPE:

1002
--

Minor Alarm Overflow
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
No

There are too many Minor Alarm fault reports for the Minor Alarm Buffer. A fault report with
the highest alarm code (= lowest priority) has been deleted from the Minor Alarm Buffer to
make space for this overflow fault report.
MAINTENANCE ACTIONS:
1. Read out and try to resolve all alarms. Reset them with OM CLALRM (6029).

13-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1003
--

Silent Alarm Overflow
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
No

There are too many Silent Alarm fault reports for the Silent Alarm Buffer. A fault report with
the highest alarm code (= lowest priority) has been deleted from the Silent Alarm Buffer to
make space for this overflow fault report.
MAINTENANCE ACTIONS:
1. Take prompt action to clear the Silent Alarms.
2. Read out and deal with remaining alarms (Major and Minor).
3. Reset the alarms with OM procedure CLALRM (6029).

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-9

ALARM CODE:
ERROR TYPE:

1005
--

Major Alarm External
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
Yes

An external condition, detected by the alarmunit, is passed on by the system as a major
alarm.
MAINTENANCE ACTIONS:
1. Reset the external alarm signal (if necessary, by a third party since it is an external
alarm) and investigate the cause of the alarm. (Rectifier alarm?).
If no alarmunit is connected, this alarm will not occur.
2. In the case of a false alarm, the alarm unit should be suspected.

13-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1006
10,20,30,40

POM-Memory Error
Error type

EHWA
ZZ
AR

:

10
20
30
40
: 00000
:
-:
No

=
=
=
=

Program fail
Memory full
Projecting data error
Read fail

MAINTENANCE ACTIONS:
1. In case of error Program fail or Read fail : retrieve project data and replace CPU-board
as required. Re-load project data.
2. In case of error Memory full : shorten project data.
3. In case of error Projecting data error : check project data.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-11

ALARM CODE:
ERROR TYPE:

1008
40

Major Central Equipment Alarm
Error type
EHWA

ZZ
AR

:
40 = PM absent/no acknowledge on the Cold Start command
: 10399
(iS3010)
PMC
10799/30799
(iS3030)
PMC
S0999, S=0...7
(S250/1000)
PMC
S1799, S=0...3
(iS3050)
PMC
01360
(S250)
CSN
11360
(S1000)
CSN
01960
(iS3050)
CSN
:
-:
No

If the CPU does not receive a correct response from the PMC/CSN, an alarm is generated
and a Warm Start is attempted.
If after the warmstart the response is still incorrect, the alarm is repeated.
If after the warmstart the response is correct, the alarm is cancelled and replaced by 1011,
error type 60.
Possible causes of this alarm are amongst other things: faulty PMC (or CSN), faulty
channel between CPU and PMC (or CSN), or faulty PMC/CSN channel part on the CPU.
MAINTENANCE ACTIONS:
1. Ensure that the PMC (or CSN) and the CPU are firmly in position. If this does not solve
the problem, continue with step 2.
2. Replace the PMC (or CSN), and if this does not help, replace the CPU.

13-12

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1008
41,42

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR

41 = No valid Flash EPROM package available in PMC.
42 = Not compatible Flash EPROM package available in PMC.
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
:
-:
Yes
:

This alarm is generated when the PMC does not contain a valid Flash EPROM package,
while an attempt is made to start up this PMC.
Possible reasons

:

Corrupted PMC Flash EPROM package;
or
Deleted PMC Flash EPROM package.

MAINTENANCE ACTIONS:
1. Ensure that the PMC is loaded with a correct (valid) PMC package. Use OM command
DIPACK to retreive the PMC package id.
2. If the PMC package id is not correct, download the correct PMC package.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-13

ALARM CODE:
ERROR TYPE:

1008
50

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR

:

50 = PM cannot become operational/restart command not
acknowledged
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
:
-:
Yes

Communication between the Peripheral Module (PM) and the subunits is not possible. This
is because the Peripheral Processor is not able to build up the required data tables.
MAINTENANCE ACTIONS:
1. Replace the PMC board.

13-14

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1008
51

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ

AR
ZZ = 00
ZZ = 01
ZZ = 02
ZZ = 03
ZZ = 04
ZZ = 10

:
51 = PM PROGRAMMING ERROR
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
:
00 = Flash EPROM cannot be programmed successfully
01 = Package checksum error
02 = Flash EPROM was not cleared
03 = Unexpected end of data
04 = Not supported download data type
10 = No PMC communication or response
:
No
: The PMC failed to perform a successful programming of its Flash EPROM.
: The data transmitted and programmed is detected to be incorrect, e.g.
transmission failures.
: The Flash EPROM is detected not to be clear after a delete package or
before a download package.
: The data received to be prgrammed is detected to be incomplete
: The download source file does contain a data type which are not supported
by the installed BOOT PROM of the PMC.
: A PMC EHWA, cooperating a download or delete session, does not
response or does not confirm the BOOT phase.

MAINTENANCE ACTIONS:
On ZZ=00 or ZZ=02 after a delete package:
1. Unrecoverable error, replace the PMC board.
On ZZ=01:
1. Retry might be successful.
On ZZ=02 before download:
1. Retry by a successive delete package and a secondary download.
2. If step 1 does not solve the problem, then replace the PMC board.
On ZZ=03 or ZZ=04 after a delete package:
1. Check the input file for validity. When other PMCs, downloaded with the same file, did
also signal this error, then the input file is invalid.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-15

2. Retry if the file is valid.
On ZZ=10:
1. Check PMC insertion and status (GREEN LED on at least) and retry.
2. The problem may also rise when an inconsistency exists between PMC and CPU, if this
could be the case perform a warmstart and check the PMC to be global OUT.
3. If a successive download or delete does deliver the same problem, it is most likely that
the PMC does not support the BOOT phase, necessary for download. Replace the PMC
in this case.

13-16

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1008
60

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR

:
60 = PM phase mismatch
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
:
-:
Yes

The CPU and Peripheral Processor are out of phase. The possible phases are:
- Pre-operational phase;
- Re-starting phase;
- Operational phase.
Example: A mismatch occurs if the Peripheral Module (PM) does a cold start.Then it reopens communication in the pre-operational phase, while being registered as
being in the operational phase in the CPU.
The CPU will do a warmstart to re-initialise the PM.
If the warmstart is successfull, the alarm is cancelled, and replaced by alarm 1011,error
type 40.
MAINTENANCE ACTIONS:
1. If the alarm occurs frequently change the PMC.
2. If the alarm still keeps coming back, change the CPU and re-load the project data.
3. If the alarm occurs rarely just record the event.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-17

ALARM CODE:
ERROR TYPE:

1008
70

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR

:
70 = PM buffer overflow
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
:
-:
Yes

Too many call events are offered to the Peripheral Module (PM). This event can indicate
malfunctioning of certain PCTs. It can also indicate an overload condition in the CPU or in
the Peripheral Processor.
The CPU performs a Warm Start to re-initiate the PM.
If the warmstart is successfull, the alarm is cancelled, and replaced by alarm 1011,error
type 50.
MAINTENANCE ACTIONS:
1. In case of an occasional PM Congestion alarm, no specific actions have to be taken.
Record/report the alarm.
2. If the alarm occurs frequently, it is advised to deal with possible other alarms first.
3. Try to establish whether the problem is caused by:
- The loading of the system;
- A PCT;
- The Control Boards (CPU, PMC).
a. Investigate the system's loading with aid of traffic analysis.
b. Set the PCTs in one shelf to OUT. If the problem disappears, set the PCTs one by
one to INS, until you found the faulty PCT.
c. If this does not work, probably the CPU and/or the PMC is faulty.
4. Replace the PMC.
5. If no improvement replace the CPU and re-load the project data.

13-18

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1008
71

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR

:
71 = CPU command buffer overflow
: 10499
(iS3010)
10899/30799
(iS3030)
01199/11199
(S250/1000)
01899
(iS3050)
:
-:
yes

The CPU detected command buffer overflow. This can indicate an overflow condition in the
Peripheral Processor. The CPU performs a Warm Start to re-initiate the Peripheral Module
(PM)
If the warmstart is successfull, the alarm is cancelled, and replaced by alarm 1011, error
type 51.
MAINTENANCE ACTIONS:
1. In case of an occasional CPU command buffer overflow alarm, no specific actions have
to be taken. Record/report the alarm.
2. If the alarm occurs frequently, it is advised to deal with possible other alarms first.
3. Investigate the system's loading with aid of traffic analysis. If this does not give the
cause of the problem go to step 3.
4. Replace the PMC.
5. If no improvement, replace the CPU and re-load the project data.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-19

ALARM CODE:
ERROR TYPE:

1008
80 (1)

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR

:

80 = Operator communication, see also next page for the same
error type
: 10310/10311
(iS3010)
10710/10711/30710/30711 (iS3030)
S0910/S0911, S=0...7
(S250/1000)
S1710/S1711, S=0...3
(iS3050)
:
-:
yes

For the analogue operator position, this alarm is generated by the CPU when no more
correct IN-data is received, which may be caused by the following:
- Defect in the IN-direction;
- Defect in the OUT-direction causes the operator position to stop the data flow in the INdirection.
If the microcomputer in the analogue operator position still works, the Minor Alarm LED and
the buzzer are activated. The buzzer can be silenced using key ZA. If the microcomputer in
the analogue operator position is defective, then there are no alarm indications. If it is the
only operator position present, the system will automatically switch over to night service.
MAINTENANCE ACTIONS:
1. Check the connection of the operator console to the PMC board and the supply voltage
to the operator console. Eliminate a possible extension cable fault by directly connecting
the operator position to the Analogue Operator Circuit (AOC). Use connector FAB/FAC
for XXX10/XXX11 respectively.
2. If there is no improvement, carry out the operator position self test; sub test 1 is directly
relevant.
3. If the operator position is usable, replace the AOC.

Note: To prevent this alarm occurring for those AOC's not connected to operator
positions, set the operator circuit hardware addresses to NIN.

13-20

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1008
80 (2)

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ

:
80 = I/O bus communication failure
: 10399
(iS3010)
PMC
10799/30799
(iS3030)
PMC
S0999, S=0...7 (S250/1000)
PMC
S1799, S=0...3 (iS3050)
PMC
or
10499
(iS3010)
CPU
10899
(iS3030)
CPU
S1199, S=0, 1
(S250/1000)
CPU
01899
(iS3050)
CPU
:
00 = Peripheral Circuit Controller 0
01 = Peripheral Circuit Controller 1
02 = Add-on and Tone Control
03 = Protocol CoProcessor
04 = Digital Signal Processor 0
05 = Digital Signal Processor 1
06 = Digital Operator's Circuit

(PCC0)
(PCC1)
(ATC)
(PCP)
(DSP0)
(DSP1)
(DOC)

The CPU or Peripheral Module (PM) detected a communication failure with the specified
peripheral controller (in case of the CPU the PCP is the only possible component).
The CPU will do a warmstart to re-initialise the PM. If the warmstart is succesfull, the alarm
is cancelled. This alarm then will be replaced by alarm 1011, error type 70.
This alarm 1008, error type 80, will be accompanied by the alarm ”major only by system
start recoverable PM fault” (see alarm 1009, error type 80). The 1008, error type 80 alarm
can then only be found in the history bufer.

Note: The Break In Circuits (BIC) make use of the Add-on and Tone control.
MAINTENANCE ACTIONS:
1. If the error occurs more than once, replace the CPU or PMC (see EHWA).

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-21

ALARM CODE:
ERROR TYPE:

1008
90

Major Central Equipment Alarm (continued)
Error type
EHWA

ZZ
AR
ZZ = 00

:
90 = PSU alarm
: 00599
01199/21199
S2699/S2799, S=0...7
S2099, S=0...3
01360
11360
01960
: 00 - 11
:
Yes

(iS3010)
(iS3030)
(S250/1000)
(iS3050)
(S250)
(S1000)
(iS3050)

PSU
PSU
PSU
PSU
CSN
CSN
CSN

: Low voltage alarm.
iS3010/3030/3050 : +5 V, -5 V, +12 V, -12 V, VCMOS, VBAT.
S250/1000
: VCMOS (for CSN), -5 V, +12 V, -12 V
(< 0.6 V Backpanel pin BB309).
VCMOS
: Normally approx. 0.2 V higher than+5 V.
VBAT
: Voltage of the backup battery pack (EBU) for the
RAMs.
If the alarm is caused by too low VBAT, the alarm should disappear after
the backup battery pack (EBU) is recharged by the internal battery charger
(loading time approx. 6 hours).

ZZ = 01
ZZ = 02

ZZ = 03
ZZ = 04
ZZ = 05
ZZ = 06
ZZ = 07
ZZ = 08
ZZ = 09
ZZ = 10
ZZ = 11

13-22

: 48 V fuse alarm, fuse faulty or removed (iS3010/3030/3050 only). See
corresponding LED.
: Ring voltage (25 Hz, 75 V) too low alarm (< 50 V). This alarm occurs after
the ring voltage has been too low during more than 4 minutes (Backpanel
pin BB109).
: Low AC-Voltage alarm. The mainpower voltage is too low.
: Early powerfail detected, not resulting in power down, might have reset
boards.
: Frame synchronisation slip alarm.
: -48 V group 0 alarm (< -31 V / Backpanel pin BB111).
: -48 V group 1 alarm (< -31 V / Backpanel pin BB311).
: -48 V group 2 alarm (< -31 V / Backpanel pin BB113).
: -48 V group 3 alarm (< -31 V / Backpanel pin BB313).
: -48 V External power supply alarm (< -31 V / Backpanel pin BB115).
: Low voltage VBAT alarm (only from CSN in S250/1000).

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

MAINTENANCE ACTIONS:
1. When ZZ=05:
This indicates a reset of the ATC on the PMC.
If this error occurs only rarely, no further action is required.
If the error occurs frequently or alarm 1080 also occurs, check the external clock
synchronisation.
Otherwise:
2. Check the fuses.
3. When ZZ=00:
To check whether this alarm is caused by too low VBAT only :
Remove the connection to the backup battery pack (EBU). VBAT now will detect normal
voltage and if the alarm was caused by VBAT only, the alarm should disappear.
4. Disconnect or switch off the mains.
If the fuses and the external supply are in good condition , replace the PSU.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-23

ALARM CODE:
ERROR TYPE:

1009
80

Major, only by system restart recoverable PM fault
Error type
EHWA

:
80 = I/O bus communication failure
: 10399
(iS3010)
PMC
10799/30799
(iS3030)
PMC
S0999, S=0...7 (S250/1000)
PMC
S1799, S=0...3 (iS3050)
PMC
or
10499
(iS3010)
CPU
10899
(iS3030)
CPU
S1199, S=0, 1
(S250/1000)
CPU
01899
(iS3050)
CPU

ZZ

:

00
01
02
03
04
05
06

=
=
=
=
=
=
=

Peripheral Circuit Controller 0
Peripheral Circuit Controller 1
Add-on and Tone Control
Protocol CoProcessor
Digital Signal Processor 0
Digital Signal Processor 1
Digital Operator's Circuit

(PCC0)
(PCC1)
(ATC)
(PCP)
(DSP0)
(DSP1)
(DOC)

The CPU or Peripheral Module (PM) detected a communication failure with the specified
peripheral controller (in case of the CPU the PCP is the only possible component). If this
alarm is not only present in the history buffer, but also in the alarmbuffer, the CPU did not
try to recover the failure. This may be caused by an important system function which is not
operational anymore.
The CPU action, when storing the alarm in the history buffer, depends on a previous
occurance and the integration time.
1. There is no previous 1009 alarm present in the historybuffer.
-or2. There is such alarm present, but not satisfying the integration time:
The IO-bus timeout did not occur recently.
The 1009 alarm is stored only in the history buffer.
An 1008-80 alarm is generated and a warmstart is performed.
See also alarm 1008-80 (2)
3. There is a previous 1009 alarm present, satisfying the integration time. Another IO-bus
timeout occurred recently. No 1008-80 alarm (and warmstart!) is generated, but the

13-24

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

number of occurancies is increased in the history buffer, and the 1009-80 alarmreport is
now copied to the alarm buffer.

Notes: 1. The Break In Circuits (BIC) make use of the Add-on and Tone control.
2. In case of a permanently not functioning controller the system does just one
warmstart as a recovery attempt. After that warmstart no action is taken
anymore. This means that the maintenance engineer does not have to read out
the alarms in a continuously warmstarting system.
MAINTENANCE ACTIONS:
1. Try to confirm the malfunctioning of the indicated controller.
2. Replace PMC or CPU (see the EHWA) if required.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-25

ALARM CODE:
ERROR TYPE :

1010
10, 15, 30, 35, 40, 50,
51, 60, 61, 70, 80, 90

Cold Start Done,
Error type

:

10
15
30
35
40
50
51
60
61
70
80
90

EHWA
ZZ
AR

=
=
=
=
=
=
=
=
=
=
=
=

Initial power-up
Watchdog expired
Power-up and CPU data mutilated
CPU I/O congestion and CPU data mutilated
PM phase mismatch and CPU data mutilated
PM congestion and CPU data mutilated
CPU command buffer overflow and CPU data mutilated
PM absent and CPU data mutilated
CSN absent and CPU data mutilated
I/O bus time out and CPU data mutilated
Too many restarts and CPU data mutilated
Warmstart forced by OM procedure 9100 and CPU data
mutilated

: 00000
:
-:
No

A Coldstart has been performed. The error type in the additional information in the fault
report identifies the reason. All previous alarms have been reset.
MAINTENANCE ACTIONS:
1. Make a note of any other alarms (examine later).
2. In case of an occasional Cold Start (e.g. arising from an external supply interruption) the
emergency battery unit (EBU) is suspect. A forced interruption of the external supply
should result in a Warmstart (alarm code 1011). Check the EBU, PSU and CPU.
3. If coldstarts frequently occur without apparent external reasons perform the following
steps:
a. Replace the CPU and reload the system.
b. If the error still occurs, replace the PSU and reload the system.

Note: On the operator position, only the autonomous minor alarm is indicated. The
system will have already stopped data transmission to the Operator Position.

13-26

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
1011
ERROR TYPE: 30, 35, 40, 50, 51, 60,
61,70, 80, 90
Warm Start Done
Error type

EHWA
ZZ
AR

:

30
35
40
50
51
60
61
70
80
90
: 00000
:
-:
No

=
=
=
=
=
=
=
=
=
=

Power-up
CPU I/O congestion
PM phase mismatch
PM event buffer overflow
CPU command buffer overflow
PM absent
CSN absent
I/O bus time out
Too many restarts
Forced by OM procedure WARMST, 9100

A Warmstart has been performed. The project data is still intact. The error type in the
additional information of the fault report identifies the reason for the start.
MAINTENANCE ACTIONS:
1. Make a note of any other alarms (examine later). If a Peripheral Module (PM) is
involved, it can be identified in the 1008 reports.
2. Reset the alarms with OM procedure CLALRM (6029).
3. In case of error type 40, 50, 51, 60 (or 61) or 70, check the PMC (or CSN).
The PM number can be found in the history buffer, check alarm codes 1008 - error types
60/70/71/80 for PMs. When communication loss or fail is detected on a PM, an alarm is
stored for that PM. The CPU performs a warmstart. If the CPU can re-establish
communication with that PM, the specific alarms for that PM (alarm 1008 60/70/80) are
cleared. They still can be found in the history buffer.
4. In case of error type 80, see alarm code 1013.
5. In case of error type 30 or 90, no specific actions have to be taken.

Notes: 1. A Warm Start leads to the breaking of all current telephone connections.
2. Emergency bypass telephones will continue to be directly connected to
exchange lines for 1 minute after the warm start is completed.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-27

ALARM CODE:
ERROR TYPE:

1013
10

Restart Done
Error type
EHWA
ZZ
AR

:
10 = Restart done - Exception occurred
: 00000
:
-:
No

An exception in the software has occurred. The software control is forced back to the
Operating System. The connections remain intact.
MAINTENANCE ACTIONS:
1.

Record/report the alarm. If possible, include the specific conditions under which this
error occurred.
2a. Read out and deal with any other alarms.
2b. Use the command GENADF as follows:
- GENADF: 8999,<FILE NAME>;
- GENADF: 8998,<FILE NAME>;
3.
4.

(read exception buffer)
(read exception buffer and erase it)

If there are no other alarms, a software error must be assumed, which should be
reported to the manufacturer.
Reset the alarms with OM procedure CLALRM (6029).

13-28

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1014
1. . . 5,7

PE Parameter Error
Error type

EHWA

ZZZ
AR

:

1 = Tone error (0ZZ= tone number)
(related to PE24ZZ)
2 = Ring rhythm error (0ZZ= tone number)
(related to PE24(ZZ+32))
3 = Ticker tone error (0ZZ= ticker number)
(related to PE24(ZZ+64))
4 = Signal group byte data error (ZZZ= line number-1)
(related to PE4400) *
5 = Signal group bit data error (ZZZ= line number-1)
(related to PE4401) *
7 = Slave data error (00Z= slave type)
(related to PE4402)
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
: Tone, ticker or signal group number or slave type
:
No

* : With the line number is meant:
The Nth call of the calls to projecting procedure PE4400/4402 in the DLF summarised
with the calls made in the effectuated part of the projectstore. The latter is possible
when additional projecting in a projected system is done.
During sending of Project Engineering (PE) data to a Peripheral Module (PM), the indicated
parameter has been found incorrect.
Line number

= Line number in the projecting data load file (DLF) starting at the first call
to projecting procedure PE4400/4401.

Notes: The CPU does not validate data to be sent to the PM, when executing the POM
data. The PM just validates the data during the startup.
In the tables 13.3 up to 13.6 the tone numbers, the ringing numbers, the slave numbers and
their associate meaning are given.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-29

MAINTENANCE ACTIONS:
1. The PE parameters are not correct. Check the PE file and then reload, using the
existing or a new file as required.

TONE
NUMBER
00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
17
18
19
20
23
24
25
26

DEFAULT
TONE
SOURCE

TONE
Internal Ringing Tone.
External Ringing Tone.
Internal Dial Tone.
First External Dial Tone.
Second and following External Dial Tones.
Delayed Hot Line Dial Tone.
Busy Tone.
Number Unobtainable Tone.
Congestion Tone.
Diversion Active Tone.
Confirmation Tone.
Urging Tone.
Call Waiting Tone Burst.
Paging Absent Tone.
Paging in Progress Tone.
By-Pass Tone.
Camp On Busy Tone.
Park Tone.
Through Connect Ring Tone.
Basic Ticker Tone
Call Waiting Indication Tone.
Alternative Routing Dial Tone.
Alternative Routing Warning Tone.
Enter Password Tone.

DEFAULT
RHYTHM
NUMBER

15
15
15
05
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
0
0
15
0
05

26
26
00
00
00
00
07
09
08
53
00
56
08
09
26
18
25
07
26
0
24
53
0
53

NOTE
1

2
2

2

Table 13.3. System Tones.

Note: 1. The internal and tie line ringing tone.
2. The tone is sent to the destination party only, using a break-in circuit. The BIC
is switched in during approximately one second.

13-30

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

RING
RHYTHM
TONE
NUMBER
00
01
02
03
04
05
06
07

DEFAULT
RHYTHM
NUMBER

RHYTHM

Internal Ring Current Rhythm.
External Ring Current Rhythm.
Auto Ring Back Ring Current Rhythm.
Emergency Ring Current Rhythm.
Through Connect Ring Current Rhythm.
SSM Ring Current Rhythm A.
SSM Ring Current Rhythm B.
Night Service Ring Current Rhythm.

26
27
26
00
27
07
58
59

Table 13.4. Ringing Rhythms.

TICKER
NUMBER
00
01

DEFAULT
TONE
SOURCE

Break in Ticker Rhythm.
Add-On Ticker Rhythm.

DEFAULT
RHYTHM
NUMBER

01
01

RHYTHM

00
57

Table 13.5. Ringing Rhythms.

SLAVE
NUMBER
8
9

SLAVE TYPE
Tone Frequency
Tone Level
Table 13.6. Slave Numbers.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-31

ALARM CODE:
ERROR TYPE:

1014
6,8

PE Parameter Error (continued)
Error type
EHWA
ZZZ
AR

:
6 = Board installation error
: XXX99 = Board address
:
--:
No

Error type
EHWA
ZZZ
AR

:
8 = PCT installation error
: XXXXX = PCT address
:
--:
No

During the sending of project data (PE data) to the PM, an invalid signalling group number
was detected.
MAINTENANCE ACTIONS:
1. Check the PE file for correct version and exchange numbers.
2. Check all Variable Signalling Data Block numbers and PCT types in the PE data printout, and correct if necessary.
IMPORTANT
If the CPU has done a COLDSTART, and the CPU has taken the default projecting data
(present in ROM), the PMC assumes an analogue operator (AOC board mounted on PMC).
When hardware is installed for the digital operator (DOC board mounted on PMC), the
PMC will detect an error during initialisation of the hardware. This will result in the projecting
error mentioned here:
EHWA

Alarmcode
Error type :

: 10310
10710
00910
10910
01710
: 1014
8

(iS3010)
(iS3030)
(S250)
(S1000)
(iS3050)

This alarm is normal during the coldstart, so the DOC-hardware should not be suspected of
errors at this moment.

13-32

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1014
9

PE Parameter Error (continued)
Error type
EHWA

ZZZ
AR

:
9 = Time-out error
: 10399
(iS3010)
10799/30799
(iS3030)
S0999, S=0...7 (S250/1000)
S1799, S=0...3 (iS3050)
:
--:
No

During the projecting/initialization phase a projecting/initialization command was not
acknowledged by the PM.
MAINTENANCE ACTIONS:
1. If other errors are reported, check those errors first. Alarm 1014, error type 9 is usually
accompanied and caused by other errors.
2. If no other errors are reported, check the PE file.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-33

ALARM CODE:
ERROR TYPE:

1015
--

Emergency bypass function is activated
EHWA
AR

: 00000
:
Yes

MAINTENANCE ACTIONS:
Verify the reason why the emergency bypass is activated.

13-34

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1023
--

Garbage Buffer Overflow
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
No

More irregularities are detected in the processing of telephony functions than statistically
may be expected (unexpected call events).
MAINTENANCE ACTIONS:
1. Read out the Garbage Buffer with OM procedure DIGABU (6024).
2. Determine the common factor in the reports.
Overflow of the garbagebuffer can be caused by abnormal usage of a signalgroup for a
PCT. It can also be caused by a CPU or PPU software error.
To interpret the events in the garbage buffer specific knowlegde is required about the
system's software architecture.

Notes: 1. If the Garbage Buffer becomes full, an alarm is given and the contents are
frozen.
2. The buffer can be cleared by means of an OM procedure, which also resets the
alarm.
3. A coldstart will also clear the buffer and reset the alarm.
4. The garbage event buffer leaks with one event per day.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-35

ALARM CODE:
ERROR TYPE:

1030
--

Minor Alarm External
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
Yes

An external condition is passed on by the system as a Minor Alarm.
MAINTENANCE ACTIONS:
1. Reset the external alarm signal and investigate its cause, e.g. rectifier.
2. In the case of a false alarm, check the alarm unit.

13-36

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1040
10

Board Fault
Error type
EHWA
ZZ
AR

:
10 = ESU/MCE board removed
: XXX99 = ESU/MCE board address
:
-:
Yes

The indicated emergency bypass board ('MCE-') has been removed from the system. The
emergency switch over function for the extensions connected via this board is no longer
operational.
ESU = Emergency Switch over Unit
MCE = Metering Circuit & Emergency Switch over Unit
MAINTENANCE ACTIONS:
1. In case the MCE is installed, and this alarm is active, replace the board.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-37

ALARM CODE:
ERROR TYPE:

1040
20

Board Fault (continued)
Error type
EHWA
ZZ

AR

:
20 =
: XXX99 =
:
00 =
01 =
02 =
03 =
04 =
06 =
:
No

PMC board failure
Board address
Board not operational
Board communication failed
Board queue congestion
Out of synchronisation
Flow request failed
DOC communication fail

A fault is discovered for a second time within 12 minutes during the operational phase of
specific control hardware on the board. This error will only be reported for those boards
containing a microprocessor, or for boards controlled by another board with a
microprocessor.
When the fault occurs only once within 12 minutes alarm 1040 error type 50 is generated
instead.
SAS will subsequently disable call processing for the PCTs controlled by the board, and
possibly generate a PCT removed alarm. The latter alarm is possible when the SAS takes a
PCT out of operation.
MAINTENANCE ACTIONS:
1. Retry to activate the board by removing and re-installing it.
2. If no improvement, or if the alarm reoccurs later on, replace the board.

13-38

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1040
30

Board Fault (continued)
Error type
EHWA
ZZ

AR

:
30 =
: XXX99 =
:
00 =
01 =
02 =
04 =
07 =
08 =
09 =
10 =
11 =
:
No

Board activation error
Board address
Board not operational
Board communication failed
Board queue congestion
Flow request failed
Board in boot mode, package present
Board in boot mode, no package present
Board in boot mode, package corrupted
Board package deletion failed
Board package downloading not supported

A fault is discovered during the activation of specific control hardware on the board. This
error will only be reported for those PCT boards containing a microprocessor, like DTUs
and DLCs, and in particular after a system start. The System Assurance Software (SAS)
will subsequently disable call processing for the PCTs on the board.
MAINTENANCE ACTIONS:
1. Replace the PCT board.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-39

ALARM CODE:
ERROR TYPE:

1040
31

Board Fault (continued)
Error type
EHWA
ZZ

AR

:
31 = Board programming error
: XXX99 = Board address
:
80 = FEPROM cannot be programmed successfully
:
81 = Package checksum error
:
82 = FEPROM was not cleared
:
83 = Unexpected end of data
:
84 = The download source file contains a data type that is not
supported by the boot PROM installed on the board
:
85 = Board was not in boot mode
:
86 = Board communication failure
:
No

MAINTENANCE ACTIONS:
80 or 82

(after a delete package command)
Unrecoverable error, replace the PCT board.

81

A retry might be successful.

82

(before a download)
Retry by first deleting the package and then performing a second download. If
the problem is not solved replace the PCT board.
Check that the input file is valid; if downloads to other boards report the same
error using the same file, then the file is invalid.
Put PCT in boot mode.
Replace the PCT board.

83, 84
85
86

13-40

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1040
40

Board Fault (continued)
Error type
EHWA
ZZ
AR

:
40 = Board hard timer error
: XXX99 = Board address
:
-:
No

During progress of a process, congestion was met when retrieving a timer from a pool of
free timers. The timer was required for an important function, and continuing the process
without the timer would risk the progress of the communication protocol.
If the error occurs the first time, the CPU tries to re-activate the board. The board is kept
under special attention during 12 minutes.
If the error does not re-occur within 12 minutes alarm 1040 error type 50 is generated.
If the error reoccurs the System Assurance Software (SAS) will disable callprocessing for
the PCTs on the board, and generate this alarm (1040 error type 40) .
MAINTENANCE ACTIONS:
1. Try re-activation by removing and inserting the board.
2. If this does not help replace the board.
3. Frequent occurence of this alarm can indicate overload of the PMC.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-41

ALARM CODE:
ERROR TYPE:

1040
50

Board Fault (continued)
Error type
EHWA
ZZ
AR

:
50 = Intermittent board fault
: XXX99 = Board address
:
-:
No

The PM detected a communication failure between the PMC and the board controller on the
specified board.
The CPU deactivated the board and reactivated it. The board was monitored for 12
minutes, and no further failure event of the board was received.
If, within the 12 minutes, a board controller communication failure is detected for a second
time, alarm code 1040 error type 20 is generated instead. In this case the board will be
booked absent, and can only be recovered by re-installing it.
SAS will subsequently disable call processing for the PCTs controlled by the board, and
possibly generate a PCT removed alarm. The latter alarm is possible when the SAS takes a
PCT out of operation.
MAINTENANCE ACTIONS:
If this error occurs rarely, no further action is required.
If this error occurs frequently or alarm code 1040 error type 20 occurs, the board should be
replaced.

13-42

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1040
51

Board Fault (continued)
Error type
EHWA
ZZ
AR

:
51 = Intermittent board fault
: XXX99 = Board address
:
06 = Digital Operator Circuit (DOC)
:
No

The PM detected a communication failure between the PMC and the board controller on the
specified board. The PM itself did a successfull attempt to recover the board.
The PCT(s) on the board have been unoperational for a while, generating possibly an 1042
alarm, error type 50, ZZ=02 (link error). This alarm will be cancelled once the board is
recovered.
If the PM is unable to recover the board, alarm 1008, error type 80xx is generated instead
(I/O-bus timeout). In that case the system will perform a warmstart to re-initialise the
function on that board.
MAINTENANCE ACTIONS:
If this error occurs rarely, no further action is required.
If this error occurs frequently, the board should be replaced.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-43

ALARM CODE:
ERROR TYPE:

1041
20,21,30

Intermittent PCT Fault
Error type

EHWA
ZZ

AR

:

20
21

= An important unexpected event for a PCT has been received
= The CPU and the Peripheral Processor are not synchronized (call
failure event)
30 = The automatic “In Service” PCT testloop found a faulty PCT. It
was put in ABL condition. The ABL test loop tested the PCT
again, found that it was correct, and put it back to service again.
The transition INS-ABL caused alarm 1042 error type 20. The
transition ABL-INS cleared the 1042 alarm error type 20, and
generated the alarm 1041 error type 30 instead.
: XXXXX= PCT
: ONLY for error type 20:
01
= CALL-REQUEST
08
= CALL-REQUEST-FOR-INTERCOM
16
= TRUNK-IDLE
17
= INCOMING-SEIZURE
19
= FORWARD-RELEASE-RECEIVED
20
= BACKWARD-RELEASE-RECEIVED
22
= CALLED-PARTY-ONHOOK-RECEIVED
48
= READY-FOR-SEIZURE-RKT-RDT
51
= NO-FORWARD-MFC-SIGNAL
52
= MFC-READY-FOR-RELEASE
70
= PAGING-CHANNEL-IDLE
136
= PCT-ORDER-FAILED
137
= PCT-TIME-TABLE-FULL
139
= SERVICE-ORDER-REJECTED
144
= MFC-PROCEDURE-FAILED
145
= PCT-HARD-TIMER-ERROR
:
No

The call processing program has detected a fault, which cannot be confirmed by the
System Assurance Software (SAS). The PCT concerned is set to IDLE, and made available
again for call processing. To interpret the event belonging to error type 20 specific
knowledge is required about the system's software architecture. An explanation about the
meaning of events is outside the scope of this manual.
MAINTENANCE ACTIONS:
1. If a particular PCT is repeatedly alarmed, replace the PCT board concerned.
2. Read out and deal with any other alarms.

13-44

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1041
40

Intermittent PCT Fault (continued)
Error type
EHWA
ZZ
AR

:
40 = Successful retry to get the PCT operational
: XXXXX = any PCT position
:
-For explanation of ZZ see alarm code 1042 error type 50.
:
No

The PPU detected a communication failure between the PCT and the outside world.
(except for: no terminal being connected to the PCT).
The CPU did a rollback on that PCT. The PCT was monitored for 12 minutes, and no
further failure event of that PCT was received.
If, within 12 minutes, a communication failure is detected for a second time, alarm code
1042 error type 50 and up is generated instead. In this case the PCT will be booked
unoperational and can only be recovered by taking it out of service, followed by putting it
into service again.
MAINTENANCE ACTIONS:
1. If this error occurs rarely, no further action is required.
2. If this error occurs frequently, or alarm code 1042 error type 50 and up occurs, check
the connection with the outside world.
3. If this does not help, replace the board.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-45

ALARM CODE:
ERROR TYPE:

1042
10

PCT Fault
Error type
EHWA
ZZ
AR

:

10 = PCT put in unobtainable condition due to unoperational
condition of the board.
: XXXXX = Board address
:
-:
Yes

The indicated board has been removed (or taken out operation by SAS) from the system or
became deactivated while one or more PCTs on the board were in the circuit condition INS.
Or:
A PCT on specified board was put into service while the board was removed, or could not
be activated. (check possible 1040-30 alarm)

Note: After system start PCT's on absent or not activated boards are not put into service,
so no alarm reports will be generated.
The PCTs may be put into service by OM 7040.
Or:
A PCT on specified board was in service while the board was booked unoperational by the
CPU due to some reason (check possibly also present 1040 alarms).
This alarm disappears as soon as the board is re-installed or the last in-service-PCT is put
in the OUT or NIN condition.
If a board cannot be activated after the board is installed (check with OM 7032), the board
should be replaced.
MAINTENANCE ACTIONS:
1. Check possible relation with alarm 1040, error type 20 or with alarm 1048.
2. If the removal is permanent, set the circuit condition of the PCTs to NIN.

Note: If a relationship between boards has been specified, removal of the master board
will also cause the PCTs on the associated boards to be "removed".

13-46

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1042
20

PCT Fault (continued)
Error type
EHWA
ZZ
AR

:
20 = PCT test fault
: XXXXX = PCT address
:
-:
Yes

The indicated PCT is found faulty by the automatic INS test. The PCT is automatically set to
the circuit condition ABL.
MAINTENANCE ACTIONS:
1. Replace the PCT board concerned.
See also explanation with alarm 1041 error type 30.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-47

ALARM CODE:
ERROR TYPE:

1042
30

PCT Fault (continued)
Error type
EHWA
ZZ
AR

:
30 = PCT permanently busy
: XXXXX = PCT address
:
-:
Yes

The indicated PCT is recorded as "busy" by the software for longer than a specified time.
MAINTENANCE ACTIONS:
1. If necessary listen-in on a LCT or trunk line to verify that the connection is still valid.
Maybe terminate the call to free the line.
2. If freeing the line is unsuccessful (OM SERBRQ, 1028) read out it's current state (OM
DIPCTS 1026), and report the result to the service organisation. Force a Warm Start by
means of OM WARMST (9100) at a suitable time.
3. If the busy condition has to be considered as normal the alarm can be reset by means of
OM CLALRM (6029). Free the line by OM SERBRQ (1028).

Note: PCTs involved in connections with dataprotection are not reported “permanently”
busy.

13-48

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1042
40

PCT Fault (continued)
Error type
EHWA
ZZ
AR

:
40 = PCT permanently idle
: XXXXX = PCT address
:
-:
Yes

The indicated PCT is recorded as "Idle" by the software. This means that this PCT is not
seized for longer than a specified time. The period of time is specified by means of a
Project Engineering (PE) procedure.
MAINTENANCE ACTIONS:
1. Determine the functional group to which the indicated PCTs belong.
2. If they are ATUs, also determine the trunk group number to which they belong and
whether this trunk group is used for incoming and outgoing calls.
3. Check the PE data for this functional/trunk group.
4. Verify the operation of the PCT(s) involved.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-49

ALARM CODE:
ERROR TYPE:

1042
50

PCT Fault (continued)
Error type
EHWA
ZZ

AR

:
50 =
: XXXXX =
:
00 =
01 =
02 =
03 =
06 =

:

07
08
09
13
10
12
No

=
=
=
=
=
=

Line circuit (LCT)/Operator circuit (OCT)failure
LCT/OCT/Digital Trunk address
Service button pushed too long (ALC)
Disable received
(ALC)
Link error
(DLC, KTLC)
Hard link error
(DLC, KTLC)
Order failed
(DLC, KTLC, DTU-BA,
DTU-PH, DTX-I)
Service order failed
(DLC, KTLC)
Terminal no response
(DLC, KTLC)
Buffer congestion
(DLC)
Controller no response
(DLC, KTLC)
Wrong voice/data indication
(DLC, KTLC)
Crossed lines
(DLC)

00:

In ”closed loop” condition the a-wire was too long connected to
earth. This error can indicate a cabling failure. When a lot of
ALC's generate this alarm (“drowned cable?”), the system may
become overheated.

01:

The (ALC) board is erroneous.

02, 03, 06, 07, 08, 09, 13:

A fatal PMC-DLC, PMC-KTLC, PMC-DTU-BA, PMC-DTU-PH
or PMC-DTX communication failure occurred. The CPU has
already done an attempt to recover the circuit from a recent
simular error and put it under special attention. This recovery
attempt failed: the error re-occurred within 12 minutes. Now the
circuit is put out of operation (blocked by SAS).
Exception: When a LAM 308 or SOPHO-SET 308 is connected
to the DOC board, and the A-B wires are reversed, the alarm
1042 with additional info 5002 will occur for the ports on the
DOC.

10:
12:

13-50

The port is incorrectly assigned: e.g. as a data port, while being
a voice port.
A-B-wire are reversed.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

MAINTENANCE ACTIONS:
1. Check if error can be explained by wrong or bad connections between PCT and the
terminal, for example. When required, put the PCT back into service by taking it
temporary out of service.
2. If the connections are correct, the board should be replaced.
The concerned PCT will be set unavailable for call processing. It can be recovered by
taking it out of service, followed by putting it into service again. If no action is taken within
24 hours this alarm is possibly followed by a 1050 alarm.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-51

ALARM CODE:
ERROR TYPE:

1042
60,61

PCT Fault (continued)
Error type
EHWA
ZZ
AR

: 60,61 = Peripheral Circuit (PCT) / Virtual Circuit (VCT) activation error
: XXXXX = PCT/VCT address on DTU-board
:
14 = Logical link disconnected
:
No

(This alarm is related to alarm code 1041 error type 40)
For a second time within 12 minutes a PCT/VCT could not be put in operation, the
communication link could not be set up.
MAINTENANCE ACTIONS:
1. Check the connections and cables from and to the IPH boards.
2. If the connections and cables are correct replace the IPH boards.

13-52

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1042
70

PCT Fault (continued)
Error type
EHWA
ZZ

AR

:
70 =
: XXXXX =
:
06 =
10 =
13 =
:
No

Communication failure
Address of port on IPH-board
D-channel wrong reply
PE parameter failure
D-channel no reply

(This alarm is related to alarm code 1041 error type 40)
An alarm is reported for the second time by the corresponding circuit, within 12 minutes.
MAINTENANCE ACTIONS:
If ZZ = 06 or 13

: check the connections and the cables from and to the IPH boards.
If the connections and the cables are correct, replace the IPH boards.

If ZZ = 10

: Check the Project Engineering (PE) data from the DTU-IPH
combination.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-53

ALARM CODE:
ERROR TYPE:

1042
80

PCT Fault (continued)
Error type
EHWA
ZZ
AR

:
80 = Protocol mismatch
: XXXXX = PCT address
:
-:
No

The communication protocol between the system, and the device connected to the system
does not match.
MAINTENANCE ACTIONS:
Check compatibility between equipment defined in the system and equipment connected to
the system. For example a LAM is connected, but the circuit is defined in system as
Supervisor-set.

13-54

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1042
90

PCT Fault (continued)
Error type
EHWA
ZZ
AR

:
90 = Execute CPM failure
: XXXXX = PCT
:
-:
No

An internal software inconsistency has been detected.
MAINTENANCE ACTIONS:
Read ou the garbage buffer (MML command DIGABU) and send information to PQS
helpdesk.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-55

ALARM CODE:
ERROR TYPE:

1043
10

DCC Board Alarm
Error type
EHWA
ZZ
AR

:
10 = RFP error
: XXX99 = DCC board address
:
-:
No

MAINTENANCE ACTIONS:
1. Check RFP connections.
2. Check RFP or replace RFP.

13-56

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1043
20

DCC Board Alarm(continued)
Error type
EHWA
ZZ
AR

:
20 = Burst mode controller error
: XXX99 = DCC board address
:
-:
No

MAINTENANCE ACTIONS:
1. Replace the DCC board.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-57

ALARM CODE:
ERROR TYPE:

1043
30

DCC Board Alarm(continued)
Error type
EHWA
ZZ
AR

:
30 = Backbone communication is lost
: XXX99 = DCC board address
:
-:
No

MAINTENANCE ACTIONS:
1. Check strap settings on DCC board.
2. Try to reboot the DCC board.
3. If all fails, replace the DCC board.

13-58

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1043
40

DCC Board Alarm(continued)
Error type
EHWA
ZZ
AR

9707

:
40 = General hardware error
: XXX99 = DCC board address
:
-:
No

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-59

ALARM CODE:
ERROR TYPE:

1043
50

DCC Board Alarm(continued)
Error type
EHWA
ZZ

AR

:
50 =
: XXX99 =
:
01 =
02 =
03 =
:
No

General software error
DCC board address
Subscription database corrupt
DCC-address incorrect
Duplicate DNR in the system

MAINTENANCE ACTIONS:
If ZZ = 01

If ZZ = 02

If ZZ = 03

13-60

: Perform backup of the board. Look in the generated .LST file which
entries are corrupt. Perform cleanup command on the board, the DCC
will then remove automatically the corrupted records.
: The RFPs on this board will not become in service. The green led
keeps flashing. The DCC is placed in the wrong position (or still
contains subscription from a previous life). Perform backup command
of the board to look which DNRs are on the board. Place the board on
the right position or remove all subscriptions.
: A DNR has been moved in the ehwadnr.pdt file to another EHWA (on
another board), but the previous subscription is still present on the
DCC. This alarm should always be present on 2 boards. Perform a
backup of both boards and check which board contains the right one. If
the ehwadnr.pdt file must be repaired, again perform a backup of both
boards. Perform a cleanup of both boards, first the faulty board and
then the right board.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1043
60

DCC Board Alarm(continued)
Error type
EHWA
ZZ
AR

:
60 = The RFP-ID is missing or incorrect
: XXX99 = DCC board address
:
-:
No

MAINTENANCE ACTIONS:
1. The RFP-ID downloaded from the PM to the DCC is missing or incorrect. Project correct
RFP-ID parameters in the PM data.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-61

ALARM CODE:
ERROR TYPE:

1044
10

DCC Board Configuration Alarm
Error type
EHWA
ZZ
AR

:
10 = The RFP configuration does not match with the actual situation
: XXX99 = DCC board address
:
-:
No

MAINTENANCE ACTIONS:
1. In the DECT manager, adapt the RFP configuration to the actual situation.
Clear the alarms.

13-62

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1045
01...13

Manually Controlled Test - Error Report
Error type

EHWA
ZZ
AR

:

00
01
02
03
04
05
06
07
08
09
10
11
12
13
: XXXXX
:
-:
No

=
=
=
=
=
=
=
=
=
=
=
=
=
=
=

Wrong or no response after putting the circuit in the testmode
CODEC test
Signalling test
Transmission test
Transmission test from port 0 to port 1
Transmission test from port 1 to port 0
Transmission test from port 0 to port 2
Transmission test from port 2 to port 0
Transmission test from port 1 to port 2
Transmission test from port 2 to port 1
Taxmetering test
Receiver test
Sender test (only on RST-KD)
Polarity test
PCT

The indicated Peripheral Circuit (PCT) is found faulty during a manually controlled test.
MAINTENANCE ACTIONS:
1. Replace the PCT board concerned.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-63

ALARM CODE:
ERROR TYPE:

1046
01...13

Manually Controlled Test - Information
Error type

EHWA
ZZ

AR

:

00 = Test Set Up
01 = CODEC test
02 = Signalling test *
03 = Transmission test *
04 = Transmission test from port 0 to port 1
05 = Transmission test from port 1 to port 0
06 = Transmission test from port 0 to port 2
07 = Transmission test from port 2 to port 0
08 = Transmission test from port 1 to port 2
09 = Transmission test from port 2 to port 1
10 = Taxmetering test *
11 = Receiver test
12 = Sender test (only on RST-KD)
13 = Polarity test *
:XXXXX = PCT address
:
01 = PCT not installed
02 = Circuit Condition ABL
03 = Waiting time exceeded
04 = No test program available
05 = No auxiliary PCT available, for example:
- No INS RKT for Test Phase 1;
- No INS RDT for Test Phase 3;
- No INS RDT or RKT for Test Phase 12;
- One or more ALCs or ATUs on same board are not NIN.
:
No

* Only when test cards/connectors are used.
The indicated Peripheral Circuit (PCT) could not be (completely) tested. The reason is
indicated by ZZ.
MAINTENANCE ACTIONS:
1. Check for possible incompatibilities between:
- PCT type under test;
- Circuit condition of the PCT under test;
- Test type as specified in the Target list;
- Type of Test Card / Connector fitted (if applicable);
- Non-resident test program(s) where applicable.
2. If necessary, repeat the test with another Test Card/ Connector.
3. If necessary, replace the indicated PCT.

13-64

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
1048
ERROR TYPE: 00,01,02,03,05,06,07,08,09
DTU Alarm
Error type

EHWA
ZZ
AR

:

00
01
02
03
05
06
07
08
09
: XXX99
:
-:
Yes

=
=
=
=
=
=
=
=
=
=

DTU Loss of frame alignment
DTU Remote alarm detected
DTU Alarm Indication Siganl (AIS) detected
DTU Excessive error rate detected
DTU Clock error detected
DTU Alarm indication by LTU
DTU Signalling handles watch dog alarm
DTU Loss of multiframe alignment
DTU Remote alarm Timeslot 16 detected
DTU board address

A DTU alarm has been generated. The error type in the additional information in the fault
report identifies the reason.
It is beyond the scope of this manual to explain the possible reasons. Just report the reason
when replacing the board.
SAS will subsequently disable call processing for the PCTs controlled by the board, and
possibly generate a PCT removed alarm. The latter alarm is possible when the SAS takes a
PCT out of operation.
MAINTENANCE ACTIONS:
1. Error type 00,02,03,06,08:
a. Check the 2 Mb/s line, for example:
- Board connector;
- Cable might be too long;
- Too much jitter;
- Transient resistance too high.
b. DTU or Line Termination Unit (LTU), if present, might be faulty.
2. Error type 01,05,07,09:
Probably DTU or LTU (if present) faulty. Replace the DTU and/or LTU board.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-65

ALARM CODE:
ERROR TYPE:

1049
--

DTU-Slip detected
Error type
EHWA
ZZ
AR

:
-: XXX99 = DTU board address
:
-:
No

On the DTU board a "slip" is detected. This error may occur when there are bad
connections in the 2 Mb/s link. This alarm can also be given when taking the 2Mb/s link in
service, for example, after installation, or after starting up the system.
"Slip" occurs when the clocks of the interconnected exchanges are not synchronised.
MAINTENANCE ACTIONS:
1. Check that one of the systems is “clock-slave” of the other and that in the “slave”-system
the concerned DTU has a connection to the clock circuit-inlet on the PMC.
2. Check that the DTU-board functions properly.

13-66

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1050
--

PCT Excluded from Normal Traffic
Error type
EHWA
ZZ
AR

:
-: XXXXX = PCT
:
-:
Yes

The indicated Peripheral Circuit (PCT) is excluded from normal traffic for reasons beyond
its control. This alarm will be generated 24 hours after the alarm situation arose. It has a
different meaning, depending on the PCT type: (for PCT type: see PE procedure 4000)
Voice/Data Channel : SOPHO-SET not or not correct connected.
Data Channel
: LAM not or not correct connected.
Trunk unit
: Trunkline not connected or trunk in distant exchange not in
operation.
B or V channel
: Opposite B or V channel not in operation (used with DTU-PR)
D-channel
: D channel not in operation (used with DTU-PR)

Note: This alarm may be related to alarm code 1042, error type 50/60/61/70/80.
MAINTENANCE ACTIONS:
1. a. Check the terminal connections in case the indicated PCT is a Voice Channel or a
Data Channel.
b. Check the connection to the distant exchange in case the indicated PCT is an ATU.
2. B-channel/V-channel : check opposite B-channels/V-channels
3. D-channel
: check other alarms. If problem still remains: Replace the
boards.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-67

ALARM CODE:
ERROR TYPE:

1051
--

PCT Blocked by Dial Tone Time Out
Error type
EHWA
ZZ
AR

:
-: XXXXX = PCT
:
-:
Yes

This alarm will be generated only if a check on time out of dialtone has been defined by PE
procedure 2028.
After detection of no-dial-tone, the trunk concerned is given to a process that checks at
regular intervals if still no dial tone can be detected. If now dialtone is detected the trunk line
is again available for call processing. The trunk line becomes also available again for call
processing when an incoming seizure is detected.
MAINTENANCE ACTIONS:
1. Check the operation of the indicated Peripheral Circuit (PCT) with the test telephone
and possibly with a manually controlled test.
2. Maybe the trunk is not connected to the public exchange, because the emergency
bypass is active.
3. If no error is found, check with the staff of the public telephony exchange.

13-68

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1052
--

ISDN Trunk(s) excluded from normal traffic
Error type
EHWA
ZZ
AR

:
-: XXXXX = PCT
:
-:
Yes

This alarm can occur for:
1. Trunks on the DTU-BA or DTX-I. It means that the signal on the trunk is too bad; the
trunk is excluded from normal traffic.
2. The D-channel on the DTU-PH. It means that the 'data link protocol' has failed. All
trunks on the DTU-PH are excluded from normal traffic.
MAINTENANCE ACTIONS:
In case of the alarm occurs for:
1. A trunk on the DTU-BA or DTX-I, then:
a : Check the line e.g.

-

Board connector;
Cable might be too long;
Check line signal.

b : DTU-BA or DTX-I might be faulty.
2. The D-channel on the DTU-PH:
a : If there are alarms 1048 for the board, then perform the maintenance actions for
1048. Ignore alarm 1052 until the alarms 1048 disappear.
b : If there are no alarms 1048 for the board, then the system will try to re-establish
the link. If this is successful, then alarm 1052 will disappear, else the data link
protocol needs to be checked for errors.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-69

ALARM CODE:
ERROR TYPE:

1060
--

Output Device Absent
Error type
EHWA
ZZ
AR

:
-: 00000
:
-:
Yes

The system has output data for an application, for example toll ticketing, but the device to
receive it, for example a printer, has not been connected to the CPU.
For toll-ticketing output this alarm is generated only when the internal buffer is filled for
more than 80%. The alarm is cleared when the buffer has been emptied to a filling level
below 60%. There is, therefore, only an indirect relation between the alarm and a device
being connected or not.
The output data is buffered. If the buffer is full, additional data is lost.
MAINTENANCE ACTIONS:
1. Connect the device as soon as possible, to avoid loss of data.
Ensure beforehand that the baud rate of the system and the device are the same.
2. If the alarm is raised while the device is connected, verify the correct working of the
channel.

13-70

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1065
--

SOPHO SystemManager (SSM) Fault
Error type
EHWA
ZZ
AR

:
*
: 00000
:
*
:
No

* Refer to the SOPHO SystemManager Customer Engineer Manual.
The connected SOPHO SystemManager has generated an alarm.
MAINTENANCE ACTIONS
1. Check the SOPHO SystemManager and its interface to the system.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-71

ALARM CODE:
ERROR TYPE:

1066
00,10,20,30,80,90,95

SOPHO SystemManager Communication Failure
Error type

EHWA
ZZ
AR

:

00 = SOPHO SystemManager communication failure or SOPHO
SystemManager absent (ZZ = link number)
10 = Not enough memory to completely start a switching service (ZZ
= degree to which the service started)
20 = Management functions/CPU mismatch
30 = SOPHO SystemManager can not handle a service (ZZ =
service number)
80 = Remote Session 4 x wrong password
90 = Remote Alarming, no connection
95 = Remote Toll Ticketing, no connection
: 00000
: Link grade or service number
:
No

ALARM SEMANTICS:
The system has found an error in the communication with an external device (a SOPHO
SystemManager or a remote service device).
MAINTENANCE ACTIONS:
00ZZ : 1. Connect the SOPHO SystemManager as soon as possible to avoid loss of
information. Ensure that the baud rate of the system and the SOPHO
SystemManager are the same.
2. Ensure that the cable to the SOPHO SystemManager is connected.
3. Check the SOPHO SystemManager. If serviceable, replace the cable to the
system.
10ZZ
20-30ZZ
80-90--

95--

13-72

:
:
:
:
:

Decrease the number of switching services
Reset the number of switching services by system warmstart
SOPHO SystemManager fault. Consult relevant documentation.
Verify that remote connect attempt was authorised.
Verify that : - Modem is connected to CMS90 and is operational;
- Remote Set Up parameters are correct;
- Remote Service center is available.
: See 90--.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

ALARM CODE:
ERROR TYPE:

1080
--

Clock Supply Warning
Error type
EHWA

ZZ
AR

:
-: 10360
10760
01760
01360
11360
01960
:
-:
Yes

(iS3010)
(iS3030)
(iS3050)
(S250)
(S1000)
(iS3050)

PMC
PMC
PMC
CSN
CSN
CSN

MAINTENANCE ACTIONS:
1. Check if the Primary Rate (2MB/s) or Basic Access links are according the projecting
parameter 4180 and the signal group data (Basic Access only).
2. Check the cables between PMC and DTUs or CSN and DTUs.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-73

ALARM CODE:
ERROR TYPE:

1081
00

PCT Warning
Error type
EHWA
ZZ
AR

:
00 = Service degradation warning
: XXXXX = PCT
:
-:
No

During startup of an intelligent terminal, it is detected that the terminal does not support all
features offered by the system.
MAINTENANCE ACTIONS:
Consult specification of the terminal and system to know which features will not work.
Decide if lack of these features is acceptable. If not replace the terminal with a more
intelligent type.

13-74

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

13.3.

USER COMPLAINTS

The following information consists of guidelines for the pinpointing of faults which are not
automatically alarmed, but are detected by users (including the operators).
Always deal first with any alarms!
See ”Actions in Case of Alarm”.
In the guidelines which follow it is assumed that the problem does not originate from the
telephone sets or the connections between the telephone sets and the system Main
Distribution Frame (MDF).
In case of doubt, use a spare telephone set which is 100 % serviceable, connected directly
to the MDF Analogue Line Circuit (ALC) block by means of an MDF test plug. This test plug
causes the line to be disconnected. Ensure that there is a reliable ground connection
between the telephone set and system ground for the enquiry button.

13.3.1.

Extension Users

COMPLAINT: NO DIAL TONE - USING A ROTARY DIAL SET OR A KEYTONE SET
Possible causes:
- In case of complaint "No dial tone, also after repeated attempts":
. Analogue Line Circuit (ALC) defective (loop detection, transmission path);
. Circuit not in service.
- In case of complaint "Sometimes no dial tone":
. The dial tone generator on the PMC is defective;
. Intermittent fault on the ALC(s) concerned.
ACTIONS:
If the complaints are related only to one ALC board, then follow Actions A1 to A6. If the
complaints are related to extensions distributed over two or more ALC printed wiring
boards, then follow Action B1. (See project data print-out, or use OM command.)
A1. Determine the position of the ALC printed wiring board concerned.
A2. Ensure that the ALC printed wiring board and front connector are pushed firmly home
and make a visual check of the relevant MDF connections.
A3. Check the service condition of the ALC circuit. It should be In Service-No Owner (INSNO) when the telephone handset is on-hook, and In Service-Call Processing 2 (INS-

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-75

CP02) when off-hook. Check this condition using OM 7030 to display the service
condition, and asking the extension user to lift and replace the handset.
A4. If the above mentioned service conditions cannot be achieved then set the ALC board
to Out of Service (OUT) using OM 7012. Then set the ALC board to In Service (INS)
using OM 7010.
Now repeat the service condition check, Action 3.
A5. If no improvement, replace the ALC printed wiring board in accordance with Chapter
14.
A6. If no improvement, then re-check the above results by means of a more careful
investigation (if necessary replace the cable between the ALC board and the MDF).
B1. The complaints are related to extensions connected to various ALC printed wiring
boards. Replace the PMC in accordance with chapter 14.

COMPLAINT: DIALLING NOT POSSIBLE (CONTINUOUS DIAL TONE)
Possible causes:
- In case of impulse telephone set (in systems with or without Receiver/Sender for
Keytone/Dial tone (RST-KD):
. Analogue Line Circuit (ALC) defect (loop detector does not detect short loop
interruptions).
- In case of keytone telephone set (in systems with or without RST-KD):
. ALC defect (transmission path defective).
. One of the Receiver Key Tones (RKTs) is defective.
ACTIONS:
1. Execute a manually controlled test on all RKTs (in circuit condition INS). If an RKT is
reported defective and it is located on the PMC, replace the PMC printed wiring board in
accordance with Chapter 14. If an RKT is reported defective and it is located on the
RST-KD, replace the RST-KD printed wiring board in accordance with Chapter 14.
2. If complaints are linked to one or more extensions connected to the same ALC printed
wiring board, replace the ALC printed wiring board in accordance to chapter 14.

13-76

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

COMPLAINT: NO LONG-DISTANCE OR INTERNATIONAL DIAL TONE (ALSO FOR
OPERATOR) - IN COUNTRIES WITH PUBLIC EXCHANGE 2ND DIAL TONE
Possible causes:
- Incomplete project data.
- Public Exchange does not give 2nd dial tone (on one or more lines).
- Receiver Dial Tone does not detect the 2nd dial tone (from one or more exchange lines).

Note: The last two mentioned causes are under the assumption that the Project data
specifies: synchronisation with Public Exchange dial tones for dial tones
regenerated by the system to the caller.
ACTIONS:
1. Ensure that the project data part for the External Numbering scheme is complete
2. Verify the exchange lines (trunk group and line number, circuit conditions).
3. If Project Engineering data and the line conditions are in order, replace the PMC in
accordance with chapter 14.

COMPLAINT: NO DIAL TONE AFTER PRESSING ENQUIRY BUTTON
Probable cause: ALC printed wiring board defective (Ground detectors, Inbus hardware).
(In case of loop-interrupt button, ensure that actual loop-interrupt time is within the PE data
specification.)
ACTION:
Replace the ALC printed wiring board concerned, in accordance with the instructions in
chapter 14.

COMPLAINT: EXTENSION DOES NOT RING
Probable cause: ALC printed wiring board defect (Ringing relay, Outbus hardware).
ACTION:
Replace the ALC printed wiring board concerned, in accordance with the instructions in
chapter 14.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-77

COMPLAINT: WRONG DESTINATION
Possible causes (Direct Dialling In (DDI) and Transit connections not taken into account):
- If related with internal destinations:
. In case of impulse telephone set:
ALC loop-monitor is not detecting loop interruptions properly.
. In case of keytone extension.
Receiver Keytone (RKT) is not working properly.
- If related with external destinations:
. In case of impulse or loop signalling on the trunk line group concerned:
The impulse circuitry in one or more Trunk Units is not functioning correctly.
. In case of keytone signalling on the trunk line group concerned:
Sender Keytone (SKT) is not working properly.
ACTIONS:
If the problem occurs only with external destinations, see action 1or 2.
If the problem occurs with both internal and external destinations, see action 3 or 4.
1. External destinations and impulse or loop signalling on trunk line group concerned:
Investigate the problem by checking all Trunk Units of the trunk line group, using the test
telephone. If a Trunk Unit is found, check whether the Trunk Unit itself is defective, or
whether there is an external cause (line or distant exchange) by temporarily
interchanging lines within the trunk line group.
2. External destinations and keytone signalling on trunkline group concerned: If the system
is equipped with an RST-KD, execute a manually controlled test on all SKTs (in service
condition INS). If an SKT is reported defective, replace the RST-KD board concerned in
accordance with the instructions in chapter 14.
The SKTs on the PMC board can only be tested implicit with the RKT test. If the RKT
test is terminated without an error report, than the SKTs are also in order.
3. Internal destinations and impulse telephone set. Replace the associated ALC printed
wiring board.
4. Internal destinations and keytone telephone set: Execute a manually controlled test on
all RKTs (in circuit condition INS). If an RKT is reported defective, replace the PMC or
the RST-KD printed wiring board concerned in accordance with Chapter 14.

13-78

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

COMPLAINT: NO TICKER TONE (THREE-PARTY CONVERSATION WITHOUT
OPERATOR INVOLVEMENT)
Possible causes:
- Add-on and Tone Control (ATC) circuit on the PMC defective.
ACTION:
Replace the PMC in accordance with the instructions in Chapter 14.

COMPLAINT: THREE-PARTY CONVERSATION (WITHOUT OPERATOR
INVOLVEMENT) DOES NOT WORK PROPERLY
Probably a defect in the Add-on and Tone Generator Control (ATC) circuit on the Peripheral
Module Controler (PMC).
ACTION:
Replace the PMC in accordance with the instructions in Chapter 14.

13.3.2.

Operator

COMPLAINT: ANALOGUE OPERATOR POSITION NO LONGER FUNCTIONS
Possible causes:
- Operator Position has switched over to condition "absent";
- Operator Position has been set to circuit condition OUT or NIN;
- Data communication with the Operator Position is faulty.
ACTIONS:
1. Set circuit condition to INS.
2. Disconnect the handset plug, then plug it in again.
3. If no improvement, ensure circuit condition of Operator's Position is INS. EHWA of AOC:
10310, 10311 for S55;
10710, 10711 for S255.
4. If no improvement, use one of the other Operator Positions to read out the fault reports
and deal with them in accordance with the instructions in section ”Actions in case of
alarm”.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-79

5. If necessary, test the Operator Position using the "self-test". See Chapter ”diagnostic
test”.

COMPLAINT: OPERATOR POSITION REACTS IN AN ABNORMAL WAY
Possible causes:
- One or more "lamps" (LEDs) are defective;
- A Number Display is defective;
- One or more keys are defective.
ACTION:
Test the Operator Position using the "Self-test". See Chapter ”Diagnostic test”.

COMPLAINT: NO TICKER TONE (THREE-WAY CONVERSATION WITH OPERATOR
INVOLVED)
Possible causes:
- Add On and Tone Generator Control (ATC) on the PMC defective.
ACTION:
Replace the PMC in accordance with the instructions in Chapter 14.

COMPLAINT: THREE-WAY CONVERSATION (WITH OPERATOR INVOLVED) DOES
NOT WORK PROPERLY
Probably a defect in the Add On and Tone Generator Control (ATC) on the PMC, or a faulty
Analogue Operator Card (AOC).
ACTION:
Replace the AOC / PMC in accordance with the instructions in Chapter 14.

13-80

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

COMPLAINT: SOMETIMES THE TAXMETERING REPORTING CALL DOES NOT
OCCUR
After termination of an outgoing call for which taxmetering was controlled, no cost-reporting
call occurs.
Possible causes:
- The Public Exchange is not sending taxmetering impulses on one or more exchange
lines.
- The Metering Circuit is defective.
- Since the Metering Circuit is not on the Analogue Trunk Unit (ATU), either the connection
between the Metering Circuit (MC) card and the ATU is faulty or the ATU is faulty.
- Analogue Combination Card (ACC) faulty.
ACTIONS:
1. Determine which exchange line(s) are concerned (trunk group and line number(s), as
indicated by the display on the operator position).
2. Convert the trunk group and line number(s) to hardware address(es), by using OM
command.
3. Replace the ATU or MC board in accordance with Chapter 14. If an ACC with a Trunk
Unit is applied, replace the TU or ACC.
4. If there is no improvement, check the exchange line, by temporarily interchanging lines
within the trunk line group, for example.

9707

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-81

13.4.

ALARM CODES TABLE

The alarm codes are summarized in table 13.7. (MA, MI and SI stand for Major, Minor and
Silent Alarm respectively.)

ALARM
CODE

ALARM CODE MEANING

DEFAULT
ALARM TYPE

NOTES

PAGE(S)

1000

Major Alarm Overflow

MA

99

13-7

1002

Minor Alarm Overflow

MI

99

13-8

1003

Silent Alarm Overflow

SI

99

13-9

1005 *

Major Alarm External

MA

99

1006

POM-Memory Error

MA

99

Major Central Equipment Alarm

MA

99

Major, only by system restart recoverable, PM fault

MA

01

13-24
13-26

1008

*

1009
1010

2,4

13-10
13-11

1,2,3

13-12...22

Cold Start Done

MA

99

1011

*

Warm Start Done

SI

99

2

13-27

1013

*

Restart Done

MI

01

2

13-28

1014

*

PE Parameter Error

MI

99

2

13-29...33

1015

Emergency bypass function is activated

SI

99

1023

*

Garbage Buffer Overflow

SI

99

2

13-35

1030

*

Minor Alarm External

MI

99

2,4

13-36

1040

*

Board Fault

MI

02

1041

*

Intermittent PCT Fault

MI

98

2

13-44/45

1042

*

PCT Fault

MI

99

2,4

13-46...54

1043

*

DCC Board Alarm

MI

99

13-56

1044 *

DCC Board Configuration Alarm

MI

99

13-62

1045 *

Manually Controlled Test - Error Report

MI

99

1046 *

Manually Controlled Test - Information

MI

99

13-64

1048

DTU Alarm

MI

98

13-65

1049

DTU-Slip detected

SI

99

13-66

1050 *

PCT Excluded from Normal Traffic

MI

99

2,4

13-67

1051 *

PCT Blocked by Dial Tone Time Out

MI

99

2,4

13-68

1052

ISDN Trunk(s) excluded from normal traffic

MI

99

1060 *

Output Device Absent

MI

99

1065 *

SOPHO SystemManager (SSM) Fault

MI

99

13-71

SOPHO SystemManager Communication Failure

MI

99

13-72

1080

Clock Supply Warning

MI

99

13-73

1081

PCT Warning

MI

99

13-74

1066

*

*

13-34

13-37...43

2,3

13-63

13-69
4

13-70

alarm level (MA, MI or SI) can be defined in PE data, therefore check PE data to see if the default applies or not.

Table 13.7. Alarm Codes.

See notes overleaf.

13-82

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9707

Notes: 1.
2.
3.
4.

9707

May mean a total telephony failure.
Fault Integration possible; see PE data.
Automatic Recovery carried out for most of the faults.
Automatic Recovery carried out for all fault.

DB-A 9150e-35
© Philips Communication Systems B.V. 1997. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

13-83

14.

REPLACEMENT PROCEDURES

The following sections give detailed instructions for the replacement and associated testing
of hardware items in an operational exchange. Possible reasons for the replacement are:
- Item is defective/suspect;
- Item must be replaced by another version;
- Item must be replaced by a more expanded version.
The instructions are of course, also applicable:
- When an item has to be temporarily removed/disconnected.
- As general test instructions per type of item, e.g. for the purpose of testing spares
holdings.

14.1.

COMPATIBILITY

Before replacing a hardware item of a system, a check must be made to ensure that the
part substituted for the original is a permissible replacement, hence compatible with the rest
of the system.
Replacement is always permitted when:
- The first 9 digits of the type number of the replacement item are the same as those of the
unit being replaced.
- The 10th digit of the replacement item is the same as or higher than that of the item being
replaced (except for items from any pre-production series for which consecutively 10th
and 11th digit combinations 99, 98, 97,... are used).
Replacements which deviate from this rule are only permitted when laid down in the
administration (a list of replacement type numbers for example) of the department
responsible for project engineering.

14.2.

TESTING SPARES HOLDINGS

For the efficient rectification of faults, it is essential that the spare hardware units held in
stock are always complete and 100 % functionally tested. Because the boards are
frequently transported, it is important (other than for Peripheral Circuits), to repeat a
functional test from time to time.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

14-1

14.3.

TIME OF REPLACEMENT

Before deciding to make a replacement, the following factors should be considered:
- The inconvenience caused to the user by the existing problem;
- The inconvenience that would be caused by the proposed replacement action.
When necessary, effect replacements outside working hours. For example:
- An ALC defect, where one of the other seven ALCs on the printed wiring board must
generally not be disturbed (a data line for example).
Replacements and similar operations should always be made in consultation with the
system operator/manager. They are then also notified in respect of possible new alarms.

14.4.

RE-TEST AFTER REPLACEMENT

When a problem has disappeared after replacement of a hardware part, it cannot always be
concluded that the replaced part was the cause of the problem. It is possible that another
condition has changed simultaneously with the replacement, whether or not as a result of
the actions of replacement.
For this reason it is recommended that in general the hardware part is not (immediately)
sent away for repair, but first set into operational use once again, if possible in a harmless
location, but in any case a location where minimum inconvenience is caused to users. It
should also be ensured that the suspect hardware is subjected to intensive use.

14.5.

WRITING OF REPAIR FORM (REPAIR CARD)

When a hardware part is found to be defective, it must be sent for repair. For this purpose it
is most important that the detected problem is clearly indicated on a repair form to be
attached to the part. In addition to the general administrative details, give the following
information:
- Problem

: Alarm code and (if applicable) the additional information or a short
description of the problem.
- Circuit
: Complete hardware address (as given with the alarm code in the case
of alarms).
This defines the suspect area in most cases to one of the individual
circuits on the printed wiring board concerned.
- Circumstances : Specific conditions which must exist before the problem manifests
itself.

14-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

14.6.

UPDATING PROJECT RECORDS

When one or more type numbers change (different 12th digit, ... completely different type
number) due to replacement(s) within the exchange, this must be noted in the technical
records of the exchange concerned.

14.7.

REPLACEMENT PROCEDURES

All replacement procedures follow a basic pattern of five steps. These are as follows:
-

Set out of service (service condition OUT);
Remove front cables (as appropriate);
Remove and replace faulty board;
Replace front cables (as appropriate);
Set into service (service condition INS).

This basic pattern can be followed throughout all the procedures, but there are many
exceptions and special cases.
A few basic rules apply to all cases:
- Take the necessary precautions to prevent electrostatic discharge. Use for example
grounded anti static floor mats and/or table mats, be sure to ALWAYS wear a grounded
anti statics wrist strap.
- NEVER remove a Peripheral Circuit (PCT) board that is NOT in the OUT or NIN
condition. Always check first that the desired OM command was executed to protect
against errors.
- When putting a PCT-board or piece of equipment back into service (service condition
INS) ensure that it actually goes to INS. This may take some time.
- When a board has more than one front connector, it is advised that they are marked
before being removed, to avoid confusion. Use labels as necessary.
- When a board has front connections the front connectors should always be removed
before the board is removed from the shelf.
- When a board is replaced it should be inserted and removed at right angles to the shelf
using the correct tool. This is to ensure that all back panel connections are made or
broken at the same time.

14.7.1.
1.
2.
3.
4.

Replacement of PMC

Check the number of the replacement item (see section 14.1.).
Remove the faulty board from the shelf.
Insert the replacement board, a warmstart is carried out.
Check that the PPU contains the correct software package, if not download the correct
software package.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

14-3

14.7.2.
1.
2.
3.
4.
5.

Check the number of the replacement item (see section 14.1.).
Remove the PMC board from the shelf.
Remove the faulty AOC daughter board from the PMC.
Plug the replacement AOC daughter board into the PMC board.
Insert the PMC board into the shelf, a warmstart is carried out.

14.7.3.
1.
2.
3.
4.
5.

Replacement of the Alarm Unit

Switch off external alarms and ESU.
Replace alarm unit.

14.7.5.
1.
2.
3.
4.
5.

Replacement of DOC

Check the number of the replacement item (see section 14.1.).
Remove the PMC board from the shelf.
Remove the faulty DOC daughter board from the PMC.
Plug the replacement DOC daughter board into the PMC board.
Insert the PMC board into the shelf, a warmstart is carried out.

14.7.4.
1.
2.

Replacement of AOC

Replacement of VPU

Check the type number of the replacement item (see section 14.1.).
Remove the front connectors from the faulty board.
Remove the faulty board from the shelf.
Insert the replacement board.
Replace the front connectors on the new board.

14.7.6.

Replacement of CPU

If the running POM data differs from the previously downloaded or last backuped POM
data, because it has been modified by OM, then make a new backup of the Run Time POM
database into the Flash EPROM POM memory and copy it to the MPC.
1.
2.
3.
4.
5.

Disconnect the primary supply.
Check the type number of the replacement item (see section 14.1.).
Disconnect the front cables from the board.
Remove the faulty board from the shelf.
Insert the replacement board.

14-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

6.
7.

Reconnect the cables.
Reconnect the primary supply and a system start up is carried out. This is indicated by
the red LED and the green LED. During a system start up POM database (if present) is
copied from the Flash EPROM POM memory into the Run Time Database RAM
memory.
8. Check that the CPU contains the correct software package.
9. If no POM database is available in Flash EPROM POM memory, then download the
previously saved POM data and execute the ”coldstart” procedure.
10. Note any alarms except Coldstart Done (1010).
11. Reset all alarms.
12. Check that telephone traffic is possible.

14.7.7.

Replacement of the VIC

If the running POM data differs from the previously downloaded or last backuped POM
data, because it has been modified by OM, then make a new backup of the Run Time POM
database into the Flash EPROM POM memory and do a download.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

Disconnect the primary supply.
Check the type number of the replacement item (see section 14.1.).
Disconnect the front cables from the board.
Remove the CPU board from the shelf.
Exchange the VIC daughter board.
Insert the CPU board.
Reconnect the cables.
Reconnect the primary supply and a system start up is carried out.
Note any alarms except Coldstart Done (1010).
Reset all alarms.
Check that telephone traffic is possible.

14.7.8.

Replacement of Peripheral Circuits

The following Peripheral Circuits are covered by this procedure:
1.
2.
3.

Receiver/sender for Keytones/Dial tone (RST-KD, RST-KD-02 or RST-KD-03);
Analogue Line Circuits, for the KTLC board see note 1;
Analogue Trunk Units;
Digital Trunk Units.
Check the type number of the replacement item (see section 14.1.).
Set the board out of service.
Remove the front connectors from the board.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

14-5

4.
5.
6.
7.

8.

Remove the board from the shelf.
Insert the replacement board.
Set the board into service.
For ALC-A01 perform the following test:
- Make a call to the connected telephone set (or to a telephone set plugged into the
MDF).
- Make a call from the connected extension (or from a telephone set plugged into the
MDF).
- During one of these two calls use the enquiry button (twice) to go to and from the
enquiry condition (test of the detector; it is not necessary to go any further than the
reception of dial tone).
Replace the front connectors onto the new board.

Notes: 1) If the KTLC board with 8 PCTs is removed from a shelf while the power is on,
there is a chance that the data stored in the RAM is mutilated. To avoid startup problems it is advised to clear the contents of the RAM. This can be done
by removing and replacing strap X2.1, while the KTLC board is removed from
the shelf.
2) For the KTLC board with 16 PCTs strap X2.1 should be removed from the
board since the RAM of this board is backed up through the backpanel.

14.7.9.
1.
2.

3.
4.
5.
6.
7.

Replacement of MC/MCE OR ESU

Check the type number of the replacement item (see section 14.1.).
Set out of service the Analogue Trunk Units (ATUs) and Analogue Line Circuits (ALCs)
connected to the faulty board. (See Office Data manual for details of the appropriate
ATUs and ALCs).
Remove front connectors from the board.
Remove the board from the shelf.
Insert the replacement board into the shelf.
Replace front connectors onto the new board.
Set into service any ATUs and ALCs, which were set out of service in step 2.

14.7.10.

Replacement of the PSU

Replacing PSU will put the system out of operation.
If the running POM data differs from the previously downloaded or last backuped POM
data, because it has been modified by OM, then make new a backup of the Run Time POM
database into the Flash EPROM POM memory.

14-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

1.

2.
3.
4.
5.
6.
7.
8.

Check that the new PSU is compatible (see section 14.1.).
Note: A PSU-S can not be replaced by a PSU-ML. A PSU-ML can on a termporary
basis be replaced by a PSU-S.
Remove the external power supply or mains voltage supply.
If connectors are mounted at the front side of the PSU: remove them.
WAIT AT LEAST 5 MINUTES.
Pull the PSU out of the shelf.
Insert the new PSU.
Connect the external DC supply or mains voltage as required.
Power up. A warm start is carried out. This is indicated by the red LED and green LED
on the CPU.

For installing the transformer refer to chapter 15.

14.7.11.

Replacement of DLCs

• General
The DLC-C board contains hardware to control DLC-D boards.
One DLC-C and one DLC-board, should always occupy positions in the same unit group.
The master-slave relation of the boards should be defined by projecting procedures.
If in doubt about the DLC-C to DLC-D connections, check them against figure 14.1. Also,
the slot number of the DLC-C board must be lower than for any DLC-D board.
DLC-C
(pos.n)

DLC-D
(pos. n+1)

FAA

FAA

FAB

FAB
Figure 14.1. DLC-C, DLC-D Connections.

DLC-I requires no special attention.
• Replacement of DLC-C
1. Set the circuits of the DLC-C and the DLC-D boards in the same unit group to OUT.
2. Remove all cables.
3. Remove the DLC-C board.
4. Insert the replacement board in such a way that no connection is made with the
backpanel.
5. Connect all cables.
6. Put the replacement board in position.
7. Wait until the green LED on the DLC-C lights and the red LED extinguishes.
8. Set the circuits on the board to INS.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

14-7

• Replacement of DLC-D
1. Set the circuits of the DLC-C and DLC-D boards in the same unit group to OUT.
2. Remove the upper cable (FAA) of the DLC-board followed by the lower cable (FAB).
See figure 420.
3. Remove the DLC-D board.
4. Check the type number of the replacement item (section 14.1.).
5. Insert the replacement board.
6. Remove the DLC-C board for 5 sec. and put it back, with the frontconnectors
inserted.
7. Connect the lower cable (FAB) of the board followed by the upper cable (FAA). See
figure 420.
8. Wait until the green LED on the DLC-C lights and the red LED extinguishes.
9. Set the circuits on the board to INS.
• Replacement of DLC-I, DTX-I and DLC-U
1. Check the number of the replacement item (see section 14.1.).
2. Follow the same procedure as for DLC-C.

14.7.12.
1.
2.
3.
4.
5.
6.
7.

Check the type number of the replacement item (see section 14.1.).
Set the circuits on the related DTU-board out of service.
Remove the front connectors from the IPH-boards.
Remove the IPH-boards from the shelf.
Insert the replacement IPH-A and IPH-B boards.
Replace the front connectors onto the new boards.
Set the circuits on the related DTU-board in service again.

14.7.13.
1.
2.
3.
4.
5.
6.

Replacement of the IPHs

Replacement of LTU

Check the number of the replacement item (see section 14.1.).
Set the circuits on the related DTU-board out of service.
Remove the front connectors from the board.
Remove the board from the shelf.
Insert the replacement board into the shelf.
Replace the front connectors onto the new board.

14-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

15.

POWER SUPPLY INSTALLATION

15.1.

EARTH AND POWER CONNECTIONS

This chapter explains how to:
- Make the earth and power connections;
- Install the transformers / rectifier unit;
- Install an external power supply.
The SOPHO ISPBX can be powered directly from the mains. It is not possible to adjust the
required voltage for the ISPBX. The power provision must be provided with switch and/or a
wall-mounted socket. The switch and/or the socket must be located in the same room as
the ISPBX and must also be suitably located near by the ISPBX.

Caution: - Do not connect the power cord to the mains power provision until the
installation is completed!!
- Be sure that the AC power provision is fused with a value of 16 A or less.
- Be sure that the primary voltage of the system matches the local mains
voltage! (See note on transformer for the SOPHO iS3010/3030).
Note:

Never shorten the mains cord.

Each cabinet has its individual Power Supply Unit. The transformers can cause very high
inrush currents. Dependent of the quality of the mains supply and the fuses, the transformer
may blow a fuse at switching on or after a power fail. A proper fuse of 16 A will normally
withstand the inrush current of a single cabinet SOPHO iS3030 with a 800 VA (or less)
transformer, even when the mains supply has very low impedance.
Automatic circuit breakers are not recommended, since they are more sensitive to high
inrush current than melting fuses. Nevertheless it is advised to test the switching on of the
ISPBX for a number of times (10x).
The ISPBX is equipped with a 4 V Emergency Battery Unit (EBU). The purpose of the EBU
is to prevent loss of project dependent data stored in memory in the event of a system
failure. The EBU is not to be connected in this stage of the installation but it is advised to
complete the installation of the system first. In the procedure for the system start up the
Emergency Battery must be connected.
The SOPHO iS3010/3030 is designed as safety class 2 equipment and therefore has reinforced isolation. This means that for the safety, with respect to hazardous voltages on the
mains supply, no safety ground is required. Nevertheless local requirements ,may demand
extra precautions. Therefore be well informed about these requirements and connect the

9505

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

15-1

earth of the system accordingly. The earth connection in the cabinets is a screw connection
point which is shown in the following diagrams:
- SOPHO iS3010 . . . . Diagram 330.
- SOPHO iS3030 . . . . Diagram 331.
- MDF Cabinet . . . . . . Diagram 460.
Diagram 335 shows how to connect the earth and safety earth cables. However, local
country earth specifications may overrule the rules as shown in diagram 335.
If additional 48 V is required e.g. for the alarm unit (if this unit is not supplied with mains
power!) this voltage can be derived from the PSU by means of a F122 connector. Diagram
321 gives the information for terminating this 48 V on the MDF.
In addition diagram 321 can be used if more information is required on the power
connections on the back panel of the SOPHO iS3010/3030.

15.2.

POWERING THE TWO CABINET SOPHO iS3030

If required it is possible to power the cabinets by an external DC supply, this should provide
power in case of a mains failure. In that case both cabinets should be powered as
described in section 15.5. External Power Supply.
When installing a second cabinet it is best to have separate fuses for both cabinets
(separate power groups). The wires of the mains supply in the building must be in
accordance with the 2 fuses (it must be installed by qualified personnel). If this solution is
too expensive, a cheaper alternative may be found in:
- Using a timed relay with delay on operate (delay > 150 msec.). This alternative uses only
one fuse, the relay takes care of spreading the inrush currents in time, so the fuse does
not have to withstand them simultaneously. Of course the timed relay has to be installed
by qualified personnel too. An example is given in figure 15.1.
- Using a 25 A fuse, provided that the wires of the mains supply in the building are in
accordance with the 25 A fuse.

15-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9505

Mains

Master
Cabinet
Main Fuse
16 A

Switch
(Optional)

Wall
socket

Slave
Cabinet

Relay
Delay on
operate

Wall
socket

Figure 15.1. Installing the timed relay for a two cabinet SOPHO iS3030.

15.3.

INSTALLING THE TRANSFORMER / RECTIFIER UNIT

Transformers used are:

Transformer
300 VA
500 VA
660 VA
800 VA

In combination with?
PSU-S and PSU-S02
PSU-ML and PSU-ML02
PSU-ML and PSU-ML02
PSU-ML and PSU-ML02

Used in sytems?
SOPHO iS3010
SOPHO iS3010/3030
SOPHO iS3010/3030
SOPHO iS3030

Secondary
outputs?

Diagram?

1 winding
1 winding
2 windings
2 windings

323
324 or 326
325 or 327
325 or 327

Table 15.1. Transformers used.

Note

: Which connecting diagram is to be used depends on the type of rectifier unit
used, because there are two different types of rectifier units. Diagrams 324 and
325 are valid for one type of rectifier unit, while diagrams 326 and 327 are valid
for another type of rectifier unit. Be sure you consult the correct diagram.

15.3.1.

Installing the 300 VA Transformer

The 300 VA transformer used in SOPHO iS3010 should be installed according diagram 323
as follows:
1.

Disconnect the mains power.

2.

Make sure you have sufficient space in the PSU compartment to be able to replace
the transformer. If not, take out the nearest PCB board(s) for sufficient space.

3.

Position the transformer as shown in diagram 323. Be sure the two notches at the
back of the transformer match in the cabinet and fasten the bolt.

9505

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

15-3

4.

Connect the two faston connectors of the transformer to the backpanel as shown in
diagram 321 and 323. The wires may be exchanged.

5.

Lead the mains cord through the ferrite ring (5 windings) and bind the ferrite ring
against the cabinet frame by means of a tie-wrap as shown in diagram 323.

6.

Connect the mains power.

15.3.2.

Installing the 500 VA Transformer

If the 500 VA transformer is used in SOPHO iS3010/3030, then install it according diagram
324 or 326 (depends on the rectifier unit type used) as follows:
1.

Disconnect the mains power.

2.

Make sure you have sufficient space in the PSU compartment to be able to replace
the transformer. If not, take out the nearest PCB board(s) for sufficient space.

3.

First connect the transformer to the rectifier unit outside the cabinet as shown in
diagram 324/326. The transformer wires to be connected to the rectifier unit may be
exchanged. Place the capacitor against the rectifier plate by means of an adhesive
disk, as shown in the diagrams.

4.

Position the transformer and rectifier unit assembly in the cabinet as shown in
diagram 324/326, this may take some force. Be sure the two notches at the back of
the transformer match in the cabinet and fasten the two bolts.

5.

Connect the two faston connectors of the rectifier unit to the backpanel as shown in
diagram 321 and 324/326. The faston connectors may not be exchanged, the red wire
is + and the blue wire is -.

6.

Lead the mains cord through the ferrite ring (5 windings) and the rectifier plate as
shown in diagram 324/326.

7.

Connect the mains power.

15.3.3.

Installing the 660 VA and 800 VA Transformers

The 800 VA is used in SOPHO iS3030 and 660 VA is used in both the systems SOPHO
iS3010/3030 and should be installed according diagram 325 or 327 (depends on the
rectifier unit type used) as follows:

15-4

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9505

1.

Disconnect the mains power.

2.

Make sure you have sufficient space in the PSU compartment to be able to replace
the transformer. If not, take out the nearest PCB board(s) for sufficient space.

3.

First connect the transformer to the rectifier unit outside the cabinet as shown in
diagram 325/327. The transformer wires of the same colour should be taken together
and connected to the rectifier unit. Place the capacitor against the rectifier plate by
means of an adhesive disk, as shown in the diagrams.

4.

Position the transformer and rectifier unit assembly in the cabinet as shown in
diagram 325/327, this may take some force. Be sure the two notches at the back of
the transformer match in the cabinet and fasten the two bolts.

5.

Connect the two faston connectors of the rectifier unit to the backpanel as shown in
diagram 321 and 325/327. The faston connectors may not be exchanged, the red wire
is + and the blue wire is -.

6.

Lead the mains cord through the ferrite ring (5 windings) and the rectifier plate as
shown in diagram 325/327.

7.

Connect the mains power.

15.4.

POWER CONSUMPTION AND FUSES

Following table shows the typical power consumption.
Typical Power Consumption [W]
Idle

0,4 Erlang/
Extension

0,7 Erlang/
Extension

Maximum
Power
Consumption
[VA]

SOPHO iS3010 (48 analogue extensions)

20

70

80

300 or 500

SOPHO iS3030 (160 analogue extensions)

40

200

250

660

SYSTEM

Table 15.2. Power Consumption.

The internal DC power provision is fused in the power supply. The PSU-S (02) and the
PSU-ML (02) are provided with fuses for the 48 V DC power provision to the shelves. The
fuses are accessible at the front side of the PSUs. The power supply is provided with a
label which gives information on the fuses. Each fuse is equipped with a LED which lights if
the related fuse is blown.
The 'OK' LED at the bottom of the PSU lights when all voltages are present. When the 'OK'
LED not lights, usually one of the fuses is blown. All fuses have the same values: 3,15 A

9505

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

15-5

fast blow, high current breaking capacity. Figure 15.2. gives an overview of the PSU fuses
and the board positions they fuse.

1
9
1

1
9
1

-48V2

-48V3

108, 109, MDF via the F122
front connector (see note)
009, 010, 101, 102
103, 104, 105, 106, 107
including power supply for

-48V4

-48V2

104, MDF via the F122
front connector (see note)
101

-48V1

-48V4

005, 006, 007, 008

102, 103

-48V1

001, 002, 003, 004

003, 004

-48V0

SUPPLIED TO BOARD
POSITIONS IN SOPHO
iS3030

001, 002

-48V0

SUPPLIED TO BOARD
POSITIONS IN SOPHO
iS3010

-48V3

the operator position

-60V
For ATU-ST02/12/26

For ATU-ST02/12/26

Distribution of -48 V to the Board positions.

Means LED

-60V
0V
GND

P
S
U
M
L

F122
-48V
(Outputs to MDF)
'OK' LED

P
S
U
M
L
0
2

-48V4
Means F122 connector position

F122
-48V
(Outputs to MDF)
'OK' LED

Means fuse
Means signalling voltage connector
for ATU-ST02/12/26.

Figure 15.2. Front Layout of the PSU-ML and PSU-ML02.

Note :

15.5.

- 48V4 group is not filtered and should be taken into account when using -48 V
from these positions.

EXTERNAL POWER SUPPLY

If required it is possible to connect an external DC supply to the SOPHO iS3010/3030
systems. This external DC supply should supply power for normal operation in the event of
a mains failure.
The external DC supply is not supported by Philips Communication Systems organisation
and should be purchased by the customer. The external DC supply should have the
specifications as mentioned below.

15-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9505

Note

:

Caution :

If an external power supply is used, Philips cannot guarentee that the external
power supply will meet the appropriate safety and EMC requirements.
It is not allowed to connect the external power supply if the internal power
supply is still active. When using an external power supply, then the
transformer and the external rectifier, if any, must be disconnected from the
system.

In case only a transformer (48-62 Hz) and bridge rectifier unit is used:
-

Transformer nominal output voltage
Maximum DC voltage after bridge rectifier

:
:

42.5
61

V (RMS)
V

Required power figures can be derived from table 15.1. Power Consumption.
In any other case:
-

-

U
I-average

51 V (- /+9 V);
7 A for SOPHO iS3010;
13 A for SOPHO iS3030 per cabinet.
I-switch-on
Depends on the properties of the external supply in combination
with input capacitance of - PSU-S (02) : 15 000 µF;
- PSU-ML (02) : 45 000 µF.
Allowed ripple : <1,2 mV Physophometrically weighted at 800 Hz;
: < 10 mV-top for frequencies > 3400 Hz.
Max. DC power interruption time : 5 ms;

Note

:

:
:
:
:

To comply with the ripple specification the positive contribution of the input
capacitance of the PSUs may be taken into account.
- PSU-S (02) : 15 000 µF;
- PSU-ML (02) : 45 000 µF.

The external DC box should be connected to the backpanel by means of two faston
connectors (+ 2 isolation sleeves) according diagram 321. The ordering numbers are:
Faston connector

-

2422 015 14263 (Philips number);
1-160304-8 (AMP number).

Isolation sleeve

-

2422 034 18203 (Philips number);
926539-1 (AMP number).

Note :

9505

Special mounting tool is required for assembling the connector for the external
DC box.

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

15-7

15-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9505

APPENDIX A

A.

FRONT CONNECTOR ASSEMBLY

A.1.

PREPARING THE 8X2 TWISTED CABLE

Step

Description/Action

1

Remove the outer cable covering leaving free 80 mm or more of the inner wires.
See figure A.1.

2

Separate and untwist wire pairs. Normally cable pairs 1...4 and 5...8 have its own
side of the connector.

A.2.
Step

PREPARING THE MULTI COAX CABLE
Description/Action

1

Remove the outer cable covering leaving free 80 mm or more of the inner wires.
See figure A.1.

2

The coax shield of the 8 wires can only be removed using a special tool. This tool is
not included in the tool set.

3

Eight common shield wires are used for connector assembling. The rest can be cut
off.

A.3.
Step

USING THE PIERCE INSERTION TOOL (Wire insertion)
Description/Action
See diagram 160 for the insertion tool parts.

Note :

Each insertion tool is set in proper conditions before leaving the factory.

1

Mount the insertion tool on the edge of the table for efficient handling and operation,
using the table clamp.

2

Separate wire pairs 1...4 and 5...8, and position the cable in the cable clamp as
shown in diagram 161 for 8x2 for twisted pair cable or diagram 162 for 8 x coax
cable.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

A-1

Step

Description/Action

3

Cable positioning
8x2 twisted wire cable
The 8x2 twisted wire cable is fit in the clamp in horizontal position. Shift the 8x2
twisted wire cable as far as the cable cover end ”hits” the arrow on top of the
insertion head as shown in diagram 161.
Coax cable
The coax cable is fit in the clamp in vertical position. Leave 10 mm between the
outer cable covering and the locating block as shown in diagrams 160 and 162.

4

Determine that the cable colours match with the connector numbering.

5

If you want to start with cable pair 1, then insert the connector into the insertion
head as shown in diagram 161. The pin numbers 101...108 of the connector should
now face the wire guiding gap.

6

Shift the connector, from left to right, in the insertion head until you hear the first
click. To confirm the correct contact cavity position: the right-end of the connector
should be in line with the connector position mark.

Caution :

7

Once in the insertion head, the connector should be shifted according
the direction of the arrow (according the diagrams: from left to right)
only. Do not shift in the opposite way, this may damage the tool.

Check that the connector and the cable are positioned correctly, before proceeding
installation.

Wire insertion
8

Select the individual wire and pull it into the wire slot in such a way that the wire is
positioned after the wire positioning hook.

9

Guide the wire underneath the insertion head and straighten the wire by a slight
force, holding the wire between the thumb and the direction finger.

10

Squeeze the hand lever till the end. The wire now should be inserted into the
contact slot.

11

Releasing the hand lever, the connector moves to the next contact cavity.

A-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

Step

Description/Action

12

Repeat the above operations for each individual wire till the whole contact row is
inserted.

13

In case the connector has to be wired selectively: Each squeeze-release action of
the hand lever moves connector to the next contact cavity.
For each connector contact that should be left empty, one squeeze-release action
of the hand lever should be carried out without a wire.

14

If a visual inspection is required during the installation pull the connector out of the
insertion head, shifting from left to right only!

15

After the first contact row is installed, pull out the connector and turn it over 180
degrees. Bear in mind step 6. The empty contact row (pin numbers 301...308) is
now facing the wire guiding gap.

16

Repeat all the steps as described above starting with wire pair 5.

17

Take out the connector after inserting the last wire. Bear in mind step 6.

A.4.
Step

USING THE CLAMPING TOOL (Connector assembling)
Description/Action

1

Mount the connector covers by hand according diagram 165. This should be done
to keep the assembly together, before inserting into the assembly tool.

2

Having assembled the connector covers, insert the complete assembly, as far as it
shifts, in the head of the assembly tool according diagram 165.

3

Squeeze the hand lever till the end and release it. Now the connector should be
ready for use.

A.5.

WHEN THE INSERTION TOOL GETS STUCK

In case something went wrong and the connector is stuck in the connector insertion gap,
then it is not possible to squeeze the hand lever till the end. In that case turn the screw for
loosening the insertion punch to the left only (according the arrow). This action should
release the insertion punch and you can take out the connector, which might be broken.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

A-3

outer cable covering *
coax shield *
isolation layer *
isolation layer
coax core

8 x 2 cable

80 mm
common shield
wires

8 x coax cable

80 mm

*

80 mm to be stripped of
Figure A.1. Cable preparation.

A.6.

RE-ADJUSTING THE INSERTION TOOL

Each insertion tool is set in proper conditions before leaving the factory. A minimum of
adjustment is required during life time.
Re-adjustment should be carried out only if during installation, the individual wires are
sliding away in the wire guide after the wire was cut. In that case the pressure on the wire
has to be re-adjusted. This should be done by means of the wire guiding gap adjustment
screws as shown in diagram 160.
Factory setting of the gap is 0.2 mm.

Caution :

A-4

Be sure that after re-adjusting the wire gap is not completely closed. Closing
the gap completely would cause damage.

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

APPENDIX B

B.

S0-INTERFACE

B.1.

INTRODUCTION

The DLC-I board provides 7 and the DTX-I provides 15 basic rate (2B+D) connections,
each of which can be used as an S0 bus (2B+D S0-interface, 4-wire, 192kbps) to which
different ISDN terminals may be attached. Each B-channel has a circuit number (2 to 15 for
DLC-I, 2 to 30 for DTX-I). One S0 bus has two B-channels (0 and 1) with two adjacent
circuits for example 2&3. Channel B0 always has an even numbered circuit. A DNR can be
assigned to each circuit and, thus, to each B channel. This is the so-called ”Port Oriented
ISDN”: each B-channel has a DNR allocated to it.
At present, two types of basic rate terminals can be connected to a DLC-I and DTX-I: the P
terminals and the 1TR6 terminals.

B.2.

P TERMINALS

These are similar to the SOPHO-SET S terminals which are in use with the DLC-C/D/U
boards and they use the Terminal Message Protocol (TMP) network layer protocol on the
S0 bus.
The following types of P terminals are available:
-

SOPHO-SET P375D;
SOPHO-SET P375;
SOPHO-SET P370D;
SOPHO-SET P370;
SOPHO-LAM P375.

P terminals can be connected to a, DTX-I, DLC-I, but also to a DLC-C/D or DLC-U via a
PNT1, see figure B.1. The P terminal concept applies the proprietary Terminal Message
Protocol, which is already in use in the ISPBX to communicate with digital terminals on
DLC-C/D/U boards. There are no translations to/from other types of protocols.
The P terminal is connected to the S0 bus of either the PNT1, DTX-I or the DLC-I. The user
will not notice any difference in operation.
The PNT1 has two interfaces:
- a 2 wire 2B+D Us-interface of 152 kbps connected to a DLC-C/D/U;
- a 4 wire 2B+D S0-interface of 192 kbps to which one or two P terminals may be
connected.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-1

ISPBX
TMP

DLC-I
or
DTX-I

TMP

P
TERMINAL

DLC-C/D
or
DLC-U

ISDN 2B+D
S0-interface,
4-wire, 192 kbps

TMP

P
TERMINAL

PNT1

ISDN 2B+D
S0-interface,
4-wire, 192 kbps

ISPBX 2B+D
Us-interface,
2-wire, 152 kbps

Figure B.1. P Terminal Connection.

The 2B+D connection allows a choice of two B channels per S0 bus - channel 0 and
channel 1. This 0 and 1 are used as the Terminal Endpoint Identifier (TEI). Users of a P
terminal must allocate a TEI value which is stored in the terminal. When no value has been
allocated, the default TEI will be used; see table B.1.
NUMBER OF B
CHANNELS

DEFAULT TEI

SOPHO-SET P375D

2

0&1

SOPHO-SET P375

1

0

SOPHO-SET P370D

2

0&1

SOPHO-SET P370

1

0

SOPHO-LAM P375

1

1

P TERMINAL

Table B.1. Default TEI Values for P Terminals.

In general, B channel 0 is used for voice and B channel 1 is used for data. For P terminals
this can be changed by changing the TEI setting. This setting is changed at the terminal
itself, see the relevant Customer Engineer Manual.
For example, a SOPHO-LAM is a data terminal and normally uses B channel 1; its default
TEI is 1. If this TEI is changed to 0, it will use B channel 0 for its data connections. When
the default setting (0&1) of either the SOPHO-SET P375D or SOPHO-SET P370D is
changed into either setting 0 or setting 1, the data port of that terminal will be inactive.
When a P terminal is connected to the S0 bus it will occupy the B channel belonging to its
TEI as soon as it becomes operational. The channel becomes permanently occupied and
cannot be used by other terminals on the bus.

B-2

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

The S0 bus will be activated as soon as at least one of its B channels is put into service.
The S0 bus will be completely functional only when both of the B channels have been put
into service. After activation of the S0 bus, the PPU will wait for a specified time for the
response of connected P terminals. If no P terminals are present, the PPU will assume that
a 1TR6 terminal is connected to the S0 bus.

B.3.

1TR6 TERMINALS

The 1TR6 Terminals are specifically designed to be used with a 1TR6 network and they
use a 1TR6 protocol on the S0 bus. The DLC-U, DLC-I or DTX-I makes a mapping to the
ISPBX internal ISDN standard (based on Euro-ISDN): the SIG-protocol. This SIG-protocol
is translated by the PPU into the TMP protocol.
In the ISPBX the 1TR6 basic rate terminal can be connected to the S0 bus as follows (see
figure B.2.):
- Directly to a DLC-I or DTX-I board;
- Via PNT1, release 2 to a DLC-U.
ISPBX

1TR6

DLC-I
or
DTX-I

TMP

1TR6
TERMINAL

DLC-U

ISDN 2B+D
S0-interface,
4-wire, 192 kbps

1TR6
TERMINAL

1TR6 PNT1
(rel. 2)
ISDN 2B+D
S0-interface,
4-wire, 192 kbps

ISPBX 2B+D
Us-interface,
2-wire, 152 kbps

Figure B.2. 1TR6 Terminal Connection.

Following 1TR6 terminals are available:
- SOPHO-SET P171 also called the ”Digital Ordinary Telephone” (DOT);
- SOPHO-SET P271 also called the DOT+;
- SOPHO-SET I385 (ISDN).

Note: A maximum of two SOPHO-SET P171 and four SOPHO-SET P271 terminals may
be connected to an S0-Bus.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-3

The users of 1TR6 terminals without automatic TEI assignment should not use TEI values 0
or 1 for their terminals because it will cause the DLC-U, DLC-I or the DTX-I to start TMP
protocol instead of 1TR6 protocol. 1TR6 terminal users should allocate a correct Endgeräte
Auswahl Ziffer (EAZ) which is stored in the terminal.
For calls from the 1TR6 terminal, the B channel - EAZ relation is:
- EAZ setting 2 :
- EAZ setting 3 :
- Other EAZ
:

1TR6 terminal uses B channel 0 (even EHWA).
1TR6 terminal uses B channel 1 (odd EHWA).
1TR6 terminal uses B channel 0 or 1, depending on the presence of P
terminals on the same bus, or on the requested service.

For calls to the 1TR6 terminal, the B channel - EAZ relation is:
- 1TR6 terminal uses B channel 0 (even EHWA):
EAZ=2 is sent to the terminal.
Terminal with EAZ setting 2 or 9 will accept the call.
- 1TR6 terminal uses B channel 1 (odd EHWA):
EAZ=3 is sent to the terminal.
Terminal with EAZ setting 3 or 9 will accept the call.
In general, EAZ setting 9 is used for accepting calls with any EAZ value.

B.4.

S0 BUS RESTRICTIONS

There are a number of restrictions when connecting the P and 1TR6 terminals on the same
S0 bus; see table B.2.

WARNING

B-4

:

When an additional terminal is connected to the S0 bus the resultant
disruption caused on the S0 bus might result in loss of data in an existing
data session running on an other terminal on the same S0 bus. To avoid
this situation be sure that the terminal(s) on the same S0 bus are idle.

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

S0 BUS CONFIGURATION

RESTRICTIONS

P terminal (1) using B0
P terminal (2) using B1

It is not possible to use 1TR6 terminals on that bus because both channels
are permanently in use. Both the SOPHO-SET P375D and P370D use both
channels. Thus 1TR6 terminals cannot be used on the same bus.

P terminal using B0
1TR6 terminals not sending
EAZ=2

The P terminal occupies B channel 0 so all calls made by 1TR6 terminals will
be routed to B channel 1, irrespective of the requested service.

P terminal using B1
1TR6 terminals not sending
EAZ=3

The P terminal occupies B channel 1 so all calls made by 1TR6 terminals will
be routed to B channel 0, irrespective of the requested service.

1TR6 terminals not sending
EAZ=2 or EAZ=3

During a call to the S0 bus it is possible that all 1TR6 terminals respond,
although only one can fully support the requested service. The service
Bildtelefon (Videophone) with EAZ setting 9 requires this configuration
because it uses B channel 0 for ton (sound) and B channel 1 for bild (video).

1TR6 terminal with EAZ=2
1TR6 terminal with EAZ=3

Calls from the terminal with EAZ=2 will use B channel 0 and calls from the
terminal using EAZ=3 will use B channel 1. This configuration will be
required when two 1TR6 terminals with the same service are connected to
the bus.
Table B.2. S0 Bus Restrictions.

B.5.

CABLING S0 BUS

The S0 bus consists of 2 balanced twisted pairs with one pair for each direction: transmit
and receive. The distance between the SOPHO-SET and the ISPBX depends on the
configuration and the cable characteristics of the cable used between the wall socket and
the Main Distribution Frame (MDF) of the ISPBX.
Typical cable characteristics are given in table B.3.

S0 BUS

SPECIFICATION

Cable impedance

100 Ω at 96 kHz

Wire diameter

0.5 mm

Loop attenuation

< 10 dB / km at 96 kHz

Round trip delay

< 1 µsec / 100 m

Bit error rate

< 10-7
Table B.3. S0 Bus Specification.

Figures B.3. and B.4. illustrate the various configurations. The distances given do not
include the length of the SOPHO-SET line cord: this length is normally 6 m.
When using another cable, the length must be <10 m.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-5

Both twisted pairs must be terminated (preferably in the wall socket) with a 100 Ω resistor
on the location indicated in figures B.3. and B.4.

WARNING 1: - When using a cable with characteristics other than the ones listed in table
B.3. the distances mentioned above are different.
- An intermediate MDF in the connection can also affect the overall cable
characteristics.
- Additional attenuation,caused by joints, occurs when cables are connected
together.
When the SOPHO-SET is connected via a PNT1 to a DLC-A, B, C, D or U in the ISPBX the
distance can be extended by 1500 m. In that case the attenuation of the cable used
between the PNT1 and DLC may not exceed 15 dB (at 100 kHz, without noise insertion).
There are two reasons for using the PNT1--DLC-C/D/U combination:
- in configurations where the terminals are located beyond the maximum distance allowed
by the S0-interface: the PNT1 extends the distance between terminal and ISPBX by 1500
m.
- in situations where the existing 2-wire cabling does not allow for the connection of 4-wire
ISDN terminals.

WARNING 2: When the SOPHO-SET P is connected to the PNT1 S0 bus not using the
standard line cord but using a longer cable (and extra wall socket), that cable
must be terminated by a 100 Ohm terminator over the two transmit wires and
a 100 Ohm terminator over the two receive wires in the wall socket; in the
PNT1 the resistors R1.7 and R1.8 must be disconnected by de-soldering
solder pad X2.2 and X2.4 as illustrated in figure B.5.
When the SOPHO-SET P is directly connected to the PNT1 S0 bus all four
solder pads bust be soldered through; when no cable termination is wanted
all four solder pads must be de-soldered (open).

B-6

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

MDF

TERMINAL

1
PNT1
direct connections using the
standard terminal line cord.

ISPBX

max. 1500 m
DLC-C/D/U

TERMINAL

2

max. 600 m

max. 1500 m
PNT1

TERMINAL

DLC-C/D/U

point to point
max. 100 m

TERMINAL

max. 500 m

1

PNT1

max. 1500 m
DLC-C/D/U

y-configuration
TERMINAL

2

max. 100 m
max. 600 m

max. 1500 m
PNT1

DLC-C/D/U

extended passive bus
TERMINAL

TERMINAL

1

2
max. 100 m

= wall socket
= wall socket

with

100 Ω terminators.

without 100 Ω terminators.

= PNT1 with two of the four 100 Ω resistors disconnected; see figure B.5.
The distances mentioned are only valid when cables with the characteristics given in table B.3. are used.
Figure B.3. Possible Wiring Configuration and Distances.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-7

MDF
max. 600 m
TERMINAL

ISPBX
DLC-I
or
DTX-I

point to point
max. 100 m

TERMINAL
1

max. 500 m

DLC-I
or
DTX-I

y-configuration
TERMINAL
2

max. 100 m
max. 600 m

DLC-I
or
DTX-I

extended passive bus
TERMINAL
1

TERMINAL
2

max. 100 m
max. 150 m

DLC-I
or
DTX-I

short passive bus
TERMINAL
1

TERMINAL

TERMINAL
8

2

MDF
max. 600 m
TERMINAL

PNT1
(rel. 2)

max. 1500 m

PNT1
(rel. 2)

max. 1500 m

PNT1
(rel. 2)

max. 1500 m

PNT1
(rel. 2)

max. 1500 m

ISPBX
DLC-U

point to point
max. 100 m

TERMINAL
1

max. 500 m

DLC-U

y-configuration
TERMINAL
2

max. 100 m
max. 600 m

DLC-U

extended passive bus
TERMINAL
1

TERMINAL
2

max. 100 m
max. 150 m

DLC-U

short passive bus
TERMINAL
1

TERMINAL
2

= wall socket
= wall socket

TERMINAL
8

with

100 Ω terminators.

without 100 Ω terminators.

The distances mentioned are only valid when cables with the characteristics given in table B.3. are used.
Figure B.4. Possible Wiring Configuration and Distances.

B-8

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

PNT1 COMPONENT SIDE
R1.5

R1.6

R1.7

R1.8

MAINS
CONNECTOR

S0 CONNECTORS

PNT1 SOLDERING SIDE

X2.3

Us CONNECTOR

X2.2

S0 CONNECTORS

TERMINATION
None

X2.1

X2.4

Us CONNECTOR

TRANSMIT
X 2.1
X 2.2
Open
Open

RECEIVE
X 2.3
X 2.4
Open
Open

50 Ω

Closed

Closed

Closed

Closed

100 Ω

Closed

Open

Closed

Open

Open : solder pad not soldered through.
Closed : solder pad soldered through.
Figure B.5. Location of Solder Pads and 100 Ω Resistors in the PNT1.

B.6.

CONNECTORS AND PIN NUMBERING

• Terminal Line Cord
On both ends the terminal line cord (maximum length 10 m.) terminates with an eight way
jack. Figure B.6. shows the front view and the pin numbers of the line cord jack.
12345678
T RR T

clip

Legend: 1=not connected
2=not connected
3=transmit (T)
4=receive
(R)
5=receive
(R)
6=transmit (T)
7=not connected
8=not connected

+
+
-

(from the terminal)
(into the terminal)
(into the terminal)
(from the terminal)

and
and
and
and

power+
powerpowerpower+

Figure B.6. Terminal Line Cord Jack.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-9

• S0-interface Wall Socket
The S0-interface wall socket is a eight pins modular socket; see figure B.7. When the
SOPHO-SET is line powered, power provision is done via pin 3&6 (positive polarity) and
pin 4&5 (negative polarity) when the power source is in the normal power mode.
Legend: 1=not connected
2=not connected
3=receive
(R)
4=transmit (T)
5=transmit (T)
6=receive
(R)
7=not connected
8=not connected

12345678
RT TR

+
+
-

(from the terminal)
(into the terminal)
(into the terminal)
(from the terminal)

and
and
and
and

power+
powerpowerpower+

Figure B.7. S0-interface Wall Socket.

F122

DLC-I

MDF

WALL
SOCKET

TERMINAL

+

<

5a

4

R

+

T

302

5b

5

R

-

R

101

1a

3

T

+

-

RECEIVE

301

+

>

T

-

TRANSMIT

R

102

1b

6

T

-

RECEIVE

>

TRANS-MIT

<

Figure B.8. S0 Bus Connectors and Pin Numbers; see also table B.4.

MDF

DLC-I or
DTX-I
S0 bus 0
circuits 2&3

WALL SOCKET /
CONNECTOR
PIN NUMBER

1a

3

1b

4

5a

5

5b

6

TERMINAL

Figure B.9. On-Site Cabling.

B-10

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

S0 BUS

CIRCUIT

0

2&3

1

DLC-I
CONNECTOR

4&5

FBA:

FBA:

FBA:
2

6&7
FBA:

3

8&9
FBB:

4

10 & 11
FBB:

5

12 & 13
FBB:

6

14 & 15

101
102
301
302
103
104
303
304
105
106
305
306
107
108
307
308
101
102
301
302
103
104
303
304
105
106
305
306

MDF
BLOCK
block 1: 1a
1b
5a
5b
block 1: 2a
2b
6a
6b
block 1: 3a
3b
7a
7b
block 1: 4a
4b
8a
8b
block 2: 1a
1b
5a
5b
block 2: 2a
2b
6a
6b
block 2: 3a
3b
7a
7b

SIGNAL
MEANING
R+
RT+
TR+
RT+
TR+
RT+
TR+
RT+
TR+
RT+
TR+
RT+
TR+
RT+
T-

Table B.4. S0 Bus Connectors and Pin Numbers.

B.7.

LINE POWERING

The DLC-I or DTX-I S0 bus offers the combination of the proprietary TMP and the public
1TR6 protocol and is therefore referred to as the 'combi-bus'.
The TMP protocol and SOPHO-SET P terminals enables full access to the features and
applications offered by the ISPBX. At the same time, support of the 1TR6 protocol means
that the combi-bus provides the interface for ISDN terminals, for example a group 4 fax, a
PC, etc.
The possibility to connect two terminals per DLC-I or DTX-I line circuit ensures a more
efficient use of system ports as compared with the current DLC-C/D/U solution.
The power taken from the S0 bus, when only one terminal is connected, is 400 mW at 40V.
When the maximum number of terminals is connected, the power taken is 1W at 24V.
The maximum number of terminals which can be powered by the combi-bus depends on
the power consumption of the terminals; see the Customer Engineer manuals for the power

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-11

consumption of the SOPHO-SET P37x terminals. Any additional terminal should be mains
powered. Exceeding the maximum number of allowed line powered terminals may result in
a shut-down of the bus; normal operation is then only possible for the mains powered
terminals.

Note: Line powering is provided by the DLC-I or DTX-I; no additional LDC is required.

B.8.

CONFIGURATION ASPECTS

The 2B+D combi-bus does not support the passive bus concept in the true ISDN way but
provides a similar addressing scheme for combining up to 8 terminals on one and the same
interface. The main difference is that the combi-bus only allows 2 DNRs and it does not
support the Multiple Subscriber Numbers as defined by ISDN. The two B channels of the
combi-bus are seen, from a system point of view, as two extension interfaces, each with
their own DNR. Each B channel can be used to connect either a SOPHO-SET P37x or a
cluster of 1TR6 terminals.
The connection type must be determined in the projecting by assigning a signalling group
number to the S0 bus; see table B.5.

CONNECTION TYPE
Point-to-point
Extended passive bus
Short passive bus

LANGUAGE

SIGNALLING
GROUP NUMBER

German

0904

English

0906

German

0904

English

0906

German

0905

English

0907

Table B.5. DLC-I Signalling Group Number.

The terminals within a 1TR6 cluster are sharing the same DNR and act, seen from the user
point of view, as if they are connected in parallel. The maximum number of terminals per
cluster is 8.

Note:

In case of a SOPHO-SET P37X D (with a data port) both B channels are already
occupied: one for voice and one for data.

The maximum number of terminals that can be connected to the same bus is given in table
B.6. This table shows, the number of SOPHO-SET P terminals and corresponding number
of 1TR6 terminals for each combination; see also figure B.10.

B-12

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

SITUATION

SOPHO-SET P

1TR6 TERMINALS

1
2
3
4

2× P37x
1× P37x D
1× P37x
0

0
0
1 ... 7 (one cluster)
1 ... 8 (two clusters)

Table B.6. Maximum Number of Terminals on a Combi-bus.

Within a given a cluster any arrangement of 1TR6 terminals is possible, for example a
cluster can consist of two voice telephones, a group 4 fax and a PC.
Terminals in a cluster providing the same service, for example two 3.1 kHz voice
telephones, act as if they were connected in 'parallel'. This means that an incoming call to a
given cluster is signalled at all service compatible terminals. An incoming telefax group 4
call is only signalled on all group 4 terminals with the same DNR.
If one terminal within a cluster is off hook, all other terminals are blocked, meaning that they
can neither setup or answer a call.
ISPBX
SITUATION 1

P375 /
P370

P375 /
P370

*

PNT1

SITUATION 2

P375 D /
P370 D

*

PNT1

SITUATION 3

P375 /
P370

1TR6

**

DLC-I
or
DTX-I
DLC-C/D/U

DLC-I
or
DTX-I
DLC-C/D/U

DLC-I
or
DTX-I

PNT1
(rel. 2)

DLC-U

CLUSTER 1
SITUATION 4

1TR6

1TR6

CLUSTER 2
* :
** :

**

DLC-I
or
DTX-I

PNT1
(rel. 2)

DLC-U

CLUSTER 1

Either DLC-I or DTX-I is used or DLC-U / PNT1 (releases 1 or 2) combination is used.
Either DLC-I or DTX-I is used or DLC-U / PNT1, release 2 combination is used.

Figure B.10. Configuration of P and 1TR6 terminals.

9412

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

B-13

B-14

DB-A 9150e-35
© Philips Communication Systems B.V. 1994. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.

9412

PIN NUMBERING
FRONT VIEW
FAA

FAA
308

301

B

C

D

101

B

C

108

D
PIN NUMBERING
FRONT VIEW

FBA

FBA
101

301

B

B

C

C
108

308

PIN NUMBERING
FRONT VIEW
101

FCA

B

B

C

C

D

308

D

FCA

301

108

D

D

PWB FRONT CONNECTOR IDENTITIES
DB-A 9150e-35
Diagram 100
9209

CONDUCTIVE BRACELET OR
ANTI STATIC WRISTWATCH

USING THE ANTI STATIC BRACELET
DB-A 9150e-35
Diagram 110

9412

COLOUR OF WIRES

WIRE PAIR
5

COUNT
GROUP
a
WHITE

RED

5

b
1

1

31

61

WHITE

BLUE

1

2

32

62

YELLOW

1

3

33

63

GREEN

1

4

34

64

94

WHITE

BLACK

1

5

35

65

1

1

2

4
2

3

95

6

3

5
2

6

4

93

WHITE

3

92

WHITE

6

4

91

2

1
1

WHITE / RED

RED

2

6

36

66

96

WHITE / RED

BLUE

2

7

37

67

97

WHITE / RED

YELLOW

2

8

38

68

98

WHITE / RED

GREEN

2

9

39

69

99

WHITE / RED

BLACK

2

10

40

70

100

WHITE / BLUE

RED

3

11

41

71

WHITE / BLUE

BLUE

3

12

42

72

WHITE / BLUE

YELLOW

3

13

43

73

WHITE / BLUE

GREEN

3

14

44

74

WHITE / BLUE

BLACK

3

15

45

75

WHITE / YELLOW

RED

4

16

46

76

WHITE / YELLOW

BLUE

4

17

47

77

WHITE / YELLOW YELLOW

4

18

48

78

WHITE / YELLOW

GREEN

4

19

49

79

WHITE / YELLOW

BLACK

4

20

50

80

WHITE / GREEN

RED

5

21

51

81

WHITE / GREEN

BLUE

5

22

52

82

WHITE / GREEN

YELLOW

5

23

53

83

WHITE / GREEN

GREEN

5

24

54

84

WHITE / GREEN

BLACK

5

25

55

85

Location of the count groups
in a cable
Note : 1. The first count group 1 is located in the
centre of the cable and it contains a
transparant earthing wire
2. The corresponding a and b wires are twisted

COLOUR
WIRE
PAIR
a

b

1

RED / BLACK

RED

6a

2

BLUE / BLACK

BLUE

2b

6b

3

3a

7a

4

GREEN / BLACK

GREEN

3b

7b

5

GREY / BLACK

GREY

4a

8a

6

WHITE / BLACK

WHITE

4b

8b

7

PINK / BLACK

PINK

8

BROWN / BLACK

BROWN

1a
1b

RED

6

26

56

BLUE

6

27

57

YELLOW

6

28

58

88

WHITE / BLACK

GREEN

6

29

59

89

WHITE / BLACK

BLACK

6

30

60

Connector 1

Connector 0

87

WHITE / BLACK

YELLOW / BLACK YELLOW

Colours of wires in a front connector

86

WHITE / BLACK

5b

2a

101
WHITE / BLACK

5a

90

1a

301

101

5a

1b

6b

3a

7a

3b

7b

4a
108

6a

2b

Colours in the cables as delivered by Philips

5b

2a

301

8a

4b

308

108

COLOURS OF WIRES
DB-A 9150e-35
Diagram 120

8b

308

9412

55

CABLE STRIPPING
DB-A 9150e-35
Diagram 121

9412

INSERTING A FRONT CONNECTOR

REMOVING A FRONT CONNECTOR

INSERTING AND REMOVING
OF A FRONT CONNECTOR
DB-A 9150e-35
Diagram 122

9412

FLAT CABLE CONNECTING AND
DISCONNECTING
DB-A 9150e-35
Diagram 123

USING WIRING TOOL
DB-A 9150e-35
Diagram 130

1
10
6
2
a+b
3

a=15
b=19

7

A*

3

11
8

12
4
a=9
b=13

B*

9

C*

5
a=Cable diameter Ø 3,68
a+b
5

b=Cable diameter Ø 5.6

FIXING COAX CONNECTOR TO CABL
DB-A 9150e-35
Diagram 131

15±0.2

INSERTING AN IC
DB-A 9150e-35
Diagram 140

9209

A

B

A
C

A

B

C

B

C

*
FIRST ADJUST LEGS

* ADJUSTING PLATE
A 40 POL
B 28 POL
C 24 POL

REMOVING AN IC
DB-A 9150e-35
Diagram 141

9209

A

A

ASSEMBLING OF FLOORSTAND 1
DB-A 9150e-35
Diagram 150

9412

A

A

ASSEMBLING OF FLOORSTAND 1.5
DB-A 9150e-35
Diagram 152

9412

Min. 45cm

Min. 50cm

Min. 45cm
SLAVE
see note

MASTER

Min.10cm
Max. 900cm

Min. 45cm
Max. 900cm

SLAVE
see note

Min. 10cm
Max. 125cm

Min. Distance to the
wall in front is 80 cm

Note: Install the 2 cabinets of a
SOPHO iS3030 either
side by side or above one another.
If the cabinet at the left side is an
MDF cabinet, then install the MDF cabinet
against the system cabinet at the right side

LOCATING THE TWO CABINET
SOPHO iS3030
DB-A 9150e-35
Diagram 155

9412

CABLE CLAMP
(COAX POSITION CABLE)

CABLE CLAMP
LOCATING BLOCK
WIRE POSITIONING HOOK

(8×2 CABLE POSITION)

WIRE GUIDING GAP
WIRE SLOT
INSERTION HEAD

CONNECTOR POSITION
MARK

ARROW

WIRE GUIDING GAP
ADJUSTMENT

CONNECTOR
INSERTION GAP

CONNECTOR

HAND LEVER

TABLE CLAMP
SCREW FOR LOOSENING THE
INSERTION PUNCH, IF STUCK
(TURN LEFT ONLY)

PIERCE F122 CONNECTOR
INSERTION TOOL PARTS
DB-A 9150e-35
Diagram 160

9209

8×2 TWISTED CABLE

USE 6mm ALLEN
KEY FOR THIS SCREW

CONNECTING THE 8×2
TWISTED PAIR CABLE TO F122 CONNECTOR
DB-A 9150e-35
Diagram 161
9209

10mm

COAX

CONNECTING THE
8× COAX CABLE TO F122 CONNECTOR
DB-A 9150e-35
Diagram 162
9209

2

3
1

USING THE F122 CONNECTOR
ASSEMBLY TOOL
DB-A 9150e-35
Diagram 165

9209

3

1

2

REMOVING THE COVER
DB-A 9150e-35
Diagram 300

9412

SOPHO iS3010
UG0

P
C
T
1

P
C
T
2

UG1

P
C
T
3

P
C
T
4

P
S
U

001 002 003 004
P
C
T
5

P
C
T
6

P
M
C
M
C

C
P
U

005
TRANSFORMER
&
BATTERY
COMPARTMENT

V
I
C

101 102 103 104

105

UG2

SOPHO iS3030
UG0

P
C
T
1

P
C
T
2

UG1
P
C
T
3

P
C
T
4

UG2
P
C
T
5

P
C
T
6

UG3
P
C
T
7

P
C
T
8

UG4
P
C
T
9

P
C
T
10

001 002 003 004 005 006 007 008 009 010
P
C
T

P
C
T

P
C
T

P
C
T

P
C
T

P
C
T

PCTs

C
P
U

011

or

TRANSFORMER,
RECTIFIER
&
BATTERY
COMPARTMENT

M
C

* = CPU (VIC) is not present in
the slave cabinet. Position
108 in the salve cabinet may
cantain a restricted number of

V
I
C

D
L
C
/
L
D
C

*

11 12 13 14 15 16

P
M
C
M
C

P
S
U
M
L

101 102 103 104 105 106 107 108 109
UG5

UG6

UG7

110

UG8*UG9

TYPICAL SHELF LAYOUT
DB-A 9150e-35
Diagram 310

9412

A

D

E

B
F

PWB LOCK

G

C

MAINS CORD

FASTENING OF THE PWB LOCK IN THE
EMC CABINETS FOR SOPHO iS3010/3030
DB-A 9150e-35
Diagram 315
9412

2

S
S
S
S
S

S

S

S

S

S

S

S

MAINS CORD
S
1
S

S

CABLE TENSION RELIEF

CABLING OF THE EMC CABINETS
FOR SOPHO iS3010/3030
DB-A 9150e-35
Diagram 316

9412

TIE-WRAP

MAINS CORD

SOPHO iS3010 EMC CABINET
WITHOUT RECTIFIER UNIT
DB-A 9150e-35
Diagram 317

9412

MAINS CORD

INSTALLING THE TRUNK FILTERS FOR
ATU-SS02 AND ATU-ST02 (EMC CABINET)
DB-A 9150e-35
Diagram 318
9412

BLACK
RED

5 WINDINGS

INSTALLING THE MAINS CABLE AND
THE EBU IN A NON-EMC CABINET
DB-A 9150e-35
Diagram 319

9209

2

1

INSTALLING THE EBU IN AN EMC IMPROVED CABINET

CONNECTING AND MOUNTING
THE EBU IN AN EMC
CABINET / MOUNTING V.24 CONNECTOR
DB-A 9150e-35
Diagram 320
9412

One of the following 3 power supply combinations can be
connected to the rear side of the power compartment:

/–
/+

*
*

BLUE
POWER
RED

**
**

Safety Mains Transformer only
(safety class 2)

**

–, BLUE
+, RED
REAR SIDE POWER COMPARTMENT
Safety Mains Transformer with rectifier unit
(safety class 2)

(SOPHO iS3010/3030)


51 V DC
(+/- 9 V)

+

External DC supply
RED
EBU
BLUE

*

= Connect here the faston connectors of the transformer in case of no rectifier unit is used.
If rectifier unit is used, connect here the faston connectors of the rectifier unit. Be sure the wire colors
(polarities) match.
If an external DC supply is used, connect here the faston connectors of the external DC supply. Be
sure the polarities match.

**

= Reserved for future use.

PSU - MDF 48 V connection.
(connect only if required, e.g. if alarm unit is
fed with 48 V instead of mains)
PSU (Connector FCC)
1a 2a
1b 2b

GND

8a
8b

- 48 V

POWER CONNECTIONS
DB-A 9150e-35
Diagram 321

9412

A

A
TIE-WRAP

300VA TRANSFORMER
CONNECTING DIAGRAM
DB-A 9150e-35
Diagram 323

9412

BLUE

RED

ADHESIVE DISK

500VA TRANSFORMER AND RECTIFIER
UNIT CONNECTING DIAGRAM
DB-A 9150e-35
Diagram 324
9412

BLUE

RED

ADHESIVE DISK

660VA AND 800VA TRANSFORMER
AND RECTIFIER UNIT CONNECTING
DIAGRAM
DB-A 9150e-35
Diagram 325

9412

BLUE

RED
K
A

K

K
A

A
A

K

ADHESIVE DISK

500VA TRANSFORMER AND RECTIFIER
UNIT CONNECTING DIAGRAM
DB-A 9150e-35
Diagram 326
9412

BLUE

RED
K
A

K

K
A

ADHESIVE DISK

A
A

K

BROWN

GREEN

660VA AND 800VA TRANSFORMER
AND RECTIFIER UNIT CONNECTING
DIAGRAM
DB-A 9150e-35
Diagram 327

9505

CABLES TO MDF

EARTH CONNECTION

CABLES TO MDF

PLUG FOR CONNECTING
ANTISTATIC BRACELET

ROUTING CABLES AND EARTH
CONNECTION - SOPHO iS3010
DB-A 9150e-35
Diagram 330

9412

CABLES TO MDF

EARTH CONNECTION

CABLES TO MDF

PLUG FOR CONNECTING
ANTISTATIC BRACELET

ROUTING CABLES AND EARTH
CONNECTION - SOPHO iS3030
DB-A 9150e-35
Diagram 331

9412

Conn.
MDF

Slave
Cabinet

Disconn.
MDF

Master
Cabinet

EARTH CONNECTING DIAGRAM WITHOUT SAFETY EARTH

When using arrestors in the MDF, then
this earth connection is mandatory.

Same connections
for the next MDF.

Conn.
MDF

Disconn.
MDF

Conn.
MDF

Disconn.
MDF

Slave
Cabinet

Master
Cabinet

SAFETY EARTH CONNECTIONS

Note 1 :
Note 2 :

Local country earth specifications may overrule the earth connection rules as described in this diagram.
At the earth point of the cabinets 3 small screws and 2 big screws are available. For connecting the safety earth use
always one of the big screws.

= Earth screw

= Safety earth point

= Ground earth point (e.i. metal pin in the cellar)

EARTH CONNECTIONS
DB-A 9150e-35
Diagram 335

9209

1

2

CABLES FROM
SYSTEM
(DISCONNECTING
BLOCKS)

3

EARTH CONNECTION
20

21

EXTERNAL
CABLES
(CONNECTING
BLOCKS)

EARTH
CONNECTING
BLOCK

40

JUMPERING MDF - SOPHO iS3010
DB-A 9150e-35
Diagram 340

9412

CONNECTING BLOCKS

DISCONNECTING BLOCKS

1

2

3

EARTH CONNECTION

40

EARTH
CONNECTING
BLOCKS

JUMPERING MDF - SOPHO iS3030
DB-A 9150e-35
Diagram 341

9412

PMC-MC

A

TO SLAVE CABINET

A

SLAVE CABINET

PMC-MC

A

FROM MASTER CABINET

INSTALLING THE PMC-PMC CABLE AND THE
MAINS CABLE IN AN EMC CABINET
DB-A 9150e-35
Diagram 350

9209

PMC-MC

B
TO SLAVE CABINET

B

SLAVE CABINET

PMC-MC

B

FROM MASTER CABINET

INSTALLING THE PMC-PMC CABLE
IN A NON-EMC CABINET
DB-A 9150e-35
Diagram 351

9209

FAA
FAB
FAC
FAD
FBA
1a 2a
1b 2b

FBB
FBC
FBD

8a
8b

FCA
FCB
FCC
FCD

PERIPHERAL
CIRCUIT
BOARD

CONNECTOR
POSITION ON
PERIPHERAL CIRCUIT

ALC-A

FBC

FAD
ALC-E
FCA

DLC-C

FCC

DLC-D

FCC

FAD
DLC-U
FCA

FBA

CCT/
Wires

CCT/
Wires

0
a

1
b

a

b

a

b

b

a

not
used

a

b

a

b

b

a

b

b

a

b

b

a

b

8

b

RX0

a

b

a

b

b

a

+

b

a

b

a

b

a

b

a

a

b

a

b

a

b

a

b

a

b

a

RX3

-

+

-

+

-

+

-

+

-

+

-

a

b

a

+

a

b

a

b

a

b

a

b

a

b

b

a

b

a

b

a

a

b

a

-

+

-

+

-

+

-

+

-

+

-

+

-

TX10
+
-

TX11
+
-

b
7

14

b
15

6

b
7

14

TX1

b
15

6

13

b
7

14

5

+

b
6

13

TX0
-

7

b

5

12

+

6
a

13

4

CCT/
Wires

b
5

12

11

-

b

4

3

+

a

12

11

RX2
-

a

CCT/
Wires

5
b

4

3

10

RX1
-

a

a

11

2

9

+

a

b

b

10

1

a

a

a

3

2

a

0

a

CCT/
Wires

4
b

10

9
a

a

2

1
a

b

a

a

b

8
a

b

9

CCT/
Wires

3

a

1

8
a

CCT/
Wires

2
b

0
a

CCT/
Wires

b

b

not
used

TX2

TX3
-

+

-

DLC-I
FBB

RX4
+
-

RX5
+
-

RX6
+
-

not
used

+

TX4

FAB

RX0
+
-

RX1
+
-

RX2
+
-

RX3
+
-

+

TX5

TX0

TX6

TX1

-

not
used

TX2

TX3
-

+

-

DTX-I (7)
FBA

RX4
+

RX5
-

+

RX6
-

+

not
-

TX4

used

+

TX5

used

RX0
+
-

RX1
+
-

RX2
+
-

RX3
+
-

+

FBA

RX4
+
-

RX5
+
-

RX6
+
-

RX7
+
-

+

FBD

RX8
+
-

RX9
+
-

RX10
+
-

RX11
+
-

FCC

DTA

RX12
+
-

RX13
+
-

RX14
+
-

not
used

TX12
+
-

TX13
+
-

TX14
+
-

not
used

FBC

Extension
line

Entry
point
'IN'
a
b

Entry
point
'OUT'
a
b

not
used

not
used

not
used

not
used

not
used

a

b

TX1

not
-

FAB

DTX-I

TX0

TX6

TX4

TX5

TX8
+

TX2

+

+

-

+

TX6

TX9
-

TX3
-

TX7
-

LINE CIRCUIT CONNECTIONS AT MDF BLOCKS
DB-A 9150e-35
Diagram 400
9304

FAA
FAB
FAC
FAD
FBA
FBB

1a 2a
1b 2b

FBC
FBD

8a
8b

FCA
FCB
FCC
FCD

PERIPHERAL
CIRCUIT
BOARD

CONNECTOR
POSITION ON
PERIPHERAL CIRCUIT

ATU
(4 CCTs)

FBC

ATU
(6 CCTs)

FBC

ATU
(8 CCTs)
(8 MCs)
(8 ESUs)

ATU-IL
(4-wire)

FBA

FBB

FBC

FBC
ATU-E&M
(2-wire)
FCA

FAD
ATU-E&M
(4-wire)
FCA

FBC
ATU-PA
FCA

ATU-PSI

ATU-G
(8 CCTs)

FBC
FAD 1)
Emergency Extension
Connections
FCA

1)

CCT/
Wires

CCT/
Wires

0
a

1
b

a

b

a

b

a

b

a

b

a

b

a

EE

E

b

a

EE

E

b

a

EE

E

0
a

b

a

b

a

b

a

EE

E

b

a

EE

E

not
used

5

not
used

not
used

b

a

b

a

b

a

b

a

b

a

EE

E

b

a

EE

b

E

3

4
b

a

ESU0

ESU1

ESU2

ESU3

b

+

+

+

+

b

ESU4
+
-

b

c

3

7

3

3

d
not

EE

M

1
MM

M

d

MM

M

Ext. 1

ALC Ext. 1
b

M

d

MM

M

3

c

MM

M

d

c

MM

M

2

1

not
used

MM
3

2

d
3
MM

not
used

not
used

not
used

1

not
used

not
used

not
used

not
used

0
MM

not
used

M

MM

not
used

not

not

not

not

used

used

used

used

3

4
b

MM
1

0

M

2

c

0

Teleph.
a
b

a

c

used

c

Microph.
a
b

b

d
not

3

2

3

c

used

b

not
used

a

d

-

ESU7
+
-

2

c

0

not
used

b

ESU6
+
-

1
d

M

EE

1

ESU5
+
-

-

not

EE

a

-

used

3

b

b

used

3

not
used

a

-

a

not
b

not
used

b

b

0

b

a

a

not
used

2

ALC Ext. 0

b

not
used

2

Ext. 0

0

not
used

a

2

Contact
a
b

a

3
b

2

1

b

CCT/
Wires

2

To ALC
a
b

a

CCT/
Wires

6

1

0
E

CCT/
Wires

2

1

0
a

a

1

0
E

b

1

0
a

CCT/
Wires

2

1

0
E

a

1

0
a

b

5

0
a

a

1

4
a

CCT/
Wires

2
b

1

0
a

CCT/
Wires

a

5
b

a

6
b

a

7
b

a

b

Two Emergency Extensions or two Emergency ALC Extensions
can be connected to an ATU-G, it is not possible to have both
solutions. During normal operation the Emergency Telephones
cannot be used. In case of two ALC extensions are used as
Emergency Extensions, they also can be used as normal
extensions during normal operation.

ANALOG TRUNK CIRCUIT CONNECTIONS
AT MDF BLOCKS
DB-A 9150e-35
Diagram 401
9209

FAA
FAB
FAC
FAD
FBA
1a 2a
1b 2b

FBB

8a
8b

FBC
FBD
FCA
FCB
FCC
FCD

PERIPHERAL
CIRCUIT
BOARD

CONNECTOR
POSITION ON
PERIPHERAL CIRCUIT

MC-A/C

FCB
(connections to exchange
lines)

a

FCD
(connections to exchange
lines)

a

FCB
(connections to exchange
lines)

a

FCD
(connections to exchange
lines)

a

FBD
(connections to exchange
lines)

a

FCD
(connections to exchange
lines)

a

FBC
(connections to
trunk circuit numbers)

a

FBD
(connections to exchange
lines)

a

FCC
(connections to
trunk circuit numbers)

a

FCD
(connections to exchange
lines)

a

(connected to
ATU with
4 CCTs)

MC-A/C
(connected to
ATU with
6 CCTs)

MC-D/F
(connected to
ATU with
4 CCTs)

MC-D/F
(connected to
ATU with
6 CCTs)

DTU-CA/PR
DTU-PU/PH

FBA
(FBB for DTU-PH)
FBA

CCT/
Wires

CCT/
Wires

0

1
b

a

b

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

b

a

b

b

a

12

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

a

b

a

b

+

b

a

b

a

b

a

b

a

b

a

b

a

a

b

a

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b
9
b
9
b
11
b
11

--

b

--

TX2

TX3

+

-

b
15

10

+

b
7

10

-

b
11

8

TX1

b
9

8

+

b
15

14

TLO
120 Ω

-

a

6

5

-

b

10

5

TX0

a

8

7

TLO
120 Ω

+

a

7

4

-

b

7
b

14

13

4

RX3

a

5

6

+

b

5

6

--

a

7

12

CCT/
Wires

6
b

13

4

15

-

b

4

15

+

a

6

3

RX2
-

a

3

--

RX1
-

a

b

b

CCT/
Wires

5
b

12

11

14

TLI
120 Ω

RX0

a

b

a

3

14

13

TLI
120 Ω

a

b

b

15

2

13

12

a

b

a

3

2

1

12

a

b

b
11

10

1

0

b

CCT/
Wires

4

a

2

9

0

b

14

1

8

a

2

13

0

b
10

1

CCT/
Wires

3

a

9

0

CCT/
Wires

2

a

8

+

CCT/
Wires

-

+

+

-

DTU-BA
FBB

RX5
+
-

RX6
+
-

not
used

FCD

Data in
a
b

not
used

not
used

not
used

FBA

LTU

RX4
+
-

do not
connect

LDC
FCC

1
a

8
a

2
b

a

b

a

9
b

a

TX4
+

Data out
a
b

3
b

a

b

a

10

TX5

not
used

4
b

a

b

a

11

TX6

not
used

5
b

a

b

a

12

-

not
used
not
used

6
b

a

b

a

13

7
b

a

b

a

14

b
15

MC / DTU / LDC CONNECTIONS AT
MDF BLOCKS
DB-A 9150e-35
Diagram 402

b

9209

FAA
FAB
FAC
FAD
FBA
1a 2a
1b 2b

FBB

8a
8b

FBC
FBD
FCA
FCB
FCC
FCD

PERIPHERAL
CIRCUIT
BOARD

CONNECTOR
POSITION ON
PERIPHERAL CIRCUIT

CCT/
Wires

FBB
(connections to
extensions)

MCE-A/C/D/F
(connected to
ATU with
6 CCTs)
Max. 12 CCTs
per MCE board

a

FCB
(connections to
extensions)

a

FBC
(connections to
trunk circuits)

a

a

a

a

FBB
(connections to
extensions)

Max. 16 CCTs
per MCE board

a

FCD
(connections to exchange
lines)

(connected to
ATU with
6 CCTs)

a

FBD
(connections to exchange
lines)

MCE-A/C/D/F

FBD
(connections to exchange
lines)

FCC
(connections to
trunk circuits)

Max. 16 CCTs
per MCE board

a

FBB
(connections to
extensions)

(connected to
ATU with
4 CC Ts)

FCB
(connections to
extensions)

FCD
(connections to exchange
lines)

MCE-A/C/D/F

a

a

FCB
(connections to
extensions)

a

FBD
(connections to exchange
lines)

a

FCD
(connections to exchange
lines)

a

CCT/
Wires

0

CCT/
Wires

1
b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

8

2
b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

9

0

0

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b
15
b
9
b
11
b
9

10

b
11

8

b
9

10

b
11

6

b
7

14

5

b
7

8

13

10

b

b
15

10

5

4

a

8

5

12

b

14

7

4

9

b

a

6

5

4

3

a

7

6

11

b

7
b

14

5

4

3

a

7

6

15

b

13

4

3

a

5

6

CCT/
Wires

6
b

13

12

15

8

a

4

3

CCT/
Wires

5
b

12

15

2

7

a

3

10

1

6

a

2

9

0

b

b

11

14

1

8

a

2

13

0

b

a

3

14

1

12

a

2

13

0

b

CCT/
Wires

4
b

11

14

1

12

a

2

13

0

b

10

1

12

a

2

9

CCT/
Wires

3
b

10

1

8

CCT/
Wires

b
15
b

not

not

b

used

used

b

not
used

not
used

11

MCE CONNECTIONS AT MDF BLOCKS
DB-A 9150e-35
Diagram 403
9209

FAA
FAB
FAC
FAD
FBA
1a 2a
1b 2b

FBB

8a
8b

FBC
FBD
FCA
FCB
FCC
FCD

PERIPHERAL
CIRCUIT
BOARD

CCT/
Wires

FBA
(connection to ALC circuits, via MDF or direct)

a

FBB
(connections to
extensions)

a

FBC
(connections to ATU circuits via MDF or direct)

ESU

CONNECTOR
POSITION ON
PERIPHERAL CIRCUIT

a

FBD
(connections to exchange
lines)

a

FCA
(connection to ALC circuits, via MDF or direct)

a

FCB
(connections to
extensions)

a

FCC
(connections to ATU circuits via MDF or direct)

a

FCD
(connections to exchange
lines)

a

CCT/
Wires

0

CCT/
Wires

1
b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

0

2
b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

1

0

8

b

a

b

a

b

a

b

a

b

a

9

b

a

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

11

b

a

b

a

b

a

a

b

a

b

a

b

a

b

a

b

a

b

a

a

b

a

b

a

b

a

b

a

b

a

b

a

b

a

b
7

14

b
15

14

b
15

14

13

b
7

6

13

b
7

6

13

12

7
b

6

13

12

11

b

5

12

11

a

5

12

CCT/
Wires

6
b

5

4

11

10

a

4

3

CCT/
Wires

5
b

4

3

10

CCT/
Wires

4
b

3

10

9

8

a

10

9

8

b

2

9

8

a

2

1

CCT/
Wires

3
b

2

1

0

CCT/
Wires

b
15

14

b
15

ESU CONNECTIONS AT MDF BLOCKS
DB-A 9150e-35
Diagram 404

b

9209

FAA
FAB
FAC
FAD

FAB
FAC

FBA

FBA

FBB

FBB

FBC
FBD

FBC
FBD

FCA

FCA

FCB
FCC
FCD

FCB
FCC
FCD

PERIPHERAL
CIRCUIT
BOARD

CONNECTOR
POSITION ON
PERIPHERAL CIRCUIT

PMC
(with DOC)

connector pos. FAA

PMC
(with AOC)

FAB
(second oper. position)

FCB (Standard
8 extension lines)
ACC

FAC**
(on PEC position 0 and 1
a TU, type AS01/M50 or
AS01/0B or SS01/0B)

KTLC-8
or
KTLC-A

FBA

(8 CCTs)

FBD

FBA
KTLC-E
(16 CCTs)

FBD
FAB

FCC

8a
8b

CCT/
Wires

CCT/
Wires

CCT/
Wires

CCT/
Wires

CCT/
Wires

CCT/
Wires

CCT/
Wires

CCT/
Wires

0

not
used

not
used

not
used

not
used

not
used

not
used

not
used

a

FAC
(first oper. position)

*

1a 2a
1b 2b

b

Teleph.
Ta Tb

Microph.
Power
Power
Ma Mb -48V gnd -48V gnd

Teleph.

Microph.

Ta

Ma

Tb

Power

not
used

Power

Mb -48V gnd -48V gnd

not

Data in
Data out
Power
DIa DIb DOa DOb -48V gnd
Data in

used

DIa

Data out

Power

DIb DOa DOb -48V gnd

line CCT 0 line CCT 1 line CCT 2 line CCT 3 line CCT 4 line CCT 5 line CCT 6 line CCT 7
a
b
a
b
a
b
a
b
a
b
a
b
a
b
a
b
trunk 0
a
b

trunk 1
a
b

0
a

1
b

a

b

a

b

a

b

a

4
a

a

b

a

b

a

b

a

b

a

a

b

a

b

a

b

a

b

a

13

b

c

b

c

b

c

b

a

b

a

14

c

d

c

d

c

d

c

c

b

c

15

d

c

d

c

d

c

c

d

c

12

c

d

c

d

c

d

c

d

c

13

d
7

10
c

d
3

6

d

d
7

2

9
d

3
d

6

5

8
b

c

1

4

not
used

2
d

5

0

11

emer. tel.*
a
b

1
d

4

7

10
a

c

3

6

trunk 3
a
b

0
b

7

2

b

trunk 2
a
b

3
b

6

9

12
a

b

5

8
a

a

1

4
a

not
used

2
b

5

0
a

emer. tel.*
a
b

d
11

d

c

d

c

14

d
15
d

If the emergency switch on the ACC is active the emergency telephone is connected to trunk circuit 0 for the first PEC and for the
second PEC connected to trunk 2. Trunk 1 and trunk 3 do not have a emergency switch over option. The emergency telephone is
only used for emergency purposes.

** Use the description which is applicable.

PMC, ACC AND KTLC CONNECTIONS AT MDF
BLOCKS
DB-A 9150e-35
Diagram 405
9304

DLC-C / DLC-D ( / LDC) connections
1
0
0

1
0
0

1
0
0

1
0
0

DLC-I connections

1
0
0

DTU-BA connections

1
0
0

1
0
0

FAA

FAA

FAA

FAA

B

B

B

B

C

C

C

D

D

D

FBA

FBA

FBA

FBA

B

B

B

B

C

C

C

D

D

FCA

FCA

FCA

FCA

B

B

B

C

C

D

D

C

*

*

*

*

*

*

*

*

D

To MDF

To MDF

C

*

D

To MDF

*

D

*

*
Clock to PMC

To MDF

B
C
D

D
L
C
D

D
L
C
C

1
0
0
FAA

D
L
C
C

D
L
C
D

L
D
C

1
0
0

DTU-CA/PR
connections

DTU-PU/PH
connections

FAA

C

D
L
C
I

DTU-LTU
connections

D

D
T
U
B
A

1
0
0

1
0
0

FAA

B

B

B

C

C

C

D

Second DTU
If applicable

FBA

D

See
Note1

FBA

B

1

2

C

Second DTU
If applicable

B

FBA
B

C

*
D

D

1

See Note2

C

2

D

D

*
Clock to PMC

FCA
B
C
D

FCA
Clock to PMC

B

D
T
U

Note1 :
Note2 :

If DTU-PU

C
D

Clock to
PMC

FCA

D
T
U

If DTU-PU is used, then the coax front connector
position is FBA, while the rest of the FB.. front
connectors are not used.
If DTU-PH is used, then connector position is FBB.

B
C

To NT1 Multiplexing
Equipment (GND, -48 V).
DTU-PU and DTU-PH
only.

D

D
T
U

DLC / LDC / DTU / LTU CABLING
DB-A 9150e-35
Diagram 420.1

L
T
U
To MDF

9209

1
0
0

1
0
0

FAA

FAA

B

B

C

C

Input 75Ω*

D

D

Output 75Ω*

Input/output 75Ω or 120 Ω

FBA

Input/output 75Ω or 120Ω *

FBA

B

B

C

C

D

D

FCA

Clock output to PMC (2.048 MHz).
D
T
U
C
A
/
P
R

B
C
D

Connector not used

*

Connector not used

*

Connector not used

*

FCA

Clock output to PMC
(2.048 MHz).

B

*
C
D

D
T
U
P
U

DTU CONNECTOR FBA
LTU CONNECTOR A (FCB)
* TLI-120Ω (a)
* TLI-120Ω (b)

1a
1b

5a
5b

* TLO-120Ω (a)
* TLO-120Ω (b)

Shield incoming
Not connected
* TLI-75Ω (a) **

2a
2b
3a

6a
6b
7a

Shield outgoing
Not connected
* TLO-75Ω (a) **

* TLI-75Ω (b) **
Not connected
Ground

3b
4a
4b

7b
8a
8b

* TLO-75Ω (b) **
Not connected
Not connected

Either the coax connectors or
the F122 connector are used
for input and output

GND and -48 V (250 mA)
To NT1 multiplexing equipment.
For connector layout refer to
diagram 420.3.

120Ω CABLE CONNECTORS
1a
1b

5a
5b
6a
6b
7a

TLO-shield

Not connected

2a
2b
3a
3b
4a
4b

7b
8a
8b

Not connected

LTU Alarm signal
LTU Alarm ground

TLI-data
TLI-shield

TLO-data

* TLI = Trunk Line Incoming from the LTU (inward).
TLO = Trunk Line Outgoing to the LTU (outward).
**

=

***

=

These signals are not present on the LTU with the 12 NC
code : 9562 151 1210.
Straps are positioned on DTU-PR only. These straps are
used to connect the cable shields of the incoming and
outgoing cable to ground or to leave the cable shields
floating.

***

75Ω CABLE CONNECTIONS
Not connected

LTU CONNECTOR B (FCD)
MDF → LTU
135Ω

Not connected

1a
1b
2a

5a
5b
6a

2b
3a
3b

6b
7a
7b

4a
4b

8a
8b

LTU → MDF
135Ω

Not connected

Straps are positioned
on the DTU-PR only

*** Strap
Maintenance
Alarm LTU signal
TLI-data
TLI-shield
LTU Alarm signal
LTU Alarm ground

1a
1b
2a

5a
5b
6a

Not connected

2b
3a
3b

6b
7a
7b

Not connected
TLO-data
TLO-shield

4a
4b

8a
8b

Not connected
Service alarm
LTU ground

Strap ***

DTU-CA/PR/PU AND LTU INTERFACE
CONNECTIONS
DB-A 9150e-35
Diagram 420.2

9209

1
0
0
FAA
B
C

Input 75Ω*

D

Output 75Ω*

DTU-PH CONNECTOR FBB
LTU CONNECTOR A (FCB)

FBA

* TLI-120Ω (a)

C

*
D

FCA

Either the coax connectors or the
F122 connector are used for
input and output.

D

* TLO-120Ω (a)

5b
6a
6b
7a

* TLO-120Ω (b)
Shield outgoing
Not connected
* TLO-75Ω (a) **

3b
4a
4b

7b
8a
8b

* TLO-75Ω (b) **
Not connected
Not connected

Clock output to PMC (2.048 MHz).
* TLI = Trunk Line Incoming from the LTU (inward).

B
C

5a

1b
2a
2b
3a

* TLI-75Ω (b) **
Not connected
Ground

Input/output 75Ω or 120 Ω*

B

1a

* TLI-120Ω (b)
Shield incoming
Not connected
* TLI-75Ω (a) **

**

D
T
U
P
H

TLO = Trunk Line Outgoing to the LTU (outward).
= These signals are not present on the LTU with the 12 NC
code : 9562 151 1210.

GND and -48 V (250 mA)
To NT1 multiplexing equipment

DTU-PH CONNECTOR FCD

Ground
-48 V

1a
1b

5a
5b

Ground
-48 V

Ground
-48 V
Ground

2a
2b
3a

6a
6b
7a

Ground
-48 V
Ground

-48 V
Ground
-48 V

3b
4a
4b

7b
8a
8b

LTU CONNECTOR B (FCD)
MDF → LTU
135Ω

-48 V
Ground
-48 V

5a
5b

2a
2b
3a

6a
6b
7a

3b
4a
4b

Not connected

1a
1b

LTU → MDF
135Ω

7b
8a
8b

Not connected

Connector FCD is connected to NT1
multiplexing equipment (-48 V, 250 mA).

120Ω CABLE CONNECTORS

TLI
TLI-shield
Not connected

Ground

1a
1b

5a
5b

2a
2b
3a
3b

6a
6b
7a
7b

4a
4b

8a
8b

75Ω CABLE CONNECTIONS
1a
1b

5a
5b

Not connected

TLI-data
TLI-shield

2a
2b
3a
3b

6a
6b
7a
7b

TLO-data
TLO-shield

Not connected
Ground

4a
4b

8a
8b

Not connected
Not connected

TLO
TLO-shield

Not connected

Not connected

DTU-PH AND LTU INTERFACE
CONNECTIONS
DB-A 9150e-35
Diagram 420.3

9209

ATUs (4CCTs) Connections to MC-A/C
1
0
0

1
0
0

1
0
0

1
0
0

ATUs (6CCTs) Connections to MC-A/C

1
0
0

1
0
0

FAA

C

D

D

FBA

FBA

B

B

C

C

D

1
0
0

B

C

1
0
0

FAA

B

1
0
0

D

FCA

*

FCA

*

B
C

*

*

B
A
T
U

A
T
U

A
T
U

A
T
U

D

4

3

2

M
C
A
/
C

To MDF

1
0
0

1
0
0

1

1
0
0

A
T
U

A
T
U

2

M
C
A
/
C

To MDF

1

D

ATUs (4CCTs) Connections to MC-D/F
1
0
0

C

A
T
U

3

*

*

ATUs (6CCTs) Connections to MC-D/F

1
0
0

1
0
0

FAA

C

D

1
0
0

B

C

1
0
0

FAA

B

1
0
0

D

FBA

FBA

*

B

*
*

B

*

C

C

D

*

D

FCA

*

B
C

*
A
T
U

A
T
U

A
T
U

A
T
U

D

4

3

2

1

M
C
D
/
F

FCA

*

To MDF
B

*
A
T
U

A
T
U

A
T
U

M
C
D
/
F

4

C

To MDF

3

2

1

D

ATU/MC INTERCONNECTIONS
DB-A 9150e-35
Diagram 421

9209

ATUs (4CCTs) Connections to MCE-A/C/D/F
1
0
0

1
0
0

1
0
0

ATUs (6CCTs) Connections to MCE-A/C/D/F, 16 CCTs

1
0
0

1
0
0

1
0
0

FAA

1
0
0

B

C

1
0
0

FAA

B

1
0
0

C

D

D
To
ALC-A (1)
Conn. FBC
or ALC-E
Conn. FAD

FBA

*

To
ALC-A (1)
Conn. FBC
or ALC-E
Conn. FAD

FBA

B

B

C

C

To MDF

To MDF
*

D

D
To
ALC-A (2)
Conn. FBC
or ALC-E
Conn. FCA

FCA
B
C

FCA
B

*
A
T
U

A
T
U

A
T
U

A
T
U

To
ALC-A (2)
Conn. FBC
or ALC-E
Conn. FCA

A
T
U

C

D

A
T
U

A
T
U

M
C
E

4

M
C
E

3

2

1

D

4

3

2

1

ATUs (6CCTs) Connections to MCE-A/C/D/F, 12 CCTs
1
0
0

1
0
0

1
0
0

1
0
0

1
0
0

1
0
0

*

:

These are split cables.

**

:

When using two ALC-A with 8 CCTs each,
then these connections should be made.

***

:

When using one ATU board (6 CCTs), then
the FCA, FCB, FCC and FCD connections
on the MCE are not used.

*

FAA
B

*

C
D

Note1 : If MCE-D , diagram only valid
for 9562 151 6820 upwards.

FBA
**
B
C
D
**
***

FCA

To MDF

B
C
D

A
L
C
E

A
L
C
A

A
L
C
A

A
T
U

A
T
U

1

2

2

M
C
E

1

ATU/MCE INTERCONNECTIONS
DB-A 9150e-35
Diagram 422

9209

PCT
position
1
0
0
FAA
B
C
D
DISCONNECTING BLOCKS MDF
1a 2a
1b 2b

FBA

8a
8b

B
C

a b a b a b a b a b a b a b a b
Trunk Circuit numbers

D

0

1

2

3

4

5

6

7

FCA
B
C
D

A
T
U
G

1a 2a 3a 4a
1b 2b 3b 4b

a b a b a b a b
Two Emergency Extensions or two Emergency ALC Extensions can
be connected to an ATU-G, it is not possible to have both solutions.
During normal operation the Emergency Telephones cannot be used.
In case of two ALC extensions are used as Emergency Extensions,
they also can be used as normal extensions during normal operation.

Ext0

Ext1

ALC0

ALC1

Emergency Extension 0
Emergency Extension 1

ALC (Emergency) Extension 0
ALC (Emergency) Extension 1

To ALC

ATU-G ESU FUNCTIONS
DB-A 9150e-35
Diagram 423

9209

ATUs (4CCTs) Connections to ESU
1
0
0

1
0
0

1
0
0

1
0
0

FAA

1
0
0

*

1
0
0

1
0
0

1
0
0

*

*

*

B
C
D

FBA
Extensions
1 ... 8

**
B
C

Exchange
lines 1 ... 8

D

*

**

To MDF

FCA
Extensions
9 ... 16

B
*
C
A
L
D C
E

A
L
C
A

A
L
C
A

A
T
U

A
T
U

A
T
U

A
T
U

1

2

4

3

2

Exchange
lines 9 ... 16

1

E
S
U

ATUs (6CCTs) Connections to ESU
1
0
0

1
0
0

1
0
0

1
0
0

FAA

1
0
0

*

ATUs ( including 8CCTs, 8 ESUs, 8MCs)
1
0
0

1
0
0

1
0
0

FAA

*

B

lines 1 ... 4

C

D

Exchange

B

C

1
0
0

D

FBA

ESU
Extensions
lines 1 ... 4

FBA
Extensions
1 ... 6

**
B

B

C

To
MDF

C
Exchange
lines 1 ... 6

D

To

D

MDF

**
FCA

Extensions
8 ... 16

FCA
Extensions
9 ... 14

B
C

Exchange
lines 5 ... 8

B
C

A
L
D C
E

A
L
C
A

A
L
C
A

A
T
U

A
T
U

1

2

2

Exchange
lines 9 ... 14

1

*

:

These are split cables.

**

:

When using two ALC-A with 8 CCTs each,
then these connections should be made.

E
S
U

A
L
D C
E

A
L
C
A

A
T ESU
U Extensions
lines 5 ... 8

ESU/ATU/ALC INTERCONNECTIONS
DB-A 9150e-35
Diagram 424

9209

PCT Position
1
0
0

1
0
0
FAA
B
C
D

FBA
B
C
D

Flat cable
34 pol

FCA
B
I
P
H
A

I
P
H
B

C
D

IPH-A - IPH-B INTERCONNECTIONS
DB-A 9150e-35
Diagram 425

9209

FAA

1
0
0

B
C

14

1

D

*

FBA
B

Modem 2

C

Modem 3

D

FCA

25 13

*

B

Modem 1 Modem 2 Modem 3

*

C
D

MODEM 0

Modem 1

*
M
L
U

*

a b c d a b c d a b c d a b c d

* Wiring according

to the table below

WIRE
1a
1b

PIN
22
25

CIRCUIT
125
142

2a
2b
3a

3
18
5

3b
4a
4b

Circuit number

0

1

2

3

CIRCUIT NAME
Calling indicator (not used)
Test indicator

ABBREVIATION
RI
TI

104
141
106

Received data
Local loopback
Clear to send

RD
CTS

15
20
17

113
108
115

Transmitter signal element timing (DTE)
Connect data set to line / data terminal ready
Receiver signal element timing

TC
DTR
RC

5a
5b
6a

2
7
4

103
102
105

Transmitter data
Ground
Request to send

TD
SG
RTS

6b
7a
7b

21
6
23

140
107
111

Loopback / maintenance test
Data set ready
Data signalling rate selector

SQD
DSR
DRS

8a
8b

8
11

109
126

Data carrier detect
Select transmit frequency

DCD
STF

MLU - MODEM - MDF CABLING
DB-A 9150e-35
Diagram 430

9209

FAA

1
0
0

B
C

14

1

D

*

FBA

MODEM 0

Modem 1

B

Modem 2

C

Modem 3

D

25 13

FCA
B
C
D

M
L
U

1a 5a

1a 5a

a b c d a b c d a b c d a b c d

* Wiring according

Circuit number

0

1

2

3

to the table below

WIRE
2a

PIN
3

SIGNAL
104

2b
3a
3b

18
5
15

141
106
113

4a
4b
5a

20
17
2

108
115
103

5b
6a
6b

7
4
21

102
105
140

7a
7b
8a

6
23
8

107
111
109

Modem 1 Modem 2 Modem 3

MLU - MODEM FOR MODEM POOL TO MDF
DB-A 9150e-35
Diagram 431
9209

PSU-F connections to ATU-LB
1
0
0
FAA

1
0
0

*

1
0
0

*

1
0
0

1
0
0

*

1
0
0
FAA

*

B

*

1
0
0

1
0
0

*

*

C

D

*

1
0
0

B

C

1
0
0

D

FBA

*
*
*

FBA

*
B

*
B

*

C

*

*

*

*

*

C

*

D

*

*

*

FCA

B

*

D

FCA

*

B

C

*

*

*

A
T
U

A
T
U

A
T
U

A
T
U

(X)

(X)

2

C
P
S
U
F

1

D

A
T
U

A
T
U

A
T
U

A
T
U

(X)

D

(X)

2

P
S
U
F

1
1
9
0
FAA
B
C

ATU-LB12

PSU-F
D

FBA
FCC / FCD

FAA ÷ FBD

B

CHECK CORRECT
POSITION
HIGH SIDE PIN

C
D

MDF Disconnecting blocks
1a
1b

RED
BLUE

2a
2b

FCA

YELLOW
GREEN

1a 2a
1b 2b

8a
8b

*
Alarm

P
S
U
F

B
C
D

PSU-F (- ATU-LB) INTERCONNECTIONS
DB-A 9150e-35
Diagram 436
9209

METAL EARTH
STRIP

OVERVOLTAGE ARRESTOR AND CARTRIDGE
(SOFYCOM)
DB-A 9150e-35
Diagram 440

9412

4.25mm
6.6mm

*

COAXIAL CONNECTOR FOR MDF
DB-A 9150e-35
Diagram 450

9412

NOTE: Cut-off the wires that are not used.

1a 2a
1b 2b

8a
8b

1a 2a
1b 2b

8a
8b

101
301

308

101

108

102
103
104

1a
1b
2a

105
106
107
108
301
302
303
304
305
306
307
308

8b

To analogue
operator position

OPERATOR CONNECTION BOX
DB-A 9150e-35
Diagram 460

9209

Sign up to vote on this title
UsefulNot useful