February 2015 - App_rpt-users - lists.keekles.org

Hit and run
by Robert Newberry 10 Feb '15

10 Feb '15

I know this may be kinda off topic. It really grinds my gears when you get people who log into my node throw their call and disconnect less than a minute later. I run zello on my node which records all traffic. It is also nice because I can monitor my nodes 24/7 with ease. How the hell can I engage someone in a QSO if I can't answer them in less than a minute? It's funny the few people I have caught we had some nice QSOs. One of them I've remanded friends with. It just makes me laugh people must think my nodes are dead but they get fair use and I guess I need to train to answer a user in less than a minute.

7 13

12V to 5V DC-DC Converters?
by James Lyles 10 Feb '15

10 Feb '15

I have one of these on order, I'll run some tests when it actually arrives. http://www.ebay.com/itm/310847327341?_trksid=p2059210.m2749.l2649&ssPageNam…

1 0

re Zello on Allstar
by Jon Rorke 10 Feb '15

10 Feb '15

How do you install Zello on an Allstar node? Can you use it like iax_rpt or zoiper? Do tell. Jon VA3RQ > I run zello on my node which records all traffic. It is also nice > because I can monitor my nodes 24/7 with ease.

3 3

Re: [App_rpt-users] wtf? a ranger node? (was strange courtesy tone)
by Bryan Fields 10 Feb '15

10 Feb '15

On 2/10/15 9:47 AM, Bryan D. Boyle wrote: > jum and i wrote an nprm to establish a single freq on non interference basis, > League lobbied against it, fcc shot it down :( I just can't stand the politics of this stuff some times. -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

2 1

Re: [App_rpt-users] wtf? a ranger node? (was strange courtesy tone)
by Bryan Fields 10 Feb '15

10 Feb '15

On 2/9/15, 1:39 AM, Bryan Fields wrote: > 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.... I read the source to app_rpt.c and found that nodes starting with a 9 are called a ranger node. No idea what this is. Can anyone elaborate? > #define ISRANGER(name) (name[0] == '9') > /* if has a RANGER node connected to it, use special telemetry for RANGER mode */ > if (haslink) > { > res = telem_lookup(myrpt,mychannel, myrpt->name, "ranger"); > if(res) > ast_log(LOG_WARNING, "telem_lookup:ranger failed on %s\n", mychannel->name); > } looks like a ranger node is suppose to listen for a LiTZ and then connect to another node. When others are using that other node as along as the ranger node is connected to it it will send the "ranger" CT which is what I'm hearing. > {"ranger","|t(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,150,0)"} Good news is my 1800 hz decode from audacity was correct! So I'm guessing this is meant to be some kinda half duplex node that links in for emergency use. Anyone have any idea on this? I can't find anything on the docs site about ranger nodes. If I make the node in the 1902 the problem goes away, or I could define the "ranger" CT to be nothing. 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

3 2

Incoming Echolink connection doesn`t work
by Torben Klimt 10 Feb '15

10 Feb '15

hi all, from one day to another it is not possible to connect my node by echolink. outgoing connectens work well but if i want to connect from external i get following message any ideas ? -- Executing [28535@radio-secure:1] Rpt("echolink/el0-28", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-28' -- Hungup 'Zap/pseudo-213277950' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-29", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-29' -- Hungup 'Zap/pseudo-1746953366' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-30", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-30' -- Hungup 'Zap/pseudo-1705317437' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-31", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-31' -- Hungup 'Zap/pseudo-1525394495' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-32", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-32' -- Hungup 'Zap/pseudo-1076156582' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-33", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-33' -- Hungup 'Zap/pseudo-82187291' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-34", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-34' -- Hungup 'Zap/pseudo-76728912' -- Executing [28535@radio-secure:1] Rpt("echolink/el0-35", "28535") in new stack == Spawn extension (radio-secure, 28535, 1) exited KEEPALIVE on 'echolink/el0-35' -- Hungup 'Zap/pseudo-62045735' greetings

2 3

2 nodes setup to auto connect don't seem to work
by Mike Lussier 10 Feb '15

10 Feb '15

Good afternoon all, I have two nodes on my internal network. both on the same subnet. for the past 16 hours if I look at either node that show state as "Connecting" and not connected . Any thoughts ? I tried it once from one node running a script and before I went to bed last night I tried it from the other side. Mike AE4ML -- *"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*

5 9

XIPAR
by Luc Drolet VE2 LUQ 09 Feb '15

09 Feb '15

Hello to you all, I want to install a Xipar on a computer, 3 times and I still can have an error message "Unable to retrive http://mirroir.anl.gov/pub/centros/6/os/i386/images/install. img " I even burn another cd d`installation I think it's the XIPAR server, when do you think? Thank you and Happy Day 73`s Luc VE2LUQ

2 2

Multiple servers and local connections
by Doug Crompton 09 Feb '15

09 Feb '15

I decided to write something up on this since so many more people are putting multiple servers on LAN's and I get these questions all the time. This is a first cut so let me know if anything needs correction or clarification. I will be putting it out as a howto on the hamvoip site. Considerations when using more than one Allstar server on a LAN When you have more than one server on the same private LAN and you want to connect them locally or connect into them from the outside there are some special considerations. Allstar uses a database that is constantly updated with the public IP addresses and ports of all other active nodes on the network including your own. So if you have two (or more) local nodes on different computers and they try to connect to each other they will not be able to. Most routers do not know how to handle their own public IP from within the LAN, so you have to enter the local IP address and port information in the nodes section of each servers rpt.conf file. Here is an example of how to do it: First you need to go to allstarlink.org and put each server on a different port. The default iax port is 4569 and when you define a server that is what is assigned. If you have two servers you need to pick one and change the port, say to 4568. You do this in the network tab of the server configuration at allstarlink.org. Only change the port, do not change or add any IP addresses. If you have more than two servers just keep assigning new port numbers for each. Locally the servers port is assigned in /etc/asterisk/iax.conf - [general] bindport=4569 <<<< change this to the same port that you assigned for this server at allstarlink.org Do this for each server. Then you need to add entries in /etc/asterisk/rpt.conf. Here is an example for two servers: If you had two nodes, each on a different server and server1 with node 40000 had an IP address of 192.168.1.101 and port of 4569 and server2 with node 40001 had an IP address of 192.168.0.100 with a port of 4568 then you would put the following in nodes section of your rpt.conf file: [nodes] ; Note, if you are using automatic update for allstar link nodes, ; no allstar link nodes should be defined here. Only place a definition ; for your local nodes, and private (off of allstar link) nodes here. 40000 = radio(a)127.0.0.1/40000,NONE 40001 = radio@192.168.1.100:4568/40001,NONE <<<< IP and port of other local server On the other server it would be just reversed with the other nodes IP address and port. 4569 is default and would not need to be entered but shown here for clarity. [nodes] ; Note, if you are using automatic update for allstar link nodes, ; no allstar link nodes should be defined here. Only place a definition ; for your local nodes, and private (off of allstar link) nodes here. 40001 = radio(a)127.0.0.1/40001,NONE 40000 = radio@192.168.1.101:4569/40000,NONE <<<< IP and port of other local server In addition to doing this if you want outside connectibility to your nodes you need to open ports in your router. In this example you would add port 4569 udp to IP address 192.168.0.101 and another entry for port 4568 udp to IP address 192.168.0.100 Also if you want outside ssh access there are two things you can do. If you want direct public ssh access to both servers then you would need to change one servers ssh port since they would both be on port 222. You do this in /etc/ssh/sshd_config on the BBB or in /etc/sshd_config on Centos. Change the port number and remember what it is as you will have to use this port to log into this server in the future. One could stay at 222 and the other might be 223. You would then add both entries to your routers port forwarding. If server1 was port 222 and server2 was 223 then add port 222 tcp 192.168.0.101 and port 223 tcp 192.168.0.100 entries to your router. Another option would be to leave them both at port 222 and then you can log into which ever one is port forwarded. You would only forward one server in your router. Lets say port 222 was routed to 192.168.0.101, server1. When you ssh from the outside to your public IP address at port 222 it would go to that server. But you really want to get to server2. So once you log into server1 you simply type - ssh root(a)192.168.0.100 -p 222 - Now you get the server2 login, enter your password and you are connected there. If you only want LAN ssh access not public then you can just connect by local IP address. No port change and no router entries are necessary. If you are using lsnodes or Allmon and you want public access to multiple servers behind a LAN you will need to change the web server ports on the 2nd and subsequent servers and forward them appropriately in your router. The default is port 80 but this could be changed to some more obscure series of ports of your choosing. Again if you just want local access no changes are necessary, just use the servers local IP address. Always restart Asterisk whenever you make these changes. 73 Doug WA3DSP http://www.crompton.com/hamradio

1 0

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