Possible to send emails by camera connected to NVR?

O

Optik

n3wb
Apr 1, 2016
16
3
London
I have NVR 7608NI/I2 with minidome 2CD2532F-IS. NVR emailing very low resolution pictures, i want my camera to email the alerts, as it can be setup to a lot higher resolution. Any help appreciated.
Thanks guys.
P.S. all the settings on the camera's email settings are the same as on the NVR. test fails and no emails from my cam...
 
Last edited by a moderator:
Thanks for directing to this thread. Still not that detailed, got the principle, but i am not strong on Static route settings. Can not understand what values of net-mask and metric should be.
 
Got it. Mask is standard 255.255.255.0 but had to static route all range of the 192.168.254.0 network segment, including NVR and camera in question. Everything now works. Thanks again for pointing in the right direction!
Result: NVR emailed pictures are 704x480, camera pictures 2048x1536. Huge improvement in quality. Canceling NVR emailing as a result.
 
Last edited by a moderator:
Got it. Mask is standard 255.255.255.0 but had to static route all range of the 192.168.254.0 network segment, including NVR and camera in question. Everything now works. Thanks again for pointing in the right direction!
Click to expand...
Excellent!
Well done for solving the puzzle, and getting it working.
 
  • Like
Reactions: Optik
Travieso said:
How did u get this to work I'm curious now
Click to expand...
I did explain this in my last comment to this tread, but can add more details.
In Static Rout List settings (hopefully in your router, i have ASUS N66U). if your router has no such settings, time to upgrade.
Anyway, in my ASUS setting go like this:

[TABLE="class: FormTable_table, width: 100%, align: center"]
[TR]
[TD="colspan: 6, align: left"]Static Route List (Max Limit : 32)[/TD]
[/TR]
[TR]
[TH="align: center"]Network/Host IP
[/TH]
[TH="align: center"]Netmask
[/TH]
[TH="align: center"]Gateway
[/TH]
[TH="align: center"]Metric
[/TH]
[TH="align: center"]Interface
[/TH]
[/TR]
[/TABLE]

[TABLE="class: list_table, width: 100%, align: center"]
[TR]
[TD="width: 34%"]192.168.254.0 NVR Internal network IP[/TD]
[TD="width: 18%"]255.255.255.0[/TD]
[TD="width: 18%"]192.168.1.*** NVR IP (check with SADP)[/TD]
[TD="width: 8%"][/TD]
[TD="width: 10%"]LAN[/TD]
[TD="width: 12%"][/TD]
[/TR]
[TR]
[TD="width: 34%"]192.168.254.1 NVR IP[/TD]
[TD="width: 18%"]255.255.255.0[/TD]
[TD="width: 18%"]192.168.1.***[/TD]
[TD="width: 8%"][/TD]
[TD="width: 10%"]LAN[/TD]
[TD="width: 12%"][/TD]
[/TR]
[TR]
[TD="width: 34%"]192.168.254.2 Cameras[/TD]
[TD="width: 18%"]255.255.255.0[/TD]
[TD="width: 18%"]192.168.1.***[/TD]
[TD="width: 8%"][/TD]
[TD="width: 10%"]LAN[/TD]
[/TR]
[/TABLE]

On every IPC in Network-TCP/IP change IP4 Default Gateway to INTERNAL NVR IP (192.168.254.1 )

Hope it is easy to follow...
 
Last edited by a moderator:
  • Like
Reactions: badmannen and klasipca
Awesome! Thank you for sharing!
 
Optik said:
I did explain this in my last comment to this tread, but can add more details.
In Static Rout List settings (hopefully in your router, i have ASUS N66U). if your router has no such settings, time to upgrade.
Anyway, in my ASUS setting go like this:

[TABLE="class: FormTable_table, width: 100%, align: center"]
[TR]
[TD="colspan: 6, align: left"]Static Route List (Max Limit : 32)[/TD]
[/TR]
[TR]
[TH="align: center"]Network/Host IP[/TH]
[TH="align: center"]Netmask[/TH]
[TH="align: center"]Gateway[/TH]
[TH="align: center"]Metric[/TH]
[TH="align: center"]Interface[/TH]
[/TR]
[/TABLE]

[TABLE="class: list_table, width: 100%, align: center"]
[TR]
[TD="width: 34%"]192.168.254.0 NVR Internal network IP[/TD]
[TD="width: 18%"]255.255.255.0[/TD]
[TD="width: 18%"]192.168.1.*** NVR IP (check with SADP)[/TD]
[TD="width: 8%"][/TD]
[TD="width: 10%"]LAN[/TD]
[TD="width: 12%"][/TD]
[/TR]
[TR]
[TD="width: 34%"]192.168.254.1 NVR IP[/TD]
[TD="width: 18%"]255.255.255.0[/TD]
[TD="width: 18%"]192.168.1.***[/TD]
[TD="width: 8%"][/TD]
[TD="width: 10%"]LAN[/TD]
[TD="width: 12%"][/TD]
[/TR]
[TR]
[TD="width: 34%"]192.168.254.2 Cameras[/TD]
[TD="width: 18%"]255.255.255.0[/TD]
[TD="width: 18%"]192.168.1.***[/TD]
[TD="width: 8%"][/TD]
[TD="width: 10%"]LAN[/TD]
[/TR]
[/TABLE]

On every IPC in Network-TCP/IP change IP4 Default Gateway to INTERNAL NVR IP (192.168.254.1 )

Hope it is easy to follow...
Click to expand...

I think that Netmask really should be 255.255.255.255, In my router I cannot set Host IP with the .0 mask in the end.
 
maybe some one will be happy to read this if you got a router like this:
| | o |
|--- ,---. ,---. |---. ,---. . ,---. ,---. | ,---. ,---.
| |---' | | | | | | | | | | | | |
`---' `---' `---' ` ' ` ' ` `---' `---' `---' `---' `

MediaAccess TG589vn v3



....


if you do , you might need to edit its config.ini file. and then use telnet to go in and modify the static routes since it doesn´t show up in the normal webinterface.

heres a link that I used to solve it.

to enable telnet use this:https://mackonsti.wordpress.com/2012/01/11/enable-telnet-thomson-tg585-routers/

and to set up the static route , use this one:
https://getflix.zendesk.com/hc/en-gb/articles/201833214-Technicolor-TG587n-v3
 
Optik said:
not sure. 255.255.255.0 is a standard mask... does it work with 255.255.255.255??

Sent from my SM-G935F using Tapatalk
Click to expand...
Nope, didn't get it to work unfortunately.
 
The /32 mask (255.255.255.255) means that all octects must match, but why not declaring the whole subnet, 192.168.254.0 255.255.255.0 via nvr.wan.ip.address ? (even though a /28, 255.255.255.240, is more than enough, for a 8 port NVR)
Cheers,
jonatha
 
Greetings all,

Quick introduction: Had my first IP cam / NVR system installed at my place (NVR-8108-P8, V3.4.1 firmware, and 8x DS-2CD2335-I cams, v5.3.6 firmware on those). Have figured most of it out, but for the life of me I cannot get my emails to send an attached image from the NVR. (I have it enabled in the email settings of the NVR, as well as the Save VCA Image ticked for each Intrusion Detection setting on each cam). Further to that, I cannot use any of the VCA analysis on my NVR as there seem to be no images saved in the first place. The image storage counter on the disk management/system information never goes above 1024MB either, so I don't think any images are being saved at all.)

So, I thought I would try the trick of letting the IP cam send an email itself with an attached image, but I've run into the problem with my modem/router not letting me set a subnet mask of 255.255.255.0 to match that of the NVR.

The main question: Can I manually set the subnet mask on the NVR to 255.255.255.255 instead, without cocking anything up? (I can set that in my Static Route list on my moden/router.)

The secondary question: Anyone have an explanation as to why image attachments are not working for my particular NVR and why image snapshots aren't being saved in the first place? I tried logging directly into the camera and enabling the JPEG Event-Based snapshots there, enabled the schedule for those events, but it was there that I noticed there was nowhere to actually save the images. Camera has no card slot, and the NAT hard-drive tab detected nothing, not even the NVR hard-drive... shouldn't the NVR hard-drive be detected if the camera is connected to it?

Hope someone can help me with this... I really do need those emails to have an image attachment, otherwise I'm having to fumble into the iVMS-4500 app and that invariably takes too long to get an image, so I'd be missing what's happening when it happens.

Cheers in advance.
 
Last edited by a moderator:
For your first question, using a /32 ( 255.255.255.255) subnet mask, simply means that all octets (which represent the ip address) must match, so if you create a static route for, eg., 192.168.254.3 255.255.255.255, this route is valid only for the host 192.168.254.3, and not for 192.168.254.2 or 192.168.254.4.....
If you have, let's say, 8 hosts that must be reacheable, if you use a /28 sm (255.255.255.240), hosts from 192.168.254.1 to 192.168.254.15 will be reacheable via that static route, if you use a /24 sm (255.255.255.0), the whole class C 192.168.254.0 network (hosts from 192.168.254.1 to 192.168.254.254) will be reacheable thanks to that route
Cheers,
jonatha
 
Okay, I'm not getting very far with this, so I hope someone won't mind stepping me through this.

On my NVR network settings:

the IPv4 is 192.168.1.106
the subnet mask is 255.255.255.0
IPv4 default gateway is 192.168.1.1
DNS server is 192.168.1.1

Under advanced settings, I have Enable Virtual Host checked (which lets me directly access cam settings).

On each of my cams:

IPv4 is 192.168.254.X (where X is 2-9 for each of 8 cams)
IPv4 subnet mask is 255.255.255.0
IPv4 Default Gateway is currently 192.168.1.1
DNS server is 8.8.8.8

First verification: I'm supposed to change the cam IPv4 default gateway to 192.168.254.1, correct? When I do this, I can ping and tracert the cams from command line.

On my TP-Link 300M modem router, under Static Route:
I can set Destination, Subnet Mask, Gateway, and Interface. Currently it is as follows

Destination, Subnet mask, Gateway, Interface
192.168.254.0, 255.255.255.0, 192.168.1.106, br0
192.168.254.1, 255.255.255.255 (cannot set last to 0), 192.168.1.106, br0
192.168.254.2, 255.255.255.255 (cannot set last to 0), 192.168.1.106, bro

Now if I omit those last two entries, having just the first one, I can still ping and tracert the cams on their 192.168.254.x IP. However, when I try to send a test email from the cam, it says "Failed to connect to the test server". The same email SMTP server and port settings work perfectly fine under the NVR email settings, and I'm getting my Intrusion Alerts as expected from the NVR (just with no pictures even when picture enabled.)

Any suggestions?
 
Since your cameras are connected at the PoE switch of the NVR, the cameras can not communicate with the 192.168.1.XXX network which is your lan. Therefore the gateway of the cameras must be set to 192.168.254.1 which is the internal PoE switch of the NVR. For any network communication of the camera, the packets from the cameras are routed at the 192.168.254.1 IP and then the NVR through the Virtual Host feature bridges the two lans (the 192.168.1.XXX and the 192.168.254.XXX) and routes the packets to the next gateway defined in the NVR which is the 192.168.1.1 (i.e. your main LAN router).

Always reboot both camera and NVR when you change ny IP settings.

If you can telnet to the camera then you may verify the low level network and DNS connectivity by pinging from the camera telnet prompt any webserver, say the google DNS 8.8.8.8. If this test fails then you have a basic network misconfiguration. If it succedess and you still can not send emails from the camera, then ensure that your gmail account allows less secure applications to send emails.

Also I assume that the br0 interface at the static route definition in your router is the LAN interface and not your WAN interface.
 
If you set the 0 at the end of the subnet mask, you have to declare a network address like 192.168.254.0 (this in few words, and not always true) , not an host address, like 192.168.254.2 (also this isn't always true, some routers simply don't take in consideration the host portion of the IPv4 address, but now isn't so important)).
I think that the br0 refers to the bridge ath0/switch0 (the wireless and the ethernet interfaces). The first entry, is more than enough for reach the cameras behind the NVR .... just tried on my camera behind the NVR, the emails are ok .....
Try, as @aster1x has suggested above, by setting the correct default-gateway to the camera.
Cheers,
jonatha
 
Last edited by a moderator:
You must log in or register to reply here.
Top Bottom