Jabber Edu Implementations

From XMPP WIKI
Jump to navigation Jump to search

This page has implementation details of higher education instant messaging services. The intent is to aid troubleshooting of federation, and to share details on deployment best practices.
More information about the federated higher education instant messaging services can be found on the Jabber Edu Federation page.

Name Server information User population Clients Additional server features Additional information

Carnegie Mellon University

  • Server: Openfire
  • Cluster: No
  • Authentication: GSSAPI, PLAIN (against K5 on the backend)
  • Domains: 1
  • Users: handful
  • Population: staff mostly
  • Desktop clients: nothing official, Adium/Pidgin work well
  • Web client: not yet
  • Multi-user chat

Gustavus Adolphus College

  • Server: Openfire
  • Cluster: No
  • Authentication: LDAP
  • Domains: 1
  • Users: any of our 5000 ldap accounts could use it.
  • Population: students, faculty, staff, ( about a dozen active users )
  • Multi-user chat
  • Voip integration with asterisk
  • HTTP presence service
  • IM Gateways - AOL, ICQ, IRC, MSN, Yahoo

New York University

  • Server: Openfire
  • Cluster: No
  • Authentication: LDAP
  • Domains: 1
  • Users: ~250
  • Population: IT staff
  • Desktop clients: Adium, Pidgin, and iChat
  • Web client: no
  • Multi-user chat

University of Wisconsin-Madison

  • Server: ejabberd
  • Cluster: Yes
  • Authentication: LDAP
  • Domains: 16
  • Users: 750 active (65,000 eligible)
  • Population: students, faculty, staff, organizations, K-12's
  • Desktop clients: Psi is recommended
  • Web client: not yet
  • Multi-user chat
  • Vcard user directory (not integrated with campus directory)