| Table of Contents |
|---|
Summary
This article discussed how to understand and correct UDR usage Exceptions. In the sections Below you will find the main UDR Exception error messages and troubleshooting steps. If UDR records are being imported and the error "UUIH record(s) were found, but not in proper date range." then UUIH adjustments need to be made in the database.
...
Steps: to add a pattern, go into the GeoTree (Setup -> GeoTree), first decide where the pattern is located and go to that location in the GeoTree, i.e., select a Continent, Country, State, Category, etc. as needed until you are at the correct level. Check to see if the pattern exists in the tree, if not click the Add button at the right bottom of the page to add the pattern. After the pattern is saved, reprocess the UDR Exceptions to rate the missed records. See the GeoTree Configuration article for more information on modifying the GeoTree. Once we are sure the pattern is not missing, we need to assure the UDRLocation for this pattern is covered with a rate
...
Steps: add the missing rate in UDR Rates under the setup tabpage. You can also check:
If the package is attached to the user
The Rate plan
The Rate group
Rates (attached to the corresponding pattern in case the GeoTree is used)
| Info |
|---|
Note: Patterns with World zone=1 should have 1 added to their patterns. |
Missing Class
Issue: the class (e.g. Inbound, toll Free) may be missing the rate for the corresponding UDRRateGroup in the UDR rates table
...
This message can appear for several different reasons.
User missing in the UDRUserIdentifierHistory table
...
Resolution: check the validity of the Identifier in the UDRUserIdentifierHistory table to map calls to EngageIP Billing. For instance is the Identifier (DID, IMSI, etc.) on multiple accounts? Ensure there is only one match.
Steps:
Click on the on Setup tab
Click on UDR User Identifier History
Check the UDR User Identifier History table for the Identifier mentioned in the Exception message. If the Identifier is missing or incorrect check that:
the correct and valid package is attached to the user
the package on the user account has a valid UDR Rate Plan
locate the the identifier value on the user account and ensure it is valid (what the identifier field is named and where it is located depends on your configuration. For instance it may be a profile question tied to user-packages).
check the start and end dates (explained below)
...
Resolution: correct the dates in the UDRUserIdentifierHistory table
Steps:
Click on the Setup tab
Click on UDR User Identifier History
In the UDR User Identifier History table listing click on the Identifier mentioned in the Exception message
Check the Start and End dates and compare them to the UDR date in order to correct them
...
Invalid format for Release time / for BroadWorks for BroadWorks feed
Issue: this error most often occurs when the CDR type is "long Duration" and does not contain a release time (as the call is not complete yet). Alerts are generated for these CDRs because the call exceeded the duration threshold configured on the switch. In this instance rating is not performed and an exceptions is generated. Once the call is complete, another record will be sent with full details.
...
If you want not to bill cancelled User Usage, then that user's Owner must have OwnerParentAccountBillingType = Bill Accounts OR Bill Accounts Using Invoicer Taxes OR Owner of that user must be in Cancelled State.