This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 10%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERP%3C/text%3E%3C/svg%3E)
I've created a communication service resource in Pay As You Go subscription and attached a cognitive service, but I'm facing an issue in Answering Machine Detection.
Sharing error as below:
[
{
"id": "b13fbf83-6daf-44bc-be7e-e568651b707f",
"source": "calling/callConnections/03004580-fe06-4180-8a05-5ca48bf52e69",
"type": "Microsoft.Communication.PlayFailed",
"data": {
"failedPlaySourceIndex": 0,
"version": "2025-06-15",
"operationContext": "tts-play-test",
"resultInformation": {
"code": 400,
"subCode": 8565,
"message": "Action failed due to a bad request to Cognitive Services. Please check your input parameters."
},
"callConnectionId": "03004580-fe06-4180-8a05-5ca48bf52e69",
"serverCallId": "aHR0cHM6Ly9hcGkuZmxpZ2h0cHJveHkuc2t5cGUuY29tL2FwaS92Mi9jcC9jb252LXVhZW4tMDQtcHJvZC1ha3MuY29udi5za3lwZS5jb20vY29udi9rNXpnTGxHc3NFMmcxSjJYcXhaVExRP2k9MTAtMTI4LTEwNC04MiZlPTYzODk4MDU5ODUzNDc1MDMwNA==",
"correlationId": "c28b2896-1219-4e65-996d-0979635dc717",
"publicEventType": "Microsoft.Communication.PlayFailed"
},
"time": "2025-11-13T10:54:38.4795918+00:00",
"specversion": "1.0",
"datacontenttype": "application/json",
"subject": "calling/callConnections/03004580-fe06-4180-8a05-5ca48bf52e69"
}
]
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 86%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVL%3C/text%3E%3C/svg%3E)
Hi @Rahul Patel Just following up to check if your issue has been resolved or if you still require any assistance. Kindly share the requested information so we can connect for further troubleshooting if needed.
Please remove this answer. I've added answer instead of comment.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 46%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMG%3C/text%3E%3C/svg%3E)
To fix this issue, make sure your Azure Communication Service and Cognitive Service are in the same region, then recheck that you are using a valid voice name and a supported audio format like riff-16khz-16bit-mono-pcm in your TTS request. Also confirm that your Cognitive Service is on the Standard (S0) tier, because the Free (F0) tier does not work with ACS calling features. Verify that the key and endpoint you are using match the Cognitive Service you attached, and reconnect the Cognitive Service to your Communication Service if needed. After correcting these settings, the Answering Machine Detection and TTS should work normally.
Hello Vimal & Mahi,
I can also screenshare and explain the problem. Please let me know if it is feasible for you to do.
Hi @Rahul Patel
Just checking in to see if above information was helpful ?
Hi @Rahul Patel
Could you please help me understand the following questions?
Hello, Please find my answers here:
Are you able to create and successfully make outbound calls without the AMD feature enabled?
Answer : Yes, outbound calls works fine.
Have you verified that your Cognitive Services instance is operational, correctly configured, and using the Standard tier?
Answer : Yes, cognitive service created, connected with azure communication service and it is indeed in standard tier. I can share more details regarding connection string, endpoints over email if you like.
Hi @Rahul Patel
Error sub code 8565 indicates Cognitive Services Error.
The error indicates that Azure Communication Services successfully forwarded the TTS/AMD request to Cognitive Services, but Cognitive Services rejected it with a 400 BadRequest (subCode 8565). This usually occurs when the Cognitive Services resource is not Standard tier, the region doesn’t match ACS, the TTS input parameters are invalid (unsupported voices/SSML), or the Speech resource is not fully provisioned.
Official Documentation: Generic subcodes
Hello Vimal and Mahi,
Thank you for you reply.
const callConnection = await acsClient.getCallConnection(callConnectionId);
const callMedia = callConnection.getCallMedia({
cognitiveServicesEndpoint: "https://australiaeast.api.cognitive.microsoft.com/" // Paid resource endpoint
});
const playSources = [{
text: "Hello, this is a test call from Azure.",
sourceLocale: "en-AU",
voiceName: "en-AU-NatashaNeural",
kind: "textSource"
}];
const playTo = [{
phoneNumber: "PARTICIPANT_PHONE_NUMBER" // Replace with the target participant's phone number
}];
const playOptions = {
operationContext: "tts-play-test"
};
try {
await callMedia.play(playSources, [], { operationContext: "tts-play-test" });
console.log("TTS playback started successfully!");
} catch (err) {
console.error("Error during TTS playback:", err);
}
Hi @Rahul Patel
You can follow the official documentation here for full implementation details. This article explains how Answering Machine Detection works in ACS using audio analysis to distinguish between a human and a voicemail. It describes how to enable AMD during call setup, monitor the resulting events, and then branch your call flow (e.g., play a message or leave a voicemail) based on the detection result.