Remote Call Forwarding on 3300 Using DISA 1

[3300Novice]

I am trying to setup remote call forwarding (so that a user can call in from home and forward their extension to their cell phone) using a DISA trunk. I have the DISA trunk setup and enabled, but how do you tell it which extension you want to forward for when you call in? I am a novice on the 3300 so as much detail as possible would be appreciated.

I have setup a DID (I.e. 555-555-5549) that when I call I get the DISA tone, from there I can enter feature access codes, but I'm not sure what to enter/do from there.

Thank you!!

 

[Mitelmatt]

Hi

Try the Call Forward Follow me Third Party Feature access code?

you will then need to put in the extension number you want to divert and then the number you want to divert too. Never tried it externally but that would seem logical.

You may have to set up a speedcall which has the FAC followed by a pause and then the number you want to trasfer too. Then through disa you can dial the speedcall

Give it a try

By the way the feature code are in system admin, system options, Feature Access Code Assignment. If there is no code under that call forward, add one

 

[Mitelmatt]

did you get it to work then??

Thanks for the star!!

 

[3300Novice]

Yep, I did, thanks for your help. For anyone searching on this in the future here are the detailed instructions. Very cool, it provides full Remote Call Forwarding (RCF) functionality through the phone system.

1) System Administration -> Call Handling -> DISA Calling -> Miscellaneous Assignment

2) Set the “DISA Directory Number” to any unused DID extension #. I.e. I entered 1088 to use 555-1088 on our system as the number to call into to be able to use DISA functions, such as turn on remote call forwarding.

3) The extensions you want to be able to use remote call forwarding with should probably be in their own Class of Service because you may not want to enable these Class of Service Options for all extensions.

4) For the Class of Service for the extensions you need to remote call forward, the following must be set to Yes:
a. Call Forwarding Accept
b. Call Forwarding (External Destination)
c. Third Party Call Forward Follow Me Accept

5) For Class of Service for the trunk that you are calling in on (I.e. Our T1 trunk) the following must be set to Yes:
a. Third Party Call Forward Follow Me Allow

6) Go to the Feature Access Code assignment page and write down the feature access codes for:
a. Call Forwarding – Follow Me – Third Party (On our system it is #67)
b. Cancel Call Forwarding – Follow Me – Third Party (On our system it is **10)

That’s all there is to setting it up, it’s actually pretty easy. Now using our system and my extension (Extension 1037) to turn on Remote Call Forwarding to my cell phone (555-5356) I would:
1) Call 555-1088 (The DISA DID)
2) At the tone press #67103795555356 (I.e. Feature access code for Call Forwarding – Follow Me – Third Party + extension to be forwarded + 9 to get an outside line + the phone # to forward to).

To cancel remote call forwarding on my extension I would:
1) Call 555-1088 (I.e. The DISA DID)
2) At the tone press **101037

 

[Mitelmatt]

excellent, that's how i would have expected it to work.

Great example above though.

Well done

 

[kwbMitel]

I've been using this process for years and there is one critical ommision from your process.

The trunks need to be toll controlled via COR or you must use DISA with verified account codes.

Otherwise you have opened up your system to toll fraud.

Dial DISA, Dial 9, dial anywhere.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

KWB - I have beaten myself black and blue over DISA. The client demands it with 9+ worldwide access permitted and an 800 number on it inbound, good grief Charley Brown. Initially they also demanded 4-digit DISA pin codes, which of course were compromised immediately & they got hit with about $10k toll fraud charges over a long 4-day holiday weekend (Thanksgiving). That was several years ago. We wisely got it in writing to enable this, so we were covered. All that's changed is the length of the PIN. They thought by going to 7 digits it would help. Wrong again. Then to 10 digits with # required at the end. That lasted about 6 weeks then broken again. Ultimately they had to remove the toll-free number on the front end. We had to have one of the IXC security people come in and make a presentation to get them to finally realize that *WE* were right