Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Several Issues with Ignite and MiCollab Client Integration.

Status
Not open for further replies.

Mitel2016bm

Technical User
Mar 29, 2016
2
US
I have a virtual customer that has, Ignite (MiCC Client softphones), Desk phones that are HotDesked into, and also MiCollab Client softphones. I am not too familiar with Ignite, even being trained on MiCC that training had nothing to do with Ignite...go figure!

I have 3 issues for this same customer, any ideas on this would be greatly appreciated.

1) Ignite keeps throwing a user into and at random, Make Busy states, and when they attempt to switch into a non-make busy state, it is non-responsive. The user was removed from the queue and was moved over to a new machine and went through the process of logging them into the Phone (HotDesk), MiCollab and Ignite. Same behavior in Ignite: thrown into a make busy state and never into ready mode...phone did not indicate make busy and unable to change from make busy to available (or any other make busy state).

2) When removing make busy code in MiCollab, it updates the Desk phone, but not Ignite. Only for one user, this user is a supervisor or manager of the queues.

3) 2 Agents cannot go into break in Ignite. When they click the break busy option they have to click several times before it will stick. This is causing issues with them logging off and on the phones in their A.M. shift.
 
Welcome to the wonderfull MiCC world.

for Micc and its interpoerability with the Pabx , versions are critical

When posting its always best if thats the first line , just list of the versions of everything involved

If I never did anything I'd never done before , I'd never do anything.....

 
Understood - Hope this answers your response! MiCollab is at 7.1.0.55 (MSL 10.4.13), MiCC is at 8.0.1.1, and MCD is at 7.2.1.24. There are MBGs also in this environment - MiVBG is at 9.2.0.23 (MSL 10.4.13.0). All of these are Virtual Servers on VMware, if you need to know that? What else do you need? I may need to call Mitel PS, but thought I would maybe get some feedback on here first...Thanks!
 
1) Ignite keeps throwing a user into and at random, Make Busy states, and when they attempt to switch into a non-make busy state, it is non-responsive. The user was removed from the queue and was moved over to a new machine and went through the process of logging them into the Phone (HotDesk), MiCollab and Ignite. Same behavior in Ignite: thrown into a make busy state and never into ready mode...phone did not indicate make busy and unable to change from make busy to available (or any other make busy state). C
[highlight #FCE94F]Check the MiCC YSE...Employee Workload...Make sure they are not set for single media this would throw a mb every time since they can only be in single media, Can be adjusted or new one built under multimedia/Workload[/highlight]​

2) When removing make busy code in MiCollab, it updates the Desk phone, but not Ignite. Only for one user, this user is a supervisor or manager of the queues.

3) 2 Agents cannot go into break in Ignite. When they click the break busy option they have to click several times before it will stick. This is causing issues with them logging off and on the phones in their A.M. shift.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top