Hi Dimo,
Dimo wrote:
If you mean that avp will be available upon bye and that lifetime is
the duration since connect it would be great and looks exactly as what
we need. What type of duration do you plan on using? Seconds?
yes, this will be the idea. Could you upload this as a feature request
on the tracker?
thanks and regards,
bogdan
Best,
Dimo
On 11/16/06, Bogdan-Andrei Iancu <[EMAIL PROTECTED]> wrote:
Hi Dimo,
there are two ways to accomplish that:
1) make the dialog module to publish an avp with the dialog lifetime
when the dialog is terminated.
2) implement AVPs per dialog -> you will be able to store in an AVP
the start timestamp and make a diff at the end of the dialog.
Looking from the difficulty perspective, I say option 1) is more
feasible.
regards
bogdan
Dimo wrote:
> Hi guys,
> It was nice seeing and talking to you on the conference. As discussed
> with Bogdan I am sending this e-mail with a request for a dialog
> module feature.
>
> Is it possible to add to the roadmap an implementation of an avp
> exported by the dialog module which can hold the start time of the
> current call?
> The idea is on BYE to be able to access what the call start was (OK
> 200) for the call for which BYE message is being processed.
> In this way RADIUS accounting for call end can be done sending both
> start and stop time with extra accounting parameters and having the
> billing server calculate the duration of the call by only looking at
> the accounting stop.
>
> Best,
> Dimo
>
> _______________________________________________
> Devel mailing list
> [email protected]
> http://openser.org/cgi-bin/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
