Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Maybe the WS-DISCOVERY gives you extra information. I would try not to use any port after the IP of the camera. </p> <p>When the test sends an UDP to the multicast address 239.255.255.250, port 3702 (WS-Discovery), this is the camera's answer: </p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" 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"&gt; &lt;SOAP-ENV:Header&gt; &lt;wsa:MessageID&gt;uuid:cb3dea50-aa60-11e1-88b9-00408cb972aa&lt;/wsa:MessageID&gt; &lt;wsa:RelatesTo&gt;uuid:5bca11ff-61b8-4d07-8a26-90274ad51db8&lt;/wsa:RelatesTo&gt; &lt;wsa:To SOAP-ENV:mustUnderstand="true"&gt;http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous&lt;/wsa:To&gt; &lt;wsa:Action SOAP-ENV:mustUnderstand="true"&gt;http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches&lt;/wsa:Action&gt; &lt;d:AppSequence SOAP-ENV:mustUnderstand="true" MessageNumber="1" InstanceId="1338367479"&gt;&lt;/d:AppSequence&gt; &lt;/SOAP-ENV:Header&gt; &lt;SOAP-ENV:Body&gt; &lt;d:ProbeMatches&gt; &lt;d:ProbeMatch&gt; &lt;wsa:EndpointReference&gt; &lt;wsa:Address&gt;urn:uuid:65a142fc-a41e-11e1-9cc8-00408cb972aa&lt;/wsa:Address&gt; &lt;/wsa:EndpointReference&gt; &lt;d:Types&gt;dn:NetworkVideoTransmitter&lt;/d:Types&gt; &lt;d:Scopes&gt; onvif://www.onvif.org/type/video_encoder onvif://www.onvif.org/type/ptz onvif://www.onvif.org/hardware/P5534-E onvif://www.onvif.org/name/AXIS%20P5534-E onvif://www.onvif.org/location/ &lt;/d:Scopes&gt; &lt;d:XAddrs&gt; h##p://zeroconfIP/onvif/device_service h##p://unicastIP/onvif/device_service &lt;/d:XAddrs&gt; &lt;d:MetadataVersion&gt;1&lt;/d:MetadataVersion&gt; &lt;/d:ProbeMatch&gt; &lt;/d:ProbeMatches&gt; &lt;/SOAP-ENV:Body&gt; &lt;/SOAP-ENV:Envelope&gt; </code></pre> <p>Try to discover the response and see if any XAddrs is not the default you expect.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to get device information using Onvif library c#?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USchirrin dul ari
    1. USchirrin dul ari
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO:: yes, i have tried it on ODM but it also returns me the same error i have mentioned here.
      singulars
      1. PO
      1. USAzeem Akram
    2. COSorry, the request must be sent to device_service.
      singulars
      1. PO
      1. USchirrin dul ari
    3. COIn particular, the XAddr for device_service is for 99% of all NVT going to be .../onvif/device_service but it _may_ by anything. It behooves to check the ProbeMatch (or Hello) and use that, rather then calculate it in code. Based on your comment above, I presume your NVT always does choose .../onvif/device_service. Try pasting that URL into your browser. You should see a sane response. Also try SoapUI to verify your NVT is behaving properly.
      singulars
      1. PO
      1. USJesse Chisholm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload