Snapshot URL to Yeskamo IP camera or NVR
- Thread starter beos
- Start date
Yes it has a web GUI on port 80 on local LAN (IP cams are on a separate LAN controlled by the NVR). The web GUI looks similar to the one I have for Hikvision but it doesn't seems fully functional, at least not out of the box. It is not documented in their manuals either, refer to a mobile app and to EseeCloud for desktop app. Otherwise it has port 10000 open according to nmap, but nothing else.
Have you tried any URL's yet?
Such as:
Such as:
Code:
http://user:password@NVR-IP_address/ISAPI/Streaming/channels/101/picture
@TonyR
Yes I have tried a number of these. Essentially they all give this response
---
~$ curl -v " :<pass>@192.168.1.151/ISAPI/Streaming/channels/101/picture"
< HTTP/1.1 404 Not Found
< Server: nginx
< Content-Length: 0
< Connection: close
<
* Closing connection 0
---
Now I don't have a camera on channel 1, but only on 2, 3 and 4. If channel 2 is "102" in your URL it gave the same response.
Yes I have tried a number of these. Essentially they all give this response
---
~$ curl -v " :<pass>@192.168.1.151/ISAPI/Streaming/channels/101/picture"
- Trying 192.168.1.151:80...
- TCP_NODELAY set
- Connected to 192.168.1.151 (192.168.1.151) port 80 (#0)
- Server auth using Basic with user 'admin'
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Server: nginx
< Content-Length: 0
< Connection: close
<
* Closing connection 0
---
Now I don't have a camera on channel 1, but only on 2, 3 and 4. If channel 2 is "102" in your URL it gave the same response.
Sorry for the formatting above, not used to this editor...
Code:
~$ curl -v "http://admin:<pass>@192.168.1.151/ISAPI/Streaming/channels/101/picture"
* Trying 192.168.1.151:80...
* TCP_NODELAY set
* Connected to 192.168.1.151 (192.168.1.151) port 80 (#0)
* Server auth using Basic with user 'admin'
> GET /ISAPI/Streaming/channels/101/picture HTTP/1.1
> Host: 192.168.1.151
> Authorization: Basic YWRtaW46VGhlYW5zdzNy
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Server: nginx
< Content-Length: 0
< Connection: close
<
* Closing connection 0Try this url:
Code:
http://192.168.1.151/cgi-bin/view.cgi?chn=0&u=admin&p=Theansw3r
OR
http://192.168.1.151/cgi-bin/snapshot.cgi?chn=0&u=admin&p=Theansw3rNot working...
This is the login page. looks pretty generic... URL is ""
Attachments
It's a Juan NVR ( Guangzhou Juan Intelligent Tech Joint Stock Co.,Ltd )
Old models was using cgi-bin/snapshot.cgi?chn=0&u=user&p=pass for snapshot.
Screenshots from an old Juan DVR:
I downloaded firmware file for a new NVR model and tried to find the snapshot URL, but couldn't find it.
You can try this URL, but probably it wont work:
Code:
http://192.168.1.151/NetSDK/Video/encode/channel/101/snapshot
Code:
http://192.168.1.151/cgi-bin/gw.cgi
http://192.168.1.151/cgi-bin/gw2.cgiThis one was the first that actually gave something else than a 404 response!
Code:
curl -v "http://admin:<pass>@192.168.1.151/NetSDK/Video/encode/channel/101/snapshot"
* Trying 192.168.1.151:80...
* TCP_NODELAY set
* Connected to 192.168.1.151 (192.168.1.151) port 80 (#0)
* Server auth using Basic with user 'admin'
> GET /NetSDK/Video/encode/channel/101/snapshot HTTP/1.1
> Host: 192.168.1.151
> Authorization: Basic YWRtaW46VGhlYW5zdzNy
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Server: nginx
< Content-Length: 111
< Connection: close
<
{
"DEV" : "XVR",
"VER" : "1.0",
"API" : "",
"StatusCode" : "error",
"RetDetail" : "Save failure"
}
* Closing connection 0These gave 404 response.
It should be 201 301 or 401.This one was the first that actually gave something else than a 404 response!
As I mentioned above my channel 1 has no IP cam only channels 2-4. Should it be "102" in the url above for channel 2? However got the same response with "102".Code:curl -v "http://admin:<pass>@192.168.1.151/NetSDK/Video/encode/channel/101/snapshot" * Trying 192.168.1.151:80... * TCP_NODELAY set * Connected to 192.168.1.151 (192.168.1.151) port 80 (#0) * Server auth using Basic with user 'admin' > GET /NetSDK/Video/encode/channel/101/snapshot HTTP/1.1 > Host: 192.168.1.151 > Authorization: Basic YWRtaW46VGhlYW5zdzNy > User-Agent: curl/7.68.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 200 OK < Content-Type: application/json < Server: nginx < Content-Length: 111 < Connection: close < { "DEV" : "XVR", "VER" : "1.0", "API" : "", "StatusCode" : "error", "RetDetail" : "Save failure" } * Closing connection 0
These gave 404 response.
