Difference between revisions of "Determine firstline parts: Bad request protocol Packet"

From Kolmisoft Wiki
Jump to navigationJump to search
(New page: If youc have a lot of messages: [Aug 6 17:45:54] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet [Aug 6 17:45:58] WARNING[30322]: chan_sip.c:6713 ...)
 
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
If youc have a lot of messages:
If you have a lot of messages:


[Aug  6 17:45:54] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:54] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:58] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:58] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:59] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:59] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet


That's buggy Cirpak, read:  http://lists.digium.com/pipermail/asterisk-users/2008-February/205617.html
That's buggy Cirpack, read:  http://lists.digium.com/pipermail/asterisk-users/2008-February/205617.html
 
===Solution:===
 
Add to iptables such 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
 
More details: http://www.mail-archive.com/asterisk-users@lists.digium.com/msg196091.html

Latest revision as of 12:27, 9 December 2008

If you have a lot of messages:

[Aug  6 17:45:54] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:58] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet
[Aug  6 17:45:59] WARNING[30322]: chan_sip.c:6713 determine_firstline_parts: Bad request protocol Packet

That's buggy Cirpack, read: http://lists.digium.com/pipermail/asterisk-users/2008-February/205617.html

Solution:

Add to iptables such 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

More details: http://www.mail-archive.com/asterisk-users@lists.digium.com/msg196091.html