asterisk users - Jan 2005 - ASTCC: potential billing issue and "fix"

I had the same problem, and it's a database issue, not a code problem.
Use the character "^" in front of the pattern in the routes table, and
I
think you will have better luck.  E.g., "^1416......." will match only
numbers that start with "1416".

Bruce Komito
High Sierra Networks, Inc.
www.servers-r-us.com
(775) 236-5815


On Sat, 22 Jan 2005, Nabeel Jafferali wrote:
> Before I start, I just want to say this is not necessarily a problem
> with ASTCC, but may be a problem the way I have set up ASTCC (and
> possibly the way others have set it up as well). The issue is that ASTCC
> tries to match the pattern *anywhere* in the called number, not
> necessarily only at the beginning.
>
> I have set up ASTCC Routes like this:
>
> 1800		Tollfree	Trunk1	0	0	100
> 1416		Canada	Trunk2	0	0	400
> - other NANPA codes -
> 1		USA		Trunk1	0	0	400
> 011971	UAE		Trunk3	0	0	3000
> - other international codes -
>
> Now, for "other international codes" I have not included all the
> countries, just the ones that are important for now. I has expected to
> add others as they became necessary. However, today somebody called
> "011966..." which is not one of the included countries. I guess
it
> instead picked up the "1" pattern and billed the call at 4c per
minute.
>
> To get around this, I tried to add:
>
> 011		Other		Trunk3	0	0	10000
>
> which should have charged $1 per minute for all other countries and sent
> them out Trunk3. If I call "011966..." it works fine. But, if I
call
> "011416..." it picks up the NANPA pattern for Canada defined,
instead of
> the non-NANPA "catch-all" I have defined.
>
> I tried to fix the problem by adding "0112" to "0119"
patterns (4-digit,
> to make a "better" pattern match) to the routes table, so
"011416..."
> would pick up "0114" instead of "1416", but it
didn't work. Reordering
> the mySQL table so these 8 non-NANPA catch-alls appeared at the top of
> the table (before the "1416" and other NANPA entries) fixed it
though.
>
> --
> Nabeel Jafferali
> Tel: +1 (416) 628-9342  Toronto
>      +1 (646) 225-7426  New York
> FWD: 46990
> Email/MSN: nabeel<at>jafferali.net
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
> This message has been categorized as "Legitimate" by Bayesian
Analyzer.
> If you do not agree, please click on the link below to train the Analyzer.
>
http://nospam.wpti.net/bt/a.aspx?M=C:%5Csmtpmail%5CBayesTraining%5C2005-01-22%5Cc2348896a2944f408c615aa0e5208995&C=2
>
> --
> -----------------------------------------------------------------------
> This message has been inspected by DynaComm i:mail
> -----------------------------------------------------------------------
>
>
>

Before I start, I just want to say this is not necessarily a problem
with ASTCC, but may be a problem the way I have set up ASTCC (and
possibly the way others have set it up as well). The issue is that ASTCC
tries to match the pattern *anywhere* in the called number, not
necessarily only at the beginning.

I have set up ASTCC Routes like this:

1800		Tollfree	Trunk1	0	0	100
1416		Canada	Trunk2	0	0	400
- other NANPA codes -
1		USA		Trunk1	0	0	400
011971	UAE		Trunk3	0	0	3000
- other international codes -

Now, for "other international codes" I have not included all the
countries, just the ones that are important for now. I has expected to
add others as they became necessary. However, today somebody called
"011966..." which is not one of the included countries. I guess it
instead picked up the "1" pattern and billed the call at 4c per
minute.

To get around this, I tried to add:

011		Other		Trunk3	0	0	10000

which should have charged $1 per minute for all other countries and sent
them out Trunk3. If I call "011966..." it works fine. But, if I call
"011416..." it picks up the NANPA pattern for Canada defined, instead
of
the non-NANPA "catch-all" I have defined.

I tried to fix the problem by adding "0112" to "0119"
patterns (4-digit,
to make a "better" pattern match) to the routes table, so
"011416..."
would pick up "0114" instead of "1416", but it didn't
work. Reordering
the mySQL table so these 8 non-NANPA catch-alls appeared at the top of
the table (before the "1416" and other NANPA entries) fixed it though.

--
Nabeel Jafferali
Tel: +1 (416) 628-9342  Toronto
     +1 (646) 225-7426  New York
FWD: 46990
Email/MSN: nabeel<at>jafferali.net