1KHW002479 FOX61x LEDA1

ABB Power Systems
FOX61x
LEDA1
User Manual
User Manual FOX61x
LEDA1
Release History: Release 1: December 2012
Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine scannable form
is not permitted, either in whole or in part. The contents of the manual may not be disclosed
by the recipient to any third party, without the prior written agreement of ABB.
An exception is the preparation ofLEDA1 a backup copy of the software for your own use. For
devices with embedded software, the end-user license agreement on the enclosed CD
applies.
This document may not be used for any purposes except those specifically authorised by
contract or otherwise in writing by ABB.
Disclaimer: ABB has taken reasonable care in compiling this document, however ABB accepts no liability
whatsoever for any error or omission in the information contained herein and gives no other
warranty or undertaking as to its accuracy.
ABB can accept no responsibility for damages, resulting from the use of the network
components or the associated operating software. In addition, we refer to the conditions of
use specified in the license contract.
ABB reserves the right to amend this document at any time without prior notice.
Blank pages: Any blank page present is to accommodate double-sided printing.
Document No.: 1KHW002479
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © December 2012 by ABB Switzerland Ltd
Table of Content
1 Preface 11
1.1 Precautions and safety 11
1.2 Symbols and notations 11
1.3 Interfaces and circuit categories 11
1.4 Document history 12
2 Introduction 13
2.1 General 13
2.2 Unit view 14
3 Functions and specifications 15

3.1 Feature licences 15
3.2 E&M interface 15
3.3 Conference 17
3.4 General 18
4 Installation 21
4.1 Prerequisites 21
4.2 Slots and deployment scenarios for the LEDA1 unit 22
4.3 Jumpers 23
4.4 Overvoltage protection 23
4.5 Compatibility 23
4.5.1 FOX61x units 23
4.5.1.1 LESU1 23
4.5.2 FOX51x units 23
4.5.2.1 NEMSG, NEMCA, NEMGE 23
4.5.3 Previous ESW revisions 24
4.6 Connections and cables 24
4.6.1 Front connector of the LEDA1 unit 24
4.6.2 Cable 32 pairs, DIN to open end 25
4.6.3 Fixing the cables to the cable tray 25
5 Functional Description 27
5.1 Network applications 27
5.1.1 Point-to-point (P2P) 27
5.1.2 Point-to-multipoint (P2MP) 28
5.1.3 Multipoint-to-multipoint (MP2MP) 30
5.2 Conferencing 32
5.2.1 Local conferences 32
5.2.2 Conferences in the P2MP application 33
5.2.3 Conferences in the MP2MP application 33
LEDA1LEDA1 3
5.3 Voice 34
5.3.1 E&M voice interface types 34
5.3.2 Line echo cancellation 34
5.3.3 E&M interface voice transport 34
5.3.4 Conference voice transport 36
5.4 Signalling 40
5.4.1 E&M signalling interface states and CAS bits 40
5.4.2 E&M signalling interface types 41
5.4.2.1 E&M type I 41
5.4.2.2 E&M type II 42
5.4.2.3 E&M type III 44
5.4.2.4 E&M type IV 44
5.4.2.5 E&M type V 46
5.4.3 E&M interface signalling transport 47
5.4.4 E&M interface signalling modes of operation 48
5.4.5 Conference signalling transport 50
5.5 Conference cross connections 54
5.5.1 Unprotected network connections 54
5.6 Protection 56
5.6.1 Subnetwork connection protection and linear trail protection 56
5.6.1.1 Protection features 56
5.6.1.2 Protection configuration 57
5.6.2 Equipment protection (EQP) 57
5.6.2.1 EQP features 57
5.6.2.2 EQP prerequisites 58
5.6.2.3 EQP configuration 58
5.6.2.4 EQP status 59
6 Commissioning 61
6.1 Commissioning of a user port 61
6.1.1 Prerequisites 61
6.1.1.1 CESM1 unit 61
6.1.1.2 LEDA1 unit 61
6.1.1.3 TDM transport unit 62
6.1.1.4 FOXCST 62
6.1.1.5 PETS 62
6.1.2 Configuration of a user port 62
6.2 Commissioning of a conference 64
6.2.1 Prerequisites 64
6.2.1.1 CESM1 unit 64
6.2.1.2 LEDA1 unit 64
6.2.1.3 TDM transport unit 65
6.2.1.4 FOXCST 65
6.2.1.5 PETS 65
6.2.2 Configuration of a conference 65
6.3 E&M signalling range considerations 69
6.3.1 Trunk circuit to LEDA1 69
6.3.2 LEDA1 to trunk circuit 70
4 LEDA1LEDA1
7 Operation 73
7.1 Unit optical indicators 73
7.2 Loops 75
7.3 Line states 76
7.4 Maintenance 78
7.4.1 Inventory data 78
7.4.2 Unit ESW download 78
7.4.3 ESW upgrade with EQP 78
8 FOXCST reference 81
8.1 Introduction 81
8.2 AP: / unit-x: LEDA1 83
8.2.1 AP: / unit-x, Overview 83
8.2.2 AP: / unit-x, Main 83
8.2.3 AP: / unit-x, Configuration 83
8.2.3.1 AP: / unit-x, Configuration - Conferencing 83
8.2.3.2 AP: / unit-x, Configuration - EQP 84
8.2.4 AP: / unit-x, Fault Management 85
8.2.5 AP: / unit-x, Status 87
8.2.5.1 AP: / unit-x, Status - EQP 87
8.3 AP: / unit-x / conf-z 89
8.3.1 AP: / unit-x / conf-z, Overview 89
8.3.2 AP: / unit-x / conf-z, Main 89
8.3.2.1 AP: / unit-x / conf-z, Main - General 89
8.3.3 AP: / unit-x / conf-z, Configuration 89
8.3.3.1 AP: / unit-x / conf-z, Configuration - General 89
8.4 AP: / unit-x / conf-z / part-a 90
8.4.1 AP: / unit-x / conf-z / part-a, Overview 90
8.4.2 AP: / unit-x / conf-z / part-a, Main 90
8.4.2.1 AP: / unit-x / conf-z / part-a, Main - General 90
8.4.2.2 AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status 91
8.4.3 P: / unit-x / conf-z / part-a, Configuration 91
8.4.3.1 AP: / unit-x / conf-z / part-a, Configuration - General 91
8.4.3.2 AP: / unit-x / conf-z / part-a, Configuration - CTP 93
8.4.4 AP: / unit-x / conf-z / part-a, Fault Management 94
8.4.5 AP: / unit-x / conf-z / part-a, Performance Management 95
8.4.5.1 AP: / unit-x / conf-z / part-a, Performance Management - Protection 95
8.4.6 AP: / unit-x / conf-z / part-a, Status 96
8.4.6.1 AP: / unit-x / conf-z / part-a, Status - General 96
8.4.6.2 AP: / unit-x / conf-z / part-a, Status - Maintenance 96
8.4.6.3 AP: / unit-x / conf-z / part-a, Status - CTP 97
8.5 AP: / unit-x / port-y 99
8.5.1 AP: / unit-x / port-y, Overview 99
8.5.2 AP: / unit-x / port-y, Main 99
8.5.2.1 AP: / unit-x / port-y, Main - General 99
8.5.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status 99
8.5.3 AP: / unit-x / port-y, Configuration 100
8.5.3.1 AP: / unit-x / port-y, Configuration - General 100
LEDA1LEDA1 5
8.5.3.2 AP: / unit-x / port-y, Configuration - CTP 101
8.5.4 AP: / unit-x / port-y, Fault Management 102
8.5.5 AP: / unit-x / port-y, Performance Management 103
8.5.5.1 AP: / unit-x / port-y, Performance Management - Protection 104
8.5.6 AP: / unit-x / port-y, Status 104
8.5.6.1 AP: / unit-x / port-y, Status - General 104
8.5.6.2 AP: / unit-x / port-y, Status - Maintenance 105
8.5.6.3 AP: / unit-x / port-y, Status - CTP 106
9 Annex 109
9.1 Associated documents 109
6 LEDA1LEDA1
Figures
Figure 1: Terminal equipment connected in a star network, with conference 13

Figure 2: LEDA1 unit view 14
Figure 3: FOX615 subrack with 19 LEDA1 units and 1 LEDE1 unit 22
Figure 4: FOX612 subrack with 6 LEDA1 units and 1 LEDE1 unit 22
Figure 5: Pin-out of the LEDA1 front connector, front view 24
Figure 6: Side view of the cable tray and the cable in FOX615 25
Figure 7: Top view of the cable tray and the cable in FOX612 26
Figure 8: Point-to-point application with LEDA1 27
Figure 9: Point-to-multipoint linear application with LEDA1 28
Figure 10: Point-to-multipoint star application with LEDA1 29
Figure 11: Multipoint-to-multipoint linear application with LEDA1 30
Figure 12: Multipoint-to-multipoint star application with LEDA1 31
Figure 13: Local conference on LEDA1 32
Figure 14: Conference in the P2MP application 33
Figure 15: Conference in the MP2MP application 33
Figure 16: LEDA1 voice interface 34
Figure 17: Level configuration on input and output directions 35
Figure 18: E&M interface voice transport 35
Figure 19: Test signal sequence 36
Figure 20: Conference voice transport, MP2MP 37
Figure 21: Conference voice transport, P2MP 38
Figure 22: Test signal sequence 39
Figure 23: LEDA1 signalling interface 40
Figure 24: E&M signalling type I, and implementation with LEDA1 42
Figure 25: E&M signalling type II, and implementation with LEDA1 43
Figure 26: E&M signalling type III, and implementation with LEDA1 44
Figure 27: E&M signalling type IV, and implementation with LEDA1 45
Figure 28: E&M signalling type V, and implementation with LEDA1 46
Figure 29: E&M interface signalling transport 47
Figure 30: Incoming and outgoing lines 49
Figure 31: Outgoing signalling timing 49
Figure 32: Incoming signalling timing 50
Figure 33: Conference signalling transport, MP2MP 51
Figure 34: Conference signalling transport, P2MP 52
Figure 35: NE types in point-to-multipoint and multipoint-to-multipoint applications 54
Figure 36: 1+1 protection 56
Figure 37: M signalling with LEDA1 69
Figure 38: M signalling, closed contact 69
Figure 39: M signalling, open contact 70
Figure 40: E signalling with LEDA1 70
Figure 41: E signalling, closed contact 70
Figure 42: Fault indication LEDs on the LEDA1 unit 73
Figure 43: Diagnostic loops on the LEDA1 unit 75
Figure 44: MOM (managed object model) of the LEDA1 unit 81
LEDA1LEDA1 7
8 LEDA1LEDA1
Tables
Table 1: Electrical interfaces and circuit categories 11

Table 2: Document history 12
Table 3: E&M interface functions and specifications 15
Table 4: Conference functions and specifications 17
Table 5: General functions and specifications 18
Table 6: E&M signalling types 41
Table 7: LED signalling on LEDA1 74
Table 8: Maintenance function signal replacement 77
Table 9: Managed objects (MOs) for LEDA1 82
Table 10: AP: / unit-x, Configuration - Conferencing 83
Table 11: AP: / unit-x, Configuration - EQP 85
Table 12: AP: / unit-x, Fault Management 85
Table 13: AP: / unit-x, Status - EQP 87
Table 14: AP: / unit-x / conf-z, Configuration - General 89
Table 15: AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status 91
Table 16: AP: / unit-x / conf-z / part-a, Configuration - General 91
Table 17: AP: / unit-x / conf-z / part-a, Configuration - CTP 93
Table 18: AP: / unit-x / conf-z / part-a, Fault Management 94
Table 19: PM counter interval availability 95
Table 20: PM group: Protection 95
Table 21: AP: / unit-x / conf-z / part-a, Status - General 96
Table 22: AP: / unit-x / conf-z / part-a, Status - Maintenance 96
Table 23: AP: / unit-x / conf-z / part-a, Status - CTP 97
Table 24: AP: / unit-x / port-y, Main - Admin And Oper Status 99
Table 25: AP: / unit-x / port-y, Configuration - General 100
Table 26: AP: / unit-x / port-y, Configuration - CTP 101
Table 27: AP: / unit-x / port-y, Fault Management 103
Table 28: PM counter interval availability 103
Table 29: PM group: Protection 104
Table 30: AP: / unit-x / port-y, Status - General 104
Table 31: AP: / unit-x / port-y, Status - Maintenance 105
Table 32: AP: / unit-x / port-y, Status - CTP 106
LEDA1LEDA1 9
10 LEDA1LEDA1
PREFACE
1 Preface
1.1 Precautions and safety
Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety
requirements as defined in EN 60950 (Safety of Information Technology
Equipment).
Please refer to the following document:
"1KHW002497 FOX61x Precautions and Safety".
1.2 Symbols and notations
This User Manual uses the following symbols:
NOTICE Non-observance could result in equipment damage.

Failing to comply with this may result in physical damage.
→ Possible actions are given.
Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
Please note:
Shows significant information.
1.3 Interfaces and circuit categories
Table 1: Electrical interfaces and circuit categories

LEDA1 interface Circuit category Max. rating
according to EN Voltage Current
60950-1
Local power supply TNV2 < 72 VDC < 0.1 A
E&M voice interface TNV1 < 1.1 VRMS < 10 mA
E&M signalling interface TNV3 < 75 VDC < 135 mA
FOX61xLEDA1 11
PREFACE
1.4 Document history
Table 2: Document history

Date FOX61x Changes since previous version
Release
December 2012 R1 First release of the LEDA1 unit for FOX61x.
12 FOX61xLEDA1
INTRODUCTION
2 Introduction
This section presents a general introduction to the LEDA1 unit.
The section is closed with a unit view in section "Installation" (page 21).
2.1 General
This document describes the architecture and functions of the LEDA1 unit
and shows, how this unit is commissioned and operated as part of the
FOX61x.
The LEDA1 unit is a 1-slot wide service unit of FOX61x. As a FOX61x PDH
unit it provides PBUS access.
The unit supports the following interfaces:
− 8 analogue voice interfaces with a telephony bandwidth of 300 Hz to
3.4 kHz, configurable to 2-wire or 4-wire access mode,
− 16 E&M signalling interfaces, where each voice channel offers 2 E&M
signalling channels.
The LEDA1 unit is designed for two main applications:
− Inter-exchange connections, supporting E&M interface types I to V.
− Terminal equipment connections, e.g. for party line subscriber sets or
modems for data over voice transmission.
Beside the voice access LEDA1 offers the possibility to establish voice con-
ferences with participants from the LEDA1 unit or any voice circuit available
in FOX61x.
FOX61x FOX61x
LEDA1 TDM E&M

LEDA1
Network
Voice
Confer-
FOX61x
ence
E&M TDM LEDA1
E&M
Network
P12 transport unit
Figure 1: Terminal equipment connected in a star network, with confer-

ence
LEDA1 has an access capacity of 4 x 2 Mbit/s towards the FOX61x internal

cross connection backplane, PBUS, allowing access of the eight voice user
ports and of up to 10 voice conferences with up to 32 participants in total.
The following network features will help to enhance the systems availability:
• Performance monitoring
• 1+1 end to end linear trail protection
FOX61xLEDA1 13
INTRODUCTION
A more economical use of the network resources can be achieved by the

features like:
• Support of point-to-multipoint linear networks (P2MP)
• Support of multipoint-to-multipoint linear networks (MP2MP)
LEDA1 is connected to a TDM transport unit as e.g. a LEDE1 unit via the
PBUS in the backplane of FOX61x.
2.2 Unit view
Figure 2: LEDA1 unit view
Figure 2 shows the LEDA1 unit hardware. On the front plate are two LEDs
for the unit- and traffic failure indication. The connector for 8 E&M interfaces
is based on the standard DIN 41 612.
14 FOX61xLEDA1
FUNCTIONS AND SPECIFICATIONS
3 Functions and specifications

The LEDA1 unit provides the following functions and conforms to the corre-
sponding standards and recommendations (conformance to applicable parts
of the standards).
3.1 Feature licences
This unit is not subject to feature licences.
3.2 E&M interface
NOTICE Overvoltage. Risk of equipment damage!

Please note that external primary protection with gas discharge tubes is
mandatory.
Table 3: E&M interface functions and specifications

Feature Rating or standard Release
Analogue voice interface ITU-T G.711, 11/1988 r1a
Pulse code modulation (PCM) of voice frequencies:
A-law
Type of voice interface 2-wire r1a
4-wire
Number of voice interfaces 8 r1a
Performance characteristics ITU-T G.712, except specifications below r1a
Impedance in the voice band r1a
- 2-wire input/output 600 Ω, balanced and floating
- 4-wire input
- 4-wire output
Impedance in the voice band, unit in unconfigured or r1a
reset state
- 2-wire input/output 600 Ω, balanced and floating
- 4-wire input
- 4-wire output
Impedance in the voice band, unit in unpowered state not controlled r1a
Isolation (input and output) r1a
- Maximum DC voltage 100 V
- Minimum isolation voltage 1500 VRMS
Discrimination against out-of-band signals reference frequency 1014 Hz, test level -10 dBm0, r1a
measurement A → D
- 150 Hz 3 dB typical
- 50 Hz ≥ 36 dB
FOX61xLEDA1 15
Table 3: E&M interface functions and specifications (continued)

Absolute envelope delay between the AF interface and r1a
PBUS
- Transmit direction (interface → PBUS) 400 to 835 μs
- Receive direction (PBUS → interface) 290 to 725 μs
Maximum line length r1a
- Attenuation at 800 Hz ≤ 0.5 dB
- Line length ≤ 260 m with 0.4 mm wire
Signalling interfaces E&M Swiss PTT 692.01/S, 05/1989 r1a

Basic Requirements for the telephone exchange
technology, Volume I, book I.S, version 1/3: Inter-
faces between exchange and transmission equip-
ment
Swiss PTT 692.05/D.19, 06/1992 r1a
technology, Volume V, book V.D.19, version 1.0:
Universal 8-wire E&M interface
Swiss PTT 692.07/E, 07/1978 r1a
technology, Volume VII, section E, version 1/2:
Pulse signalling
Signalling interface types type I to type V r1a
Number of signalling interfaces 8x2 r1a
(2 interfaces per voice channel)
Meaning of signalling bits r1a
- Input M connected to ground a = 0 (default, can be inverted)
- Input M connected to battery or open a = 1 (default, can be inverted)
- Input M’ connected to ground b = 0 (default, can be inverted)
- Input M’ connected to battery or open b = 1 (default, can be inverted)
- Bit a = 0
output E connected to ground
- Bit a = 1
output E open
- Bit b = 0
- Bit b = 1 output E’ connected to ground
output E’ open
Unused signalling bits r1a
- Bit c =0
- Bit d =1
Pulse distortions r1a
- M/M’ → E/E’ ≤ 3 ms
Delay r1a
- M/M’ → PBUS ≤ 250 μs
- PBUS → E/E’ ≤ 250 μs
Propagation time differences between the two signalling r1a
channels
- M/M’ → PBUS ≤ ±125 μs
- PBUS → E/E’ ≤ ±125 μs
E and E’ outputs, contact open r1a
- Maximum permanent voltage -75 V
- Maximum leakage current at -72 V -20 μA
16 FOX61xLEDA1
Table 3: E&M interface functions and specifications (continued)

E and E’ outputs, contact closed r1a
- Maximum constant current -135 mA
- Maximum voltage drop for 135 mA 3V
- Current limiting -0.4 A typical
E and E’ outputs r1a
- signal reference mechanical ground
- CAS disabled contact open
- Unit in unconfigured, reset or unpowered state contact open
M and M’ inputs specification r1a
- Reverse voltage identical to -UBAT
- Short-circuit current -UBAT / 40 kΩ
M and M’ inputs specification, switching thresholds r1a
- Voltage at M/M’ -5 V to +75 V M/M’ connected to ground
- Voltage at M/M’ -24 V to -UBAT M/M’ connected to battery or open
M and M’ inputs specification, unit in unconfigured, r1a
reset or unpowered state
- Impedance > 50 kΩ to -UBAT
- Voltage level -UBAT
3.3 Conference
Table 4: Conference functions and specifications

Conferences Linear addition of the voice signals r1a
Wired-AND addition of the CAS signalling signals
Conference type Multipoint-to-multipoint r1a
Point-to-multipoint
Maximum number of conferences 10 r1a
Maximum number of participants per conference 17 r1a
Maximum number of participants per unit 32 r1a
FOX61xLEDA1 17
3.4 General
Table 5: General functions and specifications

Front connector DIN 41612 r1a
2 x 32 pins, rows a and c
No hardware settable options on the unit All unit parameters are software settable with the r1a
Element Manager
Hot swapping You can replace a LEDA1 unit without interfering r1a
with any other units. No actions on powering, con-
figuration or commissioning need to be taken if you
remove/replace a LEDA1 unit
PBUS access 4 x P12 r1a

Cross connections Flexible cross connections to any other FOX61x r1a
TDM unit on the P0_nc traffic layer
Protection
- Equipment protection 1:1 equipment protection r1a
- Traffic protection 1+1 linear trail protection (LTP) r1a
1+1 subnetwork connection protection with inherent
monitoring (SNC/I)
Performance monitoring Protection switchover events (per user port and r1a
conference participant)
Alarm reporting ITU-T X.733 (1992) r1a
Information technology – open systems intercon-
nection – systems management: Alarm reporting
function
Maintenance
- Test signal insertion Per user port and conference participant r1a
- Out of service Per user port and conference participant r1a
- Loops Voice and signalling front -to-front loop r1a
Voice and signalling back-to-back loop
Power consumption r1a

- Power supply range VBAT refer to "1KHW002460 FOX61x Product Features
and Characteristics"
- Maximum current consumption, IVBAT 87 mA
VBAT = -48 V
- Maximum total power requirement from battery, PTOT 4.2 W
VBAT = nominal voltage
Mechanical parameters r1a

- Construction practice 19 inch
- Height of unit (1 HU = 44.45 mm) 6 HU
- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot)
- Size of the PCB (H x D) 233 mm x 220 mm
18 FOX61xLEDA1
Table 5: General functions and specifications (continued)

- Weight 510 grams
- RoHS Directive 2002/95/EC of the European Parliament
and of the Council of 27.1.2003 on the Restriction
of the use of certain hazardous substances in elec-
trical and electronic equipment
- WEEE Directive 2002/96/EC of the European Parliament
and of the Council of 27.1.2003 on waste electrical
and electronic equipment
Reliability r1a
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 61 years
Emission refer to "1KHW002460 FOX61x Product Features r1a

CENELEC EN 50121-4, 07/2006 r1a
Immunity refer to "1KHW002460 FOX61x Product Features r1a
CENELEC EN 50121-4, 07/2006 r1a
Safety refer to "1KHW002460 FOX61x Product Features r1a
CENELEC EN 50124-1, 03/2001 r1a
Ambient conditions refer to "1KHW002460 FOX61x Product Features r1a
ETSI EN 300 019-1-8 V2.1.4, 04/2003 r1a
Class 8.1 and class Special (3M5)
FOX61xLEDA1 19
20 FOX61xLEDA1
INSTALLATION
4 Installation
This chapter presents the prerequisites for the installation of the LEDA1 unit
in section "Prerequisites" (page 21).
The section "Slots and deployment scenarios for the LEDA1 unit" (page 22)
shows the available slots for the unit and some application examples.
The following sections give information about the usage of jumpers and
external protection circuits.
The section "Compatibility" (page 23) handles the compatibility of the LEDA1
unit with other FOX61x units, FOX units and with previous ESW revisions,
while section "Connections and cables" (page 24) handles any external con-
nections and cables.
4.1 Prerequisites
Before installing a LEDA1 unit take care to follow the safety advice as listed
in "1KHW002497 FOX61x Precautions and Safety".
Valid combinations of hardware (HW) and embedded software (ESW) ver-
sions are given in "1KHW002459 FOX61x Release Notes".
For the installation of FOX61x HW, "1KHW002461 FOX615 Installation" or
"1KHW002462 FOX612 Installation".
FOX61xLEDA1 21
INSTALLATION
4.2 Slots and deployment scenarios for the LEDA1 unit
The LEDA1 unit uses one slot in the FOX61x subrack.

In a FOX61x, the LEDA1 unit can be operated in any of the following slots:
• FOX615: 1 … 10, 12 … 21.
• FOX612: 7 … 10, 12 … 14.
Slot 11 is reserved for the working CESM1 unit.
In maximum 20 LEDA1 units (160 subscribers without network connection)
can be operated in a FOX615.
FOX615
Slot Slot Slot
1 11 21
L L L L L L L L L L CL L L L L L L L L L
E E E E E E E E E EE E E E E E TDM
E E E E E
D D D D D D D D D D SD D D D D D D D D D Network
A A A A A A A A A A MA A A A A A A A A E
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
6 x 2 Mbit/s
Figure 3: FOX615 subrack with 19 LEDA1 units and 1 LEDE1 unit
The example above shows a FOX615 subrack equipped with 19 LEDA1

units, i.e. 152 user ports, which can be transported over 6 x 2 Mbit/s links
over the TDM network.
FOX612
Slot Slot Slot
7 11 14
L L L L CL L L TDM
E E E E EE E E Network
D D D D SD D D
A A A A MA A E
1 1 1 1 1 1 1 1
2 x 2 Mbit/s
Figure 4: FOX612 subrack with 6 LEDA1 units and 1 LEDE1 unit
The example above shows a FOX612 subrack equipped with 6 LEDA1 units,
i.e. 48 user ports, which can be transported over 2 x 2 Mbit/s links over the
TDM network.
22 FOX61xLEDA1
INSTALLATION
4.3 Jumpers
There are no jumpers or any other kind of hardware settable items on the
LEDA1 unit.
4.4 Overvoltage protection
External primary protection (230 V gas discharge tubes) is mandatory for

each subscriber line. These protection elements are normally plugged onto
the MDF.
4.5 Compatibility
4.5.1 FOX61x units

The deployment of a LEDA1 unit in FOX61x is compatible with any other
FOX61x unit.
4.5.1.1 LESU1
The analogue voice interfaces of the LEDA1 unit are interoperable with the
analog voice interfaces of the LESU1 units.
The CTPs of the LEDA1 unit are interoperable regarding end-to-end connec-
tion protection (LTP) with the CTPs of the LESU1 and units.
The LEDA1 unit is able to provide voice conferences with the subscrib-
ers connected to the LESU1 and units.
4.5.2 FOX51x units

4.5.2.1 NEMSG, NEMCA, NEMGE
The analogue voice interfaces of the LEDA1 unit are interoperable with the
analog voice interfaces of the NEMSG, NEMCA and NEMGE units.
The E&M signalling interfaces of the LEDA1 unit are interoperable with the
E&M signalling interfaces of the NEMSG, NEMCA and NEMGE units.
The CTPs of the LEDA1 unit are interoperable regarding end-to-end connec-
tion protection (LTP) with the CTPs of the NEMSG, NEMCA and NEMGE
units.
The LEDA1 unit is able to build distributed voice conferences with the
subscribers connected to the NEMSG units, using the conference capability
of the NEMSG unit.
FOX61xLEDA1 23
INSTALLATION
4.5.3 Previous ESW revisions

The LEDA1 unit with ESW release is the first release for the FOX61x.
4.6 Connections and cables
4.6.1 Front connector of the LEDA1 unit

The front connector of the LEDA1 unit has 64 pins (2x32, row a and row c
are used). This corresponds to 8 interfaces, each with 8 lines. Every inter-
face consists of balanced voice lines (2-wire or 4-wire) and 4 lines for signal-
ling.
A ground wire is not provided. To ensure correct functioning of the signalling,
a common earth return from the exchange to the LEDA1 unit is required.
This connection is established via the subrack ground. The potential differ-
ence between the exchange ground and the FOX61x ground must be less
than 4 V.
2-wire 4-wire a b c Connector positions
on the unit
b1 32 E’
Voice port 8 a1 31 M’ Signalling port 8
b2 30 E
a2 29 M
b1 28 E’
LEDA1
a1 27 M’
Voice port 7 Signalling port 7
b2 26 E
a2 25 M
b1 24 E’
a1 23 M’
b2 22 E 32
a2 21 M
b1 20 E’
Voice port 5 a1 19 M’ Signalling port 5

b2 18 E
a2 17 M
b1 16 E’
a1 M’
1
Voice port 4 15 Signalling port 4
b2 14 E
a2 13 M
b1 E’
Front Backplane
12
a1 11 M’
Connector Connectors
b2 10 E
a2 9 M
b1 8 E’
a1 7 M’
b2 6 E
a2 5 M
b1 4 E’
a1 3 M’
b2 2 E
a2 1 M
Figure 5: Pin-out of the LEDA1 front connector, front view
24 FOX61xLEDA1
INSTALLATION
4.6.2 Cable 32 pairs, DIN to open end

An open ended or unterminated cable with 32 pairs is used to connect the 8
interfaces of the LEDA1 unit with the 2-wire and 4-wire voice interfaces and
the E&M and E’&M’ signalling interfaces to the MDF. The MDF end of the
cable is open ended.
The length of the cable can be specified (minimum length 3 m).
Latching clips must be used to secure the cable to the LEDA1 front connec-
tor.
Please note:
The specified cables are the same cables as used for the FOX51x unit
NEMSG.
Please note:
The cable route on the cable tray should follow approximately the projection
of the unit slot on the cable tray.
4.6.3 Fixing the cables to the cable tray

When operating the LEDA1 unit in a FOX615, the cable must be attached to
the cable tray as shown in the Figure 6.
Figure 6: Side view of the cable tray and the cable in FOX615
When operating the LEDA1 unit in a FOX612, the cable must be attached to
the cable tray as shown in the Figure 7.
FOX61xLEDA1 25
INSTALLATION
Figure 7: Top view of the cable tray and the cable in FOX612
26 FOX61xLEDA1
FUNCTIONAL DESCRIPTION
5 Functional Description
This chapter gives the detailed functional description of the LEDA1 unit in
the FOX61x subrack:
• Network applications with the LEDA1 unit (section "Network applications"
(page 27)).
• Description of the voice and signalling conferencing features (section
"Conferencing" (page 32)).
• All voice related functions as input and output levels, echo cancellation
and voice signal transport (section "Voice" (page 34)).
• All signalling related functions as E&M interface types and signalling
transport (section "Signalling" (page 40)).
• Cross connection examples for conference applications (section "Confer-
ence cross connections" (page 54)).
• Traffic and equipment protection functions (section "Protection"
(page 56)).
5.1 Network applications
The main network applications with the LEDA1 unit are

• LEDA1 in a point-to-point application.
• LEDA1 in a point-to-multipoint application.
• LEDA1 in a multipoint-to-multipoint application.
5.1.1 Point-to-point (P2P)

The point-to-point application connects one E+M interface (voice and signal-
ling) with another E+M interface through a TDM network.
The connection can be protected with 1+1 SNCP or LTP.
Network element 1 Network element 2
TDM
Network
E+M E+M
interface interface
P12 transport unit
LEDA1 unit
Figure 8: Point-to-point application with LEDA1
FOX61xLEDA1 27
5.1.2 Point-to-multipoint (P2MP)

The point-to-multipoint application is a linear or star network application. It
connects one master E+M interface with several slave E+M interfaces
through a TDM network.
When the master terminal sends, it sends in direction towards the slaves,
and all slave terminals can receive the sent signal.
When a slave terminal sends, it sends in direction towards the master, and
only the master can receive the sent signal.
The sender does not receive its sent signal.
This type of application is used together with the conferencing features of
LEDA1.
The connection between any two network elements can be protected with
1+1 SNC protection on the transport layer
It is also possible to implement a shared protection ring (SPR) for the protec-
tion of the linear LEDA1 network. For further information please refer to
"1KHW002467 FOX61x TDM Services".
to to
Master master
Intermediate slave slave
Tail end slave
Network element 1 Network element k Network element n
TDM TDM
Network Network
E+M E+M
interface local
interface
master
E+M
interface
P12 transport unit
Conference on
LEDA1 unit
LEDA1 unit
Figure 9: Point-to-multipoint linear application with LEDA1
28 FOX61xLEDA1
to
master
Slave 1
to slave
Master or local
TDM E+M
1 1
Network interface
2
to
master Slave 2
3
TDM 1
E+M
Network interface
1
to
to master Slave 3
E+M master
interface TDM
master Network to slave
or local
P12 transport unit

1 2
Conference on
LEDA1 unit
E+M
interface
LEDA1 unit
E+M
interface
Figure 10: Point-to-multipoint star application with LEDA1
FOX61xLEDA1 29
5.1.3 Multipoint-to-multipoint (MP2MP)

The multipoint-to-multipoint application is a linear or star network application.
It connects one master E+M interface with several slave E+M interfaces
through a TDM network.
When the master terminal sends, it sends in direction towards the slaves,
and all slave terminals can receive the sent signal.
When a slave terminal sends, it sends in direction towards the master and
towards the tail end slave, and all master and slave terminals can receive
the sent signal.
This type of application is used together with the conferencing features of
LEDA1.
The connection between any two network elements can be protected with
1+1 SNC protection on the transport layer
It is also possible to implement a shared protection ring (SPR) for the protec-
tion of the complete LEDA1 network. For further information please refer to
"1KHW002467 FOX61x TDM Services".
to to
Master master
Intermediate slave slave
Tail end slave
Network element 1 Network element k Network element n
TDM TDM
Network Network
E+M E+M
interface interface
master
local
E+M
P12 transport unit interface
Conference on
LEDA1 unit
LEDA1 unit
Figure 11: Multipoint-to-multipoint linear application with LEDA1
30 FOX61xLEDA1
to
master
Slave 1
to slave
Master or local
TDM E+M
1 1
Network interface
2
to
master Slave 2
3
TDM 1
E+M
Network interface
to
master Slave 3
1
to
TDM
E+M master Network to slave
or local
interface
master
P12 transport unit

1 2
Conference on E+M
LEDA1 unit interface
LEDA1 unit
E+M
interface
Figure 12: Multipoint-to-multipoint star application with LEDA1
Please note that in an intermediate slave the differentiation between “to mas-
ter” and “to slave” is done from a protocol point of view. The conferencing is
the same for all participants, irrespective if they are “local”, “to master” or “to
slave”.
FOX61xLEDA1 31
5.2 Conferencing
5.2.1 Local conferences

The LEDA1 unit offers up to 10 individual voice conferences for local partici-
pants, i.e. from LEDA1 ports or any other E+M or PSTN unit in the network
element. The conferences include also the participants from the “to master”
and “to slave” direction, i.e. from other network elements, transported via the
TDM network.
The number of participants per conference is limited to 17.
The total number of participants of all 10 conferences is limited to 32.
Local conferences on one or several LEDA1 units can be cascaded to build
one large conference with more than 17 participants.
The voice conference function performs the addition of the voice signals.
The G.711 coded signals of the participants are decoded to the linear format,
level adjusted and added. The voice signal of every second participant is
inverted to avoid feedback or other acoustic instabilities.
Finally the summed signal is coded to the G.711 format. The signalling pat-
terns of all participants are combined in a wired-AND function, i.e. if any of
the participants exhibits an active state (CAS-bit = 0), this active state is
inherited to the combined CAS signal.
master/slave
Voice G.711 linear
P12 transport ,
e.g. LEDE1
participants 1+1 protection switching,
cross connect
linear
Σ G.711
LESU1
local
participants
CAS
&
conference
local
participants LEDA1
LESU1
local
participants G.711
1
local
analog Voice and
participants
LEDA1 E+M
front
CAS interface
8
E&M
Figure 13: Local conference on LEDA1
32 FOX61xLEDA1
5.2.2 Conferences in the P2MP application

Conferences in the point-to-multipoint application add the voice and CAS
signals of the local participants to the signal going towards the master.
There is no addition in the direction to the last slave or towards the local par-
ticipants.
to master to slave
PBUS
PBUS
local local
1 n
Figure 14: Conference in the P2MP application
5.2.3 Conferences in the MP2MP application

Conferences in the multipoint-to-multipoint application consist of a number of
sub-conferences. The number of sub-conferences corresponds to the num-
ber of participants. The sub-conference of each participant adds the voice
and CAS signals of all participants except the own signal.
The designation “to master” or “to slave” has no relevance for the conference
itself, since the setup is symmetrical in relation to the network directions. The
“to master” and “to slave” participant designations just help to setup the
transport cross connections.
to master to slave
PBUS
Σ Σ
1 2 3 4 n 1 2 3 4 n
1
2 2
3
4
n
Σ 1
3
4 Σ n
PBUS
local 2 3 4 local
1 n
Figure 15: Conference in the MP2MP application
FOX61xLEDA1 33
5.3 Voice
5.3.1 E&M voice interface types

The LEDA1 unit offers 8 2-wire or 4-wire analogue voice interfaces. The
voice interface type is configurable by the element manager individually per
port.
The analogue voice bandwidth is 300 … 3'400 Hz. The voice input and out-
put gains are configurable by the element manager individually per port.
The analogue voice signal is coded and decoded according to ITU-T G.711,
A-law.
a1
D
b1
A
4-wire
a2
A
2-wire
b2
D
Figure 16: LEDA1 voice interface
5.3.2 Line echo cancellation

A mismatch between the impedance of the subscriber line and the LEDA1
user port line impedance causes a near end echo that can be heard at the
far end.
The line echo canceller reduces this near end echo with a tail length of 1 ms.
This feature can be enabled or disabled in the LEDA1 interface configura-
tion.

When connecting a modem to LEDA1 the echo canceller must be disabled
by configuration.
An enabled echo canceller can disturb the data transmission.
Please note:
The LEDA1 unit is not able to detect a modem control tone (and automati-
cally disable the echo canceller).
The line echo canceller can be enabled or disabled. The echo canceller is
mainly used in the 2-wire interface mode.
The echo canceller requires the returned echo signal to be attenuated by at
least 6 dB to be able to adapt, i.e. the line termination at the subscribers ter-
minal equipment must be close to the 600 Ω line impedance implemented on
LEDA1.
5.3.3 E&M interface voice transport

With each of the 8 user ports the LEDA1 unit offers a 2-wire or 4-wire ana-
logue voice interface.
34 FOX61xLEDA1
For each subscriber port the relative input level and relative output level of
the analogue signal can be adjusted by configuration:
In the digital network the relative level is at 0 dBr according to ITU-T G.101,
i.e. the relative level configuration corresponds directly to the signal levels at
the analogue port. The following figure shows the relative levels, and in italic
also the absolute levels.
-2 dBr Analogue Input
0 dBr
-12 dBm to digital Level -10 dBm
conversion setting
-2 dBr
Analogue PCM
Signal Signal
Digital to Output
analogue Level
conversion setting
-6 dBr -6 dBr 0 dBr
-14 dBm -8 dBm
Figure 17: Level configuration on input and output directions
The values in italic are examples of absolute levels. With the shown configu-
ration you have in upstream direction a gain of 2 dB and in downstream
direction a loss of 6 dB.
Please note:
With the 2-wire interface type the absolute output level should always be at
least 1 dB below the absolute input level in order to eliminate any echo or
instability of the subscriber interface.
Please note:
To avoid reflexions with high impedance telephones connected to a user
port, an external terminating resistor must be applied. The resulting termina-
tion should be close to 600 Ω.
Echo signals due to reflexions cause disturbances in conferences.
Please note:
The theoretical load capacity of a PCM A-law coded signal is +3.14 dBm0.
With a relative level of 0 dBr, the maximum absolute level is therefore 0 dBr
+ 3.14 dBm0 = 3.14 dBm.
Back -to-back Set out of

loop service
a2
A
2-wire b2 Input level 0 dBr
D Voice signal
setting
1111'1111 to PBUS
2-wire / Test signal Set out of Protection

4-wire 4-wire insertion service switch
Working voice signal

from PBUS
a1 D Output level 0 dBr Protecting voice signal
silence
b1 A setting tone from PBUS
Figure 18: E&M interface voice transport
The voice handling can be configured with the following control mechanisms:
• Interface type 2-wire or 4-wire:
FOX61xLEDA1 35
The 2-wire interface type uses only the a2/b2 pins of the voice user port.
The 4-wire interface type uses the a1/b1 pins for the output signal and
the a2/b2 pins for the input signal.
• Back-to-back loop:
The maintenance function ‘back-to-back loop’ loops the voice signal com-
ing from the backplane back to the backplane. The loop is transparent.
• Front-to-front loop:
The maintenance function ‘front-to-front loop’ loops the voice signal com-
ing from the front interface back to the front interface.
The signal is looped via the backplane, i.e. the PBUS. The loop is trans-
parent.
• Input level:
With the 2-wire interface type the relative input level can be configured
from -12.5 dBr to +9.5 dBr in steps of 0.5 dBr.
With the 4-wire interface type the relative input level can be configured
• Output level:
With the 2-wire interface type the relative output level can be configured
from -20.0 dBr to -1.0 dBr in steps of 0.5 dBr.
With the 4-wire interface type the relative output level can be configured
• Interface line state ‘out of service’:
The maintenance function ‘out of service’ of an interface replaces the
transmit signal going to the PBUS by an ‘all-1’ signal.
In receive direction the receive signal from the PBUS is replaced by a
silence signal, i.e. by an ‘all-0’ signal in the 16-bit linear voice domain.
• Interface line state ‘test signal insertion’:
The maintenance function ‘test signal insertion’ replaces in receive direc-
tion the voice signal by a continuous test signal sequence:
Frequency
[Hz]
2'000
1'666
1'388
1'000
888
694
500
444
0.5 s time
7.0 s
Figure 19: Test signal sequence
• Protection switching:
In receive direction a working and a protecting channel can be config-
ured. Switching criteria are ‘trail signal fail’ and ‘trail signal degrade’ from
the P12 transport unit. With CAS enabled, CAS AIS is an additional
switching criterion.
5.3.4 Conference voice transport

The LEDA1 unit offers voice conferences with a maximum of 17 participants
per conference. In order to eliminate any instabilities the participants input
signals and output signals can be attenuated.
36 FOX61xLEDA1
The squelch function suppresses small voice levels in order to avoid sum-
ming up noise signals. The squelch level can be configured on the unit layer.
The higher the squelch level the higher are also audible disturbances on the
voice signal.
In the multipoint-to-multipoint (MP2MP) application, all participants are han-
dled identically. Each participant has its own sub-conference. The sub-con-
ference of each participant adds the voice signals of all participants except
the own signal.
Test signal Set out of Protection

insertion service switch

from PBUS
Input Protecting voice signal Participant 1:
P1 Squelch silence
gain tone from PBUS local or
to master or
P2 to slave
Σ
P3 Output
gain Voice signal
Pn 1111'1111 to PBUS


from PBUS
P2 Squelch silence
to master or
P1 to slave
P3
Pn
Σ Output
gain
1111'1111
Voice signal
to PBUS


from PBUS
P3 Squelch silence
to master or
P1 to slave
Σ
P2 Output
gain Voice signal


from PBUS
Input Squelch Protecting voice signal Participant n :
Pn silence
to master or
P1 to slave
Σ
P2 Output
P3 gain Voice signal
1111'1111 to PBUS
Figure 20: Conference voice transport, MP2MP
In the point-to-multipoint (P2MP) application, only the participant ‘to master’

has a sub-conference, adding the voice signals of all other participants
except the own signal. The other participants (‘local’ or ‘to slave’) receive
their voice signal from the ‘to master’ participant.
FOX61xLEDA1 37


from PBUS
Input Protecting voice signal
P1 Squelch silence
gain tone from PBUS Participant 1:
to master
P2
Σ
P3 Output
gain Voice signal


from PBUS
P2 Squelch silence
to slave
Output
P1 Voice signal
gain
1111'1111 to PBUS


from PBUS
P3 Squelch silence
local
Output
P1 Voice signal
gain
1111'1111 to PBUS


from PBUS
Input Squelch Protecting voice signal
Pn silence
gain tone from PBUS Participant n :
local
Output
P1 gain Voice signal
1111'1111 to PBUS
Figure 21: Conference voice transport, P2MP
The voice handling can be configured with the following control mechanisms:
• Input gain:
The input gain of each participant can be configured from -9 dB to 0 dB in
steps of 3 dB.
• Output gain:
The output gain of each participant can be configured from -9 dB to 0 dB
in steps of 3 dB.
• Squelch:
The noise suppression function of each participant can be enabled or dis-
abled. The noise suppression level can be configured on the unit layer
with the squelch level to ‘low’, ‘medium’ or ‘high’.
38 FOX61xLEDA1

When connecting a modem to a LEDA1 conference the squelch function
must be disabled by configuration.
An enabled squelch function can disturb the data transmission.
• Participant line state ‘out of service’:
The maintenance function ‘out of service’ of a participant replaces the
transmit signal going to the PBUS by an ‘all-1’ signal.
In receive direction the receive signal from the PBUS is replaced by a
silence signal, i.e. by an ‘all-0’ signal in the 16-bit linear voice domain.
• Participant line state ‘test signal insertion’:
tion the voice signal by a continuous test signal sequence:
Frequency
[Hz]
2'000
1'666
1'388
1'000
888
694
500
444
0.5 s time
7.0 s
Figure 22: Test signal sequence
FOX61xLEDA1 39
5.4 Signalling
5.4.1 E&M signalling interface states and CAS bits

With each of the 8 user ports the LEDA1 unit offers 2 signalling interfaces
E&M and E’&M’. E&M signalling is used as interface between a trunk circuit
(e.g. PABX) and a signalling unit (signalling transport). LEDA1 plays the role
of a signalling unit.
The E&M signalling is transported through a TDM network in the CAS bits.
The M and M’ signalling inputs control the CAS bits a (M) and b (M’). The E
and E’ signalling outputs are controlled correspondingly by the CAS bits a
(E) and b (E’).
VCC
a/b
M/M’
-U BAT GND
E/E’ a/b
GND GND
Figure 23: LEDA1 signalling interface
The detectors for the M and M’ signal states are implemented as voltage
detectors, not as current detectors. The default mapping of M and M’ signal
states to CAS signalling states is as follows.
M signal connected to ground → CAS a-bit = 0
M signal open or connected to battery voltage → CAS a-bit = 1
M’ signal connected to ground → CAS b-bit = 0
M’ signal open or connected to battery voltage → CAS b-bit = 1
To be able to handle all five E&M interface types (refer to section "E&M sig-
nalling interface types" (page 41) the CAS bit value for the M-detection can
be inverted.
The E and E’ signal outputs are open (highZ) in the inactive state and con-
nected to ground in the active state:
CAS a-bit = 0 → E signal output connected to ground (lowZ)
CAS a-bit = 1 → E signal output open (highZ)
CAS b-bit = 0 → E’ signal output connected to ground (lowZ)
CAS b-bit = 1 → E’ signal output open (highZ)
In case CAS is not used the signalling transport is not available. The E and
E’ signal outputs are kept in the open state.
40 FOX61xLEDA1
5.4.2 E&M signalling interface types

E&M signalling has five different implementations, called type I to type V.
The differences between the types are
− the number of used wires,
− the signalling voltage levels, and
− the detector bias voltage levels.
An inactive state (onhook) is transported with the CAS bit = 1, the active
state (offhook) is transported as CAS bit = 0.
Table 6: E&M signalling types

State Type M, M’ M bias CAS a, b E, E’ E bias
active I battery ground 0 ground battery
II battery ground 0 ground battery
(SB wire) (SG wire)
III battery ground 0 ground battery
(SB wire)
IV ground battery 0 ground battery
(SB wire) (SG wire)
V ground battery 0 ground battery
inactive I ground ground 1 open battery
II open ground 1 open battery
III ground ground 1 open battery
(SG wire)
IV open battery 1 open battery
V open battery 1 open battery
The LEDA1 unit supports all five interface types with some restrictions in the
interface cabling. Refer to the sections below.
5.4.2.1 E&M type I
Type I is a 2-wire interface using the M and E wires.

In the inactive state the M-wire is connected to ground and the E-wire is
open.
In the active state the M-wire is connected to battery and the E-wire is con-
nected to ground.
FOX61xLEDA1 41
Trunk circuit Signalling unit
GND
onhook
M Current
GND
detector
offhook
-U BAT
onhook
-U BAT
Current E
detector
offhook GND
Trunk circuit LEDA1
GND
onhook
M onhook = GND → a/b = 1
offhook = -UBAT → a/b = 0
offhook
-U BAT
-UBAT
onhook
-U BAT
Current E a/b = 1 → onhook = open
detector
a/b = 0 → offhook = GND
offhook GND
Figure 24: E&M signalling type I, and implementation with LEDA1
Please note:
The implementation of the interface type I with LEDA1 requires the M signal-
ling to be inverted.
5.4.2.2 E&M type II
Type II is a 4-wire interface using the M, SB (signal battery), E and SG (sig-

nal ground) wires.
In the inactive state the M-wire and the E-wire are open.
In the active state the M-wire is connected to battery voltage fed from the
signalling unit via the SB wire and the E-wire is connected to ground fed
from the trunk unit via the SG wire.
This interface type allows having the trunk circuit and the signalling unit in
different buildings.
42 FOX61xLEDA1

onhook
M Current
GND
detector
offhook SB -U BAT
onhook
-U BAT
Current E
detector
GND
SG offhook
Trunk circuit LEDA1

onhook
M onhook = -UBAT → a/b = 1
offhook = GND → a/b = 0
offhook SB GND connect SB to GND on the MDF
-UBAT
onhook
-U BAT
detector a/b = 0 → offhook = GND
GND
SG offhook GND SG wire is not used in LEDA1
Figure 25: E&M signalling type II, and implementation with LEDA1
The implementation of the interface type II with LEDA1 is accomplished by

connecting the SB wire to ground at the main distribution frame. The SG wire
is not used in this implementation.
For correct operation the potential difference between the trunk circuit
ground and the FOX61x ground must be < 4 V. This is generally the case if
the trunk circuit and the FOX61x are located in the same building.

The type II implementation is only applicable for in-house application.
FOX61xLEDA1 43
5.4.2.3 E&M type III
Type III is a 4-wire interface using the M, SB (signal battery), E and SG (sig-
nal ground) wires.
In the inactive state the M-wire is connected to ground fed from the signalling
unit via the SG wire and the E-wire is open.
In the active state the M-wire is connected to battery voltage fed from the
signalling unit via the SB wire and the E-wire is connected to ground.
SG GND
onhook
M Current GND
detector
offhook SB -U BAT
onhook
-U BAT
Current E
detector
offhook GND
Trunk circuit LEDA1

SG
leave SG wire open
onhook

offhook SB GND connect SB to GND on the MDF
-UBAT
onhook
-U BAT
offhook
GND
Figure 26: E&M signalling type III, and implementation with LEDA1
The implementation of the interface type III with LEDA1 is accomplished by

is not used in this implementation and is left open.
5.4.2.4 E&M type IV
Type IV is a 4-wire interface using the M, SB, E and SG wires.

In the active state the M-wire is connected to ground fed from the signalling
unit via the SB wire and the E-wire is connected to ground fed from the trunk
unit via the SG wire.
This interface type allows having the trunk circuit and the signalling unit in
different buildings.
44 FOX61xLEDA1

onhook
M Current
-U BAT
detector
offhook SB GND
onhook
-U BAT
Current E
detector
GND
SG offhook
Trunk circuit LEDA1

onhook
offhook SB GND
-UBAT connect SB to GND on the MDF
onhook
-U BAT
SG offhook GND
GND SG wire is not used in LEDA1
Figure 27: E&M signalling type IV, and implementation with LEDA1
The implementation of the interface type IV with LEDA1 is accomplished by

is not used in this implementation.
For correct operation the potential difference between the trunk circuit
ground and the FOX61x ground must be < 4 V. This is generally the case if
the trunk circuit and the FOX61x are located in the same building.

The type IV implementation is only applicable for in-house application.
FOX61xLEDA1 45
5.4.2.5 E&M type V
Type V is a 2-wire interface using the M and E wires.

In the active state the M-wire and the E-wire are connected to ground.
onhook
M Current
-U BAT
detector
GND offhook
onhook
-U BAT
Current E
detector
offhook GND
Trunk circuit LEDA1

onhook
GND offhook
-UBAT
onhook
-U BAT
offhook GND
Figure 28: E&M signalling type V, and implementation with LEDA1
No special measures have to be taken to implement the type V interface with

LEDA1.
46 FOX61xLEDA1
5.4.3 E&M interface signalling transport

With each of the 8 user ports the LEDA1 unit offers 2 signalling interfaces
E&M and E’&M’. The M and M’ signalling inputs control the CAS bits a (M)
and b (M’). The E and E’ signalling outputs are controlled correspondingly by
the CAS bits a (E) and b (E’).
Back-to-back CAS Set out of

loop enabled service
a-bit a
b
M 0
c
d
1
CAS signalling
1111
1111 to PBUS
M signalling
-UBAT inverted
b-bit abcd
M’
-UBAT
CAS AIS
monitor
CAS Signalling CAS Test signal Set out of Protection

AIS mode enabled insertion service switch
E Working CAS signalling

from PBUS
a-bit Protecting CAS signalling
Signalling 1111 from PBUS
forwarding / 1101
blocking 1111 CAS AIS
GND monitor
E’
b-bit
GND
Figure 29: E&M interface signalling transport
The CAS handling can be configured with the following control mechanisms:
• M signalling inverted:
M/M’ signal connected to ground → CAS a/b-bit = 1
M/M’ signal open or connected to battery voltage → CAS a/b-bit = 0
M signal not inverted:
M/M’ signal connected to ground → CAS a/b-bit = 0
M/M’ signal open or connected to battery voltage → CAS a/b-bit = 1
The maintenance function ‘back-to-back loop’ loops the CAS pattern
coming from the backplane back to the backplane.
Please note:
The signalling loops work only for quasi static signalling patterns (< 1 signal-
ling state change per second).
The maintenance function ‘front-to-front loop’ loops the CAS pattern com-
ing from the front interface back to the front interface.
The signal is looped via the backplane, i.e. the PBUS.
FOX61xLEDA1 47
• CAS enabled:
In transmit direction the a and the b bit are controlled by M and M’, the c
bit is fixed to ‘0’ and the d bit is fixed to ‘1’.
In receive direction the E and E’ signals are controlled by the a and b bit:
CAS a/b-bit = 0 → E/E’ signal output connected to ground (lowZ)
CAS a/b-bit = 1 → E/E’ signal output open (highZ)
CAS disabled:
In transmit direction the abcd bits are all set to ‘1’.
In receive direction the CAS AIS monitoring is disabled and the E and E’
signal outputs are set to open.
• Interface line state ‘out of service’:
The maintenance function ‘out of service’ of an interface replaces the
abcd bits from and towards the PBUS by the CAS AIS.
Depending of the signalling mode, the E/E’ output signals can be open
(‘transparent’, ‘incoming’) or closed to ground (‘outgoing’).
• Interface line state ‘test signal insertion’:
tion the abcd bits by the idle pattern ‘1101’, i.e. the E and E’ signal out-
puts are set to open.
• Signalling mode:
In receive direction the signalling mode defines the behaviour of the E/E’
signal outputs in case of a received CAS AIS. Please refer to section
"E&M interface signalling modes of operation" (page 48).
5.4.4 E&M interface signalling modes of operation

Transmission line and transmission equipment failures in the TDM network
cause the insertion of the alarm indication signal (AIS) in the signalling chan-
nel of an affected voice channel (CAS AIS = abcd = 1111).
If CAS is enabled in the port managed object, the signalling mode controls
the reaction of the E and E’ signal outputs in case of a received CAS AIS.
The following modes are available:
− transparent
− incoming
− outgoing
The terms “incoming” and “outgoing” are related to the connection establish-
ment. The calling exchange uses the signalling lines designated as “outgo-
ing”, on the called exchange these lines are designated as “incoming”. A
connection is established from the “outgoing” interface to the “incoming”
interface.
48 FOX61xLEDA1
Calling LEDA1 LEDA1 Called

exchange M, M’ TDM CAS AIS E, E’ exchange
outgoing Network incoming
CAS AIS
E, E’ M, M’
forward direction
backward direction
Figure 30: Incoming and outgoing lines
Depending if the failure occurred in direction to a called exchange or in direc-

tion to the calling exchange, the reaction on this failure must be handled dif-
ferently.
In forward direction, i.e. in direction to the called exchange, a transmission
failure must not block this connection so as not to tie up other exchanges to
call this telephone. The connection must be cleared at the incoming end.
In backward direction, i.e. in direction to the calling exchange, a transmission
failure must block this connection so it is not used again until the fault is cor-
rected. The connection must be blocked at the outgoing end.
The LEDA1 unit can provide such automatic signalling in case of transmis-
sion failures with the signalling mode configuration.
• Outgoing
At the outgoing end of a connection, the LEDA1 port configured to “out-
going” provides the following blocking signal to block the calling
exchange:
− When CAS AIS is received the outputs E/E’ are opened (derived from
bits a/b).
− After 12.5 s, the outputs E/E’ are connected to ground, i.e. blocked.
− 0.4 s after the CAS AIS is cleared, the outputs E/E’ are unblocked, i.e.
E/E’ are controlled by the a and b signalling bits.
CAS AIS
active
inactive
time
E/E’ 12.5 s
0.4 s
open
ground
time
Figure 31: Outgoing signalling timing
• Incoming
At the incoming end of a connection, the LEDA1 unit configured to
“incoming” provides the following 700 ms clear forward signal pulse to
free the called exchange:
− When CAS AIS is received the outputs E/E’ are opened (derived from
bits a/b).
− After 12.5 s, the outputs E/E’ are connected to ground for 0.7 s and
afterwards opened again.
− 0.4 s after the CAS AIS is cleared, the outputs E/E’ are unblocked, i.e.
E/E’ are controlled by the a and b signalling bits.
FOX61xLEDA1 49
CAS AIS
active
inactive
time
E/E’ 12.5 s
0.7 s 0.4 s
open
ground
time
Figure 32: Incoming signalling timing
• Transparent
This setting is used if the trunk line is used in an application that does not
require the manipulation of the signalling bits as described above. An
example is when the channel is used to transmit data using an analogue
modem:
− The output signals E/E’ are always directly controlled by the a and b
signalling bits.
5.4.5 Conference signalling transport

The LEDA1 unit offers up to 10 conferences with a maximum of 17 partici-
pants per conference. The signalling patterns of all participants are com-
bined in a wired-AND function, i.e. if any of the participants exhibits an active
state (CAS-bit = 0), this active state is inherited to the combined CAS signal.
In the multipoint-to-multipoint (MP2MP) application, all participants are han-
dled identically. Each participant has its own sub-conference. The sub-con-
ference of each participant adds the CAS signals of all participants except
the own signal.
50 FOX61xLEDA1
Conference Participant
CAS CAS
enabled enabled
Working CAS signalling
from PBUS
Protecting CAS signalling
1111 from PBUS Participant 1:
P1 1101 local or
1111 to master or
CAS AIS
to slave
monitor
P2 1111
&
P3 1111 CAS signalling to PBUS
Pn 1101
Participant
CAS insertion service switch
enabled

from PBUS
1111 Participant 2:
from PBUS
P2 1101 local or
1111 to master or
CAS AIS to slave
monitor
P1 1111
P3
Pn
& 1101
1111 CAS signalling to PBUS
Participant
CAS
enabled
from PBUS
1111 from PBUS Participant 3:
P3 1101 local or
1111 to master or
CAS AIS
to slave
monitor
P1 1111
&
Pn 1101
Participant
enabled

from PBUS
1111 Participant n :
from PBUS
Pn 1101 local or
1111 to master or
CAS AIS to slave
monitor
P1 1111
P2
P3 & 1101
Figure 33: Conference signalling transport, MP2MP
In the point-to-multipoint (P2MP) application, only the participant ‘to master’

has a sub-conference, adding the CAS signals of all other participants
except the own signal. The other participants (‘local’ or ‘to slave’) receive
their CAS signal from the ‘to master’ participant.
FOX61xLEDA1 51
Conference Participant
CAS CAS
enabled enabled
from PBUS
1111 from PBUS
P1 1101 Participant 1:
1111 to master
CAS AIS
monitor
P2 1111
&
Pn 1101
Participant
enabled

from PBUS
1111 from PBUS
1111 to slave
CAS AIS
monitor
1111
P1
1101
Participant
CAS
enabled
from PBUS
1111 from PBUS
1111 local
CAS AIS
monitor
1111
P1
1101
Participant
enabled

from PBUS
1111 from PBUS
Pn 1101 Participant n :
1111 local
CAS AIS
monitor
1111
P1
1101
Figure 34: Conference signalling transport, P2MP
The CAS handling can be configured with the following control mechanisms:
• Participant CAS enabled:
In direction from the PBUS the abcd bits are the signalling bits received
from the PBUS.
In direction to the PBUS the abcd bits coming from the conference are
sent to the PBUS.
Participant CAS disabled:
In direction from the PBUS the CAS AIS monitoring is disabled and the
abcd bits are all set to ‘1’ (CAS AIS).
In direction to the PBUS the abcd bits coming from the conference are
replaced by the CAS AIS.
52 FOX61xLEDA1
Participant CAS enabling has precedence over the conference CAS ena-
bling.
• Participant line state ‘out of service’:
The maintenance function ‘out of service’ of a participant has the same
effect on the signalling as the CAS disabling of the participant, i.e. the
abcd bits from and towards the PBUS are replaced by the CAS AIS.
• Participant line state ‘test signal insertion’:
The maintenance function ‘test signal insertion’ replaces in direction from
the PBUS the abcd bits by the idle pattern ‘1101’.
• Conference CAS enabled:
In direction to the PBUS the abcd bits resulting from the AND combina-
tion are sent to the PBUS.
Conference CAS disabled:
In direction to the PBUS the abcd bits resulting from the AND combina-
tion are replaced by the idle pattern ‘1101’.
In direction from the PBUS a working and a protecting channel can be
configured. Switching criteria are ‘trail signal fail’ and ‘trail signal degrade’
from the P12 transport unit. With participant CAS enabled, CAS AIS is an
additional switching criterion.
Please note:
It a port requires CAS for the control signal transport CAS must be enabled
on the P12 transport signal.
→ The termination mode of the P12 transport signal must be set to
“PCM30” or “PCM30C”.

It is possible to create a cross connection from a LEDA1 port using CAS to
another CTP not using CAS.
→ This would result in a non operational signalling transport.
FOX61xLEDA1 53
5.5 Conference cross connections
5.5.1 Unprotected network connections

Conferences in a point-to-multipoint or multipoint-to-multipoint application
require the configuration of the connection role of the participants according
to the network element type:
Slave NE without Slave NE
Master NE participant Slave NE tail end
to slave to master to slave to master
TDM TDM TDM
Network Network Network
LEDA1 LEDA1 LEDA1
to master local local local
P12 transport unit
Figure 35: NE types in point-to-multipoint and multipoint-to-multipoint

applications
• Master NE:
− 1 participant ‘to master’, connected to the master terminal.
− 1 participant ‘to slave’, connected to the P12 transport in direction to
the slave NEs.
− any number of ‘local’ participants, connected to the local slave termi-
nals.
Please note:
When only one ‘master’ participant is connected at the ‘master NE’, no con-
ference is required and the master interface can be connected directly
towards the slave NEs.
• Slave NE without DTE:
− no participants.
• Slave NE:
− 1 participant ‘to slave’, connected to the P12 transport in direction to
the slave NE tail end.
− 1 participant ‘to master’, connected to the P12 transport in direction to
the master NE.
− at least 1 participant ‘local’, connected to the local slave terminal.
• Slave NE tail end:
− 1 participant ‘to master’, connected to the P12 transport in direction to
the master NE.
− at least 1 participant ‘local’, connected to the local slave terminal.
54 FOX61xLEDA1
Please note:
When only one ‘local’ participant is connected at the ‘slave NE tail end’, no
conference is required and the local interface can be connected directly
towards the ‘master NE’.
Conferencing signals are all taken from the PBUS. There is no direct access
of the local port signals to a conference, i.e. all participants of a conference
must be cross connected with the cross connect configuration of FOX61x.
Please note:
It a participant requires CAS for the control signal transport CAS must be
enabled on the P12 transport signal.
→ The termination mode of the P12 transport signal must be set to
“PCM30” or “PCM30C”.

It is possible to create a cross connection from a LEDA1 conference partici-
pant using CAS to another CTP not using CAS.
→ This would result in a non operational signalling transport.
FOX61xLEDA1 55
5.6 Protection
5.6.1 Subnetwork connection protection and linear trail protection

5.6.1.1 Protection features
LEDA1 supports 1+1 linear trail protection (LTP) and 1+1 inherently moni-
tored subnetwork connection protection (SNCP/I). 1+1 protection is available
for the E+M ports and for the conference participants.
The difference between the two protection scenarios lies in the availability of
CAS. CAS AIS is a failure criterion of the own layer, i.e. of the P0 layer.
• If CAS is available the CAS AIS failure can be detected, which is then the
1+1 linear trail protection. Trail protection protects against server failures
and disconnected matrix connections (via CAS AIS detection).
• If CAS is not available only the server layer defects can be detected,
which is then the 1+1 SNCP/I protection. SNCP/I protects against server
failures.
1+1 protection provides the 1+1 unidirectional protection. The operation type
can be configured to revertive or non-revertive.
working working
TDM
protecting Network protecting
P12 P12 P12 P12

transport transport transport transport
P-12 P-12 P-12 P-12
PBUS PBUS
P12 P12 P12
P0 P0 P0
LEDA1 E&M E&M LEDA1
Figure 36: 1+1 protection
56 FOX61xLEDA1
5.6.1.2 Protection configuration
P0 protection switching takes place in the LEDA1 cross connect function (P0
cross connect).
Protection switching action is driven by the traffic signal request type:
• Traffic signal requests:
− Signal fail (SF)
The SF state is activated if the analysis of the incoming server signal
on the transport unit reports a signal failure, e.g. loss of signal.
− CAS-AIS
The CAS signalling pattern abcd of the received signal exhibits an
AIS, i.e. abcd = 1111.
− Signal degraded (SD)
The SD state is activated if the analysis of the incoming server signal
on the transport unit reports a degraded signal, e.g. BER 10-6.
It is possible to check the status of the protection switch (working, protecting
circuit) via the CTP status function.
For more information on cross connections and protection switching please
refer to FOX61x TDM Services Manual.
5.6.2 Equipment protection (EQP)

5.6.2.1 EQP features
To protect the LEDA1 functions against a failure on the LEDA1 unit, FOX61x
offers the possibility to equip the subrack with a second LEDA1 unit.
EQP protects the conference function. The E&M interfaces can not be pro-
tected.
In case of a failure on the active (working or protecting) unit the user traffic is
rerouted from the failed LEDA1 unit to the stand-by LEDA1 (protecting or
working) unit.
The working and the protecting LEDA1 units can be plugged in any free slot
of the FOX61x subrack.
FOX61xLEDA1 57
Please note:
The ports on the standby unit are inactive.
Please note:
The protection switching is non revertive, i.e. after the repair of a failed
LEDA1 unit, the currently active LEDA1 unit remains the active unit irrespec-
tive if it is the working or protecting unit.
Please note:
During a protection switching event the user traffic is interrupted for up to
10 s.
Please note:
Performance management data on the standby unit is cleared.
→ Performance management data collection restarts after an equipment
protection switchover event on the active unit.
5.6.2.2 EQP prerequisites
To enable equipment protection for the LEDA1 unit some prerequisites must
be met:
• The protecting LEDA1 unit must be in the unassigned state. Otherwise
the unit will not be selectable in the EQP configuration in AP: /unit-x, Con-
figuration - EQP: Create EQP Group…, EQP Group Creation, Protecting
Unit.
• The protecting unit must be hardware compatible with the working unit.
Check the hardware compatibility status after the EQP group configura-
tion in the AP: /unit-x, Status - EQP: Units Status, HW Compatible.
• The protecting unit must be software compatible with the working unit.
Check the software compatibility status after the EQP group configuration
in the AP: /unit-x, Status - EQP: Units Status, SW Compatible.
The compatible software must be installed on the LEDA1 unit before the
EQP group creation.
• The unit configuration of an equipment protection group is always done
on the active unit. The configuration on the standby unit is not possible.

The configuration of an equipment protection group must be saved (AP: /
Configuration - Configuration Management: Save).
Otherwise, in case of a protection switch event, the NE will load an outdated
configuration from the internal configuration database and the NE configura-
tion will be corrupted.
5.6.2.3 EQP configuration
The working LEDA1 unit of an EQP group is assigned and configured the
same way as a stand alone LEDA1 unit.
The protecting LEDA1 unit is running with the same ESW as the working unit
and must be in the unassigned state.
The 1+1 equipment protection group is configured on the working unit:
58 FOX61xLEDA1
• AP: /unit-x, Configuration - EQP.

− Execute the command “Create EQP Group…”.
− Select the Protecting unit, e.g. /unit-18.
− Execute “OK”.
• Save the NE configuration.
Further on any changes on the LEDA1 configuration must be done on the
active unit. To find out which unit is the active unit check the AP tree or the
unit status of the working or protecting LEDA1 unit.
5.6.2.4 EQP status
The unit status of the working and protecting units shows the actual status of
the units belonging to the equipment protection group. The unit status offers
also the commands for the EQP manipulation:
• Manual switch
The currently standby unit is set as active unit and the currently active
unit is set as standby unit. This requires that the currently standby unit is
in operational state, i.e.
− has no failure,
− is not isolated.
A manual switch is possible if it is indicated with the “Manual Switch-Over
Allowed” parameter.
Note that this command can only be activated on the working unit status
window.
• Forced switch
The currently standby unit is set as active unit, independent of the failure
state of the currently standby unit.
Note that there is a risk that the user traffic will be permanently inter-
rupted if the currently standby unit is in a failure state.
The currently active unit is set as standby unit.
Note that this command can only be activated on the working unit status
window.
• Isolate unit
To be able to perform a maintenance action, e.g. update of the embed-
ded software, on an active unit without activating a protection switch-
over, the working unit can be isolated. This means that the protection
switching state machine is frozen and no protection switch will be done
until the isolation of the unit is removed.
Note that the isolate unit command can only be applied to the working
unit.
• Join unit
Remove the isolation of a previously isolated unit.
Note that the join unit command can only be applied to the working unit.
The table in the EQP status window displays the following items:
• Unit
MO address of the unit belonging to the EQP group.
• EQP unit mode
The working unit is the unit where the protection group has been config-
ured.
The protecting unit is the unit that has been set to the unassigned state
before configuring the protection group.
FOX61xLEDA1 59
• Active
Active true means the unit is the active unit, i.e. it is the operational unit.
Active false means the unit is the standby unit, i.e. it is not the operational
unit.
The active state can be changed with the “Manual Switch” and “Forced
Switch” commands.
• Failure
Failure true means the unit is in a failure state.
Failure false means the unit is not in a failure state.
The failure state can not be changed manually.
• Substituted
Substituted true on the working unit means the unit has been substituted
by the protecting unit. A substituted unit is also in the “active false” state.
Substituted false on the working unit means the unit has not been substi-
tuted, i.e. it is the active unit or it has been isolated.
The substituted state of the protecting unit is always false.
• Isolated
Isolated true means the unit has been isolated with the “Isolate Unit”
command.
Isolated false means the unit is not isolated.
The isolation state can be changed with the “Isolate Unit” and “Join Unit”
commands.
The isolated state of the protecting unit is always false.
• HW Compatible
HW compatible true means the working HW unit is compatible with the
protecting HW unit.
HW compatible false means the working HW unit is not compatible with
the protecting HW unit. Equipment protection is not possible.
• SW Compatible
SW compatible true means the working unit embedded software (ESW) is
compatible with the protecting unit ESW.
SW compatible false means the working unit ESW is not compatible with
the protecting unit ESW. Equipment protection is not possible.
• DB Saved
DB saved true means the current configuration of the working unit has
been saved to the FOX61x internal database.
DB saved false means the current configuration of the working unit has
not been saved to the FOX61x internal database. A protection switching
event will load an outdated configuration and traffic will be disturbed.
60 FOX61xLEDA1
COMMISSIONING
6 Commissioning
This section describes the management of the basic system functions of the
LEDA1 unit and the configuration example for a user port and a voice confer-
ence.
In this section, you will find the following information:
• Managed object model (MOM) of the LEDA1 unit (section "Commission-
ing of a user port" (page 61)).
• Commissioning example of the LEDA1 unit and the configuration of a port
(section "Commissioning of a user port" (page 61)).
• Commissioning example of the LEDA1 unit and the configuration of a
voice conference (section "Commissioning of a conference" (page 64)).
• Calculation examples for the E&M signalling range (section "E&M signal-
ling range considerations" (page 69)).
Please refer to "1KHW002466 FOXCST Operation"for details on the general
GUI aspects, and to refer to "1KHW002464 FOX61x System Description" for
specific characteristics of the FOX61x.
6.1 Commissioning of a user port
6.1.1 Prerequisites
Before starting the commissioning of a user port on the LEDA1 unit, the fol-
lowing prerequisites need to be fulfilled.
6.1.1.1 CESM1 unit
In a FOX61x, a CESM1 needs to be in operation in slot 11 of the FOX61x

subrack.
6.1.1.2 LEDA1 unit
In a FOX61x, the LEDA1 service unit is inserted into one of the following
slots:
− FOX615:
slot 1 … 10,
slot 12 … 21.
− FOX612:
slot 7… 10,
slot 12 … 14.
For the installation of the unit, refer to "1KHW002461 FOX615 Installation" or
refer to "1KHW002462 FOX612 Installation".
A valid ESW is installed on the LEDA1 unit. For the management of ESW,
refer to "1KHW002466 FOXCST Operation". For details about compatible
ESW versions, refer to "1KHW002459 FOX61x Release Notes".
Port-y of the LEDA1 unit is connected to a central office with a 2-wire or 4-
wire voice connection and 2 E&M interfaces.
FOX61xLEDA1 61
COMMISSIONING
6.1.1.3 TDM transport unit
A TDM transport unit is inserted in the FOX61x and is running with a proper
ESW:
− LEDE1,
− DATI1,
− SAMO1,
− SAMO2.
6.1.1.4 FOXCST
FOXCST needs to be installed on a PC, and a management connection from

the FOXCST to the FOX61x needs to be up and running. For details about
the installation and operation of the FOXCST, please refer to FOXCST Oper-
ation Manual.
The amount and accessibility of operations depend on the user profile with
which you are logged in. For more information, please refer to FOXCST
Operation Manual.
6.1.1.5 PETS
The PETS on the FOX61x network element must be configured to an appro-

priate synchronization clock source, i.e. a clock source traceable to a PRC.
For the PETS configuration refer to FOX61x TDM Services Manual.
6.1.2 Configuration of a user port

For the configuration of the user port, the following steps have to be per-
formed.
Port configuration This action list shows step by step how to configure a user port. The given
example uses mostly the default values.
The following assumptions and identifiers are used:
 The LEDA1 unit is assumed to be plugged in slot 17 of a FOX615.
 The port to be configured has the identifier port-1.
 The voice connection is of 2-wire type.
Accept the unit Proceed as follows:

1. Navigate to the equipment status dialogue:
 AP:/unit-17, Main - Equipment:
2. Assign the unit:
 Execute the command “Assign”.
3. Execute “OK”.
62 FOX61xLEDA1
COMMISSIONING
Please note:
This command has to be executed only when the property “Assignment Sta-
tus / State” has the value “Unassigned”, i.e. after the first insertion of the
LEDA1 unit.
Configure the port general Proceed as follows:

parameters
1. Navigate to the general parameters:
 AP:/unit-17/port-1, Configuration - General.
2. Select the interface type:
 “2-Wire”.
3. Set the input level:
 e.g. “0” dBr.
4. Set the output level:
 e.g. “-6.5” dBr.
5. Disable the echo cancellation:
 “false” ().
6. Enable the CAS:
 “true” ().
7. Select the signalling mode:
 “Transparent”.
8. Disable the inverted M signalling:
 “false” ().
9. Execute “Apply”.
Configure the port CTP Proceed as follows:

parameters
1. Navigate to the CTP parameters:
 AP:/unit-17/port-1, Configuration - CTP.
2. The CTP parameters are implicitly set and fixed. All displayed parame-
ters are read-only.
3. Enable the revertive protection switching:
 “true” ().
4. Disable the CAS AIS supervision:
 “false” ().
5. Disable the switch-over logging:
 “false” ().
 The user port is completely configured.
Create the cross connection Proceed as follows:

1. Configure the cross connection from the user port to a time slot on a
LEDE1 unit. It is assumed that the connection termination point (CTP) on
the LEDE1 unit has been created before on port-8, time slot 1. Please
note that the termination mode of the LEDE1 port must be configured to
PCM30 or PCM30C, i.e. using CAS!
 FOXCST menu NE/Cross Connections…:
 The “Cross Connection” dialogue opens.
 Execute “Create…”.
 The “Create Cross Connection” dialogue opens.
FOX61xLEDA1 63
COMMISSIONING
2. Select the CTP a-End working address:

 Select the LEDA1 unit, e.g. “unit-17”.
 Select the user port CTP on the LEDA1 unit, e.g. “/unit-17/port-1”.
3. Select the CTP z-End address:
 Select the LEDE1 unit, e.g. “unit-20”.
 Select the channel CTP (with one time slot) on the LEDE1 port 8,
e.g. “/unit-20/port-8/chan-1”.
4. Execute “Create”.
 The bidirectional cross connection between LEDA1 and LEDE1 is config-
ured.
Activation Proceed as follows:

1. Set the administrative state of the port-1 to up
AP:/unit-17/port-1, Main - Admin And Oper Status:
 Set Administrative Status to “Up”.
- The “Operational Status” changes to “up”.
 The port is activated.
End of instruction
6.2 Commissioning of a conference
6.2.1 Prerequisites
Before starting the commissioning of a conference on the LEDA1 unit, the
following prerequisites need to be fulfilled.
6.2.1.1 CESM1 unit
In a FOX61x, a CESM1 needs to be in operation in slot 11 of the FOX sub-

rack.
6.2.1.2 LEDA1 unit
• In a FOX61x, the LEDA1 service unit is inserted into one of the following
slots:
− FOX615:
slot 1 … 10,
slot 12 … 21.
− FOX612:
slot 7… 10,
slot 12 … 14.
For the installation of the unit, refer to FOX615 Installation Manual or
refer to FOX612 Installation Manual.
• A valid ESW is installed on the LEDA1 unit. For the management of
ESW, refer to FOXCST Operation Manual. For details about compatible
ESW versions, refer to FOX61x Release Notes.
64 FOX61xLEDA1
COMMISSIONING
6.2.1.3 TDM transport unit
• A TDM transport unit is inserted in the FOX61x and is running with a

proper ESW:
− LEDE1,
− DATI1,
− SAMO1,
− SAMO2.
6.2.1.4 FOXCST
FOXCST needs to be installed on a PC, and a management connection from

the FOXCST to the FOX61x needs to be up and running. For details about
the installation and operation of the FOXCST, please refer to FOXCST Oper-
ation Manual.
The amount and accessibility of operations depend on the user profile with
which you are logged in. For more information, please refer to FOXCST
Operation Manual.
6.2.1.5 PETS
The PETS on the FOX61x network element must be configured to an appro-

priate synchronization clock source, i.e. a clock source traceable to a PRC.
For the PETS configuration refer to FOX61x TDM Services Manual.
6.2.2 Configuration of a conference
For the configuration of a conference, the following steps have to be per-

formed.
Conference configuration This action list shows step by step how to configure a conference. The given
example uses mostly the default values.
The following assumptions and identifiers are used:
 The LEDA1 unit is assumed to be plugged in slot 17 of a FOX615.
 The LEDA1 unit is assigned.
 The conference to be configured has the identifier conf-1.
 The conference is of the multipoint-to-multipoint type.
 The conference has one “local” participant, one participant “to master”
and one participant “to slave”
Configure the unit parameters Proceed as follows:

1. Navigate to the conferencing parameters:
 AP:/unit-17, Configuration - Conferencing.
2. Create a voice conference:
 Execute “Create Voice Conference…”.
 The “Create Voice Conference” dialogue opens.
3. Enter the conference parameters:
 Index = 1.
 Number Of Participants = 3.
 Type = MP2MP.
FOX61xLEDA1 65
COMMISSIONING
5. Select the squelch level:
 Squelch Level = Medium.
 The unit parameters are configured.
Configure the conference Proceed as follows:

general parameters
1. Navigate to the general parameters:
 AP:/unit-17/conf-1, Configuration - General.
2. Enable the CAS:
 CAS = .
Configure the participant 1 Proceed as follows:

general parameters 1. Navigate to the general parameters:
 AP:/unit-17/conf-1/part-1, Configuration - General.
2. Enable the CAS:
 CAS = .
3. Disable the squelch:
 Squelch = .
4. Set the input gain:
 Input Gain = 0 dB.
5. Set the output gain:
 Output Gain = 0 dB.
6. Select the participants role:
 Role = To Master.

CTP parameters 1. Navigate to the CTP parameters:
 AP:/unit-17/conf-1/part-1, Configuration - CTP.
2. The CTP parameters are implicitly set and fixed. All displayed parame-
ters are read-only.
3. Configure the z-End:
 Enable the Revertive Protection Switching = .
 Disable the CAS AIS Supervision = .
 Disable the Switch-Over Logging = .
 The participant 1 is completely configured.
66 FOX61xLEDA1
COMMISSIONING

general parameters
1. Configuration analogue to participant 1, but with the participants role set
to “To Slave”.

general parameters
1. Configuration analogue to participant 1, but with the participants role set
to “Local”.

for participant 1
1. Configure the cross connection from the participant 1 to a time slot on a
2. Select the “Cross connections” view of the FOXCST.
 Click on the “Connection Wizard” button:
 The “Create TDM Connection” dialogue opens.

3. Set the connection parameters:
 Layer Rate = P0-nc.
 Directionality = Bidirectional.
 Protected = No.
 Label 1 = <anyName>.
 Number = 1.
4. Execute “Next ->”.
5. Select the Z-End CTP:
 Select the LEDA1 unit, part-1 of conf-1.
7. Select the A-End CTP:
 Select the LEDE1 unit, port-1/chan-1.
ured.

for participant 2 1. Configure the cross connection from the participant 2 to a time slot on a
FOX61xLEDA1 67
COMMISSIONING

 Protected = No.
 Number = 1.
 Select the LEDE1 unit, port-2/chan-1.
ured.

for participant 3 1. Configure the cross connection from the participant 3 to a user port on
the same LEDA1 unit (port-1).

 Protected = No.
 Number = 1.
 Select the LEDA1 unit, port-1.
68 FOX61xLEDA1
COMMISSIONING
 The bidirectional cross connection between LEDA1 port and conference
participant is configured.
Activation Proceed as follows:

1. It is assumed that the administrative state of the port-1 has been set to
up before.
The conference does not need any activation.
End of instruction
6.3 E&M signalling range considerations
6.3.1 Trunk circuit to LEDA1

To evaluate the maximum distance a trunk circuit can be away from the
FOX61x, the following figure has to be considered for the M wire limiting the
distance:
RS : Serial line resistance of the M wire
RP : Cable and contact leakage resistance
RT: Terminating resistance in LEDA1, 40 kΩ
UM : Voltage at the M or M’ input:
-5 … +75 V: closed contact to ground
-24 … -UBAT V: open contact, or closed contact to battery volt-
age
-UBAT: FOX61x battery voltage, -38.5 … -75 V
Trunk circuit LEDA1

onhook
M RS UM
offhook RP RT
GND GND -U BAT
Figure 37: M signalling with LEDA1
In the closed contact case, the above figure is simplified to the following
schematic:
Trunk circuit LEDA1
RS UM
RT
GND -U BAT
Figure 38: M signalling, closed contact
FOX61xLEDA1 69
COMMISSIONING
UM = RS / (RS + RT) * (-UBAT) > -5 V (= closed contact)

RS < (-5 * RT) / (-UBAT + 5)
RS < 2.8 kΩ, with –UBAT = -75 V
The maximum distance is calculated for a 0.4 mm wire (140 Ω/km) to be
2800/140 = 20 km.
In the open contact case, the following simplified schematic is used:
Trunk circuit LEDA1
M UM
RP RT
GND -U BAT
Figure 39: M signalling, open contact
UM = RP / (RP + RT) * (-UBAT) < -24 V (= open contact)

RP > (-24 * RT) / (-UBAT + 24)
RP > 66.2 kΩ, with –UBAT = -38.5 V
6.3.2 LEDA1 to trunk circuit

To evaluate the maximum distance a trunk circuit can be away from the
FOX61x, the following figure has to be considered for the E wire limiting the
distance:
RS : Serial line resistance of the E wire
RD: Serial resistance of the current detector, 1 kΩ (assumption)
IS: Current to safely activate the current detector, 30 mA (assump-
tion)
US : Voltage drop at the E contact in LEDA1, 3 V
-UBAT: Trunk circuit battery voltage, -40 … -60 V (assumption)
Trunk circuit LEDA1

onhook
RD
-U BAT
Current E RS IS US
detector
offhook GND
Figure 40: E signalling with LEDA1
In the closed contact case, the above figure is simplified to the following
schematic:
Trunk circuit LEDA1
RD
Current E RS IS US
-U BAT
detector =
GND
Figure 41: E signalling, closed contact
IS = (-UBAT + US) / (RS + RD) < -30 mA (= closed contact)
70 FOX61xLEDA1
COMMISSIONING
RS < (-UBAT + US) / (-0.03) - RD

RS < 233 Ω, with -UBAT = -40 V
The maximum distance is calculated for a 0.4 mm wire (140 Ω/km) to be
233/140 = 1.66 km.
FOX61xLEDA1 71
COMMISSIONING
72 FOX61xLEDA1
OPERATION
7 Operation
This section describes the operation functions of the LEDA1 unit. You will
find the following information:
• Optical indicators found on the LEDA1 unit front (section "Unit optical
indicators" (page 73)).
• Diagnostic loops at LEDA1 front ports (section "Loops" (page 75)).
• Maintenance functions for ports and conference participants (section
"Line states" (page 76)).
• Generic maintenance functions of the unit (section "Maintenance"
(page 78)).
Please note:
The operation functions described in this section assume a correctly config-
ured and operational LEDA1 unit.
7.1 Unit optical indicators
LEDs on the front of the LEDA1 unit are used to indicate to the user the
alarm status summary of the unit and of the network traffic signals.
XXXXx R1B
ANR_37900374
UNIT TRAFFIC
Figure 42: Fault indication LEDs on the LEDA1 unit
FOX61xLEDA1 73
OPERATION
Table 7: LED signalling on LEDA1

LED name Colour State Meaning
UNIT Red Failure Unit is not in service.
The unit is not able to provide the requested function due to
- equipment failure (total breakdown),
- mismatch of HW and SW.
Recovery from this error situation is done usually by replacement
of unit HW or ESW.
Green / Red Booting or Unit has not been taken into service yet or the unit has not been
(blinking 1 Hz) waiting provisioned.
Recovery from this situation is done by taking this unit into service
with FOXCST.
Green Running Unit is up and running, it is ready to provide the required service.
Off Failure System is not powered or outage of power supply on unit or outage
of LED.
TRAFFIC Red Failure One or more active traffic failures on the unit, independent of the
severity.
More detailed information is provided by FOXCST.
Off Normal Normal (error free) operation.
74 FOX61xLEDA1
OPERATION
7.2 Loops
The following diagnostic loops can be individually set for each of the 8 E&M
ports:
The front-to-front loop loops the voice signal and the E&M signalling
received at the front port back to the front port.
The loop is transparent, i.e. the forwarded voice signal and E&M signal-
ling towards the PBUS interface are the received signals from the front
port.
The back-to-back loop loops the voice signal and the E&M signalling
received from the network interface (P12 transport unit) back to the net-
work interface.
The loop is transparent, i.e. the forwarded voice signal and E&M signal-
ling towards the front port are the received signals from the network.
LEDA1
E&M
P-12
TDM
PBUS
Network
P12
transport
Back-to-Back Front-to-Front
Loop Loop
Figure 43: Diagnostic loops on the LEDA1 unit
Please note:
Active loops generate the MFA alarm (maintenance function active).
Please note:
On a port only one loop can be active at the same time.
Please note:
A front-to-front loop is only available if at least one cross connection of any
signal (interface or participant) on the LEDA1 unit is configured.
FOX61xLEDA1 75
OPERATION
7.3 Line states
The port and participant line state maintenance functions allow to take an
interface or a conference participant out of service or to insert a test signal
towards the front port or towards the conference.
The line state maintenance function provides the following parameters:
• In service:
This parameter restores the normal operating state of the front port or of
the conference participant.
• Out of service:
Take a front port or a conference participant out of service, i.e. replace
the voice signal by silence and the signalling by an AIS (abcd = 1111).
− Port maintenance:
This parameter can be used to simulate a failed path towards the front
port.
− Participant maintenance:
This parameter can be used to test the protection switching in a
shared protection ring (SPR) application due to a failed LEDA1 unit.
The conference is bypassed in the SPR.
Please note:
The line states of both the “to master” and the “to slave” participants must be
set to “out of service” to check the correct protection switching.
• Test signal insertion:
Replace the outgoing voice signal at the front port or a conference partici-
pants voice signal by a test signal. The signalling is replaced by the idle
pattern (abcd = 1101), i.e. the E and E’ signalling outputs are set to open.
− Port maintenance:
This parameter provides an easy way to check the connection from
the LEDA1 unit to a connected telephone set.
To insert a test signal towards the TDM network, a back-to-back loop
must be applied at the corresponding interface.
− Participant maintenance:
This parameter provides an easy way to check the connection from
the LEDA1 unit to any other conference participant.
In a point-to-multipoint application a test signal inserted at the ‘to mas-
ter’ participant is sent to all ‘local’ and the ‘to slave’ participants. A test
signal inserted at a ‘local’ or ‘to slave’ participant is sent to the ‘to mas-
ter’ participant.
In a multipoint-to-multipoint application a test signal inserted at any
participant is sent to all other participants.
When applying a maintenance function the following signals are sent
towards the front port or the conference and towards the PBUS:
76 FOX61xLEDA1
OPERATION
Table 8: Maintenance function signal replacement

Function Signal Towards front port or Towards PBUS
conference
Out of service Voice Silence 1111’1111
Signalling AIS AIS
Failure signal - TSF, TSD a
Insert test signal Voice Test signal sequence -
Signalling Idle (abcd = 1101) -
Failure signal - -
a. TSF and TSD are the FOX61x internal failure signals used to control the protection
switching
For a description of the test signal please refer to section "E&M interface
voice transport" (page 34).
For the location of the signal insertion points please refer to the figures in the
sections "E&M interface signalling transport" (page 47), "E&M interface voice
transport" (page 34), "Conference signalling transport" (page 50) and "Con-
ference voice transport" (page 36).
Please note:
Active maintenance functions generate the MFA alarm (maintenance func-
tion active).
Please note:
On a port or participant only one maintenance functions can be active at the
same time.
FOX61xLEDA1 77
OPERATION
7.4 Maintenance
7.4.1 Inventory data

It is possible to read inventory data from the LEDA1 unit via the FOXCST
with the following access point:
AP: /unit-x, Main - Inventory.
7.4.2 Unit ESW download

It is possible to update the embedded software (ESW) of the LEDA1 unit via
software download.
Please refer to "1KHW002466 FOXCST Operation" for the description of the
ESW download.
Please note:
The assignment of new embedded software restarts the LEDA1 unit.
Nevertheless the traffic functions of the LEDA1 unit are not affected.
7.4.3 ESW upgrade with EQP

When upgrading the ESW on 1:1 equipment protected LEDA1 units, care
must be taken concerning which unit will finally be the active unit. At the end
of the upgrade procedure the working unit shall be the active unit.
It is assumed that the working unit is plugged in slot 17 and the protecting
unit is plugged in slot 18 of the FOX subrack.
ESW upgrade procedure The following procedure provides the upgrade process without changing the
active unit.
Isolate the working unit Proceed as follows:

1. Isolate the working LEDA1 unit:
 AP: /unit-17, Status – EQP.
 Execute the “Isolate Unit” command.
 The working LEDA1 unit is isolated, i.e. it will not perform a protection
switchover.
ESW download and start Proceed as follows:

1. Download the new ESW file to the working LEDA1 unit:
 Menu NE - Software Download….
 Click on the table row with ID “unit-17”.
 Execute the “Configure...” command.
2. In the “Software download settings” dialogue configure the following
items:
 Select the software to be downloaded from the software selection
box.
 Set the Software Installation = Manual Start.
 Tick the “Delete unused software” box.
 Execute the “OK” command.
78 FOX61xLEDA1
OPERATION
3. Download the new ESW file to the protecting LEDA1:

 Click on the table row with ID “unit-18”.
 Execute the “Configure...” command.
4. In the “Software download settings” dialogue configure the following
items:
 Select the software to be downloaded from the software selection
box.
 Set the Software Installation = Manual Start.
 Tick the “Delete unused software” box.
 Execute the “OK” command.
5. In the “NE Software Download” dialogue execute the “Download and
Start” command.
 The new ESW is downloaded and becomes active on the working
and the protecting units.
 The new ESW is active on the working and the protecting LEDA1 units.
The working LEDA1 unit in slot 17 remains the active unit.
Join the working unit Proceed as follows:

1. Join the working LEDA1 unit:
 AP: /unit-17, Status – EQP.
 Execute the “Join Unit” command.
 The working LEDA1 unit is able again to perform a protection switchover.
End of instruction
FOX61xLEDA1 79
OPERATION
80 FOX61xLEDA1
FOXCST REFERENCE
8 FOXCST reference
This section gives a complete reference of the managed objects, properties,
and commands of the LEDA1 service unit as far as these are not covered in
the generic descriptions in refer to "1KHW002466 FOXCST Operation".
In this section, you will find the following information:
• An introduction (section "Introduction" (page 81)),
• Unit management commands and parameters (section "AP: / unit-x:
LEDA1" (page 83)),
• Conference management commands and parameters (section "AP: / unit-
x / conf-z" (page 89)),
• Conference participants management commands and parameters (sec-
tion "AP: / unit-x / conf-z / part-a" (page 90)),
• Voice and signalling port commands and parameters (section "AP: / unit-
x / port-y" (page 99)).
For a description on how to configure and bring into operation the LEDA1
unit and its main functions, please refer to section "Commissioning"
(page 61).
8.1 Introduction
Below, you will find a detailed description of all the configuration parameters
and operations belonging to the managed objects model (MOM) for the
LEDA1 service unit.
The Figure 44 shows the access point (AP) tree for the LEDA1 unit with its
managed objects.
<ap >
FOX61x
0...20 <ap >

unit-x: LEDA1
0...10 <ap>
conf-z
2 ...17 <ap>
part-a
8 <ap>
port-y
Figure 44: MOM (managed object model) of the LEDA1 unit
With these managed objects (MOs) the following functions are covered:
FOX61xLEDA1 81
FOXCST REFERENCE
Table 9: Managed objects (MOs) for LEDA1

MO Description of the management functions
unit-x: LEDA1 Rxx Restart of the unit, management of the unit ESW, labelling,
(leda1_r2b) indication of equipment status, read of inventory data, access
to logbooks. Configuration of unit parameters and equipment
protection parameters, creating or deleting of voice confer-
ences.
The detailed properties are described in "AP: / unit-x: LEDA1"
(page 83).
conf-z Management of a voice conference. Creating or deleting of
conference participants.
The detailed properties are described in "AP: / unit-x / conf-z"
(page 89)
part-a Management of a participant of a voice conference. Parame-
ters as e.g. participant role, CAS handling, maintenance func-
tions.
The detailed properties are described in "AP: / unit-x / conf-z /
part-a" (page 90)
port-y Management of the voice and E&M signalling port related func-
tions, like the level configuration, signalling handling and main-
tenance functions.
The detailed properties are described in "AP: / unit-x / port-y"
(page 99)
For each of the managed objects, properties and commands, the GUI “Tree
Views” are given.
This reference section comprises the management functions:
• Overview,
• Main,
• Configuration,
• Fault Management,
• Performance Management, and
• Status.
Most of the APs only offer a part of the management functions listed above.
The order of appearance of the management function descriptions is in
accordance with the APs in the FOXCST AP tree and the availability of the
management functions of each AP.
In the tables of the sections below, the parameter default values for proper-
ties are underlined.
Please note:
For better legibility of numbers in this user guide, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter
entry fields of the FOXCST, these inverted commas must not be entered.
Instead, the numbers are entered without these inverted commas (e.g.
40000).
Please note:
Screenshots presented in this reference are examples and show configura-
tions or data that may not correspond to the view you see when managing
your FOX61x equipment.
82 FOX61xLEDA1
FOXCST REFERENCE
8.2 AP: / unit-x: LEDA1
8.2.1 AP: / unit-x, Overview
For a description of the

− “Overview - Alarms”, and
− “Overview - Cross Connections”
management functions, please refer to "1KHW002466 FOXCST Operation".
8.2.2 AP: / unit-x, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
8.2.3 AP: / unit-x, Configuration

8.2.3.1 AP: / unit-x, Configuration - Conferencing
“Create Voice Conference” and “Delete Conference” dialogues:
Table 10: AP: / unit-x, Configuration - Conferencing

Operation Name Parameter Name Range Description / Details
Create Voice Con- Open the dialogue to create a voice con-
ference… ference.
FOX61xLEDA1 83
FOXCST REFERENCE
Table 10: AP: / unit-x, Configuration - Conferencing (continued)

Create Voice Con- Index 0 … 255 Select the conference index number.
ference 0 is a reserved value used for the auto-
assignment of a conference index: The
auto-assigned index is the lowest availa-
ble index number.
In the FOXCST the default value is the
autoassigned index number.
Number Of Partici- 0 … 3 …17 Number of participants initially assigned
pants to the voice conference.
Note that the total number of participants
per LEDA1 unit is limited to 32.
Type P2MP The conference type can be configured to
MP2MP point-to-multipoint (P2MP) or multipoint-
to-multipoint (MP2MP) in linear or star
network applications.
Please refer to sections "Conference sig-
nalling transport" (page 50) and "Confer-
ence voice transport" (page 36) for a
description of the voice and signalling
transport in the point-to-multipoint and
multipoint-to-multipoint applications.
Delete Confer- Open the dialogue to delete a confer-
ence… ence.
Delete Conference Conference All Delete all conferences.
conf-1 … conf-n Select the conference to be deleted.
Squelch Level Low Set the squelch level for all conference
Medium participants of all conferences on the
LEDA1 unit.
High For further information please refer to
section "Conference voice transport"
(page 36).
8.2.3.2 AP: / unit-x, Configuration - EQP
“Create EQP Group” and “Delete EQP Group” dialogues:
84 FOX61xLEDA1
FOXCST REFERENCE
Table 11: AP: / unit-x, Configuration - EQP

Create EQP Open the dialogue for the creation of an equip-
Group ... ment protection (EQP) group.
A unit must be in the unassigned state to be
selectable as a protecting unit.
EQP Group Crea- Group Type 1:1 Type of the EQP group.
tion
Working Unit /unit-x MO address of the working unit, e.g. /unit-17.
In the FOXCST the working unit MO address is
read-only.
Protecting Unit - List of the MO addresses of all HW compatible
/unit-y units which are not assigned, e.g. /unit-18.
Default is no unit selected.
Check Address Check the MO address of the working unit.
The command is disabled in the FOXCST since
the MO address of the working unit is provided
by the network element.
Delete EQP Group Delete an existing protection group.
Traffic on the protecting unit will be interrupted
and services will be re-established on the work-
ing unit.
The protecting unit will become unassigned.
Please note:
With equipment protection of a LEDA1 unit it is only possible to protect the
conferences on the unit.
→ Equipment connected to user ports can not be protected.
8.2.4 AP: / unit-x, Fault Management

For the a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
The following table lists the fault causes of the current AP.
Table 12: AP: / unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
SWM Software Mismatch Equipment  Minor The running ESW does not match the
Alarm assigned ESW.
SSWNA Scheduled Software Equipment  Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to the
unit.
SWIN Software Incompatible Equipment  Major The running ESW is not compatible with
With Network Element Alarm the version required by the NE type or
version.
PRC PBUS Resource Con- Processing  Major Unit has been plugged into a slot which
flict Error Alarm conflicts with another unit, e.g. when
using an outdated ESW on an ISDN-BA
linecard.
FOX61xLEDA1 85
FOXCST REFERENCE
Table 12: AP: / unit-x, Fault Management (continued)

Affecting Severity
HWIC Hardware Incompatible Equipment  Major The plugged HW is not compatible with
With Configuration Alarm the unit configuration HW stored in the
database. You may need to change the
HW or re-create the configuration for the
unit.
SWIC Software Incompatible Equipment  Major The ESW running on the unit is not com-
With Configuration Alarm patible with the unit configuration stored
in the database. You may need to
upgrade, or downgrade the ESW, or re-
create the configuration with the cur-
rently running ESW.
GSW General Software Equipment  Major An ESW internal error has been detected
Alarm Alarm that might inhibit the ESW from running
correctly.
MFA Maintenance Function Communica-  Warning A maintenance function has been acti-
Active tion Alarm vated by the operator from the unit sta-
tus.
UNAV Unit Not Available Equipment  Critical The unit that is configured is either not
Alarm plugged or not recognized due to a fail-
ure.
NSW No Application Soft- Equipment  Major There is no application ESW installed on
ware Alarm the unit, or the application ESW has not
yet finished its boot process.
UNAS Unit Not Assigned Equipment  Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, execute
the “Assign” command in the “Main”
function of the unit.
UIC Unit Incompatible Equipment  Major The inserted unit is not compatible with
Alarm the assigned unit.
PWRSVE Battery Power Saving Equipment  Critical Power saving is active on the unit, i.e. it
Alarm is kept in the “reset” state during battery
power backup.
EQM Equipment Malfunction Equipment  Critical The LEDA1 controller detects any anom-
Alarm alies on the unit, e.g. a voltage is miss-
ing, a chip does not respond, etc.
EQPUNV EQP Unit Not Available Equipment  Major The standby unit is not available, i.e. not
Alarm plugged in or has an equipment failure.
This alarm is available on the working
and the protecting unit of an EQP group.
EQPHWI EQP Hardware Incom- Equipment  Major The actual hardware is not compatible
patible With Configura- Alarm with the hardware of the protecting unit.
tion This alarm is available on the working
unit of an EQP group only.
EQPSWI EQP Software Incom- Equipment  Major The running software (ESW) is not com-
patible With Configura- Alarm patible with the software on the protect-
tion ing unit.
86 FOX61xLEDA1
FOXCST REFERENCE
Table 12: AP: / unit-x, Fault Management (continued)

Affecting Severity
EQPNPR EQP Group Not Pro- Equipment  Major The working or the protecting unit is not
tected Alarm available, i.e. not plugged in or has an
equipment failure.
EQPWUI EQP Working Unit Iso- Equipment  Major The working unit has been isolated with
lated Alarm the “Isolate Unit” status command.
No protection is available in this state.
EQPUNA EQP Working Unit Not Equipment  Major An automatic protection switch or a
Active Alarm "manual switch" or a "forced switch" to
the protecting unit has been done.
Please note:
Automatic, manual and forced protection switching is available from the
working to the protecting unit and vice versa.
→ Please refer to section "Equipment protection (EQP)" (page 57).
8.2.5 AP: / unit-x, Status
8.2.5.1 AP: / unit-x, Status - EQP
Table 13: AP: / unit-x, Status - EQP

EQP Group Manual Switch-Over  Indication that the standby unit, i.e. the working
Allowed or the protecting unit is operational and can take
over the service.
 Indication that the standby unit, i.e. the working
or the protecting unit is not operational due to a
failure or to isolation or that the database has not
been saved. A manual protection switching with
the “Manual Switch-Over” command is not possi-
ble.
FOX61xLEDA1 87
FOXCST REFERENCE
Table 13: AP: / unit-x, Status - EQP (continued)

EQP Group - Units Unit <MO address> MO address of the unit belonging to the EQP
Status group.
EQP Unit Mode Undefined Mode Mode of a unit in the EQP group.
Working Unit
Protecting Unit
Active  The unit is active (operational).
 The unit is standby (not operational).
Failure  The unit has detected failure(s).

Substituted  The working unit has been substituted by the
 protecting unit.
Isolated  The working unit has been isolated with the “Iso-
 late Unit” command.
HW Compatible  The working unit is hardware compatible with the

 protecting unit in the EQP group.
Please refer to section "EQP prerequisites"
(page 58).
SW Compatible  The working unit is embedded software compati-
 ble with the protecting unit in the EQP group.
Please refer to section "EQP prerequisites"
(page 58).
DB Saved  The configuration of the unit has been saved.

Manual Switch-Over Manual switch of the unit in the EQP group.
A switch over is performed only when the other
unit is error free and is not isolated and the data-
base has been saved.
Refer to the “Manual Switch-Over Allowed” prop-
erty above.
Note: The traffic will be interrupted for about 2 s.
Forced Switch-Over Forced switch of the unit in the EQP group.
A switch over is performed independent of the
error state of the other unit., but the unit must not
be isolated.
Note: The traffic will be interrupted for about 2 s.
Note: Traffic will remain interrupted if the active
unit is not operational.
Isolate Unit Isolate the working unit from the EQP group.
An isolated working unit will not perform any pro-
tection switch action. The protection switching
state of the unit is frozen.
Join Unit Join the isolated working unit to the EQP group,
i.e. remove the isolation.
88 FOX61xLEDA1
FOXCST REFERENCE
8.3 AP: / unit-x / conf-z
8.3.1 AP: / unit-x / conf-z, Overview

− “Overview - Alarms”, and
− “Overview - Cross Connections”
8.3.2 AP: / unit-x / conf-z, Main
8.3.2.1 AP: / unit-x / conf-z, Main - General

− “Main - General”
management function, please refer to "1KHW002466 FOXCST Operation".
8.3.3 AP: / unit-x / conf-z, Configuration
8.3.3.1 AP: / unit-x / conf-z, Configuration - General
“Create Participant” and “Delete Participant” dialogues:
Table 14: AP: / unit-x / conf-z, Configuration - General

Conference CAS  CAS of a conference can be set to on or off.
Please refer to section "Conference signal-
ling transport" (page 50) for a description of

this parameter.
Create Participant… Open the dialogue to add a participant to a

conference.
FOX61xLEDA1 89
FOXCST REFERENCE
Table 14: AP: / unit-x / conf-z, Configuration - General (continued)

Create Participant Index 0 … 255 Select the participant index number.
0 is a reserved value used for the auto-
assignment of a participant index: The auto-
assigned index is the lowest available index
number.
In the FOXCST the default value is the
autoassigned index number.
Delete Participant… Open the dialogue to delete a conference.
Delete Participant Participant All Delete all participants of a conference.
part-1 … part-n Select the participant of a conference to be
deleted.
8.4 AP: / unit-x / conf-z / part-a
8.4.1 AP: / unit-x / conf-z / part-a, Overview

− “Overview - Alarms”,
− “Overview - Cross Connections”, and
− “Overview - CTP”
8.4.2 AP: / unit-x / conf-z / part-a, Main
8.4.2.1 AP: / unit-x / conf-z / part-a, Main - General

90 FOX61xLEDA1
FOXCST REFERENCE
8.4.2.2 AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status
Table 15: AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status
Operational Status State Up Display of the IETF operational status of the par-
Down ticipant.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.4.3 P: / unit-x / conf-z / part-a, Configuration
8.4.3.1 AP: / unit-x / conf-z / part-a, Configuration - General
Table 16: AP: / unit-x / conf-z / part-a, Configuration - General

Participant CAS  CAS of a participant can be enabled or disa-
bled.
Please refer to section "Conference signal-

this parameter.
Squelch  The squelch parameter can be enabled or
disabled.
Note that the squelch level is configured on

the unit layer for all participants.
Please refer to section "Conference voice
transport" (page 36) for a description of the
squelch parameter.
FOX61xLEDA1 91
FOXCST REFERENCE
Table 16: AP: / unit-x / conf-z / part-a, Configuration - General (contin-

Input Gain -9 … 0 dB, The participants’ voice input and output sig-
step 3 nal level can be attenuated.
Output Gain -9 … 0 dB, The attenuation can be helpful in the case of
step 3 reflected signals coming from user terminals
without correct line termination where it pre-
vents ringing.
Please refer to section "Conference voice
transport" (page 36) for a description of this
parameter.
Role Local In the point-to-multipoint and multipoint-to-
multipoint linear network applications the
conferences used in the different network
elements (NE) have local connections, a con-
To Master
nection towards the master NE head end and
a connection towards the slave NE tail end.
The connection role of a participant must be
To Slave configured according to the NE type.
Please refer to section "Conference cross
connections" (page 54) for a description of
the different NE types’ connections.
92 FOX61xLEDA1
FOXCST REFERENCE
8.4.3.2 AP: / unit-x / conf-z / part-a, Configuration - CTP
Table 17: AP: / unit-x / conf-z / part-a, Configuration - CTP

CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is
P0_nc, i.e. n x 64 kbit/s.
The layer rate property of a LEDA1 conference
participant is fixed to P0_nc.
P12 Layer rate of the connection termination point is
P12, i.e. 2048 kbit/s.
n 0 … 2 characters Number of timeslots in case of P0_nc. The pos-
sible range is from 1 to 32.
The number of time slots of a LEDA1 conference
participant is fixed to 1.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDA1 conference
participant is empty.
Connected To Connection Index 0 … 65‘535 Connection index.
CTPs
Local Role z-End Local role for this connection.
a-End Working A connection is always established between an
a-end and the z-end.
a-End Protecting
For further information refer to FOX61x TDM
Services Manual.
Remote CTP MO Address Managed object address of the CTP (connec-
tion termination point) where the LEDA1 confer-
ence participant is connected to, e.g. /unit-20/
port-8/chan-1.
Remote Role z-End Remote role for this connection.
a-End Working A connection is always established between an
a-end and the z-end.
a-End Protecting
For further information refer to FOX61x TDM
Services Manual.
Directionality Bidirectional Directionality of the connection.
Unidirectional
FOX61xLEDA1 93
FOXCST REFERENCE
Table 17: AP: / unit-x / conf-z / part-a, Configuration - CTP (contin-

z-End Configuration Revertive Protection  Enable revertive protection switching.
Switching The z-End will preferably select the working a-
End.

Note that the shared protection ring (SPR) appli-
cation requires the protection type to be rever-
tive.
CAS AIS Supervi-  Use CAS AIS as protection switching criterion.
sion The CAS AIS supervision can be disabled in the
shared protection ring application to prevent an

alarm during normal operation, where the closed
protection ring can have an AIS in the CAS.
Switch-Over Log-  Enable the logging of the protection switch-over
ging events.
The events are logged in the units event log-

book.
8.4.4 AP: / unit-x / conf-z / part-a, Fault Management

Table 18: AP: / unit-x / conf-z / part-a, Fault Management

Affecting Severity
Active tion Alarm vated by the operator from the partici-
pant status.
TSF Trail Signal Failure Communica-  Major Trail signal fail (TSF) from the P12 trans-
tion Alarm port unit is active, or
CAS AIS active (only available if CAS is
enabled).
In a protected connection the working
AND the protecting path have failed.
RTSF Redundant Trail Signal Communica-  Minor Trail signal fail (TSF) from the P12 trans-
Failure tion Alarm port unit is active, or
enabled).
OR the protecting path has failed.
In an unprotected connection this fault
cause is not applicable.
94 FOX61xLEDA1
FOXCST REFERENCE
Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.
8.4.5 AP: / unit-x / conf-z / part-a, Performance Management

For the a description of the general aspects of the performance management
(PM) functions, please refer to "1KHW002466 FOXCST Operation".
The PM parameters are presented in different groups. The following counter
group is available for the LEDA1 conference participants:
• “Protection” group, see section "AP: / unit-x / conf-z / part-a, Performance
Management - Protection" (page 95),
The following counter intervals are available:
Table 19: PM counter interval availability

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.4.5.1 AP: / unit-x / conf-z / part-a, Performance Management - Protection
Table 20: PM group: Protection

PM parameter Description
Switch-Over The protection switch-over count gives information
about the number and distribution of protection
switching events.
FOX61xLEDA1 95
FOXCST REFERENCE
8.4.6 AP: / unit-x / conf-z / part-a, Status

8.4.6.1 AP: / unit-x / conf-z / part-a, Status - General
Table 21: AP: / unit-x / conf-z / part-a, Status - General

Signalling Received CAS, 0000 … 1111 Signalling bits abcd received from the PBUS.
abcd With CAS disabled all signalling bits are set to ‘1’
(CAS AIS).
Transmitted CAS, 0000 … 1111 Signalling bits abcd sent towards the PBUS.
abcd With CAS disabled all signalling bits are set to ‘1’
(CAS AIS).
8.4.6.2 AP: / unit-x / conf-z / part-a, Status - Maintenance
Table 22: AP: / unit-x / conf-z / part-a, Status - Maintenance

Line Status Line Status In Service Restore the normal operating state of the partici-
pant.
Test Signal Insertion Insert a test signal towards the participants con-
ference.
For more information refer to section "Line
states" (page 76).
Out Of Service Insert a silence and CAS AIS towards the partici-
pants conference.
states" (page 76).
96 FOX61xLEDA1
FOXCST REFERENCE
8.4.6.3 AP: / unit-x / conf-z / part-a, Status - CTP
Table 23: AP: / unit-x / conf-z / part-a, Status - CTP

Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0 signal is
connected to, e.g. /unit-20/port-1/chan-1.
Working Trail, Sta- OK No failure on the received signal.
tus
SF Signal Fail status on the received signal.
CAS AIS CAS AIS status on the received signal.
This status is only available if CAS AIS supervi-
sion is enabled.
SD Signal Degraded status on the received signal.
Not Available The status of the received signal is not available,
e.g. when the CTPs role is a-end in a unidirec-
tional connection.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Protecting Trail, OK No failure on the received signal.
Status
sion is enabled.
tional connection.
Active Trail Working The trail from the a-end working remote CTP has
been selected.
Protecting The trail from the a-end protecting remote CTP
has been selected.
Not Available There is no active trail.
FOX61xLEDA1 97
FOXCST REFERENCE
Table 23: AP: / unit-x / conf-z / part-a, Status - CTP (continued)

External Request Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the a-end
working remote CTP.
Force Protecting Force the selector to use the trail from the a-end
protecting remote CTP.
Manual Working Prefer the trail from the a-end working remote
CTP. Use this trail only if the fault status is not
worse than the fault status of the protecting trail.
Manual Protecting Prefer the trail from the a-end protecting remote
worse than the fault status of the working trail.
98 FOX61xLEDA1
FOXCST REFERENCE
8.5 AP: / unit-x / port-y
8.5.1 AP: / unit-x / port-y, Overview

− “Overview - Alarms”,
− “Overview - Cross Connections”, and
− “Overview - CTP”
8.5.2 AP: / unit-x / port-y, Main
8.5.2.1 AP: / unit-x / port-y, Main - General

8.5.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status
Table 24: AP: / unit-x / port-y, Main - Admin And Oper Status
Administrative Sta- State Up Set the IETF administrative status of the port.
tus
Down
Operational Status State Up Display of the IETF operational status of the port.
Down
Testing
Unknown
Dormant
Not Present
Lower Layer Down
FOX61xLEDA1 99
FOXCST REFERENCE
8.5.3 AP: / unit-x / port-y, Configuration

8.5.3.1 AP: / unit-x / port-y, Configuration - General
Table 25: AP: / unit-x / port-y, Configuration - General

Voice Interface Type 2-Wire The interface type of user port can be config-
4-Wire ured to 2-wire or 4-wire operation.
In the 2-wire operation the front connector
pins a2 and b2 are used as bidirectional
inputs and outputs.
In the 4-wire operation the pins a1 and b1 are
used as outputs and the pins a2 and b2 are
used as inputs.
Input Level 2-Wire mode: The relative input signal level is related to the
-infinity … 0.0 … infinity dBr, zero reference point (0 dBr).
step 0.5 Valid levels are:
4-Wire mode: 2-wire: -12.5 dBr … +9.5 dBr
-infinity … -3.5 … infinity dBr, 4-wire: -16.0 dBr … +9.5 dBr
step 0.5 Please refer to section "E&M interface voice
parameter.
Output Level 2-Wire mode: The relative output signal level is related to
-20.0 … -6.5 … -1.0 dBr, the zero reference point (0 dBr).
step 0.5 Valid levels are:
4-Wire mode: 2-wire: -20.0 dBr … -1.0 dBr
-16.5 … -3.0 … 7.0 dBr, 4-wire: -16.5 dBr … +7.0 dBr
step 0.5 Please refer to section "E&M interface voice
parameter.
Echo Cancellation  The line echo canceller can be enabled or
disabled. The echo canceller is mainly used
in the 2-wire interface mode.

Please refer to section "Line echo cancella-
tion" (page 34) for a description of this
parameter.
100 FOX61xLEDA1
FOXCST REFERENCE
Table 25: AP: / unit-x / port-y, Configuration - General (continued)

Signalling CAS  CAS of a user port can be enabled or disa-
bled.
Please refer to section "E&M interface signal-

this parameter.
Signalling Mode Transparent Please refer to section "E&M interface signal-
Incoming ling modes of operation" (page 48) for a
description of this parameter.
Outgoing
M Signalling  The M-signalling, i.e. the mapping of the M
Inverted and M’ signal states to the a and b signalling
bit state can be configured to inverted or non-
 inverted.
Please refer to section "E&M signalling inter-
face types" (page 41) for a description of this
parameter.
8.5.3.2 AP: / unit-x / port-y, Configuration - CTP
Table 26: AP: / unit-x / port-y, Configuration - CTP

CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is
P0_nc, i.e. n x 64 kbit/s.
The layer rate property of a LEDA1 port is fixed
to P0_nc.
P12 Layer rate of the connection termination point is
P12, i.e. 2048 kbit/s.
n 0 … 2 characters Number of timeslots in case of P0_nc. The pos-
sible range is from 1 to 32.
The number of time slots of a LEDA1 port is
fixed to 1.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDA1 port is
empty.
FOX61xLEDA1 101
FOXCST REFERENCE
Table 26: AP: / unit-x / port-y, Configuration - CTP (continued)

Connected to CTPs Remote CTP <MO address> Address string of a connections remote end.
Without a connection the parameter is empty
Connection Index 0 … 65“535 Index of a connection assigned to the port. With-
out a connection the parameter is empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The port is the ending point of a connection.
Please refer to "1KHW002467 FOX61x TDM
Services"
a-End Working The port is the working starting point of a pro-
tected or unprotected connection.
a-End Protecting The port is the protecting starting point of a pro-
tected connection.
Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
Please refer to "1KHW002467 FOX61x TDM
Services"
a-End Working The CTP at the connections remote end is the
working starting point of a protected or unpro-
tected connection.
a-End Protecting The CTP at the connections remote end is the
protecting starting point of a protected connec-
tion.
z-End Configuration Revertive Protection  Enable revertive protection switching.
Switching  The z-End will preferably select the working a-
End.
Note that the shared protection ring (SPR) appli-
cation requires the protection type to be rever-
tive.
CAS AIS Supervi-  Use CAS AIS as protection switching criterion.
sion  The CAS AIS supervision can be disabled in the
shared protection ring application to prevent an
alarm during normal operation, where the closed
protection ring can have an AIS in the CAS.
Switch-Over Log-  Enable the logging of the protection switch-over
ging  events.
The events are logged in the units event log-
book.
Please note:
The z-End of a protected connection shows two entries in the “Connected to
CTPs” table, one for the working and one for the protecting path.
8.5.4 AP: / unit-x / port-y, Fault Management

102 FOX61xLEDA1
FOXCST REFERENCE

Table 27: AP: / unit-x / port-y, Fault Management

Affecting Severity
Active tion Alarm vated by the operator from the port sta-
tus.
TSF Trail Signal Failure Communica-  Major Trail signal fail (TSF) from the P12 trans-
tion Alarm port unit is active, or
enabled).
AND the protecting path have failed.
RTSF Redundant Trail Signal Communica-  Minor Trail signal fail (TSF) from the P12 trans-
Failure tion Alarm port unit is active, or
enabled).
OR the protecting path has failed.
In an unprotected connection this fault
cause is not applicable.
Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.
8.5.5 AP: / unit-x / port-y, Performance Management

For the a description of the general aspects of the performance management
(PM) functions, please refer to "1KHW002466 FOXCST Operation".
The PM parameters are presented in different groups. The following counter
group is available for the LEDA1 ports:
• “Protection” group, see section "AP: / unit-x / port-y, Performance Man-
agement - Protection" (page 104),
The following counter intervals are available:
Table 28: PM counter interval availability

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
FOX61xLEDA1 103
FOXCST REFERENCE
8.5.5.1 AP: / unit-x / port-y, Performance Management - Protection
Table 29: PM group: Protection

PM parameter Description
Switch-Over The protection switch-over count gives information
about the number and distribution of protection
switching events.
8.5.6 AP: / unit-x / port-y, Status

8.5.6.1 AP: / unit-x / port-y, Status - General
Table 30: AP: / unit-x / port-y, Status - General

Signalling Received CAS, 0000 … 1111 Signalling bits abcd received from the PBUS.
abcd With CAS enabled the a and b bits control the E
and E’ outputs, the c and d bits are only used for
the CAS AIS monitoring.
With CAS disabled all signalling bits are set to ‘1’
(CAS AIS).
E Outputs, E1 Open The E output is left open.
Note that E is designated as E1 in the FOXCST.
Gnd The E output is connected to ground.
Note that E is designated as E1 in the FOXCST.
E Outputs, E2 Open The E’ output is left open.
Note that E’ is designated as E2 in the FOXCST.
Gnd The E’ output is connected to ground.
Note that E’ is designated as E2 in the FOXCST.
M Inputs, M1 -UBat The M input voltage is interpreted as connected
to the battery voltage or as open contact.
Note that M is designated as M1 in the FOXCST.
Gnd The M input voltage is interpreted as connected
to ground.
Note that M is designated as M1 in the FOXCST.
104 FOX61xLEDA1
FOXCST REFERENCE
Table 30: AP: / unit-x / port-y, Status - General (continued)

M Inputs, M2 -UBat The M’ input voltage is interpreted as connected
to the battery voltage or as open contact.
Note that M’ is designated as M2 in the
FOXCST.
Gnd The M’ input voltage is interpreted as connected
to ground.
Note that M’ is designated as M2 in the
FOXCST.
Transmitted CAS 0000 … 1111 Signalling bits abcd sent towards the PBUS.
With CAS enabled the a and b bits are controlled
by the M and M’ inputs, the c and d bits are fixed
to ‘01’.
With CAS disabled all signalling bits are set to ‘1’
(CAS AIS).
8.5.6.2 AP: / unit-x / port-y, Status - Maintenance
Table 31: AP: / unit-x / port-y, Status - Maintenance

Line Status Line Status In Service Restore the normal operating state of the
front port.
Test Signal Insertion Insert a test signal towards the front port.
states" (page 76).
Out Of Service Insert a silence and CAS AIS towards the
front port.
states" (page 76).
Loop Status Loop Status None Deactivate any loop.
Back-To-Back Loop Activate the back-to-back loop.
For more information refer to section "Loops"
(page 75).
Front-To-Front Loop Activate the front-to-front loop.
For more information refer to section "Loops"
(page 75).
FOX61xLEDA1 105
FOXCST REFERENCE
8.5.6.3 AP: / unit-x / port-y, Status - CTP
Table 32: AP: / unit-x / port-y, Status - CTP

Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Working Trail, Sta- OK No failure on the received signal.
tus
sion is enabled.
tional connection or when the CTP has no con-
nection.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Protecting Trail, OK No failure on the received signal.
Status
sion is enabled.
tional connection, or when the CTP is unpro-
tected or has no connection.
Active Trail Working The trail from the a-end working remote CTP has
been selected.
Protecting The trail from the a-end protecting remote CTP
has been selected.
Not Available There is no active trail, i.e. the CTP has no con-
nection.
106 FOX61xLEDA1
FOXCST REFERENCE
Table 32: AP: / unit-x / port-y, Status - CTP (continued)

External Request Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the a-end
working remote CTP.
Force Protecting Force the selector to use the trail from the a-end
protecting remote CTP.
Manual Working Prefer the trail from the a-end working remote
worse than the fault status of the protecting trail.
Manual Protecting Prefer the trail from the a-end protecting remote
worse than the fault status of the working trail.
FOX61xLEDA1 107
FOXCST REFERENCE
108 FOX61xLEDA1
ANNEX
9 Annex
9.1 Associated documents
1KHW028514 FOX61x Abbreviations and Terms

1KHW002497 FOX61x Precautions and Safety
1KHW002459 FOX61x Release Notes
1KHW002460 FOX61x Product Features and Characteristics
1KHW002461 FOX615 Installation
1KHW002462 FOX612 Installation
1KHW002463 FOX61x Lightning Protection
1KHW002464 FOX61x System Description
1KHW002465 FOXCST Installation
1KHW002466 FOXCST Operation
1KHW002467 FOX61x TDM Services
1KHW002468 FOX61x Ethernet Services
1KHW002469 FOX61x CESM1
1KHW002470 FOX61x LESU1
1KHW002471 FOX61x ETOP1
1KHW002472 FOX61x ELET1
1KHW002473 FOX61x LEDE1
1KHW002474 FOX61x DATI1
1KHW002475 FOX61x EPSI1
1KHW002476 FOX61x SAMO1
1KHW002477 FOX61x SAMO2
1KHW002478 FOX61x LEDS1
1KHW002480 FOX61x LEXI1
1KHW002481 FOX61x LECO1
1KHW002482 FOX61x Electrical Cables
FOX61xLEDA1 109
ANNEX
110 FOX61xLEDA1
Contact us
1KHW002480 © Copyright 2012 ABB. All rights reserved.

ABB Switzerland Ltd
Power Systems
Bruggerstrasse 72
CH-5400 Baden
Tel. +41 58 585 77 37
Fax +41 58 585 55 77
E-mail: utility.communication@ch.abb.com
www.abb.com/utilitycommunication

1KHW002479 FOX61x LEDA1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1KHW002479 FOX61x LEDA1

Uploaded by

Copyright:

Available Formats

ABB Power Systems

Release History: Release 1: December 2012

Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

Blank pages: Any blank page present is to accommodate double-sided printing.

Document No.: 1KHW002479

ABB Switzerland Ltd

3 Functions and specifications 15

Figure 1: Terminal equipment connected in a star network, with conference 13

Table 1: Electrical interfaces and circuit categories 11

1.2 Symbols and notations

This User Manual uses the following symbols:

NOTICE Non-observance could result in equipment damage.

Risk of operating trouble!

1.3 Interfaces and circuit categories

Table 1: Electrical interfaces and circuit categories

1.4 Document history

Table 2: Document history

LEDA1 TDM E&M

P12 transport unit

Figure 1: Terminal equipment connected in a star network, with confer-

LEDA1 has an access capacity of 4 x 2 Mbit/s towards the FOX61x internal

A more economical use of the network resources can be achieved by the

2.2 Unit view

Figure 2: LEDA1 unit view

3 Functions and specifications

3.1 Feature licences

This unit is not subject to feature licences.

3.2 E&M interface

NOTICE Overvoltage. Risk of equipment damage!

Table 3: E&M interface functions and specifications

Table 3: E&M interface functions and specifications (continued)

Signalling interfaces E&M Swiss PTT 692.01/S, 05/1989 r1a

Table 3: E&M interface functions and specifications (continued)

Table 4: Conference functions and specifications

Table 5: General functions and specifications

PBUS access 4 x P12 r1a

Power consumption r1a

Mechanical parameters r1a

Table 5: General functions and specifications (continued)

Emission refer to "1KHW002460 FOX61x Product Features r1a

4.2 Slots and deployment scenarios for the LEDA1 unit

The LEDA1 unit uses one slot in the FOX61x subrack.

Figure 3: FOX615 subrack with 19 LEDA1 units and 1 LEDE1 unit

The example above shows a FOX615 subrack equipped with 19 LEDA1

Figure 4: FOX612 subrack with 6 LEDA1 units and 1 LEDE1 unit

4.4 Overvoltage protection

External primary protection (230 V gas discharge tubes) is mandatory for

4.5.1 FOX61x units

4.5.2 FOX51x units

4.5.3 Previous ESW revisions

4.6 Connections and cables

4.6.1 Front connector of the LEDA1 unit

Voice port 5 a1 19 M’ Signalling port 5

Figure 5: Pin-out of the LEDA1 front connector, front view

4.6.2 Cable 32 pairs, DIN to open end

4.6.3 Fixing the cables to the cable tray

5.1 Network applications

The main network applications with the LEDA1 unit are

5.1.1 Point-to-point (P2P)

Network element 1 Network element 2

P12 transport unit

Figure 8: Point-to-point application with LEDA1

5.1.2 Point-to-multipoint (P2MP)

Network element 1 Network element k Network element n