| Summary: | ASTERISK-25189: AMI: Add Linkedid header to standard channel snapshot information. | ||
| Reporter: | Richard Mudgett (rmudgett) | Labels: | |
| Date Opened: | 2015-06-23 16:18:43 | Date Closed: | 2015-06-26 11:02:05 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface/NewFeature |
| Versions: | 13.4.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| 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. | ||
| Comments: | |||