Summary:	ASTERISK-25613: Documentation: ConnectedLineNum / Name same value as CallerID if call started from ORIGINATE
Reporter:	Nikolay Kostruba (nkls)	Labels:
Date Opened:	2015-12-07 08:18:37.000-0600	Date Closed:
Priority:	Trivial	Regression?
Status:	Open/New	Components:	Applications/app_dial
Versions:	11.17.1 13.18.4	Frequency of Occurrence	Constant
Related Issues:
Environment:	CentOs 6.3	Attachments:	( 0) originate_connectedline_error.log
Description:	In AMI Event DIAL incorrect value of ConnectedLineNum ConnectedLineName if call started from Originate. In wiki said that The CONNECTEDLINE is the opposite of the CALLERID. In Dial event we receive info about Channel and Destination channel. In fields ConnectedLineNum and Name expected to see info about destination channel, but having the same as CallerId or unknown. Example when ConnectedLineNum equal CallerID while calling from one peer to other: Event: Dial Privilege: call,all SequenceNumber: 7161 File: app_dial.c Line: 854 Func: senddialevent SubEvent: Begin Channel: SIP/1234-000000c5 Destination: SIP/1235-000000c6 CallerIDNum: 1234 CallerIDName: <unknown> ConnectedLineNum: 1234 ConnectedLineName: <unknown> UniqueID: 1449484754.219 DestUniqueID: 1449484756.220 Dialstring: 1235 Full call events log in attachment. This case can be reproduced all time when creating call from originate. Same case is working ok on 1.8 brach.
Comments:	By: Asterisk Team (asteriskteam) 2015-12-07 08:18:40.074-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Richard Mudgett (rmudgett) 2015-12-08 15:46:23.522-0600 This is not a bug. Originate is weird and has to operate this way because only one channel exists at the time the Dial event is generated.  The originated channel is both the callee and caller as far as the Dial event is concerned.  The originated channel starts off as an outgoing channel (callee) that later acts as if it is an incoming channel (caller) to run dialplan when the call is answered.  As an outgoing channel, the connected line information is sent to the destination as the caller id.  When the called party answers, the caller id of the originated channel should get updated with the party id information sent by the answerer if available at the time the call is answered.  If the caller id is not updated then the caller id has historically been what was supplied by the user as the caller id when it was originally originated. By: Rusty Newton (rnewton) 2015-12-08 16:42:25.093-0600 Thanks Richard. We should probably consider this a documentation bug then as this unusual case will certainly be confusing and we should provide an expectation for users at least somewhere in the documentation. I'm not sure where this second, but there is probably a few places on the wiki and perhaps for the ConnectedLineNum /Name fields in the event documentation.