Bug in hidden contacts on mobile devices

[Fredy Martínez Cubillos]

When searching for contacts in the mobile applications even if the contact has the extension options set: Hide this extension from 3CX company phonebook and 3CX Apps, it is shown:​

​

Which should not happen.​

​

 

[Vali_3CX]

That's a screenshot from Team, not from Contacts, I am correct?

 

[Fredy Martínez Cubillos]

That's a screenshot from Team, not from Contacts, I am correct?

Hi Vali, that's right, the screenshot is taken from iPhone in your Team view

 

[Vali_3CX]

If you search in Contacts, you find it there?

 

[Fredy Martínez Cubillos]

If you search in Contacts, you find it there?

Yes, it is also displayed from there.

 

[Vali_3CX]

OK, please tell me the PBX version as in Management Console's Dashboard, including the build number, so I could check on Monday with my PBX teammates, this is not a client issue.Thanks!
P.S 1201 is local extension or is a bridged one (extension 201 with bridge prefix 1)?

 

[Fredy Martínez Cubillos]

OK, please tell me the PBX version as in Management Console's Dashboard, including the build number, so I could check on Monday with my PBX teammates, this is not a client issue.Thanks!
P.S 1201 is local extension or is a bridged one (extension 201 with bridge prefix 1)?

3CX Version: 18.0 Update 4 (Build 965) for Debian 10

The extension is local, it is a 4-digit extension. No bridging is handled in this configuration.

Thanks. Excellent weekend!

 

[Vali_3CX]

@fredy.martinez
We were not able to replicate the issue, so I would suggest you to exit the iOS client by swiping it up, then start it again and check if the extension is still shown on Contacts. If not, it would mean it was a temporary caching problem and you could try the same exit/relaunch on Android. If extension is still shown, then I would suggest to contact our tech support so they can check the PBX configuration.
Thanks!

 

[Fredy Martínez Cubillos]

Hello Vali,
Good day.

Verification was carried out with the client and it was identified that through the user groups, one of these was visually exposing the extension number to all users. Consequently, we proceeded to remove and with this the expected behavior is achieved.

The novelty was explained to the end customer and it was understood.

Thanks for the support.