One-X Communicator 6.1 won't connect when station is 9608 / 9611 on CM6.x

[1Jumbo]

I have a custoner that has a handful of S8300's with G430s around the country. All locations except one are 5.2.1, the location that fails is a 6.x. The customer logs in remotely to the 5.2.1 using One-X Communicator 6.1 with no restriction as to the set type (which have "softphone?" set to yes). If the customer tries to connect to the 6.x, the One-X Communicator will not connect. I found out all the sets are 9608 or 9611. For testing purposes, I had him create a 4610 and he was able to log into that phone.

The customer does not want to change their set type to 4610 because they want to use the 9608/9611 features.

Therefore, it seems the network is good, he can use a One-X Communicator but not if the phone is a type 96xx. Any ideas?

 

[randyb19]

I just test on one of my 9611 phones and it connected fine. I have the phones aliased from a 9630 to get them administered. Does your customer get any type of error, or does it just hang when trying to connect?

 

[1Jumbo]

The customer was getting an error "Your login attempt was unsuccessful. The telephone type you are using is not supported in this configuration". We put in a ticket with Avaya (at customer request) and we were reminded to check the basics. The 1XC that the customer is using is 6.1.0.12 and the latest version is SP5 which is 6.1.5.07. The SP5 notes state that one of the enhancements is 96x1 support. The customer is working on getting the latest version but has to make some changes to his profile in order to download anything from Avaya so right now I am just waiting for results.

Thanks for your reply, Randyb19.

 

[1Jumbo]

Resolved issue. The Service Pack 5 version of 1XC fixed it.