## New Features: We're updating our fax webhooks

![Page Count Webhook Updates](//images.ctfassets.net/taysl255dolk/7rmXAJ8DmqyiLu47kQJT9c/295d4c15a6b58d55dd490f88fcf1b3ff/Page_numbers_fax_webhooks.png)

At Telnyx we’re all about transparency. That’s why we’re adding a helpful new feature to our Fax API. 

As our fax customers know, we bill our fax product by the page but, until now, we haven’t included the page number in the fax resources or the webhook that gets delivered to the user. We recognize that this could make it unnecessarily difficult to reconcile invoices and organize internal billing for our customers. 

With that said, we’ll soon be introducing a <code>page_count</code> parameter on both the fax resources and the inbound and outbound webhooks. We hope this will help users to keep track of their fax invoicing and billing. 

The new webhooks with the page count field will look like:

## Inbound Webhook Example

<code>
{ 
&nbsp; "data": { 
&nbsp;&nbsp; "event_type": "fax.media.processing.started", 
&nbsp;&nbsp; "id": "ebe6b30f-69fc-4f5d-8e2b-d0705ad53c77", 
&nbsp;&nbsp; "occurred_at": "2021-02-11T10:30:52.578108Z", 
&nbsp;&nbsp; "payload": { 
&nbsp;&nbsp;&nbsp; "connection_id": "1453742805816968295", 
&nbsp;&nbsp;&nbsp; "direction": "inbound", 
&nbsp;&nbsp;&nbsp; "fax_id": "359c0d23-fe39-49f1-8814-f7490197a576", 
&nbsp;&nbsp;&nbsp; "from": " 13122010119", 
&nbsp;&nbsp;&nbsp; "page_count": 2, 
&nbsp;&nbsp;&nbsp; "status": "media.processing", 
&nbsp;&nbsp;&nbsp; "to": " 13127283148", 
&nbsp;&nbsp;&nbsp; "user_id": "9fd26e62-38b3-4fa3-87df-5a9a2c62037e" 
&nbsp;&nbsp;&nbsp; }, 
&nbsp;&nbsp; "record_type": "event" 
&nbsp;&nbsp; }, 
&nbsp; "meta": { 
&nbsp;&nbsp; "attempt": 1, 
&nbsp;&nbsp; "delivered_to": "insertLocalHost/test/callback/status" &nbsp; 
&nbsp;&nbsp; } 
} 
</code>

## Outbound Webhook Example

<code>
{ 
&nbsp; "data": { 
&nbsp;&nbsp;"event_type": "fax.delivered", 
&nbsp;&nbsp;"id": "053a9845-f56e-4a11-877e-f9799fda8a8c", 
&nbsp;&nbsp;"occurred_at": "2021-02-11T10:30:52.463128Z", 
&nbsp;&nbsp;"payload": { 
&nbsp;&nbsp;&nbsp; "call_duration_secs": 30, 
&nbsp;&nbsp;&nbsp; "connection_id": "1453742805816968295", 
&nbsp;&nbsp;&nbsp; "direction": "outbound", 
&nbsp;&nbsp;&nbsp; "fax_id": "b8278a9b-a112-4152-bb7e-d6610b0d20f3", 
&nbsp;&nbsp;&nbsp; "from": " 13122010119", 
&nbsp;&nbsp;&nbsp; "original_media_url": "insert URL", 
&nbsp;&nbsp;&nbsp; "page_count": 2, 
&nbsp;&nbsp;&nbsp; "status": "delivered", 
&nbsp;&nbsp;&nbsp; "to": " 13127283148", 
&nbsp;&nbsp;&nbsp; "user_id": "9fd26e62-38b3-4fa3-87df-5a9a2c62037e" 
&nbsp;&nbsp;&nbsp;}, 
&nbsp;&nbsp;"record_type": "event" 
&nbsp;&nbsp; }, 
&nbsp; "meta": { 
&nbsp;&nbsp;"attempt": 1, 
&nbsp;&nbsp;"delivered_to": "local host/test/callback/status" 
&nbsp;&nbsp; } 
} 
</code>

This change will be made effective on __February 19th, 2021__. 

You can stay up to date with any changes to our Fax API by keeping an eye on the docs on our [developer center](https://developers.telnyx.com/docs/programmable-fax/get-started). 

As always, if you have any questions feel free to [reach out to our support team](https://telnyx.com/contact-us "Contact Us")- they’re on call 24/7/365.

We always want to be improving our transparency at Telnyx. We have added a new feature to our Fax API to now include page counts in the webhooks

New Feature: We're Updating our Fax Webhooks

As our fax customers know, we bill our fax product by the page but, until now, we haven’t included the page number in the fax resources or the webhook that gets delivered to the user.

## New Features: We've made changes in an inbound webhook

![Changes to inbound webhook](//images.ctfassets.net/taysl255dolk/1GSIe0FLdGe4iwUeiXglK2/f6c2bf00c1b3202065c4119d3ead66e7/Fax_Webhook_Release_Notes.png)

Telnyx is notifying our Programmable Fax API users of an __upcoming change to webhooks__ you receive from Telnyx. 

Inbound fax webhooks notify you when a fax is received to one of your Telnyx phone numbers. From 16th, February 2021, webhooks associated with inbound faxes will be formatted to include a new <code>partial_content</code> field. 

The new field being added to the inbound fax webhooks will show when a file in an incoming fax transmission has been partially received. This may happen if issues have prevented a fax's contents from being fully transmitted. The <code>media_url</code> field which currently exists in inbound fax webhooks will contain the part of the fax contents which was successfully transmitted. 

In order to ensure that your integrations are unaffected, you should update any application code you have written which processes webhooks from the Telnyx Programmable Fax API to accommodate this new <code>partial_content</code> field. 

No data or fields are being removed from inbound fax webhooks.

You can read the documentation for the Telnyx Programmable Fax API, in our [developer center](https://developers.telnyx.com/docs/programmable-fax/get-started). 

If you have any further questions about this change, [reach out to our team](https://telnyx.com/contact-us "Contact Us").

We are changing some inbound webhooks by adding in a field showing whether an incoming transmission has been partially or fully received.

New Features: We've made changes in an inbound webhook

Inbound fax webhooks notify you when a fax is received to one of your Telnyx phone numbers. From 16th, February 2021, webhooks associated with inbound faxes will be formatted to include a new partial_content field.

We've implemented a bug fix to prevent audio playback from being interrupted on calls.

When gathering user inputs using the <a href="https://developers.telnyx.com/docs/voice/programmable-voice/texml-translator#gather" title-"Call Control API Reference | Telnyx Developers">TeXML <code>&lt;Gather&gt;</code> verb</a> or the <a href ="https://developers.telnyx.com/api/call-control/dial-call" title-"Call Control API Reference | Telnyx Developers"><code>gather_using_audio</code> Call Control command</a>, audio can be played to prompt the user. In this situation, a user's keypad button presses will interrupt the audio playback.

However, when playing custom audio on a call, using either the <a href="https://developers.telnyx.com/docs/voice/programmable-voice/texml-translator#play" title-"Call Control API Reference | Telnyx Developers">TeXML <code>&lt;Play&gt;</code> verb</a> or the <a href ="https://developers.telnyx.com/api/call-control/start-call-streaming" title-"Call Control API Reference | Telnyx Developers"><code>playback_start</code> Call Control command</a>, and without specifying any input gathering, audio could unintentionally be interrupted by a user pressing the <code>*</code> key on their phone keypad.

Now, when custom audio is being played on a call using the TeXML <code>&lt;Play&gt;</code> verb or the Call Control <code>playback_start</code> command, and no input gathering is active, the audio will not be interrupted by any button presses unless the call is hung-up.

Find out how your fellow developers have been using custom audio playback - join our [Developer Slack Community](https://joinslack.telnyx.com/) today!

We've implemented a bug fix to prevent audio playback from being interrupted on calls.

Improved Audio Result Of Recent Bug Fix

We've implemented a bug fix to prevent audio playback from being interrupted on calls.

When gathering user inputs using TeXML or the gather_using_audio. Call Control command, audio can be played to prompt the user. In this situation, a user's keypad button presses will interrupt the audio playback.

Bug Fix: Improving Custom Audio Playback Behavior

## Public IP Mapping

![Public IPs](//images.ctfassets.net/taysl255dolk/2psF6ZVcmezv8OhMSdlZmu/7bf7f1a528ed73f4a03c15fd1b405313/New_Feature__Public_IP_Mapping.jpg)

We’re excited to share our newest feature for Telnyx Wireless: you can now map public IPs to your Telnyx [SIMs](https://telnyx.com/products/iot-sim-card) with a few simple clicks via the Telnyx API or Mission Control Portal. Public fixed IPs empower you to advertise your connected devices on the public internet at any time from any location. 

We’ve added this feature to expand the usability of our IoT SIMs -- public IPs enable you to connect to your SIM rather than just from it, making it easier to scale your IoT solution. [IoT SIM cards](https://telnyx.com/products/iot-sim-card) with public IPs will also provide value to managed service providers (MSPs), who can use their SIMs for LTE failover for their PBX system. When a failure is detected, MSPs can immediately failover to LTE, minimizing downtime on their services.

If you’re interested in adding a public IP to your SIM, head over to our [Mission Control Portal](https://portal.telnyx.com "Mission Control Portal") or our [API](https://developers.telnyx.com/docs/iot-sim), where you can: 

- Upgrade SIM cards to using a public static IP for $3 per month.
- Delete public IP addresses on SIMs.
- View public IP address costs in your invoice.

4, February 2021

You can now map public IPs to your Telnyx SIM making it easier for you to scale your IoT solution.

Map Public IPS to your Telnyx SIM

We’re excited to share our newest feature for Telnyx Wireless: you can now map public IPs to your Telnyx SIMs with a few simple clicks via the Telnyx API or Mission Control Portal.

Public IP Mapping

## Public IP Mapping: Mission Control Portal UI

We’re excited to announce that we’ve made some updates to our Mission Portal Control interface to make it easier to upgrade SIM cards to use a public static IP. Now, with a click of a button, you can make this change and see the monthly recurring charge in billing. 

In the Wireless section of the Portal, under "SIM Cards" you'll see a button that says "Set Public IP." 

![Public IP mapping Telnyx Mission Control Portal](//images.ctfassets.net/taysl255dolk/5IyoDI2K0lP9CJfJeRWlRO/d439a61c6ce654bfe1564c4aefd1b922/Public_IP_mapping_Telnyx_Mission_Control_Portal.png)
 

Once you click that button, you'll see a notification for a three dollar monthly recurring charge for the Public IP. Once you click accept, your SIM will have a Public IP!

![Public IP Mapping Telnyx](//images.ctfassets.net/taysl255dolk/6mAQFIdDgCNrOplMR0kqLH/da94449a856dbc195c25eb75725f6a9b/Public_IP_Mapping_Telnyx.png)

We've made it easier to upgrade SIM cards for use with public static IPS in the Mission Control Portal.

Public IP Mapping: Mission Control Portal UI

We’re excited to announce that we’ve made some updates to our Mission Portal Control interface to make it easier to upgrade SIM cards to use a public static IP.

Managing multiple organizations through the Mission Control Portal and Telnyx API just got a lot easier. We're thrilled to introduce [Managed Accounts](https://developers.telnyx.com/docs/account/managed-accounts) as a limited-release feature, enabling qualifying users to create sub-accounts with advanced management features.

 

## What is a Managed Account?

A Managed Account is a sub-account created from within an existing Mission Control Portal account (which we call a __manager__ account). Manager accounts have advanced control over pricing, reporting, administration, and billing functionalities of Managed Accounts:

 

### Pricing and Reporting:

- Managed Accounts inherit pricing from their manager accounts. If your organization has a [committed use agreement](https://telnyx.com/contact-us) for lower rates, your Managed Accounts will have those rates automatically.
- Pricing is hidden from Managed Accounts. Only the manager accounts that administer Managed Accounts are able to view pricing.
- Managed Accounts can generate reports on their own usage, without viewing their pricing.

 

### Administration:

- Manager accounts can log into any one of their Managed Accounts via the portal to view that Managed Account's usage and balance, and configure that Managed Account's settings.
- Manager accounts can also create an API key associated with a Managed Account, and control the Managed Account via the [Telnyx API](https://developers.telnyx.com/api/managed-accounts/list-managed-accounts).

 

### Billing:

- Managed Accounts have their own account balances, payment methods, and invoices.

 

## What can I do with Managed Accounts?

Managed Accounts are an intuitive way of administering multiple accounts and users from one unified interface. [Managed Service Providers](https://telnyx.com/use-cases/managed-service-providers) can use Managed Accounts to easily manage each of their individual customers while allowing them the freedom to log into their Managed Account and configure their communications.

 

## How can I get started with Managed Accounts?

Managed Accounts will be rolled out to all Telnyx users in the coming months. To access an early-release preview, [reach out to our sales team](https://telnyx.com/contact-us).

To learn more about Managed Accounts, jump over to our [Developer Center](https://developers.telnyx.com/docs/account/managed-accounts).

Portal_ManagedAccounts_ReleaseNotes_1200x450.svg

Managed Accounts allows Managed Service Providers (MSPs), VoIP Resellers and Organizations to manage multiple customers' billing & admin. Sign up today!

Telnyx User Portal: Managed Accounts for MSPs and Resellers

We're thrilled to introduce Managed Accounts as a limited-release feature, enabling qualifying users to create sub-accounts with advanced management features.

Introducing Managed Accounts in the Mission Control Portal

## Expanded Docs for our WebRTC JavaScript Client

It's now easier than ever to embed the full power of the Telnyx Voice API into your web browser. We've updated and expanded our API reference documentation for the Telnyx WebRTC JavaScript Client.

Our updated docs contain in-depth information and examples around three core parts of the SDK:

- The [TelnyxRTC](https://developers.telnyx.com/docs/voice/webrtc/js-client) client connects your application to Telnyx, enabling you to make outgoing calls and handle incoming calls.
- A [call](https://developers.telnyx.com/docs/voice/webrtc/js-call) represents a one-to-one audio or video call between browsers, [SIP clients](https://support.telnyx.com/en/articles/2925713-sip-uri-calling), or phone numbers.
- A [notification](https://developers.telnyx.com/docs/voice/webrtc/js-notification) is an event sent by Telnyx to notify the client of changes to the session or call.

 

### What is WebRTC?

[WebRTC](https://telnyx.com/products/webrtc) is a Real-Time Communications (RTC) protocol that enables web browsers to communicate with each other and with other devices. The technology allows users to embed communications directly into their websites and native applications, enabling unrivaled context for their end-users.

 

### What can I do with the WebRTC JavaScript SDK?

The [Telnyx WebRTC SDK](https://www.npmjs.com/package/@telnyx/webrtc) is a free, open-source JavaScript package that enables calls to be placed between browsers and the public switched telephony network (PSTN) via the Telnyx telephony engine.

We've used the SDK ourselves to build telephony into our own website. The __Call Us__ button in the header of this very website allows you to place a call directly from your browser to the Telnyx sales team using WebRTC. We've also built a web dialer tool into the __Debugging__ section of our [Mission Control Portal](https://portal.telnyx.com), allowing you to place a test call using your Telnyx account from your browser to any phone number or SIP URI via WebRTC.

 

### How can I get started with WebRTC?

Getting started with Telnyx WebRTC is quick and simple. You can follow our [quickstart](https://developers.telnyx.com/docs/voice/webrtc/fundamentals) guide to get up and running using the Telnyx Portal and a sample application we've built.

Adding the SDK to an existing app is as simple as installing the npm package:

 npm install @telnyx/webrtc --save

You can find more details on installation and usage alongside the [npm package](https://www.npmjs.com/package/@telnyx/webrtc), and explore the new [docs](https://developers.telnyx.com/docs/voice/webrtc/fundamentals) for an in-depth reference.

We've expanded our API reference documentation for our WebRTC Javascript Client to make it easier for you to access the information you need.

Expanded Docs for our WebRTC JavaScript Client

It's now easier than ever to embed the full power of the Telnyx Voice API into your web browser. We've updated and expanded our API reference documentation for the Telnyx WebRTC JavaScript Client.

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

Verify API for multichannel authentication

telnyx_verify_api.jpg

Telnyx Verify API allows you to send two factor authentication codes at ease

Telnyx Verify API for two factor authentication

Verify API has reduced all of the unnecessary steps for sending two factor authentication codes to devices. 

New Product: Verify API for Two Factor Authentication

![Webhook Logging](//images.ctfassets.net/taysl255dolk/3g7CV2xbj83AN699vWhYHy/ade681f7f8b239907cefea4ef42e2192/webhook-logger_release-notes.jpg)

If you're a Telnyx API user, you can now retrieve detailed information about webhooks for your account with our new Webhook Logging tools.

 

### What is a webhook?

A __webhook__ (also referred to as a web callback or a HTTP push API) is a way for an app to deliver data to other apps in real-time. Webhooks provide Telnyx API users with notification and context on communications events as they happen, enabling real-time communications applications.

For example, webhooks are sent by a Telnyx Call Control application when a call is initiated (<code>call.initiated</code>), answered (<code>call.answered</code>) or hung up (<code>call.hangup</code>). The Telnyx API sends webhooks to notify your application of a wide variety of events, including phone calls and numbers, text messages, SIP configuration settings, and many more as detailed in our <a href="https://developers.telnyx.com/api#webhooks">API Reference</a>.

 

### What can I do with Webhook Logging?

Webhook Logging allows you to retrieve webhooks that have already been delivered by Telnyx about events in your voice and messaging applications.

Granular filtering options allow you to refine your search with several webhook parameters, including status, time-frame, and text strings contained in the webhook. These filtering tools enable advanced debugging use-cases:

- Locate and analyze specific webhooks using their webhook ID.
- Verify the delivery of a webhook.
- Verify the contents of a webhook.
- Analyze all webhooks sent in a certain timeframe or containing a certain text string (e.g., <code>call.initiated</code>) to find anomalies.
- Analyze all webhooks with "failed" status.

Webhook Logging is the newest addition to our <a href="/release-notes/sip-trunking#nov-30-2020">growing suite</a> of advanced communications API debugging tools. With granular debugging and reporting, it's easier than ever to build next-generation communications apps on our voice and texting APIs.

 

### How can I get started with Webhook Logging?

Webhook Logging tools can be accessed via the Telnyx API's <code>/webhook_deliveries</code> endpoint.

The [Telnyx API Reference](https://developers.telnyx.com/api/webhooks/get-webhook-deliveries) contains documentation and usage examples for listing webhook deliveries and filtering results, and for finding webhook delivery details by webhook ID.

If you're a Telnyx API user, you can now retrieve detailed information about webhooks for your account with our new Webhook Logging tools.

Webhook Logging for in-depth API Debugging

Webhook Logging for Advanced API Debugging

![sip-refer release-notes](//images.ctfassets.net/taysl255dolk/50MHmJoO6HuJNBccyhESPn/bda5cb21218119b26847ff1249fc9dc8/sip-refer_release-notes.jpg)

We’re excited to announce that Telnyx Voice API users can now transfer calls using the SIP Refer method. SIP Refer enables greater control over your communications by providing a reliable means of transferring calls between parties within your organization, or to the PSTN.

<h3>Sending a REFER message via Call Control programmable voice API</h3>

Customers can request that a call be transferred by using Call Control, our programmable voice API. <a href="https://developers.telnyx.com/api/call-control/dial-call">Refer commands</a> can be sent from a Call Control application at any time during a call. This will initiate a transfer of one of the parties from the initial Telnyx call onto a new call to an external destination, without Telnyx in the call path.

This transfer method can also be used to establish a new call between the two parties from the initial Telnyx call, without Telnyx in the call path. This use-case is especially useful for calls on which sensitive information is disclosed - by removing itself from the call path, Telnyx adds an extra layer of protection to these calls.

Initiating a transfer on any Telnyx call using the Refer command adds a $0.10 surcharge to the cost of the call.

<h3>Include context with transferred calls via SIP UUI header</h3>

Context can be passed along with transferred calls in the form of SIP UUI headers. For example, a support agent who collects information from a customer can attach this information in SIP UUI headers when transferring the call to another support agent, ensuring the customer only needs to provide their information once.

For more information on transferring calls using SIP REFER, check out our <a href="https://developers.telnyx.com/api/call-control/dial-call">docs</a>. Note that this new functionality is not supported in V1 of our API. Learn more about <a href="https://developers.telnyx.com/docs/voice/programmable-voice/get-started">[migrating to the new Telnyx API V2](https://telnyx.com/resources/what-is-voice-api).</a>

Curious about using SIP REFER to build greater functionality into your comms? Talk to our [SIP experts](https://telnyx.com/contact-us) to learn more.

We’re excited to announce that Telnyx Voice API users can now transfer calls using the SIP Refer method.

Call Transfer with SIP REFER

We’re excited to announce that Telnyx Voice API users can now transfer calls using the SIP Refer method. SIP Refer enables greater control over your communications by providing a reliable means of transferring calls between parties within your organization, or to the PSTN.

SIP REFER for All Call Transfers | Telnyx Release Notes

# Messaging Release Notes & Updates

At Telnyx we’re always improving our messaging features so you can offer your customers a robust communication experience, we make changes regularly based on feedback we receive from users like you. 

Recent Updates to Messaging include:

<ul>
 <li>05/27/20201 - <a href="https://telnyx.com/release-notes/messaging#may-27-2021">Toll-Free MMS</a></li>
 <li>04/02/2020 - <a href="https://telnyx.com/release-notes/messaging#april-2-2020">Twexit API</a></li>
 <li>09/25/2019 - <a href="https://telnyx.com/release-notes/messaging#sept-25-2019">URL Shortener</a></li>
</ul>

<hr>

27, May 2021

<h2 id="may-27-2021">Toll-Free MMS</h2>

We’re excited to announce that we will now be offering MMS for [Toll Free Messaging](https://telnyx.com/products/toll-free-sms) in the US and Canada. Toll Free messaging allows for high throughputs similar to short code, but costs less and can be provisioned in minutes. With this feature, customers can: 

- Search and purchase MMS enabled Toll Free numbers in the[ Mission Control Portal](https://telnyx.com/sign-up "Mission Control Portal")
- Send and receive [MMS on your Telnyx number](https://developers.telnyx.com/docs/messaging/messages/send-receive-mms "MMS Tutorial Telnyx")

To get started, log into your Telnyx account, where you can search for and purchase an MMS enabled Toll Free number. 

02, April 2020

<h2 id="april-2-2020">Twexit API Released</h2>

![Twexit API](//images.ctfassets.net/taysl255dolk/2bVbjCzNxOAoulTjxjGnHM/1a90d6941c36b2c28ea1aaff8a5b6943/twexit-api.jpg)

Telnyx is pleased to announce our Twexit API. This will allow users to switch their messaging services from Twilio by making minimal changes to their existing Twilio messaging code.

Follow the steps to make the switch:

### 1: Telnyx Portal Setup
Start by creating a new messaging profile account on your Telnyx Portal, and set the API version to “Twexit API”. Then assign an SMS-capable number to that messaging profile.

### 2: Send A Message
To begin sending messages, simply change the following fields in your code:

1. Update the host and AccountSid in references to the Twilio messages endpoint.
2. Twilio: `POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json`
3. Telnyx: `POST https://api.telnyx.com/2010-04-01/Accounts/{organization_id}/Messages.json`
4. Update Authentication Header:
5. Twilio: `Authorization: Basic base64({AccountSid}:{AuthToken})`
6. Telnyx: `Authorization: Basic base64({organization_id}:{auth_v2_api_key})`
7. 
8. Update the From number in the request payload.

Telnyx Inbound Message notifications will be in the same format as those sent by Twilio and will be sent to the inbound webhook URL set on the messaging profile.

For a full list of parameters and more API features, go to the [Twexit API Developers Docs](https://developers.telnyx.com/docs/messaging/messages/twexit).

<hr>

25, September 2019

<h2 id="sept-25-2019">URL Shortener Released</h2>

### Custom Shortlinks With Telnyx
Today, many customers utilize public URLs in their SMS and MMS messages. And these Common URL shorteners are increasingly being blocked or flagged as SPAM. By using a Telnyx custom URL, you can more quickly update your public URL, helping ensure that your messages get through the first time, every time.

![shortened-url-options](//images.ctfassets.net/taysl255dolk/3aC6BODXtqL6hVWwAHsSsI/98cd9d49e87f41de1c7ac3758bff4b05/shortened-url-options.png)
You’ll be able to define custom URLs to communicate your use case and add your own brand name to the domain, making your links instantly recognizable to customers. And when a recipient trusts your link, they’re far more likely to click.

Custom URL Shortening is enabled per Messaging Profile. If you send SMS via phone numbers under this profile, and they contain any URLs that are part of the list of supported URLs, then they will be replaced with links that the URL Shortener service generates.

Please reach out to customer support so that they can work internally to create your customer URL shortener. Please provide the following information so customer support can process your request:
1. Your customer ID
2. Your custom domains (or let us know if you need us to provide the domains for you)
3. The profile IDs that you need the link shortner assigned to
Please note that any domains that you provide need to be set up with AAA records.

RN SMS.jpeg

Wondering what the latest messaging updates at Telnyx are? Here you will find all of our release notes for SMS and MMS.

What's new in Messaging at Telnyx?

If you're looking for all our SMS and MMS updates and release notes you can find them all contained here.

Messaging (SMS/MMS) [RELEASE NOTES]

# Number Availability Notes & Updates

At Telnyx we own our number inventory (unlike the competition), we make changes regularly based on feedback we receive from users like you. 

Recent Updates to Numbers include:

<ul>
 <li>06/08/2020 - <a href="https://telnyx.com/release-notes/numbers#june-8-2020">Tier-1 Numbering in Europe</a></li>
 <li> Check back regularly for our next update
</ul>

---

8, June 2020

<h2 id="#june-8-2020">New Tier-1 Numbering In Europe</h2>

![european-numbers](//images.ctfassets.net/taysl255dolk/1PMYwiq9e55Kj4vzOLxIEE/9270a63a45b497304e0dc145779a191f/european-numbers.jpg)

We’re proud to launch new Tier-1 numbering availability in __Austria, Slovenia, and Croatia__. Telnyx customers can now search, purchase and activate national numbers in these countries through the Mission Control Portal and the Telnyx API.

Tier-1 numbering allows for more direct control of number provisioning, more direct troubleshooting, and a wider range of number capabilities, so you can find the numbers you need, when you need them.

### Searching For And Purchasing Tier-1 Numbers
To search for Tier-1 national numbers, users can search by region, or by searching the following prefixes:

- __+43-72__ in Austria
- __+386-818__ in Slovenia
- __+385-72__ in Croatia

These new Tier-1 national numbers complement our toll-free numbers already available in these countries. Local Tier-1 numbers are also available in Slovenia and Croatia - simply search by city to find your perfect number.

Check out our developer center for more details on how to search for numbers via the [Mission Control Portal](https://developers.telnyx.com/docs/development/get-started) or the [Telnyx API](https://developers.telnyx.com/docs/numbers/phone-numbers/number-search).

Check out our [Resource Center](https://telnyx.com/resources/europe-tier-1-numbering) to learn more about how Tier-1 numbering can bolster your global voice connectivity.

If you'd like to know more about our international number offering, [contact our experts](https://telnyx.com/contact-us).

RN_Numbers.jpeg

Here you will find all of our latest updates and release notes for SIP and VoIP number inventory at Telnyx.

What's New in Numbers at Telnyx?

You can find all the latest updates and release notes together here.

Release notes