just to double check, you are also setting this two flags then in processing the INVITE, right?
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com
> -----Original Message-----
> From: Jon Bonilla (Manwe) via sr-users
sr-users@lists.kamailio.org
> Sent: Donnerstag, 6. Juni 2024 19:07
> To: sr-users@lists.kamailio.org
> Cc: Jon Bonilla (Manwe)
manwe@sipdoc.net
> Subject: [SR-Users] Re: Filtering codes in db acc
>
> El Thu, 6 Jun 2024 15:40:19 +0200
> "Jon Bonilla (Manwe) via sr-users"
sr-users@lists.kamailio.org escribió:
>
> >
> > DEBUG: acc [acc_logic.c:721]: tmcb_func(): acc callback called for
> > t(0x7f7cec807480) event type 512, reply code 407
> >
> > DEBUG: acc [acc_logic.c:443]: should_acc_reply(): probing acc state - code:
> > 407 flags: 0x220
> >
> > DEBUG: acc [acc_logic.c:449]: should_acc_reply(): failed acc is off
> >
>
> Checking the acc_logic.c I see that filter is not checked because this:
>
> if(!is_failed_acc_on(req)) {
>
> and
>
> #define is_failed_acc_on(_rq) is_acc_flag_set(_rq, failed_transaction_flag)
>
> So seems like filter needs modparam failed_transaction_flag to work. (this is
> me trying to understand C code. Forgive me if I mess it up)
>
> So I added just to check
>
> modparam("acc", "db_missed_flag", FLT_ACC_MISS) modparam("acc",
> "failed_transaction_flag", FLT_ACC_MISS)
>
> that way when I set the flag I also set for that modparam. But I get the same
> result and the same log
>
>
> acc [acc_logic.c:721]: tmcb_func(): acc callback called for t(0x7fcbd3e47920)
> event type 512, reply code 407
>
> acc [acc_logic.c:443]: should_acc_reply(): probing acc state - code: 407 flags:
> 0x220
>
> acc [acc_logic.c:449]: should_acc_reply(): failed acc is off
>
>
>
> Any ideas over there?
>
>
> thanks
>
>
>
> --
> PekePBX, the multitenant PBX solution
>
https://pekepbx.com