ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 5172] Wireshark 1.4.0 & VoIP calls "Prepare Filter" proble

Date: Tue, 7 Sep 2010 14:22:53 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5172

--- Comment #6 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2010-09-07 23:22:51 CEST ---
(In reply to comment #4)
> Hi Jaap,
> 
> I am not sure what you mean by the first call falling back to the "Constructed"
> version.

At first an attempt is made to create a display filter expression based on all
the relevant frame numbers. This happens for the first and second call. 
The difference is that this explicit filter expression is too long (there are
too many frame numbers to incorporate) for the first call, so an alternative
filter expression is constructed based on elements of the signaling protocols.

> As to the IP addresses, the H323 gateways in question each use two IP
> addresses, one for call signalling & the other is the media address.
> 
> 10.7.53.201 is one of the gateway's signalling addresses and its media address
> is 10.7.53.101. The gateway at the other end of the IP network uses 10.7.53.203
> for signalling and 10.7.53.103 for media.

I looked into the H225 packets and found 10.7.53.201 as the H245 endpoint
address. It should be filled in automagically, but isn't. May be in the ASN
template or something.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.