Can the Micollab reach the MIVB on port TCP 7050 (SDS)?
Connect to the Micollab via putty. Check this post if you dont know how
login as root and run command nc -vz {host} {port}
This is me pinging a MIVB then checking port 7050 is open
Since version 9.2 of the Micollab server clients recieve this warning when starting the application
To remove this warning you require access to he Micollab server
The step to remove the warnings can be set in
Micollab client service / Enterprise / Default account settings / Enable E911 warning
When you have issues with a Micollab client Mitel will ask you for the logs from the server and the client. What log files to check before sending them to Mitel?
Continue readingThis one had me going for a few hours.
When a user tried to login to Micollab via the legacy app or webcleint an error would show invalid credencials. But we know that the credencials are correct as the user could login to the Micollab portal!
Continue readingAfter adding feature 289 to the FCOS for your user you expected voicemail to email to work. Not with out these extra options!
Continue readingSo you enabled FCOS option 289 UM-SMTP but no emails arrived when voicemail are left.
Continue readingUpdate:
You can also download the lastest Micollab client direct from Mitel here
You can also extract the RPM for Mitel server from the ISO MiCollab PC Client 9.8.21.iso.
Once downloaded extract the package (unzip) so you have a default folder called “Software”
Click on the “Software” folder -> 6000MAS -> Blade-MiCollab_PCClient-X.X.XX-XX.noarch -> packages – several individual packages will be visible now.
After adding your email server IP/FQDN in email settings you have left some test voicemails but no email arrives!
You check the “qmail.current” log under “View log files” and find the issue, whew. How ever, now you are left with lots of failed voicemail to email messages in the qmail buffer which you dont want to be sent to the users
How do i delete unwanted emails from the qmail queues?
Continue reading