|
Hi,
In frame 34 there is a SDP that says that UDP port
5060 should be used for RTP audio. Ethereal will set up a conversation
(ip-address/port combination) and
decode packets for that
conversation with RTP dissector.
That will also be done for the packets before frame
34 when you click on one of those packets, but the Info in the Info-column will
be the result from
the first pass before the conversation was setup
(until packets are re-dissected e.g. due to display filter).
When I added a display filter string I noticed that
the packets that previously were shown as SIP became shown as RTP in the
Info-column.
It seems strange that you use port 5060 for RTP
packets (maybe a test-client has been configured in a not normal way), but the
capture still shows a possible problem that may occur when several protocols are
using same port/address combination.
/Martin
----- Original Message -----
Sent: Wednesday, May 04, 2005 12:54
AM
Subject: [Ethereal-dev] Issue with
SIP
Hello,
I
was using ethereal to capture some SIP messages and found something
strange.
Ethereal is decoding the SIP
message as RTP even though in the packet list area, it is
recognized as a SIP protocol. (Refer to the first line in the attached
ethereal file)
But in the packet
details area it appears as RTP. Why is it not decoding as a SIP
message?
Thanks in adv,
Vikas
_______________________________________________
Ethereal-dev mailing
list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
| 
