Hello Kevin!

15 May 05 17:36, Kevin Klement wrote to Mike Tripp:

 >> address, I could still have the analog node dial Seaborn if
 >> nothing was happening on the IP side...due to issues at
 >> either end.

 KK> Now, how do you do that? Can you show me?

Sorry, looks like I misremembered the way I've done this since my node's
entry has evolved over time.

You can do a simple DIAL statement with 
.  In your case, that's going to apply to
everyone using the same "generic" IP number, though.  My node had
a dual listing with a real analog number that made the translation unique
to him, though.

Binkley will try to dial the parent host/hub entry for a Pvt/Unpub listing.
 So when my node dropped his analog line and switched from a listed node to
Unpub, my Bink started trying to dial itself automatically, since I am his
host.

My nodelist compiler (QNode) can also assign a number that will override
the listed number with one of your choosing...as long as listed number is
not -Unpublished-.  If yours can do the same/similar, that might be your
path to overwriting the generic number with your own for only the specified
address.

Overall, it won't have much bearing on your problem.  Your logs will fill
with just as many attempts to call yourself as it currently does attempts
to run your null scripts.  Just another technique that might help
troubleshooting, and it recycles on the BUSY fairly quickly, but your
script probably is cycling pretty quick now.

Sorry I haven't had much tinker time to assist.  My baby girl is graduating
from high school on Fri, so the whole household has been tied up in getting
the house ready for invasion by out-of-town family this weekend.

I did manage to clone my current setup to another local drive and comment
out my EVT statements and substitute yours.  Bink did not try to outdial
for any of the existing HLOs that were in my real outbound and I tried
holding something for the same node that is giving you trouble and it
didn't/wouldn't try to dial him either.

.\\ike

--- GoldED 2.50+