Stefan, This is a generic Asterisk question and not AstLinux specific, but a couple notes ...
There are basically 3 ways DTMF can be sent: 1) dtmfmode=inband where the DTMF is sent as audio in the RTP stream, requires ulaw or alaw CODEC's and should generally never be used. 2) dtmfmode=rfc2833 where DTMF is sent as out-of-band tokens in the RTP stream, the most commonly supported method and is CODEC independent. 3) dtmfmode=info (SIP INFO) where DTMF is sent as out-of-band signals via the SIP channel, generally foolproof if supported. Personally, all my SIP extensions (IP Phones) are configured using dtmfmode=info and my upstream SIP trunk is configured with dtmfmode=rfc2833 since my SIP provider does not support SIP INFO. I have directmedia=no so Asterisk is always in the path. This works well since my SIP provider only sees Asterisk rfc2833 DTMF, not forwarding rfc2833 DTMF generated by various IP Phones that may or may not do things perfectly. It seems it is easy to do SIP INFO correctly, so my Asterisk acts as a SIP INFO -> rfc2833 DTMF gateway of sorts. Lonnie On Oct 20, 2016, at 7:58 AM, Stefan Ulm <s....@divus.biz> wrote: > > Hi all, > > got fixed the problem by using different SIP client, now the features are > working. > The strange thing is, that the dtmf logging lists the dtmf sent from both > clients, the one which could trigger the feature and the one that couldn’t > trigger the feature. > The dtmf logging information are identically except one thing: the dtmf > duration. > The dtmf which could launch the feature have a duration of 160ms, while the > dtmf that couldn’t launch the feature have a duration of 300ms. > > Dtmf which could launch feature: > [Oct 20 08:35:43] DTMF[1368]: channel.c:4063 __ast_read: DTMF begin '#' > received on SIP/904-00000047 > [Oct 20 08:35:43] DTMF[1368]: channel.c:4073 __ast_read: DTMF begin > passthrough '#' on SIP/904-00000047 > > [Oct 20 08:35:43] DTMF[1368]: channel.c:3978 __ast_read: DTMF end '#' > received on SIP/904-00000047, duration 160 ms > [Oct 20 08:35:43] DTMF[1368]: channel.c:4018 __ast_read: DTMF end accepted > with begin '#' on SIP/904-00000047 > > [Oct 20 08:35:43] DTMF[1368]: channel.c:4047 __ast_read: DTMF end passthrough > '#' on SIP/904-00000047 > > [Oct 20 08:35:44] DTMF[1368]: channel.c:4063 __ast_read: DTMF begin '9' > received on SIP/904-00000047 > [Oct 20 08:35:44] DTMF[1368]: channel.c:4073 __ast_read: DTMF begin > passthrough '9' on SIP/904-00000047 > > [Oct 20 08:35:44] DTMF[1368]: channel.c:3978 __ast_read: DTMF end '9' > received on SIP/904-00000047, duration 160 ms > [Oct 20 08:35:44] DTMF[1368]: channel.c:4018 __ast_read: DTMF end accepted > with begin '9' on SIP/904-00000047 > > [Oct 20 08:35:44] DTMF[1368]: channel.c:4047 __ast_read: DTMF end passthrough > '9' on SIP/904-00000047 > -- Feature Found: testfeature exten: testfeature > > Dtmf which couldn’t launch feature: > [Oct 20 08:36:04] DTMF[1368]: channel.c:4063 __ast_read: DTMF begin '#' > received on SIP/115-00000048 > [Oct 20 08:36:04] DTMF[1368]: channel.c:4073 __ast_read: DTMF begin > passthrough '#' on SIP/115-00000048 > > [Oct 20 08:36:04] DTMF[1368]: channel.c:3978 __ast_read: DTMF end '#' > received on SIP/115-00000048, duration 300 ms > [Oct 20 08:36:04] DTMF[1368]: channel.c:4018 __ast_read: DTMF end accepted > with begin '#' on SIP/115-00000048 > > [Oct 20 08:36:04] DTMF[1368]: channel.c:4047 __ast_read: DTMF end passthrough > '#' on SIP/115-00000048 > > [Oct 20 08:36:05] DTMF[1368]: channel.c:4063 __ast_read: DTMF begin '9' > received on SIP/115-00000048 > [Oct 20 08:36:05] DTMF[1368]: channel.c:4073 __ast_read: DTMF begin > passthrough '9' on SIP/115-00000048 > > [Oct 20 08:36:05] DTMF[1335]: channel.c:3978 __ast_read: DTMF end '9' > received on SIP/115-00000048, duration 300 ms > [Oct 20 08:36:05] DTMF[1335]: channel.c:4018 __ast_read: DTMF end accepted > with begin '9' on SIP/115-00000048 > > [Oct 20 08:36:05] DTMF[1335]: channel.c:4047 __ast_read: DTMF end passthrough > '9' on SIP/115-00000048 > > So my question: Is there a maximum dtmf duration to consider for beeing able > to trigger features? > Does it make difference if the dmtf are send inband or outband? > > Best regards > > Stefan Ulm > Technical Department | Research & Development > stefan....@divus.eu > > > > > <image002.png> > > DIVUS Headquarters Pillhof 51 . I-39057 Eppan (Südtirol) . Tel. +39 0471 633 > 662 . Fax. +39 0471 631 829 > www.divus.eu . Privacy: http://www.divus.eu/media/DivusPrivacy.pdf > > Von: Stefan Ulm > Gesendet: Mittwoch, 19. Oktober 2016 18:29 > An: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net> > Betreff: feature codes not working > > Hi all, > > I’m trying to setup some features in feratures.conf in featuremap section to > trigger custom features. > I enabled the monkey playback example in features.conf and add the > set(dynamic_feature=…) to the dialplan. > But when I have a opened connection and I press the feature code “*9” nothing > happens. > > Debugging dtmf in console I can see the dtmf coming: > [Oct 19 18:14:45] DTMF[1128]: channel.c:4063 __ast_read: DTMF begin '*' > received on SIP/904-00000008 > [Oct 19 18:14:45] DTMF[1128]: channel.c:4073 __ast_read: DTMF begin > passthrough '*' on SIP/904-00000008 > > [Oct 19 18:14:45] DTMF[1128]: channel.c:3978 __ast_read: DTMF end '*' > received on SIP/904-00000008, duration 300 ms > [Oct 19 18:14:45] DTMF[1128]: channel.c:4018 __ast_read: DTMF end accepted > with begin '*' on SIP/904-00000008 > > [Oct 19 18:14:45] DTMF[1128]: channel.c:4047 __ast_read: DTMF end passthrough > '*' on SIP/904-00000008 > > [Oct 19 18:14:55] DTMF[1128]: channel.c:4063 __ast_read: DTMF begin '9' > received on SIP/904-00000008 > [Oct 19 18:14:55] DTMF[1128]: channel.c:4073 __ast_read: DTMF begin > passthrough '9' on SIP/904-00000008 > > [Oct 19 18:14:56] DTMF[1128]: channel.c:3978 __ast_read: DTMF end '9' > received on SIP/904-00000008, duration 300 ms > [Oct 19 18:14:56] DTMF[1128]: channel.c:4018 __ast_read: DTMF end accepted > with begin '9' on SIP/904-00000008 > > [Oct 19 18:14:56] DTMF[1128]: channel.c:4047 __ast_read: DTMF end passthrough > '9' on SIP/904-00000008 > > But the feature is not triggered. The clients we are using uses all rfc2833. > Is there any other better way to debug feature triggering? > > I tried on asterisk 1.8. > > Best regards > > Stefan Ulm > Technical Department | Research & Development > stefan....@divus.eu ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
