Set up DIDWW messaging

Connect a DIDWW SMS-enabled number to your SessionCloud BYO PBX project. The app sends and receives through SessionCloud’s messaging API; SessionCloud connects to DIDWW. This integration supports text SMS.

Before you start

You need:

• A DIDWW number enabled for the incoming and outgoing SMS services you intend to use.
• An HTTP OUT SMS trunk and its Username and Password, available from the trunk’s Credentials button in the DIDWW User Panel.
• The SessionCloud server’s outbound IP addresses for your deployment, if your trunk uses an allowed-IP list.
• The exact SIP username and domain of the app account receiving the number.

DIDWW’s SMS trunk credentials are separate from your SIP login and general DIDWW account API key. See HTTP OUT trunks .

Connect DIDWW in the portal

1. Open the BYO PBX project and go to Provisioning > Advanced > Messaging.
2. Enable SMS and save the project.
3. Under Messaging providers, select DIDWW.
4. Enter the HTTP OUT trunk username and HTTP OUT trunk password.
5. Keep the default DIDWW SMS API URL, or use a documented regional endpoint from the trunk’s credentials. The default is https://sms-out.didww.com/outbound_messages.
6. Enter a Campaign ID only if your sending arrangement requires one.
7. Leave Enable this connection selected and select Save at the bottom of the page.

The portal displays a private Webhook URL for the connection. Copy the whole URL, including its token query parameter. Use the same URL for all numbers assigned to this connection and for both callback settings below.

The trunk password is encrypted on the server and excluded from app provisioning. Leave it blank when editing to retain it. Campaign ID can be cleared. Replacing the webhook credential invalidates the previous URL, so update both DIDWW trunks.

Configure outgoing SMS and delivery reports

In the DIDWW HTTP OUT trunk:

1. Authorize the sending numbers under Source Address Settings.
2. If Allowed IP addresses is restricted, include the SessionCloud server’s outbound IP addresses supplied for your deployment.
3. Set Callback URL to the complete webhook URL from SessionCloud.

SessionCloud submits the assigned number as the sender. A successful API response initially means Queued. DIDWW’s processing-success callback advances it to Sent. A final Delivered status requires a delivery receipt; DIDWW support must enable DLR notifications for the account. See the SMS HTTP specification .

Configure incoming SMS

Create or edit an HTTP IN trunk under SMS > SMS Trunks in DIDWW:

Copy the Incoming SMS JSON template from the portal, or use:

{
  "id": "{SMS_UUID}",
  "from": "{SMS_SRC_ADDR}",
  "to": "{SMS_DST_ADDR}",
  "text_base64": "{SMS_TEXT_BASE64_ENCODED}",
  "timestamp": "{SMS_TIME}"
}

Keep text_base64 and its placeholder together. SessionCloud decodes the message before displaying it, preserving quotes, line breaks and Unicode. The message ID allows retries to be stored once. Send the body with Content-Type: application/json.

Assign this HTTP IN trunk to the SMS-enabled DIDs. Creating a trunk alone does not route messages to it. See HTTP IN trunks .

Both inbound messages and delivery reports authenticate using the private URL’s token. Incoming requests can alternatively supply that token in the X-SessionTalk-Webhook-Token header. An HTTP 200 response with {"ok":true} acknowledges processing; it does not confirm delivery to the phone.

Assign numbers and configure the app

In Assign a number, select the DIDWW connection and enter the messaging number in + international format, the SIP username and the complete SIP domain, including its port when applicable. Select Assign number. Repeat for each account that needs messaging.

Open the project’s QR Codes page, select Local, and generate account provisioning for that exact SIP account. Alternatively, provide updated authenticated external provisioning. The app needs a version supporting SessionCloud’s managed API messaging; it does not need DIDWW trunk credentials. See Connect the app.

Test outgoing SMS, incoming SMS and background notifications before moving routine traffic. In Messaging activity, Last received SMS confirms that SessionCloud stored an incoming message. Check the phone’s conversation to confirm app delivery. SIP registration remains with your PBX.

If outgoing messages fail, check the trunk credentials, allowed IPs, sending number permissions, campaign requirements and account balance. If incoming messages are missing, check the HTTP IN trunk assignment, complete webhook URL, POST method and JSON template. MMS is not supported by this connection.