Connect the app to its SMS mailbox
First configure the provider’s webhook and assign the receiving number to the account’s exact SIP username and domain in the portal. Use Telnyx, Twilio, A&A or Custom HTTPS setup as appropriate.
Use an app build containing the incoming HTTPS mailbox feature. Android support for all four providers starts with build 733; store approval and availability may vary. For iOS, obtain the corresponding compatible build from your provider. Older builds may not show Incoming messages or understand A&A/Custom mailbox configuration. SessionTalk Free requires Push and Business for these messaging features.
SessionCloud
- Enable SMS and save the project in the portal.
- Assign the number to the user’s SIP account under Incoming and outgoing SMS.
- Supply updated, authenticated account provisioning through your existing external-provisioning or private QR workflow. Public Provider ID branding alone does not supply a mailbox token for every provider.
- Open the updated app with the account enabled. Use App delivery > Refresh status in the portal to check device registration.
Do not delete an existing account or its conversations merely to force a refresh. Follow your provider’s account-update procedure. The supported direct Telnyx Provider ID flow can connect an assigned mailbox after SIP sign-in; this does not imply automatic enrollment for A&A, Twilio or Custom HTTPS accounts.
If the account has Override provider SMS settings enabled, its local HTTPS gateway takes precedence for outgoing messages. Turn that override off to use the portal connection for both directions. Incoming messages still require the assigned mailbox.
Standalone SessionTalk Pro or Free
- In the portal, choose App setup beside the assigned number and copy the private messaging setup code.
- On the phone, wait for any call to end. Open the existing SIP account and turn off Enabled.
- Open Advanced SIP settings > Messaging and enable SMS. Save Advanced SIP settings, then save the account before continuing.
- Reopen Advanced SIP settings > Messaging > Incoming messages. Paste the code and choose Connect mailbox.
- Re-enable the account and open Messages.
The code must match that account’s SIP username and domain. It connects messaging without replacing the SIP login. A separately selected local HTTPS gateway still handles outgoing messages; otherwise replies use the provider connection in the portal.
The code grants access to the mailbox. Send it only to the intended user; do not post it in tickets, public screenshots or chat rooms. Disconnect mailbox removes the local connection while retaining conversation history. Disabling the mailbox in the portal prevents further server access; contact your provider to replace a compromised setup capability without losing needed history.
Verify notifications
Allow app notifications and enable push for the account. Open the app once, refresh App delivery in the portal, then send a test SMS to the assigned number. Confirm receipt in the foreground and again after returning to Home and locking the phone. Tap the notification and verify the intended conversation opens.
A registered-device count confirms that the app reported a route; it does not prove the phone received a push. An offline phone can catch up when reopened. Use Troubleshooting SMS to separate provider delivery, mailbox sync and notification problems.