[Home]

Summary:ASTERISK-06396: S(timeout) is broken
Reporter:Roy Sigurd Karlsbakk (rkarlsba)Labels:
Date Opened:2006-02-22 06:25:00.000-0600Date Closed:2011-06-07 14:10:34
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_dial
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) app_dial-2006-02-22-1.patch
Description:hi

it seems S(timeout) is broken...

reproduced with 1.2.4+ and trunk

exten => _X.,1,Dial(Zap/g1d/${EXTEN}|S(30))

   -- Executing Dial("Zap/2-1", "Zap/g1d/98013356|S(30)") in new stack
   -- Requested transfer capability: 0x00 - SPEECH
   -- Called g1d/98013356
Feb 22 13:14:37 WARNING[20228]: app_dial.c:1156 dial_exec_full: Invalid timeout specified: 'S(30)'
Comments:By: Roy Sigurd Karlsbakk (rkarlsba) 2006-02-22 07:49:42.000-0600

this patch fixes the problem, as it may seem, but the wrong timeout is set. it just counts the seconds like a normal timeout. The call can last any period of time...

   -- Executing Dial("Zap/2-1", "Zap/g1d/98013356|S(3)") in new stack
   -- Requested transfer capability: 0x00 - SPEECH
   -- Called g1d/98013356
   -- It may seem like the number from 'S(3)' is 3
   -- Zap/3-1 is proceeding passing it to Zap/2-1
   -- Nobody picked up in 3000 ms
   -- Hungup 'Zap/3-1'

By: Roy Sigurd Karlsbakk (rkarlsba) 2006-02-22 07:56:49.000-0600

sorry about this
as file pointed out on irc, the syntax is dial(dst|timeout|opts)
it's probably me having a bad day

please close this

By: Matt O'Gorman (mogorman) 2006-02-22 09:26:54.000-0600

not a bug