you must read the reply to the commands when you send them or you will block the tcp socket.<br><br><br><div class="gmail_quote">On Mon, Nov 10, 2008 at 9:48 AM, Dennis <span dir="ltr"><<a href="mailto:odermann@googlemail.com">odermann@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">you are right, the shown script is very simple. we shortened it a lot<br>
just to show the problem.<br>
<br>
in these tests we do not need any events, because we just answer and<br>
originate - for these actions we do not need any events, filters and<br>
so on.<br>
the rest we do in the cli. in the cli we do show channels and<br>
uuid_bridge. but the uuid_bridge is only done, when we kill the<br>
process of the socket script.<br>
there must be a problem, how we handle the inbound or something like this.<br>
<br>
every alse we want to do with any call and uuid works, so i can't<br>
imagine, that our php script does everything so wrong.<br>
what makes uuid_bridge or intercept so different to other api commands?<br>
<br>
isn't it possible to see something in the logfiles? perhaps, that the<br>
inbound is in a wrong state or stuck somewhere in the socket?<br>
<br>
<br>
<br>
<br>
2008/11/10 Anthony Minessale <<a href="mailto:anthony.minessale@gmail.com">anthony.minessale@gmail.com</a>>:<br>
<div class="Ih2E3d">> The way your script is parsing appears too simple.<br>
> The event socket has a specific protocol.<br>
><br>
> Every command has a reply and you must read it and take into account the<br>
> content len etc.<br>
><br>
> all replies, events etc have a content-type and content-len.<br>
<br>
</div><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>