For some calls going through FS, when customers send DTMF tones (using RFC2833), I see those logs :
Here, the customer tried to send "123456". So, I don't know why this "C" character has been sent, and I'm sure the customer didn't send this, because there's no "C" touch on his phone's keypad...
And this "C" results in a double "1" received on the IVR server (hosted on another server than FS).
(Ex : 123456 => 1C23456 => 1123456)
It doesn't happen everytime, but for around 80% of calls... So it's really a problem for us...
I looked at PCAPs for concerned calls, and saw that DTMF tones are only sent with RFC2833, not with SIP INFO nor InBand.
I first thought that digits may be received simultaneously with RFC2833 and InBand but definitely not.
Do you think what could be the cause of that ? I don't use "start_dtmf" in my diaplans, I already saw in other ML topics that this may cause double digit problems.
Is there a way to ask freeswitch to only handle 0-9*# characters ? Or any idea, I'll be glad to try anything that can help us !
Thanks for help,
Kevin
Bien cordialement,
Best Regards,
Kevin MATHY |
Ingénieur VoIP