Building

The First Route

Step One:

Define the names for customers and vendors. Although the system allows using
the same name for both customers and vendors, but on our rental platform we
do not allow that, as that will cause occasional problems on database
synchronizations. Therefore if we have a customer called p180-telco of which is
both a customer and a vendor, we need to define two names:

1. p180-telco-cust
2. p180-telco-vend

For the sake of buiding the first route, we assume the two vendors are:

1. p180-vendor101
2. p180-vendor102

Left click on the mouse over customer / vendor table and select Add.

Fill in required information.

Billing scheme is presented by three numbers.

A/B/C

A= maximum free time no billing, say if you allow a customer to enjoy 6 seconds
no need to pay per call, then A = 6; if you dont allow free call, A=0

B=minimum billing duration. If B=6, meaning minimum duration is 6 seconds

even the customer calls for only 2 seconds

C=incremental billing duration. If C=6, meaning even the customer calls for 10s,
he will be billed as 6+6=12 seconds

To illustrate the above, the billing increment should be written as 0/6/6.

Then the vendor for the same entity is created as an illustration

Then two vendors are created for illustration of the first route

Step Two:

Create the Accounts to hold the money for these customers and vendors.

1. Go to Billing | Accounts, left click while mouse over the Accounts table
and select Add.
2. Create the account name and associate it with the correct customer /
vendor ID. If this step is wrong, all billing is going to be wrong.
3. Min balance restriction threshold = the minimum balance required for a
prepaid customer to make call, if balance is below this figure, no call can
come in, example is $50
4. Min balance notification threshold = the notification by email will be sent
to this customer contact person (which can be set as switch owner
instead) to advise them balance is low and would be blocked if balance
continues to decrease without payment, example is $100
5. The effect combined by 3 and 4 will be, when the prepaid amount is
below $100, an email will be sent to remind payment; and when the
prepaid amount is below $50, calls will be blocked
6. For illustration purpose, if the customer is postpaid, no need to put these
two balances.
7. If the customer is postpaid a credit limit is required, say Min balance
restriction threshold = -$5,000 and Min balance notification threshold = -
$2,000; this will mean if the usage of this customer reaches $2,000 he will
be notified, if the usage exceeds $5,000 calls will be blocked without
payment
8. We will leave invoicing settings untouched for at this stage.


Step Three

Create payment record for prepaid customers

1. Go to Billing | Payments, add a payment record
2. Input the necessary information

Step Four

Set up IP addresses for customers and vendors. The outgoing technical prefixes
to vendors, if any, are being set at this stage while the incoming technical
prefixes are set elsewhere.

1. Go Equipment | Equipment, select Add while mouse over the equipment
table
2. Fill in the basic information. Assuming this customer gateway uses SIP
only and we are using Codec group Wholesale (p180-WS).
3. Note:
a. Proxy policy (orig.) by default we use use terminators proxy
mode. However if one way audio is reported at the customer end,
change this to proxy media.
b. Proxy policy (term.) by default we sue do not proxy whenever
possible.. However if one way audio is reported at the vendor end,
change this to proxy media.
c. Codec sorting (check orig. box if it is a customer, check term. box if
it is a vendor; mixing up here will cause unwanted results)
4. To prevent mismatch of codec, check the box of Can update media
channel before connect.
5. To avoid hang calls due to missed signals sent to the switch, put RTP
timeout (sec) = 10, meaning if the switch does not detect and media

packet for 10 seconds, the call will be closed. The disadvantage being for
those people they like to hold the line and not talking, the call will be cut.
Leave it blank if no such need is required or set longer values as
appropriate
6. Should call termination reasons are not to be shown on customer CDR,
open SIP settings and select do not transfer Reason Headers under SIP
Reason handling options. Some customer switches would not be able to
reroute if this option is selected. Please work with customer to find out.


Make sure the customer ID and the equipment are paired correctly, else traffic
could not pass.

For illustration, 2 vendor equipment are set. The outgoing technical prefixes are
denoted as ^(.*)/2234#\1, meaning a technical prefix is 2234# is added before
the call is being sent to the vendor.

This is set under Number translation rules, Out DST translate.

The Port H.323 and Port SIP are configurable for outgoing traffic to vendors (but
not configurable for incoming, of which standard ports are used), should this
vendor only accept SIP traffic at port 8900, set the value next to Port SIP as
shown.

10

11

Assuming this vendor p180-vendor-101 has two gateways of different IP

addresses and traffic are to be sent to this vendor different gateways according
to some rules.

7. Go Equipment | Equipment Group
8. Left click while mouse over the equipment group table and select Add
9. Create the Equipment Group name and fill in necessary information
10. IN the field Equipment selection rule select one from pull down
a. try routes sequentially meaning 1 call to equipment 1, 1 call to
equipment 2 and so on, within the group
b. try routes randomly meaning calls are distributed to different
equipment of same vendor at random
c. try routes according to load share rules meaning calls would be
distributed to different equipment according to the capacity as
configured during equipment setup
d. try routes by priority meaning to distribute calls according to the
priority values set in the equipment, higher value denotes higher
priority
e. Number of tries meaning if redistribute among the group if first
attempt fails, usually 2 is a safe value
f. Max outgoing calls is to be set if you want to limit as a group, no
need to set if you limit by individual equipment
g. Go back to equipment and assign the equipment group name just
created to them

12



Setting max outgoing calls in Equipment settings

Setting priority in Equipment settings, for members of a group

13

Assign equipment group back to equipment by editing equipment settings

14

Step Five

Create Rate Groups (rate = rate offered to customers, selling rates)

One customer incoming technical prefix can be assigned with one rate group and
one route group, customers with multiple routes would need to have multiple
incoming technical prefixes:

Customer p180-telco-cust incoming traffic to Philippines Mobile of which

Tech prefix 11011 = general route using low cost vendor
Tech prefix 11012 = premium route using higher quality vendor

Say the two rate groups being:

1. 639-standard
2. 639-premium

Steps are:

1. Go to Origination | Rate plans
2. Select Add while left click mouse over on rate plan table
3. Fill in required information
4. For illustrations, two rate plans are set.

15


Step Six

Create Route Groups (routes = termination routes, buying rates)

If the route is only be using 1 vendor, associate the route with a single vendor; if
the route is to be using many vendors, associate the route with the switch name,
usually pNNN

16



Step Seven

Defining rate plan and route group as per customer incoming traffic technical
prefix

1. Go Customer / Vendor | Customer Authentication
2. Select Add while left click mouse over the customer authentication table
3. IP address much match with one of the equipment of this customer
4. Netmark is to determine if incoming ip is 1 address or range of address, if
open for entire range use 255.255.255.0; if open for 1 ip address only, use
255.255.255.255
5. Tech Prefix is the prefix the customer has to add before sending traffic to
our switch, say they are sending to Philippines mobile and the required
technical prefix is 180111, then the dialing pattern of this customer is
180111 + 639 + 171234567
6. Match the customer name, equipment (if wrong here, cannot run traffic),
routing plan, rate plan and chargeable account here. Allow no mistake.
7. Assuming this customer also send to premium route, and the tech prefix
assigned to them is 180222, a second customer authentication record is
required.

17

8. Create as many records here to denote different rate / route
combinations for any one customer based on different tech. prefix. Can
only associate one set of rate / route per one tech. prefix.

Step Eight

Create rate table

This is to create selling rate to customers.

1. Go to Origination | Rates
2. Mouse over rate table
3. Select Add from menu, obtainable with left click while mouse over the
rate table
4. Associate the rate with the correct rate plan

18

19

Step Nine

Create route table

1. Go to Termination | Routes
2. Mouse over the route table and left click, select Add from the pull down
menu
3. Match the vendor, routing plan
4. Input prefix for the route
5. Input rate
6. Select equipment. If there is an equipment group use the group, else
select the correct equipment
7. Create another route with matching parameters

20

21


Step Ten

Verify if configurations are done correctly

1. Go to Debugging | Route hunting
2. Select the customer to test
3. Select the matching information, say we like to test if incoming traffic
180111639171234567 will be passed to the correct vendor
4. Select zone (only one available)
5. Click OK
6. Result will be shown under tables Routes Fit for routing and Routes
unfit for routing. Reasons for not fit will be highlighted in red.
7. Should details of call flow is needed, can use the Call Simulation function
instead of Route hunting

22

23

24


And the first route is setup correctly.

*** End of Notes ***

25