How to Use Common Sender ID for Sending SMS via CLASSOUND

This document explains how to send one-way SMS using a common sender ID (for all users) via CLASSOUND SMS service.

CLASSOUND documentation: https://wildix.atlassian.net/wiki/x/jA3OAQ

Created: June 2025

Permalink: https://wildix.atlassian.net/wiki/x/AoAzTQ

1 Introduction
2 Requirements
3 PBX Configuration
4 Additional Notes

Introduction

This document explains how to send one-way SMS using a common sender ID (for all users) via CLASSOUND SMS service.

Note:

The option is available for EU destinations only.
For USA, Canada, no sender ID is used. Instead, the recipient sees the number associated with the office number.

Requirements

CLASSOUND Service Activated
Sender ID, registered and approved for UK, UAE

PBX Configuration

Go to WMS -> PBX → System → Fax/ SMS server tab
In the Curl SMS send field, add the following Curl details for SMS server settings:

curl --location 'https://sms-outbound.wildix.com/send/' \
--header 'Authorization: Basic base64(serial:key)' \
--header 'Content-Type: application/json' \
--data '{
    "serial": <serial>,
    "to": <destination number>,
    "from": <Source number>,
    "message": <Text message>,
    "extension": <customer extension>,
    "license": <license type>
}'

Where:

serial = PBX serial number, the unique identifier of your PBX.
You can find your PBX serial in WMS → Tools and Utilities → Activation/Licenses:

Note: Serial is a fixed value and cannot be set as a variable.

to = the recipient’s phone number. You can set it as the variable {TO_NUMBER} – in this case a user can dynamically specify the appropriate destination number.

from = common sender ID, the sender name that will be displayed as the sender of one-way SMS messages (e.g., Wildix).
message = text of the message. Set it as the variable {MESSAGE} and it will be automatically populated with the content of the SMS to be sent.
extension = the extension of the user sending the SMS. Currently, it is a fixed value.
license = type of SMS licence. Currently, it is a fixed variable representing the type of SMS license assigned to the user sending the SMS.

Additional Notes

Authorization Token: can be obtained in /rw2/etc/sf2 on the PBX side:

The string in “pbx:token“ format should be decoded in base64 format. For example, you can use this service. Enter the “pbx:token“ string in the ASCII Plain Text field to get it decoded in Base64:

Sender ID Registration: some destinations require prior registration of sender IDs; ensure this is handled beforehand.
Immutable Parameters: extension and licence are currently fixed and should not be modified.