Can I use multiple SIP trunks in Microsoft Teams?

help center

In this article, we explain what you should bear in mind if you want to connect multiple SIP trunks to Microsoft Teams with our Teams integration solutions.

Both Call2Teams Go for the cCloud Telefonanlage and the Teams Connector allow you to link multiple SIP trunks to Microsoft Teams. The local network of the SIP trunk does not matter - you can, for example, connect several branches to Microsoft Teams and bundle the communication there.

It's important which teams integration solution you are using.
You can find a comparison and further information on our Teams integration overview page.

Multiple SIP trunks with the Teams Connector

You can also use the Teams Connector to connect multiple SIP trunks to Microsoft Teams. Simply follow our instructions for each trunk: Connecting Microsoft Teams with an easybell SIP trunk via the Teams Connector

Attention!

If you use SIP trunks from several local networks, you must:

Have enough Teams Connector accounts booked in the respective account
The connection to Microsoft Teams must be set up in the account of the respective trunk

Back

If you want to use your old SIP trunk in Microsoft Teams without using Microsoft call plans, Easybell offers several options. We briefly present our solutions for Teams integration with reference to the respective instructions.

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

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.

detailed view

3-D-Figur mit rundem weißen Körper, zwinkernd und Daumen-hoch-Geste vor orangefarbenem Halbkreis

We are honored!

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

Accept all cookies

These cookies are needed for a smooth operation of our website.

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
order_session	Availability Check	12 hours	HTML	Website
order-available	stores Availability Check result	12 hours	HTML	Website

Accept all cookies

These Cookies helps us improve the customer experience for you.

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
_uetsid	Microsoft Bing Ads session identifier for conversion tracking	1 day	HTML	Microsoft
_uetvid	Microsoft Bing Ads visitor identifier for remarketing	13 months	HTML	Microsoft
MUIDB	Mirrors MUID across Microsoft/Bing domains for ad tracking	1 year	HTML	Microsoft
_uetmsclkid	Used by Microsoft Advertising to track user interactions and improve ad targeting.	1 year	HTML	Microsoft
_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
_fbc	Stores Facebook click identifier (fbclid) for ad attribution	90 days	HTML	Facebook
datr	Facebook cookie that identifies browsers for security, fraud prevention, and ad delivery	2 years	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
li_fat_id	Stores LinkedIn click identifier for ad attribution	30 days	HTML	LinkedIn
lms_ads	Identifies LinkedIn members for ad targeting	30 days	HTML	LinkedIn
lms_analytics	Identifies LinkedIn members for analytics	30 days	HTML	LinkedIn
li_gc	Stores LinkedIn guest consent for cookies to ensure privacy choices are respected	6 months	HTML	LinkedIn
li_mc	LinkedIn marketing conversions cookie for audience matching and analytics	6 months	HTML	LinkedIn
li_oatml	Identifies LinkedIn members outside LinkedIn for advertising and analytics	1 month	HTML	LinkedIn
liap	Indicates if a non-WWW domain can access a LinkedIn member's ID for tracking and advertising	1 year	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
test_cookie	Checks whether browser accepts third‑party cookies so Google can deliver personalised ads	15 minutes	HTML	Google
IDE	Google DoubleClick cookie used for delivering targeted advertisements and measuring ad effectiveness	13 months	HTML	Google
DSID	Google DoubleClick cookie that links user identity across devices for personalised advertising	2 weeks	HTML	Google
RUL	DoubleClick cookie used to determine if ads have been displayed correctly and for remarketing	12 months	HTML	Google
_ga	Used to distinguish users.	2 years	HTML	Google
_ga_V3PFWQFH0B	Used to persist session state.	2 years	HTML	Google
_gid	Google Analytics session identifier that distinguishes users	1 day	HTML	Google