Caller ID and distinctive ringing problems with TDM400 cards

Hi
It is VERY hard to read this as the lines wrap.

As mentioned before edit the file so it only has the settings you need. There looks like a few that shouldnt be there such as rxwink. edit it to the bare minimum then try it.

Ian

Though what you are suggesting is sound, and I would normally agree with you. My question from my earlier post was why would this make a difference on this machine seeing that the problem happens even when the machine has been rebooted and asterisk has not been run. That is;

Machine rebooted cold.
Asterisk does not auto run
Load module with modprobe wctdm, which also loads zaptel
Plug BT line into TDM400P card
Ring line
Line goes busy.

The TDM400P card, or the zaptel modules seem to be the issue. I come to this assumption because the zonedata.c file contains information to define the ring. Therefore, I would have to assume that BT is using a differnet ring where I am, or the fact that I have CLI on the line could be causing the problem. Also, as BT is converting DSL lines, which I am one as well, to their new DSLAM's it could also be that the line levels have changed. Even if this is the case, why would this not affect other bits of equipment which are not suffering from this problem ? Is there a way to use the ztmonitor to decode the ring and display the timings ? I know that this utility does see the ring, I just don't know how to confirm that the timings in the zonedata.c file are correct.

Just to make it clear, I have slimed down my zaptel.conf to the following and yes, I still have the problem;

[trunkgroups]

[channels]
context=from-pstn
signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
channel => 3

Just been doing some more research on this issue and found in the BT SIN document 351v4p5 that a rin can be;

0.4s on
0.2s off
0.4s on
2s off

Or

0.35s on
0.22s off
and then cycle through the previous definition.

As the zonedata.c file only contains the first definition, could the code be getting confused if the later pattern is presented ?

Check the following URL for the definition;

http://www1.btwebworld.com/sinet/351v4p5.pdf

Hi Geoff

You are looking to deep and in the wrong place. as mentioned, the issue looks to be with your card and how its loading.

The Zonedata is for generation and possibly call progress tone detection. Ring patterns are detected but not from the zonedata file, If detinctive ring detection is enabled then the patterns are defined in the zapata.conf

What OS are you using ? as the only mention I have seen of proSlics is in bsd.

What do you get on the CLI when you set verbose to 7 and debug to 7 and what is in /var/log/asterisk/messages ?

Also could you post the results of lsmod to see if zaptel is loaded

Forget the Sins, they have there uses but there are 100's of TDM400s in the UK and they do not have the problem you are having. Yours is a driver problem by the looks of it.

Ian,

I assume when you ask which OS I am running your not asking if its Linux, rather you are asking which distro. The distro is a version of Mandriva, but it has a modified kernel. This I stated in one of my first posts, and also stated that since the problem started, yes it was working then stopped, I have tried several different kernels, even reverting back to a very old 2.6 kernel. The only thing I have not done is go to a 2.4 kernel.

Again I think you have missed my point. I have already written several times that I have tried multiple versions of Linux, and multiple versions of the zaptel drivers. When I first got the card the system worked, with the config that I originaly posted. The only possible thing that could have changed to cause such a specific problem is the line characteristics, which BT define. Its interesting to read the SIN document that I reffered to in my previous post as this implies that BT does not have a set ring pattern, as this could vary on a per exchange basis. Also, they give two different ring options. As the TDM400P card, or at least the modules loaded in Linux, are not detecting the ring, the pattern being used is the logical area to look at and this is coded into zonedata.c. Again, note that the card does detect the polarity reversal, this is logged as I have it running in debug mode;

Aug 12 10:26:25 filestore01 kernel: 4294913958 Polarity reversed (1 -> -1)
Aug 12 10:26:25 filestore01 kernel: 4294914018 Polarity reversed (-1 -> 1)

Its just failing to see the ring despite the ztmonitor showing that the audio tones are being seen. This again implies that the C code, due to definitions, is not seeing the pattern that it has been told to expect.

Hi Geoff

The reason I ask OS is that * is run on Solaris, BSD, Linux and windows. and all have differing levels of support for Zaptel.

When you reinstall do you delete ALL file in the /usr/lib/asterisk/modules dir.

As to the distro

when you say modified have you tried it vanilla kernel?

I have TDM400s running with customers on Mandrake 10 with no issues. as well as well as most other Distros and NO issues as you describe.

Please ignore the ring pattern and zonedata this is not to do with incoming calls.

Taken from the asterisk docs

Quote:

The loadzone parameter allows you to specify the tones that can be generated by that interface. A comma separated list of two letter country codes will load the tones for that country or region. The currently available list of tone zones defined in the zonedata.c file in /usr/src/zaptel .

Quote:

Its just failing to see the ring despite the ztmonitor showing that the audio tones are being seen. This again implies that the C code, due to definitions, is not seeing the pattern that it has been told to expect.

Could you post the whole output from a call and from lsmod lspci, /proc/interupts and what zttool and ztcfg -vv says about he card.

you could add distinctiveringdetect=yes to zapata.conf that will show if the ringing is being seen by * and will in debug display the pattern seen.

Also try moving the card to another slot if possible.

And finaly what did you do between it working and not working ?

Ian[/quote]

I have the same problem. It started about 2 months ago, which is when I got an 8M DSL connection instead of my previous 1M courtesy of ADSLMax or ADSL2 or 2+ or whatver BT has chosen. I wonder if this is it? Surely many other TDM400 users would see it too?

I do notice Geoff that your dmesg shows "NO BATTERY" is this a pointer?

Thanks, that about your DSL being upgraded sort of matches what I have seen. I think BT is changing something, or that the high pass/ low pass filter needs to be upgraded before the TDM works. I haven't yet tried changing the filter, but that is now my next port of call.

Has anyone succeeded in fixing this ?

I have an identical problem, worked my way through all the options and suggestions in this and a few other sites and still have no luck with incoming calls. I have changed filters (more than once) but that made no difference.


I can make outgoing calls just fine - this makes me think the actual module is OK.

The output with the verbose turned up is :

Connected to Asterisk 1.2.16 currently running on asterisk (pid = 8468)
asterisk*CLI> set debug 7
Core debug was 0 and is now 7
asterisk*CLI> set verbose 7
Verbosity was 0 and is now 7
== Starting post polarity CID detection on channel 4
-- Starting simple switch on 'Zap/4-1'
Aug 3 19:07:20 NOTICE[8488]: chan_zap.c:6161 ss_thread: Got event 17 (Polarity Reversal)...
Aug 3 19:07:22 WARNING[8488]: chan_zap.c:6201 ss_thread: CID timed out waiting for ring. Exiting simple switch
-- Hungup 'Zap/4-1'


Which is what I'm seeing - part of a ring, then engaged/network busy tone.

Module is set for UK OK etc.

This is a TDM400P, 1 FXO module (in position 4 if that matters)

Disconnect the card from the phone socket and I can make and receive calls OK and receive the Caller ID just fine.

Connect the card and incoming calls are engaged, but outgoing from Asterisk is fine.

Hi

We do need to see you zapata.conf, also need to know if you have a BT line with or without ADSL / DACS or a cable line before offering any advice

Ian

ianplain :

Hi We do need to see you zapata.conf, also need to know if you have a BT line with or without ADSL / DACS or a cable line before offering any advice Ian

No problem; this is a BT line with ADSL. Technically the bill is paid to Toucan but unless I'm mistaken, this is just a line provided by BT wholesale or some part of BT as my local exchange does not have LLU. The line filters have been changed [today], though I can change again if that's worthwhile - I have a few extra's still in their packing.

I'm using Ubuntu, 7.04. I upgraded the zaptel to 1.2.19 just in case that was the issue (sometimes postings suggested updating would help), but it did not help in my case as the issue remained exactly the same.

I've tried all sorts of different settings for zapata, but right now, the zapata.conf I'm using is this :


[channels]
language=en
context=from-pstn
signalling=fxs_ks

adsi = no
callerid = asreceived
callwaiting = no
cidsignalling = v23
cidstart = polarity
echocancel = yes
echotraining = yes
faxdetect = both
immediate = yes
rxgain = 5.0
txgain = 5.0
usecallerid = yes
usedistinctiveringdetection = yes
distinctiveringdetect = yes
group = 1
channel => 4

I've tried all sorts of different options, based on various suggestions, but I'm always left with the same basic problem - the start of a ring, then engaged when calling in. I'm not even sure all these options are valid, they've just been culled from various postings around the net suggesting they work for the TDM400 in the UK.

The modprobe shows in dmesg as :

[ 1952.780000] Freshmaker version: 73
[ 1952.780000] Freshmaker passed register test
[ 1953.276000] ProSLIC on module 0, product 0, version 0
[ 1953.276000] Module 0: Not installed
[ 1953.276000] ProSLIC on module 1, product 0, version 0
[ 1953.276000] Module 1: Not installed
[ 1953.276000] ProSLIC on module 2, product 0, version 0
[ 1953.276000] Module 2: Not installed
[ 1953.276000] ProSLIC on module 3, product 0, version 0
[ 1953.276000] VoiceDAA System: 04
[ 1953.476000] ISO-Cap is now up, line side: 03 rev 06
[ 1953.476000] Module 3: Installed -- AUTO FXO (UK mode)
[ 1953.504000] Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules)
[ 1953.508000] Registered tone zone 4 (United Kingdom)
[ 1953.564000] 413391 Polarity reversed (0 -> -1)
[ 1982.456000] Zaptel Transcoder support loaded
[ 1998.796000] 424699 Polarity reversed (-1 -> 1)
[ 1999.052000] 424763 Polarity reversed (1 -> -1)

In case it's relevant, zaptel.conf has :

# Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order


# Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1"
# channel 1, WCTDM, no module.
# channel 2, WCTDM, no module.
# channel 3, WCTDM, no module.
fxsks=4

# Global data

loadzone = uk
defaultzone = uk

I'm basically stuck and out of ideas, though I would be perfectly happy to be told I'd made some really dumb mistake and how to fix it as getting this working has become pretty damn important to me on a point of principle - I don't like the machine to get the better of me !

Jim

Try

Quote:

[channels] language=en context=from-pstn signalling=fxs_ks callerid = asreceived callwaiting = no cidsignalling = v23 cidstart = polarity echocancel = yes echotraining = yes immediate = no rxgain = 0.0 txgain = 0.0 usecallerid = yes group = 1 channel => 4

and see how that goes

Ian

Hi

I've just tried that and I'm still getting the same :

Quote:

root@asterisk:/etc/asterisk# /etc/init.d/asterisk stop Stopping Asterisk PBX: asterisk. root@asterisk:/etc/asterisk# /etc/init.d/asterisk start Starting Asterisk PBX: asterisk. root@asterisk:/etc/asterisk# root@asterisk:/etc/asterisk# asterisk -r Asterisk 1.2.16, Copyright (C) 1999 - 2006 Digium, Inc. and others. Created by Mark Spencer <markster@digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'show license' for details. ========================================================================= Connected to Asterisk 1.2.16 currently running on asterisk (pid = 9917) asterisk*CLI> set verbose 7 Verbosity was 0 and is now 7 asterisk*CLI> set debug 7 Core debug was 0 and is now 7 == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' Aug 4 11:41:57 NOTICE[9937]: chan_zap.c:6161 ss_thread: Got event 17 (Polarity Reversal)... Aug 4 11:42:00 WARNING[9937]: chan_zap.c:6201 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'Zap/4-1' == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' Aug 4 11:42:11 NOTICE[9941]: chan_zap.c:6161 ss_thread: Got event 17 (Polarity Reversal)... Aug 4 11:42:13 WARNING[9941]: chan_zap.c:6201 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'Zap/4-1' asterisk*CLI>

Is it possible the module is broken ? I'm able to make outgoing calls, so I was working on the basis that indicated it was most likely OK; perhaps I'm being too hopeful ?

Jim

Hi.

Ok Are you 110% sure you have callerID on the line ?

try changing polarity to ring or even diable callerID reception in zapata.conf

Ian

ianplain :

Hi. Ok Are you 110% sure you have callerID on the line ? try changing polarity to ring or even diable callerID reception in zapata.conf Ian

I'm sure caller ID is there - if I disconnect and use a phone with caller ID, it shows the incoming number OK.

Change to 'ring' and I get the same result - part ring and then line busy.

Change to usecallerid = no and it's still the same - part ring then line busy.



Any alternative ways I can interface analogue PSTN to asterisk ? This TDM400 seems to be a waste of time and money...