How PageGate Sends Messages

PageGate has the ability to send messages in a variety of formats to a variety of sources. You can send text messages to phones, pages to pagers, email to email addresses, update webpages with a CGI GET or POST statement, among other methods.

So, to send messages, you first need to know what type of messages you want to send.

How to send SMS/text messages

How to send Email

How to send pages

Communicating with chat servers, web APIs and other miscellaneous sending methods

Since reliability is incredibly important, PageGate has a failover system that allows you to automatically fail over from one method of communication to another in the event of delivery failure. For more information on how to configure a fail over, have a look at the Failover Scenarios section of the documentation.

This is the complete list of supported delivery protocols.

•XMPP (Extensible Messaging and Presence Protocol)

A method used to communicate with a variety of notification and chat programs, such as Jabber.

•TAP (Telocator Alphanumeric Protocol)

The standard message delivery protocol for analog modem, or direct serial communications to paging providers and terminals.

•TAP-IP (Telocator Alphanumeric Protocol delivered by TCP/IP)

This protocol is used to send messages to a receiving TAP system, normally paging transmitters, by TCP/IP.

•SNPP (Simple Network Paging Protocol)

A standard message delivery protocol for internet communication to a wireless provider.

•WCTP (Wireless Communications Transfer Protocol)

A standard message delivery for Internet communications to a wireless provider (both HTTP and HTTPS are supported).

•SMTP (Simple Mail Transport Protocol)

The protocol used to deliver email.

•GSM-AT (Global System for Mobile communication AT Command Set)

A method used to communicate with a cellular modem or other connected wireless device that provides a COM port in Windows and supports the AT command set for SMS delivery.

•GSM-AT-IP (Global System for Mobile communication AT Command Set over IP)

A method used to communicate with a cellular modem, router, gateway or other connected wireless device that accepts AT commands by TCP for SMS delivery.

•HTTPGET

The GET method of passing CGI parameters to a web API.

•HTTPPOST

The POST method of passing CGI parameters to a web API.

•Touch-Tone/DTMF (Dual Tone Multi-Frequency)

A way to deliver touch tone messages to older numeric-only pagers and similar equipment.

•FAX (Facsimile Machines)

Message delivery to destination Fax machines via faxmodem.

•FAXSrv (Microsoft Fax Server)

This protocol allows PageGate to integrate with a Microsoft fax server for facsimile messages.

•RawSerial

Transmission of message text over a standard serial/RS232 port (direct connect or via modem).

•RawTCP

Transmission of message text to a host via a TCP/IP connection

•File

Output a message as an ascii formatted file to a specified directory.

•UCP (Universal Computer Protocol)

A delivery protocol for analog modem, or direct serial communications to a wireless provider.

For a detailed and contextualized breakdown of what these protocols mean for delivering your messages, have a look at the How PageGate Sends Messages section of the documentation.