tks :-) But how, I am doing billing /rating based on prefix in lcr, now I cannot put these in lcr, and bill like that since some 44207 numbers will go to pstn , and other will not. What I am trying to do is to have the same billing system for all, and for enum calls rate them as £0.00, which is where the problem is because the billing rates are per prefix, and these have no special prefix. Iqbal Klaus Darilion wrote:

but I want it to be entered in acc table, but just set a price to zero when doing the bill run. In the method below I can either charge or not, I wish to be able to configure the price charged on a enum call, currently zero. This must be done by the rating engine, which is based upon prefix from lcr table, but since in lcr we dont distinguish between enum numbers or normal, then I cannot have a diff rate for it. The only way seems to be to look at the acc table, to see which gateway (internal/external) was used, which is not accurate since I am sure some gateway will use the same for passing external postn calls, as well as routing internal e164. Iqbal Klaus Darilion wrote:

looked into this, the problem I see is that when a enum lookup is done the domain part can vary, hence i cant match/look for that. I have 3 scenarios 1. PSTN call, this does enum first not match, find gw, and send out call based on prefix 2. PSTN, enum lookup matches, send call out on enum path, no lcr invloved 3. prefix based call on IP, again go out on IP, no lcr lookup I am trying to think of a way where 2 and 3 use the lcr module, where I can then place the gateways, for prefix as well as for enum matches, that way its all in one system. The prefix one can be done, currently I am not really routing to other based on prefix, but would like to, but I dont want lots of prefix based routing in ser, would like to leave that in lcr...thinking about this this should be possible eg 777 (goes to ISP A) hence in lcr I could put 77712345 mapped to ISP A ip address...is anyone doing this. If this works 3 is solved, that leaves scenario 2. When the enum happens, if we can get it to call lcr, and lcr do the routing ( I know this is overkill, since enum is supposed to tell you the route) . Maybe when enum number is dialed tell account to prefix the enum route in billing with a "special " prefix 3333 b4 all numbers, and then add this as a dummy prefix in lcr, or something like that..thoughts Iqbal Daniel-Constantin Mierla wrote: