You may have already normalized the CDRs when you had the destinations
in your tables. The normalization updates the CDR table with the
calculated destination id. If you normalize from scratch and still get
data like that you obviously have provisioned it somehow, it cannot
invent those numbers by itself without provisioning.
About dealing with custom prefixes you must craft an E164 class that
deals with your dialing plan and use it instead of the default
E164_Europe or E164_US. The updated Install wiki page describes this
in more detail.
Adrian
On Jan 16, 2009, at 1:19 PM, Brian Chamberlain wrote:
Hi All,
I am doing some testing to normalise my destinations in the way that
CDRtool expects them to be before it normalises them.. :)
I have to do this as some of my providers make me do silly things with
prefixes etc. I know CDRTool allows me to put in a prefix to strip but
I have an array of them that I need to do.
Anyway, question..
I am testing to make sure my numbers are correct so I import my radius
records into a new table and when I look at the table in CDRTool it
seem to be matching my sip destinations to names eg.:
+1415******** (VS (San Francisco) 1415)
This is confusing as I have nothing in my destination table.. Does it
do some kind of external lookup? I did have information in the
destinations table which I purged some time ago, maybe its cached
somewhere..
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
