Forward calls between distant, unconnected Mitel 2000s

[tundranugget]

We have two unconnected Mitel 2000 sites, 200 miles apart. The only possible link between the two sites is a satellite link. Call the sites HQ and Remote.

We've had a request that all calls to all managers' phones (at both HQ and Remote) be re-directed to an administrator's desk at HQ.

The administrator at HQ will need to know which manager's extension is ringing, whether the extension is at HQ or Remote.

After answering, the administrator will be need to be able to put the call through to the manager, whether at HQ or Remote. If the manager doesn't answer, the call will go back to the administrator.

The managers' phones will not go to voicemail.

We need to decide what to do if the administrator does not answer a call - where will it go.

What kind of hardware will the administrator need to handle the calls for 15+ managers?
How can we connect two separate Mitel 2000 systems?
Will a satellite link be fast enough?

It has already been suggested that we upgrade to the Mitel 3300 ICP. How much would that upgrade cost? Upper management does not really want to spend anything on this project so this upgrade is not really an option.

Any ideas?

 

[MitelInMyBlood]

The satellite link will introduce noticeable delay in the speech paths. If it were me I would suggest putting in a dedicated T1 (full T1, not channelized) and set it up for MSDN between the two sites (assuming the two SX2K machines have the necessary software options to support it. MSDN cards are dirt cheap on the secondary market and readily available.

Yes, you're going to have some monthly recurring cost for the T1 and depending on the number of concurrent calls you may need more than one. (1 MSDN T1 = 23 concurrent calls max)

Upgrading to a 3300 will not solve the connectivity gap between the two sites, though you might be able to get a cheaper circuit, i.e., something that supports MPLS, but you're also going to need a router (that supports MPLS) at each end.

If money is of primary concern I'd personally look at doing it with the old SX2K. Just off the top of my head I forget what software options you'll need on the pbx at each end, obviously some of the "voices" (Voice-1, Voice-2, etc).

I would strongly recommend having a Mitel-certified shop do the work.

 

[MitelInMyBlood]

Software-wise on the SX2K I was right, you'll need all the "voices" except voice-6 + you will need 1 digital link for each MSDN T1 at each end.

The software you can get together in two bundles, p/n 54001139 and 54001160 and you'll need these options at both ends plus sufficient available digital links (also at each end).

You may even have some or all of this now, but I'd still want a certified tech to have a look-see so there's no surprises at the last minute.

What software release is the SX2K at today?

 

[tundranugget]

Thanks for answering. We have no choice but satellite (We are a diamond mine 200 miles across the tundra from Yellowknife, the nearest city). Later, there MAY be towers and a microwave link. We currently have telephone service (116? trunks) to the outside world using satellite bandwidth provided by the local telco. So, given the satellite requirement, maybe we could start with your suggestions to link, and allow call forwarding between, the two separate SX2k systems. As an added bonus, maybe we Comm Techs could also access the HQ SX2k from the RemoteSX2k, and make configuration and programming changes.

What model PBX and MSDN cards would we need at both ends? I don't recall seeing a PBX at the Remote site.

We MAY have access to a certified Mitel tech through the telco, but most of this will have to be done by us Comm Techs, especially at the Remote site.

Someone mentioned MSDN IP trunking. Would it be a possibility?

Thanks again.
Tundra

 

[MitelInMyBlood]

IP trunking, sans compression, is going to consume approx 85k bps of bandwidth per call and VOIP in general doesn't provide very satisfactory results (in my opinion) with the high latency normally associated with a satellite hop. At least not with those in geostationary orbit at 22,000 miles in space.

How much satellite bandwidth (total) do you have?

Conceivably you could do this on the cheap (comparatively speaking) with a couple 3300 IP trunking gateways (1 at each end). I cannot give you the cost figures, those will have to come from your Mitel service provider, but I would think throwing in just a couple of gateways would be far less costly than a full forklift upgrade of your existing PBXs. (assuming the satellite hop is feasible)

With 200 miles between sites, depending on the terrain, I also might be tempted to investigate the cost of putting a terrestrial microwave shot in between the sites. If flat terrain (and depending on frequency) you might get by with the two end stubs and only 4 repeaters. This might be attractive if there are some preexisting towers you could lease space on and not have to erect your own.