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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25352:
------------------------------------------

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.

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].

> 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
>
> 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)