OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
1-24
Message Flow Between External Entities and
OSI/MHS
Message Flow Between External Entities and
OSI/MHS
The next few pages briefly describe how OSI/MHS communicates with adjacent MTAs
and RUAs.
Communication Between Adjacent MTAs and OSI/MHS
An adjacent MTA communicates with OSI/MHS through the RTS process in an MR
group. Each MHS subsystem can have multiple MR groups, and each RTS process
can support up to 20 concurrent associations. For communication with adjacent MTAs,
an OSI/MHS subsystem must:
•
Know the OSI addresses of the MTAs to which it wants to initiate outgoing
associations and send messages
•
Be configured to listen for incoming association requests on OSI addresses known
to other MTAs
You specify the OSI addresses when you define the following OSI/MHS objects:
•
GROUP objects in the MR class, representing MR groups
•
MTA objects, representing adjacent MTAs
Incoming Associations
Each MR group defined on your system is configured using a single OSI address.
When an MR group is in the STARTED state, the RTS process listens for incoming
association requests only on that address. You can configure multiple MR groups to
listen for incoming calls on the same OSI address.
Outgoing Associations
For outgoing associations, each RTS process uses the addresses defined for the MTA
object that is associated with the MTA with which it wants to communicate.
Example of Message Flow Between Adjacent MTAs Using
OSI/MHS
Figure 1-14 shows how a message flows to and from adjacent MTAs using OSI/MHS
as the relay system.