On 28/10/16 16:38, Markus wrote:
I'm using Asterisk2Billing (v2.0.16) and it appears to have an
annoying bug. When there are rates for e.g. 44 (UK landline) and 44870
(UK premium) and a fraudster manages to somehow dial 44-870 instead of
44870 the rate for 44 will match, not the one for 44870.
Am 28.10.2016 um 17:58 schrieb Max Grobecker:
why not using FILTER() in your dialplan to eleminate all chars that are not
numeric?
Like
Set(VAR=${FILTER(0-9+),${EXTEN}})
That would eleminate all characters you're not expecting.
That's great! Didn't know FILTER. Thanks!
--
Also, make sure you are using fail2ban and that you have good
passwords on your extensions.
On Fri, 28 Oct 2016 11:55:42 -0400,
John Covici wrote:
>
> How about a \ before the - ?
>
> On Fri, 28 Oct 2016 11:38:13 -0400,
> Markus wrote:
> >
> > Hi list,
> >
> > I'm using Asterisk2Billing
Hi,
Am 28.10.2016 um 17:38 schrieb Markus:
> exten => _-.,1,NoOp(Blocking dash)
> exten => _-.,n,Hangup
> How do I do it right?
why not using FILTER() in your dialplan to eleminate all chars that are not
numeric?
Like
Set(VAR=${FILTER(0-9+),${EXTEN}})
That would eleminate all
How about a \ before the - ?
On Fri, 28 Oct 2016 11:38:13 -0400,
Markus wrote:
>
> Hi list,
>
> I'm using Asterisk2Billing (v2.0.16) and it appears to have an
> annoying bug. When there are rates for e.g. 44 (UK landline) and
> 44870 (UK premium) and a fraudster manages to somehow dial 44-870
>
Hi list,
I'm using Asterisk2Billing (v2.0.16) and it appears to have an annoying
bug. When there are rates for e.g. 44 (UK landline) and 44870 (UK
premium) and a fraudster manages to somehow dial 44-870 instead of 44870
the rate for 44 will match, not the one for 44870.
So, I would like to
