[Asterisk-Users] ASTCC: potential billing issue and "fix"
Nabeel Jafferali
nabeel at jafferali.net
Sat Jan 22 15:00:37 MST 2005
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
More information about the asterisk-users
mailing list