Hi rk06, Displaying notification on the reason code change is not a big task and can be quickly implemented. The second part of the request is a little bit complicated but is possible to be done. I think that you will not able to do it using the Cisco Finesse Toaster Notification API (Finesse.ClientServices.Toaster) as it is not designed to be auto close. More about how this API works you can find here: https://gaman-gt.com/articles/cisco_finesse_notification.html A good idea would be to use the browser notification API but it has some limitations. What is also interesting, they relay on browser on OS setting. This is something that you can also find in the page mentioned above. Finally, here is a sample gadget, that may help you to try different setting for the notifications that works on the reason code change. You can change the notification basic (use Finesse or Browser API). The gadget can be downloaded from here: https://gaman-gt.com/downloads/finesse_gadgets/Finesse_Notification_Gadget_on_Reason_Code_Change_2019_12_30.zip Hope that helps you.
... View more
Where the file described in the workaround can be found (20150318-143929838_ReplicationSolution.sql) ?
Does it resolve problem with missing constrain "[dbo].[TB_DIM_PRINTER_PKEY_MAP]" ?
Thanks for help in advance.
... View more
UCCE has very interesting mechanism of monitoring basic parameters for CTIOS server. If we look at SNMP OID numbers we can see that the parameters from menu bar can be obtained to external monitoring system (cccaCtiOsActiveClients, cccaCtiOsActiveMonitors, cccaCtiOsCallsInProgress, cccaCtiOsCallsFailed). We can also find the static parameters that are related to system configuration like (cccaCtiOsServerName, cccaCtiOsPeripheralName, cccaCtiOsPeripheralType, cccaCtiOsCgSideAName, cccaCtiOsCgSideBName, cccaCtiOsPeerName). Usually all the parameters are available but sometimes we observe that only static ones are presented. What can be the cause that the dynamic parameters are not presented in SNMP (all the dynamic parameters return 0 although the menu bar of CTIOS process show those statistics) ? Can this behavior be related to CTIOS errors like: 15:05:32:466 CTIOS1-ctios Trace: IOCPConnectionMgrThread,Client[02553, 05DEF398]:Pending Writes(8000) Exceeds Limit(8000)Client disconnected by CTIOS Server,Client(2553) at Address(172.17.228.238),Total Client pending write operations is (8000) for (197) Client(s) connected,LastWriteResponseTime(0 ms)
... View more
In this case I've additional question. Below we have logs from eQueryAgentStateConf event (CTIOS 8.5.3). In this logs I've marked Attributes - in green indicating number of skill groups assigned to agent and in red skills related to the agent. Regarding to agents state table valid skill groups for this agent are skill group with id 5000 and 5988. Skill group 5021 is not valid because agent state in this group is LOGOUT. The question is why CTIOS sends also information about skills that are not currently assigned to agent ? Does CTIOS present data for skills that agent had assigned during specific time period ? 05-30-2014 12:29:52.6627 :0: CTIObject.OnEvent: Received Event: eQueryAgentStateConf Arguments:( PeripheralID:5000 AgentState:eNotReady NumSkillGroups:2 MRDID:1 ICMAgentID:5107 AgentMode:1 MaxTaskLimit:1 NumTasks:0 AgentExtension:225803844 AgentID:90901590 AgentInstrument:225803844 EnablementMask:0xA1B0010 UniqueObjectID:agent.5000.90901590 MessageID:eQueryAgentStateConf NotReadyReasonCodes: (Coaching:13004, Break: 13005) LogoutReasonCodes: (End of work:11002) NotReadyReasonRequired:True LogoutReasonRequired:True AgentAvailabilityStatus:0 IsAuthenticated:True SkillGroup: ( SkillGroupNumber:9841 SkillGroupID:5000 SkillGroupPriority:0 SkillGroupState:2 ) SkillGroup: ( SkillGroupNumber:20101 SkillGroupID:5021 SkillGroupPriority:0 SkillGroupState:1 ) SkillGroup: ( SkillGroupNumber:0 SkillGroupID:5988 SkillGroupPriority:0 SkillGroupState:2 ) )
... View more