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

Call Forwarding Glitches

In the late 1980s, prank calls were a common form of entertainment but often caused confusion, similar to today’s call forwarding glitches. Recently, a client migrating to a new PBX system experienced disruptions when users mistyped numbers for call forwarding. While user errors are common, there's a bigger concern: calls being misdirected to emergency numbers or costly lines, especially since many VoIP phones lack security features. Solutions include restricting call forwarding to internal numbers, blocking access or allowing only specific, pre-approved numbers. Ultimately, balancing control over settings is essential to prevent glitches while keeping systems user-friendly.

October 8, 2024

Amazon Announces Full-Time RTO; Vodia PBX Users Continue to Work from Anywhere

Amazon's recent decision to enforce a full-time return-to-office (RTO) policy contrasts with the growing trend of remote and hybrid work. While larger companies like Amazon can afford this shift, smaller businesses benefit from flexible WFH models. Vodia PBX enables companies to thrive remotely, offering a feature-rich, cloud-based phone system that connects teams from anywhere. With seamless CRM integration and powerful communication tools, Vodia supports organizations in their digital transformation. Learn why more than half a million users worldwide trust Vodia for their business communication needs.

September 27, 2024

Vodia Wants to Help Your MSP (Managed Service Provider) Grow

Managed Service Providers (MSPs) are essential partners for Vodia, as we collaborate closely to deliver the most innovative B2B phone systems in the industry. We continuously enhance our cloud PBX platform to maintain our leadership in cloud communications, making us the ideal choice for MSPs. We focus on both our exceptional software and building strong relationships with our partners, always seeking growth opportunities for them. As customer expectations and competition increase, we suggest MSPs leverage technologies like AI, automation and enhanced security to drive growth.

September 11, 2024