Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Callback calls priority

Status
Not open for further replies.
pkdev

pkdev

Technical User
Oct 14, 2010
273
FR
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 ?

Cheers
 
Sort by date Sort by votes
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
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
Then there's something wrong with your priority settings.

"Trying is the first step to failure..." - Homer
 
Upvote 0 Downvote
BC0265B_bbeech.png

I tried in both sort order
 
Upvote 0 Downvote
Are all calls queuing to TOPIC-CALLBACK?

"Trying is the first step to failure..." - Homer
 
Upvote 0 Downvote
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 ?
 
Upvote 0 Downvote
I have opened a case for this ... will update when support answers :)
 
Upvote 0 Downvote
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
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

S
  • Locked
  • Question
IP Office Outgoing calls shows up as Spam Calls
Replies
0
Views
332
Sud10
S
toniavaya
  • Locked
  • Question
Priority calls for agent grups and topics
Replies
4
Views
362
toniavaya
toniavaya
lp_trd
  • Locked
  • Question
Ghost calls on IPOCC10.1.2.3
Replies
4
Views
280
janni78
janni78
ChrisCheops
  • Locked
  • Question
Callback calls and real time information service level & TSF
Replies
4
Views
229
ChrisCheops
ChrisCheops
davea2
  • Locked
  • Question
Collector priority
Replies
2
Views
128
davea2
davea2

Part and Inventory Search

Sponsor

Back
Top