STDERR from your agi will be shown on
asterisk’s tty. If you’re using safe-asterisk to start, I believe
this is redirected to tty9… Or, if you can afford to take asterisk down
momentarily, you could just start asterisk without backgrounding it and you’ll
see what your script has to say ther
Hi,
Thanks for your reply. Dont the messages logged in /var/log/asterisk/messages contain error messages also dumped in tty9.
If not how can I view the messages on the tty9 console, The
problem is the server is hosted remotely and all I have is ssh access.
Shutting down asterisk might not be an
Unfortunately, STDERR from AGI scripts
does not make it to *’s log files. You can work around this by starting
Asterisk under screen. Take a look at the AGI wiki under “CLI output” for more
info. http://www.voip-info.org/wiki-Asterisk+AGI
Be warned though, that when you re-attach
to Ast
)
Restart Asterisk.
"enterprise grade".Digium calls it.
Doug.
-Original Message-From: Josh McAllister
[mailto:[EMAIL PROTECTED]Sent: Thursday, June 08, 2006 10:46
AMTo: Asterisk Users Mailing List - Non-Commercial
DiscussionSubject: RE: [Asterisk-Users] how t
On Thu, Jun 08, 2006 at 11:59:53AM -0600, Douglas Garstang wrote:
> I have only seen Asterisk send stdout to the console, which is _extremely_
> annoying. If your running a system in production mode, and your having a
> problem, you have to
>
> 1) shut Asterisk down
> 2) restart the Asterisk c
Douglas Garstang wrote:
I have only seen Asterisk send stdout to the console, which is
_extremely_ annoying. If your running a system in production mode, and
your having a problem, you have to
1) shut Asterisk down
2) restart the Asterisk console
3) reproduce the problem
4) shut asterisk down
