-
-
Notifications
You must be signed in to change notification settings - Fork 75
Capture Plans
Lorenzo Mangani edited this page Nov 10, 2017
·
9 revisions
Capture Plans are pipelines attached to capture sockets and utilized to define processing logic,
using global functions and methods exported by the loaded modules as defined in captagent.xml
.
The socket is defined in each capture plan, supporting the following capture[...]
types:
- pcap
- tzsp
- collector
socket_pcap
-> {profile}
-> capture_plan
/usr/local/etc/captagent/socket_pcap.xml
<profile name="socketspcap_sip" description="HEP Socket" enable="true" serial="2014010402">
<settings>
<param name="dev" value="eth0"/>
<param name="promisc" value="true"/>
<param name="reasm" value="false"/>
<param name="tcpdefrag" value="false"/>
<param name="capture-plan" value="sip_capture_plan.cfg"/>
<param name="filter">
<value>portrange 5060-5091</value>
</param>
</settings>
</profile>
/usr/local/etc/captagent/captureplans/sip_capture_plan.cfg
capture[pcap] {
# here we can check source/destination IP/port, message size
if(msg_check("size", "100")) {
#Do parsing
if(parse_sip()) {
# Drop unwanted methods
if(sip_check("rmethod","OPTIONS") || sip_check("rmethod","NOTIFY")) {
drop;
}
#Multiple profiles can be defined in transport_hep.xml
if(!send_hep("hepsocket")) {
clog("ERROR", "Error sending HEP!!!!");
}
}
}
drop;
}