Hi!
Again, the first two INVITEs correspond to each leg (related to the
multi-leg support). If you remove the multi-leg support, you should see
only two INVITEs: the one in missed_calls and the first one in acc.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 12/03/2013 01:01 PM, Alexander Mustafin wrote:
I’m puzzled :)
I know about modparam("acc", "db_table_missed_calls", "acc»), but this
does not change the behavior of the string generation.
1) I do a call to GW1 (do_routing)
2) GW1 return 503 Error
3) I catch an error and do use_next_gw() - call send to GW2
4)GW2 is accept the call
5)Call and dialog successfully ended
The ACC module generates next rows:
1) INVITE with sip_code=200 (columns are filled by avp) to GW2
2) INVITE with sip_code=200 (almost all columns are empty) to GW1
3) BYE with sip_code=200 to GW2
4) INVITE with sip_code=503 (columns are filled by avp) in missed_calls
to GW1.
I’m confused only this raw, with empty columns AND it’s sip_code and
think that incorrect behavior.
Best regards,
Alexander Mustafin
[email protected] <mailto:[email protected]>
03 дек. 2013 г., в 14:24, Răzvan Crainea <[email protected]
<mailto:[email protected]>> написал(а):
Hi, Alexander!
Indeed, the failed legs will be stored in the missed_call table. A
workaround would be to change the table by setting the following
parameter:
modparam("acc", "db_table_missed_calls", "acc")
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com <http://www.opensips-solutions.com/>
On 12/03/2013 07:30 AM, Alexander Mustafin wrote:
OK, Răzvan, maybe my avp’s are null at this moment - much more
important, that really sip code not presented in this row. Completely
filled row for this leg creates in missed_call table. I.e. 2 rows
creates for one leg with error - one in acc table and one in
missed_calls.
Best regards,
Alexander Mustafin
[email protected]
<mailto:[email protected]><mailto:[email protected]>
02 дек. 2013 г., в 15:07, Răzvan Crainea <[email protected]
<mailto:[email protected]>
<mailto:[email protected]>> написал(а):
Hi, Alexander!
Are you sure you are populating all the multi_leg_info AVPs for each
leg? In your case, you have two legs, therefore you should populate
each variable two times - once for the initial leg and second for the
redirect.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
<http://www.opensips-solutions.com/><http://www.opensips-solutions.com/>
On 11/30/2013 05:07 AM, Alexander Mustafin wrote:
Hi, Răzvan.
Thank you for this hint!
I set multi-leg acc support now, and it’s almost works )))
1) If first GW drop my call and return error - ACC generate row in
table
for this leg, BUT sip_code is 200 (not error code)
2) I set modparam("acc", "multi_leg_info»,…) with avp I would to store
in database, but almost all columns are empty for unsuccessfull leg -
for other legs they are present.
Best regards,
Alexander Mustafin
[email protected] <mailto:[email protected]>
<mailto:[email protected]><mailto:[email protected]>
29 нояб. 2013 г., в 14:44, Răzvan Crainea <[email protected]
<mailto:[email protected]>
<mailto:[email protected]>
<mailto:[email protected]>> написал(а):
Hi, Alexander!
If you want to have multiple rows for each leg, then you should use
multi-leg acc support[1]. Note that you should not use the CDR flag,
since you are doing old two-steps accounting.
[1]
http://www.opensips.org/html/docs/modules/1.8.x/acc#multi-call-legs
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 11/28/2013 02:36 PM, Alexander Mustafin wrote:
If first gateway in drouting return error - I need a CDR with sip
code
of error. Then, if next gw is setup the call - I need a CDR,
after BYE
message.
First attempt - generate one row INVITE in the table (with error
code),
and second attempt generate two rows - INVITE and BYE
I believe that it should work like that!
Best regards,
Alexander Mustafin
[email protected] <mailto:[email protected]>
28 нояб. 2013 г., в 15:42, Alexander Mustafin
<[email protected] <mailto:[email protected]>>
написал(а):
Hi, Razvan!
I’m tried set ACC_FAILED in places, where call may be failed. In
request route too.
Best regards,
Alexander Mustafin
[email protected] <mailto:[email protected]>
28 нояб. 2013 г., в 15:35, Răzvan Crainea <[email protected]
<mailto:[email protected]>> написал(а):
Hi, Alexander!
Have you tried setting the ACC_FAILED flag in the request route?
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
<http://www.opensips-solutions.com/>
On 11/28/2013 10:35 AM, Alexander Mustafin wrote:
Hello!
I need to store all CDRs for all calls, but some failed calls are
not to
handled by ACC.
modparam("acc", "failed_transaction_flag", "ACC_FAILED»)
failure_route[MISSED_CALL] {
if (t_check_status("[4|5][0-9][0-9]")) {
setflag(ACC_FAILED);
}
}
But call which rejected with 503 (example) error is missed in acc
table.
Best regards,
Alexander Mustafin
[email protected]
<mailto:[email protected]><mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected] <mailto:[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
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
<mailto:[email protected]><mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
<mailto:[email protected]><mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected] <mailto:[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
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
