Progressive outbound has calltype 2

[Vincent]

I've been going through the logs of T-Server as there were some problems with the desktop application not giving a popup for progressive campaigns. The problem didn't occur for preview campaigns, which was very strange.

Within the T-Server logs i saw that during the EventDialling for setting up the call the Calltype is set to 2, which i think is inbound. As far as i know this calltype is set by the switch and communicated to T-Server, but the Aspect engineer i talked with couldn't find it in his logs. I looked at the T-Server documentation for Aspect, but couldn't find anything about it.

So should the calltype be 3 for progressive campaigns and what is the way to change it?

[cavagnaro]

Constant Value Description
CallTypeUnknown 0 The type of this call is unknown.
CallTypeInternal 1 This is an internal call.
CallTypeInbound 2 This is an inbound call.
CallTypeOutbound 3 This is an outbound call.
CallTypeConsult 4 This is a consultation call.

[SisB]

T-Server has role to play on how the call is typed.
We had a similar problem when internal calls (to agent id in Avaya) were shown as Outbound. Genesys had to fix the T-Server.

Thanks

[Vincent]

I've tested the progressive outbound in our test environment and here i actually see that they are correctly set to outbound. So there must be a difference between the test environment and production, but i don't know what to check to know for sure.

There's a difference between progressive and preview that i can't explain. With preview it's the agent that initiates the outbound call. With progressive i guess it's the OCM environment.

[Vincent]

Talked to another Aspect engineer and he states that the calltype field is an Aspect Field and can't be configured as it's set by the system. Is there an option in T-Server/OCS that can be set?

[daveg]

We saw this problem, and T-Server restart fixed it. Still don't know why.

[Fra]

In the Avaya TServer there are two options, set-call-type-on-dialing (if set to true, assigns CallType based on a dialed number that T-Server checks with the telephony configuration) and override-incorrect-calltype; I don't know whether the Aspect one has similar options.


Fra

[jbobinsk]

To SisB
I had the same problem with Avaya TServer - and there is a method to resolve the problem with qualifying internal as outbound. Generaly it happens when one agent calls to another by agent ID (which is not configured in CME) not by the extension (which is configured). To resolve it you can add DN Ranges on the Switch properties noticeing the AgentIDs range.

Regards
jbobinsk

[Vincent]

[quote author=Fra link=topic=4170.msg18757#msg18757 date=1242723304]
In the Avaya TServer there are two options, set-call-type-on-dialing (if set to true, assigns CallType based on a dialed number that T-Server checks with the telephony configuration) and override-incorrect-calltype; I don't know whether the Aspect one has similar options.


Fra
[/quote]

Looked at the Aspect T-server documentation, but didn't find anything related to the call-type....comparing the configuration files didn't lead to any differences either