Versions Compared

Key

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


Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

Info

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

Note that BRI/ PRI Media Gateways are EOL.

Created: April 2018

Updated: May 2022

Permalink: https://wildix.atlassian.net/wiki/x/pw3OAQ

Table of Contents

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


Image Modified

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:

  • Create a dialplan procedure to perform the test of the ports:

...

Here is what we have after ports configuration: 



The setting is ready for the test procedure. Dial the number 9999 and check the work of the BRI device by listening to the sound file.

...

“Up” indicates that the service works correctly, while “Down” indicates the problem on the line and/ or in the Gateway configuration:



Resolving issues with ISDN operator’s line connection

Issue 1.1. The physical link is not active

...

  • Make sure that “Clock” is set up to “Use provided clock” in WMS -> Trunks, under the configuration menu of BRI/ PRI trunk
  • Request an operator to check the line’s state

Resolving issues with PBX legacy/other devices connection

Issue 2.1. The physical link is not active 

...

Note

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


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

...