Subj : Something new... To : Richard Webb From : Mike Tripp Date : Thu Oct 15 2009 02:28 pm Hello Richard! 15 Oct 09 00:41, Richard Webb wrote to mark lewis: RW> DOn't think it can do that. DOnt' know how folks handle RW> situations where they connect with somebody who's got ip and pots RW> both. Lots of ways to do it depending on how much divergence you can handle between node setups and how sophisticated your partitioning requirements are. Simpler kludges are: Assign high costs to the addresses/phone#'s of concern and use separate .EVT files that only grant the intended node permission to call when cost greater than xxx. For the common case of IP=yes/analog=no, you can just use the DIAL verb to translate the destination nodelist phone # into your own...which will always be busy if the analog node tries to dial it. The IP node will already have to have some custom nodelist compilation/DIAL substitution to convince BT to call an IP address or hostname instead of the listed POTS number. I use this trick for my own IP-only crash downlinks because BT will try to crash a call to the parent listing of the Pvt/Unpublished listing...which in this case, is me. Since my RC, my uplink and myself have dual-purpose listings, I let my analog and IP mailers all have at it...so I have failover if one channel is having trouble. I just have the IP node rescan every minute and the analog node rescan every 10 minutes. Once in a blue moon, something gets scanned out at minute 9.5 and the analog node actually beats the IP node to it and sticks me with a one minute toll call. ..\\ike --- GoldED/2 2.50+ * Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61) .