Telnyx is happy to expand our public-switched telephone network (PSTN) replacement feature set to Slovakia! 

The PSTN replacement feature set includes inbound and outbound local calling; geographic, toll-free, and national number resources; emergency service-enabled numbers; guaranteed Calling Line Identity (CLI) passthrough; dual-tone multi-frequency (DTMF) signaling; and number portability.

Adding PSTN replacement in Slovakia brings the total number of countries where we offer this service to 33 and solidifies our position as a truly global voice provider. 

For more information on our PSTN replacement services [check out our blog](https://telnyx.com/resources/pstn-replacement "PSTN replacement "). 

Dive into enhanced telephony with Telnyx's PSTN replacement in Slovakia. 

Get PSTN-replacement numbers in Slovakia

Telnyx customers can now avail of PSTN replacement services in Slovakia, as we continue to expand globally. 

Telnyx adds PSTN replacement in Slovakia

We recently added local calling services to 14 additional countries–Albania, Argentina, Bosnia And Herzegovina, Bulgaria, Chile, Costa Rica, Georgia, Israel, Japan, New Zealand, Panama, Peru, Serbia and Thailand.

Local calling is the ability to pass calls over a national network and present numbers in the local format. Local calling gives calling parties using Telnyx CLIs the ability to guarantee localized CLI. Local calling typically provides increased quality, higher ACD (Average Call Duration) and reduced PDD (Post-dial delay).

You can get started with local calling from Telnyx by [signing in](https://portal.telnyx.com "Mission Control Portal") to your Mission Control Portal account and [purchasing a number](https://portal.telnyx.com/#/app/numbers/search-numbers "Number Search and Order") from any of the 48 markets where we offer this service.

Telnyx broadens local calling services to countries like Japan, New Zealand, and Israel. 

Telnyx expands local calling presence

Telnyx expands its global presence with local calling in an additional 14 countries worldwide. 

Telnyx adds local calling in 14 countries

Introducing Verified Numbers - the latest feature from Telnyx that allows you to confirm and display your non-Telnyx phone numbers as the calling line identification on calls made through the Telnyx platform.
With Verified Numbers, you can improve your caller’s trustworthiness and professionalism, and prevent fraudulent or spammy calls. The verification process is simple and can be done through the Mission Control Portal or the REST API, and you can choose your preferred verification method - either SMS or voice call.

More information can be found in our support center [here](https://support.telnyx.com/en/articles/6988813-verified-numbers).

*If you have questions about getting started [reach out](https://telnyx.com/contact-us "Contact Us") to a member of our sales team.* 

Using a phone number obtained from a different provider, not Telnyx, as the Caller ID for your outgoing calls is simple. 

Verify non-Telnyx numbers using Mission Control Portal

Enhance your caller’s trustworthiness with Verified Numbers - now available for all new Telnyx customers.

Use a Non-Telnyx Number as the Caller ID for Outgoing Calls

Today we’re excited to launch our new Number Requirements tool in the Mission Control Portal. 

As a global carrier, Telnyx offers customers the ability to purchase or port a wide variety of phone numbers across the globe. Depending on the country and number type, you may be required to provide additional information or documentation for orders to successfully process and phone numbers to activate.

This new tool allows Telnyx users to view the supplemental information or documentation required to activate numbers ahead of time. This will help our customers better plan number ports and orders so they can avoid unforeseen wait times and get communicating quickly. 

Take a look at a quick demo to see how it works:

<div style="position: relative; padding-bottom: 53.125%; height: 0;"><iframe src="https://www.loom.com/embed/c31f8fa2b3ef42d9b55b7c4f0ee9ee0a" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

*Note that this tool only retrieves information on numbers in regions that require supplemental information for number porting and ordering. Therefore countries with no requirements for number porting or ordering will return as null in this table.*

*If you have questions about country coverage please [reach out](https://telnyx.com/contact-us "Contact Us") to a member of our sales team.* 


Our new tool will help you understand what is required for you to port or purchase a number in a specific country. 

Find international number requirements in Mission Control

Telnyx users can now view the supplemental information or documentation required to activate numbers ahead of time. 

New International Number Requirements tool live in Mission Control

Today we’re happy to announce that Telnyx Mission Control SIP Trunking is now rated “Avaya Compliant” compatible with Avaya Aura and IP Office.

Avaya and Telnyx systems certified:

- 10890 Telnyx Mission Control SIP Trunking with Avaya Aura 10.1 with ASBCE 10.1
- 10891 Telnyx Mission Control SIP Trunking with IP Office 11.1

Avaya DevConnect promotes the development, compliance-testing and co-marketing of innovative third-party solutions that are compatible with standards-based Avaya solutions. Partners help customers extend the value of their collaboration and contact center investaments and accelerate the speed at which their organization delivers true value to to the bottom line. 

Through the Mission Control Portal, Telnyx delivers next-generation SIP Trunking servies. As a DevConnect partner, Telnyx delivers proven interoperability of their SIP Trunking services with Avaya customer engagement and small business portfolios so that companies can bring their own carrier. 

With Telnyx, customers can reduce network complexity, improve security and reliability and speed up time to deployment to quickly realize revenue benefits. 

Learn more about how [Telnyx is a part of Avaya’s DevConnect program](https://www.avaya.com/en/partners/devconnect/gallery/). 


Telnyx Mission Control SIP Trunking is now rated “Avaya Compliant” compatible with Avaya Aura and IP Office

Telnyx SIP Trunking rated Avaya Compliant in 2022

Telnyx Mission Control SIP Trunking is now rated “Avaya Compliant” compatible with Avaya Aura and IP Office. 

Telnyx Mission Control SIP Trunking now rated Avaya Compliant

Starting December 16, 2022, prices for Answering Machine Detection services will change as follows:

- Standard Answering Machine Detection will be charged at $0.0020 per invocation.
- Premium Answering Machine Detection will increase from $0.0050 to $0.0065 per invocation.

__What do I need to do?__

You do not need to make any changes. After December 16, 2022, charges for Answering Machine Detection services reflective of these new prices will appear on your Telnyx invoice.

If you have any further questions about this change, please reach out to our support team using the chat function in the portal.


Starting December 16, 2022, prices for Answering Machine Detection services from Telnyx will change as follows.

Changes to prices for Answering Machine Detection services

Starting December 16, 2022, prices for Answering Machine Detection services will change as follows.

## What is a boundary elimination overlay?
A boundary elimination overlay for the Phoenix metro area means the three area codes serving the Phoenix metro area will all serve the same geographic area. There will no longer be a boundary between the 480, 602 and 623 area codes; instead, the three area codes will all serve the same combined geographic region. 

A boundary elimination overlay does not require telephone users to change their existing area code or phone number. It also does not change the way you dial calls. You’ll still use 10-digit dialing; dial the area code and phone number for all local calls, just as you do now.

## Who is affected?
__Beginning February 11, 2023, anyone with a 602 or 623 area code should begin using 10 digits__ (area code + phone number) when dialing all local calls (Mandatory 10-digit dialing has already been implemented in the 480 area code). This includes all local calls which currently allow 7-digit dialing. During the permissive 10-digit dialing period, if you forget and only dial 7 digits, your calls will still complete. The permissive 10-digit dialing period will remain in place until August 12, 2023. 

__Beginning August 12, 2023, 10-digit dialing will become mandatory__ for anyone with a 602 and 623 area code, and their calls that do not include the area code will not complete. If you forget and only dial 7 digits, you will hear a recorded message that advises you to include the area code, and you will need to hang up and re-dial your call including the area code.

### What do you need to do?
Customers in the overlay region should:

- Dial 1 + area code + phone number for all local calls
- Identify and store phone numbers as 10-digit numbers (always include the area code, even if the number is local)
- Update your equipment if needed to ensure it is programmed for 10-digit dialing (for example: fax machines, medical alert devices, alarm systems, voicemail, and call forwarding settings)
- Ensure that all personal and business items include your area code (for example: pet ID tags, business cards, and advertising material)

### What remains the same?
The following will remain the same for customers nationwide:

- Your current telephone number
- The price of a call, coverage area or other rates 
- What is considered a local call
- The way you dial a phone number (you will still use 10-digit dialing for local calls, and 1+10 digits for long distance)
- Dialing existing 3-digit numbers such as 911, 211, 311, and so on 

## If you have questions…
If you have questions regarding this notice, please visit the [Arizona Corporation Commission website](https://www.azcc.gov/utilities/telephone/all-about-area-codes). 


Phoenix's area code update: 480, 602, and 623 serve the same area. Get 10-digit dialing for all local calls, essential after August 12, 2023.

Area code boundary elimination overlay in the Phoenix, Arizona region

If you’re located in the Phoenix metropolitan area, three area code boundaries will be eliminated near you. Here’s what you need to know:

Phoenix's unified area code update

We're excited to debut [Telnyx Storage](https://telnyx.com/products/cloud-storage) in beta. Businesses and developers building data-rich apps and experiences can now access our S3-compatible API. 

Simply [log into your Mission Control Portal account](https://portal.telnyx.com/) to start creating your first buckets.

We're excited to debut Telnyx Storage in open beta. Businesses and developers building data-rich apps and experiences can now access our S3-compatible API. 

Telnyx Storage is now available in open beta

Earlier this year [Telnyx announced](https://telnyx.com/release-notes/voice-api-dialogflow-integration "Dialogflow ES integration") an integration with Telnyx Voice API and Dialogflow ES (Essentials) that enabled Telnyx voice customers to send audio calls to Dialogflow ES and receive a response from the call bot. 

Today, Telnyx is excited to expand on this effort through the integration with Dialogflow CX (Customer Experience) and the Telnyx Voice API. 

__What is the difference between Dialogflow ES and CX?__

[Dialogflow](https://cloud.google.com/dialogflow/es/docs "Google Dialogflow") is a natural language understanding platform from Google that aims to make it easy for developers to design and integrate a conversational user interface into a range of communication applications built based on Voice APIs. 

Dialogflow CX is a more advanced agent type than the ES model, and is designed to meet the needs of larger, enterprise organizations that are dealing with more sophisticated agents. 
Dialogflow can respond with either synthetic speech played on the call or text formats in webhooks, which you can customize to your application. 

Users can get started with the integration by following our [developer tutorial](https://developers.telnyx.com/docs/voice/programmable-voice/dialogflow-es). 

Telnyx expands its Voice API capabilities with Dialogflow CX integration.

Dialogflow CX integration with Telnyx Voice API

Telnyx launches Dialogflow CX integration

Telnyx Voice API now supports integration with Dialogflow CX

We are excited to announce that Direct Routing from Telnyx is now generally available with support for Dynamic Location Routing (DLR).

__What is Dynamic Location Routing?__

Dynamic Location Routing is required for VoIP providers to comply with the most up-to-date e911 guidelines–[Kari’s Law and the Ray Baum Act](https://telnyx.com/resources/karis-law-ray-baum "Kari's Law and Ray Baum Act").

Presence Information Data Format – Location Object (PIDF-LO) is a XML tag format that allows the precise location data to be sent in a SIP header which can then be used by Emergency Services at Public Safety Answering Points (PSAPs). 

__Why is PIDF-LO important for DLR?__

PIDF-LO means emergency services have the precise location where the 911 call is being made from, meaning they can send assistance to where the person is located. 

With PIDF-LO now supported for Direct Routing, Microsoft Teams users will be able to benefit from DLR. When a call is placed to 911 services, the location of the worker–down to the suite or floor–will be passed through to the correct PSAP.

You can get started with Direct Routing for Microsoft Teams by following the [setup guide](https://developers.telnyx.com/docs/voice/sip-trunking/microsoft-teams "Direct Routing for Microsoft Teams Setup") [reaching out](https://telnyx.com/contact-us "Contact Us") to a member of our team. 

Telnyx's Direct Routing for Microsoft Teams now supports DLR for enhanced e911 compliance. Discover PIDF-LO's role in precise location data.

Dynamic Location Routing support now available with Direct Routing from Telnyx

We are excited to announce that Direct Routing from Telnyx is now generally available with support for Dynamic Location Routing (DLR).

DLR Support for Microsoft Teams

We are excited to announce that from today, all [Telnyx Voice API](https://telnyx.com/products/voice-api "Telnyx Voice API") services are available in the EU. This represents another milestone in our ongoing effort to deliver world-class communication and connectivity services all across the globe. 

Telnyx users in Europe can now access Voice API services through a dedicated european endpoint—[api.telnyx.eu](https://portal.telnyx.com/#/login/sign-in). While using this endpoint, all calls, recordings and other services related to Telnyx Voice API will be processed by our datacenter located in Frankfurt, Germany. 

To receive Voice API calls in Europe, Telnyx users must set the anchorsite for the specific Voice API application to either Frankfurt, Amsterdam or London. In addition, all the participants of the conference and the calls that are added to the queue must be in the same region. 

European customers that utilize api.telnyx.eu should notice reduced latency in their calls as they are handled locally.

To see how you can anchor your media in Europe, take a look at [our guide](https://developers.telnyx.com/docs/voice/programmable-voice/voice-api-services-in-europe). If you would like to learn more about our Voice API offering or other European services, [reach out](https://telnyx.com/contact-us "Contact Us") to a member of our team.

*Note: Telnyx users that utilize premium answering machine detection will not be able to avail of [api.telnyx.eu](https://telnyx.com/release-notes/telnyx-expands-voice-api-services-europe).*


Telnyx strengthens its global presence with Voice API services in Europe. Enjoy local processing in Frankfurt and anchor media in key European cities.

Telnyx Voice API services now available in Europe

Telnyx users can now access Voice API services in Europe

Telnyx expands Voice API services to Europe

Telnyx customers can now enjoy a smoother experience when registering their toll-free messaging use cases.

Use case registration is required by the industry for sending messages from a toll-free number (TFN). Come September 30th, 2022, messaging traffic from TFNs without a registered use case may be blocked. Telnyx has been working to create an easier registration process for users ahead of this deadline. You can now complete this registration in two ways–by submitting [this form](https://docs.google.com/forms/d/18A-lyp1-S4J56FGgH7cjtEhqHfsg4SlDjQgVwKBdSgQ/closedform) or via the new API. 

Registration via the API allows for added flexibility and visibility, including bulk use case submissions and ability to track status of submitted TFNs. Visit our [developer documentation](https://developers.telnyx.com/docs/messaging/toll-free) to set up toll-free use case registration by API, or review our [support knowledge base](https://support.telnyx.com/en/articles/5353868-toll-free-messaging) for further information on toll free messaging.


Register your toll-free messaging use cases with Telnyx's new API. Streamline the process, submit in bulk, and track TFN statuses for industry compliance.

The Telnyx Messaging API now supports toll-free messaging use case registration.

Release notes