How to troubleshoot CallerID issues on a FXO
The Digium® X100M FXO module and X400M FXO module are daughter cards that allow Digium® analog cards to terminate analog telephone lines (POTS).
This document is intended to be a brief description of toublehsooting steps that Digium’s customers can take to resolve Caller ID issues on their Asterisk Server.
Requirements
At least one analog line.
A regular analog phone with Caller ID display feature
Fully configured Asterisk server with the latest version of DAHDI and Asterisk
Troubleshooting Steps
A Caller ID issue could be caused by several factors. This section explores the possibility that the issue could be located at the telco or by noise on the lines.
Connect an analog phone to the demarcation point. In telephony, the demarcation point is the point at which the telephone company network ends and connects with the wiring at the customer premises.
Place a call — using another line or mobile phone — from the PSTN to the analog phone connected at the demarcation point and check if the phone displays Caller ID. If the Caller ID information is not being shown by the phone, please contact your telco and ask them how to enable this feature.
Otherwise, please disconnect the phone and plug it to the line that is directly connected or closest to your Asterisk server and repeat the test call.
If the analog phone shows the CallerID on every call, we could potentially be facing a misconfiguration of your Asterisk server. The following section will discuss how Caller ID detection works in Asterisk and the different options that you have avaialble.
In Asterisk, the CallerID detection is done by the chan_dahdi module. Normally its configuration file is located on /etc/asterisk/chan_dahdi.conf and there are three variables that control how the feature works:
usecallerid: Sets whether to use caller ID, “yes” or “no” are the only available options
cidsignalling: Determine type of caller ID signaling in use. The Caller ID signaling types supported by Asterisk are:
bell: bell202 as used in US (default)
v23: v23 as used in the UK
v23_jp: v23 as used in Japan
dtmf: DTMF as used in Denmark, Sweden and Netherlands
smdi: Use SMDI for caller ID. Requires SMDI to be enabled
cidstart: Determine signals the start of caller ID. The options supported by Asterisk are:
ring: A ring signals the start (default)
polarity: Polarity reversal signals the start
polarity_IN: Polarity reversal signals the start, DTMF dialtone detection in India
dtmf: DTMF Caller ID spill begins only with DTMF, at various times before the ring. This causes Asterisk to constantly listen for DTMF CallerID signals on the specified channels
If cidstart is configured to use dtmf, the energy level on the line may need to be tuned to properly identify the DTMF tones. This tuning is done with the dtmfcidlevel configuration option. The specified value is compared to the average over a packet of audio level of the absolute value of 16 bit signed linear samples. The default is set to 256, but this is completely arbitrary. It must be set high enough to prevent false detections, while low enough to ensure no dtmf spills are missed.
dtmfcidlevel=256
If you are unsure how to set up these variables. Please contact your telco for more information about the type of signal that the use on the Caller ID (cidsignalling)and when their switches send it (cidstart)
And example of the default configuration of Asterisk is:
file: chan_dahdi.conf
[trunkgroups]
…
[channels]
…
usecallerid=yes
cidsignalling=bell
cidstart=ring
…
Note: “…” means that other configuration unrelated to Caller ID could be there. Please take into consideration that chan_dahdi controls more aspects than the Caller ID. Please do not delete the other variables if you are not sure what those do.
P.S. We have seen at least once where a telco disabled Caller ID by attenuating the Caller ID signal. This disables it for Asterisk and DAHDI, but a plain old telephone service (POTS) handset with Caller ID display can still show Caller ID information in this scenario. If you’re sure you have the chan_dahdi.conf settings correct for your location, and you’re still not getting Caller ID, be sure to contact the provider and make sure they actually have Caller ID enabled on the line.
source link :- http://kb.digium.com/articles/Configuration/How-to-troubleshoot-CallerID-issues-on-a-FXO-or-QuadFXO-module