diff options
author | George Joseph <george.joseph@fairview5.com> | 2016-02-07 16:34:20 -0700 |
---|---|---|
committer | George Joseph <george.joseph@fairview5.com> | 2016-02-18 16:30:18 -0600 |
commit | 6b921f706d493f926c3bceb44775aa71bdc5e225 (patch) | |
tree | 3ea44b98f0b0e81a0f69076dda19b3f7f596695b /tests/test_ast_format_str_reduce.c | |
parent | 37c273f0de946282e69c0a6166b955eb3b4f8c2e (diff) |
res_pjproject: Add ability to map pjproject log levels to Asterisk log levels
Warnings and errors in the pjproject libraries are generally handled by
Asterisk. In many cases, Asterisk wouldn't even consider them to be warnings
or errors so the messages emitted by pjproject directly are either superfluous
or misleading. A good exampe of this are the level-0 errors pjproject emits
when it can't open a TCP/TLS socket to a client to send an OPTIONS. We don't
consider a failure to qualify a UDP client an "ERROR", why should a TCP/TLS
client be treated any differently?
A config file for res_pjproject has bene added (pjproject.conf) and a new
log_mappings object allows mapping pjproject levels to Asterisk levels
(or nothing). The defaults if no pjproject.conf file is found are the same
as those that were hard-coded into res_pjproject initially: 0,1 = LOG_ERROR,
2 = LOG_WARNING, 3,4,5 = LOG_DEBUG<level>
Change-Id: Iba7bb349c70397586889b8f45b8c3d6c6c8c3898
Diffstat (limited to 'tests/test_ast_format_str_reduce.c')
0 files changed, 0 insertions, 0 deletions