We're pleased to unveil our new single sign-on (SSO) capabilities in the [Mission Control Portal](https://portal.telnyx.com/). Business accounts can now take advantage of streamlined security and efficiency in their organization's user access management.

Organizations can now leverage one of several SAML providers including __Auth0__, __Microsoft Azure Active Directory__, __Okta__, __Google GSuite__, __OneLogin__ and __LastPass__ to seamlessly provision Telnyx accounts for their organization members. 

Telnyx users can enable SSO by navigating to [My Account](https://portal.telnyx.com/#/app/account/single-sign-on) in the Mission Control Portal and entering details from their SAML provider.

If you'd like to learn more about SSO for the Mission Control Portal and how it can streamline your communications, [explore the docs](https://developers.telnyx.com) or [talk to an expert](/contact-us) today.


Enable Single Sign-On in the Telnyx Mission Control Portal via your SAML provider to streamline organizational access.

SSO (Single Sign-On) in the Mission Control Portal

We're pleased to unveil our new single sign-on (SSO) capabilities in the Mission Control Portal. Business accounts can now take advantage of streamlined security and efficiency in their organization's user access management.

Single Sign-On (SSO) for the Mission Control Portal

We're always working to make your experience better. Part of this work involves unifying your developer experience between our Elastic [SIP Trunking](https://telnyx.com/products/sip-trunks) and Call Control products.

As part of this unification, we're making a change to webhooks associated with calls that use our Voice API, Call Control.

 

## What is changing?

Webhooks associated with calls that use Call Control contain a <code>call_control_id</code> field, which associates a unique identifier with the call and its corresponding API activity. They also contain a <code>call_leg_id</code> field, which associates a separate unique identifier with the call and its SIP activity.

This call_control_id field currently takes the form <code>"call_control_id": "v2:ujuK_2BDm1w5jJLz--bMGbZ-TuMfo86BmKCDk0KllxoYLrxh1HGf3g"</code>.

After this change takes effect, the <code>call_control_id</code> field will contain the same data as the <code>call_leg_id</code> field in any given webhook, and will take this form: 

<code>"call_control_id": "d14dbcee-880b-11eb-8204-02420a0f7568"</code>. 

 

## How can I ensure my communications are unaffected by this change?

If your Voice API application parses the <code>call_control_id</code> field from Call Control webhooks, you may need to update your application to accommodate the new format of data contained in this field.

 

## When is this change happening?

This change is being rolled out in phases. If your account is set to be part of a migration phase, you'll receive a notification from your account manager, or at the email address associated with your account.

 

## Who can I contact for more information?

As always — our technical team is available 24/7 via [live chat in our Portal](https://portal.telnyx.com/), or [Slack](https://joinslack.telnyx.com/) if you have any questions.

We're making a change to Call Control webhooks. Here's how to make sure your communications are unaffected

Updates to Call Control Webhooks

We're making a phased change to Call Control identifier webhooks. Here's how to make sure your communications are unaffected

We're excited to announce that our Verify API now offers Voice and Flash Call as channels for sending 2FA codes. The new features supported are: 

- Delivering a verification code through voice call
- Delivering a verification code through flash call
- Delivering a verification code specific to the PSD2 use case
- Specifying the language for a verification code delivered through voice call or SMS

With these new features, we introduced some changes to the verification API while doing our best to maintain backward compatibility. Users who have already integrated with the API should read the release notes carefully and make the appropriate planning to accommodate the changes.
 

## Updates to API Requests and Responses 
*In the code snippets below, existing features are in green, while new features are in red.*
 
### Create a Verify Profile 

![release note 1](//images.ctfassets.net/taysl255dolk/2FvvwGTkyzb1gJF9LbqKdY/b78c40a016226cc06999ea99ea880bd2/release_note_1.png)
![Release note 2](//images.ctfassets.net/taysl255dolk/4zRao1drU2SvJLfwgQxfcP/a29fbe7d32cc9db031cbb4ab78a68e72/Release_note_2.png)
![release note 3](//images.ctfassets.net/taysl255dolk/71XH0tcDD2j55SlUgrLHMd/d8c9dd5f009df079f9315daf502968e2/release_note_3.png)

*After this release, the old style create payload to /v2/verify_profiles will still be accommodated and the response will remain unchanged. However, we encourage users to migrate to the new API.*

### Update a Verify Profile 

![update a verify profile 1](//images.ctfassets.net/taysl255dolk/1Ei0kKTyXEKAjI2TLaiwve/a587d09309471700125af13efb2441f3/update_a_verify_profile_1.png)
![update a verify profile 2](//images.ctfassets.net/taysl255dolk/73q4SarGgS1A3CkinZgXw4/27793dece4f136bb344743a0bd45fe44/update_a_verify_profile_2.png)
![update a verify profile 3](//images.ctfassets.net/taysl255dolk/3T4mjagZOsTg2lRZlyOAOb/7a42de625f6452ba98d64c4a8f3ac168/update_a_verify_profile_3.png)
![update a verify profile 4](//images.ctfassets.net/taysl255dolk/3TaL1C9OUzEOWIrHrqzjK2/1b0ddc39abe1d6ad8891beeb8a858b7a/update_a_verify_profile_4.png)

*After this release, the old style update payload to /v2/verify_profiles/[PROFILE_ID] will still be accommodated and the response will remain unchanged. However, we encourage the user to migrate to the new API.*

### Trigger a Verification

Triggering a verification to __/v2/verification__ with the old payload is still accommodated. However, the new style of API will support __/v2/verifications/{channel of delivery}.__

![release note 4](//images.ctfassets.net/taysl255dolk/499EU20cX3NaUuVpd1F41J/d8e2b468c20f4eb42eea340aef6b276e/release_note_4.png)
![release note 5](//images.ctfassets.net/taysl255dolk/3d7vcaU77fE2dPknPSIKjV/97e2bedef11f3e19e6958bce4a918d7a/release_note_5.png)
![release note 6](//images.ctfassets.net/taysl255dolk/7unFUZGUVtUgXgo9IWPHz6/9a365fa2e740a619d0a5ba7736ead762/release_note_6.png)
![trigger verification response 1](//images.ctfassets.net/taysl255dolk/6ztDTtWkHg9mrp73Q50pB/99ed16d17262ee2f74d035bf078ef1f9/trigger_verification_response_1.png)
![trigger 2](//images.ctfassets.net/taysl255dolk/3fMjmKHbPEjHeD2JvlN4Bk/54c29e2c9ef6bcf01436d407bf2ca2a7/trigger_2.png)
![trigger 3](//images.ctfassets.net/taysl255dolk/5gLDDoBK00OkANqK1yiHf0/a908b7875d70370a482d5b8d2a7a60d1/trigger_3.png)
![trigger 4](//images.ctfassets.net/taysl255dolk/61Cvi3e406VV0bokb8IX6Z/b541a5ff868990f2002848618a36da97/trigger_4.png)

*We encourage users to migrate to the new API to use the new style API features*

### Submit a Verification Code 

![Release note 7'](//images.ctfassets.net/taysl255dolk/1b449ocUr0sOg2AGO05pPX/029fc17ad5f03c96da0e9b5b4927f254/Release_note_7-.png)

*After this release, old style and new style usage for this feature remain the same.*

### List all Verify Profiles

![release note 8](//images.ctfassets.net/taysl255dolk/7pR1F9DrpTNW5exOOiEOFE/9a63315a52f253c894ac5a88b4e302ec/release_note_8.png)
![release note 9](//images.ctfassets.net/taysl255dolk/7uoy8ZpmTRAPfPLpPcPw32/01313b6c715b12763a4b24a0b37c0acc/release_note_9.png)
![release note 10](//images.ctfassets.net/taysl255dolk/3XGZ6TPmA3nFgzUzJmxkyN/d64319a6755ab40e4839b01894226d8b/release_note_10.png)

*After this release, old style list payload to __/v2/verify_profiles__ will still be accommodated and the response will remain unchanged. However, We encourage users to migrate to the new API to use the new style API features.*

### Retrieve a Verify Profile

![release note 11](//images.ctfassets.net/taysl255dolk/7gXIM1xAq23urjWJfE4XGG/57017c9240eb9184bb868ff71d374d56/release_note_11.png)
![release note 12](//images.ctfassets.net/taysl255dolk/j9L0WXtmWEnKr8LtWKYX8/a955588232b973bebf7392c0a465ef50/release_note_12.png)
![16 new](//images.ctfassets.net/taysl255dolk/4qOUEbDS2treX2DYAX6pmn/fdf5efc77bea1e49195834428aca9fce/16_new.png)

*After this release, the old style and new style request remains the same. However, there are new fields added to the response.*

### Delete a Verify Profile 

![release note 14](//images.ctfassets.net/taysl255dolk/7ESfDqxMr6zv6w8Uapia4A/74e25e682cc5bcf1ccd5885d7314a096/release_note_14.png)
![release note 15](//images.ctfassets.net/taysl255dolk/1uFawQkFwEcut2NIaSW6mT/f543d66c02ad21541fb5624c86a9aad9/release_note_15.png)
![release note 16](//images.ctfassets.net/taysl255dolk/37A31xJeskUrZAE33TVBI9/ed537e5835b1be2b7d6c19d95b127695/release_note_16.png)

*After this release, old style and new style requests remain the same. However, there are new fields added to the response.there are new fields added to the response.*

### List Verifications by Phone Number

![release note 17](//images.ctfassets.net/taysl255dolk/39dAFqJ4aMkGLUgrXiE8Zs/1fb3cc99be807e50432629301e3fac37/release_note_17.png)
![release note 18](//images.ctfassets.net/taysl255dolk/7jPondQcWcIgFDLEQsnZeW/a4636509968d6a2044c6d6440a4b19d2/release_note_18.png)

*After this release, old style and new style requests remain the same. However, there are new fields added to the response.*

### Retrieve a Verification

![Screen Shot 2021-05-25 at 12.59.33 PM](//images.ctfassets.net/taysl255dolk/GZRL46aGIELyhGe9npldG/f06aa1bfbca7c250a32193dcecb0ae9d/Screen_Shot_2021-05-25_at_12.59.33_PM.png)
![Screen Shot 2021-05-25 at 12.59.42 PM](//images.ctfassets.net/taysl255dolk/3ZZ4PXKmuYyVGVW4RrHvTq/591328ae1b7350c5611d35ee04c59123/Screen_Shot_2021-05-25_at_12.59.42_PM.png)

*After this release, old style and new style usage remain the same. However, there are new fields added to the response.*

Telnyx Verify API with SMS, voice, and flash call to send two factor authentication codes at scale.

Telnyx Verify API offers SMS, voice, and flash call

Our Verify API now offers Voice and Flash Call as channels for sending two factor authentication codes.

New Features: Verify API Voice, Flash Call, and API Updates

We’re excited to announce that our Mission Control Portal will now support the vetting of your 10DLC brand. 

![T-Mobile - Number Pool Request Form](//assets.ctfassets.net/taysl255dolk/7jAkNNeHEqfeNMF3PnukdG/603e4f4177ac79bd239fcdb87e41f900/TMUS-10DLC-Number-Pool-Request_v2.0.numbers)

10-digit long code, or 10DLC, is a carrier-led initiative aimed to increase transparency in the messaging ecosystem and allow businesses to send high throughput A2P messages at low costs. Here is an overview of what customers will be able to do with this new feature:

- Request to vet their 10DLC brand
- A $40 vetting charge will be applied to your portal balance as soon as the request goes through
- See their brand score before and after vetting
- Create campaigns that are attached to their newly vetted brand

## Who needs to vet their brand?
Immediately after creating a campaign, a brand is given a brand score. The Campaign Registry recently notified us that this brand score is actually ignored and the brand is treated as a lowest tier brand, unless the company is in Russell 3000. Therefore, we highly recommend customers to vet their brand, because it will likely result in a higher brand score, which leads to higher throughputs. 

While vetting is not guaranteed to improve your brand score, in our experience all scores have improved. A brand score is one of the main criteria that carriers use to determine message throughput (both messages per second and daily brand limitation). We recommend that all customers vet their brand to improve their odds of having the highest throughputs possible for their campaigns. 

## What if I already created campaigns? 
If you have already created campaigns prior to vetting your brand, the throughput limitations will reflect this original brand score. Therefore, we recommend that customers vet their brand before creating any additional campaigns. However, there is a manual process to process campaigns that were created before vetting that we can help to assist with. 

You can get started by [logging into your Portal account](https://portal.telnyx.com "Telnyx Mission Control Portal"), registering a brand, opening that brand page, and completing the “Vetting Request” section.

![10DLC portal vetting ](//images.ctfassets.net/taysl255dolk/69DSJFIaRnM2a9C42qS5Yq/e23527b5703db696533dfecb13fd292d/Screen_Shot_2021-05-17_at_11.19.00_AM.png)


portal vetting

Our newest portal feature allows customers to vet their 10DLC brands to obtain a higher brand score

10DLC Brand Vetting

Our newest portal feature allows customers to vet their 10DLC brands to obtain a higher brand score.

10DLC Brand Vetting on Portal | Telnyx Release Notes

We're excited to bring the full power of Telnyx to iOS and Android, with the beta launch of our new SDKs in Swift and Kotlin.

If you're a mobile app developer, you can use these new SDKs to embed making and receiving phone calls directly into your iOS or Android app.

Your new in-app phone calling capabilities are fully integrated with our [Call Control](https://telnyx.com/products/voice-api) API for full programmatic control over recording, transcription, audio playback, media streaming, call transfer, input gathering, and more. 

What's more - your calls run on the [superior Telnyx network](https://telnyx.com/our-network) for best-in-class availability, private backbone security, and super-low latency.

This beta release has some limited functionality. Additional features including push notifications are planned for an upcoming GA release after the beta has concluded.

Dive into the docs for these new SDKs at our [Developer Center](https://developers.telnyx.com/docs/voice/webrtc/get-started), or grab the SDKs directly from Github:

- [iOS SDK on GitHub in Swift](https://github.com/team-telnyx/telnyx-webrtc-ios)
- [Android SDK on GitHub in Kotlin](https://github.com/team-telnyx/telnyx-webrtc-android)


We're excited to bring the full power of Telnyx to iOS and Android, with the beta launch of our new SDKs in Swift and Kotlin.

Announcing Mobile SDKs for iOS and Android

We're excited to bring the full power of Telnyx to Android and iOS, with the beta launch of our new SDKs in Swift and Kotlin.

We're making changes to how permissions are managed within permission groups in the Mission Control Portal.

Previously, the *Group Membership* option under *Organization Management* allowed sub-users to add or remove members from permission groups.

*__This Group Membership functionality is being deprecated and replaced by a more powerful Permission Group Management functionality.__*

If a permission group has the Permission Group Management permission set to Modify, then users in that permission group will be able to create and manage new and existing permission groups, as well as add and remove users from permission groups. __This can be considered an admin-level permission, as it allows users in this group to grant any user, including themselves, any number of permissions.__

If a permission group has the Permission Group Management permission set to Read-only, then users in that permission group will be able to see all permission groups, their permissions, and users in those groups.

 

## How might this affect my account?

__When this change takes effect, all existing permissions granted under the Group Membership functionality will be revoked.__ Customers wishing to allow sub-users to add and remove other users from permission groups will need to grant those sub-users modify permissions under Permission Group Management, which will also give those sub-users permissions to create and manage permission groups.

 

## When will this change take effect?

This change will take effect on __Monday, May 17th, 2021__.

Please contact our support team by chat in the Mission Control Portal if you require assistance managing your organization's permissions in light of this change.

We're making changes to how permissions are managed within permission groups in the Mission Control Portal.

Deprecating Group Membership and introducing more powerful permission controls in the Mission Control Portal

Transition to Powerful Permission Group Management

Telnyx is happy to announce that we now support Direct Routing for Microsoft Teams. This means MS Teams users can now enjoy all the benefits of partnering with a Tier 1 provider while using your favorite communications software. 

## What is Direct Routing?

Direct Routing is a way to provide a PSTN connection to Microsoft Teams users so that they can make and receive external phone calls on any device using Teams. This allows MS Teams users to use the platform as a primary business telephony system.

Telnyx provides the SBC to interconnect with MS Teams for free through a simple portal configuration. Companies who choose to use Telnyx to route calls using MS Teams will benefit from: 
- Improved call quality, thanks to our global, private network
- More control over dialing plans and phone numbers
- Lower [calling costs](https://telnyx.com/pricing/elastic-sip "SIP Pricing") when compared to Microsft Teams Calling Plans
- Ability to scale faster thanks to Tier 1 interconnects with partners across the globe. 

 

## How do I get started?

You can get started by [setting up](https://telnyx.com/sign-up "Sign Up") a Telnyx account in our Mission Control Portal. From there, you can follow our latest [Configuration Guide](https://developers.telnyx.com/docs/voice/sip-trunking/microsoft-teams "BYOC MS Teams Guide") to set up Direct Routing for Microsoft Teams.

 
<hr>

For more information about Direct Routing or [Telnyx SIP Trunking](https://telnyx.com/products/sip-trunks "SIP Trunking Page"), please don’t hesitate to reach out to our [team of experts](https://telnyx.com/contact-us "Contact Us").

Telnyx Announces Direct Routing for Microsoft Teams

Telnyx and MS Teams

Telnyx announces new integration with Microsoft Teams so you can enjoy carrier-grade quality calling over your favorite communications platform. 

Direct Routing for Microsoft Teams with Telnyx

Telnyx is happy to announce that we now support Direct Routing for Microsoft Teams, meaning you can enjoy higher quality calls on your favorite communications platform. 

Telnyx now offers Direct Routing for Microsoft Teams

Voice API users can now transcribe speech to text in real time, with a beta version of our speech-to-text transcription tools.

Real-time speech-to-text transcription is available in six languages:

- German - <code>"de"</code>
- English - <code>"en"</code>
- Spanish - <code>"es"</code>
- French = <code>"fr"</code>
- Italian = <code>"it"</code>
- Polish - <code>"pl"</code>

Transcription can be turned on and off on-demand at any point during a call by sending a [<code>transcription_start</code>](https://developers.telnyx.com/api/call-control/dial-call) or [<code>transcription_stop</code>](https://developers.telnyx.com/api/call-control/dial-call) command along with the call's <code>call_control_id</code>. Transcription will automatically end if a call ends (through being hung-up by the end-user, or through an API command).

Transcription is billed in 15-second increments, at a cost of $0.05 / minute (or $0.0125 per 15 seconds - that's more than 30% cheaper than competing on-call transcription offerings from Twilio!).

__

To get started using these new transcription tools for Call Control, [explore the API documentation](https://developers.telnyx.com/api/call-control/dial-call).

You'll need a Mission Control Portal account to get started - [create one today](https://telnyx.com/sign-up) and get $10 of free credit to test out transcription!

Transcribe speech to text in real-time, directly from your voice calls.

Speech-to-Text Transcription for Voice Calls

We're updating how supervisor roles interact with mute and hold operations on Call Control Conferences.

Currently, participants can join conferences with certain supervisor roles, using the <code>supervisor_role</code> parameter of the [<code>join</code>](https://developers.telnyx.com/api/call-control/list-conferences) command. If a participant joins as a __monitor__, that participant is automatically muted and they cannot be heard by other participants on the call. If a participant joins as a __whisper__, that participant is only audible to specific other participants on the call.

Currently, supervisor behavior is coupled to the [<code>mute</code>](https://developers.telnyx.com/api/call-control/list-conferences), [<code>unmute</code>](https://developers.telnyx.com/api/call-control/list-conferences), [<code>hold</code>](https://developers.telnyx.com/api/call-control/list-conferences), and [<code>unhold</code>](https://developers.telnyx.com/api/call-control/list-conferences) commands, such that unmuting or unholding a conference supervisor causes them to lose their supervisor role and the associated muting characteristics.

__With this change, supervisor behavior will be separate from, and independent of, <code>mute</code>, <code>unmute</code>, <code>hold</code>, and <code>unhold</code> commands.__

Here is an example to illustrate this new conferencing behavior:

 

## Example - Muting and Unmuting Conference Monitors

1. __A participant joins a conference with <code>"supervisor_role" : "monitor"</code>.__ This supervisor role means that the participant is automatically, *implicitly* muted and cannot be heard by other participants on the call. The <code>unmute</code> command will have no effect on this participant under these circumstances, because the muting behavior is handled in the participant's <code>supervisor_role</code> property.

2. __The <code>mute</code> command is used on this participant.__ This introduces another, *separate, explicit* mute, independent of the participant's supervisor role. The participant is now *muted by two separate properties*: their supervisor role, and the <code>mute</code> command.

3. __The participant is updated using the update command with <code>"supervisor_role" : "barge"</code>.__ Barges are normal conference participants and can be heard by all other participants. However, this participant is *still explicitly muted by the <code>mute</code> command which was used in Step 2*, so they cannot be heard by other participants on this conference.

4. __The unmute command is used on this participant.__ The participant can now be heard by all other participants in the conference.

In this example, there are two separate muting behaviors observed:

- An *implicit* mute, brought upon by the participant's supervisor role.
- An *explicit* mute, brought upon by the <code>mute</code> command.

Both of these mutes must be removed to make the participant audible to others in the conference.

The muting introduced by using a <code>hold</code> command to place the participant on hold can also be viewed as an explicit mute, separate from the implicit muting associated with a participant's supervisor role. As such, un-holding a monitor or whisper participant will allow them to hear others, but they will still be muted by their supervisor role.

 
<hr>
 

This change will take effect on __Monday, April 26, 2021.__

If you have questions relating to this change, contact our development team on [Slack](https://joinslack.telnyx.com/) or by chat in the [Mission Control Portal](https://telnyx.com/sign-up).

We're updating how supervisor roles interact with mute and hold operations on Call Control Conferences.

Improving Supervisor Behavior in Conferences

Telnyx is notifying customers of the establishment of a Reassigned Numbers Database by the Federal Communications Commission (FCC).

In December 2018, the FCC authorized the establishment of the [Reassigned Numbers Database](https://www.reassigned.us/ "Reassigned Numbers Database") (RND). The aim of the database is to enable callers to determine whether a telephone number has been permanently disconnected. This allows the caller to know if the telephone number is no longer assigned to the person they want to reach.

As a Service Provider, Telnyx will be mandated to submit data to the database on a monthly basis. Over the past number of months, Telnyx has been working on technical specifications on how to submit data for the database which contains information about disconnected numbers. 

Going forward, Telnyx will offer customers a 15 day reinstatement period, during which a customer may buy back a phone number that they have previously disconnected. 

After 15 days, the number will be permanently disconnected and will be part of the next reporting period to the RND, which takes place on the 15th of each month. Once the number has been reported to the RND, the wider industry will be made aware of the disconnect and will no longer attempt to contact you via that disconnected number.   

This means that any consent you previously gave to 3rd parties (for example, pharmacies) to contact you through this number will not be applicable and you will need to establish new methods of communications with your providers.  If you wish to buy back this number for your business at a future date, the settings previously associated with the telephone number will have to be reset manually. 

This change will be implemented on __April 14th, 2021__ at 3pm CST. If you have any questions regarding the new Reassigned Numbers Database or what this will mean for how you organize your number inventory, please don’t hesitate to [reach out](https://telnyx.com/contact-us "Contact Us") to our team of experts. 


Telnyx is notifying customers of the establishment of a Reassigned Numbers Database by the Federal Communications Commission (FCC).

Reassigned Numbers Database Explained

Introducing the Reassigned Numbers Database and what it means for your business.

It's now easier than ever to debug your Webhooks, Programmable Fax and TeXML communications. Our new debugging tools in the Mission Control Portal allow you to search, analyze and debug your communications by inspecting webhooks associated with phone calls, faxes, messages, account events, and more.

Using these new debugging tools, you can find webhooks by webhook delivery ID, or filter a list of all recent webhook deliveries associated with your account by time, status, or text strings contained in the webhook body.

Faxes and phone calls can be found by Fax ID or Session ID, or filtered from a list of all fax and TeXML events on your account by time, product, originating number, or destination number. For each event, you can inspect the associated webhooks to see exactly when each was sent, and locate the source of any errors in your application.

![Self-Service Debugging for TeXML and Fax](//images.ctfassets.net/taysl255dolk/3i1fQzk9q5biDnoDcTL3yA/2762fbaec1f9e2757390e70985279874/debug-frontpage)

![Self-Service Debugging for TeXML - Webhook Inspector](//images.ctfassets.net/taysl255dolk/1LFLXyBswIM4AMMPBBEkwb/9504a99499076ed17836521bf533064b/texml-webhook)

To get started using these new debugging tools for Webhooks, TeXML, and Programmable Fax, simply [log into your Mission Control Portal account](https://portal.telnyx.com/) and browse to the Debugging tab.

Prefer to debug in your IDE? Our [Webhook Logging](https://developers.telnyx.com/api/webhooks/get-webhook-deliveries) tools allow you to extract webhooks via API with advanced filtering options.

Self Service Debugging Tools in the Mission Control Portal - Release Notes

Debug your Programmable Fax, Voice API & communications webhooks with our easy-to-use UI tools, in the Telnyx Mission Control Portal

Debugging for Fax and Voice API - UI Tools

It's now easier than ever to debug your Programmable Fax and TeXML communications, all from the Mission Control Portal.

New Debugging Tools for Webhooks, TeXML, and Fax in the Mission Control Portal

We’re excited to announce that our [Wireless SIMs](https://telnyx.com/products/iot-sim-card) now have usage based activation. This feature is useful in cases where SIMs are deployed and remain inactive for multiple billing periods, but need to be enabled on demand. Prior to this feature, Telnyx [SIMs](https://telnyx.com/products/iot-sim-card) were manually enabled via API when they were ready to be used. With usage based activation, inactive Telnyx SIMs have the option to be configured in a “standby” state with a $0.20 MRC, which automatically activates to operate as normal when it reaches 1MB of usage. 

Here’s how it works: 

- Telnyx customers register their SIM before it is inserted and configured into their hardware.
- In the portal, select the SIMs that you would like to enable usage based activation for, and click on "Manage SIM Cards Settings” from the bulk actions dropdown. 
- Select the option "Set SIMs to standby status."
- After a few minutes, your SIM status will reflect this change. 
- Once the SIM reaches 1MB of usage, it is activated in its normal state, and will be charged $2 MRC.
- The status of the SIM can be disabled via API or portal, and usage based activation can be turned on again so that you don’t have to pay $2 MRC until the SIM is used. 

 
<video width="100%" controls autoplay loop poster="">
 <source src="//videos.ctfassets.net/taysl255dolk/NG5dU0nJ5qsvIRVerjmGE/09f9481a372ec103227e8dab76e24a9c/Usage_Based_Activation.mov" type="video/mp4">
 Usage Based Activation for Telnyx Wireless SIMs
</video>

 

If you’d like to find out more about our Wireless offering, please don’t hesitate to [get in touch](https://telnyx.com/contact-us "Contact Us") with our team of experts.

Usage Based Activation

Telnyx SIM usage based activation means you can deploy your SIMs in standby, and automatically trigger them to activate

Telnyx SIM usage based activation 

We’re excited to announce that our Wireless SIMs now have usage based activation.

Release notes