Re: [asterisk-users] DTMF end '1' has duration 57 but want minimum 80 , emulating on ?IAX2/a16-q1-9657

2009-09-22 Thread Steve Underwood
On 09/21/2009 12:46 PM, Tilghman Lesher wrote:
 On Sunday 20 September 2009 22:32:41 Tzafrir Cohen wrote:

 Isn't 40ms the minimal time for a valid dtmf digit?
  
 $ grep -C1 'define AST_MIN_DTMF_DURATION' main/channel.c
 /*! Minimum allowed digit length - 80ms */
 #define AST_MIN_DTMF_DURATION 80

 This post, from the archives, is instructive and germane to the code in
 question:
 http://lists.digium.com/pipermail/asterisk-dev/2007-April/027271.html


If a DTMF decoder doesn't register a digit in under 40ms its broken. 
80ms is the minimum total digit cycle time many people specify, 
including the silence between digits. This time varies between specs, 
though. Some things specify the minimum cycle as 100ms.

Steve


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] DTMF end '1' has duration 57 but want minimum 80, emulating on ?IAX2/a16-q1-9657

2009-09-20 Thread Tzafrir Cohen
On Sat, Sep 19, 2009 at 09:17:31AM -0500, Tilghman Lesher wrote:
 On Saturday 19 September 2009 01:07:54 Rajkumar S wrote:
  I have an occasional problem where DTMF is not recognized, ie if
  clients type a digit while in menu the system does not register it.
 
  In my C server I saw a log line like this today:
 
  DTMF end '1' has duration 57 but want minimum 80, emulating on
  IAX2/a16-q1-9657
 
  Is the above message an indication of this problem? How can I fix it?
 
 It isn't evidence of this problem, but it might be indicative of it.  What
 this message says is that the DTMF lasted for 57ms, but Asterisk normally
 doesn't detect DTMF that lasts for under 80ms, 

Isn't 40ms the minimal time for a valid dtmf digit?

 so it is increasing the
 duration of the DTMF to compensate (because as a digital signal, DTMF is
 reliable, but when sent as audio, it might not be).  What it probably
 indicates is that the DTMF sent to your system is _incredibly_ short, and if a
 DTMF detector is employed, it's possible that the DTMF audio is simply too
 short to be reliably detected.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] DTMF end '1' has duration 57 but want minimum 80 , emulating on ?IAX2/a16- q1-9657

2009-09-20 Thread Tilghman Lesher
On Sunday 20 September 2009 22:32:41 Tzafrir Cohen wrote:
 Isn't 40ms the minimal time for a valid dtmf digit?

$ grep -C1 'define AST_MIN_DTMF_DURATION' main/channel.c
/*! Minimum allowed digit length - 80ms */
#define AST_MIN_DTMF_DURATION 80

This post, from the archives, is instructive and germane to the code in
question:
http://lists.digium.com/pipermail/asterisk-dev/2007-April/027271.html

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com  www.asterisk.org

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] DTMF end '1' has duration 57 but want minimum 80, emulating on IAX2/a16-q1-9657

2009-09-19 Thread Rajkumar S
Hello,

I have a 3 server asterisk configuration where one asterisk (say A) (v
1.4.25) has a digiuim card connected to E1 from which calls are routed
to another asterisk server  (B) (1.6.0.9) over SIP trunk from which
calls get routed to third server (C) (1.6.0.9) via IAX trunk.
SIP clients are connected to third server. A is the PSTN termination
server, B runs the menu and AGI and C is where SIP clients connect.
SIP clients can also dial outside and call goes like C - B - A -
PSTN.

I have an occasional problem where DTMF is not recognized, ie if
clients type a digit while in menu the system does not register it.

In my C server I saw a log line like this today:

DTMF end '1' has duration 57 but want minimum 80, emulating on IAX2/a16-q1-9657

Is the above message an indication of this problem? How can I fix it?

with regards,

raj

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] DTMF end '1' has duration 57 but want minimum 80, emulating on IAX2/a16-q1- 9657

2009-09-19 Thread Tilghman Lesher
On Saturday 19 September 2009 01:07:54 Rajkumar S wrote:
 I have an occasional problem where DTMF is not recognized, ie if
 clients type a digit while in menu the system does not register it.

 In my C server I saw a log line like this today:

 DTMF end '1' has duration 57 but want minimum 80, emulating on
 IAX2/a16-q1-9657

 Is the above message an indication of this problem? How can I fix it?

It isn't evidence of this problem, but it might be indicative of it.  What
this message says is that the DTMF lasted for 57ms, but Asterisk normally
doesn't detect DTMF that lasts for under 80ms, so it is increasing the
duration of the DTMF to compensate (because as a digital signal, DTMF is
reliable, but when sent as audio, it might not be).  What it probably
indicates is that the DTMF sent to your system is _incredibly_ short, and if a
DTMF detector is employed, it's possible that the DTMF audio is simply too
short to be reliably detected.

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com  www.asterisk.org

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] DTMF end '1' has duration 57 but want minimum 80, emulating on IAX2/a16-q1-9657

2009-09-19 Thread Cary Fitch
FWIW:
From old, old memory, DTMF was 60 ms on, 40 ms off, way back when.  With
modern technology, shorter durations could work.  Most phones of all types
don't make a standardized tone burst but produce tones only while the button
is pressed.  Fast punching will produce short tones.

On the other hand, a redialed number will be very well formatted.

Reliability of TT data transfer for audio applications (over the phone voice
mail, credit card, IVR, etc) would be better if the phones would run button
pushes through the redial buffer/formatter.  But they don't.

Cary Fitch

-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tilghman
Lesher
Sent: Saturday, September 19, 2009 9:18 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users]DTMF end '1' has duration 57 but want minimum
80, emulating on IAX2/a16-q1-9657

On Saturday 19 September 2009 01:07:54 Rajkumar S wrote:
 I have an occasional problem where DTMF is not recognized, ie if
 clients type a digit while in menu the system does not register it.

 In my C server I saw a log line like this today:

 DTMF end '1' has duration 57 but want minimum 80, emulating on
 IAX2/a16-q1-9657

 Is the above message an indication of this problem? How can I fix it?

It isn't evidence of this problem, but it might be indicative of it.  What
this message says is that the DTMF lasted for 57ms, but Asterisk normally
doesn't detect DTMF that lasts for under 80ms, so it is increasing the
duration of the DTMF to compensate (because as a digital signal, DTMF is
reliable, but when sent as audio, it might not be).  What it probably
indicates is that the DTMF sent to your system is _incredibly_ short, and if
a
DTMF detector is employed, it's possible that the DTMF audio is simply too
short to be reliably detected.

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com  www.asterisk.org

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users