Show Posts
1
Mitel MiVoice Business/MCD/3300 / Issue with SDS errors
« on: March 11, 2019, 05:56:52 AM »
Hi
We have a cluster of 8 Virtual ISS servers running 8.0. they are resiliant to 8 virtual ISS controllers in a second Data Centre with 1 GB links.
The cluster consists off around 15000 hotdesk usres homed on 4 "USR" servers and 20000 Handsets Homed on 4 "BaseID" servers.
We have problems with SDS errors comming up with "SDS Data Sharing Mismatch" errors when making changes to Pickup Groups.
They are consistantly on "USR3" controller.
We are able to manage and fix normal SDS errors as they have details of where the error lies i.e. Pickup group number, Extension number, Controller with the error.
But these "SDS Data Sharing Mismatch" errors give no details what or where the error is other than specifying the Controller where the sharing tried to work.
Or maintainer has finally agreed that there is an issue and it is not our admin method and contacted Mitel for help. The reply back was that "This sometimes happens and here is a work around"
Does anyone else have these issues and have had these helpful replies from the manufacturer.
Thanks for your time.
We have a cluster of 8 Virtual ISS servers running 8.0. they are resiliant to 8 virtual ISS controllers in a second Data Centre with 1 GB links.
The cluster consists off around 15000 hotdesk usres homed on 4 "USR" servers and 20000 Handsets Homed on 4 "BaseID" servers.
We have problems with SDS errors comming up with "SDS Data Sharing Mismatch" errors when making changes to Pickup Groups.
They are consistantly on "USR3" controller.
We are able to manage and fix normal SDS errors as they have details of where the error lies i.e. Pickup group number, Extension number, Controller with the error.
But these "SDS Data Sharing Mismatch" errors give no details what or where the error is other than specifying the Controller where the sharing tried to work.
Or maintainer has finally agreed that there is an issue and it is not our admin method and contacted Mitel for help. The reply back was that "This sometimes happens and here is a work around"
Does anyone else have these issues and have had these helpful replies from the manufacturer.
Thanks for your time.