Our tests are quite aggressive and elaborate. That is how we found out
MUTT did not work from SYSTEM() dialplan. It worked well from within
a cron job, within other bash scripts and from linux shell console as
stand alone MUTT. Bash scripts and system commands called in from
SYSTEM() has worked perfectly fine for several years, processing
approximately half a million calls per month per server. So to answer
your question - we did tests for all possible scenarios one can think
off, which includes tests from inside a script, from inside a script run
from cron, and from other background processes.
As per " Testing from cli is NOT the same! " -- No where in my
messages I mentioned we tested MUTT from CLI of Asterisk.
--
*
*FOUNDER & SR. TELECOM ANALYST*
/VOIPERNETICS COMMUNICATIONS <http://www.voipernetics.com/>/*
NATION WIDE DIDS, SIP TRUNKS & VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX & TERMINATION SERVICES.
TEL: 647-476-2067
Frank Bax wrote the following on 9/27/2011 7:22 AM:
On 09/26/11 12:47, Reza - Voipernetics wrote:
MUTT in itself works. So now the culprit is the MUTT process - why this
fails to work (without spitting any errors) when called from SYSTEM()
but works perfectly fine when invoked DIRECTLY from the console. And
yes, FULL PATH NAME for MUTT is included.
When you tested that MUTT works; did you test from inside a script run
from cron or some other background process? Testing from cli is NOT
the same! Some script behave badly when there is no terminal fro
output. Environment variables are also different.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
