[Spce-user] applying NCOS to all users

Andreas Granig agranig at sipwise.com
Thu Jan 24 04:59:20 EST 2013


Hi,

As you can see, you actually HAVE two CDRs, one for the inbound call, 
one for the outbound one.

The real issue here is that the second CDR (the one with id 111532) is 
missing the correct source_user_id (the UUID of the forwarder), so it 
doesn't get rated correctly.

Can you try to apply the change I've proposed in my previous mail and 
retry this scenario?

Andreas

On 01/23/2013 08:22 PM, Joan Cifre (ibred) wrote:
> Ok done!!!
>
> mysql> select * from accounting.cdr where call_id =
> '5cccf9732b0cedac110509986c7a9920 at 55.55.55.165:5060'\G
> *************************** 1. row ***************************
>                                  id: 111532
>                         update_time: 2013-01-23 05:23:20
>                      source_user_id: 0
>                  source_provider_id: 0
>       source_external_subscriber_id:
>         source_external_contract_id:
>                   source_account_id: 0
>                         source_user: n555555243
>                       source_domain: voip.ibreddigital.net
>                          source_cli: 34555555243
>                         source_clir: 1
>                 destination_user_id: 0
>             destination_provider_id: 5
> destination_external_subscriber_id:
>    destination_external_contract_id:
>              destination_account_id: 0
>                    destination_user: 0018005555111
>                  destination_domain: 55.55.55.165
>             destination_user_dialed: 0018005555111
>                 destination_user_in: 0018005555111
>               destination_domain_in: voip.ibreddigital.net
>                      peer_auth_user:
>                     peer_auth_realm:
>                           call_type: cfb
>                         call_status: ok
>                           call_code: 200
>                           init_time: 1358914963.394
>                          start_time: 1358914967.340
>                            duration: 28.590
>                             call_id:
> 5cccf9732b0cedac110509986c7a9920 at 84.232.7.165:5060
>                        carrier_cost: 0.00
>                       reseller_cost: 0.00
>                       customer_cost: 0.00
>                   carrier_free_time: 0
>                  reseller_free_time: 0
>                  customer_free_time: 0
>              carrier_billing_fee_id: NULL
>             reseller_billing_fee_id: NULL
>             customer_billing_fee_id: NULL
>             carrier_billing_zone_id: NULL
>            reseller_billing_zone_id: NULL
>            customer_billing_zone_id: NULL
>                 frag_carrier_onpeak: NULL
>                frag_reseller_onpeak: NULL
>                frag_customer_onpeak: NULL
>                       is_fragmented: NULL
>                            rated_at: 2013-01-23 05:23:20
>                       rating_status: ok
> *************************** 2. row ***************************
>                                  id: 111533
>                         update_time: 2013-01-23 05:23:20
>                      source_user_id: 0
>                  source_provider_id: 5
>       source_external_subscriber_id:
>         source_external_contract_id:
>                   source_account_id: 0
>                         source_user: anonymous
>                       source_domain: 55.55.55.165
>                          source_cli: anonymous
>                         source_clir: 1
>                 destination_user_id: be1f21fb-2fc0-423d-9cf1-709f2217ccb0
>             destination_provider_id: 1
> destination_external_subscriber_id:
>    destination_external_contract_id: ibred
>              destination_account_id: 3
>                    destination_user: n555555243
>                  destination_domain: voip.ibreddigital.net
>             destination_user_dialed: 555555243
>                 destination_user_in: 34555555243
>               destination_domain_in: 141.105.55.55
>                      peer_auth_user:
>                     peer_auth_realm:
>                           call_type: call
>                         call_status: ok
>                           call_code: 200
>                           init_time: 1358914963.332
>                          start_time: 1358914967.340
>                            duration: 28.590
>                             call_id:
> 5cccf9732b0cedac110509986c7a9920 at 84.232.7.165:5060
>                        carrier_cost: 0.00
>                       reseller_cost: 0.00
>                       customer_cost: 0.00
>                   carrier_free_time: 0
>                  reseller_free_time: 0
>                  customer_free_time: 0
>              carrier_billing_fee_id: NULL
>             reseller_billing_fee_id: NULL
>             customer_billing_fee_id: NULL
>             carrier_billing_zone_id: NULL
>            reseller_billing_zone_id: NULL
>            customer_billing_zone_id: NULL
>                 frag_carrier_onpeak: NULL
>                frag_reseller_onpeak: NULL
>                frag_customer_onpeak: NULL
>                       is_fragmented: NULL
>                            rated_at: 2013-01-23 05:23:20
>                       rating_status: ok
> 2 rows in set (0.00 sec)
>
>
>
>
>
> El 2013-01-23 19:59, Andreas Granig escribió:
>> Hi,
>>
>> Please provide the CDRs for this call, fetched like this:
>>
>> mysql> select * from accounting.cdr where call_id =
>> '5cccf9732b0cedac110509986c7a9920 at 55.55.55.165:5060'\G
>>
>> (note the \G instead of the semi-colon for better readability).
>>
>> From what I can see, the 302 is converted to a CFB, but the
>> callee-uuid is not carried over to the new caller-uuid. You should
>> still have two CDRs with the correct CLIs though, as I can see from
>> the logs that two call legs are written.
>>
>> I'd say (without having reproduced the scenario), a fix would be to
>> search for this line in proxy.cfg.tt2:
>>
>> if(!get_redirects("1:1"))
>>
>> and add these two lines right before that line:
>>
>> $(avp(s:caller_uuid)[*]) = $avp(s:callee_uuid);
>> $(avp(s:callee_uuid)[*]) = $null;
>>
>> This should do the trick, but let's see first what the content of your
>> CDRs actually is.
>>
>> Andreas
>>
>> On 01/23/2013 05:30 PM, Joan Cifre (ibred) wrote:
>>> Hi all,
>>> here I send a log with a call that comes from outside as anonymous to
>>> 555555243 and is forwarded to 0018005555111. The ip 55.55.55.165 is our
>>> providers server and 141.105.55.55 is our ngcp server. This is all the
>>> lines with same Caller-id but I don't know if after forwarding the
>>> caller id changes. This call is marked in CDR as an incoming call of 29
>>> seconds, but no outgoing call.
>>>
>>>
>>> El 2013-01-23 14:49, Daniel Tiefnig escribió:
>>>> On 01/23/2013 01:24 PM, Joan Cifre (ibred) wrote:
>>>>> *Not in 2.6 version! I plan to upgrade to 2.7 but not now, and this
>>>>> is urgent for me!*
>>>> Oh, I see. You could change your Peering Rules instead, to prevent
>>>> certain destinations from being reachable at all.
>>>>
>>>>> *Our problem is that a fraudulent user configures a forwarding in a
>>>>> phone (NOT in the NGCP) and then calls from outside to this phone.
>>>>> The call is fowarded to an international number. Calls come from a
>>>>> "anonymous" or "unknown" user and are forwarded with a Caller
>>>>> "anonymous" or "unknown". In CDR only Incoming calls are seen.
>>>>> Forwarded calls does not have a known Caller so they do not appear
>>>>> on CDR.
>>>> The calls should still appear in the CDRs, as they are written with the
>>>> username and the IDs of the forwarding subscriber. A subscriber
>>>> needs to
>>>> authenticate its invites, so we always know where a local call is
>>>> coming
>>>> from, and that information is written to the CDRs. Unless you have
>>>> changed the configuration of course.
>>>>
>>>> br,
>>>> daniel
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> http://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>




More information about the Spce-user mailing list