[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=227496#comment-227496 ] 

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

So, before I go all crazy and starting changing things...

{{res_hep_pjsip}} will currently change the UUID when it can find the channel name. That will currently correlate to {{res_hep_rtcp}}'s UUID. The only thing that will be missed in this is the initial INVITE request that creates the channel.

Clearly, changing this in {{res_hep_pjsip}} would be a breaking change... I'm just not sure that we'd care.

Before I make a code change, please let me know if you see any value in having {{res_hep_pjsip}} switch the UUID from the Call-ID to the 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)