FreePBX Provisioning server (port 84) not serving all files

freepbx
Tags: #<Tag:0x00007f702abcb438>

(Alkaceq) #1

Hello, I’m having bit of an issue with FreePBX (Version: FreePBX 15.0.16.77) provisioning server (default port 84), it is not serving all the files properly

I intend to upgrade Avaya phones 9611 (those are working and with FreePBX ok), so I provide firmware files .bin and .txt files in FreePBXes /tftpboot and enable provisioning server in Server Admin on port 84. Avaya phone checks that webserver upon boot to see what firmware it should download by downloading 96x1Supgrade.txt and get the .bin file in next step.

The problem is in accessing the files via HTTP, as not all HTTP requests are served. For example:

  • If the phone asks for 96x1Supgrade.txt during its bootup sequence it gets 404 not found returned, but next boot it is 200 (while nothing changes)
  • If a PC browser asks for those files, it gets the file (200 OK) , every time.
  • With .bin file,phone always gest 404 not found, but PC will get the file every time.
  • Even when trying to curl pretending to be a phone by spoofing user agent string, I get it over the browser every time, but phones wont get it. (curl -A "AVAYA/SPICE/v6.6+(9611)/Std/02" hhhh://xx.xx.xx.xx:84/S9608_11_SALKRR7_0_1_4r6.bin -O )

96x1Supgrade.txt content
SET APPNAME S9608_11_SALKRR7_0_1_4r6.bin

I see in access /var/logs/https/access.log

.150 phone
.101 pc

xx.x.xx.150 - - [04/Nov/2020:16:32:59 +0000] "GET /S9608_11_SALKRR7_0_1_4r6.bin HTTP/1.1" 404 226 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7d)"

xx.x.xx.150 - - [04/Nov/2020:16:34:12 +0000] "GET /logo.jpg HTTP/1.1" 200 3004 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7)"

xx.x.xx.101 - - [04/Nov/2020:16:37:18 +0000] "GET /96x1Supgrade.txt HTTP/1.1" 200 941 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36"

xx.x.xx.101 - - [04/Nov/2020:16:37:51 +0000] "GET /S96x1_SALBR7_0_1_4r6_V4r83.tar HTTP/1.1" 200 4700160 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36"

xx.x.xx.150 - - [04/Nov/2020:16:42:06 +0000] "GET /96x1Supgrade.txt HTTP/1.1" 404 214 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7d)"

xx.x.xx.150 - - [04/Nov/2020:16:42:17 +0000] "GET /logo.jpg HTTP/1.1" 200 3004 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7d8)"

xx.x.xx.150 - - [04/Nov/2020:16:48:35 +0000] "GET /96x1Supgrade.txt HTTP/1.1" 404 214 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea)"

xx.x.xx.150 - - [04/Nov/2020:16:48:45 +0000] "GET /logo.jpg HTTP/1.1" 200 3004 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7d89bc)"

xx.x.xx.101 - - [04/Nov/2020:16:49:19 +0000] "GET /96x1Supgrade.txt HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36"

xx.x.xx.150 - - [04/Nov/2020:16:52:56 +0000] "GET /96x1Supgrade.txt HTTP/1.1" 200 941 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7d)"

xx.x.xx.150 - - [04/Nov/2020:16:52:56 +0000] "GET /46xxsettings.txt HTTP/1.1" 200 808 "-" "Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/9611-7.1.10.0.6 (MAC:c81fea7d)"

the /ftpboot looks like this:

user@freepbx tftpboot]# ls -la
total 103320
drwxr-xr-x. 9 asterisk asterisk 4096 Nov 5 15:29 .
dr-xr-xr-x. 18 root root 240 Sep 20 14:55 …
-rw-r–r-- 1 asterisk asterisk 808 Nov 4 15:22 46xxsettings.txt
-rw-r–r-- 1 asterisk asterisk 31 Sep 4 09:20 96x1Supgrade_simple.txt
-rw-r–r-- 1 asterisk asterisk 941 Feb 9 2017 96x1Supgrade.txt
drwxr-xr-x 3 asterisk asterisk 15 Sep 26 09:05 digium
drwxr-xr-x 2 asterisk asterisk 6 Nov 5 14:33 firmwaredownloads
drwxr-xr-x 4 asterisk asterisk 40 Sep 26 09:05 images
-rw-r–r-- 1 asterisk asterisk 15226 Feb 9 2017 release.xml
drwxr-xr-x 4 asterisk asterisk 40 Sep 26 09:05 ringtones
-rw-r–r-- 1 asterisk asterisk 49987088 Feb 9 2017 S9608_11_SALKRR7_0_1_4r6.bin
-rw-r–r-- 1 asterisk asterisk 27883520 Feb 9 2017 S96x1_SALBR7_0_1_4r6_V4r83.orig.tar
-rw-r–r-- 1 asterisk asterisk 4700160 Feb 9 2017 S96x1_SALBR7_0_1_4r6_V4r83.tar
-rw-r–r-- 1 asterisk asterisk 23029760 Feb 9 2017 S96x1_UKR_V37r3509_V37r3509.tar
drwxr-xr-x 3 asterisk asterisk 15 Sep 26 09:06 sangoma
drwxr-xr-x 2 asterisk asterisk 4096 Nov 5 15:28 signatures
drwxr-xr-x 3 asterisk asterisk 22 Nov 4 14:17 vega

Is there a setting of the httpd preventing some files to be served? There is no firewall, no difference network-wise. What Am I overlooking? Is the provisioning server designed to do this or shall I bring up simple ngix to serve bin files.
Any suggestions would help, cheers. A.