topic can you confirm that the user in Collaboration Applications

jabber error code cj:109:3

ra 011 — Mon, 18 Mar 2019 00:24:03 GMT

jabber cannot control my desk phone and it appears an error code cj:109:3 with unable to connect

Do the phone services connect

sys admin — Mon, 03 Aug 2015 15:20:46 GMT

Do the phone services connect when you start jabber then fail when you swap from desk phone to computer ? i see this error code each time i try and move between desk phone and computer for calls but the phone services connect ok on startup.

I notice that the CSF registers when i start jabber but unregisters when i change from computer to phone then will not register again until i exit from Jabber and restart the application.

I have raised a tac case and will let you know what the outcome is when i know

one more question - are you using cloud based webex connect or an on prem IMP / CUPS solution ?

regards

Hi Sys admin, Jabber

Sankar Voleti — Mon, 03 Aug 2015 15:47:50 GMT

Hi Sys admin,

Jabber client can be operated in only one device mode at a time.That being said,when you switch from Softphone (use my computer for calls) to the Deskphone mode,the CSF device appears unregistered in CUCM and it is the correct behavior.When you login the next time again (without deleting the cache that stores the configuration details),Jabber will use the Deskphone itself for calls as it remembers the last device state from the previous session;that is before logging out.

Hope this helps.

Sankar

Cisco TAC

are you using cloud based

ra 011 — Tue, 04 Aug 2015 13:25:40 GMT

are you using cloud based webex connect or an on prem IMP / CUPS solution ?

Do the phone services connect when you start jabber then fail when you swap from desk phone to computer ?

Can you attach a screenshot

Sankar Voleti — Tue, 04 Aug 2015 13:25:41 GMT

Can you attach a screenshot here?If it's a problem with Deskphone control,knowing the device model and firmware details will help.Is the CCM server enabled for both LDAP Sync and Auth?

Sankar

Cisco TAC

Dear Gangabhavani Sa.my csf

ra 011 — Wed, 05 Aug 2015 08:39:05 GMT

Dear Gangabhavani Sa.

my csf cannot control Deskphone and appears this error cj:109:3 it is working with same deskphone model and firmware version

Raaed, What is the

Sankar Voleti — Wed, 05 Aug 2015 08:39:06 GMT

Raaed,

What is the deskphone model you are using?There are some mandatory roles that the user requires to be able to control the device.And secondly,the ldap information that i mentioned above is required to see where the problem could be.

Sankar

deskphone : cp-7940gfirmware

ra 011 — Wed, 05 Aug 2015 12:18:08 GMT

deskphone : cp-7940g

firmware version : 8.1(sr.2)

Ldap is used for authentication for users

Can you confirm which of the

Sankar Voleti — Wed, 05 Aug 2015 12:25:47 GMT

Can you confirm which of the below two is the issue you are facing?

1. Use my computer for calls is not working (this is Softphone mode)

but

2. Use my phone for calls is working (this is deskphone mode)

If the problem is with Softphone,then can you check the Device Pool of the CSF device to see the CM Group information (whether the CCM is referenced as hostname or IP address)?

-Sankar

Use my phone for calls is

ra 011 — Wed, 05 Aug 2015 12:59:45 GMT

Use my phone for calls is not working (this is deskphone mode)
and appears the error

Okay,if you already have

Sankar Voleti — Wed, 05 Aug 2015 13:21:17 GMT

Okay,if you already have 'Standard CTI Enabled' and 'Standard CTI Allow Control of All Devices' role for this user under User Management page,then i would check the port number used for LDAP authentication.If this problem is happening on all Jabber clients,then ensure that the port is configured to 3268 instead of 389 under LDAP Authentication section of CCM.If it is happening for one specific user,then traces will be required to see what is going on.The MAC address of the device should already be present under 'Controlled Devices' list under User Management page.

Sankar

sorry for delay ( been on

sys admin — Thu, 13 Aug 2015 15:29:20 GMT

sorry for delay ( been on holiday )

can you confirm that the user is associated with the line and that the DN has both the UDP and the CSF as associated devices

on another note -

the problem i face is different in that when Jabber starts the csf does register in CUCM. When i change this to use phone for calls that also works (no problems so far) the issue is when i try then to change back to use computer for calls - this is when the CSF does not register again and gives the error code CJ:109:3 - this code is not very helpful as it signifies an unknown error ?

also note that when i exit from Jabber whilst i am using the deskphone to make calls and the phone services for that are connected ok - i then log back into jabber and neither the deskphone or softphone have a connected status. sometimes (but not every time) there is a red cross on the phone icon and i have to manually select use my computer / deskphone for calls for either of them to get a connected status.

sometimes when i log back on after exiting whilst using the deskphone for calls the deskphone will be connected ok again and i can then change to use my computer for calls and the CSF will register (once) if i then try and change back to phone and then back to computer i get the 109 error.

this appears to be arbitrary

regards

Have you found a solution for

oliverpowell — Fri, 04 Sep 2015 09:33:00 GMT

Have you found a solution for this?

We are seeing a similar problem with users and the 7821 SIP phones. There are no differences with how users, UDPs and devices are setup. But some users are able to control their device via CTI, others are not with the error CJ:109:3

This sounds like it could be a PC issue. The users have a mixture of WIN7 and 8.1, both can control and both cannot.

Any ideas?

Oli

we have a webex connect

sys admin — Mon, 07 Sep 2015 14:01:05 GMT

we have a webex connect presence solution but managed by our engineers in japan so I cannot tell you if there were any significant changes there other than I got them to allow us to manually select the TFTP, CCMCIP and CTI servers on the jabber client.

I also updated all the jabber client CSFs with a new SIP profile with the 3 bottom SDP info settings ticked. this was the same sip profile used on our sip trunk to our Japan cluster.

At the same time I updated the device pool that the CSFs are in to have the same CUCM group, MRGL, region and location that my sip trunk to our japan cluster was also in. (this was more to do with having multiple jabber clients being able to call into a TP MCU in Japan but it may have played a part in rectifying our connection error)

These actions have possibly rectified our issue but as I said I do not have any information regarding changes that may have been made on webex connect by our engineers in Japan who I know were working with the cisco vendor there.

Hope some of this helps.

Replaced several 6945 and

jdornberger2013 — Fri, 25 Sep 2015 15:03:00 GMT

Replaced several 6945 and 8945 with 8845 phones and Jabber is "unable to connect" (CJ:109:3) to the new phones (the users were already using Jabber on their old deskphones).

I have the same thing with

gregchavarria — Tue, 03 Nov 2015 21:09:12 GMT

I have the same thing with cisco 8861 phone. I am unable to use jabber after I connected this phone. please see below connection status.ase help!

can you confirm that the user

sys admin — Wed, 04 Nov 2015 09:15:35 GMT

can you confirm that the user is associated with the line and that the DN has both the UDP (if using EM) and the CSF as associated devices.

can you also try adding Standard CTI allow control of all devices to the permissions info for the user.

regards

Hi,

Sankar Voleti — Wed, 04 Nov 2015 11:07:11 GMT

Hi,

Please check if "Standard CTI Allow Control of Phones supporting Connected Xfer and conf" and "Standard CTI Allow Control of Phones supporting Rollover Mode" are assigned to the end user in CCM End User page.These are required for 88XX,99XX and 69XX phones.If the roles are already in place,then we will have to analyze the Jabber problem report and packet captures from the laptop/PC.

-Sankar

it seems there is a bug with

lorenz84gDD — Thu, 05 Nov 2015 10:38:56 GMT

it seems there is a bug with 88xx phones so that they lose connectivity to the network every now and then. upgrade to the latest fw version in order to fix this...

Added roles - problem solved.

jdornberger2013 — Thu, 05 Nov 2015 15:20:36 GMT

Added roles - problem solved. Thanks!