Set up IntelePeer 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 an API Access username, its API password and the account’s Customer ID (EID) ready.
- Enter those values in the IntelePeer settings and use Save at the bottom of the page.
- Copy the complete Webhook URL, including its token, and set it as the incoming webhook for each messaging number in IntelePeer.
Incoming callbacks use HTTP POST. The same connection URL serves all its assigned numbers. SessionCloud handles renewal of the provider authentication token from the saved API Access credentials. Keep the complete callback URL private.
Pilot scope
Individual incoming and outgoing SMS is available. MMS attachment controls and final delivery receipts are not enabled. An accepted send is not proof of delivery to the destination phone.
See IntelePeer’s SMS message management 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.