I have found a few work arounds. Host the files on a server listening on port 80. If I host from the Avaya CM server the phones seem to be unable to download the 46xxsettings.txt file so they do not attempt to download from the Avaya server on port 81 (per the documentation). This doesn't happen on all servers but it does happen on most of ours. It appears to be a bug that AVAYA is working on. No ETA though.
It worked fine for me... Did you ever get it working? Are you running through a firewall? If you are that may be the problem. I have seen this before. What version of firmware were you running before? In firmware version 1.5 Avaya enhanced the registration sequence. Some firewalls block the registration on the newer firmware versions. Let me know.
Comment removed
Callabahn 1 year ago
I have found a few work arounds. Host the files on a server listening on port 80. If I host from the Avaya CM server the phones seem to be unable to download the 46xxsettings.txt file so they do not attempt to download from the Avaya server on port 81 (per the documentation). This doesn't happen on all servers but it does happen on most of ours. It appears to be a bug that AVAYA is working on. No ETA though.
booyakafoo 3 years ago
It worked fine for me... Did you ever get it working? Are you running through a firewall? If you are that may be the problem. I have seen this before. What version of firmware were you running before? In firmware version 1.5 Avaya enhanced the registration sequence. Some firewalls block the registration on the newer firmware versions. Let me know.
Mike (Avaya Platinum Business Partner)
mikeb172sp 3 years ago