Split dropped packet transport logging #3636
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
…le moving the packet contents to 4 (pjsip#3476)
mbradeen
force-pushed
the
sip-tp-drop-split
branch
from
9855ac8
to
1c22b22
Compare
sauwming
approved these changes
Jul 19, 2023
nanangizz
approved these changes
Jul 20, 2023
|
For future reference, the log level is increased because the packet source information is deemed important to identify any rogue senders. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To fix #3476.
Split logging to keep Warning regarding dropped packet at level 1 while moving the packet contents to 4.
The existing fix moves the entire log entry to 4. The fact that there was a dropped packet should still be logged at level 2.