Just did a clean install of ACID on a Compaq DL380 server This is a Box with Dual Pentium 733's and no built on USB. Also to make this more fun I'm using a USB PCI card to get USB support. The card has an NEC chipset and I can provide more details as wanted. It reliably does not work on bootup. What I mean by that the USB FOB is not producing any audio on it's output.. It has the normal flashing light on the fob and the software behaves like usual when sending audio (no errors) or anything on screen that looks out of ordinary.. Now if I manually do an: rpt restart and then radio key and radio unkey a few times it startes to work and then works just fine after that.. If I restart asterisk or the entire box the problem comes back. Has anyone else ever experienced this or soething like it? I will try another USB card and moving the card around to different interrups.. Just weird... and that it works after slapping it around with commands... Michigan Broadband Systems Inc. "Always Connected" (734)527-7150 Steve's cellphone: (734)904-1811 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Steve You can probably find some old posts by me saying that I have simply not been able to get a PCI USB card to talk to the URI fob. I have tried 4 different cards with at least three different chip sets. So far I have only been able to use the mother board USB. The computer is either a Dell PE2650, or PE2850 (64 bit) both with dual XEON processors (and a really high-powered PCI-X type of card cage, for up to 3 PCI cards). The PCI card works fine with a keyboard or mouse etc. With the fob it goes into the "slow blink" mode. I am guessing this is the USB interface doing the three re-tries that the USB2 standard requires - and then sending a failed indication. I use a hub to multiply ports - that usually works. Once in a great while a re-start fails. Sometimes just one fob does not start - pulling the usb cable out and plugging it back in usually fixes that. I have not tried the "rpt restart" command ... will give that a shot some time. In a related note - With astres.sh I often have trouble - sometimes serious trouble ("kernel panic" and shut down) it is related to the thread that talks to the fob (usb channel driver). To restart, I always do astdn.sh followed by astup.sh - that is pretty reliable. Looking at the help, I see I should be using "rpt reload" from within the CLI, if all I am doing is messing with the config ... so I just learned something - thanks 73 Ken BTW - looking in the C-Code for the usb channel I see that there is a jitter buffer config (like in the IAX channel). This is something I thought I might play with some time but have not yet tried it. Have you looked at it?
-----Original Message----- From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users- bounces@qrvc.com] On Behalf Of Steve Gladden Sent: Saturday, May 08, 2010 9:12 PM To: app_rpt-users@qrvc.com Subject: [App_rpt-users] Have to manually crank the usb fob to make it work?
Just did a clean install of ACID on a Compaq DL380 server This is a Box with Dual Pentium 733's and no built on USB.
Also to make this more fun I'm using a USB PCI card to get USB support. The card has an NEC chipset and I can provide more details as wanted.
It reliably does not work on bootup. What I mean by that the USB FOB is not producing any audio on it's output.. It has the normal flashing light on the fob and the software behaves like usual when sending audio (no errors) or anything on screen that looks out of ordinary..
Now if I manually do an:
rpt restart
and then
radio key and radio unkey
a few times it startes to work and then works just fine after that..
If I restart asterisk or the entire box the problem comes back.
Has anyone else ever experienced this or soething like it?
I will try another USB card and moving the card around to different interrups..
Just weird...
and that it works after slapping it around with commands...
Michigan Broadband Systems Inc. "Always Connected"
(734)527-7150
Steve's cellphone: (734)904-1811
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
Ken wrote:
Steve
You can probably find some old posts by me saying that I have simply not been able to get a PCI USB card to talk to the URI fob. I have tried 4 different cards with at least three different chip sets. So far I have only been able to use the mother board USB.
The computer is either a Dell PE2650, or PE2850 (64 bit) both with dual XEON processors (and a really high-powered PCI-X type of card cage, for up to 3 PCI cards). The PCI card works fine with a keyboard or mouse etc. With the fob it goes into the "slow blink" mode. I am guessing this is the USB interface doing the three re-tries that the USB2 standard requires - and then sending a failed indication.
I use a hub to multiply ports - that usually works. Once in a great while a re-start fails. Sometimes just one fob does not start - pulling the usb cable out and plugging it back in usually fixes that.
I have not tried the "rpt restart" command ... will give that a shot some time.
In a related note -
With astres.sh I often have trouble - sometimes serious trouble ("kernel panic" and shut down) it is related to the thread that talks to the fob (usb channel driver).
To restart, I always do astdn.sh followed by astup.sh - that is pretty reliable. Looking at the help, I see I should be using "rpt reload" from within the CLI, if all I am doing is messing with the config ... so I just learned something - thanks
73
Ken
BTW - looking in the C-Code for the usb channel I see that there is a jitter buffer config (like in the IAX channel). This is something I thought I might play with some time but have not yet tried it. Have you looked at it?
-----Original Message----- From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users- bounces@qrvc.com] On Behalf Of Steve Gladden Sent: Saturday, May 08, 2010 9:12 PM To: app_rpt-users@qrvc.com Subject: [App_rpt-users] Have to manually crank the usb fob to make it work?
Just did a clean install of ACID on a Compaq DL380 server This is a Box with Dual Pentium 733's and no built on USB.
Also to make this more fun I'm using a USB PCI card to get USB support. The card has an NEC chipset and I can provide more details as wanted.
It reliably does not work on bootup. What I mean by that the USB FOB is not producing any audio on it's output.. It has the normal flashing light on the fob and the software behaves like usual when sending audio (no errors) or anything on screen that looks out of ordinary..
Now if I manually do an:
rpt restart
and then
radio key and radio unkey
a few times it startes to work and then works just fine after that..
If I restart asterisk or the entire box the problem comes back.
Has anyone else ever experienced this or soething like it?
I will try another USB card and moving the card around to different interrups..
Just weird...
and that it works after slapping it around with commands...
Michigan Broadband Systems Inc. "Always Connected"
(734)527-7150
Steve's cellphone: (734)904-1811
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
Try this version of astres.sh and tell us if it panics or not. #! /bin/bash if [ -e /var/run/asterisk.ctl ] then killall safe_asterisk service asterisk stop sleep 2 service asterisk start else echo "Asterisk is not running!" fi
Try this version of astres.sh and tell us if it panics or not. #! /bin/bash if [ -e /var/run/asterisk.ctl ] then killall safe_asterisk service asterisk stop sleep 2 service asterisk start else echo "Asterisk is not running!" fi ================================================ I tried it 5 times and 4 of them worked. The 5th time, asterisk died (I had two (or three) remote PuTTY windows open at the time) It went into a repeated restart mode - I think this is different than the sound thread problem that led to the kernel panic. Somehow, mpg123 that I have on my system seems to have been a factor - I did not notice if the system was playing sound at the time I did the restart. I don't think so. (not everything is shown below, I tried some astdn and astup commands too) [root@ke2n ~]# astres_new.sh Shutting down asterisk: [ OK ] Starting asterisk: [ OK ] [root@ke2n ~]# Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. mpg123: no process killed Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. mpg123: no process killed Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. mpg123: no process killed Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. astres_new.sh Shutting down asterisk: [FAILED] Starting asterisk: [ OK ] [root@ke2n ~]# Asterisk ended with exit status 1 =========================================================================== Asterisk was not running at this point so I rebooted the machine. ================================================================== I did learn that it is not necessary to restart things just to load a modified config file Use "rpt reload" for that... Ken 27021 KE2N/R
participants (3)
-
Ken -
Stephen Rodgers -
Steve Gladden