Page Comparison

<div id="fb-root"></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

<div class="fb-like" data-href="https://confluence.wildix.com/x/GwKmB" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div>

...

Introduction

We know in Wildix it is very easy to create a network of several systems. Once the network is created, it is completely transparent to end users whether they are in a system that is part of a network or not. The systems on the network appear as a single system to end users. When in a WMS Network environment, there is even a filter in CDR-View to filter reports based on which PBX the activity happened on. See the filter in the screenshot below. 

Image Added

However, there is some configuration needed in order to have the filter to work.  Without such configuration the systems on the WMS Network can only access their own information. The purpose of this document is to explain the needed configurations to have a unified CDR-View in a WMS Network.

...

Here we take advantage of the fact that, once part of a WMS Network, systems are part of a secure intranetwork. In this scenario we have 2 systems: 

Image Added

As you can see, systems communicate to each other using the displayed IP addresses. For this example, we use system 2211000025eb (IP 5.15.0.1) as the database server.

...

• On the 5.15.0.1 server, login to mysql console (Password is wil01dix): 

  Code Block
  $mysql -u root -p Enter password:

  
  

• Execute the following command: 

  Code Block
  > show grants;

  
  

  Image Added
  

  
  

• As you can see in the previous picture, the login for the root account is only available from the localhost. We need to execute the following command in order to enable access from remote locations: 

  Code Block
  >GRANT ALL PRIVILEGES ON *.* TO 'root'@'5.15.0.3' IDENTIFIED BY PASSWORD '*47C562035B611FE7E0CD4CF0F58AEC9EDEBF20E3' WITH GRANT OPTION;

  
  

...

• To apply changes immediately, execute following command on mysql cli: 

  Code Block
  >FLUSH PRIVILEGES;

  
  

• Now you can logout of mysql console by executing: 

  Code Block
  >quit

  
  

• There is one more step needed. By default mysql only accepts requests from the loopback. To finalize the enabling of remote connections, open the next config file with some text editor: 

  Code Block
  $vim /etc/mysql/mariadb.conf.d/50-server.cnf

  
  

• Search for a line with “bind-address = 127.0.0.1” and add a # to the beginning. This comments out this line and no longer restricts requests only to those that come on the loopback interface 

  
  

  Image Added

• Save and close the file, then execute: 

  Code Block
  $systemctl restart mysqld.service

  
  

...

And entering any password (invalid) you should see a message like the following: 

Image Added

If you see the previous message, you can proceed to configuring the clients.

...

Configuring the rest of the Wildix systems to use the server database is actually pretty easy (provided the server is ready). By default your Wildix system uses a local database. We just need to point to the remote server instead of the localhost. We accomplish this by editing the file /etc/callweaver/cdr_mysql.conf: 

Image Added

As you can see in the previous picture, Wildix is pointing to the localhost (127.0.0.1). You just need to change it to the server IP address, 5.15.0.1 in this example: 

Image Added

In the previous picture you can note that, besides the hostname, we also changed the timeout. This is a good idea since clients won't be using the localhost and surely the access to a remote DB will take more time than for a local DB.

...

Once the configuration is complete, you are able to see events for any system from any system: 

Image Added

Final Considerations

• If the systems you are working on already have some records in the CDR, all of the previous records on the clients won't be available on cdrview
• If you use a Wildix system as a database server, old records on the DB server cdrview will be available even after unifying CDRs
• If you are using an external database server, the database structure needs to be there before configuring the clients
• If you are using an external database server, no previous records will be available (unless a full dump was used to recreate the database.  In such case, records contained in the dump will be available)
• If you are not using the same database name, table name, user or password, you need to adjust corresponding parameters on the cdr_mysql.conf file

...