One thing I noticed is that when setting up voicemail in Teams, if you set up an autoattendant to transfer directly to an individual, there’s no “ringing” tone. One would expect this to just be a standard thing when transferring anywhere, so how can we fix it?
Its really hard to tell if this is by design, or an overlook by Microsoft. My take is that once the SBC transfers the call into the Teams ecosystem, it should be handled 100% by the Teams ecosystem, but apparently this isn’t always the case, as there really is no option to pick a ring tone or music-on-hold when transferring between entities.
So what do we do? Well we have the SBC in the mix, and if we take a peak at a call trace, we do see that Teams tells the SBC the call is “progressing”…
Since the SBC is being told something is going on via the “183 Session Progress”, we can enable the ringtone. In my case, using AnyNode, this has to be enabled not on the Teams node, but on the node (or any node) the caller is calling FROM, in this case the node the SIP trunk is calling in on. The following image highlights the settings I enabled in AnyNode, your SBC may be different:
Note that I’m not 100% sure if the “ringback” setting is needed, some more experimentation will answer that, but for now, enabling tones and announcements, and (at least for me) picking the US tone group enables the US ringback tone. You would obviously want to pick your country’s native tones if not US.
Doing this enabled the ringing tone for the caller. If you have other nodes that are calling INTO Teams, you may want to enable this for those nodes as well.
Chances are all Teams Direct Routing SBCs, like Ribbon and AudioCodes also provides these features. It stinks that we have to fiddling with such things for basic functionality, but it is what it is for now.