Issue with Rendering CallComposite on Incoming Call Using Existing Call Object #5945
-
I'm currently developing a React application using Azure Communication Services (ACS), and I’ve encountered a critical issue when handling incoming calls using the CallComposite component. My app successfully detects and accepts incoming calls using the incomingCall.accept() method. Upon acceptance, I receive a valid Call object. However, I am unable to render the CallComposite using this existing Call instance. Here’s the summary of the issue: CallComposite does not accept a Call object as a prop or as part of its adapter creation workflow. The useAzureCommunicationCallAdapter function expects a targetCallees parameter (e.g., for StartCallIdentifier[]), which is intended for starting a new call — not using an already-established incoming one. As such, there's no documented or supported way to initialize the CallComposite using an accepted Call. I've reviewed the ACS documentation and GitHub issues, but none clearly describe how to integrate CallComposite with an existing incoming call scenario. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi there @inborisov! thanks for starting this discussion. For our CallComposite Incoming Calls are not supported with our CallAdapter and composite. To unlock this scenario for your Calling application you will need to familiarize yourself with our Stateful Call Client and our UI components. Here's some helpful links to get started: |
Beta Was this translation helpful? Give feedback.
Hi there @inborisov! thanks for starting this discussion. For our CallComposite Incoming Calls are not supported with our CallAdapter and composite. To unlock this scenario for your Calling application you will need to familiarize yourself with our Stateful Call Client and our UI components.
Here's some helpful links to get started: