Azure communication service - Call disconnect default timeout

Renold Christy, Allen 21

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

ajkuma 22,526 Reputation points Microsoft Employee

2022-05-05T17:53:30.033+00:00

@Renold Christy, Allen , 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.
ajkuma 22,526 Reputation points Microsoft Employee

2022-05-05T17:54:09.767+00:00

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
Renold Christy, Allen 21 Reputation points

2022-05-06T06:40:53.023+00:00

Thank you for the response @ajkuma . 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.
ajkuma 22,526 Reputation points Microsoft Employee

2022-05-07T19:22:12.46+00:00

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.
Ebraheem Al-Muneyeer (MSFT) 951 Reputation points Microsoft Employee

2022-05-09T13:07:35.167+00:00

@Renold Christy, Allen , 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
Renold Christy, Allen 21 Reputation points

2022-05-09T13:18:51.507+00:00

Thanks @Ebraheem Al-Muneyeer (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
Ebraheem Al-Muneyeer (MSFT) 951 Reputation points Microsoft Employee

2022-05-09T15:02:09.87+00:00

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
ajkuma 22,526 Reputation points Microsoft Employee

2022-05-09T18:59:20.72+00:00

@Renold Christy, Allen , Following-up, as @Ebraheem Al-Muneyeer (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!

Accepted answer

ajkuma 22,526 Reputation points Microsoft Employee

2022-05-09T19:07:18.063+00:00

@Renold Christy, Allen , 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 @Ebraheem Al-Muneyeer (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’.
Please sign in to rate this answer.
Renold Christy, Allen 21 Reputation points

2022-05-10T10:06:39.053+00:00

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

ajkuma 22,526 Reputation points Microsoft Employee

2022-05-10T11:08:03.683+00:00

@Renold Christy, Allen , Glad you found the information helpful. Thanks for the update. It's much appreciated.
Sign in to comment

Azure communication service - Call disconnect default timeout

0 additional answers