How to use the ACS samples in production on Azure?

Hi @Alex I understand you're facing an issue with the Azure Communication Services (ACS) Bot sample code getting stuck on the line var answer_result = await answerCallResult.WaitForEventProcessorAsync(); after deploying it to Azure App Service. This seems related to the linked question about deploying an IVR bot using ACS.

Firstly, the linked question was in relation to using Azure Functions. If you're deploying to a standard Web App in Azure App Service, there might be compatibility issues. Consider using Azure Functions for a more suitable environment for this type of bot.

Secondly, from what you shared it seems like the code might be encountering a deadlock situation where the WaitForEventProcessorAsync() method is waiting for an event that never arrives. Review the code surrounding this line to see if there are any potential deadlocks. Ensure proper event handling and resource cleanup.

Lastly, please double-check your Azure configuration for ACS Bot to make sure all required resources are provisioned correctly, including:

• Azure Communication Services resource
• Bot Channels registration (SMS, Phone Number)
• Connection strings for accessing ACS resources
• Verify that the bot has the necessary permissions (e.g., "Microsoft.Communication/services/read" and "Microsoft.Communication/users/readall") to access required resources.

Hope that help.

-Grace

Hi @Grmacjon-MSFT

Thanks for the fast reply. Basically this is the code that I'm using:

https://github.com/Azure-Samples/communication-services-dotnet-quickstarts/blob/main/callautomation-openai-sample-csharp/CallAutomationOpenAI/Program.cs

It worked for me fine on local machine without modification. When I came to publish it on Azure, I had to make choices about the technology to use. I wasn't sure exactly what to pick, so this is what I chose (in the Visual Studio publishing wizard):

Target: Azure
Specific target: Azure App Service (Windows)
App Service: (I created one in the correct Resource Group)
API Management: (I created one in the correct Resource Group)
Depoloyment type: Publish (generates pubxml file)

After deployment then it creates a "web app" in Azure. You're saying that I should not use this, right?

It also creates an "API Management Service".

If I'm going down the wrong route, are you able to direct me to any videos or articles that discuss how best to deploy these kind of apps, ideally one that mentions the Azure samples and getting them to work in Azure?