URS Treatment problem

[okanoyu]

There is one problem about URS.

Call is sent to announcement VDN by using the treatment function.
URS does the Call when adjunct will be done by the announcement VDN in 60
seconds or more and routing is not done normally.
There is no problem if it is within at 60 seconds.

Are there any solutions?


-- error message --
02:51:20.582_G_I_ [01:0b] look for hanged interactions: 1 at all now
    _G_W_00ed0177c0848307 [01:0b] call waits too long (87 sec)
    _I_I_00ed0177c0848307 [01:08] call deleting truly
CALL (00ed0177c0848307) HISTORY ( Dropped ):
02:51:20.583_G_I_ [01:0b] there are 0 calls in progress now

[René]

Hi,

You haven't mentioned your PBX but I assume you're talking about Avaya. The solution is quite easy - put the adjunct at the beginning of your VDN. In that case URS doesn't lose control over the call and the announcement will be played.

René

[victor]

Hi, René,

I was going to suggest the same thing, but I think this would not be a good idea if there is an input inside the announcement. Since it seems like there is a 60+ second announcement, it sounds like something that is requiring a user input.

The only way that I know on handling this would be:

call-tracking = false

and pray that you do not have any unmonitored DNs where URS call will get stuck. But then again, I am pretty weak when it comes to announcements in Avaya. What do people usually do when they have a 60+ second treatment on Avaya PBX and then they need to get get the digits? CED[] does not wait for user to enter digits. (Sorry for off-topics question...)

Best regards,
Vic

[okanoyu]

Thanks for the tips...

PBX is AVAYA.
After it announces, the setting of VDN sets adjunct.

I will test the setting of call_tracking.

Best regards,
okanoyu