Web SMS Templates

A web template allows configuration to any third party web SMS provider, all that is required is the web SMS provider accepts an http(s) POST or GET statement or an XML POST.

Requirements

The selected third party gateway MUST support https as encrypted passcode SMS messages sent across the internet is mandatory.

In addition for an enhanced end user experience, message overwrite (Protocol ID 61-67) should also be supported. Message overwrite allows new passcode messages to overwrite old SMS messages from the same senders address. This feature removes the burden of deleting used SMS passcode messages from the end users phone.

File Location

Main control file MUST end in _control.txt and should be located in Data\WEBSMSTEMPLATE

Control File Selection

The registry key “HKLM\Software\SecurEnvoy\WebSMS Gateway\TemplateFile” should be set to the file name of the control file

Control File Settings

Init File (POST Data

The following dynamic strings will be replaced:

#USERID# UserID for Authenticating With Gateway
#PASSWORD# Password for Authenticating With Gateway

Send File (POST Data)

The following dynamic strings will be replaced:

#USERID# UserID for Authenticating With Gateway
#PASSWORD# Password for Authenticating With Gateway
#MOBILENUMBER# Mobile Number
#SOURCEADDRESS# Source Address
#MESSAGE# SMS Message to Send
#10DIGITID# Unique 10 Digit Code
#OVERWRITE# Overwrite String For Setting Overwrite Last Message
#FLASH# Flash String to flash message on screen (Real Time Passcodes Only)

InitURI

The following dynamic strings will be replaced:

#USERID# UserID for Authenticating With Gateway
#PASSWORD# Password for Authenticating With Gateway

SendURI

The following dynamic strings will be replaced:

#USERID# UserID for Authenticating With Gateway
#PASSWORD# Password for Authenticating With Gateway
#MOBILENUMBER# Mobile Number
#SOURCEADDRESS# Source Address
#MESSAGE# SMS Message to Send
#10DIGITID# Unique 10 Digit Code
#OVERWRITE# Overwrite String For Setting Overwrite Last Message

Certificate Enrolment

  1. create a policy request file caller c:\certpol.txt and add the following:-

      Subject="cn=Bomgar,o=Bomgar,ou=Bomgar"
      RequestType=pkcs10
      Exportable=TRUE
  2. Create the pkcs#10 certificate request in a cmd window certreq –v –New c:\certpol.txt c:\certreq.txt

  3. After third party SMS Gateway CA have signed this request import the user certificate and root certificate

  4. Move the cert and private key to the local machine store as follows:-

    1. With ie6 export cert and private key to cert.pfx

    2. Start mmc with certificate plug-in for local machine

    3. Right click “personal/certificates” “All Tasks/Imports”

    4. Import cert.pfx

  5. With mmc certificate plug-in, select this cert and export the cert without the private key:

      For 32 bit installations:
      c:\program files\Bomgar\Security Server\DATA\WEBSMSTEMPLATE\clientcert.cer
      For 64 bit installations:
      c:\program files(x86)\Bomgar\Security Server\DATA\WEBSMSTEMPLATE\clientcert.cer

Message Text Encoding

SMS messages can be encoded before they are replaced in the #MESSAGE# string

Leave blank for no encoding

URL

Characters are URL encoded with UTF8

HexIA5

Characters are converted to a 2 digit hex Ascii code and the follows are converted to IA5

  • @ = 00
  • $ = 02
  • LineFeed = 0A
  • CR = 0D

XMLGSM

The following characters are converted then the message is url encoded

  • ‘ = '
  • " = "
  • & = &
  • > = >
  • < = &lt;
  • LineFee< = &lt;d = &#x000A;
  • CR = &#x000D;

XMLONLY

The following characters are converted (not url encoded)

  • ‘ = &apos;
  • " = &quot;
  • & = &amp;
  • > = &gt;
  • < = &lt;
  • LineFeed = &#013;

Document Encoding

Post document data can be encoded, valid options (URL)

URL

Characters are URL encoded with ISO-8859-1