Hi Guys,
Having an issue with a new site that we have relocated to.
Users are programmed on a controller that has been disconnected for the time being (ver 7.2) but are all resilient to another system in the cluster (ver 8.0 SP3 PR2).
the new site is using 6930 handsets as well as some old 5320e handset that have come across from the old building.
When I try and log users on from the old controller into the new handsets, I am getting Error: Feature Failed. when I log them onto the 5320e at the new site it works fine.
Is this because their local controller is at the latest version and doesn't support 69XX phones? I was under the impression that if they were resilient to an updated controller and currently failed over to that controller, there would be no issue.
I have also checked the logs for the failed attempts and can see the following 2 logs. (logs taken from the resilient controller as the other controller is currently switched off)
Hot Desk : 4621 logged out from *8*4137 by system during registration
Hot Desk : Login failed at *8*4137 - Redirect or update issue
happy to be proven wrong if this is not possible but just after some guidance.
The original controller will be updated and converted to virtual in the near future but has been put on hold due to unrelated license purchasing issues. Just after some answers for the customer in the meantime.
Cheers,
JCCDM
Having an issue with a new site that we have relocated to.
Users are programmed on a controller that has been disconnected for the time being (ver 7.2) but are all resilient to another system in the cluster (ver 8.0 SP3 PR2).
the new site is using 6930 handsets as well as some old 5320e handset that have come across from the old building.
When I try and log users on from the old controller into the new handsets, I am getting Error: Feature Failed. when I log them onto the 5320e at the new site it works fine.
Is this because their local controller is at the latest version and doesn't support 69XX phones? I was under the impression that if they were resilient to an updated controller and currently failed over to that controller, there would be no issue.
I have also checked the logs for the failed attempts and can see the following 2 logs. (logs taken from the resilient controller as the other controller is currently switched off)
Hot Desk : 4621 logged out from *8*4137 by system during registration
Hot Desk : Login failed at *8*4137 - Redirect or update issue
happy to be proven wrong if this is not possible but just after some guidance.
The original controller will be updated and converted to virtual in the near future but has been put on hold due to unrelated license purchasing issues. Just after some answers for the customer in the meantime.
Cheers,
JCCDM