Another bug in the OBIBT and why it should be in Beta testing

[Azouz]

I just found another bug today in the new OBIBT (bluetooth Dongle).
when I call my cell phone that is paired with my obi202, I get the AA asking to press 1, or 2 or 3.
but for some reason the AA doesn't recognize the dtmf. I tried different cell phones and different obi202 devices (i have 2 of them). same issue.
This make the OBIBt useless for Callback or bridging calls.
=========
This is the answer I got from OBI support:
Hi Azouz,

Calling into cellphone service to AutoAttendant – the DTMF is not detected and hence not supported, so what you see below is expected.
Calling into SP1 or SP2 VoIP service to AA, the DTMF detection is supported.

- Obi Support

[jimates]

I guess it is in beta, and you are now a beta tester.

[Trev]

This isn't all that surprising to me.  DTMF becomes distorted over a call phone connection.  It's impossible to parse it after this distortion.  I doubt there's anything Obihai will ever be able to do to solve that.

When you use your cell phone to call into an IVR, the carriers use something similar to rfc2833 signalling.  The phone doesn't generate the DTMF at all.  Instead, a message is sent to the carrier indicating that you pressed a button.  The carrier generates the DTMF tones on their side so there's no distortion.