[SpaceBass]

hey folks.
I'm working on having Asterisk@home do some 'outside the box' work via bash scripts.
I have written a script and placed it in /var/lib/asterisk/agi-bin.
in my dial-plan i have:

[custom-myscript]
exten => s,1, wait(1)
exten => s,2, background(custom-myscript)
exten => 1,1,AGI(myscript|arg1)
exten => 2,1,AGI(myscript|arg2)

I can run the script from the bash promt just fine:
$ myscript 1

When I try and do it from Asterisk the CLI shows that it exits 0 but it never actually works.

For testing sake myscript is a BASH script that just does a touch to create a file.

Anyone have any clues?

Thanks!

[mberlant]

Unfortunately, there are some holes (poorly documented) that are at work here. I have clues for you, but not enough knowledge to give you a solution. Here goes...

First, what is the nature of custom-myscript? Does it ask the caller to press 1 for this and 2 for that? If so, you need to include DigitTimeout and ResponseTimeout lines. Without these lines Asterisk won't be listening for the caller's input.

Second, what is the difference between arg1 and arg2? Do they perform, perhaps, a different offset in your touch command?

[chandave]

Originally Posted by SpaceBass

hey folks.
I'm working on having Asterisk@home do some 'outside the box' work via bash scripts.
I have written a script and placed it in /var/lib/asterisk/agi-bin.
in my dial-plan i have:

[custom-myscript]
exten => s,1, wait(1)
exten => s,2, background(custom-myscript)
exten => 1,1,AGI(myscript|arg1)
exten => 2,1,AGI(myscript|arg2)

I can run the script from the bash promt just fine:
$ myscript 1

When I try and do it from Asterisk the CLI shows that it exits 0 but it never actually works.

For testing sake myscript is a BASH script that just does a touch to create a file.

Anyone have any clues?

Thanks!

1. Is the first line of your script:
   #!/bin/bash
   If not, then the execl() family of system functions will not know which script interpreter to use to execute the script.
2. For the current testing version of "myscript", when "touch"ing the file, is the complete path specified or are you leaving it a relative path? If it's relative, are you sure the bash script has write access to the directory from which it is executing?
3. Try changing the first line to:
   #!/bin/bash -x
   and then run the AGI from Asterisk. Check your /var/log/asterisk/messages, to see if you see your AGI executing.
4. Since your current testing version of "myscript" just touches a file, post it verbatim to this forum.

See ya...

d.c.