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 - Lebeter

Pages: [1]
1
Mitel Software Applications / disabling Chat with Micollab?
« on: June 08, 2016, 07:43:33 PM »
beyond changing the availability in status options, is there a way to completely disable chat with Micollab out of user control?  Reasoning is we have a few employees abusing it, so wondering if the users can disabled on a case by case basis or if the whole feature can be disabled.

2
Have a few employees who abuse this.  As soon as the call forwards to them, if they don't like the caller they dump the customer into voicemail.  Wondering if that icon can be toggled in the client or on the server?

3
MiVoice Office 250/Mitel 5000 / UCA and Exchange Server 2016
« on: December 17, 2015, 03:29:28 PM »
Realize this was just released not long ago, but wondering what release if there is one at this point that would be compatible with Exchange Server 2016.

4
MiVoice Office 250/Mitel 5000 / Re: mitel 5000 and caller id
« on: February 12, 2015, 07:39:04 PM »
I don't know if this relates, but we have experienced this bug and it was finally attributed in our case SPECIFICALLY to our receptionist forwarding the call using the UCA Software Attendant Console.  The CID is passed just fine if the receptionist uses the physical phone to make the transfer.  CID will follows in that case, but not if she uses the software transfer function.  This is a bug with the Mitel UCA and I finally gave up hassling our dealer to get Mitel to fix this after 2 major version updates and multiple tickets.  When we purchased the system I went through so much assurance to our receptionist that things would be easier once she jumped into using the console I didn't have the heart to go back and tell her to go back and instead have endurred numerous complaints from sales about their inability to get CID to incoming calls from our office.  They all show up as our office number because of this bug.  Something for you to look at and may explain why it works at some and not others depending on if they are using the software console.

btw the "Propogate original caller ID on Transfer" flag list also has all the users in it, makes no difference.

5
MiVoice Office 250/Mitel 5000 / Re: Hold Timers
« on: January 20, 2015, 01:53:36 PM »
yes you are right.  currently once the recall timer expires, it does go back to the recall destination which is the station.  and yes once the recall timer expires it goes to the attendant.  the calls aren't disappearing per say.  if the station doesn't pick up the phone after it rings back their station and the recall timer expires, it goes to the receptionist.  if the receptionist doesn't pick up, the call gets forwarded to a day call group where it rings out selected extensions.  These folks are leaving people on hold for 5-10 minutes while they call someone else to get an answer.  if they don't answer that first call they put on hold they lose it.  So my only choice is to set a long hold timer for everyone, or a long alternate hold timer and assign those specific folks extensions to that alternate timer.  Hope I have it correct now?

6
MiVoice Office 250/Mitel 5000 / Re: Hold Timers
« on: January 19, 2015, 12:17:28 PM »
that makes sense with the alternate hold timer.  yeah the recall goes back to the receptionist as its supposed to do.  what happens is if the attendant/receptionist is gone we have setup a ring group to forward to, so of course those recalls will go to random people, but it works as it should.  I extended the timer so hopefully that keeps folks happy.  maybe the alternate hold timer is what a few of these folks need.

7
MiVoice Office 250/Mitel 5000 / Hold Timers
« on: January 16, 2015, 01:12:59 PM »
I need some direction on how to setup a call flow path with our 5000.  Right now someone puts a call on hold, it waits the 90 seconds, and then if the user does not pick up their call on hold, the call gets directed back to the receptionist/operator.  From there if the receptionist is not available it forwards to a hunt group of which there are random users assigned from different departments ensuring someone will pick up the call.  this is a small business so its vital we pick up the call vs it going to voicemail and lost business.

the situation arises where the user receives a call, puts the call on hold to refer to another person the user calls out to, and then wants to retrieve the call.  The problem is the call wasn't answered within the 90 seconds and then the original caller gets thrown around to the receptionist and then possibly to the hunt group if the receptionist doesn't answer.  the original caller is then confused as to how they lost the employee they original called.  while i can extend the initial hold time, i'm not sure how i can mimic the programming our old system had.

In our previous comdial system you had a hold timer and then a retry timer with i believe a programmable set number of retries.  that does not exist at least in the factory timers for the 5000, so i'm guessing people either setup workarounds as far as forwarding to dummy hunt group and setup a recall timer?

Does anyone have a method for setting a specific number of hold retry timers while not disrupting the eventual fallback forwarding if there is no pickup after so many retries?  I see an alternate hold timer, so wasn't sure how that worked.

I just remembered that the comdial system allowed you to press the hold button to extend the hold timer again vs the intertel which requires you to pick up the call and put them back on call to extend the timer.  i guess the question may be can that be programmed?

8
It looks like unless you want native calendar integration which we don't use any calendar integration natively or with Outlook, just contacts integration with Outlook, it may be a mute point to require SP1 before I run the Exchange SP3 Update.  Does that sound right?

9
Thanks for the quick reply.  Don't have SP1 on yet, will have to get the dealer out here to do that.  Do you know offhand if SP2 is supported by the original 6.0 release?

10
Mitel Software Applications / UCA 6.0 Compatible with Exchange 2010 SP3?
« on: January 24, 2014, 04:32:43 PM »
Is anyone aware of whether UCA 6.0 Server and Clients are compatible with Exchange 2010 SP2 or SP3?  I need to upgrade our server to SP3 for some other issues but was unable to back when we were on UCA 5.x and being told that it was only compatible with Exchange 2010 SP1.  Can anyone provide some clarity to this, I need to get SP3 on our mail server soon.

Pages: [1]