CCX 9.0.2 Agent Status

Hello,
Has anyone experienced this with CCX 9.0.2?
CCX realtime reports show that agent is in ready state.
Cisco Supervisor Desktop also shows ready state.
The Agent is sitting around waiting for a call and notices that calls aren't coming to him. He then realizes that his actual phone is not ready. He has to update his status in order to get it back into ready state.
CCX agent user configuration is set to Automatically go back to Available.
Doesn't happen all the time, but has been reported with several different people, in different departments, in different queues.
Ideas?
thanks

I am looking back at old TAC cases and in my case there was never an actual documented Bug ID specified within our email correspondence. It was just recommended to upgrade to su2. I know that isn't the concrete evidence you are looking for but it may be a starting point.
Hope this helps!
Tony
Please rate helpful posts

Similar Messages

Emctl agent status command not working

Every time I issue the command "emctl agent status", I get the following message:
EM Configuration issue. /u01/app/oracle/product/OSE_10.2.0.1.0/itt.ppd.ppd-ds.com_HSI1t not found
I've tried various environments. How can I determine the agent status?
Baffling product :)
Thanks
John

C:\>emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.1.0.2.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
Agent Version     : 10.1.0.2.0
OMS Version       : 10.1.0.2.0
Protocol Version : 10.1.0.2.0
Agent Home        : D:\oracle\product\10.1.0\Db_1\ALwarid-Taj.fakhruddin.local_t
aj
Agent binaries    : D:\oracle\product\10.1.0\Db_1
Agent Process ID : 2992
Agent Process ID : 2992
Agent URL         : http://ALwarid-Taj.fakhruddin.local:1832/emd/main
Started at        : 2006-10-08 08:46:10
Started by user   : SYSTEM
Last Reload       : 2006-10-08 08:46:10
Last successful upload                       : 2006-10-08 10:33:28
Total Megabytes of XML files uploaded so far :     0.06
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    38.19%
Agent is Running and Ready

Agents status

hello,
how can i know agents status
(active,hold.....)
with ifs api ?
thanks
null

You can use the iFS server manager to monitor an agent status. See page 8-11 on Oracle Internet File System Setup and Administration Guide Release 1.1.

ISE WebAgent not able to download with error Failed to download Cisco Agent ( Status = -2) !

Hi
We are able to get till WebAgent download page and while downling WebAgent we get below error...
Failed to download Cisco Agent ( Status = -2) ! . We tried with many laptops and for all we get same error while downloading the WebAgent ...
We also verified Latest Java & ActiveX components available on every laptops which we used for downloading WebAgent..
Attached the Screenshot of the WebAgent Download process
DACL Posture_Remediation used is as below
permit udp any any eq domain
icmp any any
permit tcp any host <PSN IP Address> eq 8443
permit tcp any any eq 80
permit tcp any any eq 443
permit tcp any host <PSN IP Address> eq 8905
permit tcp any host <PSN IP Address> eq 8909
permit udp any host <PSN IP Address> eq 8905
permit udp any host <PSN IP Address> eq 8906
permit tcp any host < Remediation Server> eq 80
Even we add permit ip any host <PSN IP Address> ,as last acl rule in DACL , still we were getting same error while downloading ...
Did any face the same issue , how it was resolved

This is seen when the required traffic is not allowed on the ACL.
ISE 1.1.1 added ports 8909 TCP and UDP for client download so we needed to add this into the Posture ACL.
permit tcp any any eq 8909
permit udp any any eq 8909
If you have clients with proxy failing to get the redirection then you should add 8080 to the switch.
ip http port 8080
ip port-map http port 8080
On the redirect ACL
permit tcp any any eq www
permit tcp any any eq 443
permit tcp any any eq 8080
I see you've already tried with permit ip any host
Jatin Katyal
- Do rate helpful posts -

How to view shared (NFS) 11g agent status?

I have installed the MASTER agent and the NFS agent on the same host.
Master Location = /app/oracle/ogc/agent11g (note 748535.1)
NFS State Location = /app/oracle/ogc/emstate
I see an agent running in OEM console, but I don't know if its the Master or NFS.
From the operating system I see an agent process running, but again I don't know which agent is up:
$ ps -ef|grep agent11g |grep -v grep
ogc 11421 1 0 Nov08 ? 00:00:01 /app/oracle/ogc/agent11g/perl/bin/perl /app/oracle/ogc/agent11g/bin/emwd.pl agent /app/oracle/ogc/emstate/sysman/log/emagent.nohup
ogc 11452 11421 0 Nov08 ? 00:00:31 /app/oracle/ogc/agent11g/bin/emagentIf I try to confirm the agent status using emctl, it says the agent is not running:
$ export ORACLE_HOME=/app/oracle/ogc/emstate
export PATH=$ORACLE_HOME/bin:$PATH
$ emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent is Not Running
$ export ORACLE_HOME=/app/oracle/ogc/agent11g
export PATH=$ORACLE_HOME/bin:$PATH
$ emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent is Not RunningHow can I confirm the NFS status from the command line?

Problem Solved by setting correct PATH:
export ORACLE_HOME=/app/oracle/ogc/emstate
export PATH=$ORACLE_HOME/bin:$PATH
emctl status agentOS command correctly shows agent status.

Host agent status is unknown for database (DB6) hosts in landscape browser

Hi,
Host status is unknown for database (DB6) hosts in landscape browser.
Trusted connection between DAA and host agent is working and host agent status is also green in Agent admin. SMD_DataEnrichment_Registrator is also registered correctly. But Outside discovery is not working for database in LMDB.
Solution manager:7.1 SP10
Host agent version:172 Patch 178.
Any help on this issue will be appreciated.
Regards,
Pragadees

I have noticed in your other posting as well that you want to make a lot of customisations. I would suggest you read more on EM from this link and see what you can achieve.
http://www.oracle.com/pls/db102/portal.portal_db?selected=21

UCCX Agent Status when making a Outbound Call

Hi Need a little Help ! Advice with the Above subject matter.
I have a customer, who is running reports with Historical reporting however the reports do not give a True reflection of Agents status.
i.e. if the Agent makes an outgoing call the Reports show the agent as being not ready.
I would like to know if it is possible to change how this is reported of if it is possible for the agent to add a note when on a call which would be reflected in the Historical reports.
Can we change the state it shows when an agent is on an outbound call to show "Outbound Call" instead of "Not Ready" as it currently shows ?
Cheers
Charles

Hi Charles
We have raised the same problem towards Cisco a long time ago. The fact that an agent talking is reported as "Not ready", instead of ex. "Talking Out" is not only a problem in HR, but also in some steps of scripting, since the agent is infact on the system and is anything but "Not ready".
Ex. you could check to se if any agent are logged in to CSQ, before selecting resource. If agents are logged in, you could check to see if number of agent logged in = number of agents not ready. If this is true, then no agents are available to answer call and another CSQ could be selected.
But now since an agent talking is reported as "Not ready" because he's talking, the check for agents logged in = agents not reayd might be true, causing script no to work as intended.
So for many reasons an agent talking should be "talking" and not "Not ready". I haven't heard about any workarounds on this agent state, but I do know that Cisco has been informed on this isseu and did recognise that it would make sense to implement but I don't know when this could happen. If not in verison 8.5, then perhaps in ver. 9.
You might be able to pull something from the DB to show correct agent state, but thats not "out of the box"
Regards
Henrik

ODI agent status shown prepared in Weblogic

hi,
I have installed FDMEE 11.1.2.4. When i start services everything is ok except ODI Java EE agent. I haven't configured it ( i think it was preconfigured).
I have tried starting ODI agent from enterprise manager but i am getting an error; will paste below.
I have seen that in weblogic server under erpi integrator server my odi console status is active and odi agent status is prepared. I don't know how to start JAVA EE agent.
Any help?
Error:
Invoking Start Up operation for application oraclediagent on target ErpIntegrator0.
[Deployer:149193]Operation 'start' on application 'oraclediagent' has failed on 'ErpIntegrator0'
[Deployer:149034]An exception occurred for task [Deployer:149026]start application oraclediagent on ErpIntegrator0.: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=MasterMemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
    MemberId|ServiceVersion|ServiceJoined|MemberState
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
at oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache.<init>(OdiAgentCoherenceCache.java:52)
at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
:com.tangosol.net.RequestTimeoutException:Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=MasterMemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
    MemberId|ServiceVersion|ServiceJoined|MemberState
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
Operation Start Up on target oraclediagent Failed. Please see error logs for details.
Regards

Hi JanGLi,
The ODI Agent is completely failing to start here from the error that you initially pasted so agent tests are not going to work wherever you try them. Port 6550 should have something listening on it as that's the port that the FDMEE managed server listens on so that would only prove that the FDMEE managed server is up. I can't see the connection closed error having anything to do with running out of connections in the connection pool either as it's simply a message saying that a connection was closed (not that the connection pool is exhausted).
On the plus side though I have seen the 'Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent"' error in the past (I get a lot of the really nice issues coming my way). Which operating system are you using here? I've seen this happen on Windows when there are multiple network interfaces and an incorrect interface has been put to the top of the bind order (e.g. an interface that has fallen back to a link local address in the 169.254.0.0/16 range as DHCP has failed).
Regards
Craig

Essbase Analytics for HFM- Data Update Agent Status

Hi,
In Essbase Analytics for HFM, Data Update Agent status is showing 'Not Active', so as 'Analytic Link Data' status.
The Start/Stop option for the same is disabled. Other connectivity statuses in Bridge are all 'Available'.
What needs to be done to make Data Update status 'Active'.

Hi HP,
The Essbase Analytics Link and HFM needs to be registered with the same Shared Services. Hope you are doing the same.
Thanks & Regards
Sandy

Finesse (UCCX10) - Show Agents Status when browser minimized???

Posting this question to see if anyone knows or has done a setup where the agent status can be seen when the browser is minimized on the task bar when using Finesse (similar to how CAD is when minimized). I imagine this will be custom but trying to see if it's possible first and any help will be greatly appreciated. If there's any other way to show this as well. Many thanks.

I believe that this feature request will have to be handled by the Cisco Finesse dev team, or you will have to switch to some 3rd party agent desktop - some that is utilizing Finesse API and that would be able to handle this request for you..

CCX - In CAD software agent goes into Reserved status.

I have CCX 7.0 & CCM 7.1.
In CAD software agent goes into Reserved status when a call hit to the agent & the agent is not able to take the call as all icons are greyed out. And this is happening to few agents only while for other agents its working fine.
Can anyone suggets a solution.
Rgds,
Kiran Savalsang.

Or more accurately - ensure that the CSS that is assigned to the CTI ports includes the partition in which the agent DNs are configured.
They don't all need to be the same CSS, OR the same Partition.
Aaron
Please rate helpful posts..

CCX Wallboard - Determining If Agent Is On Phone

Using uccxhruser on CCX 8, my wallboard is set up. It is pulling agent eventType and reasonCode from the AgentStateDetail table. Works great.
I need to know if there is a way to determine if an agent is in an outbound call, regardless of their state in the AgentStateDetail database table. Is there another table/value I can probe to get this information?
For instance, when an agent is in status code 3 (Ready), and they initiate an outdial on their phone, Cisco automatically places them in 2 (Not Ready) with a reason code 32762 (Out Call). This is reflected in the AgentStateDetail table. But if they are in status code 2 (Not Ready) and initiate an outdial, AgentStateDetail remains in whatever reason code they manually set, rather than switch to Out Call.
Thanks.

Hi Geoff,
Please do not use the historical reporting tables in wallboards. This causes system instability.
CSCtw47138: "Customers experience reliability and stability issues on CCX server" + "Caused by customers using historical tables in wallboard queries which is not supported." This is a doc bug which states that this data should be added to the Admin Guide, so don't look for a version in which it is "resolved".
Admin Guide page 483: "For details about the information written to the RtCSQsSummary and RtICDStatistics database tables, see the Cisco Unified CCX Database Schema Guide. Only the RtCSQsSummary and RtICDStatistics statistics tables can be used in wallboard queries. Use of historical reporting tables in wallboard queries is not supported."
The historical reporting tables are not designed to be accessed in a real-time manner; that's why we have
RtCSQsSummary and RtICDStatistics. Accessing them through a wallboard will definitely cause system instability. We have seen a number of TAC cases raised this way.
That being said, here's more information on the historical reporting tables.
You will probably have seen the HR Admin & Dev Guide; page 57 states that code 5 for ASD.eventType is the "Talking" state. Here's sample data from my lab system, for an agent taking an ICD call:
> select eventdatetime,eventtype,reasoncode from agentstatedetail where agentid = 38;
eventdatetime           eventtype reasoncode
2013-04-05 02:44:30.194         1          0     //Agent is logged-in.
2013-04-05 02:44:30.196         2      32760 //Agent goes into not-ready state 2 ms later. Not Ready reason code 32760 states that this is because s/he logged in.
2013-04-05 02:44:37.754         3          0     //Agent goes into ready state.
2013-04-05 02:45:01.993         4          0     //Agent is in reserved state: an ACD call is incoming.
2013-04-05 02:45:05.044         5          0     //After 4 s, the agent is in talking state.
2013-04-05 02:45:11.213         6          0     //The agent then goes to work state.
6 row(s) retrieved.
If the agent went on an outbound campaign call / a non-ACD call (whether inbound or outbound), the flow would be different; however, the eventType would change similarly. This is how historical reporting is able to see for how long agents talk, whether on ACD or non-ACD calls.
You can prepend "run uccx sql db_cra" to your SQL queries from the admin CLI, to see what kind of data you will get.
Finally, all the guides can be accessed from here.

Agent Status Reports OMS Version : (unknown)

I upgraded our 11g OEM installation to 12.1.0.1 and just completed patching to 12.1.0.3. Some of the 11g agents were on platforms not supported by 12.1.0.1 (part of the motivation fro the 12.1.0.3 upgrade, now complete).
Following the instructions in Chapter 7, Installing Oracle Management Agent in the Oracle Enterprise Manager Cloud Control Basic Installation Guide 12c Release 3 (12.1.0.3) I was able to get the agent installed and started on one of the servers I was not able to upgrade during the upgrade process. The new agent is up and running but reports OMS Version : (unknown) -
cmspweb:app/agent12g/agent_inst/bin->./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
Agent Version     : 12.1.0.3.0
OMS Version       : (unknown)
Protocol Version : 12.1.0.1.0
Agent Home        : /usr/local/oracle/app/agent12g/agent_inst
Agent Binaries    : /usr/local/oracle/app/agent12g/core/12.1.0.3.0
Agent Process ID : 3821
Parent Process ID : 3767
Agent URL         : https://garmin.ucdavis.edu:3872/emd/main/
Repository URL    : https://oracle-emrep1.ucdavis.edu:4904/empbs/upload
Started at        : 2013-10-08 11:56:26
Started by user   : oracle
Last Reload       : (none)
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 69.43%
Collection Status                            : Collections enabled
Heartbeat Status                             : OMS is unreachable [bad response]
Last attempted heartbeat to OMS              : 2013-10-08 14:30:13
Last successful heartbeat to OMS             : (none)
Next scheduled heartbeat to OMS              : 2013-10-08 14:30:43
Agent is Running and Ready
and the upload fails with the error EMD upload error:full upload has failed: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors. (OMS_DOWN) which makes sense. Searching the web I found a number of suggestions including securing the agent, which I was able to do and resynching the agent from the console which I am *not* able to do as the agent and targets are not showing in the console.
The targets.xml file on the agent host has one line -
<Targets AGENT_TOKEN="CB22F0CA441C8CDECF3CA3ABA0D8C02C9AACFF98A41D653CFB2F41B7BC41EE0D"/>
and I realize that is not at all a complete file. In the gcagent.log file I see ping errors -
2013-10-08 14:29:43,596 [319:8C08BF97] INFO - attempting initial heartbeat
2013-10-08 14:29:43,805 [319:8C08BF97] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: ERROR- Failed to update Target type Metadata)
2013-10-08 14:29:43,810 [319:8C08BF97] WARN - Ping protocol error
o.s.gcagent.ping.PingProtocolException [OMS sent an invalid response: "ERROR- Failed to update Target type Metadata"]
The firewall is open and the agent is using the correct port and I am stumped. If anyone has any suggestions I would certainly appreciate them.
Thank you.
Bill Wagman

Is this a newly installed agent?
Did it work before? What has changed since it last worked?
Anything in the emagent.trc file?
$emctl upload
EMD upload error: uploadXMLFiles skipped :: OMS
version not checked yet..
this is emctl status agent[dev01/AixAgentOracleHome/agent10g]$emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.1.0.4
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.4.0
OMS Version : UnknownThe agent does not connect successfully with the OMS, no version there.

Agent Status Stuck in EIM/CIM - "reserved"

Good morning.
We currently have one agent stuck in a "reserved" status, with no emails populating. We cannot get the status to clear.
Is there any suggestions on how to clear a stuck status?
Thank you,
CIM version 4.3.1

I would use your lab system and try the registry setting RouteRequestTimeout (default is 30000 so probably msecs).
\ICM\\PGn[A,B]\PG\CurrentVersion\PIMS\pimN\EAGENT\Data\Config
I don't know if this is correct, of course. But it looks tantalizing
Regards,
Geoff

UCCX 8.0.2 - Call in stuck with Agent status ready

Hi Guys,
I would like know what is the best log about RTMT I can use to analyze the calls stayed stuck with agent. Was verified in Real Time Report that there are agent available (state ready), but, the call was transfered for queue.
Thanks
Wilson

To find the root cause of stuck calls you need to Check MIVR/CCX engine logs
below is the link to read MIVR/CCX engine logs
http://docwiki.cisco.com/wiki/Guide_to_reading_MIVR_logs_for_Telephony_Issues_-_ICD_Call_Flow
I hope this will help

CCX 9.0.2 Agent Status

Similar Messages

Maybe you are looking for