Summary:ASTERISK-06339: Extension matching with the . wildcard does not obey digit timeout
Reporter:timrobinson (timrobinson)Labels:
Date Opened:2006-02-16 13:55:22.000-0600Date Closed:2006-03-02 02:07:02.000-0600
Versions:Frequency of
Description:When making a call from a Grandstream phone set to Early Dial ('overlap' dialling) Asterisk ignores the digit timeout value, and thinks it has a match as soon as the extension string matches.

Unless I am doing something wrong, digits sent using Early Dial (484 Address Incomplete) should obey this timeout....


Dialplan example:
; Other international calls - Gradwell voip first, then Onetel
exten => _00XX.,1,Set(TIMEOUT(digit)=4)
exten => _00XX.,2,SetcallerID(01256790472)
exten => _00XX.,3,Dial(IAX2/gradwell/${EXTEN},60,tT)
exten => _00XX.,103,Busy

as soon as I dial '00184' Asterisk thinks it has a match and sends only these digits.  Trace below:
Verbosity is at least 4
   -- Remote UNIX connection
   -- Executing Set("SIP/225-0b86", "TIMEOUT(digit)=4") in new stack
   -- Digit timeout set to 4
   -- Executing SetCallerID("SIP/225-0b86", "01256790472") in new stack
   -- Executing Dial("SIP/225-0b86", "IAX2/gradwell/00184|60|tT") in new stack
   -- Called gradwell/00184
   -- Call accepted by (format alaw)
   -- Format for call is alaw
   -- IAX2/gradwell-3 is circuit-busy
   -- Hungup 'IAX2/gradwell-3'
 == Everyone is busy/congested at this time (1:0/1/0)
   -- Executing Busy("SIP/225-0b86", "") in new stack
 == Spawn extension (local, 00184, 104) exited non-zero on 'SIP/225-0b86'
Comments:By: Olle Johansson (oej) 2006-02-28 09:58:57.000-0600

I don't think that timeout is handle anywhere in this case. It's up to the phone to handle all timeouts for digits and so.