Summary:	ASTERISK-30027: ari: expose channel driver's unique id (i.e. Call-ID for chan_sip/chan_pjsip) in ARI channel resource
Reporter:	Moritz Fain (maurice2k)	Labels:
Date Opened:	2022-04-26 05:29:56	Date Closed:	2022-05-19 21:28:36
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_ari_channels
Versions:	19.3.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	When creating outgoing calls with ARI channel originate there's no way to get the ID of the underlying channel driver (i.e. the Call-ID in case of SIP/PJSIP). This patch exposes the channel driver's unique ID as "protocol_id" in ARI channel resources and makes it possible to retrieve the SIP Call-ID for logging/referencing purposes.
Comments:	By: Asterisk Team (asteriskteam) 2022-04-26 05:29:57.652-0500 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2022-04-26 05:39:10.552-0500 Do you plan on putting this on Gerrit for code review? By: Moritz Fain (maurice2k) 2022-04-26 06:18:52.694-0500 yes, just pushed it to gerrit By: Friendly Automation (friendly-automation) 2022-05-19 21:28:37.504-0500 Change 18565 merged by Friendly Automation: ari: expose channel driver's unique id to ARI channel resource [https://gerrit.asterisk.org/c/asterisk/+/18565|https://gerrit.asterisk.org/c/asterisk/+/18565] By: Friendly Automation (friendly-automation) 2022-05-19 21:35:02.537-0500 Change 18544 merged by Friendly Automation: ari: expose channel driver's unique id to ARI channel resource [https://gerrit.asterisk.org/c/asterisk/+/18544|https://gerrit.asterisk.org/c/asterisk/+/18544] By: Friendly Automation (friendly-automation) 2022-05-22 15:40:37.273-0500 Change 18413 merged by Joshua Colp: ari: expose channel driver's unique id to ARI channel resource [https://gerrit.asterisk.org/c/asterisk/+/18413|https://gerrit.asterisk.org/c/asterisk/+/18413] By: Friendly Automation (friendly-automation) 2022-05-22 15:40:52.691-0500 Change 18567 merged by Joshua Colp: ari: expose channel driver's unique id to ARI channel resource [https://gerrit.asterisk.org/c/asterisk/+/18567|https://gerrit.asterisk.org/c/asterisk/+/18567]