Sangoma Wanpipe VoiceTime: USB Voice Sync Tool

[gmcust3]

I bought Sangoma VoiceTime and while installing

Sangoma Wanpipe VoiceTime: USB Voice Sync Tool

I get Error as :

make KBUILD_VERBOSE=1 -C /lib/modules/2.6.18-92.el5.vnow/build SUBDIRS=/root/wan pipe-voicetime-1.0.9/src EXTRA_FLAGS="-D__LINUX__ -I/lib/modules/2.6.18-92.el5.v now/build/include/ -I/include -I/usr/include -I/root/wanpipe-voicetime-1.0.9/src /include -I/lib/modules/2.6.18-92.el5.vnow/build/include/linux -I/usr/src/zaptel -1.0.9" HOMEDIR=/root/wanpipe-voicetime-1.0.9 modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-92.el5.vnow-i686'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /root/wanpipe-voicetime-1.0.9/src/.tmp_versions
rm -f /root/wanpipe-voicetime-1.0.9/src/.tmp_versions/*
make -f scripts/Makefile.build obj=/root/wanpipe-voicetime-1.0.9/src


-------------

ViciDialNOW CE doesn't support this product ?

[gardo]

There's your solution.

I bought Sangoma VoiceTime and while installing

Sangoma Wanpipe VoiceTime: USB Voice Sync Tool

I get Error as :

make KBUILD_VERBOSE=1 -C /lib/modules/2.6.18-92.el5.vnow/build SUBDIRS=/root/wan pipe-voicetime-1.0.9/src EXTRA_FLAGS="-D__LINUX__ -I/lib/modules/2.6.18-92.el5.v now/build/include/ -I/include -I/usr/include -I/root/wanpipe-voicetime-1.0.9/src /include -I/lib/modules/2.6.18-92.el5.vnow/build/include/linux -I/usr/src/zaptel -1.0.9" HOMEDIR=/root/wanpipe-voicetime-1.0.9 modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-92.el5.vnow-i686'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /root/wanpipe-voicetime-1.0.9/src/.tmp_versions
rm -f /root/wanpipe-voicetime-1.0.9/src/.tmp_versions/*
make -f scripts/Makefile.build obj=/root/wanpipe-voicetime-1.0.9/src


-------------

ViciDialNOW CE doesn't support this product ?

[williamconley]

i've done a lot of make oldconfig runs ... never had one work.

i have also found that on some installs, certain files are auto-deleted by the kernel construction scripts before they are needed. then when they are needed ... they are no longer available.

this happened to me a few times in CentOS before i switched to Gentoo, and i think it happened once or twice in gentoo as well. I haven't bumped into it in Ubuntu at all. the issue is missing kernal files that are required to patch the module into the kernel. i actually had some old install instructions that involved copying those files to a temp location during the kernel compile and then copying them back after they got deleted during the build.

but of course, first i tried the "make oldconfig" several times with no success before looking into what that actually does. the files it makes are not valid for the purposes of the packages that are missing them, or that was my experience. back then.

[gmcust3]

[root@vici wanpipe-voicetime-1.0.9]# make oldconfig
make: *** No rule to make target `oldconfig'. Stop.
[root@vici wanpipe-voicetime-1.0.9]# CD
-bash: CD: command not found
[root@vici wanpipe-voicetime-1.0.9]# cd
[root@vici ~]# make oldconfig
make: *** No rule to make target `oldconfig'. Stop.
[root@vici ~]#
[root@vici ~]#

Spoke to Sangoma Tech Specialst and they asked me to install these first :

Wanpipe Driver Minimum Requirements

C developement tools ...(gcc)
C++ developement tools
Make utility
Ncurses library
Perl developement tools
AWK
FLEX
Patch
libtermcap-devel
bison

I am NOT sure what we have already there in Vici.

Creator of VNOW can guide me plz ?

[gardo]

You need to do "make oldconfig" and "make mrproper" on the kernel source directory and not on the wanpipe. The kernel source directory is located in: "/usr/src/kernels".

[gmcust3]

[root@vici ~]# cd /usr/src/kernels
[root@vici kernels]# make oldconfig
make: *** No rule to make target `oldconfig'. Stop.
[root@vici kernels]# ls -la
total 24
drwxr-xr-x 3 root root 4096 Oct 10 00:40 .
drwxr-xr-x 5 root root 4096 Oct 10 00:40 ..
drwxr-xr-x 18 root root 4096 Oct 10 00:40 2.6.18-92.el5.vnow-i686
[root@vici kernels]# make oldconfig
make: *** No rule to make target `oldconfig'. Stop.
[root@vici kernels]#

[gmcust3]

Finally, I got it installed.

An update for them who wants to go for it on VicidialNOW CE 1.2

1) Make sure you have all prerequisite installed.

Just run those commands: (the yum commands)

http://wiki.sangoma.com/wanpipe-linux-a ... quirements

2) You will see :

Installed: kernel-devel.i686 0:2.6.18-164.6.1.el5
Updated: gcc.i386 0:4.1.2-46.el5_4.1
Updated: patch.i386 0:2.5.4-29.2.3.el5
Updated: perl.i386 4:5.8.8-27.el5
Installed: bison.i386 0:2.3-2.1
Installed: gcc-c++.i386 0:4.1.2-46.el5_4.1
Installed: flex.i386 0:2.5.4a-41.fc6

3) Download the latest driver and Reinstalled :

http://downloads.asterisk.org/pub/telep ... 2.1.tar.gz


4) Use make ZAPDIR=/root/zaptel-1.4.12.1 INSTEAD of make ZAPDIR=/usr/src/zaptel-1.4.12.1 if your folder is in root.

5) zttest returns me { after installing VoiceTime } :

--- Results after 914 passes ---
Best: 100.000 -- Worst: 99.844 -- Average: 99.996170, Difference: 99.997322

6) Color gone . Means my CLI is ALL black and white.

Gardo, kindly correct me if I am wrong somewhere.

[But Sangoma GUY jumped out of his chair when he saw Asterisk 1.2 lol ]

Though I am YET to see ANY IMPROVEMENT in sound quality.

[gardo]

LOL. That's a common reaction to people used to using Asterisk as a PBX and not as a dialer. That's why most "stable" and "enterprise" linux distributions prefer older more stable versions of software. Take CentOS and Ubuntu LTS for example.

[gmcust3]

But I get an error as Conference Number NOT found when agents are logging in.

Also, I see too many xpp errors while booting up my server.

But when I run /etc/init.d/zaptel start , it gets normal.

What is xpp errors ?

and why I need to /etc/init.d/zaptel start ?

Zaptel doesn't get start automatically ?

[gardo]

Looks more like an Asterisk configuration issue. It would help if you can post your Asterisk CLI and xpp errors.

Zaptel starts automatically by default. You need to edit /etc/rc.local and add the necessary entries for your Sangoma USB voice timer.

[gmcust3]

I get xpp errors when server is booting up.

Where can I get boot log so that I can send u the logs ?

I have

#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

### uncomment If kernel RAM drive is enabled
#mke2fs -m 0 /dev/ram0
#mount /dev/ram0 /var/spool/asterisk/monitor
#mkdir /var/spool/asterisk/monitor/DONE
#mkdir /var/spool/asterisk/monitor/ORIG

# Disable console blanking and powersaving
/usr/bin/setterm -blank
/usr/bin/setterm -powersave off
/usr/bin/setterm -powerdown

### start time server
/usr/sbin/ntpdate -u 18.145.0.30
### ntpd

### start apache, mysql and vsftpd
/etc/init.d/httpd start
/etc/init.d/mysqld start
/etc/init.d/vsftpd start

### roll the Asterisk logs upon reboot
/usr/share/astguiclient/ADMIN_restart_roll_logs.pl

### clear the server-related records from the database
/usr/share/astguiclient/AST_reset_mysql_vars.pl

### load timer source
modprobe zaptel
#modprobe wcfxo
modprobe ztdummy
ztcfg -vvvvvvvvvvvv

### sybsys local login
touch /var/lock/subsys/local

### sleep for 20 seconds before launching Asterisk
sleep 20

### start up asterisk
/usr/share/astguiclient/start_asterisk_boot.pl

/usr/local/bin/motd.sh > /etc/motd

[gmcust3]

Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: tor2: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: tor2: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_ec_span
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_ec_span
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wct4xxp: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wct4xxp: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wcte12xp: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wcte12xp: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wct1xxp: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wct1xxp: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_rbsbits
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wcte11xp: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wcte11xp: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wctdm24xxp: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wctdm24xxp: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wcfxo: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wcfxo: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wctdm: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wctdm: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_hooksig
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_dtmf_tone
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: wcusb: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: wcusb: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_receive
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_receive
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_qevent_lock
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_ec_chunk
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_transmit
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_transmit
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_unregister
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_unregister
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_hooksig
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_hooksig
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_register
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_register
Nov 27 21:40:08 vici kernel: xpp: disagrees about version of symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: xpp: Unknown symbol zt_alarm_notify
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol xbus_new
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol xbus_activate
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol xbus_disconnect
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol dump_xframe
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol put_xbus
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol xbus_receive_xframe
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol get_xbus
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol xframe_init
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol put_xframe
Nov 27 21:40:08 vici kernel: xpp_usb: Unknown symbol get_xframe
Nov 27 21:40:11 vici kernel: wanpipe_voicetime: Loading WANPIPE VoiceTime (USB) Driver - v1.0.9
Nov 27 21:40:11 vici kernel: wanpipe_voicetime: Probing WANPIPE VoiceTime (USB) device on 4 ...
Nov 27 21:40:11 vici kernel: usbcore: registered new driver wanpipe_voicetime

Output of Var/log/messages

[gardo]

Have you done your research yet? What does google say about those errors?