Set up Bandwidth 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
- Have the Account ID, messaging Application ID, OAuth Client ID and OAuth Client Secret ready. The OAuth credentials need messaging access.
- Enter these values in the Bandwidth settings and use Save at the bottom of the page.
- Copy the complete Webhook URL, including its token, into the application’s incoming and outgoing callback settings in Bandwidth.
- Confirm that your messaging number belongs to the configured application.
Callbacks use JSON HTTP POST. One connection URL serves its assigned numbers; SessionCloud also checks the callback’s Application ID. Keep the token in the URL when copying it.
Pilot scope
Individual incoming and outgoing SMS and delivery-status callbacks are implemented. MMS attachment controls are not enabled. Test incoming callbacks and outgoing delivery receipts with your account before customer rollout.
See Bandwidth’s messaging webhooks guide .
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.