TE410 issues - Internally clocked

jmross · July 29, 2020, 6:31pm

Hi, I’m having some issues with our TE410 cards.

In our server we had two of these cards but just one T1 line plugged into port 1 of the first card at the moment. We started having crackling sounds which persisted after the cable was replaced. Our provider says the issue is not on their end.

We had a lot of errors like:

NOTICE[20291] chan_dahdi.c: Got DAHDI event: HDLC Abort (6) on D-channel of span 1

and, I believe, timing slips indicated by /proc/dahdi/1.

In dahdi-channels.conf, it said that this span (card 0, span 1) was a clock source:

Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) ESF/B8ZS ClockSource

We moved the cable to the first port of the second card (card 1, span 1) and the crackling issue seems to have gone away. The above HDLC related error is gone too. So, does this indicate hardware failure with the first card?

Another concern is that the new span being used is now internally clocked. I don’t think this is optimal. I also see timing slips when doing cat /proc/dahdi/5.

Here’s the output when restarting DAHDI (systemctl restart dahdi):

Jul 29 13:20:43 voip systemd[1]: Stopping LSB: DAHDI kernel modules...
Jul 29 13:20:43 voip dahdi[2714]: Unloading DAHDI hardware modules: rmmod: ERROR: Module wct4xxp is in use
Jul 29 13:20:43 voip dahdi[2714]: rmmod: ERROR: Module oct612x is in use by: wct4xxp
Jul 29 13:20:43 voip dahdi[2714]: rmmod: ERROR: Module wct4xxp is in use
Jul 29 13:20:43 voip dahdi[2714]: rmmod: ERROR: Module dahdi_echocan_mg2 is in use
Jul 29 13:20:43 voip dahdi[2714]: rmmod: ERROR: Module dahdi is in use by: oct612x wct4xxp dahdi_echocan_mg2
Jul 29 13:20:43 voip dahdi[2714]: error
Jul 29 13:20:43 voip systemd[1]: Stopped LSB: DAHDI kernel modules.
Jul 29 13:20:43 voip systemd[1]: Starting LSB: DAHDI kernel modules...
Jul 29 13:20:43 voip dahdi[2756]: Loading DAHDI hardware modules:
Jul 29 13:20:43 voip dahdi[2756]:    wct4xxp: done
Jul 29 13:20:43 voip dahdi[2756]: D: auto '/sys/bus/dahdi_devices/devices/pci:0000:05:01.0'
Jul 29 13:20:43 voip dahdi[2756]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:05:01.0
Jul 29 13:20:43 voip dahdi[2756]: D: auto '/sys/bus/dahdi_devices/devices/pci:0000:05:02.0'
Jul 29 13:20:43 voip kernel: [4214603.879355] dahdi_devices pci:0000:05:01.0: local span 1 is already assigned span 1
Jul 29 13:20:43 voip kernel: [4214603.879362] dahdi_devices pci:0000:05:01.0: local span 2 is already assigned span 2
Jul 29 13:20:43 voip kernel: [4214603.879364] dahdi_devices pci:0000:05:01.0: local span 3 is already assigned span 3
Jul 29 13:20:43 voip kernel: [4214603.879366] dahdi_devices pci:0000:05:01.0: local span 4 is already assigned span 4
Jul 29 13:20:43 voip dahdi[2756]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:05:02.0
Jul 29 13:20:43 voip kernel: [4214603.881675] dahdi_devices pci:0000:05:02.0: local span 1 is already assigned span 5
Jul 29 13:20:43 voip kernel: [4214603.881679] dahdi_devices pci:0000:05:02.0: local span 2 is already assigned span 6
Jul 29 13:20:43 voip kernel: [4214603.881682] dahdi_devices pci:0000:05:02.0: local span 3 is already assigned span 7
Jul 29 13:20:43 voip kernel: [4214603.881684] dahdi_devices pci:0000:05:02.0: local span 4 is already assigned span 8
Jul 29 13:20:43 voip dahdi[2756]: using '/etc/dahdi/assigned-spans.conf'
Jul 29 13:20:44 voip kernel: [4214604.014814] wct4xxp 0000:05:01.0: Span 1 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.014873] wct4xxp 0000:05:01.0: SPAN 1: Primary Sync Source
Jul 29 13:20:44 voip kernel: [4214604.014953] wct4xxp 0000:05:01.0: Span 2 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.015007] wct4xxp 0000:05:01.0: SPAN 2: Secondary Sync Source
Jul 29 13:20:44 voip kernel: [4214604.015096] wct4xxp 0000:05:01.0: Span 3 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.015162] wct4xxp 0000:05:01.0: SPAN 3: Tertiary Sync Source
Jul 29 13:20:44 voip kernel: [4214604.015241] wct4xxp 0000:05:01.0: Span 4 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.015295] wct4xxp 0000:05:01.0: SPAN 4: Quaternary Sync Source
Jul 29 13:20:44 voip kernel: [4214604.015299] wct4xxp 0000:05:02.0: WARNING: Cannot set priority on span 5 to 5. Please set to a number between 1 and 4
Jul 29 13:20:44 voip kernel: [4214604.015377] wct4xxp 0000:05:02.0: Span 1 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.015433] wct4xxp 0000:05:02.0: WARNING: Cannot set priority on span 6 to 6. Please set to a number between 1 and 4
Jul 29 13:20:44 voip kernel: [4214604.015522] wct4xxp 0000:05:02.0: Span 2 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.015540] wct4xxp 0000:05:01.0: All spans in alarm : No validspan to source RCLK from
Jul 29 13:20:44 voip kernel: [4214604.015551] wct4xxp 0000:05:01.0: RCLK source set to span 1
Jul 29 13:20:44 voip kernel: [4214604.015591] wct4xxp 0000:05:02.0: WARNING: Cannot set priority on span 7 to 7. Please set to a number between 1 and 4
Jul 29 13:20:44 voip kernel: [4214604.015679] wct4xxp 0000:05:02.0: Span 3 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.015735] wct4xxp 0000:05:02.0: WARNING: Cannot set priority on span 8 to 8. Please set to a number between 1 and 4
Jul 29 13:20:44 voip kernel: [4214604.015813] wct4xxp 0000:05:02.0: Span 4 configured for ESF/B8ZS
Jul 29 13:20:44 voip kernel: [4214604.016165] wct4xxp 0000:05:02.0: RCLK source set to span 1
Jul 29 13:20:44 voip kernel: [4214604.016169] wct4xxp 0000:05:02.0: System timing mode, RCLK set to span 1
Jul 29 13:20:44 voip dahdi[2756]: Running dahdi_cfg: done.
Jul 29 13:20:44 voip systemd[1]: Started LSB: DAHDI kernel modules.

I’m concerned about this line:

Jul 29 13:20:44 voip kernel: [4214604.015299] wct4xxp 0000:05:02.0: WARNING: Cannot set priority on span 5 to 5. Please set to a number between 1 and 4

/etc/dahdi/system.conf:

# Autogenerated by /usr/sbin/dahdi_genconf on Wed Jul 29 13:43:49 2020
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" ESF/B8ZS RED
span=1,1,0,esf,b8zs
# termtype: te
bchan=1-23
dchan=24
echocanceller=mg2,1-23

# Span 2: TE4/0/2 "T4XXP (PCI) Card 0 Span 2" ESF/B8ZS RED
span=2,2,0,esf,b8zs
# termtype: te
bchan=25-47
dchan=48
echocanceller=mg2,25-47

# Span 3: TE4/0/3 "T4XXP (PCI) Card 0 Span 3" ESF/B8ZS RED
span=3,3,0,esf,b8zs
# termtype: te
bchan=49-71
dchan=72
echocanceller=mg2,49-71

# Span 4: TE4/0/4 "T4XXP (PCI) Card 0 Span 4" ESF/B8ZS RED
span=4,4,0,esf,b8zs
# termtype: te
bchan=73-95
dchan=96
echocanceller=mg2,73-95

# Span 5: TE4/1/1 "T4XXP (PCI) Card 1 Span 1" (MASTER) ESF/B8ZS
span=5,5,0,esf,b8zs
# termtype: te
bchan=97-119
dchan=120
echocanceller=mg2,97-119

# Span 6: TE4/1/2 "T4XXP (PCI) Card 1 Span 2" ESF/B8ZS RED
span=6,6,0,esf,b8zs
# termtype: te
bchan=121-143
dchan=144
echocanceller=mg2,121-143

# Span 7: TE4/1/3 "T4XXP (PCI) Card 1 Span 3" ESF/B8ZS RED
span=7,7,0,esf,b8zs
# termtype: te
bchan=145-167
dchan=168
echocanceller=mg2,145-167

# Span 8: TE4/1/4 "T4XXP (PCI) Card 1 Span 4" ESF/B8ZS RED
span=8,8,0,esf,b8zs
# termtype: te
bchan=169-191
dchan=192
echocanceller=mg2,169-191

# Global data

loadzone        = us
defaultzone     = us

/etc/dahdi/assigned-spans.conf:

#
# Autogenerated by /usr/sbin/dahdi_span_assignments on Wed Jul 29 13:43:49 EDT 2020
# Map devices + local spans to span + base channel number

# Device: [] @PCI_Bus_05_Slot_02 /sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:01.0/pci:0000:05:01.0
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:01.0/pci:0000:05:01.0 1:1:1
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:01.0/pci:0000:05:01.0 2:2:25
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:01.0/pci:0000:05:01.0 3:3:49
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:01.0/pci:0000:05:01.0 4:4:73

# Device: [] @PCI_Bus_05_Slot_03 /sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:02.0/pci:0000:05:02.0
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:02.0/pci:0000:05:02.0 1:5:97
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:02.0/pci:0000:05:02.0 2:6:121
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:02.0/pci:0000:05:02.0 3:7:145
/sys/devices/pci0000:00/0000:00:02.0/0000:01:00.3/0000:05:02.0/pci:0000:05:02.0 4:8:169

/etc/asterisk/dahdi-channels.conf:

; Autogenerated by /usr/sbin/dahdi_genconf on Wed Jul 29 13:43:49 2020
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" ESF/B8ZS RED
group=0,11
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 1-23
context = default
group = 63

; Span 2: TE4/0/2 "T4XXP (PCI) Card 0 Span 2" ESF/B8ZS RED
group=0,12
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 25-47
context = default
group = 63

; Span 3: TE4/0/3 "T4XXP (PCI) Card 0 Span 3" ESF/B8ZS RED
group=0,13
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 49-71
context = default
group = 63

; Span 4: TE4/0/4 "T4XXP (PCI) Card 0 Span 4" ESF/B8ZS RED
group=0,14
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 73-95
context = default
group = 63

; Span 5: TE4/1/1 "T4XXP (PCI) Card 1 Span 1" (MASTER) ESF/B8ZS
group=0,15
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 97-119
context = default
group = 63

; Span 6: TE4/1/2 "T4XXP (PCI) Card 1 Span 2" ESF/B8ZS RED
group=0,16
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 121-143
context = default
group = 63

; Span 7: TE4/1/3 "T4XXP (PCI) Card 1 Span 3" ESF/B8ZS RED
group=0,17
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 145-167
context = default
group = 63

; Span 8: TE4/1/4 "T4XXP (PCI) Card 1 Span 4" ESF/B8ZS RED
group=0,18
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 169-191
context = default
group = 63

How do I set this span use the far end as the timing source? Do I edit the configuration files in /etc/dahdi/ or should those continue to be auto-generated?. Maybe I need to change something in genconf_parameters?

Thanks

david551 · July 29, 2020, 8:19pm

The policy on the forum is that problems with Dahdi devices should be addressed to the card vendor, using their commercial support channels. One of the reasons for this is that Sangoma/Digium are card vendors and a lot of their designs have been cloned.

jmross · July 29, 2020, 9:05pm

OK, I understand that this forum might not be able to tell me if my card is failing.

But, I’m mostly concerned with this error:

wct4xxp 0000:05:02.0: WARNING: Cannot set priority on span 5 to 5. Please set to a number between 1 and 4

Why won’t it let me set the timing parameter to 5 on this span?

Rmcgrath · July 30, 2020, 5:17pm

First of all you should always set clock source to external.
Span=1 ,0,
Span=2,0 ,

jmross · July 30, 2020, 5:59pm

Thanks for your reply.

I just made the timing internal (0) for the card I’m not using right now. ie. spans 1-4.

In /etc/dahdi/system.conf:

span=1,0,0...
...
span=2,0,0...
...
span=3,0,0...
...
span=4,0,0...
...
span=5,1,0...
...
span=6,2,0...
...
span=7,3,0...
...
span=8,4,0...

and it’s says it isn’t internally clocked anymore.

Maybe I have the Ident Wheel on the cards set wrong? Not sure, I’m kind of new to this… I’m still not sure why I couldn’t set that span to having timing of 5. The documentation for system.conf says that the timing numbers should be different for each span. But does that mean 1-8 across both cards or each card has spans with timing of 1-4?

Thanks

Rmcgrath · July 30, 2020, 7:34pm

You are confusing the clock priorities when card will provide clock synchronization, but if is connected to a service provider it must set to 0.
It will better someone with more experience can help you on site.

garyg · July 30, 2020, 11:47pm

In our setups of switchtype = euroisdn, timing clock source comes from the carrier network to the CPE. So clock source priority is only used to give an order to the connected network spans clock source for timing.
Eg. Spans 1-4 come from the carrier to your equipment = requires timing clock source priority.
Spans 5-8 go to an external PBX = no timing clock source stated, we deliver the timing.

I would be looking at chan_dahdi.conf for the signalling source to confirm it is correct. In our old versions we have it in /etc/asterisk/chan_dahdi.conf.

Note that you need to state what type of signalling you expect from each span.

signalling=pri_cpe ;coming from the carrier to your CPE. You receive the timing clock source and need to state the priority.
signalling=pri_net ;going from your CPE to another PBX. You deliver and are delivering the timing clock source for these as you’re in essence acting as the carrier.

You can look closer at the debug from the CLI for other issues;
pri set debug on span x
pri set debug off span x
pri show debug ;don’t leave it on when you’ve finished.

I’m not the expert but hope this helps with some part.

system · August 29, 2020, 11:47pm

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