[asterisk-bugs] [Asterisk 0016111]: AMI doesn't handle COLP correctly when bridging IAX and SIP channels after an attended transfer

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16111 
====================================================================== 
Reported By:                AlexB
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16111
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-21 19:04 CDT
Last Modified:              2009-10-22 06:47 CDT
====================================================================== 
Summary:                    AMI doesn't handle COLP correctly when bridging IAX
and SIP channels after an attended transfer
Description: 
Please compare the different behavior of the TAPI client in the following
scenarios:

Scenario 1 (fully working):

A calls B at siprovider
Ext 211 answers A (211's TAPI client shows A)
Ext 211 puts A on hold
Ext 211 dials ext. 212 (212's TAPI client shows 211)
Ext 211 transfers A to 212 (212's TAPI client shows A) <--- !!!


Scenario 2 (wrong behavior):

A calls C at iaxprovider
Ext 211 answers A (211's TAPI client shows A)
Ext 211 puts A on hold
Ext 211 dials ext. 212 (212's TAPI client shows 211)
Ext 211 transfers A to 212 (212's TAPI client shows C) <--- !!!

In both scenarios, the phone display always shows the connected line party
number correctly. However, when A dials the IAX provider's number as in the
2nd scenario, the AMI doesn't send proper information after the call has
been transferred between SIP extensions.

Please see the attached AMI events logs and the ones from the TAPI
monitor.
====================================================================== 

---------------------------------------------------------------------- 
 (0112605) AlexB (reporter) - 2009-10-22 06:47
 https://issues.asterisk.org/view.php?id=16111#c112605 
---------------------------------------------------------------------- 
Let me highlight the following snippet of log taken from
tapi-2n_scenario.txt:

OnConnectedID [000102DF]
	Call.ConnectedID.Blocked = False
	Call.ConnectedID.Name = ''
	Call.ConnectedID.Number = '045******4'
	Call.ConnectedID.OutOfArea = False
	Call.ConnectedID.Flags = [00000008]
		LINECALLPARTYID_ADDRESS


Call.ConnectedID.Number should be '328******5', while '045******4' is the
called number at the IAX provider! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-22 06:47 AlexB          Note Added: 0112605                          
======================================================================