FYI,
I just tested bind_digit_action with inband dtmf and it works splendidly. I recommend using bind_digit_action. Also, in case you didn't see it, Brian West added a magic extension that looks for the presence of "telephone-event" in the SDP and then turns on inband dtmf detection if the rtpmap is missing. Look in conf/dialplan/default.xml for the "global" extension. The lines that do the auto dtmf thing are commented out by default. I just uncommented them and tested with Eyebeam configured for inband dtmf. (It also works when Eyebeam is set for 2833...)
Also, on the FS conf call today the community did a tag-team effort to test and document the bind_digit_action app. It has a lot more information than it did previously:
Hope this helps.
-MC
On Wed, Dec 22, 2010 at 8:01 AM, Dmitry Sytchev
<kbdfck@gmail.com> wrote:
Hi! We are trying to migrate our Asterisk system to Freeswitch, and
faced with some trouble:
We use inband at user side, and want Freeswitch to regenerate it to
RFC2833 before sending to media gateway.
When user endpoints use rfc2833 bind_meta_app and bind_digit_action
work as expected, but not with start_dtmf (as needed to parse inband
DTMF). We can't use rfc2833 DTMF on user endpoints as there seems to
be a problem in freeswitch or our media gateway leading to audible
DTMF duplicates.
When user endpoints are set to inband, I see messages on console about
DTMF detection:
2010-12-22 18:50:30.802253 [DEBUG] switch_ivr_async.c:2089 DTMF DETECTED: [*]
2010-12-22 18:50:30.803253 [DEBUG] switch_rtp.c:1985 Send start packet
for [*] ts=503795131 dur=160/160/2000 seq=43701
2010-12-22 18:50:30.823282 [DEBUG] switch_rtp.c:1921 Send middle
packet for [*] ts=503795131 dur=320/320/2000 seq=43702
...skip...
2010-12-22 18:50:30.923393 [DEBUG] switch_rtp.c:1921 Send middle
packet for [*] ts=503795131 dur=1920/1920/2000 seq=43712
2010-12-22 18:50:30.923393 [DEBUG] switch_rtp.c:1921 Send end packet
for [*] ts=503795131 dur=2080/2080/2000 seq=43713
...skip...
2010-12-22 18:50:31.242695 [DEBUG] switch_ivr_async.c:2089 DTMF DETECTED: [1]
2010-12-22 18:50:31.242695 [DEBUG] switch_rtp.c:1985 Send start packet
for [1] ts=503798651 dur=160/160/2000 seq=43732
So digits are received but no in-call action launched by
bind_meta_app. I tried start_dtmf before and after bind_meta_app but
with no success. Is there a way to make inband dtmf launch in-call
actions while transcoding it to RFC2833 on trunk side?
I can't make inband dtmf trigger my actions :(
--
Best regards,
Dmitry Sytchev,
IT Engineer
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org