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

Similar Messages

  • 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

  • Configure Jabber for Mac with local CUCM and WebEx Connect

    Hi, I was wondering if anyone has been able to configure the Jabber for Mac 8.6.2 client to use the WebEx Connect presence server with a local CUCM and Unity Connection servers. The preferences accounts tab does not show or allow the addition of the voice services. I have added from a working local CUCM preferences plist file what I believe are the correct entries however I still cannot see the accounts on the preferences tab. We currently do not have a local cisco presence server hence the requirement to trial the WebEx Connect server as I can't get past the first configuration step without it.
    regards
        paul

    Hi - I have done this via the admin portal but still cannot get the Jabber client for Mac to register for voice.  The Windows version works fine for the same user and CUCM device.   Are there any other settings that need to be enabled specific to the Mac client?
    Thanks.

  • Failed to sign on the WEBEX server on jabber for windows 9.2.6

    hi,
      just wanna intergrate Jabber for windows with Webex meeting feature, but failed
      i hvae intergrate CUCM 8.6.2 CUPS 8.6.4 & CUC 8.6.2 now ,
    and the jabber client （version 9.2.6）has the feature  with IM, aduio & video call , voice mail .
    but the client seems failed to got the certificate form the webex server.
    less configrue guide or deployment guide about how to intergraed cwms 1.5 with cups 8.6 and cucm 8.6 can i found
    anyone can help me ?
    really thanks!!!!
    消息编辑者为：Qiyu Bao

    need help
    Qiyu Bao 编写:need help！！！！need help！！！！

  • Jabber for Windows 9.1 and WebEx Voicemail Tab

    Guys
    we are using both Jabber for Windows (9.1) and WebEx connect clients. both connect to WebEx cloud services. when we use WebEx connect we have all features including voicemail but when we use Jabber for Windows there isnt any voicemail option at all present.
    both are doing phone integration and everything else is working fine.
    Now when we do the same for our andriod tablets we have the option for voicemail.
    i  understand that there are several feature differences but based on the searches ive been doing, voicemail should be present and i havent actually seen anyone having this problem. Note, this is using WebEx not CUPS.
    i know im probably missing something completely here.
    thanks again

    Do these users all have a conferencing profile assigned to them in CUCM (9.0) or CUPS (8.x)?
    Regards,
    Erik
    Sent from Cisco Technical Support iPad App

  • Jabber for Windows On Premise Webex Integration

    Hi,
    I just upgraded to 9.0.4 and am having an issue integrating Webex into Jabber.  Our Webex meeting center site is SSO enabled.  In jabber, when I attempt to setup my meetings account I get the below message:
    I've tried clicking the edit button and specifying various forms of my domain credentials with no luck.  I also see the below blurb in the jabber for windows environment configuration guide:
    Does that message mean that Jabber does not support a SSO enabled Webex meeting center site?
    Thanks,
    Dave

    That's correct, sorry.
    Please remember to rate helpful responses and identify helpful or correct answers.

  • Jabber for Windows - Flip between WebEx and CUPS logins

    I am running Jabber for Windows 9.0.5
    I want to flip between my CUPS install in my lab and a WebEx Connect instance we are testing.  I can get it logged into my CUPS instance but when I go to File -- Connection Settings and choose WebEx, it will not login.  I tried specifying the server but I don't know what the URL would be.  The one in the default is
    https://loginp.webexconnect.com/cas/auth.do
    But that seems to not work.
    How do I get Jabber for windows to login to my Connect account?  Maybe it's not supposed to but I thought this was the on-demand version of Jabber that is documented here
    http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps6836/ps12511/data_sheet_c78-704195.html&ei=6J-AUK8yjJOzBtLFgbAK&usg=AFQjCNFQ_n2Ih1yyFi_LQry4M_5E0ba-uA&sig2=v0-ta4tEtjZMzU6hC3Vf0A

    Hello, Josh!
    You can switch the config of J4W by altering the Connection Settings under the File menu before you log in. On my Jabber client, I selected the Cisco WebEx server type and left the login server address by checking the default server option. Make sure you log into WebEx Messenger (formerly WebEx Connect) using your complete email name (in my case, [email protected]) and your WebEx Messenger IM password (not necessarily same as WebEx Meeting Center credentials). I don't know the startup process for J4W, so I don't know how this works with the default server option. I'll follow up, though, as I know I saw a post that addresses this.

  • 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 SSO

    I'm using Jabber for Windows with a Webex backend for IM&P with CUCM and Unity Connection on-site.
    It looks like I can use SSO for logging into Webex with Jabber but I wanted to confirm if it will also work for logging into CUCM with the phone services account as well as for logging into Unity Connection for IMAP so that our users don't have to enter the phone services or voicemail account details manually.
    Any thoughts?
    Thanks,
    Brian Meade

    Hi Eric,
    No specific configuration is done on CWMS for Jabber for Windows integration. All this is done on Jabber side. I would advise you to reach out to Jabber Clients community or open a TAC ticket with Jabber for Windows team.
    -Dejan

  • Jabber for Windows 10.5 shows contacts from Address Book multiple times?

    What would cause Jabber for Windows 10.5.1 to show a contact multiple times from the address book when searching?  See attached screenshot. 

    I tried removing firefox and rebooting/reinstalling Jabber with no luck.  I reimaged my machine and loaded 10.5.2 fresh install with no previous versions and still getting the random crash.  Also, I have users who say it has crashed on them during a WebEx and have had installation problems when upgrading from 9.x to 10.5.x.  Version 9 is very solid, sticking with 9.7.5.  I have about 10% of my test users having varying problems with version 10.5.x, waiting till the next release.  Hopefully Cisco will spend a few more weeks testing the next one before publishing it on their site.
    --edit--
    Also, when you finally get frustrated and want to downgrade, Jabber 10.5.x doesn't uninstall completely and you end up with an error like the image attached when you try to install v9.7.5 for example and can't install Jabber even after rebooting.  I had to run Microsoft Fix It install/Uninstall option and tell it to uninstall Jabber before Windows allowed me to install an older version of Jabber.  Not too happy with this release.  Strange enough though, some of my users have the exact same laptop I do, same windows build, same patches, etc, and it works fine for them.  Anyway, not deploying this one.  Good luck.

  • Jabber for Windows Can't Login

    Hi,
    I have Jabber for Windows 9.6.1 and IM and Presence Server 9.1.1. The problem is it says it cannot communicate with the server upon logging in. But if I typed a wrong username / password it says "Your username and password is not correct." Has anyone experienced this? I cannot open a TAC case because this is a demo only. Hope someone can help.
    Thank you.

    I have a similar problem.  I have two production clusters that I support.
    The first in running CUCM 8.6(2), without IM & Presence, and the second is running CUCM 9.1(2) with Presence 9.1(1).
    The two clusters are georgrapphically dispersed, but are in the same domain.  I've built a lab environment simulalating the first cluster, which is soon to be upgraded.  As part of the upgrade, IM & Presence server will be added.  EVentally, the two clusters will be able to Jabber each other.  At present, we use WebEx Connect.
    The lab environment has a CM, Unity, and a IM &P server.  The License manager has been set up and a copy of my production licenses have been converted to CUWL, and are installed in the test environment.  The lab envrionment is installed w/o DNS, and all servers are a) referenced by IP address, and b) on the same subnet.
    My CM links to LDAP are complete, and I can see all of my AD users in CM, Unity, and IM&P.
    Additionally, I have configured a local user in CM.  I have both a local user and an AD user configured to a phone in an unused range. These two users are active and enabled.
    I've created CSRs for the IM&P server and CM, and have imported my private CA certs as well as certs for tomcat,cups-xmpp, and ipsec.  As far as I can tell, the required services are up.
    For Jabber, I'm currently playng with 10.5.0 for Windows.When I attempt to login I'm told the username or is incorrect.

  • Jabber for Windows 10.5.1 not working without elevated permissions

    Customer starts Jabber for Windows 10.5.1 and gets a pop-up about CiscoJabber.exe, wbxcOIEx.exe, and wbxcOIEx64 and to contact WebEx support.  It appears these components are talking to Outlook.  Show connection status under Outlook we see a mapi connection error with a code 0x80080005 that goes back to permissions error.
    Users are not local administrators running Windows 7.  Jabber was packaged using LanDesk and deployed to PC and installed with admin rights.
    Workaround was to grant elevated permissions to Jabber folder that had CiscoJabber.exe, wbxcOIEx.exe, and wbxcOIEx64.
    see attached screenshot.
    TAC Case 632162203 sent issue to BU for escalation, meanwhile customer elevated that folder permissions

    @ richard Beck   good answer your answer is right 

  • 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 crashing

    Jabber for windows - crashes on start up
    CUCM 7.1.3
    Windows 7 32 bit
    Cisco Presence   8.0.2.10000-30
    - these are in the application event log
    Log Name:      Application
    Source:        MsiInstaller
    Date:          6/27/2012 10:43:19 PM
    Event ID:      11729
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          WGL\bfairchild
    Computer:      CORPLAPR8YK305.corp.wgtnet.com
    Description:
    Product: Cisco Jabber -- Configuration failed.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">11729</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-28T02:43:19.000000000Z" />
        <EventRecordID>35189</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CORPLAPR8YK305.corp.wgtnet.com</Computer>
        <Security UserID="S-1-5-21-867046329-488861948-689510791-2168" />
      </System>
      <EventData>
        <Data>Product: Cisco Jabber -- Configuration failed.</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Binary>7B45353431313243312D463832412D343834372D383633312D4341313833384541353442347D</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        MsiInstaller
    Date:          6/27/2012 10:43:18 PM
    Event ID:      11706
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          WGL\bfairchild
    Computer:      CORPLAPR8YK305.corp.wgtnet.com
    Description:
    Product: Cisco Jabber -- Error 1706. No valid source could be found for product Cisco Jabber.  The Windows Installer cannot continue.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">11706</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-28T02:43:18.000000000Z" />
        <EventRecordID>35188</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CORPLAPR8YK305.corp.wgtnet.com</Computer>
        <Security UserID="S-1-5-21-867046329-488861948-689510791-2168" />
      </System>
      <EventData>
        <Data>Product: Cisco Jabber -- Error 1706. No valid source could be found for product Cisco Jabber.  The Windows Installer cannot continue.</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Binary>7B45353431313243312D463832412D343834372D383633312D4341313833384541353442347D</Binary>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Microsoft-Windows-RestartManager
    Date:          6/27/2012 10:43:15 PM
    Event ID:      10000
    Task Category: None
    Level:         Information
    Keywords:     
    User:          WGL\bfairchild
    Computer:      CORPLAPR8YK305.corp.wgtnet.com
    Description:
    Starting session 0 - ‎2012‎-‎06‎-‎28T02:43:15.619915900Z.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
        <EventID>10000</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-28T02:43:15.620916000Z" />
        <EventRecordID>35187</EventRecordID>
        <Correlation />
        <Execution ProcessID="8160" ThreadID="8616" />
        <Channel>Application</Channel>
        <Computer>CORPLAPR8YK305.corp.wgtnet.com</Computer>
        <Security UserID="S-1-5-21-867046329-488861948-689510791-2168" />
      </System>
      <UserData>
        <RmSessionEvent xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
          <RmSessionId>0</RmSessionId>
          <UTCStartTime>2012-06-28T02:43:15.619915900Z</UTCStartTime>
        </RmSessionEvent>
      </UserData>
    </Event>
    Log Name:      Application
    Source:        MsiInstaller
    Date:          6/27/2012 10:43:15 PM
    Event ID:      1040
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          WGL\bfairchild
    Computer:      CORPLAPR8YK305.corp.wgtnet.com
    Description:
    Beginning a Windows Installer transaction: {E54112C1-F82A-4847-8631-CA1838EA54B4}. Client Process Id: 8400.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1040</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-28T02:43:15.000000000Z" />
        <EventRecordID>35186</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CORPLAPR8YK305.corp.wgtnet.com</Computer>
        <Security UserID="S-1-5-21-867046329-488861948-689510791-2168" />
      </System>
      <EventData>
        <Data>{E54112C1-F82A-4847-8631-CA1838EA54B4}</Data>
        <Data>8400</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        MsiInstaller
    Date:          6/27/2012 10:43:14 PM
    Event ID:      1001
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          WGL\bfairchild
    Computer:      CORPLAPR8YK305.corp.wgtnet.com
    Description:
    Detection of product '{E54112C1-F82A-4847-8631-CA1838EA54B4}', feature 'Cisco_Jabber_Files' failed during request for component '{14F2AABC-F10C-4DE6-BC0E-28ED6D7F8508}'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-28T02:43:14.000000000Z" />
        <EventRecordID>35185</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CORPLAPR8YK305.corp.wgtnet.com</Computer>
        <Security UserID="S-1-5-21-867046329-488861948-689510791-2168" />
      </System>
      <EventData>
        <Data>{E54112C1-F82A-4847-8631-CA1838EA54B4}</Data>
        <Data>Cisco_Jabber_Files</Data>
        <Data>{14F2AABC-F10C-4DE6-BC0E-28ED6D7F8508}</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        MsiInstaller
    Date:          6/27/2012 10:43:14 PM
    Event ID:      1004
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          WGL\bfairchild
    Computer:      CORPLAPR8YK305.corp.wgtnet.com
    Description:
    Detection of product '{E54112C1-F82A-4847-8631-CA1838EA54B4}', feature 'Cisco_Jabber_Files', component '{826A7892-74F0-481D-B5F2-3F733F91DB81}' failed.  The resource 'C:\Program Files\Cisco Systems\Cisco Jabber\JabberMeeting\DesktopShare\atgpcdec.dll' does not exist.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1004</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-28T02:43:14.000000000Z" />
        <EventRecordID>35184</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CORPLAPR8YK305.corp.wgtnet.com</Computer>
        <Security UserID="S-1-5-21-867046329-488861948-689510791-2168" />
      </System>
      <EventData>
        <Data>{E54112C1-F82A-4847-8631-CA1838EA54B4}</Data>
        <Data>Cisco_Jabber_Files</Data>
        <Data>{826A7892-74F0-481D-B5F2-3F733F91DB81}</Data>
        <Data>C:\Program Files\Cisco Systems\Cisco Jabber\JabberMeeting\DesktopShare\atgpcdec.dll</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Hi,
    Jabber is attempting to repair itself from a conflict with the WebEx productivity tools.  However, it is looking for the original install file (.msi), cannot find it and therefore the repair fails.  To work around this problem you need to:
    1 - Download the same version of CiscoJabberSetup.msi that is installed.  You can check the version by finding CiscoJabber.exe in your Program Files directory, right click, Properties and on the Details tab there is a product version.
    2 - Copy this file to the location fro which you previously installed Jabber.  For example, if you downloaded the .msi to your desktop previously, do the same here again.  If you got this update as part of an auto update, then copy the file to "%temp%".
    3 - Launch Jabber - it should successfully repair itself and launch.
    Thanks,
    Rob.

  • Jabber for Windows SSO with CWMS

    We've configured our WebEx Meetings Server 2.0 for SSO with ADFS 3.0 and it works in various browsers.  The docs for Jabber for Windows say that it can do SSO to WebEx Meetings Server but there are no details in the configuration guide and I haven't been able to get it to work. After I turn on SSO, Jabber won't authenticate with the Meetings Server.  All the guide says is
    If you configure SSO with Cisco WebEx Meetings Server, Cisco Jabber can seamlessly integrate with the SSO environment. In this case, you do not need to specify credentials in order for users to authenticate with Cisco WebEx Meetings Server.
    Any ideas?

    Hi Eric,
    No specific configuration is done on CWMS for Jabber for Windows integration. All this is done on Jabber side. I would advise you to reach out to Jabber Clients community or open a TAC ticket with Jabber for Windows team.
    -Dejan

Maybe you are looking for