[QUERY] CallAutomationClient: PlayToAllAsync returns "8536" Action failed, file could not be downloaded

[iliev-ilian]

Library name and version

Azure.Communication.CallAutomation 1.1.0

Query/Question

We are using the Call Automation Api und Sdk and have set up Event for Incoming Call. Event is received. When event is received, we:

1. Instantiate CallAutomationClient:
   var client = new CallAutomationClient('');

2. Answer the call:
   var options = new AnswerCallOptions(incomingCallContext, callbackUri)
   {

        CallIntelligenceOptions = new CallIntelligenceOptions() { CognitiveServicesEndpoint = new Uri(<**??????**>) }
    };
   
    AnswerCallResult answerCallResult = await client.AnswerCallAsync(options);
   

3. Call is answered and we receive the corresponding event.

4. We try to play text to all participants:
   var playSource = new TextSource(textToPlay)
   {
   VoiceName = "en-US-NancyNeural"
   };

   var playOptions = new PlayToAllOptions(playSource);
   answerCallResult.CallConnection.GetCallMedia().PlayToAllAsync(playOptions);

5. As event after PlayToAllAsync, we receive PlayFailed event with code "8536" Action failed, file could not be downloaded.

We are following the documentation and sample in https://github.com/Azure-Samples/communication-services-dotnet-quickstarts/tree/main/callautomation-openai-sample-csharp and just replaced the connection strings.

We suppose may be the cognitive services endpoint is not the correct one. Which connection string for Cognitive Services should be used? Or how should we set up the Congnitive Services?
We have tried using following connection strings:

Environment

No response

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

[w1stler]

Similar issue happens on 1.2.0 for Python SDK.

[PascalRoessnerDSA]

Hello, has there been any solution to this? I am running into the same issue using the same sample code as a basis?

[PascalRoessnerDSA]

@iliev-ilian I was able to resolve it now. The issue is that the Azure AI Service is not allowed to be located in Germany - here is the list of supported regions

So creating a new Azure AI Service located in West Europe resolved the issue for me