This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2564MODN: Radio connects to hands-free buds but there is no audio in either direction. guidance appreciated.

Part Number: CC2564MODN

Hi team,

my customer is using the CC2564MODN for a mobile radio. they are trying to test audio connection between their radio and some AirPod Pros to start. they just need a simple way of establishing and maintaining a two-way audio path. they can connect to the AirPods but they do not have audio in either direction. can you help provide some guidance to establish two-way audio?

To get to this point they had to send a terminating response upon receiving a “Current Calls List Indication” (note: the sample code did *not* have do anything with this message; however, in order to keep the buds connected they had to send a terminating response after they received this in the callback).  Right now they are receiving the following messages when they perform a connection:

 

1) remote device property changed, connection changed to true

2) authentication IO capabilities request

3) authentication IO capabilities response

4) authentication user confirmation request

5) remote device property changed, pairing changed to true

6) remote device property changed, encryption changed to true

7) remote device property changed, services known changed to true

8) HFR connection status

9) HFR connected

10) HFR available CODEC list indication

11) HFR service level connection established

12) HFR disable sound enhancement indication

13) remote device property changed, sniff state changed

14) remote device property changed, sniff state changed

15) HFR speaker gain indication

16) HFR microphone gain indication

17) HFR response hold status indication

18) HFR current calls list indication

 

At this point their buds stay connected, but they have no audio.  Note: most of these messages are just ignored by the user; the last 2 they send a terminating response.  At this point, it would be helpful to have a bounce diagram of what is expected in response to any of these messages to obtain audio. the sample application mostly just prints out the reception of these messages and doesn’t do anything else — the one change they had to do was send a terminating response after #18.  Any guidance would be appreciated.

can you please also help with the following questions -

1. as an audio gateway, do I present myself as both a headset and hands-free audio gateway, or do you only do one at a time?

2. Can both Hands-Free event callback and Headset event callback be registered at the same time?

3. Does the Headset event callback also require some kind of terminating response?  I was not able to find an equivalent call in the API header files.

Thanks,

Kevin Lai