HELP!! Caller ID “unknown” for all inbound call

Home » Asterisk Users » HELP!! Caller ID “unknown” for all inbound call
Asterisk Users 6 Comments

This is a very strange problem (at least for me). I just realized that
started from April 20th 2012 every inbound call is from “unknown”.
Prior that, asterisk succesfully displayed the caller caller’s ID for SOME
of the calls (30-50% success rate). I am using PBX | monitoring menu to see
this report.

As far as I remember, I dont modify any settings that related to caller ID,
but few days ago (I dont remember the exact date), I modify the rxgain and
txgain value in chan_dahdi.conf.
The inbound caller ID doesn’t display on the log and on the phone.

I’m running asterisk 1.8.7.0
FreePBX 2.8.1
FXO card using Digium AEX800B

The caller ID is display well on the phone If I connect the phone directly
without connecting to asterisk (just for testing purpose)

This is my chan_dahdi.conf

[trunkgroups]

[channels]
context=from-pstn
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=8.0
txgain=8.0
callgroup=1
pickupgroup=1

;Uncomment these lines if you have problems with the disconection of your
analog lines
;busydetect=yes
;busycount=3

immediate=no

#include dahdi-channels.conf
#include chan_dahdi_additional.conf
chan_dahdi.conf (END)

This is my dahdi-channels.conf
; Autogenerated by /usr/sbin/dahdi_genconf on Fri Mar 30 22:32:16 2012
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is
intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global
settings
;

; Span 1: WCTDM/0 “Wildcard AEX800 Board 1” (MASTER)
;;; line=”1 WCTDM/0/0 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

;;; line=”2 WCTDM/0/1 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
callerid=
group=
context=default

;;; line=”3 WCTDM/0/2 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
callerid=
group=
context=default

;;; line=”4 WCTDM/0/3 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 4
callerid=
group=
context=default

;;; line=”5 WCTDM/0/4 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 5
callerid=
group=
context=default

;;; line=”6 WCTDM/0/5 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 6
callerid=
group=
context=default

Any help would be very appeciated.

Thanks and best regards,
Anam.

6 thoughts on - HELP!! Caller ID “unknown” for all inbound call

  • I see extra/additional fields in the pasted configuration
    dahdi-channels.conf, try removing these. Then do a “module reload
    chan_dahdi”

    Regards,
    Sammy

    On Sun, Apr 22, 2012 at 12:49 PM, Satria Anamarta
    wrote:

  • Thanks Sammy for looking at my post 🙂

    Removing those 2 lines for all the channel still doesn’t solve the problem 🙁

    Any other ways I should try?

    BR,
    Anam

  • do a complete reload(dahdi/asterisk/amportal) and then check.

    On Mon, Apr 23, 2012 at 12:18 PM, Satria Anamarta
    wrote:

  • OK. Run `diff` on the old (you did save a copy somewhere, didn’t you?) and
    new versions of chan_dahdi.conf, and see if you changed anything else.

  • That looks perfectly sane (it’s quite normal to get an extra blank line added
    on the end with certain editors).

    Yes indeed. So the next question must be: Has anything else changed? Run
    $ ls – altr /etc/asterisk/
    which will list the files in the folder /etc/asterisk, most recently modified at
    the bottom. Has anything else changed?

    Do the same thing also for /etc/dahdi:
    $ ls -altr /etc/dahdi/

    They shouldn’t. Anyway, changing them back didn’t fix it, so that is unlikely
    to have much to do with it. It’s probably some other setting that was
    accidentally changed by some configuration-generating utility.

    Watch out especially for anything “international”. Different countries (and
    sometimes, even different phone companies within the same country) use
    different methods of sending caller ID information. For instance, BT uses a
    modified version of the Bellcore standard but with UK modem tones, and the
    number is sent between the polarity reversal and first burst of ringing; some
    UK cable companies use DTMF during ringing.