- Joined
- Jul 9, 2018
- Messages
- 694
- Reaction score
- 166
We have a bunch of Fanvil X2 phones which we use in a small call centre. They've been great little phones and have worked very well in a hot desk environment for about 8-9 months until we upgraded to V16. V16 also came with a firmware update for these phones and we've subsequently upgraded to 16.1.
Our problem is that everything works fine for a few days (up to a week). After that some weird stuff starts to happen such as:
After this the only way we've been able to get each affected phone working properly again is a factory reset after which it is fine again for a few days (a reboot doesn't fix anything).
I can tell when a phone is affected as under "Phones" in the console the phone in question appears just with it's IP address (i.e. "192.168.x.x") and no longer says "via sbc 192.168.0.2:5060" after it.
Other hot-desking phones are working fine, it's just the Fanvil X2's that are affected.
Our setup is:
I was hoping someone else had experienced a similar issue.
Our problem is that everything works fine for a few days (up to a week). After that some weird stuff starts to happen such as:
- Unable to log out of a phone
- Phone appears to be logged in but shows as logged out in console
- Difficulty joining and leaving queue
- If you log into a new phone it doesn't log you out of the previous phone
- This affects all Fanvil X2's but no other phones.
After this the only way we've been able to get each affected phone working properly again is a factory reset after which it is fine again for a few days (a reboot doesn't fix anything).
I can tell when a phone is affected as under "Phones" in the console the phone in question appears just with it's IP address (i.e. "192.168.x.x") and no longer says "via sbc 192.168.0.2:5060" after it.
Other hot-desking phones are working fine, it's just the Fanvil X2's that are affected.
Our setup is:
- Cloud install hosted by Google deployed via PBX Express
- Local SBC
- Professional 16SC
- Version 16.0.273
- Phones running most recent 3CX approved firmware
I was hoping someone else had experienced a similar issue.