Connector Equipment Import CDR
This module allows to import the CDR data from the Netsapiens backend as Odoo Analytic Lines.
- On Contacts/Phone Rates, import data
- Create a Sales Order, and select a correctly configured Subscription Product.
- Confirm the Sales Order. This will:
- Assign a new Analytic Account to the SO
- Create a Subscription with this Analytic Account
- Create an Agreement with this Analytic Account
- Edit Agreement
- Add Service Profile
- On Service Profile, assign Equipment
- On Equipment, assign Equipment Backend
- On Equipment Backend, configure connection and Products to import
- On Service Profile, run "Import CDR"
The "Import CDR" will query call records based on the query configuration in the Service Profile: the Query Type (User, Domain) and the Query Parameter to use.
To be able to use the generated Analytic Lines for billing, the sale_timesheet module needs to be installed, and the Products generated by the "Import CDR" should be configured.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Import call detail records (CDR) from a Netsapiens phone backend into Odoo as analytic lines, so call minutes can be billed through timesheets. Users configure the query and product mapping, then run the import manually or daily.
This module connects Odoo to a Netsapiens phone system and turns call records into billable analytic lines.
On a Service Profile you get new fields: Query Type (by Domain or by User), Query Parameter, and Last CDR Sync Date, plus an "Import Now" button. Pressing it (or the daily scheduled job) asks the backend for call records since the last sync, keeps only outbound calls, and matches each dialled number against patterns configured on the backend.
On the Backend Equipment you can add a list of Products, each with a regular expression pattern and a sequence. The first matching pattern decides which product the call is billed to. International calls also get a phone rate looked up to compute an amount; otherwise the amount is zero and only the minutes are recorded.
Results are written as analytic lines on the analytic account of the linked Agreement, with the call count in the reference, the duration in minutes, and the product. The last sync date is updated so the next run only fetches new calls. If no analytic account is found, an error is raised.
A menu "Backend Equipments Productline" under Maintenance configuration lets you manage these product/pattern mappings. A daily cron named "Import CDR" is provided but is inactive by default.
Depends on
Menus it adds
Models and fields (3)
- backend.equipment · extends an existing modelsync_schedule, product_line_ids (Products)
- agreement.serviceprofile · extends an existing modelquery_type, last_cdr_sync (Last CDR Sync Date), query_parameter
- backend.equipment.product_line · new modelname, pattern (Pattern), sequence (Sequence), backend_id
Text generated by AI (DeepSeek) from reading the Odoo 12.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/vertical-isp.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.