Meridian America Link/Customer Controlled Routing manual Overview of Meridian Link

12Chapter 2: Overview of Meridian Link

Connecting these hardware components requires two (optionally three) signaling links:

¥Link 0 is an Application Module Link (AML), which connects the Meridian 1 system to the IPE Module or the Application Module.

¥Link 1 is a Host Link (or Meridian Link), which connects the host computer to the IPE Module or the Application Module. This Host Link can be implemented as a dedicated X.25 link supporting a single host computer or as a TCP/IP Ethernet LAN link supporting as many as 16 Meridian Link applications.

Note 1: If both the Meridian Link (using TCP/IP) and CCR applications are running, the Meridian Link third-party application can support only up to 15 Meridian Link applications.

Note 2: Any mlusr administration sessions requiring association IDs will reduce the number of association IDs available for Meridian Link applications. For example, if your system has eight association IDs registered to Meridian Link applications and then you register two association IDs for mlusr administration, your system will have six association IDs available (five, if CCR is running).

Note: If you have registered all 16 association IDs (15 if CCR is running) to Meridian Link applications, two overflow association IDs are available for mlusr administration only.

¥Link 2 is (optionally) a Meridian Mail Link (MML), which connects a Meridian Mail system to the IPE Module or the Application Module.

In addition, the IPE Module and the Application Module provide an interface for a system console, which enables you to perform administration and maintenance. A port that is designed to be connected to a modem allows you to perform these activities from a remote location.

The key software required to make these hardware components and links work together is the Meridian Link application, which resides in the IPE Module or Application Module.

553-3202-210 Standard October 1998