[Home]

Summary:ASTERISK-13632: H extension doesn't execute inside Macros in 1.4.23.1
Reporter:Matt Schmandt (mschmandt)Labels:
Date Opened:2009-02-23 16:06:58.000-0600Date Closed:2009-02-24 12:08:09.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_macro
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Starting in Asterisk 1.4.23 or 1.4.23.1 the Macro function no longer uses executes the h extension inside the macro after the call is hung up.  This functionality used to work fine in 1.4.22.  With 1.4.23.1 it will execute the h extension back from where the macro was called.

****** ADDITIONAL INFORMATION ******

Below is an example showing that it is not calling the h extension from the marcro.

hqast01*CLI> show dialplan macro-stdexten-ms
[ Context 'macro-stdexten-ms' created by 'pbx_config' ]
 'h' =>            1. Noop("I AM HERE")                          [pbx_config]
 's' =>            1. Dial(SIP/${ARG2}|20)                       [pbx_config]
                   2. Voicemail(${ARG1}|u)                       [pbx_config]

-= 2 extensions (3 priorities) in 1 context. =-
   -- Executing [2095@from_avaya:1] Goto("DAHDI/3-1", "internal|3095|1") in new stack
   -- Goto (internal,3095,1)
   -- Executing [3095@internal:1] Macro("DAHDI/3-1", "stdexten-ms|2096|3096") in new stack
   -- Executing [s@macro-stdexten-ms:1] Dial("DAHDI/3-1", "SIP/3096|20") in new stack
   -- Accepting call from '111111111111' to '2095' on channel 0/3, span 1
   -- Called 3096
   -- SIP/3096-082412f0 is ringing
   -- Channel 0/3, span 1 got hangup request, cause 16
 == Spawn extension (macro-stdexten-ms, s, 1) exited non-zero on 'DAHDI/3-1' in macro 'stdexten-ms'
 == Spawn extension (internal, 3095, 1) exited non-zero on 'DAHDI/3-1'
   -- Executing [h@internal:1] NoOp("DAHDI/3-1", ""Hangup completed"") in new stack
   -- Hungup 'DAHDI/3-1'
Comments:By: Ronald Chan (loloski) 2009-02-23 21:50:32.000-0600

i think there was a similar bug posted here a week ago or so that has been close. i might be wrong but lets hope a developer will pick this
By: Francesco Romano (francesco_r) 2009-02-24 03:10:18.000-0600

I had this problem too. Tried also with the latest 1.4 r178141.