WS-Discovery and express discovery from XPRotect

MIP
, , , ,
1

Hi,

We are a video encoder manufacturer and we have some issues with the express discovery from XProtect.

Our implementation of WS-Discovery is working with all VMS and ODM except XProtect.

On a probe message we send the following response:

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

<soapenv:Envelope xmlns:soapenv=“http://www.w3.org/2003/05/soap-envelope”

xmlns:a=“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”

xmlns:tt=“http://www.onvif.org/ver10/schema”>

soapenv:Header<a:Action soapenv:mustUnderstand=‘true’>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</a:Action>

<a:RelatesTo>uuid:0673c10c-36c7-480e-9283-00005efe0fdf</a:RelatesTo>

</soapenv:Header>

soapenv:Body

urn:uuid:c1c03eb7-885c-4c4c-a27c-7881d335c6c4onvif://www.onvif.org/name/ATOMAS-MINI onvif://www.onvif.org/hardware/ATOMAS-MINI onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/type/audio_encoder onvif://www.onvif.org/Profile/Streaming onvif://www.onvif.org/Profile/T http://10.192.2.3:80/onvif/device_service1

</soapenv:Body>

</soapenv:Envelope>

10.192.2.3 is the ip address of the device.

Could you see why XProtect doesn’t go further?

Thanks,

Sylvain

2

Hi Sylvain,

Which Device Pack version are you using? I suggest trying with the latest released as we had fixes in the ONVIF discovery recently.

Also at which step does it fail? Does the device show in the list at all?

3

Hi Maxim,

By upgrading to the latest version, it fixed the issue.

Thanks,

Sylvain