Intercept ? 1

[macphoneguy]

I have a SX-2000, with a Superset7 and a analog RAD that under the right conditions the RAD goes into DND which in turn makes the caller's just hear ringing and they get stuck in Limbo, I did figure out how intercept handling would work for DNIC's and it did light a Light however the RAD is on a ONS port's anyone have any thoughts

 

[MitelTech]

You want intercept handling to do what? Please clarify what you are trying to do and we may be able to help.
As for the rad going into DND, this can be for a number of reasons. If there is no greeting on the rad, the system will put it in DND. If the greeting is longer then what is programmed in the COS, the system will put it in DND. If the rad goes RNA for some reason, the system will put it in DND. You may want to check into those to eliminate the problem.

 

[macphoneguy]

to clarify, we would like to setup a "idiot" light so if the RAD goes into DND for whatever reason someone will have a visual indication, there is a greeting on the rad as when it's not in DND and you dial the rad directly it answers the call and you hear the message, they have called the RAD 6-8 times to check the timing, so we are reasonably Certin that is Right, EDOC's explain how to do it if the set going out of service is a DNIC based unit but the RAD is a ONS port, which only shows either Idle, Busy, or indeterminate for states,
we would like to do this as the call volume is all over the place from 1 call every 10 minutes to 1 every 10 seconds,

 

[cwc3]

sounds like you may need a group of rads!

 

[MitelTech]

I agree with cwc3 on that one.
Not sure, but if you set up a BLF/DSS key for the rad extension number, will it indicate it's in DND? You'd have to try that one.

Do you know you can locate active features on any type of set by entering from maintenance:
loc feat ext XXXX where XXXX is the extension number.

 

[macphoneguy]

MitelTech, You gave me the idea with the DSS/BLF option, I assigned the Rad port number to a dss/blf key and manually put it in DND and WALA the led Started Blinking manually undid it and it stopped Blinking. . . What a Great Web Site,

 

[MitelTech]

Glad it worked out for ya!

 

[Lundah]

I was just working on a similar issue today. In this particular application, the RAD was setup in a single-member hunt group. The hunt group was the first alternative for a non-prime attendant group. Only the first unanswered call to the attendant would go to the RAD, it would go DND afterwards. Like above, I checked the timers, everything looked good. What I did find wrong was that the hunt group type was not set to RAD (has to be a terminal hunt to do this), and there was a 2nd non-prime attendnant group intended for overflow that didn't have anything pointed to it. Changed the hunt group type to RAD, and added the 2nd attendant group as 2nd alternative for the first attendant group, and it's been humming along fine all day.