Did you tried <PhotoUriWithToken>http://10.0.0.1/sAMAccountName.jpg</PhotoUriWithToken> instead "UDSPhotoUriWithToken" ?
When in local network, by default Jabber 9.7 uses EDI and the mentioned document have a specific session on this.
Regards
*Install Cisco Jabber for Windows on a workstation that is registered to an Active Directory domain. In this environment, you do not need to configure Cisco Jabber for Windows to connect to the directory. The client automatically discovers the directory and connects to a Global Catalog server in that domain.
EDI uses native Microsoft Windows APIs to retrieve contact data from the directory service.
The following are the default settings for on-premises deployments with
EDI:
- Cisco Jabber integrates with Active Directory as the contact source.
- Cisco Jabber automatically discovers and connects to a Global Catalog.
Note:
Cisco Jabber supports
UDS using the following
Cisco Unified Communications Manager versions:
- Cisco Unified Communications Manager Version 9.1(2) or later with the following COP file: cmterm-cucm-uds-912-5.cop.sgn.
- Cisco Unified Communications Manager Version 10.0(1). No COP file is required.
You can deploy approximately 50 percent of the maximum number of Cisco Jabber clients that your Cisco Unified Communications Manager node supports.