equis software
2007-Apr-11 07:53 UTC
[asterisk-users] Execute EAGI script with params from extensions.conf
How can I execute an EAGI script with params from extensions.conf Example python script: InfMsg -s 1 in my extensions.conf exten => 492,1,Answer exten => 492,2,eagi,InfMsg -s 1 exten => 492,3,Hangup() It doesn?t work my * report... -- Executing [92@telpin-112:2] EAGI("Zap/4-1", "InfMsg -s 1") in new stack -- Launched AGI Script /var/lib/asterisk/agi-bin/InfMsg -s 1 == InfoTerminal -s 1: Failed to execute '/var/lib/asterisk/agi-bin/InfMsg -s 1': No such file or directory -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070411/bcd77c7f/attachment-0001.htm
Griepentrog Scott
2007-Apr-11 08:01 UTC
[asterisk-users] Execute EAGI script with params fromextensions.conf
I don't think you can put arguments to the agi. Try is as: exten => 492,2,eagi,InfMsg -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com]On Behalf Of equis software Sent: Wednesday, April 11, 2007 10:54 AM To: asterisk-users@lists.digium.com Subject: [asterisk-users] Execute EAGI script with params fromextensions.conf How can I execute an EAGI script with params from extensions.conf Example python script: InfMsg -s 1 in my extensions.conf exten => 492,1,Answer exten => 492,2,eagi,InfMsg -s 1 exten => 492,3,Hangup() It doesn?t work my * report... -- Executing [92@telpin-112:2] EAGI("Zap/4-1", "InfMsg -s 1") in new stack -- Launched AGI Script /var/lib/asterisk/agi-bin/InfMsg -s 1 == InfoTerminal -s 1: Failed to execute '/var/lib/asterisk/agi-bin/InfMsg -s 1': No such file or directory -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070411/1c865573/attachment.htm
Sean Bright
2007-Apr-11 08:05 UTC
[asterisk-users] Execute EAGI script with params from extensions.conf
You need to pass the arguments as separate arguments to the EAGI dialplan application, eg: exten => 492,2,EAGI(InfMsg,-s,1) but I would recommend using pipes... exten => 492,2,EAGI(InfMsg|-s|1) But maybe that's just me. On 4/11/07, equis software <equissoftware@gmail.com> wrote:> > How can I execute an EAGI script with params from extensions.conf > > Example python script: > InfMsg -s 1 > > in my extensions.conf > exten => 492,1,Answer > exten => 492,2,eagi,InfMsg -s 1 > exten => 492,3,Hangup() > > It doesn?t work > > my * report... > > -- Executing [92@telpin-112:2] EAGI("Zap/4-1", "InfMsg -s 1") in new stack > -- Launched AGI Script /var/lib/asterisk/agi-bin/InfMsg -s 1 > == InfoTerminal -s 1: Failed to execute > '/var/lib/asterisk/agi-bin/InfMsg -s 1': No such file or directory > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070411/67daf95e/attachment.htm
Eric "ManxPower" Wieling
2007-Apr-11 08:09 UTC
[asterisk-users] Execute EAGI script with params from extensions.conf
equis software wrote:> How can I execute an EAGI script with params from extensions.conf > > Example python script: > InfMsg -s 1 > > in my extensions.conf > exten => 492,1,Answer > exten => 492,2,eagi,InfMsg -s 1 > exten => 492,3,Hangup() > > It doesn?t work > > my * report... > > -- Executing [92@telpin-112:2] EAGI("Zap/4-1", "InfMsg -s 1") in new stack > -- Launched AGI Script /var/lib/asterisk/agi-bin/InfMsg -s 1 > == InfoTerminal -s 1: Failed to execute '/var/lib/asterisk/agi-bin/InfMsg > -s 1': No such file or directoryCommas. exten => 492,2,eagi(InfMsg,-s,1) At leeast in older versions of Asterisk, AGI only supports 1 parameter. I got around this by separating options with an &. Then break them out into options within my script. I don't know if 1.2 or 1.4 fixed this.