4 Mar
2005
4 Mar
'05
5:24 p.m.
Hi Paul,
Note that by enabling "failed_transactions" ALL the failed transaction
will be logged which will generate a lot of accounting traffic. I would
suggest you to consider forcing accounting from script only where is
needed by calling:
acc_db_request("no_pstn_access","acc");
Best regards,
Marian
Java Rockx wrote:
Klaus,
Thanks for the reply. I do have failed_transactions set to 1 and in
the main route block I call setflag(1) for INVITE messages. Is that
all I should have to do?
Regards,
Paul
On Fri, 04 Mar 2005 15:48:37 +0100, Klaus Darilion
<klaus.mailinglists(a)pernau.at> wrote:
--
Voice System
http://www.voice-system.ro
Hi Paul!
Try to set failed_transactions.
from acc/README:
1.3.5. failed_transactions (integer)
Should be failed transactions (status>=300) accounted too ?
Default value is 0 (no).
Example 1-5. failed_transactions example
modparam("acc", "failed_transactions", 1)
regards,
klaus
Java Rockx wrote:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Hi All.
How do I get SER to account for failed INVITE messages? For example,
if someone attempts to call a PSTN number and they do not have the
free-pstn ACL, then our server replies with a 503 Service Unavailable.
I'd like to see this appear in the MySQL acc table.
Do I just use the setflag() function in the failure route for INVITEs?
For example:
route {
t_on_failure("1");
if (!t_relay()) {
sl_reply_error();
break;
}
}
faillure_route[1] {
if (method=="INVITE") {
setflag(1);
}
}
Regards,
Paul
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers