Hi all, I've been looking into XX-5417 - use HTTP instead of TFTP to manage phones in support of remote workers.
Actually, I got sidetracked looking into HTTPS, Basic/Digest Authentication, default ports, and the state of CounterPath provisioning. Ultimately we do want phones to be authenticated and use HTTPS. But I'll keep those issues separate from this thread. So getting back to what was requested in XX-5417: Switch to HTTP for the phones that currently use TFTP, because the latter does not traverses NATs and firewalls. I looked into both LG-Nortel 68xx and Nortel IP 12x0. The bad news is that there are phone bugs/limitations that prevent this from working seamlessly. The good news is that the sipXecs basics are in place already. Yes, the tftproot contents are already available via HTTP on port 80. sipXecs will be ready to go with little or no modification, once the phone issues are sorted out. Here are the instructions and issues for each phone. 1. LG-Nortel 68xx - Navigate to the "Upgrade Configuration" screen in the Web GUI. - Select "HTTP/HTTPS" radio button. - Set "HTTP/HTTPS URL" to "http://<domain_or_IP>/phone/profile/tftproot" - Change "HTTP/HTTPS Port" from 443 to 80. - Click "Change", and then "Reboot" or send the profile from sipXconfig. The phone reboots and does an HTTP GET for its <MAC> configuration file as expected. But the phone then attempts to retrieve its Phonebook CSV and firmware files via TFTP, which of course will fail for the remote worker. So firmware updates and phonebook changes will not be delivered. Also the settings on the "Upgrade Configuration" screen are deleted. They would have to be reset manually after each reboot, or the remote worker phone will no longer pick up configuration changes. (See XTRN-563: HTTP/HTTPS Upgrade Configuration settings partially ignored, then deleted after reboot) 2. Nortel IP 12x0 - Navigate to the "Advanced' screen in the Web GUI. - Change the "Config Server Type" to "HTTP". - Ensure the "Config Server Address" is set to the domain or IP, same as for TFTP. - Leave "HTTP Proxy" main value blank, but set its "Port" to 80. (See XTRN-562) - Ensure the "Auto-config Profile" is set to "Profile-C", same as for TFTP. - Change "Auto-config Path" from "Nortel/config" to "phone/profile/tftproot/Nortel/config". - Click "Commit Changes". - Send the profile from sipXconfig. The phone reboots and does an HTTP GET for its SIP<MAC>.xml configuration file (which includes phonebook entries) as expected. But the phone does not attempt to retrieve its firmware files at all, so firmware updates will not be delivered. It's a known limitation, and already being investigated. (See XTRN-561: HTTP Config Server Type - phone skips firmware upgrade.) There is a minor TFTP firmware retrieval limitation, the files can only be retrieved from the root of the server. (The "Auto-config Path" applies to config, not firmware.) This would be a problem if carried over to HTTP, since the firmware files would be in "phone/profile/tftproot". It should be possible to solve with a small change apache config change, by mapping "phone/profile/tftproot" to the root. I'll keep XX-5417 open while we have phone issues, and possibly an apache config change outstanding. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
