<div dir="auto">They're referring to the signaling type of the fire alarm dialer to the monitoring service / central station. There are different types including different kinds of pulsing, and then the Ademco contact ID which is mainly used in addressable systems.<div dir="auto"><br></div><div dir="auto">We have had luck with the 4+2 and other pulse dialings but mixed results with contact ID since it is dumped onto the line so quickly (I have a recording of it somewhere - it's very quick and sometimes is too quick where it is not received reliably - inband DTMF settings or not). It seems that systems with Ademco contact ID also like to call out a lot more than pulse systems likely because they're busier systems and probably more to report on.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">We usually put our dialtone on only where absolutely needed, or if it's some temporary setup for our customers and we try to corral them to a network monitor solution or a cellular / wireless / AESnet setup, again as others have mentioned, it will all depend on the jurisdiction and what they allow/disallow/support.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 15, 2020, 19:30 Camille Issa <<a href="mailto:camille@alianza.com">camille@alianza.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div>
<div style="direction:ltr">VoIP protocol is SIP. <span id="m_-6328329973717576069ms-outlook-ios-cursor">
</span></div>
</div>
<div><br>
</div>
<div>
<div>Camille Issa</div>
<div>919-623-2137</div>
</div>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_-6328329973717576069divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dennis <<a href="mailto:dennislv@gmail.com" target="_blank" rel="noreferrer">dennislv@gmail.com</a>><br>
<b>Sent:</b> Tuesday, December 15, 2020 7:00:19 PM<br>
<b>To:</b> Camille Issa <<a href="mailto:camille@alianza.com" target="_blank" rel="noreferrer">camille@alianza.com</a>><br>
<b>Cc:</b> <a href="mailto:voiceops@voiceops.org" target="_blank" rel="noreferrer">voiceops@voiceops.org</a> <<a href="mailto:voiceops@voiceops.org" target="_blank" rel="noreferrer">voiceops@voiceops.org</a>><br>
<b>Subject:</b> Re: [VoiceOps] ATAs compatible with fire alarm panels</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div style="font-family:verdana,sans-serif;font-size:small;color:#000000">
What signalling protocol are they using?</div>
<div style="font-family:verdana,sans-serif;font-size:small;color:#000000">
<br>
</div>
<div style="font-family:verdana,sans-serif;font-size:small;color:#000000">
We have a few Ademco Contact-ID panels out there. I've had good luck using Grandstreams with inband dtmf.</div>
<div>
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div><br>
</div>
Thanks...
<div>-Dennis</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div>
<div dir="ltr">On Tue, Dec 15, 2020 at 1:36 PM Camille Issa <<a href="mailto:camille@alianza.com" target="_blank" rel="noreferrer">camille@alianza.com</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p>Hello all – looking for recommendations (other than keeping the analog line) for VoIP ATA’s that are compatible with fire alarm panels. Anyone got a good working solution out there?<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><span style="color:black">Camille Issa | Vice President, Sales<b> </b></span><b><span style="color:rgb(0,114,188)"><br>
Alianza – The Cloud Communications Platform Company</span></b><u></u><u></u></p>
<p><span style="color:black">Call Or <b><i><u><a rel="noreferrer"><span style="color:rgb(5,99,193)">Text</span></a></u></i></b> 919-229-4040 | </span><a href="mailto:camille@alianza.com" target="_blank" rel="noreferrer"><span style="color:rgb(5,99,193)">camille@alianza.com</span></a><span style="color:rgb(31,73,125)"><br>
</span><span style="color:black"><a href="http://www.alianza.com/" target="_blank" rel="noreferrer"><span style="color:rgb(5,99,193)">Alianza</span></a> | <a href="http://www.alianza.com/call-to-the-cloud" target="_blank" rel="noreferrer"><span style="color:rgb(5,99,193)">Blog</span></a> | <a href="http://www.linkedin.com/company/alianza" target="_blank" rel="noreferrer"><span style="color:rgb(5,99,193)">LinkedIn</span></a> | <a href="http://www.twitter.com/alianza_inc" target="_blank" rel="noreferrer"><span style="color:rgb(5,99,193)">Twitter</span></a></span><u></u><u></u></p>
<p><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank" rel="noreferrer">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote>
</div>
</div>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank" rel="noreferrer">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>