<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
robb wrote:
<blockquote cite="mid:48EE50C2.2070406@boardman.me.uk" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
I have a TDM400 working quite well, Digium dialled in and recompiled
chan_zap with some changes , to get BT Callerid working and I have set
hangup on polarity in the zaptel.conf which seems to work well<br>
<br>
this is a BT home line, not business, if you have a business line you
should get the DCT set to 800ms and the disconnect clear should work <br>
</blockquote>
<br>
<br>
Would you be kind enough to share the changes you made to get callerID
working please? Any chance of posting the relevant bits of your zap
config also?<br>
<br>
My situation is that I have callerid working most of the time on a home
BT line. Hangup is fairly reliably detected. TDM400P<br>
<br>
However, at a customers site on a bunch of business BT lines and the
same model of TDM400P we see unreliable hangups (not frequent, but
occasional times that lines are getting stuck off hook). Also callerId
is working about 50-60% of the time and when it doesn't work (or
genuinely that the callerId is witheld) there is a long pause for about
2-3 rings before Asterisk answers the zap line. It would be desirable
to limit this pause because it makes it look like they are being slow
to answer all the calls!<br>
<br>
Just wondering what changes you made?<br>
<br>
Also, anyone understand why DCT is different between home and business
lines? Can the Zap code be changed to avoid needing something tweaking
on the exchange?<br>
<br>
Thanks<br>
<br>
Ed W<br>
</body>
</html>