Troubleshoot the UI Library
When you're troubleshooting voice or video calls, you might need to provide a call ID. This ID identifies Azure Communication Services calls. Each call can have multiple call IDs.
In this article, you use the Azure Communication Services UI Library to get essential debugging information.
Prerequisites
- An Azure account with an active subscription. Create an account for free.
- A deployed Communication Services resource. Create a Communication Services resource.
- A user access token to enable the call client. Get a user access token.
- Optional: Completion of the quickstart for getting started with the UI Library composites.
Set up troubleshooting
For detailed documentation and quickstarts about the Web UI Library, see the Web UI Library Storybook.
To learn more, see Troubleshooting in the Web UI Library.
For more information, see the open-source Android UI Library and the sample application code.
Get debug information
You can get the call ID from CallComposite
.
val callComposite: CallComposite = CallCompositeBuilder().build()
...
val callHistoryRecords = callComposite.getDebugInfo(context).callHistoryRecords
val callHistoryRecord = callHistoryRecords.lastOrNull()
val callDate = callHistoryRecord.callStartedOn
val callIds = callHistoryRecord.callIds
For more information, see the open-source iOS UI Library and the sample application code.
Get debug information
You can get the call ID from CallComposite
.
let callComposite = CallComposite()
...
let debugInfo = callComposite.debugInfo
let callHistoryRecords = debugInfo.callHistoryRecords
let callHistoryRecord = callHistoryRecords.last
let callDate = callHistoryRecord?.callStartedOn
let callIds = callHistoryRecord?.callIds
Users can also find the call ID via the action bar on the bottom of the call screen. For more information, see the UI Library use cases.