- Joined
- Apr 3, 2017
- Messages
- 4
- Reaction score
- 2
Hi,
We recently started our Teams Direct Routing with 3cx as SBC. Everybody is very happy to use Teams for handling their calls. Only there is one issue
.
If we transfer a call (in Teams) to another Teams user. The transfer fails...
Apparently Teams Telephony System refers the call to the SBC rather than handling the call internally.
So the call flow is as follows:
Incoming call from SBC to MS Teams -> MS Teams user transfers the call to internal user -> Call fails as MS Teams generates a REFER back to the SBC rather than route the call internally to MS Teams user target. (I have attached the log files from 3cx, while attempting a transfer)
(see also: https://techcommunity.microsoft.com...ing-internal-call-transfer-failure/m-p/754902, from here I copied the line above and below
)
A workaround would be to disable REFER as an allowed method within the SBC's signaling messages, then MS Teams does not use REFER for transfers and just re-INVITEs to the SBC. That way the internal transfers work perfectly fine.
However in 3cx this is not an option (without some code hacking), since the Direct Routing Trunk is not visible in the admin console.
Does anybody have some idea how to approach this (or apply the workaround) within 3cx?
Vincent
We recently started our Teams Direct Routing with 3cx as SBC. Everybody is very happy to use Teams for handling their calls. Only there is one issue
If we transfer a call (in Teams) to another Teams user. The transfer fails...
Apparently Teams Telephony System refers the call to the SBC rather than handling the call internally.
So the call flow is as follows:
Incoming call from SBC to MS Teams -> MS Teams user transfers the call to internal user -> Call fails as MS Teams generates a REFER back to the SBC rather than route the call internally to MS Teams user target. (I have attached the log files from 3cx, while attempting a transfer)
(see also: https://techcommunity.microsoft.com...ing-internal-call-transfer-failure/m-p/754902, from here I copied the line above and below
A workaround would be to disable REFER as an allowed method within the SBC's signaling messages, then MS Teams does not use REFER for transfers and just re-INVITEs to the SBC. That way the internal transfers work perfectly fine.
However in 3cx this is not an option (without some code hacking), since the Direct Routing Trunk is not visible in the admin console.
Does anybody have some idea how to approach this (or apply the workaround) within 3cx?
Vincent