Hi,
I have a customer who is developing a login/logout applicaton for their SSIP 5k & 7k. Now they have the following issues/questions:
- They managed to get phone to successfully browse a page using IIS anonymous access, but the doc implied that it would use digest authentication for HTTP GET requests - what is going on?
- Why is the model number in the HTTP header SSIP_5000 when the model number returned by the API is SSIP5000?(I thought the values would be identical)
- Will the MAC address/Serial Number returned in the HTTP header always be fixed at 12 characters long and prefixed by SN:?
Scenario
They are trying to browse to an SSL-protected site from the SSIP 5000 phone’s microbrowser.
What they have done
They followed the instructions contained within that certificates bulletin (17877) and created a self-signed CA certificate. They then installed it to the phone’s CA list as described and that worked successfully. They created a pfx from the certificate so that they could install in IIS and SSL-enable the website.
What Happens
When they browse to the site using Internet Explorer and the site displays correctly with no errors or warnings.
When they browse to the site using the phone microbrowser they get a browser error:
SSL certificate problem, verify that the CA cert is ok.
Details: error 14090086:SSL routines
SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
A trace in Wireshark shows the client and server hello succeed, then comes the TLS fatal alert with bad Certificate as the description.
So it looks as though my CA certificate is wrong somehow even though the same process works fine with a different browser.
Are there any known issues using a custom certificate installed to the phone’s CA list from the microbrowser?
Thanks in advance
