Wednesday, October 5, 2011

Contact is in Terminated/Connected State

I came across this error the other day on a new UCCX 8 install.  You call into any of the triggers, but disconnects immediately.  Doing a reactive debug shows that it fails on the Accept step in the script with the following error:

Contact ID:x, Channel ID:y, Contact is in Terminated/Connected state.

You will notice that x and y will change based on your call attempts.  I tried upgrading to 8.5(1)SU1 and 8.5(1)SU2, but didn't help.

Also, in the trace files that you can grab via RTMT, you will see the following entry:

4323: Oct 01 10:25:12.495 CDT %MIVR-SS_TEL-7-UNK:CallID:4 MediaId:5937/2 Task:17000000003, CallCtlConnFailed, Inbound call, callctl cause:107, [6612:PT_Internal:1/(P1-jtapi_1) GCID=(2,4323)->ACTIVE]->FAILED

Now, ask anyone else, any you will most likely be told that it is a codec issue 99% of the time with a callctl cause of 107.  That is true.  But, in this case, it is not.

The fix is to create a new Media Termination Dialog Group and apply it to your triggers.  TAC said it has something to do with the fact that if your licensing is messed up when you setup the initial Media Termination Dialog Group, it won't work and you have to recreate it once your licensing are setup correctly.

Thanks,
IPTBuzz

No comments: