Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Callback calls priority

Callback calls priority

Callback calls priority

Hi all,

I'm trying to achieve this :
* callers have the ability to ask for callback ==> done with callback ability, call remains is topic's queue, works fine
* callers that choose to keep on hold should be treated before callers which asked for callback

I'm struggling with the 2nd point. I tried to create a task tag which have a default value of 1 and which I set to 2 if the caller choose callback.
I then goes to "Source group priority", choose my topic, choose my task tag
But I still have the "oldest" call treated 1st (I've tried both UP & DOWN sort without any impact)

any idea of what I'm missing ?


RE: Callback calls priority

any idea ?

RE: Callback calls priority

It depends how your TaskFlow is configured.
Check in a Queue Monitor if the Tag stays as 2 while queuing.

"Trying is the first step to failure..." - Homer

RE: Callback calls priority

we display the tag in realtime supervision. The tag is set to 2 when callback is asked.
But the routing process stills distribute calls in FIFO instead of the dealing with call's with tag to 1 first.

RE: Callback calls priority

Then there's something wrong with your priority settings.

"Trying is the first step to failure..." - Homer

RE: Callback calls priority


I tried in both sort order

RE: Callback calls priority

Are all calls queuing to TOPIC-CALLBACK?

"Trying is the first step to failure..." - Homer

RE: Callback calls priority

yes they are

RE: Callback calls priority

We've made a lot of test and it seems that the priority is not working when we have a callback set.

With a standard task flow, we manage to use priority to answer 1st calls with the lowest priority.
But when we have a call waiting in the queue to be called back it is always treated by FIGO, even if it had an higher priority

I'm running 10.1.0, do you think it may be a bug ?

RE: Callback calls priority

I have opened a case for this ... will update when support answers :)

RE: Callback calls priority

There's always at least one bug in a IPOCC release =)

I didn't notice it when I tested the callback, but to be fair all our customers use a custom built callback until Avaya fixes their own to be usable.

"Trying is the first step to failure..." - Homer

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close