User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Today, I have published in OKay's RPM repository RPMs for the Enhanced CDR Importer (ECI) for FusionPBX 1.0.1. The ECI is a drop-in replacement for the CDR importer that comes with FusionPBX. It has a plugin architecture allows you to easily export the CDR into third-party software such as Helpdesk, CRM or Bigdata applications.

RPM's are available for Centos 6 and 7. And you can find it if you type yum search fusionpbx-enhanced-cdr-importer.

The ECI requires FusionPBX 4.1 or better.



User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

It is almost a direct yes answer. SSL certificates protect the integrity and privacy of your service. If you google a little, you will find you can create your own SSL certificates yourself. However, using a home-made it is not always the best solution.

Self-signed home-made certificates offer the same level of protection than a commercial one. The difference is that certificate authorities from commercial certificates are already imported in most of the devices. Which it enables a trust relationship when verifying the certificate. Commercial certificates have some levels of review, therefore when getting a certificate for domain, there could be a trust relationship as depending the kind of commercial certificate you were getting, some identity reviews were done.

On the other hand, there are multi-domain, wildcard or single FQDN certificates. Multi-domain certificates take advantage of the multi DN capability of SSL certificates and allow you to have for example and domains together. Wildcard certificates are those that accept anything on the hostname part of the domain, for example, and will be accepted in the same certificate.

I will write about the different options and the implications of using an SSL certificate.


User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Provisioning is the fact of letting an IP Telephone to pull its configuration form an external entity. When a telephone pulls the information, it will at least this information:

  • SIP Credential
  • Codec configuration
  • Admin access

Some other phones are more advanced and they can pull more information, such as shortcuts, display information, tunes, SIP/RTP parameters, etc.

CDR Importer is the element that allows pushing your call details into a database for a post-mortem analysis. For example, Billing.

FusionPBX as a project offers you these things. So, having a Provisioning and CDR Importer server sounds quite easy if you are talking about stand-alone deployments, but in this case, I will write about something more interesting: cluster deployment. Regardless of you have a high-availability or load-balanced cluster, there is a point where you have enough load that you need to take out non-essential VoIP functions out of the main SIP nodes to keep load and service quality at an acceptable level. Moving out of the SIP Cluster Nodes functions such as provisioning or CDR importing is one of the first steps you should do.