Wildix BRI Series Admin Manual

Brand: Wildix

Model: BRI Series

Type: Admin Manual

This manual is also suitable for

Debugging and troubleshooting of Media Gateways

Page 2 of 14

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

way)

Reason:

Provisioning, network or functioning of BRI devices is not correct

Solution:

The Reset procedure of the Gateway.

Reset operation resolves some problems related to the Gateway (strange blinking of LEDs, connectivity

problems) and some problems related to LAN connection, access to the configuration page via http etc. Follow

these steps to perform the correct operation procedure:

The Gateway should be connected only to the power :

Press the button signed as reset/default on the backside of the Gateway, using paperclip or the object of a

similar shape:

Debugging and troubleshooting of Media Gateways

Page 3 of 14

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.

In case the operation was not successful, repeat it again.

Test procedure (performed after the device is reset)

For the test performance you need:

1 PBX with a user (you can create a new user especially for the test or use an existing one)

1 provisioned phone associated to this user

1 Dialplan procedure

1 provisioned BRI device (which was previously reset and upgraded to the latest version of firmware)

1 network cable to connect the ports involved in the test

The test

The test consists of a call with two ports involved, one used as outgoing, another one – as incoming.

The PBX plays the audio file in loop to keep the call running and give the possibility to test the device.

It is recommended to perform this operation in a specifically designed test environment in order to exclude the

problems caused by some external factors, that could influence the result (the problems related to the operator,

lines, configuration etc).

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

Debugging and troubleshooting of Media Gateways

Page 4 of 14

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 if online Guide

needed); connect the needed ports using the network cable RJ45:

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

Debugging and troubleshooting of Media Gateways

Page 5 of 14

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.

Once the procedure is entered into the Dialplan, it should be associated to the user:

Go to WMS -> -> select BRI device and click to configure. Set up TE as one port, NT as the Trunks Edit

second port (by choice) and associate " " Dialplan procedure with both of them. Here, in the example, testbri

W01BRI is tested and another BRI device is used to set up the second port:

Here is what we have after ports configuration:

Debugging and troubleshooting of Media Gateways

Page 6 of 14

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.

Reason:

Connection of BRI/ PRI Gateway to the ISDN operator’s line or to the PBX Legacy/ other devices should be

checked.

Solution:

Access PRI/ BRI Gateway web interface

Go to menu. Now you can see the list of all the ISDN interfaces and the state of the physical linkISDN

“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

How to solve:

Debugging and troubleshooting of Media Gateways

Page 7 of 14

Check/ substitute the wiring

Check that the following wiring scheme is used (“straight” wiring):

In case of the wiring to the network terminal Selta with DB9 connector, the correct scheme of the wiring is

the following one:

Issue 1.2. The signal is not active

How to solve:

Make sure that “ is set up to “ ” in WMS -> , under the configuration menu Clock” Use provided clock Trunks

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

How to solve:

Check/ substitute the wiring

Check the mode in which the ISDN interface of the PBX Legacy operates:

If it operates in TE mode with " " , the Wildix PRI Gateway should operate as NT Use provided clock

with the clock set up to "Generate clock"

If it operates in NT mode with " ", the Wildix PRI Gateway should operate as TE with Generate clock

the clock set up to "Use provided clock"

Debugging and troubleshooting of Media Gateways

Page 8 of 14

Issue 2.2. The signal is not active

How to solve:

Check the protocol type used by the legacy PBX (DSS1 or QSIG), align consequently the settings of the

Wildix PRI Gateway in WMS -> -> Trunks BRI/PRI trunks

Issue 3. In case of connection to Cisco router provided by Fastweb operator, the BRI Gateway has problems

both with incoming and outgoing calls

How to solve:

Make sure that the gateway ports are set up in TE mode. Connect Cisco device to the Media Gateway

ports using the crossover cables:

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.

This debugging tool helps you to identify the following problems:

Echo or noise in your network

Voice quality issues

Analog signals

Debugging and troubleshooting of Media Gateways

Page 9 of 14

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"

Mipt.PcmCaptureEndpoint = "BRI/PRI port-channel"

Mipt.PcmCaptureIpAddr = "PBX IP"

Where:

"BRI/PRI port-channel" is BRI/ PRI port and channel from which the PCM trace will be taken. For example,

"BRI1-1" is BRI port 1, channel 1.

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

Debugging and troubleshooting of Media Gateways

Page 10 of 14

-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

Click to generate a fileStart

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 and (or ) Format : .au Channels : forward both

Click to save the fileOK

Note: Pcap trace can be enabled only for one particular channel.

Debugging and troubleshooting of Media Gateways

Page 11 of 14

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

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 -> the status is changed to "Requested"Apply & Start Capture

Make a call

After completing it, click -> the status is changed to "Completed"Apply & Stop Capture

Go to menu -> File -> click on the file to download it:Management

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

Debugging and troubleshooting of Media Gateways

Page 12 of 14

Open the trace with Wireshark program.

Debugging of ISDN Gateways using Syslog

Collecting and analyzing syslog can be useful in order to debug various issues.

For the information on how to collect syslog without Remote syslog server, read the Guide: Collecting Syslog

from Wildix Devices.

It is also possible to enable remote syslog on Wildix devices: go to WMS -> double click on a Devices,

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. Refer to

for detailed information.Remote Syslog Guide

ISDN Gateways:

Connect to the Gateway via SSH (on Windows you can use “putty” or other SSH clients) using the same

credentials you used for access to web interface

Use the string to begin the session:

logs on

To finish the session, use the string:

logs off

Make a test call

The logs help you to understand eventual issues, here is what happens when a user places an outgoing call to a

trunk:

PBX receives a request from the user and forwards it to the BRI/ PRI Gateway

The Gateway forwards the call to the operator

The operator responds to the Gateway with the status “Call Proceeding” to confirm the reception of the

request

The operator responds with the status “Call Progress” to indicate that the call has been routed to the

destination

The operator responds with the status “Alerting” to indicate that the destination is available

The operator responds with the status “Setup Confirm” to indicate that the call has been responded

Debugging and troubleshooting of Media Gateways

Page 13 of 14

In case the call could not be connected or the call was hang up by the operator, the Media Gateway receives the

following message: “Unicast RECV Disconnect”

Check the field indicating the reason of the call disconnection, for example: “Cause: Normal call clearing (16)”.

Check the codes of disconnection reasons: https://en.wikipedia.org/wiki/ISDN_User_Part#Cause_codes

Debugging of W04FXO Gateways

To debug W04FXO device, access the Gateway on its IP address (e.g. 192.168.1.16) via telnet protocol:

Use the command line (on Windows) or Terminal (on Unix and other systems) to enter the Gateway telnet

IP (e.g. 192.168.1.16):

telnet <DEVICE IP>

Where:

<DEVICE IP> is the IP adress of W04FXO

To start the debug, use the following string:

debug -o

To stop the debug, use this string:

debug -c

To disconnect from the device:

quit

Troubleshooting of W01/ W02 FXS 2014

Special behavior

Debugging and troubleshooting of Media Gateways

Page 14 of 14

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

SIPTransportRemote = UDP

SIPServerPortRemote = 5060

Note: Consult for details.Provisioning Custom Settings Guide

Wildix BRI Series Admin Manual

Brand: Wildix

Model: BRI Series

Type: Admin Manual

This manual is also suitable for

Download PDF

report

Wildix BRI Series Admin Manual

This manual is also suitable for

Wildix BRI Series Admin Manual

Related papers

Other documents