cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1119
Views
1
Helpful
3
Replies

Cisco IP Communicator - Disabling HTTP config download

abendayan
Level 1
Level 1

Good day,

 

I have a problem where IP Communicator is taking 10 minutes to download it's configuration.  We know the problem, it stems from an issue on internal proxy servers to proxy the HTTP config files from CUCM.  We can clearly see in the debugs that the instant the CIPC client finally decides to use TFTP the config file is downloaded and the client registers.  So my question is this, can we shorten that timeout window to just a few seconds or is there a way to tell the CIPC client via a registry entry to forego HTTP download of the config and just default to TFTP?  I have looked and looked online but cannot find a way to disable this.


We are using CIPC Client 8.6.2.0 with CUCM 11.5.

 

Thanks!

 

AB

1 Accepted Solution

Accepted Solutions

abendayan
Level 1
Level 1

We opened up a TAC case and this behavior can be changed.  There is a registry entry entitled "EnableHttpDownload" that you can set to "0" and it will change this behavior.  On my machine the entry was located in:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems, Inc.\Communicator

 

If you do not find it in this spot just search the registry for that entry and as far as I can see it is only in there one time.

 

I validated via wireshark captures before and after the change that when set to "0" the CIPC client does default directly to TFTP.

 

Thanks!

 

AB

 

View solution in original post

3 Replies 3

Jaime Valencia
Cisco Employee
Cisco Employee

AFAIK there is no way to modify that behavior.

HTH

java

if this helps, please rate

Thank you.  

Is there a published document that lists all the possible registry entries available for the CIPC client?  

 

Thanks!

 

AB

abendayan
Level 1
Level 1

We opened up a TAC case and this behavior can be changed.  There is a registry entry entitled "EnableHttpDownload" that you can set to "0" and it will change this behavior.  On my machine the entry was located in:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems, Inc.\Communicator

 

If you do not find it in this spot just search the registry for that entry and as far as I can see it is only in there one time.

 

I validated via wireshark captures before and after the change that when set to "0" the CIPC client does default directly to TFTP.

 

Thanks!

 

AB