Music on Hold in Teams & 4 seconds until Hold is in place for caller
There was a time I found out during my tests of our Direct Routing implementation that Microsoft made its promises happened and Music On Hold started to work on regular PSTN calls to Teams users. It was a time when I got a report of the new "issue". Users complained it takes too long until the call is put on Hold after clicking on the button. I was just curious what happened because I remember from previous tests this was just matter of second but users reported 4 seconds. Hmmm.... Then I realized I can hear the music ... wohoooo ... So deeper deep dive showed that Microsoft is handling Hold and Music on Hold in very specific way. At least for me. If you click Hold in Teams during the PSTN call you are basically transferring the call to another Teams "user"/object which is playing music for you. You can even hear the very short ring! Very confusing for the caller on PSTN side but I believe it's about way how you want to handle the Ring message on your SBC at the end. Good reason I believe not to change that behavior because of other reasons. And that's also the explanation why it takes so long time! Imagine with Direct Routing following scenario (below is SIP trace for better understanding) 1/Teams proxy is sending REFER, if you have your SBC setup in proper and recommended way then 2/ SBC sends invite back to Teams Proxy, 3/ then you have Ringing in place, 4/ all the SDP exchange of media sources (we are also running Mediabypass so imagine all ICE lite story happening) and boom, 5/ your call is on hold aka transferred to something else than your Teams user. Obviously the other way around, I mean getting the call back from Hold, is somehow reverted process but without REFER. Teams proxy basically sends new INVITE but now with Teams users media sources. Also takes a while and some users might be confused that they did something wrong or call is gone?! So at the end it's not 4 seconds but slightly around 3 (users are exaggerating a bit, right) I believe that this way of handling MoH is also reason why it will take some time until Microsoft will provide also MoH for Transfer function in Teams. Now if you click transfer or consult transfer the Teams Proxy sends Invite with inactive media session so might be another confusion for PSTN caller that there is just silence. Looking forward for Microsoft delivering these features for 100% and even more I would be happy to provide our management their own company MoH (not only on queues or AA 😉 but for users) Hope this article helps some of you
Delay transferring out from auto attendant
We have been testing Teams with Direct Routing trunks provided by a carrier partner. All inbound and outbound calls direct to/from Teams users connect without issue. We are using the Teams apps on Windows and iOS - no deskphones are involved yet. I have a simple auto attendant set up which greets the caller with the text-to-speech feature, and then transfers to a queue. This queue plays the default music on hold while alerting queue members. The problem I have is that a caller will dial the number associated with the auto attendant, the call will be answered within a couple of seconds, and then immediately the greeting will be read out and the user will be transferred to the call queue. There is then a silent period of between 5-10 seconds before the music on hold for the queue is heard - this varies with each call, at the lower end it's an acceptable delay, but when it gets to 10s of silence it really isn't workable. If I set the routing on the call queue to put the caller back into the auto attendant after a wait period this happens without any silence - the maximum wait period for the queue is reached and the greeting is played as soon as the music on hold ends. I am not able to determine whether the delay is happening within the auto attendant as it just waits after playing the greeting, or whether it's an issue at the start of the call queue. I opened a support ticket and was told that this delay is expected behavior and it is designed that way - the problem is that it's long enough for people to abandon calls as they think there is a problem. The queue is in conference mode, but this isn't an issue with users answering calls from queues so I don't think that is relevant anyway. Is it true that this delay is expected behavior? Is it expected due to a technical limitation or is it really designed that way?
Teams dial pad missing due to RegistarPool Attribute
Not a question but thought this should share in the community with my blog post and recent finding. Most common issues after moving/migrating users to Teams from SfB were few, Teams license assigned or assigned license change not replicate on time or delay. License was Phone System since this was Direct Routing work. is enable for Enterprise voice. Whether the user assigned a Voice Routing Policy. Whether the user assigned a Teams Calling Policy. Registar Pool missing/ empty. I found this new experience and read full article - Teams dial pad missing due to Registar Pool Attribute I got help from my old friend (MS Premier support) to do the replication in Backend @Muninder PS Thanks Reach out to me on Madushka Dias (@madushka) / Twitter or https://www.linkedin.com/in/madushkadias/.Teams keeps sending INVITE to 5067
Hello everyone, The story is, I have an SBC that is shared between multiple tenants, using one base domain and different subdoms (as multi tenant should be). But, instead, I separated each tenant with different ports (for a reason). There is this one tenant that I assigned port 5069. Call inbound from PSTN to Teams works well, but when call outbound from this tenant, Teams keeps sending INVITE to SBC through 5067 instead 5069. Checked the PSTNGateway setting, the SignalingPort already set to 5069. Anyone experienced this before? Thank you in advance.Teams Direct Routing
Hi, Is it possible to create two Policies under direct routing and add 1 SBC in one policy and 1 in another, then assign 1policy to user abc and 1 policy to user xyz. Exmaple- Direct Routing - Voice Route Name - Test 1 (SBC - test1.abc.com) - Map this with user abc Direct Routing - Voice Route Name - Test 2 (SBC - test2.lab.abc.com( - Map this with user xyz
Consult then transfer can only chat in mobile app in direct routing
Hello, First of all, I appologize if this question been asked in other post. When doing transfer call from PSTN to another user using desktop app, the "Consult then transfer" works fine, even when transferring to external phone number (PSTN or mobile number). But when using Android mobile app, "Consult then transfer" can only using chat when the target is another MSTeams user (same domain/organization). There is no other options, it directly brings the chat. I still can do "Consult then transfer" using voice from mobile app when transferring external number (PSTN/mobile) although that's the only logical way since I cant do chat to transfer call to such target. Is this how it works/limitation when on mobile app? Thank you in advance.
