How to: Enforce Jabber Client Version(s)

[issofunky]

I'm looking for a way to enforce all systems can only connect with a specific version (11.5)

Is there a simple / quick way to stop 11.1 jabber clients from connecting and allow only 11.5?

I am referencing roll out / tftp deployment design.

http://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200119-Configure-CUCM-TFTP-for-Jabber-Automatic.html

[Jaime Valencia]

There is no way from the admin point of view in CUCM/IM&P to do what you're asking, as long as the client (and that means even 3rd party XMPP clients) has the right info, they should be able to login.

Not sure if there is some way to limit that directly in the endpoints.

[issofunky]

Ergo, my only real world next steps is enforcing GPO policy to force systems to check and update.

Thanks for the quick response.