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

I have some new info on this that may explain what the user above is experiencing as well.

I have now tested this on two seperate systems. Worked perfect on U9. Upgrade to U10 Alpha and it breaks. They both behave exactly the same. At first I thought this was for external calls only but what I have found in testing as that the AI agent will only answer from the internal extension for its boss. If I call internally from any other extension on the system its the same behavior as the external calls. Hang up / Fallback extension.

Error code 4096 "AI Bridge" 500 Server Internal Error
@Ryan_Fisher_Techmode please check Mike's response above

ensure you have the following allowed models on the AI Project i,e gpt-realtime-1.5, gpt-realtime-2, gpt-realtime-whisper.

1785500127740.png
 
Alejando-

Thanks. I have verified the set up.I am positive the api is working because i get full functionality out of it when i call internally as its boss.
 
I have some new info on this that may explain what the user above is experiencing as well.

I have now tested this on two seperate systems. Worked perfect on U9. Upgrade to U10 Alpha and it breaks. They both behave exactly the same. At first I thought this was for external calls only but what I have found in testing as that the AI agent will only answer from the internal extension for its boss. If I call internally from any other extension on the system its the same behavior as the external calls. Hang up / Fallback extension.

Error code 4096 "AI Bridge" 500 Server Internal Error

@Ryan_Fisher_Techmode please check Mike's response above

ensure you have the following allowed models on the AI Project i,e gpt-realtime-1.5, gpt-realtime-2, gpt-realtime-whisper.

1785500127740.png
Exact same issue as me. Models are allowed and there are plenty of credits. It just fails for some reason (setup is configured for realtime-2 and gpt-5.6-luna for chat). Internal or external, neither work.
 
@Ryan_Fisher_Techmode please open a support ticket for further troubleshooting as I have mentioned in my other messages. Thanks!
 
Hello Dears
I confirmed and double checked.
From my side everything is working. However one of our clients had the problem and now it suddenly started to work.
Can you try again?

Strange because https://status.openai.com/ always showed up.

No changes are required to 3CX. Please everyone try again now.
 
Hello Dears
I confirmed and double checked.
From my side everything is working. However one of our clients had the problem and now it suddenly started to work.
Can you try again?

Strange because https://status.openai.com/ always showed up.

No changes are required to 3CX. Please everyone try again now.
Confirmed. It seems it started working but is not super stable. Probably OpenAI issues! I'll keep testing and report back if I have any new clues.
 
  • Like
Reactions: N_G and nikolascx
It's stable dont worry. And it was openai Sending 500 (with empty message)
We also contacted openai in the meantimem.
Sometimes it happens. I think having 1 billion users it's okay if sometimes they give a 500 for some cases.
For us it never failed. So it wasnt a global downtime.
 
Yes music on hold only, if a call is parked it uses the music on hold that you set within System —- Call Parking —- Music on hold file for parked calls.
It would be awesome if the park keys could be set to play the default department music so they could operate in the same way as the hold does per department, hopefully that is an easy feature add on for you guys to build.
 
So many great new features in this update! The pop out dialler is a game changer for the PWA app, our customers are going to love this! Switching phone templates is going to save us so much time with custom handset changes too!
 
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.
 
For the MCP client is there any future scope to include configuration endpoints?
 
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.
 
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.

Error409607/30/2026 1:57 PMAI BridgeInternal 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?
 

Members Online Now

No members online now.

Forum statistics

Threads
111,770
Messages
588,889
Members
164,551
Latest member
voiplam