rhinoequipment.com // View topic - Analog-Intermittant Caller ID Display

rhinoequipment.com Forum Index :: FAQ :: Search :: Memberlist :: Usergroups

Analog-Intermittant Caller ID Display

This forum is locked: you cannot post, reply to, or edit topics.

This topic is locked: you cannot edit posts or make replies.

rhinoequipment.com Forum Index // Rhino OST PCI Cards

View previous topic :: View next topic

jfinstrom
Site Admin

Joined: 07 Mar 2007
Posts: 25

Posted: Wed Apr 25, 2007 8:20 am Post subject: Analog-Intermittant Caller ID Display

Some users of analog lines may experience intermittent Caller ID issues. The makers of Asterisk have done well to try and eliminate these issues but they still exist. In testing with the default entries in zapata.conf caller ID missed on about 2 in 10 calls. We added the following entries to our zapata.conf and asterisk missed about 1 in 20.

Code:

usecallerid=yes
callerid=asreceived
cidsignalling=bell
cidstart=ring

From our research in this matter we are told 100% success is not likely to occur but we will continue to research this to get the rate of success as high as possible.

jfinstrom
Site Admin

Joined: 07 Mar 2007
Posts: 25

Posted: Thu Apr 26, 2007 3:27 pm Post subject:

Update. Some users have noticed improvements by editing channels/chan_zap.c in asterisk

In this file there is a line that looks like

Code:

.cid_rxgain = +5.0,

I am not sure if there was an issue with other cards that use Asterisk but ours do not require this boost so you may change the code to look like:

Code:

.cid_rxgain = 0.0,

Then from the asterisk source folder

Code:

make && make install

jfinstrom
Site Admin

Joined: 07 Mar 2007
Posts: 25

Posted: Tue May 15, 2007 3:04 pm Post subject:

So I have been scraping page after page of code to discover why Asterisk isn't playing nice with caller id.. I have gone through several work around with varied levels of success. The latest work around is giving me 100% success in a lab environment so I would like to see if it works in application. The issue seems to be our cards are too fast for asterisk. By default asterisk waits until ring 1 to get caller id data. It seems that by the time ring 1 hits the caller id data is hit and miss. So I recompiled asterisk and said listen at ring 0 and it seems to work.

The work around:

It was pointed out to me by a community member that their is no need to use dynamite to catch fish.

You may add the following to your zapata.conf

Code:

sendcalleridafter=0

Below is the dynamite no need to do both.....

-------------------------cut------------------------------
Download the appropriate asterisk source from digiums ftp.

Untar the file.

Edit the callerid.h (asterisk-x.x.x/include/asterisk/callerid.h)

scroll down about line 45 you will see

Code:

#define CID_START_RING 1

Change that to:

Code:

#define CID_START_RING 0

Then from the asterisk source folder make && make install

Next restart asterisk. If it fails to come up you may need to add the following to /etc/asterisk/modules.conf

Code:

noload => app_speech_utils.so

please forward your results to jfinstrom [at] rhinoequipment.com

Thanks

	rhinoequipment.com Forum Index // Rhino OST PCI Cards	All times are GMT - 7 Hours
Page 1 of 1

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum