- App_rpt-users - lists.keekles.org

Monitoring an allstar node?
by Michael Graff 21 Sep '12

21 Sep '12

I have a working hub-type configuration, which will work well enough until I get the radio hardware hooked up. :) I have noticed some people are able to find out what node is transmitting by, I assume, monitoring something on their local system. Can anyone give me a hint about how this might work? I would love to have a GUI client that showed graphically the node interconnections, which node is keying up, etc. If there is a lower level protocol I could use (through IAX2, or some call-out from app_rpt) could I be given a hint on where to start looking? --Michael

1 0

ok...
by Bryan D. Boyle 21 Sep '12

21 Sep '12

so...got it registered...and can connect between node connected on one internal server on iax port 4570 to another on iax port 4569...it shows up in the node list on the mother ship... However...using the cli command 'rpt fun node dtmf-function' between them...nada. do I have to specify somewhere the proper ports@IP (ie 192.168.1.98:4569 and vice versa) to get commands to pass between the servers? Sorry for what may seem bloody obvious... BB

3 3

Re: [App_rpt-users] changing IAX port
by Bryan D. Boyle 21 Sep '12

21 Sep '12

i was looking up on allstarlink for where to plug in the port number on jims's side, but didn't see anywhere to specify it. everything works from my side...got the router and firewall set up right, etc...just missing that one ifinal piece of the puzzle. thanx. -- Bryan Sent from my iPhone please forgive misspellings... On Sep 21, 2012, at 4:42, "Ken" <ke2n(a)cs.com> wrote: > The node:port format is for the bindaddr= command, of course. For bindport= > you just put in the port number. > > Ken > > -----Original Message----- > From: app_rpt-users-bounces(a)ohnosec.org > [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ken > Sent: Friday, September 21, 2012 4:40 AM > To: 'Bryan D. Boyle'; 'app_rpt mailing list' > Subject: Re: [App_rpt-users] changing IAX port > > Brian > It's in iax.conf > > You can use the keyword "bindport=" or you can add the port to the number in > "bindaddr=" (node:port) > > This port number needs to be in your router too and in the registration > server (use the portal to specify the port you selected) > > Also, if you have any non-registering nodes in that system, the port number > needs to be explicitly used in identifying those nodes to the other system. > > 73 > > Ken > > >> -----Original Message----- >> From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users- >> bounces(a)ohnosec.org] On Behalf Of Bryan D. Boyle >> Sent: Thursday, September 20, 2012 10:17 PM >> To: app_rpt mailing list >> Subject: [App_rpt-users] changing IAX port >> >> I'm installing a second computer here to drive Yet More RF out of the > House >> of RF here...and since I'm doing so...wondering where on the mother >> ship > do >> you change the port that IAX is configured for. >> >> I think I see where, in the config files, you change it...but, >> obviously, > the >> head end has to know where the handshake is supposed to go. >> >> Am I missing something? Not that that would be out of character > (according >> to my bride...), but...just thought I'd ask. >> >> Tnx >> >> Bryan WB0YLE >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

2 2

Re: [App_rpt-users] URI frustration
by Anthony Percy 21 Sep '12

21 Sep '12

Hi Jay, The reason I replied is I have been trying ( and I think got a working solution) to fix a similar problem for weeks, talk about CM108 URI Frustration.....! What happened is this... 1. Our VK2CRZ allstar node 2393 has been working for a few years now but the PC is a bit old... So we bought a new Intel H55 chipset based i3 mobo a few months ago to replace it (Model no is ASUS P7H55D-M Pro mobo). 2. We loaded new ACID install, copied the existing /etc/asterisk files, unplugged the USB cable existing URI connected to the repeater and connected to the new Allstar PC.... 3. We found the COR and PTT worked fine but the audio was just hum.. :-( 4. Plugged the URI back into the existing repeater and it works fine!!! 5. Looks like an audio path problem.... but the URI green LED was flashing slower and after a few cold boots we noticed the new boot now had the URI green LED flashing faster and now the repeater audio worked fine!!! Did a warm reboot , URI green was flashing slower and repeater audio was now hum again....No matter what I did could I get the URI green LED flashing faster again on the ACID install.... My research indicated that there is some sort of conflict between the URI sound driver (snd-usb-audio) and the snd-hda-intel driver that is used for the Realtek ALC886 sound card on this H55 express chipset motherboard...And maybe a probelm with the H55 USB bus... This is what I tried... 1. Disable the Sound card in the Bios... It seems that as soon as the snd-hda-intel drivers are loaded, your URI sound drivers are stuffed and now unreliable, so that was no fix. 2. Gave up on Centos/ACID and setup up latest Debian 6.x on the ASUS mobo . Downloaded allstar source code, and setup dev enviroment. 3. Compiled Zaptel first... Compiled OK but zaptel udev was broken on reboot. Easliy fixed by changing zaptel.rules "=" lines to"=="!!! 4. Compiled asterisk OK and did make install, All OK. 5. Tried loading Realtek ALC886/snd-hda-intel sound card drivers.. Worked fine but they TOTALLY removed snd-usb-audio URI sound drivers!!!! 6. Noticed that Realtek ALC886/snd-hda-intel sound card drivers is really a ALSA driver install with configure options. Googled and found options to reload snd-usb-audio drivers.... e.g download from alsa-projects.org; alsa-driver-1.0.25 and ./configure --enable-dynamic-minors 7. Disable sound card in bios and reboot. URI drivers are now working again... 8. Now load alsa-oss-1.0.25 drivers or the chan_usradio driver complains about missing devices...and cold reboot. Now allstar seems to work ok on the URI card... Warm reboots don't work all the time however in resetting URI card. Only cold reboot will reset the URI, in that a warm reboot may end up with the URI green leds flashing slowly but a cold reboot 9/10 times now seems to set the URI green leds flashing at the normal rate... Sometimes a "alsa force-reload" will help reset the URI I hope this is not a general problem but is one that is mobo/URI specific.... Hope it helps Anthony, VK2ACP Jay Urish jay(a)unixwolf.net 1:00 PM (2 hours ago) Yes, my LED appears to be flashing at the right rate. I just have an audio path problem.. I have the COR and PTT right.. Subject: Re: [App_rpt-users] URI frustration Message-ID: <CA+rLymGUn_jFFBfrJFZQ1=u3AFW621jhPAs9S57Xz6=SfGZL4g(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi Jay, I had a similar problem recently. on a repeater that worked perfectly using an older motherboard... ... To check if its the same problem, is the URI green LED flashing at its normal rate, e.g. 3-4 times a second or is it a lot slower? And are you using the current ACID install???? Regards Anthony, VK2ACP

3 3

changing IAX port
by Bryan D. Boyle 21 Sep '12

21 Sep '12

I'm installing a second computer here to drive Yet More RF out of the House of RF here...and since I'm doing so...wondering where on the mother ship do you change the port that IAX is configured for. I think I see where, in the config files, you change it...but, obviously, the head end has to know where the handshake is supposed to go. Am I missing something? Not that that would be out of character (according to my bride...), but...just thought I'd ask. Tnx Bryan WB0YLE

2 1

Remote Base Memory RX CTCSS
by Tim Sawyer 20 Sep '12

20 Sep '12

How is a remote base memory channel programed with P/L decode? For example with this memory: [memory] 09 = 146.895,136.5,l-t -- Tim :wq

4 7

node registration problems
by Bradley Haney 19 Sep '12

19 Sep '12

Still having problems of keep the allstarlink node registered. ECHOLINK is solid through asterisk but allstarlink keeps disconnecting. WHen i do a Iax2 reload this is the error i get.. [Sep 19 22:05:34] NOTICE[20399]: chan_iax2.c:11430 set_config: Ignoring bindport on reload [Sep 19 22:05:34] NOTICE[20399]: chan_iax2.c:11489 set_config: Ignoring bindaddr on reload [Sep 19 22:05:34] WARNING[20399]: acl.c:345 ast_append_ha: is not a valid IP == Loaded firmware 'iaxy.bin' Any thoughts? Below is what i see when i do a iax2 show registry show registry Host dnsmgr Username Perceived Refresh State 67.215.233.178:4569 N 28079 <Unregistered> 60 Request Sent K9WRA*CLI> Bradley

1 0

Re: [App_rpt-users] URI frustration
by Anthony Percy 19 Sep '12

19 Sep '12

Hi Jay, I had a similar problem recently. on a repeater that worked perfectly using an older motherboard... ... To check if its the same problem, is the URI green LED flashing at its normal rate, e.g. 3-4 times a second or is it a lot slower? And are you using the current ACID install???? Regards Anthony, VK2ACP Message: 2 Date: Tue, 18 Sep 2012 11:23:14 -0500 From: Jay Urish <jay(a)unixwolf.net> To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] URI frustration Message-ID: <50589FF2.3020408(a)unixwolf.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed I was up late last night still trying to get my tkr-750 working with my URI. Thank you to the guys that sent me wiring info, but i'm still not working right. The audio being transmitted from the repeater sounds like it has AC buzz in it. When I transmit with my portable, the repeater only stays keyed for 5 seconds. Does anybody actually have this working? What should my node stanza in usbradio.conf look like?

1 0

App_rpt
by K&R Yoksh 19 Sep '12

19 Sep '12

Hi Jeff. I'm doing this same thing on my nodes. Check out the DTMF script on my web page: http://www.qsl.net/k0kn/scripts.html This will allow you to send commands to any node within the same server. 73, Kyle K0KN

2 1

Remote command?
by Jeffrey S. Carrier 19 Sep '12

19 Sep '12

Is there a way to mute the MDC1200? My control codes are working but the MDC is transmitted over the TX path on all linked repeaters. Is it possible to mute this? Thanks, K0JSC ________________________________ From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Tuesday, September 18, 2012 10:32 AM To: Jeffrey S. Carrier; app_rpt mailing list Subject: RE: [App_rpt-users] Remote command? Well, how about *4XXXX*31999# (like if you wanted to execute *1999 on the linked node) Jim ________________________________ Date: Tue, 18 Sep 2012 10:14:18 -0600 From: jeff.carrier(a)rmsmsecurity.com To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Remote command? Quick question, I'm playing with MDC1200 control due to all of the recent posts. I have that part working but here is my issue. I have 4 nodes, 3 of them are connected to radios and one of them is a hub node. The hub node is connected to the internet and is the connection point to the allstar and echolink network. The 3 nodes connected to the radios are on private wireless LAN. I'd "like" to be able to send a command on one of the RF nodes via either MDC1200 or DTMF to say disable incoming connections but that command has to be passed to the "hub" node. Is there a way to properly format a macro to accomplish this or am I stuck with doing *4XXXXX then sending the command? Thanks in advance 73 de K0JSC _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0