There are ways to "Crisis Alert" for a Meridian but not nearly as clean and easy as a Definity. It takes a little work but when your done there is a lot you can do with the application.
We monitor the constant string of information on the maintenance port with an inhouse written visual basic program running on an old junk server with a network connection. The program scans the datafile every thirty seconds or so for certain codes that we define (these are easily changed). When it sees one of the defined codes it has instructions on what to do i.e. we send an email to a distribution list in MSExchange. Some of the entries in the distribution list are pagers, cell phones with text messaging etc.
We are COAMS and do the same thing on certain alarm codes. For 911 the calls are routed to a particular trunk group - we monitor for activity on that trunk group and capture CLID, date, time etc via our little program and forward all the info in the email message. People on the distribution list for 911 have "rules" in exchange for a message from 911 - more pagers etc..
The little program is also handy if your looking for transient problems. You simply input the service code, alarm code or some in other indicator your looking for into the visual basic monitor and your notified when the code appears.
Nortel service providers hate our little program. They would much rather charge you $1 or $2 per port per month to monitor your system and notify you if there are problems. We implemented our program and found where our maintenance provider was disregarding alarm indications - we proved it and got our maintenance contract $$ returned on two 2000 port 81c sytems.