{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/release-axis-ptz-queue-ownership-when-control-is-finished/", "item": { "id": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/", "slug": "release-axis-ptz-queue-ownership-when-control-is-finished", "url": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished.md", "json": "https://update.dsesecurity.com/api/v1/posts/release-axis-ptz-queue-ownership-when-control-is-finished/" }, "title": "Release Axis PTZ queue ownership when control is finished", "summary": "Review Axis PTZ queue ownership separately from motion commands. Use the documented request, query and drop operations and verify the intended handoff without assuming queue release stops camera movement.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-29T20:33:19+00:00", "modified_at": "2026-10-29T20:33:34+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 520, "potentially_affected": "Axis products exposing the documented Pan/tilt/zoom API interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends explicit acquisition, status and release transitions in the client, with motion-stop behavior reviewed independently.", "primary_source": { "name": "Axis Communications — Pan/tilt/zoom API", "url": "https://developer.axis.com/vapix/network-video/pantiltzoom-api/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: End the control session deliberately and check the resulting owner. Keep releasing a queue position separate from stopping motion and from accepting another operator’s camera view.

\n

Source fact: documented behavior

\n

Axis’s Pan/tilt/zoom API says its PTZ queue permits one controlling user at a time and prioritizes requests, with smaller priority numbers taking precedence.

\n

The queue API uses control=request to request ownership, control=query to inspect client status and control=drop to relinquish control or leave the queue.

\n

When control queueing is enabled for a video channel, the source limits PTZ control to the client that currently possesses it.

\n

What the source does not establish

\n

Do not infer that dropping ownership sends a motion-stop command, removes every queued client or changes another channel’s state. Confirm the actual channel, queue configuration and client identity handling. Keep physical movement, priority policy and safe operator handoff as separate checks.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends explicit acquisition, status and release transitions in the client, with motion-stop behavior reviewed independently.

\n
    \n
  1. Choose a supported camera and an attended clear test scene with two authorized clients. Record the intended channel and actual queue settings. Identify which client should control first and how each reports its queue state. Preserve the existing priority policy rather than altering user-group priorities merely to force a demonstration result.
    2. \n
  2. Use the documented request and query workflow for the first client. Keep a movement request separate from the evidence identifying the current owner. Ask the second client to make its expressly approved control request and retain both clients’ observations. Do not treat a rejected or waiting client as a device failure without examining the queue state.
    3. \n
  3. Stop any approved test movement through its supported control procedure, then release the first client’s ownership or queue position through the documented drop operation. Query the relevant client states again and verify the intended handoff with an operator. Clean up the test clients and restore the approved operator arrangement instead of leaving a background session unexplained.
    4. \n
\n

Verification and evidence

\n

Retain the channel, client references, queue settings, ownership requests, status observations and release outcome in one timeline. Record physical stop and the next operator’s control as distinct observations. Have another reviewer reconstruct the owner at each step without relying solely on the displayed picture.

\n

Use a proposed client fixture where a session ends without releasing its queue position. Require the implementation review to identify the missing release path and its supported handling. Keep disconnection and error recovery subject to the exact client design. No camera movement, queue handoff or universal disconnect behavior was tested for this article.

\n

Official references

\n\n

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.

\n", "content_text": "Bottom line: End the control session deliberately and check the resulting owner. Keep releasing a queue position separate from stopping motion and from accepting another operator’s camera view.\nSource fact: documented behavior\nAxis’s Pan/tilt/zoom API says its PTZ queue permits one controlling user at a time and prioritizes requests, with smaller priority numbers taking precedence.\nThe queue API uses control=request to request ownership, control=query to inspect client status and control=drop to relinquish control or leave the queue.\nWhen control queueing is enabled for a video channel, the source limits PTZ control to the client that currently possesses it.\nWhat the source does not establish\nDo not infer that dropping ownership sends a motion-stop command, removes every queued client or changes another channel’s state. Confirm the actual channel, queue configuration and client identity handling. Keep physical movement, priority policy and safe operator handoff as separate checks.\nApplicability questions\n\nWhich video channel and client identity should own the current session?\nWhat queue configuration and priorities actually apply?\nHow does the client query and release its position?\nWho verifies motion has stopped before the next approved operator takes control?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends explicit acquisition, status and release transitions in the client, with motion-stop behavior reviewed independently.\n\nChoose a supported camera and an attended clear test scene with two authorized clients. Record the intended channel and actual queue settings. Identify which client should control first and how each reports its queue state. Preserve the existing priority policy rather than altering user-group priorities merely to force a demonstration result.\nUse the documented request and query workflow for the first client. Keep a movement request separate from the evidence identifying the current owner. Ask the second client to make its expressly approved control request and retain both clients’ observations. Do not treat a rejected or waiting client as a device failure without examining the queue state.\nStop any approved test movement through its supported control procedure, then release the first client’s ownership or queue position through the documented drop operation. Query the relevant client states again and verify the intended handoff with an operator. Clean up the test clients and restore the approved operator arrangement instead of leaving a background session unexplained.\n\nVerification and evidence\nRetain the channel, client references, queue settings, ownership requests, status observations and release outcome in one timeline. Record physical stop and the next operator’s control as distinct observations. Have another reviewer reconstruct the owner at each step without relying solely on the displayed picture.\nUse a proposed client fixture where a session ends without releasing its queue position. Require the implementation review to identify the missing release path and its supported handling. Keep disconnection and error recovery subject to the exact client design. No camera movement, queue handoff or universal disconnect behavior was tested for this article.\nOfficial references\n\nPan/tilt/zoom API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "content_markdown": "Bottom line: End the control session deliberately and check the resulting owner. Keep releasing a queue position separate from stopping motion and from accepting another operator’s camera view.\n\n## Source fact: documented behavior\n\nAxis’s [Pan/tilt/zoom API](https://developer.axis.com/vapix/network-video/pantiltzoom-api/) says its PTZ queue permits one controlling user at a time and prioritizes requests, with smaller priority numbers taking precedence.\n\nThe queue API uses control=request to request ownership, control=query to inspect client status and control=drop to relinquish control or leave the queue.\n\nWhen control queueing is enabled for a video channel, the source limits PTZ control to the client that currently possesses it.\n\n## What the source does not establish\n\nDo not infer that dropping ownership sends a motion-stop command, removes every queued client or changes another channel’s state. Confirm the actual channel, queue configuration and client identity handling. Keep physical movement, priority policy and safe operator handoff as separate checks.\n\n## Applicability questions\n\n- Which video channel and client identity should own the current session?\n\n- What queue configuration and priorities actually apply?\n\n- How does the client query and release its position?\n\n- Who verifies motion has stopped before the next approved operator takes control?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends explicit acquisition, status and release transitions in the client, with motion-stop behavior reviewed independently.\n\n- Choose a supported camera and an attended clear test scene with two authorized clients. Record the intended channel and actual queue settings. Identify which client should control first and how each reports its queue state. Preserve the existing priority policy rather than altering user-group priorities merely to force a demonstration result.\n\n- Use the documented request and query workflow for the first client. Keep a movement request separate from the evidence identifying the current owner. Ask the second client to make its expressly approved control request and retain both clients’ observations. Do not treat a rejected or waiting client as a device failure without examining the queue state.\n\n- Stop any approved test movement through its supported control procedure, then release the first client’s ownership or queue position through the documented drop operation. Query the relevant client states again and verify the intended handoff with an operator. Clean up the test clients and restore the approved operator arrangement instead of leaving a background session unexplained.\n\n## Verification and evidence\n\nRetain the channel, client references, queue settings, ownership requests, status observations and release outcome in one timeline. Record physical stop and the next operator’s control as distinct observations. Have another reviewer reconstruct the owner at each step without relying solely on the displayed picture.\n\nUse a proposed client fixture where a session ends without releasing its queue position. Require the implementation review to identify the missing release path and its supported handling. Keep disconnection and error recovery subject to the exact client design. No camera movement, queue handoff or universal disconnect behavior was tested for this article.\n\n## Official references\n\n- [Pan/tilt/zoom API](https://developer.axis.com/vapix/network-video/pantiltzoom-api/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/", "url": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Release Axis PTZ queue ownership when control is finished", "item": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/#article", "identifier": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/", "url": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/", "headline": "Release Axis PTZ queue ownership when control is finished", "description": "Review Axis PTZ queue ownership separately from motion commands. Use the documented request, query and drop operations and verify the intended handoff…", "abstract": "Review Axis PTZ queue ownership separately from motion commands. Use the documented request, query and drop operations and verify the intended handoff without assuming queue release stops camera movement.", "articleBody": "Bottom line: End the control session deliberately and check the resulting owner. Keep releasing a queue position separate from stopping motion and from accepting another operator’s camera view.\nSource fact: documented behavior\nAxis’s Pan/tilt/zoom API says its PTZ queue permits one controlling user at a time and prioritizes requests, with smaller priority numbers taking precedence.\nThe queue API uses control=request to request ownership, control=query to inspect client status and control=drop to relinquish control or leave the queue.\nWhen control queueing is enabled for a video channel, the source limits PTZ control to the client that currently possesses it.\nWhat the source does not establish\nDo not infer that dropping ownership sends a motion-stop command, removes every queued client or changes another channel’s state. Confirm the actual channel, queue configuration and client identity handling. Keep physical movement, priority policy and safe operator handoff as separate checks.\nApplicability questions\n\nWhich video channel and client identity should own the current session?\nWhat queue configuration and priorities actually apply?\nHow does the client query and release its position?\nWho verifies motion has stopped before the next approved operator takes control?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends explicit acquisition, status and release transitions in the client, with motion-stop behavior reviewed independently.\n\nChoose a supported camera and an attended clear test scene with two authorized clients. Record the intended channel and actual queue settings. Identify which client should control first and how each reports its queue state. Preserve the existing priority policy rather than altering user-group priorities merely to force a demonstration result.\nUse the documented request and query workflow for the first client. Keep a movement request separate from the evidence identifying the current owner. Ask the second client to make its expressly approved control request and retain both clients’ observations. Do not treat a rejected or waiting client as a device failure without examining the queue state.\nStop any approved test movement through its supported control procedure, then release the first client’s ownership or queue position through the documented drop operation. Query the relevant client states again and verify the intended handoff with an operator. Clean up the test clients and restore the approved operator arrangement instead of leaving a background session unexplained.\n\nVerification and evidence\nRetain the channel, client references, queue settings, ownership requests, status observations and release outcome in one timeline. Record physical stop and the next operator’s control as distinct observations. Have another reviewer reconstruct the owner at each step without relying solely on the displayed picture.\nUse a proposed client fixture where a session ends without releasing its queue position. Require the implementation review to identify the missing release path and its supported handling. Keep disconnection and error recovery subject to the exact client design. No camera movement, queue handoff or universal disconnect behavior was tested for this article.\nOfficial references\n\nPan/tilt/zoom API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "datePublished": "2026-10-29T20:33:19+00:00", "dateModified": "2026-10-29T20:33:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/release-axis-ptz-queue-ownership-when-control-is-finished/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Release Axis PTZ queue ownership when control is finished" }, "articleSection": [ "IT", "Video Surveillance" ], "keywords": [ "IT", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 520, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Pan/tilt/zoom API", "url": "https://developer.axis.com/vapix/network-video/pantiltzoom-api/" } } ] } }