Avaya One-X Communicator SIP Restriction

[Keggles]

Does anyone know a clever way to restrict the usage of OneX Communicator in Avaya 8 SIP either by a single feature or some limiting factor?

I was initially under the impression that the IPSoftphone feature would and that is not the case. I am able to filter all users with the device type "One-X Communicator" in SMGR and isolate stations via our remote worker/VPN addressing schemes currently, but would essentially like to force all users that have obtained this software and are using it to have to call in.

 

[avayaguy23]

The restriction should be at the software deployment level. Have them submit a request to be a part of an AD group for Avaya one-x communicator.

 

[Keggles]

That is in place, however, I need to be able to administrate what is currently in place or have the ability to enable/disable its usage.

 

[avayaguy23]

A software deployment utility should be able to remove software if they aren't part of an AD group. You should talk to your Group policy folks. Otherwise, you should migrate to use Avaya Workplace.

 

[Keggles]

All viable options, although, I am looking to administrate the current environment, Avaya OneX with SIP based users.

 

[NewNic]

your just tryin to find all your users? you could change the cor/cos so they caint call out. then they would be forcd to call you with a trouble

 

[avayaguy23]

I’m assuming you do not have system manager integrated with Active Directory. System manager will sync with AD. It will add/remove their system manager profile based on the AD group sync. No system manager profile means unable to login to the phone.