Unable to login Unified CCX Agent - Revision history

Sansahoo: Removing all content from page

2010-10-19T08:43:04Z

Removing all content from page

← Older revision		Revision as of 08:43, 19 October 2010
Line 1:		Line 1:
-	~~== Unified CCX agent is unable to log in ==~~
-	~~<BR>~~
-	~~{\| border="1"~~
-	\|-
-	~~! '''Problem Summary'''~~
-	~~\| Unified CCX agent is unable to log in using CAD/CAD-BE.~~
-	\|-
-	~~! '''Error Message'''~~
-	~~\| Depending on the type of failure, various error popups can be seen on CAD.~~
-	\|-
-	~~! '''Possible Cause'''~~
-	\|
-	~~There can be many causes for agent login failure. Some of the causes are: <BR>~~
-	~~'''1.''' The given ID of agent is wrong.<BR>~~
-	~~'''2.''' The IPCC extension given by agent is wrong.<BR>~~
-	~~'''3.''' Network connectivity issue between CAD and Unified CCX. <BR>~~
-	~~'''4.''' The password given by Agent is wrong.<BR>~~
-	~~'''5.''' Agent's Phone is not associated with RM JTAPI provider (RM Appuser) is CUCM.<BR>~~
-	~~'''6.''' Agent's Phone has more than 4 lines.<BR>~~
-	~~'''7.''' Agent's Phone has a shared line (IPCC extension) which is shared amongst more than one phone.<BR>~~
-	~~'''8.''' An extension on agent's phone is not unique. The same extension is configured on different partitions in CUCM.<BR>~~
-	~~'''9.''' Agent is using a phone which is using IPv6 addressing.<BR>~~

-	\|-
-	~~! '''Recommended Action'''~~
-	\|
-	'''Step 1.''' Check whether agentID and IPCC extension associated with that resource is showing up of '''Resources''' page of Appadmin (Appadmin > Subsystems > RmCm > Resources). If the agent does not exist then check whether that agent is deleted from CUCM or not.
-
-	'''Step 2.''' If the agent is shown on '''Resources''' page and still agent is unable to login, then Open CDA and click on '''Setup > Synchronize Directory Services'''. Relaunch CAD and try to login agent again. If login still doesn;t work then try further steps
-
-	~~'''Step 3.''' Enable log facilities in following log levels <BR>~~
-	~~<pre>~~
-	~~1. SS_RM DEBUG~~
-	~~2. ICD_CTI DEBUG~~
-	~~3. Enable debug logging on CAD</pre> <BR>~~
-
-	~~'''Step 4.''' Try to login agent from CAD which will fail <BR>~~
-	~~<BR>~~
-	~~'''Step 5.''' Download MIVR logs from Unified CCX for the timeframe when Agent tried to login using the RTMT tool.<BR>~~
-	~~<BR>~~
-	'''Step 6.''' Try to find the login request coming from CAD to Unified CCX. For this Search for '''"SET_AGENT_STATE_REQ"''' in MIVR logs, which is coming from IP address where CAD is installed. In following example we can see that login request for agent "an1" is coming from IP address "64.103.254.206".<BR>
-	~~<pre>~~
-	938197: Dec 01 11:41:52.484 IST %MIVR-ICD_CTI-7-UNK:ClientConnMgr: Processing msg on socket:Socket[addr=64.103.254.206,port=3067,localport=12028] Msg is {length=45 type=SET_AGENT_STATE_REQ,invokeId=2,agentState=LOGIN,eventReasonCode=0,forcedFlag=False,agentID=an1,agentDN=3001,agentPwd=***** }</pre>
-	~~<BR>~~
-	If you do not see login request coming in logs, then check whether agent is using the agent ID in correct case and whether the specified IPCC extension is correct. If agentID and IPCC specified is correct then there might be some network issue. Collect CAD and MIVR logs and raise a case.
-	~~<BR><BR>~~
-	'''Step 7.''' Try to find the response which Unified CCX is sending for this login request,For this Search for '''"CONTROL_FAILURE_CONF"''' in MIVR logs, which is being sent to the IP address from where the login request came. Note that the invokeId field of login message and response message is same (in this case "2"). This tells that the message being sent is in response to login request.<BR>
-	~~<pre>~~
-	938208: Dec 01 11:41:52.929 IST %MIVR-ICD_CTI-7-UNK:OutboundMessageprocessor : sending msg : { length=-1 type=CONTROL_FAILURE_CONF,invokeId=2,failureCode=CF_INVALID_PASSWORD_SPECIFIED,errorCode=0, text=Unable to authenticate Resource. to socket: Socket[addr=64.103.254.206,port=3067,localport=12028] } </pre>
-	~~<BR><BR>~~
-	~~'''Step 8.''' Note the failureCode field. This specifies the cause of login failure. Following is the list of common login failure codes:~~
-	~~<BR>~~
-	* '''CF_INVALID_PASSWORD_SPECIFIED''' : Agent specified the wrong password.
-	~~<BR>~~
-	* '''CF_SPECIFIED_AGENT_ALREADY_SIGNED_ON''' : Agent is already logged on. CAD will give an option to force-login when it receives this error.
-	~~<BR>~~
-	* '''CF_SPECIFIED_EXTENSION_ALREADY_IN_USE''' : Someother agent is logged on the same IPCC extension. CAD will give an option to force-login when it receives this error.
-	~~<BR>~~
-	* '''CRS_JTAPI_CCM_PROBLEM''' : Cannot login due to problem in CUCM. Check whether agent's device is associated with RM JTAPI provider (Application user)in CUCM. If problem persists then please collect JTAPI client logs in all debug levels and raise a case.
-	~~<BR>~~
-	* '''CF_MAXIMUM_LINE_LIMIT_EXCEEDED''' : Agent phone has more than 4 lines. Reduce the number of lines on agent's phone from CUCM.
-	~~<BR>~~
-	* '''CF_SHARED_LINES_NOT_SUPPORTED''' : One or more lines associated with the agent's device is being shared by multiple phones. Each line on agent phone should be associated with only agent's device. Remove the line from other device. Error can also occur in [http://docwiki-dev.cisco.com/wiki/Unable_to_login_Unified_CCX_Agent_in_an_Extension_Mobility_setup Extension Mobility configurations].
-	~~<BR>~~
-	* '''CF_EXTENSION_NOT_UNIQUE''' : One or more lines associated with the agent's device is not unique and is configured on different partitions. Remove the line from other partitions.
-	~~<BR>~~
-	* '''CRS_AGENT_DEVICE_IPv6''' : Agent's device is using IPV6 addressing. These devices are not compatible with CAD. So use IPV4 addressing for agent's device.
-	~~<BR>~~
-	* '''CRS_LINE_RESTRICTED''' : Cannot login due to problem in CUCM. Please collect JTAPI client logs in all debug levels and raise a case.
-	~~<BR>~~
-	* '''CRS_DEVICE_RESTRICTED''' : Cannot login due to problem in CUCM. Please collect JTAPI client logs in all debug levels and raise a case.
-	~~<BR>~~
-	~~<BR>~~
-	~~'''Step 9.'''If the problem is still not solved then collect logs in following log levels and raise a support case.~~
-	~~<pre>~~
-	~~1. SS_RM DEBUG~~
-	~~2. ICD_CTI DEBUG~~
-	~~3. Enable debug logging on CAD~~
-	~~4. JTAPI client logs in all debug levels~~
-	~~</pre> <BR>~~
-	\|-
-	~~! '''Release'''~~
-	~~\| 8.0(1)~~
-	\|-
-	~~! '''Associated CDETS #'''~~
-	~~\| None.~~
-	\|-
-	\|}
-
-	~~<BR>~~
-	~~[[Category:Unified CCX, Release 8.0]]~~

Sansahoo: /* Unified CCX agent is unable to log in */

2010-10-19T08:37:47Z

Unified CCX agent is unable to log in

← Older revision		Revision as of 08:37, 19 October 2010
Line 1:		Line 1:
-	== ~~Unable to login~~ Unified CCX ~~Agent~~ ==	+	== Unified CCX agent is unable to log in ==
	<BR>		<BR>
	{\| border="1"		{\| border="1"
	\|-		\|-
	! '''Problem Summary'''		! '''Problem Summary'''
-	\| Unified CCX ~~Agent~~ is unable to ~~login~~ using CAD/CAD-BE	+	\| Unified CCX agent is unable to log in using CAD/CAD-BE.
	\|-		\|-
	! '''Error Message'''		! '''Error Message'''
-	\| Depending on the type of failure, error ~~pop ups~~ can be seen on CAD.	+	\| Depending on the type of failure, various error popups can be seen on CAD.
	\|-		\|-
	! '''Possible Cause'''		! '''Possible Cause'''
	\|		\|
-	There can be many causes for agent login failure. Some of the causes are : <BR>	+	There can be many causes for agent login failure. Some of the causes are: <BR>
	'''1.''' The given ID of agent is wrong.<BR>		'''1.''' The given ID of agent is wrong.<BR>
	'''2.''' The IPCC extension given by agent is wrong.<BR>		'''2.''' The IPCC extension given by agent is wrong.<BR>

Cchetty: 1 revision

2010-04-09T15:21:01Z

1 revision

← Older revision

Revision as of 15:21, 9 April 2010

Habui: /* Unable to login Unified CCX Agent */

2010-01-12T22:33:44Z

Unable to login Unified CCX Agent

New page

== Unable to login Unified CCX Agent ==
 
{| border="1"
|-
! '''Problem Summary'''
| Unified CCX Agent is unable to login using CAD/CAD-BE
|-
! '''Error Message'''
| Depending on the type of failure, error pop ups can be seen on CAD.
|-
! '''Possible Cause'''
|
There can be many causes for agent login failure. Some of the causes are : 
'''1.''' The given ID of agent is wrong. 
'''2.''' The IPCC extension given by agent is wrong. 
'''3.''' Network connectivity issue between CAD and Unified CCX. 
'''4.''' The password given by Agent is wrong. 
'''5.''' Agent's Phone is not associated with RM JTAPI provider (RM Appuser) is CUCM. 
'''6.''' Agent's Phone has more than 4 lines. 
'''7.''' Agent's Phone has a shared line (IPCC extension) which is shared amongst more than one phone. 
'''8.''' An extension on agent's phone is not unique. The same extension is configured on different partitions in CUCM. 
'''9.''' Agent is using a phone which is using IPv6 addressing. 

|-
! '''Recommended Action'''
|
'''Step 1.''' Check whether agentID and IPCC extension associated with that resource is showing up of '''Resources''' page of Appadmin (Appadmin > Subsystems > RmCm > Resources). If the agent does not exist then check whether that agent is deleted from CUCM or not.

'''Step 2.''' If the agent is shown on '''Resources''' page and still agent is unable to login, then Open CDA and click on '''Setup > Synchronize Directory Services'''. Relaunch CAD and try to login agent again. If login still doesn;t work then try further steps

'''Step 3.''' Enable log facilities in following log levels 
<pre>
1. SS_RM DEBUG
2. ICD_CTI DEBUG
3. Enable debug logging on CAD</pre> 

'''Step 4.''' Try to login agent from CAD which will fail 
 
'''Step 5.''' Download MIVR logs from Unified CCX for the timeframe when Agent tried to login using the RTMT tool. 
 
'''Step 6.''' Try to find the login request coming from CAD to Unified CCX. For this Search for '''"SET_AGENT_STATE_REQ"''' in MIVR logs, which is coming from IP address where CAD is installed. In following example we can see that login request for agent "an1" is coming from IP address "64.103.254.206". 
<pre>
938197: Dec 01 11:41:52.484 IST %MIVR-ICD_CTI-7-UNK:ClientConnMgr: Processing msg on socket:Socket[addr=64.103.254.206,port=3067,localport=12028] Msg is {length=45 type=SET_AGENT_STATE_REQ,invokeId=2,agentState=LOGIN,eventReasonCode=0,forcedFlag=False,agentID=an1,agentDN=3001,agentPwd=***** }</pre>
 
If you do not see login request coming in logs, then check whether agent is using the agent ID in correct case and whether the specified IPCC extension is correct. If agentID and IPCC specified is correct then there might be some network issue. Collect CAD and MIVR logs and raise a case.
 
'''Step 7.''' Try to find the response which Unified CCX is sending for this login request,For this Search for '''"CONTROL_FAILURE_CONF"''' in MIVR logs, which is being sent to the IP address from where the login request came. Note that the invokeId field of login message and response message is same (in this case "2"). This tells that the message being sent is in response to login request. 
<pre>
938208: Dec 01 11:41:52.929 IST %MIVR-ICD_CTI-7-UNK:OutboundMessageprocessor : sending msg : { length=-1 type=CONTROL_FAILURE_CONF,invokeId=2,failureCode=CF_INVALID_PASSWORD_SPECIFIED,errorCode=0, text=Unable to authenticate Resource. to socket: Socket[addr=64.103.254.206,port=3067,localport=12028] } </pre>
 
'''Step 8.''' Note the failureCode field. This specifies the cause of login failure. Following is the list of common login failure codes:
 
* '''CF_INVALID_PASSWORD_SPECIFIED''' : Agent specified the wrong password.
 
* '''CF_SPECIFIED_AGENT_ALREADY_SIGNED_ON''' : Agent is already logged on. CAD will give an option to force-login when it receives this error.
 
* '''CF_SPECIFIED_EXTENSION_ALREADY_IN_USE''' : Someother agent is logged on the same IPCC extension. CAD will give an option to force-login when it receives this error.
 
* '''CRS_JTAPI_CCM_PROBLEM''' : Cannot login due to problem in CUCM. Check whether agent's device is associated with RM JTAPI provider (Application user)in CUCM. If problem persists then please collect JTAPI client logs in all debug levels and raise a case.
 
* '''CF_MAXIMUM_LINE_LIMIT_EXCEEDED''' : Agent phone has more than 4 lines. Reduce the number of lines on agent's phone from CUCM.
 
* '''CF_SHARED_LINES_NOT_SUPPORTED''' : One or more lines associated with the agent's device is being shared by multiple phones. Each line on agent phone should be associated with only agent's device. Remove the line from other device. Error can also occur in [http://docwiki-dev.cisco.com/wiki/Unable_to_login_Unified_CCX_Agent_in_an_Extension_Mobility_setup Extension Mobility configurations].
 
* '''CF_EXTENSION_NOT_UNIQUE''' : One or more lines associated with the agent's device is not unique and is configured on different partitions. Remove the line from other partitions.
 
* '''CRS_AGENT_DEVICE_IPv6''' : Agent's device is using IPV6 addressing. These devices are not compatible with CAD. So use IPV4 addressing for agent's device.
 
* '''CRS_LINE_RESTRICTED''' : Cannot login due to problem in CUCM. Please collect JTAPI client logs in all debug levels and raise a case.
 
* '''CRS_DEVICE_RESTRICTED''' : Cannot login due to problem in CUCM. Please collect JTAPI client logs in all debug levels and raise a case.
 
 
'''Step 9.'''If the problem is still not solved then collect logs in following log levels and raise a support case.
<pre>
1. SS_RM DEBUG
2. ICD_CTI DEBUG
3. Enable debug logging on CAD
4. JTAPI client logs in all debug levels
</pre> 
|-
! '''Release'''
| 8.0(1)
|-
! '''Associated CDETS #'''
| None.
|-
|}

 
[[Category:Unified CCX, Release 8.0]]