Hello, I have about 125 Brightsign units and when I republished 2 of them they stopped sending out their UDP status commands. For example PLAYING* is sent out so we know all is well through our Medialon controller. Is there something I may be missing in the setup file of the BrightSign that is stopping outbound commands? I have republished from known working .brs files and I still do not see either of the two problem units reporting out via Wireshark traces. I am able to UDP to them and reboot them. Just hoping it's something in my set-up file I'm forgetting. Is there a sample of a set-up file I can compare to mine? I feel like I've tried every option possible at this point. Thanks!
Date
Votes
5 comments
-
Lyndon There's no setup option that affects udp. It would be something in the presentation itself.
are you using a script only for playback? or html? some cms? brightauthor?
No udp messages get sent out? but it receives udp fine?
-
patrick131 We use Brightauthor to setup/build the scripts. I thought it may be a bad set up file, so I swapped the media into a known working bright author file and still had no luck. Yes, it receives reboot and play commands and responds accordingly, when the Medialon sends a STATUS there is no response from the bright sign. We have also replaced the bright sign with a different player with the same result republishing multiple times with different known working bright author files. Medialon report that it opens the connection and sees the player but is not getting the return of PLAYING* status out of the player. We are also not seeing it in a wireshark as we do with the other 125 players. The other difficult part of trouble shooting it is that there are other players in the same area on the same switch that work. Very strange, appreciate any ideas you might be able to offer.
-
Lyndon Do you have a copy of the log tab from the player that' not working properly? If you publish, and enable debugging to the system log from the publish tab, the log tab will have more details about what's happening while the unit listens for udp commands. Please send a copy of your brightautor project to support@brightsign.biz.
-
patrick131 Thanks Lyndon I sent the files to the support email.
-
patrick131 Lyndon, were you able to learn anything from the log files I sent? We've had some time over the past few days and have gotten back into this issue. We see in the logs that the player is seeing the STATUS? and reports UDP Event PLAYING* but even connected directly with a hub to the device (172.18.25.200), we are not seeing PLAYING* actually leave the device. What we see is startPlayback to 224.0.200.200.
Other test examples:
118working-udp-mcast == 172.18.25.118 is sending UDP 5000 packets to 224.0.200.200 (MULTICAST). Data is startplayback.
118working-udp-bcast== 172.18.25.110 is sending UDP 5000 packets to 255.255.255.255 (BROADCAST) Data is PLAYING
200notworking-udp-mcast== 172.18.25.200 is sending UDP 5000 packets to 224.0.200.200 (MULTICAST). Data is startplayback.
[ 49.904] TIME: Probe = 0.020279
[ 49.905] *** 00:00:06.827 b_objdb_class: Class:'NEXUS_AudioInput' count:9 live:9
[ 49.908] TIME: ConfigureResources = 0.023774
[ 49.933] + Creating roDatagramSender
[ 49.934] + 2019/08/19 13:50:21.385
[ 49.934] + ### Launch playback
[ 49.934] + Bootup: entry signal
[ 49.935] + UDP notification sent: startPlayback
[ 49.936] + 2019/08/19 13:50:21.387
[ 49.936] + msg received - type=roAssociativeArray
[ 51.200] + 2019/08/19 13:50:22.652
[ 51.201] + msg received - type=roDatagramEvent
[ 51.201] + UDP Event PLAYING*
[ 53.186] + 2019/08/19 13:50:24.637
[ 53.186] + msg received - type=roDatagramEvent
[ 53.187] + UDP Event PLAYING*There is no traffic from 172.18.25.200, UDP 5000 to 255.255.255.255 (BROADCAST)
Please sign in to leave a comment.