<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns1="http://schemas.microsoft.com/office/2004/12/omml">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceType"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place" downloadurl="http://www.5iantlavalamp.com/"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
        {mso-style-priority:99;}
span.MSOHYPERLINK
        {mso-style-priority:99;}
a:visited
        {mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
        {mso-style-priority:99;}
p
        {mso-style-priority:99;}
..MsoChpDefault
        {mso-style-type:export-only;}
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Calibri;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p
        {mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman";}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:Calibri;
        color:#1F497D;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I actually was contemplating ordering the
E&M card because of the CCO article.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thank you for the feedback.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Jason Aarons
(US) [mailto:jason.aarons@us.didata.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, September 30, 2007
10:00 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Ted Nugent; Lelio Fulgenzi<br>
<b><span style='font-weight:bold'>Cc:</span></b> Countryman, Edward;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [cisco-voip] <st1:place
w:st="on"><st1:PlaceName w:st="on">FXO</st1:PlaceName> <st1:PlaceType w:st="on">Port</st1:PlaceType></st1:place>
for overhead paging</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>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).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Thus I stick with
FXO/Valcom 2003A.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>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. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Ted Nugent
[mailto:tednugent73@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, September 30, 2007
10:36 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Lelio Fulgenzi<br>
<b><span style='font-weight:bold'>Cc:</span></b> Jason Aarons (US); Countryman,
Edward; cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] <st1:place
w:st="on"><st1:PlaceName w:st="on">FXO</st1:PlaceName> <st1:PlaceType w:st="on">Port</st1:PlaceType></st1:place>
for overhead paging<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p style='margin:0in;margin-bottom:.0001pt'><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'>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. </span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On 9/26/07, <b><span style='font-weight:bold'>Lelio
Fulgenzi</span></b> <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>>
wrote:</span></font></span> <o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>is this with the use of an adapter? the adapter has all these dials and<br>
knobs that protect agains that sort of stuff. <br>
<br>
although a 130db screech would be interesting to see in our animal barns.<br>
<br>
----- Original Message -----<br>
From: "Jason Aarons (US)" <<a
href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com </a>><br>
To: "Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>>;
"Countryman, Edward"<br>
<<a href="mailto:Edward.Countryman@provena.org">Edward.Countryman@provena.org
</a>>; <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Sent: Wednesday, September 26, 2007 2:58 PM<br>
Subject: RE: [cisco-voip] <st1:place w:st="on"><st1:PlaceName w:st="on">FXO</st1:PlaceName>
<st1:PlaceType w:st="on">Port</st1:PlaceType></st1:place> for overhead paging<br>
<br>
<br>
>I would disagree, FXS has limited supervision disconnect, stick with a <br>
> FXO as best practice. I've seen FXS interfaces get stuck offhook and the<br>
> paging units screech 130db noise....also ATA behaves differently between<br>
> CCM and CME, FXO doesn't.<br>
><br>
> -jason <br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</a>] On Behalf Of Lelio Fulgenzi<br>
> Sent: Wednesday, September 26, 2007 2:54 PM<br>
> To: Countryman, Edward; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] <st1:place w:st="on"><st1:PlaceName w:st="on">FXO</st1:PlaceName>
<st1:PlaceType w:st="on">Port</st1:PlaceType></st1:place> for overhead paging <br>
><br>
> save yourself the trouble....get an adapter and use an FXS port. ;)<br>
><br>
> we use the Bogen TAM-B.<br>
><br>
> ----- Original Message -----<br>
> From: "Countryman, Edward" <<a
href="mailto:Edward.Countryman@provena.org"> Edward.Countryman@provena.org</a>><br>
> To: <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
> Sent: Wednesday, September 26, 2007 2:41 PM<br>
> Subject: [cisco-voip] <st1:place w:st="on"><st1:PlaceName w:st="on">FXO</st1:PlaceName>
<st1:PlaceType w:st="on">Port</st1:PlaceType></st1:place> for overhead paging <br>
><br>
><br>
>> Has anyone successfully configured and used an FXO port to access an<br>
>> overhead paging system? All I can seem to find are E&M
examples.<br>
>> _______________________________________________ <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">https://puck..nether.net/mailman/listinfo/cisco-voip
</a><br>
>><br>
> _______________________________________________<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">https://puck..nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
> -----------------------------------------<br>
> Disclaimer:<br>
><br>
> This e-mail communication and any attachments may contain<br>
> confidential and privileged information and is for use by the <br>
> designated addressee(s) named above only. If you are not the<br>
> intended addressee, you are hereby notified that you have received<br>
> this communication in error and that any use or reproduction of<br>
> this email or its contents is strictly prohibited and may be<br>
> unlawful. If you have received this communication in error,
please<br>
> notify us immediately by replying to this message and deleting it<br>
> from your computer. Thank you. <br>
><br>
><br>
<br>
_______________________________________________<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">https://puck..nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
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.
</STRONG></P></BODY>