sms messaging
NotePage Logo
NotePage Software
NotePage Orders
Download NotePage Software
Software Solutions
NotePage Support

 SNPP Settings
 WCTP Settings
 TAP Numbers
 SMTP Settings
 PageGate Support
 NotePager Pro Support
 Learning Center
 Support Forum
NotePage Resellers
NotePage Press Releases

NotePage Background Graphic

Overview of How PageGate Sends Messages Video Tutorial

How PageGate Sends Messages

Please be patient while the video loads
wmv video format mov video format
itunes feed avi video format

How PageGate Sends Messages Transcript for Video:
Welcome to the overview of how PageGate sends messages. In this tutorial, we’ll be going over the protocols and delivery methods PageGate has available to deliver messages and handle data. Most commonly, PageGate is used as a messaging platform and most of its protocols deal with message delivery. However, some of the protocols we support allow for some very innovative and intricate systems that could potentially send and receive SMS or send content to a web API and also check for updates from that same API, just to name a few examples.

Currently, PageGate supports protocols that allow you to:

  • Send SMS through internet and cellular hardware
  • Send email directly from the PageGate Mail server engine or relayed through your SMTP server
  • Send pages using internet, modem, serial and TCP-to-Terminal methods
  • Communicate with web APIs that support GET/POST methods
  • Communicate with XMPP chat servers
  • Send Faxes by modem or Microsoft Fax Server
  • Output Raw content to a serial port
  • Output Raw content to an IP address via TCP
  • Output a file to a local or UNC path

To say that there are numerous ways that you could implement the program would be an understatement. For example, you could have the program deliver SMS, pages and email all at the same time while also scanning for reply SMS, then use the content of those replies to update multiple web APIs. You could even implement a filter system that would only update the web APIs if specific keywords or key phrases were found in the body of the reply and deliver all non-web API traffic to an email and SMS distribution list.

So, let’s talk about how PageGate can deliver the different types of messages it’s capable of.

First, let’s go over SMS. There are three potential delivery methods you have for sending text messages.

  • Internet

PageGate supports delivering messages through a carrier’s internet to SMS Gateways via the SNPP, WCTP and SMTP/email protocols. The program also supports delivering messages to SMS aggregators like I Am Responding, Active911, Infobip and Clickatel, just to name a few, using those same protocols as well as HTTP GET and POST methods to interact with their web APIs.

  • Cellular Hardware

PageGate supports both physically connected (USB and RS232) and TCP accessible cellular hardware. The program supports the command set for multiple styles of hardware and can be used with nearly any device that supports the AT command set to send and receive SMS. Examples of this hardware are the Multitech MTC-H5 cellular modem or the Airlink GX450 cellular gateway.

  • Dial-Up Modem

While not many carriers still support this method of delivery, PageGate supports using the TAP protocol with dial-up modem and connected phone line to deliver messages to a carrier’s TAP gateway. The program supports the command set for multiple styles of modem and can be used with nearly any device that supports the standard AT command set.

Next, let’s go over email. SMTP is the protocol used to deliver email and PageGate has a full mail server engine as a core part of the program. This means that you can configure PageGate to deliver email on behalf of your email domain just like any other mail server would. However, doing so will require you to add the public IP address of the PageGate server to the SPF record of your email domain to avoid having your messages filtered as spam. Alternatively, you can configure PageGate to relay your email traffic through any SMTP server you have access and permission to use, just like an email client.

Currently, PageGate supports SSL and STARTTLS handshaking methods and supports LOGIN, PLAIN and CRAM-MD5 SMTP authentication methods.

Next, let’s go over delivering pages. PageGate offers protocols that allow you to communicate with on-site paging hardware as well as pagers hosted through companies like SPOK/USA Mobility and American Messaging. If your pagers are hosted through a company, PageGate supports delivering messages by internet using SNPP, WCTP and SMTP/email as well as using a dial-up modem and connected phone line to use the TAP protocol.

If your pagers are hosted through an on-site paging terminal, PageGate supports serial/RS232, modem and TCP delivery of the TAP protocol.

Next, let’s go over web API communication. PageGate has the ability to use the HTTP GET and POST methods to interact with a web API. Due to the program’s flexible nature, you can use nearly any expression you need to pass to the web API by configuring it in the program’s templating system. For example, one web API might want &auth declared but another might want &authorization declared and it’s incredibly easy to configure either or both as you need.

Now we’re going to get to a few miscellaneous sending methods available in the program. As mentioned earlier in the video, PageGate has the ability to communicate with XMPP chat servers. So, it could send messages to your recipients via Jabber or any other chat system that supports using the XMPP protocol.

PageGate also offers the ability to send faxes by dial-modem with connected phone line or through a local or network available Microsoft fax server. This allows the program multiple potential pathways to deliver any faxes you may need.

PageGate can also output Raw formatted content to either a serial port or IP address. This can be useful for one-way communication with a heartbeat program or other receiving system that can parse the content output by PageGate.

Last we have a delivery method that isn’t usually used to deliver messages, the File protocol. This protocol gives PageGate the ability to output a message as a file to a local or network share path. To give you a few ideas of how this protocol could be used, you might use it for record keeping; where a copy of every message sent to a particular distribution group is written to a directory that’s potentially monitored by another application. You could have all reply SMS written as a file to a path that PageGate’s GetASCII module was monitoring, which would allow you to configure a filtering system that scans the files generated for certain key words or phrases, then deliver the reply SMS to one distribution group if the keywords or phrases are found and a completely different distribution group if they weren’t.

Effectively, the File protocol is handy for record keeping and for generating content that needs to be processed through one of PageGate’s filtering systems.

This concludes the video tutorial overview of how PageGate sends messages.

PageGate Video Tutorials Additional PageGate Video Tutorials
RSS Feed for Video Tutorials Video RSS Feed

send sms
Copyright 1996-2020 NotePage, Inc. Privacy Policy
View Mobile Version NotePage.net