Karl Stallknecht Posted February 3, 2016 Report Posted February 3, 2016 In the provisioner app, the top lists the provisioner URL but it is missing the "https:" - see screenshot:
Brian Sloan Posted February 15, 2016 Report Posted February 15, 2016 is https even working yet? we have had to use http.
Karl Stallknecht Posted February 15, 2016 Author Report Posted February 15, 2016 Really? We've been using https for provisioner the entire time with no problem...
Brian Sloan Posted February 15, 2016 Report Posted February 15, 2016 Interesting. I was told by 2600 support to not use https for now. Hopefully they will chime in here and let us know if it has been changed :)
Administrators Darren Schreiber Posted February 16, 2016 Administrators Report Posted February 16, 2016 Hi there, You're both right :-) https:// works fine. However, some phones (we're narrowing down which ones, but appears to be just Polycoms and only certain firmwares) don't appear to like that we use a wildcard cert (or something about our cert, but we're pretty sure it's because it's a wildcard). We're in the process of revising our cert so that it's a specific domain name to see if that resolves the issue. Either way, we'll continue to support both methods, so use whichever suits you.
Rick Guyton Posted February 16, 2016 Report Posted February 16, 2016 I don't think Yealinks will provision via HTTPS yet either. The only allow for certain CAs by default and Godaddy isn't one of them... GeoTrust is though... hint, hint... ;)
Brian Sloan Posted February 17, 2016 Report Posted February 17, 2016 I have mostly yealink deployed and I definitely remember having issues when trying to use HTTPS.
esoare Posted March 3, 2016 Report Posted March 3, 2016 Same here, using Yealinks...always had to use HTTP:// @ Karl Stallknecht I informed 2600hz that it was a "Typo" when it said https://! lol Rather than make a debate of which one to use , it shows neither http or https, therefore, you can use either one!! :D
Administrators Darren Schreiber Posted March 18, 2016 Administrators Report Posted March 18, 2016 I didn't fully answer this question but since I just saw a code commit for the fix to it, I'll come back here.The "Typo" is actually because:1) We originally hard-coded https://p3.zswitch.net2) Someone complained that wasn't white-labeled3) We changed it to try and dynamically generate and also show http:// or https:// depending on something (I forget) (which was kind of dumb)4) The branding is missing still so now the domain is just gone*sigh*We'll try again and get the UI updated to have the brand in there, but you'll need to explicitly set the brand in the branding app I think (or it uses your base domain, I don't remember exactly). I'll try to remember to update this once we roll the fix.
Recommended Posts