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

Strengthening PBX security: Passkeys and the Vodia Phone System

Vodia PBX strengthens security with passkeys, giving users and administrators a secure, passwordless login method that eliminates many vulnerabilities tied to traditional credentials. Passkeys use public key cryptography, storing the private key on the user’s device and the public key on the server, making them resistant to phishing and credential theft. By reducing reliance on passwords, Vodia minimizes the attack surface in cloud environments and makes authentication simpler and more secure, while ensuring a smoother, faster login experience for all users.

October 21, 2025

Why Vodia is the Ideal PBX for Microsoft Environments

Many organizations rely on Microsoft as the foundation of their daily operations, but their communication systems often exist in parallel rather than in harmony. Vodia closes that gap by bringing telephony into the same environment where teams already work, turning separate systems into one connected structure. This approach removes friction between platforms, simplifies management, and gives IT teams better control and visibility over daily communication. It also creates a more seamless experience for employees, reduces operational overhead, and builds a stronger, more flexible foundation that supports growth, collaboration, and long-term scalability.

October 17, 2025

Vodia to Attend CVxExpo 2025 in Glendale, Arizona

Vodia will be attending CVxExpo 2025 in Glendale, Arizona, from November 3–5. Sales Engineer Eric Altman will be on site to meet with current and prospective partners, demonstrating how Vodia’s PBX solutions can strengthen technology roadmaps for 2026. This year, Vodia highlights new integrations with ActiveCampaign, Freshdesk, HighLevel, Microsoft 365, Microsoft Presence, monday.com, and Odoo Cloud, along with enhanced call center capabilities such as agent activity dashboards, call recordings, and transcription features. Partners and attendees can schedule meetings with Eric to learn more about scalable, feature-rich, and cost-effective telecommunications solutions built for enterprises and SMBs.

October 14, 2025