Hi Anthony, i really apologise for not being still able to provide the trace, i am under product release and this is an issue of the many to be managed and it's in my company backlog. I did not wanted to make FUD or being arrogant, really. It's just that i read an issue in the mailing list similar to what i experience. We still not analyzed deeply and you know that a non deterministic bug it's something quite difficult to be traced down, require a continuous testing environment to catch the issue while collecting a lot of logs :( Will do it, just is in a schedule of activities. Fabio On 22/04/10 17.33, Anthony Minessale wrote:
Are you arrogantly refusing to collect the actual sip traces but still feel the need to report an issue? That is called FUD and we do not tolerate it here. Either hold your tongues or collect the info. Do not just use our mailing list to say you have "random and not reproducible problems" It does nobody any good. We have now wasted 3 email exchanges simply asking for the information. If you were able to produce the ladder diagram surely you could have done what I asked and did a pcap from the FS box and a console trace. Maybe you should learn more about network topology before you send us any more email.