09-17-2018 07:51 AM
09-17-2018 07:51 AM
Been experementing with Call Queues, has anyone any issues where Call Queues not rings in the Teams client but in the SfB client only?
If i call directly on my number as a test it comes directly into Teams but when called to a que nothing appears in Teams.
But as soon as i open the SfB client the calls gets acknowledge from the que directly.
09-17-2018 08:18 AM
09-17-2018 08:35 AM
09-17-2018 08:48 AMSolution
09-18-2018 09:54 AM
Call Queues on Teams is now in GA ??? Is that correct ?? Also is this working with direct routing ? as there were some reports of service numbers not working on DR.
@Christopher Webb wrote:
Ok, I just tested mine, and the queue comes right up in Teams no issues. I used to experience what you have before, but again this was before I switched to Teams only.
You can set just one user to Teams only if you want to give this a try vs. the whole tenant. I have how you can do so if you don't have the option on the user on the admin center to change it you can switch it via powershell.
09-18-2018 10:22 AM
09-18-2018 11:41 AM
Thanks, that's great to hear that it is finally on roll out. I don't think it has hit my tenant yet. Also can you tell me, if you click a phone number on a webpage, and you are set up for Teams only, does it behave as you would expect and make the call from Teams ? I know that there were some issues with that. More specifically, I want to use Teams to make calls from Dynamics 365 CRM records. The October release of D 365 is going to bring some further integration between D 365 and Teams and having it boot you out from Teams to make the outbound PSTN call using SfB when you click on the number within Teams is just weird - but that is what mine does right now. I am hoping that is going to change very soon.
09-18-2018 01:42 PM
09-19-2018 01:08 AM
Thanks that is as I thought. Hopefully they will have some news about that at Ignite, because right now it is a bizarre omission from the solution given the announced Dynamics 365 integration. Maybe it will come with the October release of Windows 10 as that would be an obvious point if there was any pre-requisite that needed to be implemented on the OS side. It needs to "just work"...
09-19-2018 01:55 AM
Regarding the question for Direct Routing and Call Queues -- Service numbers can currently not be provided via Direct Routing, but you can vote on the feature here: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/35022145-allow-service-numbers...
12-04-2018 12:30 PM - last edited on 12-05-2018 10:17 AM by Eric Starker
Not sure if it's relevant to this post but in order for us to resolve S4B & Teams call feature issues for our clients, we worked extensively with MS for over a year to build a MS-certified Connector that addresses issues and missing legacy PBX features that businesses still need and MS does not see the need to develop. Legacy features such as analog, faxing, ACD Agent log-in/out, true enterprise extension dialing, external paging, etc. are still being used by many businesses.
I also have a question and would like to know what challenges (if any) have anyone faced when attempting to utilize MS Teams as a full-functioning legacy PBX phone system or UCaaS replacement? Why aren't more companies using MS Teams as a phone system since it is free and included in the E5/M5 license pack? The alternative Cap-Ex cost of a premises-based IP phone system is at least $300-$500/user (100 user company: $30k-$50K just for the phone system alone) plus Telco lines and phone service costs. With Teams Calling, if you have E5, phone system is included and you just need a MS or 3rd party calling plan for $10-$24/user. Why isn't this being adopted more?