Provisioning Problem

[user57659]

Hello!
I have ran out of ideas on where to look to try and fix this, so hence posing here to see if you can provide any help:

We have a self hosted 3CX instance that runs on its own V-LAN in front of it it has its own PFsense Firewall and all has been well. We are using some old unsupported phones and some custom templates to run them. but I don't think this is the issue.

When I try and provision a phone with the custom template and the Mac address, the phone is not picking up the template at all, but it is getting on the correct network as I can access its web interface fine. 3CX Logs this error as:
Provisioning file /provisioning/42/9c57ad3eb656.xml requested by 10.6.1.207 could not be generated
3CX Template Parser ID: 30040 05/01/2023 15:53:06

As a result I can't add any new phone to the network. I get the same if I try and add a supported phone. The instance we have is running on Debian and I have checked the provisioning folder and there seems to be firmware located where it should be.

Nothing has changed on the network, but I am not ruling out a network issue.

If I go in to the 3cx Interface and try and bring up the provisioning link ( which is a LAN address). it comes up with " page cannot be found "

The existing phones work as they should, but I am unable to add anything new.

Any help or advice would be greatly appreciated.

 

[user57659]

There is no option to save - only "OK"

 

[Guillaume Bourgeois]

There is no option to save - only "OK"

Ok = Save.

did you go back to see as requested? Is the MAC still present? Is the URL the same?

 

[user57659]

Yes, still the same after pressing OK.

 

[Csut12]

Seeing same behavior post V18 Update 6 - 3CX logs are spitting out dozens of:

Provisioning file /provisioning/[instanceID?]/[macOfPhone].boot requested by [OfficePublicIP] could not be generated

Nothing comes to mind as being changed (outside of updating to V18 update 6). The log message reference phones/extensions (e.g. ext # 6XX) freshly provisioned as little as couple months ago. Our config is much more basic/standard, not using VLANs, using RPi SBC. Appears to be a possible bug (or a configuration that isn't supported moving forward?)... So far phones still appear to work, not sure if will cause problem provisioning new phone(s) though.

I don't monitor this forum much, so apologies if miss a notification. Not currently free to do too much debug.

 

[Guillaume Bourgeois]

Seeing same behavior post V18 Update 6 - 3CX logs are spitting out dozens of:

Provisioning file /provisioning/[instanceID?]/[macOfPhone].boot requested by [OfficePublicIP] could not be generated

Nothing comes to mind as being changed (outside of updating to V18 update 6). The log message reference phones/extensions (e.g. ext # 6XX) freshly provisioned as little as couple months ago. Our config is much more basic/standard, not using VLANs, using RPi SBC. Appears to be a possible bug (or a configuration that isn't supported moving forward?)... So far phones still appear to work, not sure if will cause problem provisioning new phone(s) though.

I don't monitor this forum much, so apologies if miss a notification. Not currently free to do too much debug.

This is not a bug..
I have already replied to this remark, see here to know more :

Please read ;
https://www.3cx.com/community/threads/update-6-beta-available-now.118217/post-549620

Thank you anyway for your participation.

 

[Csut12]

This is not a bug..
https://www.3cx.com/community/threads/update-6-beta-available-now.118217/post-549620

Is « bruteforce » tentative hack/download provisioning file ..
is same for password…

The below seems less like *hack* and more like fallback behavior. Specifically the "[OfficeIP]" below is not an unknown IP but correct IP of our office.

If this is bruteforce/hack attempt why is coming from our office? Presumably this is either Phone or SBC sending these requests.

Provisioning file /provisioning/[instanceCode]/firmware/yealink//YL0000000000.rom requested by [OfficeIP] could not be generated
3CX Template Parser ID: 30040 02/04/2023 9:00:46 PM
Provisioning file /provisioning/[instanceCode]/firmware/yealink//YL0000000000.rom requested by [OfficeIP] could not be generated
3CX Template Parser ID: 30040 02/04/2023 9:00:43 PM
Provisioning file /provisioning/[instanceCode]/firmware/yealink//YL0000000000.rom requested by [OfficeIP] could not be generated
3CX Template Parser ID: 30040 02/04/2023 9:00:40 PM
Provisioning file /provisioning/[instanceCode]/firmware/yealink//T48S.rom requested by [OfficeIP] could not be generated
3CX Template Parser ID: 30040 02/04/2023 9:00:36 PM
Provisioning file /provisioning/[instanceCode]/firmware/yealink//T48S.rom requested by [OfficeIP] could not be generated
3CX Template Parser ID: 30040 02/04/2023 9:00:33 PM

Here is example bruteforce/hack attempt:

User or password is invalid from 87.237.52.58. (User: 101, password: Phone101)
3CX Phone System Management Console ID: 30037 02/05/2023 6:53:51 PM
User or password is invalid from 87.237.52.58. (User: 105, password: Phone@105)
3CX Phone System Management Console ID: 30037 02/05/2023 6:53:51 PM
User or password is invalid from 87.237.52.58. (User: 222, password: Phone222)
3CX Phone System Management Console ID: 30037 02/05/2023 6:53:51 PM

 

[Guillaume Bourgeois]

The below seems less like *hack* and more like fallback behavior. Specifically the "[OfficeIP]" below is not an unknown IP but correct IP of our office.

...

Forgive me, when I wrote my answer, I didn't understand that you knew the IP address where the requests come from.

But, you can read @JohnS_3CX's answer in another post.
https://www.3cx.com/community/threads/provisioning-errors-in-v18-update-6-rc.118759/post-551522

Hi,

You can ignore these messages, this is not a failure or actual issue.

By default, the phones are programmed by Yealink to ask for various files, none of which are needed to work successfully with 3CX. Think of them as optional functions that phones have.

This is not a problem at all, and your functionality is not affected. Update 6 RC has more detailed Event logs, so you are just seeing messages that were not visible in the past, but were still happening in the background.

Have nice day !

Sincerely,