New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure SDK Review - [IC3 ACS Calling] #7241
Comments
Native SDK UI SDK |
TelecomManager is a system service provided by the Android operating system that allows apps to interact with and manage various aspects of the telephony and call handling functionality on Android devices. It is part of the Android Telephony framework. If Contoso developers set a value to CallAgentOptions.telecomManagerOptions that will enable TelecomManager integration. When TelecomManager integration is enabled, Contoso application will no longer be able to select Audio output device. Contoso developers will need to use SDK to change audio route. TelecomManagerOptions telecomManagerOptions = TelecomManagerOptions();
telecomManagerOptions.phoneAccountId = "<unique string per application>”;
telecomManagerOptions.isResumeCallAutomatically = false;
CallAgentOptions options = CallAgentOptions();
options.telecomManagerOptions = telecomManagerOptions;
CallClient callClient = CallClient(callClientOptions);
CallAgent callAgent = callClient.createCallAgent(
context,
callConfig.communicationTokenCredential,
options
).get();
Call call = callAgent.join(context, joinMeetingLocator, joinCallOptions);
// Set Audio output via TelecomManager. Only in use with TelecomManager integration.
call.setAudioRoute(CallAudioState.ROUTE_SPEAKER)
|
New SDK Review meeting has been requested.
Service Name: IC3 ACS Calling
Review Created By: Bob Gao
Review Date: 03/12/2024 02:05 PM PT
Hero Scenarios Link: Not Provided
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: .NET, iOS, Android,
Description: ACS Calling Mar Release
Detailed meeting information and documents provided can be accessed here
The text was updated successfully, but these errors were encountered: