September 2013 - App_rpt-users

USING own SIP for AUTO PATCH
by Bradley Haney 04 Sep '13

04 Sep '13

Hello all. Having an issue with ACID trying to use my own SIP.. It appears when i try to enter in the correct info for the peer and registry statement on the sip.conf and do a astres.sh it bombs out where for what ever reason for the next 10 or so when i log in and do a asterisk -r and do help there are no SIP option on the command line.. then after some time it some how starts up. I thought something was wrong with my system so i put the install disc in again and re downloaded all the software and started over. Everything works fine until i try to add a peer into the SIP.conf I tried the settings for asterisk 1.2, 1.4 and even 1.8 VOIP povider i use is callcentric. Any thoughts? I have been using callcentric for about 2 years on my regular PBX and no issues. ON a side note does anyone have a good inbound extension.conf part that woudl include incoming from my own SIP to be able to have the asterisk answer and let phone control work on the repeater. I would easily pay the 5.00 month for the service, but our members would like to have a local number for our repeater. Thanks in advance. Bradley kc9gqr

2 1

Re: [App_rpt-users] execute CLI command via macro?
by Geoff Edmonson 03 Sep '13

03 Sep '13

You mean like root@[local]> asterisk -rx "rpt fun [node number] *81" and... You want to do that from a macro? No. However, if you want to connect to different nodes, that's entirely what the [macro] stanza in rpt.conf is all about. Search the archives here or on ohnosec.org or even Timmy's drupal page. Google is your friend. "Bryan D. Boyle" <bdboyle(a)bdboyle.com> wrote: >digging through the list archives, yes it's painful. would yield a treasure trove on this topic. > >-- >Bryan >Sent from my iPhone 5...small >keyboard, big fingers...please >forgive misspellings... > > > >On Sep 3, 2013, at 4:14, Paul Schlacter <paulschlaterradio(a)gmail.com> wrote: > >> Hello Group, >> Is there a conventional way to execute CLI commands via a custom macro? >> >> In other words: >> >> Could app_rpt take a received DTMF command to execute a macro that would execute a predefined CLI command? >> >> 73 all! >> >> Paul >> _______________________________________________ >> 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

execute CLI command via macro?
by Paul Schlacter 03 Sep '13

03 Sep '13

Hello Group, Is there a conventional way to execute CLI commands via a custom macro? In other words: Could app_rpt take a received DTMF command to execute a macro that would execute a predefined CLI command? 73 all! Paul

2 1

Re: [App_rpt-users] RXONDELAY not working?
by tom 02 Sep '13

02 Sep '13

The chan_simpleusb.c code clearly has the rxondelay parameter. However, I tested it on a couple of half-duplex nodes and didn't see any effect. A bug? Tom / K5TRA

5 6

Paul, Your Email box is full
by Jim W7RY 02 Sep '13

02 Sep '13

Hey Paul... AH6FM Trying to send you a message... Your email box is full... So the system says... Thanks and Aloha! 73 Jim W7RY

1 0

Re: [App_rpt-users] linktolink syntax in rpt.conf & passing of tuchtones
by C B 01 Sep '13

01 Sep '13

Thank you Chris ________________________________ From: "cwsaums(a)aol.com" <cwsaums(a)aol.com> To: C B <harvard5362(a)yahoo.com> Sent: Sunday, September 1, 2013 1:50 PM Subject: Re: [App_rpt-users] linktolink syntax in rpt.conf & passing of tuchtones Here is the configuration example for value pairs in configuration stanzas This shows the correct answer is - No spaces http://ohnosec.org/drupal/node/46 Craig AC2FE Sent from my iPad On Sep 1, 2013, at 4:05 PM, C B <harvard5362(a)yahoo.com> wrote: Hi I have read different examples of the "linktolink" statement in rpt.conf there are 2 different examples one with a space either side of the "=" sign and one with no spaces. 1) linktolinl = yes 2) linktolink=yes Which is the correct syntax. Also when connecting a allstar node to another controllers port, will touch tones frome a station conning into a allstar nose pass from the next allstar node to the controller? Thank you in advance for your help. Chris _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

linktolink syntax in rpt.conf & passing of tuchtones
by C B 01 Sep '13

01 Sep '13

Hi I have read different examples of the "linktolink" statement in rpt.conf there are 2 different examples one with a space either side of the "=" sign and one with no spaces. 1) linktolinl = yes 2) linktolink=yes Which is the correct syntax. Also when connecting a allstar node to another controllers port, will touch tones frome a station conning into a allstar nose pass from the next allstar node to the controller? Thank you in advance for your help. Chris

1 0

Allstar on different distros
by Tony KT9AC 01 Sep '13

01 Sep '13

OK, I'm going to ask if there ongoing efforts to package or provide install schemes for different hardware? I have had a node running for years on an old P4 just fine. For a low-power, fanless box I've gravitated toward the HP Thin clients, which really aren't that bad. 1.0Ghz AMD Geode, 512MB ram and an upgrade to a 44-pin 8GB Compact Flash. I have a need to build and remotely deploy three of these and would like a common install to manage. I do the standard noatime and tmpfs changes to keep the flash quiet and happy. ACID won't install on Thin Clients; XIPAR will install but takes about 3-4 hours and doesn't do MDC1200 or record traffic that I need (acid archives). I can install Debian 7.1 in about 20 minutes and it absolutely flies. Asterisk 1.8 and the current ACID SVN all compile under Debian but I can't get it to work with the URI interface. Dmesg and lspci show the URI but Allstar using the "radio tune" shows the card as "-1". I have a whole weekend in this latest build attempt. It would seem that out in the real world you can install Asterisk on anything, and that is the spirit of open-source. What would be required to get app_rpt and some of the chan stuff to run on "commodity" installs (apt-get install asterisk for example)? A lot of this is over my head, but I'm willing to try. I realize that some builds were customized for a point in time, so that begs the question about modern day attempts (Debian 7.1 runs the 3.2.0-4-686-pae kernel). Thanks Kirk for your script, but I found out late last night it doesn't use the same hardware that I do. Thanks. Tony (27129/27418/27460)

3 3

Cylon Suppression
by David Osborn 01 Sep '13

01 Sep '13

I followed with interest the discussion on accessing command mode with a macro, and the innovative ideas to achieve the desired result. That was very informative and speaks to the flexibility that Jim and others built-in to AllStar (Kudos, guys). I'm looking at a similar project but I keep getting attacked by the Cylons J (http://www.youtube.com/watch?v=0ccKPSVQcFk ) Our hub node (2483) hosts the EchoLink gateway. It has no RF hardware connected to it (then it wouldn't be a hub!). If a user on one of our other nodes wants to make an EchoLink connection, he has to go into command mode to access the hub first, then (after the Cylons have had their say), they enter the command to make the EchoLink connection, and so-on. That works well, but it's a little long-winded. What I would like to do is create a "Speed Dial" for a selected list of EchoLink nodes, and Macros appear to be ideal for this. The idea is that the Macro would accept a 3-digit suffix to connect, and a different 3-digit suffix to disconnect, like this: [functions] 6 = macro [macro] 101 = *42483*33338712# ;Connect echolink 102= ...Next connect macro 201= *42483*13338712# ;Disconnect echolink 202=...Next Disconnect macro This means that, keying *6101 will connect to the first EchoLink node (GD4HOZ, as it happens!), and keying *6201 will disconnect it. It works, except... Because there's no gap in the macro execution, the Cylons stick their galactic oars in ("By Your Command") and it actually comes out of the remote EchoLink node - which would come as a shock to the node owner. What I'm looking for is an approach that will ideally circumvent the Cylon message (even though I do kinda like it) and just get-on with the job of connecting. Perhaps a script, as Brian suggested, would do the job, by adding a delay or two, but that would still give the command message to the local user - which may not be a bad thing. Has anybody else done any EchoLink "Speed Dial" trickery? David

3 3