Call forward your extension from destination phone? 3

[Cabarrus]

I have some users that travel between two sites, is it possible for them to enable/disable call forwarding of there extension to a different phone when they arrive at there non primary location.

They have a new Mitel 3300 CX-II Release 4.1 with 5324 phones. Both sites use the same controller via T1.

thanks

 

[kwbMitel]

Call Forward I'm Here.

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

 

[LoopyLou]

If you have the feature number programmed in the Cluster programing it should work. With the above.

There may be no i in team but there are three f's in fudge off.

 

[Cabarrus]

So a user would enter a feature access code and there extension to setup forward, then to unforward to the samething with a different feature access code?

Could you elaborate a little more on how it would work.

thanks

 

[kwbMitel]

You do know that this info is readilty available in the help files right?

As Loopylou correctly pointed out, you must have the cluster featureID code programmed correctly in your cluster form.

For Call Forward Follow Me (Third-Party) and I Am Here forwarding, enable Call Forwarding Accept in the Class of Service Options form of the forward destination.

To program Call Forward:
Press SuperKey.
Press No until "Call Forwarding?" appears.
Press Yes.
Press Next until the type of Call Forward appears.
Press Review.
If a number is already programmed, press Change.
Press Program.
Do one of the following:
Dial the destination number.
For Call Forward I Am Here, dial your extension number.
Press Save.
Press SuperKey.

To turn Call Forward on or off (once it has been set up):
Press SuperKey.
Press No until Call Forwarding appears.
Press Yes.
Press Next until the type of Call Forward appears.
Press Review.
Press Change.
Do one of the following:
To turn Call Forward on, press TurnOn.
To turn Call Forward off, press TurnOff.
Press SuperKey.

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

 

[Supernova99]

Why not setup hotdesking if you have a clustered network
Then you have the ability to carry all your personal keys and the benefit of caller ID

Share what you know - Learn what you don't

 

[kwbMitel]

Hotdesking is not applicable to all situations. Especially if the 2 sites are in different Toll coverage areas.

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

 

[MitelAU]

kwbMitel,

Least cost routing would solve the issue you mentioned. Site A connects to Site B. User logs into Site B and wants to make a call local to Site A. ARS route on site B would send call across IP trunk to Site A as local hop off.

Knowledge is power, thats why we share!

 

[kwbMitel]

Voipin, really, you think I don't know about LCR? Give me a little credit. Now you're talking about something that requires hours of maintenance a year as compared to allowing a user to forward their call. Besides, read my post again especially the Not always part.

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

 

[MitelAU]

kwbMitel

No need to get your knickers in a knot.

Knowledge is power, thats why we share!

 

[Supernova99]

Perhaps it just a UK thing but LCR is not so important these days for UK national calls
Most Telcos provide either peak or off peak calling for landline calling and international and mobile calling plans
So if sites have the same telco connected to the system they would have the same calling plan regardless of location. The only execptions being international and mobile calling where specific links can reap cost savings. If these links are in place the ARS on the clustered network would point to these routes anyway to ensure that the best savings are made.

Just my pennies worth.

Share what you know - Learn what you don't

 

[kwbMitel]

Voipin - Agreed, that was a little harsh. Must've been a blood sugar low moment.

Supernova: You need to consider that what works for you may or may not work for the poster in their location. I'm not saying that Hotdesking won't work, but if we're just talking about a couple of users, why bother. Read my signature for my way of thinking.

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

 

[SXWizard]

In a clustered system you can program a Remote DSS/BLF key on the extension on system B to answer calls to the extension on system A. No forwarding required. From the Remote DSS/BLF Help file:


DSS Directed Call Pickup
When a DSS key is pressed during a ringing indication, the host set will perform a directed pickup of the call ringing the monitored device.

 

[Cabarrus]

Main site has the 3300 CX-II w/ 20 Channel PRI and the second site is connected via point2point T1 , and the phones get DHCP from the controller at the main site. A clustered system would assume a 3300 at each site right?

thanks

 

[kwbMitel]

We assume 3300 at both sites because you told us there was a 3300 at both sites. Are you now changing that statement?

Interesting that you say they are connected via T1 and that the phones at site 2 get DHCP from site 1. This indicates that you have IP Connectivity site to site. Is there a particular reason that you do not want Voice over this IP Connection? (Bandwidth considerations for e.g.)

Regardless how the controllers are connected. IP, T1, Xnet over PRI. Clustering is possible with good design and the features mentioned above are available.

All features mentioned above, Forwarding, Hotdesking, Remote BLF's require Clustering.

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

 

[Cabarrus]

Both sites use the same controller via T1." sorry if that wasnt clear.

We do have IP connectivity site to site, cisco router at each site HP Procurve 2610 POE at each site, voice & data vlans, untagged data and tagged voice ports.

When you mentioned dont want voice over ip connection, isnt that what i have though?

As I understand it, all the features mentioned above would require clustering if i had a controller at each site.

I apologize if my statement of both sites use same controller was near clear in meaning one controller shared by two sites.

thanks again

 

[Supernova99]

Hotdesking is the answer then

Share what you know - Learn what you don't

 

[kwbMitel]

second site is connected via point2point T1

Interesting that you say they are connected via T1 and that the phones at site 2 get DHCP from site 1. This indicates that you have IP Connectivity site to site. Is there a particular reason that you do not want Voice over this IP Connection? (Bandwidth considerations for e.g.)

We do have IP connectivity site to site, cisco router at each site HP Procurve 2610 POE at each site, voice & data vlans, untagged data and tagged voice ports. When you mentioned dont want voice over ip connection, isnt that what i have though?

Point2Point T1 is not Voice over IP.

Hotdesking requires Clustering
Remote Busy Lamps requires Clustering
I Am Here Forwarding requires Clustering

Your questions are giving me the impression your systems are not clustered.

[highlight]New Option:[/highlight]
Call forward 3rd party can be accomplished with simple networking.

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

 

[paterson]

Hotdesking can be done on a single controller. It just requires that you program the single controller as if it was in a clustered environment. Search on Help files for Nodal Hotdesking.

_______________________________________________________________

If you did not take enough time to get it right the first time...

What makes you think that you have time to fix it?

 

[Cabarrus]

I thought HotDesking required additional licensing, ill have to double check.

Point2Point T1 isnt voice over ip at second site? That is a bit confusing to me, if you could clarify. Our second site smaller site without the Mitel Controller uses POE an ip phones , default gateway is a cisco router which routes through T1 interface to a T1 inferface on the destination router and back through Procurve switch to controller. I define that as voice over ip, what do we call it?

thanks