Jabber for Windows 9.1(3) - All network connections fail at least once a day

Hi,
We have Jabber for Windows 9.1(3) running, with the MSI 3.2 installed as well.
At least once a day my computer stops making network connections (Outlook gets disconnected, Internet Explorer cannot connect to Google, Chrome also fails). When I shut down and restart Jabber all network IO resumes.
Has anyone seen this behavior?
I've made two problem reports for this. Is anyone interested?
Regards,
Erik Tamminga
PS. Server side we're running all 9.1 versions.

We had the same issue and logged a TAC case, and the final result was to uninstall media services as mentioned above. Obviously now you no longer have desk phone video.
The new 9.2 beta has a new media service version, and the rollout of the new 9.2 client is mid march I believe, so hopefully this rectifies the problems, because if it doesn't I think this would not be a good thing for Jabber as a product unfortunately.
Cheers

Similar Messages

Jabber for Windows - periodically tries to re-install and fails

Jabber 9.1
CUCM 7.1.3
Windows 7 32 bit
Cisco Presence 8.0.2.10000-30
Jabber for windows - periodically tries to re-install and fails. After install Jabber works for awhile but then when trying to open another program(Outlook, IE Explorer) it tries to re-install. If I go to the directory where the install files are and do repair it works. This seems like a conflict with another application.
I see this in the Windows application event log:
Detection of product '{4EB9D7DD-65B5-44ED-B877-CE3EF9B4530F}', feature 'Cisco_Jabber_Files', component '{7CB949BE-2270-4992-9C4C-8FDDB90F6FE2}' failed. The resource 'C:\Program Files\Cisco Systems\Cisco Jabber\JabberMeeting\DesktopShare\atgpcdec.dll' does not exist.
Jabber 9.1
CUCM 7.1.3
Windows 7 32 bit
Cisco Presence 8.0.2.10000-30

Hi,
Do you have WebEx Productivity plugin installed on the machine? I can reproduce this problem after exiting Jabber, creating a One-click meeting from Outlook and restarting Jabber. Please provide further information to help me open a defect.
- What was the version of Jabber on this machine prior to 9.1.0?
- What is the version of the WebEx productivity tool plugin (if it is installed)?
- Is there a particular sequence that you can follow to reproduce it everytime?
Thanks,
Maqsood

Jabber for Windows 9.0.1 on WebEx Connect Admin

When will the Jabber for Windows 9.0.1 client be on the WebEx Connect Admin web site for controlled upgrade of the clients?

Jabber for Windows 9.0(1) will not be posted automatically for all customers.
An internal communication will be issued to all internal CSM's and PSM's in the next couple of days explaining the exact procedure for requesting access to the client and how to raise the ops request to make it available for the customer org in question ... so reach out to the your Partner manager to understand that procedure and to enable access for your customers.
Regards,
John

Call/video not working between Cisco jabber for Windows and VCS control C40s

Hello,
I've been struggling with no luck how to make a call using Cisco Jabber for Windows 9.6.0 registered to CM 8.6.2 with intercluster ICT to another CM 8.6.2 where we have a VCS Control 7.0.2 via GK H225, and all C40s are registered as H.323.
The VCS has interworking between H323 and SIP, however not sure if there is any problem with that. Assuming it is ok, not sure either if I'm facing any interoperability issue because in my remote site I have C40 (H323 registered at VCS and SIP listening mode) and cisco jabber for windows which is SIP based.
If is not possible, would I be able to change my C40 from H323 to SIP at VCS, or have both H323/SIP registered at VCS? If so, will I need to change as well instead of GK I'll have to establish a SIP Trunk between the CM and VCS?
Another thing I do not believe either I would be able to have one VCS connected with two clusters, right?
I'm just trying to find a solution in case my current topology is not compatible, but feel free if you have any better idea to make it work.
Anyway here is what is happening:
When I make a call from my cisco jabber windows to C40 using alias number. The call is being redirected just fine to the C40 and it rings, however when someoene or the auto answer picks it up, the call dropped right away.
However, if I enabled the MTP in my CSF device, the call gets longer before dropping. I was even able to see my jabber " start video" turns green, before was grayed out all the time and the call dropped faster. I hear a fast busy tone.
I'm able to provide SDI traces, logs, diagnostic sip/h323 calls from VCS in order to know for sure if this is an incompatible issue or something I can workaround.
Let me know if someone of you are interested in read these logs or could point me on the right direction.
Thanks!

Ok,
I have looked at both logs. I have to mentinon though that you didnt
provide the log that shows the h323 setup between cucm and the VCS. This
is most likely because the call originated from a different cucm than
the ones you provided the logs from.
The call would have orginated from the first cucm in the cucm group of
this trunk: Name=RL_TRUNK_VIDEO
The cucm ip will be : 10.252.53.10.
This is the VCS log that confirms where the h323 request originated
from:
pr 10 22:50:29 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:29,187"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="54000"
Received RAS PDU:
Having said that here is my analysis of the logs that you sent..
Jabber sent an INVITE to CUCM and advertised all the codecs (audio and
video it can support)..
Observer that Jabber says it doesnt support G729 anexB
21:55:16.576 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message
from 10.223.20.73 on port 54677 index 90661 with 2220 bytes:
[862370,NET]
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/TCP 10.223.20.73:54677;branch=z9hG4bK000029d3
From: "4122107" <sip:[email protected]>;tag=00059a3c78000011000070b0
-00000e65
To: <sip:[email protected]>
Call-ID: [email protected]
Max-Forwards: 70
Date: Fri, 11 Apr 2014 01:55:16 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CSF/9.4.1
m=audio 19252 RTP/AVP 0 8 18 105 104 101
c=IN IP4 10.223.20.73
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
m=video 28878 RTP/AVP 97
c=IN IP4 10.223.20.73
++++Now lets observer the capabilites exchange during h245 negotiation
between cucm and VCS++++
Here CUCM advertises its caps to VCS (afterreceiving caps from VCS)
Note that G729A, G729AB, G729 is all advertised..
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,017"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : terminalCapabilitySet
capabilityTableEntryNumber 2,
       capability receiveAudioCapability :
g729wAnnexB : 6
       capabilityTableEntryNumber 3,
   capability receiveAudioCapability : g729AnnexAwAnnexB : 6
       capabilityTableEntryNumber 4,
       capability
receiveAudioCapability : g729 : 6
capabilityTableEntryNumber 5,
       capability receiveAudioCapability :
g729AnnexA : 6
++++++
After doing MSD (master slave determination, we move to the OLC phas e..
Here we see that the far end..c40 wants to use G729AB for media++++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,783"
Module="network.h323" Level="DEBUG": Src-ip="10.224.114.11" Src-
port="11163"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
   forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
     dataType audioData :
g729AnnexAwAnnexB : 20,
     multiplexParameters
h2250LogicalChannelParameters :
+++Next VCS sends G729AB as the codec to use to CUCM+++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,784"
Module="network.h323" Level="DEBUG": Dst-ip="10.252.53.10" Dst-
port="45660"
Sending H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
   forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
     dataType audioData :
g729AnnexAwAnnexB : 20,
     multiplexParameters
h2250LogicalChannelParameters :
++++The next thing we get is an OLC reject from CUCM and this is where
th call drops++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= response : openLogicalChannelReject :
forwardLogicalChannelNumber 1,
   cause dataTypeNotSupported : NULL
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="INFO": Dst-ip="10.224.114.11" Dst-
port="11163"
Detail="Sending H.245 OpenLogicalChannelRejResponse
+++We then receive a call release from cucm with cause code of 47:
resource unavailable++++
Apr 10 22:50:32 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:32,365"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="50913"
Received H.225 PDU:
Q931
   Message Type: Release
Complete
   Call reference flag: Message sent from originating side
Call reference value: 0x7b
   Info Element : Cause
     Location: Usr
   Cause Value: Resource unavailable
   Info Element : User User
   Length = 22
Suggestions:
Change the region setting between the ICT trunk to VCS and Jabber to use
G711 and test again.

No Audio on either end Cisco Jabber for Windows over Cisco AnyConnect

Our telephony staff is replacing our aging/unsupported VoIP system with a Cisco system and as the network tech, I'm trying to get Jabber for Windows to work over our AnyConnect VPN client. Jabber to Cisco phone and Jabber to Jabber calls work fine within our LAN.
However, when I take a laptop to a separate internet connection and connect to the network via the VPN, I can't get any audio to pass across the system, in either direction. If I call a phone on our LAN using the Jabber client (via AnyConnect), the phone rings and when I answer it, it's just dead air on both ends. If I reverse the process, calling from the phone to the Jabber client, the same thing, Jabber client rings, but dead air both ways once I answer.
Things I can do from the laptop over the VPN connection:
I'm able to get to the phone's web interface using that same laptop.
I can ping the phone as well. In fact, the VPN profile I'm using has full access to the entire VoIP Vlan including all IP traffic (all ~65,000 ports).
Searching the address book also works fine. I can search for staff and it's pulling directly from our Active Directory environment.
Is there any special settings on the firewall that I need to setup to allow the voice traffic (which I assume is RTP traffic)? I tried to add a service policy for RTP traffic, but that didn't seem to work...unless I built it wrong.
Jabber for Windows - 10.6.0
Cisco Anyconnect - 3.1.06079
Cisco 5515-x ASA - 9.2

I was able to resolve this on my own. I thought that SIP traffic needed to be inspected via the global inspection policy in order for it to pass through the firewall. I ran into the same issue with ICMP traffic from an Anyconnect client to LAN devices. I had to enable ICMP in that policy for us to be able to ping LAN devices over the VPN tunnel. So when I saw that SIP was already being inspected by this policy, I moved on looking for other solutions. Then I stumbled deep within a Google search (almost hit the end of the Internet doing so) where someone mentioned that SIP shouldn’t be inspected by that policy. So I unchecked it and bam! Voice is now working over the anyconnect client to phones on the LAN.

Cisco Jabber for Windows - Anti-Virus Software

Hello,
Cisco Jabber for Windows could not resolve outlook contacts, when a client has installed McAffee Anti-Virus Software.
Is there any documentation available, how to setup a Anti-Virus Software, to get Cisco Jabber for Windows running?
Cisco Jabber for Windows Version 9.2.4 Build 4528
Outlook 2013
Thanks
Alex

this is all what we mention about antivirus; http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_J6915A59_00_jabber-windows-server-setup/JABW_BK_J6915A59_00_jabber-windows-server-setup_chapter_00.html
Some antivirus or firewall applications, such as Symantec EndPoint Protection, block inbound CDP packets, which disables desk phone video capabilities. You should configure your antivirus or firewall application to allow inbound CDP packets. See the following Symantec technical document for additional details about this issue: Cisco IP Phone version 7970 and Cisco Unified Video Advantage is Blocked by Network Threat Protection.
with that being said; we probably would like to get the jabber process excluded from the antivirus list so that it allows for inbound MAPI communication as that is what is used for quering for the outlook contact.
The only process that ever runs from Jabber for windows is "CiscoJabber.exe" which is located in the following path:
C:\Program Files (x86)\Cisco Systems\Cisco Jabber
i hope this helps.

Jabber for Windows 10.5 and global redundancy

Hi All,
I implement J4W 10.5 in a full redundant environment, that contains:
- 3 x CUCM 10.5
- 2 x Unity Connection 10.5
- 2 x IM&P 10.5
- 2 x Expressway-C 8.2.2
- 2 x Expressway-E 8.2.2
After testing, I notice that the redundancy/failover does not act the same way depending the product, sometime no.
As it is not clearly stated in the documentation, what is clearly supported as automatic failover, and what's not, when using Jabber for Windows 10.5?
In my first test, I saw that Jabber does not support failover with UnityConnection: if the primary peer is down, no more voicemail on Jabber.
If jabber run in Mobile and Remote Access, and the Expressway where it's conencted goes down, it doesn't switch to the other peer.
It will be good to have a document that relate all the redundancy and failover support with Jabber, what can we expect during the failover process.
It will help a lot of people.
Thanks
Gabriel

Yep, that's what I did now.
But keep in mind this is not really explained, even if crossing all the documentations.
There is no document explaining what behaviour to expect in Jabber in case of redundancy of all the UC components.
For the CUCM, it's not clear, and nothing is mentionned in case of MRA.
IM&P is documented, but nothing for MRA.
Expressays states about redundancy, but the behaviour to expect is not. Same for XMPP federation, no idea.
UnityConnection as well, nothing is explained.

Using CUPC7/CUPC8.6 and Jabber for windows...unable to access voicemail.

Using CUPC7/CUPC8.6 and Jabber for windows...unable to access voicemail.
Setup includes CUCM9.0, Unity Connection 9.0, Presence 9.0....
steps taken to configure(and results acheived)
1-users created locally on CUCM and Enabled for IM and Presence.
2-able to login to clients (CUPS7/8.6 and Jabber) but getting error Voicemail Error. The server has rejected the provided credentials. [1903]
in order to verify there is nothing wrong with the credentials...i checked on unity and i am sure it's the PIN(12345) i need to use .
Can Anyone help me out here...Thanks in advance.

It's not looking for your PIN - that is only used over DTMF-based interactions - it's looking for your CUC password. If the mailbox is synced from LDAP and you have LDAP Auth enabled on CUC, then this would be your AD password. If it's synced over AXL, not synced at all, or LDAP synced but without Auth, then there will be an alphanumeric password field on the mailbox under Edit > Change Passwords.
Please remember to rate helpful responses and identify helpful or correct answers.

Jabber for windows 9.2.6 client

hi
i have just upgraded some of my cisco jabber for windows clients to the latest release 9.2.6 (upgraded from 9.2.3)
i noticed that the first time the client startsup i get certificate warnings for our CUCM-PUB, SUB, CUC device and CUPS server. (all version 8.6)
all use the standard cisco SSL certificate (have not deployed 3rd party SSL certificates)
is there a way to get all these certificates trusted by the client machines, it has never prompted me before and works fine with 9.2.3
on the mac clients i have added them to the keychain when i first deployed the clients (manual job) but i like to see if i can automate this for my 30 windows clients (the users will not click on this themselves and will use it as an excuse not to load jabber (they don't like the call window pop ups but that is something for jabber 9.6 client
any idea how to get these certificates trusted by the windows computers (we have an 2008 r2 active directory so could do something with an group policy and or use our own internal windows certificate authority)
many thankss

when i run show web-security i get this
admin: show web-security
Version: V3
Serial Number: 441991719279266168307794
SignatureAlgorithm: SHA1withRSA (1.2.840.113549.1.1.5)
Issuer Name: CN=mydomain-CA, DC=mydomain, DC=com
Validity From: Mon Oct 28 15:32:30 GMT 2013
           To:   Wed Oct 28 15:32:30 GMT 2015
Subject Name: CN=uk-cucm-pub.mydomain.com, OU=IT, O=mydomain, L=London, ST=London, C=GB
Key: RSA (1.2.840.113549.1.1.1)
    Key value: 3082010a0282010100d2a01565f2533b3602158e83fede75fef2751aa957902e0e556e814bb7e6aaed5d5138b6cf3d87d59f5c4be2740ab9f5dc3318a34ab551daa817f6ccd562c3c628f75ef278ed81bbd816ec44d178da86850c3bdd74b727cde092616e7674785c45efc88e98ba4d89da97fc92ac2901f41c23ed692460a1d64c171a6d5613dfe2e1bab2b82f5f1a5d9fe55b067e858a0d2cd48a8be59c9e54cccdac1238acd2738128626252b3e69198fc852217f930d6cd2bc6a3481452be355bae6c6ccfc7d5e86a39ff7b0304cfb53e1555ccc8c4224cf661f912946b4e0db2926991d704f65cd92546155048cecb0f11c5046f743434d1577cbb4c175611acdf2fbf33bfb30203010001
Extensions: 7 present
     Extension: ExtKeyUsageSyntax (OID.2.5.29.37)
     Critical: false
     Usage oids: 1.3.6.1.5.5.7.3.1,
     Extension: KeyUsage (OID.2.5.29.15)
     Critical: false
     Usages: digitalSignature, keyEncipherment,
     Extension: SubjectKeyIdentifier (OID.2.5.29.14)
     Critical: false
     keyID: 8e9c68b7e4acc73c6734b1df3d9ca0a7ccb7183d
     Extension: AuthorityKeyIdentifier (OID.2.5.29.35)
     Critical: false
     keyID: 88c4622540d7efbbdac1af207249c77c287f9c6c
     Extension: CRLDistributionPoints (OID.2.5.29.31)
     Critical: false
     distributionPoint
        fullName: 1 names
          1) ldap:///CN=mydomain-CA,CN=UK-CA,CN=CDP,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=mydomain,DC=com?certificateRevocationList?base?objectClass=cRLDistributionPoint (uri)
     Extension: AuthorityInfoAccessSyntax (OID.1.3.6.1.5.5.7.1.1)
     Critical: false
     accessMethod: 1.3.6.1.5.5.7.48.2
     accessLocation: ldap:///CN=mydomain-CA,CN=AIA,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=mydomain,DC=com?cACertificate?base?objectClass=certificationAuthority (uri)
     Extension: (OID.1.3.6.1.4.1.311.20.2)
     Critical: false
     Value: 04141e12005700650062005300650072007600650072 ]
Signature:
lots of text
]-----BEGIN CERTIFICATE-----
certificate characters
-----END CERTIFICATE-----
no sign of subject alternate names in those details so am not sure how i would change this
on your cucm system are your host details listed as ip address or host name, mine are listed as ip address and perhaps the certificate mismatch is caused by these settings?
Host Name/IP Address Description
10.33.2.20 PUBLISHER
10.33.2.21 SUBSCRIBER 1
if the cucm servers were listed as uk-cucm-pub or uk-cucm-pub.mydomain.com and uk-cucm-sub.mydomain.com perhaps it would accept the certificates
web-security
Version: V3
Serial Number: 441991719279266168307794
SignatureAlgorithm: SHA1withRSA (1.2.840.113549.1.1.5)
Issuer Name: CN=Accel-CA, DC=accel, DC=com
Validity From: Mon Oct 28 15:32:30 GMT 2013
           To:   Wed Oct 28 15:32:30 GMT 2015
Subject Name: CN=uk-cucm-pub.accel.com, OU=IT, O=Accel, L=London, ST=London, C=GB
Key: RSA (1.2.840.113549.1.1.1)
    Key value: 3082010a0282010100d2a01565f2533b3602158e83fede75fef2751aa957902e0e556e814bb7e6aaed5d5138b6cf3d87d59f5c4be2740ab9f5dc3318a34ab551daa817f6ccd562c3c628f75ef278ed81bbd816ec44d178da86850c3bdd74b727cde092616e7674785c45efc88e98ba4d89da97fc92ac2901f41c23ed692460a1d64c171a6d5613dfe2e1bab2b82f5f1a5d9fe55b067e858a0d2cd48a8be59c9e54cccdac1238acd2738128626252b3e69198fc852217f930d6cd2bc6a3481452be355bae6c6ccfc7d5e86a39ff7b0304cfb53e1555ccc8c4224cf661f912946b4e0db2926991d704f65cd92546155048cecb0f11c5046f743434d1577cbb4c175611acdf2fbf33bfb30203010001
Extensions: 7 present
     Extension: ExtKeyUsageSyntax (OID.2.5.29.37)
     Critical: false
     Usage oids: 1.3.6.1.5.5.7.3.1,
     Extension: KeyUsage (OID.2.5.29.15)
     Critical: false
     Usages: digitalSignature, keyEncipherment,
     Extension: SubjectKeyIdentifier (OID.2.5.29.14)
     Critical: false
     keyID: 8e9c68b7e4acc73c6734b1df3d9ca0a7ccb7183d
     Extension: AuthorityKeyIdentifier (OID.2.5.29.35)
     Critical: false
     keyID: 88c4622540d7efbbdac1af207249c77c287f9c6c
     Extension: CRLDistributionPoints (OID.2.5.29.31)
     Critical: false
     distributionPoint
        fullName: 1 names
          1) ldap:///CN=Accel-CA,CN=UK-CA,CN=CDP,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=accel,DC=com?certificateRevocationList?base?objectClass=cRLDistributionPoint (uri)     [
     Extension: AuthorityInfoAccessSyntax (OID.1.3.6.1.5.5.7.1.1)
     Critical: false
     accessMethod: 1.3.6.1.5.5.7.48.2
     accessLocation: ldap:///CN=Accel-CA,CN=AIA,CN=Public%20Key%20Services,CN=Services,CN=Configuration,DC=accel,DC=com?cACertificate?base?objectClass=certificationAuthority (uri)
     Extension: (OID.1.3.6.1.4.1.311.20.2)
     Critical: false
     Value: 04141e12005700650062005300650072007600650072 ] Signature:
0000: 90 e8 32 00 2e f3 58 ec 18 20 6d 54 0a 49 9c ce [..2...X.. mT.I..]
0010: 94 90 02 6e 2f 15 1e f2 c3 6c 45 96 14 8e ff 25 [...n/....lE....%]
0020: 39 db 50 08 03 3b 48 a3 c7 69 7a 03 76 d1 e3 3d [9.P..;H..iz.v..=]
0030: 73 94 08 7c d3 13 f2 7c 58 ff ba 26 47 ed 6a 50 [s..|...|X..&G.jP]
0040: 9d 80 f8 64 cc dd 34 9f 95 32 3f 7f 32 04 f4 8b [...d..4..2?.2...]
0050: 86 e3 9d 23 03 06 06 ad f2 1b e0 0a a6 ed c0 3d [...#...........=]
0060: d4 dd 57 0f 61 d3 2b 14 d1 d0 3e c4 3a e3 df ac [..W.a.+...>.:...]
0070: c7 b8 dd 37 ba e2 e6 aa 35 a1 9b 7d 27 b8 d0 5a [...7....5..}'..Z]
0080: d9 cc d9 89 90 e0 72 de b1 32 4d d2 fc c8 2e c0 [......r..2M.....]
0090: a1 f9 57 8e b7 9d 1d 00 d8 a8 4d 26 ed c6 92 f6 [..W.......M&....]
00a0: 99 7a 1c ee 58 8d 76 20 7b af a1 54 0b 57 c3 d3 [.z..X.v {..T.W..]
00b0: 92 1f 64 d0 04 22 ae 17 c2 2a 1d d1 83 e0 c3 85 [..d.."...*......]
00c0: 67 4e 94 67 65 e8 e2 39 87 ef 78 f7 41 7e bd 34 [gN.ge..9..x.A~.4]
00d0: 79 8d be ae 45 5c 56 73 1d 6c 02 bf 3a 93 b4 a9 [y...E\Vs.l..:...]
00e0: f8 80 76 f1 ad 42 6e 42 cd 54 00 1e ca c5 b8 98 [..v..BnB.T......]
00f0: 05 a4 dd 3c 89 47 7b 4a 61 af 4b 32 2c 0c 96 a6 [...<.G{Ja.K2,...]]-----BEGIN CERTIFICATE-----
MIIFOjCCBCKgAwIBAgIKXZhrSwAAAAAAUjANBgkqhkiG9w0BAQUFADA/MRMwEQYK
CZImiZPyLGQBGRYDY29tMRUwEwYKCZImiZPyLGQBGRYFYWNjZWwxETAPBgNVBAMT
CEFjY2VsLUNBMB4XDTEzMTAyODE1MzIzMFoXDTE1MTAyODE1MzIzMFowbDELMAkG
A1UEBhMCR0IxDzANBgNVBAgTBkxvbmRvbjEPMA0GA1UEBxMGTG9uZG9uMQ4wDAYD
VQQKEwVBY2NlbDELMAkGA1UECxMCSVQxHjAcBgNVBAMTFXVrLWN1Y20tcHViLmFj
Y2VsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANKgFWXyUzs2
AhWOg/7edf7ydRqpV5AuDlVugUu35qrtXVE4ts89h9WfXEvidAq59dwzGKNKtVHa
qBf2zNViw8Yo917yeO2Bu9gW7ETReNqGhQw73XS3J83gkmFudnR4XEXvyI6Yuk2J
2pf8kqwpAfQcI+1pJGCh1kwXGm1WE9/i4bqyuC9fGl2f5VsGfoWKDSzUiovlnJ5U
zM2sEjis0nOBKGJiUrPmkZj8hSIX+TDWzSvGo0gUUr41W65sbM/H1ehqOf97AwTP
tT4VVczIxCJM9mH5EpRrTg2ykmmR1wT2XNklRhVQSM7LDxHFBG90NDTRV3y7TBdW
EazfL78zv7MCAwEAAaOCAgkwggIFMBMGA1UdJQQMMAoGCCsGAQUFBwMBMAsGA1Ud
DwQEAwIFoDAdBgNVHQ4EFgQUjpxot+SsxzxnNLHfPZygp8y3GD0wHwYDVR0jBBgw
FoAUiMRiJUDX77vawa8gcknHfCh/nGwwgcIGA1UdHwSBujCBtzCBtKCBsaCBroaB
q2xkYXA6Ly8vQ049QWNjZWwtQ0EsQ049VUstQ0EsQ049Q0RQLENOPVB1YmxpYyUy
MEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
YWNjZWwsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmpl
Y3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludDCBuAYIKwYBBQUHAQEEgaswgagw
gaUGCCsGAQUFBzAChoGYbGRhcDovLy9DTj1BY2NlbC1DQSxDTj1BSUEsQ049UHVi
bGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlv
bixEQz1hY2NlbCxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNz
PWNlcnRpZmljYXRpb25BdXRob3JpdHkwIQYJKwYBBAGCNxQCBBQeEgBXAGUAYgBT
AGUAcgB2AGUAcjANBgkqhkiG9w0BAQUFAAOCAQEAkOgyAC7zWOwYIG1UCkmczpSQ
Am4vFR7yw2xFlhSO/yU521AIAztIo8dpegN20eM9c5QIfNMT8nxY/7omR+1qUJ2A
+GTM3TSflTI/fzIE9IuG450jAwYGrfIb4Aqm7cA91N1XD2HTKxTR0D7EOuPfrMe4
3Te64uaqNaGbfSe40FrZzNmJkOBy3rEyTdL8yC7AoflXjredHQDYqE0m7caS9pl6
HO5YjXYge6+hVAtXw9OSH2TQBCKuF8IqHdGD4MOFZ06UZ2Xo4jmH73j3QX69NHmN
vq5FXFZzHWwCvzqTtKn4gHbxrUJuQs1UAB7KxbiYBaTdPIlHe0phr0syLAyWpg==
-----END CERTIFICATE-----

Jabber for Windows openLDAP and Deskphone Control

Hello all
I have a new install of 9.1 CUCM, with CUCM IM and Presence. I'm trying to get Jabber 4 windows functioning with an openLDAP directory, and also get Deskphone control working. I suspect i missed something with the configuration as this 9.1 interface is a little different than i'm used to.
First of all, does the concept of a Jabber-Config.xml still apply to a 9.1 install or does the "Service Profile Configuration" in the CUCM interface write the Jabber-config.xml file for you? If my customer uses openLDAP for their LDAP how should I configure the "Service Profile" or do I still use a jabber-config.xml file?
I have successfully tied openLDAP into CUCM with Authetication and brought the users into CUCM. I tested Authentication by logging into the End user page for both CUCM and the CUP server so I know authenticaiton is working. I can login to Jabber but when i click on Help "connection Status" it shows me only connected to "PRESENCE" and "OUTLOOK ADDRESS BOOK" my "Directory", and DESKPHONE" will not connect.
Can I actually get a copy of "my jabber-config.xml" file from the CUCM server to see what it looks like?
Thanks all

Ok I have half of the problem resolved. I got Deskphone controll working with CTI.
Still working on the LDAP issue with openLDAP
My config file looks like so
<?xml version="1.0" encoding="utf-8"?>
   EDI
   1
   ldap.acme.ca
   389
   backup.acme.ca
   389
   0
   uid=voipldap,ou=Users,dc=acme,dc=ca
   password
   givenname
   (&(objectClass=inetOrgPerson)
   telephonenumber
   uid
   ou=users,dc=acme,dc=ca
I got this from page 117 of this guide
http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_1/JABW_BK_CA48EE46_00_cisco-jabber-for-windows-administration.pdf
The error I'm getting "invalid credential" but i know they are good because i'm using the same account and path for the CUCM LDAP sync.
Any help would be appreciated.

Jabber for Windows - wildcard search against LDAP directory

Hi all,
I have set up an on premise environment with CUCM, CUPS and a 3rd party LDAP Directory. For CUPC everything is working fine. For Jabber for Windows it took me some time to find the correct jabber-config.xml settings to make it working.
At the moment I am able to search the LDAP Directory, but I have to write the complete Name, i.e. "Miller, John", in the search field. If I try it with "Miller" only, I get no results for my search.
I played arround with the <UseWildcards>0</UseWildcards> tag without any changes in the behaviour.
Is there anybody who can help?
Best regards
Manfred

Hi Manfred,
Jabber for Windows has been tested with following directory services:
Supported Directories
Microsoft Active Directory 2003
Microsoft Active Directory 2008
Cisco Unified Communications Manager User Data Service UDS is supported on Cisco Unified Communications Manager version 8.6.2 or later.
OpenLDAP
The behavior you are seeing could be related to interop issues. I suggest to open a TAC case for further assistance.
Thanks,
Maqsood

Jabber for Windows 9.2 deskphone control issue

Hi experts,
I'm having a problem with the newly installed Jabber for Windows 9.2.0. When I click on the bottom right "control phone" and select my Cisco 7941 it fails. I tried restarting the Cisco CTIManager service with no luck.
Deployment:
IM&Presence: cloud (Webex service)
CUCM version: 8.6(2a)
LDAP integration: full (with authentication)
Deskphone control was working prior the upgrade of Jabber for Windows. Everything else remained the same version.
Using Jabber softphone as a client still works fine.
CUCM ENd User is correctly configured.
Wireshark trace of my Jabber for Windows 9.2 client communicating with CUCM when attempting to control my deskphone shows the following:
Username: filippo.zangheri
Password: checked three times (it is correct because Jabber softphone works fine).
Any hint?
Thanks.
Filippo

Davide,
I know i am kind of late to the party on this one but i have fixed my issue and wanted to give you the information to see if this will work for you. If this is even still an issue?
I too had the same issue and just like you i confirmed everything was correct however I discovered something when I was looking into my End User profile on the CUCM. I had originally swapped my 7971 phone with a new 8945 phone and I had both phones associated with my line for a while before I removed the old 7971.
My End User profile still had both phones associated with my number even though the 7971 phone had been removed from my line. This was not allowing the CTI to connect to my 8945 phone or allow my jabber client to "Control Phone" properly because it couldn't figure out which phone to control. I went into the CUCM and physically deleted the 7971 phone from the system which released the associated phone in my End User profile. Once I did that, I "Control Phone" in my Jabber client and voila it worked like a charm!
To make sure I didn't have any Jabber client issues after doing this i signed out of my Jabber client and deleted the local system profile for the Jabber client and then signed back into Jabber and let it recreate the profile. Once that was done i have not had any issues with my Jabber client controlling my phone and all functions work perfectly.
Hope this helps...

Jabber for Windows 9.1.0 no contact lists are added

Hi,
We are using Jabber for Windows 9.1.0, we are surprised to see that contact list is empty. Do we need to manually add all the users? We have Presence server integrated with LDAP.
How can we add all the users to be appeared on contact list of all the users?
Regards
MAC

Did you configure the contact list in IM&P so that you had them when you logged in????
If not, yes, your contact list will be empty and you need to add the users manually.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Jabber For Windows deskphone control

All,
This is my last stop before getting with TAC and I just wanted to see if anyone has had and resolved this issue:
Jabber for Windows (all versions up to 9.1) Desk phone control most times takes several attempts to become active and working. If the client is shut down, the client defaults to Computer for calls and it takes several more attempts to get desk phone working again (half the time I get a red X over device option icon.
Anyone else experienced this or have a suggestion?
CUCM8.5
Presence 8.6
Gareth

Richard,
I managed to get everything working again (hopefully!).
I removed all devices from my prefile and re added them, as well as restarting the presence service and CTI service in CUCM. Seems to have done the trick for now.
Gareth

Jabber for Windows LDAP Profiles

I have been unable to find a lot of information on LDAP profiles, but I came across a blog that said that LDAP profiles are only used for Android, iphone and ipad. It stated that the only way to control the search base on Jabber for Windows is by using the jabber-config.xml file. So far this appears to be true based on my limited testing.
I have been able to integrate with OpenLDAP using the jabber-config.xml file to set the server and search base. The only problem i can see with this particular design is I would have to give all users the same LDAP profile and search settings. In our environment this will not satisify our requirements.
Does anyone know of a way where i can integrate with OpenLDAP, use the Jabber for windows client and control the LDAP search setttings on a per user basis?
Thanks

Yes but you won't like it.
Group Configuration File NamesYou specify the name of the group configuration files in the Cisco Support Field on the CSF device configuration in Cisco Unified Communications Manager.If you remove the name of the group configuration file in the CSF device configuration on Cisco Unified Communications Manager, Cisco Jabber for Windows detects the change, prompts the users to sign out, and loads the global configuration file. You can remove the name of the group configuration file in the CSF device configuration by deleting the entire configurationFile=group_configuration_file_name.xml string or by deleting the group configuration filename from the string.If users have desk phone devices only, use the following command line argument to specify unique names configuration files for different groups: TFTP_FILE_NAMESee the Install Cisco Jabber for Windows chapter for more information about the command line arguments.
Please remember to rate helpful responses and identify helpful or correct answers.

Jabber for Windows 9.1(3) - All network connections fail at least once a day

Similar Messages

Maybe you are looking for