Warning: getdate() [function.getdate]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/includes/asfunc.php on line 92

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/includes/asfunc.php on line 92

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/themes/Multimedija/theme.php on line 135

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/includes/counter.php on line 56

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 69

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 70

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 71

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /web/d2/users/globtel/ipac/modules/MS_Analysis/mstrack.php on line 72
- TISKANJE



   monitoring center  
 
 
 
      Interface  
Higher reliability in transmitting alarms due to the triple (quadruple) connection: IP connection, telephone line and GSM (GPRS) network. In case of one of these connections being down, the next is chosen according to the prioritized order.
Immediate alarm transfer to the monitoring center: transfer over a broadband connection takes less than a second.
Control Panel Compatibility: the IP_AC interface can be installed in any alarm device supporting the CONTACT_ID protocol (most alarm devices).
Works over any type of IP networks: Any local area network (LAN) can support the needs of a few modules. A switched 100Mbps network is desirable and WAN connection with 256 kbps or above of continuous bandwidth is desirable. Module can be used across corporate WANs, VPNs, wireless networks, and broadband connections including ADSL, Cable, SDSL, Nx64, T1, and E1.
Various input signal connectivity: Different types of signals from any kind of devices can be connected to the IP_AC’s I/O module and transferred to the monitoring center.
Outputs triggering possibility: Outputs on the IP_AC’s I/O module can be triggered by specific events at the secured objects side or by the commands, send over the Internet.
Interface doesn’t need static IP address: A DHCP address can be used.
Allows the UDP and TCP protocol: Module allows to be connected over UDP or TCP/IP protocol. With TCP there is no need to forward port at the costumer promises, but the receiver can connect to limited number of TCP connections.
     
Cost-effectiveness. Sending alarms over an inexpensive network designed for Internet access saves the cost of telephone line transfer.
  
     
High level of message encryption transferred over the Internet (256 bit, AES encryption).
  
Easy installation and programming via TelipServiser software.
      Receiver  
Constant, 24/7 control over the lines: Signals from the IP_REC receiver are periodically sent from the monitoring center side to the IP_AC interface at the secured building side in order to check the proper operation of the line. In case of no return signal, the IP_REC sends an alarm to the monitoring center. This function prevents sabotage and line faults.
     
Monitoring of the serial connection between the IP_REC and the monitoring centre operating software.
  
     
Mediate the events into monitoring centre software via serial connection using Contact ID protocol or simulate many other protocols like Surgard, Ademco protocols…
  
     
User’s personal data managing possibility: Users can access their own databases over the Internet as well as receiving events over e-mail.
  
     
Users capacity: 3.000+ users, depends on TCP/UDP protocol usage.
  
     
Internal independent database: Have its own internal HDD for events storage.
  
     
Easy configuration and administration through any Web accessible ControlPanel software.
  
     
 
 
 

© 2007 Globtel d.o.o.. Vse pravice pridržane.