If you are able to receive calls on Teams but cannot complete or connect calls, there are several potential causes and resolutions to consider:
- Enterprise Voice Feature: Ensure that you are enabled for the Enterprise Voice feature. If you attempt to call someone and receive a message stating that the call cannot be completed, it may be because your account is not enabled for this feature. You should contact your IT administrator to verify that your account has the necessary permissions and licenses (E3 with Phone System or E5).
- Missing Dial Pad: If you notice that the dial pad is missing from the Calls tab in Teams, this indicates that your user account may not have the correct settings or license. You can check your account settings by using the Teams PowerShell cmdlet:
Make sure all required values are set correctly as described in the documentation for enabling users for Direct Routing, voice, and voicemail.Get-CsOnlineUser -Identity <UserIdParameter> | fl Identity,EnterpriseVoiceEnabled,HostedVoiceMail,OnPremLineURI - Online Voice Routing Policy (OVRP): Check if the number you are dialing matches any patterns in your Online Voice Routing Policy. If there are no matching patterns, the call will not connect. Ensure that:
- There is a pattern in the OVRP that matches the dialed number.
- The usage profile for the call matches the one set up for your account.
- The gateway specified for the SBC is enabled.
- Gateway Status: If the gateway used by Teams is disabled, it will prevent calls from being completed. You can check the gateway status by running the following PowerShell cmdlet:
Ensure that theGet-CsOnlinePSTNGateway | fl Identity,Fqdn,SipSignalingPort,MaxConcurrentSessions,EnabledEnabledparameter is set toTrue. If it is not, you can enable it using:Set-CsOnlinePSTNGateway -Identity "<GatewayIdentity>" -Enabled $true - Network Configuration: Sometimes, network devices such as firewalls may block SIP messages, which can prevent calls from connecting. Make sure that the SIP signaling IPs and FQDNs are allowed on all network devices that connect the SBC to the internet. You can find the required IP addresses listed in the documentation for SIP signaling.
If you have checked all of these areas and are still experiencing issues, it may be beneficial to reach out to your IT support team for further assistance.