- Joined
- May 4, 2023
- Messages
- 36
- Reaction score
- 20
Hey,
Had this strange issue, only experienced it twice but wondering if anyone has encountered it before or any suggestions on where to look. It's incredibly frustrating when it happens.
The issue is sometimes when factory resetting a previously provisioned phone, the phone cannot reprovision with the 3CX server.
When this happens, I can provision a different phone (same make/model) to the 3CX server under the same extension without issue. I can also take the factory reset phone and provision it on another 3CX server no problem.
I also see an error logged on 3CX when the factory resetted phone attempts to provision:
Provisioning file /provisioning/[PATH]/[MAC].cfg requested by [IP] could not be generated
If I try to browse to the provisioning URL from my PC I get a 404 error and the same message is logged on the 3CX system.
It seems almost as if the MAC address of the phone somehow becomes blocked or stuck somewhere.
Reprovioning was attempted
1. without removing the phone from the extension, just logging into the phone after reset and entering the provisioning URL
2. Removing the phone from the extention and recreating
The phone was also factory reset several times during and the above steps were taken multiple times.
The last time I resolved it by restarting the whole 3CX server at OS level. This time that did not work, but after leaving it for ~3 hours while I caught up on other things, when I returned to it I re-created the phone on 3CX and it provisioned without issue.
Obviously neither of these options are great for live environments.
As mentioned, the phone is now provisioning fine and back to the customer so I don't have any way to test potential fixes unless I can find a way to reproduce the issue, just hoping someone familiar with the inner workings of 3CX might know what could potentially be causing this.
I can't remember what the details were the last time this happened, but this time:
3CX on-premise 18.0 (Build 20)
Phone: Yaelink T42s running firmware 66.86.0.5
Provisioning over STUN, however I did try access the provisioning URL with the 3CX server LAN IP address and got the same 404 page and error logged in 3CX
Had this strange issue, only experienced it twice but wondering if anyone has encountered it before or any suggestions on where to look. It's incredibly frustrating when it happens.
The issue is sometimes when factory resetting a previously provisioned phone, the phone cannot reprovision with the 3CX server.
When this happens, I can provision a different phone (same make/model) to the 3CX server under the same extension without issue. I can also take the factory reset phone and provision it on another 3CX server no problem.
I also see an error logged on 3CX when the factory resetted phone attempts to provision:
Provisioning file /provisioning/[PATH]/[MAC].cfg requested by [IP] could not be generated
If I try to browse to the provisioning URL from my PC I get a 404 error and the same message is logged on the 3CX system.
It seems almost as if the MAC address of the phone somehow becomes blocked or stuck somewhere.
Reprovioning was attempted
1. without removing the phone from the extension, just logging into the phone after reset and entering the provisioning URL
2. Removing the phone from the extention and recreating
The phone was also factory reset several times during and the above steps were taken multiple times.
The last time I resolved it by restarting the whole 3CX server at OS level. This time that did not work, but after leaving it for ~3 hours while I caught up on other things, when I returned to it I re-created the phone on 3CX and it provisioned without issue.
Obviously neither of these options are great for live environments.
As mentioned, the phone is now provisioning fine and back to the customer so I don't have any way to test potential fixes unless I can find a way to reproduce the issue, just hoping someone familiar with the inner workings of 3CX might know what could potentially be causing this.
I can't remember what the details were the last time this happened, but this time:
3CX on-premise 18.0 (Build 20)
Phone: Yaelink T42s running firmware 66.86.0.5
Provisioning over STUN, however I did try access the provisioning URL with the 3CX server LAN IP address and got the same 404 page and error logged in 3CX