[Spce-user] Billing fees best practices

[Jiri Ptacnik]

Hello everyone,

What are the best practices for big billing profiles / billing fees?

For example, I have 35 000 lines with prefixes and prices from my
peering partner in this format:

prefixes (per line)
-----------
99576
99590
99532
49
49155
49156
4915630
4915678

or another format, per line, more grouped, only 8000 lines
------------------------
614200, 614201
61453
43
43651, 43652, 43653, 43657, 43659, 43666, 43668, 43669, 4367, 4368,
4369, 43710, 43711, 43730, 43740, 43810, 43820, 438703411, 438706411,
438713411, 438716411
43696
43664, 43680, 43681, 43688
43501, 43502, 43503, 43504, 43505, 43506, 43507, 43508, 43509, 43517, 4357, 4359
43660, 4367833, 4367890, 4367891, 43699
43644, 43655, 43661, 43663, 43665, 43667, 436688, 43670, 43677, 43678,
4368860, 4368861, 4368864, 4368877, 436889, 43689, 43690

I tried import first example as Prefix string match rule, but it did
not bill. What is working is rewrite this rules to regex like (just
example) this:

^(421|423|420|30|31|32|33|34|36|39|40|43|45|46|47|48|49|350|351|352|353|354|356|357|358|359|370|371|372).*$

But create billing profile with optimized regex fees in less lines is
extremely hard, and when peering partner send new price list, it will
be more hard. Even if we rewrite 8000lines list to regex, GUI is not
taking some realy long expressions. And may be, a lot of complex
regexs may be slow to rate...

How you deal with this kind of stuff on your CEs?

thanks
George