[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:43 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();
  }
}
====================================================================== 

---------------------------------------------------------------------- 
 (0120471) kobaz (reporter) - 2010-04-15 10:43
 https://issues.asterisk.org/view.php?id=17191#c120471 
---------------------------------------------------------------------- 
Something like that... it doesn't exactly match up with the 3 versus the 1,
but there's an issue in there somewhere. 

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