The receive queue is empty, so either the kernel is no putting the
traffic there or kamailio consume it.
Is this box in the same subnet as initial target? Is it having the same
IP as the initial target of the packets? If I anot wrong, tcp mirroring
is a bit more tricky and restrictive in what has
root@homer02:~# netstat -altp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program name
tcp0 0 homer02.x.xxx:sip*:*
LISTEN 16018/kamailio
tcp0 0 homer02.x.xxx:5066 *:*
L
If you use netstat, what is in the recv queue for tcp packets on sip ports?
netstat -altp
Cheers,
Daniel
On 18/01/2017 16:43, JR Richardson wrote:
> Yes, this is a sipcapture node. I'm listening on a switch port that is
> set to mirror my VoIP traffic. I see all SIP UDP/TCP packets on the
> mir
Yes, this is a sipcapture node. I'm listening on a switch port that is
set to mirror my VoIP traffic. I see all SIP UDP/TCP packets on the
mirror port and the Ethernet port of the host node. Just don't see any
TCP packets process in kamailio, debug 3. UDP packets are processed as
expected.
My conf
Somehow is not clear for me how you have the configuration there ...
before commenting further, this needs to be clarified.
The node you presented the config is a sipcapture instance, right? What
is sending traffic to it? Is another kamailio with siptrace module? Or
the sipcature agent? Or you hav
> On Mon, Jan 16, 2017 at 10:29:39AM -0600, JR Richardson wrote:
>> Yes, I'm familiar with the methods sipcapture uses, I don't use HEP,
>> using raw socket capture, I think this may be a sipcapture issue,
>> debuging kamailio shows normal startup and processing of UDP SIP
>> packets, but does not
On Mon, Jan 16, 2017 at 10:29:39AM -0600, JR Richardson wrote:
> Yes, I'm familiar with the methods sipcapture uses, I don't use HEP,
> using raw socket capture, I think this may be a sipcapture issue,
> debuging kamailio shows normal startup and processing of UDP SIP
> packets, but does not show a
Hey Daniel,
Yes, I'm familiar with the methods sipcapture uses, I don't use HEP,
using raw socket capture, I think this may be a sipcapture issue,
debuging kamailio shows normal startup and processing of UDP SIP
packets, but does not show any activity with TCP packets. I have
enabled/disabled the
Hello,
is it this about a sipcature node? If yes, then it receives the packets
over HEP, meaning that is not going to the normal processing path.
Kamailio detects it is not a SIP packet, executes some callbacks for
non-sip packets registered by modules (in this case sipcapture). The
module detecti
What happens when you try:
modparam("sipcapture", "hep_capture_on", 1)
On 01/13/2017 10:33 AM, JR Richardson wrote:
> Iptables is not blocking, but it was worth a check.
>
> Thanks.
>
> JR
>
>
> I assume you have ruled out firewall? It's something that can nab even
> experienced people:
>
>
Iptables is not blocking, but it was worth a check.
Thanks.
JR
I assume you have ruled out firewall? It's something that can nab even
experienced people:
# iptables -Ln
-- Alex
On Thu, Jan 12, 2017 at 03:25:27PM -0600, JR Richardson wrote:
> Hi All,
>
> Just enabled SIP TCP on a homer capt
I assume you have ruled out firewall? It's something that can nab even
experienced people:
# iptables -Ln
-- Alex
On Thu, Jan 12, 2017 at 03:25:27PM -0600, JR Richardson wrote:
> Hi All,
>
> Just enabled SIP TCP on a homer capture server, I can see the SIP TCP
> Sessions on the server with ngr
12 matches
Mail list logo
