March 2014 - App_rpt-users - lists.keekles.org

Motorola GM1200
by James Hill 07 Mar '14

07 Mar '14

Hi Guys, Is anybody using a Moto GM1200? I've just bought one, with the intention of using it with simpleusb and parport PTT and COR. Has anyone any information as to the pinouts? I've seen plenty of information regarding programming cables, but not much on hooking up to Echolink/Allstar. Thanks, James 29681 --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

2 1

Re: [App_rpt-users] incoming allstar connections fail
by Doug Crompton 07 Mar '14

07 Mar '14

I tried connecting to you on web transceiver here and it connects but I cannot key. I can disconnect and connect but thats about it. I am not a big fan of web transceiver. I use iaxrpt. If you have a server that is the way to go. You can set it up in windows and access your nodes from anywhere. If you need help setting it up let me know. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Thu, 6 Mar 2014 21:25:12 -0500 From: kb1ncj(a)gmail.com To: doug(a)crompton.com Subject: Re: [App_rpt-users] incoming allstar connections fail Oh and telephone portal connects are working.. so it is puzzling. On 03/06/2014 12:43 PM, Doug Crompton wrote: Do you have the web transceiver access enabled on your node access settings at allstarlink.org? Can others connect to you allstar node to node? What is your node number? 73 Doug WA3DSP http://www.crompton.com/hamradio > Date: Thu, 6 Mar 2014 12:28:12 -0500 > From: kb1ncj(a)gmail.com > To: app_rpt-users(a)ohnosec.org > Subject: [App_rpt-users] incoming allstar connections fail > > I can't figure out why.. I have port 4569 forwarded and echolink works > fine with it's needed ports forwarded. I am trying to test using the web > transceiver. A friend of mine can't connect to my node from his Allstar > node either. Am I blocked from my own node using the web transceiver? > Thanks for any help.. > Greg > _______________________________________________ > 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

XIPAR Allstar Password where is it stored?
by Joe Bennett 07 Mar '14

07 Mar '14

Keep getting connection refused for our node... Looked in iax_rpt_custom.conf and set 'secret' to our password... Then did an amportal restart... What else needs to be done? -Joe KA3NAM

1 0

Re: [App_rpt-users] USB FOB options
by Steve Wright 07 Mar '14

07 Mar '14

Okies, so these USB FOBs have a blob of hard (epoxy?) goop on the chip so I can't get at the pins. BUT, the device has two LEDs and four switches that go direct to the chip. Why do we need any more I/O than that? Do I even need access to the pins? I should be able to take PTT off one of the LEDs, and put COR onto one of the switches. Why not? Soldering to pins is the hard way, and lots of devices are potted. Steve -- Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers +64 21 040 5067

3 2

incoming allstar connections fail
by Greg 06 Mar '14

06 Mar '14

I can't figure out why.. I have port 4569 forwarded and echolink works fine with it's needed ports forwarded. I am trying to test using the web transceiver. A friend of mine can't connect to my node from his Allstar node either. Am I blocked from my own node using the web transceiver? Thanks for any help.. Greg

2 1

USB URIx overmodulation problem?
by Kevin Oleniczak 06 Mar '14

06 Mar '14

I'm using a URIx module with my radio and am in the process of adjusting audio levels. I'm following the well documented procedures to set rx and tx levels but noticed that that choices in txvoice levels have little or no effect. I've made some measurements with my service monitor. radio tune txvoice 10 >> 0.35Khz deviation radio tune txvoice 14 >> 4.8Khz deviation radio tune txvoice 15 >> 4.8Khz deviation radio tune txvoice 20 >> 5.2Khz deviation radio tune txvoice 100 >> 5.2Khz deviation radio tune txvoice 500 >> 5.2Khz deviation radio tune txvoice 900 >> 5.2Khz deviation With a goal of 3KHz deviation, its not possible through settings alone. Any ideas why this is so touchy? thanks

6 6

Re: [App_rpt-users] IP-connected mountain-top toys
by mike＠midnighteng.com 06 Mar '14

06 Mar '14

1 0

IP-connected mountain-top toys
by Steve Wright 06 Mar '14

06 Mar '14

Greetings, Anyone playing with any outdoor IP-connected ham radio toys other than Asterisk? I have a little bit of Ubiquiti AirMAX which is good fun, and looking at doing some remote SDR. What else? Steve -- Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers +64 21 040 5067

1 0

Allstar connecting to Echolink Problem
by Kent Ochs 06 Mar '14

06 Mar '14

I too have been experiencing some inbound connection problems with Echolink. This only effects certain Echolink users but not others user, who at the same time are able to connect without problem. After restarting our system, the problem does go away I had a chance the other night to do some troubleshooting with a user who was having trouble connecting to our system. Running the Asterisk remote console, I saw his connection attempt and failure. The attempted Echolink connection lookup was by his IP address. 1. I confirmed that his IP address was valid. 2. I confirmed that his Callsign/IP was not in the local Allstar Echolink database. What was interesting was I could not lookup his Callsign on the Echolink Database Server either, but he was able to connect directly to my personal computer, so he was authenticated somehow to the Echolink system. 3. After 5 minutes he did show up in the Echolink database I was looking at (Shown at the top of the Echolink database lookup screen as nawest.echolink.org) 4. After a server restart he was able to connect my Allstar Node. What I did notice was that there is a naeast.echolink.org database server that is not in my server list. Here is what I think is happening. 1. I'm not sure which database the sync runs against. (First one in the server list?) 2. If a call/ip can not be authenticated local, then a separate lookup occurs against each server in the Server List. 3. If the user has authenticated to an Echolink server not in the Server List (like naeast.echolink.org) this individual Echolink database lookup process will also fail. It appears the sync process between Echolink database server is a little longer than the stated 20 seconds stated by the Echolink folks. So, if a user connects to an Echolink server, other than one in your server list. There may be a significant delay from the time the user shows up in the Echolink database and is finally downloaded to the local copy on the Allstar server. I have added naeast.echolink.org to the list of recommended database servers in the Servers list and I am waiting to see if this solves the problem. (Is Echolink load balancing first to nawest and naeast? Are they having sync delays and/or problems?) Then again perhaps there is something wrong with the local Echolink database sync process that restarting the server fixes. I sure would like to know what Echolink database server the sync process connects to by default. Kent W9KAO 1. Re: Allstar connecting to Echolink? (Kevin Oleniczak) 2. Re: Re :__Problems_with_Echolink (torben(a)klimt-online.com) Thanks to those that responded... i had waited several hours/days without the node appearing active and do not have a second client running simultaneously within my network. The later responses indicated the search for my node failed to find a match, but that was because the wrong callsign was used. See below. cruiser*CLI> echolink dbget c N9JPG-L 960818|N9JPG-L|71.194.253.53 >> Below that is my echolink.conf file for reference. Note the servers listed - 1,5,3. I used these in my conf file as it noticed that was what my echolink client was using. server1=nawest.echolink.org server2=nasouth.echolink.org server3=servers.echolink.org >>Make sure you point the echolink ports in your router to your allstar server and as was mentioned you can only run one echolink node per public IP address. As noted earlier, that is all set as suggested on the howto page for allstar to do echolink. Any other ideas?

3 4

Re: [App_rpt-users] App_rpt-users Digest, Vol 61, Issue 12
by Steve Wright 05 Mar '14

05 Mar '14

> > Does anyone have any idea why I need to "double-boot" to successfully > register with the hub? > Even the wackiest of ideas will be appreciated! Maybe you have a firewall part-way up while asterisk is trying to make an outgoing connect request? What happens if you just restart asterisk, and not reboot the whole machine? Try adding a second register attempt in your confs? Steve

1 0