Difference between revisions of "Destination Groups Policy"
| Line 2: | Line 2: | ||
Main idea is to keep Destination Groups in a stable and constant state. | Main idea is to keep Destination Groups in a stable and constant state. | ||
'''BILLING IS DONE BY PREFIX NOT BY GROUP''' | |||
It is one-time job to configure Destination Groups and include prefixes which you want to be in your Destination Groups. | It is one-time job to configure Destination Groups and include prefixes which you want to be in your Destination Groups. | ||
Latest revision as of 09:33, 4 November 2015
This page will explain how to deal with Prefixes (Destinations) and Destination (Prefix) Groups.
Main idea is to keep Destination Groups in a stable and constant state.
BILLING IS DONE BY PREFIX NOT BY GROUP
It is one-time job to configure Destination Groups and include prefixes which you want to be in your Destination Groups.
Later you can only slightly adjust Destination Groups by adding/removing NECESSARY prefixes to/from Group.
Your prefixes in the Destination Groups will be used in Statistics and Tariff management.
IMPORTANT: IT IS NOT NECESSARY TO ASSIGN ALL PREFIXES TO DESTINATION GROUPS
This is very important to understand.
During the course of work, you will import a lot of new tariffs with new prefixes. And the prefixes which are not already in your DB by default will not be assigned to any Destination Group.
AND THIS IS TOTALLY FINE.
No need to assign all and every prefix to the Destination Group.
Do this only if you REALLY NEED it.
