Jul 05 2022
TLS 1.2 between Cisco CUBE and MS Direct Routing TLS connectivity status Inactive
kindly I have made all steps below and still facing the TlS connectivity status Inactive.
1-Created a CSR from CUBE and signed it from GoDaddy public SSL certificate then imported the signed again.
2-Created a Public DNS pointing to the FQDN of the Cube which is NATed to the private IP of the cube.
3-opened all needed Ports even opened the whole ports still facing the same error.
4-made the whole dial peers that is needed.
Please check the below screen shoot
Jul 10 2022
@Ibrahimooooooov on the Cube, did you imported the Baltimore CA as well? Can be that the Cube is closing the connection as the Baltimore CA (that is Neede to validate certificate from M365) isn’t installed on the Cube?
let me know