Microsoft has recently released Teams calling functionality for list of legacy devices using SIP Gateway.
If you see, this is also a kind of calling inter-op service provided by Microsoft with few differences like the underlying call control infrastructure will be provided by Microsoft and the SIP devices wont register to their vendor specific call control servers.
Let's look into what this service offers!
What is SIP Gateway: SIP gateway is a service provided by Microsoft to enable a compatible SIP phones to be used as Teams calling devices just like a normal Teams Phone, though not all feature sets are enabled with SIP Gateway.
Benefits of using SIP Gateway: With hybrid workplace setup most Organizations have already moved or are moving to a soft client-based collaboration & calling devices. Orgs still migrating their enterprise voice calling to Microsoft Teams from Skype or any other on-prem based PBXs can use this service to retain their investments done on these compatible SIP hard phones and together with Microsoft Teams calling infrastructure(calling plans, direct routing) make the best use of these legacy hard phones.
Functionality supported by SIP Gateway:
Make/Receive Calls
Hold/Resume, Mute/Unmute
Call Transfer, local call forwarding
DTMF support
Do not disturb
Voicemail with Message waiting indicators
List of compatible legacy SIP phones:
SIP phones currently supported through this feature are Cisco 88XX,78XX,6821 with MPP firmware, Poly VVX series, Yealink T20,T30,T40,T50 series and Audio Codes 400 series
Complete list of can be found here
Requirement to use legacy SIP phones with SIP Gateway:
License for Phone system, this could be via E5 or standalone
PSTN number through Microsoft Calling Plans, Direct Routing or Operator Connect
Common Area Phone license for common area devices
Configuring SIP Gateway:
Pre-requisites: Along with the requirements stated above, there are few pre-requisites for SIP Gateway configuration
Open UDP ports 49152 to 53247, and TCP port 5061 for IP range 52.112.0.0/14 to 52.120.0.0/14
Allow network traffic to Microsoft 365 and Teams
SIP devices should not be behind a proxy
Reset SIP devices to factory default settings
Verify SIP Gateway is available for the Organization- Sign-in into Teams Admin Center, at the left, select Teams devices and see if the SIP devices tab is visible. If yes, then SIP Gateway service is enabled
Enable SIP Gateway for Users:
SIP Gateway can be enabled using Teams Admin Center or using PowerShell
Using Teams Admin Center: Under Calling Policies section, select the required policy, click edit and enable "SIP devices can be used for calls".
Using PowerShell: SIP Gateway can be enabled for Users by using Set-CsTeamsCallingPolicy cmdlet, select the appropriate policy and set -AllowSIPDevicesCalling attribute to True
Configure SIP Gateway Provisioning Server URL: The Provisioning server URLs can be either be configured manually or can be passed using DHCP options Three provisioning server URLs are shared by Microsoft that can be used:
コメント