November 2009 - App_rpt-users - lists.keekles.org

re App_Rpt from USB drive
by Jon Rorke 04 Nov '09

04 Nov '09

Hi All, anyone tried running asterisk/App_rpt from a USB drive? Is it possible? What about using usb drive to install ACID from? Just curious. Jon VA3RQ

2 1

Dyn DNS client
by Carl Swanson 04 Nov '09

04 Nov '09

Hello all... I am slowly building up node 2391 as a remote base, and I am wondering what all of you (that have dynamic IP addresses) do for updating your IP address against a static hostname. I use a Custom DNS service from DynDNS. Are you mostly relying on a hardware router/firewall to update IP addresses, or is there something embedded in the Allstar network structure that maintains a database of updated IP addresses? I will probably have a lot more questions, but these will do for now. 73, Carl, K6CRS ___________________________________________ Carl Swanson, CBRE/CEA/CBNT Broadcast Engineer, Dial-Global 24/7 Formats HAM: K6CRS & VE3SSO / GMRS: WPOJ453 / SHIP: WDD5353 GROL w/SRE: PG-GB-03704 / US Army MARS: AAM9ICA/AAR9MM

2 1

Re: [App_rpt-users] Changes in new version?
by Matt Beasant 03 Nov '09

03 Nov '09

2009/11/3 Ramesh Dhami (VA3UV) <Ramesh(a)va3uv.com> > Hi Matt; > > Not sure why you are using duplex=3 on a repeater node.... have you tried > duplex=2? (this is the correct setting for a repeater node)... > > > From the ACID sysadmin manual... > > duplex=2: Full Duplex with telemetry tones and hang time. > This mode is preferred when interfacing a > repeater. > > > duplex=1 is half duplex, so yes, your COS will be ignored. > > duplex=3 is full duplex, but no repeated audio. > > > Also what is your duplex setting in usbradio.conf? - you want to set that > to duplex=1 so that you can issue dtmf codes while the node is transmitting. > > > Let me know how you make out... > > > Cheers, > > Ramesh. > > Hi there Ramesh and thanks for the reply. Hope all is well with you? I'm using duplex=3 because if I use duplex=2 I get two sources of repeated audio: - One via the RC210 and its RAD board ( I know you're familiar with the Arcom controllers ) - One via app_rpt This causes an echo in the repeated audio due to the different delays. So, I used duplex=3 which stops the app_rpt repeated audio. It all used to work OK.... I will check the usbradio.conf duplex setting maybe thats my problem..... Thanks for the info Ramesh, I'll let you know how it goes.... Cheers and hope to chat again soon, when is the best time to catch you on your node? 73 Matt

1 1

Installing Asterisk/Allstar by hand
by Tony Langdon, VK3JED 03 Nov '09

03 Nov '09

Hi, it's been a while since I've had my AllStar system running. I'm looking to try and get it back up and running. However, it will be located on a virtual server, and will be basically a conference server. Installing using ACID is not an option, so I will need to configure by hand, except I will be moving my old configuration over to the new box. I have been meaning to do this for ages, but I had issues installing Asterisk onto my previous VPS, that my provider wasn't able to help with. The new system is Xen based, so hopefully it will compile and install now. Anyone have any pointers? 73 de VK3JED / VK3IRL http://vkradio.com

2 1

Changes in new version?
by Matt Beasant 03 Nov '09

03 Nov '09

Hi all, I apologies in advance for this epic email but it is necessary for me to describe my setup here to accurately detail the issues I am seeing! I have two repeaters linked with app_rpt nodes but they are set up in different ways. Essentially the two repeaters are the same in that they have Arcom RC210 controllers with audio delay boards to remove squelch tails. I use CTCSS ( PL ) exclusively and my hardware decoders have longish mute times and the audio delay boards take this right out - I have about 600 or 700ms of audio delay to take out the squelch tail. My first repeater has the app_rpt node connected to port 2 of the RC210 and the repeater on port 1. I have linked the two ports via the RC210. The app_rpt node is running duplex=1 and hangtime=0 as the hangtime is taken care of by the RC210. This is node 2250. This node has yet to be upgraded to the latest app_rpt build. On the next repeater, (2237) I needed to find a way of interfacing the USB fob with the RC210 without using the second port and linking them together. The reason for this was that at both sites I have two other (UHF) repeaters that I need to link together using app_rpt too and as the RC210 has only 3 ports, thats not enough to do it via the RC210. So I tried to find a way of directly connecting the USB fob to the repeater radio. So, I picked off the Rx audio on the output of the delay board, T'd off the COS point and connected the PTT output of the fob to the PTT output of the RC210, so it can key the Tx. I was running duplex=3 in my rpt.conf on this new repeater and had a hang time of 5 seconds, with CT's setup and everything was fine. It was possible for a user on the repeater to jump in before the CT had finished and/or during the hang time of the node. This was great as I had the CTs set up to send a "K" on the RC210 ( local activity ) and the app_rpt node send an "R" for remote activity, everyone could tell whether a signal had come in from the local repeater or across the link. Effectively the app_rpt was emulating the RC210. I updated the software yesterday using a fresh ISO downloaded yesterday morning and rebuilt the node software to the latest version. I then copied across my old usbradio.conf file from a backup I made before the install. This then caused a segfault anytime there was any COS activity. I used a default usbradio.conf instead of mine and the segfault stopped. I then changed some of the values to suit my setup and it seems to be working now.( I will have to go back and visit this again as I dont currently know which setting I changed in usbradio.conf that stopped the segfault. ( sorry )) However, things seem to be behaving differently. It seems that the node ignores any COS signals until the hang timer has expired. I tried using different duplex settings in rpt.conf and any hang time I have seems to cause the node to ignore COS until it has expired. To overcome the problem I am currently running zero hangtime, in duplex mode 1 so the CT plays and the carrier drops right away, Its the only way I can get the system to operate without loosing the first 5 seconds of rx audio / COS signal. Duplex mode 3 seems to work in exactly the same way, I cannot tell the difference but mode 3 seemed to work fine before. Has something changed in the way the duplex settings are working or the way in which COS is handled? Again, apologies for the long email but I didnt want to put a bug report in as I am really not certain if what I am seeing is a bug or I am not understanding something right or doing something wrong here, which is most likely! I have seen this segfault behaviour before on nodes we built for a motorsport event's safety comms a couple of weeks ago. Again the pressure was on as it was a live system and I didnt have time to fiddle about with usbradio.conf to see what causes it or fixes it. I need to do more work on this but I am wondering if I am the only one who is seeing this? Thanks for your patience! BTW, I am really interested in some of the features that are currently commented out in the default rpt.conf file - presume some sort of analogue input / data aquisition device is needed to implement these features? Thanks to all the developers for all their hard work and hours of effort, it is really appreciated here! Best 73, Matt G4RKY

1 0

Fwd: Problem with iax?
by Anthony Percy 01 Nov '09

01 Nov '09

Hi Steve, Sorry for the late reply, I have been away in Brisbane.. I think I have found the problem, it looks like I have not been running rc.updatenodelist to create the rpt_extnodes file!!! As you can guess I am still learning.... Maybe we should put some debug statement in the code at line 4190 of app_rpt.c /* if file does not exist */ if (stat(myrpt->p.extnodefile,&mystat) == -1) { if (ourcfg) ast_config_destroy(ourcfg); ourcfg = NULL; ast_mutex_unlock(&nodelookuplock); return(NULL); } e.g if the stat() fails.????? e.g rc.updatenodelist is not running etc (assuming this is the correct part of the code) What do you think?? Also is there a chance I could get a development allstar node number as I need to test some configs before we put them on node 2393, the club 70CM repeater ? I have applied for one but I never get the email. Regards Anthony VK2ACP On Tue, Oct 20, 2009 at 8:58 PM, Stephen Rodgers < hwstar(a)rodgers.sdcoxmail.com> wrote: > Anthony Percy wrote: > > Hi Steve, > > Thanks for the reply. The strange thing is that when we turn the > debugging > > on we see no error messages at all!!! > > Neither is there anything in the log files... All we see is a "psuedo > .... > > hangup" when we call allstar. Calling echolink creates a log list of > > connection messages and it works fine.. > > > > How do we check if the node list is updating correctly? > > > > regards > > > > AP > > > > On Tue, Oct 20, 2009 at 5:57 AM, <hwstar(a)rodgers.sdcoxmail.com> wrote:s > > > > >>> From: Anthony Percy <anthcp(a)gmail.com> > >>> Date: 2009/10/19 Mon AM 01:24:32 PDT > >>> To: app_rpt-users(a)qrvc.com > >>> Subject: [App_rpt-users] Problem with iax? > >>> > >>> Hi all, > >>> We recently built a new allstar asterisk repeater using a svn > development > >>> build from a few weeks ago. ( I did have a small prob with the build > but > >>> that was easy to fix by altering a makefile, I can elaborate if > required) > >>> It works fine as a repeater with the DMK fob but when we call an > allstar > >>> node it fails. However, when we call a echolink server it works fine. > >>> We parsed our older xipar config files to build the new configs for the > >> svn > >>> build, I guess we may have missed something for the iax to work? > >>> It also seems to register ok on the allstar stats site... > >>> Any suggestions? > >>> When we put our older allstar repeater back in place it works fine on > >>> allstar so it can't be a network or firewall issue... > >>> > >>> Regards > >>> > >>> Anthony Percy, VK2ACP > >>> > >>> Chifley Amateur Radio Club. > >>> > >>> > >> > >> There should be connect errors displayed on the Asterisk console. It > would > >> be helpful to see those. > >> > >> A hint: Maybe your node list is not updating correctly. > >> > >> Steve > >> WA6ZFT > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users(a)qrvc.com > >> http://qrvc.com/mailman/listinfo/app_rpt-users > >> > >> > >> > > > Use the following Asterisk cli commands to enable debugging and a more > verbose output from Asterisk > > core set verbose 4 > rpt debug level 5 > > The node list should be located in file /var/lib/asterisk/rpt_extnodes > > It is a text file so you can use text tools to view it. > > The file gets downloaded every 10 minutes, and the top of the file should > contain two recent time stamps which are no > more than 30 minutes old. > > The other thing to check is if the system is registering properly. > If you use the following, Asterisk CLI command, you should get something > similar to this: > > radios*CLI> iax2 show registry > Host dnsmgr Username Perceived Refresh > State > 67.xx.xx.xx:4569 N A2010 72.xx.xx.xx:4569 60 > Registered > > It's 3 AM here, and I can't sleep. > > Steve > WA6ZFT > > > >

1 0