Also, will the capability of playing G.729 streams be added to the wishlist?
Thanks,
Brian Daniel
On Fri, Sep 16, 2011 at 9:43 AM, Matthews, Jeremy wrote:
> Hi,
>
> ** **
>
> Currently, in the Telephony/VoIP Calls section, one can only play G.711u
> and G.711a RT
Siva,
A switch sends data only to the ports related to specific data
conversations. A hub sends/floods all data to all ports. You'll need to
mirror a port or add a hub or network tap.
Like Jaap Keuter said:
Check the Wiki on CaptureSetup. It's probably a switch you're connected to.
http://wiki.wi
.exe, wireshark crashs upon startup but only
if I have either IP=0.0.0.0 or IP=169.254.xx.xx.
The easy way to cause the crash is:
ipconfig /release
Then start wireshark.
Yes, I often use wireshark when I have either IP=0.0.0.0 or
IP=169.254.xx.xx.
Thanks for your Time!
Brian Daniel
Marc,
Yes, Jaap is correct. Enabling the /3GB switch mentioned in
http://wiki.wireshark.org/KnownBugs/OutOfMemory is what made my
WireShark work better with my XP Pro and 4 GB RAM. I can open more of my
512MB capture files OK but others it crashes at around 65%. What the packets
are in the packet
wrote:
>
> On Apr 28, 2009, at 10:10 AM, Brian Daniel wrote:
>
> > I want to take max advantage of my quad processor and RAM. Will the
> > Windows-XP-Win64 build of WireShark take advantage of the additional
> > RAM if I upgrade my Windows Vista 64-bit from 4Gig RAM to 8
I want to take max advantage of my quad processor and RAM. Will the
Windows-XP-Win64 build of WireShark take advantage of the additional RAM if
I upgrade my Windows Vista 64-bit from 4Gig RAM to 8Gig RAM?
I'm going to try my hand at compiling the Win64 WireShark again. Are there
any options to set
Looking at http://buildbot.wireshark.org/trunk/waterfall the Windows-XP-x86
automated runs many more steps than the Windows-XP-Win64.
checked api
ran tests
created portableapps package
created u3 package
copied docs
built docs
I noticed this a while back and I waited a while before mentioning it.
Gerald,
Good job! On my Windows Vista 64-bit PC I got these results:
When I install wireshark-win32-1.1.4-SVN-28096.exe Destination Folder =
When I install wireshark-win32-1.1.4-SVN-29100.exe
Destination Folder = C:\Program Files (x86)\Wireshark
When I install wireshark-win64-1.1.4-SVN-29100.e
When I install wireshark-win32-1.1.4-SVN-28080.exe
Destination Folder = C:\Program Files\Wireshark
When I install wireshark-win32-1.1.4-SVN-28083.exe or
wireshark-win32-1.1.4-SVN-28084.exe or wireshark-win32-1.1.4-SVN-28085.exe
etc...
Destination Folder =
Thanks for your Time!
Brian
ems faster than
Windows. Ah... Oops, I just killed it. C++ error again. It seems to be my
huge .cap file that kills wirshark.
Thanks for your Time!
Brian
On Sat, Apr 18, 2009 at 2:36 PM, Brian Daniel wrote:
> Gerald,
>
> I've installed it on my Intel quad core 64-bit vista PC and
;ll try it Windows 7 Beta and let
you know.
Thanks for your Time!
Brian Daniel
706-507-8104
--
CONFIDENTIAL OR PRIVILEGED: This communication contains information
intended only for the use of the individuals to whom it is addressed and may
contain information that is privileged, confidential, or e
Someone has done great work and I can hear G711 calls but can not hear G729
calls. I’m running wireshark-win32-1.1.4-SVN-28054.exe which seems stable so
far. I have set preferences for RTP and change "Treat RTP version 0 packets"
into T.38 packets. Our VoIP traffic uses some G.711 and mostly G.729.
Sanjeeb,
If you have the option, I recommend forcing G711 for any FAX even though it
takes more bandwidth.
Good Luck,
Brian
2009/4/7 Deka Sanjeeb Kumar-KHBJ46
> Hi All,
>
> I was trying to send FAX over IP network.
>
> I enabled G729 and t.38 codec on both endpoints.
>
> While checking the Wir
CPU=i386 failed also CPU=AMD64
Systems available to me:
Intel E6550, 4Gig RAM, XP Pro 32-bit (wireshark win32 worked)
Intel Q6600, 4Gig RAM, Windows Vista 64-bit Home Prem
Intel T7500, 3Gig RAM, XP Pro 32-bit + Windows 7 beta 64-bit
offline 6 pending for Windows-XP-Win64
http://buildbot.wireshar
Jon,
Is your goal to output directly from wireshark into a MySQL database instead
of a .cap file? Then be able to generate .cap files out of the database
based on date, time range, and other standard filters. Keep us posted on
your progress.
For now, I have to capture 40 .cap files each at 512 Me
Thanks everyone for your help!
I truely had to very carefully read every line of that
http://www.wireshark.org/docs/wsdg_html/#ChSetupWin32 part of the
WiresharkDeveloper's Guide.
I compiled a wireshark win32 and it runs as expected!
Lesson learned: Read the documentation carefully!
I list these
OK, this is the part I was getting confused on...
Don't use Cygwin's gcc!
yet it tells me to
2.2.2. Install Cygwin
Download <http://www.cygwin.com/setup.exe> the cygwin installer and start
it.
Trying it...
On Tue, Mar 17, 2009 at 9:06 AM, Brian Daniel wrote:
> Thanks Gera
be doing something really OS level dumb because, rm -rf (directory)
is a linux command but I'm using XP Pro 32-bit to try and compile wireshark
as win32 and win64.
Thanks,
Brian
On Wed, Mar 11, 2009 at 5:40 PM, Brian Daniel wrote:
> Cool thanks folks! Since http://buildbot.wireshark.org/trunk/w
. I just checked in a change to use
> WIRESHARK_TARGET_PLATFORM (note the fixed spelling) instead of PLATFORM.
>
> Config.nmake sets CPU according to WIRESHARK_TARGET_PLATFORM. You shouldn't
> have
> to set it yourself.
>
> Brian Daniel wrote:
> > Yep, turns out
Yep, turns out I need to keep my setting: Platform=BPC
Should I use WIRESHRK_TARGET_PLATFORM=win64 ??
For now, I'll try to temporarily change to Platform=win32 or win64 each time
I launch the cmd.exe
Also, what CPU= should I put for my Intel Core2 Quad Q6600?
x86 is a solution for a very old Intel
Thanks Gerald! Where is the list of CPU abbreviation codes? such as AMD64?
I didn't think it would care about the CPU since I've currently left it
selected CPU=win32.
I'm currently on a Core2 Duo CPU E6550 running XP Pro SP3
Once this works on win32 (known to usually work), I'll also try this on my
21 matches
Mail list logo
