> [mailto:
wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Munish Dayal
> Sent: 03 September 2009 13:38
> To:
wireshark-dev@xxxxxxxxxxxxx
> Subject: Re: [Wireshark-dev] Need help in Decoding RTP
> Multiplex streamsinWireshark
>
>
> Hi,
>
> Is this dissector code for "RTP multiplexed streams"
> submitted to Wireshark ?
> What is the bug number ?
>
> Thanks,
> Munish
>
> -----Original Message-----
>
> Message: 5
> Date: Fri, 28 Aug 2009 18:20:28 +0100
> From: "Neil Piercy" <
Neil.Piercy@xxxxxxxxxxxx>
> Subject: Re: [Wireshark-dev] Need help in Decoding RTP Multiplex
> streams inWireshark
> To: "Developer support list for Wireshark"
> <
wireshark-dev@xxxxxxxxxxxxx>
> Message-ID:
>
> <
CEDCBB894168244E9C8BD430E1E9F1AB037156A2@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> ip.access have developed a basic dissector for this protocol
> which we will happily add to the project - I'll raise a bug
> report and attach the file.
>
> At present it only handles the uncompressed RTP header case,
> but should provide a starting point for further development.
>
> BTW we have called the protocol nb_rtpmux, as the 29.414 spec
> is originally for the Nb interface.
>
> Regards,
> Neil
>
>
> =================================================
> ip.access ltd Tel: 01954 713715
> Building 2020, Fax: 01954 713799
> Cambourne Business Park,
> Cambourne,
> Cambridge, CB23 6DW, UK
> Company Registered Number 3400157
> Visit the website at
http://www.ipaccess.com
> <
http://www.ipaccess.com/>
> =================================================
>
>
>
>
>
> ________________________________
>
> From:
wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:
wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of shruti singh
> Sent: 27 August 2009 12:36
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Need help in Decoding
> RTP Multiplex streams inWireshark
>
>
> Hi,
>
> Yes RTP multiplexing is in compliance to 3GPP TS
> 29.414 Release
> 7 specification
>
> thanks
> Shruti
>
>
> On Wed, Aug 26, 2009 at 7:58 PM, Jaap Keuter
> <
jaap.keuter@xxxxxxxxx> wrote:
>
>
> Hi,
>
> Is there an RFC on that? Are there sample
> captures to work with? This always helpsin development.
>
> Thanx,
> Jaap
>
> Now competing at
http://www.ec2009.info
>
> On 26 aug 2009, at 07:36, shruti singh
> <
shruti.is.singh@xxxxxxxxx> wrote:
>
>
>
> Hi
>
> I need to decode RTP Multiplex
> streams using wireshark. Presently we can decode only Non
> -Multiplexed RTP streams in wireshark.
>
>
> A multiplexed voice packet is
> composed by concatenating RTP encapsulated voice packets and
> IP and UDP headers.
>
> Below is the Multiplex Packet format
>
>
>
> IP
>
> UDP
>
> Multiplex Header
>
> Compressed RTP Header
>
> RTP Payload
>
> Multiplex Header
>
> Compressed RTP Header
>
> RTP Payload
>
>
>
> This Multiplex header is repeated in
> beginning of each RTP packet. So I was thinking of way to
> extract this multiplex header & use it to decode each RTP
> packet following this Multiplex header.
>
> I supose we need to make a dissector
> packet-rtpmultiplex.c regestring to a UDP port as a starting point.
>
>
>
> Dissect the multiplex header,
> decompress the rtp header and have the RTP dissector dissecting
> the resulting "RTP packet" - decompressed
> header+data.
>
> Could you help me in dissecting the
> multiplex header and make this work.
>
>
>
>
> Also I need to know the steps to
> write our own filters in wireshark
>
>
>
>
> It would be great help. Kindly reply
> as soon as possible
>
>
>
>
> Regards
>
> Shruti
>
>
> >>>>>>>>>>>>>>
>
>
>
>
>
>
>
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is
> intended solely for the use of the individual to whom it is
> addressed. It may contain privileged or confidential
> information and should not be circulated or used for any
> purpose other than for what it is intended. If you have
> received this message in error,please notify the originator
> immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using,
> copying, altering, or disclosing the contents of this
> message. Aricent accepts no responsibility for loss or damage
> arising from the use of the information transmitted by this
> email including damage from virus."
> ______________________________________________________________
> _____________
> Sent via: Wireshark-dev mailing list <
wireshark-dev@xxxxxxxxxxxxx>
> Archives:
http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev
>
> mailto:
wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
>
