How do I configure my Jabber client?
Gives information on Jabber client configuration
Jabber clients are available for download for Windows, Mac OS X and Linux, as well as mobile operating systems. Popular desktop clients include Spark and Pidgin (both are free and available for Windows, Mac OS X, and Linux), and MirandaIM (free, Windows-only).
Configuration
| Setting | Value |
|---|---|
| Server name | im.uic.edu |
| Protocol | XMPP |
| Port | 5222 |
| Username | NetID@im.uic.edu |
| Password | ACCC common password |
| Resource Name | unique name for this location (for example "Work", "Home", "Laptop") |
| Resource Priority | unique number for the priority of this location (higher number = higher priority) |
To add contacts, use your client's interface to add NetID@im.uic.edu where NetID is the UIC NetID of the person you want to add to your contact list. If that person uses Jabber, they will receive a request to authorize you. Once authorized, you will see their status in your contact list.
Using Jabber from multiple locations or devices
If you want to use Jabber from two (or more) locations simultaneously (which means if you have it open on two or more devices), there are two things you want to keep in mind:
- Name your resource - give each client a different resource name, for example: work, home, laptop, mobile
- Set your resource priority - once you've named each resource, set a different priority for each client (note that the higher the number, the higher the priority).
Now, say that you're logged in from two locations:
- resource: work
priority: 2 - resource: home
priority: 1
If you set it up this way, by default, messages will be routed to your work location. If you are out and about campus and log in from your laptop (resource: laptop priority: 3), new messages will go to your laptop. You can also force messages to go to a particular resource by sending messages to NetID@im.uic.edu/resourcename.
If you set the resource name to the same value on two different Jabber clients, you will experience problems logging in. If you set the priority to the same value on two clients, the most recent connection wins.