Http response code 503 errors due to DRM not correctly detected by HDHR

So I was trying to figure out why several items that I had scheduled were not recording as expected.

It seems that unfortunately the “DRM” detection is not always correct on the Prime. In this particular case, it seems that the HDHR is NOT detecting that channel 606 is DRM. Channels will try to stream, but will get an error 503. The TA responds with “Channel is temporarily unavailable” and the hdhr responds with “rejecting request from 192.168.1.223 - no video data”

The only way around it is to manually disable the channel from either the HDHR web interface or the DVR interface…

Validated that it is not a channels issue by using VLC to try to stream the channel from that tuner. Other channels (702, 704, 711) all streamed OK.

606 is STARZHD here (which is understandably DRM protected…) but as mentioned, unfortunately was not being auto detected as DRM by the HDHR and thus neither could Channels DVR on its own.

BTW during this time period there was no other tuner activity on this unit (all three tuners were available). The next scheduled item was 4 hrs away.

– [times are not exact between HDHR and Channels logs… but the items are the same repeating]

HDHR log Snippet:
20170212-19:00:03 HTTP: rejecting request from 192.168.1.223 - no video data
20170212-19:00:32 CableCARD: tr/resolve_tuning_rsp timeout error (cchost_tr_resolve_tuning:34)
20170212-19:00:32 HTTP: rejecting request from 192.168.1.223 - no video data
20170212-19:53:25 Tuner: tuner0 streaming rtp to 192.168.1.177:53287
20170212-19:53:30 CableCARD: tr/resolve_tuning_rsp timeout error (cchost_tr_resolve_tuning:34)
20170212-19:53:31 CableCARD: message: Requested channel is temporarily unavailable. Please try again later.


Channels Log snippet:

2017/02/12 10:50:02 [DVR] Starting job 1486920870-ch606 Get a Job (2016) on ch=[606]
2017/02/12 10:50:02 [DVR] Waiting 5h39m27.879827786s until next job 1486945770-ch702
2017/02/12 10:50:07 [ERR] Failed to start stream on channel 606 via 13175861: got http response code 503
2017/02/12 10:50:07 [DVR] Error running job 1486920870-ch606: could not start stream on channels=[606]: got http response code 503
2017/02/12 10:50:31 [DVR] Starting job 1486920870-ch606 Get a Job (2016) on ch=[606]
2017/02/12 10:50:31 [DVR] Waiting 5h38m58.893415745s until next job 1486945770-ch702
2017/02/12 10:50:36 [ERR] Failed to start stream on channel 606 via 13175861: got http response code 503
2017/02/12 10:50:36 [DVR] Error running job 1486920870-ch606: could not start stream on channels=[606]: got http response code 503
2017/02/12 10:50:37 [DVR] Starting job 1486920870-ch606 Get a Job (2016) on ch=[606]
2017/02/12 10:50:37 [DVR] Waiting 5h38m52.777331326s until next job 1486945770-ch702
2017/02/12 10:50:42 [ERR] Failed to start stream on channel 606 via 13175861: got http response code 503
2017/02/12 10:50:42 [DVR] Error running job 1486920870-ch606: could not start stream on channels=[606]: got http response code 503
2017/02/12 10:51:06 [DVR] Starting job 1486920870-ch606 Get a Job (2016) on ch=[606]

Does re-scanning on the PRIME detect the DRM status?

Sounds like a HDHR firmware bug if not. Nothing we can do about it on our end.

Yup… I understand it may not be a channels issue… but others may need to be aware of the scenario in case they see the same symptoms with missed recordings

Rescanning on that unit does not redetect. There were also at least 3 other channels that have the same behavior. Rescanning on a different unit also does not show 606 as DRM either with the same results. Interestingly… there was one channel that was detected as DRM on the first unit, but not DRM on a different unit (channel was DRM)

I do have 4 primes on the system… but that should not be relevant. All primes are FW 20161117. At first I thought that it was a bad CC or TA, but the issue was happening with multiple primes.

Provider: Charter Cable (now Spectrum)
CC: Cisco (Scientific Atlanta)
TA: Cisco

Please report to [email protected] or on their forums. I suspect it has something to do with the TA, but I have no idea.