[asterisk-bugs] [JIRA] (ASTERISK-30027) ari: expose channel driver's unique id (i.e. Call-ID for chan_sip/chan_pjsip) in ARI channel resource

Moritz Fain (JIRA) noreply at issues.asterisk.org
Wed Apr 27 07:59:40 CDT 2022


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

Moritz Fain updated ASTERISK-30027:
-----------------------------------

    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.


  was:
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 "pvt_id" in ARI channel resources and makes it possible to retrieve the SIP Call-ID for logging/referencing purposes.



> ari: expose channel driver's unique id (i.e. Call-ID for chan_sip/chan_pjsip) in ARI channel resource
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30027
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30027
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_ari_channels
>    Affects Versions: 19.3.1
>            Reporter: Moritz Fain
>            Assignee: Moritz Fain
>
> 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.



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



More information about the asterisk-bugs mailing list