LE Audio device as central and peripheral simultaneously

[Turo]

My question is related to LE Audio, i guess, since i have no previous experience from it. Is it possible to have a device as a peripheral for mobile phone sending data to some characteristics and same time as a central to another nRF5340 streaming LE Audio (CIS)?

Device A and B are nRF5340. Device A generating and streaming audio to device B. Audio stream could be e.g. a mic(s) or line(s) in. There is no audio stream from device A to mobile phone. Also device A is generating and sending data to a mobile phone. Data could be e.g. temp, status, voltage etc.

I'm just wondering for example how much resources this LE Audio (CIS) takes.

[Jon]

Ok, I tried modifying the audio sample (gateway) to only connect to a single headset and added the NUS service similar to the example referenced above. I can connect to the device using NRFConnect application, but no services or characteristics appear on the NrfConnect app. Any idea what I might be doing wrong?

Update: I found that if I temporarily remove the call to ble_mcs_server_init() in the audio sample code, then my services will appear. Perhaps there is a conflict with the gatt_register_services done by mcs and other gatt services?

[Karl Ylvisaker]

Hello,

Could you share some details on what changes you made to the application to add the NUS service, and how it is behaving following these changes?
Do you get any unexpected logs, or are there logs you would expect to see that are missing, etc?

Best regards,
Karl

[Jon]

I don't know if you saw my update, but I tracked down the issue to the audio sample calling ble_mcs_server_init(). If I set CONFIG_BT_MCS=n then my services/attributes show up normally.

[Karl Ylvisaker]

Oh, I see it now - I am glad to read that you were able to resolve the issue.

Please do not hesitate to ask if you should encounter any other issues or questions in your work! :) 

Best regards,
Karl

[Jon]

Ultimately I'll have to figure out why this breaks -- I thought that there could be  multiple calls to bt_gatt_register_services...

For the moment, though, I don't need to worry about this.