UK Caller ID on TDM410P *HELP*

Asterisk Asterisk Support
1

Hi,

I am running Asterisk 1.6.2.17.2 CLI only and a TDM410P.
I’m UK based to the damn caller id issue is prevailing.

I’m using DAHDI but I am having the exact problem mentioned in the following threads;
The digium thread explains the problem AND solution better than I can.

Sorry guys, I know this is a lot to read but I would really appreciate some guidance on the matter as it is basically a deal breaker for me. No caller id, no asterisk! The first thread is short and to the point.

http://forums.digium.com/viewtopic.php?t=8477
http://fonality.com/trixbox/forums/trixbox-forums/help/uk-caller-id-issues-dahdi

/etc/asterisk/chan_dahdi.conf

; DAHDI Telephony Configuration file

; GENERAL -->

[trunkgroups]

[channels]
language=en
context=inbound
usecallerid=yes
cidsignalling=v23
cidstart=polarity
hidecallerid=no
waitfordialtone=yes
callwaiting=no
usecallingpres=yes
sendcalleridafter = 2
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
callerid = asreceived
useincomingcalleridondahditransfer = yes
answeronpolarityswitch=yes
hanguponpolarityswitch=yes
busydetect=yes
busycount=3
progzone=uk
tonezone=4

;TRUNKS -->

;FXO1
context = pstn-inbound
group = 1                                                                             
signalling = fxs_ks
channel = 1

;FXO2
context = gsm-outbound
group = 2
signalling = fxs_ks
channel = 2

;TEMPLATES -->

[fxs-phones](!)
usecallerid = yes
hidecallerid = no
threewaycalling = yes
transfer = yes
echocancel = yes
echotraining = yes
context = local
signalling = fxo_ks

;PHONES -->

[FXS4](fxs-phones)
callerid = "Ding-Dong-The-PBX-Is-Dead" <(i.e.9999999999>
dahdichan = 4

/etc/dahdi/system.conf

# Dahdi Configuration File
# Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER)

fxsks=1
echocanceller=mg2,1
fxsks=2
echocanceller=mg2,2
# channel 3, WCTDM/0/2, no module.
fxoks=4
echocanceller=mg2,4

# Global data

loadzone        = uk
defaultzone     = uk

I’ve simplified the dialplan to try and diagnose the problem, so just two phones that ring when a call comes in from the pstn/fxo- channel 1.

/etc/asterisk/extensions.conf

; extensions.conf - the Asterisk dial plan

; GENERAL -->

[general]
static=yes
writeprotect=no
autofallthrough=yes
clearglobalvars=no
;
;extenpatternmatchnew=no
;priorityjumping=yes
;userscontext=default


; GLOBALS -->

[globals]
ignorepat => 9

; DIALPLAN -->

[default]

[local]
exten => 100,1,Dial(DAHDI/4)

exten => 200,1,Dial(SIP/TEST-SIP)

exten => 1234,1,VoiceMailMain()

[pstn-inbound]
exten => s,1,Dial(DAHDI/4&SIP/TEST-SIP,10)
        same => n,Hangup()

[incoming]
exten => s,1,Dial(DAHDI/4&SIP/TEST-SIP,10)
        same => n,Hangup()

and here is the debug output from the wctdm24xxp module when an incoming call is received.
Notice that Asterisk is answering the call before the polarity reversal. The polarity event should come first!

/var/log/messages

Mar 20 15:47:01 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on 1/1!
Mar 20 15:47:02 localhost kernel: wctdm24xxp 0000:00:0a.0: 348398 Polarity reversed (-1 -> 1)
Mar 20 15:47:02 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on 1/1!
Mar 20 15:47:02 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on 1/1!
Mar 20 15:47:02 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on 1/1!
Mar 20 15:47:04 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on 1/1!
Mar 20 15:47:05 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on 1/1!
Mar 20 15:47:05 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on 1/1!
Mar 20 15:47:05 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on 1/1!
Mar 20 15:47:07 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on 1/1!
Mar 20 15:47:08 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on 1/1!
Mar 20 15:47:08 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on 1/1!
Mar 20 15:47:08 localhost kernel: wctdm24xxp 0000:00:0a.0: 354983 Polarity reversed (1 -> -1)
Mar 20 15:47:08 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on 1/1!

Thanks
Danny

2

Deleted

3

The reversal should come before the first ring. That’s the whole point of the BT system.

4

You can also give the Digium Support department a ring/e-mail directly:

digium.com/support

Cheers.

5

Yeah I thought that’s what I said? I must have explained it wrong.

But how on earth do I get the polarity reversal first?

The patch that the other guys have used tells asterisk to ignore all rings before the id is received fully.
I have no idea because the old patch was for zap on asterisk 1.4

6

The reversals are controlled by the network.

7

I’m having exactly the same trouble :frowning:
Am running AsteriskNOW 1.7.1 with freepbx updated to 2.8final and asterisk 1.6.2.17.2
Have spent ages googling to try and find a newer version of that 1.4 patch, but thus far no luck.

8

[quote=“Tunes0710”]I’m having exactly the same trouble :frowning:
Am running AsteriskNOW 1.7.1 with freepbx updated to 2.8final and asterisk 1.6.2.17.2
Have spent ages googling to try and find a newer version of that 1.4 patch, but thus far no luck.[/quote]

Hi,

I finally solved my problem, but it got to the stage of me reporting a bug in the tracker.
In fact it was the only time I actually got any help on the matter.

IRC was useless, I posted in 5 forums and other than the replies here I got nothing.
I still think there is a bug but as my problem has been resolved by upgrading to the latest asterisk I think you’re going to be hard pressed to fix it in your current setup.

Furthermore, now it’s working properly the polarity reversal is now first in the message log and NOT second.
I installed asterisk 1.8.3.2 with dahdi 2.4 on centos 5.5 final.

Oh other than that, here is the bug tracker page, there might be some useful info there for you.
Good luck.

https://issues.asterisk.org/view.php?id=19006

Danny