October 2009 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Node not registering
by hwstar＠rodgers.sdcoxmail.com 31 Oct '09

31 Oct '09

> > From: Doug Bade <kd8b(a)thebades.net> > Date: 2009/10/29 Thu PM 01:53:55 PDT > To: app_rpt mailing list <app_rpt-users(a)qrvc.com> > Subject: Re: [App_rpt-users] Node not registering > > > >> > > >> > Do I need a hole in the firewall for the registry??? I have one > >> for SIP.. 4569 > >> > > >> > > >> > from my iax.conf file > >> > > >> > register=A2235:xxxxxx@register.allstarlink.org > >> > where xxxxxx = my password.... > >> > > >> > from my rpt.conf file > >> > > >> > > >> statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > >> > >> > > >> > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > >> > > >> > is uncommented.... > >> > > >> > I am not seeing what is wrong.. > >> > > >> > Help ?? > >> > > >> > Doug > >> > KD8B > >> > > > > > >>There should be a be a forward statement for port 4569 in your > >>firewall directing the external port 4569 on your public IP to an > >>internal private IP hosting the node. > >> > >>Just to make sure your router is not playing games with source port > >>numbers, I forced registration for node 2235 to always user port 4569. > >> > >>FYI: Although not needed for ACID, SIP should be port 5060 plus udp > >>ports 10000-20000 > >> > >>Steve > >>WA6ZFT > >> > >>Steve; > > Steve and List; > > > I did already open up a port forward on 4569 for UDP......... I am > suspecting maybe TCP too????? > > I will open the others too.... > > Doug > KD8B > > > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)qrvc.com > http://qrvc.com/mailman/listinfo/app_rpt-users > The udp protocol on port 4569 is all that should be required. Recheck the internal port forwarding in the router, and you might want to see what registration messages(errors) are being printed on the asterisk cli. Steve WA6ZFT

3 4

Re: [App_rpt-users] Node not registering
by Doug Bade 29 Oct '09

29 Oct '09

>> > >> > Do I need a hole in the firewall for the registry??? I have one >> for SIP.. 4569 >> > >> > >> > from my iax.conf file >> > >> > register=A2235:xxxxxx@register.allstarlink.org >> > where xxxxxx = my password.... >> > >> > from my rpt.conf file >> > >> > >> statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null >> >> > >> > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates >> > >> > is uncommented.... >> > >> > I am not seeing what is wrong.. >> > >> > Help ?? >> > >> > Doug >> > KD8B >> > >>There should be a be a forward statement for port 4569 in your >>firewall directing the external port 4569 on your public IP to an >>internal private IP hosting the node. >> >>Just to make sure your router is not playing games with source port >>numbers, I forced registration for node 2235 to always user port 4569. >> >>FYI: Although not needed for ACID, SIP should be port 5060 plus udp >>ports 10000-20000 >> >>Steve >>WA6ZFT >> >>Steve; Steve and List; I did already open up a port forward on 4569 for UDP......... I am suspecting maybe TCP too????? I will open the others too.... Doug KD8B

1 0

Node not registering
by Doug Bade 29 Oct '09

29 Oct '09

I finally have my repeater on site and running and connected through a Untangle firewall and am not getting my node to show as being received on the node list. I can ping the registry domain ( allstarlink.org) so basic connectivity seems ok... and I have what appears to be the correct line un commented and what looks to be properly formatted but no update....I must be missing something... Do I need a hole in the firewall for the registry??? I have one for SIP.. 4569 from my iax.conf file register=A2235:xxxxxx@register.allstarlink.org where xxxxxx = my password.... from my rpt.conf file statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates is uncommented.... I am not seeing what is wrong.. Help ?? Doug KD8B

2 2

Re: [App_rpt-users] Node not registering
by hwstar＠rodgers.sdcoxmail.com 29 Oct '09

29 Oct '09

> > From: Doug Bade <kd8b(a)thebades.net> > Date: 2009/10/29 Thu AM 11:49:31 PDT > To: app_rpt mailing list <app_rpt-users(a)qrvc.com> > Subject: [App_rpt-users] Node not registering > > I finally have my repeater on site and running and connected through > a Untangle firewall and am not getting my node to show as being > received on the node list. I can ping the registry domain ( > allstarlink.org) so basic connectivity seems ok... and I have what > appears to be the correct line un commented and what looks to be > properly formatted but no update....I must be missing something... > > Do I need a hole in the firewall for the registry??? I have one for SIP.. 4569 > > > from my iax.conf file > > register=A2235:xxxxxx@register.allstarlink.org > where xxxxxx = my password.... > > from my rpt.conf file > > statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > is uncommented.... > > I am not seeing what is wrong.. > > Help ?? > > Doug > KD8B > There should be a be a forward statement for port 4569 in your firewall directing the external port 4569 on your public IP to an internal private IP hosting the node. Just to make sure your router is not playing games with source port numbers, I forced registration for node 2235 to always user port 4569. FYI: Although not needed for ACID, SIP should be port 5060 plus udp ports 10000-20000 Steve WA6ZFT _______________________________________________ App_rpt-users mailing list App_rpt-users(a)qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users

1 0

New low power mini-ATX from INtel
by Vaidotas 28 Oct '09

28 Oct '09

Just find new Intel low power motherboard D945GSEJT with Atom (idle 12,28 W with chipsets). Plus on board simple 12V connector, SODIMM RAM, ... ****************** Vaidotas Dilys Vilnius Lithuania ******************

1 0

Autopatch
by Frank Herzog 28 Oct '09

28 Oct '09

Hi, sometimes we get a busy-tone on the clients listening with rpt() to a radio channel. I wonder, if this is the result of app_rpt trying to do an autopatch. Is there the possibility to completely deactivate the autopatch feature? Thanks for your support, Frank **************************************** Dr.-Ing. Frank Herzog mailto:frank.herzog@dhp-gmbh.de PGP Fingerprint: D3EE B4D5 544C 7309 9D36 DFAD 5B6D C145 1409 E855 Tel: +49-241-990000-21 Fax: +49-241-990000-91 DOHMEN, HERZOG & Partner GmbH Soerser Weg 9 52070 Aachen Gesch?ftsf?hrende Gesellschafter Dr.-Ing. Marc Dohmen Dr.-Ing. Frank Herzog Amtsgericht Aachen HRB 5931 St.-Nr.: 201/5953/3633 USt-IdNr.: DE164205623 **************************************** Diese Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e- mail is strictly forbidden.

1 0

Slightly OT: Help with IAX2 protocol/NAT
by Stephen - K1LNX 28 Oct '09

28 Oct '09

I have a problem that I need help with, and google is not being very useful at the moment (or I'm feeding it the wrong query, which is probably the case). I have two Asterisk boxes, both sitting behind a single NAT'ed public IP address. I have IAX2 traffic from Allstar pointing to the app_rpt box, and SIP traffic pointing to the other box which is acting as my home phone system. I keep both systems separate for various reasons, so running this all on one installation was not an option, hence the two separate boxes :) I want to take advantage of the IAX2 protocol for the box running my home phone system outside of my LAN, but the problem is as I only have a single IP address UDP port 4569 is already pointing to the app_rpt box. I have been shifting a few ideas around in my head, none of which I think will be easy to implement, or even guaranteed to work with my desired results. It's entirely possible that I may be trying to re-invent the wheel, but as I know there is much talent on this list concerning Asterisk maybe someone already has a solution for this :D Please reply to me off-list if you can/are willing to offer me some help or maybe even a clue ;) 73 and tnx Stephen K1LNX -- ********************************** Stephen Brown - ARS K1LNX Johnson City, TN EM86 http://www.k1lnx.net google voice: 423-665-9367 **********************************

2 2

Green is good
by Stephen Rodgers 28 Oct '09

28 Oct '09

I added a feature to the node list command on allstarlink.org. If your node number has a green background, it means that the register statement in iax.conf is registering properly with register.allstarlink.org, and that you can most likely connect to other nodes and accept connections from other nodes without a problem. If it is a grey background it means you are not registering, and you should resolve it by putting the something like this in your iax.conf file: register=Anode:password@register.allstarlink.org where: node is your assigned Allstar link node number. password is your assigned Allstar Link access password. For example, node 1234 which has a password of 12345678 would put the following line in [general] section /etc/asterisk/iax.conf: [general] . . . register=A1234:12345678@register.allstarlink.org. Note: You will need to issue an iax2 reload command from the Asterisk Command line, or restart Asterisk after you save iax.conf. Please note that registering is a very different mechanism than posting status using the statpost in rpt.conf. Registering is what enables your node to connect to other nodes, and enables your node to validate an incoming connection. If you are set up for a static IP (very early Allstarlink users only), then you should start registering anyway as we want to get everybody to be using registration. If you have a static IP registration on allstarlink.org, once you start registering, please let either Jim or I know so that we can convert your node to the register method. Steve WA6ZFT

1 0

IRlp not connecting after upgrade
by RED BUTTON MOBILE 27 Oct '09

27 Oct '09

Hi all I recently did a fresh reload using latest Acid and rebuilt my node 2249. I also reinstalled my chan irlp node from backup file. The asterisk is working but I cant connect using chanIrlp any mode. I get a connection fail. It was working before I did the reinstall of the whole package. Any ideas? Jon VA3RQ

1 0

irlp_chan users please note...
by Randy Hammock 26 Oct '09

26 Oct '09

Please note, Dave Cameron VE7LTD is preparing to purge the IRLP node PGP key list of nodes that have not recently reported to the IRLP IP server. He is making an adjustment to his procedure to see which node are also reporting to the status servers. To make sure your irlp_chan node remains on the PGP key list first you must become the user: repeater. Then run the following command: rm -f $LOCAL/last_ip_address Then you should run: $SCRIPTS/ipupdate Under normal IRLP operation a file update downloads a "temporary" version of ipupdate which has the previous command to delete the $LOCAL/last_ip_address file which will force the ipupdate script to contact the IRLP IP server. You can check if your node is on the HAS NOT REPORTED LIST by going to the following URL: http://server2.irlp.net/hosts/noupdate_list If your node is on the list, then above procedure should get you off the list. -- Randy Hammock KC6HUR http://kc6hur.net IRLP 4494 / ALLSTAR 2035 http://irlp.kc6hur.net

1 0