Re: [asterisk-dev] Chan_pjsip keep_alive_interval

2016-11-09 Thread Joshua Colp
On Wed, Nov 9, 2016, at 02:22 PM, Ross Beer wrote: > Hi Joshua, > > > Looking at traces, there are packets being sent with length 4. These show > as PSH, ACK in a Wireshark. However, in TLS I don't see any such packets > which I believe is the cause of the TLS connection is being closed. > > >

Re: [asterisk-dev] Chan_pjsip keep_alive_interval

2016-11-09 Thread Ross Beer
transports? Kind regards, Ross From: asterisk-dev-boun...@lists.digium.com <asterisk-dev-boun...@lists.digium.com> on behalf of Joshua Colp <jc...@digium.com> Sent: 09 November 2016 17:48 To: asterisk-dev@lists.digium.com Subject: Re: [asterisk-dev

Re: [asterisk-dev] Chan_pjsip keep_alive_interval

2016-11-09 Thread Joshua Colp
On Wed, Nov 9, 2016, at 01:25 PM, Ross Beer wrote: > Hi, > > > I'm investigating an issue where TLS connections close with a 'RST' after > a random period of time. > > > I can see that PJSIP sets 'PJSIP_TRANSPORT_IDLE_TIME=600', with the > option in pjsip.conf 'keep_alive_internal' set, does

[asterisk-dev] Chan_pjsip keep_alive_interval

2016-11-09 Thread Ross Beer
Hi, I'm investigating an issue where TLS connections close with a 'RST' after a random period of time. I can see that PJSIP sets 'PJSIP_TRANSPORT_IDLE_TIME=600', with the option in pjsip.conf 'keep_alive_internal' set, does this set both 'PJSIP_TCP_KEEP_ALIVE_INTERVAL' and