[asterisk-users] Asterisk Warning 2512

[Rizwan Hisham]

I just saw the sip debug and its showing that for every notify request,
asterisk is sending a bad request response.

here is the debug

<--- SIP read from 70.80.000.00:1031 --->
NOTIFY sip:69.90.111.11:9060 SIP/2.0
Via: SIP/2.0/UDP 70.80.000.00:1032;branch=z9hG4bK-ade549bd
From: Blake <sip:blakeday at 69.90.111.11 <sip%3Ablakeday at 69.90.111.11>
>;tag=90115683e082af23o0
To: <sip:69.90.111.11>
Call-ID: 966d3c03-ea9c07a3 at 10.4.1.22
CSeq: 7741 NOTIFY
Max-Forwards: 70
Event: keep-alive
User-Agent: Linksys/SPA2102-5.2.3
Content-Length: 0

<------------->
--- (10 headers 0 lines) ---
<--- Transmitting (no NAT) to 70.80.000.00:1031 --->
SIP/2.0 489 Bad event
Via: SIP/2.0/UDP 70.80.000.00:1032;branch=z9hG4bK-ade549bd;received=
70.80.000.00
From: Blake <sip:blakeday at 69.90.111.11 <sip%3Ablakeday at 69.90.111.11>
>;tag=90115683e082af23o0
To: <sip:69.90.111.11>;tag=as3ef6a439
Call-ID: 966d3c03-ea9c07a3 at 10.4.1.22
CSeq: 7741 NOTIFY
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0

Why is it doing so?

On Thu, Apr 17, 2008 at 2:36 AM, Tony Mountifield <tony at softins.clara.co.uk>
wrote:

> In article <4809880c0804170159l7f760673xf0d4eaac61025581 at mail.gmail.com>,
>  Rizwan Hisham <rizwanhasham at gmail.com> wrote:
> > I have been seeing a lot of the following warning messages on my
> asterisk
> > cli. Can naybody tell why these messages are showing up. I am using only
> SIP
> > to make calls from m asterisk.
> >
> > [Apr 17 04:52:24] WARNING[2512]: chan_sip.c:6480
> determine_firstline_parts:
> > Bad request protocol Bad event
> >
> > Also it will be great if anybody can tell where i can find the
> explanation
> > of all the warnig codes and error codes of asterisk if there is any.
>
> The [2512] is not a warning code. It is just the process ID of the
> Asterisk
> process or thread that generated the warning.
>
> The next part of your message (chan_sip.c:6480) shows the source file and
> line number where the error was generated. You can go to that point in
> the file to see what kind of checks it was making. You can also turn on
> SIP debugging at the Asterisk CLI> prompt to see the packets sent to/from
> Asterisk.
>
> Cheers
> Tony
> --
> Tony Mountifield
> Work: tony at softins.co.uk - http://www.softins.co.uk
> Play: tony at mountifield.org - http://tony.mountifield.org
>
> _______________________________________________
> -- 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
>



-- 
Best Regards
Rizwan Hisham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080417/30225051/attachment.htm