Jabber no deskpone control

                   cup 8.6, cucm 7.13 , jabber 9.2 client.
all been working ok until recently we lost cti deskphone control.
No apparent changes to configuration.
her is some output from problem report:
Failed to register with CUCM [error: eInvalidState]
Failed to authenticate with CUCM [error: eNoCredentialsConfigured]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(423)] [csf.ecc-wrapper] [connectToCUCM] - -----------------------------------------------
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(424)] [csf.ecc-wrapper] [connectToCUCM] - Connection Details
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(425)] [csf.ecc-wrapper] [connectToCUCM] - CCMCIP Address: [10.96.10.12, 10.96.11.6]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(426)] [csf.ecc-wrapper] [connectToCUCM] - CTI Address   : [10.96.10.4, 10.96.11.7]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(427)] [csf.ecc-wrapper] [connectToCUCM] - TFTP Address : [10.96.10.12, 10.96.11.6]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(428)] [csf.ecc-wrapper] [connectToCUCM] - Username      :
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(429)] [csf.ecc-wrapper] [connectToCUCM] - DeviceName    :
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(430)] [csf.ecc-wrapper] [connectToCUCM] - -----------------------------------------------
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(492)] [csf.ecc-wrapper] [connectToCUCM] - Failed to register with CUCM [error: eInvalidState]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(493)] [csf.ecc-wrapper] [connectToCUCM] - -----------------------------------------------
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(494)] [csf.ecc-wrapper] [connectToCUCM] - Connection Details
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(495)] [csf.ecc-wrapper] [connectToCUCM] - CCMCIP Address: [10.96.10.12, 10.96.11.6]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(496)] [csf.ecc-wrapper] [connectToCUCM] - CTI Address   : [10.96.10.4, 10.96.11.7]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(497)] [csf.ecc-wrapper] [connectToCUCM] - TFTP Address : [10.96.10.12, 10.96.11.6]
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(498)] [csf.ecc-wrapper] [connectToCUCM] - Username      :
2012-07-18 11:33:09,562 ERROR [0x00000390] [src\phone.cpp(499)] [csf.ecc-wrapper] [connectToCUCM] - DeviceName    :

Hi Randy,
Have you specified this base filter in jabber-config.xml file? As per Admin Guide:
"In some cases, base filters do not return query results if you specify a closing bracket in your Cisco Jabber for Windows configuration file. For example, this issue might occur if you specify the following base filter: (&(memberOf=CN=UCFilterGroup,OU=DN))
To resolve this issue, remove the closing bracket; for example, (&(memberOf=CN=UCFilterGroup,OU=DN)"
Thanks,
Maqsood

Similar Messages

Jabber and deskphone control with video

Hi all,
one of our clients has IM and presence 9.1 and jabber on windows 9.1.X and is integrating with Active directory for user synchronization and authentication.
Q.
why when we use deskphone control with jaber users have an audio in hardware phones but video in Jabber clients not working ?
Note that the media service interface file is installed.
Help needed.
Thanks in advance.

you might want to have a look at this post
https://supportforums.cisco.com/thread/2160363
=============================
Please remember to rate useful posts, by clicking on the stars below.
=============================

Separate Jabber account to control presence?

I have a customer that wants admins or secretaries to be able to control their Presence. Is there a way to configure a separate profile that can't see messages but can control the account's presence?

Is there a way to dig into the API and provision an add-on or widget to jabber to allow a presence-only endpoint?

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 and iChat

Hi All
A question re iChat and Jabber accounts. I assume that when one has a conversation between two Jabber accounts using the iChat interface that it is using the Jabber protocol (XMPP) and not the AIM protocol. Is my understanding correct? If am I correct, has anyone noticed whether the Jabber protocol is more successful at completing calls (audio or video) between Macs and Windows PCs? Is Gmail Jabber still intra-Gmail only?
Cheers
Steve

Ok. So if I only have a Google Talk Jabber account I can't open gateways anyway. Understood - it's on its way. And we're not sure about Mac to PC over Jabber. iChat still controls the Jabber XMPP call leading to reduced quality than potentially possible.
BTW I think iChat gets itself in a real mess if you flick between using AIM video and Jabber video. As I noted in another thread I had a Mac-Mac AIM call with a friend and then we tried Jabber each using the iChat interface. The Jabber call seemed about the same quality - again with the iChat interface making poor use of bandwidth. When we tried to go back to an AIM video call we could not complete initially because I "failed to respond" and then, after we each deactivated the Jabber accounts, the AIM conversation simply got stuck at "starting".
So far I see the following with iChat:
1. Mac to Mac: poor use of available bandwidth leading to sub quality calls vs what could be achieved if available bandwidth were utilised.
2. Poor integration of Jabber. Simply not well thought out (two windows instead of one etc) and badly executed (iChat gets tied in knots).
3. Almost impossible Mac to PC audio/video communication.
Are you listening yet Apple?

Cisco Jabber for Windows Client SDK

Is there an SDK for Cisco Jabber for Windows client? I could only find the Web SDK. Are there no other SDKs that would let me control features of the Jabber Windows Client?

And in order to avoid TAPI limitation, they say they have started using Jabber which controls all phone functionalities through an Application User connected to the Call Manager.
Assuming they are referring to the normal Jabber for Windows/Mac/iOS/Android applications then this is wrong. Jabber - the client, not the IM&P servers which are part of the CUCM cluster (if you're familiar with Lync consider CUCM+IM&P servers a Front End Pool) - do not use an Application User at all. When a user starts Jabber, assuming SAML SSO is off, they supply an email address. This is used to find the servers via DNS SRV records, or the Mobile and Remote Access Expressway (roughly analogous to a Lync Edge pool) to tunnel through the firewall. After the email address they are prompted for their End User username and password. This is then used to access several APIs on the server, namely the User Data Service to discover what the user has. This would include what the user has configured/available to them. After this is done the Jabber client does one of three things with respect to phone functionality:
If the user has no phone devices provisioned for them - physical or software - it becomes an IM&P client only.
If the user has a software phone phone provisioned, it registers as that using SIP. In this way Jabber is the actual phone. This is called a CSF device for Jabber Windows/OS X.
If the user has a desk phone assigned to their End User account AND administrative policy is to default to desk phone control, it registers to CTI Manager on the CUCM server to control the user's physical phone.
A user can toggle between option two and three, if appropriately provisioned, but cannot have both simultaneously. In other words, Jabber is either controlling a physical phone over CTI or is a phone itself using SIP. The difference is where the audio/video media is sent from/to.
All of this happens using that human's End User credentials.
Now, if you wanted to have a server control the user's phone - either a physical one or Jabber - you would use the TSP as an interface to CTI Manager on the CUCM server and receive real-time events (e.g. the user went off-hook, the phone is ringing with this caller ID, etc.) and issue commands to that phone (e.g. make a call to X). This is done using an Application User account because the server would need to do this for multiple users simultaneously. If you also use the Super Provider concept, the CUCM administrator doesn't have to take the extra step of associating every phone to your Application User manually. Instead, you can simply issue CTI subscriptions to see any/all device activity you want.
This is all assuming you wanted to do the integration server-side to avoid having to update the Cisco TSP application on every user PC (which also limits your WPF application to machines capable of running the TSP) every time the CUCM administrator patches the servers. If you don't care about that, then you can do this all client-side on the user's PC, and have them supply their End User credentials.
Of course, you could also reconsider the Jabber SDK and just embed the make/receive call functionality directly into your application instead.

Unable to select 'Use Phone for audio calls' on Cisco Jabber Client 9.6 for Windows

Hi,
I have recently deployed Cisco Presence Server and integrated with Call Manager 9.1.2. I have successfully deplyed 6700 users on IM & Presence. Some of the users requested for Cisco Jabber with phone control.
I have added CFS client on the Call Manager and associated it with the same extension numbers from their desk phones. I am currently able to make audio and video calls for these specific users. I am currently using Cisco Jabber Client 9.6 for windows. I have users both daisy chained to their desk phones and who are not. Can you please confirm if it does make any difference.
Problem Faced -
I am not able to use to option use phone for audio calls. The phone comes down with a cross sign on it. At the same time Cisco Jabber by default uses the client and it works as expected.
Can you please let me know if any of you guys have faced a similar issue.
Please let me know if you need any information regading the configuration used.
Looking forward for your valuable comments.
Thank you.
Regards,
Joseph Chirayath.

Hi Will,
I am attaching the screen shot for the END USER on CUCM 9.X that has been configured on Cisco Jabber.
Please do let me know if you need any further information.
Thank you.

Cisco Jabber client with other telephony devices

Hi,
I am completely new to Jabber and just started to understand Cisco jabber client for windows.
I understood that the jabber client supports xmpp for IM and CTI integration with Cisco Call manager for call control.
Is there a provision to integrate the jabber client to non-Cisco devices like Avaya or nortel or an ITS Netrix turret?
Integrate direct or indirect - as in with a plugin
Please do direct to any available documentation that would help
Thanks

Hi,
Welcome to Jabber! Yes, the client supports XMPP and CTI.
And yes you can use your existing Avaya / Nortel phones using a Cisco UC feature called Extend and Connect. No plugin required! It allows Jabber to CTI control any phone with a dialable number, including public phones. You can read more about the Extend and Connect feature here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/9_1_1/ccmfeat/CUCM_BK_C3E0EFA0_00_cucm-features-services-guide-91_chapter_0110010.pdf
To configure it for Jabber for Windows you can follow these instructions:
http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_1/JABW_BK_E4CC9599_00_environment-configuration-guide_chapter_010.html#JABW_CN_EB63387E_00
Regards,
Matt

Jabber Screen share grayed out - SOLVED

Community, I need your help! I don't know where else to look.
I have in production CUCM (9.1.2.10000-28) and CUPS (9.1.1.31900-1) and I want to solve a few misbehaviors on CUPS.
Everything works without problems; except for the screen share, which works just partially our environment was deployed using Jabber for Windows version 9.2.4 now, we are trying to move to the latest version (9.6.0) during the process I found that only the screen share is not working when the call is not initiated by a client running 9.2.4, call, chat, and outlook integration works for all versions.
Currently we have a mix of this versions:
9.2.4
9.2.6
9.6.0
My first guess was a misconfiguration problem, but I the phones and users have the correct SIP profile.
Then I thought it was a problem with the COP file, but I checked in CCO and there is not a cop file under "Jabber for Windows" but there is one if you look under "Jabber for iPhone/Android" (Click here)
Last I checked the Jabber-config.xml (find it attached) and there is nothing weird.
What else can I check?
Why only when the call is dialed from Jabber client with version 9.2.4 the screen share works?
Reference links:
https://supportforums.cisco.com/document/103466/uploadinginstalling-cop-file-cucm-cts-18
https://supportforums.cisco.com/document/106926/jabber-config-file-generator
https://supportforums.cisco.com/document/133291/how-verify-cop-file-installed-properly-jabber-android
https://supportforums.cisco.com/document/100421/unable-share-desktop-jabber-windows

Hi Amit,
So to confirm, desktop sharing is only available when the CSFs are actively registered to CUCM and appropriate BFCP configured on the SIP profile? This is the only way to enable desktop sharing when using On Premise deployment?
We currently use Webex Messenger deployment with our internal Jabber and the desktop sharing is avaiable without having to place a call. So gussing its different when using cloud deployment.
This is fairly crucial for a couple of deployments I am working on currently, this coupled with the fact they they are using Citrix clients with Jabber. Call control in Citrix is proving difficult and one of the customers is happy just to have desktop control wiith Jabber and not softphone. But are you saying that desktop sharing is only available when using the softphone?
Cheers
Oli

Jabber Windows - no phone control with LDAP Custom filter

I am unable to control the desktop phone from the Jabber 9.1 Windows client when the CallManager LDAP Directory uses a Custom Filter.
Has anyone else experienced this?
If I set the LDAP Custom Filter to <none> and save, then Desktop Phone control works great.
If I set it to use my custom filter, then trying to enable Desktop control just gives me the spinning circle, then times out to the Red X symbol.
I do not need to resync the LDAP Directory to get the error, just enable/disable the custom filter and save.
In both cases calling from the Computer works great.
This is an On-Prem deployment with full MS-AD LDAP integration.
Versions are:
Jabber - 9.1.0 build 12296
CUPC - 8.6.4.11900-1
CUCM - 8.6.2.22900-9
I upgraded to CUCM 8.6.2 SU2 last night hoping that would fix the problem, but no luck.
The LDAP filter is one I have used in numerous other clusters with no CTI issues.
It allows me to sync to the root directory, but only import active user accounts with an entry in the ipPhone AD attribute:
(&((objectclass=user)(ipPhone=*))(!(objectclass=Computer))(!(UserAccountControl:1.2.840.113556.1.4.803:=2)))
Thanks, Randy

Hi Randy,
Have you specified this base filter in jabber-config.xml file? As per Admin Guide:
"In some cases, base filters do not return query results if you specify a closing bracket in your Cisco Jabber for Windows configuration file. For example, this issue might occur if you specify the following base filter: (&(memberOf=CN=UCFilterGroup,OU=DN))
To resolve this issue, remove the closing bracket; for example, (&(memberOf=CN=UCFilterGroup,OU=DN)"
Thanks,
Maqsood

Jabber Cannot Control Desk Phone

I know, I know. A well-worn topic. But it's just not happening for me, and I'm new to Presence 9.1 This is a new installation. Also using CUCM 9.1 and Jabber 9.2.6. I don't even know where the Jabber error logs are.
Anyway, when I try to get Jabber to control the desk phone, it doesn't work and when I look at the connection status, I get an error stating that there is a connection error to the CTI server. That server is my CUCM Subscriber. I am LDAP integrated, but we are pointing the a global catalog. The CCMCIP service is running, the profile is created and the user is associated with it. On the CUCM user, the phone is associated to the user, the line is set up as the primary extension, and the user is in the Standard CTI and Standard CCMUSER groups. The user is configured to use IM and Presence, and the profile is selected. On the phone, the user is set as the owner and the line appearance is set to the user.
The two things I've seen that might be issues are that we are using the following LDAP filter:
(&(objectclass=user)(!(objectclass=Computer))(!(UserAccountControl:1.2.840.113556.1.4.803:=2))(|(ipphone=*)(samAccountName=adm-*)))
I didn't create this and I don't know enough about filters yet to know if this is good.
Secondly, in my past experience, the configurations for the CTI service (i.e. "cti_1.1.1.1_cti_tcp_host_synced_000" - not the real IP) have always been created automatically, but they had to be created manally for this install. I don't know if that's a function of 9.1 or if there's an integration issue.

Hey Refran,
I had the same issue when doing a LAB installation.
My problem was, that I sometimes used DNS names and sometimes IP Addresses.
After I changed everything to IP Adresses, Jabber was able to connect to the CTI Server.
How did you configure your Servers of CUCM (System--> Server) and the Integration of CUPS and CUCM?
Here a log of Jabber:
REGISTER sip:172.20.10.56 SIP/2.0
Via: SIP/2.0/UDP 172.20.10.56:5060;branch=z9hG4bK000001b4
From: <sip:+41417xxxxx@>;tag=001d72c593ae000200004084-00002998
To: <sip:+41417xxxxx@> -------------------------------------------------------------------------------- here you should see theIP, but in my case this was missing
Call-ID: [email protected]
Max-Forwards: 70
Date: Thu, 27 Jun 2013 21:33:58 GMT
CSeq: 101 REGISTER
User-Agent: Cisco-CSF/9.3.1
My recommendation for your is to test again, after changing everything to IP Adresses.
Otherwise, you can also change the hostfile of the client
Best regards
Ben

Jabber 9 UCM 6 and phone control..

Hello, I'm setting up Presence and Jabber for a client with UCM 6.1. Everthing seems to be working fine except the ability to control desktop phones from Jabber. Although all the settings appear to be ok whenever a user tries to change from softphone to hardphone in Jabber it fails. I have a TAC case open and we are at the..let's pull the same logs again stage..which means they are stumped usually. So my question is..Has anyone out there ever got this to work with CallManager 6? I am begining to suspect that this feature just doesn't work with this version of CallManager. Any help would be much appreciated.
Thanks!
Justin

Supported Servers for On-Premises Deployments
Cisco Unified Communications Manager versions 7.1.4 to 9.0
Note
Cisco Jabber for Windows supports Cisco Unified Communications Manager 7.1.3 if you install the following COP file to enable CSF devices: ciscocm.installcsfdevicetype.cop.sgn.Download ciscocm.installcsfdevicetype.cop.sgn from the Cisco Jabber for Windows administration package on Cisco.com.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

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

Jabber no deskpone control

Similar Messages

Maybe you are looking for