Adjustable T1, T2 and T4 timeouts about sipgo HOT 5 CLOSED

I would not go with this func. I would still like to know some use case of changing this values from default one?
Exposing just with var for me is enough, if someone needs to change one timer, he should look others as well.

from sipgo.

I would still like to know some use case of changing this values from default one?

T1 is an estimate of RTT and it should be quite different when you connect to a node in the same data center or to a node on another continent. In the former case it should retry (and eventually fail and do failover) much earlier.

It's not that important for my current project, where I'm trying to go with sipgo. 500 ms is OK in this case. But there might be cases when it's a big deal.

I would not go with this func.

Yeah, it doesn't look nice. I just can't come up with a better way now. Maybe, introducing more ClientRequestOption for timers will be better.

from sipgo.

thnx for sharing. Sure T1 is most important. So it is more I want to change T1 and let others be populated.

Maybe we can have this to be populated on package level
SetT1 SetT2 etc..

Let me know would this be enough. We can always export all timers, but maybe for now keeping package API small?

from sipgo.

This waits too long. Adding priority

from sipgo.

@a12n was delayed, but done.

from sipgo.