[OpenSIPS-Users] What's the best solution for national accounting?

[Brett Nemeroff]

I'm not sure if I'm answering your question right, but in general it's a
good idea to normalize the destination numbers. ie: if your users don't
normally dial in e.164 format, normalize it for the cdr to that. For
example, if they dial a local number with the national bit discarded, then
add the national bit. the pseudo logic looks like:
if $customer = 23 then
    set to_did = 01144$rU
end if

You don't have to dial on that of course, but it helps to account it that
way. I'd be interested in hearing how other people are doing this as well.


On Thu, Jun 11, 2009 at 8:56 AM, Joan <aseques at gmail.com> wrote:

> I'm using the opensips+cdrtool+mediaproxy+freeradius solution for an
> opensips setup.
> My users are dialing directly the number in case of national calls,
> i.e. 912123123.
> In the SIP Destination table, it gets writen as 912123123 at example.com.
>
> And the problem is that I cannot get a price for the calls because, it
> depends on the definition of E164_Europe in the cdr_generic.php
> Since it doesn't fit on any of the categories, the call is just free.
>
> My question is, what is the better solution for this?
>
> 1.- Users have to mandatory use either 912123123 or
> 00international_code912123123 for the call
> 2.- I correct the E164_Europe to suit my needs
> 3.- Somehow change the values before normalizing the table?
> 4.- Something else?
>
> Thanks for your answers
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090611/ad9fc4f2/attachment.htm