Jabber
Android Jabber
Android Jabber Workaround for some unsupported phones:
- set the CUCM security mode to “mixed-mode”. You can do this with the “utils ctl set-cluster mixed-mode”. There is no more need of e-token with a 10.0 release (don't know exactly since when, maybe even a 9.0)
- activate CAPF and CTL Provider services
- create a secure phone profile (authenticate is OK, port 5061 for SIP), assign it to the BOT device
- set the CAPF parameter to “Install/upgrade” in the BOT device with a key size that matches the one you set in the secure phone profile
IGEL
Wyse
- Wyse thin OS 8.6 Supports Jabber
- Note: JVDI package cannot be installed on Dell Wyse 3030 LT, 5040, 5010, and 7010 thin clients.
- Wyse Support Platforms
- Wyse 5070 thin client
- Wyse 5060 thin client
- Wyse 3040 thin client
- Cisco Jabber Softphone for VDI 12.7.0 Agent
- Install Cisco Jabber JVDI
Jabber Photos
How to upload photos see ad
Photo Resolution and image type
Cisco Jabber does not apply any modifications to enhance rendering for contact photos in GIF format.
As a result, contact photos in GIF format might render incorrectly or with less than optimal quality.
To obtain the best quality, use PNG format for your contact photos.
The optimum dimensions for contact photos are 128 pixels by 128 pixels with an aspect ratio of 1:1.
128 pixels by 128 pixels are the maximum dimensions for local contact photos in Microsoft Outlook.
AD Photo Schema config
- on the AD, go to the run menu and type mmc to launch the console UI then go to file - add remove snap in
- select “active directory schema” and click add.
- classes and attributes on LHS
- expand the attributes to view all available attributes in the system
- right click on the attribute you want (eg jpegPhoto ) and select properties
- then check the box for “replicate in global catalog”
- Save
Note: you might need to install the Schema plugin
https://technet.microsoft.com/en-us/library/cc732110.aspx
Chat Address Incorrect
https://communities.cisco.com/thread/49717?start=0&tstart=0
I did get this to work for new users, but old users still showing up with <user>@<domain> rathen than <email>
More work to figure out exactly why and how to correct….
Example Jabber Config file:
<?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Options> <DockedWindowVisible>false</DockedWindowVisible> </Options> <Policies> <BDIDirectoryURI>mail</BDIDirectoryURI> <CalendarAutoRefreshTime>900</CalendarAutoRefreshTime> <EnableLoadAddressBook>false</EnableLoadAddressBook> <ServicesDomainSsoEmailPrompt>ON</ServicesDomainSsoEmailPrompt> </Policies> <Directory> <SipUri>mail</SipUri> <BDISipUri>mail</BDISipUri> <UseSIPURIToResolveContacts>true</UseSIPURIToResolveContacts> <BDIUseSIPURIToResolveContacts>true</BDIUseSIPURIToResolveContacts> <IMAddresses>mail</IMAddresses> <BDIIMAddresses>mail</BDIIMAddresses> </Directory> </config>
Jabber Config File Generator
Jabber 11.5 Parameter Reference Guide
Jabber RMA
DNS SRV Record Check
https://cway.cisco.com/tools/SrvRecord
Jabber - disable Auto Discovery
msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 UPN_DISCOVERY_ENABLED=false
* https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jvdi/dell-wyse/jvdi_b_release-notes-jvdi-dell-wyse-thin-os.html * https://techzone.cisco.com/t5/Cisco-Unified-Presence-Clients/Jabber-Softphone-for-VDI-JVDI-Introduction-and-Configuration/ta-p/1302954 * https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jvdi/12_9/rns/jvdi_b_release-notes-jvdi-129/jvdi_b_release-notes-jvdi-129_chapter_01.html