Message-ID: <242781847.10343.1711629255995.JavaMail.confluence1@kb0.noctel.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10342_1118913962.1711629255945" ------=_Part_10342_1118913962.1711629255945 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you have more than a couple of handsets in your infrastructur= e, it might make sense to cache Polycom firmware updates locally in order t= o save Internet bandwidth. When a new firmware is available, your pho= nes will download it automatically from the http://firmware.noctel.com serv= er. If there are hundreds or thousands of phones on your network, thi= s can be a bandwidth intensive process, so it is suggested to cache the fil= es.
Follow these steps to cache these firmware files with a Linux server and= your DNS server.
<IfModule mod_disk_cache.c>
Cach= eRoot /var/www/cache/
CacheEnable disk /
Ca= cheDirLevels 5
CacheDirLength 3
CacheMaxExp= ire 86400
ProxyRequests On
ProxyVia On
ProxyPass /polycom http://noctel.com/polycom/
</IfModule>
<VirtualHost *:80>DocumentRoot /var/www/html/ServerName noctel= -local-cacheErrorLog logs/noctel-error_log = ;CustomLog logs/noctel-access_log common</VirtualHost>
The first time that a phone requests a firmware file from the NocTel ser= ver, the apache web server will cache the request for a period of up to one= day.
You can confirm that this cache is working once the first request has be= en made. The directory structure under /var/www/html/ will contain th= e firmware that is being cached.