WELCOME [ Log In · Register ]        SITE [ Search · Page Index · Recent Changes ]    RSS

NBE - PRI Span Debugging

Note: This page is marked for deletion.

1) The first step is to check the physical layer connection between NBE and the telco.To do this we will need to open wanpipemon following the steps below.

alarms-properties.png

a) Right click on the port you want and click properties. 

alarms-start-wanpipemon.png

b) Click on the "T1/E1 Groups of channels" tab and then select a channel group. Once selected right click and pick "Start WANPIPE Monitor".

alarms-tools-alarms.png

c) In wanpipemon click on "T1/E1 Tools" and then click "Alarms" to view the alarm status page.

alarms-status-alarms.png

d) As you can see you have all the different T1/E1 alarms here 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 http://wiki.sangoma.com/Pinouts#A101/2/4%20Cross

2) Once you have a physical layer connection then you just simply need to insure the 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 insure the status looks as shown below, also note below is only a single T1 so E1 and multiple links will show more channels.

pri-status.png

 

3) Now if you have a different status other then "Idle" then refer to the legend below. If you can not resolve the issue please send everything at http://wiki.sangoma.com/SangomaTechSupport#nbe to techdesk@sangoma.com

pri-channel-status-legend.png

4) Now if the D channel is up but calls do not work then place NBE into development mode by following the steps at http://wiki.sangoma.com/NBE-debugging#enable_devel_mode. Once in development mode there will be a new log for each time in "\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\. Now before you continue to debug the calls first go to http://wiki.sangoma.com/nbe-faq#basic to get an understanding of how this all works.

5) 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!

6) Now below is a trace of a 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://wiki.sangoma.com/NBE-pri-span-debugging-outbound-rejected

Outbound Call That Works --> http://wiki.sangoma.com/NBE-pri-span-debugging-outbound-working

7) If you can not sort out the issue please go to http://wiki.sangoma.com/SangomaTechSupport#nbe and send everything into techdesk@sangoma.com.