I recommend that you do not uncomment the lines which are in fact comments.
It will result in error messages indicating that the configuration parser has
no idea what to make of lines which are standard English text.
Also, in general “I have uncommented everything” is a bad policy, because even
if everything you uncommented is then parseable and valid syntax (unlike here)
a) it may or may not reflect what you want to do, because you clearly didn’t
think “do I want to uncomment this bit or not?”
b) it may or may not make sense, because quite often some settings are
mutually exclusive, so enabling them all results in something that contradicts
itself
c) it may well result in something insecure, because examples in config files
(which are commented out for a very good reason) often show how you would
set something to a secure setting without knowing quite what that secure
setting is in your environment
So, please revert to the original file, and then read it, treating the
comments which are there to explain the settings (which are commented out in
case you don’t actually want them) as a guideline telling you which settings
(not explanations) you might like to uncomment in order to enable them.
If you do not understand what a particular setting does, try a search engine
for “Asterisk setting name”, substituting “setting name” with the thing you
are unsure of.
If that doesn’t help, feel free to come back here and ask about that setting.
However, uncommenting every single line in a configuration file which contains
English explanations as well as configuration lines will simply result in
something unparseable, and which nobody can help you recover from other than
“put it back the way it was”.
Tks for your reply, following to this i have re-comment the lines like that:
; Filenames can either be relative to the standard Asterisk log directory
; (see 'astlogdir' in asterisk.conf), or absolute paths that begin with
; '/'.
;
; An optional formatter can be specified prior to the log levels sent
; to the log channel. The formatter is defined immediately preceeding the
; levels, and is enclosed in square brackets. Valid formatters are:
; - [default] - The default formatter, this outputs log messages using a
; human readable format.
; - [plain] - The plain formatter, this outputs log messages using a
; human readable format with the addition of function name
; and line number. No color escape codes are ever printed
; nor are verbose messages treated specially.
; - [json] - Log the output in JSON. Note that JSON formatted log entries,
; if specified for a logger type of 'console', will be formatted
; per the 'default' formatter for log messages of type VERBOSE.
; This is due to the remote consoles interpreting verbosity
; outside of the logging subsystem.
;
; Log levels include the following, and are specified in a comma delineated
; list:
; debug
; trace
; notice
; warning
; error
; verbose(<level>)
; dtmf
; fax
; security
; <customlevel>
;
; Verbose takes an optional argument, in the form of an integer level. The
; verbose level can be set per logfile. Verbose messages with higher levels
; will not be logged to the file. If the verbose level is not specified, it
; will log verbose messages following the current level of the root console.
;
; Debug has multiple levels like verbose. However, it is a system wide setting
; and cannot be specified per logfile. You specify the debug level elsewhere
; such as the CLI 'core set debug 3', starting Asterisk with '-ddd', or in
; asterisk.conf 'debug=3'.
;
; Special level name "*" means all levels, even dynamic levels registered
; by modules after the logger has been initialized (this means that loading
; and unloading modules that create/remove dynamic logger levels will result
; in these levels being included on filenames that have a level name of "*",
; without any need to perform a 'logger reload' or similar operation).
; Note that there is no value in specifying both "*" and specific level names
; for a filename; the "*" level means all levels. The only exception is if
; you need to specify a specific verbose level. e.g, "verbose(3),*".
;
; We highly recommend that you DO NOT turn on debug mode if you are simply
; running a production system. Debug mode turns on a LOT of extra messages,
; most of which you are unlikely to understand without an understanding of
; the underlying code. Do NOT report debug messages as code issues, unless
; you have a specific issue that you are attempting to debug. They are
; messages for just that -- debugging -- and do not rise to the level of
; something that merit your attention as an Asterisk administrator. Both
; debug and trace messages are also very verbose and can and do fill up
; logfiles quickly. This is another reason not to have debug or trace
; modes on a production system unless you are in the process of debugging
; a specific issue.
;
;debug => debug
;trace => trace
;security => security
;console => notice,warning,error
;console => notice,warning,error,debug
;messages => notice,warning,error
full => notice,warning,error,debug,verbose,dtmf,fax
;full-json => [json]debug,verbose,notice,warning,error,dtmf,fax
;syslog keyword : This special keyword logs to syslog facility
;syslog.local0 => notice,warning,error
A log level defined in 'custom_levels' above
important.log = important
then i have reload with the command logger reload and edit the files `asterisk.conf to set the log level to 3:
[options]
verbose = 3
debug = 3
When i lauch the cli i have this message : `
Asterisk 18.19.0, Copyright (C) 1999 - 2022, Sangoma Technologies Corporation and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 18.19.0 currently running on Asterisk (pid = 1020)
Parsing /etc/asterisk/logger.conf
No '=' (equal sign) in line 185 of /etc/asterisk/logger.conf
Core debug is still 3.
Asterisk*CLI> exit
Asterisk cleanly ending (0).
Executing last minute cleanups
Asterisk ending (0).
root@Asterisk:/etc/asterisk# nano logger.conf
root@Asterisk:/etc/asterisk# nano asterisk.conf
root@Asterisk:/etc/asterisk# asterisk -rcvvvv
'c' option is not compatible with remote console mode and has no effect.
Asterisk 18.19.0, Copyright (C) 1999 - 2022, Sangoma Technologies Corporation and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 18.19.0 currently running on Asterisk (pid = 1020)
Parsing /etc/asterisk/logger.conf
No '=' (equal sign) in line 185 of /etc/asterisk/logger.conf
Core debug is still 3.
As @david551 suggest to me, i guess level 3 is enable but i have no clue how to do : and also turn on protocal logging, with “pjsip set logger on”.
`
I know it sound very silly for you guys but could you please try to help me to moove forward with this.