- Joined
- Feb 8, 2019
- Messages
- 124
- Reaction score
- 18
Reprovisoning an already provisioned phone should not take more than a minute. What you are describing in not normal.
When you select a device and click on the reprovision button through the management console the PBX will send a NOTIFY message to the phone asking it to check for updates.
The phone should reply with a 200 OK message and then send a few HTTP "GET" requests to the PBX requesting the various provisioning files. The PBX will reply with 200 OK to the files it can provide and send them to the phone. The time this process needs to complete depends on the size of the files. If there is a new firmware for the phone for example this process could take longer. A normal reprovision for a blf change however should not take over a minute.
The management console log will tell you which files are requested and which ones will be generated but not much more.
You will need to use wireshark to capture a reprovision and see where the delay is.
YiannisH_3CX
Yealink T46S fw 66.84.0.35, but same question for T27G and T23G
3CX has a phone template file.
The extension has 'Phone Provisioning' and BLF settings.
Snippet from management console log file. (this may not be useful)
2019/07/02 17:45:16.877|17660|0026|Inf|PRV: 84 provisioning files are in dictionary
2019/07/02 17:45:16.878|17660|0008|Trc|MYPHONE: Remove phonebook entries of deleted DN 2998
2019/07/02 17:45:16.878|17660|0008|Trc|Hide chat and delete myphone call history for 2998
2019/07/02 17:45:16.878|17660|0014|Trc|Delete ContactImage:
2019/07/02 17:45:16.878|17660|0024|Trc|Delete greetings for extension: 2998
2019/07/02 17:45:16.878|17660|0014|Trc|Delete missed calls notification for extension: 2998
2019/07/02 17:45:16.879|17660|0033|Trc|Delete wake-up time for extension: 2998
2019/07/02 17:45:16.879|17660|0028|Trc|Delete VoiceMails for extension: 2998
2019/07/02 17:45:16.879|17660|0014|Trc|Delete audio conferences for extension: 2998
2019/07/02 17:45:16.879|17660|0028|Trc|Delete favorites group ___FAVORITES___2998
You mention that 3CX sends a NOTIFY request to the phone. I am guessing that the NOTIFY request triggers the phone start the provisioning process. I understand that Yealink firmware supports two auto provisioning methods. Old - without boot files and New - with boot files.
Which method does 3CX support?
old
3CX sends trigger NOTIFY
phone request to download configuration files from 3CX server
Does 'Common.cfg' exist"
yes - download common.cfg
no - skip common.cfg
does 'MAC.cfg' exist?
yes - download 'MAC.cfg'
no - skip download
reboot phone
new
3CX sends trigger NOTIFY
phone request to download configuration files from 3CX server
Does 'MAC.boot' exist"
yes - download MAC.boot and the config file listed in the MAC.boot file
no - skip download MAC.boot
does 'y0000.boot' exist?
yes - download y0000.boot and the config file listed in the y0000.boot file
no - use old method
Which of the above files are created by 3CX using the phone template file?
Which of the files are created by 3CX using the Phone Provisioning and BLF settings?
Another topic,
I understand that the Yealink phone can backup the phone's local settings (upload) to the provisioning server.
Does the 3CX server allow the phones to upload a file to the provisioning folder?
Thank you,