Avaya Aura switch and TServer for TSAPI

A question regarding Avaya Aura switch and TServer for TSAPI

Is it required to set the wait-time after adjunct routing (in the call vector setup) to a greater value than expected queue time in Genesys? Let’s say if we will have wait times for more than 30 minutes before we find an available agent in Genesys - the wait-time in AACM needs to be greater than 30 minutes?

Since no treatments are supported on TServer TSAPI I cannot ask switch for ringback and indicate I have control over the call (like on some other switches)

Genesys deployment guide shows examples where this timeout in AACM is 10 sec, but with that setting I get the error: performanceLimitExceeded

A search at Genesys support gives this answer:
Root Cause - vector timout
Solution -Increase vector timeout in switch to avoid the error. Or tune strategy to speed up routing before switch timer expires

But with a long timeout in AACM you lose the possibility to let the switch do fallback routing if Genesys is down.. Anyone out there with experience of AACM and TServer TSAPI?

Many thanks in advance!

Hi. The ideal is that you create a VDN containing a vector for playing music (or any sort of treatment) for a long period (lets say 60 seconds). Then, on the target selection block of IRD, you place that VDN number on the busy treatments list and let TServer ans URS do their magic

Hi,

OK, thanks! Will try it!
So this kind of treatment works even if TServer TSAPI doesnt not support any treatments (TApplyTreatment, TGiveMusicTreatment, TGiveRingBackTreatment or TGiveSilenceTreatment) against the switch?

I think will be as it is actually not a treatment but more like a parking feature

Enviado de meu SM-G9650 usando o Tapatalk