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>

...

 <div class="lang-box-pdf">
	<div>
<div class="lang-switch">
			<span class="letters-form"><a title="English" href="#">EN</a>&nbsp;|&nbsp;<a title="Italian" href="#" >IT</a>&nbsp;|&nbsp;<a title="French" href="#" target="_blank">FR</a>&nbsp;|&nbsp;<a title="German" href="#">DE</a></span>
		</div>
		<div class="google-lang">
			<div id="google_translate_element">
			</div>
			<script type="text/javascript">
					function googleTranslateElementInit() {
						new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
						}
			</script>
			<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
		</div>
		
		<div class="pdf-button">
			<a href="#https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=77988379" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
		</div>
	</div>
</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. 

...

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 on in a WMS Network.

Requirements

The only requirement to have a unified CDR-View is to have all of the systems configured to use the same database. Out of the box, every system uses a local database. So, first of all we need a database server that is accessible to all of the systems on the WMS network. For the sake of simplicity in this document we use one of the systems as a database server for the rest of systems. 

Configuration

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: 

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.

Server configuration

The database server needs to be accessible by all of the other systems. Since here we are using one of the systems as the database server, we don't need to worry about the database structure, it is already there. We just need to make it available:

...

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

Client configuration

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: 

...

Another thing worth mentioning is the fact that we did not change the dbname, table, user or port. This is because we are using a Wildix system as a database server, which means the database structure is ready. We did not change the password either because we configured the same password for the remote root access as the local root account was using.

Result

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

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

...

<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>

...