Configuring SMS Interface

Use

To enable SMS message sending, use Conversation API.

The procedure below, which defines the interface that enables sending SMS messages, was for the built-in voicemail service created for Communication Desktop (CDT). It was used for sending SMS notifications to agents when there was a new voicemail. This feature is no longer supported.

Prerequisites

The only supported option is HTTP so you must have a service provider for the HTTP push service.

Procedure

  1. Double-click the SMS Server module in the Modules table.

  2. Enter the required parameters for the session object type HTTP according to the table below.

At startup the SMS module prints to a log an INFO level message that contains an example HTTP query that can be used to fine-tune the parameters.

Table 1. HTTP Interface Parameters

Parameter

Description

Set Password

If the service provider requires a secure connection, select this option, and enter the password.

Note:

  • If this password is used, it must be encrypted. For that, the Certificate for External Password Encryption must be defined in Agent Server variables in IA, and the certificate must be installed on servers where Agent Server, CEM Server, Email Sender, and SMS Server are installed.

  • The encryption certificate (Agent Server variable Certificate for External Password Encryption) is used also for decryption even if that certificate has expired. If the expired certificate is removed from the system, encryption/decryption will fail. To avoid that, do not remove the expired certificate from the servers where Agent Server, CEM Server, Email Sender, and SMS Server are installed. If the certificate has been removed, to correct the situation re-enter this password, and the one in System Services > E-Mail Settings.

Set Local Password

To use a secure connection for receiving SMS messages, select this option and enter the password. This password is used by the third-party SMS cloud service for authenticating itself to the Sinch Contact Pro SMS service.

HTTP Keys

For entering specific information required by the service provider. Enter that in name=value pairs that configure how the HTTP query is built, for example: Okey=src;Dkey=dest;Bkey=body;werb=GET.

  • Okey: A string, defines name for a parameter containing sender’s address (number)

  • Dkey: A string, defines name for a parameter containing destination address.

  • Bkey: A string, defines name for parameter containing message body.

  • werb: A string, defines the http query werb. Possible values are POST and GET.

  • OKstr: A string, defines optional string. If the string is found on HTTP servers, the reply message indicates success, for example: 200 OK. If the OKstr string is not defined, only HTTP status is used to determine if the sending was successful. The default value is empty (not in use).

  • SearchBody: 1/0. Specifies if also reply message body is searched for OKstring. The default value is 0 (not in use).

  • URLEnc: 1/0. Specifies if a message sent to the SMS server provider is URL-encoded. The default value is 0 (not in use).

  • URLEncGet: 1/0. The value 1 specifies that only message text of the GET request is URL-encoded.

Additional Data

Define additional information that SMS service providers may require, for example the character set used. String is passed as such, and its form and content depend on the service provider. For example: &data_type==UTF8&flags=1, &data_type==data_latin1

HTTP Server Address

IP address of the SMS service provider’s server.

HTTP Page

Web page that provides the SMS functionality.

If you use Twilio, the path must contain the user name, that is, the value of User that you have given in the Session String parameter.

HTTP Port

Port number of the SMS service providers server where the SMS engine connects to.