mitelmitel
Programmer
We have some people who's YA Lite clients do not monitor the phone.
There are no error messages - when you click 'call' or you ring the deskphone it just does nothing.
I checked the .Net 1.1. framework hotfix and that has been deployed.
________________________
This is the scenario:
YA Server running 5.0
YA Lite clients running 5.0
2 x 3300 CXi's.
CXi 'A' on site A running 9.0.0.48
CXi 'B' on site B running 9.0.0.48
Sites are not clustered or linked via IP Trunking
Both are used by the main YA Server.
_______________________
The problem extns are on Site B.
Site A have no problems at all.
_______________________
This is what I have found out.
Half of the users on Site B [around 10] are able to monitor their deskphones from YA, the other half cannot.
I swapped the working phones with the non working phones [reregistered them] but still no joy.
I swapped the working phones' switch ports with non working phones' switch ports - no joy.
I modified an existing YA Lite profile to use a 'working' extn number when it is loaded instead of its own 'non working extn' and it monitored it fine - ruling out the client.
I created a new YA Lite profile and added a 'non working' extn to it, when I loaded it onto my laptop - it did not monitor it. Using a known working extn number - it worked fine.
So this rules out Network, switches, cabling, client & user profile.
I then created a new extn on Site B, then modified my new YA Lite profile to use it. The client monitored the phone perfectly. This points to the 3300's existing extn numbers being the problem.
So, I checked the Class of service for the affected extns and all were using the same for the whole site, which had the HCi [Mitai] options enabled.
I then deleted the non monitor-able extns from Site B completely, and de-associated them from the clients in YA Administration. Then reprogrammed them back onto Site B, re-registered the deskphones, and reassigned the extn number to the user profile - BUT STILL THE SAME PROBLEM!
Even after completely wiping the extn number and reassigning it - I still get the problem where YA Lite client does not monitor the phone. Yet..... If I program any NEW extns they work perfectly fine, as do 10 or so of the existing extns.
As I said, there are no error messages at all - the client just does not respond at all to any intervention with the deskphone when assigned to any of these extns that cannot be monitored.
The systems have not had a reboot for a while - so I have setup a reboot of both 3300's and the YA server this weekend.
Has anyone encountered this problem before? I cannot think of anything else to do!
Please help - thanks!
There are no error messages - when you click 'call' or you ring the deskphone it just does nothing.
I checked the .Net 1.1. framework hotfix and that has been deployed.
________________________
This is the scenario:
YA Server running 5.0
YA Lite clients running 5.0
2 x 3300 CXi's.
CXi 'A' on site A running 9.0.0.48
CXi 'B' on site B running 9.0.0.48
Sites are not clustered or linked via IP Trunking
Both are used by the main YA Server.
_______________________
The problem extns are on Site B.
Site A have no problems at all.
_______________________
This is what I have found out.
Half of the users on Site B [around 10] are able to monitor their deskphones from YA, the other half cannot.
I swapped the working phones with the non working phones [reregistered them] but still no joy.
I swapped the working phones' switch ports with non working phones' switch ports - no joy.
I modified an existing YA Lite profile to use a 'working' extn number when it is loaded instead of its own 'non working extn' and it monitored it fine - ruling out the client.
I created a new YA Lite profile and added a 'non working' extn to it, when I loaded it onto my laptop - it did not monitor it. Using a known working extn number - it worked fine.
So this rules out Network, switches, cabling, client & user profile.
I then created a new extn on Site B, then modified my new YA Lite profile to use it. The client monitored the phone perfectly. This points to the 3300's existing extn numbers being the problem.
So, I checked the Class of service for the affected extns and all were using the same for the whole site, which had the HCi [Mitai] options enabled.
I then deleted the non monitor-able extns from Site B completely, and de-associated them from the clients in YA Administration. Then reprogrammed them back onto Site B, re-registered the deskphones, and reassigned the extn number to the user profile - BUT STILL THE SAME PROBLEM!
Even after completely wiping the extn number and reassigning it - I still get the problem where YA Lite client does not monitor the phone. Yet..... If I program any NEW extns they work perfectly fine, as do 10 or so of the existing extns.
As I said, there are no error messages at all - the client just does not respond at all to any intervention with the deskphone when assigned to any of these extns that cannot be monitored.
The systems have not had a reboot for a while - so I have setup a reboot of both 3300's and the YA server this weekend.
Has anyone encountered this problem before? I cannot think of anything else to do!
Please help - thanks!