<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=iso-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Denis Galvão - iSolve wrote:
<blockquote cite="mid200501181055.54343.denis@isolve.com.br" type="cite">
<pre wrap="">Em Seg 17 Jan 2005 19:13, Steve Kann escreveu:
</pre>
<blockquote type="cite">
<pre wrap="">I've already replied, asking for a trace.. If you get the trace, and
send it, we can look at what is actually happening:
<Quote>
What would really help, though, is a packet trace of the call. The
best way to get this is to use either ethereal or tcpdump. (there is an
ethereal for windows).
If you use ethereal for Windows, have it capture all udp, make the call,
and have it stay up for about 30 seconds, and save the file. You can
then send that file to me, and I'll be able to see what's going on a lot
better than guessing here..
</Quote>
</pre>
</blockquote>
<pre wrap=""><!---->
Hi Steve.
I will do it, but I cant today.
How could you get some info with a call trace from ethereal!?
You will have a lot of traffic between 4569 UDP(IAX2) from both sides, how
could you have a diagnostic of the problem!?
</pre>
</blockquote>
Because you can look at the individual packets, their timestamps, and
their actual time of arrival -- ethereal parses IAX2 traffic.<br>
<br>
<br>
<br>
<blockquote cite="mid200501181055.54343.denis@isolve.com.br" type="cite">
<pre wrap="">Thanks and best regards.
</pre>
</blockquote>
<br>
</body>
</html>