{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "item": { "id": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "slug": "translate-axis-event-namespaces-before-building-an-rtsp-filter", "url": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter.md", "json": "https://update.dsesecurity.com/api/v1/posts/translate-axis-event-namespaces-before-building-an-rtsp-filter/" }, "title": "Translate Axis event namespaces before building an RTSP filter", "summary": "Translate Axis event-declaration prefixes into the documented RTSP event-topic filter prefixes. Preserve the selected topic and message-content filter separately when checking event receipt.", "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:26+00:00", "modified_at": "2026-10-29T20:33:34+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 500, "potentially_affected": "Axis products exposing the documented Event data streaming interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends storing the device declaration, translated topic expression and optional content expression as separate reviewed fields.", "primary_source": { "name": "Axis Communications — Event data streaming", "url": "https://developer.axis.com/vapix/network-video/event-data-streaming/", "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: Keep the declared event identity and its RTSP subscription expression together. Resolve the namespace translation before treating a missing notification as proof that the physical event never occurred.

\n

Source fact: documented behavior

\n

Axis’s Event data streaming says event declarations use tns1 and tnsaxis, while event-topic filters use onvif and axis respectively.

\n

The documented stream carries XML event notifications over RTSP/RTP, and the workflow begins by querying supported event declarations.

\n

The source distinguishes the eventtopic topic filter from the eventcontent filter for message source, key and data elements.

\n

What the source does not establish

\n

Do not infer an identical subscription syntax for WebSocket or another transport. Confirm the actual device’s supported events and stream prerequisites. A translated expression is a configuration input, not proof of notification delivery, event continuity or a complete recording workflow.

\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 storing the device declaration, translated topic expression and optional content expression as separate reviewed fields.

\n
    \n
  1. Retrieve the supported event declaration from an authorized pilot device and preserve the relevant topic and field names. Copy identifiers from that response rather than deriving them from a friendly event label. Write the RTSP topic expression beside the declaration and explicitly check each namespace prefix against the documented translation.
    2. \n
  2. Review any content filter independently from topic selection. Identify whether each named item belongs to the message source, key or data. Use a proposed harmless input with a known expected field value, and obtain a second reviewer’s reading of the complete expression before starting the subscription. Keep credentials out of stored request examples.
    3. \n
  3. Establish the approved stream through the supported client workflow and exercise only the permitted event input. Compare the received XML topic and relevant fields with the reviewed declaration and filters. If the notification is missing, retain the request and response evidence and investigate support, syntax and the input observation separately instead of broadening every filter at once.
    4. \n
\n

Verification and evidence

\n

Retain the declaration, translated topic filter, optional content filter and sanitized stream result with the observed input time. Have another reviewer match the received event to its intended source and value. Keep a working video picture separate from confirmation of the event stream.

\n

For a proposed desk exercise, deliberately leave declaration-style prefixes in a subscription expression and ask the reviewer to correct the mapping before any live request. Also review a content expression that selects the wrong field. These are labeled test fixtures, not observed faults. No RTSP subscription or notification-delivery test has been performed 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: Keep the declared event identity and its RTSP subscription expression together. Resolve the namespace translation before treating a missing notification as proof that the physical event never occurred.\nSource fact: documented behavior\nAxis’s Event data streaming says event declarations use tns1 and tnsaxis, while event-topic filters use onvif and axis respectively.\nThe documented stream carries XML event notifications over RTSP/RTP, and the workflow begins by querying supported event declarations.\nThe source distinguishes the eventtopic topic filter from the eventcontent filter for message source, key and data elements.\nWhat the source does not establish\nDo not infer an identical subscription syntax for WebSocket or another transport. Confirm the actual device’s supported events and stream prerequisites. A translated expression is a configuration input, not proof of notification delivery, event continuity or a complete recording workflow.\nApplicability questions\n\nWhich actual event declaration and topic should the consumer receive?\nWhich declaration prefixes need translation for the RTSP request?\nWhat message fields should a separate content filter select?\nWhich harmless observed input can verify the intended notification?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends storing the device declaration, translated topic expression and optional content expression as separate reviewed fields.\n\nRetrieve the supported event declaration from an authorized pilot device and preserve the relevant topic and field names. Copy identifiers from that response rather than deriving them from a friendly event label. Write the RTSP topic expression beside the declaration and explicitly check each namespace prefix against the documented translation.\nReview any content filter independently from topic selection. Identify whether each named item belongs to the message source, key or data. Use a proposed harmless input with a known expected field value, and obtain a second reviewer’s reading of the complete expression before starting the subscription. Keep credentials out of stored request examples.\nEstablish the approved stream through the supported client workflow and exercise only the permitted event input. Compare the received XML topic and relevant fields with the reviewed declaration and filters. If the notification is missing, retain the request and response evidence and investigate support, syntax and the input observation separately instead of broadening every filter at once.\n\nVerification and evidence\nRetain the declaration, translated topic filter, optional content filter and sanitized stream result with the observed input time. Have another reviewer match the received event to its intended source and value. Keep a working video picture separate from confirmation of the event stream.\nFor a proposed desk exercise, deliberately leave declaration-style prefixes in a subscription expression and ask the reviewer to correct the mapping before any live request. Also review a content expression that selects the wrong field. These are labeled test fixtures, not observed faults. No RTSP subscription or notification-delivery test has been performed for this article.\nOfficial references\n\nEvent data streaming — 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: Keep the declared event identity and its RTSP subscription expression together. Resolve the namespace translation before treating a missing notification as proof that the physical event never occurred.\n\n## Source fact: documented behavior\n\nAxis’s [Event data streaming](https://developer.axis.com/vapix/network-video/event-data-streaming/) says event declarations use tns1 and tnsaxis, while event-topic filters use onvif and axis respectively.\n\nThe documented stream carries XML event notifications over RTSP/RTP, and the workflow begins by querying supported event declarations.\n\nThe source distinguishes the eventtopic topic filter from the eventcontent filter for message source, key and data elements.\n\n## What the source does not establish\n\nDo not infer an identical subscription syntax for WebSocket or another transport. Confirm the actual device’s supported events and stream prerequisites. A translated expression is a configuration input, not proof of notification delivery, event continuity or a complete recording workflow.\n\n## Applicability questions\n\n- Which actual event declaration and topic should the consumer receive?\n\n- Which declaration prefixes need translation for the RTSP request?\n\n- What message fields should a separate content filter select?\n\n- Which harmless observed input can verify the intended notification?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends storing the device declaration, translated topic expression and optional content expression as separate reviewed fields.\n\n- Retrieve the supported event declaration from an authorized pilot device and preserve the relevant topic and field names. Copy identifiers from that response rather than deriving them from a friendly event label. Write the RTSP topic expression beside the declaration and explicitly check each namespace prefix against the documented translation.\n\n- Review any content filter independently from topic selection. Identify whether each named item belongs to the message source, key or data. Use a proposed harmless input with a known expected field value, and obtain a second reviewer’s reading of the complete expression before starting the subscription. Keep credentials out of stored request examples.\n\n- Establish the approved stream through the supported client workflow and exercise only the permitted event input. Compare the received XML topic and relevant fields with the reviewed declaration and filters. If the notification is missing, retain the request and response evidence and investigate support, syntax and the input observation separately instead of broadening every filter at once.\n\n## Verification and evidence\n\nRetain the declaration, translated topic filter, optional content filter and sanitized stream result with the observed input time. Have another reviewer match the received event to its intended source and value. Keep a working video picture separate from confirmation of the event stream.\n\nFor a proposed desk exercise, deliberately leave declaration-style prefixes in a subscription expression and ask the reviewer to correct the mapping before any live request. Also review a content expression that selects the wrong field. These are labeled test fixtures, not observed faults. No RTSP subscription or notification-delivery test has been performed for this article.\n\n## Official references\n\n- [Event data streaming](https://developer.axis.com/vapix/network-video/event-data-streaming/) — 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/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "url": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/#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": "Translate Axis event namespaces before building an RTSP filter", "item": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/#article", "identifier": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "url": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/", "headline": "Translate Axis event namespaces before building an RTSP filter", "description": "Translate Axis event-declaration prefixes into the documented RTSP event-topic filter prefixes.", "abstract": "Translate Axis event-declaration prefixes into the documented RTSP event-topic filter prefixes. Preserve the selected topic and message-content filter separately when checking event receipt.", "articleBody": "Bottom line: Keep the declared event identity and its RTSP subscription expression together. Resolve the namespace translation before treating a missing notification as proof that the physical event never occurred.\nSource fact: documented behavior\nAxis’s Event data streaming says event declarations use tns1 and tnsaxis, while event-topic filters use onvif and axis respectively.\nThe documented stream carries XML event notifications over RTSP/RTP, and the workflow begins by querying supported event declarations.\nThe source distinguishes the eventtopic topic filter from the eventcontent filter for message source, key and data elements.\nWhat the source does not establish\nDo not infer an identical subscription syntax for WebSocket or another transport. Confirm the actual device’s supported events and stream prerequisites. A translated expression is a configuration input, not proof of notification delivery, event continuity or a complete recording workflow.\nApplicability questions\n\nWhich actual event declaration and topic should the consumer receive?\nWhich declaration prefixes need translation for the RTSP request?\nWhat message fields should a separate content filter select?\nWhich harmless observed input can verify the intended notification?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends storing the device declaration, translated topic expression and optional content expression as separate reviewed fields.\n\nRetrieve the supported event declaration from an authorized pilot device and preserve the relevant topic and field names. Copy identifiers from that response rather than deriving them from a friendly event label. Write the RTSP topic expression beside the declaration and explicitly check each namespace prefix against the documented translation.\nReview any content filter independently from topic selection. Identify whether each named item belongs to the message source, key or data. Use a proposed harmless input with a known expected field value, and obtain a second reviewer’s reading of the complete expression before starting the subscription. Keep credentials out of stored request examples.\nEstablish the approved stream through the supported client workflow and exercise only the permitted event input. Compare the received XML topic and relevant fields with the reviewed declaration and filters. If the notification is missing, retain the request and response evidence and investigate support, syntax and the input observation separately instead of broadening every filter at once.\n\nVerification and evidence\nRetain the declaration, translated topic filter, optional content filter and sanitized stream result with the observed input time. Have another reviewer match the received event to its intended source and value. Keep a working video picture separate from confirmation of the event stream.\nFor a proposed desk exercise, deliberately leave declaration-style prefixes in a subscription expression and ask the reviewer to correct the mapping before any live request. Also review a content expression that selects the wrong field. These are labeled test fixtures, not observed faults. No RTSP subscription or notification-delivery test has been performed for this article.\nOfficial references\n\nEvent data streaming — 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:26+00:00", "dateModified": "2026-10-29T20:33:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/translate-axis-event-namespaces-before-building-an-rtsp-filter/" }, "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/translate-axis-event-namespaces-before-building-an-rtsp-filter/#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": "Translate Axis event namespaces before building an RTSP filter" }, "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": 500, "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 — Event data streaming", "url": "https://developer.axis.com/vapix/network-video/event-data-streaming/" } } ] } }