Autocom Abb Sofo

AMENDMENTS
The items that follow are incorporated in the update of this manual from issue 0201 to 0204:
CHAPTER/SECTION DESCRIPTION
2.4.10. CHTRAP and DITRAP Second additional parameter is added in trap type 11
(Call@Net 2.8)
3.3. NETWORK AND SYSTEM Boundaries 265 and 324 are added/changed (Call@Net
BOUNDARIES 2.8)
3.4. SYSTEM OPTIONS Options 124, 126, 130 and 133 are added/changed
(Call@Net 2.8)
3.5. NETWORK TIMERS Timers 32, 140 and 205 are changed
4.3. SUBCOMMANDS S3xxxx Subcommands S36100 and S36102 are changed
(Call@Net 2.8)
4.4. SUBCOMMANDS S4xxxx Subcommand S40210 info added (Call@Net 2.7)
4.4. SUBCOMMANDS S4xxxx Subcommand S42400 is changed (Call@Net 2.8)
3.3. NETWORK AND SYSTEM Boundaries 106, 110, 277, 278, 279, 326, 327, 328,329,
BOUNDARIES 382, 383 and 384 are added/changed (Call@Net 2.9)
3.4. SYSTEM OPTIONS Options 98 and 132 are added (Call@Net 2.9)
3.5. NETWORK TIMERS Timers 77, 84, 128, 222, 223, are added/changed
(Call@Net 2.9)
4.2. SUBCOMMANDS S2xxxx Subcommand S21070 is added (Call@Net 2.9)
4.3. SUBCOMMANDS S3xxxx Subcommands S30000, S30001, S37300 and S37500 are
added/changed (Call@Net 2.9)
4.4. SUBCOMMANDS S4xxxx Subcommand S45600 is added (Call@Net 2.9)
1
2.5. SECOND LINE Commands DIPDAT, DEPDAT and SPPMON are
COMMANDS FOR PVE removed (Call@Net 2.10)
3.3. NETWORK AND SYSTEM Boundaries 308 and 309 are added (Call@Net 2.10)
BOUNDARIES Boundary 213 is changed (Call@Net 2.10)
3.4. SYSTEM OPTIONS Options 115, 134 and 136 are added (Call@Net 2.10)
3.5. NETWORK TIMERS Timer 224 is added (Call@Net 2.10)
4.3. SUBCOMMANDS S3xxxx Subcommand S30430 is changed and S30903 is added
(Call@Net 2.10)
4.9. SUBCOMMANDS S9xxxx Subcommands S99710, S99720 and S99730 are removed
(Call@Net 2.10)
3.3. NETWORK AND SYSTEM Boundaries 91, 150, 285, 372, 385, 386, 387, 388 and 389
BOUNDARIES are added/changed (Call@Net 2.11)
3.4. SYSTEM OPTIONS Option 135 is added; option 124 has become obsolete
(Call@Net 2.11)
3.5. NETWORK TIMERS Timers 225, 226, 227 and 230 are added (Call@Net 2.11)
4.9. SUBCOMMANDS S9xxxx Subcommands S92260, S92280, S92420 and S92425 are
added/changed (Call@Net 2.11)
3.3. NETWORK AND SYSTEM Boundaries 047, 077, 390 and 401 are added (Call@Net
BOUNDARIES 3.1)
3.4. SYSTEM OPTIONS Options 131, 137 and 138 are added (Call@Net 3.1)
3.5. NETWORK TIMERS Timers 228, 229, 231 and 232 are added (Call@Net 3.1)
4.3. SUBCOMMANDS S3xxxx Subcommand S30410 added (Call@Net 3.1)
2
4.4. SUBCOMMANDS S4xxxx Subcommand S45230 changed and S45250 added
(Call@Net 3.1)
4.9. SUBCOMMANDS S9xxxx Subcommands S92650, S92660 and S92670 added
(Call@Net 3.1)
3
PREFACE
This manual is valid for SOPHO Call@Net (previously known as SSW 810), running on all
ISPBX models of the SOPHO iS3000 Series. All of these systems will further be referred to as
"ISPBX".
LICENSING AGREEMENT
The licensing agreement for an ISPBX determines which facilities are available. It is therefore
possible that a facility described here will not work on a specific ISPBX, even though it has
been correctly configured. Check the relevant license agreement to determine what is
available.
GENERAL NOTE
Fully Integrated Networks (FINs) are only supported by the iS3070/3090!
NOTICE TO THE USER
Unless stated otherwise (in text and figures), the term :
- ALC-G represents the ALC-G, ALC-GP or ALC-G(R).

- DTX-I represents the DTX-I or DTX-I(R).
- PMC represents the PMC-HR, PMC-MC or PMC-G :
- PMC-HR represents the PMC-HR or PMC-G (with NCC-HR).
- PMC-MC represents the PMC-MC or PMC-G (with or without NCC-MC).
4
1. INTRODUCTION
This manual contains maintenance actions and OM commands intended for the more
specialized maintenance engineer, to deal with extraordinary behaviour of the system.
It describes those OM commands which can cause incorrect system behaviour if they are not
correctly executed.
Also background information is given to solve complex error situations and alarms.
A number of tools are available to help the specialist to observe and test the ISPBX system,
for example:
- OM for test tools;

- Second Line Maintenance Tools.
Furthermore the manual contains the complete description of:
- all the subcommands;

- all system and network boundaries, options and timers.
In general the following rules should be kept in mind:
- Be patient with the system;

- Always deal first with any alarms;
- Do not take any thoughtless action;
- Initiate a Manually Controlled Test on suspected resources;
- Execute corrective actions outside working hours;
- Check whether the system is not overloaded;
- Contact the national PHILIPS SERVICE ORGANIZATION;
- Keep the record of system documentation and problem reports up to date.
For the normal maintenance aspects and OM commands reference is made to the
MAINTENANCE MANUAL and OM COMMANDS MANUAL.
Note: Commands or parameter values may differ per type of the various SOPHO ISPBXs. These
differences are mentioned whenever applicable.
WARNING: ALTHOUGH REMOTE SECOND LINE MAINTENANCE IS

TECHNICALLY POSSIBLE, IT IS STRONGLY ADVISED TO DO
SECOND LINE MAINTENANCE LOCALLY.
5
2. OPERATIONAL MAINTENANCE TOOLS
2.1. INTRODUCTION
This chapter describes those OM commands intended for the more specialized maintenance
engineer, to deal with abnormal behaviour of the system.
There are two groups of OM commands:
- OM for Tools (included in the System Software) and

- Second Line Maintenance tools (only available on a separate floppy disk/CD-ROM).
The OM Commands for Tools are used to display the results of the Local Operating System
(LOS) functions which monitor the routing counters, the usage of various pools.
The Second Line Maintenance tools comprise those OM commands and subcommands to test
specific system parts and to display specific information of the system, normally not accessible
to the user.
Furthermore, the second line maintenance tools comprise an OM command to change PE data
without reloading or reprojecting the system and an OM command to force a password to a
new value.
For the interpretation of the displayed information when executing the OM commands one
should be familiar with the terms that are explained in the section that follows.
2.2. EXPLANATION OF TERMS
• Process
In the ISPBX a number of functions have to be performed: call control, system assurance,
operational maintenance, etc. Each function can be seen as a process which is going on in
the system in parallel with other processes. Also functions have to be performed more
than once in parallel, e.g. more than one call has to be handled at the same time.
• State
The process consists of a number of state descriptions and associated data; both the state
descriptions and data are intrinsically tied together. A state is the description of the actions
on the possible stimuli; one of the actions is a transition to another state. The data signifies
the process instance.
• Process Instance Value (PIV)
Each process is identified uniquely by a PIV which is allocated at the moment the process
6
is created. Process instances share the code they execute, but have different data to
operate on.
They are running in parallel, sharing the same resources (CPU time, memory) they need.
This mechanism is called concurrent running.
When a process instance is created it waits for stimuli; when there are no stimuli, nothing
happens and the process instance is in the stable state.
• Transition
When a stimulus occurs the process instance performs the actions; when all actions have
been performed, the process instance enters in the stable state again. The total sequence
of actions from stable state to stable state is called a transition.
• Partitions
A process instance can be split into partitions, each performing a part of the task. The
number of partitions in a process instance is dynamic; new partitions can be created and
partitions can be deleted during the lifetime of a process instance. A process instance
always has at least one partition. The partition is normally in a stable state. As result of a
stimulus a transition is started during which a number of actions are performed; the
transition eventually ends in a (new) stable state.
Only one partition in a process instance can be in a transition. When a stimulus is received
by a partition, the other partitions are automatically "blocked" for new stimuli until the
receiving partition enters a stable state again.
A partition is in a stable state when no transition is going on; a process is in a stable state
when all its constituting partitions are in a stable state and no stimulus is on its way. Now
any partition can receive a signal.
For call processing the state of a partition can be changed into two independent
dimensions:
- x-state: this is the state with respect to the outside world, e.g. an extension user goes
off-hook.
- y-state: this is the state of the "call control machine", e.g. communication with another
partition or topology actions.
• Pass Of Control (POC)
The transition in a partition can be extended to another partition using the special stimulus:
the Pass Of Control.
• Switch Of Control (SOC)
Within a partition, the x- and y-state communicate with each other with a special stimulus:
the Switch Of Control.
The dynamic data is structured in three separate parts:
• Process Control Block (PCB)

The PCB contains information relevant to the process instance as a whole plus details of
various partitions attached to the process.
7
• Partition Control Block (PACB)
The PACB is the data for the individual partition.
• Control Block (CB)
The CB contains the record of the states.
All process instances start from a basic "mother" process instance which is present at system
start-up time. This structure is the basic element to operate on when process instances are
created, modified and destroyed; this is illustrated in the figure that follows.
PCB
PACB
CB1
Figure 2-1 Simplest Process Instance.
When a partition is created a CB is automatically allocated to it. When no further actions are
taken, this CB remains allocated until the partition is killed.
The maximum number of CBs per partition is 5; together they form an ordered set. When
more CBs are needed the CBs can be added; the CBs in the set are renumbered automatically.
PCB PCB
PACB PACB
CB1 CB1
CB2 CB2 (new)
CB3 (old CB2)
Figure 2-2 Addition of a CB.
The CBs may be removed in similar but reverse way in which they were added. The ordered
list is maintained.
There are two classes of partitions:
8
- the controlling partition;
- the subordinate partition.
The controlling partition is the one which launches another partition; this launched partition
becomes the subordinate. The relation between PACB (the controlling partition) and PACB'
(the subordinate) is illustrated in the figure that follows.
A/B C
PACB(1) PACB’(2)
Figure 2-3 Controlling and Subordinate Partition Relation.
Each controlling partition can have two subordinates. The controlling partition uses a logical
link name, A or B to send messages to the subordinate; the subordinate uses a logical link name
C to send messages to the controlling partition.
When a partition launches a subordinate it must specify a CB sequence for the launched
partition and all following CBs numbered after the one specified are split off from the launching
partition and added to the launched partition.
Initial Situation Situation after launching a partition

PCB PCB
PACB PACB PACB (new)
CB1 CB1 CB1 (old CB2)
CB2
Figure 2-4 Launching a Partition.
This implies that the launching partition must have at least two CBs.
Furthermore, as each partition must have two states, it is necessary that the launching partition
specifies the state of the launched partition.
Launching a new process is done in a similar way.
9
Initial Situation Situation after launching a partition
PCB PCB PCB (new)
PACB PACB PACB (new)
CB1 CB1 CB1(old CB2)
CB2
Figure 2-5 Launching a Process.
A new process is created; this results in a new partition as well and one of the CBs is used as
the CB of the new partition.
2.3. OM FOR TOOLS
The OM Commands for Tools comprise the following OM commands:
- DIPOOL: Display number of free packets;

- DIROCO: Display routing counters.
In some commands the EHWA has to be entered. Note that for a single unit system the unit
number may be omitted.
2.3.1. DIPOOL
The command DIPOOL is used to display the number of free packets in a system. The display
is continuous and can be aborted by means of 'Ctrl X'. The following line is displayed when one
of the items is changed; the number of items displayed can not be changed.
Display Number of Free Packets 293!
DIPOOL : [<UNIT>];
Related subcommand: S99140
Response example
<DIPOOL:1;
PCB PACB CB SIG BUF SDB MDB LDB IOM STCK CDB
10
387 0380 0375 0400 0020 0016 0400 0190 000021 0097 1000
387 0380 0375 0398 0020 0015 0400 0190 000022 0097 1000
Command aborted
The displayed information indicates the following items:
- PCB : Process Control Blocks; this is the number of free process control blocks.
Every active process, e.g. one call, uses one block. The total number of PCBs
equals boundary 202 + 1.
- PACB : Partition Control Blocks; this is the number of free partition control blocks.
Every active process uses at minimum one block, e.g. call processing uses two
blocks for every call.
The total number of PACBs equals boundary 202.
- CB : Gives the number of free control blocks.
The total number of control blocks equals boundary 202.
When the number of CBs is smaller than a minimum value, the system does not
accept new calls anymore until the number of CBs is larger than the minimum
plus a hysteresis value.
This minimum can be calculated as follows:
boundary 202 - (boundary 202 x percentage of boundary 121).
Using, for example, the default values for a CPU3000 as given in chapter 3 this is:
500 - (500x85%)=75.
This minimum plus hysteresis can be calculated as follows:
boundary 202 - (boundary 202 x percentage of boundary 121)+
(boundary 202 x percentage of boundary 127)
500 - (500x85%)+(500x7%)=110.
11
- SIG : Signal Packet Pool; this indicates the queue for the processor.
This number is reduced as soon as the processor starts processing.
In a normal system 385<SIG<400.
When the number of SlGs is smaller than a minimum value, the system does not
accept new calls anymore until the number of SlGs is larger than the minimum
plus a hysteresis value.
This minimum can be calculated as follows:
boundary 203 - (boundary 203 x percentage of boundary 123).
400 - (400x18%)=328.
This minimum plus hysteresis can be calculated as follows:
boundary 203 - (boundary 203 x percentage of boundary 123)+
(boundary 203 x percentage of boundary 128)
400 - (400x18%)+(400x3%)=340.
- BUF : Buffer Packet Pool; free format data packets used in free format signals or by
PACBs. The total size of the Buffer Packet Pool equals boundary 222.
- SDB : Number of free Short Data Blocks (digit memories).
The total number of Short Data Blocks equals boundary 204. This number is
reduced, when e.g. a new call is set up, an A, C or M call is answered or when
executing a subcommand of an OM command.
- MDB : *) Number of free Medium Data Blocks.
The total number of Medium Data Blocks equals boundary 257. This number is
reduced, when e.g. Full Detailed Call Recording (FDCR) is activated.
- LDB : *) Number of free Long Data Blocks (see boundary 205).
The total number of Long Data Blocks equals boundary 205. This number is
reduced, when e.g. a batch job is executed (-10 blocks), for a toll ticketing call (-
1 block), for every projected OM terminal (-14 blocks) and when executing an
OM command in this unit (-14 blocks).
- IOM : Number of free I/O packets used for information transfer to/from the CPU.
The total number of I/O packets equals boundary 288.
- STCK : Number of free user stacks.
The total number of user stacks equals boundary 206.
- CDB : *) Call recording data blocks
The total number of call recording data blocks equals boundary 293.
*) Below some information is given about the use of LDBs, MDBs and CDBs in relation to the
use of toll ticketing and/or FDCR.
With toll ticketing (TT) active, information is gathered during the call about the call and stored
in a memory block called a Long Data Block (LDB). LDBs are used for different applications
12
but part of them is reserved for TT. These are called TT data blocks. The maximum number
of TT data blocks is limited by boundary 139 (max. number of TT data blocks).
When the call is finished it is copied into another type of data block, called Call Recording Data
Block (CDB) and the LDB and/or MDB is immediately available for new TT info (a CDB is
reserved together with the LDB or MDB).
So the accounting information is kept into the CDBs until it is sent to an output device. Since
the maximum number of CDBs is much higher than the maximum possible number of LDBs
or MDBs, this way buffering of accounting info in the CPU is created.
From the above it is obvious that the number of CDBs that uses call accounting must be at
least equal to the number of LDBs or MDBs.
2.3.2. DIROCO
OM command DIROCO, display routing counters, gives details of Physical CHannels (PCHs).
The EHWA, to be entered in this command, can be of a single PCH but also of a board which
contains PCHs (if CRT is omitted).
After reading the counters these counters are set to zero. The system does not record the last
reading action. It is possible to display the routing counters of units other than the unit where
the OM terminal is situated by specifying an EHWA in another unit.
Display Routing Counters 292!
DIROCO : <SHELF>,<BRD>[,<CRT>s/r];
Related subcommand S99120
Response example
<DIROCO:2014,7,2;
SHELF BRD CRT CHANNEL DESTINATION C1: C2: C3: C4: C5: C6: C7: C8:
2014 7 0 0 2014 24 xxx xxx xxx xxx xxx xxx xxx xxx
The first column of the output format indicates the number of the physical channel (PCH); the
second column gives the EHWA of the destination. The next eight columns indicates the route
counters (C1 ... C8) with a max. value of 255.
- C1 : Number of IMP messages with time outs;

- C2 : Maximum number of retries encountered;
13
- C3 : Number of incorrect received CRCs;
- C4 : Number of overflow messages received;
- C5 : Number of overflow messages sent;
- C6 : Number of discarded messages;
- C7 : Not used;
- C8 : Not used.
• Explanation
When the previous execution of the OM command was a long time ago, the counter values
might be reasonable high; this does not give any valuable information.
Valuable information can be obtained when the command is executed twice.
The first time will reset the counters to zero. Now when executing the command for a
second time, say half an hour later, it might be possible that for instance the number of
IMP messages with time outs (C1) or the number of incorrect received CRCs (C3) is
unusual for a normal operating system.
Also when for instance a complete PM shelf is taken out of service the number of incorrect
received CRCs (C3) or the number of discarded messages (C6) might be unusual.
2.4. SECOND LINE MAINTENANCE TOOLS
The Second Line Maintenance tools comprise the following OM Commands:
- DIPCHD : Display physical channel destination

- DISIGQ : Display signals in signal queue
- DILOAD : Display (main) processor load percentage;
- CHLDCT : Tune load control data
- DIPVAR : Display number of free packets once per minute
- CHBSPT : Change BSPT definition
- DIISDN : Display ISDN dynamic trunk access data
- FIOWNR : Display all resources with specified owner
- FCLAIM : Display all resources with given type and claim
- STMONI : (Re-)Start unrestricted status monitoring
- CHTRAP : Change the status of a system trap
- DITRAP : Display system traps
- CHPERD : Change peripheral data
- DIPERD : Display peripheral data
- EXSUBC : Execute PE subcommands
- FRCPSW : Force to new password
- CHPMFU : To change the Complete Number Identification (CNI)
- DIPMFU : To display the CNI
- DIMEUS : Display Memory Usage
14
WARNING: IN GENERAL THE ABOVE MENTIONED OM COMMANDS SHOULD
ONLY BE USED BY HIGHLY QUALIFIED MAINTENANCE
PERSONNEL, BECAUSE MISUSING THESE COMMANDS CAN
CAUSE SERIOUS PROBLEMS TO THE SYSTEM.
2.4.1. DIPCHD
The OM command DIPCHD, display physical channel (PCH) destination, is a variant of the
OM command DIROCO.
The difference between command DIPCHD and DIROCO is the fact that the command
DIPCHD will only display the destination of the physical channel pointed by the EHWA given
by SHELF, BRD and CRT whereas the command DIROCO will display the destination and all
available routing counters which are reset after they are displayed.
Therefore the command DIPCHD must be used if only the destination of a PCH must be
retrieved.
If parameter CRT is omitted all PCHs will be displayed.
Display Physical Channel Destination 307!
DIPCHD : <SHELF>,<BRD>[,<CRT>s/r];
Response example
<DIPCHD:2014,15,0&&2;
SHELF BRD CRT PCH DESTINATION
2014 15 0 0 2013 15
2014 15 1 1 2013 17
2014 15 2 2 2013 19
EXECUTED
2.4.2. DISIGQ
The OM command DISIGQ displays properties of CPU signals which are waiting to be
processed by the CPU. This queue is called the signal queue.
It shows the signal identifier, S(ignal)-address, the time in the queue and some additional
parameters (if available). These additional parameters are only available for signals which are
15
more than 10 seconds in the signal queue of the unit where the OM terminal is situated.
If a signal remains in the signal queue for a very long time, this might be an overload situation
or might indicate a software problem.
If a signal is in the signal queue for more than ten hours, this will be reported by an alarm
(unaccepted signal) and will then be deleted from the signal queue.
This time period (of ten hours) can be changed by OM CHTRAP (type 10).
Display Waiting Signals in Signal Queue 308!
DISIGQ : ;
Response example
<DISIGQ:;
SIGNAL-ID S-ADDRESS TIME-IN-QUEUE PARAMETERS
3103 13300000 00546
35D5 160C5103 11259 8B34 0000 0038 14
EXECUTED
Explanation of figures in the response of this command are to be obtained at the help desk.
2.4.3. DILOAD
The OM command DILOAD, display (main) processor load percentage, gives a continuous
display of the load of the main processor in the system where the OM terminal is situated.
Output to the terminal is only given when changes occur. Output can be stopped by means of
'Ctrl X'.
Display (Main) Processor Load 309!
DILOAD : ;
Response example
<DILOAD:;
Main processor load (in %)
005
009
012
16
011
Command aborted
2.4.4. CHLDCT
The OM command CHLDCT, tune load control data, can be used to change the parameters
of Load Control. The parameters define minimum and maximum load levels, guaranteed load
levels, fault detection levels, etc. The parameters are not project dependent.
In normal circumstances it is not necessary to change those parameters, because Load Control
is flexible enough to adapt to changing load conditions. However, for test purposes or in case
of unexpected emergencies the parameters can be changed. The tuning command only allows
changes within acceptable values.
Before executing this OM command, it is advised to execute OM command DIOVLD first, to

obtain the parameter values of the actual situation and to see which parameter needs to be
changed.
The parameter SOURCE indicates the item to be changed; it can be:
0 = SAS urgent actions;
1 = SAS fault handling;
2 = SAS preventive tests;
3 = OM urgent actions;
4 = OM maintenance;
5 = OM manual tests;
6 = CP call processing;
7 = CP registration and measurements;
8 = SAS general;
9 = OM general;
10 = GOS resource management;
11 = Unit total;
17
12 = Sampling.
The parameter DATA-INDICATOR indicates the type of data to be changed; it can be:
2 = guaranteed load in %;
3 = maximum load in %;
4 = minimum load in %;
5 = maximum simultaneous tasks allowed in numbers;
6 = time out value in minutes;
7 = minimum simultaneous tasks allowed in numbers.
The parameter DATA-VALUE represents the new value in the range O ... 2000.
After validation of the parameters subcommand S10530 is sent to the destination unit, where
it will change the given load control parameter.
Tune Load Control Data 359!
CHLDCT : <SOURCE>,<DATA-INDICATOR>,<DATA-VALUE>[,<UNIT>];
Example
<CHLDCT:1,2,20;
EXECUTED
2.4.5. DIPVAR
The OM command DIPVAR, display number of free packets per minute, is a variant of the OM
command DIPOOL. The command is used together with OM command STALDM to monitor
the load of the system given by parameter UNIT.
The differences with DIPOOL are:
- The display is once per minute;

- Output is always given, also when no differences occur;
- In the output DATE, DAY and TIME are issued;
18
It is adviced to execute this command in batch, as it takes about one minute to abort the
display.
The execution of command DIPVAR is done by subcommand S99130.
Display Number of Free Packets Once per Minute 310!
DIPVAR : [<UNIT>];
Response example (leading zeros omitted)
<DIPVAR,2;
DATE DAY TIME PCB PACB CB SIG BUF SDB MDB LDB IOM STCK CDB
1996-02-08 +1+ 10:5 1160 1157 1153 0400 0500 0028 0400 0166 - 0099 0010
0
1996-02-08 +1+ 10:5 1160 1157 1153 0400 0500 0028 0399 0166 - 0099 0010
1
Command aborted
Refer to command DIPOOL for explanation of the terms in the response.
2.4.6. CHBSPT
The CCITT has defined telecommunication services for ISDN. In the ISPBX the Internal Basic
Service Category (IBSC) is introduced to identify, in a condensed way, the Basic Service.
For trunk traffic it is possible to distinguish different sets of characteristics depending on the
Basic Service. Because various IBSCs might require the same characteristics, a reduction
mapping is introduced, distinguishing only a number of Basic Service Profile Types (BSPT).
The IBSCs are mapped on the BSPTs by OM command CRBSPT; see OM Commands manual.
Each defined BSPT uniquely identifies a set which contains a number of IBSCs. The BSPT is a
name for a collection of IBSCs; the contents of the BSPT set can be altered.
This command CHBSPT can be used to change the definition of a BSPT set. The sets may be
completely or partly overlapping.
The BSPTs 0 ... 19 and 94 ... 99 cannot be changed by command CHBSPT.
19
Change BSPT Definition 220!
CHBSPT : <BSPT>;
The command will ask a number of times for the additional parameter IBSC.
See the OM Commands Manual for a description of the IBSC and BSPT parameter.
2.4.7. DIISDN
With the OM command DIISDN, display ISDN dynamic trunk access data, it is possible to
display the dynamic data (usage) of the ISDN B-channels in a trunk. This command has two
parameter layout possibilities and displays the ISDN trunk access data as given below:
Display ISDN dynamic trunk access data 213!
DIISDN : <UNIT+BUNDLE>,<IBSC>s/r;
Example
<DIISDN:6023,0&&19;
BUNDLE IBSC CUR-IBSC-CALLS BSPT MAX-AVAIL-LINES CURRENT-BSPT-
CALLS
23 0 0 any - 0
23 1 0 any - 0
23 2 0 any - 0
.....
.....
EXECUTED
Display ISDN dynamic trunk access data 231!
DIISDN : <SHELF>,<BRD>s/r,<CRT>s/r[,<B-CHANNEL>s/r];
Example
20
<DIISDN:6013,19,0,1&&31;
SHEL BRD CRT BCH BND IBSC#TOTBSPTMAX #TOTBCH- DIR CLM #INC#OUT#TOT
F STATUS
601319 0 1 24 14 0 any - 0 free - no 0 0 0
601319 0 2 24 14 0 any - 0 free - no 0 0 0
601319 0 3 24 14 0 any - 0 free - no 0 0 0
.....
.....
EXECUTED
2.4.8. FIOWNR and FCLAIM
The OM command FIOWNR displays all EHWAs of the resources with owner specified by
parameter OWNER in the specified unit(s). If parameter UNIT is omitted the command is
executed systemwide; the parameter OWNER is represented by 0 ... 8, see table below. If no
resources are found which have the specified ownership, the message "No relations or data
found" is returned. The command is executed after subcommand S99000 is sent to the unit
given by UNIT.
The OM command FCLAIM displays all EHWAs of the resources with type specified by
parameter RESOURCE-TYPE and with a claim specified by parameter CLAIM-TYPE in the
specified unit(s). If parameter UNIT is omitted the command is executed "systemwide"; the
parameter CLAIM-TYPE is represented by 0 ... 8, see table below. If no resources are found
which have the specified claim type, the command will return "EXECUTED" and no message
is returned.
NUMBER OWNER/ NUMBER OWNER/ NUMBER OWNER/

CLAIM- CLAIM- CLAIM-
TYPE TYPE TYPE
0 NO 3 SYS 6 SAS2
1 START 4 SAS1 7 POM2
2 CP1 5 POM1 8 CP2
Table 2-1 Parameter OWNER and CLAIM-TYPE.
21
Display all Resources with Specified Owner 311!
FIOWNR : <OWNER>s/r[,<UNIT>s/r];
Response example
<FIOWNR:1&&8,2;
SHELF BRD CRT Required Current Owner
2014 1 INS INS SYS
2011 6 0 INS INS CP2
EXECUTED
Display all Resources with given Type and Claim 312!
FCLAIM : <RESOURCE-TYPE>s/r,<CLAIM-TYPE>[,<UNIT>s/r];
Response example
<FCLAIM:0,4,2;
SHELF BRD CRT Required Current Owner CLAIM
2011 1 5 OUT INS CP2 SAS1
2012 3 0 INS INS SAS2 SAS1
EXECUTED
2.4.9. STMONI
The OM command STMONI, (Re-)Start unrestricted status monitoring, is used to reset the
table containing the digit strings of the status monitoring items requested by the user. The
length of this table is defined by boundary 291.
This table is filled when a user programs a monitoring function under a key or an operator
programs a line of ten status monitoring functions in the status display.
During the lifetime of the ISPBX, this table becomes full, because items can not be removed
once they are added. This command STMONI can be used to reset this table.
A warning is given that all status monitoring registrations are lost when this command is
executed. To build up new registrations, it is necessary to force all extensions and operators
22
to resend their status requests. This can be done by putting them out and back to in service
again, or just pull their connection.
(Re-)Start unrestricted status monitoring 449!
STMONI : <UNIT>;
2.4.10. CHTRAP and DITRAP
Change the Status of a System Trap 216!
CHTRAP : <TRAP>,<ON_OR_OFF>[,<UNIT>];
Only execute this command after having consulted the helpdesk. They can inform about the
specific parameter values to be entered.
This command can set or re-set a system trap. A system trap is able to detect and report a
certain unexpected system event.
For example: the CSTA trap will cause the system to generate a system dump and report
certain alarms when it detects an unexpected message.
WARNING: THIS COMMAND CAUSES SERIOUS SYSTEM PERFORMANCE

DEGRADATION. THEREFORE IT IS RECOMMENDED TO GIVE
CHTRAP A HIGH AUTHORITY CLASS
Any system restart will set the value of a trap back to it's initial value. Mark that the initial values
of the various traps depends on system option 34.
The following parameter values can be entered:
<TRAP>: Identification of the trap (0 ... 17)

0= mapped port trap
1= invalid signal destination trap
2= resource release trap
3= SNC release trap
4= data handler exception trap
23
5= overrule journal updating (for lab purposes only)
This type is only available if the system is set to test mode by system
option 34 (for lab purposes only)
6= handle POCs and SOCs as signals (POC: Pass Of Control; SOC:
Switch Of Control)
This type is only available if the system is set to test mode by system
option 34
7= pool management trap
8= double POC SOC send trap
9= alarm occurrence trap
additional questions for this type of trap:
Enter [<ALARM-CODE>] (00...249) :
Enter [<ALARM-QUALIFIER>] (0...99) :
Enter[[<SHELF>][,[<BRD>][,<CRT>]]] :
It is not allowed to omit all three of the parameters.
<ALARM-QUALIFIER>can only be entered if<ALARM-
CODE>is entered.
10 = signal waiting too long trap
additional questions for this type of trap:
Enter [<SIGNAL-ID>] (H´000...H´FFF) :
Enter [<TIME>] (1...65534) :
It is not allowed to enter the same<SIGNAL-ID>twice
11 = param and stack initialization
additional question for this type of trap
Enter [<PRESET-VALUE>] (H'0000...H'FFFF) :
Enter [<UNUSED-STACK-TEST-VALUE>] (H'0000..H'FFFF)
:
12 = PVN protocol trap
13 = CSTA trap; turning on this trap (as from Call@Net 2.4), three
additional parameters will be requested to set a trap for the
detection of specific faults:
Enter parameter [<C-SET>] (H'0000...H'FFFF) :
Enter parameter [<I-SET>] (H'0000...H'FFFF) :
Enter parameter [<M-SET>] (H'0000...H'FFFF) :
The default values for these additional parameters are H'FFFF.
The relation between a CSTA-alarm (with Alarm code 61 and
Qualifier 083) and the settings for the CSTA trap is as follows.
24
The value of the second column of the ADD. INFO field of the alarm
represents the specific fault detected. This value is given in
hexadecimal. The first character of this value identifies the set type:
0 = M-set, 1 = I-set, 2 = C-set. The second character identifies the
specific element.
In order to enable (or disable) the notification of a specific fault
situation, the corresponding bit within the set must be set (or reset).
For example, when a CSTA alarm occurs with the value D'42
(=H'2A) in the second column of ADD. INFO, it means the C-set
(the "2") with element 10 (the Ä")
Subsequent alarms for the same fault situation can be disabled by
setting bit 10 (counted from right to left, starting with zero) of the C-
set to 0 (1111 1011 1111 1111 = H'FBFF). This is done by means of
CHTRAP: enter parameter [<C-set>] (H'0000-H'FFFF) : H'FBFF
14 = Pool overload trap
15 = Switching Special alarm trap
16= General Call Control trap (as from Call@Net 2.6)
17= General Freeze Control trap(as from Call@Net 2.6)
<ON_OR_OFF>: Status of the trap (0..1)
0 = OFF
1 = ON
<UNIT>: Unit number (1 ... 14) (Unit may only be omitted in single unit
systems)
Additional information of the various types of traps:
Type 0 : Mapped port trap
A port (extension, trunk, etc.) is still mapped to a partition that wants to kill itself.
The following actions are taken upon detection of the fault situation:
- The process of the partition that wants to kill itself is frozen.

- A frozen process system dump is generated.
- The following alarms are generated:
- 41,19 (Cleared software exception, port eventing on not existing partition)
- 33,1 (Diagnostic Notice, dump information available) where ADD.=0 (Frozen
process), INFO=Number of structure missing.
- 33,3 (Diagnostic Notice, Process frozen due to exception)
- 34,2 (System Maintenance Notice, System dump created due to a trigger) where
ADD.=Trap-id of trap that initiated system dump generation.
25
Type 1 : Invalid signal destination
This facility traps signals inside the CPU with an invalid destination address.
The following actions are taken upon detection of the fault situation:
- The signal is removed automatically by the LOS.

- The process will be frozen, if the originator of the signal is a non-static instance
(saddress.form = instanceform, instanceyform, eventportform, eventportyform) within
the CPU.
- A frozen process system dump or normal triggered by trap system dump is generated.
- 41,7 (Cleared software exception, Invalid signal destination) where ADD.=empty and
INFO=Signal identity.
- 33,1 (Diagnostic Notice, dump information available) where ADD. depends on
whether the process has been frozen; ADD.=0 (Frozen process) or ADD.=4
(Trigger from trap). INFO=Number of structure missing.
- 33,3 is only generated in the case of a frozen process (Diagnostic Notice, Process
frozen due to exception)
Type 2 : Resource release trap
This trap is used to detect a software-resource that is still occupied, while its related process
wants to kill itself.
The following actions are taken when the fault is detected:

This trap requires a special level update of the CPU software, which can be acquired from the
help desk.
This trap can not be used in combination with the SNC release trap (type 3).
26
Type 3 : SNC release trap
This trap checks whether still SNCs are booked busy (by Call Control) when a partition kills
itself.

This trap can not be used in combination with the resource release trap (type 2).
Type 4 : Additional Data-Handler checks
This facility sets an additional check on the CPU data handling process. This checks for the size
of the data structure name, data layout and the presence of the data structure.
- The system will execute an operational start due to exception.

- A system dump due to software exception is generated.
- 31,51 (System State Altered, operational warmstart due to exception) where
ADD.=0,1 or 2. This parameter indicates whether a hotstart (0) or warmstart (1) was
executed.
- 33,1 (Diagnostic Notice, dump information available) where ADD.=1 (Software
exception), INFO=Number of structure missing.
- 34,2 (System Maintenance Notice, System dump created due to a trigger where
- 41,9 (Cleared Software Exception, Data Handler exception where ADD.=Data
structure Synonym, INFO=Data Structure Identity
- 61,4 (Informatory Event, Additional information on DH exception) where
ADD.=error type, INFO=Signal identity
Type 5 : Overrule mandatory journal-updating
27
This facility allows for "change" OM commands in a system in which journalling is not
operational (due to central backup failure or because it has been switched off). This facility is
only allowed if the system is in test mode (system option 34).
Type 6 : Handle POCs and SOCs as signals
This enables the system to include the POCs and SOCs (special type of signals) in a system
dump. This facility is only allowed if the system is in test mode (system option 34). These
signals can be included in a system dump because they are now treated as normal signals and
make use of signal packets, just like other signals do.
This allows for a better analysis of software errors and display of parameters in PCSCOPE, but
causes a serious decrease of system performance (PCSCOPE is a development debugging and
analysis tool).
Type 7 : Pool management trap
The LOS uses pools of (data) packets for storage purposes. This trap guards against returning
a packet that has already been released.
The following is performed when the fault is detected:
- a trap triggered system dump is generated;

- The 'release' action is not executed.
- 33,1 (Diagnostic Notice, dump information available) where ADD.=4 (Trigger due to
trap), INFO=Number of structure missing.
Type 8 : Double send of POC or SOC
Application-software should send a POC or a SOC only once. This trap detects those
occasions where these are send twice (or more) and executes an operational start (due to
cleared software exception).
Furthermore the following actions are taken upon detection of this fault:
- The process of the partition that sends a POC or SOC twice (or more) is frozen.
- 41,42 Double POC/SOC error, in INFO the POC/SOC id may be found.
28
Type 9 : Alarm occurrence trap
In some cases a software fault is easier to find, if a system dump is created as soon as a specific
alarm is raised.
The following items are generated when the alarm is detected:
- A trap triggered system dump.

At most 4 alarm-codes, qualifiers and/or EHWAs can be entered.
(All) programmed alarm codes, qualifiers and/or EHWAs are removed from the list when the
trap is switched off. It is not possible to remove a single entry.
Type 10 : Signal waiting too long
This facility makes it possible to define the signal waiting time. At expiry of this time, the
system generates the alarm "Signal waiting too long" and removes the signal from the signal
queue.
This timer is normally (if this facility not set) 10 hours.
The following items are generated when the fault is detected:
- A trap triggered system dump;

- 41,11 (Cleared Software Exception, Unaccepted signal) where ADD.=0 (Signal
waiting too long), INFO=Signal identity.
29
If no time is specified then the default value will be 10 seconds. At most 4 signal-ids and times
can be entered.
(All) programmed signal ids and times are removed from the list when the trap is switched off.
It is not possible to remove a single entry.
Type 11 : Param and stack initialization
Some software-errors are the result of non-initialized variables. In the case that these variables
have a preset value, errors can be found more easily. As initialization takes time (causing a
performance-degradation) this initialization is normally not executed. If this trap is switched
ON, all param-fields and stacks are initialized to a preset value.
The preset value can be entered, but default the value H'AAAA is used. No special actions, like
a system dump generation or alarms are taken.
The initialization is not executed if SOCs and POCs are treated as normal signals (system is in
test mode and trap 6 is set).
Since Call@Net 2.8 this type is extended with an early warning system to announce excessive
stack usage on particular moments during execution of the software.
A second additional parameter 'UNUSED-STACK-TEST-VALUE' is used to define the number

of bytes (of each stack) which is supposed not to be used.
When the system occupies memory data in the 'not to be used' area the trap is triggered.
- The following alarm is generated:

- 43,15 (Cleared Software Congestion, Excessive stack usage indicating potential stack
overload).
Type 12 : PVN protocol trap
This trap generates a dump when the PVN data consistency check (activated by boundary 344)
finds an inconsistency. This can be an unexpected PVN protocol message, or the situation that
a user-channel is claimed but never used.
- A triggered system dump;

30
Type 13 : CSTA trap
This trap causes the system to generate a system dump in the case of an unexpected situation.
This can be if an inconsistency exist between the CSTA-SP and the CSTA-FH, or an
inconsistency exists within either one internally.
- A trap-triggered system dump;

- 33,1 (Diagnostic Notice, dump information available) where ADD.=4 (sysdump on
trigger), INFO=Number of structure missing.
- 34,2 (System Maintenance Notice, System dump created due to a trigger)
- 61,83 (Informatory event, a csta service error). ADD. and INFO contain the cause of
alarm. In several cases for specific parameters ADD. and INFO and if the system is in
operational mode, the alarm is suppressed. The alarm is raised if the system is both in
testmode and operational mode.
Type 14 : Pool overload trap
Within the LOS (Local Operating System), pools of (data) packets are used to store all kind of
information. A trap is implemented that guards against overload of a packet pool. This trap will
deliver DUMP information direct on the moment a pool overload is detected by the LOS
sensor. The restart (warmstart/hotstart) will prevent the system of hanging in a pool
congestion situation. Via the trap type (0 = no-restart, 1 = restart) it is decided to restart or
only create a system dump.
Type 15 : Switching special alarm trap
This trap, if active, generates a dump when the waiting message queue gets corrupted or if the
wrong messag ID is sent by the TMS server. The following actions are taken in case of this fault
situation:
- A system dump is generated;

- 33,1 (diagnostic notice, dump information available);
- PAR1=3 (sysdump on trigger), PAR2= number of missing structure;
- 34,2 (system maintenance notice, system dump created due to trigger);
- PAR1=trap-id of the trap that initiated the dump.
31
Type 16 : General Call Control trap
This trap, if active, enables system dump generation in the software, conditionally. This trap is
basically a general-purpose call control trap. This trap is implemented to control the places
where the dumps are generated and to make the dumps conditional. The following actions are
taken upon detection of the fault situation, which are indicated by the following alarms:
- A system dump is generated;

- 33,1 (diagnostic notice, dump information available);
- PAR1=3 (sysdump on trigger), PAR2= number of missing structure;
- 34,2 (system maintenance notice, system dump created due to trigger);
Type 17 : General Freeze Control trap
This trap, if active, enables system freeze in the software, conditionally. This trap is basically a
general-purpose freeze control trap. This trap is implemented to control the places where the
freezes are generated and to make the freeze conditional. The following actions are taken
upon detection of the fault situation, which are indicated by the following alarms:

- 33,3 (diagnostic notice, process frozen due to exception);
- PAR1 and PAR2 = none;
- 34,1 (system maintenance notice, number of frozen processes exceeded threshold);
Display System Traps 217!
DITRAP : [<TRAP>][,<UNIT>];
This command shows the status of the various system traps. Refer to OM CHTRAP for
detailed information on the parameter<TRAP>and of the additional parameters.
If<TRAP>is omitted, it shows the status of all traps which have been turned on.
The parameter<UNIT>may only be omitted in single unit systems.
Response example
<DITRAP:,5;
Unit 5:
32
TRAP STATUSPAR1 PAR2 PAR3 PAR4 PAR5
mapped port trap ON - - - - -
invalid signal trap OFF - - - - -
resource release trap OFF - - - - -
SNC release trap OFF - - - - -
data handler trap OFF - - - - -
overrule journal updating OFF - - - - -
handle POCs/SOCs as signal OFF - - - - -
pool management trap OFF - - - - -
double POC/SOC trap ON - - - - -
alarm occurrence trap ON 31 12 05014 14 10
- - 05012 12 -
61 - - - -
41 19 - - -
signal waiting too long trap ON BF9 30 - - -
CAO 45 - - -
- 60 - - -
657 10 - - -
param/stack initialization OFF AAAA - - - -
PVN protocol trap OFF - - - - -
CSTA trap OFF - - - - -
Pool overload trap OFF - - - - -
Switching special alarm trap OFF - - - - -
General Call Control trap OFF - - - - -
General Freeze Control trap OFF - - - - -
EXECUTED
<
2.4.11. CHPERD and DIPERD
Change Peripheral Data 408!
CHPERD : <DEBUG-TYPE>, <SHELF>, <BRD>[,<CRT>];
Only execute this command after having consulted the helpdesk. They can inform about the
specific parameter values to be entered.
This command changes data in the PPU or PPH.
33
It does not use a subcommand (no journalling) and can only be executed in the unit where the
OM-terminal is connected.
<DEBUG-TYPE> : Debug type of data (0..FF)

0 = PM-general
1 = PM-specific-port
2 = PPH-general
etc. (t.b.s. in PPU and/or PPH)
<SHELF> : shelf position, format UUCCS
UU = unit number (1..14)
CC = cabinet number (1..15)
S = shelf number (1.. 4)
<BRD> : Board number (1..29)
<CRT> : Circuit number (0..31)
The command requests for data strings of hexadecimal digits (0, ... 9, A, B, C, D, E, F), where
each data string must be terminated by a ;.
These data strings must comply with the following rules:
- 20 characters per data string as a maximum;

- each data string must have an even number of characters;
- characters should be hex-digts (0 ... F);
- 25 data strings as a maximum;
- at least one data string must be entered.
Execution of this command requires a password.
Response example
0 4 8 12 16 20
12 34 56 78 9A BC
EXECUTED
<
The meaning of this response is specified in the PPU or PPH.
34
Display Peripheral Data 483!
DIPERD : <DEBUG-TYPE>, <SHELF>, <BRD>[,<CRT>];
This command displays data from the PPU or PPH. Consult OM command CHPERD for the
meaning of the parameters.
2.4.12. EXSUBC
The OM command EXSUBC, execute PE subcommands, enables the execution of single PE

subcommands in one or more local units.
By PE subcommands is meant: subcommands not related to any dedicated OM command.
Normally subcommands can not be executed from the OM device directly (subcommands
have authority class 15 which is disabled at all OM devices). Reason for this is that
subcommands do not perform validations on the input parameters and in a number of cases
more subcommands together make an entity. It is the task of the OM command to validate
and guard the consistency.
PE subcommands represent data which is normally defined in the start up phase of a project
(projecting phase). However in a number of cases the situation might occur that a user wants
to execute a PE subcommand in a running system. Example is a timer value which seems to
have an incorrect value. Rather then having to re-project the system, it would save a lot of time
if the timer could be changed by means of an OM command instead.
Command EXSUBC enables the execution of PE subcommands; the procedure meets the
following requirements:
- Depending on the required subcommand entered as a parameter to EXSUBC the

command will request the user to enter additional parameters. These additional
parameters are the parameters of the subcommand asked for.
Refer to the corresponding documentation for a description of those parameters.
- Because the specified subcommand might change some critical data, the command
EXSUBC should only be used by qualified people. So EXSUBC is given an authority class
which only should be enabled after entering a password.
- If the changes made are correct and must be permanent, a MIS file should be made by
executing command GEBUMI.
- In order to limit the use of this OM procedure, after one execution, the procedure will
delete itself from both the central memory and the local back-up device (not the case in
Call@Net 2.4 onwards).
- As always the possibility exists that system behaviour is badly damaged (e.g. the user
35
changes the wrong timer), an advice should be given to the user to execute the command
outside working hours.
- The subcommands to change boundaries, options, RTDM- and ACDM-data are not only
written to the PE list but also to the secondary list to effect the new value immediately.
However a small number of options when they are changed need a hotstart to become
active. For this reason check always the result. When the change is not activated execute
a hotstart.
The changed timer values (S92230) are activated by performing a hotstart.
WARNING: FOR CCS SYSTEMS, PE DATA IS OFTEN NETWORK DATA

(TIMERS, OPTIONS, ETC.). SO USUALLY THE COMMAND
SHOULD BE EXECUTED "SYSTEMWIDE".
Execute PE Subcommands 313!
EXSUBC : <SUBC-MNEM>[,<UNIT>];
SUBC-MNEM is the mnemonic of one of the following subcommands to be executed:
S92100 : Set system boundaries
S92200 : Set system options
S92230 : Set system timers
S92250 : Write forward MFC 1 data
S92260 : Write forward MFC 2 data
S92270 : Write backward MFC A data
S92280 : Write backward MFC B data
S92285 : Write termination after MFC A data
S92290 : Write termination after MFC B data
S92300 : Write alarm code parameter
S92310 : Write resource type parameter
Example
36
<EXSUBC:S92230,2;
WARNING: Executing subcommands might cause real damage to the system.
Do you want to continue yes/no ? :yes;
Enter parameter TIMER-INDEX :3;
Enter parameter UNIT-T (0 = 10msec, 1 = 100 msec, 2 = 1 sec, 3 = 10 sec,
4 = continuous) :0;
Enter parameter TIMER-VALUE (0..16383) :5;
To activate the changes made, perform a hot start and check the result.
If the changes are correct and must be permanent, make a MIS file.
2.4.13. FRCPSW
The OM command FRCPSW, force to new password, will force the password belonging to
the password group given by parameter PW-GROUP and the password key given by
parameter PW-KEY to the new value given by additional parameter PW.
If no new password is entered, no password will be assigned.
The command should only be used when all qualified people have forgotten the value of a
password. In order to limit the use of this procedure, after one execution, the procedure will
delete itself from both the central memory and the local backup device (not the case in
Call@Net 2.4 onwards).
The execution of the command is done by subcommand S22100.
The relation between PW-GROUP and the range of the corresponding PW-KEYs is given in
Table 2-2 PW-GROUP and PW-KEY Relation.
PW-GROUP DESCRIPTION PW-KEY

0 Authority class password (0...3)
1 Protection level NEW password (0...7)
2 Protection level APPEND password (0...7)
3 Protection level READ password (0...7)
4 Protection level DELETE password (0...7)
5 Degradation level password (0...2)
6 Miscellaneous password (0...2)
Table 2-2 PW-GROUP and PW-KEY Relation
37
Force to New Password 314!
FRCPSW : <PW-GROUP>, <PW-KEY>;
Example
<FRCPSW:0,11;
New password : xxxxxx; (not visible)
Verification : xxxxxx; (not visible)
EXECUTED
2.4.14. UPDUAL
The OM command UPDUAL initiates the reload of a package update in an iSMAN

(Metropolitan Area Network) of CCS-based systems. Depending on the parameters supplied,
the system will re-project or coldstart (load the MIS-file) after the new package has been
loaded.
A hotstart is only possible in case of a coldstart after reload.
The command UPDUAL can be used in CCS systems.
Before the command UPDUAL is given the following preconditions have to be checked/set:
- Set BMLOCK.
- Create a MIS-file system wide.
- Install the new maintenance releases on the DBU of all units involved (System Software,
PL.POM file and firmware packages).
- In case of 'Re-project after reload':
Install the projecting files on the DBU and remove all MIS-files from the DBU (for all units
involved). Copy on the unit containing the CBU the empty journal file from the LBU to the
DBU.
- In case of 'Coldstart after reload':
Copy the created MIS-files from the LBU to the DBU in each unit involved. Copy on the
unit containing the CBU the empty journal file from the LBU to the DBU.
Initiate a package reload in an iSMAN of CCS-based platforms 493!
UPDUAL : [[<UNIT>] [, [<UPDATE-START>] [,<HOTSTART>] ] ];
Related subcommands: S81540 and S81550
38
<UNIT>: The unit number range 1 ... 14
If the parameter is omitted, the command is executed system wide.
<UPDATE-START>: 0 = Load the package and coldstart standby cluster
1 = Load package and re-project standby cluster
If the parameter is omitted, zero (0) is assumed.
<HOTSTART>: 0 = No hotstart is executed
1 = A hotstart is executed by the system
If the parameter is omitted, zero (0) is assumed.
Note: Using function key F10 and switching to the standby cluster will abort the command.
Aborting the command is, to up to a certain point, possible by typing Ctrl-X. Abortion may
take some time. No confirmation is given. Please be patient.
2.4.15. CHPMFU and DIPMFU
Change PM Function 499!
CHPMFU : <PM-FUNCTION>, <UNIT>;
PM -FUNCTION : 1 = CNI (Complete Number Identification);

2 = Currency (not supported yet);
3 = Digit insertion (not supported yet);
4 = Digit deletion (not supported yet).
UNIT : Unit number (1...14).
The command asks for additional parameters:
1) First or second place: 1 = first

2 = second
2) ISDN protocol types: 1 = ETSI or QSIG
2 = 1TR6
CNI is not supported for other protocols.
3) Basic-MNPBI, a 2-digits hex number :
Default H'23 or H'21 (trunk for free numbers) : for other values refer to the
Signalling Manual.
39
4) Primary-MNPBI, a 2-digits hex number :
Default H'24 or H'22 (trunk for free numbers) : for other values refer to the
Signalling Manual.
5) Type Of Number : 1 = subscriber
2 = national
3 = international
4 = transparent or not applicable
6) Trunk Access Code : digits 0..9, *, #, A, B, C
7) International Prefix : digits 0..9, *, #, A, B, C
8) National Prefix : digits 0..9, *, #, A, B, C
9) Own Country Code : digits 0..9, *, #, A, B, C
10) Own Area Code : digits 0..9, *, #, A, B, C
11) Own Local Prefix : digits 0..9, *, #, A, B, C
Display PM Function 504!
DIPMFU : <PM-FUNCTION>[[,<SHELF/UNIT>] [,<BRD>]];
PM -FUNCTION : 1 = CNI (Complete Number Identification);

2 = Currency (not supported yet);
3 = Digit insertion (not supported yet);
4 = Digit deletion (not supported yet).
SHELF/UNIT : Shelf position, format UUCCS:
UU = Unit number (1...14), must be omitted in a single unit system,
CC = cabinet number (1...15),
S = Shelf number (1...4);
BRD : Board position in the shelf (1...29).
If the signalling group data is read from the PM directly, a SHELF and BRD indicating a PM must
be given.
2.4.16. DIMEUS
This command can be used to determine the physical memory size of a system.
40
Display Memory Usage 494!
DIMEUS : [<AREA>][,[<USER>][,[<UNIT>]]];
Related subcommand S99610.
AREA omitted Summary of the memory areas

1 Summary of users of the system memory area
2 Depending on USER parameter
USER (is only applicable for AREA = 2)
omitted Summary of users of the heap memory area
0 Display of the heap administration
1 Display of the LOS pools
2 Display of the non permanent overlays
3 Display of the service data
4 Display of pSOS info
5 Display of the free blocks of heap
Response example
<DIMEUS:,,2;
MEMORY AREAS
AREA DESCRIPTION BASE LAST SIZE DECIMAL
1 SYSTEM 80000000 8065D001 0065D002 6.36M
2 HEAP 8065D002 81FFFFFF 019A2FFE 25.64M
TOTAL 02000000 32M
EXECUTED
2.5. SECOND LINE COMMANDS FOR PVE
Private Virtual Enhancements (PVE) is an entity within the PBX that provides SOPHO
functionality as a TCP/IP service to a server called "Call@Net Application Server". This
Call@Net Application Server is a PC, running the MyOffice@Net or Management@Net
software.
For operational usage of the PVE functionality, LOSYSOP 121 must be set to "TRUE".
Furthermore allowance license 56 (Call@Net Application Service) is required.
The PVE supports the following functionality :
41
- monitoring;
- data retrieval;
- facility activation / deactivation.
For PVE, the following Second Line OM commands are available:
- DIPMON : Display PVE Monitor

- STSRVC : Start Relay Service
- SPSRVC : Stop Relay Service
- DISRVC : Display Relay Service Status
Display PVE Monitor 571
DIPMON : <DNR>s/r;
Display the PVE monitoring status of the specified DNR. It only displays if a DNR is monitored,
not which attributes are monitored.
Response:
<DIPMON:2300&&2302;
DNR MONITOR
2300 Yes
2301 Yes
Message 31: No relations or data found
EXECUTED
Start Relay Service 567
STSRVC : <IP-SERVICE>[,<UNIT>];
Start a relay service. Currently only the PVE service can be started.
Parameter IP-SERVICE is 0, meaning PVE service.
However this command is also intended for starting other relay services (e.g. CSTA, IPVN).
When parameter UNIT is omitted, the command is executed in the unit where the OM
terminal is connected to.
To be able to execute this command, LOSYSOP 121 (PVE Active) must be TRUE.
42
Stop Relay Service 568
SPSRVC : <IP-SERVICE>[,<UNIT>];
Stop a relay service. Currently only the PVE service (0) can be stopped. However this
command is also intended for stopping other relay services (e.g. CSTA, IPVN).
Display Relay Service Status 569
DISRVC : <IP-SERVICE>[,<UNIT>];
Display the status of a relay service. Currently only the status of the PVE service (0) can be
displayed. However this command is also intended for displaying the status of other relay
services (e.g. CSTA, IPVN).
Response:
<DISRVC:0;
UNIT SERVICE STATE
2 PVE CONNECTED
EXECUTED
Possible service statuses are :
- STARTING : the PVE manager is starting to listen for a PVE server

connection.
- STARTED : the PVE manager is listening for a PVE server connection
- CONNECTED : the PVE manager has a connection with a PVE server
- STOPPING : the PVE manager is stopping to listen
- STOPPED : the PVE manager is not listening
43
3. BOUNDARIES, OPTIONS AND TIMERS
3.1. INTRODUCTION
This chapter describes the projecting data which can be changed in the ISPBX system
software. The software consists of a program and data. The program cannot be adapted; the
data can be changed by executing OM commands and subcommands.
Nearly all data can be loaded by means of OM (Operational Maintenance) procedures.

However, some data can rather be programmed on site, like the traffic class of an extension.
Thus a separation is made between PE (Project Engineering) data and OM data. The PE data
can only be changed by qualified system technicians. Also the projecting load file in the
subcommand format is only readable for system engineers.
The PE data consists of two types. Type one determines lengths of tables, type two 'fills' the
tables. Type one consists only of a parameter group called the 'system boundaries'. Type two
consists of parameters which determine the system properties in detail.
Normally, assigned PE values can be changed on a running system by means of OM procedures

without disturbing main system functions. However, this is not possible for Network and Local
System Boundaries, Options and Timers.
Options and timers can be changed by OM command EXSUBC where some of them need to
be effectuated by an operational start. The EXSUBC command informs whether the
operational start is needed.
System boundaries must be changed in the PE file and then together with the LL file loaded
back into the system by STPROJ.
Boundary -, option - and timer values can be displayed by OM DIMDAT (see OM commands
manual for details on this command)
WARNING: BOUNDARIES, TIMERS AND OPTIONS WHICH ARE NOT

MENTIONED MUST BE SET TO THEIR DEFAULT VALUES.
3.1.1. Network and Local System Boundaries
In general the system boundaries define the length of tables. These length of tables are
projectable because of various reasons. One of the main reasons is that these tables determine
the required size of memory. Because it is projectable it is possible in emergency cases to
increase critical items and to decrease less critical items in order to fulfil system demands.
44
Another reason is that the maximum number of users per facility is projectable and so the
quantity of facilities can be sold tailor made. Expansions of these tables by the customer can
be prevented. So if the customer wants to increase the facilities he can be charged for that.
The boundaries can be changed by executing subcommand S92100 (Set Unit Boundaries and
System Parameter) using OM command EXSUBC. The OM command CHBOUN is available
to change 'safe' boundaries. A safe boundary is a boundary that, when changed, does not need
reprojecting. CHBOUN requires a lower authorization level than EXSUBC
The presentation of the boundaries is as follows:
- LOBOUNDxxx : means that it is a local boundary, which means that the value of this
parameter is unique within a unit: so the same parameter can have
different values in different units of a particular network.
- NEBOUNDxxx : means that it is a network boundary, which means that a parameter
has a value which is unique within the network: so the same
parameter must have the same value in all units.
Note: The CCS systems use these boundaries network wide. All other
systems use these boundaries only locally.
- BOUNDxxx : means that this system boundary is not projectable using the SOPHO
Configurator Package (SCP) program. It can be a 'local' or 'network'
boundary.
- xxx : is an index number, corresponding with the index number applied by
the subcommand.
An example of the notation is:
LOBOUND016 : MAX NUMBER OF OPERATORS
(min...max) : default
The minimum and maximum values are given between brackets, the default value is given after
the colon.
3.1.2. Options
The system options (NESYSOPxxx) are of the Boolean type, indicating whether a system
option is valid (TRUE or YES) or not (FALSE or NO). The options can be changed by executing
subcommand S92200 (Set System Options) using OM command EXSUBC. Also the OM
command CHOPTI is available to change an option: it requires a lower authorization level than
EXSUBC.
45
NESYSOP000 : MULTI-UNIT
default : false
3.1.3. Timers
In the last section all system timers (NETIMERxxx) are described. It is advised to apply the
smallest time unit (seconds), especially when the defined timer function requires an accurate
timing. The reason for this is as follows:
Suppose a timer is required of one minute. As soon as the timer is started the system
determines that the timer is exceeded at the moment that the system clock jumps to the next
minute. Thus in case the timer is activated at the moment that the system clock indicates 59
seconds, then after one second the minute counter is increased and the system concludes that
the timer is exceeded !!! Thus the projected timers and real duration of the timers is depending
on the state of the system clock at the moment of the activation of the timers.
This implies:
- A timer of 1 second expires between 0 and 1 second;

- A timer of 3 seconds expires between 2 and 3 seconds;
- A timer of 1 minute expires between 0 and 1 minute;
- A timer of 3 minutes expires between 2 and 3 minutes.
Timer functions, which require a range of minutes, can of course be specified in seconds if they
require a more accurate timing.
Such a solution is not possible for the timers which define seconds, but most of the concerned
timer functions do not require such an accurate timing.
NETIMER002 : EXTERNAL DIAL TONE TIME
(4 ... 10) : 8
The minimum and maximum values are given between brackets and the default value is given
after the colon.
The timers can be changed by executing subcommand S92300 (Set System Timers) using OM
command EXSUBC. Also the OM command CHTIME can be used to change a timer: it
46
requires a lower authorization level than EXSUBC.
WARNING: BOUNDARIES, OPTIONS AND TIMERS SHOULD ONLY BE

CHANGED BY HIGHLY QUALIFIED MAINTENANCE PERSONNEL,
SINCE INCORRECT HANDLING OF THESE, MIGHT CAUSE
SERIOUS PROBLEMS IN THE SYSTEM.
3.2. QUICK REFERENCE TABLES
System Boundaries
47
BOUNDARY DESCRIPTION
0 Country number
1 Exchange number
2 Administrative number
3 Spare identity
4 Default traffic service class night
5 Default traffic service class day
6 A led flash condition
7 Default AG number
8 Default CV value
9 Max. number of closed channels
10 Max. number of extension circuits
11 Max. number of night extensions
12 Representative ISPBX number
13 Max. number of hotlines
14 ISPBX transit counter
15 Max. number of secretary groups
16 Max. number of operators
17 Max. number of groups
18 Message waiting softring time (in units of 100 msec)
19 Max. number of absolute time daily broadcast subscribers
20 Max. number of COB places
21 Max. number of COB queues
22 Max. number of ARB destination cases
23 Max. number of ARB primary places
24 Max. number of ARB primary queues
25 Default extension IBSC
26 Default operator IBSC
27 Max. number of BSPs
28 Max. number of history messages
48
29 Max. number of queued CANS calls
30 Max. number of abbreviated numbers in system
31 Max. number of digit conversions per route
32 Max. number of projected CV values in system
33 Size of converter compatibility list in system
34 Enquiry digit
35 Max. number of IABD numbers per user
36 Max. number of IABD elements
37 Max. number of total IABD list entries
38 Max. number of interval times
39 Max. number of system time broadcast subscribers
40 Max. number of absolute time broadcast subscribers
41 Max. number of correct absolute time broadcast subscriber
42 SAS interunit communication guarding time
43 SAS interunit comm immediate recovery time
44 SAS interunit communication recovery time
45 Max. number of unit reachability subscribers
46 Max. number of extension DNRs
47 Max. number of sub-signalling groups for EL@Ns
48 Threshold for silent alarm limited by time
49 Threshold for silent alarm limited by amount
50 Max. number of Multi Function Boards
51 Max. number of RKT-SDTs
52 Max. number of SKT-RDTs
53 Max. number of trunks
54 Max. number of converters
55 Max. number of IN-MFCs
56 Max. number of OUT-MFCs
57 Max. number of bundles
49
58 Max. number of interunit bundles
59 Max. number of routes per unit
60 Max. number of paging routes in system
61 Max. number of interunit routes
62 Max. number of interunit lines
63 Max. number of routes in system
64 Max. number of message waiting requests in queue
65 Max. number of virtual paging codes
66 Max. number of paging lines
67 Max. number of ATF calls per route
68 Max. number of simultaneous ARB calls per initiator
69 Max. number of ATF calls in unit per type
70 Max. number of analysis trees
71 Max. number of analysis pyramids
72 Max. number of analysis groups
73 Max. number of DNRs in the system
74 Max. number of outgoing destinations
75 Reactivating buzzer time
76 Max. number of TMS slots
77 Max. number of lines of VoIP data
78 TMS guarding time
79 Max. number of PIVs in OMDM
80 Max. number of units
81 Limit time of call in queue
82 Max. number of CMs
83 Max. number of PMs
84 Max. number of Device Ports
85 Max. number of Devices per Device Port
86 Max. number of SCUs
50
87 Max. number of CIIs
88 Threshold for number of frozen processes
89 Max. number of channels per CIU
90 Max. number of command modules
91 Max. number of resource relations
92 Max. number of signalling group bit items
93 Max. number of signalling group byte items
94 Max. number of slave data items
95 Max. number of time source items
96 Max. number of function key menus
97 Max. number of devices in system
98 Max. number of TT lines per page
99 SAS AH default alarm distribution
100 Max. number of CP command handler transports
101 Max. number of B buttons
102 Number of passwords
103 Max length of queue indication
104 Limit time already answered call in queue
105 Max. number of rollback events
106 Rollback retry count for port id
107 Rollback retry count for no port id
108 Max. number of PCTs IPS
109 Number of facility intervals
110 Rollback retry count for CP2 owned port id
111 DNR radix number
112 Project number of digits
113 Max. number of external numbers
116 Max. number of IAS timeslots
117 Number of four digit pack
51
118 Max. number of TMS translations
119 Max. number of stimuli
120 Max. number of batch jobs
121 CB pool occupancy threshold
122 Stack pool occupancy threshold
123 Signal pool occupancy threshold
124 EPD occupancy threshold
125 Threshold for start stop PATS
126 Max memory size (kbyte) preserved for overlays
127 CB pool occupancy hystheresis
128 Signal pool occupancy hystheresis
129 Stack pool occupancy hystheresis
130 EPD occupancy hystheresis
131 Max. number of directed calls
132 Max paging COB on code queue length
133 Operator metering queue threshold
134 Default extension BSPT
135 Max. number of MAT request
136 SAS AH resource probation interval
137 Max. number of paging queue entries
138 Max. number of paging COB queue length
139 Max. number of TT data blocks
141 Main memory hard fault threshold
142 Main memory soft fault threshold
143 ACD forced absent guarding time
144 Max. number of TMS windows
145 TMS message waiting type
146 Max. number of barred numbers
147 Max. number of observed groups
52
148 Max. number of observed routes and bundles
149 Max. number of observed specific converters
150 Max. number of PCTs per PM
151 Max. number of interunits to unit
152 System limited number of units
153 System limited number of board positions
154 System limited number of shelves
155 System limited number of PCT boards per PM
156 System limited number of BICs per PM
157 System limited number of SCUs
158 System limited number of circuits per board
159 System limited number of virtual resources
160 System limited number of display members
161 System limited number of connectable parts per PM
162 System limited number of SNLs per SCU
163 System limited number of DTUs per PM
164 System limited number of CRTs per Board
165 System limited number of CM slices per CM
166 System limited number of channels per SNL
167 System limited number of channels per CII
168 System limited number of MICs per CM
169 System limited number of CRUs per SM
170 System limited number of SMs
171 System limited number of CSGs per SM
172 System limited number of Switch and Sense per MIC
174 System limited number of cabinets
175 Maximum number of CIEs
176 System limited number of function key levels
177 System limited number of ESUs per PM
53
178 System limited number of CRU entries per SM
179 System limited number of SNCs per connectable part
180 System limited number of authority class indexes
181 System limited number of level 0 function keys
182 System limited number of level 1 function keys
183 System limited number of softkeys
189 System limited number of single downloads
190 System limited number of PMCs parallel downloaded
191 System limited number of SNLs per connectable part
192 Max. number of selective answering extensions
193 Number of call positions per extension
194 Max. number of simultaneous ARB calls per Destination
195 Max. number of destination queues
196 System limited number of SNLs per PMC
197 System limited number of channels per RPM-IU-SNL
198 System limited number of SNCs per RPM-IU-SNL connection
part
199 System limited number of ports on a BIM
202 Max. number of control blocks
203 Max. number of signal packets
204 Max. number of short data blocks
205 Max. number of long data blocks
206 Max. number of user stacks
207 Max. number of D channels
208 Max. number of virtual channels per DTU
209 Max. number of RST-SOCOTEL
210 Disk space alarm upper level
211 Disk space alarm lower level
212 Max. number of TGST action requests
213 Max. number of different OM commands in system
54
214 Max. number of observed assistance groups
215 Max. number of PPH parameter block data items
216 Max. number of COB cases short COB queue
217 Max. number of COB cases long COB queue
218 Max. number of long facility destinations
219 Max. number of members
220 Max ranknumber for short dialling group
221 Max. number of TFM sessions
222 Max. number of buffer packets
223 Buffer pool occupancy threshold
224 Buffer pool occupancy hystheresis
225 Max. number MML standard message text string
226 Max. number MML specific error text string
227 Max. number MML header line text string
228 Max. number MML format sensitive text string
229 Max. number MML format insensitive text string
230 Max. number MML block text characters
231 Max. number of ACD groups
232 Office number
233 Default calling subscriber category
234 General calling subscriber category
235 Max. number of BSPT for trunks
236 Max. number of VCTs per DTU-BA for DPNSS
237 PVN package ID
238 Max. number of ISDN trunk circuits
239 Max. number of ISDN trunk B channels
240 ISDN INW flow receive window size
241 ISDN INW flow send window size
242 ISDN SIG flow receive window size
55
243 ISDN SIG flow send window size
244 ISDN MAN flow receive window size
245 ISDN MAN flow send window size
246 Max. number of BSPTs
247 Max. number of ACD agents
248 Max. number of BSP per extension circuit
249 Max. number of DTU-BAs for DPNSS
250 Max. number of FDCR data blocks
251 Max download request buffer size
252 Max. number of installed software packages
253 Max. number of route tables in the system
254 Max. number of sequence tables per unit
255 Average number of outgoing digit conversions per route
256 Pause tone
257 Max. number of medium data blocks
258 Access code for emulation
259 Number of digits for itemized bill
260 Don't disturb reset time (in minutes)
261 Max. number of temporary don't disturb cases
262 Max. number of agents per ACD group
264 Max. number of standard message queue places per ACD group
265 Number of feature requests per unit
266 Default MSN type
267 Default fixed MSN digit B0
268 Default fixed MSN digit B1
269 Max. number of PVN flows/calls
270 Max. number of PVN links
271 Max. number of user channels addresses
272 Max. number of hatches
56
273 Outstanding route opt. requests
274 Max. number of specific announcement circuits (Wake-up,
Mess. Waiting etc.)
275 Max. number of IPD entries
276 Max. number of CSTA links per unit
277 Max. number of CSTA monitored BSPs
278 Max. number of CSTA monitored global BSPs (obsolete since
Call@Net 2.9)
279 Max. number of CSTA calls per unit
280 MFC area number
281 Sub cluster ID
282 Projected Voice BSPT for operator
283 Monitored Assistance Groups
284 Standard message queue places (see also ACD)
285 Default trunk access code
286 Default baudrate character protocol
287 Default baudrate BCS protocol
288 Max. number of I/O packets
289 System limited number of address ranges
290 Max. number of buffered logging messages
291 Max. number of status monitoring items
292 Max. number of devices in unit
293 Max. number of stored call recording data blocks
294 Presentation restricted number digit
295 Begin of partial trunk access code
296 Default CLI 1
297 Default CLI 2
301 Max. number of Fixed Trunk Line Destination (FTLD) strings
302 Max. number of long Fixed Trunk Line Destination (FTLD)
strings
57
303 Max. number of DCCs
304 Max. number of alarmed CTAs
305 Max. number of internal CNND database entries
306 Max. number of CNND cache entries
307 Max. number of Free Numbering entries
308 First enquiry on trunk digit
309 Second enquiry on trunk digit
310 Max. number of peripheral file users per unit
311 Max. number of chained direct diversions
312 Length of unconditional MSN
313 ISDN transparency mode
314 Max. number of MRG members
315 Max. number of CLI/COL translation
316 Default connection allowance
317 SOPHO units left before warning tone
318 Tone type for warning tone
319 Enquiry keytone digit
320 Disable enquiry keytone digit
321 System limited number of solid state disks
323 Max. number of IP broadcast messages per second
324 Max. number of sockets per unit
325 Max. number of sockets per task
326 Max. number of CSTA data paths
327 Max. number of global CSTA data paths (obsolete since
Call@Net 2.9)
328 Max. number of CSTA IO registrations
329 Max. number of global CSTA IO registrations (obsolete since
Call@Net 2.9)
330 Max. number of CSTA call ids per unit
331 Message waiting dialtone
58
332 Basic DNR dialtone
333 Max. number of server dialled prefixes
334 Max. number of tasks
335 Max. number of queues
336 Max. number of message buffers
337 Max. number of semaphores
338 Max. number of timers
339 Intrusion digit
340 Forced release digit
341 Second enquiry keytone digit
342 Max. number of internal name database entries
343 CDD sorted order
344 PVN data consistency check interval time
345 Number of ARB relations
346 Rollback retry count for virtual port
347 Max. virtual ports in rollback
348 Max. percentage of ISDN virtual calls
349 Max. number of Conference Group Chains
350 Max. number of external name database entries
351 Max. number of usernames for FTP in system
352 Max. number of FTP sessions in unit
353 Max. number of OM datablocks in a system/unit
354 Max. number of tariff classes
355 Second disable enquiry keytone digit
356 iPVN TCP port number
357 Max. number of virtual lines
358 Assign, Change, Delete and Display Voice Logging Relation
359 QSIG transit PINX counter
360 Max. number of different Function Key data entries
59
361 Max. number of different Soft Key data entries
362 Max. number of Function Key data entries as sum available
(FKD entries of all menus together)
363 Max. number of total Soft Key data entries as sum available
(SKD entries of all menus together)
364 Max. number of call forwarding not reachable
365 PVE listen port
366 MFC end of CLI string character
367 PVE maximum extension monitors
368 PVE maximum groupmonitors
369 PVE maximum data monitors
370 PVE Manager ID
371 PVE Server ID
372 Max. number of Virtual PM's in a unit
373 Default Local Domain Identifier
374 Max. number of Local Domains
375 Max. number of location table entries
376 Max. number of numbering plan conversion entries
377 Prefix digit in call recording for E.164
378 Prefix digit in call recording for PNP
379 Max. number of profiles
380 Max. number of known IP addresses
381 Max. number of MOH circuits
382 Max. number of nodes in a WAN network
383 Max. number of virtual (notification) calls per WAN mobility
384 Delay time for CLIP on analogue set
385 QSIG GFP operational mode
386 Byte 1 IP address gatekeeper
60
390 QSIG Charging of Transferring User Indicator
401 Max. length of call rerouting diversion table
Table 3-1 System Boundaries
System Options
61
OPTION DESCRIPTION
0 Multi unit
1 Calling identity suppression in TT output
2 Keytone extensions
3 DPNSS account code restriction
4 Call set up to individual metering
5 Call to individual and tax metering
6 Destructive metering read allowed
7 Shuttle with forced release
8 Shuttle allowed extension dialled extension on hold
9 Shuttle allowed extension dialled trunk on hold
10 Shuttle allowed trunk dialled extension on hold
11 Shuttle allowed trunk dialled trunk on hold
12 Diversion on busy PLE allowed
13 Diversion on busy INE allowed
14 Series calls prohibit
15 Reroute don't disturb
16 IABD allowed for operators
17 Facility clock operates on traffic service class
18 Call waiting tone after extending to busy extension
19 Off hook Voice Mail Protocol
20 Block outgoing calls on TT datablock congestion
21 Reactivating buzzer
22 General call and overload signalling
23 M individual LED flash condition
24 Recall on hook allowed
25 M led flash condition
26 Source info route with access code repetition
27 Message waiting queueing softring
28 Wait for close sign (suffix)
62
OPTION DESCRIPTION
29 Block trunk after detection time out
30 More than 10 pulses as 1 digit to PSTN exchange
31 LOS switch 1
32 LOS switch 2
33 No reload via sensor point 6
34 Operational mode instead of test mode
35 Operational applications output format
36 LOS switch 6
37 LOS switch 7
38 LOS switch 8
39 Timer 201 used when announcement for DDI
40 Closed number scheme in network
41 Determine destination routes in hold
42 Delay before on hold by operator
43 CII types with even and odd numbered channels
44 Night mode display
45 Periodic call waiting tone
46 Dynamic group COB with intrusion allowance
47 Post dialling available
48 Number suppression in TT output
49 SAS alarm handler Signalling At Distance present
50 SAS alarm handler Signalling At Distance manual confirmation
51 Ignore progress indicator in ISDN release protocol
53 Network incompatibility allowed
54 Network incompatible mark
55 Transfer before answer allowed
56 Recall after clear in enquiry
57 MML other than English
58 Desksharing automatic download FKM
63
OPTION DESCRIPTION
59 Desksharing automatic deactive previous
60 Full Detailed Call Recording in stead of Toll Ticketing
61 Station call in case of idle group member
62 Digit conversion on outgoing route possible
63 NU tone after procedure error
64 Activate CFWB on assign
65 Reroute on no response
66 System with CSN-BC
67 SAS AH V 28 signalling ORED
70 Discard CLI in case of interworking
71 Block ARB destination for new calls
72 Keep ARB relation after ring time out
73 Cancel ARB relation after dialling the same destination
74 Unconditionally CLIR
75 Overrule CLIR for operators
76 Overrule CLIR for TT and Call Recording
77 Overrule CLIR prohibited for extensions
78 BSPT in BSP-ID not allowed at operators
79 CLIR in DPNSS send zeros
80 Automatic recall on trunk upon enquiry
82 FDCR no empty party B field allowed
83 Route optimization
84 Integrated Password Dialling
85 Upgraded COS autonomously to night
86 Unique cluster ID
88 Prevent alert from empty S0 bus
90 Warning tone on time-break calls
93 Suppress dial tone
94 Direct charging display refresh
64
OPTION DESCRIPTION
95 FTLD to match CLI
98 Insert Cluster ID for local DNR at SuperVisor
99 Access external CNND database for internal translation
101 Local CNND function active
102 Optimise status monitoring messages
103 Show Ethernet alarm
104 Prohibit desksharing between units
105 TSD for supervisors active
106 Free Numbering active
107 Offer call to supervisors at first announcement
109 Auto transfer of intrusion and force release digits
110 CDD database present
111 CDD feature active
112 CNND based on 8 bits latin1 or 7 bits
113 CSTA monitor events only after device idle
114 Highest of PID or extension traffic class used
115 Function key downloading by external
116 ACD diversion chaining allowed
117 Absent switching of last ACD member prohibited
118 Time break active for operators
119 Unique line numbering
120 iPVN active
121 PVE active
122 Opposite PBX does not support Do Not Disturb over DPNSS
123 PVE short XML
124 CLIP on analogue ETSI terminals
125 Busy indication for congestion on ACD groups
126 Diverting user id as CLI when diverting to external
127 Remote breakout accounting
65
OPTION DESCRIPTION
128 Skip journalling for intra-unit desksharing activation/
deactivations
129 Suppress Name-Number relations by default in RTRIEV output
130 Enable IP service alarms
131 Enable break-in circuits in remote PM
132 Synchronise to ISDN date/time
133 Sound buzzer for parked call in W-queue
134 Generate accounting record for Free-of-Charge call
135 iTMP free port allocation
136 Tone to operator when caller clears
137 Display route number of paging trunk
138 Pass external CLI/COL in CSTA transferred event
Table 3-2 System Options
System Timers
66
TIMER DESCRIPTION
0 Internal dial tone time
1 Interdigit time
2 External dial tone time
3 Number may be complete time
4 Post dialling time
5 Internal ring tone time
6 Tone limit time
7 Call forwarding time
8 Delayed hotline time
9 Delta ARB time
10 External ringtone time
11 ARB ringing time
12 Number not complete time
13 SAS silent alarm timer
14 SAS interunit communication schedule time
15 CSG change synchronization reference time
16 SAS SL handle loop guarding time
17 Trunk OL path guard time
18 OMDM delay time
19 Delay time before on hold by operator
20 Plug removed time
21 Operator not answering time
22 Return to operator time
23 CANS hooting time out
24 CANS on time
25 CANS off time
26 Fast call handling time
27 NE ringtone time
28 CFW INE to SCNE time
67
TIMER DESCRIPTION
29 CFW SCNE to MCNE time
30 CFW MCNE to CANS time
31 CANS release time
32 Reroute to overflow extension
33 CFW PLE to operator time
34 Periodically ticker tone time
35 TMS server guard time
36 Message waiting trigger time
37 COB display refresh time
38 Operator call buzzer refresh time
39 Chief operator activity scan interval
40 DDI divert to operator time
41 DDI tone time
42 DDI dial tone time
43 DDI interdigit time
44 MFC interdigit time
45 SAS SEH PM test time
46 SAS SEH SCU installation test time
47 SAS SEH PM installation test time
48 SAS SEH SCU test time
49 DDO wait for answer time
50 CP-PCT command guarding time
51 Test blocked trunk interval time
52 Seizure acknowledge time
53 Group information interval time (SOPHO Business telephone)
54 ACC sending answer delay time
55 ACC activation delay time
56 LOS system dump scan time
58 DDI keytone after answer time
68
TIMER DESCRIPTION
59 LEDs test time
60 Test transition time
61 Paging wait for answer time
62 Paging return to operator time
63 SAS DTU ownership retry time
64 SAS DTU alarm integration time
65 SAS DTU guard time
66 SAS short rollback timer
67 Hot start phase 2 guard time
68 PM hot start guarding time
69 Hot start resource transition short time
70 Hot start resource transition long time
71 SNR path congestion retry time
72 PCT short transition guarding time
73 PM warm start time
74 POM TT block return processing time
75 ILC load control time
76 CPC general null time
77 PFH inter unit communication guard time
78 PFH night traffic interval time
79 SAS short delay time
80 External dial tone detection time
81 External dial tone pre-detection time
82 DPNSS-DASS protocol guarding time
83 DPNSS-DASS release synchronization time
84 DPNSS communication guarding time
85 Traffic measurement extension scan time
86 Traffic measurement trunk scan time
87 Traffic measurement paging scan time
69
TIMER DESCRIPTION
88 Traffic measurement operator scan time
89 Traffic measurement auxiliary scan time
90 Traffic measurement call scan time
91 Transfer prohibit time
92 TMS download guarding time
93 DDI data call ringing time
94 SOCOTEL proceed to send guarding time
95 SOCOTEL inter digit guarding time
96 SAS ESU guarding time
97 SAS alarm handler remote alarm confirmation time
98 Paging repeat time
99 Announcement answer delay time
100 System congestion time
101 Announcement repeat time
102 Operator B led refresh time
103 Operator unit call handling refresh time
104 POM TT congestion time (fixed timer)
105 Operator congestion time
106 ARB time out check time
107 Call waiting ticker time
108 Idle time job time
109 CP command handler guarding time
110 POM lock retry time
111 POM congestion time
112 POM repeat execution time
113 POM CI command time
114 POM short time
115 Hello PM time
116 Hello PM response time
70
TIMER DESCRIPTION
117 PM transition guarding time
118 Hello SN time
119 SN response time
120 SAS DTU CC test time
121 CMP clear guarding time (fixed timer)
122 ATM synchronization time
123 POM TOM quarter hour interval (fixed timer)
124 SAS SNC congestion time
125 SAS PATS schedule time
126 Convertor not answering time
127 CM load sensing time
128 Claim check delay time
129 SAS schedule time
130 SAS postponed recovery time
131 Dial tone interval time
133 CSG response time
134 Requeue attempt time
135 SAS PCT test time
136 DDI dial tone delay time
137 SAS BAPT display time
138 Emergency extension ring back time
139 Hello CIU time
140 CIU response time
141 TSW test transmitter time
142 RRM schedule time
143 CIU reset time
144 SNR release path time
145 SAS PM tone source test time
146 General transition guard time
71
TIMER DESCRIPTION
147 Call logging delay time
148 SAS PM test time
149 POM long congestion time
150 LOS GLC monitor time
151 SAS congestion time
152 Wait for download acknowledge time
153 Wait for delete acknowledge time
154 Download retry time
155 ISDN overlap receiving guard time
156 Wait for insertion of authorization code time
157 CSG change reference point time
158 Recall ring time
159 DDI calling party control timer
160 DDO calling party control time
161 DDO called party control time
162 ACD group scan time
163 Trunk seizure acknowledge guarding time
164 DASS communication guarding time
165 POM DTAP inform guard time
166 SYS INW flow establish guarding time
167 OM board and PCT commands guarding time
168 Hotstart after load delay time
169 Hello IAS time
170 IAS response time
171 PM wait for the first resource transition
172 PM wait for the next resource transition
173 IAS recording alerting time
174 ACD wait before repeat processing
175 Charging display refresh time
72
TIMER DESCRIPTION
176 PM link closed during reset time
177 Close link delay time
178 ARB free notification delay time
179 ARB Call setup guarding time
180 Block ARB destination interval time
181 PPU response time
182 Delta ARB on free time
183 Delta ARB on busy for destination time
184 Delta ARB on free for destination time
186 SAS device idle after failure time
187 Logging device idle after failure time
188 Broadcast guarding time
191 MFE overall guarding time
192 PVN signalling channel setup guard time
193 PVN user channel setup guard time
194 PVN user channel reservation guard time
195 PVN UCA guard time
196 Route optimisation delay time
197 Overlay dialling time
198 PVN Hatch communication guarding time
199 CSTA predictive call ringing time
200 Conversation limitation time
201 Announcement answer delay time for DDI to idle extension
202 CIE transmission guard time
203 Dual mode cluster guard time
204 Dual mode operational start time
205 BIM transmission guard time
206 Dual mode communication guard time
207 CSTA command guarding time
73
TIMER DESCRIPTION
208 Terminal verification response time
212 Delayed transfer time
213 Multiple ring group call setup delay time
214 Twinning destination signalling guarding time
215 PDFS log file access repeat time
216 Disk space verification interval time
217 Peripheral protocol trace response guarding time
218 Synchronisation alarm integration timer
219 Minimum intrusion time
220 Maximum time between intrusion and forced release
221 Line park incoming call guarding time
222 QSIG communication guarding time
223 DECT Mobility update retry timer
224 QSIG AOC maximum wait for final charge time
225 QSIG Path replacement initiation time
226 QSIG Path replacement completion time
227 QSIG path retention guarding time
228 QSIG call intrusion request guarding time
229 QSIG call intrusion protection level (CIPL) request guarding
time
230 QSIG supplementary service guard time
231 QSIG AOC Complete Guarding Time
232 Call@Net Application Server Link Guarding Time
Table 3-3 System Timers
3.3. NETWORK AND SYSTEM BOUNDARIES
This section contains all the network and system boundaries of an ISPBX system.
LOBOUND000: COUNTRY NUMBER
All: (0000 ... 9999): 0
74
Specify the country number.
LOBOUND001: EXCHANGE NUMBER
All: (0000 ... 9999): 0

Specify the exchange number.
LOBOUND002: ADMINISTRATIVE NUMBER
All: (0000 ... 9999): 0

Specify the administrative number.
LOBOUND003: SPARE IDENTITY
All: (0000 ... 9999): 0

Spare identity.
NEBOUND004: DEFAULT TRAFFIC SERVICE CLASS NIGHT
All: (0 ... 7): 2

Define the default value of the night traffic class.
This parameter defines the default traffic class for extensions in 'night' situations.
NEBOUND005: DEFAULT TRAFFIC SERVICE CLASS DAY
All: (0 ... 7): 2

Define the default value of the day traffic class.
This parameter defines the default traffic class for extensions in 'day' situations.
LOBOUND006: A-LED FLASH CONDITION
All: (2 ... 10): 4

Define the maximum number of waiting calls after which the A-led starts flashing. This
parameter defines the number of waiting calls in an operator A queue after which the
concerned A-led starts flashing.
BOUND007: DEFAULT AG NUMBER
All: (0 ... (maximum number of analysis groups - 1): 0

Analysis group (AG) per default assigned to each extension.
75
Per default each extension belongs to the default AG. The default AG can never be higher than
the highest projected analysis group (NEBOUND072).
BOUND008: DEFAULT CV VALUE
All: (0 ... (maximum number of projected compatibility values in system - 1): 0

Compatibility Value (CV) as default assigned to each extension and trunk. Per default each
extension and trunk has the default CV assigned. The default CV is default set assigned (known
to the system) and also set compatible to itself in the compatibility matrix. The default CV can
never be higher than the highest projected CV (NEBOUND032).
BOUND009: MAX NUMBER OF CLOSED CHANNELS
All: (70 ... 140): 100

The SAS switching equipment handler keeps an administration of the switching network
channels (snc or interunit) it has closed to isolate a fault found in a switching equipment
resource in order to release them again when the faulty resource is withdrawn from service.
LOBOUND010: MAX NUMBER OF EXTENSION CIRCUITS
Ccss: (2 ... 9984): 172

Ccs4: (2 ... 9984): 172
Cpu3000: (2 ... 1152): 172
This parameter defines the maximum number of extension circuits. The value must be at least
the total number of extension circuits plus 2, that is all circuits plus 2 because one is reserved
for a hardwareless DNR and one for the basic DNR.
LOBOUND011: MAX NUMBER OF NIGHT EXTENSIONS
All: (1 ... 255): 5

Specify the ultimate total number (sum) of overflow extensions, permanent line extensions,
individual night extensions, sub common night extensions and main common night extensions.
This parameter defines the area to be reserved for these special extensions.
NEBOUND012: REPRESENTATIVE ISPBX NUMBER
All: (0 ... 49999): 0

This parameter defines the ISPBX representative DNR.
This parameter together with the office number (LOBOUND 232) and possibly the area
number (LOBOUND 280) represents the ISPBX subscribers number. It is used as calling line
identity in outgoing MFC calls when the internal DNR does not belong to the PSTN number
76
scheme. The most significant digit gives the number of leading zeros.
Examples:
INPUT Repr. PABX INPUT Repr. PABX

number number
0 - 4000X 0000X
X X 49999 00009999
0X X ABCD ABCD
0000X X 0ABCD ABCD
1000X 0X 1ABCD 0ABCD
20030 0030 4ABCD 0000ABCD
LOBOUND013: MAX NUMBER OF HOTLINES
All: (0 ... 512): 5

Specify the ultimate number of hot lines (normal+delayed). This parameter defines the area
to be reserved for the hot line facility.
NEBOUND014: ISPBX TRANSIT COUNTER
All: (0 ... 25): 8

This parameter defines the maximum number of transit ISPBX, that a DPNSS call may pass
through. It is used to support the DPNSS loop avoidance supplementary service described in
BTNR 188.
For consistent working in a combined DPNSS and QSIG network (supporting iSNet on top of
QSIG) it is advised to keep NEBOUND 14 and 359 the same in all PINXs.
LOBOUND015: MAX NUMBER OF SECR GROUPS
All: (0 ... 1000): 5

Specify the ultimate number of secretary groups.
This parameter defines the data area to be reserved for secretary groups in executive/
secretary combinations.
77
Note: The sum of LOBOUND015+LOBOUND017 (max number of groups) should not exceed
1430.
LOBOUND016: MAX NUMBER OF OPERATORS
Ccs4: (0 ... 31): 0

Ccss: (0 ... 31): 0
Cpu3000: (0 ... 8): 0
Specify the ultimate number of operators.
This parameter defines the area to be reserved for operator and operator circuit data.
Number depends mainly on the number of non DDI lines, DDI to the operators, assisted or
non assisted outgoing traffic, number of extensions.
LOBOUND017: MAX NUMBER OF GROUPS
All: (0 ... 1000): 5

Specify the ultimate number of group arrangements. This parameter defines the area to be
reserved for group data (all type of groups).
Note: The sum of LOBOUND017+LOBOUND015 (max number of secretary groups) should not
exceed 1430.
BOUND018: MESSAGE WAITING SOFTRING TIME
All: (50 ... 50): 50

This parameter defines the time (xl00ms) an extension receives the softring to indicate that a
message is waiting for this extension.
BOUND019: MAX NUMBER OF ABSOLUTE TIME DAILY BROADCAST

SUBSCRIBERS
All: (1 ... 10): 6

A process can take or cancel a subscription to (periodically) receiving absolute time messages
once per 24 hour. This parameter gives the maximum number of processes that have a
subscription to absolute time daily messages at the same time.
LOBOUND020: MAX NUMBER OF COB PLACES
All: (1 ... 999): 30

Define the maximum number of COB places.
78
This parameter defines the ultimate number of COB cases within one unit.
LOBOUND021: MAX NUMBER OF COB QUEUES
All: (1 ... 999): 10

Define the maximum number of COB queues. This parameter defines the ultimate number of
COB destinations within one unit.
LOBOUND022: MAX NUMBER OF ARB DESTINATION PLACES
Ccs4: (0 ... 512): 5

Ccss: (0 ... 512): 5
Cpu3000: (0 ... 255): 5
Define the maximum number of ARB destination cases. This parameter defines the ultimate
number of ARB destinations.
LOBOUND023: MAX NUMBER OF ARB PRIMARY PLACES
Ccs4: (0 ... 512): 5

Ccss: (0 ... 512): 5
Cpu3000: (0 ... 255): 5
Define the maximum number ARB primary places. This parameter defines the ultimate
number originating ARB cases.
LOBOUND024: MAX NUMBER OF ARB PRIMARY QUEUES
Ccs4: (0 ... 512): 5

Ccss: (0 ... 512): 5
Cpu3000: (0 ... 255): 5
Define the maximum number arb primary queues. This parameter defines the ultimate
number of extensions which can have ARB simultaneously.
NEBOUND025: DEFAULT EXTENSION IBSC
All: (0 ... 19): 14

Internal Basic Service Catagory (IBSC) default assigned to each extension. Each extension has
this default IBSC; by OM command (CHDNRS) the IBSC may be changed.
NEBOUND026: DEFAULT OPERATOR IBSC
All: (0 ... 19): 14

Internal Basic Service Catagory (IBSC) default assigned to each operator. Per default each
79
operator has this default IBSC; not projectable per operator by OM.
BOUND027: MAX NUMBER OF BSPs
Ccs4: (2 ... 9984): 242

Ccss: (2 ... 9984): 242
Cpu3000: (2 ... 3000): 242
Specifies the ultimate number of BSPs that can be present in a unit.
LOBOUND028: MAX NUMBER OF HISTORY MESSAGES
All: (255 ... 255): 255

Define the maximum number of history messages.
This parameter defines the length of the history fault buffer.
LOBOUND029: MAX NUMBER OF QUEUED CANS CALLS
All: (2 ... 255): 4

Define the maximum number of queued CANS calls.
This parameter defines the maximum number of calls which can be queued in the CANS
queue.
NEBOUND030: MAX NUMBER OF ABBREVIATED NUMBERS IN SYSTEM
All: (0 ... 4496): 50

Specify the maximum number of common pool abbreviated numbers. This parameter defines
the area to be reserved for registration of the common abbreviated numbers. Due to the
applied search algorithm, the tables using this boundary can NOT be filled for 100%.
LOBOUND031: MAX NUMBER OF DIGIT CONVERSIONS PER ROUTE
All: (0 ... 20): 4

Define the maximum number of incoming digit conversions per route.
This parameter defines the area to be reserved for incoming digit conversions per route
(maximum number of applied conversions per route, including digits suppression and adding
of digits). For performance reasons project this value as small as possible: for every incoming
digit a search through the conversion table will be done.
The maximum number of outgoing digit conversion is defined by NEBOUND255.
80
NEBOUND032: MAX NUMBER OF PROJ CV VALUES IN SYSTEM
All: (1 ... 255): 16

Maximum number of compatibility values (CV).
This parameter determines the number of CVs. This is used to reserve area and to validate
the concerned OM input. The 'compatibility value' facility provides the possibility to add a
criterion of which it is dependent too if two parties are allowed to collaborate with each other.
For allowance the concerned parties must have identical CVs.
NEBOUND033: SIZE OF CONV COMPATIBILITY LIST IN SYSTEM
All: (5 ... 255): 8

Define the size of the converter compatibility list. This parameter defines the area to be
reserved for storing 'compatibility-protocol' converter relations. A converter is any circuit
performing modem functions, a protocol can be the bit rate or e.g. V.24 or X.21.
NEBOUND034: ENQUIRY DIGIT
All: (0 ... 15): 15

Define which digit will be interpreted as enquiry signal.
The projected enquiry digit (pulses) which is received in a non-dialling state will be interpreted
as "enquiry signal". This cannot be applied by keytone extensions. This facility is normally only
applied if there is no earth connection present at the extensions. Project digit "15" (null digit)
if no enquiry digit is applicable. The presence of the facility 'calibrated loop pulse' is depending
on the applied signalling group number for the line circuits.
LOBOUND035: MAX NUMBER OF IABD NUMBERS PER USER
All: (1 ... 100): 10

Define the maximum number of individual abbreviated numbers an user is allowed to store.
This parameter limits the number of individual abbreviated numbers for all the users with the
facility Individual Abbreviated Dialling.
LOBOUND036: MAX NUMBER OF IABD ELEMENTS
All: (150 ... 12000): 150

Define the number of elements needed to store the external numbers for the facility IABD
(Individual Abbreviated Dialling) and LENR (Last External Number Repetition).
This parameter defines the space of a common pool to store the external numbers for the
81
facilities IABD and LENR. Every user the LENR facility is assigned to, needs two elements. An
external number with less than eleven digits can be stored in one element; all larger external
numbers occupy two elements.
LOBOUND037: MAX NUMBER OF IABD LIST ENTRIES
All: (47 ... 4621): 50

Define the maximum number of lists to store external numbers for the facilities IABD
(Individual Abbreviated Dialling) and LENR (Last External Number Repetition).
This parameter defines the number lists that are used to store the external numbers in the
common pool. For every user the IABD numbers with sequence number 0, 1, 2, ... 9 and the
LENR number are stored in the first list. The IABD numbers with sequence number 11, 12,
13 ... 19 are stored in the second list etc. So every user needs at least one list and utmost ten
lists. A good estimation for max number of IABD list entries=(max number of IABD elements
(=LOBOUND036)) /3).
BOUND038: MAX NUMBER OF INTERVAL TIMES
All: (32 ... 32): 32

The max number of interval times that can be inserted per facility
An interval consists of two interval times (on time and off time). The facility clock operates on
a week's cycle. The number of intervals that can be inserted in the table of the facility clock
(per facility) is (max number of interval times)/2. So, per week and per facility the clock can
make max number of interval times switches.
BOUND039: MAX NUMBER OF SYSTEM TIME BROADCAST SUBSCRIBERS
All: (1 ... 10): 4

A process can take or cancel a subscription to (periodically) receiving system time messages.
This parameter gives the maximum number of processes that have a subscription to system
time messages at the same time.
BOUND040: MAX NUMBER OF ABSOLUTE TIME BROADCAST SUBSCRIBERS
All: (1 ... 10): 4

A process can take or cancel a subscription to (periodically) receiving absolute time messages
once per minute. This parameter gives the maximum number of processes that have a
subscription to absolute time messages at each minute at the same time.
82
BOUND041: MAX NUMBER OF CORRECT ABSOLUTE TIMERS BROADCAST
SUBSCRIBERS
All: (2 ... 10): 4

A process can take or cancel a subscription to receiving correct absolute timers messages.
This. parameter gives the maximum number of processes that have a subscription to correct
absolute timers messages at the same time.
Note that the minimum value of the boundary must be the number of projected CMs + 1.
BOUND042: SAS INTERUNIT COMMUNICATION GUARDING TIME
Ccs4: (6 ... 6): 6

Ccss: (6 ... 6): 6
Every SAS interunit communication guarding time times SAS interunit communication
schedule time seconds, the SAS communication handler checks the hello guarding with
another unit.
BOUND043: SAS INTERUNIT COMMUNICATION IMMEDIATE RECOVERY

TIME
Ccs4: (1 ... 1): 1

Ccss: (1 ... 1): 1
After SAS interunit communication immediate recovery time times SAS interunit
communication schedule time seconds, the SAS communication handler attempts to recover
communication with another unit when the communication has been lost for the first time.
BOUND044: SAS INTERUNIT COMMUNICATION RECOVERY TIME
Ccs4: (60 ... 60): 60

Ccss: (60 ... 60): 60
After SAS interunit communication recovery time times SAS interunit communication
schedule time seconds, the SAS communication handler attempts to recover lost
communication with another unit when immediate recovery has failed.
BOUND045: MAX NUMBER OF UNIT REACHABILITY SUBSCRIBERS
Ccs4: (20 ... 20): 20

Ccss: (20 ... 20): 20
Defines the number of subscription entries in the administration of the SAS communication
handler for the unit reachability change broadcast message.
83
BOUND046: MAX NUMBER OF EXTENSION DNRS
Ccs4: (2 ... 9984): 200

Ccss: (2 ... 9984): 200
Cpu3000: (2 ... 1152): 200
Specifies the ultimate number of DNRs related to extension circuits (both ISDN and non-
ISDN, including hardwareless and basic DNRs) that can be present in a unit. This boundary
should be given the same value as max number of non-ISDN extensions (LOBOUND010).
NEBOUND047: MAX NUMBER OF SUB-SIGNALLING GROUPS FOR EL@Ns
All: (0 ... 255): 1

This boundary defines the number of Sub-Signalling groups for the ErgoLine@Net terminals.
In the OM command the sub-signalling has to be specified in hexadecimal format : 0100 ...
01FE. It also determines the highest signalling group number, so in the resulting signaling group
number 01xx: xx can never be larger than (NEBOUND047 - 1).
NEBOUND048: THRESHOLD FOR SILENT ALARMS LIMITED BY TIME
All: (1 ... 65000): 624

Specifies the reside time (in units of seconds) of concerned silent alarms.
If the boundary value (time) is exceeded by the time a silent alarm of category "limited by time"
resides in the silent queue (faults in central apparatus), the concerned alarm is moved to the
minor queue.
NEBOUND049: THRESHOLD FOR SILENT ALARMS LIMITED BY AMOUNT
All: (1 ... 65000): 2

Specifies the maximum number of concerned silent alarms.
If the boundary is exceeded. by the number of silent alarm reports of category "limited by
amount" residing in the silent alarm queue (faults in apparatus of pools), an additional alarm
report "silent alarm number threshold exceeded" is created and stored in the minor or major
alarm queue (depending on the project data).
LOBOUND050: MAX NUMBER OF MULTI FUNCTION BOARDS
All: (1 ... 1): 1

This parameter describes the maximum number of multi-function-boards that are available in
a unit. Multi-function-boards are boards that contain more than one function.
84
They are treated differently than the normal boards.
LOBOUND051: MAX NUMBER OF RKT SDTs
Ccs4: (0 ... 512): 6

Ccss: (0 ... 512): 6
Cpu3000: (0 ... 255): 6
Specify the ultimate number of RKTs.
This parameter defines the area to be reserved for keytone receiver data. The RKT circuits
are present on the RST-KD and PMC:
RST-KD : 3 RKTs and 3 dial tone switches
PMC-MC : 6 RKT circuit
PMC-HR : 6 RKT circuits
PMC-LU : 3 RKT circuits
Depends mainly on the number of extensions, as a guide counts:
500 extensions : 12
1000 extensions : 18
LOBOUND052: MAX NUMBER OF SKT RDTs
Ccs4: (0 ... 512): 4

Ccss: (0 ... 512): 4
Cpu3000: (0 ... 255): 4
Specify the ultimate number of SKTs - RDTs.
85
This parameter defines the area to be reserved for keytone sender data. and receiver dialtone
data. Both type of circuits are present on the RST-KD and PMC:
RST-KD : 2 SKT - RDT circuits
PMC-MC : 4 SKT - RDT circuits
PMC-HR : 4 SKT - RDT circuits
PMC-LU : 2 SKT - RDT circuits
500 extensions :8
LOBOUND053: MAX NUMBER OF TRUNKS
Ccs4: (0 ... 3000): 4

Ccss: (0 ... 3000): 4
Cpu3000: (0 ... 500): 4
Specify the ultimate number of non-ISDN trunks.
This parameter defines the area to be reserved for exchange line circuit data, tie line circuit
data and conference circuit data. There may not be projected more than 100 trunks in one
route (search time limit). The maximum number of 3000 is only allowed for "special project
systems", which have a low traffic intensity per trunk line.
LOBOUND054: MAX NUMBER OF CONVERTORS
All: (0 ... 255): 4

Define the maximum number of converters (modems).
86
This parameter defines the area to be reserved for MLU data.
LOBOUND055: MAX NUMBER OF IN MFCs
Ccs4: (0 ... 512): 4

Ccss: (0 ... 512): 4
Cpu3000: (0 ... 255): 4
Specify the ultimate number of RST-IMs.
This parameter defines the area to be reserved for MFC receiver data.
LOBOUND056: MAX NUMBER OF OUT MFCs
Ccs4: (0 ... 512): 4

Ccss: (0 ... 512): 4
Cpu3000: (0 ... 255): 4
Specify the ultimate number of RST-OMs.
This parameter defines the area to be reserved for MFC sender data.
LOBOUND057: MAX NUMBER OF BUNDLES
All: (1 ... 255): 4

Define the maximum number of bundles.
This parameter defines the area to be reserved for bundle data which is applied in external
routes. The required number depends on the external routing. As a guide the following can be
used:
- when number of routes <5 then 2 bundles per route;

- when number of routes >5 then 1 bundle per route.
LOBOUND058: MAX NUMBER OF INTERUNIT BUNDLES
Ccs4: (0 ... 255): 4

Ccss: (0 ... 255): 4
Cpu3000: (0 ... 255): 1
Define the maximum number of interunit bundles.
This parameter defines the area to be reserved for bundle data of bundles which are applied
in interunit routes.
87
BOUND059: MAX NUMBER OF ROUTES
All: (1 ... 255): 5

Specify the ultimate number of routes within this unit.
This parameter defines the area to be reserved for route group data.
NEBOUND060: MAX NUMBER OF PAGING ROUTES IN SYSTEM
All: (5 ... 200): 5

Define the maximum number of paging routes used in the system.
This parameter defines the room to be reserved for paging routes. A paging route is always
directed to a paging unit. Within a paging area only one unit has paging hardware equipment.
The local paging service will direct calls for paging always to that unit.
LOBOUND061: MAX NUMBER OF INTERUNIT ROUTES
Ccs4: (0 ... 255): 4

Ccss: (0 ... 255): 4
Define the maximum number of interunit routes.
This parameter defines the area to be reserved for interunit route group data.
LOBOUND062: MAX NUMBER OF INTERUNIT LINES
Ccs4: (0 ... 3315): 255

Ccss: (0 ... 3315): 255
Define the maximum number of interunit lines.
This parameter defines the area to be reserved for interunit line data: (number of units - 1)255.
NEBOUND063: MAX NUMBER OF ROUTES IN SYSTEM
All: (0 ... 255): 5

Specify the ultimate number of routes within the system.
This parameter defines the area to be reserved for route network data.
BOUND064: MAX NUMBER OF MSG WAITING REQUESTS IN QUEUE
All: (0 ... 255): 255

Specify the ultimate number of msg waiting requests stored in the msg waiting service.
88
This parameter defines the data space to be reserved for msg waiting requests in the msg
waiting service.
LOBOUND065: MAX NUMBER OF VIRTUAL PAGING CODES
All: (0 ... 100): 8

Specify the ultimate number of virtual paging codes.
This parameter defines the room to be reserved for the specification of virtual paging codes.
The expression 'virtual paging' is used in case a public address (PA) system is used in
combination with a paging software arrangement. The operator can store a call in a paging
(waiting) queue by dialling a paging prefix. Paging service will then provide a ranknumber.
Next, the call is announced by asking the wanted party to dial the paging answer prefix and the
ranknumber. When the call is answered or the waiting party releases the ranknumber is
returned to the service and can be used again. This parameter defines the maximum number
of calls that can be stored in this way.
If this option is required then also a virtual bundle must be assigned and ranknumbers have to
be assigned to this bundle. This option can be used together with other paging configurations.
LOBOUND066: MAX NUMBER OF PAGING LINES
All: (0 ... 255): 8

Specify the ultimate number of lines used for paging.
This parameter defines the room to be reserved for paging line data. This number determines
the maximum number of hardware paging circuits which can be applied. The only possible
interface is ESPA.
LOBOUND067: MAX NUMBER OF ATF CALLS ON ROUTE
All: (0 ... 255): 5

Specify the maximum number of Automatic Trunk Find (ATF) calls possible per route. An ATF
call is an Automatic Ring Back call or a Camp On Busy call on a trunk route as result of trunk
congestion.
LOBOUND068: MAX NUMBER OF SIMULTANEOUS ARB CALLS PER

INITIATOR
All: (0 ... 25): 5

Specify the maximum number of simultaneous ARB calls per initiator. An ARB call is an
89
Automatic Ring Back call started by an extension user (the initiator).
LOBOUND069: MAX NUMBER OF ATF CALLS IN UNIT PER TYPE
All: (0 ... 255): 25

Specify the maximum number of Automatic Trunk Find (ATF) calls possible per ATF type in a
unit. This parameter defines the room to be reserved for ATF Automatic Ring Back (ARB) data
and ATF Camp On Busy (COB) data in one unit. An ATF call is an ARB call or a COB call on a
trunk route as result of trunk congestion. The different types of ATF are NO ATF, ATF ARB
and ATF COB. The ATF type is route data so an ATF ARB pool and an ATF COB pool can
exist at the same time in one unit.
NEBOUND070: MAX NUMBER OF ANALYSIS TREES
All: (10 ... 255): 15

Define the maximum number of analysis trees.
This parameter defines the area to be reserved for analysis trees. Together with the number
of pyramids (NEBOUND071) the size of the number analysis area is determined by these two
parameters.
The number of analysis trees determines the number of starting points to enter a different
numbering scheme. Thus the number of analysis trees defines the number of first pyramids.
Such a starting point is created if a not yet existing analysis tree number (ATN) is assigned at
the routing data or at the number analysis.
NEBOUND071: MAX NUMBER OF ANALYSIS PYRAMIDS
All: (10 ... 2000): 30

Define the maximum number of analysis pyramids.
This parameter defines the area to be reserved for analysis pyramids. See also previous
parameter. The number of pyramids defines the maximum total of pyramids which can be
used to define the analysis trees. The creation of pyramids and the definition of the outlets is
arranged internally. As soon as a digit string is assigned to an ATN (analysis tree number) the
necessary pyramids are added/adapted.
NEBOUND072: MAX NUMBER OF ANALYSIS GROUPS
All: (5 ... 255): 5

Maximum number of analysis groups. This parameter defines the area to be reserved for
analysis group data. The analysis group facility provides the facility to create different number
90
analysis per group of extension users.
NEBOUND073: MAX NUMBER OF DNRs IN THE SYSTEM
All: (1125 ... 65530): 1125

This parameter defines the area to be reserved for storing internal numbers. The length of the
dnr-lc table is restricted to the maximum number of DNRs in the system that can be defined.
This parameter defines the area to be reserved for storing DNRs (sum of extension DNRs,
Operator DNRs and Group DNRs).
For a stand-alone system the minimum value of this boundary 73 depends on the sum of
boundary 46 (max number of extension dnrs), boundary 16 (max number of operators) and
boundary 17 (max number of groups).
For a multi-unit system the minimum value of this boundary 73 depends on the sum of these
boundaries over all the units
NEBOUND074: MAX NUMBER OF OUTGOING DESTINATIONS
All: (1 ... 255): 5

Define the maximum number of outgoing destinations.
This parameter defines the area to be reserved for outgoing destination data.
NEBOUND075: REACTIVATING BUZZER TIME
All: (0 ... 30): 15

The time-limit after which the call buzzer has to be reactivated.
Expiry of this timer is checked on expiry of NETIMER038.
The reactivating buzzer facility is performed for calls which are waiting for assistance at an
operator position longer than a period equal to this parameter.
NEBOUND076: MAX NUMBER OF TMS SLOTS
All: (0 ... 255): 20

This parameter defines the total number of slots in the windows used in the communication
between TMS (SSM) and ISPBX.
This projectable parameter defines the maximum number of slots for both the communication
to TMS (SSM) and the communication from TMS (SSM). When the parameter has value 0, then
91
no communication is possible with TMS (SSM) at all. When the parameter is 20, then a
maximum of 1 slot per window is possible.
NEBOUND077: MAX NUMBER OF LINES OF VOIP DATA
All: (0 ... 255): 1

This boundary defines the average number of lines of VoIP data in the signalling groups for the
ErgoLine@Net terminals. This boundary is an average, meaning that when it is set to 100, you
can have one signalling group using 90 lines and another signalling group using 110 lines, as long
as the average usage is not more than 100 lines.
BOUND078: TMS GUARDING TIME
All: (60 ... 300): 120

This parameter defines the maximum allowable time (in minutes) for processing of a request
that is sent to TMS (SSM) by TMS (SSM) Server. When a request is not answered within TMS
GUARDING TIME minutes and this time-out is detected by TMS Server then the involved
service will be re-initialized.
BOUND079: MAX NUMBER OF PIVS IN OMDM
All: (1 ... 100): 10

Determines the number of PIVs to be stored in OMDM.
This boundary determines the size of the structure in which the PIVs of detached user
processes are stored in OMDM.
BOUND080: MAX NUMBER OF UNITS
All: (14 ... 14): 14

Define the maximum number of units per system.
This parameter defines the area to be reserved for multi unit data.
NEBOUND081: LIMIT TIME OF CALL IN QUEUE
All: (0 ... 65000): 65000

Define the time-limit after which the second overload level is reached. The overload signalling
facility will be performed for calls which are waiting for assistance at an operator position. The
second overload level is reached whenever any call is waiting longer than a period equal to this
parameter.
92
LOBOUND082: MAX NUMBER OF CMs
All: (1 ... 1): 1

Define the maximum number of CMs.
This parameter defines the maximum number of CM shelves applied in this unit. This
information is used to validate the input of OM/PE data.
LOBOUND083: MAX NUMBER OF PMs
Ccss: (1 ... 31): 4

Ccs4: (1 ... 31): 4
Cpu3000: (1 ... 4): 4
Specify the ultimate number of PMs.
This parameter defines the maximum number of PMs applied in this unit. This information is
used to validate the input of OM/PE data.
Note that the maximum value is 8 in an upgraded SOPHO-S250/1000 with non compact PMs.
LOBOUND084: MAX NUMBER OF DEVICE PORTS
Cpu3000: (1 ... 9): 9

CCS
This parameter is not applicable for CCS systems : the maximum number of device ports in a
CCS system is defined by LOBOUND292.
CPU3000
Define the maximum number of V.24 ports.
When the VIC is connected to the CPU3000 the number of V.24 ports is doubled to 6.
Including the ports of the LBU, the DBU and the optional solid state disk device, this leads to
maximally 9 device ports.
BOUND085: MAX NUMBER OF DEVICES PER DEVICE PORT
Cpu3000: (10 ... 10): 10

CCS
This parameter is not applicable (n.a.) for CSM systems
93
CPU3000
Define the maximum number of devices (= the number of application types) on one port.
LOBOUND086: MAX NUMBER OF SCUs/SNSs
Ccs4: (2 ... 6): 6

Ccss: (2 ... 6): 6
Cpu3000: (1 ... 1): 1
CCS
This parameter defines the maximum number of switching network slices (SNS boards)
applied in this unit. The value of this boundary must be equal to the value of boundary 087,
because there is only one PCP chip per SNS board.
CPU3000
Define the maximum number of CSN-BCs in the system.
For systems with or without a CSN-BC the value is 1.
LOBOUND087: MAX NUMBER OF CIIs
Ccs4: (2 ... 6): 6

Ccss: (2 ... 6): 6
Cpu3000: (1 ... 1): 1
CCS
Defines the maximum number of PCP chips. This value must be equal to the value of boundary
086 (see description of boundary 086).
CPU3000
Define the maximum number of PCP chips.
This parameter defines the maximum number of PCP chips. This information is used to
validate the input of OM/PE data.
NEBOUND088: THRESHOLD FOR NUMBER OF FROZEN PROCESSES
All: (1 ... 99): 5

Dumps, caused by a frozen process, only generate silent alarms.
94
In case the number of frozen processes reaches the above mentioned threshold, alarm code
034, qualifier 001 will be generated. The counter (within the LOS) will be reset during any
system start, as only then frozen processes are released again.
NEBOUND089: MAXIMUM NUMBER OF CHANNELS PER CIU
All: (16 ... 16): 16

Maximum number of channels per CIU board.
BOUND090: MAX NUMBER OF COMMAND MODULES
All: (150 ... 1200): 1200

Cpu3000: (150 ... 1200): 1200
Maximum number of simultaneous loaded command modules.
This parameter defines the number of command modules that can be loaded in memory
simultaneously (by OMDM). Command modules are OM commands, OM subcommands and
SAS overlays. For memory size reasons, the number of command modules is limited. In case
a command module is requested that is not yet loaded in memory, but this maximum value is
reached, OMDM will automatically delete a previously loaded command module.
LOBOUND091: MAX NUMBER OF RESOURCE RELATIONS
Ccs4: (200 ... 12000): 200

Ccss: (200 ... 12000): 200
Cpu3000: (200 ... 10000): 200
Define the maximum number of resource relations.
This boundary defines the needed area for resource relations (hardware configuration
administration).
BOUND092: MAX NUMBER OF SIGNALLING GROUP BIT ITEMS
All: (100 ... 100): 100

Define the maximum number of signalling group bit items that can be changed.
This parameter defines the area to be reserved in the CPU for signalling group bit item
changes.
For this storage, area is to be reserved in bits and bytes:
BOUND092: number of bits to be edited.
95
BOUND093: number of bytes to be edited.
The ISPBX is equipped with a number of standard signalling groups. These groups are
programmed in the PPU/PMC firmware. For flexibility reasons some of the signalling group
properties (bits and bytes) can be changed. These changes are stored in the CPU and will be
copied to and become active in the PM at the moment the PPU/PMC is set into service.
The PPU/PMC has some limitations related to changing the signalling groups properties. These
are:
• Not more than 32 different signalling groups can be changed and

• the total property size (all bits + bytes) of the changed signalling groups may not exceed
the 1500 bytes.
Example:
Let the properties of signalling group A be 11 bits and 65 bytes.
Let the properties of signalling group B be 5 bits and 40 bytes.
Changing bits/bytes in signalling group A and in group B results in a total property size of
changed signalling groups of:
67 bytes in the signalling group A property (65 bytes + 11/8 bytes) and 41 bytes in the
signalling group B property (40 bytes + 5/8 bytes).
The total group property size becomes 67 +41 = 108 bytes.
Free memory available for other signalling groups which can be changed is 1500 - 108 = 1392
bytes.
BOUND093: MAX NUMBER OF SIGNALLING GROUP BYTE ITEMS
All: (100 ... 1500): 100

Define the maximum number of signalling group byte items that can be changed.
This parameter defines the area to be reserved for signalling group byte items that can be
changed; for further explanation see BOUND092.
BOUND094: MAX NUMBER OF SLAVE DATA ITEMS
All: (45 ... 45): 45

Define the maximum number of slave data items.
96
This parameter defines the number of slave data items related to the ATC chip.
BOUND095: MAX NUMBER OF TIME SOURCE ITEMS
All: (100 ... 250): 250

Define the maximum number of time source items.
This parameter defines the area in which the total number of time elements, used at the audio
specifications, is to be stored.
NEBOUND096: MAX NUMBER OF FUNCTION KEY MENUS
All: (1 ... 65534): 5

Define the maximum number of function key menus. This parameter defines the area to be
reserved for storing the function key and soft key menu data. See also boundaries 360 ... 363.
NEBOUND097: MAX NUMBER OF DEVICES IN SYSTEM
Ccs4: (30 ... 200): 50

Ccss: (30 ... 200): 50
Cpu3000: (30 ... 90): 90
Define the maximum number of devices in the system.
This parameter defines the area to be reserved for the devices in the system.
CPU3000: The maximum is the number of V.24 ports on the CPU3000 (LOBOUND084)
multiplied by the number of BCS channels on one port (LOBOUND085). The minimum value
of 30 is chosen.
NEBOUND098: MAX NUMBER OF TT LINES PER PAGE
All: (1 ... 99): 65

Define the required number of lines per page in the tollticketing output.
LOBOUND099: SAS AH DEFAULT ALARM DISTRIBUTION
All: (0 ... 3): 2

Define the alarm handler default distribution.
This parameter defines the default alarm distribution:
- 0 = main distribution frame (MDF);

- 1 = operator;
97
- 2 = operator, but if not present then to the MDF;
- 3 = operator and MDF.
By means of OM the alarms can be rerouted.
BOUND100: MAX NUMBER OF CP COMM HANDLER TRANSPORTS
All: (5 ... 10): 10

Max number of outstanding cp comm hndlr signals waiting for reply.
Each cp communication handler process can process "in parallel" a number of information
transport requests to a cp communication handler process in another unit.
The outstanding requests are administrated until the information transport to the requesting
unit is executed. The maximum number of outstanding information transport request is
defined by this parameter.
BOUND101: MAX NUMBER OF B BUTTONS
All: (4 ... 4): 4

Define the maximum number of B buttons. This boundary depends on the number of B
buttons defined in the CPU PPU interface: operator buttons.
BOUND102: NUMBER OF PASSWORDS
All: (51 ... 67): 67

Number of passwords related to:
- authority class (16 passwords).

Restriction on execute subcommands, commands and operator desk commands related
to the current OM device
- protection level (4x8=32 passwords).
File protection level related to the OM device.
There are four protection codes: New, Append, Read and Delete access (NARD).
There are eight protection levels for each protection code.
- degradation level (3 passwords).
Restriction level used for resource status manipulations.
- miscellaneous (16 passwords).
Other features that need passwords.
98
BOUND103: MAX LENGTH OF QUEUE INDICATION
All: (0 ... 15): 10

This parameter defines the maximum value of queue length shown at the operator desk.
BOUND104: LIMIT TIME OF ALREADY ANSWERED CALL IN QUEUE
All: (0 ... 65000): 65000

This parameter specifies the time in seconds after which "already answered calls" will be
signalled at operator users.
BOUND105: MAX NUMBER OF ROLLBACK EVENTS
All: (3 ... 3): 3

Used for resource rollback.
The number of rollback events sent over the operational eventpath by the rollback function
to force release of resources.
BOUND106: ROLLBACK RETRY COUNT FOR PORT ID
All: (255 ... 255): 255

The number of attempts of the rollback function to take a claimed resources with port-id after
rollback events are sent.
See also BOUND 110.
Note: Between successive attempts the function delays for "claim check delay time" seconds
(NETIMER 128).
BOUND107: ROLLBACK RETRY COUNT FOR NO PORT ID
All: (255 ... 255): 255

The number of attempts of the rollback function to take a claimed resources without port-id.
99
Note: Between successive attempts the function delays for "claim check delay time" seconds
(NETIMER 128).
BOUND108: MAX NUMBER OF PCT IPS
Ccs4: (80 ... 80): 80

Ccss: (40 ... 40): 40
Cpu3000: (5 ... 20): 20
Maximum number of concurrent pct interface processes.
BOUND109: MAX NUMBER OF FACILITY INTERVALS
All: (50 ... 50): 50

The max number of total interval times that can be inserted for all facilities together. For all
facilities the interval date, time, marks and par data is to be stored in an index table (one index
table per data item). The maximum number of items of all facilities together (=max number
of total interval times) defines the table length of the index table (=max number of facility
intervals).
BOUND110: ROLLBACK RETRY COUNT FOR CP2 OWNED PORT ID
All: (4 ... 255): 4

When a port is roll-backed (e.g. due to FRCOUT) and the port or process is not able to
honour the rollback request, per default it takes about 20 minutes to release the port.
After that a rollback failure dump is created and sometimes a restart occurs.
This time is determined by the value of BOUND 106 (Rollback retry count for port id)
multiplied by the value of NETIMER 128 (Claim check delay time). However most of the
rollbacks occur due to problems in the call processing area. A dump generated after 20
minutes has no signal history anymore and finding the cause of the problem is very difficult.
This boundary is used to specify how much the time between rollback and rollback failure
(creation of the dump) can be decreased for resources owned by Call Processing (CP2). With
the default setting of BOUND 110, a dump is created after 20 seconds (note that this is not
valid for ISDN trunk lines : this is still 20 minutes). The chance that more information is still in
the signal history is increased and offers more investigation possibilities.
NEBOUND111: DNR RADIX NUMBER
All: (10 ... 15): 10

This radix number determines the set of digits that are possible within an extension DNR.
100
The set starts at digit 0 up to the value of the radix number (0 . . . 9 in case radix=10). This
radix influences the size of hundred groups.
NEBOUND112: PROJECT NUMBER OF DIGITS
All: (10 ... 15): 12

This boundary determines the set of digits that can be dialled from extension or other
equipment (the maximum present size). No other digits may ever be dialled. The set starts at
digit 0 up to the value of the boundary (0 . . . # in case boundary=12).
This boundary influences the size of analysis pyramids.
NEBOUND113: MAX NUMBER OF EXTERNAL NUMBERS
All: (255 ... 255): 255

This boundary determines the possible number of digit strings leading to the analysis
conclusion "external number".
BOUND116: MAX NUMBER OF IAS TIMESLOTS
Ccs4: (30 ... 248): 30

Ccss: (30 ... 248): 30
Cpu3000: (30 ... 124): 30
This parameter identifies the maximum number of IAS timeslots within the system.
BOUND117: NUMBER OF FOUR DIGIT PACK
All: (5 ... 5): 5

This parameter represents the number of times a packet of four digits is needed to store an
external number. An external number is maximum 20 digits long, so five packets of four digits
are needed to store an external number.
BOUND118: MAX NUMBER OF TMS TRANSLATIONS
All: (256 ... 256): 256

This parameter defines the maximum number of translations for the translation between
equipment code and DNR and/or tone function, used in the communication between TMS
(SSM) and ISPBX.
BOUND119: MAX NUMBER OF STIMULI
All: (10 ... 255): 192
101
This parameter determines the size of the SAS stimulus buffer.
BOUND120: MAX NUMBER OF BATCH JOBS
All: (6 ... 6): 6

The maximum number of batch jobs that have been submitted and did not yet expire or have
not been cancelled by the user.
BOUND121: CB POOL OCCUPANCY THRESHOLD
All: (85 ... 85): 85

Used for CM load sensing.
When the number of occupied control blocks exceeds the given percentage threshold, the
system stops accepting new calls and an alarm is generated.
BOUND122: STACK POOL OCCUPANCY THRESHOLD
All: (65 ... 65): 65

When the number of occupied stacks exceeds the given percentage threshold, the system
stops accepting new calls and an alarm is generated.
BOUND123: SIGNAL POOL OCCUPANCY THRESHOLD
All: (18 ... 18): 18

When the number of occupied signal packets exceeds the given percentage threshold, the
BOUND124: EPD OCCUPANCY THRESHOLD
All: (80 ... 80): 80

When the number of occupied eventpath directory entries exceeds the given percentage
threshold, the system stops accepting new calls and an alarm is generated.
BOUND125: THRESHOLD START STOP PATS
All: (4 ... 10): 10
102
This parameter controls Periodic Autonomous Testing
When the number of stimuli in the SAS-stimulus buffer exceeds "threshold start stop pats"
stimuli, then the SAS-CTRL will switch off PATS. When the number of stimuli in the SAS-
stimulus buffer decreases below "threshold start stop pats" stimuli, then the SAS-CTRL will
switch on PATS again.
BOUND126: MAX MEMORY SIZE PRESERVED FOR OVERLAYS
Ccs4: (128 ... 128): 128

Ccss: (32 ... 32): 32
Cpu3000: (128 ... 128): 128
Before memory is reserved for containing diagnostic data for the system dump, an amount of
memory is preserved. Afterwards this memory is released again to be sure to have memory
at least to load a few (not permanent) overlays.
BOUND127: CB POOL OCCUPANCY HYSTHERESIS
All: (7 ... 7): 7

When the number of occupied control blocks has exceeded the threshold, the system accepts
new calls only when the occupation level has dropped below: ("threshold"-"hystheresis")%.
BOUND128: SIGNAL POOL OCCUPANCY HYSTHERESIS
All: (3 ... 3): 3

When the number of occupied signal packets has exceeded the threshold, the system accepts
new calls only when the occupation level has dropped below: ("threshold"-"hystheresis")%.
BOUND129: STACK POOL OCCUPANCY HYSTHERESIS
All: (5 ... 5): 5

When the number of occupied stacks has exceeded the threshold, the system accepts new
calls only when the occupation level has dropped below: ("threshold"-"hystheresis")%.
BOUND130: EPD OCCUPANCY HYSTHERESIS
All: (10 ... 10): 10
103
When the number of occupied event path directory entries has exceeded the threshold, the
system accepts new calls only when the occupation level has dropped below: ("threshold"-
"hystheresis")%
BOUND131: MAX NUMBER OF DIRECTED CALLS
All: (1 ... 1): 1

Define the maximum number of directed calls.
This parameter defines the number of simultaneous calls over pre-defined resources.
LOBOUND132: MAX PAGING COB ON CODE Q LENGTH
All: (0 ... 30): 5

This parameter gives the ultimate number of entries in a paging COB on code queue. In the
paging service is a COB queue for urgent and non urgent calls to real paging that meet a busy
paging code. The number of entries in the total COB on code queue is set by max paging COB
queue length. Room is reserved for the ultimate number of entries.
BOUND133: OPERATOR METERING QUEUE THRESHOLD
All: (1 ... see description): 40

Define the maximum number of queued metering results.
This boundary determines the ultimate number of metering results to be queued in operator
service (total for all operators in one unit). Because every result takes two control blocks, this
boundary can avoid a control block congestion caused by operator metering.
BOUND134: DEFAULT EXTENSION BSPT
All: (0 ... 98): 95

This parameter defines the default BSPT for extensions. This BSPT should contain the default
extension IBSC.
BOUND135: MAX NUMBER OF MAT REQUESTS
All: (64 ... (max. number of stimuli x 2/3)): 64

This parameter is used for controlling the max number of request for MAnually controlled
Testing (MAT) in the SAS stimulus buffer.
104
BOUND136: SAS AH RESOURCE PROBATION INTERVAL
All: (0 ... 900): 900

This parameter determines the time period, in which a new occurrence of an error on a
recovered resource will lead to definitive isolation of the resource.
LOBOUND137: MAX NUMBER OF PAGING Q ENTRIES
All: (0 ... 100): 10

Each paging route with "meet-me" has a field to store paging calls that are accepted.
Such a call is waiting to be picked up, but it is also possible that the call is not yet transmitted
by the paging transmitter (paging code "busy" or paging transmitter not yet available for
sending, because it is busy with another call).
The total number of entries in the queue and the meet me field is limited by this boundary.
LOBOUND138: MAX PAGING COB Q LENGTH
All: (0 ... 10): 5

This parameter gives the ultimate number of entries in a paging COB queue. In the paging
service each bundle has a COB queue. The number of entries in each COB queue is limited
by max paging COB queue length.
BOUND139: MAX NUMBER OF TT DATA BLOCKS
All: (1 ... 600): 290

Defines the maximum number of used toll-ticketing data blocks. Each time call processing
needs a TT data block, it asks one from toll-ticketing SP. If the total number of used TT data
blocks reaches its maximum, the caller will get congestion.
BOUND141: MAIN MEMORY HARD FAULT THRESHOLD
All: (0 ... 65535 (H'FFFF)): 1000

This value is the threshold at which an alarm report is generated, indicating that the number
of hard faults in the main memory of the reported CM CPU slice is too great and the memory
should be replaced at the next maintenance visit.
BOUND142: MAIN MEMORY SOFT FAULT THRESHOLD
All: (0 ... 65535 (H'FFFF)): 1000

This value is the threshold at which an alarm report is generated, indicating that the number
105
of soft faults in the main memory of the reported CM CPU slice is too great and the memory
should be replaced at the next maintenance visit.
BOUND143: ACD FORCED ABSENT GUARDING TIME
All: (600 ... 3600): 600

This timer is used as an overall guarding timer for SOPHO CallManager ACD. If the
projectable Forced Absent timer is not defined by means an OM command (CRGRPA or
CHACDD) then the system sees to it that for a system limited time the member is rung. This
system limited time is the ACD FORCED ABSENT GUARDING TIME. This timer has been
defined in order to be sure that the forced absent facility does not allocate all kinds of
resources for a long time.
BOUND144: MAX NUMBER OF TMS WINDOWS
All: (10 ... 10): 10

This parameter defines the total number of windows used in the communication between
TMS (SSM) and ISPBX.
NEBOUND145: TMS MESSAGE WAITING TYPE
All: (0 ... 2): 0

(message waiting type 0 . . . message waiting type 2): message waiting type 0 This system
parameter defines the type of message waiting that will be used for TMS (SSM) purposes. The
values of this parameter are related to the values of the mode TMS (SSM) message waiting
types.
BOUND146: MAX NUMBER OF BARRED NUMBERS
All: (50 ... 50): 50

Defines the maximum number of barred external numbers.
This parameter defines the area to be reserved for storing barred external numbers. The
maximum number of barred external numbers is fixed. The numbers to be barred can be
assigned by means of a dedicated OM procedure. Thus above the 'normal' blocking via traffic
class investigations this facility provides a possibility to bar numbers for all parties. For example
an outgoing numbering scheme at which local calls of any 6 digits are allowed, except the digits
891317. In this case the specification of the barred digits in the pyramids is quite complex and
memory consuming.
It is much easier to specify allowance for every 6 digits and to define 891317 as a barred
number by means of OM. This OM can also be used to free the blocked digit string again. It is
106
especially useful for external numbers which have to be blocked temporarily only.
BOUND147: MAX NUMBER OF OBSERVED GROUPS
All: (10 ... 10): 10

Specify the ultimate number of group arrangements that can be observed by traffic
measurements.
This parameter defines the area to be reserved for traffic measurement data for observed
groups.
BOUND148: MAX NUMBER OF OBSERVED ROUTES AND BUNDLES
All: (50 ... 50): 50

Specify the ultimate number of exchange and tieline routes+interunit routes+paging
routes+exchange and tieline bundles+interunit bundles that can be observed by traffic
measurements.
This parameter defines the area to be reserved for traffic measurement data for observed
routes and bundles.
BOUND149: MAX NUMBER OF OBSERVED SPECIFIC CONVERTERS
All: (1 ... 1): 1

Specify the ultimate number of converters that can be observed by traffic measurements. This
parameter defines the area to be reserved for traffic measurement data for observed
converters.
BOUND150: MAX NUMBER OF PCTS PER PM
All: (512 ... 512): 512

This boundary describes the physical maximum number of PCTs per Peripheral Module.
BOUND151: MAX NUMBER OF INTERUNITS TO UNIT
Ccs4: (256 ... 256): 256

Ccss: (256 ... 256): 256
Cpu3000: (1 ... 1): 1
This boundary describes the maximum number of channels within a Switching Network Link
which can be used for interunit messages to one other unit.
107
BOUND152: SYSTEM LIMITED NUMBER OF UNITS
All: (1 ... 14): 14

Define the system limited number of units.
This boundary is a system parameter and its value is constant.
BOUND153: SYSTEM LIMITED NUMBER OF BOARD POSITIONS
All: (0 ... 29): 29

Define the system limited number of board positions per shelf.
This parameter is a system parameter and its value is constant.
BOUND154: SYSTEM LIMITED NUMBER OF SHELVES (PER CABINET)
Ccs4: (4 ... 4): 4

Ccss: (4 ... 4): 4
Cpu3000: (1 ... 4): 2
This boundary is a system parameter.
BOUND155: SYSTEM LIMITED NUMBER OF PCT BOARDS PER PM
All: (EMPTY ... EMPTY): 24

This boundary describes the maximum number of boards within a Peripheral Module which
contains PCTs. Boards positioned left of the PSC as well as boards positioned right of the PPU
are considered (with power supply boards excluded). This means that DTU's are also
considered to be PCT boards.
BOUND156: SYSTEM LIMITED NUMBER OF BICs PER PM

This boundary describes the maximum number of Break-In Circuits per PM.
BOUND157: SYSTEM LIMITED NUMBER OF SCUs
Ccs4: (EMPTY ... EMPTY): 6

Ccss: (EMPTY ... EMPTY): 6
Cpu3000: (EMPTY ... EMPTY): 1
This boundary describes the physical maximum number of switching network slice (SNS)
positions in a CSM shelf. For CPU3000 systems only one CSN-BC is allowed.
108
BOUND158: SYSTEM LIMITED NUMBER OF CIRCUITS PER BOARD

Define the system limited number of PCT circuits per board.
BOUND159: SYSTEM LIMITED NUMBER OF VIRTUAL RESOURCES

System limited number of virtual resources per unit.
A virtual resource is a node in the hardware configuration tree: virtual resources have no
external representation (EHWA, external status). The hardware configuration commands
have this value as a upper limit.
BOUND160: SYSTEM LIMITED NUMBER OF DISPLAY MEMBERS

Define the maximum number of display members in a multi access group.
This parameter defines the number of members in a multi access group that can have a status
display facility. This display facility is only possible on SOPHO Business telephones. This limit
is due to a system constraint (amount of processing to update all LED's of the specified
SOPHO Business telephones). This boundary is a system parameter and its value is constant.
BOUND161: SYSTEM LIMITED NUMBER OF CONN PARTS PER PM
Ccs4: (2 ... 2): 2

Ccss: (2 ... 2): 2
Cpu3000: (4 ... 4): 4
The PM-T-switch of the PMC-MC/HR/LU is not fully interconnectable. That is that it can not
interconnect each inlet and each outlet.
Ports which can be interconnected by the PM-T-switch are defined to be within the same
connectability part. This parameter defines the maximum number of connectable parts within
a PM. The system boundary is to be set to the maximum value possible in the entire unit.
109
BOUND162: SYSTEM LIMITED NUMBER OF SNLS PER SCU

Cpu3000: (1 ... 8): 8
CCS
This boundary describes the physical maximum number of links per switching network slice.
CPU3000
Systems with a CSN : this boundary describes the physical maximum number of outlets on the
CSN-BC board (8).
Systems without a CSN : this boundary describes the physical maximum number of outlets on
the PMC-MC master board (2).
BOUND163: SYSTEM LIMITED NUMBER OF DTUs PER PM

This boundary describes the maximum number of DTU boards (primary rate interface) that
can be mounted within a Peripheral Module.
BOUND164: SYSTEM LIMITED NUMBER OF CRTs PER BOARD

This boundary describes the maximum number of non-PCT (logical) circuits on boards.
BOUND165: SYSTEM LIMITED NUMBER OF CM SLICES PER CM

This boundary describes the physical maximum number of CPU slices in a CSM.
BOUND166: SYSTEM LIMITED NUMBER OF CHANNELS PER SNL

CCS
110
This boundary describes the physical maximum number of 64 kbit/s channels in a 2 Mb/s
switching network link.
CPU3000
This boundary describes the physical maximum number of 64 kbit/s channels in a 3x4 Mb/s
switching network link.
BOUND167: SYSTEM LIMITED NUMBER OF CHANNELS PER PCP-CHIP

This boundary describes the maximum number of control channels per PCP-chip.
BOUND170: SYSTEM LIMITED NUMBER OF SMs

This boundary describes the maximum number of Switching Modules in the system.
BOUND171: SYSTEM LIMITED NUMBER OF CSGs PER SM

This boundary describes the maximum number of Clock and Signal Generators in a Switching
Module.
BOUND172: SYSTEM LIMITED NUMBER OF SWITCH AND SENSE PER CIE

This parameter indicates the system limited number of switch and sense connections on the
CIE for external use. A CIE contains 10 switch - and 13 sense points.
BOUND174: SYSTEM LIMITED NUMBER OF CABINETS

Cpu3000: (1 ... 4): 1
This boundary defines the system limited number of cabinets per unit.
111
BOUND175: MAXIMUM NUMBER OF CIEs
Ccs4: (1 ... 4): 2

Ccss: (1 ... 4): 2
This boundary defines the maximum number of CIE boards in a CSM system. The number of
Backup Interface Modules (BIMs) is derived from this boundary value as well.
BOUND176: SYSTEM LIMITED NUMBER OF FUNCTION KEY LEVELS

Number of levels per programmable SOPHO Business telephone function key.
BOUND177: SYSTEM LIMITED NUMBER OF ESUs PER PM

This parameter indicates the system limited number of Emergency Switch over Units (ESU),
that can functionally be located within one PM shelf.
BOUND178: SYSTEM LIMITED NUMBER OF CRU ENTRYS PER SM

This boundary describes the maximum number of clock reference entries.
BOUND179: SYSTEM LIMITED NUMBER OF SNCS PER CONN PART
Ccs4: (128 ... 128): 128

Ccss: (128 ... 128): 128
Cpu3000: (96 ... 96): 96
The system parameter defines the maximum number of switching network channels defined
per PM connectability part. In fact: (nbr of sncs per conn part) = (nbr of snls per conn part)
(nbr of sncs per snl).
BOUND180: SYSTEM LIMITED NUMBER OF AUTHORITY CLASS INDEXES
All: (16 ... 16): 16

This boundary describes the maximum number of authority class indexes.
BOUND181: SYSTEM LIMITED NUMBER OF LEVEL 0 FK
All: (54 ... 54): 54
112
Specify the number of function keys for level 0 of the digital extension.
This parameter defines the number of level 0 function keys present on a digital extension.
BOUND182: SYSTEM LIMITED NUMBER OF LEVEL 1 FK
All: (66 ... 66): 66

Specify the number of function keys for level 1 of a digital extension.
This parameter defines the number of level 1 function keys present on a digital extension.
BOUND183: SYSTEM LIMITED NUMBER OF SOFTKEYS
All: (45 ... 60): 45

Specify the number of softkeys of a digital extension.
This parameter defines the number of softkeys (facility keys) present on a digital extension.
BOUND189: SYSTEM LIMITED NUMBER OF SINGLE DOWNLOADS
All: (6 ... 6): 6

This is a system parameter which defines the maximum number of Flash-EPROM files
concurrent open for download in one unit.
BOUND190: SYSTEM LIMITED NUMBER OF PMCs PARALLEL DOWNLOADED
Ccs4: (31 ... 31): 31

Ccss: (31 ... 31): 31
Cpu3000: (8 ... 8): 8
This system parameter defines the maximum number of PMCs concurrently busy with a
parallel download action.
BOUND191: SYSTEM LIMITED NUMBER OF SNLs PER CONN PART
All: (4 ... 4): 4

This system parameter defines the maximum number of switching network links possible to
be projected to a single connectability part. Since the number of connectability parts of a
PM1100 is 2, it is possible to project a maximum of 8 SM-PM links to the PM1100. For the
description of "connectability part" refer to LOBOUND161 (system limited number of conn
parts per PM).
113
BOUND192: MAX NUMBER OF SELECTIVE ANSWERING EXTENSIONS
All: (0 ... 40): 20

This system parameter defines the maximum number of extensions that can be assigned the
selective call answering facility.
BOUND193: NUMBER OF CALL POSITIONS PER EXTENSION
All: (1 ... 10): 8

This system parameter defines the maximum number of call positions an extension, with the
selective answering facility assigned, can hold.
BOUND194: MAX NUMBER OF SIMULTANEOUS ARB CALLS PER DEST.
All: (0 ... 25): 5

This parameter defines the maximum number of simultaneous ARB calls per destination.
BOUND195: MAX NUMBER OF SIMULTANEOUS ARB DESTINATIONS
Ccs4: (0 ... 512): 5

Ccss: (0 ... 512): 5
Cpu3000: (0 ... 255): 5
This parameter defines the maximum number of extensions that can be assigned ARB
destination simultaneously.
BOUND196: SYSTEM LIMITED NUMBER OF SNLS PER PMC
All: (4 ... 4): 4

This parameter defines the maximum number of SNLs per PMC. This parameter is a system
parameter and its value is fixed.
BOUND197: SYSTEM LIMITED NUMBER OF CHANNELS PER RPM-IU-SNL
All: (32 ... 32): 32

This parameter defines the maximum number of SNLS per PMC. This parameter is a system
parameter and its value is fixed.
BOUND198: SYSTEM LIMITED NUMBER OF SNCS PER RPM-IU-SNL CONN

PART
All: (128 ... 128): 128

This parameter defines the maximum number of SNCs (Switching Network Channels) per
114
remote PM or remote interunit connectivity part. This parameter is a system parameter and
its value is fixed.
BOUND199: SYSTEM LIMITED NUMBER OF PORTS ON BIM

This boundary defines the number of (fixed and variable) device-ports that are available on a
Backup and Interface Module (BIM).
BOUND202: MAX NUMBER OF CONTROL BLOCKS
Ccs4: (2050 ... 6150): 2050

Ccss: (950 ... 2050): 950
Cpu3000: (950 ... 2050): 950
This parameter describes the maximum number of control blocks that are available in a unit.
Control blocks are blocks of memory, used for call setup, for the creation of static and
dynamic processes etc. The number of calls that can be made simultaneously, depends also on
the value of this boundary. The number of control blocks used for static and dynamic
processes is normally about 150.
The number of simultaneous calls can be calculated by dividing the remaining number of free
control blocks by 2. So for the default value 950 the number of simultaneous calls will be about
(950-150) / 2 = 400. For systems with e.g. a lot of permanent data connections the number
of control blocks can be increased.
BOUND203: MAX NUMBER OF SIGNAL PACKETS
Cpu3000: (1920 ... 1920): 1920

Ccss: (960 ... 960): 960
Ccs4: (1920 ... 1920): 1920
This parameter describes the maximum number of signal packages that are available in a unit.
Signal packages are used for sending messages between two processes in a single unit or
between processes in different units of a iS3000 network.
BOUND204: MAX NUMBER OF SHORT DATABLOCKS
Ccs4: (150 ... 512): 150

Ccss: (50 ... 50): 50
Cpu3000: (30 ... 50): 50
This parameter describes the maximum number of short datablocks that are available in a unit.
115
A short data block is used by an extension, which is in dial phase. As a result, this parameter
determines the number of extensions which can be in dial phase simultaneously.
Consider to raise this parameter value, if the number of available RKTs is substantially higher
than this parameter value.
BOUND205: MAX NUMBER OF LONG DATABLOCKS
Ccs4: (480 ... 700): 480

Ccss: (340 ... 340): 340
Cpu3000: (200 ... 480): 340
This parameter describes the maximum number of long datablocks that are available in a unit.
Also refer to BOUND139.
BOUND206: MAX NUMBER OF USER STACKS
Ccs4: (160 ... 480): 160

Ccss: (75 ... 100): 80
Cpu3000: (75 ... 100): 80
This parameter describes the maximum number of user stacks that are available in a unit.
LOBOUND207: MAX NUMBER OF D CHANNELS
All: (0 ... 20): 2

The number of D channels in a unit.
The parameter indicates the number of D channels in a unit. D-channels are used in DPNSS.
LOBOUND208: MAX NUMBER OF VIRTUAL CHANNELS PER DTU
All: (1 ... 30): 30

The number of virtual channels per DTU.
The parameter indicates the number of virtual channels per DTU. Virtual channels are used in
DPNSS.
LOBOUND209: MAX NUMBER OF RS SOCOTELS
All: (0 ... 255): 4

Specify the ultimate number of SOCOTELs.
This parameter defines the area to be reserved for SOCOTEL receiver (RST-SL) data.
116
NEBOUND210: DISK SPACE ALARM UPPER LEVEL
Ccs4: (H'0000 (0%) ... H'0064 (100%)): H'005A (90%)

Ccss: (H'0000 (0%) ... H'0064 (100%)): H'005A (90%)
If the disk space that is in use on a storage device reaches a percentage of the storage capacity
of that device that is equal or higher than the percentage specified above then a disk space
alarm should be raised.
NEBOUND211: DISK SPACE ALARM LOWER LEVEL
Ccs4: (H'0000 (0%) ... H'0064 (100%)): H'0050 (80%)

Ccss: (H'0000 (0%) ... H'0064 (100%)): H'0050 (80%)
If the disk space that is in use on a storage device is decreasing to a percentage of the storage
capacity of that device that is less than the percentage specified above then the disk space
alarm can be erased.
BOUND212: MAX NUMBER OF TGST ACTION REQUESTS
All: (1 ... 250): 100

This parameter defines the size of a buffer in TGST for storage of signals requesting an action
by TGST. After each action TGST will fetch these signals from the signal queue and store them
in the buffer before starting the next action.
NEBOUND213: MAX NUMBER OF DIFFERENT OM COMMANDS IN SYSTEM
All: (700 ... 1000): 700

Maximum number of different OM commands in system This parameter defines maximum
number of different OM commands in the system. Each OM command has a unique authority
class index (ACI) assigned to it. These ACIs are used to index the ACIV-table, for which area
has to be reserved (in the RAM memory). The actual value of the parameter has to incorporate
some 'breathing space' to be able to expand the number of OM commands.
NEBOUND214: MAX NUMBER OF OBSERVED ASSISTANCE GROUPS
All: (1 ... 10): 3

Specify the ultimate number of assistance groups that can be observed by traffic
measurements. This parameter defines the area to be reserved for traffic measurement data
for observed assistance groups.
BOUND215: MAX NUMBER OF PPH PARAMETER BLOCK DATA ITEMS
All: (0 ... 400): 200
117
Define the maximum number of PPH parameter block data items. This parameter defines the
area to be reserved for PPH parameter block data.
The PPH is equipped with a number of Parameter Block. These blocks are programmed in the
PPH PROMs. For flexibility reasons some of the Parameter Block data can be changed by OM
procedures. This boundary defines the number of changes allowed in the Parameter Block.
LOBOUND216: MAX NUMBER OF COB CASES SHORT COB QUEUE
All: (1 ... 5): 3

Define the maximum number of camp on busy (COB) cases of type 'short-COB-queue'. This
parameter defines the ultimate number of COB cases on the same extension, if that extension
has been assigned the COB queue type 'short-COB-queue'. COB is e.g. activated when a busy
extension is selected by an operator. The length of the COB queue per busy extension is
determined by this parameter.
LOBOUND217: MAX NUMBER OF COB CASES LONG COB QUEUE
All: (1 ... 20): 5

Define the maximum number of camp on busy (COB) cases of type 'long-COB-queue'. This
parameter defines the ultimate number of COB cases on the same extension, if that extension
has been assigned the COB queue type 'long-COB-queue'. COB is e.g. activated when a busy
extension is selected by an operator. The length of the COB queue per busy extension is
determined by this parameter.
LOBOUND218: MAX NUMBER OF LONG FACILITY DESTINATIONS
All: (25 ... 1000): 50

Defines the maximum number of external numbers that can be contained within a table.
This table is used for the following facilities:
- Follow-me;
- Fixed-follow-me;
- Call forwarding don't answer;
- Call forwarding busy extension.
Note: Activated facilities to internal destinations will not occupy space within this table.
LOBOUND219: MAX NUMBER OF MEMBERS
Ccs4: (2 ... 5000): 172
118
Ccss: (2 ... 5000): 172
Cpu3000: (2 ... 2600): 172
Defines the total number of memberships that can be assigned within one unit. A membership
is connected to an extension when it is made a secretary, executive or groupmember.
Note: Each time e.g. an extension is made secretary for an other executive, it uses one
membership.
NEBOUND220: MAX RANKNUMBER FOR SHORT DIALLING GROUP
All: (0 ... 64): 40

Defines the maximum ranknumber that can be selected using the facility short code dialling
(short code dialling group and pick up by rank number) within groups
Note: Each group member is assigned a ranknumber. Only a limited number of members can be
selected by the facility short code dialling within groups.
NEBOUND221: MAX NUMBER OF TFM SESSIONS
All: (1 ... 16): 1

Defines the maximum numbers of TFM sessions which may be active at the same time.
This value should be according to the projecting of the used TMS (SSM) equipment.
BOUND222: MAX NUMBER OF BUFFER PACKETS
Ccs4: (800 ... 2400): 800

Ccss: (600 ... 2400): 600
Cpu3000: (500 ... 600): 600
This parameter describes the maximum number of buffer packages that are available in a unit.
Buffer packages are used for free format data of free format signals between two processes in
a single unit or between processes in different units of an iS3070 network.
Buffer packages are also used for free format buffers of PCBs and PACBs.
BOUND223: BUFFER POOL OCCUPANCY THRESHOLD
All: (80 ... 80): 80

When the number of occupied buffer packets exceeds the given percentage threshold, the
119
BOUND224: BUFFER POOL OCCUPANCY HYSTHERESIS
All: (10 ... 10): 10

When the number of occupied buffer packets has exceeded the threshold, the system will
accept new calls only when the occupation level has dropped below:
("threshold"-"hystheresis")%
BOUND225: MAX NUMBER OF MML STANDARD MESSAGE TEXT STRING
Ccs4: (1 ... 1): 1

Ccss: (1 ... 1): 1
Cpu3000: (1 ... 1): 1
Define the maximum number of standard message text strings per MML version.
This parameter defines the fixed number of standard message text strings in the system.
This parameter is fixed (not to be changed) for implementation reasons.
BOUND226: MAX NUMBER OF MML SPECIFIC ERROR TEXT STRING
All: (1 ... 1): 1

Define the maximum number of specific (non standard) error text strings per MML version.
This boundary is fixed and must be related to the number of text strings in the related MML
text files. Only to be changed by LAB.
BOUND227: MAX NUMBER OF MML HEADER LINE TEXT STRING
Ccs4: (250 ... 250): 250

Ccss: (1 ... 1): 1
Cpu3000: (1 ... 1): 1
Define the maximum number of header line text strings per MML version.
BOUND228: MAX NUMBER OF MML FORMAT SENSITIVE TEXT STRING
Ccs4: (1000 ... 1000): 1000

Ccss: (1000 ... 1000): 1000
120
Cpu3000: (1000 ... 1000): 1000
Define the maximum number of format sensitive text strings per MML version.
BOUND229: MAX NUMBER OF MML FORMAT INSENSITIVE TEXT STRING
Ccs4: (1 ... 1): 1

Ccss: (1 ... 1): 1
Cpu3000: (1 ... 1): 1
Define the maximum number of format insensitive text strings per MML version.
BOUND230: MAX NUMBER OF MML BLOCK TEXT CHARACTERS
Ccs4: (5 ... 5): 5

Ccss: (5 ... 5): 5
Cpu3000: (5 ... 5): 5
Define the maximum number of block text characters per MML version.
Total text characters that can be kept by the system = (max. number MML block text
characters) 253.
BOUND231: MAX NUMBER OF ACD GROUPS
Ccs4: (0 ... 100): 10

Ccss: (0 ... 100): 10
Cpu3000: (0 ... 100): 10
Specify the ultimate number of ACD group arrangements.
This parameter defines the area to be reserved for ACD group data.
LOBOUND232: OFFICE NUMBER
All: (0 ... 49999): 0

This parameter defines the office number.
This parameter together with the representative PABX number (NEBOUND 012) and
possibly the area number (LOBOUND 280) represent the ISPBX subscriber number. It is used
as calling line identity in outgoing MFC call when the internal DNR does not belong to the
121
PSTN number scheme.
The most significant digit gives the number of leading zeros.
See NEBOUND 012 for an example.
LOBOUND233: DEFAULT CALLING SUBSCRIBER CATEGORY
All: (1 ... 15): 1

Calling subscriber category, as default assigned to each extension/ operator.
This parameter defines the default calling subscriber category for extensions and operators,
used for DDO calls with MFC-CSS1 signalling, when sending the calling line identity.
LOBOUND234: GENERAL CALLING SUBSCRIBER CATEGORY
All: (1 ... 15): 6

Specify the General Calling Subscriber Category.
The General Calling Subscriber Category is part of the calling line identity in a tandem DDI-
DDO call with MFC-CSS1 signalling, while the DDI does not have MFC-CSS1 signalling.
NEBOUND235: MAX NUMBER OF BSPTs FOR TRUNKS
All: (1 ... 15): 2

Specifies the number of different BSPTs that can be assigned to a trunk route or a trunk
bundle.
LOBOUND236: MAX NUMBER OF VCTs PER DTU-BA DPNSS
All: (14 ... 30): 30

The maximum number of VCTs on a DTU-BA for DPNSS.
LOBOUND237: ISNET PVN PACKAGE ID
All: (0000 ... 9999): 0

Specifies the PVN Package Identifier.
LOBOUND238: MAX NUMBER OF ISDN TRUNK CIRCUITS
Ccs4: (0 ... 750): 20

Ccss: (0 ... 750): 20
Cpu3000: (0 ... 100): 20
122
Specifies the ultimate number of ISDN trunk L1 entities.
LOBOUND239: MAX NUMBER OF ISDN TRUNK B CHANNELS
Ccs4: (0 ... 1504): 64

Ccss: (0 ... 1504): 64
Cpu3000: (0 ... 512): 64
Specify the ultimate number of B-channels that can be used for ISDN trunk traffic.
This parameter defines the area to be reserved for B-channel trunk line data. This parameter
has a relation with the unit boundary max number of ISDN trunk circuits.
Depending on the number of B-channels per access (ISDN trunk circuit) the minimum value
should be projected at 2 times max number of ISDN trunk circuits.
The boundary should never be projected larger than 32 times max number of ISDN trunk
circuits (but do observe the above given maximum).
BOUND240: ISDN INW FLOW RECEIVE WINDOW SIZE
All: (0 ... 0): 0

Define the default receive window size for INW flows.
This parameter defines the number of messages that can be buffered for receive by the CPU
on INW communication flows.
BOUND241: ISDN INW FLOW SEND WINDOW SIZE
All: (0 ... 0): 0

Define the default send window size for INW flows.
This parameter defines the number of messages that can be buffered for send by the CPU on
INW communication flows.
BOUND242: ISDN SIG FLOW RECEIVE WINDOW SIZE
All: (1 ... 127): 4

Define the default receive window size for SIG flows.
on SIG communication flows.
123
BOUND243: ISDN SIG FLOW SEND WINDOW SIZE
All: (1 ... 255): 3

Define the default receive window size for SIG flows.
on SIG communication flows.
BOUND244: ISDN MAN FLOW RECEIVE WINDOW SIZE
All: (1 ... 255): 2

Define the default receive window size for MAN flows.
on MAN communication flows.
BOUND245: ISDN MAN FLOW SEND WINDOW SIZE
All: (1 ... 255): 3

Define the default receive window size for MAN flows.
on MAN communication flows.
BOUND246: MAX NUMBER OF BSPTs
All: (99 ... 99): 99

Specifies the number of BSPTs known to the system.
Extension Service and Trunk Service will use the related keyrange to generate a data structure
to store the BSPT to IBSC relations.
BOUND247: MAX NUMBER OF ACD AGENTS
Ccs4: (0 ... 400): 50

Ccss: (0 ... 400): 50
Cpu3000: (0 ... 400): 50
Specifies the ultimate number of ACD agents.
BOUND248: MAX NUMBER OF BSP PER EXTENSION CIRCUIT
All: (2 ... 17): 4

Specifies the number of different user profiles that can be assigned to an extension circuit.
124
BOUND249: MAX NUMBER OF DTU-BA DPNSS
All: (0 ... 20): 2

The maximum possible number DTU-BA boards for DPNSS.
BOUND250: MAX NUMBER OF FDCR DATA BLOCKS
Ccs4: (1 ... 2400): 400

Ccss: (1 ... 2400): 350
Cpu3000: (1 ... 400): 350
Defines the maximum number of Full Detailed Call Recording (FDCR) data blocks that can be
in use simultaneously. Each time call processing needs a FDCR data block, it asks one from call
recording SP. If the total number of used FDCR data blocks has reached its maximum, the call
may proceed, but it will not be registered. FDCR uses FDCR data blocks for incoming and
internal calls, and for outgoing calls without toll ticketing. For outgoing calls WITH toll
ticketing, FDCR uses TT data blocks.
The number of available TT data blocks is projected via BOUND139.
Note: Boundary 250 must be at least 50 lower than boundary 257 (max. number of medium data
blocks).
BOUND251: MAX DOWNLOAD REQUEST BUFFER SIZE
Ccs4: (0 ... 300): 300

Ccss: (0 ... 300): 300
Cpu3000: (0 ... 80): 40
This is a boundary parameter which defines the maximum number of download request
buffered by the system for later execution.
NEBOUND252: MAX NUMBER OF INSTALLED SOFTWARE PACKAGES
All: (3 ... 40): 30

This parameter defines the maximum number of software packages installed in the system
(combination of board type, subtype, package relations).
NEBOUND253: MAX NUMBER OF ROUTE TABLES IN SYSTEM
All: (1 ... 255): 20

This is a boundary parameter which defines the maximum number of route tables in the
system.
125
BOUND254: MAX NUMBER OF SEQUENCE TABLES PER UNIT
All: (1 ... 1250): 40

This is a boundary parameter which defines the maximum number of route sequence tables
per unit.
NEBOUND255: MAX NUMBER OF OUTGOING DIGIT CONVERSIONS
Ccs4: (0 ... 6000): 20

Ccss: (0 ... 6000): 20
Cpu3000: (0 ... 4000): 20
This boundary specifies the total amount of required outgoing digit conversions.
The maximum number of incoming digit conversion is defined by LOBOUND031.
BOUND256: PAUSE TONE
All: (0 ... 5): 0

This parameter determines which tone is given during the announcement repeat time:
0 : COB tone
1 : external ring tone
2 : internal ring tone
3 : music on hold (= PCT type music on hold)
4 : music on COB (= PCT type announcement)
5 : no tone
BOUND257: MAX NUMBER OF MEDIUM DATABLOCKS
Ccs4: (800 ... 2400): 800

Ccss: (400 ... 2400): 400
Cpu3000: (400 ... 500): 400
This parameter describes the maximum number of medium datablocks that are available in a
unit.
126
Note: Boundary 257 must be at least 50 higher than boundary 250 (max. number of FDCR data
blocks).
NEBOUND258: ACCESS CODE FOR EMULATION
All: (0 ... 65535): 4895 (=H'131F)

This parameter defines the MCL Local Access Code sent to the trunk in case of (Mercury)
Smartbox Emulation. The access code is projectable, but should normally be '131' for Mercury
Indirect Access (i.e. the default value).
Projecting rule: each of the four nibbles of this system parameter represents a digit, with H-F
(null digit) used as a filler when the access code contains less than four digits. Filler nibbles
(when required) must always be appended at the end of the digit string.
NEBOUND259: NUMBER OF DIGITS FOR ITEMIZED BILL
All: (0 ... 12): 0

This parameter defines how many digits of the calling party identification will be sent to the
carrier network for the network facility 'itemised bill by extension'.
If this parameter is 0, no calling party identification will be sent. When the facility 'itemised bill
by extension' is activated in the MCL network, then this parameter must be set to 3.
BOUND260: DON'T DISTURB RESET TIME
All: (0 ... 65535 minutes): 0

This parameter defines the duration (in minutes) of the temporary don't disturb facility. When
this parameter is projected to the minimum value (0), semi-permanent don't disturb is offered
to entitled users.
When a value >0 is projected, temporary don't disturb is offered with duration equal to the
projected value.
BOUND261: MAX NUMBER OF TEMPORARY DON'T DISTURB CASES
All: (0 ... 255): 50

This parameter defines a boundary for the total number of simultaneous active temporary
don't disturb cases in a unit.
BOUND262: MAX NUMBER OF AGENTS PER ACD GROUP
All: (0 ... 100): 25
127
This parameter defines the maximum number of agents that can be assigned to each ACD
group.
BOUND264: MAX NUMBER OF STANDARD MESSAGE QUEUE PLACES PER

ACD GROUP
All: (1 ... 100): 15

This parameter defines the number of queue places in the standard message queue that are
available for one ACD group.
NEBOUND265: NUMBER OF FEATURE REQUESTS PER UNIT
All: (1 ... 120): 50

This parameter defines the number of ErgoLine phones, which can handle physical device
features at the same time. It is advised to set this boundary the same in all units of a FIN.
BOUND266: DEFAULT MSN TYPE
All: (0 ... 2): 2

A default MSN type is assigned to each ISDN extension circuit. This default can be one of the
following values:
0 = no MSN.
1 = MSN.
2 = MSN with fixed digit.
The MSN type can be changed by means of OM command CHMSNP.
BOUND267: DEFAULT FIXED MSN DIGIT B0
All: (0 ... 14): 2

Default fixed MSN digit assigned to a BSP relation to B0.
If the circuit to which you assign a BSP-ID is the B0 channel of an Sbus, then the 'default fixed
MSN digit B0' is assigned to the BSP-ID
In an operational system you can change the 'fixed MSN digit B0' by means of OM command
CHFMSN.
128
BOUND268: DEFAULT FIXED MSN DIGIT B1
All: (0 ... 14): 3

Default fixed MSN digit assigned to a BSP relation to B1.
If the circuit to which you assign a BSP-ID is the B1 channel of an S0bus, then the 'default fixed
MSN digit B1' is assigned to the BSP-ID
In an operational system you can change the 'fixed MSN digit B1' by means of OM command
CHFMSN.
BOUND269: MAX NUMBER OF PVN FLOWS
All: (0 ... 1550): 310

By means of this parameter you determine the maximum number of PVN (Private Virtual
Network) flows allowed in the system. It is advised to project this parameter as follows:
31 x 'Max. Number of PVN Links' (see BOUND270).
BOUND270: MAX NUMBER OF PVN LINKS
All: (0 ... 50): 10

This parameter defines the maximum number of PVN links that are allowed in the system.
BOUND271: MAX NUMBER OF USER CHANNEL ADDRESSES
All: (0 ... 50): 10

This parameter defines the maximum number of User Channel Addresses which are used to
setup PVN calls through the intervening network.
BOUND272: MAX NUMBER OF HATCHES
All: (0 ... 255): 75

This parameter defines the area which must be reserved for hatches. A hatch is a functional
entity that can put SOPHO ISPBX signalling data in IMP or HDLC format in 64 Kbit/s channels
and vice versa. PVN uses hatches to send and receive signalling channel data.
LOBOUND273: MAX NUMBER OF OUTSTANDING ROUTE OPTIMISATION

REQUESTS
All: (0 ... 100): 5

This boundary defines the maximum number of calls being processed in parallel. This
129
maximum applies per unit and to calls which are originated in this unit.
LOBOUND274: MAX NUMBER OF SPECIFIC ANNOUNCEMENT CIRCUITS
All: (0 ... 255): 20

This boundary defines the maximum number of specific announcement circuits. An
announcement circuit is used by a continuous announcer (e.g. wake-up and message waiting
with announcement facilities).
NEBOUND275: MAX NUMBER OF IPD ENTRIES
All: (1 ... 6000): 100

This boundary defines the maximum number of Password, PID and/or Cost Centre relations
that can be stored for Integrated Password Dialling.
LOBOUND276: MAX NUMBER OF CSTA LINKS PER UNIT
All: (0 ... 15): 2

This boundary defines the maximum number of CSTA EDP links (iS links) that can be
connected to this unit. It is restricted by the sum of the licenses 17 (S0bus link CSTA) and 21
(Ethernet link CSTA).
LOBOUND277: MAX NUMBER OF CSTA MONITORED BSPs
All: (0 ... 2000): 16

This boundary defines the maximum number of BSPs in this unit, that can be monitored by the
CSTA EDP link connected to this unit. It is restricted by license number 18 (Active CSTA
monitors).
This boundary is calculated by the SUM of :
- the maximum number of CSTA monitored seats

- the number of group DNRs, where CSTA seats are operational
- the number of facilities, like call diversion(s) to not monitored extensions.
LOBOUND278: MAX NUMBER OF CSTA MONITORED GLOBAL BSPs
All: (0 ... 500): 16

This boundary defines the maximum number of BSPs in the IMP network, which are
monitored by CSTA for which the EDP link is connected to this unit.
This boundary is obsolete since Call@Net 2.9.
130
NEBOUND279: MAX NUMBER OF CSTA CALLS PER UNIT
All: (0 ... 3000): 48

This boundary defines the maximum number of calls in this unit involving CSTA monitored
local BSPs. Note that the value of this parameter must not be higher than:
(max. number of control blocks (boundary 202) - 150) / 4.
LOBOUND280: MFC AREA NUMBER
All: (0 ... 49999): 0

This parameter defines the area number.
This parameter together with the office number (LOBOUND 232) and the representative
PABX number (NEBOUND 012) represents the ISPBX subscriber number. It is used a calling
line identity in outgoing MFC calls when the internal DNR does not belong to the PSTN
number scheme.
The most significant digit gives the number of leading zeros.
See NEBOUND 012 for an example.
LOBOUND281: SUB CLUSTER ID
All: (0 ... 9999): 0

If the system option 'unique cluster ID' is false, this parameter is used by route optimization
and flexible operator mechanisms, in order to uniquely determine the PBX within the DPNSS
network.
LOBOUND282: PROJECTED VOICE BSPT FOR OPERATORS
All: (0 ... 98): 95

This parameter defines the BSPT set which is to be used for checking whether a call is voice-
oriented. It is, for instance, used as a BSPT for operator calls (so don't set this boundary to
zero).
When the IBSC of a call is enclosed in the BSPT indicated by boundary 282, the call is identified
as voice-oriented and break-in, call waiting etc. will be possible (as far as other facilities allow
it). When the IBSC is not enclosed in the BSPT, the voice-oriented facilities will not be
possible.
For incoming ISDN trunk calls also an identification must be made, because voice-oriented
calls use other timers then data-oriented calls. Whether a call with a certain IBSC is voice-
131
oriented is also determined from the fact that the IBSC is enclosed in the boundary 282 BSPT
value.
When this boundary is projected to a value larger than 98, the value 95 (voice/ possible voice)
is used internally.
LOBOUND283: MAX NUMBER OF MONITORED ASSISTANCE GROUPS
All: (0 ... 16): 2

This parameter defines the maximum number of monitored assistance groups.
LOBOUND284: MAX NUMBER OF STANDARD MESSAGE QUEUE PLACES PER

MONITORED ASSISTANCE GROUP
All: (1 ... 100): 15

This parameter defines the number of queue places in the standard message queue that are
available for one monitored assistance group.
BOUND285: DEFAULT TRUNK ACCESS CODE
All: (0 ... 49999): 0

This boundary defines the default trunk access code for media connection to the
ErgoLine@Net based on TMP. The most significant digit gives the number of leading zeros.
Examples:
- 0 = no digit string;
- 1234 = digit string 1234;
- 10000 = digit string 0;
- 20030 = digit string 0030;
- 40001 = digit string 00001.
The digit string is analysed in number analysis tree 0. The result-id must be trunk access code
(TAC). The outgoing analysis tree belonging to the concerned destination must consist of
external numbers 1... 9 with MIN length=4 and MAX length=4. The destination must lead to
a route with the IP-gateway.
BOUND286: DEFAULT BAUDRATE CHAR PROTOCOL
All: (8 ... 20): 10

This parameter defines the baudrate for character oriented protocols; the next values are
available :
132
08 = 1200
10 = 2400
12 = 4800
14 = 9600
17 = 19200
18 = 38400
20 = 57600
BOUND287: DEFAULT BAUDRATE BCS PROTOCOL
All: (8 ... 20): 17

This parameter defines the baudrate for the BCS oriented protocols; the next values are
available
08 = 1200
10 = 2400
12 = 4800
14 = 9600
17 = 19200
18 = 38400
20 = 57600
BOUND288: MAX NUMBER OF I/O PACKETS
Ccs4: (48 ... 480): 160

Ccss: (48 ... 480): 80
Cpu3000: (10 ... 100): 80
This parameter describes the maximum number of I/O packets that are available for the local
operating system (LOS), for the I/O via internal and external protocols.
133
BOUND289: SYSTEM LIMITED NUMBER OF ADDRESS RANGES
All: (2 ... 2): 2

Specify the number of address ranges within one PM. Each compact PM has a high and a low
address range. Because these PMs have more than 256 ports, the port range is divided in two
parts; a low and a high part. Don't mix this parameter with BOUND191 (system limited
number of SNLs per conn part).
BOUND290: MAX NUMBER OF BUFFERED LOGGING MESSAGES
Cpu3000: (0 ... 100): 50

Specify the ultimate number of buffered logging messages for remote maintenance.
This parameter defines the area to be reserved for the remote logging facility.
BOUND291: MAX NUMBER OF STATUS MONITORING ITEMS
All: (0 ... 10000): 600

A status monitoring item is one DNR or line number monitored by the operator (busy lamp
panel) or a SOPHO-SET Business telephone. This parameter defines the area to be reserved
for the status monitoring service.
BOUND292: MAX NUMBER OF DEVICES IN UNIT
All: (10 ... 100): 25

This boundary defines the maximum number of devices that can be assigned to a CCS unit.
This parameter is only valid for a CCS system.
The number of devices in a CPU3000 system is defined by BOUND084.
BOUND293: MAX NUMBER OF STORED CALL RECORDS BUFFERS
Ccs4: (1000 ... 65533): 1000

Ccss: (300 ... 300): 300
Cpu3000: (1000 ... 65535): 1000
This boundary defines the maximum number of stored call recording buffers.
The maximum value (65533) has about 6 hours storage capacity if the call rate of the system
is 3 calls per second.
134
BOUND294: PRESENTATION RESTRICTED NUMBER DIGIT
All: (0 ... 15): 15

This boundary defines the digit that is used to display the presentation restricted number. If
the value of this parameter is outside the range of 0-15, the system will assume the value 15.
BOUND295: BEGIN OF PARTIAL TRUNK ACCESS CODE
All: (0 ... 6): 0

This boundary defines the start position of the first digit of the trunk access code that is
included in the toll ticketing/FDCR record (in case of MFE signalling).
BOUND296: DEFAULT CLI 1
All: (0 ... 65535): 65535

When an extension has FCM "indialling barred" and an ISDN route has INCOMING route
option "DDI barred check" in the ISDN setup message, the caller DNR (which is assumed to
be a local DNR in the PABX) is replaced by a DNR as defined in the boundaries 296 (Default
CLI 1) and 297 (Default CLI 2). CLI 1 is the higher part and CLI 2 the lower part of the DNR.
Coding : Default CLI 1 n00xx n = the number of leading zero's;

xx = the upper two digits of the DNR.
Default CLI 2 xxxx xxxx = the lower four digits of the DNR.
Examples :
0 1234 1234
99 9999 999999
10000 1234 01234
10009 9999 099999
50000 9 000009
50000 0 000000
65535 65535 no replace
BOUND297: DEFAULT CLI 2
All: (0 ... 65535): 65535

See boundary 296
BOUND301: MAX NUMBER OF FTLDs
All: (1 ... 3000): 4
135
This boundary is valid for special projects only.
This boundary defines the ultimate number of all Fixed Trunk Line Destination (FTLD) strings
(long and short) and the number of Fixed Trunk Line Identities.
BOUND302: MAX NUMBER OF LONG FTLDs
All: (1 ... 3000): 4

This boundary defines the ultimate number of long Fixed Trunk Line Destination strings. Any
FTLD string longer than 6 digits, is considered as a long FTLD. This boundary may not exceed
boundary 294.
BOUND303: MAX NUMBER OF DCCs
All: (1 ... 32): 4

This boundary specifies the ultimate number of DCCs of board types 13 and 16.
This parameter does not apply to DCCs of board type 15.
BOUND304: MAX NUMBER OF ALARMED CTAs
All: (1 ... 500): 4

This boundary specifies the ultimate number of CTAs that can (at the same time) have alarms
present. It will in general not be necessary to give this parameter the same value as the number
of actually installed CTAs as it is not likely that they'll all report errors at the same time.
LOBOUND305: MAX NUMBER OF INTERNAL CNND DATABASE ENTRIES
Ccs4: (0 ... 11015): 0

Ccss: (0 ... 11015): 0
Cpu3000: (0 ... 2360): 0
This boundary has become obsolete since Call@Net 2.5 because both the Internal CNND and
Internal CDD functions share the same database.
This boundary is necessary to build the internal CNND database, used by the local CNND
function for translation of the (R)DNRs into name relations. It defines the number of RDNR/
name relations that can be stored in the unit.
The maximum number of entries is equal to the sum of the boundaries 46 (Max. number of
136
extension DNRs), 16 (Max. number of operators) and 17 (Max. numbers of groups). If the size
of boundary 305 is kept equal to the sum of these three projected boundaries, no congestion
can occur on the CNND database.
If the boundary is made 0 (zero), no internal CNND database will be created during system
startup.
Note that the database requires 23 bytes + 1 bit RAM space per defined entry. The size of
the internal CNND database and the cache memory together may never exceed 64 kB for the
CSM platform.
BOUND306: MAX NUMBER OF CNND CACHE ENTRIES
All: (0 ... 1000): 0

This boundary determines the size of the CNND cache memory. It is used for building a
CNND cache memory, used by call processing for temporary storing name/number
translations. The cache is cyclic and translations are stored according to the FIFO (first in first
out) principle. Cache entries are not removed explicitly, but when the cache is full and a new
entry has to be stored, the oldest entry (which was stored first) is overwritten.
Note that the cache requires 30 bytes RAM space per defined entry. The size of the cache
memory and the internal CNND database together may never exceed 64 kB for the CSM and
the CPU3000 platform.
NEBOUND307: MAX NUMBER OF FREE NUMBERING ENTRIES
Ccs4: (1 ... 65530): 50

Ccss: (1 ... 65530): 50
Cpu3000: (1 ... 21700): 50
This boundary specifies the max number of Free Numbering entries in the system.
NEBOUND308: FIRST ENQUIRY ON TRUNK DIGIT
All: (0 ... 15): 15

This boundary specifies the 'First Enquiry On Trunk Digit'.
When an extension is involved in a trunk-line call and the call is in conversation phase, then at
pressing the enquiry button the digit(s) projected by this boundary (and NEBOUND 309) are
sent as keytone-digits to the connected trunk line.
When NEBOUND 308 is projected to digit "15" (null-digit), enquiry on trunk through sending
keytone digits is not applicable.
137
When NEBOUND 309 is projected to digit "15" (null-digit), only one enquiry on trunk digit
(defined with NEBOUND 308) is sent.
NEBOUND309: SECOND ENQUIRY ON TRUNK DIGIT
All: (0 ... 15): 15

This boundary specifies the 'Second Enquiry On Trunk Digit' (see NEBOUND 308).
BOUND310: MAX NUMBER OF PERIPHERAL FILE USERS PER UNIT
All: (0 ... 16): 10

This boundary defines the maximum number of users per unit that can simultaneously use the
'Peripheral File Storage Mechanism' (PFSM). By means of the PFSM applications (users) within
peripheral boards or TMP terminals (not yet supported) are able to access a file on the logical
device e.g. the LBU controlled by the iS3000 system.
BOUND311: MAX NUMBER OF CHAINED DIRECT DIVERSIONS
All: (0 ... 5): 0

This boundary is required to chain the direct diversions. It defines the number of direct
diversions (fixed FM, FM, CF on busy, CF when absent, CF when out of order) in a chain which
can be executed in one PBX system. This boundary avoids looping and to guard system
resources.
BOUND312: LENGTH OF UNCONDITIONAL MSN
All: (1 ... 6): 1

Default length of unconditional MSN. In case MSN type 1 (unconditional MSN) is projected
with UBM of boundary 266 (default MSN type), then the length of MSN will be initiated to the
value of this boundary 312.
If the specified length is 0 or higher than 6, the length will be initialised to 1.
BOUND313: ISDN TRANSPARENCY MODE
All: (0 ... 65535): 65535

This parameter defines the handling of elements in ISDN messages for ISDN-trunk towards
ISDN-extension (S0bus) calls. Sixteen items can be specified by this parameter. For each item
it can be specified whether the item is set (1) or reset (0).
The decimal value of this parameter is calculated in a binary way: Determine which items have
to be set (value = 1), then calculate the power of 2 indicated by the item index and finally add
138
the results.
Example:
To set the items 0, 5 and 10: (2 to the power 0) + (2 to the power 5) + (2 to the power 10)
= 1 + 32 + 1024 = 1057.
Up till now the following items have been defined:
- item index 0 (CLIR intervention)

- 1: a presentation restricted calling party number will be modified (i.e. filled with 6
times the 'presentation_restricted_number_digit (boundary 294) and a type of
number and number plan 'unknown'/'unknown'.
- 0: a presentation restricted calling party number will be left unchanged.
- item index 1 (empty CLI intervention)
- 1: a calling party number which is empty and not presentation restricted or not
present at all, will be changed into a calling party number with 6 times an asterisk
(******) and a type of number and number plan 'unknown'/'unknown'.
- 0: a not presentation restricted calling party number will be left unchanged.
- item index 2 (Number plan and type in CLI intervention)
- 1: the type of number and number plan in a calling party number will always be
changed into 'unknown'/'unknown'.
- 0: the type of number and number plan will be left unchanged.
- item index 3 (Sending complete intervention)
- 1: the 'sending complete string' is sent in an information element after expiration of the
number_may_be_complete timer.
- 0 : no 'sending complete string' is sent in an information element after expiration of the
number_may_be_complete timer.
BOUND314: MAX NUMBER OF MRG MEMBERS
Cpu3000: (1 ... 128): 5

Ccss: (1 ... 128): 5
Ccs4: (1 ... 128): 5
Maximum number of members per Multiple Ring Group (MRG).
For performance reasons there is a limit on the maximum number of members that will start
ringing simultaneously within a MRG; see also NETIMER 213 (Multiple Ring Group Call Setup
Delay Time).
139
NEBOUND315: MAX NUMBER OF CLI/COL TRANSLATION ENTRIES
All: (0 ... 10000): 50

This boundary states the total number of CLI/COL translation strings which can be defined in
the system. Since the CLI/COL translation tables are considered network data, this boundary
must the same for every unit in the system.
NEBOUND316: DEFAULT CONNECTION ALLOWANCE
All: (0 ... 3): 0

This boundary specifies the default connection allowance, a CV-value gets when it is created.
'0' means that the connection is not possible; '3' means connection is allowed.
BOUND317: SOPHO UNITS LEFT BEFORE WARNING TONE
All: (0 ... 65535): 1

This parameter gives the number of SOPHO units left on which the warning tone must be
given. Default value is 1 SOPHO unit. If the value is set to 0, no warning tone is given.
BOUND318: TONE TYPE FOR WARNING TONE
All: (0 ... 27): 12

For call break at zero budget, default the 'call waiting tone burst' is given. But it is possible to
define the type of warning tone to be given. Select from the list below:
00 = internal ring tone
01 = external ring tone
02 = internal dial tone
03 = first external dial tone
04 = second external dial tone
05 = delayed hotline dial tone
06 = busy tone
07 = nu tone
08 = congestion tone
140
09 = diversion active dial tone
10 = confirmation tone
11 = urging tone
12 = call waiting tone burst
13 = paging absent tone
14 = paging in progress tone
15 = bypass tone
16 = conference control tone
17 = cob tone to caller
18 = park tone
19 = through connect ring tone
20 = ticker tone 0
21 = howler tone
22 = party connect tone
23 = call waiting indication tone
24 = alternative routing dial tone
25 = alternative routing warning tone
26 = enter password tone
27 = routing tone
BOUND319: ENQUIRY KEYTONE DIGIT
All: (0 ... 15): 15

This boundary defines which keytone digit is interpreted as enquiry signal. The enquiry
keytone digit is only applicable for extensions which have the FCM 59 and/or 60 'enquiry by
keytone digit' assigned. The projected digit is interpreted as 'enquiry signal' when it is received
141
in a non-dialling state. Project digit '15' (null digit) if no enquiry keytone digit is applicable.
See also BOUND341.
BOUND320: DISABLE ENQUIRY KEYTONE DIGIT
All: (0 ... 15): 15

This boundary defines which keytone digit will be interpreted as signal to disable the facility
'enquiry by keytone digit' for the remaining part of the call. The disable enquiry keytone digit
is only applicable for extensions which have the FCM 59 and/or 60 'enquiry by keytone digit'
assigned. The projected digit is interpreted as 'disable signal'. When it is received in a non
dialling state, the facility enquiry by keytone digit is disabled for the remaining part of the call.
Project digit '15' (null digit) if no enquiry keytone digit is applicable.
See also BOUND355.
BOUND321: SYSTEM LIMITED NUMBER OF SOLID STATE DISKS
Cpu3000: (empty ... empty): 2

This system limited boundary defines the maximum number of solid state disks (number of
flash SIMMs) for CPU3000. This value of this boundary is a system parameter and its value is
constant.
BOUND322: MAX NUMBER OF STATUS OBSERVER ENTRIES
All: (1 ... 10): 5

This system limited boundary defines the maximum number of registries that can be attached
to the status observer at the same time. For each resource type a status observer exist.
BOUND323: MAX NUMBER OF IP BROADCAST MESSAGES PER SECOND
Cpu3000: (10 ... 500): 50

This system limited boundary defines the maximum number of (Ethernet) broadcast messages
that the system is willing to handle within each one-second time interval.
When this boundary is projected too high, it can have an impact on the call control
performance. When the TCP/IP network generates too many broadcast messages the
processing of these messages will decrease the call control performance. By proper
assignment of this boundary call control will not suffer from such poor network behaviour.
When this boundary is set too low it is no longer possible to set up a new IP connection with
the CPU3000, but this has no impact on normal call control performance.
142
It is advised to use the default value of this boundary.
BOUND324: MAX NUMBER OF SOCKETS PER UNIT
All: (50 ... 500): 50

This system limited boundary defines the total number of TCP/IP related sockets available in
the system. IIt also defines the general constraints for IP-related applications like CSTA over
Ethernet. All IP-related applications within the system together never can use more sockets
than is defined here.
Be sure that the value of boundary 324 is at least 10 higher than the value of boundary 325.
For example when boundary 325 is set to 45, the minimum value of boundary 324 must be 55
(or higher).
LOBOUND325: MAX NUMBER OF SOCKETS PER TASK (CPU3000 only)
Cpu3000: (40 ... 50): 40

This system limited boundary defines the general constraints for TCP/IP-related applications
like CSTA over Ethernet. Individual pSOS tasks like the TCP/IP relay task never can use more
sockets per task than is defined here.
BOUND326: MAX NUMBER OF CSTA DATA PATHS
All: (1 ... 2000): 1

This parameter defines the maximum number of data paths to BSPs in that unit.
BOUND327: MAX NUMBER OF GLOBAL CSTA DATA PATHS
All: (1 ... 500): 1

This parameter defines the maximum number of data paths to BSPs in the multi unit network
from CSTA sessions active in that unit.
BOUND328: MAX NUMBER OF CSTA IO REGISTRATIONS
All: (1 ... 2000): 1

This parameter defines the maximum number BSPs in a unit that can be registered by CSTA
from the own or any other unit.
143
BOUND329: MAX NUMBER OF GLOBAL CSTA IO REGISTRATIONS
All: (1 ... 500): 1

This parameter defines the maximum number of BSPs in the multi unit network that can be
registered by CSTA sessions active in that unit.
LOBOUND330: MAX NUMBER OF CSTA CALL IDS PER UNIT
All: (4096 ... 4096): 4096

This boundary defines the number of CSTA Call-Ids that can be used within one unit. The Call-
Id towards the EDP is a concatenation of the unit number and the Call-Id within the unit (range
0 - 0xDFFF(hex)).
LOBOUND331: MESSAGE WAITING DIALTONE
All: (0 ... 28): 28

This boundary defines the dialtone to be given when an extension user starts a call while a
message waiting is active on his DNR. By setting this boundary to its default value, no specific
message waiting dialtone is given. The boundary value corresponds with the tone-functions
(e.g. diversion-active-dial-tone = 9)
LOBOUND332: BASIC DNR DIALTONE
All: (0 ... 28): 9

This boundary defines the dialtone to be given when a call is made from a basic DNR. By
setting this boundary to null tone (=28), no specific basic DNR dialtone is given. The boundary
value corresponds with the tone-functions (i.e. default : diversion-active-dial-tone = 9)
NEBOUND333: MAX NUMBER OF SERVER DIALLED PREFIXES
All: (0 ... 40): 18

This parameter defines the maximum number of prefixes having result-id 145 (CSTA server
dialled) within a unit.
NEBOUND334: MAX NUMBER OF TASKS
All: (25 ... 25): 25

This boundary defines the number of tasks that can be used in the pSOSystem (the real time
operating system).
144
NEBOUND335: MAX NUMBER OF QUEUES
All: (25 ... 25): 25

This parameter defines the number of queues that can be used in the pSOSystem (the real
time operating system).
NEBOUND336: MAX NUMBER OF MESSAGE BUFFERS
All: (250 ... 250): 250

This parameter defines the of message buffers that can be used in the pSOSystem (the real
time operating system).
NEBOUND337: MAX NUMBER OF SEMAPHORES
All: (25 ... 25): 25

This parameter defines the number of semaphores that can be used in the pSOSystem (the
real time operating system).
NEBOUND338: MAX NUMBER OF TIMERS
All: (10 ... 10): 10

This parameter defines the number timers of that can be used in the pSOSystem (the real time
operating system).
NEBOUND339: INTRUSION DIGIT
All: (0 ... 15): 15

This boundary defines what digit is to be sent in case the break-in suffix is dialled for
establishing a 'network priority/forced release' call (FCM 61). The default value 15 (H'F)
implies 'no digit defined'.
NEBOUND340: FORCE RELEASE DIGIT
All: (0 ... 15): 15

This boundary defines what digit is to be sent in case the force release suffix is dialled for
establishing a 'network priority/force release' call (FCM 61). The default value 15 (H'F) implies
'no digit defined'.
NEBOUND341: SECOND ENQUIRY KEYTONE DIGIT
All: (0 ... 15): 15

This boundary defines which second keytone digit (first digit defined by boundary 319 "enquiry
145
keytone digit") is interpreted as enquiry signal.
The enquiry keytone digits are only applicable for extensions which have the facility enquiry
by keytone digit assigned. The projected digits will be interpreted as "enquiry signal" when it
is received in a non-dialling state.
Project digit "15" (null digit) if only one enquiry keytone digit is applicable.
NEBOUND342: MAX NUMBER OF INTERNAL NAME DATABASE ENTRIES
All: (0 ... 65530): 0

This boundary defines the maximum of name-number entries in the internal database. When
a SOPHO iSNET MAN network is used the boundary must have the same value for each unit.
NEBOUND343: CDD SORTED ORDER
All: (0 ... 2): 0

This boundary defines the sorting order to be used for CDD.
0 = Standard International
1 = Danish
2 = Swedish
When a SOPHO iSNET MAN network is used the boundary must have the same value for
each unit.
NEBOUND344: PVN DATA CONSISTENCY CHECK INTERVAL TIME
All: (5 ... 65535): 65535

This boundary defines the interval time (in seconds) that the PVN service process executes a
consistency check of the data. This test checks all active signalling channels for inconsistencies.
If an inconsistency is found the signalling channel is released and if the PVN trap is active an
alarm is raised and a dump is generated
LOBOUND345: MAX NUMBER OF ARB RELATIONS
Ccs4: (0 ... 512): 15

Ccss: (0 ... 512): 15
Cpu3000: (0 ... 255): 15
This boundary defines the maximum number of simultaneous ARB relations in the iS3000 unit.
146
NEBOUND346: ROLLBACK RETRY COUNT FOR VIRTUAL PORT
All: (255 ... 255): 255

This boundary defines how often the CLAIM CHECK DELAY TIME may expire before a
process, to which the rollback signal for a virtual port is frozen.
NEBOUND347: MAX VIRTUAL PORTS IN ROLLBACK
All: (1 ... (max number of signal packets)/2): 50

This boundary defines the maximum number of concurrent rollback sign virtual ports within
one iS3000 unit.
NEBOUND348: MAX PERCENTAGE OF ISDN VIRTUAL CALLS
All: (0 ... 100): 20

This boundary defines the maximum percentage to which ISDN virtual calls can take up flow
resources, as well as in a unit and to or from a PM.
NEBOUND349: MAX NUMBER OF CONFERENCE GROUP CHAINS
All: (1 ... 10): 1

This boundary defines the number of chained conference groups that can exist in the system.
The maximum length of one conference group chain is defined by boundary 311 (max. number
of chained direct diversions). The length of one conference group chain is the value of
boundary 311 + 1.
The total number of conference group chains that can exist in the system is (the value of
boundary 349) * (the value of boundary 311 + 1).
NEBOUND350: MAX NUMBER OF EXTERNAL NAME DATABASE ENTRIES
All: (0 ... 65530): 0

This boundary is valid for one special project only. It defines the maximum of name-number
entries in the external database. When a SOPHO iSNET MAN network is used the boundary
must have the same value for each unit.
LOBOUND351: MAX NUMBER OF USERNAMES FOR FTP IN SYSTEM
Cpu3000: (1 ... 20): 5

This boundary defines the maximum number of usernames that can be assigned within
CPU3000 system.
147
LOBOUND352: MAX NUMBER OF FTP SESSIONS IN UNIT
Cpu3000: (1 ... 5): 2

This boundary defines the maximum number of simultaneous FTP sessions that can be active
within CPU3000 system.
LOBOUND353: MAX NUMBER OF OM DATABLOCKS IN A UNIT/SYSTEM
All: (100 ... 200): 100

This boundary defines the maximum number of OM datablocks which are available in a unit/
system. When using the SysManager 410 it is advised to set this value higher than the default.
LOBOUND354: MAX. NUMBER OF TARIFF CLASSES
All: (0 ... 255): 10

This boundary defines the maximum number of tariff classes that are available in the system.
NEBOUND355: SECOND DISABLE ENQUIRY KEYTONE DIGIT
All: (0 ... 15): 15

This boundary defines which second keytone digit (first digit defined by boundary 320 "disable
enquiry keytone digit") is interpreted as signal to release the keytone receiver for the enquiry-
by-keytone-digit facility.
The projected keytone digits, which are received by a keytone receiver in a non-dialling state
will be interpreted as a "disable signal". This disable signal is used to disable the enquiry-by-
keytone-digit facility for the remaining part of the call.
Project digit "15" (null digit) if only one disable enquiry keytone is applicable.
LOBOUND356: IPVN TCP PORT NUMBER
All: (1000 ... 65535): 2595

This boundary defines the port number for the TCP/IP server on the CIE-2 or CPU3000 that
is used for iPVN signalling connections.
NEBOUND357: MAX NUMBER OF VIRTUAL LINES
All: (1 ... 1012): 68

This boundary defines the maximum of virtual lines. The default value is the sum of the default
values of boundary 53 (max number of trunks) and boundary 239 (max number of ISDN trunk
B-channels).
148
LOBOUND358: MAX NUMBER OF VOICE LOGGING RELATIONS
All: (0 ... 500): 0

This boundary defines the maximum number of voice logging relations.
NEBOUND359: QSIG TRANSIT PINX COUNTER
All: (0 ... 31): 8

This boundary defines the maximum number of transit Private Integrated Network eXchanges
(PINX) that a call set-up may be routed through to protect the network against indefinite
looping (loop avoidance).
It is used to support the Transit Counter additional network feature (ANF-TC) at the Q
reference point between Private Integrated Network Exchanges (PINXs) connected together
within a Private Integrated Service Network (PISN) as specified in ECMA-225.
For consistent working in a combined DPNSS and QSIG network (supporting iSNet on top of
QSIG) it is advised to keep NEBOUND 14 and 359 the same in all PINXs.
NEBOUND360: MAX NUMBER OF DIFFERENT FUNCTION KEY DATA ENTRIES
All: (0 ... 65534): 600

See NEBOUND 363 for the description.
NEBOUND361: MAX NUMBER OF DIFFERENT SOFT KEY DATA ENTRIES
All: (0 ... 65534): 225

NEBOUND362: MAX NUMBER OF FUNCTION KEY DATA ENTRIES AS SUM

AVAILABLE ( FKD entries of all menus together)
All: (0 ... 65534): 600

NEBOUND363: MAX NUMBER OF TOTAL SOFT KEY DAT ENTRIES AS SUM

AVAILABLE (SKD entries of all menus together)
All: (0 ... 65534): 225

NEBOUND 362&363 define the maximum number of all Function Keys and Soft Keys over all
menus that can be stored, irrespective of whether keys definitions are equal or not.
149
NEBOUND 360&361 define the maximum number of different Function Key Data Entries and
Soft Key Data Entries that can be stored respectively.
When Function Key Data or Soft Key Data is "shared" among menus (i.e. same key definition
in different menus), less memory space is occupied and NEBOUND 360&361 can be
decreased accordingly.
Hence, if there is "no sharing" of data, the values of boundary values of NEBOUND 360&362
should be the same and NEBOUND 361&363 should be the same.
Alternatively, if it is assumed that some percentage of the Function Key data / Soft Key data
will be shared among menus then the memory space required to store the actual key data
(defined by NEBOUND 360&361) can be reduced by the same percentage.
For the calculation of the default values, "no sharing" of data is assumed and it is assumed that
all menus may be completely filled with Function Keys and Soft Keys.
Calculation example
menu 1 menu 2 menu 3 menu 4

FKD entry 1 1 1 4
FKD entry 2 2 2 5
FKD entry 3 3 3 6
FKD entry 4
the meaning of 1 ... 6 is for example as follows :

1 = the Follow me function programmed under key 6
2 = the Do Not Disturb function programmed under key 7
3 = the Automatic Ring Back function programmed under key 8
4 = the Follow me function programmed under key 1
5 = the Do Not Disturb function programmed under key 2
6 = the Break-in function programmed under key 3
then the result of the boundary values is :

NEBOUND096 = 4
NEBOUND360 = 6
NEBOUND362 = 13
A similar calculation can be done for the Soft Key data entries.
150
NEBOUND364: MAX NUMBER OF CALL FORWARDING NOT REACHABLE
All: (0 ... 255): 10

This boundary defines the maximum number of call forwarding not reachable relations. It is
introduced to prevent congestion due to successive call forwarding not reachables to the same
group. In the call present state (system option 88) the boundary defines the maximum number
of parallel call attempts. DDI calls that are rejected due to this boundary can be rerouted to
the operator when the incoming route has assistance.
LOBOUND365: PVE LISTEN PORT
All: (0 ... 65534): 2596

This boundary defines the PVE listen port to connect to the Private Virtual Enhancements
(PVE) manager.
NEBOUND366: MFC END OF CLI STRING CHARACTER
All: (11 ... 14): 14

This boundary can be used to define the appropriate end of CLI string in an outgoing MFC
message. Previously this end character of the CLI was fixed to the character I-15 (H' 0E). For
the Argentinian market it is necessary to use character I-12 (H' 0B) as the end character.
The values that are allowed to be used are:
11 (H' 0B) corresponds to I-12
12 (H' 0C) corresponds to I-13
13 (H' 0D) corresponds to I-14
14 (H' 0E) corresponds to I-15
LOBOUND367: PVE MAX EXTENSION MONITORS
All: (0 ... 65534): 50

This boundary defines the maximum number of extension monitors per monitor type.
LOBOUND368: PVE MAX GROUP MONITORS
All: (0 ... 65534): 5

This boundary defines the maximum number of group monitors per monitor type.
151
LOBOUND369: PVE MAX DATA MONITORS
All: (0 ... 65534): 50

This boundary defines the maximum number of data monitors per monitor type.
LOBOUND370: PVE MANAGER ID
All: (0 ... 65534): 1

This boundary specifies the Manager ID to verify the compatibility of the PVE manager and
PVE server.
LOBOUND371: PVE SERVER ID
All: (0 ... 65534): 12345

This boundary specifies the Server ID to verify the compatibility of the PVE server and the PVE
manager.
BOUND372: MAX NUMBER OF VIRTUAL PM'S IN A UNIT
All: (1 ... 5): 1

Note that the total number of PM's (the sum of boundary 83 and this boundary) in a unit may
never exceed 31.
NEBOUND373: DEFAULT LOCAL DOMAIN IDENTIFIER
All: (0 ... 255): 0

This value will automatically be assigned to all newly assigned DNRs (either extension, group
or operator DNRs) and all newly created (trunk/DPNSS) routes. When set to 255, or the
projected local domain identifier indicates a non-existing local domain, no local domain
identifier is assigned to new DNRs or routes.
NEBOUND374: MAX NUMBER OF LOCAL DOMAINS
All: (1 ... 255): 5

Defines the number of local domains in the iSNet-MAN.
NEBOUND375: MAX NUMBER OF LOCATION TABLE ENTRIES
All: (1 ... 65530): 50

Defines the number of location table entries in the iSNet-MAN.
152
NEBOUND376: MAX NUMBER OF NUMBERING PLAN CONVERSION ENTRIES
All: (1 ... 65530): 50

Defines the number of numbering plan conversion entries in the iSNet-MAN.
NEBOUND377: PREFIX DIGIT IN CALL RECORDING FOR E.164
All: (0 ... 15): 15

Defines the digit to be put before the number in the calling/called party field in a call recording
record to indicate that the number is the implicit representation of an E.164 explicit number.
When the default (15) is used, no digit will be shown.
NEBOUND378: PREFIX DIGIT IN CALL RECORDING FOR PNP
All: (0 ... 15): 15

Defines the digit to be put before the number in the calling/called party field in a call recording
record to indicate that the number is the implicit representation of a PNP explicit number.
When the default is used, no digit will be shown.
LOBOUND379: MAX NUMBER OF PROFILES
All: (0 ... 100): 0

This boundary defines the total number of Client Service Profiles. A client service profile
describes which logical device name will be used when either Operational Maintenance (OM)
or Switching Services (SS) is executed over TCP/IP.
LOBOUND380: MAX NUMBER OF KNOWN IP ADDRESSES
All: (0 ... 100): 0

This boundary defines the total number of IP addresses that can be related to Client Service
Profiles.
LOBOUND381: MAX NUMBER OF MUSIC ON HOLD CIRCUITS
All: (1 ... 255): 4

This boundary defines the number of Music On Hold (MOH) circuits possible in a unit.
NEBOUND382: MAX NUMBER OF NODES IN A WAN NETWORK
All: (1 ... 150): 10

This boundary defines the number of nodes in a WAN network.
153
LOBOUND383: MAX NUMBER OF VIRTUAL (NOTIFICATION) CALLS PER WAN
MOBILITY
All: (1 ... 15): 1

This boundary defines the number of simultaneous virtual (notification) calls for free-number
updates per WAN mobility.
If the default value of 1 is not suitable for the system, a good value for this boundary can be
based on the following information :
1. When there is no requirement for a parallel update, this boundary should be set to 1 to
indicate sequential update. The value of the boundary depends on the network topology
and the traffic and the availability of lines in that particular system, so that congestion is
kept to a minimum.
2. A safe value can be determined by using the following rule :
- For each node, determine for each relevant route, the maximum number of
simultaneous virtual (notification) calls possible.
- Select the route, which stands lowest with regard to the maximum number of
simultaneous virtual (notification) calls. Let the maximum number of simultaneous
virtual (notification) calls of that route be X.
- The boundary value should not be set to more than X/2.
Assuming that actual number of Virtual Channels is same as maximum number of
Virtual Channels :
- for Primary Rate, this boundary should be set to 30/2 =15.
- for Basic Rate, this boundary should be set to 2/2 = 1.
NEBOUND384: DELAY TIME FOR CLIP ON ANALOGUE SET
All: (0 ... 255): 30

The boundary defines a number of 10 msec. intervals. The default value = 30, meaning 300
msec. delay. The max value is 255 (2.55 seconds). In exceptional cases, when values above 2
seconds are used then NETIMER 50 (CP PCT Command Guarding Time) must be set to 4
seconds.
LOBOUND385: QSIG GFP OPERATIONAL MODE
All: (0 ... 3): 0

This boundary defines the operational mode for the QSIG Generic Function Protocol, which
is used for the control of QSIG Supplementary Services. The boundary value defines the
encoding of the Protocol Profile (octet 3) and the way Supplementary Service operations are
encoded : as local (universal integer type) or global (universal object identifier type) value.
154
- 0 : ECMA-165 3rd edition (1997), ECMA-165 4th edition (2001), ETS-300239 2nd edition
(1995), ISO-11582 1st edition (1995), ISO-11582 1st + corr. edition (1999), ISO-11582
2nd edition (2002) and EN300239 3rd edition (2002) specification.
The Protocol Profile is encoded as value 31 (0x1F) and the operation is encoded as local
value in universal integer type.
- 1 : ECMA-165 1st edition (1992), ECMA-165 2nd edition (1993) and ETS-300239 1st
edition specification.
The Protocol Profile is encoded as value 17 (0x11) and the operation is encoded as global
value in universal object identifier type with value (1, 3, 12, 9, operation).
- 2 : Mix of ECMA, ETSI and 'early' ISO specification.
The Protocol Profile is encoded as value 17 (0x11) and the operation is encoded as local
value in universal integer type (exceptional combination).
- 3 : Mix of ISO and 'early' ECMA and ETSI specification.
The Protocol Profile is encoded as value 31 (0x1F) and the operation is encoded as global
value in universal object identifier type (exceptional combination).
BOUND386: BYTE 1 IP ADDRESS GATEKEEPER
All: (0 ... 255): 0

Boundaries 386, 387, 388 and 389 define the four bytes of the IP address of the H323
gatekeeper.
Layout is : byte1. byte2. byte3. byte4.
All: (0 ... 255): 0

See boundary 386.
All: (0 ... 255): 0

See boundary 386.
All: (0 ... 255): 0

See boundary 386.
NEBOUND390: QSIG CHARGING OF TRANSFERRING USER INDICATOR
All: (0 ... 2): 1
155
This boundary defines the response on an 'AOC Complete signal' with the next values :
- 0 = Free Of Charge
- 1 = Continue Charging
- 2 = Stop Charging
NEBOUND401: MAX LENGTH OF CALL REROUTING DIVERSION TABLE
All: (0 ... 65530): 50

This boundary defines the maximum length of call rerouting diversion table.
3.4. SYSTEM OPTIONS
This section contains a description of all the system options of an ISPBX system.
NESYSOP000: MULTI-UNIT
All: default=False
This parameter defines if the unit is a stand alone system or if the unit is part of a SOPHO iSNet
WAN.
LOSYSOP001: CALLING IDENTITY SUPPRESSION IN TT OUTPUT
All: default=False
This option is used in the toll ticketing process.
If the option is TRUE and a call is not identified as malicious call trace then the calling identity
is not displayed.
LOSYSOP002: KEYTONE EXTENSIONS
All: default=False
Keytone extensions are connected to the system.
If the option is FALSE, the system will assume that only extensions with rotary dial are
connected, thus no receiver keytone will be connected.
If the option is TRUE, the system will connect a receiver keytone when a new call is made, no
matter if the originating extension is keytone or rotary dial. PMCs or RST-KDs have to be
present and in service in that case.
156
NESYSOP003: DPNSS ACCOUNT CODE RESTRICTION
All: default=False
This option switches the interpretation of the account code received from another ISPBX via
DPNSS.
- DPNSS network with SOPHO ISPBXs only:

The system option "DPNSS account code restriction" is set to FALSE. The account
information contains the following parameters:
- Cost centre type (1 digit).
- Private/Business indicator (1 digit).
- Department of the caller (3 digits).
- Password indicator (1 digit).
- Cost centre number (variable length, maximum 12 digits, 16 for PIDs).
Except for the cost centre number, each parameter of the account information has a fixed
length. The cost-centre number is the last parameter of the account information. With the
length indicator of the DPNSS account code string, the length of the cost centre number
can be determined.
- DPNSS network with SOPHO ISPBXs and non SOPHO ISPBXs:
The option "DPNSS account code restriction" is set to TRUE. The account information
contains the cost centre number (variable length, max. 12 digits, 16 for PIDs) only.
LOSYSOP004: CALL SET UP TO INDIVIDUAL METERING
All: default=False
Metering pulses received during operator call set up are for the extension account.
If the option is FALSE, they will be for the operator account.
LOSYSOP005: CALL TO INDIVIDUAL AND TAX METERING
All: default=False
Define if metering pulses have to be stored in both the operator and individual extension
buffer in case of operator metering.
LOSYSOP006: DESTRUCTIVE METERING READ ALLOWED
All: default=False
Individual metering buffer should be reset to zero after read out.
157
LOSYSOP007: SHUTTLE WITH FORCED RELEASE
All: default=False
Define whether the "shuttle" is selectable by dialling a digit or that it is defined by the type of
opposite parties in relation to LOSYSOP008, -009, -010 and -011.
If the option is TRUE shuttle is selectable independent of the type of opposite parties.
LOSYSOP008: SHUTTLE ALLOWED EXTENSION DIALLED EXT ON HOLD
All: default=False
Define if "shuttle" is allowed in case an internal extension is dialled in enquiry condition with an
internal extension on hold.
With this parameter is defined if "shuttle" is allowed in a situation where an internal extension
was dialled with an internal extension on hold.
LOSYSOP009: SHUTTLE ALLOWED EXTENSION DIALLED TRUNK ON HOLD
All: default=False
Define if "shuttle" is allowed in case an internal extension is dialled in enquiry condition with a
trunk on hold.
With this parameter is defined if "shuttle" is allowed in a situation where an internal extension
was dialled with a tie line or exchange line on hold.
LOSYSOP010: SHUTTLE ALLOWED TRUNK DIALLED EXTENSION ON HOLD
All: default=False
Define if "shuttle" is allowed in case a trunk is dialled in enquiry condition with an internal
extension on hold.
With this parameter is defined if "shuttle" is allowed in a situation where a trunk was dialled
with an internal party on hold.
LOSYSOP011: SHUTTLE ALLOWED TRUNK DIALLED TRUNK ON HOLD
All: default=False
Define if "shuttle" is allowed in case a trunk is dialled in enquiry condition with a trunk on hold.
With this parameter is defined if "shuttle" is allowed in a situation where a tie line or exchange
line was dialled with a tieline or exchange line on hold. In this situation transit situations can be
originated, but that depends on the transit allowances between routes.
158
LOSYSOP012: DIVERSION ON BUSY PLE ALLOWED
All: default=False
Define if diversion of calls to a busy PLE is required.
With this parameter incoming calls which are routed to a busy PLE can be diverted to the
operator/night service.
LOSYSOP013: DIVERSION ON BUSY INE ALLOWED
All: default=False
Define if diversion of calls to a busy INE is required.
With this parameter incoming calls which are routed to a busy INE can be diverted to the
operator/night service.
LOSYSOP014: SERIES CALLS PROHIBIT
All: default=False
Define if the set up of series calls is prohibited.
With this parameter the set up of series calls can be prohibited. This counts for incoming as
well as for outgoing traffic (Germany).
LOSYSOP015: REROUTE DON'T DISTURB
All: default=False
This option defines if internal calls and DDI calls via a non-assisted trunk route, to a DNR (or
group DNR, since Call@Net 2.5) with an active DND must be rerouted to the operator/night
service.
The operator/night extension can by-pass this protection.
LOSYSOP016: IABD ALLOWED FOR OPERATORS
All: default=False
Define whether the facility Individual Abbreviated Dialling and Last External Number
Repetition is available for operators.
If the facility IABD and LENR is assigned to operators, it should be considered that every
external number that is dialled by an operator has to be stored.
159
LOSYSOP017: FACILITY CLOCK OPERATES ON TRAFFIC SERVICE CLASS
All: default=False
Facility clock or operator can change traffic service class If the option is TRUE, the facility clock
is able to change the traffic service class and the operator day/nigh/condition not.
If the option is FALSE, the operator day/nigh/condition is able to change the traffic service class
and the facility clock not.
LOSYSOP018: CALL WAITING TONE AFTER EXTENDING TO BUSY

EXTENSION
All: default=False
Whether or not call waiting tone burst is given to a busy extension when a call is extended to
that extension by an operator or night extension.
If the option is TRUE and a call is extended by the operator or the night extension to a busy
extension that busy extension will get a call waiting tone burst (unless the extension is data
protected) to notify the extension that a call is waiting.
If the option is FALSE, the call waiting tone burst will not be given.
LOSYSOP019: OFF HOOK VOICE MAIL PROTOCOL
All: default=False
This option defines which protocol is used for the Voice Mail Server.
If this option is 'TRUE' the off-hook protocol is used. This means that the ISPBX waits for the
VMS to answer the call. After the VMS has answered the call the ISPBX sends the information
as DTMF digits to the VMS.
If the option is 'FALSE' then the on-hook protocol is used. This means that the ISPBX sends
information as DTMF digits to the VMS before sending ring current.
LOSYSOP020: BLOCK OUTGOING CALLS ON TT DATA BLOCK CONGESTION
All: default=False
If the option is TRUE, new outgoing calls will be blocked on routes with toll ticketing if there
is congestion on toll ticketing data blocks.
If the option is FALSE, the oldest toll ticketing data block will be overwritten. Use DIPOOL to
check for shortage on LDBs or CDBs.
160
LOSYSOP021: REACTIVATING BUZZER
All: default=False
If there is a call waiting longer than the projected reactivating buzzer time, the system
overrules the buzzer-off condition.
If the option is TRUE, the call buzzer is reactivated if there is a call waiting longer than a the
time limit which is set by NEBOUND075 (reactivating buzzer time).
LOSYSOP022: GENERAL CALL AND OVERLOAD SIGNALLING
All: default=False
The overload signalling and general control facilities can be activated.
If the option is TRUE:
- Whenever the first overload level, in the Ai or C queue, is reached, the Q-led is activated
with a slow rhythm,
- Whenever the second overload level, in the Ai or C queue, is reached, the Q-led is
activated with a fast rhythm.
- All the calls queued in the Ai, C and M queues can only get with the A button (actions on
the C and M buttons are rejected).
LOSYSOP023: M INDIVIDUAL LED FLASH CONDITION
All: default=False
Define the M-individual led flash condition.
This parameter defines if the operator M-lamp should start flashing in case of an individual call
to operator.
LOSYSOP024: RECALL ON HOOK ALLOWED
All: default=True
If an internal party goes "on hook" in selection with an external party on hold while the number
(may be) complete condition is not reached, this option will define whether the external party
will be released or queued in the operator's C queue.
If the option is TRUE, the external party is queued in the operator's C queue.
If the option is FALSE, the external party is released according to the normal release
procedure.
161
LOSYSOP025: M LED FLASH CONDITION
All: default=False
Define the M-led flash condition.
This parameter defines if the operator M-lamp should start flashing in case of a preferred call
to operator.
LOSYSOP026: SOURCE INFO ROUTE WITH ACCESS CODE REPETITION
All: default=False
Indicating whether the access code is sent to the source info route.
This parameter is only valid on access of a route with source info indication (datakop). It
controls whether or not the access code is sent after sending the identification of the source.
TRUE : <DNR><ACCESS CODE>
FALSE : <DNR>
LOSYSOP027: MSG WAITING QUEUEING SOFTRING
All: default=False
Whether or not a message waiting softring is repeated.
If the option is TRUE, the message waiting softrings are given repeatedly.
If the option is FALSE, the message waiting softring is given only once.
LOSYSOP028: WAIT FOR CLOSE SIGN
All: default=False
Wait for the close sign before handling an initiated or canceled facility.
If the option is TRUE, this indicates that after initiating or cancelling a facility which changes
data in the ISPBX a close sign (#) should be entered before the entered command will be
executed.
LOSYSOP029: BLOCK TRUNK AFTER DETECTION TIME OUT
All: default=False
Define if a trunk line will become "blocked" (ABL fail condition) if the dial tone detection time
out occurs.
162
This option defines if a trunk line will be "blocked" when the guard timer of the external dial
tone detection runs out.
When blocking takes place in this situation a test initiated by the trunk service after a while will
test the trunk line on detection of the external dial tone. If in this test the trunk line is found in
order the port will be released to be used again for trunk traffic.
LOSYSOP030: MORE THAN 10 PULSES AS 1 DIGIT TO PUBLIC EXCHANGE
All: default=True
Define if one digit, which is sent to the public exchange can consist of more than 10 pulses.
With this parameter it is defined if '*', '#' and 'D'-'F' can be dialled to the public exchange or
not. This option is only valid, if the concerning bundle data is 'impulse-dialling'.
LOSYSOP031: LOS SWITCH 1
All: default=True
Reserved for later use.
All: default=True
LOSYSOP033: NO RELOAD VIA SENSOR POINT 6
All: default=True
This parameter indicates whether the LOS must activate a reload when alarm sensor point 6
changes state. Alarm sensor point 6 is located on the main distribution frame where sensor
point count starts at 1 and ends at 8.
TRUE corresponds with reload DISABLED.
LOSYSOP034: OPERATIONAL MODE INSTEAD OF TEST MODE
All: default=True
This parameter indicates whether the system is running in an operational environment, or in
a LAB environment.
LOSYSOP035: OPERATIONAL APPLICATIONS OUTPUT FORMAT
All: default=True
163
This option defines whether the system gives operational applications output format or LAB
output.
If the option is TRUE, the system gives operational applications output format.
If the option is FALSE, the system gives LAB output.
All: default=True
All: default=True
All: default=True
LOSYSOP039: TIMER 201 USED WHEN ANNOUNCEMENT FOR DDI TO IDLE

EXTENSION
All: default=False
This parameter determines whether the time before a voice announcement message for a
'successful DDI call' is given to an incoming trunk is determined by timer 201 or not.
If this parameter is TRUE then timer 201 is used. When it is FALSE then timer 99 is used.
NESYSOP040: CLOSED NUMBER SCHEME IN NETWORK
All: default=False
The number scheme of the directory numbers in an inter PBX network (DPNSS).
If the option is FALSE, the system will assume that an open number scheme is used. The
cluster-id of the local PBX is not a part of the directory numbers.
If the option is TRUE, the system assumes that a closed number scheme is used. The first part
of each directory number consists of the cluster-id of the local PBX.
164
NESYSOP041: DETERMINE DESTINATION ROUTES IN HOLD UNIT
All: default=False
This option indicates whether in case of enquiry calls the destination routes should be
determined in the hold unit.
LOSYSOP042: DELAY BEFORE ON HOLD BY OPERATOR
All: default=False
This option specifies if the facility delay before on hold by operator is active (this is a French
facility).
LOSYSOP043: CII TYPES WITH EVEN AND ODD NUMBERED CHANNELS
All: default=True
This option must always have the value TRUE. When FALSE the system will not function.
LOSYSOP044: NIGHT MODE DISPLAY
All: default=False
The night mode display facility can be activated.
If the option is TRUE, all the operators in an assistance group are absent, the spare LED is lit
or the 'moon' sign/plain text (depending on the type of operator position) is given on every
operator position of this assistance group to notify the night mode.
LOSYSOP045: PERIODIC CALL WAITING TONE
All: default=False
Periodic call waiting tone to extensions in case of COB.
If the option is TRUE, the call waiting tone burst is given periodically to the busy extension
whenever calls are in the camp on busy situation to that extension.
If the option is FALSE, the call waiting tone burst is given only once.
LOSYSOP046: DYNAMIC GROUP COB WITH INTRUSION ALLOWANCE
All: default=False
If the option is TRUE, the COB facility is only allowed whenever the call waiting tone is
possible. The number of COB cases for a group arrangement depends on the number of
present members in the group. This option overrules the COB limitation given by the
165
simultaneous of COB cases system boundary.
If the option is FALSE, the standard COB facility allowance is used.
NESYSOP047: POST DIALLING AVAILABLE
All: default=False
This option specifies if the facility postdialling is available.
This facility offers the possibility of postdialling, which means dialling of digits after the speech
condition has been reached.
LOSYSOP048: NUMBER SUPPRESSION IN TT OUTPUT
All: default=False
This option is used in the toll ticketing process.
If the option is TRUE and a call is a private call then the number dialled is not displayed.
LOSYSOP049: SAS AH SAD PRESENT
All: default=False
Signalling At Distance (SAD) aperture is connected to the system.
If the option is FALSE, the system will assume that no SAD is present, so alarm level
information will never be passed to SAD but to other destinations.
If the option is TRUE, the system will (under certain alarm routing conditions) reroute the
alarms to SAD (alarm level information by a modem through the PSTN to a remote
destination).
LOSYSOP050: SAS AH SAD MANUAL CONFIRMATION
All: default=False
Specify weather a Remote Alarm must be confirmed.
This parameter defines whether an alarm status change signalled to the remote maintenance
port must be confirmed with CALSIG or that no confirmation is necessary.
If the option is TRUE and manual confirmation is not executed within a given time after a
remote alarm status change, the alarm status is rerouted to 'local'.
166
LOSYSOP051: IGNORE PROGRESS INDICATOR IN ISDN RELEASE PROTOCOL
All: default=False
When this system option is set to FALSE then for calls between extensions/operators and
ISDN trunks, on receipt of the DISCONNECT message by the ISDN trunk:
- the B-channel will be connected depending on the received progress-indicator (in-band

information),
- invocation of ISDN supplementary services (MCI) is possible,
- release of the call is postponed until the extension or operator clears the call.
When the option is set to TRUE the call will be cleared in both directions without examination
of the progress indicator.
Upgrading scenario
This option is re-introduced in Call@Net 2.5. It was already used in SSW 805 (called
"Enhanced ISDN Release Protocol"), but it had an "inverted" meaning.
Customers who now have Call@Net and are happy with the way the ISDN release protocol
is implemented must not be confronted with a change in functionality.
This "inverted" meaning has the following consequences :
- When upgrading either from SSW 805 or Call@Net, current system behaviour will be
maintained.
- When upgrading from SSW 805 the "old system option 51" will be inverted. That is,
behaviour as projected in SSW 805 will be maintained.
- When upgrading from Call@Net the "new system option" will be FALSE so that the
progress indicator is not ignored.
LOSYSOP053: NETWORK INCOMPATIBILITY ALLOWED
All: default=False
The network compatibility function can be used.
If the option is FALSE, the network compatibility function cannot be used.
If the option is TRUE, the network compatibility function can be used.
This option is NOT allowed to be projectable for SPELL!
167
LOSYSOP054: NETWORK INCOMPATIBLE MARK
All: default=False
The network is incompatible.
If the option is FALSE, the network is compatible.
If the option is TRUE, the network is incompatible.
This option is controlled by the program and may therefore not be protected for SPELL!
LOSYSOP055: TRANSFER BEFORE ANSWER ALLOWED
All: default=True
This option indicates if a transfer is possible before the second opposite party has answered
the call.
If the option is TRUE, then transfer is allowed.
LOSYSOP056: RECALL AFTER CLEAR IN ENQUIRY
All: default=False
This option indicates whether or not a recall to the initiator should be executed if the initiator
goes on hook in selection or alerting if this is not allowed.
If this option is TRUE, the recall shall be executed.
LOSYSOP057: MML OTHER THAN ENGLISH
All: default=False
This option indicates whether texts of OM commands (headers, guidance, messages etc.) are
English or other than English.
If the option is FALSE, the texts are English.
If the option is TRUE, the texts are other than English.
LOSYSOP058: DESKSHARING AUTOMATIC DOWNLOAD FKM
All: default=True
If this option is true, the function key menu (FKM) is downloaded to the set each time a
desksharing DNR is activated on the set.
168
If this option is false, the FKM is downloaded to the set only if a desksharing DNR is activated
to a set where no DNR was present.
LOSYSOP059: DESKSHARING AUTOMATIC DEACTIVATE PREVIOUS
All: default=True
This option indicates whether a previous desksharing DNR is automatically deactivated when
a new desksharing DNR is activated on the set. In this case there can only be one desksharing
DNR per set.
If this option is false, the previous desksharing DNR remains on the set when a new one is
activated. All (desksharing) DNRs on the set can be called. The latest one is activated is the
one that is used as originator when a call is made.
LOSYSOP060: FDCR INSTEAD OF TOLL TICKETING
All: default=False
This system option defines whether the Full Detailed Call Recording or the Toll Ticketing is
activated in the system.
If the option is TRUE, the Full Detailed Call Recording is activated.
If the option is FALSE, the Toll Ticketing is activated.
NESYSOP061: STATION CALL IN CASE OF IDLE GROUP MEMBER
All: default=True
This is an option which is typical for the SOPHO CallManager ACD facility 'Station Call'.
This option determines whether or not a station call (i.e. a first announcement message) must
be given to the calling party if there are idle members in the ACD group.
If the option is FALSE and the destination is idle, then the destination is rung immediately and
no station call is given to the caller.
If the option is TRUE a station call is given regardless the status (i.e. idle, busy etc.) of the called
party.
NESYSOP062: DIGIT CONVERSION ON OUTGOING ROUTE POSSIBLE
All: default=False
This option defines whether digit conversion on outgoing route is to be performed or not.
169
If the option is TRUE, the given digit string is converted to a digit string found in the digit
combinations for the specified roue and destination.
If the option is FALSE, no digit conversion is performed.
In order to fully utilize the Least Cost Call Routing facility, this system option must be set to
TRUE.
NESYSOP063: NU TONE AFTER PROCEDURE ERROR
All: default=False
This option defines which tone is sent to the user after a procedure error.
If the option is TRUE, the system sends the 'NU tone'.
If the option is FALSE, the system sends the 'busy tone'.
NESYSOP064: ACTIVATE CFWB ON ASSIGN
All: default=False
This option defines if CFWB (Call Forwarding When Busy) relation will be activated on
creation of the relation.
Default (false): the relation will not be activated on creation.
LOSYSOP065: REROUTE NO RESPONSE
All: default=False
This option defines whether rerouting of calls to a not responding S0-bus or DECT handset is
required on non assisted trunks.
No response is received, if the terminal is disconnected from the S0-bus or the handset is
switched off.
On assisted trunks, rerouting in case of no response is always applicable.
LOSYSOP066: SYSTEM WITH CENTRAL SWITCHING NETWORK
All: default=True
This option defines whether the system contains a CSN-BC/SNS/SCU or not.
If the option is TRUE, the system must contain a central switching card.
170
If the option is FALSE, the system may not contain a CSN-BC/CPU-ME/MT.
LOSYSOP067: SAS AH V.28 SIGNALLING ORED
All: default=False
This option determines the working mode of the V.28 alarm signalling device on the top
VIC3000 connector.
If the option is TRUE, the working mode will be the 'OR mode', meaning that the first V.28
signal line indicates the presence of a Major OR a Minor OR a Circuit Blocked alarm. The other
two signal lines are not used in this case.
If the option is FALSE, the three V.28 signal lines indicate successively the presence of a Major,
a Minor and a Circuit Blocked alarm.
NESYSOP070: DISCARD CLI IN CASE OF INTERWORKING
All: default=False
If TRUE, the calling and connected line identities are NOT transmitted towards ISDN trunks
in case of interworking (e.g. via DPNSS, ISDN transit).
Note: This is required by some Telecom organizations and/or public exchanges to avoid numbers
outside the allocated number range.
NESYSOP071: BLOCK ARB DESTINATION FOR NEW CALLS
All: default=False
This option defines whether an ARB destination will be blocked in the meantime between
release (on-hook) and receipt of an ARB call setup.
NESYSOP072: KEEP ARB RELATION AFTER RING TIME OUT
All: default=False
This option defines whether an ARB relation is kept ('TRUE') or not ('FALSE') if an ARB initiator
does not answer an ARB call back call.
NESYSOP073: CANCEL ARB RELATION AFTER DIALLING SAME DESTINATION
All: default=False
This option defines whether an ARB relation is cancelled ('TRUE') or not ('FALSE') if an ARB
initiator selects the same destination again.
171
NESYSOP074: UNCONDITIONALLY CLIR
All: default=False
This option defines whether the facility 'CLIR' is enabled permanently for a complete ISPBX.
All other CLIR system options are neglected if this option is set TRUE !!
'TRUE' means 'CLIR for complete ISPBX enabled'.
'FALSE' means 'CLIR for complete ISPBX disabled'.
NESYSOP075: OVERRULE CLIR FOR OPERATORS
All: default=True
This option defines whether the facility 'Overrule CLIR' is available for operators.
'TRUE' means 'Overrule CLIR available'.
'FALSE' means 'Overrule CLIR not available'.
NESYSOP076: OVERRULE CLIR FOR TT AND CALL RECORDING
All: default=True
This option defines whether the facility 'Overrule CLIR' is available for the Toll Ticketing and
Call Recording output.
'TRUE' means 'Overrule CLIR available'.
'FALSE' means 'Overrule CLIR not available'.
NESYSOP077: OVERRULE CLIR PROHIBITED FOR EXTENSIONS
All: default=False
This option defines whether the facility 'Overrule CLIR' is prohibited for extensions/ terminals
with Facility Class Mark 'Overrule CLIR'.
'TRUE' means 'Overrule CLIR prohibited'.
'FALSE' means 'Overrule CLIR allowed'.
NESYSOP078: BSPT IN BSP-ID NOT ALLOWED AT OPERATORS
All: default=False
This option defines whether the BSPT in the BSP-ID is accepted (L-button) and displayed at
172
an operator console if an OM command is executed.
NESYSOP079: CLIR IN DPNSS SEND ZEROS
All: default=False
This option defines whether CLIR/COLR via DPNSS is supported.
If the option is 'FALSE', the NPR-string (Number Presentation Restriction mandatory) is used
via DPNSS to indicate that an extension has CLIR/COLR.
However, if the call is made via a PABX that does not support the NPR-string, the call will not
succeed.
If the option is 'TRUE', the identity of an extension that has CLIR/COLR, is replaced by zeros
before sending it via DPNSS to another PABX.
LOSYSOP080: AUTOMATIC RECALL ON TRUNK UPON ENQUIRY
All: default=False
This option specifies if, upon enquiry of an extension in conversation with a trunk line, a recall
is sent to the PSTN and no other enquiry actions are started. If this option is FALSE then the
PABX enquiry functionality is followed.
LOSYSOP082: FDCR NO EMPTY PARTY B FIELD ALLOWED
All: default=False
This option specifies whether or not in the output of FDCR an empty party B identification
field is replaced by the party B category. By default an empty party B identity (null digits) is
allowed.
NESYSOP083: ROUTE OPTIMISATION
All: default=True
This option defines whether the ISPBX may initiate and execute (on request from another
ISPBX) route optimization.
In case of a multiple unit configuration, Route Optimisation must be applied in the unit where
the original DPNSS route is connected to.
If the option is 'FALSE', no route optimization is initiated nor executed in this unit.
If the option is 'TRUE', route optimization is initiated or executed in this unit.
173
NESYSOP084: INTEGRATED PASSWORD DIALLING
All: default=False
This option defines whether or not the ISPBX validates Passwords, PIDs and Cost Centres.
If the option is 'TRUE', the ISPBX validates Passwords, PIDs and Cost Centres. You must enter
the relations for the Passwords, PIDs and Cost Centres via OM. If the option is 'FALSE', the
SSM Access Manager is required for validation. In this case Password, PID and Cost Centre
relations have to be entered via the SSM.
NESYSOP085: UPGRADED COS AUTONOMOUSLY TO NIGHT
All: default=False
This option defines whether or not the ISPBX autonomously switches all Upgraded traffic
classes to Night traffic class, when the system enters Night condition.
If the option is 'TRUE', the Upgraded traffic classes are automatically switched to night.
If the option is 'FALSE', the Upgraded traffic classes are not automatically switched to night.
NESYSOP086: UNIQUE CUSTER ID
All: default=True
This option defines whether the Cluster-ID (option 'TRUE') or the combination Cluster-ID +
Sub-Cluster-ID (option 'FALSE') will be used as PBX unique identification. The route
optimization mechanism and the flexible operator mechanism use this PBX unique
identification.
NESYSOP088: PREVENT ALERT FROM EMPTY S0 BUS
All: default=False
This option specifies whether the call enters the alerting phase at the moment the setup
message is sent towards the ISDN terminal (option is FALSE) or the alerting phase is entered
after a reply on the setup message is received from the ISDN terminal (option is TRUE).
LOSYSOP090: WARNING TONE ON TIME-BREAK CALLS
All: default=False
This system option specifies if the warning tone is given to the parties involved (option is
TRUE) in a time-break call before it is being cleared.
The warning tone is not given in case the connection is data protected.
174
LOSYSOP093: SUPPRESS DIAL TONE
All: default=False
This option determines whether the dial tone for extensions is suppressed; it is only valid for
special projects.
LOSYSOP094: DIRECT CHARGING DISPLAY REFRESH
All: default=False
This system option specifies whether at receipt of charging information at a trunk line, the
charging display at an extension has to be updated directly.
This option (if the value is TRUE) applies to analogue trunks and digital trunks with channel
associated signalling i.e. when metering pulses are received.
Whether the advice of charge is displayed depends among other things on the extension and
trunk characteristics.
WARNING: APPLYING THIS OPTION MAY CAUSE A HIGH SYSTEM LOAD
LOSYSOP095: FTLD TO MATCH CLI
All: default=False
This option is valid for special projects only.
This option specifies whether or not the projected FTLD (Fixed Trunk Line Destination) string
is to be compared with the callers CLI (Calling Line Identification) upon seizing a trunk line
with the FTLI facility (option is true) or not (option is false).
NESYSOP098: INSERT CLUSTER ID FOR LOCAL DNR AT SUPERVISOR
All: default=False
When a DPNSS open numbering scheme is used and a valid internal number has to be
displayed on a digital operator console like the SuperVisor 25, 35 and 60(E), and LOSYSOP
105 (TSD for Supervisors Active) is disabled, this option specifies whether the number is
displayed as NDNR (Network DNR) or as DNR.
A number is specified as "valid internal" when it is an existing DNR belonging to the same
DPNSS cluster as the operator console.
If the option is TRUE the number is displayed as NDNR (Network DNR)
If the option is FALSE the number is displayed as DNR.
175
In all other cases (e.g. closed numbering scheme is used or the number is not existing/
external), the number displayed will be unaffected.
This option is also used to enable a SuperVisor 60(E) to lookup the name of a number in the
Central Phoneware Database based on NDNRs. Other SuperVisors don't use the PhoneWare
Database (Phonebook).
LOSYSOP099: ACCESS EXTERNAL CNND DATABASE FOR INTERNAL

TRANSLATION
All: default=False
This option determines whether the external database is accessed for the translation of an
internal number (DNR) to a name string. Calling Name Number Display (CNND) will first try
to translate the internal number via the internal database (located in the system itself), but if
this fails for some reason (e.g. the internal database is not present or the DNR/name relation
is not found) this option (if TRUE) allows the DNR to be translated by the external database
application. So this option determines whether the external database application is accessed
or not.
LOSYSOP101: LOCAL CNND FUNCTION ACTIVE
All: default=False
This option determines whether CNND can access the internal database for translating
internal numbers (numbers of the local unit) into names.
Note that the internal database can only translate telephone numbers of the local unit.
Telephone numbers received from a route can only be translated with the help of an external
database (BTS Phoneware application). The external database can even be used as a fall back
for the internal database (for the translation of internal numbers) if system option 99 is TRUE.
If this option is FALSE, then CNND does not work.
LOSYSOP102: OPTIMISE STATUS MONITORING MESSAGES
All: default=False
When this system option is TRUE, the load in the system because of status monitoring is
minimised. In case a group member is monitored for 'unrestricted status monitoring' and the
status changes, only a message for 'unrestricted status monitoring' is sent by the CPU to other
system parts. No (unnecessary) messages are sent for group status monitoring (for groups for
which 'group display' is TRUE and 'LED based status monitoring' is FALSE (CRGRPA/
DIGRPA)).
This option must be FALSE if DLC-A/B and/or KTLC-01 boards are used.
176
LOSYSOP103: SHOW ETHERNET ALARM
Cpu3000: default=False
When this option is true alarm code 63, QLF 10 is given. This alarm informs the user about
the status of the UTP Ethernet connector.
When this option is FALSE no UTP connector related alarms will be raised.
In case of an Ethernet related application (e.g. CSTA over Ethernet) it is advised to set this
option to TRUE. When no Ethernet related applications are installed set this option to FALSE
to prevent unwanted alarm messages.
LOSYSOP104: PROHIBIT DESKSHARING AND INSTALLATION BETWEEN

UNITS
All: default=False
This option is used to prohibit that DNR data is changed in the local unit when using
desksharing or installation. When this system option is TRUE, then moving DNRs from and to
a specific unit using both facilities will be prohibited. An initiator performing such an action will
receive number unobtainable tone.
Moving a DNR within a unit is still possible, however creating a DNR using installation is
prohibited.
LOSYSOP105: TSD FOR SUPERVISORS ACTIVE
All: default=False
This system option defines whether the TSD function is available for digital operators (SSV25/
35). If the option is TRUE , the system will try to translate the DNR of internal parties which
are retrieved from the different operator queues into names. If this is successful, the name is
displayed for the operator. Note that an SSM/SysManager with TSD functionality is required.
LOSYSOP106: FREE NUMBERING ACTIVE
All: default=False
When this system option is TRUE, Free Numbering can be used in an iSNet WAN with a
closed numbering scheme : NESYSOP 040 (closed number scheme in network) must be set
to TRUE as well.
Any Free Number in the network can be moved to anywhere in the network with most
characteristics like facility class marks, traffic classes etc.
177
LOSYSOP107: OFFER CALL TO SUPERVISORS AT FIRST ANNOUNCEMENT
All: default=False
This system option specifies if the first announcement is awaited before the call is queued and
notified to the operator. This option is only relevant when an IAS announcement is involved.
When this system option is TRUE, the call is offered immediately to the operator.
When this system option is FALSE, the call is offered after the first announcement has finished
LOSYSOP109: AUTOMATIC TRANSFER OF 'INTRUSION' AND 'FORCE RELEASE'

DIGITS
All: default=False
This system option specifies whether or not the intrusion digit and the force release digit
should be automatically transferred after a first initiation of a 'network priority/forced release'
call (FCM 61) to the next exchange.
LOSYSOP110: CDD DATABASE PRESENT
All: default=False
This option has become obsolete since Call@Net 2.5 because both the Internal CNND and Internal
CDD functions share the same database.
This option specifies if the CDD database is present or not. When option is true it is possible
to load CDD-data into the internal Name-Number database.
Actual usability of the CDD feature is controlled by LOSYSOP111.
LOSYSOP111: CDD FEATURE ACTIVE
All: default=False
This option specifies if the CDD feature (browsing from a terminal) is allowed.
LOSYSOP112: CNND BASED ON 8 BITS ISO 8859 LATIN 1 OR 7 BITS ASCII
All: default=False
CDD supports 8 bits ISO 8859 Latin 1. In SSW 805, CNND supports 7 bits ASCII.
This system option defines whether CNND uses either 7 bits ASCII or 8 bits ISO 8859 Latin
1. Only the ErgoLines, the SuperVisor 25 and -30 (and perhaps a high-end DECT handset)
support 8 bits; all other external devices can only handle 7 bits. Note that the SysManager 410
supports 8 bits for the entry of names.
178
LOSYSOP113: CSTA MONITOR EVENTS ONLY AFTER DEVICE IDLE
All: default=False
When this option is false, then CSTA events are generated for a monitor as soon a monitor for
a device is activated.
When this option is true, then CSTA events are generated for a monitor as soon a monitor for
a device is activated AND it has been idle.
LOSYSOP114: HIGHEST OF PID OR EXTENSION TRAFFIC CLASS USED
All: default=False
This option specifies which traffic class is used for PID dialling. If this option is false (default),
the traffic class belonging to the PID is used for PID dialling calls. If this option is true, the
system determines which traffic class has the highest value: the one belonging to the PID or
the one belonging to the extension. The highest one is used for a PID dialling call.
NESYSOP115: FUNCTION KEY DOWNLOADING BY EXTERNAL (Call@Net

Application Server)
All: default=False
This option specifies if the ISPBX should start downloading the function key menu when this
is requested by the terminal or send a request towards the Call@Net Application Server
(Management@Net / MyOffice@Net).
If this option is TRUE the Call@Net Application Server is in charge of handling the function
key menu downloading. The ISPBX only starts downloading when the OM command
DOWNLD is given. All other situations that lead to a function key menu download results in
a message towards the Call@Net Application Server.
LOSYSOP116: ACD DIVERSION CHAINING ALLOWED
All: default=False
This option specifies whether or not chaining of ACD diversions (CFWN, CFWO and CFWE)
is allowed.
LOSYSOP117: ABSENT SWITCHING OF LAST ACD MEMBER PROHIBITED
All: default=False
This option specifies whether or not the last present member of an ACD group can be
switched absent.
179
LOSYSOP118: TIME BREAK ACTIVE FOR OPERATORS
All: default=False
The time break function is used to limit the conversation time of (incoming and outgoing) calls
between extensions or trunks and external parties.
When an operator is involved in the connection, time break can be enabled or disabled,
depending on whether this option is set TRUE or FALSE.
LOSYSOP119: UNIQUE LINE NUMBERING
All: default=False
This option can be projected only. It can not be changed (using CHOPTI or EXSUBC) in a
running system.
LOSYSOP120: iPVN ACTIVE
All: default=False
This option (together with license item 29) specifies whether iPVN is active or not.
LOSYSOP121: PVE ACTIVE
All: default=False
This option is used to enable (TRUE) or disable (FALSE) the possibility to start the PVE service.
When this option is FALSE it is not possible to start the PVE service using OM command
STSRVC or a operational system start.
Once the PVE service is started no check is done on this option.
NESYSOP122: OPPOSITE PBX DOES NOT SUPPORT DO NOT DISTURB OVER

DPNSS
All: default=False
This option specifies whether or not other PBXs in the DPNSS network supports the BTNR
188 supplementary service Do Not Disturb (DND).
If the option is FALSE then all PBXs in the DPNSS network supports the BTNR 188
supplementary service DND.
If the option is TRUE then one or more PBXs in the DPNSS network does not support the
BTNR 188 supplementary service DND.
180
Since Call@Net 2.5 the BTNR 188 supplementary service DND is supported by the CPU
software. When one or more PBXs in the DPNSS networks does not support the BTNR 188
supplementary service DND (e.g. Call@Net 2.4 and lower) then this option should be set to
TRUE.
This prevents unexpected call termination when calling an extension or group that has the
DND functionality activated.
Consequence of setting this system option is that the re-routing to assistance does not fully
work according to the new Call@Net 2.5 specification.
Also bypassing de DND situation does not work for all types of call scenarios.
LOSYSOP123: PVE SHORT XML
All: default=True
This option determines whether the output of the PVE manager is short or long XML :
- when TRUE, the output is short XML : 2-character XML element names.
- when FALSE, the output is long XML : complete element names.
LOSYSOP124: CLIP ON ANALOGUE ETSI TERMINALS
All: default=False
This option is used to select the protocol for CLIP on analogue ETSI terminals :
- when FALSE : Danish specification TDK-TS 900 216 (default).

- when TRUE : ETSI standard EN300 659-1 Annex B prior ringing with/without polarity
reversal.
When polarity reversal is required, e.g. for SOPHO BaseLine Pro terminal with CLI, then the
following requirements must also be met:
- PMC package 410.08.01/510.08.01 (or higher) or PPU package 170.05.01/27.05.01 (or

higher);
- The terminal must be connected to an ALC-F or ALC-G circuit with signalling group
32XX, of which bit 10 ' Subscriber with CLI' must be on and bits 2, 7 and 9 must be off.
This option is obsolete since Call@Net 2.11 because this is now enabled via FCM 74.
LOSYSOP125: BUSY INDICATION FOR CONGESTION ON ACD GROUPS
All: default=False
This option specifies whether congestion (false) or busy tone (true) is sent for incoming calls
181
to an ACD group in the following situation:
- ACD group has extended property F set to '1';

- incoming trunk call is made via a line in a bundle with signalling type ISDN-A or ISDN-B;
- no Camp On Busy can be started on the ACD group.
LOSYSOP126: DIVERTING USER ID AS CLI WHEN DIVERTING TO EXTERNAL
All: default=False
When a call is diverted to external over an ISDN or MFC trunk line, the number of the
diverting PBX extension user is used as CLI in the MFC call setup (instead of the CLI of the
original party) when this option is TRUE.
When this option is FALSE then the standard behaviour is in effect : the CLI indicates the
original calling party.
If this option is TRUE and the diverting party is assigned :
- FCM 46 (CLI permanently restricted), then still the diverting party along with the other
components are shown as the CLI.
- FCM 51 (COL permanently restricted), then the CLI only contains the 'Calling Subscriber
Category' followed by End of CLI .
In case of diversion to external via DPNSS, the value of LOBOUND 234 (General Calling
Subscriber Category) is included in the CLI.
Note that 'Calling Subscriber Category' and End of CLI are additional information for MFC
only.
NESYSOP127: REMOTE BREAKOUT ACCOUNTING
All: default=False
When this option is TRUE in both the gateway and originating PBX, then either at the end or
at the transfer of a remote breakout call, the call charging duration and destination digits are
transported from gateway PBX to originating PBX. Once the consistent information is
received in the originating PBX, the corresponding fields are replaced in the FDCR Accounting
Records of the originating PBX. Additionally, for all outgoing trunk calls, to provide an
indication of where breakout occurred, the destination digits are prefixed with the cluster ID
of the gateway PBX and route number of the outgoing trunk.
182
LOSYSOP128: SKIP JOURNALLING FOR INTRA-UNIT DESKSHARING
ACTIVATION/DEACTIVATIONS
All: default=False
The default value of this option is FALSE (journalling enabled).
This option can be set to TRUE to increase the performance of the intra-unit desksharing
moves. Then the system will not journal these moves.
The inter-unit desksharing moves are not affected by this option.
LOSYSOP129: SUPPRESS NAME-NUMBER RELATIONS BY DEFAULT IN RTRIEV

OUTPUT
All: default=False
This option defines the default behaviour of OM command RTRIEV.
When this option is TRUE, the name-number relations are NOT included in the retrieve file
when executed and omitting the parameter "retrieve-options" in OM command RTRIEV.
LOSYSOP130: ENABLE IP SERVICE ALARMS
All: default=True
This option specifies whether IP Service alarms are generated.
When a user wants to connect to Simple Alarming over IP and no Client Service Profile is
available for that user, the connection is refused. In that case an alarm is generated, when this
option is TRUE. When FALSE, no alarm is generated.
NESYSOP131: ENABLE BREAK-IN CIRCUITS IN REMOTE PM
All: default=False
This option specifies whether the Break-in Circuits (BICs) in a remote PM are enabled. New
functionality like Voice Logging and Silent Monitoring sometimes allocate BICs for a longer
period. This behaviour causes normal calls from/towards a remote PM (RPM) to meet
congestion, because all timeslots in the RPM link may be occupied by BICs. By default BICs in
a remote PMs are now disabled. In systems with low traffic it is possible to enable the BICs by
setting this system option. If the option is changed in a running system then the RPM requires
a restart to enable the BICs. BICs in remote PPU shelves are not disabled.
183
NESYSOP132: SYNCHRONISE TO ISDN DATE/TIME
All: default=False
When this option is TRUE and the general bundle option 'ISDN date/time synchronisation' is
set, the ISDN date/time indicated by the first next incoming or outgoing ISDN trunk call over
a line in this bundle (at regular intervals of 15 minutes) is used to synchronise the ISPBX date/
time.
When this option is FALSE, the date/time has to be set using OM command SEDATI.
LOSYSOP133: SOUND BUZZER FOR PARKED CALL IN W-QUEUE
All: default=False
When this option is TRUE, the call buzzer on a SuperVisor console is activated when the
operator parks the call in the W-queue; when this option is FALSE no call buzzer is activated.
LOSYSOP134: GENERATE ACCOUNTING RECORD FOR FREE-OF-CHARGE

CALL
All: default=False
This option specifies whether an accounting record is generated for a 'Free-Of-Charge' call.
When this option is TRUE, an accounting record is generated; when FALSE only a standard
record is generated for a 'Free-Of-Charge' call.
NESYSOP135: iTMP FREE PORT ALLOCATION
All: default=False
This option allows automatic allocation of a MAC address to a virtual PCT. When this option
is set to TRUE, an ErgoLine@Net terminal (with its related MAC address) is automatically
assigned to the next free virtual circuit.
NESYSOP136: TONE TO OPERATOR WHEN CALLER CLEARS
All: default=False
In case an extension calls the operator (answers) and the extension clears the call the operator
console is normally cleared and returns to idle. When this option is TRUE and the extension
clears the call the operator receives tone and the displayed information remains intact until the
operator clears. This enables to operator to note the extensions number/name.
NESYSOP137: DISPLAY ROUTE NUMBER OF PAGING TRUNK
All: default=False
184
This option specifies whether the route number of a paging trunk will be displayed when a
pager is called or when a paging call has fallen back to the operator (C-queue). When the
option is set to TRUE the route number will be displayed on the operator console. When the
option is set to FALSE nothing changes with respect to existing functionality.
NESYSOP138: PASS EXTERNAL CLI/COL IN CSTA TRANSFERRED EVENT
All: default=False
This option specifies whether the CLI/COL of the external party is passed in the CSTA-
transferred event. When this option is ON and the CLI/COL of the external party is available
then the CLI/COL of the external party is passed as a dialling number in the CSTA transferred
event; when OFF (default) the route and line number of the trunk line is passed in the CSTA
transferred event.
3.5. NETWORK TIMERS
This section gives a description and the value of all the network timers of an ISPBX system.
The timer values are given in seconds, unless it is stated otherwise.
NETIMER000: INTERNAL DIAL TONE TIME
All: (4 ... 10 Sec): 8 Sec

Define the dialling time out on dial tone (internal dial tone time).
This parameter defines the maximum time that internal dial tone is sent to a caller. The caller
has to start dialling within the defined time.
In case of expiry the caller receives busy or nu tone (depends on option 63).
NETIMER001: INTERDIGIT TIME
All: (4 ... 10 Sec): 8 Sec

Define the dialling time out between internal digits (interdigit time).
This parameter defines the maximum allowed dialling pause between digits when dialling an
internal number.
In case of expiry the caller will receive busy or nu tone (depends on option 63).
NETIMER002: EXTERNAL DIAL TONE TIME
All: (4 ... 10 Sec): 8 Sec
185
Define the dialling time out on public exchange dial tone (external dial tone time).
This parameter defines the maximum time that the public exchange dial tone is sent to a caller.
The caller should start dialling within the defined time.
In case of timer expiry the caller will receive busy or nu tone (depends on option 63).
NETIMER003: NUMBER MAY BE COMPLETE TIME
All: (3 ... 20 Sec): 4 Sec

Define the dialling time out between external digits to complete the number
This parameter defines the maximum pause between digits when dialling an external number
after the minimum number length has been reached.
In case of timer expiry the caller remains connected with the exchange line but digit senders
and receivers will be disconnected.
NETIMER004: POST DIALLING TIME
All: (4 ... 10 Sec): 8 Sec

Define the post dialling tone time.
This parameter defines the time for post-dialling in case a busy or congestion condition has
been encountered (this does not apply to operators).
NETIMER005: INTERNAL RING TONE TIME
All: (60 ... 180 Sec): 180 Sec

Define the internal ringing time or camp on busy time.
This parameter defines the maximum ringing time and camp on busy time of an internal call.
NETIMER006: TONE LIMIT TIME
All: (2 ... 1800 Sec): 8 Sec

Define the tone time limit.
With this parameter the maximum duration of tones (busy tone, number unobtainable tone,
congestion tone, confirmation tone) to an extension is defined.
186
NETIMER007: CALL FORWARDING TIME
All: (5 ... 60 Sec): 15 Sec

Define the call forwarding don't answer diversion time.
With this parameter the time is defined after which a call is diverted in case of a call to an
extension with the call forwarding don't answer facility.
NETIMER008: DELAYED HOTLINE TIME
All: (3 ... 8 Sec): 8 Sec

Define the hot line delay time.
With this parameter the time is defined after which the hot line connection is initiated in case
of extensions with the hot line after delay facility.
NETIMER009: DELTA ARB TIME
All: (300 ... 86400 Sec): 1800 Sec

(86400 seconds is 24 hours)
Define the ARB guarding time.
This parameter sets the maximum time an ARB call request remains valid. After the timer has
expired, the ARB call will be cancelled or not (option 72).
NETIMER010: EXTERNAL RING TONE TIME
All: (60 ... 240 Sec): 180 Sec

Define the external ring tone time.
This parameter defines the maximum time external ring tone is provided after the call is
extended by the operator/night service. This timer is not activated by calls which are incoming
via routes with an active 'assistance' mark. In this case the external ringtone is provided until
the call is answered by the called party or by the operator again.
NETIMER011: ARB RINGING TIME
All: (20 ... 60 Sec): 30 Sec

Define the ARB ringing time.
This parameter defines the maximum ringing time to the originator of an automatic ring back
call. In case of timer expiry the ARB call will be cancelled.
187
NETIMER012: NUMBER NOT COMPLETE TIME
All: (5 ... 16 Sec): 8 Sec

Define the dialling time out between external digits when number not complete (number not
complete time). This parameter defines the maximum pause allowed between digits when
dialling an external number before the minimum length of the external number has been
reached. In case of timer expiry the connection will be released and the caller receives busy
or nu tone (depends on option 63).
NETIMER013: SAS SILENT ALARM TIMER
All: (30 ... 1440 Min): 30 Min

If the timer expires, the alarm handler verifies if silent alarms of category "limited by time" have
to be moved to the minor queue.
NETIMER014: SAS INTERUNIT COMMUNICATION SCHEDULE TIME
All: (5 ... 5 Sec): 5 Sec

This timer is the scheduling timer of the SAS communication handler. Other timed SAS
communication handler activities are expressed as a multiple of this time (UBM parameters).
NETIMER015: CSG CHANGE SYNC REF TIME
Ccs4: (60 ... 999999 Min): 1440 Min

Ccss: (60 ... 999999 Min): 1440 Min
CSG change synchronization reference time. If the timer expires, an attempt is made to
synchronize the CSG (Clock Signal Generator) complex to another external synchronization
reference in order to check on a round robin base whether all external references are still
working properly. An external reference is in fact an entry on the Clock Reference Unit
(CRU). The CRU entry is a resource itself.
NETIMER016: SAS SL HANDLE LOOP GUARDING TIME
All: (1 ... 1 Min): 1 Min

Guarding time for loop guarding of SNL test.
Guarding time to close or open a loop in the other unit for SNL test.
NETIMER017: TRUNK OL PATH GUARD TIME
All: (30 ... 30 Sec): 30 Sec

This timer value is used in the pctip to guard the ol path of a trunk during the time it is mapped
188
to pctip.
NETIMER018: OMDM DELAY TIME
All: (5 ... 10 Sec): 10 Sec

Time to wait before retrying to load an overlay.
This timer controls how long the omdm delay process should wait before it retries to load an
overlay by sending the appropriate signal to the OMDM.
NETIMER019: DELAY TIME BEFORE ON HOLD BY OPERATOR
All: (2 ... 5 Sec): 5 Sec

After the operator answers an external call, this time interval will prohibit to set the concerned
party on hold (this is a French facility).
NETIMER020: PLUG REMOVED TIME
All: (5 ... 120 Sec): 30 Sec

Define the operator plug removed time.
This parameter defines the time the operator plug has to be removed before the operator
console is taken out of service.
NETIMER021: OPERATOR NOT ANSWERING TIME
All: (0 ... 16383 Sec): 16383 Sec

Define the operator absent time (not answering time).
This parameter defines the time after which the system takes the operator console out of
service in case the console is not attended. When used, then project between minimum and
maximum value. Default the null value is used.
NETIMER022: RETURN TO OPERATOR TIME
All: (10 ... 40 Sec): 25 Sec

Define the return to operator or night service time.
This parameter defines the time after which an assisted call is returned to the operator or night
service after it was extended to a busy or not answering extension.
189
NETIMER023: CANS HOOTING TIME OUT
All: (120 ... 300 Sec): 180 Sec

Define the CANS hooting time.
This parameter defines the maximum hooting time of the common answering night service.
The time, a "hooted" call can be answered, is determined by NETIMER031.
NETIMER024: CANS ON TIME
All: (1 ... 10 Sec): 1 Sec

Define the "hooter on" time.
With this parameter the "on" period of the CANS hooter cadence is defined.
NETIMER025: CANS OFF TIME
All: (1 ... 10 Sec): 4 Sec

Define the "hooter off" time.
With this parameter the "off" period of the CANS hooter cadence is defined.
NETIMER026: FAST CALL HANDLING TIME
All: (1 ... 5 Sec): 1 Sec

Define the fast call handling timer.
This parameter defines the time that the operator display information remains visible after a
call was extended according to the fast call handling procedure.
NETIMER027: NE RING TONE TIME
All: (60 ... 240 Sec): 180 Sec

Define the night facility ring tone time.
This parameter defines the time after which existing calls are cancelled in case the night service
does not answer. In case of expiry, the call is cleared.
NETIMER028: CFW INE SCNE TIME
All: (20 ... 60 Min): 16383 Min

Define the call forwarding (no answer) time from INE to SCNE.
190
This parameter defines the time after which a call to a not answering ringing individual night
extension is forwarded to the sub common night extension.
If no SCNE is assigned to the concerned route then the call will be forwarded to the MCNE
or CANS.
When used, then project between minimum and maximum value. Default the null value is
used.
NETIMER029: CFW SCNE TO MCNE TIME
All: (20 ... 60 Min): 16383 Min

Define the call forwarding (no answer) time from SCNE to MCNE.
This parameter defines the time after which a call to a not answering ringing sub common night
extension is forwarded to the main common night extension.
If the MCNE is absent then the call will be forwarded to the CANS (if present).
used.
NETIMER030: CFW MCNE TO CANS TIME
All: (20 ... 60 Min): 16383 Min

Define the call forwarding (no answer) time from MCNE to CANS.
This parameter defines the time after which a call to a not answering ringing main common
night extension is forwarded to the CANS.
If no CANS is applied then the MCNE remains ringing as long as defined by NETIMER027.
If the MCNE is switched absent then the call is immediately forwarded to the CANS.
used.
NETIMER031: CANS RELEASE TIME
All: (60 ... 240 Sec): 180 Sec

Define the CANS release time.
This parameter defines the time after which a call is to be cancelled from the night service
191
queue, after the call was transferred to the CANS. This timer overrules the general night
service release timer (NETIMER027) in this case. Notice that the CANS hooting time is
defined by NETIMER023.
NETIMER032: REROUTE TO OVERFLOW EXTENSION TIME
All: (30 ... 90 Sec): 90 Sec

Define the overflow extension wait time.
This parameter defines the time period after which an external incoming call is forwarded
from operator to the overflow extension. If this occurs, the operator is not warned (no flashing
led indication). Note that if option 107 (offer call to supervisor at first announcement) is false
and an announcement becomes active before the call is offered to the A-queue, the timer
starts at the moment the announcement starts.
When used, then project between minimum and maximum value. Else project the null value.
NETIMER033: CFW PLE TO OPERATOR TIME
All: (20 ... 60 Min): 16383 Min

Define the call forwarding (no answer) time from PLE to OP/(M)CNE. This parameter defines
the time after which a call to a not answering ringing permanent line extension will be
forwarded to the operator or (M)CNE. When used, then project between minimum and
maximum value. Default the null value is used.
NETIMER034: PERIODICALLY TICKER TONE TIME
All: (10 ... 10 Sec): 10 Sec

Defines within which time a busy night extension (periodically) should receive a ticker tone.
This parameter defines the interval time between two ticker tone bursts, given to a night
extension in case of an incoming call to a busy night extension.
NETIMER035: TMS SERVER GUARD TIME
All: (10 ... 30 Sec): 15 Sec

This parameter defines at what interval SSM (TMS Server) will check the queues for time-outs.
NETIMER036: MESSAGE WAITING TRIGGER TIME
All: (5 ... 10 Min): 5 Min

This parameter defines the interval time (divided by three) between two message waiting
192
softrings.
The default setting (5) results in message waiting softrings being generated every 3*5 = every
15 minutes.
NETIMER037: COB DISPLAY REFRESH TIME
All: (2 ... 3600 Sec): 10 Sec

Define the COB display refresh time.
If a SOPHO Business telephone starts COB on a busy extension the left display side is used to
display the place in the COB queue. This left display side (the place in the COB queue) will be
refreshed after a certain time. The COB display refresh time defines the interval between 2
COB display refreshments.
NETIMER038: OPERATOR CALL BUZZER REFRESH TIME
All: (1 ... 30 Sec): 5 Sec

Define the operator call buzzer refresh time.
The reactivating buzzer facility will be performed for calls which are waiting for assistance at
an operator position longer than a period.
The timer defines the interval between 2 call buzzer refreshments; It determines the delay of
the actual buzzer status.
Note: A lower value increases the loading, a higher value increases the delay.
NETIMER039: CHIEF OPERATOR ACTIVITY SCAN INTERVAL
All: (10 ... 60 Sec): 15 Sec

Define the chief operator activity scan interval.
This timer defines the interval between two display refreshments of the OM command
DIOPCT.
NETIMER040: DDI DIVERT TO OPERATOR TIME
All: (10 ... 40 Sec): 25 Sec

Define the divert to operator or night service time of DDI calls.
This parameter defines the time after which a DDI call to an extension is diverted to the
operator or night service. This option is only applicable in case the 'assistance' route mark is
assigned and this diversion is defined in the DDI route marks.
193
For announcement on incoming trunk, NETIMER 201 can be related to this timer. See the
description of NETIMER 201.
NETIMER041: DDI TONE TIME
All: (5 ... 360 Sec): 8 Sec

Define the tone time out on DDI calls.
This parameter defines the maximum duration of tones (not dial tones) to a DDI caller (e.g.
during release actions).
NETIMER042: DDI DIAL TONE TIME
All: (5 ... 50 Sec): 8 Sec

Define the maximum time dial tone is sent to a DDI caller.
This parameter defines the maximum time that dial tone is sent to a DDI caller. The caller has
to start dialling within the defined time.
NETIMER043: DDI INTERDIGIT TIME
All: (5 ... 20 Sec): 8 Sec

Define the DDI interdigit guarding time.
This parameter defines the maximum pause allowed between digits during DDI.
NETIMER044: MFC INTERDIGIT TIME
All: (5 ... 5 Sec): 5 Sec

Define the maximum interval between MFC-digits.
This timer determines the maximum interval between MFC-digits.
NETIMER045: SAS SEH PM TEST TIME
All: (150 ... 2300 Sec): 500 Sec

This timer is used when SAS is in normal mode. For SAS in installation mode see SAS-SEH PM
inst test time. On expiry of the timer the SAS-SEH will be triggered to start a new PM
timeswitch test. To aim for a test rate, so that all user channels are in theory tested once a
week, the following algorithm has to be used:
time= (seconds per week) / (128xnumber of PMs)
194
= 3600x24x7 / (128xnumber of PMs)
= 4725 / number of PMs
= 4725 / 10 (for the default value)
NETIMER046: SAS SEH SCU INST TEST TIME
All: (20 ... 200 Sec): 20 Sec

This timer is used when SAS is in installation mode. For SAS in normal mode see SAS-SEH
SCU/SNS test time. On expiry of the timer the SAS-SEH will be triggered to start a new SCU/
SNS timeswitch test. The test rate is chosen so that all user channels are tested as fast as
possible.
NETIMER047: SAS SEH PM INST TEST TIME
All: (20 ... 150 Sec): 20 Sec

This timer is used when SAS is in installation mode. For SAS in normal mode see SAS-SEH PM
test time. On expiry of the timer the SAS-SEH will be triggered to start a new PM timeswitch
test. The test rate is chosen so that all user channels are tested as fast as possible.
NETIMER048: SAS SEH SCU TEST TIME
All: (200 ... 1200 Sec): 400 Sec

This timer is used when SAS is in normal mode. For SAS in installation mode see SAS-SEH SCU
inst test time. On expiry of the timer the SAS-SEH will be triggered to start a new SCU
timeswitch test. To aim for a test rate, so that all user channels are in theory tested once a
week, the following algorithm has to be used:
time= (seconds per week) / (number of channels)
= 3600x24x7 / (8x32xnumber of SCUs)
= 2400 / number of SCUs
= 2400 / 6 (for the default value)
NETIMER049: DDO WAIT FOR ANSWER TIME
All: (60 ... 16383 Min): 16383 Min

Defines the time within which an answered signal has to be received from the opposite
exchange. When a trunk line (of which the outgoing bundle characteristic DDO wait for
answer=true) is seized, a timer (DDO wait for answer time) is started within which an
195
answered signal has to be received from the opposite exchange. On expiry of this timer the
DDO call will be released.
NETIMER050: CP PCT COMMAND GUARDING TIME
All: (3 ... 3 Sec): 3 Sec

This parameter is used to protect CP against hang up when the PPU is not answering in time
on a command in inner receive case.
NETIMER051: TEST BLOCKED TRUNK INTERVAL TIME
All: (5 ... 30 Min): 5 Min

Define the time between two tests of a trunk port which became blocked after the time out
occurred of the guard timer on detection of the external dial tone.
This parameter defines the time between two tests of trunk lines which are in ABL fail
condition and were blocked at the moment the guard time out on detection of the external
dial tone occurred. The blocked trunk lines will be tested one at a time on a low priority to
avoid extra load on the system.
NETIMER052: SEIZURE ACKNOWLEDGE GUARD TIME
All: (2 ... 5 Min): 2 Min

Define the time the test process, which is testing the trunks in blocked condition, will wait for
the seizure acknowledge of the trunk.
This parameter defines the time the test process for blocked trunk lines will wait for seizure
acknowledge of the trunk. If the seizure acknowledge guard time runs out the trunk line was
blocked by a line blocked signal and not by a time out of the guard timer on detection of the
external dial tone. The trunk will stay in "blocked" condition.
Note: In the PPU a guard timer is running on detection of seizure acknowledge. The seizure
acknowledge guard time must be bigger than this guard timer in the PPU.
NETIMER053: GROUP INFORMATION INTERVAL TIME
All: (2 ... 15 Sec): 5 Sec

Display information about a group on a SOPHO Business telephone at regular intervals.
NETIMER054: ACC SENDING ANSWER DELAY TIME
All: (1 ... 10 Sec): 3 Sec
196
The timer is only used for the MFC facility answering circuit dialled. It is delay time needed
between the ending of sending of the last backward MFC signal the R2 mode and the sending
of the answering over the involved trunk line.
NETIMER055: ACC ACTIVATION DELAY TIME
All: (1 ... 10 Sec): 2 Sec

The timer is used for the MFC facility answering circuit dialled. It is delay time needed between
the sending of sending of the answer signal over the trunk line and the sending of the MFC
answer signal. The timer is also used as delay time, after signal is sent to PPH/PMC to make
or break the PM path.
NETIMER056: LOS SYSDUMP SCAN TIME
All: (1 ... 30 Min): 3 Min

This timer has a twofold use:
- It defines the time to be measured before automatic writing of system dumps starts upon
performing an operational start.
- It defines the time to be measured before a retry is performed for writing system dumps
that became locked, due to e.g. device errors, no space on backup device, etc.
NETIMER058: KEYTONE AFTER ANSWER TIME
All: (1 ... 10 Sec): 2 Sec

Time between answering and connecting a RKT-SDT.
This timer is used for trunks (ATUs) with signalling type "keytone after answer". On an
incoming seizure the trunk is answered and this timer is started. On expiry of this timer a RKT-
SDT is connected to the trunk.
NETIMER059: LEDS TEST TIME
All: (3 ... 5 Sec): 4 Sec

Time for switching a group of leds during the test of an operator position.
Checking leds and displays of an operator position is a facility implemented for France. It can
be initiated by pressing C button, as the position is in maintenance and microphone plug
removed. Leds are split in 5 groups, each group is switched on after expiring of this timer.
197
NETIMER060: TEST TRANSITION TIME
All: (1 ... 5 Sec): 3 Sec

Minimum time before an operator can restart leds checking, after the test has been stopped.
After an end request of the leds checking test, restarting the test is forbidden for the duration
of this timer. This timer has been implemented in order to prevent an excessive sending of
signals to PPU, by a continuous pressing of C and E keys (start ... stop ... start ... stop).
NETIMER061: PAGING WAIT FOR ANSWER TIME
All: (30 ... 240 Sec): 180 Sec

Defines the time within which a call to paging has to be answered.
When meet me paging (virtual or real) is done then a timer is started within which the call
should be answered. If no answering is done the caller is released.
NETIMER062: PAGING RETURN TO OPERATOR TIME
All: (10 ... 40 Sec): 30 Sec

Defines the return to operator or night extension time in case of paging.
This parameter defines the time after which a call to paging equipment is returned to the
operator or night extension in case the call is not answered by the paged person.
NETIMER063: SAS DTU OWNERSHIP RETRY TIME
All: (10 ... 60 Sec): 30 Sec

Defines the time between two attempts to gain the ownership of a DTU in case it is already
owned by an other process.
NETIMER064: SAS DTU ALARM INTEGRATION TIME
All: (9 ... 30 Sec): 10 Sec

Defines the time during which the DTU alarms in the PPU are integrated before the alarms
are read by the CPU.
NETIMER065: SAS DTU GUARD TIME
All: (2 ... 60 Sec): 30 Sec

Defines the time in which the CPU must receive a reply from the PPU after sending a
command to the DTU (via the PMCP).
198
NETIMER066: SAS SHORT ROLLBACK TIMER
All: (1 ... 1 Sec): 1 Sec

Timer used after rollback events before first check if resource is free.
If it is necessary to rollback a resource and the resource is not free, the rollback function sends
rollback events to the process controlling the resource, waits for a time determines by the SAS
short rollback timer and then starts checking at intervals determined by the claim check delay
time if the resource is free. Generally the resource does not become free immediately but
rather quickly and this timer increases the chance that the resource is found to be free on the
first check.
NETIMER067: HOTSTART PHASE2 GUARD TIME
All: (5 ... 5 Min): 5 Min

Guarding of hotstart phase 2 length.
Hotstart phase 2 ends upon a message of the pm-manager given when all PMs are ready with
hotstart. When this message is given the hotstart continues with phase 3. When the message
is not given hotstart phase 3 is started upon this timer.
NETIMER068: PM HOTSTART GUARDING TIME
All: (120 ... 300 Sec): 120 Sec

Interval in which a state transition of a hotstarting PM has to take place.
NETIMER069: HOTSTART RESOURCE TRANSITION SHORT TIME
All: (3 ... 3 Sec): 3 Sec

Ccs4: (1 ... 1 Sec): 1 Sec
Wait time between processing a number of PCTs.
Time HSP will wait after taking action on a number of PCTs in hotstart phase 3 to prevent
overload on status transitions.
NETIMER070: HOTSTART RESOURCE TRANSITION LONG TIME
All: (120 ... 120 Sec): 120 Sec

Wait time between processing PMs and boards.
Time HSP will wait after taking action on PMs and after processing boards in hotstart phase 3
to prevent status transitions sequence problems (insure that PMs and boards are INS before
199
processing PCTs).
NETIMER071: SNR PATH CONGESTION RETRY TIME
All: (1 ... 10 Sec): 5 Sec

Time after which an SNR resource activation is tried again.
NETIMER072: PCT SHORT TRANSITION GUARDING TIME
All: (3 ... 15 Sec): 15 Sec

Time interval in which a short transition of the hardware status of a PCT, such as to birth state,
has to be completed.
NETIMER073: PM WARMSTART TIME
All: (120 ... 120 Sec): 120 Sec

Ccs4: (15 ... 15 Min): 15 Min
Time used to determine the end of a warmstart.
CPU3000
Estimated time for one PM and successors to warmstart. The total duration of a warmstart is
determined by the number of PMs multiplied by this parameter value.
CCS
Estimated time for all PMs to finish the warmstart.
NETIMER074: POM CRS BLOCK RETURN PROCESSING TIME
All: (5 ... 5 Sec): 5 Sec

Time after which an incoming block return is processed by the POM call recording service.
NETIMER075: ILC LOAD CONTROL TIME
Ccss: (3 ... 3 Sec): 3 Sec

Ccs4: (1 ... 1 Sec): 1 Sec
Delay time to control the load that is caused by ILC correct events that are sent to the
opposite unit. Before such an event is sent on an ABL nu to ABL fail transition for ILCs, a delay
timer is started. The timer value (together with the maximum number of concurrent ILC
transitions and the maximum number of units) determines the maximum number of ILC
correct events that are sent to a unit per time-interval.
200
NETIMER076: CPC GENERAL NULL TIME
All: (0 ... 0 Sec): 0 Sec

This parameter is used in MCS to get control back after a SOC or POC has been sent. A timer
is started with 0 seconds time to inject a time out in sys current piv immediate after the last
SOC or POC has been sent.
NETIMER077: PFH INTERUNIT COMMUNICATION GUARD TIME
All: (3 ... 10 Sec): 5 Sec

This parameter is used to protect the multi unit software against hang up when
communication is lost.
Note: This timer should always be 1 second higher than the DPNSS (NETIMER 84) and QSIG
(NETIMER 222) communication guard time.
NETIMER078: PFH NIGHT TRAFFIC INTERVAL TIME
All: (11 ... 11 Sec): 11 Sec

This parameter is used to make rerouting attempts on a periodical time base.
NETIMER079: SAS SHORT DELAY TIME
All: (3 ... 3 Sec): 3 Sec

This parameter is used as a general timer to delay some action.
NETIMER080: EXTERNAL DIAL TONE DET TIME
All: (5 ... 60 Sec): 40 Sec

Define the external dial tone detection time.
This parameter defines the maximum time the exchange waits for reception of external dial
tone in case of dialling out. In case of time out the call is aborted.
NETIMER081: EXTERNAL DIAL TONE PRE DET TIME
All: (1 ... 180 Sec): 1 Sec

Define the pre (external) dial tone detection time.
This parameter defines the time to elapse before the external dial tone receiver is connected.
The timer is activated only if concerned bundle mark is true.
201
NETIMER082: DPNSS DASS PROTOCOL GUARDING TIME
All: (120 ... 65767 Sec): 300 Sec

Define the guarding time out for the DPNSS protocol in the call setup phase.
This timer guards the DPNSS protocol in the call setup phase for every call. On expiration of
the timer, the DPNSS line and all other resources will be released.
NETIMER083: DPNSS DASS RELEASE SYNCHRONISATION TIME
All: (4 ... 60 Sec): 20 Sec

Define the DPNSS/DASS release synchronisation timer to guard the release of a busy DPNSS
line. After receipt of an unknown DPNSS/DASS message in idle, this timer is started to guard
the synchronisation for this line. On expiration of the timer the line is booked free again.
NETIMER084: DPNSS COMMUNICATION GUARDING TIME
All: (2 ... 9 Sec): 4 Sec

Timer used to guard inner receive case.
This timer is used when an inner receive case is used for DPNSS communication with another
ISPBX.
Note: This timer should always be 1 second lower than the PFH interunit communication guard
time (NETIMER 77).
If the timer value is higher than the default value, it should be checked that it is lower than
the value of the "PABX communication timer" in the SSV60 application.
NETIMER085: TRAFFIC MEASUREMENT EXTENSION SCAN TIME
All: (10 ... 16383 Sec): 30 Sec

The time between the switch count scans performed by the Extension Service.
To determine the Erlang value of extensions and groups Extension Service performs at
intervals defined by this timer switch count scans.
NETIMER086: TRAFFIC MEASUREMENT TRUNK SCAN TIME
All: (10 ... 16383 Sec): 30 Sec

The time between the switch count scans performed by the Trunk Service.
To determine the Erlang value of trunk and interunit bundles Trunk Service performs at
intervals defined by this timer switch count scans.
202
NETIMER087: TRAFFIC MEASUREMENT PAGING SCAN TIME
All: (10 ... 16383 Sec): 30 Sec

The time between the switch count scans performed by the Paging Service.
To determine the Erlang value of paging routes Paging Service performs at intervals defined by
this timer switch count scans.
NETIMER088: TRAFFIC MEASUREMENT OPERATOR SCAN TIME
All: (1 ... 16383 Sec): 10 Sec

The time between the switch count scans performed by the Operator Service. To determine
the Erlang value of operator/operator queues Operator Service performs at intervals defined
by this timer switch count scans.
NETIMER089: TRAFFIC MEASUREMENT AUXILIARY SCAN TIME
All: (1 ... 16383 Sec): 5 Sec

The time between the switch count scans performed by the Auxiliary Service. To determine
the Erlang value of auxiliary resources and convertors Auxiliary Service performs at intervals
defined by this timer switch count scans.
NETIMER090: TRAFFIC MEASUREMENT CALL SCAN TIME
All: (10 ... 16383 Sec): 30 Sec

The time between the switch count scans performed by the Call Duration Timing Service. To
determine the average call length the Call Duration Timing Service performs at intervals
defined by this timer switch count scans.
NETIMER091: TRANSFER PROHIBIT TIME
All: (0 ... 60 Sec): 0 Sec

The transfer prohibit timer is used for trunks in the direct dialling out call, while the trunk does
not provide the answer signal. Before expiring of the timer, the trunk cannot be transferred.
If the timer is projected to zero (default), no prohibition occurs.
NETIMER092: TMS DOWNLOAD GUARDING TIME
All: (5 ... 40 Sec): 20 Sec

This timer guards a TFM download session. If this timer expires, it is assumed that the TFM
session is killed. The value is depending on the response time of the SSM (TMS).
203
NETIMER093: DDI DATA CALL RINGING TIME
All: (10 ... 16383 Sec): 30 Sec

Define the divert to operator or night service time of DDI data calls. This parameter defines
the time after which a DDI data call to an extension is diverted to the operator or night service.
NETIMER094: SOCOTEL PROCEED TO SEND GUARDING TIME
All: (2 ... 40 Sec): 5 Sec

Define the guarding time between outgoing seizure on a SOCOTEL trunk and the first
backward reply from the opposite exchange. After seizure of the outgoing trunk with
SOCOTEL signalling, an RS-SOCOTEL is started. The timer guards the call, while the opposite
exchange starts a RS-SOCOTEL to send the first backward signal. In case of expiry, the trunk
is forward released. The default is the specified value for France.
NETIMER095: SOCOTEL INTERDIGIT GUARDING TIME
All: (4 ... 20 Sec): 15 Sec

Define the dialling time out between SOCOTEL digits (interdigit time).
This parameter defines the maximum allowed dialling pause between digits when indialling
with SOCOTEL. In case of expiry, the call is completed depending on the DDI options of the
trunk. The default is the specified value for France.
NETIMER096: SAS ESU GUARD TIME
All: (1 ... 15 Min): 15 Min

Define the ESU guarding time.
This parameter defines the time that the external lines must remain directly connected to the
extensions, after the failures have disappeared. After expiry, the external lines are switched
over to the line interface circuits.
NETIMER097: SAS AH REMOTE ALARM CONFIRMATION TIME
All: (30 ... 60 Min): 30 Min

Define the time in which a remote alarm should be confirmed.
This parameter defines the time in which an alarm level change sent to Signalling At Distance
(SAD) must be confirmed by the system engineer. Upon expiry of the timer the alarms will be
rerouted because it must be assumed that they did not arrive.
204
NETIMER098: PAGING REPEAT TIME
All: (10 ... 16383 Sec): 30 Sec

Define the interval for a repeated seizure of a paging line.
This parameter defines the interval between two calls to the paging equipment for a meet me
paging call as long as it is not answered.
NETIMER099: ANNOUNCEMENT ANSWER DELAY TIME
All: (0 ... 60 Sec): 5 Sec

This parameter determines the time before a voice announcement message is given to an
incoming trunk to which announcement is projected.
When announcement for 'DDI successful calls' is projected to a trunk and the trunk has dialled:
- an idle extension or
- a (non ACD) group with at least one idle extension or
- meet me paging, when no other party is already paging for the same destination or
- speech paging, when no other party is already paging for the same destination and paging
equipment is found,
then timer 201 is used in stead of timer 99 when system option 39 is true.
NETIMER100: SYS CONGESTION TIME
All: (30 ... 30 Sec): 30 Sec

Generally used timer.
When a process instance meets congestion, it will in general delays for "sys congestion time"
seconds, between successive attempts to continue.
NETIMER101: ANNOUNCEMENT REPEAT TIME
All: (1 ... 60 Sec): 10 Sec

This parameter determines the time between two voice announcements given to an incoming
trunk to which announcement is projected.
NETIMER102: OPERATOR B LED REFRESH TIME
All: (0 ... 999999 Sec): 5 Sec

Define the operator B led refresh time.
205
An operator B-led is lit, when the allocated route(s) do(es) not have idle trunks. The timer
defines the interval between 2 B led refreshments. Together with the number of B-buttons, it
determines the delay of the actual route status, known in the trunk service and the displayed
status on the operator console(s).
Note: A lower value increases the loading, a higher value increases the delay.
NETIMER103: OPERATOR UNIT CALL HANDLING REFRESH TIME
All: (30 ... 300 Sec): 30 Sec

Define the operator unit call handling refresh time.
This timer defines the interval between 2 checks on assistance of units delivering assistance to
the local area. Together with the number of units in the local area it determines the delay in
actual status of the local area in the operator service.
NETIMER104: POM TT GLC CONGESTION TIME
All: (1 ... 1 Sec): 1 Sec

Timer is started when load control monitors too much load for the system. The TT process
is suspended until the timer expires. Then again load control is asked if the load is not too high.
If it is too high the timer is started again.
NETIMER105: OPERATOR CONGESTION TIME
All: (30 ... 60 Sec): 30 Sec

Defines the operator hunting time for a free trunk when in case of operator DDO congestion
occurred.
This parameter defines the time during which retries are done to find a free trunk in case of a
DDO call. The timer is started when during an operator DDO call no free trunks are available.
This timer is also used for the ATF-COB facility (a facility only available for extensions). During
this time the ATF-COB facility is searching for a free trunk line for the extension which
selected the (busy) trunk route.
NETIMER106: ARB TIME OUT CHECK TIME
All: (2 ... 2 Min): 2 Min

Define the time between two checks on timed out ARB-cases.
This parameter defines the time between two checks on ARB-cases older than the delta ARB
time.
206
NETIMER107: CALL WAITING TICKER TIME
All: (2 ... 2 Sec): 2 Sec

Defines the duration of the call waiting tone burst.
This parameter defines the time a call waiting tone burst should be given to a party involved
in a break in situation or call waiting situation (e.g. camped on extension).
NETIMER108: IDLE TIME JOB TIME
All: (1 ... 1 Sec): 1 Sec

Generally used timer.
When a process instance needs a job to be performed at idle time, it will in general delay for
"sys idle time job time" seconds, between successive jobs.
NETIMER109: CP COMM HANDLER GUARD TIME
All: (5 ... 30 Sec): 10 Sec

The timer determines after what time no reply from the opposite unit is to be expected
anymore:
- A reject is to be send to the requesting process or;

- Another restart command is sent (in case of unit communication reestablishing).
NETIMER110: POM LOCK RETRY TIME
All: (1 ... 3 Sec): 2 Sec

Time to wait before retrying to set a lock.
This timer controls how long the lock handler should wait before it retries to set the unit lock
in a certain unit.
NETIMER111: POM CONGESTION TIME
All: (3 ... 3 Sec): 3 Sec

Controls waiting time after congestion message.
This timer controls how long the command interpreter should wait before re-executing an
OM command that has returned the result congestion.
207
NETIMER112: POM REPEAT EXECUTION TIME
All: (1 ... 1 Sec): 1 Sec

Controls the time between two executions of an execution routine.
This timer controls how long the command scheduler should wait before the execution
routine of an OM command is called again. This execution routine is only called again if it has
returned one of the results: output continuously, new output or output no change.
NETIMER113: POM CI COMMAND TIME
All: (5 ... 30 Min): 10 Min

Guarding time for terminal input. This timer guards the input from the OM terminal. If within
this time no input (new command) is given at the OM terminal the command interpreter
cancels the OM session (only for non-coded sessions).
NETIMER114: POM SHORT TIME
All: (0 ... 0 Sec): 0 Sec

Timer to be able to execute a receive case.
This timer is used by the command interpreter to send it to itself Then, it executes an inner
receive case to be able to check whether a certain file management signal is queued for the
CI. Note that this timer must always be zero.
NETIMER115: HELLO PM TIME
All: (60 ... 60 Sec): 60 Sec

Time interval between two hello messages to PM.
NETIMER116: HELLO PM RESPONSE TIME
All: (60 ... 60 Sec): 60 Sec

Time interval in which PM has to answer on "hello PM" message.
With the "hello PM" message the proper functioning of the PM is checked. The PM has to give
answer before the hello PM time has passed.
NETIMER117: PM TRANSITION GUARDING TIME
All: (120 ... 120 Sec): 120 Sec

Interval in which a state transition of the PM has to take place.
208
NETIMER118: HELLO SN TIME
All: (5 ... 5 Sec): 5 Sec

The hello sn time is the interval-time in the switching network interface process for sending a
hello sn message to the next active SCU (the hello-messages are sent one by one to all active
SCUs in a cyclic order). Per SCU the maximum time between two messages is 100 seconds
(firmware limitation).
NETIMER119: SN RESPONSE TIME
All: (2 ... 30 Sec): 5 Sec

The SN response time is the guarding time in the switching network interface process for
receiving a reply message from the SN after sending a command-message to this SN.
NETIMER120: SAS DTU-CC TEST TIME
All: (10 ... 10 Sec): 10 Sec

Guarding and delay time during DTU-CC test action.
NETIMER121: CMP CLEAR GUARDING TIME
All: (10 ... 10 Sec): 10 Sec

This timer is used for the guarding of the CMP clear protocol.
NETIMER122: ATM SYNCHRONIZATION TIME
All: (1 ... 1 Min): 1 Min

Time is in minutes and not in seconds.
The ATM-synchronization-time is the interval time for tuning the system time clock in the LOS
with respect to the (more accurate) system time clock in the SNS or CSGs. It is also the
interval time for updating the absolute time on the operator desk.
NETIMER123: POM TOM QUARTER HOUR INTERVAL
All: (900 ... 900 Sec): 900 Sec

Timer value for traffic measurement (900 seconds; not 15 minutes because of accuracy
reasons). Interval is the time interval at which service counters will be gathered by the traffic
observation manager.
209
NETIMER124: SAS SNC CONGESTION TIME
All: (5 ... 5 Sec): 5 Sec

Timer used in the AVM operations.
Between successive attempts by SAS to reserve a snc general it delays for "SAS SNC
congestion time" seconds.
NETIMER125: SAS PATS SCHEDULE TIME
All: (30 ... 30 Sec): 30 Sec

Trigger for the PATS process to perform its action.
From this timer value the PATS will derive the total amount of stimuli to be generated for
preventive testing of a resource type.
NETIMER126: CONVERTOR NOT ANSWERING TIME
All: (10 ... 120 Sec): 120 Sec

Defines within which time a convertor should receive an answer acknowledge.
This parameter defines within what time (after through connection of a data call, in which a
convertor is involved) the convertor should receive an answer acknowledge from the opposite
party.
NETIMER127: CM LOAD SENSING TIME
All: (3 ... 3 Sec): 3 Sec

Timer used in the CM load control sensor.
Every "CM load control sensing time" seconds the CM load control sensor checks the
occupancy of the CB, stack, EPD and signal packets pools, and hereby controls the accepting
of new calls.
NETIMER128: CLAIM CHECK DELAY TIME
All: (5 ... 5 Sec): 5 Sec

Timer used in the AVM operations. Between successive take claimed resource attempts by
SAS in general it delays for "claim check delay time" seconds.
See also boundaries 106, 107 and 110.
210
NETIMER129: SAS SCHEDULE TIME
All: (2 ... 10 Sec): 2 Sec

Trigger for the SAS controller to perform action. The SAS-CTRL will invoke the scheduling
function, to initiate a SAS Action Process Instance if required, at intervals of "SAS schedule time
seconds".
NETIMER130: SAS POSTPONED RECOVERY TIME
All: (100 ... 43200 Sec): 14400 Sec

Trigger for the SAS postponed recovery process to perform action.
This SAS process will invoke recovery attempts for resource alarmed at a specific alarm level.
Therefore the total cycles for postponed recovery will elapse 3 times this value (for major,
minor and silent alarm level).
43200 seconds equals 720 minutes or 12 hours.
NETIMER131: DIAL TONE INTERVAL TIME
All: (2 ... 5 Sec): 2 Sec

This parameter defines the time between the first time and the second time dial tone is given
in case of a delayed hot line with post dialling and a trunk as hot line destination. This timer is
introduced in order to indicate to the delayed hot line initiator that the delayed hot line time
is expired and post dialling can be started.
NETIMER133: CSG RESPONSE TIME
All: (2 ... 5 Sec): 5 Sec

Time interval for in which a response of the CSG or SNS is expected.
NETIMER134: REQUEUE ATTEMPT TIME
All: (60 ... 600 Sec): 60 Sec

This timer initiates a queueing attempt for taxmetering results at the initiating operator unit
while that unit is not accessible.
NETIMER135: SAS PCT TEST TIME
All: (30 ... 60 Sec): 30 Sec

Overall timer used in the PCT test.
211
This timer has to prevent possible hangup of the PCT test in cases, where no reply has been
received on a previously given command. On expiry of the timer the test is aborted with result
"fail".
NETIMER136: DDI DIAL TONE DELAY TIME
All: (1 ... 10 Sec): 3 Sec

The timer can avoid the loss of digits, when resources in the opposite exchange are not ready,
while the outgoing seizure is already received (as incoming seizure) in the ISPBX. After timer
expiring, the dial tone is started.
NETIMER137: SAS BAPT DISPLAY TIME
All: (3 ... 3 Sec): 3 Sec

Time interval used in the BAPT process.
After a command has been given on the terminal, the BAPT process will wait "SAS BAPT
display time" seconds, to receive the resulting events from the PCTs, before a prompt is
echoed on the terminal. On a time-out BAPT switches from display mode to command input
mode.
NETIMER138: EMERGENCY EXTENSION RING BACK TIME
All: (5 ... 30 Sec): 15 Sec

Define the emergency extension ring back time.
This parameter defines the maximum ringing time to the a caller of the emergency extension
in case that party has to be rung back. There are three cases when an extension is rung back
by the emergency extension:
- The caller released while talking to the emergency extension.

- The caller released while the emergency extension was ringing. After answering by the
emergency extension the caller will be rung back.
- The emergency extension was busy. ARB is started automatically.
As soon the emergency extension is free he will be rung. Upon answering the caller will
be rung.
NETIMER139: HELLO CIU TIME
All: (30 ... 30 Sec): 30 Sec

Timer used in the CM CIU handshake.
212
Every "hello CIU time" seconds the CM sends a "hello" command to the CIU/CIE/BIM. For a
CCS system, this is the handshake between CPU and CIE/BIM
NETIMER140: CIU RESPONSE TIME
All: (7 ... 7 Sec): 7 Sec

Time interval in which a response of the BIM is expected.
NETIMER141: TSW TEST TRANSMITTER TIME
All: (2 ... 5 Sec): 2 Sec

Timer used in the programming TSW test transmitter/receiver.
This timer has to prevent possible hangup of the test in cases, where no reply has been
"fail".
NETIMER142: RRM SCHEDULE TIME
All: (1 ... 10 Sec): 2 Sec

RRM must call load control when starting transition for successor.
If rejected it cannot send a signal to itself but it must start a timer.
NETIMER143: CIU RESET TIME
Cps: (3 ... 5 Sec): 3 Sec

Time interval reserved for CIU hardware resetting.
After the reset command (high address resetting) the CM has to wait "CIU reset time" seconds
before the first "hello command" may be sent. The value has to be greater than the time
required by the CIU to become operational.
NETIMER144: SNR RELEASE PATH TIME
All: (15 ... 15 Min): 15 Min

This timer determines the time a PM-SN path remains occupied after deactivating an SN-tone-
resource.
NETIMER145: SAS PM TONE SOURCE TEST TIME
All: (60 ... 60 Sec): 60 Sec

Overall timer used in the PM tone-source-test.
213
This timer has to prevent possible hangup of the test in cases, where no reply has been
"fail".
NETIMER146: GENERAL TRANSITION GUARD TIME
All: (45 ... 90 Sec): 60 Sec

Time interval in which a transition of the hardware status has to be completed.
NETIMER147: CALL LOGGING DELAY TIME
All: (10 ... 10 Sec): 10 Sec

Time to wait before logging callers base.
This parameter defines the time that an incoming call has to wait before this call is logged in
the callers base of the SOPHO Business telephone. This parameter is only relevant when the
call is received on a line position or executive line position of the SOPHO Business telephone
and is withdrawn by the initiator.
NETIMER148: SAS PM TEST TIME
All: (30 ... 30 Sec): 30 Sec

Timer used for PM testing.
This timer is started after the test command for testing the PM timeswitch has been sent to
the PM. Before the timer expires an event has to be received from the PM, containing the test
result. If not, the test is aborted.
NETIMER149: POM LONG CONGESTION TIME
All: (5 ... 5 Sec): 5 Sec

Controls waiting time after congestion message.
NETIMER150: LOS GLC MONITOR TIME
All: (1 ... 1 Min): 1 Min

The timer is minutes and not in seconds.
Timer required for the load control monitor to reschedule itself
Via OM commands you can start the load control monitor. It is a static process that keeps
running on its own until you cancel it. It requires a timer to reschedule itself in each monitor
interval.
214
NETIMER151: SAS CONGESTION TIME
All: (30 ... 30 Sec): 30 Sec

This parameter defines the time interval on which the global status of the remote alarming
device will be inspected.
NETIMER152: WAIT FOR DOWNLOAD ACK TIME
All: (120 ... 120 Sec): 120 Sec

This system timer defines how long the CPU waits for a response of a download command.
NETIMER153: WAIT FOR DELETE ACK TIME
All: (90 ... 90 Sec): 90 Sec

This system timer defines how long the CPU waits for a response of a delete command.
NETIMER154: DOWNLOAD RETRY TIME
All: (10 ... 10 Sec): 10 Sec

This system timer is used by the download process to retry to restart a download action after
congestion is met.
NETIMER155: ISDN OVERLAP RECEIVING GUARD TIME
All: (10 ... 16383 Sec): 15 Sec

Define the time to wait for an INFORMATION message after a SETUP-ACK message has
been sent or the time to wait between two INFORMATION messages.
This parameter defines the pause between a SETUP-ACK and an INFORMATION message
and between two INFORMATION messages. On expiry the call is released with a
DISCONNECT message or DDI fail is executed.
NETIMER156: WAIT FOR INSERTION OF AUTHORIZATION CODE TIME
All: (0 ... 16 Sec): 4 Sec

This timer is used with Mercury Smartbox Emulation and defines the time the system will wait
for the BT network to occupy a line to the MCL network.
NETIMER157: CSG CHANGE REFERENCE POINT TIME
Cpu3000: (10 ... 30 Sec): 15 Sec

Define the time after which the clock reference point will be changed.
215
When a DTU becomes free of transmission errors, this timer will be started. On expiry of this
timer an attempt is made to synchronize the internal clock to the CRU-entry connected to this
DTU.
Note: This is only done if the ranknumber of this CRU-entry is lower than the rank-number of the
CRU-entry currently used to synchronize the internal clock to.
NETIMER158: RECALL RINGING TIME
All: (20 ... 40 Sec): 30 Sec

This parameter defines the maximum ringing time to the originator of a recall. In case of timer
expiry the recall will be cancelled.
NETIMER159: DDI CALLING PARTY CONTROL TIME
All: (10 ... 120 Sec): 30 Sec

Define the maximum re-answer time for extensions in a DDI call with calling party control.
This parameter defines the maximum time in which an extension may re-answer a DDI call
with MFC-CSS1 signalling after going on hook (restoration mode is calling party control). In
case the timer expires, the backward release protocol is started.
NETIMER160: DDO CALLING PARTY CONTROL TIME
All: (10 ... 180 Sec): 90 Sec

Define the maximum re-answer time for trunks in a DDO call with calling party control. This
parameter defines the maximum time in which a trunk may re-answer a DDO call with MFC-
CSS1 signalling after going "on hook" (restoration mode is calling party control). In case the
timer expires, the forward release protocol is started and the caller is given busy tone.
NETIMER161: DDO CALLED PARTY CONTROL TIME
All: (10 ... 65535 Min): 65535 Min

Define the maximum re-answer time for extensions in a DDO call with called party control.
This parameter defines the maximum time in which an extension may re-answer a DDO call
with MFC-CSS1 signalling after going on hook (restoration mode is called party control). In
case the timer expires, the forward release protocol is started and the caller freed.
NETIMER162: ACD GROUP SCAN TIME
All: (5 ... 60 Sec): 15 Sec

This timer defines the switch count rate (performed within extension service) for ACD group.
This switch-counting is done for DIGRPS.
216
NETIMER163: TRUNK SEIZURE ACKNOWLEDGE GUARDING TIME
All: (10 ... 10 Sec): 10 Sec

Define the guarding time between outgoing seizure on a MFC trunk and the seizure
acknowledge. In case of expiry, the trunk is forward released.
NETIMER164: DASS COMMUNICATION GUARDING TIME
All: (1 ... 10 Sec): 4 Sec

This timer is used to guard e.g. a call charge information request to the public exchange.
NETIMER165: POM DTAP INFORM GUARD TIME
All: (30 ... 40 Sec): 30 Sec

Define POM DTAP information guard time. The timer determines after what time no reply
from File Interface Process is expected anymore.
NETIMER166: SYS INW FLOW ESTABLISH GUARDING TIME
All: (180 ... 300 Sec): 180 Sec

This timer is used by the application processes (e.g. interface processes), for guarding the flow
establishment of the INW layer, as it must be established by the LOS.
NETIMER167: OM BOARD AND PCT COMMANDS GUARDING TIMER
All: (120 ... 120 Sec): 120 Sec

Guard the time between a command sent from OM to a board or PCT and the corresponding
reply event.
When via OM a board or PCT is assigned or deleted, a command is sent to that board or PCT
and the reply event is awaited. If no reply would be sent (hardware not operational), OM
would wait forever. This timer value is used to guard this situation.
NETIMER168: HOTSTART AFTER LOAD DELAY TIME
All: (60 ... 60 Sec): 60 Sec

This timer defines the time between subcommand S81110 (ACTUPD) completes and the
activation of the reload by the LOS.
NETIMER171: PM WAIT FOR THE FIRST RESOURCE TRANSITION
All: (10 ... 10 Min): 10 Min
217
This timer defines the time the download process waits before the first resource reports itself
as downloadable.
NETIMER172: PM WAIT FOR THE NEXT RESOURCE TRANSITION
All: (90 ... 90 Sec): 90 Sec

This timer defines the maximum time the download process waits between two resources
that reports themselves as downloadable.
NETIMER174: ACD WAIT BEFORE REPEAT PROCESSING
All: (1 ... 5 Sec): 5 Sec

The ACD wait before repeat processing specifies the time after which the processing of the
ACD message repeat queue is initiated or continued.
NETIMER175: CHARGING DISPLAY REFRESH TIME
All: (5 ... 16383 Sec): 10 Sec

The charging display refresh time specifies the time after which new Advice Of Charge
information will be displayed during a call with a trunk with metering.
NETIMER176: PM LINK CLOSED DURING RESET TIME
All: (10 ... 10 Sec): 10 Sec

The interval in which the reset (switch from flash to boot PROM) of the PMC has to take place.
At the start of this interval the link will be closed and at the end of this interval the link will be
reopened.
NETIMER177: CLOSE LINK DELAY TIME
All: (2 ... 2 Sec): 2 Sec

Delay before the actual close link command is executed. In CPU3000 this delay is required
because otherwise signals send to a destination before the close link is executed will never
arrive at that destination.
NETIMER178: ARB FREE NOTIFICATION DELAY TIME
All: (0 ... 10 Sec): 3 Sec

Delay time between an ARB destination becomes free and notifying the free status to the
initiator.
218
NETIMER179: ARB CALL SETUP GUARDING TIME
All: (30 ... 70 Sec): 40 Sec

This timer defines the interval in which a call setup must be received after an idle free
notification reply is received at the destination side. The value should be set at least 10 seconds
higher than the value of NETIMER 011.
NETIMER180: BLOCK ARB DESTINATION INTERVAL TIME
All: (10 ... 30 Sec): 15 Sec

This timer defines the interval during which an ARB destination will be blocked (depending on
the system option) after the ARB destination becomes free.
NETIMER181: PPU RESPONSE TIME
All: (3 ... 3 Sec): 3 Sec

Response time of the PPU to a 'download data request' or a 'display data request'.
NETIMER182: DELTA ARB ON FREE TIME
All: (300 ... 86400 Sec): 1800 Sec

Define the ARB guarding time for ARB on free cases at the initiator side.
This parameter defines the time that an ARB on free call request remains valid at the initiator
side. The moment that this timer expires, the ARB call will be cancelled.
NETIMER183: DELTA ARB ON BUSY FOR DESTINATION TIME
All: (300 ... 86400 Sec): 1800 Sec

Define the ARB guarding time for ARB on busy cases at the destination side.
This parameter defines the time that an ARB on busy call request remains valid at the
destination side. The moment that this timer expires, the ARB relation will be cancelled at the
destination.
NETIMER184: DELTA ARB ON FREE FOR DESTINATION TIME
All: (300 ... 86400 Sec): 1800 Sec

219
Define the ARB guarding time for ARB on free cases at the destination side.
This parameter defines the time that an ARB on free call request remains valid at the
destination side. The moment that this timer expires, the ARB relation will be cancelled at the
destination.
NETIMER185: SSM RESPONSE TIME LIMIT
All: (1 ... 6 Sec): 3 Sec

This parameter defines the maximum time that the SSM or the DSM may take before replying
on an service display request, a CNND or a TSD request from the ISPBX.
If the SSM or the DSM does not respond within this time the call will proceed without any
service information or CNND/TSD information. This means that nothing will be displayed on
the extension display.
NETIMER186: SAS DEVICE IDLE AFTER FAILURE TIME
All: (30 ... 600 Sec): 60 Sec

This timer is set by the alarm device handlers for the Alarm Unit.
If, after an open file, a failure is received, the timer is started. When the timer expires, the open
file will be sent again.
NETIMER187: LOGGING DEVICE IDLE AFTER FAILURE TIME
All: (30 ... 600 Sec): 60 Sec

This timer is set by the remote logging output process.
If, after an open file, a failure is received, the timer is started. When the timer expires, the open
file will be sent again.
NETIMER188: BROADCAST GUARDING TIME
All: (3 ... 3 Min): 3 Min

This timer is used by the monitoring service process. It is used as a master timer which triggers
a slave timer per PM. A conversion factor 5 is applicable, which means that the actual
broadcast guarding time is 900 seconds (15 minutes).
If, within this time no broadcast acknowledge is received, broadcasting is enabled again (it is
assumed that the PPU has missed a broadcast for some reason).
220
NETIMER191: MFE OVERALL GUARDING TIME
All: (60 ... 7200 Sec): 90 Sec

This timer defines the maximum time for the MFC protocol sequence.
The timer is started after an outgoing or incoming seizure. It is stopped at the moment the
MFC connection is released. If the timer expires, congestion signal is send to the opposite
exchange.
NETIMER192: PVN SIGNALLING CHANNEL SETUP GUARD TIME
All: (12 ... 255 Sec): 12 Sec

This timer guards the setup time of the PVN signalling channel. It also covers the security
mechanism. If the signalling channel is not setup within this time, then the setup has failed.
NETIMER193: PVN USER CHANNEL SETUP GUARD TIME
All: (12 ... 255 Sec): 12 Sec

This timer guards the setup time of the PVN user information channel. If the signalling channel
is not setup within this time, then the setup has failed.
NETIMER194: PVN USER CHANNEL RESERVATION GUARD TIME
All: (12 ... 255 Sec): 12 Sec

This timer guards the PVN ScenSIG protocol for reservation of the user information channel
after clearing of a PVN-DPNSS call. If the protocol is not ready within the specified time, then
the user information channel is cleared.
NETIMER195: PVN UCA GUARD TIME
All: (12 ... 255 Sec): 12 Sec

This timer defines the maximum time that a destination PTNX can keep a UCA reserved.
Within this time an incoming call on this UCA should arrive.
NETIMER196: ROUTE OPTIMISATION DELAY TIME
All: (0 ... 16383 Sec): 0 Sec

This timer defines the delay after which route optimisation should take place. The timer is
started at the moment a DPNSS call is transferred.
If multiple units of the originating ISPBX are on the original route, then the timer of the unit
221
where the DPNSS route resides is used.
NETIMER197: OVERLAY DIALLING TIME
All: (1 ... 8 Sec): 3 Sec

This timer defines the time period during which it is checked whether there are no more digits
to come.
If no digit is entered in this period, another analysis tree is chosen by the dial type 'Overlay
Time Out Dialling' and analysis starts again from the first dialled digit.
If one or more digits are entered in this period, another analysis tree is chosen by the dial type
'Overlay Continue Dialling' and analysis starts again from the first dialled digit.
NETIMER198: PVN HATCH COMMUNICATION GUARDING TIME
All: (30 ... 255 Sec): 30 Sec

This timer guards the setup of the hatch communication. Within this time 'hatch connected'
must be received.
NETIMER199: CSTA PREDICTIVE CALL RINGING TIME
All: (30 ... 240 Sec): 180 Sec

This timer defines the maximum ringing time of the destination in a predictive CSTA call with
allocation state 'established'. Within this time the destination has to answer the call, else the
predictive call side is released.
NETIMER200: CONVERSATION LIMITATION TIME
All: (10 ... 16383 Min): 16383 Min

This timer defines the duration time of external calls when the time-break facility is active.
After this time the trunk will be released.
When the maximum value (16383) is assigned, it means that the timer is not active. Even when
a higher value (except 16383) has been assigned, the ultimate value of this timer is 1440
minutes (24 hours). Note that the min. value is in seconds.
NETIMER201: ANNOUNCEMENT ANSWER DELAY TIME FOR DDI TO IDLE

EXTENSION
All: (0 ... 60 Sec): 25 Sec

This timer is only used when system option 39 is true. In that case it determines the time
222
before a voice announcement message is given to an incoming trunk to which announcement
has been projected for successful DDI calls and when it dialled:
- an idle extension or
- a (non ACD) group with at least one idle extension or
- meet me paging, when no other party is already paging for the same destination or
- speech paging, when no other party is already paging for the same destination and paging
equipment is found.
If system option 39 is false, then timer 99 is used for successful DDI calls.
This timer can be used to give announcements for unanswered calls after they are rerouted to
the operator: then the value of timer 201 must then be equal to or greater than the value of
timer 40.
NETIMER202: CIE TRANSMISSION GUARD TIME (CCS only)
All: (3 ... 3 Sec): 3 Sec

This timer guards transmission between central control and the CIE.
NETIMER203: DUAL MODE CLUSTER GUARD TIME (CCS only)
All: (30 ... 30 Sec): 30 Sec

This timer guards the communication between the two clusters during dual mode.
NETIMER204: DUAL MODE OPERATIONAL START TIME (CCS only)
All: (2 ... 2 Sec): 2 Sec

This timer guards the signal sending before an operational start can be done during dual mode.
NETIMER205: BIM TRANSMISSION GUARD TIME (CCS only)
All: (7 ... 7 Sec): 7 Sec

This timer guards transmission between central control and the BIM.
NETIMER206: DUAL MODE COMMUNICATION GUARD TIME (CCS only)
All: (2 ... 2 Sec): 2 Sec

This timer guards communication between the operational CPU cluster and the stand-by CPU
cluster. It expires when response, which is expected from the other cluster, does not come
within the specified time. This mechanism prevents from a dead-lock situation.
223
NETIMER207: CSTA COMMAND GUARDING TIME
All: (10 ... 30 Sec): 10 Sec

This timer guards the handling of CSTA commands by the switch. Whenever a CSTA
command is not handled before the timer expires, a failure-response is sent to the application
which issued the command.
NETIMER208: TERMINAL VERIFICATION RESPONSE TIME
All: (10 ... 60 Sec): 10 Sec

This timer guards the response of the terminal verification command sent to the PMC by OM
command DIDOTE. If no response is received within the specified time, control is returned
to the service process and a 'no response' indication is given on the OM terminal.
NETIMER212: DELAYED TRANSFER TIME
All: (12 ... 60 Sec): 20 Sec

This timer defines the maximum time during which a delayed call transfer can be performed.
This timer is applicable when a call is transferred before answer and no alerting has been
received yet from a terminal or network. When the timer expires the enquiry call is cleared,
and the party on hold is released or rerouted to the operator.
NETIMER213: MULTIPLE RING GROUP CALL SETUP DELAY TIME
All: (0 ... 5 Sec): 0 Sec

This timer defines (during the setup of a Multiple Ring Group call) the delay time between any
two subsequent members to start ringing (when idle) or to start COB (when busy).
NETIMER214: TWINNING DESTINATION SIGNALLING GUARDING TIME
All: (2 ... 10 Sec): 4 Sec

The ISPBX waits for the status of the twinning destination. If the twinning destination fails to
respond within this time, then it is assumed to be idle. The ISPBX will then try to set up a
connection to this destination.
NETIMER215: PDFS LOG FILE ACCESS REPEAT TIME
All: (10 ... 10 Sec): 10 Sec

This timer defines the access repeat time when access to the PDFSuu.LOG file has failed. The
PDFSuu.LOG file is a log file that logs the result of finished peripheral data file access
processed. When the access to the log file failed (e.g. the file was types), a period of pdfs-log-
file-access-repeat-time seconds will be waited before another access attempt to the log file is
224
executed.
NETIMER216: DISK SPACE VERIFICATION INTERVAL TIME
All: (30 ... 30 Sec): 30 Sec

This timer defines the disk space verification interval time. The disk space is verified when
applications writes data to a file on the storage device. The time between two verifications is
disk-space-verification-interval-time seconds.
NETIMER217: PERIPHERAL PROTOCOL TRACE RESPONSE GUARDING TIME
All: (5 ... 30 Sec): 10 Sec

This timer defines the peripheral protocol trace response guarding time. The responses on the
peripheral protocol trace commands to the PMC, sent by OM commands STRTPT, STOPPT
and DIPCRT are guarded by the "peripheral protocol trace response guarding time".
NETIMER218: SYNCHRONISATION ALARM INTEGRATION TIMER
All: (30 ... 65535 Sec): 65535 Sec

This timer defines the time, the CSG interface process waits before a synchronisation alarm is
generated. If the external clock is back within this time no synchronisation alarm is generated.
If the timer expires and the system is still synchronised on the internal clock, then alarm 61/13
is generated (system not synchronised to external reference).
If the timer has its default/maximum value, no timer is started and the synchronisation alarm
is given at once.
NETIMER219: MINIMUM INTRUSION TIME
All: (0 ... 16383 Sec): 5 Sec

After the system has automatically transferred a received intrusion-digit, it will only forward a
received force-release-digit after the time specified by this parameter. This way it is ensured
that a minimum intrusion time is guaranteed in which a calling user can announce that a tie line
circuit is going to be released.
NETIMER220: MAXIMUM TIME BETWEEN INTRUSION AND FORCE-RELEASE
All: (0 ... 16383 Sec): 60 Sec

This timer specifies the time the system accepts a force-release-suffix after an intrusion suffix
is received (not for operators). If the user does not dial this force-release suffix within the
specified time, the intrusion situation remains, but the tie line circuit can no longer be force
released.
225
This timer is only applicable in network situations; it can not be used in the own (local) PBX.
NETIMER221: LINE PARK INCOMING CALL GUARDING TIME
All: (10 ... 16383 Sec): 16383 Sec

This timer specifies the time after which an incoming call on a line waiting for line pickup is
diverted to assistance. When the value is 16383 sec the guarding time is infinite.
NETIMER222: QSIG COMMUNICATION GUARDING TIME
All: (2 ... 9 Sec): 4 Sec

This timer is similar to NETIMER 84 (DPNSS communication guarding time) and is also meant
to guard inner receive case.
Note: This timer should always be 1 second lower than the PFH interunit communication guard
time (NETIMER 77).
If the timer value is higher than the default value, it should be checked that it is lower than
the value of the "PABX communication timer" in the SSV60 application.
NETIMER223: DECT MOBILITY UPDATE RETRY TIMER
All: (4 ... 30 Sec): 10 Sec

The timer defines the time interval between the first attempt to update a node and the
subsequent attempt if the first attempt of update has failed. The timer value is in the order of
seconds to avoid crossings between two consecutive attempts.
NETIMER224: QSIG AOC MAXIMUM WAIT FOR FINAL CHARGE TIME
All: (15 ... 15 Sec): 15 Sec

The timer defines the guarding time of the forward release procedure to obtain charging
information from the outgoing gateway PINX. On time-out, or on receiving incorrect charging
information, alarm 061:033 is raised in the originating PINX.
NETIMER225: QSIG PATH REPLACEMENT INITIATION TIME
All: (30 ... 60 Sec): 30 Sec

The timer defines the guarding time for the receipt of a response to a request for QSIG Path
Replacement.
NETIMER226: QSIG PATH REPLACEMENT COMPLETION TIME
All: (15 ... 30 Sec): 15 Sec
226
The timer defines the guarding time for clearing of the old connection after the new
connection has been established.
NETIMER227: QSIG PATH RETENTION GUARDING TIME
All: (60 ... 180 Sec): 60 Sec

The timer defines the guarding time for path retention.
On receiving a request for path retention, this timer is started in the terminating PINX, which
waits for the receipt of a QSIG Supplementary Service invocation request. On expiry of the
timer, the call is cleared.
NETIMER228: QSIG CALL INTRUSION REQUEST GUARDING TIME
All: (1 ... 60 Sec): 30 Sec

This timer operates in the originating PINX. It is used for two purposes.
- To guard against absence of response to 'Supplementary Service Call Intrusion' request. It

defines the maximum time for which the originating PINX waits for the 'Supplementary
Service Call Intrusion' request response (success or error) from the wanted user PINX.
- To guard against absence of response to wait-on-busy request after successful intrusion.
It defines the maximum time for which the originating PINX waits for the wait-on-busy
request response (success or error) from the wanted user PINX.
NETIMER229: QSIG CALL INTRUSION PROTECTION LEVEL (CIPL) REQUEST

GUARDING TIME
All: (1 ... 60 Sec): 10 Sec

This timer operates in the wanted user terminating PINX to guard against absence of response
to request for 'Call Intrusion Protection Level' (CIPL) of unwanted user. It defines the
maximum time for which the wanted user PINX waits for the 'CIPL' request response (with
the CIPL of the unwanted user) from the unwanted user PINX.
NETIMER230: QSIG SUPPLEMENTARY SERVICE GUARD TIME
All: (1 ... 60 Sec): 15 Sec

The timer defines the guarding time for the Supplementary Services (de-) activation requests
like QSIG Message Waiting Indication and Do Not Disturb.
NETIMER231: QSIG AOC COMPLETE GUARDING TIME
All: (2 ... 8 Sec): 4 Sec
227
This timer is used for guarding the receipt of a response on the 'AOC Complete signal'.
NETIMER232: Call@Net APPLICATION SERVER LINK GUARDING TIME
All: (10 ... 10 Sec): 10 Sec

This timer is used for guarding the receipt of a response from the Call@Net application
server. After two times the time period of this timer without response from the Call@Net
application server, the link to the server is closed.
228
4. SUBCOMMANDS
This chapter contains the format description of all subcommands (in numerical order). In
general the format of the subcommands differs from the format of the OM command. The
meaning of the parameters in the subcommands is the same as the parameters of the OM
commands. So for the explanation of those parameters reference is made to the OM
COMMANDS MANUAL. For the new parameters a description is given at the corresponding
subcommand.
Appendix A A . OM COMMANDS AND SUBCOMMANDS in this manual gives a quick

reference of the OM commands and their related subcommands.
The main function of an OM command is to change or read operational data such as

administrative data, hardware configuration, routing data, etc. Other functions of an OM
command are for example:
- Validations of entered parameters.

- Composing the subcommands.
- Deciding what to do in case of errors.
Execution of an OM command usually results in the execution of one or more related

subcommands.
The function of the subcommands is to access the service processes by sending signals to
them. Subcommands are only executed in the unit to which they are sent.
• Validation
In general the validation of the parameters is done by the OM command; not by the
subcommand. However not in all circumstances validation can be done by the OM
command, for example checking against local boundaries. In these cases the actual
validation is postponed until the execution time, or the OM command composes a specific
test-subcommand. When that test-subcommand is executed validation is done.
229
4.1. SUBCOMMANDS S1xxxx
Find Momentary Traffic Observation Results
S10300 : <OBJECT>, <STATIC-IND>[,<PARAM-1>[,<ASSIST-GROUP>]];
OBJECT : A number 0 ... 18 or 21 identifying the object observed.

STATIC-IND : `Scan static data also' indicator; it can be:
0= both static and dynamic data;
1= only the dynamic data.
PARAM-1 : This optional parameter differs per object.
ASSIST-GROUP : only used for object 16: queue-type.
The subcommand format per object, for both static and dynamic data (static-ind=0), is as
follows:
- Bundle : S10300: 0,0,<BUNDLE>;

- Route : S10300: 1,0,<ROUTE>;
- Inter unit bundle : S10300: 2,0,<IU-BUNDLE>;
- Inter unit route : S10300: 3,0,<IU-ROUTE>;
- Extensions : S10300: 4,0;
- Extension or group : S10300: 5,0,<DNR>;
- Paging route : S10300: 6,0,<PAG-ROUTE>;
- Add On Circuit : S10300: 7,0;
- RKT-SDT : S10300: 8,0;
- SKT-RDT : S10300: 9,0;
- Incoming MFC : S10300: 10,0;
- Outgoing MFC : S10300: 11,0;
- Socotel data : S10300: 12,0;
- Convertor : S10300: 13,0,<CONVERTOR-TYPE>;
- Operators : S10300: 14,0;
- Specific operator : S10300: 15,0,<OPERATOR-DNR>;
- Queues : S10300: 16,0,<QUEUE-TYPE>,<ASSIST-GROUP>;
- SN channels : S10300: 17,0,<PM-SHELF>;
- Call data : S10300: 18,0,<UNIT>;
- Hatch : S10300: 21,0;
OM command DITRAF.
230
Display Periodic Traffic Observation Results
S10310 : <OBJECT>, <FIGURE-TYPE>[,<PARAM-1>[,<ANALYSIS-

GROUP>]];
OBJECT : A number 0 ... 19 or 21 identifying the object.

FIGURE-TYPE : This parameter indicates which results are given; it can be:
0= results of the last expired quarter of an hour;
1= cumulative results from beginning up to and including the
last quarter of an hour.
PARAM-1 : This optional parameter differs per object; see examples below.
ANALYSIS-GROUP : only used for object 19: dialled facilities.
The subcommand format per object, for the results of the last expired quarter of an hour
(figure-type=0), is as follows:
- Bundle : S10310: 0,0,<BUNDLE>;

- Route : S10310: 1,0,<ROUTE>;
- Inter unit bundle : S10310: 2,0,<IU-BUNDLE>;
- Inter unit route : S10310: 3,0,<IU-ROUTE>;
- Extensions : S10310: 4,0;
- Extension or group : S10310: 5,0,<DNR>;
- Paging route : S10310: 6,0,<PAG-ROUTE>;
- Add On Circuit : S10310: 7,0;
- RKT-SDT : S10310: 8,0;
- SKT-RDT : S10310: 9,0;
- Incoming MFC : S10310: 10,0;
- Outgoing MFC : S10310: 11,0;
- Socotel data : S10310: 12,0;
- Convertor : S10310: 13,0,<CONVERTOR-TYPE>;
- Specific operator : S10310: 14,0,<OPERATOR-DNR>;
- Queues : S10310: 15,0,<ASSIST-GROUP>;
- SN channels : S10310: 16,0,<PM-SHELF>;
- Call data : S10310: 17,0;
- IU traffic dispersion : S10310: 18,0,<UNIT>;
- Dialled facilities : S10310: 19,0,<RESULT-ID>,<ANALYSIS-GROUP>;
- Hatch : S10310: 21,0;
OM command DISPTO.
231
Change Traffic Measurement Object List
S10320 : <ACTION>[,<OBJECT>[,<PARAM-1>]];
ACTION=0 : Assign traffic measurement object (ASTMOB).

ACTION=1 : Delete traffic measurement object (DETMOB), or when no other
parameters are given:
Erase traffic measurement object list (ERTMLI)
For the other parameters, see subcommand S10310.
Read Traffic Measurement Object List
S10321 : ;
OM command DITMOB.
Start / Stop Traffic Measurement
S10330 : <ACTION>,[<PERIODS>][,<OUTPUT-SWITCH>];
ACTION=0 : Start Traffic Measurement (STRTTM).

S10330:0,<PERIODS>;
ACTION=1 : Stop Traffic Measurement (STOPTM).
S10330:1,,<OUTPUT-SWITCH>;
Change / Display Traffic Measurement Timing
S10331 : <ACTION>[,<ON-TIME>][,<PERIODS>,<CYCLIC>];
ACTION=0 : Assign Traffic Measurement Timing (ASTMTI).

S10331:0,<ON-TIME>,<PERIODS>,<CYCLIC>;
ACTION=1 : Delete Traffic Measurement Timing (DETMTI).
S10331:1,<ON-TIME>;
232
ACTION=2 : Display Traffic Measurement Timing (DITMTI).
S10331:2,;
Change Logical Device Name for Traffic Measurement
S10340 : <ACTION>,[<LDN>];
ACTION=0 : Assign and store traffic measurement output device name (CHTMOD).
S10340:0,<LDN>;
ACTION=1 : Remove output device name (CHTMOD).
S10340:1,;
Display Traffic Measurement Output Device / File Name / Status
S10341 : <ACTION>;
ACTION=0 : Display traffic measurement output devices (DITMOD).

ACTION=1 : Display traffic measurement output file names (DITMOF).
ACTION=2 : Display traffic measurement status (DISPTM).
Change Traffic Measurement Output File Name
S10342 : <ACTION>,[<FILE-NAME>];
ACTION=0 : Assign and store the new file name (CHTMOF).

S10342:0,<FILE-NAME>;
ACTION=1 : Remove the file name (CHTMOF).
S10340:1,;
Start Load Monitor
S10500 : <OUTPUT-FILE>,<MONITOR-INTERVAL>,<ON-TIME>,<OFF-
233
TIME>,<DATA-INDICATOR>;
OM command STALDM.
Display Overview of Load
S10510 : <DATA-INDICATOR>;
OM command DIOVLD.
Cancel Load Monitor
S10520 : <ACTION>,[<ON-TIME>],[<OFF-TIME>];
ACTION=2 : Display load monitor intervals (DISLDM).

S10520:2,,;
ACTION=1 : Cancel load monitor (CANLDM).
S10520:1,[<ON-TIME>],[<OFF-TIME>];
Tune Load Control Parameters
S10530 : <PARAM-NAME>,<DATA-VALUE>;
PARAM-NAME : The identification of the parameter to change.

DATA-VALUE : The new parameter value (0 ... 2000).
OM command CHLDCT.
234
Set Date and Time
S21000 : <YEAR>,<MONTH>,<DAY>,<DAY-OF-WEEK>,<HOURS>,<MINUTES>;
OM commands SEDATI.
Display Exchange Identity
S21050 : <REPORT-FORM>;
OM command DIEXID.
Change Cluster Identity
S21060 : [[<CLUSTER-ID>],[<ASSISTANCE-POINT>],[<LOCAL-
OPERATOR-MARK>]];
OM command CHCLID.
Assign / Erase Node ID to/from Node ID Table
S21070 : <ACTION>[,<NODE-ID>];
ACTION=0 : Assign Node ID to Node ID Table (ASNOIT).

S21070:0,<NODE-ID>;
ACTION=1 : Erase Node ID from Node ID Table (ERNOIT).
S21070:1[,<NODE-ID>];
Facility Timing
S21100 : <ACTION>,<FACILITY>[,<ON-TIME>,<OFF-
235
TIME>][,<CYCLIC>][,<SEQUENCE-TABLE/ZONE>];
ACTION=0 : Assign facility timing (ASFATI).

S21100:0,<FACILITY>,<ON-TIME>,<OFF-
TIME>,<CYCLIC>[,<SEQUENCE-TABLE/ZONE>];
ACTION=1 : Delete facility timing (DEFATI).
S21100:1,<FACILITY>,[,<ON-TIME>,<OFF-TIME>][,,<SEQUENCE-
TABLE/ZONE>];
If the parameters ON-TIME and OFF-TIME are omitted all intervals are
deleted.
If the parameter SEQUENCE-TABLE is omitted, the interval is deleted for
all sequence tables.
ACTION=2 : Display facility timing (DIFATI).
S21100:2,<FACILITY>[,,,,<SEQUENCE-TABLE/ZONE>];
If the parameter SEQUENCE-TABLE is omitted, the interval of all sequence tables is

displayed.
Licensing
S21200 : [<LICENSE-NUMBER>],[<LIC_REPORT>];
LICENSE-NUMBER : Identification of the license number to be displayed. When

omitted, all licences are displayed.
LIC_REPORT : Identification of which license string is to be displayed. When
omitted, the active license string is displayed. Valid values for
LIC_REPORT are:
0 = system licenses
1 = licenses from file
OM command DILICS.
236
Activate License String
S21210 : <ACTION>;
ACTION=0 : Check license file (ACLICS).

S21210: 0;
ACTION=1 : Activate license file (ACLICS).
S21210: 1;
Retrieve Fingerprint
S21220 : ;
OM command RTFING.
Change Default Authority Class or Protection Level
S22000 : <LDN>,<ACTION>,<AUTHORITY/PROT-TYPE>,<PROTECTION>;
ACTION=0 : Set the default authority class (CHDEAU).

S22000: <LDN>,0,<AUTHORITY>;
ACTION=1 : Erase the default authority class (CHDEAU).
S22000:<LDN>,1,<AUTHORITY>;
ACTION=2 : Set default protection level (CHDEPR).
S22000:<LDN>,2,<PROT-TYPE>,<PROTECTION>;
Display Default Authority Class or Protection Level
S22010 : <LDN>;
OM command DIAUPR.
237
Change Authority Class Index and Value Relation
S22020 : <AUTHORITY-INDEX>[,<AUTHORITY>];
Change Authority Class Index and Value Relation (CHACIV):
S22020:<AUTHORITY-INDEX>,<AUTHORITY>;
Reset Authority Class Index and Value Relation to default:
S22020:<AUTHORITY-INDEX>;
Change Password
S22100 : <PW-GROUP>,<PW-KEY>,[<SCRM-OLD-PW>],<SCRM-NEW-PW>;
OM command CHPASS.
The parameters SCRM-OLD-PW and SCRM-NEW-PW are the scrambled old and new
passwords.
Change Traffic Class Restriction Level
S23000 : <TERMINAL-TYPE>,[<TRFC>],[<RESTRICTION>];
OM commands CHTFCR and DITFCR.
Change Facility Class Mark Restriction Level
S23010 : <TERMINAL-TYPE>,[<FCM>],[<RESTRICTION>];
OM commands CHFCMR and DIFCMR.
238
Add New Extension DNR/BSP-ID
S30000 : <BSP-ID>,<SHELF>,[<BRD>],<CRT>[,<ORDER-IND>][,<NEW/
INTERUNIT-MOVE CREATION>];
NEW/INTERUNIT-MOVE CREATION (0 or 1) is used (for PVE) to indicate if a BSP-ID has

been created due to an inter-unit move or it is just a new relation. When this optional
parameter is not present it is assumed that it concerns a new relation.
0 = creation due to interunit move.
1 = creation due to new relation.
Delete Extension DNR/BSP-ID
S30001 : <BSP-ID>,<DELETE/INTERUNIT-MOVE INDICATION>;
DELETE/INTERUNIT-MOVE INDICATION (0 or 1) is used (for PVE) to indicate if a BSP-ID

has been deleted or a BSP-ID has been deleted with the intention to move the BSP-ID to
another unit.
0 = interunit move.
1 = delete.
Move Extension DNR
S30002 : <DNR>,<SHELF>,<BRD>,<CRT>[,<ORDER-IND>];
239
Try Ownership and Claim Resources
S30003 : [<DNR>],[<SHELF>],[<BRD>],[<CRT>],<UNIT>;
This subcommand may never be written to the journal file.
Force Claim or Reset Claim of Resource
S30004 : <ACTION>,[<DNR>],[<SHELF>],[<BRD>],[<CRT>],<UNIT>;
ACTION=1 : Stop guard then claim resource:

The subcommand is meant as a protection when processing journals.
Normally this subcommand is written to the journal file.
ACTION=2 : Reset claim(s):
The subcommand is used to stop the protection after completion of the
OM command. Normally this subcommand is written to the journal file.
ACTION=3 : Stop guard and reset claim(s):
This combination is used when the command is aborted before the actual
execution is started. In this application the subcommand is not written to
the journal file.
Change DNR-Unit Relation
S30005 : <DNR>,[<UNIT>];
Subcommand Check Move Success
S30006 : <ACTION>,<BSP-
ID>[,<SHELF%BRD%CRT>[,<BSPS%NE%EXEC%HOTL%LONG>]],[<OR
DER-IND>];
BSPS : Number of BSPs to be moved;

NE : Number of Night Extensions to be moved;
240
EXEC : Number of Executives to be moved;
HOTL : Number of Hot Lines to be moved;
LONG : Number of Long DNRs (used for destination identification) to be moved.
ACTION=1 : Delete BSP

S30006:1,<BSP-ID>;
ACTION=2 : Delete DNR (+BSPs)
S30006:2,<BSP-ID>;
ACTION=3 : Add DNR + one BSP
S30006:3,<BSP-ID>,<SHELF%BRD%CRT>;
ACTION=4 : Add one BSP
ACTION=5 : Move DNR to other EHWA within unit
ACTION=6 : Move DNR to other unit
S30006:6,<BSP-ID>,<SHELF%BRD%CRT>,
<BSPS%NE%EXEC%HOTL%LONG>;
Subcommand Handle Extension Data
S30007 : <ACTION>,<BSP-ID>[,<MET-COUNT/FIX-MSN-
DIGIT>,[<TRFC>],<NO-C/FCM-DATA>[,<SUB-C>]];
FCM-DATA =Facility class mark data;

FIX-MSN-DIGIT =Fixed MSN digit;
MET-COUNT =Meter count;
NO-C =No congestion data;
SUB-C =Subscriber category;
TRFC =Traffic service class data.
ACTION=1 : Read no congestion data.

S30007:1,<BSP-ID>;
ACTION=2 : Read Facility Class Mark data and Fixed MSN data.
S30007:2,<BSP-ID>;
ACTION=3 : Read congestion data.
S30007:3,<BSP-ID>;
ACTION=4 : Write no congestion data; reset meter count.
241
S30007:4,<BSP-ID>,<MET-COUNT>,<TRFC>,<NO-C>,<SUB-
C>;
ACTION=5 : Write no congestion data; no reset.
S30007:5,<BSP-ID>,<MET-COUNT>,<TRFC>,<NO-C>,<SUB-
C>;
ACTION=6 : Write Facility Class Mark data and Fixed MSN data
S30007:6,<BSP-ID>,<FIX-MSN-DIGIT>,,<FCM-DATA>;
Handle IABD Data
S30008 : <ACTION>,<DNR>,<IABD-NO>[,<DEST-NUMBER>];
IABD-NO = Sequence number;

DEST-NUMBER = Individual abbreviated number.
ACTION=1: Read IABD number;

2: Write IABD number;
3: Erase IABD number list for extensions with Facility Class Mark (FCM);
4: Erase IABD number list for operators;
5: Check LENR facility for extensions with check on FCM;
6: Check LENR facility for extensions without check on FCM;
7: Assign LENR buffer for extensions;
8: Assign LENR buffer for operators;
9: Erase IABD number list for extensions with FCM.
10: Check IABD facility and erase IABD number
11: Check IABD facility and write IABD number
12: Display IABD-NR
Subcommand to Select Function for Command CHDNRC
S30009 : <BSP-ID>[,<UNIT>];
242
Change Operator DNR-Operator Circuit Relation
S30010 : <DNR>[,<SHELF>],[<BRD>],[<CRT>],<OPERATOR-TYPE>;
Add or move operator DNR (CHOPDC):
S30010:<DNR>,<SHELF>,<BRD>,<CRT>,<OPERATOR-TYPE>;
Delete operator DNR (CHOPDC):
S30010:<DNR>,,,,<OPERATOR-TYPE>;
Subcommand Check Operator Move
S30011 : <DNR>[,<SHELF>,<BRD>,<CRT>];
Check possibility to add an operator DNR-operator line circuit relation:
S30011:<DNR>,<SHELF>,<BRD>,<CRT>;
Check possibility to delete an operator DNR-operator line circuit relation:
S30011:<DNR>;
Subcommand for Retrieving Message Waiting Information
S30012 : <ACTION>,<BSP-ID>[,<MESSAGE WAITING INFO TYPE>];
OM command CHDNRC.
ACTION=3 : Retrieve message waiting information.

S30012:3,<BSP-ID>;
ACTION=5 : Change message waiting information.
S30012:5,<BSP-ID>,<MESSAGE WAITING INFO TYPE>;
MESSAGE WAITING INFO TYPE : one digit (0...7)

This digit in binary format gives : XYZ
X= message waiting type 2 : 1 (= present) or 0 (= absent)
243
Y= message waiting type 1 : 1 (= present) or 0 (= absent)
Z= message waiting type 0 : 1 (= present) or 0 (= absent)
Display DNR/BSP-ID-Circuit Relation
S30020 : <BSP-ID>;
OM command DIDNRC.
Display Circuit - DNR/BSP-ID Relation
S30030 : <SHELF>,<BRD>,<CRT>;
OM command DICDNR.
Change and Display MSN parameters of an EHWA
S30060 : <ACTION>,<SHELF>,<BRD>,<CRT>[,<MSN-TYPE>,<NUMBER-OF-
MSN-DIGITS>];
OM commands: CHMSNP and DIMSNP.
ACTION=2 : Display MSN parameters of an EHWA.

S30060:2,<SHELF>,<BRD>,<CRT>;
ACTION=5 : Change MSN parameters of an EHWA.
S30060:5,<SHELF>,<BRD>,<CRT>,<MSN-TYPE>,<NUMBER-OF-
MSN-DIGITS>;
Change and Display fixed MSN digits.
S30080 : <ACTION>,<BSP-ID>[,<DIGIT>];
OM commands: CHFMSN and DIFMSN.
ACTION=2 : Display fixed MSN digit for a BSP.

S30080:2,<BSP-ID>;
244
ACTION=5 : Change fixed MSN digit for a BSP.
S30080:5,<BSP-ID>,<DIGIT>;
Change or Display COB Queue Type to BSP-ID Relation
S30100 : <BSP-ID>[,<COB-QUEUE-TYPE>];
Assign/change COB Queue Type to BSP-ID Relation (CHCOBD):
S30100:<BSP-ID>,<COB-QUEUE-TYPE>;
Display COB Queue Type to BSP-ID Relation (DICOBD):
S30100:<BSP-ID>;
Change Traffic Class of DNR/BSP-ID
S30250 : <DAY-TRFC>,<NIGHT-TRFC>,<UP-TRFC>,<DOWN-TRFC>,<BSP-
ID>;
OM command CHTRFC.
Display Traffic Class of DNR/BSP-ID
S30260 : <BSP-ID>;
OM command DITRFC.
Change Subscriber Category of DNR/BSP-ID
S30280 : <SUBSCR-CAT>,<BSP-ID>;
OM command CHCASC.
245
Display Subscriber Category of DNR/BSP-ID
S30281 : <BSP-ID>;
OM command DICASC.
Change / Display DNR Service Capabilities
S30290 : <ACTION>,<BSP-ID>[,<IBSC>[,<BSPT>[,<ORDER-IND>]]];
ACTION=0 : Change DNR service capabilities (CHDNRS).

S30290:0,<BSP-ID>,<IBSC>[,<BSPT>];
If parameter BSPT is omitted, the BSPT corresponding with the entered
IBSC is selected.
ACTION=2 : Display DNR service capabilities (DIDNRS).
S30290:2,<BSP-ID>;
ACTION=3 : Retrieve DNR service capabilities.
S30290:3,<BSP-ID>;
Assign Facility Class Mark to an Extension
S30300 : <FCM>,<ACTION>,<BSP-ID>;
ACTION=1 : Assign facility class mark to an extension (ASFACM).

S30300:<FCM>,1,<BSP-ID>;
ACTION=0 : Erase facility class mark from an extension (ERFACM).
S30300:<FCM>,0,<BSP-ID>;
Assign, Erase and Display Selective Answering DNR
S30310 : <ACTION>[,<DNR>];
ACTION=0 : Assign Selective Answering DNR (ASSADN).

S30310:0,<DNR>;
246
ACTION=1 : Erase Selective Answering DNR (ERSADN).
S30310:1,<DNR>;
ACTION=2 : Display Selective Answering DNR (DISADN).
S30310:2;
Display all Facility Class Marks of an Extension
S30320 : <BSP-ID>;
OM command DIFACM.
Change Default Facility Class Mark Set for Extensions
S30330 : <FCM>,<ACTION>;
ACTION=0 : Delete facility class mark to the default set (CHDFCM).

S30330:<FCM>,0;
ACTION=1 : Add facility class mark to the default set (CHDFCM).
S30330:<FCM>,1;
Display Facility Class Mark Summary
S30340 : <FCM>;
OM command DIFCSU.
Change Call Forwarding Relation
S30400 : <CF-TYPE>,<ACTION>,<ORIG-BSP-ID>,<DEST-NUMBER>,<DEST-
TYPE>,[<CFDA-TIME>][,<CALL-ORIGINATOR-TYPE>][,<ACT>];
ACTION=0 : Assign Call Forwarding (CHCALF).

S30400:<CF-TYPE>,0,<ORIG-BSP-ID>,<DEST-NUMBER><DEST-
TYPE>,[<CFDA-TIME>][,<CALL-ORIGINATOR-TYPE>][,<ACT>];
ACTION=1 : Erase Call Forwarding (CHCALF).
247
S30400:<CF-TYPE>,1,<ORIG-BSP-ID>;
ACTION=2 : Display Call Forwarding (DICALF).
S30400:<CF-TYPE>,2,<ORIG-BSP-ID>;
Parameter ACT is only used when ACTION = 0 and CF-TYPE = 1.
ACT = 1 indicates that the CFBE has to be activated : in case of a 'RTRIEV dynamic data', the
activated CFBEs are included in the RTRIEV files.
Call Rerouting Diversion Table
S30410 : <ACTION>,[<ROUTE>],[<REROUTING DIVERSION NUMBER>];
ACTION=0 : Assign Rerouting Diversion Number to Route (ASRTDN).

S30410:0,[<ROUTE>],[<REROUTING DIVERSION NUMBER>];
ACTION=1 : Erase Rerouting Diversion Number from Route (ERRTDN).
ACTION=2 : Display Rerouting Diversion Number for Route (DIRTDN).
Change Follow Me
S30430 : <ACTION>,<ORIG-BSP-ID>[,<DEST-NUMBER>][,<ORIG-
IBSC>][,<ACTIVATE>][,<OM-ACTIVATED>];
OM commands CHFLME and DIFLME.
ACTION= 0: Validate FM originator;

1: Validate fixed FM originator;
2: Validate FM destination;
3: Activate FM;
4: Assign fixed FM;
5: Erase fixed FM;
6: Cancel FM;
7: FM retrieve data;
8: FM switch prepare mark;
9: FM switch fixed mark;
10 : Read all follow me destinations.
248
Parameter ACTIVATE is only used when ACTION = 4.
ACTIVATE = 1 indicates that the fixed FM has to be activated : in case of a 'RTRIEV dynamic
data', the activated fixed FMs are included in the RTRIEV files.
Parameter OM-ACTIVATED can be 0 or 1.
- 0 = Indicates that the subcommand has not been initiated by means of OM.
Absence of this parameter has the same meaning.
- 1 = Indicates that the subcommand is initiated by OM command CHFLME.
When this parameter is set the execution of the subcommand will be done in a different
way when ACTION = 3 (Activate FM) or ACTION = 6 (Cancel FM).
Change Hot Line
S30500 : <ACTION>,<ORIG-BSP-ID>[,<DEST-NUMBER>,<DELAY>,<POST-
DIAL>,<TRFC>];
ACTION=0 : Assign hot line (CHHOTL).

S30500:0,<ORIG-BSP-ID>,<DEST-NUMBER>,<DELAY>,<POST-
DIAL>,<TRFC>;
ACTION=1 : Erase hot line (CHHOTL).
S30500:1,<ORIG-BSP-ID>;
ACTION=2 : Display hot line (DIHOTL).
Change and Display Fixed Trunk Line Identity
S30510 : <ORIG-BSP-ID>[,<IDENT-NUMBER>];
Change Fixed Trunk Line Identity (CHFTLI).

S30510: <ORIG-BSP-ID>,<IDENT-NUMBER>;
Display Fixed Trunk Line Identity (DIFTLI).
S30510: <ORIG-BSP-ID>;
249
Change and Display Entry Point Local Exchange
S30520 : <ACTION>[,<DEST-NUMBER>];
ACTION=0 : Change Entry Point Local Exchange (CHEPLE).

S30520: 0,<DEST-NUMBER>;
ACTION=1 : Erase Entry Point Local Exchange (CHEPLE).
S30520: 1;
ACTION=2 : Display Entry Point Local Exchange (DIEPLE).
S30520: 2;
Handle Secretary Data
S30600 : <ACTION>,<EXEC-BSP-ID>,<EXEC-RANK>,<SECR-BSP-
ID>,<SECR-RANK>,<TYPE-CODE>;
OM commands ASEXSE and CREXSE.
ACTION=0 : Append a new executive secretary to the pool identified by a secretary

member of that pool.
ACTION=1 : Check that the given secretary is no member of another pool and that space
is available to create a new pool.
ACTION=2 : Create a new executive-secretary pool.
ACTION=3: Erase the pool identified by a secretary member of that pool.
ACTION=4: Validate the given BSP-ID as member of a pool and return a secretary
member of that pool as pool identification.
ACTION=5 : Read and return all executives that are member of the pool identified by a
secretary of that pool.
ACTION=6 : Validate the input parameters against the pool data of the pool identified by
a secretary member of that pool.
Handle Executive Data
S30610 : <ACTION>,<EXEC-BSP-ID>,<SECR-BSP-ID>[,<MULTI-SECR-
MARK>,<CFTS-MARK>[,<BUSY-BUSY-IND%EXEC-LINE-POS%EXEC-
250
PICKUP-ALLOWED>]];
OM commands ASEXSE and CREXSE.
ACTION=0 : Validate executive BSP-ID

S30610:0,<EXEC-BSP-ID>,<SECR-BSP-ID>;
ACTION=1 : Erase executive data in extension service.
S30610:1,<EXEC-BSP-ID>,<SECR-BSP-ID>;
ACTION=2 : Write an executive BSP-ID in extension service.
S30610:2,<EXEC-BSP-ID>,<SECR-BSP-ID>,<MULTI-SECR-
MARK>,<CFTS-MARK>[<BUSY-BUSY-IND%EXEC-LINE-
POS%EXEC-PICKUP-ALLOWED>];
CFTS-MARK can be 0 or 1. It represents the call forwarding on busy executive to secretary;

this is the first digit of the TYPE-CODE parameter.
Erase all Executive Data
S30611 : ,<EXEC-BSP-ID1>,[<EXEC-BSP-ID2>],[<EXEC-BSP-
ID3>],[<EXEC-BSP-ID4>],[<EXEC-BSP-ID5>];
OM command EREXSE.
Display one or all Executive Secretary Pools
S30620 : [<EXEC/SECR-BSP-ID>];
OM command DIEXSE.
Test on/Create Command File to erase Executive Secretary Group
S30630 : <ACTION>,<DNR/BSP-ID>[,<COMMAND FILE>,<DEFAULT

PROTECTION>];
ACTION=0 : Validate BSP-ID (CRESGR).

S30630:0,<BSP-ID>;
251
ACTION=1 : Create command file to erase executive secretary group (CRESGR).
S30630:1,<DNR>[,<COMMAND FILE>,<DEFAULT
PROTECTION>];
OM command ERESGR.
Display Subcommand for OM command DIESGR
S30640 : [<GROUP-DNR>];
OM command DIESGR.
Store or Erase Group Arrangement Data
S30700 : <ACTION>,<GROUP-DNR>,[<SUPERVISOR-BSP-ID/MEMBER-DNR/
MEMBER-RANK/ACD-PRIORITY%ACD-FULL-THRESHOLD%ACD-BUSY-
THRESHOLD>],[<GROUP-PROPS/SWITCH-ALL/INIT-STATUS/ACD-
FORCED-ABSENT-TIME%ACD-AFTER-CALL-WORK-TIME%ACD-CALL-
IN-QUEUE-TIME>],[<MEMBER-RANK/GROUP-DISPLAY[%EXT-
PROPS]/ACD-PAUSE-TONE>],[<R[ST]/MEMBER-DNR%SWITCH-
ALL/INIT-STATUS%MEMBER-RANK/LINE-POS%PARK-POS/LDN>];
R = common park position (in the OM commands manual referred to as <PARK-POS>)
S = member line position (in the OM commands manual referred to as <LINE-POS>)
T = member park position (in the OM commands manual referred to as <PARK-POS>)
ACTION=0 : Create group arrangement (CRGRPA).

S30700:0,<GROUP-DNR>,<SUPERVISOR-BSP-ID>,<GROUP-
PROPS>,<GROUP-DISPLAY[%EXT-PROPS]>,<R>;
ACTION=1 : Assign a member to a group arrangement (ASGRPM).
S30700:1,<GROUP-DNR>,<MEMBER-BSP-ID>,<SWITCH-ALL/INIT-
STATUS>,<MEMBER-RANK>,<LINE-POS%PARK-POS>;
ACTION=2 : Erase group arrangement (ERGRPA).
S30700:2,<GROUP-DNR>,,,,;
ACTION=3 : Validate before create (CRGRPA).
S30700:3,<GROUP-DNR>,<SUPERVISOR-BSP-ID>,<GROUP-
PROPS>,<GROUP-DISPLAY>,<MEMBER-BSP-ID%RST>;
252
ACTION=4 : Validate before append (ASGRPA).
S30700:4,<GROUP-DNR>,<MEMBER-BSP-ID>,<SWITCH-ALL/INIT-
STATUS>,<MEMBER-RANK>, <LINE-POS%PARK-POS>;
ACTION=5 : Validate before delete member (DEGRPM).
S30700:5,<GROUP-DNR>,<MEMBER-RANK>;
ACTION=6 : Delete a member from a group arrangement (DEGRPM).
S30700:6,<GROUP-DNR>,<MEMBER-RANK>;
ACTION=7 : Switch member to absent
S30700:7,<GROUP-DNR>,<MEMBER-BSP-ID>;
ACTION=8 : Change ACD group data 1 (see also action 10)
S30700:8,<GROUP-DNR>,<ACD-THRESHOLD-PRIORITY%ACD-
FULL-THRESHOLD %ACD-BUSY-THRESHOLD>,<ACD-FORCED-
ABSENT-TIME% ACD-AFTER-CALL-WORK-TIME%ACD-CALL-IN-
QUEUE-TIME>,<ACD-PAUSE-TONE>,<ACD-Q-POS-
ALGORITHM%ACD-Q-PRIORITY>;
ACTION=9 : Change ACD group Day/Night status.
S30700:9,<GROUP-DNR>,<DAY/NIGHT>;
ACTION=10 : Change ACD group data 2 (see also action 8).
S30700:10,<GROUP-DNR>,<ACD-LDN>;
The following special values are defined for the parameters:
- threshold-priority, forced-absent-time, after-call-work-time, call-in-queue-time and

pause-tone:
- 98=keep current value;
- 99=write default value.
- full-threshold and busy-threshold:
- 9998=keep current value;
- 9999=write default value.
Retrieve Group Arrangement Data
S30710 : <ACTION>[,<GROUP-DNR/MEMBER-BSP-ID>];
ACTION=0 : Check if given DNR is a group DNR.

S30710:0,<GROUP-DNR>;
ACTION=1 : Display group arrangement data; if GROUP-DNR is omitted the data of all
groups are displayed (DIGRPA).
S30710:1[,<GROUP-DNR>];
253
ACTION=2 : Display group member data (DIGRPM).
S30720:2,<MEMBER-BSP-ID>;
Retrieve Data of ACD Group and Members
S30730 : <DNR>,<INDICATOR>[,<MEMBER-RANK>];
INDICATOR: 0= display only statistical data;

1= display either statistical data or real-time data, depending on
whether new data is available or not.
OM command DIGRPS.
Retrieve Park/line Position Status or/and Executive Line Position of DNR
S30740 : <BSP-ID>;
OM command DIPLPO.
Change and Display Twinning Relation
S30750 : <ACTION>,<ORIG-BSP-ID>[,<DEST-NUMBER>];
ACTION = 0 Assign twinning relation (CRTWIN)

S30750:0, <ORIG-BSP-ID><DEST-NUMBER>;
ACTION = 1 Erase twinning relation (ERTWIN)
ACTION = 2 Display twinning relation (DITWIN)
254
Change Abbreviated Number
S30800 : <ACTION>,<AG>,<ABBR-NUMBER>,<EXP-NUMBER>,<TRFC>;
ACTION=0 : Assign abbreviated number (CHABNR).

S30800:0,<AG>,<ABBR-NUMBER>,<EXP-NUMBER>,<TRFC>;
ACTION=1 : Erase abbreviated number (CHABNR).
S30800:1,<AG>,<ABBR-NUMBER>;
Change Function Key Data
S30900 : <MENU>,<KEY>,<KEY-LEVEL>,[<KEY-DATA>],<PRIO-
CODE+SOFT-RING>[,<LED-CODE>];
OM command CHFKDA.
If parameter KEY-DATA is omitted, the key is deleted from the menu.
If parameter LED-CODE is omitted, LED off (=0) will be assigned.
Copy Function Key Data
S30903 : <ACTION>,[<SOURCE-MENU>],<DESTINATION-MENU>[,[<START-
KEY>],[<END-KEY>][,<KEY-LEVEL>]];
ACTION=0 : Copy source menu to destination menu (CPFKDA).

S30903: 0,[<SOURCE-MENU>],<DESTINATION-
MENU>[,[<START-KEY>],[<END-KEY>][,<KEY-LEVEL>]];
ACTION=1 : Clear the specified function key menu (CPFKDA).
S30903: 1,,<DESTINATION-MENU>[,[<START-KEY>],[<END-
KEY>][,<KEY-LEVEL>]];
255
Display Translated Function Key Menu
S30905 : <BSP-ID>[,<FK-NBR>];
OM command DITFKM.
Display Menu of DNR/BSP-ID
S30910 : <BSP-ID>;
OM command DIMDNR.
Change Menu Number of DNR/BSP-ID
S30920 : <BSP-ID>,[<MENU>];
OM command CHMDNR.
Display all DNRs/BSP-IDs related to a Menu number
S30930 : [<MENU>];
OM command DIDNRM.
Change Analysis Group or Compatibility Value
S30940 : <ACTION>,<BSP-ID>,[<AG>],[<CV>];
ACTION=0 : Change analysis group or compatibility value (CHAGCV).

S30940:0,<BSP-ID>,[<AG>],[<CV>];
ACTION=2 : Display analysis group or compatibility value (DIAGCV).
S30940:2,<BSP-ID>,,;
256
Request Download for BSP-ID
S30960 : <BSP-ID>;
OM command DOWNLD.
Assign, Delete and Display PID or Cost Centre Numbers
S31000 : <ACTION>,[<PID/COST-
CENTRE>],[<TRFC>],[<DNR>][,<BUDGET>[,BUDGET-
UNIT>]%<BUDGET-ACTION>];
ACTION=0 Assign Cost Centre number (ASPICC):

S31000: 0 , <COST-CENTRE>, , ;
Assign General PID Number (ASPICC):
S31000: 0 , <PID>, <TRFC>, ;
Assign Personal PID Number (ASPICC):
S31000:0 , <PID>, <TRFC>, <DNR>;
Assign General PID with budget:
S31000: 0 , <PID>, <TRFC>, , <BUDGET>, <BUDGET-UNIT>;
ACTION=1 Erase PID or Cost Centre numbers (ERPICC):
S31000: 1 , <PID/COST-CENTRE>, , ;
Erase Personal PID number:
S31000: 1 , <PID>, , <DNR>;
Erase all Personal PID numbers for <DNR>:
S31000: 1 , , , <DNR>;
ACTION=2 Erase (without output) PID or Cost centre numbers (CHDNRC). See
ACTION = 1.
ACTION=3 Display PID or Cost Centre numbers (DIPICC):
S31000: 3 , <PID/COST-CENTRE>, , ;
Display Personal PID number (DIPICC):
S31000: 3 , <PID>, , <DNR>;
Display all Personal PID numbers for <DNR>:
S31000: 3 , , , <DNR>;
ACTION=4 Check PID or Cost Centre numbers (ASPICC).
S31000: 4 , <PID/COST-CENTRE>, [<TRFC>] , [<DNR>];
257
ACTION=5 Change Cost Centre Budget and Budget Unit
S31000: 5 , <COST-CENTRE>, <TRFC>, , <BUDGET>,
<BUDGET-UNIT>%<BUDGET-ACTION>;
Change Relation: DNR / Password Protected Facilities
S31330 : <ACTION>,[<DNR>],[<PSWD-FUNCTION>],[<PSWD>];
<PSWD-FUNCTION>:
0 =Up/Downgrading traffic class.

1 =Password DDO.
2 =Reset password to all zeros.
Omitted =Up/Downgrading traffic class / password DDO.
ACTION=0 : Assign access to Password Protected Facilities (ASAPPF).

S31330:0,<DNR>,[<PSWD-FUNCTION>],[<PSWD>];
If PSWD is omitted the default password (all zeros) is assumed.
If the PSWD-FUNCTION is omitted all relations (functions) are assigned to
the DNR.
ACTION=1 : Erase access to Password Protected Facilities (ERAPPF).
S31330:1,<DNR>,[<PSWD-FUNCTION>],;
If the PSWD-FUNCTION is omitted then all relations (functions) for the
DNR are erased.
ACTION=2 : Erase (without output) access to Password Protected Facilities
(CHDNRC).
S31330:2,<DNR>,[<PSWD-FUNCTION>],;
DNR are erased.
ACTION=3 : Display access to Password Protected Facilities (DIAPPF).
S31330:3,[<DNR>],[<PSWD-FUNCTION>],;
If the DNR is omitted the relations (functions) for all DNRs are displayed.
DNR are displayed.
If both parameters are omitted, then all relations (functions) are displayed.
ACTION=4 : Retrieve access to Password Protected Facilities (CHDNRC, RTRIEV).
S31330:4,<DNR>,<PSWD-FUNCTION>,;
ACTION=5 : Check access to Password Protected Facilities (CHDNRC).
S31330:5,,,;
258
Create / Change Compatibility Value
S32000 : <CV>,<VOICE/DATA>[,<V24-
CIRCUITS>,<SPEED+MODE>,<MISCELLANEOUS>[,<GUARD-
1+GUARD-2>]];
OM commands CRCVAL and CHCVAL.
Erase Compatibility Value
S32010 : <CV>;
OM command ERCVAL.
Change CV pair Connection Allowance Relation
S32020 : <CV-A>,<CV-B>,<CON-ALLOWANCE>;
OM command CHCVCA.
Create / Erase Convertor Type
S32030 : <ACTION>,<CONVERTOR-TYPE>;
ACTION=1 : Create convertor type (CRCTYP).

S32030:<1>,<CONVERTOR-TYPE>;
ACTION=0 : Erase convertor type (ERCTYP).
S32030:<0>,<CONVERTOR-TYPE>;
Assign / Erase Convertor EHWA Relation
S32040 : <SHELF>,<BRD>,<CRT>[,<CONVERTOR-TYPE>];
Assign convertor EHWA relation (ASCONV).
259
S32040: <SHELF>,<BRD>,<CRT>,<CONVERTOR-TYPE>;
Erase convertor EHWA relation (ERCONV).
S32040:<SHELF>,<BRD>,<CRT>;
Assign CV pair Convertor Type Relation
S32050 : <CV-A>,<CV-B>,<CONVERTOR-TYPE>;
OM command ASCVCT.
Display Convertor EHWA Relation
S32060 : [<CONVERTOR-TYPE>],<ACTION>;
ACTION=1 : Display convertor EHWA relation (DICONV).

S32060:<CONVERTOR-TYPE>,1;
ACTION=0 : Validate convertor EHWA relation.
S32060: <CONVERTOR-TYPE>,0;
Assign TMS Digit Position
S33000 : <DIGIT-POSITION>;
OM command ASTMSD.
Display TMS Window Size
S33010 : [<WINDOW>];
OM command DITMSW.
WINDOW=2..8 is used for services from SSM (TMS) to the ISPBX.
WINDOW=129..135 is used for services from the ISPBX to SSM (TMS).
260
In subcommands decimal values are used; in OM commands, hexadecimal values are used.
Window=129 decimal is window=81 hexadecimal, for example.
Assign TMS Window Size
S33020 : <WINDOW>,<WINDOW-SIZE>;
OM command ASTMSW. For the WINDOW parameter, see subcommand S33010.
Display TMS Announcement-Code Relation
S33030 : [<Announcement-Code>];
OM command DITMST.
Change TMS Announcement-Code Relation
S33040 : <ANNOUNCEMENT-CODE>,[<ANNOUNCEMENT-
SOURCE>,<SPECIFICATION>];
ANNOUNCEMENT-SOURCE is omitted:
S33040:<ANNOUNCEMENT-CODE>;
ANNOUNCEMENT-SOURCE =1:
S33040:<ANNOUNCEMENT-CODE>,1,<DIGIT-STRING>;
S33040:<ANNOUNCEMENT-CODE>,2,<TONE-FUNCTION-CODE>;
S33040:<ANNOUNCEMENT-CODE>,3,<SHELF>,<BOARD>,<CIRCUIT>;
261
Display TMS Logical Name Relation
S33050 : [<WINDOW>];
OM command DITMSL.
Change TMS Logical Name Relation
S33060 : <WINDOW>,[<LDN>][,<CLUSTER-ID>];
OM command CHTMSL. For the WINDOW parameter, see subcommand S33010.
Change Authorization Code
S34000 : <CV-VALUE>,<AC>;
OM command CHAUCO.
Display Metering Results
S35200 : <MET-TYPE>,[<DNR/UNIT/ROUTE>];
OM command DIMERE.
Start, Stop and Display Toll Ticketing or FDCR
S35300 : <ACTION>,<CR-TYPE>[,<FILE-NAME>];
CR-TYPE : Call Recording type:

0= FDCR command given;
1= Toll Ticketing command given.
ACTION=0 : Start Call Recording (STRTTT, STRTFR).
S35300:0,<CR-TYPE>,<FILE-NAME>;
ACTION=1 : Stop Call Recording (STOPTT, STOPFR).
S35300:1,<CR-TYPE>;
262
ACTION=2 : Display Call Recording status and characteristics (DISPTT, DISPFR).
S35300:2,<CR-TYPE>;
Change Threshold Level of Route
S35400 : <ROUTE>,[<TICS>][,<DURATION>];
OM command CHTRLV.
Change Toll Ticketing Characteristics
S35500 : <LINES-PER-PAGE>;
OM command CHTTCR.
Display Threshold Level of Route Number
S35600 : [<ROUTE>];
OM command DITRLV.
Change Toll Ticketing or FDCR Output Device
S35700 : <ACTION>[,<LDN>][,<FILE-NAME>][,<OUTPUT-FORMAT-
VERSION>];
ACTION=0 : Change Call Recording output device (CHTTOD, CHFROD).

S35700:0,<LDN>[,,<OUTPUT-FORMAT-VERSION>];
ACTION=2 : Display Call Recording output device (DITTOD, DIFROD).
S35700:2;
The parameter <FILE-NAME>is not yet implemented, but has been added for future use.
263
Change FDCR Characteristics
S35800 : <FDCR-CALL-TYPE>,<OFF-ON>;
OM command CHFRCR.
Change Special Extension (up to/including Call@Net 2.7)
S36100 : [<DNR>],<TYPE>,<ACTION>,[<ROUTE>or <ASSIST-

GROUP>],[<SHELF%BRD%CRT>[,<B-CHANNEL>]];
TYPE 1: Main Common Night Extension (MCNE);

2: Sub Common Night Extension (SCNE);
3: Individual Night Extension (INE);
4: Overflow Extension (OVE);
5: Permanent Line Extension (PLE).
ACTION=0 Read special extensions

- General MCNE S36100:,1,0;
- Specific MCNE S36100:,1,0,<ASSIST-GROUP>;
- SCNE S36100:,2,0,<ROUTE>;
- INE S36100:,3,0,,<SHELF%BRD%CRT>[,<B-
CHANNEL>];
- OVE S36100:,4,0,<ROUTE>;
- PLE S36100:,5,0,,<SHELF%BRD%CRT>[,<B-
CHANNEL>];
ACTION=1 Assign or delete MCNE (CHMCNE).
Assign/change general MCNE (CHMCNE)
S36100:<DNR>,1,1;
Delete general MCNE (CHMCNE).
S36100:,1,1;
Assign/change specific MCNE (CHMCNE)
S36100:<DNR>,1,1,<ASSIST-GROUP>;
Delete specific MCNE (CHMCNE)
S36100:,1,1,<ASSIST-GROUP>;
Assign or change SCNE (CHSCNE).
S36100:<DNR>,2,1,<ROUTE>;
264
Delete SCNE (CHSCNE).
S36100:,2,1,<ROUTE>;
Assign or change INE (CHINEX).
S36100:<DNR>,3,1,,<SHELF%BRD%CRT>[,<B-CHANNEL>];
Delete INE (CHINEX).
S36100:,3,1,,<SHELF%BRD%CRT>[,<B-CHANNEL>];
Assign or change OVE (CHOVEX).
S36100:<DNR>,4,1,<ROUTE>;
Delete OVE (CHOVEX).
S36100:,4,1,<ROUTE>;
Assign or change PLE (CHPLEX).
S36100:<DNR>,5,1,,<SHELF%BRD%CRT>[,<B-CHANNEL>];
Delete PLE (CHPLEX).
S36100:,5,1,,<SHELF%BRD%CRT>[,<B-CHANNEL>];
ROUTE is the route number for SCNE or OVE.
Change Special Extension (since Call@Net 2.8 upwards)
S36100 : [<DNR>],<TYPE>,<ACTION>,[<ASSIST-GROUP/CV>or
<ROUTE>],[<SHELF%BRD%CRT>[,<B-CHANNEL>]];
For backward compatibility during upgrading via RTRIEV-files, the subcommand still accepts
Assistance Groups when manipulating MCNE relations.
Below, only the differences with the command above (up to/including Call@Net 2.7) are
given:
ACTION=1 Assign or delete MCNE (CHMCNE). Only to be used when upgrading via
RTRIEV-files. The 4th parameter is handled as <ASSIST-GROUP>.
Internally all CVs, related to the ASSIST-GROUP are retrieved and
assigned to the MCNE-DNR.
S36100:<DNR>,1,1,<ASSIST-GROUP>;
S36100:,1,1,<ASSIST-GROUP>;
ACTION=2 Assign or delete MCNE-CV relation
S36100:<DNR>,1,2,<CV>;
265
S36100:,1,2,<CV>;
Read or Change Night Extension Marks
S36101 : <BSP-ID>,<TYPE>,<ACTION>;
ACTION=1 : Check special extension;

ACTION=2 : Set special extension;
ACTION=3 : Reset special extension;
ACTION=4 : Set prohibit absence mark;
ACTION=5 : Reset prohibit absence mark.
TYPE is the same as for S36100.
Read Night Extension Availability
S36102 : <DNR>,<TYPE>[,<READ-INDICATOR>][<ASSIST-GROUP>or
<CV>];
The 4th parameter in the command (<ASSIST-GROUP>or <CV>) must be read as follows:
- up to/including Call@Net 2.7: <ASSIST-GROUP>

- since Call@Net 2.8 upwards: <CV>
If <READ-INDICATOR>equals 0, then the system checks whether <DNR>is at least used

once, as a SCNE, OVE, INE or PLE.
If <READ-INDICATOR>equals 1, then the system checks whether <DNR>is at least used

twice, as a SCNE, OVE, INE or PLE.
If <READ-INDICATOR>is omitted, then 0 SCNEs, OVEs, PLEs or INEs are assumed with
this DNR.
If <TYPE>= MCNE and <READ-INDICATOR>equals 0, then the system checks whether

DNR has already been assigned as a general MCNE.
If <TYPE>= MCNE, <READ-INDICATOR>= 1 and <ASSIST-GROUP>or <CV>is not

given, the subcommand checks if the DNR has been assigned as an (ASSIST-GROUP or CV)
266
specific MCNE.
If <TYPE>= MCNE, <READ-INDICATOR>= 1 and <ASSIST-GROUP>or <CV>is

given, the subcommand checks if the DNR has been assigned as an (ASSIST-GROUP or CV)
specific MCNE to an ASSIST-GROUP or CV different from the given one.
Read CANS Availability
S36103 : [<DNR>];
Change Traffic Class of Night Extension Group
S36150 : <NE-LEVEL>,<TRFC>;
OM command CHTRNE.
Change CANS and Hooter Characteristics
S36200 : <ACTION>[,<UNIT>];
ACTION=1 : Assign CANS (ASCANS);

ACTION=2 : Erase CANS (ERCANS);
ACTION=3 : Set hooter(CHHOOT);
ACTION=4 : Erase hooter(CHHOOT).
Display CANS and Hooter Characteristics
S36250 : ;
OM command DICANS.
267
Change and Display Basic DNR
S37000 : <ACTION>,[<BSP-ID>];
ACTION = 0 Assign Basic DNR (CHBDNR)

S37000: 0,<BSP-ID>;
ACTION = 1 Erase Basic DNR (CHBDNR)
S37000: 1,[<BSP-ID>];
ACTION = 2 Display Basic DNR (DIBDNR)
S37000: 2,[<BSP-ID>];
Collective Deactivation of Desksharing
S37010 : ;
OM command DADESK.
Change and Display DNR - Name Relation
S37100 : <ACTION>,[<NUMBER>],[<NAME1>],[<NAME2>], [<CLUSTER-

ID>],[<DIRECTORY>],[<ATTRIBUTES>];
This subcommand is a combined subcommand performing actions for CHNAME, DIDNRN,

DINDNR, DINAMU, CHDNRC, CHOPDC, CHBDNR, ERGRPA and RTRIEV.
Parameter ACTION is mandatory and the remaining parameters are optional, depending on
the value of ACTION.
ACTION = 0 Change DNR - Name relation (CHNAME and CHDNRC).

ACTION = 1 Delete (CHNAME).
ACTION = 2 Display Number Name (DIDNRN).
ACTION = 3 Display Name Number (DINDNR).
ACTION = 4 Display Memory (DINAMU).
ACTION = 5 Change special (RTRIEV).
ACTION = 6 Delete CDD and CNND without output (CHDNRC, CHOPDC,
CHBDNR and ERGRPA).
268
NAME1 Name string (part 1) belonging to the DNR (1...20 characters), possibly
enclosed by double quotes (if ACTION = 5)
NAME2 Name string (part 2) belonging to the DNR (1...20 characters), always
enclosed by double quotes (if ACTION = 5)
Note: - When the name string is retrieved by RTRIEV, it is written to the output enclosed by
double quotes. Therefore it may be necessary to split the name string into two separate
strings NAME1 and NAME2, since it may become larger than 20 characters.
- It is advised to enter names, by first entering the last name of a person and then the
first names or first name initials. This is in line with the browsing function.
Assign, Change and Display the Network Location of a Free Number
S37200 : <ACTION>[,[<FDNR>][,<FN-LOC-1>[,<FN-LOC-2>]]];
ACTION = 0 Assign/change the Network Location of a Free Number (CHFDNR).

S37200:0,<FDNR>,<FN-LOC-1>;
ACTION = 1 Erase one or all Free Numbers with the specified Network Location or all
Free Numbers (CHFDNR).
Remove all Free Numbers :
S37200:1;
Remove the specified Free Number :
S37200:1,<FDNR>;
Remove all Free Numbers with Network Location FN-LOC-1 :
S37200:1,,<FN-LOC-1>];
ACTION = 5 Change the Network Location of all Free Numbers with location FN-
LOC-1 to FN-LOC-1 (CHFDNR).
S37200:5,,<FN-LOC-1>,<FN-LOC-2>;
Subcommand for Retrieve Dynamic Data
S37300 : <ACTION>,<DNR-1>[,<DNR-2>];
ACTION = 0 Set group member absent.

S37300:0,<DNR-1>;
ACTION = 1 Set secretary absent.
269
S37300:1,<DNR-1>;
ACTION = 2 Set executive absent.
S37300:2,<DNR-1>;
ACTION = 3 Set executive DNR-2 absent at secretary DNR-1.
S37300:3,<DNR-1>,<DNR-2>;
ACTION = 4 Set night-extension absent.
S37300:4,<DNR-1>;
ACTION = 5 Activate don't disturb
S37300:5,<DNR-1>;
ACTION = 7 Set WAN DECT Mobility failed
S37300:7,<DNR-1>;
ACTION = 8 Reset WAN DECT Mobility failed
S37300:8,<DNR-1>;
Assign, Change, Delete and Display Voice Logging Relation
S37400 : <ACTION>,[<VL-SUBJECT>],[<VL-DESTINATION>];
ACTION=1 : Read VL-Subject/VL-Destination relation (DIVLRE).

S37400:1,<VL-Subject>,;
Display the specified Voice Logging relation.
S37400:1,,;
Display all specified Voice Logging relations.
ACTION=2 : Retrieve VL-Subject/VL-Destination relation (CHDNRC)
Retrieve the VL-Destination of the VL-Subject.
ACTION=4 : Check space (CHDNRC)
S37400:4,,;
Check space for one new relation.
ACTION=5 : Enter/Change VL-Subject/VL-Destination relation (CHDNRC, CHVLRE
and RTRIEV)
S37400:5,<VL-Subject>,<VL-Destination>;
If the entry exists, it is overwritten.
The Voice Logging relation is deleted.
S37400:5,,<VL-Destination>;
All Voice Logging relations to <VL-Destination>are deleted.
270
S37400:5,,;
All Voice Logging relations are deleted.
ACTION=6 : Check DNR.
S37400:6,<DNR>,;
Check that <DNR>is an allowed DNR.
ACTION=7 : Delete DNR (CHDNRC)
S37400:7,<DNR>,;
Deletes all relations where <DNR>is subject or destination.
Change Facility State
S37500 : <ACTION>,<FAC-ID>,<BSP-ID>,<STATE>;
ACTION=5 : Change Facility State (CHFSTA).

S37500:5,<FAC-ID>,<BSP-ID>,<STATE>;
Perform Number Analysis Action
S40200 : <TREE>,<ACTION>,<AG/NUMBER/ROUTE>,<DIAL-TYPE/TRFC>;
ACTION=0 : Assign analysis tree to dial type (ASTREE).

S40200:<TREE>,0,<AG/ROUTE>,<DIAL-TYPE>;
ACTION=1 : Change traffic class barring (CHTBAR).
S40200:<TREE>,1,<NUMBER>,<TRFC>;
ACTION=2 : Assign barred external numbers (ASBARR).
S40200:<TREE>,2,<NUMBER>;
ACTION=3 : Erase barred external numbers (ERBARR).
S40200:<TREE>,3;
Insert Analysis Result
S40210 : <TREE>,<NUMBER>,<TRFC>,<RESULT-ID>,<ADD-
271
INFO>[,[<ROUTE-TABLE>][,<TARIFF-CLASS>]];
The parameter ADD-INFO gives additional information necessary for OM commands

ASINTN, ASBLCK, ASEXTN, ASEXTP and CHCSDD.
- If the Result-id is 12, 13, 120 ... 125, ADD-INFO is maximum 3 digits indicating the paging
route.
- If the Result-id is 14 (priority trunk access code), 21 (trunk access code), 91 (network
access code) or 92 (ISDN access code), ADD-INFO is maximum 3 digits indicating the
destination.
- If the Result-id is 22 (external number) ADD-INFO has the layout:
PQRS MM NN DD with the following meaning:

.P = post-digit; default "D" (=null digit)
.Q = restoration mode; default "0" (=first party control)
.R = toll operator intrusion allowance; default "1" (=true)
.S = pre-digit; default "D" (=null digit)
.MM = minimum number length;
.NN = maximum number length;
.DD = dial tone place.
- If the Result-id is 48 (operator A general) ROUTE-TABLE indicates the CV-value.
- If the Result-id is 49 (operator A queue) ADD-INFO consists of 1 or 2 digits indicating the
A-queue number and ROUTE-TABLE indicates the CV-value.
- If the Result-id is 82 (TMS dialled) the actual length to be stored in the Number Analysis
Service is: NUMBER+ADD-INFO.
- If the Result-id is 132 (PVN User Channel Address dialled) or 133 (PVN signalling channel
address), ADD-INFO consists of 2 digits, indicating the unit number. The parameter
ROUTE-TABLE defines the PVN mode (one digit only!) for Result-id is 133.
- If the Result-id is 97 (internal destination with foreign address), then ADD-INFO consists
of 2 digits, indicating the local domain number.
- If the Result-id is 145 (CSTA server dialled), then ADD-INFO consists of 8 digits
(PPQQRRSS) with the following meaning :
- PP : Server-code
- QQ : Action code
- RR : Password number length
- SS : Additional info number length
- For other Result-ids ADD-INFO is two digits indicating the length.
272
Assign or Erase General Cancel Code
S40220 : <RESULT-ID>,<ACTION>;
ACTION=0 : Delete general cancel code (ERGECA).

S40220:<RESULT-ID>,0;
ACTION=1 : Add general cancel code (ASGECA).
S40220:<RESULT-ID>,1;
Assign Tariff Structure
S40240 : <ACTION>,<TARIFF-CLASS>[,<INITIAL-TARIFF>,<TIME-
PERIOD>,<DEFAULT-TARIFF>,[<TARIFF-2>[,<TARIFF-
3>[,<TARIFF-4>[,<TARIFF-5>]]]]];
ACTION=0 : Assign Tariff Class (CHTRIF)

S40240: 0,<TARIFF-CLASS>[,<INITIAL-TARIFF>,<TIME-
PERIOD>,<DEFAULT-TARIFF>,[<TARIFF-2>[,<TARIFF-
3>[,<TARIFF-4>[,<TARIFF-5>]]]]];
ACTION=1 : Delete Tariff Class
S40240:1,<TARIFF-CLASS>;
Assign, Change and Delete Local Domain Relation
S41000 : <ACTION>,<LOCAL-DOMAIN-ID>[,[<NUMBERING-PLAN>],<DNR/
ROUTE>[,<PARAM-1>,<PARAM-2>,<PARAM-3>]];
ACTION=0: Assign local domain data (CHLDOM)

S41000:0,<LOCAL-DOMAIN-ID>,<NUMBERING-PLAN>,
<PARAM-1>,<PARAM-2>,<PARAM-3>;
ACTION=1: Delete local domain data (ERLDOM)
S41000:1,<LOCAL-DOMAIN-ID>,<NUMBERING-PLAN>;
ACTION=3: Assign local domain ID to DNR (CHDNRL)
S41000:3,<LOCAL-DOMAIN-ID>,,<DNR>;
ACTION=4: Display local domain ID for DNR (DIDNRL)
273
S41000:4,<LOCAL-DOMAIN-ID>,,<DNR>;
ACTION=5: Assign local domain ID to route (CHRTLD)
S41000:5,<LOCAL-DOMAIN-ID>,,<ROUTE>;
ACTION=6: Display local domain ID for route (DIRTLD)
S41000:6,<LOCAL-DOMAIN-ID>,,<ROUTE>;
ACTION=7: Display DNRs for local domain ID
S41000:7,<LOCAL-DOMAIN-ID>;
ACTION=8: Display routes for local domain ID
S41000:8,<LOCAL-DOMAIN-ID>;
PARAM-1, 2 and 3 contain the data entered with CHLDOM separated by a '%' sign :
- PARAM-1 : Country-code % Area-code % DDI-prefix

- PARAM-2 : International-prefix % National-prefix % Trunk-access-code
- PARAM-3 : TON-CPN % TON-CLI % Ins-Tac-for-unk % Route-ins-tac
Local domain data is network data and as a consequence equal in all iSNET-MAN units.
The relations between DNR/route and Local domain ID's are local data in the unit the DNR/
route is located.
Change Location Determination Data
S41010 : <ACTION>,<NUMBERING-PLAN>,<TYPE-OF-NUMBER>,<ORIG-
DIGIT-STRING>[,<NEW-DIGIT-STRING>];
ACTION=0 : Change Location Data (CHLODD).

S41010:0,<NUMBERING-PLAN>,<TYPE-OF-NUMBER>,
<ORIG-DIGIT-STRING>,<NEW-DIGIT-STRING>;
ACTION=1 : Delete Location Data (CHLODD).
S41010:1,<NUMBERING-PLAN>,<TYPE-OF-NUMBER>,
<ORIG-DIGIT-STRING>;
Change Numbering Plan Conversion Data
S41020 : <ACTION>,<ORIG-NUMB-PLAN,<NEW-NUMB-PLAN>,<ORIG-
TON>,<ORIG-DIG-STRING>[,<NEW-TON>,<NEW-DIGIT-
274
STRING>];
ACTION=0 : Change Conversion Data (CHNPCD).

S41020:0,<ORIG-NUMB-PLAN,[<NEW-NUMB-PLAN>,<ORIG-
TON>,
<ORIG-DIG-STRING>,<NEW-TON>,<NEW-DIGIT-STRING>;
ACTION=1 : Delete Conversion Data (CHNPCD).
S41020:1,<ORIG-NUMB-PLAN,[<NEW-NUMB-PLAN>,<ORIG-
TON>,
<ORIG-DIG-STRING>;
Change and Read Answering Priority of A-Queue
S42000 : <OPERATOR-DNR>[,<NEW/NEXT>[,<A1...A16>][,<A1...A16>];
NEW/NEXT : If this is the first command string sent by OM command CHAQPR, then this
parameter has the value NEW (=0); if this is not the first string, then this
parameter has the value NEXT (=1).
A1 ... A16: This parameter string contains a maximum of 11 call types; at least one call
type must be filled in. Each call type must be given as a two digit number,
so types 0 ... 9 must have leading zeroes.
If NEW/NEXT = 1 and the number of call types is greater than 11, then the second
<A1...A16>parameter is available for the remaining call types.
See also OM command CHAQPR.
Change / Display Queue Lamp Relation
S42010 : <ACTION>[,<LAMP-ID>][,<INTERNAL-CALL-TYPE/A-QUEUE-
NUMBER>];
ACTION=0 : Display queue lamp relation (DIQLMR).

S42010:1[,<LAMP-ID>][,<INTERNAL-CALL-TYPE/A-QUEUE-
NUMBER>];
275
ACTION=1 : Change queue lamp relation (CHQLMR).
S42010:0,<LAMP-ID>,<INTERNAL-CALL-TYPE/A-QUEUE-
NUMBER>;
Change Answering Priority of M- or C- Queue
S42030 : <Q-TYPE>,<M1/C1>[,<M2/C2>[,<M3/C3>[,<C4C5C6C7C8>]]];
Q-TYPE : This parameter can be:

-4=C-queue;
-5=M-queue.
M1/C1 : This is the first call type; the parameter is mandatory.
M2/.../C3 : This is the second and third call type; the parameter is optional but M3/
C3 can only be entered when M2/C2 has been entered.
C4 ...C8 : Five call types, packed (only meaningful for C-queues).
See also OM commands CHMQPR and CHCQPR.
Display Answering Priority of M- or C- Queue
S42040 : <Q-TYPE>[,<OPERATOR-DNR>];
Q-TYPE : This parameter can be:

-4=C-queue;
-5=M-queue.
OM commands DIMQPR and DICQPR.
Display List of Active or Idle Operators
S42050 : <DTYPE>[,<ASSIST-GROUP>];
DTYPE : This parameter can be:

-0=active operator type;
-1=idle operator type.
276
OM commands DIOPAC and DIOPID.
Display Activity of Operator Continuously
S42060 : [<OPERATOR-DNR>];
OM command DIOPCT.
Display Status of Operator
S42070 : <OPERATOR-DNR>;
OM command DIOPST.
Change Trunk Access Code of B-Button
S42100 : <ACTION>,<B-BUTTON>[,<TRUNK-CODE>];
ACTION=0 : Display trunk access code B-button (DIBBUT).

S42100:0,<B-BUTTON>;
ACTION=1 : Change trunk access code B-button (CHBBUT).
S42100:1,<B-BUTTON>,<TRUNK-CODE>;
ACTION=2 : Delete trunk access code B-button (CHBBUT).
S42100:2,<B-BUTTON>[,<TRUNK-CODE>];
Change Operator Availability List
S42200 : <ACTION>,[<ASSIST-
GROUP>],[<U1U2U3U4U5>],[<U6U7U8U9U10U11U12U13>];
ACTION=0 : Assign operator availability list (CHOPAV).

S42200:0,[<ASSIST-
GROUP>][,<U1U2U3U4U5>],[<U6U7U8U9U10U11U12U13>];
ACTION=1 : Erase operator availability list (CHOPAV).
277
S42200:1,[<ASSIST-
GROUP>][,<U1U2U3U4U5>],[<U6U7U8U9U10U11U12U13>];
ACTION=2 : Display operator availability list (DIOPAV).
S42200:2,[<ASSIST-GROUP>];
U1 : This is the first unit; the parameter is mandatory for CHOPAV.

U2 ... U13 : This is the second, third, etc. unit number; the parameter is optional.
Each unit number must be given as a two digit number, so unit number 0
... 9 must have leading zeroes.
If the ASSIST-GROUP parameter is omitted the general assistance group is assumed.
Change Assistance Group of Operator
S42300 : <ACTION>,<OPERATOR-DNR>[,<ASSIST-GROUP>];
ACTION=0 : Assign assistance group of operator (CHASOP).

S42300:0,<OPERATOR-DNR>[,<ASSIST-GROUP>];
ACTION=1 : Erase assistance group of operator (CHASOP).
ACTION=2 : Display assistance group of operator (DIASOP).
Change Assistance Group to Compatibility Value Relation
S42310 : <ACTION>,<CV>[,<ASSIST-GROUP>];
ACTION=0 : Assign assistance group to CV relation (CHASCV).

S42310:0,<CV>[,<ASSIST-GROUP>];
ACTION=1 : Erase assistance group to CV relation (CHASCV).
ACTION=2 : Display assistance group to CV relation (DIASCV).
278
Display Load of Operator
S42320 : [<OPERATOR-DNR>];
OM command DIOPLD.
Change/Display Assistance Group Properties
S42400 : <ACTION>,[<ASSIST-GROUP>][,ASSIST-GROUP-PROPS,[LDN]];
If Parameter ASSIST-GROUP is not filled in, the General Assistance Group is assumed.
The layout of the <ASSIST-GROUP-PROPS>is :
- up to/including Call@Net 2.7 : <P>

- since Call@Net 2.8 : <P[Q]>
P = Operating monitoring (off = 0, on = 1).
Q = When in night, go to general assistance group before (specific) MCNE (off = 0, on = 1)
For both parameters, the default is 0.
ACTION=2 : Display Assistance Group Properties (DIASPR).

S42400:2,[<ASSIST-GROUP>];
ACTION=5 : Change Assistance Group Properties (CHASPR).
S42400:5,[<ASSIST-GROUP>][<ASSIST-GROUP-PROPS>,[LDN]];
Create / Display BSPT Definition
S43000 : <ACTION>,<BSPT>[,<IBSC>];
Parameter IBSC is not a number as it is in the OM command, but it is a string of 20 bits (IBSC
0 to 19) that can be 0 or 1. If a particular IBSC is included in the BSPT the corresponding bit
is set to 1; else it is 0.
ACTION=0 : Create BSPT Definition (CRBSPT).

S43000:0,<BSPT>,<IBSC>;
279
ACTION=2 : Display BSPT Definition (DIBSPT).
S43000:2,<BSPT>;
Perform Trunk Network Action
S45000 : <ACTION>,<DEST%ROUTE-TABLE/ROUTE>,[<TREE/UNIT],[<FST-
DT>],[<SND-DT>][,[<ACC-REP>][,NUMBERING-PLAN]];
ACTION=0 : Change destination network data (CHDSTC).

S45000:0,<DEST%ROUTE-TABLE>,<TREE>,<FST-DT>,<SND-
DT>,[<ACC-REP>],[NUMBERING-PLAN];
ACTION=1 : Add route location (CRROUT).
Perform Trunk Network Action - Delayed Seizure
S45010 : <DEST>,<DEL-SEIZ>;
This subcommand is an addition to subcommand S45000 (OM command CHDSTC).
Perform Trunk Service Action
S45020 : <ROUTE>,<ACTION>[,<ORIG-NUMBER>][,<CONV-MUMBER>];
ACTION=0 : Create route (CRROUT).

S45020:<ROUTE>,0;
ACTION=1: Erase route (ERROUT).
S45020:<ROUTE>,1;
ACTION=2 : Assign digit conversion (ASDGCV).
S45020:<ROUTE>,2[,<ORIG-NUMBER>][,<CONV-MUMBER>];
ACTION=3 : Erase digit conversion (ERDGCV).
S45020:<ROUTE>,3;
ACTION=4 : Check space in local route table.
S45020:<ROUTE>,4;
ACTION=5 : Check erase allowance.
S45020:<ROUTE>,5;
280
Change Route Characteristics General
S45030 : <ROUTE>,<GEN-OPTS>,<GEN-TONE>[[,<CV>][,<BSPT>]][,CC-
TABLE];
OM command CHRTCG.
Change Route Characteristics Incoming
S45040 : <ROUTE>,<INC-OPTS>,<TONE-AND-DDI-
OPTS>[,[<TREE>][,[<A-QUEUE>][,<BSPT>]]];
OM command CHRTCI.
Change Route Characteristics Outgoing
S45050 : <ROUTE>,<OUT-OPTS>,<ATF>[,<BSPT>];
OM command CHRTCO.
Change Bundle Characteristics
S45060 : <BUNDLE>,<DIR-AND-NEG>,<OPTIONS>,<CON-AND-SIGN-
TYPE>[[,<ALL-CALLS>][,BSPT>]];
OM command CHBNDC.
Allocate or De-allocate Bundle to or from Route
S45070 : <ACTION>,<ROUTE>,<BUNDLE>;
ACTION=0 : Assign bundle to route (ASBNDL).

S45070:0,<ROUTE>,<BUNDLE>;
ACTION=1 : Delete bundle from route (DEBNDL).
S45070:1,<ROUTE>,<BUNDLE>;
281
Assign Line to Bundle
S45080 : <ACTION>,[<BUNDLE>],[LINE>],<SHELF%BRD%CRT>[,<B-
CHANNEL>];
ACTION=0 : Assign line to bundle (ASLINE).

S45080:0,<BUNDLE>,<LINE>,<SHELF%BRD%CRT>[,<B-
CHANNEL>];
ACTION=1 : Delete line from bundle (DELINE).
S45080:1,,,<SHELF%BRD%CRT>[,<B-CHANNEL>];
Display Destination Data
S45100 : <DEST>;
OM command DIDEST.
Display Route / Bundle / Line Data
S45110 : <ACTION>,[<ROUTE/BUNDLE>][,[<SHELF%BRD%CRT>][,[<B-
CHANNEL>][,[,<BSPT>]]]];
ACTION=0 : Display route data (DIROUT).

S45110:0,<ROUTE>[,,,,<BSPT>];
ACTION=1 : Display bundle data (DIBNDL).
S45110:1,<BUNDLE>[,,,,<BSPT>];
ACTION=2 : Display line data (DILINE).
S45110:2,,<SHELF%BRD%CRT>[,<B-CHANNEL>];
282
Change Bundle-DTU Relation
S45120 : <ACTION>,<BUNDLE>[,<SHELF>,<BRD>];
ACTION=0 : Assign bundle to DTU (CHBDTU).

S45120:0,<BUNDLE>,<SHELF>,<BRD>;
ACTION=1 : Delete bundle from DTU (CHBDTU).
S45120:1,<BUNDLE>;
ACTION=2 : Display bundle DTU relation (DIBDTU).
S45120:2,<BUNDLE>;
Change Route-BSPT Relation
S45130 : <ACTION>,<ROUTE>[,<BSPT>];
ACTION=0 : Assign route-BSPT relation (ASBSPR).

S45130:0,<ROUTE>,<BSPT>;
ACTION=1 : Erase route-BSPT relation (ERBSPR).
S45130:1,<ROUTE>,<BSPT>;
ACTION=2 : Display route-BSPT relation (DIBSPR).
S45130:2,<ROUTE>;
Change Bundle-BSPT Relation
S45140 : <ACTION>,<BUNDLE>[,<BSPT>];
ACTION=0 : Assign bundle-BSPT relation (ASBSPB).

S45140:0,<BUNDLE>,<BSPT>;
ACTION=1 : Erase bundle-BSPT relation (ERBSPB).
S45140:1,<BUNDLE>,<BSPT>;
ACTION=2 : Display bundle-BSPT relation (DIBSPB).
S45140:2,<BUNDLE>;
283
Change (B-) Channel Dedication
S45150 : <DED-TYPE>,<SHELF>,<BRD>,<CRT>,<BCH-VALUE>;
OM command CHCDED.
Display (ISDN) Trunk Circuit
OM command DITCRT.
Assign, Erase and Display Digit Conversion on an Outgoing Route
S45170 : <ROUTE&ACTION>[,[<DEST>][,[<ORIG-NUMBER>][,[<CONV-
NUMBER>][,<DIALTONE-PLACE>]]]];
ACTION=0 : Assign digit conversion on an outgoing route (ASDGCO).

S45170:<ROUTE>0,<DEST>,<ORIG-NUMBER>,<CONV-
NUMBER>,<DIALTONE-PLACE>;
ACTION= : Erase digit conversion on an outgoing route (ERDGCO).
S45170:<ROUTE>1,[<DEST>],<ORIG-NUMBER>;
ACTION=2 : Display digit conversion on an outgoing route (DIDGCO).
S45170:<ROUTE>2[,[<DEST>][,[<ORIG-NUMBER>]]];
Validate before ASBNDL / CHBNDC
S45180 : [<ROUTE>],<BUNDLE>[,<SIGN-TYPE>];
OM command ASBNDL.
If <SIGN-TYPE>is omitted, then <ROUTE>must be entered.
284
Set / Reset Route Type
S45190 : <ROUTE>,<ROUTE-TYPE>;
ROUTE-TYPE : 0 = route is non-DPNSS and non-QSIG

1 = route is a DPNSS route
2 = route is a QSIG route
OM command ASBNDL.
Change Inter Unit Bundle Data (CCS)
S45200 : <BUNDLE>[,[<DIR>][,<ROUTE>]];
Change inter unit bundle characteristics (CHIBNC).
S45200:<BUNDLE>,<DIR>;
Assign bundle to an inter unit route (ASIBND).
S45200:<BUNDLE>,,<ROUTE>;
Delete bundle from the interunit route (DEIBND).
S45200:<BUNDLE>;
Change Inter Unit Line Data (CCS)
S45210 : <SHELF>,<BRD>,<CRT>,[<BUNDLE>];
Assign line to inter unit bundle (ASILIN).
S45210:<SHELF>,<BRD>,<CRT>,<BUNDLE>;
Delete line from inter unit bundle (DEILIN).
285
Assign, Change, Delete PVN Data
S45230 : <ACTION>[,<PAR-1>[,<PAR-2>[,<PAR-3>[,<PAR-4>[,<PAR-
5>]]]]];
This subcommand is used for all OM commands for PVN, except display. Display PVN data
uses subcommand S45250. By means of the parameter Action, the distinction is made
between the various OM commands.
ACTION=1 : Change PVN route data part 1 (CHPVNR).

S45230:1,<ROUTE>,<M/S>,<SIGCH-ADDRESS>,<RIN>,<TREE>;
ACTION=2 : Change PVN route data part 2 (CHPVNR).
S45230:2,<ROUTE>,<UCA-PREFIX>,<PVN-MODE>,<CV>;
ACTION=3 : Delete PVN route data (CHPVNR).
S45230:3,<ROUTE>;
ACTION=5 : Assign PVN User Channel Address (UCA) data (ASPVNU).
S45230:5,<UCA-PREFIX>;
ACTION=6 : Delete PVN User Channel Address (UCA) data (DEPVNU).
S45230:6,<UCA-PREFIX>;
ACTION=8 : Change PVN sequence table data (CHPVNT).
S45230:8,<ROUTE>,<SEQUENCE-TABLE>,<SIGCH-
INFO>,<USRCH-INFO>;
SIGCH-INFO is the information of the following parameters in the
CHPVNT command, where SIGCH-INFO = SIGCH-TV x 10 + SIGCH-
TU :
- SIGCH-TU = Signalling channel timer unit
- SIGCH-TV = Signalling channel timer value
USRCH-INFO is the information of the following parameters in the
CHPVNT command, where USRCH-INFO = USRCH-TV x 10 + USRCH-
TU :
- USRCH-TU = User channel timer unit
- USRCH-TV = User channel timer value
ACTION=9 : Change PVN security information (CHPVNS).
S45230:9,[<SECURITY-CODE>],<PTN-ID>;
PTN-ID is the Private Telecommunication Network Identifier. This is a
number in the range 0...9999. This number is used to verify that both
parties belong to the same network
If <SECURITY-CODE> is omitted, then the default security code is
stored.
286
ACTION=11 : Change PVN compressor DNR
S45230:11,<DNR>;
Change Fixed Trunk Line Destination
S45240 : <SHELF>,<BRD>,<CRT>,<DEST-NUMBER>,<IDENT-NUMBER>;
Display PVN Data
S45250 : <ACTION>[,<PAR-1>[,<PAR-2>]];
This subcommand is used for all 'display' OM commands for PVN. By means of the parameter
Action, the distinction is made between the various OM commands : DIPVND, DIPVNR,
DIPVNT and DIPVNU.
ACTION=0 : Display PVN route data (DIPVNR).

S45250:0,<ROUTE>,<UNIT>;
ACTION=4 : Display PVN User Channel Address (UCA) data (DIPVNU).
S45250:4;
ACTION=7 : Display PVN sequence table data (DIPVNT).
S45250:7,<ROUTE>,<SEQUENCE-TABLE>;
ACTION=12 : Display PVN compressor DNR (DIPVND)
S45250:12;
Change Route Relation (CCS)
S45300 : <ROUTE-ALTERN>,<ORIG-UNIT>,<FAR-DEST>,<IU-
ROUTE>,<NEAR-DEST>;
OM commands CHRORE and CHUNRE.
287
Display Unit and Route Relation (CCS)
S45310 : <ROUTE-ALTERN>,<ORIG-UNIT>;
OM command DIURRE.
Display Route Table
S45400 : <ROUTE>,<SEQUENCE-TABLE>;
OM command DIROTA.
Change Route Table
S45410 : <ROUTE-TABLE>,[<USER-TYPE>],<SEQUENCE-TABLE>,<TABLE-
INDEX>[,<ROUTE%PREF-CODE>,<TRFC>%[SMART-BOX-EM]>];
OM command CHROTA.
Change Compatibility Value-assistance Point Relation
S45420 : <CV>[,<ASSISTANCE-POINT>[,<LOCAL OPERATOR MARK>]];
OM command CHCVAP.
Display Compatibility Value-assistance Point Relation
S45430 : [<CV>];
OM command DICVAP.
Change and Display CLI or COL Translation Table
S45500 : <ACTION>,<CC-TABLE>[,<ORIG-CC-STRING>[,[<DEST-CC-
288
STRING>]]];
ACTION=0 : Change entry in CC table (CHCCTR).

S45500:0,<CC-TABLE>,<ORIG-CC-STRING>,<DEST-CC-STRING>;
ACTION=1 : Delete entry in CC table (CHCCTR)
S45500:1,<CC-TABLE>,<ORIG-CC-STRING>;
ACTION=2 : Display CC table/route relations (DICCTR and DICCRT).
S45500:2,<CC-TABLE>,<ORIG-CC-STRING>;
Change CLI/COL Identity of a Trunk Line or Virtual Line
S45510 : <ACTION>,<LINE>[,<CLI/COL-STRING>];
ACTION=0 : Assign CLI/COL Identity of a Trunk Line (CHCCLI).

S45510:0,<LINE>,<CLI/COL-STRING>;
ACTION=1 : Delete CLI/COL Identity of a Trunk Line (CHCCLI).
S45510:1,<LINE>;
ACTION=2 : Display CLI/COL Identity of a Trunk Line (DICCLI).
S45510:2,<LINE>,<CLI/COL-STRING>;
Change and Display QSIG Facility Selection Method
S45600 : <ACTION>,<QSIG-FACILITY>[,<PROPRIETARY-OR-QSIG>];
ACTION=0 : Change and QSIG Facility Selection Method (CHQFSM).

S45600:0,<QSIG-FACILITY>,<PROPRIETARY-OR-QSIG>;
ACTION=1 : Display QSIG Facility Selection Method (DIQFSM).
S45600:1,<QSIG-FACILITY>;
Perform Action on Paging Area or Paging Route
S46000 : <ACTION>[,[<AREA>]][,[<UNIT/
289
ROUTE>]][,[<MIN>],[<MAX>]][,<PAGING-CODE>];
ACTION=1 : Read paging answering area (DIPARE).

S46000:1;
ACTION=2 : Check if member unit of area (DIPARE).
S46000:2,<AREA>;
ACTION=3 : Create paging area (CRPARE).
S46000:3,<AREA>,<UNIT>;
ACTION=4 : Define paging answering area (CHPARE).
S46000:4[,<AREA>];
ACTION=5 : Delete member unit from paging area (ERPARE).
S46000:5,<AREA>;
ACTION=6 : Erase paging area (ERPARE).
S46000:6,<AREA>;
ACTION=7 : Check paging code assigned to area.
S46000:7,,,,,<PAGING-CODE>;
ACTION=8 : Create paging route at network level (CRPART).
S46000:8,<AREA>,<ROUTE>[,<MIN>,<MAX>];
ACTION=9 : Erase paging route at network level (ERPART).
S46000:9,,<ROUTE>;
ACTION=10: Change real paging route number length (CHPANL).
S46000:10,,<ROUTE>,<MIN>,<MAX>;
Perform Action on Paging Route
S46010 : <ACTION>,[<ROUTE>],[<REAL-TYPE%MD-TYPE>],[<DIGIT-
INT>],[<DIGIT-EXT>],[DIGIT-ASS];
ACTION=1 : Check space to add route.

S46010:1,<ROUTE>;
ACTION=2 : Create paging route at local level (CRPART).
S46010:2,<ROUTE>,<REAL-TYPE>;
The possible values of <REAL-TYPE>are (not the same as in the OM
command):
0 = virtual paging
1 = real paging
ACTION=3 : Check route empty
290
S46010:3,<ROUTE>;
ACTION=4 : Change paging route mode digits (CHPAMD).
S46010:4,<ROUTE>,<REAL-TYPE%MD-TYPE>,[<DIGIT-
INT>],[<DIGIT-EXT>],[<DIGIT-ASS>];
The possible values of <REAL-TYPE>are (not the same as in the OM
command):
0 = virtual paging
1 = real paging
ACTION=5 : Erase paging route at local level (ERPART).
S46010:5,<ROUTE>;
ACTION=6 : Read paging route type (DIPARE).
S46010:6,<ROUTE>;
ACTION=7 : Determine next paging route and read type.
S46010:7,[<ROUTE>];
Perform Action on Paging Resource
S46020 : <ACTION>,<ROUTE>,[<SHELF>],[<BRD>],[<CRT>][,<PAGING-
CODE>];
ACTION=1 : Assign paging code to virtual route (ASPACD).

S46020:1,<ROUTE>,,,,<PAGING-CODE>;
ACTION=2 : Check delete code allowance.
ACTION=3 : Delete code from paging route (DEPACD).
ACTION=4 : Assign paging line to real route (ASPALN).
S46020:4,<ROUTE>,<SHELF>,<BRD>,<CRT>;
ACTION=5 : Check delete paging line allowance.
ACTION=6 : Delete line from paging route (DEPALN).
ACTION=7 : Display paging line data (DIPALN).
291
Display Paging Route Data
S46030 : <ROUTE>;
OM command DIPART.
Test the Alarm Equipment
S50100 : <UNIT>;
OM command TSALRM.
Insert Manual Test Request
S50200 : <ACTION>[,[<SHELF>][,[<BRD>][,[<CRT>][,<REP-
FACTOR>]]]];
ACTION=0: Insert resource into test request list (INTEST).

S50200: 0[,[<SHELF>][,[<BRD>][,[<CRT>][,<REP-FACTOR>]]]];
ACTION=1: Delete resource from test request list (DETEST).
S50200:1[,[<SHELF>][,[<BRD>][,[<CRT>]]]];
ACTION=2: Display manual test request (DITEST).
S50200:2[,[<SHELF>][,[<BRD>][,[<CRT>]]]];
Create Directed Calls
S50300 : <ORIG-SHELF>,<ORIG-BRD>,<ORIG-CRT>,<DEST-
SHELF>,<DEST-BRD>,<DEST-CRT>;
OM command ASDICA.
292
Delete Directed Calls
S50301 : <ORIG-SHELF>,<ORIG-BRD>,<ORIG-CRT>[,<DEST-
SHELF>,<DEST-BRD>,<DEST-CRT>];
OM command DEDICA.
Display Resources Used by Directed Calls
S50302 : [<ORIG-SHELF>,<ORIG-BRD>,<ORIG-CRT>];
OM command DIDICA.
Change Periodic Autonomous Test (PAT) Mode
S50500 : <ACTION>[,<RESOURCE-TYPE>];
ACTION=0: Periodic Autonomous Test in normal mode (CHPATM).

S50500:0;
ACTION=1: Periodic Autonomous Test in installation mode (CHPATM).
S50500:1;
ACTION=2: Display cyclic counter of specified resource type (DIPATC).
S50500:2,<RESOURCE-TYPE>;
ACTION=3: Clear cyclic counter (CLPATC).
S50500:3;
Perform Action on Diagnostical System Data
S51000 : <ACTION>,[<LDN>];
ACTION=0: Erase system dump data (ERSYSD).

S51000:0,;
ACTION=1: Start dumping system dump data (DUSYSD).
S51000:1,<LDN>;
293
Perform Action for Change System Dump Data
S51010 : <DUMP>,<AUTO>;
OM command CHSYSD.
Perform Action for Display System Dump Information
S51020 : ;
OM command DISYSD.
Set Up Controlled Connection
S55000 : <SHELF%BRD%[CRT]>,[<B-
CHANNEL>],[<X>],<SHELF%BRD%CRT>,[<B-
CHANNEL>],<[X]%P>;
[X]%P includes the circuit number of the destination port and a parameter S or P:
- S indicates a single path (OM command CRCCSP);

- P indicates a paired path (OM command CRCCPP).
Manage Controlled Connection
S55010 : <ACTION>,<COCO-NUMBER>[,<TONE-FUNCTION/DIGIT/
FREQUENCY>];
ACTION=0: Display controlled connection (DICOCO).

S55010:0,<COCO-NUMBER>;
ACTION=1: Erase controlled connection (ERCOCO).
ACTION=2: Start controlled connection tone (SECCTO).
S55010:2,<COCO-NUMBER>,<TONE-FUNCTION>;
ACTION=3: Stop controlled connection tone (SECCTO).
294
ACTION=4: Send controlled connection digit (SECCDI).
S55010:4,<COCO-NUMBER>,<DIGIT>;
ACTION=5: Received controlled connection digits (DICCDI).
ACTION=6: Send controlled connection frequency (SECCDI).
S55010:6,<COCO-NUMBER>,<FREQUENCY>;
ACTION=7: Send controlled connection digit pulsed (SECCDI).
S55010:7,<COCO-NUMBER>,<DIGIT>;
Display History Buffer
S60230 : <REPORT-TYPE>;
Display major alarms (DIMAJA).
S60230:15;
Display minor alarms (DIMINA).
S60230:14;
Display silent alarms (DISILA).
S60230:13;
Display blocked alarms (DIBLCK).
S60230:11;
Display history buffer (DIHIBU).
S60230:<REPORT-TYPE>;
Reroute Alarm Signalling
S60260 : <ROUTE-TYPE>;
OM command REROUT.
295
Digital Line Alarms
S60270 : <SHELF>,<BRD>,[<CRT>],<MODE>,<COUNTER>;
COUNTER=0: Display digital line alarms (DIDILA);

S60270:<SHELF>,<BRD>,[<CRT>],<MODE>,0;
COUNTER=1: Erase digital line alarm counters (ERDILA).
S60270:<SHELF>,<BRD>,[<CRT>],<MODE>,1;
Display and Erase CTA Alarms
S60280 : <ACTION>[,<BSP-ID>][,<SHELF>,<BRD>];
ACTION=0 Display CTA alarms (DICTAA).

S60280: 0[,<SHELF>,<BRD>];
ACTION=1 Erase CTA alarms (ERCTAA).
S60280: 1,<BSP-ID>;
Clear Alarm Buffers
S60290 : <UNIT>;
UNIT=0: Own unit;
UNIT=1: All units
OM command CLALRM.
Change Announcement on Incoming Trunks
S65000 : <ANN-SELECTION>,[<ANN-NO>],[<ASSIST-GROUP>][,<ANN-
CHANGE-ADD-INFO>];
OM command CHANNO.
The contents of parameter ANN-CHANGE-ADD-INFO varies with parameter ANN-
296
SELECTION:
0= DDI fail calls

S65000: 0,[<ANN-NO>],[<ASSIST-GROUP>],<ANN-DDI-FAIL-OPTION>;
1= Successful DDI calls
S65000: 1,[<ANN-NO>],[<ASSIST-GROUP>];
2= Non-DDI calls
S65000: 2,[<ANN-NO>],[<ASSIST-GROUP>];
3= Calls to operator A-queue
S65000: 3,[<ANN-NO>],[<ASSIST-GROUP>],<A-QUEUE>;
7= Music on hold
S65000: 7,[<ANN-NO>],;
Change Announcement Information for ACD
S65010 : <ANN-SELECTION>,[<ANN-NO>],[<GROUP-DNR>],<ANN-CHANGE-
ADD-INFO>;
OM command CHANNO.
The contents of parameter ANN-CHANGE-ADD-INFO varies with parameter ANN-

SELECTION:
4= Station Call Announcement

S65010:4,[<ANN-NO>],<GROUP-DNR>,[<1ST-ANN-DELAY-TIME>];
5= Night Service Announcement
S65010:5,[<ANN-NO>],<GROUP-DNR>,[<1ST-ANN-DELAY-TIME>];
6= Delay message
S65010:6,[<ANN-NO>],<GROUP-DNR>,[<DELAY-MESS-PRE-
TIME>],[<DELAY-MESS-REPEAT-TIME>],[<QUEUE-POSITION>];
Display Announcement Information for ACD
S65015 : <1>,<GROUP-DNR>;
OM command DIANNO.
297
Set Circuit Conditions
S70100 : <ACTION>,<SHELF>[,<BRD>][,<CRT>];
ACTION=0: Set circuit condition INS (SETINS).

ACTION=1: Set circuit condition OUT (SETOUT).
ACTION=2: Set circuit condition NIN (SETNIN).
ACTION=3: Force circuit condition OUT (FRCOUT).
Get Resource Degradation Level
S70110 : <SHELF>[,[<BRD>][,<CRT>]];
This subcommand performs a validation on the EHWA.
Display Service Condition
S70300 : <SHELF>[,[<BRD>][,<CRT>][,<B-CHANNEL>]];
OM command DISERV.
Find Resource with given Circuit Condition
S70310 : <CONDITION>,<COMMAND-TYPE>;
OM command FISERV.
COMMAND-TYPE can be: 0=MML command;

1=Operator desk command.
298
Display Service Condition of Virtual Channel
OM command DIVICH.
Display CPU Slice Mask Status (CCS)
S70330 : ;
OM command DICCSS.
Read or Change Night Extension Marks
S36101 : <BSP-ID>,<TYPE>,<ACTION>;
ACTION=1 : Check special extension;

ACTION=2 : Set special extension;
ACTION=3 : Reset special extension;
ACTION=4 : Set prohibit absence mark;
ACTION=5 : Reset prohibit absence mark.
TYPE is the same as for S36100.
Set and Display Unit Status (CCS)
S70400 : <ACTION>,[<UNIT>];
ACTION=0: Display unit status (DIUNIT).

S70400:0,<UNIT>;
Action 0 (display unit status) should never be used in an LL file.
ACTION=1: Set unit status installed (UNIINS).
S70400:1,<UNIT>;
ACTION=2: Set unit status not installed (UNININ).
S70400:2,<UNIT>;
299
Change and Display Peripheral Data Output Device
S75000 : <ACTION>[,<LDN>];
ACTION=0 Change Peripheral Data Output Device (CHPDOD).

S75000: 0,<LDN>;
ACTION=1 Display Peripheral Data Output Device (DIPDOD).
S75000: 1,<LDN>;
Change and Display Peripheral Data File Status
S75010 : <ACTION>[,<TASK>[,<RENAME-AND-REOPEN>]];
ACTION=0 Change peripheral data file status (CHPDFS).

S75010: 0,<TASK>,<RENAME-AND-REOPEN>;
ACTION=1 Display peripheral data file status (DIPDFS).
S75010: 1,<TASK>,<RENAME-AND-REOPEN>;
Start, Stop and Display Peripheral Circuit Trace
S75020 : <ACTION>,<SHELF%BRD>,<FILE-NAME[.EXT]>,<MAX-FILE-
SIZE%STOP-AT-MAX-FILE-SIZE>,<CRT-0-UPTO-AND-
INCLUDING-15>,<CRT-16-UPTO-AND-INCLUDING-31>;
ACTION=0 Start the PPH protocol trace application and save already available data
(STRTPT)
S75020: 0,<SHELF%BRD>,<FILE-NAME[.EXT]>,<MAX-FILE-
ACTION=1 Start the PPH protocol trace application and data already available is lost
(STRTPT)
S75020: 1,<SHELF%BRD>,<FILE-NAME[.EXT]>,<MAX-FILE-
ACTION=2 Stop peripheral circuit trace (STOPPT)
300
S75020: 2,<SHELF%BRD>;
ACTION=3 Display peripheral circuit trace (DIPCRT)
ACTION=4 Verify if the application can be started
Handle Overlay Modules
S80000 : <ACTION>[,<OVERLAY-ID>];
ACTION=0: Load overlay module (LDOVLM).

S80000:0,<OVERLAY-ID>;
ACTION=1: Delete overlay module (DEOVLM).
S80000:1 ,<OVERLAY-ID>;
ACTION=2: Display overlay module (DIOVLM).
S80000:2[,<OVERLAY-ID>];
ACTION=3: Set overlay module protection (SEOVLM).
ACTION=4: Reset overlay module protection (REOVLM).
(from Call@Net 2.4 only OM command DIOVLM exists).
Validation subcommand for ACTUPD (CCS)
S81100 : ;
Execution subcommand for ACTUPD (CCS)
S81110 : ;
301
System Starts
S81500 : <START-TYPE>,<SUB-START-TYPE>;
START-TYPE can be : 0=reload (OM command STLOAD)

1=reproject (OM command STPROJ)
3=cold start (OM command STCOLD)
4=warm start (OM command STWARM)
SUB-START-TYPE is not valid for START-TYPE 3.
It can be : 0=no hot start
1=hot start
Dual Mode System Starts (CCS)
S81530 : <ACTION>,<START-TYPE>,<SUB-START-TYPE>;
ACTION=0: Start dual mode for a unit (STDUAL)

S81530: 0,<START-TYPE>,<SUB-START-TYPE>;
ACTION=1: Stop dual mode for a unit (SPDUAL)
ACTION=2: Swap cluster status: from operational to stand-by or vice versa, for a unit
(SWDUAL)
Refer to S81500 for explanation of <START-TYPE>and <SUB-START-TYPE>
Validate the UPDUAL request in each unit (CCS)
S81540 : <UPDATE START>,<HOTSTART>;
Refer to UPDUAL in section 2.4.14. UPDUAL.
302
Initiate reconfiguration/activation stage in each unit (CCS)
S81550 : <UPDATE START>,<HOTSTART>,<ACTIVATE>;
<UPDATE START>and <HOTSTART>: refer to UPDUAL in section 2.4.16.
ACTIVATE : 0 = activate reconfiguration phase;

1 = initiate recvonfiguration phase;
2 = abort UPDUAL process.
Start and Stop Maintenance Mode (CPU3000 only)
S81560 : <ACTION>,<START-TYPE/FALL-BACK>,<HOTSTART>,<GUARDING-
TIME>;
ACTION=0 Start maintenance mode (STMAIN).

S81560: 0,<START-TYPE>,<HOTSTART>,<GUARDING-TIME>;
ACTION=1 Stop maintenance mode (SPMAIN).
S81560: 1,<FALL-BACK>;
Start Load Boot Program (CPU3000 only)
S81600 : <NEW-PACK>;
OM command STLOBP.
Generate Back-up in Memory Image Snapshot
S83000 : <LOCAL-OR-NETWORK-SIN>;
OM command GEBUMI.
303
Validate before making MIS-file or Retrieve-file
S83001 : <ACTION>;
ACTION=0: Validate (GEBUMI).

S83001:0;
ACTION=1: Validate (RTRIEV)
S83001:1;
Set Network Compatible (CCS)
S83002 : <ACTION>,<CBU-EXEC>;
ACTION=0: Set network compatible (CHCOMP).

S83002:0;
ACTION=1: Set network incompatible (CHCOMP).
S83002:1;
CBU-EXEC=0: CBU execution
CBU-EXEC=1: Non CBU execution
Display Network Compatibility (CCS)
S83003 : [<UNIT>];
OM command DICOMP.
Generate Back-up in Logical Format (first part)
S83005 : <DATA-TYPE>;
The DATA-TYPE parameter can be 0, 1, ..., 10 and 27; see Table 4-1 Parameter DATA-TYPE.
OM command RTRIEV.
304
DATA- MEANING DATA- MEANING
TYPE TYPE
0 All data. 16 Operator console data.
1 PE data. 17 Paging data.
2 LL data. 18 Night traffic data.
3 Network data. 19 Data functions data.
4 Overlay data. 20 Toll ticketing data.
5 Hardware configuration data. 21 Traffic measurement data.
6 Inter unit trunk data. 22 Facility timing data.
7 Inter unit routing data. 23 TMS data.
8 Restriction levels data. 24 Passwords.
9 Trunk data. 25 General cancel data.
10 Number analysis data. 26 System dump data.
11 DNR data. 27 Non changeable by OM.
12 Function keys and menus. 28 Announcement data
13 Group arrangements. 29 Remote Maintenance data
(CPU3000 only)
14 Executive secretary data. 30 PSW data
15 Abbreviated numbers. 31 PID/CC data
Table 4-1 Parameter DATA-TYPE
Generate Back-up in Logical Format (second part)
S83006 : <DATA-TYPE>;
The DATA-TYPE parameter can be 0, 2, 3, 11, 12, ..., 26, 28, 29, 30, 31; see Table 4-1
Parameter DATA-TYPE.
OM command RTRIEV.
305
Submit Batch File Execution
S85030 : <JOB>,<DATE-AND-TIME>,<AUTHORITY>,<PROTECTION>,<LDN>;
OM command SUBJOB.
Perform Test to find out if Device is a Back-up Device
S85040 : <LDN>;
OM command INIDSK.
Display Batch File Execution
S85010 : [<JOB>];
OM command DISJOB.
Command File Execution
S85020 : <ACTION>,<JOB>;
Cancel command file execution (CANJOB).
S85020:C,<JOB>;
Suspend command file execution (SUSJOB).
S85020:S,<JOB>;
Resume command file execution (RESJOB).
S85020:R,<JOB>;
306
Submit Batch File Execution
S85030 : <JOB>,<DATE-AND-TIME>,<AUTHORITY>,<PROTECTION>,<LDN>;
OM command SUBJOB.
Perform Test to find out if Device is a Back-up Device
S85040 : <LDN>;
OM command INIDSK.
Assign Remote Maintenance Configuration Data from Projecting File (CPU3000

only)
S86001 : <ACTION>,[<SUBSCRIBER-OR-HAYES-STRING-NR>],[<REMOTE-
USER-GROUP>],[DATA-PART>],<PARAM-5>[,<PARAM-6>];
OM command CHREMC.
This subcommand is only used (via OM-command RTRIEV) in projecting files.
ACTION may have the following values:

0 = assign password and connection parameter
1 = assign system identification part
2 = assign calling station identification part
3 = assign a subscriber number part
4 = assign a Hayes initiation string part.
SUBSCRIBER-OR- indicates the number of either a subscriber or a Hayes initiation string.

HAYES-STRING-NR Possible values are:
0 ... 9 = subscriber number
0 ... 1 = Hayes initiation string.
REMOTE-USER- indicates the remote user group for which the ACTION must be
GROUP performed:
0 = user group 0
1 = user group 1.
307
DATA-PART The maximum size of a subcommand is 50 characters. A number of
remote maintenance configuration data have a size bigger then the
maximum capacity of a subcommand. In this case a mechanism should
be defined in order to divide data in smaller pieces which fit into a
number of subcommands. The parameter DATA_PART indicates the
order of the data blocks and can have the following values:
0 = the first data block which is characters 1... 15;
1 = the second data block which is characters 16...30
2 = the third data block which is characters 31...40.
If it is not necessary to divide the data then DATA_PART may be
omitted.
PARAM-5 and These two parameters contain the data that must be assigned. For a
PARAM-6: number of actions, ASCII values are used to store string information.
This is done for the following reasons:
1. Original data might contain ";" and/or ":". OM-basic will use
these characters as separators for parameter and subcommand
string;
2. When a retrieve file is processed, by iS3000-convert,
automatically characters are converted to uppercase. This
should be avoided.
In order to clarify the idea, we give an example:
Original data: "This is a string"
Hexadecimal value: "54686973206973206120737472696E67"
The maximum size of a parameter in a subcommand is 20 characters.
Consequently using the above example, PARAM-5 and PARAM-6
become:
PARAM-5: 54686973206973206120
PARAM-6: 737472696E67.
The value of action defines the value of PARAM-5 and PARAM-6.
ACTION = 0 REMOTE_USER_GROUP = 0...1

PARAM-5 = ASCII-format of password which is scrambled (max. 12
characters)
PARAM-6 = connection parameters (= number of invalid connect
attempts %, connection set-up command %, number of retries %,
time intervals between retries).
308
ACTION = 1 REMOTE_USER_GROUP = 0..1
DATA_PART = 0
PARAM-5 = ASCII-format of characters 1...10 of system
identification (max. 20 characters)
DATA_PART = 1
ACTION = 2 REMOTE_USER_GROUP = 0...1

DATA_PART = 0
PARAM-5 = ASCII-format of characters 1...10 of calling station
DATA_PART = 1
ACTION = 3 SUBSCRIBER_OR_HAYES_STRING_NR = 0..9

REMOTE_USER_GROUP = 0..1
DATA_PART = 0
PARAM-5 = ASCII-format of characters 1..10 of subscriber
number (max. 20 characters)
DATA_PART = 1
ACTION = 4 SUBSCRIBER_OR_HAYES_STRING_NR = 0..9

DATA_PART = 0
PARAM-5 = ASCII-format of characters 1...10 of Hayes
initiation string (max. 20 characters)
DATA_PART = 1
309
DATA_PART = 2
EXECUTION This subcommand assigns the remote maintenance configuration by

writing the data in RDSP. Each execution can result to one of the
following:
- EXECUTION_COMPLETED: action is terminated normally, no
errors;
- FATAL_EXECUTION_ERROR: action causes an unrecoverable
error. This happens when:
1. PARAM-6 is used though it is not expected;
2. Input parameters are out of range. For example, ACTION =
5 or USER_GROUP = 2 are out of range;
3. The combination of input parameters is incorrect. For
example, ACTION = 0 has no DATA_PART;
4. The conversion of ASCII-format to character-format fails. For
example, because the length of ASCII-format string is odd or the
ASCII-values are out of valid input character range.
Change or Display Remote Logging Output Device
S86010 : <ACTION>[,<LDN>];
Change remote logging output device CHRLOD.
S86010:0[,<LDN>];
Display remote logging output device DIRLOD.
S86010:2;
310
Start, Stop or Display Remote Logging Output/Status
S86020 : <ACTION>[,<FILE_NAME>;
Start remote logging status STRTRL.
S86020:0,<FILE_NAME>;
Stop remote logging status STOPRL.
S86020:1;
Display remote logging status DISPRL.
S86020:2;
Set Unit Boundaries and System Parameter
S92100 : <INDEX>[,<VALUE>];
For the INDEX and VALUE parameters, see chapter 3. BOUNDARIES, OPTIONS AND
TIMERS.
Example: S92100:59,10; means that the maximum number of routes is 10.
Display Manager Data
S92120 : <MANAGER-TYPE>[,<MANAGER-INDEX>];
OM command DIMDAT.
311
Display MFC Manager Data
S92130 : <MFC-TYPE>,<MFC-INDEX>,<ADD-INDEX>;
Display MFC Manager Data for MFC-TYPE 0 ... 3; OM command DIMMFC.
Display MFC Manager Data
S92140 : <MFC-TYPE>,<MFC-INDEX>,<ADD-INDEX>;
Display MFC Manager Data for MFC-TYPE 4 & 5; OM command DIMMFC.
Set System Options
S92200 : <INDEX>,<VALUE>;
INDEX : See chapter 3. BOUNDARIES, OPTIONS AND TIMERS.

VALUE : 1=yes; 0=no.
Example : Suppose `shuttle with forced release' is applied; then the subcommand is:
S92200:7,1;
Set System Timers
S92230 : <INDEX>,<UNIT-T>,<TIME-VALUE>;
INDEX : See chapter 3. BOUNDARIES, OPTIONS AND TIMERS.

UNIT-T : 0 = seconds, 1 = minutes.
TIME-VALUE : Number of time units.
Change Tone Data, Ring Data and Ticker Data
S92240 : <ACTION>,<FUNCTION-ID>,<NR-OF-ITEMS/ITEM-
NR>,[<PERIODICITY/TONE-SOURCE/TICKER-SOURCE>][,<TIME-
312
VALUE>,<UNIT-T>];
ACTION=0 : Open tone function.

S92240: 0,<FUNCTION-ID>,<NR-OF-
ITEMS>,<PERIODICITY>;
The value of the <FUNCTION-ID>is between 0 and 99 for tone
functions. See Table 4-7 Description of Tone, Ring and Ticker
Functions.
ACTION=1 : Enter PSC tone function (used for PSC hardware).
S92240: 1,<FUNCTION-ID>,<ITEM-NR>,<TONE-
SOURCE>,<TIME-VALUE>,<UNIT-T>;
Functions.
ACTION=2 : Enter PMC tone function (used for PMC hardware).
S92240: 2,<FUNCTION-ID>,<ITEM-NR>,<TONE-
Functions.
ACTION=3 : Enter ring/ticker function (used for both, PSC and PMC hardware).
S92240: 3,<FUNCTION-ID>,<ITEM-NR>,[<TICKER-
SOURCE>],<TIME-VALUE>,<UNIT-T>;
-Ring data:
S92240: 3,<FUNCTION-ID>,<ITEM-NR>,,<TIME-
VALUE>,<UNIT-T>;
-Ticker data:
S92240: 3,<FUNCTION-ID>,<ITEM-NR>,<TICKER-
The value of the <FUNCTION-ID>is between 100 and 199 for ring
functions and between 200 and 299 for ticker functions. See Table 4-
7 Description of Tone, Ring and Ticker Functions.
TIME-VALUE : Number of time units (0...63)
See Table 4-8 PSC Tone Source Numbers and Table 4-9 PMC Tone Source numbers for the
TONE SOURCE data of the PSC and of the PMC, respectively.
313
Write Forward MFC I Data
S92250 : <GROUP-I>,<GROUP-I-RESULT>;
GROUP-I : Forward group I signals 1...15 or no data; see Table 4-2 Relation
between Signal Number and Subcommand Parameter.
GROUP-I- : Meaning of the forward group I signals:
RESULT 0= digit;
1= not used digit;
2= end of dialling.
SIGNAL NUMBER 10 1 ... 9 11 12 13 14 15 NO DATA

GROUP I, II, A, B.
SUBCOMMAND 0 1 ... 9 A B C D E F
PARAMETER.
Table 4-2 Relation between Signal Number and Subcommand Parameter
Write Forward MFC II Data
S92260 : <GROUP-II>,<GROUP-II-RESULT>;
GROUP-II : Forward group II signals 1...15 or no data; see Table 4-2 Relation
GROUP-II- : Meaning of the forward group II signals:
RESULT 0 = priority 0;
1 = priority 1;
2 = priority 2;
3 = no DDI allowed;
4 = priority 4;
5 = priority 5;
6 = collect call.
Example: S92260:8,6; (forward group II-8 signal, 6 = collect call)
314
Write Backward MFC A Data
S92270 : <PROGRESS-CC>,<GROUP-A>,<ACTION-CC>[,<POSITION>];
PROGRESS-CC : Indicates the progress of the Call Control:

0= request next digit;
1= call successful;
2= extension busy;
3= time out;
4= DDO call successful;
5= not existing number;
6= DDI barred;
7= not allowed call;
8= congestion;
9= number unobtainable;
10= don't disturb;
11= automatic answering circuit dialled;
12= automatic answering circuit reply.
19= request first digit of calling party identity.
20= request next digit of calling party identity.
GROUP-A : Backward group A signals 1...15 or no data that has to be sent
for the indicated termination option; see Table 4-2 Relation
ACTION-CC : Indicates the meaning of the backward group A signals:
0= backward release;
1= switch through;
2= change over to Group B;
3= data protected call;
4= no action;
5= execute break in.
POSITION : <POSITION>indicates how many incoming MFC digits (1...9)
have to be received before the CLI request is sent. It can only be
used when <PROGRESS-CC>is 19 (request first digit of calling
party identity). The default value is 1.
315
Write Backward MFC B Data
S92280 : <PROGRESS-CC>,<GROUP-II-RESULT>,<GROUP-B>,<ACTION-
CC>;
PROGRESS-CC : Indicates the progress of the Call Control:

0 = not allowed;
1 = call successful;
2 = extension busy;
3 = time out;
4 = DDO call successful;
5 = not existing number;
6 = DDI barred;
7 = not allowed call;
8 = congestion;
9 = number unobtainable;
10 = don't disturb;
11 = not allowed;
12 = not allowed;
13 = extension busy-in call of type KD1 (for China CSS1
signalling);
signalling);
signalling);
signalling);
signalling);
signalling).
GROUP-II- : Meaning of the forward group II signals:
RESULT 0 = priority 0;
1 = priority 1;
2 = priority 2;
3 = no DDI allowed;
4 = priority 4;
5 = priority 5;
316
6 = collect call.
GROUP-B : Backward group B signals 1...15 or no data that has to be sent
for the indicated termination option and group II result; see
Table 4-2 Relation between Signal Number and Subcommand
Parameter.
ACTION-CC : Indicates the meaning of the backward group A signals:
0 = backward release;
1 = switch through;
2 = change over to Group B;
3 = data protected call;
4 = no action;
5 = execute break in.
Examples :
S92280:1,6,1,1; (call successful, B-1, switch through)
S92280:2,6,3,0; (extension busy, B-3, backward release)
Write Termination after Received MFC A Data
S92285 : <GROUP-A>,<TERM-ACT>;
GROUP-A : Backward group A signals 1...15 or no data that has to be sent

for the indicated termination option; see Table 4-2 Relation
TERM-ACT : Indicates the outgoing termination action after reception of the
specific backward MFC A signal:
0 = send next digit;
1 = forward release and send congestion tone;
2 = forward release and send number unobtainable tone;
3 = forward release and send busy tone;
4 = switch through (speech path);
5 = switch to group B;
6 = start regeneration;
7 = send calling line identity.
317
Note: Termination actions 0, 6 and 7 must always be assigned to a group A signal. However, each
of these termination actions may not be assigned to more than one group A signal. This
implies that:
- It is not possible to (directly) modify a group A signal which has been assigned
termination action 0, 6 or 7.
- When termination action 0, 6 or 7 is assigned to a different group A signal, the group

A signal which was previously assigned to that termination action will implicitly be
modified to termination action 2.
Write Termination after Received MFC B Data
S92290 : <GROUP-B>,<GROUP-II>,<TERM-ACT>;
GROUP-B : Backward group B signals 1...15 or no data that has to be sent

for the indicated termination option and group II result; see
Table 4-2 Relation between Signal Number and Subcommand
Parameter.
GROUP-II : Forward group II signals 1...15 or no data; see Table 4-2 Relation
TERM-ACT : Indicates the outgoing termination action after reception of the
specific backward MFC A signal.
1 = forward release and send congestion tone;
2 = forward release and send number unobtainable tone;
3 = forward release and send busy tone;
4 = switch through (speech path).
Write Alarm Code Parameter
S92300 : <ALARM-HANDLER-CODE>,<ACDM-INDEX>,<ACDM-VALUE>;
ALARM-HANDLER-CODE:
ACDM-INDEX : 0 = SAS alarm level;

1 = SAS alarm threshold occurrence (in occurrences);
2 = SAS alarm threshold time (in seconds).
ACDM-VALUE : 0 = major;
318
1 = minor;
2 = silent;
21 = silent by time;
22 = silent by amount.
Write Resource Type Parameter
S92310 : <RESOURCE-TYPE>,<RTDM-INDEX>,<RTDM-VALUE>;
RESOURCE-TYPE:
RTDM-INDEX and RTDM-VALUE see Table 4-3 RTDM-INDEX and RTDM-VALUE.
319
RTDM-INDEX RTDM-VALUE
INDEX MEANING
0 PAT short cycle time. in units of 5 minutes.
1 PAT long cycle time. in units of 5 minutes.
2 SAS suspicion threshold. in occurrences.
3 SAS alarm level. in levels: 0= major
1= minor
2= silent
3= blocked
4= default (no alarming)
21= silent by time
22= silent by amount
4 SAS alarm threshold in occurrences.
occurrences.
5 SAS alarm threshold time. in seconds.
6 SAS isolation threshold in occurrences.
occurrences.
7 SAS isolation threshold time. in seconds.
8 resource hold time. in units of 5 seconds.
9 SAS silent alarm threshold in hours.
time.
10 SAS failure alarm level. in levels: 0= major
1= minor
2= silent
3= blocked
4= default (no alarming)
21= silent by time
22= silent by amount
11 availability reduction threshold. in percent, or 65535 (meaning no alarming).
Table 4-3 RTDM-INDEX and RTDM-VALUE
320
Assign/Delete Shelf and Modules
S92400 : <ACTION>,<SHELF>[,<SHELF-TYPE>];
ACTION=0: Assign shelf and modules (ASSHLF).

S92400:0,<SHELF>,<SHELF-TYPE>;
ACTION=1: Delete shelf and modules (DESHLF).
S92400:1,<SHELF>;
Assign/Delete Tone Sources to (from) PM
S92401 : <ACTION>,<SHELF>,<BRD>;
ACTION=0: Assign tone sources to PM (ASTONE).

S92401:0,<SHELF>,<BRD>;
ACTION=1: Delete tone sources from PM (DETONE).
S92401:1,<SHELF>,<BRD>;
Display Data about Shelf and Modules
S92405 : <SHELF>;
OM command DISHLF.
Assign/Delete Board
S92410 : <ACTION>,<SHELF-0%BRD-0%>[,<BOARD-TYPE[BOARD-
STYPE]>[,<SIG-GROUP>,[<HW-TYPE>][,<SHELF-1%BRD-
1%>]]];
When parameter SHELF-0%BRD-0% is the EHWA of a slave board, then the EHWA of the
corresponding main board is indicated by the parameter SHELF-1%BRD-1%.
321
ACTION=0: Assign board (ASBRDS).
S92410:0,<SHELF%BRD%>,<BOARD-TYPE[BOARD-STYPE]>,
<SIG-GROUP>,<HW-TYPE>[,<SHELF%BRD%>];
ACTION=1 : Delete board and circuits (DEBRDS).
S92410:1,<SHELF%BRD%>;
ACTION=5 : Change subtype of the board (CHBDST).
S92410:5,<SHELF%BRD%>,<BOARD-TYPE[BOARD-STYPE]>;
ACTION=10 : Assign board and circuits; do not set INS (ASBRDS).
ACTION=20 : Assign board and circuits; set all INS (ASBRDS).
Display Data about Boards
S92415 : <SHELF>,<BRD>;
OM command DIBRDS.
Display TCP/IP Configuration
S92416 : <SHELF>,<BRD>;
OM command DITCPC.
Display MAC-Address Relations
S92420 : <MAC-ADDRESS>;
OM command DIMACA.
Assign, Change and Delete Peripheral Circuit
S92425 : <SHELF>,<BRD>,<CRT>[,<PCT-TYPE>][,<SIG-GROUP>][[,<HW-
322
TYPE>][,<MAC-ADDRESS>]];
OM commands ASPCTB, CHPCTB and DEPCTB.
CHPCTB : Change peripheral circuit data on board.

S92425:<SHELF>,<BRD>,<CRT>[,<PCT-TYPE>][,<SIG-
GROUP>][[,<HW-TYPE>][,<MAC-ADDRESS>]];
ASPCTB : Assign peripheral circuit.
S92425:<SHELF>,<BRD>,<CRT>,,<SIG-GROUP>[,<HW-TYPE>];
DEPCTB : Delete peripheral circuit.
Assign/Delete Link
S92430 : <ORIG-SHELF%ORIG-BRD%ORIG-CRT>[,<LINK-TYPE>,<DEST-
SHELF%DEST-BRD%DEST-CRT>[,<PAR-4>][,<PAR-5>]];
OM commands ASLINK and DELINK.
The EHWAs are represented by one parameter, separated by % signs. Always two % signs
are present, even if an element is empty.
Trailing parameters that are completely empty may be omitted.
- Parameter ORIG-SHELF%ORIG-BRD%ORIG-CRT refer to the SCU or PMC.

For the PMC the ORIG-CRT can be 30 ... 33.
- LINK-TYPE indicates the type of link:
2 up to 7for CCS;
4 and 5for CCS and CPU3000;
10 & 11for CPU3000 only.
- PAR-4 and PAR-5 depend on the type of link; see Table 4-4 Relation between the various
Parameters.
In case of a delete action only the first parameter ORIG-SHELF%ORIG-BRD%ORIG-CRT

may be entered.
323
LINK- TYPE OF LINK EHWA PAR-4 PAR-5
TYPE DESTINATIO
N
2 SM-PM (controllable) PMC/PSC Sequence- "empty"
number
3 SM-PM (not PMC/PSC Sequence- "empty"
controllable) number
4 SM-RPM* (controllable) Remote DTU EHWA local Sequence-
DTU number
5 SM-RPM* (not Remote DTU EHWA local Sequence-
controllable) DTU number
6 SM-IU (controllable) Local DTU Sequence- Unit
number
7 SM-IU (not Local DTU Sequence- Unit
controllable) number
10 PM-PM PMC "empty" "empty"
11 SM-PM PMC "empty" "empty"
* = Also used for CPU3000 systems except for S250/1000.
Table 4-4 Relation between the various Parameters
Display Link Data
S92435 : <SHELF>[,[<BRD>],[<CRT>][,<LINK-TYPE>]];
OM command DILINK.
If the parameters BRD and CRT are omitted the parameter LINK-TYPE indicates the type the
link has to be.
324
Define, Erase or Retrieve Logical Device Name (LDN)
S92440 : <ACTION>,<LDN1>[,<LDN2>][,<UNIT>];
ACTION=1 : Assign for ASLDNM. A new LDN is assigned to an already existing LDN.
S92440:1,<LDN1>,<LDN2>,<UNIT>;
ACTION=2 : Assign for ASDEVC.
S92440:2,<LDN1>,,<UNIT>;
ACTION=5 : Validate assignment.
S92440:5,<LDN1>,,<UNIT>;
ACTION=8 : Validate erase for DELDNM.
S92440:8,<LDN1>;
ACTION=9: Validate erase for DEDEVC.
S92440:9,<LDN1>;
ACTION=10 : Erase for DELDNM.
S92440:10,<LDN1>;
ACTION=11 : Erase for DEDEVC.
S92440:11,<LDN1>;
ACTION=12 : Reassign ASLDNM.
S92440:12,<LDN1>,,<UNIT>;
ACTION=13 : Validate reassign ASLDNM.
S92440:13,<LDN1>;
Assign or Delete Port, Change Port Characteristics
S92445 : <ACTION>,<SHELF%BRD%CRT>[,<PROTOCOL-
TYPE>][,<CONNECTION-TYPE>][,<BAUDRATE>];
ACTION=0 : Assign Port (ASPORT).

S92445:0,<SHELF%BRD%CRT>,<PROTOCOL-
TYPE>,<CONNECTION-TYPE>,<BAUDRATE>;
ACTION=1 : Erase Port (DEPORT).
S92445:1,<SHELF%BRD%CRT>;
ACTION=2 : Validate Erase Port
S92445:2,<SHELF%BRD%CRT>;
325
ACTION=3 : Change Port Characteristics (CHPORT).
S92445:3,<SHELF%BRD%CRT>,<BAUDRATE>];
Assign or Delete Device
S92450 : <ACTION>,[<SHELF%BRD%CRT>],<LDN>[,<EQUIPMENT-TYPE>];
ACTION=0 : Assign ASDEVC.

S92450:0,<SHELF%BRD%CRT>,<LDN>,<EQUIPMENT-TYPE>;
ACTION=1 : Erase for DEDEVC.
S92450:1,,<LDN>;
ACTION=2 : Validate erase device.
S92450:2,,<LDN>;
Subcommand for Command DICONF
S92455 : <SHELF>[,[<BRD>][,<CRT>]];
Retrieve/Display Device Characteristics
S92460 : <LDN>;
OM command DIDEVC.
Display Port Characteristics
OM command DIPORT.
326
Assign/Delete Clock Reference Unit Entry
S92480 : <ACTION>,<SHELF>%<BRD>%<CRUE-CRT>;
ACTION=0 : Assign CRU entry (ASCRUE).

S92480:0,<SHELF>%<BRD>%<CRUE-CRT>;
ACTION=1 : Delete CRU entry (DECRUE).
S92480:1,<SHELF>%<BRD>%<CRUE-CRT>;
Display Clock Reference Unit Entry
S92485 : ;
OM command DICRUE.
Assign/Delete Board Relation and/or Virtual Channels
S92500 : <NVCT>,<IPH-SHELF>,<IPH-BRD>,<IPH-CRT>[,<DTU-
SHELF>,<DTU-BRD>];
The parameter NVCT is the required number of virtual channels (NVCT=0 ... 30).
Assign D-channel (ASBRVC).
S92500:<NVCT>,<IPH-SHELF>,<IPH-BRD>,<IPH-CRT>,<DTU-SHELF>,<DTU-
BRD>;
Delete D-channel (DEBRVC).
S92500:<NVCT>,<IPH-SHELF>,<IPH-BRD>,<IPH-CRT>;
327
Note: In case of a DTU-PH or DTU-BA, IPH-BRD and IPH-CRT can be a DTU-BRD and DTU-
CRT.
Find PCT by Type
S92510 : <PCT-TYPE>;
OM command FIPCTT.
Change Signalling Group Data
S92600 : <BIT/BYTE>,<SIG-GROUP>,<ITEM>,[<DATA>],[<PM-OBJECT>];
OM command CHPMPD.
PM-OBJECT = 0 : Signalling group data

= 1 : Slave data
= 2 : PSC tone data
= 3 : Ring data
= 4 : Ticker data
= 5 : PMC tone data
= 6 : Direct downloadable data
Change Slave Data
S92620 : <OBJ-INDEX>,<ITEM-NR>,<DATA>;
OBJ-INDEX for Slave-Data-Type.
OM command CHPMPD.
Display PM Projecting Data
S92630 : <PM-OBJECT>[,<OBJ-INDEX>[,<ITEM-NR>[,<BIT/
BYTE>]]],[<SHELF>,<BRD>];
If PM-OBJECT =6 then <SHELF>,<BRD>must specify a PM shelf and board.
328
OM command DIPMPD.
Change IP Projecting Data For EL@Ns
S92650 : <IP-SIG-GROUP>,<IP-PROJ-DATA-TYPE>,<IP-PROJ-DATA-
VALUE>/<ACTION>[,<TAG-1>[,<TAG-2>[,<DATA-LINE-
1>[,<DATA-LINE-2>]]]];
Depending on parameter <IP-PROJ-DATA-TYPE>, parameter <IP-PROJ-DATA-VALUE>

has a different meaning.
In case parameter <IP-PROJ-DATA-TYPE> has value 3 (VoIP data), then parameter

<ACTION>,<TAG-1>,<TAG-2>,<DATA-LINE-1>,<DATA-LINE-2> are valid.
ACTION = 0 : Reset and ACTION = 1: Data (append)
- S92650 : <IP-SIG-GROUP>,<0>,<NUMBER>;
- S92650 : <IP-SIG-GROUP>,<1>,<LANGUAGE>;
- S92650 : <IP-SIG-GROUP>,<2>,<IP-ADDRESS>;
- S92650 : <IP-SIG-GROUP>,<3>,<ACTION>[,<TAG-1>[,<TAG-2>[,<DATA-
LINE-1>[,<DATA-LINE-2>]]]];
The sub-signalling is specified in hexadecimal format : 0100 ... 01FE.
Parameters <TAG> and <DATA-LINE> are between quotes " ". This means that 18
characters (20-2 quotes) are left. Therefore parameters <TAG> and <DATA-LINE> are
split into <TAG-1>, <TAG-2> and <DATA-LINE-1>, <DATA-LINE-2>.
OM command CHIPPD.
Activate IP Projecting Data For EL@Ns
S92660 : ;
OM command ACIPPD.
329
Display IP Projecting Data For EL@Ns
S92670 : <IP-SIG-GROUP>;
OM command DIIPPD.
Install Software Package Relation
S92700 : <ACTION>,[<NEW-PACK>],[<OLD-PACK>],<BOARD-STYP>;
OM command INSTPK.
ACTION=1 : Delete relations.

S92700:1,[<NEW-PACK>],[<OLD-PACK>],<BOARD-STYP>;
ACTION=2 : Relate new package without a reference.
ACTION=3 : Relate new package wit reference to the old package.
Delete and Display Software Package
S92710 : <ACTION>,[<SHELF-0%BOARD-0%>][,<WAIT>];
ACTION=1 : Delete Software Package from the board (DEPACK).

S92710:1,[<SHELF-0%BOARD-0%>][,<WAIT>];
The meaning of the optional wait indication is:
WAIT = 0:don't wait for completion of delete operation,
WAIT = 1:wait for completion of delete operation.
ACTION=2 : Display Software Package in the system (DIPACK).
S92710:2,[<SHELF-0%BOARD-0%>];
The optional <WAIT>can not be used here.
330
Downloading Terminals
S92730 : <ACTION>,<PACK>,<SHELF>,<BRD>,<CRT>;
ACTION=0: Display downloading terminals (DIDOTE).

S92730:0,<PACK>,<SHELF>,<BRD>,<CRT>;
ACTION=1: Start downloading terminals (STDOTE).
S92730:1,<PACK>,<SHELF>,<BRD>,<CRT>;
Display Equipment Identification
S92750 : <SHELF>,<BRD>;
OM command DIEQID.
Change and Display MOH-CV Relation
S92800 : <ACTION>,<CV>[,[<SHELF>],[<BRD>],[<CRT>]];
ACTION=5: Assign MOH-CV Relation (CHCVMH)

S92800:5,<CV>,<SHELF>,<BRD>,<CRT>;
ACTION=5: Delete MOH-CV Relation (CHCVMH)
S92800:5,<CV>;
ACTION=2: Display MOH-CV Relation (DICVMH)
S92800:2,<CV>;
Display TCP/IP Configuration
S92900 : <SHELF>,<BRD>;
OM command DITCPC.
331
Start FTP Server
S92910 : <SUSPEND/RESUME>;
OM command STFTPS.
Change/Delete IP User
S92930 : <ACTION>,<IP-
APPLICATION>,<USERNAME>,[<USERNAME2>],<PASSWORD>,[<US
ERNAME2>];
The parameter USERNAME contains the first 18 characters, delimited by quotes.

USERNAME2 contains the last two characters of the username, delimited by quotes. The
same applies to PASSWORD and PASSWORD2.
ACTION=0: Change IP user (CHIPUS)

ACTION=1: Delete IP user (DEIPUS)
OM command STFTPS.
Display IP User
S92950 : <IP-APPLICATION>;
OM command DIIPUS
Display IP Sessions
S92960 : [<IP-APPLICATION>][,<SHELF>,<BRD>];
OM command DIIPSE.
332
Check if system is reachable through IP-network
S92970 : [<SHELF>],[<BRD>],<IP-ADDRESS>;
Display all Resources with Specified Owner
S99000 : <OWNER>;
OM command FIOWNR.
OWNER: 0= NO 3= SYS 6= SAS2

1= START 4= SAS1 7= POM2
2= CP1 5= POM1 8= CP2
Change Client Service Profile
S93100 : <PROFILE-ID>[,[<SERVICE>][,[<ALLOWED>][,[<LDN>]]]];
OM command CHPROF.
Display Client Service Profile(s)
S93110 : [<PROFILE-ID>];
OM command DIPROF.
Change IP Address - Client Service Profile Relation
S93120 : <IP-ADDRESS>[,[<PROFILE-ID>]];
OM command CHIPPR.
333
Display IP Address - Client Service Profile Relation(s)
S93130 : [<IP-ADDRESS>][,[<PROFILE-ID>]];
OM command DIIPPR.
Display Physical Channel Destination
S99010 : <SHELF>,<BRD>[,<CRT>];
OM command DIPCHD.
Perform Action on Dump Trigger
S99100 : <SHELF>,[<BRD>],<CRT>,<ACTION>
OM command TRSYSD.
If parameter BRD is empty:
ACTION =0 : Direct dump without LDB is made.

S99100: <SHELF>,,<CRT>,0;
ACTION =1 : Direct dump with LDB is made.
S99100: <SHELF>,,<CRT>,1;
ACTION =2 : Off hook trigger.
S99100: <SHELF>,,<CRT>,2;
If parameter BRD is not empty:
ACTION =0 : Activate system dump trigger.

S99100:<SHELF>,<BRD>,<CRT>,0;
Read and Reset Routing Counters
S99120 : <SHELF>,<BRD>[,<CRT>];
OM command DIROCO.
334
Display Number of Free Packets once per Minute
S99130 : ;
OM command DIPVAR.
Read Number of Free Packets
S99140 : ;
OM command DIPOOL.
Start (reset) unrestricted status monitoring
S99150 : ;
OM command STMONI.
Change BSPT definition
S99200 : <BSPT>,<IBSC-STRING>;
IBSC-STRING is a string of 20 digits (0 or 1) indicating which IBSC (0 ... 19) is part of the BSPT:
a 1 in the string means that the IBSC is part of the BSPT.
OM command CHBSPT.
Display ISDN dynamic trunk access data
S99210 : <BUNDLE>,<IBSC>;
OM command DIISDN.
335
Start/Stop service
S99500 : <START/STOP>,<IP-SERVICE>;
OM commands STSRVC and SPSRVC.
Parameter START/STOP can be 0 (start service) or 1 (stop service).
Display Service
S99510 : <IP-SERVICE>;
OM command DISRVC.
Change or Display System Trap
S99610 :
<ACTION>[,<TRAP>[,<ON_OR_OFF>[,<PAR1>[,<PAR2>[,<PAR3>]]]]];
ACTION =0 : Change Trap Status (CHTRAP, see section 2.4.10. CHTRAP and
DITRAP)
S99610: 0,
[,<TRAP>[,<ON_OR_OFF>[,<PAR1>[,<PAR2>[,<PAR3>]]]]
];
ACTION =1 : Display Trap Status (DITRAP, see section 2.4.10. CHTRAP and
DITRAP)
S99610: 1;
PAR1 : Alarm code (0..255), Signal id (H'000..H'FFF) or Preset value
(H'0000..H'FFFF)
PAR2 : Alarm qualifier (0..255) or Time in seconds (H'1..H'FFF)
PAR3 : SHELF%BRD%CRT
336
Display Memory Usage
S99620 : <AREA>,<USER>;
OM command DIMEUS.
Display PVE Monitor
S99700 : <DNR>;
OM command DIPMON.
337
4.10. ALARM CODE DATA MANAGER
ALARM CODE ALARM TYPE

011 SAS Buffer Overflow
012 Major Alarm in other Unit
013 Minor Alarm in other Unit
014 Silent Alarm in other Unit
015 Blocked Alarm in other Unit
016 Blocked Circuits Report
017 Alarm Routing Modification Report
018 Silent Alarms - limited by amount threshold - exceeded
019 Failed Resource Report
021 Sensor Event 1
022 Sensor Event 2
023 Sensor Event 3
024 Sensor Event 4
025 Sensor Event 5
026 Sensor Event 6
027 Sensor Event 7
028 Sensor Event 8
031 System State Altered
032 Back-up Problems
033 Diagnostic Notice
034 System Maintenance Notice
035 License Warning
036 License Alarm
041 Cleared Software Exception
042 Not cleared Software Exception
043 Cleared Software Congestion
044 Not Cleared Software Congestion
338
ALARM CODE ALARM TYPE
045 Illegal Resource Identity
046 Cleared Hardware Exception
047 Cleared Protocol Exception
051 Project Engineering Fault
061 Informatory Event
062 Additional Notice
063 Special Usability Notice
064 Manually Controlled Test Failure
065 Special Hardware Notice
066 Time Integrated Hardware Notice
067 Not Usable Resources
068 Obtainable Notice
069 Resource Availability Reduction
071 Service button pushed too long
081 Diagnostic Informatory Event
082 Unlicensed Facility Accessed
083 Temporary License will expire
084 Temporary License has expired
085 Ethernet Link Fault
100 Hard Hardware Fault
110 Intermittent Hardware Fault
120 Soft Hardware Fault
130 Severely Suspected Resource
Table 4-5 Alarm Code and Alarm Type.
339
4.11. RESOURCE TYPE DATA MANAGER
RESOURCE- DESCRIPTION
TYPE
000 Line circuit (LCT)
001 Trunk circuit (TRC)
002 Operator circuit (OPC)
003 IAS timeslot
004 Receiver-Sender Socotel
005 Add-on Circuit
006 Converter
007 Receiver keytone - sender dial tone
008 Sender keytone - receiver dial tone
009 Incoming MFC
010 Outgoing MFC
011 Hatch
012 Peripheral Module Controller resource
013 Board
014 Device
015 Communication Interface boards, except the CII (type 027)
016 Null tone
017 External ring tone
018 Internal ring tone
019 Music On Hold tone (MOH)
020 Switching Network Link (SNL)
021 Switch and Control Unit (SCU)
022 Central Module (CM)
023 Central Memory Slice (CMS)
024 Majority Interface Circuit (MIC)
025 Clock Signal Generator (CSG)
340
RESOURCE- DESCRIPTION
TYPE
026 Clock Reference Unit (CRU)
027 Communication Interface Internal (CII)
028 Switching Network Module (SM)
029 Logical Channel
030 Physical Channel
031 Testbus
032 Paging circuit
033 Camp on Busy tone
034 Busy tone
035 CRU entry
036 Unit Logical Link (ULL)
037 Digital Trunk Unit-Control
038 Virtual Channel
039 D-Channel
040 Shelf
041 Multi function board
042 SN routing tone
043 SN announcement
044 Interunit Line Circuit
045 Peripheral Module (PM)
046 Prim - pm - network / pm - network
047 SN specific announcement
048 Communication Interface External (CIE)
049 Switch and Sense Unit (SSU)
050 Backup and Interface Module (BIM)
255 Null resource
Table 4-6 Resource Type List
341
4.12. TONE, RING AND TICKER FUNCTION
FUNCTION FUNCTION ID DESCRIPTION

Tone Function 000 Internal ring tone.
001 External ring tone.
002 Internal dial tone.
003 First external dial tone.
004 Second external dial tone.
005 Delayed hotline dial tone.
006 Busy tone.
007 Number unobtainable tone.
008 Congestion tone.
009 Diversion active dial tone.
010 Confirmation tone.
011 Urging tone.
012 Call waiting tone burst.
013 Paging absent tone.
014 Paging in progress tone.
015 Bypass tone.
017 Camp on busy tone to caller.
018 Park tone.
019 Through connect ring tone.
020 Ticker tone 0.
023 Call Waiting Indication tone (not used).
024 ARB destination ring back tone.
026 Enter password tone.
027 Routing tone.
Ring Function 100 Internal ring current.
101 External ring current.
102 Automatic ring back current.
342
FUNCTION FUNCTION ID DESCRIPTION
103 Emergency alarm ring current.
104 Through connect ring current.
106 Service B ring (used for message waiting
ring).
107 Ring burst (not used).
Ticker Function 200 Break-in ticker.
201 Add-on ticker.
202 Urging Ticker (not used).
203 Call waiting Ticker (not used).
204 Dial up Break in Ticker.
Table 4-7 Description of Tone, Ring and Ticker Functions
Note: The default settings of Tone, Ring and Ticker functions can be found in the Signalling Data
Manual.
The Signalling Data Manual shows more Tone, Ring and Ticker functions than Table 4-7
Description of Tone, Ring and Ticker Functions. The ones not mentioned have become
obsolete or are intended for future use.
4.13. PSC TONE SOURCES
The table below lists the Tone Sources which are available at the PSC:
343
TONE- FREQUENCY LEVEL (dBm0) COMMENT
SOURCE (Hz)
00 --- --- Contents PROM identification
01 --- --- Idle pattern (silence)
02 4 periods of 400 0 Ticker (incl. 500 msec)
03 4 periods of 425 - 12 Ticker (incl. 500 msec)
04 4 periods of 425 - 3 Ticker (incl. 500 msec)
05 150 + 440 - 6 - 15
06 400 -3
07 400 -6
08 400 -9
09 400 - 12
10 400 x 33.3 -3
11 400 x 33.3 -9 400 Hz modulated by 33.3 Hz
12 400 x 33.3 - 17
13 425 -3
14 425 -6
15 425 -9
16 425 - 12
17 425 - 23
18 425 x 25 - 10 425 Hz modulated by 25 Hz
19 425 x 25 - 14
20 450 0
21 450 -4
22 450 -8
23 950 - 4.5
24 950 -9
25 950 - 13
344
TONE- FREQUENCY LEVEL (dBm0) COMMENT
SOURCE (Hz)
26 1400 - 4.5
27 1400 -9
28 1400 - 13
29 1800 - 4.5
30 1800 -9
31 1800 - 13
Table 4-8 PSC Tone Source Numbers
4.14. PMC TONE SOURCES
The PMC has a number of tone sources. The table below, lists the default settings of these
sources. The default values of some tone sources might have been changed by OM: CHPMPD
(see OM Commands Manual (MML)) or by subcommand: S92620.
345
TONE TONE SLAVE DATA REMARK
SOURCE SPECIFICATION
FREQ. LEVEL TONE LEVEL
(Hz) (dBm)
0 425 -3 18 3 ticker
1 0 0 0 0 silence
2 425 - 12 20 12 H'FF*
3 450 -8 22 8
4 950 - 13 24 13
5 150 440 - 6 - 15 17 6 ticker
6 1400 - 13 25 13
7 1800 - 13 26 13
8 400 -9 19 9
9 400 - 12 19 12
10 425 - 23 20 23
11 425 x 25 - 10 32 10
12 400 x 33.3 - 17 31 17
13 425 -3 30 3
14 450 0 22 0
15 425 -9 20 9
16 941 1336 - 10.2 - 8 14 6 DTMF `0'
17 697 1209 - 10.2 - 8 1 6 DTMF `1'
18 697 1336 - 10.2 - 8 2 6 DTMF `2'
19 697 1477 - 10.2 - 8 3 6 DTMF `3'
20 770 1209 - 10.2 - 8 5 6 DTMF `4'
21 770 1336 - 10.2 - 8 6 6 DTMF `5'
22 770 1477 - 10.2 - 8 7 6 DTMF `6'
23 852 1209 - 10.2 - 8 9 6 DTMF `7'
24 852 1336 - 10.2 - 8 10 6 DTMF `8'
25 852 1477 - 10.2 - 8 11 6 DTMF `9'
346
TONE TONE SLAVE DATA REMARK
SOURCE SPECIFICATION
FREQ. LEVEL TONE LEVEL
(Hz) (dBm)
26 941 1209 - 10.2 - 8 13 6 DTMF `*'
27 941 1477 - 10.2 - 8 15 6 DTMF `#'
28 697 1633 - 10.2 - 8 4 6 DTMF `A'
29 770 1633 - 10.2 - 8 8 6 DTMF `B'
30 852 1633 - 10.2 - 8 12 6 DTMF `C'
31 941 1633 - 10.2 - 8 16 6 DTMF `D'
* Tone source 2 has a fixed setting.
Table 4-9 PMC Tone Source numbers
347
5. I/O BUS OBSERVER
5.1. INTRODUCTION
The I/O bus observer is designed for observing the commands and messages between the
CPU and PPU and between the PPU and subparts like ATC, TSC, PCC. It is the predecessor
of the PM Bus Observer.
The I/O bus observer is a board containing some logic for interpretation and formatting of the
commands and messages of the I/O bus and a receiver/transmitter for the standard V.24/V.28
interface to a terminal or keyboard/printer.
The I/O bus observer directly scans the I/O bus in the PM. Therefore only the PCTs in the PM
in which the I/O bus observer board is located can be observed.
The I/O bus observer can cooperate with any normal asynchronous terminal or PC with
emulator program.
Note: The I/O bus observer can only be used in the PM2500 and PM1000.
5.2. INSTALLATION
PROCEDURE:
The I/O bus observer board must be placed in that PM, of which the commands and messages
are to be observed.
Actions
- First check the strap setting on the board; see Figure 5-1 Strap Settings.
348
BA
Strap setting for PCT

Positions in PM1100
X2.1
X2.2
FBC
To
VDU
BB
Strap setting for PM2500
X2.1
X2.2
Figure 5-1 Strap Settings
- Place the board in one of the right hand side positions of the PSC, e.g. pos. 20, 21, 23 or
24 for the PM2500 shelf or place the board in position 8 of the PM1000 shelf.
- Switch on the VDU.
- Set the terminal characteristics and select the baud rate.
- Connect the VDU to the I/O bus observer; the cable used depends on the type of terminal.
The cable with the Canon plug is used for VT type terminals.
For the pin numbering of the connectors, see Figure 5-2 I/O Bus Observer Cable.
349
Terminal
side
1
14
YW / BLK -2 I/O bus
side
BU / BLK -3 301 - GY/BLK
GY / BLK -4 101 - RD/BLK
102 - RD
GR / BLK -5 303 - WT/BLK
103 - BL/BLK
Seen from wiring side
RD -7 305 - PK/BLK
RD/BLK -20 105 - YW/BLK
BR/BLK -20
WT/BLK -20
PK/BLK -22 307 -BR/BLK
107 - GN/BLK
25
13
25-pole male F122-

D-connector connector
7 RD 102 - GND RD 102
2 YW/BLK 103 - TXD BL/BLK 103
3 BL/BLK 104 - RXD YW/BLK 105
5 GN/BLK 106 - CTS GY/BLK 301
4 GY/BLK 105 - RTS GN/BLK 107
20 RD/BLK 108/2 - DTR PK/BLK 305
22 PK/BLK - RI RD/BLK 101
6 107 - DSR WT/BLK 303
8 109 - DCD BR/BLK 307
Figure 5-2 I/O Bus Observer Cable
5.3. START
5.3.1. Initial Entry
The I/O bus observer is started by pressing the space bar a number of times. This results in an
automatic speed setting of the observer. The I/O bus observer answers by:
SOPHO-S I/O-BUS OBSERVER Software ref. 10.18 date. 88-3-22
350
For restart request: push esc
This announcement indicates a correct functioning of the observer.
5.3.2. Main Menu
The main menu is entered by pressing the ESC key (F11 on the VT220); this is the restart key
and results in displaying the main menu. The main menu comprises the following six options:
RESTART REQUESTED
1 = New baud rate (Z80 reset) Push space bar.
2 = New selection of all (clear buffer contents).
3 = Go on with selected equipment (clear buffer contents).
4 = Go on with selected equipment (do not clear buffer contents).
5 = Repeat buffer contents and go on like 4.
6 = New selection of all and repeat buffer contents.
Ready for observing the I/O-BUS
• Option 1: New baud rate setting

When another baud rate is wanted the observer does not have to be removed from the
shelf. Select option 1 in the main menu, set another baud rate on the terminal and press
the space bar a number of times. Continue as described in 5.3.1. Initial Entry.
• Option 2: New selection of all
Using this option it can be determined which messages and PCTs are to be observed. This
is always necessary at an initial entry or after setting the baud rate. If more or less messages
or PCTs have to be observed a complete new selection has to be made. Continue with
5.3.3. Message Selection.
• Option 3: Go on with the selected equipment
After interrupting the message output display can be resumed by selecting this option. The
original message/PCT selection is used.
• Option 4: Go on with the selected equipment
Same as option number 3, but now the buffer contents is not cleared.
• Option 5: Repeat buffer contents and go on like option 4
Messages are temporarily stored in FIFO buffers. If this option is chosen the previously
stored messages are displayed first and then normal display is resumed (of new messages).
• Option 6: New selection of all and repeat buffer contents
351
A new option can be selected and the buffer contents is repeated.
5.3.3. Message Selection
After selecting option 2 in the main menu, the observer will interrogate the user to determine
which messages are to be stored and displayed.
The different types of messages can be selected by answering the questions given in Table 5-
1 I/O Bus Observer Set-upby y (yes) or n (no).
When one wants to observe the messages to/from a particular PCT one must specify that PCT
as follows:
The PCT numbers have to be entered using the board position and circuit number.
- Board position is always two digits; so do not forget a leading zero if applicable.
- Circuit number is one digit.
Check that the numbers given do exist. If not you have to start with <ESC>.
Selection of a range of PCT numbers is done as follows:
- Range 1: first PCT number ... last PCT number

- Range 2: first PCT number ... last PCT number...<CR>
For example: board 7 circuit 0 and board 12 circuit 0 up to and including 5 are entered as
follows:
07, 0 07, 0 12, 0 12, 5 <CR>
352
SELECTIONS REMARKS
Do you want the hex. codes only The observer is able to display both the
hexadecimal code of the commands and
messages and a description of them
(string). When only the codes are wanted
and not the description then enter 'y'.
The strings only give an indication. Not all
of them are correct and not all of the
codes have related strings.
Do you want the CPU messages All CPU events and commands; when 'no'
was entered the following questions
concerning the CPU are skipped.
Continue with 'Peripheral Circuit
Control' message.
Do you want the CPU-PCT/VCT messages Events from a PCT and the commands to
a PCT; when 'no' was entered the next
question is skipped. Determine when you
want the PCT messages of all the PCTs
or only a number of them.
Do you want them of all PCT numbers When the first question (codes only) was
confirmed this question is skipped; then
all PCTs messages are displayed.
When the answer is 'no' one must specify
the PCTs.
Do you want the CPU-BIC messages Messages to the Break-In Circuits (BIC).
Do you want the CPU-SNC messages Messages between the:
. Internal Switching Network (TSW) and
CPU.
. Boards and CPU.
Do you want the CPU-BOARD messages Maintenance messages between CPU
and PM.
Do you want the CPU-PMCP messages Hexadecimal codes between CPU and
PM; when 'yes' is selected the messages
between the CPU and PPU (CI-PPU) are
also displayed.
353
SELECTIONS REMARKS
Do you want the hex. codes also Only relevant for PM2500.
Do you want the PCC messages Messages to/from the Peripheral Circuit
Control chip.
Do you want the TSC messages Messages to/from the Time Switch
Controller chip.
Do you want the CI-INT messages Messages to/from the CI-INT. When 'y' is
entered the channel can be selected in
the following question; when 'no' was
entered the next question is skipped.
which channel 1.CI-INT1 Answer with 1, 2 or 3.
displayed 2.CI-INT2
type (1/2/3) 3.CI-INT1, 2
Do you want the messages transparent
Do you want the CI-DIG messages Messages to/from the CI-DIG in unit
groups 0 and 1 (OIU, DLC, IPH, etc.)
Board position CI-DIG
Board type of CI-DIG 1.OIU Answer with 1, 2, 3 or 4.
2.DLC
3.IPH
type (1/2/3/4) 4.DTU-BA
Do you want the ADC messages Messages to/from the Alarm and
Disconnect Circuit (for the status and
alarm collection).
Do you want the ATC messages Messages to/from the Add-on and Tone
generator Circuit.
Do you want the DTU-CC messages Messages to/from the DTU-CC board
(for PM2500).
Table 5-1 I/O Bus Observer Set-up
5.4. EXAMPLE OF THE SET-UP
SOPHO-S I/O BUS OBSERVER Software rel. 10.18 date 88-3-22
354
For restart request : push esc
Do you want the hex. codes only (Y/N) N
Do you want the CPU messages (Y/N) Y
Do you want the CPU-PCT/VCT messages (Y/N) Y
Do you want them of all PCT/VCT numbers (Y/N) N
Do you want the CPU-BIC messages (Y/N) N
Do you want the CPU-SNC messages (Y/N) N
Do you want the CPU-BOARD messages (Y/N) Y
Do you want the CPU-PMCP messages (Y/N) N
Do you want the hex. codes also (Y/N) Y
Do you want the PCC messages (Y/N) N
Do you want the TSC messages (Y/N) N
Do you want the CI-INT messages (Y/N) N
Do you want the CI-DIG messages (Y/N) N
Do you want the ADC messages (Y/N) N
Do you want the ATC messages (Y/N) N
Do you want the DTU-CC messages (Y/N) N
1000 CI-CPU IN 08 40 C0 CC 09 00 00 00 02 40 43 18 01 29 46 9C
CPU EVENT PCT 01,0 OPERATOR BUTTON ON PARAM. 29
1028 CI-CPU OUT 08 00 10 C3 09 00 00 00 01 40 13 1E 80 00 26 34
CPU COMMAND PCT 01,0 CLEAR CHARACTERS ON ONE DISPLAY PARAM. 00
1052 CI-CPU OUT 08 00 30 C4 09 00 00 00 01 40 13 1E 80 01 FD 80
355
CPU COMMAND PCT 01,0 CLEAR CHARACTERS ON ONE DISPLAY PARAM. 01
1087 CI-CPU OUT 08 00 10 C5 08 00 00 00 01 46 19 21 00 93 F3
CPU COMMAND PCT 01,0 ACTIVATE HANDSET
1120 CI-CPU OUT 08 00 30 C6 0A 00 00 00 01 46 1A 21 80 F1 A0 23 09
CPU COMMAND PCT 01,0 CHANGE PA PARTY INFORMATION LEDS PARAM. F1 A0
1148 CI-CPU OUT 08 00 10 C7 0A 00 00 00 01 40 01 00 03 02 32 84 27
CPU COMMAND PCT 01,0 CONNECT PAIR PARAM. 02 32
1169 CI-CPU OUT 08 00 30 C8 0A 00 00 00 01 40 02 03 01 02 FF B4 22
CPU COMMAND PCT 01,0 START TONE WITH AUTOMATIC STOP PARAM. 02 FF
1194 CI-CPU IN 08 40 C0 CE 09 00 00 00 02 40 43 18 03 02 0C 5B
CPU EVENT PCT 01,0 OPERATOR DIGIT PARAM. 02
1227 CI-CPU OUT 08 00 30 C4 0A 00 00 00 01 40 01 00 03 02 32 80 23
CPU COMMAND PCT 01,0 CONNECT PAIR PARAM. 02 32
1254 CI-CPU OUT 08 00 10 C5 0B 00 00 00 01 40 15 1E 01 00 00 02 42 2D
Note: The time announcements (HH:MM:SS) as well as the 10-second intervals (10, 20 up to
50) are not shown here but they will appear on the screen.
5.5. INTERPRETATION
A description of the message line with the hexadecimal code is given in Figure 5-3 Message
Line with Hexadecimal Code.
TIME CI-CPU IN 08 40 C0 CC 09 00 00 00 02 40 43 18 01 29 46 9C
time direction
(msec)
IMP message (signal)
message type
Figure 5-3 Message Line with Hexadecimal Code
356
The explanation of a message line with description is given in Figure 5-4 Message Line with
Description.
TIME CPU EVENT PCT 01,0 OPERATOR BUTTON ON PARAM,29
time Control Description Signal

(msec) number parameter
destination/origin
event/command
origin/destination
Figure 5-4 Message Line with Description
By selecting hexadecimal codes only, the output contains line 1 or 2.
By selecting hexadecimal also, both lines are displayed; the output will therefore have two lines
per message. In this case the time is not displayed in second line.
For the interpretation of parts of the I/O-bus Observer trace reference is made to appendix
B: Signalling, Commands & Messages.
In the following two sections two examples are given of an I/O-bus Observer trace.
5.6. I/O BUS OBSERVER EXAMPLE 1 - ENQUIRY CALL
This section gives the observation of an enquiry call. The extensions involved are two analogue
telephone sets connected to an ALC-A01 and one digital telephone set connected to a DLC-
A. The situation is as follows:
- Extension 2000 connected to ALC 8, 0 goes off hook;

the RST-KD (6, 0/6, 1) is attached
- Extension 2000 calls extension 2016 which is connected to DLC 13, 2;
the RST-KD (6, 0/6, 1) is released.
- Extension 2016 answers.
- Extension 2016 calls extension 2001 which is connected to ALC 8, 1.
- Extension 2001 answers.
- Extension 2016 goes on-hook; the call is transferred.
- Extension 2001 goes on-hook.
- Extension 2000 goes on-hook.
357
Note: The RST-KD function, which is mentioned in this example, refers to an RST-KD board in
the PM2500 shelf.
Figure 5-5 Situation Outline shows the circuits involved and identifies the signals at the I/O-bus
interface as referred to on the I/O-bus Observer output.
For the interpretation of parts of the I/O-bus Observer trace (commands and messages of
ALC A/B and RST-KD) reference is made to appendix B . SIGNALLING, COMMANDS &
MESSAGES.
The I/O-bus Observer trace shows the set up selection and the complete sequence of events
as generated by the Observer, with some editing information to separate the major sections.
Finally the flow diagram give a two dimensional presentation of the trace, with some necessary
interpretation and showing the major PM parts and the signal directions.
358
TSW SWITCHING
NETWORK
ALC 8,0 1,15

DNR 2000
1
RST - KD
DET 2
1,17
4
ATC
DIAL TONE (15)
SILENCE (0,1)
DLC 13,2 1,18

DNR 2016
1,19
3
ALC 8,1 1,20
DNR 2001
CI-IMP CI-IMP CPU

PCC INT 1 TSC CPU
A B C D E F G LEGEND:
A = PCC Command
B = PCC Event
I/O BUS C = CI-INT1 Command
D = CI-INT1 Event
OBSERVER E = SWI Connect
PPU F = CI-CPU IN/PCT Event
G = CI-CPU OUT/PCT Command
Figure 5-5 Situation Outline
5.6.1. I/O Bus Observer Trace of an Enquiry Call
Below the output of the I/O Bus Observer is given. The major sections are separated by text
frames with some editing information. See also the note in section 5.4. EXAMPLE OF THE
359
SET-UP.
SOPHO-S I/O-BUS OBSERVER Software ref. 10.18 date. 88-3-22
Do you want the CPU-PCT/VCT messages (Y/N) Y
Do you want them of all PCT/VCT nmbrs (Y/N) Y
Do you want the CPU-SNC messages (Y/N) Y
Do you want the hex. codes also (Y/N) Y
Do you want the PCC messages (Y/N) Y
Do you want them of all PCT nmbrs (Y/N) Y
Do you want the TSC messages (Y/N) Y
Do you want them of all PCT nmbrs (Y/N) Y
Do you want the CI-INT messages (Y/N) Y
which channel displayed
1. CI-INT1
2. CI-INT2
3. CI-INT1, 2
type (1/2/3)
360
Do you want the messages transparent (Y/N) N
Extension 2000 (ALC 8, 0) goes off-hook; RST-KD (6, 0/6, 1) connected.
4715 PCC EVENT PCT 08, 0 DATA = 01011111
4729 CI-CPU IN 08 40 C0 C5 08 00 00 38 02 40 40 00 01 DA 40
PCT EVENT PCT 08, 0 CALL REQUEST
4729 PCC COMMAND PCT 08,0 DATA = 11111100
4785 CI-CPU OUT 08 00 30 C5 08 00 00 38 01 40 09 10 02 02 57
PCT COMMAND PCT 08, 0 RESOURCES READY
4855 CI-CPU OUT 08 00 10 C6 0A 00 00 38 01 40 01 00 01 02 2F 1A 9F
PCT COMMAND PCT 08, 0 CONNECT PAIR AND AUTOMATIC DISCONNECT PARAM. 02 2F
4859 SWI CONNECT MUX 1,15 TO PCT 08, 0
4860 SWI CONNECT PCT 08,0 TO MUX 1, 15
4866 CI-CPU OUT 08 00 30 C7 0A 00 00 28 01 40 01 00 03 02 32 C7 98
PCT COMMAND PCT 06,0 CONNECT PAIR PARAM. 02 31
4869 SWI CONNECT MUX 1,17 TO PCT 06,0
4871 SWI CONNECT PCT 06,0 TO MUX 1,17
4885 CI-CPU OUT 08 00 10 C8 0A 00 00 28 01 40 02 03 02 02 FF 47 9C
PCT COMMAND PCT 06,0 START SENDING DIAL TONE PARAM. 02 FF
361
4889 SWI CONNECT TONE 15 TO PCT 06,1
Extension 2000 (ALC 8, 0) calls extension 2016 (DLC 13,2); RST-KD (6,0/6, 1) is released.
0680 PCC EVENT PCT 06,0 DATA = 00000101
0693 CI-CPU IN 08 40 C0 C6 09 00 00 28 02 40 44 20 00 02 0E 70
PCT EVENT PCT 06,0 DIGIT RECEIVED KEY TONE PARAM. 02
0720 CI-CPU OUT 08 00 01 CC 0A 00 00 38 01 40 01 00 05 02 2F 43 46
PCT COMMAND PCT 08,0 CONNECT SINGLE PARAM. 02 2F
1332 CI-CPU IN 08 40 C0 C7 09 00 00 28 02 40 44 20 00 00 8B 4D
1862 CI-CPU IN 08 40 C0 C8 09 00 00 28 02 40 44 20 00 01 7A 99
2791 CI-CPU IN 08 40 C0 C9 09 00 00 28 02 40 44 20 00 06 3F A7
362
2920 CI-CPU OUT 08 00 10 CE 0C 00 00 62 01 40 0C 1C 00 00 00 02 32 3B FF
PCT COMMAND PCT 13,2 START CALL AND TONE WITH AST PARAM. 00 00 02 32
2923 CI- INT1 B COMMAND 00 62 20 00 PAR. 00
2929 CI-CPU OUT 08 00 30 CF 0E 00 00 62 01 46 05 15 00 02 00 00 00 0F 0F
PCT COMMAND PCT 13,2 EXTENSION DISPLAY CALLING NUMBER PARAM. 02 00 00 00
2940 CI- INT1 C COMMAND 00 62 05 00 PAR. 02 00 00 00 0F 0F
2948 CI-CPU OUT 08 00 10 C0 0A 00 00 28 01 40 01 00 04 02 31 83 92
PCT COMMAND PCT 06,0 DISCONNECT PAIR PARAM. 02 31
2951 SWI CONNECT TONE 01 TO PCT 06, 0
2998 CI-CPU OUT 08 00 30 C1 08 00 00 28 01 40 09 10 56 40 ED
PCT COMMAND PCT 06,0 RELEASE RKT-SDT PORT
3059 CI-CPU IN 08 40 C0 CA 08 00 00 28 02 40 45 08 04 3F 22
PCT EVENT PCT 06,0 READY FOR SEIZURE RKT-SDT
Extension 2016 (DLC 13,2) answers.
2319 CI- INT1 0 EVENT 00 62 13 00
2322 SWI CONNECT MUX 1, 18 TO PCT 13, 2
2323 CI-CPU IN 08 40 C0 CB 08 00 00 62 02 40 40 00 00 76 8F
PCT EVENT PCT 13,2 CALL ANSWER
2325 SWI CONNECT PCT 13,2 TO MUX 1, 18
2349 CI-CPU OUT 08 00 10 C4 08 00 00 62 01 40 09 10 01 1F 69
PCT COMMAND PCT 13, 2 ANSWER ACKNOWLEDGE
2352 CI-INT1 D COMMAND 00 62 0F 00 PAR. 00
363
Extension 2016 (DLC 13,2) activates the enquiry button.
6066 CI-INT1 1 EVENT 00 62 04 00
6069 CI-CPU IN 08 40 C0 CC 08 00 00 62 02 40 40 00 05 07 56
PCT EVENT PCT 13,2 SERVICE BUTTON SHORT OFF
6096 CI-CPU OUT 08 00 10 C6 0A 00 00 62 01 40 01 00 04 02 32 4F D4
PCT COMMAND PCT 13, 2 DISCONNECT PAIR PARAM. 02 32
6176 CI-CPU OUT 08 00 30 C7 0A 00 00 62 01 40 02 03 01 02 FF 27 C7
PCT COMMAND PCT 13, 2 START TONE WITH AUTOMATIC STOP PARAM. 02 FF
Extension 2016 (DLC 13, 2) calls extension 2001 (ALC 8, 1).
1851 CI-INT1 2 EVENT 00 62 01 00 PAR. 02
1855 CI-CPU IN 08 40 C0 CD 09 00 00 62 02 40 44 20 01 02 C1 00
PCT EVENT PCT 13, 2 DIGIT RECEIVED DIAL PULSES PARAM. 02
1890 CI-CPU OUT 08 00 30 C9 0A 00 00 62 01 40 01 00 03 02 33 2B C1
PCT COMMAND PCT 13, 2 CONNECT PAIR PARAM. 02 33
2530 CI-INT1 3 EVENT 00 62 01 00 PAR. 00
2533 CI-CPU IN 08 40 CO CE 09 00 00 62 02 40 44 20 01 00 4F 85
PCT EVENT PCT 13,2 DIGIT RECEIVED DIAL PULSES PARAM. 00
2929 CI-INT1 4 EVENT 00 62 01 00 PAR. 00
364
2932 CI-CPU IN 08 40 C0 CF 09 00 00 62 02 40 44 20 01 00 4B 79
4088 CI-INT1 5 EVENT 00 62 01 00 PAR. 01
4091 CI-CPU IN 08 40 C0 C0 09 00 00 62 02 40 44 20 01 01 BA AD
4222 CI-CPU OUT 08 00 30 CB 0C 00 00 39 01 40 0C 1C 00 00 00 02 34 CC 5C
PCT COMMAND PCT 08,1 START CALL AND TONE WITH AST PARAM. 00 00 02 34
5070 CI-INT1 E COMMAND 03 0C 00 00 PAR. 00
5107 CI-INT1 6 EVENT 03 0C 00 00 PAR. 00 68 C9 00
Extension 2001 (ALC 8,1) answers.
0127 CI-CPU IN 08 40 C0 C1 08 00 00 39 02 40 40 00 00 5B 84
PCT EVENT PCT 08,1 CALL ANSWER
0153 CI-CPU OUT 08 00 30 CD 08 00 00 39 01 40 09 10 01 C2 6D
PCT COMMAND PCT 08,1 ANSWER ACKNOWLEDGE
Extension 2016 (DLC 13,2) goes on-hook (call transfer).
3000 CI-INT1 7 EVENT 00 62 02 00
365
3004 CI-CPU IN 08 40 C0 C2 08 00 00 62 02 40 40 00 02 27 61
PCT EVENT PCT 13,2 CALL CLEARED
3260 CI-CPU OUT 08 00 30 CF 0A 00 00 62 01 40 01 00 04 02 33 92 08
Extension 2001 (ALC 8,1) goes on-hook.
2135 CI-CPU IN 08 40 C0 C3 08 00 00 39 02 40 40 00 02 7B 8F
2171 CI-CPU OUT 08 00 10 C2 0A 00 00 38 01 40 01 00 04 02 2F FB 51
PCT COMMAND PCT 08,0 DISCONNECT PAIR PARAM. 02 2F
2191 CI-CPU OUT 08 00 30 C3 0A 00 00 39 01 40 01 00 04 02 34 87 55
2242 CI-CPU OUT 08 00 10 C4 0A 00 00 38 01 40 02 03 00 12 30 BA D4
PCT COMMAND PCT 08,0 START TONE PARAM. 12 30
366
4093 CI-CPU IN 08 40 C0 C4 08 00 00 38 02 40 40 00 02 CB 84
4130 CI-CPU OUT 08 00 30 C5 08 00 00 38 01 40 03 02 01 6E F4
PCT COMMAND PCT 08,0 STOP TONE
5.6.2. Flow Diagram
This section gives an example of a trace with some necessary interpretation and it shows the
major PM parts and the signal directions.
367
PCC/ PCC/
CL-INT TSC PPU CPU PPU TSC CL-INT
TIME
Extension 2000 (ALC 8,0) goes off-hook; RST-KD (6, 0/6,1) connected.
2000 off-hook (ALC8,0)
4715
Call request
4729
Enable CODEC 8,0
4729
Resources ready
4785
Conn.pair to ALC
4855
Connect1,15 - 8,0
4859
4860 Connect 8,0 - 1,15
Conn.pair to RST-KD
4866
Connect1,17 - 6,0
4869
Connect 6,0 - 1,17
4871
Start DT on RST-KD
4885
Set RST-KD rec. On
4887
Connect DT to 6,1
4889
0010
0030
0050
Extension 2000 (ALC 8,0) calls extension 2016 (DLC 13,2); RST-KD (6,0/6,1) is released.
0680 Digit ‘2’ from RST-KD (6,0)

Digit ‘2’ from (6,0)
0693
Stop DT on RST-KD
0694
Conn. Single to ALC
0720
0722 Connect 1,15 - 8,0
End digit
0808
Digit ‘0’ from RST-KD
1324
1332 Digit ‘0’ from (6,0)
End digit
1469
1855
Continue on next page
368
PCC/ PCC/
TIME
Digit ‘1’ from 6,0
1862
End digit
1970
2779
2791
End digit
2916
St call DLC 13,2
2920
Call to SOPHO-SET
2923
Display calling #
2929
Calling # to SOPHO-SET
2940
....... Connect RT on 1,19
Disconnect RST-KD
2948
Silence on 6,0
2951
Release RST-KD
2998
Set RST-KD to idle
3000
Release KD ready
3059
Silence on 1,18
.......
Extension 2016 (DLC 13,2)answers
20,16 off hook (DLC13,2)

2319
Connect1,18 - 13,2
2322
Call answer 13,2
2323
Connect 13,2 - 1,18
2325
Answer Ack.
2349
Extension 2016 (DLC 13,2)activates the enquiry button

2016 activates enquiry
6066
Enquiry DLC 13,2
6069
Disconnect 13,2
6096
Silence on 13,2
6099
Start DT on 13,2
6176
Connect DT to 13,2
6179
369
PCC/ PCC/
TIME
Extension 2016 (DLC 13,2) calls extension 2001 (ALC8,1).
Digit ‘2’ from SOPHO-SET

1851
Silence on 13,2
1853
1855
Conn. pair to DLC
1890
Connect1,19 - 13,2
1894
Connect13,2 - 1,19
1896
2530
2533
2929
2932
4088
4091
4222 St call ALC 8,1
Ringing on ALC 8,1
4225
....... Conn. RT on 1,20
Ringing off ALC 8,1
5219
....... Silence on 1,20
Extension 2001 (ALC 8,1) answers.

2000 off-hook ( ALC 8,1)
0113
Acknowledge
0125
0126 Connect 1,20 - 8,1
Call answer
0127
Enable CODEC 8,1
0128
Connect 8,1 - 1,20
0130
Answer ack
0153
370
PCC/ PCC/
TIME
Extension 2016 (DLC 13,2) goes on-hook (call transfer)
2016 on-hook
3000
Silence to 13,2
3002
13,2 call cleared
3004
Disconnect pair
3260
Silence to 13,2
3263

2001 on-hook (ALC 8,1)
1842
Silence to 8,1
2133
8,1call cleared
2135
Disable 8,1 CODEC
2135
Disconnect pair 8,0
2171
Silence to 8,0
2174
Disconnect pair 8,1
2191
Silence to 8,1
2195
Start BT to 8,0
2242
Busy tone to 8,0
2246
Silence to 8,0
2743
Busy tone to 8,0
3242
Silence to 8,0
3742
Extension 2000 (ALC 8,0) goes on-hook

2000 on-hook
3808
Silence to 8,0
4092
8,0 call cleared
4093
Stop tone 8,0
4130
Disable 8,0 CODEC
4132
4133 Silence to 8,0
E nd
5.7. I/O BUS OBSERVER EXAMPLE 2 - DDO CALL
This section gives the observation of a simulated DDO call via an ATU-SS01 as illustrated in
Figure 5-6 Situation Outline. Extension 37215 initiates and releases a DDO call to extension
37214 via an ATU-SS with impulse signalling.
371
‘00’ ATU-SS
(15,0)
DNR 37215
ALC
DNR 37214
Figure 5-6 Situation Outline
The trace starts when the ATU-SS is seized: extension 37215 has dialled the trunk access code
('00').
On the right hand of the trace a column is given to mark the number dialled (37214) and to
give the operation of the I- and S-relays.
More details of the commands and messages of the ATU-SS01 is given in appendix B .
SIGNALLING, COMMANDS & MESSAGES.
Ready for observing the I/O - Bus

REMARKS
Extension 37215 has dialled the trunk access code (’00’); the ATU-SS is seized.
8533 PCC COMMAND PCT 15,0 DATA = 01101110 Operate I-relay, disable CODEC
8736 PCC EVENT PCT 15,0 DATA = 01000000 call detector detects ring pulse
Enable CODEC
Extension 37215 starts dialling the number 37214.

Operate S-relay
digit ‘3’
Release S-relay
372
5174 PCC COMMAND PCT 15,0 DATA = 01100100 operate S-relay
8339 PCC COMMAND PCT 15,0 DATA = 01110100 digit ‘7’
3135 PCC COMMAND PCT 15,0 DATA = 01101100 release S-relay
digit ‘2’
operate S-relay, digit ‘1’
1090 PCC COMMAND PCT 15,0 DATA = 01110100 digit ‘4’
9062 PCC EVENT PCT 15,0 DATA = 00000000 release S-relay
Extension 37215 goes on-hook

0826 PCC COMMAND PCT 15,0 DATA = 01111100 release I-relay
0835 PCC COMMAND PCT 15,0 DATA = 01111110 Disable CODEC
373
5.8. I/O BUS OBSERVER EXAMPLE 3 - DTU-CA
5.8.1. Set-up
When one wants to observe the commands and messages between the DTU-CA, PPU and
CPU it is necessary to know the data format of the DTU-CA to select the correct setting of
the I/O bus observer; see Figure 5-7 Commands and Messages between the DTU-CA, PPU
and CPU.
The DTU-CA data format is given in the table in Figure 5-8 DTU-CA Data Format and I/O Bus
Observer Selections - part 1and Figure 5-9 DTU-CA Data Format and I/O Bus Observer
Selections - part 2at the end of this chapter.
Select ‘CPU-PCT/VCT Select ‘PCC’

messages messages
CPU PPU DTU-CA

PCT Commands MDF
Call
Control PCT Events
PCC Commands COD0 Outgoing 2Mbit/s
PCT Events Incoming 2Mbit/s
CPU Command,board x CODI
(TS0.....17) (TS0.....31)
Error CPU Event,board x
Signalling
Select ‘CPU board’

messages
Figure 5-7 Commands and Messages between the DTU-CA, PPU and CPU
The set-up for observing a DTU-CA is as follows:
SOPHO-S I/O-BUS OBSERVER Software rel. 10.18 date. 88-3-22
Do you want the CPU-PCT/VCT messages (Y/N) N
374
Do you want the CPU-SNC messages (Y/N) N
Do you want the hex. codes also (Y/N) N
Do you want the PCC messages (Y/N) Y
Do you want them of all PCT nmbrs (Y/N) N
Define the PCT numbers from which you want the PCC messages.
Example: BOARD 7 CIRCUIT 0 and BOARD 12 CIRCUIT 0 up to and including 5
07,0 07,0 12,0 12,5CR
13,0 13,0 15,0 15,1
Do you want the TSC messages (Y/N) N
Do you want the CI-INT messages (Y/N) N
5.8.2. Various Error Situations
This section gives the DTU-CA traces of a number of error situations like CRU cable removed
and replaced, remote DTU-CA taken out of service and back to in service, coax cable
removed and replaced at local DTU-CA.
CRU cable removed (to create a frame slip) and replaced.
CRU cable removed to create a frame slip; 2.5 minutes later.
375
0989 CPU EVENT BOARD 13 DTU ALARM EVENT PARAM. 04 01
3075 CPU COMMAND BOARD 13 GIVE DTU ALARM INFO
3079 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 04 00 00 00 D0
Again 2.5 minutes later.
CRU cable is replaced.
1019 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 04 00 D0 00 D0
RESTART REQUESTED
CRU cable again removed, but replaced after a longer period.
376
RESTART REQUESTED
Increased periodic test frequency of the remote DTU-CA.
377
5044 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 09 00 DO 00 D0
2426 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. FF 00 FO 00 F0
Synchronization alarm given here; alarm code 061, qualifier 013.
3768 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 09 00 FO 00 F0
3957 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. FF 00 DO 00 D0
378
6540 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. FF 00 FO 00 F0
3957 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 09 00 FO 00 F0
RESTART REQUESTED etc.
Remote DTU-CA taken out of service.
379
5607 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 01 00 DO 05 FF
5936 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. FF 05 FF 05 FF
RESTART REQUESTED
Remote DTU-CA back in service.
380
5821 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 00 05 FF 05 FF
381
6051 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 00 00
4758 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 00 05 FF 00 D0
RESTART REQUESTED
Coax cable removed at local DTU-CA.
382
5046 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 00 00 D0 11 FF
5355 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. FF 11 FF 11 FF
RESTART REQUESTED
383
Coax cable replaced at local DTU-CA.
384
3342 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. 02 11 FF 00 D0
3811 CPU EVENT BOARD 13 DTU ALARM INFO EVENT PARAM. FF 00 D0 00 D0
RESTART REQUESTED
5.8.3. Outgoing Call with Backward Release
2473 PCT COMMAND PCT 14,3 OUTGOING SEIZURE
385
2495 PCT COMMAND PCT 14,3 CONNECT PAIR PARAM. 02 0B
3524 PCT EVENT PCT 14,3 SEIZURE ACKNOWLEDGE PARAM. FF
4821 PCT COMMAND PCT 14,3 TRANSMIT OF DIGIT PARAM. 01
4984 PCT EVENT PCT 14,3 TRUNK TRANSMIT DIGIT ACKNOWLEDGE PARAM. FF
386
0160 PCT EVENT PCT 14,3 NUMBER COMPLETE RECEIVED PARAM. FF
5476 PCT EVENT PCT 14,3 ANSWER RECEIVED PARAM. FF
1974 PCT EVENT PCT 14,3 BACKWARD RELEASE RECEIVED PARAM. FF
2015 PCT COMMAND PCT 14,3 DISCONNECT PAIR PARAM. 02 0B
2030 PCT COMMAND PCT 14,3 FORWARD RELEASE
3081 PCT EVENT PCT 14,3 TRUNK IDLE
387
5.8.4. Outgoing Call with Forward Release
5662 PCT COMMAND PCT 14,3 OUTGOING SEIZURE
5680 PCT COMMAND PCT 14,3 CONNECT PAIR PARAM. 02 0C
0167 PCT EVENT PCT 14,3 SEIZURE ACKNOWLEDGE PARAM. FF
388
3040 PCT EVENT PCT 14,3 NUMBER COMPLETE RECEIVED PARAM. FF
2918 PCT EVENT PCT 14,3 ANSWER RECEIVED PARAM. FF
2777 PCT COMMAND PCT 14,3 DISCONNECT PAIR PARAM. 02 0C
2837 PCT COMMAND PCT 14,3 FORWARD RELEASE
389
5.8.5. Incoming Call with Backward Release
2683 PCT EVENT PCT 13,1 INCOMING SEIZURE PARAM. FF
2791 PCT COMMAND PCT 13,1 SEND PROCEED TO SEND
2803 PCC COMMAND PCT 13,1 CONNECT PAIR AND AUTOMATIC DISCONNECT PARAM.
2815 PCC COMMAND PCT 13,1 START TONE WITH AUTOMATIC STOP PARAM. 02 FF
390
4521 PCT EVENT PCT 13,1 DIGIT RECEIVED DIAL PULSES PARAM. 02
4559 PCT COMMAND PCT 13,1 CONNECT PAIR PARAM. 02 31
5668 PCT COMMAND PCT 13,1 SEND NUMBER COMPLETE
5688 PCC COMMAND PCT 13,1 CONNECT PARAM. 02 31
0125 PCC COMMAND PCT 13,1 SEND ANSWER
4214 PCT COMMAND PCT 13,1 DISCONNECT PARAM. 02 31
4264 PCT COMMAND PCT 13,1 CLEAR BACK
4247 PCT COMMAND PCT 13,1 START TONE PARAM. 06 21
391
5015 PCT EVENT PCT 13,1 FORWARD RELEASE RECEIVED PARAM. FF
5133 PCT COMMAND PCT 13,1 RELEASE ACKNOWLEDGE
5143 PCT COMMAND PCT 13,1 STOP TONE
5.8.6. Incoming Call with Forward Release
4610 PCT EVENT PCT 13,1 INCOMING SEIZURE PARAM. FF
4710 PCC COMMAND PCT 13,1 SEND PROCEED TO SEND
4728 PCT COMMAND PCT 13,1 CONNECT PAIR AND AUTOMATIC DISCONNECT PARAM.
392
4747 PCT COMMAND PCT 13,1 START TONE WITH AUTOMATIC STOP PARAM. 02 FF
0602 PCT COMMAND PCT 13,1 SEND NUMBER COMPLETE
393
0183 PCT COMMAND PCT 13,1 SEND ANSWER
2198 PCT EVENT PCT 13,1 FORWARD RELEASE RECEIVED PARAM. FF
2240 PCT COMMAND PCT 13,1 DISCONNECT PAIR PARAM. 02 33
2254 PCT COMMAND PCT 13,1 RELEASE ACKNOWLEDGE
The figures on the following pages form one table.
394
CPU Message Selection PCC Event Lay Out
UG0 UG1 UG2 UG3 (DTU PPU)
Select CPU Board Messages X3 X2 Y X1 M M M M
3,1 1,1 7,1 5,1 11,1 9,1 15,1 13,1 d c TS17 b a d c TS1 b a
3,2 1,2 7,2 5,2 11,2 9,2 15,2 13,2 TS18 TS2
3,3 1,3 7,3 5,3 11,3 9,3 15,3 13,3 TS19 TS3
3,4 1,4 7,4 5,4 11,4 9,4 15,4 13,4 TS20 TS4
3,5 1,5 7,5 5,5 11,5 9,5 15,5 13,5 TS21 TS5
3,6 1,6 7,6 5,6 11,6 9,6 15,6 13,6 TS22 TS6
3,7 1,7 7,7 5,7 11,7 9,7 15,7 13,7 TS23 TS7
4,0 2,0 8,0 6,0 12,0 10,0 16,0 14,0 TS24 TS8
4,1 2,1 8,1 6,1 12,1 10,1 16,1 14,1 TS25 TS9
4,2 2,2 8,2 6,2 12,2 10,2 16,2 14,2 TS26 TS10
4,3 2,3 8,3 6,3 12,3 10,3 16,3 14,3 TS27 TS11
4,4 2,4 8,4 6,4 12,4 10,4 16,4 14,4 TS28 TS12
4,5 2,5 8,5 6,5 12,5 10,5 16,5 14,5 TS29 TS13
4,6 2,6 8,6 6,6 12,6 10,6 16,6 14,6 TS30 TS14
4,7 2,7 8,7 6,7 12,7 10,7 16,7 14,7 TS31 TS15
- - - - - - - - 0 N5 N4 N3 N2 N1 I2 I1
Select CPU Board Messages WD LTU CLK SLI ER AIS RA FA
Select CPU-PCT/VCT Messages
LEGEND
X1...3 = Spare bits. LTU = LTU alarm detected.
Y = Remote alarm indication. CLK = Clock error detected.
M...M = All ‘0’ indicates frame alignment ok. SLIP = Slip detected.
TS1...15 = External time slots. ERR = Excessive error rate detected.
TS17...31 = External time slots. AIS = AIS detected.
N1...N5 = Bits for national use. RA = Remote alarm detected.
I1...I2 = Bits for international use. FA = Loss of frame alignment
WD = Watchdog alarm.
Figure 5-8 DTU-CA Data Format and I/O Bus Observer Selections - part 1
395
CODI/ PCC Command Lay Out PCC Message
CODO (PPU DTU) UG0 UG1 UG2 UG3
TS0 X3 X2 Y X1 M M M M 1,0 5,0 9,0 13,0
TS1 d c TS17b a d c TS1 b a 1,1 5,1 9,1 13,1
TS2 TS18 TS2 1,2 5,2 9,2 13,2
TS3 TS19 TS3 1,3 5,3 9,3 13,3
TS4 TS20 TS4 1,4 5,4 9,4 13,4
TS5 TS21 TS5 1,5 5,5 9,5 13,5
TS6 TS22 TS6 1,6 5,6 9,6 13,6
TS7 TS23 TS7 1,7 5,7 9,7 13,7
TS8 TS24 TS8 2,0 6,0 2,0 14,0
TS9 TS25 TS9 2,1 6,1 10,1 14,1
TS10 TS26 TS10 2,2 6,2 10,2 14,2
TS11 TS27 TS11 2,3 6,3 10,3 14,3
TS12 TS28 TS12 2,4 6,4 10,4 14,4
TS13 TS29 TS13 2,5 6,5 10,5 14,5
TS14 TS30 TS14 2,6 6,6 10,6 14,6
TS15 TS31 TS15 2,7 6,7 10,7 14,7
TS16 Z N5 N4 N3 N2 N1 I2 I1 3,0 7,0 11,0 15,0
TS17 RST TM X LPT LP0 AIS RA TST 3,1 7,1 11,1 15,1
TS18....31 are not used.
LEGEND
X1...3 = Spare bits. TM = Set test mode.
Y = Outward remote alarm bit.. Z = Spare.
M...M = Fixed ‘0’ in SW.. LPT = Close test loop.
TS1...15 = External time slots. LP0 = Close test loop 0.
TS17...31 = External time slots. AIS = Transmit AIS.
N1...N5 = Bits for national use. RA = Transmit remote alarm.
I1...I2 = Bits for international use. TST = Test alarm indications.
RST = Reset DTU.
Figure 5-9 DTU-CA Data Format and I/O Bus Observer Selections - part 2
396
6. DUAL I/O BUS OBSERVER
6.1. INTRODUCTION
The Dual I/O bus observer (DIO) is a tool to observe the data on the I/O in the SOPHO ISPBX
system. The I/O bus is a proprietary bus used for communication between the PPU and other
PM boards in the PM shelf.
Note: The Dual I/O bus observer can only be used in the PM2500 and PM1000.
The DIO consists of an observer board which is placed in the PM shelf on a position where
the I/O bus to be traced is available, and a PC which is connected to the observer board.
An extension board can be used to connect a possible second I/O bus to observer board to
observe the other I/O bus of the PPU. In this case the data of both I/O busses can be traced,
but concurrent I/O bus activity is not allowed.
The interface to the I/O bus contains a hardware FIFO buffer in which the data from the I/O
bus is stored together with the high and low address and a number of status signals. Data
entering the FIFO can be selected on the high and low address by means of the hardware
registers controlled by the processor. The processor reads the data from the FIFO and by
processing this data a message is generated which can be sent to the PC.
The DIO has a red and a green LED; the meaning is given in Table 6-1 Meaning of the Red and
Green LED.
RED GREEN MEANING

OFF OFF No power
OFF ON Operational
OFF WINKING Data still present in FIFO
buffer
ON OFF Error/power up/self-test
ON ON Operational/Wait for PC init
data
Table 6-1 Meaning of the Red and Green LED
397
Mark
BP
X2.1
103 101
FA (EXT-IOBUS)
BA
FBB (V36)
X2.2
X3.1
103 101
101 108
201 208 X1.1
102 101 BP
FCD (RS232)
Figure 6-1 Jumper Positions (default situation)
Strap settings
- X1.1 not placed (OFF) : DIO using smt 84C00 (default)

when placed (ON) : DIO using leaded 84C00
- X2.1 placed on 101-102 : CPU clock of 4.9 MHz (default)
placed on 102-103 : CPU clock of 2.45 MHz
- X2.2 placed on 102-103 : when X1.1 is OFF (default)
placed on 101-102 : when X1.1 is ON
- X3.1 X3.1 not used (lab environment only)
398
6.2. INTERFACE AND CABLING
The connectors are used to connect the following:
- FA : I/O Bus 1
- FBB : not used (lab environment only)
- FCD : PC connection: 600, 1200, 4800, 9600 or 19200 Baud serial path
(RS232).
- BA : I/O Bus 0
- BP : not used (lab environment only)
- EEB : on board connector (X3.1); not used (lab environment only)
The pin numbers and their signal meaning are given in the following tables.
399
PIN NUMBER SIGNAL PIN NUMBER SIGNAL
FA CONNECTORS I/O BUS 1
101 NBRDY 301 ground
102 OCS 302 ground
103 W/R 303 ground
104 C/D 304 ground
105 ground 305 ground
107 ground 307 ICS
108 ground 308
109 ground 309
110 DAT7 310
111 DAT6 311
112 DAT5 312
113 DAT4 313
114 DAT3 314
115 DAT2 315
116 DAT1 316
117 DAT0 317
FCD CONNECTOR (RS232)
101 301
102 Ground 302 ground
103 TXD-B 303
105 RXD-B 305
107 307
Table 6-2 Front Connectors
400
BA-CONNECTOR I/O BUS 0
101 DAT0 301 DAT1
103 DAT2 303 DAT3
105 DAT4 305 DAT5
107 DAT6 307 DAT7
108 308
109 309
110 310
111 311 BRDY
113 C-ND 313 W-NR
115 NOCS 315 ICS
116 ... 129 316...329
130 +5V (PM) 330
131 +5V (PM) 331
132 +5V(PM) 332
Table 6-3 Back Panel Connectors
401
X 3.1.-CONNECTOR
101 Strobe (act low) 201 DAT0
102 NBIST 202 DAT1
103 203 DAT2
104 +5V 204 DAT3
105 205 DAT4
106 206 DAT5
107 207 DAT6
108 ground 208 DAT7
Table 6-4 On-board Connector
402
Terminal
side
1
14
YW / BLK -2 I/O bus
side
BU / BLK -3 301 - GY/BLK
GY / BLK -4 101 - RD/BLK
102 - RD
GR / BLK -5 303 - WT/BLK
103 - BL/BLK
Seen from wiring side
RD -7 305 - PK/BLK
RD/BLK -20 105 - YW/BLK
BR/BLK -20
WT/BLK -20
PK/BLK -22 307 -BR/BLK
107 - GN/BLK
25
13
25-pole male F122-

D-connector connector
7 RD 102 - GND RD 102
2 YW/BLK 103 - TXD BL/BLK 103
3 BL/BLK 104 - RXD YW/BLK 105
5 GN/BLK 106 - CTS GY/BLK 301
4 GY/BLK 105 - RTS GN/BLK 107
20 RD/BLK 108/2 - DTR PK/BLK 305
22 PK/BLK - RI RD/BLK 101
6 107 - DSR WT/BLK 303
8 109 - DCD BR/BLK 307
Figure 6-2 Pin Numbering of PC - DIO Cable
6.3. INSTALLATION
PROCEDURE:
The DIO board must be placed in the PM of which the commands and messages are to be
observed.
Actions
403
- First check the strap setting on the board;Figure 6-1 Jumper Positions (default situation).
- Place the DIO board in the PM shelf in position 20, 21, 23 or 24.
- Switch on the PC.
- Set the terminal characteristics and select the baud rate.
- Connect the PC to the front connector FCD on the DIO; for the pin numbering of the
connectors,Figure 6-2 Pin Numbering of PC - DIO Cable.
- Establish the communication between the PC and DIO.
6.4. MAIN MENU
The human interface of the DIO is menu driven. The DIO is started by pressing the space bar
a number of times. The main menu is automatically entered and displayed; it comprises the
following options:
SOPHO DUAL IO-BUS OBSERVER

SOFTWARE RELEASE 13.0 26 JUNE 1992
(ESC = OPERATIONAL RESTART REQUEST)

(CTRL-B = PREVIOUS QUESTION REQUEST)
1 = New selection of all

2 = Adjust selections
3 = Trigger settings
4 = Redisplay of buffer
5 = Clear buffer
6 = New baud rate
7 = Hard reset
O = Continue observing
D = Display settings
This announcement indicates a correct functioning of the observer.
• New selection of all

The I/O bus observer is set by just answering questions. The observer can be set to trace
all hardware 10 devices to your own needs. When using this option, some sub-settings get
fixed default values, e.g. selection of flow types when displaying ISDN messages.
• Adjust selections
The fixed default values and other special settings, like I/O bus trace, can only be selected
using this menu; see section 6.4.1. Adjust Selections Menufor detailed description.
404
• Trigger settings
When using this option the observer checks all I/O bus messages for equality against user
defined trigger strings. If equal the observer starts a pre-selected action, like starting to
display the received messages; see section 6.4.2. Trigger Settings for detailed description.
• Redisplay of buffer
The contents of the software FIFO buffers is re-scanned and displayed. So when you have
changed the settings in between, different messages might be displayed: the oldest
messages are displayed first.
• Clear buffer
All stored messages are deleted: all hardware and software FIFO buffers are empty and
the timer for the time stamps is reset to zero.
• New baud rate
When another baud rate is wanted the observer does not have to be removed from the
shelf. Select another baud rate and press the space bar a number of times.
• Hard reset
All settings are cleared and the observer restarts.
• General Options
continue observing : to resume observing after interrupting the output display;
display settings : to see which selections are active; the ranges are also displayed;
control B : return to a previous question;
control T : toggle function to switch the 10 seconds time stamp on or off;
ESCape : with the ESC-key the observer always returns to the main menu;
Exit: return to a previous menu.
• Common remarks for range settings
When you want to observe the CPU-PCT.VCT (virtual circuit), the Peripheral Circuit
Controller (PCC) and the Time Switch (TSW) messages to/from a particular PCT you
must specify that PCT as follows:
- board position : always two digits, so do not forget a leading zero if applicable.
- circuit number: one digit (0 ... 7); if you gave a non existing number you have to resume
with <ESC>.
Selection of a range of PCT numbers is done as follows:
- range 1 : first PCT number ... last PCT number
- range 2 : first PCT number ... last PCT number ... <CR>
Maximum seven different ranges per resource (PCT, BOARD, TSW, etc.) can be selected.
For example: board 7 circuit 0 and board 12 circuit 0 up to and including 5 are entered as
follows:
07, 0 07, 0 12, 0 12, 5 <CR>
For the DIO a board has maximum 8 circuits. So in case the CPU-PCT messages of a board
with 9 or more circuits have to be observed, the circuits have to be specified as follows:
- DTU-CA/PU (with 30 circuits) in board position 1:
01,0 04,7 <CR>(for PCC messages see 6.4.1. Adjust Selections Menu)
405
• ALC-F (with 16 circuits) in board position 5:
05,0 06,7 <CR>
• It is also possible to observe the messages of one of these circuits, for example circuit 9 of
an ALC-F on board position 5: 06,0. .06,0 <CR>
Note: When you use the CPU-PCT/VCT selection to switch the messages (on/off), the ranges
remain unchanged. The same applies for the CPU-BOARD ranges.
Port type VCT is used with DPNSS only.
With 'CPU OFF' all CPU messages will not be displayed anymore. However the subsettings
are not changed. So later selection of this menu e.g. CPU enabled and then O (continue
observing) continues in the same CPU settings.
6.4.1. Adjust Selections Menu
With this menu you can select each message separately; the following menu is shown:
1 = CPU-PPU
2 = PCC (PCC=Peripheral Circuit Controller)
3 = CI (CI=Communication Interface)
4 = TSW (TSW=Time SWitch)
5 = ADC (ADC=Automatic Disconnect Circuit)
6 = ATC (ATC=Add-on and Tone generation
Controller)
7 = DTU-CC
8 = Process stimuli
9 = Transparent display
A = I/O bus dump

Ø = Exit
• CPU-PPU Messages Menu

With the CPU-PPU messages you can select the different CPU messages; the following
menu is shown:
406
1 = CPU-PCT/VCT
2 = CPU-PCT/VCT circuit
ranges
3 = CPU-BIC (BIC=Break-In Circuit)
4 = CPU-SNC (SNC=Switching Network Circuit)
5 = CPU-BOARD
6 = CPU-BOARD ranges
7 = CPU-PMCP (PMCP=PPU Control Process)
8 = CPU-ISDN
C = CPU off
Ø= Exit
- CPU-ISDN Menu
With the 'CPU-ISDN' messages menu you can select the 'CPU-ISDN' messages
separately; the following menu is shown:
1 = CPU-INW (INW=Internal NetWork layer or flow

type INW)
2 = CPU-SIG (SIG=SIGnalling messages)
3 = CPU-MAN-SE (MAN-SE=Management SErvice
messages)
4 = CPU-MAN-AL (MAN-AL=Management ALarm messages)
5 = CPU-MAN-TR (MAN-TR=Management TRace messages)
6 = CPU-MAN-SP (MAN-SP=Management Switch & Port
messages)
7 = CPU-DAT (DAT=Flow type used for end-to-end
messaging)
8 = CPU-IDL info (IDL=Internal Data Link layer; layer
2b)
G = All types on
H = All types off
I = CPU-ISDN off
Ø= Exit
All selections 1...8 are toggle selections. For example when you choose CPU-INW while
407
these messages are ON yet, the display of CPU-INW is switched OFF (and vice versa).
With 'All types on' all flow types and the IDL info will be selected to be displayed. With 'All
types off' the display of any flow message or IDL info will be switched OFF. With 'CPU-
ISDN off' the display of any CPU-ISDN message is deselected, however the individual
settings will be kept, so later enabling of the CPU-ISDN will come up in the same settings.
• PCC Messages Menu

For the PCC messages to and from the digital boards (DTU-CA/DTU-PU) the range
setting is special, because just four PCC-bits are used.
- The four PCC-bits for the relative PCT numbers 1 ... 15 are put in the four least
significant bits within the PCC-bytes of the concerned PCT numbers 1 ... 15.
- The four PCC-bits for the relative PCT numbers 17 ... 31 are put in the four most
significant bits within the PCC-bytes of the concerned PCT numbers 17 ... 31.
• CI Messages Menu
With the CI messages menu you can select the CI devices from which you want to see the
messages; the following menu is shown:
1 = CI-DIG A
2 = CI-DIG B
3 = CI-DIG C
4 = CI-INT
5 = Channel select
Ø = Exit
For the correct settings of the CI channels the following configuration aspects apply:
- In case a PSC-A/B/C/D/E/F is used in the PM shelf just four CI channels are available.
You can select them with 'CI-DIG A' and 'CI-TNT' (CH 1, 2, 7 and 8).
- In case a PSC-G is used in the PM shelf there are eight CI channels.
The relation between the CI-channel and the board you want to observe is given in
Table 6-5 Relation between CI-channel and Board Position.
408
CI-CHANNEL PCT BOARD POSITION
CI-DIG A CH. 1 0 up to 7
CI-DIG A CH. 2 0 up to 7
CI-DIG B CH. 3 8 up to 15
CI-DIG B CH. 4 8 up to 15
CI-DIG C CH. 5 8 up to 15
CI-DIG C CH. 6 8 up to 15
CI-INT CH. 7 up to 15
CI-INT CH. 8 0 up to 15
Table 6-5 Relation between CI-channel and Board Position
- First the CI-DIG channels will be used if they are available.

- In case the CI-DIG channels are occupied, the CI-INT channels will be used.
- The boards using CI communication with the PPU will be assigned starting with the
lowest board number. For example boards 0, 2, 4, 6, 8, 12 and 14 are boards using CI-
communication, the relation between the board and CI-channel as given in Table 6-6
Relation between Board Number and CI-channel exists.
BOARD NUMBER CI-CHANNEL

0 CI-DIG A CH. 1
2 CI-DIG A CH. 2
4 CI-INT CH. 7
6 CI-INT CH. 8
8 CI-DIG B CH. 3
12 CI-DIG B CH. 4
14 CI-DIG C CH. 5
Table 6-6 Relation between Board Number and CI-channel
You can determine if you want the messages translated or not. If you select a CI device to
be displayed untranslated, no more selection can be done because the complete CI (chip)
device is displayed transparently.
The settings for the different IMP channels is done via 'Channel select' menu.
409
• CI 'Channel Select' Menu
With the CI Channel select menu you can select the channels from which you want to see
the CI messages; the following menu is shown:
1 = CI-DIG A CH. 1
2 = CI-DIG A CH. 2
3 = CI-DIG B CH. 3
4 = CI-DIG B CH. 4
5 = CI-DIG C CH. 5
6 = CI-DIG C CH. 6
7 = CI-INT CH. 7
8 = CI-INT CH. 8
9 = All CI channels equal settings
Ø = Exit
Formatting of these messages to be displayed can be selected via the following menu:
1 = Transparent display
2 = L2 formatting only
3 = Flow type (ISDN, TMP, DPNSS)
4 = Port type (DASS/DPNSS)
- Transparent display : all IMP messages are displayed without any formatting.
- L2 formatting only : all flow oriented messages are displayed in a simple formatted
way.
- Flow type : any flow oriented message is scanned, translated and formatted
according to the selection given in the following toggle menu:
410
1 = CI-INW
2 = CI-SIG
3 = CT-MAN-SE
4 = CT-MAN-AL
5 = CI-MAN-TR
6 = CI-MAN-SP
7 = CI-DAT
8 = CI-TMP-P
9 = CI-TMP-B
A = CI-DPNSS-R ( -R=for Real data links)
B = CI-DPNSS-V ( -V=for Virtual data links)
C = CI-IDL info
G = All types on (normally used)

H = All types off
I = CI-flow type messages
off
Ø= Exit
Via this menu the different flow types and IDL info can be selected via toggle options. TMP
flow types are displayed transparently, DPNSS flow types are translated like DPNSS
messages while the other flow types are translated like ISDN messages.
When the CI channels are set equal via the All CI channels equal settings' option, the board
position and board type are always requested, even when only the CI-INT is selected.
Finally you can select the board position (1 ... 16) and board type (OIU, DLC, IPH, DTU-
BA, DTU-PH) for which the CI channel is used. This is only necessary for the CI-DIGs so
the settings are not required for CI channels 7 & 8 (CI-INT).
• Process Stimuli Messages Menu

This option is for lab use only.
6.4.2. Trigger Settings
The I/O bus has the possibility to set triggers. When using this option the observer checks all
I/O bus messages for equality against the user defined trigger strings. If equal the observer
starts a pre-selected action, like starting to display received messages.
When you select Trigger Settings, the following menu is shown:
411
1 = Set switch ON trigger string
2 = Set switch OFF trigger string
6 = Single history trace
7 = Multiple observer trace
8 = History & continued trace
9 = Start observing after trigger
A = Display trigger ON string

B = Display trigger OFF string
Ø= Exit
• Setting trigger string

By choosing 1 or 2 you can select either a switch ON or switch OFF trigger string. The
ON trigger is used for switching the I/O bus observer from waiting to display status, while
the switch OFF trigger is used to define the condition on which the I/O bus observer
switches from display to waiting status (waiting for switch ON trigger again).
• Display of trigger string

With the display of the trigger strings, the strings can be user checked. The strings are
displayed as binary values no matter how they were defined and their meaning. Defined
CPU message triggers are displayed as full CPU message strings, inclusive bytes like form,
signal id, etc.
• Starting triggered I/O bus observing

The I/O bus observer starts observing without display of messages, until the switch ON
trigger is found; the I/O bus observer can be started in the following trigger modes:
- Single history trace : a history redisplay is started.

At the end of the redisplay the observer will stop
and wait for user (keyboard) input.
- Multiple observer trace : normal displayed observing is started.
When the trigger OFF string is found the observer
will stop the display of messages and again first wait
for a switch ON trigger string, etc.
- History & continued trace : a history redisplay is started and normal continued
observing is started.
- Start observing after trigger : normal observing with message display is started.
For the trigger option the following notes apply:

- The output of the observer during triggered operation fully depends on the selection
412
made via the 'selection menus', so first set your selection before selecting a triggered
operation.
- The observer checks all I/O bus messages, also those messages which are not selected
to be displayed; for example you can trigger on a CPU message, but the message itself
is not displayed.
- When a message equal to the switch ON string is found, <***Trigger***>is displayed.
- When a message equal to the switch OFF string is found, no special message will be
generated. When in the 'Multiple Observer trace', the occurrence can be seen via the
prompt 'Waiting for trigger . . .'.
- When using the dual I/O bus observer, the 10 seconds time stamp is displayed even
when waiting for a trigger ON situation. By these time stamps you can determine how
long it took before the trigger ON situation occurred.
413
7. PM OBSERVER
7.1. INTRODUCTION
The PM Observer is meant for observation of the internal communication paths between the
SOPHO ISPBX boards. It is meant as a tool for fault tracing and replaces various tasks of the
I/O bus observer and Dual I/O bus observer for ISPBX's 'without' an I/O bus. Detailed
descriptions of the applications of the PM Observer can be found in the section 7.3.
INSTALLATION.
The PM Observer consists of two parts: a printed circuit board and a software package for an
IBM compatible Personal Computer which is connected to the observer board.
The main functions of the PM Observer are:
- Observing communication via CODI/CODO (e.g. ATUs, ALCs, KTLC).

(64kb/s channels used for controlling the PCTs)
- Observing communication via USO/USI (e.g. DLCs, DTXs, DTUs).
(64kb/s IMP channels or bit oriented protocols)
- Observing the CPU-PPU communication.
The PM Observer has a red and a green LED; the meaning is given in the table below.
RED GREEN MEANING

Off Off No power
On Off Internal test is active
On On Waiting for PC commands
Off On Observer mode
Off Blinking Local mode
Blinking On Firmware absent
Table 7-1 Meaning of the Red and Green LED
Straps and DIP switches are available to select the following modes:
- Observer mode (used for diagnostics);

- Download mode;
For firmware downloading via the PM bus, the PM Observer can communicate with the
414
PM in IMP/HDLC via USO/USI at a PCT position. See 7.6. DOWNLOADING THE
FIRMWAREfor more information.
- Vakans mode.
This mode was developed for a special application (Vakans). For diagnostics this mode is
not used !
APPLICATION DIP SWITCH

1 2 3 4 5 6 7 8
Observer mode (factory OFF OFF OFF OFF OFF OFF OFF OFF
setting)
Download mode OFF OFF OFF OFF OFF ON OFF OFF
'Vakans' in other ISPBXs OFF OFF OFF OFF OFF OFF ON ON
than SSW 300 and
Product Releases 200/
205
'Vakans' in SSW 300 and OFF OFF OFF OFF OFF OFF OFF ON
Product Release 200/205
Table 7-2 DIP Switch Settings
Mark
X4.1
108 101
208 201 BP
Bist connector
FA
BA
Off On
1
FB
BB
8
S1-1
201 101
X6.2
OM-VDU
Reset Switch 208 108

X6.1
MPC X3.1
Figure 7-1 Location of DIL Switches and Jumper Pads
Strap settings
- X3.1 place straps 101-201 to 108-208 if a DCC (DECT Controller Card) is placed on the
415
PM Observer board. So the PM Observer is used as card extender.
Note: X4.1 is not a strap position but a BIST connector which is used for factory testing.
7.2. INTERFACES AND CABLING
The PC-PM Observer serial link specifications are as follows:
- XON/XOFF protocol;
- Baudrate 4800, 9600, 19200;
- COM 1 to COM 4 are supported;
- No CRC generation;
- data transfers byte oriented;
- Full duplex.
There are two V.24 connectors (F122 connectors):
- One for connecting a PC via the standard MPC (CPU-ME/MT/VIC - MPC) cable.
- One for connecting a PC via the standard OM-VDU (CIx - VDU) cable.
The V.24 interface can handle data with asynchronous baudrates up to 19200 bit/s.
DTE/DCE CIRCUIT NAME CONNECTOR IN- OR

CIRCUIT OUTPUT
104 RECEIVED DATA .(RXD) 103 IN
106 READY FOR SENDING (CTS) 105 # IN
108 DATA TERMINAL READY (DTR) 107 OUT
103 TRANSMITTER DATA (TXD) 301 OUT
102 SIGNAL GROUND (SG) 302 -
105 REQUEST TO SEND (RTS) 303 ! OUT
107 DATA SET READY (DSR) 305 IN
109 DATA CARRIER DETECT (DCD) 307 IN
#=not connected at PM Observer.
!=always active.
Table 7-3 Layout for connecting MPC Cable
416
DTE/DCE CIRCUIT NAME CONNECTOR IN- OR
CIRCUIT OUTPUT
103 TRANSMITTER DATA (TXD) 103 OUT
104 RECEIVED DATA (RXD) 105 IN
105 REQUEST TO SEND (RTS) 107 ! OUT
106 READY FOR SENDING (CTS) 301 # IN
107 DATA SET READY (DSR) 303 IN
108 DATA TERMINAL READY (DTR) 305 OUT
109 DATA CARRIER DETECT (DCD) 307 IN
102 SIGNAL GROUND (SG) 102, 104, 106, -
108
302, 304, 306, -
308
#=not connected at PM Observer.
!=always active.
Table 7-4 Layout for connecting OM-VDU Cable
7.3. INSTALLATION
7.3.1. General
The PM Observer can be used in the following ways/positions:
In a free PCT Position (Independently)
In this case the PM Observer is used in a PCT position in a shelf.
•(R)PM1100 shelf: In position 16 (next to the PMC); data for all peripheral circuits in the
shelf, except those on the PMC board itself, can be traced.
•CSM shelf: In position 18.
•All systems: In a free PCT position in a unit group; only data with respect to this
unit group can be traced. The PM Observer must be placed at the right
hand side of the board which is to be observed.
As an Extender to the:
417
PMC: In SOPHO iS3010/3030/3050/3070 and SOPHO-S55/255. The following data can be
traced:
•CPU - PMC communication.
•Data for peripheral circuits. Note that the communication to circuits (e.g. DOC) on
the PMC cannot be traced! This restriction is not valid for hatches.
PSC: In SOPHO iS3070, SOPHO-S2500 and SOPHO-S250/1000. The following data can
be traced:
•All communication with peripheral circuits in the shelf.
•CPU-PPU communication can only be traced in the SOPHO-S1000 with software
Package 640. In the SOPHO-S2500 and the SOPHO iS3070 trace of CPU-PPU
communication is not possible in this configuration. Tracing the DTU-CC
communication is also not possible.
PCT: All communication data with respect to the Unit Group in which the PM Observer is
placed.
PI: Not used in SSW 8xx and Call@Net. In SOPHO-S50/100 with PR640, this
configuration can be used to trace CPU-PPU communication.
The PM Observer automatically detects the PCT, PMC or PSC position.
The cabinet can be closed while the PM Observer is installed. You have to remove the
extender rails on the PM Observer. Also the earth pin at the front side of the board must be
removed.
PROCEDURE: Hardware Installation Procedure
Before you start with the hardware installation procedure, it is adviced to consult the previous
sections in this chapter. Perform the following steps for the hardware installation.
Actions
1. Determine which communication you want to observe. Consult section 7.3.1. General
and determine how you want to apply this board and in which position.
2. If you want to use the PM Observer in a free PCT position as an independent board and
you want to have the cabinet closed, you must remove:
- the extender rails;
- the earth pin at the front side.
Keep these items, because you need them when you want to use the PM Observer in
applications where it is used as extender.
3. Check the strap setting on the board (see Figure 7-1 Location of DIL Switches and Jumper
Pads) and the DIP switch setting (see Table 7-2 DIP Switch Settings).
418
4. If the PM Observer is used as extender, do the following:
- Set the board in the position where the PM Observer must be placed in condition Out
Of Service.
- Take the board out of the position.
5. Place the PM Observer board and connect the PC to the MPC connector or OM - VDU
connector (depending on the used cable) on the PM Observer. For the pin numbering of
the connectors, see Table 7-3 Layout for connecting MPC Cableand see Table 7-4 Layout
for connecting OM-VDU Cable. Wait until the red and green LEDs are lit.
6. If the PM Observer is used as extender, the board which you have taken out of the shelf
must be placed onto the PM Observer. Set the board in service condition In Service.
7. Reset the PM Observer and wait until the red and the green LEDs are lit.
8. Switch on the PC.
9. Continue with the software installation procedure.
Software Installation and Startup
The software can be installed on a PC which is running Windows 95/98/NT.
Execute the file PMCSMEXE.EXE.
7.4. GETTING STARTED
7.4.1. General Information
When you have installed and started the program, as described in previous sections, you are
ready to use the program. There are a number of keys and key combinations which can be
very useful:
F1 = Help screen (a help screen is available for almost every option).

Alt+F4 = Quit the active procedure.
Alt+Spacebar = Gives additional menu with the following screen options:
•Restore.
•Move.
•Size.
•Minimize.
•Maximize.
•Close.
Tab = Change fields within the menus.
F10 (or Alt) = Go to menu bar.
419
PROCEDURE: Observer Settings
It is necessary to adjust the program to your system and to your requirements. The following
procedure gives the most important settings.
Actions
1. Select the 'Settings' menu in the PM Observer menu.

2. Select the 'Shelf . . .' menu and select the type of shelf that you have.
3. Select the 'Settings' menu and the 'Input . . .'. Now you must select:
4. Select 'Com Port'.
Now select 9600 Bd (if your system is a 486 or higher you can select 19200 Bd) and the
COM port that you want to use.
5. Select 'OK' to terminate this menu.
6. Select the 'Settings' menu and the 'Output . . .'. Now you must select:
- Dump file = File with only Hex notation of the fetched information.
Log file = File which contains the translated HEX information from a trace.
The input data is always displayed on the screen.
- Translation: as required (only for ISDN)
The translation parameter determines whether the input is stored as it was received,
or whether the input is stored after a translation. Translation means that the received
codes are translated into messages. Determine the translation level that you want to
have.
7. Select the 'Settings' menu and the 'Observe ...'. Now you can select:
- PCC messages.
You may specify three ranges to observe PCC messages.
Specify the shelf and board position and the timeslot for each range.
- IMP communication (USI/USO).
You may specify up to six IMP communication (USI/USO) channels (timeslots) which
are to be observed.
- CPU <-->PPU messages (200/205)
Note that you can observe CPU - PPU messages in al other System Software by
selecting the appropriate IMP channel. SSW 200 and SSW 205 are an exception to this.
Therefore a dedicated item is made in this menu.
420
Note: If there is no communication between the board and the PC, you are not able to select an
item and you will get the message:
WARNING: NOTHING SELECTED FOR OBSERVATION (CHECK SETTINGS/

OBSERVE)
8. Select the 'Settings menu and the 'Triggers...'.

You can define on which condition tracing must start and on which condition tracing must
stop. If you do not fill in the parameters, tracing starts immediately after selecting 'start' in
the start menu.
9. Select the 'Settings' menu and the 'Filters...'.
By means of the filters, you can specify which data must be discarded or which data must
be passed through. If you do not fill in these filter options all data is passed through to the
file.
Examples
Table 7-5 General Overview of Parameter Settings in Relation to various Configurations and
Table 7-7 Examples of Parameter Settings in Relation to various Configurations give a general
overview with examples showing how the PM Observer can be used. Note that in this
overview non-SSW 805 systems are also mentioned.
421
COMMUNICATION SYSTEM/ PM PARAMETER SETTINGS
SHELF TYPE OBSERVER IN
POSITION:
IMP messages for e.g. PM1100 Second position IMP messages -/--/00
DTX-I(15) in the first iS3030 in that Unit
position of a Unit iS3010 Group
Group
PCTs in positions 11 ... CSM-PM As extender for see Table 7-6 Relation board/
19 the PMC. trace position in CSM-PM
shelves
PCTs in positions 1 ... (R)PM255 As extender for IMP messages 0/<board
16, 18, 19 First post. in iS3030 the PMC. pos.>/00 e.g. 0/03/00 for pos.
UG SOPHO-S255 3 e.g. 0/04/00 for pos. 4
PCTs in positions 1 ... PM1100 PM Observer in IMP messages 0/<board
15 First pos. in UG position 16 or as pos.>/00 e.g. 0/03/00 for pos.
extender for the 3 e.g. 0/04/00 for pos. 4
PMC
DTU-PH timeslot 16 PM1100 PM Observer in IMP messages 0/<sec. board
messages position 16 or as pos.>/00 e.g. 0/04/00 for
extender for the board pos. 3; 0/18/16 for board
PMC pos. 18; 0/19/16 for board pos.
19
Table 7-5 General Overview of Parameter Settings in Relation to various Configurations
422
BOARD POSITION TRACE POSITION
11 01
12 03
13 05
14 07
15 09
16 11
17 13
18 15
19 17
Table 7-6 Relation board/trace position in CSM-PM shelves
423
COMMUNICATIO SYSTEM/ PM OBSERVER IN PARAMETER SETTINGS
N SHELF POSITION:
TYPE
CPU-PPU SOPHO Observer as extender IMP select 00/09/00 or via
S1000 for the PMC (position 9) backpanel: 00/0x/xx. See
(PMC-LU) Table 7-8 PM Observer
settings CPU-PPU (CPU-
ME/MT) communication in
SOPHO S1000 (PMC-LU)
CPU-PPU iS3070 / Position 16 or use the IMP select x 0/17/00 (for
3090 PM Observer as link sequence 0) AND IMP
PM1100 extender for the PMC select x+1 0/17/02 (for link
sequence 1)
CPU-ME/MT-PMC iS3010 As extender for the IMP messages 1/03/00
CPU3000 PMC-MC.
CPU-ME/MT-PMC iS3030 As extender for the IMP messages 1/08/00 and
(Master/ PMC-MC. IMP messages 1/08/02
first shelf)
CPU-ME/MT-PMC iS3030 As extender for the IMP messages 1/07/00
(slave/ PMC-MC.
second
shelf)
CPU-PMC RPM255 As extender for the IMP messages 1/07/00 and
PMC-MC. IMP messages 1/07/02
CPU-PMC RPM1100 As extender for the IMP messages 0/17/00 and
PMC-MC. IMP messages 0/17/02
CPU-PMC PM-CSM Pos. 18 or use the IMP messages 0/17/00 and
shelf observer as extender IMP messages 0/17/02
for the PMC (pos. 19)
(select PM1100 shelf)
424
N SHELF POSITION:
TYPE
CPU-ME/MT-PMC iS3050 PM Observer in - IMP messages 0/18/02 (for
position 16 of the CPU - PMC comm. shelf 1),
controlling shelf (with 0/18/04 (for CPU - PMC
CPU-ME/MT) (Also comm. shelf 2) and 0/18/08
possible as extender for (for CPU
the PMC) - PMC comm. shelf 3) IMP
messages 0/18/00 can be
used for PMC but also for
CSN-BC. This depends on
system configuration.
PCC communication PM1100 PM Observer in PCC range x from 0/07/00
Board position 7 position 16 or in the UG to 0/07/15
Circuits 0 ... 15 or as extender for the
PMC.
PCC communication PM2500 PM Observer in a PCC range x from 0/08/00
Board position 8 position in the UG or as to 0/08/07
Circuits 0 ... 7 extender for the PCT
board.
IMP mess. in timeslot PM1100 Position 16 or use the IMP messages 0/18/16 and
16 for a board in PM Observer as IMP messages 0/19/16
position 18 or 19 extender for the PMC
CPU3000 iS3050 PM Observer in via backpanel 00/18/xx
position 16 of the where xx = 00:
controlling shelf (with communication between
CPU3000) (Also CPU and CSN. xx = 01 up
possible as extender for to (incl) 08: CPU/PMC to
the PMC) other shelves (01 = master
PMC)
CPU3000 iS3030 As extender for the IMP messages 1/08/01 and
(Master/ PMC-MC. IMP messages 1/08/02
first shelf)
425
N SHELF POSITION:
TYPE
CPU3000 iS3030 As extender for the IMP messages 1/07
(Slave/ PMC-MC.
second
shelf)
CPU3000 SOPHO Observer as extender via backpanel 00/1x/xx : see
S1000 for the PMC (position 9) Table 7-9 PM Observer
settings CPU-PPU
(CPU3000) communication
in SOPHO S1000 (PMC-
LU)
Table 7-7 Examples of Parameter Settings in Relation to various Configurations
Parameter settings for the SOPHO S1000 (CPU-ME/MT or CPU3000) are given in Table 7-8
PM Observer settings CPU-PPU (CPU-ME/MT) communication in SOPHO S1000 (PMC-
LU)and Table 7-9 PM Observer settings CPU-PPU (CPU3000) communication in SOPHO
S1000 (PMC-LU).
The relation between the physical channel number (PCH) and the EHWA PM Observer is a
fixed one. The relation between the PCH and the EHWA destination depends on the
projecting order.
The PCH/EHWA destination relation can be displayed with second line OM command
DIPCHD.
426
EHWA PCH PCH EHWA PARAMETER
DESTINATION SETTING
12,11,1 0 12,13 CSN-BC 0/11/00
12,11,3 2 12,9 shelf 2 Primary PM 0/11/04
12,11,4 3 11,9 shelf 1 0/11/06
12,11,5 4 13,9 shelf 3 0/12/00
12,11,6 5 14,9 shelf 4 0/12/02
12,11,7 6 13,14 IAS 0/12/04
12,11,8 7 21,9 shelf 5 0/12/06
12,11,9 8 22,9 shelf 6 0/11/01
12,11,10 9 23,9 shelf 7 0/11/03
12,11,11 10 24,9 shelf 8 0/11/05
Table 7-8 PM Observer settings CPU-PPU (CPU-ME/MT) communication in SOPHO S1000

(PMC-LU)
EHWA PCH PCH EHWA PARAMETER

DESTINATION SETTING
12,11,1 0 12,13 CSN-BC 0/10/00
12,11,3 2 12,9 shelf 2 Primary PM 0/10/01
12,11,4 3 11,9 shelf 1 0/10/02
12,11,5 4 13,9 shelf 3 0/10/03
12,11,6 5 14,9 shelf 4 0/10/04
12,11,7 6 21,9 shelf 5 0/10/05
12,11,8 7 22,9 shelf 6 0/10/06
12,11,9 8 23,9 shelf 7 0/10/07
12,11,10 9 24,9 shelf 8 0/11/00
Table 7-9 PM Observer settings CPU-PPU (CPU3000) communication in SOPHO S1000

(PMC-LU)
427
7.5. MENU AND FILE STRUCTURE
7.5.1. Menu
The main purpose of the software is to expand the received trace data with meaningful
comments. It also allows and helps the user to enter commands which can be selected from a
menu.
The file(InitFile) sub-menu offers the following choices:
- New Reset all init settings to default;

- Open... Specify file name as init file;
- Save Save settings to current init file;
- Save as... Specify new file name as init file and write;
- Exit Close the application.
The input sub-menu offers the following choices:
- Dump File Specify file name as input dump file;

- Log File Specify input log file;
- Com port Specify COM port with settings.
The output sub-menu offers the following choices:
- Dump File Specify file name as output dump file;

(dump file=file which contains unchanged PMO data).
- Log File Specify output log file.
(log file=file which contains changed (translated) PMO data).
The settings sub-menu offers the following choices:
- Input
- Select input from com port/dump file/log file;
- Output
Output
- Select output to dump file/log file (screen is always on);
- Select level of translating input data (limited support).
- Shelf
- Specify the system in which the board is placed.
- Observe (can be modified during operation)
428
- Specify up to three PCC (CODI/CODO) ranges to observe (EHWA oriented), full
data specification;
- Specify IMP channels (0...15 or 0...31) (USI/USO) to observe (EHWA oriented); It is
also possible to observe the CPU - PPU communication by selecting the PMC EHWA;
- Enable/disable PPU-CPU messages for SSW 200/205. (SOPHO-S55 and S255 only.)
In all other System Software, CPU-PPU communication is observed by specifying the
correct IMP channel(s).
- Triggers (can be modified during operation)
- Set one start and one stop trigger;
Set start trigger on specified channel and/or data to start tracing. After triggering filters
are active (if enabled).
set stop trigger on specified channel and/or data to stop tracing. If single triggering is
active then tracing is stopped permanently else the start trigger condition is active
again.
- Set start/stop trigger to date and time or to a data pattern;
- Trigger once or repeat trigger conditions.
- Filters (can be modified during operation)
- Specify up to ten filters on EHWA oriented board locations with full data specification
(hexadecimal);
- Set filtering mechanism by pass or don't pass data switch.
The control sub-menu offers the following choices:
- Start Enables input from selected input device or file;

- Pause Hold/resumes input from selected input device or file;
- Stop Causes input file to be closed or a stop command is transmitted to the
PMO;
- Off Line Sets PM Observer in local storage mode. Afterwards the PC can be
disconnected and then switched off. The green LED will start blinking. The
stored trace data can be retrieved by reconnecting the PC and using the
Start command in the control sub-menu.
Note that the internal buffer is limited (appr. 2500 blocks of 160 kbytes). If
the buffer is full previous data will be overwritten.
The help sub-menu offers windowed general help information, keyboard help and product
information.
7.5.2. File Structure
The software of the PM Observer comprises program and data files. The following files are
distinguished:
429
- PMCSMEXE.EXE Program files.
- PMCSM40.ICO Icon file.
- PMO.INI Init file containing software setup, file names, filter and
trigger settings. The file type is ASCII, generated by
software (user can also modify the file by means of an
editor).
- MPMO.DAT Library file containing user interface menus and the help
information.
- PMO.ICO Icon file for PMO Icon in windows.
- PMCSMDLL.DLL Dynamic Link Library.
- WINSOCK.DLL Dynamic Link Library for the Windows Sockets.
7.5.3. Messages in the Header
During executing a procedure, the PM Observer program displays coded messages in the top
line of the PM Observer screen e.g. D.L3 .... The meaning of the messages is given in the table
below.
430
STATUS FIELD MEANING
NUMBER INDICATOR
1 C COM port used as input
T TCP/IP (socket) used as input
D Dump file used as input
L Log file used as input
. No input source selected yet
2 D Dump file selected as output
. No dump file selected as output
3 L Log file selected as output
. No log file selected as output
4 N Translation level set to not required
1 Translation level set to 1
. No translation level set yet
5 S Board synchronized with PC application
. Board not yet synchronized with PC application
6 O Observing in progress
A Observing active
P Observing paused
. Currently not observing
Table 7-10 Meaning of the coded messages
7.6. DOWNLOADING THE FIRMWARE
The firmware in the PM Observer is generally not downloaded in the factory. To download
the firmware, follow the procedure below:
PROCEDURE: Downloading the Firmware
Preconditions
431
Before starting the download procedure make sure that the following requirements are met:
- PM Observer board must be equipped with a boot PROM with 12 NC: 3522 254 18732,
or with a 12th digit higher than 2.
- System with at least one PCT position projected with a special board type.
- Maintenance PC connected to the CIS(-RM) in the iS3070 or
SMPC with OM link to the iS3010, iS3030 and iS3050.
- PM Observer firmware distribution floppy disk.
Actions
To download the firmware execute the following steps:
1. Install the firmware package in the LBU.

In the case of an iS3070 with a CPS, the file must be copied from the MPC to the LBU.
For CPU-ME/MT systems, the firmware file must be installed on the hard disk of the SSM-
MPC in the directory which is assigned to the ISPBX as LBU. The firmware file has file
name: F8xxxx.xxx.
2. Project a PCT board position for the PM Observer by ASBRDS:
<ASBRDS:<SHELF>,<BOARD>,36, 090A;
3. Execute OM command INSTPK.
This command reports to the system that a 'new package' is available for a particular type
of board. The actual downloading takes place at a later stage (step 8).
4. Set the PM Observer board into download mode (see Table 7-2 DIP Switch Settings:
switch 6 is 'on' and the other switches are 'off').
Note that, if there is no valid firmware package installed in the FEPROMs, the DIL switches
can all be set in the 'off' position. The board detects that there is no firmware installed and
goes automatically in the download mode.
5. Place the PM Observer board in the selected board position.
The red LED will be lit. Wait until both, the red and the green LEDs are lit (this takes about
12 seconds).
6. Set the PM Observer board out of service by SETOUT.
7. Delete the old firmware package by DEPACK. The red LED starts flashing (the green LED
remains on).
8. Set the PM Observer board into service by SETINS. The system will now download the
firmware package (which is assigned by INSTPK in step 3) to the PM Observer board.
During the download process, the board is in the ABL-er (or -te) status; this is normal.
9. When downloading is completed (the board is in ABL-er), set the board to "NIN", pull it
out of the shelf and set the switches to the correct mode of operation (see Table 7-2 DIP
Switch Settings).
10. Delete the board with the command:
432
<DEBRDS:<SHELF>,<BOARD>;
Now the PM Observer is ready for use.
433
8. PM/CSM OBSERVER
8.1. INTRODUCTION
The PM/CSM Observer module is used to monitor the PM- and CSM- communications bus
located on the backpanels of the PM and CSM shelves. It is available for Windows only. The
complete PM/CSM Observer package is made up of the following components:
• The Observer PC application (or host).

• The Observer board (PM); this is a dedicated board to observe the PM bus
• A PROM package for the installed CIE (CSM), allowing it to act as an observer.
The observer board/PROM package contain firmware that enables the host to receive data
from the bus and allows the host to filter the observed bus data. With the board for the PM
bus also triggers may be set. The host offers the user an interface to control observer boards
and also contains some functionality for the translation of data received from the board.
When observing a PM bus the host interfaces with the PM board and communicates via a serial
link.
When observing the CSM bus the host interfaces with a CSM board and communicates via an
ethernet connection.
8.2. INTERFACES AND CABLING
The PM/CSM Observer application interfacing setup varies depending on whether the
application is being used for PM or CSM.
8.2.1. PM Observer interfacing
The PM/CSM Observer application interfaces with a PM Observer board via a cable
connection to one of the COM ports on the host PC. Use one of the following cable types:
• OM-VDU HR (Cl-x - VDU)

• MPC
8.2.2. CSM Observer interfacing
The PM/CSM Observer application interfaces with a CSM board via a TCP/IP connection. For
this reason the host PC requires a network card. In addition, a TCP/IP protocol stack must be
434
available on the host PC. The CSM Observer board can be connected to the PC via the
network using one of the following methods depending on your version of windows.
Point-to-point connection
This is the preferred connection. To connect to the CSM-observer with a point-to-point

connection, a one-to-one (direct) cable has to be used.
CSM Point-to-point connection

Observer One-to-one UTP
PC with Windows 95
Figure 8-1 CSM Observer Connection - Point-to-point
Network connection
A cross-UTP cable with a cable layout as shown in Figure One is required to connect the CSM
Observer board to the application PC, provided that PC is running Windows 3.xx and is
already connected to an existing network infrastructure. The cable layout must be as shown
in figure 8.2.
CSM Observer Board Network Connection

TX+(1) (1)TX+
TX - (2) (2)TX -
RX+(3) (3) RX+
RX- (6) (6) RX-
NA (4) (4) NA
NA (5) (5) NA
NA (7) (7) NA
NA (8) (8) NA
Figure 8-2 Cross UTP Cable Layout
The PC must have a second IP address in order to communicate. When using Windows 3.11
with Microsoft TCP/IP-32 installed it is possible to add a second IP address. If you are using
another TCP/IP stack implementation that does not offer this functionality the point-to-point
connection can be used.
435
Company infrastucture - Ethernet
CSM Cross UTP

Observer
PC with Windows 3.11
Figure 8-3 CSM Observer Connection - Network connection
8.3. INSTALLATION
1. Create a directory to hold the PM/CSM Observer-related files.

2. Copy the following files from the installation floppy into this directory:
PMCSMEXE.EXE
PMCSMDLL.DLL
PMCSM40.ICO
MPMO.DAT
WINSOCK.DLL (Dummy version)
3. Create a new program group and/or program item, then choose an appropriate icon so
that PMCSM40.ICO is associated with the executable.
Note that running the PM/CSM Observer requires the winsock.dll file. To use the PM
Observer it is only necessary to have the dummy winsock.dll file which must be copied to the
windows directory. To use the CSM Observer is necessary to have a TCP/IP stack and a real
winsock.dll file. If the target PC is equipped with a TCP/IP stack and a real winsock.dll file then
make sure the dummy version is either removed or not installed.
8.3.1. Communication guidelines
For the CSM Observer to function correctly it is necessary for the target PC to be configured
for network operations. The following guidelines describe this process:
- When the target PC does not have an IP address use the following configurations:
- configure the CSM board observer with the IP address 192.168.1.239 and netmask
255.255.255.0 (this must be done by the bootp server).
- configure the target PC with the IP address 192.168.1.250 and netmask
255.255.255.0.
- When the target PC is already configured with an IP address:
- ask the network manager of the site what netmask is used.
436
- ask the network manager for a spare IP address for the CSM board observer
- configure the CSM board observer with that IP address (this must be done by the
bootp server).
Providing the PC with an IP address is done as follows in Windows 3.11:
1. Choose the Windows Setup icon in the Main group.

2. Choose Change Network Setting from the Options menu. The Network Setup dialog
appears.
3. Double click the name of your network adaptor card in the Network Drivers list.
4. Choose the Advanced button in the Settings dialog box.
5. Add the IP address and click on OK.
6. Click on OK in the Network Setup dialog box.
7. Restart your computer for the changes to take effect.
8.4. GETTING STARTED
PROCEDURE: Starting the PM/CSM Observer
Actions
• Double click on the PM/CSM Observer icon. The main screen is displayed.
Note the toolbar buttons; use these to perform a variety of actions as an alternative to the
equivalent menu option. Where appropriate they are mentioned in this chapter in italic text.
PROCEDURE: Selecting a Shelf
Actions
1. Select Shelf... from the Settings menu. The Shelf Select dialog is displayed.
Note: The PM (red) and CSM (green) Observer icons allow you to distinguish which screen relates
to which area of functionality. All settings-related screens display one or both of these
icons. If a screen relates to both the PM and CSM Observers then both icons are shown. If
a screen relates to only one of these then the appropriate icon is displayed.
2. Click on a radio button to select either a PM Observer shelf or the CSM Observer.
3. Click on OK.
437
PROCEDURE: Defining the input source
Actions
1. Select Input... from the Settings menu. The Input Selection screen is displayed.
2. Click on a radio button to select an input source for an observer session. Four options are
available:
TCP/IP
Select this option to observe the CSM bus. The TCP/IP Setup screen is displayed. This
option is only available if the CSM-Shelf option is selected in the Shelf Selection screen.
Enter the IP address of the CSM Observer board (currently set at 192.168.1.239, but not
always the case; see 8.3.1. Communication guidelines).
COM Port
Select this option to observe the PM bus. The COM Port Setup screen is displayed. This
option is only available if one of the PM Shelf options is selected in the Shelf Selection
screen. Click on the required port and baud rate radio buttons, then click on OK.
Note: The number of stop bits is set to one, the number of data bits is set to eight, no parity is
selected and the data flow is set to Xon/Xoff.
Dump File
Select this option to use the dump file of a previous session as input. Click on the Browse...
button. The Open Dump File dialog is displayed. Use this dialog to navigate to the required
location, select a dump file and click on OK.
Log File
Select this option to use a log file from a previous PM/CSM Observer session as input. Click
on the Browse... button. The Open Log File dialog is displayed. Use this dialog to navigate
to the required location, select a log file and click on OK.
3. Click on OK.
PROCEDURE: Defining the output format
Actions
1. Select Output... from the Settings menu. The Output Selection screen is displayed.
2. Click on the required Output to: radio button. You can choose to save data as a dump file
(as raw, untranslated data), as a log file (as processed data) or not to save at all. Use the
Browse... buttons to display a selection screen allowing you to select output dump or log
files from previous session.
438
Note: The PM/CSM Observer automatically rename files to include a version number if a file name
is used that already exists. Up to 99 versions are supported.
3. Click on a Translation radio button to specify how the output data will be represented.
Three levels of translation are supported. The translated data is shown on screen and, if
specified, saved in the log file. When a dump file is selected as the output location the
selected translation level only applies to the data displayed on screen.
4. Define the Log/Dump Cycle. Activate the Cyclic Log/dump checkbox and set an upper
limit on the dump or log file in the File size field. When the specified size is reached a
second file is opened and used as the output file. When the second file is full the first one
is re-used. Note that the name of the second file is identical to the first one except that
the final character is changed to a 'b'.
Note: You can activate the Disable Screen Output option to increase system performance.
5. Click on OK.
PROCEDURE: Defining triggers
Shortcut available - click on Hand button.
Actions
1. Select Triggers... from the Settings menu. The On Board Trigger Selection dialog is
displayed. Use this dialog to define the start and stop conditions for observing sessions
using the PM Observer board. Note that this option is only available if a PM shelf is
selected in the Select Shelf dialog. Trigger settings are not used while the input source is
either a dump or a log file.
2. Click on the required Trigger Type radio button.
3. Enter the required Message Start Trigger details. These are the start conditions when
selecting message-based triggering.
4. Enter the required Message Stop Trigger details. These are the stop conditions when
selecting message-based triggering.
5. Enter the Time Trigger start and stop details. This information is used for time-based
triggering.
6. Activate the Trigger Mode check box if required. This specifies that the start and stop
conditions are used only once.
7. Click on OK.
439
Note: If both the start and stop condition are omitted then tracing starts immediately and
continues until a user intervenes.
PROCEDURE: Defining observation criteria
Shortcut available - click Glasses button.
Actions
1. Select Observe... from the Settings menu. The On Board Message Selection dialog is
displayed. Use this dialog to define which board positions and/or timeslots to be observed.
Note that this option is only available if a PM shelf is selected in the Select Shelf dialog.
Three types of communication can be observed:
PCC communication (CODI/CODO)
To observe this type of communication:
- Activate one or more of the PCC range check boxes.
- Enter the required range details in the form shelf/board position/timeslot. Note that
the start condition specification must always have a value less than or equal to the stop
condition, and that for systems such as the S55 or S255 the peripheral module is split
into an upper and lower part; the upper part is called shelfnumber 0 and the lower part
is called shelfnumber 1.
IMP/HDLC communication (USI/USO)
Activate one or more of the 'Active' check boxes. You can select up to six timeslots or
boards for observation. Each selector consists of a check box and a link specification
similar to the PCC specification. Activate the HDLC check box to observe HDLC data in
the IMP channel.
Note: Digital board normally use one timeslot for communication and all other slots for data
transfer. Note that data transfer slots are protected and cannot be observed.
CPU-PPU serial communication (S55/S255)

Activate the CPU-PPU check box. This type of communication can be observed for S55
and S255 systems using SSW 200/205. Note that the PM Observer board must be placed
in the PMC position (as extender).
2. Click on OK.
8.4.1. Defining filters
Shortcut available - click on the Funnel button.
440
Select Filters... from the Settings menu. The On Board Filter Selection dialog is displayed. Use
these 'pass' filters to define the data you want to collect. The exact content of the On Board
Filter Selection dialog depends on whether you selected a PM or CSM board in the Shelf Select
dialog. The steps required to complete both variations of the On Board Filter Selection dialog
are described below.
PROCEDURE: PM Observer Board Filters
Actions
1. Click on a Filter Method radio button. Select 'Pass data' to filter out data you want to be
displayed or 'Don't pass data' to filter out data you do not want to be displayed.
2. Activate a filter by clicking in the appropriate check box. A filter is activated when the
check box is marked with an X.
3. Enter the required range details in the Sh/Brd/Ts field. Range details are entered in the
form shelf/board position/timeslot. You can set the timeslot parameter to 'don't care'
(represented by XX) if required.
4. Set the Type specification. Click on the drop-down list arrow to display a pick list of
options.
5. Enter any additional specifications in the Data field. You can enter additional data to look
for 'special' messages. This data can be specified as either hexadecimal or binary. Data
bytes must be separated by spaces. The HEX component is always three characters long,
starting with an H, followed by two characters in the range 0 to F, or X for 'don't care'.
The binary component must start with a B, followed by one to eight 0 or 1's, or X. If less
then 8 characters are specified then additional X's are used as padding.
6. Click on OK.
Note: Filters have no effect when the selected input source is a dump file or a log file.
PROCEDURE: CSM Observer Board Filters
Actions
Note: All data from the CSM-bus is passed to the PC application if no filters are selected.
1. Activate the required Board A checkbox(es). These allow you to observe all messages
having either CPU cluster 0 or 1 as source (represented as CC0 or CC1). CPU cluster 0
is the operational CPU in both 4/2 mode as well as dual mode. CPU cluster 1 is the standby
CPU during dual mode.
2. Activate the required Board B checkbox(es). Activate the checkbox for a specific
destination mark to observe all related messages. Note that odd board numbers can only
be observed using the CSM Observer while connected to bus 0, while even board
441
numbers can only be observed while connected to Bus 1.
3. Select the required CAP Channel radio button to observe a specific (logical) channel. Note
that you can select ALL (default).
4. Activate the required Filters checkbox(es). Use the 'Messages Only' checkbox to force
filtering on IMP messages only. Note that each of the four filter definitions can filter on IMP
messages and s_addresses.
5. Click on OK when your selection is complete.
8.4.2. Handling configuration settings
Once you have set up a configuration of settings for a PM/CSM session you can save these
settings in an .ini file (default name pmo.ini). This facility allows settings to be reused.
- Select Reset Settings from the File menu to reset all user settings to the default.
- Select Open Settings from the File menu to restore saved settings. A standard Windows
file navigation dialog is displayed. Navigate to the required file and click on OK.Shortcut
available - click on the Folder button.
- Select Save from the File menu to save the current settings to the default .ini file.Shortcuts
available - click on the Disk button.
- Select Save Settings As from the File menu to save the settings in a user defined file. A
standard Windows file navigation dialog is displayed. Navigate to the required file and click
on OK.
8.4.3. Starting and stopping the observation session
Shortcuts available - click on the appropriate button.
Start
Select Start from the Control menu to begin the observation session.
Stop
Select Stop from the Control menu to end the observation session.
Pause
Select Pause from the Control menu to temporarily suspend the observation session.
Select Pause a second time to resume the observation.
Off Line
442
Select Off Line from the Control menu to put the PM Observer into local storage mode. This
command is only applicable to the PM component (e.g. not the CSM component). The
application PC can now be disconnected and/or switched off. A green LED on the PM
Observer board starts blinking. The stored observation data can be retrieved by reconnecting
the PC and selecting twice 'Start' from the Control menu.
Note: The internal buffer is limited in size to approximately 2500 blocks of 160 Kbytes each.
Previous data is overwritten if the buffer if full.
8.4.4. Quitting the PM/CSM observer
Select Exit from the File menu to quit the PM/CSM Observer. You are notified if the current
settings have not been saved.
8.4.5. Copying settings to other applications
Use the Copy to Clipboard to copy all data in the current screen to the clipboard. You can
paste this information into another application as required.
Note: It is not possible to select an area of data and copy it to the clipboard using the standard
Windows copy command.
8.4.6. Getting help
Select an option from the Help menu. A window containing the relevant help text is displayed.
443
9. PPH PROTOCOL TRACER
9.1. Introduction
The PPH Protocol Tracer observes and records the external communication of the following
PPH boards.
- DTX-I
- DLX-U
- DLX-L
- DLC-U
- DTU-PH
Information extracted using the PPH Protocol Tracer is used for fault tracing. The PPH
Protocol Tracer is used in conjunction with the Peripheral File Storage Mechanism.
The following OM commands are related to the PPH Protocol Tracer :
- STRTPT : Start Peripheral Circuit Trace

- STOPPT : Stop Peripheral Circuit Trace
- DIPCRT : Display Peripheral Circuit Trace Information
The following OM commands are related to the Peripheral File Storage Mechanism :
- CHPDOD : Change Peripheral Data Output Device

- DIPDOD : Display Peripheral Data Output Device
- CHPDFS : Change Peripheral Data File Status
- DIPDFS : Display Peripheral Data File Status
9.2. Peripheral File Storage Mechanism (PFSM)
The Peripheral File Storage Mechanism (PFSM) is an interface between peripheral boards,
terminals and the CPU, it enables various applications on the peripheral boards and terminals
to create and manipulate files in the CPU. These files can be accessed from a remote site,
giving its stored data easier accessibility.
The PPH Protocol Tracer is the only application able to use the PFSM at the moment.
9.2.1. Files
Each file contains data produced by an application from within the same unit. So when OM
444
command DIPFSM is executed for unit X, it will show the files that are used by the application
running in unit X. A file name in a unit is unique e.g. if in command STRTPT for "file -name" an
existing file is entered, error 111 (file name exists) occurs. A maximum of sixteen files can exist
in a unit, depending on boundary 310 (max number of peripheral file users per unit) and
boundary 322 (max number of status observer entries). When an application creates a file, it
determines the file's properties.
The PFSM File Properties are:
- File name
- File Type
- Protection level (default NARD is 3333)
- Maximum file size
The process of writing data to a file is identified as a task. A task is a collection of specific
repetitive actions within an application. Every task has its own unique number. All task
numbers consist of a unit number followed by a three digit number (running consecutively
from 000 to 254). If a new task number is needed, the next consecutive number is
automatically taken, when 254 is reached, 000 is re-used. A file is automatically closed on
completion of an application task. If the file closure fails, the service engineer is able to close
the file at any time using OM commands. When a file is opened the application determines
whether it has read, stop or do not stop (when maximum file size is reached) capabilities.
- Stop when maximum file size is reached.

When the maximum file size is reached, the file is closed and the writing process is over.
- Do not stop when maximum file size is reached.
When the maximum file size is reached, the file is closed and its extension is changed to
.BAK and a new file is opened using the original file name and extension. This process then
continues in a loop, constantly re-using the .BAK file to replace the active file.
9.2.2. Log Files
Log files can be read (using OM command TYPFIL) and can be deleted (using OM command
DELFIL). A separate and single log file (PDFSuu.LOG) exists in every unit on the LBU,
recording the initiation, execution and release details of PFSM tasks. Task details can be
viewed on the log file when the task is complete.
The data consists of:
- File identification
- Task number
- EHWA of the board/terminal that was related to the task
445
- Identification of type of user e.g. PPH Protocol Tracer
- Maximum size of file
- Stop at maximum file size
- Time task started
- Time task finished
- Number of files overwritten (if do not stop when maximum file size is reached)
- Indication if a read or write error has occurred
- Indication why task was finished (reason for stopping)
- Indication whether or not errors had occurred
9.3. EXAMPLE
Let's assume one wants to make a protocol trace of a number of circuits on an DTX-I board
e.g. 1012,5 and the circuits 2&3 (because of performance reasons, it is advised to do the
protocol trace for a few circuits only). The following layout is assumed:
DTX-I PMC CPU LBU
Trace
Application
OM terminal
Figure 9-1 Configuration
The output device should be assigned with OM Command CHPDOD. The default output
device is LBU.
The control of the flow of information from the Peripheral Board to the specified file on the
Logical Device can be done with OM Commands CHPFSM, DIPFSM, CHPDOD and
DIPDOD. On the LBUxx a LOG file with file name PDFSxx.LOG is created by the system
autonomously. This file shows apart from stopping the trace application via an OM command
the reason of interruption of the process. The possible situations are mentioned under the
STOPPT command.
Boundary 210 (disk space alarm upper level) controls when reaching the maximum threshold
of the LBU and generates a alarm. The CPU will now stop the process. In this case stop action
3 (disk space exceeded) is mentioned in the log file.
446
The following alarm codes are related to PFSM:
- code 61 : QLF 55 : Access to peripheral data file failed;

- code 61 : QLF 56 : Access to PDFS log file failed;
- code 81 : QLF 20 : Peripheral data file close due to maximum size.
An example of a log file is given below.
TASK FILE-ID EHWA BSP-ID APPL MAX-F-S R/W STOP-AT-M-F-S

2000 LBU02:T886.01 2011 7 - - 0 3 W No
STARTED STOPPED LOST-FILES ERRORS REASON-FOR-STOPPING
1999-04-10 +11:49 1999-04-10 +11:50 0 No 0
TASK FILE-ID EHWA BSP-ID APPL MAX-F-S R/W STOP-AT-M-F-S

2001 LBU02:T886.00 2011 7 - - 0 3 W No
STARTED STOPPED LOST-FILES ERRORS REASON-FOR-STOPPING
1999-04-10 +11:51 1999-04-10 +11:52 0 No 2
Figure 9-2 Example of log file
When all information of the trace has been collected and the process has been stopped the
trace file has to be prepared for the Trend Aurora Expert. This software program runs under
Windows. It should be installed on a PC, SMPC or BIM version 2. The file created by the
protocol tracer should be converted from the iS3000 format into a binary file, file name
XXXXXX.EXP, with the help of the iS3000 Convert with the option "Binary" set to ON.
Note: The Trend Aurora Expert software is not supplied by Philips.
WARNING: DO NOT USE AN OLD VERSION OF S2500 CONVERT.

USE THE CALL@NET VERSION OF IS3000 CONVERT.
The diagram below gives the required steps between the file created by the iS3000 on the
LBU and the Trend Aurora Expert.
File on iS3000 xxxxxx.EXP Trend

LBU Convert binary Aurora
Tool file Expert
Figure 9-3 Prepare Trace File for the Trend Aurora Expert
For detailed information consult the Trend Aurora Expert User Manual.
447
10. TCP MONITOR TOOL
The TCP monitor tool retrieves information requested by a user. Different functions are
available, depending on the source of information, PABX or disk.
The TCP monitor tool allows you to:
• Get statistical information about the TCP relay process on CIE (CCS system) or CPU3000
board.
Be aware that the CPU3000 is not used in SSW 805.
• Look at data transferred via the TCP relay process.
The TCP relay process can be seen as the access point in the PABX where TCP/IP messages
over Ethernet enter and leave the PABX, from or to an external application. At the moment
CSTA applications and iPVN can be connected to the PABX via the TCP relay process.
10.1. INSTALLATION
The TCP monitor is a program written for Windows 95/NT platform. The computer on which
runs the application must have a valid IP address.
The physical configurations possible are shown in the following figure:
Client Network
TCP Monitor
BIM
ISPBX Network
Figure 10-1 Physical configurations
448
In the above figure, the BIM acts as a gateway for the PABX traffic to the clients network and
vice versa. In this situation the PABX-BIM connection (via the CIE board) is a point to point
connection.
10.2. FUNCTION DEFINITION
The TCP Monitor retrieves the information a user requests from the PABX or from Disk.
Depending on the source, PABX or Disk, different functions are available. Table below shows
the tools in relation to the function.
PABX (USING NETWORK) DISK (USING DATA FILE)

Sockets ->Overview Translation ->TCP Monitor
Sockets ->Information
Sockets ->Clear
System ->Information
System ->Performance
Table 10-1 Tool-Function Relation
A source must be selected and opened for any function to be available. A source is selected by
choosing Source ->Open.
10.3. NETWORK SOURCE
Figure 10-2 "Data source" (Network) window
CCS systems use the CIE address.
Fill in the "CIE/CPU3000 name" or the "CIE/CPU3000 IP address".
449
The "CIE IP address" is the IP address of the CIE. This address is found on:
- the BIM 1.4/1.6 : in the /usr2/bim/run/cie/bootptab.cur file.

- the BIM 2.0 : in the /usr2/bim/run/cie/bootptab file.
The shelf position of the CIE determines the line in the bootptab file that holds the IP address.
CIE-1 indicates that this line is for the CIE in shelf position 7, CIE-2 indicates shelf position 8,
etc.
Establishing the connection is reported in the main dialog window. If the link is established, the
functions underneath Socket and System are available.
10.4. DATA FILE (DISK)
Figure 10-3 "Data source" (Data file) window
The file name of the data file is filled in or can be browsed.
The data file must be a log file of type "RAW", made by the TCP Monitor tool.
The status of the file opening is reported in the main dialog window. If the opening succeeds,
the functions underneath translation are available.
10.5. FUNCTIONS
Once the source is open, functions are available. This section gives a detailed description of
the functions.
450
10.5.1. Function "Socket Overview..."
Figure 10-4 "Socket Overview..." window
This function gives a short overview of all the sockets available to the system. It consists of a
table with six columns providing the following information:
• The first column represents the socket number used by PNA (and which is used to identify
a socket in the TCP Monitor program),
• The second column shows the socket state (Client/Server/Unused),
• The third column shows the IP address of the remote host computer linked to the PABX,
• The fourth column shows the TCP port number used by PNA to uniquely identify this TCP
session,
• The fifth column shows the S-address of the peer process in the PABX,
• The sixth column shows the port number used to initially set-up the connection to the
PABX by the host computer. It shows which service is offered.
10.5.2. Function "Socket Information..."
This function retrieves information related to a socket.
451
Figure 10-5 "Socket Information" window
• Flushed bytes
Bytes that are not processed because the header information of the message was not
correct. Length header greater than 256.
• Discarded
Count of the messages not received in time by the EDP and thus discarded.
• Bytes in/out
Number of bytes sent out and received on this socket.
• Message in/out
Number of messages sent out and received on this socket.
• Open/Close
Number of times this connection has been open.
• TimeStamp
A long field that can hold a value sent with the clear command.
452
• Socket Status
This field can hold the following status
- UNUSED: Not in use.
- SERVER: The socket is used to listen for connections.
- CLIENT (EMPTY): The socket is used to transfer data between and EDP and the
PABX. There is no risk of overflow of the buffers.
- CLIENT (THRESHOLD): The socket is used to transfer data between and EDP and
the PABX. It has lost a message during the last 30 seconds.
- CLIENT (OVERFLOW): The socket is used to transfer data between and EDP and the
PABX. At this moment, the socket has lost several messages. If this status remains for
30 seconds, the socket will be closed.
- BROKEN: The socket is about to be closed. The relay process is waiting for an
acknowledgment from the CCS to actually close the socket.
• Remote IP address
This is the IP address of the EDP to which the socket is connected.
• Remote Port
The port number used for this connection by the EDP.
• S-Address
The S-Address of the service process in the PABX that receives and sends data over this
socket.
• Connect port
The port number the connection was originally set-up over. This determines the action
taken upon the data coming in over this socket.
• Socket ID
Identification number used internally to identify the connection/socket.
10.5.3. Function: "Socket clear"
This function clears all statistical information of a socket.
453
Figure 10-6 "Socket clear" window
If the check box "Current time" is unchecked, the user can enter a time in the "Time" edit box.
Socket ID identifies the socket that should clear the statistical information.
The command is issued if the "Clear" button is pressed.
After clearing, the statistical information prior to clearing is shown.
10.5.4. Function "Socket Peek"
This function enables the TCP/IP relay process to copy all the data, coming in and going out,
from a certain socket and send it to the TCP Monitor application. This way it is possible to
"peek" at the information that is being exchanged between two peer processes.
The peeked data can be interpreted as CSTA data, Hexadecimal data, Raw data or iPVN data.
To set the data type for displaying on screen choose the right type in the upper part of the
454
window.
Figure 10-7 "Socket Peek" window
Start the peeking of data by pressing "Start Peek". A window will pop up in which you must
enter the ID of the socket to be peeked (see 10.5.1. Function "Socket Overview...")
Screen output can be suppressed by ticking the "Pause screen output" box. Start logging the
peeked data to disk by pressing "Start Log". A window will pop up in which you must enter file
455
name and file type. Use file type Raw (default) in case the log should be send to the service
department, or to save disk space. Files of type Raw thus created can be translated again by
the TCP Monitor Tool by using Data file (DISK) as source (see 10.4. DATA FILE (DISK)).
The time stamp found in the log and in the screen dump is the time of the PC the TCP Monitor
is running on. The [<<] or [>>] indicate the direction of the message:
[<<] The message was received by the PABX.
[>>] The message was send by the PABX.
It is possible to start several peeks on different sockets.
10.5.5. Function "System Information..."
Figure 10-8 "System Information..." window
This function retrieves the following system information:
• Last IP digit
Applicable for CCS systems only. Gives the last digits of the CIE IP address (see 10.3.
NETWORK SOURCE)
• Max sockets
Gives the maximum number of sockets available for connections (i.e. number of used and
unused sockets). At start up, the PABX opens 5 sockets. This means that in that example
there are a maximum of (32- 5=) 27 sockets available for connection with clients.
• Large buffers
Applicable for CCS systems only. Gives the number of buffers not allocated on the CIE.
456
This figure relates to the stacking of messages on the CIE and thus relates to the
performance of the CIE. Under normal conditions this figure is approximately 67. Under
heavy traffic load from the Ethernet, more messages are queued and the number of free
large buffers drops.
• IP gateway
Gives the IP address used by the TCP/IP relay function as default gateway.
10.5.6. Function "Performance Measure"
Echoing messages to the CIE in case of CCS, or to CPU3000 does the performance
measurement. The TCP Monitor sends out a message and waits until it receives that message
again. If it receives the message, the message is send out again. This is done until the stop
button is pressed. After 4096 messages an automatic refresh is done and the new statistic
information is displayed.
Figure 10-9 "Performance Measure" window
The Message size can be changed from CSTA to MONITOR to use the typical message size
required.
10.5.7. Function "TCP Monitor file"
The name of the function (under the heading "Translate" in the main menu) already defines
which kind of file is opened. The TCP Monitor application only supports TCP Monitor log files
(i.e. of type Raw data).
457
Each time the Translate box is changed (the figure below shows CSTA data) the file is reread
and translated.
Figure 10-10 "TCP Monitor file" window
The output is written on the screen can also be written to a disk by Starting a log and after
opening, selecting a translation type.
PROCEDURE: How to generate a TCP monitor log file to send to the

service department
Actions
1. Find out the IP address of the ISPBX that is used for the Ethernet iSLink that is to be
logged.
Refer to 10.3. NETWORK SOURCE for more information. This address will be referred
to as IP-PABX.
2. Find out the IP address of the PC that is used for the Ethernet iSLink that is to be logged.
458
On most NT PCs this can be done in the following way:
- Select Start / Run...
- Fill in "cmd" after "Open". This opens a command window.
- Enter command "ipconfig" in the command window.
Note down the address given after "IP Address". This address will be referred to as IP-
CSTA.
3. Make sure the CSTA application has made a connection to the PABX.
4. Start the TCP Monitor tool.
5. Open the TCP Monitor tool:
- Select Source/Open.
- Tick "Network".
- Fill in IP-PABX after "Host name".
- Click "Open".
6. On the TCP Monitor tool:
- Select Sockets / Socket overview. This opens a "List overview" window.
- In the "List overview" window:
- Find the row where "IP address" is the same as IP-CSTA and "Connect port" is 2555.
- Note down the number under "ID" (first column) of that row. This ID will be referred
to as SOCKET-ID.
If there is no such row then the CSTA application has not made a connection to the
PABX.
- Close the "List overview" window.
7. On the TCP Monitor tool:
- Select Sockets / Socket Peek; Now a "Peek on a socket" window is opened.
- In the "Peek on a socket" window:
- In the upper part of the window you can select how the CSTA data is shown on the
screen. Select the type you want.
- Press "Start Log".
- Enter name of the log file to be generated.
- Make sure you choose file type Raw (*.RAW).
- Press "Start Peek".
- Enter the SOCKET-ID as retrieved in step 6.
8. Let the CSTA application run and let the logging go on until the situation to be logged has
occurred.
9. On the TCP Monitor Tool in the "Peek on a socket" window:
- Press "Stop Peek".
- Press "Stop Log".
The log file is now ready (and the TCP Monitor Tool may be closed).
459
A. OM COMMANDS AND SUBCOMMANDS
This appendix contains the list of the OM commands (MML and Operator desk) and the
related subcommands available in Call@Net. There is not always a one-to-one relation
between the OM command and the subcommand; usually the execution of an OM command
results in the execution of one or more related subcommands.
SUB MML OD DESCRIPTION

COMM. COMM. COMM.
S10300 DITRAF Find Momentary Traffic Observation Results
S10310 DISPTO Display Periodic Traffic Observation Data
S10320 ASTMOB Change Traffic Measurement Object List
DETMOB
ERTMLI
S10321 DITMOB Read Traffic Measurement Object List
S10330 STRTTM Start or Stop Traffic Measurement
STOPTM
S10331 ASTMTI Change / Display Traffic Measurement Timing
DITMTI
DETMTI
S10340 CHTMOD Change Logical Device Name
S10341 DITMOD Display Traffic Measurement Output Device / File
Name / Status
DITMOF
DISPTM
S10342 CHTMOF Change Traffic Measurement Output File Name
S10500 STALDM Start Load Monitor
S10510 DIOVLD Display Overview of Load
S10520 CANLDM Cancel Load Monitor
DISLDM
S10530 CHLDCT Tune Load Control Parameters
Table A-1 Subcommands S1xxxx.
460
COMM. COMM. COMM.
S21000 SEDATI 2100 Set Date and Time
DIDATI 2102
S21050 DIEXID 2105 Display Exchange Identity
S21060 CHCLID Change Cluster Identity
DICLID
S21070 ASNOIT Assign, Erase and Display Node Id
ERNOIT
DINOIT
S21100 ASFATI Facility Timing
S21200 DILICS Display License
DEFATI
S21220 RTFING Retrieve Fingerprint
S22000 CHDEAU Change Default Authority Class or Protection
Level
CHDEPR
S22010 DIAUPR Display Default Authority Class or Protection
Level
S22020 CHACIV Change Authority Class Index and Value Relation
S22100 CHPASS Change Password
S23000 CHTFCR 2300 Change Traffic Class Restriction Level
DITFCR 2301
S23010 CHFCMR 2302 Change Facility Class Mark Restriction Level
DIFCMR 2303
461
COMM. COMM. COMM.
S30000 CHDNRC 3000 Add New Extension DNR
S30001 Delete Extension DNR
S30002 Move Extension DNR
S30003 Try Ownership and Claim Resources
S30004 Force Claim or Reset Claim of Resource
S30005 Change DNR-Unit Relation
S30006 Subcommand Check Move Success
S30007 Subcommand Handle Extension Data
S30008 Handle IABD Data
S30010 CHOPDC 3001 Change Operator DNR-Operator Circuit
Relation
S30011 Subcommand Check Operator Move
S30012 Subcommand for Retrieving Message Waiting
Information
S30020 DIDNRC 3002 Display DNR-Circuit Relation
DICDNR 3003
S30060 DIMSNP Display MSN parameters of an EHWA
CHMSNP Change MSN parameters of an EHWA
S30080 DIFMSN Display fixed MSN digits
CHFMSN Change fixed MSN digits
S30100 CHCOBD Change or Display COB Queue Type to DNR
Relation
DICOBD
S30250 CHTRFC 3025 Change Traffic Class of DNR
S30260 DITRFC 3026 Display Traffic Class of DNR
S30280 CHCASC Change Subscriber Category of DNR
S30281 DICASC Display Subscriber Category of DNR
S30290 CHDNRS Change / Display DNR Service Capabilities
DIDNRS
462
COMM. COMM. COMM.
S30300 ASFACM 3030 Assign Facility Class Mark to an Extension
ERFACM 3031 Erase Facility Class Mark of an Extension
S30310 ASSADN Assign, Erase and Display Selective Answering
DNR
ERSADN
DISADN
S30320 DIFACM 3032 Display all Facility Class Marks of an Extension
S30330 CHDFCM Change Default Facility Class Mark Set for
Extensions
DIDFCM
S30340 DIFCSU 3034 Display Facility Class Mark Summary
S30400 CHCALF 3040 Change Call Forwarding Relation
DICALF 3042
S30410 ASRTDN Assign Call Rerouting Diversion Table
ERRTDN Erase Call Rerouting Diversion Table
DIRTDN Display Call Rerouting Diversion Table
S30430 CHFLME 3043 Change Follow Me
DIFLME 3044
S30500 CHHOTL 3050 Change Hot Line
DIHOTL 3052
S30520 CHEPLE Change and Display Entry Point Local Exchange
DIEPLE
S30520 CHEPLE Change and Display Entry Point Local Exchange
DIEPLE
S30600 ASEXSE Handle Secretary Data
CREXSE
S30610 Handle Executive Data
S30611 EREXSE Erase all Executive Data
S30620 DIEXSE Display one or all Executive Secretary Pools
463
COMM. COMM. COMM.
S30630 CRESGR Test on/Create Command File to erase Executive
Secretary Group
ERESGR
S30640 DIESGR Display Subcommand for OM command DIESGR
S30700 CRGRPA Store or Erase Group Arrangement Data
ASGRPM 3070
ERGRPA
DEGRPM 3071
CHACDD
S30710 DIGRPA 3072 Retrieve Group Arrangement Data
DIGRPM
S30730 DIGRPS Retrieve Data of ACD Group and Members
S30740 DIPLPO Retrieve park/line position status or/and exec line
position of DNR
S30800 CHABNR 3080 Change Abbreviated Number
DIABNR 3082
ASIABD 3085
ERIABD 3086
S30900 CHFKDA Change Function Key Data
DIFKDA
S30905 DITFKM Display Translated Function Key Menu
S30910 DIMDNR Display Menu number of DNR
S30920 CHMDNR Change Menu number of DNR
S30930 DIDNRM Display all DNRs related to a Menu number
S30940 CHAGCV 3094 Change Analysis Group or Compatibility Value
DIAGCV 3095
S30960 DOWNLD 3096 Request Download for DNR
S31000 ASPICC 3100 Assign PID or Cost Centre numbers.
ERPICC 3101 Erase PID or Cost Centre numbers.
464
COMM. COMM. COMM.
DIPICC 3102 Display PID or Cost Centre numbers.
S31330 ASAPPF 3133 Assign access to Password Protected Facilities.
ERAPPF 3134 Erase access to Password Protected Facilities.
DIAPPF 3135 Display access to Password Protected Facilities.
S32000 CRCVAL Create Compatibility Value
CHCVAL
DICVAL
S32010 ERCVAL Erase Compatibility Value
S32020 CHCVCA Change CV pair Connection Allowance Relation
DICVCA
S32030 CRCTYP Create / Erase Convertor Type
ERCTYP
DICTYP
S32040 ASCONV Assign Convertor EHWA Relation
ERCONV
S32050 ASCVCT Assign CV pair Convertor Type Relation
S32060 DICONV Display Convertor EHWA Relation
S33000 ASTMSD Assign and Display SSM (TMS) Digit Position
DITMSD
S33010 DITMSW Display SSM (TMS) Window Size
S33020 ASTMSW Assign SSM (TMS) Window Size
S33030 DITMST Display SSM (TMS) Tone Type Relation
S33040 CHTMST Change SSM (TMS) Tone Type Relation
S33050 DITMSL Display SSM (TMS) Logical Name Relation
S33060 CHTMSL Change SSM (TMS) Logical Name Relation
S34000 CHAUCO Change Authorization Code
S35200 DIMERE 3520 Display Metering Results
S35300 STRTTT Start, Stop and Display Toll Ticketing or FDCR
STRTFR
465
COMM. COMM. COMM.
STOPTT
STOPFR
DISPTT
DISPFR
S35400 CHTRLV Change Threshold Level of Route
S35500 CHTTCR Change Toll Ticketing Characteristics
S35600 DITRLV Display Threshold Level of Route Number
S35700 CHTTOD Change Toll Ticketing or FDCR Output Device
CHFROD
DITTOD
DIFROD
S35800 CHFRCR Change FDCR Characteristics
S36100 CHMCNE 3610 Change Special Extension
CHSCNE 3611
CHINEX 3612
CHPLEX 3613
CHOVEX 3614
S37200 CHNDNR Change DNR - Cluster Relation
S36102 Read Night Extension Availability
S36103 Read CANS Extension Availability
S36150 CHTRNE 3615 Change Traffic Class of Night Extension Group
S36160 DISPEX 3616 Display Special Extension
S36200 ASCANS 3620 Change CANS and Hooter Characteristics
ERCANS 3621
CHHOOT 3623
S36250 DICANS 3622 Display CANS and Hooter Characteristics
S37000 CHBDNR Change and Display Basic DNR
DIBDNR
S37010 DADESK Collective deactivation of Desksharing
466
COMM. COMM. COMM.
S37100 CHNAME Change and Display DNR - Name Relation
DINAME
S37200 CHFDNR Assign, Change and Display the Network
Location of a Free Number
DIFDNR
S37300 Subcommand for Retrieve Dynamic Data
S37400 CHVLRE Assign, Change, Delete and Display Voice Logging
DIVLRE Relations
S37500 CHFSTA Change Facility State
467
COMM. COMM. COMM.
S40200 ASTREE 4020 Perform Number Analysis Action
CHTBAR 4024
ASBARR 4026
ERBARR 4027
S40210 ASBLCK 4021 Insert Analysis Result
ASINTN 4022
ASEXTN 4023
MAKENU 4025
DIBARR 4028
DIDIAL
DINASM
DINASD
DINARS
S40220 ASGECA Assign or Erase General Cancel Code
ERGECA
DEGECA
S40240 CHTRIF Assign Tariff Structure
S41000 CHLDOM Assign, Change and Delete Local Domain Relation
ERLDOM
CHDNRL
DIDNRL
CHRTLD
DIRTLD
S41010 CHLODD Change Location Determination Data
S41020 CHNPCD Change Numbering Plan Conversion Data
S42000 CHAQPR Change Answering Priority of A-Queue
S42010 CHQLMR Change / Display Queue Lamp Relation
DIQLMR
468
COMM. COMM. COMM.
S42030 CHMQPR Change Answering Priority of M- or C- Queue
CHCQPR
S42040 DIMQPR Display Answering Priority of M- or C- Queue
DICQPR
S42050 DIOPAC Display List of Active or Idle Operators
DIOPID
S42060 DIOPCT Display Activity of Operator Continuously
S42070 DIOPST Display Status of Operator
S42100 CHBBUT Change Trunk Access Code of B-Button
DIBBUT
S42200 CHOPAV Change Operator Availability List
DIOPAV
S42300 CHASOP Change Assistance Group of Operator
DIASOP
S42310 CHASCV Change Assistance Group to Compatibility Value
Relation
DIASCV Display Assistance Group to Compatibility Value
Relation
S42320 DIOPLD Display Load of Operator
S42400 CHASPR Change Assistance Group Properties
DIASPR Display Assistance Group Properties
S43000 CRBSPT Create BSPT Definition
DIBSPT
S45000 CHDSTC Perform Trunk Network Action
S45010 CHDSTC Perform Trunk Network Action - Delayed
Seizure
S45020 CRROUT Perform Trunk Service Action
ERROUT
ASDGCV
469
COMM. COMM. COMM.
ERDGCV
S45030 CHRTCG Change Route Characteristics General
S45040 CHRTCI Change Route Characteristics Incoming
S45050 CHRTCO Change Route Characteristics Outgoing
S45060 CHBNDC Change Bundle Characteristics
S45070 ASBNDL Allocate or De-allocate Bundle to or from Route
DEBNDL
S45080 ASLINE Assign Line to Bundle
DELINE
S45100 DIDEST Display Destination Data
S45110 DIROUT Display Route / Bundle / Line Data
DIBNDL
DILINE
DIFTLD Display Fixed Trunk Line Destination
S45120 CHBDTU Change Bundle DTU relation
DIBDTU
S45130 ASBSPR Change Route-BSPT Relation
ERBSPR
DIBSPR
S45140 ASBSPB Change Bundle-BSPT Relation
ERBSPB
DIBSPB
S45150 CHCDED Change (B-) Channel Dedication
S45160 DITCRT Display (ISDN) Trunk Circuit
S45170 ASDGCO Assign, Erase and Display Digit Conversion on an
Outgoing Route
ERDCGO
DIDCGO
S45180 ASBNDL Validate before ASBNDL / CHBNDL
470
COMM. COMM. COMM.
CHBNDL
S45190 ASBNDL Set DPNSS-mark of Route
S45200 CHIBNC Change Inter Unit Bundle Data (CCS)
ASIBND
DEIBND
S45210 ASILIN Change Inter Unit Line Data (CCS)
DEILIN
S45230 CHPVNR Assign and Delete PVN data
CHPVND
CHPVNS
CHPVNT
ASPVNU
DEPVNU
S45240 CHFTLD Change Fixed Trunk Line Destination
S45250 DIPVNR Display PVN data
DIPVNU
DIPVND
DIPVNT
S45300 CHRORE Change Route Relation (CCS)
CHUNRE
S45310 DIURRE Display Unit and Route Relation (CCS)
S45400 DIROTA Display Route Table
S45410 CHROTA Change Route Table
S45420 CHCVAP Change Compatibility Value-assistance Point
Relation
S45430 DICVAP Display Compatibility Value-assistance Point
Relation
S45500 CHCCTR Change and Display CLI or COL Translation Table
DICCTR
471
COMM. COMM. COMM.
DICCRT
S45600 CHQFSM Change and Display QSIG Facility Selection
Method
DIQFSM
S46000 DIPARE Perform Action on Paging Area or Paging Route
(CCS)
CRPARE
CHPARE
ERPARE
CRPART
ERPART
CHPANL
S46010 CRPART Perform Action on Paging Route
CHPAMD
ERPART
DIPARE
S46020 ASPACD Perform Action on Paging Resource
DEPACD
ASPALN
DEPALN
DIPALN
S46030 DIPART Display Paging Route Data
472
COMM. COMM. COMM.
S50100 TSALRM Test the Alarm Equipment
S50200 INTEST Insert Manual Test Request
DETEST
DITEST
S50300 ASDICA Create Directed Calls
S50301 DEDICA Delete Directed Calls
S50302 DIDICA Display Resources Used by Directed Calls
S50500 CHPATM Change Periodic Autonomous Test (PAT) Mode
DIPATC
CLPATC
S51000 DUSYSD Perform Action on Diagnostical System Data
ERSYSD
S51010 CHSYSD Perform Action for Change System Dump Data
S51020 DISYSD Perform Action for Display System Dump
Information
S55000 CRCCSP Set Up Controlled Connection
CRCCPP
S55010 DICOCO Manage Controlled Connection
ERCOCO
SECCTO
DICCDI
SECCDI
473
COMM. COMM. COMM.
S60230 DIMAJA 6020 Display History Buffer
DIMINA 6021
DISILA 6022
DIHIBU 6023
DIBLCK 6025
S60260 REROUT 6026 Reroute Alarm Signalling
S60270 DIDILA Digital Line Alarms
ERDILA
S60280 DICTAA Display and Erase CTA Alarms
ERCTAA
S60290 CLALRM 6029 Clear Alarm Buffers
S65000 CHANNO Change Announcement on Incoming Trunks
S65010 CHANNO Change Announcement Information for ACD
S65015 DIANNO Display Announcement Information for ACD
474
COMM. COMM. COMM.
S70100 SETINS 7010 Set Circuit Conditions
S75000 CHPDOD Change and Display Peripheral Data Output
Device
DIPDOD
FRCOUT 7015
S70110 Get Resource Degradation Level
S70300 DISERV 7030 Display Service Condition
S70310 FISERV 7031 Find Resource with given Circuit Condition
S70320 DIVICH Display Service Condition of Virtual Channel
S70330 DICCSS Display CPU slice status mask (CCS only)
S70399 Display all Resources with given Type and Claim
S70400 UNIINS Set and Display Unit Status (CCS)
UNININ
DIPCRT
S75000 CHPDOD Change and Display Peripheral Data Output
Device
DIPDOD
S75010 CHPDFS Change and Display Peripheral Data File Status
DIPDFS
S75020 STRTPT Start, Stop and Display Peripheral Circuit Trace
STOPPT
DIPCRT
475
COMM. COMM. COMM.
S80000 LDOVLM Handle Overlay Modules
DEOVLM
DIOVLM (from Call@Net 2.4 only OM command DIOVLM
SEOVLM exists).
REOVLM
S81100 ACTUPD Validation subcommand for ACTUPD (CCS)
S81110 Execution subcommand for ACTUPD (CCS)
S81500 STWARM 8151 Load, start and Reconfiguration
STCOLD 8152
STLOAD
STPROJ
S81530 STDUAL Start dual mode (CCS only)
SPDUAL Stop dual mode
SWDUAL Swap cluster mode
S81540 UPDUAL Validate the UPDUAL request in each unit (CCS
only)
S81550 UPDUAL Initiate reconfiguration/activation stage in each
unit (CCS only)
S81560 STMAIN Start and Stop Maintenance Mode
SPMAIN
S81600 STLOBP Start Load Boot Program
S83000 GEBUMI 8300 Generate Back-up in Memory Image Snapshot
S83001 PUBUMI 8301 Validate before making MIS-file or Retrieve-file
S83002 CHCOMP Set Network Compatible (CCS)
S83003 DICOMP Display Network Compatibility
S83005 RTRIEV Retrieve PE and OM Data from System
S83006 Generate Back-up in Logical Format
S83010 UPDATE Update Unit from Journal (CCS)
S85000 Create Batch Job
476
COMM. COMM. COMM.
S85010 DISJOB Display Batch File Execution
S85020 CANJOB Command File Execution
SUSJOB
RESJOB
S85030 SUBJOB Submit Batch File Execution
S85040 INIDSK Perform Test to find out if Device is a Back-up
Device
S86001 CHREMC Assign Remote Maintenance Configuration Data
from Projecting File
S86010 CHRLOD Change remote logging output device
DIRLOD Display remote logging output device
S86020 STRTRL Start remote logging status
STOPRL Stop remote logging status
DISPRL Display remote logging status
477
COMM. COMM. COMM.
S92100 Set Unit Boundaries and System Parameter
S92120 DIMDAT Display Manager Data
S92130 DIMMFC Display MFC Manager Data
S92200 Set System Options
S92230 Set System Timers
S92240 CHPMPD Change Tone Data, Ring Data and Ticker Data
S92250 Write Forward MFC I Data
S92260 Write Forward MFC II Data
S92270 Write Backward MFC A Data
S92280 Write Backward MFC B Data
S92285 Write Termination after Received MFC A Data
S92290 Write Termination after Received MFC B Data
S92300 Write Alarm Code Parameter
S92310 Write Resource Type Parameter
S92400 ASSHLF Assign / Delete Shelf and Modules
DESHLF
S92401 ASTONE Assign / Delete Tone Sources to (from) PM
DETONE
S92416 DITCPC Display TCP/IP Configuration
S92410 ASBRDS Assign / Delete Board
CHPCTB
S92415 DIBRDS Display Data about Boards
S92420 DIMACA Display MAC-Address Relations
S92425 ASPCTB Assign, Change and Delete Peripheral Circuit
CHPCTB
DEPCTB
S92430 ASLINK Assign / Delete Link
478
COMM. COMM. COMM.
DELINK
S92435 DILINK Display Link Data
S92440 ASLDNM Define, Erase or Retrieve Logical Device Name
(LDN)
DELDNM
S92445 ASPORT Assign, Change or Delete Port Characteristics
CHPORT
DEPORT
S92450 ASDEVC Assign / Delete Device
DEDEVC
CHDEVA
S92455 Select next Sub-command for Command
DICONF
S92456 DICONF Display Configuration Data
S92457 DICONF Display Configuration Data
S92460 DICHAR Retrieve Device Characteristics
DIDEVC Display Device Characteristics
S92465 DIPORT Display Port Characteristics
S92480 ASCRUE Assign Clock Reference Unit Entry
DECRUE
S92485 DICRUE Display Clock Reference Unit Entry
S92500 ASBRVC Assign / Delete Board relation and/or virtual
channels
DEBRVC
S92510 FIPCTT Find PCT by Type
S92600 CHPMPD Change Signalling Group Data
S92620 CHPMPD Change Slave Data
S92630 DIPMPD Display PM Projecting Data
S92650 CHIPPD Change IP Projecting Data for EL@Ns
479
COMM. COMM. COMM.
S92660 ACIPPD Activate IP Projecting Data for EL@Ns
S92670 DIIPPD Display IP Projecting Data for EL@Ns
S92700 INSTPK Install Software Package Relation
S92710 DIPACK Display Software Package
DEPACK Delete Software Package
S92730 STDOTE Start Downloading Terminals
DIDOTE
S92750 DIEQID Display Equipment Identification
S92800 CHCVMH Change MOH-CV relation
DICVMH Display MOH-CV relation
S92910 STFTPS Start FTP Server
S93100 CHPROF Change Client Service Profile
S93110 DIPROF Display Client Service Profile(s)
S93120 CHIPPR Change IP Address - Client Service Profile
Relation
S93130 DIIPPR Display IP Address - Client Service Profile
Relation(s)
S99000 FIOWNR Display all Resources with Specified Owner
S99010 DIPCHD Display Physical Channel Destination
S99100 TRSYSD Perform Action on Dump Trigger
S99120 DIROCO Read and Reset Routing Counters
S99130 DIPVAR Display Number of Free Packets once per Minute
S99140 DIPOOL Read Number of Free Packets
S99150 STMONI Start (reset) unrestricted status monitoring
S99160 CHPMFU Change PM Function
DIPMFU Display PM Function
S99200 CHBSPT Change BSPT Definition
S99210 DIISDN Display ISDN dynamic trunk access data
480
COMM. COMM. COMM.
S99500 STSRVC Start IP-Service
SPSRVC Stop IP-Service
S99510 DISRVC Display IP-Service
S99610 CHTRAP Change the Status of a System Trap
DITRAP Display System Traps
S99620 DIMEUS Display Memory Usage
S99700 DIPMON Display PVE Monitor
481
B. SIGNALLING, COMMANDS & MESSAGES
This appendix only contains a summary of the signalling information and the format of the
commands & messages of the following PCTs:
- ALC;
- RST-KD01;
- ATU-SS01;
- ATU-ST02;
- ATU-CH02;
- ATU-EMxx;
- ATU-AS01.
For detailed information of the commands & messages format of all types of PCTs reference
is made to the Hardware Manual; detailed signalling information can be found in the Signalling
Data Manual.
When interpreting the observation results, the reader should be aware of the fact that:
- The signalling information depends on the PPU type module;

- The format of the commands & messages can be different for the various versions of a
particular PCT type.
B.1. ALC COMMANDS & MESSAGES
• Messages from PCT to PMC
482
MSB 6 5 4 3 2 1 LSB
Detectors DIS LD GKD X X X X X
DIS = Disabled indicator: 0 = enable ALC;

1 = disable ALC.
LD = loop detector: 0 = open loop;

1 = Closed loop
GKD = earth detector: 0 = no earth on a-wire;

1 = earth on a-wire
X = Don’t care.:
Disabled 1 1 1 1 1 1 1 1
• Commands to the PCT
483
MSB 6 5 4 3 2 1 LSB
Drivers X X T X PR R* PDN DIS
T = Test access relay: 0 = test access bus connected;

1 = test access bus disconnected.
R = Ring/speech: 0 = ring;
1 = speech.
PDN = Power down: 0 = enable CODEC/filter;
1 = disabled CODEC/filter.
DIS = Disabled indicator; 0 = enable ALC;
1 = disable ALC.
PR = Polarity Reversal: 0 = off
1 = on
X = Don’t care.:
Disabled 1 1 1 1 1 1 1 1
Ringing state 1 1 1 1 1 0 1 0
Speech condition 1 1 1 1 1 1 0 0
Idle 1 1 1 1 1 1 1 0
B.2. RST-KD/01 COMMANDS & MESSAGES
All command/message bytes are transmitted/received with the least significant bit first.
COMMAND BITS
MSB 6 5 4 3 2 1 LSB
RECEIVE 1) 0 1 X X X X X X
IDLE 0 0 X X X X X X
DISABLE 1 X X X X X X X
1) X is don't care.
Table B-1 RKT Commands
484
MESSAGE BITS
MSB 6 5 4 3 2 1 LSB
DIGIT- 2) 0 0 0 D D D D 1
RECEIVED
AVAILABLE- 3) 0 0 0 0 0 0 0 0
EOD
DISABLED 4) 1 1 1 1 1 1 1 1
2) D is digit field.
3) In response to IDLE command or END-OF-DIGIT state.
4) In response to DISABLE command.
Table B-2 RKT Messages
COMMAND BITS
MSB 6 5 4 3 2 1 LSB
SEND-DIGIT (SKT) 0 1 X 1 D D D D
STOP- (SKT) 0 1 X 0 X X X X
SENDING
RECEIVE (RDT) 0 1 1 X X X X X
RESET-RDT (RDT) 0 1 0 X X X X X
IDLE (SKT and 0 0 0 0 X X X X
RDT)
DISABLE (SKT and 1 X X X X X X X
RDT)
Table B-3 SKT-RDT Commands
485
MESSAGE BITS
MSB 6 5 4 3 2 1 LSB
TONE-RECEIVED 0 0 0 0 0 0 0 1
AVAILABLE- 3) 0 0 0 0 0 0 0 0
EOD
DISABLED 4) 1 1 1 1 1 1 1 1
3) In response to IDLE command or END-OF-DIGIT state.
4) In response to DISABLE command.
Table B-4 SKT-RDT Messages
B.3. ATU SIGNALLING, COMMANDS & MESSAGES
B.3.1. ATU-SS01
• Messages
MSB 6 5 4 3 2 1 LSB
Detectors 0 CD MD 0 0 0 0 0
CD = Call detector (15-50Hz).
MD = Metering pulse detector (50Hz, 12/16kHz).
The bits are ‘1’ when the condition is present and ‘0’ when absent
Disabled 1 1 1 1 1 1 1 1
• Commands
486
MSB 6 5 4 3 2 1 LSB
Drivers TP CP TA* I* S* - PDN 0
TP = Transmission pad.
CP = Compensation pad.
TA = Test access relay.
I = Impulse (dial) relay.
S = Short circuit relay.
PDN = Power down (CODEC/filter)
A ‘1’ activates a driver except for the bits marked by*; these bits are inverted.
Disabled 1 1 1 1 1 1 1 1
• Signalling ATU-SS01
SIGNAL PUBLIC EXCHANGE ATU

LINE CIRCUIT INCOMING
CONNECTION
IDLE a to - 48V; b to earth Open Loop; detector CD off
SEIZURE RING a to - 48V; b to earth Open loop; detector CD on
RING CURRENT
CLEAR FORWARD IN RING a to - 48V; b to earth Open loop; detector CD off
STATE
ANSWER a to - 48V; b to earth Relay i closed, relay s open
CLEAR BACKWARD a to - 48V; b to earth Open loop
Table B-5 Incoming Seizure without Polarity
487
LINE CIRCUIT OUTGOING
CONNECTION
IDLE a to - 48V; b to earth Open loop; detector CD off
SEIZURE a to - 48V; b to earth Relay i closed
PRE-SENDING-PAUSE a to - 48V; b to earth Relay i closed
DIGIT PULSE a to - 48V; b to earth Relay i open, relay s closed
PULSE PAUSE a to - 48V; b to earth Relay i closed, relay s closed
INTER DIGIT PAUSE a to - 48V; b to earth Relay i closed, relay s closed
METERING PULSE (first is a to - 48V; b to earth Relay i closed, relay s open
answer) MT operate
CLEAR FORWARD a to - 48V; b to earth Open loop
ENQUIRY a to - 48V; b to earth Relay i open, relay s closed
Table B-6 Outgoing Seizure without Polarity.

CONNECTION
SEIZURE RING a to - 48V; b to earth Open loop; detector CD on
RING CURRENT
CLEAR FORWARD IN RING a to - 48V; b to earth Open loop; detector CD off
STATE
ANSWER a to - 48V; b to earth or Relay i closed, relay s open
a to earth; b to - 48V PD operate
CLEAR BACKWARD a to - 48V; b to earth or Open loop
a to earth; b to - 48V
CLEAR FORWARD a to - 48V; b to earth PD release
(optional)
Table B-7 Incoming Seizure with Polarity.
488
CONNECTION
SEIZURE a to - 48V; b to earth Relay i closed; detector PD
off
PRE-SENDING-PAUSE a to - 48V; b to earth Relay i closed
DIGIT PULSE a to - 48V; b to earth Relay i open, relay s closed
PULSE PAUSE a to - 48V; b to earth Relay i closed, relay s closed
DIALLING
INTER DIGIT PAUSE a to - 48V; b to earth Relay i closed, relay s closed
ANSWER a to - 48V; b to earth or Relay i closed, relay s open
a to earth; b to - 48V PD operate
METERING PULSE (first is a to - 48V; b to earth or Relay i closed, relay s open
answer) a to earth; b to - 48V MT operate
CLEAR BACK a to - 48V; b to earth Relay i closed, relay s open
PD release
CLEAR FORWARD a to - 48V; b to earth Open loop
ENQUIRY a to - 48V; b to earth Relay i open, relay s closed
Table B-8 Outgoing Seizure with Polarity.
B.3.2. ATU-ST02
• Messages
489
MSB 6 5 4 3 2 1 LSB
Detectors DIS FRD MD ID/ DD SD 1 SAD
FKZ
DIS = Disabled indicator.
FRD = Forward release detector.
ID/FKZ = Idle detector/Femkennzeichen (long distance indicator).
DD = Dial detector.
SD = Seizure detector.
SAD = Seizure acknowledge detector
• Commands
MSB 6 5 4 3 2 1 LSB
Driver group 1 1 F* CP I* ST* V* PDN DIS
Driver group 0 0 A B C T D E -
F = Connect FKZ detector (Femkennzeichen -long distance indicator).

ST = Speech path through connect.
V = Connect through during impulsing out.
PDN = Power down (CODEC/filter).
DIS = Disable message transfer.
A = Connect dial detector (DD)
B = Connect idle (ID) and seizure acknowledge (SAD) detector.
C = Connect a-wire, via low resistance, to earth.
T = Test switch relay
D = Connect a/b-wires to speech condition potentials of incoming call.
E = Connect seizure detector (SD).
• Initialization Command Bits
MSB 6 5 4 3 2 1 LSB
Driver group 1 1 1 0 1 1 1 1 1
Driver group 0 0 0 0 0 0 0 0 -
490
• Signalling ATU-ST02
491
CONNECTION
IDLE a : low resistance to - 60V a : high resistance to earth
b : high resistance to earth b : low resistance to - 60V
Detector ID on
SEIZURE a : low resistance to - 60V a : high resistance to earth
b : low resistance to earth b : low resistance to - 60V
Detector SD on
DIGIT PULSE (without FKZ) a : low resistance to earth a : low resistance to - 60V
b : talking state potential b : without potential
Detector DD on
DIGIT PULSE (with FKZ) a : low resistance to earth a : low resistance to - 60V
b : low resistance to - 60V b : high resistance to earth
Detector DD on, detector
FKZ on
DIGIT PAUSE a : without potential or low a : low resistance to - 60V
resistance to - 60V
b : talking state potential b : without potential
Detector DD off
INTER DIGIT PAUSE a : low resistance to - 60V
Potentials of the talking state b : without potential
Detector DD off
NUMBER COMPLETE Potentials of the talking state a : low resistance to earth
b : low resistance to - 60V
ANSWER (if there was a Potentials of the talking state a : low resistance to earth
FKZ) b : low resistance to - 60V
ANSWER (if there was no Potentials of the talking state a : high resistance to earth
FKZ) b : low resistance to - 60V
BUSY Potentials of the talking state a : low resistance to earth
492
CONNECTION
ON-HOOK CALLED PARTY Potentials of the talking state a : low resistance to earth
(FLSZ pulse) b : low resistance to - 60V
ON-HOOK CALLED PARTY Potentials of the talking state a : high resistance to earth
(FLSZ pause) b : low resistance to - 60V
CLEAR FORWARD AC current on a/b line Potentials of the foregoing
state
Detector FRD on
Table B-9 Incoming Seizure.
493
CONNECTION
IDLE a : low resistance to - 60V a : high resistance to earth
Detector ID on
SEIZURE a : low resistance to - 60V a : low resistance to earth
SEIZURE a : low resistance to earth Detector SAD on.
b : low resistance to - 60V Switch off potentials and
close loop
DIGIT PULSE a : low resistance to earth Open loop
DIGIT PAUSE a : low resistance to earth Closed loop
INTER DIGIT PAUSE a : low resistance to earth Closed loop
METERING 16 kHz pulse on the a/b line Closed loop
Detector MD on
CLEAR FORWARD Same potentials as in the Open loop
foregoing state
Table B-10 Outgoing Seizure.
B.3.3. ATU-CH02
• Messages
494
MSB 6 5 4 3 2 1 LSB
Detectors DIS - - LD - - - -
DIS = Disabled indicator:
LD = loop current detector:
Disabled 1 1 1 1 1 1 1 1
• Commands
MSB 6 5 4 3 2 1 LSB
Drivers TP CP TA* I* ST* D* PDN DIS
ST = Switch through relay.
D = D-relay; connects selected potentials to a/b-wires.
• Initialization Command Bits
MSB 6 5 4 3 2 1 LSB
0 0 1 1 1 0 1 0
• Signalling ATU-CH02
495
SIGNAL ATU ATU
OUTGOING INCOMING
CONNECTION CONNECTION
IDLE a to - 48V; b to earth a to -4 8V; b to earth
Detector CD off Detector CD off
SEIZURE DC loop between a & b a to - 48V; b to earth
Detector CD on Detector CD on
DIGIT PULSE DC loop open a to - 48V; b to earth
Detector CD off
DIGIT PAUSE DC loop between a & b a to - 48V; b to earth
Detector CD on
INTER DIGIT PAUSE DC loop between a & b a to - 48V; b to earth
Detector CD on
NUMBER COMPLETE *) DC loop between a & b a & b no potential
Detector CD off
ANSWER *) DC loop between a & b a & b no potential
Detector CD off
TALKING, BUSY, FREE DC loop between a & b a to - 48V; b to earth
CLEAR FORWARD DC loop open a to - 48V; b to earth
CLEAR BACKWARD *) DC loop between a & b a & b no potential
*) If projected.
Table B-11 Line Signals for Loop Current Tie Line
496
SIGNAL ATU ATU
OUTGOING INCOMING
CONNECTION CONNECTION
IDLE a & b to earth a & b to earth
SEIZURE a & b to - 48 V a & b to - 48 V
DIGIT PULSE a & b no potential a & b to earth
Detector CD off
DIGIT PAUSE a & b to - 48 V a to - 48V; b to earth
Detector CD on
INTER DIGIT PAUSE a & b to - 48 V a to - 48V; b to earth
Detector CD on
NUMBER COMPLETE *) a & b to - 48 V a & b no potential
Detector CD off
ANSWER *) a & b to - 48 V a & b no potential
Detector CD off
TALKING, BUSY, FREE a & b to - 48 V a & b to earth
CLEAR FORWARD a & b no potential a & b to earth
CLEAR BACKWARD *) a & b to - 48 V a & b no potential
*) If projected.
Table B-12 Line Signals for Simultaneous Tie Line.
B.3.4. ATU-EMxx
• Messages
497
MSB 6 5 4 3 2 1 LSB
Detectors DIS 0 0 E 0 0 0 0
E = e-wire detector:
Disabled 1 1 1 1 1 1 1 1
• Commands
MSB 6 5 4 3 2 1 LSB
2-wire circuit TP CP TA* M - - PDN DIS
4-wire circuit T0 T1 TA* M X* T2 PDN DIS
T0, T1, T2 = Attenuator (PAD) control bits for 4 - wire circuits; see table B13.
M = m/mm - wire control relay.
X = Compander control relay.
498
T0 T1 T2 LINE TYPE
0 0 0 Coupling with carrier equipment
0 0 1 Coupling with switched lines
0 1 1 CCITT Rec. for international lines
1 0 1 Coupling with analogue trunk unit
1 1 0 Coupling with digital trunk unit
Table B-13 Line Types
The tables on the following pages give the strapping information of the ATU-EMxx 2 & 4-
wire.
• 2 & 4-wire Signalling Strapping
499
SITUATI DESCRIPTION STRAPS M- M-
ON RELAY CONTACT
(TONES ON X X X X X X M-BIT RELAY DE-
WHEN:) *) ENERGIZED
1 2 3 4 5 9 1 0
m-
wir
e
ear
th/
ope
n
1 - Idle and mains + - + - - - off on See (a) in
failure figure below
2 - Busy and mains + - + - - + on off
failure
3 - Busy and not + - - + - - off on See (b) in
mains failure figure below
4 - Idle and not + - - + - + on off
mains failure
m-wire minus/
open
5 - Idle and mains - + + - - - off on See (c) in
6 - Busy and mains - + + - - + on off
failure
7 - Busy and not - + - + - - off on See (d) in
8 - Idle and not - + - + - + on off
mains failure
m-wire loop/open
9 - Idle and mains - - + - + - off on See (e) in
10 - Busy and mains - - + - + + on off
failure
500
SITUATI DESCRIPTION STRAPS M- M-
ON RELAY CONTACT
(TONES ON X X X X X X M-BIT RELAY DE-
WHEN:) *) ENERGIZED
1 2 3 4 5 9 1 0
11 - Busy and not - - - + + - off on See (f) in
12 - Idle and not - - - + + + on off
mains failure
*) M-BIT: 1 = Idle/inactive; 0 = Busy/active.
Table B-14 ATU-EMxx 2 & 4-Wire Signal Reception Strapping (Strap X1, ... , X5, X9)
m m m
(e)
(a) (c) mm
m m m
(f)
(b) (d) mm
Figure B-1 M-contact State
501
SITUATI SIGNALLI CARRIER E-WIRE STRAP X8 E-BIT
ON NG EQUIPMENT *)
1, 4, 5, 8, 9, Tone on idle Tone (idle) Signal **) + 0
12 Open - 0
No tone (busy) Signal **) - 1
Open + 1
2, 3, 6, 7, Tone on Tone (busy) Signal **) - 1
10, 11 busy Open + 1
No tone (idle) Signal **) + 0
Open - 0
*) E-BIT: 0 = Idle/inactive; 1 = Busy/active.
**) Signal: Earth, minus or loop.
Table B-15 ATU-EMxx 2 & 4-Wire Signal Reception Strapping (Strap X8)
• 4-wire Options
BIT X RELAY X COMPANDER STRAP STRAP MM- WIRE

X10 X11
0 on Active + - Earth
- + Open
1 off Inactive + - Earth
- + Open
When both straps X10 and X11 are absent the compander is not used.
Table B-16 Compander Control (Strap X10 and X11)
502
LINE TYPE ATU-EM03 and ATU-EM01 with OTHER ATU TYPES
12NC 9562 151 3910
RECEIVE TRANSMIT RECEIVE TRANSMIT
AMPLIFIED X12 IN X13 OUT X12 OUT X13 OUT
LINE
UNAMPLIFIED X12 OUT X13 IN X12 IN X13 IN
LINE
Table B-17 Transmit and Receive Strap Settings (Strap X12 and X13)
• Signalling ATU-EMxx
503
TYPE OF OUTGOING EXCHANGE INCOMING EXCHANGE
SEIZURE SIGNAL M E E M SIGNAL
CONTINUOUS SEIZURE A A
SIGNALLING A A INCOMING SEIZURE
WITHOUT
OPTIONAL SEIZURE A A
SIGNALS ACKNOWLEDGE
SIGNALLING A A A A INCOMING SEIZURE
WITH DELAY DELAY DIAL
DIAL
A A A A PROCEED TO SEND
SEIZURE A A
ACKNOWLEDGE
SIGNALLING A A A A INCOMING SEIZURE
WITH SEIZURE ACKNOWLEDGE
ACKNOWLEDGE
SEIZURE A A A A
ACKNOWLEDGE
WITH PROCEED
TO SEND A A A A PROCEED TO SEND
SEIZURE A A A A
ACKNOWLEDGE
PULSE SEIZURE A A
SIGNALLING INCOMING SEIZURE
WITHOUT
OPTIONAL SEIZURE
SIGNALS ACKNOWLEDGE
PULSE SEIZURE A A
WITH SEIZURE ACKNOWLEDGE
ACKNOWLEDGE
SEIZURE
ACKNOWLEDGE
504
SEIZURE SIGNAL M E E M SIGNAL
PULSE SEIZURE A A
SIGNALLING INCOMING SEIZURE
WITH PROCEED
TO SEND A A PROCEED TO SEND
SEIZURE
ACKNOWLEDGE
M = M driver/detector.
E = E driver/detector.
A means driver/detector is active.
Table B-18 Seizure Protocols

DIALLING SIGNAL M E E M SIGNAL
CONTINUOUS TRANSMIT DIGIT A A
SIGNALLING A A DIGIT RECEIVED
WITH OPTIONAL
ANSWER A A A A ANSWER
ANSWER RECEIVED A A A A
CONT. SIGN. A A ANSWER
OPTIONAL ANSWER RECEIVED A A A A
ANSWER AS A
PULSE
PULSE TRANSMIT DIGIT A A
SIGNALLING DIGIT RECEIVED
WITH OPTIONAL
ANSWER A A ANSWER
ANSWER RECEIVED
Table B-19 Dialling Protocols
505
RELEASE SIGNAL M E E M SIGNAL
CONTINUOUS FORWARD RELEASE A A FORWARD RELEASE
SIGNALLING RECEIVED
WITHOUT RELEASE
RELEASE ACKNOWLEDGE
ACKNOWLEDGE
IDLE
IDLE
CONTINUOUS FORWARD RELEASE A A A A
SIGNALLING A A FORWARD RELEASE
WITH RELEASE RECEIVED
ACKNOWLEDGE
RELEASE
ACKNOWLEDGE
IDLE
IDLE
PULSE FORWARD RELEASE A A
WITHOUT RECEIVED
RELEASE
ACKNOWLEDGE IDLE
IDLE
WITH RELEASE RECEIVED
ACKNOWLEDGE
A A RELEASE
ACKNOWLEDGE
IDLE
IDLE
SIGNALLING A A A A FORWARD RELEASE
WITH RECEIVED
COMPELLED
RELEASE IDLE
IDLE
506
Table B-20 Release Protocols
507
BLOCKING SIGNAL M E E M SIGNAL
CONTINUOUS BLOCKED BY A A
SIGNALLING OPPOSITE
WITHOUT EXCHANGE
RELEASE Repeated until
ACKNOWLEDGE opposite exchange
reacts with signal
PULSE SIGNAL BLOCKED BY A A
WITH CYCLIC OPPOSITE
TEST AND EXCHANGE
RETESTING A A Repeated until
PROCEDURE opposite exchange
reacts with a release
signal or a continuous
signal or a short signal
in case of the release
ack signal is not
projected
PULSE SIGNAL BLOCKED BY A A
WITH ONLY OPPOSITE
CYCLIC TEST EXCHANGE
PROCEDURE A A Repeated until
opposite exchange
signal
PULSE SIGNAL FORWARD RELEASE A A
WITH BLOCKED BY A A
COMPELLED OPPOSITE
RELEASE AND EXCHANGE
ONLY CYCLIC
TEST A A Repeated until
PROCEDURE opposite exchange
signal
508
Table B-21 Blocking Protocols
B.3.5. ATU-AS01 (ALS70)
• Messages
MSB 6 5 4 3 2 1 LSB
Detectors DIS 0 MD 0 HLG 0 LR 0

HLG = Current loop/Low ohmic current loop - speech polarity.
LR = Low ohmic current loop - reverse polarity.
Disabled 1 1 1 1 1 1 1 1
• Commands
MSB 6 5 4 3 2 1 LSB
Driver group 1 1 TP CP I* ST* V* PDN DIS
Driver group 0 0 GH GL RL TA SP SP SP
ST = Speech path through connect.
V = Connect through during impulsing.
PDN = Power down (CODEC/filter).
GH = Connect HG detector.
GL = Connect LG detector.
RL = Connect LR detector.
TA = Test access relay
SP = Spare.
Disabled 1 1 1 1 1 1 1 1
• Signalling ATU-AS01
509
SIGNAL PUBLIC EXCHANGE ATU INCOMING CONNECTION
LINE CIRCUIT
IDLE a to earth; b to - 48 V Relay gh closed; detector HLG off
SEIZURE RING a to - 48 V; b to earth Relay gh closed, relay rl closed;
detector HLG on
PROCEED TO SEND a to - 48 V; b to earth Relay gl closed, relay rl closed; detector
HLG on
DIGIT PULSE a/b open Relay gl closed, relay rl closed; detector
HLG off
PULSE PAUSE a to - 48 V; b to earth Relay gl closed, relay rl closed; detector
HLG on
INTER DIGIT PAUSE a to - 48 V; b to earth Relay gl closed, relay rl closed; detector
HLG on
NUMBER COMPLETE a to - 48 V; b to earth Relay gl open, relay rl closed; detector
HLG off
ANSWER a to - 48 V; b to earth Relay gl closed, relay rl closed; detector
HLG on
CALLED PARTY ON a to - 48 V; b to earth Relay gl open, relay rl closed; detector
HOOK HLG off
CLEAR FORWARD a to earth; b to - 48 V Relay rl closed; detector LR on
RELEASE a to earth; b to - 48 V Relay rl open
ACKNOWLEDGE
BLOCK LINE Relay gl closed; relay rl closed
Table B-22 Incoming Seizure.
510
SIGNAL PUBLIC EXCHANGE ATU OUTGOING CONNECTION
LINE CIRCUIT
IDLE a to earth; b to - 48 V Relay gh closed; detector HLG off
SEIZURE a to earth; b to - 48 V Relay gh closed, relay rl closed, relay st
closed; detector LR on
SEIZURE a to earth; b to - 48 V Relay gh closed, relay rl closed, relay st
ACKNOWLEDGE closed; detector LR on
DIGIT PULSE a to earth; b to - 48 V Relay v closed, relay i open, relay gl
open, relay rl open, relay st open;
detector LR off
PULSE PAUSE a to earth; b to - 48 V Relay v closed, relay i closed; detector
HLG on
INTER DIGIT PAUSE a to earth; b to - 48 V Relay v open, relay i open, relay gl
closed, relay rl closed, relay st closed;
detector LR on
NUMBER COMPLETE a to - 48 V; b to earth Relay gl closed, relay rl closed, relay st
open; detector HLG on
METERING PULSE a to - 48 V; b to earth Relay gl closed, relay rl closed, relay st
closed; detector TMD on
CLEAR BACKWARD a to earth; b to - 48 V Relay gl closed, relay rl closed, relay st
closed; detector HLG off, detector LR
on
CLEAR FORWARD a to - 48 V; b to earth Relay gh open, relay gl open, relay rl
open, relay st open
Table B-23 Outgoing Seizure
511
512

Autocom Abb Sofo

Uploaded by

Copyright:

Available Formats

Autocom Abb Sofo

Uploaded by

Document Information

Original Description:

Original Title

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

Autocom Abb Sofo

Uploaded by

Copyright:

Available Formats

AMENDMENTS

Fully Integrated Networks (FINs) are only supported by the iS3070/3090!

NOTICE TO THE USER

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

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

- OM for test tools;

Furthermore the manual contains the complete description of:

- all the subcommands;

In general the following rules should be kept in mind:

- Be patient with the system;

WARNING: ALTHOUGH REMOTE SECOND LINE MAINTENANCE IS

There are two groups of OM commands:

- OM for Tools (included in the System Software) and

2.2. EXPLANATION OF TERMS

The dynamic data is structured in three separate parts:

• Process Control Block (PCB)

Figure 2-1 Simplest Process Instance.

CB2 CB2 (new)

CB3 (old CB2)

Figure 2-2 Addition of a CB.

There are two classes of partitions:

Figure 2-3 Controlling and Subordinate Partition Relation.

Initial Situation Situation after launching a partition

PACB PACB PACB (new)

CB1 CB1 CB1 (old CB2)

Figure 2-4 Launching a Partition.

Launching a new process is done in a similar way.

PACB PACB PACB (new)

CB1 CB1 CB1(old CB2)

Figure 2-5 Launching a Process.

2.3. OM FOR TOOLS

The OM Commands for Tools comprise the following OM commands:

- DIPOOL: Display number of free packets;

Display Number of Free Packets 293!

Related subcommand: S99140

The displayed information indicates the following items:

Display Routing Counters 292!

Related subcommand S99120

- C1 : Number of IMP messages with time outs;

2.4. SECOND LINE MAINTENANCE TOOLS

The Second Line Maintenance tools comprise the following OM Commands:

- DIPCHD : Display physical channel destination

If parameter CRT is omitted all PCHs will be displayed.

Display Physical Channel Destination 307!

Related subcommand: S99010

Display Waiting Signals in Signal Queue 308!

Display (Main) Processor Load 309!

Before executing this OM command, it is advised to execute OM command DIOVLD first, to

The parameter SOURCE indicates the item to be changed; it can be:

0 = SAS urgent actions;

1 = SAS fault handling;

2 = SAS preventive tests;

7 = CP registration and measurements;

10 = GOS resource management;

5 = maximum simultaneous tasks allowed in numbers;

6 = time out value in minutes;

7 = minimum simultaneous tasks allowed in numbers.

Tune Load Control Data 359!