Do you use the LogOut Protocol for the OutBound

[eferreyra]

Hi, im programming the Agent Logout Protocol of the OutBound (OCS), till now i was doing a Extension.TLogout() and waiting the confirmation, reading some docs i find out the LogOut protocol of the OCS, GSW_AGENT_REQ_TYPE = "LogOut". 

Is this necessary, right ? (i assume yes for now)

It is necessary always ? If i dont have a campaign loaded ? If the campaign is stopped or unloaded ? i ask because i need the campaign info for the LogOut protocol.

How do you handle receive a LogOutAcknowledge but you are in a OutBound call received after LogOut request ?

I read the timeout to logout is always call_wait_connected_timeout, what effect has to reduce this time ? now is in 120 sec. i think is stressing for the guys to wait this time for no reason, i test and always have to wait this time for this protocol, there is some way to short this if the OCS dont really need this time ?

Maybe there is nothing to respond to my worrys but thanks for reading, the post helps me to clarify my situation...

[bublepaw]

This protocol is only needed when You do campaign in predictive mode. It helps system to calculate number of calls and it prevents overdials ( situation in which Outbound places a call and agent logs out ).

This request is only valid for loaded and active campaigns.

If You receive LogOutAck durign outbound call just wait for call to end and agent to finish his work and log-out agent from desktop.

In documentaion for Outbound server there is definition how to setup call_wait_connected_timeout:

"For ISDN: Specifies the timeout, in seconds, between dialing and the
determination that the called party is not answering.
For analogue and line-side DNs: Specifies timeout between the first ring
and the determination that the called party is not answering.
"

Regards

Paul

[eferreyra]

Thanks Paul!