These things are always really useful on paging integrations and super cheap- http://www.vikingproductstore.com/viking/security-equipment-21427-Viking_PI1_Paging_Interface_PI1.html
On Sun, May 28, 2017 at 2:32 PM, Nick Garrett <[email protected]> wrote: > 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) > > 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. > > > Nick Garrett > E-mail: [email protected] / Direct: 815-717-2046 <(815)%20717-2046> > > [image: Rival5 Technologies Corp] <http://www.rival5.com/> > > Rival5 Technologies Corp > Managed Cloud Communications > > Office: 815-717-2052 <(815)%20717-2052> / Toll-Free: 855-4-RIVAL5 > <(855)+474-8255> / Fax: 815-717-2053 <(815)%20717-2053> > 10074 West 190th Place / 41.544248, -87.865169Mokena, Illinois 60448-8752 > www.Rival5.com <http://www.rival5.com/> > > [image: Twitter] <http://twitter.com/rival5tech> [image: Facebook] > <http://facebook.com/rival5tech> [image: LinkedIn] > <https://www.linkedin.com/company/rival5-technologies-corp-> > > On Fri, May 26, 2017 at 5:06 PM, Norton, Mike <[email protected]> > wrote: > >> 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. >> >> >> >> -mn >> >> >> >> *From:* Ben Amick [mailto:[email protected]] >> *Sent:* May 26, 2017 4:02 PM >> >> *To:* Norton, Mike <[email protected]>; [email protected] >> *Subject:* RE: FXO port ignore battery failure >> >> >> >> 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. >> >> Either way, looks like you’ll have your solution by Monday. >> >> >> >> *From:* Norton, Mike [mailto:[email protected] >> <[email protected]>] >> *Sent:* Friday, May 26, 2017 4:57 PM >> *To:* Ben Amick <[email protected]>; [email protected] >> *Subject:* RE: FXO port ignore battery failure >> >> >> >> 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. >> >> >> >> 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. >> >> >> >> 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. >> >> >> >> -mn >> >> >> >> *From:* Ben Amick [mailto:[email protected] <[email protected]>] >> *Sent:* May 26, 2017 3:37 PM >> *To:* Norton, Mike <[email protected]>; [email protected] >> *Subject:* RE: FXO port ignore battery failure >> >> >> >> 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 >> >> >> >> *From:* cisco-voip [mailto:[email protected] >> <[email protected]>] *On Behalf Of *Norton, Mike >> *Sent:* Friday, May 26, 2017 2:52 PM >> *To:* [email protected] >> *Subject:* [cisco-voip] FXO port ignore battery failure >> >> >> >> 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. >> >> >> >> -- >> >> Mike Norton >> >> I.T. Specialist >> >> Peace Wapiti School Division No. 76 >> >> >> 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 >> >> >> 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 >> >> _______________________________________________ >> cisco-voip mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
