Meridian Link-Based Applications Do Not Receive Expected Messages - Nortel Meridian Meridian 1 Maintenance Manual

Meridian Link-based applications do not receive expected
messages
Some of the messages received by a Meridian Link-based application from
the Meridian 1 are unsolicited due to events that occur on devices (ringing,
answering, and so on). Some messages are responses from the application
software after the application has requested a service.
Because the Application Module or IPE Module can handle multiple
applications at the same time, if an application does not have the correct
configuration, it will not receive the expected messages. Follow the
procedures below to find out why the application is not receiving the
expected messages.
AM debugging tools (trace, monitor, record, filter)
The following list explains the tools available to track the flow of messages
between the application and the Application Module or IPE Module. See
Chapter 3, ÒLink maintenance commandsÓ for information on using the
tools.
¥ The trace command allows application software to capture all the
messages flowing over a link (or through the Application Module or
IPE Module) to files. The messages are represented in hexadecimal
format. The file specified in the trace command is stored in the
/usr/mlusr/trace directory.
¥ The monitor command allows application software to monitor all or a
selective subset of application messages flowing on a particular
association on the system console.
¥ The record command allows the application software to record all or a
selected set of messages flowing on a particular association to a file.
The record command is activated on a per-association basis. The file
specified in the record command is stored in the /usr/mlusr/rec
directory.
¥ The filter command allows the application software to filter out a
selected set of application messages that flow on a particular
association through the Application Module or IPE Module.
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Chapter 4: Diagnosing faults 233