OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
1-25
Communication Between Adjacent MTAs and
OSI/MHS
Transferring a Message From an Adjacent MTA (MTA 1) to
OSI/MHS
The following steps describe a message flow between adjacent MTAs:
1. The sending MTA (MTA 1) attempts to bind to OSI/MHS by initiating an association
request to OSI/MHS.
2. OSI/MHS responds positively to the association request if all prerequisites for
connection establishment are satisfied. One important prerequisite is that an MR
group must have been previously configured with the OSI address matching that
specified in the association request. That is, the MTA object for MTA 1 must be
configured with the remote OSI address of MTA 1.
3. After an association has been established, MTA 1 transfers a message to
OSI/MHS.
Transferring a Message From OSI/MHS to an Adjacent MTA
(MTA 2)
1. The RTS process (having received a message from MTA 1) passes the message
on to the MR process for routing.
2. The MR process examines the originator/recipient (O/R) name of the recipient,
checks the route-selection criteria (defined as part of the ROUTE object), and
determines that this message should be sent to MTA 2.
3. The MR process attempts to bind by requesting an association with MTA 2.
Figure 1-14. Message Flow Between Adjacent MTAs Using OSI/MHS
013VS T .VSD
Adjacent
MTA 1
OSI/AS
OSI/MHS
MR Group
RTS
PDU
MRP
Adjacent
MTA 2