May 2012 - App_rpt-users - lists.keekles.org

Nodeshark help ...
by Tony Youngblood 21 May '12

21 May '12

Installing nodeshark and made proper directories and folders as I can see the wav and other files generate I'n my qso logs. Nodeshark says sync is successful but not showing any data. I research this error abit but didn't find exactly what I needed for this scenario. Action-> Executing:pscp -v -P (myport) -pw (mysecret) (user)@(nodeIP):/etc/asterisk/qso/201202* c:\qso\qso28384 ERROR-> 'pscp' is not recognized as an internal or external command, operable program or batch file. Any advice, tips? 73 ;(;) AllStar 28384 Irlp 7998 / 7766 / 7926 Echo 563329 :(:)

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 39, Issue 24
by Tony Youngblood 21 May '12

21 May '12

Change it... One of the first things I did on mine. 222 is not required per say. I haven't even configured SIP for myself and a gazillion attempts from this ip addy. grrrr ;(;) AllStar 28384 Irlp 7998 / 7766 / 7926 Echo 563329 :(:) On May 20, 2012, at 10:43 PM, app_rpt-users-request(a)ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: SIP bots, hack attempts? - SSH also (dave k) > 2. What is a PGCM (Fran) > 3. Re: SIP bots, hack attempts? (George Csahanin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 20 May 2012 20:03:00 -0700 (PDT) > From: dave k <dave_k_420(a)yahoo.com> > To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] SIP bots, hack attempts? - SSH also > Message-ID: > <1337569380.87802.androidMobile(a)web114004.mail.gq1.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > I am seeing brute force attempts to ssh/222. This is my first time running on 222 so i assumed it would be unknown. Is 222 a common alternative? > > Sent from Yahoo! Mail on Android > > From: Don Hackler <donh(a)sigma.net>; > To: Tony Youngblood <k5try73(a)gmail.com>; > Cc: app_rpt-users(a)ohnosec.org <app_rpt-users(a)ohnosec.org>; > Subject: Re: [App_rpt-users] SIP bots, hack attempts? > Sent: Mon, May 21, 2012 2:27:51 AM > > Any VOIP system with exposed SIP ports will get hit regularly by 'bots trying to get in. > > (I mostly see them from China and other Asian countries?) > > First, make sure your system is behind a firewall. ?Don't expose any ports you don't absolutely have to. > > Second, use really good passwords on your SIP accounts and anything else that is exposed to the outside. > > Third, make sure that if they manage to hack a SIP account, make sure they can't run up a bunch of charges on an outbound VOIP trunk. > > (If you have a VOIP provider hooked up for outbound calls, only leave enough money prepaid in the account you are willing to risk; maybe $25 or so. ?Don't enable international calls. ?Don't enable auto-replenishment from a credit card.) > > If they get in, they will route dozens of calls simultaneously through your system. ?In a half hour, they can run up thousands of call minutes if you let them. > > > > On May 20, 2012, at 7:13 PM, Tony Youngblood wrote: > > Interesting discussion I had about sip hacks I had so I checked my log. Any details, advice, insight? > > file is 71,073,169 big! > > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fu-min"<sip:fu-min@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fu-tze"<sip:fu-tze@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fu-yeung"<sip:fu-yeung@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fugwo"<sip:fugwo@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuarnibol"<sip:fuarnibol@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuat"<sip:fuat@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fubler"<sip:fubler@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuccellaro"<sip:fuccellaro@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuchsberger"<sip:fuchsberger@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuck-me-over-some-more"<sip:fuck-me-over-some-more@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fucktool"<sip:fucktool@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fudd"<sip:fudd@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fude"<sip:fude@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fudenberg"<sip:fudenberg@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > [Mar? 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fudge"<sip:fudge@108.238.216.11>' failed for '95.211.167.69' - No matching peer found > > ;(;) > > AllStar 28384 > > Irlp 7998 / 7766 / 7926 > > Echo 563329 > > :(:) > > > On May 19, 2012, at 11:00 AM, app_rpt-users-request(a)ohnosec.org wrote: > > Send App_rpt-users mailing list submissions to > ? ?app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > ? ?http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > ? ?app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > ? ?app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > Today's Topics: > > ??1. adding extensions to acid ?all-star repeater (Bradley Haney) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 19 May 2012 09:19:32 -0500 > From: Bradley Haney <kc9gqr(a)gmail.com> > To: app_rpt-users(a)ohnosec.org > Subject: [App_rpt-users] adding extensions to acid ?all-star repeater > Message-ID: <E3E3A42F-65BD-4B2E-BE21-67654048A29C(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > Hello all.. > > Been looking through the old forums and trying to get a handle on how to add ?SIP extensions to my all-star box. ?We are currently running acid distro on our repeater and using the allstarlink auto patch service. ??I would like to be able to add a few sip extensions ??so when i am on my cell phone i can connect to the repeater and listen or dial ?my wife who is a ham on a different extension and ring her phone. ??The extensions do not have to have ?"outside access" for the auto patch as the extensions would be used for internal communication to and from the repeater or to and from other extensions i add . ?Example ?extension 123 (which would be a sip client) be able to dial 28079 which is the repeater. ?or ?a person on the repeater ?be able to dial ?extension 123 and have the sip client ring. ?I have a static ip address so i know that won't be a problem, ?just a little confused on how to add everything in the ?config files. ??Does > anyone by ?chance have a good working example > ?they could share? ?I would try the other distro ?but everyone like the web trans idea instead of using echo link ?:) ??? > > Thanks for any help i could get.. > > Bradley > allstar node 28079 > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > End of App_rpt-users Digest, Vol 39, Issue 22 > ********************************************* > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >

1 0

Re: [App_rpt-users] SIP bots, hack attempts? - SSH also
by dave k 21 May '12

21 May '12

I am seeing brute force attempts to ssh/222. This is my first time running on 222 so i assumed it would be unknown. Is 222 a common alternative? Sent from Yahoo! Mail on Android From: Don Hackler <donh(a)sigma.net>; To: Tony Youngblood <k5try73(a)gmail.com>; Cc: app_rpt-users(a)ohnosec.org <app_rpt-users(a)ohnosec.org>; Subject: Re: [App_rpt-users] SIP bots, hack attempts? Sent: Mon, May 21, 2012 2:27:51 AM Any VOIP system with exposed SIP ports will get hit regularly by 'bots trying to get in. (I mostly see them from China and other Asian countries…) First, make sure your system is behind a firewall. Don't expose any ports you don't absolutely have to. Second, use really good passwords on your SIP accounts and anything else that is exposed to the outside. Third, make sure that if they manage to hack a SIP account, make sure they can't run up a bunch of charges on an outbound VOIP trunk. (If you have a VOIP provider hooked up for outbound calls, only leave enough money prepaid in the account you are willing to risk; maybe $25 or so. Don't enable international calls. Don't enable auto-replenishment from a credit card.) If they get in, they will route dozens of calls simultaneously through your system. In a half hour, they can run up thousands of call minutes if you let them. On May 20, 2012, at 7:13 PM, Tony Youngblood wrote: Interesting discussion I had about sip hacks I had so I checked my log. Any details, advice, insight? file is 71,073,169 big! [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fu-min"<sip:fu-min@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fu-tze"<sip:fu-tze@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fu-yeung"<sip:fu-yeung@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fugwo"<sip:fugwo@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuarnibol"<sip:fuarnibol@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuat"<sip:fuat@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fubler"<sip:fubler@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuccellaro"<sip:fuccellaro@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuchsberger"<sip:fuchsberger@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fuck-me-over-some-more"<sip:fuck-me-over-some-more@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fucktool"<sip:fucktool@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fudd"<sip:fudd@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fude"<sip:fude@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fudenberg"<sip:fudenberg@108.238.216.11>' failed for '95.211.167.69' - No matching peer found [Mar 6 23:59:41] NOTICE[1694] chan_sip.c: Registration from '"fudge"<sip:fudge@108.238.216.11>' failed for '95.211.167.69' - No matching peer found ;(;) AllStar 28384 Irlp 7998 / 7766 / 7926 Echo 563329 :(:) On May 19, 2012, at 11:00 AM, app_rpt-users-request(a)ohnosec.org wrote: Send App_rpt-users mailing list submissions to app_rpt-users(a)ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request(a)ohnosec.org You can reach the person managing the list at app_rpt-users-owner(a)ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. adding extensions to acid all-star repeater (Bradley Haney) ---------------------------------------------------------------------- Message: 1 Date: Sat, 19 May 2012 09:19:32 -0500 From: Bradley Haney <kc9gqr(a)gmail.com> To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] adding extensions to acid all-star repeater Message-ID: <E3E3A42F-65BD-4B2E-BE21-67654048A29C(a)gmail.com> Content-Type: text/plain; charset=us-ascii Hello all.. Been looking through the old forums and trying to get a handle on how to add SIP extensions to my all-star box. We are currently running acid distro on our repeater and using the allstarlink auto patch service. I would like to be able to add a few sip extensions so when i am on my cell phone i can connect to the repeater and listen or dial my wife who is a ham on a different extension and ring her phone. The extensions do not have to have "outside access" for the auto patch as the extensions would be used for internal communication to and from the repeater or to and from other extensions i add . Example extension 123 (which would be a sip client) be able to dial 28079 which is the repeater. or a person on the repeater be able to dial extension 123 and have the sip client ring. I have a static ip address so i know that won't be a problem, just a little confused on how to add everything in the config files. Does anyone by chance have a good working example they could share? I would try the other distro but everyone like the web trans idea instead of using echo link :) Thanks for any help i could get.. Bradley allstar node 28079 ------------------------------ _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users End of App_rpt-users Digest, Vol 39, Issue 22 ********************************************* _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

2 1

adding extensions to acid all-star repeater
by Bradley Haney 19 May '12

19 May '12

Hello all.. Been looking through the old forums and trying to get a handle on how to add SIP extensions to my all-star box. We are currently running acid distro on our repeater and using the allstarlink auto patch service. I would like to be able to add a few sip extensions so when i am on my cell phone i can connect to the repeater and listen or dial my wife who is a ham on a different extension and ring her phone. The extensions do not have to have "outside access" for the auto patch as the extensions would be used for internal communication to and from the repeater or to and from other extensions i add . Example extension 123 (which would be a sip client) be able to dial 28079 which is the repeater. or a person on the repeater be able to dial extension 123 and have the sip client ring. I have a static ip address so i know that won't be a problem, just a little confused on how to add everything in the config files. Does anyone by chance have a good working example they could share? I would try the other distro but everyone like the web trans idea instead of using echo link :) Thanks for any help i could get.. Bradley allstar node 28079

1 0

Re: [App_rpt-users] Any RTCM Voter Installations Out There?
by Tim Sawyer 17 May '12

17 May '12

There are two halves. 1) the RTCM needs to be connected to the radio and configured. 2) configure app_rpt/chan_voter. You are asking about the second half. First, you should always update from SVN when setting up a new system and periodically thereafter. The instructions are on the Allstar site in the support section. Then chan_voter needs to be configured. That happens by adding one file (voter.conf) and modifying one line in rpt.conf. -- Tim :wq On May 17, 2012, at 11:35 AM, Frederick Bray wrote: > Hi Tim, > > Thanks for the offer of help. > > Assuming that I have a clean install of the latest ACID Centos distribution, what do I need to add to get the voter functionality? I'm just looking for a bit of an overview -- such as "compile and install X" rather than detailed step by step instruction as to how to do it. > > Thanks. > > Fred > > On 5/17/2012 11:10 AM, Tim Sawyer wrote: >> I'm not so sure about an "average" user, but I'm glad to help anyway. :-) >> >> The stuff on the project page is old. There's a newer voter doc on the micro-node site. Read through that but don't feel bad if it doesn't make total sense. It's easy once you know how. I'll be glad to help you shorten the learning curve. Just send me an email off list or post your questions here. Telephone is ok too... sometimes that's much easier. >> -- >> Tim >> :wq >> >> On May 17, 2012, at 9:27 AM, Frederick Bray wrote: >> >>> I very recently purchased my RTCM module and will be ordering a second one soon. >>> >>> It will be a while before I have time to get it all running, but I thought I'd see whether there are any "average" users out there who might relate their experiences for the purpose of helping to educate me. (Jim Dixon has very kindly offered assistance, but because of work commitments it will be a while before I can meet with him.) >>> >>> I gather that chan_voter isn't included in the current ACID CENTOS distribution and will need to be compiled on my system. I can do this as I have a little bit of UNIX/Linux experience, but I don't want re-invent the wheel unnecessarily. >>> >>> Is there any documentation that I should be reading in addition to that on the voter project site? >>> >>> Thanks. >>> >>> 73, >>> >>> Fred Bray >>> W6WAW >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >

1 0

Re: [App_rpt-users] Technically possible?
by dave k 14 May '12

14 May '12

We just did the same thing. Multisite analog to multi side DMR bridge w/mobile radio and all star. Worked very nice. Audio going from analog to digital in some cases actually sounded better on digital thanks to the noise reduction in the trbo. Still have large variation in the digital audio levels occasionally overloading the URI input but I suspect could be helped with a inline compressor/limiter. Sent from Yahoo! Mail on Android

2 1

Technically possible?
by Alan Adamson 13 May '12

13 May '12

I have searched high and low and yet haven't found much good information for what I'm about to ask. I hope this mail list might help with that. I'm about to dive into AllStar and all its associated parts. BUT, I'd like to know if what I'm thinking makes sense, and that there isn't a more preferred way of doing it? I have a wide area coverage (for Atlanta anyway) 440 ham repeater, it's currently a Master II converted. I'm about to replace it with an NXDN Icom 440 repeater (digital, but it will continue to run in mixed mode as well). I'd like to be able to connect it to AllStar, or other VOIP services (yes, like IRLP, maybe Echo, and who knows maybe someday D-Star). Now don't get all excited, I'm not about to think that I can do that *digitally*. All audio will be analog either decoded or about to be encoded. Secondly, I'd like to *remote* all the services to my house and host them from there, instead of at the repeater site. It does have internet, but it's remote, not readily accessible, etc. So, is the following feasible, desired, are the better ways to do what I'm thinking? a) take the analog audio input/output at the repeater and put it into either a URI with a fanless PC install of AllStar, or a PicoNode with Pickle and LOX. b) put the other services (ala, IRLP, Echo, etc) at my house with a dedicated PC setup with URI's and another install of AllStar (ok, Asterisk and it's associated radio parts) c) connect all that together with IP and the appropriate setups to allow links to be created, torn down. NOTE: I didn't say anything about any form of *external controller*, other than the Unix boxes and their AllStar installs. I'm hoping I won't need one and will just use the NXDN repeater and its internal controller for what is needed at the repeater. If I did the above, what issues will occur when you link the repeater to oh say IRLP via an IP connection between two AllStar nodes? Will there be any issues with DTMF, tail crashes, courtesy tones, etc. Either not being there or being there when they shouldn't be? Lastly is it possible to add a simplex radio to the home node such that it will connect me to the repeater, or other services (again over and IP link)? Sheesh, I get confused just trying to explain this.. I've looked all over to try and find some similar examples of this, I'm sure they exist, but it appears that either I'm not entering the right Google search phrases or they aren't too well documented. Any help, advice, steering, etc welcome. Thanks, Alan

5 5

Re: [App_rpt-users] [possibly OT] AllStar registration
by Giuseppe Marullo 12 May '12

12 May '12

On 5/12/2012 5:58 PM, Tim Sawyer wrote: > Yes, the registration process can be very frustrating. Please explain "nothing works". > -- > Tim > :wq Tim, thanks for your answer. Here it is: 1) Tried to register. I filled all the fields. 2) Received a confirmation email on my address. Title "Welcome to AllStar Link Networks" 3) Copied and pasted the link I received to confirm into a browser 4) Received the following on the page: Account activation * Token does not exist / Account is already activated 5) Tried to login on the home page. Received: Callsign or password is invalid 6) Tried to recover password. Received: Forgot Password * Invalid email address * Invalid username 7) Tried to contact the administrator for the validation process. No reply after several days. Tried to send email on most of the addresses on the contact page. No dice. 8) Tim, you are my point 8 Giuseppe Marullo IW2JWW - JN45RQ

1 0

Re: [App_rpt-users] [possibly OT] AllStar registration
by Giuseppe Marullo 12 May '12

12 May '12

> Did you click the link to confirm your e-mail address? They also need to verify you have a call sign. Sure, but from that it went south. > Are you in Italy? I'll be in Rome for a couple days, and just happened to see your e-mail. My mom and I came over here on a cruise ship. WE visited Livorno and Pisa yesterday. Matt, I am near of Milan. I have been in Rome about 3 weeks ago for a week. How is it going? Cruise ships are not so popular these days here, you will understand. Giuseppe Marullo IW2JWW - JN45RQ

1 0

ices plugin
by dave k 12 May '12

12 May '12

Im trying to activate the ICES icecast output module as a always on link to my freestar node. I'm a asterisk newb, so i need a little help. I believe I need to add exten => 28525,n,Ices(/etc/asterisk/asterisk-ices.conf) to my extensions.conf. Is this correct? I tried putting it under [radio] [radio-secure] and its own separate [stream] section but i never see the ices application execute. Do i need to add a separate extension and make a call between them? How would i debug this? thanks confused dave

4 5