Hi Lu, Okay, you are correct, it appears you're not registered for some reason. The next step is to take a look at the asterisk logfiles to see if they hold any answers as to what's wrong. So, login to the Asterisk/app_rpt server and from the command prompt issue this command: grep chan_iax2 /var/log/asterisk/messages | tail -100 This should print out the last 100 lines of log entries related to the chan_iax2 channel driver. This info should explain what's wrong with registrations. Please give this a try and report back. Note that your AllStar password may be included in this printout, so, use caution before just cutting-and-pasting into a reply e-mail. Happy Holidays! 73, David KB4FXC On Wed, 4 Dec 2013, Lu Vencl wrote:
Well I tried the recommended command: wget -O - http://nodes1.allstarlink.org/cgi-bin/nodes.pl and here are my results. [root@Node27976_WoodlandPark00256483dba8 ~]# wget -O - http://nodes1.allstarlink.org/cgi-bin/nodes.pl --2013-12-04 21:50:01-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl Resolving nodes1.allstarlink.org... 96.36.57.202 Connecting to nodes1.allstarlink.org|96.36.57.202|:80... connected. HTTP request sent, awaiting response... 403 2013-12-04 21:50:06 ERROR 403: (no description).
So you are correct, I am not registered, but the next question is why? My IP address only changes when I reboot the router or after about 3 weeks when the DHCP expires. This just suddenly started just a few days ago, so I am at a loss. I am open to suggestions at this point.. Thanks KA4EPS
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of David McGough Sent: Wednesday, December 04, 2013 1:16 PM To: Andrew Sylthe Cc: app_rpt-users@ohnosec.org; Benjamin L. Naber Subject: Re: [App_rpt-users] Registration server down?
Guys,
I don't think anything is broken with the registration server(s)--I just checked the logs at my repeater site and everything seems fine.
You must have a *stable* Internet connection to maintain registration. And, realistically, in my experience, a static IP address will improve your results significantly.
Once your system has registered, you can perform a test from the command prompt of your ACID server to get the latest node list. That command is:
wget -O - http://nodes1.allstarlink.org/cgi-bin/nodes.pl
If this command fails with a 500 error (or 403 error), you're not registered properly. This could mean that your IP address has changed since your last registration.
I hope this helps-
73, David KB4FXC
On Wed, 4 Dec 2013, Andrew Sylthe wrote:
I personally have noticed my IAX registration failing to 67.175.236.94 (AllStar) periodically throughout the day (and the past few days for that matter). I have other IAX and SIP registrations that are not experiencing the same loss of registration. I don't believe it to be a problem with my internet connection. I will say that I haven't done a tcpdump, but am willing to if someone needs more diagnostic information from my endpoint.
On Wed, Dec 4, 2013 at 11:55 AM, Benjamin L. Naber <Benjamin@kb9lfz.com>wrote:
there have been an increasing number of reports in which folks are having troubles with connecting to other nodes.
It's apparent to me that until Master Daddy has an issue, nothing will be done about it.
On Wed, 2013-12-04 at 12:42 -0500, Lu Vencl wrote:
Any chance the registration server is down? For some reason, my node in CO is unable to connect to anyone and it does not show up in the database.
Example: http://stats.allstarlink.org/nodeinfo.cgi?node=27976
Node 27976
Node 27976 is no longer in the database
But if I try to connect to other nodes, I do seem to attempt to make connections ok, but they fail.
Last login: Wed Dec 4 12:08:53 2013 from 166.205.50.234
Installed and Running Server Packages:
XIPAR - http://www.xelatec.com/xipar
Asterisk - http://www.asterisk.org
FreePBX - http://www.freepbx.org
IP Address = 192.168.0.2
MAC Address = 00:25:64:83:DB:A8
[root@Node27976_WoodlandPark00256483dba8 ~]# ping register.allstarlink.org
PING register.allstarlink.org (67.215.233.178) 56(84) bytes of data.
64 bytes from register.allstarlink.org (67.215.233.178): icmp_seq=1 ttl=56 time=66.4 ms
64 bytes from register.allstarlink.org (67.215.233.178): icmp_seq=2 ttl=56 time=65.5 ms
64 bytes from register.allstarlink.org (67.215.233.178): icmp_seq=3 ttl=56 time=66.5 ms
64 bytes from register.allstarlink.org (67.215.233.178): icmp_seq=4 ttl=56 time=66.3 ms
64 bytes from register.allstarlink.org (67.215.233.178): icmp_seq=5 ttl=56 time=66.0 ms
64 bytes from register.allstarlink.org (67.215.233.178): icmp_seq=6 ttl=56 time=65.7 ms
^C
--- register.allstarlink.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5790ms
rtt min/avg/max/mdev = 65.594/66.129/66.577/0.383 ms
[root@Node27976_WoodlandPark00256483dba8 ~]# ^C
[root@Node27976_WoodlandPark00256483dba8 ~]# asterisk -r
Asterisk 1.4.28, Copyright (C) 1999 - 2009 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
================================================================== =======
Connected to Asterisk 1.4.28 currently running on Node27976_WoodlandPark00256483dba8 (pid = 1631)
Verbosity is at least 99256483dba8*CLI>
Node27976_WoodlandPark00256483dba8*CLI> core set verbose 99
Verbosity is at least 99256483dba8*CLI>
Node27976_WoodlandPark00256483dba8*CLI> rpt fun 27976 *327892
== Parsing '/var/lib/asterisk/rpt_extnodes': Found
== Parsing '/var/lib/asterisk/rpt_extnodes': Found
== Parsing '/var/lib/asterisk/rpt_extnodes': Found
== Parsing '/var/lib/asterisk/rpt_extnodes': Found
== Parsing '/var/lib/asterisk/rpt_extnodes': Found
== Parsing '/var/lib/asterisk/rpt_extnodes': Found
-- Call accepted by 99.45.143.74 (format ulaw)
-- Format for call is ulaw
-- Hungup 'IAX2/99.45.143.74:4569-777'
-- Hungup 'DAHDI/pseudo-1878106708'
-- Hungup 'DAHDI/pseudo-1462231487'
-- <DAHDI/pseudo-2063202499> Playing 'rpt/nodenames/27892' (language 'en')
-- <DAHDI/pseudo-2063202499> Playing 'rpt/connection_failed' (language 'en')
-- Hungup 'DAHDI/pseudo-2063202499'
Node27976_WoodlandPark00256483dba8*CLI>
I think one time this happened to me before and it ended up being the registration server.. Any ideas? Any commands I could try to see the process flow of registration?
Lu
KA4EPS
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users