Re: Cisco Jabber Integration - Facing Login issue

sehrlichmcs · ‎02-06-2018

Hello Team,

Can someone, please help me on this issue.

Thanks in advance

I have downloaded sample code 11.7 version and integration in my solution when I am trying to run the application I am facing the LogOut issue.

It is automatically getting LogOut. Please refer my observations below.

[cwic] 6/02/2018 19:38:27.328 resetGlobals: reseting ...

InvalidCertificate.js:58

[cwic][INFO ][19:38:28.299] System Initializing.

InvalidCertificate.js:58

[cwic][INFO ][19:38:28.300] Detected Chrome browser.

InvalidCertificate.js:58

[cwic][INFO ][19:38:28.300] Initializing Chrome extension.

contentscript.js:1

[cwic.ext] waiting for 'init' as extension: ppbllmlcmhfnfflbkbinnhacecaankdh

InvalidCertificate.js:58

[cwic][INFO ][19:38:28.348] Chrome extension has been initialized.

cwic_plugin.js:1

[cwic.ext] 19:38:28.349 loaded with origin: http://localhost:64933

cwic_plugin.js:1

loadExtProps @ cwic_plugin.js:1

init @ cwic_plugin.js:1

e @ InvalidCertificate.js:58

cwic_plugin.js:1

[cwic.ext] 19:38:28.358 append_iframe onload

contentscript.js:1

[cwic.ext] 19:38:28.365 initializing extension channel {cwicExtId: "ppbllmlcmhfnfflbkbinnhacecaankdh", verbose: true, version: "3.1.0.363", system_release: "Cisco Unified Communications System Release 9.3", objectId: "cwic_relay"}

contentscript.js:1

[cwic.ext] 19:38:28.369 Content script connected to Cisco extension: ppbllmlcmhfnfflbkbinnhacecaankdh

contentscript.js:1

[cwic.ext] 19:38:28.369 forward ciscoSDKClientMessage 'init' to background script

contentscript.js:1

[cwic.ext] 19:38:30.290 send ciscoSDKServerMessage 'userauthorized' to client

contentscript.js:1

[cwic.ext] 19:38:30.291 send ciscoSDKServerMessage 'init' to client

InvalidCertificate.js:58

[cwic][DEBUG][19:38:30.293] Received Message: userauthorized {messageId: "5f19859a-9b99-434f-ab48-06d1de39bfc4", name: "userauthorized", content: true}

contentscript.js:1

[cwic.ext] 19:38:38.474 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

InvalidCertificate.js:58

[cwic][DEBUG][19:38:38.476] Received Message: init {messageId: "a5293d2c-70e3-41a2-b9fe-a4cebed5c41f", replyToMessageId: "0", name: "init", content: {…}}

InvalidCertificate.js:58

[cwic][INFO ][19:38:38.477] System Initialized.

contentscript.js:1

[cwic.ext] 19:38:39.330 forward ciscoSDKClientMessage 'setProperty' to background script

contentscript.js:1

[cwic.ext] 19:38:39.333 forward ciscoSDKClientMessage 'setProperty' to background script

contentscript.js:1

[cwic.ext] 19:38:39.334 forward ciscoSDKClientMessage 'setUserCredentials' to background script

InvalidCertificate.js:58

[cwic][DEBUG][19:38:39.336] Received Message: lifecyclestatechanged {messageId: "45a630e9-53a5-4bf4-ab3b-416656b5d7af", name: "lifecyclestatechanged", content: "SIGNEDOUT"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:39.889] Login state has changed to: Signed Out.

contentscript.js:1

[cwic.ext] 19:38:39.890 send ciscoSDKServerMessage 'setUserCredentials' to client

contentscript.js:1

[cwic.ext] 19:38:39.892 send ciscoSDKServerMessage 'userprofileemailaddressrequired' to client

contentscript.js:1

[cwic.ext] 19:38:39.893 send ciscoSDKServerMessage 'setProperty' to client

contentscript.js:1

[cwic.ext] 19:38:39.895 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

contentscript.js:1

[cwic.ext] 19:38:39.896 send ciscoSDKServerMessage 'setProperty' to client

contentscript.js:1

[cwic.ext] 19:38:39.897 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

contentscript.js:1

[cwic.ext] 19:38:39.898 forward ciscoSDKClientMessage 'setProperty' to background script

contentscript.js:1

[cwic.ext] 19:38:39.900 forward ciscoSDKClientMessage 'startSignIn' to background script

InvalidCertificate.js:58

[cwic][DEBUG][19:38:39.901] Received Message: setUserCredentials {messageId: "8e743aea-4534-4521-a3bf-e539f072b4f8", replyToMessageId: "1517926116586928", name: "setUserCredentials", content: ""}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:39.902] Received Message: userprofileemailaddressrequired {messageId: "42ca206d-6672-4b33-9d5d-9f5caa6c6624", name: "userprofileemailaddressrequired", content: {…}}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:39.903] Received Message: setProperty {messageId: "99ce7191-86a0-4da7-b54d-d60aad609dd4", replyToMessageId: "15179261158595324", name: "setProperty", content: {…}}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:39.904] Received Message: lifecyclestatechanged {messageId: "8ee9d3c8-b413-416c-a55b-5bde2ebffe2a", name: "lifecyclestatechanged", content: "DISCOVERING"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:40.369] Login state has changed to: Discovering Services.

InvalidCertificate.js:58

[cwic][DEBUG][19:38:40.370] Received Message: lifecyclestatechanged {messageId:"b5b3f6e7-37a1-405f-8fd2-5ae99cdee1b7", name: "lifecyclestatechanged", content: "SIGNEDOUT"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:40.816] Login state has changed to: Signed Out.

contentscript.js:1

[cwic.ext] 19:38:40.817 send ciscoSDKServerMessage 'setProperty' to client

contentscript.js:1

[cwic.ext] 19:38:40.818 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

contentscript.js:1

[cwic.ext] 19:38:40.818 send ciscoSDKServerMessage 'startSignIn' to client

contentscript.js:1

[cwic.ext] 19:38:40.819 send ciscoSDKServerMessage 'userprofileemailaddressrequired' to client

contentscript.js:1

[cwic.ext] 19:38:40.820 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

contentscript.js:1

[cwic.ext] 19:38:40.820 forward ciscoSDKClientMessage 'setUserProfileEmailAddress' to background script

InvalidCertificate.js:58

[cwic][DEBUG][19:38:40.821] Received Message: setProperty {messageId: "b8193fef-2c68-4068-b4a6-064aa3e061e5", replyToMessageId: "15179261158584249", name: "setProperty", content: {…}}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:40.821] Received Message: setProperty {messageId: "5a12f57e-a2aa-48cb-9bd8-9b0157e4e192", replyToMessageId: "15179261158585214", name: "setProperty", content: {…}}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:40.822] Received Message: lifecyclestatechanged {messageId: "e8276d94-808c-4afe-abb0-c893dc3150c1", name: "lifecyclestatechanged", content: "SIGNEDOUT"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:41.265] Login state has changed to: Signed Out.

contentscript.js:1

[cwic.ext] 19:38:41.266 send ciscoSDKServerMessage 'setUserProfileEmailAddress' to client

contentscript.js:1

[cwic.ext] 19:38:41.268 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

InvalidCertificate.js:58

[cwic][DEBUG][19:38:41.269] Received Message: lifecyclestatechanged {messageId: "036da5c3-89e9-4d18-a16b-a6d26fc31455", name: "lifecyclestatechanged", content: "DISCOVERING"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:41.785] Login state has changed to: Discovering Services.

InvalidCertificate.js:58

[cwic][DEBUG][19:38:41.786] Received Message: setUserProfileEmailAddress {messageId: "4e211c61-b6fc-41f2-86fb-ade7e018e8e1", replyToMessageId: "15179261199034458", name: "setUserProfileEmailAddress", content: ""}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:41.787] Received Message: lifecyclestatechanged {messageId: "a246cf10-48aa-4a08-8e6d-435be0c0a08c", name: "lifecyclestatechanged", content: "DISCOVERING"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:42.193] Login state has changed to: Discovering Services.

InvalidCertificate.js:58

[cwic][DEBUG][19:38:42.194] Received Message: startSignIn {messageId: "81f4807e-039e-47c9-a1ed-36d15f712017", replyToMessageId: "1517926117089257", name: "startSignIn", content: ""}

InvalidCertificate.js:58

[cwic][DEBUG][19:38:42.195] Received Message: userprofileemailaddressrequired {messageId: "121e6f88-879f-4fce-8764-b65b665939ba", name: "userprofileemailaddressrequired", content: {…}}

contentscript.js:1

[cwic.ext] 19:38:42.197 forward ciscoSDKClientMessage 'setUserProfileEmailAddress' to background script

contentscript.js:1

[cwic.ext] 19:38:42.207 send ciscoSDKServerMessage 'setUserProfileEmailAddress' to client

InvalidCertificate.js:58

[cwic][DEBUG][19:38:42.208] Received Message: setUserProfileEmailAddress {messageId: "bc28ac88-97b6-4245-915b-4a7cefac6039", replyToMessageId: "15179261221964824", name: "setUserProfileEmailAddress", content: ""}

contentscript.js:1

[cwic.ext] 19:38:43.114 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

InvalidCertificate.js:58

[cwic][DEBUG][19:38:43.116] Received Message: lifecyclestatechanged {messageId: "755792f2-5498-4134-ba30-c5ed9078b8fb", name: "lifecyclestatechanged", content: "SIGNINGIN"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:43.889] Login state has changed to: Signing In.

contentscript.js:1

[cwic.ext] 19:38:43.890 send ciscoSDKServerMessage 'lifecyclestatechanged' to client

contentscript.js:1

[cwic.ext] 19:38:43.892 send ciscoSDKServerMessage 'userprofilecredentialsrequired' to client

InvalidCertificate.js:58

[cwic][DEBUG][19:38:43.893] Received Message: lifecyclestatechanged {messageId: "b86b3321-48b0-434c-be8d-8a5eb510d43e", name: "lifecyclestatechanged", content: "SIGNEDOUT"}

InvalidCertificate.js:58

[cwic][INFO ][19:38:44.401] Login state has changed to: Signed Out.

InvalidCertificate.js:58

[cwic][DEBUG][19:38:44.402] Received Message: userprofilecredentialsrequired {messageId: "37f06aad-bdcb-45e3-88a4-c81c989dc6e2", name: "userprofilecredentialsrequired", content: {…}}

InvalidCertificate.js:58

[cwic][INFO ][19:38:44.403] Credentials are required.

dstaudt · ‎02-06-2018

It's not clear from the console logs what the issue may be - perhaps username/password. Have tried 'Manual Sign In', providing the CUCM address, and then providing CUCM user credentials associated with a Jabber device (note, the sample should accept username without '@domain' on the end.)

You can get more detailed logs via the info here, which may provide a clue: https://developer.cisco.com/site/jabber-websdk/develop-and-test/voice-and-video/troubleshooting/

For detailed assistance with logs or troubleshooting, I'd suggest opening a DevNet Developer Support ticket:

https://developer.cisco.com/site/devnet/support/

sehrlichmcs · ‎02-06-2018

Hello dstaudt,

Thanks for your quick response.

I will go through the logs once and will check where I am missing it.

sehrlichmcs · ‎02-07-2018

Hello Team,

We are facing "eCapabilityMissing" issue when we are dialing to mobile numbers.

Please see below logs I got it from "Jabber Web SDK" file

2018-02-07 19:02:19,423 ERROR [0x000031f4] [src\jsdk\src\ClientManager.cpp(125) ] [webuc] [webuc::ClientManager::getClientAuthorizationStatus] - [9600] Client with id: 278980.101 doesn't exist

2018-02-07 19:02:19,470 ERROR [0x00002e84] [\cdm\src\win32\VolumeControlImpl.cpp(38)] [csf.cdm] [csf::cdm::VolumeControlImpl::VolumeControlImpl] - Problem with initalizing volume controls

2018-02-07 19:02:19,482 ERROR [0x00002e84] [\adapters\config\ConfigAdapter.cpp(1024)] [ConfigService-ConfigAdapter] [CSFUnified::ConfigAdapter::getConfig] - Config FeatureSet Not Started

2018-02-07 19:02:19,488 ERROR [0x00002e84] [ork\src\framework\LibraryLoader.cpp(118)] [library-loader] [CSFUnified::LibraryLoader::LoadService] - Unable to find service matching the name: class CSFUnified::TelemetryService

2018-02-07 19:02:19,490 ERROR [0x00002e84] [ork\src\framework\LibraryLoader.cpp(202)] [library-loader] [CSFUnified::LibraryLoader::LoadFeatureSet] - Unable to find feature set matching the name class CSFUnified::MediaDeviceFeatureSet

2018-02-07 19:02:19,601 ERROR [0x00002e84] [src\services\impl\LifeCycleImpl.cpp(127)] [Life-Cycle-Logger] [CSFUnified::LifeCycleImpl::Impl::Start] - Error: The current lifecycle state is not ready to start

2018-02-07 19:02:33,985 ERROR [0x00002e84] [apper\src\api\JCFWrapperAPIImpl.cpp(549)] [webuc.jcfwrapper.JCFWrapperAPI] [webuc::JCFWrapperAPIImpl::originate] - Start Audio call failed. No Audio capabilities!

dstaudt · ‎02-07-2018

The snippet above does not seem to refer to 'eCapabilityMissing' - did you intend to attach a log file?

From the above, I might guess that the plugin is unable to initialize media resources (microphone/speakers/camera) - can you share what OS, physical PC hardware, etc. you are testing with? Have you tried using a 'traditional' PC/laptop?