" /> URS issue - Genesys CTI User Forum

Author Topic: URS issue  (Read 3159 times)

Offline blacklord

  • Newbie
  • *
  • Posts: 30
  • Karma: 0
URS issue
« on: October 07, 2010, 05:29:02 AM »
Advertisement
Guys, getting a lot of stuff like the foloowing in our URS logs:

    _I_I_000101d4b4e68453 [14:33] wandering call come to cdn
    _I_W_000101d4b4e68453 [01:11] call collision (000101d4b4e68453)

By a lot, I mean around 100 calls every ten minutes or so.

They don't [i]seem[/i] to be a problem 9as in they continue to route normally) but just wondering if anyone can cast light on why this might be happening.

regs,

Lance

Offline mark

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: URS issue
« Reply #1 on: October 07, 2010, 11:21:30 AM »
Do you have agents that receive calls from non genesys routed sources?

Offline kubikle

  • Full Member
  • ***
  • Posts: 140
  • Karma: 7
Re: URS issue
« Reply #2 on: October 07, 2010, 11:27:49 PM »
Normally it means that router runs startegy for some call and decides to start running other (or the same from the begining). Old instance of running strategy for this call is dropped (but can be exceptions and 2 instances can run for some time). If old instance is dropped then something like this should be in log:
terminate current routing and start new one from the beginning.

Use case 1:
Call come on on loaded RP and strategy started.
Router send call to IVR (as busy treatment).
IVR itself move calls on another DN (may be on the original RP) that also has loaded strategy.
based on option use_ivr_info router either continue old running old strategy instance or terminate it and restart startegy from the beginning

Use case 2:
call is routed from one RP1 to RP2.
Before router receive EventRouteUsed on RP1 the EventRouteRequest on RP2 is receved. Router starts new strategy
on RP2 while allow old strategy instance to complete normally (postrouting).

may be there other use cases.
In any case call collision message means that router has for some time (may be very short) 2 strategies instances for the same call.