Line going to voicemail on incoming call 1

[noisecode]

I have a line that, as far as I know, is only assigned to two extensions, 115 (dispatch phone) and 133 (bell). When someone calls in on this line, after a few rings it goes to the voicemail for extensions 100 (which is an operator). I don't believe this line is any pools. So far I have tried removing 100 from coverage group and removing the line from the console on extension 100 but it STILL goes to voicemail for extension 100. Any ideas on what to check next?

 

[tdaugirdas]

Extensions 115 and 133 may be in a group that the operator phone has an active cover button for. If not, then maybe extension 100 is programmed as the designated "message receiver" for a coverage group with extensions 115 and 133. You may have to do a "print all" to figure out what is going on - paying particular attention to the printouts for the three extensions involved and group coverage information.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[noisecode]

I do not see anything on message receiver for a coverage group, is this the same as principal user?

 

[tdaugirdas]

Why don't you do a "print" report for extensions 100, 115 and 133 - and post the results here - then maybe we can see what is going on.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[noisecode]

Well, what I ended up doing was assigning principal user for 806 (the line in question)to 133 (bell). 133 has no coverage assigned, so now 806 will ring forever, which is what they wanted. Good enough for me.

 

[TouchToneTommy]

Lines that are not in pools will cover to the voice mail of the lowest Logical ID that both has the line assigned and voice mail coverage. In this case that is your Operator.

You can also assign the line to an unused adjunct extension, and make that adjunct the principal user, so that the line won't cover.

Just be sure to label the adjunct in some way so you'll remember what it is doing.