OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
1-26
Communication From Remote UAs to OSI/MHS
4. MTA 2 accepts that association request if all criteria for connection establishment
are satisfied.
5. When an association is established, OSI/MHS transfers the message to MTA 2.
Communication From Remote UAs to OSI/MHS
A remote UA (that conforms to the 1988 P7 protocol) communicates with OSI/MHS
through the RS process in an RS group. Only the RUA is capable of initiating
associations to OSI/MHS. OSI/MHS never attempts to initiate an outgoing association
to an RUA.
Establishing Associations
For communication with RUAs, OSI/MHS must be configured to listen for incoming
associations on addresses known to remote users. One or more RS groups must be
configured for this purpose, depending on your requirements.
Each RS group defined on your system is configured using a single OSI address.
When an RS group is in the STARTED state, it listens for incoming association
requests on that address.
Several RS groups may be configured to listen for incoming association requests on
the same or different OSI addresses. For load balancing, ease of management,
performance, and recovery reasons, it may be beneficial to:
•
Assign specific OSI addresses to specific sets of users (by telling them which
addresses to use)
•
Configure several RS groups to listen on the same OSI address
•
Spread users over multiple RS and MS groups
Example of a Message Flow From a Remote UA to an MS
User on OSI/MHS
Figure 1-15 shows how a message flows from an RUA to an MS user on OSI/MHS.