08-24-2020 08:16 AM - edited 08-24-2020 08:18 AM
Hi, we'tring to testing the direct routing offered from MS Teams using a Cisco ISR 4321. We've followed this guide:
The unique difference is that we haven't user the procedure of requesting a new certificate through thc CSR but we've imported a third party wildcard certificate.
The problem is that the Cisco router and MS teams don't communicate at all (TLS and SIP are inactive). We've already checked the licensing, the certificate validity, the domain and so on.
Someone have already done a succesful intergation between Cisco ISR and Teams Direct routing that can help us.
I can provide the router configuration and logs and also the pcap traces.
Thanks for help
Alberto.
09-25-2020 02:42 AM
Hi Alberto,
Please try to change the revocation-cehck for Baltimore trustpoint to none
crypto pki trustpoint baltimore
enrollment terminal
revocation-check none
Regards,
Ibrahima
09-25-2020 03:27 AM
Hi Ibrahima, thanks for your reply. I've already solved the problem that was the certificate upload.
We modified the key encryption, add a protection passoword on that and re-uploaded the certificate using this command:
crypto pki import XXX pem terminal password
After that the SBC is registered correctly.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide