Update callresult on outbound campaign using PSDK

[PeteHoyle]

[quote author=PeteHoyle link=topic=9421.msg42717#msg42717 date=1458143288]
[quote author=cavagnaro link=topic=9421.msg42706#msg42706 date=1458130600]
And what are the other ways? Using http commands to OCS?
[/quote]

Hi,

Yes as you say using http commands to OCS is one way.

The other way I was thinking was using the OutboundDesktop PSDK API, in the background it's the same in that it sends a UserEvent, just a slightly different API. I've never used this method though, always just create my own UserEvents..
[/quote]


Actually thinking about this more, I have some distant memory that some of the OCCS HTTP requests are specific to certain dialling modes and will only work with Power GVP and Progressive GVP modes. I think it is the RecordProcessed and UpdateCallCompletionStats requests that are only supported by these dialling modes.

[cavagnaro]

[quote author=PeteHoyle link=topic=9421.msg42728#msg42728 date=1458202686]
[quote author=PeteHoyle link=topic=9421.msg42717#msg42717 date=1458143288]
[quote author=cavagnaro link=topic=9421.msg42706#msg42706 date=1458130600]
And what are the other ways? Using http commands to OCS?
[/quote]

Hi,

Yes as you say using http commands to OCS is one way.

The other way I was thinking was using the OutboundDesktop PSDK API, in the background it's the same in that it sends a UserEvent, just a slightly different API. I've never used this method though, always just create my own UserEvents..
[/quote]


Actually thinking about this more, I have some distant memory that some of the OCCS HTTP requests are specific to certain dialling modes and will only work with Power GVP and Progressive GVP modes. I think it is the RecordProcessed and UpdateCallCompletionStats requests that are only supported by these dialling modes.
[/quote]


Yeah, only HTTP modes like Power GVP, Progressive GVP with GVP VXML client and Push Preview with ORS

[luchosrock]

[quote author=PeteHoyle link=topic=9421.msg42716#msg42716 date=1458143152]
Have a look at the OCS option below.

If the Agent goes into Ready at the end of a call the OCS will assume that record is finished with, so if you set this option to not let the Agent go into Ready that should mean you can still update the record.
[/quote]

Thanks Pete for your quick reply.

When the agent is in NotReady status during after call work, is the record finished already?

Is the OCS option you mentioned campaign/group specific or is it globally scoped? I mean, will all outbound campaigns be affected by this configuration?

[PeteHoyle]

[quote author=luchosrock link=topic=9421.msg42742#msg42742 date=1458227088]
[quote author=PeteHoyle link=topic=9421.msg42716#msg42716 date=1458143152]
Have a look at the OCS option below.

If the Agent goes into Ready at the end of a call the OCS will assume that record is finished with, so if you set this option to not let the Agent go into Ready that should mean you can still update the record.
[/quote]

Thanks Pete for your quick reply.

When the agent is in NotReady status during after call work, is the record finished already?

Is the OCS option you mentioned campaign/group specific or is it globally scoped? I mean, will all outbound campaigns be affected by this configuration?
[/quote]

If the Agent goes into Not Ready after the call without first going Ready then the record should still be able to be updated. Have a look at the TServer and OCS logs to see what is happening.

Looks like the option can either be set a application level or switch level..

[facembani223]

Are OutboundDesktop requests made through TServer?

[luchosrock]

Yeah, they are made as a UserEvent through T-Server RequestSendEvent

[cavagnaro]

Post Tserver and OCS logs for a sample call. Indicate ConnID