Hi,

You should have 2 records (as it is a call which did not established) :
1 - one as missed call, because of the missed call flag
2 - one as normal call (the db_flag+cdr_flag) in combination with the "failed_transaction_flag"

Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 26.03.2014 09:56, dpa wrote:

Hello!

 

In attachment you can find ordinary call (not successful)

1.1.1.1    – SIP UA

1.1.1.2    – Opensips

1.1.1.3    – SIP UA

 

 

In opensips.cfg

“modparam("acc", "early_media", 0)

modparam("acc", "report_cancels", 1)

modparam("acc", "detect_direction", 1)

modparam("acc", "db_flag", 15)

modparam("acc", "db_missed_flag", 16)

modparam("acc", "failed_transaction_flag", 17)

modparam("acc", "db_table_acc", "acc")

modparam("acc", "db_table_missed_calls", "acc")

modparam("acc", "cdr_flag", 22)”

 

and

 

before INVITE will be translated to callee SIP UA

“  setflag(15);

  setflag(16);

  setflag(17);

  setflag(22);”

 

I see that Opensips tried to insert several entries into acc.

 

The question is, why did Opensips try to insert into acc several entries due to one call? Is this because of db_flag and failed_transaction_flag?

 

Thank you for any help.

 

 



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to