<Manguera> hello
<Manguera> yate - Rev 1846 not resolved problem one a one call
<killall-9> by "one a one call" you mean the individual message not ack-ed from external Python issue, right?
<killall-9> i suggest to capture with ethereal/wireshark the tcp port, look at the timing of exchanged text lines
<killall-9> there should be pairs of %>message and %<message with little time in between
<killall-9> i mean %%>message and %%<message (irc escape problem)
<Manguera> hello kill
<Manguera> the mensagges is correct, both in time and in quantity
<Manguera> messages are not lost and have no lag
<killall-9> so there is little time between %%> and %%< and long time between these groups?
<Manguera> it is as if it were an emergency gate, which open single-sided
<Manguera> the message from the first call is unable to return to yate
<killall-9> again, at TCP level is ok but in Yate is not?
<killall-9> can you pastebin somewhere the output of tcpdump so i can look at the times?
<Manguera> Pending enter a message in a second call to reopen the door, there the message of the first call may happen because the door became open
<Manguera> yes kill
<Manguera> i have pastebin
<Manguera> minute
* _monica_ has quit IRC ("Leaving")
<Manguera> kill
<Manguera> no problem four you i capture with ethereal/wireshark ?
<killall-9> well, you can't put that in a pastebin ;-)
* vircuser has joined #yate
<Manguera> I pass messages to a file and paste in pastebin
<vircuser> hi
* killall-9 has quit IRC ("changing computer")
* killall-9 has joined #yate
* l-fy has quit IRC (Nick collision from services.)
* vircuser is now known as l-fy
<l-fy> done
<Manguera> kill
<Manguera> talk to my partner who has a yate in his notebbok for sniff and I said that there was no problem of packages or times, not lost
<Manguera> in your notebook runs a old version yate and is not the problem
<Manguera> the problem appeared with a new revision
<killall-9> does this happen all the time or only on 1st message?
<Manguera> 1st mensage = 1st call --> not connect
<Manguera> 2st mensage = 2st call --> connect two calls
<Manguera> at the same time
<Manguera> call 1 and 2 connect at the same time
<Manguera> 3st mensage = 3st call --> not connect
<Manguera> 4st mensage = 4st call --> connect again two calls (3 call and 4 call)
<Manguera> second mennsage re-open door and connect last calls
<killall-9> can you please capture the communication between yate and python?
<killall-9> i tried to reproduce with php and failed to
<Manguera> ok kill, no problem
<Manguera> now I think update python to the new release 2.4.5 (March 11, 2008)
<Manguera> older version running 2.4.4
<Manguera> mmm
<Manguera> Maybe this new release python causing the problem
<Manguera> i think my partner has in his notebook a yate running OK one a one call
<Manguera> as it arrives at the office will see that version of python and revision of yate is assigned running, and test re python upgrade to the new release and make a call
<Manguera> i bet that is the new version of python
<Manguera> if you can wait kill, I think it will be the best thing, at least to establish that the problem is
<Manguera> guess that also want to solve the problem for the new release of python