" /> Network to Premise Routing... - Genesys CTI User Forum

Author Topic: Network to Premise Routing...  (Read 5858 times)

tony

  • Guest
Network to Premise Routing...
« on: October 03, 2007, 09:29:44 AM »
Advertisement
Hi!

Network TSever 7.0
URS 7.2
Premise TServer 7.2
Avaya PBX & Network (national) Routing


We've recently updated some of our routing, to ensure that Genesys data is populated across our Network to the Premise Sites and is then available to Agents.  Problem is, now we've "fixed" the issue, we have a dilemma in the way the interactions are being reported;

Before the changes, Warm/Consult calls being passed across our Network were recorded as 1 Inbound + 1 Consult and our Reporting guys were happy with this, as they could apply a simple equation to determine non-accountable (Consult) from accountable (Inbound) calls.

However, we now see Warm/Consult calls across the Network being routed and recorded as 2 Inbound Calls, with no Consult.  Genesys tell us that this is by design, therefore there is nothing for them to fix.  We've been wracking our brains to try and find a way to record the Consult as a Consult, rather than an Inbound but it is the local PBX which instrucsts Genesys of the CallTypes, so we can't affect a change in that area.  We've also considered pegging calls and a whole host of other scenarios, to discern between what is (and what is not) a Consult call from the Network.

Has anyone come across this and perhaps came up with a definative solution?  It's worth some cake (of which I have ample, at this time...) :)

Thanks,

Tony

Marked as best answer by on Yesterday at 09:27:34 PM

tony

  • Guest
Re: Network to Premise Routing...
« Reply #1 on: October 08, 2007, 08:52:27 AM »
  • Undo Best Answer
  • Replying to my own post after 5  days on here means that I either did not explain it well enough or it really is a doozer of a problem!  :o

    Does anyone know if it is possible to create a "smart" routing solution, to discern between Inbound and Consult Calls, as they pass into or out of a local Switch, from the Network?  Or perhaps there is a way to observe 2 calls (thereby 2 ConnID's) within 1 interaction and annotate one of them as a pseudo-Consult call, for reporting purposes...?

    My guess is it can't be done...???  :(

    Tony

    Offline mark

    • Sr. Member
    • ****
    • Posts: 415
    • Karma: 2
    Re: Network to Premise Routing...
    « Reply #2 on: October 08, 2007, 10:27:51 AM »
    Tony,

    Isn't there a 'Tranferring Agent' flag somewhere within the routing, I am sure there is. If so, you could do a check on this, if this KV has a value then you could assume that it is a consult call.

    Mark

    Offline mark

    • Sr. Member
    • ****
    • Posts: 415
    • Karma: 2
    Re: Network to Premise Routing...
    « Reply #3 on: October 08, 2007, 10:29:28 AM »
    StrLen[UData['GCS_TransferringAgentName']] > 0

    Try that! :D

    tony

    • Guest
    Re: Network to Premise Routing...
    « Reply #4 on: October 08, 2007, 11:25:11 AM »
    Hmmm... I will look out for TransferringAgentName in our Network and Premise TServer logs...  I am also looking at TServer messaging, too - things like; EventPartyChanged - RequestCompleteTransfer - RequestMuteTransfer.  Basically anything which indicates that it is not only a Network Inbound call...

    Thanks Mark!

    Tony

    tony

    • Guest
    Re: Network to Premise Routing...
    « Reply #5 on: October 08, 2007, 03:44:50 PM »
    Don't have TransferringAgentName - must be UData specific to your site...?

    That aside, whatever is placed in the strategy for transfers across the Network may well be misleading.  Just because a call enters the Queue as a Consult, it doesn't necessarily mean it will leave as a Consult - it is quite possible that, after about 20 seconds the Agent might give up and leave the Caller to wait in the Queue by themselves - that means; 1 Transfer/Consult [b]and [/b] 1 Inbound IN to the Queue on the Network and then 1 Inbound OUT of the Queue, to the Site... :(

    Tony

    Offline René

    • Administrator
    • Hero Member
    • *****
    • Posts: 1832
    • Karma: 62
    Re: Network to Premise Routing...
    « Reply #6 on: October 08, 2007, 07:11:40 PM »
    Hi Tony,

    Firstly I have to state that my experience with network routing equals zero (read: no experience) but I have an idea ;).

    I think it should be possible to configure switch to classify calls coming through particular trunk as internal. If you can do that then premise TServer should recognise the call as "Consult". Disadvantage of this idea is that you need dedicated trunk for transferred calls....

    BTW The key "GCS_TransferringAgentName" is added to the transferred call by Genesys Contact Navigator.

    René