Hi Brian,
The logic of the rating first determines the destination then it
searches for a price for it. So for every entry in destinations table
you MUST have an entry in the rates table otherwise the price is zero.
The best practice is to maintain a central minium destination table
common for all customers (add entries to it as it grows) and define
custom rates for each of them. Also if you have lot of resellers you
can create a main rating table and add only exceptions for the
destinations particular to some of them.
Adrian
On Jan 20, 2009, at 3:56 PM, Brian Chamberlain wrote:
Hi All,
I am sending calls to a number of different sip providers.
I have rates & destinations from all of them. Some of the providers
have broken up the amount of destinations into 30,000 different codes.
I am trying to build the rates and destinations tables so it is easy
to maintain in the future.
Would I be best having a minimal set of destinations to cover each
country and my local countries/areas and having the rates being more
specific.
I suppose my questions are the folowing.
If I have a destination:
1 USA
and a rate for 1 USA .02
and a rate for 1617 USA (Boston)
and the customer dials Boston then looking at the logic, even though I
don't have a boston Destination CDRTool will still rate the call using
the rate for 1617
If the reverse was through and I had a destination 1617 for boston but
only a rate for 1 USA would CDRTool use the 1 rate even though it
found the destination for 1617 in the destinations table?
Thanks,
Brian
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
