Describe the bug

When using the cap_initiator api to start and stop a unicast stream, the command bap preset does not come into work after having used cap_initiator unicast_start followed by cap_initiator unicast_stop the first time. Prior to the first use of cap_initiator unicast_start, whatever is configured with bap_preset will be used for the stream, but not after.

This was seen on an nrf5340 Audio DevKit

Regression

• This is a regression.

Steps to reproduce

1. Build and flash the audio shell and zephyr controller, e.g. build:
   west build -b nrf5340_audio_dk/nrf5340/cpunet -d build/nrf5340audiodk/hci_ipc samples/bluetooth/hci_ipc --pristine -- -DCONF_FILE=nrf5340_cpunet_iso-bt_ll_sw_split.conf
2. Have a peripheral device with a unicast audio server on it that supports cap.
3. Connect to the audio shell over uart and issue the following commands:

bt init
bt clear all
bt connect-name <name>
bap init
bap discover

optionally set bap preset configuration to whatever you want, and then

cap_initiator unicast_start
// Wait for streaming to occur
cap_initiator unicast_stop

4. Change presets with bap preset command to be different
5. Try to restart a unicast stream with cap_initiator unicast_start and observe that the stream will be started with whatever was running in CI: Test checkpatch #3.

Relevant log output

Impact

Annoyance – Minor irritation; no significant impact on usability or functionality.

Environment

nrf5340 Audio DevKit

Additional Context

No response