SOLVED

MS Teams - call queue - number from direct routing?

%3CLINGO-SUB%20id%3D%22lingo-sub-251661%22%20slang%3D%22en-US%22%3EMS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251661%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20to%20create%20Call%20queue%20for%20Microsoft%20Teams%20(or%20Skype%20for%20Business%20Online)%2C%20when%20phone%20number%20(line%20number%20%2F%20caller%20ID)%20should%20be%20used%20from%20Direct%20Routing%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20do%20not%20see%20Powershell%20way%2C%20and%20I%20do%20have%20option%20just%20to%20purchase%20new%20numbers%20from%20Microsoft%20directly%2C%20but%20I%20want%20to%20use%20existing%20numbers%20(that%20can%20not%20be%20ported%20to%20Microsoft)%2C%20and%20are%20in%20use%20through%20Microsoft%20Teams%20%E2%80%93%20direct%20routing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%2C%3C%2FP%3E%0A%3CP%3EKind%20regards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-251661%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECall%20Queues%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECall%20Queues%20questions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-329741%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-329741%22%20slang%3D%22en-US%22%3EI%20would%20like%20to%20know%20more%20about%20how%20to%20set%20this%20up.%20We%20tried%20following%20your%20guide%20and%20could%20not%20get%20it%20working.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328607%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328607%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20it%20is%20funny%2C%20it%20is%20marked%20as%20%22Launched%22%20%2C%20but%20with%20note%2C%20that%20this%20important%20part%20will%20be%20in%20next%20quarter.%3C%2FP%3E%0A%3CP%3EIt%20will%20be%20much%20better%20if%20they%20communicate%20this%20feature%20as%20a%20separate%20entry%20in%20roadmap%20with%20current%20status..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328580%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328580%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20that%20this%20is%20on%20the%20Microsoft%20road%20map..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20see%20here%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fskypeandteams.blob.core.windows.net%2Fartefacts%2FSkype%2520for%2520Business%2520to%2520Teams%2520Capabilities%2520Roadmap.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fskypeandteams.blob.core.windows.net%2Fartefacts%2FSkype%2520for%2520Business%2520to%2520Teams%2520Capabilities%2520Roadmap.pdf%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3DMicrosoft%2520Teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3DMicrosoft%2520Teams%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20out%20the%20%E2%80%9CCall%20Queues%E2%80%9D%20Roadmap%20on%20the%20second%20URL%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EMicrosoft%20Teams%20-%20Call%20Queues%3C%2FSTRONG%3E%3CBR%20%2F%3EPhase%201%20of%20Call%20Queues%20is%20now%20available%20for%20Teams.%20The%20work%20primarily%20focused%20on%20enabling%20the%20same%20set%20of%20features%20previously%20available%20to%20Skype%20for%20Business%20Online.%20Additional%20work%20is%20ongoing%20for%20support%20for%20phone%20number%20usage%20via%20Direct%20Routing%20and%20is%20expected%20next%20quarter.%3CBR%20%2F%3EMore%20info%3CBR%20%2F%3E%E2%80%A2%20Featured%20ID%3A%2024174%3CBR%20%2F%3E%E2%80%A2%20Added%20to%20Roadmap%3A%2010%2F24%2F2017%3CBR%20%2F%3E%E2%80%A2%20Last%20Modified%3A%201%2F29%2F2019%3CBR%20%2F%3E%E2%80%A2%20Tags%3A%20Microsoft%20Teams%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327509%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327509%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20blog%20article%20states%20%22%3CSPAN%3E**This%20article%20does%20not%20applies%20to%20Direct%20Routing%20with%20Microsoft%20Teams.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDo%20you%20have%20this%20working%20with%20Direct%20Routing%2FTeams%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-294404%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294404%22%20slang%3D%22en-US%22%3ENot%20sure%20if%20this%20will%20be%20relevant%20at%20this%20stage%20but%20we%20have%20built%20a%20Microsoft-certified%20Cloud%20Connector%20that%20delivers%20voice%20services%20for%20Teams%20calling%20directly%20to%20the%20O365%20Tenant.%20Our%20geo-redundant%20solution%20also%20completes%20the%20missing%20PBX%20and%20legacy%20feature-set%2C%20provides%20full%20integration%20capabilities%20to%20Call%2FContact%20Centers%20and%20CRMs%20and%20handles%20extension%20dialing%2C%20DID%20%2FTF%20number%20porting%2C%20as%20we%20are%20a%20Tier1%20Cloud%20UC%20carrier.%20Our%20cloud%20dial-plan%20allows%20for%20legacy%20PBX%20or%20Skype4B%20to%20Teams%20extension%20dialing%20during%20migration%20as%20well.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292035%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292035%22%20slang%3D%22en-US%22%3E%3CP%3EActually%2C%20you%20can%20use%20on-premises%20PSTN%20numbers%20with%20call%20queue.%20The%20trick%20is%20to%20convert%20the%20destination%20number%20to%20AA%5CCQ%20SIP%20URI%20Guid.%20There's%20no%20service%20numbers%20involved%20in%20this%20setup.%20I%20have%20done%20this%20for%20all%20of%20the%20Direct%20Routing%20deployments%20so%20far%20and%20works%20well%20too.%20I've%20written%20a%20blog%20about%20it.%20Have%20a%20look%20and%20see%20if%20that%20works%20for%20you%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fthamaraw.com%2F2018%2F09%2F10%2Fusing-on-premises-pstn-numbers-for-call-queues-and-auto-attendant-for-microsoft-teams%2F%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fthamaraw.com%2F2018%2F09%2F10%2Fusing-on-premises-pstn-numbers-for-call-queues-and-auto-attendant-for-microsoft-teams%2F%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291903%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291903%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20basically%2C%20you%20have%20to%20pay%20to%20Microsoft%20for%20a%20number%20and%20for%20voice%20minutes%2C%20and%20can%20not%20use%20your%20on-prem%20numbers%2C%20ISP%20and%20pricing.%3C%2FP%3E%0A%3CP%3EThat%20is%20something%20that%20we%20wait%20to%20support%20direct%20SIP%20Trunk%20for%20existing%20service%20numbers%2C%20etc.%2C%20not%20doing%20forwarding%2Ftransformation%20....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291728%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291728%22%20slang%3D%22en-US%22%3E%3CP%3ENo.%20You%20won't%20use%20the%20Microsoft's%20service%20number%20to%20nothing%20but%20just%20routing%20the%20calls%20internally%20using%20your%20SIP%20Trunk.%3C%2FP%3E%3CP%3EYou%20could%20forward%20one%20of%20your%20DIDs%20to%20the%20service%20number%2C%20as%20example.%3C%2FP%3E%3CP%3EThe%20difference%20is%20that%20it%20is%20not%20possible%20to%20configure%20your%20own%20DID%20directly%20on%20the%20call%20queue%2C%20so%2C%20you%20create%20a%20%22transformation%22%20on%20the%20destination%20number.%3C%2FP%3E%3CP%3EAlways%20that%20someone%20dials%20your%20DID%2C%20you%20send%20the%20call%20to%20Microsoft's%20service%20number%20of%20your%20call%20queue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291727%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291727%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20but%20we%20are%20talking%20about%20getting%20from%20on-prem%20through%20SIP%20trunk%20-%20my%20existing%20service%20numbers%2C%20to%20the%20Teams..%2C%20not%20buying%20them%20from%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291725%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291725%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20guys%2C%3C%2FP%3E%3CP%3EActually%20it%20is%20possible%20and%20works%20pretty%20well.%3C%2FP%3E%3CP%3EWhat%20you%20have%20to%20do%20is%20to%20get%20a%20service%20number%20from%20Microsoft%20and%20then%20create%20a%20call%20queue%20or%20auto%20attendant%20on%20Legacy%20SfB%20Portal%20using%20this%20service%20number.%3C%2FP%3E%3CP%3EAfter%20that%2C%20always%20that%20your%20gateway%2Fsbc%20receives%20a%20call%20on%20the%20extension%20number%20(private%20number)%20that%20you%20want%20to%20use%20for%20the%20CQ%2FAA%20you%20send%20the%20call%20to%20MS%20Teams%20throught%20Direct%20Routing%20using%20as%20destination%20number%2C%20the%20number%20of%20the%20service%20number%20that%20you%20are%20using.%3C%2FP%3E%3CP%3EFor%20instance%2C%20if%20someone%20dials%209999%20internally%2C%20you%20must%20forward%20this%20call%20to%20%2B12122345678%20(Microsoft's%20service%20number%20that%20you%20got).%3C%2FP%3E%3CP%3EAs%20we%20are%20talking%20about%20Teams%2C%20it%20is%20important%20that%20all%20of%20the%20users%20on%20call%20queue%20(group)%20were%20already%20configured%20to%20use%20Teams%20as%20their%20native%20client.%3C%2FP%3E%3CP%3EI%20hope%20it%20helps!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252374%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252374%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20you%20go%2C%20just%20like%20I%20told%20you.%26nbsp%3B%3Athumbs_up%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251885%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251885%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20so%20this%20is%20probably%20not%20supported%2C%20since%20others%20are%20asking%20the%20same...%3C%2FP%3E%0A%3CP%3ERef%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F35022145-allow-service-numbers-from-a-sip-trunk-via-teams-d%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F35022145-allow-service-numbers-from-a-sip-trunk-via-teams-d%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251748%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251748%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20hope%2C%20because%20the%20way%20it%20is%20now%20with%20the%20service%20number%20in%20Office%20365%2C%20it%20simply%20doesn%E2%80%99t%20work%20when%20using%20Direct%20Routing%20or%20CCE.%20Rebellions%20are%20built%20on%20hope%2C%20remember.%20%3Asmiling_face_with_smiling_eyes%3A%20If%20it%E2%80%99s%20not%20on%20User%20Voice%20then%20you%20should%20put%20it%20there%2C%20I%E2%80%99ll%20vote%20for%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251670%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251670%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20sure%3F%20Where%20is%20documentation%3F%20If%20so%2C%20I%20can%20not%20find%20feature%20request%20on%20ideas%20site...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251663%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251663%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%2C%20it%E2%80%99s%20not%20possible%20to%20use%20service%20numbers%20via%20Direct%20Routing.%20Let%E2%80%99s%20hope%20it%20will%20be%20possible%20in%20the%20future%2C%20because%20as%20you%20say%20it%E2%80%99s%20not%20always%20possible%20to%20port%20just%20your%20switchboard%20number%2C%20for%20example.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20meanwhile%2C%20do%20a%20static%20call%20forward%20of%20your%20switchboard%20number%20to%20the%20service%20number%20acquired%20from%20Office%20365%2C%20that%20should%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EMarten%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-452408%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-452408%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F23116%22%20target%3D%22_self%22%3E%40Sascha%20Stops%3C%2FA%3E%20mentioned%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FAuto-Attendant-and-Call-Queues-with-Direct-Routing%2Fm-p%2F452363%23M29950%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ethis%20thread%3C%2FA%3E%2C%20that%20the%20documentation%20to%20this%20feature%20is%20now%20online%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmanage-resource-accounts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSPAN%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmanage-resource-accounts%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EBut%20in%20our%20case%20the%20feature%20is%20not%20available%20yet%20in%20Teams%20Admin%20Center%2C%20we%20don't%20have%20the%20option%20%22Resource%20Account%22%20under%20%22Org-wide%20settings%22.%20Can%20anyone%20confirm%20this%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576711%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576711%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F321129%22%20target%3D%22_blank%22%3E%40sasfbr%3C%2FA%3E%26nbsp%3BYou%20should%20see%20it%20now%2C%20it's%20supposed%20to%20be%20GA%2C%20i'm%20seeing%20it%20in%20both%20tenants%20i%20have.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576764%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576764%22%20slang%3D%22en-US%22%3E%3CP%3EI%20do%20confirm%20this%20is%20resolved%20and%20now%20working.%3C%2FP%3E%0A%3CP%3EEU%20tenants%2C%20first%20release%20features.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGo%20to%20%3CA%20href%3D%22https%3A%2F%2Fadmin.teams.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fadmin.teams.microsoft.com%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E1)%20Create%20resource%20account%3C%2FP%3E%0A%3CP%3E2)%20Create%20auto-attendant%20or%20call%20queue%2C%20connect%20with%20resource%20account%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EConnect%20with%20powershell%20and%3A%3C%2FP%3E%0A%3CP%3E3)%20assign%20phone%20number%20from%20on-premise%20%2F%20direct%20routing%20through%20cmdlet%20to%20resource%20account%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576766%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576766%22%20slang%3D%22en-US%22%3EI%20do%20confirm%20this%20is%20resolved%20and%20now%20working.%3CBR%20%2F%3EEU%20tenants%2C%20first%20release%20features.%3CBR%20%2F%3E%3CBR%20%2F%3EGo%20to%20%3CA%20href%3D%22https%3A%2F%2Fadmin.teams.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fadmin.teams.microsoft.com%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E1)%20Create%20resource%20account%3CBR%20%2F%3E2)%20Create%20auto-attendant%20or%20call%20queue%2C%20connect%20with%20resource%20account%3CBR%20%2F%3E%3CBR%20%2F%3EConnect%20with%20powershell%20and%3A%3CBR%20%2F%3E3)%20assign%20phone%20number%20from%20on-premise%20%2F%20direct%20routing%20through%20cmdlet%20to%20resource%20account%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-622391%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-622391%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F330%22%20target%3D%22_blank%22%3E%40Hrvoje%20Kusulja%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnybody%20else%20having%20issues%20with%20Audio%20(Media%20Flow)%20when%20using%20Direct%20Routing%20for%20a%20Call%20Queue.%20Inbound%5COutbound%20PSTN%20calls%20work%20fine%20to%20the%20Teams%20User%20Direct%20Dial.%20However%2C%20when%20I%20call%20the%20Teams%20Call%20Queue%20(own%20number%20assigned%20to%20Resource%20Account)%2C%20the%20call%20rings%20on%20the%20Teams%20client%20and%20can%20be%20answered%20but%20get%20no%20media%20flow%20either%20way%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-623110%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-623110%22%20slang%3D%22en-US%22%3EWe%20had%20that%20same%20issue%20with%20call%20queues%20and%20Microsoft%20service%20numbers.%20There%20is%20certainly%20some%20issues%20in%20the%20call%20queue%20functionality.%20When%20we%20switched%20to%20direct%20routing%20things%20were%20better%20but%20not%20perfect.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-623235%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-623235%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F277131%22%20target%3D%22_blank%22%3E%40ialastairhunter%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks.%20We%20are%20Direct%20Routing%20and%20haven't%20used%20MS%20provided%20service%20numbers.%3C%2FP%3E%3CP%3EWe%20had%20been%20waiting%20for%20them%20to%20allow%20Direct%20Routing%20numbers%20for%20Call%20Queues%20which%20only%20went%20into%20GA%20recently%20so%20purposefully%20held%20off.%20Obviously%2C%20they%20still%20have%20a%20bit%20of%20work%20to%20do!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-676686%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-676686%22%20slang%3D%22en-US%22%3EWe%20have%20created%20a%20call%20queue%20and%20tested%20by%20calling%20the%20SIP%20URI%20and%20its%20working%2C%20which%20is%20routing%20to%20the%20user%20configure%20on%20it.%3CBR%20%2F%3EWhen%20we%20created%20an%20AA%20and%20associate%20the%20Call%20queue%20to%20it%2C%20while%20calling%20from%20SFB%20via%20SIP%20URI%20of%20AA%2C%20calls%20show%20transfering%20to%20Call%20queue%20however%20it%20doesnt%20reach%20the%20user.%3CBR%20%2F%3EHave%20anyone%20encounter%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-743086%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-743086%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F248051%22%20target%3D%22_blank%22%3E%40fowler_23%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20seeing%20the%20same%20issue%20when%20using%20on%20premises%20numbers%20for%20Direct%20Routing%20in%20a%20call%20queue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-744191%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-744191%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Ben%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECall%20is%20currently%20with%20Microsoft%20for%20investigation.%20Awaiting%20their%20feedback.%20It%20has%20been%20with%20them%20for%20a%20while.%20They%20are%20suggesting%20the%20issue%20is%20within%20their%20control.%3C%2FP%3E%3CP%3EWill%20update%20back%20here%20when%20I%20hear%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-769055%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-769055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Ben%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20Session%20Border%20Controller%20are%20you%20using%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-769361%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-769361%22%20slang%3D%22en-US%22%3EAudioCodes%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-770480%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-770480%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOK%20-%20just%20checking%20to%20see%20if%20was%20Ribbon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20just%20downloaded%20the%20latest%20firmware%20which%20looks%20to%20have%20resolved%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824549%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824549%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20may%20be%20aware%20but%20Audiocodes%20have%20just%20released%20a%20new%20software%20update%20which%20looks%20to%20have%20a%20lot%20of%20improvements%5Cfixes%20for%20Teams%20related%20voice%20issues.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EMaybe%20get%20it%20installed%20and%20see%20if%20it%20fixes%20the%20issue%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERelease%20is%20Software%20Update%20Version%207.20A.254%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-828888%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20-%20call%20queue%20-%20number%20from%20direct%20routing%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828888%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F248051%22%20target%3D%22_blank%22%3E%40fowler_23%3C%2FA%3E%3CBR%20%2F%3EI%20opened%20a%20ticket%20with%20Microsoft%20and%20we%20found%20out%20it%20will%20not%20work%20with%20the%20Polycom%20VVX%20phones.%20Also%20the%20user%20that%20is%20part%20of%20the%20queue%20has%20to%20be%20in%20Teams%20Only%20mode%20and%20then%20it%20will%20work%20as%20well.%20We%20aren't%20quite%20ready%20to%20go%20to%20Teams%20Only%20mode%20so%20we%20aren't%20able%20to%20use%20this%20feature%20quite%20yet.%20We%20are%20still%20waiting%20on%20a%20few%20interop%20features%20to%20come%20through%20before%20switching%20our%20pilot%20team%20to%20full%20Teams%20Only.%3C%2FLINGO-BODY%3E
Highlighted
MVP

How to create Call queue for Microsoft Teams (or Skype for Business Online), when phone number (line number / caller ID) should be used from Direct Routing?

 

I do not see Powershell way, and I do have option just to purchase new numbers from Microsoft directly, but I want to use existing numbers (that can not be ported to Microsoft), and are in use through Microsoft Teams – direct routing.

 

Thank you,

Kind regards

30 Replies
Highlighted

Unfortunately, it’s not possible to use service numbers via Direct Routing. Let’s hope it will be possible in the future, because as you say it’s not always possible to port just your switchboard number, for example.

 

In the meanwhile, do a static call forward of your switchboard number to the service number acquired from Office 365, that should work.

 

Regards,

Marten

Highlighted

Are you sure? Where is documentation? If so, I can not find feature request on ideas site...

Highlighted

I just hope, because the way it is now with the service number in Office 365, it simply doesn’t work when using Direct Routing or CCE. Rebellions are built on hope, remember. :smiling_face_with_smiling_eyes: If it’s not on User Voice then you should put it there, I’ll vote for it.

Highlighted
Best Response confirmed by Hrvoje Kusulja (MVP)
Solution

Yeah, so this is probably not supported, since others are asking the same...

Ref: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/35022145-allow-service-numbers...

Highlighted

There you go, just like I told you. :thumbs_up:

Highlighted

Hi guys,

Actually it is possible and works pretty well.

What you have to do is to get a service number from Microsoft and then create a call queue or auto attendant on Legacy SfB Portal using this service number.

After that, always that your gateway/sbc receives a call on the extension number (private number) that you want to use for the CQ/AA you send the call to MS Teams throught Direct Routing using as destination number, the number of the service number that you are using.

For instance, if someone dials 9999 internally, you must forward this call to +12122345678 (Microsoft's service number that you got).

As we are talking about Teams, it is important that all of the users on call queue (group) were already configured to use Teams as their native client.

I hope it helps!

Highlighted

Yeah, but we are talking about getting from on-prem through SIP trunk - my existing service numbers, to the Teams.., not buying them from Microsoft.

Highlighted

No. You won't use the Microsoft's service number to nothing but just routing the calls internally using your SIP Trunk.

You could forward one of your DIDs to the service number, as example.

The difference is that it is not possible to configure your own DID directly on the call queue, so, you create a "transformation" on the destination number.

Always that someone dials your DID, you send the call to Microsoft's service number of your call queue.

Highlighted

So basically, you have to pay to Microsoft for a number and for voice minutes, and can not use your on-prem numbers, ISP and pricing.

That is something that we wait to support direct SIP Trunk for existing service numbers, etc., not doing forwarding/transformation ....

Highlighted

Actually, you can use on-premises PSTN numbers with call queue. The trick is to convert the destination number to AA\CQ SIP URI Guid. There's no service numbers involved in this setup. I have done this for all of the Direct Routing deployments so far and works well too. I've written a blog about it. Have a look and see if that works for you

 

https://thamaraw.com/2018/09/10/using-on-premises-pstn-numbers-for-call-queues-and-auto-attendant-fo...

Highlighted
Not sure if this will be relevant at this stage but we have built a Microsoft-certified Cloud Connector that delivers voice services for Teams calling directly to the O365 Tenant. Our geo-redundant solution also completes the missing PBX and legacy feature-set, provides full integration capabilities to Call/Contact Centers and CRMs and handles extension dialing, DID /TF number porting, as we are a Tier1 Cloud UC carrier. Our cloud dial-plan allows for legacy PBX or Skype4B to Teams extension dialing during migration as well.
Highlighted

The blog article states "**This article does not applies to Direct Routing with Microsoft Teams."

 

Do you have this working with Direct Routing/Teams?

Highlighted

Hi,

 

It seems that this is on the Microsoft road map..

 

Please see here

 

https://skypeandteams.blob.core.windows.net/artefacts/Skype%20for%20Business%20to%20Teams%20Capabili...

 

https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=Microsoft%20Teams

 

Check out the “Call Queues” Roadmap on the second URL

 

Microsoft Teams - Call Queues
Phase 1 of Call Queues is now available for Teams. The work primarily focused on enabling the same set of features previously available to Skype for Business Online. Additional work is ongoing for support for phone number usage via Direct Routing and is expected next quarter.
More info
• Featured ID: 24174
• Added to Roadmap: 10/24/2017
• Last Modified: 1/29/2019
• Tags: Microsoft Teams

Highlighted

Yeah, it is funny, it is marked as "Launched" , but with note, that this important part will be in next quarter.

It will be much better if they communicate this feature as a separate entry in roadmap with current status..

Highlighted
I would like to know more about how to set this up. We tried following your guide and could not get it working.
Highlighted

@Sascha Stops mentioned in this thread, that the documentation to this feature is now online:

https://docs.microsoft.com/en-us/MicrosoftTeams/manage-resource-accounts

 

But in our case the feature is not available yet in Teams Admin Center, we don't have the option "Resource Account" under "Org-wide settings". Can anyone confirm this?

Highlighted

@sasfbr You should see it now, it's supposed to be GA, i'm seeing it in both tenants i have.

Highlighted

I do confirm this is resolved and now working.

EU tenants, first release features.

 

Go to https://admin.teams.microsoft.com

1) Create resource account

2) Create auto-attendant or call queue, connect with resource account

 

Connect with powershell and:

3) assign phone number from on-premise / direct routing through cmdlet to resource account

I do confirm this is resolved and now working.
EU tenants, first release features.

Go to https://admin.teams.microsoft.com

1) Create resource account
2) Create auto-attendant or call queue, connect with resource account

Connect with powershell and:
3) assign phone number from on-premise / direct routing through cmdlet to resource account