The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can arrange and organize your contacts by name or status.
Cisco Jabber lets you add contacts from chat applications such as Google Talk or Microsoft Lync.
Your system administrator must enable this feature. If you cannot add external contacts, ask your system administrator for help.
You can create contact lists in XML format and then import them into Cisco Jabber.
Cisco Jabber imports the contacts from the definitions file. The contacts are available in your contact list.
<?xml version="1.0" encoding="utf-8"?> <buddylist> <group> <gname>Group Name</gname> <user> <uname>IM Address</uname> <fname>Display Name</fname> </user> </group> </buddylist>
Element | Description |
---|---|
<?xml version="1.0" encoding="utf-8"?> | XML declaration.
|
buddylist | Root element of the contact list definition. |
group | Parent element of a contact group.
One group can contain multiple users. There is no limit to the number of users a group can contain. There is also no limit to the number of groups you can include in a contact list definitions file. However, your server sets a restriction to the number of contacts that you can add to Cisco Jabber. You must ensure you do not exceed that limit in your contact list definitions file. |
gname | Specifies the name of the group. |
user | Parent element that holds details for a single user. |
uname | Specifies the instant messaging (IM) address of a user. |
fname | Specifies the name that displays in the client user interface. |
<?xml version="1.0" encoding="utf-8"?> <buddylist> <group> <gname>Sales</gname> <user> <uname>amckenzi@example.com</uname> <fname>Adam McKenzie</fname> </user> <user> <uname>aperez@example.com</uname> <fname>Anita Perez</fname> </user> </group> <group> <gname>Marketing</gname> <user> <uname>nfox@example.com</uname> <fname>Nancy Fox</fname> </user> </group> </buddylist>
<?xml version="1.0" encoding="utf-8"?> <buddylist> <group> <gname>Sales</gname> <user> <uname>amckenzi@example.com</uname> <fname>Adam McKenzie</fname> </user> <user> <uname>aperez@example.com</uname> <fname>Anita Perez</fname> </user> </group> <group> <gname>Marketing</gname> <user> <uname>nfox@example.com</uname> <fname>Nancy Fox</fname> </user> </group> </buddylist>