E_CTIOS_SERVICE_SEND_MESSAGE_FAILED. Best possible action

I have developed agent desktop application based on CTIOS API.

Some times when i am changing state, i start getting this error message: E_CTIOS_SERVICE_SEND_MESSAGE_FAILED. Afterwards Agent is not able to change state or even logout.

I checked my connection and connectivity with the server. It is fine.

What should be the best possible action from application point of view when i get this error message? should i logout agent and clear the state OR try to reconnect. How??

As per our CTIOS dev. guide, this error means the following:

E_CTIOS_SERVICE_SEND_MESSAGE_FAILED     -902        Could not send message. Session may not be connected.

The message sessions between CIL and CTIOS server are based on TCP. The transport layer will deal with this issue. If the CIL sends message failed, an eOnCILError event with failure code E_CTIOS_SERVICE_SEND_MESSAGE_FAILED will be generated. And if there is no response comes back, CIL WILL NOT resent the message or generate a timeout event.

Looks like there could be something wrong from the N/w end because the session becomes invalid breaks the message flow.

To check it further can you get me the following info:

--> What is the UCCE version ?

--> Provide all logs to check from server end. Below are the trace levels needed

CTIOS :

            Using registry editor set

            - EMSTraceMask= 60a0F(hex)

CTIsrvr:

            Using registry editor set
            - EMSTraceMask= F8 (hex)

OPC (Agent PG):

            C:\>opctest /cust <cust_inst> /node <node>
            OPCTEST: debug /noall
OPCTEST: debug /on
OPCTEST: debug /ctimsg
OPCTEST: quit

            EMS Trace 0x40
           
PIM (Agent PG):

            C:\>procmon <cust_inst> <node> pim<pim instance>
            >>>>trace tp* /on
            >>>>trace precall /on
            >>>>trace *event /on
            >>>>trace csta* /on                
            >>>>trace periph* /on
           
JTAPI GW:

            C:\>procmon <cust_inst> <node> jgw<jtapi instance>
            >>>trace JT_TPREQUESTS /on
            >>>trace JT_JTAPI_EVENT_USED* /on
            >>>trace JT_PIM_EVENT /on
            >>>trace JT_ROUTE_MESSAGE /on
            >>>trace *CONF* /on
            >>>trace JT_CONNECTION* /on

-- Please check if you notice any such issue with our out of Box CTIOS client as well.

 The issue was with the wrong port number.  That is why i belive it was not able to connect and we were getting the error.