[asterisk-bugs] [JIRA] (ASTERISK-25352) res_hep_rtcp correlation_id is different then res_hep

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227492#comment-227492 ] 

Matt Jordan commented on ASTERISK-25352:
----------------------------------------

The issue is correct - {{res_hep_pjsip}} tracks things by {{Call-ID}} (as we won't have a channel name when the {{INVITE}} request is first processed) and {{res_hep_rtcp}} tracks by Channel name, as it is independent of {{res_hep_pjsip}}.

So, to tie both together, we really can't use the Channel name :-(

With a small tweak in {{chan_pjsip}}'s {{dialplan_function}}, we can expose the SIP Call-ID. In {{res_hep_rtcp}}, we can then check the channel technology type and attempt to get the SIP Call-ID if the underlying channel type is a SIP ({{chan_sip}} or {{chan_pjsip}}) channel. If it's neither, we can always fall back to channel name.

> res_hep_rtcp correlation_id is different then res_hep
> -----------------------------------------------------
>
>                 Key: ASTERISK-25352
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25352
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_hep_rtcp
>    Affects Versions: 13.4.0
>         Environment: CentOS 6 x86_64
>            Reporter: Kevin Scott Adams
>            Assignee: Matt Jordan
>
> When trying to correlate data using Web Homer there seems to be no RTCP data with the call flow.
> When researching further the data is in the Homer database but the res_hep is using call_id and res_hep_rtcp is using the channel name, so the Homer SQL lookup shows no data.



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