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

Introduction

...

SIP Trunk Settings Guide describes trunk settings and can be helpful in configuring various parameters of Media Gateways: 

• ISDN - FXO - GSM - SIP Trunk Settings Guide

Troubleshooting of BRI Gateways in case of provisioning or network issues

...

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:

...

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

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

debug -c

• To disconnect from the device:

...

• 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 “Call Progress” “Setup Confirm” 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

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>

...

• been responded

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

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

debug -c

• To disconnect from the device:

quit

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:

• SIPTransportRemote = UDP
• SIPServerPortRemote = 5060

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

...