[1.14.2 & older version] Incoming calls use speaker as default output instead of phone mic/earpiece

[mithileshbhumca]

Describe the bug
When an incoming call is answered using the Azure Communication Services Call Composite UI, the default audio output is set to speaker instead of the earpiece/microphone (default device). This causes unexpected loud audio in situations where the user expects a private call through the phone earpiece.

To Reproduce
Steps to reproduce the behavior:

1. Receive an incoming call using the Azure Communication Services Call Composite UI.
2. Answer the call.
3. Observe that the call audio is automatically routed to the speaker.
4. There is no option to default to the earpiece/mic without manually switching the audio route.
5. This bug is always reproducible.
6. Code snippet
   I used to initialized callComposite:
   callComposite = CallCompositeBuilder()
   .applicationContext(context)
   .credential(credential)
   .displayName("")
   .callScreenOrientation(CallCompositeSupportedScreenOrientation.PORTRAIT)
   .telecomManagerOptions(
   CallCompositeTelecomManagerOptions(
   CallCompositeTelecomManagerIntegrationMode.SDK_PROVIDED_TELECOM_MANAGER,
   PHONE_ACCOUNT_ID
   )).build()

For accept incoming call :

callComposite?.accept(context, incomingCallId, getLocalOption())

Expected behavior
When the user answers an incoming call, the audio output should default to the phone’s earpiece/mic (default in-call device), not the loudspeaker. The user should have to explicitly switch to speaker mode if desired.
Same behavior can compare with Teams.

Screenshots
After accepting incoming call, default audio is speaker

AzureCommunicationUILibrary

• Version: [v1.14.2] & all version

Smartphone (please complete the following information):

• Device: Samsung Galaxy M35
• API: 35

Additional context
This issue affects the expected user experience for normal phone calls. By default, users expect to hold the phone to their ear, not have the speaker enabled automatically for incoming calls.

[ahammer]

Thanks for the report. Today the Call Composite does not expose an API to control the initial audio route (earpiece vs speaker). Users can switch routes in-call, but default selection isn’t configurable.

We’ve got “Default audio route selection API” on the backlog. There is no ETA at this time. We’ll update this issue when that changes.

For privacy-focused setups right now: if a Bluetooth device is connected at answer time, audio will route to it by default.