On Wed, Oct 20, 2021 at 3:30 PM jacky z wrote:
> We found most of the time, it follows a global (per process) buff and is
> followed by a per connection buff and then the message is read.
>
>
try to do a tcpdump on that interface/port, then wireshark the pcap, you
will see what opensips see
eg:
We found most of the time, it follows a global (per process) buff and is
followed by a per connection buff and then the message is read.
Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]:
DBG:proto_tls:tls_read_req: *Using the global ( per process ) buff *
Oct 19 13:34:32 sipserver /usr/sbin/ope
Thanks! We found an end point sent an INVITE, but the server did not
receive. The time of this message in the opensips log matched the INVITE.
Not sure whether the INVITE message failed to be read for whatever reason.
Then we checked the server and found a lot of such messages. The server is
a stil
On Wed, Oct 20, 2021 at 11:00 AM jacky z wrote:
>
> Recently checked the log and found a lot of items.
>
> DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request
>
> Does this mean that there is an incoming message but the server can't read
> it successfully? What can induce this p
Hi Team,
Recently checked the log and found a lot of items.
DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request
Does this mean that there is an incoming message but the server can't read
it successfully? What can induce this problem? Thanks!
Regards,
Jacky
