Post Rating

Post Rating Schedule

To be used by Post Rating Scheduler to poll the CDR from an NMS with a set of filtering criteria, apply rate plan of the Charge To Account, and record the charges to the CDR in the NPS. 

  • The output CDR entries written to the NPS's CDR by the Post Rating are marked with cdr_type=="post"
  • The Post Rating Schedule is being scanned every PostRatingScanPeriod, and PostRatingPollSize time interval of CDR are polled by each scan.
    • The ratio PostRatingPollSize/PostRatingScanPeriod determines the amount of time to process a period of CDR. e.g a ratio of 6 will take 1 day to process every 6 day of CDR.
    • Call Per Second (CPS) must be be considered in choosing the PostRatingPollSize to prevent the number of CDR per poll to become too large (i.e. no more then a few thosand). e.g. 10 CPS will result in 3000 CDR per poll if PostRatingPollSize=="5 minute".
    • See NAS System Parameters for more details of these parameters.
  • When adding a new Post Rating Schedule entry, set the Next Poll to the desired CDR Release Time where the specific Post Rating should start polling the CDR from.
    • Next Poll for an existing Post Rating Schedule entry can be modified to skip over a period of CDR, or to re-rate an already rated period.


Parameter Values Default Descriptions
User Account
String <NULL> Specify the Account filter for NMS's CDR
Account Domain
String <NULL> Specify the Domain filter for NMS's CDR
<NULL> Specify the PAC filter for NMS's CDR
Specify DB's DSN to support post rate target with same domain name from multiple target servers
Charge To Account
String <User Account>
Specify the Account to associate the Rating Result
Charge To Domain
String <Account Domain>
Specify the Domain to associate the Rating Result
Debit Account
Yes or No No
If "Yes", debit the Rating result from the associated Charge Account
Batch End Only
Yes or No No
If "Yes", Rate only CDRs that are marked as "Batch End"
Rate Orig
Yes or No Yes
If "Yes", Rate CDRs originated by the Account User
Rate Term
Yes or No No If "Yes", Rate CDRs terminated to the Account User
Rate User
Yes or No Yes
If "Yes", Rate CDRs correlate with Account User in either the CDR "Orig Sub", "Orig Domain", "Term Sub" and  "Term Domain"
Rate Connection
Yes or No No If "Yes", Rate CDRs correlate with Account User via Connection's Rate Account and Domain
Rate Class
Yes or No No If "Yes" apply LERG Class to Rate Lookup.
LERG Class can be either fetched from NMS or locally looked up as determined by "Fetch Class"
Logical Orig

Device URI
"Device URI" - origination defined by <From-URI>
"Logical URI "- origination defined by <Logical URI>
"BTN" - origination defined by <Origination ID>
"By ID" - origination defined by <By ID>
Logical Term
String Device URI "Device URI" - termination defined by <From-URI>
"Logical URI "- termination defined by <Logical URI>
"BTN" - termination defined by <Origination ID>
Translate Orig Number
String <NULL>
Rule to translate the Origination Number (i.e. User part of the Origination URI) prior to Rating
Translate Term Number
String <NULL> Rule to translate the Termination Number (i.e. User part of the Termination URI) prior to Rating
Fetch Class
Yes or No No If "Yes", fetch LERG Class from NMS CDR. If "No" lookup LERG Class at NAS

Multi-Tier Rating

Multi-Tier rating can be implemented by multiple Post Rating to the same set of CDR.

As an example, some CDR's would need to be rated twice, once with the rate a carrier is selling it's service for, and once with it's cost, so the margin a carrier makes can be calculated. Let's say if you click on 'generate invoice' for a user/domain/reseller, if there could be another link to 'generate cost & margin', which would take a different rate plan and run all CDR's through this rate plan.