Example: Receiving Replies via EMAG WCTP

PageGate can be easily integrated with Verizon's Enterprise Messaging platform (EMAG), which supports an enterprise WCTP gateway that supports one-way and two-way messaging.

With one-way implementations, PageGate delivers SMS through the Verizon EMAG WCTP gateway but no reply is expected and none is monitored for.

With two-way implementations, PageGate delivers SMS through the same gateway but replies are expected. In order to provide those replies to you, the EMAG WCTP API requires a reply address; somewhere to route the replies. PageGate's Webdata API provides the ability to receive those replies and this API must be hosted on an outward facing web server as the reply URL provided to the EMAG WCTP API must be internet accessible.
 
You can then configure reply processing in a few ways:

•Static Recipient or Group

This is the most basic form of reply processing. All replies will be delivered to the specified recipient or group.

•Reply processing with GetASCII API Advanced Polling rules

If you own the GetASCII API, you can feed the reply information through that system for advanced processing. This allows you to modify message content and who the replies should go to but does not allow for conditional modification or conditional sending. For example, you couldn't have the program scan the body of the message for a keyphrase, then completely change who the message is intended to go to based on it. That would require the PageGate Filter Pack.

•Reply processing with the GetASCII API and the PageGate Filter Pack

Reply messages can be fed through PageGate's Filter Pack to allow for conditional sending. For instance, with the PageGate's filter pack, you can tell PageGate to conditionally change who receives the message based on what the text in the reply is. As an example, you could configure a filter system so that any time the word lunch shows up in a reply message, that reply is sent to the cafeteria group instead of the general replies group.

You could configure a system where replies from a certain phone number will always be copied to certain recipients or groups.

You could configure a system where certain keywords or phrases are replaced with other keywords or phrases. For example, you could translate a code like PD4N in to 4th Precinct.

You could configure a system to describe every element I've just described all at once.

However, you must own and implement the Filter Pack to have the functionality necessary to do conditional sending as described.

Step 1: Host webdata.exe on your web server

The first thing you'll need to do is host webdata.exe on your web server so you can provide the return URL to the EMAG WCTP API. The following steps are for IIS but this can be done with any web server suite.

1)Copy webdata.exe from the PageGate program directory to your server's scripting directory.

2)Open the IIS Admin and select the server object.

3) Open Handler Mappings.

4) Right click CGI-exe, left click Edit Feature Permissions

5) Check Execute.

6) Click OK.

7) Select the Server object again.

8) Open ISAPI and CGI Restrictions.

9) Right click in the box and select Add.

10) Specify the following and click OK:

Step 1a: Share the folder webdata.exe is hosted in

If PageGate is not running on the server hosting webdata.exe, you will need to share the directory where webdata.exe is hosted to allow the GetASCII interface to parse data sent to the receiver.

Step 2: Configure the EMAG WCTP API to send replies to Webdata

1)Log in to the EMAG web portal

2)Go to Connections - APIs

3)Edit your existing WCTP API connection.

4)Provide the URL to webdata.exe in the Return URL field.

Example: https://yourIPhere/pgscripts/webdata.exe

5)Apply the changes.