Microsoft released Skype for Business Server 2019, v7.0.2046.396
See description in KB4470124 and download from hereTuesday, April 19, 2022
Friday, February 11, 2022
Microsoft Skype for Business Server 2015: February 2022
Tuesday, December 21, 2021
MC307310 - sip-all FQDNs will not be supported starting March 1st, 2022
Microsoft Message Center
Message Summary
We're making some changes to Teams Direct Routing
On March 1, 2022, we will be removing support for sip-all.pstnhub.microsoft.com and sip-all.pstnhub.gov.teams.microsoft.us FQDNs from Direct Routing configuration.
Note: If you aren't using Session Border Controllers you can safely disregard this message.
How this will affect your organization:
When this change is implemented, if no actions taken and sip-all FQDN is used, users will no longer be able to make or receive calls via Direct Routing.
What you need to do to prepare:
Customers will need to use the recommended subnets (52.112.0.0/14 and 52.120.0.0/14) for any classification or ACL rules and discontinue using the sip-all FQDN when configuring Session Border Controls for the Direct Routing.
Learn more:
Tuesday, December 14, 2021
Microsoft Skype for Business Server 2019: December 2021
Friday, December 3, 2021
MC299922 - Direct Routing will stop processing SIP requests which have 'Replaces' headers
Microsoft Message Center
Message Summary
We'll be making some changes to Teams Direct Routing.
Note: Starting on January 3, 2022, Direct Routing will stop processing SIP requests which have Replaces headers.
When will this happen:
We will begin this change in early January '22 and expect to complete mid-January '22.
How this will affect your organization:
When this change is implemented, Direct Routing will reject SIP requests that have Replaces headers defined.
What you need to do to prepare:
Please check your Session Border Controller configuration and be sure that you are not using Replaces headers in SIP requests.
MC299923 - Trusted certificate authorities for Direct Routing SIP interface are changing
Microsoft Message Center
Message Summary
We're making some changes to the Direct Routing SIP interface.
Starting on February 1, 2022, the Direct Routing SIP interface will only trust certificates that are signed by Certificate Authorities (CAs) that are part of the Microsoft Trusted Root Certificate Program.
How this will affect your organization:
If your SBC certificate is not signed by a CA, you service may be impacted when this change takes effect. Unsupported certificates will not be accepted and you will lose PSTN connectivity via Direct Routing.
Note: Make sure that your SBC certificate is signed by a CA that is part of the program and that the Extended Key Usage (EKU) extension of your certificate includes Server Authentication.
Learn more: