Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setup capture for rtcp #53

Closed
pcw11211 opened this issue Jan 25, 2016 · 8 comments
Closed

setup capture for rtcp #53

pcw11211 opened this issue Jan 25, 2016 · 8 comments

Comments

@pcw11211
Copy link

how do i setup captagent to capture rtcp and how/where can the info/charts be viewed ?

@lmangani
Copy link
Member

Hi,

In order to capture RTCP packets you need to load and configure the protocol_rtcp module:
<load module="protocol_rtcp" register="local">

The reports will be correlated to their corrensponding SIP sessions and visualized in HOMER 5 call details when matching

@pcw11211
Copy link
Author

in /usr/local/etc/captagent/captagent.xml
<load module="socket_pcap" register="local"/>
in /usr/local/etc/captagent/protocol_rtcp.xml
<?xml version="1.0"?>
<document type="captagent_module/xml">
<module name="protocol_rtcp" description="RTCP Protocol" serial="2014010402">
<profile name="proto_rtcp" description="PROTO RTCP" enable="true" serial="2014010402">
<settings>
<param name="rtcp-version" value="2"/>
</settings>
</profile>
</module>
</document>
/usr/local/etc/captagent/socket_pcap.xml
<profile name="socketspcap_rtcp" description="RTCP Socket" enable="true" serial="2014010402">
<settings>
<param name="dev" value="eth10"/>
<param name="promisc" value="true"/>
<param name="reasm" value="false"/>
<param name="capture-filter" value="rtcp"/>
<param name="capture-plan" value="rtcp_capture_plan.cfg"/>
<param name="filter">
<value>portrange 10000-60000</value>
</param>
</settings>
</profile>
everything else default

which database/table does the trcp info go to?

@adubovikov
Copy link
Member

Hi,

it should be populated into the rtcp_capture table.

Wbr,
Alexandr

On 26.01.2016 03:31, pcw11211 wrote:

in /usr/local/etc/captagent/captagent.xml
||
in /usr/local/etc/captagent/protocol_rtcp.xml
||
||
||
||
||
||
||
||
||
||
/usr/local/etc/captagent/socket_pcap.xml
||
||
||
||
||
||
||
||
|portrange 10000-60000|
||
||
||
everything else default

which database/table does the trcp info go to?


Reply to this email directly or view it on GitHub
#53 (comment).

@pcw11211
Copy link
Author

nothing in rtcp_capture
is rtcp_capture suppose to be rotated like sip_capture tables?
all i get in captagent debug is
[DEBUG] database_hash.c:111 RTCP CALLID: 600856161@192.168.1.41
[DEBUG] database_hash.c:112 RTCP IP PORT: XXX.XXX.XXX.XXX:29747
rest is [DEBUG] protocol_sip nothing with protocol_rtcp

@adubovikov
Copy link
Member

it has internal partitioning.

looks like you don't have any rtcp packets on this interface at all. Can
you please check it ?

On 26.01.2016 15:59, pcw11211 wrote:

nothing in rtcp_capture
is rtcp_capture suppose to be rotated like sip_capture tables?
all i get in captagent debug is
[DEBUG] database_hash.c:111 RTCP CALLID: 600856161@192.168.1.41
[DEBUG] database_hash.c:112 RTCP IP PORT: XXX.XXX.XXX.XXX:29747
rest is [DEBUG] protocol_sip nothing with protocol_rtcp


Reply to this email directly or view it on GitHub
#53 (comment).

@pcw11211
Copy link
Author

image

rtcp is there

@pcw11211
Copy link
Author

please share a captagent debug output (sample) for rtcp packet

@lmangani
Copy link
Member

Should be one of the capture settings - is your device really eth10?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants