Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
2025-06-05 02:40 PM
2025-06-05 07:41 PM
hi @salle01
I can not duplicate what you are experiencing. I am using zoom workplace app for windows version 6.4.12.
Please see screen shot from zoom workplace app calling desk2 and logs for the call. It shows internal user names and extensions.
What version of zoom workplace are you using?
Did my response answer your question? If so, please don't forget to mark the reply as an accepted solution.
thanks, eliot
2025-06-06 07:26 AM - edited 2025-06-06 07:27 AM
Here is a call log entry for an internal call that occurred recently. It's supposed to show the actual caller, but for some reason, it's showing up as the external caller ID (the call queue extension) we set up for each phone user even though these are internal calls. I am using Zoom version 6.4.12
2025-06-09 02:29 PM
Exact same issue!
2025-07-08 08:56 AM
Hello @Bt86136H,
I'm sorry for the inconvenience and delayed response.
This is to acknowledge that your concern submitted through the ticket TS1866230 has been resolved.
Let us know if there's anything else.
2025-07-08 09:35 AM
It's back to normal on our end. Thank you!