[SR-Users] Not able to connect kamailio via SIP Client

Daniel-Constantin Mierla miconda at gmail.com
Thu Feb 21 16:30:39 CET 2019


On 21.02.19 16:14, Daniel Tryba wrote:
> On Thu, Feb 21, 2019 at 04:55:40PM +0530, Prabhat Kumar wrote:
>> When i try to login via SIP Client(zoiper) i am getting the following error.
>>
>> Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: INFO:
>> <core> [core/parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR:
>> <core> [core/parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR:
>> <core> [core/parser/msg_parser.c:675]: parse_msg(): ERROR: parse_msg:
>> message=<???#007???>
>> Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR:
>> <core> [core/receive.c:199]: receive_msg(): core parsing of SIP
>> message failed (114.241.140.68:4569/1)
>>
>>
>> How can i fix this problem?
> By learning how to debug problems.
>
> Read the error: 
> parse_first_line: method not followed by SP
> parse_first_line: bad message (offset: 0)
>
> So there is something wrong with the message (esp. the first line)
> somehow. Now use tools to capture this message (tcpdump/ngrep/wireshark)
> and check if there is something wrong with the message (read the related
> SIP RFCs to figure out how the message should look). The error mentions
> "method not followed by SP(ace?)". So what does the first line look
> like?
>
> If the message is bad, fix the client.  If the message isn't, you either
> have found a kamailio bug or more likely made a mistake in your config.
> Either way, enable more logging for debugging.
> https://www.kamailio.org/dokuwiki/doku.php/tutorials:debug-syslog-messages
> gives some info. If you still need help, then give the relevant input and
> config.

To add my opinion here: it seems that binary data is sent to the SIP
port, it could be STUN, TLS pointed to a TCP port or some other type of
data sent to the wrong port due to some misconfiguration.

Try to watch the traffic coming from 114.241.140.68 to your sip server
with wireshark, tcpdump, ... and maybe you can figure out what data is
sent there.

Cheers,
Daniel


-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com




More information about the sr-users mailing list