Setup guide
Everything Security Center needs before the camera can create a bookmark: the Web SDK role, an SDK certificate, a user with the right privilege, and the four values you type into the package.
AddCameraBookmark call on one or more cameras — a timestamped marker an operator can find on the
Security Desk timeline and search by text. Nothing is installed on the Security Center side; the camera is just
another Web SDK client.System → Roles → Add an entity → Role → Web-based SDK. Give it a name, pick the server, and note the
port and base URI it reports — the defaults are 4590 for HTTP and
4590/443 for HTTPS with base URI WebSdk. If the role already exists,
open it and read the values off the Properties tab rather than creating a second one.
Whatever this page shows is what the package needs — the address, port and base URI fields in the settings page map one-to-one onto it.
Web SDK requests are authenticated with a user and an SDK certificate. The package defaults to CamStreamer's connector certificate, the same one the original videoCheckpoint script ships with — leave the Application ID field empty to use it.
If your Security Center is licensed for your own SDK certificate, paste that string into the field instead. Either way it goes into the username, after a semicolon:
Authorization: Basic base64("<user>;<application id>:<password>")
This is the single most common cause of a 401 with no useful message — the certificate is not a header of its own.
A dedicated Security Center user is worth it — it keeps the camera's activity separate in the audit trail. It needs the Add bookmarks privilege and view access to the cameras you will bookmark; nothing else. Log in as that user once in Security Desk to clear any first-login password change.
On the camera, open the package UI and complete the Genetec Security Center panel:
https normally; https (no cert check) if the Web
SDK still serves a self-signed certificate
Web SDK address / portthe server and port from step 1
Base URIWebSdk unless you changed it
User / passwordthe user from step 3
Application IDempty = CamStreamer connector certificate
Camera GUIDsfilled in for you by Load cameras
Then, in order: Test connection → Load cameras → tick the cameras → Send test bookmark. All three use the values currently in the form, so you can prove the path before saving anything. Only then hit Save & restart.
One code can bookmark several cameras at once — useful when a checkpoint is covered by a reader camera and an overview camera.
The bookmark text is the code itself, optionally prefixed by a word of your choice
(CHECKPOINT 8404612031728). A prefix makes bookmarks from this camera easy to pick out of a text
search when several sources write to the same timeline.
If it doesn't work
Almost always the application ID: it must sit in the username after a semicolon. Next most likely is a user whose password change is still pending, or one without Add bookmarks.
A self-signed Web SDK certificate makes a normal HTTPS request fail. Switch the protocol to https (no cert check) — the package talks to Genetec over raw node TLS specifically so this option really works.
The Web SDK can answer 200 on a soft failure. The package reads Rsp.Status and shows whatever
came back in Last error — check there before assuming the network is at fault.