[asterisk-bugs] [JIRA] (ASTERISK-25358) dateformat not read from logger.conf by remote console

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-25358:
-------------------------------------

    Target Release Version/s: 18.4.0

> dateformat not read from logger.conf by remote console
> ------------------------------------------------------
>
>                 Key: ASTERISK-25358
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25358
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Documentation
>    Affects Versions: 11.19.0, 13.1.1, 13.5.0
>            Reporter: Igor Liferenko
>            Assignee: Mark Murawski
>              Labels: patch
>      Target Release: 16.18.0, 18.4.0
>
>         Attachments: date_and_call_id.patch
>
>
> My setup:
> logger.conf:
> [general]
> dateformat=%F %T
> [logfiles]
> console => notice,warning,error,debug,verbose
> asterisk.conf:
> [options]
> timestamp = yes
> I need timestamps in asterisk remote console so as to leave it running in screen and if something happens it would be easier to debug things.
> So, I add 'timestamp = yes' to asterisk.conf. But timestamp format is not read from logger.conf by 'asterisk -rvvv' for unknown reason and it shows timestamps partly in default format, and partly in "dateformat", which looks ugly:
> ...
> [Aug 31 20:17:40]     -- Registered IAX2 to 'X.X.X.X:4569', who sees us as X.X.X.X:4569 with no messages waiting
> [2015-08-31 20:17:41] NOTICE[31380]: chan_iax2.c:11159 socket_process_helper: Peer 'iax-provider' is now REACHABLE! Time: 150
> ...



--
This message was sent by Atlassian JIRA
(v6.2#6252)