[asterisk-bugs] [Asterisk 0016566]: [patch] AMI Redirect hangs up channel if it is in Background()

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16566 
====================================================================== 
Reported By:                BigJimmy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16566
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.28 
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-01-07 13:04 CST
Last Modified:              2010-01-11 12:10 CST
====================================================================== 
Summary:                    [patch] AMI Redirect hangs up channel if it is in
Background()
Description: 
When using the Asterisk Manager interface to redirect a channel, it hangs
up the channel if it is in the dialplan executing Background().  Other
applications, such as Playback don't have this problem.

/var/log/asterisk/full give me this odd error:
[Jan  7 10:54:05] WARNING[23048] pbx.c: Channel 'SIP/104-00000003' sent
into invalid extension '?' in context 'agentconnect0', but no invalid
handler

The invalid extension displayed is char(255).
====================================================================== 

---------------------------------------------------------------------- 
 (0116449) BigJimmy (reporter) - 2010-01-11 12:10
 https://issues.asterisk.org/view.php?id=16566#c116449 
---------------------------------------------------------------------- 
It appears that the issue has been resolved in the 1.4 branch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-11 12:10 BigJimmy       Note Added: 0116449                          
======================================================================