[asterisk-bugs] [JIRA] (ASTERISK-25613) Incorrect ConnectedLineNum / Name value if call started from ORIGINATE

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228582#comment-228582 ] 

Richard Mudgett commented on ASTERISK-25613:
--------------------------------------------

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.

> Incorrect ConnectedLineNum / Name value if call started from ORIGINATE
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-25613
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25613
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_dial
>    Affects Versions: 11.17.1
>         Environment: CentOs 6.3
>            Reporter: Nikolay Kostruba
>            Severity: Minor
>         Attachments: originate connectedline error.log
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)