The cameras aren't working, why?
Please, please ensure you have the correct user name and password. Telephone the nursery to confirm this before proceeding any further. Note that the user name and password are both case sensitive. Be careful not to mix up the '-' and the '_' symbols.
The cameras aren't working, and I'm not being asked for a user name and password. Why?
It is possible that the camera server needs rebooting. This is a very simple procedure. Telephone or e-mail the nursery and request that they "reset the camera server". If you are not being asked for the user name or password this is the most likely problem. For the more technical parents out there you can ping the server to confirm if it is active. The Cybertots on the Crescent server is ctcres.cybertots.co.uk, the Cybertots on the Green server is ctgreen.cybertots.co.uk, and the Cybertots at Limetrees server is ctlime.cybertots.co.uk.
I've requested the server is reset, but it's still not working. Why??!?
The camera server takes roughly 2 minutes to begin transmitting images again once reset. Please be patient and try again shortly.
All I get for the cameras is a blue screen.
This normally suggests that the cameras have lost power, or been disconnected from the cameras server. Please email support if this occurs.
None of the above solutions are working. What can I do?
If you have tried all of the above, then please email support and I will try and work through the problem with you personally.
The camera images are too small or low quality can I change them?
Aside from changing the resolution of your monitor there is nothing that can be done about the size of the images as it is determined by the server and subsequently must be the same for each parent. Increasing the image size or quality inevitably slows down the refresh rate. We have tried to settle on the optimum size and quality without sacrificing too much of the refresh rate. However, if you are really unhappy with the current image size then please email support and if popular consensus demands it we can change the image size.
The camera images are refreshing too slowly, is there any way I can speed them up?
The speed of the video stream is determined by a number of factors. If there are a high number of parents logged on at any one time the images may begin to slow down. If you are using the ActiveX component or Firefox you should expect something between 2 frames per second to 0.3 frames per second. If you are not using the ActiveX component you should expect something between 1 frame per second to 0.3 frames per second.
Why are there now three different ways of viewing the cameras?
Because the amount of different Internet browsers, connection speeds, and working environments pose a variety of problems to any single given solution. As a consequence we are now offering three different ways of viewing the life camera images to try and ensure all parents can get the best experience possible.
UPDATE: As of the site redesign you should now automatically be sent to the correct camera system. If you are not you can change the system from the method being used from the bottom of the camera page.
View camera feeds from Internet Explorer utilising the ActiveX component
This provides an optimal refresh rate but requires an ActiveX component to be installed. ActiveX does not work in many other Internet browsers such as Firefox. The ActiveX component is a small software program that is installed from the webpage and is used to stream the camera images. This can cause problems if you are on a computer that will not install the ActiveX component, for example on a University campus or an Internet cafe.
View camera feeds from Firefox with no ActiveX component.
This provides an optimal refresh rate without the need to install an ActiveX component. Firefox doesn't need the ActiveX component in order to stream the camera images, and as such this option eliminates the need to install it.
View camera feeds from Internet Explorer or Firefox utilising JavaScript.
Rather than streaming the video feed directly this method takes a still image from the cameras, loads it, then requests receives and loads the next still image. As the browser must constantly negotiate with the server for these still images this provides a slightly slower refresh rate (it is limited to about 1 frame per second). On some versions of Internet Explorer this provides a very flickery display as the image is not being cached correctly. There is no known workaround for this problem yet, but if we recommend that you get Firefox.