<br><div class="gmail_quote">On Sat, Apr 7, 2012 at 1:38 PM, Alex Crow <span dir="ltr"><<a href="mailto:acrow@integrafin.co.uk">acrow@integrafin.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/04/12 10:33, Wesley Akio wrote:<br>
><br>
> Maybe the dialplan is waiting for curl to return... Can you see that<br>
> at the logs?<br>
><br>
><br>
<br>
Thanks Wesley,<br>
<br>
But the curl should return as soon as the event is detected, and surely<br>
the queued request for PAGD should proceed regardless of my polling for<br>
events after it. I've even tried listening for all events and logging<br>
them but I see nothing in the logs and still have to wait for the web<br>
server to timeout. The really odd thing is that if I don't do anything<br>
else in my PHP after the PAGD ESL call then I hear the message playing,<br>
as soon as I try to do anything else (including polling for events) I don't.<br>
<br>
I am just curious as to a) if I am trying to do something unsupported or<br>
b) I have found a bug.<br>
<br></blockquote><br>I suspect there are better tools at your disposal for doing what you are trying to do. If I were in your shoes (someone who obviously has Web dev and PHP experience) then I would cut my losses with method and head straight for HTTAPI. My guess is that the initial learning curve will be a bit steep but that once you get over the hump you will be building awesome applications without all the weird issues. <br>
<br>-MC<br></div>