V20 Update 10 Alpha: MCP, AI Server & More Admin Control

[richiewhite]

Some really cool stuff here, and looking forward to getting to grips with the new features!

Has there been a change to call flow scripting? I ask as a script that works with CRM integration, that currently works fine in U9, is failing to start in U10 with the error "Autofac.Core.DependencyResolutionException: An exception was thrown while activating CallFlow.CFD.CRMLookupComponent.". More than happy to provide more detail if needed.

 

[SoterisH_3CX]

Hello @richiewhite

I have sent you a PM.

 

[tronic]

For the MCP client is there any future scope to include configuration endpoints?

 

[Pierre.m]

Hi,


Very nice update. Can't wait to test the MCP features. You guys are killing it!

I have one question about the Caller ID selection. I read this is only for users that have multiple DDI's assigned to them. We have customers with muli-queue agents who need to change their caller ID depending on the departpment they use for that call. The DDI's are assigned to their queues and not the users themselves. It would be awsome if they could select Queue assigned DDI's as well. At this moment we use multiple outbound rules and prefixes to handle this.

Thanks.

This is a very nice update indeed!
The ability to select the outgoing DID is an option we have been waiting for for a long time. Primarily because we previously worked with systems where this was possible. But indeed, being able to select DIDs from the queues you are currently active in would be the best option. Especially for smaller environments where someone can then call back from the general DID or, for example, the support queue DID.

 

[Nick - SPN Co]

Hey everyone- Great update. Really looking forward to a lot of these features. I am running into two issues with the new alpha update. Is anybody else seeing something similar?

1. My AI Agents are no longer answering. I have tried on both realtime1.5 and realtime2.0 and the calls just hang up immediately. Our agents were working prior to the update.
2. I created a new AI Transcription server and it shows successfully connected. However calls seem to get stuck "in queue". Screenshot below:

View attachment 52138


In event log i see the following occurring a few different times.

Error

4096

07/30/2026 1:57 PM

AI Bridge

Internal Server Error

UPDATE:

Agents answer internal calls. They do not answer external calls. A call into an agent triggers the AI Bridge error above.

I'm having the same issue but it's with both internal and external calls to agents. I've tried setting up new agents from scratch too but am getting the same AI Bridge internal server error. Were you able to get this one resolved at all?

 

[SteveITS]

Thanks. Found one I didn't expect, but they have some dummy extensions and I bet they can use the new queue escalation algorithms.

 

[Ryan_Fisher_Techmode]

I'm having the same issue but it's with both internal and external calls to agents. I've tried setting up new agents from scratch too but am getting the same AI Bridge internal server error. Were you able to get this one resolved at all?

Nick-

Are you still having the issue? I believe this ended up being a problem on the Open AI side and has been resolved for me.

 

[Nick - SPN Co]

Nick-

Are you still having the issue? I believe this ended up being a problem on the Open AI side and has been resolved for me.

I still am! I'm working with 3CX support on it but so far no luck. It does look to be an OpenAI issue from the logs.

 

[Ronald Lysmont]

Hi,


Very nice update. Can't wait to test the MCP features. You guys are killing it!

I have one question about the Caller ID selection. I read this is only for users that have multiple DDI's assigned to them. We have customers with muli-queue agents who need to change their caller ID depending on the departpment they use for that call. The DDI's are assigned to their queues and not the users themselves. It would be awsome if they could select Queue assigned DDI's as well. At this moment we use multiple outbound rules and prefixes to handle this.

Thanks.

Same request here. DDI's are assigned to Department and routed to CQ's. The CQ members from different CQ's use outbound rules with corresponding prefix and outbound caller ID. It would be great if they can select the outbound rule instead of remembering the prefix for that rule.

Thanks

 

[SweetAction]

Same request here. DDI's are assigned to Department and routed to CQ's. The CQ members from different CQ's use outbound rules with corresponding prefix and outbound caller ID. It would be great if they can select the outbound rule instead of remembering the prefix for that rule.

Thanks

SMS works this way (a number assigned to a queue is usable for outbound messages of queue members), so hopefully this is an easy change.

 

[Leon - Telepuls]

great updates thanks!

 

[bbaker73]

Undockable Dial pad and granular user permisions to reporting node is AWESOME.

One request on the dial pad, when undocked, can you add the BLF hide/unhide menu. As it is, need to redock it, toggle the blf, then undock again to show the blf panel un the undocked dialer.

 

[N_G]

This is a massive step forward for 3CX.

Native MCP support, the standalone 3CX AI Server, programmable voice applications, and greater administrative control are not simply new features, they are transforming 3CX into a much more flexible and enterprise ready communications platform.

Instead of forcing customers to adapt their operations to a fixed system, these capabilities will allow us to build around their actual business requirements.

We are genuinely excited to start testing these features and developing new solutions for our clients.

Shukran to Nick and the entire 3CX team. Update 10 looks like a major milestone, and we cannot wait to see what we can build with it.

Thank you so much for the heads up! Much appreciated.

And thank you for all the other positive comments from everyone. We have one more nice improvement coming for update 10 after our summer break!