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/ygBuAQ" 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="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=23986378" 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>

This Admin Guide describes how to debug and troubleshoot various issues with Wildix Media Gateways.

Note that BRI/ PRI Media Gateways are EOL.

Introduction

...

Troubleshooting of W01/ W02 FXS 2014

Special behavior

Custom encryption is enabled on W01/ W02 FXS for SIP signaling (implemented in WMS version 3.82.32840.35). Starting from WMS version 3.85.35394.9, alternative SIP port for remote registration of W01FXS / W02FXS is used for SIP registration (the first port from RTP range).
In some scenarios, for example, when iptables forwarding is not available, port redirect doesn't work. As a result, W01/ 02 FXS can loss SIP registration. 

Solution

Disable the encryption for devices located behind NAT/ Firewall. To implement, you need to apply the following custom parameters to [wildixfxs] section of /rw2/etc/provisioning.conf file:

...

The following logical scheme demonstrates the procedure. In this case W02BRI is used (in case W01BRI is tested, you need another BRI device, to set up the second port):

To perform the test:

• Create a user or use an existing one to perform the test. In this example the user “test2” with the extension number 103 is used:
  

• Connect the Gateway to the Wildix test PBX and make the provisioning (refer to the online Guide if needed); connect the needed ports using the network cable RJ45:

...

• Access the Gateway's web interface -> System -> Packet Capture
• Fill in the following fields:
  • URL: file://test.pcap, where "file://" is the path to save a file, "test.pcap" - its name
  • Link Name: eth1
• To start the trace, click Apply & Start Capture -> the status is changed to "Requested"
• Make a call 
• After completing it, click Apply & Stop Capture -> the status is changed to "Completed"

...