[Wireshark-users] How to see BSSGP

Hi All, I´ve captured data from a Gb over IP network and now I need to open all BSSGP traffic. However wireshark does not seem to recognize BSSGP PDUs Is there something that I´m missing? Or simply wireshark does not support BSSGP over IP. BR Juan

Re: [Wireshark-users] How to see BSSGP

Thanks Anders. Really helpful! Best regards Juan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Anders Broman Sent: Martes, 20 de Febrero de 2007 03:09 p.m. To: 'Community support list for Wireshark' Subject: Re: [Wireshark-users] How to see BSSGP

Re: [Wireshark-users] How to see BSSGP

It worked! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Martes, 20 de Febrero de 2007 06:52 p.m. To: wireshark-users@wireshark.org Subject: Re: [Wireshark-users] How to see BSSGP Thanks Anders. Really helpful! Best regards Juan -Original

Re: [Wireshark-users] Jitter wrong in wireshark?

Hi Anders, good question. I´m not sure but I guess is codec is PCMA G711 8KHz (will take a look during call setup in a couple of hours). However Payload type is 97 (0x61), and wireshark shows it as Payload type=Unknown According to the formula, jitter calculation depends on timestamps and

Re: [Wireshark-users] Jitter wrong in wireshark?

Hi Anders, Yes, your are right. Codecs affect jitter calculation because of the sampling frequency. In practice, it affects when calculating the timestamp to seconds. I.e: when multipling timestamp ticks to convert to seconds one must use the frequency sampling of the current codec. As

Re: [Wireshark-users] Jitter wrong in wireshark?

OK, Really usefull. Would be good to add an options menu for payload types and sampling frequencies in RTP Preferences for the cases when dynamic payload types are used. Unfortunately right now no time for the moment to do that. Thanks a lot for the help Juan -Original Message- From:

Re: [Wireshark-users] Wireshark and 2GB capture files

Hi Alex, I never used CentOS, however independently of the OS it is recommended not to grow up to much the files to keep them manageable. Otherwise it takes too much to process them. Using multiple files when doing the capture and limiting them to lets say 100MB (or less) you can handle that

[Wireshark-users] NSIP port ranges

Hi All, According to WS Preferences protocol NSIP can be mapped only to 2 UDP ports in order to be decoded as NSIP. Is there any way to map port ranges, or at least more than 2 ports to be decoded as NSIP? BR, Juan ___ Wireshark-users mailing list

[Wireshark-users] NSIP port Ranges

Hi All, According to WS Preferences protocol NSIP can be mapped only to 2 UDP ports in order to be decoded as NSIP. Is there any way to map port ranges, or at least more than 2 ports to be decoded as NSIP? BR, Juan ___ Wireshark-users mailing list

Re: [Wireshark-users] Estimate tcp packet loss from receiver end only

Hi, one way is, you can check the number (and cause if possible) of retransmitted packets exporting the tcp conversation for example to an excel. That will give you the amount of lost packets during the connection. I don´t know whether WS has an option to do this (I didn´t find that). Br, Juan

Re: [Wireshark-users] Understanding what I'm seeing

Hi, Be sure you do not have a firewall in your PC. Check it in Network Connections-Properties. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Luis EG Ontanon Sent: Miércoles, 10 de Octubre de 2007 01:25 p.m. To: Community support list for

Re: [Wireshark-users] help - write Data to flat file

Hi, may be you want to a File-Export to File and save it like plain TXT. BR Juan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Ken Vizena Sent: Jueves, 06 de Diciembre de 2007 11:05 a.m. To: [EMAIL PROTECTED];

Re: [Wireshark-users] Nondeterministic 200 ms delay between sends (5Frames per Sec)

Hi, I would check two things (may be you already did it): 1- Check whether both TCP channels keep connected during the whole process, or they´re reconnecting all the time. 2- Check whether the synch messages are doing well since it looks like a synchronization problem. BR, Juan