Well...I spent some time with the Verizon engineers who are familiar with our set-up troubleshooting this problem. I did the same thing I did the other day when the ARC went down: busied out all the PRIs on that chassis. We watched as calls were routed correctly onto the next available PRI as they are supposed to. The difference between this time and the time I was having trouble was I had a functioning NIC behind the HiPerARC. This raises an interesting question: does a dead ARC-NIC cause some kind of strange state on the chassis whereby it somehow holds the hunt group hostage? If so, how??? Any clues, 3Com?
A dead nic does not hold the hunt group hostage. The hunt group is dependent on your Telco provider. If your hunt sequence is first available - a dead nic will roll over.
I *know* that this is how it's supposed to happen. However, this is not the way the chassis was behaving in Real Life. I had done a local busy-out on all the PRIs on the chassis and calls were *not* rolling onto the next available PRI. The only way I could get the calls to carry through was to power down the chassis. My question is *why* did I have to do this? I *should* have been able to just send telco a busy signal and have the calls roll on. ********************************************************* Michelle M. Mogil Network and Computing Systems 735 Rhodes Hall, Cornell University, Ithaca, NY 14853 vox: (607) 255-0516, fax: (607) 255-8521 email: mmm3@cornell.edu ********************************************** - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.