["Mark Lewis" <mlewis@xxxxxxxxxx>]

I have now completed my plugin. I would like to release it so that others can benefit from my efforts. What is the proceedure for releasing a new plugin?

 

I only have access to a Windows system, and therefore cannot test my plugin on other platforms.

---

From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Mark Lewis
Sent: 20 June 2006 10:04
To: Ethereal development
Subject: [Filter Test: P272621] RE: [Ethereal-dev] Dissector plug-in for Pro-MPEG CoP 3 r2(2dparityfec)

Thanks Anders and Jim,

 

I have just had a look at the AMR dissector and it will be very useful for me in solving this problem - thanks for the tip. Unfortunatly there is no control information sent to setup the protocol as no control channel is available in this application. Payload type 96 is always used.

 

I will add a preferences page similar to AMR to allow the dissector to be turned on and off, and I will default it to off. This should solve the problem.

 

Thanks,

 

Mark

---

From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Anders Broman (AL/EAB)
Sent: 20 June 2006 09:51
To: Ethereal development
Subject: RE: [Ethereal-dev] Dissector plug-in for Pro-MPEG CoP 3 r2(2dparityfec)

Hi,

If there is control information sent setting up the RTP connection you could use the mechanism used in the SDP dissector to set up a RTP converstion

and transfer data about the Media type used for that conversation.

 

The AMR dissector has a preference setting (default 0 = not used) to dissect a specified PT as AMR.

 

Brg

Anders

---

From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Mark Lewis
Sent: den 20 juni 2006 11:39
To: ethereal-dev@xxxxxxxxxxxx
Subject: [Ethereal-dev] Dissector plug-in for Pro-MPEG CoP 3 r2 (2dparityfec)

Hello,

 

I have developed a dissector plug-in for Pro-MPEG Code of Practice #3 release 2 FEC data (http://www.pro-mpeg.org/publications/pdf/Vid-on-IP-CoP3-r2.pdf). This protocol is for sending FEC data over RTP.

 

The protocol defines that this data is always sent with RTP payload type 96 (0x60). My plug-in currently recognizes all RTP traffic with payload type 96 as belonging to this protocol. However, payload type 96 is specified by RTP as dynamic and may be used for other purposes within other protocols. I don't want to issue my plug-in and then find that data of type 96 that is not Pro-MPEG FEC is then dissected as such.

 

Please could somebody suggest the a mechanism for dealing with this problem?

 

Thanks,

 

Mark

 

 

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev