December 2014 - App_rpt-users - lists.keekles.org

Registration issues
by Thor Wiegman 30 Nov '15

30 Nov '15

Tonight I had a user tell me that one of my nodes wouldn't connect anywhere. Verified, rebooted the server, still nothing. Tried running the rc.updatenodelist script manually and it just sits there. However, after running the following command I do get an update and can now connect to other nodes. /usr/bin/wget -O /var/lib/asterisk/rpt_extnodeshttp://nodes1.allstarlink.org/cgi-bin/nodes.pl When I checked two other nodes they had the same problem and same work-around. I ran that same command for nodes2 and it works. When I run it for nodes3 it times out. Could a problem with nodes3.allstarlink.org be causing the rc.updatenodelist script to choke? And could that have been causing my nodes to not be able to connect to others?

5 5

URI<>TKR-750 cable
by Jay Urish 06 Feb '15

06 Feb '15

Does anybody have notes on connecting tkr750 to a URI? TIA, W5GM

4 3

Echo-stink
by Johnny Keeker 05 Jan '15

05 Jan '15

I've found the 'permit=w1aw,w5yi,etc' line in the echolink.conf only allows for 29 allowed calls. Any more than 30 entries in the list prevents incoming requests on or not on the list access to the node. Short of checking for typo's, using a backslash\ to continue to the next line, or adding another 'permit= line' hasn't proved any results. ???

6 6

command to disable transmit
by Greg 29 Dec '14

29 Dec '14

Is there a way to set up a dtmf command to disable rf transmit or disable radio key, then re-enable? Thanks Greg

2 1

Re: [App_rpt-users] Remote Base question
by mike＠midnighteng.com 29 Dec '14

29 Dec '14

Sam and Corey, I could be wrong about this but I think you might want to look for irq sharing problems. Most likely, your bios setup all the usb hubs built in to the same irq. There is not alot of things you can do to remedy this except the following might help. As always, I would turn off any built-in devices that are not used. Turn off any unused usb hubs. Unplug any usb devices not needed. Plug only one usb-fob dongle per hub when possible. (a built-in hub usually has two usb ports) You may be able to (at this point) try to reset the pnp system if your bios allows. Sometimes these problems are fault of the bios pnp and sometimes it is because on pnp device does not fully comply to the pnp standard. And that device is not necessarily the one you are having the problem with. Things to try ? Let me know if you get it... ...mike/kb8jnm > -------- Original Message -------- > Subject: Re: [App_rpt-users] Remote Base question > From: Sam Nabkey <sam.nabkey(a)gmail.com> > Date: Mon, December 29, 2014 8:11 pm > To: Corey Dean <n3fe(a)repeater.net> > Cc: mike(a)midnighteng.com, Allstar app_rpt-users Group > <app_rpt-users(a)ohnosec.org> > > > I have to pull the fob quite a few times. You can tell when you need to do > it because the node will disoconnect but when you try and reconnect, it > will announce the connection but you cannot use the remote. I've tried > everything. > > I guess time will tell with me. How often do you have to reset it? > > Corey N3FE > > On Dec 28, 2014, at 10:18 AM, Sam Nabkey <sam.nabkey(a)gmail.com> wrote: > > I've used several fobs a URIx and a RIM. Same result. Sometimes I have > to pull the fob from the port to get it to reset. > > Its either something I'm missing or ? > > > On Dec 28, 2014 9:43 AM, <mike(a)midnighteng.com> wrote: > > > > > Corey, > > > > I think I understand what you were saying about the querk in the DH RB. > > > > I can say that the doug hall has a few little issues of its own > > (depending on firmware ver). > > > > 1st, even though you can power the rbi-1 through radio power, don't do > > it. > > Power with its own cord w 12vdc. > > > > But it is important to do the following when you setup from a fresh > > power-up, > > > > watch the display to see which radio is being programed default at > > power-up, > > > > enter a freq for each of the bands/radios you have installed until it > > has powered off the unused bands/radios, starting with the one that it > > reverted to last(blinked). > > > > When finished, you should have only the active working band/radio with > > power-up. > > (some older radios will not power down but x31,x41 should work ok) > > > > Then you can feel confident that it will run without error. > > > > It is possible to run into a error when switching from a radio memory to > > a vfo mode especially after a reset. > > > > ...mike/kb8jnm > > > > > > > -------- Original Message -------- > > > Subject: Re: [App_rpt-users] Remote Base question > > > From: Corey Dean <n3fe(a)repeater.net> > > > Date: Sun, December 28, 2014 2:01 am > > > To: Sam Nabkey <sam.nabkey(a)gmail.com> > > > Cc: "mike(a)midnighteng.com" <mike(a)midnighteng.com>, Allstar app_rpt-users > > > Group <app_rpt-users(a)ohnosec.org> > > > > > > > > > When the node disconnects it does keep blinking. I played with it for > > hours. Every once in a while the uhf side will mess is and instead of > > taking say 444.050, it will take 440.050. Switch it back to vhf and then > > to uhf fixes that though. Time will only tell how things will work! > > > > > > Corey > > > > > > > On Dec 28, 2014, at 1:23 AM, Sam Nabkey <sam.nabkey(a)gmail.com> wrote: > > > > > > > > Very cool Corey! > > > > > > > > I am glad you have it working... In your case, does the light stop > > flashing when you disconnect from the RB? Mine doesn't and sometimes I > > have to unplug and plug back in the URI for it to work again. > > > > > > > > Sam > > > > > > > >> On Sun, Dec 28, 2014 at 12:04 AM, Corey Dean <n3fe(a)repeater.net> > > wrote: > > > >> Well the remote base is up and running. > > > >> > > > >> One thing that got me and it shouldn't have was this was the first > > time I used a FOB that had the blinking light on it. It had the blob over > > the chip so I saved it for ACID use and the PP outputs and inputs. I kept > > trying to troubleshoot why the light would stop blinking when I added in > > remote=rbi. I shouldn't have worried about it as once I connected to it > > from another node, the light started blinking and away I went. I also > > didn't realize that the CLI wouldn't work unless another node or IAXRPT was > > connected to the remote base. > > > >> > > > >> With that all squared away I still couldn't get things working. As > > suggested by someone else I disconnected the reset line from pin 4 and > > bam... It started working right away.. I spent many many hours on this > > and all these little gotchas was what was holding me back. > > > >> > > > >> Thanks again for all the help from everyone. This was actually > > pretty simple now that I know how things work when you are using a remote > > base. It is a little different setup then configuring a regular node. > > > >> > > > >> Thanks again everyone! > > > >> > > > >> Corey N3FE > > > >> > > > >>> On Sat, Dec 27, 2014 at 9:02 AM, <mike(a)midnighteng.com> wrote: > > > >>> > > > >>> Sam and Corey, > > > >>> > > > >>> I did just want to point out that the one node connect is only valid > > if > > > >>> you use the > > > >>> node=remote base option. > > > >>> > > > >>> 29261 = radio(a)127.0.0.1/29261,NONE,y ;y=remote base > > > >>> > > > >>> Without the "Y" many nodes can connect to the remote base node. > > > >>> > > > >>> What I did was put the control in a main node and use only use the > > audio > > > >>> paths for the remote base node then I do not have to connect to it in > > > >>> control mode to control it. > > > >>> This way I don't have to connect to it at all to control it. > > > >>> May not be suitable for everyone's config though. > > > >>> > > > >>> And Sam may be right about the reset line, I have never connected it > > > >>> myself. > > > >>> Something to try. > > > >>> > > > >>> But I doubt it has any bearing on a FOB issue. > > > >>> > > > >>> I have no issues with DH-RBI > > > >>> > > > >>> ...mike/kb8jnm > > > >>> > > > >>> > -------- Original Message -------- > > > >>> > Subject: Re: [App_rpt-users] Remote Base question > > > >>> > From: Sam Nabkey <sam.nabkey(a)gmail.com> > > > >>> > Date: Sat, December 27, 2014 8:46 am > > > >>> > To: mike(a)midnighteng.com > > > >>> > Cc: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > > > >>> > > > > >>> > > > > >>> > Corey.... > > > >>> > > > > >>> > I just went through this... > > > >>> > > > > >>> > here is what I have learned... > > > >>> > > > > >>> > The URI light will not blink until you connect to the Remote with > > another > > > >>> > node or iaxrpt. after that, it appears to stay blinking, however, > > I believe > > > >>> > it shoud go out again when you disconnect? Mine doesn't.. > > > >>> > > > > >>> > You need to use the *4xxx controlling the far node routine to > > manipulate > > > >>> > the remote from a connect node. OR you can use IAXRPT to test. > > > >>> > > > > >>> > I sometimes have to stop and restart asterisk to correct an issue > > where the > > > >>> > remote stops responding to anything. I think it has something to > > do with > > > >>> > the URI not disconnecting and the light stopping when you > > disconnect. > > > >>> > > > > >>> > Only one node at a time can connect with the Remote Base. the > > other > > > >>> > attempts will fail. > > > >>> > > > > >>> > The Icom 706 needs Memories 50-99 entered and saved with the RPT > > TONE set.. > > > >>> > Starting at 67.0 at Memory 50 and going up each tone till you > > reach the > > > >>> > last tone and memory 99. I used 146.520 simplex in every memory > > and just > > > >>> > changed the tone incrementing 1 up till I hit 99 and the end of the > > > >>> > available tones IF you don't do this, you will get "invalid > > frequency" > > > >>> > everytime. > > > >>> > > > > >>> > The RBI remote base works but I had to disconnect pin 4 it appears > > in my > > > >>> > case anyways, the logic level is backwards? As soon as I removed > > the reset > > > >>> > pin 4, it took right off. I am going to have to work on this > > because the > > > >>> > RBI operates with fewer mishaps when its connected. > > > >>> > > > > >>> > The Kenwood TMD-700a works the best for me so far. > > > >>> > > > > >>> > Corey, I run my nodes in a private invironment so I have removed > > most of > > > >>> > the band edge and authlevel safegards that maybe should be > > included, but I > > > >>> > wanted to get it to work before I added that back in. I am using > > a USB > > > >>> > Serial interface or a USB Icom interface in the case of the 706. > > > >>> > > > > >>> > here are my working examples. I hope it at least gets you > > started. Your > > > >>> > mileage may vary, CAUTION! Beverage may be HOT! (insert favorite > > > >>> > disclaimer here..) > > > >>> > > > > >>> > ------ > > > >>> > > > > >>> > Example #1: For the IC-706: > > > >>> > > > > >>> > [582]; IC-706 Remote Base > > > >>> > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > > > >>> > duplex=1 > > > >>> > context = radio > > > >>> > accountcode=RADIO > > > >>> > functions = functions > > > >>> > memory = memory > > > >>> > > > > >>> > remote = ic706 > > > >>> > ioport = /dev/ttyUSB0 > > > >>> > civaddr = 88 > > > >>> > authlevel=0 > > > >>> > > > > >>> > [functions] > > > >>> > 0=remote,1 ; Retrieve Memory > > > >>> > 1=remote,2 ; Set freq. > > > >>> > 2=remote,3 ; Set tx PL tone > > > >>> > 3=remote,4 ; Set rx PL tone > > > >>> > 6=remote,6 ; Set Mode 1=FM 2=USB > > 3=LSB 4=AM > > > >>> > 40=remote,100 ; Rx PL off > > > >>> > 41=remote,101 ; Rx PL on > > > >>> > 42=remote,102 ; Tx PL off > > > >>> > 43=remote,103 ; Tx PL on > > > >>> > 44=remote,104 ; Low Power > > > >>> > 45=remote,105 ; Medium Power > > > >>> > 46=remote,106 ; High Power > > > >>> > 711=remote,107 ; Bump -20 > > > >>> > 714=remote,108 ; Bump -100 > > > >>> > 717=remote,109 ; Bump -500 > > > >>> > 713=remote,110 ; Bump +20 > > > >>> > 716=remote,111 ; Bump +100 > > > >>> > 719=remote,112 ; Bump +500 > > > >>> > 721=remote,113 ; Scan - slow > > > >>> > 724=remote,114 ; Scan - quick > > > >>> > 727=remote,115 ; Scan - fast > > > >>> > 723=remote,116 ; Scan + slow > > > >>> > 726=remote,117 ; Scan + quick > > > >>> > 729=remote,118 ; Scan + fast > > > >>> > 79=remote,119 ; Tune > > > >>> > 51=remote,5 ; Long status query > > > >>> > 52=remote,140 ; Short status query > > > >>> > 67=remote,210 ; Send a * > > > >>> > 69=remote,211 ; Send a # > > > >>> > > > > >>> > [memory] > > > >>> > init = 14.250,67.0,u ; 14.250MHz upper sideband > > > >>> > 00 = 146.460,100.0,sht > > > >>> > 01 = 146.940,100.0,-l > > > >>> > 02 = 14.250,100.0,u ; 14.250MHz upper sideband > > > >>> > > > > >>> > [nodes] > > > >>> > 582 = radio(a)127.0.0.1/582,NONE,y > > > >>> > > > > >>> > [nodes](+) > > > >>> > #include nodes.include > > > >>> > > > > >>> > > > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > > >>> > > > > >>> > EXAMPLE #2 For the RBI... > > > >>> > > > > >>> > [582]; Doug Hall RBI-1 > > > >>> > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > > > >>> > duplex=1 > > > >>> > context = radio > > > >>> > functions = functions > > > >>> > memory = memory > > > >>> > > > > >>> > remote=rbi > > > >>> > iobase=0x378 > > > >>> > > > > >>> > authlevel=0 > > > >>> > > > > >>> > [functions] > > > >>> > 0=remote,1 ; Retrieve Memory > > > >>> > 1=remote,2 ; Set freq. > > > >>> > 2=remote,3 ; Set tx PL tone > > > >>> > 3=remote,4 ; Set rx PL tone > > > >>> > 5=remote,140 ; short status query > > > >>> > 6=remote,5 ; Long Status Query > > > >>> > > > > >>> > 730=remote,100 ; Rx PL off > > > >>> > 731=remote,101 ; Rx PL on > > > >>> > 720=remote,102 ; Tx PL off > > > >>> > 721=remote,103 ; Tx PL on > > > >>> > 740=remote,104 ; Low Power > > > >>> > 741=remote,105 ; Medium Power > > > >>> > 742=remote,106 ; High Power > > > >>> > > > > >>> > [memory] > > > >>> > init = 146.520,94.8,sht > > > >>> > 26 = 147.260,94.8,+ltr > > > >>> > 27 = 145.270,94.8,-ltr > > > >>> > 11 = 145.110,94.8,-ltr > > > >>> > 52 = 146.520,94.8,sh > > > >>> > > > > >>> > [nodes] > > > >>> > 582 = radio(a)127.0.0.1/582,NONE,y > > > >>> > > > > >>> > [nodes](+) > > > >>> > #include nodes.include > > > >>> > > > ______________________________________________________________________________ > > > >>> > > > > >>> > Example #3 For the Kenwood TMD-700a > > > >>> > > > > >>> > [582]; Kenwood TMD-700a > > > >>> > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > > > >>> > duplex=1 > > > >>> > context = radio > > > >>> > callerid = "K8SN 582" <6164389073> > > > >>> > accountcode=RADIO > > > >>> > functions = functions > > > >>> > memory = memory > > > >>> > > > > >>> > remote = tmd700 > > > >>> > ioport = /dev/ttyUSB0 > > > >>> > > > > >>> > authlevel=0 > > > >>> > > > > >>> > [functions] > > > >>> > 0=remote,1 ; Retrieve Memory > > > >>> > 1=remote,2 ; Set freq. > > > >>> > 2=remote,3 ; Set tx PL tone > > > >>> > 3=remote,4 ; Set rx PL tone > > > >>> > 40=remote,100 ; Rx PL off > > > >>> > 41=remote,101 ; Rx PL on > > > >>> > 42=remote,102 ; Tx PL off > > > >>> > 43=remote,103 ; Tx PL on > > > >>> > 44=remote,104 ; Low Power > > > >>> > 45=remote,105 ; Medium Power > > > >>> > 46=remote,106 ; High Power > > > >>> > 51=remote,5 ; Long status query > > > >>> > 52=remote,140 ; Short status query > > > >>> > 67=remote,210 ; Send a * > > > >>> > 69=remote,211 ; Send a # > > > >>> > > > > >>> > [memory] > > > >>> > init = 146.520,94.8,sht > > > >>> > 26 = 147.260,94.8,+ltr > > > >>> > 27 = 145.270,94.8,-ltr > > > >>> > 11 = 145.110,94.8,-ltr > > > >>> > 52 = 146.520,94.8,sht > > > >>> > > > > >>> > [nodes] > > > >>> > 582 = radio(a)127.0.0.1/582,NONE,y > > > >>> > > > > >>> > [nodes](+) > > > >>> > #include nodes.include > > > >>> > > > > >>> > > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > >>> > > > > >>> > On Sat, Dec 27, 2014 at 6:11 AM, <mike(a)midnighteng.com> wrote: > > > >>> > > > > >>> > > > > > >>> > > > > > >>> > > Corey, > > > >>> > > > > > >>> > > As we have talked on this before, > > > >>> > > It really does not make any sense but here is a checklist. > > > >>> > > > > > >>> > > Look at usbradio.conf and > > > >>> > > usbxxxxx.conf > > > >>> > > Other than looking for type errors, make sure the fob is > > addressed > > > >>> > > properly. > > > >>> > > > > > >>> > > You might also add a > > > >>> > > memory=memoryxxxxx section and provide a default freq load > > string for > > > >>> > > the node (rpt.conf). > > > >>> > > > > > >>> > > init=146.520,100.0,l > > > >>> > > > > > >>> > > It's a start anyway... > > > >>> > > > > > >>> > > ...mike/kb8jnm > > > >>> > > > > > >>> > > > -------- Original Message -------- > > > >>> > > > Subject: [App_rpt-users] Remote Base question > > > >>> > > > From: Corey Dean <n3fe(a)repeater.net> > > > >>> > > > Date: Sat, December 27, 2014 12:09 am > > > >>> > > > To: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > > > >>> > > > > > > >>> > > > > > > >>> > > > A few different times I have attempted to get a remote base > > going. I am > > > >>> > > > using a Doug Hall Box. I am sure I have it wired correctly. > > On the > > > >>> > > > Parallel port I have pin 2 as serial data, 3 as serial clock > > and 4 as > > > >>> > > > reset. > > > >>> > > > > > > >>> > > > If I define remote = rbi asterisk will start but the light on > > the usb FOB > > > >>> > > > stop blinking. Once I comment out the remote = line and > > restart > > > >>> > > asterisk, > > > >>> > > > the sound fob will start to blink again and the doug hall will > > reset. I > > > >>> > > > decided to try defining any type of remote such as y or even > > ic706 and > > > >>> > > the > > > >>> > > > same thing happens. > > > >>> > > > > > > >>> > > > When I do define remote=rbi it still will not program the > > kenwood radio > > > >>> > > > either. > > > >>> > > > > > > >>> > > > I did upgrade to the latest acid svn to test as well because > > prior to > > > >>> > > > upgrading if any remote at all was defined, asterisk wouldn't > > even start. > > > >>> > > > It would bomb right out. At least now it start. I know this > > has to be > > > >>> > > > something simple. Any one have any ideas as to where to start > > looking? > > > >>> > > > > > > >>> > > > I did define a remote-base stanza for functions and the only > > things I > > > >>> > > added > > > >>> > > > other than that was. > > > >>> > > > > > > >>> > > > remote = rbi > > > >>> > > > iobase = 0x378 > > > >>> > > > authlevel = 0 > > > >>> > > > > > > >>> > > > I am also using usbradio. > > > >>> > > > > > > >>> > > > Corey N3FE<hr>_______________________________________________ > > > >>> > > > App_rpt-users mailing list > > > >>> > > > App_rpt-users(a)ohnosec.org > > > >>> > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > >>> > > > > > > >>> > > > To unsubscribe from this list please visit > > > >>> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and > > scroll down > > > >>> > > to the bottom of the page. Enter your email address and press the > > > >>> > > "Unsubscribe or edit options button" > > > >>> > > > You do not need a password to unsubscribe, you can do it via > > email > > > >>> > > confirmation. If you have trouble unsubscribing, please send a > > message to > > > >>> > > the list detailing the problem. > > > >>> > > _______________________________________________ > > > >>> > > App_rpt-users mailing list > > > >>> > > App_rpt-users(a)ohnosec.org > > > >>> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > >>> > > > > > >>> > > To unsubscribe from this list please visit > > > >>> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and > > scroll down > > > >>> > > to the bottom of the page. Enter your email address and press the > > > >>> > > "Unsubscribe or edit options button" > > > >>> > > You do not need a password to unsubscribe, you can do it via > > email > > > >>> > > confirmation. If you have trouble unsubscribing, please send a > > message to > > > >>> > > the list detailing the problem. > > > >>> > > > > > >>> _______________________________________________ > > > >>> App_rpt-users mailing list > > > >>> App_rpt-users(a)ohnosec.org > > > >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > >>> > > > >>> To unsubscribe from this list please visit > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > > to the bottom of the page. Enter your email address and press the > > "Unsubscribe or edit options button" > > > >>> You do not need a password to unsubscribe, you can do it via email > > confirmation. If you have trouble unsubscribing, please send a message to > > the list detailing the problem. > > > >> > > > >> > > > >> _______________________________________________ > > > >> App_rpt-users mailing list > > > >> App_rpt-users(a)ohnosec.org > > > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > >> > > > >> To unsubscribe from this list please visit > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > > to the bottom of the page. Enter your email address and press the > > "Unsubscribe or edit options button" > > > >> You do not need a password to unsubscribe, you can do it via email > > confirmation. If you have trouble unsubscribing, please send a message to > > the list detailing the problem. > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users(a)ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > > to the bottom of the page. Enter your email address and press the > > "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email > > confirmation. If you have trouble unsubscribing, please send a message to > > the list detailing the problem. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > to the bottom of the page. Enter your email address and press the > "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email > confirmation. If you have trouble unsubscribing, please send a message to > the list detailing the problem.

1 0

Re: [App_rpt-users] Remote Base question
by mike＠midnighteng.com 29 Dec '14

29 Dec '14

Corey, I think I understand what you were saying about the querk in the DH RB. I can say that the doug hall has a few little issues of its own (depending on firmware ver). 1st, even though you can power the rbi-1 through radio power, don't do it. Power with its own cord w 12vdc. But it is important to do the following when you setup from a fresh power-up, watch the display to see which radio is being programed default at power-up, enter a freq for each of the bands/radios you have installed until it has powered off the unused bands/radios, starting with the one that it reverted to last(blinked). When finished, you should have only the active working band/radio with power-up. (some older radios will not power down but x31,x41 should work ok) Then you can feel confident that it will run without error. It is possible to run into a error when switching from a radio memory to a vfo mode especially after a reset. ...mike/kb8jnm > -------- Original Message -------- > Subject: Re: [App_rpt-users] Remote Base question > From: Corey Dean <n3fe(a)repeater.net> > Date: Sun, December 28, 2014 2:01 am > To: Sam Nabkey <sam.nabkey(a)gmail.com> > Cc: "mike(a)midnighteng.com" <mike(a)midnighteng.com>, Allstar app_rpt-users > Group <app_rpt-users(a)ohnosec.org> > > > When the node disconnects it does keep blinking. I played with it for hours. Every once in a while the uhf side will mess is and instead of taking say 444.050, it will take 440.050. Switch it back to vhf and then to uhf fixes that though. Time will only tell how things will work! > > Corey > > > On Dec 28, 2014, at 1:23 AM, Sam Nabkey <sam.nabkey(a)gmail.com> wrote: > > > > Very cool Corey! > > > > I am glad you have it working... In your case, does the light stop flashing when you disconnect from the RB? Mine doesn't and sometimes I have to unplug and plug back in the URI for it to work again. > > > > Sam > > > >> On Sun, Dec 28, 2014 at 12:04 AM, Corey Dean <n3fe(a)repeater.net> wrote: > >> Well the remote base is up and running. > >> > >> One thing that got me and it shouldn't have was this was the first time I used a FOB that had the blinking light on it. It had the blob over the chip so I saved it for ACID use and the PP outputs and inputs. I kept trying to troubleshoot why the light would stop blinking when I added in remote=rbi. I shouldn't have worried about it as once I connected to it from another node, the light started blinking and away I went. I also didn't realize that the CLI wouldn't work unless another node or IAXRPT was connected to the remote base. > >> > >> With that all squared away I still couldn't get things working. As suggested by someone else I disconnected the reset line from pin 4 and bam... It started working right away.. I spent many many hours on this and all these little gotchas was what was holding me back. > >> > >> Thanks again for all the help from everyone. This was actually pretty simple now that I know how things work when you are using a remote base. It is a little different setup then configuring a regular node. > >> > >> Thanks again everyone! > >> > >> Corey N3FE > >> > >>> On Sat, Dec 27, 2014 at 9:02 AM, <mike(a)midnighteng.com> wrote: > >>> > >>> Sam and Corey, > >>> > >>> I did just want to point out that the one node connect is only valid if > >>> you use the > >>> node=remote base option. > >>> > >>> 29261 = radio(a)127.0.0.1/29261,NONE,y ;y=remote base > >>> > >>> Without the "Y" many nodes can connect to the remote base node. > >>> > >>> What I did was put the control in a main node and use only use the audio > >>> paths for the remote base node then I do not have to connect to it in > >>> control mode to control it. > >>> This way I don't have to connect to it at all to control it. > >>> May not be suitable for everyone's config though. > >>> > >>> And Sam may be right about the reset line, I have never connected it > >>> myself. > >>> Something to try. > >>> > >>> But I doubt it has any bearing on a FOB issue. > >>> > >>> I have no issues with DH-RBI > >>> > >>> ...mike/kb8jnm > >>> > >>> > -------- Original Message -------- > >>> > Subject: Re: [App_rpt-users] Remote Base question > >>> > From: Sam Nabkey <sam.nabkey(a)gmail.com> > >>> > Date: Sat, December 27, 2014 8:46 am > >>> > To: mike(a)midnighteng.com > >>> > Cc: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > >>> > > >>> > > >>> > Corey.... > >>> > > >>> > I just went through this... > >>> > > >>> > here is what I have learned... > >>> > > >>> > The URI light will not blink until you connect to the Remote with another > >>> > node or iaxrpt. after that, it appears to stay blinking, however, I believe > >>> > it shoud go out again when you disconnect? Mine doesn't.. > >>> > > >>> > You need to use the *4xxx controlling the far node routine to manipulate > >>> > the remote from a connect node. OR you can use IAXRPT to test. > >>> > > >>> > I sometimes have to stop and restart asterisk to correct an issue where the > >>> > remote stops responding to anything. I think it has something to do with > >>> > the URI not disconnecting and the light stopping when you disconnect. > >>> > > >>> > Only one node at a time can connect with the Remote Base. the other > >>> > attempts will fail. > >>> > > >>> > The Icom 706 needs Memories 50-99 entered and saved with the RPT TONE set.. > >>> > Starting at 67.0 at Memory 50 and going up each tone till you reach the > >>> > last tone and memory 99. I used 146.520 simplex in every memory and just > >>> > changed the tone incrementing 1 up till I hit 99 and the end of the > >>> > available tones IF you don't do this, you will get "invalid frequency" > >>> > everytime. > >>> > > >>> > The RBI remote base works but I had to disconnect pin 4 it appears in my > >>> > case anyways, the logic level is backwards? As soon as I removed the reset > >>> > pin 4, it took right off. I am going to have to work on this because the > >>> > RBI operates with fewer mishaps when its connected. > >>> > > >>> > The Kenwood TMD-700a works the best for me so far. > >>> > > >>> > Corey, I run my nodes in a private invironment so I have removed most of > >>> > the band edge and authlevel safegards that maybe should be included, but I > >>> > wanted to get it to work before I added that back in. I am using a USB > >>> > Serial interface or a USB Icom interface in the case of the 706. > >>> > > >>> > here are my working examples. I hope it at least gets you started. Your > >>> > mileage may vary, CAUTION! Beverage may be HOT! (insert favorite > >>> > disclaimer here..) > >>> > > >>> > ------ > >>> > > >>> > Example #1: For the IC-706: > >>> > > >>> > [582]; IC-706 Remote Base > >>> > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > >>> > duplex=1 > >>> > context = radio > >>> > accountcode=RADIO > >>> > functions = functions > >>> > memory = memory > >>> > > >>> > remote = ic706 > >>> > ioport = /dev/ttyUSB0 > >>> > civaddr = 88 > >>> > authlevel=0 > >>> > > >>> > [functions] > >>> > 0=remote,1 ; Retrieve Memory > >>> > 1=remote,2 ; Set freq. > >>> > 2=remote,3 ; Set tx PL tone > >>> > 3=remote,4 ; Set rx PL tone > >>> > 6=remote,6 ; Set Mode 1=FM 2=USB 3=LSB 4=AM > >>> > 40=remote,100 ; Rx PL off > >>> > 41=remote,101 ; Rx PL on > >>> > 42=remote,102 ; Tx PL off > >>> > 43=remote,103 ; Tx PL on > >>> > 44=remote,104 ; Low Power > >>> > 45=remote,105 ; Medium Power > >>> > 46=remote,106 ; High Power > >>> > 711=remote,107 ; Bump -20 > >>> > 714=remote,108 ; Bump -100 > >>> > 717=remote,109 ; Bump -500 > >>> > 713=remote,110 ; Bump +20 > >>> > 716=remote,111 ; Bump +100 > >>> > 719=remote,112 ; Bump +500 > >>> > 721=remote,113 ; Scan - slow > >>> > 724=remote,114 ; Scan - quick > >>> > 727=remote,115 ; Scan - fast > >>> > 723=remote,116 ; Scan + slow > >>> > 726=remote,117 ; Scan + quick > >>> > 729=remote,118 ; Scan + fast > >>> > 79=remote,119 ; Tune > >>> > 51=remote,5 ; Long status query > >>> > 52=remote,140 ; Short status query > >>> > 67=remote,210 ; Send a * > >>> > 69=remote,211 ; Send a # > >>> > > >>> > [memory] > >>> > init = 14.250,67.0,u ; 14.250MHz upper sideband > >>> > 00 = 146.460,100.0,sht > >>> > 01 = 146.940,100.0,-l > >>> > 02 = 14.250,100.0,u ; 14.250MHz upper sideband > >>> > > >>> > [nodes] > >>> > 582 = radio(a)127.0.0.1/582,NONE,y > >>> > > >>> > [nodes](+) > >>> > #include nodes.include > >>> > > >>> > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > >>> > > >>> > EXAMPLE #2 For the RBI... > >>> > > >>> > [582]; Doug Hall RBI-1 > >>> > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > >>> > duplex=1 > >>> > context = radio > >>> > functions = functions > >>> > memory = memory > >>> > > >>> > remote=rbi > >>> > iobase=0x378 > >>> > > >>> > authlevel=0 > >>> > > >>> > [functions] > >>> > 0=remote,1 ; Retrieve Memory > >>> > 1=remote,2 ; Set freq. > >>> > 2=remote,3 ; Set tx PL tone > >>> > 3=remote,4 ; Set rx PL tone > >>> > 5=remote,140 ; short status query > >>> > 6=remote,5 ; Long Status Query > >>> > > >>> > 730=remote,100 ; Rx PL off > >>> > 731=remote,101 ; Rx PL on > >>> > 720=remote,102 ; Tx PL off > >>> > 721=remote,103 ; Tx PL on > >>> > 740=remote,104 ; Low Power > >>> > 741=remote,105 ; Medium Power > >>> > 742=remote,106 ; High Power > >>> > > >>> > [memory] > >>> > init = 146.520,94.8,sht > >>> > 26 = 147.260,94.8,+ltr > >>> > 27 = 145.270,94.8,-ltr > >>> > 11 = 145.110,94.8,-ltr > >>> > 52 = 146.520,94.8,sh > >>> > > >>> > [nodes] > >>> > 582 = radio(a)127.0.0.1/582,NONE,y > >>> > > >>> > [nodes](+) > >>> > #include nodes.include > >>> > ______________________________________________________________________________ > >>> > > >>> > Example #3 For the Kenwood TMD-700a > >>> > > >>> > [582]; Kenwood TMD-700a > >>> > rxchannel=SimpleUSB/usb ; Rx audio/signalling channel > >>> > duplex=1 > >>> > context = radio > >>> > callerid = "K8SN 582" <6164389073> > >>> > accountcode=RADIO > >>> > functions = functions > >>> > memory = memory > >>> > > >>> > remote = tmd700 > >>> > ioport = /dev/ttyUSB0 > >>> > > >>> > authlevel=0 > >>> > > >>> > [functions] > >>> > 0=remote,1 ; Retrieve Memory > >>> > 1=remote,2 ; Set freq. > >>> > 2=remote,3 ; Set tx PL tone > >>> > 3=remote,4 ; Set rx PL tone > >>> > 40=remote,100 ; Rx PL off > >>> > 41=remote,101 ; Rx PL on > >>> > 42=remote,102 ; Tx PL off > >>> > 43=remote,103 ; Tx PL on > >>> > 44=remote,104 ; Low Power > >>> > 45=remote,105 ; Medium Power > >>> > 46=remote,106 ; High Power > >>> > 51=remote,5 ; Long status query > >>> > 52=remote,140 ; Short status query > >>> > 67=remote,210 ; Send a * > >>> > 69=remote,211 ; Send a # > >>> > > >>> > [memory] > >>> > init = 146.520,94.8,sht > >>> > 26 = 147.260,94.8,+ltr > >>> > 27 = 145.270,94.8,-ltr > >>> > 11 = 145.110,94.8,-ltr > >>> > 52 = 146.520,94.8,sht > >>> > > >>> > [nodes] > >>> > 582 = radio(a)127.0.0.1/582,NONE,y > >>> > > >>> > [nodes](+) > >>> > #include nodes.include > >>> > > >>> > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > >>> > > >>> > On Sat, Dec 27, 2014 at 6:11 AM, <mike(a)midnighteng.com> wrote: > >>> > > >>> > > > >>> > > > >>> > > Corey, > >>> > > > >>> > > As we have talked on this before, > >>> > > It really does not make any sense but here is a checklist. > >>> > > > >>> > > Look at usbradio.conf and > >>> > > usbxxxxx.conf > >>> > > Other than looking for type errors, make sure the fob is addressed > >>> > > properly. > >>> > > > >>> > > You might also add a > >>> > > memory=memoryxxxxx section and provide a default freq load string for > >>> > > the node (rpt.conf). > >>> > > > >>> > > init=146.520,100.0,l > >>> > > > >>> > > It's a start anyway... > >>> > > > >>> > > ...mike/kb8jnm > >>> > > > >>> > > > -------- Original Message -------- > >>> > > > Subject: [App_rpt-users] Remote Base question > >>> > > > From: Corey Dean <n3fe(a)repeater.net> > >>> > > > Date: Sat, December 27, 2014 12:09 am > >>> > > > To: Allstar app_rpt-users Group <app_rpt-users(a)ohnosec.org> > >>> > > > > >>> > > > > >>> > > > A few different times I have attempted to get a remote base going. I am > >>> > > > using a Doug Hall Box. I am sure I have it wired correctly. On the > >>> > > > Parallel port I have pin 2 as serial data, 3 as serial clock and 4 as > >>> > > > reset. > >>> > > > > >>> > > > If I define remote = rbi asterisk will start but the light on the usb FOB > >>> > > > stop blinking. Once I comment out the remote = line and restart > >>> > > asterisk, > >>> > > > the sound fob will start to blink again and the doug hall will reset. I > >>> > > > decided to try defining any type of remote such as y or even ic706 and > >>> > > the > >>> > > > same thing happens. > >>> > > > > >>> > > > When I do define remote=rbi it still will not program the kenwood radio > >>> > > > either. > >>> > > > > >>> > > > I did upgrade to the latest acid svn to test as well because prior to > >>> > > > upgrading if any remote at all was defined, asterisk wouldn't even start. > >>> > > > It would bomb right out. At least now it start. I know this has to be > >>> > > > something simple. Any one have any ideas as to where to start looking? > >>> > > > > >>> > > > I did define a remote-base stanza for functions and the only things I > >>> > > added > >>> > > > other than that was. > >>> > > > > >>> > > > remote = rbi > >>> > > > iobase = 0x378 > >>> > > > authlevel = 0 > >>> > > > > >>> > > > I am also using usbradio. > >>> > > > > >>> > > > Corey N3FE<hr>_______________________________________________ > >>> > > > App_rpt-users mailing list > >>> > > > App_rpt-users(a)ohnosec.org > >>> > > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >>> > > > > >>> > > > To unsubscribe from this list please visit > >>> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > >>> > > to the bottom of the page. Enter your email address and press the > >>> > > "Unsubscribe or edit options button" > >>> > > > You do not need a password to unsubscribe, you can do it via email > >>> > > confirmation. If you have trouble unsubscribing, please send a message to > >>> > > the list detailing the problem. > >>> > > _______________________________________________ > >>> > > App_rpt-users mailing list > >>> > > App_rpt-users(a)ohnosec.org > >>> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >>> > > > >>> > > To unsubscribe from this list please visit > >>> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > >>> > > to the bottom of the page. Enter your email address and press the > >>> > > "Unsubscribe or edit options button" > >>> > > You do not need a password to unsubscribe, you can do it via email > >>> > > confirmation. If you have trouble unsubscribing, please send a message to > >>> > > the list detailing the problem. > >>> > > > >>> _______________________________________________ > >>> App_rpt-users mailing list > >>> App_rpt-users(a)ohnosec.org > >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >>> > >>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > >>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > >> > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users(a)ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > >> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > >> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > >

3 4

Is it possible to use OpenVPN?
by mca555＠mac.com 29 Dec '14

29 Dec '14

Hi, I’m limited to using port 80 to access the Internet. I’ve been using proxpn on MacOS to get around the issue so I can use POP, FTP, etc. Has anyone had luck using openvpn with ACID? I’ve been wading through the archives, but have yet to find anything . I’m a complete Linux n00b so any direction would be appreciated. Thanks! Mark

3 2

Re: [App_rpt-users] Error Message When Attempting to Connect
by Steve Zingman 28 Dec '14

28 Dec '14

David, Try this: On the hub box: 41488 = radio@127.0.0.1:4572/41488,NONE 40968 = radio@192.168.20.243:4569/40968,NONE On the repeater box: 40968 = radio@127.0.0.1:4569/40968,NONE 41488 = radio@192.168.20.235:4572/41488,NONE 73, Steve N4IRS On 12/28/2014 12:28 PM, app_rpt-users-request(a)ohnosec.org wrote: > Message: 1 > Date: Sun, 28 Dec 2014 10:00:41 -0700 > From: "David Dean K0PWO"<david(a)k0pwo.com> > To: "'Jim Duuuude'"<telesistant(a)hotmail.com>, "'Allstar app_rpt-users > Group'"<app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] Error Message When Attempting to Connect > to my hub > Message-ID:<006101d022bf$d064a8a0$712df9e0$(a)k0pwo.com> > Content-Type: text/plain; charset="utf-8" > > This morning I followed the advice given by several members on the list. I added in the nodes section of both system > > > > 40968 =radio(a)192.168.20.1/40963,NONE <mailto:radio@192.168.20.1/40963,NONE> on the hub box > > 41488 =radio(a)192.168.20.1/41488,NONE <mailto:radio@192.168.20.1/41488,NONE> on the repeater box > > > > And I still get connection failed error messages > > > > Some back ground on what I have > > > > * Comcast internet > > * The Comcast supplied modem/router is bridged for modem gateway only > > * ASUS RT-AC68U Router which feeds a Cisco Switch which both boxes are currently plugged into > > * Node 41488 is my hub node and has port forwarding for port 4572 which it is assigned and configured > > * NODE 40968 is my repeater node and port forwarding for port 4569 which it is assigned and configured > > * Both machines for the moment have ssh of 222 (default) set > > * 41488 (my hub) is using static ip (on my LAN) of 192.168.20.235 > > * 40968 (my repeater) is using static ip (on my LAN) of 192.168.20.243 > > > > The repeater was working fine up until about a month ago when It quit connecting to any nodes. > > > > This morning I reset my router and reconfigured anything ? no change > > This morning I reformatted my repeater box and reconfigured using the Allstar Portal ? no change > >

3 3

Re: [App_rpt-users] Error Message When Attempting to Connect to my hub
by mike＠midnighteng.com 28 Dec '14

28 Dec '14

David there is a lot there but, do you by chance update via webmin ? if so, or even in any case, you might just do a update and recompile and see where that leaves you. Also, when you are trying to connect out, to outside node would that be a internal to a node on other server behind your nat or external allstar outside your nat. Do you have correct "port forwarding" to static addresses even if managed by router by mac id etc ? Would need it at "cable modem/router" and a external router if you are using one. One last thing... did you just switch to comcasts new dual wi-fi modem ? Perhaps someone else will nail it but I can't see it from what is stated. ...mike/kb8jnm > -------- Original Message -------- > Subject: Re: [App_rpt-users] Error Message When Attempting to Connect to > my hub > From: "David Dean K0PWO" <david(a)k0pwo.com> > Date: Sun, December 28, 2014 12:00 pm > To: "'Jim Duuuude'" <telesistant(a)hotmail.com>, "'Allstar app_rpt-users > Group'" <app_rpt-users(a)ohnosec.org> > > > This morning I followed the advice given by several members on the list. I added in the nodes section of both system > > > > 40968 = radio(a)192.168.20.1/40963,NONE <mailto:radio@192.168.20.1/40963,NONE> on the hub box > > 41488 = radio(a)192.168.20.1/41488,NONE <mailto:radio@192.168.20.1/41488,NONE> on the repeater box > > > > And I still get connection failed error messages > > > > Some back ground on what I have > > > > * Comcast internet > > * The Comcast supplied modem/router is bridged for modem gateway only > > * ASUS RT-AC68U Router which feeds a Cisco Switch which both boxes are currently plugged into > > * Node 41488 is my hub node and has port forwarding for port 4572 which it is assigned and configured > > * NODE 40968 is my repeater node and port forwarding for port 4569 which it is assigned and configured > > * Both machines for the moment have ssh of 222 (default) set > > * 41488 (my hub) is using static ip (on my LAN) of 192.168.20.235 > > * 40968 (my repeater) is using static ip (on my LAN) of 192.168.20.243 > > > > The repeater was working fine up until about a month ago when It quit connecting to any nodes. > > > > This morning I reset my router and reconfigured anything – no change > > This morning I reformatted my repeater box and reconfigured using the Allstar Portal – no change > > > > When I attempt to connect my repeater to my hub, which is on the same LAN with the node settings added that are listed above I get this error message on the CLI > > > > [Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection > > [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection > > [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192 .168.20.243 failed CallToken hash inspection > > K0PWO_Hub*CLI> [Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection > > K0PWO_Hub*CLI> [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection > > No such command '[Dec 28 08:37:53] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands) > > No such command '[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands) > > K0PWO_Hub*CLI> [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection[Dec 28 08:37:53] WAR NING[2500]: chan_iax2.c:4328 handle_call_token: Address 192.168.20.243 failed Ca llToken hash inspection > > K0PWO_Hub*CLI> [Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspection > > No such command '[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection[Dec 28 08:37:53] W ARNING[2500]: chan_iax2.c:4328 handle_call_token: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands) > > No such command '[Dec 28 08:37:55] WARNING[2508]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspection' (type 'help [Dec 28' for other possible commands) > > K0PWO_Hub*CLI> [Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_tok en: Address 192.168.20.243 failed CallToken hash inspectionexit > > No such command '[Dec 28 08:38:05] WARNING[2500]: chan_iax2.c:4328 handle_call_t oken: Address 192.168.20.243 failed CallToken hash inspectionexit' (type 'help [ Dec 28' for other possible commands) > > > > > > Once again, anybody have any ideas on what is wrong? > > > > Thank you for any help provided. > > > > David<hr>_______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

2 1

Re: [App_rpt-users] Error Message When Attempting to Connect
by mike＠midnighteng.com 28 Dec '14

28 Dec '14

Steve, I thought there was a way to define the ports for those ip's. Could not find it. Even though I had done it myself some time ago. I was able to connect to him for a chat. I was looking for that info on my system but no longer require it. He states he is unable to connect anywhere so and while that helps behind the nat, not sure it will help external. We shall see but it is needed in any case. ...mike/kb8jnm > -------- Original Message -------- > Subject: Re: [App_rpt-users] Error Message When Attempting to Connect > From: Steve Zingman <szingman(a)msgstor.com> > Date: Sun, December 28, 2014 1:38 pm > To: app_rpt-users(a)ohnosec.org > > > David, > Try this: > > On the hub box: > 41488 = radio@127.0.0.1:4572/41488,NONE > 40968 = radio@192.168.20.243:4569/40968,NONE > > On the repeater box: > 40968 = radio@127.0.0.1:4569/40968,NONE > 41488 = radio@192.168.20.235:4572/41488,NONE > > > 73, Steve N4IRS > > > On 12/28/2014 12:28 PM, app_rpt-users-request(a)ohnosec.org wrote: > > Message: 1 > > Date: Sun, 28 Dec 2014 10:00:41 -0700 > > From: "David Dean K0PWO"<david(a)k0pwo.com> > > To: "'Jim Duuuude'"<telesistant(a)hotmail.com>, "'Allstar app_rpt-users > > Group'"<app_rpt-users(a)ohnosec.org> > > Subject: Re: [App_rpt-users] Error Message When Attempting to Connect > > to my hub > > Message-ID:<006101d022bf$d064a8a0$712df9e0$(a)k0pwo.com> > > Content-Type: text/plain; charset="utf-8" > > > > This morning I followed the advice given by several members on the list. I added in the nodes section of both system > > > > > > > > 40968 =radio(a)192.168.20.1/40963,NONE <mailto:radio@192.168.20.1/40963,NONE> on the hub box > > > > 41488 =radio(a)192.168.20.1/41488,NONE <mailto:radio@192.168.20.1/41488,NONE> on the repeater box > > > > > > > > And I still get connection failed error messages > > > > > > > > Some back ground on what I have > > > > > > > > * Comcast internet > > > > * The Comcast supplied modem/router is bridged for modem gateway only > > > > * ASUS RT-AC68U Router which feeds a Cisco Switch which both boxes are currently plugged into > > > > * Node 41488 is my hub node and has port forwarding for port 4572 which it is assigned and configured > > > > * NODE 40968 is my repeater node and port forwarding for port 4569 which it is assigned and configured > > > > * Both machines for the moment have ssh of 222 (default) set > > > > * 41488 (my hub) is using static ip (on my LAN) of 192.168.20.235 > > > > * 40968 (my repeater) is using static ip (on my LAN) of 192.168.20.243 > > > > > > > > The repeater was working fine up until about a month ago when It quit connecting to any nodes. > > > > > > > > This morning I reset my router and reconfigured anything ? no change > > > > This morning I reformatted my repeater box and reconfigured using the Allstar Portal ? no change > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

1 0