TELCO CDRs

Abstract

By sharing your CDRs you help us to help you and your subscribers.

Our scoring algorithm will be able to process your network activity and detect nuisance calls active only on your network.
We’ll be able to monitor the call activity and detect false positive and take the appropriate measure near realtime.
We’ll provide various statistics regarding the call filtering on your network.
- CSV reports

CDRs are semi-anonymized. We don’t need to know the B_NUMBER. A salted HASH of this value or a constant SUBSCRIBER_ID is enough.

Custom scoring is not shared between our customers.

Custom scoring is hosted on TELCO network instance and belongs to TELCO only

CDRs are deleted each 15 or 30 days

Required fields

Fields order is not relevant, first line should contains the HEADER.

FIELDS	DESCRIPTION	MANDATORY

FIELDS	DESCRIPTION	MANDATORY
CALL_UNIQ_ID	An uniq call identifier. This information is needed to avoid duplicate information during the storage period of the CDRs. Data are purged each 1st of the month. VALUES Unique call identifier	YES
CALL_SETUP	Timestamp when the call is placed	YES
CALL_START	Timestamp when the call is	YES
CALL_END	Timestamp when the call is terminated	NO
A_NUMBER	Information related to the Caller VALUES Presentation number Sip From	YES
CALLER_ID	This filed is a legacy from ISDN / PSTN era where some devices provided more than one number VALUES Central number	NO
SUBSCRIBER_ID	We need a constant uniq identifier for each subscriber. This information can be derived from HASH(SALT+B_NUMBER) Subscriber ID IMEI Any uniq id related to the subscriber VALUES A UNIQ anonymised identifier	YES
ORIGIN	Information regarding the call’s last origin. VALUES Sip P-Charging-Vector orig-ioi	NO
SIP_VIA	SIP Via Header information	NO
SIP_PAI	SIP P-Asserted-Identity	NO
SIP_DIVERSION	Information regarding the Number Diverting / Redirecting / Forwarding a call SIP Diversion Header PSTN Redirecting Number Multiple diversion numbers should be separated by a non-CSV character	NO
CALL_SIP_CODE	SIP Status Code	NO
CALL_BLOCKED	Has the call been blocked after the call verification process? VALUES true false	YES
CALL_BLOCKED_REASON	Detailed reason regarding the call verification process VALUES NO (NO MATCH) KSPAM (KATIA SPAM) KRULE (KATIA RULE) KPREFIX (KATIA PREFIX) KSPOOFING (KATIA SPOOFING) SWL (SUBSCRIBER WHITELIST) SBL (SUBSCRIBER BLACKLIST) TWL (TELCO WHITELIST) TBL (TELCO BLACKLIST) T….. any others TELCO’s reasons	YES

Data exchange

SFTP

1. Upload

We can setup an access on our exchange server (SFTP)

Servers
- cdr.katia.ch
- ch.cdr.katia.ch
Required : provide a public SSH key

2. Download

We can download the CDRs directly from your server.

we will provide our pubic SSH key