Thanks David, Yes your statements below have been verified by last night's experience. The previous night I was gettting busy signals although I had what appeared to be a lot of free modems. When I opened the "Modem Pools" window in NavisAccess I noticed that the modems listed as "Suspect" were subtracted from the row of "Available Modems", so naturally I figured "Suspect" modems were somehow being made unavailable and that that was the cause of the busys. Apparently the busys were another issue because last night I had so many modems marked suspect (due to ongoing telco issues) that the "Available modems" columns all had big fat zeros in them, yet no busys were encountered. Obviously just a bad choice of column headings for Ascend in the Modem Pools applet. -Terry **************************************************************************** ******** Hi Terry, Typically, 'suspect' modems are placed on the virtual 'bottom' of the modem list to be used as a last resort. That is, only when all other available modems are in use, will the MAX route calls to a 'suspect' modem. You shouldn't get a busy signal from this if the modem(s) are not dead or disabled. If you have T1's and are specifying a channel to be routed to the modem slot where the suspect modem exists, you may want to change 'slot = n' where 'n' is a modem slot without any suspect, dead, or disabled modems. Disregard if you have PRI's. I had a recent case where someone had a 3048 with 2 T1's and a modem went 'bad'. So he manually disabled it but did not disable one of the channels to prevent a 'channel > modem' configuration. Subsequently, the 3048 would try to route the 48th available channel to the 'disabled' modem, anyway, and he would see CRC's skyrocket and the call fail. Strange but true. Why the MAX would still route a call to a disabled modem, I have no idea. When he disable 1 channel, his problem disappeared. Also, to reset the modem's status, you may want to disable and re-enable the modem slot that contains the suspect modems and recheck the list. Or, if that fails to clear it, reset the MAX during an available maintenance window. Hope this helps, David Pascarella Solunet TAC www.solunet.com -----Original Message----- From: Terry Lee, Publisher [mailto:magic at area-net.com] Sent: Sunday, September 22, 2002 3:28 PM To: ascend-users at max.bungi.com Subject: [Ascend] (ASCEND) Suspect Modems Friends, I have a couple of MAXen that are flagging many modems as "Suspect Modems" due to some kind of errors occuring on the trunks that is cutting calls off. It seems that these modems, once marked as suspect, are not available for use by the MAX, resulting in busy signals. Is there a quick & easy way to reset the "Suspect Modem" flags, or at least let the MAX assign these modems in spite of their status? Thank you. ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/