Partial cdr

[Krzysztof Grzyb]

Hey,

Is there a way to create partial cdr's from online diameter session in
CGRateS.

I would like to create cdr each day after midnight. Physical session
might last even month.

Did CGRateS supports Tariff-Time-Change Avp?
This mean that if tariff will change in near future (before reservation
lifetime) then returns timestamp of this change.

If GGSN find Tariff-Time-Change Avp in response then in update after
Tariff-Time-Change will sent Usage before tariff change and Usage after
tariff change

Sequence diagram in attachment

[Dan Christian Bogos]

Hi Krzysztof,

Please see inline ...

On Tue, 2019-01-08 at 10:50 +0100, Krzysztof Grzyb wrote:
> Hey,
>
> Is there a way to create partial cdr's from online diameter session
> in
> CGRateS.
>
> I would like to create cdr each day after midnight. Physical session
> might last even month.

I would say it should be possible with a bit of work around, by
creating multiple CGRateS sessions/CDRs for one diameter session.

1. Create sessions with date inside OriginID (so you can have one CDR
per day).
2. Terminate session at the end of the day (this can be done by
filters when the time is close to midnight) or manually via calling
SessionSv1.TerminateSession API.
3. Produce CDR (again can be automated with filters for last updates
close to midnight) or manually by calling SessionSv1.ProcessCDR API.
4. New updates for sessions which are disconnected will create new
CGRateS session (that is why you need to organize the unique OriginID).

Not sure if the work around is acceptable for you but it is a way.
If you are looking for a more automated solution, please open an issue
and we can see about finding solutions there.

>
> Did CGRateS supports Tariff-Time-Change Avp?
> This mean that if tariff will change in near future (before
> reservation
> lifetime) then returns timestamp of this change.
>
> If GGSN find Tariff-Time-Change Avp in response then in update after
> Tariff-Time-Change will sent Usage before tariff change and Usage
> after
> tariff change
>
> Sequence diagram in attachment

This will be a feature-request. Please add it on github together with
the diagram.

Thanks,
DanB
>