" /> Avaya Hunt - Genesys route-thru-queue - Genesys CTI User Forum

Author Topic: Avaya Hunt - Genesys route-thru-queue  (Read 5273 times)

Offline SisB

  • Jr. Member
  • **
  • Posts: 60
  • Karma: 0
Avaya Hunt - Genesys route-thru-queue
« on: June 11, 2009, 03:18:09 AM »
Advertisement
Hi Guys,

I was not able to find much detail around this in documents or anywhere else. With route-thru-queue enabled, can Genesys select an Avaya queue which is not monitored by Genesys.

E.g. An agent has 2 avaya skills, out of this one hunt is created as ACDQueue in Genesys config and other is not. Can T-Server select the queue which does not exist in Genesys while doing route select ASAI to PBX.

I tried to play around with it a bit. Deleted one ACD Queue/Hunt from CME and noticed Genesys is still routing call through that queue. However, stat server is impacted e.g. login table cannot log the queue for corresponging login event.

Anyone has insight around this?

Thanks in advance.

« Last Edit: June 11, 2009, 03:59:32 AM by SisB »

Offline Seb Reeve

  • Jr. Member
  • **
  • Posts: 62
  • Karma: 0
    • Sabio Limited
Re: Avaya Hunt - Genesys route-thru-queue
« Reply #1 on: June 19, 2009, 09:52:12 AM »
Hi - if I recall correctly the "Queue" (i.e. Hunt Group/skill Extension) used is the primary skill for the Agent this is used because TServer is monitoring logins for each agent and uses the first ThisQueue field it sees as the queue to route through.

If you change the primary skill for the agent in Avaya - you should see a different queue is used...

Rgds,
Seb

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: Avaya Hunt - Genesys route-thru-queue
« Reply #2 on: June 22, 2009, 03:34:16 PM »
[quote author=SisB link=topic=4302.msg19135#msg19135 date=1244690289]
E.g. An agent has 2 avaya skills, out of this one hunt is created as ACDQueue in Genesys config and other is not. Can T-Server select the queue which does not exist in Genesys while doing route select ASAI to PBX.
[/quote]

In general you may be able to send a call to a not monitored DN by forcing TServer to do so. But that is not the case of when you want to route a call out to an agent and pass in the ThisQueue parameter of the RouteCall a queue that Tserver hasn't registered.

Seb is right:
[quote author=Seb Reeve link=topic=4302.msg19355#msg19355 date=1245405132]
Hi - if I recall correctly the "Queue" (i.e. Hunt Group/skill Extension) used is the primary skill for the Agent this is used because TServer is monitoring logins for each agent and uses the first ThisQueue field it sees as the queue to route through.

If you change the primary skill for the agent in Avaya - you should see a different queue is used...

[/quote]

Correct. The queue used is the Avaya primary skill. If the queue has not been registered by TServer, there is no chance you can get any kind of event on it and therefore TServer clients too (e.g. Stat Server) won't be aware of anything either.

Fra