Re: [OpenSIPS-Users] Async DB statement

2017-01-24 Thread Bogdan-Andrei Iancu
Ahmed, after an async() call, the execution never returns, but it continues exclusively via the resume route. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 05:06 PM, Ahmed Munir wrote: I mean to say, after calling async

Re: [OpenSIPS-Users] Async DB statement

2017-01-24 Thread Bogdan-Andrei Iancu
Could you please rephrase / detail your question, as I do not understand what you are asking. Thanks, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 03:44 PM, Ahmed Munir wrote: Thanks, have been working on this and it is working. Btw, I

Re: [OpenSIPS-Users] Async DB statement

2017-01-24 Thread Ahmed Munir
Thanks, have been working on this and it is working. Btw, I would like to know, is there a way to resume route while using async avp_db_query? As currently setting/declaring another async route for DB query, looking for resume route in main routing script. On Tue, Jan 24, 2017 at 6:45 AM,

Re: [OpenSIPS-Users] Async DB statement

2017-01-24 Thread Bogdan-Andrei Iancu
Hi Ahmed, Note the $rc holds the return code of the LAST executed statement/instruction/function in the script. In the first case you do it right by saving the ret code of the avp_db_query into a separate variable, so you can use it even later. In the sync script, the $rc, when entering the

[OpenSIPS-Users] Async DB statement

2017-01-19 Thread Ahmed Munir
Hi, Currently I'm trying to use async fucntion for avp_db_query. The issue I'm facing while using it as not retrieving or returning correct return code and not execute later part of the routing script. See old & new DB queries; Without Async: -- route[1]{ ...