" /> ISCC transaction failed - Genesys CTI User Forum

Author Topic: ISCC transaction failed  (Read 3415 times)

Offline hugues4400

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
ISCC transaction failed
« on: November 23, 2017, 10:42:00 AM »
Advertisement
HI,

can you explain to me on the error message below and how to resolve it please:

ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES00093G)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES00094F)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES0009CU)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES0009E0)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES0009N5)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES0009NS)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES000A3T)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES000A71)
ISCC transaction failed (uuid 01AAVTN75CD156U987AHJB5AES000AAQ)

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: ISCC transaction failed
« Reply #1 on: November 23, 2017, 12:09:23 PM »
Increase log level...at least


Offline hugues4400

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: ISCC transaction failed
« Reply #2 on: November 28, 2017, 08:03:05 AM »
I have only this error message on the SIPServer

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: ISCC transaction failed
« Reply #3 on: November 28, 2017, 09:17:57 AM »
You need to check entire call flow for calls with mentioned UUIDs.

Offline hugues4400

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: ISCC transaction failed
« Reply #4 on: November 28, 2017, 11:16:06 AM »
Where can i check the call flow?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: ISCC transaction failed
« Reply #5 on: November 28, 2017, 11:18:18 AM »
Omg...at logs...
As said before, increase log levels to full on BOTH Tservers

Enviado de meu E6633 usando Tapatalk
« Last Edit: November 28, 2017, 11:40:14 AM by cavagnaro »

Offline water235

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
Re: ISCC transaction failed
« Reply #6 on: November 28, 2017, 02:57:47 PM »
What is the scenario here, do you have a routing that happens on SIP while your agents are still in Avaya ( or any other )platform ?
either ways,
when ISCC fails,
check if you have connections defined in the switch object
check if you have ERPs defined.
check for connections between the SIP Server and TServer
If there is problem in the access number distribution - if access number is not provided (even after it is defined ) restart the destination TServer if request to get access number is not placed restart the source tserver.
Also increase the log level and provide more details on the error.
if access number is provided and still if you see ISCC failures then look for your trunk settings - for the ERP .(Also check if the invite gets to your gateway(SM/SBC) - there are lot more with SIP ISCC..  but need to look into exact log details.

Thanks,
Water.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: ISCC transaction failed
« Reply #7 on: November 28, 2017, 03:04:27 PM »
[quote author=water235 link=topic=10756.msg48993#msg48993 date=1511881067]
What is the scenario here, do you have a routing that happens on SIP while your agents are still in Avaya ( or any other )platform ?
either ways,
when ISCC fails,
check if you have connections defined in the switch object
check if you have ERPs defined.
check for connections between the SIP Server and TServer
If there is problem in the access number distribution - if access number is not provided (even after it is defined ) restart the destination TServer if request to get access number is not placed restart the source tserver.
Also increase the log level and provide more details on the error.
if access number is provided and still if you see ISCC failures then look for your trunk settings - for the ERP .(Also check if the invite gets to your gateway(SM/SBC) - there are lot more with SIP ISCC..  but need to look into exact log details.

Thanks,
Water.
[/quote]Just being maybe too pushy but if the OP doesn't even get on how to increase log level you think he knows what you are talking about? I think he is a manager that is trying to fix this issue that should be escalated on his side


Enviado de meu E6633 usando Tapatalk


Offline water235

  • Newbie
  • *
  • Posts: 47
  • Karma: 0
Re: ISCC transaction failed
« Reply #8 on: November 28, 2017, 04:20:50 PM »
lol!! Can t agree more...

Thanks,
Water

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: ISCC transaction failed
« Reply #9 on: November 28, 2017, 05:39:16 PM »
Guys, just adding my two cents on this matter, because I have seen it happening over and over again:

let's just remind that all of us had to start somewhere; and some people just get thrown into Genesys projects without any clue of what it means. Maybe their manager just said: "ok, this is IT. That guy over there can handle it". Whether or not they should get trained, it is usually not their fault that they didn't. Or didn't receive any documentation. Or guidance on where to get that documentation. In addition to that, some of those people have a strong language barrier that rely on Google Translator which makes it way more difficult to explain what they need.

The goal of online forums is not to only share content and questions with people who are already experienced, but also to give at least some guidance on where to start looking at for those who where thrown into Genesys, not just reply with "RTFM".

Clearly the original poster has no clue on where to get information and the intent here is to give this guidance at least.


Now about the question: indeed more detailed logs are needed to understand what your problem is. You can increase the verbose by changing options on one of these tools: Configuration Manager (CME), Genesys Administrator (GA), Genesys Administrator Extension (GAX).
You can find out more on how the logs work on [i]Framework 8.1 SIP Server Deployment Guide[/i] (https://docs.genesys.com/Special:Repository/81fr_dep-sip.pdf?id=2e30d00a-05d6-4c84-a539-eb7ddcbde5f4) - Chapter 10: Common Configuration Option - log Section.
You must be registered as a Genesys Partner in order to access the link above.

You can also be interested in watching the [i]Tech Tutorial #81: Troubleshooting SIP Server Issues[/i] and the [i]Tech Tutorial #85: SIP Call Flow Troubleshooting[/i], and specially [i]Tech Tutorial #39: Understanding Inter Server Call Control[/i] (https://genesyspartner.force.com/customercare/GenesysRecordedTutorials) to understand a little bit more of call flows. Again, you also need to be a registered partner to access the link.

You can also learn a little bit more of call flows on the [i]Framework 8.1 SIP Server Deployment Guide[/i] that I mentioned before, and the [i]Genesys Events and Models Reference Manual[/i] (https://docs.genesys.com/Special:Repository/8g_ref_events-models.pdf?id=5fe793c7-6128-420d-8392-a75d473fd736).
« Last Edit: November 28, 2017, 05:45:54 PM by hsujdik »

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: ISCC transaction failed
« Reply #10 on: November 28, 2017, 05:49:06 PM »
Agree but also a concern on that if we guide him further he will probably do some incorrect action that could mostly cause a worst situation for him.
We are talking about a full business working behind him, I see it as irresponsible for us to provide access to those settings without knowing what exactly he is messing with...
We all have been beginners true, but I think we also had at least some basic ideas on support and risks management.

I know is hard to be on pressure, I have been there with other products and Genesys itself even today but when we face a beef too big to bite I think we double think on what should be our next step...

If he shares logs I will be more happy to help as that is something I learn too on platforms I probably haven't touched yet.

If not...we are overwhelming him with more chances on make bad move somewhere in the world


Enviado de meu E6633 usando Tapatalk