| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
NBE Driver failed to Install Because Windows took over installation
Go under Control Panel => Add/Remove Programs
Uninstall the Sangoma windows driver package entries
Go under C:/Windows/System32
Search for sdladrv string
Delet all the .INF and .sys files resulting from your search request
Uninstall NBE
Reboot the System
Re-Attempt installation!
It is important to note that you must explicitly deny Windows during the setup process. Our driver only installs properly when using our installation scripts, and the Windows Installation Wizard will not be able to install our cards.
...
NBE NBE fails to start
...
If NBE Gateway fails to start, the reason will provided in GatewayDebug.log.
...
| Code Block |
|---|
[root@localhost logs]# cat GatewayRollingFile.log.2012-01-15.bak 2012-01-15 21:16:02:101 +0800 [3279:3279] INFO - admin : Netborder Express Gateway version 4.1.4 2012-01-15 21:16:02:101 +0800 [3279:3279] INFO - netborder.infra.Application : Build : maint/nbe-4.1:21540? 2012-01-15 21:16:02:647 +0800 [3279:3279] INFO - admin : Netborder Express Gateway Starting 2012-01-15 21:16:02:767 +0800 [3279:3305] ERROR - netborder.sangoma.SangomaWanpipeInterface.wanpipe1_if1 : hardware echo cancellation is not supported on this interface. Please disable hardware echo cancellation for the current interface in the PSTN configuration parameters. 2012-01-15 21:16:02:777 +0800 [3279:3305] ERROR - netborder.sangoma.span.b1di1 : failed to apply echo cancellation parameters to all B-Channels. 2012-01-15 21:16:02:777 +0800 [3279:3305] ERROR - netborder.sangoma.span.b1di1 : Can't configure Echo Canceller! 2012-01-15 21:16:02:778 +0800 [3279:3305] ERROR - netborder.sangoma.boardManager : failed to start digital interface (span) b1(B1 - A101_digital)di1(B1I1) 2012-01-15 21:16:02:779 +0800 [3279:3304] ERROR - netborder.pstn.BoardRunnable : failed to initialize telephony board library 2012-01-15 21:16:02:781 +0800 [3279:3288] INFO - admin : Netborder Express Gateway Stopping |
...
...
Server With Multiple IP Addresses Will Not Start
Edit gw.properties files from the WebGUI, and change netborder.net.primaryIPAddress to the IP address you want NBE to listen on
...
or via your windows file management:
Edit the following file:
|
Place the following line anywhere in the above file:
|
X being the ip address that you want NBE to listen on.
...
If you are seeing this error in your Application log then your ToneDecoder.dll file has not been registered correctly.
To fix this go to "\Program Files\Netborder\Express\Gateway\drivers\sangoma\hw_abstraction_driver\" from the command prompt and run the command:
|
Once this is done then try to start NBE again to be sure the issue is corrected.
...
NBE 2.0 can't open Analog B-channel
...
NBE starts but on the "System Status" page of the Gateway Manager you see the following error message:
|
This error could occur if: - WANPIPE is not a valid wanpipe ID.
Edit the pstn-config.xml to specify a valid wanpipe for sangoma interface ID=<NBE ID value for A200>
...
You can get this error message if you do not have your FXO modules plugged in the correct socket on the A200. The modules have to go sequentially into the sockets, starting at the lowest numbered socket, and without any gaps.
The lowest numbered socket is the socket furthest away from the metal bracket on the lowest numbered card.
The lowest numbered card (when using an A200 with atleast 1 Remora card connected via a Backplane) is the left-most card in the bundle when looking from the metal bracket to the backplane.
...
Why Are Calls Not Hanging Up?
On analog lines the telco (FXS) has to tell the phone (FXO) to hangup. The reason for this is the FXS can not control if the line is on-hook or off-hook as this is the FXO's role. Example of this is if you leave a analog phone (in your house) off hook you will hear a fast busy tone, this is the telco indicating to you the call is over and to hangup. The telco can have many different ways to indicate to your FXO to hangup the line.
NBE by default has enabled most types of hangup detection, but it is possible that not the right method has been enable, for your telco.
...
restart the NBE Gateway for changes to take effect
if there is still not ringing on inbound calls, try chaging changing "Inband Progress Tones Indicator" (as seen in picture above) to ALERTING, then BOTH (if persists), making sure to restart the NBE gateway after each change. BOTH has the same effect as the default PROGRESS on 4ESS and 5ESS ISDN variant.
...
On inbound calls, some switches (particulary particularly in Germany) send the called party number (DNIS) in chunks using INFO ISDN messages after the initial SETUP message instead of the usual 'En-Block' mechanism which consists in sending the whole DNIS in the Called Party Number Information Element of the initial SETUP message. This method called 'Overlap Dialing' as opposed to the traditional 'En-Block' dialing method, is used to reduce call SETUP time and also to allow various combinations for number extensions.
...
The reason for this behaviour is behind authenticaiton authentication that is being enabled here on the 3CX side which normally can be disabled on the 3Cx side.
An altenative alternative way to resolve this issue on the NBE side is as follows:
Login to the NBE GUI.
Click on the File Browser tab.
Navigate to root > config > sip-client-registration.xml, and click on this file
On the right side of the screen you'll be able to see the content of the file. Scroll down until you reach <!-- Registrar --> section.
In this section please replace the "company.com" by a hostname/IP of the IP-PBX(3CX) that the NBE is communicating to.
Save the file by clicking Save Changes and restart NBE. This should fix the problem.
| Info |
|---|
NOTE: The resolution provided above was applicable with 3CX interaction, and wasn't tested with other IP-PBXes |
...
If from what ever reason the method above did not work, then the best practise is to disable the registration on the 3CX side
...