Dear Friends,
In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try?
I tryied to add in failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
but I'm getting ACC only the last try.
Thanks Alex
On Friday 22 January 2010, alex pappas wrote:
In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try?
I tryied to add in failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
but I'm getting ACC only the last try.
Hi alex,
you could use AVPs to store certain attributes of the previous attempts, like target, result code or similar and then just log this in the normal (extra) accounting. This is the way we use at the moment. I think Daniel also did some acc extensions in the last year, not sure if they also could help you in this regards.
Cheers,
Henning
Hi Henning,
Since I cannot use directly acc in failure Route then I will try to add the AVPs you mentioned directly in mysql with SQLOPS.
Thank you Alex
On Fri, Jan 22, 2010 at 2:55 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Friday 22 January 2010, alex pappas wrote:
In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass.
If
the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is
there
any way that I can simply setflag(1) for accounting and I can have ACC
for
every try?
I tryied to add in failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
but I'm getting ACC only the last try.
Hi alex,
you could use AVPs to store certain attributes of the previous attempts, like target, result code or similar and then just log this in the normal (extra) accounting. This is the way we use at the moment. I think Daniel also did some acc extensions in the last year, not sure if they also could help you in this regards.
Cheers,
Henning
On Friday 22 January 2010, alex pappas wrote:
Hi Henning,
Since I cannot use directly acc in failure Route then I will try to add the AVPs you mentioned directly in mysql with SQLOPS.
Hi alex,
ok, this is another option. But i was referring to do something like this:
modparam("acc", "db_extra", "$avp(failure_info)")
failure_route[1]
$avp(failure-info)=$avp(failure_info) + "gateway.." + "result.."
failure_route[2]
$avp(failure-info)=$avp(failure_info) + "gateway.." + "result.." ..
Cheers,
Henning
Hi Henning,
This could be a solution also but it would be a little more difficult in seaching infiormations about those calls against the DB,
Cheers Alex
On Fri, Jan 22, 2010 at 4:04 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Friday 22 January 2010, alex pappas wrote:
Hi Henning,
Since I cannot use directly acc in failure Route then I will try to add
the
AVPs you mentioned directly in mysql with SQLOPS.
Hi alex,
ok, this is another option. But i was referring to do something like this:
modparam("acc", "db_extra", "$avp(failure_info)")
failure_route[1]
$avp(failure-info)=$avp(failure_info) + "gateway.." + "result.."
failure_route[2]
$avp(failure-info)=$avp(failure_info) + "gateway.." + "result.." ..
Cheers,
Henning
On Friday 22 January 2010, alex pappas wrote:
Hi Henning,
This could be a solution also but it would be a little more difficult in seaching infiormations about those calls against the DB,
Hi alex,
sure, its more a way to store certain smaller parts of information to get a trace like output.
Cheers,
Henning
Hello,
On 1/22/10 1:08 PM, alex pappas wrote:
Dear Friends,
In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try?
I tryied to add in failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
but I'm getting ACC only the last try.
last failed try? Or what you mean by "the last try"? IIRC, failed transaction flag should be set for each leg if you want all failures.
Cheers, Daniel
Hi Daniel,
I use in the Failure Route the dispatcher to try in serial mode some gateways against a call. If I set in the failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
then I get in the syslog the acc of the last gateway that Dispatcher tried to terminate the call.
For the second you are asking(failure flag) I have: modparam("acc", "failed_transaction_flag", 6)
And setflag(6) int request route and in failure route but I don't get ACC for every try from failure route
I'm I doing something wrong in the configuration script ?
Thank you Alex
On Fri, Jan 22, 2010 at 3:33 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
Hello,
On 1/22/10 1:08 PM, alex pappas wrote:
Dear Friends,
In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try?
I tryied to add in failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
but I'm getting ACC only the last try.
last failed try? Or what you mean by "the last try"? IIRC, failed
transaction flag should be set for each leg if you want all failures.
Cheers, Daniel
-- Daniel-Constantin Mierla
Hi Daniel,
We make a call and the call tries from the Failure Route 5 times new gateway (with dispatcher) but WITHOUT success in termination. In every try we get back 503 Congestion. In this case how many CDRs we should see in our LOG.
We have the modparam("acc", "failed_transaction_flag", 6) and we setflag(6) for every INVITE.
Thank you Alex
On Fri, Jan 22, 2010 at 3:33 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
Hello,
On 1/22/10 1:08 PM, alex pappas wrote:
Dear Friends,
In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try?
I tryied to add in failure route :
setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails
but I'm getting ACC only the last try.
last failed try? Or what you mean by "the last try"? IIRC, failed
transaction flag should be set for each leg if you want all failures.
Cheers, Daniel
-- Daniel-Constantin Mierla
Hi Alex,
On 1/25/10 11:03 AM, alex pappas wrote:
Hi Daniel,
We make a call and the call tries from the Failure Route 5 times new gateway (with dispatcher) but WITHOUT success in termination. In every try we get back 503 Congestion. In this case how many CDRs we should see in our LOG.
We have the modparam("acc", "failed_transaction_flag", 6) and we setflag(6) for every INVITE.
iirc, at some point was an option to get all failed legs accounted. I don't remember using it so I have to check the sources (you are on 1.5.x, right?).
For next version I plan to make acc functions available on rest of the routes, should be few updates to take sip method from cseq header and ignore r-uri if it is a reply processed, in failure route should work by default, I see no reasons now what could be the problem.
Cheers, Daniel
On Fri, Jan 22, 2010 at 3:33 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello, On 1/22/10 1:08 PM, alex pappas wrote: Dear Friends, In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try? I tryied to add in failure route : setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails but I'm getting ACC only the last try. last failed try? Or what you mean by "the last try"? IIRC, failed transaction flag should be set for each leg if you want all failures. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Monday 25 January 2010, Daniel-Constantin Mierla wrote:
We make a call and the call tries from the Failure Route 5 times new gateway (with dispatcher) but WITHOUT success in termination. In every try we get back 503 Congestion. In this case how many CDRs we should see in our LOG.
We have the modparam("acc", "failed_transaction_flag", 6) and we setflag(6) for every INVITE.
iirc, at some point was an option to get all failed legs accounted. I don't remember using it so I have to check the sources (you are on 1.5.x, right?).
Hi Daniel,
do you refer to point 1.3 in the docs, "Multi Call-Legs accounting"?
Cheers,
Henning
Hi Henning,
On 1/25/10 11:48 AM, Henning Westerholt wrote:
On Monday 25 January 2010, Daniel-Constantin Mierla wrote:
We make a call and the call tries from the Failure Route 5 times new gateway (with dispatcher) but WITHOUT success in termination. In every try we get back 503 Congestion. In this case how many CDRs we should see in our LOG.
We have the modparam("acc", "failed_transaction_flag", 6) and we setflag(6) for every INVITE.
iirc, at some point was an option to get all failed legs accounted. I don't remember using it so I have to check the sources (you are on 1.5.x, right?).
Hi Daniel,
do you refer to point 1.3 in the docs, "Multi Call-Legs accounting"?
no, but might be used. That is good when you do redirect from config (e.g., 102 calling 103 which has redirect to 104 which has redirect to 105, then you want three records: 102 to 103, 103 to 104 and 104 to 105 so you know who to bill, 104 in this case if 105 is a paid number).
Cheers, Daniel
-
alex pappas -
Daniel-Constantin Mierla -
Henning Westerholt