METAmessage for Wireless
 
     
Home
About
Solutions
Products
Downloads
Support
Sales
Contact
Support - METAmessage
Problems with Sending Messages

The MCS displays the number of sent messages with counters in the Sending and Alert protocols columns of the console Flows tab. If the counters are not showing activity, check the following:

  • Are there copies of messages in the Sent items folder of the mail database or profile?
  • Does the NT account under which the MCS service runs have the proper access permissions to the database or mailbox?
    Is the MCS configured to send messages from the correct database or mailbox?
  • If using Exchange, is the profile the MCS points to pointing to the correct mailbox?
  • If using Exchange, were the Outlook profiles created while the MCS service account was logged onto the machine?
  • If testing with a wireless device, are messages getting to the desktop mail client for that same account?

The METAmessage Fax Emitter, if installed on a remote machine from the server, uses port 2002. The MCS Fax function communicates to the Onset fax gateway over TCP ports 5014, 5015, and 5016. All three of these ports need to allow for outbound-initiated communication to Onset's gateway. Each port is used for a specific communication as follows:

  • TCP port 5014: used for Print job error notification and/or confirmation.
  • TCP port 5015: used to send the print file from the MCS to the gateway.
  • TCP port 5016: used for registering an MCS installation with Onset's print gateway.

Back