Re: [SR-Users] t_set_fr() different behavior whether transport is udp or tcp

2016-08-16 Thread Daniel Tryba
On Tue, Aug 16, 2016 at 04:14:15PM +0200, Olle E. Johansson wrote: > > I'm seeing a different behavior of t_set_fr depending on transports. > Which is correct. UDP is connectionless and thus SIP has timers for > retransmits and fails when there’s no response. With connection-oriented > protocols,

Re: [SR-Users] t_set_fr() different behavior whether transport is udp or tcp

2016-08-16 Thread Olle E. Johansson
> On 16 Aug 2016, at 11:41, Daniel Tryba wrote: > > I'm seeing a different behavior of t_set_fr depending on transports. Which is correct. UDP is connectionless and thus SIP has timers for retransmits and fails when there’s no response. With connection-oriented protocols, the failure happens wh

[SR-Users] t_set_fr() different behavior whether transport is udp or tcp

2016-08-16 Thread Daniel Tryba
I'm seeing a different behavior of t_set_fr depending on transports. Scenario is that a endpoint has a failover defined in the registrat after 10s (t_set_fr(1) and handling the locally generated 408 to the failover destination). This works fine when the request and response where delivered over