Home

Team Direct Routing/Domain/SBC Config Questions

%3CLINGO-SUB%20id%3D%22lingo-sub-294470%22%20slang%3D%22en-US%22%3ETeam%20Direct%20Routing%2FDomain%2FSBC%20Config%20Questions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294470%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20direct%20routing%20setup%20questions%20and%20required%20clarification.%20I%20have%20been%20reading%20through%20the%20various%20pages%20and%20consulting%20various%20SBC%20vendor%20docs%20as%20well.%20I%20took%20the%20following%20example%20from%20one%20of%20the%20pages%20for%20a%20multi-tenant%20hosted%20setup.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStarting%20from%20one%20of%20the%20provided%20examples%20for%20a%20single%20SBC%20scenario.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CSTRONG%3ENew%20domain%20name%3C%2FSTRONG%3E%3C%2FTD%3E%3CTD%3E%3CSTRONG%3EType%3C%2FSTRONG%3E%3C%2FTD%3E%3CTD%3E%3CSTRONG%3ERegistered%3C%2FSTRONG%3E%3C%2FTD%3E%3CTD%3E%3CSTRONG%3ECertificate%20SAN%20for%20SBC%3C%2FSTRONG%3E%3C%2FTD%3E%3CTD%3E%3CSTRONG%3ETenant%20default%20domain%20in%20the%20example%3C%2FSTRONG%3E%3C%2FTD%3E%3CTD%3E%3CSTRONG%3EFQDN%20name%20that%20SBC%20must%20present%20in%20the%20Contact%20header%20when%20sending%20calls%20to%20users%3C%2FSTRONG%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Ecustomers.adatum.biz%3C%2FTD%3E%3CTD%3EBase%3C%2FTD%3E%3CTD%3EIn%20carrier%20tenant%3C%2FTD%3E%3CTD%3E*.customers.adatum.biz%3C%2FTD%3E%3CTD%3Eadatum.biz%3C%2FTD%3E%3CTD%3ENA%2C%20this%20is%20a%20service%20tenant%2C%20no%20users%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Esbc1.customers.adatum.biz%3C%2FTD%3E%3CTD%3ESubdomain%3C%2FTD%3E%3CTD%3EIn%20a%20customer%20tenant%3C%2FTD%3E%3CTD%3E*.customers.adatum.biz%3C%2FTD%3E%3CTD%3Ewoodgrovebank.us%3C%2FTD%3E%3CTD%3Esbc1.customers.adatum.biz%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Esbc2.customers.adatum.biz%3C%2FTD%3E%3CTD%3ESubdomain%3C%2FTD%3E%3CTD%3EIn%20a%20customer%20tenant%3C%2FTD%3E%3CTD%3E*.customers.adatum.biz%3C%2FTD%3E%3CTD%3Econtoso.com%3C%2FTD%3E%3CTD%3Esbc2.customers.adatum.biz%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Esbc3.customers.adatum.biz%3C%2FTD%3E%3CTD%3ESubdomain%3C%2FTD%3E%3CTD%3EIn%20a%20customer%20tenant%3C%2FTD%3E%3CTD%3E*.customers.adatum.biz%3C%2FTD%3E%3CTD%3Eadventureworks.com%3C%2FTD%3E%3CTD%3Esbc3.customers.adatum.biz%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20questions%20may%20be%20vendor%20dependent%20but%20I%20am%20just%20trying%20to%20get%20the%20general%20idea.%20We%20haven't%20selected%20a%20vendor%20yet.%3CBR%20%2F%3E1.%20I%20am%20assuming%20that%20a%20single%2Fsame%20Public%20IP%20is%20used%20to%20map%20the%20various%20tenant%20FQDNs%20sbc1.customers.aadatum.biz%20sbc2...sbc3..%20etc%2C%20however%2C%20the%20TLS%20ports%20are%20unique%20for%20each%20tenant%20so%20that%20a%20unique%20trunk%20can%20be%20built%20for%20each%20customer%20tenant%20%26lt%3B-%26gt%3B%20SBC%20relationship%20using%20the%20New-CSOnlinePSTNGateway%20command.%3CBR%20%2F%3E%3CBR%20%2F%3E2.If%20I%20were%20to%20add%20a%20second%20SBC%20in%20a%20different%20site%20taking%20contoso.com%20as%20an%20example%20customer.%3CBR%20%2F%3EWould%20I%20have%20to%20%3A%3CBR%20%2F%3Ea.register%20a%20new%20subdomain%20eg.%20sbc2a.customers.adatum.biz%20in%20contoso.com%20tenant%20%3F%3CBR%20%2F%3Eb.%20activate%20a%20dummy%20user%20in%20contoso%20tenant%2C%20using%20subdomain%20sbc2a.customers.adatum.biz%20%3F%20Does%20this%20step%20have%20to%20repeated%20every%20time%20a%20new%20SBC%20is%20added%20to%20the%20provider%20pool%20%3F%3CBR%20%2F%3Ec.%20lastly%20build%20a%20trunk%20to%20the%20second%20SBC%20using%20New-CSOnlinePSTNGateway%20command.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20We%20are%20planning%20to%20build%20a%20POC%20and%20test%20this%20in%20our%20service%20tenant.%20Moving%20forward%2C%20we%20will%20sell%20this%20as%20a%20product%20and%20setup%20customers%20as%20per%20previously%20described%20multi-tenant%20hosted%20method.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20there%20be%20any%20issues%20creating%20and%20setting%20up%20the%20POC%20using%20our%20base%20domain%20eg.%20adatum.biz%20so%20users%20will%20be%20user1%40adatum.biz%20and%20FQDN%20of%20sbc%20will%20be%20sbc.adatum.biz%20or%20do%20you%20suggest%20that%20we%20use%20subdomain%20customers.adatum.biz%2C%20build%20users%20as%20user1%40customers.adatum.biz%20and%20set%20SBC%20FQDN%20as%20sbc.customers.adatum.biz%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-294470%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295267%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20Direct%20Routing%2FDomain%2FSBC%20Config%20Questions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295267%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20confirmation%20Andrew.%20We%20plan%20on%20doing%20this%20as%20well.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295164%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20Direct%20Routing%2FDomain%2FSBC%20Config%20Questions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295164%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20done%20it%20in%20the%20way%20you%20are%20with%202%20SBC's%20with%20unique%20IP's.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEach%20tenant%20you%20want%20to%20support%20will%20have%202%20domains%20added%3A%3C%2FP%3E%0A%3CP%3E1.%20%3CEM%3EcusName%3C%2FEM%3E.sbc1.hostingprovider.com%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E2.%26nbsp%3B%3C%2FSPAN%3E%3CEM%3EcusName%3C%2FEM%3E%3CSPAN%3E.sbc2.hostingprovider.com%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20records%20will%20resolve%20each%20of%20your%20SBC%20IP's.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThen%20you%20create%20routes%20in%20each%20customer%20tenant%20(among%20other%20configuration)%20that%20include%20both%20SBC's.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EAndrew%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295097%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20Direct%20Routing%2FDomain%2FSBC%20Config%20Questions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295097%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Linus.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20to%20clarify.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Our%20model%20would%20be%20to%20have%20a%20SBC%20cluster%20with%20same%20IP%2FFQDN%20in%20one%26nbsp%3Bsite%20and%20a%20second%20SBC%20in%20a%20second%20site%20with%20a%20different%20IP%20and%20different%20FQDN.%26nbsp%3B%20Alternativly%2C%20is%20it%20a%20supported%20scenario%20to%20have%20the%20same%20FQDN%2Fhostname%20but%20two%20different%20IPs%20representing%20two%20different%20locations.%20i.e%20the%20hostname%20would%20resolve%20to%20a%20two%20IPs%2C%20the%20first%20being%20the%20SBC%20in%20the%20primary%20DC%20and%202nd%20IP%20would%20be%20the%20SBC%20in%20the%20secondary%20DC%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20%26nbsp%3BSo%20a%3CSPAN%3Edatum.biz%20being%20our%20base%20domain%2C%26nbsp%3Bcustomers.adatum.biz%20would%20be%20the%20subdomain%20and%20the%20SBC%20would%20be%26nbsp%3Bsbc1.customers.adatum.biz%20for%20testing%20calls%20in%20our%20service%20tenant.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20the%20first%20customer%2Fhosted%20tenant%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Esbc2.customers.adatum.biz%20would%20be%20the%20new%20domain%20and%26nbsp%3Bsbc2.customers.adatum.biz%20FQDN%20for%20the%20SBC.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-294935%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20Direct%20Routing%2FDomain%2FSBC%20Config%20Questions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294935%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20will%20try%20to%20answer%20your%20questions.%3C%2FP%3E%3CP%3E1.%20Yes%20you%20can%20use%20the%20same%20IP%20but%20different%20static%20host%20names%20(used%20in%20MS%20Phone%20system%20to%20identify%20customer)%20and%20different%20ports%20for%20each%20customers.%3C%2FP%3E%3CP%3E2.%20Yes%2C%20they%20would%20have%20to%20do%20those%20steps%20for%20a%20secondary%20SBC.%20But%20it%20would%20be%20better%20for%20you%20as%20hosting%20provider%20to%20setup%20the%20SBC%20load%20balanced%20so%20it%20is%20the%20same%20IP%2Fhost%20name%20that%20MS%20connects%20to.%3C%2FP%3E%3CP%3E3.%20If%20your%20company%20domain%20name%20is%26nbsp%3B%3CSPAN%3Eadatum.biz%20i%20suggest%20that%20you%20create%20a%20subdomain%20ex.%20customers.adatum.biz%20and%20setup%20SBC%20with%20sbc1.customers.adatum.biz%20or%20instead%20of%20using%26nbsp%3Badatum.biz%20you%20buy%20a%20separate%20domain%20for%20this%20service%2C%20ex.%26nbsp%3Badatumphone.biz%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
azrabi
New Contributor

Hi,

I have direct routing setup questions and required clarification. I have been reading through the various pages and consulting various SBC vendor docs as well. I took the following example from one of the pages for a multi-tenant hosted setup.

 

Starting from one of the provided examples for a single SBC scenario.

 

New domain nameTypeRegisteredCertificate SAN for SBCTenant default domain in the exampleFQDN name that SBC must present in the Contact header when sending calls to users
customers.adatum.bizBaseIn carrier tenant*.customers.adatum.bizadatum.bizNA, this is a service tenant, no users
sbc1.customers.adatum.bizSubdomainIn a customer tenant*.customers.adatum.bizwoodgrovebank.ussbc1.customers.adatum.biz
sbc2.customers.adatum.bizSubdomainIn a customer tenant*.customers.adatum.bizcontoso.comsbc2.customers.adatum.biz
sbc3.customers.adatum.bizSubdomainIn a customer tenant*.customers.adatum.bizadventureworks.comsbc3.customers.adatum.biz

 

Some questions may be vendor dependent but I am just trying to get the general idea. We haven't selected a vendor yet.
1. I am assuming that a single/same Public IP is used to map the various tenant FQDNs sbc1.customers.aadatum.biz sbc2...sbc3.. etc, however, the TLS ports are unique for each tenant so that a unique trunk can be built for each customer tenant <-> SBC relationship using the New-CSOnlinePSTNGateway command.

2.If I were to add a second SBC in a different site taking contoso.com as an example customer.
Would I have to :
a.register a new subdomain eg. sbc2a.customers.adatum.biz in contoso.com tenant ?
b. activate a dummy user in contoso tenant, using subdomain sbc2a.customers.adatum.biz ? Does this step have to repeated every time a new SBC is added to the provider pool ?
c. lastly build a trunk to the second SBC using New-CSOnlinePSTNGateway command.

 

3. We are planning to build a POC and test this in our service tenant. Moving forward, we will sell this as a product and setup customers as per previously described multi-tenant hosted method.

 

Will there be any issues creating and setting up the POC using our base domain eg. adatum.biz so users will be user1@adatum.biz and FQDN of sbc will be sbc.adatum.biz or do you suggest that we use subdomain customers.adatum.biz, build users as user1@customers.adatum.biz and set SBC FQDN as sbc.customers.adatum.biz ?

 

Thanks

4 Replies

Hi,

I will try to answer your questions.

1. Yes you can use the same IP but different static host names (used in MS Phone system to identify customer) and different ports for each customers.

2. Yes, they would have to do those steps for a secondary SBC. But it would be better for you as hosting provider to setup the SBC load balanced so it is the same IP/host name that MS connects to.

3. If your company domain name is adatum.biz i suggest that you create a subdomain ex. customers.adatum.biz and setup SBC with sbc1.customers.adatum.biz or instead of using adatum.biz you buy a separate domain for this service, ex. adatumphone.biz

Thanks Linus.

 

Just to clarify.

 

2. Our model would be to have a SBC cluster with same IP/FQDN in one site and a second SBC in a second site with a different IP and different FQDN.  Alternativly, is it a supported scenario to have the same FQDN/hostname but two different IPs representing two different locations. i.e the hostname would resolve to a two IPs, the first being the SBC in the primary DC and 2nd IP would be the SBC in the secondary DC ?

 

 

3.  So adatum.biz being our base domain, customers.adatum.biz would be the subdomain and the SBC would be sbc1.customers.adatum.biz for testing calls in our service tenant.

 

For the first customer/hosted tenant

sbc2.customers.adatum.biz would be the new domain and sbc2.customers.adatum.biz FQDN for the SBC.

Thanks

 

We've done it in the way you are with 2 SBC's with unique IP's.

 

Each tenant you want to support will have 2 domains added:

1. cusName.sbc1.hostingprovider.com

2. cusName.sbc2.hostingprovider.com

 

These records will resolve each of your SBC IP's.

 

Then you create routes in each customer tenant (among other configuration) that include both SBC's.

 

 

 

 

 

Thanks,

Andrew

Thanks for the confirmation Andrew. We plan on doing this as well. 

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
202 Replies