|
|
Joined: Apr 2006
Posts: 12
Member
|
Member
Joined: Apr 2006
Posts: 12 |
I've got a situation where inbound calls on 3 outside (non-DID) lines are set to go to a particular extension. After a no-answer the calls are then forwarded to another extension. I've been asked to remove this second forward and keep the call ringing at the original extension, however I've not seen where inbound call routing occures except for DID situations. If I could get a hand in identifying where this data is located, I can probably nail down the fix pretty easily, but in searching through commands (>3004/5, 58xx and a few others) I've come to the conclusion I'm barking up the wrong tree(s). E60X data is cleared for the original destination extension.
Any help is appreciated!
|
|
|
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: Jul 2001
Posts: 1,985
Moderator-Mitel, NEC, Vodavi
|
Moderator-Mitel, NEC, Vodavi
Joined: Jul 2001
Posts: 1,985 |
Hmm... non DID's are routed via CM3004/05. Do they really go the station in question or virtuals appearing on that station?
|
|
|
|
Joined: Nov 2005
Posts: 132
Member
|
Member
Joined: Nov 2005
Posts: 132 |
Possible you have programmed Group Diversion CM162, CM196
|
|
|
|
Joined: Apr 2006
Posts: 12
Member
|
Member
Joined: Apr 2006
Posts: 12 |
Nope, but thanks for the idea - CM162, all are NONE, same with trunks in CM196. I found something that puts me sort of on the right path. In 3019 I found last for digits of the phone number listed as part of trunk 17 (so now I have a trunk number). I think what I need now is a way to map that trunk to the virtual extension and I'll be off and running. I'm going to start pounding the command doc, but if someone's got a quick HOW-TO on this, I'd appreciate it!
|
|
|
|
Joined: Nov 2005
Posts: 132
Member
|
Member
Joined: Nov 2005
Posts: 132 |
Create virtual ext
CM11>xxx:virt ext# xxx - free virtual LEN 000-255
Assign DIT in day/night mode
CM3004>trk#:virt ext# CM3005>trk#:virt ext#
program virtual ext to the key of Dterm
CM9000>ext#,key#:virt ext#
Assign Service Restriction Class C CM1207>ext#:RC
Ringing Line Pick up : Allow CM1582>RC:0
|
|
|
|
Joined: Apr 2006
Posts: 12
Member
|
Member
Joined: Apr 2006
Posts: 12 |
Thanks Rezen. I should have stated this better - I was looking for a way to find what virtual extension(s) are tied to that trunk. In the mean time I've figured out that 3004/5 for this trunk were set to NONE. I'm putting in the desired extension (209) to see if that takes care of it. I attempted this with the virtual for 209 (1209 - set as a key on 209 Dterm) but it had no effect.
|
|
|
|
Joined: May 2006
Posts: 13
Member
|
Member
Joined: May 2006
Posts: 13 |
if the trunks are co trunks , then the incoming call handling is set in cm 3002 for day and 3003 for night. If they are set as dit trunks (04) then the ext number is set in 3004 ( day) and 3005 (night). If the calls are unanswered , then they can be told to go somewhere else in 3015 , (day) 3016(night)
|
|
|
|
Joined: Apr 2006
Posts: 12
Member
|
Member
Joined: Apr 2006
Posts: 12 |
Thanks for that lead! Set 3015/3016 to 15. However it was getting through is now gone!
|
|
|
Forums84
Topics94,520
Posts639,990
Members49,850
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
305
guests, and
31
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|