<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Ahhh... well.... ahhhh...<br><br>Since it doesnt seems to be a problem with Asterisk, it would unfortunately point<br>to a problem with the USB hardware on your PC, or some sort of weird driver<br>incompatibility with Linux. I know it has done this on 2 machines. Over the years<br>I have had MANY machines that have exhibited similar and even stranger problems<br>with their USB.<br><br>USB just isnt reliable. We know it. Thats why we dont and never have recommended<br>the use of USB devices on a mountain top or other hard to get to locations. <br><br>USB, it isnt just for breakfast anymore...... :-)<br><br>JIM WB6NIL<br><br><br>> Date: Sun, 19 Sep 2010 10:33:43 -0400<br>> From: jrorke@cogeco.ca<br>> To: app_rpt-users@qrvc.com<br>> Subject: Re: [App_rpt-users] node stops talking to URI<br>> <br>> The URI appears to be off with no lights on when this happens.<br>> <br>> On 9/19/2010 10:03 AM, Ken wrote:<br>> > This sounds like a case where the BIOS (or CENTOS?) decides to shut off the<br>> > USB port for power management reasons after seeing no data for an extended<br>> > period of time ... does the green light just stop blinking or go out<br>> > altogether? Maybe you could program the links to send some silence or<br>> > something every 5 minutes and see if that keeps it alive... as an<br>> > experiment.<br>> ><br>> > Ken<br>> ><br>> ><br>> ><br>> >> -----Original Message-----<br>> >> From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users-<br>> >> bounces@qrvc.com] On Behalf Of REDBUTTON_CTRL<br>> >> Sent: Sunday, September 19, 2010 8:50 AM<br>> >> To: app_rpt-users@qrvc.com<br>> >> Subject: [App_rpt-users] node stops talking to URI<br>> >><br>> >> Hi All, I have been having this problem for quire some time.<br>> >> I have a server box that has 2 nodes on it with URIs.<br>> >> The first node is 2379 (USB0) and the second is 2416 (USB1).<br>> >> The problem is the first node seems to stop talking to the URI<br>> >> randomly.<br>> >> The computer says its still connected to the URI but the URI wont key<br>> >> the radio nor any RX audio comes through when this happens.<br>> >> Asterisk reports the 2 nodes connected internally when its in this<br>> >> faild<br>> >> mode and I can get audio from the second node 2416 if I am connected to<br>> >> 2379 with an other node but no audio is transmitted out on 2379.<br>> >><br>> >> The 2 nodes are simplex nodes. These 2 nodes create a link bridge to<br>> >> connect 2 repeaters together.<br>> >> I normally have a start up macro to connect the 2 nodes and its a perm<br>> >> link.<br>> >> When the first node stops talking to the URI the kink goes down between<br>> >> the 2 repeaters.<br>> >><br>> >> We tried swapping the 2 URIs to see if the problem follows the URI but<br>> >> no it always happens on the first node 2379.<br>> >><br>> >> The only way I know how to get it going again is to remotely reboot the<br>> >> box. Nothing else will get the node working again.<br>> >><br>> >> The original box (p4 3 gig IBM) was set up the same way and the same<br>> >> thing was happening once every 2 to 3 weeks.<br>> >> Since then that original box died- ps failure so I rebuilt the box in<br>> >> July on an other machine (p4 3gig HP).<br>> >> Now we get the same failure but much more often. Now it happens on the<br>> >> average once aver 2 days and some times within 8 hours of a re boot!<br>> >><br>> >> When I rebuilt the node I used the latest Acid cd at the time and re<br>> >> did<br>> >> all the conf files with the latest configs so no copying from the<br>> >> original backup files. So this is 2 different computers with 2<br>> >> different<br>> >> builds with the same problem.<br>> >><br>> >> Here's the node info :<br>> >><br>> >> app Rpt version 0.255<br>> >> These are migrated nodes.<br>> >> The URIs are original CM108 units.<br>> >><br>> >> I did report this issue some time ago but nobody has any ideas as to<br>> >> whats going on. This time I knbow its got to be something in software<br>> >> on<br>> >> the first node.<br>> >> Sorry for the long post but this has been nagging me for some time and<br>> >> now its getting to the point that I have to reboot the box before nets<br>> >> to make sure its working and even then there is no guarantee it will<br>> >> stay connected.<br>> >><br>> >> Thanks,<br>> >><br>> >> Jon VA3RQ<br>> >><br>> >><br>> >> _______________________________________________<br>> >> App_rpt-users mailing list<br>> >> App_rpt-users@qrvc.com<br>> >> http://qrvc.com/mailman/listinfo/app_rpt-users<br>> ><br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@qrvc.com<br>> http://qrvc.com/mailman/listinfo/app_rpt-users<br> </body>
</html>