11 Oct
2005
11 Oct
'05
3:09 p.m.
ngrep -W byline [calling-number] port 5060 -q
It works to me..
Regards,
Ricardo Martinez.-
-----Mensaje original-----
De: Iqbal [mailto:iqbal@gigo.co.uk]
Enviado el: Martes, 11 de Octubre de 2005 14:46
Para: Klaus Darilion
CC: serusers(a)lists.iptel.org
Asunto: Re: [Serusers] logging of SIP dialog
Hi
Is there any easy way of matching all messages belonging to a call in
ngrep, aside from pulling out the call-id and the grepping
for all those
which match that call-id...I am guessing not...
iqbal
Klaus Darilion wrote:
sufficient I you
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
We use the low-level approach:
-exec rm {} \;
crontab -l
# purge SIP packet sniffs
35 5 * * * find /export/sipsniff -name pack\* -mtime +60 cat /usr/local/bin/sipsniff
#!/bin/sh
FILES=/export/sipsniff/packets
while true; do
FILESUFFIX=`date +%Y%m%d-%H%M%S`
/usr/bin/tethereal -i any -a filesize:256 -n -w $FILES.$FILESUFFIX
port 5060 or port 5061
done;
This is not very convenient for daily debugging, but debug once a month.
regards
klaus
Iqbal wrote:
> Hi
>
> Has anyone come up with a scalable method to log the complete SIP
> trace of ALL calls, i.e to separate files etc
> Ngrep is greate for a few, but I want to be able to track
all calls,
for
various purposes
Iqbal
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
.