Possible Issues in an ICD call flow

From DocWiki

Possible Issues in an ICD call flow

Problem Summary

Here we take a look at a simple ICD call and identify the various points in the call flow where we could encounter and issue or error. This is to help you look through the call flow of your call and identify the cause of the failure with the help of this tip.

Error Message

NA

Possible Cause

NA

Recommended Action

If the call fails due to some issue in Telephony then you are requested to go through the logs to check at what point the failure occurs and then use this tip to pin point the failure and the resolution for the same.

CiscoMediaOpenLogicalChannelEv is received for the call for which UCCX will setRTPParams60621: Jan 15 10:43:44.002 CST %MIVR-SS_TEL-7-UNK:CallID:58 MediaId:66342/2 Task:19000000072 com.cisco.jtapi.CiscoMediaOpenLogicalChannelEvImpl received

Media is being set up for the call at the CTI Port. CiscoRTPOutputStartedEv is received60622: Jan 15 10:43:44.002 CST %MIVR-SS_TEL-7-UNK:CallID:58 MediaId:66342/2 Task:19000000072 com.cisco.jtapi.CiscoRTPOutputStartedEvImpl received

CiscoRTPInputStartedEv is received. Media is now set up for the call at the CTI Port.60641: Jan 15 10:43:44.002 CST %MIVR-SS_TEL-7-UNK:CallID:58 MediaId:66342/2 Task:19000000072 com.cisco.jtapi.CiscoRTPInputStartedEvImpl received

The call is put on hold at the CTI port and so CiscoRTPInputStoppedEv is received61086: Jan 15 10:45:42.832 CST %MIVR-SS_TEL-7-UNK:CallID:58 MediaId:66342/2 Task:19000000072 com.cisco.jtapi.CiscoRTPInputStoppedEvImpl received

The call is put on hold at the CTI port and so CiscoRTPOutputStoppedEv is received61087: Jan 15 10:45:42.832 CST %MIVR-SS_TEL-7-UNK:CallID:58 MediaId:66342/2 Task:19000000072 com.cisco.jtapi.CiscoRTPOutputStoppedEvImpl received

The call on the CTI port goes on hold61088: Jan 15 10:45:42.832 CST %MIVR-SS_TEL-7-UNK:CallID:58 MediaId:66342/2 Task:19000000072, TerminalConnection to Terminal: CTI_1904 is HELD