Specifications (for RTP multiplexing and header compression) are:
- 3GPP TS 29.414
- 3GPP TR 43.903
Interface is GSM A-interface over IP (BSC <-> MSC), BSSMAP controlled.
BR,
Munish
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Luis EG Ontanon
Sent: Friday, September 12, 2008 4:23 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query regarding RTP dissector in Wireshark
No, RTP MUxing is not yet supported, neither does header compression AFAIK.
In order to implement suppiort for that we need two things:
pointers to the specs and capture files to test it.
MUXing implementation cuold be prety complex as it might step way outside our framework for maintaining conversation info.
I guess you have Iu-Over-IP and/or GSM-over-Iu (is that a RANAP controlled BSC?) that no-one of the Wireshark developers have ever seen.
\Lego
On Fri, Sep 12, 2008 at 10:05 AM, Munish Dayal <munish.dayal@xxxxxxxxxxx> wrote:
> Hi,
>
> I have some questions regarding the RTP dissector in Wireshark.
>
> 1. Can WireShark decode multiplexed RTP (i.e. more than one RTP packet
> within one UDP packet)? Multiplexing Header according to 3GPP
> A-InterfaceOverIP-standard (AoIP) (This standardization document
> specifies an IP-based transport interface between the BSS and a Media
> Gateway in a 2G mobile network.)
>
> 2. Can the compressed RTP Header according to 3GPP AoIP-standard be
> decoded together with multiplexed RTP?
>
> Regards,
> Munish
>
> _______________________________________________
"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."
