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
[bug]: res_pjsip_logger: Reload disables logging #246
Labels
Comments
InterLinked1
added a commit
to InterLinked1/asterisk
that referenced
this issue
Aug 9, 2023
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: asterisk#246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
jcolp
added
support-level-core
Functionality with core support level
and removed
triage
labels
Aug 9, 2023
InterLinked1
added a commit
to InterLinked1/asterisk
that referenced
this issue
Mar 21, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: asterisk#246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
InterLinked1
added a commit
to InterLinked1/asterisk
that referenced
this issue
Apr 1, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: asterisk#246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
InterLinked1
added a commit
to InterLinked1/asterisk
that referenced
this issue
Apr 4, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: asterisk#246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
May 1, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: #246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
May 1, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: #246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
May 1, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: #246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
May 1, 2024
Currently, reloading res_pjsip will cause logging to be disabled. This is because logging can also be controlled via the debug option in pjsip.conf and this defaults to "no". To improve this, logging is no longer disabled on reloads if logging had not been previously enabled using the debug option from the config. This ensures that logging enabled from the CLI will persist through a reload. ASTERISK-29912 #close Resolves: #246 UserNote: Issuing "pjsip reload" will no longer disable logging if it was previously enabled from the CLI.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity
Minor
Versions
All
Components/Modules
res_pjsip_logger
Operating Environment
N/A
Frequency of Occurrence
Constant
Issue Description
Imported from JIRA: https://issues.asterisk.org/jira/browse/ASTERISK-29912
When
res_pjsip
is reloaded, any logging enabled inres_pjsip_logger
via the CLI is disabled. This is a behavior difference from basically every other module, includingchan_sip
, and has caused confusion and annoyance for many users.Relevant log output
No response
Asterisk Issue Guidelines
The text was updated successfully, but these errors were encountered: