hello i have one problem running yate 2.0alpha shoot very rare Noted especially with a few calls high level calls the problem is dissimulates I explain sending a call to yate yate send mesage to yaypm * Retrieving #YATE modes... yaypm processing and re-send message to yate yate is block, no aswered to message yaypm now, send second calls Repeats processing to yaypm If I do this with many simultaneous calls, everything works ok unlock yate and connect 2 calls the problem is when sending calls with a time lag between call and call * lftsy has quit IRC ("Leaving") I hope understanding I think it's a problem socket Between yate and yaypm After in the first call In which yaypm processing the call yate is closed socket and re-open socket when second call incoming Then pass the package first call With 30 calls the problem is camouflaged by the high traffic are you sure yate closes socket? yaypm would stop as well ? * maciejka has left #yate ("Leaving") * maciejka has joined #yate I am not sure yate close socket It's just an idea I don't understand what is the problem? As if a door opened only on one side The message get through the door And until that is not open for a new message ej call A , call B call A ----> yate ---> yaypm call A yaypm ---- yate (socket closed, door closed) call B ----> yate ---> yaypm NOW yate open socket, open door call A yaypm ----> yate (socket open, door open thanks to call B) two calls recebie yate an processing to conect call A and B connect same time if call B not genering.... call A never procesing, and not connect ask killall-9 it looks like a buffering problem in extmodule Understand? I've understood that sometimes yate does not get messages from yaypm unless other messages are sent in opposite direction. it that right? now, high level calls the problem disimulate, and seems everything found correct what is your system? debian 2.6.24 kernel bigmen That question? maciejka: extmodule uses unbuffered I/O maciejka ---> YES, IS CORRECT yate does not get messages from yaypm unless other messages are sent in opposite direction maciejka: if it's about buffering it may be in the output of yaypm not being flushed Just that * marian has quit IRC (Remote closed the connection) killall-9: I am just checking maciejka: in PHP we use ob_implicit_flush(1); to force all output to be immediately flushed killall-9: Hi! Could you consult me on that question: http://yate.null.ro/archive/?action=show_msg&actionargs[]=29&actionargs[]=58 It concerns extmodule too and python too :) I will be online short later... * mtelegin has quit IRC ("KVIrc 3.2.6 Anomalies http://www.kvirc.net/") mtelegin: it seems python got upset when the audio stream was closed and started throwing unhandled exceptions I do not see config buffers in the extmodule Manguera: can you check with packet sniffer if messages are from from yaypm to yate? are sent from yaypm to yate ;[listener sample] ; For each socket listener there should be a section starting with the ; "listener" keyword extmodule what socket number drive yate to yaypm? 5039 ?? it is extmodule conf [listener bs] type=tcp addr=127.0.0.1 port=5039 role=global Alli?There? There? * killall-9 has quit IRC ("Leaving") It is possible that the problem by Twisted ? check with packet sniffer first I don't experience that problem http://yate.null.ro/pmwiki/index.php?n=Main.YAYPMExtmodule configuration seems ok More efficient way is to run it as a channelless script and use DumbChannel (see below) ok maciejka tnks your help (Y) * implicit has joined #yate hi hi l-fy * mmoreno80 has joined #yate hi. hi mmoreno80 hi mmoreno80