From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bryan
Field-Elliot
After working diligently with techs from two separate ATA manufacturers, we're pretty convinced that the process of sending RFC2833 DTMF digits outbound, from Asterisk to an ATA, is broken.
Note that I'm not saying that the code in Asterisk -- ast_rtp_senddigit() -- is necessarily broken. We have one vendor claiming it is, and another saying that they don't handle inbound RFC2833 well in the first place.
What I'd really like, is to apply a patch so that, instead of calling ast_rtp_senddigit, we instead generate and send an inband DTMF tone (for a duration of, say, 250ms).
After working diligently with techs from two separate ATA manufacturers, we're pretty convinced that the process of sending RFC2833 DTMF digits outbound, from Asterisk to an ATA, is broken.
Note that I'm not saying that the code in Asterisk -- ast_rtp_senddigit() -- is necessarily broken. We have one vendor claiming it is, and another saying that they don't handle inbound RFC2833 well in the first place.
What I'd really like, is to apply a patch so that, instead of calling ast_rtp_senddigit, we instead generate and send an inband DTMF tone (for a duration of, say, 250ms).
Why not set the ATA to use info, and asterisk to
inband, it should have the same affect.
_______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
