On Wed, Oct 6, 2021 at 10:40 PM Athos Ribeiro
<1909...@bugs.launchpad.net> wrote:
>
> Note that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971090 may
> be somewhat related to this one.
it probably is, because even asterisk doesn't log ansi to its own
logs, but does print it to console.
> It
Heya,
Yes, remotely attaching to console is basically the standard way of
doing anything with asterisk, the headless thing runs and accepts calls
etc but if you want to check current call status, registration, reload
dialplan, or pretty much do anything, you'll need to `asterisk -r`
to get to
@sergiodj,
> I'm not sure I agree with it. I think a better approach would be to
comment out the line I mentioned by default, since it doesn't seem to be
useful, given that the logs are already recorded in the log file under
/var/log/asterisk.
Wouldn't that remove any kind of output when you atta
Does anyone give a rat's ass about this? I'm guessing not, but some kind
of notification about it would have been nice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams co
Public bug reported:
problem:
Jan 2 00:23:40 fitpc systemd[1]: Starting Asterisk PBX...
Jan 2 00:23:40 fitpc asterisk[2328]: #033[0mPBX UUID: xx
Jan 2 00:23:40 fitpc asterisk[2328]: [Jan 2 00:23:40]
#033[1;33mNOTICE#033[0m[2328]: #033[1;37mloader.c#033[0m:#033[1;37m2230#0
