[Serusers] logging of SIP dialog
Iqbal
iqbal at gigo.co.uk
Tue Oct 11 20:43:21 CEST 2005
tks, but I need to pull all data for all calls, and then disect them
later for graphing (oh I wish).
Iqbal
Ricardo Martinez wrote:
>ngrep -W byline [calling-number] port 5060 -q
>
>It works to me..
>Regards,
>
>Ricardo Martinez.-
>
>
>
>
>>-----Mensaje original-----
>>De: Iqbal [mailto:iqbal at gigo.co.uk]
>>Enviado el: Martes, 11 de Octubre de 2005 14:46
>>Para: Klaus Darilion
>>CC: serusers at 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:
>>
>>
>>
>>>We use the low-level approach:
>>>
>>>
>>>
>>>>crontab -l
>>>>
>>>>
>>># purge SIP packet sniffs
>>>35 5 * * * find /export/sipsniff -name pack\* -mtime +60
>>>
>>>
>>-exec rm {} \;
>>
>>
>>>>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
>>>
>>>
>>sufficient I you
>>
>>
>>>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 at lists.iptel.org
>>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>>
>>>>
>>>>
>>>>
>>>.
>>>
>>>
>>>
>>_______________________________________________
>>Serusers mailing list
>>serusers at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>>
>
>.
>
>
>
More information about the sr-users
mailing list