PRI issue Excessive Fifo Errors

Hey Guy’s and Gal’s

Having an issue with my PBX where it will drop calls. PRI from sangoma PBX with sangoma card going to ATT router T1 port. Calls drop all of the sudden. Wanrouter status showed connected. PRI spans shows up and active. However var/log/messages show’s ATT says the error is on my side but I dont see it. What am I missing?

ep 12 04:09:14 freepbx kernel: wanpipe1: AFT Global TDM Intr
Sep 12 04:09:14 freepbx kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1
Sep 12 04:09:15 freepbx kernel: wanpipe1: Warning: Excessive Fifo Errors: Resync (rx=301/tx=5)
Sep 12 04:09:15 freepbx kernel: wanpipe1: AFT Sync Restart
Sep 12 04:09:15 freepbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Link Down)
Sep 12 04:09:15 freepbx kernel: wanpipe1: AFT communications enabled
Sep 12 04:09:15 freepbx kernel: wanpipe1: AFT Global TDM Intr
Sep 12 04:09:15 freepbx kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1
Sep 12 04:09:16 freepbx kernel: wanpipe1: Warning: Excessive Fifo Errors: Resync (rx=307/tx=5)
Sep 12 04:09:16 freepbx kernel: wanpipe1: AFT Sync Restart
Sep 12 04:09:16 freepbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Link Down)
Sep 12 04:09:16 freepbx kernel: wanpipe1: AFT communications enabled
Sep 12 04:09:16 freepbx kernel: wanpipe1: AFT Global TDM Intr
Sep 12 04:09:16 freepbx kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1
Sep 12 04:09:17 freepbx kernel: wanpipe1: Warning: Excessive Fifo Errors: Resync (rx=345/tx=5)
Sep 12 04:09:17 freepbx kernel: wanpipe1: AFT Sync Restart
Sep 12 04:09:17 freepbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Link Down)
Sep 12 04:09:17 freepbx kernel: wanpipe1: AFT communications enabled
Sep 12 04:09:17 freepbx kernel: wanpipe1: AFT Global TDM Intr
Sep 12 04:09:17 freepbx kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1
Sep 12 04:09:18 freepbx kernel: wanpipe1: Warning: Excessive Fifo Errors: Resync (rx=292/tx=5)
Sep 12 04:09:18 freepbx kernel: wanpipe1: AFT Sync Restart
Sep 12 04:09:18 freepbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Link Down)
Sep 12 04:09:18 freepbx kernel: wanpipe1: AFT communications enabled
Sep 12 04:09:18 freepbx kernel: wanpipe1: AFT Global TDM Intr
Sep 12 04:09:18 freepbx kernel: wanpipe1: Global TDM Ring Resync TDM = 0x1
Sep 12 04:09:19 freepbx kernel: wanpipe1: Warning: Excessive Fifo Errors: Resync (rx=290/tx=5)
Sep 12 04:09:19 freepbx kernel: wanpipe1:

HI @MedicSlim,

This looks like something the issue with the clock on the PRI.

can you refer the below wiki link:-
https://wiki.freepbx.org/display/PC/Driver+Debugging#DriverDebugging-PortI/OIssue:WanpipeOverruns

Can you help me understand what the RX=290 TX=5 means? should it be that much of a difference? and in this instance who is RX and who is TX PBX or Phone company

Also I am getting this response from Linux when going through the troubleshooting guide.

[[email protected] ~]# hdparm -t /dev/sda
-bash: hdparm: command not found
[[email protected] ~]# hdparm -t /dev/hda
-bash: hdparm: command not found
[[email protected] ~]#

do you install the command? yum install …

Your problem is

Sep 12 04:09:18 freepbx kernel: wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Link Down)

When the link is up it will work better

But when I check Wanpipe1 I get

***** w1g1: T1 Rx Alarms (LIU) *****

Short Circuit: OFF
Open Circuit: OFF
Loss of Signal: OFF

***** w1g1: T1 Tx Alarms *****

AIS: OFF | YEL: OFF

***** w1g1: T1 Performance Monitoring Counters *****

Line Code Violation : 10176
Bit Errors (CRC6/Ft/Fs) : 9
Out of Frame Errors : 30
Sync Errors : 5

Rx Level : > -2.5db

Not sure what you are wanting me to install?

Line Code Violation : 10176
Bit Errors (CRC6/Ft/Fs) : 9
Out of Frame Errors : 30
Sync Errors : 5

Looks like you need someone with a t-bert

(have you done the

http://www.telecomworld101.com/PiaF/ConfiguringT1LineDahdi.html

thing to match your timeing/framing/clocksource to the other end?)

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.