I installed a fresh vicibox-3.1.a with the new SVN-Code. This time I wanted to set it up more professional in that I try to get this usb-voicetime-stick running - to defend myself: back in those days with 40 agents, vicinow and ztdummy were fine, but I read so many good things about these voicetime sticks relating to MOH and time critical actions, that I thought, if I already got a cluster, why not adding usb-voicetime ...
I installed vicibox 3.1.a because I had no installation issues and the "sagoma-script" (saying YES to usb voicetime) finished with no errors at all (these ugly perl errors).
After that, I wanted to see the performance, so I read everything I could find about DAHDI and its tools - and I was really disappointed that I had not so good results as expected on an empty telephony server with usb-voicetime compared to a server with 50 agents on it, 20 simultanous calls, MOH and recording - and dahdi without voicetime. On the "dummy"-system i got 99.91 as average from dahdi_test and on the new "sangoma"-system I got 99.97 and worse! I could not believe that this is what I should have expected - I expected values around 100% (when there is nobody logged in at least!)
That's why I suspect, there is something missing. I already follwed the thread of kumba ( http://www.vicidial.org/VICIDIALforum/v ... highlight= )
getting the other kernels (and stuff) - but right by now I am not sure if I mix it all up - sangoma cards , voicetime sticks , bad results.
Maybe the PCI-Interfaces are lame, there is no interrupt-sharing and so I decided to post here some screen outputs and you might let me know if everything is allright, okay
?
After booting the machine, dmesg gives me:
- Code: Select all
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.4.0
wanpipe_voicetime: Loading WANPIPE VoiceTime (USB) Driver - v1.0.9
wanpipe_voicetime: Probing WANPIPE VoiceTime (USB) device on 2 ...
usbcore: registered new interface driver wanpipe_voicetime
dahdi: Registered tone zone 0 (United States / North America)
.
.
- looks good to me -
bootscreen shows the following
- Code: Select all
some lines about Invalid Rules udev/dahdi.rules .... (shall I be concerned?)
Loading DAHDI drivers
Starting Sangoma Wanrouter driver
ERROR: Wanpipe Configuration file not found
/etc/wanpipe/wanpipe1.cfg
Sangoma failed to load! Fallback to wanpipe_voicetime module !
Configuring DAHDI Hardware
Dahdi ver. Tools 2.4
Dahdi ver. 2.4
Channel map
0 channels to configure
some lines of interest may be when restarting vicidial
- Code: Select all
/etc/init.d/vicidial restart
2735 pts/4 00:00:00 asterisk
Stopping asterisk
Asterisk stopped
dahdi 199412 1 wanpipe_voicetime
crc_ccitt 1403 1 dahdi
Router is already stopped !
wanpipe_voicetime 6931 0
dahdi 199412 1 wanpipe_voicetime
usbcore 192087 4 wanpipe_voicetime,uhci_hcd,ehci_hcd
dahdi 199412 0
crc_ccitt 1403 1 dahdi
Stopped Vicidial
Loading DAHDI drivers
Starting Sangoma wanrouter driver
ERROR: Wanpipe configuration file not found:
/etc/wanpipe/wanpipe1.conf
Sangoma failed to load! Fallback to wanpipe_voicetime module!
Configuring DAHDI Hardware
DAHDI Tools Version - 2.4.0
DAHDI Version: 2.4.0
Echo Canceller(s):
Configuration
======================
Channel map:
0 channels to configure.
rolling Asterisk messages log...
rolling Asterisk event log...
rolling Asterisk cdr logs...
mv: cannot stat `/var/log/asterisk/cdr-csv/Master.csv': No such file or directory
mv: cannot stat `/var/log/asterisk/cdr-custom/Master.csv': No such file or directory
rolling Asterisk screen log...
rolling Asterisk root screen log...
mv: cannot stat `/root/screenlog.0': No such file or directory
rolling Asterisk var log screen log...
mv: cannot stat `/var/log/asterisk/screenlog.0': No such file or directory
FINISHED... EXITING
- conferences reset
- vicidial_conferences reset
- vicidial_manager delete
- vicidial_auto_calls delete
- vicidial_live_agents delete
- vicidial__users delete
- vicidial_campaign_server_stats delete
- vicidial_hopper delete
Starting Asterisk started screen
changed directory
started new screen session
detached screens
raised ulimit open files
Asterisk started... screen logging on
Started Vicidial
a lsmod gives this:
- Code: Select all
Module Size Used by
wanpipe_voicetime 6931 0
dahdi 199412 1 wanpipe_voicetime
crc_ccitt 1403 1 dahdi
edd 8720 0
mperf 1255 0
loop 14329 0
dm_mod 72644 0
sg 27508 0
sr_mod 14351 0
cdrom 37760 1 sr_mod
ata_generic 2743 0
ata_piix 20105 0
tg3 134181 0
hpwdt 6295 0
e100 33772 0
hpilo 7458 0
iTCO_wdt 9990 0
shpchp 29880 0
libata 185636 2 ata_generic,ata_piix
iTCO_vendor_support 2570 1 iTCO_wdt
pci_hotplug 27789 1 shpchp
pcspkr 1614 0
e752x_edac 12786 0
floppy 57461 0
edac_core 40558 1 e752x_edac
container 2503 0
button 5417 0
uhci_hcd 25852 0
ehci_hcd 52739 0
cciss 95054 3
scsi_mod 159145 4 sg,sr_mod,libata,cciss
usbcore 192087 4 wanpipe_voicetime,uhci_hcd,ehci_hcd
fan 3539 0
thermal 17325 0
processor 40471 0
thermal_sys 14703 3 fan,thermal,processor
dahdi_test on this system says:
- Code: Select all
Opened pseudo dahdi interface, measuring accuracy...
99.975% 99.970% 99.975% 99.976% 99.975% 99.975% 99.975% 99.976%
99.975% 99.974% 99.975% 99.975% 99.975% 99.975% 99.976% 99.975%
99.975% 99.975% 99.976% 99.974% 99.975% 99.975% 99.975% 99.976% ^C
--- Results after 24 passes ---
Best: 99.976 -- Worst: 99.970 -- Average: 99.974831, Difference: 99.974832
dahdi_test on a running system (vicibox 3.0.6, no usb voicetime) gives this:
- Code: Select all
Opened pseudo dahdi interface, measuring accuracy...
99.958% 99.974% 99.997% 99.961% 99.971% 100.000% 99.994% 99.995%
99.638% 99.971% 99.655% 99.998% 99.995% 99.993% 99.998% 99.644%
99.971% 99.991% 99.644% 99.994% 99.987% 99.986% 99.619% 99.991% ^C
--- Results after 24 passes ---
Best: 100.000 -- Worst: 99.619 -- Average: 99.913494, Difference: 100.011874
Question: Do I have usb voicetime installed correctly ?
If you guys can help me out, I swear I will order the other three sticks (that I will need for my cluster if i get it up and running performantly) here from the vicidialgroup !!! Is that a deal ?
best wishes,
r0n