[asterisk-users] UK POTS - Is there a better card than TDM400P available ?

[Matt Brown]

>> As I can see from that report, a modified version of that patch was
>> applied to 1.4:
>>
>> http://bugs.digium.com/9264#80824
>>
>> It was reverted right before the release of 1.4.8, as it required  
>> more
>> testing, and re-applied immediately after it. Hence 1.4.9[.2]  
>> includes it.
>
>
> I should have read the bug report
>
> http://bugs.digium.com/9264#8082
>
> more carefully.
>
> I have now added the line:
>
> fwringdetect=1
>
> to the /etc/asterisk/zapata.conf so the patched part of the code is  
> then utilized. This is appears to be working and hopefully will make  
> it into 1.4.10.
>
> Now to investigate the distinctive ring part :-)

Hmm scratch that !

(apologies for any line wraps)

It would appear its still broken .. and introduces a new bug !

[Apr  8 13:42:54] NOTICE[5846]: chan_zap.c:6234 ss_thread: CallerID  
number: 07875-xxxxxx, name: (null), flags=4
     -- Executing [s at incoming:1] Verbose("Zap/4-1", "Incoming call  
from BT line CallerID="" <07875xxxxxx>") in new stack
Incoming call from BT line CallerID="" <07875xxxxxx>
     -- Executing [s at incoming:2] GotoIf("Zap/4-1", "0?3:8") in new stack
     -- Goto (incoming,s,8)
     -- Executing [s at incoming:8] Set("Zap/4-1",  
"CALLERID(all)=Incoming Call: <07875xxxxxx>") in new stack
     -- Executing [s at incoming:9] MixMonitor("Zap/4-1",  
"1207658573.0.gsm") in new stack
     -- Executing [s at incoming:10] Dial("Zap/4-1", "ZAP/1r1||tr") in  
new stack
     -- Called 1r1
   == Begin MixMonitor Recording Zap/4-1
     -- Zap/1-1 is ringing
     -- Zap/1-1 is ringing
     -- Hungup 'Zap/1-1'
   == Spawn extension (incoming, s, 10) exited non-zero on 'Zap/4-1'
     -- Hungup 'Zap/4-1'
   == End MixMonitor Recording Zap/4-1

Second try ....

   == Starting post polarity CID detection on channel 4
     -- Starting simple switch on 'Zap/4-1'
[Apr  8 13:43:09] NOTICE[5848]: chan_zap.c:6191 ss_thread: Got event 2  
(Ring/Answered)...
[Apr  8 13:43:11] WARNING[5848]: chan_zap.c:6254 ss_thread: CID timed  
out waiting for ring. Exiting simple switch
     -- Hungup 'Zap/4-1'

Third try ... (bug appears)

   == Starting post polarity CID detection on channel 4
     -- Starting simple switch on 'Zap/4-1'
[Apr  8 13:43:12] NOTICE[5849]: chan_zap.c:6191 ss_thread: Got event 4  
(Alarm)...
[Apr  8 13:43:12] NOTICE[5849]: chan_zap.c:4185 zt_handle_event: Alarm  
cleared on channel 4
[Apr  8 13:43:14] WARNING[5849]: chan_zap.c:6254 ss_thread: CID timed  
out waiting for ring. Exiting simple switch
     -- Hungup 'Zap/4-1'

Some calls do show CID (as above) others do not - mainly not .. then  
as above if I call a second or third time the following happens ...  
(never on first call !)

The call is answered and I get a high pitch tone for around 5 secs  
then the line goes quiet, However the Zap channel then remains open  
for upto 1min or more then resets....

The kernel/syslog shows this BATTERY NO BATTERY issue ....

Apr  8 13:42:59 max kernel: [17434415.320000] NO RING on 1/4!
Apr  8 13:42:59 max kernel: [17434415.580000] Setting FXS hook state  
to 0 (00)
Apr  8 13:43:09 max kernel: [17434425.220000] RING on 1/4!
Apr  8 13:43:09 max kernel: [17434425.220000] 63639009 Polarity  
reversed (-1 -> 1)
Apr  8 13:43:09 max kernel: [17434425.476000] NO RING on 1/4!
Apr  8 13:43:10 max kernel: [17434426.964000] RING on 1/4!
Apr  8 13:43:12 max kernel: [17434428.148000] NO RING on 1/4!
Apr  8 13:43:12 max kernel: [17434428.388000] 63639801 Polarity  
reversed (1 -> -1)
Apr  8 13:43:12 max kernel: [17434428.804000] NO BATTERY on 1/4!
Apr  8 13:43:12 max kernel: [17434428.900000] BATTERY on 1/4 (-)!

This is new, and have not seen this in 1.4.5.1 + patch ... I think I  
will have to stay on this version until I can find out what is going  
on ...

Is is possible to get very verbose granular debug info out of Zaptel ?  
I have debug=1 and tried debug=9 in the modprobe section ..... but  
this is the most  I get from Zaptel.

Matt