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

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-25613:
------------------------------------

    Severity: Trivial  (was: Minor)

> 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: Trivial
>         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)