All MPP phones have a Cisco signed client certificate, but they might vary depending on firmware and/or hardware version. The quickest way of establishing which client certificate the phone is using, is to enable HTTPS and check what SSL certificate the phone is presenting.
Change the Web Server Port number (on this case we are using the default HTTPS 443 port) – Note: by changing the protocol to HTTPS, the phone will not change to port 443 automatically, you can to change it manually
If web access is not available for any reason, use openssl (s_client -connect) to connect to the phone in order to check the issuer of the phone certificate which will be a subordinate certificate which will correspond to an entry on the PKI site, and to also check the issuer of the subordiniate certificate, which will again be another Cisco certificate on the PKI site.
If the issuer of the subordinate certificate does not appear using the s_client command, then again use openssl (x509 -in [cert_name] -text -noout) to analyse the downloaded subordinate certificate in order to find out which root certificate issued the subordinate certificate. Again, the root certificate will correspond to an entry on the PKI site.
Hello Everyone, I have Question based on New Requirement Coming from my Customer Currently 1 User is Logging in to Phone with his Extension Mobility Profile - User also has SNR Enabled so His Cell Phone Rings Simultaneously with his IP Phone Rin...
Current Version 22.214.171.124429 Build 303429, issue has occurred on 1 version higher also. Issue is the green call button will stop working, when clicked it will not call, used for internal calls, works fine when used for external numbers.Restarting jab...
Hello All, I have a problem and have tried lots of config but not getting the call to show the internal number when forwarding out. The forum point in the right direction but when running the debug the local number is not sent thus getting a 'n...