September 2012 - App_rpt-users

compile and install app_rpt from source?
by Kevin Oleniczak 22 Sep '12

22 Sep '12

I have an existing asterisk/freepbx install on ubuntu which i use for the home phone system and would like to get app_rpt going on it as well. I'm not seeing clear instructions on which files/source to grab and where to install. Any suggestions? thanks Kevin - AB9RN

3 2

How do you restart Asterisk?
by Jim W7RY 22 Sep '12

22 Sep '12

I just changed my config file. I want to restart Asterisk so it will read the new config file. What is the command for this? Thanks! 73 Jim W7RY

3 2

Re: [App_rpt-users] Monitoring an allstar node?
by Michael Graff 22 Sep '12

22 Sep '12

I wonder if there are any design docs floating around about app_rpt... The code is just a bit more than confusing :) When I watch through the manager interface, I see things like this for all incoming calls: Event: Newchannel Privilege: call,all Channel: Zap/pseudo-267404033 State: Rsrvd CallerIDNum: <unknown> CallerIDName: <unknown> Uniqueid: 1348279997.22 The CallerIDNum and CallerIDName are not set here. I was sort of hoping I would end up with the node that keyed up, and perhaps even the call sign if they are connected using a net transceiver. I'd be satisfied with just the node... However, while a new pseudo channel is created when someone keys up, I am not sure how the internal call flow really works. I do see some IAX-layer control messages passing around, so I assume the IAX call is from the app_rpt module to the remote's app_rpt module. I'm just wishing the caller ID information could also travel through this IAX bridge, so we could know who specifically is calling when we get a new channel created. Alternatively, app_rpt could generate an event when it starts showing audio with the node number it comes from, if this were passed through the IAX2 channel. Ideally, again, it would just append its node to the path, so if node 1234 connected to 9876, and 4444 connected to 9876, a transmitter on 1234 would be seen on 4444 as: 1234 9876 --Michael

1 0

Re: [App_rpt-users] ok...
by Bryan D. Boyle 22 Sep '12

22 Sep '12

On 9/21/2012 7:00 PM, Tim Sawyer wrote: > That's what the nodes stanza is for: > > [nodes] > ; Note, if you are using automatic update for allstar link nodes, > ; no allstar link nodes should be defined here. Only place a definition > ; for your locak nodes, and private (off of allstar link) nodes here. > > 2534 = radio(a)127.0.0.1/2534,NONE ; This must be changed to your node number > 2535 = radio@192.168.1.12:4571/2535,NONE,Y ; Remote base node Yup...got it all working, after a fashion. Now to write the cross-server scripts, and so forth. May go the ssh route to get rid of Mr. Robot 'By Your Command' that gets propagated throughout our network... Thanks all, for your insights and guidance. Sometimes, you just have to keep picking at it to get it to work... BB

1 0

Re: [App_rpt-users] Monitoring an allstar node?
by Michael Graff 21 Sep '12

21 Sep '12

Mind sharing the code with one person (me?) :) I'm a decent web developer. Or, could you share how you are collecting the data? I have only just installed a node, so I'm very new to the system. I've done a lot of Asterisk coding in the past, but most of that does not really apply to Allstar. Also, does it show just directly connected nodes, or any nodes in the mesh? --Michael On Sep 21, 2012, at 5:53 PM, Tim Sawyer <tim.sawyer(a)mac.com> wrote: > I wrote a web page (http://wd6awp.net/hub/) which lets me monitor my hub. The node currently keyed gets a green background. The list of nodes is sorted by the last to key up. That way you can see which node you just heard even if you were not looking at the page while they talked. Logged in users can connect or disconnect nodes. > > <Screen Shot 2012-09-21 at 3.49.36 PM.png> > > Someday I'll release the code but it's not ready yet. > -- > Tim > :wq > > On Sep 21, 2012, at 3:39 PM, Michael Graff <explorer(a)flame.org> wrote: > >> 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 >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >

1 0

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