We have an application that integrates to Cisco using the CTI Server Message Protocol. We make an OPEN_REQ request to open a connection to the PG. When we receive the OpenConf() we check the PGStatus field on the response to check it's !=0
PGStatus field is described as follows: The current operational status of the Peripheral Gateway. Any nonzero indicates a component failure or communication outage that prevents normal CTI operations.
The PG we connect to has a number of PIMs - on one occasion one of these PIMs (e.g. VRU) was down and we received a non zero response:
The PIM that is down on the peripheral gateway (VRU) is not one that would impact the ability of our application. However we terminate our application since we received this error code as it indicates the system may have operational problems.
Should we be checking the PGStatus field on the OPEN_CONF in this manner? As technically it is an OPEN_CONF and not a FAILURE_CONF. If the system is warning something might not be correct then it seems that we can't guarantee everything will be okay for our application to operate. Does this seems valid?
HiWe have UCCX and are using cisco finesse. We have deployed popup screen feature on finesse and it is working fine, but we have a problem. It does not create new tab for each call that is handled and every new call over writes the call info with the new ...
Hi there, Suppose Agent001 is in Ready(userstate) state while Agent002 is in Not_ready(userstate) state. Agent002 makes call to Agent001,Agent001 answers the call & now they are in Talking(userstate) state...
I'm tasked with providing a credential unlock for CUCM endusers. Looking at the AXL schema and doing some trial & error I found that pinCredentials.pinResetHackCount / passwordCredentials.pwdResetHackCount is what I'm looking for.. setting this to tru...
I would like to use the UCCX API in the following scenario and was wondering if anyone could point me in the right direction: Agent Places outbound call using FinesseAgent Ends CallFinesse Automatically Dials Extension 12345 I've tried using&nbs...