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.
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:
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
@girishmani Is this issue still open in development? Could you provide an update about it? With the latest sangomartapi, it is still not resolved for us. Thank you.
This is being looked at internally but there is some difficulty reproducing the issue on the latest versions of the modules in question.
@billsimon would you please confirm if this issue persists on v16 ? And how about v17 ?
Still seeing it on v16. I don’t have a v17 system with this configuration and phone licensing.
Here’s what the situation looks like. I just tested an inbound call.
Sangoma Phone is running; a call comes in. In this case it went unanswered, but it shows properly in the call log:
I close Sangoma Phone and open it again, and now the call log has replaced that entry with the ring group number and makes it look like an outgoing call according to the arrow icon on the left.
Please post some scrubbed SIP logs of the INVITE to pastebin.freepbx.org
Which invite? From PBX to the softphone? For the call shown above:
INVITE sip:[email protected]:53192;transport=WS SIP/2.0
Via: SIP/2.0/WS 127.0.0.1:8088;rport;branch=z9hG4bKPja741b571-0780-4bb0-9d34-64b745dc67b8;alias
From: "WIRELESS CALLER" <sip:814xxx@uc-yyy>;tag=61576e51-4cfe-4873-8c89-e3de2cb3667a
To: <sip:[email protected]>
Contact: <sip:asterisk@uc-yyy:5060;transport=ws>
Call-ID: b019b94b-12bc-4c28-95c5-153f00762380
CSeq: 5699 INVITE
Allow: OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INFO, MESSAGE, REFER
Supported: 100rel, replaces, norefersub, histinfo
X-cid: 9a99f377-cae1-4b1c-868d-d86e81192269
P-Asserted-Identity: "WIRELESS CALLER" <sip:814xxx@uc-yyy>
Max-Forwards: 70
User-Agent: PBXact-16.0.45(20.17.0)
Content-Type: application/sdp
Content-Length: 1048
v=0
...payload...
By the way, a P370 phone pulls up the call logs correctly. Do the hardphone and the softphone make the same server requests to get their call logs?
I also tested it with all the latest FreePBX updates for v16 today and Sangoma Phone Desktop 4.2.0 (Windows).
It looks like the issue only happens when the call wasn’t answered by anyone in the ring group.
If the call got answered everything is fine.
CID Name Prefix - Support:
Mark Answered Elsewhere - Yes
Ignore CF Settings - Yes
Destination if no answers - Announcement => Terminate Call (Hang up)
Everything else has the default values.