Forced Login

Version 1
    This document was generated from CDN thread

    Created by: amit gandhi on 30-08-2012 09:59:22 AM
    HI,
          In SET_AGENT_STATE_REQ there is a ForcedFlag no matter what we set its value(0,1,2), agent can always forcefully login even if same id and extension is in use.
     
    On login I am sending these values
     
    AgentState AGENT_STATE_LOGIN (0)
    EventReasonCode 0
    ForcedFlag 0
    AgentExtension "1234"
    AgentID "agentid" 
    AgentPassword "password" 
     
    Any ideas what is missing or which value is sent wrong?
     
    thx

    Subject: RE: Forced Login
    Replied by: David Lender on 30-08-2012 03:20:00 PM
    Your values appear correct.  Suggest a review of the MIVR logs to see what is really happening.

    Subject: RE: Forced Login
    Replied by: amit gandhi on 31-08-2012 02:47:23 AM
    Your values appear correct.  Suggest a review of the MIVR logs to see what is really happening.

     
    As per MIVR logs
    {length=42 type=SET_AGENT_STATE_REQ,invokeId=4,agentState=LOGIN,eventReasonCode=1,forcedFlag=True,agentID=gandhi,agentDN=0909,agentPwd=***** }
     
    forced flag received is true.  
     
    I have gone through my application logs we are sending 0.  Actually no matter what I send (0,1,2,3,4,.A..Z), in MIVR it always comes as forced true.
     
    I am using CTI protocol version 11 with UCCX 8.5.
     
    Is there any possibility it is a version issue?
     
    thx

    Subject: RE: New Message from amit gandhi in Unified Contact Center Express CTI (UCC
    Replied by: David Lender on 31-08-2012 09:08:11 AM
    If you turn up tracing on the MIVR log you should be able to see the actual message you are sending.   If error persists, try using a newer protocol version such as 14 and see if that resolves the issue.
    If it does not, open a Service Request for CDN – Contact Center Applications and provide the MIVR log showing that you are sending 0 and its showing up as True.