[Home]

Summary:ASTERISK-07073: chan_sip can't handle Cirpack KeepAlive Packets
Reporter:micled (micled)Labels:
Date Opened:2006-06-01 08:02:53Date Closed:2006-06-01 11:26:20
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hello,

I am using asterisk on linux in France.

I have a message in permance :
WARNING[30888]: chan_sip.c:5206 determine_firstline_parts: Bad request protocol Packet

When i set debug :
<-- SIP read from xxx:5060:
Cirpack KeepAlive Packet
Jun  1 15:00:59 WARNING[30888]: chan_sip.c:5206 determine_firstline_parts: Bad request protocol Packet
--- (1 headers 0 lines)---

i don't known if it is a bug but this message is every 2 second and is fulling my logs.

Excuse for my english i'm french.

Comments:By: Olle Johansson (oej) 2006-06-01 08:30:15

It *is* a bad request packet, so the error message is correct. What is the problem you are reporting here?

By: Olle Johansson (oej) 2006-06-01 08:30:37

Turn off keep alives from the server.

By: micled (micled) 2006-06-01 09:12:50

I can not turn off keep alives from the server because the server is a FAI (Internet Provider) and i am a client of this server.

Can I turn off this error ?

I think that the server use another SIP server. Or this other send keep alive packet that asterisk don't known. It is possible to add an option to asterisk to understant this packet ?

Thank

By: Olle Johansson (oej) 2006-06-01 09:54:17

Well, we have as a policy not to fix problems with other UAs that are broken and not follow the specs. This is clearly such a case. We're just logging these errors. What you can do is go into the source code and remove that warning, recompile, reinstall.

By: Jeffrey C. Ollie (jcollie) 2006-06-01 10:19:36

If you are running Linux and have a relatively recent kernel you can do something like this:

iptables -A INPUT -p udp -m udp --dport 5060 -m string --string "Cirpack KeepAlive Packet" -j DROP

By: Olle Johansson (oej) 2006-06-01 11:26:19

Ok, we suggested several ways to solve the issue. Again, since I don't see this as a bug in Asterisk, we will not act on this repot. Thanks for reporting!