FYI --
I realized that in the trace that I sent, I was using a capture filter on a
single host IP address. For this scenario, the RTP will be sent to a
different IP address, which is why there is no RTP shown in the capture
file.
Guy,
Thanks for the bug fix.
>From what I know about T38, the call is always setup as a voice call. When
the terminating device detects the CED tone from the fax machine, it
initiates the switch over to T38 by sending an H245 RequestMode towards the
originator.
-----Original Message-----
From: Guy Harris [mailto:gharris@xxxxxxxxx]
Sent: Wednesday, August 18, 2004 3:36 AM
To: Ethereal user support
Subject: Re: [Ethereal-users] segmentation fault in 0.10.6 (and 0.10.5)
Oliveras, Michael wrote:
> The attached capture causes ethereal 0.10.6 to seg fault when the capture
is
> decoded.
I've checked in a fix.
> The trace is a t38 fax call through a session controller.
...which explains why, although the code was crashing in the "set up an
RTP conversation" code, no RTP traffic appeared - the T.38 call was
going over TCP, but the "set up an RTP conversation' code was assuming UDP.
Is there anything in that capture that indicates that it's setting up a
T.38 call, rather than an RTP call? Presumably we shouldn't just be
assuming that H.245 is setting up an RTP session.
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users