It's incorrect. But not a long for
ASAI defines EWT for a call in some event reports/requests (offered event report and adjunct routing request), although there is no request that instantly reports EWT for a given ACD slit group.
There are no EWT (Expected Waiting Time) in the ASAI interface nor in the documentation. An undocumented feature perhaps?
The closest I get is "Oldest Waiting Time" in a C_AIMD (Avaya Internally Meassured Data) Value Query. AMID Value Query requires Green feature SA7880, a RTU not sold anymore :-(
Oh... But your out of luck again. There are no such information in any ASAI events. But if you keep track of each call starting with the C_OFFERED event and ending with a C_CONNECTED or C_DROPPED which ever commes first, you can calculate the value your self.
you have 2 options here. you can use the definity vector commands to calculate the EWT and tell the caller how long it will take to answer the call (announcements) or I recon you could use the definity EWT command in a vector to calculate the time and send it to a vdn that is monitored by the asai (eg. there is a vdn for 1 min, vdn for 2 min, vdn for 3 min etc)
goto step x if ewt is x and step x is a vdn that is monitored via the third party. after the vdn the call is passed to a vector that passes the call to the third party.
easier to do it the first way though, and cheaper.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.