[cisco-voip] FXO Port for overhead paging

[Countryman, Edward]

I actually was contemplating ordering the E&M card because of the CCO
article.

 

Thank you for the feedback.

 

________________________________

From: Jason Aarons (US) [mailto:jason.aarons at us.didata.com] 
Sent: Sunday, September 30, 2007 10:00 PM
To: Ted Nugent; Lelio Fulgenzi
Cc: Countryman, Edward; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] FXO Port for overhead paging

 

The V9970 with 2FXS is the unit I commonly see with problems. About once
a month in customer X 40 warehouses one acts up and you have to shut/no
shut the fxs interface or reset the 9970. Valcom and Cisco tech support
are pretty clear FXS has limited disconnect supervision, and FXS
treatment varies by product (CME vs CCM).

 

Thus I stick with FXO/Valcom 2003A.

 

Whoever wrote the CCO article on E&M I don't think had enough real-world
experience with paging. When I walk into a customer using E&M for
paging,  I ask why E&M, they state they found the article on CCO and
ordered the E&M card.  

 

From: Ted Nugent [mailto:tednugent73 at gmail.com] 
Sent: Sunday, September 30, 2007 10:36 PM
To: Lelio Fulgenzi
Cc: Jason Aarons (US); Countryman, Edward; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] FXO Port for overhead paging

 

 

 

I've personally had zero issues with fxs (I typically push for the
valcom V9970, cheap easy) and only had one pain in the ass with fxo and
that was probably a disconnect between the customer and I and not an
issue with the adapter (I typically push for the valcom V2000 or better
for FXO). I've done a bunch of both fxs and fxo and not had any notable
issues with either once you determine what they have or even better if I
had the luxury of a recommendation. Once you determine what you're
interfacing with (fxo,fxs, loop ground etc...) the configuration is
pretty much self explanatory or has been for me. 

 

 



 

On 9/26/07, Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 

is this with the use of an adapter? the adapter has all these dials and
knobs that protect agains that sort of stuff. 

although a 130db screech would be interesting to see in our animal
barns.

----- Original Message -----
From: "Jason Aarons (US)" <jason.aarons at us.didata.com >
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>; "Countryman, Edward"
<Edward.Countryman at provena.org >; <cisco-voip at puck.nether.net>
Sent: Wednesday, September 26, 2007 2:58 PM
Subject: RE: [cisco-voip] FXO Port for overhead paging


>I would disagree, FXS has limited supervision disconnect, stick with a 
> FXO as best practice. I've seen FXS interfaces get stuck offhook and
the
> paging units screech 130db noise....also ATA behaves differently
between
> CCM and CME, FXO doesn't.
>
> -jason 
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net ] On Behalf Of Lelio
Fulgenzi
> Sent: Wednesday, September 26, 2007 2:54 PM
> To: Countryman, Edward; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] FXO Port for overhead paging 
>
> save yourself the trouble....get an adapter and use an FXS port. ;)
>
> we use the Bogen TAM-B.
>
> ----- Original Message -----
> From: "Countryman, Edward" < Edward.Countryman at provena.org
<mailto:Edward.Countryman at provena.org> >
> To: <cisco-voip at puck.nether.net>
> Sent: Wednesday, September 26, 2007 2:41 PM
> Subject: [cisco-voip] FXO Port for overhead paging 
>
>
>> Has anyone successfully configured and used an FXO port to access an
>> overhead paging system?  All I can seem to find are E&M examples.
>> _______________________________________________ 
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck..nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip> 
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck..nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip> 
>
> -----------------------------------------
> Disclaimer:
>
> This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the 
> designated addressee(s) named above only.  If you are not the
> intended addressee, you are hereby notified that you have received
> this communication in error and that any use or reproduction of
> this email or its contents is strictly prohibited and may be
> unlawful.  If you have received this communication in error, please
> notify us immediately by replying to this message and deleting it
> from your computer. Thank you. 
>
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck..nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip> 

 

________________________________

Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20071001/5bd8a269/attachment-0001.html