# detecting consumer closed/ track ended

**URL:** <https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592>\
**Category:** mediasoup libraries\
**Created:** [February 24, 2020, 1:48pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592 "2020-02-24T13:48:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Codeda](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@Codeda](https://mediasoup.discourse.group/u/Codeda)\
**Post date:** [February 24, 2020, 1:48pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592/1 "2020-02-24T13:48:08Z")

</div>

Is there any way to detect on client that consumer was just closed on server? [https://mediasoup.org/documentation/v3/mediasoup-client/api/#consumer-on-trackended](https://mediasoup.org/documentation/v3/mediasoup-client/api/#consumer-on-trackended) - never firing.  
`consumer.track.addEventListener('ended'` not working too.

---

<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:** [February 24, 2020, 1:53pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592/2 "2020-02-24T13:53:42Z")

</div>

Listen on server side for “transportclose” and “producerclose” in the Consumer and notify the client. This is explained in the doc.

---

<div class="post-metadata">

**Author:** ![Codeda](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@Codeda](https://mediasoup.discourse.group/u/Codeda)\
**Post date:** [February 24, 2020, 1:56pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592/3 "2020-02-24T13:56:18Z")

</div>

So, without pubsub system it’s imposible?

---

<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:** [February 24, 2020, 2:03pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592/4 "2020-02-24T14:03:09Z")

</div>

Well, you’ve seen that “trackended” is not emitted, right? We cannot do magic.

---

<div class="post-metadata">

**Author:** ![Codeda](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@Codeda](https://mediasoup.discourse.group/u/Codeda)\
**Post date:** [February 24, 2020, 2:23pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592/5 "2020-02-24T14:23:25Z")

</div>

Track was stopped on publisher’s side, then producer and it’s consumer were closed on server. Why it’s not emmiting?

---

<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:** [February 24, 2020, 2:28pm UTC](https://mediasoup.discourse.group/t/detecting-consumer-closed-track-ended/592/6 "2020-02-24T14:28:41Z")

</div>

Ask browser vendors and those who make the WebRTC specification. I won’t use this forum as a generic WebRTC forum.