Search results for query: *

Your idea would be a big security problem. You want to use a VPN

1) that is not normal. It should only take 5 seconds or so max. You have a MAS configuration issue. 2) MAS will sync to the Mitel 3300 but not the other way around. Yes, you should configure all users on the MAS server.

Mitel dropped supprt for TAPI a while ago (big mistake in my book). You are out of luck.

a couple ideas: I would guess the server had the sonicwall as the default route and perhaps it was doing some routing (which the ASA will not do). 1) Make sure the HP switch has the new ASA as the default route. 2) Make sure the email server has the HP switch (192.168.0.1) as its default...

The issue here is that most Mitel resellers are "phone people". They are not "network people". Our business has a phone and network component to it and we setup all new MAS servers that need the teleworker solution on a DMZ. Circumventing a company firewall is an absolute no no in the data...

Ask the phone company to turn on "disconnect supervision".

Yes. What issue are you having? The only thing that does not work is the 5550 IP console can not dial a page zone via Mitel IP page unit (tone button boes not work when you do a direct page from a 5550 IP console to an IP page unit). Mitel does not care about that problem and rejected a DCR...

We used to carry both (Cisco no logner). Best practice is to transition from Cisco to Mitel not the other way around.

I don't understand why the instructors teach so much CLI. I can configure an entire very complex NuPoint 12 or 3.0 system and only touch the CLI one time. If you use MAS, don't do this manually, use the "wizzard".

I hope when you say 200, 300 and 400 ext #'s you don't mean IP phones. A single cx controller will not support 400 IP phones.

MAke sure the NIC has the speed and duplex set to auto. If not, the 5550 goes nuts.

I would guess you used the wrong version of the Integrated config wizzard. Did you use the version on the MAS 1.2 CD (also included in the MAS 1.2 download for the first CD).

We are having the same issue with 9.0 UR1. We are going to upgrade to 9.0 UR2 PR2 (new as of a few days ago) and hopefully the problem will go away.