Skip to content

Commit

Permalink
rating_routing: set up some markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
jamesaimonetti committed Oct 1, 2015
1 parent 88d71e4 commit 2db6e2e
Showing 1 changed file with 59 additions and 77 deletions.
136 changes: 59 additions & 77 deletions doc/reference/routing.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,162 +5,144 @@ Language: en-US
Version: 3.22
*/

= Rating and Routing
# Rating and Routing

Topic Goal: Describe how Jonny5 and HotOrNot work. This implies also teaching
people how authz and authorization work (a flowchart would be AMAZING). Things
like how dry run works, etc would be extra-amazing.
Topic Goal: Describe how Jonny5 and HotOrNot work. This implies also teaching people how authz and authorization work (a flowchart would be AMAZING). Things like how dry run works, etc would be extra-amazing.

-----

Slide ideas:
## Let's talk billing

People like to talk a lot about "billing". What **IS** billing?

/*Intro Slides: */People like to talk a lot about “billing”. What IS billing?
The request usually comes in the form “I just need something simple.” That’s
usually a gross understatement of the actual desire.
The request usually comes in the form "I just need something simple." That's usually a gross understatement of the actual desire.

-----

Billing is a complicated topic. It helps to break it into pieces. You generally
have:
## It's complicated

Billing is a complicated topic. It helps to break it into pieces. You generally have:

* Recurring Subscriptions (monthly charges)

* Pro-rated monthly subscriptions

* Activation charges

* Per-minute / per-use charges

* Limits on spend (daily, monthly, pre-pay/credit base)

* Allocations of usage (400 minutes included - daily, monthly, etc.)

* Bursting / overage charges

* Rating of calls

* Pre-pay vs. post-pay

* Deposit tracking

* Accounts Payable / Accounts Receivable

* Strategies for warning customers when they have low balances, are overdue, or
have an expiring credit card

* Strategies for warning customers
* low balances
* overdue
* expiring credit card
* Discounts

* one time
* continuous
* Rate decks (global + account based)

* Actual cost analysis

Today, we're NOT going to cover all these things. It's too much. We're going to cover only one section of this - rating and routing.

Today, we’re NOT going to cover all these things. It’s too much. We’re going to
cover only one section of this - rating and routing.

-----

## Rating & Routing in Kazoo

*/Rating & Routing in Kazoo:/*
Kazoo's rating and routing functions are actually quite robust.

But they are not well documented so it can be easy to get lost in them.

Kazoo’s rating and routing functions are actually quite robust. But they are not
well documented so it can be easy to get lost in them. Today, we’re going to
attempt to document and explain many of them. Also, our training course has been
updated to include training on this topic.
Today, we're going to attempt to document and explain many of them.

## How we rate

- How we rate

Rating is done by jonny5. It:
Rating is done by HotOrNot:

* Normalizes your number dialed? Yes? (how?)

* Checks it against a database?
* Selects a rate based on (weight? Longest match?)
* Adds the rate to the call as a variable (doesn't necessarily mean they're charged)

* Selects a rate based on. … (weight? Longest match?)
-----

* Adds the rate to the call as a variable (doesn’t necessarily mean they’re charged)
## FLOWCHART!

FLOWCHART!
So awesome

-----

- How we do limits
## How we do limits

Limits are a concept of limiting how many flat-rate (included) calls are
available which WON’T actually result in a charge.
Limits are a concept of limiting how many flat-rate (included) calls are available which WON'T actually result in a charge.

You can limit based on:

* Inbound

* Outbound

* Resource consuming (define what this is)

* otherstuff?

-----

The hierarchy of limits is:

* Global (system_config)

* Overridden by reseller?

* Overridden by account?

If a limit is reached or not found, then we fail back to use credit based on the
rates

-----


- How we log and track balances
## How we log and track balances

Talk about the MODB database

- MODB databases

- Monthly rollovers

- Strengths (this is basically like writing a text file)
* MODB databases
* Monthly rollovers
* Strengths (this is basically like writing a text file)
* Weaknesses (not great for searching)

- Weaknesses (not great for searching)
-----

## Why our approach is unique and different

- Why our approach is unique and different
* We rate real-time
* Helps with fraud
* Scales by accounts, so technically infinitely

- We rate real-time
-----

- Helps with fraud
## How it works

- Scales by accounts, so technically infinitely
Flowchart?

-----

- How to set it up
## How to set it up

IF TIME, show off relevant system_config options

-----

- How to check that its operating
## How to check that it's operating

Sup commands?

-----

- How it works

Flowchart?


- How to read the logs

Why did a call get rated but not billed? Or how do you know if you’re over
limits? Etc.


- What to do when it doesn’t work
## How to read the logs

Why did a call get rated but not billed?
Or how do you know if you're over limits?
Etc.

- Helpful sup commands
-----

## What to do when it doesn't work

- Performance impact
Helpful sup commands
Performance impact

0 comments on commit 2db6e2e

Please sign in to comment.