Announcement

Collapse
No announcement yet.

VOIP Phonelines for Fire Alarm dialout UPS?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Where I work we comission a new building every couple of years, and although all new buildings use VoIP for phones, and the BMS is now over IP, when the telecomms guys are laying their fibre they still throw in a fifty pair for lifts, FA etc.

    Comment


      #17
      Originally posted by MisterCMK View Post
      Does the manufacturer of the communicator say that it will work with anything but plain old copper?
      Exactly, no FACP out of the box, without an additional device is compatible with VOIP. Ask any of the tech reps for any brand and they will tell you NO, it won't work

      Will it really work,? Maybe. Is maybe good enough for Fire?

      The 24 Hours of back up power of course is a huge issue, that until recently has been completely overlooked.


      Sell them a new form of communication.

      Try AES intellinet radios if the service is available in your area. No phone lines. Universal compatibility for any FACP! Ul 894 9th ed approved http://www.aes-intellinet.com/docume...788_TC_000.pdf

      Having control over your FACP communication... priceless for me, and it adds to the RMR.

      Comment


        #18
        Originally posted by zbang View Post
        (Put all your comm on a single circuit, much less a single wireless link? Not my facility.)
        This is just my opinion.

        Ultimately the phone line coming into the building is a single circuit (point of possible failure). The cable could be damaged at the street, a pole carrying it could be hit by a truck and come down or the Telco CO/Switching station could be flooded and there would be no phone service for weeks (happened here last year). These are all single points of failure outside the building that could sever communications.

        Wireless transceivers that use multiple wireless paths that are redundant are much safer that POTS lines. Sure the transceiver is a single point of possible failure, just like a POTS cable that can be cut. However all the POTS lines eventually go to a single point outside the building before hitting a central station. A wireless wireless mesh network does not need to rely on such a scheme. The system I use has a min of 4 and max of 8 available routes.

        Maybe you were referring to GSM? That's another topic with its own challenges.
        Last edited by nhfire77; 02-16-10, 08:15 PM.

        Comment


          #19
          Originally posted by nhfire77 View Post
          Ultimately the phone line coming into the building is a single circuit (point of possible failure).
          In telco-speak, each POTS line, trunk, etc is a separate circuit. They may all be in a single cable, but they're considered separate. As for physical damage, yes, it can happen but isn't nearly as common as things like internet router crashes and such failures, and telcos are still known for quick repairs when a car takes out a 200pr cable. Redundant cable paths are available in some places, however you pay dearly for them so people accept the risk.

          Originally posted by nhfire77 View Post
          Wireless transceivers that use multiple wireless paths that are redundant are much safer that POTS lines. Sure the transceiver is a single point of possible failure, just like a POTS cable that can be cut. However all the POTS lines eventually go to a single point outside the building before hitting a central station. A wireless wireless mesh network does not need to rely on such a scheme. The system I use has a min of 4 and max of 8 available routes..
          I was referring to a single-span wireless link as are commonly used for Internet delivery (e.g. WiMAX). A purpose-built multi-path system is much preferable to any single-path system. Given the choice, I'd take the multi-point radio system, then copper POTS lines (or both), and only VoIP on a non-dedicated path if that was all that's available.

          Comment


            #20
            This is from Cablevision's TOS as I was saying above:

            Cablevision does not support the use of Optimum Voice for Business as a connection between (i) medical alert systems, (ii) any high security monitoring systems (UL 681 or similar) or (iii) fire alarm systems (UL 864 or similar). and the central station monitoring Subscriber must maintain an alternate connection.

            I would further add that it won't make any difference if you are using the dialtone off a cable modem or the broadband internet connection. Both are subject to the same reliability issues. So I can't see under what conditions a UL approval for an IP communicator is possible.

            -Hal

            Comment


              #21
              Just to flog a dead equine- VoIP is Voice over IP, not any audio signal over IP. The only reason that fax's work is because the terminal adapters specifically recognise fax tones.

              Comment


                #22
                Originally posted by hbiss View Post
                This is from Cablevision's TOS as I was saying above:

                Cablevision does not support the use of Optimum Voice for Business as a connection between (i) medical alert systems, (ii) any high security monitoring systems (UL 681 or similar) or (iii) fire alarm systems (UL 864 or similar). and the central station monitoring Subscriber must maintain an alternate connection.

                I would further add that it won't make any difference if you are using the dialtone off a cable modem or the broadband internet connection. Both are subject to the same reliability issues. So I can't see under what conditions a UL approval for an IP communicator is possible.

                -Hal
                From what I've been told, they are trading off overall system reliability for early notification of the circuit path interruption. For the usual POTS line setup, you could wait as long as 24 hours before realizing that there was no connection between the central station and the FACP, assuming both lines went down at the same time. When the central station fails to receive a test timer, it will notify the responsible parties.

                If the central station is capable of getting information from Honeywell/FireLite's IP-DACT, for example, the receiver pings the IP-DACT every 7-15 seconds and you'll get notification in a hurry if anything goes down. This doesn't address the issue of what happens if there's a fire while everybody is trying to fix the Internet. I'm pretty sure that if the local fire official is notified (as he/she is supposed to be) that he'll require a fire watch by the premises owner.

                Comment


                  #23
                  Originally posted by love9099 View Post
                  We have an installation that just switched all their lines to VOIP, they did not tell us about it and normally the panels self test every day. One day the VOIP system went down and we stopped getting test signals from the 10 buildings on site, later we found out it was due to the system shutting down and not being reset. They corrected this and now we are getting test signals. We are used to using Analog phone lines where we can set up line siezure using an RJ31X block. We contacted the State Fire Marshal and we were told VOIP was ok as long as it met the rest of the codes. The issue I see is they do not have a 24 hour battery backup UPS on their VOIP system to avoid the kind of problem that occured. Analog lines would not go down if there was a power outage. Can you help me with a code reference to support this UPS backup?
                  Is your dialer listed as compatible with the phone line specs? If not no, the device used must be listed for the purpose.

                  Comment


                    #24
                    Originally posted by gadfly56 View Post
                    From what I've been told, they are trading off overall system reliability for early notification of the circuit path interruption. For the usual POTS line setup, you could wait as long as 24 hours before realizing that there was no connection between the central station and the FACP, assuming both lines went down at the same time. When the central station fails to receive a test timer, it will notify the responsible parties.

                    If the central station is capable of getting information from Honeywell/FireLite's IP-DACT, for example, the receiver pings the IP-DACT every 7-15 seconds and you'll get notification in a hurry if anything goes down. This doesn't address the issue of what happens if there's a fire while everybody is trying to fix the Internet. I'm pretty sure that if the local fire official is notified (as he/she is supposed to be) that he'll require a fire watch by the premises owner.
                    You will know of telco failures long before 24 hours. The panel will set a local trouble for phone line fail and it is up to the building occupants to do something about it at that point. Otherwise yeah, the daily test fail will be an indication that phone lines are down.

                    With the IP communicator it will provide notification that it failed to communicate with the central station. The system will still work locally. This is why I always tell our customers to call the fire department themselves if there is a problem and not to rely solely on the communicator. More calls is better than none.

                    Comment


                      #25
                      [QUOTE=MisterCMK;1168457]You will know of telco failures long before 24 hours. The panel will set a local trouble for phone line fail and it is up to the building occupants to do something about it at that point. Otherwise yeah, the daily test fail will be an indication that phone lines are down.[QUOTE]

                      If, for some panels, the installation tech remembered to select "YES" for phone line monitoring. I've seen this not happen with Silent Knight IFP series panels

                      With the IP communicator it will provide notification that it failed to communicate with the central station. The system will still work locally. This is why I always tell our customers to call the fire department themselves if there is a problem and not to rely solely on the communicator. More calls is better than none.
                      Always a good idea. No question.

                      Comment

                      Working...
                      X