Re: [Asterisk-java-users] How to continue dialplan execution after autohangup?
Brought to you by:
srt
|
From: Peter K. <pet...@ed...> - 2014-06-16 15:05:20
|
In this special case,
async agi or as i will do it, i extract all relevant info and start a thread an release the agi so dialplan execution can continue
peter
-----Ursprüngliche Nachricht-----
Von: Murthy Gandikota <mga...@nt...>
Gesendet: Mon 16 Juni 2014 16:45
An: ast...@li...
Betreff: Re: [Asterisk-java-users] How to continue dialplan execution after autohangup?
Hi Yves
Used h - priority. The dial plan execution stops at the AGI call even after auto hangup duration exceeded. With regards to objective: I have a DB intensive method that can take longer than 20 seconds when there is too much activity. If the duration of the method call exceeds the time limit, I would like to abandon it and return to the dial plan with an error message like ("Sorry, could not look up an agent"). If you could please suggest an alternative I would appreciate it.
Thanks
Murthy
--------------------------------
From: Yves A. [mailto:yv...@gm...]
Sent: Sunday, June 15, 2014 3:57 AM
To: ast...@li...
Subject: Re: [Asterisk-java-users] How to continue dialplan execution after autohangup?
Hi,
Take a look at the h - priority... this part of the dialplan becomes executed after hangup.
But more important for me, as I think there might be a smarter solution...:
what is your objective? Why auto-hangup the call at all?
yves
Am 13.06.2014 03:06, schrieb Murthy Gandikota:
Hi Yves or anyone who cares to answer,
I am using setAutoHangup(20) in my AGI script. Then I do a DB look up that can take potentially longer than 20 seconds as follows:
try {
setAutoHangup(20);
call-a-very-long-db-access-method();
} catch (Exception e) {
}
In my dialplan I call the AGI as :
exten = 2,n(lookup-agent), agi(agi://${JAVA-AGI-SERVER}/lookupAgent.agi)
exten = 2,n, VERBOSE(back from agi)
During testing I find that "back from agi" is never printed soon after 20 seconds. In other words, the agi call in the dial plan is waiting for the return from the service method in the LookupAgent.
Is this a flaw or by design? How can I return from LookupAgent after 20 seconds without async?
Thanks for your help.
Murthy
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems <http://p.sf.net/sfu/hpccsystems>
_______________________________________________
Asterisk-java-users mailing list
Ast...@li... <mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/asterisk-java-users
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Asterisk-java-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/asterisk-java-users
Mehr News und Informationen aus der Welt der EDAG Group können Sie in unserem interaktiven EMAG-Magazin (http://www.edag.de/pr/Newsletter/) nachlesen! Wir freuen uns auf Ihren Besuch!
------------------------------------------------------------------------------
Registergericht/Court of jurisdiction: Amtsgericht Wiesbaden, HRB 27623 USt.-Id: DE 292 939 239
Vorstand / Executive Board: Werner Kropsbauer (CEO), Jörg Ohlsen (CTO), Harald Poeschke (COO), Jürgen Vogt (CFO)
Aufsichtsratsvorsitzender / Chairman of the Supervisory Board: Thomas Eichelmann
Hauptsitz/Headquarters: EDAG Engineering AG, Kreuzberger Ring 40, 65205 Wiesbaden Deutschland/Germany / www.edag.com
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
|