- Joined
- Nov 23, 2020
- Messages
- 107
- Reaction score
- 23
Hello,
A strange situation: on Friday and Saturday, users from two of our phone systems started reporting that their phones were glitching and displaying a blue screen with the message "Same File!". As is often the case, we only learned about the issue after the phones had already returned to normal operation, so unfortunately no photos are available.
The only two things these systems have in common are:
-- Both use Fanvil X6U phones.
-- Both were upgraded to 3CX v20 Update 10 on November 11.
Has anyone encountered similar behavior?
AI suggests the following explanation:
According to Fanvil's provisioning documentation, when the phone downloads a configuration file from its provisioning server, it compares the downloaded file with the configuration already stored on the phone. If the contents are identical, the phone aborts the update and reports that the file is the same.
That sounds reasonable, but it raises another question: why haven't we seen this before? We've been using X6U phones since 2023, and their auto-provisioning interval has been set to the default 720 minutes the entire time. If this is simply normal provisioning behavior, I would have expected it to appear long before now rather than immediately following the Update 10 upgrade.
Version 20.0 Update 10
AI Edition 16 SC
self-hosted (Vultr VM)
A strange situation: on Friday and Saturday, users from two of our phone systems started reporting that their phones were glitching and displaying a blue screen with the message "Same File!". As is often the case, we only learned about the issue after the phones had already returned to normal operation, so unfortunately no photos are available.
The only two things these systems have in common are:
-- Both use Fanvil X6U phones.
-- Both were upgraded to 3CX v20 Update 10 on November 11.
Has anyone encountered similar behavior?
AI suggests the following explanation:
According to Fanvil's provisioning documentation, when the phone downloads a configuration file from its provisioning server, it compares the downloaded file with the configuration already stored on the phone. If the contents are identical, the phone aborts the update and reports that the file is the same.
That sounds reasonable, but it raises another question: why haven't we seen this before? We've been using X6U phones since 2023, and their auto-provisioning interval has been set to the default 720 minutes the entire time. If this is simply normal provisioning behavior, I would have expected it to appear long before now rather than immediately following the Update 10 upgrade.
Version 20.0 Update 10
AI Edition 16 SC
self-hosted (Vultr VM)
