[Spce-user] Billing fees best practices
Jiri Ptacnik
ptakjura at gmail.com
Tue Oct 20 03:30:54 EDT 2020
Thanks.
Not sure, if source plays any role. I tried also dot . in source in second
example, so everysource should be processed. Source is not important right
now for me. I need to rate outgoing calls, all.
So for example,
I am calling from 421222222222 to 421333333333 this is rated based on
regex OK
I am calling from 421222222222 to 420444444444 and this is unrated, but it
should be based on prefix
I am pretty sure, when I replace prefix rule with this regex rule, it will
work: .,^420.*$
But as I read in manual, regex is slower, better to use prefix...
G.
po 19. 10. 2020 v 23:41 odesílatel Dario D Busso <dbusso at sipwise.com>
napsal:
> Which are the CDR source and destination numbers you would expect to match?
> I see
> with regex_longest_pattern => source '.' and destination '^421.*$'
> with prefix => source '421' and destination '420'
> Did you switch the prefix in the second one?
>
> -d
> On 19.10.20 17:50, Jiri Ptacnik wrote:
>
> I am still confused,
>
> when i use this kind of billing fee pattern, it works fine:
>
>
> .,^421.*$,out,SVK,SVKall,0.00645,60,0.00645,60,0.00645,60,0.00645,60,0,regex_longest_pattern,,0,,0,0
>
> when i use this line in same billing profile, it is not working, unrated:
>
>
> 421,420,out,CZ,CZall,0.002500001,60,0.002500001,60,0.002500001,60,0.002500001,60,0,prefix,,0,,0,0
>
> What could be the problem? Regex patterns work, prefix does not.
>
> thanks
> George
>
> po 14. 9. 2020 v 13:26 odesílatel Jiri Ptacnik <ptakjura at gmail.com>
> napsal:
>
>> As I wrote, NO problem with upload.
>>
>> Looking for best practice for big billing fee set FORMAT. If you are
>> using regex, or prefixes... If someone put example of few lines of fees, it
>> will be great (you can zeroed prices, if you wish privacy).
>>
>> Thanks
>> George
>>
>> pá 11. 9. 2020 v 12:03 odesílatel Rene Krenn <rkrenn at sipwise.com> napsal:
>>
>>> Upgraded ngcp versions can provide various multithreaded ETL tools for
>>> bulk loading.
>>>
>>> You can use eg. fee import module to quickly load tens of millions of
>>> fees.
>>>
>>> br
>>>
>>>
>>>
>>> *Von:* Walter Klomp via Spce-user [mailto:spce-user at lists.sipwise.com]
>>> *Gesendet:* Freitag, 11. September 2020 11:09
>>> *An:* Jon Bonilla (Manwe) <manwe at sipdoc.net>
>>> *Cc:* spce-user <spce-user at lists.sipwise.com>
>>> *Betreff:* Re: [Spce-user] Billing fees best practices
>>>
>>>
>>>
>>> I noticed the timeout as well, but meanwhile in the background it will
>>> still finish the job. I'll take some time, but it works. At least on 6.5.x
>>>
>>>
>>>
>>> On Fri, Sep 11, 2020 at 4:13 PM Jon Bonilla (Manwe) <manwe at sipdoc.net>
>>> wrote:
>>>
>>> El Fri, 11 Sep 2020 10:00:51 +0200
>>> Jiri Ptacnik <ptakjura at gmail.com> escribió:
>>>
>>>
>>> >
>>> > How you deal with this kind of stuff on your CEs?
>>> >
>>>
>>>
>>> I've used 50K line fee csv files without issues. What's the problem when
>>> uploading 35K? Maybe nginx timeout?
>>>
>>>
>>>
>>>
>>> --
>>> PekePBX, the multitenant PBX solution
>>> https://pekepbx.com
>>> --
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> Warmest Regards,
>>>
>>>
>>> <https://myrepublic.com.sg/>
>>>
>>> *Walter Klomp*
>>>
>>> Head of Voice & Systems
>>>
>>> MyRepublic Limited
>>>
>>> T: +65 6816 1120
>>>
>>> F: +65 6717 2031
>>>
>>>
>>>
>>> MyRepublic Limited
>>>
>>> 11 Lorong 3 Toa Payoh Block B Jackson Square
>>>
>>> #04-11/15 Singapore 319579
>>>
>>>
>>> myrepublic.com.sg
>>>
>>> Follow us on: Twitter <https://twitter.com/myrepublic> | Facebook
>>> <https://facebook.com/myrepublicsg> | LinkedIn
>>> <https://www.linkedin.com/company/myrepublic>
>>>
>>>
>>>
>>>
>>> *The contents of this email and any attachments are confidential and may
>>> also be privileged. You must not disseminate the contents of this email and
>>> any attachments without permission of the sender. If you have received this
>>> email by mistake, please delete all copies and inform the sender
>>> immediately. You may refer to our company's Privacy Policy here
>>> <https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/>.*
>>> --
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>>
>>
> --
> Dario D. Busso
> Senior VoIP System Engineer
> Sipwise GmbH | an ALE Company
> Europaring F15 | 2345 Brunn am Gebirge
>
> Office: +43 1 30120
> Email: dbusso at sipwise.com
> Website: https://www.sipwise.com
>
> Particulars according Austrian Companies Code paragraph 14
> "Sipwise GmbH“ - Europaring F15 – 2345 Brunn am Gebirge
> FN:305595f, Commercial Court Wr. Neustadt, ATU64002206
>
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20201020/148d9bf1/attachment-0002.html>
More information about the Spce-user
mailing list