Teams Direct Routing with Anywhere365 (Cloud V3)
Anywhere365 Dialogue Cloud customers that use Teams Direct Routing have a direct route that connects their Session Border Controller (SBC) with Microsoft Phone System.
The Anywhere365 Dialogue Cloud Contact Center enables users to make and receive calls within Microsoft Teams while providing the features of Anywhere365 such as: call recording, real-time translation, Interactive Voice Response, reporting feature, the use of wallboards and many more. When the UCC receives an inbound call, the session will be connected to an Agent that is available on Teams.
Best practice for unwanted scenarios resulting from call forward settings
There are some features that work differently (compared to our Skype for Business offering) because of Teams related settings. Because Teams Users can configure "call answering rules" for incoming calls to go straight to voicemail or a phone number, this can result in unwanted scenarios for Anywhere365 call flows.
It is possible to overrule/ignore the call forwarding settings configured by a Teams user. So, if an Agent has configured a call forward (e.g. to voicemail or any phone number) and does not accept the call within the configured timeout or declines an incoming call from the UCC, the customer will not be forwarded to the call forward destination configured by the Agent, instead the call is offered to the next available Agent.
Best practice: set the value for the Setting “DisableCallForwarding” to “true” so that the call forwarding settings for Contact Center Agents are not respected.
Please note that your SBC should respect the X-MS-RoutingPolicy SIP-header and forward this to MS Teams accordingly.
Did you find this page helpful?
Sorry about that
Why wasn't this helpful? (check all that apply)
Thank you for your feedback.
Thanks for taking the time to give us some feedback.