/build/static/layout/Breadcrumb_cap_w.png

Cisco Systems, Inc. Cisco IP Communicator

Version: 7

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 10.2k  |  Created: 04/02/2009

Average Rating: 0
Cisco IP Communicator has 1 inventory records, 2 Questions, 1 Blogs and 1 links. Please help add to this by sharing more!

Deployment Tips (3)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 2 / 5 (Somewhat Easy) based on 2 ratings
Most Commonly Reported Deployment Method
Windows Installer with Custom Transform (MST)
10
Command Line
To assign the TFTP Servers direct during installation use the following cmd-Line extensions TFTP1 and TFTP2.

EXAMPLE:
msiexec /I [PackageName].msi ADDLOCAL="ALL" ARPSYSTEMCOMPONENT="1" /qb-! TFTP1="[IP-Adress]" TFTP2="[IP-Adress]"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
9
Note
I've deployed this recently and had to add these registry keys to manually set the servers. (.1 as primary server keys and .2 as secondary server keys). I know that this worked to automate the servers in the deployment.

[HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager2.address]
"val3"="0.0.0.1"
"val5"="0.0.0.1"

[HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager2.name]
"val3"="0.0.0.1"
"val5"="0.0.0.1"

[HKEY_USERS\S-1-5-21-1386374537-1830773436-986007298-1008\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager2.address]
"val3"="0.0.0.1"
"val5"="0.0.0.1"

[HKEY_USERS\S-1-5-21-1386374537-1830773436-986007298-1008\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager2.name]
"val3"="0.0.0.1"
"val5"="0.0.0.1"

[HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager1.address]
"val3"="0.0.0.2"
"val5"="0.0.0.2"

[HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager1.name]
"val3"="0.0.0.2"
"val5"="0.0.0.2"

[HKEY_USERS\S-1-5-21-1386374537-1830773436-986007298-1008\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager1.address]
"val3"="0.0.0.2"
"val5"="0.0.0.2"

[HKEY_USERS\S-1-5-21-1386374537-1830773436-986007298-1008\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.config.callmanager.callmanager1.name]
"val3"="0.0.0.2"
"val5"="0.0.0.2"

Also, we upgraded our call manager to authenticate to Active Directory instead of with the Computers Mac Address, and these are the registry changes that I made to put the description in as well as change it to authenticate off of description.

"HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\HostName"
"HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\AlternateDeviceName"
"HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Communicator\HostName"
"HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Communicator\AlternateDeviceName"

My formatting is a little off as I had to make a VBScript to automate the changes to change the ones that were already deployed and were authentificating off of MAC address still.

As a Additional Note - As of 04/17 after IP Comm. 7 installs and is run for the first time, it will automatically update. The TFTP servers are upated to be stored in the following loations:

[HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Communicator]
"TftpServer1"=dword:15001b0a
"TftpServer2"=dword:1410dc0a

[HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator]
"TftpServer1"=dword:15001b0a
"TftpServer2"=dword:1410dc0a

The actual servers are stored in DWORD Decimal format and need to be passed in that way. Here is how to turn a IP into Decimal format using 10.160.0.1 as a test case. Use this formula: (((((((A*256)+B)*256)+C)*256)+D)) where A=10, B=160, C=0, and D=1. So the decimal for ip 10.160.0.1 is 178257921. You can ping that number just like an ip and the numbers are interchangable. For some reason, when IP Communicator calls the decimal from the registry, it formats it backwards, so you need to use (((((((D*256)+C)*256)+B)*256)+A)) for this install only. I hope this helps. I wrote a script to autofill the username (formatted however you need for callmanager) and to populate the correct fields, let me know if you need this. Thanks!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
2
Command Line
For Cisco IP Communicator 7.0.1.0 I used the following...

Run Parameters: /i

Full Command Line: msiexec /i ciscoipc.msi /passive /norestart
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Cisco IP Communicator

Version

7

Questions & Answers (2)

Questions & Answers related to Cisco Systems, Inc. Cisco IP Communicator

1
ANSWERED
4
ANSWERS

Blogs (1)

Blog posts related to Cisco Systems, Inc. Cisco IP Communicator

blog

Reviews (0)

Reviews related to Cisco Systems, Inc. Cisco IP Communicator

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ