Telnyx SMS in a Softphone: Text From Your Business Number

Your customers text. If your team takes calls on a SIP softphone but answers texts somewhere else, conversations get split across apps, and replies come from numbers customers don't recognise. If you already have a Telnyx number with SMS enabled, you can connect it to SessionTalk. Your team then sends and receives business texts in the same softphone they use for calls.

This guide covers what the Telnyx connection does, what you need before you start and how setup works. The step-by-step instructions are in our Telnyx messaging setup guide.

What does Telnyx SMS in a softphone give your team?

• Two-way texts from a business number. Each user who needs messaging gets a Telnyx number assigned to their softphone account. Customers see your business number, not someone's personal mobile.
• Calls and texts in one app. Texts appear in Messages in the softphone, next to calling. Nobody has to switch to a separate texting tool after a call.
• Notifications when the app is in the background. Mobile users can get an alert for a new text while they're in another app or the phone is locked. They tap it to open the conversation. This needs internet access, push enabled for the account and notification permission on the phone.
• Photos where your number supports MMS. MMS works for numbers whose Telnyx settings enable it. The app checks the number's MMS capability before it uploads an attachment, and users add one item at a time. Group MMS is not supported.
• Your PBX stays as it is. SIP calling stays with your existing PBX. Messaging is a separate connection, so your messaging number can be different from your calling number.

For the wider picture (team chat, custom gateways and the other providers you can connect), see softphone SMS and MMS.

What do you need before you start?

On the Telnyx side:

1. A Telnyx number with SMS enabled.
2. A Messaging Profile with that number assigned to it.
3. Your Telnyx API key and Messaging Profile ID.
4. Your account's Public Key, from Keys & Credentials > Public Key.

On the SessionTalk side, you need a BYO PBX project in SessionCloud, plus an app version and portal that support Telnyx messaging. If the provider controls are missing from your portal, contact SessionTalk to have the feature enabled.

SMS in the SessionTalk softphone is currently available on Android only (app version 8.0.12 or later), and the free app needs the Push and Business options.

How does setup work?

Setup takes four stages, all done by the project administrator:

1. Connect Telnyx in SessionCloud. In your BYO PBX project, open Provisioning > Advanced > Messaging and enable SMS. Choose Telnyx as the messaging provider, enter the API key, public key and messaging profile ID, and save. The API key stays in the portal's provider settings. Users never handle it.
2. Point incoming messages at SessionCloud. Copy the webhook URL that SessionCloud shows for the connection. Paste it into the Webhook URL setting of the number's messaging profile in Telnyx. The URL must come from this project's connection. A URL that belongs to another application sends incoming texts to that application instead.
3. Assign the number to a user. Add the Telnyx number in full international format (for example +447700900123), and enter the user's SIP username and SIP domain. Assign numbers only to the accounts that need messaging.
4. Update the user's provisioning. Give that account updated provisioning. If you use QR codes, create a new code after you save the assignment. Direct Telnyx SIP accounts on sip.telnyx.com can use automatic enrolment in supported apps.

Then test it. Send a text from the softphone to a test mobile, reply, lock the screen, reply again and check that the notification opens the right conversation. The Telnyx setup guide walks through each step, and Troubleshooting SMS covers what to check if a step fails.

Telnyx 10DLC: who handles registration?

SessionTalk connects your Telnyx number to the softphone inbox. It doesn't register brands, campaigns or numbers for you. If you send business texts from US 10-digit numbers, complete 10DLC (A2P) registration, and any other number requirements, in your Telnyx account before you go live. Carrier service, registration and charges stay with Telnyx.

Can you use more than one messaging provider?

Yes. A BYO PBX project can save connections to several messaging providers, so you can use Telnyx alongside another provider as you grow. Each messaging number uses one connection and belongs to one SIP account. See all messaging providers for what each connection supports.

You can pair it with a hosted PBX for small business.

FAQ

Do I have to move my calls to Telnyx?

No. SIP calls stay with your existing PBX. Telnyx SMS is a separate messaging connection, and your messaging number can be different from your calling number.

Does the Telnyx connection support MMS?

Yes, for numbers whose Telnyx settings enable MMS. Users add one attachment at a time from the SMS conversation, and the service may resize images or reject files that exceed its limits. Group MMS is not supported.

Which Telnyx details do I need?

An SMS-enabled number on a Messaging Profile, your API key, the Messaging Profile ID and your account's Public Key.

Does entering Telnyx SIP credentials in the app turn on texting?

Not by itself. The account also needs the SessionCloud messaging configuration and an assigned number, delivered through updated provisioning. Direct Telnyx SIP accounts on sip.telnyx.com can use automatic enrolment in supported apps.

Who handles 10DLC registration?

You do, in your Telnyx account. SessionTalk connects the number to the softphone. Registration stays with your carrier.

Will users get a notification when a text arrives?

Yes, on mobile, when the account has push enabled, the phone has internet access and the app has notification permission. If the phone was offline, opening the app after it reconnects checks for new messages.