On Mon, 18 Feb 2013, Steven Howes wrote:
On 18 Feb 2013, at 17:03, Christopher Harrington wrote:
On Mon, Feb 18, 2013 at 10:54 AM, Steve Edwards
wrote:
) If the AGI is [...] a compiled executable (C, Fortran, Cobol,
assembler, etc.)
I'd like to see an AGI written usi
On 18 Feb 2013, at 17:03, Christopher Harrington wrote:
> On Mon, Feb 18, 2013 at 10:54 AM, Steve Edwards
> wrote:
> ) If the AGI is [...] a compiled executable (C, Fortran, Cobol, assembler,
> etc.)
> I'd like to see an AGI written using Fortran or Cobol.
Don't tempt me ;)
S--
_
On Mon, Feb 18, 2013 at 10:54 AM, Steve Edwards
wrote:
> ) If the AGI is [...] a compiled executable (C, Fortran, Cobol, assembler,
> etc.)
I'd like to see an AGI written using Fortran or Cobol.
--
-Chris Harrington
ACSDi Office: 763.559.5800
Mobile Phone: 612.326.4248
--
On Mon, 18 Feb 2013, Thorsten Göllner wrote:
I am wondering, if there is any tool available, which performs a check
for suspicious entries in the dialplan. For example a non existing
AGI-Script...
I'm just a 1.2 Luddite, but none that I know of.
Please feel free to write one. Here are a few
>> A "normal dialplan reload command" would echo no warning or something
>> similair.
Normally I would see these being logged to /var/log/asterisk/messages with a
stock Asterisk install.
Doug
--
Ben Franklin quote:
"Those who would give up Essential Liberty to purchase a little Tempora
On Mon, Feb 18, 2013 at 8:11 AM, Thorsten Göllner wrote:
>
> A "normal dialplan reload command" would echo no warning or something
> similair.
>
The duplicated extension will cause an error. Something like "cannot add
extension in line X because it already exists."
--
Carlos Alvarez
TelEvolve
Hi,
I am wondering, if there is any tool available, which performs a check
for suspicious entries in the dialplan. For example a non existing
AGI-Script or a double assigned extension ike that:
[context]
exten => *100*,1,AGI(test_app.pl)
...
exten => 190,1,Answer()
...
exten => *100*,1,AGI(ne
