<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Thanks for the responses.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Here is an update on my zap groundstart, loopstart,
"disconnect supervision" woes. Apparently, the groundstart mode in
the CAC FXO module works on loopstart lines. I still don't understand how
and why.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I have loopstart lines.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The only way "disconnect supervision" works on my system is if
I set the FXO module to groundstart. However! There is a big
caveat. In groundstart mode, incoming caller ID stops working! This
is something I am going to have to live with for now as disconnecting the line
on hang-up is far more important than caller ID.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I have no idea if the caller ID problem is a problem with
CAC FXO modules or the zap channel software or the fact that we are using
groundstart signaling on a loopstart line.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I can confirm that this is the behavior with both CAC I and
CAC II units as I have a CAC II unit and I spoke with Michael on this list who
has a CAC I unit. Both of us are in the same predicament.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Anyway, I hope others find this info useful. If anyone
has any other ideas on how I can get my caller ID to work I would be really
excited about that.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT size=2>Thanks,</FONT></DIV>
<DIV><FONT size=2>Jason</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>PS: I have seen people mention that, when you have many lines,
PRI is cheaper. This is not our case at all. San Francisco. We
have eight lines at the cost of $0.01 per line. All we pay for really is
the call time.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=swell@labranch.com href="mailto:swell@labranch.com">Surfer Dude</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=asterisk-users@lists.digium.com
href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, June 17, 2003 4:05
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [Asterisk-Users] Question ::
groundstart and loopstart</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2>Hello Astrites,</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I was just about to send out a long email about not being
able to detect hang-up with my CAC II FXO module on my PSTN POTS lines.
I had tried many configurations. I had attached a toner to the line to
see if I was getting this "disconnect supervision" signal after hang-up.
(toner has a line powered light in the off position) It seemed that I
was getting the signal, as:</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2> The light was steady on
onhook</FONT></DIV>
<DIV><FONT size=2> When the line rang the light
dimmed.</FONT></DIV>
<DIV><FONT size=2> When I picked up the line stayed dim (If
I remember correctly)</FONT></DIV>
<DIV><FONT size=2> When the other end hung up the light
stayed on</FONT></DIV>
<DIV><FONT size=2> Then turned off momentarily a few seconds
later. (I suspected this was "disconnect supervision")</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Anyway asterisk never detected hang-up. Everything
else worked. I was frustrated as hell.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>After a few days of trying everything, I tried to set my CAC
II FXO module to Groundstart and configured zaptel.conf and zapata.conf to
groundstart signaling.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Voila! Everything work!</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The question is how does groundstart and loopstart
work? How was I able to have a somewhat working system using loopstart
when it seems that the phone company signaling was groundstart? Can I
assume that my lines are indeed groundstart?</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I am really happy that it works. I can now begin the
process of deployment with a much greater feeling of security.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Jason</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV></BLOCKQUOTE></BODY></HTML>