<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText81031 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Low voltage doesn't
necessarily have to be caused by an inline device (surge
protector)..... Might be worth a look</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net on
behalf of Kris Seraphine<BR><B>Sent:</B> Fri 8/25/2006 3:16 PM<BR><B>To:</B>
cisco-voip<BR><B>Subject:</B> Re: [cisco-voip] FXO calls disconnect when
answered<BR></FONT><BR></DIV>
<DIV>that's a good thought. <BR><BR>Unfortunately I don't think it applies
to this case. I'm coming right off the block. Unless the telco is
doing something outside the building. <BR><BR>
<DIV><SPAN class=gmail_quote>On 8/25/06, <B class=gmail_sendername>Scott Coner
(US)</B> <<A
href="mailto:scott.coner@us.didata.com">scott.coner@us.didata.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV lang=EN-US vlink="blue">
<DIV>
<P><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I had a similar
problem with a customer and it turned out to be low voltage on the POTS
line. In my case the low voltage situation was being caused by an inline
surge protector on the POTS line. </SPAN></FONT></P>
<P><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Scott</SPAN></FONT></P>
<P><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<DIV>
<DIV style="TEXT-ALIGN: center" align=center><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> <A
href="mailto:cisco-voip-bounces@puck.nether.net"
target=_blank>cisco-voip-bounces@puck.nether.net</A> [mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net" target=_blank>
cisco-voip-bounces@puck.nether.net</A>] <B><SPAN style="FONT-WEIGHT: bold">On
Behalf Of </SPAN></B>Kris Seraphine<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, August 25, 2006 2:27
PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> cisco-voip<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> [cisco-voip] FXO calls
disconnect when answered</SPAN></FONT></P></DIV></DIV>
<DIV><SPAN class=e id=q_10d46b08e5f42601_1>
<P><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">Hi<BR><BR>I've been struggling with this issue for
over a month and both I and TAC seem to be stumped. <BR><BR>I have a
customer with a small office that we are trying to migrate to a centralized
CCM cluster. They have a 1760V with 4 analog lines that we want to
connect to an FXO card. When we connect the lines to the router for testing I
get the following behavior. <BR><BR>PSTN caller calls into the system.
<BR>The IP phone user hears the phone ring and answers the call.<BR>The IP
phone user sees the call disconnect After a second or two, the call begins to
ring again on the IP phone If the IP phone user answers the call again, the
call disconnects and the process repeats The PSTN caller hears ringback the
whole time. <BR><BR>The problem seems to be that the router is interpreting a
disconnect coming from the telco.<BR><BR>Trace snippet:-<BR>008192: ..Jul 31
08:36:28.484: htsp_process_event:
[2/0,<BR>FXOLS_PROCEEDING,
<BR>E_HTSP_CONNECT]fxols_offhook_connect <BR>008193: .Jul 31 08:36:28.488:
[2/0] set signal state = 0xC timestamp = 0<BR>008194: .Jul 31 08:36:28.488:
htsp_timer_stop<BR>008195: .Jul 31 08:36:28.488: htsp_process_event: [2/0,
FXOLS_CONNECT,<BR><BR>E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
<BR>008196: .Jul 31 08:36:28.716: htsp_process_event: [2/0,
FXOLS_CONNECT,<BR><BR>E_DSP_SIG_0100]fxols_normal_battery<BR>008197: ..Jul 31
08:36:28.744: htsp_process_event: [2/0,
FXOLS_CONNECT,<BR><BR>E_DSP_SIG_1100]fxols_offhook_disc <BR><BR>I've talked to
the CO guy but he's been little help. I did have them run a ground start
trunk for testing but it exibits the same behavior. <BR><BR>I've tried
every combination of battery-reversal supervisory disconnect etc... that I can
think of but I cannot seem to solve this problem. <BR><BR>TAC does not
think its hardware related but I'm going to send a replacement router out just
in case. <BR><BR>I'm hoping someone might have some suggestions for me.
<BR><BR>Thanks in advanced. <BR><BR>Kris Seraphine <BR>CCIE No.
15163, MCSE<BR><A href="mailto:Kris.Seraphine@cliftoncpa.com"
target=_blank>Kris.Seraphine@cliftoncpa.com</A><BR><BR><BR><BR
clear=all><BR>-- <BR>kris seraphine </SPAN></FONT></P></SPAN></DIV>
<DIV></DIV></DIV>
<DIV>
<P></P>
<HR SIZE=1>
<P></P><BR>
<P><STRONG><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></STRONG></P></DIV></DIV></BLOCKQUOTE></DIV><BR><BR clear=all><BR>--
<BR>kris seraphine </DIV></BODY></HTML>
<HTML><BODY><P><hr size=1></P><br>
<P><STRONG><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>
</STRONG></P></BODY></HTML>