Confirming Amfeltec PCI-e timers set up on ViciBox 10

[didntgotocollege]

Hi all, I picked up some Amfeltec pcie timers and installed them in our dialer-only servers before using vicibox 10 to set up. The cluster is working fine but I'm afraid it's not utilizing the timer cards and I don't how to confirm. The posts on the forums that I was able to find seem to not match the config files and directories of Vicibox 10 (e.g. posts mention /etc/init.d/vicidial which no longer exists). I'm also confused if dahdi_dummy is still required or still in use since the main dahdi drivers have built in timing capability now.

Is there a command/test to confirm the timers are working? I tried dahdi_test and got the "Opened pseudo dahdi interface, measuring accuracy... 99.996%" but I don't know if that's using the software timer or the hardware cards.

My dmesg appears to be laoading the cards but also mentions dahdi_dummy
[ 27.979532] dahdi: loading out-of-tree module taints kernel.
[ 27.979620] dahdi: module verification failed: signature and/or required key missing - tainting kernel
[ 27.981063] dahdi: Version: 3.1.0
[ 27.981186] dahdi: Telephony Interface Registered on major 196
[ 28.010340] dahdi: Warning: Span DAHDI_DUMMY/1 didn't specify a spantype. Please fix driver!
[ 28.010385] dahdi_dummy: Trying to load High Resolution Timer
[ 28.010386] dahdi_dummy: Initialized High Resolution Timer
[ 28.010386] dahdi_dummy: Starting High Resolution Timer
[ 28.010387] dahdi_dummy: High Resolution Timer started, good to go
[ 28.077071] Loading Amfeltec VoiceSync Driver v1.3.9 (Verbose 0)
[ 28.077176] usbcore: registered new interface driver vsusb
[ 28.077176] ...Registering vsusb (usb) device!


Any guidance or confirmation they are working would be appreciated!

Vicibox 10 install from ISO
VERSION: 2.14-869a (2.14b0.5)
BUILD: 221021-1038
DB Schema: 1669
SVN: 3651

[Kumba]

If you do a 'dahdi show status' from the asterisk CLI it should show that VOICESYNC is the timing source. When the DAHDI module loads it loads a software timer (DAHDI_DUMMY) as a default timing source until a hardware timer can be used.

[didntgotocollege]

If you do a 'dahdi show status' from the asterisk CLI it should show that VOICESYNC is the timing source. When the DAHDI module loads it loads a software timer (DAHDI_DUMMY) as a default timing source until a hardware timer can be used.

Thanks Kumba, I was so brain fried i was trying that before from terminal lol. I am unfortunately seeing DAHDI_DUMMY. So while dmesg is showing the VoiceSync driver 1.3.9 being loaded, it's not being used. I'm starting to come to the conclusion that the PCIes aren't being recognized at all by the R430 and I need to figure that out first!

Description Alarms IRQ bpviol CRC Fra Codi Options LBO
DAHDI_DUMMY/1 (source: HRtimer) 1 UNCONFI 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)

[didntgotocollege]

Simple explanation, servers aren't seeing the cards. Working with amfeltec now, they are super fast btw!

[didntgotocollege]

So now I got that working, it looks like it's loading both drivers, the dummy and voicesync
DAHDI_DUMMY/1 (source: HRtimer) 1 UNCONFI 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)
VOICESYNC/1 (source: voicesync) 1 UNCONFI 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)