Skip to content

Conversation

@j-licht
Copy link
Contributor

@j-licht j-licht commented Dec 1, 2025

add read and write deadline for tcp transport, otherwise it takes a long time to detect offline devices.

@emiago
Copy link
Owner

emiago commented Dec 6, 2025

I guess main issue could be now for client usage as you need to have this connection upfront.

I find this very hardcoded. Could maybe TCP keep alive solve problem?

@j-licht
Copy link
Contributor Author

j-licht commented Dec 8, 2025

I guess main issue could be now for client usage as you need to have this connection upfront.

What do you mean?

I find this very hardcoded. Could maybe TCP keep alive solve problem?

With keepalive enabled I'm still seeing the sip request are blocking.
What do you think about having an WithOptionSetDeadline to configure that?

@emiago
Copy link
Owner

emiago commented Dec 10, 2025

Hi @j-licht . Right now you can customize transports trhough TransportsConfig which can be passed through UA on TransportLayer.
What we basically need is to add those options somowhere in tcp transport.
On other hand, lib is moving right now to 1.0.0, and this may be delayed to 1.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants