Set up VoIP.ms messaging

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

1. In VoIP.ms, enable the REST API and set a dedicated API password. Allow the SessionCloud server’s outgoing IP address in the API access list.
2. In the SessionCloud messaging settings, select VoIP.ms, enter your account email and API password, and use Save at the bottom of the page.
3. Copy the complete incoming-message URL. In VoIP.ms, edit the messaging-enabled DID and paste it into SMS/MMS URL Callback. Keep its token and all field placeholders unchanged. Select NANPA dialing mode and enable URL Callback Retry.
4. Assign the number to its SIP account in SessionCloud and provide updated account provisioning. Enter the number in SessionCloud as +1 followed by its ten digits. Test incoming and outgoing messages with an authorized recipient.

The callback uses GET and SessionCloud replies with plain ok after processing it. Repeated callbacks with the same message ID do not create duplicate messages. The same connection URL can serve all its assigned numbers. Keep it private.

VoIP.ms SMS is limited to 160 characters; MMS text is limited to 2,048 characters. This integration handles individual conversations using US and Canadian numbers. See the provider’s API setup  and SMS/MMS settings  for account requirements.

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.