Forum Discussion
Teams Direct Routing Extension Transfer Failed
I get the idea how it works but I think it is more than that because I am also doing integration with IP/PBX system and call transfer works well to this system extensions.
Let's say I have 2XXX format for Teams extension and 3XXX for IP/PBX system extension. When I am transferring the call to IP/PBX extension, it is working well without problems but not for Teams extension. It always shown "couldn't reachable" message when failing.
One more thing, I also thought that when I transfer call to Teams extension, it automatically recognizes the extension and not forward to SBC.
Any idea? Thanks.
I was also living under impression that life could be easier with Transfer to Teams user 🙂 no way
Teams counts on fact that you wanna have in hands how the REFER message will be handled but they also count on that you will send them the REFER back to handle it properly. No matter if it is user or extension on your PBX it will simply all the time send the REFER to your Teams SBC.
I would recommend to setup on Teams SIP interface (IP Profile) to "handle locally" REFER messages and the same thing also to setup on PBX interface (IP profile). If you have setup already REFER rule in ip routing which should resend all REFER messages to Teams proxy then it should work as described earlier.I currently have such behavior:
Teams user transfer PSTN call to user -> SBC catch it -> send back the REFER to Teams -> Teams handle REFER inside
Teams user transfer PSTN call to PBX extension -> proper dial plan needs to be set to normalize number -> SBC catch it -> send back to Microsoft Teams proxy -> Proxy creates new invite and send it back to your SBC -> SBC handle it as new call to local PBX
Teams user transfer PSTN call to Teams user extension -> proper dial plan needs to be set to normalize number -> SBC catch it -> send back to Microsoft Teams proxy ->Teams handle it as number of Teams userAll is just based on current findings of my setup. One checkbox in different way and you can have different behavior. 😉
BTW. I am doing integration with CUCM and also with Openscape Voice in three regions differently. So no worries I have my headaches too 😄
HiDaveChomi ,
Since you mentioned working with CUCM, have you tried sending " Call naswered elsewhere" SIP message To / From CUCM & with Teams using SBC.
In Call Forking ( Ribbon Language) 🙂 and Remote Profile feature , parallel ringing is enabled, above will help to logs the calls as answered. If we answer in Teams, Cisco will log as answered call and vice versa. Have you came across this requirement.
Hi DaveChomi
Thanks! your explanation is great and also using AudioCodes language..hehe
I believe that I already put REFER rule in IP Routing correctly so it will be "handled locally" since it was written in manual guide. Let me do double check and re-test again to find out this further. I get the idea of REFER flow you explained.
Thanks again!
What is Line URI for users in Teams? is it just E.164 right?
Treat 2XXX and 3XXX as PBX extension and create dial plan normalization accordingly and send to SBC.
IF you set internal extension as false, then it will send to SBC as per route
If you want to transfer by Extension to Teams, you have to route the calls to SBC to process back with E164 Format as i mentioned earlier.
Check the pcap in SBC if you are sending to SBC for 2XXX
