# Audio Out - sessionId bug?

**URL:** <https://discourse.nodered.org/t/audio-out-sessionid-bug/12840>\
**Category:** Dashboard\
**Created:** [2 July 2019 21:32 UTC](https://discourse.nodered.org/t/audio-out-sessionid-bug/12840 "2019-07-02T21:32:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kororos](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kororos/32/9830_2.png) [@kororos](https://discourse.nodered.org/u/kororos)\
**Post date:** [2 July 2019 21:32 UTC](https://discourse.nodered.org/t/audio-out-sessionid-bug/12840/1 "2019-07-02T21:32:28Z")

</div>

From the node-red-dashboard documentation:

> Messages coming from the dashboard **do** have a `msg.socketid` , and updates like change of tab, notifications, and audio alerts will be directed only to that session. Delete the `msg.sessionid` to send to all sessions.

First of all, it refers to both `msg.socketid` and `msg.sessionid`. Looking at the debug output, msg has only socketid.

But my problem is that although this is honored for notifications, for audio alerts it is not (i.e. audio out is played on all clients).

Is this a bug, or am I missing something?

Version of node-red-dashboard is 2.15.5