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

How the Hospitality Industry Can Exceed Guest Expectations

As hotels prepare for the upcoming travel season, many are rethinking their communication systems to better meet modern guest expectations. Vodia CEO Dr. Christian Stredicke explains how VoIP, AI, and app-based control are key to delivering smarter, more personalized service. Guests now expect mobile-first experiences—whether for check-in, room controls, or contacting hotel staff. Vodia’s customizable communication solutions help hotels automate tasks, streamline operations, and boost guest comfort while reducing costs. With robust security and seamless integration into existing hotel management systems, Vodia enables hotels to move beyond outdated hardware and deliver the connected, high-quality experience today’s travelers demand.

April 23, 2025

Seatrade Cruise Global 2025: Communications Revolution Onboard - What Cruise Experts Need to Know

At Seatrade’s 40th anniversary, Vodia and Lufthansa Industry Solutions showcased the Vodia Maritime Communication Server and the new CruisR World App—purpose-built for next-generation cruise ships and cost-effective retrofits. Key themes at the event included AI-powered language translation, breakthrough satellite connectivity, UC platforms, and advanced emergency protocols. These innovations enable cruise lines to streamline operations, personalize guest experiences, and meet growing expectations for safety and connectivity. As the cruise industry evolves, Vodia’s solutions position communication teams to lead with smarter, more human-centric technology at sea.

April 23, 2025

Real-Time Media Streaming in Vodia PBX: AI, Call Transcription, and Security in V69.5.6 | Webinar Recording Now Available

Vodia is excited to share the recording of our April 8, 2025 webinar on "Real-Time Media Streaming in Vodia PBX: AI, Call Transcription, and Security in V69.5.6." In this session, we explore how AI, call transcription, and security have become core features in the latest version of our PBX. We dive into the practical benefits of AI, including how it improves business communication with real-time transcription, enhances security with advanced features, and streamlines workflows through integrations like OpenAI and Microsoft Teams. Watch the recording to learn how these innovations can transform your business communications and boost efficiency.

April 16, 2025