Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • UDR Rate Plan - a rate plan is one or more rate groups (priority is assigned to the groups and this priority determines where EngageIP first looks to match a rate for a call pattern. When a rate is not found in the top priority group, it goes to the second priority group to look for a match, and so on)

  • UDR Rate Group - a group contains one or more rates. For example, this is useful if you want to set up two groups of rates where one may contain Alaska and Hawaii patterns while the other does not. Basically you are only creating rate groups when there is a difference in rates.

  • UDR Class - these describe the type of call, they are determined by the rating engine based on the called/calling number, call direction or any other criteria in the rating logic (i.e. local, international, SBD, SMS, Long Distance, Toll Free, etc.)

  • UDR Pattern - a pattern is a sequence of numbers which represent all or part of a phone number. Example, the terminating number may be 15192490508, the pattern to match this may be entered as '519249'. The last 4 digits are removed as usually you don't want to specify a rate right down to the phone line, rather you want to specify a rate to the office location and all lines within that location would have the same rate. The beginning of the called number therefore determines the rate applied and whether its local or long distance

  • UDR Rate - values can be Fixed, Rated, Markup, Rated Markup or Fixed Markup and each is associated with a pattern or UDR Class.

  • GeoTree - This interface provides geographical location information / placement for patterns. The GeoTree only houses patterns and you do not add rates from this interface for patterns

  • UDR Feed - this describes the usage stream, switch, or location of the UDR details from your carrier or provider. Each feed can have it's own set of mediation processors

    • Processors - these are custom scripts applied per UDR Feed to validate the usage and trim it based on its format in order for EngageIP to be able to read and rate it correctly. These can be configured to run pre or post rating

    • Data Source - This value is configured in the 'Custom Code' section of EngageIP and is specific to your organization and should not be adjusted

...

  1. Basic Configuration (GeoTree Locations and Patterns, UDRClasses, Custom Codes, etc.) are configured by LogiSense

  2. Setup Billing Identifiers per account or userservice user-service (for example DID's, Enterprise ID's, etc.) -- this is a customer specific setup
    which generate the 'UDR User Identifier History' (UUIH) table (the UUIH table links a user to the user's billing identifier and rate plan)

  3. Setup UDR Rate Groups, Plans and Rates. (Note: large Rate Decks can be imported at this time using importing tools with the assistance of LogiSense personnel)

  4. Create UDR Buckets and assign them to Services

  5. Add UDR Rate Plans and Services to Packages

  6. Add Packages to customer accounts

  7. Import UDR Records (Put raw CDR files in the folder specified in the UDRfeed)

  8. Ensure that the EngageIP Rating [glossary_exclude] service [/glossary_exclude] is running. The Rating [glossary_exclude] service [/glossary_exclude] will process records and rate them according to the customers package and associated rate plan

UDR Billing and UDRBiller Date Definitions

...

  • Processing exceptions

  • Usage imported late (usage files didn't arrive on time or errored on import)

  • Rerating (manually via UDR report on the rating tab page or triggered by an invoice Void)

...

To see any errors, or logging related to what files are processing and progress generally, you can check the Event Log report on under Reports tab or the Alerts report on the same tabpage. These will provide indication of progress and any errors if existing.

...