<div dir="ltr">These things are always really useful on paging integrations and super cheap- <a href="http://www.vikingproductstore.com/viking/security-equipment-21427-Viking_PI1_Paging_Interface_PI1.html">http://www.vikingproductstore.com/viking/security-equipment-21427-Viking_PI1_Paging_Interface_PI1.html</a></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 28, 2017 at 2:32 PM, Nick Garrett <span dir="ltr"><<a href="mailto:nick.garrett@rival5.com" target="_blank">nick.garrett@rival5.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I have encountered this while attempting to integrate with Dukane MCS350's. Our FXO device will show "busy" since there is no loop. The MCS350 is just pumping "dialtone" down that pair all the time. Searched all over for some sort of SIP device that could connect to a pair and allow for bi-directional audio (to access zones, rooms, programming, etc)<div><br></div><div>We've opted to just throw in a device that will flip a relay on those systems and force them to use another 600 Ohm input.</div></div><div class="gmail_extra"><br clear="all"><div><div class="m_645956391096488009gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:12.8px"><div style="font-size:12.8px"><div style="font-size:12.8px"><p style="margin:0px 0px 10px;font-family:helvetica,arial,sans-serif;font-size:12px;line-height:14px"><br></p><p style="margin:0px 0px 10px;font-family:helvetica,arial,sans-serif;font-size:12px;line-height:14px"><span style="color:rgb(33,33,33);font-weight:bold">Nick Garrett</span><span style="color:rgb(33,33,33)"><br></span><font style="color:rgb(0,0,0)">E-mail: </font><font style="color:rgb(33,33,33)"><a href="mailto:Nick.Garrett@Rival5.com" style="color:rgb(17,85,204)" target="_blank"><font color="#0000ff">Nick.Garrett@Rival5.<wbr>com</font></a><span> </span></font><span style="color:rgb(33,33,33)">/ Direct: </span><span><a href="tel:(815)%20717-2046" target="_blank"><font color="#0000ff">815-717-2046</font></a></span><br></p><p style="margin:0px 0px 10px;font-family:helvetica,arial,sans-serif;font-size:12px;line-height:14px;color:rgb(33,33,33)"><a href="http://www.rival5.com/" style="color:rgb(36,169,57);background-color:transparent;text-decoration:none" target="_blank"><img src="https://htmlsigs.s3.amazonaws.com/logos/files/000/728/739/landscape/rival5-tr.png" alt="Rival5 Technologies Corp" border="0" width="96" height="40" style="border:0px;vertical-align:middle"></a><br></p><p style="margin:0px 0px 10px;color:rgb(0,0,0);font-family:helvetica,arial,sans-serif;font-size:12px;line-height:14px"><span style="font-family:arial,sans-serif;font-size:12.8px"></span></p><p style="margin:0px 0px 10px;color:rgb(0,0,0);font-family:helvetica,arial,sans-serif;font-size:12px;line-height:14px"><span style="font-weight:bold;color:rgb(33,33,33)">Rival5 Technologies Corp</span><span><br></span><span style="color:rgb(33,33,33)">Managed Cloud Communications</span></p><p style="margin:0px 0px 10px;font-family:helvetica,arial,sans-serif;font-size:12px;line-height:14px"><font color="#000000">Office: <a href="tel:(815)%20717-2052" value="+18157172052" target="_blank">815-717-2052</a> <span>/ Toll-Free: <a href="tel:(855)+474-8255" target="_blank">855-4-RIVAL5</a> / </span>Fax: <a href="tel:(815)%20717-2053" target="_blank"><font>815-717-2053</font></a></font><span style="color:rgb(0,0,0)"><br></span><span style="color:rgb(33,33,33)">10074 West 190th Place / 41.544248, -87.865169</span><span style="color:rgb(0,0,0);display:block"></span><span style="color:rgb(33,33,33)">Mokena, Illinois 60448-8752</span><font color="#000000" style="color:rgb(80,0,80)"> </font><span style="color:rgb(0,0,0)"><br></span><a href="http://www.rival5.com/" style="color:rgb(17,85,204)" target="_blank"><font color="#0000ff">www.Rival5.com</font></a><font color="#500050"><span></span><span></span></font><a style="color:rgb(17,85,204)"></a></p><p style="margin:0px 0px 10px;color:rgb(0,0,0);font-size:0px;line-height:0;font-family:helvetica,arial,sans-serif"><a href="http://twitter.com/rival5tech" style="color:rgb(36,169,57);background-color:transparent;text-decoration:none;display:inline" target="_blank"><img width="24" height="24" src="https://s3.amazonaws.com/htmlsig-assets/grey/twitter.png" alt="Twitter" style="border:none;vertical-align:middle;margin-bottom:2px;display:inline"> </a><span style="white-space:nowrap"><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="2" style="border:0px;vertical-align:middle"> </span><a href="http://facebook.com/rival5tech" style="color:rgb(36,169,57);background-color:transparent;text-decoration:none;display:inline" target="_blank"><img width="24" height="24" src="https://s3.amazonaws.com/htmlsig-assets/grey/facebook.png" alt="Facebook" style="border:none;vertical-align:middle;margin-bottom:2px;display:inline"> </a><span style="white-space:nowrap"><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="2" style="border:0px;vertical-align:middle"> </span><a href="https://www.linkedin.com/company/rival5-technologies-corp-" style="color:rgb(36,169,57);background-color:transparent;text-decoration:none;display:inline" target="_blank"><img width="24" height="24" src="https://s3.amazonaws.com/htmlsig-assets/grey/linkedin.png" alt="LinkedIn" style="border:none;vertical-align:middle;margin-bottom:2px;display:inline"> </a><span style="white-space:nowrap"><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="2" style="border:0px;vertical-align:middle"></span></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Fri, May 26, 2017 at 5:06 PM, Norton, Mike <span dir="ltr"><<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mikenorton@pwsd76.ab.ca</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_645956391096488009m_52302336517903237WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">Any paging systems I’ve come across can connect to either FXS or FXO, whichever you configure it for. FXO is a far superior choice because of the disconnect supervision and the ease of sending out digits to it,
but it seems most paging systems expect FXS in their default configuration.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">-mn<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><span><b>From:</b> Ben Amick [mailto:<a href="mailto:bamick@HumanArc.com" target="_blank">bamick@HumanArc.com</a>] <br>
</span><b>Sent:</b> May 26, 2017 4:02 PM</p><div><div class="m_645956391096488009h5"><br>
<b>To:</b> Norton, Mike <<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mikenorton@pwsd76.ab.ca</a>>; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> RE: FXO port ignore battery failure<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="m_645956391096488009h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">That’s interesting. All the paging systems I’ve hooked up in the past I’ve done via a paging adapter off an FXS port.
<u></u><u></u></p>
<p class="MsoNormal">Either way, looks like you’ll have your solution by Monday. <u></u>
<u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Norton, Mike [<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mailto:mikenorton@pwsd76.ab.c<wbr>a</a>]
<br>
<b>Sent:</b> Friday, May 26, 2017 4:57 PM<br>
<b>To:</b> Ben Amick <<a href="mailto:bamick@HumanArc.com" target="_blank">bamick@HumanArc.com</a>>;
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> RE: FXO port ignore battery failure<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">A station port would need to supply talk battery to the station, so yes that would need FXS, but no that’s not what I want.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Basically I was trying to get a dry audio output for an overhead paging system. Kinda like you would with an E&M port, but I only have the FXO ports. The idea was for this to be a temporary workaround – contractor
is installing a new paging system to replace a failed one but they are missing the module they need to interface with a telephone port, so in the meantime all they can accept is a dry audio feed.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Anyway, it is now looking like the paging contractor will be able to get the proper module they need by Monday, so I’m not going to bother trying to do the temporary workaround and I’ll just do the normal FXO
way next week.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">-mn<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Ben Amick [<a href="mailto:bamick@HumanArc.com" target="_blank">mailto:bamick@HumanArc.com</a>]
<br>
<b>Sent:</b> May 26, 2017 3:37 PM<br>
<b>To:</b> Norton, Mike <<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mikenorton@pwsd76.ab.ca</a>>;
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> RE: FXO port ignore battery failure<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I just want to ask why? The situation you’re talking about makes me think of end stations, in which case you’d want to have an FXS port, not an FXO<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@puc<wbr>k.nether.net</a>]
<b>On Behalf Of </b>Norton, Mike<br>
<b>Sent:</b> Friday, May 26, 2017 2:52 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] FXO port ignore battery failure<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I need to send a call out an FXO port that does not have talk battery or dialtone on the other end. Normally an FXO port will notice the lack of talk battery and the call will fail. Is there a way to configure the FXO port to not check
for talk battery? This is on a 2900 running 15.3M.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">-- <u></u><u></u></p>
<p class="MsoNormal">Mike Norton<u></u><u></u></p>
<p class="MsoNormal">I.T. Specialist<u></u><u></u></p>
<p class="MsoNormal">Peace Wapiti School Division No. 76<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
<u></u><u></u></span></p>
</div></div></div>
</div>
<br></div></div>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailma<wbr>n/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>