[Spce-user] No billing info in CDRs of peer to peer calls

[Roberto Oliveira]

Rene,
Thanks for the clear explanation. You figured it all right.
My situation is of type 4, but I'd like to treat the source as a subscriber
and have this calls rated. Is this possible?

I tried to create a subscriber and insert the source IP address as a Trusted
Source, but it did not solve the problem. Any advice?


Thanks--



Roberto Oliveira

-----Original Message-----
From: Rene Krenn [mailto:rkrenn at sipwise.com]
Sent: terça-feira, 31 de maio de 2016 06:27
To: Roberto Oliveira <roberto.oliveira at tmco.com.br>
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] No billing info in CDRs of peer to peer calls

hello roberto,

i assume you are looking at the accounting.cdr table and all your CDRs show
rating_status='ok'. by "all costs" you mean the CDR columns below show 0
cents:

  source_carrier_cost
  source_reseller_cost
  source_customer_cost

  destination_carrier_cost
  destination_reseller_cost
  destination_customer_cost

your /var/log/ngcp/rate-o-mat.log shows no recents error but eventual
warnings like "Missing source/destination_provider_id ..".

1. if source_user_id != "0" and destination_user_id != "0" its an on-net
call. in this case source/destination_provider_id refer to the subscriber's
reseller contract ids.

2. if source_user_id != "0" and destination_user_id == "0" it's a call
leaving ngcp by a peer interconnect, and destination_provider_id shows the
peering group's "peering contract" id.

3. if source_user_id == "0" and destination_user_id != "0" it's a call
arriving ngcp from a peer interconnect, and source_provider_id shows the
peering group's "peering contract" id.

4. if both source_user_id and destination_user_id are "0" it's a transit
call, which won't get rated (i.e. the CDR is set to rating_status="ok", but
no call fees will be calculated). there is no log warning for this case.

if your calls are of type 2 and 3 above, i suggest you check your peering
group's contracts: if they all have suitable billing profiles attached, i.e.
those profiles use nonzero fee's with aligned "in" and "out" directions.

if the calls you mention are of type 4, what you encounter is the regular
behaviour of the current rate-o-mat implementation.

let us know if this helps.

regards, rene