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

Get The Support You Need Easily Through The Vodia Help Center On Jira

Vodia support is now easier to access through the Vodia Help Center on Jira, giving partners and customers a centralized platform to submit technical support tickets, ask sales or licensing questions, and suggest new features. With a valid license key, users can open detailed requests and track their status in one place. The portal also brings together Vodia documentation, the PBX API, and the Vodia forum, making it the go-to resource for everything Vodia. Whether you're troubleshooting, planning an upgrade, or just need guidance, the Help Center is designed to streamline your experience and connect you with the right support faster.

August 7, 2025

Vodia Attends ChannelCon 2025 in Nashville

At ChannelCon 2025 in Nashville, Vodia Sales Engineer Eric Altman engaged with MSPs and IT professionals to explore how AI is shaping the future of managed services. He emphasized that ChannelCon remains a valuable space for building strong vendor-partner relationships, especially as AI continues to dominate industry conversations. Altman noted how Vodia is helping MSPs unlock greater flexibility by combining powerful PBX features with AI-driven capabilities like dynamic call analytics, customized call flows, and automated performance reporting. He also highlighted Vodia’s recent launch of prepaid cloud instances on AWS, DigitalOcean, and Microsoft Azure, designed to streamline deployment for MSPs without infrastructure or licensing delays.

August 5, 2025

5 Reasons to Choose a Business Phone System with Working Hours

A business phone system with working hours gives companies a practical way to protect employee well-being while maintaining high service standards. With Vodia PBX, employees can set individual schedules based on their time zone, forward calls to mobile devices during working hours, and route calls after hours to voicemail, queues, or designated team members. Features like Do Not Disturb, call routing by day of the week, and presence visibility let teams manage availability without sacrificing responsiveness. Whether it’s handling peak-hour demand with call distribution or disconnecting during evenings and holidays, Vodia helps organizations support work-life balance without compromising communication quality.

August 4, 2025