Enable SIP tracing on support session events #46
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trigger
kamcmd siptrace.status on
in the Kamailio containerwhen the
support-session-started
event is fired by NethServer 8.Conversely, run
kamcmd siptrace.status off
on thesupport-session-stopped
event to disable SIP tracing.What
This pull request introduces dynamic control over Kamailio SIP
tracing based on the state of support sessions, allowing the
command
kamcmd siptrace.status on
to be executed when asupport session starts and
kamcmd siptrace.status off
when itstops.
Why
By enabling SIP tracing specifically during active support
sessions, we can capture necessary TLS debug information without
overloading the system with traces outside of these sessions. This
improves both performance and debugging efficiency by limiting the
trace data to relevant periods.
NethServer/dev#7098