<br><font size=2 face="sans-serif">This looks like an issue that we had
with bad DSP's. Has TAC mentioned anything about this to you? Ours
happened about 18 months ago but sounds very familiar.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Paul Choi <asobihoudai@yahoo.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">06/18/2007 10:53 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Thomas Garman <TGarman@homesavings.com>,
cisco-voip@puck.nether.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [cisco-voip] FXO Port failures</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Have you tried using a different sig. with the LEC's<br>
assistance? <br>
<br>
Can you use this FXO card in another box to see if you<br>
come up with the same results? It sounds like you have<br>
two boxes with the same cards. <br>
<br>
Does vtsp debug tell you anything more than the debug<br>
you've already collected?<br>
<br>
Have you tested to see if there is a problem between<br>
you and the LEC?<br>
<br>
--- Thomas Garman <TGarman@homesavings.com> wrote:<br>
<br>
> <br>
> Paul,<br>
> We are using loopstart.<br>
> <br>
> <br>
> <br>
> -----Original Message-----<br>
> From: Paul Choi [mailto:asobihoudai@yahoo.com] <br>
> Sent: Monday, June 18, 2007 10:38 AM<br>
> To: Thomas Garman; cisco-voip@puck.nether.net<br>
> Subject: Re: [cisco-voip] FXO Port failures<br>
> <br>
> Thomas,<br>
> <br>
> What sort of signaling are you using on these ports?<br>
> <br>
> --- Thomas Garman <TGarman@homesavings.com> wrote:<br>
> <br>
> > <br>
> > <br>
> > <br>
> > I seem to be having trouble at 2 of my sites,<br>
> having<br>
> > constant failures<br>
> > of FXO ports (connected to the PSTN). The port<br>
> will<br>
> > work fine for about<br>
> > a day (sometimes 2), then the port will not "pick<br>
> > up" incoming calls, or<br>
> > make out bound calls.<br>
> > <br>
> > When the port fails the debugs look like the telco<br>
> > is sending a<br>
> > disconnect to us, however in lab testing the bad<br>
> > ports, this is not the<br>
> > case (the port is sensing a disconnect, but none<br>
> is<br>
> > actually being<br>
> > sent).<br>
> > <br>
> > We have been able to move the problem line(s) to<br>
> > another port, which<br>
> > will work fine, and then after a day or two will<br>
> > exhibit the same<br>
> > problem (failure).<br>
> > <br>
> > We have gone through the shut/no shut, as well as<br>
> an<br>
> > entire router<br>
> > reload, and router power cycle, and even an IOS<br>
> > upgrade (from 12.4.XC4<br>
> > to 12.4.9T3).<br>
> > <br>
> > The port, once failed, cannot be recovered.<br>
> > <br>
> > We have contacted TAC, and their solution was to<br>
> > send us new cards.<br>
> > <br>
> > I have also engaged the telco (several times) to<br>
> > test the lines, and<br>
> > they report no problems. <br>
> > <br>
> > There seems to be something that is causing the<br>
> > ports to fail, and I was<br>
> > wondering if anyone else has ever seen this type<br>
> of<br>
> > problem? <br>
> > <br>
> > <br>
> > <br>
> > Thanks in advance,<br>
> > <br>
> > Tom G.<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> ><br>
><br>
************************************************************************<br>
> > STATEMENT OF SECURITY AND CONFIDENTIALITY<br>
> > Email messages sent through an open network are<br>
> > transmitted unencrypted <br>
> > and should therefore not contain confidential<br>
> > information. The <br>
> > information contained in this electronic message<br>
> and<br>
> > any files <br>
> > transmitted with it are private and intended for<br>
> the<br>
> > sole use of the<br>
> > individual or entity to whom they are addressed.<br>
> If<br>
> > you are not the<br>
> > intended recipient, please notify the<br>
> > postmaster@homesavings.com and<br>
> > destroy all copies of this message and any<br>
> > attachments.<br>
> ><br>
><br>
************************************************************************<br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> ><br>
> https://puck.nether.net/mailman/listinfo/cisco-voip<br>
> > <br>
> <br>
> <br>
> <br>
> <br>
><br>
________________________________________________________________________<br>
> ____________Ready for the edge of your seat? <br>
> Check out tonight's top picks on Yahoo! TV. <br>
> http://tv.yahoo.com/<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
><br>
************************************************************************<br>
> STATEMENT OF SECURITY AND CONFIDENTIALITY<br>
> Email messages sent through an open network are<br>
> transmitted unencrypted <br>
> and should therefore not contain confidential<br>
> information. The <br>
> information contained in this electronic message and<br>
> any files <br>
> transmitted with it are private and intended for the<br>
> sole use of the<br>
> individual or entity to whom they are addressed. If<br>
> you are not the<br>
> intended recipient, please notify the<br>
> postmaster@homesavings.com and<br>
> destroy all copies of this message and any<br>
> attachments.<br>
><br>
************************************************************************<br>
> <br>
> <br>
<br>
<br>
<br>
<br>
____________________________________________________________________________________<br>
Don't get soaked. Take a quick peak at the forecast<br>
with the Yahoo! Search weather shortcut.<br>
http://tools.search.yahoo.com/shortcuts/#loc_weather<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</tt></font>
<br>