We have ISDN customers for whom we provide CLID-based callback: when traffic for their subnet arrives, we place a call to their router. Their router refuses the call, saving the toll charge, and calls back. Works like a charm. My question relates to determining why a particular call was placed, as one would do with wddialout on a Pipeline. A customer is reporting that the link is being brought up from our side a lot, and we'd like to look into why. Given the timing, I'd guess Code Red scans, but I'd still like to see the traffic so I can determine if an appropriate call filter can be built. On that note, does anyone have a stock call filter they use for this sort of thing? In this age of continuous scanning, it seems prudent to have restrictive call filters in place. -- Peter Lalor Infoasis plalor at infoasis.com http://www.infoasis.com/ "Where's my burrito?" -- Homer ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/