Vicibox 3.1.5 wanpipe voicetime install

[andre]

Hello, i'm trying to install and test vicibox redux 3.1.5 64bit on a single physical machine with a sangoma ut50 voicetime usb stick as additional hw (it's a test made to try this sangoma item)

After os-install and vicibox-install commands i'll get this "warning" after choosing:
OS Update: n
Stop Firewall: y
Use SVN Code: y
Install Core DB: y
Install Web App: y
- InstallVTiger: n
Install Telephony: y
- Additional Server: n
- Install Wanpipe: n
- Install Voicetime: y



And after reboot:



I think I'm missing something in install/conf procedure :\

[williamconley]

try again without the USB stick and see if it works.

[andre]

yes, without it works

[williamconley]

see if you can identify the file in question and use chmod +x filename

or just chmod +x the entire script directory in which it resides (chmod +x /path/to/directory -R)

before running the install

[andre]

I've tried to set +x to / -R just for test but the result still the same

[Kumba]

Type modprobe wanpipe_voicetime, then 'tail /var/log/messages'. Then dahdi_test

[williamconley]

maybe the vicidial script is CALLING a script that's not executable.

perhaps you could try chmod +x on the entire folder containing the wanpipe directives.

[andre]

ok, but I'm on a vm at home without the stick atm (10.13 pm here)

Code: Select all

vici-test:~ # modprobe wanpipe_voicetime
vici-test:~ # tail /var/log/messages
Jan 20 20:58:18 vici-test sshd[12431]: Server listening on :: port 22.
Jan 20 20:58:20 vici-test /usr/sbin/cron[12809]: (CRON) STARTUP (V5.0)
Jan 20 20:58:20 vici-test SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jan 20 20:58:20 vici-test SuSEfirewall2: batch committing...
Jan 20 20:58:20 vici-test SuSEfirewall2: Firewall rules successfully set
Jan 20 20:59:05 vici-test sshd[12960]: Accepted keyboard-interactive/pam for root from 192.168.223.1 port 1588 ssh2
Jan 20 20:59:18 vici-test kernel: [  331.819098] dahdi: Telephony Interface Registered on major 196
Jan 20 20:59:18 vici-test kernel: [  331.819120] dahdi: Version: 2.4.0
Jan 20 20:59:18 vici-test kernel: [  331.866454] wanpipe_voicetime: Loading WANPIPE VoiceTime (USB) Driver - v1.0.9
Jan 20 20:59:18 vici-test kernel: [  331.867593] usbcore: registered new interface driver wanpipe_voicetime
vici-test:~ # dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
99.968% 99.911% 99.967% 99.966% 99.937% 99.968% 99.967% 99.910% ^C
--- Results after 8 passes ---
Best: 99.968 -- Worst: 99.910 -- Average: 99.949145, Difference: 99.990404

@william: tried +x recursive from / but nothing

[williamconley]

I'm not sure doing it from / recursive is valid, although I guess for a test it could be interesting.

Failing that, you'll have to check the logs and script and find the actual command tossing the error.

Personally, I'd go with Kumba's version where you simply execute the appropriate commands and modify the appropriate files manually after installation to get it going NOW (but if you want to do the work, find the flaw and let Kumba know, that would be cooler, actually ). Depends on whether you need it UP NOW or whether you need a solid install for later for some reason.

[Kumba]

That does me no good unless you try this on the actual hardware. I do not know that the voicetime module will work correctly in a VM.

When the voicetime driver loads properly, you should see something like this:

Jan 21 16:29:39 dial1 kernel: wanpipe_voicetime: Loading WANPIPE VoiceTime (USB) Driver - v1.0.9
Jan 21 16:29:39 dial1 kernel: wanpipe_voicetime: Probing WANPIPE VoiceTime (USB) device on 2 ...
Jan 21 16:29:39 dial1 kernel: usbcore: registered new interface driver wanpipe_voicetime


The second thing to check is that the ZAP_MOD= part in /etc/init.d/vicidial is wanpipe_voicetime and not dahdi_dummy

[andre]

you're right but I can touch the real hw only on next monday :\
(on a vm the voicetime module work but with ridicolous scores due to its virtual usb passtrough)

in /etc/init.d/vicidial

Code: Select all

ZAP_MOD=wanpipe_voicetime

p.s. I've tried to set +x -R on /usr /var /etc /lib before running the installer and nothing

[Kumba]

The driver is not finding the USB module through your virtual machine. Your output when you load the module should be similar to what I pasted. Most notably is where it says finding device on USB X.

Can't help much beyond that.

[andre]

temporary solved in this way:

Code: Select all

vicibox-install

on 'wanpipe voicetime installed' answered 'n' than after install/config

Code: Select all

modprobe wanpipe_voicetime
nano /etc/init.d/vicidial


and changed dahdi_dummy into

Code: Select all

ZAP_MOD=wanpipe_voicetime


reboot and that's all

works both on virtual and physical (but with an accuracy of 30% on vm :p )

I was not able to address the missing 'x' permission on the script/dir btw..

[williamconley]

wait until you load the virtual one up with more than 5 agents. 30% will be the least of your worries.

[andre]

I have 20 agent in manual dial (15 active calls usually) on a test vm but with dahdi_dummy, not the usb stick :p and it's around 99,8 - 99,3... not bad for test but not good for production as well :p
it can be nice to give a try with vsphere usb hw passtrough and paravirt ops in the spare time.. but it's only for fun and test

[williamconley]

15 calls is not bad, but manual dialing is not "vicidial" per se. (OK, that's not fair, actually manual dialing in vicidial still beats the heck out of the alternative ... paper? spreadsheets? eek).

but WHY do you want to stick with manual and virtual? get 'em on a P4 and you can run 5 agents on each box with full auto!

[andre]

because they're not on a proper outbound campaing of teleselling
It's a 'online teaching & tutoring' thing based on appointments with registration on demand.. and i can make some useful experience before exporting it on our real-outbound and switch all seats from the actual avaya pbx to vici
..and last but not least the it infrastructure is under rebuild/construction so this vm runs on my laptop atm and i cannot ask more to it :p

[williamconley]

Yep. I remember those days. I had a tech who used to love to run it on his laptop. LOL

Enjoy the run. And remember that since you're virtual ... you can install it 50 times and dump it and get so used to installing it that you can do it with your eyes closed (and make ALL the mistakes you can make, so you'll know how to recognize them later when you do it by accident!)

[will_brook]

Hi,

I've installed the Sangoma Voicetime UT50 USB device on A ViciBox VERSION: 2.4-362a
BUILD: 120316-1203, single server 32 bit. When I go through Sangoma's recommendations for checking it's being used properly I don't get the results I'd expect.

cat /proc/dahdi/1

span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: HRtimer) 1" (MASTER)

According to Sangoma this should be:

Span 1: WANVTIME/1 "WANVTIME/1 (source: wanpipe_voicetime) 1" (MASTER)

Also within the Asterisk cli I ran dahdi show status, I get the following results:

Description Alarms IRQ bpviol CRC4
DAHDI_DUMMY/1 (source: HRtimer) 1 UNCONFIGUR 0 0 0

Do these results mean that Dahdi is using the server hardware timer rather than USB timer.

I've checked that the USB device is recognised in the logs, this seems good. I also checked the /etc/init.d/vicidial file and noticed that ZAP_MOD=wanpipe_voicetime is set. I also made sure that the sangoma voicetime options was selected during the vicibox install.

Although dahdi_test results seem ok:

Best: 99.999 -- Worst: 99.995 -- Average: 99.998365, Difference: 99.998366

Is this installed correctly for vicidial or am I missing something?

Regards

Will

[will_brook]

Here are the results from the log after running modprobe wanpipe_voicetime:

Apr 21 14:01:15 fb-demo01 kernel: [ 1712.972845] wanpipe_voicetime: Loading WANPIPE VoiceTime (USB) Driver - v1.0.9
Apr 21 14:01:15 fb-demo01 kernel: [ 1712.972874] wanpipe_voicetime: Probing WANPIPE VoiceTime (USB) device on 2 ...
Apr 21 14:01:15 fb-demo01 kernel: [ 1712.980106] usbcore: registered new interface driver wanpipe_voicetime

So this seems ok. But still not convinced it's working properly.