Similar doc for CUCM. https://supportforums.cisco.com/document/65651/communications-manager-rtmt-trace-locations-cli ... View more

Should also note.  This process only exports and adds contacts.  It does not update or delete them. ... View more

The dialback secret is basically a password, it can be anything.  To over simplify, the recieving XMPP verifies the identity of the connectinig server by comparing the dial back secret provided by the initial connection with the dialback secret provided by DNS lookup and return connection.  If they match it is very likely the connection is from a legitmate server. Reference: http://xmpp.org/extensions/xep-0220.html ... View more

Please rate this document. ... View more

Bug ID CSCti14618, is for tracking changes to selinux code.  It does not define a specific problem, and does not include any specific fix that can be accomplished via root.  Further troubleshooting will be needed to identify a specific bug.  Given these symptoms, I suggest investigating these 2 bugs with the first being the most likely. CSCtw46611 - NTP synch fails due to incorrect file system labelling of capture.txt CSCtl97969 - NTP fails when RU from 8.5 to 8.6 ... View more

Currently, there are only 2 documented settings... PhoneService_UseCredentialsFrom VoicemailService_UseCredentialsFrom Reference: http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_0_1/b_jabber_win_icg_chapter_0110.html#JABW_RF_C2C4828F_00 Notice the VoicemailService_UseCredentialsFrom, is for Hybrid Cloud deployments only. A quick internal search did not find any undocumented setting which would accomplish similar behavior for MeetingPlace or WebEx. ... View more

To answer both of your questions...  Yes this functionality is broken, which is why we have a bug filed. Just getting in to semantics here, but I wouldn't use the words cosmetic nor enhancment to describe the problem.  Cosmetic implies there is no effect beyond what you see, and ehancment typically means we are going to add some functionality to the product.  This is not cosmetic, because selecting the SRV option will change CUCM's behavior.  Specifically, it will query for an SRV record, not an A record.  And if there is no SRV record in DNS it won't work at all.  This is not an enhancment request, because this is a deviation from the designed behavior.  We aren't adding some new functionality, just getting what should be there working.  This is just a bug that needs fixing. -- Joseph hardy ... View more

As of today May 15, CSCth25928 is not resolved.  I recommend using the bug toolkit to track the progress of any bug.  Here's a link for your convience. http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCth25928 There is now a workaround in the bug. Workaround: Configure two A records that point to the CUPS pub and sub by configuring a dummy fqdn in DNS where the cucm sip trunk is pointing at. This dummy fqdn resolved into 2 ip addresses. Now the caveat is that you have to configure this fqdn in the cup sip proxy service parameter Server Name (supplemental) In order for cup server to recognize that this fqdn is destined for CUP otherwise we endup in a loop. -- Joseph Hardy ... View more

Following is a link with more information on replacing install media for CUCM. Cisco Unified Communications Manager (CallManager) Unified Communications CD Software Request Cases FAQ http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_qanda_item09186a00802262ed.shtml ... View more