Tech

MongoDB CDR

Published on:

August 18, 2015

Veröffentlicht am:

August 18, 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

Vodia: An Integration Paradise

Vodia redefines B2B platforms with its seamless integration solutions. Vodia's complimentary services facilitate effortless connections to communication systems, amplifying efficiency and refining workflows. Whether it's interfacing with industry-leading software providers, bridging with Microsoft Teams, or integrating chatbots, Vodia ensures comprehensive compatibility. Communication becomes the catalyst for streamlined processes, catapulting businesses into a realm of heightened productivity. Embrace the future with Vodia, where innovation and integration converge to shape a transformative business landscape.

February 22, 2024

Exceedingly Well: The Vodia Healthcare Services Communications Solution

Vodia's specialized phone system for healthcare optimizes communication, reducing wait times and simplifying staff tasks while ensuring data security under HIPAA and GDPR regulations. With features like appointment scheduling and Smart Fax, it enhances patient care and streamlines operations. Its flexible integration options make it a cost-effective solution for telemedicine, supported by a team of experts committed to delivering excellence in healthcare communication solutions.

February 19, 2024

Celebrating Two Decades of the Pulver Order

The Pulver Order, approved by the FCC in 2004, legalized VoIP, marking a pivotal moment in telecommunications history. It facilitated the integration of voice and data networks, revolutionizing communication and fostering a new era of innovation. This landmark decision unleashed a wave of entrepreneurial energy, propelling technologies like SIP into prominence and paving the way for the modern cloud phone systems we rely on today. As we commemorate this milestone, we celebrate the enduring legacy of the Pulver Order in shaping the dynamic landscape of communication.

February 12, 2024