Avoid rinnging time to be calculated by CDR

Status
Not open for further replies.

ahmed_gaffar

Joined
Jan 10, 2011
Messages
44
Reaction score
0
Hallo all of you Moderators, as visitors,

Well i am using Elastix 2.0.0 for more than 9 months now, and really a lot of thanks for every body helped with this think "it is more than great" i learned also how to connect a FXO Gateway with 8 Ports, integrating A2Billing 1.3 to the System ..every thing working fine. Only one think make me a headic that's why I'll be more than grateful if i got any tip :
"Where can i change in cdr.conf or any place else to avoid ringing time in the CDR, i want to calculate for my customers only the time they talk the ringing time should = 0 until the Cal-lee answer!!" so friends any tip will be appreciated
"Any one who need to know how to connect A2Billing with Elastix please send mail to walk through together"
 
If you are having that issues is because you are using analog trunks. To avoid this problem, get the reverse polarity service with your analog provider, and then reconfigure chan_dahdi.conf to make it work.
 
First thanx for the replay, i thought the same, but this issue is also there when there is internal calls (extension1 -> extension2) this means it is not because of the analoge gateway. i am sure there is something to configure in the cdr.conf or in the astrisk.conf to let it only calculate the talk time.
 
Re:Avoid ringing time to be calculated by CDR

Hallo jgutierrez,

Well once again thanks for your answer, can you tell me which configurations should be changed to let the Ex1--> Ex2 call also be callculated after Ex2 answer the call. I have in my elastix server like this "where ever the call come from -internal or external" the cdr as the calculater write it as Answered, and put wrong time for it. Please help it is important, we stop the whol server to solve this problem first, any Tip or Idea will bring us forwoard. Any moderator will jump for help??!!!
 
Re:Avoid ringing time to be calculated by CDR

Dear jgutierrez,

After alot of test i am sure now it is about this polarity service, so where can i change to configure my files to be sutabile? my chan_dahdi.conf look like this:

usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=0.0
txgain=0.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


any Advice??
 
3 edits to my answer and I reread your post so I don't think my answer was what you needed. Sorry.
:silly:
Michael
 
So hello all of you,

Today i got a littel bit more to solve my problem, well i made the polarity detect service in the FXO Gateway (EIA2008QA from ALLYWLL) and added lines in the chan_dahdi.conf
answeronpalarityswitch=yes
so now i have another scenario, the Gateway pass the call and the callee answer and exactly after 55sec. i got a meassage from my Elastix that there is no body answer ... and offcourse the CDR calculate nothing through this 55sec :( should i give up -:) ...so please help
 
Status
Not open for further replies.

Forum statistics

Threads
111,859
Messages
589,434
Members
164,699
Latest member
CLTedu