Repository navigation
BAP Unicast Server with Source ASE only (microphone): Windows 11 never sends Enable after Config QoS #125110
Unanswered
AndrewisAndy
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
I'm building a LE Audio microphone (Source ASE only, no speaker) based on
samples/bluetooth/audio/bap_unicast_server. When paired with Windows 11, thedevice is shown as a microphone, but recording fails: Windows sends Config Codec
and Config QoS, then never sends Enable and releases the ASE after ~15 s.
If I add one Sink ASE (which is never used), Windows enables the Source ASE and
recording works, but Windows then also shows an "audio" (output) endpoint.
Is this a known Windows LE Audio limitation, or is there something on the
server side I can change?
Environment
Configuration (mic-only)
Only a Source PAC is registered; Unicast Server Announcement has Available Sink
Context = 0x0000.
Observed (mic-only)
Windows reads Source PAC/location/contexts and subscribes to ASCS notifications
without errors. When recording starts:
Windows then retries with cig=1 and ends in the same state. Server responses
and ASE notifications all return success. The ASE never leaves QoS Configured,
so no CIS request and no TX happen.
Observed (bidirectional, works)
With 1 Sink ASE + 1 Source ASE (both PACs registered), Windows:
So the Sink ASE appears to be used only as the other half of a bidirectional CIS.
Questions
server? Is there Microsoft documentation on this?
microphone endpoint while still recording successfully?
If so, how can I confirm it from the Zephyr side?
All reactions