Shutting Down OneX (Agent OR Communicator) forcing unregistration of the hard phone (H.323)

[bseymour]

This is a new issue introduced upon our upgrade to CM10. When agents shut down OneX Agent, it forces the hard phone to unregister from CM. The issue though is that the phone continues to appear connected up at the agent's desk. The agent needs to perform a log off of that phone then log it back in.

This is the same scenario with OneX Agent or OneX Communicator, when in Shard-Control mode. We hit denial event 2018 P FURQ-Mtc: H323/Vphone Forced Unregistration Request. Maintenance has unregistered an H.323 or Vphone station. UID

We are running OneX Communicator 6.2 and OneX Agent 2.5.60315.0
IP phone is 9650: 3.28

We just upgraded to CM 10.

Any thoughts? This happens over VPN as well as in-house.

 

[avayaguy23]

Onex communicator needs to be on version 6.2.14.17-SP14-Patch8) for CM 10 support. Pretty sure avaya put an end of support on 9650 model years ago. I would suggest going through release notes to find out what is supported.