Summary:	ASTERISK-14537: AMI doesn't handle COLP correctly when bridging IAX and SIP channels after an attended transfer
Reporter:	alexb (alexb)	Labels:
Date Opened:	2009-10-21 19:04:57	Date Closed:
Priority:	Minor	Regression?	No
Status:	Open/New	Components:	Core/ManagerInterface
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) tapi-1st_scenario.txt ( 1) tapi-2nd_scenario.txt ( 2) typescript-1st_scenario.txt ( 3) typescript-2nd_scenario.txt
Description:	Please compare the different behavior of the TAPI client in the following scenarios: Scenario 1 (fully working): A calls B@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@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. ****** ADDITIONAL INFORMATION ****** sip.conf: [general] . sendrpid=pai .
Comments:	By: alexb (alexb) 2009-10-22 06:47:20 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! By: alexb (alexb) 2009-11-04 06:56:15.000-0600 Can I help somehow?