Check connection of Team Connector and Microsoft Teams

Since many steps are automated and run in the background when setting up Microsoft Teams Direct Routing, it can be difficult to see how the installation is progressing. We'll show you what to look out for.

According to Microsoft, it can take up to 24 hours from the last setup step of the Teams Connector to the complete implementation of the settings in Teams in individual cases. Only then can you make outgoing calls with Teams via easybell.

You can use the following indicators in the Microsoft Teams Admin Center to check how far your settings have already been implemented:

1. VoIP route

Under "VoIP" → "Direct Routing → "VoIP Routes", a route "All" with priority "2" was created.

The entry "All" was set as PSTN usage.

Screenshot MS Teams VoIP Routen — Die VoIP-Routen von Microsoft Teams im Überblick.

2. VoIP routing policies

Under "VoIP" → "VoIP Routing Policies" (), an "All" routing policy has been created.

The PSTN usage entry "All" was assigned here as well.

Screenshot MS Teams Routingrichtlinien — PSTN und VoIP-Route in Microsoft Teams verknüpfen.

3. user management

Under "Users" → "Manageusers", the assigned phone number can be seen.

In addition, the routing policy "All" is set in the "Policies" area.

Screenshot MS Teams Account editieren — Hier können Sie die Richtlinien aufrufen.

Screenshot MS Teams Übersicht der Richtlinien — The guidelines at a glance

If these conditions are met, your phone numbers are fully set up via Direct Routing and the users you have assigned phone numbers to should be able to make outbound calls to us.

If not, please review our Teams Connector instructions again or perform a soft phone test of the phone numbers.

Back

Depending on whether you use a SIP trunk from easybell or another provider, the setup of the Team Connector differs slightly. Here you will find suiting instructions for both cases and some additional information.

detailed view

In this tutorial, we will explain step-by-step how to use the easybell Teams Connector to connect a SIP Trunk from easybell to Microsoft Teams and assign phone numbers to Teams users.

detailed view

In this article, we will go over how to assign multiple phone numbers to a Microsoft Teams user when using easybell's Teams Connector.

detailed view

We tell you the licenses you need for Microsoft Teams to connect your own SIP Trunk with the Teams Connector.

detailed view

Störungen können auch von Ihrem Endgerät (Router oder Telefon) verursacht werden.

detailed view

In this article, we explain in detail how to set your firewall correctly to ensure smooth operation of your IP phones or PBX with easybell SIP accounts or the Cloud Telefonanlage (Cloud PBX).

detailed view

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your consent to using cookies.	2 year	HTML	Website
_pk_id	Used to store a few details about the user such as the unique visitor ID.	13 months	HTML	Matomo
_pk_ses	Short lived cookie used to temporarily store data for the visit.	30 minutes	HTML	Matomo
fe_typo_user	Assigns your browser to a session on the server.	session	HTTP	Website
apcCheckData	Availability Check	24 hours	HTML	Website
order_session	Availability Check	36 hours	HTML	Website

Name	Purpose	Lifetime	Type	Provider
_clck	Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.	1 year	HTML	Microsoft Corporation
_clsk	Connects multiple page views by a user into a single Clarity session recording.	1 day	HTML	Microsoft Corporation
CLID	Identifies the first-time Clarity saw this user on any site using Clarity.	1 year	HTML	Microsoft Corporation
ANONCHK	Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.	10 minutes	HTML	Microsoft Corporation
MR	Indicates whether to refresh MUID.	7 days	HTML	Microsoft Corporation
MUID	Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.	1 year	HTML	Microsoft Corporation
SM	Used in synchronizing the MUID across Microsoft domains.	session	HTML	Microsoft Corporation
_fbp	Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers	3 months	HTML	Facebook
fr	Ads targeting cookie for Facebook	3 months	HTML	Facebook
AnalyticsSyncHistory	This cookie is set by LinkedIn. Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries	30 days	HTML	LinkedIn
UserMatchHistory	LinkedIn Ads ID syncing	30 days	HTML	LinkedIn
bcookie	Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform. For more information about LinkedIn cookies, please navigate to https://www.linkedin.com/legal/l/cookie-table.	1 year	HTML	LinkedIn
bscookie	Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings	1 year	HTML	LinkedIn
lang	Used to memorize a user's language setting.	session	HTML	LinkedIn
li_sugr	Used to make a probabilistic match of a user's identity outside the Designated Countries	90 days	HTML	LinkedIn
lidc	To facilitate data center selection.	24 hours	HTML	LinkedIn
_guid	Used to identify a LinkedIn Member for advertising through Google Ads	90 days	HTML	Google
_gcl_au	Used to measure ad and campaign performance and conversion rates for Google ads on a site visited	90 days	HTML	Google
_gcl_aw	Used through Google Ads to understand user interaction with the site and advertising	90 days	HTML	Google
_gcl_dc	Used through Google Campaign Manager and DV 360 to understand user interaction with the site and advertising	90 days	HTML	Google
_ga	Used to distinguish users.	2 years	HTML	Google
_ga_V3PFWQFH0B	Used to persist session state.	2 years	HTML	Google

help center

Check connection of Team Connector and Microsoft Teams

1. VoIP route

2. VoIP routing policies

3. user management

We are honored!

Customers, partners and the trade press place their trust in us.