Menu
▾
▴
sipspy-users — SipSpy questions and answers
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: Tom v. d. G. <tom...@xs...> - 2009-09-22 11:16:22
|
Hi Elias, I was trying to compile spyAgent on Linux (Debian 4.0). Besides manually installing libev and the inclulded libpcap-0.8.1 it also required net/bpf.h as per include in commands.c. This file is not installed by default on Debian 4.0. Usually it's sufficient for libpcap to make a symbolic link from net/bpf.h -> pcap-bpf.h but in spyAgent it's missing the definition of BIOCIMMEDIATE which, for some reason, is not in the pcap-bpf.h. In this case I copied a bpf.h from another system to the target machine, which was sufficient to fix this issue. This dependency is most likely introduced in the 'recent' switch from poll -> libev Would it be a good idea to either: - check bpf.h in the confgure phase for the declaration of BIOCIMMEDIATE type - or include a fallback declaration - or remove the dependency - is there another (better) option? It might also be a good idea to include libev in the source, just like libpcap. Best regards, Tom |
|
From: Tom v. d. G. <tom...@xs...> - 2009-09-21 21:08:26
|
Hi Elias,
Please find attached a patch against the most recent version of spyAgent
in SVN. This only fixes the compact header for Call-ID ("i") and not for
any other compact headers.
I was wondering if you've tested replaying pcap files with the new libev
(using the -f option). In my case spyAgent keeps printing "one bpf !"
when sipSpy connects to the created "file" interface. It never stops.
The GUI (sipSpy) doesn't show any data. I can (privately) send you my
capture (pcap) file for you to test if you want...
Best regards,
Tom
-------- Originele bericht --------
Onderwerp: Re: [Sipspy-users] Compact header format
Van: elias baixas <eli...@vo...>
Aan: Tom van der Geer <tom...@xs...>
CC: sip...@li...
Datum: 21-9-2009 16:47
> Upps, you are right...
> I didn't account for the case of shortened headers... pleas send the
> patch and I'll commit it (or if you're interested in contributing more
> to SipSpy I can grant commit rights to you :D )
>
> Elias
>
>
> On 18/09/2009, at 9:11, Tom van der Geer wrote:
>
>> Hi,
>>
>> I'm using SipSpy in a test/development environment and found out that
>> spyAgent rejects SIP messages with a "no callid" error when it received
>> SIP messages that are using the compact header format for the Call-ID.
>> Some endpoints use 'i' in stead of the full 'Call-ID' header name. As
>> specified in the SIP RFC 3261 paragraph 7.3.3 and section 20(.8)
>>
>> I've created a patch for this. Is anybody interested in this? Please
>> reply!
>>
>> Best regards,
>>
>> Tom
>>
>> ------------------------------------------------------------------------------
>>
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Sipspy-users mailing list
>> Sip...@li...
>> https://lists.sourceforge.net/lists/listinfo/sipspy-users
>
|
|
From: elias b. <eli...@vo...> - 2009-09-21 15:29:02
|
Upps, you are right... I didn't account for the case of shortened headers... pleas send the patch and I'll commit it (or if you're interested in contributing more to SipSpy I can grant commit rights to you :D ) Elias On 18/09/2009, at 9:11, Tom van der Geer wrote: > Hi, > > I'm using SipSpy in a test/development environment and found out that > spyAgent rejects SIP messages with a "no callid" error when it > received > SIP messages that are using the compact header format for the Call-ID. > Some endpoints use 'i' in stead of the full 'Call-ID' header name. As > specified in the SIP RFC 3261 paragraph 7.3.3 and section 20(.8) > > I've created a patch for this. Is anybody interested in this? Please > reply! > > Best regards, > > Tom > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Sipspy-users mailing list > Sip...@li... > https://lists.sourceforge.net/lists/listinfo/sipspy-users |
|
From: Tom v. d. G. <tom...@xs...> - 2009-09-18 07:12:07
|
Hi, I'm using SipSpy in a test/development environment and found out that spyAgent rejects SIP messages with a "no callid" error when it received SIP messages that are using the compact header format for the Call-ID. Some endpoints use 'i' in stead of the full 'Call-ID' header name. As specified in the SIP RFC 3261 paragraph 7.3.3 and section 20(.8) I've created a patch for this. Is anybody interested in this? Please reply! Best regards, Tom |
|
From: Alscion M. <als...@gm...> - 2008-01-09 10:19:10
|
Hi, I've an error when I try to change the listening device on my admin console, somebody has ever add the same? Here is the log on spyAgent : New client's device eth2 Opening device "eth2" for capture, with filter ""... Setting filter: [not src port 23332 and ()] Error (syntax error) in pcap_compile Error device: (filter error) Error executing command device with args:[eth2] Thx. |
|
From: Elias B. <eli...@vo...> - 2007-07-19 11:22:50
|
Hi ! does this work ? |
