On 02/09/2015 04:08 PM, Skyler F wrote:

Maybe you should create an announcement on connect, which plays an audio file just to the node that connected to politely ask them to stay for longer than a minute. I wonder if that is possible to send audio to specific nodes? In my opinion, a minute or two is good enough. I just get ticked off when someone connects and then disconnects so fast, in matter of seconds. they don't even throw their ID out.

I stopped a reply that I was making, along those same lines, but then I stopped to think... if someone on a linked repeater system connects to a node, then, in the nature of how allstar works, that audio played from the node being connected to, would play throughout the linked repeater system. That'd probably confuse regular users of that system. Remember, after all, *we*, the guys and gals who do the configuration of our nodes/repeaters, -are- (99% of the time) those responsible for our systems. Having that kind of audio playing out, I wouldn't think, would most probably not be a good idea. Although, there's not much difference in operators of allstar and echolink, if all they're going to be doing is connecting for a minute or two, then disappearing with out waiting around for a response (if they say anything at all), or a drive-by to see if anyone is talking, hearing nothing, and disconnecting and moving to the next node. This is how hams lost 11 meters, back in the late 40's. People go and listen, hear nothing, don't say anything, and then go away. The band was probably open more often than not, but if no one was talking while someone was listening, then those listening would assume the band is dead. Connect, wait to see if the system is busy or not, then (if not) make some noise! Wait around a bit! Make some noise *again*! THEN, move on. It's exactly because of the drive-by's on Echolink (mostly) that I've turned the telemetry "OFF" on my nodes. If they don't say anything, I don't even want to know they're there. If they feel like the users of my system are ignoring them, then it's their loss, by not keying up and identifying their presence. Your mileage may vary. -Geoff/W5OMR

On 02/09/2015 04:37 PM, Doug Crompton wrote:

Putting a connect message in /var/lib/asterisk/sounds/rpt/nodenames/ would be an option. If you are using the BBB the tts_audio.sh script would create the audio file for you from a text file.

It's a bad idea. See my previous message on this subject.

This thread has proved useful one of my punch list items is to create a custom message for our little group. Looks like the BBB is pretty straight forward. My Cent OS box might take some more research on my end. Thank you

Tim, Good to know. Maybe that should be added to the wiki page on the connect messages. 73 Doug WA3DSP http://www.crompton.com/hamradio Subject: Re: [App_rpt-users] Hit and run From: tim.sawyer@mac.com Date: Mon, 9 Feb 2015 16:34:28 -0800 CC: app_rpt-users@ohnosec.org To: doug@crompton.com Nodenames on a local node won’t be heard on the connecting node. But it could be done with a connect script:connpgm=welcome.sh ; Default: Disabled. Execute a program you specify on connect. ; passes 2 command line arguments to your program: ; 1. node number in this stanza (us) ; 2. node number being connected to us (them) welcome.sh#! /bin/bash asterisk -rx “rpt playback $1 <sound_file_base_name>" -- Tim :wq On Feb 9, 2015, at 3:33 PM, Doug Crompton <doug@crompton.com> wrote:I am not sure what the difference would be. You are going to get the default connect message anyhow so if you add your words and where you are really connected to it would make more sense. Instead of the brain dead - node xxxxx connected to xxxxx in Alison's voice you could have a nice google voice saying - Welcome to the the Silicon Valley ARC Allstar node. Please stay connected a few minutes for any calls. or whatever you wanted to say. And in actuality the slowww Alison voice which probably take as long to speak as what I wrote above in the google voice. Not all node groups have repeaters connected. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Mon, 9 Feb 2015 16:41:35 -0600 From: ars.w5omr@gmail.com To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Hit and run On 02/09/2015 04:37 PM, Doug Crompton wrote: Putting a connect message in /var/lib/asterisk/sounds/rpt/nodenames/ would be an option. If you are using the BBB the tts_audio.sh script would create the audio file for you from a text file. It's a bad idea. See my previous message on this subject. _______________________________________________ App_rpt-users mailing list App_rpt-users@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 listApp_rpt-users@ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-usersTo 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.

Moved to the correct stanza and a minor tweak or two, that would work nicely. I like it. Much more the Asterisk way. -- Tim :wq

On Feb 9, 2015, at 7:15 PM, Robert A. Poff <wb3awj@comcast.net> wrote:

Or a cleaner way is to do something like this in extensions.conf. Or wherever your repeater extension is defined.

[radio-gui] exten => 28260,1,Playback(/path/to/file.ulaw) exten => 28260,n,Wait(3) exten => 28260,n,rpt,28260|P

From the iaxRpt access definition on one of my nodes.

-- Sent from my Android device with K-9 Mail. Please excuse my brevity._______________________________________________ App_rpt-users mailing list App_rpt-users@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.

Yes, that's true. And as previously stated, that's the underlying beauty of this software. There is not always ONE way to do something. In fact, I have loads of my own supporting scripts running on my nodes. However the current question was simply how to play a greeting message to an inbound connecting node without the existing connections being bothered by it. The snippet I posted was in fact a only a small bit of code that I use on my frequency agile base to restrict access to only "registered" nodes/users. I do that in lieu of having the user log in. Bob, WB3AWJ Loganville, Pa On February 10, 2015 1:55:21 AM EST, Doug Crompton <doug@crompton.com> wrote:

I think they both have their place. The script gives you loads more flexibility. You can do more than just play a sound file.

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.