Skip to Content
SessionCloud Portal

Set up Voxtelesys messaging

This integration is available in the portal as a pilot. Validate it with your provider account before customer rollout. A saved connection does not confirm live carrier delivery.

Open your BYO PBX project in Provisioning > Advanced > Messaging, enable SMS, and select this provider under Incoming and outgoing SMS.

Connect your account

  1. Enter your messaging API key in the Voxtelesys settings and use Save at the bottom of the page.
  2. Copy the complete Webhook URL, including its token.
  3. Configure Message Origination and Delivery Receipt callbacks as JSON HTTP POST requests to this complete URL in Voxtelesys.
  4. Confirm that the number is enabled for the messaging service you want to use.

One connection URL serves all assigned numbers. Keep the URL private and retain its token when configuring the callbacks.

Pilot scope

Individual SMS and MMS conversations are supported. Outgoing MMS attachments and caption text must total no more than 600 KB. Group MMS is not supported.

Validate incoming callback identifiers and duplicate handling with your account. If a callback has no message ID, the integration uses its timestamp and message contents to recognize retries; two identical messages with the same timestamp cannot be distinguished. Also test delivery receipts and attachment downloads.

See Voxtelesys’ messaging API reference .

Connect the app and test

Assign each messaging number to its user’s exact SIP username and domain, then provide updated authenticated provisioning or an account provisioning QR code. See Connect the app.

Test sending, receiving, duplicate callbacks, offline synchronization and background notifications. Check the carrier’s records before resending a message whose delivery is uncertain. Keep credentials and private webhook URLs out of screenshots and support messages.

Compare all messaging providers, or use the troubleshooting guide if messages fail.

Last updated on