Hi All.
Today I have problem with connection from 1 of the clients. Their PBX sends KEEP-ALIVE after some time after REGISTER.
I have next error in kamailio log
Feb 28 14:26:19 sbc2 /usr/sbin/kamailio[3657]: ERROR: <core> [tcp_read.c:1354]: tcp_read_req(): bad request, state=7, error=4 buf:#012KEEP-ALIVE sip:1.2.3.4 SIP/2.0#015#012#015#012#012parsed :#012KEEP-ALIVE sip:1.2.3.4 SIP/2.0
After which my kamailio closes TCP session....
This connection is done with sip TLS.
Thank you in advance.
-- Best regards, Sergey Basov e-mail: sergey.v.basov@gmail.com
Hello,
On 28/02/2017 17:05, Sergey Basov wrote:
Hi All.
Today I have problem with connection from 1 of the clients. Their PBX sends KEEP-ALIVE after some time after REGISTER.
I have next error in kamailio log
Feb 28 14:26:19 sbc2 /usr/sbin/kamailio[3657]: ERROR: <core> [tcp_read.c:1354]: tcp_read_req(): bad request, state=7, error=4 buf:#012KEEP-ALIVE sip:1.2.3.4 SIP/2.0#015#012#015#012#012parsed :#012KEEP-ALIVE sip:1.2.3.4 SIP/2.0
After which my kamailio closes TCP session....
This connection is done with sip TLS.
Is that message a single line like next?
KEEP-ALIVE sip:1.2.3.4 SIP/2.0
If yes, this is not a valid SIP message, because it lacks mandatory headers such as call-id, cseq, from/to.
Cheers, Daniel
Hi, Daniel
Yes it is without any headers... I have attached screenshot from wireshark, I can not save it because this is sip tls...
Thank you -- Best regards, Sergey Basov e-mail: sergey.v.basov@gmail.com
2017-03-01 15:57 GMT+02:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
On 28/02/2017 17:05, Sergey Basov wrote:
Hi All.
Today I have problem with connection from 1 of the clients. Their PBX sends KEEP-ALIVE after some time after REGISTER.
I have next error in kamailio log
Feb 28 14:26:19 sbc2 /usr/sbin/kamailio[3657]: ERROR: <core> [tcp_read.c:1354]: tcp_read_req(): bad request, state=7, error=4 buf:#012KEEP-ALIVE sip:1.2.3.4 SIP/2.0#015#012#015#012#012parsed :#012KEEP-ALIVE sip:1.2.3.4 SIP/2.0
After which my kamailio closes TCP session....
This connection is done with sip TLS.
Is that message a single line like next?
KEEP-ALIVE sip:1.2.3.4 SIP/2.0
If yes, this is not a valid SIP message, because it lacks mandatory headers such as call-id, cseq, from/to.
Cheers, Daniel
-- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
2017-03-01 15:48 GMT+01:00 Sergey Basov sergey.v.basov@gmail.com:
2017-03-01 15:57 GMT+02:00 Daniel-Constantin Mierla miconda@gmail.com:
If yes, this is not a valid SIP message, because it lacks mandatory headers such as call-id, cseq, from/to.
Yes it is without any headers...
So is not a valid SIP message
Thank you for clarification. -- Best regards, Sergey Basov e-mail: sergey.v.basov@gmail.com
2017-03-01 20:05 GMT+02:00 Victor Seva linuxmaniac@torreviejawireless.org:
2017-03-01 15:48 GMT+01:00 Sergey Basov sergey.v.basov@gmail.com:
2017-03-01 15:57 GMT+02:00 Daniel-Constantin Mierla miconda@gmail.com:
If yes, this is not a valid SIP message, because it lacks mandatory headers such as call-id, cseq, from/to.
Yes it is without any headers...
So is not a valid SIP message
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users