• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 50 subscribers
  • Views 412 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 Missing SCO Close Event when Phone call goes to Voicemail

Jason Gossiaux
Intellectual 905 points
Other Parts Discussed in Thread: CC2564

Hello there.  We are using the CC2564 to enable a Handsfree Bluetooth Classic headset product.  After much testing we've encountered a very unusual bug.

With an iPhone 6s running iOS9 and paired with the CC2564 headset, if an incoming phone call is not answered (goes to voicemail) the SCO channel is never closed.  This prevents the SCO channel from opening properly when another phone call comes in, and so the phone becomes incapable of generating its own ringtone (phone only vibrates) and the CC2564 becomes unable to correctly process audio. 

When this occurs, the CC2564 also becomes unstable.   It becomes impossible to put it into discovery mode or pair mode and reports errors to all library commands.  A full power cycle and re-connect with all end devices becomes necessary. 

In testing we've successfully called/answered or called/declined 100 phone calls in a row on both Android and iPhones without issue.  It is only when the call goes to voicemail that everything breaks. 

Is this possibly a known issue?  Do we need to somehow detect the call has gone to voicemail and respond with a particular action? 

I'm working to test this particular issue with iOS 10 and with multiple Android phones and will report back with more information.

Thank you,

 - Jason

  • 0
    Intellectual 905 points
    Ok, so iOS10 phones are completely broken. Sigh.

    When a call comes into an iOS10.1.1 device the CC2564 gets a:

    HFRE Control Indicator Status Indication, ID: 0x0005, Description: CALL, Value: FALSE.

    No SCO opens and no ringtone comes through. The phone then proceeds to pretty much lockup once you answer the incoming call. It was unresponsive for 55 seconds and took several seconds to become responsive once the call was ended. No clue how to debug this, as I don't have the Bluetopia Stack source and do not encounter this issue with other phones.

    Anyone have any ideas?

    - Jason
  • 0 in reply to Jason Gossiaux
    Intellectual 905 points

    This also appears working incorrectly on Android phones. After a phone call goes to voicemail, something isn't getting cleared/reset properly. On the next phone call I get no callsetup callback and no ring indicator callbacks - though the phone itself at least rings while our iPhones do not.

    Our particular implementation uses dual SCO (one connection to a Bluegiga module and one to a phone), and has worked beautifully for several months when the call is answered and hungup like normal. I'm trying to test without the dual SCO connected to see if perhaps this is something related to that....

    I do know that with phones things get rather tricky because the CC2564 needs to be the master of the SCO connection to allow for both to work properly. Some phones call the CC2564 post-pair and initiate the Handsfree connection. We detect this, close it, and re-open our own - and that has always worked really well.

    Some more info -

    Running Service Pack 1.4

    GAP_Set_Discoverability_Mode begins returning error -14 when things go bad.  This error isn't listed in the documentation as best I can tell.  Any idea what it means?



    Any help is appreciated,

    - Jason