...
The first step is to check the physical layer connection between NBE and the telco.To do this we will need to use the wanpipemoncmd line tool.
Open the windows command line tool : Windows Start -> Run -> "cmd.exe"
To view T1/E1 Alarms on the first T1 of your sangoma digital card :
wanpipemon -i wanpipe1_if1 -c Ta
The output of the command above will present status of all the different T1/E1 alarms, plus some error counters.
OOF means the line framing is out of frame so we are receiving bad data. Also on E1 you can toggle the framing and this may correct the issue.
AIS means one of the repeaters down stream are in alarm so speak with the telco about this.
YEL means the telco is in alarm so call them and find out what alarm they are in
LOS means loss of signal so the line is probably not connected. If the line looks good try a cross over cable. Note this is not the same as a ethernet cross over; pinouts are available at Cable PinoutsTo view Communications/Error statistics
wanpipemon -i wanpipe1_if1 -c sc
If there are no positive alarms on the first T1 (wanpipe1_if1), check the next T1 (wanpipe2_if1), then the third (wanpip3_if1)...etc
If there are no physical layer issues, the next step is to ensure your signaling (D channel) is up.
To do this simply open your NBE gateway manager (http://localhost:7783/) and click on "Status and Controls" and then select "Channel Status" in there.
Then ensure the status looks as shown below=idle (Blue colour)
Now if you have a different status other then "Idle" then refer to the legend below.
If you can not resolve the issue please visit NBE troubleshooting material and send all the log information to support@sangoma.com
If the D channel is up but calls do not complete:
place NBE into development mode by following the steps at http://wiki.sangoma.com/Netborder-Express-Debugging#how-to-enable-development-mode-dynamically Debugging . Once in development mode there will be a new log for each time in
Code Block \Program Files\Netborder\Express\Gateway\logs\call-logs\<<Number of Year>>\<<Number of Month>><<Name of Month>>\<<Number of Day>>\<<Hour>>
eg. \Program Files\Netborder\Express\Gateway\logs\call-logs\2009\11November\27\11\.
or you can simply locate the call-logs via the NBE WebGUI:
Now to start tracing the calls simply start with an inbound call first if inbound is not working. Now below is a trace of a working inbound call and one where the PBX does not respond to NBE's SIP messages.
Inbound Call Where PBX Does Not Respond --> Coming Soon!
Inbound Call That Works --> Coming Soon!Below is a trace of an outbound call that the pstn side rejects the call and the other call is a working outbound call. Also note if you call out and the log file is not being made you ether do not have development mode enabled (step 4), or your pbx is not sending the SIP message to IP and port you setup in the quick setup.
Outbound Call That Is Rejected From The Telco --> http> http://wiki.sangoma.com/NBE-pri-span-debugging-outbound-rejected
Outbound Call That Works --> http> http://wiki.sangoma.com/NBE-pri-span-debugging-outbound-workingIf you can not sort out the issue please visit NBE troubleshooting material and and send all that information to support@sangoma.com.
...
First enable development mode using the steps at httphttps://wikisangomakb.sangoma.com/Netborder-Express-Debugging#dev_modeatlassian.net/wiki/spaces/EOLPAF/pages/56361222/Debugging?search_id=3d089c3c-93e5-45d0-aa4e-c62007fbd459 . Once this is enabled, make a incoming call into the system. When the call is completed simply go to "File Browser -> logs -> Call logs" then navigate until you have found the log for the inbound call you made. Once you found the call it should look something like the one below. Find the circled parts below of the inbound call and take note of the value of each. In this example the ANI fields are not populated, then the DNIS values are both set to 1.
...
With these values you now know how the telco is sending inbound calls, so most likely the telco will want the same values set on an outbound call. So go to httphttps://wikisangomakb.sangoma.com/Netborder-Express-Debugging#number_planatlassian.net/wiki/spaces/EOLPAF/pages/56361222/Debugging?search_id=3d089c3c-93e5-45d0-aa4e-c62007fbd459 to see how to set these values for your outbound call. Once this is done then outbound calls should start working.
...