QCC Position

[PhoneTechMan]

Hello All - I've a question concerning the QCC feature. I've never really used it or worked on too many systems that use it either. I've a customer site that has one, along with 2 T1's for in/outbound calling. They recently added three new copper CO trunks for a smaller office that they shut down and moved the personnel to the larger site. They had us assign the CO's to the four phones. The problem is the calls coming to those CO's not only ring on the phones but at the console. So, would I be correct in my assumption that when you have a QCC position, that ALL calls go the console regardless? And a quick down & dirty overview of how QCC work would be appreciated as well. Thanks In Advance for any and all assistance.

Tony

 

[merlinman]

Lines only ring on the QCC if they are assigned there.

A quick....No way, that things a MESS, hard to train and you can't do much if anything in the way of programming of them.

I avoid them if at all possible.

That said, I have a few notes if you are interested.

 

[PhoneTechMan]

merlinman - thanks for the reply. Yes I'm seeing that they are a mess, and so is this system. I stumbled upon line assignment for a QCC in programming. I removed them, made test calls and they still ring at the console. I think I followed the correct sequence for removing them. I alos found that you can't "see" the QCC in cent. programming. Your notes and any other assistance provided will be greatly appreciated.

 

[merlinman]

Still ringing has got to be another issue, if they are not assigned to the QUEUE.

Does the QCC cover the extens these lines are on?

When it rings in, what does it show in the Display?

 

[merlinman]

One other thing I forgot to ask;

Does the QCC have to answer all other lines ringing in?

 

[PhoneTechMan]

No it doesn't cover the other exts, and when the call comes in it shows the line number in the display, i.e., 801, etc. And yes the QCC answers all other lines ringing in.

 

[merlinman]

Interesting, a PRINT may be required to see where this issue may be coming from.

It's a shame you can't get rid of the QCC though.....

 

[PhoneTechMan]

What should I look for, and do you suggest a print all or just on the QCC?

 

[jinxs]

The QCC could be an overflow for a calling group with those trunks assigned? If there are not assigned to the QCC Queue, then it has to be somewhere else. As well, are these T1's DID or loop/ground start. They could've renumbered the LDN so that calls come into the queue, then again, I'm thinking and you said you assigned these lines to other phones, so that can't be it. I would do a print of the Lines/trunks, and as well, calling group.

One thing I have found very usefull, if you can do a full print of the system, then you can open the print with notepad/wordpad/or word. Once opened, you can so a Ctrl F, this will open a search, then you can search the print for the trunks in question, and the nice thing is search again. Very useful in situations like this.

 

[merlinman]

I have been using PRINT ALL forever. It seems like the hard way to do things, but sometimes, it's the only way.

Just dial in, get it started, and walk away for awhile 'till it's done.

And, as jinxs says, you now have a very useful tool for trouble shooting.

That's what I was hinting around about.

The problem could be obvious with the PRINT ALL.

Good luck and/or, if you need another set of eyes to look it over, let us know.....

 

[PhoneTechMan]

Thanks for everyone's input, it helped alot. We finally did get the issue resolved. I couldn't "see" the console in either standard SPM(I don't think you can) or with quick access until after I did a board renumber. I did the board renumber because I was still seeing some circuit packs in the system as being in surrogate mode, and verified what was actually in the carriers by me tech onsite. Anyway to make it short, after the renumber and the system came back up, I went in again and removed the line assignments from the QCC, made some test calls, and viola!, they only rang on the phones and not the QCC! I'm thinking the restart knocked out a few bugs that had been hanging around in the system. Let me know if there's any substance to my theory. Again, thanks for all the input.