- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] 2 nodes setup to auto connect don't seem
by Mike Lussier 09 Feb '15

09 Feb '15

Sorry I'm at work I don't have access to the devices from where I'm at. You have given me a few areas to go look. Thank you Mike -- *"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan*

1 0

yet mire problemw
by jimmy keffer 09 Feb '15

09 Feb '15

my server is stuck in pst i change it but i do a shutdown -r it goes back and i try 2 change the host of the box but that also egos back on reboot someone please help me i have googleed till my blue lol

2 2

Re: [App_rpt-users] strange courtesy tone (or I'm going insane)
by Bryan Fields 09 Feb '15

09 Feb '15

On 2/9/15, 1:35 AM, mike(a)midnighteng.com wrote: > Guessing as you are... > > I'm a bit tired and need to hit the hay for now. > Will help tomorrow if still a problem you have not solved. > > It is a bit baffling but it must be just something being overlooked. I hope so, but I'm scratching my head at this point. > It appears to be two different tone sets. Look for something that matches > after the 6 beeps and see if it matches a CT. The 6 beeps are not CT's and > must be some error or triggered by some other event. Have you looked in > the logs ? I've looked at the logs and run it in debug too. No obvious errors (or any for that matter). Guess I could run it under GDB next.... 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

1 0

Re: [App_rpt-users] local rpt access via local extension?
by mike＠midnighteng.com 09 Feb '15

09 Feb '15

Jim, In asterisk, there are normally many ways to achieve the same thing. Don't make it more complicated if there is no need. Put your phone extensions in the radio control section. If you keep all the local extensions 4 digit and start with the same number, you can do something like this example... exten => 6XXX,1,Dial(sip/${EXTEN},20) ;dial ext on this box exten => 6XXX,2,VoiceMail(${EXTEN}) ;voicemail on noanswer That would be a statement that would cover all 4 digit extensions starting with a 6. my example has a voice-mail rollover. This way you do not need to define every extension. >From any extension you can dial the node number for the node you want to connect to. But to dial a phone extension from the repeater phone patch, you will need a similar/same line in the [radio] context. ...mike/kb8jnm > Mike, > > Thanks for the quick answer.. > > I have added extensions to the system using a Cisco SPA8000 > ATA. When I first configured the ATA and sip.conf I put the two > in-shack extensions into the radio-secure context as that seemed > logical.. and that did in fact work. I could call the node 27739 > and hit the USB interface. > > Even that doesn't work now. > > I've also tried this.. > > [in-shack] > include => radio-secure > exten => 6010,1,Dial(SIP/6010,60,rT) > exten => 6020,1,Dial(SIP/6020,60,rT) > > The radio-secure context is: > > [radio-secure] > exten => 27739,1,rpt,27739 > > > Thinking I could dial the 27739 extension from the in-shack contex.. not > working... > > > 73, > Jim > > > > >

1 0

Re: [App_rpt-users] strange courtesy tone (or I'm going insane)
by Bryan Fields 09 Feb '15

09 Feb '15

On 2/9/15, 12:06 AM, mike(a)midnighteng.com wrote: > Bryan, > > Not Defined? > I would put a definition in there as it is probably using a default since > nothing has been defined.(guessing from what you said). I have never not > defined them to know for sure. > > Just copy the [telemetry] section from one of your other nodes and use it. I'm using a common [telemetry] section. I've grep'd out the comments in my rpt.conf below. I'm stumped :) > root@asterisk:/etc/asterisk# grep "^[^#;]" rpt.conf > [40821] ; Change this to your assigned node number > rxchannel = Voter/1234 ; Rx audio/signalling channel > erxgain=-9 ; Echolink receive gain adjustment > etxgain=-3 ; Echolink transmit gain adjustment > functions=functions ; Repeater Function Table > phone_functions=functions ; Repeater Function Table > link_functions=functions ; Link Function Table > telemetry=telemetry ; Telemetry descriptions > wait_times=wait-times ; Wait times > macro=macro > startup_macro=*95329094 > context = radio ; dialing context for phone > callerid = "Repeater" <0000000000> ; callerid for phone calls > idrecording = |iW9CR ; id recording or morse string > accountcode=RADIO ; account code (optional) > hangtime=3000 ; squelch tail hang time (in ms) (optional) > althangtime=6000 ; longer squelch tail > totime=180000 ; transmit time-out time (in ms) (optional) > idtime=540000 ; id interval time (in ms) (optional) > politeid=30000 ; time in milliseconds before ID timer > idtalkover=none ; Talkover ID (optional) default is none > unlinkedct=ct4 ; unlinked courtesy tone (optional) default is none > remotect=ct3 ; remote linked courtesy tone (indicates a remote is in the list of links) > linkunkeyct=ct8 ; sent when a transmission received over the link unkeys > nolocallinkct=0 ; Send unlinkedct instead if another local node is connected to this node (hosted on the same PC). > eannmode=2 ; Default: 1 = Say only node number on echolink connects > beaconing=1 ; Send ID regardless of repeater activity (Required in the UK, but probably illegal in the US) > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > [902] > rxchannel = Zap/1 ; Rx audio/signalling channel > erxgain=-9 ; Echolink receive gain adjustment > etxgain=-3 ; Echolink transmit gain adjustment > duplex=2 > functions=functions ; Repeater Function Table > phone_functions=functions ; Repeater Function Table > link_functions=functions ; Link Function Table > telemetry=telemetry ; Telemetry descriptions > wait_times=wait-times ; Wait times > macro=macro > context = radio ; dialing context for phone > callerid = "Repeater" <0000000000> ; callerid for phone calls > idrecording = |iW9CR ; id recording or morse string > accountcode=RADIO ; account code (optional) > hangtime=3000 ; squelch tail hang time (in ms) (optional) > althangtime=6000 ; longer squelch tail > totime=180000 ; transmit time-out time (in ms) (optional) > idtime=540000 ; id interval time (in ms) (optional) > politeid=30000 ; time in milliseconds before ID timer > idtalkover=none ; Talkover ID (optional) default is none > unlinkedct=ct4 ; unlinked courtesy tone (optional) default is none > remotect=ct3 ; remote linked courtesy tone (indicates a remote is in the list of links) > linkunkeyct=ct8 ; sent when a transmission received over the link unkeys > nolocallinkct=1 ; Send unlinkedct instead if another local node is connected to this node (hosted on the same PC). > eannmode=2 ; Default: 1 = Say only node number on echolink connects > beaconing=1 ; Send ID regardless of repeater activity (Required in the UK, but probably illegal in the US) > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > [functions] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 ; disconnect all links > 72=ilink,7 ; Last Node to Key Up > 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 > 951=ilink,11 ; Permanent link disconnect > 952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > [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 > eannmode=2 ; announce callsign only > [morse] > speed=20 ; Approximate speed in WPM > frequency=300 ; Morse Telemetry Frequency > amplitude=4096 ; Morse Telemetry Amplitude > idfrequency=660 ; Morse ID Frequency > idamplitude=1024 ; Morse ID Amplitude > [wait-times] > telemwait=2000 ; Time to wait before sending most telemetry > idwait=500 ; Time to wait before starting ID > unkeywait=2000 ; Time to wait after unkey before sending CT's and link telemetry > calltermwait=2000 ; Time to wait before announcing "call terminated" > [nodes] > 40821 = radio(a)127.0.0.1/40821,NONE ; This must be changed to your node number > 902 = radio(a)127.0.0.1/902,NONE > [memory] > [macro] -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

1 0

strange courtesy tone (or I'm going insane)
by Bryan Fields 09 Feb '15

09 Feb '15

I've defined a local node (902) for testing my 902 MHz repeater. It's on PCIRADIO/1 and it's up and going on the test box. When I link it over to my node 40821, (224.28) it works come up and the repeater audio works as intended. However when using the 40821 node (ie input on 222.68) it has a courtesy tone added in only when the local node is linked. This tone is 6 fast beeps at 1800 hz (give or take what audacity says). I can't find it defined in my rpt.conf at all. I've really run out of ideas here, and think I might be going insane. I have audio of it up here http://keekles.org/~w9cr/40821%20wierd%20tone.wav Anyone have any ideas? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

2 1

local rpt access via local extension?
by Jim Cook 08 Feb '15

08 Feb '15

Sorry if this is more of an Asterisk question.... I'm deep into learning how to set up an Allstar* system. Had configure allstar//asterisk (lots of google and fumbling around) so that I could access to my node via a local extension in the shack. In the process of switching from usbradio to simpleusb my edited extensions file was overwritten. (the custom stuff is now in custom/extensions.conf and I have backup copies !) This dial plan results in a warning message from app_rpt: We only accept links via IAX2, Echolink, TheLinkBox or local !! (context from custom/extensions.conf) [in-shack] exten => 6010,1,Dial(SIP/6010,60,rT) exten => 6020,1,Dial(SIP/6020,60,rT) exten => 6099,1,Goto(radio-secure,27739,1) How do I make extension 6099 'local' to app_rpt again? I can dial between the extensions but fail with reorder/fast busy on 6099.. I know I HAD it working at 2 am the other night! Thanks in advance for any pointers on how to get this working again. Jimc -- W8NSA *standard installation from the Allstar download CD.

2 1

Suitable PC For Limey
by Wayne 08 Feb '15

08 Feb '15

I must admit that in my business all I have a 20 pound sledge hammers when a picture frame hammer would work I did come across a working Dell Celeron 2.66GHz with 512mb of RAM. I know that SDD’s are preferred but well, I don’t want to buy anything during the testing phase. So let me just ask: will a Celeron 2.66GHz work as a small test hub?

2 2

Re: [App_rpt-users] Ras Pi 2 doesn't like xenon flashes???
by mike＠midnighteng.com 08 Feb '15

08 Feb '15

While not familiar with the Pi2, I guess I have learned something. Never would have dreamed of a photo-sensitive chip outside of a eprom. Especially in the power supply area. They must use a on-chip led/photo transistor as a flip/flop toggle of the power. Opto-isolation. That would make sense. I have seen chips with just that but have not used them. A good lesson on new analog things to troubleshoot. All these micro-controllers are susceptible to digital rfi/rfp noise. Proper shielding your controller is still best practice regardless. Unless you like surprises that make you scratch your head. ...mike/kb8jnm > > Hi Mike & Everyone, > > My initial questions (and alarm) were if the RPi2 might be excessively > sensitive to external EMI---something like that can be really hard to deal > with around high RF environments. > > But, after reading more threads, it appears this issue is truly light > sensitivity in one of the switching PS chips (U16), due to how it's > encapsulated (or lack thereof!) in plastic. Adding a small light shield > apparently fixes this issue, based on what other testers say. > > I don't yet have a RPi2, so I can't test. > > > 73, David KB4FXC > > > > On Sun, 8 Feb 2015 mike(a)midnighteng.com wrote: > >> >> Not having tested it specifically, I would find it plausible for a xenon >> flash in very close proximity to a micro-controller create a problem but >> only in this way... >> >> RFI/EMP burst during flash, a pulse being picked-up on circuits. If not >> RFI changing something directly in ram, EMP could just put a extra >> binary >> digit in a stream of data or a extra pulse in the clock line. The later >> in >> the clock line being most probable for a lock-up. Not from the flash of >> light. The broad pulse comes from it's ballast. The wires attached to it >> and the bulb act as a antenna. >> >> If it is a problem with a strobe light, I'll bet you could get a similar >> action from a close proximity GSM cell phone during certain phone >> actions. >> And I would also bet you could find that the Pi would not be the only >> type >> of micro-controller than can be affected by this type of thing. >> >> Not to worry, Shield your Pi like you should be doing in any case and >> provide sinks for RFI on all lines in and out of the shielded area. This >> would be normal protection in a RF hostile environment. Radio 101 - It >> should never be a real issue in a properly constructed repeater. >> >> ...mike/kb8jnm >> >> > >> > >> > Hi Everyone, >> > >> > I just saw this thread in another newsgroup. Basically, they're saying >> the >> > Pi2 will hang/crash if subjected to a close xenon camera flash >> discharge! >> > >> > Weird! Can anyone confirm if this is true? ...If they're sensitive to >> a >> > flash, they might be sensitive to RF as well. Perhaps an EMP issue? >> > >> > Here is a link to the thread: >> > http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=99042 >> > >> > Again, I have NOT personally confirmed this report, but am sitting >> here >> > looking puzzled! >> > >> > >> > 73, David KB4FXC >> > >> > >> > _______________________________________________ >> > 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] Ras Pi 2 doesn't like xenon flashes???
by mike＠midnighteng.com 08 Feb '15

08 Feb '15

Not having tested it specifically, I would find it plausible for a xenon flash in very close proximity to a micro-controller create a problem but only in this way... RFI/EMP burst during flash, a pulse being picked-up on circuits. If not RFI changing something directly in ram, EMP could just put a extra binary digit in a stream of data or a extra pulse in the clock line. The later in the clock line being most probable for a lock-up. Not from the flash of light. The broad pulse comes from it's ballast. The wires attached to it and the bulb act as a antenna. If it is a problem with a strobe light, I'll bet you could get a similar action from a close proximity GSM cell phone during certain phone actions. And I would also bet you could find that the Pi would not be the only type of micro-controller than can be affected by this type of thing. Not to worry, Shield your Pi like you should be doing in any case and provide sinks for RFI on all lines in and out of the shielded area. This would be normal protection in a RF hostile environment. Radio 101 - It should never be a real issue in a properly constructed repeater. ...mike/kb8jnm > > > Hi Everyone, > > I just saw this thread in another newsgroup. Basically, they're saying the > Pi2 will hang/crash if subjected to a close xenon camera flash discharge! > > Weird! Can anyone confirm if this is true? ...If they're sensitive to a > flash, they might be sensitive to RF as well. Perhaps an EMP issue? > > Here is a link to the thread: > http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=99042 > > Again, I have NOT personally confirmed this report, but am sitting here > looking puzzled! > > > 73, David KB4FXC > > > _______________________________________________ > 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 2