With the beta release of the Detail Record Search API, developers can find call detail records (CDRs), message detail records (MDRs) and WhatsApp message records with simple commands and filtering.

The beta release enables searching for the following types of detail records:

|      |      |
| ---------- | ---------- |
| __Product__     | __`record_type`__     |
| Messaging       | `messaging`       |
| Conference &nbsp; &nbsp; &nbsp; &nbsp;      | `conference`, &nbsp; `conference-participant`       |
| WhatsApp       | `whatsapp`       |

To get started with the Detail Record Search API, check out our [tutorial](https://developers.telnyx.com/docs/debugging/detail-record-search), or dive into the [full API reference](https://developers.telnyx.com/api/detail-records/search-detail-records).

Use the Telnyx Detail Record Search API to get insights into your usage. Try it out today!

Find Records for Communications Usage via the Telnyx API

With the beta release of the Detail Record Search API, developers can find call detail records (CDRs), message detail records (MDRs) and WhatsApp message records with simple commands and filtering.

Find Detail Records for Product Usage via API

We're proud to unveil our new Media Storage API, letting you handle media in your communications more easily. 

Up to now, using Telnyx to transmit or communicate media was difficult. Users had to host files on their own servers—or worse, on a slow, public file-hosting service—and supply the URL to their Telnyx application.

Now, when sending PDF documents as faxes via API, playing back custom audio files on phone calls, sending rich media over MMS, or handling media assets in any other communications, users have a better option. The Assets API enables users to upload files directly to Telnyx via simple API commands, store them securely in our cloud environment with a friendly name for as long as they're needed, and serve them quickly and reliably in other Telnyx API actions using just their friendly name. Files can be uploaded from your local machine, or from a publicly-accessible URL. 

By default, files are available for 48 hours after upload. Users can also specify a custom time-to-live (TTL) for any file - perfect for handling sensitive files, or ensuring important files are always available for use.

For more information and usage examples, head over to our [Developer Center](https://developers.telnyx.com/docs/media/media-api/quickstart).

Telnyx introduces the Media Storage API, simplifying media handling in communications. Upload, store, and serve files directly via Telnyx with ease.

Telnyx launches Media Storage API

 Upload, store & serve media in your calls, texts and faxes.

Telnyx unveils a new Media Storage API

As we have developed the TeXML functionality in our Call Control product, we have introduced a new attribute for dial command. Telnyx users can now set a Caller ID name on Outbound Calls that are generated using TeXML. The attribute ‘from_display_name’ will be used as the Caller ID name presented to the ‘to’ number. 

The string can have a maximum of 128 characters that can contain letters, numbers, spaces, and certain special characters, namely; - , _ , ~ , ! , and +.  

If users choose not to utilize this new attribute, the display name will default to the number in the ‘from’ field. 

For any questions about this new functionality, or if you’re interested in learning more about out Voice API,[ reach out](https://telnyx.com/contact-us "Contact Us") to our team of experts.  


Enhance outbound call personalization with Telnyx's TeXML functionality, allowing for custom Caller ID names.

Caller ID for outbound calls using TeXML

Set Caller ID on outbound voice with TexML

Users can set Caller ID on Outbound Calls generated using TeXML

As part of our goal to continuously improve our products for our customers, Telnyx has been working to improve the Conference Call feature in our Call Control product. 

As we have been developing the functionality of conferencing, we have not been charging users for this feature. Now that the conference call feature is fully functional, we’ll start charging users at a rate of __$0.002/ participant /minute__ from __August 15th, 2021 00:00 UTC__. 

Customers that use conferencing will see an automatic change in their billing from this date. 

If you're interested in learning how we bill for other features, take a look at our [Call Control Pricing](https://telnyx.com/pricing/call-control "Call Control Pricing").

<hr>

For questions about this change, you can reach out to our [support team](https://telnyx.com/contact-us "Contact Us"). 


Telnyx introduces billing for the Conference Call feature in Call Control, effective from August 15th, 2021.

Conference Call Billing Implementation

If you're using our conferencing feature, you'll start to see some changes in your billing. 

We're making updates to conference call billing

Telnyx voice API users can now receive webhooks when the dominant speaker changes in a conference call. 

Dominant speaker webhooks are automatically sent on conferences set up using the Call Control REST API. These webhooks have `event_type: "conference.floor.changed"`. An example webhook is contained in the [API reference documentation for creating a conference](https://developers.telnyx.com/api/call-control/list-conferences) with Call Control. The `call_leg_id` contained in this webhook is the leg that has been identified as the dominant (or "floor") speaker.

Dominant speaker detection can also be enabled for conferences set up using TeXML. Users should specify `statusCallbackEvent = "speaker"` as an attribute of the `<Conference>` noun. An example callback is shown in the [API reference documentation for the `<Conference>` noun](https://developers.telnyx.com/docs/voice/programmable-voice/texml-translator). The `CallSid` contained in this callback corresponds to the caller that has been identified as the dominant speaker.

Telnyx Voice API users can now receive webhooks when the dominant speaker changes in conference calls.

New Webhook: Identify Dominant Speaker in Call Control Conferences

Identify Leading Voices in Conferences

Telnyx generates new invoices on the second day of every calendar month. Currently, email notifications for new invoices are sent to the primary email address associated with your Telnyx account. Now, account owners can specify additional email addresses that will also receive notification for newly available invoices. Invoice notifications set up using this new functionality will contain your invoice __as an email attachment__ - perfect for sharing invoices across your organization without needing to share access to the Mission Control Portal.

This new capability is activated by using a new Event type in the [Notification Settings section of the Mission Control Portal](https://portal.telnyx.com/#/app/account/notifications/settings). The new event type sends a notification when a new invoice is available in the portal.

For more information on creating notifications in the Mission Control Portal, head over to our [knowledge base](https://support.telnyx.com/en/articles/4277896-notification-settings).

Telnyx users can add email addresses to receive invoices beyond the primary account email. Try now!

Send newly-created invoices to multiple email addresses

Telnyx users can now specify a list of email addresses (in addition to their account's primary email address) to receive newly available invoices for a given account.

# Verify API Product Release Notes

Today we’re making our Verify API generally available to everyone. Since launching our Verify Beta last December, we’ve received a lot of great feedback from our early users.

That’s why in addition to adding Flash Call & Voice channels back in May, we’ve now included verification via WhatsApp and integrated payment details for PSD2 compliant authentications.

Also, to be more in line with industry demands, we’ve changed our billing from an API request model to a ‘pay only for success,’ Authentication one. That means, you’re only billed when a recipient successfully completes a verification. 

<hr>

<br>

23, June 2021

<h2 id="june-23-2021">Send Two-Factor Authentication via WhatsApp</h2>

We're excited to announce that your Verify API now supports delivering a verification code through WhatsApp messages. 

With this new feature, we introduced an addition 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 add this feature.

<br>

## Updates to API Requests and Responses 
*In the code snippets below, existing features are in green, while new features are in red.*
<br> 

### Create a Verify Profile 
![Verify Profile Old request](//images.ctfassets.net/taysl255dolk/4mx0T6d0tvkZ7naaoLeleP/8e74e13862348b792e0c0488e3ecfc67/Verify_Profile__Old_request.png)
![Verify Profile New Response](//images.ctfassets.net/taysl255dolk/6O2rNc5BKWsySrfO5D1SUa/2e791dc41ca41720923655c8a340ddbc/Verify_Profile___New_Response.png)

### Update a Verify Profile 
![update verify profile](//images.ctfassets.net/taysl255dolk/6fQdZY72enRKu5NfWc9Jrz/6f68dc40b72ac90166b47035db17b807/update_verify_profile.png) 

![update verify profile response](//images.ctfassets.net/taysl255dolk/1KAPsFuS8OWFf7UUfrL0dv/56e6b4e83350230776398ef57ded0f77/update_verify_profile___response.png)

### 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}.__

![trigger verification request](//images.ctfassets.net/taysl255dolk/5San6E3tUw0aDm2IjtMHHU/91197fe01917aa30cd24db22e5c108cd/trigger_verification__request.png)![trigger verification response](//images.ctfassets.net/taysl255dolk/5FAJeUYF8K5ZyizenTQ9lm/ea9bf66167237c4986556b0eff5a26fc/trigger_verification__response.png)

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

### Submit a Verification
![submit verification code](//images.ctfassets.net/taysl255dolk/5Ydtu2htgD5fwXTEQrxZur/2582a31a938663e702fbb1ce39380c1d/submit_verification_code.png)

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

### List all Verify Profiles

![list all verify profiles](//images.ctfassets.net/taysl255dolk/4MXQoWEJOElfpqxKHTt7W8/9e0cf650d03b5ea5e1f980e5e08a201a/list_all_verify_profiles.png)

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

### Retrieve a Verify Profile 

![Retrieve a verify profile](//images.ctfassets.net/taysl255dolk/3Nc0VjCSloV0XbYBVdNdp1/880f03e58190ee1f1cfb253b0fdea8e3/Screen_Shot_2021-06-23_at_4.15.57_PM.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 

![Delete a Verify Profile ](//images.ctfassets.net/taysl255dolk/5QVnL07HqhTsUDIl3xqx7t/c29c3af7de1adf3cfda2f0f9f6d41de6/Screen_Shot_2021-06-23_at_4.22.51_PM.png)

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

### List Verifications by Phone Number

![List Verifications by Phone Number](//images.ctfassets.net/taysl255dolk/1qrHHYjOqTXuMFEIbGWPbI/396dabba64803442fb67596d9c3f6ea0/Screen_Shot_2021-06-23_at_4.24.05_PM.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

![Retrieve a Verification ](//images.ctfassets.net/taysl255dolk/46DlEBS5BDVODgYTCciTEg/bcdf1c1afcd8b30584e57b6aa5b4124f/Screen_Shot_2021-06-23_at_4.25.30_PM.png)

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

25, May 2021

<h2 id="may-25-2021">Verify API Voice, Flash Call, and API Updates</h2>

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.
<br>

## Updates to API Requests and Responses 
*In the code snippets below, existing features are in green, while new features are in red.*
<br> 
### 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.*

<br>
<br>

09, December 2020

<h2 id="december-9-2020">Introducing the Verify API</h2>

<br>

Verify API has reduced all of the unnecessary steps for sending 2FA codes to devices, making it easier than ever to secure login requests, confirm account changes, and authenticate devices. 

It takes just two steps in our [portal](https://portal.telnyx.com/#/app/verify/profiles) to set up a 2FA profile  with Telnyx Verify API.

- Step 1: Create a 2FA profile that contains the configurations for sending out two factor authentication codes.

- Step 2: Create a 2FA verification using the 2FA profile ID and the end user’s phone number.

To get started, you can access our in-depth [documentation](https://developers.telnyx.com/docs/identity/verify/quickstart) here. SDK updates on Python, Ruby, Node, PHP, Java, and .NET coming soon. 

Curious about Verify? [Talk to one of our experts](https://telnyx.com/products/verify-api#beta-form) today.


Telnyx Verify API makes it easy to send authentication codes via a growing number of channels.

Telnyx Verify API for Omnichannel Authentication

Verify API - Generally Available [RELEASE NOTES]

We're excited to announce that your Verify API now supports delivering a verification code through WhatsApp messages. 

With this new feature, we introduced an addition 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 add this feature.

<br>

## Updates to API Requests and Responses 
*In the code snippets below, existing features are in green, while new features are in red.*
<br> 

### Create a Verify Profile 
![Verify Profile Old request](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Verify_Profile_Old_request_a148a207e2.png)
![Verify Profile New Response](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Verify_Profile_New_Response_2973cc811b.png)

### Update a Verify Profile 
![update verify profile](https://pleasant-sunrise-e14682326c.media.strapiapp.com/update_verify_profile_81a502655f.png) 

![update verify profile response](https://pleasant-sunrise-e14682326c.media.strapiapp.com/update_verify_profile_response_77632fe5f8.png)

### 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}.__

![trigger verification request](https://pleasant-sunrise-e14682326c.media.strapiapp.com/trigger_verification_request_9b3b2d877e.png)![trigger verification response](https://pleasant-sunrise-e14682326c.media.strapiapp.com/trigger_verification_response_cc99cceb30.png)

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

### Submit a Verification
![submit verification code](https://pleasant-sunrise-e14682326c.media.strapiapp.com/submit_verification_code_6e5874bcb4.png)

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

### List all Verify Profiles

![list all verify profiles](https://pleasant-sunrise-e14682326c.media.strapiapp.com/list_all_verify_profiles_91e78a7826.png)

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

### Retrieve a Verify Profile 

![Retrieve a verify profile](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Screen_Shot_2021_06_23_at_4_15_57_PM_9cbbd9d0ba.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 

![Delete a Verify Profile ](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Screen_Shot_2021_06_23_at_4_22_51_PM_9092298b19.png)

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

### List Verifications by Phone Number

![List Verifications by Phone Number](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Screen_Shot_2021_06_23_at_4_24_05_PM_83f2173f48.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

![Retrieve a Verification ](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Screen_Shot_2021_06_23_at_4_25_30_PM_8c7785533e.png)

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

Telnyx Verify API offers WhatsApp as a channel to send two factor authentication codes

Send Two Factor Authentication Codes Via WhatsApp

We're excited to announce that your Verify API now supports delivering a verification code through WhatsApp messages. 

New Feature: Send Two-Factor Authentication via WhatsApp

We're excited to unveil call queueing capabilities, now available via the Telnyx Voice API, Call Control.

Users making API-enabled phone calls can now add calls to a queue using the [enqueue](https://developers.telnyx.com/api/call-control/dial-call) command, and remove calls from the queue using the [leave_queue](https://developers.telnyx.com/api/call-control/dial-call) command. Information about call queues can also be retrieved using [call queue commands](https://developers.telnyx.com/api/call-control/dial-call), including valuable alerting metrics:

-   The length of time a given call has spent in a queue
-   A given call's position in a queue
-   The number of calls and average call wait time in a given queue.

To take advantage of these new call queueing features in your application, get started by reading our [tutorial](https://developers.telnyx.com/docs/voice/programmable-voice/queueing-calls), browsing the [docs](https://developers.telnyx.com/api/call-control/dial-call). To learn more about how call queueing can work for your needs, [talk to an expert](https://telnyx.com/contact-us) today.

We're excited to unveil call queueing capabilities, now available via the Telnyx Voice API, Call Control.

Call Queueing with the Telnyx Voice API

New Feature Release: Call Queueing

At Telnyx, we know that it’s important for our customers to be able to track all aspects of their calls. Through our [partnership with QXIP](https://telnyx.com/resources/telnyx-qxip-sip-debugging "QXIP Partnership"), we've developed Quality of Service (QoS) reports for voice calls to help users troubleshoot call quality issues that may arise. 

Following on from the Winter release of the [Advanced SIP Debugging Tool](https://telnyx.com/release-notes/sip-trunking#nov-30-2020 "Advanced SIP Debugging Tool"), this new feature will give customers a visual representation of the Quality of Service (QoS) of any given call on a timeline with two separate graphics, one for each the RTP media streams that are established for each call.

The new report feature is available in the Mission Control Portal through the Advanced View of our SIP Debugging tool. Reports are based on RTCP reports that are sent between SIP devices and Telnyx:

![QoS Reporting Streams](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Qo_S_Image_2_1_9db9d97c19.png)
*RTP streams and RCTP reports between Telnyx and the user*

When a call is established media starts flowing over two RTP streams, one in each direction.  Periodically, each side also sends [RTCP reports](https://en.wikipedia.org/wiki/RTP_Control_Protocol "RTCP reports") to report transmission and reception statistics during the interval. Each report includes the number of packets sent (packets), the accumulated packets that were expected but never received (packets_lost), the jitter perceived from the received packets (ia_jitter), and more.

The QoS report feature uses the data on these RTCP reports to display 4 different quality metrics on a timeline for each RTP stream. Let’s take a look at what these metrics mean:

## MOS
[Mean Opinion Score](https://en.wikipedia.org/wiki/Mean_opinion_score "MOS") (MOS) is a value that represents the audio quality of the call as perceived by the reporter. it's calculated based on Jitter and Packets Lost values. The scale goes from 1 (Bad) to 4.5 (Excellent).

![MOS](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Selection_999_364_745bfe1ea9.png)

*Mean Opinion Score*

## IA Jitter
“Ia_jitter” represents the value of [Interarrival Jitter](https://en.wikipedia.org/wiki/Jitter "IA Jitter"), as measured by the reporter.

![IA Jitter](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Selection_999_365_0ac1b6bdf0.png)

*IA Jitter*

## Packets Lost 
“Packets Lost” represents the accumulated number of RTP packets perceived as lost by the reporter.

![Packets Lost](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Selection_999_366_2dff1285cf.png)

*Packets Lost*

## Packets 

“Packets” represents the accumulated number of RTP packets that were sent by the reporter.

![Packets](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Selection_999_367_11aada4ca8.png)

*Packets*

These quality metrics will enable users to quickly identify any issues that might have affected the quality of the call, which will speed up the troubleshooting process. 

Please note that in order to capture RTCP data from your calls you first need to enable RTCP capture for your Connections on the Mission Control Portal. You can do this by Editing your SIP connection and turning the RTCP Capture toggle to ‘on’.

![Edit your SIP Trunks](https://pleasant-sunrise-e14682326c.media.strapiapp.com/Editing_your_SIP_Trunks_0607_151e24e535.png)

*Edit your SIP connection. Turn the RTCP Capture toggle to 'on'.*

If you have any questions please don’t hesitate to reach out to our [team of experts.](https://telnyx.com/contact-us "Contact Us")

<hr>

[QXIP (QuickSIP)](http://qxip.net/ "QXIP") is an R&D company that specializes in open-source and commercial development of voice monitoring technology, based in Amsterdam, The Netherlands.

QoS Reports now available in Mission Control

QoS Reports for Voice Calls are now available in the Portal. (1).png

Dive deeper into your call quality with QoS reports in Mission Control. 

Telnyx adds Quality of Service (QoS) Reports for Voice Calls

Our newest feature allows users to troubleshoot call quality issues in Mission Control. 

New feature release: Quality of Service (QoS) Reports for Voice Calls

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.

<br>

## 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>. 

<br>

## 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.

<br>

## 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.

<br>

## 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

Release notes