Recording voice traffic from Cisco Ip Communicator

[Frantisek Opravil]

Can you help me with CallRecording from Cisco IP Communicator?

I cannot record voice traffic going through CIPC configured with SCCP protocol.
We are using IP phone based recording, codec G.711 ulaw.
The CIPC is configured according to https://supportforums.cisco.com/discussion/12076306/call-recording-cipc.

We are using CUCM System version: 10.5.2.11900-3, the CIPC is version is 8.6.5.0. 
The selective call recording is controlled by Genesys service, Genesys Stream Recorder is used as voice recorder.
Call recording with Cisco IP phones 7941 and 7942 works OK.,
and recording with CIPC configured with SIP protocol works OK, too.

Unfortunately the Cisco IP Communicators with SIP protocol gets locked up intermittently; CDR records show cause 1459617833,
it corresponds to "CCM_SIP_503_SERVICE_UNAVAILABLE". The CIPC won't receive then any incoming call until the PC is reloaded.
There is no indication of the locked up state on the  CIPC screen, so CIPC users won't recognize it.
So I would prefer to use the CIPC with SCCP protocol.

The packet sniffer (Wireshark) shows, that the errors comes from the CallManager.
The SCCP packet type "StartMediaTransmissionAck" of the 2-nd voice stream to recorder is in error:
field "transmitIpAddr IPv4 Address" is OK but "transmitPort" is zero; the 2-nd voice stream is not sent to recorder. 

Thank you. 

[GadgetFood · Accepted solution]

If you try the new version does the issue still occur?

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cipc/8_6_6/Release_Notes.html#CIPS_RF_RDB3162D_00

I am not using the same service for recording but most of my users having issue with IP Communicator once I upgraded them the issue went away So not sure if this was something on PC or issue happening with that version.

[Frantisek Opravil]

Thank you James,

I have tested the CIPC version 8.6.6, configured for CallRecording - IP Phone Based Recording, configured with SCCP protocol, it worked OK. Probably the CUCM version 10.5.2.11900-3 needs it.

Many thanks for your help!