Abnormal display of the last number received

[ThierryP]

Hi,
We all work at home and PCs are equipped with the 3CX app, mobile phones too and we have external phones connected in STUN mode.
The problem is that regularly, during an internal call, the number displayed on the extension of the recipient is the last incoming number of the caller.
If you hang up and call back, the problem goes away.

Example: the number 00412123 calls and the extension 200 answers.
At the end of the call, the line is hung up.
Extension 200 calls extension 500.
On the display of extension 500, it is indicated that it is 00412123 calling. Extension 500 picks up and hears extension 200.

I restarted the server, without success. This is the last version of 3CX phone on windows.
What to do?

Thanks for your help

In french:
Nous travaillons tous à la maison et les PC sont équipés de l'app 3CX, les tel mobiles aussi et nous avons des tel externes connectés en mode STUN.
Le problème est que régulièrement, lors d'un appel interne, le numéro affiché sur l'extension du destinataire est le dernier numéro entrant de l'appelant.
Si on racroche et qu'on rappelle, le problème disparaît.

Exemple: le numéro 00412123 appelle et c'est l'extension 200 qui répond.
A la fin de la communication la ligne est raccrochée.
L'extension 200 appelle l'extension 500.
Sur l'affichage de l'extension 500, il est indiqué que c'est le 00412123 qui appelle. L'extension 500 décroche et elle entend bien l'extension 200.

J'ai redémarré le serveur, sans succès. C'est la dernère version de 3CX phone sous windows.
Que faire?

Merci pour votre aide

Thierry

 

[Evolute IT]

Does this happen only when a deskphone is involved?

 

[leejor]

I think you might have to see if this is a device issue, or 3CX issue. What device is boing used? Does this happen on more than one extension? If so, are they all the same type of set/display?
Did this just start (any updates?), or has it been happening for a while?

 

[ChrisC_3CX]

Hello @ThierryP,

As mentioned by @Frederick Marcoux and @leejor, the first thing you may want to consider doing is eliminating the possibility of this having something to do with the IP Phones being used if any. Check if you can still replicate this issue when using the 3CX Webclient for both the internal caller and the internal callee. Let us know what happens.

 

[ThierryP]

Hello,
The problem occurs with such a landline or with the 3CX application in a PC or on an Android mobile phone.

This phenomenon has been happening since the penultimate version of 3CX and I was hoping that the last update fixed this bug.

I will do some more testing to try to isolate the source of the problem.

A last point is that we use such SNOM 760 for the "STUN" connected stations. I will test with Yealink.

Thank you for your support