Supervision of the Subscriber and PBX Access Siemens

Supervision of the Subscriber and PBX

Access

Contents
1 EWSD Maintenance Concept for the Subscriber and PBX Access 3
2 Self Supervision and Alarming of the Subscriber and PBX Access 7
2.1 Supervision and Alarming of Analog Subscriber Lines 8
2.2 Supervision and Alarming of ISDN Subscriber Lines 10
2.3 Supervision and Alarming of Non ISDN PBX 12
2.4 Supervision and Alarming of ISDN PBX 14
3 Performance Monitoring of ISDN Subscriber Lines 18
4 Selected Commands 21
5 Exercise 25
6 Solution 29

SN2012EU07AL_01
1
 Siemens Supervision of the Subscriber and PBX Access

2 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

1 EWSD Maintenance Concept for the

Subscriber and PBX Access

SN2012EU07AL_01
3
 Siemens Supervision of the Subscriber and PBX Access

The EWSD maintenance measures for subscriber and PBX consider following
different access elements:

analog subscriber line and terminal

digital subscriber line (ISDN basic accesses BA) for connection of ISDN
subscribers

analog and digital PBX lines for connection of non ISDN PBX

digital PBX lines (ISDN primary rate accesses PA or ISDN basic accesses BA) for
connection of ISDN PBX
The EWSD measures for the detection, diagnosis and localization of faults in the
subscriber access are divided into self-supervision, performance monitoring and
testing:
Self-supervision has two functions: Firstly to monitor permanently the HW units DIU
and SLM, which connect subscriber and PBX lines. In case of a fault an alarm is
signaled on the SYPD. Secondly the availability of subscriber and PBX lines is
supervised. If the threshold values for non available subscriber or PBX lines is
exceeded (set by MML commands) a LINELOCKOUT alarm is signaled on the
SYPD.
The aim of performance monitoring is to provide detailed information about the
transmission quality. The information is based on fault statistics. Within the
performance monitoring the data already created by self-supervision are written into
individual files and can now be easily read out. The creation of these files and the
data collecting in these files is done by MML commands. Performance monitoring is
only used for digital subscriber or PBX lines.
Routine testing can be performed in addition to self-supervision and performance
monitoring. Here test routines are started at regular intervals, i.e. the test data are
entered once by MML-command and then automatically started by time schedules.
Routine tests detect faulty objects and also the reason for the failure. However, the
results of detailed physical measurements are not provided.
Demand testing is carried out, for example after a fault has been detected by a self-
supervision procedure or after routine testing in order to determine the physical
measurement parameters and from this the cause of the fault. Test jobs for demand
testing are performed by the system immediately. Demand testing can be carried out
by test equipment integrated in EWSD and started by MML commands, or by
external test equipment.

TIP
This chapter will only deal with the self supervision and performance monitoring of
subscribers and PBX. For routine and demand testing a specific training module is
offered.

4 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

EWSD Supervision, Performance Monitoring

and Testing of the Subscriber and PBX Access

Fig. 1

SN2012EU07AL_01
5
 Siemens Supervision of the Subscriber and PBX Access

6 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

2 Self Supervision and Alarming of the

Subscriber and PBX Access

SN2012EU07AL_01
7
 Siemens Supervision of the Subscriber and PBX Access

2.1 Supervision and Alarming of Analog Subscriber

Lines
Self supervision
All analog subscriber lines connected to DLU are monitored by the SLMA for:

External voltage
An external voltage can arise on a analog subscriber or PBX line as a result, for
example, of it coming into contact with a current-carrying wire. Such an external
voltage can trigger a connection event in the SLMA. The GP then starts the
connection setup process. If no dialing information is received while the dial tone is
being sent, then on expiry of the dial tone transmission time the GP will apply the
busy tone to the analog subscriber or PBX line. If the connection event continues
beyond the time that the busy tone is applied, the GP deduces from this that there
is a line fault.

Permanent
An external (AC) voltage can cause a permanent at a port. In order to detect
permanents, the SLMA compares the number of events at the port against a
threshold value. This threshold values specifies how many connection events may
occur at a port per second. If the threshold value is exceeded, the SLMA reports a
port fault to the GP.

Short circuit
The cause of a short circuit on a analog subscriber or PBX line can be, for
example, damage to the line. Like an external voltage, a short circuit can trigger a
connection event.

Crossed-wire condition
A crossed-wire condition may arise if the wires in a line have an insulation fault to
ground potential. If the SLMA detects a loop resistance greater than 4 kOhm
(threshold value for the indication of a loop open or closed) and less than 20 kOhm
(permissible crossed-wire condition), the SLMA deduces from this that there is a
line fault, and issues a report to the GP.

Short to ground
A short to ground can occur if the wires in a line have an insulation fault to ground
potential. When there is a short to ground, a current only flows in one wire of the
line. In the idle state, the SLMA will only detect a short to ground on the a-wire; in
the other line conditions (e.g. ringing, in-use state) it will detect them on the a-wire
and the b-wire. The SLMA will report a short to ground to the GP if it is sustained
on an individual wire of the line for at least 480 ms.

8 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

Fault handling and alarming:

If one of these faults is detected the GP/CP blocks this analog subscriber or PBX
line (NMNT). If a preset threshold (ENTR LINETHR:LNLOCKAL=) for disturbed lines
is exceeded the LED LINELOCKOUT is switched on at the SYPD. All disturbed
subscriber lines can be displayed by DISPLNLCKOUT:LNTYPE=SUB. If the GP
detects the end of a fault the transient line status changes automatically back to
IDLE.

Linelockout threshold for subscribers

(ENTR LINETHR: LNLOCKAL=)
is exceeded

DISP LNLCKOUT:
LNTYPE = SUB;
•external voltage
•permanent List of all disturbed
•short circuit subscribers
•crossed wire condition
•short to ground

Fig. 2

SN2012EU07AL_01
9
 Siemens Supervision of the Subscriber and PBX Access

2.2 Supervision and Alarming of ISDN Subscriber

Lines
Self supervision
The SLMD monitors a basic access at layers 1 and 2 for:

Activation faults
In the case of a basic access, call processing requires that layer 1 is activated.
The activation procedure for layer 1 covers the automatic setting of line
equalization and echo compensation in the SLMD transmission modules and in
the network termination (NT), plus synchronization of the NT with the line clock.
The SLMD uses timers to monitor every stage of the activation. If activation is not
completed within the permissible time, the SLMD sends a port fault report to the
GP. In the SLMD, the activation state which had been reached is stored. It is
possible to query how far the activation was successful by means of the command
STAT ILAYER1. In fault-free operation, the activation time for layer 1 is less than
300 ms.

Loss of synchronization
In order to maintain correct synchronization between the transmit and receive
modules of the SLMD and the NT during call processing, a synchronization word is
included in every frame transmitted between the SLMD and the NT. The SLMD
checks whether the frames received contain the synchronization word, and that it
is in the correct position within the frame. From any missing or misallocated
synchronization words, the SLMD detects a loss of synchronization. If the loss of
synchronization lasts longer than 2 seconds, the SLMD sends a port fault report to
the GP.

Overcurrent
An overcurrent on the subscriber line can arise as a result, for example, of a short
circuit, a ground fault, contact with a current carrying wire or from a faulty NT. To
protect against overcurrent, the SLMD limits the supply current to 50 mA. If current
limitation lasts more than 2 seconds, then the SLMD switches off the power
supply. This clears down any existing connections via the basic access. After 4
seconds, the SLMD switches the power supply on again. If current limitation again
lasts for 2 seconds, the SLMD reports the fault to the GP. At 16 second intervals
the SLMD then tests whether current limitation is still being applied. When the
supply current remains below 50 mA for the duration of the monitoring time, the
SLMD interprets this as the end of the fault, and reports it to
the GP. After a successful test activation, the GP puts the connection back into
operation again.

Overvoltage
An overvoltage on the subscriber line can arise as a result, for example, of
lightning effects or induction. The SLMD protection against overvoltage conforms
to ITU-T Recommendation K.20. Protection against voltages over 1000 V is
provided at the main distribution frame by gas-filled overvoltage arresters.

10 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

Loss of signal
When the input signal is lost, the signal level on the subscriber line drops. If the
signal level remains below a specified limit for a certain length of time, then
synchronization is also lost. The SLMD then reports a port fault to the GP.

Framing errors
The transmission quality for the 2 B and the D channel of a basic access is
monitored by the CRC12 method. If the bit error rate exceeds 10exp-3 the SLMD
reports a port fault to the GP.

Fault handling and alarming:

If one of these faults is detected the GP/CP blocks this ISDN subscriber line (NMNT).
A trial activation is performed at regular intervals (about 30-60 sec), to detect the end
of the fault. Between two trial activation the power is switched off. If the trial activation
is successful the transient line status changes automatically back to IDLE. If a preset
threshold (ENTR LINETHR:LNLOCKAL=) for disturbed lines (analog and ISDN are
counted together) is exceeded the LED LINELOCKOUT is switched on at the SYPD.
All disturbed subscriber lines can be displayed by DISPLNLCKOUT:LNTYPE=SUB.
For basic accesses with permanent layer1 activation, any failure is automatically
displayed at the BCT if the output suppression is deactivated.

Linelockout threshold for subscribers

NT (ENTR LINETHR: LNLOCKAL=)
NT is exceeded
NT
NT
NT
NT
DISP LNLCKOUT:
Activation faults LNTYPE = SUB;
loss of synchronization
loss of signal List of all disturbed
framing errors subscribers
overcurrent/overvoltage

Fig. 3

SN2012EU07AL_01
11
 Siemens Supervision of the Subscriber and PBX Access

2.3 Supervision and Alarming of Non ISDN PBX

Supervision and alarming of PBX without direct inward dialing DID
connected via a/b to DLU
These PBX lines are all connected to SLMA ports. The self supervision is
performed in the same way like for analog subscriber lines.
If the number of faulty PBX lines of a PBX exceeds the predefined threshold
(ENTR LINETHR:PGATHR=) a "LINELOCKOUT" alarm is signaled at the SYPD.
A list of all disturbed PBX lines can be reported by
DISPLNLCKOUT:LNTYPE=PBX.

Supervision and alarming of PBX with direct inward dialing DID connected
via a/b to DLU
Variant A:
PBX lines for calls originated in the PBX are connected to normal SLMA. The self
supervision works in the same way like for analog subscriber lines.
PBX lines for calls terminated in the PBX are connected to SLMA:DID. The self
supervision works in the same way like for analog subscriber lines. Additionally the
SLMA:DID monitors the presence of the idle voltage delivered by the PBX in idle
state of the line. The absence of the idle voltage is considered as a fault.
Variant C:
Incoming and outgoing PBX lines are connected to SLMA:DIOD. The self
supervision works in the same way like in the SLMA:DID.
Additionally the transmission quality of the PBX lines may be monitored by the
"killer trunk supervision method". Therefor the command ENTR PMCNTL is used
to define for a PBX the minimum average holding time of the calls
If the number of faulty PBX lines of a PBX exceeds the predefined threshold
(ENTR LINETHR:PGATHR=) a "LINELOCKOUT" alarm is signaled at the SYPD.
A list of all disturbed PBX lines can be reported by
DISPLNLCKOUT:LNTYPE=PBX.

Supervision and alarming of PBX with direct inward dialing DID connected
via PDC to DIU
Each PDC link offers 30 telephone channels with channel associated signaling
CAS in the time slot 16. The self supervision performed in the DIU is the same like
for PDC with trunks, i.e. PDC failures are treated according to the standard
alarming concept for PDC.
If the number of faulty PBX lines of a PBX exceeds the predefined threshold
(ENTR LINETHR:PGATHR=) a "LINELOCKOUT" alarm is signaled at the SYPD.
A list of all disturbed PBX lines can be reported by
DISPLNLCKOUT:LNTYPE=PBX.
Additionally the PBX lines can be monitored for extreme short average call
duration ("killer trunk supervision") and irregularities during connection set up and
clear down("MDII supervision"). The according thresholds can be administered
PBX individually by ENTR PMCNTL (according to ENTR TMCNTL for trunk
groups).

12 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

PBX without DID : connection via a/b

PBX with DID : connection via a/b

•Supervision like for analog subscribers
•List of disturbed PBX lines:
DISPLNLCKOUT:LNTYPE=PBX;
•Threshold for SYPD alarm:
ENTRLINETHR:PGATHR=...;

PBX with DID : connection via PDC

•Supervision like for PDC with trunks
LTG •List of disturbed PBX lines:
Digital non DISPLNLCKOUT:LNTYPE=PBX;
ISDN PBX PDC DIU
with
•Threshold for SYPD alarm:
CAS ENTRLINETHR:PGATHR=...;

Fig. 4

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

SN2012EU07AL_01
13
 Siemens Supervision of the Subscriber and PBX Access

2.4 Supervision and Alarming of ISDN PBX

Supervision and alarming of ISDN PBX connected via BA to DLU
The self supervision is carried out in the same way like for ISDN subscriber lines.
If the number of faulty PBX lines of a PBX exceeds the predefined threshold (ENTR
LINETHR:PGATHR=) a "LINELOCKOUT" alarm is signaled at the SYPD.
A list of all disturbed PBX lines can be reported by DISPLNLCKOUT:LNTYPE=PBX.

Supervision and alarming of ISDN PBX connected via PA to DIU

Self supervision
A primary rate access is connected to a digital interface unit (DIU) in the LTGB. The
self supervision for each PA offers the same functions like for PDC with trunks:

Loss of signal

Loss of pulse frame synchronization

Slip Frame

Alarm indication signal

D bit

Bit error

Code violations
Additionally the NT1 can send messages to the DIU concerning detected failures at
the interface to the PBX (S2M interface) or to the local switch (U2M interface). This
leads to specific alarm messages which enable the maintenance personnel to decide
whether a fault is located in the area covered by the network node or the ISDN PBX:

PA NT1 TO S2 LO SIGN LO SYNC
This PA PCM ALARM message is output in the following three cases:
NT1 at S2M has detected loss of pulse frame alignment
NT1 at S2M has detected loss of incoming PCM signal
NT1 at S2M has detected loss of CRC4 multiframe alignment
The fault is located in the section PBX ---> NT1. NT1 reports the fault to the DIU30
in the national Y2-bit of 4 consecutive service words (Y2-bit = 1000). If the fault
persists for longer than 1 minute, an error message is output.

PA NT1 TO U2 LO SIGN, SYNC BER
This PA PCM ALARM message is output in the following three cases:
NT1 at U2M has detected loss of pulse frame alignment
NT1 at U2M has detected loss of incoming PCM signal
NT1 at U2M has detected loss of CRC4 multiframe alignment
The fault is located in the section DIU ---> NT1. NT1 reports the fault to the DIU30
in the national Y2-bit of 4 consecutive service words (Y2-bit = 1110). If the fault
persists for longer than 1 minute, an error message is output.

14 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

PA LOSS OF NT1 POWER SUPPLY

Loss of power supply is signaled by the NT1 directly to the DIU by a brief internal
buffering of the power feed. The NT1 ceases to send signals after about 1 second.
This is used as the criterion for power failure.

PA NT1 TO U2 AIS
This alarm is raised when the NT1 receives AIS from the DIU or from intermediate
equipment at the U-interface. The fault is located in the section DIU ---> NT1. NT1
reports the fault to the DIU30 in the national Y2-bit of 4 consecutive service words
(Y2-bit = 1111). If the fault persists for longer than 1 minute, an error message is
output
Furthermore the PBX lines can be monitored for extreme short average call duration
("killer trunk supervision") and irregularities during connection set up and clear
down("MDII supervision"). The according thresholds can be administered PBX
individually by ENTR PMCNTL (according to ENTR TMCNTL for trunk groups).

U2M S2M
PBX

N
T
DIU
1
PA

Self supervision Alarm messages

in DIU: send back to DIU:
•loss of signal •loss of signal or
•loss of synchronization
synchronization at S2M
•slip •loss of signal or
•AIS synchronization
•D-bit at U2M
•bit error •AIS at U2M
•code violation •loss of power
•alarm responses
from the NT1

Fig. 5

SN2012EU07AL_01
15
 Siemens Supervision of the Subscriber and PBX Access

Fault handling
Fault detection in DIU/NT1

When the DIU detects itself a failure on the PDC used for a PA it sends a report to
the GP (standard concept of PDC supervision like it is used for PDC with trunks).

When the NT1 detects a failure on its S2M or U2M interfaces it send a message to
the DIU which reports this to the GP
Fault handling in the GP/CP
When the GP receives a report of a fault on the PDC link for a primary rate access, it:

clears down all the connections via the primary rate access’s PDC link in stages,
and blocks the ports against new seizure,

informs the CP of the failure (carrier failure alarm),

in the case of faults detected by the DIU it sends, insofar as is possible, a
malfunction report to the NT1 or to the ISDN PBX, as applicable,

passes a detailed fault report to the CP which generates a fault message
In the event of a fault, the GP blocks all the free ports on the PDC link 100 ms after
receiving the fault report. A fault which persists for more than 2 seconds leads to the
entire PDC link being taken out of service. The guard period of 2 seconds prevents
individual short-term disturbances on the PDC link from affecting call processing. Bit
errors are an exception to this. For bit errors, the PDC link is not taken out of service
until the number of bit errors occurring in two successive 4-second periods exceeds
36. The GP reports the exact reason for the fault to the CP after 60 seconds.
Fault monitoring overflow:
On a PDC link, the frequency of faults is also covered by the monitoring activities. For
this purpose, there is a fault counter in the GP for each PDC link. Every fault on a
PDC link which persists for more than 100 ms leads to the counter value being
incremented. When a counter overflow occurs, the GP takes the primary rate access
out of service. When the DIU determines that the fault on the PDC link has ended,
the GP is sent an end-of-fault report. After receiving the end-of-fault report, the GP
puts the PDC link into service again. If a PDC link has been taken out of service as a
result of a counter over-flow, then before it can be put back into service no new faults
must occur for a period of 10 minutes. The GP reports the end-of-fault on a PDC link
to the CP.

Alarming
If the number of faulty PBX lines of a PBX exceeds the predefined threshold (ENTR
LINETHR:PGATHR=) a "LINELOCKOUT" alarm is signaled at the SYPD.
A list of all disturbed PBX lines can be reported by DISP LNLCKOUT:LNTYPE=PBX.
TIP
Project specific there may be no "Maintenance/Service Alarm" at the SYPD in case of
failures on PDC used as primary rate access PA.

16 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

PBX
PA with
30 B and one D channel
Linelockout threshold
PA with (ENTR LINETHR: PGATHR=)
30 B and one D channel for PA - PBX lines
PA with is exceeded for one or more PBX
30 B and one D channel

DISP LNLCKOUT:
LNTYPE = PBX;
PDC faults detected by:
•Standard supervision
functions for PDC in DIU List of all disturbed
•Fault messages PBX lines
from the NT1

Fig. 6

SN2012EU07AL_01
17
 Siemens Supervision of the Subscriber and PBX Access

3 Performance Monitoring of ISDN

Subscriber Lines
The performance monitoring facility monitors the digital subscriber lines during
operation. Counters are used for gathering fault information from the digital
subscriber lines for statistical evaluation. Performance monitoring can be used to
check whether a digital subscriber line is maintaining a certain transmission quality
level. Different requirements are specified for the transmission quality of digital
subscriber lines, depending their application. Due to ITU-T recommendation a bit
error rate of 10-3 is adequate for transmitting speech, a data channel requires a bit
error rate of at least 10-6.

Recording of performance monitoring data for PBX lines on primary access PA

The performance monitoring for a PA uses the standard concept for monitoring of
PDC with CRC4.

Recording of Performance Data for a BA

The transmission quality of a basic access in the transmit and receive directions is
checked by recording frame errors. The SLMD monitors the data flow on the two B-
channels and on the D-channel. Errors are detected by a checksum (CR12 method).
The performance monitoring for a BA is started with ACT BAPERF and stopped with
DACT BAPERF.
Remarks to BAPERF:

Performance measurements tests can run for a maximum of 10 BA only.

The measurement is activated on a quarter-hourly basis.

Every 15 minutes the measurement data is recorded periodically and then stored
separately, for each measured object, to a cyclic file .

Measurement is interrupted, if the port or the SLMD module is configured to MBL.
The measurement results can be displayed with the command:
DISP BAPERF: LAC = , DN = ,
DLU = , LC =
BEGDAT = ,
BEGTIM =
[,ENDDAT = ]
[,ENDTIM = ];

18 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

• EFS seconds without frame errors

• ES seconds with a bit failure rate between 10exp-6 and 10exp-3

• SES seconds with a bit failure rate >10exp-3

• DM 60 consecutive seconds (without SES and UAS) with a bit failure rate between
10exp-6 and 10exp-3

• UAS timespan, beginning with the first of at least 10 consecutive seconds with a bit
error rate (BER) >10exp-3, and ending with the last second with a BER >
10exp-3, which is followed by at least 10 consecutive seconds with BER <
10exp-3

• FRAME ERRORS number of frame errors that occurred within the measuring interval

Fig. 7

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

SN2012EU07AL_01
19
 Siemens Supervision of the Subscriber and PBX Access

20 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

4 Selected Commands

SN2012EU07AL_01
21
 Siemens Supervision of the Subscriber and PBX Access

STAT PORT: EQN= <tsg> - <ltg> - <diu>;

output of PA, to which the ports are connected; are the ports connected at all?
check out, if ports of a DIU are active (INC, OUT, INT, BUSY) or ready for use
(IDLE)
fetch further information about the kind of trouble for disturbed ports (e.g. NCAR:
Level 1 missing; MPRT/MDIU/MLTG: units are blocked by operator;
NPRT/NLTG/NDIU: HW failure detected by EWSD;)

STAT PBXLN: LAC = ..., DN = ..., LNSTAT = ...;

output of the status of the divers PBX-lines

DISP PBXLN: LAC = ..., DN = ..., SUMMARY = COUNT [, OPMODE = ...];

quick overview about the quantity of lines to a PBX; optionally filtered by
parameter OPMODE

DISP PACHSTAT: EQN = <tsg> - <ltg> - <diu>;

information about the maintenance status of all B-channels of a PA and the sum of
D-channel transactions

STAT BA: LAC = ..., DN = ...;

display of all current call-related data of a BA

TEST ROUDB: CODE = ..., LAC = ..., DN= ... [, OPMODE = ...] [, LNO = ...] [, SERV
= ...];
check, if currently a destination designated by CODE can be accessed from a PBX
(if necessary using a specific service)

DISP CONN: LAC = ..., DN= ..., OPMODE = {IBW, IIC, IOG, ..., 1TR6}, LNO = ...;
checking lines of a PBX: which ones are currently used for a connection?

DISP PDCCHR: PDC = <tsg> - <ltg> - <diu>;

output of the PDCID, which consists of 2 text strings of six characters each and
which may contain information about the PBX (if data is maintained)

22 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

STAT PORT: EQN = <tsg> - <ltg> - <diu>;

STAT PBXLN: LAC = ..., DN = ..., LNSTAT =...;

DISP PBXLN: LAC = ..., DN = ..., SUMMARY = COUNT [, OPMODE = ...];

DISP PACHSTAT: EQN = <tsg> - <ltg> - <diu>;

STAT BA: LAC = ..., DN = ...;

TEST ROUDB: CODE = ..., LAC = ..., DN= ... [, OPMODE = ...] [, LNO = ...] [, SERV = ...];

DISP CONN: LAC = ..., DN= ..., OPMODE = {IBW, IIC, IOG, ..., 1TR6}, LNO = ...;

DISP PDCCHR: PDC = <tsg> - <ltg> - <diu>;

Fig. 8 helpful commands for surveillance of PBX

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

SN2012EU07AL_01
23
 Siemens Supervision of the Subscriber and PBX Access

24 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

5 Exercise

SN2012EU07AL_01
25
 Siemens Supervision of the Subscriber and PBX Access

26 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

Exercise 1
Title: Performance Monitoring for ISDN Subscribers
Objectives: The participant is able to start performance monitoring
measurements for ISDN subscribers
Pre-requisite: ISDN subscribers are created in the EWSD
Task

Start performance monitoring for an ISDN BA immediately. Display the test results

SN2012EU07AL_01
27
 Siemens Supervision of the Subscriber and PBX Access

28 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

6 Solution

SN2012EU07AL_01
29
 Siemens Supervision of the Subscriber and PBX Access

30 SN2012EU07AL_01
Supervision of the Subscriber and PBX Access Siemens

Solution 1
Title: Performance Monitoring for ISDN Subscribers
Objectives: The participant is able to start performance monitoring
measurements for ISDN subscribers
Pre-requisite: ISDN subscribers are created in the EWSD
Task

Start performance monitoring for an ISDN BA immediately. Display the test results

TAC1/CTYCPZ1V1150/P18/000 98-12-15 15:05:44

1094 OMT-00/WOWAL 2926/06356

0453
<ACTBAPERF:LAC=091,DN=800220;

TAC1/CTYCPZ1V1150/P18/000 98-12-15 14:09:31

0453 OMT-00/WOWAL 3054/00007

ACTBAPERF:LAC=091,DN=800220; EXEC'D

END TEXT JOB 0453

0494
<DISPBAPERF:LAC=091,DN=800220,BEGDAT=98-12-15,BEGTIM=14-09;

TAC1/CTYCPZ1V1150/P18/000 98-12-15 14:11:08

0494 OMT-00/WOWAL 3058/00165

DISPBAPERF:LAC=091,DN=800220,BEGDAT=98-12-15,BEGTIM=14-09; EXEC'D

NO (MORE) DATA FOR DISPLAY AVAILABLE.

END JOB 0494 EXEC'D

SN2012EU07AL_01
31
 Siemens Supervision of the Subscriber and PBX Access

0889
<DISPBAPERF:LAC=091,DN=800220,BEGDAT=98-12-15,BEGTIM=14-00;

TAC1/CTYCPZ1V1150/P18/000 98-12-15 14:51:48

0889 OMT-00/WOWAL 3058/04456

DISPBAPERF:LAC=091,DN=800220,BEGDAT=98-12-15,BEGTIM=14-00;

RESULTS FOR 98-12-15 (YY-MM-DD):

TIME EFS ES SES DM UAS FRAME DATA

HH:MM ERRORS ACCURATE
-------+--------+--------+--------+------+--------+-----------+---------
14:45 900 0 0 0 0 0
14:30 900 0 0 0 0 0

END TEXT JOB 0889

TAC1/CTYCPZ1V1150/P18/000 98-12-15 14:51:49

0889 OMT-00/WOWAL 3058/04457

TOTAL SUM OF BA PERFORMANCE COUNTERS:

EFS ES SES DM UAS FRAME DATA

ERRORS ACCURATE
-------+--------+--------+--------+------+--------+-----------+---------
1800 0 0 0 0 0

END JOB 0889 EXEC'D

32 SN2012EU07AL_01