" /> G3Cause 617 - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: G3Cause 617  (Read 4030 times)

Manas Mohanty

  • Guest
G3Cause 617
« on: December 30, 2007, 04:53:14 PM »
Advertisement
We have Avaya Switch . We see g3cause 617 for certain calls in 'EventRouteUsed' messages  . when i checked with switch team they said the COR setting on these station is 120 which is correct . But still i see these messages and calls are getting default routed. But interestingly i observed that not all calls to agents on these  stations are getting default routed and these agents seems to have taken few inbound calls. Anything else i need to check with Switch team?
Logged

Offline Daimonas

  • Full Member
  • ***
  • Posts: 106
  • Karma: 2
  • There's a fish in every bowl.
Re: G3Cause 617
« Reply #1 on: January 02, 2008, 09:36:44 PM »
  • Best Answer
    • This error could range from COR issue, routing (or not ) by direct agent and not setup correctly, DN monitored by multiple t-servers, invalid queue/or DN specifed in the RouteRequest message to switch, etc...

    Is there anything diffrent from this call-flow from others where it works correctly?
    « Last Edit: January 03, 2008, 02:08:28 PM by Daimonas »
    Logged

    IanDS

    • Guest
    Re: G3Cause 617
    « Reply #2 on: January 04, 2008, 11:32:13 AM »
  • Best Answer
    • 617 Permission denied will be caused by the wrong COR on the cti station / link. The link will not be able to route calls to a vdn with a different COR.

    get them to check that.

    Logged
    Pages: [1]   Go Up
    « previous next »