We have a threshold configuration setup for 467 Slice Request (opid 0x0101) with severity “Info”. TAG appears to capture that request correctly from the source (in this case 2110 from IPFM.) In notification configuration we have “Purple” setup for info in the Display field. In the purple configuration we have draw border ON and Draw Text ON. The Decay time is set to 58 (which is supposedly seconds as described in online documentation). For station KASA, sourcing TNET 22X the notification lasts about 19 seconds. For station WWDT sourcing TNET 20X the notification lasts about a second. Both sources have thresholds “TNET ALARMING” and both sources have the same notifications “Operations Alarming Hub”. Please advise.
Hi Scott, thanks for reaching out!
From the screenshots it seems the RED color border is working as expected as it stays lit after the purple is gone, is that so? what’s the decay configuration on the red and what severity it’s configured to?
Did yout try to put that purple color on another serverity, or the red color on the “info” and see what happens?
If you’ve tried all that and the behavior is still not as expected we will need to reproduce that in the lab, can you please open a bug report containing all the information from your findings, your MCS and MCM versions, along with the MCS database export?
Thanks
Nir
Hey Nir, apologies for the confusion. Please ignore the red. That is a PCR source. The TNET sources are the tiles receiving SCTE splice requests. The decay time is set to 58 seconds. The text in the window lasts the full 58 (I recently changed to :59 to no avail) but the border only lasts 19 seconds, or sometimes only a flash. I need both the text and the border to be “pepto pink” for the full :59 seconds to indicate the TNET has received a splice request and is in a 1 minute local avail. Draw border and draw text are both selected in the Notification configuration agent.
To answer other questions, we are running MCS 1.3.1-25.03.05.01. MCMs are 6.5.3. We tried to upgraded to 6.7 for QC station capability but ran into bridging issues.


