Re: [SR-Users] TCP reset behavior

2019-06-12 Thread Daniel-Constantin Mierla
thanks, > > raj > >   > > *From:*Daniel-Constantin Mierla > *Sent:* Wednesday, June 12, 2019 1:36 PM > *To:* R, Rajkumar (Raj) ; Kamailio (SER) - > Users Mailing List > *Subject:* Re: [SR-Users] TCP reset behavior > >   > > If it is established, then

Re: [SR-Users] TCP reset behavior

2019-06-12 Thread R, Rajkumar (Raj)
) - Users Mailing List Subject: Re: [SR-Users] TCP reset behavior If it is established, then the other side didn't actually requested the close of the connection. It should be in close-wait state when the remote peer sent the close request. Look at the traffic of the connection with wireshare

Re: [SR-Users] TCP reset behavior

2019-06-12 Thread Daniel-Constantin Mierla
  > ESTABLISHED 20/Kamailio > >   > >   > >   > > thanks, > > raj > > +918067153382 > >   > > *From:*Daniel-Constantin Mierla > *Sent:* Wednesday, June 12, 2019 12:29 PM > *To:* R, Rajkumar (Raj) ; Kamailio (SER) - > Users Mailing List

Re: [SR-Users] TCP reset behavior

2019-06-12 Thread R, Rajkumar (Raj)
) ; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] TCP reset behavior Hello, the connection state is OK in all outputs, so not seen as closed by Kamailio. Can you get the output of the netstat for that connection after is supposed to be closed to see its state there? Cheers, Daniel

Re: [SR-Users] TCP reset behavior

2019-06-12 Thread Daniel-Constantin Mierla
shared tcp stats help?  Awaiting your inputs on this. >> >>   >> >> thanks, >> >> raj >> >>   >> >>   >> >> *From:*sr-users *On Behalf Of >> *R, Rajkumar (Raj) >> *Sent:* Friday, June 7, 2019 10:44 PM >> *

Re: [SR-Users] TCP reset behavior

2019-06-11 Thread Daniel-Constantin Mierla
g your inputs on this. > >   > > thanks, > > raj > >   > >   > > *From:*sr-users *On Behalf Of > *R, Rajkumar (Raj) > *Sent:* Friday, June 7, 2019 10:44 PM > *To:* mico...@gmail.com; Kamailio (SER) - Users Mailing List > > *Subject:* Re: [SR-Users]

Re: [SR-Users] TCP reset behavior

2019-06-10 Thread R, Rajkumar (Raj)
Did the shared tcp stats help? Awaiting your inputs on this. thanks, raj From: sr-users On Behalf Of R, Rajkumar (Raj) Sent: Friday, June 7, 2019 10:44 PM To: mico...@gmail.com; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] TCP reset behavior Hi Daniel, Please find attached

Re: [SR-Users] TCP reset behavior

2019-06-07 Thread R, Rajkumar (Raj)
kamailio for about 15 minutes until connection release. thanks, raj From: Daniel-Constantin Mierla Sent: Friday, June 7, 2019 6:14 PM To: Kamailio (SER) - Users Mailing List ; R, Rajkumar (Raj) Subject: Re: [SR-Users] TCP reset behavior Hello, can you reproduce the case and then get

Re: [SR-Users] TCP reset behavior

2019-06-07 Thread Daniel-Constantin Mierla
Hello, can you reproduce the case and then get the output of the next commands: kamctl rpc core.tcp_list kamctl rpc core.tcp_options kamctl rpc core.tcp_info Cheers, Daniel On 06.06.19 18:53, R, Rajkumar (Raj) wrote: > > Hi All, > >   > > In our setup running kamailio (alpine image) in

[SR-Users] TCP reset behavior

2019-06-06 Thread R, Rajkumar (Raj)
Hi All, In our setup running kamailio (alpine image) in stateless mode and have following TCP config set. After client registers to the backend see two TCP connections created - one towards the client and the other towards the backendserver. If there's a abrupt network disconnect either at