This issue has been resolved. It turned out to be a SIP DOS attack to the other node. I'm not sure why he was able to connect to nodes besides mine. I have noticed multiple app_rpt boxes that have SIP enabled being attacked by Amsterdam IPs. 188.138.74.76 and 188.138.74.90 are two that come to mind. We've reported the abuse to the ISP (RIPE), but I'm not holding my breath.. 73 --- Original Message --- Kyle, Does the other node have a problem connecting to nodes other then yours? Does the other node have problems with incoming connections? What are the node numbers involved? Check the system date and time on both nodes. 73, Steve N4IRS On 10/24/2015 01:36 PM, K Yoksh wrote:

...

* Hi all, *>>* I recently converted one of my boxes from ACID to DIAL, and have run *>* into this issue... When a particular node tries to connect to me (or *>* vice-versa), I hear a 'connection failed' message, and see the *>* following in my logs: (note I've replaced the actual IP with IP ADDRESS: *>>* chan_iax2.c: Address [IP ADDRESS] failed CallToken hash inspection *>>* I did make sure that the node's IP in rpt_extnodes matches the IP of *>* the remote node. Other stations can connect to me, and vice-versa. *>>* Any ideas? *>>* Thanks. 73 *>>* Kyle Yoksh *>* K0KN *>* Olathe, KS *>* Allstar 2210-2219*