Cchetty: 1 revision

2010-04-09T15:20:55Z

1 revision

← Older revision

Revision as of 15:20, 9 April 2010

Srib: /* Call fails with CallCtlConnFailed event */

2010-01-30T01:13:02Z

Call fails with CallCtlConnFailed event

New page

== Call fails with CallCtlConnFailed event ==

{| border="1"
|-
! '''Problem Summary'''
| Call receives CallCtlConnFailed event. Unified CCX drops the call only when CallCtlConnFailedEv is received with certain cause codes like: 203 (CAUSE_BUSY), 103 (CAUSE_DEST_NOT_OBTAINABLE)
 For most other cause codes, Unified CCX does not recognize the failure and will continue to process the call. This will lead to other failures as all operations on this call are now invalid as the call has actually failed though Unified CCX did not recognize the failure.
|-
! '''Error Message'''
| Cisco001MIVR010[1].log.txt 3085 36745440: Jan 05 12:14:30.424 EDT %MIVR-SS_TEL-7-UNK:CallID:2311 MediaId:1759881/3 Task:28000079448, CallCtlConnFailed, Inbound call, callctl cause:101, [777044:Internal/(P1-jtapiuser_1) GCID=(3,1759881)->ACTIVE]->FAILED

|-
! '''Possible Cause'''
| Some issue in JTAPI / CTI that lead to the failure of the call.
|-
! '''Recommended Action'''
| <ol>
<li>Find the cause code for the CallCtlConnFailed from the MIVR/JTAPI client logs
<li>The description of the cause code can be found under '''Cause Codes''' section at the link: http://docwiki-dev.cisco.com/wiki/Common_Cause_Codes_and_Meta_Codes_in_JTAPI
<li>With all the relevant logs, escalate this to IPCBU JTAPI team
<li>Note that cause code 107 can but not necessarily indicate codec mismatch between caller and CTI port (http://docwiki-dev.cisco.com/wiki/Codec_Mismatch_between_Caller_and_CTI_Port)

 
Example:
 In this case, CallCtlConnFailed is received with cause 101. Unified CCX does not recognize this cause code and continues to process this call which leads to further errors.
 36745440: Jan 05 12:14:30.424 EDT %MIVR-SS_TEL-7-UNK:CallID:2311 MediaId:1759881/3 Task:28000079448, '''CallCtlConnFailed''', Inbound call, '''callctl cause:101''', [777044:Internal/(P1-jtapiuser_1) GCID=(3,1759881)->ACTIVE]->FAILED
 36745602: Jan 05 12:14:34.174 EDT %MIVR-SS_TEL-7-UNK:CallID:2311 MediaId:1759881/3 Task:28000079448, transfer(5555220004, 20000, ACKNOWLEDGED)
 36745621: Jan 05 12:14:34.174 EDT %MIVR-SS_TEL-3-CALL_CONTROL_INVAL_STATE:Invalid state for Call Control operation: All Call ids=CallID:2311 MediaId:1759881/3 Task:28000079448,Failure type for the CallControl error=CONSULT,Connection State=33,Failure reason=CTIERR_ILLEGAL_CALLSTATE=0x8ccc0009::Line is not in a legal state to invoke the command,Exception=com.cisco.jtapi.InvalidStateExceptionImpl: Call state not valid to initiate calls.
 36745645: Jan 05 12:14:34.174 EDT %MIVR-SS_TEL-7-UNK:Call.transferFailed(5555220004, UNKNOWN) JTAPICallContact[id=2311,implId=1759881/3,state=STATE_ANSWERED_IDX,inbound=true,App name=HOTLINE_QUEUE,task=28000079448,session=34000047642,seq num=1,cn=5556667102,dn=5556667102,cgn=7327708728,ani=null,dnis=null,clid=null,atype=DIRECT,lrd=null,ocn=5556667102,route=RP[num=5556667102],TP=777044]

</ol>
|-
! '''Release'''
| Release 7.0(1) onwards
|-
! '''Associated CDETS #'''
| NA
|-
|}

[[Category:Unified CCX, Release 8.0]]
[[Category:Unified CCX, Release 7.0]]

Call fails with CallCtlConnFailed event - Revision history

Cchetty: 1 revision

Srib: /* Call fails with CallCtlConnFailed event */