Updating termination rates on astpp

By Yevgeniya Suminova on 2021-03-24

Contents

Introduction. 1

ASTPP limitations. 1

Updating rates in web GUI on ASTPP. 1

Check termination rates in DB. 1

References. 1

End of document. 1

Introduction

In this document we will follow the process of updating termination rates on ASTPP.

Different VoIP billing platforms handle such processes differently. Some billings have an option of fixing new rates effective from X date and time. Other feature is saving the past rates in the database for a very long period of time. Thus, the CDRs can be obtained for long periods in the past.

ASTPP limitations

1. We cannot set the effective date for termination rates in future. They will be effective from the moment we upload them

2. Looks ASTPP does not save past termination rates. It just completely rewrites existing rates.

3. The points above make us doubt on how exact would be the CDRs? Probably, in order to have the exact data, we need to set up the generation of invoices for the vendor(provider) daily.

Updating rates in web GUI on ASTPP

1. Prior to import new rates we have checked how many lines do we have for Provider_N termination rates:

- 8351 rates:

2. We have also checked the “Created Date” and “Modified Date” fields.

- In our case these dates are identical as we have never yet updated the rates.

3. Then we took exactly same list of rates and imported them several times.
Each time we changed the price to be able to differentiate our tests.
Set prices: 0.1, 0.2, 0.52, 0.34 for all rates

4. We noticed that in the free version of ASTPP we cannot import the “Priority” field.
So, such column exists, but is a subject of manual implementation in the free version?

Here are all available columns for importing termination rates:

5. After importing updated rates, and each time we imported them (we tried around 3-4 times), rates were re-written. Which means the quantity of rates remained exactly the same.

In our case 8351 lines of rates.

6. We also saw that with each import, the “Modified Date” field was changed.

The “Created Date” field remained always the same. See one example:

Check termination rates in DB

1. We have 154 termination rates for our Provider_N

We have re-imported termination rates for this provider once.

2. We found our modification in DB:

mysql> select last_modified_date from outbound_routes

    -> where trunk_id = 6;

3. Let’s see if we have same quantity of rows if we select creation date:

mysql> select creation_date from outbound_routes where trunk_id = 6;

So yes, the quantity of rows is same.

4. We will now again import new rates for the same provider and will se what DB will show.
“Modified Date” has changed again:

5. We check again the DB:

- Quantity of rows remained same

- The time of last_modified_date has changed accordingly:

6. For the moment we do not see any other table where not effective (past) termination rates could be stored.

Here is the list of tables:

References

https://docs.astppbilling.org/pages/viewpage.action?pageId=4196874

End of document

***

©4z.com