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