Pelco Developer Network (PDN)

Differences in Integration Strategies Between DS and Endura

Digital Sentry (DS) and Endura support different Pelco API Web services, making for significant differences in integration strategies. Whereas Endura consists of multiple, distributed components, it may help to imagine DS as a self contained environment.  A DS server is essentially its own system manager, recording device, and multi-channel encoder; every camera or edge device connected to the DS has its own service ID or channel number, as if connected to a multi-channel encoder as well.

System Manager Locator

While Endura products support the System Manager Locator service, allowing devices to obtain the address of the system manager, DS products do not.  You must know the address of the DS Server with which you want to communicate.

Camera/Edge Device Communication

In an Endura environment, it is expected that you will communicated directly with cameras and edge devices.  DS supports the Camera Configuration, Lens Control, Motion Detection, and Positioning Control services, and it is expected that you will employ these services through DS to interact with cameras and edge devices, rather than interacting with the devices directly.

Addressing and Port Usage

All communications with a DS server will take place through the same address using different ports to utilize various services available on the server.  The system manager service of the DS uses port 60001; the recorder/video playback service uses port 60002; and camera interactions are routed through port 60010.


The DS RTSP URL format is described here.