[Spce-user] Peer to peer transit calls - CDRs not properly mediated/rated?

[Daniel Grotti]

Hi Gavin,
to investigate this issue please start from the following:

1. CDR
mysql> select * from accounting.cdr where
call_id="35585-3600172261-853630 at MSX28.foobar.com" \G;

2. Check inside the billing_fee_id matched.

3. check the fee details:
mysql> select * from billing_fees_history where id=<billing_fee_id>\G


So you can see which billing profile and fees have been matched and
which cost has been applied.


Daniel



On 02/04/2014 10:10 AM, gavin.sweet at skyracktelecom.com wrote:
> <Nudge>
> 
> Any thoughts on why carrier rating might not work as expected...?
> 
> Thanks,
> Gavin
> 
> ----- Reply message -----
> From: "Gavin Sweet" <gavin.sweet at skyracktelecom.com>
> To: <spce-user at lists.sipwise.com>
> Subject: [Spce-user] Peer to peer transit calls - CDRs not properly
> mediated/rated?
> Date: Fri, Jan 31, 2014 17:34
> 
> Hi all -
> 
>  
> 
> We’ve been running Sipwise for a long time now with no problems
> generating correct CDR records for subscriber calls (applying billing
> profiles etc).
> 
>  
> 
> We have recently started operating in a transit type model for some
> peers and are having a problem with CDRs for peer to peer transit calls.
> 
>  
> 
> Calls generate CDR records but they do not contain the expected/correct
> data in the cost and zone fields, they come out as:
>  '0.00','0.00','onnet','','platform internal','',
> 
>  
> 
> E.g.(anonymised):
> 
> '1002396','2014-01-31
> 15:56:44','0','2','','','','0','02391111111','xxx.yyy.zzz.195','442391111111','0','','0','7','','','','','0','aaa.bbb.ccc.25','441152222222','109.239.110.182','','','call','ok','200','2014-01-31
> 15:51:02.864','2014-01-31
> 15:51:07.780','331.830','35585-3600172261-853630 at MSX28.foobar.com','ok','2014-01-31
> 15:56:44','0.00','0.00','onnet','','platform
> internal','','01152222222','0','0'
> 
>  
> 
> These peering contracts are all setup using exactly the same billing
> profile as that used for the carrier profile in the subscriber calls
> that do work properly, so I cant see that it is a problem with the profile.
> 
>  
> 
> For instance the destination fee profile that should match the above is
> configured as  ^4411[5].{7}$  which works everywhere else for such a call.
> 
>  
> 
> Any one seen a similar problem?
> 
>  
> 
> Cheers
> 
> Gavin
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>