This document was generated from CDN thread
Created by: Chikeobi Njaka on 15-03-2012 06:08:19 PM
Hi Folks,
We have a recording solution that so far has been workign with all of Cisco's IP Phone devices (the split-stream ones), including IPC 7.0.5.0+. The problem we are seeing with a customer is that while all hard phones record with no problem, we are seeing a weird problem with IPC. Not on just one PC, but multiple PC's. One things we have noticed s that there seems to be no SIP signalling between the IPC and the recorder server. Once again, all the other phones work file.
I was wondering if maybe there is something in the device profile that may cause this to happen (for IPC). Below are a few of the errors we see when recording is supposed to commense:
******************************
Error Code: -1932787703
Error Name: CTIERR_ILLEGAL_CALLSTATE
Error Description: Connection is not in a valid state.
************
current tconn state [SEP18A9051836BF/[49462
hones/(P1-vmappuser) GCID=(2,15834264)->ACTIVE]->FAILED]->TALKING 98
************
When hanging up on the call.... we get the following...
TermConnDroppedEv SEP081735D5E6CB (P1-vmappuser) GCID=(2,15834264)->INVALID
CallCtlTermConnDroppedEv SEP081735D5E6CB (P1-vmappuser) GCID=(2,15834264)->INVALID
CallCtlTermConnDroppedEv ==> Number of Connections: 0
ConnDisconnectedEv (P1-vmappuser) GCID=(2,15834264)->INVALID
CallCtlConnDisconnectedEv (P1-vmappuser) GCID=(2,15834264)->INVALID
CallInvalidEv (P1-vmappuser) GCID=(2,15834264)->INVALID
********************
Any ideas?
Thanks.
Subject: RE: Recording & IP Communicator
Replied by: David Staudt on 16-03-2012 06:09:53 PM
IPC 7.0.5 should be supported for recording, and there should be no special config that you are not already familiar with from the hard phones. One thing to consider is if you are requesting the recording start after receiving the connected event or if you are waiting for the RTP start events. I would suggest waiting for the events.
To fully understand why the failure is occuring, we will likely need the detailed JTAPI logs, and possibly CTI-Manager/Callmanager as well. For best results and attention I would recommend opening a formal CDN Developer Support case.
Created by: Chikeobi Njaka on 15-03-2012 06:08:19 PM
Hi Folks,
We have a recording solution that so far has been workign with all of Cisco's IP Phone devices (the split-stream ones), including IPC 7.0.5.0+. The problem we are seeing with a customer is that while all hard phones record with no problem, we are seeing a weird problem with IPC. Not on just one PC, but multiple PC's. One things we have noticed s that there seems to be no SIP signalling between the IPC and the recorder server. Once again, all the other phones work file.
I was wondering if maybe there is something in the device profile that may cause this to happen (for IPC). Below are a few of the errors we see when recording is supposed to commense:
******************************
Error Code: -1932787703
Error Name: CTIERR_ILLEGAL_CALLSTATE
Error Description: Connection is not in a valid state.
************
current tconn state [SEP18A9051836BF/[49462
hones/(P1-vmappuser) GCID=(2,15834264)->ACTIVE]->FAILED]->TALKING 98************
When hanging up on the call.... we get the following...
TermConnDroppedEv SEP081735D5E6CB (P1-vmappuser) GCID=(2,15834264)->INVALID
CallCtlTermConnDroppedEv SEP081735D5E6CB (P1-vmappuser) GCID=(2,15834264)->INVALID
CallCtlTermConnDroppedEv ==> Number of Connections: 0
ConnDisconnectedEv (P1-vmappuser) GCID=(2,15834264)->INVALID
CallCtlConnDisconnectedEv (P1-vmappuser) GCID=(2,15834264)->INVALID
CallInvalidEv (P1-vmappuser) GCID=(2,15834264)->INVALID
********************
Any ideas?
Thanks.
Subject: RE: Recording & IP Communicator
Replied by: David Staudt on 16-03-2012 06:09:53 PM
IPC 7.0.5 should be supported for recording, and there should be no special config that you are not already familiar with from the hard phones. One thing to consider is if you are requesting the recording start after receiving the connected event or if you are waiting for the RTP start events. I would suggest waiting for the events.
To fully understand why the failure is occuring, we will likely need the detailed JTAPI logs, and possibly CTI-Manager/Callmanager as well. For best results and attention I would recommend opening a formal CDN Developer Support case.