If you are not using the deployment client part of the Micollab server and are deploying the client manaully you know that you have to fill in the Micollab server name, user and password.
This is how you pre-populate the cleint with the server name.
Taken fom the Micollab Client Admin guide
This how it looks in Regedit
Rarely you need to un-delete a voicemail message. Or maybe you need to migrate users from one nupoint to another but not restore the whole backup
If you have a backup file from the Nupoint or Micollab then you can extract it from here
Continue readingWhen running a diagnostic test on the deployment profile it does three tests. The third test is checking for connection from 85.214.114.20X to your micollab server on TCP port 36008 (through your MBG web proxy possibly)
You can test this manually via web browsing to this URL: https://mcdiagnostics.easydeploy.net/ucawebsocket/?ucahost=The FQDN of the Micollab server
e.g. https://mcdiagnostics.easydeploy.net/ucawebsocket/?ucahost=micollab.pmhaynes.co.uk
The web page should show “{“msg”:”(200 OK)”}” Anything else means the connection is blocked
e.g “Incomplete response received from application” is a response i got when the port was blocked by the firewall
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
This 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 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 readingThere is a known issue on Micollab server version 7.x and 8.x where the Micollab mobile client is failing to register to the Micollab server when used on an Iphone with IOS v13 or v14
Continue reading