I'm still leaning toward the possibility of extraneous characters in the CID name field as being the culprit due to the sporadic nature of the problem.

When you did the slot dump for the channel 16 issue, did it show an associated station or was the channel just locked out? That almost sounds like a call collision did occur on it when the "most idle" hunting was in place since the channels closer to the middle would traditionally be the most idle.

It's pretty easy to try creating a call collision to see if this is what is causing this issue. Just direct-select the trunk at exactly the same time that you have an incoming call arriving. Obviously, split-second timing is imperative, but it can be done. I hate to keep beating a dead horse [Linked Image from img.photobucket.com] but these are the only two issues that I've ever encountered that have caused the inexplicable.

Ed Vaughn, MBSWWYPBX