Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - anikan

Pages: [1]
1
Thanks for the advice all, really appreciate it, especially for a "guy off the street".

Our system is the original MXE - I dont think it is a II and I know it isnt a III - thats what the vendor want to upgrade to.

We have ISDN, SIP is a bit difficult where we are, and in 1 to 3 year we are relocating to a new site - 250+ people, two factories, warehouse the lot - totally greenfields - we may not even stay Mitel.

So Im trying to figure out how to keep the world going for a year or two, not have the global HQ phone system reliant on a PATA / IDE drive and not spend money in private manufacturing - oh and deliver everything that's wanted now. Fun times.

Have heard I can swap our the PATA drive in an emergency, our local provider appears to be conservative, if I was using our Indonesian or Vietnam providers I don't think this would be considered so "difficult" or "risky".

So I think my plan is that I will get the controller virtualized, leave the MXE as the ISDN gateway, possibly even upgrade it to a minimal MXE III even if its "just for insurance". Then when the new site is up, SIP it, hook the SIP to the virtual and decommission the MXE.

Just need to figure out the timing for OS upgrades, we are 4 our 5 people effectively looking after a 1000 - resources are very stretched and I need to keep Call Center going.

My understanding if we upgrade the controller to v8 we have to do Call Center at the same time but we can leave the clients on the old software and catch up with their end device upgrade and training later. The business wants me to continue a MiCollab trial, even if its 7.X whilst all this is happening then catch up to 8 when all done. Again fun times.

Like you guys I have been very confused by the 52XX incompatibility and challenged our vendor twice, for ref here is what they said: "...the 52xx series handsets do not work as they cannot be linked via the MiTai proprietary signalling. This was only a capability introduced in the 53xx series phones...".

Im disappointed, they are a workhorse, the 100Mb is a problem but Im getting great deals on the 2nd market - probably as everyone is trying to get rid of them.

Thanks again for the comments / advice. Really appreciate it. I might post some other questions if thats ok - its a challenge to not having been in this work for so long to come back to 6 challenges in one month.

One last thing, from your guys opinion and experience, if you were going greenfields for 250+ staff - would you stay Mitel? Half my meetings seem to be our vendor apologies how "confusing" the software / options / licensing / roles are.

Note we have recently installed Mitel controllers in New Zealand, Indonesia, Vietnam, Singapore and about to do China - so moving aware from Mitel for the HQ would be a big step.

2
Thanks for the posts all - really appreciate the confirmation. Frustrating that it cannot be done programmatically - I am looking at the option suggested - hiring someone to do it.

We do have half-a-MiCollab - everything about our world is 7.X and I have inherited it right at replacement time - whilst this voicemail change is incidental it would have been nice to get one job done simply whilst I look at alternatives / upgrades.

Again thanks for the advice and confirmation.

 

3
Mitel Software Applications / MiCollab 7.3 iPhone 11.x Confirmation
« on: April 17, 2018, 09:20:48 AM »
As per my previous post apologies if I use the wrong terms, I haven't looked at our phone system in probably 5 years (I don't even have a logon) and due to role changes I now have re-inherited responsibility and am trying to catch up - hope someone can help.

I have inherited a MiCollab 7.X project conceived in 2016, installed at cost in April 2017 and never worked since.

Our controller is an 8 year old MXE 3300 running 7.3. We have the compatible version of Call Centre installed. The vendor does not want to upgrade the MXE 3300 to 8.X because they say the hardware is failing, there are no parts and it will cause compatibility issues flowing on to Call Center requiring its upgrade and so on.

After a meeting today the vendor advised that we could fix the MiCollab 7.X install allowing testing and 10 or so users to use it whilst in parallel we work on  the upgrade of the controller hardware, software, call center, possible virtualisation then work back to MiCollab 8.X.

Somewhat happy that there was progress I have come back to two issues:

a) It appears the month after we installed MiCollab there was the mandated 8.X upgrade for iPhones (https://4sightcomms.com/mandatory-micollab-8-0-upgrade-for-apple-ios-users/)

Is someone able to tell me whether iPhone iOS 11.X is still compatible with MiCollab 7.X and are there any significant end user impacts? Or are we dead in the water, either upgrade everything to 8.X or change phone systems?

b) MiCollab is incompatible with 74 of our handsets as they are 52xx models - is someone able to explain why a handset become incompatible with MiCollab given it is a software solution?

Thanks for any help, after going back and forth for the last couple of weeks I am coming to the conclusion either the Mitel suite and licensing is too complicated, our vendor can't explain it well, Im getting really dumb with age, or to get just two test users on MiCollab I have to upgrade everything.
 

4
Apologies if I use the wrong terms, I haven't looked at our phone system in probably 5 years (I don't even have a logon) and due to role changes I now have re-inherited responsibility and am trying to catch up - hope someone can help.

We have an eight year old MXE 3300 running 7.3 for 267 extensions, effectively all with embedded voicemail enabled. We dont have MiCollab or any other feature, just Call Centre.

I am trying to complete an Executives request whilst I parallel research our upgrade options. The requirement is to shorten and standardise the voicemail experience by changing the Non-Busy option to 1 and Busy to option 5 as per http://www.mitelforums.com/articles/3300/mailbox-greeting-options.php.

Our provider has advised
(a) there is no way the default values can be changed
(b) the only means to change the existing mailboxes is via a handset and manually dialling

    198 * 999 XXXX 2 2 138 # # # # # # # # # # 1 5

        where

        198 is out voicemail number
        999 is our admin mailbox
        XXXX is our admin four digit password
        138 is the extension (in this example mine)
        # is hit 10 times to skip menus
        1 is setting Non Busy = 1
        5 is setting Busy = 5

For 267 extensions thats about 4500 numbers that have to be dialled, and 28 for any new extension.

We have been told there is no, zero, zilch, nada, nill, none and no way that this can be done programmatically.

I was hoping someone could tell me something different, a console, hack, FTP, ouija board way I can get this done? 

Pages: [1]