Re: [Wireshark-dev] Support Opus in WireShark

2020-01-20 Thread Peter Wu
On Mon, Jan 20, 2020 at 06:19:54PM +, Jiří Novák wrote: > Dear Roland, > > > I can provide some examples if needed, of exactly that. Either multiple > > OPUS streams, or traces which contain opus and G.711 in the same > > conversation. Just tell me, if you need a new bug-entry created or have

[Wireshark-dev] Q about reassembly.

2020-01-20 Thread Christian Hopps
So with IPTFS (https://tools.ietf.org/html/draft-ietf-ipsecme-iptfs-00) I've got basically a packet stream inside an IPsec/ESP datagram packet stream. I've built various data structures to track out of order etc fragments as I get called for dissecting each IPTFS payload. When there's a full pac

Re: [Wireshark-dev] Support Opus in WireShark

2020-01-20 Thread Jiří Novák
Dear Roland, > I can provide some examples if needed, of exactly that. Either multiple > OPUS streams, or traces which contain opus and G.711 in the same > conversation. Just tell me, if you need a new bug-entry created or have > an existing one to attach to. It would be nice if you can create it

Re: [Wireshark-dev] Support Opus in WireShark

2020-01-20 Thread Roland Knall
I can provide some examples if needed, of exactly that. Either multiple OPUS streams, or traces which contain opus and G.711 in the same conversation. Just tell me, if you need a new bug-entry created or have an existing one to attach to. kind regards Roland Am Mo., 20. Jan. 2020 um 12:30 Uhr sch

Re: [Wireshark-dev] Support Opus in WireShark

2020-01-20 Thread Jiří Novák
Dear Ryan, > Using C++ default parameter because I want to use Opus FEC.  When a RTP > packet lost, I need to use the next packet’s data to recovery the lost > data. But the decoder module only have data ,can’t get the neighbor > packet’s information. So I modified  the rtp_audio_stream.cpp to pla