OneX Communicator administrative mode

[geerg]

Hello all,

I am want to rollout OneX Communicator (latest version) to multiple users ( on windows 10 ) and have a question.

The install itself with the msi-file works fine but is it possible to distribute certain settings like the signalprotocol and CM server address without using the xml-files?
Is there a registry entry perhaps ( did not find it though ).
Or, is it possible to include those settings within the MSI setup?

We're using H.323 and OneX defaults to SIP.
I discovered that I need to copy the config.xml file, for example, to the roaming folder of the user and that's not what we like to do.

OurCM is 6.3 and stations are setup to use softphone.
We do not have a oneX server.

Any suggestions?

Thanks.

 

[mattKnight]

You can use a 46xxsettings file, but it doesn't do everything


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[geerg]

Yes, already tried that.
Thanks for the suggestion.

 

[mattKnight]

This is why I have never rolled out One-X communicator as a tool

It really isn't an enterprise piece of software - virtually every piece of configuration has to be carried out locally.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[redphone]

You can set the signaling protocol when you run the silent setup:

"Avaya one-X Communicator Suite.exe" /silent/ SIGNALPROTOCOL=1

0= Enable SIP signaling
1= Enable H.323 signaling

The CM server address can be set in the 46xxsettings.txt file.
SET MCIPADD 135.9.49.202

For more information:
Implementing Avaya one-X® Communicator

 

[geerg]

@redphone Thank you.

I've created a msi with all the settings needed and am going to use our policies to roll it out
to a test user.