- DarkLight
SMS
- DarkLight
You can configure the SMS Gateway servers for your application. Use these configured servers to send outbound SMS messages. After setting up the SMS server, you can perform the following:
Receive SMS messages from your customers and allow a Campaign Manager application or agent to respond to them.
Send SMS messages in your outbound campaigns.
Add New SMS Server
To add a new SMS server:
Click Create SMS Server to start the setup of a new SMS server.
Enter the SMS Server Name to uniquely identify the server and provide a Description to specify its purpose or functionality within the system.
Select the Server Type from Gateway URL, SMPP, or CPaaS based on the protocol system used to send and receive SMS messages.
Click Next to proceed with the configuration.
Server Credentials
Go to the Server Credentials tab. This tab displays fields based on the selected server type.
If the Server Type is Gateway URL:
Enter the Gateway URL to specify the server endpoint.
Enter the User Name for authentication.
Enter the Password to securely access the Gateway URL.
If the Server Type is SMPP:
Enter the SMPP Server Name to establish a connection.
Enter the SMPP Port Number to connect to the SMPP server.
Enter the SMPP User Name to access the SMPP server.
Enter the SMPP Password to authenticate and securely access the SMPP server.
Select the SMS Mode from the following options:
Sender and Receiver
Sender
Receiver. If the SMS Mode is set to Receiver, enter the Number of Receiver Instances to define the number of connections for receiving messages.
Note
Supported SMS service providers using the SMPP protocol include ACL, WebText, AT&T, and ImiMobile.
If the Server Type is CPaaS:
Select a Provider from the following options:
Twilio
Amazon Pinpoint
Note
If the Server Type is CPaaS and the selected provider is Nexmo or Others, the application does not allow editing these provider options. Nexmo and Others are no longer supported from this release
Enter the appropriate values in the required fields based on the selected provider.
Click Next.
Server Configuration
Go to the Server Configuration tab.
Select the Delivery Status Type to Required if you need delivery status updates for your SMS messages.
Select the Delivery Type from Webhook or Polling methods.
If Delivery Type is Webhook, enter the Delivery Status URL which provides the delivery status of the SMS you have sent. For example: https://<fqdn/hostname<or>PublicIPAddress>/HttpSmsReceiverApi/api/DeliveryStatus
If Delivery Type is Polling Method, configure the following parameters:
Define the Number of Message IDs per Request. It is the number of message IDs the system must request in each polling attempt.
Specify the Minimum Polling Range. Enter the minimum time (in minutes) after SMS delivery for the system to start checking the delivery status. For example, if an SMS is delivered at 1:00 PM and the minimum range is set to 5 minutes, the system starts checking at 1:05 PM.
Specify the Maximum Polling Range. Enter the maximum time (in minutes) after SMS delivery during which the system will continue to check the delivery status. For example: If the maximum range is set to 60 minutes, the system checks for delivery status until 2:00 PM.
Provide the Prefix to be used for sending SMS messages.
Click Save to apply the configurations.
Update SMS Server
Select the server name and click Edit.
Update the server details and click Save.
To Delete, select the server and click Delete. Click Ok on the confirmation pop up.
CPaaS Configuration
Configure Twilio Flex
Sending campaign SMS messages using Twilio Flex service provider usually takes 2 to 4 seconds. To eliminate this delay, the application is enhanced to send the messages in an Asynchronous mode. To achieve this, we have added a new configuration AsyncTwilioSupport to the HttpSMSReceiverAPI component. This must be set to true to send the SMS messages asynchronously.
To configure a new CPaaS provide as Twilio Flex:
Select the type of Authentication from Account SID or API Key.
If the selected Authentication Type is Account SID:
Enter the Auth Token to authenticate the Account SID.
Enter the SMS Receiver API URL which serves as the endpoint for receiving SMS messages.
If the selected authentication type is API Key:
Enter the Account SID which is the account string ID provided for the application.
Enter the API Key provided by Twilio Flex for the user.
Enter the API Secret key provided by Twilio Flex. The API Key and API Secret combined together complete the authentication.
Enter the SMS Receiver API URL, the endpoint for the SMS Receiver API to receive SMS messages. For example: https://<fqdn/hostname<or>localIPAddress>/HttpSmsReceiverApi/api
Click Next.
Note
This configured URL is populated in the IVR Template Editor for your IVR campaigns.
Configure Amazon Pinpoint
You must first configure Amazon Pinpoint. Refer to Amazon Documents for detailed instructions on how to set up and use this application for SMS campaigns.
Select Amazon Pinpoint as the Service Provider from the dropdown list.
Activate the Role-based Authentication if the application server is hosted on AWS-EC2 and this AWS-EC2 has direct access to the Pinpoint project. Deactivate the Role-based Authentication if an AWS-IAM account is being used to access the Pinpoint project and If the server is not hosted on AWS-EC2.
Enter the AWS App ID, a unique identifier for your Amazon Pinpoint application.
Enter the AWS Access Key and AWS Secret Key for the IAM account to authenticate and access the Pinpoint project.
Note
These are not required if you are using Role-based Authentication.
Enter the AWS Region where your Amazon Pinpoint project is hosted.
Provide the SMS API URL for the HttpSmsReceiverApi Web API application to activate communication with the Pinpoint service.
Configure Five9 VCC
To configure a new CPaas Provide as Five9 VCC:
Select Five9 VCC as the service provider from the dropdown list.
Set the value for Batch Size. This is the number of phone numbers included in a single API request. This setting enables efficient batch processing of phone number data.
Enter the Five9 API URL. This is the base URL of the Five9 VCC API servers for establishing a connection.
Enter the Domain Id to access and manage the domain with Five9 VCC.
Enter the Client ID and Client Secret Key that are required to get an access token from the Five9 VCC cloudauthsvcs endpoint. This combination ensures secure authentication with the API.
Enter the SMS Receiver API URL for the SMS Receiver API. For example - https://<fqdn/hostname<or>localIPAddress>/HttpSmsReceiverApi/api
Fields
Field | Description |
---|---|
Configuration Name | The name of the SMS configuration. This is used to uniquely identify the SMS server configuration in the system. |
Server Type | Specifies the type of SMS server, such as SMPP, Gateway URL, or CPaaS. |
Gateway URL | The URL of the SMS gateway server used for sending and receiving SMS messages. |
Action | Provides options to edit or delete the SMS server configuration. |
Description | A description of the SMS server configuration, outlining its purpose or role. |
User Name | The username required to authenticate and access the SMS server. |
Password | The password used to authenticate the user for accessing the SMS server. |
Role-based Authentication | |
Port | The port number used to establish communication with the SMS server. |
SMPP User Name | The username used to authenticate access to the SMPP server. |
SMPP Password | The password required to authenticate the user for accessing the SMPP server. |
SMS Mode | Defines the role of the SMS server. Options include Sender, Receiver, or Sender and Receiver. |
Number of Receiver Instance | Specifies the number of receiver instances to configure if the SMS server is used as a receiver. |
Delivery Status | Activates or deactivates the ability to receive delivery status for sent SMS messages. |
Delivery Type | Specifies the type of delivery status mechanism, such as Webhook (real-time updates) or Polling Method. |
Delivery Status URL | The URL endpoint that provides the delivery status of the SMS messages you have sent. |
Prefix | A prefix to be added when sending SMS messages. |
Number of message IDs per request | Specifies the number of message IDs included in a single API request for delivery status updates or other actions. |
Polling Range | Defines the minimum and maximum time range (in minutes) that the application will check for the delivery status of a sent SMS. For example, if an SMS is delivered at 1:00 PM, setting a minimum range of 5 and a maximum of 60 will trigger the delivery status API at 1:05 PM and check until 2:00 PM. |
CPaaS - Amazon Pinpoint | |
Role-based Authentication | Set this to ON if your application server is hosted on AWS-EC2 and has access to the Amazon Pinpoint project via an assumed role. Set this to OFF if an AWS-IAM account accesses the Pinpoint project or if the server is hosted outside AWS. |
AWS App ID | The Amazon Pinpoint project ID that is linked to an SMS-enabled channel. |
AWS Access Key | Key to access your AWS S3 bucket. Access Keys are used to sign the requests you send to Amazon S3. AWS validates this key and allows access. You use access keys to sign API requests that you make to AWS. |
AWS Region | AWS region that hosts the Amazon Pinpoint project. |
AE SMS API URL | Base URL of the HttpSmsReceiverApi Web API application. |
CPaaS - Twilio Flex | |
Account SID | Unique key that is used to identify specific resources. Twilio Flex provides 34 digits and you can identify the type of SID and the product association by the first two characters. |
API Key | Type of authentication is required when you use APIs of Twilio Flex to send SMS messages from your campaigns. |
API Secret | API Secret key provided by Twilio Flex. |
SMS Receiver API URL | URL of the SMS Receiver API. For example, https://<fqdn/hostname<or>localIPAddress>/HttpSmsReceiverApi/api |