The way we achieved this in our enterprise, irrespective if it's internal or external (MRA), is to use a custom jabber-config.xml file for Jabber phone devices and to modify the default jabber-config.xml file to disable phone services.
This is how we did it:
- Make a copy of the existing jabber-config.xml from your TFTP server and give it a different name, for the purpose of this post I'll just call it jabber-config-uc.xml and upload it to your TFTP server(s)
- Anyone provisioned with a CSF, TCT, BOT, TAB phone device will need to have the above file specified under their device. From the Jabber device, if you scroll to the bottom you can fill in the "Cisco Support Field" with configurationfile=jabber-config-uc.xml. This can be done in bulk using BAT.
- Now you'll have to update the default jabber-config.xml file to add an additional parameter under <policy> to disable telephony.
<Policies>
<Telephony_Enabled>false</Telephony_Enabled>
</Policies>
Upload the default jabber-config.xml to overwrite the existing.
Word of caution: If you do not specify a custom .xml you will cause a potential outage for your phone service users as they will take on the default xml file and phone services will be disabled.
Your IM only users will automatically use the default file while your phone service users will use the custom XML where the phone service is not disabled.
This is the solution that worked for us. It does introduce a bit of an administrative overhead to manually specify the Cisco Support Field but with templates, BAT, etc. it doesn't present a problem.
As always, test in a lab environment before you pull the trigger.
Hope this helps.
