Tech

MongoDB CDR

Published on:

August 19, 2015

Thus the move with MongoDB. Although it is latest technology (and maybe just because of that), writing natively into the database was actually relatively simple. MongoDB can deal with very large amounts of data, so the PBX does not have to bother with it. Down the road we might be even able to use the DB for reading as well, e.g. when the user is using the call history from the web interface.

Moving from CPE deployments to hosted PBX does not only put additional stress on the overall stability of the system; it also adds a lot more call data records (CDR) to be stored. Our old approach to store the CDR locally in our own little database was good for a few thousands records. However as we go forward, we are hitting the millions of records.

A simple, file based database cannot handle that any more.http://vodia.com/documentation/cdr is like a history book on CDR. Originally we started with SOAP, which was at the time a kind of cool technology especially because it was sent using HTTP—a kind of waste at the time. Due to industry demands we added the TCP-based simple CDR, a primitive technology that came from the RS-232 times with lots of problems with the field lengths and special characters.

With the increasing popularity of REST and JSON we added a JSON-based record that was again based on HTTP, which was already pretty cool. However there was still glue logic necessary to store the records in a database. Thus the move with MongoDB. Although it is latest technology (and maybe just because of that), writing natively into the database was actually relatively simple. MongoDB can deal with very large amounts of data, so the PBX does not have to bother with it. Down the road we might be even able to use the DB for reading as well, e.g. when the user is using the call history from the web interface.

To use the new feature, you need to set up the MongoDB on a server. If you set it up on the same machine, things are simple; by default connections coming from the localhost port don’t require any additional setup. If you run the DB on a separate server, you must make sure that the authorization is set up properly; you don’t want just anybody have access to your CDR. The PBX does not support authentication mechanisms for MongoDB or even encryption. It is your responsibility to make sure that only the PBX can access the database.

The schema for the URL is like this: “mongodb://server:port/database/table”. The server must be an IP address or “localhost” for the loopback address “127.0.0.1”. The port defaults to 27019 which is currently the standard MongoDB port; however we recommend to explicitly specify the port. The database string tells the server where to store the CDR; this string may contain the variable “{domain}” which is replaced with the name of the domain. The table name is a string that tells the PBX where to store the CDR. The feature will be available in 5.3. Those who can’t wait can try select 5.2.7 builds which also have it compiled in already.

Latest Articles

View All

The Vodia PBX Now Integrates with ActiveCampaign

Vodia’s latest integration with ActiveCampaign brings together a powerful cloud PBX system and a leading customer experience automation platform. This integration enables businesses to automatically track and manage customer interactions by creating and updating contacts based on call activity, recording detailed call information, and linking calls to the appropriate users within ActiveCampaign. By combining Vodia’s advanced telephony features with ActiveCampaign’s AI-driven marketing and sales automation tools, companies can deliver more personalized experiences, improve team productivity, and drive growth through smarter, data-backed communication.

May 29, 2025

Five-Star Hospitality Communications: Fanvil IP Hotel Phones and the Vodia Phone System

Hotels today need more than luxury amenities—they need smart, reliable communication systems that enhance the guest experience and streamline operations. The combination of Vodia’s powerful VoIP PBX and Fanvil’s new IP Hotel Phones delivers exactly that: seamless in-room communication, fast response to guest requests, and integration with leading PMS. With features like programmable keys, built-in Wi-Fi, AP mode, and USB charging, Fanvil’s devices are purpose-built for hospitality, while Vodia’s system brings automation, multilingual support, and cost-efficient call handling to the table.

May 27, 2025

Smarter Hotel Communication: Vodia PBX Now Integrates with Shiji PMS

Vodia now offers seamless integration with the Shiji Property Management System (PMS), empowering hotels to streamline operations, automate routine tasks, and enhance guest experiences through smarter communication. From check-in to check-out, the integration connects telephony with front desk functions—enabling features like personalized extension setup, automated call billing, room status updates via maid codes, and effortless room changes. With a secure real-time interface, no complex middleware, and support for cloud, on-prem, or hybrid deployments, the Vodia-Shiji solution is built for reliability, scalability, and modern hospitality.

May 23, 2025