Re: [asterisk-users] Cirpack KeepAlive packets causing SIP errors

2007-12-29 Thread Michiel van Baak
On 19:32, Sat 29 Dec 07, Jaap Winius wrote:
 Hi list,
 
 After a recent upgrade to Asterisk v1.4.14, my message log is now  
 filling up with
 the following error messages:
 
 -
 [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645  
 determine_firstline_parts: Bad request protocol Packet
 --- (1 headers 0 lines) ---
 bitis*CLI
 --- SIP read from 82.101.62.99:5060 ---
 Cirpack KeepAlive Packet
 -
 
 Seeing as these packets are being sent by one of my service providers,  
 I can't just turn them off. What's the best solution for this problem?

Are you using XS4ALL ?
I had the same and convinced oej those warnings are
annoying.
In trunk he moved them to DEBUG:
http://svn.digium.com/view/asterisk?view=revrevision=93741
Maybe you can backport this change.
You can also remove the ast_log line. That's what I've been
doing for some time before oej committed this move to debug.

-- 

Michiel van Baak
[EMAIL PROTECTED]
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x71C946BD

Why is it drug addicts and computer afficionados are both called users?


___
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Cirpack KeepAlive packets causing SIP errors

2007-12-29 Thread Jaap Winius
Quoting Michiel van Baak [EMAIL PROTECTED]:

 -
 [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645
 determine_firstline_parts: Bad request protocol Packet
 --- (1 headers 0 lines) ---
 bitis*CLI
 --- SIP read from 82.101.62.99:5060 ---
 Cirpack KeepAlive Packet
 -

 Are you using XS4ALL ?

Yes, although currently I'm mostly using InternetCalls for SIP. But I  
think these packets are indeed coming from a host  
(b3g6-nl.sip.b3g-telecom.com) associated with XS4ALL's VoIP service.

 http://svn.digium.com/view/asterisk?view=revrevision=93741
 Maybe you can backport this change.

Sounds like a good idea, but I'm having trouble getting the source  
code for Debian etch from xorcom.com to compile regardless. After  
attempting to compile with dpkg-buildpackage -rfakeroot -uc -b, it  
soon errors out with:

Patch bristuff/ast-send-message does not remove cleanly \
(refresh it or enforce with -f)
make: *** [unpatch] Error 1

Have I forgotten something?

Thanks,

Jaap


___
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Cirpack KeepAlive packets causing SIP errors

2007-12-29 Thread Tzafrir Cohen
On Sat, Dec 29, 2007 at 10:12:27PM +0100, Jaap Winius wrote:
 Quoting Michiel van Baak [EMAIL PROTECTED]:
 
  -
  [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645
  determine_firstline_parts: Bad request protocol Packet
  --- (1 headers 0 lines) ---
  bitis*CLI
  --- SIP read from 82.101.62.99:5060 ---
  Cirpack KeepAlive Packet
  -
 
  Are you using XS4ALL ?
 
 Yes, although currently I'm mostly using InternetCalls for SIP. But I  
 think these packets are indeed coming from a host  
 (b3g6-nl.sip.b3g-telecom.com) associated with XS4ALL's VoIP service.
 
  http://svn.digium.com/view/asterisk?view=revrevision=93741
  Maybe you can backport this change.
 
 Sounds like a good idea, but I'm having trouble getting the source  
 code for Debian etch from xorcom.com to compile regardless. After  
 attempting to compile with dpkg-buildpackage -rfakeroot -uc -b, it  
 soon errors out with:
 
 Patch bristuff/ast-send-message does not remove cleanly \
 (refresh it or enforce with -f)
 make: *** [unpatch] Error 1
 
 Have I forgotten something?

Have you made any changes in the source? They probably touch one of the
existing patches.

You can try to use quilt to make those changes as an extra patch.

-- 
   Tzafrir Cohen
icq#16849755  jabber:[EMAIL PROTECTED]
+972-50-7952406   mailto:[EMAIL PROTECTED]
http://www.xorcom.com  iax:[EMAIL PROTECTED]/tzafrir

___
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Cirpack KeepAlive packets causing SIP errors

2007-12-29 Thread LInux
Have a look at this:

http://bugs.digium.com/view.php?id=7261nbn=6

If you are running on linux (with a recent kernel), add the iptables 
firewall rule to drop the bad packets:

# drop Keep Alive packets from Cirpack SIP proxy xs4all
/sbin/iptables -A INPUT -p udp -m udp --dport 5060 -m string --string 
Cirpack KeepAlive Packet --algo bm -j DROP

Worked for me.

Hans


Jaap Winius wrote:
 Hi list,

 After a recent upgrade to Asterisk v1.4.14, my message log is now  
 filling up with
 the following error messages:

 -
 [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645  
 determine_firstline_parts: Bad request protocol Packet
 --- (1 headers 0 lines) ---
 bitis*CLI
 --- SIP read from 82.101.62.99:5060 ---
 Cirpack KeepAlive Packet
 -

 Seeing as these packets are being sent by one of my service providers,  
 I can't just turn them off. What's the best solution for this problem?

 Thanks,

 Jaap


 ___
 --Bandwidth and Colocation Provided by http://www.api-digital.com--

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
   


___
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Cirpack KeepAlive packets causing SIP errors

2007-12-29 Thread Michiel van Baak
On 22:12, Sat 29 Dec 07, Jaap Winius wrote:
 Quoting Michiel van Baak [EMAIL PROTECTED]:
 
  -
  [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645
  determine_firstline_parts: Bad request protocol Packet
  --- (1 headers 0 lines) ---
  bitis*CLI
  --- SIP read from 82.101.62.99:5060 ---
  Cirpack KeepAlive Packet
  -
 
  Are you using XS4ALL ?
 
 Yes, although currently I'm mostly using InternetCalls for SIP. But I  
 think these packets are indeed coming from a host  
 (b3g6-nl.sip.b3g-telecom.com) associated with XS4ALL's VoIP service.
 
  http://svn.digium.com/view/asterisk?view=revrevision=93741
  Maybe you can backport this change.
 
 Sounds like a good idea, but I'm having trouble getting the source  
 code for Debian etch from xorcom.com to compile regardless. After  
 attempting to compile with dpkg-buildpackage -rfakeroot -uc -b, it  
 soon errors out with:
 
 Patch bristuff/ast-send-message does not remove cleanly \
 (refresh it or enforce with -f)
 make: *** [unpatch] Error 1
 
 Have I forgotten something?

I have no idea.
I use asterisk sources from svn.digium.com for all my
installs. Most are 1.4 and some are trunk.
I think tzafrir is the one to help you here as he is more
familiar with the xorcom packages and with building debian
packages in general.

-- 

Michiel van Baak
[EMAIL PROTECTED]
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x71C946BD

Why is it drug addicts and computer afficionados are both called users?


___
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Cirpack KeepAlive packets causing SIP errors

2007-12-29 Thread Jaap Winius
Quoting Michiel van Baak [EMAIL PROTECTED]:

 Sounds like a good idea, but I'm having trouble getting the source
 code for Debian etch from xorcom.com to compile regardless.

 I have no idea.

I got it to compile. My mistake; I had attempted to modify chan_sip.c  
directly. It then refused to compile, but it also continued to after I  
had restored the original file, which threw me off. After a fresh  
download it compiled without any problems. I'll have to see if I can  
alter the code using quilt, as Tzafrir suggested, but otherwise I'll  
just follow Hans' advice and drop the incoming packets with this  
iptables rule:

# drop Keep Alive packets from Cirpack SIP proxy xs4all
/sbin/iptables -A INPUT -p udp -m udp --dport 5060 -m string --string
Cirpack KeepAlive Packet --algo bm -j DROP

(Thanks, Hans!)

Cheers,

Jaap

___
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users