 |
|
 |
|
PageGate
sms server and messaging gateway for networks
|
|
How PageGate Recieves Messages
|
PageGate allows for network messaging or network
wide SMS messaging through a combination of the
following methords: email, webpage, commandline,
textfile, Internet, serial port, modem, mobile
phone, wireless modem, direct database access
and windows client.
SMS or text messages can be sent to mobile phones,
wireless devices, cell phones, pagers, billboards,
etc....
PageGate is a flexible powerful way to take control
of corporate communications.
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.
|
PageGate SMS Server Engine - The messaging
engine takes input from any of the front-end modules
and sends the messages to telecom service providers
via modem, the Internet or email. Any number of the
front-end modules can be used simultaneously. Licenses
are required for the number of recipients setup in
the messaging / SMS server. The messaging engine can
run on an existing file or web server, or can be run
on a separate workstation or server.
Inbound Messages - ways that PageGate can accept
incoming messages:
|
|
Commandline/ASCII
Interface
Messages are sent to the PageGate Text Messaging
Engine via a single command issued at the DOS prompt.
Commandline commands may also be issued from within
windows or from within many 'canned' and custom
applications. In addition, this front-end can scan
one or more directories (networked or local) for
text files (ASCII files) containing messages. 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)
This is an excellent front-end used by itself, or
used as a tool for developers and system integrators,
to allow text messaging from within applications.
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) For
example, network monitoring software could send
a text message to an administrator if an anomaly
is detected within existing systems. |
|
|
Web Server Interface
Send text messages via webpages. PA CGI application
that allows users to dispatch messages from a webpage
on your webserver. PageGate's web interface supports
many types of web pages including single, group,
mulitpage, drop down lists and adhoc type web pages.
This interface uses a CGI script to allow any Windows
based web server to accept information entered on
a web page and send it to the Text Messaging Engine.
|
|
|
Email
Interface
Full support for SMTP and POP3 protocols for accepting
and collecting email messages. Receives incoming
email into the PageGate Messaging Engine. Received
mail messages can also be forwarded to additional
email accounts. This front-end includes a fully
functional mail server and may be used by itself
or in conjunction with existing mail servers. |
|
|
Serial
Interface
Enables PageGate to monitor a serial connection
for data. This interface is often used to accept
text that would normally be sent to a printer, and
extract out message information from that data.
|
|
|
GUI Interface
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. |
|
|
TAP-in Interface
Messages can be accepted via modem or direct serial
connection, using the standard TAP messaging protocol.
The GetTap interface accepts these messages over
a serial connection that is usually connected to
a modem. The TAP protocol is the most widely used
text messaging protocol for serial and dialup connections.
The GetTap interface enables PageGate to accept
in text messages from many sources, and then re-dispatch
the messages back out (possibly to different recipients
or groups). Also PageGate can act as a messaging
gateway for TAP clients, simplifying setup, logging
and providing a single connection for sending messages
to a wide variety of carriers. |
|
|
SNPP Add-On
Messages can be accepted over the Internet using
the standard SNPP messaging protocol, which then
can be resent using any of the various protocols.
(requires commandline/ASCII interface) |
|
|
Touchtone
Receiver Interface
A voicemodem can be used to accept messages sent
from a touch-tone phone, and convert them to textual
messages.
Example: sending the touchtones '1#3' might mean
send canned message 1 to group 3.
(requires commandline/ASCII interface) |
|
|
TAP2ASCII
PageGate's TAP2ASCII module accepts inbound TAP
connections via a modem or a direct serial connection.
Each message is accepted and saved in an ASCII
text file, in a format compatible with PageGate's
GetASCII interface. Multiple TAP2ASCII modules
can be run on the same computer as PageGate, enabling
PageGate to simultaneously accept messages from
multiple inbound TAP connections.
|
|
|
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) |
How PageGate Sends Messages
|
PageGate is a Wireless-messaging/SMS 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 wireless
devices via the wireless provider'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.
|
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 Communication 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.
|
|
Additional Connectors (formerly
called dialers)
|
Connectors
For installations that need a high message throughput
or a level of redundancy, PageGate supports
up to 16 concurrent dialers. Connectors have
been expanded to include direct connects to
telecom or paging terminals and Internet connections
for sending messages via SMTP, SNPP or WCTP.
This will allow the PageGate Messaging Engine
to simultaneously dial out to more than one
carrier at a time, or to make multiple connections
simultaneously to the same or different carriers.
Dialers can also be used to connect directly
telecom terminals via a serial cable connection.
|
 |
|
|
| System Requirements |
|
| Processor |
Pentium 500Mhz or faster |
| Memory |
128 Mb of free memory
(typically 512 Mb total memory for Windows XP, 2003
or 1 Gb total memory for Vista and newer) |
| Hard
Drive |
50 Mb Hard Drive Free
(for application & database)
|
| Connectivity
/Communications |
Analog modem for dialup
connections, serial cable for direct connections,
mobile phone or wireless modem that supports the
GSM AT command set for wireless connections, or
a dedicated (always on) internet connection. |
| Operating
System |
PageGate
can run on Windows XP and newer |
|
|
|
 |
|
|
 |
|
 |
|
