Wireshark-bugs: [Wireshark-bugs] [Bug 9021] RTP not decoded inside the conversation in v.1.10.1
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 05 Mar 2014 21:19:32 +0000

Comment # 5 on bug 9021 from 
(In reply to comment #3)
> This bug is a real bug I think - even though one side sends to the wrong UDP
> port, the other side sends to the correct UDP port but its RTP stream isn't
> being decoded either.  And fwiw I agree with Volodymyr that quite a few SIP
> devices do what the (Nortel?) MG 4000 gateway did in the attachment, of
> sending RTP back to where it received it from.  There's even a common term
> for it: "latching".
> 
> Also, this bug might (or might not) be related to bug 9835.

The RTP setup mechanism was changed some time ago to need both the offer and
the answer to set up the conversation to overcom bugs with the previous way
things where done. I don't think we can handle the latching case (easily) in
wireshark, that's normaly used to handle NAT e.g the UE IP port combination is
not seen in the SIP signaling as the UE is behind NAT and the signaling
contains the private addresses.

You are receiving this mail because:
  • You are watching all bug changes.