Mitel Forums - The Unofficial Source
Mitel Forums => Mitel Software Applications => Topic started by: Ralfo85 on July 05, 2018, 04:40:40 AM
-
Hi all, first post here.
We are using the MiCollab client in our organisation. We have employees who are using the Client within Citrix. I however have the Client installed on my laptop.
We advice the employees to import their contact from Outlook to MiCollab. I have received a call that suddenly an employee cannot call some of his contacts anymore.
He hasn't changed numbers or anything else. I tried to reproduce the error and I found something I can't explain.
I made 2 contacts directly in the Client (it made no different when I created the contacts in Outlook). Both have the exact same number. I can call the first one without any problem. When I call the other one, MiCollab says it's an invalid number and therefore cannot make the call. I have attached a screenshot of the error. It's in Dutch but I imagine it's something like: Failed. (Invalid number) / MiCollab Client could not reach xxx (phone number). The message is the same at the employee within Citrix.
Does anyone know why we receive this error and how to fix it?
-
What happens when he dials 2*242 directly?
-
2*242 is my phone number which corresponds with my mobile. This is the number I use when calling.
To clarify, we only have this issue when calling external numbers like our customers and when we have created an Outlook Contact for them.
-
What is your extension length in the MiCollab Server?
What can happen is that if it is set as 4 digits and you then create a number like you have (5 digits long) MiCollab will think it is an external number and add the outgoing prefix. Which will fail as it is invalid (and most likely is not in ARS)
-
What king of license is it using?
-
Thanks for replying. We currently have an issue with importing Outlook contacts to MiCollab.
Perhaps these incidents are linked. I have contacted our supplier about this.
I had already checked the extension length in the ARS and that does not seem to be the problem.
I'll just wait until our suppliers replies about the importing incident.