Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

How encryption affects IPCCX?

My customer has a cluster with two CallManager running version 5.1.3a. In addition to this, it has a IPCCX 4.5.2 with 10 agents. He wants to implement encryption in the cluster and in the IP calls. How does it affect the IPCCX and the agents? Could I apply encryption to all the system (CUCM cluster + IPCCX + IP phones)? Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
Super Bronze

Re: How encryption affects IPCCX?

Hi

You can apply encryption only to devices that support it.

IPCCX doesn't support it at present.

So this means that you can enable it on phones, you can enable it on gateways (provided they run Adv IP Services or Adv Enterprise Services - SP services or Voice will not do), and you can enable it on IOS-based trancoders/conference bridges (assuming the correct IOS feature level as above).

The impact of this will be that when two devices communicate that BOTH support encryption, the call will encrypt.

If a call goes from gateway to IPCC, it will not be encrypted.

The same call then transfers to an agent, and it will be encrypted from that point.

The main effect on IPCCX is that silent monitoring and recording will not work, as IPCCX cannot decrypt the voice streams that it sniffs from the network (this being the behaviour that encryption is designed to prevent).

Hope this helps

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
1 REPLY
Super Bronze

Re: How encryption affects IPCCX?

Hi

You can apply encryption only to devices that support it.

IPCCX doesn't support it at present.

So this means that you can enable it on phones, you can enable it on gateways (provided they run Adv IP Services or Adv Enterprise Services - SP services or Voice will not do), and you can enable it on IOS-based trancoders/conference bridges (assuming the correct IOS feature level as above).

The impact of this will be that when two devices communicate that BOTH support encryption, the call will encrypt.

If a call goes from gateway to IPCC, it will not be encrypted.

The same call then transfers to an agent, and it will be encrypted from that point.

The main effect on IPCCX is that silent monitoring and recording will not work, as IPCCX cannot decrypt the voice streams that it sniffs from the network (this being the behaviour that encryption is designed to prevent).

Hope this helps

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
116
Views
0
Helpful
1
Replies
CreatePlease to create content