On 8/9/2012 12:31 AM, Josh Patten wrote:
I've updated http://track.sipfoundry.org/browse/XX-5838 with a patch
that allows HTTPS provisioning. It should be noted that this does not
work unless you have a SSL cert that is verified by one of the major
cert providers like verisign, or you manually import the self-signed
CA from sipX on each polycom phone, or in the case of Bria, each
desktop machine's trusted certificate store.
Thanks Josh. Just a few questions:
In order to user HTTPS provisioning with authentication a phone will
need to be loaded with the (self-signed) Trusted CA certificate, and
be programmed with the Username and Password (PIN) for authentication.
Does each phone have a unique username and unique password?
The current TFTP and FTP access to phone profile will be maintained
for the time being. The new HTTPS docroot will use the same location
as the existing TFTP and FTP roots.
For most of my installs, sipx is behind a firewall. Is it possible to
specify the port somewhere. Many installs have only 1 public IP address
and host their own web services many of which use port already 443. You
can still use https but on a different port. The change in an Apache
config is trivial.
--
Regards
--------------------------------------
Gerald Drouillard
Technology Architect
Drouillard & Associates, Inc.
http://www.Drouillard.biz
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
