CIMPLICITYAlarm Cast Administrator: How it Works
Alarm Cast Server provides its clients with a single unified interface for dispatching text messages to numerous different destination types. The destination may be an actual text pager, a mobile phone handset, or an email address. ??The format and connection method is irrelevant; Alarm Cast Server formats and delivers the message to the destination for you.
To accomplish this task Alarm Cast utilizes a concept of a Device. A Device in Alarm Cast is the physical path the engine will utilize to connect to the destination service providers. Examples of devices include serial ports, internal or external modems, modems hosted via TCP/IP connected modem sharing devices, or Internet connections etc. Once the device is named and defined, it may be used to define service providers.
Using this device connection Alarm Cast Server communicates to the service provider using the protocol defined for the provider. In the case of most North American one-way paging service providers, the TAP protocol is used. In this case, serial packets are sent to the provider using the associated device.?? Once protocol initiation is established, message transactions are dispatched to the provider using the selected protocol method for transaction initiation and completion.
For each destination a unique network id is sent along with the message to identify the end destination on the provider???s network. The creation of a destination in Alarm Cast Server allows you to use a familiar name in place of the unique provider???s network id, which is often numeric and not easily remembered. Once the message request is sent, a response from the provider is returned to Alarm Cast where it is evaluated for transaction success or failure. The result of this message is logged within the Alarm Cast Server logs for later review. Should the transaction require a retry, it is scheduled for the next connection to the provider.
Supported Alarm Cast Protocols:
| MS-SPEECH | Speech API that converts text to speech |
| ODBC | Open Database Connectivity (Support for any ODBC compliant database) |
| OUCHPUSH | Orange Ouch Protocol |
| SMTP | Simple Mail Transport Protocol (For e-mail input to messaging service providers) |
| SMTP-FORDAU | Simple Mail Transport Protocol for Ford Australia (Proprietary protocol) |
| SNPP | Simple Network Paging Protocol (For Internet input into messaging service providers) |
| TAP | Telocator Alphanumeric Protocol, including IXO and PET (For most North American messaging service providers) |
| TR500 | TR500 PBX Protocol |
| UCP | Universal Computer Protocol (Primarily for European GSM/SMS handsets) |
