David, Thanks for the reply. The mystery has been solved. My friend W4BGH and I experimented a while back with Zoiper soft phones and IAX connections. I had since changed some of the iax.conf settings, but that Zoiper soft phone was trying to maintain a connection. That has been fixed. So the learning curve continues! You are right on target with the problem. 73, Ron Morell KA7U On 12/23/2011 10:19 AM, David KE6UPI wrote:

Well looking up the IP address its from Verizon FIOS. Could it be from anther IAXagent? Are you in the city of Valrico??

General IP Information

IP: 96.254.195.117 Decimal: 1627308917 Hostname: pool-96-254-195-117.tampfl.fios.verizon.net <http://pool-96-254-195-117.tampfl.fios.verizon.net> ISP: Verizon Internet Services Organization: Verizon Internet Services Services: None detected Type: Broadband <http://whatismyipaddress.com/broadband> Assignment: Static IP <http://whatismyipaddress.com/dynamic-static>

Geolocation Information

Country: United States us flag State/Region: Florida City: Valrico Latitude: 27.9158 Longitude: -82.229 Area Code: 813 Postal Code: 33596

David

On Fri, Dec 23, 2011 at 8:36 AM, Ron Morell <ron@morell.us <mailto:ron@morell.us>> wrote:

I have a mystery connection attempt going on. I don't know if it is bouncing back because of a connection attempt from my node or if it is from another device trying to call into the node. It looks like this:

test*CLI> [Dec 23 09:08:37] NOTICE[29328]: chan_iax2.c:6839 register_verify: No registration for peer 'ka7u' (from 96.254.195.117)

Tried to figure out where it comes from, but end up with Verizon, which covers a lot. I have my cell phone turned off, just in case IaxAgent on my phone was running in the background and was somehow trying to call in. So that device is out of the loop. Just for knowing IaxAgent on the cell phone is using this IP currently: 174.253.181.123, and calls in just fine.

[root@test asterisk]# traceroute 96.254.195.117 traceroute to 96.254.195.117 (96.254.195.117), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 0.737 ms 1.175 ms 1.400 ms 2 boid-dsl-gw03-195.boid.qwest.net <http://boid-dsl-gw03-195.boid.qwest.net> (184.99.64.195) 53.113 ms 53.921 ms 54.598 ms 3 184-99-65-17.boid.qwest.net <http://184-99-65-17.boid.qwest.net> (184.99.65.17) 55.379 ms 56.067 ms 57.184 ms 4 sjp-brdr-03.inet.qwest.net <http://sjp-brdr-03.inet.qwest.net> (67.14.34.10) 90.062 ms 90.844 ms 92.233 ms 5 63.146.27.230 (63.146.27.230) 92.767 ms 97.868 ms 98.521 ms 6 0.ge-2-1-0.SJC01-BB-RTR2.verizon-gni.net <http://0.ge-2-1-0.SJC01-BB-RTR2.verizon-gni.net> (152.63.2.62) 84.364 ms 79.095 ms 80.897 ms 7 130.81.199.29 (130.81.199.29) 139.337 ms 140.607 ms 141.284 ms 8 * * * 9 * * *

So if I have a setting somewhere that is calling out and trying to register ka7u it should show up in my /etc/asterisk/*.conf files, I think. [root@test asterisk]# grep -R "ka7u" * extensions.conf:;exten => 3001,1,Dial(IAX2/ka7u) [root@test asterisk]#

The above is the only instance of 'ka7u' in those files and it is commented out while I'm trouble shooting this. I've checked through the iax.conf files of the friend nodes I work with and commented out all the ka7u references in the iax.conf files on those and still the connection attempts continue.

Any ideas of what this is all about? Ron KA7U

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users