IP Networking Mitel 5000 v6.0 to Inter-Tel Axxess v7.0

[jmarcwsp1]

I have a client who has 15+ Axxess systems connected via IP Networking.  They eventually want to upgrade all locations to the 5000 but due to budget constraints can only do one at a time.  Although this is not supported by Mitel what are the issues that they experience?  Thanks.

[IPInstaller]

We have a v6.0 5000 networked to a v11 Axxess with no issues at all. There is also a v5/1 5000 in the network.

We also run CT Gateway which connects them all together.

Lastly, we run UCA which works across all 5000 and Axxess nodes.

[jmarcwsp1]

Any insights on HX v5.0, 5.1, or 6.0 or IP Networking to Axxess v7.0?  Thanks!!

[619Tech]

Looks like you need to upgrade the Axxess systems for IP networking with the 5000's. From the v5.0 Installation Manual:

"For network connectivity, Inter-Tel Axxess® systems require
software v7.0 or later for T1 point-to-point protocol (PPP) networking. IP networking requires
v8.231 or later system software, IP Resources Application (IPRA) firmware v9.0.0 or later, and
applicable licensing."

[jmarcwsp1]

THANK 619tech-

However I have a different customer that has (4) Axxess v7.0 system IP networked to a v6.0 Mitel 5000.  No major issues to report...

[DND ON]

If I remember my history correctly, didn't the CPC come out with version 8.2? Is there even a LAN port on a version 7 CPU?

[jmarcwsp1]

The cpc arrived at v8.0 circa 2003. Up networking on v7.0 required a chip to enable ip networking.

[Tech Electronics]

Jmarcwsp1,

First of all, what exactly are you referring to when you say that it is not supported by Mitel?

Secondly, IP networking on an Axxess was done with an IP Resource Card and not the CPU or even the CPC.

Third, the only issues that I am aware of that will always show up is faxing between sites. You can get it to work, but you cannot guarantee that it will work every time.

Fourth, why don't you upgrade the customer to the latest version of Axxess software? This way you get a little more $ and you reduce your service technicians headaches.

Thanks,

TE

[jmarcwsp1]

1.  Axxess to Mitel 5000 Networking is no longer supported in v6.0.  This means no Mitel tech support on Networking Axxess to 5000.  You are on your own to make it work.
2.  The IPRC Card set to networking required a chip- 4-32 ports.  This is v7.0-8.1.  v8.2 was the first version that was all licensing.
3.  Each site has stand alone POTS lines for faxes
4.  Axxess is end of life- no support, no licenses, no upgrades.  It would still be cheaper to buy the 5000 than upgrade the Axxess unit to 11.0.  They would also need to upgrade the firmware on all their IPRC cards.

This is for a school.  They want to upgrade all 17 locations one at a time...

[DND ON]

I had to go back and check release notes on the old versions. Yep, IPRC was released in v7 and CPC in v8. Now remembering that an Axel server was required to put the CPU on the same network as the IPRC. How archaic was that?

As to networking between Axxess and v6.0, Mitel made a big deal out of not supporting it. However, I had v9.1, v10 and v11 Axxess systems networked with v6.0 systems. The only issue I encountered was DEE not working on intercom when called from an Axxess node.

The only other issue I can think of is v6.0 phantoms not being recognized by a pre v9.0 Axxess system.

[Tech Electronics]

jmarcwsp1,

This is how I always approach this type of scenario and if you think about this in terms of logic then you can eliminate any compatibility between the systems of features that do not exist on both systems.

Also, you need to look at the OAI stream of both systems as being incompatable due to a change of the OAI to the version 10.0 stream later in Axxess so anything cross-OAI applications might need a CT Gateway and cross-OAI functions most likely will not work as expected or at all.

Other than that basic call functions should easily be supported as the networking is just seen as trunking in the most basic of terms.

I think that Mitel isn't supporting it because they don't want to deal with all the headaches of making all the features available that would have been if they were all Axxess systems or all 5000 systems. This is also a way to force companies to get off of the Axxess Platform as they think they will be incompatible.

Thanks,

TE

[jmarcwsp1]

Great insight TE!

The primary purpose of their current IP solution is to share VM.  They do not have system OAI or 3rd party software activated on any of the systems.

Thanks!!