Overview of How PageGate Accepts Messages

Video Transcript

Welcome to the overview of how PageGate accepts messages. In this tutorial, we'll be going over the different interfaces, APIs and modules PageGate supports for receiving information in the form of messages and triggers. PageGate has the ability to accept data and messaging commands in many different formats, making the program easy to deploy in any environment.

In total, PageGate accepts 12 methods of input and a filtering system:

• GUI Client
• GetASCII
• GetMail
• GetWeb
• GetSerial and SERIAL2ASCII
• GetTAP, TAP2ASCII and TAP-IP Server
• Webdata API (requires GetASCII)
• TCP Server (requires GetASCII)
• UDP Server (requires GetASCII)
• SNPP Server (requires GetASCII)
• TouchTone Receiver (requires GetASCII)
• Direct Database Integration
• Filter Pack (requires GetASCII)

The GUI Client is a Windows based application that can be installed on any workstation that has network/UNC access to the PageGate server's database. This client provides a messaging interface that allows users to select recipients and groups and deliver messages. The client also has the ability to schedule messages, schedule repeating messages and maintain a list of pre-configured message templates.

PageGate's robust security system also allows administrators to completely control which workstations and/or users are allowed to see which recipients and groups.

Next we have the GetAscii interface. Also known as the Command Line/ASCII interface, this API is capable of monitoring for ASCII files in multiple local or network directories. GetAscii also provides a command line interface for other applications to trigger messages in PageGate, which allows for easy integration in many cases.

Reviewing the GetMail interface, this API gives PageGate the ability to function as an email server which allows you to receive SMTP/Email and translate it into a different format. GetMail enables a feature in PageGate that allows you to have a copy of all traffic sent to a recipient or group forwarded to a specified email address and allows the program to host POP accessible mailboxes for your recipients and groups.

Next we have the GetWeb interface, which provides a CGI executable and a series of pre-formatted templates to publish a messaging website or series of messaging websites. Anything capable of using GET/POST HTTP methods can make use of GetWeb's CGI executable, which allows developers to trigger messages from most Web, REST and SOAP APIs in to PageGate.

The GetSerial interface allows PageGate to monitor a serial/RS232 port for raw data text strings to be parsed in to outbound messages. This is useful for monitoring arduinos, raspberry pi's, alarm panels, nurse call stations and anything else that can be connected via serial/RS232 cable to transmit alarm and alerting data.

The GetTAP interface allows PageGate to function as a TAP terminal, allowing it to receive the TAP protocol by either modem or RS-232/serial line. PageGate also offers an IP based TAP receiver, allowing it to receive the TAP protocol by TCP connection as well.

PageGate has an HTTP data receiver (webdata.exe) that can receive input from nearly any API or protocol that offers an HTTP/S request like HTTP GET, HTTP POST and WCTP. The TCP and UDP Server modules allow you to host a TCP or UDP receiver that monitors a required port for incoming TCP or UDP packets. The SNPP Server module allows PageGate to receive the SNPP protocol from other systems. The TouchTone receiver gives PageGate the ability to receive touch-tones by phone line.

As an additional method of integration, PageGate supports direct database integration with ODBC expressions to link to a variety of formats, including SQL. PageGate's Filter Pack is an add-on that allows you to modify any input to or output from any of PageGate's interfaces based on nearly any criteria of your choosing.

This concludes the overview of how PageGate accepts messages. For more information, please visit our website, www.notepage.net.