Я использую только Google Talk, и было интересно, если есть какие-либо клиенты командной строки jabber для windows? Я предпочитаю командной строки, как я использую его много на ежедневной основе, и это кажется гораздо проще. Клиент может быть либо какой-нибудь программой только для windows, либо скриптом python/ruby/perl. все в порядке.
2 ответов
MCabber
MCabber это (довольно популярно, думаю) текст-режим клиента.
mcabber — небольшой консольный клиент Jabber. mcabber включает в себя такие функции, как поддержка SASL/SSL/TLS, поддержка MUC (многопользовательский чат), ведение журнала, завершение команды, шифрование OpenPGP, поддержка OTR (Off-The-Record Messaging), динамические модули и триггеры внешних действий.
Finch (Pidgin)
мультипротокольным клиентом пиджин предлагает текстовый клиент:Finch.
Finch-это консольная IM-программа, которая позволяет вам входить в AIM, Jabber, MSN, Yahoo! и другие IM-сети.
GNU Freetalk
Freetalk является консольным клиентом Jabber. Он имеет интерфейс readline с завершением имен друзей, команд и даже обычных английских слов. Freetalk расширяемый, настраиваемый, и scriptable через хитрый интерфейс.
irssi-xmpp
плагин для irssi (который является клиентом IRC):irssi-xmpp
irssi-xmpp является плагином irssi для подключения к сети Jabber.
его цель состоит в том, чтобы обеспечить хорошую интеграцию в этом текстовом IRC-клиенте и хорошую поддержку XMPP (Jabber протокол.)
Poezio
Poezio — это бесплатный консольный XMPP-клиент (протокол, на котором построена сеть Jabber IM).
ругательство
ненормативная лексика-это простой клиент Jabber, написанный на C с использованием ncurses и libstrophe, вдохновленный Irssi.
CenterIM5 поддерживает XMPP (и GTalk), а также. Он имеет приятный интерфейс curses, но требует ввода ctrl+x для отправки сообщений. Для меня это была остановка шоу: слишком много усилий. Ваш пробег может отличаться.
Jabber command line windows
Xmpp Sender ¶ ↑
This program sends XMPP (Jabber) messages passed by command line.
It just starts, reads command line parameters, then reads config file, then it logins to server, sends specified message and quits.
I wrote it to have fun receiving notifications from remote rtorrent each time it finishes loading a torrent. But it could be used with any program which could run external utility by an event you want to be reported about.
Launch setup.exe and follow it’s directions
Run Xmpp Sender by using a shortcut created during setup
Add ruby to firewall exceptions when dialog pops up
Edit xmpp_sender.yml to use your own defaults
HOW TO USE WITH RTORRENT ¶ ↑
I’ve tested it with rtorrent 3.0.
So you’ve installed Xmpp Sender to C:\Program Files\Xmpp Sender directory.
Try to issue in cmd the following command: C:\Program Files\Xmpp Sender\xmpp_sender.exe -j ‘rtorrent just finished %N’ -b ‘torrent loaded to: %D’
You should recieve a new message in your IM with subject rtorrent just finished %N and body torrent loaded to: %D .
If you’ve received that message, then launch rtorrent ang go to Options/Preferences/Advanced/Run Program tab
Type in the field labeled Run this program when a torrent finishes this string: C:\Program Files\Xmpp Sender\xmpp_sender.exe -j ‘rtorrent just finished %N’ -b ‘torrent loaded to: %D’
Click OK button and try to load some torrents. Enjoy!
If you want to compile it you need to clone the repo git://github.com/Zloy/xmpp_sender.git and install Inno_Setup, ruby_1.8.7 and xmpp4r, ocra gems.
Change dir to where you’ve placed the cloned repo, say it be C:\ruby_apps\xmpp_sender .
Command line jabber chat clients for windows?
I only use Google Talk, and was wondering if there were any jabber command line clients for windows? I prefer command-line as I use it a lot on a day to day basis, and it seems much easier. The client can be either some windows only program, or a python/ruby/perl script. anything is fine.
2 Answers 2
MCabber
MCabber is a (quite popular, I think) text-mode client.
mcabber is a small Jabber console client. mcabber includes features such as SASL/SSL/TLS support, MUC (Multi-User Chat) support, history logging, command completion, OpenPGP encryption, OTR (Off-the-Record Messaging) support, dynamic modules and external action triggers.
Finch (Pidgin)
The multi-protocol client Pidgin offers a text client: Finch.
Finch is a console-based IM program that lets you sign on to AIM, Jabber, MSN, Yahoo!, and other IM networks.
GNU Freetalk
Freetalk is a console based Jabber client. It features a readline interface with completion of buddy names, commands, and even ordinary English words. Freetalk is extensible, configurable, and scriptable through a Guile interface.
irssi-xmpp
A plugin for irssi (which is an IRC client): irssi-xmpp
irssi-xmpp is an irssi plugin to connect to the Jabber network.
Its aim is to provide a good integration in this text-based irc client and a good support of XMPP (the Jabber protocol).
Poezio
Poezio is a free console XMPP client (the protocol on which the Jabber IM network is built).
Profanity
Profanity is a simple Jabber client written in C using ncurses and libstrophe, inspired by Irssi.
Мгновенное сообщение из консоли в jabber
Нередко перед системными администраторами встает задача оповещения себя и коллег о каких-либо событиях на сервере, будь то отчет об успешных входах по ssh, резко возросшая нагрузка, падение сервиса, сообщение о переключении на резервное питание или вскипевшем чайнике. Чаще всего такая задача решается, например, отправкой почтового сообщения. Но нельзя гарантировать, что сообщение, во-первых, прийдет вовремя, а во-вторых, что его сразу прочтут. Тогда, подумает администратор, будем использовать IM. Но как? Держать, например, centerim постоянно открытым в screen? Согласитесь, не самый радужный вариант. На выручку к нам спешит чип и дейл открытый протокол XMPP. Написано множество расширений к популярным языкам и примеров кода, позволяющих отослать сообщение кому требуется, и отослать его быстро. Пример такого кода я и приведу.
Когда мне понадобился такой функционал, я пробежался по существующим решениям на таких популярных языках, как C, php, perl, python. Некоторые предполагали использование уже готовых классов, некоторые — подгрузку модулей. Код был чудовищно громоздким и неудобочитаемым, а я искал элегантное решение. И оно было найдено в Питоне.
Итак, условимся, что работаем в Linux. На самом деле, скрипт наверняка сможет работать и в Windows, но такой целью я не задавался. Нам понадобится, собственно, сам python, а также два модуля — любой dns и xmpppy, который представлен в Debian пакетом python-xmpp.
Скрипт, используя переданные ему JID и пароль, авторизуется на сервере, отправляет сообщение и закрывает соединение. Проще некуда. Вам потребуется сделать отдельную учетку для скрипта (но можно и не делать, jabber разрешает множественные одновременные подключения с разным resource) и внести учетные данные в переменные xmpp_jid и xmpp_pwd.
Сохраните код в файл, сделайте его исполняемым, запускайте. Запуск выглядит следующим образом:
/home/username/scripts/send_xmpp_message username@email.server.ru «привет, это твой любимый сервер, не забудь вынуть пиво из серверного шкафа»
Полет фантазии неограничен: после легкой модификации, например, в скрипт можно будет перенаправлять данные вместо передачи аргументов, а используя crontab, отправлять сообщения по расписанию.
Cisco Jabber 11.0 Deployment and Installation Guide
Book Title
Cisco Jabber 11.0 Deployment and Installation Guide
Chapter Title
View with Adobe Reader on a variety of devices
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
View on Kindle device or Kindle app on multiple devices
Results
Chapter: Install Client
Install Client
Install Cisco Jabber for Windows
Cisco Jabber for Windows provides an MSI installation package that you can use in the following ways:
You can specify arguments in a command line window to set installation properties.
Choose this option if you plan to install multiple instances.
Run the MSI manually on the file system of the client workstation and then specify connection properties when you start the client.
Choose this option if you plan to install a single instance for testing or evaluation purposes.
Open the default installation package, specify the required installation properties, and then save a custom installation package.
Choose this option if you plan to distribute an installation package with the same installation properties.
Install the client on multiple computers in the same domain.
Before You Begin
You must be logged in with local administrative rights.
Use the Command Line
Specify installation arguments in a command line window.
Procedure
Step 1
Open a command line window.
Step 2
Enter the following command:
Step 3
Specify command line arguments as parameter=value pairs.
Step 4
Run the command to install Cisco Jabber for Windows .
Example Installation Commands
Review examples of commands to install Cisco Jabber for Windows.
Cisco Unified Communications Manager, Release 9.x
Cisco Unified Communications Manager, Release 8.x in Default Mode
Cisco Unified Communications Manager, Release 8.x in Phone Mode
If you are integrating with UDS when you are installing in phone mode, you must first define the Where:
CLEAR =1 — Deletes any existing bootstrap file.
PRODUCT_MODE =Phone_Mode — Sets the client to phone mode.
AUTHENTICATOR =CUCM — Sets Cisco Unified Communications Manager as the authenticator.
TFTP =1.2.3.4 — Sets 1.2.3.4 as the IP address of the TFTP server that hosts the client configuration.
CTI =5.6.7.8 — Sets 5.6.7.8 as the IP address of the CTI server.
/quiet — Specifies a silent installation.
Cisco WebEx Messenger Service
Cisco WebEx Messenger Service with SSO
Command Line Arguments
Review the command line arguments you can specify when you install Cisco Jabber for Windows.
Override Argument
The following table describes the parameter you must specify to override any existing bootstrap files from previous installations:
Specifies if the client overrides any existing bootstrap file from previous installations.
The client saves the arguments and values you set during installation to a bootstrap file. The client then loads settings from the bootstrap file at startup.
If you specify CLEAR , the following occurs during installation:
The client deletes any existing bootstrap file.
The client creates a new bootstrap file.
If no bootstrap file exists, the client creates a bootstrap file during installation.
If a bootstrap file exists, the client does not override that bootstrap file and preserves the existing settings.
Note
If you are reinstalling Cisco Jabber for Windows, you should consider the following:
The client does not preserve settings from existing bootstrap files. If you specify CLEAR , you must also specify all other installation arguments as appropriate.
The client does not save your installation arguments to an existing bootstrap file. If you want to change the values for installation arguments, or specify additional installation arguments, you must specify CLEAR to override the existing settings.
To override existing bootstrap files, specify CLEAR in the command line as follows:
Mode Type Argument
The following table describes the command line argument with which you specify the product mode:
Argument
Value
Description
Phone_Mode — Cisco Unified Communications Manager is the authenticator.
Choose this value to provision users with audio devices as base functionality.
When to Set the Product Mode
Cisco Unified Communications Manager, Release 9.x and Later — You should not set PRODUCT_MODE during installation. The client gets the authenticator from the service profile. After the user signs in, the client requires a restart to enter phone mode.
Cisco Unified Communications Manager, Release 8.x — You can specify phone mode during installation if you set Cisco Unified Communications Manager as the authenticator. The client reads the bootstrap file on the initial launch and determines it should start in phone mode. The client then gets Cisco Unified Communications Manager as the authenticator from the bootstrap file or manual settings. After the user signs in, the client does not require a restart.
Change Product Modes
To change the product mode, you must change the authenticator for the client. The client can then determine the product mode from the authenticator.
The method for changing from one product mode to another after installation, depends on your deployment.
Note
In all deployments, the user can manually set the authenticator in the Advanced settings window.
In this case, you must instruct the user to change the authenticator in the Advanced settings window to change the product mode. You cannot override the manual settings, even if you uninstall and then reinstall the client.
Change Product Modes with Cisco Unified Communications Manager Version 9.x and Later
To change product modes with Cisco Unified Communications Manager version 9.x and later, you change the authenticator in the service profile.
Procedure
Step 1
Change the authenticator in the service profiles for the appropriate users. Change Default Mode > Phone Mode
Do not provision users with an IM and Presence service.
If the service profile does not contain an IM and presence service configuration, the authenticator is Cisco Unified Communications Manager.
Change Phone Mode > Default Mode
Provision users with an IM and Presence service.
If you set the value of the Product type field in the IM and Presence profile to:
Unified CM (IM and Presence) the authenticator is Cisco Unified Communications Manager IM and Presence Service.
WebEx (IM and Presence) the authenticator is the Cisco WebEx Messenger service.
Step 2
Instruct users to sign out and then sign in again.
When users sign in to the client, it retrieves the changes in the service profile and signs the user in to the authenticator. The client then determines the product mode and prompts the user to restart the client.
After the user restarts the client, the product mode change is complete.
Change Product Modes with Cisco Unified Communications Manager Version 8.x
To change product modes with Cisco Unified Communications Manager version 8.x, you must reinstall Cisco Jabber for Windows to change the authenticator.
Change Default Mode > Phone Mode Set the following arguments, at a minimum:
CLEAR =1 to delete any existing bootstrap file.
AUTHENTICATOR =CUCM to set the authenticator to Cisco Unified Communications Manager.
PRODUCT_MODE =Phone_Mode to set phone mode as the product mode.
CLEAR =1 to delete any existing bootstrap file.
CUP to set the authenticator to Cisco Unified Presence or Cisco Unified Communications Manager.
WEBEX to set the authenticator to the Cisco WebEx Messenger service.
Authentication Arguments
The following table describe the command line arguments you can set to specify the source of authentication:
Argument
Value
Description
AUTHENTICATOR
CUP—Cisco Unified Communications Manager IM and Presence Service. On-premises deployments in the default product mode. The default product mode can be either full UC or IM only.
CUCM—Cisco Unified Communications Manager. On-premises deployments in phone mode.
WEBEX—Cisco WebEx Messenger Service. Cloud-based or hybrid cloud-based deployments.
In on-premises deployments with Cisco Unified Communications Manager version 9.x and later, you should deploy the _cisco-uds SRV record. The client can then automatically determine the authenticator.
IP address ( 123.45.254.1 )
IP address ( 123.45.254.1 )
You should specify this argument if you set Cisco Unified Communications Manager as the authenticator.
In phone mode—you should specify the address of the TFTP server that hosts the client configuration.
In default mode—you can specify the address of the Cisco Unified Communications Manager TFTP service that hosts the device configuration.
Sets the address of your CTI server.
Specify this argument if:
You set Cisco Unified Communications Manager as the authenticator.
Users have desk phone devices and require a CTI server.
Sets the address of your CCMCIP server.
Specify this argument if:
You set Cisco Unified Communications Manager as the authenticator.
The address of your CCMCIP server is not the same as the TFTP server address.
The client can locate the CCMCIP server with the TFTP server address if both addresses are the same.
Cisco Unified Communications Manager release 9.x and earlier—If you enable Cisco Extension Mobility, the Cisco Extension Mobility service must be activated on the Cisco Unified Communications Manager nodes that are used for CCMCIP. For information about Cisco Extension Mobility, see the Feature and Services guide for your Cisco Unified Communications Manager release.
Sets the value of the domain where the DNS SRV records for Service Discovery reside.
This argument can be set to a domain where no DNS SRV records reside if you want the client to use installer settings or manual configuration for this information. If this argument is not specified and Service Discovery fails, the user will be prompted for services domain information.
Domain
In Hybrid Deployments the domain required to discover Webex via CAS lookup may be a different domain than where the DNS records are deployed. If this is the case then set the SERVICES_DOMAIN to be the domain used for Webex discovery (or let the user enter an email address) and set the VOICE_SERVICES_DOMAIN to be the domain where DNS records are deployed. If this setting is specified, the client will use the value of VOICE_SERVICES_DOMAIN to lookup the following DNS records for the purposes of Service Discovery and Edge Detection:
_cisco-uds
_cuplogin
_collab-edge
This setting is optional and if not specified, the DNS records are queried on the Services Domain which is obtained from the SERVICES_DOMAIN , email address input by the user, or cached user configuration.
One or more of:
CUP
WEBEX
CUCM
Lists the services that you want Jabber to exclude from Service Discovery. For example, you may have done a trial with WebEx which means that your company domain is registered on WebEx, but you do not want Jabber users to authenticate using WebEx. You want Jabber to authenticate with an on-premises CUP CUCM server. In this case set:
Possible values are CUP, CUCM, WEBEX.
To exclude more than one service, use comma separated values. For example, to exclude CUP and CUCM, specify: EXCLUDED_SERVICEs =CUP,CUCM . To exclude all services, specify: EXCLUDED_SERVICES =CUP,CUCM,WEBEX
If you exclude all services, you need to use manual configuration or bootstrap configuration to configure the Jabber client.
true (default)—The UPN is used to find the User ID and the domain of the user, which is used during service discovery. Only the user discovered from UPN can log in to the client.
false—The UPN is not used to find the User ID and domain of the user. The user is prompted to enter credentials to find the domain for service discovery.
Example installation command: msiexec.exe /i CiscoJabberSetup.msi /quiet UPN_DISCOVERY_ENABLED =false
TFTP Server Address
Client configuration files that you create.
Device configuration files that reside on the Cisco Unified Communications Manager TFTP service when you provision users with devices.
To minimize effort, you should host your client configuration files on the Cisco Unified Communications Manager TFTP service. You then have only one TFTP server address for all configuration files and can specify that address as required.
You can, however, host your client configuration on a different TFTP server to the one that contains the device configuration. In this case, you have two different TFTP server addresses, one address for the TFTP server that hosts device configuration and another address for the TFTP server that hosts client configuration files.
Default Deployments
This section describes how you should handle two different TFTP server addresses in deployments that have a presence server.
You should do the following:
Specify the address of the TFTP server that hosts the client configuration on the presence server.
During installation, specify the address of the Cisco Unified Communications Manager TFTP service with the TFTP argument.
Retrieves the address of the Cisco Unified Communications Manager TFTP service from the bootstrap file.
Gets device configuration from the Cisco Unified Communications Manager TFTP service.
Connects to the presence server.
Retrieves the address of the TFTP service that hosts the client configuration from the presence server.
Gets client configuration from the TFTP server.
Phone Mode Deployments
This section describes how you should handle two different TFTP server addresses in phone mode deployments.
You should do the following:
During installation, specify the address of the TFTP server that hosts the client configuration with the TFTP argument.
Specify the address of the TFTP server that hosts the device configuration in your client configuration file with the following parameter: TftpServer1.
Host the client configuration file on the TFTP server.
Retrieves the address of the TFTP server from the bootstrap file.
Gets client configuration from the TFTP server.
Retrieves the address of the Cisco Unified Communications Manager TFTP service from the client configuration.
Gets device configuration from the Cisco Unified Communications Manager TFTP service.
Common Installation Arguments
The following table describes command line arguments that are common to all deployments:
Argument
Value
Description
LCID in decimal
Defines the Locale ID (LCID), in decimal, of the language that Cisco Jabber for Windows uses. The value must be an LCID in decimal that corresponds to a supported language.
For example, you can specify one of the following:
1033 specifies English.
1036 specifies French.
See the LCID for Languages topic for a full list of the languages that you can specify.
This argument is optional.
If you do not specify a value, Cisco Jabber for Windows uses the regional language for the current user as the default.
From Release 11.1(1) onwards, if you do not specify a value, Cisco Jabber for Windows checks the value for the UseSystemLanguage parameter. If the UseSystemLanguage parameter is set to true, the same language is used as for the operating system. If the UseSystemLanguage parameter is to set to false or not defined, then the client uses the regional language for the current user as the default.
The regional language is set at Control Panel > Region and Language > Change the date, time, or number format > Formats tab > Format dropdown .
Specifies the URL where users can reset lost or forgotten passwords.
This argument is optional but recommended.
Note
In cloud-based deployments, you can specify a forgot password URL using the Cisco WebEx Administration Tool. However, the client cannot retrieve that forgot password URL until users sign in.
Applies to Release 11.1(1) onwards.
Specifies whether the Sign me in when Cisco Jabber starts check box is checked when the user installs the client.
true—The Sign me in when Cisco Jabber starts check box is checked when the user installs the client.
false (default)—The Sign me in when Cisco Jabber starts check box is not checked when the user installs the client.
Specifies the unique name of a group configuration file.
You can specify either an unqualified or fully qualified filename as the value. The filename you specify as the value for this argument takes priority over any other configuration file on your TFTP server.
This argument is optional.
You can specify group configuration files in the Cisco Support Field on the CSF device configuration on Cisco Unified Communications Manager.
Controls user sign in to multiple client instances.
By default, users can sign in to multiple instances of Cisco Jabber at the same time. Set one of the following values to change the default behavior:
WBX—Users can sign in to one instance of Cisco Jabber for Windows at a time.
Cisco Jabber for Windows appends the wbxconnect suffix to the user’s JID. Users cannot sign in to any other Cisco Jabber client that uses the wbxconnect suffix.
MUT—Users can sign in to one instance of Cisco Jabber for Windows at a time, but can sign in to other Cisco Jabber clients at the same time.
Each instance of Cisco Jabber for Windows appends the user’s JID with a unique suffix.
Absolute path on the local filesystem
Defines the directory where the client writes log files.
Use quotation marks to escape space characters in the path, as in the following example:
«C:\ my_directory \Log Directory»
The path you specify must not contain Windows invalid characters.
The default value is %USER_PROFILE%\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs
Disables click-to-x functionality with Cisco Jabber.
If you specify this argument during installation, the client does not register as a handler for click-to-x functionality with the operating system. This argument prevents the client from writing to the Microsoft Windows registry during installation.
You must re-install the client and omit this argument to enable click-to-x functionality with the client after installation.
true (default)—The Report a problem menu item is enabled in the Help menu in the client.
false—The Jabber menu item option Report a problem is removed from the Help menu in the client.
If you set the argument to false, users can still manually use the Start Menu > Cisco Jabber directory, or the Program files directory and launch the Problem Report Tool manually. If a user manually creates a PRT, and this parameter value is set to false, then the zip file created from the PRT has no content.
true—PRT files sent by Jabber clients are encrypted.
false (default)—PRT files sent by Jabber clients are not encrypted.
PRT encryption requires a public/private key pair to encrypt and decrypt the Cisco Jabber problem report.
Specifies the name of a certificate with a public key in the Enterprise Trust or Trusted Root Certificate Authorities certificate store. The certificate public key is used to encrypt Jabber Problem reports. You must configure this argument with the ENABLE_PRT_ENCRYPTION argument.
Specifies the client behavior for invalid certificates.
RejectAndNotify—A warning dialog displays and the client doesn’t load.
PromptPerSession—A warning dialog displays and the user can accept or reject the invalid certificate.
For invalid certificates in FIPS mode, this argument is ignored, the client displays a warning message and doesn’t load.
Specifies whether analytics data is gathered. The default value is true.
To improve your experience and product performance, Cisco Jabber may collect and send non-personally identifiable usage and performance data to Cisco. The aggregated data is used by Cisco to understand trends in how Jabber clients are being used and how they are performing.
Full details on what analytics data Cisco Jabber does and does not collect can be found in the Cisco Jabber Supplement to Cisco’s On-Line Privacy Policy at http://www.cisco.com/web/siteassets/legal/privacy_02Jun10.html.
Specifies whether the Location feature is enabled and whether users are notified when new locations are detected.
ENABLED(default)—Location feature is turned on. Users are notified when new locations are detected.
DISABLED—Location feature is turned off. Users are not notified when new locations are detected.
ENABLEDNOPROMPT—Location feature is turned on. Users are not notified when new locations are detected.
Specifies whether the Cisco Jabber is in FIPS mode.
Cisco Jabber can be in FIPS mode on an operating system that is not FIPS enabled. Only connections with non-Window’s APIs are in FIPS mode.
If you don’t include this setting, Cisco Jabber will determine the FIPS mode from the operating system.
SSO Arguments
This section describes the command line arguments you can use to deploy Cisco Jabber for Windows with single sign on (SSO) capabilities.
Cloud-Based SSO Arguments
The arguments in the following table apply to cloud-based deployments only:
Specifies the domain name for the Cisco WebEx Org that contains the URL for the SSO service.
Cisco Jabber for Windows uses this argument to retrieve the URL of the SSO service from the Org. When Cisco Jabber for Windows gets the SSO service URL, it can request login tokens to authenticate with Cisco WebEx Messenger.
You specify the URL for the SSO service as the value of the Customer SSO Service Login URL in the Cisco WebEx Administration Tool.
LCID for Languages
The following table lists the Locale Identifier (LCID) or Language Identifier (LangID) for the languages that the Cisco Jabber clients support.
Cisco Jabber for Windows
Cisco Jabber for Mac
Cisco Jabber for Android, Cisco Jabber for iPhone and iPad
Arabic — Saudi Arabia
Chinese (Simplified) — China
Chinese (Traditional) — Taiwan
Czech — Czech Republic
English — United States
Spanish — Spain (Modern Sort)
Related References Example Installation Commands Command Line Arguments
Run the MSI Manually
You can run the installation program manually to install a single instance of the client and specify connection settings in the Advanced settings window.
Procedure
Step 1
Launch CiscoJabberSetup.msi .
The installation program opens a window to guide you through the installation process.
Step 2
Follow the steps to complete the installation process.
Step 3
Start Cisco Jabber for Windows .
Step 4
Select Manual setup and sign in .
The Advanced settings window opens.
Step 5
Specify values for the connection settings properties.
Step 6
Select Save .
Create a Custom Installer
You can transform the default installation package to create a custom installer.
Note
You use Microsoft Orca to create custom installers. Microsoft Orca is available as part of the Microsoft Windows SDK for Windows 7 and .NET Framework 4.
Download and install Microsoft Windows SDK for Windows 7 and .NET Framework 4 from the Microsoft website.
Procedure
Command or Action
Purpose
Step 1
Get the Default Transform File
You must have the default transform file to modify the installation package with Microsoft Orca.
Transform files contain installation properties that you apply to the installer.
Apply a transform file to customize the installer.
Related Information Microsoft Windows SDK for Windows 7 and .NET Framework 4
Get the Default Transform File
You must have the default transform file to modify the installation package with Microsoft Orca.
Procedure
Step 1
Download the Cisco Jabber administration package from Software Download page.
Step 2
Copy CiscoJabberProperties.msi from the Cisco Jabber administration package to your file system.
What to Do Next
Related Information Software Downloads
Create Custom Transform Files
To create a custom installer, you use a transform file. Transform files contain installation properties that you apply to the installer.
The default transform file lets you specify values for properties when you transform the installer. You should use the default transform file if you are creating one custom installer.
You can optionally create custom transform files. You specify values for properties in a custom transform file and then apply it to the installer.
Create custom transform files if you require more than one custom installer with different property values. For example, create one transform file that sets the default language to French and another transform file that sets the default language to Spanish. You can then apply each transform file to the installation package separately. The result is that you create two installers, one for each language.
Before You Begin
Procedure
Step 1
Start Microsoft Orca.
Step 2
Open CiscoJabberSetup.msi and then apply CiscoJabberProperties.msi .
Step 3
Specify values for the appropriate installer properties.
Step 4
Generate and save the transform file.
Select Transform > Generate Transform .
Select a location on your file system to save the transform file.
Specify a name for the transform file and select Save .
The transform file you created is saved as file_name .mst . You can apply this transform file to modify the properties of CiscoJabberSetup.msi .
What to Do Next
Transform the Installer
Apply a transform file to customize the installer.
Note
Applying transform files will alter the digital signature of CiscoJabberSetup.msi . Attempts to modify or rename CiscoJabberSetup.msi will remove the signature entirely.
Before You Begin
Procedure
Step 1
Start Microsoft Orca.
Step 2
Open CiscoJabberSetup.msi in Microsoft Orca.
Select File > Open .
Browse to the location of CiscoJabberSetup.msi on your file system.
Select CiscoJabberSetup.msi and then select Open .
The installation package opens in Microsoft Orca. The list of tables for the installer opens in the Tables pane.
Step 3
Remove all language codes except for 1033 (English). Restriction:
You must remove all language codes from the custom installer except for 1033 (English).
Microsoft Orca does not retain any language files in custom installers except for the default, which is 1033. If you do not remove all language codes from the custom installer, you cannot run the installer on any operating system where the language is other than English.
Select View > Summary Information .
The Edit Summary Information window displays.
Locate the Languages field.
Delete all language codes except for 1033.
Select OK .
English is set as the language for your custom installer.
Step 4
Apply a transform file.
Select Transform > Apply Transform .
Browse to the location of the transform file on your file system.
Select the transform file and then select Open .
Step 5
Select Property from the list of tables in the Tables pane.
The list of properties for CiscoJabberSetup.msi opens in the right panel of the application window.
Step 6
Specify values for the properties you require.
Tip
Values are case sensitive. Ensure the value you enter matches the value in this document.
Set the value of the CLEAR property to 1 to override any existing bootstrap file from previous installations. If you do not override existing bootstrap files, the values you set in the custom installer do not take effect.
