Introduction With Cisco Unified Communications Manager Release 11.0, Cisco Jabber users can search for groups in Microsoft Active Directory and add them to their contact lists. If a group that is already added to the contact list is updated, the contact list is automatically updated.This document will explain the procedure to achive the same. Configuration: 1.Enable enterprise group configuration in CUCM enetrprise parameter: Navigate to CUCM admin page >> System >> Enterprise parameter >> Choose CUCM publisher >> Search for the parameter "Directory Group Operations on IM and Presence" >> Enable it 2.Create Distribution Group in LDAP 3.Make sure the required users are added to the group 4. Configure CUCM to sync both users and Groups. Navigate to CUCM admin page >> System >> LDAP >> LDAP Directory and configure for Users and Groups. Perform sync once after configuring 5. Make sure the Groups are synced. Navigate to User Management >> User Settings >> User Group 6. Login to jabber and search for directory Group : File >> New >> Directory Group >> Saerch for the group and add   <!-- /* Font Definitions */ @font-face {font-family:Times; panose-1:2 0 5 0 0 0 0 0 0 0; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} @font-face {font-family:"ＭＳ 明朝"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:128; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:fixed; mso-font-signature:1 134676480 16 0 131072 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Cambria; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:Cambria; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"ＭＳ 明朝"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p {mso-style-noshow:yes; mso-style-priority:99; mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; margin-left:0cm; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Times; mso-fareast-font-family:"ＭＳ 明朝"; mso-fareast-theme-font:minor-fareast; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-family:Cambria; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"ＭＳ 明朝"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> Can see the Group is added and users who are part of groups are also added   ... View more

    Introduction   Jabber for windows 11.0 has the problem reporting method modified where Administrator can decided whether the PRT should be always left as Detailed level or basic or it can be enabled on user basis. This document describers how this can be achieved using the new config parameter added in 11.0 version   Configure   The Config key to set the log level is : LogWritingDesktop The possible values for LogWritingDesktop are = Always, UserCanEnable or Never   Always: <config version="1.0">  <Policies>    <LogWritingDesktop>Always</LogWritingDesktop>  </Policies> </config>   Logs are always set to DEBUG level.  Option to change the log level to basic will not be available in jabber user interface under file -- help. The "Enable Detailed logging" cannot be unchecked with this config value.     The logs are saved to disk space C:\Users\admin\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs and will not be wiped out or removed anytime diskspace unless jabber reset performed by user.   UserCanEnable:   <config version="1.0">  <Policies>    <LogWritingDesktop>UserCanEnable</LogWritingDesktop>  </Policies> </config>   Jabber user interface will have an option to enable / disbale detailed logging under file -- Help -- Enable detailed logging.     When this config parameter is set for jabber, the default log level is set to basic. User to enable or disable detailed level logging based on requirement.   At Detailed, the in-memory buffer is flushed to disk once full, and is at DEBUG level. In below screeshot can see jabber.txt file is created once enabled detailed logging. Where as in basic this no files will be pushed to C:\Users\admin\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs       When leaving Detailed level or resetting Jabber, all logs on disk are wiped like below. Can see the jabber.txt file is deleted from the disk.       Note : Make sure to collect PRT before you disable "Enabled detailed logging". Disbaling the detailed logging will wipe out the genearted logs.                                                                                  Never: <config version="1.0">  <Policies>    <LogWritingDesktop>Never</LogWritingDesktop>  </Policies> </config>   UI for changing level is available, and defaults to Basic.  When a PRT is manually initiated by user, immediately in-memory logs are flushed to a temporary file and that will create jabber.txt file in disk (C:\Users\admin\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs), This file will be deleted automatically as soon as the PRT is completely generated and saved by user. In this mode there will not be any files written to disk though detailed logging enabled.   Note : If this config key is not configured and jabber is just installed, there will not be any option shown related to log levels. Basicllay the UI will not have "Enabled detailed logging" showing.     With this method the logs will be in detailed level as will start write to disk as soon as logged into jabber.   ... View more

Introduction This document describes solution to jabber for android login failure when the CUPS cluster is configured using hostname under system à Server configuration.   Components Used   Cisco Jabber for Android Cisco Unified Presence / Cisco Unified IM and Presence   Problem Jabber for android fails to login with the error message “The username or password is invalid or the user account is inactive”. The same user can login to Jabber Windows, MAC and iOS with no issues.   From Jabber Problem Report: Name resolution for the server fails to resolve: 08-26 12:55:26.623 7959 9004 W         : WARN [0x5ae1d1c8][sets/adapters/imp/components/Log.cpp( 34)] [JabberWerx] [log] - [MMTP]:CCmDnsManager::DoGetHostByName_l, tp_gethostbyname() failed. host=CCO-CUPS-UCIS-S-002err=2 this=0x5ac79a48   Solution There is a known issue with the Android OS where it cannot resolve hostnames only addresses. Android can access IP addresses and FQDN’s with no issues. Also, this problem would only be present for the Android devices, Windows, MAC and iOS devices would not be affected by this problem. The workaround for this would be to change the server names to either FQDN or IP Address in the Cluster Topology page (or) System -- Server in CUCM for 10.x Note: Restart below services in sequence to have the changes with hostname / ip address / FQDN in the cluster topology to get applied. Cisco XCP Config Manager Cisco XCP Router Reference: https://code.google.com/p/android/issues/detail?id =8030     ... View more

Introduction Service discovery enables clients to automatically detect and locate services on your enterprise network. Clients query domain name servers to retrieve service (SRV) records that provide the location of servers.   The primary benefits to using service discovery are: Speeds time to deployment. Allows you to centrally manage server locations.  This document describes the configuration required for service discovery and the workflow.   Steps to configure DNS SRV records in DNS:   Domain : apps.com CUCM : CUCMPUB10 IM&P : CUPSPUB10   Step 1 : Make sure the Host record for CUCM and IM&P nodes are configured for your domain       Step 2: Configure DNS SRV record for _cisco-uds._tcp in your DNS             Step 3: (Optional) Configure _cuplogin SRV record     Verifying the DNS SRV record created: Follow the below procedure from the command prompt of PC which is connected to domain C:\Users\admin>nslookup > set type=srv > _cisco-uds._tcp.apps.com Server: UnKnown Address: 10.106.112.52 _cisco-uds._tcp.apps.com SRV service location: priority = 0 weight = 1 port = 8443 svr hostname = cucmpub10.apps.com cucmpub10.apps.com internet address = 10.106.112.6 > > _cuplogin._tcp.apps.com Server: UnKnown Address: 10.106.112.52 _cuplogin._tcp.apps.com SRV service location: priority = 0 weight = 1 port = 8443 svr hostname = cupspub10.apps.com cupspub10.apps.com internet address = 10.106.112.7  When it returns the correct FQDN and IP address we can confirm that it has been configured correctly. Note : To verify for your setup, replace apps.com with your domain.   Jabber Login with service discovery:     Jabber sends all requests (HTTP and DNS requests) simultaneously to the below: Webex messenger HTTP CAS lookup with domain _cisco-uds._tcp.<domain_name> DNS query _cuplogin._tcp.<domain_name> DNS query _collab-edge._tls.<doamin_name> DNS query   Among the successful return, the record with highest priority will be used for connecting to services:   Priority Service Request Sent 1 Webex Messenger HTTP CAS lookup 2 CUCM _cisco-uds._tcp.<domain_name> 3 CUPS / IMP _cuplogin._tco.<domain_name> 4 Expressway _collab_edge._tls.<domain_name>   Work flow from Jabber for window Problem report:   User enter userid@domain.com   2015-03-22 19:21:48,812 DEBUG [0x0000085c] [indowplugin\LifecycleController.cpp(421)] [plugin-runtime] [OnEmailEntered] - Enter -  emailAddress = inna@apps.com   Sends out DNS requests: 2015-03-22 19:21:48,875 INFO  [0x00000b84] [rc\dnsutils\win32\win32DnsUtils.cpp(273)] [csf.dns] [dns::DnsUtils::executeSRVRecordQuery] - About to make DNS SRV record query '_cisco-uds._tcp.apps.com.' 2015-03-22 19:21:48,875 INFO  [0x00000b84] [src\dnsutils\win32\win32DnsUtils.cpp(47)] [csf.dns] [dns::mapFromWindowsDNSResult] - *-----* DNS query _cisco-uds._tcp.apps.com. has succeeded. 2015-03-22 19:21:48,875 INFO  [0x00000b84] [src\edge\EnterpriseNetworkSensor.cpp(24)] [csf.edge] [logSensorEvaluation] - EnterpriseNetworkSensor strategy FindAnyInternalRecordWithLatching evaluated to true 2015-03-22 19:21:48,875 DEBUG [0x00000b84] [dge\EdgeDetectionControllerImpl.cpp(342)] [csf.edge] [edge::EdgeDetectionControllerImpl::initData] - Finished evaluation with EnterpriseNetworkSensor. Internal Connectivity: 1 2015-03-22 19:21:48,875 INFO  [0x00000b84] [rc\dnsutils\win32\win32DnsUtils.cpp(273)] [csf.dns] [dns::DnsUtils::executeSRVRecordQuery] - About to make DNS SRV record query '_collab-edge._tls.apps.com.' 2015-03-22 19:21:48,875 WARN  [0x00000b84] [src\dnsutils\win32\win32DnsUtils.cpp(52)] [csf.dns] [dns::mapFromWindowsDNSResult] - *-----* DNS query _collab-edge._tls.apps.com. has failed: DNS name does not exist.   Jabber is connected internally and hence the DNS request towards _collab-edge._tls.apps.com. failed.   CAS URL lookup request to webex messenger:     2015-03-22 19:21:48,890 INFO  [0x00000b84] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: http://loginp.webexconnect.com/cas/FederatedSSO?or g=apps.com [0] Receives HTTP response with 0: 2015-03-22 19:21:59,966 INFO  [0x00000b84] [ls\src\http\BasicHttpClientImpl.cpp(410)] [csf.httpclient] [http::executeImpl] - *-----* HTTP response from: http://loginp.webexconnect.com/cas/FederatedSSO?or g=apps.com [0] -> 0. 2015-03-22 19:21:59,966 ERROR [0x00000b84] [ls\src\http\BasicHttpClientImpl.cpp(414)] [csf.httpclient] [http::executeImpl] - There was an issue performing the call to curl_easy_perform: CONNECTION_TIMEOUT_ERROR 2015-03-22 19:21:59,966 WARN  [0x00000b84] [\casdiscovery\CasLookupQueryImpl.cpp(52)] [service-discovery] [CasLookupQueryImpl::executeCasQuery] - CAS lookup failed: Http connection failed.   Can see jabber mention that the apps.com is not a webex customer. 2015-03-22 19:21:59,966 INFO  [0x00000b84] [scovery\ServiceDiscoveryHandler.cpp(504)] [service-discovery] [ServiceDiscoveryHandler::Discover] - Domain 'apps.com' is not a webex customer. Making Ucm90 Based Discovery with DnsQueryDomain: 'apps.com'    If in case you have the webex cloud alive, jabber getting authenticated against webex messenger can be avoided by configuring "Excluded services _cisco-uds SRV record being used as webex CAS lookup failed:   2015-03-22 19:21:59,966 INFO  [0x00000b84] [quest\ServiceDiscoveryDnsSession.cpp(68)] [service-discovery] [ServiceDiscoveryDnsSession::shouldDnsRequestBeTri ed] - Should DNS request be tried : YES (Has network State Changed : YES (Unknown --> On Prem)), (Is Discovery Session Active : NO) 2015-03-22 19:21:59,966 INFO  [0x00000b84] [t\DnsEdgeServiceDiscoveryRequest.cpp(37)] [service-discovery] [DnsEdgeServiceDiscoveryRequest::makeDiscoveryRequ est] - About to make a full service discovery. (dns && possibly edge if internal records do not exist on domain 'apps.com') 2015-03-22 19:21:59,966 INFO  [0x00000b84] [elocator\EdgeDetectionDnsService.cpp(79)] [service-discovery] [EdgeDetectionDnsService::getInternalRecordsFromDn sQuery] - About to query Edge Detection for internal Dns records.   2015-03-22 19:21:59,966 INFO  [0x00000b84] [src\dnsutils\win32\win32DnsUtils.cpp(47)] [csf.dns] [dns::mapFromWindowsDNSResult] - *-----* DNS query _cisco-uds._tcp.apps.com. has succeeded.     Updates domain information:   2015-03-22 19:21:59,982 DEBUG [0x00000b84] [ces\impl\ucm-config\DnsProvider.cpp(130)] [csf.config] [ucm90::DnsProvider::addPotentialDomain] - Updated domain information: *------------------------------------* | ucm-config Library DNS Information | Highest Priority Domain: apps.com | DNS Record: cucmpub10.apps.com:8443 [weight: 0, priority: 0] | Domain Source: apps.com : LOCATOR_UDS_DOMAIN | Domain Source: apps.com : SERVICE_DISCOVERY_DOMAIN *------------------------------------*   Now it tries with _cisco-uds SRV record as the webex CAS lookup failed:   2015-03-22 19:21:59,966 INFO  [0x00000b84] [quest\ServiceDiscoveryDnsSession.cpp(68)] [service-discovery] [ServiceDiscoveryDnsSession::shouldDnsRequestBeTri ed] - Should DNS request be tried : YES (Has network State Changed : YES (Unknown --> On Prem)), (Is Discovery Session Active : NO) 2015-03-22 19:21:59,966 INFO  [0x00000b84] [t\DnsEdgeServiceDiscoveryRequest.cpp(37)] [service-discovery] [DnsEdgeServiceDiscoveryRequest::makeDiscoveryRequ est] - About to make a full service discovery. (dns && possibly edge if internal records do not exist on domain 'apps.com') 2015-03-22 19:21:59,966 INFO  [0x00000b84] [elocator\EdgeDetectionDnsService.cpp(79)] [service-discovery] [EdgeDetectionDnsService::getInternalRecordsFromDn sQuery] - About to query Edge Detection for internal Dns records      2015-03-22 19:21:59,966 INFO  [0x00000b84] [src\dnsutils\win32\win32DnsUtils.cpp(47)] [csf.dns] [dns::mapFromWindowsDNSResult] - *-----* DNS query _cisco-uds._tcp.apps.com. has succeeded.   Config files download: Jabber will fetch all required data from the server using HTTP request. thought it downloads more file here are the list of imporatant files downlaoded:   >> HOME_CLUSTER_XML : homeClusterUser.xml >> DEVICE_XML : CSFINNA.cnf.xml >> SERVICE_PROFILE_XML : SP0a920736-c32e-d40a-422f-d030784b16f1.cnf.xml >> GLOBAL_SETTINGS_XML : global-settings.xml   Here is the list of HTTP request that jabber sends:   2015-03-22 19:21:59,997 INFO  [0x00000b84] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://cucmpub10.apps.com:8443/cucm-uds/version [1] 2015-03-22 19:22:00,606 INFO  [0x00000b84] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://cucmpub10.apps.com:8443/cucm-uds/clusterUs er?email=inna@apps.com [2] 2015-03-22 19:22:00,715 INFO  [0x00000b84] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://cucmpub10.apps.com:8443/cucm-uds/clusterUs er?username=inna [3] 2015-03-22 19:22:00,731 INFO  [0x00000b84] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://CUCMPUB10:8443/cucm-uds/servers [4] 2015-03-22 19:22:00,824 INFO  [0x00000b84] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://CUCMPUB10:8443/ssosp/ws/public/singleSignO n [5] 2015-03-22 19:22:23,491 INFO  [0x000009f0] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: http://loginp.webexconnect.com/cas/FederatedSSO?or g=apps.com [6] 2015-03-22 19:22:35,488 INFO  [0x000009f0] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://CUCMPUB10:8443/cucm-uds/user/inna [7] 2015-03-22 19:22:36,190 INFO  [0x000009f0] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: https://CUCMPUB10:8443/cucm-uds/user/inna/devices [8] 2015-03-22 19:22:36,205 INFO  [0x000009f0] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: http://CUCMPUB10:6970/CSFINNA.cnf.xml [9] 2015-03-22 19:22:36,252 INFO  [0x000009f0] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: http://CUCMPUB10:6970/SP0a920736-c32e-d40a-422f-d0 30784b16f1.cnf.xml [10] 2015-03-22 19:22:36,268 INFO  [0x000009f0] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: http://CUCMPUB10:6970/global-settings.xml [11]   Can also see downloaded files and their names like below at the end of each file download. It writes the summary of downloaded files like below:   UCM version: 10.5.1 UCM domain: apps.com UCM publisher: CUCMPUB10 Current Home UDS URL: https://CUCMPUB10:8443/cucm-uds/user/inna [HOME_CLUSTER_XML]     [URL]        https://CUCMPUB10:8443/cucm-uds/user/inna     [Host]        CUCMPUB10     [Filename]    homeClusterUser.xml     [XML]        <?xml version="1.0" encoding="UTF-8" standalone="y... [SERVICE_PROFILE_XML]     [URL]        http://CUCMPUB10:6970/SP0a920736-c32e-d40a-422f-d 030784b16f1.cnf.xml     [Host]        CUCMPUB10     [Filename]    SP0a920736-c32e-d40a-422f-d030784b16f1.cnf.xml     [XML]        <serviceProfile> <versionStamp>1423494380-cacddd5... [DEVICE_XML]     [URL]        http://CUCMPUB10:6970/CSFINNA.cnf.xml     [Host]        CUCMPUB10     [Filename]    CSFINNA.cnf.xml     [XML]        <device  xsi:type="axl:XIPPhone" ctiid="7" uuid="{... [GLOBAL_SETTINGS_XML]     [URL]        http://CUCMPUB10:6970/global-settings.xml     [Host]        CUCMPUB10 [UDS_SERVERS]     [1]            CUCMPUB10 [HOME_UDS_NODES]     [1]            https://CUCMPUB10:8443/cucm-uds/user/inna [TFTP_SERVERS]     [1]            CUCMPUB10   Now it downloads the jabber-config.xml file: 2015-03-22 19:22:36,704 INFO  [0x00000894] [etutils\src\http\CurlHttpUtils.cpp(1163)] [csf.httpclient] [http::CurlHttpUtils::configureEasyRequest] - *-----* Making HTTP request to: http://CUCMPUB10:6970/jabber-config.xml [12]     Jabber also writes the downloaded content to it's cache. When it writes each time can see a line like this : 2015-03-22 19:22:36,486 INFO  [0x000009f0] [ervices\impl\cache\CacheManager.cpp(133)] [Cache-Logger] [CacheManager::writeToFile] - Sent cache object to disk   The conent of each file will be in the encrypted form. Here is sample for the one such: [Name] ServiceProfile             [Name] FileName    [Data] SP0a920736-c32e-d40a-422f-d030784b16f1.cnf.xml             [Name] Urls                 [Name] Url    [Data] http://CUCMPUB10:6970/SP0a920736-c32e-d40a-422f-d0 30784b16f1.cnf.xml             [Name] FileContents    [Data] AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAA3YGucuR0n0OEYXs+E3 uQuAAAAAAWAAAAYwBzAGYAdQBuAGkAZgBpAGUAZAAAAANmAADA AAAAEAAAANHvhHA5E3J1wkQHMz6a8IMAAAAABIAAAKAAAAAQAA AAQKozvJYt9h9fm8LX1KHz6PgNAAB5mu+4AjuVNFLxy4gAv4JD Dqbh+68toQX3NSZXn1lTJyPf4nP3u3pI5MkArRIZgyW0nGAW/i uRU6Dnv9JqmjCHaL6wg7i2d2Q5IGJEGw5hpKaxcY2XSG7k6jP/ YCW8CABB9NknN6NRLGT/R01Ojf/b/xDXvU1Fw6/TSs3W7bUrjk fKU9dYRu+lkq6i7fFHDPrkJbGkM2abYt9jZQ8JsyADco5WKFbe fXyo64dHwKZiTtvpwaY2SIGCh1caEJ387dOCA6KFjQ9l2u+Ix7 QEbjURhvx8dsVXgKO/S7tMfjoS63DWLsckikNGHZoabGkP6dkY Az7U8BfnhxGLToauot8uvGq9LDp58b4glWom6bmUtM9jEzkDFG Vyx+c91ZmrMkL7ShOmK+CPK35eLQHpJ0QAbJ+uoH8uPutERcdA XGEHJ6rODQQ7ZLKKBczMK7M2JifACg3uTrhcjSGxaRXByJidc+ gMbU67qL7CGUZ7tTeffbM1JMcWgg4ZUocEL9c5KtyFx9twYI4c o7xm/L0CpsLx0aK+UGrRdRAEfL/Uz/6B+4S0WQu/toCPvb5q8l KcFgBLOaCrYbMlQhWQmIkPLFLpEtPMsR/nSgllA0lAaPn/mGO2 BkU00/gFCVL0BA/40Xs6jUK8z5Kwp/6odG4cWt5xhtDH4XxiFz /t5ILSop3NoI5w6v3K77TsYh9BBZln4y+5X29bBzKBNlhk37F0 D2vBmT0uJAHsZHPk65FEbwu734Zj5s1CDL1eeiuU0+PytMqLVm kXOYDN2XmkXB8qpuSmMwl5ePsZaG7jogio9Anq/wzBhG3vXJp0 iSjRVODwWEybWoHo4inr7m3ZGR4pAKM6vzeaX9QD8AZKFbgjtu 9ljzq28vpujFt+9r2/wj9So7jf95hVGGm4lpV2qR8UozVjQUBs Feow+mslrV+hVi2Myz1KVEWeXa0bUT1/MIqOPskV23e7XEA4Ab RnCeqpXxiIpOmBZqv5isAhQhqRuYxrY5SJ6Os51wNw5McX/JpD EQkY5igQbnzLHPehpRJIOUTswy3BtBMC1k2Gr/wfePpFbdx8Kr +IOtehzSkJyjP+iiIzo1KUGUHrRMetIBW0dVZmV1VZU4WPmZ74 TWBkOQhBDQDYYAz4anod2VNsCVWW2ELOpHQ2rD4P4N0NtmDqi0 dv+jxnzEDIIiorOB51Vrx85qRfZjyGaY+3IlNR2nFQOY/t6PLV I5UtFL2adLgBC3E+zjR7uTk6X87j9uqfgtEg9As5FWVzx7Ntj+ E/63o1ofjyQ4ERm5eLqloBUpGCgeyY+BpR7TikV9mmwAtOJI7k xVgagcsHOSZPj/+eJPdkFNXJ29QsFhUxnWyn9bCT8bZRZ8iV+k XCc1RKCOLetlOvY+2L7mBEiLHKyO91a5x7bHN8E78ePUXZG/gg HmqdCBDjBmFAN8+ttkU3eyfi6g6kfuA0iQHrSG729h5AyoVwXl GseIKVl2HqAXiZC2982bBCHBUbkjvREK4pBjhk4RvLDVT1+HL+ 8EIZ/7TucGfQfhajTN6halZ2BzKxBbuQwaS0cIiwh5xC+aQZd2 iGClTlRzw6MPhcPK7OTz6V6PqH+7PfIjNYLTrT0vv1sQ69Tvw2 cADlJBeb6vS476A1n9DJEmKkd8yS7MJVHwN7wXwfmDS9LM+UEi o0daBQtkeZWa6LqRE07QrYBBt+JTWFEN04UsFFLa0dqhhRDFUW gRwnaQSKCnmrfS9buFo2UOXoyvLG3gY3XPGMS6IOLqclNh9Ry/ ccW9/7hob/HTc7lQS7LzjLUWjNf0FK1auxo6FxfeaFqq3SGnYV qworgd7MvlJ51lE0Otke25Esnn56812d/yWkOmjwGvhX8xrDmF qGzbNpObdj4LM9u49ckbUlaxJl0dOEXExH94jTuAuamptTc8Jm EB2pfQ/15v/eF1szt9K7NNl92ssmvdhUJWcMItF2wFIjmPnphF 23CTW8fnOJ+Xwz8YnHUXbcbc5cFg0OURNLxwNFBBn9T2YJmCwV G9xtz+olxIeUe4WwmmH/o6u6amToI7wjLU6RyaySUDVl0MWe7Q GvnoSbFcbR6IYlZHMb7Z+DBeLrKyv1YCUQOw6LQPl6A1eJfCUY L/Q+ueggKaY/YF6WDNuTuXP1ijef8itHtxJ21jbnuVshYsRots YhDbrcsVsWeKWNPJyf8GGeOuMks7+HkasWhF4xPvjLvoTXT82N SGMyHYzdwZRfbPZodarcCwuhYk/PV/6OH1uaCcIwf5ze6u5Uyf P9dwK17bs75hloc5GxuJJFy9autxt+Ox2uGjLDc8tDu7HDyj/V eyy4rNH6JC30YqlEA11TrRFKgdepLfU7J7wBdyjlEFFK7Vnry0 2rPXUJHR1VBIfTUDc2cGuB8WHobeviX3OJjz0CWuCmLadAE7PG 6ymVgjVJyKSgxRCVzPj90dq5MWzScemqPy6hfzW7cWrCwlaCqr K0HBcmmwnyJBv1vmXUHGfTdGk/oYMEjX0AXOKuZpymIwNjCD7T R+RYichfhYRU3W/yTICVX6SPB1RUdlTjZBS5/KsQtlg99+F6vg tf+7gBdV55DqQBW+hCIJV9u2/+pUB3hrhbHakOh97vSjycu7pU hMfqfEpNsH4eD07sufxC3W6Sd5MxUf0jml4KsadjTHk0BLyhXN nwf8zANfUHoEL/ye/9lXQPVd8F2c4zBj20gt78YqpzCWa2juoF 6cFgF2PO3OfrGPfV45mJ6d2G3lWw35CF4oj6UBvMAlajsn3fs2 VtLV+2n/TMw20nNP/nj1N37SHHNAcmG4Yn6+jE7a+SL5+gRDp2 Bpp8ZIGryVBtoGWmEw+SSRcHZZvzUxMYFJyQAeG9eqH0nZZVzU I3evLVbuskNeaVK8MWOQVaugrWfBKRPyOFBYtxh0sbOm7xh03u /8WebK9GQHUbQBx5YlVcJ+V3sksd+61zmgOgQmxRm/avKOFFsB AiHpwq0N/cgCOTIZYlx4I0Zt76t5lEvJ9POfqG8Ar6A4g1sOAr oH4Vz8txYFOYMDYsHX+Vax/x+itLZNFiPKNEmPuG6N24QxpfvA sf6GSDvhkoOW24VLctvAZAw++FtlTb8V/kJut2T/s3bM+BY7Sd yvejIEmtcFrwutySbPjmz6tJA5DnhG6mJqPvxgtsrpxKqAELUT R5rbHboFUoRhRwhRJA/HASggyED2l9onQXxurJQsQ2600Vuxb6 NCFVtd+8DFOlmTbC9AinbY6zFZTemNf9FMCz8S/lSBGoTMVad2 GUk/Ksx0zVhZrY8Psl0PMYI4otOPA0Qq+0/B/9vajkCVN1VOVw XHN8/38/Qpt3mNHmx9p46xmtkDC+l6aSD8tGoh88SAhMK3K5rY Okz+YiIl7/jLp6dVK4KNY+qVX7xWXa+AUqfdmAky7mLbyt2jgJ 93GIbU2sL9HG3V23/ZzIaEBzf1f6Pif1BuuIxpA49XpeOiaJkR toujxZsYSnwI2cAhEy6pZgQCeFEsmthJ+2CZ6utzaDo703yiIA /SpyI1KeENbq0wU7sAQUPVP5B/Ihjcc4bcROKmlAWambruIu+9 2d5Mk+kJJzKGHlHtH//ujnY7S06sK6YjRQ5JGx9VIjsw01BwOD tERx0piqSrmDJmwNu1bhQ8giKug0JorbDg8zUIdNWtojyId42I hwBSXJMbz671e49Se20ek2c4X0dut8Py2YV8CaJ4RpceMdU2Gi JoLc5Vbbm0fnGMpnNnCcsFB0vQFQqkgFrz1Z7nPogdevf6en2V pciAC3g2CNVF0SghLAgUJZQhEiRGzNDKPRex5czqbkbMmjwb9a dW8XG1hJw4vWQg8RdaXyUyUt7qfSys+U4t1BIGOjOklY6LypZ0 /xJKrzATQLbI46NBWq3696euWeFfZqp5mrKy6bb1JhH92aD6do 6asNkCsrej89c4l+VBt63H/sChmreu8RYKmRHbY+0X3U0Y7Ek5 HQhYq7SnhPeT56BW6f27JQLngBQkK3kXtB/iHt4FQxS0hwTn+O IbQd+Z5qs1bveinNYPk1ghvnS48dIabbX4omTQgUI117DhUF+p HBcg+GESGyCD0IyJFiUm6TvXEu+KHHRkM3hlM5KagUlVr/5hjy igkKcnrcFUez+e+cQ8xYbZNFGJRtkjhJzkqV6n6CM5K4eY/JRI amhsXzl7oslKm7+m8e9od7tpKpao2QzYcWMFO2Ep5MbzBmHc5t lLnltBSyKFlmuoGQO6UDWYrob+y4qvlQ71rEjXgoZkbIkFs42T eA8WWLLC0t2HyJg89qJGE+AW684zmknkrt8wFxHSohOrjiiKbQ +at8zj1T2ZgZ6uxBB6WVvujWAcJ26XOtznEXJzzkoscdZWB8LU A4HB+ZsEdz19h3fe/pwTwhse52lvain7d5oBqgl9RX8sz8RTpa FRH6PXsW0NaquXbLWgcu+IgwZrs33z/cJhtZsLReEOBf92gt3c vnUZjPIhUFBMsyZjRtmGOSYXJS9Y7OQ5aj6ONXbM44BH7w/XJx MszG4iO6975QsPs3VAnLDQTb37Dd4drwuefiHhVWDR/GGnR3IA 5A96YsbXUeqlbfj3Dn5vcAf2MG3WmYDiKNT6RINsw4fT26UmMM slBSrGBAZGBDFYsGuNRmWsutruwSIiK9O8gyB8YhsJkCInGHii 4dMkq1RVIb7tSrFX9HCpiITJpkebYNDWOxzC/58QYi6N1fiGsK uxmLxOAhjYJKTDciNbrEuV8ZKv0Gd87Yg/wfKkNrXluU0Y0UAA AARwmwc3W8HGiIPHL7lj5fiKmbe60=             [Name] IsDefaultServiceProfile    [Data] true          As jabber now has all the required information it will start the login process: 2015-03-22 19:22:36,704 INFO  [0x0000085c] [s\adapters\imp\StackManagerImpl.cpp(101)] [imp.service] [IMPStackCap::StackManagerImpl::doInitialise] - Entry 2015-03-22 19:22:36,704 INFO  [0x0000085c] [resets/adapters/imp/components/Log.h(37)] [csf-unified.log.h] [IMPStackCap::JabberWerxHandlerConnector<class JabberWerxCPP::JWLogger>::registerHandler] - Passing location C:\Users\admin\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs\JabberWerxCpp to Jabberwerx as logging dir for .wbt files 2015-03-22 19:22:36,704 INFO  [0x0000085c] [s\adapters\imp\StackManagerImpl.cpp(107)] [imp.service] [IMPStackCap::StackManagerImpl::doInitialise] - LoginMgr started...   2015-03-22 19:22:36,704 DEBUG [0x00000f58] [ce\src\services\impl\EventStore.cpp(435)] [csfunified.telemetry.EventStore] [telemetry::EventStore::markEventSubmittable] - Adding common data fields to Event tree. 2015-03-22 19:22:36,704 DEBUG [0x00000f58] [ce\src\services\impl\EventStore.cpp(437)] [csfunified.telemetry.EventStore] [telemetry::EventStore::markEventSubmittable] - Got value for osVersion: 'Win7SP1.0' 2015-03-22 19:22:36,704 DEBUG [0x00000f58] [ce\src\services\impl\EventStore.cpp(441)] [csfunified.telemetry.EventStore] [telemetry::EventStore::markEventSubmittable] - Got value for productName: 'J4W' 2015-03-22 19:22:36,704 DEBUG [0x00000f58] [ce\src\services\impl\EventStore.cpp(443)] [csfunified.telemetry.EventStore] [telemetry::EventStore::markEventSubmittable] - Got value for productVersion: '10.6.1.55781' 2015-03-22 19:22:36,704 DEBUG [0x00000f58] [ce\src\services\impl\EventStore.cpp(445)] [csfunified.telemetry.EventStore] [telemetry::EventStore::markEventSubmittable] - Got value for platformInfo: 'Intel(R) Xeon(R) CPU           X7560  @ 2.27GHz'   2015-03-22 19:22:38,966 DEBUG [0x0000085c] [sets\adapters\imp\components\Log.cpp(32)] [JabberWerx] [IMPStackCap::Log::log] - [XmppSDK.dll]: #0, CXmppClient::onConnect 2015-03-22 19:22:38,966 INFO  [0x0000085c] [sets\adapters\imp\components\Log.cpp(33)] [JabberWerx] [IMPStackCap::Log::log] - [XmppSDK.dll]: CXmppClient::onConnect, JabberServerInfo, host: 10.106.112.7, port: 5222 2015-03-22 19:22:38,966 DEBUG [0x0000085c] [sets\adapters\imp\components\Log.cpp(32)] [JabberWerx] [IMPStackCap::Log::log] - [XmppSDK.dll]: #0, CXmppClient::onStreamEvent ,CXmppClient::onStreamEvent, ConSessionState_Starting   2015-03-22 19:22:38,966 INFO  [0x0000085c] [sets\adapters\imp\components\Log.cpp(33)] [JabberWerx] [IMPStackCap::Log::log] - [LoginMgr.dll]: #0, CLoginContext::InitCupHAHosts ha, soap-servers:10.106.112.7 2015-03-22 19:22:38,966 DEBUG [0x0000085c] [sets\adapters\imp\components\Log.cpp(32)] [JabberWerx] [IMPStackCap::Log::log] - [LoginMgr.dll]: #0, CLoginMgrConnectionPointContainer::Fire_OnLoginSuc cess login, OnLoginSuccess 2015-03-22 19:22:38,966 INFO  [0x0000085c] [sets\adapters\imp\components\Log.cpp(33)] [JabberWerx] [IMPStackCap::Log::log] - [JabberWerxCPP.DLL]: JWLoginSink::OnLoginSuccess, autologin:0 2015-03-22 19:22:38,966 DEBUG [0x0000085c] [ts\adapters\imp\components\Login.cpp(58)] [imp.service] [IMPStackCap::Login::OnLoginSuccess] - Entry 2015-03-22 19:22:38,966 INFO  [0x0000085c] [ts\adapters\imp\components\Login.cpp(60)] [imp.service] [IMPStackCap::Login::OnLoginSuccess] - ************************************************** ************** 2015-03-22 19:22:38,966 INFO  [0x0000085c] [ts\adapters\imp\components\Login.cpp(61)] [imp.service] [IMPStackCap::Login::OnLoginSuccess] - OnLoginSuccess (autoLogin: false) 2015-03-22 19:22:38,966 INFO  [0x0000085c] [ts\adapters\imp\components\Login.cpp(62)] [imp.service] [IMPStackCap::Login::OnLoginSuccess] - ************************************************** ************** 2015-03-22 19:22:38,966 DEBUG [0x0000085c] [ets\adapters\imp\components\Login.cpp(0)] [imp.service] [IMPStackCap::Login::OnLoginSuccess] - Exit     Configuring Excluded services:   Jabber for windows excluded services can be configured using  bootstrap file or in jabber-config.xml for jabber windows clients.   Below is the sample file for jabber for windows:   <?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Policies> <VoiceServicesDomain>apps.com</VoiceServicesDomain > <ServiceDiscoveryExcludedServices>WEBEX</ServiceDi scoveryExcludedServices> </Policies> </config>   Reference:  http://www.cisco.com/c/en/us/td/docs/voice_ip_com m/jabber/Windows/9_7/JABW_BK_C4C679C9_00_cisco-jab ber-for-windows-97/JABW_BK_C4C679C9_00_cisco-jabbe r-for-windows-97_chapter_0101.html#JABW_RF_A47E40C 4_00   Note: If jabber windows never connected internally and first time login tried over edge, the excluded services will not be considered as if there is no prior jabber-config.xml file downloaded. Can try login to internally first to get the config file downloaded and from next time excluded services will be considered over edge.   For MAC, IPhone and Andriod devices URL configuration can be done to exclude services:   1. Install jabber 2. Send the URL to the user via email 3. Click on the URL, jabber will be launched and URL information will be given to jabber for service discovery   Sample URL: ciscojabber://provision?ServicesDomain=apps.com&Vo iceServicesDomain=apps.com&ServiceDiscoveryExclude dServices=WEBEX ... View more

Introduction: This document describes most commonly faced IM and Presence issues and their respective logs required for TAC troubleshooting. Note: Verify that the services involved according to the below mentioned scenario are set to the "Debug" level from the IM and Presence serviceability page, when the issue present or when you reproduce the problem It is always better to collect logs from all the nodes involved This document specifically talks about IM&P server logs, but where ever jabber is involved, please ensure to collect jabber problem report too Include below information to track the specific event Problem description or Issue Scenario Time stamp when issue occurred or reproduced Scenario 1: Jabber login failure Client profile agent logs Cisco XCP authentication Tomcat security logs Scenario 2: Chat failure XCP Connection manager XCP router Scenario 3: Presence status fails to update XCP connection manager XCP router Presence engine Scenario 4 : "On a call" (or) phone presence status failure CCM logs from CUCM Presence engine XCP router XCP connection manager Scenario 5: High Availability Server recovery manager Cluster Manager logs "utils ha status" output from CLI Scenario 6: Chat rooms (or) Persistent chat XCP text conferencing manager XCP connection manager XCP router Scenario 7: Exchange Integration for Calendaring Presence engine Scenario 8 : Inter-Cluster Peering Intercluster sync agent AXL web service Tomcat Tomcat security logs Scenario 9 : High CPU / Memory utilization Show process using-most cpu Show process using-most memory Show process load Utils diagnose test RIS DC and Perfmon logs Event viewer – Application and system logs Scenario 10 : Service restart with core dump Utils core active list Utils core active analyze <core file name from previous command> Logs of the service which restarted or crashed Scenario 11 : DRF Backup and restore DRF Master DRF Agent Component specific failure logs for the backup / Restore Scenario 12: Message Archeive failure XCP router XCP message archiver Scenario 13: Managed file transfer failure XCP File Transfer Manager service Scenario 14 : SIP federation XCP SIP federation connection manager SIP proxy Presence engine XCP connection manager XCP router Scenario 15 : XMPP federation XCP connection manager XCP router Presence engine XMPP federation connection manager Below are the screenshot from RTMT with few important log fields highlighted:     Logs can also be collected from Command line interface of the server. The below document has location deatils for specific services: https://supportforums.cisco.com/document/12221116/cisco-unified-presence-server-imp-server-log-location-cli RTMT trace collection procedure: https://supportforums.cisco.com/document/12489131/tech-note-taking-trace-unified-cm-using-rtmt                     supportforums.cisco.com/docs/DOC-29963#sthash.X3oQ2dxU.dp ... View more

1. Make sure CUCM is reachable from the jabber client PC. If the server is configured as hostname or FDQN under System – Server of CUCM administration, verify on the reachability towards the same. Verify on the DNS configuration if there is reachability issue while using hostnames / FQDN.   2. Verify on the TFTP configured for the jabber. TFTP should be configured in IM&P server administration   Navigate to IM&P admin page --- Application --- Legacy Clients --- Settings. This should point to the CUCM server, which has the TFTP service running.     3. Verify on the CCMCIP configuration:   Navigate to IM&P admin page --- Application --- Legacy Clients --- CCMCIP. This should be pointing to the CUCM server, which has the Cisco Call Manager IP phone service running.     Make sure the jabber user is associated with the CCMCIP profile.   4. Check the SIP Profile for the “Timer Register Delta” Configured. From the CSF device, find out the SIP profile configured.   Navigate to CUCM admin page --- Device --- Device Settings --- SIP Profile --- Find the SIP Profile applied on the CSF device --- look for “Timer Register Delta”     The default value for this is 5 and having a large value here would affect the jabber windows registration. Value between 5 to 10 is normal for a proper registration on a stable network.   5. The CSF line should have the end user associated with it. Find the CSF device configured for the user, navigate to DN configured à Verify that the end user is associated to it.       ... View more

Introduction   There is a typical import option available from CUPS, which can import contacts to jabber for window buddy list. Also with JFW 9.6 version, contacts can be imported to buddy list from the jabber client itself in the form .xml file.   Using Bulk Import option in CUPS:           Possible from CUPS version 8.6.4 onwards   Step 1: Create a .CSV file in the below format. The below shows a sample file:   User ID, User Domain, Contact ID, Contact Domain, Nickname, Group Name test7, APP.COM, test3, APP.COM, Sample3, General test8, APP.COM, test3, APP.COM, Sample3, General   With the above file, User test3 will be added to the buddy list of test7 and test8   Step 2: Upload the .csv file to CUPS. CUPS admin page -- Bulk Administration -- upload/download files -- Add new -- Browse the .csv file -- Select the target as "CUP Users" -- Select transaction type as "Update CUP Users - Custom File" -- Save   Step 3: Execute the file uploaded: Bulk administration —-- Contacts list —-- update —-- select the file uploaded —-- run immediately   Step 4: Check the status of file: Bulk administration —-- job scheduler -- find the job added —and check the status —-- Will be added if the job is successful   Note : The file can be created in a normal notepad and can be saved as .csv file The users (user3, user7 and user8) should be assigned to a node for the bulk job to success   Using Jabber .xml file to import contact:   Step1 : Create .xml file. Below is the sample file <?xml version="1.0" encoding="utf-8" ?> <buddylist> <group> <gname>Sample Group 1</gname> <user><uname>user1@APP.com</uname><fname>Sample User 1</fname></user> <user><uname>user2@APP.com</uname><fname>Sample User 2</fname></user> </group> <group> <gname>Sample Group 2</gname> <user><uname>user3@APP.com</uname><fname>Sample User 3</fname></user> </group> </buddylist>   With the above file, user1 and user2 will be added to the group Sample group1 Also user 3 will be added to the group Sample group2 This file also create groups Sample group 1 and 2 Here uname will the IM address of the user being added   Step 2: Login to jabber client to which you like to import contact   Step 3: Click on file -- import contacts -- select the xml file created -- open   Now the contacts will be added to buddy list   ... View more