I have. It just doesn't seem to be showing.
Originally Posted by Norphy If there were a thank button on blog entries, I would be pressing it right now. Thank you for this, very useful. You could rate it!!
Glad it helped someone.
If there were a thank button on blog entries, I would be pressing it right now. Thank you for this, very useful.
No. In the end, we stuck with CSE. In the testing phase, building the Start Menus was possible using the CSE System so we use that and it works well.
We had to look at how much it would could overall to re-license the parts we like with different products, and working with CSE got what we wanted working how we wanted so sticking with that.
So far so good.
Are you still using GPP for your start menus?
Cheers Pete looks nice and I've said that it would be good to get that system so we shall see if I continue to fail to fix things in the holidays / have to sit in reception / leave the door wedged open with a sign saying shout loud for a signature etc... or I get a nice product like that which can phone me
I've added a couple of photos to the post. Hope it helps.
Cheers Pete Looks good to me so will be sending it onto our Architects to look at inclusion on our new doors rather than the boring phone on wall that isn't helpful at times when the office is empty AKA holidays etc....
The door entry unit is a Ulydor made by Kalika. It's an intercom unit which sits on the system as an analogue phone. It's programmed to dial a 'Group' when someone presses the intercom button. Any person who answers the phone can then talk to the visitor and if they want to let them in press a code on the phone to unlock the door. The door release was an existing mechanism already in place.
As I said, it's an analogue unit only hence why we had to get the 20-Core Telephone Cable installed at the same time. But it's been useful having that analogue capability in place as well.
Hope it helps
Sounds a great project that you have been doing Pete
Quick one on the Door Entry stuff, is that a specifc module of that new system or is it one that is off the shelf and just patched to an analogue port on the system? I am looking for that for our digital system, Nortel made one but talking to a couple of firms that have used them it sounds a bit gash but none have suggested any alternatives.
So could do with knowing a bit about yours if possible
I did ask the engineer wether or not we could give the Call Server multiple IP addresses (from the two different subnets), but was told no. However, he did inform me that they working on the ability to plug the box into multiple VLANs but wasn't quite ready yet!
Can you not multihome the VOIP system across multiple VLANs, not as good but might be a possibility.
Again, thanks @SYNACK - I'm going to try and work out exactly what you mention; not sure how, would appreciate a nudge in the right direction. Our Core switch is a HP Procurve 5406zl.
You could use a single NAT stage at the interface to the LA network and have all the internal stuff behind it. A decent layer 3 switch (possibly with the advanced firmware option - depending on vendor) could let you run one to one NAT so outside you have the LA subnet lets say 172.16.1.1 to 172.16.2.254 then inside have your network split into chunks that add up to at avalible range from the LA. This way you do not need to use NAT overloading (all on one IP and stacked by messing with port numbers).
This way the LA does not see anything different and can't throw fits but you still get to use propper routing and subnets inside despite the primative conditions imposed by the upstream network.
You do need to use different subnets for each VLAN otherwise it breaks tcp/ip routing to the point that it does not work.
Thanks @SYNACK - The problem is the we're on a particular scope from SWGfL, so can't route from one subnet to this subnet through their gateway, that's why we need to use NAT. I think I got that right anyway!
You want routing rather than NAT unless you have two seporate chunks using the same ip addresses and need to use double NAT and routing. Using seporate ip ranges and routing should be much simpler.
I have a fantastic diagram on how VLAN's work if you would like to see!
Like you I have nothing but utter contempt for Capita. You were lucky we paid £24,000 for the privilidge. I now spend my days trying to find ways to undermine and destroy Capita ES and all who sail in her. We avoid giving them money at all costs. Am I bitter and twisted? Damn right!
Just been in contact with APC, support have been helpful but it would appear that the particular model of UPS only has 2 years warranty and has now expired. But, how nice, they can offer me a 20%-25% discount if I upgrade to another model. Disappointed that an Enterprise level bit of kit is only covered for 2 years.
Not sure on the XenServer shutdown times, I remember when we first set them up and ran the original script while testing and shutdown only took a few minutes.
I've sinced removed the UPS from the equation; can't trust it and have piggy backed the server onto another UPS that has plenty of capacity and have now double checked all my scripts.
I just wrote on the forum about using APC smartups and Hyper-v.
When hyper-v shuts down it takes about 30mins to close all the virtual machines for some reason. I'm still wondering if thats enough time for the hyper-v machine to shut down before the power runs out.