EuropeSIP Posted May 30, 2022 Report Share Posted May 30, 2022 Hi, I read about the reference Microsoft. MC307310, that sip.all FQDNS are not supported from next June 1. (Other reference on the web: https://pupuweb.com/mc307310-sip-fqdns-will-not-supported-starting-march-1st-2022/) Will we need to change the IPs (for TEAMS) on our systems? How we do it? Best Regards Rafa Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 30, 2022 Report Share Posted May 30, 2022 I guess you mean https://docs.microsoft.com/en-us/microsoftteams/direct-routing-whats-new which seems to be more specific. We did not use the sip-all address (use sip.pstnhub.microsoft.com instead). So this should be no problem. And the Vodia PBX does not hardcode such addresses anyway, they are a part of the trunk setup. On a side note, the next version will also support subnet ranges, so that the inbound addresses don't have to be listed with each address. On a side note, the LetsEncrypt Root CA is now in the list of supported Root CA. This is excellent news because now there is no more need to pay for a certificate just to get the Microsoft SBC accept the connection. Quote Link to comment Share on other sites More sharing options...
EuropeSIP Posted May 30, 2022 Author Report Share Posted May 30, 2022 Hi, Thanks a lot for your answer. It was helpful to calm our customer. Best Regards Rafa Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.