You are on page 1of 490

AviSuite - MCU

User Manual

Avitech GmbH

Document ID : UM_AviSuite_Mcu_All
Created / updated : Alice Lambert
Version : 1.4
Date of issue : 2018-10-10
Status : released

Avitech GmbH
Bahnhofplatz 3
88045 Friedrichshafen
Germany

It is prohibited to reproduce or transmit any part of this document for any purpose, in any form or by any means electronically or
mechanically, without the prior written permission of Avitech GmbH.
AviSuite - MCU
User Manual

Change History

Version Change Date Section(s)


1.3 See previous version 2017-11-23 n.a.
1.4 Typo and syntax corrected 2018-10-10 Various
Screenshots updated Various
“AviUnit” replaced with “unit” All
“Remove Alarm” replaces with “Clear Alarm” 5.1.1
“Avitech” and “Avitech AG” changed to “Avitech
GmbH” Various
“Delete State” text enhanced. 5.3.3.9.2
“Received OR Address” max chars corrected 5.3.5.3.2,
5.3.5.9.2
“Bidirectional” description updated 5.3.5.17.2
description of the circuit type updated 7.1.8.1,
7.1.8.2
“Total” column added 7.1.8.1,
7.1.8.2
“Channel identifier” renamed in “Channel” 7.1.8.1,
7.1.8.2
“Active Since” and “Cause” added 7.1.8.5.1
Description of the lines added 7.1.9.3
“The Printer Configuration mask” added 9.2.4
“The Email Account Configuration mask” added 9.2.5
“Table icons” added 9.4.1.5
“Bulk operations” added 9:5:5:1
“AMHS automated Diversion” removed OLD 9.5.9
“Oversize Text Handling” removed 9.5.13.1,
9.5.14.1
Note added in the Message Preview Part 10.2.4
“The AFTN Correction Position Viewer” added 11.1.9.3
“The File Tab” addee 11.1.10.3

 Avitech GmbH 2018 Page 3 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Table of Content
1 INTRODUCTION ................................................................................................. 28
1.1 Purpose and scope .............................................................................................. 28
1.2 Referenced documents ........................................................................................ 28
1.3 Abbreviations .......................................................................................................28
2 BASIC SKILLS .................................................................................................... 29
2.1 Introduction ..........................................................................................................29
2.1.1 Starting the application / Web Start technology ................................................... 29
2.1.2 How to login .........................................................................................................29
2.1.3 Navigation ............................................................................................................30
2.2 Printing mechanism ............................................................................................. 31
2.3 Finders .................................................................................................................32
2.3.1 Functions .............................................................................................................32
2.3.2 Special function calling a finder ........................................................................... 32
2.3.3 Fields ...................................................................................................................33
2.4 Chooser ...............................................................................................................33
2.4.1 The list of value chooser ...................................................................................... 33
2.4.2 Special function calling a list of value chooser .................................................... 34
2.5 Drop down menu ................................................................................................. 34
2.5.1 The File menu ......................................................................................................34
2.5.2 The Events menu ................................................................................................. 34
2.5.3 The Command menu ........................................................................................... 34
2.5.4 The Status Information menu .............................................................................. 35
2.5.5 The Report menu ................................................................................................. 35
2.5.6 The configuration menu ....................................................................................... 36
2.5.7 The Management menu ....................................................................................... 36
2.5.8 The Options menu ............................................................................................... 37
2.5.9 The Window menu ............................................................................................... 37
2.5.10 The Help menu ....................................................................................................38
3 THE DASHBOARD ............................................................................................. 39
3.1 Dashboard items .................................................................................................. 39
4 FILE MENU ......................................................................................................... 42
5 SYSTEM MESSAGES MENU ............................................................................. 43
5.1 The Event Monitor function .................................................................................. 43
5.1.1 Functions .............................................................................................................43
5.1.1.1 File Menu .............................................................................................................43
5.1.1.2 Navigation Menu .................................................................................................. 44
5.1.1.3 Options Menu ......................................................................................................44
5.1.2 Fields ...................................................................................................................44
5.1.2.1 The events table .................................................................................................. 44
5.1.2.2 The event display ................................................................................................. 46
5.2 The Event Configuration function ........................................................................ 46

 Avitech GmbH 2018 Page 4 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.2.1 Functions .............................................................................................................46


5.2.1.1 File Menu .............................................................................................................46
5.2.1.2 Options Menu ......................................................................................................47
5.2.2 Fields ...................................................................................................................47
5.3 List of events........................................................................................................48
5.3.1 General events ....................................................................................................48
5.3.1.1 AFTN_CHANNEL_CONN_STATE ...................................................................... 48
5.3.1.1.1 Description ...........................................................................................................48
5.3.1.1.2 Parameters ..........................................................................................................48
5.3.1.1.3 Necessary Actions ............................................................................................... 49
5.3.1.2 CHANNEL_STATE .............................................................................................. 49
5.3.1.2.1 Description ...........................................................................................................49
5.3.1.2.2 Parameters ..........................................................................................................49
5.3.1.2.3 Necessary Actions ............................................................................................... 50
5.3.1.3 CIRCUIT_STATE ................................................................................................. 51
5.3.1.3.1 Description ...........................................................................................................51
5.3.1.3.2 Parameters ..........................................................................................................51
5.3.1.3.3 Necessary Actions ............................................................................................... 51
5.3.1.4 COMPONENT_CONTROL .................................................................................. 52
5.3.1.4.1 Description ...........................................................................................................52
5.3.1.4.2 Parameters ..........................................................................................................52
5.3.1.4.3 Necessary Actions ............................................................................................... 53
5.3.1.5 COMPONENT_STATE ........................................................................................ 53
5.3.1.5.1 Description ...........................................................................................................53
5.3.1.5.2 Parameters ..........................................................................................................53
5.3.1.5.3 Necessary Actions ............................................................................................... 54
5.3.1.6 GENERAL_DATA_CHECK ................................................................................. 54
5.3.1.6.1 Description ...........................................................................................................54
5.3.1.6.2 Parameters ..........................................................................................................54
5.3.1.6.3 Necessary Actions ............................................................................................... 54
5.3.1.7 GENERAL_ERROR ............................................................................................. 54
5.3.1.7.1 Description ...........................................................................................................54
5.3.1.7.2 Parameters ..........................................................................................................54
5.3.1.7.3 Necessary Actions ............................................................................................... 55
5.3.1.8 MSG_OVERDUE_IN_QUEUE ............................................................................ 55
5.3.1.8.1 Description ...........................................................................................................55
5.3.1.8.2 Parameters ..........................................................................................................55
5.3.1.8.3 Necessary Actions ............................................................................................... 56

 Avitech GmbH 2018 Page 5 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.9 MESSAGE_QUEUE_NOT_EMPTY .................................................................... 56


5.3.1.9.1 Description ...........................................................................................................57
5.3.1.9.2 Parameters ..........................................................................................................57
5.3.1.9.3 Necessary Actions ............................................................................................... 57
5.3.1.10 MESSAGE_STATE ............................................................................................. 57
5.3.1.10.1 Description ...........................................................................................................57
5.3.1.10.2 Parameters ..........................................................................................................58
5.3.1.10.3 Necessary Actions ............................................................................................... 58
5.3.1.11 RESOURCE_BOTTLENECK .............................................................................. 58
5.3.1.11.1 Description ...........................................................................................................58
5.3.1.11.2 Parameters ..........................................................................................................59
5.3.1.11.3 Necessary Actions ............................................................................................... 59
5.3.1.12 SITA_GENERAL_INFORMATION ...................................................................... 59
5.3.1.12.1 Description ...........................................................................................................59
5.3.1.12.2 Parameters ..........................................................................................................59
5.3.1.12.3 Necessary Actions ............................................................................................... 60
5.3.1.13 X25_PORT_CHECK ............................................................................................ 60
5.3.1.13.1 Description ...........................................................................................................60
5.3.1.13.2 Parameters ..........................................................................................................60
5.3.1.13.3 Necessary Actions ............................................................................................... 60
5.3.2 AMS Events .........................................................................................................61
5.3.2.1 AMS_ACT_L_ERROR ......................................................................................... 61
5.3.2.1.1 Description ...........................................................................................................61
5.3.2.1.2 Parameters ..........................................................................................................61
5.3.2.1.3 Necessary Actions ............................................................................................... 61
5.3.2.2 AMS_LIST_TRANSFER ...................................................................................... 61
5.3.2.2.1 Description ...........................................................................................................61
5.3.2.2.2 Parameters ..........................................................................................................61
5.3.2.2.3 Necessary Actions ............................................................................................... 62
5.3.3 SFM Events .........................................................................................................62
5.3.3.1 SFM_AUTO_ADDRESS_DIVERSION ................................................................ 62
5.3.3.1.1 Description ...........................................................................................................62
5.3.3.1.2 Parameters ..........................................................................................................62
5.3.3.1.3 Necessary Actions ............................................................................................... 63
5.3.3.2 SFM_AUTO_DIRECTION_DIVERSION .............................................................. 63
5.3.3.2.1 Description ...........................................................................................................63
5.3.3.2.2 Parameters ..........................................................................................................63
5.3.3.2.3 Necessary Actions ............................................................................................... 65

 Avitech GmbH 2018 Page 6 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.3.3 SFM_BACKWARDS_RELAY_DONE .................................................................. 65


5.3.3.3.1 Description ...........................................................................................................65
5.3.3.3.2 Parameters ..........................................................................................................65
5.3.3.3.3 Necessary Actions. .............................................................................................. 66
5.3.3.4 SFM_BACKWARDS_RELAY_STRIPPED .......................................................... 66
5.3.3.4.1 Description ...........................................................................................................66
5.3.3.4.2 Parameters ..........................................................................................................66
5.3.3.4.3 Necessary Actions ............................................................................................... 67
5.3.3.5 SFM_CYCLIC_PDAI ............................................................................................ 67
5.3.3.5.1 Description ...........................................................................................................67
5.3.3.5.2 Parameters ..........................................................................................................67
5.3.3.5.3 Necessary Actions ............................................................................................... 67
5.3.3.6 SFM_MANUAL_ADDRESS_DIVERSION ........................................................... 67
5.3.3.6.1 Description ...........................................................................................................67
5.3.3.6.2 Parameters ..........................................................................................................67
5.3.3.6.3 Necessary Actions ............................................................................................... 69
5.3.3.7 SFM_MANUAL_DIRECTION_DIVERSION ......................................................... 69
5.3.3.7.1 Description ...........................................................................................................69
5.3.3.7.2 Parameters ..........................................................................................................69
5.3.3.7.3 Necessary Actions ............................................................................................... 70
5.3.3.8 SFM_MESSAGE_QUEUE_STALLED ................................................................. 70
5.3.3.8.1 Description ...........................................................................................................70
5.3.3.8.2 Parameters ..........................................................................................................71
5.3.3.8.3 Necessary Actions ............................................................................................... 71
5.3.3.9 SFM_MESSAGE_STORE_DELETE ................................................................... 71
5.3.3.9.1 Description ...........................................................................................................71
5.3.3.9.2 Parameters ..........................................................................................................71
5.3.3.9.3 Necessary Actions ............................................................................................... 71
5.3.3.10 SFM_MESSAGE_STORE_FAILURE .................................................................. 72
5.3.3.10.1 Description ...........................................................................................................72
5.3.3.10.2 Parameters ..........................................................................................................72
5.3.3.10.3 Necessary Actions ............................................................................................... 72
5.3.3.11 SFM_MESSAGE_STORE_ORDER .................................................................... 72
5.3.3.11.1 Description ...........................................................................................................72
5.3.3.11.2 Parameters ..........................................................................................................73
5.3.3.11.3 Necessary Actions ............................................................................................... 73
5.3.3.12 SFM_RECURRENT_ROUTING .......................................................................... 73
5.3.3.12.1 Description ...........................................................................................................73

 Avitech GmbH 2018 Page 7 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.3.12.2 Parameters ..........................................................................................................73


5.3.3.12.3 Necessary Actions ............................................................................................... 74
5.3.3.13 SFM_THRESHOLD ............................................................................................. 74
5.3.3.13.1 Description ...........................................................................................................74
5.3.3.13.2 Parameters ..........................................................................................................74
5.3.3.13.3 Necessary Actions ............................................................................................... 75
5.3.4 AFTN Events .......................................................................................................75
5.3.4.1 AFTN_ACCESS_VIOLATION ............................................................................. 75
5.3.4.1.1 Description ...........................................................................................................75
5.3.4.1.2 Parameters ..........................................................................................................75
5.3.4.1.3 Necessary Actions ............................................................................................... 76
5.3.4.2 AFTN_ANSWERBACK_FAILURE ....................................................................... 76
5.3.4.2.1 Description ...........................................................................................................76
5.3.4.2.2 Parameters ..........................................................................................................76
5.3.4.2.3 Necessary Actions ............................................................................................... 77
5.3.4.3 AFTN_BREAK_DURING_OUTPUT .................................................................... 77
5.3.4.3.1 Description ...........................................................................................................77
5.3.4.3.2 Parameters ..........................................................................................................77
5.3.4.3.3 Necessary Actions ............................................................................................... 78
5.3.4.4 AFTN_CHANNEL_GARBAGE_INFORMATION ................................................. 78
5.3.4.4.1 Description ...........................................................................................................78
5.3.4.4.2 Parameters ..........................................................................................................79
5.3.4.4.3 Necessary Actions ............................................................................................... 79
5.3.4.5 AFTN_DTG_FAILURE ......................................................................................... 79
5.3.4.5.1 Description ...........................................................................................................79
5.3.4.5.2 Parameters ..........................................................................................................80
5.3.4.5.3 Necessary Actions ............................................................................................... 80
5.3.4.6 AFTN_FEC_STATE ............................................................................................. 81
5.3.4.6.1 Description ...........................................................................................................81
5.3.4.6.2 Parameters ..........................................................................................................81
5.3.4.6.3 Necessary Actions ............................................................................................... 81
5.3.4.7 AFTN_MESSAGE_QUEUE_STALLED ............................................................... 81
5.3.4.7.1 Description ...........................................................................................................81
5.3.4.7.2 Parameters ..........................................................................................................82
5.3.4.7.3 Necessary Actions ............................................................................................... 82
5.3.4.8 AFTN_NO_CONNECTION_ESTABLISHED ....................................................... 82
5.3.4.8.1 Description ...........................................................................................................82
5.3.4.8.2 Parameters ..........................................................................................................83

 Avitech GmbH 2018 Page 8 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.8.3 Necessary Actions ............................................................................................... 84


5.3.4.9 AFTN_NO_DIAL_CONNECTION ........................................................................ 84
5.3.4.9.1 Description ...........................................................................................................84
5.3.4.9.2 Parameters ..........................................................................................................84
5.3.4.9.3 Necessary Actions ............................................................................................... 85
5.3.4.10 AFTN_OLDEST_MESSAGE_IN_QUEUE ........................................................... 85
5.3.4.10.1 Description ...........................................................................................................85
5.3.4.10.2 Parameters ..........................................................................................................85
5.3.4.10.3 Necessary Actions ............................................................................................... 86
5.3.4.11 AFTN_OMA_FAILURE ........................................................................................ 86
5.3.4.11.1 Description ...........................................................................................................86
5.3.4.11.2 Parameters ..........................................................................................................87
5.3.4.11.3 Necessary Actions ............................................................................................... 87
5.3.4.12 AFTN_QUEUE_OVERFLOW_STARTED ........................................................... 88
5.3.4.12.1 Description ...........................................................................................................88
5.3.4.12.2 Parameters ..........................................................................................................88
5.3.4.12.3 Necessary Actions ............................................................................................... 88
5.3.4.13 AFTN_RECEIVE_TIMEOUT ............................................................................... 89
5.3.4.13.1 Description ...........................................................................................................89
5.3.4.13.2 Parameters ..........................................................................................................89
5.3.4.13.3 Necessary Actions ............................................................................................... 89
5.3.4.14 AFTN_SS_MESSAGE_IN_QUEUE .................................................................... 90
5.3.4.14.1 Description ...........................................................................................................90
5.3.4.14.2 Parameters ..........................................................................................................90
5.3.4.14.3 Necessary Actions ............................................................................................... 90
5.3.4.15 AFTN_SVC_CAUSED_BY_FAULTY_MSG ........................................................ 91
5.3.4.15.1 Description ...........................................................................................................91
5.3.4.15.2 Parameters ..........................................................................................................91
5.3.4.15.3 Necessary Actions ............................................................................................... 92
5.3.4.16 AFTN_SVC_GENERATED .................................................................................. 92
5.3.4.16.1 Description ...........................................................................................................92
5.3.4.16.2 Parameters ..........................................................................................................92
5.3.4.16.3 Necessary Actions ............................................................................................... 93
5.3.4.17 AFTN_SVC_RECEIVED ...................................................................................... 93
5.3.4.17.1 Description ...........................................................................................................93
5.3.4.17.2 Parameters ..........................................................................................................93
5.3.4.17.3 Necessary Actions ............................................................................................... 94

 Avitech GmbH 2018 Page 9 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.18 AFTN_TESTMESSAGE_HANDLING .................................................................. 94


5.3.4.18.1 Description ...........................................................................................................94
5.3.4.18.2 Parameters ..........................................................................................................94
5.3.4.18.3 Necessary Actions ............................................................................................... 95
5.3.4.19 AFTN_THRESHOLD_1 ....................................................................................... 95
5.3.4.19.1 Description ...........................................................................................................95
5.3.4.19.2 Parameters ..........................................................................................................95
5.3.4.19.3 Necessary Actions ............................................................................................... 96
5.3.4.20 AFTN_THRESHOLD_2 ....................................................................................... 96
5.3.4.20.1 Description ...........................................................................................................96
5.3.4.20.2 Parameters ..........................................................................................................96
5.3.4.20.3 Necessary Actions ............................................................................................... 97
5.3.4.21 AFTN_THRESHOLD_3 ....................................................................................... 97
5.3.4.21.1 Description ...........................................................................................................97
5.3.4.21.2 Parameters ..........................................................................................................97
5.3.4.21.3 Necessary Actions ............................................................................................... 98
5.3.4.22 AFTN_RESET_THRESHOLD_1 ......................................................................... 98
5.3.4.22.1 Description ...........................................................................................................98
5.3.4.22.2 Parameters ..........................................................................................................98
5.3.4.22.3 Necessary Actions ............................................................................................... 99
5.3.4.23 AFTN_RESET_THRESHOLD_2 ......................................................................... 99
5.3.4.23.1 Description ...........................................................................................................99
5.3.4.23.2 Parameters ..........................................................................................................99
5.3.4.23.3 Necessary Actions ............................................................................................... 99
5.3.4.24 AFTN_RESET_THRESHOLD_3 ....................................................................... 100
5.3.4.24.1 Description .........................................................................................................100
5.3.4.24.2 Parameters ........................................................................................................100
5.3.4.24.3 Necessary Actions ............................................................................................. 100
5.3.4.25 AFTN_TID_FAILURE ........................................................................................ 101
5.3.4.25.1 Description .........................................................................................................101
5.3.4.25.2 Parameters ........................................................................................................101
5.3.4.25.3 Necessary Actions ............................................................................................. 102
5.3.4.26 AFTN_TRANSFER_ERROR ............................................................................. 102
5.3.4.26.1 Description .........................................................................................................102
5.3.4.26.2 Parameters ........................................................................................................102
5.3.4.26.3 Necessary Actions ............................................................................................. 103
5.3.4.27 AFTN_UNEXPECTED_MSG_RECEIVED ........................................................ 103
5.3.4.27.1 Parameters ........................................................................................................103

 Avitech GmbH 2018 Page 10 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.28 AFTN_X25_EVENT ........................................................................................... 104


5.3.4.28.1 Description .........................................................................................................104
5.3.4.28.2 Parameters ........................................................................................................104
5.3.4.28.3 Necessary Actions ............................................................................................. 105
5.3.5 AMHS Events ....................................................................................................105
5.3.5.1 AMHSRV_INFORMATION ................................................................................ 105
5.3.5.1.1 Description .........................................................................................................105
5.3.5.1.2 Parameters ........................................................................................................106
5.3.5.1.3 Necessary Actions ............................................................................................. 106
5.3.5.2 AMHS_IPN_RECEIVED .................................................................................... 106
5.3.5.2.1 Description .........................................................................................................106
5.3.5.2.2 Parameters ........................................................................................................106
5.3.5.2.3 Necessary Actions ............................................................................................. 107
5.3.5.3 AMHS_MSG_TRANSL_ORIG_NON_SYMMETRIC ......................................... 107
5.3.5.3.1 Description .........................................................................................................107
5.3.5.3.2 Parameters ........................................................................................................107
5.3.5.3.3 Necessary Actions ............................................................................................. 108
5.3.5.4 AMHS_MSG_TRANSL_RCP_NON_SYMMETRIC ........................................... 108
5.3.5.4.1 Description .........................................................................................................108
5.3.5.4.2 Parameters ........................................................................................................108
5.3.5.4.3 Necessary Actions ............................................................................................. 109
5.3.5.5 AMHS_MTA_SESSION_INFO .......................................................................... 109
5.3.5.5.1 Description .........................................................................................................109
5.3.5.5.2 Parameters ........................................................................................................109
5.3.5.5.3 Necessary Actions ............................................................................................. 110
5.3.5.6 AMHS_MTCU_INFORMATION ......................................................................... 110
5.3.5.6.1 Description .........................................................................................................110
5.3.5.6.2 Parameters ........................................................................................................110
5.3.5.6.3 Necessary Actions ............................................................................................. 110
5.3.5.7 AMHS_NON_DELIVERY_REPORT_CREATED .............................................. 110
5.3.5.7.1 Description .........................................................................................................110
5.3.5.7.2 Parameters ........................................................................................................110
5.3.5.7.3 Necessary Actions ............................................................................................. 113
5.3.5.8 AMHS_NON_DELIVERY_REPORT_RECEIVED ............................................. 113
5.3.5.8.1 Description .........................................................................................................113
5.3.5.8.2 Parameters ........................................................................................................113
5.3.5.8.3 Necessary Actions ............................................................................................. 116
5.3.5.9 AMHS_PRB_TRANSL_ORIG_NON_SYMMETRIC .......................................... 116

 Avitech GmbH 2018 Page 11 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.5.9.1 Description .........................................................................................................116


5.3.5.9.2 Parameters ........................................................................................................116
5.3.5.9.3 Necessary Actions ............................................................................................. 117
5.3.5.10 AMHS_PRB_TRANSL_RCP_NON_SYMMETRIC ............................................ 117
5.3.5.10.1 Description .........................................................................................................117
5.3.5.10.2 Parameters ........................................................................................................117
5.3.5.10.3 Necessary Actions ............................................................................................. 118
5.3.5.11 AMHS_RECIPIENT_REACHABLE ................................................................... 118
5.3.5.11.1 Description .........................................................................................................118
5.3.5.11.2 Parameters ........................................................................................................118
5.3.5.11.3 Necessary Actions ............................................................................................. 118
5.3.5.12 AMHS_RECIPIENT_UNREACHABLE .............................................................. 118
5.3.5.12.1 Description .........................................................................................................118
5.3.5.12.2 Parameters ........................................................................................................118
5.3.5.12.3 Necessary Actions ............................................................................................. 119
5.3.5.13 AMHS_RPT_TRANSL_REP_RCP_NON_SYMMETRIC................................... 119
5.3.5.13.1 Description .........................................................................................................119
5.3.5.13.2 Parameters ........................................................................................................119
5.3.5.13.3 Necessary Actions ............................................................................................. 120
5.3.5.14 AMHS_SS_ACKNOWLEDGEMENT_RECEIVED ............................................. 120
5.3.5.14.1 Description .........................................................................................................120
5.3.5.14.2 Parameters ........................................................................................................120
5.3.5.14.3 Necessary Actions ............................................................................................. 121
5.3.5.15 AMHS_SS_MESSAGE_RECEIVED ................................................................. 121
5.3.5.15.1 Description .........................................................................................................121
5.3.5.15.2 Parameters ........................................................................................................121
5.3.5.15.3 Necessary Actions ............................................................................................. 122
5.3.5.16 DISTRESS_MESSAGE_RECEIVED ................................................................. 122
5.3.5.16.1 Description .........................................................................................................122
5.3.5.16.2 Parameters ........................................................................................................122
5.3.5.16.3 Necessary Actions ............................................................................................. 123
5.3.5.17 MTA_P1_CONNECTION_EVENT ..................................................................... 123
5.3.5.17.1 Description .........................................................................................................123
5.3.5.17.2 Parameters ........................................................................................................124
5.3.5.17.3 Necessary Actions ............................................................................................. 125
5.3.5.18 MTA_P3_CONNECTION_EVENT ..................................................................... 125
5.3.5.18.1 Description .........................................................................................................125

 Avitech GmbH 2018 Page 12 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.5.18.2 Parameters ........................................................................................................125


5.3.5.18.3 Necessary Actions ............................................................................................. 127
5.3.6 CIDIN Events .....................................................................................................127
5.3.6.1 CIDIN_CPSN_ERROR ...................................................................................... 127
5.3.6.1.1 Description .........................................................................................................127
5.3.6.1.2 Parameters ........................................................................................................127
5.3.6.1.3 Necessary Actions ............................................................................................. 127
5.3.6.2 CIDIN_ENQ_FROM_UNKNOWN_AE_RCVD ................................................... 128
5.3.6.2.1 Description .........................................................................................................128
5.3.6.2.2 Parameters ........................................................................................................128
5.3.6.2.3 Necessary Actions ............................................................................................. 128
5.3.6.3 CIDIN_ENQ_RESP_FROM_UNKNOWN_AX_RCVD ....................................... 128
5.3.6.3.1 Description .........................................................................................................128
5.3.6.3.2 Parameters ........................................................................................................129
5.3.6.3.3 Necessary Actions ............................................................................................. 129
5.3.6.4 CIDIN_EXIT_AVAILABLE .................................................................................. 129
5.3.6.4.1 Description .........................................................................................................129
5.3.6.4.2 Parameters ........................................................................................................129
5.3.6.4.3 Necessary Actions ............................................................................................. 129
5.3.6.5 CIDIN_EXIT_UNAVAILABLE ............................................................................ 129
5.3.6.5.1 Description .........................................................................................................129
5.3.6.5.2 Parameters ........................................................................................................129
5.3.6.5.3 Necessary Actions ............................................................................................. 130
5.3.6.6 CIDIN_GENERAL_INFORMATION ................................................................... 130
5.3.6.6.1 Description .........................................................................................................130
5.3.6.6.2 Parameters ........................................................................................................130
5.3.6.6.3 Necessary Actions ............................................................................................. 130
5.3.6.7 CIDIN_ILLEGAL_EXIT ...................................................................................... 130
5.3.6.7.1 Description .........................................................................................................130
5.3.6.7.2 Parameters ........................................................................................................131
5.3.6.7.3 Necessary Actions ............................................................................................. 131
5.3.6.8 CIDIN_MCF_ERROR ........................................................................................ 131
5.3.6.8.1 Description .........................................................................................................131
5.3.6.8.2 Parameters ........................................................................................................131
5.3.6.8.3 Necessary Actions ............................................................................................. 132
5.3.6.9 CIDIN_PACKET_HDR_ERROR ........................................................................ 132
5.3.6.9.1 Description .........................................................................................................132
5.3.6.9.2 Parameters ........................................................................................................132

 Avitech GmbH 2018 Page 13 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.9.3 Necessary Actions ............................................................................................. 132


5.3.6.10 CIDIN_THRESHOLD_1 ..................................................................................... 133
5.3.6.10.1 Description .........................................................................................................133
5.3.6.10.2 Parameters ........................................................................................................133
5.3.6.10.3 Necessary Actions ............................................................................................. 133
5.3.6.11 CIDIN_THRESHOLD_2 ..................................................................................... 133
5.3.6.11.1 Description .........................................................................................................133
5.3.6.11.2 Parameters ........................................................................................................133
5.3.6.11.3 Necessary Actions ............................................................................................. 133
5.3.6.12 CIDIN_THRESHOLD_3 ..................................................................................... 133
5.3.6.12.1 Description .........................................................................................................133
5.3.6.12.2 Parameters ........................................................................................................133
5.3.6.12.3 Necessary Actions ............................................................................................. 134
5.3.6.13 CIDIN_RESET_THRESHOLD_1 ....................................................................... 134
5.3.6.13.1 Description .........................................................................................................134
5.3.6.13.2 Parameters ........................................................................................................134
5.3.6.13.3 Necessary Actions ............................................................................................. 134
5.3.6.14 CIDIN_RESET_THRESHOLD_2 ....................................................................... 134
5.3.6.14.1 Description .........................................................................................................134
5.3.6.14.2 Parameters ........................................................................................................134
5.3.6.14.3 Necessary Actions ............................................................................................. 134
5.3.6.15 CIDIN_RESET_THRESHOLD_3 ....................................................................... 135
5.3.6.15.1 Description .........................................................................................................135
5.3.6.15.2 Parameters ........................................................................................................135
5.3.6.15.3 Necessary Actions ............................................................................................. 135
5.3.6.16 CIDIN_TNMA_TIMEOUT ................................................................................... 135
5.3.6.16.1 Description .........................................................................................................135
5.3.6.16.2 Parameters ........................................................................................................135
5.3.6.16.3 Necessary Actions ............................................................................................. 135
5.3.6.17 CIDIN_TRANSPORT_HEADER_SYNTAX_ERROR......................................... 135
5.3.6.17.1 Description .........................................................................................................135
5.3.6.17.2 Parameters ........................................................................................................136
5.3.6.17.3 Necessary Actions ............................................................................................. 136
5.3.6.18 CIDIN_USE_EQUAL_VIRTUAL_CIRCUIT ........................................................ 136
5.3.6.18.1 Description .........................................................................................................136
5.3.6.18.2 Parameters ........................................................................................................136
5.3.6.18.3 Necessary Actions ............................................................................................. 136

 Avitech GmbH 2018 Page 14 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.19 CIDIN_VC_STATE ............................................................................................ 136


5.3.6.19.1 Description .........................................................................................................136
5.3.6.19.2 Parameters ........................................................................................................137
5.3.6.19.3 Necessary Actions ............................................................................................. 137
5.3.6.20 CIDIN_X25_EVENT ........................................................................................... 137
5.3.6.20.1 Description .........................................................................................................137
5.3.6.20.2 Parameters ........................................................................................................137
5.3.6.20.3 Necessary Actions ............................................................................................. 138
6 COMMAND MENU ............................................................................................ 139
6.1 The Command function ..................................................................................... 139
6.1.1 Function .............................................................................................................139
6.1.1.1 File .....................................................................................................................139
6.1.1.2 Options Menu ....................................................................................................140
6.1.2 Fields .................................................................................................................140
6.2 The Macro function ............................................................................................ 141
6.2.1 Function .............................................................................................................141
6.2.1.1 File .....................................................................................................................141
6.2.1.2 Action Menu .......................................................................................................142
6.2.1.3 Options Menu ....................................................................................................142
6.2.1.4 Icons ..................................................................................................................142
6.2.2 Fields .................................................................................................................143
6.3 List of commands ............................................................................................... 143
6.3.1 Introduction ........................................................................................................143
6.3.2 Nomenclature ....................................................................................................143
6.3.2.1 Arguments .........................................................................................................143
6.3.2.2 Argument combinations ..................................................................................... 144
6.3.2.3 Most used parameters ....................................................................................... 144
6.3.3 List all available commands [LIST] .................................................................... 145
6.3.4 Commands related to AFTN .............................................................................. 148
6.3.4.1 Activate channel check messages [ACT_CHCK] .............................................. 149
6.3.4.2 Activate check text [ACT_CKTEXT] .................................................................. 150
6.3.4.3 Activate CSN checking [ACT_CSNCHK] ........................................................... 150
6.3.4.4 Activate diversion for an address [ACT_DIVA] .................................................. 151
6.3.4.5 Activate diversion for a direction [ACT_DIVD] ................................................... 153
6.3.4.6 Activate automatic SVC handling [ACT_SVCG] ................................................ 154
6.3.4.7 Send cyclic AFTN test message [ACT_TMSG] ................................................. 155
6.3.4.8 Close channel [CL_CHAN] ................................................................................ 156
6.3.4.9 Close circuit [CL_CIRC] ..................................................................................... 157
6.3.4.10 Close input channel [CL_IN_CH] ....................................................................... 158
6.3.4.11 Continue outgoing messages [CONTINUE] ...................................................... 158
6.3.4.12 Deactivate channel check messages [DAC_CHCK] .......................................... 159
6.3.4.13 Deactivate check text [DAC_CKTEXT] .............................................................. 160

 Avitech GmbH 2018 Page 15 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.4.14 Deactivate CSN checking [DAC_CSNCHK] ...................................................... 161


6.3.4.15 Deactivate diversion for an address [DAC_DIVA] ............................................. 162
6.3.4.16 Deactivate diversion for a direction [DAC_DIVD] .............................................. 163
6.3.4.17 Deactivate automatic SVC handling [DAC_SVCG] ........................................... 164
6.3.4.18 Stop sending AFTN test message [DAC_TMSG] .............................................. 165
6.3.4.19 Generate a channel check message [GEN_CHCK] .......................................... 166
6.3.4.20 Generate an SVC LRLS [GEN_LRLS] ............................................................... 166
6.3.4.21 Hold outgoing messages [HOLD] ...................................................................... 167
6.3.4.22 Send AFTN test note [NOTE_TST] ................................................................... 168
6.3.4.23 Open circuit [OP_CHAN] ................................................................................... 169
6.3.4.24 Open circuit [OP_CIRC] ..................................................................................... 170
6.3.4.25 Open input channel [OP_IN_CH] ....................................................................... 171
6.3.4.26 Set channel sequence numbers [SET_CSN] ..................................................... 172
6.3.4.27 Set channel state to test [TST_CHAN] .............................................................. 173
6.3.5 Commands related to CIDIN .............................................................................. 174
6.3.5.1 Change enquiry interval [CHG_ENQ] ................................................................ 174
6.3.5.2 Close CIDIN exit centre [CL_AX] ....................................................................... 175
6.3.5.3 Close CIDIN virtual circuit [CL_VC] ................................................................... 175
6.3.5.4 Open CIDIN exit centre [OP_AX] ....................................................................... 176
6.3.5.5 Open CIDIN virtual circuit [OP_VC] ................................................................... 177
6.3.6 Other commands ............................................................................................... 178
6.3.6.1 Activate service lists [ACT_L] ............................................................................ 178
6.3.6.2 Macro or sequence of commands [MACRO] ..................................................... 180
6.3.6.3 Request application call-back [REQUEST] ........................................................ 181
6.3.6.4 Restart application [RESTART] ......................................................................... 182
6.3.6.5 Timely separate commands in a macro [WAIT] ................................................. 183
7 STATUS INFORMATION MENU ...................................................................... 184
7.1 The Circuit and Queue Monitor function ............................................................ 184
7.1.1 The Circuit and Queue Monitor tree .................................................................. 185
7.1.2 Common circuit and queue monitor functions ................................................... 185
7.1.2.1 File .....................................................................................................................185
7.1.2.2 Options ..............................................................................................................185
7.1.3 The root level .....................................................................................................186
7.1.4 The second level ................................................................................................ 186
7.1.5 The third level ....................................................................................................186
7.1.6 The fourth level .................................................................................................. 187
7.1.7 The fifth level .....................................................................................................187
7.1.8 The upper right tabs ........................................................................................... 187
7.1.8.1 The Circuit Overview tab ................................................................................... 187
7.1.8.2 The Suspicious Circuits tab ............................................................................... 189
7.1.8.3 The Queue Visualisation tab .............................................................................. 191
7.1.8.4 The Overview tab ............................................................................................... 192
7.1.8.4.1 Upper part ..........................................................................................................192

 Avitech GmbH 2018 Page 16 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.1.8.4.2 Lower part ..........................................................................................................193


7.1.8.5 The Actions and Properties tab ......................................................................... 193
7.1.8.5.1 Upper part ..........................................................................................................193
7.1.8.5.2 Lower part ..........................................................................................................194
7.1.8.5.2.1 Changing the operational state of a circuit. ....................................................... 194
7.1.8.5.2.2 Setting diversions for a circuit ............................................................................ 195
7.1.9 The lower right tabs ........................................................................................... 195
7.1.9.1.1 The Diversion tab ............................................................................................... 195
7.1.9.2 The Copy Address tab ....................................................................................... 196
7.1.9.3 The Current Day Statistics tab ........................................................................... 197
7.1.9.4 The Additional Information tab ........................................................................... 198
7.1.10 Message Viewer ................................................................................................ 199
7.1.10.1 AFTN Message Viewer ...................................................................................... 199
7.2 Connection State ............................................................................................... 200
7.2.1 Common state monitor functions ....................................................................... 200
7.2.1.1 File .....................................................................................................................200
7.2.1.2 Options ..............................................................................................................200
7.2.2 The AFTN Connection State Monitor ................................................................. 201
7.2.2.1 Column ..............................................................................................................201
7.2.3 The AMHS Connection State Monitor ................................................................ 203
7.2.3.1 Column ..............................................................................................................203
7.2.4 The CIDIN Exit Centre Connection State Monitor ............................................. 205
7.2.4.1 Column ..............................................................................................................205
7.2.5 The CIDIN Virtual Circuit Connection State Monitor .......................................... 206
7.2.5.1 Column ..............................................................................................................206
8 REPORT MENU ................................................................................................ 207
8.1 Common Report functions ................................................................................. 207
8.1.1 File .....................................................................................................................207
8.1.2 Options ..............................................................................................................207
8.2 The Overflow Queue report ............................................................................... 208
8.3 The Message Router Queue report ................................................................... 209
8.4 The Address Diversion report ............................................................................ 210
8.5 The Direction Diversion report ........................................................................... 210
8.6 The Queue Summary report .............................................................................. 211
8.7 The Channel Settings report .............................................................................. 213
8.8 The Channel State report .................................................................................. 215
8.9 The Queue Detail report .................................................................................... 216
8.10 The CSN Midnight report ................................................................................... 217
8.11 The AFTN Test Message report ........................................................................ 218
8.12 The Virtual Circuit State report .......................................................................... 218
8.13 The Virtual Circuit Group Queue report ............................................................. 219

 Avitech GmbH 2018 Page 17 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

8.14 The Exit Centre State report .............................................................................. 220


8.15 The Exit Centre Queue report ............................................................................ 221
9 CONFIGURATION MENU ................................................................................. 223
9.1 The System Configuration function .................................................................... 226
9.1.1 Functions ...........................................................................................................226
9.1.1.1 File Menu ...........................................................................................................226
9.1.1.2 Options Menu ....................................................................................................227
9.1.2 Table columns ...................................................................................................227
9.1.2.1 Upper table ........................................................................................................227
9.1.2.2 Lower table ........................................................................................................228
9.2 Common Services Configuration ....................................................................... 229
9.2.1 Functions ...........................................................................................................229
9.2.1.1 File Menu ...........................................................................................................229
9.2.1.2 Options Menu ....................................................................................................230
9.2.1.3 Icons on the left side of the table. ...................................................................... 230
9.2.2 Printer configuration Tab ................................................................................... 230
9.2.3 E-mail accounts configuration Tab .................................................................... 231
9.2.4 The Printer Configuration mask ......................................................................... 232
9.2.4.1 Functions ...........................................................................................................232
9.2.4.1.1 File Menu ...........................................................................................................232
9.2.4.1.2 Options Menu ....................................................................................................233
9.2.4.2 Fields .................................................................................................................233
9.2.5 The Email Account Configuration mask ............................................................. 234
9.2.5.1.1 File Menu ...........................................................................................................234
9.2.5.1.2 Options Menu ....................................................................................................235
9.2.5.1.3 Icons on the left side of the table. ...................................................................... 235
9.2.5.2 Fields .................................................................................................................235
9.3 Compare bundles .............................................................................................. 236
9.4 Bundle Details ....................................................................................................237
9.4.1 Functions ...........................................................................................................237
9.4.1.1 File menu ...........................................................................................................237
9.4.1.2 Action menu .......................................................................................................238
9.4.1.3 AMC menu .........................................................................................................239
9.4.1.4 Options Menu ....................................................................................................239
9.4.1.5 Table icons ........................................................................................................239
9.4.2 Fields .................................................................................................................239
9.4.3 Tabs ...................................................................................................................240
9.4.4 Import Address Look-up Tables ......................................................................... 248
9.4.4.1 Functions ...........................................................................................................248
9.4.4.1.1 File Menu ...........................................................................................................248
9.4.4.1.2 Options Menu ....................................................................................................249

 Avitech GmbH 2018 Page 18 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.4.4.2 Fields .................................................................................................................249


9.4.4.2.1 Upper Part .........................................................................................................249
9.4.4.2.2 The Compare MDR tab ...................................................................................... 250
9.4.4.2.3 The Compare CAAS tab .................................................................................... 251
9.4.4.2.4 Compare User Addresses ................................................................................. 252
9.4.5 Export Address Look-up Tables ........................................................................ 253
9.4.5.1 Functions ...........................................................................................................253
9.4.5.1.1 File Menu ...........................................................................................................253
9.4.5.1.2 Options Menu ....................................................................................................253
9.4.5.2 Fields .................................................................................................................254
9.4.6 Import Routing Tables ....................................................................................... 254
9.4.6.1 Functions ...........................................................................................................254
9.4.6.1.1 File Menu ...........................................................................................................254
9.4.6.1.2 Options Menu ....................................................................................................255
9.4.6.2 Fields .................................................................................................................255
9.5 Configuration and routing lists ........................................................................... 255
9.5.1 Common configuration and routing functions .................................................... 255
9.5.1.1 File .....................................................................................................................255
9.5.1.2 Action .................................................................................................................256
9.5.1.2.1 Options ..............................................................................................................257
9.5.2 Common configuration and routing fields .......................................................... 257
9.5.2.1 Fields .................................................................................................................257
9.5.3 Conventions used .............................................................................................. 257
9.5.3.1 Argument Types ................................................................................................ 258
9.5.3.2 Possible combinations ....................................................................................... 258
9.5.4 The AFTN Circuit Route list ............................................................................... 259
9.5.4.1 Functions ...........................................................................................................259
9.5.4.2 Fields .................................................................................................................260
9.5.4.3 The Routing tab ................................................................................................. 260
9.5.4.4 The AFTN Circuit Details tab ............................................................................. 261
9.5.4.5 The Properties tab ............................................................................................. 263
9.5.4.6 The Channels tab .............................................................................................. 266
9.5.4.6.1 The General tab ................................................................................................. 266
9.5.4.6.2 The CSN/CH tab ................................................................................................ 270
9.5.4.6.3 The Format tab .................................................................................................. 271
9.5.4.6.4 The SVC Handling tab ....................................................................................... 274
9.5.4.6.5 The Timer tab ....................................................................................................275
9.5.4.7 The Barring tab .................................................................................................. 277
9.5.4.8 The Originator tab .............................................................................................. 278
9.5.4.9 The Incoming Responsibility tab ........................................................................ 278

 Avitech GmbH 2018 Page 19 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.5 AFTN Address Route ......................................................................................... 279


9.5.5.1 Bulk Operations ................................................................................................. 280
9.5.5.2 Functions ...........................................................................................................281
9.5.5.3 Fields .................................................................................................................281
9.5.5.4 Fields .................................................................................................................282
9.5.6 Copy Addresses ................................................................................................ 283
9.5.6.1 Fields .................................................................................................................284
9.5.7 AFTN Device .....................................................................................................284
9.5.7.1 Functions ...........................................................................................................285
9.5.7.2 Fields .................................................................................................................285
9.5.7.3 Transport Addresses ......................................................................................... 286
9.5.7.4 Terminal Server Properties ................................................................................ 286
9.5.7.5 Fax Properties ...................................................................................................287
9.5.7.6 Dial In/Out Properties ........................................................................................ 287
9.5.7.7 FEC Properties .................................................................................................. 288
9.5.7.8 X25 Properties ...................................................................................................289
9.5.7.9 SITA Properties ................................................................................................. 290
9.5.8 SITA-AFTN Mapping ......................................................................................... 292
9.5.8.1 Fields .................................................................................................................293
9.5.9 AMHS Automated diversion ............................................................................... 293
9.5.10 AMHS Management Domain Look-up ............................................................... 294
9.5.10.1 Fields .................................................................................................................295
9.5.11 AMHS CAAS Look-up ........................................................................................ 296
9.5.11.1 Fields .................................................................................................................296
9.5.12 AMHS Miscellaneous ......................................................................................... 297
9.5.12.1 Fields .................................................................................................................298
9.5.13 AMHS User Addresses ...................................................................................... 299
9.5.13.1 Fields .................................................................................................................300
9.5.13.2 The Advanced Properties tab ............................................................................ 301
9.5.13.3 The Domain Defined Attributes tab .................................................................... 301
9.5.13.4 The Personal Details tab ................................................................................... 302
9.5.14 CIDIN Entry/Exit Centre ..................................................................................... 303
9.5.14.1 Fields .................................................................................................................303
9.5.15 CIDIN ADAX ......................................................................................................305
9.5.15.1 Fields .................................................................................................................305
9.5.16 CIDIN Routing ....................................................................................................306
9.5.16.1 Fields .................................................................................................................307
9.5.17 CIDIN Virtual Circuit Group ................................................................................ 307
9.5.17.1 Fields .................................................................................................................308
9.5.17.2 CIDIN Virtual Circuit ........................................................................................... 309
9.5.17.2.1 Fields .................................................................................................................310
9.5.18 AMHS User Agent ............................................................................................. 311
9.5.18.1 Fields .................................................................................................................312

 Avitech GmbH 2018 Page 20 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.19 MTA Circuit ........................................................................................................313


9.5.19.1 Fields .................................................................................................................314
10 MANAGEMENT MENU ..................................................................................... 316
10.1 The Traffic Monitor function ............................................................................... 316
10.1.1 The upper table .................................................................................................. 316
10.1.2 Lower part ..........................................................................................................318
10.1.3 Traffic Monitor functions .................................................................................... 318
10.1.3.1 File .....................................................................................................................318
10.1.3.2 Options ..............................................................................................................318
10.1.4 The Compose a command window of the Traffic Monitor.................................. 319
10.1.4.1 Fields .................................................................................................................319
10.1.4.2 Command buttons ............................................................................................. 319
10.1.4.3 Note ...................................................................................................................319
10.1.5 The Configuration window of the Traffic Monitor ............................................... 319
10.1.5.1 Fields .................................................................................................................320
10.1.5.2 Command buttons ............................................................................................. 320
10.2 The Message Retrieval ...................................................................................... 320
10.2.1 The retrieval tree ................................................................................................ 321
10.2.2 The Message Retrieval functions ...................................................................... 321
10.2.2.1 File .....................................................................................................................321
10.2.2.2 Options ..............................................................................................................321
10.2.3 The search criteria tab ....................................................................................... 322
10.2.4 The result tab .....................................................................................................326
10.3 The Archive unit ................................................................................................. 329
10.3.1 Functions ...........................................................................................................329
10.3.1.1 File .....................................................................................................................329
10.3.1.2 Options ..............................................................................................................330
10.3.2 Fields .................................................................................................................330
10.3.3 Upper Part - The Search filter ............................................................................ 330
10.3.4 Middle Part - The Result table ........................................................................... 330
10.3.5 Lower part - The Record preview ...................................................................... 331
10.4 The Channel Maintenance function ................................................................... 331
10.4.1 The channel tree ................................................................................................ 331
10.4.2 The message table ............................................................................................ 332
10.4.3 The message preview ........................................................................................ 333
10.4.4 The search function ........................................................................................... 333
10.4.4.1 Functions ...........................................................................................................334
10.4.4.1.1 File .....................................................................................................................334
10.4.4.1.2 Options ..............................................................................................................334
10.4.4.2 Special Features ................................................................................................ 335
10.4.4.3 Message Type ...................................................................................................336
10.4.4.3.1 Columns .............................................................................................................336

 Avitech GmbH 2018 Page 21 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.3.2 Query .................................................................................................................337


10.4.4.4 The AMHS tab ...................................................................................................338
10.4.4.5 The IPM tab .......................................................................................................338
10.4.4.6 The Ipn tab.........................................................................................................339
10.4.4.7 The Report tab ...................................................................................................340
10.4.4.8 The Probe tab ....................................................................................................341
10.4.4.9 Sub-tabs ............................................................................................................342
10.4.4.9.1 The IPM Details sub-tab .................................................................................... 342
10.4.4.9.2 The Ipn Details sub-tab ...................................................................................... 344
10.4.4.9.3 The Probe Details sub-tab ................................................................................. 345
10.4.4.9.4 The Deliv. Envelope sub-tab .............................................................................. 347
10.4.4.9.5 The Subm. Envelope sub-tab ............................................................................ 348
10.4.4.9.6 The Submission Result sub-tab ......................................................................... 350
10.5 The AMHS Channel Configuration mask ........................................................... 350
10.5.1 Functions ...........................................................................................................351
10.5.1.1 File .....................................................................................................................351
10.5.2 Fields .................................................................................................................351
10.6 MTA Device Configuration ................................................................................. 353
10.6.1 Functions ...........................................................................................................353
10.6.1.1 File .....................................................................................................................353
10.6.2 Fields .................................................................................................................354
10.7 Statistics function ............................................................................................... 355
10.7.1 Functions ...........................................................................................................356
10.7.1.1 File Menu ...........................................................................................................356
10.7.1.2 options Menu .....................................................................................................356
10.7.2 Common statistic fields ...................................................................................... 356
10.7.3 The standard tab ................................................................................................ 357
10.7.3.1 Search fields ......................................................................................................357
10.7.3.2 Result columns .................................................................................................. 358
10.7.3.2.1 Observation point type: Circuit ........................................................................... 358
10.7.3.2.2 Observation point type: Faulty AFTN ................................................................. 360
10.7.3.2.3 Observation point type: OVF ............................................................................. 360
10.7.4 The traffic relation tab ........................................................................................ 361
10.7.4.1 Search fields ......................................................................................................361
10.7.4.2 Result columns .................................................................................................. 362
10.7.5 The address tab ................................................................................................. 363
10.7.5.1 Search fields ......................................................................................................363
10.7.5.2 Result columns .................................................................................................. 364
10.7.6 The day23 tab ....................................................................................................364
10.7.6.1 Search fields ......................................................................................................364
10.7.6.2 Result columns .................................................................................................. 365

 Avitech GmbH 2018 Page 22 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.7 The AMC tab ......................................................................................................366


10.7.7.1 Search fields ......................................................................................................366
10.7.7.2 Result columns .................................................................................................. 367
10.7.7.2.1 AMC Definition: MTA ......................................................................................... 367
10.7.7.2.2 AMC Definition: MTAPeak ................................................................................. 368
10.7.8 The channel offline tab ...................................................................................... 370
10.7.8.1 Search fields ......................................................................................................370
10.7.8.2 Result columns .................................................................................................. 371
10.7.9 The application offline tab .................................................................................. 372
10.7.9.1 Search fields ......................................................................................................372
10.7.9.2 Result columns .................................................................................................. 373
10.7.10 The annex A tab - Switching Time Statistics ..................................................... 373
10.7.10.1 Search fields ......................................................................................................374
10.7.10.2 Result columns .................................................................................................. 374
10.7.11 The annex B tab - Circuit Statistics .................................................................... 375
10.7.11.1 Search fields ......................................................................................................375
10.7.11.2 Result columns .................................................................................................. 375
10.7.12 The annex D tab - Circuit Occupancy Statistics ................................................ 376
10.7.12.1 Search fields ......................................................................................................377
10.7.12.2 Result columns .................................................................................................. 377
10.7.13 The annex G tab - Circuit Availability Statistics ................................................. 378
10.7.13.1 Search fields ......................................................................................................378
10.7.13.2 Result columns .................................................................................................. 379
10.7.14 The annex I tab - Detailed Operational Statistics .............................................. 380
10.7.14.1 Search fields ......................................................................................................380
10.7.14.2 Result columns .................................................................................................. 381
10.7.15 The annex J tab - Operational Statistics Summary ........................................... 382
10.7.15.1 Search fields ......................................................................................................382
10.7.15.2 Result columns .................................................................................................. 383
10.7.16 The annex K tab - Service Availability Statistics ................................................ 383
10.7.16.1 Search fields ......................................................................................................384
10.7.16.2 Result columns .................................................................................................. 384
10.7.17 The annex L tab - Daily OPMET Statistics ........................................................ 385
10.7.17.1 Search fields ......................................................................................................386
10.7.17.2 Result columns .................................................................................................. 386
10.8 User Management unit ...................................................................................... 387
10.8.1 Choose user ......................................................................................................387
10.8.2 Change password .............................................................................................. 387
10.8.3 Assign roles .......................................................................................................388
10.8.4 Assign pool ........................................................................................................388
10.8.5 User management functions .............................................................................. 389
10.8.5.1 File .....................................................................................................................389

 Avitech GmbH 2018 Page 23 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.8.5.2 Action .................................................................................................................389


10.8.5.3 Options ..............................................................................................................390
10.8.6 User management fields .................................................................................... 390
10.8.7 Change password .............................................................................................. 394
10.9 Legal Recording unit .......................................................................................... 394
10.9.1 The navigation tree ............................................................................................ 396
10.9.2 The Selection Tab .............................................................................................. 397
10.9.3 The Result List Tab ............................................................................................ 399
10.9.4 Legal recording functions ................................................................................... 400
10.9.4.1 File .....................................................................................................................400
10.9.4.2 Archive ...............................................................................................................401
10.9.4.3 Options ..............................................................................................................402
10.9.5 Archiving ............................................................................................................402
11 MESSAGE OFFICE MENU BAR BUTTON ...................................................... 403
11.1 Message Office functions .................................................................................. 403
11.1.1 File .....................................................................................................................403
11.1.2 Options ..............................................................................................................404
11.1.3 Context menus ...................................................................................................405
11.1.3.1 Context menu of the Search node ..................................................................... 405
11.1.3.2 Context menu of the User Area node ................................................................ 406
11.1.3.3 Context menu of the Message Table ................................................................. 407
11.1.4 The search function ........................................................................................... 408
11.1.4.1 Functions ...........................................................................................................409
11.1.4.1.1 File .....................................................................................................................409
11.1.4.1.2 Options ..............................................................................................................409
11.1.4.2 Special Features ................................................................................................ 409
11.1.4.3 The General tab ................................................................................................. 410
11.1.4.4 The AFTN tab ....................................................................................................411
11.1.4.4.1 The Content tab ................................................................................................. 412
11.1.4.5 The AMHS tab ...................................................................................................413
11.1.4.5.1 The IPM tab .......................................................................................................414
11.1.4.5.2 The Ipn tab.........................................................................................................414
11.1.4.5.3 The Report tab ...................................................................................................415
11.1.4.5.4 The Probe tab ....................................................................................................416
11.1.4.5.5 Sub-tabs ............................................................................................................417
11.1.4.5.5.1 The IPM Details sub-tab.............................................................................. 417
11.1.4.5.5.2 The Ipn Details sub-tab ............................................................................... 418
11.1.4.5.5.3 The Probe Details sub-tab .......................................................................... 419
11.1.4.5.5.4 The Deliv. Envelope sub-tab ....................................................................... 421
11.1.4.5.5.5 The Subm. Envelope sub-tab ...................................................................... 422

 Avitech GmbH 2018 Page 24 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.4.5.5.6 The Submission Result sub-tab .................................................................. 424


11.1.5 The AFTN Channel Configuration ..................................................................... 425
11.1.5.1 Functions ...........................................................................................................425
11.1.5.1.1 File .....................................................................................................................425
11.1.5.2 Fields .................................................................................................................426
11.1.5.3 The General Settings tab ................................................................................... 426
11.1.5.4 The Channel Check Settings tab ....................................................................... 428
11.1.5.5 The SVC Settings tab ........................................................................................ 429
11.1.5.6 The TCP Device tab .......................................................................................... 430
11.1.6 The AMHS Channel Configuration .................................................................... 431
11.1.6.1 Functions ...........................................................................................................432
11.1.6.1.1 File .....................................................................................................................432
11.1.6.2 The General Settings tab ................................................................................... 432
11.1.6.3 The MTA Device tab .......................................................................................... 434
11.1.7 Autoprocess Profiles .......................................................................................... 435
11.1.7.1 Functions ...........................................................................................................435
11.1.7.1.1 File .....................................................................................................................435
11.1.7.2 Fields .................................................................................................................436
11.1.8 Online Message Monitor .................................................................................... 437
11.1.8.1 Functions ...........................................................................................................437
11.1.8.1.1 File .....................................................................................................................437
11.1.8.1.2 Options ..............................................................................................................438
11.1.8.2 The message monitoring ................................................................................... 438
11.1.9 AFTN Viewer .....................................................................................................439
11.1.10 AFTN Viewer .....................................................................................................439
11.1.10.1 Functions ...........................................................................................................440
11.1.10.1.1 File .....................................................................................................................440
11.1.10.1.2 Options ..............................................................................................................440
11.1.10.2 Fields .................................................................................................................440
11.1.10.3 AFTN Correction Position Viewer ...................................................................... 442
11.1.10.3.1 Specific functions ............................................................................................... 443
11.1.10.3.1.1 File ..............................................................................................................443
11.1.10.3.1.2 Options ........................................................................................................443
11.1.11 The AMHS Viewer unit ...................................................................................... 444
11.1.11.1 Functions ...........................................................................................................445
11.1.11.1.1 File .....................................................................................................................445
11.1.11.1.2 Options ..............................................................................................................445
11.1.11.2 The Message tab of the AMHS Viewer .............................................................. 446
11.1.11.3 The Details tab of the AMHS Viewer ................................................................. 447
11.1.11.4 The File tab of the AMHS Viewer ...................................................................... 451

 Avitech GmbH 2018 Page 25 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.11.5 The Traces tab of the AMHS Viewer ................................................................. 452


11.2 The Message Office unit .................................................................................... 453
11.2.1 The channel tree of the Message Office ............................................................ 453
11.2.1.1 The ID node .......................................................................................................454
11.2.1.2 The Correction Position node ............................................................................ 455
11.2.1.3 The Search node ............................................................................................... 455
11.2.1.4 The User Area node .......................................................................................... 456
11.2.2 The message table of the Message Office ........................................................ 456
11.2.3 The message preview of the Message Office .................................................... 458
12 OPTIONS MENU ............................................................................................... 460
13 WINDOW MENU ............................................................................................... 461
14 HELP MENU ...................................................................................................... 462
ANNEX A ABBREVIATIONS ............................................................................................. 463
ANNEX B KEYBOARD MAPPING .................................................................................... 467
B.1 List of values ......................................................................................................467
B.2 Java shortcuts ....................................................................................................467
B.2.1 JApplet - Inside an AviUnit (Java L&F) .............................................................. 467
B.2.2 Standard components ........................................................................................ 468
B.2.2.1 JButton (Java L&F) ............................................................................................ 468
B.2.2.2 JCheckBox (Java L&F) ...................................................................................... 468
B.2.2.3 JRadioButton (Java L&F) ................................................................................... 468
B.2.2.4 JToggleButton (Java L&F) ................................................................................. 469
B.2.2.5 JComboBox (Java L&F) ..................................................................................... 469
B.2.2.6 JList (Java L&F) ................................................................................................. 470
B.2.2.7 JSlider (Java L&F) ............................................................................................. 471
B.2.3 Structured components ...................................................................................... 471
B.2.3.1 JTable (Java L&F) ............................................................................................. 471
B.2.3.2 JTree (Java L&F) ............................................................................................... 473
B.2.4 Menu, toolbar, and tooltip components .............................................................. 474
B.2.4.1 JMenuBar (Java L&F) ........................................................................................ 474
B.2.4.2 JMenu (Java L&F) ............................................................................................. 475
B.2.4.3 JMenuItem (Java L&F) ...................................................................................... 475
B.2.4.4 JCheckBoxMenuItem (Java L&F) ...................................................................... 476
B.2.4.5 JRadioButtonMenuItem (Java L&F) ................................................................... 476
B.2.4.6 JPopupMenu (Java L&F) ................................................................................... 477
B.2.4.7 JToolBar (Java L&F) .......................................................................................... 477
B.2.4.8 JToolTip (Java L&F) .......................................................................................... 478
B.2.5 Text components ............................................................................................... 478
B.2.5.1 JTextField (Java L&F) ........................................................................................ 478
B.2.5.2 JTextArea (Java L&F) ........................................................................................ 479
B.2.5.3 JTextPane (Java L&F) ....................................................................................... 481
B.2.5.4 JEditorPane (Java L&F) ..................................................................................... 483

 Avitech GmbH 2018 Page 26 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.6 Containers: frames, windows, panes, and icons ............................................... 484


B.2.6.1 JDesktopPane (Java L&F) ................................................................................. 484
B.2.6.2 JOptionPane (Java L&F) ................................................................................... 486
B.2.6.3 JDialog (Java L&F) ............................................................................................ 486
B.2.6.4 JScrollPane (Java L&F) ..................................................................................... 487
B.2.6.5 JSplitPane (Java L&F) ....................................................................................... 487
B.2.6.6 JTabbedPane (Java L&F) .................................................................................. 488
B.2.6.7 JFrame (Java L&F) ............................................................................................ 489
B.2.6.8 JInternalFrame (Java L&F) ................................................................................ 489
B.2.6.9 JWindow (Java L&F) .......................................................................................... 490

 Avitech GmbH 2018 Page 27 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

1 INTRODUCTION

1.1 Purpose and scope


This manual is addressed to all users of the AviTerm system. It serves to become familiar
with the functions of the system and with existing possibilities of use. It provides information
for the daily operation.
Note: This manual shows all possible function the MCU can handle. According to
the configuration of your system some functions may not be available and some of
the screenshots shown in the next sections and chapters may differ from what you
will see on your display.

1.2 Referenced documents


No referenced documents.

1.3 Abbreviations
The list of abbreviations can be found in ANNEX A.

 Avitech GmbH 2018 Page 28 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

2 BASIC SKILLS

2.1 Introduction

2.1.1 Starting the application / Web Start technology


The Java Web Start technology is used for the deployment of the AviTerm. It works with any
browser and with any Web server. The main feature of this technology is the ability to
automatically download and install the application and / or the latest updates on the client
user machines.
A prerequisite to run the application is to have Java installed. Please contact the system
administrator for details on supported Java versions. The system administrator can also give
details on the information needed to connect to the web start server.

2.1.2 How to login


After having started AviTerm, a login window is presented to the operator.

After a successful login a splash screen is displayed during start-up of the application and
then the AviTerm main framework appears.

 Avitech GmbH 2018 Page 29 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

After a successful initialization and start-up the available units are presented to the operator.
The icon bar gives a quick access to the most needed functions. The menu bar gives all
available functions (units).
AviTerm is designed in MDI (Multiple Document Interface) concept. It is possible to start
several units within one main framework.
Each unit can only be started once within the framework. "Closing" a framework only ends
the displaying of the screen. Opening this unit again will display it as it was before it was
closed; if some parameters were already entered, they will be taken over by the next display
of the unit.
Each unit has its own menu bar and an icon bar for quick access to its main functions.
Shortcuts are only available in the framework.

2.1.3 Navigation
Title
Each unit has a title line at its top.
Menu
The menu bars of the framework and of the units contain the topics that can be
selected.
Screen navigation
Various elements such as lists, tabbed panes, combo boxes and single fields are
used in units. Please check the section: Keyboard mapping of this chapter for further
details.

 Avitech GmbH 2018 Page 30 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Popup
A popup is a display area that appears in a screen, overlaying the existing display. A
popup generally indicates which input is expected, provides navigation information
and, when necessary, indicates warnings / errors. A popup contains one of the
following:
• A list of choices.
• An information message, a warning message or an error message.

2.2 Printing mechanism


The printing mechanism follows this philosophy:
• The data loaded or entered in the screen from which the print command is selected
will be printed out
In each application two different print functions are available. One prints data directly and
one shows a preview of the data that would be printed.
Print
Using the print function will print the data currently displayed on the screen. e.g.:
• In case of a report retrieval the function will print the search criteria
• In case of a report result the function will print the report result itself
Clicking on the [Print]-button prints the data on the default printer.
Print Choice
Clicking on the Print Choice command in the File menu will open the printer dialogue
in order to choose the printer before the data is printed out.
Print Preview
The Preview command opens a new window which shows the current contents of the
form as it would appear if it were printed out. To use this functionality the form does
not need to be completely filled out.
The print out can be started directly from the print preview window. Clicking on the
[Print]-button or selecting Print in the File menu prints the form immediately to the
default printer. Selecting Print Choice in the File menu opens the printer dialogue.
After having selected the printer the current contents of the form will be printed out.

 Avitech GmbH 2018 Page 31 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

2.3 Finders
A finder is a sub window that opens to help the operator choose some particular data.
Depending on the kind of data that is searched for, the finder has two or three parts.

2.3.1 Functions
New
Clears the complete Finder.
Search
Executes the search function.
Ok
Loads the selected contents into the unit.
Cancel
Closes the finder.

2.3.2 Special function calling a finder


Fields linked to a list of values that open a finder will have a grey triangle in the upper left
corner when the cursor is placed on it. For more information about how this function can be
used please refer to the section Keyboard mapping of this chapter.

 Avitech GmbH 2018 Page 32 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

2.3.3 Fields
Filter part
The fields listed here are used as search filter to limit the search results. A detailed
description of the filter fields can be found in the respective field sections of the units.
List part
After a search is performed the results are displayed in the list. The columns of the
list differ according to the kind of contents searched for.
Message Information part
Selecting an item from the Listing will display the message in AFTN format in this
preview field.

2.4 Chooser
A chooser is a sub window that opens to help the operator choose some particular data.
There are two types of choosers:
• the list of value chooser
• the general chooser

2.4.1 The list of value chooser

This chooser opens if the operator uses the [F4]-key in one field related to a list of values. It
is composed of two parts: the filter area allows the operator to filter the template list
according to the characters typed in this area, the list area displays the various choices
offered to the operator.

 Avitech GmbH 2018 Page 33 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

2.4.2 Special function calling a list of value chooser


Fields linked to a list of values that open a chooser will have a blue square in the upper left
corner. For more information about how this function can be used please refer to the section
Keyboard mapping of this chapter.

2.5 Drop down menu


The main AviTerm window of the terminal unit contains following drop down menus.

2.5.1 The File menu

Exit
Closes the application.

2.5.2 The Events menu

Event Monitor
Opens the Event Monitor function.
Event Configuration
Opens the Event Configuration function.

2.5.3 The Command menu

Command
Opens the Command function.
Macro
Opens the Macro function.

 Avitech GmbH 2018 Page 34 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

2.5.4 The Status Information menu

Circuit and Queue Monitor


Opens the Circuit and Queue Monitor function.
AFTN Connection State Monitor
Opens the AFTN Connection State Monitor.

2.5.5 The Report menu

Overflow Queue
Opens the Overflow Queue report.
Message Router Queue
Opens the Message Router Queue report.
Address Diversion
Opens the Address Diversion report.
Direction Diversion
Opens the Direction Diversion report.

 Avitech GmbH 2018 Page 35 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Queue Summary
Opens the Queue Summary report.
Channel Settings
Opens the Channel Settings report.
Channel State
Opens the Channel State report.
Queue Detail
Opens the Queue Detail report.
CSN Midnight
Opens the CSN Midnight report.
AFTN Test Message
Opens the AFTN Test Message report.

2.5.6 The configuration menu

System configuration
Opens the System Configuration.

2.5.7 The Management menu

Traffic Monitor
Opens the Traffic Monitor function.
Message Retrieval
Opens the Message Retrieval.

 Avitech GmbH 2018 Page 36 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Archive
Opens the Archive unit.
Channel Maintenance
Opens the Channel Maintenance function.
AMHS Channel Configuration
Opens the AMHS Channel Configuration mask.
MTA Device Configuration
Opens the MTA Device Configuration mask.
Statistics
Opens the Statistics function.
User Management
Opens the User Management unit.
Legal Recording
Opens the Legal Recording unit.

2.5.8 The Options menu

Enable Tool Tips


Enables or disables the tool tips in the AviTerm application.

2.5.9 The Window menu

Close All
Closes automatically all units open in the AviTerm application.
Minimize All
Minimizes automatically all units open in the AviTerm application.
Restore All
Restores automatically all units open in the AviTerm application.
Pack All
Restores the original size of all units open in the AviTerm application.

 Avitech GmbH 2018 Page 37 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

2.5.10 The Help menu

Launch Help
Launches the general help file. For more detailed information please refer to the
chapter Help Menu.
?
Activates the context sensitive help function. For more detailed information please
refer to the chapter Help Menu.
About
Gives information about the copyright and the current version number of the
application.

 Avitech GmbH 2018 Page 38 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

3 THE DASHBOARD

The dashboard displays information about the system and is continuously updated. It is
always in the front, can be moved within the main framework window and can never be
closed or minimised.

3.1 Dashboard items


Cluster State
The server which name is written in bold is the master and the other server is in hot
standby mode and ready to become master at any time.
Received
The total number of messages received today by the message handling system from
AMHS and AFTN.
Sent
The total number of messages sent today by the message handling system via
AMHS and AFTN.
To Read
The number of messages addressed to the COM centre that have not yet been
processed. If there are messages to read the background colour of the counter is
yellow. If at least one of these messages has the priority SS the background colour of
the counter is red. It remains red until all SS messages have been read.
The operator should open the Message Office to read and process the messages
received.
Correction
The number of faulty messages that needs to be processed by correcting or deleting
them.
The operator should open the Message Office to read and process the messages
received in the correction node.

 Avitech GmbH 2018 Page 39 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

SVC
The number of AFTN service message that could not be processed automatically and
needs to be processed by the operator.
The value of SVC the counter is updated in cycles. The default cycle period is 30
seconds.
NDR
The number of AMHS non-delivery reports received by the system.
Alarms
The number of outstanding alarms to be read and processed.
The operator should open the event monitor to read and process the alarms.
Events
The number of unread events of minor criticality, generated by the system.
The operator should open the event monitor to read and process the event.
Circuit State
The circuit state section provides a multi-status view for connection, queue and
message states per circuit. Fully operational or manually closed circuits will not be
displayed here, because such circuits do not request any operator interventions, i.e.
in best case nothing is displayed here.
If the observed circuit state presents at least one of the following criteria, the circuit is
displayed in the list with corresponding indicators switched on and is updated if any
state change happens. The circuit is then considered as suspicious.
• Queue threshold value 2 is reached.
• "Message Overdue In Queue" event happened.
• Automatic diversion has been started.
• The circuit is stalled and no message is transmitted.
• All channels are blocked.
The individual circuit state indicators used are:
Circuit
The name of the circuit.
Moving the mouse pointer over one of the circuit name displays detailed
connection state information in text form as well as the last state change date
and time of the corresponding channels.
Queue
The graphical visualisation of the queued messages.
Moving the mouse pointer over the queue visualisation displays the date and
time at which the channel became suspicious.
Total
The total number of messages in the circuit queue.

 Avitech GmbH 2018 Page 40 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Overdue
The number of overdue messages in the circuit queue.
Moving the mouse pointer over the overdue value displays a tool tip with
information, such as the priority and the date and time of the oldest overdue
message in the queue.
A message is considered overdue when it is older than the timers defined in
the configuration for this circuit.
If there are overdue messages in a queue and this situation is unusual and not
caused by any other preceding operator action, the operator should open the
circuit and queue monitor to work on the resolution of this situation.
If necessary, the operator should divert the circuit.
If the configured threshold 3 (red coloured bar) has been reached, and no
overdue message is in a queue, the circuit status seems OK. The queue
seems to have been overloaded. The operator can monitor the queue status
for a while, to see whether it is a temporary situation or not. In addition the
operator can check the thresholds configured for that queue, the available
bandwidth or take other measures to avoid this situation in the future.

 Avitech GmbH 2018 Page 41 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

4 FILE MENU

Exit
Closes the application.

 Avitech GmbH 2018 Page 42 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5 SYSTEM MESSAGES MENU

5.1 The Event Monitor function

The event monitor is used by the operator to view events, alarms and warnings issued by the
operational software. A detailed list of the different system events can be found in section
List of events of this chapter.
The event monitor is divided in two parts:
• The upper part lists the events received.
• The lower part displays the selected event in more details.

5.1.1 Functions

5.1.1.1 File Menu

Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.

 Avitech GmbH 2018 Page 43 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Mark As Read
Marks the selected events as read.
Clear Alarm
Removes the alarm from the selected event.
Close
Closes the Unit.

5.1.1.2 Navigation Menu

First Alarm
Navigates to the first alarm of the table.
Previous Alarm
Navigates to the previous alarm in the table.
Next Alarm
Navigates to the next alarm in the table.
Last Alarm
Navigates to the last alarm of the table.

5.1.1.3 Options Menu

Show Toolbar
Hides or displays the toolbar.

5.1.2 Fields

5.1.2.1 The events table


All events that have been generated by the system are stored in a database and displayed in
this table. Each line corresponds to one event and shows the time, the name and the
category of the event.

 Avitech GmbH 2018 Page 44 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The newest events are displayed at the top of the list, the oldest at the bottom. The list is
updated each time a new event is created.
Upper table row
This row displays general information about the contents of the table.
Freeze checkbox
If this checkbox is ticked events generated during this time will not be
displayed in the table. A counter next to the Freeze-checkbox indicates the
number of new generated events. Removing the tick of the Freeze-checkbox
displays the new generated events in the table and actualises all other
counters.
Alarms
This counter displays the number of alarms in the table.
Unread
This counter displays the number of unread events in the table.
Count
This counter displays the number of events currently visible in the table and
the total number of events in the table. It is useful when a filter is set.
Table
Time
The date and time when the event was created by the system.
Alarm
If an alarm has been defined for the selected event an icon is displayed in this
column.
Info
supplementary information about the type of event if available.
Event
The name of the event.
Summary
Parameters of the event. Depending on the event the parameters displayed in
this field will be different.
Category
The category to which the event belongs.
• INFO
• WARNING
• NORMAL
• MEDIUM
• SEVERE

 Avitech GmbH 2018 Page 45 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.1.2.2 The event display


It shows the selected event. A detailed list of all events and parameters can be found in
section List of events of this chapter.

5.2 The Event Configuration function

The event configuration allows the operator to define all relevant information concerning
events. A detailed list of the different system events can be found in section List of events

5.2.1 Functions

5.2.1.1 File Menu

Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Reload
Reloads the data. All unsaved changes will be lost.

 Avitech GmbH 2018 Page 46 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Save
Saves the changes.
Close
Closes the unit.

5.2.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

5.2.2 Fields
Event
The name of the event. This field cannot be changed.
Category
The category to which the event belongs.
• INFO
• WARNING
• NORMAL
• MEDIUM
• SEVERE
Display
Ticking this checkbox will display the event in the event monitor each time it is
generated by the system.
Note: An event, which is not displayed, will nevertheless be written to the event log.
Alarm
Ticking this checkbox will display an alarm each time the system generates this
event.
Acoustic
Ticking this checkbox will trigger an acoustic alarm each time the system generates
this event.
Read
Ticking this checkbox will automatically mark the event as read as it is displayed on
the event monitor
Autoprint
If the name of a printer is entered in this field, the system event will be printed
automatically on this printer each time it is issued.
eMail
If an e-mail address is entered in this field, the system event will be sent automatically
to this address each time it is issued.

 Avitech GmbH 2018 Page 47 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Reset Event
Defining a "Reset Event" for an event will reset/acknowledge the event's alarm status
(if any) when the defined "Reset Event" occurs.
Example:
The event AFTN_THRESHOLD_3 is defined as follows:
• Alarm: ticked
• Reset Event: AFTN_RESET_THRESHOLD_3
When the event AFTN_THRESHOLD_3 occurs, an alarm is displayed.
When the event AFTN_RESET_THRESHOLD_3 occurs, the alarm of
the previous AFTN_THRESHOLD_3 event is removed automatically.

5.3 List of events

5.3.1 General events

5.3.1.1 AFTN_CHANNEL_CONN_STATE

5.3.1.1.1 Description
Gives the new connection state of a channel.

5.3.1.1.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID

 Avitech GmbH 2018 Page 48 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Connection State
The connection state of channel. Possible values:
• CONN_BY_HOST
• CONN_BY_REMOTE
• DISCONNECTED
• UNKNOWN
Info
Additional information.

5.3.1.1.3 Necessary Actions


None.

5.3.1.2 CHANNEL_STATE

5.3.1.2.1 Description
Gives the new state of a channel.

5.3.1.2.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.

 Avitech GmbH 2018 Page 49 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Channel State
The state of the channel:
• BLOCKED
• CLOSED
• CLOSE_INPUT
• DEAD
• HOLD
• OPEN
• TEST
• UNKNOWN
Priority
The priority concerned

5.3.1.2.3 Necessary Actions


If CH_STATE is BLOCKED, check the reason. Check the connection between the switch and
the channel.

 Avitech GmbH 2018 Page 50 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.3 CIRCUIT_STATE

5.3.1.3.1 Description
Gives the new state of a circuit.

5.3.1.3.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Circuit State
The state of the circuit:
• OPERATIVE
• INOPERATIVE

5.3.1.3.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 51 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.4 COMPONENT_CONTROL

5.3.1.4.1 Description
• The component couldn't update the keep alive timer within 20 seconds.
• The component could update the keep alive timer again.

5.3.1.4.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Component
The component that failed or that is up again. Possible values:
• AFTN
• AMHS
• AMHSRV
• CIDIN
• FEC
• TERMSERV
Component State
The component status. Possible values:
• DOWN: not operative
• INIT: initialize
• OUT_CNTRL: not operative, the keep alive timer couldn't be updated within
the last 20 seconds
• RUNNING: operative
Host Name
The name of the computer hosting the application.

 Avitech GmbH 2018 Page 52 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.4.3 Necessary Actions


If the Component State parameter is OUT_CNTRL, contact your system administrator.

5.3.1.5 COMPONENT_STATE

5.3.1.5.1 Description
Status change of a component.

5.3.1.5.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Component
The component that failed or that is up again. Possible values:
• AFTN
• TERMSERV
• CIDIN
• AMHS
• FEC
• AMHSRV
Component State
The component status. Possible values:
• DOWN: not operative
• INIT: initialize
• OUT_CNTRL: not operative, the keep alive timer couldn't be updated within
the last 20 seconds
• RUNNING: operative
Host Name
The name of the computer hosting the application.

 Avitech GmbH 2018 Page 53 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.5.3 Necessary Actions


If the Component State parameter is DOWN, inspect the SYSLOG entries in a UNIX
window (hpterm, terraterm or putty).
When this event with the Component State parameter DOWN is sent, the application will
automatically be restarted, which will then send a series of component state messages for
each start-up phase i.e. for INIT, READY and RUNNING.

5.3.1.6 GENERAL_DATA_CHECK

5.3.1.6.1 Description
Cyclic internal check of configuration data shows a consistency error.

5.3.1.6.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Information
Information text about the error.

5.3.1.6.3 Necessary Actions


Contact Avitech GmbH immediately.

5.3.1.7 GENERAL_ERROR

5.3.1.7.1 Description
An error has been found in one of the applications.

5.3.1.7.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created

 Avitech GmbH 2018 Page 54 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Component
The component that failed or that is up again. Possible values:
• AFTN
• AMHS
• AMHSRV
• CIDIN
• FEC
• TERMSERV
Error Number
The internal number assigned to this error. The name of the error is given in the
parameter Information.
Process
The name of the process which found the error. This is a hint for the Avitech staff in
case it is contacted.
Function
The function in the process. This is a hint for the Avitech staff in case it is contacted.
Process Id
The Unix process identifier. This is a hint for the Avitech staff in case it is contacted.
Information
The name or the description of the error.

5.3.1.7.3 Necessary Actions


This event may be accompanied by a COMPONENT_STATE event. If this system message
occurs frequently, it may be necessary to inform the maintenance staff or to contact Avitech
GmbH.

5.3.1.8 MSG_OVERDUE_IN_QUEUE

5.3.1.8.1 Description
This event is generated for each message that is getting overdue and staying in the queue.
So in case the handling for overdue messages is in a way that the message leaves the
queue, no event shall be generated. The flag 'overdue' is to be set to TRUE in case the
message is turning overdue and FALSE in case a previously overdue message is no longer
overdue due to configuration changes that have changed the overdue timers in a way that
the message is no longer overdue. Note that no event is to be generated when an overdue
message leaves the queue by 'normal' means (i.e. it is delivered to the client)

5.3.1.8.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created

 Avitech GmbH 2018 Page 55 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Internal MID
The internal message identifier of the message.
External MID
The External message identifier of the message.
Priority
The priority concerned
Overdue
• TRUE: the message is turning overdue.
• FALSE: the message is no longer overdue.

5.3.1.8.3 Necessary Actions


None.

5.3.1.9 MESSAGE_QUEUE_NOT_EMPTY

 Avitech GmbH 2018 Page 56 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.9.1 Description
Cyclic internal check of configuration data shows a consistency error.

5.3.1.9.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Type Of Queue
The type of the queue. Possible values:
• Circuit message queue
• Channel queue
• Input queue

5.3.1.9.3 Necessary Actions


Empty the circuit queue by ensuring that the channel is connected or by diverting the circuit.

5.3.1.10 MESSAGE_STATE

5.3.1.10.1 Description
The state of a message has changed.

 Avitech GmbH 2018 Page 57 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.10.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
IMID
The internal message identifier of the message
Message State
The state of the message. Possible values:
• PAUSED
• RESUMED
• ABANDONED

5.3.1.10.3 Necessary Actions


None.

5.3.1.11 RESOURCE_BOTTLENECK

5.3.1.11.1 Description
The number of new circuits exceeds the maximum number of new circuits allowed configured
in the setup.

 Avitech GmbH 2018 Page 58 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.1.11.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Information
Information text about the problem.

5.3.1.11.3 Necessary Actions


Initialize the list bundle and restart the system.

5.3.1.12 SITA_GENERAL_INFORMATION

5.3.1.12.1 Description
Information about SITA Messages. This system event is generated when:
• A SITA service message is received or generated by the MHS
• A MATIP Open Confirm receive timer is expired
• A MATIP Session Open receive timer is expired

5.3.1.12.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Key
The key of the information displayed. Possible values:
• STAT
• CONTCK
• SRLVAL
• SRLERR
• FORMERR
• RPTALL
• RPTBTN
• RPTONE

 Avitech GmbH 2018 Page 59 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Direction
The direction of the message. Possible values:
• INCOMING
• OUTGOING
Information
Supplementary information

5.3.1.12.3 Necessary Actions


None

5.3.1.13 X25_PORT_CHECK

5.3.1.13.1 Description
Status change of an X.25 port.

5.3.1.13.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Component
The component that failed or that is up again. Possible values:
• AFTN
• AMHS
• AMHSRV
• CIDIN
• FEC
• TERMSERV
Link
The logical name of the X.25 interface port.
Status
The status of the X.25 port. Possible values:
• AVAILABLE
• UNAVAILABLE

5.3.1.13.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 60 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.2 AMS Events

5.3.2.1 AMS_ACT_L_ERROR

5.3.2.1.1 Description

5.3.2.1.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Error description
The description of error situation

5.3.2.1.3 Necessary Actions


Contact your system administrator or Avitech GmbH.

5.3.2.2 AMS_LIST_TRANSFER

5.3.2.2.1 Description
The action "Transfer bundle" in the Bundle menu of the Configuration service has been
initiated.

5.3.2.2.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
List Version
The list version.
Action Item
The status of the action "Transfer bundle".

 Avitech GmbH 2018 Page 61 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.2.2.3 Necessary Actions


End_Transmission
• The new list version can now be activated by executing the "ACT_L NEW"
command.
Error_transmission_of_lists_not_successful
Database server problem.
• Execute the "Reset transfer" action in the Bundle menu of the Configuration
service.
• Try to reach the applications AFTN, CIDIN and AMHS by executing the
"REQUEST" command. If the request command is successfully executed and
the application response is positive - event "COMPONENT_STATE" AFTN /
CIDIN / AMHS running - try to transfer the list again. If the response is still
negative or the request command cannot be executed, contact Avitech
GmbH.

5.3.3 SFM Events

5.3.3.1 SFM_AUTO_ADDRESS_DIVERSION

5.3.3.1.1 Description
An automatic address diversion was activated or deactivated.

5.3.3.1.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
State
Indicates if the diversion had been activated or deactivated.
Source Circuit
The origin circuit identifier.
Source Device Type.
The type of the origin device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT

 Avitech GmbH 2018 Page 62 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• TAS
• TCP
• X25
Target Circuit
The target circuit.
Target Device Type
The type of the target device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Priorities
The diverted priorities.

5.3.3.1.3 Necessary Actions


None.

5.3.3.2 SFM_AUTO_DIRECTION_DIVERSION

5.3.3.2.1 Description
An automatic direction diversion was activated or deactivated.

5.3.3.2.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).

 Avitech GmbH 2018 Page 63 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
State
Indicates if the diversion had been activated or deactivated.
Source Circuit
The origin circuit identifier.
Source Device Type
The type of the origin device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Target Circuit
The target circuit.
Target Device Type
The type of the target device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Priorities
The diverted priorities.

 Avitech GmbH 2018 Page 64 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.3.2.3 Necessary Actions


None.

5.3.3.3 SFM_BACKWARDS_RELAY_DONE

5.3.3.3.1 Description
A message has been relayed back to the station from which it was received. This is
permitted in the appropriate logical target entry.

5.3.3.3.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Device Type
The type of the device of the addressee. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Circuit Name
The circuit identifier of the addressee.

 Avitech GmbH 2018 Page 65 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Transmission ident
The external message identification of the message sent.
Message mid intern
The internal message identification of the message sent. The format of an internal
message identification is in the following form: <N>3.<N>10.<N>4

5.3.3.3.3 Necessary Actions.


None.

5.3.3.4 SFM_BACKWARDS_RELAY_STRIPPED

5.3.3.4.1 Description
An addressee has been stripped from the addresses in a message. This address would have
caused backwards routing and the backwards-relaying indicator in the logical target list is set
to S and does not allow this.

5.3.3.4.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Device Type
The type of the device of the addressee. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Circuit Name
The circuit identifier of the addressee.
Transmission ident
The external message identification of the message sent.

 Avitech GmbH 2018 Page 66 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Message mid intern


The internal message identification of the message sent. The format of an internal
message identification is of the following form: <N>3.<N>10.<N>4

5.3.3.4.3 Necessary Actions


None.

5.3.3.5 SFM_CYCLIC_PDAI

5.3.3.5.1 Description
An entry in the predetermined distribution list causes address recursion when a message
with this PDAI is routed.

5.3.3.5.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
PDAI
The predetermined address indicator, which caused recursion.
Transmission ident
The external message identification of the message received by the switch.
Message mid intern
The internal message identification of the message received by the switch. The
format of an internal message identification is of the following form: <N>3.<N>10.<N>4

5.3.3.5.3 Necessary Actions


Check the entry of the PDAI in the AFTN routing list.

5.3.3.6 SFM_MANUAL_ADDRESS_DIVERSION

5.3.3.6.1 Description
A manual address diversion was activated or deactivated.

5.3.3.6.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
State
Indicates if the diversion had been activated or deactivated.

 Avitech GmbH 2018 Page 67 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Source Circuit
The origin circuit identifier.
Source Device Type
The type of the origin device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Target Circuit
The target circuit.
Target Device Type
The type of the target device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
MCD circuit
The circuit for multi circuit distribution, if any.
MCD Device Type
The device for multi circuit distribution, if any.
Priorities
The diverted priorities.

 Avitech GmbH 2018 Page 68 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.3.6.3 Necessary Actions


None.

5.3.3.7 SFM_MANUAL_DIRECTION_DIVERSION

5.3.3.7.1 Description
An automatic direction diversion was activated or deactivated.

5.3.3.7.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
State
Indicates if the diversion had been activated or deactivated.
Source Circuit
The origin circuit identifier.
Source Device Type
The type of the origin device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

 Avitech GmbH 2018 Page 69 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Target Circuit
The target circuit.
Target Device Type
The type of the target device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
MCD circuit
The circuit for multi circuit distribution, if any.
MCD Device Type
The device for multi circuit distribution, if any.
Priorities
The diverted priorities.

5.3.3.7.3 Necessary Actions


None.

5.3.3.8 SFM_MESSAGE_QUEUE_STALLED

5.3.3.8.1 Description
The output queue specified in the message parameters is not empty but no messages have
been sent from that queue within a specific interval of time. This event can only be displayed
when the monitoring of a queue by the Message Router has been defined during the
installation application.

 Avitech GmbH 2018 Page 70 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.3.8.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Queue
The identifier of the queue.

5.3.3.8.3 Necessary Actions


Observe the queue specified in the event. If the problem persists call Avitech GmbH.

5.3.3.9 SFM_MESSAGE_STORE_DELETE

5.3.3.9.1 Description
This message indicates, that database which contains a message store has been deleted.
This message is sent during the preparations for switching the message stores at midnight.
Message stores older than a certain number of days (default: 30 days) will be deleted at
midnight.

5.3.3.9.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Delete State
The success or the failure of the deletion. Possible values:
• DATABASE_DELETED.
• UNABLE_TO_DELETE.
Database User
The name database user who deletes the database.

5.3.3.9.3 Necessary Actions


This depends on the value of the parameter Delete State:
DATABASE_DELETED
No actions are required.

 Avitech GmbH 2018 Page 71 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

UNABLE_TO_DELETE
This can have two causes:
• a software error.
• a user is still logged on to a service, which uses the database.
If the problem persists, call Avitech GmbH.

5.3.3.10 SFM_MESSAGE_STORE_FAILURE

5.3.3.10.1 Description
Error during preparations for the Midnight Changeover.

5.3.3.10.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Store Hint
The error. Possible values:
• DISCONNECT_YESTERDAY_ORDER_TIMEOUT (int. value = 9): One or
more processes have not been disconnected from the YESTERDAY
database. The system will be closed down and restarted. For a system in
which only the short-term store is held online: a YESTERDAY archive was not
written.
• CREATE_MESSAGE_STORE_NEXT_DAY_NOT_OK (int. value = 10): The
TODAY database for the coming day could not be created. The system will be
restarted.
Database User
The name of the database.

5.3.3.10.3 Necessary Actions


If this event is recurrent call Avitech GmbH.

5.3.3.11 SFM_MESSAGE_STORE_ORDER

5.3.3.11.1 Description
Preparation for the Midnight Changeover.

 Avitech GmbH 2018 Page 72 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.3.11.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Order
Indication of the action carried out:
• DISCONNECT_YESTERDAY_ORDERED (intern value = 1).The processes
have been ordered to disconnect from the YESTERDAY database.
• DISCONNECT_YESTERDAY_EXECUTED (intern value = 2). The Processes
have all disconnected from the YESTERDAY database.
• BACKUP_YESTERDAY_STARTED (intern value = 3). The archiving of the
YESTERDAY database has started.
• BACKUP_YESTERDAY_FINISHED (intern value = 4). The archiving of the
YESTERDAY database has finished.
• MESSAGE_STORE_YESTERDAY_DELETED (int. value = 5). The
YESTERDAY database has been deleted.
• MESSAGE_STORE_NEXT_DAY_CREATED (int. value = 6). The TODAY
database for the coming day has been created.
• MESSAGE_STORE_TODAY_NOT_FOUND (int. value = 7). A TODAY
database could not be found during system initialization, a new TODAY
database will be created.
• MESSAGE_STORE_TODAY_CREATED (intern value = 8). The new TODAY
database has been created.
Database User
The name of the database.

5.3.3.11.3 Necessary Actions


None.

5.3.3.12 SFM_RECURRENT_ROUTING

5.3.3.12.1 Description
The AFTN addressee indicator in a message is mapped by the AFTN Routing list to a target,
which, through a sequence of diversions, has been diverted back to itself. The message will
be routed to this diversion.

5.3.3.12.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).

 Avitech GmbH 2018 Page 73 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
Destination
The address, which could not be resolved.
Target Circuit
The target circuit of the addressee.
Target Device Type
The target device of the addressee.
Transmission ident
External message identification of the message.
Message mid intern
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4

5.3.3.12.3 Necessary Actions


Use the SHO_DIVD command to check the existing direction diversions.

5.3.3.13 SFM_THRESHOLD

5.3.3.13.1 Description
This system event is used when the values of both the message router (MR) single queue
thresholds and the pool thresholds reach the defined values.

5.3.3.13.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Queue
The name of the queue for which a threshold has been passed.
Threshold State
The possible state of the threshold. Possible values:
• ABOVE
• BELOW

 Avitech GmbH 2018 Page 74 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Threshold
The number of the threshold passed. Possible values:
• Threshold1
• Threshold2
• Threshold3

5.3.3.13.3 Necessary Actions


In case of pool threshold 3 exceedance, the queues should be checked and may be diverted.

5.3.4 AFTN Events

5.3.4.1 AFTN_ACCESS_VIOLATION

5.3.4.1.1 Description
An unknown user has tried to set up a connection.

5.3.4.1.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

 Avitech GmbH 2018 Page 75 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Violation Reason
Reason for the violation. Possible values:
• UNKNOWN
• CLOSED
• BLOCKED

5.3.4.1.3 Necessary Actions


If the user is:
UNKNOWN
Check whether the user is known but has no entry in the appropriate configuration
list.
CLOSED
The connection can be opened (if required) using the OPEN_CHAN command.
BLOCKED
The channel of the user can be blocked because of a diversion or because of a fault
such as an Answerback failure.

5.3.4.2 AFTN_ANSWERBACK_FAILURE

5.3.4.2.1 Description
A channel has sent no answerback at all or an incorrect answerback either during the
connection phase before the message is sent or during the control phase after the message
has been sent.

5.3.4.2.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX

 Avitech GmbH 2018 Page 76 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Transmission Type
Type of message Transmission. Possible values:
• CONNECT: No answerback or incorrect answerback was sent during the
connection phase before the sending of a message
• SEND: No answerback or incorrect answerback was sent during the control
phase after a message has been sent.
• RECEIVE: No answerback or incorrect answerback was sent during the
control phase after a message has been received.
Answerback Norm
The answerback string stored in the AFTN channel configuration list.
Answerback Received
The answerback string received or TIMEOUT, when no answerback has been
received in time.
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
External MID
External message identification of the message.

5.3.4.2.3 Necessary Actions


If this failure occurs permanently, compare the answerback string stored in the Channel
Mode tab with the answerback string defined in the AFTN end device. Check the end device.

5.3.4.3 AFTN_BREAK_DURING_OUTPUT

5.3.4.3.1 Description
A user has pressed the BREAK key to interrupt the output of a message from the computer
and typed in a message himself. The outgoing message will automatically be repeated after
the incoming message has been completed.

5.3.4.3.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created

 Avitech GmbH 2018 Page 77 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
External MID

5.3.4.3.3 Necessary Actions


None

5.3.4.4 AFTN_CHANNEL_GARBAGE_INFORMATION

5.3.4.4.1 Description
Messages with severe errors and fragments have been received. These messages have
been sent to the correction position and the channel has been closed automatically.

 Avitech GmbH 2018 Page 78 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.4.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Number of Messages
Number of received messages with severe errors and/or fragments.
Time Diff
Time interval (in minutes) between the fragments received.

5.3.4.4.3 Necessary Actions


Check the received messages in the correction position.
When the messages have been handled re-open the circuit.

5.3.4.5 AFTN_DTG_FAILURE

5.3.4.5.1 Description
A message with an incorrect DTG (date time group) has been received.

 Avitech GmbH 2018 Page 79 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.5.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Received DTG
The Day time group received.
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4

5.3.4.5.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 80 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.6 AFTN_FEC_STATE

5.3.4.6.1 Description
State of the Front End Computer.

5.3.4.6.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
FEC Unit
Unit of the front end computer. Possible Values:
• 1
• 2
FEC state
State of the front end computer. Possible Values:
• CONNECTED
• DISCONNECTED
• MASTER

5.3.4.6.3 Necessary Actions


None.

5.3.4.7 AFTN_MESSAGE_QUEUE_STALLED

5.3.4.7.1 Description
An output queue is not empty but no message has been sent from that queue within a time
interval specified in the configuration list of the channel concerned by this event.

 Avitech GmbH 2018 Page 81 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.7.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.7.3 Necessary Actions


None.

5.3.4.8 AFTN_NO_CONNECTION_ESTABLISHED

5.3.4.8.1 Description
An output queue is not empty but no message has been sent from that queue within a time
interval specified in the configuration list of the channel concerned by this event.

 Avitech GmbH 2018 Page 82 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.8.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Connection Event
The connection event. Possible values:
• CLEAR
• CONNECT_TIMEOUT
• D_BIT_CONFIRMATION_TIMEOUT
• INTERRUPT
• IOCONTROL_FAILURE
• LEVEL_2_DOWN
• PORT_FAILURE
• RESET
• RESTART

 Avitech GmbH 2018 Page 83 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Direction
The direction. Possible values:
• INCOMING
• OUTGOING
Diagnostics
Diagnostic code of the X.25 packet concerned (cause / diagno from X.25).

5.3.4.8.3 Necessary Actions


Check the physical connection between switch and channel. Check the corresponding
channel list. If needed inform the maintenance staff.

5.3.4.9 AFTN_NO_DIAL_CONNECTION

5.3.4.9.1 Description
No dial connection can be opened.

5.3.4.9.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC

 Avitech GmbH 2018 Page 84 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• MCP
• SIT
• TAS
• TCP
• X25
Reason
The reason for the dial problem. Possible values:
• NO_TERMINALSERVER_CONNECTION
• MODEM_FAILURE=NO_CARRIER
• MODEM_FAILURE=ERROR
• MODEM_FAILURE=NO DIALTONE

5.3.4.9.3 Necessary Actions


NO_TERMINALSERVER_CONNECTION
The connection to a terminal server could not be established. Check the terminal
server connection.
MODEM_FAILURE=NO_CARRIER
No connection established or inactivity timer expired. Check the modem connection.
MODEM_FAILURE=ERROR
Error during command input. Check the modem.
MODEM_FAILURE=NO DIALTONE
No dial tone detected. Check the line.

5.3.4.10 AFTN_OLDEST_MESSAGE_IN_QUEUE

5.3.4.10.1 Description
The oldest message in an output queue has been held there too long.

5.3.4.10.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).

 Avitech GmbH 2018 Page 85 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Subject Message IMID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
Subject Message EMID
External message identification of the message.
Priority
Priority of the message. Possible values: FF, GG, KK, DD, SS.
Original target
The original target AFTN address of the message.
Original device
The original target device type of the message.

5.3.4.10.3 Necessary Actions


Examine the contents of the queue with SHO_QUE. If the message has not been sent
because of messages of a higher priority no action can be taken. Otherwise divert the queue.

5.3.4.11 AFTN_OMA_FAILURE

5.3.4.11.1 Description
The oldest message in an output queue has been held there too long.

 Avitech GmbH 2018 Page 86 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.11.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Failure Type
The type of the failure. Possible values:
• TIMEOUT
• NAC
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
External MID
External message identification of the message.

5.3.4.11.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 87 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.12 AFTN_QUEUE_OVERFLOW_STARTED

5.3.4.12.1 Description
The oldest message in an output queue has been held there too long.

5.3.4.12.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.12.3 Necessary Actions


This message is sent when the size of a queue reaches threshold level 3. When this
happens, the system moves as many messages from the queue (according to their priority
and age) to the overflow store until the reset threshold 3 is reached. According to their
priority and age means that the most recent messages with the lowest priority are moved.
If this message occurs frequently change the queue threshold parameters in the appropriate
configuration list.

 Avitech GmbH 2018 Page 88 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.13 AFTN_RECEIVE_TIMEOUT

5.3.4.13.1 Description
A message was not completely received within the specified time.

5.3.4.13.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit from which the message came.
Channel Name
The name of the channel from which the message came.
Device Type
The type of the device from which the message came. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
External MID
External message identification of the message.

5.3.4.13.3 Necessary Actions


The UDC or the connection between the UDC and the computer is not working. Switch to a
different UDC and inform the maintenance personnel.

 Avitech GmbH 2018 Page 89 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.14 AFTN_SS_MESSAGE_IN_QUEUE

5.3.4.14.1 Description
The "Oldest message priority SS" timer for an outgoing queue has been reached and the SS
message is still not sent.

5.3.4.14.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit from which the SS message has not yet been sent.
Channel Name
The name of the channel from which the SS message has not yet been sent.
Device Type
The type of the device from which the SS message has not yet been sent. Possible
values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4

5.3.4.14.3 Necessary Actions


Check the queue to find out why the SS message has not been sent. Open the channel,
open the circuit or divert the queue in order to solve this problem.

 Avitech GmbH 2018 Page 90 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.15 AFTN_SVC_CAUSED_BY_FAULTY_MSG

5.3.4.15.1 Description
An SVC was generated caused by a faulty Message.

5.3.4.15.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit on which the SVC message has been generated.
Channel Name
The name of the channel on which the SVC message has been generated.
Device Type
The type of the device on which the SVC message has been generated. Possible
values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
SVC_TYPE
The type of SVC generated.
MID SVC
Internal message identification of the SVC generated. The format of an internal
message identification is of the following form: <N>3.<N>10.<N>4
External MID SVC
External message identification of the SVC generated.
MID faulty Message
Internal message identification of the faulty message. The format of an internal
message identification is of the following form: <N>3.<N>10.<N>4

 Avitech GmbH 2018 Page 91 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.15.3 Necessary Actions


None.

5.3.4.16 AFTN_SVC_GENERATED

5.3.4.16.1 Description
The system has generated an SVC message.

5.3.4.16.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit on which the SVC message has been generated.
Channel Name
The name of the channel on which the SVC message has been generated.
Device Type
The type of the device on which the SVC message has been generated. Possible
values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
SVC Text
The text of the SVC message generated.

 Avitech GmbH 2018 Page 92 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.16.3 Necessary Actions


None.

5.3.4.17 AFTN_SVC_RECEIVED

5.3.4.17.1 Description
The system has received an SVC message.

5.3.4.17.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit from which the SVC message has been received.
Channel Name
The name of the channel from which the SVC message has been received.
The type of the device from which the SVC message has been received. Possible
values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
SVC Text
The text of the SVC message received.

 Avitech GmbH 2018 Page 93 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.17.3 Necessary Actions


None.

5.3.4.18 AFTN_TESTMESSAGE_HANDLING

5.3.4.18.1 Description
Gives the status of the test messages monitoring cycle.

5.3.4.18.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Number Of Messages
The number of message
Handling Reason
The reason for this event. Possible values:
TEST MESSAGE RECEIVED, CYCLE STARTED
Start of a cycle because of the reception of a first test message

 Avitech GmbH 2018 Page 94 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

NO FURTHER TEST MESSAGE RECEIVED IN THIS CYCLE


End of a cycle because no new test message has been received for a certain
period of time defined in the system parameters.
FURTHER TEST MESSAGE RECEIVED, NEW CYCLE STARTED
Start of a new cycle because of the reception of new test messages after the
former cycle has ended.
CYCLE TO RECEIVE TEST MESSAGES STOPPED
End of the test messages monitoring.
TEST MESSAGES OF THIS CYCLE ARE DISCARDED FROM NOW
Too many test messages have been received in a too short period of time or
too many test messages have been received within one cycle. The following
test messages will be automatically deleted from the system as soon as they
are received, and this until the end of the cycle. The test messages thus
deleted will not be stored in the database.
TEST MESSAGES DELETED, PRESERVATION TIME EXHAUSTED
The defined retention time has expired. The test messages held in the
database will be automatically deleted.
Information
Supplementary information about test message deletion.

5.3.4.18.3 Necessary Actions


None.

5.3.4.19 AFTN_THRESHOLD_1

5.3.4.19.1 Description
AFTN Queue Threshold Message. The number of messages in a queue (circuit) has reached
Threshold Value 1 (defined in the configuration list).

5.3.4.19.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.

 Avitech GmbH 2018 Page 95 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.19.3 Necessary Actions


None.

5.3.4.20 AFTN_THRESHOLD_2

5.3.4.20.1 Description
AFTN Queue Threshold Message. The number of messages in a queue (circuit) has reached
Threshold Value 2 (defined in the configuration list).

5.3.4.20.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID

 Avitech GmbH 2018 Page 96 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.20.3 Necessary Actions


None.

5.3.4.21 AFTN_THRESHOLD_3

5.3.4.21.1 Description
AFTN Queue Threshold Message. The number of messages in a queue (circuit) has reached
Threshold Value 3 (defined in the configuration list).

5.3.4.21.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT

 Avitech GmbH 2018 Page 97 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• TAS
• TCP
• X25

5.3.4.21.3 Necessary Actions


In case of a "<XXX>_WS_POOL Threshold 3 ABOVE" event (where XXX = TCP | DIO | FAX
| FEC | TAS | X25), the operator should check the queues and may divert it to the overflow.
This should not occur because of the 'automatic threshold 3 handling.

5.3.4.22 AFTN_RESET_THRESHOLD_1

5.3.4.22.1 Description
The number of messages in a queue (circuit) has reached the reset Threshold Value 1 (after
having reached Threshold Value 1 before) that was defined in the configuration list.

5.3.4.22.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

 Avitech GmbH 2018 Page 98 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.22.3 Necessary Actions


None.

5.3.4.23 AFTN_RESET_THRESHOLD_2

5.3.4.23.1 Description
The number of messages in a queue (circuit) has reached the reset Threshold Value 2 (after
having reached Threshold Value 2 before) that was defined in the configuration list.

5.3.4.23.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.23.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 99 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.24 AFTN_RESET_THRESHOLD_3

5.3.4.24.1 Description
The number of messages in a queue (circuit) has reached the reset Threshold Value 3 (after
having reached Threshold Value 3 before) that was defined in the configuration list.

5.3.4.24.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.24.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 100 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.4.25 AFTN_TID_FAILURE

5.3.4.25.1 Description
A message with an unexpected Transmission Identifier has been received.
The transmission identifier consists of the MTP followed by the CSN. If one or both
components are not correct the system generates an AFTN TID FAILURE event. If the
message contains only this error it will still be transmitted, otherwise it will be sent to the
correction position.
• If only the MTP was wrong or mutilated, the system corrects it automatically before
forwarding the message.
• If only the CSN was wrong or mutilated, the system corrects it automatically before
forwarding the message.
• If only the MTP and the CSN were wrong or mutilated, the system corrects both of
them automatically before forwarding the message.
The system increments the CSN and messages following a message that initiates an AFTN
TID FAILURE event will be handled as usual.

5.3.4.25.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit of the sender.
Channel Name
The name of the channel of the sender.
Device Type
The type of the device of the sender. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX

 Avitech GmbH 2018 Page 101 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• FEC
• MCP
• SIT
• TAS
• TCP
• X25
Received TID
The transmission identifier received.
Expected TID
The transmission identifier expected.
Subject message IMID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4

5.3.4.25.3 Necessary Actions


Check the configuration. The possible problems can be:
• The MTP ID configured between user and centre is not the same.
• The CSN length configured between user and centre is not the same.

5.3.4.26 AFTN_TRANSFER_ERROR

5.3.4.26.1 Description
An error occurred while sending or receiving messages via a channel.

5.3.4.26.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit of the sender.
Channel Name
The name of the channel of the sender.
Device Type
The type of the device of the sender. Possible values:
• AIS
• AMH
• CID
• DIO

 Avitech GmbH 2018 Page 102 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

5.3.4.26.3 Necessary Actions


Check hardware.

5.3.4.27 AFTN_UNEXPECTED_MSG_RECEIVED

5.3.4.27.1 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.
Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25

 Avitech GmbH 2018 Page 103 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Channel state
The state of the channel. Possible values:
• BLOCKED
• CLOSED
• CLOSE_INPUT
• DEAD
• HOLD
• OPEN
• TEST
• UNKNOWN
AFTN Msg. Type
The type of the message. Possible values:
• MESSAGE
• TESTMESSAGE
Internal MID
Internal message identification of the message. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
External MID
External message identification of the message.

5.3.4.28 AFTN_X25_EVENT

5.3.4.28.1 Description
The X.25 software has reported an unexpected event (reset, restart or clear) during a
message transfer.

5.3.4.28.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm,
removed...).
Generation Time
The date and time when the event was created
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.

 Avitech GmbH 2018 Page 104 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Device Type
The type of the device. Possible values:
• AIS
• AMH
• CID
• DIO
• FAX
• FEC
• MCP
• SIT
• TAS
• TCP
• X25
X25 Link
The identifier of the X.25 interface card.
Logical Channel
The logical channel (X.25).
X25 Event
The type of X.25 event. Possible Values:
• RESET
• RESTART
• CLEAR
Direction
The direction of the message. Possible values:
• INCOMING
• OUTGOING
Diagnostics
Diagnostic code of the X.25 packet concerned (cause / diagno from X.25).

5.3.4.28.3 Necessary Actions


None.

5.3.5 AMHS Events

5.3.5.1 AMHSRV_INFORMATION

5.3.5.1.1 Description
Information about errors in the AMHS retrieval.

 Avitech GmbH 2018 Page 105 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.5.1.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Information
Information text about the error.

5.3.5.1.3 Necessary Actions


Contact Avitech GmbH.

5.3.5.2 AMHS_IPN_RECEIVED

5.3.5.2.1 Description
Receipt Notification received.

5.3.5.2.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
AMHS Cause
The AMHS cause. Possible values:
• ACTUAL_RECIPIENT_DIFFERS_FROM_ORIG_INTENDED_RECIPIENT
• MTE_PRIO_DIFFERENT_FROM_URGENT
• NON_RECEIPT_NOTIFICATION
• NO_RECEIPT_NOTIFICATION_REQUESTED
• NO_REPORTED_RECIPIENT
• REPORTED_RECIPIENT_NOT_TRANSLATABLE_TO_AFTN_ADDRESS
• SUBJECT_MESSAGE_HAD_NOT_PRIO_SS
• SUBJECT_MESSAGE_NOT_FOUND
• SUBJECT_MESSAGE_NOT_UNIQUE
• UNEXPECTED_DIAGNOSTIC_CODE
MTS Identifier
MTS identifier (max. 109 character).
Subject Internal MID
Internal message identifier of subject message (24 char). The format of an internal
message identification is of the following form: <N>3.<N>10.<N>4

 Avitech GmbH 2018 Page 106 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Originator OR address
Originator O/R address of RN (max. 977 char) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
Subject IPM Identifier
IPM identifier of subject message (max. 1009 char).

5.3.5.2.3 Necessary Actions


None.

5.3.5.3 AMHS_MSG_TRANSL_ORIG_NON_SYMMETRIC

5.3.5.3.1 Description
The MTCU has received an AMHS message with an originator address that cannot be
translated into an AFTN address in a symmetric way. The AFTN address is not re-convertible
or the result of the reconversion is different from the originator address as contained in the
received AMHS message.

5.3.5.3.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
MTS Identifier
The MTS identifier (max. 110 character).
Internal MID
The internal message identifier. The format of an internal message identification is of
the following form: <N>3.<N>10.<N>4

 Avitech GmbH 2018 Page 107 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Received OR Address
Originator O/R address of RN (max. 977 char) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
AFTN Address
The AFTN address (8 characters).
Retranslated OR Address
The AMHS O/R address as the result of the re-translation of the AFTN address.

5.3.5.3.3 Necessary Actions


Check whether the address look-up tables (MD, CAAS, User Address) are in line with the
ICAO registry (ATS Messaging Management Centre AMC).
Check the MTS-Identifier to identify the MD in which the AMHS message has been created.
If such asymmetry indication occurs more often, inform the AMC.

5.3.5.4 AMHS_MSG_TRANSL_RCP_NON_SYMMETRIC

5.3.5.4.1 Description
The MTCU has received an AMHS message with a recipient address which cannot be
translated into an AFTN address in a symmetric way. The AFTN address is not re-convertible
or the result of the reconversion is different from the recipient address as contained in the
received AMHS message.

5.3.5.4.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created

 Avitech GmbH 2018 Page 108 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

MTS Identifier
The MTS identifier (max. 110 character).
Internal MID
The internal message identifier. The format of an internal message identification is of
the following form: <N>3.<N>10.<N>4
Recipient OR Address
The OR address of the recipient as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
AFTN Address
The AFTN address (8 characters).
Retranslated OR Address
The AMHS O/R address as the result of the re-translation of the AFTN address.

5.3.5.4.3 Necessary Actions


Check whether the address look-up tables (MD, CAAS, User Address) are in line with the
ICAO registry (ATS Messaging Management Centre AMC).
Check the MTS-Identifier to identify the MD in which the AMHS message has been created.
If such asymmetry indication occurs more often, inform the AMC.

5.3.5.5 AMHS_MTA_SESSION_INFO

5.3.5.5.1 Description
Information on the opening of an MTS session.

5.3.5.5.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created

 Avitech GmbH 2018 Page 109 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Information
• MTA SESSION COULD NOT BE OPEN
• MTA SESSION COULD NOW BE OPEN

5.3.5.5.3 Necessary Actions


If the message "MTA session could not be open" appears check the MTA functions or
contact your administrator.

5.3.5.6 AMHS_MTCU_INFORMATION

5.3.5.6.1 Description
Software error in the MTCU.

5.3.5.6.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Information
Description of the error

5.3.5.6.3 Necessary Actions


Contact Avitech GmbH.
Note: If the MTCU cannot open a session to the MTA the AMHS button will turn to blue.

5.3.5.7 AMHS_NON_DELIVERY_REPORT_CREATED

5.3.5.7.1 Description
Non Delivery Report created.

5.3.5.7.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
AMHS Cause
The AMHS cause. Possible values:
• ACTUAL_RECIPIENT_DIFFERS_FROM_ORIG_INTENDED_RECIPIENT
• MTE_PRIO_DIFFERENT_FROM_URGENT
• NON_RECEIPT_NOTIFICATION
• NO_RECEIPT_NOTIFICATION_REQUESTED

 Avitech GmbH 2018 Page 110 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• NO_REPORTED_RECIPIENT
• REPORTED_RECIPIENT_NOT_TRANSLATABLE_TO_AFTN_ADDRESS
• SUBJECT_MESSAGE_HAD_NOT_PRIO_SS
• SUBJECT_MESSAGE_NOT_FOUND
• SUBJECT_MESSAGE_NOT_UNIQUE
• UNEXPECTED_DIAGNOSTIC_CODE
MTS Identifier
MTS identifier (max. 67 characters).
Reason
The reason. Possible values:
• ADDRESS_MISMATCH
• RECEIPIENTS_MODIFIED
• SUBJECT_UNIDENTIFIED
• TRANSMISSION_FAILURE
• UNKNOWN_RECIPIENT_MODIFIED
Diagno
The AMHS diagnostic code. Possible values:
• NO_DIAGNOSTIC
• OR_NAME_UNRECOGNIZED
• OR_NAME_AMBIGUOUS
• MTS_CONGESTED
• LOOP_DETECTED
• RECIPIENT_UNAVAILABLE
• MAXIMUM_TIME_EXPIRED
• EITS_UNSUPPORTED
• CONTENT_TOO_LONG
• IMPRACTICAL_TO_CONVERT
• PROHIBITED_TO_CONVERT
• CONVERSION_UNSUBSCRIBED
• PARAMETERS_INVALID
• CONTENT_SYNTAX_IN_ERROR
• LENGTH_CONSTRAINT_VIOLAT
• NUMBER_CONSTRAINT_VIOLATD
• CONTENT_TYPE_UNSUPPORTED
• TOO_MANY_RECIPIENTS
• NO_BILATERAL_AGREEMENT

 Avitech GmbH 2018 Page 111 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• CRITICAL_FUNC_UNSUPPORTED
• CONVERSION_LOSS_PROHIB
• LINE_TOO_LONG
• PAGE_TOO_LONG
• PICTORIAL_SYMBOL_LOST
• PUNCTUATION_SYMBOL_LOST
• ALPHABETIC_CHARACTER_LOST
• MULTIPLE_INFO_LOSSES
• REASSIGNMENT_PROHIBITED
• REDIRECTION_LOOP_DETECTED
• EXPANSION_PROHIBITED
• SUBMISSION_PROHIBITED
• EXPANSION_FAILED
• RENDITION_UNSUPPORTED
• MAIL_ADDRESS_INCORRECT
• MAIL_OFFICE_INCOR_OR_INVD
• MAIL_ADDRESS_INCOMPLETE
• MAIL_RECIPIENT_UNKNOWN
• MAIL_RECIPIENT_DECEASED
• MAIL_ORGANIZATION_EXPIRED
• MAIL_REFUSED
• MAIL_UNCLAIMED
• MAIL_RECIPIENT_MOVED
• MAIL_RECIPIENT_TRAVELLING
• MAIL_RECIPIENT_DEPARTED
• MAIL_NEW_ADDRESS_UNKNOWN
• MAIL_FORWARDING_UNWANTED
• MAIL_FORWARDING_PROHIB
• SECURE_MESSAGING_ERROR
• DOWNGRADING_IMPOSSIBLE
Subject MTS Identifier
MTS-Id of subject message (max. 109 char).
Actual Recipient
Reported (actual) recipient's O/R address (max. 977 char) as:
• Country name.
• /ADMD name.

 Avitech GmbH 2018 Page 112 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
Originally Intended Recipient
The originally intended recipient's O/R address (max. 977 char) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
Supplementary Info
Supplementary information

5.3.5.7.3 Necessary Actions


None.

5.3.5.8 AMHS_NON_DELIVERY_REPORT_RECEIVED

5.3.5.8.1 Description
Non Delivery Report received.

5.3.5.8.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
AMHS Cause
The AMHS cause. Possible values:
• ACTUAL_RECIPIENT_DIFFERS_FROM_ORIG_INTENDED_RECIPIENT
• MTE_PRIO_DIFFERENT_FROM_URGENT
• NON_RECEIPT_NOTIFICATION
• NO_RECEIPT_NOTIFICATION_REQUESTED
• NO_REPORTED_RECIPIENT
• REPORTED_RECIPIENT_NOT_TRANSLATABLE_TO_AFTN_ADDRESS
• SUBJECT_MESSAGE_HAD_NOT_PRIO_SS
• SUBJECT_MESSAGE_NOT_FOUND

 Avitech GmbH 2018 Page 113 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• SUBJECT_MESSAGE_NOT_UNIQUE
• UNEXPECTED_DIAGNOSTIC_CODE
MTS Identifier
MTS identifier (max. 67 characters).
Reason
The reason. Possible values:
• ADDRESS_MISMATCH
• RECEIPIENTS_MODIFIED
• SUBJECT_UNIDENTIFIED
• TRANSMISSION_FAILURE
• UNKNOWN_RECIPIENT_MODIFIED
Diagno
The AMHS diagnostic code. Possible values:
• NO_DIAGNOSTIC
• OR_NAME_UNRECOGNIZED
• OR_NAME_AMBIGUOUS
• MTS_CONGESTED
• LOOP_DETECTED
• RECIPIENT_UNAVAILABLE
• MAXIMUM_TIME_EXPIRED
• EITS_UNSUPPORTED
• CONTENT_TOO_LONG
• IMPRACTICAL_TO_CONVERT
• PROHIBITED_TO_CONVERT
• CONVERSION_UNSUBSCRIBED
• PARAMETERS_INVALID
• CONTENT_SYNTAX_IN_ERROR
• LENGTH_CONSTRAINT_VIOLAT
• NUMBER_CONSTRAINT_VIOLATD
• CONTENT_TYPE_UNSUPPORTED
• TOO_MANY_RECIPIENTS
• NO_BILATERAL_AGREEMENT
• CRITICAL_FUNC_UNSUPPORTED
• CONVERSION_LOSS_PROHIB
• LINE_TOO_LONG
• PAGE_TOO_LONG

 Avitech GmbH 2018 Page 114 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• PICTORIAL_SYMBOL_LOST
• PUNCTUATION_SYMBOL_LOST
• ALPHABETIC_CHARACTER_LOST
• MULTIPLE_INFO_LOSSES
• REASSIGNMENT_PROHIBITED
• REDIRECTION_LOOP_DETECTED
• EXPANSION_PROHIBITED
• SUBMISSION_PROHIBITED
• EXPANSION_FAILED
• RENDITION_UNSUPPORTED
• MAIL_ADDRESS_INCORRECT
• MAIL_OFFICE_INCOR_OR_INVD
• MAIL_ADDRESS_INCOMPLETE
• MAIL_RECIPIENT_UNKNOWN
• MAIL_RECIPIENT_DECEASED
• MAIL_ORGANIZATION_EXPIRED
• MAIL_REFUSED
• MAIL_UNCLAIMED
• MAIL_RECIPIENT_MOVED
• MAIL_RECIPIENT_TRAVELLING
• MAIL_RECIPIENT_DEPARTED
• MAIL_NEW_ADDRESS_UNKNOWN
• MAIL_FORWARDING_UNWANTED
• MAIL_FORWARDING_PROHIB
• SECURE_MESSAGING_ERROR
• DOWNGRADING_IMPOSSIBLE
Subject MTS Identifier
MTS-Id of subject message (max. 109 char).
Actual Recipient
Reported (actual) recipient's O/R address (max. 977 char) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).

 Avitech GmbH 2018 Page 115 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Originally Intended Recipient


The originally intended recipient's O/R address (max. 977 char) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
Supplementary Info
Supplementary information

5.3.5.8.3 Necessary Actions


None.

5.3.5.9 AMHS_PRB_TRANSL_ORIG_NON_SYMMETRIC

5.3.5.9.1 Description
The MTCU has received an AMHS probe with an originator address which cannot be
translated into an AFTN address in a symmetric way. The AFTN address is not re-convertible
or the result of the reconversion is different from the originator address as contained in the
received AMHS probe.

5.3.5.9.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
MTS Identifier
The MTS identifier (max. 110 character).
Originator OR Address
Originator O/R address of RN (max. 977 char) as:
• Country name.
• /ADMD name.

 Avitech GmbH 2018 Page 116 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
AFTN Address
The AFTN address (8 characters).
Retranslated OR Address
The AMHS O/R address as the result of the re-translation of the AFTN address.

5.3.5.9.3 Necessary Actions


Check whether the address look-up tables (MD, CAAS, User Address) are in line with the
ICAO registry (ATS Messaging Management Centre AMC).
Check the MTS-Identifier to identify the MD in which the AMHS message has been created.
If such asymmetry indication occurs more often, inform the AMC.

5.3.5.10 AMHS_PRB_TRANSL_RCP_NON_SYMMETRIC

5.3.5.10.1 Description
The MTCU has received an AMHS probe with a recipient address which cannot be translated
into an AFTN address in a symmetric way. The AFTN address is not re-convertible or the
result of the reconversion is different from the recipient address as contained in the received
AMHS probe.

5.3.5.10.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
MTS Identifier
The MTS identifier (max. 110 character).
Recipient OR address
The OR address of the recipient as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).
AFTN Address
The AFTN address (8 characters).

 Avitech GmbH 2018 Page 117 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Retranslated OR Address
The AMHS O/R address as the result of the re-translation of the AFTN address.

5.3.5.10.3 Necessary Actions


Check whether the address look-up tables (MD, CAAS, User Address) are in line with the
ICAO registry (ATS Messaging Management Centre AMC).
Check the MTS-Identifier to identify the MD in which the AMHS message has been created.
If such asymmetry indication occurs more often, inform the AMC.

5.3.5.11 AMHS_RECIPIENT_REACHABLE

5.3.5.11.1 Description
The AMHS Recipient can be reached.

5.3.5.11.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
AFTN Address
The AFTN address (8 character).
OR Address
The O/R address (max. 977 characters) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).

5.3.5.11.3 Necessary Actions


None.

5.3.5.12 AMHS_RECIPIENT_UNREACHABLE

5.3.5.12.1 Description
The AMHS Recipient cannot be reached.

5.3.5.12.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).

 Avitech GmbH 2018 Page 118 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
AFTN Address
The AFTN address (8 character).
OR Address
The O/R address (max. 977 characters) as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).

5.3.5.12.3 Necessary Actions


None.

5.3.5.13 AMHS_RPT_TRANSL_REP_RCP_NON_SYMMETRIC

5.3.5.13.1 Description
The MTCU has received an AMHS report with a reported recipient address which cannot be
translated into an AFTN address in a symmetric way. The AFTN address is not re-convertible
or the result of the reconversion is different from the reported recipient address as contained
in the received AMHS report.

5.3.5.13.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
MTS Identifier
The MTS identifier (max. 110 character).
Subject MTS Identifier
The MTS identifier of the subject message (max. 110 character).
Reported Recipient
The OR address of the recipient as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.

 Avitech GmbH 2018 Page 119 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• /Organization unit name.


• /Domain-defined attributes (ICAO address).
AFTN Address
The AFTN address (8 characters).
Retranslated OR Address
The AMHS O/R address as the result of the re-translation of the AFTN address.

5.3.5.13.3 Necessary Actions


Check whether the address look-up tables (MD, CAAS, User Address) are in line with the
ICAO registry (ATS Messaging Management Centre AMC).
Check the MTS-Identifier to identify the MD in which the AMHS message has been created.
If such asymmetry indication occurs more often, inform the AMC.

5.3.5.14 AMHS_SS_ACKNOWLEDGEMENT_RECEIVED

5.3.5.14.1 Description
An SS Acknowledgement received from AMHS.

5.3.5.14.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
AMHS_Cause
The AMHS Cause. Possible values
• SUBJECT_MESSAGE_NOT_FOUND
• SUBJECT_MESSAGE_NOT_UNIQUE
• NO_RECEIPT_NOTIFICATION_REQUESTED
• MTE_PRIO_DIFFERENT_FROM_URGENT
• SUBJECT_MESSAGE_HAD_NOT_PRIO_SS
• REPORTED_RECIPIENT_NOT_TRANSLATABLE_TO_AFTN_ADDRESS
• ACTUAL_RECIPIENT_DIFFERS_FROM_ORIG_INTENDED_RECIPIENT
• UNEXPECTED_DIAGNOSTIC_CODE
• NO_REPORTED_RECIPIENT
• NON_RECEIPT_NOTIFICATION
Internal MID
The internal message identifier. The format of an internal message identification is of
the following form: <N>3.<N>10.<N>4

 Avitech GmbH 2018 Page 120 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Filing Time
Filing time.
Originator
Originator.
Subject Internal MID
Internal message identifier from subject. The format of an internal message
identification is of the following form: <N>3.<N>10.<N>4
Subject MTS Identifier
The MTS identifier.
Subject IPM Identifier
The IPM-identifier (max. 1009 char).

5.3.5.14.3 Necessary Actions


None.

5.3.5.15 AMHS_SS_MESSAGE_RECEIVED

5.3.5.15.1 Description
An AMHS SS Message has been received without a request for receipt notification or with
the MTS priority different from Urgent.

5.3.5.15.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
AMHS Cause
The AMHS cause. Possible values:
• ACTUAL_RECIPIENT_DIFFERS_FROM_ORIG_INTENDED_RECIPIENT
• MTE_PRIO_DIFFERENT_FROM_URGENT
• NON_RECEIPT_NOTIFICATION
• NO_RECEIPT_NOTIFICATION_REQUESTED
• NO_REPORTED_RECIPIENT
• REPORTED_RECIPIENT_NOT_TRANSLATABLE_TO_AFTN_ADDRESS
• SUBJECT_MESSAGE_HAD_NOT_PRIO_SS
• SUBJECT_MESSAGE_NOT_FOUND
• SUBJECT_MESSAGE_NOT_UNIQUE
• UNEXPECTED_DIAGNOSTIC_CODE

 Avitech GmbH 2018 Page 121 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

MTE Prio
Message transfer envelope priority (x.400 priority).
• Urgent
• Normal
• Non-Urgent
MTS Identifier
The MTS identifier (max. 109 chars).
IPM Identifier
The IPM-identifier (max. 1009 char).
Recipient OR address
The OR address of the recipient as:
• Country name.
• /ADMD name.
• /PRMD name.
• /Organization name.
• /Organization unit name.
• /Domain-defined attributes (ICAO address).

5.3.5.15.3 Necessary Actions


Identify the originator from the IPM identifier and inform him.

5.3.5.16 DISTRESS_MESSAGE_RECEIVED

5.3.5.16.1 Description
A distress message has been received.

5.3.5.16.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created.
Circuit Name
The name of the circuit.
Channel Name
The name of the channel.

 Avitech GmbH 2018 Page 122 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Device Type
The type of device. Possible values:
• TCP
• TAS
• DIO
• SIT
• X25
• FEC
• AIS
• MCP
• CID
• AMH
• MTA
• UA
• MS
Internal MID
The internal message identifier.
Text
The first 100 chars of message text.

5.3.5.16.3 Necessary Actions


Display the received message.

5.3.5.17 MTA_P1_CONNECTION_EVENT

5.3.5.17.1 Description
This event indicates a change or an error in the connection state of a P1 MTA.

 Avitech GmbH 2018 Page 123 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.5.17.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Event Type
The P1 connection event type. The different types are:
P1InitConnOK
Initiated connection succeeded
P1InitConnFail
Initiated connection failed
P1RespConnOK
Responder connection succeeded
P1RespConnFail
Responder connection failed
P1InitDiscOK
Initiator disconnected normally
P1InitAbort
Initiator aborted connection
P1InitReject
Initiator rejected responder's bind response
P1Unknown
Unknown connection termination
P1RespDiscOK
Responder normal disconnection
P1RespAbort
Responder aborted connection
Peer MTA
The MTA name of the peer.
Peer Presentation Address
The presentation address of the peer.
Peer Calling Address
The address of the peer used for the connection.
Local MTA
The name of our MTA.

 Avitech GmbH 2018 Page 124 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Local Presentation Address.


The presentation address of our MTA.
Association PID
The PID of the associated process.
Channel
The channel name.
Bind Type
The type of bind. Possible values:
• strong
• simple
Bidirectional
A flag determining whether or not the connection is bidirectional or not. Possible
values:
• MONO
• Bidirectional
Fail Reason
The reason for the failure, if any.

5.3.5.17.3 Necessary Actions


None.

5.3.5.18 MTA_P3_CONNECTION_EVENT

5.3.5.18.1 Description
This event indicates a change or an error in the connection state of a P3 MTA.

5.3.5.18.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).

 Avitech GmbH 2018 Page 125 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
Event Type
The P3 connection event type. The different types are:
P3InitConnOK
Initiated connection succeeded
P3InitConnFail
Initiated connection failed
P3RespConnOK
Responder connection succeeded
P3RespConnFail
Responder connection failed
P3InitDiscOK
Initiator disconnected normally
P3InitAbort
Initiator aborted connection
P3RespDiscOK
Responder normal disconnection
P3RespAbort
Responder aborted connection
Address
The O/R address of the connected P3 entity.
Device Type
The device type of the connected P3 entity. Possible values:
• UA
• MS
Association PID
The PID of the associated process.
Channel
The name of the channel serving the connected P3 entity.
Bidirectional
A flag determining whether or not the connection is bidirectional or not. Possible
values:
• MONO
• Bidirectional

 Avitech GmbH 2018 Page 126 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Fail Reason
The reason for the failure, if any.
Disconnect Status
Disconnect status

5.3.5.18.3 Necessary Actions


None.

5.3.6 CIDIN Events

5.3.6.1 CIDIN_CPSN_ERROR

5.3.6.1.1 Description
CIDIN has received a message with an illegal Packet Sequence Number.

5.3.6.1.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Reason
The identifier of the CIDIN subsystem which sent the message: CPS CIDIN protocol
stack. Possible values:
• DUPLICATE_CPSN
• FCP_IND_NOT_IN_LAST_SEG
CIDIN AX
CIDIN exit address.
MIN
Message identification number.

5.3.6.1.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 127 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.2 CIDIN_ENQ_FROM_UNKNOWN_AE_RCVD

5.3.6.2.1 Description
CIDIN Enquiry from unknown Entry Address received.

5.3.6.2.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AY
CIDIN entry address of the originator.

5.3.6.2.3 Necessary Actions


Contact the remote centre, which sent the erroneous message, if this network management
message occurs very often.
If the CIDIN switch receives a message from an unknown entry centre addressed to its own
exit address the message will be transmitted to the application layer for further processing
and sending to the appropriate destinations, but no acknowledgement will be sent to the
previous station or relay centre. The spontaneous message CIDIN_ILLEGAL_EXIT appears
on the system control board.
In this case no acknowledgement is sent to the sending station, the sending station repeats
the message once after acknowledgement time limit. Therefore the same message will be
transmitted twice to the destination addressee. After that the sending station stops repeating
the message and begins sending enquiries. For each received ENQ the spontaneous
message CIDIN_ILLEGAL_EXIT appears.

5.3.6.3 CIDIN_ENQ_RESP_FROM_UNKNOWN_AX_RCVD

5.3.6.3.1 Description
CIDIN Enquiry Response from unknown Exit Address received

 Avitech GmbH 2018 Page 128 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.3.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of the addressee.

5.3.6.3.3 Necessary Actions


Contact the remote centre, which sent the erroneous message, if this network management
message occurs very often.

5.3.6.4 CIDIN_EXIT_AVAILABLE

5.3.6.4.1 Description
An Exit address is now reachable.

5.3.6.4.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address, which can now be reached.
ENQ Count
The number of CIDIN network-management enquiry messages sent
ENQ_COUNT*TEM = time of not availability of the corresponding exit centre in
seconds. (TEM = see the CIDIN global parameter list).

5.3.6.4.3 Necessary Actions


None.
Remarks: See description of the event CIDIN_EXIT_UNAVAILABLE.

5.3.6.5 CIDIN_EXIT_UNAVAILABLE

5.3.6.5.1 Description
An Exit address is unreachable.

5.3.6.5.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).

 Avitech GmbH 2018 Page 129 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address, which is unavailable.
Remarks: AFTN messages, which cannot be transmitted because the
remote exit is not available, will be stored in the overflow storage. If the
corresponding exit centre becomes available, the stored message will be
transmitted automatically to this exit address and the event CIDIN EXIT
AVAILABLE will be generated.

5.3.6.5.3 Necessary Actions


If the remote exit centre is not available for a longer time check the physical connection or
call the remote exit centre.

5.3.6.6 CIDIN_GENERAL_INFORMATION

5.3.6.6.1 Description
Supplementary information concerning a call refusal.

5.3.6.6.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Virtual Circuit
The CIDIN virtual circuit.
Reason
Incoming call refused because of:
• UNKNOWN CALLING REMOTE CENTRE
• ALREADY CONNECTED
• CALL COLLISION

5.3.6.6.3 Necessary Actions


None.

5.3.6.7 CIDIN_ILLEGAL_EXIT

5.3.6.7.1 Description
CIDIN has received a message with an illegal Exit address.

 Avitech GmbH 2018 Page 130 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.7.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of the addressee.
CIDIN AY
CIDIN entry address of the originator.
Virtual Circuit
CIDIN virtual circuit.

5.3.6.7.3 Necessary Actions


Check the CIDIN routing table and / or the CIDIN virtual circuit list.
In case of ”illegal exit address” incoming messages, which cause this event to be displayed,
will be sent to the correction position. They cannot be retransmitted by the correction position
and must be deleted after they have been checked.
Such messages will not be written into the journal.

5.3.6.8 CIDIN_MCF_ERROR

5.3.6.8.1 Description
CIDIN reports an MCF-Error

5.3.6.8.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Internal MID
The internal message identification. The format of an internal message identification
is of the following form: <N>3.<N>10.<N>4

 Avitech GmbH 2018 Page 131 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CIDIN AX
CIDIN exit address of the addressee of the erroneous message.
CIDIN AY
CIDIN entry address of the originator of the erroneous message.
MIN
Message identification number of the erroneous message.
CPSN
CIDIN packet sequence number of the erroneous message.
MCF Error
MCF-Error. Possible values:
• MCF_CHANGED
• SEND_ERROR
• RCV_ERROR
MCF Code
MCF-Code (0 - 31) of the erroneous message.

5.3.6.8.3 Necessary Actions


Contact the remote centre, which sent the erroneous message. Check the CIDIN MCF
values in the CIDIN virtual circuit list.

5.3.6.9 CIDIN_PACKET_HDR_ERROR

5.3.6.9.1 Description
CIDIN Packet Header Error.

5.3.6.9.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Virtual Circuit
CIDIN virtual circuit.
CIDIN AY
CIDIN entry address of the originator.
MIN
Message identification number.

5.3.6.9.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 132 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.10 CIDIN_THRESHOLD_1

5.3.6.10.1 Description
CIDIN Queue Threshold Message: The number of messages in a queue (for Exit Address)
has reached Threshold Value 1.

5.3.6.10.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.

5.3.6.10.3 Necessary Actions


None.

5.3.6.11 CIDIN_THRESHOLD_2

5.3.6.11.1 Description
The number of messages in a queue (Exit Address) has reached Threshold Value 2.

5.3.6.11.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.

5.3.6.11.3 Necessary Actions


None.

5.3.6.12 CIDIN_THRESHOLD_3

5.3.6.12.1 Description
The number of messages in a queue (Exit Address) has reached Threshold Value 3.

5.3.6.12.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).

 Avitech GmbH 2018 Page 133 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.

5.3.6.12.3 Necessary Actions


None.

5.3.6.13 CIDIN_RESET_THRESHOLD_1

5.3.6.13.1 Description
The number of messages in a queue (Exit Address) has reached reset Threshold Value 1
(after having reached Threshold Value 1 before).

5.3.6.13.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.

5.3.6.13.3 Necessary Actions


None.

5.3.6.14 CIDIN_RESET_THRESHOLD_2

5.3.6.14.1 Description
The number of messages in a queue (Exit Address) has reached reset Threshold Value 2
(after having reached Threshold Value 2 before).

5.3.6.14.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.

5.3.6.14.3 Necessary Actions


None.

 Avitech GmbH 2018 Page 134 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.15 CIDIN_RESET_THRESHOLD_3

5.3.6.15.1 Description
The number of messages in a queue (circuit) has reached reset Threshold Value 3 (after
having reached Threshold Value 3 before)

5.3.6.15.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.

5.3.6.15.3 Necessary Actions


None.

5.3.6.16 CIDIN_TNMA_TIMEOUT

5.3.6.16.1 Description
A timeout has occurred during the reception of a CIDIN message.

5.3.6.16.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AX
CIDIN exit address of addressees.
CIDIN AY
CIDIN entry address of the originator.
MIN
Message identification number.

5.3.6.16.3 Necessary Actions


If this problem occurs often contact the entry centre.

5.3.6.17 CIDIN_TRANSPORT_HEADER_SYNTAX_ERROR

5.3.6.17.1 Description
CIDIN Transport Header Syntax Error.

 Avitech GmbH 2018 Page 135 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.17.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
CIDIN AY
CIDIN entry address of the originator.

5.3.6.17.3 Necessary Actions


Contact the remote centre, which sent the erroneous message, if this network management
message occurs very often.

5.3.6.18 CIDIN_USE_EQUAL_VIRTUAL_CIRCUIT

5.3.6.18.1 Description
CIDIN packets are transmitted on the virtual circuit they were received

5.3.6.18.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Virtual Circuit
CIDIN virtual circuit.
CIDIN AX
CIDIN exit address of addressees.
CIDIN AY
CIDIN entry address of the originator.
MIN
Message identification number

5.3.6.18.3 Necessary Actions


Check the configuration lists.

5.3.6.19 CIDIN_VC_STATE

5.3.6.19.1 Description
CIDIN Virtual Circuit State.

 Avitech GmbH 2018 Page 136 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

5.3.6.19.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created
Virtual Circuit
The CIDIN virtual circuit.
VC State
Status of the virtual circuit. Possible values:
• CONN_BY_HOST
• CONN_BY_REMOTE
• CONNECTING
• DISCONNECTED
• UNKNOWN
• WAITING_FOR_LINK
Reason
CIDIN virtual circuit reason. Possible values:
• IDLE TIMER TIMEOUT.
• CALL RETRY TIMER TIMEOUT.
• CONNECT TIMER TIMEOUT.
• TRANSFER ERROR BY OPERATOR COMMAND.

5.3.6.19.3 Necessary Actions


None.

5.3.6.20 CIDIN_X25_EVENT

5.3.6.20.1 Description
CIDIN X25 Event.

5.3.6.20.2 Parameters
Last Changed
The date and time when the status of the event was last modified (read, alarm
removed...).
Generation Time
The date and time when the event was created

 Avitech GmbH 2018 Page 137 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Virtual Circuit
CIDIN virtual circuit.
Link
The logical name of an X.25 interface port. The values are defined in the X25
properties of the X.25 devices.
X25 Event
The X25-event. Possible values:
• CLEAR
• CONNECT_TIMEOUT
• D_BIT_CONFIRMATION_TIMEOUT
• INTERRUPT
• IOCONTROL_FAILURE
• LEVEL_2_DOWN
• PORT_FAILURE
• RESET
• RESTART
Direction
The direction. Possible Values:
• INCOMING
• OUTGOING.
Diagnostics
Diagnostic code.

5.3.6.20.3 Necessary Actions


See above.

 Avitech GmbH 2018 Page 138 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6 COMMAND MENU

6.1 The Command function

This unit allows the operator to issue commands to the system. A detailed list of all system
commands and parameters can be found in section List of commands of this chapter.
The Command unit is divided in two parts:
• The upper part lists the commands entered manually or edited by the operator.
• The lower part displays the last commands issued to the system.

6.1.1 Function

6.1.1.1 File

Clear Command
Clears the upper part of the Command unit.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.

 Avitech GmbH 2018 Page 139 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Edit Command
The command selected in the lower part is displayed in the upper part to allow the
operator to edit it.
Execute Command
Executes the command selected in the lower part and displays it in the upper part.
Close
Closes the unit

6.1.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

6.1.2 Fields
Name
Name of the command
Parameter
Parameters used for the command
State
State of the command. Three states are possible:
• Command successfully processed
• Command pending
• Command not processed / Error
User
Login name of the user who issued the command
Creation time
Date and time at which the command was issued.

 Avitech GmbH 2018 Page 140 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.2 The Macro function

Some frequent operator tasks may require a series of commands.


With the macro unit, an operator can define a series of commands, the sequence in which
they have to be carried out, assign a name to this series and store it as a macro command.
When the macro name is given in the command line, all the commands belonging to this
macro are entered and carried out automatically in the required sequence.

6.2.1 Function

6.2.1.1 File

New
Clears the unit to create a new macro.
Load
Loads an existing macro.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Close
closes the unit

 Avitech GmbH 2018 Page 141 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.2.1.2 Action Menu

Save
Saves the macro under its current name.
Save As
Saves the macro under a new name.
Delete
Deletes the macro.
Execute Macro
Executes the macro.

6.2.1.3 Options Menu

Show Toolbar
Hides or displays the toolbar.

6.2.1.4 Icons

Insert
Inserts a row in the list.
Remove
Deletes the selected row from the list.
Remove all
Deletes all items from the list.
Move To Top
Moves the selected row to the top.
Move Up
Moves the selected row one row up.
Move Down
Moves the selected row one row down.
Move To Bottom
Moves the selected row to the bottom.

 Avitech GmbH 2018 Page 142 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.2.2 Fields
Commands
List of the commands contained in the macro.

6.3 List of commands


In this section the individual commands are described in detail. The commands are sorted
according to what they are related to and then listed by command name in alphabetical
order. Each command is listed on a separate page, with the name of the command at the top
of the page.

6.3.1 Introduction
Commands are generally constructed to indicate:
• the entity to be operated on.
Parameters can be:
• Entries which, have to be written exactly as shown in the command description.
These are shown in capital letters e.g. DIR.
• Entries, which value must be defined by the user. These are shown in lower case
italic e.g. dev.
For example, the command DAC_ DIVD dev circ implies
| | | |
operation = deactivate -------+ | | |
| | |
entity = diversion -----------------+ | |
for a direction | |
| |
| |
dev and circ specify the direction ---------+
Note: In few cases the operation names have been chosen for compatibility with
existing systems and do not conform to this construction.

6.3.2 Nomenclature
The following nomenclature is used to describe the values that can be entered as
parameters for a command. First the kind of character that has to be used is stated between
the following signs: < and >. Then in subscript and between brackets more information about
the possible values is given. The default value of a field, if any, will be stated after the
parameter description.

6.3.2.1 Arguments
Argument Description

U Upper case character.

N Digit.

 Avitech GmbH 2018 Page 143 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.2.2 Argument combinations


Combination Description

(arg) Argument is mandatory

[arg] Argument is optional

arg1 | arg2 Either argument 1 OR Argument 2.

<arg>x Argument repeated x times. It is not possible to have less or more argument than this
given number.

<arg>x...y x to y arguments allowed; x being the minimum number of arguments and y being the
maximum number of characters allowed for the parameter.

<arg>3-15 Possible numbers are comprised between these numbers and include them.

ALL Wildcard for all possible values on that parameter position

Examples

Example Description

<U>5 The parameter can be any combination of 5 upper case characters.

<U>CIDIN | AFTN The parameter can either be CIDIN, AFTN or AMHS but it has to be one of these.
| AMHS

<N>3-15 The parameter can any number between 3 and 15 including these numbers.

6.3.2.3 Most used parameters


The following parameters are used in a large number of commands. Parameters, which only
apply to a specific command, are described within the description of the command, which
uses them. Any parameters input with retrieval management, overflow management and
trace and online journal commands are not evaluated by AMS but are passed to the
appropriate service.
appl
The application concerned by the command <U>CIDIN | AFTN | AMHS
ax
CIDIN Exit centre: <U>5...8
chan
AFTN channel (subdivision of a circuit): <U>1...16
circ
AFTN circuit. Describes the device specific connection for which the command should
be carried out. This parameter depends on dev as follows: <U>1...16
• if dev = AMH ci = not used
• if dev = TAS ci = circuit

 Avitech GmbH 2018 Page 144 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• if dev = DIO ci = circuit


• if dev = CID ci = no entry
• if dev = MCP ci = Terminal Address
• if dev = OVF ci = not used
• if dev = X25 ci = circuit
• if dev = FAX ci = circuit
• if dev = TCP ci = circuit
prio
Priority Indicator: <U>SS | DD | FF | GG | KK
It is also possible to select more than one priority indicators, by holding the [Ctrl]-key
pressed and clicking on the wanted priorities in the selection list.
rtind
Routing indicator: <U>1...8
dev
Device Type. Specifies the device type for which the command should be carried
out.: <U>AMH | TAS | DIO | CID | MCP | FAX | OVF | X25 | TCP
Possible values are as follows:
• AMH : AFTN messaging via AMHS
• TAS : AFTN messaging via asynchronous terminal server links
• DIO : AFTN messaging via modem
• CID : messaging via CIDIN (former CAB)
• MCP : messaging to/from a local terminal (former EGA)
• FAX : AFTN messaging via FAX
• OVF : messaging to/from the message overflow store
• X25 : AFTN messaging via X.25 national
• TCP : AFTN messaging via TCP
vc
CIDIN virtual circuit group + virtual circuit number: <U>4 <N>1-9

6.3.3 List all available commands [LIST]


Description
List all available commands.
Category
Other
Syntax
LIST

 Avitech GmbH 2018 Page 145 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Parameters
None
Specific Parameters
None
The following table gives a short summary of the available commands and their parameters.

Command Description Parameters

ABANDON_MSG Sends the message to the TRS dev circ


mid_id.mid_time.mid_seq

ACT_CHCK Activate channel check dev circ chan operation

ACT_CKTEXT Activate check allowed ICAO signs dev circ chan

ACT_CSNCHK Activate CSN check dev circ chan

ACT_DIVA Activate AFTN address diversion rtind [MCD:dev circ] [PRIO:proi]


[TO:dev circ]

ACT_DIVD Activate AFTN direction diversion dev circ [MCD:dev circ]


[PRIO:prio] [TO:dev circ]

ACT_L Activate lists <U>(NEW | OLD)

ACT_SVCG Activate automatic SVC handling dev circ chan

ACT_TMSG Send cyclic AFTN test message dev circ chan rpt

CHG_ENQ Change enquiry interval ax value

CL_AX Close exit ax

CL_CHAN Close channel dev (circ | ALL) (chan | ALL)

CL_CIRC Close circuit dev (circ | ALL)

CL_IN_CH Close input channel dev circ chan

CL_VC Close virtual circuit vc

CONTINUE Continue outgoing messages dev circ PRIO: (prio | ALL)

DAC_CHCK Deactivate channel check dev circ chan operation

DAC_CKTEXT Deactivate check allowed ICAO signs dev circ chan

DAC_CSNCHK Deactivate CSN check dev circ chan

DAC_DIVA Deactivate AFTN address diversion rtind [MCD:dev circ] [PRIO:prio]

 Avitech GmbH 2018 Page 146 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Command Description Parameters

DAC_DIVD Deactivate AFTN direction diversion dev circ [MCD:dev circ]


[PRIO:prio]

DAC_SVCG Deactivate automatic SVC handling dev circ chan

DAC_TMSG Stop cyclic AFTN test message dev circ chan

GEN_CHCK Generate channel check message dev circ chan

GEN_LRLS Generate SVC LRLS dev circ chan

HOLD Hold outgoing messages dev circ PRIO:(prio | ALL)

MACRO Sequence of commands macro_name

NOTE_TST Send AFTN test note dev circ chan quality

OP_AX Open exit centre ax

OP_CHAN Open channel dev (circ | ALL) (chan | ALL)

OP_CIRC Open circuit dev (circ | ALL)

OP_IN_CH Open input channel dev circ chan

OP_VC Open virtual circuit vc

PAUSE_MSG Keeps the message in the queue, although the dev circ
connection is open and all other messages will mid_id.mid_time.mid_seq
be delivered.

REQUEST Request application state appl

RESTART Restart application appl

RESUME_MSG Delivers a message previously paused. dev circ


mid_id.mid_time.mid_seq

SET_CSN Set channel sequence number dev circ chan sn_in sn_out

TST_CHAN Test channel dev circ chan

WAIT Timely separates commands from each other seconds


in a macro.

 Avitech GmbH 2018 Page 147 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.4 Commands related to AFTN


Command Description Parameters

ACT_CHCK Activate channel check dev circ chan operation

ACT_CKTEXT Activate check allowed ICAO signs dev circ chan

ACT_CSNCHK Activate CSN check dev circ chan

ACT_DIVA Activate AFTN address diversion rtind [MCD:dev circ] [PRIO:proi] [TO:dev circ]

ACT_DIVD Activate AFTN direction diversion dev circ [MCD:dev circ] [PRIO:prio] [TO:dev
circ]

ACT_SVCG Activate automatic SVC handling dev circ chan

ACT_TMSG Send cyclic AFTN test message dev circ chan rpt

CL_CHAN Close channel dev (circ | ALL) (chan | ALL)

CL_CIRC Close circuit dev (circ | ALL)

CL_IN_CH Close input channel dev circ chan

CONTINUE Continue outgoing messages dev circ PRIO: (prio | ALL)

DAC_CHCK Deactivate channel check dev circ chan operation

DAC_CKTEXT Deactivate check allowed ICAO dev circ chan


signs

DAC_CSNCHK Deactivate CSN check dev circ chan

DAC_DIVA Deactivate AFTN address diversion rtind [MCD:dev circ] [PRIO:prio]

DAC_DIVD Deactivate AFTN direction diversion dev circ [MCD:dev circ] [PRIO:prio]

DAC_SVCG Deactivate automatic SVC handling dev circ chan

DAC_TMSG Stop cyclic AFTN test message dev circ chan

GEN_CHCK Generate channel check message dev circ chan

GEN_LRLS Generate SVC LRLS dev circ chan

HOLD Hold outgoing messages dev circ PRIO:(prio | ALL)

NOTE_TST Send AFTN test note dev circ chan quality

OP_CHAN Open channel dev (circ | ALL) (chan | ALL)

OP_CIRC Open circuit dev (circ | ALL)

 Avitech GmbH 2018 Page 148 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Command Description Parameters

OP_IN_CH Open input channel dev circ chan

SET_CSN Set channel sequence number dev circ chan sn_in sn_out

TST_CHAN Test channel dev circ chan

6.3.4.1 Activate channel check messages [ACT_CHCK]


Description
This command is used to activate the sending and / or controlling of channel check
messages for a channel.
Category
AFTN
Syntax
ACT_CHCK dev circ chan operation
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
operation
The "direction" for the channel check.
• BOTH: send channel check messages to channel AND control
received channel check messages from channel
• REC: only control received channel check messages from channel and
not send channel check messages to channel
• SEND: only send channel check messages to channel and not control
received channel check messages from channel
Errors
CHANNEL OFFLINE
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE

 Avitech GmbH 2018 Page 149 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Remarks
The Parameters REC and SEND are 'add-on' Parameters. This means: One
command with REC and one command with SEND for one channel are the same as
one command with BOTH for this channel.
Example(s)
Activate the sending of channel check messages for device TCP, circuit AB, channel
A:
ACT_CHCK TCP AB A SEND

6.3.4.2 Activate check text [ACT_CKTEXT]


Description
This command is used to activate the check of not allowed signs in messages for a
channel.
Category
AFTN
Syntax
ACT_CKTEXT dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL UNKNOWN
PARAMETER ERROR
Remarks
This check may be deactivated by the corresponding command DAC_CKTEXT.
Example(s)
Check the not allowed characters in messages on device TCP, circuit AVPPAFDL,
channel B:
ACT_CKTEXT TCP AVPPAFDL B

6.3.4.3 Activate CSN checking [ACT_CSNCHK]


Description
This command is used to activate channel sequence number checking for a channel.
Category
AFTN

 Avitech GmbH 2018 Page 150 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Syntax
ACT_CSNCHK dev circ chan
Note: dev = FAX is not allowed.
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Parameters
None
Errors
CHANNEL OFFLINE
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE
Remarks
The chosen channel must be configured in that manner within the corresponding
configuration list parameters (e.g. AFTN procedure, etc.).
Example(s)
Activate CSN checking for device TCP, circuit ED, channel B:
ACT_CSNCHK TCP ED B

6.3.4.4 Activate diversion for an address [ACT_DIVA]


Description
Activation of a standard or of an individual diversion of a routing indicator. Herewith
all messages containing addresses mapped to the diverted routing indicator will be
diverted to the standard or to the individual diversion. The diversion can be excluded
if it has been set as forbidden in the Logical Target configuration list.
Category
AFTN
Syntax
ACT_DIVA rtind [MCD:dev circ] [PRIO:proi] [TO:dev circ]
The check box Wildcard allows to operator to type only 5 characters and herewith
select all routing indicators that begin with these characters

 Avitech GmbH 2018 Page 151 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
MCD:dev ci
In the case of multi-circuit distribution, dev and ci of the address to be diverted
must also be specified.
TO:dev ci
Divert to the dev and ci specified. If no destination is given, the standard
diversion circuit set in the AFTN routing list will be used.
Errors
ADDRESS IN COMMAND IS COLLECTING-ADDRESS
ADDRESS NOT ADMITTED
ADDRESS OF MCD NOT EXISTENT
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
DIVERSION OF ADR TO TARGET MCD NOT ADMITTED
DIVERSION OF ADR TO TARGET NOT ADMITTED
DIVERSION OF DIRECTION FROM TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO MCD-TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO TARGET NOT ADMITTED
DIVERSION OF MCD TO TARGET IS ALREADY DIVERTED
DIVERSION TARGET NOT EXISTENT
DIVERSION TO TARGET IS ALREADY DIVERTED
DIVERSION WITH NO ROUTING INDICATOR
ERROR AT LIST-UPDATE OF DATABASE
ERROR IN COMBINATION OF PARAMETERS
LIST-SOURCE OF DIVERSION NOT EXISTENT
LIST-SOURCE OF MCD-DIVERSION NOT EXISTENT
PARAMETER ERROR
TARGET NOT CHANGED
Remarks
The standard diversion circuit is defined within the configuration list "AFTN routing".

 Avitech GmbH 2018 Page 152 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Example(s)
Activate the address diversion for all messages of priority DD and GG transmitted on
the routing indicator AVPPDA, device DIO, circuit DIALIN3 to the device DIO circuit
DIALIN1:
ACT_DIVA AVPPDA MCD:DIO DIALIN3 PRIO:DD,GG TO:DIO DIALIN1

6.3.4.5 Activate diversion for a direction [ACT_DIVD]


Description
Direction is the preamble of a target to which a message shall be sent. The direction
can be a circuit identifier of a device identifier.
This command is used to activate a diversion for a direction. The diversion circuit can
be explicitly specified in this command or if omitted, the standard diversion circuit set
in the AFTN routing list will be used.
Category
AFTN
Syntax
ACT_DIVD dev circ [MCD:dev circ] [PRIO:prio] [TO:dev circ]
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
MCD:dev ci
In the case of multi-circuit distribution, dev and ci of the circuit to be diverted
must also be specified.
TO:dev ci
Divert to the dev and ci specified. If no destination is given, the standard
diversion circuit set in the AFTN routing list will be used.
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
DIVERSION OF ADR: TO TARGET MCD: NOT ADMITTED
DIVERSION OF ADR: TO TARGET NOT ADMITTED
DIVERSION OF DIRECTION FROM TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO MCD-TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO TARGET NOT ADMITTED
DIVERSION OF MCD: TO TARGET IS ALREADY DIVERTED
DIVERSION TARGET NOT EXISTENT

 Avitech GmbH 2018 Page 153 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

DIVERSION TO TARGET IS ALREADY DIVERTED


DIVERSION WITH NO ROUTING INDICATOR
ERROR AT LIST-UPDATE OF DATABASE
ERROR IN COMBINATION OF PARAMETERS
LIST-SOURCE OF DIVERSION NOT EXISTENT
LIST-SOURCE OF MCD-DIVERSION NOT EXISTENT
PARAMETER ERROR
TARGET NOT CHANGED
Remarks
The standard diversion direction is defined within the configuration list "AFTN Logical
Targets".
Example(s)
Activate the direction diversion for all messages transmitted on the device TCP,
circuit AVPPAFST the standard diversion circuit set in the AFTN routing list:
ACT_DIVD TCP AVPPAFST

6.3.4.6 Activate automatic SVC handling [ACT_SVCG]


Description
Activate automatic SVC handling for a channel.
Category
AFTN
Syntax
ACT_SVCG dev circ chan
Note: dev = FAX is not allowed.
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
CHANNEL OFFLINE
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE

 Avitech GmbH 2018 Page 154 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Remarks
Automatic SVC handling can be switched off again by using the corresponding
command DAC_SVCG.
Refer also to the configuration settings for the chosen channel within the
corresponding list.
Example(s)
Activate automatic SVC handling for device TCP, circuit AB, channel A:
ACT_SVCG TCP AB A

6.3.4.7 Send cyclic AFTN test message [ACT_TMSG]


Description
Send the specified number of AFTN test messages to the specified channel.
Category
AFTN
Syntax
ACT_TMSG dev circ chan rpt
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
rpt
The number of times the message is to be repeated
• 0 = repeat indefinitely i.e. until the command DAC_TMSG command is
given
• n = send the message n times (max. n = 999)
Errors
CHANNEL NOT IN TEST
CHANNEL STATE WRONG
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
PARAMETER ERROR
TRANSFER ACTIVE
UNEXPECTED

 Avitech GmbH 2018 Page 155 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Remarks
None
Example(s)
Send a test message 12 times on device TCP, channel AVBBAFAA, circuit A:
ACT_TMSG TCP AVBBAFAA A 12

6.3.4.8 Close channel [CL_CHAN]


Description
Close the specified channel. Message transmission and reception on that channel will
be immediately stopped after finishing the message currently in transmission or in
reception. Also received requests to establish the connection from the other side will
be discarded.
For FAX connections the new list will be activated even if a message is being sent. In
that case the following system message will be displayed: AFTN FAX
INFORMATION: Message with fax send ID...... could not be cancelled. After the
opening of the closed channel the fax message will be sent a second time.
Category
AFTN
Syntax
CL_CHAN dev (circ | ALL) (chan | ALL)
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
PARAMETER 1 NOT ALLOWED
PARAMETER 2 NOT ALLOWED
PARAMETER 3 NOT ALLOWED
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
NO ASA-PROCESS OF THIS CHANNEL EXISTENT
NO ASE-PROCESS OF THIS CHANNEL EXISTENT
PARAMETER ERROR

 Avitech GmbH 2018 Page 156 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Remarks:
The changing of the channel state will also be reported to the operator by the system
message "AFTN CHANNEL STATE".
As a result after closing the last or only operative channel of a circuit, the circuit itself
will become inoperative. The changing of a circuit state will also be reported to the
operator by the system message "AFTN CIRCUIT STATE".
A channel can be opened again by the corresponding command OP_CHAN.
Example(s)
Close device TCP, circuit ED, channel B:
CL_CHAN TCP ED B

6.3.4.9 Close circuit [CL_CIRC]


Description
Close the specified circuit. Message transmission and reception via all channels
corresponding to that circuit will be immediately stopped after finishing the message
currently in transmission or in reception. Also received requests to establish the
connection from the other side will be discarded.
Category
AFTN
Syntax
CL_CIRC dev (circ | ALL)
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CIRCUIT UNKNOWN
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
PARAMETER ERROR
Remarks
The changing of the circuit state will also be reported to the operator by the system
message "AFTN CIRCUIT STATE".
A circuit can be opened again by the corresponding command OP_CIRC.
For messages to be sent only a limited amount can be held in the circuit queue.
Please refer to the Thresholds settings within the circuit list, the channel belongs to.

 Avitech GmbH 2018 Page 157 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Example(s)
Close device TCP, circuit AB:
CL_CIRC TCP AB

6.3.4.10 Close input channel [CL_IN_CH]


Description
Close the specified channel in the receive direction. Message transmission on that
channel will still be possible but message reception will be immediately stopped after
finishing the message currently in reception.
Category
AFTN
Syntax
CL_IN_CH dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL UNKNOWN
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
NO ASA-PROCESS OF THIS CHANNEL EXISTENT
NO ASE-PROCESS OF THIS CHANNEL EXISTENT
PARAMETER ERROR
Remarks:
The changing of the channel state will also be reported to the operator by the system
message "AFTN CHANNEL STATE".
A channel can be opened again by the corresponding command OP_IN_CH.
Example(s)
Close the reception on device TCP, circuit AVPPAFDL, channel A:
CL_IN_CH TCP AVPPAFDL A

6.3.4.11 Continue outgoing messages [CONTINUE]


Description
Continue the traffic of outgoing messages for a specific circuit with defined priority.

 Avitech GmbH 2018 Page 158 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Category
AFTN
Syntax
CONTINUE dev circ PRIO: (prio | ALL)
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
Remarks
None.
Example(s)
Continue outgoing messages with priority FF for device TCP, circuit AVAAAFRS:
CONTINUE TCP AVAAAFRS PRIO: FF

6.3.4.12 Deactivate channel check messages [DAC_CHCK]


Description
Deactivate the sending and / or controlling of channel check messages for a given
channel.
Category
AFTN
Syntax
DAC_CHCK dev circ chan operation
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
operation
The "direction" for the channel check.
• BOTH: Deactivates the sending AND the controlling of the reception of
channel check messages for the selected channel.
• SEND: Deactivates only the sending of channel check messages for
the selected channel.

 Avitech GmbH 2018 Page 159 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• REC: Deactivates only the controlling of the reception of channel check


messages for the selected channel.
Errors
CHANNEL OFFLINE
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE
Remarks
The Parameters REC and SEND are 'add-on' Parameters. This means: One
command with REC and one command with SEND for one channel are the same as
one command with BOTH for this channel.
Sending channel check messages to a channel or Controlling received channel check
messages can be activated again by the corresponding command ACT_CHCK.
Please refer to corresponding settings within the circuit/channel list.
Example(s)
Deactivates the sending and the controlling of the reception of channel check
messages on device TCP, circuit ET, channel A:
DAC_CHCK TCP ET A BOTH

6.3.4.13 Deactivate check text [DAC_CKTEXT]


Description
This command is used to deactivate the check of not allowed signs in messages of a
given channel.
Category
AFTN
Syntax
DAC_CKTEXT dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL UNKNOWN
PARAMETER ERROR

 Avitech GmbH 2018 Page 160 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Remarks
This check may be activated by the corresponding command ACT_CKTEXT.
Example(s)
Deactivate the check for not allowed characters in messages on device TCP, circuit
AVPPAFDL, channel B:
DAC_CKTEXT TCP AVPPAFDL B

6.3.4.14 Deactivate CSN checking [DAC_CSNCHK]


Description
Deactivate channel sequence number checking for the specified channel.
Category
AFTN
Syntax
DAC_CSNCHK dev circ chan
Note: dev = FAX is not allowed.
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL OFFLINE
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE
Remarks
Channel sequence number checking can be activated again by the corresponding
command ACT_CSNCHK.
The chosen channel must be configured in the appropriate manner by the
corresponding channel configuration list parameters (e.g. AFTN procedure, etc.).
Example(s)
channel sequence number checking for device TCP, circuit ED, channel B:
DAC_CSNCHK TCP ED B

 Avitech GmbH 2018 Page 161 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.4.15 Deactivate diversion for an address [DAC_DIVA]


Description
This command is used to deactivate an address diversion. Messages addressed to
the diverted routing indicator will no longer be diverted.
Category
AFTN
Syntax
DAC_DIVA rtind [MCD:dev circ] [PRIO:prio]
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
MCD:dev ci
In the case of multi-circuit distribution, dev and ci of the diverted address must
also be specified.
Errors
ADDRESS IN COMMAND IS COLLECTING-ADDRESS
ADDRESS NOT ADMITTED
ADDRESS OF MCD: NOT EXISTENT
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
DIVERSION OF ADR: TO TARGET MCD: NOT ADMITTED
DIVERSION OF ADR: TO TARGET NOT ADMITTED
DIVERSION OF DIRECTION FROM TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO MCD-TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO TARGET NOT ADMITTED
DIVERSION OF MCD: TO TARGET IS ALREADY DIVERTED
DIVERSION TARGET NOT EXISTENT
DIVERSION TO TARGET IS ALREADY DIVERTED
DIVERSION WITH NO ROUTING INDICATOR
ERROR AT LIST-UPDATE OF DATABASE
ERROR IN COMBINATION OF PARAMETERS
LIST-SOURCE OF DIVERSION NOT EXISTENT

 Avitech GmbH 2018 Page 162 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

LIST-SOURCE OF MCD-DIVERSION NOT EXISTENT


PARAMETER ERROR
TARGET NOT CHANGED
Remarks
Diversion for the routing indicator can be activated again by the corresponding
command ACT_DIVA.
Example(s)
Deactivate the diversion of messages of priority FF for the routing indicator
AVBBACFA
DAC_DIVA AVBBACFA PRIO: FF

6.3.4.16 Deactivate diversion for a direction [DAC_DIVD]


Description
This command is used to deactivate an address diversion. Messages addressed to
the diverted circuit will no longer be diverted.
Category
AFTN
Syntax
DAC_DIVD dev circ [MCD:dev circ] [PRIO:prio]
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
MCD:dev ci
In the case of multi-circuit distribution, dev and ci of the diverted circuit must
also be specified.
Errors
ADDRESS IN COMMAND IS COLLECTING-ADDRESS
ADDRESS NOT ADMITTED
ADDRESS OF MCD: NOT EXISTENT
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
DIVERSION OF ADR: TO TARGET MCD: NOT ADMITTED
DIVERSION OF ADR: TO TARGET NOT ADMITTED
DIVERSION OF DIRECTION FROM TARGET NOT ADMITTED
DIVERSION OF DIRECTION TO MCD-TARGET NOT ADMITTED

 Avitech GmbH 2018 Page 163 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

DIVERSION OF DIRECTION TO TARGET NOT ADMITTED


DIVERSION OF MCD: TO TARGET IS ALREADY DIVERTED
DIVERSION TARGET NOT EXISTENT
DIVERSION TO TARGET IS ALREADY DIVERTED
DIVERSION WITH NO ROUTING INDICATOR
ERROR AT LIST-UPDATE OF DATABASE
ERROR IN COMBINATION OF PARAMETERS
LIST-SOURCE OF DIVERSION NOT EXISTENT
LIST-SOURCE OF MCD-DIVERSION NOT EXISTENT
PARAMETER ERROR
TARGET NOT CHANGED
Remarks
Diversion for the direction can be activated again by the corresponding command
ACT_DIVD.
Example(s)
Deactivate the direction diversion for all messages transmitted on the device TCP,
circuit AVPPAFST the standard diversion circuit set in the AFTN routing list:
DAC_DIVD TCP AVPPAFST

6.3.4.17 Deactivate automatic SVC handling [DAC_SVCG]


Description
Deactivate automatic SVC handling for a channel.
Category
AFTN
Syntax
DAC_SVCG dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL OFFLINE
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED

 Avitech GmbH 2018 Page 164 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE
Remarks
Automatic SVC handling can be switched on again by using the corresponding
command ACT_SVCG.
Refer also to the configuration settings for the chosen channel within the
corresponding circuit/channel list.
Example(s)
Deactivate automatic SVC handling for device TCP, circuit ED, channel A:
DAC_SVCG TCP ED A

6.3.4.18 Stop sending AFTN test message [DAC_TMSG]


Description
Stop sending AFTN test messages to the specified channel.
Category
AFTN
Syntax
DAC_TMSG dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL NOT IN TEST
CHANNEL STATE WRONG
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
PARAMETER ERROR
Remarks
None
Example(s)
Stop sending AFTN test messages to device TCP, circuit AVBBAFAA, channel A:
DAC_TMSG TCP AVBBAFAA A

 Avitech GmbH 2018 Page 165 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.4.19 Generate a channel check message [GEN_CHCK]


Description
A channel check message will be generated and sent to the channel specified. If a
message is currently being transferred or the channel has not been opened, the
channel check command will be rejected.
Category
AFTN
Syntax
GEN_CHCK dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL OFFLINE
CHANNEL STATE WRONG
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
PARAMETER ERROR
TRANSFER ACTIVE
Remarks
Refer also to the configuration settings for the chosen channel within the
corresponding circuit/channel list.
Example(s)
Generate a channel check message for device TCP, circuit AVBBAFAA, channel A:
GEN_CHCK TCP AVBBAFAA A

6.3.4.20 Generate an SVC LRLS [GEN_LRLS]


Description
An SVC LRLS message will be generated and sent to the channel specified. The
message contains the values of the counters last message received and last
message sent of this channel just before the SVC itself is sent.

 Avitech GmbH 2018 Page 166 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Category
AFTN
Syntax
GEN_LRLS dev circ chan
Note: dev = FAX is not allowed.
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL OFFLINE
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
TRANSFER ACTIVE
Remarks
The successful generation of the SVC is reported to the operator by system message
"AFTN SVC LR LS GENERATED".
Refer also to the configuration settings for the chosen channel within the
corresponding circuit/channel list.
Example(s)
Generate and send an SVC LRLS message on device TCP, circuit AB, channel A:
GEN_LRLS TCP AB A

6.3.4.21 Hold outgoing messages [HOLD]


Description
Hold the traffic of outgoing messages for a specific circuit with defined priority(ies).
Category
AFTN
Syntax
HOLD dev circ PRIO:(prio | ALL)

 Avitech GmbH 2018 Page 167 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
Remarks
If the operator has already set some priority(ies) on hold for a given circuit, entering a
new HOLD command for this circuit with some other priority(ies) will add this(ese) to
the priority(ies) already set on hold for this circuit.
The operator can check which priorities have been set on hold by opening the Status
service and looking at the column Hold for Priorities in the Channel State
Information.
To deactivate the "hold" situation, the operator has to use the CONTINUE command.
Example(s)
Hold outgoing messages with priority FF for device TCP, circuit AVAAAFRS:
HOLD TCP AVAAAFRS PRIO: FF

6.3.4.22 Send AFTN test note [NOTE_TST]


Description
Send an AFTN test note to the specified channel.
Category
AFTN
Syntax
NOTE_TST dev circ chan quality
Note: dev = FAX is not allowed
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
quality
The AFTN message types which correspond to the value given for this
parameter are:
• 0 = Note not received
• 1 = Note bad

 Avitech GmbH 2018 Page 168 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• 2 = Note poor
• 3 = Note fair
• 4 = Note good
• 5 = Note excellent
Errors
CHANNEL STATE WRONG
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
TRANSFER ACTIVE
UNEXPECTED
Remarks
None
Example(s)
Send an AFTN test note 5 on device TCP, circuit AVBBAFAA, channel A:
NOTE_TST TCP AVBBAFAA A 5

6.3.4.23 Open circuit [OP_CHAN]


Description
Opens the specified channel.
Category
AFTN
Syntax
OP_CHAN dev (circ | ALL) (chan | ALL)
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL UNKNOWN
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED

 Avitech GmbH 2018 Page 169 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

COMMAND NOT IMPLEMENTED


NO ASA-PROCESS OF THIS CHANNEL EXISTENT
NO ASE-PROCESS OF THIS CHANNEL EXISTENT
PARAMETER ERROR
Remarks
The changing of the channel state will also be reported to the operator by a
corresponding system message.
As a result of successful opening the first channel of an inoperative circuit, the
corresponding circuit itself will become operative again. The changing of the circuit
state will also be reported to the operator by a corresponding system message.
A channel may be closed again by the corresponding command CL_CHAN.
Example(s)
Open device TCP, circuit ED, channel B:
OP_CHAN TCP ED B

6.3.4.24 Open circuit [OP_CIRC]


Description
The specified circuit will be opened and by that also all channels belonging to that
circuit. If at least one of the corresponding channels becomes active also the circuit
will be put into state OPERATIONAL and message transfer will be possible. The
changing of the circuit state will be reported to the operator by the system message
"AFTN CIRCUIT STATE".
Category
AFTN
Syntax
OP_CIRC dev (circ | ALL)
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CIRCUIT UNKNOWN
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
PARAMETER ERROR

 Avitech GmbH 2018 Page 170 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Remarks
For all concerned channels the changing of their state will also be reported to the
operator by the system message "AFTN CHANNEL STATE".
A circuit can be closed again by the corresponding command CL_CIRC.
Example(s)
Open all circuits for the device TCP:
OP_CIRC TCP ALL

6.3.4.25 Open input channel [OP_IN_CH]


Description
Messages may be sent and received via the specified channel. This channel must
have been in the close input state before.
Category
AFTN
Syntax
OP_IN_CH dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL UNKNOWN
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
NO ASA-PROCESS OF THIS CHANNEL EXISTENT
NO ASE-PROCESS OF THIS CHANNEL EXISTENT
PARAMETER ERROR
Remarks
The changing of the channel state will also be reported to the operator by a
corresponding system message.
A channel may be closed again in the receive direction by the corresponding
command CL_IN_CH.
Example(s)
Open device TCP, circuit ED, channel B in the receive direction:
OP_IN_CH TCP ED B

 Avitech GmbH 2018 Page 171 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.4.26 Set channel sequence numbers [SET_CSN]


Description
Set the channel sequence numbers for the specified channel.
Category
AFTN
Syntax
SET_CSN dev circ chan sn_in sn_out
Note: When entering "dev = FAX" the value of sn_in must be "0"
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
sn_in
New input channel sequence number
sn_out
New output channel sequence number
Errors
CHANNEL OFFLINE
CHANNEL SEQUENCE NUMBER TOO BIG
COMMAND DELETED AT RESTART
COMMAND DELETED BY USER
COMMAND INTERRUPTED
COMMAND NOT EXECUTED
COMMAND NOT IMPLEMENTED
CONFIGURATION ERROR
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
PARAMETER ERROR
TRANSFER ACTIVE
Remarks
None
Example(s)
Set the channel sequence numbers 815 in and 471 out for device TCP, circuit ED,
channel B:
SET_CSN TCP ED B 815 471

 Avitech GmbH 2018 Page 172 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.4.27 Set channel state to test [TST_CHAN]


Description
Set the state of the specified channel to TEST.
Category
AFTN
Syntax
TST_CHAN dev circ chan
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
CHANNEL STATE WRONG
CHANNEL UNKNOWN
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
NO ASA-PROCESS OF THIS CHANNEL EXISTENT
NO ASE-PROCESS OF THIS CHANNEL EXISTENT
NOT APPLICABLE WITH CURRENT AFTN PROCEDURE VALUE
PARAMETER ERROR
TRANSFER ACTIVE
Remarks
Before a channel can be set to the TEST state, the command CL_CHAN must be
given to close the channel:
Example(s)
Set device TCP, circuit AVBBAFAA, channel B to TEST:
CL_CHAN TCP AVBBAFAA B
TST_CHAN TCP AVBBAFAA B

 Avitech GmbH 2018 Page 173 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.5 Commands related to CIDIN


Command Description Parameters

CHG_ENQ Change enquiry interval ax value

CL_AX Close exit ax

CL_VC Close virtual circuit vc

OP_AX Open exit centre ax

OP_VC Open virtual circuit vc

6.3.5.1 Change enquiry interval [CHG_ENQ]


Description
Changes the time interval between the sending of two enquiries to a CIDIN exit
centre. The default time interval is set in the "TEM" column of the CIDIN AX
configuration list.
Category
CIDIN
Syntax
CHG_ENQ ax value
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
value
The interval in seconds between two enquiries. If the value is 0 no enquiry will
be sent. The interval change will be made at the expiration of the next timer.
The enquiry cycle will be executed until the command CHG_ENQ ax 0 is
executed.
Value: <N>[0 | 10-1440]
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
UNKNOWN COMMAND
GENERAL DBMS ERROR (CMD:CHG_ENQ)
Remarks
None

 Avitech GmbH 2018 Page 174 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Example(s)
Change the enquiry of ETCCA to 12:
CHG_ENQ ETCCA 12

6.3.5.2 Close CIDIN exit centre [CL_AX]


Description
Close the specified CIDIN Exit Centre. Message transmission and reception via all
virtual circuits corresponding to that Exit Centre be immediately stopped after
finishing the message currently in transmission or in reception. Also received
requests to establish the connection from the other side will be discarded.
Category
CIDIN
Syntax
CL_AX ax
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
UNKNOWN COMMAND
GENERAL DBMS ERROR (CMD: CL_AX)
Remarks
The following events will occur: CIDIN EXIT UNAVAILABLE ax
Example(s)
Close exit centre ETCCA:
CL_AX ETCCA

6.3.5.3 Close CIDIN virtual circuit [CL_VC]


Description
Close a CIDIN Virtual Circuit. Message transmission and reception on that virtual
circuit will be immediately stopped after finishing the message currently in
transmission or in reception. Also received requests to establish the connection from
the other side will be discarded
Category
CIDIN

 Avitech GmbH 2018 Page 175 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Syntax
CL_VC vc
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
UNKNOWN COMMAND
GENERAL DBMS ERROR (CMD: CL_VC)
Remarks
The following events will occur: CIDIN_VC_STATE vc DISCONNECT
Example(s)
Close virtual circuit ETCCA:
CL_VC ETCC1

6.3.5.4 Open CIDIN exit centre [OP_AX]


Description
Open the specified CIDIN Exit Centre and also all virtual circuit belonging to that exit
centre. If at least one of the corresponding virtual circuit becomes active also the exit
centre will be put into the state OPERATIONAL and message transfer will be
possible. The change of state will be reported to the operator by the system message
"CIDIN EXIT AVAILABLE".
Category
CIDIN
Syntax
OP_AX ax
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER

 Avitech GmbH 2018 Page 176 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
UNKNOWN COMMAND
GENERAL DBMS ERROR (CMD: OP_AX)
Remarks
The following events will occur: CIDIN EXIT AVAILABLE ax
Example(s)
Open exit centre ETCCA:
OP_AX ETCCA

6.3.5.5 Open CIDIN virtual circuit [OP_VC]


Description
Open a CIDIN Virtual Circuit.
Category
CIDIN
Syntax
OP_VC vc
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
UNKNOWN COMMAND
GENERAL DBMS ERROR (CMD:OP_VC)
Remarks
The following events will occur: CIDIN_VC_STATE vc OPEN
Example(s)
Open virtual circuit ETCCA:
OP_VC ETCC1

 Avitech GmbH 2018 Page 177 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

6.3.6 Other commands


Command Description Parameters

ACT_L Activate lists <U>(NEW | OLD)

MACRO Sequence of commands macro_name

REQUEST Request application state appl

RESTART Restart application appl

WAIT Waits the specified time before starting the next command. seconds

6.3.6.1 Activate service lists [ACT_L]


Description
With the command [ACT_L NEW/OLD] the system is instructed to use the new/old
list version starting from now.
With the [ACT_L] command, the system loads the new/old list version parallel to the
currently used list version and activates the new/old list for a given channel when the
message being sent is finished. For FAX the new list will be activated even if a
message is being sent. In that case the following system message will be displayed:
AFTN FAX INFORMATION: Message with fax send ID...... could not be
cancelled. After the activation of the new/old list the fax message will be sent a
second time.
Category
Other
Syntax
ACT_L <U>(NEW | OLD)
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
NEW
The last successfully transmitted service list version, if present and not
activated in the meantime
OLD
The previous service list version, which was in operation until the currently
running version was activated.
Errors
ACCESS ERROR
ACCESS OF COMPONENT 2 NOT SUCCESSFUL
ACTL-COMMAND BUSY
ACTL-COMMAND IN NMZ BUSY

 Avitech GmbH 2018 Page 178 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CMD UNEXPECTED
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
DBMS-ERROR AT SELECT VERSIONS
DELETE OF OLD DATA IN SEQUENCE-TABLE NOT SUCCESSFUL
ERROR AT STATE CROSSING
GENERAL DBMS-ERROR (CMD: ACT_L)
GENERAL DBMS-ERROR (CMD: ACT)
GENERAL DBMS-ERROR (CMD: GO)
GENERAL DBMS-ERROR (CMD: REGO)
GENERAL DBMS-ERROR (CMD: UEB)
GENERAL DBMS-ERROR IN APPL: AMHS (CMD: ACT_L)
GENERAL DBMS-ERROR IN APPL: AMHS (CMD: ACT)
GENERAL DBMS-ERROR IN APPL: AMHS (CMD: GO)
GENERAL DBMS-ERROR IN APPL: AMHS (CMD: REGO)
GENERAL DBMS-ERROR IN APPL: AMHS (CMD: UEB)
GENERAL DBMS-ERROR IN APPL: CIDIN (CMD: ACT_L)
GENERAL DBMS-ERROR IN APPL: CIDIN (CMD: ACT)
GENERAL DBMS-ERROR IN APPL: CIDIN (CMD: GO)
GENERAL DBMS-ERROR IN APPL: CIDIN (CMD: REGO)
GENERAL DBMS-ERROR IN APPL: CIDIN (CMD: UEB)
GENERAL DBMS-ERROR IN APPL: AFTN (CMD: ACT_L)
GENERAL DBMS-ERROR IN APPL: AFTN (CMD: ACT)
GENERAL DBMS-ERROR IN APPL: AFTN (CMD: GO)
GENERAL DBMS-ERROR IN APPL: AFTN (CMD: REGO)
GENERAL DBMS-ERROR IN APPL: AFTN (CMD: UEB)
GENERAL DBMS-ERROR IN AMS (CMD: ACT_L)
GENERAL DBMS-ERROR IN AMS (CMD: ACT)
GENERAL DBMS-ERROR IN AMS (CMD: GO)
GENERAL DBMS-ERROR IN AMS (CMD: REGO)
GENERAL DBMS-ERROR IN AMS (CMD: UEB)
INSERT COMMAND-TABLE NOT SUCCESSFUL
INSERT SEQUENCE-TABLE NOT SUCCESSFUL
INTERNAL ACCESS

 Avitech GmbH 2018 Page 179 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

INTERNAL ERROR
LIST TOO BIG
MEMORY INCONSISTENCE
NO LIST TRANSFERRED FOR RECEIVER
NO LIST-VERSION TO ACTIVATE OLD
NO STOP
OLD ACTL-COMMANDS IN COMMAND-TABLE, FIRST DELETE IT
PARAMETER ERROR
PORT TABLE FULL
PVC TABLE FULL
READ STATUS IN AMHS-DATABASE NOT SUCCESSFUL
READ STATUS IN CIDIN-DATABASE NOT SUCCESSFUL
READ STATUS IN AFTN-DATABASE NOT SUCCESSFUL
RUNTIME ERROR
SERVICE BOTTLE-NECK
STATE VIOLATION
TRANSMISSION NOT CORRECT FOR COMPUTER 1
TRANSMISSION NOT CORRECT FOR COMPUTER 2
UPDATE DEFINITION-TABLE NOT SUCCESSFUL
UPDATE TRANSMISSION-LIST NOT SUCCESSFUL
VERSION OF LIST NOT OK
Remarks
None
Example(s)
Switch over to the new service lists:
ACT_L NEW
Change back to the previous service lists (for example because the system does not
route satisfactorily with the latest version):
ACT_L OLD

6.3.6.2 Macro or sequence of commands [MACRO]


Description
Issue an operator defined sequence of commands.
Category
Other
Syntax
MACRO macro_name

 Avitech GmbH 2018 Page 180 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
macro_name
The name of a previously defined sequence of commands and parameters.
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
Remarks
The creation of a macro is described in chapter "System Commands".
The command will be checked before it is carried out because of possible changes
made to the service lists after the macro was defined.
Command buttons:
Print
Prints the current contents of the form. To use this functionality the form does
not need to be completely filled out. For more information about this function,
please refer to the section Printing Mechanism of the chapter Basic Skills.
Cancel
Closes the macro execution protocol.
Example(s)
1. Create a new macro with the name 'ALICE'.
2. Use the macro-editor to produce following lines:
o REQUEST AFTN
o OP_CHAN TCP AVPPAFDL A
o ACT_DIVD TCP AVPPAFHL TO:TCP AVPPAFDL
3. Save the macro
Execute the macro ALICE with the command line:
MACRO ALICE

6.3.6.3 Request application call-back [REQUEST]


Description
This command is used to check that a message oriented application is still running. A
message is sent to the specified application and if no call-back is received within a
specified time the operator knows that the application must be restarted.
Category
Other

 Avitech GmbH 2018 Page 181 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Syntax
REQUEST appl
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
COMMAND DELETED AT RESTART
COMMAND DELETED FROM USER
COMMAND INTERRUPTED
COMMAND NOT IMPLEMENTED
GENERAL DBMS-ERROR (CMD:REQUEST)
Remarks
None
Example(s)
Check if the application AFTN is still running:
REQUEST AFTN

6.3.6.4 Restart application [RESTART]


Description
This command is used to restart an application after an Initialise list.
Category
Other
Syntax
RESTART appl
Note: Choosing the AFTN application restarts all applications running on
the system, AFTN, AMHS and CIDIN
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
None
Errors
PARAMETER ERROR
Remarks
This command shall only be sued in case of an Initialise list. For all other cases the
cluster shall be executed with the cluster commands (ask your system administrator).

 Avitech GmbH 2018 Page 182 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The restart of an application with this command is not a switch over. The application
will be restarted on the running server.
The best parameter to use is AFTN as it restarts all applications at one time.
Example(s)
Restart the AFTN application:
RESTART AFTN

6.3.6.5 Timely separate commands in a macro [WAIT]


Description
Timely separates commands from each other in a macro.
Note: This command shall only be used in a macro
Category
Other
Syntax
WAIT seconds
Parameters
Parameters common to more than one command are described in section
Nomenclature of this chapter.
Specific Parameters
seconds
The number of seconds the system shall wait before starting the next
command
Errors
No known errors.
Remarks
None
Example(s)
wait 3 seconds before starting the next command:
WAIT 3

 Avitech GmbH 2018 Page 183 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7 STATUS INFORMATION MENU

7.1 The Circuit and Queue Monitor function

The Circuit and Queue Monitor represents a condensed view on the internal status of the
AviSuite AFTN/AMHS switch. It has the following main tasks:
• Visualization of the internal queues of the AFTN and AMHS switching core.
• Visualization of the messages contained in the queues mentioned above.
• Display of additional information concerning the circuits the queues are attached to.
• Display of statistical information concerning the queues.
• Offering a set of commands allowing the operator to take influence on the circuits and
queues displayed.
• Full access to the messages contained in the queues.
• Display of statistical information concerning message flows and contents per circuit.
The Circuit and Queue Monitor is composed of two parts:
• The tree in the left part
• Tabbed panes in the upper right part which name and contents depend on the level
chosen in the tree.

 Avitech GmbH 2018 Page 184 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.1.1 The Circuit and Queue Monitor tree

In the left hand part of the circuit and queue monitor a tree with 5 levels is displayed:
• The root level of this tree represents the monitored COM Centre.
• The second level contains the device types for AFTN and AMHS circuits.
• The third level contains the AFTN and AMHS circuits.
• The fourth level shows the messages queued for the circuits.
• The fifth level shows the recipient addresses of the messages.

Clicking on the latch symbol of a node will expand or collapse it.

7.1.2 Common circuit and queue monitor functions

7.1.2.1 File

Close
Closes this unit.

7.1.2.2 Options

Show Toolbar
Hides or displays the toolbar.

 Avitech GmbH 2018 Page 185 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.1.3 The root level


The root node of the tree in the left hand window represents the monitored COM Centre,
indicated by its location indicator, e.g. GOOO for Dakar. The total number of messages in all
outbound queues of this COM Centre is included in square brackets ([...]).
When the COM Centre node is selected, the upper right pane consists of 3 tabs:
• The Circuit Overview tab.
• The Suspicious Circuits tab.
• The Queue Visualisation tab.
The further details tabbed panes are:
• The Diversion tab.
• The Copy Address tab.
• The Current Day Statistics tab.
• The Additional Information tab.

7.1.4 The second level


The second level contains the device types for AFTN and AMHS circuits. Nodes at that level
represent device types for the circuits belonging to the given COM centre. The circuits are
grouped based on the device type and the user has possibility to check all circuits with the
given device type.
When a device type is selected the upper right pane is updated the same way as the
selected COM Centre and consists of 3 tabs:
• The Circuit Overview tab.
• The Suspicious Circuits tab.
• The Queue Visualisation tab.
Only the circuits with the given device type are displayed in these tabs.
The further details tabbed panes are:
• The Diversion tab.
• The Copy Address tab.
• The Current Day Statistics tab.
• The Additional Information tab.

7.1.5 The third level


The third level contains the configured AFTN and AMHS circuits.
The circuit name is followed by the number of messages queued for the circuit. Furthermore,
green arrows symbolise connected channels:
• An arrow pointing to the right indicates a connection initiated by the local server.
• An arrow pointing to the left indicates a connection initialised by the peer.
As multiple arrows may coexist, the number of established connections is also displayed.

 Avitech GmbH 2018 Page 186 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

When an AFTN or an AMHS circuit node is selected, the upper right pane consists of 2 tabs:
• The Overview tab.
• The Actions and Properties tab.

7.1.6 The fourth level


The fourth level shows the messages queued for the circuits.
For each message the ATS (in case of AFTN) or MTS (in case of AMHS) priority and the first
12 characters of the message text, but no more than 1 line are displayed.
A double click on a message on this level opens it in the Message Viewer.
When this node level is selected the right pane contains the following two tabs:
• The Overview tab.
• The Actions and properties tab.

7.1.7 The fifth level


The fifth level shows the addresses of the recipients for the selected message.
The recipient address is displayed in AFTN format, regardless whether the message has
AFTN or AMHS format.

7.1.8 The upper right tabs

7.1.8.1 The Circuit Overview tab

The first tab provides the circuit overview, a table consisting of one row for each configured
circuit and 11 columns:
• Circuit: The circuit name. It consists of up to 16 characters. By default the rows are
sorted by alphabetical order of the circuit names.
• Type: The circuit type. It can take one of the following values:
o AIS
o ERR
o MS
o TAS
o MTA
o AMH

 Avitech GmbH 2018 Page 187 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

o FAX
o OVF
o TCP
o UA
o CID
o FEC
o RV
o TRS
o DIO
o MCP
o SIT
o X.25
• Status: The status field. It shows whether the circuit is:
o OPERATIVE: Messages can be received and sent
o INOPERATIVE: Messages can neither be received or sent
o OPERATIVE IN: Messages can be received but not sent
o OPERATIVE OUT: Messages can be sent but not received
• Connection: This field indicates whether or not a circuit is connected. The values
correspond to the green arrows that are displayed with a circuit element in the third
level of the tree.
• Diversion: This field indicates whether or not a circuit is diverted. The target of the
diversion and the priorities to which the diversion applies are shown in the details part
when the row of a diverted circuit is selected.
• Total: This field indicates the total number of messages counted for the circuit.
• Overdue: For each circuit an overdue time is configurable. A message is considered
overdue when it is older than this time. The number of overdue messages in the
circuit is displayed in this column. The occurrence of an alert overdue message is
indicated by a red background.
• Stalled: A queue is considered stalled when during a configurable amount of time it is
not empty and no message has been sent during that time. In case of a stalled queue
staff should investigate the reason, e.g. a connectivity problem.
• Channel: This field is defined for AFTN channels only. It displays the name of the
AFTN channel. For AMHS channels this field is empty.
• LR and LS: Both fields are defined for AFTN channels only. LR displays the channel
identifier and the channel sequence number of the last received message whereas
LS displays the channel identifier and the channel sequence number of the last sent
message. For AMHS channels both fields are empty.

 Avitech GmbH 2018 Page 188 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The further details tabbed panes are:


• The Diversion tab.
• The Copy Address tab.
• The Current Day Statistics tab.
• The Additional Information tab.

7.1.8.2 The Suspicious Circuits tab

A circuit is suspicious if one of the following conditions is fulfilled:


• Queue threshold value 2 is reached. The system issues the system event
AFTN_THRESHOLD_2.
• Message Overdue In Queue event happened. The system issues the system event
MSG_OVERDUE_IN_QUEUE.
• Automatic diversion is enforced. The system issues the system event
SFM_AUTO_ADDRESS_DIVERSION, or SFM_AUTO_DIRECTION_DIVERSION.
• No message is transmitted because of the stalled state of the circuit. The system
issues the system event AFTN_MESSAGE_QUEUE_STALLED.
• All channels are blocked for the given circuit.
The suspicious circuit becomes unsuspicious if all system events that caused its
suspiciousness are deactivated. The following list contains information how to deactivate the
certain system events:

System event Deactivation by

AFTN_THRESHOLD_2 AFTN_RESET_THRESHOLD_2

MSG_OVERDUE_IN_QUEUE The message is getting overdue and staying in the queue.

State ACT in State DEACT in


SFM_AUTO_ADDRESS_DIVERSION, SFM_AUTO_ADDRESS_DIVERSION,
SFM_AUTO_DIRECTION_DIVERSION SFM_AUTO_DIRECTION_DIVERSION.

Channel state: BLOCKED Any other channel state except BLOCKED. It means that at
least one channel of the circuit is no longer BLOCKED.

AFTN_MESSAGE_QUEUE_STALLED Event is deactivated if any message leaves a circuit.

 Avitech GmbH 2018 Page 189 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

From the layout perspective the Suspicious Circuits tab is a copy of the Circuit Overview tab.
• Circuit: The circuit name. It consists of up to 16 characters. By default the rows are
sorted by alphabetical order of the circuit names.
• Type: The circuit type. It can take one of the following values:
o AIS
o ERR
o MS
o TAS
o MTA
o AMH
o FAX
o OVF
o TCP
o UA
o CID
o FEC
o RV
o TRS
o DIO
o MCP
o SIT
o X.25
• Status: The status field. It shows whether the circuit is:
o OPERATIVE: Messages can be received and sent
o INOPERATIVE: Messages can neither be received or sent
o OPERATIVE IN: Messages can be received but not sent
o OPERATIVE OUT: Messages can be sent but not received
• Connection: This field indicates whether or not a circuit is connected. The values
correspond to the green arrows that are displayed with a circuit element in the third
level of the tree.
• Diversion: This field indicates whether or not a circuit is diverted. The target of the
diversion and the priorities to which the diversion applies are shown in the details part
when the row of a diverted circuit is selected.
• Total: This field indicates the total number of messages counted for the circuit.
• Overdue: For each circuit an overdue time is configurable. A message is considered
overdue when it is older than this time. The number of overdue messages in the
circuit is displayed in this column. The occurrence of an alert overdue message is
indicated by a red background.

 Avitech GmbH 2018 Page 190 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• Stalled: A queue is considered stalled when during a configurable amount of time it is


not empty and no message has been sent during that time. In case of a stalled queue
staff should investigate the reason, e.g. a connectivity problem.
• Channel: This field is defined for AFTN channels only. It displays the name of the
AFTN channel. For AMHS channels this field is empty.
• LR and LS: Both fields are defined for AFTN channels only. LR displays the channel
identifier and the channel sequence number of the last received message whereas
LS displays the channel identifier and the channel sequence number of the last sent
message. For AMHS channels both fields are empty.
The further details tabbed panes are:
• The Diversion tab.
• The Copy Address tab.
• The Current Day Statistics tab.
• The Additional Information tab.

7.1.8.3 The Queue Visualisation tab

The Queue Visualisation tab provides a graphic visualisation of the queues.


• Circuit: The circuit name. It consists of up to 16 characters. By default the rows are
sorted by alphabetical order of the circuit names.
• Type: The device type of the circuit.
• Total: the number of queued messages.
• Queue: the graphical visualisation of the queued messages. The heading of this
column provides a number scale. Furthermore, 3 threshold values configurable for
each circuit are marked in the bar. The colour of the bar depends on the threshold
status as follows:
o Green: no threshold reached
o Yellow: threshold 1 reached

 Avitech GmbH 2018 Page 191 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

o Orange: threshold 2 reached


o Red: threshold 3 reached
In this tabbed pane no entry can be selected for the display of further details.

7.1.8.4 The Overview tab

7.1.8.4.1 Upper part

The upper part of the overview tab shows a table the rows of which represent the messages
queued for the circuit. Each row corresponds to one message. By default the messages are
sorted according to their ATS (SS, ..., KK) or MTS (urgent, normal, non-urgent) priorities and
according to their age within the same priority.
The structure and the content of a message entry in the overview tab depend on the type of
circuit (AFTN, MTA, UA).
EMID
External Message identifier
ATS Priority
The ATS priority assigned to the message.
Filing Time
The time at which the message was received by the AFTN handler, expressed as
Day Hour Minute.
Type
Message type such as PLAIN, FPL, DEP, NT, SW...
Reception Time
The date and time the message was received.
Originator
The AFTN address of the originator of the message.
Paused
If the messages has been paused the checkbox in this column is ticked.

 Avitech GmbH 2018 Page 192 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.1.8.4.2 Lower part

The lower part of the overview tab displays the message last selected in the upper part of the
overview tab or in the fourth level of the tree on the left part.

7.1.8.5 The Actions and Properties tab


This tab offers an interface for executing actions on a circuit. The list of actions comprises:
• Set the circuit's operational state to INOPERATIVE, OPERATIVE, OPERATIVE_IN or
OPERATIVE_OUT.
• Activate a diversion per priority, to a target circuit, potentially with MCD.

7.1.8.5.1 Upper part

The upper part of the actions and properties tab shows read-only information about the
circuit and its active diversions.
Circuit
Name
The circuit name.
device Type
The device type of the circuit.
Operational State
The operational state of the circuit.

 Avitech GmbH 2018 Page 193 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Active diversions
Target Device Type
The device type of the circuit to where the diversion is made.
Target Circuit
The circuit to where the diversion is made.
MCD Device Type
The device type of the multi circuit distribution, if any.
MCD Circuit
The multi circuit distribution, if any.
Priorities
The priorities diverted.
Active since
The date and time since when the diversion is active.
Cause
The cause of the activation of the diversion.

7.1.8.5.2 Lower part

The lower part allows the operator to change the operational state of the circuit and to set
diversions for this circuit.
The columns of the set diversions table are the same as the columns in the active diversions
table on the upper part of the tab.

7.1.8.5.2.1 Changing the operational state of a circuit.


To modify the operational state of the selected circuit the operator shall select the new state
from the drop down field and then click on the [Apply]-button.

 Avitech GmbH 2018 Page 194 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Commands executed by the system for the operational state change of an AFTN circuit:

Final State Initial State

OPERATIVE INOPERATIVE OPERATIVE_IN OPERATIVE_OUT

OPERATIVE X OP_CIRC CONTINUE OP_IN_CH

CL_CIRC
INOPERATIVE CL_CIRC X CL_CIRC
CONTINUE

OP_IN_CH
HOLD
OPERATIVE_IN HOLD X HOLD
OP_CIRC
OP_CIRC

OP_CIRC CONTINUE
OPERATIVE_OUT CL_IN_CH X
CL_IN_CH CL_IN_CH

7.1.8.5.2.2 Setting diversions for a circuit


To add a diversion the operator can add rows, fill them out with the desired parameters and
click on the [Save]-button.
To remove a diversion the operator can delete the concerned row(s) and click on the [Save]-
button.
Modifying a row in fact means two actions: removing a diversion and adding a new one.
The [Reload]-button refreshes the table and erases any unsaved modification.

7.1.9 The lower right tabs

7.1.9.1.1 The Diversion tab

 Avitech GmbH 2018 Page 195 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The diversion tab displays the following diversion parameters for the selected circuit:
Target Device Type
The type of device to which the diversion points.
Target Circuit
The circuit to which the diversion points.
MCD Device Type
The type of device in case of multi-circuit distribution.
MCD Circuit
The circuit in case of multi-circuit distribution.
Priorities
The AFTN priority concerned by the diversion.
Active Since
The date and times when this diversion has been activated.
Cause
The cause of the diversion: manual or automatic.

7.1.9.2 The Copy Address tab

The copy address tab displays the copy in and copy out circuits configured for the selected
circuit. The following information is available:
Name
The name of the copy circuit.
Message type
The list of message types for which the copy applies. If no message type is displayed,
the copy applies for all message types.
Priority
The list of priorities for which the copy applies. If no priority is displayed, the copy
applies for all priorities.

 Avitech GmbH 2018 Page 196 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Type
The type of copy:
• IN
• OUT

7.1.9.3 The Current Day Statistics tab

This tab displays statistics data of the current day, for the selected circuit among which:
• The number of received and sent messages in total.
• The number of received and sent messages per priority.
• The number of rejected messages.
• The number of AFTN service messages received.
The columns of the statistics table display the following information:
Priority
The priority concerned by the statistics on this line.
Sent num.
The number of sent messages.
Sent Size
The cumulated size of the sent messages in bytes.
Received num.
The number of received messages.
Received size
The cumulated size of the received messages in bytes.
The lines of the statistics table display the following information:
KK
Information regarding messages with the KK priority.
GG
Information regarding messages with the GG priority.

 Avitech GmbH 2018 Page 197 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

FF
Information regarding messages with the FF priority.
DD
Information regarding messages with the DD priority.
SS
Information regarding messages with the SS priority.
--
Information regarding messages with no priority such as channel checks or test
messages.
Total
Information regarding the total amount of messages.

7.1.9.4 The Additional Information tab

 Avitech GmbH 2018 Page 198 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The Additional information tab displays further information related to the selected circuit such
as:
• The configuration parameters of the selected circuit
• The configuration parameters of the channels of this circuit

7.1.10 Message Viewer


A double click on a message opens it in the message viewer. This unit is read only and
displays the AFTN or the AMHS form depending on the message opened.

7.1.10.1 AFTN Message Viewer

The AFTN Message Viewer contains the following fields.


• MSG Type: The type of message received
• EMID: The external message identifier
• Reception Time: The date and time the message was received
• ATS Prio: The AFTN priority indicator
• Recipients: The destination address(es)
• Filing Time: The filing time of the message
• Originator: The originator address
• OHI: The optional heading information according to ICAO, Annex 10, amendment 71
• Message Text: The text of the message

 Avitech GmbH 2018 Page 199 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.2 Connection State

7.2.1 Common state monitor functions

7.2.1.1 File

Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Close
Closes this unit.

7.2.1.2 Options

Show Toolbar
Hides or displays the toolbar.

 Avitech GmbH 2018 Page 200 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.2.2 The AFTN Connection State Monitor

This unit is used to monitor all AFTN channels defined in the current configuration lists.
This section gives only specific information on the subject. Details about the functions can be
found in the section Common state monitor functions of this chapter.

7.2.2.1 Column
Circuit
The name of the circuit.
Circuit State
The state of the circuit. The possible states are the following:
• OPERATIVE
• INOPERATIVE
• OPERATIVE_IN
• OPERATIVE_OUT
Hold
Shows the Priorities for which a Hold command has been initiated.
Channel
The name of the channel.
Channel State
The state of the channel. The possible states are the following:
• OPEN
• CLOSED
• TEST
• BLOCKED
• HOLD

 Avitech GmbH 2018 Page 201 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• DEAD
• CLOSE_INPUT
Connection State
The state of the connection. The possible states are the following:
• DISCONNECTED
• CONN_BY_REMOTE
• CONN_BY_HOST
Device
The name of the device
Device Type
The type of device used for the channel. The possible devices are the following:
• MCP
• TCP
• TAS
• FAX
• DIO
• FEC
• X25
• SIT
• AMH
• AIS
• TRS
• OVF
• MTA
• UA
• MS
Connection Type
The type of connection of channel. The possible session types are the following:
• FIX
• PVC
• TEMPORARY
• PERMANENT
• REMOTE
• REMOTE_EMPTY_MESSAGE
• REMOTE_FRONTEND
• MATIP_BIL

 Avitech GmbH 2018 Page 202 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• MATIP_SLV
• MATIP_MST
• TWO_WAY_MONOLOGUE
Last Changed
The date and time when the state started.

7.2.3 The AMHS Connection State Monitor

This unit is used to monitor all AMHS channels defined in the current configuration lists.
This section gives only specific information on the subject. Details about the functions can be
found in the section Common state monitor functions of this chapter.

7.2.3.1 Column
Circuit
The name of the AMHS circuit.
State
The state of the circuit. The possible states are the following:
• OPERATIVE
• INOPERATIVE
• OPERATIVE_IN
• OPERATIVE_OUT
Connection State
The state of the connection. The possible states are the following:
• DISCONNECTED
• CONN_BY_REMOTE
• CONN_BY_HOST

 Avitech GmbH 2018 Page 203 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• CONNECTING
Device Type
The type of device used for the channel. The possible devices are the following:
• MCP
• TCP
• TAS
• FAX
• DIO
• FEC
• X25
• SIT
• AMH
• AIS
• TRS
• OVF
• MTA
• UA
• MS
Session Type
The type of session used by the channel. The possible session types are the
following:
• P1
• P3
• P7
Last Changed
The date and time when the state started.

 Avitech GmbH 2018 Page 204 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.2.4 The CIDIN Exit Centre Connection State Monitor

This unit is used to monitor all CIDIN exit centres defined in the actual configuration lists.
This section gives only specific information on the subject. Details the functions can be found
in the sections Common state monitor functions of this chapter.

7.2.4.1 Column
Exit centre
The name of the exit centre
Connect State
The state of the connection
Time
The date and time when the state started.

 Avitech GmbH 2018 Page 205 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

7.2.5 The CIDIN Virtual Circuit Connection State Monitor

This unit is used to monitor all CIDIN virtual circuits defined in the actual configuration lists.
This section gives only specific information on the subject. Details the functions can be found
in the sections Common state monitor functions of this chapter.

7.2.5.1 Column
VC Group
The name of the virtual circuit group
VC Number
The number of the virtual circuit
Connection State
The state of the connection
Init State
The initial state of the virtual circuit.
Time
The date and time when the state started.

 Avitech GmbH 2018 Page 206 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

8 REPORT MENU

8.1 Common Report functions

8.1.1 File

Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Execute
Requests a new version of the current report.
Cyclic Refresh
Refreshes the report automatically every minute.
Access Reports
Opens a finder to select a previous report.
Close
Closes this unit.
Close
Closes this unit.

8.1.2 Options

Show Toolbar
Hides or displays the toolbar.

 Avitech GmbH 2018 Page 207 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

8.2 The Overflow Queue report

The Overflow report shows for each circuit, exit address or Organisation unit detailed
information about the messages waiting in the overflow storage for further processing.
These messages are transferred from a queue to the overflow store. A possible reason for
such a transfer is exceeding threshold value 3 within a queue. Messages will also be
delivered to the overflow position, when an address or direction diversion to OVF is active or
a CIDIN Exit centre is unavailable.
Note: The first line in this report is for ALL device types. This entry shows the total
number of messages which have been written to the message overflow store.
Device type
The type of device from which the messages come.
Circuit
The circuit name.
Exit address
This column is used for messages coming from CIDIN queues. It shows the CIDIN
Exit-address to which messages could not be delivered.
Organisation unit
This column is used for messages coming from AMHS queues. It shows the
Organization Unit to which messages could not be delivered.
Automatic count
The number of messages for a specific circuit which have been written to the
message overflow store automatically (Exit centre is unavailable, threshold 3 is
reached).
Manual count
The number of messages for a specific circuit which have been written to the
message overflow store manually (diversion command).
Oldest count
The number of messages for a specific circuit which have been written to the
message overflow store because the "Overdue" timer expired and the "Overdue
Target" is set to OVF.

 Avitech GmbH 2018 Page 208 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

8.3 The Message Router Queue report

The Message Router Queue report shows the connection state of each client and their
queue from the point of view of the message router.
the message router conducts 2 queues for each client:
• one queue which contains data which were not yet read by the client
(unacknowledged).
• one queue which contains data which the client has read on the socket buffer and
keeps by itself in the Main Memory (acknowledged).
Client
Name of the client.
Client State
State of the client:
ALREADY_EXIST
The client was already registered to the message router but this was ended.
NOT_YET_EXIST
If data should be sent to a client which is known in the system but not yet
connected to the message router a queue is created and the message is set in
it.
READY
'Normal state'. The client is registered to the message router and is also 'able
to work'.
REROUT
Because of a reroute command, the process receives momentarily the state
REROUT.
Unacknowledged
Number of elements in the queue which were not yet read by the client.
Acknowledged
Number of elements in the queue which the client has read from the socket buffer.

 Avitech GmbH 2018 Page 209 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

8.4 The Address Diversion report

The Address Diversion report shows for each diverted routing indicator detailed information
about the activated diversion.
Rtind
The Routing Indicator for which a diversion will be carried out.
Source device type
Device type from which messages will be diverted.
Source Circuit
Circuit from which messages will be diverted.
Target device type
Device type to which messages will be diverted.
Target Circuit
Circuit to which messages will be diverted.
Priorities
Priorities for which the diversion applies.
Active since
The date and time since when the diversion is active.

8.5 The Direction Diversion report

The Direction Diversion report shows for each diverted direction detailed information about
the activated diversions.
Device Type
Device type
Circuit
Name of the circuit

 Avitech GmbH 2018 Page 210 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Source device type


Messages coming from the combination of this device type and the circuit listed in the
next field are diverted.
Source circuit
Messages coming from the combination of this circuit and the device type listed in the
previous field are diverted.
Target device type
Messages are diverted to the combination of this device type and the circuit listed in
the next field.
Target circuit
Messages are diverted to the combination of this circuit and the device type listed in
the previous field.
Priorities
Priorities for which the diversion applies.
Active since
The date and time since when the diversion is active.

8.6 The Queue Summary report

The Queue Summary report shows for each circuit of all AFTN gateways detailed
information about each queue and in addition the message identification and date/time of the
oldest message in the queue.
Note: If the checkbox ALL has been ticked the first line of this report, (or the first
lines of each device type if ALL has also been chosen for device type), shows the
total number of messages which are currently in the queue of each device type.
Device type
The device type.
Circuit
The circuit name.
Total
The total number of messages held in the queue.
Window
The number of messages which are currently being transmitted (CIDIN only).

 Avitech GmbH 2018 Page 211 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

SS
The number of messages in the queue with the priority level SS.
Old SS
The number of messages in the queue with the priority level SS which timer has
reached the Overdue Timer set for this priority and this circuit.
Only circuits with the "Overdue Handling" parameter "SYSTEM_EVENT" can have
more than 0 messages here.
DD
The number of messages in the queue with the priority level DD.
Old DD
The number of messages in the queue with the priority level DD which timer has
reached the Overdue Timer set for this priority and this circuit.
Only circuits with the "Overdue Handling" parameter "SYSTEM_EVENT" can have
more than 0 messages here.
FF
The number of messages in the queue with the priority level FF.
Old FF
The number of messages in the queue with the priority level FF which timer has
reached the Overdue Timer set for this priority and this circuit.
Only circuits with the "Overdue Handling" parameter "SYSTEM_EVENT" can have
more than 0 messages here.
GG
The number of messages in the queue with the priority level GG.
Old GG
The number of messages in the queue with the priority level GG which timer has
reached the Overdue Timer set for this priority and this circuit.
Only circuits with the "Overdue Handling" parameter "SYSTEM_EVENT" can have
more than 0 messages here.
KK
The number of messages in the queue with the priority level KK
Old KK
The number of messages in the queue with the priority level KK which timer has
reached the Overdue Timer set for this priority and this circuit.
Only circuits with the "Overdue Handling" parameter "SYSTEM_EVENT" can have
more than 0 messages here.
Circuit State
The status of the circuit.
• OPERATIVE
• INOPERATIVE

 Avitech GmbH 2018 Page 212 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• INIT
• LIST_STOP
Queue State
The threshold status of the queue element resources.
• NORMAL
• WS1
• WS2
• WS3
Oldest IMID
IMID of the oldest message in the queue.
Oldest DTG
Time stamp of the oldest message in the queue.

8.7 The Channel Settings report

The Channel Settings report shows for each channel of one or all device types detailed
information about different settings of these channels.
Device type
The device type.
Circuit
The circuit name.
Channel
The channel name.
CID out
The circuit and channel identifier for outgoing messages
CSN ctrl
Specifies whether the channel sequence number of an incoming message is to be
checked or not. Possible values are:
• YES
• NO

 Avitech GmbH 2018 Page 213 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

LR CSN
The channel sequence number of the last message received on this channel. If no
message has been received the column is empty.
LS CSN
The channel sequence number of the last message sent on this channel. If no
message has been received the column is empty.
Chan Check
Shows if a channel check is executed on this channel. Possible values are:
• NONE
• BOTH
• SEND
• REC
Check text
Indicates if the automatic check of non ICAO format in incoming messages is set or
not. Possible values are:
• YES
• NO
Gen LR LS EXP
Indicates if the system automatically generates LR LS EXP messages. Possible
values are:
• YES
• HINT
Gen SVC MIS CH
Indicates if the system automatically generates SVC MIS CH messages. Possible
values are:
• YES
• HINT
Gen SVC QTA MIS
Indicates if the system automatically generates SVC QTA MIS messages. Possible
values are:
• YES
• HINT
Gen LR LS OP
Indicates if the system automatically generates LR LS OP messages. Possible values
are:
• YES
• NO

 Avitech GmbH 2018 Page 214 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Gen LR LS CYC
Defines if as SVC message is generated at configurable times. Possible values are:
• YES/24
• YES/12
• YES/8
• YES/6
• YES/4
• YES/3
• YES/2
• YES/1
• NO

8.8 The Channel State report

The Channel State report shows for each channel of one or all device type(s) detailed
information about different states, used MTP-Identifier and CSN.
Device type
The device type.
Circuit
The circuit name.
Channel
The channel name.
Channel State
The Channel status i.e. whether messages may be transmitted and received on this
channel. The initial setting at system start-up is defined in the configuration lists and
can be changed by a supervisor using the appropriate command.
• OPEN
• CLOSED
• BLOCKED
• TEST

 Avitech GmbH 2018 Page 215 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Connect State
This parameter shows the current status of a connection. Possible values are:
• CONN_BY_HOST
• CONN_BY_REMOTE
• DISCONNECTED
Operational State
The current operational status of the channel i.e. its availability. Possible values are:
• INIT
• STOP
• READY
• GOING_STOP
CID
The first three letters of the Transmission Identification of an outgoing message.
LR CSN
The Channel Sequence Number of the last message received on this channel.
LS CSN
The Channel Sequence Number of the last message sent on this channel.

8.9 The Queue Detail report

The Queue Detail report shows messages waiting in a specified message queue.
IMID
The internal message identifier.
EMID
The external message identifier.
Paused
Hint if the message has been paused.
Priority
The priority of the message.

 Avitech GmbH 2018 Page 216 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Address
The first addressee indicator is shown, all other addressee indicators will be shown
after displaying the message.
Filing Time
The filing time of the message.
Originator
The originator indicator of the message.
Message Body
The first 210 characters of the message body are shown. The whole message body
will be shown after displaying the message.
Reception Time
Time at which the System received the message.
Overdue [s]
Number of seconds elapsed since the message arrived in the queue.

8.10 The CSN Midnight report

The CSN Midnight report is generated once a day, shortly after midnight. It shows for each
circuit of all AFTN gateways the last CSN received and the last CSN sent before midnight.
Device Type
The type of the device (FAX, TCP, X25....).
Circuit
The circuit Name.
Channel
The channel Name
CID In
The CID of the channel in the incoming direction.
LR CSN
Last channel sequence number received on the selected day. If nothing was received
on this channel the field is empty.
Received
Time of the reception of the last CSN.

 Avitech GmbH 2018 Page 217 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CID Out
The CID of the channel in the outgoing direction.
LS CSN
Last channel sequence number sent on the selected day. If nothing was received on
this channel the field is empty.
Sent
Time of the sending of the last CSN.

8.11 The AFTN Test Message report

The Test Message report shows test messages received.


Circuit
The circuit Name.
Channel
The channel Name
Date
The date and time the test message was received.
Test Message
The text of the test message.

8.12 The Virtual Circuit State report

The Virtual Circuit State report shows for each virtual circuit detailed information about
state and connect state of the virtual circuits.

 Avitech GmbH 2018 Page 218 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

VC
The address of a CIDIN exit centre.
State
The state of the CIDIN virtual circuit. Possible values:
• OPEN
• CLOSE
• HOLD
Connect State
The connect state of the CIDIN virtual circuit. Possible values:
• CONN_BY_HOST
• CONN_BY_REM
• DISCONNECTED
• CONNECTING

8.13 The Virtual Circuit Group Queue report

The Virtual Circuit Group Queue report shows detailed information about circuit group
queues.
Virtual Circuit Group
The identifier of the virtual circuit group.
Packets
The number of X.25 packets waiting for transmission.
Queue State
The current queue state of the virtual circuit. Possible values:
NORMAL
Normal queue state.
THR1
Queue has reached level threshold 1.

 Avitech GmbH 2018 Page 219 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

RTHR1
Queue has reached level reset threshold 1.
THR2
Queue has reached level threshold 2.
RTHR2
Queue has reached level reset threshold 2.
THR3
Queue has reached level threshold 3.
RTHR3
Queue has reached level reset threshold 3.

8.14 The Exit Centre State report

The Exit Centre State report shows detailed information about exit centre state.
Exit Centre
The name of the exit centre.
Enquiries
Number of the open enquiries.
State
State of the exit centres. Possible values:
• AVAILABLE
• UNAVAILABLE

 Avitech GmbH 2018 Page 220 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

8.15 The Exit Centre Queue report

The Exit Centre Queue report shows for each Exit Centre detailed information about its
queue.
Exit Centre
The address of the exit centre.
Message Count
The total number of messages in the queue of the exit centre. The not quitted
messages which are already in a window are not counted here.
Window
The number of free windows for the exit centre. This is the number defined in the
CIDIN Entry/Exit Centre configuration list.
Prio 1
The number of messages with the priority 1 in the queue.
Prio 2
The number of messages with the priority 2 in the queue.
Prio 3
The number of messages with the priority 3 in the queue.
Prio 4
The number of messages with the priority 4 in the queue.
Prio 5
The number of messages with the priority 5 in the queue.
Prio 6
The number of messages with the priority 6 in the queue.
Prio 7
The number of messages with the priority 7 in the queue.
Prio 8
The number of messages with the priority 8 in the queue.

 Avitech GmbH 2018 Page 221 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Queue State
The message queue state.
Values:
NORMAL
Normal queue state.
THR1
Queue has reached level threshold 1.
RTHR1
Queue has reached level reset threshold 1.
THR2
Queue has reached level threshold 2.
RTHR2
Queue has reached level reset threshold 2.
THR3
Queue has reached level threshold 3.
RTHR3
Queue has reach level reset threshold 3.

 Avitech GmbH 2018 Page 222 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9 CONFIGURATION MENU
This menu contains the system configuration lists. These lists allow the operators to set the
routing parameters, to configure circuits, channels...
The system configuration lists that are active in the operational system have to be consistent
among each other. Any discrepancy can cause messages to be routed incorrectly and can,
in the worst case, make a system instable or cause it to crash. For this reason the lists are
organized in bundles. A bundle is a logical entity, which contains a consistent set of lists. A
bundle contains a single copy of each list.
Different versions of the configuration and routing lists are maintained as separate bundles,
even if only a single entry in one list differs between two bundles and all the other entries and
lists are identical. A version number identifies the different versions.
Before a bundle can be used in the operational system, it has to be transferred from the
administrative database to the operative database. The operative database is composed of
at least one bundle and at most three:
• The active version: this is the bundle version currently used in the operational
system. There can only be one bundle version activated at a given time.
• The old version: this is the bundle version used in the operational system before the
active version was used. There can only be one old bundle version at a given time.
• The new version: This is the bundle version transferred to the operational system
but not yet activated. There can only be one new bundle version at a given time.
The active version is the version currently used in the operational system. After initialising,
the system knows only this version. To activate a new bundle version two possibilities are
offered to the operator:
• Click on the [Transfer New]and then on the [Activate]-button.
• Click on the [Transfer And Activate]-button
Once a bundle has been transferred to the operative database it is frozen and cannot be
modified any longer. Any new bundle based on an operational version (i.e. the active version
or the old version) can only be generated by using the command Copy to make a copy of the
required bundle with a new version number and then modify it. The lists, which constitute a
bundle are shown below:
Circuit Route
This list defines the following aspects of the routing parameters:
• The AFTN outgoing directions. A message can only be routed to a logical
target address contained in this list.
• Destination addressees, which are not allowed in combination with specific
incoming circuits and how messages are handled with specific destination
addressees for each incoming circuit.
• Originator indicators, which are not allowed combination with specific
incoming circuits and how messages are handled.
• The different AFTN channels linked to the circuit.
• Various other routing parameters such as thresholds and overdue timers.

 Avitech GmbH 2018 Page 223 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AFTN Address Route


This list defines the rules of how the routing indicators are mapped to circuits.
AFTN Devices
This list defines the different communication devices of the AFTN channels.
AMHS Management Domain Register
This list defines the following aspects of the AMHS routing parameters:
• The mapping of AFTN nationality letters or designators to AMHS global
domain identifiers (GDI), the address mapping scheme implemented in the
AMHS MD designated by the GDI.
• The definition, for each AMHS MD which adopts the CAAS addressing
scheme according to The AMHS MD Look-Up table, of the values of the MF
address attribute organisation depending on the values of the address
attribute organisation-unit-1 which takes the AFTN location indicators of all
locations within the considered MD.
• The definition of further parameters depending on the GDI (Country, ADMD,
PRMD) of a MD and optionally on values of organisations within an AMHS
MD.
AMHS User Address Look-up
This list allows a free assignment of any X.400 O/R address to a fully qualified (i.e.
exactly 8 letter) AFTN address, regardless which addressing scheme is adopted by
the AMHS Management Domain which the address belongs to.
CIDIN Entry/Exit Centre
This list defines the Entry and Exit Centres.
CIDIN ADAX
This list defines the assignment of an AFTN destination to a CIDIN Exit centre.
CIDIN Routing
This list defines the CIDIN routing rules. It is the assignment of the AX routing
indicators to the virtual circuit groups. The local addresses in the single application
have also been defined here. By local addresses the according MCF shall be put,
however no connection paths shall be entered.
CIDIN Virtual Circuits
This list defines the physical characteristics of the CIDIN PVCs and SVCs. The
entries Circuit, Channel and Phys Proper have to be entered both for PVC and for
SVC. For PVC use the entries LCN, Number of Read Buffers and Number of Write
Buffers. For an SVC, use the entry DNA.

 Avitech GmbH 2018 Page 224 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The following picture shows how the configuration and routing lists depend from one another.

 Avitech GmbH 2018 Page 225 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.1 The System Configuration function

The system configuration unit is used to create modify or delete list bundles. These bundles
contain the configuration and routing lists necessary for the work of the application.
The consistency of the lists within a bundle has to be checked before a list bundle can be
transferred to the operational part of the server and activated as operational bundle. Once a
bundle had been transferred to the server it can no longer be modified.
The system configuration unit is divided in two tables:
• The upper table which shows the lists currently on the operational part of the server.
There can be up to three list bundles: the Active bundle, the New bundle and the Old
bundle.
• The lower table which displays the other list bundles.

9.1.1 Functions

9.1.1.1 File Menu

New
Created a new list bundle
Copy
Copies the selected list bundle

 Avitech GmbH 2018 Page 226 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Edit
Edits the selected list bundle
Import
Opens a file selection window to import a bundle.
Export
Exports the selected bundle.
Delete
Deletes the selected bundle.
Close
Closes the system message configuration.

9.1.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.
Common Services
Opens the Common Services Configuration unit.
Compare bundles
Compares two selected bundles and displays their difference. .

9.1.2 Table columns

9.1.2.1 Upper table

This part is the operational area. It contains the lists bundles transferred to the operational
server. For the list bundles of this table the functions Edit and Save are disabled.
State
The state of the bundle. There can be four different states:
• ACT: The list bundle is the operational bundle at the moment.
• OLD: The last list bundle that was active before the active version.
• NEW: The list bundle uploaded to the server to become active with the
Activate function.
Version
This column shows the version number of the list bundle. It is given automatically by
the system.

 Avitech GmbH 2018 Page 227 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Copy Of
This column shows the version from which the selected version has been copied. It is
given automatically by the system. Following values are possible:
• 1 (bundle based on an existing bundle version).
• NIL (bundle based on empty lists)
Comment
This column shows the comments about the special changes of the bundle version. It
is to be filled by the operator.
Changed On
This column shows the date and time of the latest changes of the bundle version. It is
given automatically by the system.
Changed By
The name of the operator who last changed the list bundle.
Activated On
The date and time when the bundle has been last activated.
Activated By
The name of the operator who activated the list bundle.

9.1.2.2 Lower table

This part is the non-operational area. It contains the lists bundles that are not on the
operational server. These list bundles can be created, modified or deleted.
Version
This column shows the version number of the list bundle. It is given automatically by
the system.
Copy Of
This column shows the version from which the selected version has been copied. It is
given automatically by the system. Following values are possible:
• 1 (bundle based on an existing bundle version).
• NIL (bundle based on empty lists)

 Avitech GmbH 2018 Page 228 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Comment
This column shows the comments about the special changes of the bundle version. It
is to be filled by the operator.
Changed On
This column shows the date and time of the latest changes of the bundle version. It is
given automatically by the system.
Changed By
The name of the operator who last changed the list bundle.

9.2 Common Services Configuration

The common services configuration unit is used to configure printers and e-mail originators.

9.2.1 Functions

9.2.1.1 File Menu

Print
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.

 Avitech GmbH 2018 Page 229 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Print Choice
Opens the printer dialogue. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Close
Closes the system message configuration.

9.2.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

9.2.1.3 Icons on the left side of the table.

Insert row
Depending on the tab selected, opens an empty Printer Configuration mask or an
empty Email Account Configuration mask.
Edit selected row.
Depending on the tab selected, opens a Printer Configuration mask or an Email
Account Configuration mask prefilled with the data of the selected row.
Remove selected row
Deletes the selected row from the list.
Remove all rows
Deletes all items from the list.
Reload
Reloads the data.

9.2.2 Printer configuration Tab

Name
The name of the printer.
Copies
The number of copies to be printed out.

 Avitech GmbH 2018 Page 230 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Left Margin
The number of blank characters at the left side.
Line Length
The number of characters that fit in one line.
Paper Length
The number of lines that fit on one page.
Separator Line
The line to be printed between successive printouts.
Vertical Space
The number of blank lines between successive printouts.
Wrap Unprintable
A flag determining whether or not unprintable characters are to be shown in the form
for example "<SOH>".
Unprintable characters are:

• <NUL> • <SOH> • <STX> • <ETX>


• <EOT> • <ENQ> • <ACK> • <BEL>
• <BS> • <TAB> • <LF> • <VT>
• <FF> • <CR> • <SO> • <SI>
• <DLE> • <DC1> • <DC2> • <DC3>
• <DC4> • <NAK> • <SYN> • <ETB>
• <CAN> • <EM> • <SUB> • <ESC>
• <FS> • <GS> • <RS> • <US>

9.2.3 E-mail accounts configuration Tab

Name
The name of the e-mail account.
Server
The name or IP address of the e-mail server for this account.
User
The name of the user as configured on the e-mail server.

 Avitech GmbH 2018 Page 231 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Password
The password of the user as configured on the e-mail server.
Port
The port number under which the e-mail server expects requests for connections
from users.
Originator
The name of the originator address to be used for mail output.

9.2.4 The Printer Configuration mask

This mask enables the operator to configure a printer.

9.2.4.1 Functions

9.2.4.1.1 File Menu

Print
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Print Choice
Opens the printer dialogue. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.

 Avitech GmbH 2018 Page 232 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Reload
Loads the last saved date.
Close
Closes the system message configuration.
Close
Closes the system message configuration.

9.2.4.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

9.2.4.2 Fields
Name
The name of the printer.
Copies
The number of copies to be printed out.
Left Margin
The number of blank characters at the left side.
Line Length
The number of characters that fit in one line.
Paper Length
The number of lines that fit on one page.
Vertical Space
The number of blank lines between successive printouts.
Wrap Unprintable
A flag determining whether or not unprintable characters are to be shown in the form
for example "<SOH>".
Unprintable characters are:

• <NUL> • <SOH> • <STX> • <ETX>


• <EOT> • <ENQ> • <ACK> • <BEL>
• <BS> • <TAB> • <LF> • <VT>
• <FF> • <CR> • <SO> • <SI>
• <DLE> • <DC1> • <DC2> • <DC3>
• <DC4> • <NAK> • <SYN> • <ETB>
• <CAN> • <EM> • <SUB> • <ESC>
• <FS> • <GS> • <RS> • <US>

 Avitech GmbH 2018 Page 233 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Separator Line
The line to be printed between successive printouts.

9.2.5 The Email Account Configuration mask

The common services configuration unit is used to configure printers and e-mail originators.

9.2.5.1.1 File Menu

Print
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Print Choice
Opens the printer dialogue. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Reload
Loads the last saved date in the message configuration.

 Avitech GmbH 2018 Page 234 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Close
Closes the system message configuration.
Close
Closes the system message configuration.

9.2.5.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

9.2.5.1.3 Icons on the left side of the table.

Insert row
Inserts a new row
Remove selected row
Deletes the selected row from the list.
Remove all rows
Deletes all items from the list.

9.2.5.2 Fields
Name
The name of the e-mail account.
Server
The name or IP address of the e-mail server for this account.
Port
The port number under which the e-mail server expects requests for connections
from users.
User
The name of the user as configured on the e-mail server.
Password
The password of the user as configured on the e-mail server.
Originator
The name of the originator address to be used for mail output.
Recipients
The name of the recipient addresses to be used for mail output.

 Avitech GmbH 2018 Page 235 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.3 Compare bundles

This function allows the operator to track the changes between list bundles.
First the operator has to choose the two list bundles to be compared. Clicking on the
[Compare]-button starts the comparison. A new window opens in which the results are
displayed. This action can take some time according to the number entries to be compared.

In the bundle comparison window each configuration list is displayed within a separate tab.
The name of the list in which some changes has been made is written in bold.
The changes within a list are highlighted in different colours according to the bundle.

Colour Description

Magenta underlined Text modified in bundle 1

Orange underlined Text modified in bundle 2

 Avitech GmbH 2018 Page 236 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.4 Bundle Details

A double click on a line of the lower table in the System Configuration unit opens the Bundle
unit. In this unit the operator can modify the configuration lists.

9.4.1 Functions

9.4.1.1 File menu

New
Create a new bundle
Print
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.

 Avitech GmbH 2018 Page 237 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Print Choice
Opens the printer dialogue. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Reload
Reload this bundle without saving the changes
Save
Save this bundle
Close
Closes the system message configuration.

9.4.1.2 Action menu

Check
Checks the bundle for consistency. Once the check is finished, the system displays
an information window with the results of the check.
Transfer
Transfers the bundle from the non-operational area to the operational area as NEW
bundle.
Initialize
Transfers the bundle to the operational area and restarts the MHS.
Activate
Activates the bundle on the server
Reset Transfer
Transfers the bundle with the state NEW from the operational area to the non-
operational area.

 Avitech GmbH 2018 Page 238 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.4.1.3 AMC menu

Import Address Look-up Tables


Opens the Import Address Look-up Tables unit
Export Look-up Tables
Opens the Export Address Look-up Tables unit
Import Routing Tables
Opens the Import Routing Tables unit

9.4.1.4 Options Menu

Show Toolbar
Hides or displays the toolbar.

9.4.1.5 Table icons

Insert row
Opens the corresponding form with the fields set to their default values.
Edit selected row
Opens the corresponding form to edit the entry.
Remove selected row
Deletes the selected row.
Remove all rows
Deletes all rows.
Reload the data
Reloads the contents of the table.

9.4.2 Fields

Version
Shows the version number of the list bundle. It is given automatically by the system.

 Avitech GmbH 2018 Page 239 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Copy of
Shows the version from which the selected version has been copied. It is given
automatically by the system. Following values are possible:
• 00000001 (bundle based on an existing bundle version).
• NIL (bundle based on empty lists)
State
The state of the bundle. There can be four different states:
• ACTIVE: The list bundle is the operational bundle at the moment.
• OLD: The last list bundle that was active before the active version.
• NEW: The list bundle uploaded to the server to become active with the
Activate function.
• WORKING: The list bundle has not been transferred to the operational
database and can be modified.
User
The login of the user who last changed this bundle
Last Changed
Shows the date and time of the latest changes of the bundle version. It is given
automatically by the system.
Comments
Shows the comments about the special changes of the bundle version. It is to be
filled by the operator.

9.4.3 Tabs
AFTN Circuit Route

Displays the list of all circuit routes configured in this bundle. For more information
about the circuit routes please refer to the section the AFTN Circuit Route list of this
chapter.

 Avitech GmbH 2018 Page 240 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AFTN Address Route

Displays the list of all AFTN address routes configured in this bundle. For more
information about the AFTN address routes please refer to the section AFTN Address
Route of this chapter.
Copy Addresses

Defines messages to be copied to other circuits. For more information about the copy
address please refer to the section Copy Addresses of this chapter.

 Avitech GmbH 2018 Page 241 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AFTN Device

Displays the list of all AFTN devices configured in this bundle. For more information
about the AFTN devices please refer to the section AFTN Device of this chapter.
SITA-AFTN Mapping

Maps SITA addresses to AFTN addresses and vice versa. For more information
about the SITA-AFTN mapping please refer to the section SITA-AFTN Mapping of
this chapter.

 Avitech GmbH 2018 Page 242 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AMHS Automated diversion

Displays the list of all AMHS Automated diversions configured in this bundle. For
more information about the AMHS Automated diversions please refer to the section
AMHS Automated diversion of this chapter.
AMHS Management Domain

Displays the list of all AMHS management domain registers configured in this bundle.
For more information about the AMHS management domain registers please refer to
the section AMHS Management Domain of this chapter.

 Avitech GmbH 2018 Page 243 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AMHS Miscellaneous

Displays the list of all AMHS Miscellaneous properties configured in this bundle. For
more information about the AMHS Miscellaneous please refer to the section AMHS
Miscellaneous of this chapter.
AMHS User Addresses

Displays the list of all AMHS user addresses configured in this bundle. For more
information about the AMHS user addresses please refer to the section AMHS User
Addresses of this chapter.

 Avitech GmbH 2018 Page 244 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AMHS User Agent

Displays the list of all AMHS user agents configured in this bundle. For more
information about the AMHS user agents please refer to the section AMHS User
Agent of this chapter.
MTA Circuit

Displays the list of all MTA circuits configured in this bundle. For more information
about the MTA circuit please refer to the section MTA Circuit of this chapter.

 Avitech GmbH 2018 Page 245 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CIDIN Entry/Exit Centre

Displays the list of all CIDIN Entry/Exit centres configured in this bundle. For more
information about the CIDIN Entry/Exit centres please refer to the section CIDIN
Entry/Exit Centre of this chapter.
CIDIN ADAX

Displays the list of all CIDIN ADAX configured in this bundle. For more information
about the CIDIN ADAX please refer to the section CIDIN ADAX of this chapter.

 Avitech GmbH 2018 Page 246 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CIDIN Routing

Displays the list of all CIDIN routes configured in this bundle. For more information
about the CIDIN routes please refer to the section CIDIN Routing of this chapter.
CIDIN Virtual Circuit

Displays the list of all CIDIN virtual circuits configured in this bundle. For more
information about the CIDIN virtual circuits please refer to the section CIDIN Virtual
Circuit of this chapter.

 Avitech GmbH 2018 Page 247 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.4.4 Import Address Look-up Tables

This unit allows the operator to import AMC Lists for the AMHS Management domain
Register and / or the AMHS User Address configuration lists.

9.4.4.1 Functions

9.4.4.1.1 File Menu

New
Clears all the fields
Compare Lists
Compares the imported AMC lists with the current AMHS configuration lists of the
selected bundle. Depending on the lists imported the results will be displayed in the
Compare MDR tab or in the Compare User Addresses tab.
Import Lists
Imports, modifies or deletes the selected entries in the corresponding AMHS
configuration lists.

 Avitech GmbH 2018 Page 248 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Close
Closes the unit.

9.4.4.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

9.4.4.2 Fields

9.4.4.2.1 Upper Part

AmhsMdRegister File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
management domain file to be imported.
Note: The CAAS table file has to be chosen as well in order to make a
successful list comparison.
AmhsCaasTables File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
CAAS table file to be imported.
Note: The management domain file has to be chosen as well in order to
make a successful list comparison.
User Addresses File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
user addresses file to be imported.

 Avitech GmbH 2018 Page 249 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.4.4.2.2 The Compare MDR tab

This tab is used to compare the entries of the current Management Domain Register with the
entries of the new loaded Management Domain Register.
Name
The name of the country, state or territory.
Nationality Letters
The ICAO nationality letters.
Country
The name of the country. In AMHS the ICAO standard is XX.
ADMD
The administration management domain. In AMHS the ICAO standard is ICAO.
PRMD
The private management domain.
Naming Context
Supplementary information necessary for the classification in the AMHS directory.
Operation
The result of the comparison. It is possible do filter the entries according to the result
of the comparison.
• ADD
• KEEP
• REPLACE
• DELETE

 Avitech GmbH 2018 Page 250 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Selection
If this checkbox is ticked the entry will be imported when clicking on the [Import
Lists]-button. Furthermore it is possible do filter the entries according to the checkbox
ticked or not ticked.
• Selected
• Not selected

9.4.4.2.3 The Compare CAAS tab

This tab is used to compare the entries of the current CAAS table with the entries of the new
loaded CAAS table.
Country
The name of the country. In AMHS the ICAO standard is XX.
ADMD
The administration management domain. In AMHS the ICAO standard is ICAO.
PRMD
Private management domain.
Organisation
The name of the organisation of this country, state or territory.
Organisation Unit
The organization-defined unit.
Operation
The result of the comparison. It is possible do filter the entries according to the result
of the comparison.
• ADD
• KEEP
• REPLACE
• DELETE

 Avitech GmbH 2018 Page 251 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Selection
If this checkbox is ticked the entry will be imported when clicking on the [Import
Lists]-button. Furthermore it is possible do filter the entries according to the checkbox
ticked or not ticked.
• Selected
• Not selected

9.4.4.2.4 Compare User Addresses

AFTN Address
The AFTN address.
Country
The name of the country. In AMHS the ICAO standard is XX.
ADMD
The administration management domain. In AMHS the ICAO standard is ICAO.
PRMD
Private management domain.
Organisation
The name of the organisation of this country, state or territory.
Organisational Unit 1
The first organisation-defined unit.
Operation
Result of the comparison
• ADD
• KEEP
• REPLACE
• DELETE

 Avitech GmbH 2018 Page 252 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Selection
If this checkbox is ticked the entry will be imported when clicking on the [Import
Lists]-button. Furthermore it is possible do filter the entries according to the checkbox
ticked or not ticked.
• Selected
• Not selected

9.4.5 Export Address Look-up Tables

This unit allows the operator to export the entries of the AMHS Management domain
Register and / or the AMHS User Address configuration lists into AMC Lists

9.4.5.1 Functions

9.4.5.1.1 File Menu

Reset Sources
Clears all the fields
Export Address look-up Tables
Exports the entries of the AMHS Management domain Register and / or the AMHS
User Addresses configuration lists to the selected AMC lists.
Close
Closes the Export Address Look-up function.

9.4.5.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

 Avitech GmbH 2018 Page 253 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.4.5.2 Fields
AmhsMdRegister File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
management domain file to be overwritten by the export. It is also possible to write
the file path and name manually in the field. Entering the name of a file that does not
exist will create this file when the [Export]-button is pressed.
Note: The AmhsCaasTables File has to be chosen as well in order to
make a successful export.
AmhsCaasTables File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
CAAS table file to be overwritten by the export. It is also possible to write the file path
and name manually in the field. Entering the name of a file that does not exist will
create this file when the [Export]-button is pressed.
Note: The AmhsMdRegister File has to be chosen as well in order to
make a successful export.
UserAddresses File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
user addresses file to be overwritten by the export. It is also possible to write the file
path and name manually in the field. Entering the name of a file that does not exist
will create this file when the [Export]-button is pressed.

9.4.6 Import Routing Tables

This unit allows the operator to import AMHS, AFTN and/or CIDIN routing lists to the system.

9.4.6.1 Functions

9.4.6.1.1 File Menu

New
clears all the fields
Import routing tables
Imports, the selected entries in the corresponding routing configuration lists.

 Avitech GmbH 2018 Page 254 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Close
Closes the unit.

9.4.6.1.2 Options Menu

Show Toolbar
Hides or displays the toolbar.

9.4.6.2 Fields
AFTN Routing File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
AFTN routing file to be imported.
AMHS Routing File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
AMHS routing file to be imported.
CIDIN Routing File
Clicking on the [Open]-button opens a dialog in which the operator can choose the
CIDIN routing file to be imported.

9.5 Configuration and routing lists

9.5.1 Common configuration and routing functions

9.5.1.1 File

New
Creates a new entry of the selected list type in the bundle.
Print
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.

 Avitech GmbH 2018 Page 255 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Print Choice
Opens the printer dialogue. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Reload
Reloads the current entry, ignoring the unsaved changes.
Close
Closes the entry.

9.5.1.2 Action

Save
Saves the current entry in the list type of the bundle.
Save As
Saves the current entry as a new entry in the list type of the bundle.
Note: If the new entry to be saved has been created from an already
existing entry, the text entered in the first field of the second line of the
unit has to be unique in order to save this new entry.
Delete
Deletes the current entry from the list.
Open Bundle
Opens the list bundle to which this entry belongs.
Previous Item
Display the previous entry of the configuration list.
Note: any unsaved change will be discarded when moving to another
entry of the configuration list.
Next Item
Display the next entry of the configuration list.
Note: any unsaved change will be discarded when moving to another
entry of the configuration list.

 Avitech GmbH 2018 Page 256 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.1.2.1 Options

Show Toolbar
Hides or displays the toolbar.

9.5.2 Common configuration and routing fields

9.5.2.1 Fields
Version
The bundle version this entry belongs to.
State
The state of the bundle. There can be four different states:
• ACTIVE: The list bundle is the operational bundle at the moment.
• OLD: The last list bundle that was active before the active version.
• NEW: The list bundle uploaded to the server to become active with the
Activate function.
• IN WORK: The list bundle has not been transferred to the operational
database and can be modified.
Comments
The comments entered for the bundle.
Last Changed
The date and time this entry was last changed
User
The login of the user who last changed this entry.

9.5.3 Conventions used


The conventions used in this manual describe the entries of the fields of the configuration
lists.
• First the argument type that has to be used is stated between the following signs: <
and >.
• Then in subscript and between round or square brackets more information about the
possible values is given.
• The default value of a field, if any, will be stated after the parameter description.

 Avitech GmbH 2018 Page 257 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.3.1 Argument Types


Argument Description

A Any character according to ASN.1 notation.

C Any character according to ASN.1 notation. The field is case sensitive

N Digit.

U Upper case character.

9.5.3.2 Possible combinations


Combination Description

(x) Entry is mandatory

[x] Entry is optional

arg1, arg2 Argument type 1 AND argument type 2 are possible.

val1 | val2 Either value 1 OR value 2 is possible.

<arg>x Argument repeated x times. It is not possible to have less or more argument than this
given number.

<arg>x...y x to y arguments allowed; x being the minimum number of arguments and y being the
maximum number of characters allowed for the parameter.

<N>3-15 Possible numbers are comprised between these numbers and include them.

<arg>NIL The field is empty.

Examples

Example Description

<U>(1...8) The value can be any combination of 1 to 8 upper case characters. This entry is
mandatory

<N>[3-15] The value can any number between 3 and 15 including these numbers. This entry is
optional

<U, N>(1...8) Any combination of 1 to 8 upper case characters and digits. This entry is mandatory

 Avitech GmbH 2018 Page 258 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.4 The AFTN Circuit Route list

All AFTN circuits are listed in the AFTN Circuit Route tab of the Bundle Details unit.

The Circuit unit is to used create and modify a circuit, its routing and channels.

9.5.4.1 Functions
The functions of the AFTN Circuit Route list are described in the section Common
configuration and routing functions of this chapter.

 Avitech GmbH 2018 Page 259 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The File/New function opens a popup that gives the choice of creating an AFTN or a
workstation circuit.

9.5.4.2 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
Name
The name given to the circuit. Value: <U, N>1...16 no default value.
The fields of the various tabs are described in the following sections:
• The Routing tab
• The AFTN Circuit Details tab
• The Properties tab
• The Channels tab
• The Barring tab
• The Originator tab
• The Incoming Responsibility tab

9.5.4.3 The Routing tab

This tab defines the AFTN logical targets directions for the circuit.
Circuit
This field defines the standard circuit used for outgoing messages. Entering the name
of a circuit in this field automatically fills out the priorities fields with the same name.
Value: if the standard outgoing circuit is the circuit that is being created this field shall
be left empty. Otherwise a finder is available by pressing the [F4]-key. No default
value
Diversion Circuit
This field defines the standard diversion circuit for outgoing messages.
Default value OVF.

 Avitech GmbH 2018 Page 260 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Priorities
These fields define the standard circuit for outgoing messages used according to the
priority of the message.
Copy to Circuit
This table allows the operator to define additional circuit(s) in case of multi circuit
distribution.

9.5.4.4 The AFTN Circuit Details tab

This tab defines supplementary routing parameters.


Back Standard
Defines whether or not a message may be transmitted back to the relay station from
which it was received. It is used when the message is not diverted.
Value: only the values of the drop down list are allowed. Default value: YES.
YES
Messages can be sent back to the previous relay station.
NO
Messages cannot be sent back to the previous relay station.
HINT
Messages can be sent back to the previous relay station. A system message
will be sent to the operator whenever this happens.
STRIP
Messages cannot be sent back to the previous relay station. The appropriate
address will be stripped from the message, an entry will be made in the journal
and a system message will be sent to the operator.
Back Diversion
Defines whether or not a message may be transmitted back to the relay station from
which it was received. It is used when the message is diverted.

 Avitech GmbH 2018 Page 261 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Value: only the values of the drop down list are allowed. Default value: YES.
YES
Messages can be sent back to the previous relay station.
NO
Messages cannot be sent back to the previous relay station.
HINT
Messages can be sent back to the previous relay station. A system message
will be sent to the operator whenever this happens.
STRIP
Messages cannot be sent back to the previous relay station. The appropriate
address will be stripped from the message, an entry will be made in the journal
and a system message will be sent to the operator.
Max Addresses
Specifies the maximum number of addresses which can be contained in an AFTN
message received by this circuit.
Value: The possible values are numbers between 1 and 21. Default value: 21.
Substitution PDAI
This entry specifies whether or not a predetermined addressee indicator in an
outgoing message should be replaced by the appropriate elementary addressee
indicator (or indicators) routed to the target.
If the checkbox is ticked the predetermined addressee indicator should be replaced
by the appropriate elementary addressee indicator(s).
Default value: checkbox ticked.
Diversion Handling
Target Address Diversion
Specifies whether this circuit can be used as the target of an address
diversion. If the checkbox is ticked this circuit can be used as the target of an
address diversion.
Default value: checkbox ticked.
Target Direction Diversion
Specifies whether this circuit can be used as the target of a direction diversion.
If the checkbox is ticked this circuit can be used as the target of a direction
diversion.
Default value: checkbox ticked.
Source Direction Diversion
Specifies whether this circuit can be diverted. If the checkbox is ticked this this
circuit can be diverted.
Default value: checkbox ticked.

 Avitech GmbH 2018 Page 262 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Allow Automatic Diversion


Specifies whether this circuit can be diverted automatically. If the checkbox is
ticked this this circuit can be diverted automatically.
Default value: checkbox not ticked.

9.5.4.5 The Properties tab

This tab defines the channels belonging to the circuit as well as some various properties of
the circuit. It is only available if the circuit type is AFTN.
Handling Of Faulty Msg.
For the handling of faulty messages the system has the ability to use either the
internationally defined SVCs (ICAO standard) or especially user defined domestic
SVCs / plain text.
Value: only the values of the drop down list are allowed. Default value:
"INTERNATIONAL".
DOMESTIC
User defined.
INTERNATIONAL
ICAO standard.
SPECIAL_FORMAT
Not used.
COROBOR
Not used.
Adjacent Address
For channels with Convey mode "MTP" and "GEN" the previous station has to be
entered. It specifies the AFTN addressee indicator, which will be used when the
system generates an SVC message. For a given AFTN address a suitable routing
indicator in the "AFTN Address Route" is necessary.
Value: <U>(8).

 Avitech GmbH 2018 Page 263 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Overdue Handling
When a message in a queue becomes older than the time defined in the "Overdue
Timers" field the switch will generate a system message "OLDEST MESSAGE", if
"SYSTEM_EVEN"T is selected. If "SPECIAL_POSITION" or "DEFINED_TARGET" is
selected, the message will be routed to the special position or to the defined target.
Value: only the values of the drop down list are allowed. Default value:
"SYSTEM_EVENT".
SYSTEM_EVENT
Only the system message "OLDEST MESSAGE" will be generated for this
circuit queue.
SPECIAL_POSITION
The system message "OLDEST MESSAGE" will generated for this circuit
queue and the message will be routed to the special position.
DEFINED_TARGET
The system message "OLDEST MESSAGE" will generated for this circuit
queue and the message will be routed to the destination set in the field
Overdue Target.
Overdue Target
The target circuit where messages older than the time specified in the field Overdue
Timers will be directed when "Overdue Handling" is set to "DEFINED_TARGET".
Value: possible values can be viewed by pressing the [F4]-key. Only circuits already
existing in the list bundle can be chosen. No default value.
Overdue Timers
When a message with the priority SS, DD, FF, GG or KK in a queue becomes older
than the specified time (in seconds) the switch will generate the system message
"OLDEST MESSAGE".
Value: <N>[0 | 60-3600] default value: 900.
60... 3600
Increments of 60.
0
No "OLDEST MESSAGE" message will be generated for this queue.
Queue Stalled
Specifies the time (in seconds) to be waited until the switch will generate a system
message "QUEUE STALLED", when no message has been transferred from a not
empty queue.
Value: <N>[0 | 60-3600] default value: 360.
60 ... 3600
Increment of 60.
0
No QUEUE STALLED message will be generated for that queue.

 Avitech GmbH 2018 Page 264 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Mode Of Selection
This parameter is used for channels working with X.25 devices. If more than one
Link/log. channel peer is active, the load distribution via these peers can be
administrated.
Value: only the values of the drop down list are allowed. Default value:
"INTERNATIONAL".
FIRST_FREE
The system tries to use the first Link/log. channel peer to establish a
connection. If there is an error situation, the system chooses the next peer.
CYCLIC
The system takes the Link/log. channel peers in a cyclic way each time a
connection is established.
Reset-/Thresholds
These fields define the threshold and reset threshold values for the circuit.
• When the number of message in the circuit queue reaches one of the defined
values the corresponding system message is generated by the system.
• If the number of messages in the circuit queue exceeds the value set for
threshold 3 the system moves automatically as many messages from that
queue to the overflow position until the value set for reset threshold 3 is
reached.
• When the value set for reset threshold 2 is reached a certain number of
messages previously moved to the overflow position is put back in the queue.
The system first moves the messages with the highest priority and which have
been received first. The number of messages thus moved is calculated as
follows: threshold 3 - reset threshold 2.
• When the value of reset threshold 1 is reached all messages previously
moved to the overflow position are put back in the queue.
1.
Left field value: <N>[1-9994] default value: 5
Right field value: <N>[2-9995] default value: 10
2.
Left field value: <N>[3-9996] default value: 20
Right field value: <N>[4-9997] default value: 50
3.
Left field value: <N>[5-9998] default value: 100
Right field value: <N>[6-9999] default value: 200

 Avitech GmbH 2018 Page 265 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.4.6 The Channels tab

Defines the name and the characteristics of the channels belonging to the circuit. A channel
is identified by up to 16 upper case characters or digits.
The fields of the various tabs are described in the following sections:
• The General tab
• The CSN/CH tab
• The Format tab
• The SVC Handling tab
• The Timer tab

9.5.4.6.1 The General tab

Channel
The name of the channel.
Value: <U>(1...16) No default value.
Device
The name of the device this channel is connected to.
Note: The device has to be created before the AFTN channel.

 Avitech GmbH 2018 Page 266 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CID In
Defines the channel identifier for outgoing messages. This parameter is mandatory
for the convey modes "MTP" and "GEN". It consists in three uppercase characters.
The first two characters shall not be the same (e.g. AA is not allowed). It is not
allowed to have twice the same CID within a certain device type (X.25, TCP, FAX, ...).
Value: <U>(3) No default value.
CID Out
Defines the channel identifier for incoming messages. This parameter is mandatory
for the convey modes "MTP" and "GEN". It consists in three uppercase characters.
The first two characters shall not be the same (e.g. AA is not allowed). It is not
allowed to have twice the same CID within a certain device type (X.25, TCP, FAX...).
Value: <U>(3) default value: the letters of the parameter "CID Out" in the following
order: 2, 1, 3.
Connection Type
Defines the type of connection to a device.

Device Value
Type

TCP TEMPORARY | PERMANENT | REMOTE | REMOTE_EMPTY_MESSAGE |


TWO_WAY_MONOLOGUE

TAS PERMANENT

FAX FIX

DIO TEMPORARY

FEC REMOTE_FRONTEND

X.25 PVC | TEMPORARY | PERMANENT | REMOTE

SIT TEMPORARY | PERMANENT | MATIP_BIL | MATIP_SLV | MATIP_MST

FIX
The device is connected via a fixed line.
PVC
Permanent connections will be initiated by the switch, when a device has
started. The switch knows all necessary information to set up that connection.
TEMPORARY
Temporary connections may be initiated by the switch as well as by the
device. The connection will only be closed by the switch after a certain period
of inactive time (Parameter Inactivity in the Timer tab).
PERMANENT
Permanent connections will be initiated by the switch, when a device has
started. The switch knows all necessary information to set up that connection.

 Avitech GmbH 2018 Page 267 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

REMOTE
(only used by TCP devices) This is a permanent connection, which may be
initiated and terminated only by the device.
REMOTE_EMPTY_MESSAGE
(only used by TCP devices) Quite identical to REM with the difference that the
switch sends an Empty Message informing the device about the AFTN
Identifier, which may conclude on the circuit and on the channel.
REMOTE_FRONTEND
Only in combination with FEC devices.
MATIP_BIL
The MATIP session is established from both sites.
MATIP_SLV
The MATIP session is established from the other sites.
MATIP_MST
The MATIP session is established from the own centre.
TWO_WAY_MONOLOGUE
Two connections are established at the same time: one to send messages
and one to receive messages.
Convey Mode
Defines whether the communication between the AFTN switch and the device uses
the protocol according to Annex 10/II completely ("MTP"), partly ("GEN") or not at all
("NONE"). See also the table of section Connections between an AFTN/CIDIN Switch
and devices of this chapter for further explanations of the dependencies of other
parameters from Convey Mode and Working Method.
Value: <U> (MTP | GEN | ACC) default value: MTP.
MTP
The acronym stands for Manual of Teletype Practice. Some of the features
may be switched off by AMS commands or by changes in the configuration
lists. It is not possible to change the value for Msg Ident, which is "MTPID +
CSN".
GEN
The value "MTPID + CSN" for Msg Ident can be changed to other values. The
AFTN switch generates sequence numbers for incoming messages.
Sequence numbers contained in messages will be discarded. Sending of
channel check messages is possible. A channel with the Working method
"CONF" needs "GEN" as Convey Mode.
ACC
The system accepts the transmission ID of the received message without
checking the CSN.

 Avitech GmbH 2018 Page 268 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Initial Channel State


Defines the initial operational state of the channel. This state is activated, if a new
bundle is activated via the AMS command "ACT_L NEW". The state may have
additional values (e.g. "BLOCKED") during operation of the system.
Value: <U> (OPEN | CLOSED | TEST | BLOCKED | HOLD | DEAD | CLOSE_INPUT) default value: OPEN.
OPEN
Messages can be sent to and received from this channel.
CLOSED
No messages can be sent to or received from this channel.
TEST
Only TEST messages can be sent to or received from this channel.
BLOCKED
No messages can be sent to or received from this channel.
HOLD
Messages can only be transmitted from this channel.
CLOSE_INPUT
Messages can only be sent to this channel.
Working Method
Specifies how incoming messages have to be handled. See also the table of section
Connections between an AFTN/CIDIN Switch and devices of this chapter for further
explanations of the dependencies of other parameters from Convey Mode and
Working Method. For instance the Working methods "CONF" and "CONF
FORMATSUP" are not possible together with the Convey Mode "MTP".
Value: <U> (CORRECTION_POSITION | GENERATE_SERVICE_MESSAGE | FULL_SVC CORPOS_PARTIAL_RELAY)

default value: CORRECTION_POSITION.


CORRECTION_POSITION
Faulty messages are directed to the correction position.
GENERATE_SERVICE_MESSAGE
Generates an adequate SVC when a faulty message is received and sends it
to the originator or to the previous station.
Note: If there is an error reason for which no SVC is defined or if
there are different types of errors within one message the
message is forwarded to the correction position and no SVC is
generated.
FULL_SVC
Generates an adequate SVC when a faulty message is received and sends it
to the originator or to the previous station. Faulty messages are never directed
to the correction position.
CORPOS_PARTIAL_RELAY
Messages that can only be transmitted to some addresses will be handled as
follows:

 Avitech GmbH 2018 Page 269 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• The message will be transmitted to the addresses for which it is


possible to execute the transmission
• The message with the addresses for which it is not possible to execute
the transmission, will be transferred to the correction position.
Operation Mode
For each channel the mode of operation has to be administrated
Value: <U> (FULL_DUPLEX | HALF_DUPLEX) default value: FULL_DUPLEX.
FULL_DUPLEX
It is possible to have incoming and outgoing communications simultaneously.
HALF_DUPLEX
A connection may be used only in one direction at a given time. "HDPX" is
necessary if the checkbox Confirm Connection of the Mode tab is ticked.

9.5.4.6.2 The CSN/CH tab

CSN
Control
Specifies whether the channel sequence number of an incoming message has to be
checked or not.
Length
Specifies the length (number of digits) of the channel sequence number
(CSN).
Value: <N> (3-4) default value: 4.
CH Transmission
Checkbox
Defines whether the system shall send periodic channel check messages on
the channel or not.

 Avitech GmbH 2018 Page 270 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Interval
The time in minutes between two outgoing channel check messages.
Value: <N> (1-60) default value: 20.
Example: If 15 is entered, messages will be sent at xx:00, xx:15, xx:30 and
xx:45 i.e. at 24:00, 00:15, 00:30 ... 23:45 If 60 is entered, messages will be
sent full hour.
CH Reception
Checkbox
Specifies whether the system shall expect periodic channel check messages
coming on this channel or not.
Interval
The time in minutes between two incoming channel check messages.
Value: <N> (3-60) default value: 20.
Early
Sets the tolerance (in minutes) for early incoming channel check messages.
Value: <N> (0-59) default value: 2.
Late
Sets the tolerance (in minutes) for late incoming channel check messages.
Value: <N> (0-59) default value: 3.
Note: The sum of the values "CH Early" and "CH Late" must be
lower than the value of "CH Supervision Interval".

9.5.4.6.3 The Format tab

Message Identification Format


A message identification is inserted in the header of a message. Different formats of
Msg Ident are possible. For the Convey Modes MTP or GEN a Msg Ident is
necessary.
Value: <U>(TID | CID | IMID | NONE) default value: TID.
TID
The Msg Ident is a combination of the CID and the channel sequence number
(CSN) (i.e. ABA012 if CSN length has the value 3 and ABA0012 if CSN length
has the value 4). It is the only possible value if Convey Mode is set to MTP or
the default value if Convey Mode is set to GEN.

 Avitech GmbH 2018 Page 271 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

CID
The Msg Ident consists only of the CID (e.g. ABA).
IMID
The Msg Ident is identical to the internal message identification (IMID) (i.e.
1234.987654321.567).
NONE
No Msg Ident is inserted on the header of a message. This is the default value
if Convey Mode is set to NONE.
Alignment
Value: <U> (CR_LF | CR_CR_LF) default value: CR_LF.
Specifies the contents of the alignment function (<CR> <LF> or <CR> <CR> <LF>).
This is used when composing the header information for outgoing messages. For
incoming messages both alignment types are accepted.
Message Format
Defined the message format with which messages will be transmitted on this channel.
Value: <U>(SOH | ZCZC) default value: SOH.
DTG length
Specifies whether a date time group will be inserted into an outgoing message or not.
This parameter is only necessary, if Convey Mode is set to MTP or GEN. Otherwise it
is pre-set to NO.
Max Output Text Length
Specifies the maximum number of characters allowed to be handled within a
message. If a message consists of more characters than defined here, it will be
handled as defined by the setting of parameter oversize msg handling.
Value: <N>(100-65536) default value: 1800.
Transfer Rate DTE
Defines the connection speed of the channel. The value is used to calculate the time
necessary to transfer a message to a channel. The next message will not be
transferred until this time has passed.
Value: <N>[0-128000]
Page Feed Sequence
The page feed sequence belongs to the ITA-2 ending and consists of seven <LF>
characters. It is followed by the End of Message signal.
Message Separation Signal
Specifies whether messages are to be separated by 12 letter shift, when they are
output.
Note: "letter shift" and "figure shift" are used to distinguish letters from
numbers (figures) within the"I2" code. After a "letter shift" is sent all signs
have to be interpreted as letters until a "figure shift" is sent. From this
moment on all transmitted signs have to be interpreted as numbers until
the next "letter shift".

 Avitech GmbH 2018 Page 272 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Confirmation
Answerback
This entry contains the answerback string expected to be received on this
channel when inquired by the system. The string consists of 8 up to 16
characters, which may be uppercase letters or numerical digits.
The Answerback can only be used in combination with Working method =
CONF.
Value:<U, N>[8...16]
Confirmation checkbox
Defines whether or not the system inquires the answerback string on this
channel.
Replace Prohibited Characters
Activates or deactivates the automatic check for non-ICAO characters in incoming
messages.
Value: <U>(ICAO | SITA | NO) default value: ICAO or SITA, depending on the type of the
device entered in the General tab.
ICAO
If the system detects a non-ICAO character in a message coming from this
particular channel, the non-ICAO character will be automatically replaced with
a question mark.
Note: this value cannot be selected if the type of the device
entered in the General tab is SIT.
SITA
If system detects a non-SITA character in a message coming from this
particular channel, the non-SITA character will be automatically replaced with
a question mark.
Note: this value can only be selected if the type of the device
entered in the General tab is SIT.
NO
No character check will be performed.
Fold Long Lines
Defines whether long lines are to be folded or not.

 Avitech GmbH 2018 Page 273 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.4.6.4 The SVC Handling tab

Generation
LR LS (open)
Defines whether a SVC message has to be generated informing the channel
of the last sent and received channel sequence numbers, when the state of a
channel changes to open (LR LS = Last Received, Last Sent).
LR EXP
Defines the action to be executed when a sequence control check indicates,
that the received sequence number is lower than expected (LR EXP = Last
Received, Expected).
QTA MIS
A sequence control check indicates that a message sent to this station has not
been received. The channel sends this message to the switch to require
retransmission of lost messages.
Cyclic LR LS
Defines whether a SVC message has to be generated at configurable times
informing the channel of the last sent and received channel sequence
numbers (LR LS = Last Received, Last Sent).
Value: <N> (0-24) No default value.
MIS CH
Defines the action to be executed when a channel check message is not
received within the expected interval.
Value: <U> (GEN_SVC | GEN_SVC_NON_BLOCK | SYSTEM_EVENT) default value: GEN_SVC.
GEN_SVC
An SVC MIS CH message will be generated, the operator will be informed by
a system event. The channel will be set automatically in the state blocked.
GEN_SVC_NON_BLOCK
An SVC MIS CH message will be generated, the operator will be informed by
a system event. The channel will not be set automatically in the state blocked.
SYSTEM_EVENT
The operator will be informed by a system event, no SVC MIS CH message
will be generated. The channel will not be set automatically in the state
blocked.

 Avitech GmbH 2018 Page 274 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Automatic Repetition
QTA MIS
Upon reception of an SVC QTA MIS message, retrieves automatically the
missing message(s) and sends it (them) to the originator of the SVC message.
QTA RPT TID
Upon reception of an SVC QTA RPT TID message, retrieves automatically the
message with the specified transmission identifier and sends it to the
originator of the SVC message.
QTA RPT OGN
Upon reception of an SVC QTA RPT OGN message, retrieves automatically
the message with the specified filing time and originator and sends it to the
originator of the SVC message.

9.5.4.6.5 The Timer tab

'Inactivity
Specifies the time (in seconds) the switch waits before destroying inactive temporary
connections. This is only used on connections with Connection Type set to
TEMPORARY
Value: <N> (0-3600) default value: 0 or 180 depending on the Connection Type set.
1 ... 3600
If Connection Type is set to TEMPORARY the default value is 180.
0
If Connection Type is set to other values. No change is possible in this case.
Receive Timeout
Specifies the time (in seconds) the system will wait; when during the reception of a
message, nothing is received any longer.
Value: <N> (60-3600) default value: 300.
Example: The system is receiving a message and the ling breaks before
the reception of the message ending. The system will wait the time
entered in the "Receive Timeout" field before adding "ARTIFICIAL
ENGING ADDED" to the message and handling is as the configuration
specifies.

 Avitech GmbH 2018 Page 275 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Continue After Break


Time (in seconds) after which the switch will resume message output, if no input
occurs after a BREAK. This parameter is mandatory when Operation Mode is set
to "HALF_DUPLEX".
Value: <N> [0 | 60-3600] default value: 0 or 60 depending on the Operation Mode set.
60 ... 3600
If Operation Mode is set to "HALF_DUPLEX" the default value is 60 and the
increment is 60.
0
If Operation Mode is set to "FULL_DUPLEX". No change is possible in this
case.
Connect Timeout
Specifies the time (in seconds) after the switch stops trying to connect to a channel.
Value: <N> (0-3600) default value: 120.
1 ... 3600
Default value: 120.
0
The switch does not stop trying to set up a connection until a DISCONNECT
command will be entered.
Blocked Open Time
Time (in seconds) between two attempts of automatically re-opening a BLOCKED
channel.
Value: <N>(0-3600) in increments of 60. Default value: 60.
0
The channel may only be opened per operator command.
60 ... 3600
Time in seconds between two attempts of automatically re-opening a
BLOCKED channel
Max Auto Open Attempts
Number of attempts, which the system attempts to re-open automatically a
"BLOCKED" channel.

 Avitech GmbH 2018 Page 276 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The counter will be reset if a channel is opened per operator command or if the
channel stays "OPEN" more than 30 seconds.
Value: <N>(0-9999) default value: 0.
Note: The time between two attempts is specified with the parameters
Blocked open and Connect Timeout from the "Timer" menu.
Example:
 Blocked open parameter is set to 60
 Connect Timeout parameter is set to 120
 Ch. auto open parameter is set to 5
 The system will try to re-open the channel automatically 5 times
in a row with 180 seconds interval between each attempt
(Connect Timeout time+ Blocked open time).

9.5.4.7 The Barring tab

This tab defines how messages received by this circuit are handled regarding their
destination addresses.
Allow/Deny
This parameter defines if switching messages received by this circuit is generally
allowed or not.
Address
Routing indicator.
Exception
Defines if messages switched to destinations mapped to this routing indicator are
allowed or denied contrary to the general rule set with the Allow/Deny radio buttons or
to a rule set within another row of this list.
Example: in the screenshot above, all messages received by this circuit
will be switched by the system except for messages which destination
addresses are mapped to the routing indicators AVPS and AVPV.
However, messages which destination addresses are mapped to the
routing indicator AVPSE are allowed.

 Avitech GmbH 2018 Page 277 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.4.8 The Originator tab

This tab defines how messages received by this circuit are handled regarding their originator
addresses.
Allow/Deny
This parameter defines if receiving messages on this circuit is generally allowed or
not.
Originator
Routing indicator.
Exception
Defines if messages which originator is mapped to this routing indicator are allowed
or denied contrary to the general rule set with the Allow/Deny radio buttons or to a
rule set within another row of this list.
Example: in the screenshot above, all messages received by this circuit
will be denied by the system except for messages which originator is
mapped to the routing indicator AVP. Messages which originator is
mapped to the routing indicator AVPP are denied.

9.5.4.9 The Incoming Responsibility tab

 Avitech GmbH 2018 Page 278 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

This tab defines the responsibility for the relay of addresses in an incoming message. See
ICAO doc 8259 for more detailed information.
Allow/Deny
This parameter defines if relaying messages coming from this this circuit is generally
allowed or not.
Address
Routing indicator.
Exception
Defines if messages switched to destinations mapped to this routing indicator are
allowed or denied contrary to the general rule set with the Allow/Deny radio buttons or
to a rule set within another row of this list.

9.5.5 AFTN Address Route

All AFTN routes are listed in the AFTN Address Route tab. They define how routing
indicators are mapped to logical destinations.

 Avitech GmbH 2018 Page 279 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The Address Route unit is used to configure and modify the mapping of a routing indicator
to a logical destination.

9.5.5.1 Bulk Operations

the Bulk Operations function is specific to the AFTN address route tab.

It opens a sub-window which enables the operator to:


• Search for a specific AFTN address in a group address or a PDAI address.
• Delete an addresses from one or several group addresses or a PDAI addresses.
• Replace an addresses in one or several group addresses or a PDAI addresses.

 Avitech GmbH 2018 Page 280 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.5.2 Functions

Search
Searches for the address given within all group and/or PDAI addresses of the bundle
and displays the results in a table within the window..
Replace
Replaces the address within the selected group and/or PDAI addresses of the
bundle.
Delete
Deletes the address within the selected group and/or PDAI addresses of the bundle.
Cancel
Closes the Bulk Operations window.

9.5.5.3 Fields
Group
If this checkbox is ticked, the system will search or make the changes within all group
addresses
PDAI
If this checkbox is ticked, the system will search or make the changes within all PDAI
addresses
Delete Address
If this checkbox is ticked, the only possible actions are: Search, Delete and Cancel.
Address
The AFTN Address to be searched for.
Replacement
The replacement AFTN address.
Address Route
The group or the PDAI address in which the searched address has been found

 Avitech GmbH 2018 Page 281 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Type
The addressing type: Group or PDAI
Selection
If this checkbox is ticked, the system will execute the action on this address.

9.5.5.4 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
Routing Indicator
This field contains the routing indicator, a combination of up to 8 letters. If all 8 letters
are specified, the field defines an AFTN addressee indicator.
Value: <U>1...8 no default value.
Circuit
This field defines the standard circuit used for outgoing messages. This entry is
mandatory
Value: the values that can be found in the chooser. No default value.
Diversion Circuit
This field defines the standard diversion circuit. This entry is mandatory
Value: the values that can be found in the chooser. No default value.
Priorities
These fields define the standard circuits used according to the priority of the
message.
Copy To Circuit
This table allows the operator to define additional target(s).
Additional Addressing
This radio buttons and table show how the routing indicator is to be interpreted.
None
Normal target, no additional Addressing.
Group
Group Address. The elementary address will be transferred to the target.
The Member Address(es) table will be activated.
PDAI
Predetermined addressee indicator.
The Member Address(es) table will be activated.

 Avitech GmbH 2018 Page 282 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Member Address(es)
This field can be selected when the type is Group or PDAI.
It contains the distribution list for a routing indicator with 8 characters and type
Group or PDAI. Each address indicator must itself be an entry in the AFTN
Address Routing list and may also be a group or a predetermined addressee
indicator.
Value: <U>8 no default value.
Priority
The priority for which the message will be delivered to the member address.

9.5.6 Copy Addresses

All copy addresses are listed in the Copy Addresses tab.

The Copy Addresses unit is used to define messages to be copied to other circuits
according to their incoming or outgoing circuit, their message types and their priorities.

 Avitech GmbH 2018 Page 283 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.6.1 Fields
The fields of the upper part of this nit are described in section Common configuration and
routing fields of this chapter.
Circuit
The circuit, messages of which are to be copied.
Value: <U>(NIL | 1...16) no default value.
On Input
The direction of the message to be copied. If this checkbox is ticked the incoming
messages will be copied.
Priorities
The priorities of the messages to be copied.
Message Types
The type of the message to be copied.
Value: <U>(PLAIN | CHCK | SVC | SSACK | TST | CPL | FPL | CHG | CNL | DEP | DLA | ARR | RQP | RQS | SPL | ACK | ACKL
| REJ | MAN | SAM | SRM | SLC | SIP | FLS | DES | RRP | RRN | ERR | SMM | SPA | SRJ | FCM | RJT | RFI | SWM | REA | NTM |
SNO | BTM | ATM | AFP | EST | CDN | ACP | ALR | RCF | MTR | SPI | AMT | SMT | SNP | RQM)
no default value.
Addresses
The address(es), where the message is to be copied.

9.5.7 AFTN Device

All AFTN Devices are listed in the AFTN Devices tab.

 Avitech GmbH 2018 Page 284 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The Device unit is used to configure and modify the communication means of each AFTN
channel.
Note: Only one AFTN channel can be mapped to a device.

9.5.7.1 Functions
The functions of the AFTN Device are described in the section Common configuration and
routing functions of this chapter.

The File/New function opens a popup that gives the choice of the type of device to be
created.
Note: According to the configuration of the MCU the choice may be wider as the
entries displayed in the screenshot above.

9.5.7.2 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
Name
The name of the device.
Value: <A>1...50 no default value.
Circuit / Channel
Read-only field shows the name of Circuit/Channel where a device is in use.
The specific fields the various device types are described in the following sections:
• Transport Addresses
• Terminal Server Properties
• Fax Properties
• Dial In/Out Properties

 Avitech GmbH 2018 Page 285 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• FEC Properties
• X25 Properties
• SITA Properties

9.5.7.3 Transport Addresses

These properties are used to configure TCP/IP devices.


IP Address 1
Specifies an IP address (e.g. 192.168.64.7) or a hostname. This entry is
mandatory.
Value: <N>1...3 . <N>1...3 . <N>1...3 . <N>1...3 no default value.
TCP Port 1
In case of more than one addressable AFTN application on a computer, these
applications need to be differentiated. The computer is addressed via the IP address
parameter whereas the application is addressed via service. This field is
mandatory.
Value: <N>1...5 no default value.
IP Address 2
Specifies an IP address (e.g. 192.168.64.7) or a hostname. This entry is optional.
Value: <N>1...3 . <N>1...3 . <N>1...3 . <N>1...3 no default value.
TCP Port 2
In case of more than one addressable AFTN application on a computer, these
applications need to be differentiated. The computer is addressed via the IP address
parameter whereas the application is addressed via service. This field is optional.
Value: <N>1...5 no default value.

9.5.7.4 Terminal Server Properties

These properties are used to configure TAS devices.


IP Address 1
Specifies an IP address (e.g. 192.168.64.7) or a hostname. This entry is
mandatory.
Value: <N>1...3 . <N>1...3 . <N>1...3 . <N>1...3 no default value.

 Avitech GmbH 2018 Page 286 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Service Port 1
In case of more than one addressable AFTN application on a computer, these
applications need to be differentiated. The computer is addressed via the IP address
parameter whereas the application is addressed via service. This field is
mandatory.
Value: <N>1...5 no default value.
IP Address 2
Specifies an IP address (e.g. 192.168.64.7) or a hostname. This entry is optional.
Value: <N>1...3 . <N>1...3 . <N>1...3 . <N>1...3 no default value.
Service Port 2
In case of more than one addressable AFTN application on a computer, these
applications need to be differentiated. The computer is addressed via the IP address
parameter whereas the application is addressed via service. This field is optional.
Value: <N>1...5 no default value.

9.5.7.5 Fax Properties

These properties are used to configure FAX devices.


Fax Number
Number of the FAX connection.
Value: <N>0...16
Fax Server 1
Name of the first computer on which the fax software is installed.
Value: <U, N>0...12
Fax Server 2
Name of the second computer on which the fax software is installed.
Value: <U, N>0...12

9.5.7.6 Dial In/Out Properties

These properties are used to configure DIO devices.


Modem Command
This parameter is the modem configuration string (AT command). The value is
individual for each type of modem and has to be required from the technical staff.
Value: <U, N>0...20

 Avitech GmbH 2018 Page 287 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Phone Number
Defines the telephone number of the device.
Value: <N>0...15
Dialling Method
This parameter defines the method the system has to use to dial out. This value has
to be required from the technical staff.
Value: the values set in the drop down list. Default value: TONE.
TONE
The tone method will be used.
PULSE
The pulse method will be used.

9.5.7.7 FEC Properties

These properties are used to configure FEC devices.


Port Number
Defines the number of the port with which the device is connected to the host.
Value: <N>[0-191] no default value.
Parity
Parity bits. Bit that is added to ensure that the number of bits with the value one in a
set of bits is even or odd. Parity bits are used as the simplest form of error detecting
code.
Two variants of parity bits exist: even parity bit and odd parity bit. When using even
parity, the parity bit is set to 1 if the number of ones in a given set of bits (not
including the parity bit) is odd, making the entire set of bits (including the parity bit)
even. When using odd parity, the parity bit is set to 1 if the number of ones in a given
set of bits (not including the parity bit) is even, keeping the entire set of bits (including
the parity bit) odd.
Value: the values set in the drop down list. Default value: EVEN.
Break Before ASM
This parameter gives a choice whether a “transmit inhibit” shall be sent before an
ASM message or not. Depends on station type.
ASM: an ASM is sent by the AFTN switch to an inputting station, indicating that the
message just received is not acceptable, due to various format errors or garbled
information.

 Avitech GmbH 2018 Page 288 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Transmit inhibit (AFTN break signal): the AFTN network has the provision to inhibit or
interrupt a transmission from an inputting user station. The AFTN switch will invoke
this mechanism whenever it detects a message format violation or message garbling.
The “inhibit” is presented as a disabling of certain control signals on the modem to
DTE (RS-232-C) interface. Refer to Section 4 for full details. The computer may or
may not send an accompanying ASM. If there is no ASM received, the user system
shall retransmit the entire message on the next poll from the AFTN computer.
Poll Code
Network polling - The AFTN switch polls each station on a circuit, until a station
responds by transmitting a message.
Value: <U>1 no default value.
Example: In the polling sequence, the switch sends a Transmit Select Code (TSC)
sequence comprised of 3 characters as follows: ETX DLE C where C is a single
alpha character station identifier = poll code.
Select Code
Value: <U>1 no default value.
Stop Bits
In Asynchronous serial communication the stop bit is a "stop period". It can be 1, 1.5
or 2 bits long. It cannot be shorter than the specified time (1, 1.5 or 2 bits). This stop
bit keeps the transmitter and receiver synchronized.
Value: the values set in the drop down list. Default value: ONE.
Hardware Type
This parameter defines the way the terminal server hardware handshake lines act. It
should be set to MODEM in the current configuration. Eventually interesting for
directly connected stations.
Value: the values set in the drop down list. Default value: TERMINAL.
RX State
Enables / disables reception of AFTN messages from the inputting station.
Value: the values set in the drop down list. Default value: ENRX_ENABLED.

9.5.7.8 X25 Properties

These properties are used to configure X.25 devices.

 Avitech GmbH 2018 Page 289 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Channel Number
This parameter is needed for X.25 devices using SVC connections (switched virtual
circuits which are dialup connections). It is not used together with X.25 devices using
PVCs (permanent virtual circuit). The value must be unique within the X.25 gateway
(represented by the X.25 device lists).
If Type of conn has a value other than "PVC" this field is mandatory.
Value: <N>1...16 no default value.
D-Bit
This parameter is to determine whether each packet of X.25 level shall be
acknowledged by a receipt.
Link
This parameter is only valid for X.25 devices using PVC connections. There may be a
maximum of eight peers of link / log. channel. One peer is then mandatory whereas
the other seven peers are optional. Whether it is necessary to fill out both parameters
of such a peer depends on the parameter type of connection set in the list opened by
the [General]-button.
Defines the logical name of an X.25 interface port.
Value: <C>1...12 no default value.
Log Channel
The logical channel identifier related to the logical name of an X.25 interface port.
This parameter shall be decided together with the communication partner.
Value: <N>[1-4096] no default value.

9.5.7.9 SITA Properties

These properties are used to configure a SIT device.


IP Address 1
Specifies an IP address (e.g. 192.168.64.7) or a hostname. This entry is
mandatory.
Value: <N>1...3. <N>1...3 . <N>1...3. <N>1...3 no default value.
Service Port 1
In case of more than one addressable AFTN application on a computer, these
applications need to be differentiated. The computer is addressed via the IP address
parameter whereas the application is addressed via service. This field is
mandatory.
Value: <N>1...5 no default value.

 Avitech GmbH 2018 Page 290 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

IP Address 2
Specifies an IP address (e.g. 192.168.64.7) or a hostname. This entry is optional.
Value: <N>1...3. <N>1...3 . <N>1...3. <N>1...3 no default value.
Service Port 2
In case of more than one addressable AFTN application on a computer, these
applications need to be differentiated. The computer is addressed via the IP address
parameter whereas the application is addressed via service. This field is optional.
Value: <N>1...5 no default value.
BATAP IMA T1
IMA T1 input message acknowledgment timer. This parameter is only used if the
working method is set to BATAP.
BATAP WINDOW
Maximum number of unacknowledged messages allowed. This parameter is only
used if the working method is set to BATAP.
Coding
Specifies the format in which the message has to be coded
Value: <A>(ASCII 7 Bit | 5 bit ITA-2 | 8 bit EBCDIC)
ASCII 7 Bit
ASCII: American Standard Code for Information Interchange. This is a
character-encoding scheme which encodes 128 specified characters into 7-bit
binary integers.
5 bit ITA-2
International Telegraph Alphabet No. 2.: This is a character-encoding scheme
which was the basis for 5-bit teletypewriter codes.
8 bit EBCDIC
EBCDIC: Extended Binary Coded Decimal Interchange Code. This is an 8-bit
character encoding scheme mainly on IBM mainframe and IBM midrange
computer operating systems.
For more information about the Coding scheme, please refer to the SITA
document RFC 2351: Mapping of Airline Reservation, Ticketing, and
Messaging Traffic over IP of May 1998.
Protec
Identifies the end to end messaging responsibility transfer protocol used.
Value: <U>(BATAP)

 Avitech GmbH 2018 Page 291 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

BFlag
Sets the control of the length of the packet.
Value: <A>(do not use HLD).
do not use HLD
HLD: High Level Designator: Indicates the entry or exit point of a block in the
network.
The length of the packet is not controlled.

9.5.8 SITA-AFTN Mapping

All SITA-AFTN Mapping entries are listed in the SITA-AFTN Mapping tab of the Bundle
Details unit.

The SITA-AFTN Mapping unit is used to map SITA addresses to AFTN addresses and vice
versa.

 Avitech GmbH 2018 Page 292 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.8.1 Fields
The fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
AFTN Address
The mapped AFTN address.
Value: <U>(8) no default value.
SITA Address
The mapped SITA address.
Value: <U>(8) no default value.
Sense
The direction of the mapping.
Value: <U>(BIDIRECTIONAL | AFTN_TO_SITA | SITA TO AFTN) default value: BIDIRECTIONAL

9.5.9 AMHS Automated diversion

All AMHS Automated diversions are listed in the AMHS Automated diversion tab.

 Avitech GmbH 2018 Page 293 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.10 AMHS Management Domain Look-up

All AMHS Management Domain entries are listed in the AMHS Management Domain tab.

 Avitech GmbH 2018 Page 294 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The AMHS Management Domain mask is used to map AFTN nationality Letters consisting
usually of 2 or designators made up of 1, 3, 4 or 6 letters to AMHS global domain identifiers
(GDI), the address mapping scheme implemented in the AMHS Management Domain
Register designated by the GDI.

9.5.10.1 Fields
Scheme Type
Addressing scheme adopted by the considered MD, it is unique for all entries with the
same GDI.
Value: the values set in the drop down list. Default value: XF.
Country
Country name attribute within the GDI.
Value: <U>2 default value: XX.
ADMD
Administration management domain name attribute within the GDI.
Value: <U>1...16 default value: ICAO.
PRMD
Private management domain name attribute within the GDI, to take the ICAO globally
unique value adopted by the considered MD.
Value: <U>1...16 no default value.
Nationality Letter
The ICAO Nationality designator
Value: <U>2...4 no default value.
Name
The name of the state, territory or organisation identified by routing indicator.
Value: <C>NIL | 1...80 no default value.
Naming Context
Supplementary information necessary for the classification in the AMHS directory.
Value: (c | C)=<U><2> or (o | O)=<C><1...62> no default value..

 Avitech GmbH 2018 Page 295 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.11 AMHS CAAS Look-up

All CAAS entries are listed in the AMHS CAAS tab.

The AMHS CAAS Look-up mask is used to determine which organisation belongs to which
organisation unit in domains with the CAAS addressing scheme.

9.5.11.1 Fields
Country
Country name attribute within the GDI.
Value: <U>2 default value: XX.
ADMD
Administration management domain name attribute within the GDI.
Value: <U>1...16 default value: ICAO.
PRMD
Private management domain name attribute within the GDI, to take the ICAO globally
unique value adopted by the considered MD.
Value: <U>1...16 no default value.

 Avitech GmbH 2018 Page 296 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Organisation
The name of the organisation of this country, state or territory.
Value: <A>2...64 no default value.
Organisation Unit
The organization-defined unit.
Value: <U>2...4 no default value.

9.5.12 AMHS Miscellaneous

All AMHS Miscellaneous properties are listed in the AMHS Miscellaneous tab.

The AMHS Miscellaneous mask allows defining further parameters depending on the GDI
(country, ADMD, PRMD) of a MD and optionally on values of organisations within an AMHS
MD. The following two parameters can be assigned to a GDI or a combination (GDI,
organisation):
• Address Mapping Type.
• Maximum Message Life Time.

 Avitech GmbH 2018 Page 297 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

According to the document PDR M4100002 "AFTN/AMHS Address Conversion" a


conversion of an MF-address into an AF-address can only be regarded to be successful if
the reverse conversion of the AF-address delivers the considered MF-address. Otherwise
the result of the address translation is invalid. However in very special cases within a MD
operational requirements to deviate from this strict ICAO rule may exist. Whether or not the
conversion may deviate from the rules imposed by the document PDR M4100002
"AFTN/AMHS Address Conversion" depends on the GDI or the combination (GDI,
organisation) of a MF-address to be converted into an AF-address.
The message transfer envelope of an X.400 message includes the attribute latest delivery
time. If this attribute is set, a message not yet delivered at this time will be rejected by means
of a non-delivery report. ICAO Doc 9705 SV III 2nd edition does not specify the use of latest
delivery time in AMHS however it is not excluded either. If maximum message life time has a
value other than 0 the MTCU will calculate the latest delivery time as the current time plus
maximum message life time (minutes). If necessary the MTCU has to split an outgoing
AMHS message so that each partial message has a different latest delivery time.

9.5.12.1 Fields
Country
Country name attribute within the GDI.
Value: <U>2 default value: XX.
ADMD
Administration management domain name attribute within the GDI.
Value: <U>1...16 default value: ICAO.
PRMD
Private management domain name attribute within the GDI, to take the ICAO globally
unique value adopted by the considered MD.
Value: <U>1...16 no default value.
Organisation
The name of the organisation.
Address Mapping Type
Value: the values set in the drop down list. No default value.
SYMETRIC
Symmetric or standard. ICAO rules following ICAO Doc 9705 SV III 2nd
edition and document PDR M4100002 "AFTN/AMHS Address Conversion" are
applied.
ASYMETRIC
Asymmetric. It will not be checked whether an AFTN address resulting from
conversion of an AMHS address could be re converted into the considered
AMHS address.

 Avitech GmbH 2018 Page 298 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Max Message Lifetime


Maximum Message Life Time.
Value: <N>[0...∞] no default value.
0
No latest delivery time will be determined.
1...∞
The time in minutes which the MTCU will add to the current time in order to
determine the latest delivery time.

9.5.13 AMHS User Addresses

All AMHS User Addresses are listed in the AMHS User Address tab.
The AMHS User Address Look-Up tab allows a free assignment of any X.400 O/R address to
a fully qualified (i.e. exactly 8 letter) AFTN address regardless which addressing scheme is
adopted by the AMHS management domain which the address belongs to. In this way
addressing schemes other than XF or CAAS can be defined. Furthermore, exceptions from
XF or CAAS addressing scheme adopted by a MD can be defined. Note that the GDI
attribute values (country, ADMD, PRMD) occurring in the AMHS user address look-up list
may be absent in the AMHS MD look-up list.

 Avitech GmbH 2018 Page 299 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The AMHS User Address Look-Up unit is used to configure and modify the mapping of
X.400 O/R address to an AFTN address.

9.5.13.1 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
AFTN Address
AFTN address, consisting of exactly 8 letters.
Value: <U>8 no default value.
Country
Country name attribute within the GDI.
Value: <U>2 default value: XX.
ADMD
Administration management domain name attribute within the GDI.
Value: <U>NIL | 1...16 default value: ICAO.
PRMD
Private management domain name attribute within the GDI, to take the ICAO globally
unique value adopted by the considered MD.
Value: <U>NIL | 1...16 no default value.
The fields of the various tabs are described in the following sections:
• The Advanced Properties tab
• The Domain Defined Attributes tab
• The Personal Details tab

 Avitech GmbH 2018 Page 300 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.13.2 The Advanced Properties tab

Organisation
The values of organisations are assigned by the MD which they belong to. Often the
location indicator of a particular location within a geographical region or another
organisation is used. Other values are also applied.
Value: <U>1...64 no default value.
Organisation-Defined Unit 1 - 4
The organization-defined unit part of the X.400 originator/recipient (O/R) name.
These attributes are the "lower" attributes of an X.400 O/R address
Syntax and Semantics of lower attributes are as specified by the X.400 standards
family. The characters allowed are printable strings from the ASN.1. Lower case
characters will be automatically transformed to upper case characters.
It is ensured that the mapping of AFTN addresses to X.400 O/R addresses is
injective. This means that no two different AFTN addresses may be mapped to the
same set of X.400 O/R address attributes. Otherwise an error message is displayed
when an attempt to save the AMHS user address look-up list is undertaken.

9.5.13.3 The Domain Defined Attributes tab

This tab shows "lower" attributes of an X.400 O/R address


Syntax and Semantics of the lower attributes are as specified by the X.400 standards family.
The characters allowed are printable strings from the ASN.1. Lower case characters will be
automatically transformed to upper case characters.
It is ensured that the mapping of AFTN addresses to X.400 O/R addresses is injective. This
means that no two different AFTN addresses may be mapped to the same set of X.400 O/R
address attributes. Otherwise an error message is displayed when an attempt to save the
AMHS user address look-up list is undertaken.

 Avitech GmbH 2018 Page 301 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Type 1 - 4
The type of a domain-defined attribute for this object. The domain-defined attribute is
not defined by X.400 standards but is allowed in the X.400 originator/recipient (O/R)
name to accommodate values of existing systems sending messages.
Value 1 - 4
The code immediately following the attribute type that specifies a particular property
from the set defined by the attribute type.

9.5.13.4 The Personal Details tab

This tab shows "lower" attributes of an X.400 O/R address


Syntax and Semantics of the lower attributes are as specified by the X.400 standards family.
The characters allowed are printable strings from the ASN.1. Lower case characters will be
automatically transformed to upper case characters.
It is ensured that the mapping of AFTN addresses to X.400 O/R addresses is injective. This
means that no two different AFTN addresses may be mapped to the same set of X.400 O/R
address attributes. Otherwise an error message is displayed when an attempt to save the
AMHS user address look-up list is undertaken.
Common Name
The user common name, or given name, part of the X.400 originator/recipient (O/R)
name.
Surname
The user last name, or surname, part of the X.400 originator/recipient (O/R) name.
Given Name
The user first name, or given name, part of the X.400 originator/recipient (O/R) name.
Generation Qualifier
The generation qualifier part of the X.400 originator/recipient (O/R) name
Initials
The first and middle initials of the X.400 originator/recipient (O/R) name

 Avitech GmbH 2018 Page 302 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.14 CIDIN Entry/Exit Centre

All CIDIN Entry/Exit Centres which the operator or the system can communicate with are
listed in the CIDIN Entry/Exit Centre tab.

The CIDIN Entry/Exit Centre unit is used to define and modify CIDIN Exit/Entry centres.

9.5.14.1 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
Entry/Exit address
The local Entry / Exit address.
Value: <U>5...8 no default value.
TMR
Timer for message acknowledgment.
Value: <N>[11-3600] default value: 40.
Unit: second

 Avitech GmbH 2018 Page 303 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Long Term Enquiry Timer


Interval for regular transmission of ENQ.
Value: <N>[0 | 10-1440] default value: 40.
Unit: minute
Max Text Length
Maximum Text Length.
Value: <N>[1800-20480] default value: 1800.
Window
Maximum number of not acknowledged messages sent at the same time.
Value: <N>[1-99] default value: 5.
TNMA
Timer for the final packet at received messages.
Value: <N>[10-3599] default value: 30. TNMA value shall always be less than TMR
value .
Unit: second
TEM
Timer between sent two enquiries.
Value: <N>[10-3600] default value: 40.
Unit: second
Reset- / Thresholds
Threshold definition.
1.
Left field value: <N>[1-9994] default value: 50
Right field value: <N>[2-9995] default value: 100
2.
Left field value: <N>[3-9996] default value: 150
Right field value: <N>[4-9997] default value: 200
3.
Left field value: <N>[5-9998] default value: 250
Right field value: <N>[6-9999] default value: 300
Note: The following rule shall always apply: Reset Threshold1 <
Threshold1 < Reset Threshold2 < Threshold2 < Reset
Threshold3 < Threshold3.

 Avitech GmbH 2018 Page 304 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.15 CIDIN ADAX

All CIDIN ADAX are listed in the CIDIN ADAX tab.

The CIDIN ADAX unit is used to configure and modify the mapping of an AFTN destination
address to a CIDIN Exit address. In this unit alternate Exit addresses can also be mapped to
AFTN destination addresses.

9.5.15.1 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
AFTN destination
The routing indicator for an AFTN destination address mapped to CIDIN.
Value: <U>1...8.
Primary Exit Centre
Default Exit centre. This field is a drop down list which displays the entries of the
CIDIN Exit centre list.

 Avitech GmbH 2018 Page 305 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Alternate Exit centre 1


First alternate Exit centre used in case of unavailability of the default Exit centre. This
parameter is optional. In this field a list of values displays the available entries of
CIDIN Exit centres when the [F4]-key is pressed.
Alternate Exit centre 2
Second alternate Exit centre used in case of unavailability of the default Exit centre
and of the first alternate exit centre. This parameter is optional. In this field a list of
values displays the available entries of CIDIN Exit centre when the [F4]-key is
pressed.
Maximum Text Length
Maximum text length
Value: <N>[1800-20480] default value: 1800.

9.5.16 CIDIN Routing

All CIDIN Routing are listed in the CIDIN Routing tab. This tab contains all the information
needed by CIDIN to route outgoing messages. It is the assignment of the AX routing
indicators to the virtual circuit groups. The local addresses in the single application have also
been defined here. By local addresses the according MCF shall be put, however no
connection paths shall be entered.

The CIDIN Routing unit is used to assign the AX routing indicators to the virtual circuit
groups.

 Avitech GmbH 2018 Page 306 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.16.1 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
CIDIN Exit Address
Routing indicator for CIDIN Exit / Entry address
Value: <U>1..8 no default value.
Message Code And Format
If the MCF checkbox is ticked the Message Code And Format drop down list will be
activated. The Connect Path and the Alternate Connect Path will then be deactivated.
Value: <U>[NIL | AFTN | SIM-AFTN] no default value.
AFTN
AFTN exit/entry address.
SIM-AFTN
This exit centre will be simulated by this system.
Connect Path
This field is a drop down list which displays the entries of the CIDIN virtual Circuits
list. It can only be filled in if no Message Code And Format has been defined.
Value: <U>NIL | 4 no default value.
Alternate Connect Path
This entry is automatically used in case of unavailability of the main connection path.
This field is a drop down list which displays the entries of the CIDIN virtual Circuits
list. It can only be filled in if no Message Code And Format has been defined.
Value: <U>NIL | 4 no default value.

9.5.17 CIDIN Virtual Circuit Group

The CIDIN Virtual Circuit Group tab lists all CIDIN virtual circuit groups used.

 Avitech GmbH 2018 Page 307 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The CIDIN Virtual Circuit Group unit is used to configure the physical characteristics of all
CIDIN virtual circuit groups used.

9.5.17.1 Fields
Most fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
Group
A collection of all the direct CIDIN channels between two locations.
Value: <U>4 no default value.
CIDIN virtual Circuit Number List
Defines the name and the characteristics of the CIDIN virtual circuits belonging to the
CIDIN virtual circuit group. A virtual circuit is identified by A single communications
channel between two locations.
Clicking on the [New]- icon opens an empty CIDIN virtual circuit window to create a
new virtual circuit. A double click on the name of an existing virtual circuit opens the
virtual circuit properties in the CIDIN virtual circuit window.
Note: Changes made for a virtual circuit have to be saved by clicking on
the [Save]-button of the CIDIN Virtual Circuit Group unit.
Value: <U, N>1...16 No default value.

 Avitech GmbH 2018 Page 308 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.17.2 CIDIN Virtual Circuit

The CIDIN Virtual Circuit window is used to configure the physical characteristics of all
Permanent Virtual Circuits (PVC) and Switched Virtual Circuit (SVC) used in a Virtual circuit
group.
The CIDIN Virtual Circuit window can only be open via the CIDIN Virtual Circuit Group unit. It
is used to configure the virtual circuit belonging to a specific virtual circuit group.
Note: To save a CIDIN virtual circuit, the operator has to click on the [Save]-
button of the CIDIN Virtual Circuit Group unit.

 Avitech GmbH 2018 Page 309 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Clicking on the [OK]-button enters the newly created or modified CIDIN virtual circuit in the
CIDIN virtual circuit number list table of the CIDIN Virtual Circuit Group unit bud does NOT
save these changes.
Note: All changes made in a virtual circuit have to be saved by clicking on the
[Save]-button of the CIDIN Virtual Circuit Group unit.

9.5.17.2.1 Fields
Number
A single communications channel between two locations.
Value for PVC's: <N>[1-8] no default value.
Value for SVC's: <N>[9] no default value.
Initialisation State
Initial state if the CIDIN process starts. The state can be overruled by the
"OP_/CL_VC" command.
Value: <U>[OPEN | CLOSED] default value: OPEN
Physical Property
This parameter describes the X.25 programmatic access name, defined in the X.25
port configuration file (e.g. /etc/x25/x25config_0p1 -> field 'name' or check the
programmatic access name via system administration manager (sam).
Value: <U, N>1...8 no default value.
Example: X25WAN1 => programmatic access name.
Logical Channel Number
The number of the permanent virtual circuit. The maximum value depends on the
X.25 application installed on the system and can differ from the value given below.
Value: <N>[0-4094] no default value.
Switched Domain Network Address
The X.121 call number of the local network address. This field can only be filled out
when the field Logical Channel Number is empty.
Value: <N>1...15 no default value.
Connection Delay
Delay between connect attempts. In case of value=0, the process tries only once to
open the PVC. If this is not successful the operator has to open the PVC via
command. If the value >0, the process tries after n sec to reopen the PVC by itself.
Value: <N>[0-3600] default value: 0.
Unit: second
Idle Timer
When the idle timer elapses the VC is disconnected by sending a clear request to the
network with the clearing cause set to '00'. '0' leads to not clearing the SVC (infinite
timer).
Value: <N>[0-3600] default value: 0.
Unit: second

 Avitech GmbH 2018 Page 310 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Call Retry Timer


This timer is triggered when a call request is sent and stopped when a call connected
is received. In case the timer expires the VC will be closed and the VC state will be
set to DISCONNECTED.
Value: <N>[0-3600] default value: 0.
Unit: second
Reset-/Thresholds
These fields define the threshold and reset threshold values for the virtual circuit.
1.
Left field value: <N>[1-9994] default value: 5
Right field value: <N>[2-9995] default value: 10
2.
Left field value: <N>[3-9996] default value: 20
Right field value: <N>[4-9997] default value: 50
3.
Left field value: <N>[5-9998] default value: 100
Right field value: <N>[6-9999] default value: 200
Cause/Diagnostic codes
In this table the operator can set manually causes and diagnostics to the state
connect or disconnect.

9.5.18 AMHS User Agent

All AMHS user agents are listed in the AMHS User Agent tab of the Bundle Details unit.

 Avitech GmbH 2018 Page 311 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The AMHS User Agent unit is used create and modify AMHS user agents.

9.5.18.1 Fields
The fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
AFTN Address
The address of the user agent in AFTN format.
Value: <U>(8) no default value.
Password
The password that has to be used.
Value: <C>(1...20) no default value.
Session Type
the session type to be used.
Value: <A>(P3 | P7) default value: P3
Max Content Length (bytes)
The maximum deliverable content length in bytes.

 Avitech GmbH 2018 Page 312 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.19 MTA Circuit

All MTA circuits are listed in the MTA Circuit tab of the Bundle Details unit.

Clicking on the "Insert Row" button opens a window in which the operator shall fist enter the
MTA location identifier.

The MTA Circuit unit is used create and modify MTA circuit.

 Avitech GmbH 2018 Page 313 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

9.5.19.1 Fields
The fields of the upper part of this unit are described in section Common configuration and
routing fields of this chapter.
Name
Symbolic name of the MTA circuit
Value: <A>(1...16) no default value.
Presentation Address
The presentation address the neighboured MTA has to use when connecting to us.
Value: <A>(1...50) no default value.
Their MTA Name
The name that will be used by the neighboured MTA when initiating a connection or
as answer when our MTA initiates a connection to the neighboured MTA.
Value: <A>(1...32) no default value.
Their MTA Password
The password that will be used by the neighboured MTA when initiating a connection
or as answer when our MTA initiates a connection to the neighboured MTA.
Value: <A>(1...50) no default value.
Our MTA Name
The name that will be used by our MTA when initiating a connection or as answer
when the neighboured MTA initiates a connection to our MTA.
Value: <A>(1...32) no default value.
Our MTA Password
The password that will be used by our MTA when initiating a connection or as answer
when the neighboured MTA initiates a connection to our MTA.
Value: <A>(1...50) no default value.
Is diverted circuit (temporarily disabled)
If this checkbox is ticked the remote MTA of the circuit is temporarily disabled.
RTS Transfer Timeout (seconds/megabyte)
The specific timeout value for data transfer per megabyte.
Value: <N>(0...99999) no default value.
Idle Time (seconds)
The time in seconds before a connection is closed when idle.
Value: <N>(0...99999) no default value.
Max Incoming Connections
The maximum number of accepted incoming connections.
Value: <N>(0...999) no default value.

 Avitech GmbH 2018 Page 314 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Max Outgoing Connections


The maximum number of accepted outgoing connections.
Value: <N>(0...999) no default value.
Associations
Minimum Priority
The minimal MTS priority.
Note: no value means that there is no restriction.
Permanent
Flag determining whether or not an association is considered permanent by
the MTA.
EITs Whitelist
Lists the EIT (encoded information types) allowed.

 Avitech GmbH 2018 Page 315 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10 MANAGEMENT MENU

10.1 The Traffic Monitor function

The Traffic Monitor unit serves to monitor the traffic on selected channels. It can contain
several monitors. Each monitor is divided in two parts:
• the upper table
• the lower part

10.1.1 The upper table

This table shows all messages coming from and sent to the switch on the selected channel.
Messages received by the switch have a white background, messages sent by the switch
have a grey background.

 Avitech GmbH 2018 Page 316 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

It is possible to sort this table according to one column by clicking on the column name. It is
also possible to change the order of the columns by selecting a column name and moving it
to the right or to the left.
If the operator clicks on a line in the upper table it will be highlighted, the message will be
displayed in the lower part and the focus of the table will stay on that line. To unselect the
line the operator shall press the [SHIFT]-key and click on the highlighted line.
According to the option selected in the "Compose command" window, the columns
displayed are different.
Direction
The direction of the message from the point of view of the switch.
• In: message received by the switch.
• Out: message sent by the switch
MTP ID
MTP Identifier
CSN
Channel sequence number of the message
DTG
Day / Time group of the message
Priority
ATS Priority indicator of the message
1. Address
Firs addressee indicator of the message
Filing Time
Filing Time of the message
Originator
Originator indicator of the message
OHI
Optional heading line
Text
Beginning of the text
Raw Data
Message displayed as it is received. This column is only available if the Raw format
monitoring checkbox has been ticked.

 Avitech GmbH 2018 Page 317 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.1.2 Lower part

This part displays the message selected in the upper table.

10.1.3 Traffic Monitor functions

10.1.3.1 File

Compose Command
Opens the Compose a command window of the Traffic Monitor to start or stop a
command in the selected monitor

If no monitor has been selected the system will display an error message.
Clear
Clears the list of the selected monitor
New Monitor Window
Opens a new monitor
Open Configuration
Opens the Configuration window of the Traffic Monitor
Close
Closes the traffic monitor.

10.1.3.2 Options

Show Toolbar

 Avitech GmbH 2018 Page 318 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Hides or displays the toolbar.

10.1.4 The Compose a command window of the Traffic Monitor

This window serves to configure the channel to monitor.

10.1.4.1 Fields
Subnet
The subnet of the channel
Circuit
The name of the circuit
Channel
The name of the channel
Raw format monitoring
Sets the monitoring in raw format or in interpreted format. In the raw format the
system will display the message as it has been received. The formatting of the
message will also be displayed. If the raw format has not been selected the system
will interpret the message and display only the printable characters.

10.1.4.2 Command buttons


Start
Starts the monitoring of the selected channel.
Stop
Stops the monitoring of the selected channel.
Cancel
Cancels the monitoring command.

10.1.4.3 Note
In case of monitoring CIDIN traffic, the dialog will be adapted to match CIDIN specific
boundary conditions.

10.1.5 The Configuration window of the Traffic Monitor

This window serves to configure the connection between the traffic monitor and the server.

 Avitech GmbH 2018 Page 319 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.1.5.1 Fields
Hostname
The name of the server to which the traffic monitor shall be connected.
Port
The port number on the server.

10.1.5.2 Command buttons


OK
Sends the connection command.
Cancel
cancels the connection command.

10.2 The Message Retrieval

 Avitech GmbH 2018 Page 320 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The message retrieval is used for the display of AMHS and AFTN messages processed by
the switch for the purposes of legal recording.
Note: The message retrieval is synchronised with the legal recording and can only
display the records also available in the legal recording. When an export is made in
the legal recording, the exported records are no longer available in the message
retrieval.
It is divided in three parts:
• The retrieval tree
• The search criteria tab
• The result tab

10.2.1 The retrieval tree


This is the left part of the message retrieval. It displays a folder with the retrieval results as
well as one folder per saved search criteria. Selecting a search criteria folder and clicking on
the [Execute Search]-button starts the search for the selected criteria and the result tab
takes the name of the selected search folder.

10.2.2 The Message Retrieval functions

10.2.2.1 File

New
Clears the fields.
Delete the Search Constraints
Deletes the current search constraints.
Save the current Search Constraints
Saves the current search constraints.
Close
Closes the message retrieval.

10.2.2.2 Options

Show Toolbar
Hides or displays the toolbar.

 Avitech GmbH 2018 Page 321 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Show related Messages


If the checkbox is ticked displays the related messages in the search results.
Merge related Messages
If the checkbox is ticked merges the related messages in the search results.

10.2.3 The search criteria tab

This tab displays the results of the search.


Title
Name of the search criteria.
Max. Msgs.
Maximum number of messages to be displayed.

 Avitech GmbH 2018 Page 322 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

General
Creation Time
Searches for messages with this creation time. The drop down contains the
following selection possibilities:
• "empty"
• this year
• last year
• this month
• last month
• today
• yesterday
• this hour
• last hour
If none of the drop down possibility is applicable the creation period can be set
by ticking the checkbox and entering the "from" and "to" date and time
manually.
ATS Priority
The search will be processed within messages of the selected ATS
priority(ies). It is possible to select several priorities at a time. If no priority is
selected this parameter will not be taken into account for the search.
Note: It is only possible to select priority(ies) if the message type
selected is "Messages". If more message types are selected it is
not possible to change the priorities in which the search will be
done.
Filing time
Searches for messages with this filing time. The drop down contains the
following selection possibilities:
• "empty"
• today
• yesterday
• this hour
• last hour
If none of the drop down possibility is applicable the filing time period can be
set by ticking the checkbox and entering the "from" and "to" filing time
manually.
Msg. ID
The search will be processed within messages with the message identifier
entered in this field.

 Avitech GmbH 2018 Page 323 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Originator
Searches for messages with this originator address.
Recipient
Searches for messages with this address as one to the recipients.
External Mag. ID
Searches for messages with this external message identifier.
Source Circuit
Searches for messages coming from this circuit.
Target Circuit
Searches for messages sent to this circuit.
Message Type
Searches for messages with this type of the message. The drop down
contains message types such as PLAIN, FPL, NTM, SIP...
OHI
Searches for messages with this optional heading information.
Body text
Searches for messages with this text of the message.
AMHS Specifics
These parameters are only valid for AMHS messages. If the search only concerns
AFTN messages these parameters shall not be filled out.
X.400 Priority
Searches for AMHS messages with the selected transfer priority(ies).
Original encoded Information Types
Searches for AMHS messages with these original encoded information types.
Originator Report Request
The details set in the originator report request of the message. The drop down
contains the following selection possibilities:
• "empty"
• Never
• Only if delivery fails
• Always
IPM
IPM Identifier
Searches for AMHS messages with this IPM identifier
Recipient
Searches for AMHS messages with this IPM recipient

 Avitech GmbH 2018 Page 324 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Recipient Type
Searches for AMHS messages with this type of IPM recipient.
IPN
Recipient Time
Searches for AMHS messages with this recipient time. The drop down
contains the following selection possibilities:
• "empty"
• this year
• last year
• this month
• last month
• today
• yesterday
• this hour
• last hour
If none of the drop down possibility is applicable the period of the recipient
time can be set by ticking the checkbox and entering the "from" and "to" date
and time manually.
Subject IPM Identifier
Searches for AMHS messages with this subject IPM identifier.
Report
Reason Code
Searches for AMHS reports with this reason code
Diagnostic Code
Searches for AMHS reports with this diagnostic code

 Avitech GmbH 2018 Page 325 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.2.4 The result tab

This tab displays the results of the search.


The upper table

The table displays the results of the search


Originator
The address of the originator of the message.
Priority
The priority of the message.

 Avitech GmbH 2018 Page 326 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Recipients
The addresses of the recipients of the message.
Channel Name
The name of the channel from which the message came.
Creation time
The date and time of the creation of the message.
Filing time
The filing time of the message.
Message Body
The body text of the message.
The timeline of the message

This graphic shows the life-cycle related events for the selected message in
conjunction with all the relevant information for each phase.
The timestamp for the start and the end of the timeline matches the first and last
event for the selected message and is displayed in the column of the source circuit.
The life-cycle view positions the rest of the events in the timeline, being the position
of each event proportional to its timestamp. In case of a collision (this is, two events
overlapping), the view rearranges the events so that all of them are visible (if this is
possible). In the case that an event has to be moved from its natural (proportional)
position, its timestamp is presented in red colour.

 Avitech GmbH 2018 Page 327 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The events are distributed horizontally into queues, selecting the source one for the
Input events (and therefore the Delete events) and the target for the rest of them. In
case of not being able to determine in which queue a message should be placed, a
special queue (named "Queue") is used.
The life-cycle view represents each kind of event in a different colour. When a life-
cycle event is mouse clicked, the information related to that event is presented in the
message preview part.
The Message Preview part

This part displays the selected message or the selected life-cycle event.
Note: If the message is generated by the error handler (e.g. SVC
messages) the source circuit and the source device type is "ERR".
The Message information part

This part displays some information about the selected message, in any available.

 Avitech GmbH 2018 Page 328 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.3 The Archive unit

System messages and commands can be retrieved by using this functionality.


Note: The Archive functionality is synchronised with the legal recording and can
only display the records also available in the legal recording. When an export is
made in the legal recording, the exported records are no longer available in the
Archive.

10.3.1 Functions

10.3.1.1 File

New
Clears the table and the preview and resets the search filter fields.
Search
Executes the search with the given From and To and displays the list of records in the
table.

 Avitech GmbH 2018 Page 329 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Close
Closes the archive functionality.

10.3.1.2 Options

Show Toolbar
Hides or displays the toolbar.

10.3.2 Fields

10.3.3 Upper Part - The Search filter

From
The date and time of the beginning of the period to search in. The pre-set is 24 hours
ago.
To
The date and time of the end of the period to search in. The pre-set is now.
Hits
The number of records found.

10.3.4 Middle Part - The Result table

Time
The generation time of the record.
Name
The name of the record.
Type
The type of the record.
Application
The application related to the record if it is a system event.
Summary
A summary of the content of the record.

 Avitech GmbH 2018 Page 330 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.3.5 Lower part - The Record preview

This part of the archive functionality displays a preview of the record selected in the result
table.

10.4 The Channel Maintenance function

This unit allows the administrator to monitor all existing channels and to delete messages
from these channels.
The Channel Maintenance is composed of three parts:
• The channel tree
• The message table
• The message preview

10.4.1 The channel tree


This is the left part of the Channel Maintenance. It displays all existing channels and nodes in
a tree. Each channel node can be expanded so as to see the message folders as in the
message office.
This tree also contains a search node in which it is possible to store search criteria. For more
information about the search function please refer to the section The search function of this
chapter.

 Avitech GmbH 2018 Page 331 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.2 The message table


Selecting a message folder in the channel tree will display the contents of that folder in the
message table. The items in this pane can be ordered by any of the column headers simply
by clicking on that header with the mouse.
The columns in this table are the following:
Info
Information symbols concerning the message:
• Reply to
• Reply All
• Forward
• Attachment
ID
Internal identifier of the message.
Type
Message Type such as PLAIN, FPL, DEP, NT, SW...
APrio
AFTN Priority.
Created
Date and time when the message was created.
Status
Status of the message. A message can have the following status:
X - Unsent
The message has not yet been transmitted. This status exist in the short
period of time between the moment the operator has clicked on the [Send]-
button and the moment the message has been totally processed by the
system.
P - Processed
The received message has been processed.
U - Unprocessed
The received message is still unprocessed.
O - Transmitted
The message has been transmitted successfully.
Changed on
Date when the message was changed.

 Avitech GmbH 2018 Page 332 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Changed by
Name of the operator who changed the message.
To
Address of the first recipient.
From
Address of the originator.
TPrio
AMHS priority.
Subject
Subject of the message if any.
Delivery
Date when the message was delivered.
Imp
Text of the message.

10.4.3 The message preview


This part of the Chanel Configuration displays the message that has been selected in the
message table.

10.4.4 The search function

 Avitech GmbH 2018 Page 333 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Selecting the function Search Messages in the File menu or making a double click on the
Search Result node opens the Search unit. This function allows the operator to search for
messages according to chosen criteria.
Note: If no criteria has been selected the search will be done over all messages. In
order for the search engine to work at its best capacity it is advised to select
nothing if the search has to be done over all possibilities of a criteria type.
Example: If the search has to be done in all messages of the Unprocessed node,
the Processed node and the Transmitted node, not selecting anything has the
same meaning in the search function than selecting each node but the search will
be slightly quicker.

10.4.4.1 Functions

10.4.4.1.1 File

New
Resets all the fields.
Search Messages
Starts the search according to the parameters set.
Next Search
Continues the search if more than 100 messages have been found.
Save Search Constraints
Saves the current search parameters as folder in the Search node.
Close
Closes the search unit.

10.4.4.1.2 Options

Show Toolbar
Displays or hides the toolbar.

 Avitech GmbH 2018 Page 334 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.2 Special Features


Wild cards
The operator can use the "%" character as a wild card in any text input field.
Examples:
 Body text: %YX ---- The system will search for all messages
with the Body text ending with YX.
 Body text body: ETCC% ---- The system will search for all
messages with the Body text beginning with ETCC.
 Body text: %AFL% ---- The system will search for all messages
containing the string AFL in the Body text.
 Body text: %TEST%252% ---- The system will search for all
messages containing the string TEST and the string 252 in the
body text.
Selection lists
To select a block of successive entries in a selection list, the operator shall click on
the first entry to be selected, press the [Shift]-key and click on the last entry to be
selected.
To select entries that are not in a block the operator shall click on the first entry to be
selected, press the [Ctrl]-key, click on the next entry to be selected, keep the [Ctrl]-
key pressed, click on the next entry to be selected, and so on until the last entry. If
nothing has been selected, the search will occur in all possible entries of the selection
list.
To deselect an entry in a list the operator shall press the [Ctrl]-key and click on the
entry to be deselected.
3 state checkbox
This special checkbox can have 3 different states:
• Plain - ignore: the criteria will be ignored during the search
• Not ticked - false: the search will be made for messages which do not
contain this criteria
• Ticked - true: the search will be made for messages which contain this
criteria

 Avitech GmbH 2018 Page 335 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.3 Message Type

The search will be processed within the messages of the selected type and query. If no
message type has been selected the search will be processed within all message types.
It is possible to sort each column in ascending or descending order.

10.4.4.3.1 Columns
Use
A tick in the corresponding checkbox marks the message types to be used for the
search. If the checkbox is not ticked the message type will be excluded from the
search.
Icon
Displays the icon of the different message types.
Group
Displays the group to which the different message types belong.
Type
Displays the name of the different message types.
Query
Opens a new window for input of additional search criteria concerning this message
type.

 Avitech GmbH 2018 Page 336 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.3.2 Query

Clicking on the button in this column opens a new window for input of additional search
criteria. The fields contained in this window depend from the message type. The screenshot
above shows the query window for FPL.
If parameters have already been defined, clicking on the query button opens the window with
the existing parameters. These can be modified and accepted by clicking on the [OK]-button.
Note: In a Query form all fields are connected with "AND". This means that the
search function will search for messages containing all parameters set here.
Messages missing one or more parameters set will not be take into account.
New
Clears all fields.
OK
Closes the window and displays a magnifying glass icon on the corresponding query
button, to show the operator some additional parameters have been entered.
Cancel
Closes the window without taking the changes into account.

 Avitech GmbH 2018 Page 337 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.4 The AMHS tab

This tab allows the operator to set search criteria for AMHS Messages. To be able to make
changes in the criteria of this tab the operator has to tick the checkbox next to the tab name.
If the checkbox next to the tab name is not ticked the criteria set in this tab will not be taken
into account during the search.

10.4.4.5 The IPM tab

This tab allows the operator to set search criteria for message of the type PLAIN. To be able
to make changes in the criteria of this tab the operator has to tick the checkbox next to the
tab name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not
be taken into account during the search.

 Avitech GmbH 2018 Page 338 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The Ipm Tab is composed of four sub tabs:


• The IPM Details sub-tab
• The Deliv. Envelope sub-tab
• The Subm. Envelope sub-tab
• The Submission Result sub-tab

10.4.4.6 The Ipn tab

This tab allows the operator to set search criteria for message of the type Ipn. To be able to
make changes in the criteria of this tab the operator has to tick the checkbox next to the tab
name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not be
taken into account during the search.
The Ipn Tab is composed of four sub tabs:
• The Ipn Details sub-tab
• The Deliv. Envelope sub-tab
• The Subm. Envelope sub-tab
• The Submission Result sub-tab

 Avitech GmbH 2018 Page 339 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.7 The Report tab

This tab allows the operator to set search criteria for message of the type Report. To be able
to make changes in the criteria of this tab the operator has to tick the checkbox next to the
tab name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not
be taken into account during the search.
Subject MTS Identifier
The search will be processed within messages containing the given subject MTS
identifier.
Content Identifier
The search will be processed within messages containing the given content identifier.
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).
Reported Recipient Information
The search will look at the details set in the reported recipient information of the
message.
Actual Recipient Name
The search will be processed within messages containing the given actual
recipient name.
Delivery Time
The search will be processed within messages which delivery time is
comprised within the selected time range.

 Avitech GmbH 2018 Page 340 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Type of MTS User


The search will be processed within messages containing the selected type of
MTS user.
Non-Delivery Reason Code
The search will be processed within messages containing the selected non-
delivery reason code.

10.4.4.8 The Probe tab

This tab allows the operator to set search criteria for message of the type Probe. To be able
to make changes in the criteria of this tab the operator has to tick the checkbox next to the
tab name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not
be taken into account during the search.
The Probe Tab is composed of two sub tabs:
• The Probe Details sub-tab
• The Submission Result sub-tab

 Avitech GmbH 2018 Page 341 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.9 Sub-tabs

10.4.4.9.1 The IPM Details sub-tab

This tab allows the operator to set search criteria for IPM details of message of the type
PLAIN. To be able to make changes in the criteria of this tab the operator has to tick the
checkbox next to the tab name. If the checkbox next to the tab name is not ticked the criteria
set in this tab will not be taken into account during the search.
ATS Priority
The search will be processed within messages containing one of the selected ATS
priority(ies).
Filing Time
The search will be processed within messages which filing time is comprised within
the selected time range.
Importance
The search will be processed within messages of one of the selected importance
level.
OHI
The search will be processed within messages containing the given optional heading
information.
IPM Originator
The search will be processed within the messages containing the given originator
address. No wild card can be used within this field
It is possible to enter the 8 letters of an AFTN address in this field when using wild
cards before and after the AFTN address string.

 Avitech GmbH 2018 Page 342 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

IPM Identifier
The search will be processed within messages containing the given IPM Identifier.
Subject
The search will be processed within messages containing the given subject.
Body Text
The search will be processed within the messages containing the body text entered
here.
Attachments (bytes)
The search will be processed within the messages containing attachments which size
is comprised in the range selected. Each attachment will be checked separately.
Ipm Recipients
The search will look at the details set for each recipient of the messages.
Type
The search will be processed within the messages containing Ipm recipients
with the selected type(s)
• To
• CC
• BCC
O/R Address
The search will be processed within the messages containing Ipm recipients
with the given OR address.
It is also possible to enter the 8 letters of an AFTN address in this field when
using wild cards before and after the AFTN address string.
Notification Request
The search will be processed within the messages containing Ipm recipients
with the selected notification report(s)

 Avitech GmbH 2018 Page 343 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.9.2 The Ipn Details sub-tab

This tab allows the operator to set search criteria for Ipn details of message of the type Ipn.
To be able to make changes in the criteria of this tab the operator has to tick the checkbox
next to the tab name. If the checkbox next to the tab name is not ticked the criteria set in this
tab will not be taken into account during the search.
Ipn Originator
The search will be processed within the messages containing the given Ipn originator
address.
Ipn-Intended Recipient
The search will be processed within the messages containing the given Ipm-intended
recipient address.
Subject Ipm-Identifier
The search will be processed within messages containing the given subject Ipm-
identifier.
Converted Encoded Information Types
The search will be processed within messages containing the given converted
encoded information types.
Receipt Information
The search will look at the details set in the receipt information of the message.
Receipt Time
The search will be processed within messages which receipt time is
comprised within the selected time range.
Acknowledge Mode
The search will be processed within the messages containing the selected
acknowledge mode.

 Avitech GmbH 2018 Page 344 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.9.3 The Probe Details sub-tab

This tab allows the operator to set search criteria for details of message of the type Probe.
To be able to make changes in the criteria of this tab the operator has to tick the checkbox
next to the tab name. If the checkbox next to the tab name is not ticked the criteria set in this
tab will not be taken into account during the search.
Content Length
The search will be processed for probe messages with content length in the given
range.
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).
Content Identifier
The search will be processed within messages containing the given content identifier.
Envelope Originator
The search will be processed within messages containing the given envelope
originator.
Implicit Conv.
The search will be processed within messages containing or not containing "implicit
conversion prohibited".
Conv. w. loss
The search will be processed within messages containing or not containing
"conversion with loss prohibited".

 Avitech GmbH 2018 Page 345 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Disclosure
The search will be processed within messages containing or not containing
"disclosure of other recipient Allowed".
Altn. Recip.
The search will be processed within messages containing or not containing "alternate
recipient allowed".
DL Exp.
The search will be processed within messages containing or not containing "delivery
list expansion prohibited".
Cont. Ret.
The search will be processed within messages containing or not containing "report
content return request".
Reassignm.
The search will be processed within messages containing or not containing "recipient
reassignment prohibited".
Latest delivery
The search will be processed within messages which latest delivery time is comprised
within the selected time range.
Envelope Recipients
Address
The search will be processed within messages containing the given recipient
name
Originator Report Request
The search will be processed within messages containing the selected
originator report request.

 Avitech GmbH 2018 Page 346 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.9.4 The Deliv. Envelope sub-tab

This tab allows the operator to set search criteria for the delivery envelope of message of the
type PLAIN. To be able to make changes in the criteria of this tab the operator has to tick the
checkbox next to the tab name. If the checkbox next to the tab name is not ticked the criteria
set in this tab will not be taken into account during the search.
X.400 Priority
The search will be processed within messages containing one of the selected X.400
priority(ies).
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).
Content Identifier
The search will be processed within messages containing the given content identifier.
MTS Identifier
The search will be processed within messages containing the given MTS identifier.
Envelope Originator
The search will be processed within messages containing the given envelope
originator.
Envelope Recipients
The search will be processed within messages containing the given envelope
recipients.

 Avitech GmbH 2018 Page 347 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Delivery Time
The search will be processed within messages which delivery time is comprised
within the selected time range.
Implicit Conv.
The search will be processed within messages containing or not containing "implicit
conversion prohibited".
Conv. w. loss
The search will be processed within messages containing or not containing
"conversion with loss prohibited".

10.4.4.9.5 The Subm. Envelope sub-tab

This tab allows the operator to set search criteria for the submission envelope of message of
the type PLAIN. To be able to make changes in the criteria of this tab the operator has to tick
the checkbox next to the tab name. If the checkbox next to the tab name is not ticked the
criteria set in this tab will not be taken into account during the search.
X.400 Priority
The search will be processed within messages containing one of the selected X.400
priority(ies).
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).
Content Identifier
The search will be processed within messages containing the given content identifier.

 Avitech GmbH 2018 Page 348 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Envelope Originator
The search will be processed within messages containing the given envelope
originator.
Implicit Conv.
The search will be processed within messages containing or not containing "implicit
conversion prohibited".
Conv. w. Loss
The search will be processed within messages containing or not containing
"conversion with loss prohibited".
Disclosure
The search will be processed within messages containing or not containing
"disclosure of other recipients".
Altn. Recip.
The search will be processed within messages containing or not containing "alternate
recipient allowed".
DL Exp.
The search will be processed within messages containing or not containing "delivery
list expansion prohibited".
Cont. Ret.
The search will be processed within messages containing or not containing "report
content return request".
Reassignm.t
The search will be processed within messages containing or not containing "recipient
reassignment prohibited".
Latest delivery
The search will be processed within messages which latest delivery time is comprised
within the selected time range.
Envelope Recipients
Recipients Address
The search will be processed within messages containing the given recipient
name
Originator Report Request
The search will be processed within messages containing the selected
originator report request.

 Avitech GmbH 2018 Page 349 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.4.4.9.6 The Submission Result sub-tab

This tab allows the operator to set search criteria for the submission results of message of
the type PLAIN. To be able to make changes in the criteria of this tab the operator has to tick
the checkbox next to the tab name. If the checkbox next to the tab name is not ticked the
criteria set in this tab will not be taken into account during the search.
Submission Time
The search will be processed within messages which submission time is comprised
within the selected time range.
MTS Identifier
The search will be processed within messages containing the given MTS identifier.

10.5 The AMHS Channel Configuration mask

This unit allows the administrator to create, modify or delete AMHS channels.
Note: Always restart the client on which a channel is running after modification.

 Avitech GmbH 2018 Page 350 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.5.1 Functions

10.5.1.1 File

New
Clears all the fields
Open
Opens an existing AMHS channel
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic skills.
Save
Saves the current AMHS channel. This is only possible if the AMHS channel has
already been named with the Save As function.
Save As
Saves the current AMHS channel under a new name.
Delete
Deletes the current AMHS channel.
Close
Closes the unit.

10.5.2 Fields
Channel Name
The name of the channel. It is given when the Save As function is selected.
Activation Date
The date and time when the Channel was last used from a client.

 Avitech GmbH 2018 Page 351 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Session Type
Type of connection to the MTA.
• P3: MTS (message transfer system) access protocol. The user agent is
directly connected to the MTA
• P7: MS (message store) access protocol. The user agent is connected to the
MTA via a message store.
O/R Address
The O/R Address of the channel. According to the addressing scheme chosen the
syntax used for the O/R address is different.
Message Quota [kB]
The maximum volume (in kB) of the message texts sent within the retention time.
Used Message Quota [kB]
Volume (in kB) of message texts sent within the retention time already used.
Alignment
The contents of the alignment function to be used with this channel.
• CR_LF
• CR_CR_LF
Retention Time
The number of days the messages will be retained before automatic deletion.
Attachment Quota [kB]
The maximum volume (in kB) of the files attached sent within the retention time.
Used Attachment Quota [kB]
Volume (in kB) of the files attached sent within the retention time already used.
Initial State
The initial connection state of the channel.
• CONN_BY_HOST: The connection is automatically initiated by the host
server.
• DISCONNECTED: The channel is disconnected.
Current State
The current state of the channel
• ACTIVE
• INACTIVE
MTA Device
The name of the MTA device uses with this channel. The MTA device shall have
been created before the creation of the channel.
Note: It is recommended to use only one channel per MTA device.

 Avitech GmbH 2018 Page 352 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.6 MTA Device Configuration

This unit allows the administrator to create, modify or delete MTA devices. MTA devices list
the parameters necessary to initiate a connection to the MTA. MTA devices shall be created
before AMHS channels.

10.6.1 Functions

10.6.1.1 File

New
Clears all the fields
Open
Opens an existing MTA device
Save
Saves the current MTA device. This is only possible if the MTA device has already
been named with the Save As function.
Save As
Saves the current MTA device under a new name.

 Avitech GmbH 2018 Page 353 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Delete
Deletes the current MTA device.
Close
Closes the unit.

10.6.2 Fields
Name
The name of the MTA device. It is given when the Save As function is selected.
Direction
The direction in which the MTA device handles messages from the point of view in
the client.
• OFF: The MTA device handles neither incoming nor outgoing messages.
• IN: The MTA device handles incoming messages.
• OUT: The MTA device handles outgoing messages.
• BOTH: The MTA device handles incoming and outgoing messages.
Server / MTA
The network address of the server / MTA. Usually the data entered here is the name
or the IP address of the server.
Password
The authentication password for the MTA
Connection Check Settings
If the checkbox is ticked the system will check the connection to the MTA device.
The interval field sets the interval in milliseconds between two connection checks.
The default value is 10000.

 Avitech GmbH 2018 Page 354 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7 Statistics function

This function enables the operator to search for several different statistics.
The different statistic types are described in the following sections:
• The standard tab
• The traffic relation tab
• The address tab
• The day23 tab
• The AMC tab
• The channel offline tab
• The application offline tab
• The annex A tab
• The annex B tab
• The annex D tab
• The annex G tab
• The annex I tab
• The annex J tab
• The annex K tab
• The annex L tab

 Avitech GmbH 2018 Page 355 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.1 Functions

10.7.1.1 File Menu

New
Clears the tab currently displayed.
Search
Searches the statistics according to the entered constraints.
Export
Saves the statistics of the tab currently displayed.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing Mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing Mechanism of the chapter Basic Skills.
Close
Closes the unit.

10.7.1.2 options Menu

Show Toolbar
Hides or displays the toolbar.

10.7.2 Common statistic fields


Hour
The hour to constraint results.
Day
The day to constraint results.

 Avitech GmbH 2018 Page 356 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Month
The month to constraint results.
Year
The year to constraint results. If nothing is entered in this field the current year will
apply.

10.7.3 The standard tab

The standard statistics display general information about the massage switching system.

10.7.3.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Observation Point
Type
The type of the observation point. Possible values:
• Circuit
• AeAx
• VC
• MTA

 Avitech GmbH 2018 Page 357 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• UA
• Faulty AFTN
• OVF
The entry is mandatory.
Value
The value of the observation point.
The entry is optional.

10.7.3.2 Result columns

10.7.3.2.1 Observation point type: Circuit


Time Stamp
The date for which the statistic applies.
Circuit
The circuit for which the statistic applies.
Subsystem
The subsystem for which the statistic applies.
Number Received Messages
The total number of messages received on the circuit.
Cumulated Length Received Messages
The cumulated length of messages received on the circuit.
Average Length Received Messages
The average length of messages received on the circuit.
Maximum Length Received Messages
The maximum length of messages received on the circuit.
Number Transmitted Messages
The number of messages transmitted on the circuit.
Cumulated Length Transmitted Messages
The cumulated length of messages transmitted on the circuit.
Average Length Transmitted Messages
The average length of messages transmitted on the circuit.
Maximum Length Transmitted Messages
The maximum length of messages transmitted on the circuit.
Number Received Faulty Messages (Error Code 0)
The number of faulty messages with error code 0 received on the circuit.

 Avitech GmbH 2018 Page 358 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Number Received Faulty Messages (Error Code 1)


The number of faulty messages with error code 1 received on the circuit.
Number Received Faulty Messages (Error Code 2)
The number of faulty messages with error code 2 received on the circuit.
Number Received Faulty Messages (Error Code 3)
The number of faulty messages with error code 3 received on the circuit .
Number Repeated Messages Due to Service Message
The number of messages repeated because of the reception of a service message on
the circuit.
Number Repeated Messages Due to Operator Command (No Display)
The number of messages repeated because of an operator command without display
of the message on the circuit.
Number Repeated Messages Due to Operator Command (After Display)
The number of messages repeated because of an operator command with display of
the message on the circuit.
Number Received Messages Priority SS
The number of messages received on the circuit with the priority SS.
Number Transmitted Messages Priority SS
The number of messages transmitted on the circuit with the priority SS.
Number Received Messages Priority DD
The number of messages received on the circuit with the priority DD.
Number Transmitted Messages Priority DD
The number of messages transmitted on the circuit with the priority DD.
Number Received Messages Priority FF
The number of messages received on the circuit with the priority FF.
Number Transmitted Messages Priority FF
The number of messages transmitted on the circuit with the priority FF.
Number Received Messages Priority GG
The number of messages received on the circuit with the priority GG.
Number Transmitted Messages Priority GG
The number of messages transmitted on the circuit with the priority GG.
Number Received Messages Priority KK
The number of messages received on the circuit with the priority KK.
Number Transmitted Messages Priority KK
The number of messages transmitted on the circuit with the priority KK.

 Avitech GmbH 2018 Page 359 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Number Received Messages Channel Check


The number of channel check messages received on the circuit.
Number Transmitted Messages Channel Check
The number of channel check messages transmitted on the circuit.
Number Received Service Messages
The number of service messages received on the circuit.
Number Transmitted Service Messages
The number of service messages transmitted on the circuit.

10.7.3.2.2 Observation point type: Faulty AFTN


Time Stamp
The date for which the statistic applies.
Faulty AFTN
The total number of faulty AFTN messages received.
Number Messages Forwarded to the Correction Position
The number of faulty AFTN messages forwarded to the correction position.
Number Messages Reinserted from the Correction Position
The number of faulty AFTN messages reinserted in the queue from the correction
position.
Number Messages Deleted from the Correction Position
The number of faulty AFTN messages deleted from the correction position.
Number Messages Responded by a Service Message
The number of faulty AFTN messages responded by a service message

10.7.3.2.3 Observation point type: OVF


Time Stamp
The date for which the statistic applies.
OVF
The Overflow
Number Messages sent to Overflow
The total number of messages sent to the overflow.
Number Messages sent to Overflow due to Diversion Command
The number of messages sent to the overflow because of a diversion command.
Number Messages sent to Overflow due to Threshold 3 Handling (spooling)
The number of messages sent to the overflow because of the handling of Threshold
3.

 Avitech GmbH 2018 Page 360 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Number Messages sent to Overflow due to Unavailable CIDIN Exit Centre


The number of messages sent to the overflow because of unavailable CIDIN Exit
Centre.
Number Messages sent to Overflow due to Forced Routing (OMQ)
The number of messages sent to the overflow because of OMQ forced routing.
Number Messages Received from Overflow
The number of messages received from the overflow.
Number Messages Reinserted from Overflow
The number of messages reinserted from the overflow in the routing queues.
Number Messages Deleted from Overflow
The number of messages deleted from the overflow.

10.7.4 The traffic relation tab

The traffic relation statistic tab displays the traffic of messages from one circuit to another.

10.7.4.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.

 Avitech GmbH 2018 Page 361 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Observation Point From


Type
The type of the source observation point. Possible values
• Circuit
The entry is mandatory.
Value
The value of the source observation point.
The entry is optional.
Observation Point To
Type
The type of the destination observation point. Possible values
• Circuit
• OVF
The entry is mandatory.
Value
The value of the destination observation point.
The entry is optional.

10.7.4.2 Result columns


Time Stamp
The date for which the statistic applies.
From Circuit
The origin circuit for which the statistic applies.
From Subsystem
The origin subsystem for which the statistic applies.
To Circuit
The destination circuit for which the statistic applies.
To Subsystem
The subsystem circuit for which the statistic applies.
Number of Messages
The number of messages transmitted from the "From Circuit" and received from the
"To Circuit".
Average Message Length
The average messages length of the messages transmitted from the "From Circuit"
and received from the "To Circuit".

 Avitech GmbH 2018 Page 362 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Maximum Message Length


The maximum messages length of the messages transmitted from the "From Circuit"
and received from the "To Circuit".
Average Switching Time
The average switching time of the messages transmitted from the "From Circuit" and
received from the "To Circuit".

10.7.5 The address tab

The address statistics display the number of messages received and transmitted from
addresses.

10.7.5.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Address Definition
Address
The Address to constraint results
The entry is optional.

 Avitech GmbH 2018 Page 363 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.5.2 Result columns


Time Stamp
The date for which the statistic applies.
Address
The address for which the statistic applies.
Number of Received Messages
The number of messages received from this address.
Number of Transmitted Messages
The number of messages transmitted from this address.

10.7.6 The day23 tab

The day23 statistic is generated the 23rd of the first month of each trimester (i.e. 23rd
January, 23rd April, 23rd July and 23rd October). It shows the specific statistic of this day. It
is the snapshot of the message transmission on this day.

10.7.6.1 Search fields


Time Interval
Quarter
The quarter to constraint results.

 Avitech GmbH 2018 Page 364 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.6.2 Result columns


Quarter
The date of the statistic in the form MMDD.
ICAO Origin
The AFTN address indicator of the originator of the message.
Prio SS
The number of messages with the priority SS transmitted.
Prio FF
The number of messages with the priority FF transmitted.
Prio GG
The number of messages with the priority GG transmitted.
Prio KK
The number of messages with the priority KK transmitted.
Prio DD
The number of messages with the priority DD transmitted.
Message Transition
The transition time in seconds of the messages per priority.
Prio SS Maximum (sec)
The maximum transition time of messages of priority SS.
Prio FF Maximum (sec)
The maximum transition time of messages of priority FF.
Prio GG Maximum (sec)
The maximum transition time of messages of priority GG.
Prio KK Maximum (sec)
The maximum transition time of messages of priority KK.
Prio DD Maximum (sec)
The maximum transition time of messages of priority DD.
Prio SS Average (sec)
The average transition time of messages of priority SS.
Prio FF Average (sec)
The average transition time of messages of priority FF.
Prio GG Average (sec)
The average transition time of messages of priority GG.

 Avitech GmbH 2018 Page 365 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Prio KK Average (sec)


The average transition time of messages of priority KK.
Prio DD Average (sec)
The average transition time of messages of priority DD.

10.7.7 The AMC tab

The AMC statistics provide monthly AMHS statistics and AMHS peak hours statistics for
upload to the AMC in form of CSV files.

10.7.7.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
AMC Definition
Type
The AMS statistic type. Possible values:
• MTA
• MTA Peak
The entry is mandatory.

 Avitech GmbH 2018 Page 366 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.7.2 Result columns

10.7.7.2.1 AMC Definition: MTA


STAT_ID
The number of the row.
SOURCE_COM
The name of the source COM centre.
DESTIN_COM
The name or the address of the destination COM centre.
DATE
The date when the statistic applies.
TOT_NBR_MSG_TX
Ind1 - Number of data messages transmitted daily. This element is defined as the
number of information objects which the managed MTA has transmitted to the
adjacent MTA.
TOT_AVSI_MSG_TX
Ind2 - Average size of the data messages transmitted daily. This element is defined
as the average size of information objects which the managed MTA has transmitted
to the adjacent MTA.
TOT_MXSI_MSG_TX
Ind3 - Maximum size of the data messages transmitted daily. This element is defined
as the size of the largest information object which the managed MTA has transmitted
to the adjacent MTA.
TOT_NBR_MSG_RX
Ind4 - Number of data messages received daily. This element is defined as the
number of information objects which the managed MTA has received from the
adjacent MTA.
TOT_AVSI_MSG_RX
Ind5 - Average size of the data messages received daily. This element is defined as
the average size of information objects which the managed MTA has received from
the adjacent MTA.
TOT_MXSI_MSG_RX
Ind6 - Maximum size of the data messages received daily. This element is defined as
the size of the largest information object which the managed MTA has received from
the adjacent MTA.
TOT_AVDE_MSG_TX
Ind7 - Average number of destination addresses per message transmitted daily: This
element is defined as the average number (rounded up or down to the nearest integer
value) of recipient addresses included per information object which the managed
MTA has sent to the adjacent MTA.

 Avitech GmbH 2018 Page 367 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

TOT_MSG_AVTT
Ind8 - Average transfer time (AIRAC cycle basis). This element is defined as the
average transfer time, over one day, of a sample message from the managed MTA to
the adjacent MTA.
TOT_MSG_REJ
Ind9 - Number of messages rejected daily. This element is defined as the number of
information objects received from the adjacent international MTA and rejected by the
managed MTA. An information object is considered to be rejected when the managed
MTA discards the object for at least one recipient or in its entirety, independent if a
report is generated or not and independent from the reason.
TOT_VOL_IPP_TX
Ind10- Overall traffic volume at the level of IP packets (daily total). This element is
defined as the amount of bytes of the IP packets which the managed MTA has
transmitted towards the adjacent MTA.
TOT_MAX_OUTT
Ind11 - Maximum outage duration of association between MTAs (if any). This element
is defined as the duration of the largest outage period calculated as the time when it
becomes impossible to establish any association to an adjacent MTA to the time a
message is transferred successfully to that adjacent MTA.
TOT_CML_OUTT
Ind12 - Cumulated outage duration of association between MTAs (if any). This
element is defined as the cumulated duration of the outage periods (using the same
definition of outage period as in Ind11 above).

10.7.7.2.2 AMC Definition: MTAPeak


STAT_ID
The number of the row.
SOURCE_COM
The name of the source COM centre.
DESTIN_COM
The name or the address of the destination COM centre.
DATE
The date when the statistic applies.
PK_NBR_MSG_TX
Ind13 - Number of data messages transmitted during the peak hour. This element is
defined as the number of information objects which the managed MTA has
transmitted to the adjacent MTA.
PK_AVSI_MSG_TX
Ind14 - Average size of the data messages transmitted during the peak hour. This
element is defined as the average size of information objects which the managed
MTA has transmitted to the adjacent MTA.

 Avitech GmbH 2018 Page 368 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

PK_MXSI_MSG_TX
Ind15 - Maximum size of the data messages transmitted during the peak hour. This
element is defined as the size of the largest information object which the managed
MTA has sent to the adjacent MTA.
PK_NBR_MSG_RX
Ind16- Number of data messages received during the peak hour: This element is
defined as the number of information objects which the managed MTA has received
from the adjacent (adjacent international) MTA.
PK_AVSI_MSG_RX
Ind17 - Average size of the data messages received during the peak hour. This
element is defined as the average size of information objects which the managed
MTA has received from the adjacent MTA.
PK_MXSI_MSG_RX
Ind18 - Maximum size of the data messages received during the peak hour. This
element is defined as the size of the largest information object which the managed
MTA has received from the adjacent MTA.
PK_AVDE_MSG_TX
Ind19 - Average number of destination addresses per message transmitted during the
peak hour. This element is defined as the average number (rounded up or down to
the nearest integer value) of recipient addresses included per information object
which the managed MTA transmitted to the adjacent MTA.
PK_MSG_AVTT
Ind20 - Average transfer time (peak hour basis). This element is defined as the
average transfer time, over the peak interval of the considered month, of a sample
message from the managed MTA to the adjacent MTA.
PK_MSG_REJ
Ind21 - Number of messages rejected during the peak hour. This element is defined
as the number of information objects received from the adjacent international MTA
and rejected by the managed MTA.
PK_VOL_IPP_TX
Ind22 - Overall peak hour traffic volume at the level of IP packets. This element is
defined as the amount of bytes of IP packets which the managed MTA has
transmitted towards the adjacent MTA.

 Avitech GmbH 2018 Page 369 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.8 The channel offline tab

The channel offline statistics display the offline time per channel. A channel is considered as
offline when it is neither open nor hold.

10.7.8.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter
Channel Definition
Channel
The name of the channel to constraint results.
The entry is optional.
State
The state of the channel. Possible values are:
• ALL
• OPEN
• CLOSED
• TEST
• BLOCKED
• HOLD

 Avitech GmbH 2018 Page 370 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• DEAD
• CLOSE_INPUT
The entry is mandatory.

10.7.8.2 Result columns


From Date
The date and time of the beginning of the offline period of the channel.
To Date
The date and time of the end of the offline period of the channel.
Subsystem
The subsystem to which the statistic applies.
Circuit
The circuit to which the statistic applies.
Channel
The channel to which the statistic applies.
State
The offline state of the channel.
Offline Time in seconds
Offline Time of the channel in seconds.
Offline Time percentage
Offline Time of the channel in per cent of the chosen time interval.
Number of disconnections
Number of disconnections during the chosen time interval.

 Avitech GmbH 2018 Page 371 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.9 The application offline tab

The application offline statistics display the offline time per application.

10.7.9.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Application Definition
Application
The name of the application to constraint results.
The entry is optional.
State
The state of the application. Possible values are:
• UNKNOWN
• INIT
• OUT_CNTRL
• READY
• DOWN
• RUNNING
• UNDEFINED
The entry is mandatory.

 Avitech GmbH 2018 Page 372 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.9.2 Result columns


From Date
The date of the beginning of the offline period of the application.
To Date
The date of the end of the offline period of the application
Application
The name of the application that was offline.
State
The offline state of the application.
Server
The name of the server on which the application runs.
Offline Time in seconds
The period in seconds during which the application was offline.
Offline Time percentage
The period in per cent of the chosen interval during which the application was offline.
Number of Shutdowns
The number of shutdowns

10.7.10 The annex A tab - Switching Time Statistics

The annex A - switching time statistics allow qualified statements on switching times filtered
by origin, destination and priority groups.

 Avitech GmbH 2018 Page 373 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.10.1 Search fields


Time Interval
This field is described in the section Common statistic fields of this chapter.
Search Parameters Definition
Quarter
The quarter number.
The entry is mandatory.
Circuit
The name of the circuit.
The entry is mandatory.

10.7.10.2 Result columns


Circuit
The name of the circuit to which the statistic applies.
Originating Centre
The name of the originating centre to which the statistic applies.
Adjacent Centre
The name of the adjacent centre to which the statistic applies.
Priority group
The group or priorities to which the statistic applies.
Messages for priority group
The number of messages switched for the priority group.
Fix value
Hard coded value.
Max Routing Time
The maximum routing time.
Routing Median
The median routing time.
Max Tx Time
The maximum transmission time.
Observations
additional observations.

 Avitech GmbH 2018 Page 374 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.11 The annex B tab - Circuit Statistics

The annex B - circuit statistics provides information regarding daily traffic, queue sizes and
waiting times.

10.7.11.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Circuit Definition
Circuit
The name of the circuit.
The entry is mandatory.

10.7.11.2 Result columns


Date
The date to which the statistic applies.
Circuit
The circuit which the statistic applies.
Messages
SS rx
The number of messages of priority SS received.
SS tx
The number of messages of priority SS transmitted.

 Avitech GmbH 2018 Page 375 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

DD/FF rx
The number of messages of priority DD/FF received.
DD/FF tx
The number of messages of priority DD/FF transmitted.
GG/KK rx
The number of messages of priority GG/KK received.
GG/KK tx
The number of messages of priority GG/KK transmitted.
SVC rx
The number of messages of priority SVC received.
SVC tx
The number of messages of priority SVC transmitted.
Rejected
The number of messages rejected.
Max Queued
Num
The maximum number of messages queued.
Duration
The maximum time a message was queued.

10.7.12 The annex D tab - Circuit Occupancy Statistics

 Avitech GmbH 2018 Page 376 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The annex D - circuit occupancy statistics provide a monthly report regarding circuit
occupancy, line speeds, average loads, peak hours and throughput.

10.7.12.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Circuit Definition
Originator
The name of the originator.
The entry is mandatory.
Target Circuit
The name of the target circuit.
The entry is mandatory.

10.7.12.2 Result columns


Date
The date to which the statistic applies.
Originator
The address of the originator.
Originator Indicator
The originator indicator.
Destination
The destination address.
Destination Indicator
The destination indicator.
Line speed
The speed of the line
Max Rx Bytes in Peak Hour
The maximum number of bytes received during peak hour.
Rx Peak Hours Load
The received message load during peak hour.
Total Rx Bytes
The total number of bytes received during peak hour.
Rx Bytes Avg Daily Load
The average daily load of received message.
Max Tx Bytes in Peak Hour
The maximum number of bytes transmitted during peak hour.

 Avitech GmbH 2018 Page 377 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Tx Peak Hours Load


The transmitted message load during peak hour.
Total Tx Bytes
The total number of bytes transmitted during peak hour.
Tx Bytes Avg Daily Load
The average daily load of transmitted message.

10.7.13 The annex G tab - Circuit Availability Statistics

The annex G - circuit availability statistics inform the operator about the availability of the
switching service on a per-circuit and configurable time interval basis.

10.7.13.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Search Parameter Definition
Originator
The name of the originator.
The entry is mandatory.
Destination
The name of the destination.
The entry is mandatory.

 Avitech GmbH 2018 Page 378 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Device Type
The device type to constraint results.
The entry is mandatory.
Granularity Definition
Granularity
The granularity to constraint results. Possible values are:
• FIVE
• TEN
• TWENTY

10.7.13.2 Result columns


Date
The date to which the statistic applies.
Device Type
The device type to which the statistic applies.
Originator
The originator to which the statistic applies.
Originator Indicator
The originator indicator.
Destination
The destination to which the statistic applies.
Destination Indicator
The destination indicator.
Interruption in Mins
The number of minutes the switching service was interrupted.
Avg Dispo
The average availability of the switching service.

 Avitech GmbH 2018 Page 379 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.14 The annex I tab - Detailed Operational Statistics

The annex I - detailed operational statistics filters and lists AFTN/AMHS operational
summaries including: message identifiers, filling times, switching times, message types and
transmission delays.

10.7.14.1 Search fields


Time Interval
Period Type
The type of period to constraint results. Possible values are:
• HOURLY
• DAILY
• WEEKLY
• MONTHLY
• YEARLY
The other fields are described in the section Common statistic fields of this
chapter.

 Avitech GmbH 2018 Page 380 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Search Parameter Definition


Message Type
The type of the message. Possible values are:
• FPL
• TAF
• METAR
• NOTAM
The entry is mandatory.
Center
The name of the centre.
The entry is mandatory.

10.7.14.2 Result columns


Rx EMID
The message identifier of the received message
Filing Time
The filing time of the message
Message content
The first 10 characters of the message text
Rx time
The timestamp of message reception
Switching Delay
The switching time
Tx EMID
The message identifier of the transmitted message
Tx time
The timestamp of message transmission
Tx Delay
The transmission delay

 Avitech GmbH 2018 Page 381 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.15 The annex J tab - Operational Statistics Summary

The annex J - operational statistics summary filters and lists a condensed view of the routing
activity, including message counts grouped by originator and recipient.

10.7.15.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Search Parameter Definition
Message Type
The type of the message. Possible values are:
• FPL
• TAF
• MEATR
• NOTAM
The entry is mandatory.
Center
The name of the centre.
The entry is mandatory.
Circuit
The name of the circuit.
The entry is optional.

 Avitech GmbH 2018 Page 382 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.15.2 Result columns


Centre
The Circuit to which the statistic applies.
Circuit
The circuit to which the statistic applies.
Originator
The originator of the message
Number of Rx Messages
The number of messages received.
Destination
The destination of the message
Number of Tx Messages
The number of messages transmitted.

10.7.16 The annex K tab - Service Availability Statistics

The annex K - service availability statistics inform the operator about the number of received,
transmitted and rejected messages of a given type for a given period of time (day, month,
year)

 Avitech GmbH 2018 Page 383 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.16.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Search Parameter Definition
Center
The name of the Circuit.
The entry is mandatory.
Circuit
The name of the circuit.
The entry is optional.

10.7.16.2 Result columns


Center
The name of the COM centre
Circuit
The name of the transmitting circuit
FPL
MfT
The number of FPL messages to be transmitted
MT
The number of FPL messages actually transmitted
Dispo
The availability (= MT * 100 / MfT)
TAF
MfT
The number of TAF messages to be transmitted
MT
The number of TAF messages actually transmitted
Dispo
The availability (= MT * 100 / MfT)
NOTAM
MfT
The number of NOTAM messages to be transmitted
MT
The number of NOTAM messages actually transmitted
Dispo
The availability (= MT * 100 / MfT)

 Avitech GmbH 2018 Page 384 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

METAR
MfT
The number of METAR messages to be transmitted
MT
The number of METAR messages actually transmitted
Dispo
The availability (= MT * 100 / MfT)
Totals
MfT
The sum of the number of messages to be transmitted
MT
The sum of the number of messages actually transmitted
dispo
The availability (= MT * 100 / MfT)

10.7.17 The annex L tab - Daily OPMET Statistics

The annex L - daily OPMET Statistics inform the operator about the availability of the
OPMET service (routing METAR and TAF messages) per circuit, per date, per originator and
per recipient and basis.

 Avitech GmbH 2018 Page 385 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.7.17.1 Search fields


Time Interval
These fields are described in the section Common statistic fields of this chapter.
Search Parameter Definition
Center
The name of the centre.
The entry is mandatory.
Circuit
The name of the circuit.
The entry is optional.

10.7.17.2 Result columns


Date
The date to which the statistic applies.
Centre
The centre to which the statistic applies.
Circuit
The circuit to which the statistic applies.
Originator
The originator of the message
Messages to be Sent
METAR
Number of METAR messages to be sent
TAF
Number of TAF messages to be sent
Destination
The destination of the message
Messages Sent
METAR
Number of METAR messages sent
TAF
Number of TAF messages sent

 Avitech GmbH 2018 Page 386 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.8 User Management unit

The User Management window is used to create of modify operator profiles. According to the
rights of the user operator in some functions may be disabled.

10.8.1 Choose user


This function is only available to operators with admin rights.
This function opens a chooser in which the administrator can select an existing profile in
order to change it.
More Information about choosers can be found in the section Chooser of the chapter Basic
skills.
Note: unsaved changes in a profile will be lost when a new profile is selected.

10.8.2 Change password


This function is available to all operators.

This function opens a new window in which the operator can change the password for his/her
profile. The fields are case sensitive. Clicking on the [OK]-button saves the password.

If the entries in the two fields are not identical a hint appears and the password is not saved.

 Avitech GmbH 2018 Page 387 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.8.3 Assign roles


This function is only available to operators with admin rights.

This function opens a new window in which the administrator can select or deselect roles for
a profile.
The upper line in this window allows the administrator to filter the roles. The filter field is case
sensitive.
Note: selecting a role may lead to the automatic selection of subordinate roles.
These roles are displayed in grey and cannot be deselected as long as the main
role is selected.

10.8.4 Assign pool


Only operators with admin rights can assign a pool to a profile.
To assign a pool the administrator shall select the properties tab and press the [F4]-key. This
action opens chooser in which the administrator can select a pool for a profile.
The upper line in this window allows the administrator to filter the pools. The filter field is
case sensitive.
Note: only one pool can be selected per profile. Selecting another pool
automatically deselects the current pool.

 Avitech GmbH 2018 Page 388 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.8.5 User management functions

10.8.5.1 File

New
Creates a new user.
This function is only available for users with admin rights.
Open
Opens a chooser displaying all users already created. Selecting a user from this
chooser displays his parameters in the User Management unit.
This function is only available for users with admin rights.
Save
Saves the changes.
Reload
Cancels all changes made since the last save action.
Close
Closes this unit.

10.8.5.2 Action

Change Password
Opens a new window to change the password of the user displayed in the Account
tab.
Assign Roles
Opens a new window to assign roles to the user displayed in the Account tab.
This function is only available for users with admin rights.

 Avitech GmbH 2018 Page 389 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.8.5.3 Options

Show Toolbar
Hides or displays the toolbar.

10.8.6 User management fields


The Account tab

User Name
The login name of the profile. This field is case sensitive.
If the operator has admin rights this field can be changed when the operator
creates a new profile, it is then a mandatory field. The rest of the time it is a
display only field.
In this field no accentuated characters can be used. Forbidden characters will
not be taken into account and will not be displayed.
Status
The status of the profile corresponding to the User Name. It can be active or
blocked.
If the operator has admin rights this field can be changed when the operator
creates a new profile, it is then a mandatory field. The rest of the time it is a
display only field.

 Avitech GmbH 2018 Page 390 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

First Name

The first name of the owner of the profile. This field is mandatory. If no entry
was made in this field a hint will be displayed as soon as the operator wants to
save the changes made.
Last Name

The last name of the owner of the profile. This field is mandatory. If no entry
was made in this field a hint will be displayed as soon as the operator wants to
save the changes made.
Address
The address of the owner of the profile. This field is optional.
Postal code
The postcode of the owner of the profile. This field is optional.
City
The city of the owner of the profile. This field is optional.
Country
The country of the owner of the profile. This field is optional.

 Avitech GmbH 2018 Page 391 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The Contact Information tab

Email
The e-mail address of the owner of the profile. This field is optional.
Phone
The phone number of the owner of the profile. This field is optional.
Fax
The fax number of the owner of the profile. This field is optional.
Company
The company of the owner of the profile. This field is optional.
Description
Any other information about the owner of the profile. This field is optional.

 Avitech GmbH 2018 Page 392 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The Roles tab

This tab lists the roles assigned to the profile. It is a display only field
The Properties tab

This tab shows the specific properties of the profile created. It displays to which group
the profile belongs.

 Avitech GmbH 2018 Page 393 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.8.7 Change password

This function opens a new window in which the user can change the password for his/her
profile. The fields are case sensitive. Clicking on the [OK]-button saves the password.

If the entries in the two fields are not identical a hint appears and the password is not saved.
Note: If no login is required at the start of the AviTerm application, this function is
not available.

10.9 Legal Recording unit


The Legal Recording application is mainly used to examine and analyse process data that
has been recorded. Process data is available in databases, which are currently being filled
(online recording) or which have already been removed to the archive (offline recording). The
archiving and the reading of the existing archive is part of the application. Details about the
menus can be found in the section Legal recording functions of this chapter.
The unit Legal Recording consists in three main parts:

 Avitech GmbH 2018 Page 394 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The navigation tree


It is situated on the left side of the window and gives the operator the possibility to
choose between the available databases. To activate the navigation tree or parts of it,
the relevant check-boxes have to be ticked.
The Selection Tab
After the operator has selected the database in the navigation tree the filter area in
this tab can be updated according to the entries existing in the chosen database.
The Result List Tab
After having made the optional selection of filter items and having clicked on the
[Search]-button, the results will be displayed in the Result List tab. This tab displays
the results of the online database followed by the results of the offline database. Each
of these result groups is ordered chronologically, displaying the oldest results on the
top of the list. Clicking on a single entry displays its content in the viewing field of the
lower part of the tab.

 Avitech GmbH 2018 Page 395 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

10.9.1 The navigation tree

The database from which the legal recording data have to be examined can be opened with
the navigation tree. There are two different types of database:
The offline database
In this database the archives that were created before will be imported for
investigation. This database can also be called investigation database.
Any entry can be imported and examined in this database, depending on the space
available. Every archive can be taken out of this database. Every data archived and
loaded in the investigation database can be read and exported from this database.
Each imported archive is available under its own node: Its name is defined as follows:
data type_logical name_node type_date.
Data type
This part shows that the imported data comes from the archive database. The
name is therefore always archive.
Logical name
The logical ID of the database from which the data was exported.
Node type
The type of data archived. The following possibilities exist:
• aftn: data related to the AFTN loader
• asb: data related to the airspace booking
• ats: data related to ATS apart from flight plan events
• fplevents: data related to flight plan events
• nt: data related to NOTAM
• pib: data related to briefing
• sbd: data related to Location Status
• sec: data related to security actions such as login and logout
• sw: data related to SNOWTAM
Date
The date of the recorded data.

 Avitech GmbH 2018 Page 396 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The online database


Each server has its own legal recording database. The unit Legal Recording
supports, according to the system configuration, the parallel access to several online
databases. The default database name is "live-s".
The data in this database is written by the applications that produces the legal
recording entries. These data is not yet archived on an external medium. This
database can also be called live database.
All the recorded and not yet archived entries are available for examination in this
database. Entries of this database can be saved in an archive. Subsequently it is
possible to remove the archived data from the database to make space for new
entries. Optionally the archived data will be automatically removed from the database
to prevent overflow.

10.9.2 The Selection Tab

This tabbed pane enables the operator to narrow the entries of the list.
Time Range
It is used to define or narrow the period in which the entries will be searched.
Application Filter
This filter is used to select the application searched, e.g. ATS, Retrieval, FPL,
AFTN...
The legal recording functionality stores changes in flight plans, ATS messages and
flight plan coordination under the application filter ATS and the handling of events is
stored under the application filter FPLEVENTS.

 Avitech GmbH 2018 Page 397 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Mime Filter
This filter is used to select the data type searched, e.g. ATS Cancel, ATS Arrival,
NOTAM, Flight Plan...
User Filter
This filter is used to select the initiator(s) of the action(s) searched. The initiator may
not only be a defined operator but also a service of the system.
Attribute Search
This filter allows to further detail the search. The following activities are available:
• Last_Store
• AFTN_Priority
• Action
• Status
The field "Key" is the status of the action searched. The operator is "="for Value is
equal or "!=" not equal. The following values are available.
• for the Key Last_Store:
o a date with the following format YYYYMMDDHHmm
• for the Key AFTN_Priority:
o FF
• for the Key Action:
o Delete
o Insert
o Proposal accepted
o Select
o Update
• for the Key Status:
o NOTAM waiting for operator
Hosts
This filter defines the host on which the search shall be executed.
Full-text Search
This field is a case sensitive search field. It can be used to search for a certain test or
text string within all related entries. To combine search criteria we propose to add
"<Space>+<Space>" to the search criteria.
"EDNY + EDDM" will search for all legal recording entries containing
BOTH search criteria.
It is possible to select the operator (user), the application, or the Mime type and perform a
free-text search at the same time. The chosen criteria will be logically connected with AND;
that means that to display an entry, all the criteria of the filter have to be filled in by this entry.

 Avitech GmbH 2018 Page 398 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

To get the result of the search the operator has to click on the [Search]-button and then go in
the "Result List" tab.
To simplify the choice the following fields are provided:
• Select All: selects all entries of the particular criterion (View operator, View
Application, View Mime)
• Deselect All: deselects all entries of the particular criterion (View operator, View
Application, View Mime)

10.9.3 The Result List Tab

After the optional selection of filter items and having clicked on the [Search]-button, the
results will be displayed in the "Result List" tab. This tab displays the results of the online
database followed by the results of the offline database. Each of these result groups is
ordered chronologically, displaying the oldest results on the top of the list. Clicking on a
single entry displays its content in the viewing field of the lower part of the tab.
These entries can now be processed. The following possibilities are available for all entries:
Print
The content of the preview window can be printed out. The operator only has to click
on the [Print]-button in the toolbar or click on print in the File menu.
Export
The content of the preview window can be exported. The operator has to make a right
mouse click in the preview window. Depending on the type (Mime Type) the entry can
be stored in raw format (format in which they were originally recorded), in pdf or in
html.

 Avitech GmbH 2018 Page 399 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Erroneous events are stored in the legal recording as follows:


• Application: ATS
• Mime type: Plain

At the end of the message text in the Result List an explanation line is displayed.
If such an erroneous event occurs, please contact your system provider.

10.9.4 Legal recording functions

10.9.4.1 File

New
Clears all fields.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic Skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic Skills.
Update
Refreshes the database according to the tree selection.

 Avitech GmbH 2018 Page 400 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Search
Performs a search on selected search criteria.
Close
Closes the application window, chosen views are maintained and will be available if
the window is anew opened unless the application is ended.

10.9.4.2 Archive

The menu items will only be active when the function is available in the operational context.
The following options are available in the toolbar.
Remove Archives
Removes the chosen archive(s) from the offline database. This function is only active
when at least one offline database is chosen.
Create Archives
Starts the creation of an archive. This function is only active if data is available to
create an archive and if a live database has been selected in the navigation tree.

selecting the [Create Archives]-function opens a popup window in which the


operator has to choose the maximum size of the archive to be created.
The archived data will be automatically removed from the database.
The created archives are divided into multiple files. The files are grouped by
applications. When the maximum file number of a group is reached a new file is
opened. This is repeated until all data for an application are archived.
The path in which the archive will be written is determined by the application and
cannot be changed.
The legal recording viewer is not available to the operator for the time of archiving.
After the archiving the storage path and the number of written records will be notified
to the operator by a pop up window. For permanent storage, the archives created
have to be saved manually by the operator on an external medium; for example CD,
DVD or tape.

 Avitech GmbH 2018 Page 401 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Read Archives
This starts to read an archive. This function is only active when an archive can be
read. Additionally an investigation database has to be selected in the navigation tree.
The archives have to be copied manually by the operator from the external medium
into the predefined directory. After having chosen the [Read Archives]-command a
chooser opens. With the activation of the [OK]-button the read process will begin for
the chosen archives. The archive will be written into the offline database. The viewer
is not available to the operator for the period of reading. When the selected archive
has been imported the number of records copied will be notified to the operator by a
popup and a new entry in the selection tree will be created in the Offline-s sub-node.
The re-imported archived data can then be investigated.

10.9.4.3 Options

Show Toolbar
Hides or displays the toolbar.
Check Database size
Activates or deactivates the automatic check of the database size:
• If the check of the database size is activated, the system will check the size of
all online databases.
• If the check of the database size is deactivated no warning will be issued
when an archive has to be created from a database.

10.9.5 Archiving
The archive function is provided to create archives from live recorded data and remove
recorded data from the live recording or to import already existing archives for further
analysis.
Since normally only a limited amount of legal recording entries can be held in the live
database, the archiving of live data has to be performed at regular intervals, for recording
reasons. This also provides for the permanent storage of the recorded data on external
media.
These archives can only be created on or read from a file system. According to the system
architecture they will be stored on the client or on the server side on a hard disk. Because
they are to be stored on another storage medium afterwards, the type of the storage medium
delimits the maximum size of an archive.
The functions in the Archive menu offer the possibility to create an archive from the live
database as well as to import an archive into the offline database.

 Avitech GmbH 2018 Page 402 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11 MESSAGE OFFICE MENU BAR BUTTON

11.1 Message Office functions

11.1.1 File

Refresh
Refreshes the message list.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic skills.
Delete
Deletes messages selected. This can only be done in the User Area.
Reply to
Create a reply message with the address of the sender of the selected message.
Reply all
Create a reply message with the address of the sender and the addresses of all
recipients of the selected message.
Forward
Create a message with the contents of the Subject and of the body of the selected
message.
Search Messages
Opens the search unit in which parameters can be entered in order to search defined
Messages. For more information please refer to the section The search function of
this chapter.

 Avitech GmbH 2018 Page 403 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Close
Closes the Message Office unit.

11.1.2 Options

Show Toolbar
Hides or displays the toolbar.
Detailed printout
If this checkbox is ticked, the printout will contain details.
Select Columns

Opens a window that allows the user to choose which columns are to be displayed in
the upper right pane of the selected node.
Note: The column selection applies to the selected folder and all its sub-
folders except for the search folder and the user Area.
For the search folder and the user Area the column selection applies to:
 Only the selected search results folder.
 Only the selected folder or sub-folder of the User Area

 Avitech GmbH 2018 Page 404 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Show Connection History

Opens the following window that shows the history list of the connection.
Channels

Allows configuring the channels of the Message Office as well as the auto process
profiles for each channel. For more information about these functions, please refer to
the sections AFTN Channel Configuration, AMHS Channel Configuration and
Autoprocess Profiles of this chapter.
Online Message Monitor
Opens the Online Message Monitor. For more information about this function, please
refer to the section Online Message Monitor of this chapter.

11.1.3 Context menus

11.1.3.1 Context menu of the Search node

This context menu is only available in sub-folders of the Search node.


Edit
Opens the Search unit with the last search settings used in the selected search
folder.

 Avitech GmbH 2018 Page 405 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Delete

Deletes the selected folder and all the messages it contains.


Note: The Search Results folder cannot be deleted.
Clear
Clears the search results of the selected search folder.
Search
Executes the search with the settings of the selected search folder.

11.1.3.2 Context menu of the User Area node

Add

Adds a sub-folder to the selected user area node or folder.


Delete

Deletes the selected folder and all the messages it contains.


Rename

Renames the selected folder.

 Avitech GmbH 2018 Page 406 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.3.3 Context menu of the Message Table

View as Plain
Displays the message as plain text message in the AFTN or AMHS viewer.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic skills.
Forward
Create a message with the contents of the Subject and of the body of the selected
message.
Reply to
Create a reply message with the address of the sender of the selected message.
Reply All
Create a reply message with the address of the sender and the addresses of all
recipients of the selected message.
Search for Related Messages
Searches the message office for messages related to the selected message. Related
messages can be:
• Reply messages connected to the selected message.
• Forward messages connected to the selected message.
• Notifications connected to the selected message.
• Reports connected to the selected message.

 Avitech GmbH 2018 Page 407 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Move to processed
In the processed folder the selected message can thus be moved without being
displayed first in the corresponding viewer of mask.
Delete
Deletes the selected message.

11.1.4 The search function

Selecting the function Search Messages in the File menu or making a double click on the
Search Result node opens the Search unit. This function allows the operator to search for
messages according to chosen criteria.
Note: If no criteria has been selected the search will be done over all messages. In
order for the search engine to work at its best capacity it is advised to select
nothing if the search has to be done over all possibilities of a criteria type.
Example: If the search has to be done in all messages of the Unprocessed node,
the Processed node and the Transmitted node, not selecting anything has the
same meaning in the search function than selecting each node but the search will
be slightly quicker.

 Avitech GmbH 2018 Page 408 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.4.1 Functions

11.1.4.1.1 File

New
Resets all the fields.
Search Messages
Starts the search according to the parameters set.
Next Search
Continues the search if more than 100 messages have been found.
Save Search Constraints
Saves the current search parameters as folder in the Search node.
Close
Closes the search unit.

11.1.4.1.2 Options

Show Toolbar
Displays or hides the toolbar.

11.1.4.2 Special Features


Wild cards
The operator can use the "%" character as a wild card in any text input field.
Examples:
• Body text: %YX ---- The system will search for all messages
with the Body text ending with YX.
• Body text body: ETCC% ---- The system will search for all
messages with the Body text beginning with ETCC.
• Body text: %AFL% ---- The system will search for all messages
containing the string AFL in the Body text.
• Body text: %TEST%252% ---- The system will search for all
messages containing the string TEST and the string 252 in the
body text.

 Avitech GmbH 2018 Page 409 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Selection lists
To select a block of successive entries in a selection list, the operator shall click on
the first entry to be selected, press the [Shift]-key and click on the last entry to be
selected.
To select entries that are not in a block the operator shall click on the first entry to be
selected, press the [Ctrl]-key, click on the next entry to be selected, keep the [Ctrl]-
key pressed, click on the next entry to be selected, and so on until the last entry. If
nothing has been selected, the search will occur in all possible entries of the selection
list.
To deselect an entry in a list the operator shall press the [Ctrl]-key and click on the
entry to be deselected.
3 state checkbox
This special checkbox can have 3 different states:
• Plain - ignore: the criteria will be ignored during the search
• Not ticked - false: the search will be made for messages which do not
contain this criteria
• Ticked - true: the search will be made for messages which contain this
criteria

11.1.4.3 The General tab

This tab allows the operator to set search criteria that apply to all message types.
Message Status
The search will be processed within the messages held in the selected node(s)

 Avitech GmbH 2018 Page 410 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Creation Time
The search will be processed within messages which delivery time is comprised
within the selected time range.
Last Changed Time
The search will be processed within messages which delivery time is comprised
within the selected time range.
Configured Channels
If more than one channel is configured, this field allows the operator to choose the
channel(s) in which the search will be executed.
Note: if only one channel is configured this field will not be displayed.

11.1.4.4 The AFTN tab

This tab allows the operator to set search criteria for AFTN messages. To be able to make
changes in the criteria of this tab the operator has to tick the checkbox next to the tab name.
If the checkbox next to the tab name is not ticked the criteria set in this tab will not be taken
into account during the search.

 Avitech GmbH 2018 Page 411 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.4.4.1 The Content tab

This tab allows the operator to set more search criteria. To be able to make changes in the
criteria of this tab the operator has to tick the checkbox next to the tab name. If the checkbox
next to the tab name is not ticked the criteria set in this tab will not be taken into account
during the search.
CSN Range
The search will be processed within the selected channel sequence number range.
Range combinations:
• If the input in the "Lower" field is lower than the input in the "Upper" field the
search will be executed within the defined range.
Example: CSN Range Lower = 90, Upper = 230, the search will be
executed for all messaged with a CSN from 90 to 230. These two values
are included in the search.
• If the input in the "Lower" field is greater than the input in the "Upper" field the
search will be executed outside the defined range.
Example: CSN Range Lower = 500, Upper = 50, the search will be
executed for all messaged with a CSN from 0 to 50 and from 500 to
9999. These two values are included in the search.
• If the input in the "Lower" field is the same as the input in the "Upper" field the
search will be executed only for this entry.
Example: CSN Range Lower = 40, Upper = 40, the search will be
executed for all messaged with a CSN of 40.
Date Time Group
The search will be processed within the Date Time Group comprised within the
selected time range.

 Avitech GmbH 2018 Page 412 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

ATS Priority
The search will be processed within messages containing one of the selected ATS
priorities.
Recipient
The search will be processed within messages containing the given recipient.
Filing Time
The search will be processed within messages which filing time is comprised within
the selected time range.
Originator
The search will be processed within messages containing the given Originator.
OHI
The search will be processed within messages containing the given optional heading
information.
Body Text
The search will be processed within the messages containing the body text entered
here.

11.1.4.5 The AMHS tab

This tab allows the operator to set search criteria for AMHS Messages. To be able to make
changes in the criteria of this tab the operator has to tick the checkbox next to the tab name.
If the checkbox next to the tab name is not ticked the criteria set in this tab will not be taken
into account during the search.

 Avitech GmbH 2018 Page 413 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.4.5.1 The IPM tab

This tab allows the operator to set search criteria for message of the type PLAIN. To be able
to make changes in the criteria of this tab the operator has to tick the checkbox next to the
tab name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not
be taken into account during the search.
The Ipm Tab is composed of four sub tabs:
• The IPM Details sub-tab
• The Deliv. Envelope sub-tab
• The Subm. Envelope sub-tab
• The Submission Result sub-tab

11.1.4.5.2 The Ipn tab

 Avitech GmbH 2018 Page 414 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

This tab allows the operator to set search criteria for message of the type Ipn. To be able to
make changes in the criteria of this tab the operator has to tick the checkbox next to the tab
name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not be
taken into account during the search.
The Ipn Tab is composed of four sub tabs:
• The Ipn Details sub-tab
• The Deliv. Envelope sub-tab
• The Subm. Envelope sub-tab
• The Submission Result sub-tab

11.1.4.5.3 The Report tab

This tab allows the operator to set search criteria for message of the type Report. To be able
to make changes in the criteria of this tab the operator has to tick the checkbox next to the
tab name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not
be taken into account during the search.
Subject MTS Identifier
The search will be processed within messages containing the given subject MTS
identifier.
Content Identifier
The search will be processed within messages containing the given content identifier.
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).

 Avitech GmbH 2018 Page 415 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Reported Recipient Information


The search will look at the details set in the reported recipient information of the
message.
Actual Recipient Name
The search will be processed within messages containing the given actual
recipient name.
Delivery Time
The search will be processed within messages which delivery time is
comprised within the selected time range.
Type of MTS User
The search will be processed within messages containing the selected type of
MTS user.
Non-Delivery Reason Code
The search will be processed within messages containing the selected non-
delivery reason code.

11.1.4.5.4 The Probe tab

This tab allows the operator to set search criteria for message of the type Probe. To be able
to make changes in the criteria of this tab the operator has to tick the checkbox next to the
tab name. If the checkbox next to the tab name is not ticked the criteria set in this tab will not
be taken into account during the search.
The Probe Tab is composed of two sub tabs:
• The Probe Details sub-tab
• The Submission Result sub-tab

 Avitech GmbH 2018 Page 416 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.4.5.5 Sub-tabs

11.1.4.5.5.1 The IPM Details sub-tab

This tab allows the operator to set search criteria for IPM details of message of the type
PLAIN. To be able to make changes in the criteria of this tab the operator has to tick the
checkbox next to the tab name. If the checkbox next to the tab name is not ticked the criteria
set in this tab will not be taken into account during the search.
ATS Priority
The search will be processed within messages containing one of the selected ATS
priority(ies).
Filing Time
The search will be processed within messages which filing time is comprised within
the selected time range.
Importance
The search will be processed within messages of one of the selected importance
level.
OHI
The search will be processed within messages containing the given optional heading
information.
IPM Originator
The search will be processed within the messages containing the given originator
address. No wild card can be used within this field
It is possible to enter the 8 letters of an AFTN address in this field when using wild
cards before and after the AFTN address string.
IPM Identifier
The search will be processed within messages containing the given IPM Identifier.

 Avitech GmbH 2018 Page 417 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Subject
The search will be processed within messages containing the given subject.
Body Text
The search will be processed within the messages containing the body text entered
here.
Attachments (bytes)
The search will be processed within the messages containing attachments which size
is comprised in the range selected. Each attachment will be checked separately.
Ipm Recipients
The search will look at the details set for each recipient of the messages.
Type
The search will be processed within the messages containing Ipm recipients
with the selected type(s)
• To
• CC
• BCC
O/R Address
The search will be processed within the messages containing Ipm recipients
with the given OR address.
It is also possible to enter the 8 letters of an AFTN address in this field when
using wild cards before and after the AFTN address string.
Notification Request
The search will be processed within the messages containing Ipm recipients
with the selected notification report(s)

11.1.4.5.5.2 The Ipn Details sub-tab

 Avitech GmbH 2018 Page 418 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

This tab allows the operator to set search criteria for Ipn details of message of the type Ipn.
To be able to make changes in the criteria of this tab the operator has to tick the checkbox
next to the tab name. If the checkbox next to the tab name is not ticked the criteria set in this
tab will not be taken into account during the search.
Ipn Originator
The search will be processed within the messages containing the given Ipn originator
address.
Ipn-Intended Recipient
The search will be processed within the messages containing the given Ipm-intended
recipient address.
Subject Ipm-Identifier
The search will be processed within messages containing the given subject Ipm-
identifier.
Converted Encoded Information Types
The search will be processed within messages containing the given converted
encoded information types.
Receipt Information
The search will look at the details set in the receipt information of the message.
Receipt Time
The search will be processed within messages which receipt time is
comprised within the selected time range.
Acknowledge Mode
The search will be processed within the messages containing the selected
acknowledge mode.

11.1.4.5.5.3 The Probe Details sub-tab

 Avitech GmbH 2018 Page 419 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

This tab allows the operator to set search criteria for details of message of the type Probe.
To be able to make changes in the criteria of this tab the operator has to tick the checkbox
next to the tab name. If the checkbox next to the tab name is not ticked the criteria set in this
tab will not be taken into account during the search.
Content Length
The search will be processed for probe messages with content length in the given
range.
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).
Content Identifier
The search will be processed within messages containing the given content identifier.
Envelope Originator
The search will be processed within messages containing the given envelope
originator.
Implicit Conv.
The search will be processed within messages containing or not containing "implicit
conversion prohibited".
Conv. w. loss
The search will be processed within messages containing or not containing
"conversion with loss prohibited".
Disclosure
The search will be processed within messages containing or not containing
"disclosure of other recipient Allowed".
Altn. Recip.
The search will be processed within messages containing or not containing "alternate
recipient allowed".
DL Exp.
The search will be processed within messages containing or not containing "delivery
list expansion prohibited".
Cont. Ret.
The search will be processed within messages containing or not containing "report
content return request".
Reassignm.
The search will be processed within messages containing or not containing "recipient
reassignment prohibited".

 Avitech GmbH 2018 Page 420 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Latest delivery
The search will be processed within messages which latest delivery time is comprised
within the selected time range.
Envelope Recipients
Address
The search will be processed within messages containing the given recipient
name
Originator Report Request
The search will be processed within messages containing the selected
originator report request.

11.1.4.5.5.4 The Deliv. Envelope sub-tab

This tab allows the operator to set search criteria for the delivery envelope of message of the
type PLAIN. To be able to make changes in the criteria of this tab the operator has to tick the
checkbox next to the tab name. If the checkbox next to the tab name is not ticked the criteria
set in this tab will not be taken into account during the search.
X.400 Priority
The search will be processed within messages containing one of the selected X.400
priority(ies).
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).

 Avitech GmbH 2018 Page 421 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Content Identifier
The search will be processed within messages containing the given content identifier.
MTS Identifier
The search will be processed within messages containing the given MTS identifier.
Envelope Originator
The search will be processed within messages containing the given envelope
originator.
Envelope Recipients
The search will be processed within messages containing the given envelope
recipients.
Delivery Time
The search will be processed within messages which delivery time is comprised
within the selected time range.
Implicit Conv.
The search will be processed within messages containing or not containing "implicit
conversion prohibited".
Conv. w. loss
The search will be processed within messages containing or not containing
"conversion with loss prohibited".

11.1.4.5.5.5 The Subm. Envelope sub-tab

This tab allows the operator to set search criteria for the submission envelope of message of
the type PLAIN. To be able to make changes in the criteria of this tab the operator has to tick
the checkbox next to the tab name. If the checkbox next to the tab name is not ticked the
criteria set in this tab will not be taken into account during the search.

 Avitech GmbH 2018 Page 422 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

X.400 Priority
The search will be processed within messages containing one of the selected X.400
priority(ies).
Original Encoded Information Types
The search will be processed within messages containing the given original encoded
information types.
Content Type
The search will be processed within messages containing the selected content
type(s).
Content Identifier
The search will be processed within messages containing the given content identifier.
Envelope Originator
The search will be processed within messages containing the given envelope
originator.
Implicit Conv.
The search will be processed within messages containing or not containing "implicit
conversion prohibited".
Conv. w. Loss
The search will be processed within messages containing or not containing
"conversion with loss prohibited".
Disclosure
The search will be processed within messages containing or not containing
"disclosure of other recipients".
Altn. Recip.
The search will be processed within messages containing or not containing "alternate
recipient allowed".
DL Exp.
The search will be processed within messages containing or not containing "delivery
list expansion prohibited".
Cont. Ret.
The search will be processed within messages containing or not containing "report
content return request".
Reassignm.t
The search will be processed within messages containing or not containing "recipient
reassignment prohibited".
Latest delivery
The search will be processed within messages which latest delivery time is comprised
within the selected time range.

 Avitech GmbH 2018 Page 423 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Envelope Recipients
Recipients Address
The search will be processed within messages containing the given recipient
name
Originator Report Request
The search will be processed within messages containing the selected
originator report request.

11.1.4.5.5.6 The Submission Result sub-tab

This tab allows the operator to set search criteria for the submission results of message of
the type PLAIN. To be able to make changes in the criteria of this tab the operator has to tick
the checkbox next to the tab name. If the checkbox next to the tab name is not ticked the
criteria set in this tab will not be taken into account during the search.
Submission Time
The search will be processed within messages which submission time is comprised
within the selected time range.
MTS Identifier
The search will be processed within messages containing the given MTS identifier.

 Avitech GmbH 2018 Page 424 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.5 The AFTN Channel Configuration

The AFTN Channel configuration function enables the operator to display the settings of the
channel configured in the Message Office.

11.1.5.1 Functions

11.1.5.1.1 File

Reload
Reloads the data from the last saved state.
Save
Saves the configuration.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic skills.

 Avitech GmbH 2018 Page 425 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Close
Closes this unit.

11.1.5.2 Fields
The AFTN Channel configuration is divides in 4 tabs:
• The General Settings tab
• The Channel Check Settings tab
• The SVC Settings tab
• The TCP Device tab

11.1.5.3 The General Settings tab

Channel name
The name of the channel.
Max Text length
The maximum number of characters allowed to be handled within a message.
Message Format
The message format with which messages will be transmitted on this channel.
• IA5
• ITA2
Originator
The AFTN address of the channel.
Current State
The current state of the channel
• ACTIVE
• INACTIVE

 Avitech GmbH 2018 Page 426 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Initial State
The initial connection state of the channel:
• UNKNOWN
• DISCONNECTED
• CONN_BY_HOST
• CONN_BY_REMOTE
Activation Date
The date and time when the Channel was last activated.
CID
Defines the channel identifier for outgoing messages.
CSN digits
The length (number of digits) of the channel sequence number (CSN)
CSN Rx
The current channel sequence number for the reception side
CSN Tx
The current channel sequence number for the transmission side
Alignment
The contents of the alignment function. This is used when composing the header
information for outgoing messages. For incoming messages both alignment types are
accepted.
• CR_LF
• CR_CR_LF
Conveyance Type
Defines whether the communication between the AFTN switch and the device uses
the protocol according to Annex 10/II completely ("MTP"), partly ("GEN").
• MTP
• GEN
Working Method
Specifies how incoming messages have to be handled.
• SVC
• CONF
• IMA1
• IMA2

 Avitech GmbH 2018 Page 427 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Enq / Answerback Settings


Use
Defines whether or not the system inquires the answerback string on this
channel.
Answerback
This entry contains the answerback string expected to be received on this
channel when inquired by the system.
Use Empty Message Procedure
Enable the empty message procedure to establish a connection.
Midnight tolerance
Time in minutes during which the midnight reset of the CSN for incoming messages
will not trigger any SVC message.
Retention Time
The number of days the messages will be retained by the system.

11.1.5.4 The Channel Check Settings tab

Mode
Defines whether the system shall send and expect periodic channel check messages
on the channel or not.
Tx Period
The time in minutes between two outgoing channel check messages
Rx Period
The time in minutes between two incoming channel check messages
Tolerance
Sets the tolerance (in minutes) for early and late incoming channel check messages.
Send Extra CHCK
If this checkbox is ticked an extra channel check message will be sent at midnight.

 Avitech GmbH 2018 Page 428 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Adjust System Clock By Midnight CHCK


If this checkbox is ticked the system clocked will be adjusted when receiving the
midnight channel check message.

11.1.5.5 The SVC Settings tab

Previous station
The AFTN address of the previous station. This AFTN address will be used when the
system generates an SVC message.
Generate SVC
If this checkbox is ticked SVC messages will be generated automatically.
SVC Priority
Defines the priority of the automatically generated SVC messages.
Max allowed CSN gap
Define the max value for the gap in CSN numbers that will be handled automatically.
Handle SVC QTA MIS
If this checkbox is ticked incoming SVC QTA MIS messages will be handled
automatically.
Handle SVC QTA RPT <TID>
If this checkbox is ticked incoming SVC QTA RPT <TID> messages will be handled
automatically.
Handle SVC QTA RPT <OGN>
If this checkbox is ticked incoming SVC QTA RPT <OGN> messages will be handled
automatically.

 Avitech GmbH 2018 Page 429 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.5.6 The TCP Device tab

Name
The name of the device.
Direction
The direction of the device.
• OFF
• IN
• OUT
• BOTH
Server
The network address of the server.
Call Wait Time
The time in milliseconds the application will wait after successful connection
establishment.
Local Port
The port number on the local machine
Remote Port
The port number on the remote machine
Ping Settings
Use
If this checkbox is ticked, connections will be supervised by ping.
Ping Interval
The interval in milliseconds between two consecutive ping transmissions

 Avitech GmbH 2018 Page 430 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Failure Threshold
The threshold value for unsuccessful ping transmissions after which the
connection will be considered as broken.
Close on failure
If this checkbox is ticked, the connection will be reset if the number of
unsuccessful ping transmissions exceeds the threshold value.
Keep Alive settings
Use
If this checkbox is ticked, connections will be supervised by Keep-Alive.
Keep Alive Time
Idle time in milliseconds after which the Keep-Alive will be started.
Keep Alive Interval
The interval in milliseconds between two consecutive Keep Alive
transmissions.
Failure Threshold
The threshold value for unsuccessful Keep Alive transmissions after which the
connection will be considered as broken.

11.1.6 The AMHS Channel Configuration

The AMHS channel configuration allows the administrator to modify AMHS the channel.
Note: Always restart the client on which a channel is running after modification.
The AMHS channel configuration is divided in two tabs:
• The General Settings tab
• The MTA Device tab

 Avitech GmbH 2018 Page 431 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.6.1 Functions

11.1.6.1.1 File

Reload
Reloads the last saved channel data
Save
Saves the current AMHS channel. This is only possible if the AMHS channel has
already been named with the Save As function.
Print
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Choice
Opens the print function to enable the choice of the printer on which the printout will
be done.
Close
Closes the unit.

11.1.6.2 The General Settings tab

Channel Name
The name of the channel. This is a read only field.
Activation Date
The date and time when the Channel was last used from a client. This is a read only
field.

 Avitech GmbH 2018 Page 432 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Session Type
Type of connection to the MTA.
• P3: MTS (message transfer system) access protocol. The user agent is
directly connected to the MTA
• P7: MS (message store) access protocol. The user agent is connected to the
MTA via a message store.
O/R Address
The O/R Address of the channel. According to the addressing scheme chosen the
syntax used for the O/R address is different.
Message Quota [kB]
The maximum volume (in kB) of the message texts sent within the retention time.
Used Message Quota [kB]
Volume (in kB) the files attached message texts sent within the retention time already
used.
Alignment
The contents of the alignment function to be used with this channel.
• CR_LF
• CR_CR_LF
Retention Time
The number of days the messages will be retained before automatic deletion.
Attachment Quota [kB]
The maximum volume (in kB) of the files attached sent within the retention time.
Used Attachment Quota [kB]
Volume (in kB) of the files attached sent within the retention time already used.
Initial State
The initial connection state of the channel.
• CONN_BY_HOST: The connection is automatically initiated by the host
server.
• DISCONNECTED: The channel is disconnected.
Current State
The current state of the channel. This is a read only field.
• ACTIVE
• INACTIVE

 Avitech GmbH 2018 Page 433 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.6.3 The MTA Device tab

Name
The name of the MTA device used with this channel. This is a read only field.
Direction
The direction of the MTA device
• OFF
• IN
• OUT
• BOTH
Server /MTA
The network address of the MTA Server.
[...]-button
Opens the following dialog to configure the presentation address.

Selectors
Presentation
The presentation selector (PSEL)
Session
The session selector (SSEL)
Transport
The transport selector (TSEL)

 Avitech GmbH 2018 Page 434 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Network
Server
The server IP address of symbolic name.
Port
The TCP port number
Password
The password to authenticate towards the MTA.
Connection Check Settings
Use
If this checkbox is ticked, cyclic connection checks will be used.
Interval
The interval in milliseconds between two connection checks.

11.1.7 Autoprocess Profiles

The Autoprocess Profiles function enables the operator to process automatically messages
after they have spent a given time in the unprocessed folder of the Message Office.

11.1.7.1 Functions

11.1.7.1.1 File

New
Clears the fields.

 Avitech GmbH 2018 Page 435 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Load
Loads a route part.
Save
Saves the current route part.
Save As
Saves the current route part under a new name.
Delete
Deletes the current route part.
Close
Closes this unit.

11.1.7.2 Fields
Name
Name of the profile
Active
States if the profile is the active one or not.
Note: only one profile can be active at a given time.
Last changed
The date and time when the profile was last modified.
Channel
Name of the channel on which the auto-process rule applies.
Lifetime (min)
Recurrence in minutes for the auto-process rule.
Filter
Filter applied to the auto-process rule. The filter has to be a stored search constraint.
If nothing is set in this field, all unprocessed messages will be transferred to the
processed folder after the time set in the Lifetime field.

 Avitech GmbH 2018 Page 436 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.8 Online Message Monitor


The Online allows the operator to monitor when messages are sent or received by his / her
Message Office.

11.1.8.1 Functions

11.1.8.1.1 File

New
Clears the Message Monitoring.
Start monitoring
Starts the monitoring.
Stop monitoring
Stops the monitoring.
Close
Closes the Online Message Monitor.

 Avitech GmbH 2018 Page 437 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.8.1.2 Options

Show Toolbar
Displays or hides the toolbar.
Filter
Opens the filter chooser.
Filters are stored search parameters. The filter names and parameters therefore
correspond to the folders that can be found under the Search node.
To change the parameters of the message monitoring filter, the operator shall change
the parameters of the corresponding search folder.
Clear Filter
Clears the display filter.
Enlarge Font (Ctrl +)
Enlarges the font of the Message Monitoring. This will occur at the next message
received or sent.
Shrink Font (Ctrl -)
Shrinks the font of the Message Monitoring. This will occur at the next message
received or sent.
Autoprint
If this checkbox is ticked the messages displayed on the online message monitor will
automatically be printed out.
Note: To enable the auto-print function the printer has to be a matrix
printer with endless paper and has to be defined as the standard printer
of the PC.

11.1.8.2 The message monitoring


This is the main part of the Online Message Monitor, it displays the following parameters
concerning the message:
• The direction: transmitted or received
• The type of message: PLAIN, NOTAM, FPL, DEP...
• The date and time
• The priority
• The date time group

 Avitech GmbH 2018 Page 438 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• The AFTN address of the originator


• The addressees
• The subject, if any
• The text

11.1.9 AFTN Viewer

11.1.10 AFTN Viewer


A double click on a PLAIN message in the Message Office opens the AFTN Viewer.

 Avitech GmbH 2018 Page 439 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.10.1 Functions

11.1.10.1.1 File

Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic skills.
Acknowledge
Creates and sends a receipt notification. This function is only active for messages
with Priority SS for which no receipt notification has yet been sent.
Reply to
Create a reply message with the address of the sender of the selected message.
Reply all
Create a reply message with the address of the sender and the addresses of all
recipients of the selected message.
Close
Closes the AMHS Viewer

11.1.10.1.2 Options

Displays or hides the toolbar.

11.1.10.2 Fields
TID
The first field represents the Message Transmission Protocol Identifier (MTP-ID).
It is inserted automatically when the user opens a message or creates a new
message. The MTP-ID must consist of exactly 3 alpha characters (A...Z).
This field is mandatory.
Example: SPD

 Avitech GmbH 2018 Page 440 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The second field represents the Channel Sequence Number. It is inserted


automatically when the user opens a message or creates a new message. The CSN
number consists of 3 or 4 digits depending on the configuration of the application.
DTG
According to ICAO Aeronautical Telecommunications – Annex 10, the AFTN heading
line leaves space for the 'Additional Service Indication' following the transmission
identifier. The application makes use of this field in form of inserting 'Day Time Group'
information. The DTG is inserted automatically based on the current system time
when transmission of the message occurs. The format of the DTG is specified as
'ddHHmmss'.
This field is mandatory.
Example: 07011700
Priority
The AFTN priority indicator is shown as a combo-box that offers all valid AFTN
priorities for input.
Addresses
In the address area of the AFTN form 21 addresses are displayed. The contents of
the destination address(es) field(s) will be checked for valid input. A valid input
consists of 8 IA5 uppercase letters.
This field is mandatory.
Example: EGGGYNYX
Filing Time
The Filing Time is automatically updated by the system when the message is sent,
the current time will then be inserted by the system. The format of the Filing Time is
specified as 'ddHHmm'.
This field is mandatory.
Example: 070105
Originator
The Originator address (8 IA5 uppercase letters) is automatically inserted by the
system. Every user with privilege free text has an assigned AFTN address, which is
used as originator address when sending AFTN messages.
This field is mandatory.
Example: EGGGYAYA
Optional Heading Information
The Optional Heading Information according to ICAO, Annex 10, amendment 71, is
specified as information that can be added to fill up the remainder of the Origin Line.
This means that it can carry up to 48 characters for messages of priority 'SS' and up
to 53 characters for all other messages. The allowed character set is the same as for
the message body.
This field is optional.
Example: ANY TEXT THE USER LIKES TO INSERT

 Avitech GmbH 2018 Page 441 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.10.3 AFTN Correction Position Viewer

The AFTN Correction Position Viewer is an AFTN Viewer with editable fields. It highlights the
errors that prevented the system to transmit the message and displays an error information
table at the bottom of the unit.
The operator can execute the corrections inside the AFTN Correction Position Viewer and
send the corrected message.

 Avitech GmbH 2018 Page 442 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.10.3.1 Specific functions

11.1.10.3.1.1 File

Show Message Trace


Displays the trace of the message
Show original message
Displays the original erroneous message
Revert to original
Discards all changes
Send the corrected message
Sends the corrected message
Send message
Sends the message

11.1.10.3.1.2 Options

Show special characters


Displays the special characters contained in the message.

 Avitech GmbH 2018 Page 443 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.11 The AMHS Viewer unit


A double click on a PLAIN message in the Message Office opens the AMHS Viewer.

Some fields in the Details tab and the whole Traces tab depend on the kind of message
viewed: transmitted or received.
The AMHS Viewer is composed of three different tabs:
• The Message tab of the AMHS Viewer
• The Details tab of the AMHS Viewer
• The Traces tab of the AMHS Viewer
If a file has been attached to the message, a fourth tab is displayed: The File tab of the
AMHS Viewer

 Avitech GmbH 2018 Page 444 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.11.1 Functions

11.1.11.1.1 File

Acknowledge
Creates and sends a receipt notification. This function is only active for messages
with Priority SS for which no receipt notification has yet been sent.
Reply to
Create a reply message with the address of the sender of the selected message.
Reply all
Create a reply message with the address of the sender and the addresses of all
recipients of the selected message.
Forward
Create a message with the contents of the Subject and of the body of the selected
message.
Print Choice
Prints the current contents of the form. To use this functionality the form does not
need to be completely filled out. For more information about this function, please refer
to the section Printing mechanism of the chapter Basic skills.
Print Preview
Opens a new window which shows the current contents of the form as it would
appear if it were printed out. To use this functionality the form does not need to be
completely filled out. For more information about this function, please refer to the
section Printing mechanism of the chapter Basic skills.
Close
Closes the AMHS Viewer

11.1.11.1.2 Options

Show Toolbar
Displays or hides the toolbar.

 Avitech GmbH 2018 Page 445 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

AFTN Style Address Display


Switches the view of addresses for AMHS to AFTN and vice versa.

11.1.11.2 The Message tab of the AMHS Viewer


All fields of the AMHS viewer are Display only.

ATS Prio
The ATS Priority Indicator of the AMHS message.
Filing Time
The Filing Time of the AMHS message. The format of the Filing Time is specified as
'ddHHmm'
OHI
The Optional Heading Information of the AMHS message.
Originator
Address of the originator of the message.

 Avitech GmbH 2018 Page 446 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Recipients
The addressees of the AMHS message.
A right mouse click in this field makes the following context window appear:

The operator can then choose to:


• Show the details for the selected address
• Translate all addresses from AMHS to AFTN and vice versa.
Subject
The subject of the AMHS message.
Message Text
The body of the AMHS message.
The Details window
The details window shows some detail settings for the selected address.

11.1.11.3 The Details tab of the AMHS Viewer


All fields of the AMHS viewer are Display only.
Received messages

 Avitech GmbH 2018 Page 447 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Transmitted messages

IPM Identifier
The Interpersonal Message Identifier. It is a unique identifier automatically given by
the User Agent. This identifier is part of the Header of the message.
MTS identifier
The Message Transfer Service Identifier. It is automatically given by the MTA. It will
be used in Reports in order to refer to the subject message.
Priority
The transfer priority of the AMHS message. This indicator is on the envelope of the
message. It can have the following values:
• Non-urgent
• Normal
• Urgent

 Avitech GmbH 2018 Page 448 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Importance
This parameter is included in the header of the AMHS message. It shows the
recipient the importance the originator gives to the message. It can have the following
values:
• Low
• Normal
• High
Sensitivity
This parameter is for military use only. It can have the following values:
• Not sensitive
• Personal
• Private
• Company-confidential
Reception time
The timestamp the application has given to the message by the time of the reception.
Note: This field is only in the AMHS Viewer for received messages.
Delivery time
The date and time of the delivery of the message
Note: This field is only in the AMHS Viewer for received messages.
Transmission Time
The timestamp the application has given to the message by the time of the
transmission.
Note: This field is only in the AMHS Viewer for transmitted messages.
Submission Time
The date and time at which the AMHS message was delivered.
Note: This field is only in the AMHS Viewer for transmitted messages.
Deferred Delivery Time
The date and time until when the MTS defers the delivery of the message.
Note: This field is only in the AMHS Viewer for transmitted messages.
Reply Time
The date and time until when the recipient can reply to the message.
Latest Delivery Time
The date and time until when the message shall be delivered. If the message has not
been delivered until then, it will be erased.
Note: This field is only in the AMHS Viewer for transmitted messages.
Expiry Time
The date and a time until when the message is valid.

 Avitech GmbH 2018 Page 449 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Envelope Originator Address


The address of the originator of the AMHS message envelope.
Originator Return Address
The originator return address.
Content Type
The content standard used.
Content Identifier
Identifier automatically given by the User Agent. It will be used in Reports.
Encoded Information Types
The code type of the information contained in the message.
Additional Mail Properties
Alternate Recipient Allowed
Determines whether or not the MTA can send the message to the alternate
recipient if the addressee is not reachable.
Note: This field is only in the AMHS Viewer for transmitted
messages.
Conversion With Loss Prohibited
Determines whether or not the MTA is allowed to convert the text in another
format without any loss of the contents.
Disclosure of Other Recipients Allowed
Determines whether or not the O/R addresses of other recipients are to be
indicated to each recipient at delivery.
Note: This field is only in the AMHS Viewer for transmitted
messages.
DL Expansion Prohibited
Determines whether or not the MTA is allowed to expand an address in a
delivery list and send the message to all of its subscribers if it recognizes one
as such and not as a unique address.
Note: This field is only in the AMHS Viewer for transmitted
messages.
Implicit Conversion Prohibited
Determines whether or not the MTA is allowed to convert the text in another
format.
Receipt Reassignment Prohibited
Determines whether or not the originator prohibits the intended recipients from
redirecting the submitted message.
Note: This field is only in the AMHS Viewer for transmitted
messages.

 Avitech GmbH 2018 Page 450 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.11.4 The File tab of the AMHS Viewer


All fields of the AMHS viewer are Display only.
The File tab is only displayed in the AMHS Viewer if the viewed message has an attached
file.
A double click on an attached file opens it.

Name
Name of the file.
Size
Size of the file.

 Avitech GmbH 2018 Page 451 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.1.11.5 The Traces tab of the AMHS Viewer


All fields of the AMHS viewer are Display only.
The Traces tab is only displayed in the AMHS Viewer for received messages.

Trace Information
Information about the own domain.
Internal trace Information
Information about each MTA through which the message was transmitted.

 Avitech GmbH 2018 Page 452 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.2 The Message Office unit


The Message Office is used to monitor messages which have been sent and received by the
current operator.

It is divided in 3 parts:
• The channel tree of the Message Office.
• The message table of the Message Office.
• The message preview of the Message Office.

11.2.1 The channel tree of the Message Office

 Avitech GmbH 2018 Page 453 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

11.2.1.1 The ID node


At the top of the left hand pane a node with the ICAO address assigned to the operator
logged in is displayed.
An icon on this node shows if the connection is up or down:
Connection up

The icon is green.


Connection down

The icon is red.


Note: the icon remains red until the Message Office receives a new
message, or the operator goes online.

,
A left mouse click on the connection icon opens a context menu that allows the operator to
switch the channel connection to online or to offline.
From this pane it is possible to see all messages sent and received by this ICAO address.
The messages received are sorted in 3 folders within the node with the operator's ICAO
address. These folders are the status of the message: Unprocessed, Processed and
Transmitted. In the Processed and in the Transmitted folders the messages are sorted in
new sub-folders, the name of which is a date in the format Year, Month and Day. The newest
date always situated at the top of the list. The number of days displayed is configurable by
the administrator.

Clicking on the latch symbol of a folder will expand it to show all dates for that status.

 Avitech GmbH 2018 Page 454 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

All messages received appear at first in the Unprocessed folder. Once they have been read
they will be moved automatically into the Processed folder.
Messages sent by this ICAO address will be placed in the Transmitted folder. Next to each
of these folder names is a number showing how many messages are contained in each
folder.
If more than one channel is configured each configured channel will be displayed as
separate node in the channel tree.

11.2.1.2 The Correction Position node


The XCORRPOS node is the correction position. The operator can execute the following
functions:
• receive and inspect incorrect messages
• correct and send messages
• delete messages which cannot or shall not be corrected
• split oversized messages,
• inspect and delete messages received by CIDIN

11.2.1.3 The Search node


Below the XCORRPOS node is the Search node. It has a folder in which the search results
of an unsaved search will be displayed. Further folder will be displayed if the user saves the
settings of a search with the Save Search Constraints button or action in the Search File
menu.
Selecting a folder in the Search node and clicking on the right mouse button opens the
context menu in which the user can:
• Edit the search parameters.
• Delete the folder.

 Avitech GmbH 2018 Page 455 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

• Clear the search results in the selected folder.


• Execute the search with the existing parameters.
Note: the Search Result folder cannot be deleted.
For more information about the search function, please refer to the section The search
function of this chapter.

11.2.1.4 The User Area node


Below the Search node is the User Area node. This node is where the operator can create
folders and organize messages as it best suits his / her needs. Messages received and
stored in the ID node cannot be deleted nor moved but they can be copied into the User Area
node using the drag and drop function. Here the copies can be organized into useful groups
and deleted when they are no longer needed.
Selecting the Display Area node or a folder of the Display Area and clicking on the right
mouse button opens the context menu in which it is possible to add, delete or rename a
folder.
Note: The node User Area cannot be renamed nor removed.
To delete one message in the message Area the user has to select the message and click
on the [Delete]-button or select the Delete function in the File menu.

11.2.2 The message table of the Message Office

Selecting a folder in the channel tree of the Message Office will display the contents of that
folder in the message table.
The items in this table can be ordered by any of the column headers simply by clicking on
that header with the mouse.
The order in which the columns are displayed can be changed by changing the column order
in the Select Columns window of the Options menu. In this menu it is also possible to add or
remove some columns.
Messages in this table can be opened in different ways:
• A single click on a message displays the contents in the message preview of the
Message Office.
• A double click on a message displays the message in the AMHS Viewer unit if it is a
PLAIN text message and in the corresponding form when the message format has
been recognised.
• A right mouse click on a message will produce a list of forms appropriate for the
display of that message.

 Avitech GmbH 2018 Page 456 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

The columns in this table are the following:


APrio
AFTN Priority.
Changed by
Name of the operator who changed the message.
Changed on
Date when the message was changed.
Created
Date and time when the message was created.
From
Address of the originator.
ID
Internal identifier of the message.
Info
Information symbols concerning the message:
• Reply to
• Reply All
• Forward
• Attachment
Message text
Text of the message.
Subject
Subject of the message if any.
Status
The status of the message.
In the ID node, the additional channel nodes, the search node and the user area
node, a message can have the following status:

Status Meaning

O Transmitted: The message has been transmitted successfully.

P Processed: The received message has been processed.

U Unprocessed: The received message is still unprocessed.

X Unsent: The message has not yet been transmitted. This status exist in the short
period of time between the moment the operator has clicked on the [Send]-button
and the moment the message has been totally processed by the system.

 Avitech GmbH 2018 Page 457 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

In the XCORRPOS node a message can have the following status:

Status Meaning

U Unread: The message has arrived to the correction position but has not yet been
read.

R Read: The message has arrived to the correction position has been read, but has not
yet been corrected.

C Corrected: The message has been corrected.

Timestamp
delivered time.
To
Address of the first recipient.
Type
Message type such as PLAIN, FPL, DEP, NT, SW...

11.2.3 The message preview of the Message Office

This pane displays the message selected in the message table of the Message Office.
A set of headings appear here, they are described below:
Type
Message type such as PLAIN, FPL, DEP, NT, SW...
Received
The date and time the message was received.
ATS Prio.
The ATS priority assigned to the message.
Filing Time
The time at which the message was received by the AFTN handler, expressed as
Day Hour Minute.

 Avitech GmbH 2018 Page 458 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

OHI
The Optional Header Information attached to the message.
X.400 Prio.
The X.400 priority assigned to the message.
Importance
The X.400 importance assigned to the message.
Sensitivity
The X.400 Sensitivity assigned to the message.
Delivered
The date and time of the message delivery.
Reply until
Maximum date and time of a needed reply.
Expires
Expiration date and time of the message.
Subject
Subject of the message.
Recipients
The addresses of the recipient to whom this message was addressed.
Text
The message contents.

 Avitech GmbH 2018 Page 459 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

12 OPTIONS MENU
The Options menu allows the user to enable or disable of the tool tips as well as to show or
hide the menu icons of all frames.

Enable Tool Tips


Ticking this check box enables the display of the tool tips in all frames.

 Avitech GmbH 2018 Page 460 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

13 WINDOW MENU
The Window menu helps the user to control all open windows at once.

Close All
Closes automatically all units open.
Minimize All
Minimizes automatically all units open.
Restore All
Restores automatically all units minimized.
Pack All
Restores the original size of all units open.

 Avitech GmbH 2018 Page 461 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

14 HELP MENU
The Help menu provides a general help file and a context sensitive help.

Launch Help
Launches the general help file. The help is not displayed in the MDI schema. The
help frame can be moved out of the AviTerm framework. So it is possible to work with
the system and have in parallel the help file open.
'?' - Context sensitive help
Changes the mouse cursor into a question mark. Clicking then in the HMI will open
the general help file next to the topic of the item that was clicked on.
Note: the context sensitive help shall only be used on active fields in
active windows.
About
Gives information about the copyright and the current version number of the
application.

 Avitech GmbH 2018 Page 462 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

ANNEX A ABBREVIATIONS
The following list shows the standard abbreviations of Avitech. They may not all appear in
this document.

Abbreviation Meaning

ACFT Aircraft

ACK Acknowledgement

acu AIS Centre Unit

AD Aerodrome

ADDR Address List

AFTN Aeronautical Fixed Telecommunications Network

AIP Aeronautical Information Publication

AIS Aeronautical Information Service

ALTN Alternate

AMHS ATS Message Handling System

AO Aircraft Operator

ARO Aeronautical Reporting Officer

ARR Arrival

ASHTAM NOTAM reporting (volcanic) Ash hazard

ATA Actual Time of Arrival

ATD Actual Time of Departure

ATS Air Traffic Services

atu AIS Terminal Unit

BIRDTAM NOTAM reporting Bird hazard

BRG Angle of the Arc

CHG Change

CNL Cancellation

CFL Current Flight Plan

 Avitech GmbH 2018 Page 463 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Abbreviation Meaning

CTOT Calculated Take-Off Time

DEP Departure

DEST Destination

DLA Delay

DOF Date of Flight

DTG Date and Time Group

EAD European AIS Database

EET Estimated Elapsed Time

EOBT Estimated Off Block Time

EST Estimated

ETA Estimated Time of Arrival

ETD Estimated Time of Departure

FIR Flight Information Region

FPL Flight Plan

HHMM Hours, 2 digits - Minutes, 2 digits

HMI Human Machine Interface

IATA International Air Transport Association

ICAO International Civil Aviation Organization

ID Identification

IFR Instrument Flight Rules

INB Inbound Flight Plan

INTM Intermediate

IOBD Initial Off Block Date

IOBT Initial Off Block Time

IPM Interpersonal Message

IPN Interpersonal Notification

 Avitech GmbH 2018 Page 464 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Abbreviation Meaning

IR Information Region

LOV List of Values

mcu MHS Center Unit

MDI Multiple Document Interface

METAR Meteorological aerodrome routine Weather Report

MHS Message Handling System

MSG Message

MTA Message Transfer Agent

MTS Message Transfer Service

MTOW Maximum Take Off Weight

mtu MHS Terminal Unit

NBARC Number of Arriving Aircrafts

NOF NOTAM Office

NOTAM Notice to Airmen

NOTAMC Cancel NOTAM

NOTAMN New NOTAM

NOTAMR Replacement NOTAM

OHI Optional Header Information

PERM Permanent

PIB Pre Flight Information Bulletin

PTOT Provisional Take-Off Time

RQP Request Flight Plan

RQS Request Supplementary Information

RVR Runway Visual Range

RWY Runway

SIGMET Significant Meteorological Weather Phenomena

 Avitech GmbH 2018 Page 465 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Abbreviation Meaning

SNOWTAM NOTAM reporting ice or snow related hazard

SPL Supplementary Information

TAF Terminal Aerodrome Forecast.

TID Terminal Identification Number

UA User Agent

UIR Upper Information Region

UTC Universal Time Coordinated

UTM Universal Transverse Mercator

VFR Visual Flight Rules

YYMMDD Year, 2 digits - Month, 2 digits - Day, 2 digits

 Avitech GmbH 2018 Page 466 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

ANNEX B KEYBOARD MAPPING


Except for the list of values, the keyboard shortcuts used in the AviTerm application are the
shortcuts used within Java.

B.1 List of values


Some fields are linked to a list of value. They can react in two different manners:
Open a list of value chooser

Fields having a blue square in the upper left corner will open a list of value chooser
when the operator places the cursor in one of these fields and presses the [F4]-key.
After having chosen a value the operator has to leave the field so that the system
can fill out the related fields.
Open a finder

Fields having a grey triangle in the upper left corner when the cursor is in them will
open a finder when the operator presses the [F4]-key.
It is possible to start filling up the field and then pressing on the [F4]-key. This will
result in opening a finder with a reduced list of possible entries. The use of the "%"
character as a wildcard is also allowed.
After having chosen a value the operator has to leave the field so that the system
can fill out the related fields.

B.2 Java shortcuts

B.2.1 JApplet - Inside an AviUnit (Java L&F)


Action Key sequence

Navigate out forward Tab, Ctrl + Tab

Navigate out backward Shift + Tab, Shift + Ctrl + Tab

Activate the default button (if Enter


defined)

 Avitech GmbH 2018 Page 467 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.2 Standard components

B.2.2.1 JButton (Java L&F)


This button comes to its original position after having been clicked on or having been
selected. All the Icons under the menu bar are JButtons.

Action Key sequence

Navigate forward Tab

Navigate backward Shift + Tab

Activate Default Enter

Activate Any Space bar, Alt + Char accelerator key (if defined)

Activate Cancel or Close Esc

B.2.2.2 JCheckBox (Java L&F)


This square box can be ticked or not ticked. All check boxes can be selected at the same
time.
,

Action Key sequence

Navigate forward Tab

Navigate backward Shift + Tab

Navigate within group Arrow keys

Check / Uncheck Space bar

B.2.2.3 JRadioButton (Java L&F)


Square or round box that can be ticked or not ticked. Only one radio button can be selected
at the same time.
,

Action Key sequence

Navigate forward Tab

Navigate backward Shift + Tab

 Avitech GmbH 2018 Page 468 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Navigate within group Arrow keys (Note: Navigating to a radio button selects it.)

Check / Uncheck Space bar

B.2.2.4 JToggleButton (Java L&F)


Button that stays in the position it was set.

Action Key sequence

Navigate forward Tab

Navigate backward Shift + Tab

Navigate within group Arrow keys

Check / Uncheck Space bar

B.2.2.5 JComboBox (Java L&F)


Drop down list in a field. Only one item can be selected in this list and only the selected item
can be seen in the field when the drop down list is closed.

Action Key sequence

Navigate out forward Tab

Navigate out backward Shift + Tab

Post menu Alt + Down

Retract menu Esc, Alt + Up

Toggle menu up Alt + Up

Toggle menu down Alt + Down

Activate menu item Enter

Jump to menu item without selecting Initial Char of Item (Only if the field is empty)
it

 Avitech GmbH 2018 Page 469 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Move up Up (Note: For other navigation keys, please see JList. For
more information on Edit Field, please see JTextField.)

Move down Down (Note: For other navigation keys, please see JList. For
more information on Edit Field, please see JTextField.)

B.2.2.6 JList (Java L&F)


List in which more than one item can be seen and in which the selected item is marked

Action Key sequence

Navigate out forward Tab

Navigate out backward Shift + Tab

Activate selection Enter

Move within list Up, Down

Move to beginning of list Ctrl + Home

Move to end of list Ctrl + End

Select all entries Ctrl + A

Make a selection Space bar (Note: This will deselect previous selection)

Select an additional item Ctrl + Space bar

Range select Shift + Space bar

Extend selection up Shift + Up

Extend selection down Shift + Down

Extend selection to top Shift + Home

Extend selection to end Shift + End

Block extend up Shift + PgUp

Block extend down Shift + PgDn

Block move PgUp, PgDn

 Avitech GmbH 2018 Page 470 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.2.7 JSlider (Java L&F)


Slide Bar such as the picture below

Action Key sequence

Navigate out forward Tab

Navigate out backward Shift + Tab

Minimum value Home

Maximum value End

Block increase or increase value PgUp

Block decrease or decrease value PgDn

B.2.3 Structured components

B.2.3.1 JTable (Java L&F)


Table

Action Key sequence

Navigate out forward Tab

Navigate out forward Ctrl + Tab

Navigate out backward Shift + Tab

Navigate out backward Ctrl + Shift + Tab

Move to next cell Tab

Move to next cell Right Arrow

Move to previous cell Shift + Tab

Move to previous cell Left Arrow

Wrap to next row Tab

 Avitech GmbH 2018 Page 471 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Wrap to next row Right Arrow

Wrap to previous row Shift + Tab or Left

Block move vertical PgUp, PgDn

Block move left Ctrl + PgUp

Block move right Ctrl + PgDn

Block extend vertical Shift + PgUp, Shift + PgDn

Block extend left Ctrl + Shift + PgUp

Block extend right Ctrl + Shift + PgDn

Move to first cell in row Home

Move to last cell in row End

Move to first cell in table Ctrl + Home

Move to last cell in table Ctrl + End

Select all cells Ctrl + A

Deselect current selection Up, Down

Deselect current selection Ctrl + Up, Ctrl + Down

Deselect current selection PgUp, PgDn

Deselect current selection Ctrl + PgUp, Ctrl + PgDn

Deselect current selection Home, End

Deselect current selection Ctrl + Home, Ctrl + End

Extend selection one row Shift + Up, Shift + Down

Extend selection one column Shift + Left, Shift + Right

Extend selection to beginning of row Shift + Home

Extend selection to end of row Shift + End

Extend selection to beginning of Ctrl + Shift + Home


column

Extend selection to end of column Ctrl + Shift + End

 Avitech GmbH 2018 Page 472 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Edit cell without overriding current F2


contents

Reset cell content prior to editing Esc

B.2.3.2 JTree (Java L&F)


This is a hierarchy tree. It is usually located on the left part of the frame or of the window.

Action Key sequence

Navigate out forward Tab

Navigate out backward Shift + Tab

Expand entry Right

Collapse entry Left

Toggle expand / collapse for entry Enter

Move up one entry Up

Move down one entry Down

Move to first entry Home

Move to last visible entry End

Block move vertical PgUp, PgDn

Block move left Ctrl + PgUp

Block move right Ctrl + PgDn

Block extend vertical Shift + PgUp, Shift + PgDn

Select all Ctrl + A

Select all Ctrl + /

Deselect all Ctrl + \

 Avitech GmbH 2018 Page 473 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Single select Ctrl + Space bar

Range-select Shift + Space bar

Extend selection up Shift + Up

Extend selection down Shift + Down

Extend selection to start of data Shift + Home

Extend selection to end of data Shift + End

B.2.4 Menu, toolbar, and tooltip components

B.2.4.1 JMenuBar (Java L&F)


The whole menu line

Action Key sequence

Jump to menu bar Alt

Navigate out Esc, Alt

Navigate between items within Arrow keys


menu

Select first item (if no item selected) F10

Select next item Right

Select previous item Left

Select default or selected item Enter

Post menu Up, Down, Enter, Space bar, Alt + Char accelerator key (if
defined)

Un-post menu Esc, Alt

 Avitech GmbH 2018 Page 474 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.4.2 JMenu (Java L&F)


The different selectable menus

Action Key sequence

Post menu Enter, F10

Post submenu Right

Move to next item (wrap to top) Down

Move to previous item (wrap to Up


bottom)

Retract menu Esc

Retract submenu Left

Activate default or selected item Enter

B.2.4.3 JMenuItem (Java L&F)


The item of a menu

Action Key sequence

Navigate in / out Arrow keys

Activate item Enter, Space bar, Alt + Char accelerator key (if defined)

 Avitech GmbH 2018 Page 475 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Post submenu Right

Retract submenu Left, Esc

B.2.4.4 JCheckBoxMenuItem (Java L&F)


A check box as menu item

Action Key sequence

Navigate in / out Arrow keys

Check / Uncheck item and retract Enter


menu

B.2.4.5 JRadioButtonMenuItem (Java L&F)


A radio button as menu item

Action Key sequence

Navigate in / out Arrow keys

Check / Uncheck item and retract Enter


menu

 Avitech GmbH 2018 Page 476 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.4.6 JPopupMenu (Java L&F)


Context menu

Action Key sequence

Post menu Shift + F10

Post submenu Right

Close submenu Left

Retract menu Esc

Move within menu Up, Down

Activate entry Enter, Space bar

B.2.4.7 JToolBar (Java L&F)


Icons placed under the menu bar and that show the main functions of the different menus

Action Key sequence

Navigate out forward Tab

Navigate out backward Shift + Tab

Navigate within Arrow Keys

Activate item Space

 Avitech GmbH 2018 Page 477 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.4.8 JToolTip (Java L&F)


This is a small description window that appears when the mouse is placed on an icon, a field,
a button... without clicking on it. It cannot be selected.

Action Key sequence

Post tip Ctrl + F1

Retract tip Esc, Ctrl + F1

B.2.5 Text components

B.2.5.1 JTextField (Java L&F)


Blank text field with only one line

Action Key sequence

Navigate in Alt + Char accelerator key (if defined)

Navigate out forward Tab

Navigate out backward Shift + Tab

Move to previous char Left

Move to next char Right

Move to previous word Ctrl + Left

Move to next word Ctrl + Right

Move to start of field Home

Move to end of field End

Submit entry Enter

Select all Ctrl + A

Deselect all Arrow keys

Extend selection left Shift + Left

Extend selection right Shift + Right

 Avitech GmbH 2018 Page 478 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Extend selection to start Shift + Home

Extend selection to end Shift + End

Extend selection to previous word Ctrl + Shift + Left

Extend selection to next word Ctrl + Shift + Right

Copy selection Ctrl + C

Cut selection Ctrl + X

Paste from clipboard Ctrl + V

Delete next character Delete

Delete previous character Backspace

B.2.5.2 JTextArea (Java L&F)


Blank text field with more than one line

Action Key sequence

Navigate in Tab, Alt + Char Accelerator Key (if defined)

Navigate out forward Ctrl + Tab

Navigate out backward Ctrl + Shift + Tab

Move up one line Up

Move down one line Down

Move left one char Left

Move right one char Right

Move to start of line Home

Move to end of line End

 Avitech GmbH 2018 Page 479 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Move to previous word Ctrl + Left

Move to next word Ctrl + Right

Move to start of text area Ctrl + Home

Move to end of text area Ctrl + End

Block move up PgUp

Block move down PgDn

Block move left Ctrl + PgUp

Block move right Ctrl + PgDn

Block extend up Shift + PgUp

Block extend down Shift + PgDn

Block extend left Ctrl + Shift + PgUp

Block extend right Ctrl + Shift + PgDn

Select all Ctrl + A

Deselect all Arrow keys

Extend selection up Shift + Up

Extend selection down Shift + Down

Extend selection left Shift + Left

Extend selection right Shift + Right

Extend selection to start of line Shift + Home

Extend selection to end of line Shift + End

Extend selection to start of text area Ctrl + Shift + Home

Extend selection to end of text area Ctrl + Shift + End

Extend selection to previous word Ctrl + Shift + Left

Extend selection to next word Ctrl + Shift + Right

Copy selection Ctrl + C

Cut selection Ctrl + X

 Avitech GmbH 2018 Page 480 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Paste Selected Text Ctrl + V

Delete next character Delete

Delete previous character Backspace

Insert line break Enter

Insert tab Tab

B.2.5.3 JTextPane (Java L&F)


Field in with formatted texts as well as graphics can be edited

Action Key sequence

Navigate in Tab

Navigate out Ctrl + Tab

Navigate out backwards Shift +Ctrl + Tab

Move up a line Up

Move down a line Down

Move left a component or char Left

Move right a component or char Right

Move up one vertical block PgUp

Move down one vertical block PgDn

Move to start of line End

Move to end of line End

Move to previous word Ctrl + Left

Move to next word Ctrl + Right

Move to start of data Ctrl + Home

 Avitech GmbH 2018 Page 481 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Move to end of data Ctrl + End

Move left one block Ctrl + PgUp

Move right one block Ctrl + PgDn

Select All Ctrl + A

Extend selection up one line Shift + Up

Extend selection down one line Shift + Down

Extend selection to beginning of line Shift + Home

Extend selection to end of line Shift + End

Extend selection to beginning of Ctrl + Shift + Home


data

Extend selection to end of data Ctrl + Shift + End

Extend selection left Shift + Right

Extend selection right Shift + Right

Extend selection up one vertical Shift + PgUp


block

Extend selection down one vertical Shift + PgDn


block

Extend selection left one block Ctrl + Shift + PgUp

Extend selection right one block Ctrl + Shift + PgDn

Extend selection left one word Ctrl + Shift + Left

Extend selection right one word Ctrl + Shift + Right

 Avitech GmbH 2018 Page 482 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.5.4 JEditorPane (Java L&F)


Field in with formatted texts can be edited

Note: For more information on how to navigate/move and make selections, please
see JTextArea.

Action Key sequence

Move to next HTML link or other Tab, Shift + Tab


focusable element

Move out of focusable elements that Ctrl + Tab, Ctrl + Shift + Tab
accept a tab

Activate an HTML link Enter

Navigate in / out Tab

Navigate out backwards Shift + Tab

Move up one line Up

Move down one line Down

Move left one component or char Left

Move right one component or char Right

Move up one vertical block PgUp

Move down one vertical block PgDn

Move to beginning of line Home

Move to end of line End

 Avitech GmbH 2018 Page 483 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Move to previous word Ctrl + Left

Move to next word Ctrl + Right

Move to beginning of data Ctrl + Home

Move to end of data Ctrl + End

Move left one block Ctrl + PgUp

Move right one block Ctrl + PgDn

Select All Ctrl + A

Extend selection up one line Shift + Up

Extend selection down one line Shift + Down

Extend selection left one component Shift + Left


or char

Extend selection right one Shift + Right


component or char

Extend selection to start of line Shift + Home

Extend selection to end of line Shift + End

Extend selection to start of data Ctrl + Shift + Home

Extend selection to end of data Ctrl + Shift + End

Extend selection up one vertical Shift + PgUp


block

Extend selection down one vertical Shift + PgDn


block

Extend selection to previous word Ctrl + Shift + Left

Extend selection to next word Ctrl + Shift + Right

Extend selection left one block Ctrl + Shift + PgUp

Extend selection right one block Ctrl + Shift + PgDn

B.2.6 Containers: frames, windows, panes, and icons

B.2.6.1 JDesktopPane (Java L&F)


Main application window, that allows the use of Multiple Document Interface (MDI).

 Avitech GmbH 2018 Page 484 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Navigate forward among open Ctrl + Alt + F6, Alt + Tab, Alt + Esc, Ctrl + Alt + Shift + F6, Alt +
application windows, then desktop Shift + Tab
icons

Navigate forward among open Ctrl + F6, Alt + F6, Ctrl + Shift + F6
associated windows

Navigate backward among open Alt + Shift + F6


associated windows

Post menu of window-options Shift + Esc, Ctrl + Space bar, Alt + Space bar

Open window (when set as an icon) Enter

 Avitech GmbH 2018 Page 485 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.6.2 JOptionPane (Java L&F)


Pop up window to asks for a confirmation or to inform the user

Action Key sequence

Navigate in/out Alt + F6

Navigate within Tab, Shift + Tab

Retract dialog Esc

Activate the default button (if Enter


defined)

Activate the current button Space

B.2.6.3 JDialog (Java L&F)


Sub window with a title but without menu bar

Action Key sequence

Navigate out Alt + F6

Navigate within Tab, Shift + Tab

Retract dialog Esc

Activate the default button (if Enter


defined)

Activate the current button Space

 Avitech GmbH 2018 Page 486 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.6.4 JScrollPane (Java L&F)


Scroll bar

Action Key sequence

Navigate out forward Tab

Navigate out backward Shift + Tab

Move up Up

Move down Down

Move left Left

Move right Right

Move to start of data Ctrl + Home

Move to end of data Ctrl + End

Block move up PgUp

Block move down PgDn

Block move right Ctrl + PgDn

Block move left Ctrl + PgUp

B.2.6.5 JSplitPane (Java L&F)


This is a window in which elements are separated by a division bar and act independently
from one another.

Action Key sequence

Navigate out forward Tab, Ctrl + Tab

Navigate out backward Shift + Tab, Ctrl + Shift + Tab

Move between panes Tab, F6

Move to division bar F8

 Avitech GmbH 2018 Page 487 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Resize pane vertical Up, Down

Resize pane horizontal Left, Right

Resize to min Home

Resize to max End

B.2.6.6 JTabbedPane (Java L&F)


This is a window in which card boxes can be seen.

Action Key sequence

Navigate in Tab

Navigate out Ctrl + Tab

Move to tab left Left

Move to tab right Right

Move to tab above Up

Move to tab below Down

Move from tab to page Enter, Ctrl + Down

Move from page to tab Ctrl + Up

Move from page to previous page Ctrl + PgUp

Move from page to next page Ctrl + PgDn

 Avitech GmbH 2018 Page 488 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

B.2.6.7 JFrame (Java L&F)


This is a window that has a title and a menu bar.

Action Key sequence

Navigate out Alt + Esc

Display window menu Alt + Space bar

Activate the default button (if Enter


defined)

B.2.6.8 JInternalFrame (Java L&F)


This is a window that has a title and a menu bar and is inside a JDesktop.

Action Key sequence

Open (Restore) Ctrl + F5, Alt + F5, Enter

Close Ctrl + F4, Alt + F5

Move Ctrl + F7, Alt + F7

Resize Ctrl + F8, Alt + F8

Minimize Ctrl + F9, Alt + F9

 Avitech GmbH 2018 Page 489 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4
AviSuite - MCU
User Manual

Action Key sequence

Display window menu Alt + Space bar

Activate the default button (if Enter


defined)

B.2.6.9 JWindow (Java L&F)


This is a window without any title or menu bar.

Action Key sequence

Activate the default button (if Enter


defined)

End of Document

 Avitech GmbH 2018 Page 490 of 490


Document ID: UM_AviSuite_Mcu_All 2018-10-10 Version 1.4

You might also like