[cisco-voip] Cisco VOIP and fire alarm phone lines

[Leslie Meade]

We have the same thing but we have used VG224’s for all our firepannels, with no issues

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Fuermann, Jason
Sent: Wednesday, November 04, 2009 2:14 PM
To: 'JASON BURWELL'; Tim Reimers; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Cisco VOIP and fire alarm phone lines

 

When we checked there was an exception if you owned the entire cable plant that you didn’t have to use the Telco

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of JASON BURWELL
Sent: Wednesday, November 04, 2009 2:12 PM
To: Tim Reimers; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Cisco VOIP and fire alarm phone lines

 

You may want to check up on NFPA72 Fire Alarm Code, I don't recall the section. Unless it has recently changed, I am almost certain at least the primary line has to be a dedicated POTS line direct from the Telco. I know the secondary line can be shared if used in conjunction with an RJ31X but do not recall if there are any PBX restrictions on it.

 

Jason

 

 

 

________________________________

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Reimers
Sent: Wednesday, November 04, 2009 2:52 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Cisco VOIP and fire alarm phone lines

Does anyone know if Cisco has any recommendations they officially make on supporting analog telephony devices like fire alarm panels?

 

We use ATAs for supplying dialtone to  fire alarm dialers, and we're getting issues with some panels getting "comm trouble" issues, and data not getting to the monitoring company correctly.

 

The security vendors and the OEM manufacturers are saying "we don't recommend VOIP for alarm lines"

 

Our management is saying that surely Cisco supports this, and with the correct configuration, they can make this happen.

 

I'm looking for some official Cisco guidance (links to design guide statements, etc) 

that might break the deadlock, and either allow me to prove to the vendors and OEMs that VOIP is indeed a stable technology

or, allow Cisco the graceful way of saying "it's best not to do that"

 

Anyone got anything to offer?

 

I'd imagine that there's a fair number of folks who've just decided not to use VOIP for this purpose- 

That's just not the decision here though..and I'm not the policymaker on that level.

 

Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091106/07f2dce1/attachment.html>