<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></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-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">TAM-B would connect to an FXS port, not an FXO like you currently use. FXO is a better choice because it inherently provides disconnect supervision. I have one installation, that pre-dates my involvement, that
uses a TAM-B and a few times a year we have issues with getting stuck off-hook and need to shut + no shut it and/or power-cycle the TAM-B. For new installs, I use the Bogen PCM2000. It is more than just an “interface” to a paging system though; it *<b>is</b>*
a paging system.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">That said, it sounds like all you need is somebody who can correct the programming mistake that “they” made on your paging system. Disconnect the FXO, plug a standard POTS telephone into the paging system, and
tell “them” to make that work. Most phone contractors who work on those kinds of systems get terribly confused/overwhelmed when you try to tie in with the voice gateway. The fact that you pointlessly chased down IOS updates and TAC cases tells me it has probably
not been a confusion-free situation. Tell “them” you just want it to work with a standard POTS set (which, really, is all they need to know anyway) and, in my experience, they will usually have everything solved in no time. Then go in behind them, and plug
it in to your FXO port.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-- <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mike Norton<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I.T. Support<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Peace Wapiti School Division No. 76<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Helpdesk: 780-831-3080<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Direct: 780-831-3076<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-CA">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-CA"> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Sandy Lee<br>
<b>Sent:</b> September-07-11 9:18 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Paging solution interface<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal">We have a 3rd party paging system that we connected through an FXO port on a gateway and worked fine. We defined a DN in UCM that is routed to the gateway, which is connected to the paging system that gives a dial-tone, we enter digits
to determine which speakers to reach and that’s it. They recalibrated the paging system to add speakers and it doesn’t recognise the DTMFs anymore. We upgraded the IOS, opened a case with TAC and still doesn’t work.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m looking to replace the gw/fxo interface with something else, but don’t know what to look for. Some of you guys talked about Bogen TAMB, but how does it work exactly? Is this what I need ?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks and regards.<o:p></o:p></p>
<p class="MsoNormal">Sandy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>