Using Reverse Number Lookup in Microsoft Teams

What is Reverse Number Lookup (RNL)

When you receive calls in your Teams client Reverse Number Lookup (RNL) will show the displayname instead of the actual phone number.

With RNL the system converts the number that is calling you to a name configured in your outlook contact or even Azure Active Directory.

The following order will be used to check and the last one will always override:

• SIP Invite From Header
• Azure Active Directory
• Outlook contacts
• Teams contacts

Requirements Exchange

The callee, in your tenant, needs to have a Exchange Online mailbox. The source object containing the phone number(s) to be matched against need to be mail-enabled in Exchange, either in Exchange Online or in Exchange on-premises with an Exchange Hybrid deployment. Mail-enabled objects are:

Using custom Tags with Microsoft Teams

With tags, you can categorize people based on attributes, such as role, project, skill, training, or location. For example, a “Project member” or “Manager” or Customer (guests)" tag will enable you to reach groups of people in Teams without having to type every single name.

Once the tag is added, just use “@mention” in a channel. Everyone who has been assigned with the specific tag will receive a notification just as they would if they were “@mentioned” individually.

Microsoft Teams for Linux

This how to is written for debian distro based operating systems. During this test i’m using Ubuntu Desktop 18.04.3 LTS.

Installing Microsoft Teams

First of all download the right client package for Microsoft Teams.

For my Ubuntu desktop i’m using the DEB 64-bit installer. You can also download the package using wget.

Download the package from the Teams website. You can find the latest version right here (Right click the version and copy the link)

Using eDiscovery with Microsoft Teams

Recently i was involved in a case where we needed to discover some conversations between a internal and external company due to some illegal activities.

I want to share some information on eDiscovery and Content Search with Microsoft Teams from a Security and Compliance view, this is quite simple but many of us are unaware how could you filter out the conversations and in specific to Microsoft Teams conversations.

Assign Permissions

If you have already set the permissions you can skip this first chapter.

Optimize your network for Microsoft Teams

Before you start planning your network for Microsoft Teams network connectivity, it is important to understand the connectivity principles for managing Microsoft Teams traffic and getting the best possible performance for your end users.

Traditional enterprise networks are mostly designed to provide users access to applications and data hosted in company or co-located datacenters with focus on strong perimeter security and easy to manage for the IT departments. The traditional model assumes that users will access applications and data from inside the corporate network perimeter, over WAN links from branch offices, or remotely over VPN connections and will use one break out to the public internet managed by a corporate firewall.

Setup Direct Routing with Microsoft teams

Direct Routing lets you connect a supported, customer-provided Session Border Controller (SBC) to the Microsoft Phone System. With this capability you can configure on-premises PSTN (bring your own sip trunk, BYOT) connectivity with your Microsoft Teams client.

There are a couple of certified SBC vendors you can use to setup Direct Routing.

• Audiocodes
• Ribbon
• AnyNode
• Thinktel

What do you need?

In order to setup Direct routing you will need to have some prerequisites:

No RingBack when using Microsoft Teams Direct Routing

Recently we have decomissioned our Microsoft Cloud Connector Edition and migrated most of our telephony users to Microsoft Teams with Direct Routing. One big issue we faced was that when a external caller called us by PSTN, they only heard one RingBack tone followed by deadly silence till someone picked up or landed in Azure VoiceMail.

Thanks to my friend Goos Stuut, working at our local distri for Audiocodes we found out what was happening and we solved this issue.