Forum Discussion
MS Teams Direct Routing - Internal call transfer failure
No, not by rejecting the REFER with a response code. I basically did a message manipulation rule to re-build the Allow header for calls to MS Teams without including REFER. Which vendor are you using? If you have an AudioCodes as well, I can give you the rule syntax.
Hi, We are having a similar transfer issue and I see you have the Audiocodes syntax to remove this in the ALLOW header. Any chance you could send this across so I can try this?
'No, not by rejecting the REFER with a response code. I basically did a message manipulation rule to re-build the Allow header for calls to MS Teams without including REFER. Which vendor are you using? If you have an AudioCodes as well, I can give you the rule syntax.'
Cheers
Darren
Yes we basically got this working with a firmware update on the Audiocodes direct routing SBCs 🙂
Have you setup on the opposite trunk (IP Profile for provider SIP trunk or your internal PBX not Teams side) Handle Locally of the REFER messages?
This will do the same job basically and you do not need this special manipulation which I personally consider as too much because it does not give you any chance then manipulate REFER messages.
So for IP profile of the SIP trunk towards your provider/on-prem PBX
I would setup these parameters on Audiocodes SBC
Remote REFER Mode Handle Locally Remote Replaces Mode Handle Locally Play RBT To Transferee Yes Remote 3xx Mode Handle Locally
