Teams Phone: Communication Credits or full calling plan?
We are migrating 10 users away from our old VoIP provider and onto Teams Phone. Reviewing the call activity from our existing VoIP provider, these 10 lines only appear to use an average of 15 hours of calling total, across all the numbers, per month. 99% of all the calling is domestic (US/North America). Given this, does it make more sense to have each user get a Teams Phone Standard license, and a pool of Communications Credits that the Teams Phone users draw from, versus giving each user a full Teams Phone Plus Calling Plan license?
Help needed with Teams Licensing for VoIP and Dynamics CRM integration - Expert opinions welcome!
Hello everyone, I hope you are all doing well. I am new to Microsoft Teams and I am currently trying to configure Teams VoIP for my organization. Our goal is to integrate it with Dynamics CRM for insights. However, we are facing some confusion regarding Teams licensing, and we are not sure which one to go with. As a newbie to MS Teams, I would really appreciate it if any expert in this community could explain the Teams licensing in a short/brief manner. Specifically, I would like to know which license is suitable for Teams VoIP and Dynamics CRM integration. Your expert opinion would be highly valuable to me and my team. Thank you in advance for your help and support.
new Conversation Space: Direct Routing
There are thousands of IT specialist who are deploying Direct Routing option for Teams Calling plan, bring their own PSTN telephony providers, their company telephone numbers, into Teams. Could we have separate Conversation space for Teams Direct Routing to share the experience and get MS involved in the community?Media Optimization for Direct Routing: Failover of ProxySBC for PSTNGateway
We are currently building Direct Routing voice infra for MS Teams with Media Optimization and Always Bypass mode using Audiocodes SBCs. Aim is to have two centralized ProxySBCs, primary and standby, shared over many PSTNGateways. When we define PSTN Gateway and Virtual Network Topology in Teams we can only define a single ProxySBC parameter for each PSTNGateway: PS C:\> Set-CsOnlinePSTNGateway -Identity <Identity> -GatewaySiteID <site ID> -MediaBypass <true/false> -BypassMode <Always/OnlyForLocalUsers> -ProxySBC <proxy SBC FQDN or $null> We would like to define geographical failover strategy for Calls to use standby ProxySBC. Are you aware about any possible option to achieve automatic ProxySBC failover? Options that comes to my mind, we could: Duplicate PSTNGateways once with Primary ProxySBC and second with Standby ProxySBC and play with VoicePolicies, but that would involve 2 different FQDNs and 2 Certificates for 1 same thing. Do Manual failover to Standby ProxySBC with a script but that misses automation. Build HA Pair but that's not available in two geographical different locations in our environment. Any option I overlooked how Microsoft plan ProxySBC failover? Any comments greatly appreciated.
