Re: [Wireshark-users] Some questions about dissecting EVS protocol

a possibility that the first byte of speech data can also have the "F bit" set to 1, so it is misunderstood as Toc byte? I just realised I made a silly mistake, and very sorry for causing inconvenience! Best Regards Nan Xiao On Fri, Oct 15, 2021 at 5:30 PM Nan Xiao wrote: > Hi Commu

[Wireshark-users] Some questions about dissecting EVS protocol

st TOC byte. I am just wondering if there is a possibility that the first byte of speech data can also have the "F bit" set to 1, so it is misunderstood as Toc byte? Hope someone can give me some advice! Thanks very much in advance! Best Regards Nan Xiao

Re: [Wireshark-users] Is it possible to specify dynamic payload type in tshark?

Hi Jaap, It worked! Thanks very much for your time and help! Best Regards Nan Xiao On Wed, Oct 13, 2021 at 8:55 PM Jaap Keuter wrote: > Hi, > > Have a look in your preferences file. There you’ll find an entry for > evs.dynamic.payload.type. Use that on the command line with -o

[Wireshark-users] Is it possible to specify dynamic payload type in tshark?

it is possible to do the same thing through tshark. i.e., I tried to use following command: $ ./run/tshark -r ~/evs.pcapng -d proxyLoc(udp).port==20956,evs tshark reported error: tshark: Protocol "evs" isn't valid for layer type "proxyLoc(udp).port". The pcap file is attached for re

Re: [Wireshark-users] Why does wireshark decode my RTP data as "RTP Events"?

Hi Sake, Yes, it actually worked after disabling the rtpevent protocol. Thanks very much for your time and help! Best Regards Nan Xiao On Thu, Sep 30, 2021 at 5:24 AM Sake Blok | SYN-bit wrote: > Hi Nan Xiao, > > Payload type 101 is dynamic, which means it can be any codec, but it ha

[Wireshark-users] A question about calculating "Mean Jitter" KPI for RTP flow

ly, I submitted an issue in gitlab before ( http://gitlab.com/wireshark/wireshark/-/issues/17600), but unfortunately, it seems no one noticed it. So very sorry for reposting here, and hope someone can help to clarify it. Thanks

Re: [Wireshark-users] Why does wireshark decode AMB-WR data as "Octet-Aligned Mode" instead of "Bandwidth-Efficient Mode"?

Hi Guy, Got it, thanks very much for your time and quick response! Best Regards Nan Xiao On Tue, Sep 21, 2021 at 4:54 PM Guy Harris wrote: > > On Sep 21, 2021, at 1:17 AM, Nan Xiao wrote: > > > I have an original pcap file whose RTP payload type is AMR-WB, and it > > use

[Wireshark-users] Why does wireshark decode AMB-WR data as "Octet-Aligned Mode" instead of "Bandwidth-Efficient Mode"?

e the data as "Bandwidth-Efficient Mode", but the wireshark still decodes the AMR-WB encoding as "Octet-Aligned Mode". Could anyone advise me on this issue? Thanks very much for your time in advance! (The pcap file is attached) Best Regards Nan Xiao amr-octet-align=0