Multiple phones

[MartijnDoeland]

Since the last update (16.3.0.179) we have this on our windows client. It shows the same deskphone multiple times.

 

[MartijnDoeland]

Nobody else has this issue? It's on all our windows clients, local and remote.

 

[Evolute IT]

What's the version of the PBX?

 

[MartijnDoeland]

16.0.6.655

 

[Evolute IT]

Do you see the phone multiple times in the 3CX Console > Phones?

 

[MartijnDoeland]

No, I did see other device double, but this disappeared after a reboot. I have never seen the phone on my extension 10x in the console (not even twice)

 

[Tm99]

Hi,

we have nearly the same issue since updating to the latest version of 3CX (16.0.1078) and with the new shipped version of the 3CX Windows app. I looked a little bit deeper into the issue and it seems that the problem exists not only in the Windows client but also in the web client. Just a handful of users have the problem and their phone appears two times. I checked the web client and we can see the phone two times, too. In the console it is definitely registered once.

 

[Sobiera]

What happens when you remove the phone and reprovision it again? Are your connections to the server stable? Have you changed parameters under settings > parameters ? Is your network configured properly

 

[Tm99]

Removing and re-adding the phone makes no difference. The only way to solve this seems to completely delete the whole extension. I tested this with one user and the second phone is gone, for now. But of course this is not an option for the other users. We have over a hundred extensions. In the meantime, more and more people are seeing the issue, also our boss. I cannot say when this happens because most users just click okay and don’t care. Our connection is local LAN and we never had any issues with the PBX. There was no change in the configuration of the PBX since the update last Friday. At the moment I cannot recommend to install the update and we are evaluating to go back to a restore point from last week.

 

[AWS2P]

Same problem here with a 3cx PBX on latest V16.7.1078 release on debian Vm on premise with YealinkT42S and T46S on latest FW 66.85.0.5

Like previous post I can't imagine deleting all extensions and recreate to fix this problem

 

[Daytona]

We are experiencing the same issue. On-prem Windows server running 16.0.1078. Ever since the last update, we have a few confirmed users with the issue. One extension has 2 phones registered to it and both phones are duplicated. Sometimes it shows each phone 4 times in the drop-down. If you close the Windows application and relaunch it, it will *only show each phone twice instead of 4 times.

 

[Tm99]

So we definitely have a bug in the latest version. Issue exists on Debian and Windows with default templates and different phone manufacturers, in 3CX Windows app and web client. Would be nice to get some feedback from the support.

 

[JohnS_3CX]

Hi everybody,

The app has since been updated to 16.3.0.198 so I would be interested to know if

a) you still have the issue with this version

b) and whether the multiple registrations ALSO appear in the management console

 

[Tm99]

Hi @JohnS_3CX,

version 16.3.0.198 of the client was shipped with the latest 3CX update version 16.7.1078. So it is already installed to mostly all users since we updated the PBX. But I want to make clear, that this is not a problem with the Windows client because we see the same behavior in the web client, too. And no, there are still no multiple registrations in the management console.

Due to vacation of most people in the office, I was able to restart the Debian VM where 3CX is running and it seems to fix the problem, for now. I was able to test it only with two users and both got no prompt to choose a phone for CTI. Nevertheless, I’m pretty sure this will occur again because more and more people saw the issue over the whole week.

If you need any logfiles/support data, feel free to contact me.

 

[JohnS_3CX]

Thanks @Tm99 it's good to hear that it was resolved after the restart. If the issue returns in the future we would like to hear about it.