Summary:ASTERISK-12423: SIP/2.0 400 SIP Parser Error : Missing '@', line 3, column 26
Reporter:Steven Anderson (tkfast)Labels:
Date Opened:2008-07-21 10:43:30Date Closed:2011-06-07 14:00:21
Versions:Frequency of
Description:Linksys WIP330 Phones cause Sip Parse Errors and Crash Asterisk Completely, It crashes most when you get a new incoming call then it will show No Caller ID you will have silence on both ends of the line.
Then you have to restart asterisk, sometimes it will lock up asterisk where you can't even do a stop now and you have to kill the process. When this happens is throws errors like this.
SIP/2.0 400 SIP Parser Error : Missing '@', line 3, column 26

If you turn off the Wip330 phone the systems work great. So I know it is directly related to how theses register with SIP.

Occurring on Multiple Server Running Different Versions of Asterisk.


<--- SIP read from --->
SIP/2.0 400 SIP Parser Error : Missing '@', line 3, column 26
From: "No CallID" ;tag=as678f21e5
Call-ID: 5848a4a725494e8c0bdd274e15c14ecc@
Via: SIP/2.0/UDP;rport=5060;branch=z9hG4bK7d9f6686
User-Agent: Asterisk PBX
Max-Forwards: 70
Supported: replaces
Date: Tue, 15 Jul 2008 22:16:25 GMT
Content-Length: 0


[May 16 22:08:00] WARNING[14761]: chan_sip.c:6772 determine_firstline_parts: Bad request protocol SIP Parser Error : Missing '@', line 3, column 26
[May 16 22:08:00] NOTICE[14761]: chan_sip.c:15379 handle_request: Unknown SIP command '2070SIP/2.0' from ''
-- Got SIP response 400 "SIP Parser Error : Missing '@', line 3, column 26" back from
[May 16 22:08:04] NOTICE[14761]: chan_sip.c:15766 sip_poke_noanswer: Peer '104' is now UNREACHABLE! Last qualify: 409

I have also tried to see if it does it on the follow versions of asterisk and it does the same thing.


OS Used: Debian Etch
Comments:By: Russell Bryant (russell) 2008-07-21 16:27:43

Does it actually crash?  Based on your description, it sounds like it is locking up.

Build with DEBUG_THREADS enabled, and when it locks up, grab the output of "core show locks".

# asterisk -rx "core show locks" > lock.txt

and upload that file here.

By: Olle Johansson (oej) 2008-07-25 04:46:06

Note this: Unknown SIP command '2070SIP/2.0' from '

Over UDP, that's weird.

By: Olle Johansson (oej) 2008-07-25 04:47:26

We need to see the full dialog, what the Linksys sends too (see the bug guidelines). Obiously the packet coming in has some issues.

By: Russell Bryant (russell) 2008-07-31 14:18:22

I tried sending the message quoted in the bug report into chan_sip and I don't get an error message when parsing it.  Also, based on your error messages, it seems like what actually go received isn't quite what was sent.  A real packet capture using wireshark or tcpdump would be even more useful.

By: Jason Parker (jparker) 2008-08-13 15:38:05

Closing.  There hasn't been any response from the reporter since this was opened.  We'd like to get to the bottom of this, but without the requested logs that's going to be nearly impossible.

Please reopen this issue once you are able to provide what is needed.