[Bug 1182947] Re: Cannot specify interpreter path in AGI call

2013-06-03 Thread Robie Basak
Thanks for following this up with upstream. Marking Invalid in line with upstream's decision. ** Changed in: asterisk (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu.

[Bug 1182947] Re: Cannot specify interpreter path in AGI call

2013-06-03 Thread Ariel Wainer
Just for the future peoplen finding this issue, this works: Instead of: exten = 1234,n,AGI(/path/to/interpreter /path/to/script,args) Do: exten = 1234,n,AGI(/path/to/interpreter,/path/to/script,args) -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 1182947] Re: Cannot specify interpreter path in AGI call

2013-05-23 Thread Ariel Wainer
I agree, it should be fixed upstream, I'll test it on the latest version and report to asterisk bugtracker. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1182947 Title: Cannot

[Bug 1182947] Re: Cannot specify interpreter path in AGI call

2013-05-23 Thread Ariel Wainer
Asterisk people didn't agree this is a bug: https://issues.asterisk.org/jira/browse/ASTERISK-21812 Should we close this one as well? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu.

[Bug 1182947] Re: Cannot specify interpreter path in AGI call

2013-05-22 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make Ubuntu better. This is the sort of thing that would be best fixed upstream - it's probably best not to make distro-specific changes in this area. Have you considered testing for this problem in the original upstream release and