[Serusers] Accounting Failed INVITE Messages

Java Rockx javarockx at gmail.com
Fri Mar 4 20:00:57 CET 2005


Klaus,

Good point. I've fixed my ser.cfg - Thanks!!
 
Cheers,
Paul


On Fri, 04 Mar 2005 17:52:33 +0100, Klaus Darilion
<klaus.mailinglists at pernau.at> wrote:
> AFAIK that should do. Does accouting of succesful transactions work?
> 
> btw: why 503? wouldn't 403 more appropriate?
> 
> regards,
> klaus
> 
> 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 at pernau.at> wrote:
> >
> >>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:
> >>
> >>
> >>>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 at lists.iptel.org
> >>>http://lists.iptel.org/mailman/listinfo/serusers
> >>>
> >>>
> >>
> >>
> >
> >
> 
>




More information about the sr-users mailing list