So far it seems to me that the TLS closures are mainly a cosmetic issue (though that is still to be confirmed). I experienced some mid-call issues in the past, but got them solved by adding the two rules below to the tenant’s outbound sip-profile 200...

As to my understanding, we need to distinguish between two things: flapping dial-peer status and TLS remote closures Flapping dial-peer status- Caused by bug CSCwd33038, to be fixed by IOS update TLS closures- Caused by Microsoft's DNS load balancing...

Thank you, Greg, for your suggested solution. It looks like we will have to go down that road to make Cisco and Microsoft talk to each other.To support us in doing so, could you please let us know why exactly Microsoft considers a TCP connection as i...

Hello Greg,thank you for your valuable input an your informative link. Do I understand you correctly that the observed TLS closures take place because Microsoft does not regard CUBE's sip-options keepalive messages to reset its TLS timers and because...

Excellent hint, Louie. I can confirm that disabling click2x solved the problem in my case where a conflict between J4W and Estos ProCall caused the error message. To do so, I manually reinstalled the Jabber client through CMD, disabling click2x in th...