CM: One-X Communicator cannot register to ESS when it goes active

[Craft01]

hello all,
I have a problem with Avaya one-x Communicator.
one-x communicator stations not registering to ESS survivable server during failover. All other IP Phones could register.

 

[Shibz]

Have you tried adding adding the ESS server IP to the server list ?

 

[Shibz]

Have you tried adding adding the ESS server IP to the server list ?

I mean the swrver list one-x settings

 

[Craft01]

Hi Shibz, honestly didn't since on the HardPhones we don't need adding the ESS server IP to the server list and they could register.

 

[Shibz]

That works on hard phone, but ESS IP need to be added on one-x communicatior server list. Try , and it has to work

 

[Shibz]

This will help the station to register to the Main when its active, and to the ESS when ESS goes active. Add both IPs to the server list

Hardphones gets these information from ip network region info.. softclient works differently

 

[Sean655]

The server list in One-X needs to have the ESS IP added, it does not automatically populate once connected to CM.

 

[Craft01]

Thanks Sean655, what if I have about a thousand One-X, I'm not going to change them one by one. I guess there's a faster solution !!!

 

[Sean655]

There is a way to populate the Server List but it requires a little bit of user intervention. Check out this document on using the Centralized Administration Tool: https://support.avaya.com/css/public/documents/100177366
Basically, you can adjust settings for One-X via xml files. I did this for two upgrades and it worked well to update the Server List when IP addresses of the servers changed.

There is a discover.xml file that I pushed to user computers in the appropriate Program Files folder for One-X and it has the IP address and filename of the settings file on our http server used for phone firmware. The file on the http server has the IP addresses of the CM and LSPs and is set the same way as 46xx does with the MCIPADD parameter.

The user has to log out of One-X (not exit), go into General Settings and click on the Auto Configure button at the bottom of the screen and One-X will look for the discover.xml file to know where to get the settings you want and populate the Server List.

You can also manage the settings in One-X through this method and lock down what is shown or able to be edited but I found it less helpful for troubleshooting issues. Give the document a read, I used the actual tool once and now I just manage the xml files I need manually.

I also created dns entries for CM and will probably do the same for ESS/LSP based on the site just to make my life easier for the next upgrade so that I don't have to send instructions to users to go into One-X and click Auto Configure to update the IP addresses if they change. My biggest headache was pushing the discover.xml to all of the machines.

 

[Craft01]

Hello sean655 and many thanks for all.

This requires to act on all computers in order to place the discover.xml file. It is the same thing as updating server list in One-X .

 

[Sean655]

As far as I know, that is the only option and it's better than walking the user through editing the Server List. If you reuse IPs or use DNS entries you can essentially have the process done once and not have to go through it again.

 

[Craft01]

You're right.
I'll discuss with my customer IT team, thanks a gain