MS Teams Direct Routing Redirection to Group

%3CLINGO-SUB%20id%3D%22lingo-sub-1823674%22%20slang%3D%22en-US%22%3EMS%20Teams%20Direct%20Routing%20Redirection%20to%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1823674%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20in%20the%20process%20of%20eliminating%20our%20on-premise%20SFB%20infrastructure.%26nbsp%3B%20All%20of%20our%20users%20are%20hosted%20in%20cloud%2C%20and%20we%20are%20implementing%20direct%20routing%20utilizing%20our%20Ribbon%20SBC%201000%20gateways.%26nbsp%3B%20For%20individual%20users%20receiving%20calls%20from%20PSTN%2C%20this%20is%20working%20great.%26nbsp%3B%20However%2C%20we%20do%20have%20some%20groups%20and%20auto-attendants%20that%20we%20previously%20utilized%20a%20combination%20of%20unassigned%20numbers%20and%20announcement%20forwards%20in%20Skype%20for%20Business%20server%20to%20redirect%20the%20calls%2C%20for%20example%20--%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPSTN%20users%20dials%20%2B6112345678%2C%20SBC%20routes%20those%20calls%20to%20legacy%20Skype%20FE%5CMediation%20pool%2C%20where%20there's%20an%20unassigned%20number%20rule%20that%20catches%20that%20call%20and%20forwards%20it%20out%20to%20sip%3Ahg_78924kja25jkldjf%40mydomain.com.%26nbsp%3B%20The%20PSTN%20caller%20is%20connected%20to%20the%20Teams%20hunt%20group%20or%20auto%20attendant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EI'm%20attempting%20to%20move%20this%20logic%20to%20the%20SBC%20utilizing%20a%20transformation%20table%20that%20catches%20a%20call%20to%20the%20above%20number%2C%20and%20transforms%20the%20called%20number%20field%20to%20hg_78924kja25jkldjf%40mydomain.com%20%26nbsp%3Band%20routes%20to%20my%20teams%20direct%20routing%20signaling%20group.%26nbsp%3B%20It%20does%20that...but%20the%20call%20fails%20after%20ring%20back%20with%20a%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E480%20Temporarily%20Unavailable%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EREASON%3A%20Q.850%3Bcause%3D31%3Btext%3D%221e181a52-7748-4192-9023-0e888d6d26b7%3BNo%20callee%20endpoints%20were%20found.%22%3CBR%20%2F%3ERECORD-ROUTE%3A%20%26lt%3B5061%26gt%3B%3CBR%20%2F%3ECONTACT%3A%20%26lt%3B443%26gt%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EAny%20idea%20what%20I'm%20doing%20wrong%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1823674%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETranslation%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1841683%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20Redirection%20to%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1841683%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20updating%20both%20the%20To%3A%20and%20INVITE%3A%20messages%3F%20Do%20you%20have%20a%20full%20trace%20that%20shows%20the%20respective%20changes%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi there,

 

We are in the process of eliminating our on-premise SFB infrastructure.  All of our users are hosted in cloud, and we are implementing direct routing utilizing our Ribbon SBC 1000 gateways.  For individual users receiving calls from PSTN, this is working great.  However, we do have some groups and auto-attendants that we previously utilized a combination of unassigned numbers and announcement forwards in Skype for Business server to redirect the calls, for example -- 

 

PSTN users dials +6112345678, SBC routes those calls to legacy Skype FE\Mediation pool, where there's an unassigned number rule that catches that call and forwards it out to sip:hg_78924kja25jkldjf@mydomain.com.  The PSTN caller is connected to the Teams hunt group or auto attendant.

 

I'm attempting to move this logic to the SBC utilizing a transformation table that catches a call to the above number, and transforms the called number field to hg_78924kja25jkldjf@mydomain.com  and routes to my teams direct routing signaling group.  It does that...but the call fails after ring back with a 

480 Temporarily Unavailable

REASON: Q.850;cause=31;text="1e181a52-7748-4192-9023-0e888d6d26b7;No callee endpoints were found."
RECORD-ROUTE: <sip:sip-du-a-as.pstnhub.microsoft.com:5061;transport=tls;lr>
CONTACT: <sip:api-du-c-asse.pstnhub.microsoft.com:443;x-i=1e181a52-7748-4192-9023-0e888d6d26b7;x-c=8a3f01cd4cec5114ae08f03756130df1

 

Any idea what I'm doing wrong?  

2 Replies
Highlighted

Are you updating both the To: and INVITE: messages? Do you have a full trace that shows the respective changes?

Highlighted

@James_Nelson Hi James,

 

"I'm attempting to move this logic to the SBC utilizing a transformation table that catches a call to the above number, and transforms the called number field to hg_78924kja25jkldjf@mydomain.com  and routes to my teams direct routing signaling group.  It does that...but the call fails"

 

You say users call +6112345678, so on the SBC using the transformation table, manipulate the called number +6112345678. Change it to the PSTN number of the Teams AA\CQ and then send onto the Teams Signalling Group. Called Number will then match in your tenant and callers will go to the AA\CQ.

 

That should do it for you. There's no need to transform it to the hg_xxx format.

 

Unless I'm missing something??

 

Regards