[asterisk-bugs] [JIRA] (ASTERISK-25189) AMI: Add Linkedid header to standard channel snapshot information.

[Richard Mudgett (JIRA)]

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

Richard Mudgett updated ASTERISK-25189:
---------------------------------------

    Description: 
Per John Hardin:
{quote}
In a DialBegin/DialEnd event, is there any reason not to include the LinkedId of the caller channel?

When I see a Local/xxx;2 channel as the caller in a DialBegin/DialEnd event, I need to know the channel connected to Local/xxx;1. From looking at the channel status info, it looks like this is propagated through the Linkedid field from the original caller to the Local/xxx;2 channel. Does this seem reasonable?
{quote}

Looking at the code this seems quite easy to do and a useful addition for when Local channels are involved.

It would be more useful as an addition to the standard channel snapshot headers added to many AMI event messages.

  was:
{quote}
In a DialBegin/DialEnd event, is there any reason not to include the LinkedId of the caller channel?

When I see a Local/xxx;2 channel as the caller in a DialBegin/DialEnd event, I need to know the channel connected to Local/xxx;1. From looking at the channel status info, it looks like this is propagated through the Linkedid field from the original caller to the Local/xxx;2 channel. Does this seem reasonable?
{quote}

Looking at the code this seems quite easy to do and a useful addition for when Local channels are involved.

It would be more useful as an addition to the standard channel snapshot headers added to many AMI event messages.


> AMI: Add Linkedid header to standard channel snapshot information.
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-25189
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25189
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface/NewFeature
>    Affects Versions: 13.4.0
>            Reporter: Richard Mudgett
>            Assignee: Richard Mudgett
>
> Per John Hardin:
> {quote}
> In a DialBegin/DialEnd event, is there any reason not to include the LinkedId of the caller channel?
> When I see a Local/xxx;2 channel as the caller in a DialBegin/DialEnd event, I need to know the channel connected to Local/xxx;1. From looking at the channel status info, it looks like this is propagated through the Linkedid field from the original caller to the Local/xxx;2 channel. Does this seem reasonable?
> {quote}
> Looking at the code this seems quite easy to do and a useful addition for when Local channels are involved.
> It would be more useful as an addition to the standard channel snapshot headers added to many AMI event messages.



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