# No audio is heard but RTP data is received **URL:** \ **Category:** mediasoup libraries\ **Created:** [February 10, 2020, 7:09pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566 "2020-02-10T19:09:29Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [February 10, 2020, 7:09pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/1 "2020-02-10T19:09:29Z")
I reported this previously as [Bytes are transferred but no real audio stream is received](https://mediasoup.discourse.group/t/bytes-are-transferred-but-no-real-audio-stream-is-received/126) and it is still happening (rarely) in my production and users are complaining about random failure in audio subscriptions. I’m wondering how can I trace the issue while I’m not able to reproduce it. ![audio-issue](https://global.discourse-cdn.com/free1/uploads/mediasoup/original/1X/aca4b766e66050e1ee3f9b1c077e57fa98da891d.jpeg) ---
**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 11, 2020, 11:42am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/2 "2020-02-11T11:42:23Z")
Did you actually follow [this](https://mediasoup.org/documentation/v3/mediasoup/api/#transport-consume)? ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [February 11, 2020, 2:09pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/3 "2020-02-11T14:09:14Z")
> [@ibc](#): > > Did you actually follow [this](https://mediasoup.org/documentation/v3/mediasoup/api/#transport-consume)? I believe I am and it’s working well for 99 percent of the time. However I can log the `rtpCapabilities` received from the client (web browser) if it’s the thing that I should be concerned about. ---
**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 11, 2020, 2:18pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/4 "2020-02-11T14:18:43Z")
No, that won’t help. You may try by forcing Chrome67 handler in your mediasoup-client apps (just when the browser is Chrome of course) which uses PlanB and see if the problem does not happen. However it’s super hard to figure out where the issue may be. BTW maybe you are trying to render remote audio **before** getUserMedia with audio succeed? If so some of your clients may run into the browser auto-play policy issues. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [February 11, 2020, 2:31pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/5 "2020-02-11T14:31:26Z")
> [@ibc](#): > > You may try by forcing Chrome67 handler in your mediasoup-client apps (just when the browser is Chrome of course) which uses PlanB and see if the problem does not happen. Then do you have any idea how to detect if the problem is solved? My only source at the moment is user feedbacks! Would checking data in the `rtp` trace event help? > [@ibc](#): > > BTW maybe you are trying to render remote audio **before** getUserMedia with audio succeed? If so some of your clients may run into the browser auto-play policy issues. I’ve handled the auto-play policy however it shouldn’t affect the received RTP stream and RTC stats, right? ---
**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 11, 2020, 2:39pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/6 "2020-02-11T14:39:10Z")
No, I have no idea if the problem has been solved. I don’t know if this is a problem in mediasoup or in your code. I’ve just never seen it. I suggested something but you seem to propose other checks. No, those won’t work. If you receive RTP in the browser but it does not produce audio, the issue won’t be detected by checking the stats or trace event which will just confirm you that the browser is receiving RTP packets. ---
**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 11, 2020, 2:40pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/7 "2020-02-11T14:40:20Z")
However you can check the browser stats and check whether there are decided bytes or not for that incoming audio track. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [February 11, 2020, 3:07pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/8 "2020-02-11T15:07:51Z")
> [@ibc](#): > > I suggested something but you seem to propose other checks. I’ll try your suggestion of course but before that I think I need a way to detect the issue. Then I can log when it happens and maybe I can find a particular scenario for that. > [@ibc](#): > > However you can check the browser stats and check whether there are decided bytes or not for that incoming audio track. Good idea 👌. For that I need to collect user stats/logs some where for later analysis. ---
**Author:** ![smoke](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/smoke/32/187_2.png) [@smoke](https://mediasoup.discourse.group/u/smoke)\ **Post date:** [February 12, 2020, 6:04pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/9 "2020-02-12T18:04:30Z")
We have similar reports from users, that are so sporadic it is difficult to reproduce @mkh what versions do you use? ---
**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 12, 2020, 6:30pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/10 "2020-02-12T18:30:50Z")
> [@smoke](#): > > what versions do you use? The version is irrelevant. Let’s please focus on this: > [@No audio is heard but RTP data is received](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/4): > > No, that won’t help. You may try by forcing Chrome67 handler in your mediasoup-client apps (just when the browser is Chrome of course) which uses PlanB and see if the problem does not happen. However it’s super hard to figure out where the issue may be. BTW maybe you are trying to render remote audio before getUserMedia with audio succeed? If so some of your clients may run into the browser auto-play policy issues. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [March 10, 2020, 6:54am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/11 "2020-03-10T06:54:57Z")
I could reproduce the issue. It does not happen with Chrome67 handler (as you advised 👌). Firefox is fine too. Is it safe to force Chrome67 in production until the issue is fixed? How about users with chrome \< 67? ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [March 10, 2020, 7:26am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/12 "2020-03-10T07:26:32Z")
BTW there is mistype in the [docs](https://mediasoup.org/documentation/v3/mediasoup-client/api/#DeviceOptions) I couldn’t find in github repo to submit pr: `const device = new mediasoupClient.Device({ handlerName: "Chrome67" });` Fix: `const device = new mediasoupClient.Device({ Handler: "Chrome67" }); ` ---
**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:** [March 10, 2020, 8:23am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/13 "2020-03-10T08:23:02Z")
No, it’s ok. The change was announced here. ---
**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:** [March 10, 2020, 8:25am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/14 "2020-03-10T08:25:39Z")
Which exact issue? ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [March 10, 2020, 9:00am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/15 "2020-03-10T09:00:22Z")
> [@ibc](#): > > No, it’s ok. The change was announced here. What change are you talking about? > [@ibc](#): > > Which exact issue? The issue that the topic has been created for: No audio is heard but RTP data is received. ---
**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:** [March 10, 2020, 9:22am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/16 "2020-03-10T09:22:29Z")
> [@mkh](#): > > What change are you talking about? It was not announced as I thought, sorry. BTW the API docs follow the latest version. Probably you are not using it so you still need to use previous syntax. > [@mkh](#): > > The issue that the topic has been created for: No audio is heard but RTP data is received. Yes, the issue. Not sure how to fix something that I’ve never experimented without any way to reproduce it not specific details about what’s wrong. I’m afraid the issue won’t be fixed automagically. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [March 10, 2020, 9:37am UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/17 "2020-03-10T09:37:15Z")
> [@ibc](#): > > Yes, the issue. Not sure how to fix something that I’ve never experimented without any way to reproduce it not specific details about what’s wrong. I’m afraid the issue won’t be fixed automagically. Okay I’ll help to reproduce and fix the issue since it matters for me too but before that I’ll appreciate if you could help me for a quick fix since our users are suffering from the issue. Is it safe to force Chrome67 handler (PlanB) in production until the issue is fixed? Is there any incompatibility concerns? How about users with chrome \< 67? ---
**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:** [March 10, 2020, 12:04pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/18 "2020-03-10T12:04:22Z")
> [@mkh](#): > > Okay I’ll help to reproduce and fix the issue since it matters for me too but before that I’ll appreciate if you could help me for a quick fix since our users are suffering from the issue. > [@mediasoup and mediasoup-client 3.5.2 released (IMPORTANT)](https://mediasoup.discourse.group/t/mediasoup-and-mediasoup-client-3-5-2-released-important/631): > > mediasoup 3.5.2 enables RTP MID extension in RTP sent by mediasoup to remote consumers. This is an improvement that may eventually become mandatory in the WebRTC specification (it’s already mandatory in fact). For more information about this topic, read the corresponding discussion and encountered problems that motivated this feature: [https://github.com/versatica/mediasoup/issues/360](https://github.com/versatica/mediasoup/issues/360) This addition should also fix some “no audio” issues that some users are experimenting in the last weeks. (whic… > [@mkh](#): > > Is it safe to force Chrome67 handler (PlanB) in production until the issue is fixed? Is there any incompatibility concerns? How about users with chrome \< 67? Sorry, too many questions. Read the code, check the handlers, compare them, check the limitations in older handlers, etc. I’m not being paid for giving that much free consultancy. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [March 10, 2020, 1:11pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/19 "2020-03-10T13:11:32Z")
Thanks, I’ll test the new version and let you know if the problem persists. Regarding the payment, I still don’t earn much from our small project but I will pay as soon as I can, sorry. Although I think reporting issues is one of the ways that help open source projects to grow. ---
**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:** [March 10, 2020, 1:19pm UTC](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566/20 "2020-03-10T13:19:32Z")
Yes, sure. You have helped us finding an important issue and have contributed helping others, so I was not looking at you in my other post 🙂 It’s just that we run out of time lately and cannot resolve so many questions. Some of them require that people inspect the code in certain cases (such as in order to know the limitations of using an older Chrome handler). Anyway, try 3.5.2 in server and client, please. And **ensure** clients are using 3.5.2. Note that mediasoup-client exports a `version` property via API. [Next page](https://mediasoup.discourse.group/t/no-audio-is-heard-but-rtp-data-is-received/566.md?page=2)