Hi, Dan!
You are right, this seems to be a bug. The second event shouldn't be
E_ACC_CDR, but E_ACC_EVENT. I fixed this in the git code, thanks for
noticing it.
Setting the CDR_FLAG on BYE messages means that you explicitly want to
account that message. That's why you have two events: a CDR
Hey Razvan,
I have hit the bug out of missing knowledge about how to gerate CDRs :).
For me there is no issue with BYEs since I only need INVITEs to generate
accounting.
Anyway, happy to contribute as bug finder ;).
Thanks again for your support!
DanB
Razvan,
Sorry just noticed your question on pseudovariable in BYE. Yes, you are
right, I did not set it in BYE but only in INVITE. In that case I accept
that there is no bug there.
DanB
___
Users mailing list
Users@lists.opensips.org
Hey Razvan,
Thanks for getting so fast back to me.
Regarding your question, when activating CDR for INVITE and BYE, I am
getting two E_ACC_CDR events. What is also weird is that the avp which I
set in INVITE is not recovered in BYE (see cgr_reqtype in the sample
bellow).
Here are the
Hey Guys,
As part of integrating Opensips with CGRateS, we were wondering whether
we are following the right path in terms of generating/processing CDRs
for OpenSIPS.
Here is our approach:
1. Load event_datagram
2. Load dialog
3. Configure acc params as:
modparam(acc, cdr_flag, CDR_FLAG)
Hi, Dan!
Yes, you are on the right path. You do have to specify the evi_flag,
otherwise the acc module does not know what kind of accounting to do (DB
based, log based, aaa based, events based). If you don't specify the
cdr_flag, then you will get an old-style accounting - for a single call
