Multiple Extension Divert

[MitelRob]

I have a requirement to divert a set of internal extensions to an individual number (xmas party time!). I do not have physical access to the devices but I can reprogram using the 3300 system console.
My current thinking is to export the current Call Rerouting Assignment form, edit the First Alternative for each extension and import the data back in. When the extensions need the divert removed I would import the original form back in again.

Is this the simplest option or can anyone suggest a better alternative?

 

[MitelInMyBlood]

Why not use CFFM 3rd party? Quick and easy. You of course would need to issue the command against each of the exts you wish to forward, but you can do it from any ext that has it allowed in CLOS.

You will first need to establish 2 FEature access codes; Call Forward Follow Me 3rd Party and Cancel Call Forward Follow Me 3rd Party; IE, **2 to enable, ##2 to cancel.

Works as follows;
From your phone dial **2 + the target ext + the complete destination number (as you would dial it)

Upon their return individual users should be able to cancel it themselves, or you could issue the cancel command individually to the necessary extensions.

We use this feature anytime we need to evacuate the bldg for hurricanes. We have a Dister Recovery Route Set that automatically takes the important extensions, but you know you always have a few others who suddenly at the last minute think their phones are important too, except they've already left the building.

 

[MitelRob]

Thanks for the suggestion.
I have around 30 extns to divert, is there any way of issuing an equivalent to the **2 from the Maintenance Command window? (that way I could copy/paste the commands rather than have to key them each time – lazy I’ll admit but we’re a small team so any time saving is good).

I know you can do a LOC FE EXT to find out the currently active features but that’s a report-only command.

 

[MitelInMyBlood]

No.
However, if you have the TAPI driver loaded on your PC (even the one that came free with YA-Light) you could list them all in your Outlook Contact list then simply click on each one, in sequence. The IOC application also offers this same ability.

You could also program a personal speed call entry on everyone's phone and make them responsible for forwarding their own calls. - (God forbid anyone ever be expected to take personal responsibility for their own calls.)

Every time we have attempted to address administrative tasks (ie, taking responsibility for forwarding your own G.D. phone) it has ended in disaster. The stronger the crutch you provide for your mental midgets, the more blame you will receive when something goes wrong.

Trust me.... I've been at this for 22 years.

 

[paterson]

Other than the codes, the only way to do it remotely would be either from a console set that has the COS ability to do it, or using the Group Admin tool. Dialing codes + ext# is much quicker than either of those in my opinion.

I have seen some sites that will create a System Speed Call for each extension required that contains the code + ext + destination. If the ext DN was 4444, they might make a speed dial that is *4444 or 4*444 or whatever you like. The idea is that the ext DN will be incorporated into the Speed Call. The benefit to this is that is programmed once and the user can set easily. If you want, you could create a second Speed Call for each ext that uses the same format as the first, but substitute a # for the * or whatever your dialing format will allow for. This second System Speed Call would have the code for canceling the forwarding.

The only programming changes to the Speed Calls after the fact would be changes to change the destination.

If you need to have this done from outside the building, you could implement Direct Inward System Access to get system dial tone.

_______________________________________________________________

If you are not part of the solution...

Then there's good money to be made in prolonging the problem.

 

[paterson]

I see MitelInMyBlood beat me to the suggestion! You must type fast, haha. Cheers!

_______________________________________________________________

If you are not part of the solution...

Then there's good money to be made in prolonging the problem.

 

[northportphoneguy]

OK, this may seem silly but it works for me. The security department wants more than 10 extensions forwarded to a cell phone and canceled at various times during off hours. They would have to dial in all the remote fwd code + ext + destination and then dial 'cancel all fea remote"+ext to back to the default. Miss dialing on their part was frequent.

So I dug up an old modem and wrote a small batch file that would dial to the modem the string I wanted. Simplified, it is:

atdt**1588001105>com1
sleep 4
atdt ath
sleep 4

translation is:

attention modem; get dialtone; **15(my fea code for remote cfd); 8800(extension to be fwded); 1105(speed call ext to cell)

The >com1 redirects the string to the com port1

the sleep command I found on the net to delay the batch file 4secs to give the modem time to do it's thing. The ath command hangs up the modem. Repeat as many times as you like.

You will need the Mode command to set the com port.

I set up a sheduled event in Windows to set this off at the time that the security department wants and I do a similar batch file to cancel the fowarding. I also put 2 icons on the desktop so the security officer can click the icon and the batch file will run.

Hope this helps

 

[MitelInMyBlood]

You can also perform the remote CFWD command from a Teleworker phone. That's the method we used during hurricane IKE.

As paterson suggested, the system speed call table might actually be a good place to park these, so long as it doesn't become unmanageable in size. Just be sure the trick number chosen is consistent across all users, does not cause a digit conflict and is not something that can be accidentally dialled or hit externally except through DISA. If enabling DISA for the first time, DO NOT put a toll-free number on it for access and be sure to read & understand the precautions necessary to guard against toll fraud.

Finally, since you're going to have several (many perhaps) I would highly recommend creating an Excel file to keep a record of these. (We keep ALL SYS SP entries in Excel to document what, why, and who).

 

[MitelRob]

Thanks for all the options, I particularly like the sound of the YA-Lite solution - I'll have a play around and see what works best.

Good point with documenting the SYS SP, thankfully we don't have many at the moment but it's still worth keeping a list with comments & owners etc.

Happy New Year to all.