Sangoma Desktop call log shows the ring group that delivered the call, not the actual caller ID

The call log on Sangoma Desktop seems to be utterly useless as it shows the ID of the ring group that delivered the call, rather than the caller ID of the caller:

Is there a setting to solve this, or is it a bug? (PBXact 16 / Sangoma Phone desktop latest updates)

Note that call log on the P370 phone, UCP, and Sangoma Talk mobile all show the correct caller IDs.

Can confirm. We have the same bug.

Hi @billsimon ,

We are not able to reproduce this issue locally with SCD 4.2.0 & external incoming call routed to ring group. I can see that the caller ID is correctly displayed in all 3 endpoints i.e SCD(4.2.0), STALK(1.0.17) & P370 phone.

Please restart sangomartapi process and then check the call log as it may fix this issue.

Thanks

Restart the desktop app and when it fetches the call log it then shows the ring group instead of the proper caller ID.

Hi @billsimon ,

Please share your inbound route & ring group settings to check further.

Thanks

It only happens after reopening Sangoma Phone. All call logs to the ring group are changed to the name and number of the ring group.

Example:

  1. Incoming call to the ring group in Sangome Phone.
  2. Sangome Phone shows the correct caller name and id in the call log.
  3. Exit and start Sangome Phone again.
  4. The entry in the call log is changed to the caller name and id of the ring group.

Inbound route points to ring group 1190. 1190 is a ringall group with four extensions. It’s as simple as you can get.

Hi,

Issue has been reproduced locally. We will fix and share the version soon.

Thanks

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.