Messaging providers and connection options
Keep your existing SIP service and add messaging to the softphone through a separate messaging connection. Your calling number and messaging number can be different. The provider must enable messaging on the number before you use it.
Choose where messaging runs
| Option | Message path | Who operates the inbox? | Choose this when |
|---|---|---|---|
| Provider connection | App ↔ SessionCloud ↔ messaging provider | SessionCloud | You want to enter carrier credentials and use a built-in integration. |
| Custom HTTPS | App ↔ SessionCloud ↔ your gateway ↔ provider | SessionCloud | You have an outbound SMS gateway and can forward incoming messages to a webhook. |
| Customer-hosted service | App ↔ your messaging service ↔ provider | Your service | You want the app to contact your server directly, with your own accounts, storage and carrier integration. |
SIP registration stays with your PBX in all three options. A carrier API token does not replace the app’s account provisioning or the number assignment.
Existing provider connections
| Provider | Credentials | SMS | MMS in this integration | Guide |
|---|---|---|---|---|
| Telnyx | API key and webhook public key | Incoming and outgoing | For numbers whose Telnyx settings enable MMS | Telnyx |
| Twilio | Account SID and Auth Token | Incoming and outgoing | Not enabled | Twilio |
| DIDWW | HTTP OUT trunk username/password | Incoming and outgoing | Not enabled | DIDWW |
| VoIP Innovations / Sangoma | Wholesale API username/password | Incoming and outgoing | For configured North American messaging numbers with carrier MMS service | Provider setup |
| Andrews & Arnold | Messaging number and dedicated SMS password | Incoming and outgoing through SessionCloud | Not enabled | HTTPS gateway setup |
MMS support depends on the connection, number, carrier account and app. A carrier offering MMS does not mean every integration exposes it. These connections support individual conversations; multi-recipient group MMS is not supported.
Additional provider pilots
These integrations are in pilot preparation and are not yet enabled on the production portal. The table describes their implemented scope, not live carrier certification. Use an existing connection until your pilot is enabled and validated with your provider account.
| Provider | Details to have ready | Implemented pilot scope | Incoming callback configuration |
|---|---|---|---|
| SignalWire | Space URL, Project ID, API token and separate webhook signing key | SMS | Compatibility API / LaML messaging webhook, HTTP POST |
| Flowroute | Access key and secret key | SMS and MMS | Set both SMS and MMS callback URLs to the complete portal URL |
| Bandwidth | Account ID, Application ID, OAuth Client ID/Secret | SMS | Set the application’s incoming and outgoing callbacks to the complete portal URL |
| Voxtelesys | Messaging API key | SMS and MMS | Message Origination and Delivery Receipt callbacks, JSON HTTP POST |
| Telgorithm | Company SID and API token | SMS and MMS | Messaging Config inbound message and outbound delivery status URLs |
| Tychron | API HTTP token | SMS | SMS-enabled Switch, HTTP POST, Trinity JSON 1.0 |
| IntelePeer | API Access username/password and Customer ID (EID) | SMS | Set the incoming webhook for each number |
For private webhook connections, copy the entire generated URL, including its token. SignalWire uses its separate signing key for callback verification. Configure the connection once, then assign each messaging number to its SIP account and provide updated account provisioning.
Flowroute, Voxtelesys and Telgorithm pilots allow attachments and caption text totalling up to 600 KB per outgoing MMS. Telgorithm permits at most five attachments. SignalWire, Bandwidth, Tychron and IntelePeer pilots do not enable MMS attachment controls.
During the pilot, verify incoming and outgoing messages, duplicate callbacks, offline synchronization, background notifications and supported delivery receipts. Voxtelesys callback identity needs live validation; Tychron multipart delivery receipts are not aggregated; IntelePeer final delivery receipts are not requested or processed. An accepted send is not proof of delivery to a phone.
Use a bridge or your own service
- Custom HTTPS: configure the gateway and incoming webhook. This connection handles text SMS. SessionCloud supplies the inbox and app API.
- Customer-hosted service: provision your own endpoints. Your server owns authentication, inbox storage, carrier callbacks and notification requests. Implement the optional MMS extension if your service and carrier support attachments.
- Standalone SessionTalk Pro or Free: use the SMS web-service guide and bridge download. A SessionCloud project is not required for manual standalone setup.
A bridge can integrate a provider for which there is no built-in connection. It must implement the selected interface; entering an arbitrary carrier URL or API token does not translate that carrier’s protocol automatically.
More than one provider
A project can save connections to several providers. Each assigned number uses one connection. Select the provider you want to configure, edit its details and use Save at the bottom of the page to save all edited connections.
Assignments are currently manual: configure the provider once and assign one messaging number to each SIP account that needs messages. Accounts used only for calls do not need an assignment. Disable an assignment before changing it; reassignment starts a new history and requires updated provisioning.
Continue with SMS for BYO PBX for the complete portal and app setup flow.