Advertisement
Quick Links
Debugging and troubleshooting of Media Gateways
Jun 10, 2020 22:20
Debugging and troubleshooting of Media Gateways
This Admin Guide describes how to debug and troubleshoot various issues with Wildix Media Gateways.
Created: April 2018
Updated: August 2019
Permalink:
https://confluence.wildix.com/x/ygBuAQ
Introduction
Troubleshooting of BRI Gateways in case of provisioning or network issues
Troubleshooting of BRI/ PRI Gateways in case of call issues
Resolving issues with ISDN operator's line connection
Resolving issues with PBX legacy/other devices connection
Debugging of BRI/ PRI Gateways using PCM trace
Step 1. Connect to BRI/ PRI Media Gateway
Step 2. Enable pcap trace on PBX
Step 3. Convert a pcap file using Wireshark packet analyzer
Step 4. Open a PCM file using Audacity program
Debugging of BRI/ PRI Gateways using PCAP trace
Debugging of ISDN Gateways using Syslog
Debugging of W04FXO Gateways
Troubleshooting of W01/ W02 FXS 2014
Introduction
This Guide provides information about various ways of solving Media Gateways issues and analyzes the most
typical problems with the help of examples.
Consult the Guide in case you have provisioning, network and call issues.
Some useful links
Refer to these Quick Installation Guides for reminding how to connect and configure Media Gateways:
W02/04BRI
W01/02PRI
W01/02/04FXS
W24FXS 2015
W04FXO
SIP Trunk Settings Guide describes trunk settings and can be helpful in configuring various parameters of Media
Gateways
:
Debugging and troubleshooting of Media Gateways
Page 1 of 14
Advertisement
Subscribe to Our Youtube Channel
Related Manuals for Wildix BRI Series
Summary of Contents for Wildix BRI Series
- Page 1 Debugging and troubleshooting of Media Gateways Jun 10, 2020 22:20 Debugging and troubleshooting of Media Gateways This Admin Guide describes how to debug and troubleshoot various issues with Wildix Media Gateways. Created: April 2018 Updated: August 2019 Permalink: https://confluence.wildix.com/x/ygBuAQ Introduction...
- Page 2 Debugging and troubleshooting of Media Gateways ISDN - FXO - GSM - SIP Trunk Settings Guide Troubleshooting of BRI Gateways in case of provisioning or network issues Issues: The gateway is not identified by the network The gateway appears to cause the calls’ interruption The gateway appears to affect the quality of the conversation The gateway is not available for provisioning on the WMS The gateway appears not to work correctly (the ports are not functional, the signal lights blink in a strange...
- Page 3 Debugging and troubleshooting of Media Gateways Hold the reset button. After a few moments the four LEDs of the display will start to blink. Only when all the four LEDs stop blinking, release the reset button and wait for the light of the LEDs to go out. Then unplug the power and retest the device.
- Page 4 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 needed);...
- Page 5 Debugging and troubleshooting of Media Gateways The procedure, while calling the number 9999, occupies the line corresponding to the predetermined BRI port and calls the number 5555. The number is checked by the same procedure, and the selected music file starts to play. Due to the loop that is generated, it’s possible to check all the eventual lines interruptions and the conversation quality, taking the necessary time to perform the test.
- Page 6 Debugging and troubleshooting of Media Gateways 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. Troubleshooting of BRI/ PRI Gateways in case of call issues Issue: PRI or BRI Gateway fails to make/ receive calls.
- Page 7 Check the mode in which the ISDN interface of the PBX Legacy operates: If it operates in TE mode with " Use provided clock " , the Wildix PRI Gateway should operate as NT with the clock set up to "Generate clock" If it operates in NT mode with "...
- Page 8 Debugging of BRI/ PRI Gateways using PCM trace PCM traces record all analog signals sent or received on the side of the Wildix media gateway. The data will be sent once a call is being established or is in progress. No data will be sent if the gateway if there are no calls in progress.
- Page 9 Debugging and troubleshooting of Media Gateways Step 1. Connect to BRI/ PRI Media Gateway Connect to BRI/ PRI via SSH using the following command: ssh -l admin <DEVICE IP> Where: <DEVICE IP> is the IP adress of BRI/ PRI Media Gateway. Launch the following commands : Mipt.PcmCaptureEnable = "Enable"...
- Page 10 Debugging and troubleshooting of Media Gateways -v -s0 -i any port "5001" or port "6001" Where: "5001" (incoming) and "6001" (outgoing) are ports and channels to be specified. For example: 5002, port 1 - channel 2 5003, port 2 - channel 1 5004, port 2 - channel 2 Note: Pcap trace can be enabled only for one particular channel.
- Page 11 Debugging and troubleshooting of Media Gateways 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.
- Page 12 Collecting Syslog from Wildix Devices. It is also possible to enable remote syslog on Wildix devices: go to WMS -> Devices, double click on a provisioned device to edit it and select “Syslog Server” (enter the address of the remote server). Starting from WMS version 3.88, it is possible to enable Remote Syslog without installation of a remote server.
- Page 13 IP (e.g. 192.168.1.16): telnet <DEVICE IP> Where: <DEVICE IP> is the IP adress of W04FXO Log in using your admin access credentials (admin / wildix) To start the debug, use the following string: debug -o To stop the debug, use this string:...
- Page 14 Debugging and troubleshooting of Media Gateways 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.
Need help?
Do you have a question about the BRI Series and is the answer not in the manual?
Questions and answers