MHS / MCU

MHS / MCU
AFTN/AMHS Routing
AFTN/AMHS Routing

Created by: YA & MM

AFTN/AMHS Routing Lists

 Handling Bundles
 Handling Lists
 AMC Tables
 Common Services

FEB 2024 2
 Handling Bundles

ACTive
bundle OLD
bundle NEW
bundle

Working
copies
Version
Comment
Change history
Activation
history

FEB 2024 3

The System Configuration Tables are managed together in Bundles. So, to change
the configuration of the system a new bundle has to be created first. Then,
individual tables of the configuration can be edited or changed.
The System Configuration shows two tables. The upper table contains
the "Active"
Configuration list and the "Old" list – the previous one. After creating and
transferring a new list, a third one "New" will be created. Upon activation the
"New" list will become "Active", the previously "Active" list will become "Old". The
previously "Old" list will be moved to the lower window, containing the previous
lists.
The individual settings in the Operative Lists can be accessed and viewed at any
time.
First the operator has to select the version of the "System Configuration" he
wishes to inspect.
Here the operator has the ability to check the contents of older configuration-
levels. For user information the version- number of the list presented is always
given at the top of the listing- window. The individual lists can be accessed by
entering the line of the list and use right mouse- click.
At this point it has to be underlined that from the lists displayed the "Active
Version", the "Old Version" and the "New Version" are read only. If the user wishes
to change any settings of these lists he has to create a new "Bundle". The other
lists can be changed, But in order to
avoid any confusion, it is advised to do not change any older lists and reactivate
them. We note that:
 The state of the bundle is either NEW, ACT, or OLD. The ACT one can’t be
edited.
 Each bundle has a version which is automatically set when the bundle is
created.
 A new bundle can be created by copying another bundle which will be
written "Copy Of
 After editing the new bundle, it can be checked and transferred to the
Data base. Its Activation change the state from NEW to ACT. The
parison

to compare (F4)
indicated by bold list name (tab) Here: MTA Circuit and AMHS User Addresses

FEB 2024 4
 Bundles Comparison

Compare result
Difference(s)
indicated by color
codes
• Magenta
-> modified in
bundle 1
• Orange
-> modified in
bundle 2

FEB 2024 5
 Bundle Details Overview

Bundle information:
Version number,
Copy Of version number,
State (ACT/NEW/OLD/WORKING),
User created/modified the
bundle, Last Changed or
created date/time, Comment
free text for update.

FEB 2024 6

The Configuration menu allows the operator to operate the system:

 AFTN Device Configuration,
 AFTN Circuit and Channel Configuration,
 AMHS User Agent Configuration,
 Routing Table configuration,
 AMC Look-up Tables management,
 AFTN-SITA Addresses Conversion,
 External MTAs Configuration (AMHS inter-centres Links),
 Copy of Traffic,
 Automatic Diversion.
The set of configuration lists for a given version is called "Bundle". Whenever
the operator wants to change the configuration (Adding or modifying a circuit, a
channel or the routing table etc.) he has to create a new Bundle. Each Bundle is
identified by a number that is automatically assigned to it by the application
when it is created.
The configuration window is divided into a couple of areas:
 Operational Bundles Area: Those are the bundles that have already
been checked and are ready to be activated. They can not be changed
anymore :and
ACTIVE thethere could
currently Active bundle.
be only 3 :bundles
OLD in this
the bundle wasarea:
previously ACTIVE before it was replaced by
the new
ACTIVE bundle.
NEW : this is the last bundle that has been moved
(controlled and moved from the general bundle area to the
operational bundle area) but it has not been
activated yet.
 General Bundle Area : this is the area that contains all the other
bundles that were created by the operators. These bundles are marked
by the status "Working".
Routing Lists Details Overview

Selection of a list to view

Routing lists
Available lists (represented
by a tab for each list) Number of
elements per list Number of
elements selected in currently
active tab

FEB 2024
 Routing Lists Details Overview

Print
Select list to
print & Print
Choice Print
Preview
For interlaced tables
(only) Overview
printout Detailed
printout

FEB 2024 8
Routing Lists Details Overview

Overview printout

FEB 2024 9
 AMHS Device

 AMHS Device Transport

Selector
Name of the MTA Device
Server/MTA The
network address of the
server/MTA or the name
of the server Password
The authentication
password for the MTA
(the recommendation is
to use the name in lower
case)

T
C
P

P
o
r
t

N
u
m
b
e
r

S
e
r
v
e
r

N
a
m
e
FEB 2024

10
 AMHS Channel

 AMHS Channel
Name: name of the channel (AFTN address)
Session type (P3 or P7)
Permanent: determining whether or not an
association is considered permanent
by the MTA.
O/R Address The AMHS O/R address of
the channel
MTA Device Name of the created Device
Message Quota: Maximum volume in kB
of the msg text
Retention time: The number of days
messages will be retained before
automatic deletion.

FEB 2024 11
AFTN Device

 AFTN Device

Name of the AFTN Device

Server The network address of the
server or the name of the server
Port used to connect the UA
client to
the server by default 50200
Ping Setting used to check the
network connectivity

FEB 2024 12
 AFTN Channel
 AFTN Channel
Name: name of the AFTN channel
Originator: AFTN address
CID: The Channel Identification
TCP Device Name of the created Device
Max Text Length: Maximum number of
characters of the msg text (1800 by default
according to AN10VII) Message Format: SOH or
ZCZC
CSN Digits: number of digits used in the Channel
Sequence Number
Convey Mode: Defines whether the
communication between the switch and the
devise uses the protocol according to AN10VII
completely (MTP) or partly (GEN)
Channel Check settings Define the period
between two CH messages and the tolerance
between early and late incoming CH
SVC Settings Define the SVC messages handling
and the AFTN address used in SVC Messages

FEB 2024 13
 Bundle Details Overview

Options
Common Services
• Printer configuration
• Email accounts configuration

FEB 2024 14

 Printer configuration allows adding printers and set printing

configurations for local printers.
 Email accounts configuration allows to set email accounts/
recipients configuration
 Bundle Details Overview

Options
Common Services
• Printer configuration
• Email accounts configuration

FEB 2024 15
 Import of AMC Look-up Tables

Whenever new AMC Look-up Tables are

published on the AMC website (each
AIRAC Cycle), operators are asked to
update the system configuration. This
update is done via the "Import Address
Look-up Tables" function of the "AMC"
menu in the “Bundle Details” window.

FEB 2024 16

AMC Look-up tables are used to convert AF-Addresses to MF-Addresses. There

are (03) Look-up tables :
 AmhsMdRegister Look-up Table which contains all the Management
Domains MDs registered within ICAO and it’s used to determine the MD
from an AFTN address.
 AmhsCaasTables Look-up Table which is used for conversion of AFTN
addresses to AMHS-CAAS addresses.
 UserAdresses Look-up Table which is used for the conversion of AFTN
addresses
to AMHS addresses and vice versa for any type of AMHS addressing scheme
other than CAAS.