Pelco Developer Network (PDN)

Using RTSP with Pelco API / Digital Sentry

The forum did not include any body for your post ... so I'm unsure as to what you're asking for specifically.

Please look at this article for some help: Digital Sentry RTSP URL Format.

If you are having problems with this behavior and Digital Sentry, please post additional information for troubleshooting. You may need to reach out to Pelco Product Support for assistance with Digital Sentry and/or DS Pelco API to ensure that it is running properly.

RTSP Frameserver not working

Hello, thanks for the quick reply in any case! We have two DS NVRs setup to test with the Pelco API, and cannot get a stream using the RTSP URL's specified. We have installed the Frameserver Service and the Pelco API per the instructions, and are able to pull in the device.xml, etc. to determine the Device ID and UUID to use in the commands. When I try to start a stream in VLC, I get the following errors:

core debug: net: connecting to 192.168.1.101 port 554
core debug: connection succeeded (socket = 1496)
access_realrtsp warning: Cseq mismatch, got 1, assumed 0
access_realrtsp debug: rtsp connected
access_realrtsp warning: only real/helix rtsp servers supported for now
core debug: no access modules matched
core error: open of `rtsp://192.168.1.101/?deviceid=uuid:138ff713-12c9-4ff3-9a8f-30773f2cb356' failed
core debug: dead input
core debug: changing item without a request (current 0/1)
core debug: nothing to play

I am using the Pelco API bundle v7.16, and DS NVS v7.16.

Using Device ID also fails

If I use the URL example using the device ID (rtsp://192.168.1.101/?deviceid=128) it also fails, but does not give the Cseq mismatch error:

core debug: creating access 'rtsp' location='192.168.1.101/?deviceid=128', path='\\192.168.1.101\?deviceid=128'
core debug: looking for access module matching "rtsp": 21 candidates
core debug: net: connecting to 192.168.1.101 port 554
core debug: connection succeeded (socket = 1444)
access_realrtsp debug: rtsp connected
access_realrtsp warning: only real/helix rtsp servers supported for now
core debug: no access modules matched
core error: open of `rtsp://192.168.1.101/?deviceid=128' failed
core debug: finished input
core debug: dead input
core debug: changing item without a request (current 0/1)
core debug: nothing to play
qt4 debug: IM: Deleting the input

Either way, I get the 'no access modules matched' error... Both FrameServer and PelcoAPI services were running when I performed these attempts. Video looks fine within the DS ControlPoint.

Hello!

Thank you very much for the additional information and details. This information really helps a ton to see what you've done before, what you've tried, and what you're attempting to do. Thanks!

I performed these tests this morning with the Digital Sentry unit in our partner lab that is also running 7.16. There are only 2 cameras there, one analog and one digital, so the environment is pretty minimal.

I did have success in using deviceid=camera#, however in the case of both cameras attempting to use the UUID value failed to get the live stream using VLC.
rtsp://192.168.5.145/?deviceid=1 (for the analog input)
rtsp://192.168.5.145/?deviceid=128 (for the digital input)

This succeeded in obtaining live video using VLC. For the next steps, I would suggest enabling logging for the DS Pelco API service and Frame Server service to see if the logs indicate any possible errors that need to be investigate. I have seen instances where Windows Services indicates that the service is running, but the log reveals exceptions or errors that prevent proper functionality from occurring.

To enable logging, navigate to "C:\Users\DSNVSUser\AppData\Local\Pelco\DSPelcoAPI" and edit PelcoAPISettings.xml to "1". You can do the same for Frame Server at "C:\Users\DSNVSUser\AppData\Local\Pelco\DSFrameServer" and edit FrameServerSettings.xml to "1". After editing these files you must restart the services and the generated .log files should appear in their respective directories.

A common error is if the default username / password is changed. This has been an issue in the past that will show the service is running properly but the log files will show the errors. If this is the case, there is an article in the Pelco.com Knowledge Base here: How to Update DS Pelco API Password.

If you are still encountering problems, like before you can post here to see if we can help out ... though admittedly if it is a problem with the DS Pelco API service running properly, I may need to direct you to contact Pelco Product Support.

Thanks!

Problem solved

The issue was indeed that we had set a new password when installing the system - thank you for the help!

Sure thing, I'm glad that you were able to resolve the issue. Take care!

Thanks

Thanks for the information - I did change the default password so I'll start there. Much appreciated!