Unable to Connect ACS/ Web Client to Azure AI Foundry Agent via Voice Live (Agent Mode)

Question

I am referring the Azure Samples GitHub repository: https://github.com/Azure-Samples/call-center-voice-agent-accelerator?tab=readme-ov-file,

I am trying to connect to my exact agent from AI Foundry, they have mentioned the below in the readme descriptionUse Voice Live with Foundry Agents

The Voice Live API supports connecting to an existing Azure AI Foundry Agent, allowing you to leverage pre-built capabilities, knowledge bases, and orchestration features alongside real-time voice interactions.

In the session.update configuration, you can set different properties such as the model, voice settings, turn detection, and agent connection. For detailed configuration options and step-by-step instructions, refer to the official documentation:

Use Voice Live with Foundry Agents

The Voice Live API supports connecting to an existing Azure AI Foundry Agent, allowing you to leverage pre-built capabilities, knowledge bases, and orchestration features alongside real-time voice interactions.

In the session.update configuration, you can set different properties such as the model, voice settings, turn detection, and agent connection. For detailed configuration options and step-by-step instructions, refer to the official documentation:

I have updated the env variables and the acs_media_handler file with my agent form foundry but stuck with the below error

Receiver loop error: no close frame received or sent

This silent close happens before any session.created, response.audio.delta, or other Voice Live events are returned.

help me with proper configuration steps to achieve this.

Answer 1

Try checking the client configuration and network first: make sure you are calling the correct Azure AI endpoint for your region and that the API key or AAD token you use matches the service type, verify the client has the right permissions and role assignments, and confirm there are no firewall, proxy, or DNS rules blocking outbound calls. Look at the browser console and network trace for CORS or TLS errors, ensure the SDK or client library is up to date, and validate that the resource is healthy in the Azure portal and not subject to quota or policy restrictions. If you use AAD, check token audience, expiry, and consent; if you use keys, confirm they are not rotated or expired. Collect timestamps, request IDs and error messages from logs and then contact Microsoft support with those details if the issue persists.