Solved 3CX Avaya provisioning

[Puddin]

I'm playing with a test 3cx PBX and have it mostly working; just trying to see if it will meet our needs. We have a bunch of Avaya 9611G phones that we want to reuse.
I have followed the directions on here: https://www.3cx.com/sip-phones/avaya-ip-phone-provisioning/
When the phone reboots and looking at the 242 option, it sees the server IP, port and directory but is looking for a file called '96x1Supgrade.txt' in the 'secure folder' but it does not exist even after I download the 'special firmware packages' per the document. Am I overlooking something? Ultimately it times out with a 404 error because the file does not exist on the linux box.

Thoughts/comments?

Thanks,
Ken

 

[cobaltit]

Never provisioned Avaya phones but looking at the directions you might have made a mistake unzipping the files. Make sure you extracted the contents into /provisioning/xxxxxxxxxx/ and not /provisioning/secure_folder . Also make sure the phones are either local to 3CX or connected via VPN. As soon as the slow download is done I will confirm if that file is in the ZIP file.

 

[cobaltit]

So I don't see that file in the ZIP but that might be something 3CX generates on the fly. I do see 96x1Supgrade.txt.sig and 96x1Supgrade.txt.sig.256 in a subfolder called 'signatures'.

Is this on v15.5 or v16? The guide is still marked as BETA and I don't know if anyone has done a fresh v16 install with Avaya phones at this point.

 

[Puddin]

Thanks for your responses.
I did extract the files into the /provisioning/xxxxxx folder. From everything I read the 'xxxxxx' folder was referred to as 'secure folder'. Maybe it was my bad interpretation of the doc's.

This is on 16.x. I suppose that could make a difference. Never thought about it auto-generating the file, but I suppose it could. I also saw the sig files you referred to; also thought it was strange that the file the phone is looking for is just not there. I assume the 'sig' is a signature file for file validation or similar, so how could it auto generate the upgrade file with an existing sig - but could I guess.

Perhaps I'll just have to reinstall with 15.x and try again to see if that makes any difference and not upgrade to 16 to see if I can get it working....or not.

Ken

 

[Puddin]

I also saw that in the linked instructions it referrs to provisioning the extension in avaya to where the extension and 'authentication' must match, but it seems in 16.x that it will no longer allow this as it requires to be more digits in authentication than what the extension is (4 digits). I'll reinstall 15.x and see where that takes me.

Ken

 

[AramS_3CX]

I also saw that in the linked instructions it referrs to provisioning the extension in avaya to where the extension and 'authentication' must match, but it seems in 16.x that it will no longer allow this as it requires to be more digits in authentication than what the extension is (4 digits). I'll reinstall 15.x and see where that takes me.

Ken

Hi Ken,

You don't need to add any templates in the folders. They are already in the build.
You just need to be sure that you are running the proper firmware version on your Avaya phones.

You are right, the provisioning config files would be generated "on fly".

Just be sure that your extension number and authentication ID are equal. The password need to be minimum 6 digits.

For example:
Extension number - 0001
Authentication ID - 0001
Password - 123456 (or more if you want)