Login is unavailable (23) EMCC

[Pawan Arora]

HI,

I have configured EMCC on my three cluster successfully with no error while validating the configuration. But when i tried to login to the 7942 phone, it gives me an error "login is unavailable (23) "

Please help me with this.

Regards,

Pawan Arora

[Ayodeji Okanlawon]

Pawan,

Have you enabled EMCC for the user ?

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[Pawan Arora]

Yes, it is enabled the EMCC for the end user

[Pawan Arora]

I have genrated the logs for EM from call manager. Below are the logs

2012-07-18 14:19:48,484 INFO  [http-8443-17        ] EMServiceServlet          - EMService Request# ----> : 1925

2012-07-18 14:19:48,485 INFO  [http-8443-17        ] EMServiceServlet          - 1925:EMService: Request Type=EMCC

2012-07-18 14:19:48,488 INFO  [http-8443-17        ] EMServiceServlet          - 1925: processEmccRequest: Received EMCC Login Request for :4080

2012-07-18 14:19:48,488 INFO  [http-8443-17        ] EMServiceServlet          - 1925: Executing authenticate2...

2012-07-18 14:19:48,489 INFO  [http-8443-17        ] EMServiceServlet          - 1925: authenticate2: Authenticate request.

2012-07-18 14:19:48,489 INFO  [http-8443-17        ] Authenticator             - 1925:Authenticator.authenticateTransaction: AppID: CCMSysUser- Checking values in credential cache

2012-07-18 14:19:48,489 INFO  [http-8443-17        ] Authenticator             - 1925:Authenticator.authenticateTransaction: AppID: CCMSysUser- Approved through credential cache, 109346 ms remaining

2012-07-18 14:19:48,489 INFO  [http-8443-17        ] EMServiceServlet          - 1925:EMService Authentication succeeded

2012-07-18 14:19:48,489 INFO  [http-8443-17        ] PolicyValidator           - 1925:PolicyValidator.checkDeviceAllowsLogin: Dev: SEP3CCE7359CA5C- Calling dbr.getDeviceObject

2012-07-18 14:19:48,490 INFO  [http-8443-17        ] DBRequestor               - 1925:Getting device object - loginInfo, caller

2012-07-18 14:19:48,490 INFO  [http-8443-17        ] DBRequestor               - 1925: PolicyValidator.checkDeviceAllowsLogin: Dev: SEP3CCE7359CA5C- Getting device object

2012-07-18 14:19:48,492 INFO  [http-8443-17        ] CMDatabase                - CMDatabase:getDeviceInfo: SELECT device.pkid, loginduration, decode(extensionmobilitydynamic.logintime, null, emremotedynamic.logintime, extensionmobilitydynamic.logintime)logintime, allowhotelingflag, extensionmobilitydynamic.fkenduser, decode(extensionmobilitydynamic.fkenduser, null, remoteuserid, e2.userid) currentuserid, fkenduser_lastlogin lastloginpkid,decode(fkenduser_lastlogin,null,lastremoteuserid,e1.userid) lastuserid, extensionmobilitydynamic.tkuserlocale, fkdevicepool, tkdeviceprotocol, tkproduct, tkmodel FROM Device left outer join extensionmobilitydynamic on device.pkid=extensionmobilitydynamic.fkdevice left outer join emremotedynamic on (extensionmobilitydynamic.fkdevice=emremotedynamic.fkdevice) left outer join enduser e1 on (extensionmobilitydynamic.fkenduser_lastlogin=e1.pkid) left outer join enduser e2 on (extensionmobilitydynamic.fkenduser=e2.pkid) where my_lower(device.name) like my_lower('SEP3CCE7359CA5C')

2012-07-18 14:19:48,498 INFO  [http-8443-17        ] CMDatabase                - getDeviceInfo:Device query executed

2012-07-18 14:19:48,498 INFO  [http-8443-17        ] CMDatabase                - getDeviceInfo:Result of the query: {tkproduct=333, loginduration=, lastuserid=6341, tkdeviceprotocol=0, pkid=e5760774-a54d-4245-8c77-cffc00061368, fkenduser=, tkmodel=434, logintime=, lastloginpkid=81692854-5108-4fc1-87b5-789bd9f9a507, currentuserid=, allowhotelingflag=t, fkdevicepool=032a0acc-ef20-1030-4523-dd9ddbde69fa, tkuserlocale=1}

2012-07-18 14:19:48,498 INFO  [http-8443-17        ] DBRequestor               - 1925: PolicyValidator.checkDeviceAllowsLogin: Dev: SEP3CCE7359CA5C- Device object returned

2012-07-18 14:19:48,498 INFO  [http-8443-17        ] PolicyValidator           - 1925:PolicyValidator.checkDeviceAllowsLogin: Dev: SEP3CCE7359CA5C- dbr.getDeviceObject returned

2012-07-18 14:19:48,499 INFO  [http-8443-17        ] EmccData                  - osQuery = SELECT COUNT(*) as value FROM ProductSupportsFeature p INNER JOIN Device d on (p.tkProduct =  d.tkProduct AND p.tkDeviceProtocol IN (99, d.tkDeviceProtocol )) INNER JOIN TypeSupportsFeature t ON p.tkSupportsFeature = t.Enum WHERE d.name = 'SEP3CCE7359CA5C' AND t.Moniker = 'SUPPORTS_FEATURE_EMCC'

2012-07-18 14:19:48,502 INFO  [http-8443-17        ] PolicyValidator           - 1925:PolicyValidator.checkCurrentLogin: getCurrentLoginTime return value- 0

2012-07-18 14:19:48,502 INFO  [http-8443-17        ] PolicyValidator           - 1925:PolicyValidator.checkCurrentLogin: no user currently logged in

2012-07-18 14:19:48,502 INFO  [http-8443-17        ] EMServiceServlet          - 1925 findHomeCluster: Finding Home Cluster for User: 4080

2012-07-18 14:19:48,503 ERROR [http-8443-17        ] EMServiceServlet          - 1925: Userid not exist in this cluster

2012-07-18 14:19:48,503 INFO  [http-8443-17        ] EMServiceServlet          - 1925: EmccRequest Processing Time: 18

2012-07-18 14:19:48,503 ERROR [http-8443-17        ] EMServiceServlet          - 1925: Error processing EMCC request :Userid not exist in this cluster

It is just searching in the home cluster not in the remote cluster

[ronpatel]

Hi Pawan,

Below video shows the steps involved and you will get to know where you are doing things wrong.

https://supportforums.cisco.com/videos/1970

Go through the video and see if it helps.

Regards

Ronak patel

Rate helpful posts.

[Pawan Arora]

Hi Ronak,

I have used the same video to configure the EMCC.

[RAVIKUMAR J K]

Hi All,

Though this is pretty old thread, thought I would post my experience with this error

" Login is unavailable (23) "

it may help someone.

I was getting this error despite  all services (EMCC, PSTN Access, TFTP etc) were showing activation status true for  remote  cluster.

Following procedure helped fix in my case.

1. Deleted remote cluster info on involved clusters (Advanced features --> Cluster View).

2. Changed cluster IDs for involved clusters. (System-->Enterprise parameters)

3. Created remote cluster view again on both the clusters and update EMCC Remote cluster now.(Advanced features --> Cluster View).

thanks!!!

[cshannon1077]

I had a user in our heavily used mobility core site that was getting this error 23 which was not phone specific. It turned out he had changed his PIN and forgot. Resetting proved to solve the problem. Nice to find simple fixes!

[ronpatel]

Hi

also

Login is unavailable(23) =

When the end user configuration is absent in both local and remote cluster, or

- EMCC service is not enabled on remote cluster (HC).

(User is authenticated on remote cluster only if EMCC is enabled.) Click  Update Remote Cluster Now from VC Remote Cluster Configuration page and  check if HC's EMCC service is enabled.

Regards

Ronak patel

Rate helpful posts.

[Pawan Arora]

HI Ronak,

Emcc is already enabled on both the clusters. Do you want me to disable the services and re-enabled it on both the clusters

Regards,

Pawan

[ronpatel]

HI

Have you created same user in two cluster and deleted that user in one cluster.

Regards

Ronak Patel

[Ayodeji Okanlawon]

Here is an excellent video that shows how to enable/configure EMCC..See what step you are missing

http://www.youtube.com/watch?v=WBHwy6-Uebg

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[Pawan Arora]

thats the same video which was shared by Ronak

[Pawan Arora]

Ronak,

there is one parameter "

Enable All Remote Cluster Services When Adding A New Remote Cluster " in EMCC feature configuration which is set to false. do i need to set it to true.

Regards,

Pawan

[Pawan Arora]

no...user only exists in one cluster