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
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
Have a look at this:
http://bugs.digium.com/view.php?id=7261&nbn=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 --s
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>
>
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
>> <
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 proto
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 rea
