Thank you for your interest in our PageGate application.
PageGate is a Wireless-messaging/SMS/Paging gateway. It can accept messages from one or more different sources, and is then able to deliver those messages to wireless devices via one or more industry standard communication methods.
For example, in a simple configuration PageGate can accept messages from a dispatcher, who manually enters messages into PageGate's Windows GUI Client application, and PageGate can then send those messages to mobile phones or pagers via the wireless providers's network.
In a more complicated example, PageGate can be simultaneously accepting hundreds of messages from multiple sources such as email, webpages, analog modems, manual dispatchers, integration with other applications, etc., while also delivering them with up to sixteen concurrent outbound communication sessions.
PageGate can be installed to run on a single non-dedicated workstation, or using its modular architecture, PageGate can actually be installed across a dozen or more computers for a truly high-performance messaging gateway system.
Inbound Messages - ways that PageGate can accept incoming messages:
• | PageGate's GUI Client - A simple to use Windows program for manually dispatching messages. It has many advanced features such as preset messages and recipients, scheduling, logging, reports, etc. |
• | Webpage/webserver - A CGI application that allows users to dispatch messages from a webpage on your webserver |
• | Email - Full support for SMTP and POP3 protocols for accepting and collecting email messages |
• | Commandline executable - 16-bit and 32-bit applications (executables) that can be run on the commandline, or by other applications to submit messages to PageGate (this is a common integration method for 3rd party applications) |
• | Text files - PageGate can 'watch' one or more files and folders for new text files, that contain messages (this is a common integration method for 3rd party applications) |
• | TAP - Messages can be accepted via modem or direct serial connection, using the standard TAP messaging protocol |
• | SNPP - Messages can be accepted over the Internet using the standard SNPP messaging protocol |
• | Touch-Tone - A voicemodem can be used to accept messages sent from a touch-tone phone, and convert them to textual messages |
• | Serial (RS232) - A serial port can be monitored, and messages can be extracted from the input |
• | Direct database integration - New messages can be written directly to PageGate's industry standard MS Access compatible database (this is a common integration method for 3rd party applications) |
Outbound Messages - ways that PageGate can deliver outbound messages:
• | TAP - Telocator Alphanumeric Protocol - the standard message delivery protocol for analog modem, or direct serial communications to wireless providers |
• | SNPP - Simple Network Paging Protocol - a standard message delivery protocol for Internet communications 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 - an email protocol used by many wireless providers |
• | UCP - Universal Computer Protocol - a delivery protocol for analog modem, or direct serial communications to a wireless provider |
• | GSM-AT - Global System for Mobile communication AT Command Set - a method used to communicate with a directly connected mobile phone or wireless modem for end-to-end wireless message delivery |
• | 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 |
• | Raw-Serial - transmission of message text over a standard serial port (direct connect or via modem) |
• | Raw-TCP - transmission of message text to a host via a TCP/IP connection |
|