We have a Mitel 5000 version 6.0.9.57 that was just installed this summer. A few weeks after install they started complaining about an outgoing call issue on analog lines.
They would dial a number and then connected to another number or hear a "call cannot be completed as dialled" message. They would then hang up and make the call again and would be successful. When they checked their dialed number display and the call log the number recorded was correct. We have contacted the carrier and they tell us the lines are all fine.
The customer tells us this happens very regularly, sometimes as much as every second call. I was on site yesterday and made 53 test calls and experienced 2 connections to wrong numbers. This happened while dialing the same number over and over again on all the various trunks. On the first failed call I dialled xxx-xxx-5580 and was connected to xxx-xxx-5585. The lady on the second call was mad at me and wouldn't give me her number. On both occasions the number recorded in the call log was correct.
Has anyone ever seen this type of behaviour before? Any idea if there's something in programming I can look at? All programming looks good to me and looks the same as all our other systems in the field.
Thanks
They would dial a number and then connected to another number or hear a "call cannot be completed as dialled" message. They would then hang up and make the call again and would be successful. When they checked their dialed number display and the call log the number recorded was correct. We have contacted the carrier and they tell us the lines are all fine.
The customer tells us this happens very regularly, sometimes as much as every second call. I was on site yesterday and made 53 test calls and experienced 2 connections to wrong numbers. This happened while dialing the same number over and over again on all the various trunks. On the first failed call I dialled xxx-xxx-5580 and was connected to xxx-xxx-5585. The lady on the second call was mad at me and wouldn't give me her number. On both occasions the number recorded in the call log was correct.
Has anyone ever seen this type of behaviour before? Any idea if there's something in programming I can look at? All programming looks good to me and looks the same as all our other systems in the field.
Thanks