|
|
Joined: Feb 2018
Posts: 7
Member
|
OP
Member
Joined: Feb 2018
Posts: 7 |
I have been looking everywhere in the settings for the past 2 days. One of our extensions, 130, when called, will ring but will also cause extension 166 to ring as well. This does not happen vice versa. My issue is, call forwarding has not been set, in fact I had cleared forwarding on both phones. I can not find a solution on how to fix this anywhere.
I wouldn't think it to be a group issue due to me calling the extension directly is what is causing it. Are there any other solutions to this issue? I did notice that when the extension is called, 166 will ring and you can answer it, but no info updates on the phone. The screen is just normal as though it wasn't ringing. Maybe that will help with identifying this issue,
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Oct 2004
Posts: 1,491
Member
|
Member
Joined: Oct 2004
Posts: 1,491 |
Maybe there is a ringing virtual key on extension 166 for 130 which is causing it to ring.
|
|
|
|
Joined: Feb 2018
Posts: 7
Member
|
OP
Member
Joined: Feb 2018
Posts: 7 |
That was correct actually. I am a bit newer to phone systems, so can you tell me why a virtual key would cause this to happen? If you can that is.
|
|
|
|
Joined: Nov 2006
Posts: 704
Member
|
Member
Joined: Nov 2006
Posts: 704 |
So you can answer the call to 130 when no one is present at 130 , so like a call coverage key at 166 for 130.
|
|
|
Forums84
Topics94,262
Posts638,697
Members49,757
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
140
guests, and
24
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|