Strange behaviour of after-call-divert-destination

[Toz]

Have a question regarding strange behavior of ExtensionUpdate[‘after-call-divert-destination’,DN] function in genesys. It supposed to divert a call after interaction with agent ends to a different routing point (eg for surcvey, etc), so it does. But strangely after second strategy (survey) ends it does not hang the call, stays with silence. Can you help with that issue? Is it our local problem, or genesys bug? 
The problem is not in survey itself, because I created simple strategy that sets aftercall divert and dials test agent, and after call release by agent it diverts to other strategy that simply plays message and goes to exit block. But call stays online with silence instead of being released.
T-server version is 8.1.102.35

[Kubig]

You have to release/disconnect it within your routing strategy, the exit block does not do it.

[Toz]

Added ReleaseCall[] function before exit block - did not help.

[Kubig]

Try to use Disconnect function

[Toz]

Cant find Disconnect function. Can you help me with that?

[Toz]

In log there is a error message
AttributeErrorMessage 'Object not known'
AttributeRouteType 7 (RouteTypeReject)

[Toz]

And if I set up a strategy to ReleaseCall[] without setting an aftercalldivert option - Route is OK. Call terminates.
I think aftercalldivert breaks Reject route somehow. Why?

[Kubig]

I am always using the TRoute function with RouteType equal to "RouteTypeCallDisconnect" and it works as expected.

[Toz]

You mean TRoute['','',RouteTypeReject,'']?
Already did that, got error message in log, posted before.

Can anyone assemble lab with 2 strategies on 2 RPs, where one sets ExtensionUpdate['after-call-divert-destination', XXXX], where XXXX is second RP, and second strat just plays some message and either uses TRoute or ReleaseCall[] to release call.
I can't understand why system unable to find route to reject?

[Kubig]

No, I meant  TRoute['','',RouteTypeCallDisconnect,'']

[Toz]

Ok, tried TRoute['','',RouteTypeCallDisconnect,'']

Got:
AttributeErrorCode 1143
AttributeErrorMessage 'Object not known'
AttributeReferenceID 4823057
AttributeReason [14] 00 01 01 00..
'RTR' 886
AttributeRouteType 14 (RouteTypeCallDisconnect)
AttributeOtherDN ''

[Kubig]

Weird, have to check entire logs, because it working in general cases.

[Toz]

Well - found a 'solution'
Created RP with no strategy and TRouted to it. Succesfully drops the call. But that is not right at all.

Can anybody please just repeat my case to check is that a bug or a feature? Is it necessary to open genesys care case for that, or its just our enviromnment broken somehow?

[Kubig]

What version of SIP server are you using? I will check the function within my LAB

[Toz]

posted before
8.1.102.35
Thanks!