XProtect auto WSDD questions

General
1

Hello,

We are working on enabling Express device discovery in Milestone XProtect with ITVDesk - Onvif IP Camera.

Our device responds correctly to WSDD Probe/ProbeMatches and manual ONVIF add works without issues.

However, the device does not appear in the discovery list.

We are currently returning XAddrs:
http://:7000/onvif/device_service

Could you please confirm:

  1. Does XProtect require the ONVIF device service to be available on:
    http:///onvif/device_service (port 80)?

  2. Is XAddrs with custom ports ignored during discovery?

  3. Is our ProbeMatches XML structure generally acceptable for XProtect,
    or are there any strict requirements regarding format, namespaces, or fields?

<?xml version="1.0" encoding="UTF-8"?>

<s:Envelope xmlns:s=“http://www.w3.org/2003/05/soap-envelope”
xmlns:wsa=“http://schemas.xmlsoap.org/ws/2004/08/addressing”
xmlns:d=“http://schemas.xmlsoap.org/ws/2005/04/discovery”
xmlns:dn=“http://www.onvif.org/ver10/network/wsdl”
xmlns:tds=“http://www.onvif.org/ver10/device/wsdl”>
<s:Header>
wsa:MessageIDuuid:…</wsa:MessageID>
wsa:RelatesTouuid:…</wsa:RelatesTo>
wsa:To WS-Addressing Anonymous Role </wsa:To>
wsa:Actionhttp://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action>
</s:Header>
<s:Body>
<d:ProbeMatches>
<d:ProbeMatch>
wsa:EndpointReference
wsa:Addressurn:uuid:…</wsa:Address>
</wsa:EndpointReference>
<d:Types>dn:NetworkVideoTransmitter tds:Device</d:Types>
<d:Scopes>onvif://www.onvif.org/Profile/Streaming …</d:Scopes>
<d:XAddrs>http://:7000/onvif/device_service</d:XAddrs>
<d:MetadataVersion>1</d:MetadataVersion>
</d:ProbeMatch>
</d:ProbeMatches>
</s:Body>
</s:Envelope>

Our goal is to ensure the device appears in Express discovery without manual configuration.

2
  1. Does XProtect require the ONVIF device service to be available on:
    http:///onvif/device_service (port 80)?

The XProtect can discover devices on ports different than 80.

  1. Is XAddrs with custom ports ignored during discovery?

No, the ports are not ignored during the discovery phase.

  1. Is our ProbeMatches XML structure generally acceptable for XProtect, or are there any strict requirements regarding format, namespaces, or fields?

The given XML structure generally looks fine and should work as expected.

1 Like