sixwheeledbeast

Suppose that one way to get people off the phone... That is Reset Digi, I assume. If you have no chime zones then it maybe be something odd. Take a backup with Wintex and default the panel, try from there to rule out hardware issue.

Zone programmed as Chime. Press the Chime button it will go away.

Exactly, completely agree.

Consider yourself lucky, it's normally rock hard toffee pennies.

Protecting a 350k house with a 200 quid alarm, baffles me...

Would only detect you on the way in. As I say, Follow zones are for that sort of thing.

Er, Perimeter then. Or Perim-Follow depending on the PIR's location.

I don't see why not.

You thinking of a move...?

Depending on the PowerMax model there are walk-through zones to do that. Inter-Follow is one of them. I don't think I would want the landing device to point down the stairs TBH, I would have a sensor on the landing and one in the hall.

You should use a static IP. It must be set in the control panel. UDL/Digi Options.

The OP said dual path...

Will be worth knowing, but not identifiable by an aerial. While they both do a similar job Redcare GSM is arguably a better product than Dualcom GPRS.

I also agree with many comments above. Please also consider the cost of switching companies. It will be unlikely you will be able to transfer the monitoring so you will have the cost of new kit and connection charges. Also other companies maybe cheaper but make sure you consider what's included. Parts, servicing, call outs, out of hours are they extra or included. Will the new signalling be to the same Grade as the out going. I think for Redcare GSM it sounds about right depending on location?

It all depends on how competent you are at that stuff really. You will find it's only available on top end enterprise routers, if your using a router to do it. The whole point of a VLAN (Virtual LAN) is to isolate the LAN into sections, so yes that wouldn't work on the LAN side.

Yes, S01 is Sounder number one. Not generic really.

S01 is a fault with the external sounder.

If there all fitted to the same standard and specification, surely this would only need doing once for each model/firmware? Again I would expect the manufacturer to have had this done externally. I also agree with PJ about 1 and 2 being hard to implement on some networks. Point 3 should be done as standard for anyone with knowledge of setting up firewalls, however, someone with a network background would understand this in more depth than an alarm monkey.

What alternative solutions would you recommend?

That's fair comment. From and installer POV we expect the DVR to be secure. I can understand why many are not, look at shellshock for example, These CVE's will never be updated in older DVR units. I wouldn't be surprised if most DVR's sold today are running outdated linux kernels or suffer from known exploits. The issue is as you say, the run of the mill engineer is bearly capable of punching some holes in the firewall and installing the client. This is where the manufacturers should step up IMO. After all you say about layers, you can put the DVR on a VLAN to protect the site but what about the private images stored on the DVR? Ultimately the installer would be responsible if anything did happen.

This also interests me from an installer POV too. I wanted to split this out to keep the other thread on topic. Do you find a large number of DVR's provide an attack route on to the network? Basic or Enterprise kit? Any models you can use as an example? Do you feel it's up to the manufactures to design them better or the installers to have them VLAN'd? etc...

If it's not been serviced then it's not on contract. Therefore, you will be at the bottom of there todo list for today.

Texecom Registered installer.

I am not trying to put you off but when flashing it's critical that it goes well or you will brick your panel. If you save a few quid but you brick a panel it's not a good cost saving exercise. Also the flasher has been the same for years, even the older less powerful panels had the same flasher separate. I can only speculate the reasons for this, maybe security or cost are some of the factors.

I second that. The programming port is for flashing only.