Millions of callerid.c: Unknown IE 0 errors in log

Asterisk Asterisk Support
1

Hi,

We’re having a fatal problem with Asterisk 1.2.13 running with a Digium TDM card. Basically, at random the Asterisk server will stop functioning and the log file will fill up with thousands of “callerid.c: Unknown IE 0” errors per second. This has actually filled the harddrive overnight on a few occasions, causing the actual system to all but stop functioning.

We’re using a Digium TDM card with 4 fxo modules connected to RJ12 sockets on a VoIP gateway (unfortunately they force you to use the RJ12 sockets for voice traffic, they disallow the use of SIP).

I’m going to disable callerid for a week and see if that fixes the problem. Does anyone know why this would happen, or what I could do to fix it?

Thanks

2

Ok, further research reveals that it’s definitely a callerid issue. The exact problem is that Asterisk is receiving an invalid “Information Element” on the line, and for some reason this causes it to go haywire, when it should really just make the callerid “Unknown” or “Private Number”.

Is there a way log a bug report to the Asterisk developers?

3

bugs.digium.com/

where are you, what format of CID is the box giving out, what do you have zapata.conf configured for ?

4

I’m in Australia. I have no idea what format of CID the box is giving out, but I can find out. I didn’t realise you could configure Asterisk to parse different CID formats.

Anyway, zapata.conf is as follows:

;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-pstn
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

usecallerid=no
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
;faxdetect=incoming
;faxdetect=outgoing
faxdetect=no

;Include genzaptelconf configs
#include zapata-auto.conf

And zapata-auto.conf is as follows

; Autogenerated by /usr/local/sbin/genzaptelconf – do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the global settings
;
callerid=asreceived

; Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1"
signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 1
context=from-pstn
group=0
channel => 1

signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 2
context=from-pstn
group=0
channel => 2

signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 3
context=from-pstn
group=0
channel => 3

signalling=fxs_ks
; Note: this is a trunk. Create a ZAP trunk in AMP for Channel 4
context=from-pstn
group=0
channel => 4

; Span 2: ZTDUMMY/1 “ZTDUMMY/1 1”

5

if you have the Asterisk source (and you should have, even with that distro !!) then have a look at /usr/src/asterisk/configs/zapata.conf.sample (may be located elsewhere)

cidsignalling= and cidstart= will probably be where to start. being in Aus, you might find you’re using v23 like the UK maybe ??

i would normally say look at the wiki, but that page seems to be lagging behind a bit.

6

Cool, well I’ll have a play with cidsignalling and cidstart. Hopefully the voip gateway uses a supported signalling method!

Thanks for your help baconbuttie :smiley:

7

IE is usually referred to in a PRI. Make sure you are also loading your module with opermode=AUSTRALIA

ex.
modprobe wctdm opermode=AUSTRALIA

You will want to make sure this is in boot script also.