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

Vodia Now Integrates with Grafana®

Vodia now integrates with Grafana Labs®' technology to enhance observability in installations, addressing the needs of critical infrastructure environments like emergency services and healthcare. By integrating with Grafana's® scalable metrics, logs and traces solutions, Vodia ensures secure and reliable communication systems. This integration enables geo-redundant deployment and proactive incident response, supporting Vodia's commitment to IT security. Vodia also provides extensive support for implementing, monitoring and auditing these high-availability communication solutions, ensuring seamless integration with various platforms and adherence to stringent data protection measures.

June 19, 2024

The End of the Line

NEC's exit from the on-premise telephone systems market has left many customers at a crossroads, seeking effective alternatives. Vodia provides a seamless transition to our on-premise PBX, utilizing a proven migration path and advanced VoIP technology. In recent migrations, we observed the deep-rooted reliance on "lines" within NEC systems. Our approach ensured a smooth adaptation, teaching users to transition from the old two-step process to a more intuitive VoIP interface. VoIP eliminates physical lines, offering a robust, efficient, and user-friendly communication solution. With Vodia, your organization can continue to communicate effectively, ensuring business continuity and enhanced communication capabilities.

June 10, 2024

#SmartCommunication For Successful Learning

Effective communication is pivotal in enhancing learning experiences. Collaboration between educators and parents fosters a positive environment for students. Amidst the digitalization of education, prioritizing #SmartCommunication is essential for seamless integration of technology into teaching and learning. As learning methods evolve, educators are transforming into facilitators, guiding learners towards acquiring, applying and sharing knowledge. The role of assessment is also evolving, emphasizing the application and utilization of knowledge. While technology shapes the future of education, personal interaction remains vital.

June 7, 2024