New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
do not fragment flag #1510
Comments
example of INVITE with |
This is not something done in Kamailio, but more about the tcp/os stack implementation. Usually tcp sends with do not fragment flag set in order to adapt to the largest MTU that can be used on the path. Not aware if this is something that can be configured at OS level, but I checked kamailio tcp code and there is no such flag set. If you want to discuss more, bring this topic to sr-users, there might be other people that know more about system options/how to tune this. |
As I get it from that article, then it can be controlled at OS level via:
|
looks as
do not fragment
flag is applied to TCP transport by defaultLater will test on default config.
The text was updated successfully, but these errors were encountered: