V20 U10 Extending Our AI Lead: Improved Agents, MCP, and Local Transcription on a Mac

I'm wondering if related. Pushed the posted Security Update to some of my v20u10 systems this morning, all the systems that have received the update, now error on Integrations -> AI -> Realtime API:
One that also has v20u10, that did not install the security update, does not error.

1794495448377.png
 
  • Like
Reactions: N_G
Hi @Marco@ could you please open a support ticket with us, in this way you can submit us the pbx logs for further analysis.

Thanks!
 
  • Like
Reactions: N_G
  • Like
Reactions: N_G
This release is absolutely killer. The MCP integration has literally proven super useful in less than 30 mins of having it connected.

Well done all.
 
Hope your ready for the second mindblow - Updating 500 phones - ok, next :cool:

View attachment 52852
I know!!!!! Love the new phones page. So much more useful info than before. Great re-design and functionality improvement.

Now all I can wish for Christmas is bulk edit of the following:
- ringtone
- time/date format
- logo
Then I can finally stop worrying about micromanagers and their "valuable input" that will be very helpful to everyone

(Oh... and maybe multicast info)

Did I mention? ..... I LOVE THE NEW UPDATE
 
@HarryI @JamieR @Benedikt Machens Thank you for the heads up good feedback - Re multi edit for ringtone & logo - We will check it out! We are continue our focus on administration automation via our interface but also MCP - I think you will big steps forward there in the next few releases.
 
@HarryI @JamieR @Benedikt Machens Thank you for the heads up good feedback - Re multi edit for ringtone & logo - We will check it out! We are continue our focus on administration automation via our interface but also MCP - I think you will big steps forward there in the next few releases.
Thank you @N_G !!!! Every update is better than the previous.
 
  • Like
Reactions: N_G
Update 10 (20.0.10.1785): GetInboundCalls now returns DestinationDn empty. Intended or a bug?

Our 3CX-hosted instance auto-updated to 20.0.10.1785 overnight on 13 Nov. Since then the XAPI inbound call report returns an empty DestinationDn on every leg. The extension, queue or IVR number now comes back in DestinationCallerId instead. Before the update it was the other way round.

It applies to calls made before the update too, so it looks like a change in how the report is generated, not in the stored call data. The outbound report is unchanged.

Request:
Code:
GET /xapi/v1/ReportInboundCalls/Pbx.GetInboundCalls(periodFrom=...,periodTo=...,trunkDns='',callsType=0)

Same leg, before and after the update:
Code:
Before: "DestinationDn": "16", "DestinationCallerId": "",   "DestinationDisplayName": "User Name (16)"
After:  "DestinationDn": "",   "DestinationCallerId": "16", "DestinationDisplayName": "User Name (16)"
All other fields are unchanged.

Is this a permanent change or a bug? The Update 10 Alpha 2 notes mention "Improved inbound and outbound call report generation", so it may be intended.

- If it's permanent should integrations now read the destination number from DestinationCallerId?
- If it's a bug, is a fix planned?
 
In new V20 U10 update, now we have the option of adding a DID list for users which allows them to call from this number by selecting from the dialpad.
According to instructions, we need to add these numbers to user's profile so it becomes visible on the user's dialpad

Until here it works good. But when i assign these DIDs to the user, the incoming call to this DID directly starts ringing at that user extension.

If i want to use outbound DID selection while calling somewhere ( cool feaute because we really need it)
How can i prevent the change for the incoming calls ( it should follow the trunks own destination like IVR )

What am i missing with setting up new feature?

1794651357175.png1794651671420.png
 
No at present the user can only select from DIDs assigned to them. In update 11 you will be able to allow them to choose from a queue DID, as long as they are part of the queue.