# New ‘packet’ event in Data producers

**URL:** <https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411>\
**Category:** mediasoup libraries\
**Created:** [November 18, 2019, 3:59pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411 "2019-11-18T15:59:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vpalmisano](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/vpalmisano/32/43_2.png) [@vpalmisano](https://mediasoup.discourse.group/u/vpalmisano)\
**Post date:** [November 18, 2019, 3:59pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411/1 "2019-11-18T15:59:27Z")

</div>

Hi,  
I’m trying to listen to the new ‘packet’ event on a Data producer, but I can’t get anything. I think It works only for audio/video producers, right?

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [November 18, 2019, 4:05pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411/2 "2019-11-18T16:05:13Z")

</div>

Right. We cannot provide any useful info in the JS layer regarding SCTP packets since, anyway, we cannot provide the full data they contain (for that you need a real Node.js based `DataConsumer`).

---

<div class="post-metadata">

**Author:** ![vpalmisano](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/vpalmisano/32/43_2.png) [@vpalmisano](https://mediasoup.discourse.group/u/vpalmisano)\
**Post date:** [November 18, 2019, 4:08pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411/3 "2019-11-18T16:08:43Z")

</div>

Yes. I’m looking at the `Bot` code contained in the `mediasoup-demo` repository.

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [November 18, 2019, 4:40pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411/4 "2019-11-18T16:40:05Z")

</div>

BTW I’ve properly documented the “packet” event right now:

> **[mediasoup :: Debugging](https://mediasoup.org/documentation/v3/mediasoup/debugging/#packet-Event)**
>
> Cutting Edge WebRTC Video Conferencing

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [November 19, 2019, 4:57pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411/5 "2019-11-19T16:57:54Z")

</div>

BTW, if you are using `enablePacketEvent()`, sorry for this:

> [@mediasoup 3.3.3 released](https://mediasoup.discourse.group/t/mediasoup-3-3-3-released/418):
>
> mediasoup 3.3.3 has been released. Here the changes: Add consumer.setPriority() and consumer.priority API to prioritize how the estimated outgoing bitrate in a transport is distributed among all video consumers (in case there is not enough bitrate to satisfy them). Make video SimpleConsumers play the BWE game by helping in probation generation and bitrate distribution. Add consumer.preferredLayers getter. Rename enablePacketEvent() and “packet” event to enableTraceEvent() and “trace” event (so…

> Rename `enablePacketEvent()` and “packet” event to `enableTraceEvent()` and “trace” event (sorry SEMVER).

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [December 2, 2019, 11:11pm UTC](https://mediasoup.discourse.group/t/new-packet-event-in-data-producers/411/6 "2019-12-02T23:11:01Z")

</div>