I understand, but autoservice and AGI wouldn't be running on the same channel
at the same time. And I assume that once the transfer is completed, original
AGI call will be terminated. If I am wrong in that assumption, then I am in
trouble.
It should be noted that, while you say that AGI can't run twice on the same
channel, the the second AGI call does go through and everything works as
intended. I am just worried that this will cause some problem down the line,
and I would like to avoid the debug message.
Regards,
On Thursday, 02. March 2023. 10:57:23 (+01:00), Joshua C. Colp wrote:
On Thu, Mar 2, 2023 at 5:50 AM Nikša Baldun <i...@voxdiversa.hr> wrote:
Hi Joshua,
thanks for the answer. Meanwhile, I've found that the debug message about
competing threads happens because I am using Fast AGI, and two threads call AGI
from the same channel. I assume this could potentially be resolved if I call
ast_app_exec_sub AFTER the attended transfer has already been completed (and,
based on your input, autoservice should be used). This is trickier to
implement, but I'll try.
Fundamentally two threads can't service the same channel at the same time. So
autoservice and AGI can't run on the same channel at the same time, just like
AGI can't run twice on the same channel at the same time. It's the equivalent
of having two people tell you what to do at the same time.
--
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
--
Nikša Baldun
VoxDiversa
Sjedište:
IX Trokut 1
10020 Zagreb
Ured:
Ilica 425
10090 Zagreb
Tel.: +385 1 8000676
Web: www.voxdiversa.hr
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
