Message Statuses
Appendix D - Message Statuses
The first table lists the core message status codes and their respective descriptions. At any given point in time, each and every QTRACS message has one, and only one disposition, which is represented by one of the core status's. QTRACS permanently logs the core statuses for each message in the name of the message source.
The second table lists the auxiliary message status codes and their respective descriptions. The auxiliary status codes are not used to describe the disposition of a message; rather, they provide extra information regarding actions that were taken by various QTRACS users who have handled the message. QTRACS logs the auxiliary statuses for each message in the name of the user who performed the action.
Status Code |
Status Name |
Status Description |
---|---|---|
10 |
SCHD |
This core status applies to both forward and local messages. This status indicates that a message has been created and is scheduled to be sent at a later time. This system automatically transmits scheduled messages according to the batch message transmission schedule. |
20 |
PEND |
This core status applies to both forward and local messages. This status indicates that a message has been created, placed on the Communication Manager's input queue, and is awaiting transmission. This intermediate status will normally progress to XMIT. |
30 |
XMIT |
This core status applies to both forward and local messages. This status indicates that a message has been created, placed on the Communication Manager's input queue, and is currently in the process of transmitting to the intended recipient(s). This intermediate status will normally progress to RCVD. |
41 |
RJCT |
This core status applies to forward messages only. It indicates that, due to errors detected by the QTRACS Communications Manager, the message was not successfully transmitted to its intended recipient(s). |
42 |
NSVC |
This core status applies to forward messages only. It indicates that the message was not successfully delivered to its intended recipient(s). Furthermore, it indicates that the message failed to be delivered successfully because the MCT was not in service. |
43 |
DRPD |
This core status applies to forward messages only. It indicates that the message was not successfully delivered to its intended recipient(s). Furthermore, it indicates that the message failed to be delivered successfully because the mobile dropped the message due to an error (possibly incompatible macro versions.) |
44 |
UNDL |
This core status applies to forward messages only. It indicates that the message was not successfully delivered to its intended recipient(s). |
45 |
CNLG |
This core status applies to forward messages only. It indicates that the user has attempted to cancel the transmission of a previously requested message. This is an intermediate status that MAY eventually result in the successful cancellation of the message. (In some cases, it is too late to cancel a transmitting message because the system successfully delivers the message before it can be stopped.) |
46 |
CNLD |
This core status applies to forward messages only. It indicates that a request to cancel a message has ended with a successful cancellation. This status is a final status. |
50 |
RCVD |
This core status applies to all messages. This status indicates that a message has been successfully delivered to its intended recipient(s). This status may or may not be a final status. If 'return receipt' has been requested, then the status will eventually progress to READ when the receiver actually ccreads the message; otherwise, the RCVD status will be the final status. |
60 |
READ |
This core status applies to forward and local messages. It indicates that the message was successfully received and read by its intended recipient(s). This status is a final status. |
Status |
Status Name |
Status Description |
---|---|---|
n/a |
UNSN |
This status applies to both return and local messages. All of these messages are initially received in a user's mailbox as Unseen. This status is usually an intermediate status that eventually progresses to one of the final status's described below; however, Unseen may be a final status. |
61 |
SEEN |
This status applies to both return and local messages. This indicates that a message has been read (but not claimed). This status is a final status. |
62 |
CLMD |
This status applies to return messages only. It indicates that a message has been seen and responsibility for it has been 'claimed'. The status is a final status, and is only applicable to coverage addressed messages that are read by users that have authorization to 'claim' messages. (This special status is closely linked to the ignored status defined below.) |
63 |
CC'D |
This status applies to both forward and return messages the have been carbon-copied to an auxiliary account via the QMASS functionality. It indicates that a copy of a message has been forwarded to an auxiliary account. The status is final. Note that the sender of a message will never know if the CC'D recipient has seen the message, (it may remain unseen on the auxiliary system). |
n/a |
IGND |
This status applies to return messages only. This special status is only applicable to messages addressed to coverages with more than one member. If one of the members of the coverage is an 'authorized claimer', and other members of that same coverage are 'ignorers of claimed messages', then this status will occur as follows: When a 'claimer' reads the message, the status of the copies of the same message in the other coverage members' mailboxes (who are defined as 'ignorers') will be set to Ignored. |
90 |
FWRD |
This auxiliary status is tracked whenever a message is originally received by a host user and later forwarded to another. |
91 |
RSNT |
This auxiliary status is tracked whenever a message is originally sent by a host user and later resent to another. |
92 |
RPLY |
This auxiliary status is tracked whenever a message is originally received by a host user and later responded to by sending a message to the original sender. |
93 |
MARK |
This auxiliary status is tracked whenever a message is tagged by a host user for later resolution. |
94 |
SUPR suppressed |
This auxiliary status is tracked whenever the body of a message is suppressed. A message could be suppressed at the time it is sent/received, or it could be suppressed 'after the fact' by a call to a QTRACS API. |
95 |
DLTD deleted |
This auxiliary status is tracked whenever a message is deleted from a mailbox. |