I am not entirely sure when this started occurring (currently running v18.0.4.965), but my Avaya 96xx phone rebooted the other day, and it wouldn't provision itself (it just said "no call server address").
After doing a tcpdump to watch the DHCP + HTTP provisioner traffic from my phone to my 3CX PBX, I noticed the phone is getting an invalid response from the server:
I can easily reproduce this by sending a CURL with the same User-Agent string the phone is using to the 3CX PBX web server:
To alleviate this, I think it might be good to adjust the NGINX rules to something like this (which will disable the out-dated browser check for /provisioning, but leaves it in place for the rest of the UI):
Of course, I made this change locally (and there's probably a much better way to do this--I just needed a quick fix to get my phones provisioning again), but it will only last until the next time 3CX is updated
.
Thanks for such a great product, I've been using 3CX for YEARS, and this is the first (minor) issue I've run into--keep up the good work!
After doing a tcpdump to watch the DHCP + HTTP provisioner traffic from my phone to my 3CX PBX, I noticed the phone is getting an invalid response from the server:
I can easily reproduce this by sending a CURL with the same User-Agent string the phone is using to the 3CX PBX web server:
Code:
curl -i --http1.1 http://172.16.254.200/provisioning/xxxxxxxxxxxx/96xxupgrade.txt -H 'User-Agent: Mozilla/4.0 (compatible; MSIE 6.0)'
HTTP/1.1 200 OK
Server: nginx
Date: Sun, 21 Aug 2022 20:38:00 GMT
Content-Type: application/octet-stream
Content-Length: 228
Connection: keep-alive
Content-Type: text/html
<html><body><h1>Unfortunately, you are using an outdated and unsupported browser.<br>Please upgrade your browser to improve your experience and security.<br>Supported browsers: Chrome, Edge, Safari or Firefox.</h1></body></html>To alleviate this, I think it might be good to adjust the NGINX rules to something like this (which will disable the out-dated browser check for /provisioning, but leaves it in place for the rest of the UI):
Code:
# /var/lib/3cxpbx/Bin/nginx/conf/snippets/40-common.conf
#
# After this stanza:
if ($http_user_agent ~ "MSIE|Trident" ) {
set $test "outdated";
}
# Add this:
if ($request_uri ~ ^/provisioning) {
set $test "provisioning";
}
# So this check statement will never be reached when anything under /provisioning/... is requested
if ($test = "outdated") {
rewrite ^ /outdated break;
}Of course, I made this change locally (and there's probably a much better way to do this--I just needed a quick fix to get my phones provisioning again), but it will only last until the next time 3CX is updated
.Thanks for such a great product, I've been using 3CX for YEARS, and this is the first (minor) issue I've run into--keep up the good work!
Last edited by a moderator:
