iS3000/SIP@Net

OM Commands Manual

March 2017
A Publication of
NEC Nederland B.V.
HILVERSUM, THE NETHERLANDS

Date : March 2017

Great care has been taken to ensure that the information contained in this
handbook is accurate and complete. Should any errors or omissions be
discovered or should any users wish to make suggestions for improving this
handbook, they are invited to send the relevant details to:

NEC Nederland B.V.

P.O. BOX 32
1200 JD HILVERSUM
THE NETHERLANDS

© NEC Nederland B.V.

All rights are reserved. Reproduction in whole or in part is prohibited
without the written consent of the copyright owner.
All brand names and product names in this document are trademarks or
registered trademarks of their respective companies.
 CONTENTS

1. INTRODUCTION .................................................................................... 11
1.1. WHAT IS AN OM COMMAND .......................................................................................................11
1.2. OM COMMAND (MML) SYNTAX ..................................................................................................11
1.3. REPRESENTATION OF OM COMMANDS ......................................................................................12
1.4. ON SCREEN HELP FUNCTIONS ......................................................................................................13
1.5. KEYBOARD COMMANDS ..............................................................................................................13
1.6. SYSTEM RESPONSES .....................................................................................................................14
1.7. EHWA STRUCTURE .......................................................................................................................14
1.8. IPv6 ASPECTS................................................................................................................................15

2. ABBREVIATED NUMBERS ...................................................................... 17

3. ANALYSIS GROUP, COMPATIBILITY VALUE AND SERVICE PROFILE ......... 18

3.1. ANALYSIS GROUP AND COMPATIBILITY VALUE ...........................................................................18
3.2. SERVICE PROFILE ..........................................................................................................................18

4. BACKUP MAINTENANCE ....................................................................... 20

4.1. AUTOMATIC GENERATION OF BACK-UP FILES .............................................................................23
4.2. MAKING A FIRE COPY ...................................................................................................................25
4.3. UNIT COMPATIBILITY ...................................................................................................................26

5. BOUNDARIES, OPTIONS AND TIMERS ................................................... 27

6. CALL FORWARDING .............................................................................. 29

7. CAMP ON BUSY .................................................................................... 31

8. CCIS OVER IP ......................................................................................... 32

9. COMMAND FILE EXECUTION ................................................................. 33

9.1. NORMAL COMMAND FILES ..........................................................................................................33
9.2. AUTHORITY OVERRULING COMMAND FILES ...............................................................................34

10. DATA FUNCTIONS ................................................................................. 35

10.1. COMPATIBILITY VALUES AND CONVERTORS ...............................................................................35
10.1.1. Compatibility Values ....................................................................................................................35
10.1.2. Convertors....................................................................................................................................36
10.2. REMARKS ABOUT DOWNLOADING ..............................................................................................37
10.3. SELECTIVE ANSWERING DNR .......................................................................................................38

11. DATE, TIME AND EXCHANGE-ID ............................................................ 39

12. DIGITAL ALARMS .................................................................................. 42

13. DISPLAY METERING .............................................................................. 44

14. DNR/BSP-ID - LINE CIRCUIT/CENTRAL MODULE RELATIONS .................. 45

-3-
15. DOWNLOAD ......................................................................................... 47
15.1. EXTENSION DOWNLOAD ..............................................................................................................47
15.2. TERMINAL DOWNLOAD ...............................................................................................................47
15.3. PERIPHERAL BOARD DOWNLOAD ................................................................................................49
15.4. DT700/DT820 FIRMWARE DOWNLOADING ................................................................................50

16. DPNSS CLUSTER IDENTITY / ASSISTANCE POINT / FREE NUMBERING /

DECT MOBILITY iSNet WAN................................................................... 52
16.1. CLUSTER IDENTITY........................................................................................................................52
16.2. ASSISTANCE POINT.......................................................................................................................52
16.3. FREE NUMBERING ........................................................................................................................53
16.4. DECT MOBILITY IN iSNet WAN .....................................................................................................53

17. EMPOWERED USER ............................................................................... 55

18. EXECUTIVE SECRETARY GROUPS ........................................................... 56

18.1. NORMAL EXECUTIVE/SECRETARY GROUPS .................................................................................56
18.2. ENHANCED EXECUTIVE/SECRETARY GROUPS ..............................................................................57

19. FACILITY CLASS MARKS ......................................................................... 59

19.1. FACILITY CLASS MARKS FOR EXTENSIONS ...................................................................................59
19.2. DEFAULT FACILITY CLASS MARKS .................................................................................................60

20. FACILITY TIMING ................................................................................... 61

21. FAULT REPORTS .................................................................................... 62

21.1. ALARM BUFFERS ..........................................................................................................................62
21.2. HISTORY BUFFERS ........................................................................................................................63
21.3. ALARM ROUTING .........................................................................................................................63
21.4. CORDLESS TERMINAL ADAPTOR ALARMS....................................................................................63

22. FILE MANIPULATION ............................................................................. 64

23. FOLLOW ME .......................................................................................... 66

24. FUNCTION KEYS AND MENUS ............................................................... 67

24.1. FUNCTION KEYS............................................................................................................................67
24.2. MENU-DNR/BSP-ID RELATIONS ...................................................................................................68

25. GENERAL CANCEL CODE / DEACTIVATION DESKSHARING / CHANGE

FACILITY STATE ..................................................................................... 69
25.1. GENERAL CANCEL CODE...............................................................................................................69
25.2. COLLECTIVE DEACTIVATION OF DESKSHARING ...........................................................................69
25.3. CHANGE FACILITY STATE ..............................................................................................................69

26. GROUP ARRANGEMENTS ...................................................................... 70

27. HARDWARE CONFIGURATION............................................................... 74

27.1. MODULES, BOARDS AND CIRCUITS..............................................................................................74
27.1.1. Shelves .........................................................................................................................................75
27.1.2. Boards ..........................................................................................................................................76

-4-
27.1.3. Circuits .........................................................................................................................................78
27.2. SWITCHING NETWORK TONE SOURCES.......................................................................................79
27.3. CLOCK REFERENCE UNIT ENTRIES ................................................................................................79
27.4. D-CHANNELS ................................................................................................................................80
27.5. DEVICES AND LOGICAL DEVICE NAMES .......................................................................................81
27.5.1. Devices .........................................................................................................................................81
27.5.2. Logical Device Names...................................................................................................................83
27.6. LINKS ............................................................................................................................................84

28. HOT LINE............................................................................................... 86

29. IABD AND LENR FACILITY ...................................................................... 87

30. IBSC - BSPT RELATIONS ......................................................................... 88

31. INCOMING CALL SCREENING (INTERNAL/EXTERNAL) ............................ 89

32. INITIALISE DISK ..................................................................................... 91

33. INTEGRATED ANNOUNCEMENT SERVER (IAS)/MUSIC ON HOLD (MOH) 92

33.1. INTEGRATED ANNOUNCEMENT SERVER (IAS) .............................................................................92
33.2. MUSIC ON HOLD (MOH) ..............................................................................................................93

34. INTER UNIT NETWORKING .................................................................... 94

34.1. INTER UNIT ROUTING...................................................................................................................94
34.2. INTER UNIT TRUNK TRAFFIC.........................................................................................................94

35. IP CONFIGURATION AND FTP SERVER ................................................... 96

35.1. IP CONFIGURATION......................................................................................................................96
35.2. FTP SERVER (CPU3000 only) ........................................................................................................97
35.3. CLIENT SERVICE PROFILES ..........................................................................................................100

36. IP ENABLING / SIP ................................................................................102

36.1. IP ENABLING FULL TMP / SIP SIGNALLING DATA .......................................................................102
36.2. SIP TRUNKING ............................................................................................................................106
36.3. SIP EXTENSIONS .........................................................................................................................111

37. LICENSES ..............................................................................................113

37.1. SYSTEM LICENCES ......................................................................................................................113
37.2. HARDWARE-LESS FINGERPRINT .................................................................................................116
37.3. LICENSES FOR DT820 STANDARD SIP TERMINALS .....................................................................116

38. LOAD CONTROL ...................................................................................119

38.1. MONITOR LOAD .........................................................................................................................119
38.2. DISPLAY LOAD ............................................................................................................................119

39. LOCATION SERVICE ..............................................................................121

40. MANAGER DATA AND SUBSCRIBER CATEGORY ....................................122

41. MERCURY INDIRECT SERVICE ...............................................................123

-5-
42. MULTIPLE SUBSCRIBER NUMBER .........................................................124

43. NAME NUMBER RELATIONS .................................................................125

44. NIGHT TRAFFIC AND SPECIAL EXTENSIONS...........................................128

44.1. CANS AND HOOTER ....................................................................................................................128
44.2. NIGHT EXTENSIONS ....................................................................................................................128
44.3. SPECIAL EXTENSIONS .................................................................................................................129

45. NUMBERING SCHEME ..........................................................................130

45.1. NUMBERING SCHEME GENERAL ................................................................................................130
45.2. INTERNAL NUMBERING SCHEME ...............................................................................................131
45.3. EXTERNAL NUMBERING SCHEME ..............................................................................................134

46. OPERATOR CONSOLE ...........................................................................135

46.1. B-BUTTON / ACCESS CODE RELATION........................................................................................135
46.2. QUEUE PREFERENCE ..................................................................................................................135
46.2.1. A-Queue .....................................................................................................................................135
46.2.2. C-Queue .....................................................................................................................................136
46.2.3. M-Queue ....................................................................................................................................136
46.2.4. Queue to Lamp Relation ............................................................................................................137
46.3. OPERATOR AVAILABILITY LIST AND ASSISTANCE GROUP ..........................................................137
46.3.1. Availability List ...........................................................................................................................137
46.3.2. Assistance Group .......................................................................................................................137
46.4. OPERATOR STATUS ....................................................................................................................139

47. OVERLAY MODULES .............................................................................141

48. PAGING................................................................................................142
48.1. GENERAL PAGING ......................................................................................................................142
48.2. VIRTUAL PAGING ........................................................................................................................143
48.3. REAL PAGING..............................................................................................................................143

49. PASSWORD PROTECTED FACILITIES......................................................144

49.1. ASSIGN PASSWORD ....................................................................................................................144
49.2. COSTCENTRES ............................................................................................................................145
49.3. TIME BASED CALL BREAK AT ZERO BUDGET ..............................................................................146

50. PERIPHERAL FILE STORAGE ..................................................................147

50.1. PERIPHERAL FILE STORAGE MECHANISM ..................................................................................147
50.2. PPH PROTOCOL TRACE ...............................................................................................................149

51. PRIVATE VIRTUAL NETWORKING .........................................................150

52. PROJECTING.........................................................................................153

53. QSIG AND ISDN ADDRESSING...............................................................155

53.1. LOCAL DOMAIN DATA ................................................................................................................155
53.2. SPECIAL SERVICE PREFIX ............................................................................................................156
53.3. DNR / ROUTE - LOCAL DOMAIN RELATION ................................................................................157
53.4. LOCATION DETERMINATION DATA ............................................................................................158
53.5. NUMBERPLAN CONVERSION .....................................................................................................159

-6-
53.6. QSIG FACILITY SELECTION ..........................................................................................................159
53.7. INTEROPERATION WITH THE COMPLETE NUMBER IDENTIFICATION (CNI) FUNCTION .............160

54. REMOTE MAINTENANCE ......................................................................161

55. SERVICE CONDITIONS ..........................................................................164

56. SMS SERVICE........................................................................................167

57. SysManager .........................................................................................168

58. SYSTEM DUMP.....................................................................................170

59. SYSTEM SECURITY ................................................................................173

59.1. AUTHORITY AND PROTECTION ..................................................................................................173
59.1.1. Authority Class Indexes ..............................................................................................................174
59.1.2. Authority Classes and Protection Levels ....................................................................................175
59.2. PASSWORDS ...............................................................................................................................176
59.3. RESTRICTION LEVELS ..................................................................................................................178
59.3.1. Facility Class Mark Restriction Levels.........................................................................................178
59.3.2. Traffic Class Restriction Levels ...................................................................................................178

60. TESTING ...............................................................................................179

60.1. PERIODIC AUTONOMOUS TESTING ...........................................................................................179
60.2. MANUALLY CONTROLLED TESTING ............................................................................................179
60.3. TEST OF THE ALARM BOX...........................................................................................................180
60.4. CONTROLLED CONNECTION.......................................................................................................180
60.5. DIRECTED CALL ...........................................................................................................................182

61. TOLL TICKETING AND FULL DETAILED CALL RECORDING .......................183

61.1. TOLL TICKETING..........................................................................................................................183
61.2. FULL DETAILED CALL RECORDING ..............................................................................................184

62. TOOLS ..................................................................................................186

62.1. NUMBER OF FREE PACKETS / ROUTING COUNTERS ..................................................................186
62.2. (SECOND LINE) COMMANDS FOR PVE .......................................................................................187
62.3. VARIOUS OTHER (SECOND LINE) COMMANDS ..........................................................................188

63. TRAFFIC CLASSES .................................................................................190

64. TRAFFIC OBSERVATIONS AND MEASUREMENTS ..................................191

64.1. TRAFFIC OBSERVATIONS ............................................................................................................191
64.2. TRAFFIC MEASUREMENT ...........................................................................................................196
64.2.1. Start, Stop and Status ................................................................................................................196
64.2.2. Timing.........................................................................................................................................196
64.2.3. Output ........................................................................................................................................197
64.2.4. Object List ..................................................................................................................................197
64.2.5. Output Formats ..........................................................................................................................198

65. TRUNK TRAFFIC....................................................................................204

65.1. DESTINATIONS ...........................................................................................................................204
65.2. ROUTE TABLES ...........................................................................................................................205

-7-
65.3. ROUTES ......................................................................................................................................205
65.3.1. Routes General...........................................................................................................................205
65.3.2. Route Characteristics .................................................................................................................206
65.3.3. Digit Conversion .........................................................................................................................206
65.3.4. CLI or COL Translation ................................................................................................................207
65.3.5. QSIG Call Diversion Rerouting Table ..........................................................................................209
65.3.6. Route-BSPT Relation ..................................................................................................................209
65.4. BUNDLES ....................................................................................................................................210
65.4.1. Bundles General .........................................................................................................................210
65.4.2. Bundle-BSPT Relation.................................................................................................................211
65.4.3. Digital Bundles ...........................................................................................................................211
65.5. LINES ..........................................................................................................................................212
65.5.1. CLI/COL Identity of a Trunk Line ................................................................................................213
65.6. FIXED TRUNK LINES ....................................................................................................................213
65.6.1. Destinations and Identities ........................................................................................................213
65.6.2. Entry Point Local Exchange ........................................................................................................214

66. TWINNING ...........................................................................................215

67. UNIT STARTS ........................................................................................216

67.1. DUAL MODE (CCS only) ..............................................................................................................218
67.2. MAINTENANCE MODE (CPU3000 only) .....................................................................................219
67.3. PMC-IP / PMC-SIC / SIC ..............................................................................................................220
67.4. DUAL SERVER / SERVER CLUSTER ..............................................................................................222

68. UNIT STATUS .......................................................................................225

69. VOICE LOGGING ...................................................................................226

A. ERROR MESSAGES ...............................................................................227

A.1. FIXED RESIDENT ERROR MESSAGES (1 ... 99) .............................................................................227
A.2. SPECIFIC NON-RESIDENT ERROR MESSAGES (100 ... 189) .........................................................231
A.3. GENERAL ERROR MESSAGES (190 ... 256)..................................................................................240

B. PARAMETERS .......................................................................................243

C. BOARD AND PCT TYPES ........................................................................320

C.1. BOARD - TYPES ...........................................................................................................................320
C.2. PCT-TYPES ..................................................................................................................................327
C.2.1 Line Circuit (LCT) ........................................................................................................................327
C.2.2. Trunk Circuit (TRC) .....................................................................................................................332
C.2.5. Operator Circuit (OCT) ...............................................................................................................337
C.2.6. In-MFC ........................................................................................................................................338
C.2.8. Paging Circuit .............................................................................................................................338
C.2.9. RS-Socotel ..................................................................................................................................339
C.2.10. Music on Hold (MOH) / Music on COB / Wake-up/MW Announcement Circuit.......................339
C.2.11. D-channel ...................................................................................................................................339
C.2.12. Trunk circuit ISDN (TRC-ISDN) ....................................................................................................340
C.2.13. IAS-TS .........................................................................................................................................340
C.2.14. HATCH ........................................................................................................................................340

D. OVERVIEW OF OM COMMANDS ..........................................................341

-8-
-9-
PREFACE
This manual is valid both SIP@Net platforms : the SIP@Net Server platform and the iS3000 platform.

• SIP@Net Server platform

Platform with an IP-based switching network.
Processors : External Server or In Skin Server (ISS, ISS-2 or ISS-3).
Optionally, this platform can handle IP-PMs.
For more details of the SIP@Net Server, see the "SIP@Net Server - CE Manual".

• iS3000 platform
Platform with a TDM-based switching network.
The subtypes are :
- iS3000 Single processor : CPU3000, ISS, ISS-2, ISS-3 or external server
- iS3000 Fault Tolerant processor : CSM processor module
For more details of the In Skin Server, see the Installation Manual "How to install the ISS/ISS-2/ISS-3".

All of the system platforms 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, ALC-G(R) and ALC-GM/GD.
- DTX-I represents the DTX-I or DTX-I(R).
- PMC represents the PMC-HR, PMC-MC, PMC-G, PMC-SIC or PMC-IP :
- PMC-HR represents the PMC-HR, PMC-G (with NCC-HR),
PMC-SIC (with NCC-HR) or PMC-IP (with NCC-HR).
- PMC-MC represents the PMC-MC, PMC-G (with or without NCC-MC),
PMC-SIC (with or without NCC-MC) or PMC-IP (with or without NCC-MC).
- DTU-PH represents the DTU-PH or DTU-G.
- DTU-PU represents the DTU-PU or DTU-G.
- CPU3000 represents the CPU3000 or the In Skin Server (ISS/ISS-2/ISS-3).
The ISS/ISS-2/ISS-3 can be mounted on the SIC, PMC-SIC or PMC-IP.

SECOND LINE MAINTENANCE COMMANDS

Nowadays the Second Line Maintenance Commands are included in the SIP@Net software packages.
For the sake of completeness, a brief description of these former Second Line Maintenance commands (see
below) is included in this manual in the relevant chapters (mainly in chapter “TOOLS”). More details can be
found in the "Second Line Maintenance Manual".

CHLDCT DIMEUS EXSUBC DIPMON

CHPERD and DIPERD DIPCHD FIOWNR STSRVC
CHPMFU and DIPMFU DIPOOL FCLAIM SPSRVC
CHTRAP and DITRAP DIPVAR FRCPSW DISRVC
DIISDN DIROCO STMONI
DILOAD DISIGQ UPDUAL

- 10 -
1. INTRODUCTION
1.1. WHAT IS AN OM COMMAND

OM stands for Operational Maintenance. An OM command allows you to perform maintenance functions
on an operational system with the minimum of inconvenience. OM commands may be entered via a
Personal Computer or OM terminal using Man Machine Language (MML). An OM command in MML is a
mnemonic of 6 letters. There are two levels of OM commands, called the first and second line maintenance.
This book gives all the first line maintenance commands in MML. The second line maintenance commands
are reserved for the system specialists.

OM via the operator's desk is not so user friendly and the number of operator desk commands is limited.
An OM command on the operator's desk consists of a 4-digit code. See the OM COMMANDS MANUAL
(OPERATOR DESK) for these commands.

The use of OM commands includes:

- The specification and modification of project dependent data like External Numbering Scheme and
Traffic Classes.
- Changing of service conditions.
- Reading of alarms and system status reports.
- Assigning of facilities to extension users.

1.2. OM COMMAND (MML) SYNTAX

Each OM command comprises a six character mnemonic, a colon (:), a number of parameters (some or all
of which may be optional) separated by commas and finally a semi-colon (;) or an exclamation mark (!).
If you terminate the command with a semi-colon the command is executed and the system prompt < is
returned.

Parameters are shown like this : <DNR>

This means that you must enter the information representing the directory number (DNR) of an extension.

Optional parameters are shown like this : [<DNR>]

This means that anything inside the square brackets [ ] may be omitted. In certain cases the square
brackets may contain a number of parameters or a parameter and a comma. In such cases it denotes that
either everything inside the brackets must be filled in or everything inside the brackets must be omitted.

Example: A BSP-ID has the format : <DNR>[-<BSPT>].

Note: Unit numbers are always shown as [<UNIT>].

As a rule this parameter is mandatory in multi-unit systems and must be omitted in single unit
systems. Unit '0' may be entered: this is the unit the OM terminal is connected to.

Parameters are always of the ‘single” type and some may be of the ‘series' and/or ‘range' type depending
on the OM command used.

- 11 -
- Single : A single number, e.g. <DNR>
For example : 34078
- Series : Two, three or four numbers separated by ampersand signs (&). The possibility to
input a series is indicated in this book by an s after the parameter, e.g. <DNR>s
For example : 34078&34079&34062
The OM action is performed for each of the numbers. The numbers need not be in
sequential order.
- Range : Two numbers separated by two ampersand signs (&&). The possibility to input a
range is indicated in this book by an r after the parameter, e.g. <DNR>r
For example : 34070&&34079
The OM action is performed for all numbers from the lowest to the highest
inclusive. The first number must be lower than the second.
- Series/Range : The parameter can be series or range. This is indicated by s/r after the parameter,
e.g. <DNR>s/r.
The two types cannot be mixed, e.g. 34070&34079&&34100 is not a valid input.
Series/range on a BSP-ID parameter is only possible when the BSPT part is the
same, e.g. 2406-98&&2410-98 is allowed, 2406-97&&2410-98 is not allowed.

1.3. REPRESENTATION OF OM COMMANDS

Throughout this book everything you type in is shown in bold capitals: LIKE THIS.
System responses are in small capitals : LIKE THIS.
An OM command in this book has the following layout:

Change Abbreviated Number 124 # !

CHABNR:<ABBR-NUMBER>[,[<EXP-NUMBER>],[<TRFC>][,<AG>s/r]];
The heading gives the description of the OM command. The number after the heading indicates the
authority class index. This index is used to change the authority class of the command. A # sign indicates
that this command is written to the journal file, if the journal updating is on. The exclamation mark (!)
means that the command can only be executed with the journal updating on, i.e. it will not execute when
OM command SWJUPD:0; is executed.

If the terminal you use does not have the same authority class the command cannot be executed. OM
command DIOVLM displays the authority class of this command.

The actual command description follows in the box. The box contains the 6 letter mnemonic, followed by
parameters. The meaning of the parameters is explained in appendix B. PARAMETERS. This appendix also
gives the minimum and maximum value of the parameter. Note that the maximum value might be set
lower in the projecting for your exchange. Consult the Office Data Manual of your exchange for these
values.

The command you type in might look like this:

CHABNR:**33,0224978,4;

This command links abbreviated number **33 to expanded number 0224978 and tells the system that a
user of this abbreviated number must have at least traffic class 4. Because the analysis group number <AG>
is omitted, the abbreviated number is added to the common pool. The system replies with : EXECUTED.

- 12 -
1.4. ON SCREEN HELP FUNCTIONS

To facilitate the use of OM commands the system offers help texts (guidance) on the screen during an OM
session. This guidance can be subdivided into:

• Guidance About all OM Commands

To obtain a list of available OM commands simply enter a question mark (?) after the system prompt (<).
However this is only for non-coded OM-sessions. This means that this feature is not available for OM-
sessions via PC-applications.

• Guidance About One OM Command

To obtain the correct syntax (i.e. the version of the OM command resident in your system) of a
particular OM command, enter the six character code, a colon and a question mark. The syntax is then
displayed with a description of the parameters. The system ends by repeating what was already typed in.
CHABNR:?
Change abbreviated number
CHABNR:<ABBR-NUMBER>[,[<EXP-NUMBER>],[<TRFC>][,<AG>s/r]];
If only the abbreviated number is entered, the erase function will be
executed. If the analysis group number is omitted, the common analysis
group number is used.

After this the parameter guidance can be used. See below.

• Guidance About One Parameter

To obtain help information about a parameter type a question mark at the parameter position you want
help about. This results in a short guidance text about the parameter concerned.
CHABNR:**005,?
EXP-NUMBER: Expanded number (1...20 digits)
CHABNR:**005,
Help about the first parameter can be obtained by first asking guidance about one OM command and
when the command is repeated again typing in a question mark directly after the colon.

1.5. KEYBOARD COMMANDS

Ctrl-G Start OM session.

Ctrl-K Start coded OM session (for machine applications).
Ctrl-X Abort OM command.
Ctrl-S or NO-SCROLL key: Suspend OM output.
Ctrl-Q or NO-SCROLL key again: Continue OM output.
DEL Delete the last character.
? Help information.

Enter END; or Ctrl-E to finish the OM session.

Enter END! or Ctrl-D to finish the OM session and distribute the license information.

- 13 -
1.6. SYSTEM RESPONSES

The reponse to an OM command can be the following:

• Acceptance
The acceptance response means that the command was correct and is executed. It consists of the
message: EXECUTED.

• Rejection
The rejection response consists of one line containing the error code followed by the corresponding
error message, e.g.:
Error ###: corresponding text
REJECTED
<
Look up the error number in appendix A. ERROR MESSAGES for more information about the error.

• Request
Sometimes a parameter causes non-fatal error. This means that the system does not stop the execution
of the command, although a parameter is wrong. It will respond with: Px:
The user can input the value for parameter x, terminated with a semi-colon (;) and the command will be
executed or abort the command by typing Ctrl-X.

• Congestion
The command is correct but can not be executed due to a temporary lack of resources.
This causes the message:
CONGESTION!
The user does not have to repeat the command, it will be executed when the system has resources
available. Alternatively the user can abort the command using Ctrl-X and try to execute the
command some time later.

1.7. EHWA STRUCTURE

The EHWA has the following format:

<SHELF>[,[<BRD>][,<CRT>][,<B-CHANNEL>]];

This enables the following combinations:

• <SHELF>;
This is the address of the geographical shelf. Within this shelf a number of modules and other non-board
related resources might be located. This address can never be used to identify a single module, even if
the shelf contains only one module.
Example:
EHWA of shelf : 2011;

• <SHELF>,,<CRT>;
This is the address of a module (PM, CM or SM). These are administrative resources and will always have
circuit condition INS.
Note that in order to address the PM controller (PPU or PMC) the EHWA of the controller board must be
used (e.g. 2011, 17).
In order to allow for external addressing of modules in all kinds of hardware configurations, these
resources are given a circuit identification within the geographical shelf.
The modules contained by a shelf are displayed by OM command : DISHLF:<SHELF>;

- 14 -
• <SHELF>,<BRD>;
This is the address of the geographical board AND (conditionally) if there is only one function on that
board, it is the address of the function too.
A board function is a classification of a type of resource. Often the board function is performed by a
number of resources.
Board functions must have an external hardware address. This is necessary to enable the identification
of the function in certain alarm reports. In case the board comprises only one function the address of
the geographical board is the address of the function too.
When more functions are combined on the geographical board an extra parameter is required to
identify the various board functions.
Examples :

Conventional PM board
EHWA of board : 2011,10;
EHWA of PM board function : 2011,10;
EHWA of first PCT on the board : 2011,10,0;
EHWA of the last PCT on the board : 2011,10,7;
EHWA of PMC : UU011,17; (UU = unit)
EHWA of DOC on the PMC board : UU011,17,0; (UU = unit)

• <SHELF>,<BRD>,<CRT>;
This is the address of a board function (in case more functions are combined on the same board) OR it is
the address of one of the resources actually performing the board function.

1.8. IPv6 ASPECTS

There is a growing demand for the usage of IPv6 : in the near future IPv6 will be a "must have".
Support of IPv6 is introduced in SIP@Net 6.1 in such a way that it offers the customer installed base the
possibility to gradually move from IPv4 to IPv6.
This is in particular needed during the transition period from IPv4 to IPv6; allowing customers to keep on
benefiting from their investment in IPv4 "only" SIP terminals and other equipment.

IPv6 is only supported on a SIP@Net Server platform, running on Windows 2008/2012 OS.
Components, closely related to SIP@Net, like the SIP Driver and Media Server are made IPv6 aware.

To be able to control IP-PMs on a SIP@Net Server platform, the PMC-IP is the only hardware board that
supports IPv6.

Keep in mind that IPv6 is not supported on :

- the ISG, PMC-G, PMC-SIC and SIC board

- the ISS (Windows XPE) and ISS-2/ISS-3 (both WES7)
- Windows 2003
- the traditional TDM systems

IPv6 has impact on SIP@Net and all IP related protocols; in particular those protocols that carry IP
addresses, like for example SIP. Also those OM commands that hold IP addresses are modified to
accommodate for IPv6 addressing.
Whether an IPv6 IP address is allowed to be entered in the OM commands depends on the value of system
boundary 448 (IP Version Support) unless stated otherwise.

- 15 -
Possible values of boundary 448 :

- 0 = only IPv4 is supported.

- 1 = only IPv6 is supported.
- 2 = both IPv4 and IPv6 are supported.

System boundary 448 also determines the "start listen ports" for the various IP based protocols for IPv4
only, IPv6 only or both.
Note that this boundary is only valid for "native-IP" systems. All other platforms can never be set to a value
other than 0.

The IP address format in the various OM commands can be as follows :

- IPv4 : a.b.c.d
- IPv6 : a:b:c:d:e:f:g:h (according to RFC 5952)

The following IPv6 address formats are also accepted :

- a:b:c::e:f:g:h
- a:b:c:d:e::g:h
- a:b:c:0:e:f:g:h
- a:b::e:f:g:h
- a:b:0:0:e:f:g:h

When entered in a certain format, the display output might be slightly different.

The following OM commands are effected by IPv6 :

ASCSVR / DICSVR DIIPSE

CHDTSS / DIDTSS DISIED
CHIPPR / DIIPPR DITCPC
CHPCDR / DIPCDR RTFING
CHPVNR / DIPVNR CHIPPD
CHSICI / DISICI EXPING
CHSIPA / DISIPR DICONF

- 16 -
2. ABBREVIATED NUMBERS
These commands are used to assign, erase and display relations between an abbreviated number and an
expanded number. This relation is assigned to a certain analysis group. This means that only users in this
analysis group will be able to use the abbreviated number. If this analysis group number (AG) is omitted,
the action will be performed in the common pool, which is accessible to all extension users.

Change Abbreviated Number 124 # !

CHABNR:<ABBR-NUMBER>[,[<EXP-NUMBER>],[<TRFC>][,<AG>s/r]];
The expanded number <EXP-NUMBER> and the traffic class <TRFC> must always be entered in
combination:
- an expanded number is erased from the common pool by leaving both <EXP-NUMBER> and <TRFC>
empty;
- an expanded number is erased from the group pool by leaving <EXP-NUMBER>, <TRFC> and <AG>
empty;
- an expanded number is changed by entering both <EXP-NUMBER> and <TRFC>.

Display Abbreviated Number 125

DIABNR:[<ABBR-NUMBER>s/r][,<AG>s/r];
If the abbreviated number is not entered then all abbreviated number relations of the given analysis group
are displayed. If AG is omitted, the relations of the common pool will be displayed.
Response:

ABBREVIATED EXPANDED NUMBER TRAFFIC ANALYSIS

NUMBER CLASS GROUP
xxxx xxxxxxxxxxx xx xx

- 17 -
3. ANALYSIS GROUP, COMPATIBILITY VALUE AND SERVICE PROFILE
These OM commands are used to change and display the relation between Analysis Group (AG) and BSP-ID
and/or Compatibility Value (CV) and BSP-ID and to change and display the relation between a BSP-ID and
the service profile.

3.1. ANALYSIS GROUP AND COMPATIBILITY VALUE

The BSP-ID can also be a group DNR. See chapter Trunk Traffic to assign a Compatibility Value to a route. It
is not possible (nor is it needed) to assign an Analysis Group to a route.

Change Analysis Group Number and Compatibility Value of DNR/BSP 207 # !

CHAGCV:<BSP-ID>sr[,[<AG>][,<CV>]];
If either the CV and/or the analysis group parameter is omitted the relation between the BSP-ID and the
omitted parameter(s) is set to the default value. In the number analysis, Analysis Groups can be defined
(using command ASTREE) for the following “DIAL-TYPE”s :

- 0 = Extension dialling
- 1 = Enquiry dialling
- 4 = Alternative destination dialling
- 5 = Follow Me primary dialling
- 8 = Overlay time-out dialling
- 9 = Overlay continue dialling

Display Analysis Group and Compatibility Value of DNR/BSP 208

DIAGCV:<BSP-ID>sr
Response:
DNR-BSPT ANALYSIS- COMPATIBILITY-
GROUP VALUE
xxxxxx xx xx

3.2. SERVICE PROFILE

Change DNR/BSP Service Capabilities 183 # !

CHDNRS:<BSP-ID>sr,<IBSC>,<BSPT>[,<ORDER-IND>];
The BSPT parameter that is assigned should be previously defined by command CRBSPT or by the system. It
should contain the specified IBSC. When only the IBSC is to be changed, then the BSPT must be equal to the
BSPT in the BSP-ID. When the BSPT differs from the BSPT in the BSP-ID then the BSP-ID is changed.
It is not allowed to give BSPT 99 in the BSP-ID.
Note that this command will download the specified terminal which will go to "non operational" for a
moment.

Display DNR/BSP Service Capabilities 210

DIDNRS:<BSP-ID>sr;
Response:
DNR-BSPT IBSC
xxxx xx

- 18 -
- 19 -
4. BACKUP MAINTENANCE
Each unit has a database in the Central Memory (CM), containing all administrative data.
This data should also be available on the backup devices.
The following files, representing the database in the Central Memory, can be made:

- Memory Image Snapshot files (MIS files), containing the CM database in binary format;
- Logical Format files, containing the CM database in subcommand format.

Before making these files, the Backup Maintenance Lock (OM command BMLOCK) must be set to avoid the
changing of the database while it is being copied to the backup device.
When reconfiguring a system common practice is to create retrieve files, adapt these retrieve files and next
reproject the system with these adapted retrieve files. Between the creation of the retrieve files and the
reprojecting of the system with these adapted retrieve files BM lock remains set, to restrict the execution
of data changing OM commands. However, when doing so, also no Desksharing actions can be executed as
long as BM lock is set.
To solve this problem OM lock is to be used. After having made the retrieve files, OM lock is set and next
BM lock is reset. Desksharing actions are now possible and are written to the journal file. When
reprojecting the system with the adapted retrieve files all Desksharing actions, executed in the time period
that OM lock was set, are present after reprojecting the system (after reprojecting the system, the journal-
file is executed).

Set / Clear Backup Maintenance Lock 108

BMLOCK:<OFF-ON>;
Disables (or enables) all data changing OM activities in a system. The lock should be set before making a
MIS file or a Logical Format file, and cleared afterwards.
<BMLOCK:<OFF-ON>;
Give user identification : USER-ID;

or
<BMLOCK:<OFF-ON>,<AWAIT>,<USER-ID>;

- in case parameter <AWAIT> is set to 1, it will wait until another/previous BMLOCK is cleared. Meanwhile
"Congestion" is displayed.
- in case parameter <AWAIT> is set to 0 and another/previous BMLOCK was set “BM or OM lock already
set by" is displayed.

Set / Clear Operational Maintenance Lock 511

OMLOCK:<OFF-ON>;
This command can be used to temporary disable all OM actions (executed from an OM device) which
change the configuration data. However OM actions initiated from an extension (e.g. when desksharing is
executed) remain possible : the changes are written to the journal file.

- when BM lock is set, OM lock is of no importance (don't care).

BM lock has a higher priority than OM lock
- when OM lock is set, BM lock can only be reset !
- when OM lock is not set, BM lock can be set and reset.
<OMLOCK:<OFF-ON>;
Give user identification:<USER-ID>;

- 20 -
Change to New Empty Journal File 109
CHJOUR:<NETWORK-SIN>;
Before using this command the BM lock should be set first. This command deletes all versions of the journal
file and makes a new empty journal file with the input SIN (Snapshot Identification Number).
The SIN should be the same as the MIS files present. Check the SIN of the MIS files by typing:

DIRECT:LBUxx:LMxx01.POM./,U;

WARNING: THIS COMMAND DELETES INFORMATION NOT YET PRESENT IN THE LATEST MIS FILE(S).
USE GEBUMI, UNLESS THIS IS WHAT YOU REALLY WANT.

Generate Backup in Logical Format 105

RTRIEV:[<RETRIEVE-ACTION>][,[<UNIT>]][,<RETRIEVE-OPTIONS>];
WARNING: Do not use SWJUPD when making a retrieve.
Before using this command the BM lock should be set first. If the unit number is omitted, the Logical
Format files are made in all units of the system. The Logical Format files are called PRxx.POM (PE data) and
ORxx.POM (LL data).
Parameter RETRIEVE-OPTIONS can be used to indicate whether dynamic data and/or name-number
relations should also be included in the retrieve files.
In case of dynamic data, the following data is also retrieved :

- Follow-me destination (for extensions and groups)

- Follow-me prepared (for extensions and groups)
- Fixed Follow-me activation
- Set/Reset Call Forwarding on Busy Extension
- Set/Reset Don't disturb
- Night Extension absent/presence
- Executive absent/presence
- Secretary absent/presence
- Set Executive present by Secretary
- Group member absent/presence
- Set/Reset DECT WAN Mobility
- Set upgraded Traffic Class to night for all BSPs (system option NESYSOP085)

Dynamic data (as listed above) can also be saved in the journal file, depending on system option
LOSYSOP190 “Enable journaling of dynamic data“.
It is advised to set this option to 'YES' on a SIP@Net Server and ISS/ISS-2/ISS-3 system and to 'NO' (default)
on an iS3000 CPU3000/CCS system.

Generate Backup in Memory Image Snapshot 104

GEBUMI:[<UNIT>];
WARNING: DO NOT USE THIS COMMAND WHEN TRUNKS ARE IN CIRCUIT CONDITION OUT.

Before using this command the BM lock should be set. If the unit number is omitted, the MIS file (Memory
Image Snapshot) is made in all units of the system (systemwide) and a new empty journal file is introduced.
On completion of the command the advice is given to make a firecopy (if a MIS file is made in all units). See
also section 4.2. MAKING A FIRE COPY.
After the MIS files are made, old versions may be deleted to make space on the local backup using the
PUBUMI command. Each MIS file is called LMxx01.POM (xx=unit number) and is present on the Local
Backup.

- 21 -
Generate Backup Files 609
GEBUFI:;
Before using this command the BM lock should be set.
The GEBUFI command executes the following actions as an automatic operation :

1. Make a complete retrieve : network, local and dynamic data. The result will be a PR and OR file.
2. Rename the retrieve files PR and OR back to PE and LL.
3. Generate a MIS file (only on the iS3000 TDM platform, not on the SIP@Net Server).
4. Generate a new empty journal file.

The versioning mechanism takes care that always the last projecting files are used on a restart, and that
there are maximum of 8 PE/LL files.

See also section 4.1. AUTOMATIC GENERATION OF BACK-UP FILES.

Purge the MIS-file on the Backup Device 479

PUBUMI:[<UNIT>];
PUBUMI purges MIS files at the backup device. If no unit is specified, MIS files are purged in the unit the
command is executed from. If only one MIS file is present on the backup device, no MIS file will be deleted.
Response:
UNIT 2 : MIS-file version a DELETED !
UNIT 2 : MIS-file version b DELETED !
UNIT 14: MIS-file version c DELETED !

where a, b and c indicate the file generations.

Switch Journal Updating 106

SWJUPD:<OFF-ON>;
After starting an OM session the journal updating is on, commands are written to the journal file. For
special purposes (test during installation) it can be switched off.

WARNING: SWITCHING THE JOURNAL UPDATING OFF LEADS TO GAPS IN THE JOURNAL FILE. ALSO THE
BM LOCK WILL BE OVERRULED FOR THE CONCERNING OM TERMINAL.

Update Unit from Journal 107

UPDATE:[<UNIT>][,<SERVER-NUMBER>];
On the iS3000 platform
When executing this command on the iS3000 platform parameter <SERVER-NUMBER> is not relevant.
After an operational restart normally the journal file is executed. When an operational restart occurs during
the execution of an OM command, the possibility exists that the operational restart occurred due to an
erreonous subcommand. Because this subcommand is also present on the journal file the unit would keep
on restarting. This would be a deadlock situation.

To prevent this, the journal file is not executed when the unit lock is set (this happens automatically during
the execution of an OM command). If the journal file is not executed this is signalled to the user. Two
possibilities exist:

- 22 -
- The operational restart was not the result of a wrong subcommand. Give the UPDATE command to
execute the journal file.
- The operational restart was the result of a wrong subcommand. After the UPDATE command another
operational restart occurs. Report this situation, as it is due to a software error.

On the SIP@Net Server platform

When executing this command on the SIP@Net server platform parameter <UNIT> is not relevant.
Parameter <SERVER-NUMBER> is only relevant on the SIP@Net Server platform in a Dual Server or
Server Cluster configuration. In these configurations the command should be executed on the Active Server
or on the Master Server.

When SERVER-NUMBER = 0 … 22 : (update by file copy)

The specified Standby or Slave Server is updated by copying the PE & LL and journal file to the specified
Standby or Slave Server. When SERVER-NUMBER = 0 all Slave Servers are updated.

When SERVER-NUMBER is omitted: (update by sending backlog)

The UPDATE command compares the signature of the journal files in each Standby or Slave Server with the
signature of the journal file in the Active Server/Master Server. When signatures are equal, a check is
performed whether there is a backlog of journal file items. In the (exceptional) case that there is a backlog,
this backlog of journal file items is sent to the Standby or Slave Server in question.

4.1. AUTOMATIC GENERATION OF BACK-UP FILES

The journal file will grow over time, and with journaling dynamic data, it will grow faster and become
significantly larger. To reduce the risk of a long start-up time due to a large journal file, one is advised to
regularly execute OM command GEBUFI, which retrieves the projecting and clears the journal file. OM
command AUBUFI 'Automatic GEBUFI' makes this easier. Keep in mind that subjobs submitted from
projecting and/or journal file are ignored when the date-and-time is in the past, or when the system time is
not set. This is the case on CCS platform and therefore this function is not supported for this platform.

Automatic GEBUFI 610

AUBUFI: [<COMMAND-FILE>],[<LOG-FILE>],[<DATE>],[<TIME>],[<UNIT>],
[<REPEAT-PERIOD>];
OM command AUBUFI “Automatic GEBUFI” creates a command-file containing a GEBUFI and a SUBJOB
command and submits it at the given DATE and TIME in the given UNIT.
The job is repeated after REPEAT-PERIOD number of days (1 ... 9999).
For the <COMMAND-FILE> only '/' (latest) may be used for the generation.

- in case <COMMAND-FILE> is left empty, the default "LBUxx:AUBUFI.COM./" is used.

- in case <LOG-FILE> is left empty, the default "LBUxx:AUBUFI.LOG./" is used.
- in case <REPEAT-PERIOD> is left empty, the job is repeated daily.

This command is only accepted if protection levels (NARD) of the OM terminal are at least set to 1131.
It is advised to have system option LOSYSOP 190 “Enable Journalling of Dynamic Data“ set to 'YES' on a
SIP@Net Server and ISS/ISS-2/ISS-3 system and to 'NO' (default) on an iS3000 CPU3000/CCS system. When
set to ‘YES’ check that system boundary NEBOUND440 "Dynamic Data Backup Buffer Size" is not set to 0.

- 23 -
Example
On a single unit system (unit1), the following command creates the command file LBU01:AUBUFI.COM on
the LBU01 and submits this as batch-job scheduled for tomorrow 1:00 AM, to be repeated every 7 days:
<AUBUFI:,,+1,01:00,,7;

The command file AUBUFI.COM on the LBU is as follows :

<BMLOCK:1,1,AUBUFI;
<GEBUFI:;
<BMLOCK:0,1,AUBUFI;
<SUBJOB:LBU01:AUBUFI.COM./,LBU01:AUBUFI.LOG./,+7,01:00,1;
<END;

In case no regularly back up files are made (manually, OM command AUBUFI or using another batch job)
the journal file may grow to an unacceptable size, which may cause problems :

- A journal file is delimited to 999,000 items. Journaling will stop after reaching this number of items.
- A very large journal file takes quite some time to load after cold start.

In case the maximum size of the Journal file is reached, Alarm Code/Qualifier 68/7 "Journal file is full" is
generated. Boundary 439 "Journal Sequence Number Threshold" defines the number of subcommands that
can be written to the journal after which Alarm Code/Qualifier 68/6 "Journal file is large" is generated.
To prevent reaching this situation it is now possible to automatically generate a GEBUFI. The following two
system boundaries are introduced which define the parameters for "automatic GEBUFI", together with the
already existing boundary 439 :

- System boundary 457 specifies the time of the day, a backup must be executed automatically in the
background. It is advised to set this time at a quiet moment, for example at midnight.
When this boundary 457 has not been specified (value 65535) or when it is out of range (hours >23 or
minutes >59), then the time 03:42 is taken.
When this boundary 457 is changed in a running system, the change is effectuated after midnight or is
effectuated immediately after setting date and time.

- System boundary 458 specifies the percentage the "journal file is almost large" and an automatic back
up is scheduled. The "journal file is almost large" threshold equals : NEBOUND439 x
(NEBOUND458)/100).
When this boundary 458 has not been specified (value 65535) or when it is out of range, then the
percentage 80% is taken.

Boundary
What is automatically done
439 457 458
Run GEBUFI at 02:15 hrs when the number of journal file items is more
50 215 10
than 10% from boundary 439, being equivalent to 5000 items.
Always run GEBUFI at 20:30 hrs, no matter what the number of journal
50 2030 0
file items is at that moment.
All 3 boundaries on the default values :
50 65535 65535 Run GEBUFI at 3:42 hrs when the number of journal file items is more
than 80%, being equivalent to 40,000 items.

- 24 -
4.2. MAKING A FIRE COPY

For safety reasons, it is advised to copy the customer’s specific related files files (PE, LL, MIS, journal and
license file) from the LBU to another device, for example an external memory device, another PC or your
SMPC.

Note: It is advised to keep the two latest versions of the PE, LL, MIS and journal files as fire copies.

On a CCS system
The LBU of the CCS system is on the BIM PC.

1. On the BIM command line type in "dirlbu" to find out which disk (disk 1 or 2) is the LBU.
[C:/BIM/work] dirlbu

LBU directory: 'C:/BIM/run/disk1/' (this is the UNIX notation, not Windows)

F14100V1.903 FA0000V1.107 journlv3.pom lm0101v2.pom

F22031v1.302 configv1.pom le01v1.pom pe01v8.pom
F98610V1.230 lics01v1.lic ll01v8.pom plv1.pom

2. Now navigate to the directory C:\BIM\run\disk1.

3. Select the PE, LL, MIS, journal and license files.
4. Copy those files to a directory on another device, for example an external memory device.
5. Label the directory with the customer’s name, the date/time.
6. Store the memory device in a safe place.

On a CPU3000 system
The LBU of the CPU3000 systems is on the CPU3000 itself.
A fire copy of the customer’s specific related files are created on the SMPC as follows:

1. Select the specific customer directory.

2. Use the "Disk Emulator" program to copy the files from the LBU to the specific customer directory of the
SMPC.
3. Execute the command CPYFIL to copy the files from the LBU to PC, for example :

CPYFIL:LBU01:PE01.POM,PC01:;
Repeat this command for the LL, MIS, journal and license file.
Note that instead of using the "Disk Emulator" program, it is possible to use a FTP program.

4. Copy the files from the SMPC to a directory on another device, for example an external memory device.
5. Label the directory with the customer’s name, the date/time.
6. Store the memory device in a safe place.

On a SIP@Net Server platform

Simply use the Windows way to navigate to the LBU of the SIP@Net server.

1. Copy the files from the LBU to another device, for example an external memory device.
2. Label the directory with the customer’s name, the date/time.
3. Store the memory device in a safe place.

- 25 -
4.3. UNIT COMPATIBILITY

These commands are used when a non-simultaneous upgrade must be made in a iSNet Metropolitan Area
Network (iSNet MAN) or also called “Fully Integrated Network” (FIN).

In this situation the network will consist of units with the old software package (not yet upgraded) and
units with the new software package. This means that the total network consists of two (incompatible)
smaller networks. The network compatibility function ensures that calls between incompatible networks
are still possible but without facilities.

Change the Network Compatibility 403

CHCOMP:<INC-OR-COM>;

Display Unit Compatibility 402

DICOMP:<UNIT-1>[,<UNIT-2>];
The displayed status is the status of UNIT-2 as seen by UNIT-1.
Response:
UNIT COMPATIBILITY
xx xxx

The compatibility can be one of the following:

- Compatible;
- Incompatible;
- Unknown

- 26 -
5. BOUNDARIES, OPTIONS AND TIMERS
A number of 'safe boundaries', options and timers can be changed using OM commands :

- CHBOUN : Only safe boundaries can be changed.

Unsafe system boundaries (see Second Line Maintenance Manual) must be changed in
the PE file and then together with the LL file loaded back into the system by STPROJ.
- CHOPTI : All system options can be changed using OM command CHOPTI, except options 119 and
156 : these have to be changed in the PE file.
- CHTIME : All system timers can be changed

Refer to the Second Line Maintenance Manual for the complete list of system boundaries, options and
timers.

When the above mentioned commands are executed, first a warning is given and the user is asked for a
confirmation (this is done because it is not checked if the changes damage the system). On negative reply,
the execution of the command is aborted. Before the command ends, a message is given that a MIS-file
should be made to make the change(s) permanent.
The actual values of system boundaries, options and timers can be displayed by OM command DIMDAT.
Note that unsafe boundaries can also be changed using 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.

Change Boundary Value 507 # !

CHBOUN:<BOUNDARY-INDEX>,<BOUNDARY-VALUE>[,<UNIT>];
BOUNDARY-INDEX : The boundary to be modified.
BOUNDARY-VALUE : The new value of this boundary.
UNIT : Unit number (1 ... 14) in which the boundary should be modified.
If omitted, the action is executed network wide.

In case of an unsafe boundary the system response is: " Unsafe boundary, change not allowed".
It is advised to use the MEMCAL tool to change unsafe boundaries, using the following procedure:

1. Execute OM command GEBUMI to create a MIS file.

2. Execute OM command RTRIEV to create the PR/OR files.
3. Convert the PR file to PC format.
4. Run the MEMCAL tool to change the required unsafe boundaries in the PR file.
5. Safe the file to filename PEuu.TXT.
6. Convert the PEuu.TXT to iS3000 format.
7. Rename ORuuV1.POM to LLuuV1.POM.
8. Load both the PE and LL file to the LBU.
9. Execute OM command STPROJ to reproject the system.

Change Timer Value 497 # !

CHTIME:<TIMER-INDEX>,<TIMER-UNIT>,<TIMER-VALUE>[,<UNIT>];
TIMER-INDEX : The timer to be modified.
TIMER-UNIT : 0 = seconds, 1 = minutes.
TIMER-VALUE The new value of this timer (0 ... 16383).
UNIT : Unit number (1 ... 14) in which the timer should be modified.
If omitted, the action is executed network wide.

- 27 -
Change Option Value 498 # !
CHOPTI:<OPTION-INDEX>,<OPTION-VALUE>[<UNIT>];
OPTION-INDEX : The option to be modified.
OPTION-VALUE : The new value of this option : 0 = False 1 = True.
UNIT : Unit number (1 ... 14) in which the option should be modified.
If omitted, the action is executed network wide.

In case one of the unsafe options (119 and 156) is changed using CHOPTI, the system response "This option
cannot be changed using CHOPTI" (or "Restriction on action") is given.

Display Manager Data 221

DIMDAT:<MANAGER-TYPE>[,[<MANAGER-INDEX>s/r][<UNIT>]];
This command can show the parameter value(s) of either boundaries, options or timers.
The Second Line Maintenance manual gives detailed information of the items mentioned above.
If the index is omitted all data of the specified manager is displayed.
Response:
UNIT MANAGER-TYPE MANAGER-INDEX VALUE (TIME-UNIT)
xx xx xx xx xx

- 28 -
6. CALL FORWARDING
These commands are used to assign, erase and display the call forwarding relations between an originator
DNR (or BSP-ID) and a destination number. There are various types of call forwarding : see overview below.
The full format of OM command CHCALF is as follows :

CHCALF: <CF-TYPE>,[<ORIG-BSP-ID>sr][[,[<DEST-NUMBER>]][,[<UNIT>]]
[,[<CFDA-TIME>][,<CALL-ORIG-TYPE>]]];

Depending on the CF-TYPE, either parameter ORIG-BSP-ID or UNIT must be specified : see below.
Parameter <UNIT> might be omitted in a single unit system.

CF-TYPE ORIG-BSP-ID is UNIT

0 = CF on don't answer extension extension BSP-ID ---
1 = CF on busy extension extension BSP-ID ---
2 = CF on absent group member group DNR (all groups) ---
3 = CF on empty group group DNR (all groups) ---
4 = CF on group overflow ACD group DNR ---
5 = CF on group in night service ACD group DNR ---
6 = CF on not existing DNR --- UNIT
7 = CF on out of order extension --- UNIT
8 = CF on not reachable extension extension BSP-ID ---
9 = CF on SMA no valid CLI --- UNIT
10 = CF on SMA enquiry triggered --- UNIT
11 = CF on don't answer group group DNR (non-ACD) ---
12 = CF on busy group group DNR (non-ACD & MRG) ---

The destination number (DEST-NUMBER) can be:

- a group or extension DNR

- a general or individual operator DNR
- a trunk access code and external number
- a DPNSS/QSIG number.

Layout of CHCALF per CF-Type

CHCALF: 0,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>[,,[<CFDA-TIME>][,[<CALL-ORIG-TYPE>]]];
CHCALF: 1,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];
CHCALF: 2,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];
CHCALF: 3,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];
CHCALF: 4,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];
CHCALF: 5,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];
CHCALF: 6,,[<DEST-NUMBER>],<UNIT>[,,[<CALL-ORIG-TYPE>]];
CHCALF: 7,,[<DEST-NUMBER>],<UNIT>[,,[<CALL-ORIG-TYPE>]];
CHCALF: 8,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];
CHCALF: 9,,[<DEST-NUMBER>],<UNIT>[,,[<CALL-ORIG-TYPE>]];
CHCALF:10,,[<DEST-NUMBER>],<UNIT>[,,[<CALL-ORIG-TYPE>]];
CHCALF:11,<ORIG-BSP-ID>s/r[,[<DEST-NUMBER>],,[<CFDA-TIME>][,[<CALL-ORIG-TYPE>]]];
CHCALF:12,<ORIG-BSP-ID>s/r[,<DEST-NUMBER>][,,,[<CALL-ORIG-TYPE>]];

- 29 -
Remark for CF-Type 11
Implicitly, in case the <DEST-NUMBER> is empty the call forwarding destination is the own group.

Change Call Forwarding Relation 127 # !

CHCALF: <CF-TYPE>,[<ORIG-BSP-ID>s/r][[,[<DEST-NUMBER>]][,[<UNIT>]]
[,[<CFDA-TIME>][,<CALL-ORIG-TYPE>]]];
If parameter <DEST-NUMBER> is omitted, the call forwarding relation of the originator will be erased,
except for CF-TYPE 11. If, for CF-TYPE 11, parameters <DEST-NUMBER> and <CFDA-TIME> are
omitted, the call forwarding relation of the originator will be erased.

Display Call Forwarding Relations 128

DICALF:[<BSP-ID>s/r][,<UNIT>];
Response:
ORIGINATOR CF-TYPE CF-DESTINATION CFDA-TIME ORIG-TYPE
ext-dnr xxxx xxxx xx x
grp-dnr xxxx xxxx xx x

For the CF-types 0 ... 5, 8, 11 and 12 the command layout is:

DICALF:[<BSP-ID>s/r;

The <UNIT> parameter is only applied to display the CF-types 6, 7, 9 and 10. It may only be omitted in a
single unit system. This makes the command layout:

DICALF:[,<UNIT>];

- 30 -
7. CAMP ON BUSY
The OM commands for Camp On Busy (COB) are used to assign/change and display the maximum length of
the COB queue for a DNR (or BSP-ID). Three COB-QUEUE-TYPES are distinguished:

- No-COB-Queue;
- Short-COB-Queue;
- Long-COB-Queue.

The type of queue is specified by a number in the parameter field COB-QUEUE-TYPE.

Change COB Queue Type Relation 372 # !

CHCOBD:<BSP-ID>s/r[,<COB-QUEUE-TYPE>];
If the parameter COB-QUEUE-TYPE is omitted, the ‘Short-COB-Queue' type is chosen as default.

Display COB Queue Type Relation 373

DICOBD:<BSP-ID>s/r;
Response:
DNR-BSPT COB-QUEUE -TYPE
xxxx xxxx-cob-queue
xxxx xxxx-cob-queue
xxxx xxxx-cob-queue
.. .. .. ..

- 31 -
8. CCIS OVER IP
In order to enhance call handling interworking between the iS3000 and the 2000 IPS platforms, PBC has
implemented the Common Channel Inter-office Signalling (CCIS) protocol in the iS3000. With this NEC-
proprietary protocol customers are able to make calls between any iS3000 user and any 2000 IPS user. CCIS
supports a wide range of features (including Call Back, Enquiry, Transfer, Diversions etc.) and is able to
operate over TDM (primary rate) as well as over IP.

Change Point-Code Identity 341 # !

CHPCID:<SHELF>,<BRD>[,<POINT-CODE>];
This command is used to add (or change) a point-code to a unit.
When parameter <POINT-CODE> is omitted, it is removed from the unit.

Display Point-Code Identity 344

DIPCID:[<UNIT>];
This command is used to display the Point-Code of one unit.
When parameter <UNIT> is omitted, the Point-Code of all units is displayed.

Change Point Code Data Relation 304 # !

CHPCDR: <POINT-CODE>[,[<IP-ADDRESS>],[<TRUNK-CODE>],[<ROUTE>],
[<CODEC-LIST>][,<UNIT>]];
This command is used to change the Point-Code Data. When only <POINT-CODE> is given, the relation will
be deleted.
The command asks for additional parameters :

First alternative DPC : [<POINT-CODE>];

Second alternative DPC : [<POINT-CODE>];
Third alternative DPC : [<POINT-CODE>];
Send Change Day Night message allowed : (0=no, 1=yes);

POINT-CODE : is the Point-Code of the CCIS destination.

IP-ADDRESS : is the address of the CCIS destination.
TRUNK-CODE : is the Trunk Access Code of the media route (max. 6 digits).
ROUTE : is the (virtual) route that is used for incoming calls (0 ... 254).
CODEC-LIST : is a number (1 ... 17) of the supported CODECs.

Display Point Code Data Relation 338

DIPCDR:[<POINT-CODE>s/r][,<PC-REPORT-TYPE>][,<UNIT>];
This command is used to display the Point-Code Data.

<DIPCDR:,1;
UNIT DCP OPEN IP-ADDRESS
2 41 No 192.168.1.5
2 52 Yes 192.168.1.100
2 63 No 192.168.1.12

<DIPCDR:,2;
UNIT DCP OPEN TAC ROUTE CODEC ALTERNATIVE-DPC’S D/N-all
2 41 No 85 85 2 63 52 - No
2 52 Yes 85 85 2 41 63 - No
2 63 No 85 85 2 52 41 - No

- 32 -
9. COMMAND FILE EXECUTION
A command file gives the possibility to execute a series of commands at a pre-determined time, e.g. at
night, when there is little traffic. It is also used when a series of commands must be executed regularly, e.g.
once a week. This series of commands is contained in a command file, also called a job. All OM commands
may be used in a command file.
A command file can be made in two ways:
- It can be made on a PC and transferred to the unit;
- It can be made on a unit with the CREFIL command.

A command file should look like an OM session, i.e. every command should start with the ready indication
(<). The session should be terminated with the command <END;.

A line in a command file can have 3 meanings:

- It contains an OM command and starts with the ready indication (<), e.g. <DIDEST:0;
- It is a comment line and starts with a backslash and an asterisk (\*). It ends with an asterisk and a
backslash (*\), e.g. \* This is a comment line *\
This is only possible on a PC. These comment lines will disappear after Converting to iS3000 layout.
- It contains a password or an additional parameter as a response to question from the system, e.g.
PASSWORD;

An example of a complete command file is:

<CRGRPA:1000,57
1100,1,0;
1101,1,1;
;
<END;
EXIT;

9.1. NORMAL COMMAND FILES

Cancel a Batch Job 284

CANJOB:<JOB>[,<UNIT>];
The indicated job is cancelled completely. This can be a job that is not yet executed or an active job.

Display Command File Execution status 283

DISJOB:[<JOB>][,<UNIT>];
If the job number is omitted all jobs in the given unit are displayed.
Response:
Unit Job Status Date Day Time Commandfile spec Log file spec
xx xx xxxx xxxx-xx-xx +x+ xx:xx xxx:xxxxx.xxx.x xxx:xxxx.xxx.x

The status of a job can be one of the following :

- HOLD : Job was not active and is suspended.
- AFTER : Job is waiting for time out.
- ACTIVE : Job is active.
- SUSPEND : Job was active and is suspended.
- ERROR : Error accessing the command file or opening log file.
- HOLD-ACTIVE : Timer expired during hold state.

- 33 -
Resume Command File Execution 286
RESJOB:<JOB>[,<UNIT>];
This command is used to resume a job that has been suspended.

Submit Command File 282

SUBJOB:[<COMMAND-FILE>],[<LOG-FILE>],[<DATE>],[<TIME>],[<UNIT>];
If no command file is specified, the default is used: LBUxx:SUBMIT.COM./

If no log file is specified, the file name of the command file is used, with the extension LOG, e.g.
LBUxx:SUBMIT.LOG./

If the date and/or time are not specified the current date and time are used, this means the command file
starts immediately. Recommended is to spread the subjobs with an interval of three minutes.
This command will only be accepted if protection levels of the OM terminal are at least NARD = 1131. The
authority class and protection levels during the execution of the command file are the session authority
class and protection levels of the terminal on which the job is submitted.

If a command file is submitted it is assigned a job number by the system. From this point on the system
refers to the job number of the submitted command file.

Suspend Command File Execution 285

SUSJOB:<JOB>[,<UNIT>];
This command is used to suspend the execution of a job. It can be resumed later.

9.2. AUTHORITY OVERRULING COMMAND FILES

Submit Authority Overruling Command File 288

EXSJOB:[<COMMAND-FILE>],[<LOG-FILE>],[<DATE>],[<TIME>],[<UNIT>];
This command is used to submit a special command file. When the special command file is executed the
authority class is set to unrestricted.
If no command file is specified, the default is used: LBUxx:SUBMIT.COM./
This command will only be accepted if protection levels of the OM terminal are at least NARD = 1131.

Change Command File into Authority Overruling Command File 287

CHSJOB:[<COMMAND-FILE>];
This command is used to change a normal command file into a special command file.

- 34 -
10. DATA FUNCTIONS
These commands are used to maintain and assign Compatibility Values (CVs), Convertors and selective
answering DNRs (SAQC). CVs and convertors are used to determine whether parties may be connected to
each other.

10.1. COMPATIBILITY VALUES AND CONVERTORS

CVs are used for voice parties and data parties:

- With voice parties CVs are used to inhibit a conversation, e.g. in a hotel the kitchen is assigned a
different CV as the guests, to make it impossible for the guests to dial the kitchen.
- With data parties CVs are used to check if it is possible for parties to understand each other, e.g. are the
baud rates the same?

If two parties have different CVs the following connection allowances are possible:
- the connection is allowed
- the connection is not allowed
- the connection is only allowed via a convertor
- the connection is not possible.

When CVs must be created and assigned use the following procedure:
- For both voice and data:
- Use CRCVAL to create CVs;
- Fill in the connection allowance matrix with CHCVCA
- Assign CVs to DNRs with CHAGCV (see chapter 3. ANALYSIS GROUP, COMPATIBILITY VALUE AND
SERVICE PROFILE)
- For data only, when convertors are necessary:
- Use CRCTYP to create a convertor type
- Use ASCONV to link this convertor to an EHWA
- Use ASCVCT to link CVs to the convertor
- Use CHCVCA to fill this in in the connection allowance table.

10.1.1. Compatibility Values

Change CV 130 # !
CHCVAL: <CV>,<VOICE/DATA>[,<V-24 CIRCUITS>,<SPEED+MODE>,<MISCELLANEOUS>
[,<GUARD-1+GUARD-2>]];
If in the VOICE/DATA parameter V is filled in, the rest of the parameters should be omitted. The old data is
overwritten.

Change CV-Pair Connection Allowance Relation 135 # !

CHCVCA:<CV-A>s/r,<CV-B>s/r,<CON-ALLOWANCE>;
This command assigns the connection allowance from CV-A to CV-B.

Create CV 129 # !
CRCVAL: <CV>,<VOICE/DATA>[,<V-24 CIRCUITS>,<SPEED+MODE>,<MISCELLANEOUS>
[,<GUARD-1+GUARD-2>]];
If in the VOICE/DATA parameter V is filled in, the rest of the parameters should be omitted.

- 35 -
Display CV 132
DICVAL:[<CV>s/r];
If no CV is specified all CVs are displayed.
Response:
CV V/D V24-CIRCUITS/SPEED MODE MISCELLANEOUS GUARD-1 GUARD-2
OPTION [BAUD] [MIN] [SEC]

Display CV Pair-Connection Allowance 136

DICVCA:[<CV-A>s/r],<CON-ALLOWANCE>s/r;
If the CV is omitted all relation with the specified connection allowance are displayed.
Response:
CV-A CV-B CONNECTION-ALLOWANCE
xx xx xx

Erase CV 131 # !
ERCVAL:<CV>;
All relations with the specified CV are also removed.

10.1.2. Convertors

Assign Convertor to EHWA 143 #!

ASCONV:<SHELF>,<BRD>s/r,<CRT>s/r,<CONVERTER-TYPE>;

Assign CV Pair Convertor Type Relation 140 # !

ASCVCT:<CV-A>s/r,<CV-B>s/r,<CONVERTER-TYPE>;
This command can only be used if convertor type is created first. Use the CRCTYP command to do this.

Create Convertor Type 137 # !

CRCTYP:<CONVERTER-TYPE>s/r;

Display Convertor EHWA 142

DICONV:[<CONVERTER-TYPE>s/r][,<UNIT>s/r];
If no unit number is specified, the data for all units will be displayed.
Response:
SHELF BRD CRT CONVERTOR-TYPE
xx xx xx

Display Convertor Type 139

DICTYP:;
Response:
CONVERTOR TYPES
CREATED

- 36 -
Display CV Pair Convertor Type 141
DICVCT:[<CONVERTER-TYPE>s/r];
Response:
CV-A CV-B CONVERTOR TYPE

Erase Convertor EHWA 144 # !

ERCONV:<SHELF>,<BRD>s/r,<CRT>s/r;
The relation is only removed if the service condition of the circuit is "not installed".

Erase Convertor Type 138 # !

ERCTYP:<CONVERTER-TYPE>s/r;
A convertor type can only be removed if no MLU EHWA convertor relation with a convertor of the specified
type exists in the system.

10.2. REMARKS ABOUT DOWNLOADING

It is possible to download a SOPHO-SET and LAM with data. This data can be:
- Data Terminal Equipment (DTE) data. This comprises V.24 circuit data, speed etc.
- Function key data. This data is needed to program the function keys.

• DTE Data
DTE data is downloaded when:
- The checksums of the SOPHO-SET or LAM is incorrect. SOPHO-SET or LAM without power for a long
time.
- When a new compatibility value is assigned to the BSP-ID (or DNR) of the data ports of SOPHO-SET or
LAM.
- When a user asks for new data with the download data request. See the relevant SOPHO-SET
documentation.
- When the download command is issued on the OM terminal. See chapter Download.

• Function Key Data

Function key data is downloaded to extensions with FCM 12:
- The checksums of the SOPHO-SET is incorrect. SOPHO-SET without power for a long time.
- When a user asks for new data with the download data request.
- When the download command is issued on the OM terminal. See chapter Download.

A function key can have one of four priorities:

- 0 = No data assigned to the function key;
- 1 = Data assigned to function key by ISPBX low priority;
- 2 = Data assigned to function key by user;
- 3 = Data assigned to function key by ISPBX high priority.

When downloading function key data, data with a higher priority overwrites data with a lower priority.
Data on function keys, defined by the user, not used by the ISPBX stay intact during downloading. For
the user it is possible to overwrite function key data downloaded by ISPBX if this data has priority 1. It is
not possible for the user tho overwrite data which has priority 3.
See chapter Function Keys and Menus for more information about defining function key data.

- 37 -
10.3. SELECTIVE ANSWERING DNR

The 'selective answering DNR' facility has been designed for special projects only.
It allows to selectively answer a call from the waiting queue. This queue is displayed on a screen.

Assign selective answering DNR 428

ASSADN:<DNR>s/r;

Display selective answering DNR 430

DISADN:<UNIT>s/r;

Erase selective answering DNR 429

ERSADN:<DNR>s/r;

- 38 -
11. DATE, TIME AND EXCHANGE-ID
Display Date and Time 112
DIDATI:;
Response:
YEAR-MONTH-DAY +DAY-OF-WEEK+ HOURS:MINUTES

When the time is never set, "0000-01-01 +1+ 00:00" is displayed.

Set Date and Time 111

SEDATI:<YEAR>,<MONTH>,<DAY>,<DAY-OF-WEEK>,<HOURS>,<MINUTES>;
If the date does not match the Gregorian calender the command is aborted and the date and time are not
changed. The CPU3000 system has a real time clock. When this system becomes operational, the correct
date and time are already set.

Note: The date and time on feature phones are updated automatically every 24 hours and after the
execution of SEDATI.

The ISPBX date and time can be synchronized (set) to the date and time provided by PSTN service provider
via ISDN trunks. The functionality allows automatic switch over to daylight-savings-time. iS3000 date/time
is synchronised to the ISDN date/time indicated by the first incoming or outgoing ISDN trunk call at regular
intervals of 15 minutes if the time difference is 10 seconds or more (assuming that the PSTN sends the
seconds in the ISDN date/time information element). To implement this functionality, NESYSOP 132
(Synchronise to ISDN date/time) must be TRUE and bundle option 'ISDN date/time synchronisation' in the
OM command CHBNDC must be set.

When ISDN date/time synchronization is active, there are two (independent) sources from which the
iS3000 date/time can be set :
- date/time can be synchronised to ISDN date/time without executing OM command SEDATI first :
'Monday' will be regarded as first 'day-of-the-week' (digit '1').
- when date/time is set, it can be changed either due to an ISDN date/time update or by means of
executing OM command SEDATI.

Note that on the SIP@Net Server and ISS/ISS-2/ISS-3 platform, the date &time can not be set using OM
command SEDATI. It has to be set using the “Date and Time Properties” of the Windows server.

Display Exchange Identity (and Loaded Overlay Sets) 113

DIEXID : [<UNIT>s/r][,<REPORT-FORM>];
Response for an 85x package (if parameter <REPORT-FORM> is omitted) and in case license 73 (Start
Upgrade Period) is present and license 78 (SWA Upgrade Allowance) is not present then DIEXID shows the
upgrade period (start quarter and end quarter) and SOFTWARE-ASSURANCE has value No. DAYS-LEFT shows the
number of days after which the current upgrade license (license 73) expires.
See example below in which license 73 is 2013Q1.

UNIT CM PACKAGE -ID PATCH COUNTRY EXCHANGE# ADMIN# USER# 12NC

1 1 9861.00 0 0670 0042 3031 1302 3522-274-40690

PACK-RELEASE UPGRADE PERIOD DAYS-LEFT SOFTWARE-ASSURANCE

START END
2013Q3 2015Q1 2016Q1 273 No

- 39 -
In case license 73 (Start Upgrade Period) is present and license 78 (SWA Upgrade Allowance) is also present
then DIEXID shows only the quarter of the end of the upgrade period and <SOFTWARE-ASSURANCE> has
value Yes. <DAYS-LEFT> is empty.
See example below in which license 73 is 2013Q1.

PACK-RELEASE UPGRADE PERIOD DAYS-LEFT SOFTWARE-ASSURANCE

START END
2015Q3 - 2016Q1 - Yes

In case the PACKAGE-ID shows y861.xx, the meaning is as follows :

y : indicates the platform SIP@Net is running on :

- 6 means CPU3000 without an Accelerator Module (AM)
- 9 means CCS systems and CPU3000 with an AM
- 8 means SIP@Net Server and ISS/ISS-2/ISS-3

861 : indicates the major release, for example 861, for SIP@Net 6.1

xx : indicates the minor release

- 00 for the initial major release
- 01 for the first minor release
- 02 for the second minor release

P : indicates a patch on a certain major/minor release

- 0 means : no patch
- 1 means the first patch for one particular customer’s major or minor release
- 2 means another patch for another particular customer’s major or minor release

When the unit is not known, DIEXID:0; can be entered: 0 means 'own unit'.
Parameter <REPORT-FORM> can be :

- 0 = Brief Report : is also shown in case the parameter is omitted.

- 1 = Verbose Report
- 2 = License Configuration Report
- 9 = CPU3000 SIMM Report

COUNTRY# indicates the country number.

COUNTRY COUNTRY# COUNTRY COUNTRY#

Austria 720 France 380
Australia 150 Great Britain 420
Belgium 170 Italy 520
Brazil 200 Luxembourg 630
Switzerland 980 Netherlands 670
Germany 320 Portugal 790
Denmark 300 Sweden 970
Spain 850 South Africa 960
Hungary 450 Rest of the World 000
Far East 022

- 40 -
Then the exchange number, administrative number, the user number (not used) and the 12 NC are
displayed.

The second line in DIEXID displays information related to the SIP@Net upgrade period.

REPORT-FORM = 1 (Verbose Report) :

The following output also appears, showing the Loaded Overlay Sets :
FILE EXT 12 NC PACK ID L
xxxx.xx xxxx xx x xxxxx xxxx.xx x

This gives the names of all files, their extension, if they are active or not, the package-ID and the level.

REPORT-FORM = 2 (License Configuration Report)

The following output appears, showing the type of exchange :
UNIT LICENSE CONFIGURATION
1 iS3030 License

REPORT-FORM = 9 (CPU3000 SIMM Report)

Supports the investigation of possible problems with the SIMMs on the CPU3000.
The following output appears :
[xxxxxxxx][xxxxxxxx]yyy

where ‘x’ is a one-character information item of one flash component on [SIMM1][SIMM2].

Possible values of ‘x’ are :

space : component not present

‘-’ : unkwown Flash type
‘a’ : any AMD device
‘B’ : STM M29F016B (not to be trusted)
‘d’ : STM M29F016D
‘f’ : Fujitsu device
‘s’ : other STF device

‘yyy’ indicates the settings of the RAMs used on the AM3000 module :

‘yyy’ = MC68040 burst cycles are disabled : new RAM (9600 021 13xxx)
‘yyy’ = missing : old RAM (9600 021 46xxx)

- 41 -
12. DIGITAL ALARMS
This command is used to get information about the detector status in the DTUs received by the CM.

Display Digital Alarms 300

DIDILA:<SHELF>,<BRD>s/r[,[<CRT>s/r][,<MODE>]];
The CRT parameter must be omitted for non-ISDN non-Basic-Access boards like the DTU-CA, DTU-PR,
DTU-CC, DTU-PH and DTU-PU. The CRT parameter is mandatory for ISDN circuits from DTU-BA, DTU-PH and
DTX-I.
The display MODE is only valid for non-ISDN DTU boards. If MODE is omitted the abstract display is given.

Response (abstract):
Alarms of resource on position <SHELF>,<BRD>, since <DATE>,<DAY-OFWEEK>,<TIME>

Detector Status Counter

Clock error detected On/Off 0
Loss of frame alignment On/Off 0
Excessive error rate detected On/Off 0
Slip detected On/Off 0
Signalling handler watchdog alarm On/Off 0
Loss of multiframe alignment On/Off 0
Remote alarm detected On/Off 0
Remote alarm ts16 detected On/Off 0
AIS 2 Mbit/s detected On/Off 0
AIS 64 kbit/s detected On/Off 0

Response (full display):

Alarms of resource on position <SHELF>,<BRD>, since <DATE><DAY-OFWEEK>,<TIME>

Detector Status Counter

Clock error detected On/Off 0
Alarm indicated by LTU On/Off 0
Loss of frame alignment On/Off 0
Excessive error rate detected On/Off 0
Slip detected On/Off 0
Signalling handler watchdog alarm On/Off 0
Loss of multiframe alignment bit 0 On/Off 0
Loss of multiframe alignment bit 1 On/Off 0
Loss of multiframe alignment bit 2 On/Off 0
Loss of multiframe alignment bit 3 On/Off 0
Remote alarm detected On/Off 0
Remote alarm ts16 detected On/Off 0
AIS 2 Mbit/s detected On/Off 0
AIS 64 kbit/s detected On/Off 0

- 42 -
Response (ISDN):
Alarms for trunk resource on position <SHELF>,<BRD>,<CRT>, since <DATE>
<DAY-OF-WEEK>,<TIME>

Detector Status Counter

Bit error warning On/Off 0
Slip warning On/Off 0
Power overload On/Off 0
Loss of frame alignment On/Off 0
Alarm indication signal On/Off 0
Loss of signal On/Off 0
RAI On/Off 0
RAI CRC4 On/Off 0
Excessive bit error On/Off 0
Excessive slip On/Off 0
Clock error On/Off 0
Link failure On/Off 0

Erase Digital Alarms 368

ERDILA:<SHELF>,<BRD>s/r[,[<CRT>s/r][,<MODE>]];

- 43 -
13. DISPLAY METERING
Display Metering Results 126
DIMERE:<MET-TYPE>[,[<BSP-ID>s/r] [,<UNIT>s/r OR<ROUTE>s/r]];
The command will only be accepted if the protection levels are at least 5 for each of the actions New,
Append, Read and Delete. The header line states whether the read type is destructive or non-destructive.
This is a system option.

If only MET-TYPE is entered, the system will ask the following:

- MET-TYPE 0, Metering on BSP-ID.

Additional parameter : [<BSP-ID>];
- MET-TYPE 1, Night Extensions.
Additional parameter : [<UNIT>];
- MET-TYPE 2, Route.
Additional parameter : [<ROUTE>];

If the question is answered with a single semi-colon, all results of the given metering type are displayed.
Response:

DNR-BSPT/NE-UNIT/ROUTE (NON) DCESTRUCTIVE READ TYPE

(Dep. on MET.-TYPE) METERING COUNTS
xx xx

- 44 -
14. DNR/BSP-ID - LINE CIRCUIT/CENTRAL MODULE RELATIONS
This group of OM commands is used to display and change the relation between DNRs/BSP-IDs and line
circuits/central module.
Note that the maximum length of a DNR can be upto 10 digits. This applies to all DNR related functionality
including all DNR-related OM commands and OM display output.
System boundary NEBOUND 421 (max number of DNR digits) defines the maximum number of digits of a
DNR. Valid values are 6, 8 and 10. Other values are corrected as follows: 7 is changed to 8, 9 is changed to
10, smaller than 6 or larger than 10 is changed to 6. To change this boundary it must be added to the PE
projecting file, with which the system must be reprojected. Commands CHBOUN and EXSUBC can not be
used to change this boundary.

Change Extension DNR/BSP-ID to Line Circuit/Central Module Relation 99 # !

CHDNRC:<BSP-ID>s/r[,<SHELF>,[<BRD>],<CRT>[,<ACTION-INDICATOR>]];
Depending on the parameter combination and whether the BSP-ID is entered, an assign, delete or move
action is executed:

- ASSIGN: assign a DNR, create hardware-less DNR or make a DNR hardware-less. BSP-ID, SHELF, BRD, CRT
and [ACTION-INDICATOR] must be entered. If the BSP-ID only consists of a DNR and the DNR is not yet
known in the system then the default BSPT will be used. For the hardware-less DNR, the Central
Module-EHWA must be given.

- DELETE (hardware-less) DNR/BSP-IDs.

Enter a BSP-ID only. If only the DNR part of the BSP-ID is entered, then all BSP-IDs with that DNR are
deleted.

- MOVE (hardware-less) DNR to a line circuit EHWA.

DNR, SHELF, [BRD], CRT, [ACTION-INDICATOR] must be entered. Ony the DNR part of the BSP-ID is
entered, for always all BSP-IDs with that DNR are moved to the entered hardware address. For the
hardware-less DNR, the Central Module-EHWA must be given.
ACTION-INDICATOR ([P[Q[R]]]).
When this parameter is omitted, PQR will get the default value 000.
P determines whether a multi-unit move must still be executed if the destination unit has not enough
room for the IABD list or for the name of a DNR . If this bit is set then a multi-unit move might erase the
IABD list and/or the database contents associated with a DNR
Q is the ORDER-INDICATOR. It indicates whether the BSP-ID must be inserted before or after an existing
BSP.
R indicates the desksharing license facility indicator.

Change Operator DNR to Operator Circuit Relation 100 # !

CHOPDC:<DNR>s/r[,<SHELF>,<BRD>,<CRT>,<OPERATOR-TYPE>];
If the hardware address is omitted, the relation is erased. If the operator DNR is to be moved to another
line circuit, the old relation must be erased first.

Display Circuit to DNR/BSP-ID Relation 101

DICDNR:<SHELF>,[<BRD>s/r],<CRT>s/r;
To reduce processing time it is advised in case of a range of parameters for the circuit number to choose
the upper value not higher than the actual highest circuit number on a board in the system.
For the hardware-less DNR, the Central Module-EHWA must be given.

- 45 -
Response example:
SHELF BRD CRT TYPE DNR-BSPT Usable MSN
2014 - 0 Hardware-less 2014-95 No No

Display DNR to Circuit/Central Module Relation 102

DIDNRC:<BSP-ID>s/r;
Response example:
DNR SHELF BRD CRT TYPE
1234 2011 11 2 LC
1245 2014 - 0 Hardware-less

Note: Active desksharing DNRs are displayed as ‘normal' fixed DNRs; inactive desksharing DNRs are
hardware-less DNRs.

Change Basic DNR/BSP 35 # !

CHBDNR:<BSP-ID>[,<UNIT>];
If UNIT is specified: create the Basic DNR or add a new BSP-id to the Basic DNR of the specified unit. Each
unit must have a different Basic DNR projected. If the DNR exists already for the specified unit, the DNR-
part of the new BSP-ID must be the existing DNR of that unit.
If UNIT is not specified: delete Basic DNR. If only the DNR-part of the BSP-ID is entered, then all BSP-IDs
with the Basic DNR are deleted.

Display Basic DNR/BSP 53

DIBDNR:[<UNIT>];
Display the Basic DNR of the specified unit. If no unit is specified the Basic BSPs of all units are shown.
Response:
DNR-BSPT UNIT
xxxx-xx xx

Change SMA Relation 503 # !

CHSMAR:<SHELF>,<BRD>,<CRT>[,<DEST-NUMBER>];
This command is used to change/delete the relation between the virtual SMA circuit and the called-number
of a remote user. The called-number of the SMA user consists of the Trunk Access Code and the telephone
number of the remote user. When a virtual SMA circuit contains a CLI of a remote user, then the remote
user can directly use SMA access from a remote location without using the activate procedure.

Display DNR - MAC Address/SMA Relation 509

DIDNRR:<BSP-ID>s/r;
When a DNR is related to an IP-terminal then the MAC-address of the IP-terminal is displayed.
When a DNR is moved to a virtual SMA shelf then the number of the remote user is displayed, when the
SMA is active.
DNR SHELF BRD CRT SIG-GROUP TYPE DESCRIPTOR
2300 2015 3 0 0101 IP 08 00 6F 82 20 6C
2370 2016 1 2 0201 SMA 00612345678

- 46 -
15. DOWNLOAD
Download comprises three subjects:
- The downloading of extensions (SOPHO-SETs/LAMs, ErgoLines);
- The downloading of firmware packages for terminals (ErgoLine D325);
- The downloading of packages to peripheral boards.

15.1. EXTENSION DOWNLOAD

This command requests the download of DTE data to a DNR related to a LAM or the download of DTE data
and function key data to a DNR, related to a SOPHO-SET. See also section "Remarks about Downloading" in
chapter "Data Functions".

Download for a BSP-ID 296

DOWNLD:[<BSP-ID>s/r][,<ALL-SIP>[,<UNIT>]];
An ALC or ISDN extension can not be downloaded, although this command returns “EXECUTED” in such a
case. It is not allowed to enter the all-BSPT (99) as BSPT part.
- to download a (range/series) of (SIP/TMP) terminals : DOWNLD:<BSP-ID>sr;
- to download all SIP terminals : DOWNLD:,1[,<UNIT>];
In case of SIP terminals, see also OM command DOWNLS below.

Download Specific SIP Terminal 635

DOWNLS:[<SHELF>,<BRD>s/r,<CRT>s/r][,,,<UNIT>];
In case a SIP terminal uses desk sharing and the terminal is in the logged off situation (no BSP-ID assigned to
the virtual SIP EHWA), it is not possible to trigger the download of that specific SIP terminal, due to the fact
that OM command DOWNLD requires a BSP-ID.
The only option to trigger the download of such an extension is to give OM command DOWNLD:,1;
causing all SIP terminals to download.

To overcome this situation, OM command DOWNLS can be used (since SIP@Net 5.2). This command allows
the user to specify a specific virtual SIP EHWA and trigger the download of a specific SIP terminal.
- to download specific SIP terminal(s) use : DOWNLS:<SHELF>,<BRD>sr,<CRT>sr;
- to download all SIP terminals use : DOWNLS:,,,<UNIT>;

15.2. TERMINAL DOWNLOAD

Terminal downloading is supported for the ErgoLine D325, D330 and D340 with firmware package 2.01
onwards.

Only idle terminals, loaded with a package that is not similar to the provided software package, or no
software package, are downloaded. The firmware package of the terminals that have to be downloaded
must be on the LBU (in all units).

If one download is started, no other downloads can be executed because one download is permitted at the
time.

The parameter PACK is related to a specific terminal type.

- 47 -
Start Downloading Terminal(s) 558 # !
STDOTE:<PACK>[,[<SHELF>],[<BRD>][,[<CRT>][,<UNIT>s/r]]];
The syntax and the different input possibilities are as follows :

- To upgrade all terminals of a certain type, network wide :

STDOTE:<PACK>;

- To upgrade all terminals of a certain type, in one unit :

STDOTE:<PACK>,,,,<UNIT>s/r;

- To upgrade all terminals of a certain type in one PM :

STDOTE:<PACK>,<SHELF>,,<CRT>; specify the EHWA of the PM

- To upgrade all terminals of a certain type connected to one board :

STDOTE:<PACK>,<SHELF>,<BRD>;

- To upgrade one specific terminal :

STDOTE:<PACK>,<SHELF>,<BRD>,<CRT>;

Since terminal downloading is a CPU time consuming action, it is recommended to do this downloading
preferable outside working hours. Downloading of terminals is done in parallel. During downloading the
terminal is 'non-operational'.

The verification of the download is initiated with the OM command DIDOTE. This command compares the
given file with the loaded package and displays, if present, the incorrectly loaded terminals.
After a download action of the terminals, the maintenance engineer can check whether the download was
successful or not using OM command DIDOTE. OM command DIEQID can be used to check which package is
present in the terminal.

Display Downloading Terminal(s) 559

DIDOTE:[<PACK>[,[<SHELF>],[<BRD>][,[<CRT>][,<UNIT>s/r]]]];
The syntax, different input possibilities and response examples are as follows :

To check in all units (or in one specific unit) if the download (terminal or board) is still running :
<DIDOTE:;
or e.g. <DIDOTE:,,,,2&3;
UNIT 2 : Download process is RUNNING
UNIT 3 : Download process IDLE
: Download process temporary unavailable
: Download process start error, write software error report

To display all terminals (network wide) not loaded with the file specified by parameter PACK :
<DIDOTE:<PACK>;
e.g. <DIDOTE:FE5101.010;
or <DIDOTE:FE5101.010,,,,2&3;
SHELF BOARD-NUMBERS
2011 1 3 7 8 11 15
3011 10 11 13 14

- 48 -
To display all terminals (for the specified unit or for one specified PM) not loaded with the file specified by
parameter PACK :

<DIDOTE:<PACK>,<SHELF>,,<CRT>;
e.g. <DIDOTE:FE5101.010,2014,,2; (specify the EHWA of the PM)
or <DIDOTE:FE5101.010,2011;
SHELF BOARD-NUMBERS
2011 1 3 7 8 11 15
2012 10 11 13 14

To verify all terminals of a certain type connected to one board :

<DIDOTE:<PACK>,<SHELF>,<BRD>;
e.g. <DIDOTE:FE5101.010,2011,7;
SHELF BRD PCT-NUMBERS
2011 7 2 6 10 14

To verify one specific terminal :

<DIDOTE:<PACK>,<SHELF>,<BRD>,<CRT>;
e.g. <DIDOTE:FE5101.010,2011,7,6;
SHELF BRD CRT SOFTWARE STATUS
2011 7 6 EMPTY
INCORRECT-PACKAGE
CORRECT-PACKAGE
NOT-AVAILABLE (means that the specified resource is not responding to the
information request)
NO-RESPONSE (means that the PMC to which the specified resource
belongs is not responding to the information request)
ALL CORRECT (means that the resources have the correct package)

15.3. PERIPHERAL BOARD DOWNLOAD

Install Software Package Relation 316 # !

INSTPK:[<NEW-PACK>],[<OLD-PACK>][,<BRD-STYP>];
Keep in mind that with this command the relation between a board (sub) type and the firmware package is
specified.
The actual downloading of the package starts after a SETOUT/SETINS of the board.
- Install a new package relation :
INSTPK:<NEW-PACK>[,,<BRD-STYP>];

- Replace an old package relation by a new :

INSTPK:<NEW-PACK>,<OLD-PACK>[,<BRD-STYP>];

- Delete a package relation :

INSTPK:,<OLD-PACK>[,<BRD-STYP>];

Parameter <BRD-STYP> can be used in case different packages has to be loaded on the
same kind of board.

- 49 -
Parameter <BRD-STYP> must be used in systems with a mixture of same kind of boards,
because those boards have different incompatible firmware packages.
This applies for the following boards :

- DTX-I and DTX-I(R) : F220xx and F221xx

- PMC-MC/HR and PMC-G : F14xxx or F15xxx and F18xxx
- PMC-G and PMC-SIC : F18xxx and F19xxx

Firmware downloading is done in a different way for the following boards :

- ISG : the firmware and a prebisg.txt (specifying the package) must be on a TFTP server.
- SIC : the firmware and a prebsic.txt (specifying the package) must be on a TFTP server.
- PMC-SIC : can be done via INSTPK and/or from TFTP server (prebpmc.txt).
In case both methods are active and define different packages, the PMC-SIC will first download the TFTP
package and then the INSTPK package.
So the package defined by INSTPK overrules the TFTP package !!!

Display Software Package 412

DIPACK:[<SHELF>,<BRD>s/r];
When SHELF and BOARD are omitted, displayed is the package that should be present at a board type with
a specific board sub type.
When SHELF and BOARD are not omitted, displayed is the package that should be present (PACKAGE-ID)
and the package that is actually present at the board (LOADED-PACKAGE):
SHELF BRD CRT TYPE SUBTYPE PACKAGE-ID LOADED-PACKAGE
xxxx xx xx xx xx xxxx.xx.xx xxxx.xx.xx

Delete Software Package 410 # !

DEPACK:<SHELF>,<BRD>s/r[,<WAIT>];
This can only be executed for a board which is out of service.
WAIT: wait for completion of the delete operation (yes = 1, no = 0).

15.4. DT700/DT820 FIRMWARE DOWNLOADING

Initially the DT700/DT820 SIP terminals are loaded with NEC proprietary SIP firmware (NSIP). To be able to
cooperate with SIP@Net, this NSIP firmware has to be replaced by Standard SIP firmware. This Standard SIP
firmware must be available on a TFTP server in the network.
This way of downloading is possible since SIP@Net 5.0 in combination with SIP driver version 1.3.0 (or
higher). Note that it is independent of the DT700/DT820 firmware version itself.
It is not necessary that all DT700/DT820 terminals are in the same VLAN.
In case of previous releases of SIP@Net and/or SIP driver, one have to use the “IP Phone Manager”, to load
Standard SIP firmware : all DT700/DT820 terminals must be in the same VLAN.
However to get the terminal operational several configuration files have to be made.
Since SIP@Net 5.1 "One Touch Deployment" is introduced, requiring only three configuration files per
system.

IMPORTANT NOTE
It is not possible to replace NSIP firmware by DT700 Standard SIP firmware version 2.1 (or higher) in one go.
First replace NSIP firmware by Standard SIP firmware version 2.0 using the command CHDTSS. Once this
version 2.0 is loaded in the terminal, upgrade from version 2.0 to version 2.1 (or higher) by putting version
2.1 (or higher) on the TFTP server and rebooting the terminals.

- 50 -
CAUTION: DURING THE REPLACEMENT PROCESS OF NSIP FIRMWARE BY STANDARD SIP FIRMWARE, DO
NOT INTERRUPT THE DOWNLOAD/SAVING PROCESS.
IF INTERRUPTED, THE TERMINAL WILL DAMAGED AND WILL NOT BECOME OPERATIONAL !!!

Change DT700/DT820 System Settings 620 # !

CHDTSS:[<IP-ADDRESS-TFTP-SERVER>][,<UNIT>];
The command will ask for the additional parameters :

Enter [<ALTERNATIVE USERNAME>>]:;

Enter [<PASSWORD>]:;

This command specifies the IP address that the DT700/DT820 needs to use for the TFTP server, to obtain its
Standard SIP firmware package. If no proper TFTP IP address is specified, automatic conversion of the NSIP
package to a Standard SIP package is not performed. Even though the DT700/DT820 receives the IP address
of the TFTP server using DHCP, this parameter is not used when a firmware download is enforced from
SIP@Net, requiring the need for this command.

For successful downloading, also check the following items :

- the system is running SIP@Net 5.0 (or higher).
- SIP driver version 1.3.0 (or higher) is used.
- in the DHCP server pass the boot server for TFTP along in option 66 as follows :
tftp://192.168.1.80
So include tftp:// in front of the IP address : this assures that the terminal uses TFTP without
changing the download protocol manually.
- in the DHCP server, option 162 has to be used as well : here the IP address of the SIP driver has to be
specified.
- use LLDP for auto-advertisement and discovery of the network parameters.

System timer NETIMER247 (DT700/DT820 Download Guarding Time) guards the firmware download
process.
In case parameter <IP-ADDRESS-TFTP-SERVER> is omitted, the IP address will be removed. If no IP
address is specified, DT700 firmware downloading is not performed automatically by SIP.
Parameter <IP-ADDRESS-TFTP-SERVER> is used in combination with "One Touch Deployment" of
DT700/DT820 and Polycom Soundpoint SIP terminals. It specifies the default Alternative Username.

See also section 37.3. LICENSES FOR DT820 STANDARD SIP TERMINALS for more DT820 details.

Display DT700/DT820 System Settings 621

DIDTSS:[<UNIT>s/r];
This command shows the IP address of the TFTP server. If no proper TFTP IP address is specified, automatic
conversion of the NSIP package to a Standard SIP package is not performed. Even though the DT700/DT820
receives the IP address of the TFTP server using DHCP, this parameter is not used when a firmware
download is enforced from SIP@Net.
Response:

<DIDTSS:;
UNIT IP-ADDRESS-TFTP-SERVER
1 192.168.1.80
UNIT DEFAULT-USERNAME DEFAULT-PASSWORD
1 NEC -

- 51 -
16. DPNSS CLUSTER IDENTITY / ASSISTANCE POINT / FREE NUMBERING /
DECT MOBILITY iSNet WAN
16.1. CLUSTER IDENTITY

These commands are used to assign and display the DPNSS identity and/or assistance point of a system.
The identity is called the cluster identity. This is the number, by which the iS3000 system can be reached by
other exchanges. The assistance point defines where operator assistance should be given.

Change Cluster Identity 320 # !

CHCLID:[[<CLUSTER-ID>] [,<ASSISTANCE-POINT>[,<LOCAL-OPERATOR-MARK>]]];
If the assistance point is omitted, source assistance is selected.
If the Cluster ID and the assistance point are omitted, it is cleared.
If the local operator mark is omitted, value 0 will be assumed.

Display Cluster Identity 321

DICLID:;
Response:
CLUSTER-ID Assistance point Local Operator Mark
xx xxxx xx

Note: Any assistance point and local operator mark assigned to a compatibility value by CHCVAP overrules
those assigned by CHCLID. Therefore, first check the settings of the compatibility value by DICVAP.

16.2. ASSISTANCE POINT

Change CV related Assistance Point and Local Operator Mark 452 # !

CHCVAP:<CV>[,<ASSISTANCE-POINT>[,<LOCAL-OPERATOR-MARK>]];
This command assigns or removes the assistance point related to the entered CV. Also the local operator
mark related to this assistance point can be assigned.
If only the CV parameter is specified, the assistance-point will be deleted.

Display CV related Assistance Point and Local Operator Mark 453

DICVAP:[<CV>s/r];
This command displays the compatibility value's assistance point and local operator indication. If no CV is
specified, the assistance-point and local-operator-mark of all CVs are displayed.
Response:
CV ASSISTANCE-POINT LOCAL-OPERATOR-MARK
xx xxxxxxxxxxxx Yes
xx No

- 52 -
16.3. FREE NUMBERING

Assign/Change the Network Location of a Free Number 450 #

CHFDNR:[<FDNR>][,<FN-LOC-1>[,<FN-LOC-2>]];
The following parameter combinations are allowed :
- Assign or Change the network location of the specified Free Number :
CHFDNR:<FDNR>,<FN-LOC-1>;
- Change the network location of all Free Numbers with FN-LOC-1 to FN-LOC-2 :
CHFDNR: ,<FN-LOC-1>,<FN-LOC-2>;
- Remove specified Free Number :
CHFDNR:<FDNR>;
- Remove all network locations of FN-LOC-1 (a confirmation request (yes/no) is given to prevent the user
accidentally deleting all FDNRs related to a given FN-LOC-1) :
CHFDNR: ,<FN-LOC-1>;
- Remove all Free Numbers :
CHFDNR: ;

Display the Network Location of a Free Number 451

DIFDNR:<FDNR>][,<FN-LOC>];
The following parameter combinations are allowed :
- Display all Free Numbers with their network location :
DIFDNR: ;
- Display the network location of the specified Free Number and the network location of the Free
Numbers that start with the specified Free Number :
DIFDNR:<FDNR>;
- Display all Free Numbers with the specified Network Location :
DIFDNR: ,<FN-LOC>;

Response:
FREE NUMBER NETWORK LOCATION
1234 5678

16.4. DECT MOBILITY IN iSNet WAN

The commands in this section have to be used to implement DECT Mobility in an iSNet WAN (Wide Area
Network) based on DPNSS. In each ISPBX the so called Node IDs of the other ISPBXs must be assigned
(ASNOIT).

The own Node ID is allowed to be present in the Node ID list, but this is not required. This allows each Node
to have the same list of Node IDs.

Before assigning the Node IDs, they first have to be specified using OM command CHCLID.

Assign Node ID to Node ID Table 594 # !

ASNOIT:<NODE-ID>s;
When a new Node ID is added to the list of Node IDs (which is present in all the nodes), each node in the
network shall be updated.

- 53 -
Erase Node ID from Node ID Table 595 # !
ERNOIT:[<NODE-ID>s];
To remove Node ID entry/all entries from the list of Node IDs in the nodes of the network.
When parameter NODE-ID is omitted all Node ID entries are deleted.

Display Node ID Table 596

DINOIT:;
This command displays (in increasing order) the list of nodes in the network.
Response:
NODE ID
32
51

- 54 -
17. EMPOWERED USER
An “empowered user” is relevant in a SIP@Net configuration, having the 3C App Suite.
Such an empowered user has a SIP@Net device and one or more 3C devices. Depending on the user
preference SIP@Net features or 3C features are made available. A SIP@Net device keeps his SIP@Net
characteristics and a 3C device keeps his 3C-characteristics. So a user interface of (for example) a DT700 SIP
terminal depends on the platform that receives the SIP registration.

Create Empowered User 636 # !

CRPUSR:<DNR>s/r,<TAC>;
This command creates an empowered user in SIP@Net. Parameter TAC is the Trunk Acces Code of the SIP
trunk to 3C.

Display Empowered User 637

DIPUSR:[<DNR>s/r];
This command diplays the relation of an empowered user.
When parameter DNR is omitted all relations are shown.
The status in SIP@Net can be : Free, Busy or Not usable.

DNR TAC STATUS

1400 65 Free
1401 65 Busy
1402 65 Not usable

SIP@Net Status 3C Status Meaning

Free Online DNR has been subscribed for presence at 3C system and non of the
devices of the preferred user is on the phone.
Busy On the phone DNR has been subscribed for presence at 3C system and one of the
devices of the preferred user is on the phone.
Not usable Offline DNR has not been subscribed at 3C system.

Delete Empowered User 638 # !

ERPUSR:<DNR>s/r;
This command deletes the relation of one or more empowered users.

- 55 -
18. EXECUTIVE SECRETARY GROUPS
18.1. NORMAL EXECUTIVE/SECRETARY GROUPS

Assign Executive Secretary Relation to Pool 146 # !

ASEXSE: <EXEC/SECR-BSP-ID>,[<EXEC-BSP-ID>],[<EXEC-RANK>],
<SECR-BSP-ID>[,[<SECR-RANK>][,<EXEC-LINE-POS>]];
This command is used to add executives and secretaries to an existing pool, created with the CREXSE
command. If only a secretary is added, the EXEC-BSP-ID and EXEC-RANK must be omitted. If an executive is
added the SECR-BSP-ID will be the preferred SECR-BSP-ID and may never be omitted. SECR-RANK may be
omitted if it is a single secretary pool.

The EXEC-LINE-POS is only allowed if the EXEC-BSP-ID is not empty and if the EXEC-BSP-ID and the SECR-
BSP-ID are located in the same unit. Note that when the EXEC-LINE-POS is omitted or set to 'no', it is not
possible to assign it to an 'executive key' (because no function key translation takes place).

Create Executive Secretary Pool 145 # !

CREXSE: <TYPE-CODE>,<EXEC-BSP-ID>,[<EXEC-RANK>],<SECR-BSP-ID>
[,[<SECR-RANK>][,<EXEC-LINE-POS>]];
This command is used to create a pool, assign general pool information to it and to enter the first executive
secretary relation to it. The executive BSP-ID may not be already in use as an operator or group-DNR or a
secretary BSP-ID. The same applies to the secretary BSP-ID. The EXEC-RANK and SECR-RANK may be
omitted if there is only one executive and one secretary in the pool.

The EXEC-LINE-POS is only allowed if the EXEC-BSP-ID and the SECR-BSP-ID are located in the same unit.
Note that when the EXEC-LINE-POS is omitted or set to 'no', it is not possible to assign it to an 'executive
key' (because no function key translation takes place).

Display One or More Executive Secretary Pools 148

DIEXSE:[<EXEC/SECR-BSP-ID>s][,<UNIT>s/r];
Response:
TYPE CODE EXECUTIVE SECRETARY
PQRSTU DNR-BSPT RANK EXEC-LINE-POS DNR-BSPT RANK
xxxxxx xxxxxx xx xx xxxxxx xx

Erase an Executive Secretary Pool 147 # !

EREXSE:<EXEC/SECR-BSP-ID>s;
If the message "Inconsistent executive-secretary pool data" is displayed, the command should be executed
again.

- 56 -
18.2. ENHANCED EXECUTIVE/SECRETARY GROUPS

The commands for enhanced executive/secretary groups create command files. These command files will
have to be offered by the user to the system in order to create or erase the enhanced executive/secretary
groups.
See also chapter 9. COMMAND FILE EXECUTION.

Create Command File to Create Executive/Secretary Group 251 # !

CRESGR:<GROUP-DNR>[,<GROUP-PROPS>];
The properties MUST indicate a non-ACD group with group display. If this parameter is omitted value "9"
will be used.
Switch allowance for all members (yes/no) : YES/NO;
Line position status prevails extension status (yes/no) : YES/NO;
Rerouting after transfer prohibited (yes/no) : YES/NO;
Hold tone after transfer (yes/no) : YES/NO;
LED based status monitoring (yes/no) : YES/NO;
Inhibit diversion for member - member calls (yes/no) : YES/NO;
Unrestricted call pick-up allowed (yes/no) : YES/NO;
Call forwarding on busy executive to secretary (yes/no) : YES/NO;
Secretary allowed to switch absent (yes/no) : YES/NO;
Busy indication when executive and secretary busy (yes/no) : YES/NO;
Common park positions (yes/no) : YES/NO;
Line position for executives (yes/no) : YES/NO;
Line position for secretaries (yes/no) : YES/NO;
Private park positions for executives (yes/no) : YES/NO;
Executive line position for executives (yes/no) : YES/NO;
Executive BSP-ID X : [<BSP-ID>];

- (No BSP-ID means last executive).

Preferred Secretary BSP-ID X:[<BSP-ID>];

- (No BSP-ID means last secretary).

Non preferred Secretary BSP-ID:[<BSP-ID>];

- (No BSP-ID means last secretary).

Command File name:[<COMMAND-FILE>];

If the name of the command file is omitted, file name: LBUxx:CRESGR.COM./ is used, unless it already exists.

Display Executive - Secretary Group 302

DIESGR:[<GROUP-DNR>];
When the GROUP-DNR is omitted, all groups in the system are displayed.
Response:
PROP GROUP PARK EXT-PROP CF-O-BUSY SECR-SW BUSY-B-I EXE-PICI MULT-EX MULT-SE
xx xx xx xxxxxxx xxx xxx xxx xxx xxx xxx
MEMBER RANK SW-ALL TYPE RANK LINE-POS PARK-POS EXEC-LP MENU PRE-SECR FM-ACT
xxxxxx xx xxx xxxx x xxx xxx xxx xx xxxxxx xxx

Command DIPLPO displays the park/line position status. See also chapter Group Arrangements.

- 57 -
Create Command File to Erase Executive/Secretary Group 301 # !
ERESGR:<GROUP-DNR>;
Additional parameters:

Command File name: [<COMMAND-FILE>];

If the name of the command file is omitted, file name LBUxx:ERESGR.COM./ is used.

Create Command File to Initiate Certain Function Key Menus 306 # !

INESGR:;
Creates a command file to initiate standard menus (last 6 menus in the system) for executives and
secretaries.
Additional parameters:

Enter short access code : <NUMBER>;

Command File name: [<COMMAND-FILE>];

If the name of the command file is omitted, file name: LBUxx:INESGR.COM./ is used, unless it already exists.

- 58 -
19. FACILITY CLASS MARKS
Facility Class Marks (FCM) are related to extensions. They are used in two ways:

- As an indication to the system, to which facilities an extension user is entitled

- To indicate the characteristics of an extension, e.g. Long Line or Voice Mail Server

Each OM terminal has a restriction level, indicating which FCMs may be changed. This restriction level of an
OM terminal can be changed. See also chapter 59. SYSTEM SECURITY.
Note that some FCMs are marked as "Read Only" in appendix B. PARAMETERS. This means that they can
not be assigned or erased with ASFACM and ERFACM, but a specific other command must be used to assign
and erase them. An example of this is FCM Hot Line, which must be assigned with command CHHOTL.

Note that there are two possibilities to display Facility Class Marks :

- display the Facility Class Marks assigned to one or more BSP-ID.

- display all BSP-IDs to which one particular Facility Class Mark is assigned.

19.1. FACILITY CLASS MARKS FOR EXTENSIONS

These commands make it possible to assign, erase and display the FCM of specific extensions and to display
the summary of the FCMs used in the system.

Assign Facility Class Mark 20 # !

ASFACM:<FCM>s,<BSP-ID>s/r;

Display Facility Class Mark 22

DIFACM:<BSP-ID>s/r;
or
DIFACM:,<FCM>[,<UNIT>];
In case of a multi-unit configuration and the unit is specified, the DNRs/BSP-IDs with the specified FCM will
be retrieved only for the specified unit.
When the unit is omitted, the command is executed system wide : note that this can take a while.

Response examples:
<DIFACM:2505&2506;

DNR-BSPT FACILITY CLASS MARKS

2505-95 7 : Follow me / call forwarding entitled
57 : Desk-sharing entitled
82 : R/O CSTA monitored
2506-95 7 : Follow me / call forwarding entitled
69 : Cost of call on assisted user
82 : R/O CSTA monitored

<DIFACM:,82;

DNR-BSPT FACILITY CLASS MARKS

1250 82 : R/O CSTA monitored
1260
2505-95
2506-95
2507-95
2670-95

- 59 -
In the given example, 1250 and 1260 are group DNRs.
The displayed information is in order the (group) DNRs have been created.

Display Facility Class Mark Summary 23

DIFCSU:<FCM>[,<UNIT>];
If the UNIT is omitted, the command is performed system wide.
Response:
VOICE-PORTS DATA-PORTS GROUPS
#SET #RESET #SET #RESET #SET #RESET
xx xx xx xx xx xx

These have the following meaning:

VOICE-PORTS #SET : number of voice extensions who have the FCM assigned.
#RESET : number of voice extensions who don't have the FCM.
DATA-PORTS #SET : number of data extensions who have this FCM assigned.
#RESET : number of data extensions who don't have this FCM.
GROUPS #SET : number of group arrangements who have this FCM.
#RESET : number of group arrangements who don't have this FCM.

Erase Facility Class Mark 21 # !

ERFACM:<FCM>s,<BSP-ID>s/r;

19.2. DEFAULT FACILITY CLASS MARKS

These commands are used to change and display the default FCMs, these are facility class marks that are
automatically assigned to new extensions. Note that changing the default FCMs will not affect existing
extensions.

Change Default Facility Class Mark Set for Extensions 18 # !

CHDFCM:<FCM>s[,<ADD-OR-DELETE>];
If the ADD-OR-DELETE parameter is omitted, the facility mark(s) will be deleted from the default set. See
parameter FCM in appendix B. PARAMETERS to determine which FCMs can be assigned as default, they are
marked with D.

WARNING: This action is executed in all the units of a system.

Display Default Facility Class Mark Set for Extensions 19

DIDFCM:;
Response:
DEFAULT FACILITY CLASS MARKS
xx

- 60 -
20. FACILITY TIMING
Assign Facility Timing Service 224 # !
ASFATI: <FACILITY>s/r,<ON-TIME>,<OFF-TIME>,<CYCLIC>[,[<SEQ-TABLE/ZONE>]
[,<UNIT>]];
- When the TRFC facility class (0) is selected for FACILITY, the time when the unit switches from day traffic
class to night traffic class and vice versa is set. Omit SEQ-TABLE/ZONE.

Note that to be able to use the "facility timing" for day-night traffic class switching, system option
LOSYSOP 017 (facility clock operates on traffic service class) must be set to "TRUE".

- When the SAS facility class (1) is selected for FACILITY, the signalling of SAS alarms can be specified to
occur at a pre-defined time. Omit SEQ-TABLE/ZONE.

- When Least Cost Routing and Private Virtual Networking (2) is selected for FACILITY, the active SEQ-
TABLE must be entered. The default SEQ-TABLE for the OFF period is 1, so for an ON period only SEQ-
TABLE 2 to 5 are valid.

- When the Tariff Class Facility (3) is selected for FACILITY, the active ZONE must be entered. The default
ZONE for the OFF period is 1, so for an ON period only ZONE 2 to 5 are valid.

Delete Facility Timing 225 # !

DEFATI: <FACILITY>s/r[,[<ON-TIME>],[<OFF-TIME>][,[<SEQ-TABLE/ZONE>]
[,<UNIT>]]];
If both ON-TIME and OFF-TIME are omitted all programmed intervals are deleted.

Display Facility Timing Service 223

DIFATI:<FACILITY>s/r[,[<SEQ-TABLE/ZONE>][,<UNIT>]];
- Parameter SEQ-TABLE must only be given when FACILITY = 2
- Parameter ZONE must only be given when FACILITY = 3

Response:

UNIT ON-TIME OFF-TIME CYCLIC ON-TIME-EXP OFF-TIME-EXP SEQ-TABLE/ZONE

- 61 -
21. FAULT REPORTS
This chapter contains the commands dealing with fault reports. These are commands concerning alarm
buffers, history buffers and alarm routing.

In all commands if the unit number is omitted the command is performed system wide (advised).

Fault reports (all display commands in this chapter) have the following layout :

CODE TYPE SHELF BRD CRT OCC DATE TIME QLF ADD. INFO

CODE gives the error code. See the Maintenance Manual for more information.
TYPE stands for RESOURCE TYPE : see appendix B. PARAMETERS.
SHELF, BRD and CRT give an indication (if applicable) of the hardware address where the fault occurred.
OCC, DATE and TIME give the number of occurences of the error and the date and time of the first
occurence.
QLF stands for qualifier. Look up the qualifier in the Maintenance Manual - Alarm Codes.
ADD. INFO stands for additional information and gives two digits. Refer to the Maintenance Manual for the
meaning of these digits.

21.1. ALARM BUFFERS

Clear Alarm Buffers 52

CLALRM:[<UNIT>s/r];
Alarms must have been read out before they can be cleared.

Note: Clearing an alarm does not clear the cause of the alarm.

Display Blocked Alarms 46

DIBLCK:[<UNIT>s/r];

Display Major Alarms 50

DIMAJA:[<UNIT>s/r];

Display Minor Alarms 49

DIMINA:[<UNIT>s/r];

Display Silent Alarms 48

DISILA:[<UNIT>s/r];

Switch Alarm Expansion Option Off or On 443

SWALEX:[<OFF-ON>];
With this command the alarm code, qualifier and resource type can be expanded with explanatory text
(when executing the commands DIHIBU, DIMAJA, DIMINA, DISILA and DIBLCK).

- 62 -
21.2. HISTORY BUFFERS

Display History Buffer 47

DIHIBU:<REPORT-TYPE>s/r[,<UNIT>s/r];

21.3. ALARM ROUTING

Confirm Alarm Signalling at Distance 389

CALSIG:;
The Signalling at Distance (SAD) alarms can only be confirmed if the current alarm destination is SAD.
This command is used to confirm alarms on a Remote Maintenance Centre.
Response:
IF ALARMS ARE NOT CONFIRMED:
ALARMS CONFIRMED ROUTE-TYPE ALARM DESTINATION
xxxxx xxxxx xxxx

Reroute Alarm signalling 51

REROUT:<ROUTE-TYPE>[,<UNIT>s/r];
A unit number has to be given only if the route type "Isolate unit" is entered. With the other route types it
is not allowed to enter a UNIT. Note that rerouting alarms is intended for temporary use only : it is NOT
journalled.
To assign another alarm destination, boundary LOBOUND099 (SAS AH Default Alarm Distribution) has to be
changed permanently.

21.4. CORDLESS TERMINAL ADAPTOR ALARMS

These commands are used to display and delete stored alarm information of the Cordless Terminal Adaptor
(CTA) connected to DCCs within the system.

Display CTA Alarms 529

DICTAA:[<SHELF>,<BRD>];
Response:
DNR-BSPT CTA ALARM CURRENT TRANSIENT HISTORY
2402-95 No No No No
CTA software reset No No No

When the EHWA of a DCC is given, then the CTA alarms for all CTAs which have reported alarms and are
related to the given DCC board are displayed.

If the EHWA is omitted, then the CTA alarms for all CTAs which have reported alarms are displayed.

Erase CTA Alarms 530 #

ERCTAA:<BSP-ID>;
With the BSP-ID you select for which CTA the reported alarms will be cleared.

- 63 -
22. FILE MANIPULATION
If in a command the file specification <FILE> is used, it consists of the following items :

<LDN>:<FILE-NAME>.<EXTENSION>.<GENERATION>

If the generation is omitted the latest version will be used.

In the DIRECT and CPYFIL commands it is possible to specify wildcards in some file specifications.
Wildcard characters are:
- * replaces the whole file-name or the file extension;
- % replaces a single character, it is possible to use more than one %.

Copy File 90
CPYFIL:<SOURCE-FILE>,<DESTINATION-FILE>;
If in the destination file the file-name and/or extension are omitted, these will be the same as in the source
file.
Omit the generation number of the destination file as this is administrated by the system autonomously.
Any entered generation number for the destination will be ignored.

Create File 94
CREFIL:<FILE>;
Only / (latest) may be used for the generation. Protection levels of the OM terminal should be at least 3 for
each of the actions New, Append, Read and Delete.
This command is only used to create command files: see chapter 9. COMMAND FILE EXECUTION.
All the commands in the command file should look the same as on the screen, so they must start with the
ready indication <.
If a command asks for additional parameters or passwords these can also be given in the command file, but
should not be preceeded with a <.
The last command of the command file should be <END;
Type EXIT; to close the command file. It is not advised to create other types of files, used by the system
itself.

Example
We want to create a command file (MYFILE.COM) to read out the date and time and to create a group
arrangement.

CREFIL:LBU01:MYFILE.COM./;
LINE 0001 : <DIDATI:;
LINE 0002 : <CRGRPA:1234,12,,1401;
LINE 0003 : 1403,1,0;
LINE 0004 : ;
LINE 0005 : <END;
LINE 0006 : EXIT;

Delete File 91
DELFIL:<LDN>:<FILE-NAME>.<EXTENSION>.<GENERATION>;
Note that the protection levels on the OM terminal should be equal to or more than the protection levels
of the file to be deleted. Only / (latest) or 0 (zero = oldest) may be used for the generation.

- 64 -
Display List of Files on a Logical Device 92
DIRECT: <LDN>:[<FILE-NAME>[.<EXTENSION>[.<GENERATION>]]]
[,<DIRECTORY-TYPE>];
If the directory type is omitted, the system directory is given.
Response, depending on directory type : see appendix B. PARAMETERS.

- System directory:
VOLUME FILE NAME NARD CRE-DATE/TIME MOD-DATE/TIME TS 12NC
- User directory:
VOLUME FILE NAME NAME REFNAME ACI/FLAG DEF CUR
- Description directory:
VOLUME FILE NAME DESCRIPTION

The file name or file extension can be specified using the * as wild card character, for example :

DIRECT:LBU01:ABC.*;

This lists all files starting with "ABC".

Purge File 95
PURFIL:<LDN>:[<FILE-NAME>.<EXTENSION>];
This command erases all old generations of a file. Only the latest version is unaffected.

Type File 93
TYPFIL:<FILE>[,<FORMAT INDICATOR>];
If the generation is omitted, the latest version is used. It is not allowed to type binary files or executable
files. The format-indicator specifies the output format.

Move File 505

MOVFIL:<SOURCE-FILE>,<DESTINATION-FILE>;
Specification of the <SOURCE-FILE>:
<LDN>:<FILE-NAME>.<EXTENSION>[.<GENERATION>]
Specification of the <DESTINATION-FILE>:
<LDN>:[<FILE-NAME>[.<EXTENSION>[.<GENERATION>]]]

MOVFIL makes a copy from a source file to a destination file and when the action is successful the source
file is deleted. When the source file and the destination file are located on the same unit a fast copy is
performed : in this case the time stamp of the destination file will be the same as the time stamp on the
source file.

Zip File 560

ZIPFIL:<SOURCE-FILE>,<DESTINATION-FILE>;
This command is intended to be used in combination with Management@Net and SysManager 410.
ZIPFIL zips a source file to a destination file. The <LDN> must be LBU or DBU. In case of CPU3000 GBU
files may be zipped.
No wildcards are permitted in the source file or in the destination file.
In the source file the addition "/" (newest generation) may be used.
The destination file extension is always 'ZIP'.

- 65 -
23. FOLLOW ME
The OM commands for Follow-me (FM) are used to assign, erase and display the FM facility or the fixed FM
facility. Normal FM destinations can be changed by the extension user, fixed FM destinations cannot be
changed by the extension user. The FM originator is a BSP-ID or group DNR (group DNR is not allowed for
fixed FM). FM destinations are :

- Extension;
- Group number;
- Individual operator;
- Operator M queue;
- External destination;
- Paging;
- DPNSS.

Change Follow Me Relation 290 # !

CHFLME:<FM-TYPE>,<ORIG-BSP-ID>s/r[,[<DEST-NUMBER>][,<CALLORIG-TYPE>]];
If DEST-NUMBER is omitted the relation is erased. Series/Range is only useful if you want to erase Follow-
me relations.

For normal Follow-me : If a relation is assigned the command checks if the originator is Follow-me entitled.
If necessary assign the FCM Follow-me entitled first (ASFACM). The destination should not have FCM
Follow-me protected. This command will only write to the journal file (#) in case of a fixed FM relation.

Display Follow-me Relations 291

DIFLME:<ORIG-BSP-ID>s/r;
Response :
ORIGINATOR FIXED-FM-DESTINATION STATUS FM-DESTINATION ORIG-TYPE
3100-95 3102 NONACT ------ ------
3500-95 3600 ACTIVE ------ ------
3200-95 ---- ------ 3801 Internal
3200-95 ---- ------ 3336 External

- 66 -
24. FUNCTION KEYS AND MENUS
A set of function key definitions that can be sent to an extension is called a menu. Each menu has a number.
This group of commands is used to assign and display the contents of the function keys menus of SOPHO-
SETs and the relation of the menus to the BSP-IDs.
The extension automatically gets the function key data belonging to its menu.
Refer to the Customer Engineer Manual of the relevant SOPHO-SET for more details about function keys.
See also chapter Data Functions and chapter Download for more explanation about downloading.

24.1. FUNCTION KEYS

Change Function Key Data 260 # !

CHFKDA: <MENU>s/r,<KEY>s/r,<KEY-LEVEL>s/r[,[<KEY-DATA>],<PRIO-CODE>
[,<LED-CODE>]];
Optional response (when KEY-DATA is +0, +1, +2, +*, +, ++ or ++1 ... ++9, or LED-CODE is 09 ... 31, 65, 75 or
79 ... 98):

Enter soft ring indication: [<SOFT-RING>];

If SOFT-RING is omitted, no softring is assigned. If the LED-CODE is omitted, 0 = LED off will be assigned.
If KEY-DATA, PRIO-CODE and LED-CODE are omitted the key is deleted from the menu.
The command is journalled, however, when it is executed on an OM device with equipment type 14/15 it
will not be journalled.

Display Function Key Data 261

DIFKDA:[<MENU>s/r[,<KEY>s/r]];
Note: The higher NEBOUND096, the longer you have to wait for the response (max 10 minutes), even
when there are only a few Function Key Data Menus really projected.

Response:
MENU KEY KEY-LEVEL ---KEY-DATA--- PRIO-CODE LED-CODE SOFT-RING
xx xx xx xxxxxx xx xx xx

It is also possible to copy/clear function key menus. The command is journalled, however, when it is
executed on an OM device with equipment type 14/15 it will not be journalled. Notice that this could result
in inconsistent function key network data. This is however not a problem because the combination of this
equipment type and this OM command is primary meant for the MA4000/Management@Net Application.
In that case that application controls the content of the function key menus instead of the iS3000 (see also
NESYSOP 115).

Copy Function Key Data 598 # !

CPFKDA: [<SOURCE-MENU>],<DESTINATION-MENU>s/r[,[<START-KEY>],
[<END-KEY>][,<KEY-LEVEL>]];
No check is performed whether SOURCE-MENU is empty; empty keys will be copied as well.
- when SOURCE-MENU is omitted, the DESTINATION-MENU specified is :
- competely cleared : when START-KEY, END-KEY and KEY-LEVEL are omitted.
- partly cleared : when START-KEY, END-KEY and/or KEY-LEVEL are specified.
- when START-KEY is omitted function key 0 is assumed.
- when END-KEY is omitted all function keys starting at START-KEY are cleared/copied.
- when KEY-LEVEL is omitted both levels are cleared/copied.

- 67 -
Display Translated Function Key Menu 294
DITFKM:<BSP-ID>s/r[,<KEY>s/r];
It is not allowed to give BSPT 99 in the BSP-ID.
Response:

DNR-BSPT MENU KEY KEY-LEVEL --KEY-DATA-- PRIOCODE LED-CODE SOFTRING XLATED

xxxx xx xx xx xxxxxx xx xx xx xx

24.2. MENU-DNR/BSP-ID RELATIONS

Change Menu Number of DNR/BSP 262 # !

CHMDNR:<DNR/BSP-ID>s/r[,<MENU>];
If the MENU is omitted the relation is erased.

Display ALL BSP-IDs Belonging to a Menu Number 396

DIDNRM:[<MENU>s/r][,<UNIT>];
When the unit number is omitted the command is executed systemwide.
When the menu number is omitted all BSP-IDs of all menus are displayed.
Response:

MENU DNR-BSPT
xx xx

Display Menu Number of DNR/BSP 263

DIMDNR:<DNR/BSP-ID>s/r;
Response:
DNR-BSPT MENU
xx xx

- 68 -
25. GENERAL CANCEL CODE / DEACTIVATION DESKSHARING / CHANGE
FACILITY STATE
25.1. GENERAL CANCEL CODE

The General Cancel Code is used to cancel a number of facilities which are active on an extension. This
cancelling is done by dialling a code on the extension.
Data stored in a list controls which facilities are cancelled by the General Cancel Code. The data stored
consists of the result-ids of the facilities to be cancelled.
Changing a General Cancel Code affects data in all units of the network, which means that the results of the
commands ASGECA and ERGECA are system wide.

Assign General Cancel Code 325 # !

ASGECA:<RESULT-ID>s;
The result-ids in the list indicate which facilities are deactivated by the General Cancel Code. The following
result-ids are allowed : 31, 32, 36, 41, 45, 57, 67, 85, 88, 99, 170, 172, 174, 176, 178 and 180.

Display General Cancel Code 326

DIGECA:;
This command displays the General Cancel Code list.

Erase General Cancel Code 327 # !

ERGECA:<RESULT-ID>s;
This command removes result-id(s) from the General Cancel Code list.

25.2. COLLECTIVE DEACTIVATION OF DESKSHARING

By means of the OM command DADESK it is possible to deactivate all the active desksharing extensions.
The deactivation is done unit-wide if the unit number is given as parameter for this OM Command. If during
execution of the OM Command resources are found which cannot be claimed, the related desksharing
extensions are not deactivated. It is also possible to daily schedule the deactivation by means of running a
batch file containing this OM command.

Collective Deactivation of Desksharing 591 !

DADESK:[<UNIT>];
When parameter UNIT is omitted the OM command is executed systemwide. This command is NOT
journalled.

25.3. CHANGE FACILITY STATE

OM command CHFSTA can be used to change the state of an extension facility, for example switch an
executive/secretary or group member absent or present. This command is not journalled.

Change Facility State 597

CHFSTA:<FAC-ID>,<BSP-ID>s/r,<STATE>;

- 69 -
26. GROUP ARRANGEMENTS
When making a new group arrangement, the group must first be created with CRGRPA.
With this command the members of the group can also be assigned.
When adding members to a existing group arrangement ASGRPM must be used.
Deleting members from a group can be done with DEGRPM.
Use DIGRPA to find out which group arrangements are existing and use DIGRPM to find out if a DNR is part
of a group.

Assign a Member to a Group Arrangement 178 # !

ASGRPM: <GROUP-DNR>,<MEMBER-BSP-ID>,[<SWITCH-ALL/INIT-STATUS>],
<MEMBER-RANK>[,[<LINE-POS>][,[<PARK-POS>]
[,[<DEFAULT-GROUP>]]]];
This command is used to add members to an existing group arrangement.
If either the parameters <LINE-POS> or <PARK-POS> is omitted, 0 (no) is assumed.
The <SWITCH-ALL/INIT-STATUS> may only be omitted for an observation group.
Parameter <DEFAULT-GROUP> is only relevant in case of a Multiple Group Member (MGM).

Create Group Arrangement 177 # !

CRGRPA: <GROUP-DNR>,<GROUP-PROPS>[,[<GROUP-DISPLAY>]
[,[<SUPERVISOR-BSP-ID>][,[<PARK-POS>][,<EXT-PROPS>]]]];
In case of an ACD group, the system will ask for additional parameters :

Enter unit number:;

Enter Threshold priority [<THRESHOLD-PRIORITY>],(default=0):;
Enter Full Threshold [<ACD-THRESHOLD>],(default=100):;
Enter Busy Threshold [<ACD-THRESHOLD>],(default=100):;
Enter Forced Absent Time [<ACD-TIME-PERIOD>], default=infinite):;
Enter After Call Work Time [<ACD-TIME-PERIOD>],(default=0 sec.):;
Enter Call in Queue Time [<ACD-TIME-PERIOD>],(default=infinite):;
Enter Pause tone [<ANN-PAUSE-TONE>],(default=Silence):;
Enter CallManager logical device ACDxxy [<LDN>], default=none):;
Enter Queue Pos. Algorithm [<Q-POS-ALGORITHM>],(default=absolute):;
Enter Queue Priority [<Q-PRIORITY>],(default=lowest):;

For all groups the next additional parameters will be asked :

Enter <MEMBER-BSP-ID>,[<SWITCH-ALL/INIT-STATUS>],<RANK>
[,[<LINE-POS>][,[<PARK-POS>][,[<DEFAULT-GROUP>]]]] : ;

The system repeats this question until you enter a single semicolon (;).
Example: 2401,1,4,1,1;

Fill in the BSP-ID, fill in if the member is allowed to switch absent (0 or 1), fill in his rank number within the
group (used for short-code dialling within the group).

For ACD groups, <LINE-POS> and <PARK-POS> must be omitted.

The optional <GROUP-DISPLAY> should be switched off, unless:
- the LED functionality is required on release 1 SOPHO-SETs,
- Rank number dialling is required.

- 70 -
In case the <GROUP-DISPLAY> option is used, the amount of extensions that are located in the group
arrangements on DTX-I's/DLCU's is limited. Note that with option 102 extensive status messages can be
avoided.
For non-ACD groups at least one member must be assigned before the group arrangement will be set up.
For ACD groups it is possible to create a `no member' group.
If GROUP-PROPERTY 28 Observation Group is selected, the remaining parameters must be omitted. Also all
optional parameters in de additional parameters must be empty.

Change ACD Group Data 425 # !

CHACDD:<GROUP-DNR>;
The system will ask for additional parameters:

Enter ACD group threshold priority [<THRESHOLD-PRIORITY>] (def=0) : ;

Enter Full Threshold [<ACD-THRESHOLD>] (default=100) : ;
Enter Busy Threshold [<ACD-THRESHOLD>] (default=100) : ;
Enter Forced Absent Time [<ACD-TIME-PERIOD>] (default=infinite) : ;
Enter After Call Work Time [<ACD-TIME-PERIOD>] (default=0) : ;
Enter Call in Queue time [<ACD-TIME-PERIOD>] (default=infinite) : ;
Enter Pause tone [<ANN-PAUSE-TONE>] (default=Silence) : ;
Enter CallManager MIS logical device ACDxxy [<LDN>] (default=none) : ;
Enter Queue Position Algorithm [<Q-POS-ALGORITHM>] (def=absolute) : ;
Enter ACD group Queue Priority [<Q-PRIORITY>] (default=lowest) : ;

Note: To avoid system degradation, the value 0 for the 'forced absent time' should not be used
An LDN can be deleted by entering ‘-' as LDN.
Up to 100 ACD groups can be monitored by the same MIS output device at the same time.

Change ACD Group Day/Night Status 448 # !

CHGRDN:<GROUP-DNR>,<DAY/NIGHT>;

Delete a Member from a Group Arrangement 404 # !

DEGRPM:<GROUP-DNR>,<MEMBER-RANK>;

Display One or More Group Arrangements 180

DIGRPA:[<GROUP-DNR>s][,<UNIT>s/r];
Response for an ACD group:

PROP GROUP T-PR F-THR B-THR FA-TIM ACW-TIM CIQ-TIM PAUSE MAN-DEV
XX XXXXXX X XXXX XXXX XX XX XX XX XXXXXXX

PROP GROUP Q-POS Q-PR

XX XXXXXX X X

PROP GROUP DISPL SUPERV PARK EXT-PR MEMBER SW-ALL RANK LP PP

XX XXXXXX X XXXXXX XX XX XXXXXX X XX - -

Response for a non-ACD group:

PROP GROUP DISPL SUPERV PARK EXT-PR MEMBER SW-ALL RNK LP PP DEF PRES
XX XXXXXX X XXXXX XX XX XXXXX X XX XX XX XX XX

- 71 -
Display Group Member 405
DIGRPM:<MEMBER-BSP-ID>s;
Response:
MEMBER GROUP SW-ALL RANK LINE-P PARK-P DEFAULT PRESENT
2310-95 2500 1 0 No No Yes Yes
2310-95 2800 1 7 No No No No
2311-95 2500 1 1 No No No No

In the example above, member 2310 is a member of group 2500 and 2800, of which 2500 is its default
group.

Display ACD Group Status 64

DIGRPS:<GROUP-DNR>[,[<MEMBER-RANK>][,<DISPLAY-MODE>]];
This command can only be executed on groups with group property Automatic Call Distribution (ACD).

The status of ACD members is shown per 20 rank numbers: member rank 0 ... 19, 10 ... 29, 20 ... 39, 40 ...
59, 60 ... 79 and 80 ... 99. A particular range of members is displayed if the value of MEMBER-RANK falls
within that range.

In case pameter DISPLAY-MODE is omitted the OM command gives output continuously.

Response (if MEMBER-RANK points to the first range of rank numbers) :

Statistical Group info:

ACD AWT
xx xx

Real-time Member and Group info:

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 LGQ NCH NLC D
. + + - - * xx xx xx x

In the header(s) the rank numbers of the group members are given. Also the following abbreviations are
used:

ACD Average call duration in seconds;

AWT Average waiting time in seconds;
LGQ Length of Group-COB-Queue;
NCH Number of calls handled;
NLC Number of lost calls;
D Day/Night service (D/N).

The statistical group information is displayed every 15 minutes, while the real-time information is displayed
every time a change occurs in the status of the group members.
The status of the group members can be one of the following:

"." Idle
"+"
Busy/(When applicable, this is followed by the number of calls waiting in the Enquiry individual COB
queue, e.g. +1)
"*" Ringing
"-" Absent/After call work
"=" Not in service
"" Not assigned

- 72 -
Display Park/Line Position Status and Service Condition 219
DIPLPO:<GROUP-DNR/BSP-ID>s/r;
Response:
DNR-BSPT BSP-STATUS PRK1 PRK2 LINE-POS EXEC-LINE-POS
BSP EHWA COB STAT COB STAT COB
xxxxxx-xx xxxxx xxxxxxx xx xx xx xx xx xx xx

The BSP-STATUS is a combination of the BSP status and EHWA status. The following combinations are
possible:

BSP EHWA MEANING

free free BSP might be used for a call.
busy busy BSP is busy.
free busy BSP is free but EHWA is occupied by other BSP.
free not avail BSP is free but EHWA not available (set NIN, OUT etc.)
downloading - BSP is busy because terminal is downloading.
claimed - BSP is claimed (possible to be moved to other EHWA).
not usable not avail BSP is not usable (too many BSPs assigned to one EHWA / Hardwareless
DNR).

If the given DNR is a group DNR:

Response:
DNR COB PRK1 PRK2 PRK3 PRK4 PRK5 PRK6 PRK7 PRK8 PRK9
xxxx xx xx xx xx xx xx xx xx xx xx

Erase One or More Group Arrangements 179 # !

ERGRPA:<GROUP-DNR>s;
Note: The execution of this command can take some time, especially when an assigned device has its V.24
cable not connected (only for ACD-group).

- 73 -
27. HARDWARE CONFIGURATION
The commands for hardware configuration are used to change the projected configuration of a system.
This can be done to:
- Add resources to the system (boards, modules, links etc.);
- Replace existing boards.

27.1. MODULES, BOARDS AND CIRCUITS

Display Hardware Configuration 407

DICONF:<SHELF>[,[<BRD>][,<CRT>]];
Response :
A graphical representation of dependencies with directly related resources. An example of this command
for a PM board gives te following :
<DICONF:1011,1;
*
1011 17 - PM INS
|
1011 1 - BRD INS
|
PCT's ( 1011,1,x)
x = 0 1 2 3 4 5 6 etc. 31
EXECUTED

An other response example of DICONF, in case system option 189 “Use SIP Media” is set to TRUE is as
follows :
<DICONF:1011,17;
SIC (192.168.116.50:2950)
|
PMC/PSC INS
(1011,17)
|
+--- board (1011, x)
| x = 1 3 5 7 9 11 13 15 17
|
+--- internal ring tone
+--- logical channel
+--- routing tone
+--- null tone
+--- cob tone
+--- busy tone
+--- external ring tone
+--- testbus
EXECUTED

- 74 -
27.1.1. Shelves

Assign Shelf and Type 69 # !

ASSHLF:<SHELF>,<SHELF-TYPE>;
If an iS3010 or iS3030 shelf is assigned, the command will ask for the EHWA of the related lower or upper
shelf. Because these shelves always are physically located in the same cabinet, they have to be present
together.
It is possible to assign all kinds of virtual shelves (shelf type 16, 17 and 18) in any cabinet : it is not restricted
to the first cabinet anymore. The limitations of maximal 31 PMs per system remains and as there is always
a “real PM” required for the CPU assignment, maximal 30 virtual PMs can be projected.
For example, a maximum of 10 “virtual-SIP-shelves”, resulting in 10 x 512 = 5120 SIP ports. Boundary 174
(System limited number of cabinets) influences the location where virtual shelves can be assigned.

Delete Shelf 333 # !

DESHLF:<SHELF>;

Display Shelf 334

DISHLF:[<SHELF>];
When parameter <SHELF> is omitted, all shelves are displayed in brief format.
Response:
<DISHLF:12;

SHELF INFO :

SHELF BRD CRT TYPE

12 - - PM-1100-shelf

MODULES IN SHELF : BOARD POSITIONS

SHELF BRD CRT TYPE 12345678901234567890123456789
12 - 2 PM X X XXXXX X X X X

<DISHLF:;

SHELF INFO :

SHELF BRD CRT TYPE

12 - - PM-1100-shelf

12 - - PM-1100-shelf
13 - - Virtual-PM-shelf (iTMP)

14 - - Virtual-SMA-shelf (SMA/CCIS)

15 - - Virtual-SIP-shelf
16 - - Virtual-SIP-shelf

17 - - Virtual-SIP-shelf

18 - - Virtual-SIP-shelf

19 - - Virtual-SIP-shelf

23 - - Virtual-SMA-shelf (SMA/CCIS)

24 - - Virtual-SMA-shelf (SMA/CCIS)

- 75 -
27.1.2. Boards

Assign Board in Shelf 319 # !

ASBRDS: <SHELF>,<BRD>,<BOARD-TYPE>[-<BRD-STYP>][,<SIG-GROUP>
[,[<HW-TYPE>] [,<AS-PCTS>]]];
With this command the following boards can be assigned:
- CM boards like the CIE;
- SM boards like the CSN-BC or SNS);
- All PM boards, including the IAS;

BRD-STYP discriminates between boards with the same board type. This allows the OM command "INSTPK"
for installing different firmware packages on boards with equal board types.

Note: Parameter BRD-STYP has to be used in systems with a mixture of DTX-I and DTX-I(R) boards,
because those two boards have different incompatible firmware packages.
Parameter BRD-STYP has to be used in systems with a mixture of PMC-MC/HR and PMC-G boards,
because those two boards have different incompatible firmware packages.

If AS-PCTS is omitted all circuits of the boards will be automatically assigned. If HW-TYPE is omitted, 255 (no
test) is assumed. If the assigned board is a slave board, the command will ask for the EHWA of the
corresponding main board:

Additional parameters : <SHELF>,<BRD>;

SNS (Switching Network Slice) boards must be assigned in ascending order (SNS-n cannot be assigned
before SNS-n-1). When the SNS boards 0 and 1 are assigned, the CSG entry is assigned implicitly. When a
CIE board is assigned, the SSU (Switch and Sense Unit) entries and the BIM (Back-up and Interface Module)
are assigned implicitly.

Change the Subtype of a Board 315 # !

CHBDST:<SHELF>,<BRD>s/r[,<BRD-STYP>];
This command is used when the subtype of a board must be entered or changed, used in combination with
the download of peripheral boards.
If <BRD-STYP> is omitted, the current board sub-type is removed.

Delete Board from Shelf 324 # !

DEBRDS:<SHELF>,<BRD>;
With this command the following boards can be deleted:

- For a CPU3000 system, all types of PCT boards may be deleted. The CPU3000 and CSN-BC cannot be
deleted and for the PM boards: the PMC located in the same shelf as the CPU3000 cannot be deleted.
For PM boards located in another shelf as the one in which the CPU3000 is located, the corresponding
SM-PM or PM-PM link has to be deleted first.
- Before an SNS board in a CCS system may be deleted the corresponding links have to be deleted first.
For SNS-0 and SNS-1, the same must be done for the CRU entries. The CSG entries are deleted
automatically when the board is deleted. The SNS boards must be deleted in descending order.
- Before a CIE board may be deleted, the device ports and devices must be deleted first. The SSU entries
and the BIM circuit are deleted automatically when the CIE board is deleted.

- 76 -
A board can only be deleted if:
- the board and all the circuits on this board are in NIN;
- the board does not have any channels or ports in use (e.g. when a DTU-CC should be removed from the
system, the link in which the DTU-CC is used should be deleted first);
- the board does not have any other relations.

Change IP Signalling Data Group of a Board/PM Shelf 315 # !

CHIPSG:<SHELF>,<BRD>s/r[,<IP-SIG-GROUP>];
In case parameter <BRD> represents the PMC, then all PCT boards in that shelf will automatically get the
same IP-SIG-GROUP. When necessary, one or more boards/circuits can be given a different IP-SIG-GROUP,
by deleting the IP-SIG-GROUP from that particular board and re-assigned it with another IP-SIG-GROUP.
This might be necessary in case of (for example) a different Codec order setting or other IP-SIG-GROUP
parameters like FAX, Route Table to the Media Server, etc.
In case of one ISG board in the shelf, the media access code in the IP-SIG-GROUP(s) must be the same,
leading to the ISG board in the same shelf.

Example : <CHIPSG:11,17,B000;

in which 11 indicates the SHELF, 17 is the PMC board position. Then all PCT boards in shelf 11 have the
same IP-SIG-GROUP.
In case of more than one ISG board in the shelf, a number of PCT boards in the shelf can have IP-SIG-
GROUP e.g. B001, containing the media access code leading to ISG-1 and some other PCT boards in the
same shelf can have IP-SIG-GROUP e.g. B002, containing another media access code leading to ISG-2.
Example : <CHIPSG:11,1&&8,B001;
<CHIPSG:11,9&&16,B002;

Then the boards in positions 1 up to 8 will use ISG-1 and the boards in positions 9 up to 16 will use ISG-2.
If parameter <IP-SIG-GROUP> is omitted, the IP-SIG-GROUP is deleted from the board/PM shelf.
The IP-SIG-GROUP of the board can be displayed using command DIBRDS.

Display Boards in Shelf 335

DIBRDS:<SHELF>,<BRD>;
Response:
BOARD INFO:
SHELF BRD CRT TYPE SUBTYPE MAIN/SLAVE HW-TYPE SIG-GROUP IP-SIG-GROUP
xxxx xx - xx xx xxxx xx xxxx xxxx

RESOURCES ON BOARD:
SHELF BRD CRT RES-TYPE HW-TYPE SIG-GROUP
xxxx x x xxx xx xxxx
xxxx x x xxx xx xxxx

Display Equipment Identification 536 !

DIEQID:<SHELF>,<BRD>s/r[,[<CRT>s/r],<EQUIPMENT-ID>];
This command can be used to display :

- the 12NC and SB number (production serial number) of the most recently developed boards like the
ALC-G, DCC, DLX-U, DLX-L, CIE and CPU3000.
- to display the hardware version of a certain board :
DIEQID:<SHELF>,<BRD>s/r;
- to display the software/hardware version of a certain board :
DIEQID:<SHELF>,<BRD>s/r,,<EQUIPMENT-ID>;

- 77 -
- the (boot)software/hardware version of a certain terminal.
- to display the hardware version of a certain terminal :
DIEQID:<SHELF>,<BRD>s/r,<CRT>s/r;
- to display the (boot)software/hardware version of a certain terminal :
DIEQID:<SHELF>,<BRD>s/r,<CRT>s/r,<EQUIPMENT-ID>;

When DIEQID is done on an analogue card without "intelligence" on board, an error message is given. In
case a range of boards is specified and this range includes such an analogue card, that card is skipped and
not displayed. The hardware-type offers the possibility to display more than one 12NC/SB number per
board. This can be the case when a board contains a daughter board. The boards must be In Service.

The main software on the board can consist of an initial- and an actual package. In that case both packages
are displayed.
Identification of boards and terminals can be done, even while they are in use by call processing.
Response examples :

SHELF BRD HARDWARE-TYPE HW-12NC HW-SERIAL#

2011 3 MAIN 9562-203-27374 SBxxx00389
2011 5 MAIN 9562-158-54106 SBxxx00345
2011 7 DAUGHTER 9562-158-54200 SBxxx00463

SHELF BRD CRT SOFTWARE-TYPE MAIN-PACK SW-12NC PROJ-PACK

2011 11 11 ACTUAL 111.11.111 1234.123.12345 111.11.111
2011 11 11 INITIAL 111.11.111 1234.123.12345 111.11.111

SHELF BRD CRT BOOTPACK SW-12NC

2011 11 11 111.11.111 1234.123.12345

Display MAC-Address Information 599!

DIMACA:<MAC-ADDRESS>s[,<UNIT>];
The response is the EHWA of the LCT that is related to the given MAC-address on a virtual PCT board. Also
the related DNR's are displayed.
When UNIT is omitted, the OM command is executed for all units.
Response:
MAC-ADDRESS SHELF BRD CRT DNR
xxxxxxxxxxxx xxxx x x xxxx
xxxxxxxxxxxx xxxx x x xxxx

27.1.3. Circuits

Assign Peripheral Circuit to Board 369 # !

ASPCTB:<SHELF>,<BRD>,<CRT>s/r,<PCT-TYPE>[,[<SIG-GROUP>][,<HW-TYPE>]];
If HW-TYPE is omitted, 255 (no test) is assumed.

Change Peripheral Circuit Data of a Board 120 # !

CHPCTB:<SHELF>,<BRD>,<CRT>s/r,<SIG-GROUP>[,<HW-TYPE>][,<MAC-ADDRESS>];
When a PM board is assigned and PCTs are present on it, it is possible to change the sub SIG-GROUP and
HW-TYPE of these PCTs. Suppose SIG-GROUP is represented by 'aass', only the ss-part can be changed.
A MAC address can only be assigned to a virtual circuit. ASPCTB is not required/possible for these type of
circuits. System option NESYSOP 135 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.
To remove a MAC address, an empty MAC address must be specified.

- 78 -
Delete Peripheral Circuit from PM Board 370 # !
DEPCTB:<SHELF>,<BRD>,<CRT>s/r;
A circuit can only be deleted if:
- the circuit is in NIN;
- the circuit does not have any other relations.

Find PCTs by Type 73

FIPCTT:<PCT-TYPE>s/r[,<UNIT>];
Response: A list of all EHWA's with the required PCT type.

27.2. SWITCHING NETWORK TONE SOURCES

Display of the switching network tone sources can be done with the DICONF command on the EHWA of a
PM.

Assign Switching Network Tone Sources to a PM 331 # !

ASTONE:<SHELF>,<BRD>;

Delete Switching Network Tone Sources from a PM 332 # !

DETONE:<SHELF>,<BRD>;

27.3. CLOCK REFERENCE UNIT ENTRIES

Assign Clock Reference Unit Entry 350 # !

ASCRUE:<CRUE-SHELF>,<CRUE-BRD>,<CRUE-CRT>;
The CRUEs can reside on the following boards:

- on the SNS : top coax connector is circuit 48, bottom coax connector is circuit 49.
- on the CSN-BC : top coax connector is circuit 20, bottom coax connector is circuit 21.
- on the PMC-MC, projected as master (board-type 92) : top coax connector is circuit 20, bottom coax
connector is circuit 21.

Delete Clock Reference Unit Entry 351 # !

DECRUE:<CRUE-SHELF>,<CRUE-BRD>,<CRUE-CRT>;

Display Clock Reference Unit Entry 66

DICRUE:[<UNIT>];
Response:
SHELF BRD CRT CURRENT STATUS SELECTED
11 19 20 ABL-er
11 19 21 INS *

The * at the end of the output string gives the active clock reference unit entry (CRUE).

- 79 -
27.4. D-CHANNELS

ASBRVC can be used to assign virtual channels to DPNSS trunks or to set a relation between the D-channel
at the IPH or DTU and the trunks at the DTU.
For the boards with basic rate DPNSS (DTU-BA, DTX-I, DTU-VC) no D-channel is present, the command
assigns the virtual circuits to the traffic channels.
For the boards with primary rate DPNSS (DTU-PR/PU/PH), this command assigns the DTU board and the
virtual channels to the D-channel. For DASS, this command is only used for assigning the DTU board to the
D-channel (no virtual channels!).

Assign Board Relation and/or Virtual Channels 67

ASBRVC:<SHELF>,<BRD>,<CRT>s/r,<DTU-SHELF>,<DTUBRD>[,<NVCT>];
The parameters <SHELF>,<BRD>,<CRT> refer to the following:

- DTX-I EHWA of the PCT(s) to which the virtual circuit is related (if required).
- DTU-BA EHWA of the PCT(s) to which the virtual circuit is related (if required).
- DTU-VC EHWA of the PCT(s) to which the virtual circuit is related (if required).
- DTU-PH EHWA of the D-channel (circuit 16 on the DTU).
- DTU-PR/PU EHWA of the D-channel (circuit 1 of the IPH).

The parameter<NVCT>only applies to primary rate DPNSS (DTU-PR/PU/PH).

Example for a DTX-I, installed in shelf 1011, card slot 1:
ASBRVC:1011,1,2&&31,1011,1;

Example for a DTU-PH, installed in shelf 1011, card slot 1:

ASBRVC:1011,1,16,1011,1,30;
(The number of virtual circuits must be equal to the number of traffic channels on the board).

Example for a DTU-PR/PU, installed in shelf 1011, card slot 1. The IPH-B is installed in shelf 1011, card slot 3:
ASBRVC:1011,3,1,1011,1,30;
(The number of virtual circuits can be less than the number of traffic channels on the board)

Delete Board Relation and/or Virtual Channels 358 # !

DEBRVC:<SHELF>,<BRD>,<CRT>s/r;
Conditions are:
- Board must be in circuit condition NIN;
- D-Channel circuit must be in circuit condition NIN;
- No line-bundle relations must be present;
- No CRU entry must be assigned to the DTX or DTU.

With command DICONF you can display assigned board relations and/or virtual channels.

- 80 -
27.5. DEVICES AND LOGICAL DEVICE NAMES

27.5.1. Devices

Specific channels have a predefined function depending on the type of board and on the position of
switches on the board. This means that in certain situations there is a relation between the channel
number (circuit number) entered in the commands and the equipment type.
Consult the Maintenance Manual to find out this relation.

Assign Device 411 #

ASDEVC:<SHELF>,<BRD>,<CRT>,<LDN>,<EQUIPMENT-TYPE>;
This command assigns a device to an already (with command ASPORT) initialised port.
The logical device name will become the unique identifier of the equipment type. After assigning a device,
the circuit must be set to INS.
For CCS systems, the device is assigned to a circuit of the CIE board, but is physically connected to BIM.

Examples for a CPU3000 system:

ASPORT:11,18,21,1,0; : assign local BCS port on EHWA 11,18,21

ASDEVC:11,18,21,VDU020,20; : assign OM 1 keyboard device with LDN 'VDU020' on port
ASDEVC:11,18,21,VDU021,21; : assign OM 1 display device with LDN 'VDU021' on port
CHDEAU:VDU020,x,1; : set the required authority class x for VDU020
ASDEVC:11,18,21,TMSAPP,29; : assign SSM/SysManager services with LDN 'TMSAPP' on port
ASPORT:11,18,26,2; : assign logical port on EHWA 11,18,26
ASDEVC:11,18,26,SOLDSK,7; : assign a solid state disk device

Examples for a CCS system:

ASPORT:14,10,0,2; : assign logical port on EHWA 14,10,0

ASDEVC:14,10,0,VDU140,20; : assign OM 1 keyboard device with LDN 'VDU140' on port
ASDEVC:14,10,0,VDU141,21; : assign OM 1 display device with LDN 'VDU141' on port
CHDEAU:VDU140,x,1; : set the required authority class x for VDU140

Finish programming of the port at the Backup and Interface Module (BIM).

Note: OM keyboard and display are considered to be two separate devices. The command should be given
twice to assign a complete OM terminal.

Delete Device 442 #

DEDEVC:<LDN>;
It is not allowed to delete a device when it has more than one LDN assigned to it. Delete the additional
LDNs with command DELDNM first.

Activate/de-activate RBU 484 #

ACTRBU:<OFF/ON>;
First an RBU (Remote Backup Unit) must be created. An RBU is used as a (remote) alternative of an LBU.
The RBU is created as follows (assuming a V.24 port has been projected for remote maintenance):
ASDEVC:<SHELF>,<BRD>,<CRT>,RBUxx,26; (xx=unit)
Then the RBU can be (de)activated with the ACTRBU command.

- 81 -
Display Device Characteristics 81
DICHAR:<SHELF>,[<BRD>s/r],<CRT>s/r;
Response:
SHELF: BRD CRT: Logical Device Name: Equipment type:
xxxx xx xx xxxxxx xx
Prop: Gen: Rec.size: Open files: Conc.comm: Baudrate:
xxxxxx xx xxxxx xxx xx xxxx
- NON STORAGE CHARACTERISTICS -
Virutal line lenghth: Cursor (up, down, left, right, home & clear)
: xxxxxx x x x x x x
: xxxxxx : xxxxxx
: xxxxxx : xxxxxx

See display parameters Prop. and Gen. for more information about this response.
When the EHWA of the CM module is given, all devices of that unit are displayed using the first line of the
normal output only. Note that all assigned devices will be displayed. Devices assigned in ‘overlay' will have
the same equipment type as the ‘original' device.

Display Device Characteristics 421

DIDEVC:<LDN>;
Response:
LOGICAL DEVICE NAME EQUIPMENT TYPE
XXXXXX XX
SHELF BRD CRT PROP GEN REC.SIZE OPEN FILES CONC.COMM:
xxxx xx xx xxxxxx xx xxx xx x
- NON STORAGE CHARACTERISTICS - KEYBOARD
Line lenghth cursor: (up, down, left, right, home & clear)
xx x x x x x x
Free space (kbytes) xxxxxx
Free space (kbytes) xxxxxx

See appendix B. PARAMETERS for more information about display parameters Prop and Gen.
Note that all assigned devices will be displayed. Devices assigned in ‘overlay' will have the same equipment
type as the ‘original' device.

Assign (V.24) Port 417

ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>[,<CONNECTIONTYPE>];
This command selects the required port and communication protocol for an application that wants to
communicate with a device. If the BCS communication protocol is chosen, the optional parameter
'connection-type' determines whether remote communication with modems is needed.
For CCS systems: use ASPORT to assign the port number, which physically resides on the BIM, to the CIE.

Change Baudrate on V.24 Port 419

CHPORT:<SHELF>,<BRD>,<CRT>s/r,<BAUDRATE>;
This command changes the baudrate for the port on the given hardware address.

Delete (V.24) Port 418

DEPORT:<SHELF>,<BRD>,<CRT>;
This command deletes the port characteristics that have been established by commands ASPORT and
CHPORT. All devices that have been assigned on this port must be deleted first, otherwise an error is
reported.
For a CCS system, the last OM port can not be deleted.

- 82 -
Display Port Characteristics 420
DIPORT:<SHELF>,<BRD>,<CRT>s/r;
Response:
SHELF BRD CRT PROTOCOL TYPE CONNECTION TYPE BAUDRATE
xxxx xx xx x x xx

LOGICAL DEVICE NAMES

xxxxxx
xxxxxx

The connection type is only shown if protocol type is BCS.

Change Device Application 471

CHDEVA:[<APPLICATION>[,<MINIMUM-VERSION>,<MAXIMUMVERSION>]];
Response:

APPLICATION VERSION : 3

An application (like the CallManager MIS) can use this OM command to agree with the ISPBX upon the
version. By this OM command, it sends it's MINIMUM-VERSION and MAXIMUM-VERSION. As a result of this,
the ISPBX will set for the highest common version of the application and of the ISPBX. This OM command
must be executed per session.
If MINIMUM-VERSION and MAXIMUM-VERSION are omitted, the ISPBX will set for the highest version that
it can support.

27.5.2. Logical Device Names

Assign Logical Device Name 61 #

ASLDNM:[<LDN1>],<LDN2>[,<UNIT>];
The command ASLDNM can be used after using the ASDEVC command, to attach an additional LDN to the
device on the EHWA that was assigned with ASDEVC.

LDN1 must be an existing LDN and LDN2 is the LDN to assign.

Be very careful with logical device names LBU, DBU and CBU.

Re-assign an LDN in the network as follows: leave LDN1 out, enter the LDN to be reassigned in LDN2 and
enter the unit number where the LDN resides.

Delete Logical Device Name 62 #

DELDNM:<LDN>;
A device may have more than one LDN assigned to it. This command will not delete the last LDN : see
DEDEVC to delete the last LDN.
If LDN is CBU, this command will be executed when journal updating is OFF.
For a CCS system, if LDN is VDU, LBU, DBU or FXAL, the delete action is not allowed.

WARNING: Do not delete the CBU, unless the CBU must be moved!

- 83 -
27.6. LINKS

Assign Link 56 #
ASLINK:<SHELF>,<BRD>,<CRT>,<LINK-TYPE>;

• LINK-TYPE 2, SM-PM controllable.

Additional parameters:<SHELF>,<BRD>,<SEQUENCE-NO>;
Enter the PM EHWA and the sequence number (0 or 1 for PM2500 / 0 or 6 for PM1100).

• LINK-TYPE 3, SM-PM not controllable.

Additional parameters:<SHELF>,<BRD>,<SEQUENCE-NO>;
Enter the PM EHWA and the sequence number (0 for PM2500 / 1 … 5, 7 for PM1100).

• LINK-TYPE 4, SM-RPM controllable.

Additional parameters:<SHELF>,<BRD>;
<SHELF>,<BRD>,<SEQUENCE-NO>;
Enter the Local DTU EHWA, the Remote DTU EHWA and the sequence number (0 or 1 for CCS systems,
and 0 only for CPU3000)

• LINK-TYPE 5, SM-RPM not controllable.

Additional parameters:<SHELF>,<BRD>;
<SHELF>,<BRD>,<SEQUENCE-NO>;
Enter the Local DTU EHWA, the Remote DTU EHWA and the sequence number of the link (0 … 3).

• LINK-TYPE 6, SM-IU controllable.

Additional parameters:<SHELF>,<BRD>,<SEQUENCE-NO>,<UNIT>;
Enter the DTU EHWA, the sequence number (0 or 1) and the destination unit.

• LINK-TYPE 7, SM-IU not controllable.

Additional parameters:<SHELF>,<BRD>,<SEQUENCE-NO>,<UNIT>;
Enter the DTU EHWA, the sequence number (0 … 7) and the destination unit.

• LINK-TYPE 10, PM-PM (CPU3000 only).

Additional parameters:<SHELF>,<BRD>;
Enter the PMC EHWA of the opposite end.

• LINK-TYPE 11, SM-PM (CPU3000 only).

Additional parameters:<SHELF>,<BRD>;
Enter the PMC EHWA.
Shelf, board and circuit refer to the switching module port, which is a CSN-BC, PMC-MCMASTER or an
SNS. To a PMC-MC board two links must be connected.

Delete Link 57 #
DELINK:<SHELF>,<BRD>,<CRT>;
Specify the hardware address of the switching network link to be deleted. It is not possible to delete the
links between the CSN and the PMC-Primary. A link can only be deleted if:
- The link is in NIN;
- For links to a RPM or another unit the DTU-CC should be in NIN;
- The destination PMC is in NIN;
- The link with the control channel may not be deleted until all not-controllable links to the same
destination have been deleted.

- 84 -
Display Link Data 58
DILINK:<SHELF>[,[<BRD>,<CRT>][,<LINK-TYPE>]];
If the board and circuit number are specified, no type of link may be entered. If board and circuit are
omitted the link type may be given. If the link type is omitted all link types are displayed.
Response:
<DILINK:1014;
EHWA LINK TYPE OF LINK EHWA DEST EHWA LDTU EHWA RDTU SIDE SEQ UNIT
1014 5 4 IU-control 1014 13 0 1014 13 - - - - - 0 2
1014 5 5 IU-control 1014 11 0 1014 11 - - - - - 0 3
1014 6 4 IU-control 1014 15 0 1014 15 - - - - - 1 4

- 85 -
28. HOT LINE
These commands are used to assign and delete the FCM Hot Line to a BSP-ID. If a BSP-ID gets this facility
also the destination of the hot line is entered.
There are two kinds of hot line:

- Delayed hot line.

If the handset is lifted the system waits a pre-determined time before the connection to the destination
is made. This gives the user the possibility to dial another BSP-ID.

- Non-delayed.
Immediately after the handset has been lifted the connection to the destination is made.

Change Hot Line 122 # !

CHHOTL:<ORIG-BSP-ID>s/r[,<DEST-NUMBER>,<DELAY>,<POST-DIAL>,<TRFC>];
If only the originator BSP-ID is entered the hot line relation of the originator will be erased. Series/range
can only be used when erasing.

Display Hot Line 123

DIHOTL:<ORIG-BSP-ID>s/r;
Response:
ORIGINATOR DESTINATION DELAYED POSTDIALLING TRAFFIC-CLASS
xxxxxx xxxxxxxxxxxx x x x

- 86 -
29. IABD AND LENR FACILITY
These commands are used to assign and delete the FCM for Individual Abbreviated Dialling (IABD) and Last
External Number Repetition (LENR) to a DNR.

Assign IABD and LENR Facility 244 # !

ASIABD:<DNR>s/r;

Erase IABD and LENR Facility 245 # !

ERIABD:<DNR>s/r;

Change IABD or LENR 303 # !

CHIABD:<DNR>s/r[,[<IABD-NO>][,<DEST-NUMBER>]];
This command assigns or erases individual abbreviated numbers. The DNR must have the facility LENR/IABD
assigned by ASIABD.
For LENR omit the parameter <IABD-NO>.The DNR user can then call the destination number by dialling
the code for LENR only.
Any external number, dialled at the extension after a number has been entered by CHIABD will be
overwritten.
For IABD enter all parameters. The DNR user can then call the destination number by dialing the
abbreviated dialling prefix followed by the number defined by IABD-NO.
Erase all IABD numbers by omitting [,[<IABD-NO>][,<DEST-NUMBER>]] or erase a specific IABD
number by omitting [,<DEST-NUMBER>].

Display IABD or LENR 317 # !

DIIABD:<DNR>s/r[,<IABD-NO>];
This command shows the LENR/IABD information of a DNR. If <IABD-NO> is omitted, all LENR/IABD
information of a DNR is given.
Response:
DNR IABD-NO DEST
2400 -- 0030740000
2400 00 0030740001
2400 01 0030740002
2400 90 0030740003

- 87 -
30. IBSC - BSPT RELATIONS
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. 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.

Once a BSPT is created, the definition of a BSPT set can be changed using command CHBSPT. The sets may
be completely or partly overlapping.

The BSPTs 20 ... 93 can be changed by command CHBSPT. Since SIP@Net 5.1 it is also possible to change
BSPT 94 ... 98. This change is made because new gateway products often use IBSC 2 (3.1 kHz Audio) and this
is not included in the default voice BSPT 95 and 97.

Create BSPT Definition 78 # !

CRBSPT:<BSPT>;
Additional parameter:[<IBSC>];

The BSPT to be entered in this command ranges from 20 ... 93.

Enter all IBSCs belonging to the BSPT. Exit with a single semicolon on a line.
Once a BSPT is created, it can be changed using command CHBSPT.

Change BSPT Definition 220 !

CHBSPT:<BSPT>;
The command will ask a number of times for the additional parameter IBSC.

Display BSPT Definition 79

DIBSPT:<BSPT>s/r;
For each BSPT (0 ... 98) the list of IBSCs contained are given:
Response:
BSPT IBSC
xxx xxxxxxxxxxx
xxx xxxxxxxxxxx

- 88 -
31. INCOMING CALL SCREENING (INTERNAL/EXTERNAL)
Incoming Call Screening, as introduced in SIP@Net 5.0.5, allows only specific external parties to make a DDI
call to a specific DNR (extension or group number).

Since SIP@Net 5.3.1 this Incoming Call Screening functionality is expanded that it can also be used for
internal calls, but only when system option NESYSOP 212 (Access Lists Applicable for Internal Calls) is set to
"TRUE".
To this end, an Access List has to be assigned to one (or more) DNR(s). This Access List contains only those
internal and external numbers (based on their CLI) that are allowed to make a (DDI) call to that specific
extension that has an Access List assigned. The CLI in the Access List can be a complete number or a
number block. The "allowance" to make a (DDI) call to an extension is also known as "whitelisting".
The Access List assigned to the extension or group number is checked under the next preconditions :
- a DDI call is made via an ISDN, SIP, QSIG or MFC route, AND
- a CLI is received, AND
- the route has the incoming option "DDI barred check on incoming calls" set to "1".

In case of an incoming DPNSS or CCIS call, the Access List is checked :

- when the call into the private network is made via an ISDN, SIP, QSIG or MFC route, AND
- a CLI is received, AND
- the DPNSS or CCIS route has the incoming option "DDI barred check on incoming calls" set to "1".

Since SIP@Net 6.3 the Incoming Call Screening functionality based on "whitelisting" is expanded to allow
"blacklisting" as well. Whether the complete Access list is a "whitelist" or a "blacklist" is determined by the
first entry specified in the list (using parameter CLI-ACCESS):
Furthermore, since SIP@Net 6.3 it is possible to assign an Access list to a route, using OM command CHRTCI.

Assign a Number (CLI) to an Access List 628 # !

ASACLI: <ACCESS-LIST-ID>,<CALLING-LINE-ID>[,[<CLI-TYPE>]
[,<CLI-ACCESS>]];
Parameter <CALLING-LINE-ID> can be a unique number or a number block.
Parameter <CLI-TYPE> indicates whether the CLI represents an external or internal party : when
omitted, the CLI represents an external party.
Parameter <CLI-ACCESS> indicates whether the complete list is a "whitelist" (PERMIT) or a "blacklist"
(DENY).
An empty Access-list is considered as being not assigned to a DNR or route.
Anonymous Calls, empty CLI or presentation restricted calls can be blocked using a Deny-entry of 20 stars.
When an internal CLI is assigned and system option NESYSOP 212 is "FALSE" then a message is given :

WARNING: System option 212 disables access list for internal calls.

Change Access List of a BSP-ID 631 # !

CHDNRA:<BSP-ID>s/r[,<ACCESS-LIST-ID>];
When ACCESS-LIST-ID is omitted, the list is removed from a BSP-ID.

TIP : For simplicity reasons, the ACCESS-LIST-ID can be the same as the DNR. But keep in mind that the
highest possible ACCESS-LIST-ID number is 65534 : this is one less than the maximum value of
boundary 446.

- 89 -
Display the Contents of an Access List 630
DIACLI:[<ACCESS-LIST-ID>s/r];
When an internal CLI is assigned and system option NESYSOP 212 is "FALSE" then a message is given :

WARNING: System option 212 disables access list for internal calls.

Response example :
<DIACLI:;
ACCESS-LIST-ID CALLING-LINE-ID CLI-TYPE CLI-ACCESS

1 11 Internal Permit
1 1300 Internal Permit
1 15 Internal Permit
1 035689 External Permit
1 5309 External Permit
2 020689 External Deny
2 040511 External Deny
2 ******************** External Deny

Display BSP-ID - Access List Relation 632

DIDNRA:<BSP-ID>s/r,[<ACCESS-LIST-ID>];
- Display the Access List ID that is assigned to a BSP-ID :
DIDNRA:<BSP-ID>s/r;
- Display all BSP-IDs to which an Access List is assigned :
DIDNRA:,<ACCESS-LIST-ID>;
- Display BSP-IDs that have no Access List assigned :
DIDNRA:,;

Response example :
<DIDNRA:2510&&2946;
BSP-ID ACCESS-LIST-ID
2510-95 0
2812-95 1
2945-95 2
2946-95 -

Erase a Number (CLI) from an Access List 629 # !

ERACLI:<ACCESS-LIST-ID>[,<CALLING-LINE-ID>[,<CLI-TYPE>]];
In case only the <ACCESS-LIST-ID> parameter is entered, then all CLIs are removed from the Access
List.

- 90 -
32. INITIALISE DISK
This command is used to format the back-up device.

Initialise Disk 289

INIDSK:<LDN>;
This command will occupy the VDU until the back-up device is formatted.
Response:
Password:
WARNING: THE CONTENTS OF THE FEPROM ON CPU3000 WILL BE LOST!

- 91 -
33. INTEGRATED ANNOUNCEMENT SERVER (IAS)/MUSIC ON HOLD (MOH)
33.1. INTEGRATED ANNOUNCEMENT SERVER (IAS)

If an Integrated Announcement Server (IAS) is connected to the unit, an announcement can be given to
incoming calls.

Change Announcement Information 318 # !

CHANNO:<ANN-SELECTION>[,[<ANN-NO>][,<SHELF>,<BRD>,<CRT>]];
If <ANN-NO> is omitted, the announcement message is removed.
For ANN-SELECTION 6: omit <ANN-NO> if only dynamic announcements are needed.

The command will ask for additional parameters:

• ANN-SELECTION is 0: DDI fail calls

Enter assistance group number : [<ASSIST-GROUP>];
Enter encountered DDI fail situation: : [<ANN-DDI-FAIL>];

• ANN-SELECTION is 1: Successful DDI calls

Enter assistance group number : [<ASSIST-GROUP>];

• ANN-SELECTION is 2: Non-DDI calls

(includes PLE, INE, MCNE, SCNE and CANS)
Enter assistance group number : [<ASSIST-GROUP>];

• ANN-SELECTION is 3: Calls to operator A-queue

Enter assistance group number : [<ASSIST-GROUP>];
Enter A-queue: : [<A-QUEUE>];

• ANN-SELECTION is 4: Station calls for ACD group

Enter ACD group DNR : [<GROUP-DNR>];
Enter 'First announcement delay time': : <ACD-TIME-PERIOD>;

• ANN-SELECTION is 5: Night announcement for ACD group

Enter ACD group DNR : [<GROUP-DNR>];
Enter 'First announcement delay time': : <ACD-TIME-PERIOD>;

• ANN-SELECTION is 6: Delay message for ACD group

Enter ACD group DNR : [<GROUP-DNR>];
Enter 'Delay message pre-time' : <ACD-TIME-PERIOD>;
Enter 'Delay message repeat-time' : <ACD-TIME-PERIOD>;
Enter 'ANN-NO for QUEUE POSITION i' : <ANN-NO>;

(This is asked up to 16 times)

• ANN-SELECTION is 7: Music On Hold

The EHWA (<SHELF>,<BRD>,<CRT>) is optional, it corresponds to the (specific) IAS circuit.
When <ANN-NO> is omitted in the command, the relation with the EHWA is deleted.
To activate announcement changes, the command SETOUT and SETINS must be given.

Note: Each change of the 'first announcement delay time' of either announcement selection 4 or 5,
overwrites the existing value of either selection.

- 92 -
Display Announcement Information 392
DIANNO:<SELECT-ANNOUNCEMENT-DATA>[,<UNIT>sr];
Depending on the selection made, the system will ask for additional parameters.

In case of an Assistance Group:

Enter assistance group number : [<ASSIST-GROUP>];
Response:
DDI-FAIL: BUSY DIAL-TIME-OUT NBR-UNOBT OTHER-FAIL DDI SUCC NON DDI
xx xx xx xx xx xx
A-QUEUES: A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 A12 A13 A14 A15 A16
x x x x x x x x x x x x x x x x x x x

In case of an ACD group:

Enter ACD group DNR: : <GROUP-DNR>;
When the unit number is omitted, the command is executed system wide.
Response:
STATION CALLS ANN-NO PRE-TIME
xx xx
NIGHT ANNOUNCEMENT ANN-NO PRE-TIME
xx xx
DELAY MESSAGE ANN-NO PRE-TIME REPEAT-TIME
xx xx xx
QUEUE-POS ANN-NO
x xx

In case of Music On Hold:

Response:
MUSIC ON HOLD ANN-NO EHWA relation
xx xxxx xx xx

Note: Each change of the 'first announcement delay time' of either announcement selection 4 or 5,
overwrites the existing value of either selection.

33.2. MUSIC ON HOLD (MOH)

The CV of the party that initiates the on hold situation, determines the MOH to be given. To this end OM
command CHCVMH can be used to create/change/delete a relation between the CV and the EHWA of the
MOH circuit (IASA or ALC).
The CV mechanism (often in combination with different Analysis Groups and Assistance Groups) is used to
share one ISPBX system by different companies : this is known as 'multi-user' or 'multi-tenant'.
Using the CV-MOH relation enables different companies to give their 'own' Music On Hold.

Change MOH-CV Relation 589 # !

CHCVMH:<CV>[,[<SHELF>],[<BRD>],[<CRT>][,<UNIT>]];
Parameters <SHELF>,<BRD>,<CRT> represents the EHWA of the MOH resource (IASA or ALC).
When the EHWA is omitted the relation is deleted; UNIT may be omitted in a single unit system.
To each CV only one MOH resource can be allocated.
One MOH resource can be allocated to a number of CV's.

Display MOH-CV Relation 590 !

DICVMH:[<CV>s/r][,<UNIT>];
When both parameters are omitted, all relations are shown.

- 93 -
34. INTER UNIT NETWORKING
Note: Inter unit networking is only available on iS3070 and iS3090 systems.

34.1. INTER UNIT ROUTING

Change Route Relation 271 #

CHRORE:<UNIT>,<ROUTE-ALTERN>;
The command asks for additional parameters:
[<ORIG-UNIT>,<FAR-DEST>[,<IU-ROUTE>]]:;

If the inter unit route number is omitted the route relation is erased. If all additional parameters are
omitted the command is stopped. If the alternate route is entered as routing alternative the originator unit
must equal the unit in which the route relation must be changed.

Change Unit Relation 272 #

CHUNRE:<UNIT>,<ROUTE-ALTERN>;
The command asks for additional unit parameters:
[<ORIG-UNIT>,<FAR-DEST>[,<NEAR-DEST>]]:;

If the near destination is omitted the unit relation is erased. If all additional parameters are omitted the
command is stopped. If the alternate route is entered as routing alternative, the originator unit must equal
the unit in which the route relation must be changed.

Display Unit and Route Relations 273

DIURRE:<UNIT>,<ROUTE-ALTERN>,<ORIG-UNIT>s/r;
Response:
ROUTING ORIGINATOR FAR NEAR INTERUNIT
ALTERNATIVE UNIT DESTINATION DESTINATION ROUTE
xxx xxx xxx xxx xxx

34.2. INTER UNIT TRUNK TRAFFIC

Assign Bundle to Interunit Route 265 # !

ASIBND:<BUNDLE>,<ROUTE>,<UNIT>;

Assign Line to Interunit Bundle 267 # !

ASILIN:<SHELF>,<BRD>,<CRT>,<BUNDLE>;

Change Inter Unit Bundle Characteristics 264 # !

CHIBNC:<BUNDLE>,<BUNDLE-DIR>,<UNIT>;

Delete Bundle from Inter Unit Route 266 # !

DEIBND:<BUNDLE>,<UNIT>;

- 94 -
Delete Line from Inter Unit Bundle 268 # !
DEILIN:<SHELF>,<BRD>,<CRT>;

Display Inter Unit Bundle Data 270

DIIBND:<BUNDLE>,<UNIT>;
Response:
BUNDLE ROUTE UNIT DIR
xx xx xx x
SEQ SHELF BRD CRT
xx xxxxx xx xx

Display Inter Unit Route Data 269

DIIROU:<ROUTE>,<UNIT>;
Response:
ROUTE UNIT SEQ BUNDLE DIR
xx xx xx xx xx

- 95 -
35. IP CONFIGURATION AND FTP SERVER
35.1. IP CONFIGURATION

TCP/IP is used by various applications over Ethernet. As the Ethernet port is physically shared with the last
V.24 port of the VIC3000, Ethernet is only available when the status of the last V.24 port is out of service.

Display TCP/IP Configuration 537 !

DITCPC:<SHELF>,<BRD>[,<CRT>];
This command shows the IP-address, netmask, default gateway address and the Ethernet address for the
CPU3000/ISS/ISS-2/ISS-3, the CIE and the ISG board(s).
See response examples below.

Output for the CPU

<DITCPC:11,18;
ITEM VALUE
Physical Address 00-50-56-06-91-50
Application IPv4 Address 192.168.9.201
Subnet Mask 255.255.255.0
Default Gateway 192.168.9.1
Application IPv6 Address 2001:aaaa:0:22:9d5a:6660:4d5d:8102

Output for the PMC-IP supporting both IPv4 and IPv6

<DITCPC:11,20;
ITEM VALUE
Physical Address 08-00-6F-82-A1-9A
IPv4 IP Address 192.168.160.19
Subnet Mask 255.255.255.0
Default Gateway 192.168.9.1
IPv6 IP Address 2001:aaaa:0:22:9d5a:6660:4d5d:8103

In case the PMC-IP has no support for IPv4 the content of the IPv4 related information will be left empty.
The same holds for the content of IPv6 related information on the PMC-IP that has no support for IPv6.

Output for the PMC-IP supporting only IPv6

<DITCPC:11,20;
ITEM VALUE
Physical Address 08-00-6F-82-A1-9A
IPv4 IP Addre -
Subnet Mas -
Defaultteway -
IPv6 Address 2001:aaaa:0:22:9d5a:6660:4d5d:8103

Check if System is reachable through IP Network 564

EXPING:[<SHELF>],[<BRD>],<IP-ADDRESS>;
Parameters SHELF and BOARD are the EHWA of the CPU3000 or the CIE board (with firmware package
FA1000.601 onwards) of the system where the command is executed. In case of the CPU3000 board, the
EHWA may be omitted.

Parameters SHELF and BOARD can be omitted only as the pair.

When the EHWA is correct, the ping is executed.
If the EHWA does exist, but the board is not a CIE-2 or CPU3000 board, the error message 'EHWA has
incorrect type' is given.

- 96 -
Parameter IP-ADDRESS is the IP address of the destination system. It must be entered in IP-address format,
for example 192.168.1.128.

Possible output:
• Output in case the destination is reachable:
- Host is alive.
• Output in case the destination is not reachable (if the response is not obtained within 5 secs):
- No answer (timed out).
• Outputs in case the system is not able to execute the request:
- Temporary not able to execute ping (try again later).
- Unable to send ping request due to internal error! (retry or execute warmstart).

35.2. FTP SERVER (CPU3000 only)

The Ethernet interface can be used as a carrier for the FTP protocol. For this purpose FTP client software
must be installed on the SMPC. This makes it possible to up- and download files to and from the LBU/DBU
of the CPU3000.
During start up of the system the FTP server task is started when a username/password combination is
projected (CHIPUS command). When no username/password combination is projected on start up of the
system the FTP server task is started but its execution is suspended. The FTP server can be resumed and
suspended with an OM command STFTPS.
An active FTP session can only be stopped from the SMPC (client).

Note that on the ISS/ISS-2/ISS-3 no FTP server is default available. In case one want to use FTP on the
CPU400, one have to install a commonly available FTP server.

Change IP User 548 !

CHIPUS:<IP-APPLICATION>;

Enter username : <USERNAME>;

Enter password : <PASSWORD>;
Confirmation: : <PASSWORD>;

When the username already exists the old password is changed to the new password.

Delete IP User 547 !

DEIPUS:<IP-APPLICATION>;
Enter username : <USERNAME>;

Display IP User 549 !

DIIPUS:[<IP-APPLICATION>;]
This will display all available usernames in afphabetic order, the application (FTP) and if the username is still
usable.

- 97 -
Display Current IP Sessions 550 !
DIIPSE:[<IP-APPLICATION>][,<SHELF>,<BRD>][,<IP-REPORT-TYPE>];
This will display the various current IP sessions.
For a CPU3000 system the <SHELF>,<BRD> parameters may be omitted and then the IP sessions for the
CPU3000 board are displayed.
For a CCS system the <SHELF>,<BRD> parameters indicates the CIE for which the IP sessions are
displayed.

If <IP-APPLICATION> is omitted then the sessions of all IP-Applications are displayed.

If <IP-REPORT-TYPE> is omitted then all IP related parameters are displayed.

Below some examples of the DIIPSE output.

<DIIPSE:;
SOCKET APPLICATION PORT IP ADDRESS PORT

6 OM 23 192.168.9.201 0
7 OM 23 fd01:aaaa:0:22:38a7:bf2a:c35c:12f7 0
1 FTP 21 0.0.0.0 0
2 CSTA 2555 192.168.9.200 0
9 FDCR 2599 192.168.9.200 0
15 SIP 2610 192.168.9.201 0
16 SIP 2610 fd01:aaaa:0:22:38a7:bf2a:c35c:12f7 0
EXECUTED

<DIIPSE:,,,2;
SOCKET APPLICATION STATUS USERNAME

6 OM LISTEN -
7 OM ESTABLISH -
1 FTP LISTEN -
2 CSTA LISTEN -
9 FDCR LISTEN -
15 SIP LISTEN -
16 SIP ESTABLISH -
EXECUTED

Close IP Sessions 352

DEIPSE:<SOCKET>[,<SHELF>,<BRD>];
With this command it is possible to close a specific established TCP connection towards for example a CSTA
application, OM over IP or FDCR over IP. Note that it is not possible to close a server socket : this is a socket
in the state LISTEN. Such a socket can be closed using second line command SPSRVC.
Parameter SOCKET specifies the internal Id of a TCP or UDP socket that should be closed.
This Id can be displayed with OM command DIIPSE, in column 'SOCKET'.
For CPU3000 systems, parameters <SHELF>,<BRD> may be omitted and then the TCP session for the
CPU3000 board will be aborted.
For CCS systems, parameters <SHELF>,<BRD> indicates the CIE for which the TCP session will be aborted.
On CCS systems the OM command DEIPSE also requires an update of the CIE package to release 100.10.02.

- 98 -
Start FTP Server 545 !
STFTPS:<SUSPEND/RESUME>[,<UNIT>];
This command will ask for a USERNAME/PASSWORD combination. After execution of this OM Command
the FTP server will be resumed. Within 1 minute an FTP session has to be started, otherwise the FTP server
is suspended again.
The USERNAME and PASSWORDS are programmed with CHIPUS.
From the iS3000 point of view, the authority class required to execute STFTPS is the only protection. Once
the FTP connection is established, the file protection levels (NARD) are not checked and also file version
management is not supported.
Note that when the last V.24 port is put into service, it means that the Ethernet interface is not available
anymore. As a consequence also the FTP server is not available. When in this situation the FTP server is
started with the OM command, it is rejected.

WARNING: TO AVOID FILE VERSION CONFLICTS IT IS ADVISED:

- TO CHECK THE FILE VERSION, BEFORE TRANSFERRING FILES.
- TO EXECUTE THE FTP SESSION ON THE DBU WHEN THE SYSTEM IS IN THE MAINTENANCE
MODE.

EXAMPLE
Execute DITCPC to read out the IP configuration items of the iS3000.
Create an FTP username and password :

CHIPUS:0;
Enter Username: Flintstone;
Enter password: *****; Note that the password "Wilma" will not be displayed.
Confirmation: *****;

Execute STFTPS to resume the FTP session:

STFTPS:1,1;

Now start the FTP client software.

Build up the FTP connection using the following values:

HOST TYPE : automatic

IP-ADDRESS : 192.168.1.12
USERNAME : Flintstone
PASSWORD : Wilma

Once the FTP connection is established, files can be transferred to and from the LBU/DBU of the CPU3000.

Note: When "DISK1" represents the LBU, "DISK2" represents the DBU.
When "DISK1" represents the DBU, "DISK2" represents the LBU.
Take care of this before transferring files.

- 99 -
35.3. CLIENT SERVICE PROFILES

SIP@Net can be hardened by using Client Service Profiles.

A profile as created by CHPROF is a set of services provided by SIP@Net, for example OM over IP, SIP, FDCR
over IP, iTMP, etc.
A profile can be granted to a PC/device by creating a relation between the profile and the interface IP
address of that PC/device, using OM command CHIPPR.
A profile can be granted to more than one PC/device. A PC/device can have only one profile (per IP address).
A PC can use a service provided by SIP@Net only if it is granted to its interface IP address.
The default profile (profile 0) grants services to all PCs/devices that have no profile. Therefore a hardened
SIP@Net server should have no (or very limited) services in the default profile 0.

REMARKS
1. PCs/devices that have a profile can only use the services of that profile, not the services of the default
profile.
2. SIP devices (SIP terminals, SIP DECT radios, SIP trunks, Media Servers) do not need a profile. These
devices connect to the SIP driver, not directly to SIP@Net service.
3. The SIP service must be granted to the devices running a SIP driver (e.g. the ISG board, the IPG on the
PMC-IP board or the local server).
4. A SIP@Net Server/ISS/ISS-2/ISS-3 system also needs a profile to use services. However, to prevent that
the engineer gets locked out completely, OM via a “telnet” session is always allowed on the local server.
5. The profile is checked only on establishment of a connection. Existing connections are not cleared if due
to CHPROF/CHIPPR a service is not granted anymore. This may be noticed first when SIP@Net Service or
the requesting device is restarted.

Change IP Address - Client Service Profile Relation 587 #

CHIPPR:<IP-ADDRESS>[,[<PROFILE-ID>][,[<UNIT>]]];
This command can be used to perform the following tasks, using the given parameter combinations :
- Assign an IP address - Client Service Profile relation :
CHIPPR:<IP-ADDRESS>,<PROFILE-ID>[,<UNIT>];
- Remove an IP address - Client Service Profile relation :
CHIPPR:<IP-ADDRESS>[,,<UNIT>];

Parameter UNIT may be omitted in a single unit system.

Display IP Address - Client Service Profile Relation(s) 588 !

DIIPPR:[<IP-ADDRESS>][,[<PROFILE-ID>][,[<UNIT>]]];
This command can be used to perform the following tasks, using the given parameter combinations :

- Show an IP address - client service profile relation :

DIIPPR:<IP-ADDRESS>[,,<UNIT>];
- Show all IP clients for a profile :
DIIPPR:,<PROFILE-ID>,[<UNIT>];
- Show all IP clients :
DIIPPR:[,,<UNIT>];

Parameter UNIT may be omitted in a single unit system.

If a PROFILE-ID is displayed between brackets, then the PROFILE-ID has not been specified. In that case, the
default profile will be used.

- 100 -
<DIIPPR:;
IP-ADDRESS PROF-ID
fd01:aaaa:0:22:9d5a:6660:4d5d:8102 1
192.168.001.196 1
EXECUTED

Change Client Service Profile 585 #

CHPROF:<PROFILE-ID>[,[<SERVICE>][,<ALLOWED>][,<LDN>][,[<UNIT>]]]]];
It is strongly recommended to create Client Service Profiles as a means to protect 'OM', 'SS', 'Simple
Alarming' and 'FDCR' from unauthorised use. The default-profile does not allow the services over IP. When
you want to use either service it is advised to create a new profile that does allow these services. The
command CHPROF can be used to perform the following tasks, using the given parameter combinations :

- Assign a service :
CHPROF:<PROFILE-ID>,<SERVICE>,1,<LDN>[,<UNIT>];
- Delete a service :
CHPROF:<PROFILE-ID>,<SERVICE>,0[,,<UNIT>];
- Delete a profile :
CHPROF:<PROFILE-ID>[,,,,<UNIT>];

Parameter UNIT may be omitted in a single unit system.

Display Client Service Profile(s) 586 !

DIPROF:[<PROFILE-ID>][,[<UNIT>]];
When both parameters are omitted, all profiles are shown. Parameter UNIT may be omitted in a single unit
system.

- 101 -
36. IP ENABLING / SIP
36.1. IP ENABLING FULL TMP / SIP SIGNALLING DATA

The data to be assigned to groups of terminals is mainly hardware oriented. Therefore the data is related to
the sub-signalling group of the circuit of the ErgoLine@Net terminal. Per sub-signalling group of the circuits
of ErgoLine@Net terminals the following data can be determined :

- VoIP data, like codec settings and gatekeeper address.

- Media access code, determining the routing of the media connection via a gateway.
- Language.

For a specific ErgoLine@Net terminal, the (sub-)signalling group and the MAC-address are assigned to a
circuit by means of CHPCTB.

This command is also used to define the signalling group(s) containing some characteristics, relevant for SIP
trunks and extensions.

Change IP Projecting Data For ErgoLine@Net Terminals 500 # !

CHIPPD:<IP-SIG-GROUP>,<IP-PROJ-DATA-TYPE>[,<IP-PROJ-DATA-VALUE>];
Parameter <IP-SIG-GROUP> can be :
- 0100 ... 01FE (hexadecimal) for IP enabling (iTMP) (check system boundary 47)
- B000 ... B0FE (hexadecimal) for SIP trunks/extensions (check system boundary 420)
The sub-signaling group can never be larger than the value of boundary 47 (or 420) – 1.

The IP-PROJ-DATA-TYPE can be 0 upto 11 :

- 0 is used in all situations
- 1, 2 and 3 are used for IP-enabling, CCIS over IP and IP Dect
- 4 up to 11 are used for SIP trunking and extensions

Depending on parameter 2 (IP-PROJ-DATA-TYPE), parameter 3 (IP-PROJDATA-VALUE) has a

different meaning as given as follows :

CHIPPD:<IP-SIG-GROUP>,0,<MEDIA ACCESS CODE>;

CHIPPD:<IP-SIG-GROUP>,1,<LANGUAGE>;
CHIPPD:<IP-SIG-GROUP>,2,<GATEKEEPER IP ADDRESS>
CHIPPD:<IP-SIG-GROUP>,3; (VoIP data)
Enter tag : for example QOSVoiceData;
Enter data : for example DSCP=0;
Enter data : for example UP=255; (repeat until ;)
CHIPPD:<IP-SIG-GROUP>,4,<CODEC>[[[,<CODEC>],<CODEC>],<CODEC>];
CHIPPD:<IP-SIG-GROUP>,5,<PAYLOAD>;
CHIPPD:<IP-SIG-GROUP>,6,<RFC2833>;
CHIPPD:<IP-SIG-GROUP>,7,<SRTP>[,[<CRYPTO>][,<AUTH>]];
CHIPPD:<IP-SIG-GROUP>,8,<FAX>;
CHIPPD:<IP-SIG-GROUP>,9,<ROUTE TABLE MEDIA SERVER>;
CHIPPD:<IP-SIG-GROUP>,10,<SESSION GUARDING TIMER>;
CHIPPD:<IP-SIG-GROUP>,11,<DISABLE PROGRESS TONES>;

- 102 -
Media Access Code (in case IP-PROJ-DATA-TYPE = 0)
A number of maximum 6 digits. This number, analysed in tree 0, must result in a trunk access code,
network access code or abbreviated number, leading to a trunk connected to the Gateway. When specified,
it overrules the (default) media access code as defined by BOUND 285. In case of an IMP, DPNSS or QSIG
network, the ErgoLine@Net terminal and the ISG or trunk to the gateway must be located in the same unit.
In case of SIP extensions, it is the media access code for SIP extensions.

Language (in case IP-PROJ-DATA-TYPE = 1)

0 = English 7 = Danish 14 = Hungarian *)

1 = Dutch 8 = Portuguese 15 = Romanian *)
2 = German 9 = Czech 16 = Serbian *)
3 = French 10 = Norwegian 17 = Croatian *)
4 = Spanish 11 = Catalan 18 = Slovak *)
5 = Italian 12 = Polish 19 = Russian *)
6 = Swedish 13 = Slovenian 20...255 = reserved.

*) Note that these languages are available in application package fec010v1.106 or higher. The preferred
language can also be selected locally on the terminal.

Gatekeeper (in case IP-PROJ-DATA-TYPE = 2)

This is the IP address of the Gatekeeper. In case of the ISG board, this IP address should be 0.0.0.0, meaning
"no Gatekeeper" is used. If no Gatekeeper is projected, the value of boundaries 386 ... 389 are used as
default for the concerned signalling group.

VoIP data (in case IP-PROJ-DATA-TYPE = 3)

In this case, the system will ask for the following additional parameter(s), for example :
Enter tag : QOSVoiceData;
Enter data : DSCP=0;
Enter data : UP=255;
Enter data : ;

This line is repeated until an empty string is entered. The tag and data entries are as described in the IP-
enabling Customer Engineer Manual. The tag is entered without the squared brackets [ ]. The maximum
length of a string is 20 characters. A string can not contain commas and semicolons. When another tag has
to be specified, this command must be executed once more.
The result of the given input in this example is :

MEANING
[QOSVoiceData] Quality Of Service
DSCP=0 Differentiated Services Code Point (0-63)
UP=255 User Priority (0-7), 255 = disabled

See also the response example of OM command DIIPPD.

The maximum number of ”text strings” (lines) for a tag is limited by LOBOUND 077. The data entered by
means of this command replaces the data stored with the same tag. In other words, if the tag is stored
already for this sub-signalling group, then the data is replaced. Entering a tag string and only an empty data
string clears the data for this tag. There is no validation of the tag and the data. In this way the VoIP data
can be downloaded without the CPU having thorough knowledge of the VoIP data.

- 103 -
REMARKS
If a tag is defined once and the data is downloaded in the terminal, the values can only be changed by
redefining the tag values.
Removing a tag by using CHIPPD (by entering the tag name without data) will only removed the tag-data
from the system memory. It will not reset the tag-data in the terminal. If one wants to use the default
values again, these default values must be entered in the VoIP-data (by using CHIPPD) or the terminal must
be rebooted. After entering the VoIP-data by using CHIPPD the data must be downloaded to the
ErgoLine@Net. The OM commands ACIPPD and DOWNLD perform this.

CODEC (in case IP-PROJ-DATA-TYPE = 4)

In case more than one codec is given the first codec is the preferred codec :
- 0 = G.711 uLaw
- 1 = G.711 ALaw
- 2 = G.729A (is compatible with G.729)
- 3 = G.729AB (G.729A with silence suppression)

Payload (in case IP-PROJ-DATA-TYPE = 5)

Payload can be 10, 20, 30 or 40 msecs.
Note that the 10 msecs payload is new in SIP@Net 5.0.

RFC2833 (in case IP-PROJ-DATA-TYPE = 6)

This indicates whether RFC2833 is used :
- 0 = do not use RFC2833
- 1 = use RFC2833 with payload type 96
- 96 ... 127= use RFC2833 with payload type 96 ... 127

SRTP (Secure RTP ) (in case IP-PROJ-DATA-TYPE = 7)

This specifies security items :

- SRTP : 0 = No, don't use SRTP

(default value since SIP@Net 5.0)
1 = Optional, use RTP or SRTP
(default value in previous SIP@Net releases)
2 = Preferred, use SRTP, also accept RTP
3 = Mandatory, only SRTP is allowed
- CRYPTO : 0 = AES_CM_128_HMAC_SHA1_80
1 = AES_CM_128_HMAC_SHA1_32
- AUTH : 0 = No
1 = Yes

FAX: Specifies how fax transmission is done (in case IP-PROJ-DATA-TYPE = 8)

This indicates how fax transmission is done:
- 0 = G.711 (Default)
- 1 = T.38
- 2 = Fax disabled

Route Table Media Server (in case IP-PROJ-DATA-TYPE = 9)

This indicates the Route Table number (0 ... 254).

- 104 -
Session Guarding Timer (in case IP-PROJ-DATA-TYPE = 10)
This parameter defines if session guarding is required or not (RFC 4028). In this case a timer has been added
that can be given :

- a value of 0 (no session guarding active).

- a value between 90 and 3600 seconds representing the keep-alive interval in seconds.
In RFC4028 this value is referred to as the session-expires header value. According to RFC4028 a value
smaller than 90 seconds is not allowed. This would also impose a higher load on the iS3000 and
therefore small values for this timer on CPU3000 and CCS are therefore not advised. As a rule of thumb
a value of 1800 seconds (also the default value according to RFC4028) is advised. Smaller values are
allowed on the SIP@Net Server and the ISS/ISS-2/ISS-3 platform.

Disable progress-tones (in case IP-PROJ-DATA-TYPE = 11)

This parameter defines whether a SIP response message is given instead of Progress Tone :
- 0 = No : Progress tone may be given to SIP extension.
- 1 = Yes : SIP Response instead of progress tone is given to SIP extension.

If a SIP extension has an IP Signalling Group for which “Disable progress-tones” has been set to 1, then a
call from this SIP extension will not be answered solely to give a progress tone. Instead, if appropriate, one
of the following SIP Response codes will be given :
"404=Not Found", "486=Busy Here" or "480=Temporarily Unavailable".

Display IP Projecting Data For ErgoLine@Net Terminals / SIP 502

DIIPPD:<IP-SIG-GROUP>s;
Response example :

<DIIPPD:0101;
SIG-GRP LANGUAGE ACCESS CODE GATEKEEPER CODECS PAYLOAD RFC2833
0103 0 75 0.0.0.0 - - -

VoIP DATA
[QOSVoiceData]
DSCP=0
UP=255
[Codecs]
Preferred1=G711aLaw

For SIP signalling groups :

<DIIPPD:B001;

SIG-GRP LANGUAGE ACCESS CODE GATEKEEPER CODECS PAYLOAD RFC2833 ROTA

B001 - 75 - 2 3 0 1 30 96 12

SRTP ENCRIPTION AUTHENTICATION FAX SESSION DISABLE-TONES

2 AES _CM_128_HMAC_SHA1_80 Yes 1 1800 -

VoIP DATA
-

Activate IP Projecting Data For ErgoLine@Net Terminals 501 # !

ACIPPD:;
This command is used to activate the changed signalling data for IP enabling. SIP signalling data does not
have to be activated. The data must be distributed in two stages: first to the iTMP-driver and then to the
concerned ErgoLine@Net terminals. Change of a Media Access Code is effective immediately.

- 105 -
The iTMP-driver receives the projecting data :
- on registration to the iS3000.
- by executing OM command ACIPPD.

ErgoLine@Net terminals receive the (changed) projecting data on registration to the iTMP-driver. This
means that after a change of data the concerned ErgoLine@Net terminals needs to be downloaded (in
order to put the change into effect) in one of the following ways :
- initiated from the ErgoLine@Net terminal;
- by executing OM command DOWNLD of the concerned DNR;
- by executing OM commands SETOUT and SETINS of the concerned circuit.
- by unplugging and plugging the ErgoLine@Net terminal.

Exceptions are the Media Access Code (this data is never sent to the ErgoLine@Net terminals; it is used in
the iS3000 locally) and the Currency (the iTMP-driver sends the currency to the ErgoLine@Net terminals
after a change). The data that is downloaded to the ErgoLine@Net terminals includes :

- Gatekeeper IP address
- Ring rhythms
- Currency
- Language
- VoIP data
- Function Key data.

36.2. SIP TRUNKING

Assign SIP Specific Data to SIP Route 600 # !

CHSIPD:<SIP-ROUTE>[,<POINT-CODE>];
This command is used to assign certain SIP related items, before the SIP trunk is taken into service. The
command will ask for the following additional parameters :

<ROUTE-NAME>
This parameter defines the user part of the URI, as it is supplied by the SIP provider the URI that is
applied for registrations is the combination of this parameter and the registrar name (OM
command CHSIPA) separated by an @ character. The length of the user name is limited to 78
characters, excluding the start and end quotes (since SIP@Net 5.1). The name may contain upper
and lower case letters and digits (separators and punctuations are not allowed : the formal
specification is given in RFC 2396 and contains a more complex format).
<LEASE-TIME>
This value specifies the proposed lease time for registration in minutes, ranging from 1 ... 9999.
After half the value, the iS3000 will refresh it's lease. In case it is left empty, a default of 60 is taken.
<PROT>
This parameter defines the SIP protocol used :
- "T" or "t" specifies that TCP needs to be applied whenever a SIP command is sent.
- "U" or "u" specifies that UDP needs to be applied whenever a SIP command is sent.
- "S" or "s" specifies that TLS needs to be applied whenever a SIP command is sent.
If it is left empty when setting data on a new route then UDP is applied.
<USERNAME>
This parameter defines the username that is applied during the registration process. It's
specification is identical to the <ROUTENAME>. In case it is left empty it is assumed that no
authentication has to be performed.

- 106 -
<PASSWORD>
This parameter defines the password related to <USERNAME> that is applied during the
registration process. The specification is identical to <USERNAME>. In case it is left empty it is
assumed that no authentication has to be performed.
<SPV>
SIP Provider Variant. Even though SIP is a standard, a variety of options following different RFCs
remains possible. Therefore a number of provider dependant variants has been implemented.
See appendix B. PARAMETERS for more details.
0 = Generic variant : generic SIP, suitable for most provider.
<P2P-RTP>
This parameter defines whether calls are made P2P or non-P2P :
0 = Calls between a SIP extension and the SIP trunk are made via the ISG in a hybrid domain and
via the Media Server in a SIP@Net Server domain.
1 = Calls between a SIP extension and the SIP trunk are made peer-to-peer (P2P).
This implies that no ISG or Media Server is involved in media handling.
<ADD-RECEIVE-PHONE-CONTEXT-AS-PREFIX>
This is used in combination with an AudioCodes Mediant 1000.
This parameter defines whether the phone-context parameter in the From or To header of a
received INVITE message has to be used as prefix : 0 = no, 1 = yes.
<IDENTITY-HEADER>
Specifies what identity header is used for the SIP trunk in the INVITE and 200 OK. These identity
headers are used to encode and decode the calling and connected name/number information :
0 = No separate Identity header
1 = P-Asserted-Identity header (in INVITE & RESPONSE)
2 = P-Preferred-Identity header (in INVITE & RESPONSE)
3 = P-Asserted-Identity header (in INVITE, RESPONSE & UPDATE)
4 = P-Preferred-Identity header (in INVITE, RESPONSE & UPDATE)
<EARLY-MEDIA>
SIP allows SDP data in the 180 Ringing or 183 SessionProgress messages. SDP data in the ringing
phase makes it possible to establish media stream in the ringing phase. The behaviour of SIP@Net
depends on the direction of the call and the used interface (SIP-trunk or iPVN).
0 = Early Media is not active
1 = Early Media is active
<SIP-SIG-GROUP>
SIP signalling group data per point code (optional).
<LOCAL DOMAIN-ID>
Local Domain ID per point code (optional).
<AUTHENTICATION REALM>
Some providers require a configurable authentication realm per route (1 … 80 characters).
<USE REFER>
Enables the "SIP Refer" method to transfer calls over a SIP trunk :
0 = No Refer
1 = Refer supported for inbound and outbound calls over a SIP trunk.
<ADD-CNND-NAME>
Add the "CNND name" to the outgoing SIP messages on the SIP-trunk route.
0 = Do not add the CNND name
1 = Add the CNND name
<SIP-TRUNK-GUARDING-TIME>
0 = no SIP trunk guarding
Min. 60 seconds … max. 3600 seconds

- 107 -
<DISABLE-SUPPORT-100REL>
By means of the SIP route option ”Disable Support 100rel” the use of reliable provisional responses
can be configured for outgoing calls.
0 = Support 100rel enabled.
On SIP routes with option Early Media the INVITE message will indicate the support of 100rel.
1 = support 100rel disabled.
On SIP routes with option Early Media the INVITE Message will not indicate the support of
100rel.

For SIP Protocol variant 4 "OCS" the value of this option is ignored; always "disabled" is assumed."

Once a SIP route is projected one can change certain parameters by entering a new value. Using the '-'
clears the parameter; leaving it 'empty' will not change the parameter, but leaves the parameter as it is.
The complete SIP route can be removed using OM command DESIPR.

Assign SIP IP Related Data to SIP Route 601 # !

CHSIPA:<SIP-ROUTE>[,<POINT-CODE>];
This command is used to assign certain SIP related items, before the SIP trunk is taken into service. The
command will ask for the following additional parameters :

<INSIDE-GLOBAL-IP-ADDR>
The IP address of the NAT/STUN server that is used.
In case no NAT/STUN server is used, this parameter must be left empty.
<INSIDE-GLOBAL-IP-PORT>
The IP port of the NAT/STUN server that is used.
In case no NAT/STUN server is used, this parameter must be left empty.
<PROXY-IP-ADDR>
The provider's proxy IP address.
<PROXY-IP-PORT>
The provider's proxy port. In case it is left empty port 5060 is taken.
<PROXY-NAME>
Optionally : the provider's proxy domain name part of the URI, e.g. proxy.pbc.nl.
<REGISTRAR-IP-ADDR>
The provider's registrar IP address.
<REGISTRAR-IP-PORT>
The provider's registrar port. In case it is left empty port 5060 is applied.
<REGISTRAR-NAME>
Optionally : the provider's registrar domain name part of the URI, e.g. regist.pbc.nl.
Enter SIP driver IP address.
<SIP-DRIVER-IP-ADDRESS>
Optionally : the IP address of the own SIP driver.
<SIP-DRIVER-IP-PORT>
Optionally : the IP listen port of the own SIP driver : default port 5060 (boundary 416).

Once a SIP route is projected one can change certain parameters by entering a new value. Using the “-”
clears the parameter. Leaving it “empty” will not change the parameter, but leaves the parameter as it
is. The complete SIP route can be removed using OM command DESIPR.

Activate / De-activate Registration of a SIP Route 602 # !

- 108 -
 RESIPR:<SIP-ROUTE>,<STATUS>;
This command is used to (de-)activate (without registration) the SIP route that is assigned for SIP trunking.
Use command DISIPR to check the status.

- 109 -
Verify the Status of the SIP Trunk 606
DISIPR:<SIP-ROUTE>[,<POINT-CODE>];
This command is used to obtain the SIP data entered by means of CHSIPD and CHSIPA.
In case parameter <POINT-CODE> is omitted all SIP routes with the specified route number are
displayed. The status of the SIP route and the registration process can be observed using this command.

The status can be :

- OUT : the SIP route is Out of Service.

- REG-ING : the SIP route is busy with its registration.
- INS : the SIP route is In Service and operational.

Response example (is different in various releases) :

<DISIPR:88;
ITEM VALUE
Route number : 88
Inside global IP address : port : -
Proxy IP address : port : 192.168.1.10:5060
Proxy domain name : -
By DNS obtained Proxy IPaddress(R/O) : -
Registrar IP address : port : 192.168.1.10:5060
Registrar domain name : -
By DNS obt. Registrar IPaddress(R/O) : -
SIP driver IP address:port : -:5060
Route user name : Amsterdam
Requested lease time in minutes : 3600
Remaining lease time in minutes : 3261
Transport protocol : UDP
Authentication username : Administrator
Authentication password : 1234567
SIP protocol variant : 1
Peer-2-peer RTP : 1
Add received phone-context as prefix : 0
Identity Header : none
Early Media : 0
SIP signalling group : -
Local domain : -
Authentication Realm : -
Use Refer : 0
Add CNND name to outgoing messages : 1
SIP trunk guarding time : 0
Requested route status : SERVER
Current route status : INS

Delete SIP Data from SIP Route 605 # !

DESIPR:<SIP-ROUTE>[,<POINT-CODE>];
This command is used to delete SIP related items from a SIP route.

- 110 -
36.3. SIP EXTENSIONS

Change SIP User Data 603 # !

CHSUSR:<SHELF>,<BRD>,<CRT>;
The command will ask for the additional parameters :
Enter [<PASSWORD>] : ;
Enter [<ALTERNATIVE USERNAME>] : ;

The following applies :

- if <PASSWORD> is omitted no authentication is performed.
- if <ALTERNATIVE USERNAME> is omitted then the <DNR> is the user name.
- for desksharing an <ALTERNATIVE USERNAME> has to be entered.
- the <DNR(user name)> or <ALTERNATIVE USERNAME> is applied for registration.
- OM command CHDNRC has to be executed to assign a DNR to the virtual EHWA.
- in previous releases : the <PASSWORD> and <ALTERNATIVE USERNAME> relation can be removed
by leaving these two parameters empty.
- since SIP@Net 5.1 : for the <PASSWORD> and <ALTERNATIVE USERNAME> either :
- a new value can be given
- the value is not changed by typing ';'
- the value is deleted by typing '-;'

Display SIP User Data 607

DISUSR:[<SHELF>,<BRD>s/r,<CRT>s/r];
In case <SHELF>,<BRD>,<CRT> is omitted a search can be done for a given <DNR> or
<ALTERNATIVE USERNAME>.
Enter [<ALTERNATIVE USERNAME>] : ;
Enter [<UNIT>] : ;

After the virtual extensions and virtual PM are INS and the SIP driver is also operational, this command can
be used to verify that the registration of the SIP terminal(s) is successful. The registration process is done
on the initiative of the SIP terminal. The time it takes to register a SIP terminal depends fully on the
behaviour of the SIP terminal. If a virtual EHWA has an IP-Address then the SIP terminal is registered.
In case the registration expires in the iS3000 then the circuit will get the ABL-fail status.
In case the user enters the EHWA the user is not requested for additional information.

Response example :
<DISUSR:15,2,0&&3;
SHELF BRD CRT DNR ALT.USERNAME PASSWORD
15 2 0 2010 - -
15 2 1 2011 - -
15 2 2 2020 - 2020
15 2 3 2021 - 2021

Display SIP Extension Data 613

DISIED:[[<SHELF>],[<BRD>s/r],[<CRT>s/r][,<SIP-REPORT-TYPE>]];
This command is used to display the dynamic extension data for SIP extensions. This includes the IP address
and SIP port number of the extension, an indication on whether TCP, UDP or TLS is used to carry SIP and
information on the SIP registration lease times.

- 111 -
The data is shown for a given EHWA (<SHELF>,<BRD>,<CRT>).
If no EHWA is given, the command ask for :
Enter <USERNAME>[,<UNIT>] or <DNR>:

Parameter SIP-REPORT-TYPE can be used to display the SIP User-Agent ID, as sent by a SIP terminal
during registration.
When attribute <sec.tagSerialNo> in the sip.cfg file of the Polycom terminals is set to 1, the
Polycom terminal shows its MAC address (Ethernet address) through protocol signaling.

Response examples :

<DISIED:;
Enter <USERNAME>[,<UNIT>] or <DNR>:2101;

SHELF BRD CRT DNR LEASE.REQ LEASE.LEFT

15 1 8 2101 300 221

• SIP-REPORT-TYPE=0
<DISIED:15,1,8&9,0;
SHELF BRD CRT DNR IP-ADDRESS PORT PROT
15 1 8 2101 192.168.9.160 5060 UDP
15 1 9 2108 192.168.9.165 5060 UDP

• SIP-REPORT-TYPE=1
<DISIED:15,1,8&9,1;
SHELF BRD CRT DNR SIP USER-AGENT ID
15 1 8 2101 NECSDT700_ITL_24D/2.3.10.10_0060B90A6874
15 1 9 2108 NECSDT700_ITL_12D/2.3.10.10_0060B90A5271

• SIP-REPORT-TYPE=2
<DISIED:15,1,8&9,2;
SHELF BRD CRT DNR LEASE.REQ LEASE.LEFT
15 1 8 2101 300 221
15 1 9 2108 3600 1488

Change iS3000 SIP Domain Name 604 # !

CHSIDO:[<UNIT>s/r];
The command will ask for the additional parameter :
<DOMAIN-NAME : ;

The following applies :

- if authentication is required, the DOMAIN-NAME is mandatory : it is used by the authentication
algoritm.
- in case no PASSWORD and ALTERNATIVE USERNAME is used (see OM command CHSUSR) the
DOMAIN-NAME may be omitted.
- the DOMAIN-NAME can be removed by leaving it empty.

Display iS3000 SIP Domain Name 608

DISIDO:[<UNIT>s/r];

- 112 -
37. LICENSES
37.1. SYSTEM LICENCES

These commands are used to activate new licenses, to display license information and to obtain the
fingerprint of the system.

Activate License String 531 # !

ACLICS:[<UNIT>];
This command activates the License String in file LICSuu.LIC, which must be present on the LBU. User
confirmation is required to really activate the license string.

When the License string is not correct or not available, rejection codes are returned. The functions of the
previous License string are still applicable. Additional information about the reason of rejection will only be
available in an alarm (code/qualifier = 81/001 and 81/002) when errors were encountered during parsing of
the License String and not for example when the license file was not found.
When a difference is detected between the fingerprint in the License File and the fingerprint read from the
iS3000 hardware, then a rejection code is returned and both fingerprints are displayed.

If the new License string does not contain all the functions that were available in the previous License string,
then a text is displayed asking the user to confirm the License string activation. A License string with a
generation date which is more recent than the system date can not become active. A rejection code is then
returned.
After using the ACLICS command, a back up should be made (GEBUFI/GEBUMI), to store the License String.

Display actual License Information and not licensed Items 462 !

DILICS:[<LICENSE-NUMBER>][,[<UNIT>][,<LIC-REPORT>]];
The LICENSE-NUMBER defines which license information is displayed. When the parameter is omitted all
licenses are displayed.

If UNIT is omitted, then the licenses of all units are displayed.

The LIC-REPORT defines whether the License String as available in the CPU is displayed (LIC-REPORT =
'active_licenses') or whether the License String as available in the License file LICSuu.LIC is displayed (LIC-
REPORT = 'inactive_licenses (from file)').

Note that the LICSuu.LIC file must be present on the LBU.

When LIC-REPORT = 'active_licenses' (or omitted), then the command displays the licensed functions, the
number of items in use of the licensed functions and the items of the licensed functions that are projected
but not licensed.
When LIC-REPORT = 'inactive_licenses (from file)', then the command displays only the functions that shall
be licensed when the License String is activated.

Example: A system has a projection of 70 BSP-IDs and a license for 64 BSP-IDs; the 6 not licensed BSP-IDs
are displayed with the DILICS OM-command.

When the License string is not correct or not available, rejection codes are returned. An indication is
displayed whether the License string is a Service License string. A column in the output shows the expiry
date of the function. The License info is not displayed when the digital signature is not correct.

- 113 -
Response example :
<DILICS:;
Active licenses
UNIT NR DESCRIPTION GRANTED TOTAL USED EXPIRY DATE
01 001 : BSP Yes 21216 27 -
01 002 : IMP Yes - - -
01 003 : ACD agent Yes 100 0 -
01 005 : DPNSS TRUNK Yes - - -
01 006 : Cost Accounting Yes - - -
01 007 : System Management Yes - - -
01 008 : FDCR Yes - - -
01 009 : LCCR Yes - - -
01 010 : Voice Mail Yes - - -
01 011 : iSNet PVN Yes - - -
01 012 : Ext Password Dialing Yes 100 0 -
01 013 : MOH from IAS Yes - - -
01 014 : Dynamic Delay Message Yes - - -
01 015 : Operator Monitoring Yes - - -
UNIT NR DESCRIPTION GRANTED TOTAL USED EXPIRY DATE
01 017 : iSLink CSTA ISDN Yes 100 0 -
01 018 : CSTA monitor Yes 100 0 -
01 019 : Ext Desk Sharing No 0 0 -
NOT LICENSED DNR-BSPT
1308-95
UNIT NR DESCRIPTION GRANTED TOTAL USED EXPIRY DATE
01 020 : CNND Yes - - -
01 021 : iSLink CSTA Ethernet Yes 100 0 -
01 022 : Install DNR-EHWA No - - -
01 023 : CSTA I/O Services Yes - - -
01 024 : CSTA I/O Registration Yes 100 0 -
01 025 : Free Numbering Yes - - -
01 026 : ICDD Yes - - -
01 027 : CCBS Yes - - -
01 028 : ECDD Yes - - -
01 029 : iPVN Yes 40 0 -
01 030 : Project Application 1 Yes - - -
01 031 : Multi line D340 Yes 80 0 -
01 032 : Multi line D340/330 Yes 50 0 -
01 033 : MultL D340/330/325 Yes 10 0 -
UNIT NR DESCRIPTION GRANTED TOTAL USED EXPIRY DATE
01 034 : CSTA PBC application Yes 100 0 -
01 035 : CSTA EP application Yes 100 0 -
01 036 : CSTA EXTERN appl. Yes 100 0 -
01 037 : CSTA EXTERN seat Yes 100 0 -
01 038 : CSTA CC210 appl. Yes 100 0 -
01 039 : CSTA CC210 seat Yes 100 0 -
01 040 : CSTA PBC seat Yes 100 0 -
01 041 : CSTA DMS application Yes 100 0 -
01 042 : CSTA DMS seat Yes 100 0 -
01 045 : CSTA 3P TAPI appl. Yes 100 0 -
01 046 : CSTA 3P TAPI seat Yes 100 0 -
01 047 : CSTA EP seat Yes 100 0 -
01 048 : Voice Logging Yes - - -
01 049 : CSTA voice log appl. Yes 100 0 -
UNIT NR DESCRIPTION GRANTED TOTAL USED EXPIRY DATE
01 050 : CSTA voice log seat Yes 100 0 -
01 051 : CSTA CTI server appl. Yes 100 0 -
01 052 : CSTA CTI server seat Yes 100 0 -
01 056 : BCT synchronization Yes - - -
01 057 : QSIG Suppl. Services Yes - - -
01 058 : QSIG iSNet Yes - - -
01 059 : ISG channels Yes 1010 0 -
01 060 : CSTA messenger appl. Yes 100 0 -
01 061 : CSTA messenger seat Yes 100 0 -

- 114 -
 01 064 : CSTA desktop appl. Yes 100 0 -
01 065 : CSTA desktop seat Yes 100 0 -
01 066 : Software SMA user Yes 100 0 -
01 067 : CCIS TRUNK Yes - - -
01 068 : iTMP DECT Yes - - -
UNIT NR DESCRIPTION GRANTED TOTAL USED EXPIRY DATE
01 069 : SIP Extensions Yes 1010 4 -
01 070 : SIP Trunk Suppl.Serv. Yes - - -
01 071 : SIP Server Yes - - -
01 072 : SIP Server on ISS Yes - - -
01 073 : Start Upgrade Period Yes 20141 - -
01 074 : Non-NEC SIP trunk Yes - - -
01 075 : SIP trunk channels Yes 1000 0 -
01 076 : SIP Server Availabil. No - - -
01 077 : SIP Server Slaves No 0 0 -
01 078 : SWA Upgrade Allowance No - - -
01 079 : Native SIP Server Yes - - -
01 081 : Gateway Extension Yes 10 3 -
01 082 : DT820 Gigabit Yes 200 128 -
01 083 : DT820 Ext Linekey 16 Yes 150 128 -
01 084 : DT820 Ext Linekey 32 Yes 100 34 -

Retrieve Fingerprint 532 # !

RTFING:;
When UNIT is omitted, the OM command is executed for all units.
A fingerprint is an identification of a product instance. This is programmed in the product and can not be
modified. The fingerprint consists of two parts: a protocol prefix and:

- for CPU3000 : the CPU3000 Board Identification, i.e. the 12 NC and the SB number.
- for CCS with CIE-2 boards : the CIE Board Identification.

The fingerprint is put in the file FINGuu.LIC on the LBU and is displayed on the OM terminal.
The Fingerprint of a SIP@Net Server/ISS/ISS-2/ISS-3 is programmed in an USB dongle (Sentinel).
The External Hardware Address (EHWA) of the equipment from which the Fingerprint is read, is displayed
on the screen of the OM device. This EHWA is required when some boards must be replaced and there is a
doubt about whether or not these boards carry the system Fingerprint.
In case of a SIP@Net Server the dongle can be installed on a remote dongle server, using the SIP@Net
installer. Then RTFING also shows the IP address of the remote dongle server.
A remote dongle can also be used for the ISS/ISS-2/ISS-3 platform, but this not likely the case.

Response :
<RTFING:;
DONGLE IP ADDRESS (only shown in case of a SIP@Net Server or ISS/ISS-2/ISS-3)
192.168.116.20
UNIT FINGERPRINT SHELF BRD CRT STATUS
05 aa0024IC960002104003xxx0045AA 5014 18 - Fing. written to file

The STATUS can be :

- Fing. written to file
- Fing. not written
- Fing. unobtainable

In this example 960002104003 is the 12 NC and 0045 is the SB number of the fingerprint containing
equipment.

- 115 -
37.2. HARDWARE-LESS FINGERPRINT

Since SIP@Net 6.2, the "Hardware-less Fingerprint" license mechanism is introduced as a new method to
define a Hardware Key Code (=Fingerprint) of a SIP@Net Server platform. Especially, in case the SIP@Net
Server is running in a VM and/or "IPv6 only" environment, this "Hardware-less Fingerprint" license
mechanism is an alternative for the Sentinel USB dongle. Note that the dongle does not support IPv6.

The Hardware Key Code (HWKeycode) is defined by means of the Full computer name of the Windows
platform hosting the SIP@Net executable.

To enable the "Hardware-less Fingerprint" license mechanism, the computer must be placed in a Domain
and the Domain Controller must be installed on a different computer than SIP@Net is running on.
The Hardware-less Fingerprint can be used on all server platforms, including the ISS/ISS-2/ISS-3 and Virtual
Machines.

The license file can be obtained via LMS by offering the Full computer name (max 128 characters).

OM command RTFING is slightly changed to support the usage of the Hardware-less Fingerprint.
RTFING shows the first 57 characters of the Full computer name.

<RTFING:;

UNIT FINGERPRINT SHELF BRD CRT STATUS

01 aa0016HN081545846400AA 11 18 - Fing. written to file

HARDWARE-LESS FINGERPRINT
Full computer name: XPS8300BCTVM2.isdlab.local
Domain Controller : \\LabRouter.isdlab.local
HWKeycode : aa0016HN081545846400AA

The Hardware-less Fingerprint is only displayed if no Dongle has been found.

If a corresponding and valid license file has been found then it is displayed under the header FINGERPRINT.

37.3. LICENSES FOR DT820 STANDARD SIP TERMINALS

There are two DT820 base models :

- DT820 : ITY-6D – 6 line keys with a display, 10/100

- DT820 : ITY-8LDX – 8 line keys, a single page DESI-less display, 10/100

By using the following additional licenses, the two models can be upgraded to give additional variants :

- License 82 "DT820 Gigabit" to offer Gigabit support on both the ITY-6D and ITY-8LDX models.
- License 83 "DT820 Ext Linekey 16" upgrades the ITY-8LDX to 16 line keys in total on 2 DESI-less pages.
- License 84 "DT820 Ext Linekey 32" upgrades the ITY-8LDX to 32 line keys in total on 4 DESI-less pages.

The licenses are exchanged with the DT820 terminals via proprietary headers in the SIP REGISTER and SIP
200OK reply.
The licenses are counted static if the license is assigned to a virtual SIP circuit using OM command CHSIPL.

- 116 -
Change SIP License 639 # !
CHSIPL:<SHELF>,[<BRD>s/r],[<CRT>s/r][,<DT820-LICENSE>];
Parameter <DT820-LICENSE> is one of the following :
1 = DT820 Gigabit License
2 = DT820 Ext Linekey 16
3 = DT820 Ext Linekey 32
4 = DT820 Gigabit License + DT820 Ext Linekey 16
5 = DT820 Gigabit License + DT820 Ext Linekey 32

If parameter <DT820-LICENSE> is omitted then all licenses are removed.

If no more licenses are present an error message is returned. The licenses will be added to the circuit but
the license can not be used untill the relevant license is increased / additional licenses are ordered.

The licenses are counted static if the license is assigned to a virtual SIP circuit using OM command CHSIPL.
From the provisioning point of view, the installation/configuration aspects are similar as for the DT700
series. One Touch Deployment (OTD) can also be used to enroll the DT820 terminals. When OTD is used,
system boundary 468 specifies the "DT820 default license suite" for DT820 terminals that register via OTD.
The value of this boundary 468 can be 0 (= no license) or 1 … 5 as given in parameter <DT820-LICENSE>.

The registration results in assignment of the default license, to the circuit and, if it is possible to assign the
licenses, then the license is distributed to the terminal.
Lack of licenses will result in a license alarm and the terminal will operate in basic mode. Either increase the
required licenses or remove the license(s) from those EHWA’s that do not need/require the license(s).

WARNING : When removing the license(s) from an EHWA that have a DT820 previously registered via the
OTD mechanism, that EHWA will get the specified licenses of boundary 468 back again after
a DT820 re-registration. So before removing the licenses from the EHWA, it is advised to set
boundary 468 to 0 (meaning no licenses).

Display SIP Licenses 640

DISIPL:[<SHELF>],[<BRD>sr],[<CRT>sr][,<DT820-REPORT>]];

• To display the license of one circuit : DISIPL:<SHELF>,<BRD>,<CRT>;

• To display all licenses of one board : DISIPL:<SHELF>,<BRD>,0&&31;
• To display all EHWA’s with a particular license : DISIPL:,,,<DT820-REPORT>;

Parameter <DT820-REPORT> can be :

1 = Show all EHWAs with terminal license Giga, Giga/LK16 or Giga/LK32
2 = Show all EHWAs with terminal license LK16 or Giga/LK16
3 = Show all EHWAs with terminal license LK32 or Giga/LK32
4 = Show all EHWAs with terminal license Giga/LK16
5 = Show all EHWAs with terminal license Giga/LK32

Response example :

<DISIPL:15,6,0&&4;
SHELF BRD CRT SIP USER-AGENT ID MAC-ADDRESS GIGA LK16 LK32
15 6 0 NECSDT700_ITL-8LD/2.3.43 - N -
15 6 1 NECSDT800_ITY-6D/2.3.43. Y N -
15 6 2 NECSDT800_ITY-8LDX/2.3.4 0060B9FB4077 X - Y
15 6 3 PolycomVVX-VVX_600-UA/5. N - -
15 6 4 - - - -

- 117 -
The column SIP USER-AGENT ID is just cut off after 24 characters.
The meaning of the license columns GIGA, LK16 and LK32 is as follows :

- = No license assigned
X = No license available (license alarm)
P = License assigned waiting for acceptance by terminal
Y = License assigned and accepted by terminal
N = License assigned but not supported by terminal
spaces = License change : wait for next registration message from the terminal

OM command DISIPL displays the last received USER-AGENT-ID. The licenses are counted statically.
When a license is assigned to the EHWA of a SIP-circuit, it is counted.
The status in DISIPL becomes "P" (pending) because a different terminal might have plugged in and on
receipt of the first register from the terminal the status becomes "N" if the terminal does not support the
specified DT820 license. All EHWA’s that show this status "N" must trigger the engineer to remove the
license from the EHWA, to have sufficient licenses left for other EHWA’s.

- 118 -
38. LOAD CONTROL
The load of a unit can be expressed in "permission units" of the CPU. The value of the permission units
approaches the real load in %, but in case of changing load characteristics they may deviate. They should be
interpreted as relative values. This load is caused by tasks running at the same moment. Examples of tasks
are: calls, periodic tests and OM commands. These tasks are distributed over sources. A source combines a
specific category of tasks. There are two types of sources. The primary sources show tasks that can be
directly identified. The secondary sources contain tasks that are started by other tasks. For each source and
for the unit as a whole, a guaranteed load level exists. If the actual load of a unit is above its guaranteed
level, it will only allow more tasks as long as they stay below the guaranteed level of the corresponding
source.

The monitor process and the display command are completely independent of each other.

38.1. MONITOR LOAD

The load in a unit can be monitored. This process writes information about the load in all the sources to a
file. Only one load monitoring process can run in a unit.

Start Load Monitor 298

STALDM: <FILE>,<MONITOR-INTERVAL>,<ON-TIME>,<OFF-TIME>,<DATA-INDICATOR>
[,<UNIT>];
The layout of the output is the same as in the DIOVLD command, but in addition a 13th column indicates
the actual load percentage and each line is preceded by the date and time in the following format:
YYYY-MM-DD +W+ HH:MM

Cancel Load Monitor 299

CANLDM:[<ON-TIME>],[<OFF-TIME>][,<UNIT>];
If the load monitor was active, it will be stopped and the file will be closed.

Display Load Monitor 346

DISLDM:[<UNIT>];
Response:

UNIT ON-TIME OFF-TIME ON-TIME EXPIRED OFF-TIME EXPIRED

xx xxxxx xxxxx xxxxx xxxxx

38.2. DISPLAY LOAD

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'.

See the "Second Line Maintenance Manual" for more details.

- 119 -
Display (Main) Processor Load 309 !
DILOAD:;

Display Overview of Load 297

DIOVLD:<DATA-INDICATOR>[,<UNIT>];
Response:
SAS SAS SAS OM OM OM CP CP SAS OM GOS UNIT
URG FHL TST URG MNT MAT CAL RM GEN GEN RM TOT
xx xx xx xx xx xx xx xx xx xx xx xx

Primary sources are :

SAS-URG : System Assurance urgent actions

SAS-FHL : System Assurance fault handling and location
SAS-TST : System Assurance preventive tests
OM-URG : Operational Maintenance urgent commands
OM-MNT : Operational Maintenance
OM-MAT : Operational Maintenance tests
CP-CAL : Call Processing
CP-RM : Call Processing Registration and Measurements

Secondary sources are :

SAS-GEN : System Assurance work

OM-GEN : Operational Maintenance work
GOS-RM : Global Operating System resource management
UNIT-TOT : indicates the total load for the unit.

Tune Load Control Data 359 !

CHLDCT:<SOURCE>,<DATA-INDICATOR>,<DATA-VALUE>[,<UNIT>];
This command (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.

See the "Second Line Maintenance Manual" for more details.

- 120 -
39. LOCATION SERVICE
Since SIP@Net 6.4 SIP@Net can act as a location server (LIS). SIP@Net has a database to maintain IP /
Range <-> location-ID’s relations. The database can be managed with OM-commands. See manual SIP in
iS3000/SIP@Net.

Change Location-ID Default 643 #!

CHLCDF:[<LOCATION-ID>][,<UNIT>];

Change or remove the default Location-ID of a unit. Omitting the Location-id removes the Location-ID of
the unit. UNIT may only be omitted in single unit systems.

Display Location-ID Default 644

DILCDF:[<UNIT>];
Display Default Location-ID of a unit. If UNIT is omitted, the command will be executed system wide.

Change IP-Address - Location ID relation 641 #!

CHLCID:<IP-ADDRESS>,[<PREFIX-LENGTH>],[<LOCATION-ID>][,<UNIT>];

Change or remove IP Address Location-ID relation. Omitting the Location-id removes the relation.
Ranges are created by entering the prefix-length, e.g. IPv4 192.168.1.0/24 means 192.168.1.0 ..
192.168.1.255

UNIT may only be omitted in single unit systems.

Display IP-Address - Location ID relation 642

DILCID:[<IP-ADDRESS>],[<PREFIX-LENGTH>][,<UNIT>];

Displays the content of the location-id database. Omitting the IP-address displays all entries of given unit. If
UNIT is omitted, the command will be executed system wide.

- 121 -
40. MANAGER DATA AND SUBSCRIBER CATEGORY
Display MFC Manager Data 222
DIMMFC:<MFC-TYPE>,<MFC-INDEX>s/r,[<MFC-ADD-INDEX>s/r][,<UNIT>];
Response:
MFC-TYPE MFC-INDEX MEANING-MFC-SIGNAL or
MFC-TYPE MFC-INDEX BACKWARD-MFC-SIGNAL CALL-CONTROL-ACTION or
MFC-TYPE MFC-INDEX MFC-ADD-INDEX BACK-MFC-SIGNAL CALL-CONTROL-ACTION or
MFC-TYPE MFC-INDEX CALL-CONTROL-ACTION or
MFC-TYPE MFC-INDEX MFC-ADD-INDEX CALL-CONTROL-ACTION

Change Subscriber Category of DNR/BSP 72 # !

CHCASC:<SUBSCR-CAT>,<BSP-ID>s/r;
The Subscriber Category is transmitted during each outgoing MFC call as first digit of the Calling Line
Identity (CLI).
This command assigns a Subscriber Category to a BSP-ID. This applies to both extensions and operators. A
Subscriber Category assigned to an operator position must be effectuated by a transition from day to night
of the operator position.

Display Subscriber Category of DNR/BSP 71

DICASC:<BSP-ID>s/r;
Response:
DNR-BSPT SUBSCR-CAT
xxxx xx

- 122 -
41. MERCURY INDIRECT SERVICE
This OM command for Smart Box Emulation is used to change the authorization code (PIN code) for each
user group in the system. This PIN code is used by Mercury for Call authorization.

Change Authorization Code 401

CHAUCO:[<CV>];
If the CV (Compatibility Value) is omitted the default value is used (usually 0).
Response:
Old authorization code: <AC>;
New authorization code: <AC>;
Verification: <AC>;

- 123 -
42. MULTIPLE SUBSCRIBER NUMBER
Change Fixed MSN Digit 431 # !
CHFMSN:<BSP-ID>,<DIGIT>;

Change MSN Parameters 415 # !

CHMSNP:<SHELF>,<BRD>,<CRT>s/r,<MSN-TYPE>[,<NO-MSN-DIGITS>];
Parameter NO-MSN-DIGITS can only be entered if MSN-TYPE indicates MSN (1).

Note: When associated hardware addresses (i.e. the two EHWAs of an S0bus) are involved, then the MSN
parameters of both hardware addresses must be projected identical.

Display Fixed MSN Digit 441

DIFMSN:<BSP-ID>s/r;
Response:
FIXED MSN
DNR-BSPT DIGIT
xxx xxx

Display MSN Parameters 424

DIMSNP:<SHELF>,<BRD>,<CRT>s/r;
Response:
SHELF BRD CRT MSN-TYPE NUMBER-OF-MSN-DIGITS
xxxx xx xx x x

- 124 -
43. NAME NUMBER RELATIONS
Until Call@Net 2.5 for name/number relationship two possibilities exist:

• Calling Name Number Display (CNND) relations (license 20)

CNND makes it possible to display also names on the display of an extension instead of only the DNR.
Although referred to as 'Calling Name and Number Display', the commercial term for CNND is 'Central
Name and Number Directory'.

• Central Directory Dialling (CDD) relations (license 26)

CDD offers Ergoline D330/D340 users Phonebook browsing in a phonebook located in the iS3000.
The CDD database contains names and numbers within the company.
The CDD database allows different numbers having the same name.

Since Call@Net 2.6 the Directory Distribution Services (DDS) application updates the name/number
relations data from the central PhoneWare directory. Now both the CNND and the CDD functions share the
same databases, within the PBX. There is one database for internal names and one database for external
names.

Since Call@Net 2.6 it is also possible to have multiple names belonging to one DNR and vice versa.
The first specified name is automatically the preferred name for CNND but this can also be changed.

Note: Although OM command CHNAME can be used, it is strongly advised to use Management@Net or
the SysManager 410 for the daily maintenance of the name directories.

Entering/Deleting Name/Number Relations 121 # !

CHNAME:[<DNR/NUMBER>s][,[<CLUSTER-ID>][,[<DIRECTORY>]]];
Enter [<DNR/NUMBER>[,<NAME>[,[<CLUSTER-ID>][,[<DIRECTORY>]
[,[<ATTRIBUTES>]]]]]];

Assigning or changing a name/number relation can only be executed via the additional parameters. This is
done because input on the main command line is converted to upper case characters (so names in this case
could only be specified with upper case characters). Additional parameters can also be lower case.

The CDD as well as the CNND database allow the same name to be associated with more than one number.
In the CDD (and not in the CNND) database it is also allowed to have more than one name assigned to one
number. Via the hidden field in the <ATTRIBUTES> field the preferred number/name relation for CDD
can be selected.

The first name entered will become preferred : when a second name is entered it can be set to preferred; if
so the first name automatically becomes non-preferred.
With directory 2=ROUTE the additional parameter <ATTRIBUTES> is irrelevant and is ignored.

When all parameters on the main command line are omitted the command will ask for additional
parameters.

- Assign and change entries via additional parameters, or delete all entries (when the confirmation
request is acknowledged affirmative).
CHNAME:;

- Delete all entries from the Internal Directory (when the confirmation request is acknowledged
affirmative).
CHNAME:,,;

- 125 -
- Delete all entries identified with the specified DNR/NUMBER-values.
CHNAME:<DNR/NUMBER>s;

- Delete all entries identified with the specified CLUSTER-ID-value from the Internal Directory (when the
confirmation request is acknowledged affirmative).
CHNAME:,<CLUSTER-ID>;

- Delete (a series of) entries with specified DNR/NUMBER-and CLUSTER-ID-values from the Internal
Directory.
CHNAME:<DNR/NUMBER>s,<CLUSTER-ID>;

- Delete all entries identified with the specified DIRECTORY-value (when the confirmation request is
acknowledged affirmative).
CHNAME:,,<DIRECTORY>;

- Delete all entries identified with the specified CLUSTER-ID- and DIRECTORY-value (when the
confirmation request is acknowledged affirmative).
CHNAME:,<CLUSTER-ID>,<DIRECTORY>;

- Delete all entries identified with the specified DNR/NUMBER- and DIRECTORY-value.
CHNAME:<DNR/NUMBER>s,,<DIRECTORY>;

- Delete (a series of) entries identified with the specified NUMBER-, CLUSTER-ID- and DIRECTORY-values.
CHNAME:<DNR/NUMBER>s,<CLUSTER-ID>,<DIRECTORY>;

Names may be entered in upper and/or lower case characters.

Note: The size of the database can be projected smaller than the maximum number of DNRs in the unit.
This implies that congestion can occur on storing a new name into the database, when the database
is full.
A name/DNR relation is automatically stored in the unit the DNR is assigned in. Therefore it is not
possible to move a name/DNR relation to another unit, unless the DNR is moved to the other unit.
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 normal browsing functions.

Display Number/Name Relation 542

DIDNRN:<DNR/NUMBER>s/r[,[<CLUSTER-ID>][,[<DIRECTORY>]]];
This command shows the names and numbers of the specified NUMBERs from the CDD database.
Depending on the optional parameters, the following information is displayed:

- Display all entries identified with the specified DNR/NUMBER-values in the Internal Directory :
DIDNRN:<DNR/NUMBER>s/r;

- Display all entries identified with the specified DNR/NUMBER-values and CLUSTER-IDvalue in the
Internal Directory :
DIDNRN:<DNR/NUMBER>s/r,<CLUSTER-ID>;

- Display all entries identified with the specified DNR/NUMBER-values, CLUSTER-ID-value and DIRECTORY-
value :
DIDNRN:<DNR/NUMBER>s/r,<CLUSTER-ID>,<DIRECTORY>;

- Display all entries identified with the specified DNR/NUMBER-values and DIRECTORYvalue :
DIDNRN:<DNR/NUMBER>s/r,,<DIRECTORY>;

- 126 -
If a number/name is entered and the relation is not present, the message "No relation or data found" is
given.
If there is no CDD database present, the message "No CDD-database present" is given.
Response:
CLUSTER-ID DNR/NUMBER NAME HIDE PREF DIRECTORY
41 1234 Benbow D. Yes Yes Internal
41 3456 Smith J. No No Internal
- 00356564325 Thomas A. - Yes External
6 DPNSS Route

Display Name/NumberRelation 543

DINDNR:[<DIRECTORY>];
Enter: [<NAME>];
This command displays the DNR/numbers that are related to the search string.
In general parameter <DIRECTORY> can be omitted.
Response:
CLUSTER-ID DNR/NUMBER NAME HIDE PREF DIRECTORY
41 1234 Benbow D. Yes No Internal
41 3456 Smith J. No Yes Internal

Display Name/Number Usage 544

DINAMU:[<UNIT>s/r];
This command displays the size and free space of the internal, external and route name databases in the
specified units.
When parameter <UNIT> is omitted, the command is executed in the local database.
Response:
UNIT INTERNAL-ENTRIES FREE EXTERNAL-ENTRIES FREE ROUTE-ENTRIES FREE
2 150 81 50 47 20 16
5 200 63 100 34 20 12

- 127 -
44. NIGHT TRAFFIC AND SPECIAL EXTENSIONS
44.1. CANS AND HOOTER

Assign Unit to CANS Area 203 # !

ASCANS:[<UNIT-1>s/r,<UNIT-2>];
<UNIT-1> will be assigned to the Common Answering Night Service (CANS) area in <UNIT-2>.
In a single unit system both parameter 1 and 2 can be omitted.

Change Hooter Presence Mark 205 # !

CHHOOT:<MARK>[,<UNIT>s/r];
Indicates to the system if a hooter is present or not.

Display CANS and Hooter Characteristics 206

DICANS:[<UNIT>];
If no unit number is specified the command is performed system wide.
Response:
UNIT HOOTER NIGHT TRAFFIC CLASSES CANS AREA
INE SCNE MCNE CANS
xx xxx xx xx xx xx xxxxxxx

Erase Unit from CANS Area 204 # !

ERCANS:[<UNIT-1>s/r,<UNIT-2>];
<UNIT-1> will be erased from the CANS area in <UNIT-2>.
In a single unit system both parameter 1 and 2 can be omitted.

44.2. NIGHT EXTENSIONS

To display night extensions the DISPEX command is used : see next section.

Change Individual Night Extension 198 # !

CHINEX:<SHELF>,<BRD>s/r,<CRT>s/r[,[<B-CHANNEL>s/r][,<DNR>]];
When the DNR parameter is omitted the Individual Night Extension (INE) is deleted. The B-Channel only has
to be given in case of an ISDN trunk line.

Change Main Common Night Extension 196 # !

CHMCNE:[<UNIT>s/r][,<DNR>][,<CV>s/r];
It makes it possible to assign or to change a specific Main Common Night Extension (MCNE). If the DNR is
omitted in the command, the specific MCNE is deleted.
If CV is omitted the general MCNE is assigned. If DNR and the CV are omitted, the general MCNE is deleted.

Note that in previous releases, parameter CV is ASSIST-GROUP.

Change Sub Common Night Extension 197 # !

CHSCNE:<ROUTE>s/r[,<DNR>];
When the DNR is omitted the Sub Common Night Extension (SCNE) is deleted.

- 128 -
Change Traffic Class of Night Extension Group 201 # !
CHTRNE:<NE-LEVEL>,<TRFC>[,<UNIT>s/r];

44.3. SPECIAL EXTENSIONS

Change Overflow Extension 200 # !

CHOVEX:<ROUTE>s/r[,<DNR>];
When the DNR is omitted the Overflow Extension (OVE) is deleted.

Change Permanent Line Extension 199 # !

CHPLEX:<SHELF>,<BRD>s/r,<CRT>s/r[,[<B-CHANNEL>s/r][,<DNR>]];
When the DNR is omitted the Permanent Line Extension (PLE) is deleted. The B-Channel only has to be
given in case of an ISDN trunk line.

Display Special Extensions 202

DISPEX:[<UNIT>];
The unit number is only displayed for the MCNE DNR in a multi unit system. The assistance group is only
displayed for an (assistance group) specific MCNE.The route number is only displayed for the SCNE or OVE
DNR. The EHWA (SHELF, BRD, CRT) and the B-channel are only displayed for the INE or PLE DNR.

Response:
TYPE DNR UNIT ROUTE SHELF BRD CRT B-CH CV (ASSISTANCE-GROUP in older releases)
xx xxxxxx xx xx xxxxx xx xx - xx

- 129 -
45. NUMBERING SCHEME
The whole numbering scheme can be divided into the internal numbering scheme and the external
numbering scheme. Both types of number analysis data are held in the same type of trees. As the internal
and external numbering scheme data require different parameters, different OM commands are available.
Some commands are valid for both numbering schemes.

The names internal number and internal numbering scheme can give confusion of thought. Internal
numbers are the numbers that belong to extensions (DNRs). Such an internal number is only one of the
analysis results of the internal numbering scheme. Other analysis results in the internal numbering scheme
are abbreviated number, follow-me prefix etc.

45.1. NUMBERING SCHEME GENERAL

Change Traffic Class Barring 38 # !

CHTBAR:<TREE>,<NUMBER>,<TRFC>;
This command is used to change the traffic class in a number analysis tree, without affecting the analysed
digits.

Display Number Analysis Result String 426

DINARS:<TREE>s/r[,<RESULT-ID>];
This command searches for the number that is related to a result identity. When Result-Id is omitted, all
related numbers in the given tree will be displayed.
Response :
TREE CODE ANALYSIS RESULT NUMBER ID NUMBER
xx xxx xxxxxxxxxxxxxxxxxx xxxxx xx xxx

The 'ID NUMBER' (when applicable) gives information about the destination (assigned with ASINTN and
CHCSDD). The destination 'ID' is given and the related ‘NUMBER'. For example the ‘ID' could be :

P = Paging route
D = Destination
Q = A-queue number
S = Server
U = Unit

Display Number Analysis Scheme Data 42

DINASD:<TREE>s/r[,<NUMBER>];
This command is used to display (part of) the contents of a number analysis tree. If an existing NUMBER is
entered the display starts from the last pyramid in which this digit string is analysed.
The tree numbers for the internal numbering scheme can be displayed by using command DIDIAL, for DDI
by using command DIROUT and for DDO by using command DIDEST. The tables of the tree are displayed
per level. Each table consists of :

A B C D E F G H I J K L M N O P Q R

- 130 -
These letters have the following meaning :

A = Digit in table
B = Result ID number
C = Analysis result
D = Next analysis table/Line number/Tariff Class
E = Number length/PVN mode/Number of Virtual Lines/Pause Place
F = Destination/Route table/A queue/Unit/Password Validation/Server
G = Paging route number/Pause (sec)
H = Traffic Class (TRFC)
I = Minimum length of numbers
J = Maximum length of numbers
K = Dial tone place
L = Pre-digit
M = Post-digit
N = Restoration-mode
O = Toll operator intrusion allowance/Charged number
P = Barring possible mark
Q = Location Lookup (see note)
R = Point Code

Note: Since SIP@Net 5.0.4 “Location Lookup” is introduced and displayed in column Q.
In previous SIP@Net releases, column Q displayed the Point Codes. This is now moved to column R.

Display Number Analysis Scheme Used Memory 45

DINASM:;
Response :
ANALYSIS TABLES EXTERNAL NUMBER BLOCKS
(PROJECTED) (FREE) (MAXIMUM) (FREE)
xx xx xx xx

Make Number Unobtainable 39 # !

MAKENU:<TREE>,<NUMBER>;
This command is used to erase an internal or external numbering scheme number or block.

45.2. INTERNAL NUMBERING SCHEME

Assign Analysis Tree to Dial Type 33 # !

ASTREE:<TREE>,<DIAL-TYPE>s[,<AG>/<ROUTE>];
The analysis group is only used for the following dial types :

- 0 = Extension dialling
- 1 = Enquiry dialling
- 4 = Alternative destination dialling
- 5 = Follow Me primary dialling
- 8 = Overlay time-out dialling
- 9 = Overlay continue dialling

If the analysis group it is omitted, the default will be used. If the analysis group is omitted for alternative
destination dialling then a general tree is assigned to all analysis groups that have no specific tree for
alternative destination dialling.
For dial types 0 ... 9 and 11 the third parameter is AG.

- 131 -
For dial type 10, the third parameter is ROUTE : the analysis tree for 'Network Node Dialling' is assigned to
the route.

Assign Internal Numbering Scheme Block 34 # !

ASBLCK: <TREE>,<NUMBER>,<TRFC>,<NUMBER-LENGTH/CV/POINT-CODE>,
<RESULT-ID>[,<DEST>];
This command is used to assign a block of internal numbers or abbreviated dialing : only the RESULT-IDs 10,
23 and 24 are allowed.

When assigning a block of internal numbers in the initial dialling tree (using OM command ASBLCK with
RESULT-ID 10), an optional destination can be assigned.

A call to a number projected as 'internal number', for which no DNR has been assigned is implicitly
considered as an 'external number' and is passed to a destination, following the normal routing projecting :
Destination – Route-Table – Route – Bundle – Line(s). The destination characteristics 'dialtone-options',
'access-code-repetition' and 'delayed-seizure' are ignored.

Suppose the 1xxx range is assigned and a destination is specified, then when 1234 is dialled (which is a non-
existing DNR), the call is routed to the specified destination. It overrules the "Call Forwarding on not
existing DNR" (CF-TYPE 6) when set. When also the 2xxx range is assigned and no destination is specified,
then when 2345 is dialled (which is a non existing DNR), the call is routed to the "Call Forwarding on not
existing DNR" (CF-TYPE 6) when set.

Assign Internal Numbering Scheme Number 36 # !

ASINTN: <TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER>]
[,<NUMBER-LENGTH/CV/POINT-CODE>]];
This command is used to assign a prefix. In most cases the parameters DEST/NUMBER and NUMBER-
LENGTH/CV must be omitted.
Exceptions to this rule are:

- If RESULT-ID = 48 or 49:
CV is an optional parameter and is only used in case of RESULT-ID = 48 or 49. When the CV is omitted in
the command, the existing relation (if present) is deleted.
- If RESULT-ID = 49:
DEST/NUMBER must be given. Fill in the A-queue number (1 ... 16).
- If RESULT-ID = 14, 21, 91, 92, 138, 147:
DEST/NUMBER must be the destination number.
- If RESULT-ID = 12, 13, 120 ... 125, 139 ... 142:
DEST/NUMBER must be the paging route number.
- If RESULT-ID = 20, 25, 43, 68, 69, 70, 71, 72, 73, 74, 82, 105 ... 115, 118, 119, 127, 135, 136:
NUMBER-LENGTH must be given and DEST/NUMBER must be empty.

Note: The NUMBER-LENGTH in RESULT-ID 111 is used to validate the dialled cost centre code.
The last digit of the cost centre code must be equal to the sum of the other digits MOD length.
For example, if the length is 6 then 1 2 3 4 5 3 is a valid cost centre code. 1+2+3+4+5=15. 15
MOD 6 = 3 (remainder after division). Last digit is also 3, therefore it is a valid cost centre code.

- If the RESULT-ID is 50, 51, 143 and 144 and the DEST/NUMBER is empty or '0', PID validation (SSM) is
used. If the DEST/NUMBER = 1 then password (IPD) validation is used. The NR-LENGTH (0 ... 16) is the
length of the PID or password and NUMBER means 'prefix'.
- If RESULT-ID = 82:
The number of characters in NUMBER must be compatible with the TMS digit position.

- 132 -
- If RESULT-ID = 104:
NUMBER-LENGTH (0 ... 16) indicates length of password.
DEST/NUMBER is 0 means 'change password of current DNR' and 1 means 'change password of any
other DNR'.
- If RESULT-ID = 132, 133:
Enter the unit number for DEST/NUMBER. NUMBER-LENGTH must be empty in the case of 132. In the
case of 133, NUMBER-LENGTH must be PVN mode.
- If RESULT-ID = 150:
The DEST/NUMBER is the virtual line number and NUMBER-LENGTH indicates the range of consecutive
virtual line numbers 1 ... 99 (1 = default and 99 = max number of virtual lines).
- RESULT-IDs 10, 22, 23, 24 and 145 are not allowed.

Change CSTA Server Dialled Data 158 # !

CHCSDD: <TREE>,<NUMBER>,<TRFC>,<SERVER-AND-ACTION-CODE>
[,[<PW-NBR-LENGTH>][,<ADD-INFO-NBR-LENGTH>]];
With this command a prefix can be defined leading to the result-id "CSTA server dialled".

Display CSTA Server Dialled Data 215

DICSDD:<TREE>[,[<NUMBER>][,<SERVER-AND-ACTION-CODE>]];
This command displays the data stored of the prefixes with result-id "CSTA server dialled".

- If the parameter NUMBER is omitted, all available CSTA server dialled data for the given TREE and
SERVER-AND-ACTION-CODE will be displayed.
- If the parameter SERVER-AND-ACTION-CODE is omitted, all available CSTA server dialled data for the
given TREE and NUMBER will be displayed.
- If the parameter NUMBER and SERVER-AND-ACTION-CODE are omitted, all available CSTA server dialled
data for the given TREE will be displayed.

The layout of the display is as follows (example):

TREE NUMBER SERVER-CODE ACTION-CODE #PASSWORD-DIGITS #ADD.INFO-DIGITS
0 #49 1 5 0 4
0 #49 1 5 0 4

Display Dial Type Relations 44

DIDIAL:[<DIAL-TYPE>s/r];
If DIAL-TYPE is omitted all dial types will be displayed.
Response example :

DIAL-TYPE ANALYSIS ANALYSIS ROUTE

GROUP No TREE No No
0 : Extension dialling xx xx -
1 : Enquiry dialling xx xx -
2 : Operator dialling - xx -
3 : Post dialling - xx -
4 : Alternative destination dialling xx xx -
5 : FM primary dialling xx (1) xx -
6 : Pick up destination dialling - xx -
7 : Executive secretary dialling - xx -
8 : Overlay time-out dialling xx xx -
9 : Overlay continue dialling xx xx -
10: QSIG network party dialling - xx xx
11: Media dialing - xx -

1) When no specific Analysis Group is assigned (using ASTREE) a “-” is shown, meaning the default
Analysis Group.

- 133 -
45.3. EXTERNAL NUMBERING SCHEME

Assign External Numbering Scheme Number 37 # !

ASEXTN: <TREE>,<NUMBER>,<TRFC>,<MIN-LENGTH>,<MAX-LENGTH>,
<DIALTONE-PLACE>[,[<TARIFF-CLASS>][,<PAUSE-PLACE>,<INTERVAL>]];
Give [<ROUTE-TABLE>[,<POINT-CODE>]:;
Give [<LOCATION-LOOKUP>]:;

The number (or number range) gets result-ID 022 (External number).
The number (or number range) gets result-ID 022 (External number).
ROUTE-TABLE is only relevant for Least Cost Call Routing.
ROUTE-TABLE and POINT-CODE are only relevant for Least Cost Call Routing via CCIS.
LOCATION-LOOKUP is used to be able to recognise the own number, when dialled asexternal number.

Assign External Numbering Scheme Number with additional Parameters 328 # !

ASEXTP: <TREE>,<NUMBER>,<TRFC>,<MIN-LENGTH>,<MAX-LENGTH>,
<DIALTONE-PLACE>[,[<TARIFF-CLASS>][,<PAUSE-PLACE>,<INTERVAL>]];
Additional parameters:[<PRE-DIGIT>][,[<POST-DIGIT>][,[<RESTMODE>]
[,[<INTR-ALL>/<CHARGED>][,<ROUTE-TABLE>[,<POINT-CODE>]]]]];

This command is used when the number sent to the opposite exchange must be preceded by a pre-digit
(also called Class-of-Call or Call-type) or followed by a post-digit and/or when the restoration mode and/or
the intrusion allowance (toll-free, ISDN) are used (CSS1). The number (or number range) gets result-ID 022
(External number).

Assign Barred External Number 40 # !

ASBARR:<TREE>,<NUMBER>;
This command is used to bar an external number. The external number must have been defined with
ASEXTN. This means that the result-ID 022 (External number) must be present in the concerning tree. Use
DIDEST to locate the right tree number. In this command this command <NUMBER> can be 1 ... 16 digits.

Erase Barred External Numbers 41 # !

ERBARR:;
All numbers in the barring list will be erased from it.

Display Barred External Numbers 43

DIBARR:;
Response is a list of barred external numbers and the analysis tree number.
--BARRED NUMBER-- ANALYSIS TREE No
xxxxxxxx xx

- 134 -
46. OPERATOR CONSOLE
46.1. B-BUTTON / ACCESS CODE RELATION

CHBBUT and DIBBUT are provided to read and write the relation between B-buttons and trunk access codes.
After a command which modifies this relation has been executed, the other B-button bound data (routes
associated with the access code, B-LED status) are updated by the system. The relation is defined per unit.

Change or Delete Trunk Access Code of B-button 184 # !

CHBBUT:<B-BUTTON>[,<TRUNK-CODE>] [,<UNIT>s/r];
If the trunk access code is omitted, the code under the indicated B button will be deleted.

Display Trunk Access Code of B-button 185

DIBBUT:<B-BUTTON>[,<UNIT>s/r];
Response:
B-BUTTON UNIT TRUNK-CODE
xx xx xx

46.2. QUEUE PREFERENCE

CHMQPR, CHCQPR, CHAQPR modify the answering priority list for the M, C and A call types. DIAQPR,
DICQPR and DIMQPR display the list for A, C and M call types.
The commands which change the answering priority for M and C call types affect the preference for both
the general and individual call queues, the M and C queue preference lists are the same for all operators in
one unit.
The commands for A queues change the priority order in which incoming calls are served by a specific
operator. In case of incoming calls (A calls) there is a preference table for every operator.

46.2.1. A-Queue

Change Answering Priority of A-Queue 188 # !

CHAQPR:<OPERATOR-DNR>,<A1>[,<A2>[,<A3>[,<A4>[,<A5>]]]];
If from a certain An (n=1 to 5) parameter onwards the rest of the parameters are omitted, the preference
list will be set to the default order, with the exception of the values already entered. The default order is 1
to 16 (see parameter An).
If A5 has been entered, the following request appears:

<Enter A-Queues [<A6>[,<A7>...<A13>]]] ...]:

Display Answering Priority of A-Queue 189

DIAQPR:<OPERATOR-DNR>s;
Response:
OPERATOR A-QUEUE PRIORITY LIST (Descending order)
xxxxxx x x x x x x x x x x x x x x x x

- 135 -
46.2.2. C-Queue

Change Answering Priority of C-Queue 187 # !

CHCQPR:[<UNIT>s/r],<C1>[,<C2>[,<C3>[,<C4>[,<C5>]]]];
If from a certain Cn (n=1 to 5) parameter onwards the rest of the parameters are omitted, the preference
list will be set to the default order, with the exception of the values already entered.
The default order is:
(3) = Recall - on hook
(2) = Recall - not on hook
(0) = Direct dial in - not answered
(1) = Direct dial in - unsuccessful
(5) = Taxmetering
(6) = Through connection - busy
(8) = Through connection - ringing
(7) = Preferred call
(4) = Series

If C5 has been entered, the following request appears:

<Enter call types [<C6>[,<C7>[,<C8>[,<C9>]]]];

Display Answering Priority of C-Queue 361

DICQPR:[<OPERATOR-DNR>s][,<UNIT>s/r];
One or both parameters must be omitted. If both parameters are omitted, the answering priority is
displayed for all operators in all units of the system.
Response:
OPERATOR-DNR UNIT CODE CALL-TYPE
xxxx x x xxxxxxxxxxxx

46.2.3. M-Queue

Change Answering Priority of M-Queue 186 # !

CHMQPR:[<UNIT>],<M1>[,<M2>[,<M3>]];
If both M2 and M3 are omitted, the preference list will be set to the default, with the only exception of M1
as first element (and the former default first element in the default position of M1). The default order is:
preferred call (2), normal call (1), individual call (0).

Display Answering Priority of M-Queue 362

DIMQPR:[<OPERATOR-DNR>s][,<UNIT>s/r];
Response:
OPERATOR-DNR UNIT CODE CALL-TYPE
xx xx x XXXXXX

- 136 -
46.2.4. Queue to Lamp Relation

Change Queue Lamp Relation 423 # !

CHQLMR:<LAMP-ID>,<INTERNAL-CALL-TYPE/A-QUEUENUMBER>[,<UNIT>];
If UNIT is omitted the command will be executed system wide.

Display Queue Lamp Relation 422

DIQLMR:[<LAMP-ID>][,<UNIT>s/r];
If LAMP-ID is omitted, all LAMP-IDs are displayed. If UNIT is omitted the command will be executed system
wide.
Response:
UNIT LAMP QUEUE LIST
xx xx xx

46.3. OPERATOR AVAILABILITY LIST AND ASSISTANCE GROUP

CHOPAV and DIOPAV are used to determine and read the order in which the units have to be hunted for
operator service when a unit does not offer operator service to the calls originated in it. This sequence is
defined per unit and per assistance group.

46.3.1. Availability List

Change Operator Availability List 190 # !

CHOPAV:<UNIT>[,[<ASSIST-GROUP>][,<U1>[,<U2>[,<U3>[,<U4>]]]]];
If from a certain Un (n=1 to 5) parameter on all parameters are omitted the availability list will be initialized
only with the entered Un-1 units data.
If U4 has been entered, the following request appears:

<Enter none to 9 additional unit numbers [<U5>[,<U6>... [,<U13>] ... ]];

Display Operator Availability List 191

DIOPAV:[<UNIT>s/r][,<ASSIST-GROUP>];
If the unit number is omitted the command is performed system wide. Unit numbers in the availability list
are displayed in descending order of priority.
The display format is:
UNIT Assist-group Availability list (Descending order)
xx xx xx

46.3.2. Assistance Group

CHASOP, DIASOP, CHASCV and DIASCV define and read the relation between assistance groups and
operators and between assistance groups and CV values. The purpose is to split up the system for multi
user operation.

- 137 -
Change Assistance Group of Compatibility Value 194 # !
CHASCV:<CV>s/r[,<ASSIST-GROUP>];

Change Assistance Group of Operator 192 # !

CHASOP:<OPERATOR-DNR>s[,<ASSIST-GROUP>];
If the assistance group is omitted the general assistance group will be taken. The operator must have
inactive status: Headset removed (i.e. night mode) or global status OUT or NIN.

Display Assistance Group of Operator 193

DIASOP:<OPERATOR-DNR>s;
If no assistance group is displayed the operator is assigned to the general assistance group.
Response:
OPERATOR ASSISTANCE-GROUP
xxxx xx

Display Assistance Group of Compatibility Value 195

DIASCV:<CV>s/r;
If no assistance group is displayed the general assistance group is related to this compatibility value.
Response:
CV ASSISTANCE GROUP
xx xx

Display Service Mode of Assistance Groups 366

DISEMD:[<ASSIST-GROUP>s/r];
The service mode indicates the DAY or NIGHT condition of the operators. If the assistance group is omitted
the general assistance group is displayed.
Response:
ASSIST-GROUP SERVICE MODE
xx xxxx

Change Assistance Group Properties 476 # !

CHASPR:[<ASSIST-GROUP>],<ASSIST-GROUP-PROPS>[,<UNIT>];
This command can switch operator monitoring ON or off. If it is switched on, the command will ask for an
additional parameter:

Enter 'Operator monitoring logical device name' (LDN) :<LDN>

If you type ' ; ' the LDN is not changed.

When ASSIST-GROUP is omitted, the general assistance group is changed.

Display Assistance Group Properties 477

DIASPR:[<ASSIST-GROUP>][,<UNIT>];
Response (example) :
UNIT ASSIST-GROUP PROPERTIES MIS-LDN
2 - 00
2 1 01 xxx

- 138 -
46.4. OPERATOR STATUS

The commands in this group are used to inform the chief operator about the condition of all operator
consoles.

Display Activity and Status of Operators 365

DIOPST:[<OPERATOR-DNR>s][,<UNIT>s/r];
This gives information about the activity (active or not active) and about the state (idle, busy, OM mode).
One or both parameters must be omitted. If both parameters are omitted the status of all operators in the
system is displayed.
Response:
OPERATOR-DNR UNIT ASSIST-GROUP ACTIVITY STATUS
xxxx xx xx xxx xxx

Display List of Active Operators 363

DIOPAC:[<ASSIST-GROUP>s/r][,<UNIT>s/r];
If UNIT is omitted, all operators in the system are displayed. If the assistance group is omitted, the general
assistance group is displayed.
Response:
OPERATOR-DNR UNIT ASSIST-GROUP
xxxx xx xx

Display List of Idle Operators 364

DIOPID:[<ASSIST-GROUP>s/r][,<UNIT>s/r];
If UNIT is omitted, all operators in the system are displayed. If the assistance group is omitted, the general
assistance group is displayed.
Response:
OPERATOR-DNR UNIT ASSIST-GROUP
xxxx xx xx

Display Load of Operators 367

DIOPLD:[<OPERATOR-DNR>s][,[<UNIT>s/r][,<QUEUE-DISPLAY>]];
The first two parameters can not be used simultaneously. If the first two parameters are omitted, the load
of all the operators in the system will be displayed.
One can choose with <QUEUE-DISPLAY> to display either the load on the queues signalled by :

- LEDs A1, A2, A3, A4, C, M1, M2 (default) or

- LEDs U2/A5, U3/A6, U4/A7.

Response:
DNR UNIT A:L C A1:L C A2:L C A3:L C C:L C M:L C TOTAL
xxxx xx x x x x x x x x x x x x xx

Display Load and Status of Operators Continuously 343

DIOPCT:[<OPERATOR-DNR>][,[<UNIT>][,<QUEUE-DISPLAY>]];
The first two parameters can not be used simultaneously. If the first two parameters are omitted, data
about the unit where the OM terminal is located will be displayed.

- 139 -
One can choose with <QUEUE-DISPLAY> to display either the load on the queues signalled by :

- LEDs A1, A2, A3, A4, C, M1, M2 (default) or

- LEDs U2/A5, U3/A6, U4/A7.

The displayed information is refreshed periodically, with a default of 15 seconds.

Response:
DNR ACTIVITY STATUS A:C L A1:C L A2:C L A3:C L C:C L M:C L M2:C L TOTAL
xxxx xx xx x x x x x x x x x x x x x x xx

C indicates the number of calls waiting.

L indicates the first or second overload :

- L=1 : First overload level. The call is waiting and all operators are busy.
- L=2 : Second overload level. The call is waiting for more than 20-40 seconds, or more calls are
waiting.

- 140 -
47. OVERLAY MODULES
These OM commands (except DIOVLM) related to overlays are not relevant anymore in systems with the
latest releases.

Delete Specified Overlay Module from Memory 86 #

DEOVLM:<OVERLAY-ID>s[,<UNIT>s/r];

Display Overlay Modules in Memory 87

DIOVLM:[<OVERLAY-ID>s][,<UNIT>s/r];
If the overlay identity is omitted, all overlays are displayed.
Response:
UNIT OVERLAY-ID REFERENCE LOAD-STATUS CURR-AUTH
xx xxxxx.xxx xxx xxx xxx

Load Overlay Module in Memory 85 #

LDOVLM:<OVERLAY-ID>s[,<UNIT>s/r];

Reset Delete Protection of Overlay Module 89 #

REOVLM:<OVERLAY-ID>s[,<UNIT>s/r];

Set Delete Protection of Overlay Module 88 # !

SEOVLM:<OVERLAY-ID>s[,<UNIT>s/r];

- 141 -
48. PAGING
The following types of paging are defined:
- Virtual paging, using a loudspeaker system;
- Real paging, using paging equipment. This can be further divided into:
- Meet-me paging. The pocket receiver beeps when there is a call waiting.
- Non Meet-me paging. The pocket receiver is equipped with a display or voice channel.

The OM commands can be divided in:

- General commands, which must be executed for both virtual and real paging;
- Commands for virtual paging;
- Commands for real paging (Meet-me and Non Meet-me).

48.1. GENERAL PAGING

The commands in this section are used to create and/or display the paging area(s) and paging routes.

Create Paging Area 246 # !

CRPARE:<AREA>[,<UNIT>];
Each paging area has one unit, where the paging equipment is connected (ATU-PA in case of real paging).
This is called the Utility-unit, <UNIT> indicates this Utility-unit. This Utility-unit must also be given in case
of virtual paging, although no paging equipment is connected.

Change Paging Area 248 # !

CHPARE:<UNIT>[,<AREA>];
This command is used to add units to an existing paging area. This means the command can only be
executed in a multi unit system.

Display Paging Area Data 258

DIPARE:<AREA>;

Erase Paging Area 247 # !

ERPARE:<AREA>;

Create Paging Route 249 # !

CRPART:<AREA>,<ROUTE>[,<MIN>,<MAX>];
If MIN and MAX are given, a real route is created, else a virtual route is created for later use in OM
command ASPACD. The difference between minimum and maximum number length equals the number of
digits that can be post dialled.

Display Paging Route Data 257

DIPART:<ROUTE>;
Response:
ROUTE MIN MAX AREA UTILITY-UNIT VR-TYP
followed by the mode digits (real paging) or the virtual codes (virtual paging)

- 142 -
Erase Paging Route 250 # !
ERPART:<ROUTE>;

48.2. VIRTUAL PAGING

Assign Code to Virtual Paging Route 253 # !

ASPACD:<ROUTE>,<PAGING-CODE>s/r;
PAGING-CODE must be unique in the system. Conflicts with codes used for real paging are possible. No on-
line check can be performed on this.

Delete Code from Virtual Paging Route 254 # !

DEPACD:<ROUTE>,<PAGING-CODE>s/r;
PAGING-CODE may not be in use by the application.

48.3. REAL PAGING

Assign Line to Real Paging Route 255 # !

ASPALN:<ROUTE>,<SHELF>,<BRD>,<CRT>;

Change Real Paging Route Mode Digits 252 # !

CHPAMD: <ROUTE>,<REAL-TYPE>,<MD-TYPE>[,[<DIGIT-INT>][,[<DIGIT-EXT>]
[,<DIGIT-ASSIST>]]];
Refer to the documentation of the paging equipment to see if mode digits for urgent and non-urgent and
for assisted, external and internal paging are supported.

Change Real Paging Route Number Length 80 # !

CHPANL:<ROUTE>,<MIN>,<MAX>;

Delete Line from Real Paging Route 256 # !

DEPALN:<ROUTE>,<SHELF>,<BRD>,<CRT>;
The line may not be in use by the application.

Display Paging Line Data 259

DIPALN:<SHELF>,<BRD>s/r,<CRT>s/r;
Response:
SHELF BRD CRT ROUTE
xx x x xxx

- 143 -
49. PASSWORD PROTECTED FACILITIES
49.1. ASSIGN PASSWORD

This group of commands is used to control the Integrated Password Dialling (IPD) process.

Assign Access to Password Protected Facilities 463 # !

ASAPPF:<DNR>s/r[,<FAC-INDICATOR>s/r];
ASAPPF is used to assign access to the password related facilities like :
- Traffic class up-/downgrading
- Password DDO and Change Password
- Desksharing
- IP Phone registration

When Traffic class up-/downgrading or Password DDO (or both) is assigned, the Change Password facility is
assigned implicitly. When a facility is assigned to a DNR for the first time, the associated password is set to
the default value (all zeros). An extension user has to change this default password to a 'real' password
before it can be used.
When password protection is set for IP Phone registration (FAC-INDICATOR = 2), registration to the IP
CallManager is only possible with the DNR and password. The DNR and password are separated by a "#". An
example of a registration string is : 2301#123456.
If the facility indicator is omitted, the password is reset to all zeros for that DNR.
OM command ASINTN is used to specify the password length (Result-ID 104).
The maximum password length is 16 digits/keypad characters (0 ... 9, * and #).

Improved Security of Password (since SIP@Net 5.1.3)

In case the password length is more than 3 digits/keypad characters and to avoid that then simple
passwords like 1111, 9999, 1234 and **** are used, the following new password rules for the facilities
using IPD are implemented. The password may not contain :

- 4 consecutive identical digits/characters, e.g. 122223 or 999936 or 1****5

- 4 consecutive incremental digits/characters, e.g. #1234# or *4567* or 389*#3
- 4 consecutive decremental digits/characters, e.g. 5432 or 4321 or #*98

Erase Access to Password Protected Facilities 464 # !

ERAPPF:<DNR>s/r[,<FAC-INDICATOR>s/r];
If the facility indicator is omitted, all password protected facility relations for the entered DNR are erased.
If the password protected facility "Traffic class up/downgrading" (FAC-INDICATOR=0) is erased or all
password protected facilities are erased, then the traffic class of the extension is changed to day/night
switching mode.

Display Access to Password Protected Facilities 465

DIAPPF:[<DNR>s/r][,<FAC-INDICATOR>s/r];
Passwords are never displayed, only an indication is given whether the default password is still set. If both
parameters are omitted, all relations are displayed.
Response:
DNR FACILITY INDICATOR DEFAULT PASSWORD
1672 0 : Up/downgrading traffic class Yes
1 : Password DDO
3470 0 : Up/downgrading traffic class No

- 144 -
49.2. COSTCENTRES

Assign PID, Cost Centre Number or Budget 466 # !

ASPICC: <PID/COST-CENTRE>s[,[<TRFC>][,[<DNR>][,[<BUDGET>]
[,[<BUDGET-UNIT>][,<TAC>]]]]];
ASPICC is used to assign a Personal IDentification code (PID), a budget or Cost Centre relations.
In case of a PID also a traffic class value must be entered and optionally a DNR.
When a BUDGET is entered and the DNR is omitted, a general PID is assigned.
In a multi-unit configuration, BUDGET-UNIT must be entered.

Note : Since SIP@Net 5.3.4 onwards one can specify per PID/CC number whether the user has to dial a TAC
or not. In case parameter TAC is projected, after dialling the PID/CC prefix and number, the user
hears external dial tone and needs to dial the external number only to make an external call.
When no TAC is projected for this PID/CC dialling facility, a TAC has to be dialled.

Change PID Data 513 # !

CHPICC: <PID/COST-CENTRE>s,[<TRFC>][,[<DNR>][,[<BUDGET>],
[<BUDGET-ACTION>][,[<BUDGET-UNIT>][,<TAC>]]]];
CHPICC is used to change Personal IDentification codes (PID), budgets or cost centre relations.
If the value of BUDGET-ACTION is :
- 0 : the value of the BUDGET will be subtracted from the budget stored in the database.
- 1 : the value of the BUDGET will be added to the budget stored in the database.
- 2 : the value of the BUDGET will be reset to the value of the budget.

It is not possible to change the BUDGET and BUDGET-UNIT at the same time with BUDGET-ACTION 0 and 1.

Erase PID or Cost Centre Number 467 # !

ERPICC:[<PID/COST-CENTRE>s][,<DNR>s/r];
It is not allowed to omit both parameters. If the PID/COST-CENTRE number is omitted, the DNR must be
given. In that case all PID numbers for that DNR are erased.

Display PID or Cost Centre Numbers 468

DIPICC:[<PID/COST-CENTRE>s][,<DNR>s/r];
If both parameters are omitted, all possible PID / Cost Centre numbers are displayed.
Response:
<DIPICC:;
PID/COST CENTRE TRFC DNR BUDGET BUDGET-UNIT TAC

112233 6 1300 80 1 0
445566 5 1355 100 1 0
778899 7 1356 - - -
112233445566 7 - 300 1 -

- 145 -
49.3. TIME BASED CALL BREAK AT ZERO BUDGET

Assign Tariff Structure 562 # !

CHTRIF: <TARIFF-CLASS>[,<INITIAL-TARIFF>,<TIME-PERIOD>,<DEFAULT-TARIFF>,
[<TARIFF-2>[,<TARIFF-3>[,<TARIFF-4>[,<TARIFF-5>]]]]];
When only parameter <TARIFF-CLASS> is entered, the tariff class is deleted.
Parameter <TIME-PERIOD> is specified in seconds.
When the optional parameters <TARIFF-2...5> are omitted a tariff structure is assigned with only one
tariff.

Display Tariff Structure 563 !

DITRIF:<TARIFF-CLASS>s/r;
Response:
TARIFF-CLASS INITIAL COST TIME TARIFF TARIFF-2 TARIFF-3 TARIFF-4 TARIFF-5
1 5 40 3 4 2 - -
2 2 20 3 1 - - -

- 146 -
50. PERIPHERAL FILE STORAGE
The 'Peripheral File Storage Mechanism' (PFSM) function is a generic mechanism which offers peripheral
boards and TMP terminals the possibility to transport data of any kind to or from a file on a logical device
(e.g. LBU). Applications within the peripheral boards and TMP terminals can make use of the PFSM function.
An application that wants to use the PFSM function must define some settings related to the way of using it
at the start of the PFSM task.

- the file specification (i.e. file name and extension);

- the maximum allowed file size (only applicable when the application writes to the file);
- the method for writing;
-
Two methods for writing exist:

- Stop writing when the maximum file size is reached.

When the file has reached the maximum size no more data is written to it and the application shall
(normally) close the file. Whether or not the application will stop itself depends on the application.

- Continue writing when the maximum file size is reached.

When the file has reached the maximum size no more data is written to that file. Instead, the file is
closed, renamed to a file where the file extension is changed to 'BAK'. When already such a file with
extension 'BAK' exist, this file will be deleted first. Subsequently a new file with the original file name
and extension is opened. The writing continuous to that file.
This results in two file versions i.e. one file with the original file name and extension (say INFO.EXP)
which is currently used by the application and a file with the original file name but with extension BAK
(INFO.BAK which is the previous INFO.EXP file).

Each PFSM task is associated with a 'task number'. A task number relates the additional information of
applicable SAS alarms with the concerned file. The task number is visible by OM and after release in the log
file PDFSuu.LOG on the LBU of the unit. This task number is unique within the system.

Two types of OM commands exist related to the PFSM; i.e. OM commands to manage the PFSM function
itself and OM commands related to applications that use the PFSM function. An example of such an
application is the PPH Protocol Tracer, or the Integrated PM Observer (IPMO, in combination with PMC-G
with package 1810.03.01).

50.1. PERIPHERAL FILE STORAGE MECHANISM

With the following commands you can control the logical device assigned for the Peripheral File Storage
Mechanism.

Change Peripheral Data Output Device 525 # !

CHPDOD:[<LDN>][,<UNIT>s/r];
Defines to which device the peripheral data file(s) will be sent.
Changing the LDN does not influence file(s) which were already opened.
When the LDN is omitted, the LBU of the unit becomes the output device for peripheral data.

Display Peripheral Data Output Device 526 !

DIPDOD:;
Displays of all units the LDN defined as peripheral data output device.

- 147 -
Response:
UNIT DEVICE-NAME
xx xxxxxxx

The command is executed system wide and displays per unit the peripheral data output device.
With the following commands you can control the status of peripheral files (displaying/closing files).

Change Peripheral Data File Status 527 !

CHPDFS:<TASK>[,<RENAME-AND-REOPEN>];
Each PFSM task is associated with a task number. This task number is unique within the system.

This OM command changes the status of the file related to an application that uses the PFSM function. The
file status can be changed in two ways :

- The file is closed. This implies that the PFSM task for the application, which had opened the file, is
finished.
- The file is closed and renamed to a file with the same file name but with extension 'BAK'. When the
'BAK' file with the same file name already exist this file will be deleted first. Subsequently a new file is
opened with the same file name and extension as the original file.
- This implies that the PFSM task for the application continuous: The application uses the newly opened
file. When during the executing of this command something fails, this will be notified with a specific
error message on the OM terminal.

When RENAME-AND-REOPEN = 1 (yes) (only applicable for write tasks), the file (assume the name is
name.txt) will be closed and renamed to name.bak. Subsequently a new file name.txt will be opened (the
write task continues).

When RENAME-AND-REOPEN = 0 (no), the file will be closed (the read or write task is finished) but no
renaming and reopening will take place.

When RENAME-AND-REOPEN is omitted, the default value NO will be assumed.

Display Peripheral Data File Status 528 !

DIPDFS:[<TASK>s/r][,<UNIT>s/r];
Displays information related to the file(s) of not finished task(s).
Finished tasks can be found in the log file PDFSuu.LOG on the LBU of the unit.
When TASK is omitted, the file status concerning all running tasks within the unit(s) are displayed.
Specifying both parameters is not allowed.
Response:
TASK PERIP-DATA-FILE SHELF BRD CRT BSP-ID APPL-ID R/W MAX-FILE-SIZE
xxxxx xxxxxxxxxxxxx xxxxx xx xx xxxxxx xx x xx

STOP-AT-M-F-S START-TIME PASSED-BYTES ERRORS OVERWRITTEN-FILES

- 148 -
50.2. PPH PROTOCOL TRACE

Start Peripheral Circuit Trace 519 !

STRTPT: <SHELF>,<BRD>,<FILE-NAME>.<EXTENSION>,<MAX-FILE-SIZE>,
<STOP-AT-MAX-FILE-SIZE>;
Note that <FILE-NAME> must be a non-existing file name.
The additional parameter <CRT>[&&<CRT>] defines the circuit or circuit range to be traced.
It can be terminated by entering a semi-colon (;).
You are asked for confirmation if old trace data has to be saved.
Examples of circuit numbers :

- DTU for ISDN/QSIG : CRT 0

- DTU for DPNSS : CRT 1&&15 and 17&&31
- DTX-I for ISDN/QSIG : even CRT 2, 4, 6, etc.
- DTX-I for DPNSS : CRT 2&3, 4&5, 6&7, etc.
- PMC-G : no circuits have to be specified : the whole SHELF is captured.

Stop Peripheral Circuit Trace 520 !

STOPPT:<SHELF>,<BRD>;
If this action is succesfull then the filename of the the stopped trace file is displayed.
Apart from stopping the trace application via this command, the trace application is implicitly stopped
when certain situation occurs. This is indicated by "REASON FOR STOPPING" in the log file. An example of
the PDFSuu.log file (with two ended tasks) is given below.

TASK FILE-ID EHWA BSP-ID APPL MAX-F-S R/W STOP-AT-M-F-S

1000 LBU01:TRACE.POM 12 7 - 0 4 W No

STARTED STOPPED LOST-FILES ERRORS REASON-FOR-STOPPING

2013-01-30 +11:00 2013-01-30 +11:30 0 No 1

Display Peripheral Circuit Trace Information 521

DIPCRT:<SHELF>,<BRD>;
The following information is displayed when a trace is in progress:

SHELF BRD OUTPUT-FILE MAX-FILE-SIZE STOP-AT-MAX-FILE-SIZE

xxxxx xxx xxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxx
BOARD-FREE-MEMORY DATA-IN-MEMORY LOST-MESSAGES
xxx xxx xxx
CIRCUIT
xxxxxxx

- 149 -
51. PRIVATE VIRTUAL NETWORKING
This group of OM commands is used for maintaining and displaying data used by iSNet Private Virtual
Networking (PVN).
A Compressed PVN route is a PVN route for which a voice compressor board (DTU-VC) is used.
The DTU-VC used for compressed mode PVN, must have signalling group number 6504 without further
circuits. Thereupon circuit 5 (circuit for the DNR) of the DTU-VC must have signalling group 6504 and PCT
type LCT.
In case of iPVN, parameter SIGCH-ADDRESS in OM command CHPVNR is the IP address of the CIE-2/
CPU3000 of the opposite ISPBX.

Change PVN Route 457 # !

CHPVNR:<ROUTE>[,[<SIGCH-ADDRESS>],[<UCA-PREFIX>],<RIN>,<M/S>];
With this command, PVN route data can be changed, added or deleted. A route is a PVN route when it
contains at least one bundle with signalling type DPNSS-PVN.
This command asks for additional parameters:
Enter [<PVN-MODE>][,[<CV>][,[<TREE>][,<USER-MODE>]]]:

- Add a PVN route : all parameters have to be given. In case of an incoming route, the SIGCH-
ADDRESS and the UCA-PREFIX may be omitted.
- Change a PVN route : all parameters have to be given.
- Delete PVN route data : only enter the route number.

<TREE>
This is the tree where the analysis for the parameter <SIGCH-ADDRESS> is started. Using
a tree other then initial the dialling tree keep telephone users from dialling the signalling
channel address manually. The special tree only makes sense if the route is only used for PVN
calls and is not e.g. the route to the PSTN which also handles all the normal PSTN calls.

<USER-MODE>
• 0 = normal PVN
The user channel is answered by the destination PBX immediately; the destination party may not have
answered the telephone or may not be answered at all. This results in a faster user channel setup than
the option "delayed" but it is only recommended for leased lines where there is no cost issue.

• 1 = delayed PVN
The user channel is answered by the destination PBX when the destination party answers the call.
Recommended for PVN user channels through the PSTN where metering starts at the receipt of an
answer signal. In this case the bundle option “DDO local ring tone provided“ of the PVN route must be
set to 1.

Display PVN Route Data 459

DIPVNR:[<ROUTE>][,<UNIT>];
Response examples:

<DIPVNR:7;
ROUTE UNIT SIGCH-ADDRESS
7 1 192.168.1.36
UCA-PREFIX RIN M/S
781 2221 0
PVN FLOWS
MODE CV TREE STATUS EHWA-HATCH USER-MODE ACT EST START-TIME
0 0 0 idle - - - delayed 0 0 -

- 150 -
<DIPVNR:8;
ROUTE UNIT SIGCH-ADDRESS
8 1 fd01:aaaa:0:22:9d5a:6660:4d5d:8102
UCA-PREFIX RIN M/S
784 2224 1
PVN FLOWS
MODE CV TREE STATUS EHWA-HATCH USER-MODE ACT EST START-TIME
0 0 0 idle - - - delayed 0 0 -

- The EHWA of the used hatch resource is given,

- The STATUS now can be: idle, claimed, set up, identify, wait, ready, released, reserved or POM,
- When a specific route is given as parameter for DIPVNR (e.g. DIPVNR: 123) then the display is
continuous. When data is changed, the changes are displayed on the screen.
- CTRL-X stops the continuous display.

The start time of the signalling is shown, the number of active flows (user channels and virtual calls) and the
number of establishing flows (calls in set-up phase).

Change PVN Compressor DNR 495 # !

CHPVND:[<DNR>][,<UNIT>];
The PVN compressor DNR is the DNR (or group DNR) via which a voice compressor (DTU-VC) is occupied
when a compressed PVN route is to be set up.
If DNR is omitted, then the compressor DNR is deleted.
UNIT may only be omitted in a single unit system. Otherwise, assign the compressor DNR in the same unit
as the compressed PVN route.

Note: The compressor DNR must have BSPT 0 and IBSC 0.

Assign the following FCMs to the compressor DNR: 3 (break in protected), 4 (data protected), 35
(call waiting protected) and 49 (ARB protected).
Assign "no COB" to the compressor DNR (using CHCOBD).

Display PVN Compressor DNR 496

DIPVND:[<UNIT>];
Response:
PVN-COMPRESSOR-DNR
xxxxxx

Assign PVN User Channel Address 455 # !

ASPVNU:<UCA>[,<UNIT>];
The user channel address is the DDI number that an opposite ISPBX must dial to setup a user channel.

Delete PVN User Channel Address 456 # !

DEPVNU:<UCA>[,<UNIT>];
Error message 'UCA busy' may indicate that the specified UCA is in use and cannot be deleted.

Display all PVN User Channel Address(es) 461

DIPVNU:[<UNIT>];
If UNIT is omitted, the command is executed for all units in the system.
Response:
UNIT UCA
xxx xx

- 151 -
Change the PVN Sequence Table 458 # !
CHPVNT: <ROUTE>[,<SEQUENCE-TABLE>[,<SIGCH-TU>,<SIGCH-TV>][,<USRCH-TU>,
<USRCH-TV>]];
Depending on the parameter combination, the PVN sequence table can be changed or (partly) cleared. The
timer values will be changed to 0 seconds.
This command must only be set at the "MAIN" side of the PVN route, because this side controls the
reservation timers.

Display the PVN Sequence Table(s) 460

DIPVNT:<ROUTE>[,<SEQUENCE-TABLE>];
This command displays the contents of one or all sequence tables belonging to the specified route. If the
SEQUENCE-TABLE is omitted, all sequence tables for the specified route are displayed.
Response:
SIGNALLING CHANNEL USER CHANNEL
SEQUENCE-TABLE VALUE TIME-UNIT VALUE TIME-UNIT
1 2 Minutes 2 Minutes
2 2 Minutes 2 Minutes
3 2 Minutes 2 Minutes
4 2 Minutes 2 Minutes
5 2 Minutes 2 Minutes

Change PVN Security Code 472 # !

CHPVNS:[<PTN-ID>];
The PTN-ID is a number that is specified for the network. It is used by the PVN security mechanism during
set-up of a signalling channel to verify if both parties belong to the same network. When the PTN-ID is
omitted, the sytem will return to the default PTN-ID, which is 9999. In this case only the old security code
will be asked. The new security code will also return to its default value. The default security code is
'899111'.
This command asks for additional parameters:

Enter old Security code :<SC>;

[Enter new Security code :<SC>;]
[Verification :<SC>]

All ISPBX's in a PVN network must have the same PTN-ID and security code.

- 152 -
52. PROJECTING
The commands in this chapter are used to:

- Change and display the general PM projecting data, e.g. slave data, signalling group data, tone data and
audio data;
- Change and display the PPH (Peripheral Projecting Handler) projecting data, e.g. PPH data, L1, L2, L3 and
TEI.

Change PM Projecting Data 75 # !

CHPMPD: <PM-OBJECT>,<OBJ-INDEX>[,[<NBR-OF-ITEMS>],[<PERIODICITY>]
[,<UNIT>]];
The NBR-OF-ITEMS and PERIODICITY must be omitted for PM-OBJECTS 0 and 1. If the UNIT is omitted the
command will be executed system wide.

The command will ask for additional parameters, depending on the PM-OBJECT entered :

• PM-OBJECT 0 : Signalling group data.

Additional parameters : <ITEM-NBR>,<BIT/BYTE>[,<DATA>];
If DATA is omitted, the existing data is cleared.

• PM-OBJECT 1 : Slave data.

Depending on the given OBJ-INDEX the additional parameters have the following meaning :
OBJ-INDEX 6 (ATC data):
Additional parameters : <ITEM-NBR>[,<DATA>];
If DATA is omitted the existing data is cleared.
This action is only required for certain PSC tone-PROM-sets. Refer to the signalling data manual for
details.

• PM-OBJECT 1 : Slave data.

Depending on the given OBJ-INDEX the additional parameters have the following meaning :
OBJ-INDEX 8 (Stc tone data):
Additional parameters : <TONE-SRC>,<FREQ-VALUE>;

• PM-OBJECT 1 : Slave data.

Depending on the given OBJ-INDEX the additional parameters have the following meaning :
OBJ-INDEX 9 (Stc level data):
Additional parameters : <TONE-SRC>,<LEVEL-VALUE>;

• PM-OBJECT 2 : PSC tone data (when PPU-(PMU)-PSC hardware is used).

Additional parameters : <ITEM-NBR>[,<TONE-SRC>,<T-VALUE>,<UNIT-T>];
If TONE-SRC, T-VALUE and UNIT-T are omitted, the existing data is cleared.

Note: When PSC data is changed, a warning is given that also the PMC data should be changed.

• PM-OBJECT 3 : Ring data.

Additional parameters : <ITEM-NBR>[,<T-VALUE>,<UNIT-T>];
If T-VALUE and UNIT-T are omitted, the existing data is cleared.

• PM-OBJECT 4 : Ticker data.

Additional parameters : <ITEM-NBR>[,<TICKER-SRC>,<T-VALUE>,<UNITT>];
If TICKER-SRC, T-VALUE and UNIT-T are omitted, the existing data is cleared.

- 153 -
• PM-OBJECT 5 : PMC tone data (when PMC hardware is used).
Additional parameters : <ITEM-NBR>[,<TONE-SRC>,<T-VALUE>,<UNIT-T>];
If TONE-SRC, T-VALUE and UNIT-T are omitted, the existing data is cleared.

Note: When PMC data is changed, a warning is given that also the PSC data should be changed.

• PM-OBJECT 6 : Direct downloadable signalling group data to PM.

Additional parameters : <ITEM-NBR>,<BIT/BYTE>[,<DATA>];

If DATA is omitted the existing data is cleared. During download the OM terminal locks.
There are no messages given about what is downloaded directly and what not.
You can check this with the DIPMPD command.
If not all items are changed in the PM data, still a warm start or SETOUT/SETINS of the PM is necessary.
The signalling data manual describes which data can be downloaded directly.

Display PM Projecting Data 76

DIPMPD: <PM-OBJECT>[,[<OBJ-INDEX>][,[<ITEM-NBR>][,[<BIT/BYTE>]]]
[[,<SHELF>/<UNIT>][,<BRD>]]];
Response for tone/ring/ticker functions:
PM-OBJ FUNC NR-OF-ITEMS PERIOD ITEM-NR TONE/TICKER-SRC VALUE-T UNIT-T
xxx xx xxx xx xx xx xx xx

Response for slave data:

SLAVE-TYPE ITEM-NBR DATA
xx xx xx

Response for signalling group data:

SIG-GROUP ITEM-NBR DATA
xx xx xx

- 154 -
53. QSIG AND ISDN ADDRESSING
In general "Addressing" is a means of indicating what a series of digits mean (within a certain numbering
scheme). For example to determine that all external numbers starting with a '0' are 'national' numbers,
normally used to make inter-local calls. Addressing applies to both called (dialled) numbers and
calling/connected party numbers.

In older releases, addressing was done using the Complete Number Identification (CNI) function. However
this CNI function only offers one conversion for all PBX parties. It is also not transparent for transit calls and
not really suitable for multi-tenant configurations.

Keep in mind that when QSIG and ISDN addressing is not projected, the CNI function will work as usual.

53.1. LOCAL DOMAIN DATA

Change Local Domain 574 # !

CHLDOM:<LOCAL-DOMAIN-ID>,<NUMBERING-PLAN>;
Creates or changes a Local Domain.
The command asks for additional parameters:
1. Enter Country/Level 2 Code :
2. Enter Area/Level 1 Code :
3. Enter DDI Prefix :
4. Enter International/Level 2 Prefix :
5. Enter National/Level 1 Prefix :
6. Enter Special Services Prefix :
7. Enter Trunk Access Code :
8. Enter Preferred TON for Called Party Number :
9. Enter Preferred TON for Calling/Connected Party Number :
10. Insert Trunk Access Code for CLI/COL with TON unknown :
11. Route defines call back Trunk Access Code for CLI/COL :
12. Enter Numbering plan of CLI in gateway or transit calls :

The additional parameter entries 10 & 11 may have the value '0' (= no) or '1' (= yes).
For all additional parameters either :

- a new value can be given

- the value is not changed by typing ';'
- the value is deleted by typing '-;'

All parameters containing a code or prefix have a length of maximum 6 digits.

NUMBERING-PLAN may have the following values:

- 0 = Unknown : all additional parameters are asked except 6 & 8.

- 1 = E.164 : all additional parameters are asked.
- 2 = PNP : all additional parameters are asked.

In previous releases only one Special Services Prefix could be assigned per Local Domain for Numbering
Plan E.164. The Type Of Number of the Special Services Prefix was defined by the parameters 'Preferred
TON for Called Party Number' or 'Preferred TON for CLI/COL Party'. The maximum length of the Special
Services Prefix was six digits.

- 155 -
OM command CHSSPD is used to be able to specify multiple Special Services Prefixes with a maximum
length of 12 digits per Local Domain/Numbering Plan. It is also possible to define the Called Party
Numbering Plan and Type Of Number belonging to that Special Services Prefix.

Display Local Domain 575

DILDOM:<LOCAL-DOMAIN-ID>sr;
Response example :
DILDOM:1;
LOCAL-DOMAIN DATA ITEMS LDI UNKNOWN E.164 PRIVATE
Local Domain / Numbering Plan assigned 1 - * *
Country/Level 2 Code 31 -
Area/Level 1 Code 20 43
DDI Prefix 593 -
International/Level 2 Prefix 00 -
National/Level 1 Prefix 0 -
Special Services Prefix 1 >
Trunk Access Code 0 -
Preferred TON for Called Party Number 2 2
Preferred TON for Calling/Connected Party Number 2 2
Insert Trunk Access Code for CLI/COL with TON unknown 0 0
Route inserts Trunk Access Code for CLI/COL 0 0
NP of CLI in gateway or transit calls 0 0

> To see the assigned Special Services Prefixes, see command DISSPD.

Erase Local Domain 576 # !

ERLDOM:<LOCAL-DOMAIN-ID>[,<NUMBERING-PLAN>];
Erases a local domain or one of its numbering plans.

If the NUMBERING-PLAN parameter is omitted, the complete local domain is removed, otherwise the data
for that numbering plan is removed from the local domain only.

If there is any DNR or route still using this local domain, it is not possible to remove the complete local
domain or the last numbering plan.

53.2. SPECIAL SERVICE PREFIX

Create / Change Special Service Prefix Domain / Called Party NPI and TON 469 # !
CHSSPD: <LOCAL-DOMAIN-ID>s/r[,<CALLED-PARTY-NP>[,<SSP>[,<SSP-NP>,
<SSP-TON>]]];
This command is used to define multiple Special Services Prefixes per Local Domain andNumbering Plan
and to define the Called Party Numbering Plan (NPI) and Type Of Number (TON) belonging to that Special
Services Prefix.

- when all parameters are given a Special Services Prefix (SSP) is defined with the given Numbering Plan
(SSP-NP) and Type of Number (SSP-TON).
- when the Special Services Prefix is already defined for the given Local Domain (LOCALDOMAIN-ID) and
Called Party Numbering Plan (CALLED-PARTY-NP), the entry is overwritten.
- when parameters <SSP-NP> and <SSP-TON> are omitted, the relation is deleted.
- when parameter <SSP> is omitted, all Special Services Prefixes for the given Local Domain and Called
Party NP are deleted.
- when also parameter <CALLED-PARTY-NP> is omitted, all entries for the given Local Domain are deleted.

- 156 -
Display Special Service Prefix Domain 470
DISSPD:<LOCAL-DOMAIN-ID>s/r
This command shows all the Special Services Prefixes that are defined for the given Local Domain.
Response example :
<DISSPD:1;
LOCAL DOMAIN CALLED-PARTY-NP SPECIAL-SERVICES-PREFIX SSP-NP SSP-TON
1 1 112 0 0
<EXECUTED

53.3. DNR / ROUTE - LOCAL DOMAIN RELATION

Change DNR to Local Domain Relation 577 # !

CHDNRL:<DNR>sr[,<LOCAL-DOMAIN-ID>];
Assigns a local domain identifier to a DNR.
When the LOCAL-DOMAIN-ID parameter is omitted, the local domain relation is removed from the DNR.

Display DNR-Local Domain Relation 578

DIDNRL:[<DNR>sr][,<LOCAL-DOMAIN-ID>];
- when the parameter DNR is entered (and LOCAL-DOMAIN-ID is omitted), the relation local domain -
DNR is displayed.
- when the LOCAL-DOMAIN-ID parameter is entered (and DNR is omitted), all DNR's assigned to the local
domain are displayed.

Response example :
DIDNRL:,1;
DNR LOCAL-DOMAIN
1300 1
1301 1

Change Route to Local Domain Relation 579 # !

CHRTLD:<ROUTE>sr[,<LOCAL-DOMAIN-ID>];
When the LOCAL-DOMAIN-ID parameter is omitted, the local domain relation is removed from the route.

Display Route-Local Domain Relation 580

DIRTLD:[<ROUTE>sr][,<LOCAL-DOMAIN-ID>];
- when the ROUTE parameter is entered, the relation local domain - route is displayed but then the
LOCAL-DOMAIN-ID parameter must be omitted.
- when the ROUTE parameter is omitted (and only LOCAL-DOMAIN-ID is entered), all routes assigned to
the local domain are displayed.

Response example :
DIRTLD:,1;
ROUTE LOCAL-DOMAIN
1 1
2 1

- 157 -
53.4. LOCATION DETERMINATION DATA

Change Location Determination Data 581 # !

CHLODD: <NUMBERING-PLAN>,<TYPE-OF-NUMBER>,<ORIG-DIGIT-STRING>
[,<NEW-DIGIT-STRING>];
Creates, deletes or changes an entry in the table concerning location determination.

- when the NEW-DIGIT-STRING has been entered and the relation is not present yet in the table, the
relation is created else it is changed.
- when the parameter is omitted, the relation is removed.

Both the ORIG-DIGIT-STRING and NEW-DIGIT-STRING parameter have a length of maximum 20 digits.
Wildcards are indicated with '%' at the end of the string.
The last '%' means 'one digit or more'.
The number of '%' characters in the NEW-DIGIT-STRING may not be more than those in the ORIG-DIGIT-
STRING.

Example
For an iS3000 system in Holland (country code 31), Hilversum (area code 35) with DDI prefix 689 and a 4
digit internal number range 1xxx, the following has to be exeuted :

CHLODD:1,3,31356891%,1%;
CHLODD:1,2,356891%,1%;
CHLODD:1,1,6891%,1%;

Since SIP@Net 5.0 there is no longer the restriction that the location entry has to be unique. The new
behaviour is applicable for all NPI’s and TON’s.

SIP@Net will look for a best matching entry, instead of an exactly matching entry. This offers the possibility
to convert string 31356891% to 1%, but to convert all other strings starting with 3135% to 0035% and all
remaining strings % to 000%.

Be aware that using overlap receiving in this example will result in a direct match after dialling the first digit.
This can be avoided by forcing a minimum number length by using multiple % in the original digit string, so
in this case you could say %%%% will become 000%%%%.

Display Location Determination Data 582

DILODD:<NUMBERING-PLAN>[,<TYPE-OF-NUMBER>[,<ORIG-DIGIT-STRING>]];
Displays the content of the location determination table, either for all relations within a numbering plan or
for a specific relation in a numbering plan.

- when only the first parameter is entered, all relations for that numbering plan are displayed. When the
second parameter is given also all relations for the location for that Type Of Number (TON) are displayed.
- when all parameter are given one relation is shown.

Response example :
DILODD:1;
NUMBERING-PLAN TYPE-OF-NUMBER ORIG-DIGIT-STRING NEW-DIGIT-STRING
1 3 31356891% 1%
1 2 356891% 1%
1 1 6891% 1%

- 158 -
53.5. NUMBERPLAN CONVERSION

Change Numbering Plan Conversion Data 583 # !

CHNPCD: <ORIG-NUMB-PLAN>,<NEW-NUMB-PLAN>,<ORIG-TON>,
<ORIG-DIGIT-STRING>[,<NEW-TON>,<NEW-DIGIT-STRING>];
Creates, deletes or changes an entry in the table concerning numbering plan conversion.

- when NEW-TON and NEW-DIGIT-STRING are present, the relation is created or changed.
- when they are omitted, the relation is removed.

It is also possible to assign Numbering Plan Translations (only for Calling/Connected party numbers) within
the same numbering plan, for example :

" NPI E.164, TON Unknown, number 03512345678 " to

" NPI E.164, TON National, number 3512345678 ".

Display Numbering Plan Conversion Data 584

DINPCD: <ORIG-NUMB-PLAN>[,<NEW-NUMB-PLAN>[,<ORIG-TON>
[,<ORIG-DIGIT-STRING
Displays the content of the conversion table, either for all relations within a numbering plan or for a specific
relation in a numbering plan.

- when only the ORIG-NUMB-PLAN is entered, all relations for that numbering plan are displayed.
- when also the NEW-NUMB-PLAN is given also all relations for the conversion between both numbering
plans are displayed.
- when ORIG-TON is given, all relations with a certain TON for the conversion between both numbering
plans are displayed.
- when all parameter are given one relation is shown.

53.6. QSIG FACILITY SELECTION

In principle, interworking between QSIG defined facilities and DPNSS facilities on top of QSIG is not
supported. The exceptions on this rule are the Basic Call, Identification Services, the interworking between
DPNSS Loop Avoidance and QSIG Transit Counter and the facilities which can be selected using OM
command CHQFSM.

Change QSIG Facility Selection Method 592 #

CHQFSM:<QSIG-FACILITY>s/r,<PROPRIETARY-OR-QSIG>;

Display QSIG Facility Selection Method 593 !

DIQFSM:[<QSIG-FACILITY>s/r];

- 159 -
53.7. INTEROPERATION WITH THE COMPLETE NUMBER IDENTIFICATION (CNI) FUNCTION

If no addressing is projected at all (no local domains defined/assigned), Complete Number Identification
(CNI) will still work as usual. When addressing is projected while also CNI is activated (for ISDN), conversion
of explicit address is done partly by the PPH and partly by the CPU.

The CNI function can be projected using OM command CHPMFU.

See the "Second Line Maintenance Manual" for more details.

Change PM Function 499 !

CHPMFU:<PM-FUNCTION>,<UNIT>;
This command can be used to change the PM-function “Complete Number Identification” (CNI)

Display PM Function 504 !

DIPMFU:<PM-FUNCTION>[[,<SHELF/UNIT>][,<BRD>]];

- 160 -
54. REMOTE MAINTENANCE
Change Remote Maintenance Configuration (not for CCS) 427
CHREMC:<REMOTE-USER-GROUP>[,<UNIT>];
This OM command is only relevant for CPU3000 systems. Remote maintenance for CCS systems is
programmed by a menu option on the Backup and Interface Module (BIM).

Data can be entered for two remote user groups: 0 and 1. In this way two logical groups of users can be
defined using the remote maintenance function (e.g. service organisation and customer organisation). This
user group is used by the SSM/SysManager to identify itself as being part of the service or customer
organisation.

Note: To activate the new changes made by CHREMC, the port has to be taken out of service and back to
in service again.

The command will request a new value for all fields, displaying the values or strings already present (with
the exception of the password). If the RMAINx.CNF file is new, the default values will be displayed. If only a
semi-colon is given, the contents of the field will be unchanged. If a space followed by a semi-colon is
entered the field is cleared.

The table below shows an example of the remote configuration. Note that the CPU3000 supports the Hayes
protocol only.

DESCRIPTION MAX SIZE DEFAULT VALID CHARACTERS

Password 6 chars RMAINT All upper case ASCII chars
Number of connection attemps 255 6 0 ... 9
1 = Connect allowed
Connection setup command 2 1 2 = Dial back allowed
3 = Both allowed
Subscriber number 0 ... 9 (Dial back
22 digits --- See Modem Manual
number)
0 (must be
Calling station identification ---
empty)
Number of retries 255 5 0 ... 9
Time (in units of 10 seconds) between
255 12 0 ... 9
retries
System identification 30 chars --- All ASCII chars
Hayes modem initiation string 0 40 chars --- All ASCII chars
Hayes modem initiation string 1 40 chars --- All ASCII chars

Note: Subscriber number 0 is the remote alarm number.

Subscriber number 1 is the fall-back remote alarm number.

The changed data is stored in a datastructure in the RAM.

- 161 -
The minimum requirements for modems at the ISPBX side are:
- Hayes AT command interface (via V.24 port);
- V22, V22bis, V32;
- AT commands: ‘ATH', ‘ATDT' and ‘ATZ';
- ATZ is used to return to stored profile;
- DCD circuit follows carrier (only HIGH if connection available);
- No command echoing (ECHO OFF);
- Results are given and are in text form;
- Dial-up telephone line;
- Escape sequence default ‘+++';
- Escape sequence guard time 1 second;
- Carriage return character ‘0D' (hex);
- AT-command string of more than 1 command e.g. ATE0V0S0=1;
- Error correction disabled;
- Flow control disabled;
- Data compression disabled;
- AUTO ANSWER mode.

Example of the CHREMC:

<CHREMC:0,3;
Password in configuration file [... ...] :; Entered password is not shown
Number of connect attempts [010] :002;
Connection setup command [1] :2;
Subscriber number 0 [0W035:6891234] :0W0356894321; Content of field changed
Subscriber number 1 [0W035:6891111] : ; Content of field cleared
Subscriber number 2 [0W035:6892222] :; Content of field not changed
Subscriber number 3 [ ] :;
Subscriber number 4 [ ] :;
Subscriber number 5 [ ] :;
Subscriber number 6 [ ] :;
Subscriber number 7 [ ] :;
Subscriber number 8 [ ] :;
Subscriber number 9 [ ] :;
Calling station identification [pcs-hilversum] :;
Number of retries [006] :025;
Time interval [012] :;
System identification [pcs-hilversum] :PCS-iS3050;
Hayes initiation string 0 [ ] :&F
Hayes initiation string 1 [ ] :&C1&B1&A0E0S0=1X0S14=1
Message 100: The new configuration file is stored
EXECUTED

Note: The characters used in the subscriber number are passed on to the modem. The modem may
recognize the following characters as Hayes commands:
- W. Wait for dial tone,
- @ Wait for silence,
- , Wait some time.

- 162 -
The CPU3000 logs all relevant actions on the remote port. By means of OM commands remote logging
output can be activated (and de-activated). Remote access attempts are always logged.

Change Remote Logging Output Device (CPU3000 only) 436

CHRLOD:[<LDN>][,<UNIT>s/r];
Before logging can be started the output device must be specified by means of command CHRLOD. When a
printer is assigned as output device, this has to be another one as the one possibly assigned for toll-
ticketing.

Display Remote Logging Output Device (CPU3000 only) 437

DIRLOD:;
Response:
UNIT DEVICE-NAME OUTPUT-FORMAT-VERSION
xx XXXXX XX

Start Remote Logging (CPU3000 only) 438

STRTRL:<FILE-NAME>;
The layout of the logging messages is :

Command System id date time group/user or: alarm

DIALBACK ISPBX iS3050 1993-10-26 09:24 0/0
DISCONNECT ISPBX iS3050 1993-10-26 10:36 0/0
CONNECT ISPBX iS3050 1993-10-27 11:03 1/4
DISCONNECT ISPBX iS3050 1993-10-27 11:12 0/0
ALARM ISPBX iS3050 1993-10-27 13:14 0010
DISCONNECT ISPBX iS3050 1993-10-27 13:18 0/0

Stop Remote Logging (CPU3000 only) 439

STOPRL:;
To stop logging output.

Display Remote Logging (CPU3000 only) 440

DISPRL:;
Response:
RL-OUTPUT-FILE RL-STATUS RL-STATUS
XXXXX act act
XXXXX act act

- 163 -
55. SERVICE CONDITIONS
The commands for service conditions are used to change the service conditions of resources or to display
them. The service condition of a resource comprises:

- Required service condition. This is the status the resource should have.
- Actual or current service condition. The status of the resource.
- Owner. The software activity using the resource.
- B-channel status.
- CPU slice mask status.

Certain actions are not allowed:

- Taking the CBU or a higher system part to Out of Service or Not Installed while journal updating is on;
- Taking a module or a higher system part to Out of Service or Not Installed;
- Taking shelves or a higher system part Out of Service or Not Installed.

Other actions must be confirmed:

- Taking the last OM terminal or a higher system part to Out of Service or Not Installed;
- Taking the CBU or a higher system part to Out of Service or Not Installed.

Some resources are classified by a system degradation level, when they are taken to Out of Service (OUT)
or Not Installed (NIN). The user must know the correct password. See chapter System Security.

Display Service Condition 27

DISERV:<SHELF>[,[<BRD>s/r][,<CRT>s/r][,<B-CHANNEL>s/r]]];
The B-CHANNEL parameter is for ISDN only. If no range or series is given in the EHWA the display is
continuous. Use CTRL-X to stop the display.
Response:
SHELF BRD CRT REQUIRED CURRENT OWNER
xxxx xx xx x x x

If the B-CHANNEL parameter is entered the following is displayed:

SHELF BRD CRT B-CH B-CH-STATUS
xxxx xx xx xx xxxxxxx

The B-CH-STATUS can be:

- Free;*)
- Busy;
- Busy and incoming claimed;
- Busy for testing;
- Not usable; *)
- Claimed for ATF-ARB;
- Busy outgoing selection in progress.

*) The status ‘not usable' will be displayed (instead of ‘free') in case no line has been assigned.

Note: If the CRT parameter is an ISDN access and the owner is CP2 (and no B-channel parameter is
present), then an additional counter with the number of CP2-owned channels is shown (range 2 and
upwards).

- 164 -
Display Service Condition of Virtual Channel 360
DIVICH:<SHELF>,<BRD>s/r,<CRT>s/r;
This command is used to display the service condition of virtual channels (DTU-PR/PH/BA boards). If no
range or series is given the display is continuous. Use CTRL-X to stop the display.
Response:
SHELF BRD CRT REQUIRED CURRENT OWNER
xxxx xx xx x x x

Force Service Condition to Out of Service 29 #

FRCOUT:<SHELF>,<BRD>s/r[,<CRT>s/r];
This command is used if a resource never becomes idle. If the circuit number is omitted the board is meant.
If required, a password may be asked for.
Possible responses:
Password for degradation level x: ?
Error 113: Continuation deactivates the CBU. Switch off journal update first!
REJECTED
Error 140: Last OM device may not be deactivated on this ISPBX plattform
REJECTED
Continuation deactivates special device(s)
(e.g. LBU, DBU).
Continue (yes/no)?:

Set Service Condition to In Service 24 #

SETINS:<SHELF>[,<BRD>s/r][,<CRT>s/r];

If the circuit number is omitted the board is meant. If both the circuit and board are omitted the shelf service
condition is meant.

Set Service Condition to Not Installed 26 #

SETNIN:<SHELF>,<BRD>s/r[,<CRT>s/r];
If the circuit number is omitted the board is meant. If required, a password may be asked for.
Response:
Password for degradation level x: ?
Error 113: Continuation deactivates the CBU. Switch off journal update first!
REJECTED
Error 140: Last OM device may not be deactivated on this ISPBX platform
REJECTED
Continuation deactivates special device(s)
(e.g. LBU, DBU).
Continue (yes/no)?:

Set Service Condition to Out of Service 25 #

SETOUT:<SHELF>,<BRD>s/r[,<CRT>s/r];
If the circuit number is omitted the board is meant. If required, a password may be asked for.
Response:
Password for degradation level x:
Error 113: Continuation deactivates the CBU. Switch off journal update first!
REJECTED
Error 140: Last OM device may not be deactivated on this ISPBX platform
REJECTED
Continuation deactivates special device(s)
(e.g. LBU, DBU).
Continue (yes/no)?:

- 165 -
Find Resource with Given Service Condition 28
FISERV:<CONDITION>s[,<UNIT>s/r];
If no unit number is specified, the action is performed system wide.
Response:
SHELF BRD CRT REQUIRED CURRENT OWNER
xxxx xx xx x x x

Display all Resources with Specified Owner 311 !

FIOWNR:<OWNER>s/r[,<UNIT>s/r];
This command 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 "system-wide".
If no resources are found which have the specified ownership, the message "No relations or data found" is
returned.

Display all Resources with given Type and Claim 312 !

FCLAIM:<RESOURCE-TYPE>s/r,<CLAIM-TYPE>[,<UNIT>s/r];
This command 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 "system-wide".
If no resources are found which have the specified claim type, the command will return "EXECUTED" and no
message is returned.

Display the CPU Slice Mask Status (CCS only) 454

DICCSS:[<UNIT>][,<MODE>];
This command continues monitoring the status of the slices until it is terminated by the OM user. In case
parameter MODE = 1 (full display), the processor type on the CCS boards are given.
Response:
SLICE_1 SLICE_2 SLICE_3 SLICE_4
status status status status

Where status can be:

- operational;
- masked;
- synchronizing;
- dual (operational);
- dual (standby).

The OM command DICCSS is modified to be able to read out the processor type for each slice. Now, two
years later, the package is changed in such a way that the minority of CCS slices is automatically masked. In
case of 50/50% mix the 2 'old' slices with MC68360FE will be masked.

WARNING: Before upgrading, first check with OM command DICCSS that you have 4 CCS boards with the
same processor type. If not, you will not have a 4/2 tolerant processor after the upgrade !
Note that it is not relevant which processor type is used, as long as they are all the same.

- 166 -
56. SMS SERVICE
This service allows the analogue terminal, connected to the PBX, to send short messages through the PBX
towards a fixed network terminal and also to receive short messages from a fixed network terminal. The
feature is only available via ISDN trunks.

The way SMS is activated from a terminal depends on the Service Centre in the public network. In most
cases after sending one SM, the Service Centre registers the terminal as 'SMS terminal'.

The following commands are used to identify the SMS Service Centre.

To use this service the Calling Line Identity (CLI with FSK) must be supported. The CLI can not only be sent in
DTMF, but also in FSK.

PRECONDITIONS

- The extensions used are analogue phones, called Sirio, from Telecom Italia.
- PMC-G package version 04.01 (or higher) is required.
- System option LOSYSOP 154 (SMS service allowed) must have value '1' (yes).
- FCM 76 (CLIP on analogue terminal with FSK) must be assigned to the appropriate extensions.
- FCM 77 (SMS allowed) must be assigned to the terminal(s) that are allowed to send/receive SM's.
- The destination characteristic "delayed seizure" (CHDSTC) must be set to one, since en-block sending is
required for this service. Another possibility is to project the "SMS Service Centre" number as external
number and to assign a route table to it.
- The local domain of the extension that wants to use the SMS service must be adapted such that the
correct CLI (e.g. full national number) is sent to the public net. Addressing command CHLDOM must be
used for this.

Assign SMS Service Centre Identity 409 # !

ASSCID:<SERVICE-CENTRE-TYPE>,<SERVICE-CENTRE-IDENTITY>;
This command is used to assign the SMS Service Centre Identity to a unit.

Erase SMS Service Centre Identity 414 # !

ERSCID:<SERVICE-CENTRE-TYPE>[,<SERVICE-CENTRE-IDENTITY>];
This command is used to erase the SMS Service Centre Identity
When parameter <SERVICE-CENTRE-IDENTITY> is omitted, all relations are removed.

Display SMS Service Centre Identity 444

DISCID:[<SERVICE-CENTRE-TYPE>];
This command is used to display the SMS Service Centre Identity.
When parameter <SERVICE-CENTRE-IDENTITY> is omitted, all relations are displayed.

- 167 -
57. SysManager
Use the following sequence of commands if a SysManager (a Telephone Management System=TMS) must
be connected:

- Use ASINTN to assign the TMS prefix (see chapter Numbering Scheme);
- Use CHTFCR if traffic classes must be changed from the TMS (see chapter System Security);
- Use ASTMSD to assign the digit position;
- Use ASTMSW to assign the relation between window and window size;
- Use CHTMST to assign the relation between the tone type and tone source;
- Use CHTMSL to assign the relation between a service (window) and the TMS handling that service.

Assign TMS Digit Position 275 # !

ASTMSD:<DIGIT-POSITION>;
Specifies which digit contains the TMS service code. If, for example the code for TMS is *12, the 4th
position contains the service code.

Assign TMS Window Size 277 # !

ASTMSW:<WINDOW>,<WINDOW-SIZE>[,<UNIT>];
Specifies the service code and the related number of possible simultaneous services.
BAR/UNBAR (service number 5) uses the command CHTRFC and the window size must therefore be set to 1.
Service number 5 is renamed to 'Change PBX Data' : this window size must be set to 1.

Change TMS Logical Name Relation 281 # !

CHTMSL:<WINDOW>[,[<LDN>][,[<CLUSTER-ID>][,<UNIT>]]];
This command links a logical device name of a TMS to a service number (WINDOW).

Normally, parameter <CLUSTER-ID> must be omitted.

For window 83, the following applies : in case of Do Not Disturb over DPNSS with centralized SysManager,
either parameter <LDN> or <CLUSTER-ID> has to be specified as follows :

- in the PBX where the SysManager is located :

- assign the LDN related to the SysManager and omit CLUSTER-ID.
- in the PBXs where the SysManager is not located :
- omit LDN but assign the CLUSTER-ID of the PBX where the SysManager is located.

When both <LDN> and <CLUSTER-ID> are filled in, the command is rejected.

Change TMS Announcement Code Relation 279 # !

CHTMST:<ANNOUNCEMENT-CODE>[,[<ANNOUNCEMENT-SOURCE>][,<UNIT>]];
The relation between the ANNOUNCEMENT-CODE and the ANNOUNCEMENT-SOURCE is assigned per UNIT.
The relation to an announcement code is erased by omitting the ANNOUNCEMENT-SOURCE.

- 168 -
The command will ask for additional parameters:

- ANNOUNCEMENT-SOURCE is 1:
Synchronous announcer specified by a DNR
Enter<DNR>of synchronous announcer:
- ANNOUNCEMENT-SOURCE is 2:
Tone announcer specified by tone-function number
Enter <TONE_FUNCTION>number of tone announcer:
- ANNOUNCEMENT-SOURCE is 3:
Continuous announcer specified by an EHWA
Enter<SHELF>,<BRD>,<CRT>of continuous announcer:

Display TMS Digit Position 274

DITMSD:;
Response:
DIGIT POSITION
4

Display TMS Logical Device Name Relations 280

DITMSL:[<WINDOW>][,<UNIT>];
Response:
UNIT WINDOW LDN CLUSTER-ID
1 81 TMS03 -
1 83 - 45
2 83 - 45

Display TMS Announcement Code Relations 278

DITMST:[<ANNOUNCEMENT-CODE>][,<UNIT>];
Response:
ANNOUNCEMENT-CODE relations:
ANNOUNCEMENT-CODE relations
UNIT CODE SOURCE DNR TONE SHELF BRD CRT
xx xx x xxxxxx xx xxxx xx xx

Display TMS Window Size and Status 276

DITMSW:[<WINDOW>][,<UNIT>];
Response:
UNIT WINDOW MAX SIZE ACTUAL SIZE STATUS
xx xx xx xx xxx

- 169 -
58. SYSTEM DUMP
System dumps are used when serious problems occur in a system and the cause of these problems is
unknown.
This system dump contains diagnostic system data gathered by the Local Operating System (LOS) of a unit.
The system dump can be sent together with the Problem Report to determine the cause of these problems.
Also do a RTRIEV and enclose the generated files: OR and PR.

A system dump is made in the central memory of a unit:

- After a freeze
- After an operational start (warm or hot), due to a software exception
- After an operational start (warm or hot), due to a manual request (OM command)
- After executing of OM command TRSYSD or (since SIP@Net 5.1.3) via a trigger dump command over
CSTA (BusinessConneCT).

The next step for the user is to decide what to do with the system dump information:

- In case the system dump data is not needed use ERSYSD to delete the system dump information in the
central memory or;
- Use DUSYSD to save to a logical device (LBU or PC). As soon as the dump is saved completely, it will be
erased automatically from the memory. This action can also be performed automatically, in this case the
save will be done to the local backup.

Change Diagnostic System Data Parameters 133 # !

CHSYSD:<SHELF>,,<CRT>,<DUMP>,<AUTO>;
This command determines which data is stored in a system dump and whether the dump information is
automatically saved to the local backup.
The default setting is:

DUMP AUTO
0 = Freeze ON
1 = Exception ON
2 = Manual start OFF
3 = Trigger ON

Display Diagnostic System Data Information 134

DISYSD:<SHELF>,,<CRT>;
Response:
FEMT Presence Writing Sequence nr. Appended nr. Frozen nr.
xxxx xxxxxxx xxxxxx xx xx xx

In this response FEMT stands for Frozen process, software Exception,Manual start and Triggered system
dump. Auto FEMT displays the automatic writing (0= no, 1= yes). Presence indicates the presence of system
dump information (absent/present/writing/blocked). Writing indicates the current segment name,
sequence number indicates the sequence number of the dump currently present.
The appended number gives the number of dumps currently appended to the file DSuuss.DMP
(ss=sequence nr).
The frozen number indicates the number of frozen processes since the last operational start.

- 170 -
Dump Diagnostic System Data 230
DUSYSD:<SHELF>,,<CRT>[,<LDN>];
This command will start the dumping of Diagnostic System Data present in the central memory to a Logical
Device. The EHWA (SHELF and CRT) must indicate a CM module.
If <LDN> is omitted, the local backup (LBU) will be used.
The following files are dumped to the specified device:

DAuu01.DMP, the current environment dump, containing:

- Process Instance Value (PIV)
- Stack pointer
- PACBs of the current process
- Control blocks of the current process
- Stack
- Priority/identity and destination address of the signals of the signal queues, etc.
DBuu01.DMP, segment dump part 1.
DCuu01.DMP, segment dump part 2.
DDuu01.DMP, segment dump part 3.
DEuu01.DMP, segment dump part 4.
DSuu01.DMP, appended current environments.

If <LDN> is omitted, the local backup (LBU) will be used.

Erase Diagnostic System Data 231

ERSYSD:<SHELF>,,<CRT>;
As long as a system dump is present in the central memory, no new dump can be made.
With this command the dump information is erased from the central memory.

Trigger System Dump 232

TRSYSD:<SHELF>,[<BRD>],<CRT>,<DUMP-ACTION>;
The EHWA can only identify a PCT or the CM. If BRD is omitted the CM is indicated.
No new system dump can be made as long as an old one is still present. This command is only used on
indication of the “Helpdesk - NEC Hilversum” in case of system errors.
This system dump can be copied to a PC and sent back to determine the cause.
Note that when a dump is reset (DUMP-ACTION = 0), the EHWA of the CPU has to be given for example as
follows :

- iS3010 / 3030 : TRSYSD:12,,2,0;

- iS3050 : TRSYSD:11,,0,0;
- iS3070 / 3090 : TRSYSD:1014,,0,0;

Example of an Off-hook trigger dump

1. First check with DISYSD for any outstanding dump action and "Auto" yes/no.
2. Suppose a telephone set is connected on EHWA 11,3,8. Then specify in TRSYSD:11,3,8,2;
in which "11,3,8" is the EHWA of the telephone set and "2" is the dump-action "Set off-hook trigger".
3. By going off-hook from the telephone set, a system dump will be made.
4. After the dump is made execute DUSYSD.
5. Do not forget to reset the off-hook trigger, as follows :
TRSYSD:11,,0,0; (example for an iS3050 system)
Otherwise every time a dump is created, when going off-hook from that telephone set.

- 171 -
Trigger dump command over CSTA
In some situations it is helpful to be able to created a SIP@Net trigger dump from a BusinessConneCT (BCT)
client. Since SIP@Net 5.1.3 the CSTA interface is expanded so that a SIP@Net trigger dump can be created
from a BCT client, running release 6.1.0 (or higher).

System dump by setting a trap

A system dump is also made by setting a so-called “trap”.
For example in case Alarm Code 35, QLF 4 is raised, a system dump has to be made.

See the "Second Line Maintenance Manual" for more details.

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.
So, for the example given it is as follows :

<CHTRAP:9,1;
Enter parameter [<ALARM-HANDLER-CODE>] (0..249) :35;
Enter parameter [<ALARM-HANDLER-QUALIFIER>] (0..99) :4;
Enter parameter [[<SHELF>][,[<BRD>][,<CRT>]]] :;
Unit 1 : alarm occurrence trap switched ON with parameters 35,4

WARNING : AFTER THE DUMP IS MADE, DO NOT FORGET TO SWITCH OFF THE TRAP.

<CHTRAP:9,0;
Unit 1 : alarm occurrence trap switched OFF

Display System Trap 217 !

DITRAP:[<TRAP>][,<UNIT>];
This command shows the status of the various system traps.
Refer to OM command CHTRAP for detailed information on the parameter <TRAP> and 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.

- 172 -
59. SYSTEM SECURITY
System security consists of the following:

• Authority classes
Each OM command has an authority index. This index is linked to an authority class. This authority class
is compared with the authority class of the OM terminal. If the OM terminal does not have the authority
class of the command, the command cannot be executed.
A distinction is made between session and default authority class. The default authority classes are
given to a terminal when a new session begins. The session authority can be changed but it disappears
after the session is terminated.

• Protection levels
Each file has protection levels for specific actions on the file.
The actions are:

New : to determine if a user is allowed to make a new version of an existing file.

Append : to determine if a user is allowed to append to a file.
Read : to determine if a user is allowed to read a file.
Delete : to determine if a user is allowed to delete an existing file.

These are compared with the protection levels of the OM terminal. If the OM terminal does not have
the same (or higher) protection level as the file for a specific action, the command will not be executed.
A distinction is made between session and default protection levels. The default protection levels are
given to a terminal when a new session begins. The session protection levels can be changed but they
disappear after the session is terminated.

• Passwords.
Some commands are potentially dangerous. The user must type in a password, before the command can
be executed.

• Restriction levels.
Each OM terminal, operators desk and SSM/SysManager system has restriction levels assigned to it. This
means that some traffic classes and FCMs cannot be assigned on that specific terminal or operators desk.

59.1. AUTHORITY AND PROTECTION

With these commands it is possible to define the authority classes, to set the default and session authority
class and protection levels of an OM terminal. The authority class consists of 16 levels. The authority classes
have the following default meanings:

- 173 -
 AUTHORITY CLASS PERMITTED ACTIONS
0 Display functions for the customer
1 Change telephony functions by customer
2 Change complex and data functions by customer
3 File management
4 Batch jobs
5 Change of service conditions
6 Maintenance level 1
7 Maintenance level 2
8 Maintenance level 3
9 Second line maintenance tools
10 Spare (user definable)
11 Spare (user definable)
12 Spare (user definable)
13 Spare (user definable)
14 Change session authority class and protection (always allowed)
15 Subcommands (never allowed)

Protection levels are used to protect files against unauthorized use of an OM terminal.
There are four kinds of protection: New (N), Append (A), Read (R) and Delete (D), each having a protection
level between 0 (lowest level) and 7 (highest level). Each file has a specific protection level; only a terminal
that has an equal or higher protection level can manipulate that file, e.g. a terminal with NARD 7443 can
not delete a file with NARD 4444. New, append and read would be allowed for this example.

Display the current authority classes and protection levels by :DIAUPR: ;

59.1.1. Authority Class Indexes

Change Authority Class Index and Value Relationship 14 # !

CHACIV:<AUTHORITY-INDEX>[,<AUTHORITY>];
With this command it is possible to change the authority class connected to an OM command.
Each OM command has an AUTHORITY-INDEX to which an AUTHORITY class can be linked. This command
asks for a password.

Display Authority Class Index and Value Relationship 117

DIACIV:<AUTHORITY-INDEX>;
Response:
Authority-index Authority
xxx xx

- 174 -
59.1.2. Authority Classes and Protection Levels

Change Default Authority Class 114 # !

CHDEAU:<TERMINAL>,<AUTHORITY>[,<ALLOWED>];
This command may ask for a password.
The effect of this change will not be noticed until a new session is started.

Change Default Protection Level 115 # !

CHDEPR:<TERMINAL>,<PROT-TYPE>,<PROTECTION>;
This command may ask for a password.
The effect of this change will not be noticed until a new session is started.

Change Session Protection Level 14

CHSEPR:<PROT-TYPE>,<PROTECTION>;
This command may ask for a password.
The new protection level is only valid for the current session.

Change Session Authority Class 14

CHSEAU:<AUTHORITY>[,<ALLOWED>];
This command may ask for a password.
The new authority class is only valid for the current session.

Display Authority Class and Protection Level 116

DIAUPR:[<TERMINAL>];
If the terminal name is omitted the current terminal name is used. In that case both the default and the
session protection level are displayed.
Response :
Default protection level (N/A/R/D): ... ...
(Session protection level (N/A/R/D): ... ...)
Default authority class : ... ... ... ... ...
(Session authority class : ... ... ... ... ...)

- 175 -
59.2. PASSWORDS

Passwords are used by several commands. Each password is identified by a password group and a password
key.
The following table indicates the default passwords:

PASSWORD GROUP
PASSWORD
0 1 2 3 4 5 6
KEY
AUTH. PROT. N PROT. A PROT. R PROT. D SERVICE MISC.
0 --- --- --- --- --- ---
1 --- --- --- --- --- SYSTEM RISKY
2 --- --- --- --- --- RISKY
3 --- --- --- --- ---
4 --- --- --- --- ---
5 --- CONFID CONFID CONFID CONFID
6 RISKY RISKY RISKY RISKY RISKY
7 RISKY RISKY RISKY RISKY RISKY
8 RISKY
9 RISKY
10 RISKY
11 RISKY
12 RISKY
13 RISKY --- = No password present

These default passwords can be changed by OM command CHPASS.

Change Password 235 # !

CHPASS:<PW-GROUP>,<PW-KEY>;
Response:
Old Password :
New Password :
Verification :

Fill in the old password and the new password (and again the new password for verification). A password
can be deleted by just entering a semi-colon when asked for the new password and verification. A
password consists of maximum 6 characters.

- 176 -
The following table gives the password groups and the password keys present in the groups:

PASSWORD RELATED
DESCRIPTION PASSWORD KEY
GROUP COMMAND
0 CHDEAU Changing default authority class 0 ... 13 (Authority class No.)
0 CHSEAU Changing session authority class 0 ... 13 (Authority class No.)
1 ... 4 (NARD) CHDEPR Changing default protection level 0 ... 7 (Protection level)
1 ... 4 (NARD) CHSEPR Changing session protection level 0 ... 7 (Protection level)
5 SETOUT Set service condition to out of service 0 ... 2 (Degradation level)
5 SETNIN Set service condition to not installed 0 ... 2 (Degradation level)
5 FRCOUT Forcing service condition to out of service 0 ... 2 (Degradation level)
5 UNIINS Set service condition of unit to installed 2 (Degradation level)
5 UNININ Set service condition of unit to not installed 2 (Degradation level)
6 CHVLRE Change Voice Logging Relation 2
6 INIDSK Initialise disk 1
6 CHACIV Change ACI and value relation 1

The following degradation levels are used in password group 5:

- 0 = Not serious : for degradation of PCT boards.

- 1 = Serious : for degradation of PMs.
- 2 = Very serious : for degradation of CM, SM, CM boards, SM boards, devices, SNL, ULL, DTU and PCH.

Force to New Password 314 !

FRCPSW:<PW-GROUP>,<PW-KEY>;
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.

See the "Second Line Maintenance Manual" for more details.

- 177 -
59.3. RESTRICTION LEVELS

This group of OM commands is used to determine which FCMs and traffic classes may be assigned and
deleted from a certain terminal type.

59.3.1. Facility Class Mark Restriction Levels

Change Facility Class Mark Restriction Level 228 # !

CHFCMR:<TERMINAL-TYPE>s/r[,[<FCM>s/r][,<RESTRICTION>]];
If the FCM level is omitted all FCM levels will be changed depending on the restriction. If parameter
RESTRICTION is omitted the action is restricted as a default.

Display Facility Class Mark Restriction Level 229

DIFCMR:<TERMINAL-TYPE>s/r;
Response:
Unrestricted facility class marks for "TERMINAL TYPE"
xx xx xx xx xx xx

59.3.2. Traffic Class Restriction Levels

Change Traffic Class Restriction Level 226 # !

CHTFCR:<TERMINAL-TYPE>s/r[,[<TRFC>s/r] [,<RESTRICTION>]];
If the traffic class level is omitted all traffic class restriction levels will be changed depending on the
restriction. If parameter RESTRICTION is omitted the action is restricted as a default.

Display Traffic Class Restriction Level 227

DITFCR:<TERMINAL-TYPE>s/r;
Response:
Unrestricted traffic classes for "TERMINAL TYPE"
xx xx xx xx xx xx

- 178 -
60. TESTING
60.1. PERIODIC AUTONOMOUS TESTING

Periodic Autonomous Testing (PAT) ensures that most system parts are tested from time to time. If a PAT
fails the result appears in an alarm buffer. A successful test result is not displayed.

Change Periodic Autonomous Testing Mode 83

CHPATM:<PAT-MODE>[,<UNIT>s/r];

This command is used to switch the unit between the Normal and Installation/Factory test mode. In the
Installation/Factory test mode the periodic autonomous test has a higher priority than the handling of
telephone traffic. Periodic autonomous testing is an idle time job in the normal mode, i.e. telephone traffic
is more important than testing.

Remark: A fault report with alarm code 16 with qualifier 3 indicates that the Installation/Factory test
mode is set.

Clear Periodic Autonomous Testing Cycle Counter 84

CLPATC:[<UNIT>s/r];

Display Periodic Autonomous Testing Cycle Counter 82

DIPATC:<RESOURCE-TYPE>s/r[,<UNIT>s/r];
Response:
UNIT RESOURCE-TYPE CYCLE-COUNTER
xx xx xx

60.2. MANUALLY CONTROLLED TESTING

Manually Controlled Testing (MAT) gives the possibility to insert resources in a test request list. If this test
fails the result can be read out from history buffer 12. A successful test will not be displayed. The following
rules apply for the hardware addresses in these command:

- If CRT is omitted, the board is indicated.

- If BRD is omitted, the module is indicated.
- If BRD and CRT are omitted, the shelf is indicated.

Delete Resource from Test Request List 97

DETEST:[<SHELF>[,[<BRD>s/r][,<CRT>s/r]]];
If the shelf is not specified, ALL test requests in the system will be deleted.
Response:
Do you want to delete ALL manual test requests (YES/NO) : ?

Display Manual Test Requests 98

DITEST:[<SHELF>[,[<BRD>s/r][,<CRT>s/r]]];
If at least the shelf is specified the test requests STATUS and REP-FACTOR are shown, according to the
following rules:
- STATUS = request in progress or
- STATUS = request waiting

- 179 -
Repeat factor = 0 means continuous testing, while any other value represents the number of tests for that
EHWA that still has to be performed, plus the current test if the status is waiting. If an EHWA is specified,
the general status of manually controlled tests is displayed. Otherwise for each unit the total number of
waiting requests and requests in progress is given.

If at least SHELF has been input the response is:

SHELF BRD CRT STATUS REP-FACTOR
xxxxx xx xx xx xx

Otherwise:
UNIT # WAITING # IN PROGRESS
xx xx xx

Insert Resource into Test Request List 96

INTEST:<SHELF>[,[<BRD>s/r][,[<CRT>s/r][,<REP-FACTOR>]]];
If the repeat factor is omitted, value 1 is used.

60.3. TEST OF THE ALARM BOX

Test Alarm Box 233

TSALRM:[<UNIT>s/r];
In the case of a CPU3000, only the alarm output (upper socket) at the CPU3000 is tested.
Response:
Please enter the required test state ie "on", "off" or "end" ?

60.4. CONTROLLED CONNECTION

The commands for controlled connections are used to establish and release a one way or a both way
connection between two ports.

It is also possible to make a one way connection between a Sender/Receiver Tone and a port.

A connection is established by means of the commands: CRCCSP or CRCCPP. The controlled connection is
released by means of command ERCOCO. The actual status of the controlled connection is displayed by
means of command DICOCO.
The following statuses are possible:

- SETUP : Controlled connection has been set up.

- ACTIVE : Connection has been established and active.
- ERROR : An error has been detected and the related resources released.
Clear the controlled connection by means of the ERCOCO command.
Note that an action of SAS or the command FRCOUT can be the cause that a connection
goes to error.
- KILL : Connection has been erased.

The service condition of the circuits which are involved, must be OUT.
If a tone resource or a B-channel is involved, the circuit must be in service condition INS.
A controlled connection is limited to a unit. Per unit a maximum of 5 controlled connections may be set up.

- 180 -
Create Controlled Connection Single Path 322
CRCCSP:<SHELF-A>,<BRD-A>[,<CRT-A>[,<B-CHANNEL-A>,<EXCLUSIVE-A>]];
The EHWA entered is that of the source EHWA. If the board number is omitted it means that a module (e.g.
a PM) is addressed.
The parameters B-CHANNEL and EXCLUSIVE are mandatory for ISDN ports.

The system asks for the destination EHWA:

<SHELF-B>,<BRD-B>,<CRT-B>[,<B-CHANNEL-B>,<EXCLUSIVE-B>];

Create Controlled Connection Paired Path 323

CRCCPP:<SHELF-A>,<BRD-A>[,[<CRT-A>>][,<B-CHANNEL-A>,<EXCLUSIVE-A>]];
If the board number is omitted it means that a module (e.g. a PM) is addressed. The parameters B-
CHANNEL and EXCLUSIVE are mandatory for ISDN ports.

The system asks for the destination EHWA:

<SHELF-B>,<BRD-B>,<CRT-B>[,<B-CHANNEL-B>,<EXCLUSIVE-B>];

A controlled connection will be set up between A and B.

Display Controlled Connection 330

DICOCO:[<COCO-NUMBER>],[<UNIT>];
If the COCO-NUMBER is omitted the status of all controlled connections in the unit is given.
Response:
UN # STATE SHELF BRD CRT BB X SHELF BRD CRT BB X T
xx x xxx xxxxx x x xx x xxxx x x xx x x
SET UP TIME: [ROLL BACK TIME]

Erase Controlled Connection 329

ERCOCO:<COCO-NUMBER>[,<UNIT>];

Send Controlled Connection Tone 397

SECCTO:<COCO-NUMBER>[,[<TONE-FUNCTION>],[<UNIT>]];
Before using this command, be sure that the controlled connection is established and is in the ‘active' state.

Send Controlled Connection Digit 398

SECCDI:<COCO-NUMBER>,<DFP-INDICATOR>,<DIGIT/FREQ>[,<UNIT>];
Before using this command, be sure that the controlled connection is established and is in the ‘active' state.

Display Controlled Connection Digit 399

DICCDI:<COCO-NUMBER>[,<UNIT>];
Before using this command, be sure that the controlled connection is established and is in the ‘active' state.

- 181 -
60.5. DIRECTED CALL

The directed call facility is used to test the function of receiver/sender resources. A directed call is limited
to one unit.
The sequence to set up a directed call is as follows:

- Directed call definition.

- A directed call is defined by means of command ASDICA.
- Directed call activation.
- The directed call is activated by means of the extension of the user. The user goes off hook and dials the
directed call facility code. He receives the dial tone if the resources which are defined for the extension
are idle.

The directed call is removed from the registration list by means of command DEDICA.

Assign Resources to a Directed Call 393 # !

ASDICA:<SHELF>,<BRD>,<CRT>;
The EHWA indicates the originator.
The system asks for the resource EHWA(s):
<SHELF>,<BRD>,<CRT>;

The command is stopped by typing a single semi colon.

Delete Resources of a Directed Call 395 # !

DEDICA:<SHELF>,<BRD>s/r,<CRT>s/r[,<SHELF>,<BRD>,<CRT>];
The first EHWA indicates the originator, the second is the resource EHWA.

Display Direct Call Definition 394

DIDICA:[<SHELF>,<BRD>s/r,<CRT>s/r][,<UNIT>s/r];
Response:
ORIGINATOR RESOURCE
SHELF BRD CRT SHELF BRD CRT TYPE
xxxxx xx x xxxxx xx xx xxx
xxxxx xx xx xxx
xxxxx xx x xxxxx xx xx xxx
xxxxx xx xx xxx

- 182 -
61. TOLL TICKETING AND FULL DETAILED CALL RECORDING
The OM commands for toll-ticketing are only relevant when the system option "Full Detailed Call Recording
in stead of Toll Ticketing" (60) is set to "FALSE". Likewise the OM commands for Full Detailed Call Recording
(FDCR) are only relevant when system option 60 is set to "TRUE". Commands STOPTT and STOPFR are
independent of option 60.

61.1. TOLL TICKETING

Change Thresholds of Route Number 152 # !

CHTRLV:<ROUTE>s/r,[<TICS>][,<DURATION>];
A call is only included in a call recording report, if the number of ticks (metering pulses) or the duration of
the call exceeds a certain threshold. This command is used to assign these thresholds.

Display Thresholds of Route Number 153

DITRLV:[<ROUTE>s/r];
This command shows the threshold(s) of a route as set by CHTRLV.
Response:
ROUTE THRESHOLD THRESHOLD
METERING-TICS DURATION (seconds)

Change Toll Ticketing Characteristics 154 # !

CHTTCR:<LINES-PER-PAGE>;
Indicates the number of lines after which a page feed is generated in the call recording file.

Change Toll Ticketing Output Definitions 155 # !

CHTTOD:[[<LDN>][,[<OUTPUT-FORMAT-VERSION>][,<UNIT>s/r]]];
Indicates to which device the toll ticketing file should be sent and in which output format. If LDN (Local
Device Name) is omitted no output device is defined any more. If the output device is changed while toll
ticketing is active, the "old" device remains valid until toll ticketing is restarted.

Display Toll Ticketing Output Definitions 156

DITTOD:;
If the output device is changed while toll ticketing is active, the "old" device remains valid until toll ticketing
is restarted. In this case the displayed device is not the current output device. This command is always
executed system wide.
The response is:
UNIT OUTPUT-DEVICE OUTPUT-FORMAT-VERSION
xx xxxx x

Display Toll Ticketing Status and Characteristics 151

DISPTT:;
The response is:
TT-OUTPUT-FILE FILE- TT- IN ACCUMULATIONS:
STATUS STATUS PROGR CALLS PULSES DUR CALLS
filename xxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxx

- 183 -
Start Toll Ticketing 149 #
STRTTT:<FILE-NAME>;
Before toll ticketing can be started the output device must be specified.
This can be a LBUxx, a PC, a toll-ticketing device or a printer.
If necessary use DICHAR to obtain a list of valid devices.
When toll ticketing is active, another toll ticketing start with a different file name may be done.
This redirects the output to the other file and the old one is closed.
This to prevent gaps in the TT output.
The file contains the following items:

CC CCT DP P/B EXT IBSC P/N PSW NUMBER DIALLED DATE TIME DUR. UNITS TETN
xx xx xx x xxxx xx x xxxxxx xxxx xxxxx xxxx xx xxx xxxx

If the costcentre (CC) and costcentre type (CCT), department (DP), private/business indicator (P/B) and/or
password (PSW) are not used by the caller, a blank is displayed in the related area. TETN contains the route
and line number of the external line.

Stop Toll Ticketing 150 #

STOPTT:;
This command stops toll ticketing and closes the output file.

61.2. FULL DETAILED CALL RECORDING

Change FDCR Characteristics 445 # !

CHFRCR:<FDCR-CALL-TYPE>s/r,<OFF-ON>;
This command adds or removes a FDCR call type to or from the list of recorded items. It allows you to
perform call recording on a restricted set of call types.

Change FDCR Output Definitions 347 # !

CHFROD:[[<LDN>][,[<OUTPUT-FORMAT-VERSION>][,<UNIT>s/r]]];
Indicates to which device the Full Detailed Call Recording (FDCR) file should be sent and in which output
format. If LDN is omitted no output device is defined any more. If the output device is changed while FDCR
is active, the "old" device remains valid until FDCR is restarted.

Display FDCR Output Definitions 371

DIFROD:;
If the output device is changed while FDCR is active, the "old" device remains valid until FDCR is restarted.
In this case the displayed device is not the current output device. This command is always executed system
wide.

The response is:

UNIT OUTPUT-DEVICE OUTPUT-FORMAT-VERSION
xx xxxx x

- 184 -
Display Full Detailed Call Recording 345
DISPFR:;
This command is used to display the FDCR output file. Furthermore this command displays the accumulated
metering pulses and call duration time, which are lost as result of congestion on accounting records.

The (example) response is:

FDCR-OUTPUT-FILE FILE- TT- IN ACCUMULATIONS:
STATUS STATUS PROGR CALLS PULSES DUR CALLS
filename xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxx

Recording call types :

internal calls : 1
outgoing calls : 1
incoming calls : 1
tieline calls : 1
assistance calls : 0
paging calls : 0
toll-ticketing calls : 1
accounting iSNet (DPNSS) transit calls : 0
filter accounting CCIS/iSNet (DPNSS) internal calls : 0

Start Full Detailed Call Recording 340 # !

STRTFR:<FILE-NAME>;
Before FDCR can be started the output device must be specified with CHFROD. This can be a LBUxx, a PC or
a printer. If necessary use DICHAR to obtain a list of valid devices.
When FDCR is active, another FDCR start with a different file name may be done.
This redirects the output to the other file and the old one is closed. This to prevent gaps in the output.
For more information about this file, refer to the Facility Implementation Manual (Management Facilities).

Stop Full Detailed Call Recording 342 # !

STOPFR:;
This command is used to close the FDCR output file.

- 185 -
62. TOOLS
The OM commands in this chapter are former Second Line Maintenance Commands.
See the "Second Line Maintenance Manual" for more details.

62.1. NUMBER OF FREE PACKETS / ROUTING COUNTERS

The commands for tools are used to display the results of the Local Operating System (LOS) functions which
monitor the routing counters, the use of software resources.

For detailed information of these OM commands, reference is made to the Second Line Maintenance
Manual.

Display Number of Free Packets 293

DIPOOL:[<UNIT>];
This command 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. The display will be continuously and can be aborted by means of ‘Ctrl X'.
Response:
PCB PACB CB SIG BUF SDB MDB LDB IOM STCK CDB OM
387 0380 0375 0400 0020 0016 0400 0190 000021 0097 1000 0185
387 0380 0375 0398 0020 0015 0400 0190 000022 0097 1000 0185
Command aborted

Display Number of Free Packets Once per Minute 310 !

DIPVAR: [<UNIT>];
This command (display number of free packets per minute) is a variant of OM command DIPOOL.
The command is used together with OM command STALDM (see section 38.1. MONITOR LOAD) 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

It is advised to execute this command in batch, as it takes about one minute to abort the display.

Display Routing Counters 292

DIROCO:<SHELF>,<BRD>[,<CRT>s/r];
This command 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).
It is also possible to display the routing counters of other units.
Response:
SHELF BRD CRT CHNL DESTINATION C1 C2 C3 C4 C5 C6 C7 C8
xxxx xx xx x xxxx xx xx xx xx xx xx xx xx xx

- 186 -
Display Physical Channel Destination 307 !
DIPCHD:<SHELF>,<BRD>[,<CRT>s/r];
This command (Display Physical Channel Destination) is a variant of 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.

62.2. (SECOND LINE) COMMANDS FOR PVE

Private Virtual Enhancements (PVE) is an entity within the PBX that provides iS3000 functionality as a
TCP/IP service to a management system like MA4000, Management@Net or MyOffice@Net.

For operational usage of the PVE functionality, LOSYSOP 121 must be set to "TRUE".
Furthermore allowance license 56 (Business ConneCT synchronization) is required.

The PVE supports the following functionality:

- monitoring;
- data retrieval;
- facility activation / deactivation.

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.

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).

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).

- 187 -
62.3. VARIOUS OTHER (SECOND LINE) COMMANDS

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 more than 10 seconds in the
signal queue of the unit where the OM terminal is situated.

Display Waiting Signals in Signal Queue 308 !

DISIGQ:;

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.

(Re-)Start unrestricted status monitoring 449 !

STMONI:<UNIT>;

DIMEUS
This command can be used to determine the physical memory size of a system.
Since SIP@Net 6.2 the command is extended with the option to show more detailed information about the
usage of the SIP service data.

Display Memory Usage 494 !

DIMEUS:[<AREA>][,[<USER>][,[<UNIT>]]];

CHPERD and DIPERD

This command changes data in the PPU or PPH.
It does not use a subcommand (no journalling) and can only be executed in the unit where the OM-terminal
is connected.

Change Peripheral Data 408 !

CHPERD:<DEBUG-TYPE>,<SHELF>,<BRD>[,<CRT>];

Display Peripheral Data 483 !

DIPERD:<DEBUG-TYPE>,<SHELF>,<BRD>[,<CRT>];

- 188 -
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.

Execute 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

- 189 -
63. TRAFFIC CLASSES
Change Traffic Class of DNR/BSP 16 # !
CHTRFC: [<DAY-TRFC>],[<NIGHT-TRFC>],[<UP-TRFC>],[<DOWN-TRFC>],
<BSP-ID>s/r;
If any of the parameters DAY-TRFC, NIGHT-TRFC, UP-TRFC or DOWN-TRFC is omitted the corresponding
traffic class is not changed.

Initially the UP-TRFC will be the same as the DAY-TRFC and the DOWN-TRFC will be the same as the NIGHT-
TRFC.

The DNR part of the BSP-ID is sufficient as long as the DNR is unique.

If the DNR is an operator DNR only the DAY-TRFC is relevant.

Display Traffic Class of DNR/BSP 17

DITRFC:<BSP-ID>s/r;
If the traffic class of an operator DNR is displayed only the DAY-TRFC is displayed.
Response:
DNR-BSPT DAY-TRF-Class NIGHT-TRF-Class UP-TRF-Class DOWN-TRF-Class
xxxxxx xx xx xx xx

- 190 -
64. TRAFFIC OBSERVATIONS AND MEASUREMENTS
64.1. TRAFFIC OBSERVATIONS

The command for traffic observation is used to scan and display the dynamic and static data of various
resources in the system.
The static data is read out when the command is executed. It consists of:

- Number of resources in OUT;

- Number of resources in ABL;
- Number of resources in NIN;
- Total number of resources in a pool;
- Total number of B-channels (ISDN only);
- Not usable B-channels (ISDN only).

The dynamic data is scanned with a higher frequency. If the dynamic data changes a new output line is
generated. Dynamic data comprises:

- Number of busy resources;

- Number of idle resources;
- Number of congested resources (never reset);
- Number of Camp On Busy situations on resources;
- Etc.

Data about the following resources can be observed with this command:

- Bundle and route data;

- Inter unit bundle and route data;
- Extension and group data;
- Paging route data;
- Add On Circuit (AOC) data;
- RKT-SDT and SKT-RDT data;
- Incoming and outgoing MFC data;
- Socotel data;
- Convertor data;
- Operator data and data about queues;
- Switching Network Channel (SNC) data;
- Call data;
- Inter Unit Traffic Dispersion;
- Dialled Facilities;
- Hatch data .

Display Result of Traffic Observations 209

DITRAF:<OBJECT>;
The command will ask for additional parameters, depending on the selected object. Note that only objects
without an asterisk (*) can be used for this command. See appendix B. PARAMETERS for parameter OBJECT.

The result of this command is some static and some dynamic data.

This command can be executed in the following ways:

- 191 -
• Display traffic observations of bundle (see also OM command DIISDN)
DITRAF:0;
Enter bundle number:30;
Enter unit number:1;

Response :
OBSERVED-ITEM STATIC-DATA
BUNDLE UNIT OUT ABL NIN TOTAL BCH BCH-NIN
xxx xx x x x x x x
OBSERVED-ITEM DYNAMIC-DATA
BUNDLE UNIT BUSY CONG
xxx xx xx xx

• Display traffic observations of route

DITRAF:1;
Enter route number:30;

Response :
OBSERVED-ITEM STATIC-DATA
ROUTE OUT ABL NIN TOTAL BCH BCH-NU
xxx x x x x x x
OBSERVED-ITEM DYNAMIC-DATA
ROUTE UNIT BUSY CONG COBS
xxx xx xx xx xx

• Display traffic observations of inter unit bundle

DITRAF:2;
Enter interunit bundle number:10;
Enter unit number:1;

Response :
OBSERVED-ITEM STATIC-DATA
IU-BUNDLE UNIT OUT ABL NIN TOTAL
xxx xx x x x x
OBSERVED-ITEM DYNAMIC-DATA
IU-BUNDLE UNIT BUSY CONG
xxx xx xx xx

• Display traffic observations of inter unit route

DITRAF:3;
Enter interunit route number: 10;
Enter unit number:1;

Response :
OBSERVED-ITEM STATIC-DATA
IU-ROUTE UNIT OUT ABL NIN TOTAL
xxx xx x x x x
OBSERVED-ITEM DYNAMIC-DATA
IU-ROUTE UNIT BUSY CONG
xxx xx xx xx

• Display traffic observations of extensions

DITRAF:4;
Enter unit number:1;

Response :
OBSERVED-ITEM DYNAMIC-DATA
EXTENSION-UNIT BUSY RING
xx xx xx

- 192 -
• Display traffic observations of extension or group
DITRAF:5;
Enter extension BSP-ID or group DNR : 1311;

Response:
OBSERVED-ITEM DYNAMIC-DATA
DNR-BSPT TYPE PRES ABS BUSY RING COB UNS-BIDS
xxx-xx xxx xx xx xx xx xx xx

• Display traffic observations of paging route

DITRAF:6;
Enter paging route number:40;

Response:
OBSERVED-ITEM STATIC-DATA
PAG-ROUTE UNIT OUT ABL NIN TOTAL
xxx xx x x x x
OBSERVED-ITEM DYNAMIC-DATA
PAG-ROUTE UNIT BUSY CONG COBS
xxx xx xx xx xx

• Display traffic observations of Add On Circuit (7), RKT-SDT (8), SKT-RDT (9), Incoming MFC (10),
Outgoing MFC (11), Socotel data (12) or Hatch (21)
DITRAF:7 ... 12 and 21;
Enter unit number:1;

Response :
OBSERVED-ITEM STATIC-DATA
RES-ID UNIT OUT ABL NIN TOTAL
xxx xx x x x x
OBSERVED-ITEM DYNAMIC-DATA
RES-ID UNIT BUSY CONG
xxx xx xx xx

• Display traffic observations of convertor

DITRAF:13;
Enter convertor type:0;
Enter unit number:1;

Response :
OBSERVED-ITEM STATIC-DATA
IU-ROUTE UNIT OUT ABL NIN TOTAL
xxx xx x x x x
OBSERVED-ITEM DYNAMIC-DATA
IU-ROUTE UNIT BUSY CONG
xxx xx xx xx

• Display traffic observations of specific operator

DITRAF:14;
Enter operator DNR : 8991;

Response for specific DNR :

OBSERVED-ITEM DYNAMIC-DATA
OP-DNR OP-STAT M-IND WA UA C-SER* C-TAX* C-BUSY* C-RING* C-PRE*
xxx xxx x x x x x x x x

- 193 -
 General response :
OBSERVED-ITEM STATIC-DATA
OPERATOR-UNIT OUT ABL NIN TOTAL
xx x x x x
OBSERVED-ITEM DYNAMIC-DATA
OPERATOR-UNIT PRES PRES-CH PRES-POM ABS-POM ABS
xx xx xx xx xx xx

- * C-SER : series call rerouted to the C queue

- * C -TAX : tax metering information
- * C -BUSY : call to a busy extension rerouted to the C queue
- * C -RING : call which encountered ringing time out rerouted to the C queue
- * C -PRE : preferred calls

• Display traffic observations of queues

DITRAF:15;
Enter queue type:0;
Enter assistance group:;
Enter unit number:1;

Response :
OBSERVED-ITEM DYNAMIC-DATA
ASSIST-GROUP UNIT M-QUEUE C-QUEUE A-QUEUE
xx xx xx xx xx

• Display traffic observations of Switching Network Channels

DITRAF:16;
Enter PMC/PSC address <SHELF>,<BRD> : 17;

Response :
OBSERVED-ITEM DYNAMIC-DATA
SHELF-BRD-CRT BUSY CONG
xxx - xx xx xx

• Display traffic observations of calls

DITRAF:17;
Enter single or multi unit calls:1; (0=single, 1=multi)
Enter unit number:1;

Response for a multi unit system :

OUTSTANDING MULTI UNIT CALLS IN REQUESTED UNIT
SOURCE: EXT OPE OPE OPE NE NE NE EXT TRK EXT TRK TRK
DESTIN UNIT: EXT EXT TRK OTH EXT TRK OTH TRK EXT PAG PAG TRK
xx xx xx xx xx xx xx xx xx xx xx xx xx

Response for a single unit system :

OUTSTANDING SINGLE UNIT CALLS IN REQUESTED UNIT
SOURCE: EXT OPE OPE OPE NE NE NE EXT TRK EXT TRK TRK
DESTIN UNIT: EXT EXT TRK OTH EXT TRK OTH TRK EXT PAG PAG TRK
xx xx xx xx xx xx xx xx xx xx xx xx xx

- 194 -
In case of an ISDN route, traffic can also be observed using the command DIISDN.
With this command (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 231 !

DIISDN:<SHELF>,<BRD>s/r,<CRT>s/r[,<B-CHANNEL>s/r];
Response example :
<DIISDN:12,9,0;
SHELF BRD CRT BUNDLE MAX-INC MAX-OUT TOTAL CUR-INC CUR-OUT CUR-TOT
12 9 0 0 30 30 30 1 1 2
12 9 0 0 30 30 30 1 2 3
12 9 0 0 30 30 30 2 2 4

Message 222: Command aborted

Display ISDN Dynamic Trunk Access Data 213 !

DIISDN:<UNIT+BUNDLE>,<IBSC>s/r;
Response example :
<DIISDN:0,14;
BUNDLE IBSC CUR-IBSC-CALLS BSPT MAX-AVAIL-LINES CURRENT-BSPT-CALLS
0 14 2 any - 4

Message 222: Command aborted

- 195 -
64.2. TRAFFIC MEASUREMENT

If Traffic Measurement must take place, do the following:

- Put the object to be observed in the Object List.

- Enter the time and length of the measurement.
As an alternative it is possible to start and stop the measurement manually.
- Traffic Measurement data is stored in a buffer.
This contents of this buffer can be displayed on the screen with DISPTO.
If an output device and file name have been assigned it will also be written to a file.

64.2.1. Start, Stop and Status

Start Traffic Measurement Observation 374

STRTTM:<PERIODS>;

Stop Traffic Measurement Observation 379

STOPTM:<OUTPUT-SWITCH>;

Display Traffic Measurement Status 387

DISPTM:;
Response:
UNIT START START TOTAL CURR NOT-OUT MEAS FILE
DATE TIME PERIODS PERIOD PERIODS STATUS STATUS
xx xxxxx xxxxx xx xx xx xx xx

64.2.2. Timing

Assign Traffic Measurement Timing 380

ASTMTI:<ON-TIME>,<PERIODS>,<CYCLIC>;
The previous measurement must end 15 minutes before the next one starts.
Cyclic means that the measurement is done weekly, depending on a system boundary.

Delete Traffic Measurement Timing 381

DETMTI:[<ON-TIME>];
ON-TIME indicates the start time of the measurement that has to be erased. If it is omitted, all
programmed measurements are deleted.

Display Traffic Measurement Timing 382

DITMTI:;
Response:
ON-TIME PERIODS CYCLIC
xxxx xxxx xxx

- 196 -
64.2.3. Output

Change Traffic Measurement Output Device 383 !

CHTMOD:[<LDN>][,<UNIT>s/r];
If the Logical Device Name (LDN) is omitted no output device is defined any more.

Change Traffic Measurement Output File Name 385 !

CHTMOF:[<FILE-NAME>];
If FILE-NAME is omitted no output file is defined any more.

Display Traffic Measurement Output Device 384

DITMOD:;
This command is always executed system wide.
Response:
UNIT CURR-DEVICE NEW-DEVICE
xx xxxxxx xxxxxx

Display Traffic Measurement Output File Names 386

DITMOF:;
Response:
CURR-FILENAME NEW-FILENAME
xxxxxx xxxxxx

Display Traffic Measurement Object Figures 388

DISPTO:<OBJECT>;
See parameter Object. This parameter must be present on the object list.
The command will ask for additional parameters. Which parameters, depend on the entered objects.
Response: Traffic measurement data.

64.2.4. Object List

Assign Traffic Measurement Object 378

ASTMOB:<OBJECT>;

Delete Traffic Measurement Object 375

DETMOB:<OBJECT>;

Display Traffic Measurement Object List 376

DITMOB:[<UNIT>s/r];
Response:
UNIT OBJECT-GROUP OBJECT-INDEX
xx xxxxxx xxxxxx

Erase Traffic Measurement Object List 377

ERTMLI:[<UNIT>s/r];
If UNIT is omitted all the lists in all the units are erased.

- 197 -
64.2.5. Output Formats

The result of the traffic measurement is a file or the display of data on the screen. The output varies with
the selected object for traffic measurement. The time (e.g. average holding time) in this output is given in
seconds, the carried load in Erlangs.

The following pages describe the format of the screen output (DISPTO).

When the output is written to a file, the file consists of lines, starting with the unit number, object number
and followed by numbers. An example of such a file is given for object 0:

1 STATIC FIGURES
1 0 5 24 0 0 0 0 0
1 END STATIC FIGURES
1 DYNAMIC FIGURES
1 0 5 20.4 0.30 12 23 34
1 END DYNAMIC FIGURES

The static data in the example above consists of:

1 = Unit number
0 = Object : Exchange and Tie Line Bundles
5 = Bundle number
24 = Total circuits
0 = Circuits in OUT
0 = Circuits in NIN
0 = Circuits in ABL
0 = Total B-channels
0 = Not usable B-channels

The dynamic data in the example above consists of:

1 = Unit number
0 = Object
5 = Bundle number
20.4 = Average holding time
0.30 = Carried load
12 = Incoming seizures
23 = Outgoing seizures
34 = Congestion

Compare this output with the screen output given on the next pages.

Note: The data below is the output on the screens (file output data is given in the Facility Management
manual). The figures in brackets, given in the outputs of the objects 14 and 15, are not part of the
screen layout but indicate the number in the traffic measurement output file.

The objects numbers have the following meanings :

- 198 -
• Object 0 : Exchange and Tie Line Bundles
Average holding time : xxx .xx
Carried load : xxx .xx
Incoming seizures : xxxxxxxxxxxx
Outgoing seizures : xxxxxxxxxxxx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx
Total B-channels : xxx
Not usable B-channels : xxx

• Object 1 : Exchange and Tie Line Routes

COB started : xxxxxxxxxxxx
COB to seizure : xxxxxxxxxxxx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx
Total B-channels : xxx
Not usable B-channels : xxx

• Object 2 : Inter Unit Bundles

Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 3 : Inter Unit Routes

Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 4 : All Extensions In a Unit

Average holding time : xxx .xx
Carried load : xxx .xx
COB started : xxxxxxxxxxxx
COB to ringing : xxxxxxxxxxxx
Average ringing time : xxx .xx
Ringing started : xxxxxxxxxxxx
Answered : xxxxxxxxxxxx

• Object 5 : Extension Groups

Average holding time : xxx .xx
Carried load : xxx .xx
COB started : xxxxxxxxxxxx
COB to ringing : xxxxxxxxxxxx
Average ringing time : xxx .xx
Ringing started : xxxxxxxxxxxx
Answered : xxxxxxxxxxxx
Average No of COBs : xxx .xx
Average COB time : xxx .xx
Unsuccessful bids : xxxxxxxxxxxx
Present groupmembers : xxx
Absent groupmembers : xxx

- 199 -
• Object 6 : Paging Routes (Real Paging)
Average holding time : xxx .xx
Carried load : xxx .xx
COB started : xxxxxxxxxxxx
COB to seizure : xxxxxxxxxxxx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 6 : Paging Routes (Virtual Paging)

Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx

• Object 7 : Add-on Circuits

Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 8 : RKT-SDTs
Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 9 : SKT-RDTs
Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 10 : Incoming MFC Circuits

Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 11 : Outgoing MFC Circuits

Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

- 200 -
• Object 12 : RS-Socotel Circuits
Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 13 : Convertors
Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

• Object 14 : Operators
Average holding time : xxx .xx
Carried load : xxx .xx

AVERAGE AVERAGE QUEUED HANDLED

QUEUE QUEUE LENTGTH QUEUE TIME CALLS CALLS
(0) M individual xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(28) WA xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(29) UA xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(10) C preferred xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(7) C series xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(8) C taxmetering xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(9) C through connect busy xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(11) C through connect ringing xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx

• Object 15 : Operator Queues

AVERAGE AVERAGE QUEUED HANDLED
QUEUE QUEUE LENTGTH QUEUE TIME CALLS CALLS
(1) M normal xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(2) M preferred xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(3) C ddi not answered xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(4) C ddi unsuccessful xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(5) C recall not on hook xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(6) C recall on hook xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(12) A1 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(13) A2 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(14) A3 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(15) A4 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(16) A5 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(17) A6 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(18) A7 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(19) A8 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(20) A9 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(21) A10 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(22) A11 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(23) A12 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(24) A13 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(25) A14 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(26) A15 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx
(27) A16 xxx.xx xxx.xx xxxxxxxxxxx xxxxxxxxxx

- 201 -
• Object 16 : Switching Network Channels

Congestion : xxxxxxxxxx

All PMs in a specific unit will be observed.

Therefore, only additional parameter for unit number is asked.
For each quarter of an hour, the data of the first PM is written to the output file of traffic measurement.
Data of other PMs is only written to the output file when the data is changed.
OM command DISPTO can be used to display the data of a specific PM.

• Object 17 : Calls
Single Unit:
SOURCE DEST INTRA UNIT INTRA UNIT
CALL TYPE AVERAGE DURATION ESTABLISHED CALLS
Ext Ext xxx.xx xxxxxxxxxx
Ope Ext xxx.xx xxxxxxxxxx
Ope Ope xxx.xx xxxxxxxxxx
Ope Oth xxx.xx xxxxxxxxxx
Spec-ext Ext xxx.xx xxxxxxxxxx
Spec-ext Trk xxx.xx xxxxxxxxxx
Spec-ext Oth xxx.xx xxxxxxxxxx
Ext Trk xxx.xx xxxxxxxxxx
Trk Ext xxx.xx xxxxxxxxxx
Ext Pag xxx.xx xxxxxxxxxx
Trk Pag xxx.xx xxxxxxxxxx
Trk Trk xxx.xx xxxxxxxxxx

Multi Unit:
SOURCE DEST INTRA UNIT INTRA UNIT INTER UNIT INTER UNIT
CALL TYPE AVERAGE DURATION ESTABLISHED CALLS AVERAGE DURATION ESTABLISHED CALLS
Ext Ext xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Ope Ext xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Ope Ope xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Ope Oth xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Spec-ext Ext xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Spec-ext Trk xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Spec-ext Oth xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Ext Trk xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Trk Ext xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Ext Pag xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Trk Pag xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx
Trk Trk xxx.xx xxxxxxxxx xxx.xx xxxxxxxxx

• Object 18 : Inter Unit Traffic Dispersion

Destination Unit 1 : xxxxxxxxxx
Destination Unit 2 : xxxxxxxxxx
Destination Unit 3 : xxxxxxxxxx
Destination Unit 4 : xxxxxxxxxx
Destination Unit 5 : xxxxxxxxxx
Destination Unit 6 : xxxxxxxxxx
Destination Unit 7 : xxxxxxxxxx
Destination Unit 8 : xxxxxxxxxx
Destination Unit 9 : xxxxxxxxxx
Destination Unit 10 : xxxxxxxxxx
Destination Unit 11 : xxxxxxxxxx
Destination Unit 12 : xxxxxxxxxx
Destination Unit 13 : xxxxxxxxxx
Destination Unit 14 : xxxxxxxxxx

• Object 19 : Dialled Facilities

Internal : xxxxxxxxxx
Assisted : xxxxxxxxxx
External : xxxxxxxxxx

- 202 -
• Object 21 : Hatch
Average holding time : xxx .xx
Carried load : xxx .xx
Congestion : xxxxxxxxxxxx
Total Circuits : xxx
Circuits in OUT : xxx
Circuits in NIN : xxx
Circuits in ABL : xxx

- 203 -
65. TRUNK TRAFFIC
The commands for trunk traffic are used to enter and display data needed for external traffic (both
incoming and outgoing). OM for trunk traffic is divided as follows:

- First the destinations are defined (for outgoing traffic).

- Destinations are related to a trunk access code or a network access code.
- One or more route tables are allocated to a destination to determine the different routing possibilities
to this destination (route numbers)
- More destinations can lead to the same rota.
- Each route has a unique number.
- A route consists of one or more bundles.
- Bundles are numbered per unit.
- A bundle consists of lines (trunk circuits).
- All lines in a bundle have the same characteristics and are linked to the EHWA of a trunk circuit.
- For ISDN bundles an extra level is present. Within the bundle ISDN trunk circuits are assigned. Within
these trunk circuits the B-channels (the actual trunk lines) are present. The B-channels of one circuit
should all be assigned to the same bundle.

65.1. DESTINATIONS

Destinations are only used for outgoing traffic and are related to an access code. Dialling the same access
code always results in the same destination, independent of the unit where the code was dialled.
Destination numbers are unique in the system.

Change Destination Characteristics 157 # !

CHDSTC: <DEST>,<TREE>,<DIALTONE-OPTIONS>,<ROUTE-TABLE>[,[<ACC-REP>]
[,<DELAYED-SEIZURE>[,<NUMBERING-PLAN>]]];
This command defines the network characteristics of a destination. If characteristics were already defined
for the destination the old ones will be overwritten by the new characteristics. This gives the possibility to
introduce changes in the external numbering scheme. In this case a new analysis tree must be defined,
after which the old tree is replaced by the new tree.

- if ACC-REP is omitted, the access code repetition counter is set to 0.

- if DELAYED-SEIZURE is omitted, no delayed seizure is performed.
- if NUMBERING-PLAN is omitted, the 'unkwown' number plan is selected.

Display Destination Data 171

DIDEST:<DEST>;
This command shows the characteristics (like route table, number plan) of a destination.
Response:
<DIDEST:0;

DEST TREE FST-DT SND-DT ACC-REP ROUTE-TABLE DELAY-SEIZURE NUMB-PLAN LOC-LOOKUP

0 60 1 0 0 0 D 0 0 0

- 204 -
65.2. ROUTE TABLES

Change Route Table 406 # !

CHROTA:<ROUTE-TABLE>[,[<USER-TYPE>][,<SEQUENCE-TABLE>][,<UNIT>]];
When USER-TYPE is omitted, all user types will be adapted.
When SEQUENCE-TABLE is omitted, 1 is assumed.

Additional parameters : <ROUTE>,<PREF-CODE>,<TRFC>[,<SMART-BOXEM>];

When all additional parameters are omitted, the contents of the route table will be erased.
The command will repeat this question up to 8 times, or until it is terminated with a single semi-colon.

Display Route Table 337

DIROTA:<ROUTE-TABLE>s/r[,[<SEQUENCE-TABLE>s/r] [,<UNIT>]];
When SEQUENCE-TABLE is omitted, 1 is assumed.
Response:
<DIROTA:0;

ROUTE-TABLE UNIT SEQUENCE-TABLE

0 1 1

NORMAL EXTENSION OPERATOR PRIORITY EXTENSION

ROUTE PREF TRFC SMART ROUTE PREF TRFC SMART ROUTE PREF TRFC SMART
0 p 3 No 0 p 3 No 0 p 3 No

65.3. ROUTES

A route table has one or more routes assigned to it. The route numbers are unique in a system.

65.3.1. Routes General

Create Route 159 # !

CRROUT:<ROUTE>[,<UNIT>];
If a route with the same route number already exists the command is rejected.

Display Route Data 172

DIROUT:<ROUTE>[,<BSPT>];
When the BSPT parameter is omitted default BSPT 98 is displayed.
Response:
<DIROUT:0;

ROUTE UNIT BSPT GEN-OPTS GEN-TONE CV CC-TABLE

0 1 - 0111110000100000 543444 0 -

INC-OPTS TONE-AND-DDI-OPTS TREE A-QUEUE OVE SCNE ACCESS-LIST

00100000000 000000000 - 16 - - 1

OUT-OPTS ATF
0011000 0

NO INCOMING DIGIT CONV. ON THIS ROUTE (USE DIDGCO FOR OUTGOING DIGIT CONV.)

SEQ BUNDLE
0 0

- 205 -
Erase Route 160 # !
ERROUT:<ROUTE>;
This command is only accepted when the route is known in the system and when there are no bundles and
no SCNEs and/or OVEs assigned to it any more.

65.3.2. Route Characteristics

Change Route Characteristics General 161 # !

CHRTCG: <ROUTE>,<GEN-OPTS>,<GEN-TONE>[,[<CV>][,<BSPT>]
[,<CC-TABLE-NR>]]];
If the compatibility value is omitted the default value will be valid. If the BSPT is omitted the default value
(98) is valid. The command will only be accepted if the route and the BSPT are already known in the system.
If general characteristics were already defined the old ones will be overwritten by the new ones.
CC-TABLE-NR represents the CLI or COL translation table.

Change Route Characteristics Incoming 162 # !

CHRTCI: <ROUTE>,<INC-OPTS>,<TONE-AND-DDI-OPTS>[,[<TREE>]
[,[<A-QUEUE>][,<BSPT>][,<ACCESS-LIST-ID]]];
If in INC-OPTS P=0 then:
- V, W, X and Y must be omitted;
- TREE must be omitted;
- In TONE-AND-DDI-OPTS only P and Q must be given.

If A-QUEUE is omitted calls are routed to the A16 general queue.

If the BSPT is omitted the default value (98) is valid.

Change Route Characteristics Outgoing 163 # !

CHRTCO:<ROUTE>,<OUT-OPTS>,<ATF>[,<BSPT>];
If the BSPT is omitted the default value (98) is valid.

65.3.3. Digit Conversion

See the DIROUT command to display the incoming digit conversions.

Assign Digit Conversion to an Incoming Route 164 # !

ASDGCV:<ROUTE>,[<ORIG-NUMBER>][,<CONV-NUMBER>];
Either ORIG-NUMBER or CONV-NUMBER may be omitted.

Erase Digit Conversion from an Incoming Route 165 # !

ERDGCV:<ROUTE>;
All digit conversions are erased from the route.

- 206 -
Assign Digit Conversion on Outgoing Route 390 # !
ASDGCO: <ROUTE>,<DEST>,[<ORIG-NUMBER>][,[<CONV-NUMBER>]
[,[<DIALTONE-PLACE>][,<PAUSE-PLACE>,<INTERVAL>]]];
Either parameter <ORIG-NUMBER> or <CONV-NUMBER> may be omitted.
Note that in case a ROUTE-TABLE is defined in the External Numbering Scheme the parameter
DELAYED SEIZURE in OM command CHDSTC must be set to “1”.

Erase Digit Conversion from an Outgoing Route 391 # !

ERDGCO:<ROUTE>[,<DEST>,<ORIG-NUMBER>];
The selected digit conversions are erased from the route.

Display Digit Conversion on Outgoing Route 400

DIDGCO:<ROUTE>s/r[,[<DEST>][,<ORIG-NUMBER>]];
Response:
ROUTE DESTINATION ORIGINAL NUMBER CONVERTED NUMBER DT-PLACE PAUSE INTERVAL
12 12 2 23025555 0 4 4

65.3.4. CLI or COL Translation

The 'CLI/COL translation' enables users to be presented by another CLI (Calling Line Identity) or COL
(Connected Line Identity). This is especially required for extensions which are not enabled to be reached
directly from the public ISDN network. When these extensions are engaged in a call via ISDN to the public
network, they send an invalid DNR, which may lead to confusion in the public network. This facility enables
users to express with which CLI or COL they wish to be presented to the ISDN. The following examples show
some of the possible combinations:

- non-DDI extensions;
- All or some extensions send the general access number as CLI or COL;
- Groupmembers send their group DNR.

Although 'CLI/COL translation' was initially developed for ISDN, it can also be used on QSIG, SIP and
analogue E&M trunk lines and also on CCIS using a TAC.

Change CLI and COL Translation 514 # !

CHCCTR: <CC-TABLE-NR>s/r[,<ORIG-CC-STRING>[,[<DEST-CC-STRING>]
[,[<LDI-SELECTOR>][,<LOCAL-DOMAIN-ID>]]]];
Add a new entry to the specified CC-table or redefine an existing translation in the specified CC-table.

It is possible to use wildcards in both the ORIG-CC-STRING and the DEST-CC-STRING. The wildcard character
which can be used is '%'. This character stands for only one digit. Wildcards can only be used to terminate
the strings. So 123%% is possible, while 12%4% is not.

- when wildcards are used in the ORIG-CC-STRING, for example 123%%, then all 5-digit CLI or COL strings
which start with 123 are translated according to the specified translation.
- when wildcards are used in the DEST-CC-STRING, for example 45%%, then the last two digits are copied
from the last two digits in the CLI or COL, which is to be translated.

Example:
CHCCTR: 1,123%%,45%%;

- 207 -
Now the CLI or COL of extension 12345 is translated to 4545.

- when DEST-CC-STRING is left empty (not omitted, do not forget the comma) the system sends an empty
CLI or no COL to the ISDN.
- when DEST-CC-STRING is omitted, the entry is deleted from the specified CC-table. It is possible to use
wildcards in the ORIG-CC-STRING, but only that exact entry will be deleted. The wildcard mechanism can
not be used to delete a number of entries which start with the same digits.
- when ORIG-CC-STRING and DEST-CC-STRING are omitted, the complete specified CC-table is deleted
(after confirmation).

Since SIP@Net 4.2 this command is expanded with parameters LDI-SELECTOR and LOCAL-DOMAIN-
ID. In previous releases, for the CLI/COL translation (executed on an incoming or outgoing call via an ISDN,
QSIG or SIP trunk) the explicit calling or connected party number is composed of data in the Local Domain
ID (LDI) of the trunk route (country code, area code, etc.) and the converted number. Since SIP@Net 4.2,
per CC translation it can be specified which LDI is used to compose the Calling/Connected Party.

This can be :

- LDI of the trunk route, via which the call is made, or

- LDI of the Calling / Connected Party (see note 1), or
- a specific LDI.

Note 1 : In case of a DPNSS call (see note 2) call to an ISDN/QSIG/SIP trunk (or vice versa) the LDI of the
DPNSS route (see note 2) route is used.

In case of a CCIS call to an ISDN/QSIG/SIP trunk (or vice versa) the LDI of the CCIS route is used.

In case of call that is diverted to external, and system option LOSYSOP126 (diverting user ID as CLI
when diverted to external) is TRUE, then the LDI of the diversion user is used.

Note 2 : Also valid for PVN, iPVN or iSNet-QSIG calls.

When a CC-translation is assigned, the table below indicates which LDI is used to compose the first part of
the CLI/COL (only in ISDN, SIP and QSIG trunk calls).

NUMBER OF LOCAL
LDI-SELECTOR USED LDI
PARAMETERS DOMAIN ID
3 LDI of route
4 0 LDI of route
4 1 LDI of calling or connected party
5 omitted entered entered LOCAL-DOMAIN-ID
5 omitted omitted default LOCAL DOMAIN (boundary 373)

CLI/COL Translation for internal calls

"CLI/COL translations for internal calls" offers the ability to display another number (to call back) than an
extension's or operator's DNR on the terminal of the opposite party in an internal call.
System boundary 441 defines the CC-table which contains the numbers for CLI/COL translation for internal
calls. It is advised to use this CC-table for internal calls only. The existing commands CHCCTR and DICCTR
can be used to assign or display CC-translation. The parameters LDI-SELECT and LOCAL-DOMAIN-ID of
command CHCCTR are obsolete, when the CC table is used for internal calls.

- 208 -
Display CLI and COL Translation 515 # !
DICCTR:<CC-TABLE-NR>s/r[,<ORIG-CC-STRING>];
- when ORIG-CC-STRING is omitted, all entries in the specified CC-table are displayed.
- when ORIG-CC-STRING is specified, but no exact match can be found in the CC-TABLE, then a wildcarded
entry is searched for and, when found, displayed.

The ORIG-CC-STRING itself may also contain wildcards, but it can not be used to display all translation
entries which start with the same digits. Only the best matched entry in the CC-TABLE is displayed.

Display CC-Table/Route Relation 512 # !

DICCTR:<CC-TABLE-NR>s/r[,<ORIG-CC-STRING>];
This command displays all routes which use the specified CC-table to translate CLI or COL strings.

65.3.5. QSIG Call Diversion Rerouting Table

The Call Diversion Rerouting Table contains per incoming route digit blocks that, after call diversion is
encountered, indicate which call diversion-to numbers must result in execution of call rerouting.

The Call Rerouting Table has also a 'general outlet', valid for all routes. If a given diversion-to number can
not be found for the given route, a check is done if the given diversion-to number can be found in the
category 'all routes'. The diversion-to number is found when one or more leading digits or all digits of the
given diversion-to number match a complete digit block, as defined in the Call Diversion Rerouting Table.

When the diversion-to number is not found, Forward Switching is performed.

Assign Rerouting Diversion Number to Route 480 # !

ASRTDN:[<ROUTE>],<REROUTING-DIVERSION-NUMBER>;
When no route is defined, the Rerouting Diversion Number is assigned for all routes.

Erase Rerouting Diversion Number from Route 481 # !

ERRTDN:[<ROUTE>],[<REROUTING-DIVERSION-NUMBER>];
- when no route is defined, the Rerouting Diversion Number is removed from all routes.
- when the Rerouting Diversion Number is empty, all Rerouting Diversion Numbers are removed from the
given route (or all routes).

Display Rerouting Diversion Number for Route 482

DIRTDN:[<ROUTE>][,[<REROUTING-DIVERSION-NUMBER>]];
- when no route is defined, the Rerouting Diversion Number is displayed for all routes.
- when the Rerouting Diversion Number is empty, all Rerouting Diversion Numbers are displayed for the
given route (or all routes).
- when the Rerouting Diversion Number is not empty, the relation(s) with a matching or near matching
Rerouting Diversion Number is (are) displayed.
- when both parameters are empty all relations in the Call Rerouting Diversion table are displayed.

65.3.6. Route-BSPT Relation

Assign BSPT to Route 54 # !

- 209 -
 ASBSPR:<ROUTE>,<BSPT>;
BSPT 98 and 99 may not be assigned. When a new BSPT is assigned to a route it will have the same set of
characteristics as the default BSPT (98).

Display BSPT of a Route 63

DIBSPR:<ROUTE>;
Response:
ROUTE BSPT
xx xx

Erase BSPT from Route 59 # !

ERBSPR:<ROUTE>,<BSPT>;
BSPT 98 cannot be removed from a route.

65.4. BUNDLES

Bundles are assigned to routes. They are numbered per unit, so the same number may occur more than
once in a multi-unit system.

65.4.1. Bundles General

Assign Bundle to Route 167 # !

ASBNDL:<ROUTE>,<BUNDLE>;
The signalling type of the first bundle assigned to a route determines if this route will be a DPNSS route or
not. It is not allowed to mix DPNSS bundles and non-DPNSS bundles in one route.

Note that for a DPNSS route the signalling type must be set with CHBNDC before assigning bundles to the
route, because the default signalling type is non-DPNSS.

Change Bundle Characteristics 166 # !

CHBNDC: <UNIT+BUNDLE>,<DIR-AND-NEG>,<OPTIONS>,<CON-AND-SIG-TYPE>
[,[<ALL-CALLS>][,<BSPT>]];
If ALL-CALLS is omitted, there is no restriction on the maximum number of allowed calls.
If BSPT is omitted BSPT 98 will be valid.

Delete Bundle from Route 168 # !

DEBNDL:<ROUTE>,<BUNDLE>;

Display Bundle Data 173

DIBNDL:<UNIT+BUNDLE>[,<BSPT>];

Response:
<DIBNDL:0;

- 210 -
BUNDLE BSPT ROUTE UNIT DIR-AND-NEG OPTIONS CON-AND-SIG-TYPE ALL-CALLS
0 - 0 1 2 2 1100100001000000 3 15 -

SEQ SHELF BRD CRT B-CH LINE

0 12 9 0 1 0000
1 12 9 0 2 0001
2 12 9 0 3 0002
3 12 9 0 4 0003
4 12 9 0 5 0004
5 12 9 0 6 0005
etc.

65.4.2. Bundle-BSPT Relation

Assign BSPT to Bundle 55 # !

ASBSPB:<UNIT+BUNDLE>,<BSPT>;
BSPT 98 and 99 may not be assigned. When a new BSPT is assigned it will have the same set of
characteristics as the default BSPT (98).

Display BSPT of a Bundle 77

DIBSPB:<UNIT+BUNDLE>;
Response:
BUNDLE BSPT
xx xx

Erase BSPT from Bundle 60 # !

ERBSPB:<UNIT+BUNDLE>,<BSPT>;

65.4.3. Digital Bundles

All DTUs can have Bundle - DTU relations except the DTU-CC and the ISDN DTUs (DTU-BA and DTU-PH). A
relation with bundles can be assigned to make outgoing calls impossible in case of a DTU alarm.

Change Bundle - DTU Relation 175 # !

CHBDTU:<UNIT+BUNDLE>[,<SHELF>,<BRD>];
If the shelf and board are omitted the bundle - DTU relation is erased.

Display Bundle - DTU Relation 176

DIBDTU:<UNIT+BUNDLE>s/r;
Response:
BUNDLE DTU POSITION
02022 2011 00 -5

- 211 -
65.5. LINES

Assign Line to Bundle 169 # !

ASLINE:<BUNDLE>,<LINE>,<SHELF>,[<BRD>],<CRT>[,<B-CHANNEL>];
When an ISDN circuit is assigned and the B-channel parameter is not entered, all B-channels are assigned to
the bundle. This means that all B-channels have the same line number.
For Multi-Line functionality it is mandatory to use 'unique line numbering' (LOSYSOP119 must be 'yes').

Virtual Lines
Virtual lines can be used in the Multi-Line functionality.
These lines are assigned by specifying the CM shelf as follows :

ASLINE:<BUNDLE>,<LINE>,14,,0; (for an iS3070/3090 system)

ASLINE:<BUNDLE>,<LINE>,11,,2; (for an iS3050 system)
ASLINE:<BUNDLE>,<LINE>,12,,2; (for an iS3010/3030 system)

The bundle specified in the first parameter must have connection type 5 'virtual connection' and signalling
type 19 'virtual lines' by OM-command CHBNDC 'Change bundle characteristics'. Only one such a bundle
can be assigned per unit and it can have no lines other than virtual lines assigned to it. Other bundle-
characteristics are irrelevant for the virtual lines bundle. This bundle can not be assigned to a route.

Note: To delete or display a virtual line, use the command DELINN or DILINN.

Delete Line from Bundle 170 # !

DELINE:<SHELF>,<BRD>s/r,<CRT>s/r[,<B-CHANNEL>s/r];
If in case of an ISDN circuit the B-channel parameter is not entered, all B-channels will be deleted from the
bundle.

Delete Line by its Line Number 551 # !

DELINN:<LINE>s/r[,<UNIT>];

Display Line by its Line Number 552

DILINN:<LINE>s/r[,<UNIT>];
Response : see OM command DILINE.

Display Line Data 174

DILINE:<SHELF>,<BRD>s/r,<CRT>s/r[,<B-CHANNEL>s/r];
Response:
SHELF BRD CRT B-CH LINE BUNDLE ROUTE UNIT INE/PLE/FTLD FTLI
xxxxx xx xx xx xxxx xxx xx xx xx xx xx xxx

Change B-Channel Dedication 212 # !

CHCDED:<DED-TYPE>,<SHELF>,<BRD>s/r,<CRT>s/r,<BCH-VALUE>;
Parameter BCH-VALUE is series/range when parameter DED-TYPE is 0 ... 2.

- 212 -
Display ISDN Trunk Circuit 211
DITCRT:<SHELF>,<BRD>s/r,<CRT>s/r;
The response is different for primary rate circuits and basic rate circuits (Ass indicates whether a B-channel
is assigned to a bundle):
Response primary rate:
SHELF BRD CRT BUNDLE INC-CALLS OUT-CALLS TOTAL-CALLS
xxxx xx xx xx xxx xxx xxx

B-CH DEDICATION Ass B-CH DEDICATION Ass B-CH DEDICATION Ass

1 outgoing Yes 2 outgoing Yes 3 outgoing Yes
4 outgoing Yes 5 outgoing Yes 6 outgoing Yes
7 outgoing Yes 8 outgoing Yes 9 outgoing Yes
10 outgoing Yes 11 incoming Yes 12 incoming Yes
13 incoming Yes 14 incoming Yes 15 incoming Yes
17 incoming Yes 18 incoming Yes 19 incoming Yes
20 incoming Yes 21 incoming Yes 22 bothway Yes
23 bothway Yes 24 bothway Yes 25 bothway Yes
26 bothway Yes 27 bothway Yes 28 bothway Yes
29 bothway Yes 30 bothway Yes 31 bothway Yes

Response basic rate:

SHELF BRD CRT B-CH LINE BUNDLE ROUTE UNIT INE PLE
xxxx xx xx xx xxx xxx xx xx xxxx xxxx

B-CH DIDICATION Ass

0 bothway Yes
1 bothway Yes

65.5.1. CLI/COL Identity of a Trunk Line

Change CLI/COL Identity of a Trunk Line or Virtual Line 554 # !

CHCCLI:<LINE>s/r[,[<CLI/COL-STRING>][,<UNIT>]];
Multi-line users can be presented to the public ISDN by a CLI/COL which has been assigned to the real or
virtual line which is being used, instead of being presented by the DNR of their terminal.

When parameter CLI/COL-STRING is omitted or empty, the original CLI/COL identity is deleted.

Display CLI/COL Identity of a Trunk Line or Virtual Line 555 #

DICCLI:<LINE>s/r[,<UNIT>]];
Response:
LINE CLI/COL
xxxx xxxx

65.6. FIXED TRUNK LINES

65.6.1. Destinations and Identities

In systems it is possible to have a fixed relation between terminals and analogue trunk lines. This facility is
used in DECT servers. When a certain terminal wants to initiate a call, it will always be connected to a
particular trunk line and when a call is coming in on that particular trunk line it will always be connected to
that terminal. The OM commands used to assign this situation are CHFTLD and CHFTLI. The IDENT-NUMBER
is the reference between the two commands.

- 213 -
In case the fixed trunk facility is used and a terminal is connected to the PBX that connects the trunk lines
to the PSTN, the 'entry point local exchange' has to be assigned (OM command CHEPLE).

Change Fixed Trunk Line Destination 523 #

CHFTLD:<SHELF>,<BRD>s/r,<CRT>s/r[,[<DEST-NUMBER>][,<IDENT-NUMBER>]];
BOARD and CIRCUIT can only be given as series or range when both DEST-NUMBER and IDENT-NUMBER are
omitted.

- when DEST-NUMBER is omitted, then the destination will be deleted.

- when IDENT-NUMBER is omitted, then depending on an already existing relation, the identity will be
deleted or a free identity will be chosen by the system.

Display Fixed Trunk Line Destination 517

DIFTLD:<IDENT-NUMBER>s/r[,<UNIT>];
When UNIT is omitted, then the command is only executed in the unit to which the OM terminal is
connected.
Response:
SHELF BRD CRT B-CH LINE BUNDLE ROUTE UNIT INE/PLE/FTLD FTLI
xxxxx xx xx xx xxxx xxx xx xx xx xx xx xxx

Change Fixed Trunk Line Identity 522 #

CHFTLI:<BSP-ID>[,<IDENT-NUMBER>];
When IDENT-NUMBER is omitted then the relation will be deleted.

Display Fixed Trunk Line Identity 518

DIFTLI:<BSP-ID>s/r;
Response:
DNR-BSPT FTLI
xxxxxx xx xxx

65.6.2. Entry Point Local Exchange

Change Entry Point Local Exchange 535 #

CHEPLE:[<DEST-NUMBER>];
The DEST-NUMBER is the cluster identity followed by the trunk access code. In case no DPNSS is used, the
DEST-NUMBER consists of the trunk access code only.

When the DEST-NUMBER is omitted then the relation will be deleted.

Display Entry Point Local Exchange 524

DIEPLE:;
Response:
ENTRY POINT LOCAL EXCHANGE
xxxxxxx

- 214 -
66. TWINNING
These OM commands are used to create, delete and display twinning relations.

Create Twinning Relation 103 # !

CRTWIN:<ORIG-BSP-ID>,<DEST-NUMBER>;
This command is used to create a twinning relationship between a dialled destination and its twinning
destination.

Erase Twinning Relation 118 # !

ERTWIN:<ORIG-BSP-ID>s;
This command is used to erase all information about a twinning relationship of the dialled destination.

Display Twinning Relations 119

DITWIN:<ORIG-BSP-ID>s/r;
This command is used to display information about a twinning relationship.
The ORIG-BSP-ID is the dialled destination.
Response:
DIALLED DESTINATION TWINNING DESTINATION
1000-95 1001

- 215 -
67. UNIT STARTS
The following unit start related OM commands are available:

STLOAD : Load a new software package.

STPROJ : Start projecting.
STCOLD : Cold start.
STWARM : Warm start.
STDUAL : Start Dual Mode (CCS systems only, not for single CCS systems).
SPDUAL : Stop Dual Mode (CCS systems only, not for single CCS systems).
SWDUAL : Switch Dual Mode (CCS systems only, not for single CCS systems).
STMAIN : Start Maintenance Mode (CPU3000 systems only).
SPMAIN : Stop Maintenance Mode (CPU3000 systems only).
STLOBP : Start Load Boot Program (CPU3000 systems only).
UPDUAL : Initiate a package reload (CCS systems only, not for single CCS systems).

The warm start is an operational start; it restarts the system using the project data stored in RAM.
A different type of an operational start is the hot start. The hot start takes less time than a warm start
because it does not download projecting data to the Peripheral Modules (PMs), it only tells the PMs to start
those resources which were operational before the start.

As a result of this, all PMs will start simultaneously and set all their resources into service without testing
them. The starts: STLOAD, STPROJ and STCOLD first load new data and then perform an operational start.
This operational start is by default a warm start but can be changed to a hot start, except for the STPROJ
which always uses a warm start. A hot start is only sensible if the PMs do not need to be downloaded. This
explains that the hot start is not available for the restart: STPROJ, because this explicitely reprojects the
complete unit, including the PMs.

The system accepts one hot start per 15 minutes. If it encounters a second hot start request within this
period of time, it assumes that the previous attempt was unsuccessful. It will therefore replace the second
hot start by a warm start.

If a restart in another unit occurs, that other unit will become unobtainable. This will not be reported,
because the command normally is successfully executed.

Each system start can be divided into two parts: first the CPU (hard- and software) is initialised and then all
peripherals (hard- and software) are initialised. Especially the latter is a time consuming task. To reduce
large restart times, the hot start mechanism exists. This mechanism is implemented as a sub-start type of a
warm start, cold start or reload. It only operates on resources that are already initialised and operational. If
no hotstart is executed, all projecting data for PMs, including board and circuit information, is downloaded
to all PMs during the system start. Especially for larger systems, this takes a considerable amount of time. If
a hotstart is executed, the CPU assumes that the data for the PMs has not changed, and the PMs are
instructed to start themselves without re-projecting all items.

Load a new Software Package 435

STLOAD:[<UNIT>][,<HOTSTART>];
The OM-command STLOAD is used to load a new CPU package in the system. It does so by requesting the
program in the boot-PROM to load a new software-package. Upon completion of the load, the new
software-package is automatically started, either using:

- the MIS-file (if present);

- projecting-files (if present);
- executing the internal projecting.

- 216 -
In case a hotstart is requested, a MIS-file must be present on the backup device. If this is not the case or
when the MIS-file is package-incompatible, the command is rejected.

Initiate a package reload in an iSMAN of CCS-based platforms 493 !

UPDUAL:[[<UNIT>][,[<UPDATE-START>][,<HOTSTART>]]];
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.

See the "Second Line Maintenance Manual" for more details.

Execute Projecting 434

STPROJ:[<UNIT>];
This command executes the projecting files: PExx.POM and LLxx.POM.

Coldstart a Unit 433

STCOLD:[<UNIT>][,<HOTSTART>];
This command is used to coldstart a unit. This restarts the system using a MIS-file.
Execution of this command can be necessary for two reasons:

- The data in the data-base of the ISPBX is inconsistent, but a MIS-file is present. A coldstart uses this MIS-
file for restoring the data in the data-base before a system start is executed.
- Major maintenance-actions are executed, but the system does not function as expected. In that case a
previously generated MIS-file can be used for restoring the data in the data-base as it was before the
maintenance was executed.

The command is rejected when no MIS-file is found or when the MIS-file is package-incompatible.

Note: After a cold start of a unit (CCS only) the date and time in a single unit system must be set by means
of OM command SEDATI. In case of a cold start in a unit which is part of a network of operational
ISPBX units, the date and time are retrieved by means of inter-unit links.
The CPU3000 system has a real time clock. When this system becomes operational, the correct date
and time are already set.

Warmstart a Unit 432

STWARM:[<UNIT>][,<HOTSTART>];
This command is used to warmstart a unit. The unit is still working but the behaviour is not predictable. In
some cases system assurance does not provide a proper solution or does not detect the improper
behaviour at all. In these cases the command STWARM can be used to force a warmstart.

During a warmstart the data in the data-base of the ISPBX is used to become operational again.

- 217 -
Start Load Boot Program (CPU3000 only) 538
STLOBP:<NEW-PACK>[,<UNIT>];
With this command you can replace an existing boot package. The upgrade is performed while the system
is operational running the CPU package in DRAM. The CPU3000 has the capability to store two boot
programs. If during boot program upgrade, the system goes down for whatever reason, there is still a boot
program available that allows the system to become operational again.

Once the STLOBP command has been executed, the new boot program is available and will be selected by
the pre-boot program. The new boot program becomes operational when a CPU package has been loaded
with the OM command STLOAD.

If the package load is done in maintenance mode, the new boot program will only be validated when
maintenance mode is stopped (SPMAIN). If it is done without using maintenance mode, the new boot
program is validated when it successfully completed the load of the new CPU package.
UNIT may only be omitted in a single unit system.

Display Loaded Boot Programs (CPU3000 only) 546

DILOBP:[<UNIT>];
The OPERATIONAL boot program is the one that loaded the current CPU package.
The STAND-BY boot program is:

- for another type of processor, or

- the program to be used for the next STLOAD of a CPU package, or
- the program that will be re-installed on fall-back from maintenance mode.

UNIT may only be omitted in a single unit system.

67.1. DUAL MODE (CCS only)

A CCS system can be switched into dual mode by STDUAL (not valid for single CCS systems). This allows for
loading (new) software (CPU, project data) into an operational system. The CPU, which consists of four CCS
boards is split into two clusters of two CCS boards each. One of the clusters keeps the control of the
complete system, while the other is set stand-by. This standby cluster can be provided with new software,
while the other cluster keeps the system operational.

Subsequently, tasks can be swapped by SWDUAL: the operational cluster is switched to standby mode and
the standby cluster to operational. This is a try out for the new software; If the new software causes
problems, one can always fall back to the existing software.

Start Dual Mode 473

STDUAL:[<UNIT>][,<RESTART>];
This command splits the CPU into two clusters; an operational cluster and a cluster which is stand-by.
This command is accepted if:

- All slices are synchronised and the Dual mode Backup Unit (DBU) is available:
- Both the CBU and DBU contain an empty journal file;
- Backup Maintenance Lock (BMLOCK) is set.

- 218 -
Stop Dual Mode 474
SPDUAL:[<UNIT>];
This command stops dual mode for a unit and must be entered in the operational cluster. Create a MIS file
before stopping dual mode on slices 2 and 3.

Switch Dual Mode 475

SWDUAL:[<UNIT>][,<HOTSTART>];
This command changes the cluster from operational to stand-by and vice versa. The operational cluster
controls the hardware. The stand-by cluster only controls some devices on the BIM.

67.2. MAINTENANCE MODE (CPU3000 only)

A CPU3000 system can be switched into maintenance mode. This allows for loading (new) software (CPU,
projecting data) into an operational system with the possibility of fall back. Fall back means in this case,
return the system into the situation it was, before maintenance mode was entered. The CPU is for this
purpose equipped with two disk devices that can be accessed via two different Logical Device Names (LBU
and DBU). The original software will be on the LBU and the new software can be put on the DBU. By
swapping, the DBU or LBU can be put 'under' the CPU as environment to work on. If the new software
causes problems, the system or the maintenance engineer can decide to fall back to the existing software.
The system performs the fall back based on a guarding timer, the maintenance engineer by an OM
command (SPMAIN).

Start Maintenance Mode 533

STMAIN:[<UNIT>][,[<RESTART>][,[<HOTSTART>][,[<GUARDING-TIME>]]]];
In order to perform a safe upgrade via a remote port, it is recommended to enter the maintenance mode,
using the OM command STMAIN. Also local upgrade using the maintenance mode is possible.In case the
upgrading process fails for what ever reason, the system will fall back after x minutes (specified by
parameter GUARDING-TIME) to its original configuration. If GUARDING-TIME is omitted a default value of
30 minutes will be applied by the system.

Note: As long as the system is in the maintenance mode, all activity that is by default performed on the
LBU, will then be performed on the DBU, for example RTRIEV.

To leave the maintenance mode, once the upgrade has been performed and is satisfying, use the OM
command SPMAIN.
UNIT may only be omitted in a single unit system.
If RESTART is omitted the system will enter maintenance mode without performing a restart. Optionally
RESTART can be specified (Reload, Cold Start or Projecting). The specified RESTART is executed when the
maintenance mode is entered with STMAIN.
If HOTSTART is omitted no hotstart (0) is assumed.

Stop Maintenance Mode 534

SPMAIN:[<UNIT>][,<FALL-BACK>];
If FALL-BACK is omitted the new installed environment will be made active.
If FALL-BACK is requested (1) the system will install the original environment.

- 219 -
67.3. PMC-IP / PMC-SIC / SIC

SIC : Server Interface Card

PMC-SIC : Peripheral Module Controller – Server Interface Card
Next to the SIC functionality this board also offers “PMC” functionality.
PMC-IP : Peripheral Module Controller – IP Gateway
Next to the PMC-SIC functionality this board also offers “ISG” functionality, when projected.
ISS/ISS-2/ISS-3: This is a functional name for the combination of an In Skin Server (ISS),
mounted on a PMC-IP, PMC-SIC or SIC

The PMC-IP, PMC-SIC or SIC board can be configured in a :

- “hybrid” iS3000 system with a TDM-based switching network.
System option 179 “Native SIP Server” is set to “0”.
- “native IP” SIP@Net Server system has an IP-based switching network.
System option 179 “Native SIP Server” is set to “1”.

Change SIC Configuration Item 614 # !

CHSICI:[<SHELF>],[<BRD>],[<SIC-ITEM>][,[<SIC-ITEM-VALUE>]];
Before executing this command, first check system option 179 “Native SIP Server”.

• In a “hybrid” iS3000 system : system option 179 “Native SIP Server” is set to “0”.
OM command CHSICI sets the IP address that the CPU will use to establish an IP link with the PMC-IP,
PMC-SIC or SIC. The CPU will only attempt to connect to the PMC-IP, PMC-SIC or SIC when an IP address
to the PMC-IP, PMC-SIC or SIC has been projected.
Parameters <SHELF> and <BRD> must be omitted !!!
In case parameter <SIC-ITEM> is omitted the values are reset to factory defaults.

Example :
<CHSICI:,,1,192.168.5.10;

• In a “native IP” SIP@Net Server system : system option 179 “Native SIP Server” is set to “1”.
In a SIP@Net Server one or more IP-PMs can be projected. Each IP-PM has its own PMC-IP, PMC-SIC or
SIC board. It must be possible to maintain and configure each PMC-IP, PMC-SIC or SIC individually. Note
that a SIC is not addressable using an EHWA, therefore the SIC is addressed using the EHWA of the PMC
it provides the IP link to.
So, parameters <SHELF> and <BRD> indicates the PMC that is connected via the PMC-IP, PMC-SIC or SIC.

In the example below it is assumed that there are two IP-PM shelves : 12 and 13.

Example :
<CHSICI:12,17,1,192.168.5.10;
<CHSICI:13,17,1,192.168.5.10;

When executing the SIC (PMC-SIC/PMC-IP) related OM commands (CHSICI, DISICI and RESICI) might give
one of the following error messages :

Error Meaning
110 : Failed to connect to SIC SIC is unreachable
111 : SIC is not supported on this platform SIC is only functional on server
112 : Media Server is used instead of SIC SIP@Net server is configured to use a Media Server (system
option LOSYSOP 179)

- 220 -
Display SIC Information 615
DISICI:[<SHELF>][,[<BRD>]];
OM command DISICI is used to display information related to the PMC-IP, PMC-SIC or SIC. Parameter
<SHELF>,<BRD> indicates the “PMC” position.
The <SHELF> and <BRD> parameters must only be given in case of an IP-PM connected to a SIP@Net
Server : system option 179 “Native SIP Server” is set to “1”.
The <SHELF>,<BRD> parameters must be omitted in systems not using IP media : system option 179 “Native
SIP Server” is set to “0”.

The following information is displayed :

- the loaded boot package and application package
- the IP address, default gateway, boot server, netmask with an indication if the IP address is a fixed IP
address or has been obtained using DHCP, and
- the status of the links for the PMC/CSN that are controlled via the SIC. Their requested status is INS. The
status shown is the current status.
- the SVR# is the Slave Server number (in a Server Cluster configuration only) that is allowed to take over
the control of the IP-PM in case the Master Server is down.

The IP address in the 1st line is the projected address of the PMC-IP, PMC-SIC or SIC and will always be
shown. The rest of the information is read from the PMC-IP, PMC-SIC or SIC at the projected address.
If no valid PMC-IP, PMC-SIC or SIC is addressed, or when the PMC-IP, PMC-SIC or SIC is unreachable for
another reason, then those items will be shown as '-'.
The layout for the DISICI OM command depends on the system layout, therefore some realistic examples
are given below.

• On PMC-IP, PMC-SIC or SIC IPv4

<DISICI:11,17;
SIC IP ADDRESS NETMASK DEFAULT GATEWAY
192.168.9.116:2950 255.255.255.0 192.168.9.1

ETHERNET ADDRESS DHCP TFTP SERVER

00-18-27-00-63-9B Yes 192.168.9.251

SIC IP ADDRESS
[fd01:aaaa:0:22:38a7:bf2a:c35c:12f7]:2950

BOOT-PACK APPL-PACK HW-12NC HW-SERIAL#

C090.01.01 C000.01.01 9600-021-53003 SBxxx00012

SHELF BRD STATUS LPORT SIC IP ADDRESS SVR#

11 17 INS 20112 192.168.9.51:22094 10

On hybrid CSN (IPv4) the output is similar to the example above for PMC-IP IPv4

• On PMC-IP IPv6:
<DISICI:11,17;
SIC IP ADDRESS
[fd01:aaaa:0:22:38a7:bf2a:c35c:12f7]:2950

ETHERNET ADDRESS DHCP TFTP SERVER

00-18-27-00-63-9B Yes fd01:aaaa:0:22:38a7:bf2a:c35c:1299

SIC IP ADDRESS NETMASK DEFAULT GATEWAY

192.168.9.116:2950 255.255.255.0 192.168.9.1

BOOT-PACK APPL-PACK HW-12NC HW-SERIAL#

C090.01.01 C000.01.01 9600-021-53003 SBxxx00012

SHELF BRD STATUS LPORT SIC IP ADDRESS SVR#

11 17 INS 20112 [fd01:aaaa:0000:2200:38a7:bf2a:c35c:1300]:22094 10

- 221 -
Reset SIC Interface 616 # !
RESICI:[<SHELF>][,[<BRD>]];
Enter password for degradation level 1:;

OM command RESICI resets the SIC board and disconnects the link with the CPU (ISS/ISS-2/ISS-3).
It is only possible to reset a SIC that can be reached using the projected IP address.
Parameters <SHELF> and <BRD> indicates the PMC that is connected via the SIC.
These parameters must only be given in case of an IP-PM.
When no connection can be made to the SIC the command is REJECTED with the message :

Error Meaning
110 : Failed to connect to SIC SIC is unreachable

67.4. DUAL SERVER / SERVER CLUSTER

The SIP@Net Server can operate in the following redundant configurations :

• Dual Server configuration

one Active Server and one Stand-by Server, either in LAN or WAN.

• Server Cluster configuration

one Master Server and one (or more) Slave Servers.
Optionally, the Master Server on its own can be a Dual Server LAN configuration.

Switch Cluster Server 625 !

SWCSVR:<ACTION>;
The OM command SWCSVR "Switch Cluster Server" is used to change the operation mode of a Dual Server
Configuration. The command is also used to allow data changing OM actions in the Standalone mode.

Parameter <ACTION> can be :

- 1 = Switch Active/Standby Server : the command is only accepted on the Active Server.
- 2 = Allow OM in Standalone mode.

Assign Cluster Server Data 627 # !

ASCSVR:<SERVER-NUMBER>;
This command asks for the following additional parameters, depending on the value of system boundary
448 (IP version support) :

448 = 0 : IPv4 only 448 = 1 : IPv6 only 448 = 2 : both IPv4 & IPv6
<OWN-IPV4-ADDRESS>; <OWN-IPV6-ADDRESS>; <OWN-IPV4-ADDRESS>;
<APPLICATION-IPV4-ADDRESS>; <APPLICATION-IPV6-ADDRESS>; <OWN-IPV6-ADDRESS>;
<MASTER-SERVER>; <MASTER-SERVER>; <APPLICATION-IPV4-ADDRESS>;
<APPLICATION-IPV6-ADDRESS>;
<MASTER-SERVER>;

Note that in SIP@Net 5.2.1 (and higher), an extra parameter (IP-SIG-GROUP) was asked for.
However that parameter is not relevant anymore, and therefor it has been removed since SIP@Net 6.1.

- 222 -
For each item either :

- a new value can be given

- the value is not changed by typing ';'
- the value is deleted by typing '-;'

The items configured with OM command ASCSVR are not maintained in the Windows registry.
This command can not be used to install the individual servers in a Dual Server or Server Cluster
configuration.
First the individual servers have to be installed by running the SIP@Net installer on each server and by
choosing the required configuration. Once all individual servers are installed, the projecting of the whole
configuration has to be specified, using OM command ASCSVR. So be sure that the various IP addresses
specified in ASCSVR are identical to the IP addresses, initially specified in the SIP@Net installer.
To make the settings active re-project the various servers by “STOP” and “START” the SIP@Net Service.
The parameters set by ASCSVR can be read on using command DICSVR.

Display Cluster Server Data 633 !

DICSVR:[<SERVER-NUMBER>];
This command shows the various IP-addresses, netmask and default gateway address of the Dual Server
SIP@Net configuration. It also shows which is the Active Server or the Standby Server and whether the Dual
Server Protocol is up. If the Own IP Address has been found on a network interface card (NIC) then the
items found on the NIC are displayed in column Adapter. If the NIC hasn't been found then instead of the
Physical Address "Not found" is displayed.

Response example of a single server with system boundary 448 = 0 : IPv4 only.

<DICSVR:;
ITEM VALUE
Server Single Server
Physical Address 00-30-D6-10-73-0A
Application IPv4 Address 192.168.116.20
Subnet Mask 255.255.255.0
Default Gateway -

ITEM VALUE (Set by SIP@Net Installer)

Application IPv4 Address 192.168.116.20
Own IPv4 Address -

Response example of a single server with system boundary 448 = 2 : both IPv4 & IPv6.

<DICSVR:;
ITEM VALUE
Server Single Server
Physical Address 00-30-D6-10-73-0A
Application IPv4 Address 192.168.116.20
Application IPv6 Address fe80::473:2ddf:2bf0:2829
Subnet Mask 255.255.255.0
Default Gateway -

ITEM VALUE (Set by SIP@Net Installer)

Application IPv4 Address 192.168.116.20
Application IPv6 Address fe80::473:2ddf:2bf0:2829
Own IPv4 Address -
Own IPv6 Address -

- 223 -
Below a response example is shown of a Server Cluster configuration of three Slave Servers (2, 3 and 4) and
one Master Server, which is a Dual Server configuration, server 1 and 5 (system boundary 448 = 2 : both
IPv4 & IPv6).

<DICSVR:;
ITEM VALUE
Server (1) ACTIVE Master
Dual Server Protocol Up (5) Yes fd01:aaaa:0:22:192:168:99:101
Cluster Server Protocol (2) Yes fd01:aaaa:0:22:192:168:99:100
Cluster Server Protocol (3) Yes fd01:aaaa:0:22:192:168:2:100
Cluster Server Protocol (4) Yes fd01:aaaa:0:22:192:168:10:100
Physical Address 00-12-34-56-78-9A
Application IPv4 Address 192.168.99.200
Application IPv6 Address fd01:aaaa:0:22:192:168:99:200
Subnet Mask 255.255.255.0
Default Gateway 192.168.99.1
Own IPv4 Address 192.168.99.100
Own IPv6 Address fd01:aaaa:0:22:192:168:99:100

ITEM VALUE (Set by SIP@Net Installer)

Application IPv4 Address 192.168.99.200
Application IPv6 Address fd01:aaaa:0:22:192:168:99:200
Own IPv4 Address x) 192.168.99.100
Own IPv6 Address x) fd01:aaaa:0:22:192:168:99:100

<DICSVR:1;
ITEM VALUE
Server Number 1
Own IPv4 Address y) 192.168.99.100
Own IPv6 Address y) fd01:aaaa:0:22:192:168:99:100
Application IPv4 Address z) 192.168.99.200
Application IPv6 Address z) fd01:aaaa:0:22:192:168:99:200
Server Configuration Master

x) : a possible (!) here indicates that the :

Own IP address in the registry is not available on this machine.

y) : a possible (!) here indicates that the :

Own IP address given with ASCSVR does not match the own IP address in the registry, or
Own IP address given with ASCSVR for an other server does match the own IP address in this registry.

z) : a possible (!) here indicates that the :

Application IP address given with ASCSVR does not match the Application IP address in the registry, or
Application IP address given with ASCSVR for an other server does match the Application IP address in
this registry.

Delete Cluster Server Data 634 # !

DECSVR:[<SERVER-NUMBER>];
This command can be used to delete the Server Cluster configuration items.

- 224 -
68. UNIT STATUS
Display Unit Status 30
DIUNIT:<UNIT-1>[,<UNIT-2>s/r];
The unit status displayed is the status of UNIT-2 as seen by UNIT-1.
Response:
UNIT MANAGEMENT COMMUNICATION CURRENT
NUMBER STATUS STATUS ROUTING
xxx xxx xxx xxx

The management status can be INS (installed) or NIN (not installed), the communication status can be
Established or Lost and the current routing can be Primary or Alternate.
If UNIT-2 is entered as a single parameter, the display will be continuous and can be aborted by ‘Ctrl X'.

Set Unit Status to Installed 31 #

UNIINS:[<UNIT-1>s/r],<UNIT-2>;
The unit status modified is the status of unit 2 as seen by unit 1. When unit 1 is omitted, it is executed in all
units.
Response:
Password for degradation level 2: ?

Set Unit Status to Not Installed 32 #

UNININ:[<UNIT-1>s/r],<UNIT-2>;
The unit status modified is the status of unit 2 as seen by unit 1. When unit 1 is omitted, it is executed in all
units.
Response:
Password for degradation level 2: ?

- 225 -
69. VOICE LOGGING
This group of OM commands is used to change and display the relation between a Voice Logging Subject
and a Voice Logging Destination. 'VL-SUBJECT' as well as 'VL-DESTINATION' are internal DNRs.
Note that an operator DNR can also be a 'VL-SUBJECT'.

Voice Logging requires license 48.

Assign, Change or Delete Voice Logging Relation 484 # !

CHVLRE:[<VL-SUBJECT>s],[<VL-DESTINATION>];
The 'VL-SUBJECT' is the DNR that has to be logged and the 'VL-DESTINATION' is the DNR of the logging
device.
- when 'VL-SUBJECT' was assigned before, the relation will be updated.
- when 'VL-DESTINATION' is omitted, the relation will be deleted.
- when 'VL-SUBJECT' and 'VL-DESTINATION' are omitted, all relations will be deleted.

This command may be password protected :

OM command CHPASS:6,2;

Display Voice Logging Relation 516

DIVLRE:[<VL-SUBJECT>];
The 'VL-SUBJECT' is the DNR that is voice logged.
When 'VL-SUBJECT' is omitted, all relations are shown.
Response example:
Subject Destination
2300 1822
6230 1041
3305 6681

Total of 3 used and 8 free in unit 2

If Voice Logging is not licensed, the summary line in the response is:

Total of 3 used and 8 free in unit 2 (NOT LICENSED)

- 226 -
A. ERROR MESSAGES
This chapter contains an overview of the error messages and codes related to OM commands.

1 … 99 : Fixed resident error messages

100 … 189 : Specific non-resident error messages
190 … 256 : General error messages

A.1. FIXED RESIDENT ERROR MESSAGES (1 ... 99)

1. Parameter 1 out of range.

The first parameter of the command has an entered value which is out of range according to
projectable boundaries or a fixed mode set.
Examples are an offered route number of 120 while the maximum number of routes is 100, a DNR
containing an over-ten digit while the DNR-radix number is projected to 10 or an entered digit
representing an option while the digit can not be translated to a legal value of an internal mode set.
2. Parameter 2 out of range.
As "Parameter 1 out of range" but for the second parameter.
3. Parameter 3 out of range.
As "Parameter 1 out of range" but for the third parameter.
4. Parameter 4 out of range.
As "Parameter 1 out of range" but for the fourth parameter.
5. Parameter 5 out of range.
As "Parameter 1 out of range" but for the fifth parameter.
6. Parameter 6 out of range.
As "Parameter 1 out of range" but for the sixth parameter.
7. Parameter out of range.
As "Parameter 1 out of range" but to be used for additional parameters.
8. Non existing value of parameter 1.
The value of parameter 1 is within the boundaries but is not known to the system while it is a
requirement of the command that is should be known.
Examples: A DNR that should be known (e.g. when assigning a facility to the DNR) but is not known in
Translation Service. A route, a convertor type, a facility class mark being within boundaries but not
known in the corresponding service process.
9. Non existing value of parameter 2.
As "Non existing value of parameter 1" but for parameter 2.
10. Non existing value of parameter 3.
As "Non existing value of parameter 1" but for parameter 3.
11. Non existing value of parameter 4.
As "Non existing value of parameter 1" but for parameter 4.
12. Non existing value of parameter 5.
As "Non existing value of parameter 1" but for parameter 5.
13. Non existing value of parameter 6.
As "Non existing value of parameter 1" but for parameter 6.
14. Non existing value of parameter.
As "Non existing value of parameter 1" but for additional parameters.
15. Already existing value of parameter 1.
The value of parameter 1 is within the boundaries but already known to the system while it is a
requirement of the command that is should not be known yet.
Examples: A route, a convertor type, a cv-value etc., which is to be created, being within boundaries
but already known in the corresponding service process.
16. Already existing value of parameter 2.
As "Already existing value of parameter 1" but for parameter 2.

- 227 -
17. Already existing value of parameter 3.
As "Already existing value of parameter 1" but for parameter 3.
18. Already existing value of parameter 4.
As "Already existing value of parameter 1" but for parameter 4.
19. Already existing value of parameter 5.
As "Already existing value of parameter 1" but for parameter 5.
20. Already existing value of parameter 6.
As "Already existing value of parameter 1" but for parameter 6.
21. Already existing value of parameter.
As "Already existing value of parameter 1" but for additional parameters.
22. Parameter 1 missing.
Parameter 1 is omitted while it is not allowed according to system options or previously successfully
executed commands.
If the parameter is omitted conflicting with the value of another parameter in the same command
string the message "Illegal parameter combination" is used instead.
Example: Parameter 1 is the unit number. This parameter may only be omitted in a single unit-
system (project dependent). In a multi-unit system then this message is generated.
23. Parameter 2 missing.
As "Parameter 1 missing" but for parameter 2.
24. Parameter 3 missing.
As "Parameter 1 missing" but for parameter 3.
25. Parameter 4 missing.
As "Parameter 1 missing" but for parameter 4.
26. Parameter 5 missing.
As "Parameter 1 missing" but for parameter 5.
27. Parameter 6 missing.
As "Parameter 1 missing" but for parameter 6.
28. Illegal parameter combination.
This message is used when parameters within a command are related to each other. The value of one
parameter can exclude the value of another parameter or the value of one parameter may require
that another parameter is omitted. For cases like these it can not be determined which parameter
actually is wrong (fatal validation).
This message is also used if a certain parameter is composed of several items (e.g. a parameter is a
bit-stream, each bit representing an option). If one item of the parameter excludes another item
within the same parameter this message can be used. As it is known which parameter is wrong this
error may be non-fatal.
29. Device is write protected.
An attempt is made to write to a write protected device.
30. Lack of space.
This message is used as an execution error because no room is available in the corresponding service
process to add new data. In most cases it will be evident which specific action causes the error as
most commands add only one relation at a time so this error message will give sufficient information.
31. No relations or data found.
This message is used in commands performing a display function.
Example: All abbreviated numbers are to be displayed but there are no abbreviated numbers defined
at all.
32. EHWA not in use.
The elements of an entered EHWA are within the boundaries but the EHWA is not known to the
system while it is a requirement of the command that is should be known.
Example: A DNR is to be assigned to an LCT but the LCT (by its EHWA) is not known.
33. EHWA already in use.
The elements of an entered EHWA are within the boundaries but the EHWA is already known to the
system while it is a requirement of the command that is should not be known yet.

- 228 -
 Example: A board is to be installed at a certain position but that position (by its EHWA) is already
occupied.
34. EHWA has incorrect type.
Is used for actions on a resource (entered as EHWA) while the type of the entered EHWA does not fit
with the action.
Example: A DNR is to be assigned to an LCT but the offered EHWA belongs to a trunk.
35. Incorrect status.
If an action to be performed on a resource requires a certain status (NIN, OUT, etc) and the resources
does not have this status this message is used.
36. DNR has incorrect type.
Used for actions on a DNR while the DNR has not the correct type (operator, group, extension).
Example: An extension has to be moved but the offered DNR belongs to an operator instead of an
extension.
37. Resource not assigned.
Used for actions on a resource that should be assigned to a certain pool.
Example: A trunk is to be removed from a bundle while it is not assigned.
38. Resource already assigned.
Used for resources which are to be assigned to a certain pool.
Example: Trunk lines, paging lines, paging codes to be assigned to a route while it is already been
assigned before.
39. Invalid input data.
The entered data in a command is conflicting with earlier entered data or data of one parameter is
conflicting with data of another parameter in the same command string.
40. Not yet implemented.
Standard message to cover an action within a command which has not yet been implemented.
41. Restriction on action.
Besides the authority class mechanism also restrictions within a command are possible. If within a
command a certain action is to be performed while this action is restricted to certain users only or
not possible because of implementation reasons this message is used.
Example: From a certain OM terminal it is only allowed to change only a few facility class marks
and/or traffic classes
Another example is derived from the limited possibilities of OM from the operator console. For a
certain action a password is required. As passwords contain characters which are not available at an
operator console this action will not be possible (restricted to OM terminals).
42. File specification error.
File specifications are normally a concatenation of logical device name and file name (plus extension)
in one parameter. Depending on the context certain characters are allowed or not. If the parameter
contains invalid characters this message is used.
43. Source file specification error.
As "File specification error" but to be used in commands with more file specifications in the same
command string.
44. Destination file specification error.
As "File specification error" but used in commands with more file specifications in the same
command string.
45. Logical device does not exist.
File specifications are normally a concatenation of logical device name and file name (plus extension)
in one parameter. First check will always be to check the parameter on invalid characters. If invalid
characters are present the message " ... file specification error" will be used. If not, it will be checked
if the logical device name part refers to an existing logical device. If not this message "Logical device
does not exist" is used. If the parameter is not a file specification but only a logical device name the
message "Non existing value of parameter x" is used instead.
46. Source logical device does not exist.
As "Logical device does not exist" but used in commands with more file specifications in the same
command string.

- 229 -
47. Destination logical device does not exist.
As "Logical device does not exist" but used in commands with more file specifications in the same
command string.
48. File open error.
Execution error when accessing a file to be opened.
49. File write error.
Execution error when accessing a file for writing.
50. File read error.
Execution error when accessing a file for reading.
51. File delete error.
Execution error when accessing a file to be deleted.
52. File close error.
Execution error when accessing a file to be closed.
53. File specification incomplete.
File specifications are normally a concatenation of logical device name and file name plus extension
and generation in one parameter.
Depending on the command one or more of these parts may be omitted.
Defaults then may be used per part. If a part is omitted while no default is known this message is
used.
54. Source file specification incomplete.
As "File specification incomplete" but used in commands with more file specifications in the same
command string.
55. Destination file specification incomplete.
As "File specification incomplete" but used in commands with more file specifications in the same
string.
56. Illegal password entered.
Password is not correct.
57. File not found.
The specified filename does not exist.
58. Source file open error.
The specified (source) filename does not exist.
59. Destination file open error.
The specified (destination) filename does not exist.
60. Protection level mismatch.
Your protection level does not permit the requested action.
61. Maximum number of open files exceeded.
The maximum number of open files is reached, so it is not possible to open another one.
62. File already opened.
63. End of medium detected.
64. Device hardware error occurred.
65. Unreliable device.
66. Device unobtainable.
67. BSP-ID not unique
68. BSP-ID does not exist
69. Action not allowed for Internal Backup Unit (IBUxx)
70. Command not supported on this ISPBX
71. Action not allowed in dual mode
72. Action not allowed in dual mode on standby or slave cluster
73. UPDUAL still in progress
74. UPDUAL finished
75. Command not supported for this device
76. Parameter 7 out of range
As "Parameter 1 out of range" but for the seventh parameter.

- 230 -
77. Parameter 8 out of range
As "Parameter 1 out of range" but for the eight parameter.
78. Parameter 9 out of range
As "Parameter 1 out of range" but for the ninth parameter.
79. Parameter 10 out of range
As "Parameter 1 out of range" but for the tenth parameter.
80. Non existing value of parameter 7
As "Non existing value of parameter 1" but for parameter 7.
81. Non existing value of parameter 8
As "Non existing value of parameter 1" but for parameter 8.
82. Non existing value of parameter 9
As "Non existing value of parameter 1" but for parameter 9.
83. Non existing value of parameter 10
As "Non existing value of parameter 1" but for parameter 10.
84. Already existing value of parameter 7
As "Already existing value of parameter 1" but for parameter 7.
85. Already existing value of parameter 8
As "Already existing value of parameter 1" but for parameter 8.
86. Already existing value of parameter 9
As "Already existing value of parameter 1" but for parameter 9.
87. Already existing value of parameter 10
As "Already existing value of parameter 1" but for parameter 10.
88. Parameter 7 missing
As "Parameter 1 missing" but for parameter 7.
89. Parameter 8 missing
As "Parameter 1 missing" but for parameter 8.
90. Parameter 9 missing
As "Parameter 1 missing" but for parameter 9.
91. Parameter 10 missing
As "Parameter 1 missing" but for parameter 10.
92. Additional parameter 1 out of range
93. Additional parameter 2 out of range
94. Additional parameter 3 out of range
95. Additional parameter 4 out of range
96. Additional parameter 5 out of range
97. Additional parameter 6 out of range
98. Additional parameter 7 out of range

A.2. SPECIFIC NON-RESIDENT ERROR MESSAGES (100 ... 189)

• OM for ANALYSIS GROUP, COMPATIBILITY VALUE AND SERVICE PROFILE

120 BSPT value not allowed for group DNR
• OM for BACKUP MAINTENANCE
110 BM or OM lock was set by:
111 BM or OM lock already set by:
112 BM lock was not set
113 BM lock not set ! (CHJOUR)
113 BM lock should be set first ! (GEBUMI/RTRIEV)
114 No new journal file created
115 Error deleting old journal file !
116 Old journal file not deleted
117 SIN overflow encountered
118 Journal updating switched off; no systemwide GEBUMI allowed

- 231 -
 119 Not allowed in dual mode on this operational cluster
119 Journal not found (GEBUMI)
120 Not allowed to set network incompatible
121 Not all package-ids equal
122 BM lock not set because OM lock already set; OM lock set by:
148 Delete not allowed
• OM for CALL FORWARDING
120 DNR already assigned the selective call answering facility
• OM for CAMP ON BUSY
120 BSPT value not allowed for group DNR
• OM for CIRCUIT CONDITIONS
111 Higher degradation level required
112 It is not allowed to deactivate this resource
113 Continuation deactivates the CBU. Switch off journal update first !
114 No virtual channel assigned
137 Action not allowed because there are already two CCS slices masked
138 It is not allowed to deactivate the local SMPC
139 Action not allowed because port has no logical device yet
140 Last OM device may not be deactivated on this ISPBX platform
186 It is not allowed to deactive shelves, modules or the CPU
• OM for COMMAND FILE EXECUTION
180 Command file specification error
181 Log file specification error
182 Date and time not set (use SEDATI)
183 Command file not found
184 Log file not found
185 Maximum number of jobs already submitted
186 Job not submitted due to internal error; try again
187 Maximum file length [4000char's] exceeded
188 Incompatible command file
189 Use EXSJOB for special batch files
• OM for DATA FUNCTIONS
120 No expanded cv modes
122 Still EHWAs for convertor type present
• OM for DIGITAL ALARMS
110 Resource not in service
• OM for DISPLAY METERING
120 BSPT value not allowed for operator DNR
• OM for DNR/BSP-ID - LINE CIRCUIT RELATIONS
120 No space for new DNR
121 DNR is not assigned
122 DNR is already assigned to other EHWA
123 Move not possible - too many BSPs assigned
124 WARNING : EHWA now contains more than one BSP-ID!
125 No space for LENR data
126 No space for IABD data
127 DNR is special extension
128 Not all IABD numbers are transferred
129 DNR or EHWA busy
130 (Some) involved BSP is executive or secretary
133 DNR is groupmember
134 DNR already in use
135 No space for BSP data

- 232 -
 136 No space for night extension data
137 No space for diversion to external data
138 No space for executive data
139 No space for hotline data
140 DNR and/or BSP already assigned to given EHWA
141 Incorrect BSP-ID or DNR has incorrect type
142 ALL-BSPT (99) not allowed
143 Maximum number of BSPs with given DNR already assigned
144 BSPT does not exist
145 BSP-ID already exists
146 DNR has been assigned the selective call answering facility
147 BSP is executive or secretary
148 No space for password data
149 BSPT does not contain IBSC
150 Special extension is already assigned to EHWA
151 No desksharing license
152 Special extension may not be moved to hardware-less position
153 Another Basic DNR for this unit already exists
154 After this action the BSP will be not-usable
155 No space for CNND data
156 CNND relation not transferred
157 Not all IABD numbers and CNND relations are transferred
• OM for DOWNLOAD
110 Download package delete error
111 No reply on delete error
120 ALL-BSPT (99) not allowed
121 Incorrect BSP-ID or DNR has incorrect type
• OM for EXECUTIVE/SECRETARY GROUPS
120 Executive BSP-ID has incorrect type or is already assigned
121 Secretary BSP-ID has incorrect type or is already assigned
122 Identifying BSP-ID is incorrect
123 Executive and secretary BSP-ID are not located in the same unit
124 Warning: BSP-ID is assigned to other executive-secretary pool or group
125 Warning: BSP-ID is not related to a feature phone
126 Warning: BSP-ID is already related to a function key menu
127 BSP-ID already in use
128 File already present
129 New command file written
130 Executive and secretary BSP-ID not located within the one unit
131 Group DNR is special extension
140 Warning: Function key menus should be used for exec/sec group
141 Number of function key menus too small
142 Group property not allowed
144 BSP-ID already assigned the selective call answering facility
145 ALL-BSPT (99) not allowed
146 BSP-ID with same identifying DNR already assigned to this group
147 Executive BSP-ID is already assigned as ACD group member
148 Secretary BSP-ID is already assigned as ACD group member
• OM for FACILITY CLASS MARKS
120 Mark is R/O or not existing or disabled on this type of DNR
121 Action not allowed for this facility class mark
124 Incorrect BSP-ID or DNR has incorrect type
• OM for FILE MANIPULATION
140 Directory file not found

- 233 -
 141 Directory file open error
142 Directory read error
143 Source file read error
144 Copy read error >Check presence of incomplete destination file !
145 Copy write error >Check presence of incomplete destination file !
146 Delete not allowed
147 Binary files may not be typed
148 Purge not allowed
149 Unexpected File Manager reply with warning
150 Unexpected File Manager reply
151 Copy write error
152 Wild cards not supported on this device
153 Error in internal zip algorithm
• OM for FOLLOW ME
151 Originator is not follow me entitled
152 Destination is follow me protected
153 Action currently not allowed
154 ALL-BSPT (99) not allowed
• OM for FUNCTION KEYS AND MENUS
120 ALL-BSPT (99) not allowed
132 Key-data indicates park position: led code not allowed
133 Key-data indicates executive line position: wrong led code
134 Key-data indicates executive line position: led code missing
135 Function_key/level doesn't allow key-data for park/line position
136 Series/range not allowed for function key or level when assigning data
137 Key-data indicates automatic transfer: wrong led code
138 Key-data indicates automatic transfer: led code missing
139 Function key doesn't allow key-data for automatic transfer
• OM for GENERAL CANCEL CODE
120 Result-id not allowed for general cancel code
• OM for GROUP ARRANGEMENTS
120 Group DNR and/or member BSP-ID are special extension DNR
121 Group has no ACD property (DIGRPS)
121 Member BSP-ID has incorrect type or is already assigned (CRGRPA/ASGRPM)
122 No-member group not allowed
123 DNR already in use
124 Member BSP-ID cannot be switched to absent
125 Still follow me relation present
126 Still call forwarding relation present
127 Park/line position only allowed in non ACD group
128 Option F of extended properties may only be set for ACD groups
129 DNR not found
130 BSP-ID already assigned the selective call answering facility
131 A no-member group may not be switched to Day status
132 BSP-ID with same identifying DNR already assigned to this group
133 BSP-ID or DNR does not exist
134 ALL-BSPT (99) not allowed
135 Member with same DNR already assigned to group with same supervisor
136 Member BSP-ID is already assigned as executive
137 Member BSP-ID is already assigned as secretary
138 No space for new ACD group member
139 DNR has incorrect type or group has no ACD property
140 No logical device assigned due to lack of space
141 No more members allowed in Multiple Ring Group

- 234 -
 142 Group DNR and member BSP-ID are not located in the same unit
143 No space for member or group assignment
• OM for HARDWARE CONFIGURATION
110 Not allowed circuit number at board
111 Action not allowed when journal updating switched ON !
112 Still boards in shelf present
113 The sequence number is invalid
114 Still links present
115 Still devices present
116 Still bundle-DTU relations present with bundle
117 Still a DNR present
118 Still line-route relations present
119 Still line-bundle relations present
120 Still special extension relations present
121 Still D-channel relation present
122 Still CRU-entry present
123 Still main-slave board relation present
124 Not allowed to delete last LDN
125 Still LDN relations present (DEDEVC)
125 Still tone sources present (DEBRDS)
126 Still boards controlled by this board present
127 Port occupied by B-channel of adjacent ISDN bus
128 A port, required for B-channel, is already in use
129 Different PCT-types not allowed at same bus
130 Module controller board is already present
131 PMC-MC-PRIMARY board may not be deleted
132 CSN-BC board may not be deleted
133 Only one remote port allowed in unit
134 Board not yet assigned
135 Illegal link combination
136 Link can not be deleted
137 This fixed device may not be deleted
138 Device name or type incorrect or not allowed for this port
139 Link type not allowed
140 Device not known as local device in unit (ASLDNM)
140 Link circuit number out of range (ASLINK/DELINK)
141 Still remote PM or Interunit link present in local PM
142 First CSN-PMC link has to be assigned to local PM
143 Still device ports present
144 First assign the SNS board(s) with lower EHWA
145 First assign the SNS board(s) with higher EHWA
146 Conflict between equipment type and LDN
147 Not allowed to delete circuit
149 LBU and DBU may not be deleted on this ISPBX
150 Device not known as local device in unit
151 Not all requested virtual circuits is assigned
152 Equipment type not supported on this ISPBX
160 This link can not be assigned as a controllable link
161 Board not yet assigned
162 Controller board not yet assigned
163 Link incompatible with board
164 Device incompatible with board
165 Assign the controllable links to this destination first
166 Delete the not controllable links to this destination first

- 235 -
 167 Still PCH resources in use
168 Not enough PCH resources available
169 Incorrect board position
170 Main board not present
171 DTU-CC not used in interunit link
172 DTU-CC already used in link
173 Parameter NVCT not allowed for given EHWA
174 Value for parameter 4 is not allowed on this ISPBX platform
175 Board is not an SCU board
176 Link assigned, but due to lack of space no or not all ILCs (ASLINK)
176 Not all requested virtual circuits assigned (ASBRVC)
177 Inconsistent data detected in HCA
178 Shelf not yet assigned
179 DTU already used with other CRU-entry
180 Still virtual circuits present
181 Still convertor present
182 Change board subtype not allowed for this board
183 Board of circuit is not yet assigned
184 Not allowed; use assign/delete board command
185 No related board characteristics table found
187 Board is not a PMC-MC-MASTER board
188 Board is not a CSN-BC
189 Board is not a PMC board
• OM for IABD AND LENR FACILITIES
120 DNR has no IABD and LENR FACM assigned
• OM for INITIALISE DISK
140 It is not allowed to initialise a CBU
141 Device no storage device
142 Command currently not allowed. Files open on device, try again.
• OM for INTEGRATED ANNOUNCEMENT SYSTEM
121 Group has no ACD property
• OM for INTER UNIT TRUNK TRAFFIC
120 Bundle already assigned
121 Bundle not assigned to route
• OM for LICENSING
110 License file not found or file type incorrect
111 License string incorrect
112 Fingerprint in license file does not match system fingerprint
113 System fingerprint unobtainable
114 Digital signature in license file incorrect
115 Generation date of license string newer than current system date
116 Error in licensing mechanism
117 License string too long
118 SIP@Net Server unlicensed
119 SIP@Net on ISS unlicense
120 Start upgrade period license too low
121 Start upgrade period unlicensed
122 Start upgrade period license invalid
123 Start upgrade period too low and SIP@Net Server unlicensed
124 Start upgrade period too low and SIP@Net on ISS unlicensed
125 Start upgrade period and SIP@Net Server unlicensed
126 Start upgrade period and SIP@Net on ISS unlicensed
127 Start upgrade period invalid and SIP@Net Server unlicensed
128 Start upgrade period invalid and SIP@Net on ISS unlicensed

- 236 -
 130 Mandatory facility "Native SIP Server" would be unlicensed
131 Start upgrade period unlicensed and "Native SIP Server" unlicensed
132 Start upgrade period too low and "Native SIP Server" unlicensed
133 Start upgrade period invalid and "Native SIP Server" unlicensed
• OM for MANAGER DATA
120 BSPT value not allowed for operator DNR
• OM for MERCURY INDIRECT SERVICE
120 Old authorization code validation error
121 New authorization code verification error
• OM for MISCELLANEOUS DNR ACTIONS
120 No local CNND database defined
• OM for MULTIPLE SUBSCRIBER NUMBER
120 Not allowed to change MSN parameters of a DCC circuit
• OM for NIGHT TRAFFIC AND SPECIAL EXTENSIONS
121 DNR already assigned the selective call answering facility
122 Already other special extension type assigned to trunkline
123 Special extension type incorrect
124 DNR is member of special extension group
125 DNR is group with special extension member
• OM for NUMBERING SCHEME
120 Barring mark set
121 Number already barred
• OM for OVERLAY MODULES
140 Overlay not found
141 Delete not allowed
142 Delete postponed until the overlay is unused
143 Delete request pending
144 No loading space available in memory
145 CM device error
146 Error in overlay found
147 Action not allowed for permanent overlays
• OM for PAGING
121 Unit already assigned to a paging area
122 Unit is utility unit
123 Still routes assigned to area
124 Still virtual codes assigned to route
125 Still lines assigned to route
135 Route has incorrect type
• OM for PASSWORD PROTECTED FACILITIES
120 Password relation not found
121 PID/CC not found
122 PID/CC already assigned
123 PID/CC ‘999999' is reserved for malicious call trace
• OM for PERIPHERAL FILE STORAGE MECHANISM
110 File not open
111 Rename and reopen of the file is not allowed
112 File already closed
113 Backup file could not be accessed (protection level mismatch)
114 Backup file could not be accessed (file already opened)
115 Backup file could not be accessed (device hardware error occurred)
116 Backup file could not be accessed (device unreliable)
117 Backup file could not be accessed (device unobtainable)
118 Backup file could not be accessed

- 237 -
 119 File rename error (maximum number of open files exceeded)
120 File rename error (file already opened)
121 File rename error (protection level mismatch)
122 File rename error (device is write protected)
123 File rename error (end of medium detected)
124 File rename error (device hardware error occurred)
125 File rename error (device unreliable)
126 File rename error (device unobtainable)
127 File rename error (action not supported)
128 File rename error
129 File open error (maximum number of open files exceeded)
130 File open error (file already exist)
131 File open error (protection level mismatch
132 File open error (device is write protected)
133 File open error (end of medium detected)
134 File open error (device hardware error occurred)
135 File open error (device unreliable)
136 File open error (device unobtainable)
137 File open error (action not supported)
138 File open error
139 File action failed
• OM for PPH PROTOCOL TRACE
110 Maximum number of applications using the PFSM function is reached
111 File already exists
112 Resource is not in service
113 Application is already running
114 Application is not running
115 Application is not running, but there is still old data available
116 Reserved file used
117 Disk space upper threshold exceeded
118 Resource does not respond
119 Open file not supported on device
• OM for PRIVATE VIRTUAL NETWORKING
120 Old security code validation error
121 New security code verification error
137 Signalling Channel busy
138 UCA busy
139 RIN already assigned to a signalling channel
140 PVN route is not a Main route
• OM for PROJECTING
110 Data rejected by service process
133 No PR and/or LL file
140 PM (being) activated
141 Downloading active
• OM for REMOTE MAINTENANCE
100 The new configuration is stored
110 Either RMAIN0.CNF or RMAIN1.CNF should be used
111 A new configuration file RMAINx.CNF is written (x=remote usergroup)
112 No new configuration file is written
113 Not allowed to clear this item
• OM for SYSTEM DUMP
140 No system dump present
141 Dump already present
142 Writing system dump initiated

- 238 -
 143 Writing system dump already in progress
144 System dump erased
• OM for SYSTEM SECURITY
110 Old password validation error
111 New password verification error (CHPASS)
111 Unknown OM terminal (CHDEAU/CHDEPR/DIAUPR)
120 Authority class index 0..15 can not be changed
121 Authority class value 15 is not allowed
122 No value has been found, given index not known
• OM for TESTING
100 Request already present
101 Request not found
110 B-channel not available for test (CRCCSP/CRCCPP)
111 Error during release of the controlled connection (ERCOCO)
112 The current controlled connection state does not allow this command
113 The digits received are already monitored
114 No digit receiving resource involved in this controlled connection
115 No digit sending resource involved in this controlled connection
116 No tone sending resource involved in this controlled connection
117 Controlled connection rolled back
118 Maximum number of controlled connections exceeded
119 No tone resources allowed in paired path controlled connections
120 Controlled connection erased
121 Error during flow establishment
122 No pulsed sending resource
125 Incompatible resource status
• OM for TOLL TICKETING AND FULL DETAILED CALL RECORDING
110 FDCR facility not active
111 Toll Ticketing facility not active
• OM for TRAFFIC OBSERVATIONS AND MEASUREMENT
110 Traffic measurement not started: already active
111 Traffic measurement inconsistency
112 No figures available; data currently being gathered
113 Figures not yet available
120 ALL-BSPT (99) not allowed
121 BSPT value not allowed for group DNR
122 BSPT value not allowed for operator DNR
• OM for TRAFFIC CLASSES
120 BSPT value not allowed for operator DNR
• OM for TRUNK TRAFFIC
120 Bundle already assigned
122 BSPT is not assigned
123 BSPT not known in system
124 BSPT already assigned
125 BSPT not unique (IBSC overlap)
126 Some B-channels in this circuit already assigned to other bundle
127 BSPT invalid or not assigned
128 Still SCNE or overflow extension assigned to route
129 Still bundles assigned to route
130 Still PVN data assigned to route (ERROUT)
130 Trunk/bundle incompatible with involved EHWA(s) (CHBNDC/ASLINE)
131 No lines allowed in a PVN bundle
132 Signalling-type of bundle and route mismatch

- 239 -
 133 Original number is conflicting with an already defined conversion
134 Invalid input data - too many parameter characters
136 Bundle not in specified route
141 No space for FTLD data
142 FTLI already assigned to other trunk line
143 Special extension assigned to trunk line
144 No bundle-route relations present
145 Trunk line type does not support FTLI/FTLD facility
146 Incorrect number of inc-options (non-DDI : 6, DDI : 10)
147 Incorrect number of tone-and-ddi-optons (non-DDI : 2, DDI : 9)
148 Tree not allowed for non-DDI
149 Incorrect number of options (must be : 4)
• OM for UNIT STARTS
110 A hotstart is not yet possible
111 A MIS-file is required to execute a coldstart
112 A hotstart is not allowed
113 Not all slices synchronous
114 File CONDUA.POM not present on DBU
115 System already in dual mode
116 System not in dual mode
117 Not allowed on this cluster
118 BM lock not set
119 Cluster not operational
120 Empty JOURNL.POM file must be present on CBU and DBU
121 Unable to rename configuration files on LBU or DBU
122 No MIS-file present on LBU or DBU
123 Unit number in CONDUA.POM file differs from CONFIG.POM file for warm start
124 No new MIS-file generated after SWDUAL on this cluster yet
125 CIE or SNS communication error present
126 Hard errors occurred during last memory test
127 Snapshot identification number not equal in JOURNL.POM on CBU and DBU
128 LBU contains CONDUA.POM and/or DBU contains CONFIG.POM

A.3. GENERAL ERROR MESSAGES (190 ... 256)

190. Notice - Projecting unit.

Part of message used during projecting phase (processing LL-file).
191. Notice - Updating unit.
Part of message used during processing journal file (JOURNL.POM).
192. at line number
Part of message used during projecting phase.
193. at sequence number
Part of message used during processing journal file.
194. aborted.
195. disabled
196. completed
197. NO
Enter yes or no, to answer a certain question.
200. Parameter syntax error.
201. Unknown command.
The command is unknown, or the command is not loaded because the local backup device is
currently unavailable.

- 240 -
202. No load space.
The OM (sub)command cannot be loaded due to a lack of space.
203. Command counter overflow.
There are too many simultaneous executions of the same OM (sub)command.
204. Authority class mismatch.
It is not allowed to execute the OM command from the current terminal.
205. Too few parameters.
206. Too many parameters.
207. Congestion!
This may occur in access to the Central Back-up, simultaneous updates in the same unit, etc.
208. Unit unobtainable.
The unit indicated in the command cannot be reached.
This error message can be followed by:
REJECTED The completed action is rejected;
EXECUTED The action is accepted and written to the journal file, but not executed yet. As soon as
the unit is obtainable again, it will be updated from the journal file.
209. Illegal multiple value.
A parameter is entered as a series or range when this is not allowed.
210. Notice -.
Header when the system generates information to the user, which is not an error indication.
211. Input line discarded.
Used after Ctrl-X from an OM terminal.
212. Question mark at illegal position.
213. Unit currently locked.
214. Line too long.
215. Time out.
216. Illegal multiple value combination.
An example is a range command with the second value smaller than the first: 50&&10. This is not
allowed.
217. Too many parameter values.
218. Parameter value too long.
219. No colon at position 7 encountered.
220. Device error.
221. Error in overlay.
The overlay contains a checksum error and is therefore not a loadable set, or the package ID of
the overlay is not conform the package ID of the system.
222. Command aborted.
223. Illegal multiple command.
It is not allowed to execute the command as a multiple command.
224. Enter new value.
225. Non-convertible parameter.
226. Execution completed.
228. Open error.
229. END;
230. Message.
231. No guidance text available.
232. aborted : Log-file open error.
233. aborted : Log-file write error.
234. See Maintenance manual.
235. END OF DIALOGUE #
236. Error.
237. REJECTED.
238. EXECUTED.
239. Job

- 241 -
240. Unit
241. finished executing
242. Unit updating.
During execution of an OM command a unit is met which is not up to date. The result can be:
-Unit updating + EXECUTED
The command is accepted and written to the journal file. Execution is postponed because the
unit is updating.
-Unit updating +automatic retry
The command is not yet accepted and not written to the journal file. First a validation must be
done in the unit which is not up to date. Depending on this validation the command will be
rejected or journalled and executed.
243. First value in range bigger than second value.
244. Empty parameter value.
245. Press; to continue or CTRL X to abort guidance.
246. Comma or ampersand in parameter repair input.
247. Parameter value too short.
248. Backup update error.
249. Backup congestion.
250. Backup unobtainable.
251. Unit not installed.
A local data updating action is attempted in a unit which is not installed.
252. Backup maintenance currently locked.
All OM actions that are normally written to journal file are currently disabled. This situation is the
result of the execution of OM command BMLOCK. BMLOCK might be set because a MIS-file or a
Retrieve-file is to be made.
253. YES
A question will be put on the OM terminal screen if you have to confirm the continuation of a
certain action. You can only enter yes (complete the action) or no (abort the action).
254. Operational maintenance currently locked.
All OM actions that are normally written to journal file and executed from an OM device, are
currently disabled. OM actions initiated from an extension (e.g. when desksharing is executed)
remain possible and are written to the journal file. This situation is the result of the execution of
OM command OMLOCK. OMLOCK might be set to temporary disable all OM actions which
change PBX configuration data.

- 242 -
B. PARAMETERS
A
A-queue number (1 ... 16) 1 = A1 to 16 = A16 (general).

A-QUEUE
Routing to operator A-queue (1 ... 16).

ABS
Displayed value, indicating the number of operators absent.

ABS-POM
Displayed value, indicating the number of operators absent and in OM mode.

ABBR-NUMBER
Abbreviated number (1 ... 6 digits).

AC
Authorization code for Mercury smart box emulation (2 ... 20 digits).

ACC-REP
Access code repetition counter (0 ... 6).

ACCESS-LIST-ID
Access List ID number can range from 0 ... 65534 (one less than maximum value of boundary 446, which is
65535).

ACD-TIME-PERIOD
ACD timer (used for various purposes) :
0 = 0 seconds
1 = infinite
2 = 5 seconds
3 = 10 seconds
4 = 15 seconds
5 = 20 seconds
6 = 25 seconds
7 = 30 seconds
8 = 40 seconds
9 = 50 seconds
10 = 1 minute
11 = 2 minutes
12 = 5 minutes

ACD-THRESHOLD
ACD group dynamic COB threshold per 100 present and IN-SERVICE group members.
If the full and busy thresholds are to be defined as fixed values instead of depending on the number of
present and in service agents, the value entered in this parameter must be offset with 9900. Thus, a fixed
threshold value of T must be entered as 9900 + T. The maximum is 9997.
Example: if the fixed threshold is 20, the parameter value becomes 9920.

ACI/FLAG
Authority Class Index or in the case of a MIS file the validity flag: (v=valid, i=invalid).

- 243 -
ACTION
The server handling call processing, management and applications. The Active Server binds the Interface IP
address to the network adapter. The Interface IP address is the Application Interface for SIP@Net.

ACTION-INDICATOR
[P[Q[R]]]
P = IABD-IND:
Indicates if an inter unit move is continued when there is not enough space for the IABD numbers
belonging to the DNR in the destination unit.
0 = Abort execution when lack of space for IABD numbers in the destination unit (default)
1 = Continue execution in spite of lack of space for IABD numbers in the destination unit
When P is required to supply Q in case of assign or single unit system, P must be 0.
Q = ORDER-IND:
Indicated whether the BSP-ID must be inserted in the BSP list before or after any existing BSP with the same
value.
0 = BSP is inserted after any existing BSP with same BSPT value (default)
1 = BSP is inserted before any existing BSP with same BSPT value (use for desksharing)
R = VALIDATION-IND: Indicates the desksharing license validity
0 = Perform move without any license checks.
1 = Perform a DeskSharing license check. Abort execution when after move the BSP would become
unlicensed.

ACTIVE SERVER
Indication of the default Active Server (1 = Yes) or the default Standby Server (0 = No) in a Dual Server
configuration.

ADD-CNND-NAME
Add the "CNND name" to the outgoing SIP messages on the SIP-trunk route.
0 = Do not add the CNND name
1 = Add the CNND name

ADD-INFO-NBR-LENGTH
One or two digits in the range of 0 ... 20 indicating the number of additional info digits to be given. If the
parameter is omitted, it is assumed that no additional info digits have to be given.

ADD-OR-DELETE
Action parameter : 0 = delete, 1 = add.

ADD-RECEIVE-PHONE CONTEXT-AS-PREFIX
Used for the AudioCodes Mediant 1000. Specifies if the Phone-Context parameter in the From or To header
of a received INVITE message has to be used as prefix : 0 = no, 1 = yes.

AG
Analysis group (0 ... 254).

ALL-CALLS
Number of allowed calls in the bundle for a given BSPT (0 ... 254).

ALL-SIP
1 indicates that all Polycom SIP terminals have to be rebooted. Note that those terminals then obtain their
configuration files from the TFTP server.

ALLOWED
OM terminal is (not) allowed to execute commands of the assigned authority class : 0 = not allowed
(default), 1 = allowed.

- 244 -
ALTERNATIVE USERNAME
This parameter defines the “alternative username” related to the given circuit. It is mainly used in case of
desksharing. This “alternative username” is applied during the registration process. It may contain upper
and lower case characters and has to contain at least one non-numerical character. The length is limited to
18 characters. In case this parameter is left empty it is assumed that the DNR is applied as username during
the authentication process.

ANN-DDI-FAIL
Announcement DDI fail option :
0 = Call to busy party
1 = Dialling time out
2 = Call to a non-allocated number
3 = Other unsuccessful calls

ANN-NO
Announcement number (0 ... 254).

ANNOUNCEMENT-CODE
0 ... 255; In some messages TMS will send an equipment number (60 ... 79), indicating a tone source to
which the subscriber should be connected. This equipment number is defined in the appropriate TMS *.PDT
files.

ANNOUNCEMENT-SOURCE
0 or empty erases the relation
1 = Synchronous announcer specified by a DNR
2 = Tone announcer specified by a tone-function number
3 = Continuous announcer specified by an EHWA

ANN-PAUSE-TONE
Pause tone for ACD groups :
0 = COB tone
1 = Internal ring tone
2 = External ring tone
3 = MOH
4 = Music on COB
5 = Silence

ANN-SELECTION
Announcement selection on incoming trunks (0 ... 7) :
0 = DDI fail calls
1 = Successful DDI calls
2 = Non-DDI calls (including PLE, INE, MCNE, SCNE and CANS)
3 = Calls to operator A-queue
4 = Station calls for ACD group
5 = Night announcement for ACD group
6 = Delay message for ACD group
7 = Music on hold

APPLICATION
Application identification :
16 = CallManager keyboard
17 = CallManager display
20 = General OM keyboard 1
21 = General OM display 1

- 245 -
22 = General OM keyboard 2
23 = General OM display 2

APPL-ID
Identification of the type of application that uses the PFSM : 0 = PPH Protocol Tracer.

APPLICATION-IP-ADDRESS
The IP address (in digit format : aaa.bbb.ccc.ddd) that external applications use to connect to SIP@Net. If
the heartbeat protocol detects an error then the Server binds the Application IP address to the network
adapter.

APPLICATION-VERSION
1 or 2 in the case of the CallManager (default 1);
2 ... 9 in the case of general OM (default 2).

AREA (in Paging related OM commands)

Paging area number (0 ... 13).

AREA (in OM command DIMEUS)

Omitted = Summary of the memory areas
1 = Summary of users of the system memory area
2 = Depending on parameter User in command DIMEUS

AS-PCTS
Indication whether the circuits on boards should be assigned automatically or not : 0 = manual, 1 =
automatic.

ASS
B-channel assigned yes or no.

ASSIST-GROUP
Assistance Group (1 ... max), where max is equal to : boundary 452 (max. number of Assistance Groups) - 1

ASSIST-GROUP-PROPS
Assistance group properties in the format :
P = Operator monitoring (0 = off, 1 = on).
Q = When in night: go to general assistance group before (specific) MCNE (0 = off, 1 = on).
Q is optional; when Q is omitted, the default value (0 = off) is taken.
System defaults for the PQ properties are : 00.

ASSISTANCE-POINT
Indicates in which exchange operator assistance should be given (1 ... 12 digits). This can be :
- network DNR or Cluster identify of the own exchange (local assistance).
- network DNR or Cluster identity of another exchange (external assistance).
- nothing (Source assistance).

ATF
Automatic trunk find :
0 = No ATF
1 = ATF by camp on busy (COB)
2 = ATF by automatic ring back (ARB)

- 246 -
ATTRIBUTES
P[Q]
P = Name Visibility Attribute (only relevant for CDD) :
0 = Name is visible for CDD (default).
1 = Name is hidden for CDD (name is not shown while browsing the list of names with directory dialling).
Q = Preferred Name Attribute (only relevant for CNND) :
0 = Name will not be selected as preferred in case of CNND. The first name entered will become preferred :
when a second name is entered it can be set to preferred; if so the first name automatically becomes non-
preferred.
1 = Name will be selected as preferred in case of CNND.

AUTHENTICATION REALM
Some providers require a configurable Authentication Realm per route (1 ... 80 characters).

AUTHORITY
Authority class (0 ... 15). Authority classes have the following meaning :
0 = Display functions for the customer
1 = Change telephony functions by customer
2 = Change complex and data functions by customer
3 = File management
4 = Batch jobs
5 = Change of service conditions
6 = Maintenance level 1
7 = Maintenance level 2
8 = Maintenance level 3
9 = Second line maintenance tools
10 = Spare (user definable)
11 = Spare (user definable)
12 = Spare (user definable)
13 = Spare (user definable)
14 = Change session authority class and protection (always allowed)
15 = Subcommands (never allowed)

AUTHORITY-INDEX
Authority Class Index : numeric identification of an OM command.

AUTO
Automatic writing of system dump information to the local backup : see also parameters DUMP and WRITE-
SEL :
0 = Automatic writing disabled (default for DUMP = 2)
1 = Automatic writing enabled (default for DUMP = 0, 1 or 3)

AWAIT
At setting, await for the backup maintenance lock (BMLOCK) to be cleared.
0 = no waiting
1 = waiting

B-BUTTON
B button id (1 ... 4).

B-CHANNEL
Relative B-channel number within the circuit : only valid for ISDN.

- 247 -
BAUDRATE
Communication speed (in Bauds) which is used on the V.24 port :
8 = 1200
10 = 2400
12 = 4800
14 = 9600
17 = 19200
18 = 38400
20 = 57600

BCH-VALUE
Relative B-Channel (0 ... 31) (if DED-TYPE is 0 ... 2) or number of B-channels (if DED-TYPE is 3 ... 5).

BIT/BYTE
Indicating a bit (0) or a byte (1).

BOARD-FREE-MEMORY
The size of free memory on the board available for the PFSM application.

BOARD-TYPE
Board type : see Appendix C. BOARD AND PCT TYPES.

BOUNDARY-INDEX
The boundary to be modified.

BOUNDARY-VALUE
The new value of the boundary.

BR
Displayed parameter, indicating if the dialled destination is barred or not.

BRD
Board position in shelf (1 ... 29).

BRD-STYP
The sub type of the board. This is an arbitrary number given to a board, to distinguish between several
boards of the same type (0 ... 99).

BSP-ID
Basic Service Profile Identification. This parameter is used instead of parameter DNR. It consists of a DNR
and a BSPT, separated by a hyphen (-):

<DNR>[-<BSPT>]

The -<BSPT> may be omitted when there is only one BSPT present on the DNR.

BSPT
Basic Service Profile Type (0 ... 99).
BSPT 20 ... 93 are user definable : use OM command CRBSPT and CHBSPT.
Since SIP@Net 5.1 it is also possible to change BSPT 94 up to and including 98. This change is made because
new gateway products often use IBSC 2 (3.1 kHz Audio) and this is not included in the default voice BSPT 95
and 97.
Not all ISDN services (BSPTs) might be supported by the public exchange.
Note that on a route only one BSPT with priority 2 is allowed.

- 248 -
 BSPT IBSC PRIORITY DESCRIPTION
0 0 1 64 kBit/s unrestricted
1 1 1 Speech
2 2 1 3.1 kHz audio
3 3 1 3.1 kHz audio non-ISDN
4 4 1 7 kHz audio
5 5 1 Teletex
6 6 1 Telefax4
7 7 1 Mixed mode
8 8 1 Videotex
9 9 1 Slow scan television
10 10 1 Fernwirken
11 11 1 GrafikTelefon
12 12 1 Bildschirmtext
13 13 1 Bildtelefon Bild
14 14 1 SOPHO ISPBX speech
15 15 1 SOPHO ISPBX modem data
16 16 1 X.21
17 17 1 X.25
18 18 1 Bildtelefon Ton
19 19 1 64 kBit/s unrestricted non-ISDN
20 ... 93 User definable 2 Free for use (CRBSPT and CHBSPT)
0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16,
94 2 Data / possibly data
17, 19
95 1, 3, 4, 14, 18, 19 2 Voice / possibly voice
96 0, 2, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17 3 Data
97 1, 14, 18 3 Voice
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14,
98 4 Any (Default)
15, 16, 17, 18, 19
99 All BSPTs

BUDGET
Value to add to/subtract from the budget or the value to set the budget to. The range is 0 ... 999999.

BUDGET-ACTION
0 = subtract from the budget
1 = add to the budget
2 = set budget to amount

BUDGET-UNIT
Unit number where the budget is stored (1 ... 14).

BUNDLE
Bundle number (0 ... 254)

- 249 -
BUNDLE-DIR
Direction of a bundle:
0 = incoming
1 = outgoing
2 = bothway.

C
C call type:
0 = DDI-not answered
1 = DDI-unsuccessful
2 = Recall not on hook
3 = Recall on hook
4 = Series
5 = Taxmetering
6 = Through connection busy
7 = Preferred call
8 = Through connection ringing

CALL-ORIG-TYPE
Indicates for which call originator type the Call Forwarding / Follow-Me relation is valid :
0 = Call Forwarding / Follow-Me must be executed for both internal and external calls
(default if omitted)
1 = Call Forwarding / Follow-Me must be executed for internal calls only
2 = Call Forwarding / Follow-Me must be executed for external calls only

CALLED-PARTY-NP
Numbering Plan of the called party : see parameter NUMBERING-PLAN.

CALLING-LINE-ID
Calling Line ID (CLI) can be 20 digits.

C-BUSY
Displayed value, indicating the number of busy calls in the C-queue.

C-PRE
Displayed value, indicating the number of preferent calls in the C-queue.

C-RING
Displayed value, indicating the number of ringing calls in the C-queue.

C-SER
Displayed value, indicating the number of series calls in the C-queue.

C-TAX
Displayed value, indicating the number of taxmetering calls in the C-queue.

CC-TABLE-NR
Number of the CLI or COL translation table (0 ... 254).

CFDA-TIME
Call Forwarding on Don't Answer time in seconds (5 ... 254 sec).

- 250 -
CF-TYPE
Type of Call Forwarding :
0 = Call Forwarding on don't answer
1 = Call Forwarding on busy
2 = Call Forwarding on absent group member
3 = Call Forwarding on empty group
4 = Call Forwarding on group overflow
5 = Call Forwarding on group in night service
6 = Call Forwarding on not existing DNR
7 = Call Forwarding on out of order extension
8 = Call Forwarding on not reachable extension
9 = Call Forwarding on SMA no valid CLI
10 = Call Forwarding on SMA enquiry triggered
11 = Call Forwarding on don’t answer group
12 = Call Forwarding on busy group

CHARGED
0 = toll free
1 = charged (default)

CLI/COL-STRING
Digit string of 0 ... 16 digits indicating the CLI or COL.

CLI-TYPE
0 = External (default)
1 = Internal

CLI-ACCESS
0 = CLI-DENY
1 = CLI-PERMIT

CLUSTER-ID
The identity of the iS3000 system (cluster) for use with DPNSS (1 ... 6 digits, each 0 ... 9)

COB-QUEUE-TYPE
Length definition for the Camp On Busy queue. Three types :
0 = No COB queue
1 = Short COB queue
2 = Long COB queue

COCO-NUMBER
Controlled Connection Number : this is a unique number for each controlled connection for test purposes.
It must be in the range 1 ... 99.

CODEC
This can be 0 ... 3 :
0 = G.711 uLaw
1 = G.711 ALaw
2 = G.729A (is compatible with G.729)
3 = G.729AB (G.729A with silence suppression)

- 251 -
CODEC-LIST
A list of CODECs as defined in the ISG (1 ... 255). The CODEC specifies the which compression algorithm is
used. G.711 is not compressed, with G.729 compression the required bandwidth for VoIP can be reduced.
The supported CODECs are G.711 (payload sizes 30 or 40 ms) and G.729(A) (payload sizes 20, 30 and 40 ms).

CODEC-LIST G.711 payload size G.729 (A) payload size PREFERRED

1 40 - not appl.
2 30 - not appl.
3 - 20 not appl.
4 - 30 not appl.
5 - 40 not appl.
6 30 20 G.711
7 30 30 G.711
8 30 40 G.711
9 40 20 G.711
10 40 30 G.711
11 40 40 G.711
12 30 20 G.729
13 30 30 G.729
14 30 40 G.729
15 40 20 G.729
16 40 30 G.729
17 40 40 G.729

COMMAND-FILE
Command file specification consisting of :
[LDN:]FILE-NAME[.EXTENSION[.GENERATION]]
If GENERATION is omitted, the latest generation is used.
If EXTENSION is omitted, COM is used.
If FILE-NAME is omitted, SUBMIT is used.
If LDN is omitted, LBUxx is used, in which xx represents the unit number in which the job was submitted.

CON-ALLOWANCE
Connection allowance :
0 = Not possible
1 = Not allowed
2 = Allowed only with convertor
3 = Allowed

CON-AND-SIG-TYPE
Bundle connection and signalling type Y[Z]Z
Y represents the connection type :
0 = Four wire tie line
1 = Two wire PSTN line
2 = Two wire tie line
3 = Digital PSTN line
4 = Digital tie line
5 = Virtual connection

- 252 -
ZZ represents the signalling type:
INCOMING : OUTGOING :
0 = impulse impulse
1 = impulse/KT sensitive impulse
2 = keytone keytone
3 = MFC keytone
4 = keytone-CLI keytone-CLI
5 = keytone after answer keytone
6 = DPNSS-x DPNSS-x
7 = DPNSS-y DPNSS-y
8 = MFP MFP
9 = MF Socotel MF Socotel
10 = DASS DASS
11 = MFE MFE
13 = MFC-CSS1 MFC-CSS1
14 = ISDN-A ISDN-A
15 = ISDN-B ISDN-B
16 = DPNSS-PVN DPNSS-PVN
17 = DPNSS-x DPNSS-VM-x
18 = DPNSS-y DPNSS-VM-y
19 = virtual lines
20 = QSIG-A QSIG-A
21 = QSIG-B QSIG-B
22 = QSIG-PVN QSIG-PVN
23 = CCIS CCIS
24 = SIP SIP

CONDITION
Service condition :
0 = INS
1 = OUT
2 = OUT-ac
3 = ABL-er
4 = ABL-er-ac
5 = ABL-nu
6 = ABL-te
7 = ABL-te-ac
8 = ABL-deac
9 = ABL-fail
10 = ABL-hot
11 = NIN

CONNECTION-TYPE
If the BCS protocol is used (PROTOCOL-TYPE), this parameter determines whether modems are used or not :
0 = no, 1 = yes.

CONV-NUMBER
Converted DNR, indicating the result string after conversion.

CONVERTOR-TYPE
Convertor type (0 ... 254).

CRE-DATE/TIME
Creation date and time of a file.

- 253 -
CRT
Circuit number (0 ... 54).

CRUE-BRD
Board position of the clock entry.

CRUE-CRT
Circuit number of the clock entry.

CRUE-SHELF
Shelf number of the clock entry.

CUR
Current authority class value.

CV
Compatibility value (0 ... 254).

CYCLIC
Cyclic or once : 0 = cyclic, 1 = once.

DATA
The contents of the BIT/BYTE (0 ... 255).

DATA-INDICATOR
This indicator specifies the kind of data :
0 = Load in permission units
1 = Number of tasks running
2 = Guaranteed load in %
3 = Maximum load in %
4 = Minimum load in %
5 = Maximum number of tasks allowed
6 = Timeout value in minutes

DATA-IN-MEMORY
The amount of trace data present on the board which is not yet stored in output file.

DATE
Absolute date in the form YYYY-MM-DD or relative date in the form +dddd (number of days).

DAY
Day of the month (1 ... 31).

DAY/NIGHT
Day or Night indication for ACD groups : 0 = Night, 1 = Day

DAY-OF-WEEK
Day of week (1 ... 7). Normally Monday is day 1.

DAY-TRFC
Traffic class during day time (see TRFC).

DED-TYPE
Dedication type (0 ... 5) :
If DED-TYPE is 0 ... 2 (1TR6/Euro-ISDN) :

- 254 -
The dedication mode of a specific B-Channel :
0 = Set B-Channel dedication incoming
1 = Set B-Channel dedication outgoing
2 = Set B-Channel dedication bothway
IF DED-TYPE is 3 ... 5 (VN2) :
The maximum number of calls in the access:
3 = Set maximum number of incoming calls
4 = Set maximum number of outgoing calls
5 = Set maximum number of calls

DEF
Default authority class value.

DEFAULT-GROUP
Default group for the concerned member (0=no, 1=yes, empty=no)

DEFAULT-TARIFF
The number of SOPHO units the budget is decreased with, after the parameter "time-period" expires.
Possible values 1 ... 9.

DELAY
Delay mark : 0 = no, 1 = yes.

DELAYED-SEIZURE
Delayed seizure mark : 0 = no, 1 = yes.

DESCRIPTION
A description of the function of the file.

DEST
Number of the destination (0 ... 254).

DEST-CC-STRING
Translated CLI or COL string : max. 16 digits, the string may end in wildcards (%).

DEST/NUMBER
Number of the destination (0 ... 254), in Numbering scheme this can also be a paging route
(0 ... 254). In the case of PVN result-id's this can also be a unit number.

DEST-NUMBER
Destination number for Entry Point Local Exchange, Follow Me, Hot Line, Twinning and Call Forwarding
types 0 ... 5 (1 ... 20 digits) and 6 and up (1 ... 8 digits).

DEST-BRD
Board identification of destination : see BRD.

DEST-CRT
Circuit identification of destination : see CRT.

DEST-SHELF
Shelf identification of destination : see SHELF.

DESTINATION-FILE
Destination file specification ( LDN:[FILENAME[.EXTENSION[.GENERATION]]] ).

- 255 -
DESTINATION-MENU
Menu number (0 ... 65533, max number is defined by NEBOUND 96). This is the location where the source-
menu is copied to.

DFP-INDICATOR
Digit, frequency or pulsed indicator :
0 = digit
1 = frequency
2 = pulsed

DIALTONE-OPTIONS
P : first external dial tone given to the caller : 0 = no, 1 = yes.
Q : second external dial tone given to the caller : 0 = no, 1 = yes.

DIALTONE-PLACE
Place in the digit string (<MAX-LENGTH) where second dial tone is generated : 0 ... 19 (0 = no second
dialtone).

DIAL-TYPE
0 = Extension
1 = Enquiry
2 = Operator
3 = Post
4 = Alternative destination
5 = FM primary
6 = Pickup destination
7 = Executive secretary
8 = Overlay time out dialling
9 = Overlay continue dialling
10 = QSIG network party dialling (network destination dialling)
11 = Media dialling

DIGIT
The given digit will be used as fixed MSN digit when the MSN type of the EHWA to which the BSP is
assigned is 'MSN with fixed digit'.

DIGIT-ASSIST
Mode digit for assisted transit calls (1 keyed numeral)

DIGIT-EXT
Mode digit for external originated calls (1 keyed numeral)

DIGIT-INT
Mode digit for internal originated calls (1 keyed numeral)

DIGIT/FREQ
Depending on DF-INDICATOR: Digit (0 ... 15) or a frequency (0 ... 6).
The control frequency is 6.

DIGIT-POSITION
TMS digit position (1 ... 20). This indicates the place where TMS (SSM/SysManager) expects the service code
in a dialled string.

- 256 -
DIR-AND-NEG
Bundle direction and ISDN negotiation : P[Q]
P = Bundle direction : Q = ISDN negotiation rule :
0 = Incoming 0 = Any B-channel
1 = Outgoing 1 = Exclusive B-channel
2 = Bothway 2 = Preferred B-Channel

DIRECTORY
0 = Internal directory, containing names and numbers within the company (default).
1 = External directory, containing names and numbers outside the company.
2 = Route directory, containing the route name database.

DIRECTORY-TYPE
S = System directory layout (default)
U = User directory layout
D = Description directory layout

DISPLAY-MODE
0 = Continuously displayed (default)
1= Once displayed

DNR
Directory number (1 ... 10 digits). It is possible to use leading zero's (0) until a projectable digit is
encountered. System boundary NEBOUND 421 (max number of DNR digits) defines the maximum number
of digits of a DNR. Valid values are 6, 8 and 10. Other values are corrected as follows: 7 is changed to 8, 9 is
changed to 10, smaller than 6 or larger than 10 is changed to 6.

DNR/NUMBER
A digitstring consisting of 1 to 10 digits.
The digits must be elements out of the digitset 0 ... 9, *, #, A, B and C.
minimum length = 1 digit
maximum length = 10 for internal directory numbers

DOMAIN-NAME
The domain name that is to be applied for registration of extensions. The length of the domain name is
limited to 18 characters. The name may contain upper and lower case letters and digits (separators and
punctuations are not allowed).

DOWN-TRFC
Downgraded traffic class (see TRFC).

DS
Displayed parameter, indicating the destination of a call.

DT
Displayed parameter, indicating the dial tone place.

DT820-LICENSE
0 = No License (default)
1 = DT820 Gigabit License (for both the ITY-6D and ITY-8LDX models) (license 82)
2 = DT820 Ext Linekey 16 (ITY-8LDX only) (license 83)
3 = DT820 Ext Linekey 32 (ITY-8LDX only) (license 84)
4 = DT820 Gigabit License + DT820 Ext Linekey 16 (ITY-8LDX only) (license 82 & 83)
5 = DT820 Gigabit License + DT820 Ext Linekey 32 (ITY-8LDX only) (license 82 & 84)

- 257 -
DT820-REPORT
1 = Shows all EHWA with terminal license Giga, Giga/LK16 of Giga/LK32
2 = Shows all EHWA with terminal license LK16 of Giga/LK16
3 = Shows all EHWA with terminal license LK32 of Giga/LK32
4 = Shows all EHWA with terminal license Giga/LK16
5 = Shows all EHWA with terminal license Giga/LK32

DTU-BRD
Board location of the DTU.

DTU-SHELF
Number of the shelf in which the DTU is located.

DUMP
Cause of the system dump (0 ... 3):
0 = A frozen process
1 = An operational start due to a software exception
2 = An operational start due to a manual request
3 = A trigger to gather diagnostical data

DUMP-ACTION
System dump action (0 ... 2) :
0 = Reset dump trigger
1 = Create immediate dump
2 = Set off-hook trigger

DURATION
Threshold of call duration in seconds (max 4 digits).

EARLY-MEDIA
Early Media is active when this parameter is set to 1. Early media offers the possibility to redirect RTP-
streams in the ringing phase after Call Forwarding or transfer.

END-KEY
Indicates the function key where copying/clearing ends (0 ... 254) : the end-key is included in the copy/clear
operation.

ERRORS
Indication whether or not read or write errors had occurred.

EQUIPMENT-ID
Identification of the (boot-) software/hardware version of a board or a terminal.
0 = indicates the HW-type (default)
1 = indicates the Main Software
2 = indicates the Boot Software

EQUIPMENT-TYPE
Type of the device :
0 = Non OM keyboard (Lab usage)
1 = Non OM display (Lab usage)
4 = Disc not tested (obsolete)
5 = Toll ticketing
7 = Solid State Disk
11 = MIS Output CallManager
13 = Fixed alarming (CCS only)

- 258 -
14 = OM keyboard Nolog (no journalling)
15 = OM display Nolog (no journalling)
16 = OM keyboard CallManager
17 = OM display CallManager
20 = OM 1 keyboard
21 = OM 1 display
22 = OM 2 keyboard
23 = OM 2 display
24 = Printer
25 = FDCR (ASCII output)
26 = Disk Emulator
27 = Alarm signaller
28 = Alarm unit (CPU3000 only)
29 = SSM/SysManager services
32 = FDCR (binary output)
33 = FDCR over IP

Note that no journalling is done on 'devices' with equipment type 14/15 (OM keyboard/display Nolog) for
the following OM commands:
- ASFACM and ERFACM : only relevant for FCM 24 (Do Not Disturb).
- CHFKDA and CPFKDA.
Keep in mind that 'no journalling' may cause minor network function key data inconsistency for OM
commands CHFKDA and CPFKDA.

EXCLUSIVE
Exclusivity mark : 0=no, 1=yes.
The exclusivity mark is used when the access is used to a controlled connection. The system will not accept
or make calls to any B-channel in this access if the exclusivity mark is set.

EXEC-BSP-ID
Executive BSP-ID (see BSP-ID)

EXEC-RANK
Executive rank in pool (0 ... 9).

EXEC-LINE-POS
Indication if the executive line position must be assigned : 0=no, 1=yes.

EXEC/SECR-BSP-ID
Identifying BSP-ID for an executive/secretary group; BSP-ID of any executive or secretary in that group (see
BSP-ID).

EXP-NUMBER
Expanded number (1 ... 20 digits).

EXT-PROPS
Extended group properties [ABCDE[F[G[H[I[J[K[L]]]]]]]], each 0 =false or 1=true.
A = Line position status prevails extension status :
- if true, group members will notice a call, which arrives at a fellow group member's line position
even if this fellow group member's extension is busy.
- if false, then a call to a member's line position is only signalled when the member's extension is
idle.

- 259 -
B = No rerouting after transfer.
Trunk calls being transferred to a member in the same group and not answered within a specified
time, will not be rerouted to an operator, even if the route has 'assistance' activated.
C = Hold tone after transfer. This gives 'hold tone after transfer' to an incoming caller, which is
transferred by a group member to fellow group member, which is ringing.
D = LED based status monitoring. Status monitoring messages are related to LED codes.
E = Inhibit diversion of member-member calls.
A call from one group member to another in the same group, can not be diverted (like FM).
F = Inhibit operator assistance. This applies to ACD groups only : it inhibits a call to an ACD group from
getting operator assistance.
- for a routing group this is automatically set to 1.
- for all other types of groups, this option must be false.
G = Unrestricted call pick-up allowed.
This allows for individual call pick-up by extension users outside the group arrangement.
H = This applies to ACD groups only.
In case ACD-group info is requested via PVE then the SIP@Net value of the counters "Number of
Calls Handled (NCH)" and "Number of Lost Calls (NLC)" are sent via PVE. If the option is set to :
- 0 : then the counters return the gathered data since the creation of the ACD-group : this is
accumulated data.
- 1 : then the counters return the gathered data since the previous request : this is the current
minus the previous value (delta).

Option H = 0 Option H = 1
NCH NLC NCH NLC
Creation 0 0 0 0
Request 1 18 12 18 (=18-0) 12 (=12-0)
Request 2 18 12 0 (=18-18) 0 (=12-12)
Request 3 29 15 11 (=29-18) 3 (=15-12)
Request 4 31 16 2 (=31-29) 1 (=16-15)
Request 5 63 33 32 (=63-31) 17 (=33-16)
Meaning of option H

Note that after re-projecting of the system all values are set to "0".
For all other types of groups, this option must be false.
I = Busy indication when congestion on COB.
This applies to routing groups only : when this option is set to 1 and when a call is made to a
routing group, then the call will be cleared with clearing cause busy, when :
- the group is in day, and the COB queue is full.
- the group is in night, and it has a Call Forwarding When Night destination that is an extension
terminal, that has a full COB queue.
When a routing group is projected and this option is not entered, the value of this property is
equal to the system option LOSYSOP171.
J = Do not switch absent after expiry of forced absent timer (applies for ACD groups only).
K = Switch member absent/present when individual FM is activated/cancelled.
This feature is not available for "Empty Group not allowed" groups.
L = COB queue prior to CF on busy group (don’t care for ACD groups).

- 260 -
If the group is a routing group :
- properties A, B, C, D, E, G, H, J, K and L are not applicable : must be 0.
- property F must have the value 1.
- when the property “Busy indication when congestion on COB“ [I] is not entered, the value is equal to
the value of system option LOSYSOP171.

EXTENSION
Extension of a file, max 3 characters e.g. POM.

FACILITY
0 = Traffic class
1 = SAS facility class
2 = Least Cost Call Routing and iSNet Private Virtual Networking second list active
3 = Tariff Class Facility

FAC-ID
The required facility :
0 = Group member state.
1 = Executive/Secretary state.

FAC-INDICATOR
Password protected facility indicator :
0 = up/downgrading traffic class
1 = password DDO/desksharing
2 = IP Phone registration

FALL-BACK
Specifies if fall back to the original environment must be made.
0 = Don't fall back, activate the current environment.
1 = Fall back, activate the original environment.

FAR-DEST
Far destination unit (1 ... 14).

FCM
Facility class mark (RO = read only, D = possible default)

0 = add on entitled D
1 = IABD and LENR RO
2 = break in entitled D
3 = break in protected D
4 = data protected D
5 = data protected entitled D
6 = ELC barred D
7 = follow me entitled / call forwarding entitled D
8 = follow me protected D
9 = indialling barred D
10 = metering D
11 = preference to operator D
12 = Business telephone
13 = test call entitled D
14 = trunk priority allocation D
15 = long line D
16 = call forwarding on don't answer or on absent group member RO

- 261 -
17 = hot line RO
18 = delayed hot line RO
19 = group member RO
20 = call pick-up individual RO
21 = executive RO
22 = secretary RO
23 = special extension RO
24 = don't disturb D
25 = don't disturb entitled D
26 = toll ticketing D
27 = status display member RO
28 = external service display D
29 = auto COB on originator D
30 = auto COB on destination D
31 = X.21 DTE D
32 = keytone post dialling allowed (to be set on the destination !) D
33 = voice mail server D
34 = call waiting entitled D
35 = call waiting protected D
36 = start COB entitled D
37 = CF on busy extension or on empty group RO
38 = direct access protected D
39 = fixed follow me entitled RO
40 = TRANSCOM DTE D
41 = line position available RO
42 = park position available RO
43 = executive line position entitled RO
44 = enquiry by impulse digit D
45 = selective call answering RO
46 = CLI permanently restricted D
47 = overrule CLIR D
48 = ARB entitled D
49 = ARB protected D
50 = B-channel overflow D
51 = COL permanently restricted D
52 = message waiting on ALC D
53 = collect call reception entitled D
54 = CF on not reachable extension or on busy group RO
55 = time-break enabled D
56 = B-channel bundling allowed D
57 = desksharing entitled D
58 = keytone dialling D
59 = enquiry by keytone digit D
60 = enquiry by keytone digit full D
61 = network priority/force release D
62 = enquiry by keytone entitled D
63 = multi-line entitled D
64 = conference supervisor RO
65 = CLIP on analogue terminal ETSI D
66 = desksharing protected D
67 = intercom call entitled D
68 = intercom call allowed D
69 = cost of call on assisted user D
70 = iSNet MAN DECT mobility entitled D

- 262 -
 71 = iSNet WAN DECT mobility entitled D
72 = extension features applied to group calls D
73 = listen in call entitled D
74 = CLIP on analogue terminal Danish D
75 = Change SMA relation entitled D
76 = CLIP on analogue terminal with FSK D
77 = SMS allowed D
78 = SIP video protected D
79 = Diversion Bypass Entitled D
80 = Display hold party CLI on analogue terminal D
81 = Pickup in conversation allowed D
82 = CSTA monitored RO
83 = Ignore PI in-band information (related to SIP terminals) D
84 = Automatic Answer (related to SIP and ErgoLine terminals) D
85 = Unrestricted call pickup individual allowed (independent of group arrangement) D
86 = Non Peer-to-Peer media D
87 = Voice recording D
88 = auto don't disturb overrule D
89 = BCT user functionality D
90 = Gateway Extension D
91 = Gateway Extension Registered RO
92 = CF on don't answer group RO
93 = COB queue protection RO

FDCR-CALL-TYPE
The type of call for Full Detailed Call Recording :
1 = Internal calls
2 = Outgoing calls
3 = Incoming calls
4 = Tie-line calls
5 = Assistance calls
6 = Paging calls
7 = Toll Ticketing calls
8 = Accounting iSNet (DPNSS) transit calls
9 = Filter accounting CCIS/iSNet (DPNSS) internal calls

FDNR
Free Number : a digit string consisting of 1 to 6 digits (determined by boundary 307). The digits must be
elements out of the digit set 0 ... 9, *, #, A, B, C. The parameter can be a complete DNR or the first digits of
a range of DNRs.

FIGURE-TYPE
Indication of the traffic measurement figures that are required :
0 = last quarter hour figures
1 = cumulative figures

FILE
File specification consisting of :
LDN:FILE-NAME.EXTENSION[.GENERATION]

FILE-NAME
File name (1 ... 6 alphanumeric characters)

- 263 -
FM-TYPE
Type of Follow-me :
0 = follow-me
1 = fixed follow-me

FN-LOC
Free Number Network Location : a digit string consisting of 1 to 6 digits (determined by boundary 307).
The digits must be elements out of the digit set 0 ... 9, *, #, A, B, C.
The parameter can be a complete DNR or the first digits of a range of DNRs.
This parameter can be either a DPNSS Cluster ID or a Network Access Code (other signalling).
In case of <FN-LOC-1> it indicates the existing location and of <FN-LOC-2> indicates the new
location.

FORMAT INDICATOR
0 = OM display
1 = SysManager

FREQ-VALUE
Stc-tone data (0 ... 33) : see Table B-9 Stc-Tone Data for PMC.

GEN
Maximum number of generations present on a device.

GEN-OPTS
General route options PQRSTUVWXYZ[A[B[C[D[E]]]]] (0 = no, 1 = yes)
P = data protection applied
Q = assistance required
R = add on allowed
S = toll ticketing on route
T = impulse postdialling allowed
U = keytone postdialling allowed
V = enquiry on trunk allowed
W = Flexible operator assistance available
X = Time-break check
Y = Time-break enabled
Z = CNND name/number translation required
A = Network priority/force release
B = Line park allowed
C = QSIG segmenting allowed
D = Closed number scheme presentation
E = Disable CCBS (ISDN routes only)

GEN-TONE
General tone types PQRSTU
P = Tone type before answer (2 ... 5)
Q = Tone type after answer (2 ... 5)
R = Tone during hold conditions (0 ... 3)
S = Tone type for COB before answer (0 ... 6)
T = Tone type for COB after answer (0 ... 6)
U = Tone for special recall to operator (0 ... 5)
The possible tone types are :
0 = Music on hold / no tone

- 264 -
1 = Music on hold / waiting tone
2 = No tone
3 = Waiting tone (the COB-tone to caller, nbr 17 Table B-8 Description of Tone, Ring and Ticker Functions.)
4 = Internal ring back tone
5 = External ring back tone
6 = Busy tone

GENERATION
Generation of a file (/ = latest, 0 (zero) = oldest, or 1 ... 9)

GROUP-DISPLAY
Group display. Flashing light on all member extensions when a member is called : 0 = no, 1 = yes.

GROUP-DNR
Group directory number : see DNR.

GROUP-BSP-ID
Group basic service profile identity.

GROUP-PROPS

OBSER- CALL CALL EMPTY

ROUTING GROUP HUNTING AUTO GROUP
VATION ACD PICKUP PICKUP GROUP
GROUP HUNTING SEQUENCE COB PROPERTY
GROUP GROUP MEMBER ALLOWED
No No No No --- No --- No --- 0
Yes --- 8
Yes Yes No --- 1
Yes --- 9
Yes Cyclic No --- No No 17
Yes 3
Yes No 23
Yes 11
Yes Yes No No 19
Yes 5
Yes No 25
Yes 13
No No No 21
Yes 7
Yes No 27
Yes 15
Fixed No --- No No 16
Yes 2
Yes No 22
Yes 10
Yes Yes No No 18
Yes 4
Yes No 24
Yes 12
No No No 20
Yes 6

- 265 -
 OBSER- CALL CALL EMPTY
ROUTING GROUP HUNTING AUTO GROUP
VATION ACD PICKUP PICKUP GROUP
GROUP HUNTING SEQUENCE COB PROPERTY
GROUP GROUP MEMBER ALLOWED
Yes No 26
Yes 14
Multiple No --- No No 49
Ring Yes 52
Yes No 55
Yes 58
Yes Yes No No 48
Yes 51
Yes No 54
Yes 57
No No No 47
Yes 50
Yes No 53
Yes 56
No No Yes Yes Cyclic No --- No Yes 30
Yes Yes 39
Yes Yes No Yes 32
Yes Yes 41
No No Yes 34
Yes Yes 43
Fixed No --- No Yes 29
Yes Yes 38
Yes Yes No Yes 31
Yes Yes 40
No No Yes 33
Yes Yes 42
Longest No --- No Yes 35
Idle Yes Yes 44
Yes Yes No Yes 36
Yes Yes 45
No No Yes 37
Yes Yes 46
Yes No No --- No --- No --- 28
Yes No Yes --- --- No --- Yes Yes 59

Group Property 60 (see below) has to be used in case of a conference group.

OBSER- CALL CALL EMPTY

CONFERENCE ROUTING GROUP HUNTING AUTO GROUP
VATION ACD PICKUP PICKUP GROUP
GROUP GROUP HUNTING SEQUENCE COB PROPERTY
GROUP GROUP MEMBER ALLOWED
Yes No No No Yes Fixed No --- No No 60

GUARDING-TIME

- 266 -
Guarding time in minutes (5 ... 99).
The value specifies the time, before the system falls back to the original environment automatically, in case
a system upgrade has been performed in maintenance mode.

GUARD-1+GUARD-2
Data guard time in minutes (000 ... 255) and incoming call guard time in seconds (000 ... 255) in the form:
mmmsss.
Remember to fill in exactly 6 digits for this parameter.
In the case of X.21: Clock adaption buffer size (12 ... 240).

HOTSTART
0=No hot start, 1=Hot start.

HOURS
Hours (0 ... 23).

HW-TYPE
Hardware type : refer to appendix C. BOARD AND PCT TYPES.

IABD-NO
Sequence Number for Individual Abbreviated Dialling.

IBSC
Internal Basic Service Category (0 ... 19). Same as BSPT 0 ... 19.

IDENT-NUMBER
Identification number of trunk line (0 ... 3000).

IDENTITY-HEADER
Specifies what identity header is used for the SIP trunk in the INVITE and 200 OK. These identity headers
are used to encode and decode the calling and connected name/number information :
0 = No separate identity header
1 = P-Asserted-Identity header (in INVITE and RESPONSE)
2 = P-Preferred-Identity header (in INVITE and RESPONSE)
3 = P-Asserted-Identity header (in INVITE, RESPONSE and UPDATE)
4 = P-Preferred-Identity header (in INVITE, RESPONSE and UPDATE)

INC-OPTS
Incoming traffic options PQRSTUV[WXYZ] (0 = No, 1 = Yes)
P = DDI traffic on route : if 'P=No' then WXYZ are omitted.
Q = Break-in protection
R = Transit allowed
S = Malicious call trace
T = Announcement allowed
U = Answer before announcement
V = Calling party control of incoming trunk call
W = DDI-delay time required
X = DDI barred check on inc. calls
Y = DDI call waiting required
Z = Socotel shortened protocol

INC-OR-COM

- 267 -
Indication if the network has to be set compatible or incompatible :
0 = compatible
1 = incompatible

INITIAL-TARIFF
The number of SOPHO units needed for call setup : possible values 0 ... 9.

INSIDE-GLOBAL-IP-ADDR
The NAT IP address that is to be applied. In case it is left empty no NAT is applied.

INSIDE-GLOBAL-IP-PORT
The NAT IP port that is to be applied. In case it is left empty the internal port number will be applied.

INTERFACE-IP-ADDRESS
The Interface IP address (in digit format : aaa.bbb.ccc.ddd) is configured with the IP address that
applications use to connect to SIP@Net. The interface is also called Application Interface.

INTERNAL-CALL-TYPE/A-QUEUE-NUMBER
Internal Call types:
0 = Individual call
1 = Normal call
2 = Preferred call
A-queue number : see parameter A-QUEUE.

INTERVAL
Duration (1 ... 255 seconds) of the pause in an external number. The place of the pause is defined by
parameter PAUSE-PLACE.

INTR-ALL
Intrusion allowance for toll (public exchange) operator (0 ... 1).
0 = not allowed
1 = allowed

IP-ADDRESS
IP address in format
- IPv4 : a.b.c.d
- IPv6 : a:b:c:d:e:f:g:h

IP-ADDRESS-TFTP-SERVER
IP address of the TFTP server from which the DT700 obtains its firmware package.
Note that the DT700 terminal range does not support IPv6 yet.
IP address in format
- IPv4 : a.b.c.d
- IPv6 : a:b:c:d:e:f:g:h

IP-APPLICATION
Indicates IP application :
0 = FTP (not valid for OM command DIIPSE)
1 = OM
2 = CSTA
3 = iPVN
4 = PVE / BCT sync
5 = TMS
6 = ALRM
7 = FDCR

- 268 -
8 = iTMP
9 = CCIS
10 = SIP
11 = SIC
12 = others

IP-PROJ-DATA-TYPE
0 = Media Access Code
1 = Language
2 = Gatekeeper
3 = VoIP data
4 = CODEC
5 = Payload
6 = RFC2833
7 = SRTP
8 = FAX
9 = Route Table Media Server
10 = Session Guarding Timer
11 = Disable Progress Tones

IP-PROJ-DATA-VALUE
Number is the Media Access Code of maximum 6 digits
Language can be 0 ... 19
IP address of the Gatekeeper
VoIP data and QOS
CODEC can be :
0 = G.711 uLaw
1 = G.711 ALaw
2 = G.729A
3 = G.729AB
Payload can be 10, 20, 30 or 40 msecs.
RFC2833 indicates whether RFC2833 is used (1) or not (0)
SRTP indicates whether SRTP is used (1) or not (0)
FAX indicates how fax transmission is done G.711 (0), T.38 (1), FAX disabled (2)
Route Table indicates the Route Table to the Media Server
Session Guarding Timer indicates the session guarding timer value in seconds (90 ... 3600 sec). A value of 0
means no session guarding active.
Disable Progress Tones indicates whether SIP Response message (1) is given instead of Progress Tones (0).

IP-REPORT-TYPE
Type of report
1 = Show IP address information.
2 = Show status/username.

IP-SIG-GROUP
IP Signalling group (0100 ... 01FE hexadecimal) for IP enabling.
IP Signalling group (B000 ... B0FE hexadecimal) for SIP trunks/extensions.

ITEM-NBR
The item number (0 ... 255).

IU-ROUTE
Inter Unit route (0 ... 254).

- 269 -
JOB
Number of the batch job (01 ... 99).

KEY
Function key number (0 ... 254) :
Level 0 : 0 ... 25, 100 ... 127 Real function keys
Level 1 : 0 ... 37, 100 ... 127 Real function keys
Level 0 : 26 ... 99, 128 ... 254 Virtual function keys
Level 1 : 38 ... 99, 128 ... 254 Virtual function keys
See the Customer Engineer Manual of the relevant SOPHO-SET / ErgoLine terminals.

KEY-DATA
Information to be stored under the function key or facility codes to be stored under virtual keys (max. 17
digits, max. 4 digits for soft-keys).

KEY-LEVEL
Function key level (0 or 1)

LAMP-ID
Operator Service LEDs :
1 = A1 LED
2 = A2 LED
3 = A3 LED
4 = A4 LED
5 = M1 LED
6 = M2 LED
7 = U2 / A5 LED
8 = U3 / A6 LED
9 = U4 / A7 LED

LDI-SELECTOR
This parameter is used to specify whether or not a LOCAL-DOMAIN-ID has to be selected to compose the
CLI/COL :
0 = LOCAL-DOMAIN-ID of trunk route is used.
1 = LOCAL-DOMAIN-ID of calling party / connected party is used.
empty = LOCAL-DOMAIN-ID is determined by parameter LOCAL-DOMAIN-ID.

LDN
Logical device name (1 ... 6 characters) : normally the following conventions are used (xx = unit number) :
- ACDxxy for the CallManager MIS
- ALUNxx for alarm unit device
- ALRMxx for alarm signaler
- CBU for the central backup
- DSKxx for disk emulator (in combination with OM command ZIPFIL, see SysManager 410 manual)
- DBU for the dual mode backup
- FDxx for SSM/SysManager FDCR device
- FXALxx for fixed alarm
- GBU for the general backup (CPU3000 only and if present)
- LBUxx for the logical backup device
- PCxx for the personal computer with the disk emulator software
- RBUxx for the remote backup device
- PRTRxx for the printer
- REMALM for remote alarming device
- TMSxx for the TMS (SSM/SysManager)

- 270 -
- TTxx for SSM/SysManager toll ticketing device
- VDUxxy for the OM terminal : y = 0 for keyboard : y = 1 for display.

LEASE-TIME
This value specifies the proposed lease time for registration in minutes, ranging from 1 ... 9999. After half
the value, SIP@Net will refresh it's lease.

- 271 -
LED-CODE
Code of the indication light (0 ... 31) or a function code (32 ... 255).
0 = LED off
1 = Follow-me
2 = Automatic Ring Back
3 = Call waiting
4 = spare 0
5 = Do Not Disturb
6 = Night presence
7 = Exec/secr presence
8 = Group presence
9 = Group member rank 0
10 = Group member rank 1
11 = Group member rank 2
12 = Group member rank 3
13 = Group member rank 4
14 = Group member rank 5
15 = Group member rank 6
16 = Group member rank 7
17 = Group member rank 8
18 = Group member rank 9
19 = Group member rank 10
20 = Group member rank 11
21 = Group member rank 12
22 = Group member rank 13
23 = Group member rank 14
24 = Group member rank 15
25 = Group member rank 16
26 = Group member rank 17
27 = Group member rank 18
28 = Group member rank 19
29 = Group member rank 20
30 = Group member rank 21
31 = Group member rank 22

For function codes (32 ... 255) see the Customer Engineer Manual of the relevant SOPHO-SET and ErgoLine
terminals.

LEVEL-VALUE
Stc-level data (0 ... 29) : see Table B-10 Coded Tone Levels for PMC.

LICENSE-NUMBER
1 = BSP
2 = IMP
3 = ACD agent
5 = DPNSS TRUNK
6 = Cost Accounting
7 = System Management
8 = FDCR
9 = LCCR
10 = Voice Mail
11 = iSNet PVN
12 = Extension (Integrated) Password Dialling
13 = MOH from IAS

- 272 -
14 = Dynamic Delay Messages
15 = Operator Monitoring
17 = iSLink CSTA ISDN
18 = CSTA monitor
19 = ExtensionDesk Sharing
20 = CNND
21 = iSLink CSTA Ethernet
22 = Installation DNR-EHWA
23 = CSTA I/O Services
24 = CSTA I/O Registrations
25 = Free Numbering
26 = ICDD
27 = CCBS
28 = ECDD
29 = iPVN
30 = Project Application 1
31 = Multi-Line for ErgoLine D340
32 = Multi-Line for ErgoLine D340 and D330
33 = Multi-Line for ErgoLine D340, D330 and D325
34 = CSTA PBC application
35 = CSTA EP application
36 = CSTA EXTERN application
37 = CSTA EXTERN seat
38 = CSTA CC210 application
39 = CSTA CC210 seat
40 = CSTA PBC seat
41 = CSTA DMS application
42 = CSTA DMS seat
45 = CSTA 3rd party TAPI application
46 = CSTA 3rd party TAPI seat
47 = CSTA EP seat
48 = Voice Logging
49 = CSTA voice log application
50 = CSTA voice log seat
51 = CSTA CTI server application
52 = CSTA CTI server seat
56 = Business ConneCT Synchronization
57 = QSIG Supplementary Service
58 = QSIG iSNet
59 = ISG channels
60 = CSTA Messenger application
61 = CSTA Messenger seat
62 = CSTA CC200 application
63 = CSTA CC200 seat
64 = CSTA Desktop application
65 = CSTA Desktop eat
66 = Software SMA user
67 = CCIS TRUNK
68 = iTMP DECT
69 = SIP Extensions
70 = SIP Trunk Supplementary Services
71 = SIP Server
72 = SIP Server on ISS/ISS-2/ISS-3
73 = Start Upgrade Period

- 273 -
 74 = Non-NEC SIP trunk
75 = SIP trunk channels
76 = SIP Server Availability (formerly Dual Server)
77 = SIP Server Slaves
78 = SWA Upgrade Allowance
79 = Native SIP Server
81 = Gateway Extension
82 = DT820 Gigabit
83 = DT820 Ext Linekey 16
84 = DT820 Ext Linekey 32

LIC-REPORT
Specifies whether the active licenses or the licenses as available in the file LICSuu.LIC (where uu = unit
number) are to be displayed :
0 = active licenses
1 = inactive licenses (from file)

LINE
Line number displayed on the operators console (1 ... 4 decimals).

LINES-PER-PAGE
Number of lines per page (10 ... 99).

LINE-POS
Indicates if a line position must be assigned to a group member : 0=no, 1=yes.

LINK-TYPE
Type of link to be assigned or displayed :
2 = SM-PM controllable
3 = SM-PM not controllable
4 = SM-RPM controllable
5 = SM-RPM not controllable
6 = SM-IU controllable
7 = SM-IU not controllable
10 = PMC-PMC
11 = CSN-PMC

LOCAL-DOMAIN-ID
The maximum number of local domain identifiers (specified by NEBOUND 374).

LOCAL-OPERATOR-MARK
Indicates whether first assistance by local operator(s) must be tried before assistance according to
assistance point will be attempted (0=no, do not try local operator first, 1=yes, try local operator first)

LOCATION-ID
LOCATION-ID : value 10000000 .. 99999999
Location-ID consists of 8 digits numeric value representing the location.

LOCATION-LOOKUP
This parameter defines whether Location Lookup is applicable for the external number specified using OM
command ASEXTN :
- 0 = no Location Lookup
- 1 = Location Lookup

LOG-FILE

- 274 -
File specification consisting of:
[LDN:]FILE-NAME[.EXTENSION[.GENERATION]]
If GENERATION is omitted, the latest generation is used.
If EXTENSION is omitted, LOG is used.
If FILE-NAME is omitted, the name of the COMMAND-FILE is used.
If LDN is omitted, the LDN of the COMMAND-FILE is used.

LOST-MESSAGES
The number of messages lost during trace due to congestion.

M
Internal call type
0 = individual
1 = normal
2 = preferred

M-IND
Displayed value, indicating the number of calls in the M-queue.

M/S
Main/Sub identification (0=main, 1=sub); identifies whether the protocol behaviour for a specified route
will be main or sub.

MAC-ADDRESS
Unique Ethernet identification, format: 12 hexadecimals. All equipment with an Ethernet-connection has
such a unique address. An example of a MAC address is "08003e888911".

MANAGER-INDEX
Index number of the requested manager type.

MANAGER-TYPE
Type of manager : 0 = unit boundary, 1 = option, 2 = timer

MARK
Hooter presence mark : 0 = not present, 1 = present

MASTER-SERVER
SIP@Net Server in a Server Cluster configuration can be the Master (1) or Slave Server (0).

MAX
Maximum paging length (MIN ... 20).

MAX-FILE-SIZE
Maximum allowed file size. The following maximum file size can be chosen :
0 : file may be expanded until upper threshold of disk space is reached
1 : 10 Kbytes
2 : 100 Kbytes
3 : 720 Kbytes
4 : 1440 Kbytes
5: 8 Mbytes

MAX-LENGTH
Maximum number length (1 ... 20). Must be > or equal MIN-LENGTH.

- 275 -
MAXIMUM-VERSION
Version that is supported by the equipment-type.

MD-TYPE
Type indication of the offered set of mode digits : 0 = prefix mode, 1 = suffix mode.

MEMBER-BSP-ID
BSP-ID of group member : see BSP-ID.

MEMBER-RANK
Rank of the member within a group.

MENU
Menu number (0 ... 65533, max number is defined by NEBOUND 96)

MET-TYPE
Metering type :
0 = Metering count of DNRs or BSP-IDs
1 = Metering count of night extensions
2 = Metering count of routes

MFC-ADD-INDEX
Additional requested MFC index, indicating :
- Priority of the received signal II, on MFC-TYPE =3;
- Previously sent signal II, on MFC-TYPE =5;
- No meaning on other MFC-TYPES.

MFC-INDEX
The requested MFC index (0 ... 20) : see Table B-1 Relation between MFC-TYPE and MFC-INDEX.

MFC-TYPE
Selected MFC structure (0 ... 5) : see Table B-1 Relation between MFC-TYPE and MFC-INDEX.

MFC-TYPE MFC-INDEX
0 Forward group I Forward signal (0 ... 15)
1 Forward group II Forward signal (0 ... 15)
2 Backward group A Call progress index (0 ... 12 & 19 ... 20)
3 Backward group B Call progress index (1 ... 10 & 13 ... 18)
4 Termination group A Backward signal index (0 ... 15)
5 Termination group B Backward signal index (0 ... 15)

Table B-1 Relation between MFC-TYPE and MFC-INDEX

Relation between MFC-TYPE and MFC-INDEX
The call progress numbers have the following meaning :
0 = Request next digit
1 = Call successful
2 = Extension busy
3 = Time out
4 = DDO successful
5 = Not exist. number

- 276 -
6 = DDI barred
7 = Call not allowed
8 = Congestion
9 = Number unobtainable
10 = Don't disturb
11 = Auto. answer dialled
12 = Auto. answer reply
13 = Busy - call type 1
14 = Busy - call type 2
15 = Busy - call type 3
16 = Busy - call type 4
17 = Busy - call type 5
18 = Busy - call type 6
19 = Request first digit of CLI
20 = Request next digit of CLI

MIN
Minimum paging length (1 ... 6).

MIN-LENGTH
Minimum number length (1 ... 20).

MINIMUM-VERSION
Version that is supported by the equipment-type.

MINUTES
Minutes (0 ... 59).

MISCELLANEOUS
A string consisting of 12 characters: ABCDEFGHIJKL
In case of X.21, only options B (=0), D (=0/1), E (=0/1), F (=7) and G (=2) are used, set all other options to 0.
A : Echo during keyboard dialing ? 0 = no, 1 = yes
B : Transmit unknown subscriber address ? 0 = no, 1 = yes
In the case of DTE's: 0 = subaddressing, 1 = no subaddressing
C : Convert to upper case ? 0 = no, 1 = yes
D : Hot line ? 0 = no, 1 = yes
In the case of X.21: 0 = switched, 1 = leased
E : Byte oriented protocol ? 0 = no, 1 = yes
F : Wordlength 5, 6, 7 or 8 bits
G : Parity 0 = no parity, 1 = even parity, 2 = odd parity
H : Stopbits 0 = 1 stop bit, 1 = 1.5 stop bit, 2 = 2 stop bits
I : Break sequence initiates call clear 0 = disable or 1 = enable
J : Rate adaption options 0 = no options
1 = flow control end-to-end for asynchronous, or
network independent clock for synchronous
K : Terminal adaption function 0 = X.30 TA, 1 = V.110 TA
L : Rate adaption method 0 = DRA, 1 = V.110 / X.30 / ECMA-102

MOD-DATE/TIME
Modification date and time of a file.

MODE
Display mode : 0 = Abstract (default), 1 = Full display.

MODULE

- 277 -
This parameter indicates a PM module (0 ... 31).

MONITOR-INTERVAL
The time between measurements in minutes (1 ... 100).

MONTH
Month (1 ... 12).

MSN-TYPE
Type of Multi Subscriber Number :
0 = No MSN
1 = MSN
2 = Fixed MSN digit

NAME
Name string belonging to a DNR (1 ... 20 characters). Enter the last name first.

NAME/SIN
Command name or in the case of a MIS file the Snapshot
Identification Number (SIN): LOCAL or Nxxxxx (xxxxx = ident number).

NARD
Protection level in the format New, Append, Read, Delete (4 digits of 0 ... 7).

NBR-OF-ITEMS
The number of items in a tone function (0 ... 255).

NE-LEVEL
Night extension level :
0 = INE
1 = SCNE
2 = MCNE
3 = CANS

NE-UNIT
Unit in which the night extension is present (1 ... 14).

NEAR-DEST
Near destination unit, unit directly connected to own unit (1 ... 14).

NETWORK-SIN
Network Snapshot Identification Number, 6 characters, the first character is "N", the following 5 are
decimal digits.
In the Dual Server configuration this parameter indicates the signature : a random number in the range
N00001 .... N99999.

NEW-DIGIT-STRING
The length of a new digit string is maximum 20 digits. Wildcards are indicated with '%' at the end of the
string. The last '%' means 'one digit or more'.
The number of '%' characters in the NEW-DIGIT-STRING may not be more than those in the ORIG-DIGIT-
STRING.

NEW-NUMB-PLAN
The new numbering plan can be :
0 = Unknown

- 278 -
1 = E.164
2 = Private Numbering Plan (PNP)

NEW-PACK
See parameter PACK.

NEW-TON
The New Type Of Number (TON) may have one of the following values :
0 = Unknown
1 = Subscriber (E.164) / Local (PNP)
2 = National (E.164) / Level 1 regional (PNP)
3 = International (E.164) / Level 2 regional (PNP)

NIGHT-TRFC
Night traffic class : see TRFC.

NL
Displayed parameter, indicating the number length.

NODE-ID
The identification of the Node.

NO-MSN-DIGITS
Number of MSN digits (0 ... 10).

PREFIX-LENGTH :
For IPV4: value 8, 12 .. 32 with stepsize 4
For IPV6: value 64, 68 .. 128 with stepsize 4
The default prefix-length is 32 for IPV4 and 128 for IPV6.

NUMBER
Digit string of 1 ... 16 keyed numerals.
The number of digits depends on the command. It is generally not more than 6 but in case of an external
number up to 16 digits are allowed.
Allowed: 0 ... 9, *, #, A ... C.

NUMBER-LENGTH/CV/POINT-CODE
In OM commands ASBLCK and ASINTN : length of internal number or code (1 ... 6).
In command ASINTN the following exceptions to this rule exist:
- In combination with result-ID 43 maximum 12 digits.
- In combination with result-IDs 48 and 49: CV is an optional parameter. When the CV is omitted in the
command, the existing relation (if present) is deleted.
- In combination with result-ID 82 the maximum length of this parameter is 0 ... 20 digits - length of given
NUMBER.
- In combination with result-ID 104 ... 110, 113 ... 115 this parameter indicates the length of the password:
6 ... 12 digits.
- In combination with result-ID 111 and 112 this parameter indicates the length of the password: 1 ... 16
digits.
- In combination with result-ID 118, 119 maximum 2 digits.
- In combination with result-ID 133, this represents the PVN-MODE:
- 0 = PVN Standard Mode (default),
- 1 = PVN Modem Mode,
- 2 = PVN Compressed Mode.
- In combination with result-ID 135, 136 maximum 1 digit.

- 279 -
NUMBERING-PLAN
0 = Unknown
1 = E.164
2 = Private Numbering Plan (PNP)

NVCT
Number of virtual circuits (0 ... 30).

OBJ-INDEX
See table below.

PM-OBJECT OBJ-INDEX
0 Signalling group data SIG-GROUP : see appendix C. BOARD AND PCT TYPES for a subset of the
signalling data or the Signalling Data Manual for the complete set.
1 Slave data 6 ATC data
8 Stc-tone data : see Table B-9 Stc-Tone Data for PMC.
9 Stc-level data : see Table B-10 Coded Tone Levels for PMC .
2 PSC tone data Tone-function (0 ... 99)
For Tone-function : see Table B-8 Description of Tone, Ring and Ticker
Functions.
For Tone-Source : see Table B-11 PSC Tone Source Numbers.
3 Ring data Tone-function (100 ... 199)
For Tone-function : see Table B-8 Description of Tone, Ring and Ticker
Functions.
For Tone-Source of the PSC : see Table B-11 PSC Tone Source Numbers.
For Tone-Source of the PMC : see Table B-12 PMC Tone Source numbers.
4 Ticker data Tone-function (200 ... 204)
For Tone-function : see Table B-8 Description of Tone, Ring and Ticker
Functions.
For Tone-Source of the PSC : see Table B-11 PSC Tone Source Numbers.
For Tone-Source of the PMC : see Table B-12 PMC Tone Source numbers.
5 PMC tone data Tone-function (0 ... 99)
For Tone-function : see Table B-11 PSC Tone Source Numbers.
For Tone-Source of the PMC : see Table B-12 PMC Tone Source numbers.
6 Direct downloadable Signalling group 9700 or 9800
signalling group data to
PPU

Table B-2 Relation between PM-OBJECT and OBJ-INDEX

OBJECT
Object for Traffic Observation or Measurement.
The DITRAF, DISPTO, ASTMOB and DETMOB commands ask for additional parameters, depending on the
object.
The relation between objects and parameters is given in Table B-3 Relation between OBJECT and
Additional Parameters.

OBJECT ADDITIONAL PARAMETERS

- 280 -
 0 Bundles BUNDLE, UNIT [, FIGURE-TYPE]
1 Routes ROUTE, FIGURE-TYPE
2 Inter unit bundles IU-BUNDLE, UNIT, FIGURE-TYPE
3 Inter unit routes IU-ROUTE, UNIT, FIGURE-TYPE
4 Extensions UNIT, FIGURE-TYPE
5 Groups GROUP-DNR, FIGURE-TYPE
6 Paging routes PAG-ROUTE, FIGURE-TYPE
7 Add on circuits UNIT, FIGURE-TYPE
8 RKT-SDT circuits UNIT, FIGURE-TYPE
9 SKT-RDT circuits UNIT, FIGURE-TYPE
10 Incoming MFC circuits UNIT, FIGURE-TYPE
11 Outgoing MFC circuits UNIT, FIGURE-TYPE
12 Socotel circuits UNIT, FIGURE-TYPE
13 Convertors CONVERTOR-TYPE, UNIT, FIGURE-TYPE
14 Specific operators OPERATOR-DNR, FIGURE-TYPE
15 Queues ASSIST-GROUP, UNIT, FIGURE-TYPE
16 Switching Network Channels SHELF,17, CRT (PM-Module), FIGURE-TYPE
17 Call data UNIT, FIGURE-TYPE
* 18 Interunit traffic dispersion data SOURCE UNIT, UNIT, FIGURE-TYPE
* 19 Dialled facilities data RESULT-ID, AG, UNIT, FIGURE-TYPE
21 Hatches UNIT, FIGURE-TYPE
* = Only applicable for DISPTO, ASTMOB and DETMOB.

Table B-3 Relation between OBJECT and Additional Parameters

OFF-ON
On or off : 0 = off, 1 = on

OFF-TIME
See parameter ON-TIME.

OLD-PACK
See parameter PACK.

ON-TIME
Time in the format: DHHMM
D = day (1 ... 7), HH = hour (0 ... 23) and MM = minute (0 ... 55, multiple of 5).
In the case of facility timing: time of upgrading. In the case of traffic measurement: time on which
measurement has to start.

OP-STAT
Displayed value, indicating the status of the operator, i.e. Idle, Busy or OM mode.
OPERATOR-DNR
Operator directory number : see DNR.

- 281 -
OPERATOR-TYPE
0 = Basic operator console
1 = Enhanced operator console
2 = Digital operator console

OPTION-INDEX
The option to be modified.

OPTION-VALUE
The new value of the option.

OPTIONS
Bundle options KLMNO[PQRSTUVWXYZ] (0 = no, 1 = yes). When the bundle direction is incoming,
PQRSTUVWXYZ must be omitted.
K = Long line check
L = Exchange line barred check
M = Register recall available or DASS CLI max 16 digits
N = Echo canceller connected
O = ISDN date/time synchronisation
P = Metering available on bundle
Q = Detection first dialtone applied
R = Pre dialtone detection first dialtone
S = Pre dialtone detection second dialtone
T = Provisional switch through
U = Answer sensitive
V = DDO wait for answer
W = Routing tone
X = TRANSCOM tone detection and alarming
Y = DDO sent MFC area number
Z = DDO local ring tone provided

ORDER-IND
This parameter specifies the place where the BSP must be inserted :
0 = the BSP is inserted after any existing BSP with the same BSPT value;
1 = the BSP is inserted before any existing BSP with the same BSPT value.

ORIG-BSP-ID
Originator directory number : see BSP-ID.
ORIG-CC-STRING
Original CLI or COL string which has to be translated : max. 16 digits, the string may end in wildcards (%).

ORIG-DIGIT-STRING
The length of an original digit string is maximum 20 digits. Wildcards are indicated with '%' at the end of the
string. The last '%' means 'one digit or more'.

ORIG-NUMBER
Number to be converted (1 ... 6 digits).

ORIG-NUMB-PLAN
The original numbering plan can be :
0 = Unknown
1 = E.164
2 = Private Numbering Plan (PNP)

ORIG-TON

- 282 -
The Original Type Of Number (TON) may have one of the following values :
0 = Unknown
1 = Subscriber (E.164) / Local (PNP)
2 = National (E.164) / Level 1 regional (PNP)
3 = International (E.164) / Level 2 regional (PNP)

ORIG-UNIT
Originator unit (1 ... 14).

OUT-OPTS
Outgoing route options PQRST[U[V]] (each 0 = no, 1 = yes)
P = Direct switch through
Q = Break in protection on outgoing calls
R = D button allowed
S = Transit allowed
T = Source identification
U = Insert or append close sign
V = CLI restricted (only for SIP and ISDN)

OUTPUT-FILE
The specification of the load control output file :
(LDN:FILE-NAME.EXTENSION.GENERATION)

OUTPUT-FORMAT-VERSION
0 =12 digit Costcentre/PID and 20 digit destination field.
1 =16 digit Costcentre/PID and 20 digit destination field.
2 =16 digit Costcentre/PID and 32 digit destination field.
3 = version 2 plus "Cradle to Grave" report
4 = version 3 plus "Group Call performance" and start time in seconds (new in SIP@Net 6.3)

OUTPUT-SWITCH
Switch to indicate if output of Traffic Measurement data has to be stopped or continued :
0=stop, 1=continue.

OVERLAY-ID
Overlay identity (6 chars) : OM (sub)commands are 6 characters, SAS actions are 4 characters.

OVERWRITTEN-FILES
The number of file(s) overwritten (applicable when open type = write-continuous).

OWN-IP-ADDRESS
The IP address used for the heartbeat protocol (in digit format : aaa.bbb.ccc.ddd).

OWNER
Possible owners of resources are :

NUMBER OWNER/CLAIM-TYPE MEANING

0 NO No owner
1 START Owner of resource during HOTSTART
2 CP1 Call Processing 1
3 SYS System
4 SAS1 System Assurance 1
5 POM1 Project engineering and Operational Maintenance 1

- 283 -
 6 SAS2 System Assurance 2
7 POM2 Project engineering and Operational Maintenance 2
8 CP2 Call Processing 2

P2P-RTP
0 = Calls between a SIP extension and the SIP trunk are made via the ISG in a hybrid domain and via the
Media Server in a server domain.
1 = Calls between a SIP extension and the SIP trunk are made peer-to-peer. This implies that no ISG or
Media Server is involved in media handling.

PACK
The FEPROM/RAM file names are Fcpppv.vll or Fccppv.vll, in which :

'F' : all FEPROM/RAM file names start with an 'F'.

'c' or 'cc' : indicates the type of board:
14 or 15 = PMC-HR/MC/LU
18 = PMC-G
19 = PMC-SIC / PMC-IP
22 = DTX-I / DTX-I (R) note 1
32 = DLC-U
33 = DLX-U
34 = DLX-L
43 = DCC
46 = DCC-8
51 = DTU-VC
52 = ALC-G
55 = DTU-G note 5
6x = CPU3000 without AM3000 note 2
82 = PM Observer
9x = CCS and CPU3000 with AM3000 note 2
A0 = SNS
A1 = CIE
B0 = Primary boot CPU3000 note 3
B6 = Boot program CPU3000 without AM3000 note 4
B9 = Boot program CPU3000 with AM3000 note 4
E3 / E4 / E5= ErgoLine D330 / 340 / 325
'ppp' or 'pp' : indicates the package-identity.
'v.v' : indicates the version.
'll' : indicates the level update.

Notes 1 F220xx for DTX-I and F221xx for DTX-I(R)

2 Package downloading is not under CPU control. Package-ids are only displayed with OM
command DIEXID.
3 Primary boot program downloading is not supported in the field.
4 OM command STLOBP has to be followed for this package.
5 Downloading the DTU-G requires special functionality from PMC and CPU. Therefore
downloading is supported in combination with a PMC-G with package F18100.501 (or

- 284 -
 higher), PMC-MC/PMC-HR with package F14101.301/F15101.301 (or higher) and with CPU
package 810.35 (or higher). The DTU-G has one generic operational package that supports
both the DTU-PU and the DTU-PH mode. Upon production the DTU-G contains an
operational package. To upgrade a DTU-G :
a) Put the DTU-G board in a DTU-PH board position;
b) Make sure that the board mode on the DTU-G is set to DTU-PH and that the protocol
mode corresponds with the protocol mode of the actual board position (ISDN/DPNSS);
c) Execute normal upgrade scenario (INSTPK/SETOUT/SETINS).
The Operational Package ID can be read by means of the OM command
DIPACK:<SHELF>,<BRD>;
This applies for both DTU-PU mode as well as DTU-PH mode.
Examples :
F22010.105 : DTX-I package 201.01.05
FA0000.304 : SNS package 000.03.04
F98102.041 : CCS package 810.20.A (41 is the hex value for 'A')

PAG-ROUTE
Paging route number (0 ... 254) : see also ROUTE.

PAGING-CODE
Virtual paging code (1 ... 6 digits).

PARK-POS
Defines if park positions must be assigned : 0 = no, 1 = yes.
If the value is 1, then 9 park positions are defined for the group DNR.
If the park position is related to a group member, then 2 park positions are defined.

PASSED-BYTES
The size of the data written to / read from the currently accessed file.

PASSWORD
The password is applied during the SIP registration process. It may contain upper and lower case characters.
In case it is left empty it is assumed that no authentication is performed.
in OM command CHSIPD (used for a SIP trunk), the length is limited to 78 characters since SIP@Net 5.1.
in OM command CHSUSR (used for SIP terminals), the length is limited to 8 characters.

PAT-MODE
Periodic Autonomous Test Mode : 0 = normal, 1 = installation mode/factory test.

PAUSE-PLACE
Defines the pause position in the outgoing digit string (external number). The time of the pause is defined
by parameter INTERVAL.

PC-REPORT-TYPE
1 = Show IP address information
2 = Show non IP information

PCT-TYPE
Circuit type :
1 = Line circuit (LCT)
2 = Trunk circuit (TRC)
3 = Operator circuit (OCT)
4 = Convertor

- 285 -
5 = RKT-SDT
6 = SKT-RDT
7 = In-MFC
8 = Out-MFC
9 = Paging circuit
10 = RS-Socotel
11 = Music on Hold
12 = Music on COB
13 = D channel
14 = Trunk circuit ISDN
15 = Wake_up/MW announcement circuit
16 = Hatch
17 = IAS-TS
PCT types are discussed in more detail in appendix C. BOARD AND PCT TYPES.

PEER-IP-ADDRESS
The opposite heartbeat interface in the SIP@Net Dual Server and/or Server Cluster (in digit format :
aaa.bbb.ccc.ddd). If omitted, then the SIP@Net Server is not working in the Dual Server and/or Server
Cluster configuration.

PERIODICITY
The item number where the periodicity sets in (0 ... 254).
This parameter must be smaller than the NR-OF-ITEMS.

PERIODS
Number of measurement periods of 15 minutes (1 ... 254)

PERIP-DATA-FILE
File identification (LDN, file name, extension).

PID/COST-CENTRE
Personal IDentification code (1 ... 16 digits) or Cost Centre number (1 ... 12 digits).

PM-OBJECT
The type of object when changing the PM projecting data : see Table B-2 Relation between PM-OBJECT and
OBJ-INDEX.

POINT-CODE
Point Code (1 ... 16367 : in OM command ASEXTN limited to 1 ... 9999)
A node in a CCIS network is identified by a point code. The Destination Point Code (DPC) is the destination
node of a call and the Originating Point Code (OPC) is de originating node of a call. The Point Code is
comparable with the iS3000 node identification.

PORT-ID
Port identifier (6 hexadecimal digits or *)

POST-DIAL
Post dialling mark : 0 = no, 1 = yes.

POST-DIGIT
Digit, following the external number (0 ... D).

PR#
Displayed parameter, indicating the paging route number.

- 286 -
PRE-DIGIT
Digit, preceeding the external number (0 ... D).

PREF-CODE
Preferred/Non prefered code : 0=non-preferred, 1=preferred.

PRES
Displayed value, indicating the number of operators present.

- 287 -
PRES-CH
Displayed value, indicating the number of operators present and call handling.

PRES-POM
Displayed value, indicating the number of operators present and in the OM mode.

PRIO-CODE
(Over)write Priority code :
1 = User can reprogram the key
3 = User cannot reprogram the key

PROP
Properties of a device : 6 bits (0=no, 1=yes), indicating respectively: Read access, write access, multiple file
device, multiple file access device, variable record size, relative access device.

PROPRIETARY-OR-QSIG
0 = Proprietary (default)
1 = QSIG standardised

PROT
SIP protocol selection : the meaning is as follows :
- a 'T' or 't' specifies that TCP needs to be applied whenever a SIP command is sent.
- a 'S' or 's' specifies that TLS needs to be applied whenever a SIP command is sent.
- in case it is left empty UDP is applied.
- any other character selects UDP.

PROT-TYPE
Protection type : 0 =new, 1=append, 2=read, 3=delete.

PROTECTION
Protection level (0 ... 7) of New, Append, Read or Delete

PROTOCOL-TYPE
Type of protocol used in device communication :
0 = Character protocol (CPU3000 only)
1 = BCS protocol (CPU3000 only)
2 = Logical protocol

PROFILE-ID
Identifies a profile (0 ... 65535) : 0 = default profile (always present)

PROXY-IP-ADDR
The provider's proxy IP address.

PROXY-IP-PORT
The provider's proxy port.

PROXY-NAME
The provider's proxy domain name part of the URI, e.g. proxy.pbc.nl.

PSI
Protocol Stack Identifier.

PTN-ID
PVN Private Telecommunication Network Identity (0 ... 9999) : the default value is 9999.

- 288 -
PVN-MODE
PVN working mode :
0 = PVN Standard working mode (default)
1 = PVN Modem working mode (Network Signalling Convertor (NSC))
2 = PVN Compressed working mode

PW-GROUP
Password group (0 ... 7) : see Table B-4 Relation between PW-GROUP and PW-KEY.

PW-KEY
Password key (0 ... 15) : see Table B-4 Relation between PW-GROUP and PW-KEY.

PW-GROUP PW-KEY REMARKS

0 0 ... 13 Authority class Number
1 ... 4 0 ... 7 1-New
2 = Append
3 = Read
4 = Delete
PW-KEY indicates the protection level
5 0 ... 2 PW-KEY indicates the degradation level
6 0 or 1 1 = INIDSK and CHACIV, 0 =not used.

Table B-4 Relation between PW-GROUP and PW-KEY

PW-NBR-LENGTH
One or two digits in the range of 0 ... 16 indicating the number of password digits to be given. If the
parameter is omitted, it is assumed that no password digits have to be given.

Q-POS-ALGORITHM
Queue Position Algorithm :
1 = absolute position in the COB queue (default).
2 = weighted position. The weighted position is calculated relative to the number of active agents, and the
maximum length of the queue.

Q-PRIORITY
Queue Priority (1 ... 8) : the Queue Priority number ranges from 1 (highest priority) to 8 (lowest, default).
QSIG-FACILITY
0 = Automatic Ring Back
1 = Optimum Path

QUEUE-DISPLAY
Select the operator queues for display load :
0 = display load of queues signalled by leds A1, A2, A3, A4, C, M1, M2
1 = display load of queues signalled by leds U2/A5, U3/A6, U4/A7

QUEUE-TYPE
Type of operator queue (0 ... 22) :
0 = Total values for M, C and A queues
1 = A1 queue
2 = A2 queue
3 = A3 queue
4 = A4 queue
5 = A5 queue

- 289 -
6 = A6 queue
7 = A7 queue
8 = A8 queue
9 = A9 queue
10 = A10 queue
11 = A11 queue
12 = A12 queue
13 = A13 queue
14 = A14 queue
15 = A15 queue
16 = A16 queue
17 = M normal queue
18 = M preferred queue
19 = C DDI not answered queue
20 = C DDI unsuccessful queue
21 = C DDI recall not on hook queue
22 = C DDI recall on hook queue

RANK
Rank number in chief/secretary and group arrangements.

REAL-TYPE
Paging type in the case of real paging :
0 = Meet-me paging urgent
1 = Meet-me paging non-urgent
2 = Speech paging urgent
3 = Speech paging non-urgent
4 = Display paging urgent
5 = Display paging non-urgent

REASON FOR STOPPING

0 = Normally
1 = Maximum file size reached
2 = Stopped by OM command
3 = Disk space exceeded
4 = Communication with user lost
5 = Maximum number of open files reached
6 = File already exist
7 = Error
8 = End of file
9 = File already opened
10 = Protection error
11 = File write protection
12 = End of medium detected
13 = Device error
14 = Media error
15 = Communication error
16 = Link to device closed
17 = Command not supported
18 = Timeout application
19 = Error application
20 = Retransmission failed

- 290 -
REFNAME
Reference command name of the file.

REGISTRAR-IP-ADDR
The provider's registrar IP address.

REGISTRAR-IP-PORT
The provider's registrar port. In case it is left empty port 5060 is applied.

REGISTRAR-NAME
The provider's registrar domain name part of the URI, e.g. regist.pbc.nl.

REMOTE-USER-GROUP
Remote user group (0 ... 1).

RENAME-AND-REOPEN
Defines whether or not the file that was requested to be closed, must be renamed to a file with the same
file name but with extension 'BAK' (when such file already exist, it is deleted first) and subsequently a new
file with the original file name and extension must be opened :
0 = no
1 = yes

REP-FACTOR
Number of test repeats (0 ... 9) (0 means continuous testing).

REPEAT-PERIOD
Number of days after which the job has to be repeated (1 ... 9999).
When no value is specified, the job is repeated daily.

REPORT-FORM
0 = Brief Report
1 = Verbose Report
2 = License Configuration Report
9 = Information item of one flash component (chip) on SIMM1 and SIMM2.

REPORT-TYPE
The following report types exist :
00 = No suspicion report
01 = No successors failed
02 = Cancelled event of interest
03 = Suspicion level exceeded
04 = Expired alarm integration
05 = Expired isolation integr.
06 = Solved alarm
07 = Passive alarm
08 = Suspicion
09 = Alarm integration
10 = Successors failed
11 = Blocked alarm
12 = Manually controlled test
13 = Silent alarm
14 = Minor alarm
15 = Major alarm
99 = Project engineering alarm
REROUTING-DIVERSION-NUMBER

- 291 -
The number to reach the diverted-to destination user.

RES-ID
Miscellaneous resource type :
0 = Add on circuit
1 = RKT-SDT
2 = SKT-RDT
3 = Incoming MFC
4 = Outgoing MFC

RESOURCE-TYPE
See table below.

RESOURCE-TYPE DESCRIPTION
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)
026 Clock Reference Unit (CRU)
027 Communication Interface Internal (CII)
028 Switching Network Module (SM)
029 Logical Channel

- 292 -
 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 B-5 Resource Type List

REST-MODE
Restoration mode :
0 = First party control
1 = Calling party control
2 = Called party control

RESTART
A variable indicating the type of start to be executed :
0 = Warmstart (not for STMAIN)
1 = Coldstart
2 = Re-project
3 = Reload

RESTRICTION
Restriction :
0 = unrestricted or 1 = restricted.

RESULT-ID
Result identity : see table below.

- 293 -
 FROM DIAL TYPE / SOURCE
0 1 2 3 4 5 6 7 8 9 DD DD DP DP
RES I O NS NS
DESCRIP TION
ID S- S-
IN O
UT
00 * Second external dialtone place - - - - - - - - - - - X - -
01 No direct result X X X X X X X - X X X X X X
10 Internal number X X X - X @ X - X X X - X X
**
11 Operator M code dialled general X X - - X - - - X X X - X -
12 Meet-me paging urgent with CLI X X X - X - - - X X X - X X
13 Meet-me paging non urgent with CLI X X X - X - - - X X X - X X
14 Priority trunk access code X X X - X - - - X X X - X X
20 Paging answer prefix X - - - - - - - X X - - X -
21 Trunk access code X X X - X - - - X X X - X X
22 * External number - - - - - - - - - - - X - -
23 Common pool abbr. dialling X X X - - - - - X X X - X -
1
** )
24 Group pool abbr. dialling X X X - - - - - X X - - - -
**
25 Access individual abbr. number @ @ @ - - - - - @ @ - - - -
26 Access last external number @ @ @ - - - - - @ @ - - - -
27 Activate FM from primary @ @ - - - - - - @ @ - - - -
28 Prepare FM from primary @ @ - - - - - - @ @ - - - -
29 Activate FM from destination X X - - - - - - X X - - - -
30 Cancel FM from dest. selective X X - - - - - - X X - - - -
31 Cancel FM from dest collective X X - - - - - - X X - - - -
32 Cancel FM from primary X X - - - - - - X X - - - -
33 Pick up general X X - - - - - - X X - - - -
34 Pick up individual X X - - - - - - X X - - - -
35 Switch out of group by member @ @ - - - - - - @ @ - - - -
36 Switch in group by member @ @ - - - - - - @ @ - - - -
37 Switch out of group by supervisor @ @ - - - - - - @ @ - - - -
38 Switch in group by supervisor @ @ - - - - - - @ @ - - - -
39 Executive secretary access @ @ - - - - - - @ @ - - - -
40 Executive secretary absent @ @ - - - - - - @ @ - - - -
41 Executive secretary present @ @ - - - - - - @ @ - - - -
42 Executive secretary complete - - - - - - - X - - - - - -
43 Cost centre prefix X X X - - - - - X X - - - -

- 294 -
 FROM DIAL TYPE / SOURCE
0 1 2 3 4 5 6 7 8 9 DD DD DP DP
RES I O NS NS
DESCRIP TION
ID S- S-
IN O
UT
44 Night extension absent @ @ - - - - - - @ @ - - - -
45 Night extension present @ @ - - - - - - @ @ - - - -
46 CANS code dialled X - - - - - - - X X - - - -
47 Operator M code dialled priority X X - - - - - - X X X - X -
48 Operator A general - - - - - - - - - - X - X -
49 Operator A queue - - - - - - - - - - X - X -
50 Desksharing activate @ - - - - - - - - - @ - - -
51 Desksharing deactivate @ - - - - - - - - - @ - - -
52 Test telephone @ - - - - - - - @ @ - - - -
53 Emergency access code X - - - - - - - X X - - - -
54 Dial up data protection @ @ - - - - - - @ @ - - - -
55 Add on prefix - @ - - - - - - - - - - - -
56 Automatic ring back - - X @ - - - - - - - - - -
57 Cancel automatic ring back X X X - - - - - X X - - - -
58 Break in - - - @ - - - - - - - - - -
59 Bypass code - - - @ - - - - - - - - - -
60 Malicious call trace - @ X - - - - - - - - - - -
61 Extension programming - - - - - - - - - - - - - -
62 Common floor service dialled X X - - - - - - X X - - - -
63 Laundry dialled X X - - - - - - X X - - - -
64 Information dialled X X - - - - - - X X - - - -
65 Reception dialled X X - - - - - - X X - - - -
66 Set don't disturb @ @ - - - - - - @ @ - - - -
67 Reset don't disturb @ @ - - - - - - @ @ - - - -
68 Convertor prefix X X - - - - - - X X X - - -
69 Store individual abbr. number @ @ - - - - - - @ @ - - - -
70 Erase individual abbr. number @ @ - - - - - - @ @ - - - -
71 Replace ind. abbr. number @ @ - - - - - - @ @ - - - -
72 Upgrade traffic service class @ - - - - - - - @ @ - - - -
73 Downgrade traffic service class @ - - - - - - - @ @ - - - -
74 No traffic service class selected @ - - - - - - - @ @ - - - -
75 Call waiting code dialled X X - - - - - - X X - - - -
76 Message waiting LED on type 0 X X - - - - - - X X - - - -

- 295 -
 FROM DIAL TYPE / SOURCE
0 1 2 3 4 5 6 7 8 9 DD DD DP DP
RES I O NS NS
DESCRIP TION
ID S- S-
IN O
UT
77 Message waiting LED on type 1 X X - - - - - - X X - - - -
78 Message waiting LED on type 2 X X - - - - - - X X - - - -
79 Message waiting LED off type 0 X X - - - - - - X X - - - -
80 Message waiting LED off type 1 X X - - - - - - X X - - - -
81 Message waiting LED off type 2 X X - - - - - - X X - - - -
82 TMS dialled X - - - - - - - X X - - X -
83 Activate FM from primary group @ @ - - - - - - @ @ - - - -
84 Prepare FM from primary group @ @ - - - - - - @ @ - - - -
85 Cancel FM from primary group @ @ - - - - - - @ @ - - - -
86 Activate FM from dest. group X X - - - - - - X X - - - -
87 Cancel FM from dest. sel. group X X - - - - - - X X - - - -
88 Cancel FM from dest. coll. group X X - - - - - - X X - - - -
89 Auto answering circuit dialled - - - - - - - - - - X - - -
90 COB display for supervisor @ - - - - - - - @ @ - - - -
91 Network access code X X X - X X - - X X X - X -
92 CSDN access code @ - - - - - - - @ @ - - - -
93 Give a line - - X - - - - - - - - - - -
94 Start post dialling - X - - - - - - - - - - - -
95 Enquiry on trunk initiation - X X - - - - - - - - - - -
96 Enquiry on trunk take over - X X - - - - - - - - - - -
98 Activate diversion on busy X X - - - - - - X X - - - -
99 Cancel diversion on busy X X - - - - - - X X - - - -
100 Activate fixed follow me X X - - - - - - X X - - - -
101 Start call waiting - - - @ - - - - - - - - - -
102 Start Camp On Busy - - - @ - - - - - - - - - -
103 General cancel code X X - - - - - - X X - - - -
104 Change password X X - - - - - - X X - - - -
105 Enable up/down-grading X X - - - - - - X X - - - -
106 Disable up/down-grading X X - - - - - - X X - - - -
107 Upgrade traffic class X X - - - - - - X X - - - -
108 Downgrade traffic class X X - - - - - - X X - - - -
109 Password DDO from own X X - - - - - - X X - - - -
110 Password DDO from other X X X - - - - - X X - - - -

- 296 -
 FROM DIAL TYPE / SOURCE
0 1 2 3 4 5 6 7 8 9 DD DD DP DP
RES I O NS NS
DESCRIP TION
ID S- S-
IN O
UT
111 Cost centre modulo X X X - - - - - X X - - - -
112 Cost centre validate X X X - - - - - X X - - - -
113 Access port direct (SSM) X X X - - - - - X X X - X -
114 Access port call back (SSM) X X X - - - - - X X X - X -
115 Cancel call back call (SSM) X X X - - - - - X X X - X -
116 Private call X X X - - - - - X X - - - -
117 Directed call X X - - - - - - X X - - - -
118 Short code dialling group X X - - - - - - X X - - - -
119 Pick up by rank number X X - - - - - - X X - - - -
120 Speech paging urgent with CLI X X X - X - - - X X X - X X
121 Speech paging non urgent with CLI X X X - X - - - X X X - X X
122 Display paging urgent with CLI X X X - X - - - X X X - X X
123 Display paging non urgent with CLI X X X - X - - - X X X - X X
124 Display paging urgent X X X - X - - - X X X - X X
125 Display paging non urgent X X X - X - - - X X X - X X
127 CallManager MIS dialled @ @ - - - - - - @ @ - - - -
128 ACD group day prefix @ @ - - - - - - @ @ - - - -
129 ACD group night prefix @ @ - - - - - - @ @ - - - -
130 Dial up break in @ @ - - - - - - @ @ - - - -
131 Dial up CLIR X X - - - - - - X X - - - -
132 PVN user channel address - - - - - - - - - - X - - -
133 PVN signalling channel address - - - - - - - - - - X - X -
134 Overlay X X - - - - - - - - - - - -
135 Log on prefix X X - - - - - - - - - - - -
136 Log off prefix X X - - - - - - - - - - - -
137 CSTA control prefix X - - - - - - - - - - - - -
138 Subnetwork access code X X X - X X - - X X X - X -
139 Meet me paging urgent X X X - X - - - X X X - X X
140 Meet me paging non urgent X X X - X - - - X X X - X X
141 Speech paging urgent X X X - X - - - X X X - X X
142 Speech paging non urgent X X X - X - - - X X X - X X
143 Move DNR for installation @ - - - - - - - - - - - - -
144 Create DNR for installation @ - - - - - - - - - - - - -

- 297 -
 FROM DIAL TYPE / SOURCE
0 1 2 3 4 5 6 7 8 9 DD DD DP DP
RES I O NS NS
DESCRIP TION
ID S- S-
IN O
UT
145 CSTA server dialled *** X X - - - - - - X X - - - -
146 Forced Release - - - @ - - - - - - - - - -
147 Line access @ @ - - - - - - - - - - - -
148 Line pickup @ @ - - - - - - - - - - - -
149 Line park - @ - - - - - - - - - - - -
150 Line park incoming call - - - - - - - - - - X - - -
151 Network Node Id See Table B-7 Result ID 151
152 Dial for group prefix X X - - - - - - X X - - - -
153 Intercom prefix X X - - - - - - X X - - - -
154 Listen in call prefix X - - - - - - - - - - - - -
155 Dummy Prefix - - - - X - - - - - - - - -
156 SMA access enblock X X - - X - - - - - - - - -
157 SMA access DTMF X X - - X - - - - - - - - -
158 Operator C queue - - - - - - - - - - X - X -
159 Operator C queue for DND - - - - - - - - - - X - - -
160 Dial-up CLIP X X - - - - - - - - - - - -
161 Upgrade day night traffic class X X - - - - - - - - - - - -
162 Downgrade day night traffic class X X - - - - - - - - - - - -
163 Prevent assistance - - - - - - - - - - X - - -
164 Diversion bypass prefix X X X - - - - - - - - - - -
165 SMA Terminating Service Access - - - - - - - - - - X - - -
Code
166 Show own DNR X - - - - - - - - - - - - -
167 Pickup in conversation general X - - - - - - - - - X - - -
168 Pickup in conversation individual X - - - - - - - - - X - - -
169 Activate Call Forwarding @ @ - - - - - - @ @ - - - -
Don't Answer from primary
170 Cancel Call Forwarding @ @ - - - - - - @ @ - - - -
Don't Answer from primary
171 Activate Call Forwarding @ @ - - - - - - @ @ - - - -
When Busy from primary
172 Cancel Call Forwarding @ @ - - - - - - @ @ - - - -
When Busy from primary
173 Activate Call Forwarding @ @ - - - - - - @ @ - - - -
Not Reachable from primary

- 298 -
 FROM DIAL TYPE / SOURCE
0 1 2 3 4 5 6 7 8 9 DD DD DP DP
RES I O NS NS
DESCRIP TION
ID S- S-
IN O
UT
174 Cancel Call Forwarding @ @ - - - - - - @ @ - - - -
Not Reachable from primary
175 Activate Twinning from primary X X - - - - - - X X - - - -
176 Cancel Twinning from primary X X - - - - - - X X - - - -
177 Activate FM internal originator X X - - - - - - X X - - - -
178 Cancel FM internal originator X X - - - - - - X X - - - -
179 Activate FM external originator X X - - - - - - X X - - - -
180 Cancel FM external originator X X - - - - - - X X - - - -
181 Switch out of specific group by X X - - - - - - X X - - - -
member
182 Switch in specific group by member X X - - - - - - X X - - - -
183 Activate SMA X X - - - - - - X X - - - -
184 Set COB queue protection X X - - - - - - X X - - - -
185 Reset COB queue protection X X - - - - - - X X - - - -
X = Normally accessable from this dial source.
@ = Normally accessable, but appropriate FCM or OM facility configuration must be assigned to
originating party.
* = Automatically assigned with ASEXTN.
** = Assigned with ASBLCK.
*** = Assigned with CHCSDD.
1
) = only on SIP/CCIS/QSIG and DPNSS (as indicated in the last but one column).
- = Not accessable from this dial type source.

Table B-6 Result IDs

FROM DIAL TYPE / SOURCE

RES ID DESCRIPTION
10 11
151 Network Node Id X -
X = Normally accessable from this dial source.
- = Not accessable from this dial type source.

Table B-7 Result ID 151

RETRIEVE-ACTION
Indicates which data should be retrieved :
0 = retrieve Network and Local data
1 = retrieve Network data only
2 = retrieve Local data only

- 299 -
RETRIEVE-OPTIONS
Indicates which data should be retrieved : PQ
P = retrieve dynamic data : 0 = no (default), 1 = yes
Q = retrieve name number relations : 0 or 1, depending on LOSYSOP 129.

RIN
Route Identification Number (1 ... 20 digits).

ROUTE
Route number (0 ... 254).

ROUTE-ALTERN
Routing alternative :
0 = primary
1 = alternative

ROUTE-NAME
This parameter defines the user part of the URI, as it is supplied by the SIP provider the URI that is applied
for registrations is the combination of this parameter and the registrar name (OM command CHSIPA)
separated by an @ character. The length of the user name is limited to 78 characters, excluding the start
and end quotes (since SIP@Net 5.1).
The name may contain upper and lower case letters and digits (separators and punctuations are not
allowed : the formal specification is given in RFC 2396 and contains a more complex format).

ROUTE-TABLE
Route table number (0 ... 254).

ROUTE-TYPE
0 = Suppress all
1 = MDF
2 = Standard (according to PE file)
3 = Isolate unit (No outgoing alarms to other units)
4 = Standard operator and MDF

R/W
Indication for which actions the file is opened :
- R = read from file
- W = write to file

SC
Security Code. The default value is '899111'.

SCT
Index, indicating the software state (1 ... 4 decimal numbers).

SECR-BSP-ID
Secretary BSP-ID : see BSP-ID.

SECR-RANK
Secretary rank in pool (0 ... 9)

SELECT-ANNOUNCEMENT-DATA

- 300 -
0 = Announcement data for assistance group
1 = Announcement data for ACD group
2 = Announcement data for music on hold

SEQ
Sequence number of a bundle in a route or a line in a bundle.
Sequence numbers are assigned automatically and represent the order in which the lines or bundles are
defined. It also represents the order in which the bundle or line is selected.

SEQUENCE-NO
Sequence number of a link (0 ... 7).

SEQUENCE-TABLE
Sequence table, indicates which route table should be selected (1 ... 5). 1 indicates the default table, 2 ... 5
can be used for Least Cost Routing and iSNet Private Virtual Networking (select with facility timing).

SEQ-TABLE/ZONE
Sequence table/zone (see parameter Sequence table).
When it concerns the tariff class, the (tariff)zone has to be given. Possible values 2 ... 5.

SERVER-AND-ACTION-CODE
A digit string with the format: P[Q]Q
P is the server code. It indicates the type of server addressed :
0 = Message server
1 = ACD MIS server
[Q]Q is the action requested from the server. The range depends on the type of server given by SERVER-
CODE. The following actions are defined for each application type:

Message Server : 0 = normal text message to server

1 = urgent text message to server
2 = forward normal text message
3 = forward urgent text message
4 = broadcast normal text message
5 = broadcast urgent text message

ACD MIS Server : 0 = agent login

1 = agent logout
2 = agent not ready
3 = agent ready
4 = agent login and ready
5 = enter transaction code
6 = agent request consultation
7 = agent logout by supervisor
8 = agent not ready by supervisor
9 = agent ready by supervisor
10 = ACD group to day service
11 = ACD group to night service

SERVER-NUMBER
Number of the SIP@Net Server in a Server Cluster configuration : possible values 1 ... 22.

- 301 -
SERVICE
Identifies a service for a Client Service Profile :
0 = OM
1 = TMS (SysManager)
2 = ALRM (Simple Alarming)
3 = FDCR
4 = iTMP server
5 = SIP server

SERVICE-CENTRE-IDENTITY
A digit string (1 ... 20 digits) identifying the SMS Service Centre.
SERVICE-CENTRE-TYPE
0 = SMS Service Centre

SET-NAME
Filename of a set (6 characters).

SET-TYPE
Type of set :
0 = all types
1 = active resident sets
2 = inactive resident sets
3 = overlay sets
4 = resident sets

SHELF
Shelf identity, in format UUCCS, in which :
UU = Unit (1 ... 14), must be omitted for single unit systems
CC = Cabinet (1 ... 15)
S = Shelf (1 ... 9)
1 ... 4 are real hardware shelves.
5 ... 9 are virtual PM shelves (can only be assigned in the same cabinet as where the CM resides; maximum
number of virtual PM shelves can be 5 (BOUND 372)).
In an iS3050 boundary 154 (system limited nbr of shelves per cabinet) must be set to 4.
In an iS3010/3030 the virtual PM numbers can be 3 ... 7.

SHELF-TYPE
Indicates the type of shelf :
0 = PM-2500 shelf (local or remote)
6 = PM-1100 shelf
7 = RPM-1100 shelf
8 = RPM-255 upper shelf
9 = RPM-255 lower shelf
10 = PM-255 upper shelf
11 = PM-255 lower shelf
12 = PM-55 upper shelf
13 = PM-55 lower shelf
14 = PM-1000 shelf
15 = CSM shelf

- 302 -
16 = Virtual PM shelf (iTMP)
17 = Virtual SMA shelf (SMA/CCIS)
18 = Virtual SIP shelf

SIC-ITEM
This can be :
1 : set IP address of the SIC
2 : set the TCP port for the links to the SIC
3 : set control <SERVER-NUMBER> [optional]
When omitted, it reset the values to the factory defaults.

SIC-ITEM-VALUE
The meaning of this parameter depends on the value of parameter SIC-ITEM :
SIC-ITEM=1 : SIC-ITEM-VALUE : the IP address of the SIC.
SIC-ITEM=2 : SIC-ITEM-VALUE : the TCP port for the links to the SIC.
SIC-ITEM=3 : SIC-ITEM-VALUE : only required in a Server Cluster configuration.
If a Slave Server is allowed to take over the IP-PM then this item defines the Slave <SERVER-NUMBER>.
If no value is given, then the <SIC-ITEM> is reset to the factory default.

SIGCH-ADDRESS
- in case of PVN : signalling channel address of the opposite ISPBX (1 ... 20 digits)
- in case of iPVN : the IP address of the opposite ISPBX : CPU3000, CIE-2 or SIP@Net Server.
IPv4 = a.b.c.d
IPv6 = a:b:c:d:e:f:g:h

SIGCH-TU
Signalling channel timer unit (0=seconds, 1=minutes); identifies the unit of the time value specified by
parameter SIGCH-TV.

SIGCH-TV
Signalling channel timer value (0 ... 16383).

SIG-ID
Signal identifier (0 ... FFF (hex) or * = don't care).

SIG-GROUP
PPU signalling group (4 hexadecimal) : see appendix C. BOARD AND PCT TYPES.

SIP-DRIVER-IP-ADDRESS
The IP Address of the own SIP driver.

SIP-DRIVER-IP-PORT
The IP Port of the own SIP driver : default value is specified by boundary 416 (SIP driver listen port for UDP
and TCP) and 437 (SIP driver TLS listen port)

SIP-ROUTE
SIP route number (0 ... 254)

SIP-REPORT-TYPE
Specifies the info to be displayed next to EHWA and DNR :
0 = display IP-address, port, protocol.
1 = display SIP User-Agent type.
2 = display lease-time requested and left.

- 303 -
SIP-SIG-GROUP
SIP Signalling Group : B000 ... B0FE (0 ... 254).
The default SIP Signalling Group is specified by system boundary 439.

SIP-TRUNK-GUARDING-TIME
SIP trunk guarding time in seconds.
0 = no SIP trunk guarding
1 … max. 1800 seconds : 60 seconds is adviced.

SMART-BOX-EM
Mercury smart box emulation : 0 = no, 1 = yes.

SOCKET
Internal ID of a TCP or UDP Socket.

SOFT-RING
Controls the soft ring that can be activated for function keys where a group member is monitored. (0 ... 3).
0 = no softring
1 = one softring beep
2 = two softring beeps
3 = three softring beeps

SOURCE-FILE
Specification of the source file in the format :
LDN:FILENAME.EXTENSION[.GENERATION]

SOURCE-MENU
Menu number (0 ... 65533, max number is defined by NEBOUND 96).

SPEED+MODE
Concatenation of Terminal speed and Conversation mode: TTC.
The following terminal speeds are possible (in Bauds) :
1 = 50
2 = 75
3 = 110
4 = 150
5 = 200
6 = 300
7 = 600
8 = 1200
9 = 1275
10 = 2400
11 = 3600
12 = 4800
13 = 7200
14 = 9600
15 = 12000
16 = 14400
17 = 19200
18 = 38400
19 = 48000
20 = 56000
21 = 64000

- 304 -
The following conversation modes are possible :
0 = Full duplex, asynchronous
1 = Full duplex, synchronous
2 = Half duplex, asynchronous
3 = Half duplex, synchronous
4 = Simplex outgoing, asynchronous
5 = Simplex outgoing, synchronous
6 = Simplex incoming, asynchronous
7 = Simplex incoming, synchronous

SPV
SIP Protocol Variant : Even though SIP is a standard, a variety of options following different RFCs remains
possible. Therefore a number of provider dependant variants has been implemented :

0 = Generic variant
Generic SIP protocol, suitable for most providers.
1 = Toplink / Inode variant
See RFC3325 for more details.
2 = Telsome variant
The Danish SIP provider Telsome requests a non-standard authorization method. During
authentication the username of the From URI and the password of the route are used.
3 = KPN variant
In the KPN variant the Privacy header will have the value "user" in case of presentation of restricted
numbers. Default, in case of presentation of restricted numbers, SIP@Net will add a Privacy header
with the value "id" to the SIP message.
Also in case of an incoming SIP trunk call to a BCT routing point, the incoming diversion header is
ignored.
4 = Microsoft OCS / Lync / Skype-for-Business variant
No diversion header will be added, as this causes problems in OCS 2007 R2.
Note that for this SPV, license 74 "Non-NEC SIP Trunk" is required.
5 = Microsoft Office Exchange Server variant (VoiceMail)
For inter working with Microsoft Office Exchange Server on the iS3000/SIP@Net Server.
6 = Skype-Connect variant
In the from-field (outgoing Invite from SIP@Net towards Skype) Skype requires the Skype
authentication username, instead of the calling party identity as done in the generic SIP protocol.
Note that for this SPV, no license 74 "Non-NEC SIP Trunk" is required.
7 = Tele2 variant
If this SPV is selected on the SIP route, then :
- for secret calls, the From-header shows the name "Anonymous" and the number
sip:<number>@<ip-address> instead of "Anonymous" sip:anonymous@anonymous.
- in the diversion-header a SIP URI is sent, instead of a tel URI.
A diversion header is included in SMA calls, when system option 139 "Provide CLI (of calling party)
to SMA access" is set to "1".
8 = Hellenic Telecommunications Organization (Ote SA) variant
The provider's proxy domain name in the URI.
9 = Telenor variant
In case a call is made to a DNR in an SMA relation and the call is routed to the remote terminal via a
SIP route (that has this Telenor SIP Protocol Variant) then the INVITE message will have a diversion
header. Note that for the diversion header also license 70 (SIP Trunk Supplementary Services) must
be present.
10 = 3C Application Suite variant
Support of Tie-line functionality sending and receiving of Call-Info header.

- 305 -
11 = Telfort variant
Provider Telfort uses the “To header” to identify the destination instead of the “Request header”
and uses the domain name in the URI's.

Since SIP@Net 6.0.1, this SPV 11 is extended for calls with "CLI permanently restricted" as follows :
- The "From" field must look like :
<sip:anonymous@anonymous.invalid>;tag=8962975833482463694.
- The "Contact", "P-Asserted" and "P-Preferred" headers may contain the identity when using
presentation restriction.
12 = "Discard diversion header" in the incoming INVITE
This SPV 12 is like SPV 3 "KPN variant", however, in case of SPV 12 the Privacy header will have the
value "id" (instead of "user") in case of presentation of restricted numbers.
13 = Gateway variant : it acts as SIP extensions.
A SIP route to the 3C system must be configured exclusively for Gateway Extensions.
Note that for this SPV, license 81 "Gateway Extension" is required.
14 = SIP@Net Media Server used as Conference Bridge to 3C.
A SIP route to the 3C system must be configured exclusively for Conference Bridge.
It uses the "iS3000-Conference-User-Agent-ID" to enable 3C Conference Bridge.
15 = Telenor Sweden variant
Same as SPV 9 (Telenor), but when composing the external CLI (of the SMA extension) in the
Diversion header the CC translation table of the route is ignored: only the Local Domain data of
SMA extension and SIP route is used.

SSP
Special Services Prefix : can be one upto 12 digits.

SSP-NP
Numbering Plan of the Special Services Prefixes : see parameter NUMBERING-PLAN.

SSP-TON
Type Of Number of the Special Services Prefixes : see parameter TYPE-OF-NUMBER.

START-KEY
Indicates the function key where copying/clearing starts (0 ... 254).

START-TIME
Date and time when the PFSM task was started.

STATE
Required facility state :
0 = Absent / Deactivate
1 = Present / Activate

STATUS
Status of the SIP route :
0 = de-activate the SIP route
1 = activate the SIP route as registerer (client)
2 = activate the SIP route without registration
3 = activate the SIP route as registrar (server)

STOP-AT-MAX-FILE-SIZE
Defines whether or not the application must be stopped when the file size has reached the defined
maximum size.

- 306 -
1 (yes) : The application stops when the file has reached the specified maximum size.
0 (no) : The application continues when the file has reached the specified maximum size. This implies that
the file is closed and renamed to a file with the same file name but with extension.
"BAK" : The application continuous writing to this newly opened file.

SUBSCR-CAT
Category of subscriber indicating the type of calling party (1 ... 15).

SUPERVISOR-BSP-ID
Supervisor BSP-ID (see BSP-ID)

SUSPEND/RESUME
Indicates when an FTP server must be suspended or resumed :
0 = suspend / 1 = resume

SWITCH-ALL/INIT-STATUS
SWITCH-ALL / INIT-STATUS SWITCH-ALLOWANCE INITIAL STATUS AFTER ASSIGN
0 No Loggedin and present
1 Yes Loggedin and present
2 Yes Loggedin and absent
3 Yes Loggedout and absent
Value 0 and 1 are used for normal group arrangements and ACD.

Values 2 and 3 can be used by third party applications (CSTA) that manipulate the absent/present status
of ACD group members. These applications also store (value 3) or possibly store (value 2) in SIP@Net
whether or not the group member has “logged in into the application”. Only when logged in the member
can switch absent/present.
Example: value 3 is used for Contact Centre 400.

TAC
Trunk Access Code : a digit string related to Result ID 21 (using OM command ASINTN).

TARIFF-CLASS
Tariff class. Possible values 0 ... 254.

TARIFF
See the parameter "Default-Tariff".

TASK
Task number related to a peripheral data file access task. The task number consist of two elements: UNIT
and TASK-SEQUENCE-NUMBER. UNIT is the unit where the resource is located that accesses the peripheral
data file. TASK-SEQUENCE-NUMBER is a (running) number, 000 ... 254, that identifies the task within a unit.
After successful initiation the next number for TASK is used.
Examples:
TASK UNIT TASK SEQUENCE NUMBER
2000 2 000
1020 1 020
12254 12 254

TERMINAL
Terminal name of 5 characters (eg. VDUxx)

- 307 -
TERMINAL-TYPE
0 = VDU
1 = Operator console
2 = Operator console with key
3 = TMS (SystemManager)

THRESHOLD-PRIORITY
ACD group priority : 0=No priority, 1=Priority group.

TICS
Threshold of metering ticks (max 4 digits).

TICKER-SOURCE
Added ticker function source (0 ... 3) :
0 = no ticker
2 = ticker tone 0
3 = ticker tone 1

TIME
Time specification in format <HOURS>:<MINUTES>

TIME-PERIOD
Time period in seconds (1 ... 60).
After the time period has been expired, the budget is decreased.

TIMER-INDEX
The timer to be modified.

TIMER-UNIT
0 = seconds
1 = minutes

TIMER-VALUE
The new value of the timer.

T-VALUE
Number of time units (0 ... 63).

TONE-AND-DDI-OPTS
Tone and direct dialling in options PQ[RSTUVWX] :
P = Busy tone before answer (0=no, 1=yes)
Q = Busy tone after answer (0=no, 1=yes)
R = DDI tone to be sent to external party (0 ... 4)
- 0 = no tone
- 1 = internal dial tone
- 2 = external dial tone
- 3 = internal ring tone
- 4 = external ring tone
S = Traffic class (0 ... 7)
T = Action when DDI to busy extension (0 ... 9)
U = Action when DDI dial time out (0 ... 9)
V = Action when DDI ringing time out (0 ... 9)
W = Action when DDI to unallocated number (0 ... 9)
X = Action when unsuccessful DDI call (0 ... 9)

- 308 -
For TUVWX the following actions are possible :
0 = Busy tone
1 = NU tone
2 = Clear backward
3 = No action
4 = COB and send answer
5 = Operator or busy tone
6 = Operator or nu tone
7 = Operator or clear back
8 = Operator or no action
9 = Operator or night extension

TONE-FUNCTION
Default settings of Tone, Ring and Ticker functions can be found in the Signalling Data manual.
In this manual there are more Tone, Ring and Ticker functions as given in this table.

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 (not used)
012 Call waiting tone burst.
013 Paging absent tone.
014 Paging in progress tone.
015 Bypass tone.
016 Conference control tone (not used)
017 Camp on busy tone to caller.
018 Park tone.
019 Through connect ring tone.
020 Ticker tone
021 Howler tone
024 ARB destination ring back tone.
025 Alternative routing warning tone (not used)
026 Enter password tone.
027 Routing tone.
Ring Function 100 Internal ring current.
101 External ring current.
102 Automatic ring back current.
103 Emergency alarm ring current.
104 Through connect ring current.

- 309 -
 105 Service A ring.
106 Service B ring (used for message waiting ring).
107 Ring burst.
Ticker Function 200 Break-in ticker.
201 Add-on ticker.
202 Urging ticker
203 Call waiting ticker.
204 Dial up Break in Ticker.
Table B-8 Description of Tone, Ring and Ticker Functions.
The ones not mentioned here have become obsolete or are intended for future use.

TONE-SRC
Tone source number on the PSC-A tone PROM or PSC-G Country Group 1 (see Table B-11 PSC Tone Source
Numbers) or on the PMC (see Table B-12 PMC Tone Source numbers.). See Table B-13 Conversion Tone
Source Numbers of PSC-A to PMC for the relation between tone sources on the PSC and PMC.

FREQ- VALUE TONE TYPE FREQUENCY LEVELS (dBm0) REMARKS

0 Silence
1 DTMF 697 1209 - 4.2 - 2
2 DTMF 697 1336 - 4.2 - 2
3 DTMF 697 1477 - 4.2 - 2
4 DTMF 697 1633 - 4.2 - 2
5 DTMF 770 1209 - 4.2 - 2
6 DTMF 770 1336 - 4.2 - 2
7 DTMF 770 1477 - 4.2 - 2
8 DTMF 770 1633 - 4.2 - 2
9 DTMF 852 1209 - 4.2 - 2
10 DTMF 852 1336 - 4.2 - 2
11 DTMF 852 1477 - 4.2 - 2
12 DTMF 852 1633 - 4.2 - 2
13 DTMF 941 1209 - 4.2 - 2
14 DTMF 941 1336 - 4.2 - 2
15 DTMF 941 1477 - 4.2 - 2
16 DTMF 941 1633 - 4.2 - 2
17 Ticker 400 0 4 cycles
18 Ticker 425 0 4 cycles
19 Single 400 0
20 Single 425 0
21 Single 440 0
22 Single 450 0

- 310 -
 23 Single 620 0
24 Single 950 0
25 Single 1400 0
26 Single 1800 0
27 Dual 150 450 0-9
28 Dual 350 440 -3-3
29 Dual 440 480 -3-3
30 Dual 480 620 -3-3
31 Multiply 33.33 400 0
32 Multiply 25 425 0
33 Carrier 33.33 400 -2 80% modulation
34 H'FF 0 Idle pattern for DTX-I
35 H'00 0 Zero pattern

Table B-9 Stc-Tone Data for PMC

INDEX LEVEL (dB) INDEX LEVEL (dB) INDEX LEVEL (dB)

0 0 10 - 10 20 - 20
1 -1 11 - 11 21 - 21
2 -2 12 - 12 22 - 22
3 -3 13 - 13 23 - 23
4 -4 14 - 14 24 - 24
5 -5 15 - 15 25 - 25
6 -6 16 - 16 26 - 26
7 -7 17 - 17 27 - 27
8 -8 18 - 18 28 - 28
9 -9 19 - 19 29 - 29

Table B-10 Coded Tone Levels for PMC

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 as given in this table. The ones not
mentioned have become obsolete or are intended for future use.

TONE-SOURCE FREQUENCY (Hz) LEVEL (dBm0) COMMENT

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)

- 311 -
 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
26 1400 - 4.5
27 1400 -9
28 1400 - 13
29 1800 - 4.5
30 1800 -9
31 1800 - 13

Table B-11 PSC Tone Source Numbers

TONE SPECIFICATION SLAVE DATA

TONE SOURCE REMARK
FREQ. (Hz) LEVEL (dBm) TONE LEVEL
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

- 312 -
 5 150 440 - 6 - 15 17 6
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'
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 B-12 PMC Tone Source numbers.

PSC-A TONE SOURCE PMC TONE SOURCE

4 0
16 2
17 10
18 11
20 14
22 3

- 313 -
 25 4
26 6
28 6
31 7

Table B-13 Conversion Tone Source Numbers of PSC-A to PMC

TREE
Analysis tree number (0 ... 254).

- 314 -
TRFC
Traffic class (0 ... 7) : see example below.

TRAFFIC CLASS DESCRIPTION

0 Only to operator
1 Internal traffic
Limited tie-line access
Abbreviated external traffic
2 Destinations of traffic class 1, plus:
Full tie-line access
More abbreviated dialled extensions
3 Destinations of traffic class 2, plus:
DDO to local area
More abbreviated dialled extensions
4 Destinations of traffic class 3, plus:
DDO to national destinations
More abbreviated dialled extensions
5 Destinations of traffic class 4, plus:
DDO to continental destinations
More abbreviated dialled extensions
6 No restrictions
7 Operator traffic class

TRUE OR FALSE
The new value of the option : 0 = false, 1 = true.

TRUNK-CODE
Trunk access code (1 ... 6 digits).

TS
Type and Subtype of a file.
T can be the following :
A = ASCII format
B = Binary format
L = Local data type
N = Network data type
S = System reserved
X = Executable file

S can be the following :

A = Action overlay
B = Backup library
C = Command overlay
D = Dump data
E = Compressed dump data
F = FDCR (Full Detailed Call Recording)
G = General data
I = PE initial file
J = Journal
K = Metering data

- 315 -
L = Backup location
M = Memory image
N = Compressed memory image
O = Traffic observation
P = Program library
Q = Sequence number
R = Resident set
S = Snapshot subcommands
T = Toll ticketing
U = Unit configuration

TYPE-CODE
Type code PQRSTU (for each letter: 0 = no, 1 = yes) :
P = Call forwarding on busy executive to secretary
Q = Secretary allowed to switch absent
R = Single executive pool
S = Single secretary pool
T = Busy indication in the case of executive and secretary busy
U = Executive line position pickup by related executives allowed

TYPE-OF-NUMBER
Type Of Number (TON) may have one of the following values :
0 = Unknown
1 = Subscriber (E.164) / Local (PNP)
2 = National (E.164) / Level 1 regional (PNP)
3 = International (E.164) / Level 2 regional (PNP)

U
Unit number (n=1 to 14).

UA
Displayed value, indicating the number of unanswered calls.

UCA
User Channel Address (1 ... 6 digits).

UCA-PREFIX
User Channel Address prefix (1 ... 20 digits).

UNIT
Unit number (0, 1 ... 14) : unit '0' means: the unit the OM terminal is connected to, or the 'own' unit.

UNIT+BUNDLE
Composite parameter of unit and bundle; format [UU]BBB.

UNIT+DEST
Local destination id [UU]DDD.

UNIT-INDICATOR
Indicates if a single unit or multi unit call should be observed :
0 = single unit call
1 = multi unit call

- 316 -
UNIT-T
Time unit (0 ... 4) :
0 = 10 msec
1 = 100 msec
2 = 1 sec
3 = 10 sec
4 = continuous

UNS-BIDS
Displayed value, indicating the total number of unsuccessful bids on a group or group members.

UP-TRFC
Upgraded traffic class : see parameter TRFC.

USER
This parameter is only applicable for AREA = 2 (OM command DIMEUS)
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
*) 31 = Display of SIP service data
4 = Display of pSOS info
5 = Display of the free blocks of heap
6 = Display of the SIP heap administration
*) marks sub-USER-related info

USE REFER
This parameter enables the "SIP Refer" method to transfer calls over a SIP trunk :
0 = No Refer
1 = Refer supported for inbound and outbound calls over a SIP trunk.

USER-ID
User-ID : 1 ... 6 characters.

USER-MODE
The user-mode specifies the answering mode of a PVN user channel :
0 = normal PVN (default)
1 = delayed PVN

USERNAME
This parameter defines the username that is applied during the registration process. It's specification is
identical to parameter <ROUTE-NAME>. In case it is left empty it is assumed that no authentication has to
be performed.

USRCH-TU
User channel timer unit : identifies the unit of the time value specified by parameter USRCH-TV :
0 = seconds
1 = minutes

USRCH-TV
User channel timer value (0 ... 16383).

- 317 -
USER-TYPE
Indicates for which type of user a routing table is valid :
0 = Normal extension
1 = Operator
2 = Priority extension

V24-CIRCUITS
V option (0 ... 14) or digit string ABCDEFGHIJ KL, each 0 or 1, to set the circuits individually : see table below.

V-OPTION 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
CT108-2 1 0 0 0 0 1 1 1 1 1 1 1 1 1 1
CT108-ON 0 0 0 0 0 0 0 1 1 0 0 1 1 1 1
CT105-CREQ 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
CT103-DCALL 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1
CT107-AUTON 1 0 0 1 1 0 0 0 0 1 1 1 1 0 0
AUTOM-ANSW 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
CT105-109 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
CT106-109-INH 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
CT105-ON 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1
DGUARD-ACT 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
DGUARD-INC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
V.25BIS 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

V-OPTION
If the circuits are filled in individually : 0 = off, 1 = on.

A CT108-2 : CT108 not as call request. CT108 set as 108.1 or 108.2. If this circuit is on it is used
as CT108.2 else it is used as C108.1 (call request).
B CT108-ON : If this option is chosen, CT108 is assumed permanently on, independent of the
actual state of the circuit.
C CT105-CREQ : This option allows CT105 to be used as a call request.
D CT103-DCALL : Activity on CT103 initiates a call request.
E CT107-AUTON : CT107 as call clear indication. CT107 may be turned off independent of the state
of CT108.
F AUTOM-ANW : Automatic answer on incoming call.
G CT105-CT109 : CT105 connected to CT109.
H CT106-CT109-INH : CT109 enables CT106.
I CT105-ON : CT105 is assumed continuously on, independent of the actual state of the circuit.
J DGUARD-ACT : No activity on CT103 or CT104 during certain time clears the call.
K DGUARD-INC : No data activity on incoming call within certain time clears the call.
L V.25BIS : V-interface working according to V.25bis.
In the case of X.21 : A= Autoclear, F=Auto answer.

VL-DESTINATION
DNR (not a group DNR and not an operator DNR) of the Voice Logging device.

- 318 -
VL-SUBJECT
DNR of extension or operator (not a group DNR) of the Voice Logged party.

VOICE/DATA
Voice data indication (V or D).

WA
Displayed value, indicating the number of waiting calls.

WAIT
Wait for completion of the delete operation : 0 = no, 1 = yes.

WINDOW
TMS (SSM/SysManager) service number (1 ... 9, 81 ... 89) : see note below.
Normally the following values are used, check this in the SystemManager documentation.
From the iS3000 to SystemManager :
81 = External Service Display (SysManager)
82 = Room Status
83 = Automatic entry of messages (SysManager)
84 = Night Watchman control
85 = Peripheral facility manager request
86 = Peripheral facility manager user-to-PFM
87 = Access manager
From TMS (SysManager) to the iS3000 :
02 = Wake up
03 = Message waiting without announcement (SysManager)
04 = Automatic Directory Dialling (SysManager)
05 = Change PBX data (SysManager) (bar/unbar, DND, PID)
06 = Message waiting with announcement / security patrol manager alarm (SSM/SysManager)
07 = Peripheral facility manager-to-user
08 = Port protection call back

Note : The window numbers in the OM command are in hexadecimal. Window numbers in the
subcommands are in decimal. For example, hexadecimal window number 81 corresponds to window
number 129 in decimal.

WINDOW-SIZE
The number of simultaneous processes sent to the TMS (SysManager) (0 ... 254).

YEAR
Year (1985 ... 2099).

- 319 -
C. BOARD AND PCT TYPES
C.1. BOARD - TYPES

The table below lists all the boards. The board-type is not mentioned if it can not be projected by ASBRDS
(like PSU, LTU etc.) The signalling group, mentioned in this table, corresponds to the application. Other
applications with corresponding signalling groups can be found in the Signalling Data Manual. The PCT-
TYPE used by the application is in the "PCT-TYPES ON BOARD" column. The mode of operation for individual
circuits can be changed to a PCT-TYPE, which is mentioned between square brackets, by first DEPCTB and
subsequently ASPCTB.
PCT-TYPES are discussed in section C.2. PCT-TYPES.

CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS

TYPE GROUP TYPE BOARD
ACC 08 3205 35 LCT Extension
[TRC/MOH/Ann]
ACU (APNSS) APNSS-board
ALC-Axx 03 3204 35 LCT [MOH/Ann] Extension
ALC-Bxx 03 3204 35 LCT [MOH/Ann] Extension
ALC-Exx 06 3205 35 LCT [MOH/Ann] Extension
ALC-Fxx/G 06 3204 35 LCT [MOH/Ann] Extension/clearing signal
ALC-Fxx/G 06 3210 35 LCT [MOH/Ann] Extension/Message-Waiting LED

ALC-GM with 59 321C 255 LCT [MOH/Ann] Extension/Message-Waiting LED

daughter board
ALC-GD
ALC-GM with-out 06 3210 255 LCT [MOH/Ann] Extension/Message-Waiting LED
daughter board
ALC-GD
AOC on PMC 0A04 255 [OCT]
AS01 on ACC01 3304 35 [TRC] ALS70
AS0B on ACC0B 3304 35 [TRC] ALS70
ASU-G 06 9B17 255 Standard board 16 lines
ASU-G 06 3Exx 255 [TRC] Subscriber Signalling
ASU-G 06 3Exx 255 [TRC] PD Signalling
ATU-AS01 22 3304 35 TRC ALS70
ATU-AS01 22 3704 35 TRC Eind-Overdrager
ATU-AS0B 22 3304 35 TRC ALS70
ATU-AS11 22 3704 35 TRC Eind-Overdrager
ATU-AS36 22 3F04 35 TRC Austria enhanced SS
ATU-AS48 22 4904 35 TRC French DDO
ATU-CH01 22 3404 255 TRC Cailho
ATU-CH02 22 3804 35 TRC German Cailho

- 320 -
CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS
TYPE GROUP TYPE BOARD
ATU-DI13 24 4104 255 TRC United Kingdom DDI
ATU-EL03 24 4204 35 TRC EC and loop disconnect
ATU-EM 35 5F04 255 TRC External alarm
ATU-EM-D 22 3604 35 TRC Digital data + EM
ATU-EMxx 22 35 *) TRC 1 bit protocol
See Table C-2 1-Bit Protocols
22 7704 35 *) TRC Italy EM
22 7604 35 *) TRC Spain EM
ATU-G 24 3304 35 TRC ALS70
24 3704 35 TRC Eind-Overdrager
24 3E04 35 TRC SS
ATU-G2 24 4604 35 TRC PDO Sweden
24 3E0C 35 TRC SS Sweden
24 7804 35 TRC PD2 New Zealand
ATU-G3 1) 24 3E1A 35 TRC PD1 Spain
24 3E16 35 TRC SS Germany
24 3E04 35 TRC SS China
24 3E04 35 TRC SS South Africa
24 4706 35 TRC SS France
ATU-G3 2) 24 3E04 35 TRC SS0
24 3E0C 35 TRC PD1
24 3304 35 TRC ALS70
24 3704 35 TRC AS0/AS2 Eind-Overdrager
24 3E1A 35 TRC PD1C Spain
24 4706 35 TRC SS08 France
ATU-G4 24 3E04 35 TRC SS01/AS2D Italy
24 3704 35 TRC AS21/AS2D Italy
ATU-G5 24 3E04 35 TRC SS0M Brazil
24 3E0C 35 TRC PD1M Brazil
24 3704 35 TRC AS0M Brazil
ATU-G6 24 3E1F 35 TRC SS02 Germany
ATU-IL31 22 4A04 255 TRC China
ATU-ILxx 22 See table 35 *) TRC 1 bit protocol
C-2. See table C-2.
ATU-LB01 22 3A04 255 TRC Local battery
ATU-LB12 22 See table 35 *) TRC 1 bit protocol
C-2. See table C-2.

- 321 -
CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS
TYPE GROUP TYPE BOARD
ATU-LD28 22 4804 35 TRC French DDI
ATU-LDxx 22 3B04 35 TRC Loop-diconnect (SS-DC5)
ATU-PA 30 3D04 255 Paging Circuit Paging
ATU-PD05 22 450B 35 TRC Denmark polarity detect
ATU-PD07 22 4604 35 TRC Sweden polarity detect
ATU-PD11 22 3E04 35 TRC Polarity detection
ATU-PDx8 24 4704 35 TRC French polarity detection
ATU-PSI 20 3E04 255 TRC Analoge door-contact
ATU-SS02 22 3E04 35 TRC SS
ATU-SSxx, not 02 23 3E04 35 TRC SS
ATU-ST02 2 ports 21 3904 35 TRC German IKZ
ATU-ST02 4 ports 22 3904 35 TRC German IKZ
ATU-ST03 22 4304 255 TRC United Kingdom DC10
ATU-ST12 2 ports 21 3C04 35 TRC Luxembourg IKZ
ATU-ST12 4 ports 22 3C04 35 TRC Luxembourg IKZ
ATU-ST26 22 4004 35 TRC Austria 3 wire Signalling
ATX (APNSS) -- ---- --- APNSS
ATU-EC03 22 3504 35 TRC Earth-Calling (EC)
CCS 88 ---- ---
CFC 24 0E04 255 TRC Conference circuit
03 0E05 255 LCT Conference circuit
CIE 89 ---- ---
CPU3000 86 ---- ---
CSN-BC 75 ---- ---
DCC 16 6204 255 LCT DECT, BB-section 0
16 6205 255 LCT DECT, BB-section 1
16 6206 255 LCT DECT, BB-section 2
16 6207 255 LCT DECT, BB-section 3
DCC-8 13 6204 255 LCT DECT, BB-section 0
13 6205 255 LCT DECT, BB-section 1
13 6206 255 LCT DECT, BB-section 2
13 6207 255 LCT DECT, BB-section 3
DLC-A 02 2804 4 *) LCT 2 wire Us-interface TMP
DLC-B 04 2806 4 *) LCT 2 wire Us-interface TMP
DLC-C 05 2807 255 LCT [OCT] 2 wire Us-interface TMP
DLC-D 07 2808 255 LCT [OCT] 2 wire Us-interface TMP

- 322 -
CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS
TYPE GROUP TYPE BOARD
DLC-I 05 0904 255 LCT 4 wire S0-bus TMP/1TR6
DLC-U (15) 10 0912 255 LCT [OCT] TMP/1TR6+take-over/ETSI

DLC-U (15) 10 090A 255 LCT [OCT] 2w, TMP/1TR6/ETSI

DLC-U (7) 12 090F 255 LCT [OCT] 2w, TMP/1TR6/ETSI
DLX-L (15) 64 0930 255 LCT 2w (2B1Q), TMP/1TR6, ETSI
(15 ports)
DLX-L (15) 30 65 090A 255 LCT 2w (2B1Q), TMP/1TR6, ETSI
ports
DLX-U (15) 15 67 0930 255 LCT 2w (Upn), TMP/1TR6
ports
DLX-U (15) 30 68 090A 255 LCT 2w (Upn), TMP/1TR6
ports
DLX-U (31) 31 69 0931 255 LCT 2w (Upn), TMP/1TR6
ports
DOC on PMC -- 1904 255 [OCT]
DTA 00 3204 35 LCT Digital Test Access
DTU-BA 26 6605 255 TRC 2B+D DPNSS, B side
26 6604 255 TRC 2B+D DPNSS, A side
28 5C04 255 ISDN-TRC 2B+D 1TR6
DTU-CC 50 2004 48
DTU-G strapped See Maintenance Manual Part 3 (Board Interfaces & Strap Settings). For board type and
and used as signalling group : see DTU-PH below. Always use hardware type 255. DTU-G can be
replacement of a used in all shelves, except an (R)PM2500.
DTU-PH
DTU-G strapped See Maintenance Manual Part 3 (Board Interfaces & Strap Settings). For board type and
and used as signalling group : see DTU-PU below. Always use hardware type 255. DTU-G can be
replacement of a used in all shelves, except an (R)PM2500.
DTU-PU
DTU-PH 18 5D0D 255 ISDN-TRC 30B+D ETSI International, free
numbering
18 5D20 255 QSIG-TRC QSIG, User side
18 5D21 255 QSIG-TRC QSIG, Network side
19 6705 255 TRC/D-Channel 30B+D DPNSS, B side
19 6704 255 TRC/D-Channel 30B+D DPNSS, A side
19 6708 255 TRC/D-Channel 30B+D DASS
DTU-PU as 25 3004 49 *) TRC Belgium
DTU-CA
25 See table 49 *) TRC 1 bit protocol
C-2. See table C-2.
25 2B04 49 *) TRC Italy

- 323 -
CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS
TYPE GROUP TYPE BOARD
25 2D04 49 *) TRC France
25 2C04 49 *) TRC Sweden
25 2E04 49 *) TRC South Africa
25 2904 49 *) TRC Netherlands (ALS70)
25 3104 49 *) TRC Denmark
25 5004 49 *) TRC Thailand
25 5304 49 *) TRC China
25 2F04 49 *) TRC South Africa outgoing
25 5204 49 *) TRC Spain
25 5504 49 *) TRC Czech Republic
25 5604 49 *) TRC Brazil
25 5404 49 *) TRC Greece
DTU-PU as 50 2004 48 in (R) PM2500
DTU-CC
DTU-PU as 25 2605 50 *) TRC DPNSS, A-side
DTU-PR
25 2606 50 *) TRC DPNSS, B-side
25 2608 50 *) TRC DASS
DTU-PU remote 52 5904 255 in RPM1100/255
CC (UG7/6/5/4)
DTU-PU/2 local 51 5904 48 See row below
CC
in a CCS system : in PM1100 in the even PCT positions, except 16.
in the PM part of the CSM shelf : in all PCT positions.
since SIP@Net 4.1 : in all positions except 16 in a PM1100 and PM 19 inch
53 5904 255 CPU3000 system
(UG0/3/4/5)
DTU-VC 17 660C 255 TRC [LCT] DPNSS, A-side
17 660D 255 TRC [LCT] DPNSS, B-side
DTU-VC + TRK-VC 17 660C 255 TRC DPNSS, A-side
17 660D 255 TRC DPNSS, B-side
DTX-I(R) (15) 14 09xx 255 LCT S0-bus
[TRC/OCT/ISDN-
TRC]
27 6610 255 ISDN-TRC DPNSS, A-side
27 6611 255 ISDN-TRC DPNSS, B-side
29 5Cxx 255 ISDN-TRC ISDN
28 5C20 255 QSIG-TRC QSIG, User side
28 5C21 255 QSIG-TRC QSIG, Network side

- 324 -
CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS
TYPE GROUP TYPE BOARD
DTX-I(R) (7) 11 09xx 255 LCT S0-bus
[TRC/OCT/ISDN-
TRC]
26 660C 255 ISDN-TRC DPNSS, A-side
26 660D 255 ISDN-TRC DPNSS, B-side
28 5Cxx 255 ISDN-TRC ISDN
28 5C20 255 QSIG-TRC QSIG, User side
28 5C21 255 QSIG-TRC QSIG, Network side
ESU (-LG) /MCE 34 1E04 64 Emergency switching
IAS as IAS-A 14p 05 2807 255 LCT [MOH/Ann]
IAS as IAS-A 30p 09 280D 255 LCT [MOH/Ann]
IAS 14p 57 7B04 255 LCT, IAS-TS [MOH] IAS 14 ports
IAS 30p 56 7B05 255 LCT, IAS-TS [MOH] IAS 30 ports
INC -- ---- ---
IPH-A -- ---- ---
IPH-B 31 2504 255 D-channel DPNSS/DASS
ISG / IPG 18 5D21 255 In System Gateway /
IPG part of the PMC-IP
KTLC 8/A 03 2304 35 LCT 4 wire analoge set
KTLC-E 06 2305 35 LCT 4 wire analoge set
LDC -- ---- ---
LTU-(C/F) -- ---- ---
MC -- ---- ---
MCE See ESU
MLU convertor 33 1604 255 Convertor [TRC]
MLU leased Line 22 1604 255 TRC [convertor]
MOH-I -- ---- ---
OIU 32 1706 255 OCT Supervisor
PM-observer 36 090A 255
PMC-HR/PMC-G/ 90 0B04 255 RKT-SDT/
PMC-SIC/PMC-IP SKT-RDT
[OCT/HATCH]
PMC-LU 93 0B04 255 RKT-SDT/
SKT-RDT
[OCT/HATCH]
PMC-MC/PMC-G 91 0B04 255 RKT-SDT/
PMC-SIC/PMC-IP SKT-RDT
(slave) [OCT/HATCH]

- 325 -
CIRCUIT NAME BOARD SIGN. HARDW PCT-TYPES ON APPLICATIONS
TYPE GROUP TYPE BOARD
PMC-MC/PMC-G/ 92 0B04 255 RKT-SDT/
PMC-SIC/PMC-IP SKT-RDT
(master) [OCT/HATCH]
PSC 94 ---- ---
PSU-ML (D)/F -- ---- ---
RST-IM 41 1504 82 IN-MFC
RST-KDxx 40 1404 255 RKT-SDT/
SKT-RDT
RST-OM 43 150A 83 OUT-MFC
RST-SL 42 1C04 81 RS-Socotel Socotel France
42 2104 80 RS-Socotel Socotel Spain
SNS 77 ---- ---
SS01 on ACC01 -- 3E04 35 [TRC] Eind overdrager
SS0B on ACC0B -- 3E04 35 [TRC] Eind overdrager
Virtual PCT 37 0101 255 LCT IP enabling and SMA
Virtual SMA 38 0201 255 LCT SMA
Virtual SIP Trunk 44 B0xx 255 TRC SIP
board
Virtual SIP 39 B0xx 255 LCT SIP
Extension board
VPU -- ---- ---
1) 9562 158 81000
2) 9562 158 81100
*) Note: These hardware test types only apply to the PM2500, use type 255 for other types of PM.

Table C-1 Various Types of Boards

- 326 -
PPU MODULE-TYPE SIGNALLING GROUP REMARKS
ATU-EM 3604 EM General
ATU-EM-AS 7304 France EM-AS
ATU-EM-LD 7404 France EM-LD
ATU-EM2-PULSE 7004 EM pulse protocol
ATU-EM3 6F04 Sweden IF3 and Brasil
ATU-EM4 6E04 Sweden IF4
ATU-EM5 6D04 Sweden IF5
ATU-EM6 6C04 Sweden IF6
ATU-EM7 6B04 Sweden IF7
ATU-EM8 6A04 Sweden IF8
ATU-EMF 7204 France
ATU-EMG 7504 Germany

Table C-2 1-Bit Protocols

C.2. PCT-TYPES

C.2.1 Line Circuit (LCT)

ACC/ALC-Axx/ALC-E/ALC-Bxx
Signalling Group Remarks
3204 Enquiry by earth button, no auxiliary pulse detect (8 lines).
3205 Enquiry by earth button, no auxiliary pulse detect (16 lines).
3206 Enquiry by dial-one or auxiliary pulse.
3207 Enquiry by dial-one or auxiliary pulse and Special timing for Spain
3208 Enquiry by hook flash.
320A Enquiry by dial-one or auxiliary pulse.
320C Enquiry by dial-one.
3216 Enquiry by aux. loop swedish signalling.
3218 Enquiry by aux. loop or enquiry digit [0].
321A Enquiry by aux. loop or enquiry digit [0] swedish signalling.

ALC-F/ALC-G
Signalling Group Remarks
3205 Enquiry by earth button, no auxiliary pulse detect.
Polarity reverse used to indicate release.
3207 Enquiry by dial-one or auxiliary pulse and Special timing for Spain
Polarity reverse used to indicate release.
3210 French signalling
Polarity reverse used to indicate release.
3216 Enquiry by aux. loop Swedish Signalling.
Polarity reverse used to indicate release.
321A Enquiry by aux. loop or enquiry digit [0] Swedish signalling.
Polarity reverse used to indicate release.

- 327 -
CFC
Signalling Group Remarks
0E05 Conference circuit as line circuit

DCC
See Table C-1 Various Types of Boards

DLC-A/B/C/D
Signalling Group TMP
2804 level : English
Language : English
280A level : Dutch
Language : Dutch
280C modem converter function

DLX-L
Signalling Group Remarks
090A DLX-L (15) in 2B mode
0930 DLX-L (15) in 1B mode
0908 ... 090B+ DLX-L (15) in 2B mode if the DLX-L is used to substitute the DLX-U, DLC-U or DTX-I.
0910 ... 0917 Note : The DLX-L offers a different extension interface as the DLX-U, DLC-U and DTX-I.
Therefore it cannot be used as a one-to-one replacement of the DLX-U, DLC-U
and DTX-I.

DLX-U
Signalling Group Remarks
090A DLX-U(15) in 2B mode
0930 DLX-U(15) in 1B mode
0931 DLX-U(31) in 1B mode
0908 ... 090B + DLX-U(15) in 2B mode if the DLX-U is used to substitute the DLC-U or DTX-I.
0910 ... 0917 Note : The DLX-U offers a different extension interface as the DLC-U and DTX-I.
Therefore it cannot be used as a one-to-one replacement of the DLC-U and DTX-I.

DTA
Signalling Group Remarks
3204 DTA circuit

DTU-VC without TRK-VC

Signalling Group Remarks
6614 passive side (automatic answer calls)
6615 active side (generate Call-request)

DTX-I (DLC-I and DLC-U

Signalling Group 0904
Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : NET33
Language : German
Download possible : NO

- 328 -
Signalling Group 0905
Port Application : Layer-1 : Short passive bus
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : NET33
Language : German
Download possible : NO

Signalling Group 0906

Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : NO

Signalling Group 0907

Port Application : Layer-1 : Short passive bus
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : NO

Signalling Group 0909

Port Application : Layer-1 : Remote extension
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : NET33
Language : German
Download possible : YES

Signalling Group 090A

Download possible : YES
Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 090B

Port Application : Layer-1 : Remote extension
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 090C

Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

- 329 -
Signalling Group 090D
Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Dutch
Language : Dutch
Download possible : NO

Signalling Group 090E

Port Application : Layer-1 : Short passive bus
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Dutch
Language : Dutch
Download possible : NO

Signalling Group 090F

Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0910

Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Modem converter function : On
Download possible : YES

Signalling Group 0911

Port Application : Layer-1 : Remote extension
Layer-3 : Call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0912

Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : Call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0913

Port Application : Layer-1 : Short passive bus
Layer-3 : Call handover, Automatic MSN generation (ETSI)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

- 330 -
Signalling Group 0914
Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : No call handover, No automatic MSN generation
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0915

Port Application : Layer-1 : Short passive bus
Layer-3 : No call handover, No automatic MSN generation, (ETSI extensions)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0916

Port Application : Layer-1 : Extended passive bus or point-to-point
Layer-3 : Call handover, No automatic MSN generation
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0917

Port Application : Layer-1 : Short passive bus
Layer-3 : Call handover, No automatic MSN generation, (ETSI extensions)
TMP Application : Transm. level : Terminal setting
Language : Terminal setting
Download possible : YES

Signalling Group 0928

Port Application : QSIG basic rate – User Side : SMA Access Number
Download possible : YES

Signalling Group 0929

Port Application : QSIG basic rate – Network Side : SMA Personal Number
Download possible : YES

IAS (14/30 ports)

See Table C-2 1-Bit Protocols.
Only CCT '1' can have PCT-type 'LCT'.

IAS-A (14/30 ports)

See Table C-2 1-Bit Protocols

- 331 -
C.2.2. Trunk Circuit (TRC)

ASU-G
Signalling Group Remarks
9B17 Signalling Group of the ASU-G board-16 lines.
3Exx Subscriber signalling (Signalling Group per PCT)
3Exx Polarity Detect signalling (Signalling Group per PCT)

TU-AS01 on ACC01 / TU-AS0B on ACC0B

Signalling Group Remarks
3304 ALS70

ATU-AS01 / ATU-AS0B
Signalling Group Remarks
3304 ALS70
3704 Eind-Overdrager

ATU-AS11
Signalling Group Remarks
3704 Eind-overdrager

ATU-AS36
Signalling Group Remarks
3F04 Austria enhanced SS

ATU-AS48
Signalling Group Remarks
4904 French DDO

ATU-AS36
Signalling Group Remarks
3F04 Austria enhanced SS

ATU-AS48
Signalling Group Remarks
4904 French DDO

ATU-CH01
Signalling Group Remarks
3404 Cailho

ATU-CH02
Signalling Group Remarks
3804 German Cailho

ATU-DI13
Signalling Group Remarks
4104 United Kingdom DDI

ATU-EC03
Signalling Group Remarks
3504 Earth-Calling

- 332 -
ATU-EL03
Signalling Group Remarks
4204 EC and loop disconnect

ATU-EM
Signalling Group Remarks
3604 EM general
7304 France EM-AS
7404 France EM-LD
7004 EM pulse protocol
6F04 Sweden IF3 and Brasil
6E04 Sweden IF4
6D04 Sweden IF5
6C04 Sweden IF6
6B04 Sweden IF7
6A04 Sweden IF8
7204 France 1bit
7504 Germany 1bit
7604 Spain EM
7704 Italy EM

ATU-G
Signalling Group Remarks
3304 ALS70
3704 Eind-Overdrager
3E04 SS0

ATU-G2
Signalling Group Remarks
7804 New Zealand PD23
4604 Sweden PD0
3E0C Sweden SS0

ATU-G3 (9562 158 81000)

Signalling Group Remarks
3E1A Spain PD1
3E16 Germany SS
3E04 SS0
4706 France SS08

ATU-G3 (9562 158 81100)

Signalling Group Remarks
3E04 SS0
3E0C PD1
3304 ALS70
3704 AS0/AS2 Eind-Overdrager
4706 SS08 France
3E1A PD1C Spain

ATU-G4
Signalling Group Remarks
3E04 SS01/SS0D Italy
3704 AS21/AS2D Italy

- 333 -
ATU-G5
Signalling Group Remarks
3E04 SS0M Brazil
3E0C SS01/SS0D Italy
3704 AS21/AS2D Italy

ATU-G6
Signalling Group Remarks
3E1F SS02 Germany

ATU-IL31
Signalling Group Remarks
4A04 China IL

ATU-ILxx
Signalling Group Remarks
3604 EM general
7304 France EM-AS
7404 France EM-LD
7004 EM pulse protocol
6F04 Sweden IF3 and Brasil
6E04 Sweden IF4
6D04 Sweden IF5
6C04 Sweden IF6
6B04 Sweden IF7
6A04 Sweden IF8
7204 France 1bit
7504 Germany 1bit

ATU-LB01
Signalling Group Remarks
3A04 Local Battery

ATU-LB12
Signalling Group Remarks
3604 EM general
7304 France EM-AS
7404 France EM-LD
7004 EM pulse protocol
6F04 Sweden IF3 and Brasil
6E04 Sweden IF4
6D04 Sweden IF5
6C04 Sweden IF6
6B04 Sweden IF7
6A04 Sweden IF8
7204 France 1bit
7504 Germany 1bit

ATU-LD28
Signalling Group Remarks
4804 French DDI

- 334 -
ATU-LDxx
Signalling Group Remarks
3B04 Loop disconnect (SS-DC5)

ATU-PDx8
Signalling Group Remarks
4704 French polarity detection

ATU-PD05
Signalling Group Remarks
450B Denmark polarity detection

ATU-PD07
Signalling Group Remarks
4604 Sweden polarity detection

ATU-PD11
Signalling Group Remarks
3E04 Polarity detection

ATU-PSI / ATU-SSxx
Signalling Group Remarks
3E04 SS

ATU-ST02 with 2 ports and/or 4 ports

Signalling Group Remarks
3904 German IKZ

ATU-ST03
Signalling Group Remarks
4304 United Kingdom DC10

ATU-ST12 2 ports, 4 ports

Signalling Group Remarks
3C04 Luxembourg IKZ

ATU-ST26
Signalling Group Remarks
4004 Austria 3 wire signalling

CFC
Signalling Group Remarks
0E04 Conference circuit as trunk circuit

DTX-I
Signalling Group Remarks
5C09 1TR6
5C12 ETSI, free numbering
5C20 'real' QSIG, User side
5C21 'real' QSIG, Network side
6610 DPNSS, A-side (NT / direct)
660C DPNSS, A-side (TE / via public)
660D DPNSS, B-side (TE)

- 335 -
DTU-PH
Signalling Group Remarks
5D0D 30B+D, ETSI, International, free numbering
5D20 30B+D, QSIG, User side
5D21 30B+D, QSIG, Network side
6705 30B+D DPNSS, B-side
6704 30B+D DPNSS, A-side
6708 30B+D DASS

DTU-PU as DTU-CA
Signalling Group Remarks
3604 EM general
7304 France EM-AS
7404 France EM-LD
7004 EM pulse protocol
6F04 Sweden IF3 and Brasil
6E04 Sweden IF4
6D04 Sweden IF5
6C04 Sweden IF6
6B04 Sweden IF7
6A04 Sweden IF8
7204 France 1bit
7504 Germany 1bit
2904 Channel associated (Netherlands (ALS70))
2B04 Channel associated (Italy)
2C04 Channel associated (Sweden)
2D04 Channel associated (France)
2E04 Channel associated (South Africa)
2F04 Channel associated (South Africa outgoing)
3004 Channel associated (Belgium)
3104 Channel associated (Denmark)
5004 Channel associated (Thailand)
5204 Channel associated (Spain)
5304 Channel associated (China)
5404 Channel associated (Greece)
5504 Channel associated (Czech Republic)
5604 Channel associated (Brazil)

DTU-VC with TRK-VC

Signalling Group Remarks
660C DPNSS, A side
660D DPNSS, B side

TU-SS on ACC01, TU-SS0B on ACC0B

Signalling Group Remarks
3E04 Eind overdrager

- 336 -
C.2.3. RKT-SDT

PMC
Signalling Group Remarks
0B04 Receiver key tone, sender dial tone

RST-KDxx
Signalling Group Remarks
1404 Receiver key tone, sender dial tone

C.2.4. RDT-SKT

PMC
Signalling Group Remarks
0B04 Receiver dial tone, sender key tone

RST-KDxx
Signalling Group Remarks
1404 Receiver dial tone, sender key tone

RST-KD18
Signalling Group Remarks
1404 Receiver dial tone, sender key tone
1405 Receiver dial tone with long (1.2 s) recognition time and sender key tone
1406 Receiver dial tone, sender key tone and receiver ring tone/busy tone for transcom

C.2.5. Operator Circuit (OCT)

Signalling Group Board-Name PPU Module-Type

0A04 AOC on PMC-HR/MC/LU - with SV20 or SV25 AOC
0A05 AOC on PMC-HR/MC/LU - with SV50 AOC
1905 DLC-C/D - with PNT1-SV25 or 35 SuperVisor-30
1904 DLC-C/D - with SV30 SuperVisor-30
6404 DLC-U (15)/(7) - with PNT1-SSV60 SuperVisor-60
6005 DLC-U (15)/(7) - with PNT1-SV25 or SV35 SuperVisor-1TR6
6004 DLC-U (15)/(7) - with PNT1-SV55 SuperVisor-1TR6
5B04 DLC-U (15)/(7) - with SV30 SuperVisor-30-D
6404 DLX-U/L - with PNT1/L - SV60 SuperVisor-60
6005 DLX-U/L - with PNT1/L - SV25 or SV35 SuperVisor-1TR6
6004 DLX-U/L - with SV55 SuperVisor-1TR6
1905 DOC on PMC-HR/MC/LU - with PNT1 - SV25 SuperVisor-30
1904 DOC on PMC-HR/MC/LU - with PNT1 - SV30 SuperVisor-30D
6004 DOC on PMC-HR/MC/LU - with SV55 SuperVisor-1TR6
6004 DTX-I(R) (15)/(7) - with SV55 SuperVisor-1TR6
6005 DTX-I(R) (15)/(7) - with SV25 or SV35 SuperVisor-1TR6
6404 DTX-I(R) (15)/(7) - with SV60 SuperVisor-60
1706 OIU - with SV20 or SV25 or SV50 OIU
7D04 PMC-G - with SV25 or SV35 SuperVisor-1TR6

For all configurations HARDW-TYPE 255 has to be specified.

- 337 -
C.2.6. In-MFC

RST-IM
Signalling Group Remarks
1504 Transmission plan 01, CSS1 signalling
1505 Transmission plan 02, CSS1 signalling
1506 Transmission plan 03, CSS1 signalling
1507 Transmission plan 04, CSS1 signalling
1508 Transmission plan 05, CSS1 signalling
1509 Transmission plan 06, CSS1 signalling

C.2.7. Out-MFC

RST-OM
Signalling Group Remarks
150A Transmission plan 01
CSS1 signalling, without backward signals for repetition
150B Transmission plan 02
CSS1 signalling, without backward signals for repetition
150C Transmission plan 03
CSS1 signalling, without backward signals for repetition
150D Transmission plan 04
CSS1 signalling, without backward signals for repetition
150E Transmission plan 05
CSS1 signalling, without backward signals for repetition
150F Transmission plan 06
CSS1 signalling, without backward signals for repetition
1510 Transmission plan 01
CCITT-R2 signalling for Indonesia, with:
- Backward A signal A5 = switch through
- Backward A signal A8 = repeat last but 1 digit
- Backward A signal A9 = repeat last but 2 digit
1511 Transmission plan 01
CCITT-R2 signalling for Brunei, with:
- Backward A signal A5 = switch through
- Backward A signal A7 = repeat last digit
- Backward A signal A8 = repeat last but 1 digit
- Backward A signal A9 = repeat last but 2 digit
1512 Transmission plan 01
CCITT-R2 signalling for Poland, with:
- Backward A signal A6 = switch through
- Backward A signal A7 = repeat last but 2 digit
- Backward A signal A8 = repeat last but 3 digit

C.2.8. Paging Circuit

ATU-PA
Signalling Group Remarks
3D04 Paging

- 338 -
C.2.9. RS-Socotel

RST-SL
Signalling Group Remarks
1C04 Socotel France phase 2
1C04 Socotel France phase 3
2104 Socotel Spain:
- double frequencies: two out of five
- control frequency =1700 Hz.
2105 Socotel Spain:
- double frequencies: two out of six
- control frequency =1900 Hz.

C.2.10. Music on Hold (MOH) / Music on COB / Wake-up/MW Announcement Circuit

ACC with/without MOH-I, ALC-A/B/C/F/G with/without MOH-I

Signalling Group Remarks
320E Operation with open/close loop
2204 Operation with close loop, open loop causes alarm, clearing of alarm after manual action
on OM interface
2205 Operation with close loop, open loop causes alarm, automatic alarm clearing on close
loop

IAS with IAS firmware

Remarks
See Table C-1 Various Types of Boards.
Except circuit number 1

IAS with IASA firmware

Remarks
See Table C-1 Various Types of Boards.

C.2.11. D-channel

DTU-PH for DPNSS/DASS firmware (port number 16)

Remarks
See Table C-1 Various Types of Boards.

IPH-B
Remarks
See Table C-1 Various Types of Boards.

- 339 -
C.2.12. Trunk circuit ISDN (TRC-ISDN)

DTU-PH with 1TR6 firmware

Signalling Group Remarks
5D04 User side, 1TR6 (PSI=H'03)
5D05 Network side, 1TR6 (PSI=H'12)
5D06 User side, 1TR6 (PSI=H'13)

DTU-PH for VN2

Signalling Group Remarks
5D07 User side, VN6 (PSI=H'23)

DTU-PH for ETSI

Signalling Group Remarks
5D09 User side, ETSI (PSI=H'33), Belgium
5D0A User side, ETSI (PSI=H'37), Switzerland
5D0B User side, ETSI (PSI=H'67), Germany
5D0C User side, ETSI (PSI=H'35), Italy
5D0D User side, ETSI (PSI=H'6B) for free numbers
5D0E User side, ETSI (PSI=H'6D) for free numbers
5D20 User side, QSIG
5D21 Network side, QSIG

DTX-I for 1TR6/ETSI

Signalling Group Remarks
5C04 User side, 1TR6, Germany
5C05 Network side, 1TR6-tieline
5C06 User side, 1TR6-tieline
5C0D User side, ETSI-Netherlands
5C0E User side, ETSI-Belgium
5C0F User side, ETSI-Switzerland
5C10 User side, ETSI-Germany
5C11 User side, ETSI-Italy
5C12 User side, ETSI (PSI=H'6A) for free numbers
5C13 User side, ETSI (PSI=H'6C) for free numbers
5C20 User side, QSIG
5C21 Network side, QSIG

C.2.13. IAS-TS

IAS with IAS firmware

Signalling Group Remarks
See Table C-1 Various Types of Boards.

C.2.14. HATCH

PMC
Signalling Group Remarks
6104 Hatch

- 340 -
D. OVERVIEW OF OM COMMANDS
ACIPPD ...................... 105 AUBUFI ........................ 23 CHFRCR ..................... 184
ACLICS ....................... 113 BMLOCK ...................... 20 CHFROD .................... 184
ACTRBU ....................... 81 CALSIG ......................... 63 CHFSTA ....................... 69
ASACLI ......................... 89 CANJOB ....................... 33 CHFTLD ..................... 214
ASAPPF...................... 144 CANLDM .................... 119 CHFTLI ....................... 214
ASBARR ..................... 134 CHABNR....................... 17 CHGRDN...................... 71
ASBLCK ...................... 132 CHACDD ...................... 71 CHHOOT.................... 128
ASBNDL ..................... 210 CHACIV ...................... 174 CHHOTL....................... 86
ASBRDS ....................... 76 CHAGCV....................... 18 CHIABD ....................... 87
ASBRVC ....................... 80 CHANNO ...................... 92 CHIBNC ....................... 94
ASBSPB...................... 211 CHAQPR..................... 135 CHINEX ...................... 128
ASBSPR...................... 210 CHASCV ..................... 138 CHIPPD ...................... 102
ASCANS ..................... 128 CHASOP ..................... 138 CHIPPR ...................... 100
ASCONV ...................... 36 CHASPR ..................... 138 CHIPSG ........................ 77
ASCRUE ....................... 79 CHAUCO .................... 123 CHIPUS ........................ 97
ASCSVR ..................... 222 CHBBUT ..................... 135 CHJOUR....................... 21
ASCVCT ....................... 36 CHBDNR ...................... 46 CHLCDF ..................... 121
ASDEVC ....................... 81 CHBDST ....................... 76 CHLCID ...................... 121
ASDGCO .................... 207 CHBDTU ..................... 211 CHLDCT ..................... 120
ASDGCV..................... 206 CHBNDC..................... 210 CHLDOM ................... 155
ASDICA ...................... 182 CHBOUN ...................... 27 CHLODD .................... 158
ASEXSE ........................ 56 CHBSPT ........................ 88 CHMCNE ................... 128
ASEXTN ..................... 134 CHCALF ........................ 30 CHMDNR..................... 68
ASEXTP ...................... 134 CHCASC ..................... 122 CHMQPR ................... 136
ASFACM ...................... 59 CHCCLI ....................... 213 CHMSNP ................... 124
ASFATI ......................... 61 CHCCTR ..................... 207 CHNAME ................... 125
ASGECA ....................... 69 CHCDED ..................... 212 CHNPCD .................... 159
ASGRPM ...................... 70 CHCLID......................... 52 CHOPAV .................... 137
ASIABD ........................ 87 CHCOBD ...................... 31 CHOPDC ...................... 45
ASIBND ........................ 94 CHCOMP...................... 26 CHOPTI........................ 28
ASILIN.......................... 94 CHCQPR ..................... 136 CHOVEX .................... 129
ASINTN ...................... 132 CHCSDD ..................... 133 CHPAMD ................... 143
ASLDNM ...................... 83 CHCVAL ....................... 35 CHPANL..................... 143
ASLINE ....................... 212 CHCVAP ....................... 52 CHPARE ..................... 142
ASLINK......................... 84 CHCVCA ....................... 35 CHPASS ..................... 176
ASNOIT ........................ 53 CHCVMH...................... 93 CHPATM.................... 179
ASPACD ..................... 143 CHDEAU..................... 175 CHPCDR ...................... 32
ASPALN ..................... 143 CHDEPR ..................... 175 CHPCID........................ 32
ASPCTB........................ 78 CHDEVA ....................... 83 CHPCTB ....................... 78
ASPICC....................... 145 CHDFCM ...................... 60 CHPDFS ..................... 148
ASPORT ....................... 82 CHDNRA ...................... 89 CHPDOD.................... 147
ASPVNU .................... 151 CHDNRC....................... 45 CHPERD..................... 188
ASRTDN ..................... 209 CHDNRL ..................... 157 CHPICC ...................... 145
ASSADN ....................... 38 CHDNRS ....................... 18 CHPLEX...................... 129
ASSCID ...................... 167 CHDSTC ..................... 204 CHPMFU ................... 160
ASSHLF ........................ 75 CHDTSS ........................ 51 CHPMPD ................... 153
ASTMOB .................... 197 CHEPLE ...................... 214 CHPORT ...................... 82
ASTMSD .................... 168 CHFCMR .................... 178 CHPROF..................... 101
ASTMSW ................... 168 CHFDNR ....................... 53 CHPVND .................... 151
ASTMTI...................... 196 CHFKDA ....................... 67 CHPVNR .................... 150
ASTONE ....................... 79 CHFLME ....................... 66 CHPVNS..................... 152
ASTREE ...................... 131 CHFMSN .................... 124 CHPVNT .................... 152

- 341 -
CHQFSM.................... 159 CRPUSR........................ 55 DIBSPR ...................... 210
CHQLMR ................... 137 CRROUT ..................... 205 DIBSPT ........................ 88
CHREMC .................... 161 CRTWIN ..................... 215 DICALF ........................ 30
CHRLOD .................... 163 DADESK ....................... 69 DICANS...................... 128
CHRORE ...................... 94 DEBNDL ..................... 210 DICASC ...................... 122
CHROTA .................... 205 DEBRDS ....................... 76 DICCDI ....................... 181
CHRTCG..................... 206 DEBRVC ....................... 80 DICCLI ....................... 213
CHRTCI ...................... 206 DECRUE ....................... 79 DICCSS ...................... 166
CHRTCO..................... 206 DECSVR...................... 224 DICCTR ...................... 209
CHRTLD ..................... 157 DEDEVC ....................... 81 DICDNR ....................... 45
CHSCNE ..................... 128 DEDICA ...................... 182 DICHAR ....................... 82
CHSEAU ..................... 175 DEFATI ......................... 61 DICLID ......................... 52
CHSEPR ..................... 175 DEGRPM ...................... 71 DICOBD ....................... 31
CHSICI ....................... 220 DEIBND ........................ 94 DICOCO ..................... 181
CHSIDO ..................... 112 DEILIN .......................... 95 DICOMP ...................... 26
CHSIPA ...................... 108 DEIPSE ......................... 98 DICONF ....................... 74
CHSIPD ...................... 106 DEIPUS......................... 97 DICONV ....................... 36
CHSIPL ....................... 117 DELDNM ...................... 83 DICQPR ..................... 136
CHSJOB ....................... 34 DELFIL .......................... 64 DICRUE........................ 79
CHSMAR ...................... 46 DELINE ....................... 212 DICSDD...................... 133
CHSSPD ..................... 156 DELINK ......................... 84 DICSVR ...................... 223
CHSUSR ..................... 111 DELINN ...................... 212 DICTAA ........................ 63
CHSYSD ..................... 170 DEOVLM .................... 141 DICTYP ........................ 36
CHTBAR ..................... 130 DEPACD ..................... 143 DICVAL ........................ 36
CHTFCR ..................... 178 DEPACK ....................... 50 DICVAP........................ 52
CHTIME ....................... 27 DEPALN ..................... 143 DICVCA........................ 36
CHTMOD ................... 197 DEPCTB ........................ 79 DICVCT ........................ 37
CHTMOF.................... 197 DEPORT ....................... 82 DICVMH ...................... 93
CHTMSL..................... 168 DEPVNU..................... 151 DIDATI ......................... 39
CHTMST .................... 168 DESHLF ........................ 75 DIDEST ...................... 204
CHTRAP ..................... 172 DESIPR ....................... 110 DIDEVC........................ 82
CHTRFC ..................... 190 DETEST ...................... 179 DIDFCM....................... 60
CHTRIF ...................... 146 DETMOB .................... 197 DIDGCO ..................... 207
CHTRLV ..................... 183 DETMTI ...................... 196 DIDIAL ....................... 133
CHTRNE ..................... 129 DETONE ....................... 79 DIDICA....................... 182
CHTTCR ..................... 183 DIABNR ........................ 17 DIDILA ......................... 42
CHTTOD .................... 183 DIACIV ....................... 174 DIDNRA ....................... 90
CHUNRE ...................... 94 DIACLI .......................... 90 DIDNRC ....................... 46
CHVLRE ..................... 226 DIAGCV ........................ 18 DIDNRL...................... 157
CLALRM....................... 62 DIANNO ....................... 93 DIDNRM ...................... 68
CLPATC ...................... 179 DIAPPF ....................... 144 DIDNRN..................... 126
CPFKDA ....................... 67 DIAQPR ...................... 135 DIDNRR ....................... 46
CPYFIL ......................... 64 DIASCV ...................... 138 DIDNRS ....................... 18
CRBSPT ........................ 88 DIASOP ...................... 138 DIDOTE ....................... 48
CRCCPP ..................... 181 DIASPR....................... 138 DIDTSS ........................ 51
CRCCSP...................... 181 DIAUPR ...................... 175 DIEPLE ....................... 214
CRCTYP........................ 36 DIBARR ...................... 134 DIEQID ........................ 77
CRCVAL ....................... 35 DIBBUT ...................... 135 DIESGR ........................ 57
CREFIL ......................... 64 DIBDNR........................ 46 DIEXID ......................... 39
CRESGR ....................... 57 DIBDTU ...................... 211 DIEXSE......................... 56
CREXSE ........................ 56 DIBLCK ......................... 62 DIFACM ....................... 59
CRGRPA....................... 70 DIBNDL ...................... 210 DIFATI ......................... 61
CRPARE ..................... 142 DIBRDS ........................ 77 DIFCMR ..................... 178
CRPART ..................... 142 DIBSPB ....................... 211 DIFCSU ........................ 60

- 342 -
DIFDNR........................ 53 DIOVLD ...................... 120 DISPTM ..................... 196
DIFKDA ........................ 67 DIOVLM ..................... 141 DISPTO ...................... 197
DIFLME ........................ 66 DIPACK ........................ 50 DISPTT....................... 183
DIFMSN ..................... 124 DIPALN ...................... 143 DISRVC ...................... 187
DIFROD ..................... 184 DIPARE....................... 142 DISSPD ...................... 157
DIFTLD....................... 214 DIPART....................... 142 DISUSR ...................... 111
DIFTLI ........................ 214 DIPATC....................... 179 DISYSD ...................... 170
DIGECA........................ 69 DIPCDR ........................ 32 DITCPC ........................ 96
DIGRPA ....................... 71 DIPCHD ...................... 187 DITCRT ...................... 213
DIGRPM ...................... 72 DIPCID ......................... 32 DITEST ....................... 179
DIGRPS ........................ 72 DIPCRT ....................... 149 DITFCR ...................... 178
DIHIBU ........................ 63 DIPDFS ....................... 148 DITFKM ....................... 68
DIHOTL ........................ 86 DIPDOD ..................... 147 DITMOB .................... 197
DIIABD......................... 87 DIPERD ...................... 188 DITMOD .................... 197
DIIBND ........................ 95 DIPICC........................ 145 DITMOF..................... 197
DIIPPD ....................... 105 DIPLPO......................... 73 DITMSD ..................... 169
DIIPPR ....................... 100 DIPMFU ..................... 160 DITMSL...................... 169
DIIPSE .......................... 98 DIPMON .................... 187 DITMST ..................... 169
DIIPUS ......................... 97 DIPMPD ..................... 154 DITMSW .................... 169
DIIROU ........................ 95 DIPOOL ...................... 186 DITMTI ...................... 196
DIISDN ....................... 195 DIPORT ........................ 83 DITRAF ...................... 191
DILCDF ...................... 121 DIPROF ...................... 101 DITRAP ...................... 172
DILCID ....................... 121 DIPUSR ........................ 55 DITRFC ...................... 190
DILDOM .................... 156 DIPVAR ...................... 186 DITRIF ....................... 146
DILICS ........................ 113 DIPVND...................... 151 DITRLV ...................... 183
DILINE ....................... 212 DIPVNR ...................... 150 DITTOD ..................... 183
DILINK ......................... 85 DIPVNT ...................... 152 DITWIN ..................... 215
DILINN ....................... 212 DIPVNU...................... 151 DIUNIT ...................... 225
DILOAD ..................... 120 DIQFSM ..................... 159 DIURRE........................ 94
DILOBP ...................... 218 DIQLMR ..................... 137 DIVICH....................... 165
DILODD ..................... 158 DIRECT ......................... 65 DIVLRE ...................... 226
DIMACA ...................... 78 DIRLOD ...................... 163 DOWNLD..................... 47
DIMAJA ....................... 62 DIROCO ..................... 186 DOWNLS ..................... 47
DIMDAT ...................... 28 DIROTA ...................... 205 DUSYSD ..................... 171
DIMDNR ...................... 68 DIROUT ...................... 205 ERACLI......................... 90
DIMERE ....................... 44 DIRTDN ...................... 209 ERAPPF...................... 144
DIMEUS ..................... 188 DIRTLD ....................... 157 ERBARR ..................... 134
DIMINA ....................... 62 DISADN ........................ 38 ERBSPB...................... 211
DIMMFC .................... 122 DISCID........................ 167 ERBSPR...................... 210
DIMQPR .................... 136 DISEMD ..................... 138 ERCANS ..................... 128
DIMSNP..................... 124 DISERV ....................... 164 ERCOCO .................... 181
DINAMU .................... 127 DISHLF ......................... 75 ERCONV ...................... 37
DINARS ...................... 130 DISICI ......................... 221 ERCTAA ....................... 63
DINASD ..................... 130 DISIDO ....................... 112 ERCTYP ........................ 37
DINASM .................... 131 DISIED ........................ 111 ERCVAL ....................... 36
DINDNR ..................... 127 DISIGQ ....................... 188 ERDGCO .................... 207
DINOIT ........................ 54 DISILA .......................... 62 ERDGCV .................... 206
DINPCD ..................... 159 DISIPL ........................ 117 ERDILA ........................ 43
DIOPAC ..................... 139 DISIPR ........................ 110 ERESGR ....................... 58
DIOPAV ..................... 137 DISJOB ......................... 33 EREXSE ........................ 56
DIOPCT ...................... 139 DISLDM...................... 119 ERFACM ...................... 60
DIOPID ...................... 139 DISPEX ....................... 129 ERGECA ....................... 69
DIOPLD ...................... 139 DISPFR ....................... 185 ERGRPA ....................... 73
DIOPST ...................... 139 DISPRL ....................... 163 ERIABD ........................ 87

- 343 -
ERLDOM .................... 156 MAKENU.................... 131 STMAIN ..................... 219
ERNOIT ........................ 54 MOVFIL........................ 65 STMONI .................... 188
ERPARE ..................... 142 OMLOCK ...................... 20 STOPFR ..................... 185
ERPART ..................... 143 PUBUMI ....................... 22 STOPPT ..................... 149
ERPICC....................... 145 PURFIL ......................... 65 STOPRL...................... 163
ERPUSR ....................... 55 REOVLM .................... 141 STOPTM .................... 196
ERROUT..................... 206 REROUT ....................... 63 STOPTT...................... 184
ERRTDN ..................... 209 RESICI ........................ 222 STPROJ ...................... 217
ERSADN ....................... 38 RESIPR ....................... 109 STRTFR ...................... 185
ERSCID ...................... 167 RESJOB ........................ 34 STRTPT ...................... 149
ERSYSD ...................... 171 RTFING ...................... 115 STRTRL ...................... 163
ERTMLI ...................... 197 RTRIEV ......................... 21 STRTTM..................... 196
ERTWIN ..................... 215 SECCDI ....................... 181 STRTTT ...................... 184
EXPING ........................ 96 SECCTO ...................... 181 STSRVC ...................... 187
EXSJOB ........................ 34 SEDATI ......................... 39 STWARM................... 217
EXSUBC ..................... 189 SEOVLM..................... 141 SUBJOB ....................... 34
FCLAIM...................... 166 SETINS ....................... 165 SUSJOB........................ 34
FIOWNR .................... 166 SETNIN....................... 165 SWALEX ...................... 62
FIPCTT ......................... 79 SETOUT...................... 165 SWCSVR .................... 222
FISERV ....................... 166 SPDUAL...................... 219 SWDUAL.................... 219
FRCOUT ..................... 165 SPMAIN ..................... 219 SWJUPD ...................... 22
FRCPSW .................... 177 SPSRVC ...................... 187 TRSYSD ...................... 171
GEBUFI ........................ 22 STALDM ..................... 119 TSALRM..................... 180
GEBUMI ...................... 21 STCOLD ...................... 217 TYPFIL ......................... 65
INESGR ........................ 58 STDOTE ........................ 48 UNIINS ...................... 225
INIDSK ......................... 91 STDUAL...................... 218 UNININ...................... 225
INSTPK......................... 49 STFTPS ......................... 99 UPDATE....................... 22
INTEST ....................... 180 STLOAD...................... 216 UPDUAL .................... 217
LDOVLM .................... 141 STLOBP ...................... 218 ZIPFIL .......................... 65

- 344 -