[asterisk-bugs] [Asterisk 0017191]: Specifying return_context for ParkAndAnnounce affects 'h' exten behavior

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17191 
====================================================================== 
Reported By:                kobaz
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17191
Category:                   PBX/pbx_config
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.26 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-15 10:32 CDT
Last Modified:              2010-04-15 10:38 CDT
====================================================================== 
Summary:                    Specifying return_context for ParkAndAnnounce
affects 'h' exten behavior
Description: 
sip peer 210 context = cos_internal+local+ld+intl

I have the following dialplan:

context cos_internal+local+ld+intl {
  includes {
    services;
  }

  h => {
    GoSub(dialOut,h,1);
  }
}

context services {
  10 => {
    ParkAndAnnounce(,90,Console/dsp,park_timeout);
    // ParkAndAnnounce(,90,Console/dsp); // use this instead and flow is
correct
    Hangup();

park_timeout:
   NoOp();
  }
}
====================================================================== 

---------------------------------------------------------------------- 
 (0120469) kobaz (reporter) - 2010-04-15 10:38
 https://issues.asterisk.org/view.php?id=17191#c120469 
---------------------------------------------------------------------- 
It looks like it has to do with the fallback offset:

Will timeout back to extension [cos_internal+local+ld+intl] 10, 3
  versus
Will timeout back to extension [cos_internal+local+ld+intl] 10, 1

so it's setting some internal return position... and the return position
is not reset when it hits 'h'

the 3 is the start of park_timeout:... which is on line 3... (the comment
is ignored)
so that makes sense, since it can fallback to the park timeout label after
the timeout is hit... but... the timeout line number should not be applied
to running 'h' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-15 10:38 kobaz          Note Added: 0120469                          
======================================================================