Whenever an incoming call comes in jabber i get only 2 option answer and reject, i dont get any option such as reply with chat, i have seen a demo video where they have shown a incoming call coming where the users decline with a chat message instead of direct reject.
For this to work, Jabber must be able to find a user that matches the calling number as-is or post-transformation using a Directory Lookup Rule. Note that this is an LDAP/UDS query, not a local search of your contact list!
Here's how it works:
Incoming call received with ANI of 1234
If a Directory Lookup Rule XML file exists, Jabber applies any matching transformation rules.
Jabber queries the configured directory source for any accounts with a phone number of 1234
If wildcard searches are enabled in the jabber-config.xml file it actually searches for *1234* (i.e. contains)
If alternate phone number lookups are enabled, it also searches the mobile, home phone, etc. fields. Be sure these are indexed to avoid a significant performance hit on your LDAP servers.
The directory source returns any matching records. Jabber uses the configured username attribute to build a URI (e.g. firstname.lastname@example.org) and searches IM&P for a valid user. If one is found it shows the chat button in toast. It also replaces the caller ID from CUCM with whatever it got from LDAP.
If more than one record is returned, Jabber will use whichever one is in the first position. Since this is unpredictable/random, be sure that phone numbers are unique to each user account in LDAP.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...