Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2000IPS - inbound call routing day/night

Status
Not open for further replies.

bsols

Technical User
Jul 29, 2005
47
US
I've got a situation where inbound calls on 3 speciffic (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 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).

Any help is appreciated!
 
The E60X forwarding is all clear. In fact, my first attempt to fix this was to turn forwarding on, pointing to VM Pilot, however this had no effect on anything but internal extension-to-extension calls.

My understanding from documentation left by the original installer is that there are day/night delay ring forwards turned on for these 3 outside lines - this is what I'm trying to nail down.
 
Well, here's what I've done - in looking at the extensions at issue: 209 (original ext), 217 and 218(extensions forwarded to) there are no entries under E60X(any, 0-6) except that 217 has forwarding to 1217 (a virtual station). I did some hunting around in CM11 and found this: CM11>017>1217 - AND I also found that the inbound last-four digits (7317) are listed in CM3019>17 data (this would follow the original installer's M.O. in another system that contains DID). Now, I think I need to confirm that my thinking here is right. I now know the trunk I need to work on is 17(based on CM my findings in CM3019), so am I correct in assuming that CM11>017 (which I believe is a virtual LEN) might somehow relate to the trunk number?

I appologise for dumping all my thoughts here, but I want to be thorough - and I appreciate all the help I've received here.
 
ok, 3002/4 were both set to NONE (aha!) so I've set them to 209 to see if this does it. In the mean time, here's the rest:
3009-NONE
3010-1
3012-CODE NOT USED
3013-15
3014-15

Thanks!
 
The worrying thing here is if 3002 & 3004 were not set then 017 was not a DID what was the setting for 3002?
 
Sorry that should read was not a DIT We already knew they were not DID
 
3002 is set to 2 (trunk line), which is why I thought I was suddenly on the right track. Apparently I'm not because the issue is still there. They sure don't make this simple.
 
All fixed - 3015/16 - set both to 15 and that took care of it. Thanks again for the help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top