Jabber for windows soft phone issue

Hi Guys
Wondering if anyone has come accross this.. I have just installed J4W 10.5.2, the presence / IM works fine however the soft phone doesn't  register.  it comes up with error.. Connection error. Ensure the server information in the Phone Services tab on the Options window is correct. Contact your system administrator for assistance
The machine is obviously on the data VLAN.. however  when i connect  the machine to the voice VLAN the soft phone registers ok..  see attached document
A little background.. the SVIs for the VLANS are on a firewall but there are no restrictions between the data and voice VLANs .. see attached
please help

Did you find a solution to this i have a PC that is doing the exact same? softphone doesn't work on data  VLAN but does switched to Voice VLAN it connects and works properly.
PC connected direct to Data VLAN
-Allows CTI control of DeskPhone Softphone fails.
PC connected Direct to Voice VLAN
-Allows CTI contol of DeskPhone Softphone works.
Does not seem to be a Network problem because can use the same ports on a My Laptop and the Jabber Client works on Both VLANS

Similar Messages

  • Jabber for Windows Voicemail Playback Issue

    Hi,
    I have Jabber for Windows installed and voicemail is working ok but when I playback a voicemail from the Jabber client the MWI light does not go out on the phone. If you do the opposite ie listen to a new voicemail through the phone the new message indicator goes out on jabber.
    Also if you listen to the voicemail through Jabber client the voicemail plays through the PC speakers. Is there anyway in getting Jabber to direct the call to the phone so the user can pick the handset to listen like you can when listening to voicemail through the Unity Connection Web Inbox.
    Thanks for you time
    Regards
    Neil

    Hi Neil,
    Playing the voicemails in Jabber should turn off the MWI light. You need to open a TAC case and sent on a problem report to debug this further.
    For the second question, the only way I think you can do this is by setting Jabber to deskphone mode and then using the "Call Voicemail" button.
    - Colin

  • Cisco Jabber for Windows Voicemail issue

    At this I'm in processing of implementation Cisco Jabber UC solution for big Company.
    I use CUCM 9.1.2, Cisco IM and Presence 9.1.2, CUC 9.1.2, Cisco Jabber for Windows 9.6.1.
    I have issue in Cisco Jabber with VoiceMail Integration - when I leave voice message for any user,
    than this message is arrived only him Cisco IP Phone, but not in him Cisco Jabber.
    From Cisco Jabber Connectivity status in help menu I see that VoiceMail service is successfully connected
    and I see VoiceMail button in Cisco Jabber.
    How can I resolve this issue?

    Have you configured the UC Service profile on CUCM with both Voicemail server and mailbox servers?

  • 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 cannot control 8841 desk phone

    Hello Team,
    We have a problem with desktop phone control in case of 8841 phone.
    When the user try to switch to the 8841 phone in Jabber then we got the following error message in the log: 
    2014-11-07 09:39:53,855 ERROR [0x00000298] [ice\TelephonyAdapterPhoneDevice.cpp(178)] [TelephonyAdapter] [TelephonyAdapter::selectDeviceImpl] - switchMode to device [SEP84802D7698D6] failed with error [eDeviceRegCouldNotOpenDevice]
    We get the red X on the phone icon, and the desktop phone control is not working.
    If the same user try to control 7940 phone, then it's working fine.
    The environment: UCM 9.1.2.12901-3, CUPS 9.1.1.51900-5, Jabber for Windows 10-5.2
    Edited:
    Same issue with UCM 10.5.1, CUPS 10.5.1, and Jabber for Windows 10.5.2.
    Regards,
    Zsolt

    Hi Zolt,
    The RT phones need below end user permissions also in order to control deakphones:
    Standard CTI Allow Control of Phones supporting Connected Xfer and conf
    Standard CTI Allow Control of Phones supporting Rollover Mode
    If they are not added, please add these permission.
    Regards

  • Jabber for Window, phone mode, how to disable "use my computer for calls"

    We have a Citrix environment and only want to control the Cisco deskphone with Jabber for Windows in the phone mode.
    We use CUCM 8.6.2 and I have installed Jabber for Windows 9.7.0 and all works fine, I can control my deskphone, make and receive calls, phonebook and Outlook integration works fine.
    Is it possible to disable "use my computer for calls" as we do not want users to make calls via Citrix, but only use the deskphone for this.
    Thanks, Perry

    Hi Matthias,
    Soft-phone mode cannot be disabled. Supported Features on Virtual Environment are the following.
    Supported Features
        Instant messaging and presence with other Cisco Jabber clients
        Desk phone control
        Voicemail
        Presence integration with Microsoft Outlook 2007, 2010 and 2013
    We have an existing defect which is in Terminated state because feature is not supported hence cannot be fixed.
    CSCub40605 - J4W - Ability to disable softphone mode in Citrix environment.
    HTH,
    Please rate if you find this post helpful.
    Regards,
    Mohammed Noor

  • Jabber for Windows 9.0.1 phone control of Cius?

    Can the Jabber for Windows client control a Cius like it can a 79XX phone?                  

    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

  • Jabber for Windows- VM issue

    I had configured Jabber for windows in  windows 7, the problem is after logging into jabber client iam not able to get the "phone accounts" under options.
    Iam able to call , and recieve calls but no voice mail. In the Jabber cleint diagnostic it shows username and password is wrong for voice mail.
    If i have 'phone acounts' option in jabber client i could set username and password for voice mail. Iam able to telnet the unity server.
    Any clue?
    We have IM&Presence 9.0, CUCM 9.0
    Jabber - 9.2
    Tnx
    Bobby

    HI,
    As Aron states - you can configure your client to use same login and password ID as other UC services. This will then mask the fields you see in your jabber client. This is great when you don't want your users to have to populate the fields. The less they have to do the better.
    Check your Unity Connection system - is it AXL ot AD or neither ?
    If you can, your better to use only one username / password across your UC environment. For now just check your setting for the VM service is not set .

  • Jabber for Windows - Outlook Meeting integration issue/questions

    Hi,
    A couple of questions if anyone else has experienced or can answer:
    1. When you turn on Jabber it appears in the trace file to create a transitionlist of meetings in your calendar for the next four hours. Eg if meeting 8-9 it will show 8:00 BUSY
            9:00 FREE
    and this works ok. This transitionlist also seems to update each time a status change occurs from what I have observed.
    The problem we seem to have is if I open Jabber at 7.45am and have a meeting 8 - 9 then it shows "In a meeting", then if I create a meeting at 9.15am for 10am-10.30am, the meeting status does not change as it seems to operate of the four hour transitionlist. I have the setting in the CUPS server for exchange sync to happen every twenty minutes, but this does not seem to update.
    I'm be focussing on the wrong area but basically not all calendar appt's update status in Jabber, especially the one's created within the four hour pperiod.
    2. To have the presence status of a person in an Outlook email address field, do you need 2010 or does it work with prior versions, we currently operate 2003. I have configured the SIP component in AD, but no status or click to call facility from Outlook.
    Thanks in advance
    Mal

    Hi Mal,
    Thanks for your post. Issue (1) sounds like a configuration issue in your setup. Please open a TAC case for further assistance.
    Regarding (2), Jabber for windows does noot support Office 2003. List of supported MS Office applications is listed in Jabber for Windows administration guide.
    http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_0_1/b_jabber_win_icg_chapter_01000.html#reference_AC2F9334FEC54DA98861EB52944C6F08
    Thanks,
    Maqsood

  • Jabber for windows 9.7 photo issue

    Hello,
    I'm facing an issue with corporate photos on Jabber version 9.7. Before, with version 9.2 i had the same problem but after add an entry on the file jabber-config.xml the corporate photos were already shown.
    What can be the cause for this behaviour with version 9.7?

    Hi Amit,
    Hope you're doing well. Guess the problem is solved. We installed this new version 9.7 of jabber on a machine with Windows XP OS. After reviewing the Cisco Jabber for Windows 9.7 Release Notes I noticed that the only available Operating Systems for jabber 9.7 are:
    Operating System Support Cisco Jabber for Windows 9.7 supports the following operating systems:
    •Windows 7 (32 bit and 64 bit)
    •Windows 8 (32 bit and 64 bit). Note: Metro Interface and Windows 8 RT are not supported.
    •Windows 8.1 (32 bit and 64 bit). Note: MediaNet (including deskphone video feature) does not currently support Windows 8.1
    Thanks a lot!

  • Jabber for Windows / iPhone - issue with photo and search

    Dear community,
    I have an issue regarding Cisco Jabber for Windows as well as iPhone & iPad.
    I recently upgraded our Call Manager infrastructure from 8.6.5 to 10.0. Along with that, I wanted to rollout the new Jabber for Windows (9.7.2) because now we use a very old version (9.2.1).
    After I upgraded my test client, I noticed that the user photos (which are retrieved from active directory) were gone.
    So for the first time, I decided to modify the the jabber-config.xml (I attatched the two different versions).
    I used the jabber config generator to create the new version: https://supportforums.cisco.com/document/106926/jabber-config-file-generator
    My attempt is to achive these goals:
    1) I want one config file which is working with Jabber for Windows, iPhone & iPad, Android as well as Jabber for Mac
    2) I want a secure connection from the client to our directory server
    3) I want to retrieve the user photos from the active directory user (attribute thumbnailPhoto)
    4) Jabber should find only users which are a member of the active directory group "example" (example is a nested group which contains several users and at least _one_ other group). Until now, the whole active directory was searched for users/contacts.
    So far, 1) and 2) seems to work fine. 3) and 4) are the troublemakers and I really don't no why.
    Can somebody help me?
    Best regards,
    René

    Look at this thread. You can find the answer there.
    https://supportforums.cisco.com/discussion/12241391/ldap-contacts-and-photos-jabber-ipad-iphone-and-android-not-working
    First I had to uncheck "Use UDS for Contact Resolution" and then I had to create a new jabber-config.xml and upload it to the TFTP server.
    But there are a few limitations you have to deal with. But I have mentioned that in the other thread.

  • Jabber for Windows 9.2 Deskphone Control

    Hi,
    I have a deployment with:
    CUCM 9.1(1a) (9.1.1.20000-5)
    IM and Presence 9.1(1a) 9.1.1.20000-5
    Jabber for Windows 9.2.3(4417)
    I have got most features working but Deskphone Control is not working. I can see the devices associated with my user from within Jabber when I select "Use my phone for calls" but cannot control them.
    The connection status page shows the correct IP address for the CTI server.
    I have spent hours reading through various documents and forums which seem to contain contradictory advice.
    To clarify theserver  versions that I have deployed support the new UC Services which are referenced from a Service Profile which is assigned to the user.
    I am not making any progress resolving this issue. Does anyone have any advice on how to move forward with this?
    Thanks
    James

    Hi Daniel,
    we have a Problem with AD-User and DeskPhone ...
    The "Active Local User" can control a DeskPhone
    The "Active LDAP Synchronized User" can't control a DeskPhone from same PC, but he can controll a Softphone.
    Cisco UCM - 9.1.2.10000-28 with LDAP Sync/Auth via 3269 (success)
    Cisco UCMIMP - 9.1.1.31900-1
    Cisco Jabber - 9.6.0 Build 17088
    564 INFO  [0x0000226c] [src\common\thread\WorkerThread.cpp(94)] [csf.ecc] [run] - Started thread: CtiConnection
    564 DEBUG [0x0000226c] [utilities\socket\TcpSocketHelper.cpp(82)] [csf.ecc] [connect] - About to connect to 172.20.1.11
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(957)] [csf.ecc] [SendRequest] - CDPProvider::SendRequest, msg.sequenceNumber=1, pObject=0477A214, pdunames[msg.msgID]=PROVIDER_OPEN_REQUEST
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(967)] [csf.ecc] [SendRequest] - SendRequest setting msg.sequenceNumber to , msg.sequenceNumber=2
    564 DEBUG [0x0000226c] [oneprovider\QBE\ProtocolElement.cpp(330)] [csf.ecc] [encode] - Message::encode: , msg.protoVersion=0x000e0000, msg.msgID=3, sizeof(Header)=32, fixedSize=108, varSize=90
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(973)] [csf.ecc] [SendRequest] - SendRequest Succeed., pdunames[msg.msgID]=PROVIDER_OPEN_REQUEST, msg.sequenceNumber=2
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(986)] [csf.ecc] [SendEvent] - CDPProvider::SendEvent, pObject=0477A210, nType=1001
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(919)] [csf.ecc] [OnEvent] - CDPProvider::OnEvent, pObject=0477A210, nType=1001, pvThis=0477A210
    564 DEBUG [0x0000226c] [pper\DeskPhoneConnectionContext.cpp(317)] [csf.ecc] [ecc::DeskPhoneConnectionContext::OnProviderEventUpdated] - OnProviderEventUpdated(1001), state=STATE_INITIAL_LOGIN, loginstate=LOGINSTATE_OPENING
    564 DEBUG [0x0000226c] [c\deskphoneprovider\DPProvider.cpp(1148)] [csf.ecc] [DispatchTheMessage] - CDPProvider::DispatchTheMessage, nPduNum=4, pduName=PROVIDER_OPEN_RESPONSE
    564 DEBUG [0x0000226c] [c\deskphoneprovider\DPProvider.cpp(1232)] [csf.ecc] [DispatchTheMessage] - Received , pdunames[nPduNum]=PROVIDER_OPEN_RESPONSE, seqNum=2
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(267)] [csf.ecc] [HandleMessage] - CDPProvider::HandleMessage, nPduNum=4
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(407)] [csf.ecc] [HandleResponse_ProviderOpen] - CDPProvider::HandleResponse_ProviderOpen
    564 DEBUG [0x0000226c] [oneprovider\QBE\ProtocolElement.cpp(360)] [csf.ecc] [decode] - Message::decode: , totalSize=107, type=0, magic=4294958557, msg.protoVersion=0x000e0000, pduNum=4, hdrSize=32, fixedSize=52, varSize=31
    564 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(415)] [csf.ecc] [HandleResponse_ProviderOpen] - CUCM protocol version: , resp.getProtoVersion()=0x000e0000
    564 WARN  [0x0000226c] [c\deskphoneprovider\DPProvider.cpp(1026)] [csf.ecc] [ResetHeartbeatTimer] - m_heartbeatIntervalS not set, timeout not set.
    845 DEBUG [0x0000226c] [c\deskphoneprovider\DPProvider.cpp(1148)] [csf.ecc] [DispatchTheMessage] - CDPProvider::DispatchTheMessage, nPduNum=126, pduName=PROVIDER_OPEN_COMPLETED_EVENT
    845 DEBUG [0x0000226c] [c\deskphoneprovider\DPProvider.cpp(1290)] [csf.ecc] [DispatchTheMessage] - PDUTYPE_ProviderEvent or PDUTYPE_Heartbeat, nPduNum=126, pdunames[nPduNum]=PROVIDER_OPEN_COMPLETED_EVENT
    845 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(267)] [csf.ecc] [HandleMessage] - CDPProvider::HandleMessage, nPduNum=126
    845 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(488)] [csf.ecc] [HandleEvent_ProviderOpenCompleted] - CDPProvider::HandleEvent_ProviderOpenCompleted
    845 DEBUG [0x0000226c] [oneprovider\QBE\ProtocolElement.cpp(360)] [csf.ecc] [decode] - Message::decode: , totalSize=161, type=0, magic=4294958557, msg.protoVersion=0x000e0000, pduNum=126, hdrSize=32, fixedSize=72, varSize=65
    845 WARN  [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(502)] [csf.ecc] [HandleEvent_ProviderOpenCompleted] - ProviderOpen failed: reason: 0x8ccc0060, Directory login failed - authentication failed.
    845 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(986)] [csf.ecc] [SendEvent] - CDPProvider::SendEvent, pObject=0477A210, nType=1008
    845 DEBUG [0x0000226c] [rc\deskphoneprovider\DPProvider.cpp(919)] [csf.ecc] [OnEvent] - CDPProvider::OnEvent, pObject=0477A210, nType=1008, pvThis=0477A210
    845 DEBUG [0x0000226c] [pper\DeskPhoneConnectionContext.cpp(317)] [csf.ecc] [ecc::DeskPhoneConnectionContext::OnProviderEventUpdated] - OnProviderEventUpdated(1008), state=STATE_INITIAL_LOGIN, loginstate=LOGINSTATE_LOGGING_IN
    845 DEBUG [0x0000226c] [pper\DeskPhoneConnectionContext.cpp(891)] [csf.ecc] [ecc::DeskPhoneConnectionContext::DPLogoutWorkItem::DPLogoutWorkItem] - create DPLogoutWorkItem
    845 DEBUG [0x0000226c] [pper\DeskPhoneConnectionContext.cpp(892)] [csf.ecc] [ecc::DeskPhoneConnectionContext::DPLogoutWorkItem::DPLogoutWorkItem] - Setting _loginState = LOGINSTATE_DISCONNECTING
    845 DEBUG [0x0000226c] [c\deskphonewrapper\CC_DPService.cpp(926)] [csf.ecc] [ecc::CC_DPService::raiseLoginFailure] - raiseLoginFailure(5)
    845 DEBUG [0x000013a0] [pper\DeskPhoneConnectionContext.cpp(898)] [csf.ecc] [ecc::DeskPhoneConnectionContext::DPLogoutWorkItem::run] - DPLogoutWorkItem::run()
    845 INFO  [0x0000226c] [\deskphonewrapper\CC_DPService.cpp(1078)] [csf.ecc] [ecc::CC_DPService::notifyConnectionStatusObservers] - dispatching ConnectionStatus Change eIdle
    845 DEBUG [0x00002788] [c\deskphonewrapper\CC_DPService.cpp(298)] [csf.ecc] [ecc::CC_DPService::start] - Finished waiting for deskphone to go in to service...
    845 INFO  [0x000013a0] [rc\deskphoneprovider\DPProvider.cpp(218)] [csf.ecc] [Close] - CDPProvider::Close
    845 INFO  [0x0000226c] [control\CallControlManagerImpl.cpp(3092)] [csf.ecc.evt] [ecc::CallControlManagerImpl::notifyConnectionStatusChange] - CONNECTION_STATUS_CHANGE: eIdle
    845 ERROR [0x00002788] [control\CallControlManagerImpl.cpp(1989)] [csf.ecc] [ecc::CallControlManagerImpl::doConnect] - doConnect() returnCode : AuthentincationFailure
    845 DEBUG [0x000017a0] [s\telephonyservice\ECCObservers.cpp(153)] [csf-unified.telephony.ECCObserverLogger] [ECCObservers::onConnectionStatusChange] - onConnectionStatusChange(status = eIdle).
    845 DEBUG [0x0000226c] [\deskphonewrapper\CC_DPService.cpp(1014)] [csf.ecc] [ecc::CC_DPService::raiseProviderStateChange] - Got cxn change, disconnecting deskphone video Idle
    845 DEBUG [0x000013a0] [rc\deskphoneprovider\DPProvider.cpp(957)] [csf.ecc] [SendRequest] - CDPProvider::SendRequest, msg.sequenceNumber=2, pObject=0477A214, pdunames[msg.msgID]=PROVIDER_CLOSE_REQUEST
    845 ERROR [0x00002788] [control\CallControlManagerImpl.cpp(2025)] [csf.ecc] [ecc::CallControlManagerImpl::doConnect] - doConnect() returnCode : eDeviceRegAuthenticationFailure
    845 DEBUG [0x000017a0] [elephonyservice\BackgroundWorker.cpp(35)] [csf-unified.telephony.BackgroundWorkerLogger] [BackgroundWorker::doTask] - Adding new task to BackgroundWorker. Task name is: TelephonyAdapter::onConnectionStatusChange
    845 INFO  [0x0000226c] [rc\deskphonevideo\DeskPhoneVideo.cpp(76)] [csf.ecc] [ecc::DeskPhoneVideo::disconnect] - disconnecting
    845 DEBUG [0x000013a0] [rc\deskphoneprovider\DPProvider.cpp(967)] [csf.ecc] [SendRequest] - SendRequest setting msg.sequenceNumber to , msg.sequenceNumber=3
    845 INFO  [0x00002788] [control\CallControlManagerImpl.cpp(2411)] [csf.ecc] [ecc::CallControlManagerImpl::doDisconnect] - --->
    845 DEBUG [0x000017a0] [common\processing\TaskDispatcher.cpp(29)] [TaskDispatcher] [Processing::TaskDispatcher::enqueue] - Enqueue TelephonyAdapter::onConnectionStatusChange - Queue Size: 9
    845 DEBUG [0x0000226c] [c\deskphonevideo\DeskPhoneVideo.cpp(315)] [csf.ecc] [ecc::DeskPhoneVideo::stopCdp] - Stopping CDP
    845 DEBUG [0x000013a0] [oneprovider\QBE\ProtocolElement.cpp(330)] [csf.ecc] [encode] - Message::encode: , msg.protoVersion=0x000e0000, msg.msgID=9, sizeof(Header)=32, fixedSize=4, varSize=0
    845 INFO  [0x00002788] [pper\DeskPhoneConnectionContext.cpp(267)] [csf.ecc] [ecc::DeskPhoneConnectionContext::stop] - DeskPhoneConnectionContext::stop
    845 DEBUG [0x000013a0] [rc\deskphoneprovider\DPProvider.cpp(973)] [csf.ecc] [SendRequest] - SendRequest Succeed., pdunames[msg.msgID]=PROVIDER_CLOSE_REQUEST, msg.sequenceNumber=3
    845 DEBUG [0x0000226c] [c\deskphonevideo\DeskPhoneVideo.cpp(318)] [csf.ecc] [ecc::DeskPhoneVideo::stopCdp] - CDP stopped
    845 INFO  [0x000017a0] [src\AccessoriesManager.cpp(234)] [csf.accessory.event] [accessory::AccessoriesManager::onConnectionStatusChange] - Received onConnectionStatusChange - eIdle
    845 DEBUG [0x00002788] [pper\DeskPhoneConnectionContext.cpp(891)] [csf.ecc] [ecc::DeskPhoneConnectionContext::DPLogoutWorkItem::DPLogoutWorkItem] - create DPLogoutWorkItem
    845 INFO  [0x000013a0] [\deskphoneprovider\CtiConnection.cpp(49)] [csf.ecc] [stop] - CtiConnection::stop
    Thanks,
    Guennadi

  • 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

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

  • 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

Maybe you are looking for