[asterisk-bugs] [JIRA] (ASTERISK-25352) res_hep_rtcp correlation_id is different then res_hep
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Sat Sep 5 15:25:33 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227494#comment-227494 ]
Matt Jordan commented on ASTERISK-25352:
----------------------------------------
Note that the first patch that will need to be done is just to {{chan_pjsip}}, in order to extract the SIP call-id.
> 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)
More information about the asterisk-bugs
mailing list