question

RenoldChristyAllen-6911 avatar image
0 Votes"
RenoldChristyAllen-6911 asked ajkuma-MSFT commented

Azure communication service - Call disconnect default timeout

If a ACS audio/video call is active/in-progess for a certain period. Will the call gets disonnected automatically or is there any default time for the call to disconnect

azure-communication-services
· 8
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@RenoldChristyAllen-6911, Thanks for posting this question.

To better assist you on this, is this the issue you’re facing since the setup or just recently started seeing the problem? Do you receive any specific error message/error code? Could you please share more details about your setup?

1.To isolate the issue, you may enable and access call logs

2.Review the calling SDK error codes. These error codes are exposed through the call.callEndReason property after a call ends.

3.User-facing diagnostics is currently supported only for our JavaScript / Web SDK.
You may examine various properties of a call via User Facing Diagnostics, please check this doc.

4.The doc outlines timeouts that apply to the Communication Services Calling SDKs. Typically, the timeout must not occur when the call is active.


Kindly let us know, we will be more than happy to assist you further.


1 Vote 1 ·

Additionally, This article provides information about limitations and known issues related to the Azure Communication Services Calling SDKs and Communication Services Call Automation APIs. Known issues in the SDKs and APIs


1 Vote 1 ·

Thank you for the response @ajkuma-MSFT. Actually I wanted to check regarding the clean-up of a ACS call if that call is active/in-progress for more than 24 hours. Does ACS cleans up the resources automatically or is it something we need to do to end/disconnect the call.

Also is there any default time limit set for an ACS call.

It would be very helpful if get any MSDN doc regarding this case.


0 Votes 0 ·
ajkuma-MSFT avatar image ajkuma-MSFT RenoldChristyAllen-6911 ·

RenoldChristyAllen-6911, Thanks for the follow-up and additional clarification. I'm discussing on this internally and will get back to you shortly. I hope you have a great weekend.

0 Votes 0 ·

@RenoldChristyAllen-6911 , Currently, there is a hard limit of 30 hours for calls, after that they will be ended (Not sure if that will change in the future). That said, and to avoid not needed charges, it is recommended to always end the call by calling "call.hangUp({ forEveryone: true });" Notice how we set forEveryone to true, which will end the call for everyone in the call. You can check our sample here getting-started-with-calling




1 Vote 1 ·

Thanks @ealmuneyeer-MSFT for the response that helps a lot :).
Is there a msdn doc regarding the 30 hours hard limit for the calls. If so, can you share the link for them as well

Thanks in advance for sharing

0 Votes 0 ·
ajkuma-MSFT avatar image ajkuma-MSFT RenoldChristyAllen-6911 ·

@RenoldChristyAllen-6911, Following-up, as @ealmuneyeer-MSFT mentioned, the limit is 30 hours and implement the recommended solution.

Regarding Azure docs, I have relayed this feedback to our Product Engineering (and Content team), and they have a work item to update this point in the doc to add more clarity.
However, currently there is no ETA on when this update will be published in the doc. As soon as we have more information on this, I’ll update this thread.

-To benefit the community, I’ll go ahead and summarize this info shared as an answer. Please Accept’ it as an answer, this will help users to find the answers easily if they have the same question. Thank you and have a great week!

Kindly be assured that we have relayed the feedback to our PG team. We appreciate your valuable feedback. Thanks for your patience!

1 Vote 1 ·
ealmuneyeer-MSFT avatar image ealmuneyeer-MSFT RenoldChristyAllen-6911 ·

I could not find that documented anywhere in the msdn documentation. I will follow-up on this internally to check the possibility to add it to our documentation

0 Votes 0 ·

1 Answer

ajkuma-MSFT avatar image
0 Votes"
ajkuma-MSFT answered ajkuma-MSFT commented

@RenoldChristyAllen-6911, To benefit the community, posting our discussion as an answer.

Currently, there is a hard limit of 30 hours for calls, after that they will be ended.

Workaround: To avoid charges, it is recommended to always end the call by calling "call.hangUp({ forEveryone: true });".
Notice how we set forEveryone to true, which will end the call for everyone in the call. You can check our sample here getting-started-with-calling
-Thanks to @ealmuneyeer-MSFT for sharing this.

Azure doc: We have relayed this feedback to our Product Engineering (and Content team), and they're working on adding more clarity on this.
However, currently there is no ETA on when this update will be published in the doc. As soon as we have more information on this, I’ll update this thread.


Kindly be assured that we have relayed the feedback to our PG team. We appreciate your valuable feedback.

Thanks for your patience!


To benefit the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer’ & ‘Up-Vote’.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks @ajkuma-MSFT and @ealmuneyeer-MSFT for your valuable response. Surely this has helped the question I put forth :)
Once again thank you :)

0 Votes 0 ·
ajkuma-MSFT avatar image ajkuma-MSFT RenoldChristyAllen-6911 ·

@RenoldChristyAllen-6911, Glad you found the information helpful. Thanks for the update. It's much appreciated.

0 Votes 0 ·