SMDI service thread base class. More...
#include <smdi.h>
Inherits: Thread, Mutex
The SMDI service thread responds to SMDI service events that are received and distributes those events through several abstract calls that can be defined in an application specific class. The SMDI service thread also defines entry points for sending SMDI control messages such as changing message waiting lamp status.
Create an SMDI service thread for the derived class at the specified priority level. The Start() method should be used to kick it off once the class is created.
pri | level for the service thread. |
Destroy the SMDI service thread and any resources it uses.
Turn the message waiting lamp on at the specified targeted directory number.
target | directory station number. |
Turn the message waiting lamp off at the specified targeted directory number.
target | directory station number. |
Return number of seconds that have transpired since any SMDI message has been received and processed by the service thread. This can be used to determine if the link is broken.
Handler to call in a derived class when contact with the SMDI data source has been broken. By default, it simply exits the SMDI service thread.
Handler to call in derived class when an incoming ring event is received. SMDI ring events include SMDI_DIRECT, SMDI_FWDALL, SMDI_FWDBUSY, and SMDI_FWDNA.
cid | calling station id. |
fwd | forwarding station for integrated greetings. |
port | number or line of SMDI entity ringing. |
mtype | message type identifier. |
desk | number of SMDI entity ringing. |
Handler to call in derived class when SMDI status messages are received. These are typically associated with message waiting lamp control requests.
msg | status string from SMDI source. |
Send SMDI message waiting message in either the network or serial protocol derived class.
msg | waiting control string. |
Read input from either the network or serial session protocol class.
SMDI service thread routine. This calls Readline to receive input from the session protocol (network or serial) and the various dispatch routines based on the type of message received.
| Kdoc |