|
When debugging your connection, you should start from the physical layer and move upwards. 1. To check if you are physically connected, type: #>wanrouter status
If it says connected, move to the next step, otherwise:
Check if your cables are plugged in.
Check if you are using the correct port (A102/4) (Port 1 is the lowest one, the active port will be red or green (connected/disconnected)
Check if you are using the proper cables. (Line from Telco uses straight T1/E1 Cable; Line to channel bank or to another PBX uses cross T1/E1 cable)
Check if you are using the proper coding/framing. (contact your Telco for this information)
2. Tp check if you are having errors/overruns, type repeatedly: #>ifconfig <interface name>
It is normal to have a few errors (usually occurs during line synchronization), if your number of overruns and errors is not incrementing go to the next:
If your number of errors is increasing:
You could be using the wrong framing/coding mode.
Try replacing your cables.
If you have noise on the line, contact your telco to test the line.
If your number of overruns is increasing:
You have an interrupt issue, please contact Sangoma Tech Support.
3. To check if you are having line/bit errors, or alarms. type: #>wanpipemon -i <interface name> -c Ta
Check if you have any alarms on.
RED (Red Alarm) - Physical Layer issue, go back to step 1.
YEL (Yellow Alarm) - Other end of the connection is down; Contact your telco or check the connected PBX/Channel Bank
ALOS/LOS (Loss of Signal) - Physical Layer issue, go back to step 1.
OOF (Out of Frame) - You could be using the wrong framing mode.
If all alarms are off, repeat command several times and check if any of the counters are incrementing. If counters are not incrementing abnormally, go to next step. Else:
If you have Bit errors or Line code violation incrementing, go to step 1.
If you have Framing bit errors or Bit errors, you could be using the wrong framing mode.
4. Launch Zaptel, type: #>ztcfg -vvv
If you have no errors, proceed to the next step, otherwise: If you have this message:
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'
The zap device was not ready, wait 2-3 seconds and try again.
If you get the same message after 4-5 seconds, then you probably did not configure UDEV for Zaptel devices,
go to zaptel source directory (usually usr/src/zaptel), type:
#>make install-udev
Then try again.
If you get this error:
ZT_CHANCONFIG failed on channel XX: No such device or address (6)
Your /etc/zaptel.conf is not configured properly.
5. Launch Asterisk with added verbosity and command line #>asterisk -vvvvvvvvvc
If you are in the Asterisk CLI, go to the next step, else:
If you get this error:
Jan 12 23:30:06 WARNING[6896]: chan_zap.c:912 zt_open: Unable to open '/dev/zap/channel': No such file or directory
:
:
:
Jan 12 23:30:06 WARNING[6896]: loader.c:554 load_modules: Loading module chan_zap.so failed!
Then your /etc/asterisk/zapata.conf is not configured properly.
If you get something like:
Signalling requested is FXO KewStart but channel signalling is FXO Loopstart...
Then your /etc/zaptel.conf and /etc/asterisk/zapata.conf do not match.
6. In the Asterisk CLI, type: #>zap show channels
Check that you have the correct amount of channels registered in Asterisk, and in the proper context.
You should an entry for each of your zap channels in addition to your pseudo channel, for example:
Chan Extension Context
pseudo from-incoming
1 from-pstn
2 from-pstn
3 from-pstn
If you are using a PRI ISDN connection, type: #>pri show span <span number>
It should say:
*CLI> pri show span 2
Primary D-channel: 48
Status: Provisioned, Up, Active
:
:
N200 Counter: 3
If it says:
Status: Provisioned, Down, Active
You are not receiving frames, start a trace .
If D Channel goes up and down,
Recompile/reinstall zaptel.
Go to zaptel source directory and type:
#>make clean; make install
|
