# Billing & Billing Group Release Notes
At Telnyx we’re always flexible when it comes to billing, we make changes regularly based on feedback we receive from users like you. 

Recent Updates to how Telnyx bills users include:

<ul>
  <li>03/17/2021 - <a href="https://telnyx.com/release-notes/new-feature-release-billing-groups#mar-17-2021">Telnyx adds GBP billing to Mission Control</a></li>
  <li>06/06/2020 - <a href="https://telnyx.com/release-notes/new-feature-release-billing-groups#june-6-2020">Multi-Currency Billing in AU Dollars</a></li>
  <li>11/11/2019 - <a href="https://telnyx.com/release-notes/new-feature-release-billing-groups#nov-11-2019">Billing Groups Released</a></li>
  <li>01/30/2017 - <a href="https://telnyx.com/release-notes/new-feature-release-billing-groups#jan-30-2017">Rate Center Search</a></li>
</ul>

<hr>

17, March 2021

<h2 id="mar-17-2021">Telnyx adds GBP billing to Mission Control</h2>

![Telnyx UK - Release Notes](//images.ctfassets.net/taysl255dolk/6O5tQIiEhppKwOXPaDvANx/96fe005e8e0be96f5ec3f56f92f39374/GBP_Multi-Currency_Billing__1_.jpg)

Today, Telnyx is delighted to announce that our customers can now choose to pay and see pricing in pounds Sterling (GBP). This new functionality is part of a wider multi-currency initiative, which aims to make the Telnyx platform easier to use, for both new and existing customers.

For a UK-based business, working in GBP will allow you to better understand your pricing as it appears on our website and in the Mission Control Portal, making your invoices more clear and predictable. More importantly, it makes life easier for Telnyx users who bill their customers in GBP. Telnyx users will now be able to streamline their finance operations by attributing the Telnyx cost to the spending of their customers directly. 

This billing feature release comes after the announcement that we have achieved [full PSTN replacement](https://telnyx.com/resources/uk-pstn-replacement "UK PSTN Replacement") in the UK. Our dedicated network [point of presence in London](https://telnyx.com/resources/telnyx-anchorsite-low-latency "London PoP"), [international call routing](https://telnyx.com/release-notes/sip-trunking "Telnyx International Call Routing"), and a more reliable UK +44 number search and ordering experience, means that our UK customers can now avail of a fully-featured telephony solution in England, Wales, Scotland and Northern Ireland.

### How to activate GBP billing on your Telnyx account

To get started, you’ll need to [sign up](https://telnyx.com/sign-up "Sign Up") for a Telnyx account. Once you’ve verified your email address and logged into your Mission Control Portal, we’ll ask you a few questions about how you’ll be using Telnyx. Simply select GBP from the drop-down menu in this box, and that’s it! Your pricing and invoicing will appear in GBP for all usage associated with that specific account.

<hr>

6, June 2020
<h2 id="june-6-2020">Multi-Currency Billing in Australian Dollars</h2>

![Multi-Currency Billing in Australian Dollars](//images.ctfassets.net/taysl255dolk/4vlkQy6C2YOpuRu0dRCy2/5e69f246efaa3a1426c4da6e1c769dfd/AU_Launch_ReleaseNotes_1200x450_2x.png)

We’re excited to announce that Telnyx customers can now choose to pay and see pricing in Australian Dollars (AUD). This new functionality marks the beginning of a wider multi-currency initiative aimed at making our platform easier to use for everyone.

If you’re an Australian business, working in AUD will allow you to better understand your pricing as it appears on our website and in the Mission Control Portal, making your invoices more clear and predictable.

This billing feature comes as part of wider improvements to our services Down Under, including our [dedicated network point of presence in Sydney](https://telnyx.com/release-notes/call-control), [better international call routing](https://telnyx.com/release-notes/sip-trunking), [SIP registration on sip.telnyx.com.au](https://telnyx.com/release-notes/sip-trunking), a more reliable Australian +61 number search and ordering experience, and our ability to serve as an ISDN replacement in Australia, through our [Elastic SIP Trunking](https://telnyx.com/products/sip-trunks) and [Programmable SMS](https://telnyx.com/products/sms-api) offerings.

### How to activate AUD billing on your Telnyx account

To get started, you’ll need to [sign up for a Telnyx account](https://telnyx.com/sign-up). Once you’ve verified your email address and logged into your Mission Control Portal, we’ll ask you a few questions about how you’ll be using Telnyx. Simply select AUD from the drop-down menu in this box, and that’s it! Your pricing and invoicing will appear in AUD for all usage associated with this account.

<hr>

11, November 2019
<h2 id="nov-11-2019">Billing Groups Released</h2>

![Billing Group Feature Image](//images.ctfassets.net/taysl255dolk/44IsCthfrmmiEqXXBwuaLK/8ce3079abd9efe5635b8442bb138f793/Resource-BillingGroups-1200x450_2x.png)

We’re happy to announce a new feature for managing your usage and billing information — __Billing Groups__, now available in the <a href="https://portal.telnyx.com/#/app/account/billing-groups">Mission Control Portal</a> and Telnyx API.

This new feature offers a better way to manage your customer sub-accounts, making it easy to add and manage billing groups to categorize usage reports and end-of-month invoice records.

Billing Groups allow you to separate your phone numbers and usage for a specific end customer, this will be particularly useful for resellers of our services with customers of their own. Sub-accounts can now be billed the exact inbound and outbound usage for the month, depending on when numbers and profiles were assigned to the Billing Group.

### Benefits of Billing Groups

- __Billing of Sub-Accounts__: Resellers of our services who have customers of their own will find this feature particularly useful for billing the exact usage, partial and recurring charges for the month.
- __Reporting & Metadata__: Billing Group information is stored within the metadata of the corresponding CDR. This provides for easier filtering of records by customer.

### Setting Up Billing Groups

Set up Billing Groups in minutes with the Mission Control Portal. You can start creating Billing Groups in four simple steps:

1. Navigate to the __My Account__ section, located within the dropdown in the top right of the Mission Control Portal.
2. Select __Billing Groups__ from the top navigation bar.
3. Enter the __name__ of the Billing Group.
4. Click __Create__.

Once you’ve created your Billing Groups, you can start assigning them to numbers and outbound profiles within their corresponding sections. You may also label outbound calls dynamically through a custom SIP header.

To find out more about creating your Billing Groups via the Telnyx API, head over to our [Developer Center](https://developers.telnyx.com/api/billing-groups/billing-group/list-billing-groups).

<hr>

30, January 2017
<h2 id="jan-30-2017">Rate Center Search Released</h2>

Our [Rate Center Lookup](https://telnyx.com/products/phone-numbers) is here, and we’re delighted to share it with everyone! We’ve got a lot of exciting things in store for you, and this rate center search is just one of many tools and updates that we’ll be releasing in 2017.

### Using the Rate Center Search Feature

Using the search feature of our Rate Center Lookup tool is quick and easy:

1. Choose a country from the dropdown
2. Choose a state or province from the dropdown

You can include a specific city or rate center in the third field to narrow down your results, which will be listed next to the map in the following format:

- Rate Center
- Location
- LATA
- LATA Name


Billing Group Feature Image

Need information on the latest billing releases at Telnyx? Here you will find all our billing & billing group updates all in one place.

Whats the Latest in Billing at Telnyx?

We’re happy to announce a new feature — Billing Groups — which makes it easy for you to categorize usage reports and end-of-month invoice records. 

Telnyx Billing [RELEASE NOTES & Updates]

## Instituting Billing and Reporting for WebRTC

Starting __Monday, March 29, 2021__, Telnyx is instituting billing and reporting for WebRTC usage. This release note outlines what this change means for customers, and how WebRTC calls are billed, reported, and invoiced.

<br>

## Pricing Details for WebRTC Calls

The total cost for inbound and outbound calls initiated and answered on a Telnyx WebRTC browser client consists of two components: 

1. The per-minute usage cost of the WebRTC interface.
2. The per-minute usage cost of any underlying SIP infrastructure used as part of the call.

WebRTC calls are priced at __$0.002/minute__, in addition to any cost associated with PSTN call legs. 

<br>

### Cost Computation for WebRTC Calls

__Inbound Call to a Telnyx Phone Number connected to a WebRTC client:__

Calls placed to a Telnyx phone number can be answered using a WebRTC client. The cost for such calls is as follows:

- [__$0.0035 / min__ to receive calls to a local Telnyx phone number in the US.](/pricing/elastic-sip)
- [__$0.002 / min__ to receive inbound calls to a browser or app](/pricing/call-control) (in this case, the WebRTC client).

Thus the total cost of the call is $0.0035 + $0.002 = $0.0055 / min. 

For example, on a 120-second call, the total charge is $0.0055 / min × 2 min = $0.011.

<br>

__Outbound Call from a WebRTC client to a PSTN number:__

A WebRTC client can be used to place calls to any phone number on the PSTN via Telnyx. The cost for such calls is as follows:

- [__$0.005 / min__ to place calls to a local phone number in the US](/pricing/elastic-sip). (Assuming the number is in Zone 1 of our [destination-based pricing](/pricing/elastic-sip). This applies to most phone numbers in the lower 48 states.)
- [__$0.002 / min__ to place outbound calls from a browser or app](/pricing/call-control) (in this case, the WebRTC client).

Thus the total cost of the call is $0.005 + $0.002 = $0.007 / min.

For example, on a 120-second call, the total charge is $0.007 / min × 2 min = $0.014.

<br>

## Call Detail Records (CDRs) for WebRTC Calls

Call Detail Records (CDRs) are available for WebRTC calls, just like regular Elastic SIP Trunking or Voice API calls.

An example CDR from a WebRTC call is shown below. 

<br>

| Field     | Value     |
| ---------- | ---------- |
| cld       | +1224xxxxxxx       |
| cli       | +1312xxxxxxx       |
| start_timestamp       | 2021-03-04 21:13:07       |
| end_timestamp       | 2021-03-04 21:15:03       |
| billed_sec       | 120       |
| cost       | 0.004       |
| rate       | 0.002       |
| direction       | outbound       |
| uuid       | 6ae3XXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX       |
| user_id       | 246bXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX       |
| call_sec       | 102       |
| session_uuid       | 6ae3XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX       |
| connection_id       | 1583XXXXXXXXXXXXXXX       |
| billing_group       | ABC Calling Services       |
| tags       |        |

<br>

Users may view CDRs associated with WebRTC usage in the [Detail Requests](https://portal.telnyx.com/#/app/reporting/detail-requests) tab of the Reporting section in the Portal, by selecting __WebRTC__ as the Report Type.

<br>

![Requesting WebRTC Call Detail Records in the Mission Control Portal](//images.ctfassets.net/taysl255dolk/1DmfBTnUVVYuED0vhMGK1h/b0193f415b826106dbc17b53aea725c3/portal_webrtc_billing.png)

<br>

Similarly, CDRs associated with SIP usage are available by selecting __Calls__ as the Report Type.

<br>

__Matching SIP CDRs and WebRTC CDRs__

In the CDR example illustrated above, only the WebRTC component of the total cost of the call is shown. A separate CDR is created for the SIP Trunking usage component, showing the relevant rate for its usage.

<p>Calls which contain a WebRTC component and a SIP Trunking component will thus have two separate CDRs describing the call and its costs. These CDRs will have an identical value in their <code>uuid</code> field, so that they can be easily matched. In future iterations of WebRTC billing and reporting, we plan to provide a unified reporting system which contains complete call information, inclusive of all billable components.</p>

<br>

### Invoicing for WebRTC Calls

Invoices will present information on SIP Trunking usage and WebRTC usage separately, even if calls are made that use both WebRTC and SIP Trunking.

<p><a href="//assets.ctfassets.net/taysl255dolk/7kxBmBtHF5IvBTyrFcJ0US/52a10bddec1085d872566ed2fe41dfb6/Sample_Invoice_-_WebRTC.pdf" title="Sample Invoice - Telnyx WebRTC">Download a sample invoice illustrating WebRTC usage.</a></p>

SIP Trunking usage is presented in the invoice in the *Usage Charges - Voice and Data* section under "Termination" and "Origination".

WebRTC usage is presented in the invoice in the *Usage Charges - Voice and Data* section under "WebRTC Termination" and "WebRTC Origination".

<br>

### Coming Soon to Telnyx WebRTC

In the future, we will be adding even more functionality to WebRTC billing and reporting, including:

- Filtering by call source type in reports, so you can tell if calls came from a phone number or WebRTC client.
- Aggregated reporting for WebRTC calls.
- The ability to see unified call costs via our Portal or API, containing all of the cost components for any given call.

If you'd like to be the first to know about these new features, [talk to our sales team](/contact-us) about WebRTC.


We are instituting billing and reporting for WebRTC. Learn all the details in the release notes here.

Instituting Billing and Reporting for WebRTC

Starting Monday, March 29, 2021, Telnyx is instituting billing and reporting for WebRTC usage. This release note outlines what this change means for customers, and how WebRTC calls are billed, reported, and invoiced.

We’re excited to announce that our portal functionality is ready for registering 10DLC brands and campaigns. 10-digit long code, or 10DLC, is a carrier led initiative aimed to increase transparency in the messaging ecosystem and allow businesses to send high throughput A2P messages at low costs. 10DLC only applies to message traffic terminating within the US, and does not affect senders currently using toll free numbers. Here is an overview of what customers will be able to do with this new feature: 

- Create a brand 
- Create a campaign to attach to a brand
- Assign numbers to your 10DLC campaign

## Who needs to register for 10DLC

If your business falls into either of the categories below, we highly recommend that you register your A2P traffic for 10DLC to avoid message filtering and throughput limitations. While there are currently no consequences for non-registered traffic, AT&T has announced that they will be charging higher message rates starting May 1, and other carriers are likely to follow. 

Sending A2P + P2P on local long codes - You should register your A2P traffic with 10DLC, but your P2P traffic can remain as is. 
Sending purely A2P traffic on local long codes - All of your traffic should be registered with 10DLC. 

## Registering a 10DLC Brand and Campaign

Telnyx customers will be able to see an option called “Campaigns” in the Messaging section of the Mission Control Portal. 
![10DLC Registration via Mission Control Portal ](//images.ctfassets.net/taysl255dolk/6msrKx6AaUKJS617SB2Kx4/8446297159e5c9ab27b661d97234d530/10DLC_Portal_.png)

Here, you can enter information to register their brand (business), and create a campaign (use case) to attach to your brand, to start sending their A2P messages via 10DLC. 

## Assigning Numbers to Your 10DLC Campaign

Any specific phone number can only be assigned to one campaign. Campaigns can have many assigned phone numbers. For example, if there are two campaigns: one for appointment reminders and another for marketing, the same phone number cannot be used in both campaigns. In order to use the same phone number, a "Mixed" campaign is recommended which allows for up to 5 sub use cases. AT&T message fees may be higher for mixed campaigns.

If you have already purchased numbers with Telnyx, you can assign those to your 10DLC campaigns individually or by selecting a messaging profile. If you don’t currently have any numbers with Telnyx, you can buy them directly from our portal in the “Numbers” section. Once you submit your brand and campaign for registration, there may be a delay before your messages are routed with 10DLC. 

## 10DLC for ISVs and Resellers 

We will be adding additional documentation for best practices when creating brands & campaigns. Our initial release for our 10DLC feature does not yet support higher throughput, (~200,000 messages per brand per day across all campaigns) and we are recommending that ISVs and resellers hold off on submitting their campaigns until further notice. We are still working with vendors/carriers before recommending specific brand & campaign set up for this type of use case.  

Furthermore, increased throughput for 10DLC (beyond what local long code currently offers) will not be immediately available. We will announce when higher throughputs (up to 30MPS) are available with 10DLC. The API functionality for brand and campaign registration will be available soon. 


10dlc mission control portal 

Our newest portal feature allows customers to register 10DLC brands and campaigns with ease

10DLC Registration via Mission Control Portal 

Our newest portal feature allows customers to register 10DLC brands and campaigns with ease.

Register for 10DLC via Mission Control Portal 

# SIP Product Release Notes & Updates
At Telnyx we’re always improving and expanding our network to deliver the highest quality SIP experience for your customers, we make changes regularly based on feedback we receive from users like you. 

Recent Updates to SIP include:

<ul>
  <li>02/25/2021 - <a href="https://telnyx.com/release-notes/sip-trunking#feb-02-2021">New Quality of Service (QoS) Reports for Voice Calls Now Available in Mission Control</a></li>
   <li>11/30/2020 - <a href="https://telnyx.com/release-notes/sip-trunking#nov-30-2020">New Advanced SIP Debugging Feature Now Available in Mission Control 
</a></li>
   <li>08/05/2020 - <a href="https://telnyx.com/release-notes/sip-trunking#aug-5-2020">Outbound Voice Profiles Simplified</a></li>
  <li>04/15/2020 - <a href="https://telnyx.com/release-notes/sip-trunking#april-15-2020">International Conversational Direct</a></li>
  <li>04/15/2020 - <a href="https://telnyx.com/release-notes/sip-trunking#april-15-2020-e911">Emergency Services in Ireland</a></li>
  <li>10/31/2019 - <a href="https://telnyx.com/release-notes/sip-trunking#oct-31-2019">Global Expansion for SIP Registration</a></li>
  <li>10/08/2019 - <a href="https://telnyx.com/release-notes/sip-trunking#oct-8-2019">New PoP in Sydney, Australia</a></li> 
</ul>

25, February 2021
<h2 id="feb-25-2021">New Quality of Service (QoS) Reports for Voice Calls Now Available in Mission Control</h2>

![QoS Reports now available in the Portal](//images.ctfassets.net/taysl255dolk/4zWz7Gsh7qq45yyQHpw5Ht/1830f265dc5a73258af10cfb9553dbc8/QoS_Reports_for_Voice_Calls_are_now_available_in_the_Portal..png)

At Telnyx, we know that it’s important for our customers to be able to track all aspects of their calls. Today, we’re excited to release Quality of Service (QoS) reports for voice calls to help users troubleshoot call quality issues that may arise. 

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.

On these graphics customers will be able to see 4 different metrics:

1. __Packets__
“Packets” represents the incremental number of RTP (real-time transport protocol) packets that were sent in this direction.
2. __Packets lost__
“Packets_lost” represents the incremental (accumulated) number of RTP packets perceived as lost by the RTCP (real-time transport control protocol) information, as measured by the receiving party.
3. __MOS__
“MOS” (Mean Opinion Score) represents the value as a function of Jitter, the number of lost packets, and the round trip time (RTT)- when available- as measured by the receiving party.
4. __IA Jitter__
“Ia_jitter” represents the value of Interarrival Jitter, as measured by the receiving party.

The QoS report will enable users to quickly identify any issues that might have affected the quality of the call, which will speed up the troubleshooting process. Take a look at the sample report below:

![QoS Report Screenshot](//images.ctfassets.net/taysl255dolk/1A26MoHZFFOmQovS4zmyw5/f1df7c3390eed50f85c03c4f8beca86a/QoS_Screenshots.png)

*Sample QoS report now available in Mission Control*

The new report feature is available in the Mission Control Portal through the Advanced View of our SIP Debugging tool.

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

30, November 2020
<h2 id="nov-30-2020">New Advanced SIP Debugging Feature Now Available in Mission Control</h2>

![995 x 374 Advanced SIP Debugging is now live in Mission Control](//images.ctfassets.net/taysl255dolk/69g6JHqNgKqGZ88yAVEERK/8a16192ac6d2a7276cca4ff3c59f2d92/995_x_374_Advanced_SIP_Debugging_is_now_live_in_Mission_Control.jpg)

Telnyx are delighted to announce the launch of an advanced SIP debugging feature in the Mission Control Portal. 

Behind the scenes, Telnyx engineers have been using the Homer tool to troubleshoot issues with SIP calls. We have integrated the __Homer__ tool to extend it’s use to Telnyx customers for easy troubleshooting through an improved UI and a host of new features. Telnyx portal users now have the ability to:

- export the callflows in PCAP format for advanced packet inspection
- export the callflows in text format for sharing. 

The Advanced SIP debugging tool will allow Telnyx customers to perform an in-depth inspection of their SIP calls. 

Telnyx plans on adding QoS metrics to the advanced SIP debugging tool to enable our customers to measure audio quality of calls on a timeline report. 

Telnyx users can access this new feature by navigating to the ‘__Debugging__’ tab on the menu on the left hand side of your Mission Control Portal and clicking ‘__Advanced View__’. Why not [check it out](https://portal.telnyx.com/)?

<hr>

05, August 2020
<h2 id="aug-5-2020">Changes to Outbound Voice Profiles</h2>

![high-volume-short-duration](//images.ctfassets.net/taysl255dolk/52QbdWedGZtTqimDHcY8RF/dedb59c3892162e8b65d77f41d68849c/high-volume-short-duration.jpg)

We’re launching a new Outbound Voice Profile creation experience in the Mission Control Portal to simplify the process of getting up and running with your Telnyx account.

### Why We Changed Outbound Voice Profiles

As we continue to expand our international SIP trunking services across the globe, we’ve heard a lot more feedback from users who want a simple process for seeing international outbound call pricing and making international outbound calls with Telnyx. With that feedback in mind, we’re confident that this new experience will make it easier than ever for customers to start making outbound calls on our global, purpose-built communications network, and see exactly how much those calls will cost.

#### Simplified Traffic Types
Users now only need to specify whether their voice traffic type is __Conversational__ or __High Volume/Short Duration__.

Our telephony engine now handles fax traffic and direct routing as standard, so there’s no longer any need to select the Fax or Conversational Direct traffic types to enjoy these benefits.

#### US and International Calling, all in one Conversational Outbound Voice Profile
Users who create a new Outbound Voice Profile and select the __Conversational__ Traffic Type for regular calls can use this profile to make calls internationally.

There is no longer any need to specify a Service Plan on Outbound Voice Profiles, or to create separate profiles for USA-48/CAN and International Service Plans. You can still choose to allow or disallow calls by international destination, set maximum allowable destination rates, and set daily spend limits on connections to protect your account from fraud.

Pricing for US and international outbound calling is now available in one Global Conversational rate deck. Users can find this deck under “Outbound (Termination) Voice/Fax Usage” in the Voice Pricing section of the Mission Control Portal.

### Legacy Outbound Voice Profiles
If you created an Outbound Voice Profile before today, you’ll still be able to edit its settings with the Legacy Outbound Voice Profile experience. For any profiles created after today, you’ll see the new experience as described in these release notes.

For a limited time, creating, updating, and adding connections to Legacy Outbound Voice profiles will still be supported.

The following functionality of Legacy Outbound Voice profiles will be removed when support for legacy profiles ends:

- Switching back to the legacy experience when creating new Outbound Voice Profiles in the Mission Control Portal, to specify legacy traffic types (like Fax and Conversational Direct) and service plans.
- Creating Legacy Outbound Voice Profiles via the Telnyx API.
- Adding connections and apps to a Legacy Outbound Voice Profile.

For more information on Outbound Voice Profiles, talk to our [experts](https://telnyx.com/contact-us).

<hr>

15, April 2020
  <h2 id="april-15-2020">International Conversational Direct</h2>

![high-volume-short-duration](//images.ctfassets.net/taysl255dolk/52QbdWedGZtTqimDHcY8RF/dedb59c3892162e8b65d77f41d68849c/high-volume-short-duration.jpg)

We’re excited to announce a new product for international outbound voice — International Conversational Direct, which is now available in the Mission Control Portal and the Telnyx API.

International Conversational Direct offers improved quality and higher connection rates on your outbound calls. Call quality is enhanced by optimizing the route preferences and leveraging our direct partnerships with local Tier-1 carriers across the globe to choose a high-quality route every time.

Set up high-quality global outbound calling in minutes with the Mission Control Portal for more direct call connections and better quality. You can enable International Conversational Direct in two simple steps:

1. Create a new Outbound Profile with Traffic Type: __Conversational Direct__ and Service Plan: __International + US-48/CAN__
2. Assign a connection to your new Outbound Profile.

![direct-outbound-profile](//images.ctfassets.net/taysl255dolk/1iXFLkGImwU3MizDWoJLZc/5c34fe40f542e1fe3a088599590ad081/direct-outbound-profile.jpg)

Usage-based pricing for International Conversational Direct termination can be found by logging into your Mission Control Portal and heading to the Pricing page.

This launch builds on our existing high-quality termination offering, including our [domestic Conversational Direct](https://telnyx.com/release-notes) product launched late last year.

Want to configure your Outbound Profiles to enable International Conversational Direct via API instead? Head on over to our [Developer Center](https://developers.telnyx.com) to learn how.

Learn more about the benefits of International Conversational Direct on our [Resource Center](https://telnyx.com/resources/outbound-quality-international-conversational-direct).

<hr>

15, April 2020
<h2 id="april-15-2020-e911">Emergency Services In Ireland</h2>

![ireland-emergency-numbers](//images.ctfassets.net/taysl255dolk/1y0U2knJc4isuxpr7GL8Zs/f188c8bd30665b0feebf10cc5f50a5b0/ireland-emergency-numbers.jpg)  

We’re excited to announce the addition of emergency services to our numbers in Ireland. Emergency services can be enabled on some local Irish numbers for an additional monthly recurring cost.

### How do I enable emergency services on my Irish numbers?
Emergency services can be enabled on your local numbers in just a few steps via the Mission Control Portal:

1. Purchase an Irish number
2. Select the ambulance icon 🚑 next to your number in the __My Numbers__ section of the Mission Control Portal.
3. Enter or select an address in the dialog box. This address is provided to the emergency services when an emergency call is made from your number.

Please note that addresses must be entered in the correct format, including the __Business Name__, __Street Address__, __Extended Address__, __City/Locality__ and __Postcode__ fields populated, and with the State field containing the name of a county in the Republic of Ireland:

Carlow, Cavan, Clare, Cork, Donegal, Dublin, Galway, Kerry, Kildare, Kilkenny, Laois, Leitrim, Limerick, Longford, Louth, Mayo, Meath, Monaghan, Offaly, Roscommon, Sligo, Tipperary, Waterford, Westmeath, Wexford, and Wicklow

Once you have submitted your details, it will take local regulators approximately 48 hours to enable emergency calling on the number.

For more information on enabling emergency services on your numbers, our dedicated support team is on hand to help via chat, 24/7.

You can learn more about our emergency services offering in other countries at our [Resource Center](https://telnyx.com/resources/emergency-services-ireland-numbers).

<hr>

31, October 2019
<h2 id="oct-31-2019">Global Expansion for SIP Registration</h2>

![global-sip-expansion](//images.ctfassets.net/taysl255dolk/2MHlMZfrqQZaaWO2bQtRst/6930fab9a8a5cbc0328a3e0d71449fd4/global-sip-expansion.png)  

We’re excited to announce that we’ve expanded support for SIP registrations to even more global destinations. With this release, we now support registrations locally within Europe and Australia, with Canada coming soon.

This global expansion enables registrations beyond our US sites located at sip.telnyx.com. SIP registrations are now possible on the following domains:

- sip.telnyx.eu
- sip.telnyx.com.au
- sip.telnyx.ca (coming soon)

This means that customers using devices which depend on SIP registrations can now register with any of the regions listed above and be able to receive inbound calls from the regional SIP proxy.

We’ve also extended our full support for UDP, TCP and TLS to each of these new locations, so you can keep using your existing signaling protocol. With regional routing of your SIP signaling traffic, you’ll experience reduced latency and improved deliverability.

Configuring your SIP Region is easy and can be tested with the following steps:

1. Register your SIP device against sip.telnyx.XXXX
2. Make a phone call to the number or SIP URI assigned to the Connection.
3. Your SIP device will receive the inbound call from the SIP regional proxy that you registered against.

That’s it — you’ve now updated your SIP Registration region. To find out how you can complete these same steps via API, check out our [Developer Center](https://developers.telnyx.com/api/v1/mission-control/find-connections).

For more information on SIP Registration, head over to sip.telnyx.com.

<hr>

08, October 2019
  <h2 id="oct-8-2019">New Telnyx PoP in Sydney, Australia</h2>

![sydney-au-pop](//images.ctfassets.net/taysl255dolk/4SHrI6SQnzO3hSvO3LBvCl/bdba938561fb26d57d529a8410f92441/sydney-au-pop.png)

The release of a new Telnyx point-of-presence (PoP) in Sydney, Australia brings about three big changes to the Telnyx network.  

The first is our continued global network expansion. The rollout of our first point-of-presence in Australia — with more to come in the near future — expands our connection points to the Telnyx network, to benefit customers in Australia and Asia.

Secondly, we built Anchorsite® to improve call quality and reduce packet loss, with traffic routed through the PoP with the lowest latency. You can now choose to anchor your call media at this new Sydney PoP for even better call quality.

And finally, SIP signaling is now possible through this new region. You can test this out by pointing your SIP devices to sip.telnyx.com.au for outbound calls, or by selecting Australia as your SIP region under Connections Inbound settings for inbound calls.

It’s now possible to keep both your call media and signaling all within Australia, reducing latency and directing all media and traffic over our private IP-network.

If you’re interested in anchoring call media and SIP signaling at this new location, you can configure your connection in the [Mission Control Portal](https://portal.telnyx.com/). Check out our [Developer Center](https://developers.telnyx.com) to see how you can make the same updates via the Telnyx API.

SIP Trunking Release Notes 

Wondering what the latest updates for SIP Trunking at Telnyx are? Here you will find all the feature releases, all in on place.

What's New in Telnyx's SIP Trunking Product?

If you're looking for our SIP Trunking release notes and updates you can find them all together here.

SIP (Session Initiation Protocol) [RELEASE NOTES]

Call Control Release Notes Image

Looking for the latest updates in Call Control at Telnyx? Here you will find our release notes and updates, all in one place.

What's New With Call Control at Telnyx?

You can find all our Call Control release notes and updates here.

Call Control [RELEASE NOTES & UPDATES]

We're adding more flexibility when recording calls using TeXML, allowing you to choose between single- or dual-channel call recording more easily.

<br>

<h3>How to specify Single-Channel Recording via TeXML</h3>

<p>Recording calls using the TeXML <span class="code"><a href="https://developers.telnyx.com/docs/voice/programmable-voice/texml-translator#record" title="Call Control API Reference | Telnyx Developer Center">&lt;Record&gt;</a></span> verb produces a dual-channel recording by default.</p>

<p>Now, users can specify an additional <span class="code">channels</span> attribute with the <span class="code">&lt;Record&gt;</span> verb to produce a single-channel recording:</p>

<p class="code">
&lt;Response&gt;<br>
&nbsp;&nbsp;&lt;Record <strong>channels="single"</strong> action="/test/callback/on-record" method="POST" recordingStatusCallback="/test/callback/recording" /&gt;<br>
&lt;/Response&gt;<br>
</p>

<p>The channels attribute can have a value of <span class="code">"single"</span> or <span class="code">"dual"</span>. The default value is <span class="code">"dual"</span>, so if you're already using TeXML to record dual-channel calls, your integration won't be affected.</p>

<br>

<h3>How this change affects webhook information passed by Telnyx</h3>

<p>Telnyx passes information about recordings in the form of a webhook sent to the <span class="code">recordingStatusCallback</span> and <span class="code">action</span> URLs specified in the <span class="code">&lt;Record&gt;</span> verb. With this change, the information in the webhooks will include a new <span class="code">"RecordingChannels"</span> field. The <span class="code">"RecordingChannels"</span> field can have a value of <span class="code">"1"</span> for single-channel recordings or <span class="code">"2"</span> for dual-channel recordings.</p>

The webhook example shown below describes a single-channel call recording: 

<p class="code">
{<br>
&nbsp;&nbsp;"AccountSid": "9fd26e62-XXXX-XXXX-XXXX-XXXXXXXXXXXX",<br>
&nbsp;&nbsp;"CallSid": "v2:Yl-sKJ4znm3N7v9-nstE9oJNH48s4PfWVJ1UB5nsJMKHS9RqQ6gNdg",<br>
&nbsp;&nbsp;"CallSidLegacy": "v2:Yl-sKJ4znm3N7v9-nstE9oJNH48s4PfWVJ1UB5nsJMKHS9RqQ6gNdg",<br>
&nbsp;&nbsp;"From": "+1555XXXXXXX",<br>
  &nbsp;&nbsp;<strong>"RecordingChannels": "1",</strong><br>
&nbsp;&nbsp;"RecordingDuration": "4",<br>
&nbsp;&nbsp;"RecordingSid": "f1099038-XXXX-XXXX-XXXX-XXXXXXXXXXXX",<br>
&nbsp;&nbsp;"RecordingStatus": "completed",<br>
&nbsp;&nbsp;"RecordingUrl": "S3 URL",<br>
&nbsp;&nbsp;"To": "+1555XXXXXXX"<br>
}
</p>

<p>This change will be in effect from <strong>Monday, March 1, 2021</strong>. Want to learn more about recording calls with TeXML? Visit our <a href="https://developers.telnyx.com/docs/voice/programmable-voice/texml-translator#record" title="Call Control API Reference | Telnyx Developers">API reference</a> to explore the docs!</p>

We're adding more flexibility when recording calls using TeXML, allowing you to choose between single- or dual-channel call recording more easily.

TeXML Options for Recording is LIVE

We're adding more flexibility when recording calls using TeXML, allowing you to choose between single- or dual-channel call recording more easily. Recording calls using the TeXML <Record> verb produces a dual-channel recording by default.



More Recording Options for TeXML

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

## Outbound Webhook Example

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

<p>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 <strong>without specifying any input gathering</strong>, audio could unintentionally be interrupted by a user pressing the <code>*</code> key on their phone keypad.</p>

<p>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.</p>

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

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.

<br>

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

<br>

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

<br>

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

<br>

### Billing:

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

<br>

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

<br>

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

Managed Accounts in the Telnyx Mission Control Portal

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.

Release notes