CUCM 10.5 webdialer and SSO

Hi everyone,

We have installed a brand new cucm 10.5 and we want to use Cisco Webdialer (SOAP) to make call from our CRM.

So it works but we have a 2 or 3 secondes delay that is due to SSO self-test, when making calls

As you can see in the logs, the webdialer take 2 or 3 secondes to find that SSO service  is disabled:

2015-01-12 11:18:19,054 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - UserIdwebdialer
2015-01-12 11:18:19,054 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - tokennull
2015-01-12 11:18:19,056 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl -

https://172.16.124.100/ssosp/ws/public/singleSignOn
2015-01-12 11:18:19,879 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl -
SSO TEST INFERENCE
Is CUCM server 172.16.124.100 SSO enabled  ? false
2015-01-12 11:18:19,880 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - This is NONSSO Mode :  userid passed, password passed : positive scenario We will return  CallResponse with new message
2015-01-12 11:18:19,880 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - prof.getUser()webdialer
2015-01-12 11:18:19,881 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - cred.getUserID()webdialer
2015-01-12 11:18:19,882 DEBUG [http-bio-443-exec-52] webdialer.Credential - tokennull
2015-01-12 11:18:19,882 DEBUG [http-bio-443-exec-52] webdialer.Credential - gettokennull
2015-01-12 11:18:19,883 DEBUG [http-bio-443-exec-52] webdialer.Credential - getPasswordwebdialer
2015-01-12 11:18:19,883 DEBUG [http-bio-443-exec-52] webdialer.Credential - getUserIDwebdialer
2015-01-12 11:18:19,884 DEBUG [http-bio-443-exec-52] webdialer.Credential -

https://172.16.124.100/ssosp/ws/public/singleSignOn
2015-01-12 11:18:20,564 DEBUG [http-bio-443-exec-52] webdialer.Credential -
SSO TEST INFERENCE
Is CUCM server 172.16.124.100 SSO enabled  ? false
2015-01-12 11:18:20,688 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl -

https://172.16.124.100/ssosp/ws/public/singleSignOn
2015-01-12 11:18:21,393 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl -
SSO TEST INFERENCE
Is CUCM server 172.16.124.100 SSO enabled  ? false
2015-01-12 11:18:21,394 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - Dial Rule apply:true
2015-01-12 11:18:21,395 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - Dest before:00660431792
2015-01-12 11:18:21,396 DEBUG [http-bio-443-exec-52] webdialer.WebdialerSoapServiceImpl - Dest after:00660431792
2015-01-12 11:18:21,396 DEBUG [http-bio-443-exec-52] webdialer.CTIProvider - openline to make call
2015-01-12 11:18:21,417 DEBUG [http-bio-443-exec-52] webdialer.CTIProvider - com.cisco.ccm.webdialer.CTIProvider@9c5aa3.openLine() - opened device:SEP6899CD844F6E
2015-01-12 11:18:21,418 DEBUG [http-bio-443-exec-52] webdialer.CTIProvider - com.cisco.ccm.webdialer.CTIProvider@9c5aa3.openLine() - opened line:5977on partition on device:SEP6899CD844F6E
2015-01-12 11:18:21,421 DEBUG [(P2-172.16.124.100) EventThread] webdialer.CTIProvider - No thread for this device in HT:SEP6899CD844F6E
2015-01-12 11:18:21,649 DEBUG [http-bio-443-exec-52] webdialer.CTIProvider - com.cisco.ccm.webdialer.CTIProvider@9c5aa3.closeLine() - closed line 5977
2015-01-12 11:18:21,651 DEBUG [http-bio-443-exec-52] webdialer.CTIProvider - com.cisco.ccm.webdialer.CTIProvider@9c5aa3.closeDevice() - closed device SEP6899CD844F6E
2015-01-12 11:18:21,652 DEBUG [http-bio-443-exec-52] webdialer.CTIProvider - com.cisco.ccm.webdialer.CTIProvider@9c5aa3.closeDevice() - Removed device SEP6899CD844F6E from control list

As we are in a call center context, we want to reduce at a minimum value the reactivity of the Webdialer service. Does anyone know i can speed up the makecall so that there is no SSO self-test?

thank you in advance for your help.

regards

Nat

Hi Nat,

I believe this is a known defect to be fixed in 10.5(1.99995.9).

Hi Nicholas,

Do you think this fix could already be part of the 10.5(2) ?

Yes, it appears to be fixed in 10.5(2) but I am double-checking with the engineers since a couple dates don't match the way they should.  We do have an Engineering Special where it's fixed, if not.  I'm including the ES version here for my own reference:  10.5.(1.12016-1)

I'll come back and let you know what I hear from the engineers. 

Good news everyone!  (Said in my best Professor Farnsworth voice.)

I got confirmation from the engineers that the fix is in 10.5(2). 

Hi Nicholas,

many thanks for your investigation. we will update to 10.5.2 to make some more tests..

regards

Nathaniel