Hello. How can we help you?
< All Topics
Print

Release Notes: December 2022

Callroute has now moved to a continuous feature delivery model where new features and bug fixes are released as soon as they have passed our quality assurance tests. This allows customers to benefit from new features as quickly as possible without waiting for a specific release date.

In line with this new release cycle, the way we write our release notes has also changed. Instead of release notes being created in line with a specific rollout package, we are now going to summarise all features released each month. These notes will be released on the last day of the month.

Changes

The following features have been released this month

Microsoft Teams Service Username in Portal

It is now possible to see the User Principal Name of the connected account on the Microsoft Teams service integration. Previously, customers needed to remember what account was being used to synchronise and assign number to their Teams users.

The username is visible under the Microsoft Teams Service Health Checker

Filter Call Detail Reports by Custom Date Range and Time

Now customers can drill down their call detail records to a specific time frame within a date range bringing more granularity to our reporting solution.

Improved Teams Direct Routing Integration

Previously, customers would see their Callroute SBC name in the SBC page of the Microsoft Teams Admin Center. Due to the way we connect to Teams, the view would always show warnings on connection status within the Admin Center. These were always false warnings.

We have improved integration now so that the Callroute SBC doesn’t show in the SBC area of the Teams Admin Center but is still present in the Callroute-E164 voice route. As a result, customer tenants should now better represent the status of their service.

New Call Minute Report

It is now possible to view a report of the total number of minutes consumed within a specified date range providing increased visibility into company phone usage

Number Tagging

It is now possible for customers to tag numbers with custom tags. This allows customers to group numbers together so that searching for particular numbers becomes an easier task. To assign a tag, expand a number and click Edit Tags

Customers can also colour code tags to make them more recognisable.

Colour coding can be done in the Callroute Admin section. You’ll find a new Tag setting

Numbers can be search for using one or more tags at both all range and per range levels

Number Description Now Visible in Additional Details Section

It is now possible to see the whole number description in the Additional Details section of an expanded number. You will no longer need to click the edit description link to view this information.

Automatically Activate and Assign a Teams User’s CLI on Inbound Number Assignment

It is now also possible to activate and assign a Teams user’s CLI directly from inbound number ranges. previously, this would require the user to be activated. Now, activation and number assignment can be done from number ranges, removing the additional step to activate the user in the Teams service first.

Customers will notice a new filter on inbound number assignment allowing you to filter the results by active or inactive users. Inactive will be identified with a purple disc, while active users will have a green disc.

Previously inactive users where not selectable. Now when selected, Callroute will assign them the number as their Teams number and setup their Teams calling features without additional steps

Default Inbound Service Now Pre-Selected When Assigning Inbound Numbers

For bring your own carrier numbers with a default inbound route, when assigning per number destinations, the default service is pre-selected as the primary service allowing admins to implement assignments quicker than before

Removal of the Callroute-E164 Teams Dial Plan

Previously we deployed a custom dial plan to Teams as part of the provisioning process. The purpose of this dial plan was to handle Teams users with an extension LineURI e.g. tel:+441234567890;ext=1234. The dial plan removed the ext=1234 element when calls where placed to us.

We have now implemented an update to our Teams gateway that removes this from the call instead. This means that we can improve performance of Teams number assignments because we do not have to grant the user the dial plan.

In addition, this also helps us support our international customers better. Teams will now use the default tenant dial plan based on the user’s Microsoft 365 license usage location. Therefore, if a user is licensed in Germany and they attempt to dial a national format number, Teams will convert it to a +49 E.164 number instead of +44.

Implementation of New Teams Emergency Call Routing Policy

As part of our Teams deploy service we now deploy emergency calling numbers to the Global Teams Emergency Call Routing Policy. This deploys the following numbers

  • 999
  • 101
  • 112
  • 111
  • 911
  • 190
  • 197

Should any voice enabled user need to call emergency services, these numbers will be dialed without normalization by the Teams dialplan and send to us in national format to adhere with local emergency call routing standards

Update to Callroute-E164 Voice Route to Support New Emergency Calling Implementation

To support the implementation of the Teams Emergency Call Routing Policy, the Callroute-E164 voice route has been updated to accept emergency numbers in addition to E.164 numbers. Customers on older deployments should update their route manually with the new dialed number pattern below

Support for Anonymous Caller ID

Customers can now set their Teams Caller ID Policy to anonymous and Callroute will honour this when calls process through our network.

BT Wholesale BYOC

This month we have released support for partners of BT Wholesale UK to take advantage of Callroute’s bring your own carrier solution. BT customers can now enjoy seamless setup and voice dialing within minutes of activation

Localised Media in LATAM

We are pleased to announce that we can now support LATAM based customers and carriers with regionalised media. Our new datacentre in Sao Paulo, Brazil will allow LATAM carriers and customers keep their call media within region improving quality and service availability in the region.

BYOC IP Based Carriers

We are now able to support carriers who use a customer IP address as the method of identification and billing. This is in addition to our existing support for SIP Registration, Prefix, FQDN and Custom SIP Headers. This feature now means Callroute can support any carrier.

Other

Performance enhancements to Callroute front and back end platforms to improve stability and speed