Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



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

...

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


Info

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

Created: April 2018

Updated: February August 2019

Permalink: https://confluence.wildix.com/x/ygBuAQ

Table of Contents

Introduction

...

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:

...

  • Echo or noise in your network
  • Voice quality issues
  • Analog signals

Step 1. Connect to BRI/ PRI Media Gateway

  • Connect to BRI/ PRI via SSH using the following command:

...

"PBX IP" is the IP address of your PBX where the PCM traffic will be sent.


Step 2. Enable pcap trace on PBX

  • Go to WMS Settings -> Tools and utilities -> Generate trace
  • Enable "Custom tcpdump" option and enter the following string: 

...

  • Click Start to generate a file
  • When the file is generated, click Stop
  • Click on the file to download it

Step 3. Convert a pcap file using Wireshark packet analyzer 

To convert a pcap file to a PCM file (*.au format), use Wireshark:

  • Select UDP packet -> Analyze -> Decode as RTP
  • After the decoding is completed, go to Telephony -> RTP -> RTP Analysis 
  • Select Save Payload As
  • Name the file and select a folder to save it
  • Choose Format : .au and Channels : forward (or both)
  • Click OK to save the file

Step 4. Open a PCM file using Audacity program

After you converted a pcap file to a PCM one, you can open it using Audacity program.

With the help of Audacity, you can listen to each RTP stream that the PCM file contains and identify the reasons of echo or noise in your network or any other analog and voice quality issues.


Debugging of BRI/ PRI Gateways using PCAP trace

Note

PCAP tracing feature is available starting from BRI/ PRI firmware v. 43.1.1264.


  • Access the Gateway's web interface -> System -> Packet Capture
  • URL and Link Name
  • 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"
  • Go to Management menu -> File -> click on the file to download it:

Open the trace with Wireshark program.

Debugging of ISDN Gateways using Syslog 

...

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:

...