[Spce-user] Incoming call CDR

[Danny Cappellari]

Hi guys, Matthias' solution is ok because the billing of incoming calls cannot be on-net but only from external CLIs

 
 ----
Cappellari Danny
Responsabile Supporto Tecnico | ConnectLife S.r.l

Tel. +39 045 2081019 | Mobile: +39 392 4206436
cappellari at connectlife.it



Questo documento è formato esclusivamente per il destinatario. Tutte le informazioni ivi contenute, compresi eventuali allegati, sono da ritenere esclusivamente confidenziali e riservate secondo i termini del vigente D.Lgs. 196/2003 in materia di privacy e del Regolamento europeo 679/2016 – GDPR-  e quindi ne è proibita l’utilizzazione ulteriore non autorizzata. Se avete ricevuto per errore questo messaggio, Vi preghiamo cortesemente di contattare immediatamente il mittente e cancellare la e-mail.






Da: "Matthias Hohl" <matthias.hohl at telematica.at>
A: "'Vincent Dubois'" <vdubois at b2b2c.com>, "'Danny Cappellari'" <cappellari at connectlife.it>, "undefined" <spce-user at lists.sipwise.com>
Inviato: lunedì 28 aprile 2025 17:31
Oggetto: AW: [Spce-user] Incoming call CDR



Hey Vincent,

yes you are sure, I have forgotten about on-net calls.

There you need to look bit deeper and take <source_customer_cost> and <dest_customer_cost> from the same CDR line to bill a call from subscriber A to subscriber B.

But basically the identification of inbound and outbound is true. Just the on-net calls need to be fished out with another logic of source/dest customer costs.

 

 

Von: Vincent Dubois <vdubois at b2b2c.com>
Gesendet: Montag, 28. April 2025 14:38
An: 'Danny Cappellari' <cappellari at connectlife.it>; spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Incoming call CDR



Not exactly true, what he suggested would make you miss some inbound calls. You can not separate in and out CDR for the simple reason that a CDR could be both.

 

If one of your customers could call another one of your customers, then the same CDR will be outgoing for one customer and incoming for the other customer.

 

You should have a system that checks every CDR, and bill the source_user and/or destination_user(_in) depending on your rules.

If you need to separate them, you will have to make duplicates sometimes.

 

Vincent Dubois | Analyste programmeur

B2B2C

514-908-5420

 

From: Matthias Hohl <matthias.hohl at telematica.at>
Sent: April 28, 2025 6:14 AM
To: 'Danny Cappellari' <cappellari at connectlife.it>; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Incoming call CDR

 

	

You don't often get email from matthias.hohl at telematica.at. Learn why this is important

	

CAUTION : External Mail. Do not click on links or open attachments you do not trust.
ATTENTION : Courriel externe. Ne cliquez pas sur des liens et n'ouvrez pas de pièces jointes auxquels vous ne faites pas confiance.



You can easily idenfity a incoming and outcoming call by the tables in the CDR file.
so there is basically no separation needed.

 

 

OUTBOUND:

               IF

                              "<source_account_id>" IS NOT "0"

 

 

INBOUND:

               IF

                              "<source_account_id>" IS "0"

               AND

                              "<destination_customer_cost>" IS NOT "0"

                              OR

                                            "<destination_customer_cost>" IS "0"

                              AND

                                            "destination_customer_free_time>" IS NOT "0"

 

 

 

 

Von: Danny Cappellari via Spce-user <spce-user at lists.sipwise.com>
Gesendet: Montag, 28. April 2025 10:57
An: spce-user at lists.sipwise.com
Betreff: [Spce-user] Incoming call CDR



Hello, we have to bill some of our customers for incoming calls. At the moment outgoing and incoming calls are recorded on the same CDR files. Is it possible to separate incoming calls into specific CDR files?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20250428/e68ddf4a/attachment.htm>