From 10a49ab3627b7e93c01b22376cdf71015422894c Mon Sep 17 00:00:00 2001 From: Joshua Colp Date: Tue, 9 May 2017 10:25:29 +0000 Subject: res_hep_rtcp: Provide chan_sip Call-ID for RTCP messages. This change adds the required logic to allow the SIP Call-ID to be placed into the HEP RTCP traffic if the chan_sip module is used. In cases where the option is enabled but the channel is not either SIP or PJSIP then the code will fallback to the channel name as done previously. Based on the change on Nir's branch at: team/nirs/hep-chan-sip-support ASTERISK-26427 Change-Id: I09ffa5f6e2fdfd99ee999650ba4e0a7aad6dc40d --- configs/samples/hep.conf.sample | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'configs') diff --git a/configs/samples/hep.conf.sample b/configs/samples/hep.conf.sample index 3d1e74139..32bd8df39 100644 --- a/configs/samples/hep.conf.sample +++ b/configs/samples/hep.conf.sample @@ -24,5 +24,9 @@ capture_id = 1234 ; A unique integer identifier for this ; with each packet from this server. uuid_type = call-id ; Specify the preferred source for the Homer ; correlation UUID. Valid options are: - ; - 'call-id' for the PJSIP SIP Call-ID + ; - 'call-id' for the PJSIP or chan_sip SIP + ; Call-ID ; - 'channel' for the Asterisk channel name + ; Note: If 'call-id' is specified but the + ; channel is not PJSIP or chan_sip then the + ; Asterisk channel name will be used instead. -- cgit v1.2.3