Set up Tychron 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
- Enter your API HTTP token in the Tychron settings and use Save at the bottom of the page.
- Copy the full Webhook URL, including its token.
- Configure the SMS-enabled Switch in Tychron to use HTTP POST and Trinity JSON 1.0, with the copied URL as its destination.
One connection URL serves all numbers assigned to it. SessionCloud replies with an empty HTTP 204 after processing, preventing a callback response from being interpreted as an automatic SMS reply. Keep the complete URL private.
Pilot scope
Individual incoming and outgoing SMS is available. MMS attachment controls are not enabled. Delivery receipts for multipart SMS are not combined into a final result for the whole message; do not treat acceptance as confirmed delivery.
See Tychron’s SMS API 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.