There is no problem as such.
On Sat, Mar 24, 2012 at 5:20 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
>
> On 3/23/12 3:15 PM, Jijo wrote:
>
> Hello,
>
> Yes it is sending CRLF after the second CRLF from client.
>
> Another thing is, Kamailio would send CRLF even if the second CRLF come
> a
Hello,
On 3/23/12 3:15 PM, Jijo wrote:
Hello,
Yes it is sending CRLF after the second CRLF from client.
Another thing is, Kamailio would send CRLF even if the second CRLF
come after few seconds.
I believe we don't have any way to drop it ?
not really, in a stream protocol, such delays can
Hello,
Yes it is sending CRLF after the second CRLF from client.
Another thing is, Kamailio would send CRLF even if the second CRLF come
after few seconds.
I believe we don't have any way to drop it ?
Thanks
Jijo
On Fri, Mar 23, 2012 at 5:34 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
>
Hello,
is kamailio sending crlf after the second crlf from the client?
There is no notion of a packet in a stream connection, even a sip packet
can be send char by char and the server has to assemble it by keep
reading in a local buffer until all is retrieved.
Cheers,
Daniel
On 3/23/12 1:50
Hi
Sorry for the late reply,
I observed this issue when testing with broken TLS UA, which was sending
CRLF in two packets instead of double CRLF in a single packet.
It is very easy to recreate using openssl s_client command , where kamailio
as server
openssl s_client -connect 192.168.2.151:506
Hello,
looking at the code, it seems that CRLF is sent only after CRLFCRLF. Can
you get a pcap for your case?
Cheers,
Daniel
On Tue, Feb 28, 2012 at 5:28 PM, Jijo wrote:
> Hi All.
>
> As per the tcp_crlf_ping description, kamailio shall reply CRLF only when
> it receives "CRLF CRLF". But In t
Hi All.
As per the tcp_crlf_ping description, kamailio shall reply CRLF only when
it receives "CRLF CRLF". But In the 3.1.0 version, if kamailio recieves
"CRLF", it respond back CRLF. Is this an expected behavior or an error?
Thanks
Jijo
___
SIP Expre
