We are excited to announce that, as of today, Telnyx supports emergency calling with dynamic locations in the US and Canada. 

Before this we offered regular E911, which is non-dynamic emergency calling for numbers. This will continue to be an available option for non-US or Canada numbers.

RAY BAUM’s Act states that, by 2022, enterprises operating Multi-Line Telephone Services (MLTS) will be required to provide dispatchable location information at the time of all 911 calls. Telnyx’s Dynamic E911, also known as E911 with Dynamic Location Routing, can help get you there. Unlike traditional emergency calling where the emergency-enabled phone number is associated with a specific address, Dynamic E911 phone numbers are decoupled from addresses, and instead associated with an end user. In order to utilize Dynamic E911, Telnyx users must now define end users at onboarding. 

Accurate location information of the end user is sent at the time of a 911 call using PIDF-LO (Presence Information Data Format-Location Object). 

To test out the new API, head over to our Developer Guide. If you’d like to know more about our emergency calling capabilities, reach out to our [team of experts](https://telnyx.com/contact-us "Contact Us").

Dynamic e911 provides accurate location information at the time of a 911 call.

e911 with Dynamic Location Routing now available

Dynamic e911 provides accurate location information at the time of an emergency call using Dynamic Location Routing. 

Available Now: Dynamic e911

From today, Telnyx now supports premium answering machine detection (AMD) on our Voice API. This feature will increase the accuracy of voicemail detection, so your businesses can deliver the right messages, at the right time. 

Premium AMD uses advanced speech recognition technology and a machine learning process to achieve exceptional accuracy in determining whether a call has been connected to a live person or an answering machine. This feature can make more granular classifications of the call result by identifying, silence, an answering machine greeting, a human residence greeting, or a human business greeting, giving businesses a greater understanding of where their calls are ending up. 

When a call is answered, the premium AMD software runs real-time detection and sends a ‘call.machine.premium.detection.ended` webhook with one of the following results: 

- `human_residence`, 
- `human_business`, 
- `machine`, 
- `silence` or 
- `fax_detected`. 

If a beep is detected a `call.machine.premium.greeting.ended` webhook with the result of `beep_detected` is also sent. If a beep is detected before `call.machine.premium.detection.ended` only a `call.machine.premium.greeting.ended` webhook is sent. If a beep is detected after `call.machine.premium.detection.ended`, both webhooks will be sent.

Premium answering machine detection is now available with pricing listed [here](https://telnyx.com/pricing/call-control). Get started with answering machine detection by following the guide in our [developer docs](https://developers.telnyx.com/docs/voice/programmable-voice/answering-machine-detection). 

For more information about how premium AMD can help your business, check out our [product page](https://telnyx.com/products/voice-api) or [get in touch](https://telnyx.com/contact-us "Contact Us") with our team of experts.

Boost your call accuracy with Telnyx's premium Answering Machine Detection. Identify human greetings, machines, and silences for just $0.005/call leg.

Premium Answering Machine Detection from Telnyx

Make more accurate classifications with premium Answering Machine Detection from Telnyx

Telnyx releases premium Answering Machine Detection

Today, we’re excited to announce the beta release of Telnyx Video Rooms. 

Video Rooms allows customers to leverage our multi-cloud infrastructure to build customizable, scalable, programmable video applications. Video Rooms supports multiple different types of high-quality media including webcam video streams, screen-sharing, and audio to enable rich interactions between participants, no matter where they are in the world. This is all made possible by the Telnyx network -  a class-leading private, global backbone for your video, voice, and texting communications.

As this isn’t your typical out-of-the-box video solution, you can choose which features to build into your application. With Telnyx Video Rooms, you can have granular control over audio and video streams, screen sharing, dominant speaker detection, and more. 

You can start building your custom experience by [signing up](https://telnyx.com/sign-up "Sign Up") to the Mission Control Portal and following the guide over on our developer site. 

Video Rooms will be kept in beta while we’re working to build more functionality and stability into the product. As you work to build your ideal video experience, we’d love your feedback and ideas on how we can build a better product that is more suited to your needs. To give your feedback, [reach out](https://telnyx.com/contact-us "Contact Us") to our sales team.

If you’re looking for assistance within the portal or with our docs, you can contact a member of our support team at any time through the bottom right-hand corner of the screen.

We can’t wait to see what you build.


Video Rooms Beta

Build customizable, scalable, programmable video experiences with Telnyx Video Rooms.

Telnyx Video Rooms now in Beta

We’re opening our latest Video product to beta users

New Product Beta- Telnyx Video Rooms

In the past year, Telnyx has added PSTN replacement capabilities in a number of countries outside of the US. To enhance the experience of our growing customer base outside of the US, we have made updates to the International Number Search and Order process. These changes will automate the process and give users instant visibility into the required documentation, end-user information, and emergency services requirement to purchase and activate international numbers.

We’ve amended our existing API and implemented a new API to overcome constraints with the international number ordering and porting process. 

Users will be able to check out and reserve international numbers for 48 hours. Within this 2-day period users will be sent notifications to gather the documents required to purchase the international numbers. If the documentation is not provided within the time period, the numbers will be released. If the documents are provided within the 48 hours, the purchase will move to a Telnyx internal review.

We’ve also updated the UI in Mission Control Portal to streamline the process of international number ordering. 

With the new view of the Orders tab it’s easier to see requirements for Sub Orders and provide the documentation to fulfil these requirements, all with just a few clicks. In the view for each Sub Order there’s also a Communications section where customers can speak to a Telnyx representative about that specific Sub Order.

For more information on our latest release, [check out our blog](https://telnyx.com/resources/international-number-search-and-order-made-easy "International Number Search and Order"). To test out the new API, head over to our [Developer Docs](https://developers.telnyx.com/docs/numbers/phone-numbers/international-number-search) to see for yourself how easy it is to implement. If you’d like to know more about our international numbering capabilities, reach out to our [team of experts](https://telnyx.com/contact-us "Contact Us").


International Search and Order

We've updated our international search and order to make it easier to buy numbers, all around the world. 

International Number Search and Order Updates

We've updated our Number Search and Order APIs to make it even easier to buy numbers, all around the world. 

Telnyx updates International Number Search and Order

Today we are releasing two additional values to the verstat parameter to provide customers with more granular information on call attestation and verification results.  

Initial SHAKEN/STIR implementation introduced a verification feature, a *verstat* parameter, that is included in the *P-Asserted-Identity* SIP header. The *verstat* parameter includes information about the caller identity validation and attestation level, with possible values of TN-Validation-Passed, TN-Validation-Failed or No-TN-Validation depending on verification results of the PASSPorT and attestation level. This verification is done for inbound calls from the PSTN as well as on-net calls from Telnyx customers to other Telnyx customers.

Following Telnyx efforts to improve the SHAKEN STIR framework, we are introducing additional values to the *verstat* parameter. These new values will provide Telnyx customers with more granular information regarding originating Caller ID attestation and verification results.

As of today, the possible values are as follows:

|      |      |      |      |
| ---------- | ---------- | ---------- | ---------- |
|      | __`Verstat Value`__       | &nbsp;        | __Description__       |
|      | `TN-Validation-Passed`       | &nbsp;        | Identity header verification successful and call has an A attestation        |
|      | `TN-Validation-Failed`       | &nbsp;        | Identity header verification failed        |
|      | `No-TN-Validation`       | &nbsp;        | No verification took place because Identity header was not provided       |
|*__NEW__* &nbsp; | `TN-Validation-Passed-B` &nbsp;        | &nbsp;        | Identity header verification successful and call has a B attestation       |
|*__NEW__* &nbsp; | `TN-Validation-Passed-C` &nbsp;        | &nbsp;        | Identity header verification successful and call has a C attestation       |

<br/>

For more information on the SHAKEN/STIR framework check out our [resource center](https://telnyx.com/resources "Resource Center") or reach out to our [team of experts](https://telnyx.com/contact-us "Contact Us").


With the new verstat parameters, you'll receive more detailed information about caller ID attestation and verification results.

Introducing new SHAKEN/STIR verstat parameters 

We've added two new verstat parameters to give you more insights into SHAKEN/STIR call verification and attestation results. 

New SHAKEN/STIR verstat parameters

Telnyx has been fully SHAKEN/STIR compliant since June 30th, 2021. We have been attesting to all calls originating on the Telnyx network, and passing the identity header on to the recipient for inbound calls that have been signed by the originating provider. However, customers have not able to view the attestations.

As of today, customers will have visibility into attestations via the ability to check SHAKEN/STIR call compliance by consulting Call Detail Records (CDRs) on Reporting Detail Reports.

Telnyx CDRs will now present an additional field, “Stir Shaken,” that can have the following values:
- A
- B
- C
- Unavailable
- Invalid

For inbound calls Telnyx will verify the content of the Identity header and for outbound calls Telnyx will authenticate and generate an Identity header. The results for both authentication and verification will be added to the CDR that can be retrieved by Telnyx users through Mission Control Portal.

For inbound calls (calls from the PSTN to Telnyx customers), Caller ID SHAKEN/STIR results in the CDR are mapped in the following way:

|     |      |      |      |     |      |      |
| ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
| __SHAKEN/STIR Identity__       | &nbsp; &nbsp; &nbsp;       | __Attestation__       | &nbsp; &nbsp; &nbsp;       | __Validation__       | &nbsp; &nbsp; &nbsp;       | __CDR “Stir Shaken” Value__       |
| Provided         |        | A       |        | Passed       |        | A       |
| Provided      |        |B      |        | Passed       |        | B       |
| Provided       |        | C       |        | Passed       |       | C       |
| Provided      |        | -       |        | Not Passed       |        | Invalid       |  
| Not Provided      |        | -       |        | -     |        | Unavailable       |  

<br>

For outbound calls (calls from Telnyx to the PSTN), Caller ID SHAKEN/STIR results in the CDR are mapped in the following way:

|     |      |      |      |     |      |      |
| ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
| __SHAKEN/STIR Identity__       | &nbsp; &nbsp; &nbsp;       | __Attestation__       | &nbsp; &nbsp; &nbsp;       | __Validation__       | &nbsp; &nbsp; &nbsp;       | __CDR “Stir Shaken” Value__       |
| Provided         |        | A       |        | Passed       |        | A       |
| Provided      |        |B      |        | Passed       |        | B       |
| Provided       |        | C       |        | Passed       |       | C       |

<br> 

This capability is only applicable to US domestic calls (calls from +1 prefix to +1 prefix)

For on-net calls, please ensure you register with your credentials connection via TCP or for IP/FQDN connection please specify TCP as the inbound transport protocol. This will help to prevent packet fragmentation and call completion issues.

<br>

For more information on the SHAKEN/STIR framework check out our [resource center](https://telnyx.com/resources "Resource Center") or reach out to our [team of experts](https://telnyx.com/contact-us "Contact Us").


Telnyx's CDRs now feature SHAKEN/STIR attestation values. Monitor call authenticity, ensure compliance, and elevate your communication standards.

SHAKEN/STIR attestation in Call Detail Records

You can now view your SHAKEN/STIR call attestations.

SHAKEN/STIR attestation is now available in Call Detail Records

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.

Release notes