Instant Messaging (IM) FAQs
- Does ETS offer instant messaging?
- What is XMPP
- What support does ETS provide for instant messaging?
- Who can use the service?
- How can I create an account?
- What clients are supported?
- Can I use Microsoft Office Communicator?
- How can I communicate with users on AIM or googletalk?
- What settings do I use in my client?
- Why do I see security warnings?
- Why doesn't voice chat work?
- Why doesn't video chat work?
- Why doesn't TLS work?
- Why doesn't file transfer work?
ETS offers an Instant Messaging (IM) server at jive.state.ak.us. The service authenticates against the enterprise directory and is accessible with an IM client which supports XMPP.
XMPP is an IETF open standard for real-time communication. It was once known as the jabber protocol. See xmpp.org for more detailed information.
ETS runs and monitors the server. ETS will answer questions about the service and provide access to configuration notes for IM clients. The users of the service are assumed to be able to configure their own IM client software. Jive does not receive after-hours attention.
Jive intended to facilitate day-to-day communication among state employees and is not intended to support mission-critical or life-and-safety systems.
Anyone with an account in the enterprise directory who is inside the State of Alaska WAN or has VPN access may use the service.
You do not need to create (or register) an account. Everyone with enterprise directory access already has an account. Simply authenticate to use it.
Most clients which support XMPP can be used. Some clients used successfully are:
See Confluence for more details on these clients. Microsoft's IM client will not work with Jive.
This client will not work with Jive. The Microsoft IM client uses SIP/SIMPLE protocol. Microsoft has chosen not to support the XMPP protocol.
Jive is for use on the State of Alaska WAN. It does not permit connections with other instant messaging systems.
All clients will ask for the following information in some form. Exactly the client asks for it will vary.
|Common client settings||Possible values|
|server, domain, or host||jive.state.ak.us|
xmpp with "old" ssl
|username, uid, or user||Your email username|
Jive communication is protected with a self-signed X.509 certificate. Some clients accept it quietly. Other clients protest mildly. Other clients may refuse to accept it.
For those who which to verify the certificate (if you can do that with content provided via HTTP), the SHA1 fingerprint is
The purpose of the certificate is to provide encryption. This self-signed certificate functions perfectly for this purpose.
There is no support for voice. Jive provides text-chat services.
There is no support for video. Jive provides text-chat services.
There is no support for TSL. All communication with Jive is encrypted via SSL on port 5223.
Jive provides text-chat services. Jive does not provide any file transfer facility. Depending on your clients, you may be able to do peer-to-peer file transfers but it is neither supported nor encouraged.