September 2013 - App_rpt-users

announcements
by Harry Romano 09 Sep '13

09 Sep '13

Hi all , How do you turn off the announcements in allstar? Is there a way to turn their volume down? 73's Harry KC4RPP

7 11

announcements
by Ken 08 Sep '13

08 Sep '13

>>When you set the TX and RX levels per instructions the announcements will be the correct level. Actually Harry, many people find the announcements too loud for their tastes, even when everything is adjusted OK. A while back somebody posted a script that went through the entire directory containing all the announcements and lowered the volume by a certain number of DB. Perhaps with some searching you could find it, or some other user on here will have a copy. 73 Ken

1 0

Passing DTMF to another controller
by C B 08 Sep '13

08 Sep '13

Hi I am trying to get DTMF from other ALLSTAR nodes to pass to a controller connected to a node. My configuration is a beagle board with the controller on port 2 (another controller will ne on port 1 latter). I have set in the RPT.CONF linktolink=yes propagate_dtmf=yes On both nodes. Below I have copied my RPT.CONF information in case I have placed them in the wrong place or I have a syntax error or some other error. Thank you in advance for any help. Chris ; Radio Repeater configuration file (for use with app_rpt) ; ; ; Your Repeater ; [29876] ; Change this to your assigned node number rxchannel=Beagle/beagle29876 duplex=0 erxgain=-3 etxgain=3 ;controlstates=controlstates scheduler=schedule29876 morse=morse29876 macro=macro29876 functions=functions29876 phone_functions=functions29876 link_functions=functions29876 telemetry=telemetry wait_times=wait-times context = radio callerid = "Repeater" <0000000000> idrecording = |iN6LXX accountcode=RADIO hangtime=001 althangtime=100 totime=170000 idtime=540000 politeid=3000 linktolink=yes propagate_dtmf=yes idtalkover=|iN6LXX unlinkedct=ct2 remotect=ct3 linkunkeyct=ct8 ;nolocallinkct=0 ;eannmode=1 ;connpgm=yourconnectprogram ;discpgm=yourdisconnectprogram ;lnkactenable=0 ;lnkacttime=1800 ;lnkactmacro=*52 ;lnkacttimerwarn=30seconds ;remote_inact_timeout=1800 ;remote_timeout=3600 nounkeyct=1 ;holdofftelem=0 beaconing=0 ; ; *** Status Reporting *** ; ; Uncomment the either group following two statpost lines to report the status of your node to stats.allstarlink.org ; depending on whether you are running ACID or Limey Linux. ; ** For ACID *** statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ** For Limey Linux ** ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ; Morse code parameters, these are common to all repeaters. ; [morse29876] speed=18 frequency=800 amplitude=4096 idfrequency=750 idamplitude=1024 [schedule29876] ;dtmf_function = m h dom mon dow ; ala cron, star is implied [functions29876] 1=ilink,1 2=ilink,2 3=ilink,3 4=ilink,4 5=macro,1 70=ilink,5 71=ilink,6 72=ilink,7 73=ilink,15 74=ilink,16 75=ilink,8 80=status,1 81=status,2 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up 0=autopatchdn ; Autopatch down 989=cop,4 980=status,3 99=cop,6 ; Place command macros here [macro29876] [29877] ; Change this to your assigned node number rxchannel=Beagle/beagle29877 duplex=0 erxgain=-3 etxgain=3 ;controlstates=controlstates scheduler=schedule29877 morse=morse29877 macro=macro29877 functions=functions29877 phone_functions=functions29877 link_functions=functions29877 telemetry=telemetry wait_times=wait-times context = radio callerid = "Repeater" <0000000000> idrecording = |iN6LXX accountcode=RADIO hangtime=100 althangtime=100 totime=170000 idtime=540000 politeid=3000 linktolink=yes propagate_dtmf=yes idtalkover=|iN6LXX unlinkedct=ct2 remotect=ct3 linkunkeyct=ct8 ;nolocallinkct=0 ;eannmode=1 ;connpgm=yourconnectprogram ;discpgm=yourdisconnectprogram ;lnkactenable=0 ;lnkacttime=1800 ;lnkactmacro=*52 ;lnkacttimerwarn=30seconds ;remote_inact_timeout=1800 ;remote_timeout=3600 nounkeyct=0 ;holdofftelem=0 beaconing=0 ; ; *** Status Reporting *** ; ; Uncomment the either group following two statpost lines to report the status of your node to stats.allstarlink.org ; depending on whether you are running ACID or Limey Linux. ; ** For ACID *** statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ** For Limey Linux ** ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ; Morse code parameters, these are common to all repeaters. ; [morse29877] speed=18 frequency=800 amplitude=4096 idfrequency=750 idamplitude=1024 [schedule29877] ;dtmf_function = m h dom mon dow ; ala cron, star is implied [functions29877] 1=ilink,1 2=ilink,2 3=ilink,3 4=ilink,4 5=macro,1 70=ilink,5 71=ilink,6 72=ilink,7 73=ilink,15 74=ilink,16 75=ilink,8 80=status,1 81=status,2 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up 0=autopatchdn ; Autopatch down 989=cop,4 980=status,3 99=cop,6 ; Place command macros here [macro29877] [telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ct2=|t(660,880,150,2048) ct3=|t(440,0,150,4096) ct4=|t(550,0,150,2048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ct8=|t(700,1100,150,2048) remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); remotemon=|t(1209,0,50,2048) cmdmode=|t(900,903,200,2048) functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) patchup=rpt/callproceeding patchdown=rpt/callterminated ; ; This section allows wait times for telemetry events to be adjusted ; A section for wait times can be defined for every repeater ; [wait-times] telemwait=2000 idwait=500 unkeywait=2000 calltermwait=2000 ; ; This is where you define your nodes which cam be connected to. ; [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. 29876 = radio(a)127.0.0.1/29876,NONE 29877 = radio(a)127.0.0.1/29877,NONE ; Memories for remote bases [memory] ;00 = 146.580,100.0,m ;01 = 147.030,103.5,m+t ;02 = 147.240,103.5,m+t ;03 = 147.765,79.7,m-t ;04 = 146.460,100.0,m ;05 = 146.550,100.0,m #includeifexists custom/rpt.conf

2 2

Re: [App_rpt-users] SIP VoIP for Asterisk
by Dwaine Garden VE3GIF 07 Sep '13

07 Sep '13

Bill, sorry for hijacking your thread. Didn't mean it.... Dwine Bill South <wbs099(a)yahoo.com> wrote: > While this thread is not part of what I originally asked about (SIP provider recommendations) I'll add that 911 access is mandated in some LATAs, but seems to be some debate if it must be 911 or if 9-911 is OK, or other variations. I worked in the telecom business for over 25 years in various parts of the USA and different localities would respond differently to the question about 911. When E911 first came out, where a database lookup was done by the local police emeregency agency systems answering 911 calls showing names and addresses, some jurisdictions mandated that database had to show the exact location the call was originating from, not a billing address of some companies headquarters. Big problem for some large companies where a single billing address is used for all telco circuits. For residences I'm not sure anyone has put much thought into laws regarding 911 dialing and any restrictions thereof; businesses on the other hand, where > 100's maybe thousands of workers are in the same building and floor and locating a 911 caller could be pretty tough for local emnergency responders, there are, or were anyway, laws in some locations mandating 911 unrestricted. The thought has always been though that in an emergency people have the expectation, whether at home or work, that they can dial 911 and get help; not sure where the laws stands now on that across the USA. > >-------------------------------------------- >On Thu, 9/5/13, Dwaine Garden VE3GIF <DwaineGarden(a)rogers.com> wrote: > > Subject: Re: [App_rpt-users] SIP VoIP for Asterisk > To: "Jim Duuuude" <telesistant(a)hotmail.com> > Cc: "app_rpt mailing list" <app_rpt-users(a)ohnosec.org> > Date: Thursday, September 5, 2013, 7:40 PM > > Canadian customers have to provide an > address and name for 911 purposes for a DID. Bell and > Rogers were mandated with their VoIP services. > > I gave them the logs of the server where the IP address were > listed. Rogers was good and moved me to a new IP address > and filtered out the source. > > I had an iptables script that would ban IP address that > attempted a certain number of connections during a certain > amount of time. Then ban that IP address. It worked great. > It stopped the hackers script dead cold. Until they ran > the 911 script. They were ruthless in their attacks. > > My all-star node was the best fun I have had with Ham radio. > I'll fire it back up again. Just waiting for the dust > to settle without a DID setup. > > Dwaine > > Jim Duuuude <telesistant(a)hotmail.com> wrote: > > Double BRAVO-SIERRA!! > > If that were true, a LOT of large business owners (some of > which may even operate > large businesses :-) ) would be in jail, if they HAPPEN to > have a phone system or even > worse, service from the "phone company", that > requires dialing 9 to get an "outside line". > > I bet even the police dept has to dial 9 to dial 911. > > And as far as that goes, put the line in your pet > tarantula's name, and make it clear to them > that the spider is more then willing to 'serve its > time' for such a terrible transgressions!! :-) > > Wholesale outbound telecom services, such as ones provided > by most SIP providers, are *NOT* > "in your name", *NOR* do they even technically > have a "phone number" or a "service > address". > Just because you pay the bill for them does not, in any > manner, construe that you are the end user > of the service. > > Jim > > > > > Date: Thu, 5 Sep > 2013 14:58:42 -0400 > Subject: RE: [App_rpt-users] SIP VoIP for Asterisk > From: DwaineGarden(a)rogers.com > To: telesistant(a)hotmail.com > CC: dshaw(a)ke6upi.com; app_rpt-users(a)ohnosec.org > > It was an interesting experience. Has anyone else > experienced the same problem and had the police involved? > I did mention that I would change the > Dial string. The police told me that a person has to be > able to dial 911 and get emergency services. > > I gave up and just walked over to the all-star computer and > hit the power button. Sadly, it has been off ever since. > > If I had changed the 911 Dial string before the incident. > The police would of not gotten involved. Never known about > the situation. > > Just let everyone know. The two police officers were very > good about it. They told me that its happening a lot and > 911 is getting a little upset about it. > > I told them they should go after the person responsible. > They told me that's you. The line is in your name. > > Anyway, just wanted to throw out there my experience. > > Dwaine > > Jim Duuuude <telesistant(a)hotmail.com> wrote: > > Okay (and yes, that is STUPID and most likely > WRONG, but most police depts are > just completely ignorant of telecom issues). So, fine... > GIVE them access to 911. > Let them dial it. But, sadly, on YOUR phone network, the > dialing string is just a LITTLE > bit longer (like about 30 digits in front of the 911)... get > it? > > Jim > > > Date: Thu, 5 Sep > 2013 14:07:58 -0400 > From: DwaineGarden(a)rogers.com > To: dshaw(a)ke6upi.com > CC: app_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] SIP VoIP for Asterisk > > The problem is you are not allowed by law to have a phone > without unrestricted access to 911. I had Metro Toronto > police at my door explaining that even if I block 911 to any > outside connections I would be breaking the law. If you > have a server on the internet with sip. They have to able > to connect to be able to call 911. > > I told the police it was retard. They told me that was fine > they will charge me. > > Police told me that even if someone breaks into your house. > If there is a phone install, the criminals better have > access to dial 911 unrestrictive. > > The hackers did not get into the box. They were trying for > months. Got pissed off and changed their script to dial > 911 constantly. SIP and DID see a 911 call. It dials it. > No questions asked. No login or nothing. > > The Police told me it was a huge problem. SIP or DID are > setup like a public pay phone. Full access to 911. > > It was an eye opener for me. You learn something new > everyday. If I see someone asking about SIP or DID. I let > them know about my experience. > > David KE6UPI <dshaw(a)ke6upi.com> wrote: > > I'm sorry Dwaine what are you > talking about? Sorry If I don't understand what your > talking about. > > I have both a public Asterisk server and a local > Asterisk server. I have never had anyone connect and make a > call that was not authenticated user.. Yes they try and > fail2ban will block them. There are many way to stop > unwanted hackers on your server. > > > > As for dialing 911 just make a dial plain to route to space > if you want. > > Google "Asterisk Security" > > http://www.voip-info.org/wiki/view/Asterisk+security > > > > David > > > > On Thu, Sep 5, 2013 > at 9:13 AM, Dwaine Garden VE3GIF <DwaineGarden(a)rogers.com> > wrote: > > It > works great until the hacks find the machine. They > port scan non stop. Its especially fun when their > scripts dial 911 constantly. There is no way to turn > off dialing 911 for SIP. > > > > > Bill South <wbs099(a)yahoo.com> > wrote: > > > > > I'm thinking of adding some type of > SIP trunking or other VoIP service provider to my ACID > Asterisk system to support in/out bound calling. > I've read some emails on the app_rpt reflector > with names of providers mentioned, but I am looking for > recommendations, as there are zillions of VoIP providers out > there. This is going to be used very sparingly so > least-cost is a good thing, but good reliability and no > bombardment with email adds by the provider is desired too. > I can easily get by with a single number, but may want > to add additional DIDs later. Thoughts? > > > > > > >Bill > > > > > > > > >_______________________________________________ > > >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 > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > -----Inline Attachment Follows----- > > _______________________________________________ > 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 1

Presentation
by Scott Weis 07 Sep '13

07 Sep '13

Does anyone have a presentation that covers asterisk/app_rpt/allstarlink that they would be willing to share? I have a club presentation on Wednesday and have been totally slammed at work. Thanks & 73 de, Scott KB2EAR

1 0

Beagle board Black
by Ken Robinson 07 Sep '13

07 Sep '13

Hi All, Can anyone tell me if the Beagle board Black will act as an Allstar node, reading about it I think some of the input outputs have been taken out of the new board 73's Ken G0lce

2 1

PCGM (Programmable Clock Generator Module)
by Randy Neals 07 Sep '13

07 Sep '13

Does anyone have any info on possibility availability of the PCGM? thx, -R

1 0

running out of 2XXXX node numbers
by Jim Duuuude 07 Sep '13

07 Sep '13

Since we were at the 'last' of the 2XXXX 5 digit node numbers, I "reclaimed" some un-issued node numbers in the 27000-29999 range. We now have 250 node numbers in the "free" pool that will be issued before going to a new number sequence. IF any of you have "reservations" for node numbers perhaps "next to" yours that haven't been assigned yet, speak now or forever hold your peace (or piece, perhaps, if you are a gun enthusiast :-) ), before what you were wanting/expecting gets given to someone else. Thanks Jim WB6NIL

1 0

Re: [App_rpt-users] permit= echolink.conf
by N7LD＠aol.com 06 Sep '13

06 Sep '13

Yes, you need to recompile after the change. make upgrade, make svsrc for Limey In a message dated 9/5/2013 8:51:12 P.M. Pacific Daylight Time, cypresstower(a)yahoo.com writes: Good call on echolink permit list increase by changing the EL_MAX_CALL_LIST 30 to a larger number. Did you have to recompile. Would you be kind enough to fill us in on the details??? Thank you From: "N7LD(a)aol.com" <N7LD(a)aol.com> To: tim.sawyer(a)me.com; app_rpt-users(a)ohnosec.org Sent: Thursday, September 5, 2013 8:43 PM Subject: Re: [App_rpt-users] permit= echolink.conf Thanks Tim, that worked!!! Set mine to 60 and it works. Lee In a message dated 9/5/2013 4:58:21 P.M. Pacific Daylight Time, tim.sawyer(a)me.com writes: Look at /usr/src/astsrc/asterisk/channels/chan_echolink.c I'm no good at C but I have a stinking suspicion that increasing EL_MAX_CALL_LIST would allow both bigger permit and deny lists :-) -- Tim :wq On Sep 5, 2013, at 11:25 AM, _N7LD(a)aol.com_ (mailto:N7LD@aol.com) wrote: Looks like I am having the same problem. Looks like the MAX stations is 30 Lee In a message dated 5/21/2013 11:08:47 A.M. Pacific Daylight Time, _w8jtw(a)yahoo.com_ (mailto:w8jtw@yahoo.com) writes: Is there anyway to increase the permit= list in echolink.conf to work with more than 25 or so stations? Once I get beyond 25 it does not want to allow beyond the first 25. Or is there a way to limit to just USA connections? I dont want to run a wide open echolink but have many friends i don't want to block need to have capacity of about 100 or so. Thought of trying Permit=W*,N*,A*,K* not sure if that would limit to just US callsigns or not. Any suggestions? Thanks Joe W8JTW Node 27891 _______________________________________________ App_rpt-users mailing list _App_rpt-users(a)ohnosec.org_ (mailto:App_rpt-users@ohnosec.org) http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list _App_rpt-users(a)ohnosec.org_ (mailto:App_rpt-users@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 _______________________________________________ App_rpt-users mailing list _App_rpt-users(a)ohnosec.org_ (mailto:App_rpt-users@ohnosec.org) http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Re: [App_rpt-users] permit= echolink.conf
by N7LD＠aol.com 06 Sep '13

06 Sep '13

Thanks Tim, that worked!!! Set mine to 60 and it works. Lee In a message dated 9/5/2013 4:58:21 P.M. Pacific Daylight Time, tim.sawyer(a)me.com writes: Look at /usr/src/astsrc/asterisk/channels/chan_echolink.c I'm no good at C but I have a stinking suspicion that increasing EL_MAX_CALL_LIST would allow both bigger permit and deny lists :-) -- Tim :wq On Sep 5, 2013, at 11:25 AM, _N7LD(a)aol.com_ (mailto:N7LD@aol.com) wrote: Looks like I am having the same problem. Looks like the MAX stations is 30 Lee In a message dated 5/21/2013 11:08:47 A.M. Pacific Daylight Time, _w8jtw(a)yahoo.com_ (mailto:w8jtw@yahoo.com) writes: Is there anyway to increase the permit= list in echolink.conf to work with more than 25 or so stations? Once I get beyond 25 it does not want to allow beyond the first 25. Or is there a way to limit to just USA connections? I dont want to run a wide open echolink but have many friends i don't want to block need to have capacity of about 100 or so. Thought of trying Permit=W*,N*,A*,K* not sure if that would limit to just US callsigns or not. Any suggestions? Thanks Joe W8JTW Node 27891 _______________________________________________ App_rpt-users mailing list _App_rpt-users(a)ohnosec.org_ (mailto:App_rpt-users@ohnosec.org) http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list _App_rpt-users(a)ohnosec.org_ (mailto:App_rpt-users@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 1