You probably didn't read over my originally post carefully. In the dialplan A2billing.php script is called in the "X" extension. Then there is X,n,Hangup() so now "X" extension is dead.
After that in "h" extension I have ANOTHER script running. However, the CLI output (which again I posted in my original post) shows that the A2Billing.php script which was run in the "X" extension actually terminated at the end of "h" extension. I would appreciate it if someone with knowledge can please weigh in. Regards, On Mon, Apr 11, 2011 at 12:06 PM, Pezhman Lali <[email protected]> wrote: > h is hangup extension, and will be executed after hangup > > > On Mon, Apr 11, 2011 at 6:36 PM, Bruce B <[email protected]> wrote: > >> Thanks for the input but I am not sure if that answer my question of if >> it's normal behaviour for AGI scrip to terminate after the "h" extension >> rather than end of "x" extension even if it was only run in "x" extension. >> >> Regards, >> >> On Mon, Apr 11, 2011 at 6:34 AM, Pezhman Lali <[email protected]> wrote: >> >>> Dear >>> there is some problem. >>> the true way for running php script, is using agi not system. >>> second after 5 sec, a lot of channel variables were removed, it makes >>> your program wrong. >>> with some little experience you can add your script to a2billing, try it. >>> >>> best >>> >>> On Sat, Apr 9, 2011 at 7:22 PM, Bruce B <[email protected]> wrote: >>> >>>> Hi Everyone, >>>> >>>> Trying to run a php script after DeadAGI for A2Billing does it's magic. >>>> This is the dialplan: >>>> >>>> [a2billing] >>>> exten => _X.,1,System(php pre-call.php ${CALLERID(num)} ${EXTEN} >>>> ${UNIQUEID}) >>>> exten => _X.,n,AGI(a2billing.php,1) >>>> exten => _X.,n,Hangup() >>>> *exten => h,1,Wait(5)* >>>> *exten => h,n,System(php post-call.php ${CALLERID(num)} ${UNIQUEID})* >>>> >>>> As you can see above, I even added a 5 seconds wait time before running >>>> my post-call script but the problem is that DeadAGI and AGI actually >>>> terminates after the "h,n" extension is run. I thought this weired because >>>> "X" extension is already finished at "X,3". >>>> >>>> Is this normal behavioral for AGI/DeadAGI? >>>> Is there a workaround this other than including my post-call script into >>>> the a2billing.php itself? >>>> >>>> Output from CLI for proof: >>>> >>>> -- Executing [h@a2billing:1] Wait("SIP/101-00000034", "5") in new >>>> stack >>>> *-- Executing [h@a2billing:2]* System("SIP/101-00000034", "php >>>> post-call.php 101 1302360230.52") in new stack >>>> -*- <SIP/101-00000034>AGI Script a2billing.php completed, returning >>>> -1* >>>> * >>>> * >>>> Thanks, >>>> >>>> -- >>>> _____________________________________________________________________ >>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>>> New to Asterisk? Join us for a live introductory webinar every Thurs: >>>> http://www.asterisk.org/hello >>>> >>>> asterisk-users mailing list >>>> To UNSUBSCRIBE or update options visit: >>>> http://lists.digium.com/mailman/listinfo/asterisk-users >>>> >>> >>> >> >> -- >> _____________________________________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> New to Asterisk? Join us for a live introductory webinar every Thurs: >> http://www.asterisk.org/hello >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
