UNOC provides a public Jabber server at jabber.unoc.net. We
require digest authentication and TLS for maximum security (port 5222).
For legacy clients, SSL on port 5223 is available. Of course, IPv6
connections are always welcome at the same server address as above :-)
Contact
The administrator of this server is amir@jabber.unoc.net
 .
If you are experiencing problems with our service, or would like to contact the administrator,
please email jabber AT unoc.net.
News
2008.05.01 16:08 PDT: IPv6 connectivity returns.
2008.01.03 23:02 PST: Server either crashed or was rebooted by the
NOC (reason unknown/not given). More investigation required. Sorry for the inconvenience! We are planning to move the service to a more stable machine, pending some administrative issues.
2007.11.29 16:25 PST: Another "mysterious" Openfire crash.
2007.08.18 12:45 PDT: Upgraded Openfire to latest version, and restarted server. Please
report any instabilities... Again, we apologize for the downtime!
2007.07.21 20:05 PDT: Jabber server has been shut down due to scalability issues related
to Openfire. Fix expected next week. Sorry for the inconvenience!
2007.03.31 22:00 PDT: Upgraded server to Openfire 3.2.4 and added experimental Yahoo!
gateway. Took the Web Jabber client offline.
2007.02.27 15:45 PDT: AIM & MSN transports should be running now. Apologies for the
minor outage.
2006.10.29 00:20 PDT: Upgraded to Wildfire 3.1.0. Upgraded MSN transport.
Upgraded AIM transport.
2006.08.15 16:00 PDT: Upgraded MSN transport. Thanks for reporting!
2006.08.15 09:15 PDT: Jabber server restarted after mysteriously
crashing. Thanks for reporting!
2006.07.05 13:55 PDT: Apparently the Jabber server died, with no sign
of the VM left! Nothing in the error logs. Maybe Wildfire can't stay up for
more than 4 months? It's been restarted... sorry for the inconvenience!
2006.03.09 21:40 PDT: Upgraded to Jive Wildfire 2.5.1. Sadly, the Java
setup on this machine does not handle IPv6. I'm guessing it's a problem with
Java's way of detecting whether a host is dual-stacked or not. It's not able
to bind to an IPv6 socket. Will need to investigate this further...
2006.03.08 20:10 PDT: Brought the AIM/ICQ transport back online. The new
version of PyAIM-t has some nice features, and hopefully with the upgrade of the
Jabber server (sometime soon), we will have a stable setup!
2006.03.07 22:30 PDT: Added Web Jabber service over SSL. The interface is
much better than what we had before, plus, it doesn't require anything special on
the client-side. Comments welcome.
2006.02.21 12:25 PDT: I was casually running w and noticed:
14:20:11 up 309 days, 4:49, 1 user, load average: 6.65, 6.61, 6.63
As usual, the jabber server must be the culprit. I killed it and reverted back to
Wildfire 2.4.4. I've never heard of a bug-create release! Apparently there is a bug
in the SASL code that is causing the server to go into an infinite loop. Fix
expected in the next release.
2006.02.19 13:30 PDT: Upgraded server software to Jive Wildfire 2.5.0, and at the
same time, got rid of the SOCKS5 Bytestream Proxy component, as it is now included in
Wildfire's core functionality. As they claim some memory leaks have been fixed, let's
hope we don't have to restart the server every 2 weeks :)
2005.12.27 16:00 PDT: Server has been upgraded to Jive Wildfire. 99% of the user
accounts were migrated to the new installation. If you are unable to connect, please email
us and we will migrate your account manually. You may need to reregister with your legacy
gateways. Do this by removing the transport, and then reregistering with it. The MSN
transport is back, and an ICQ transport has been added.
2005.11.18 01:30 PDT: Misconfigured authentication credentials on the MySQL backend
caused the Jabber server to core dump due to inability to reconnect to the database server,
yesterday.
In other news, we are looking to switch to Jive Messenger as the new server platform, but its
lack of IPv6 support is a problem, so this is being postponed.
2005.10.13 00:10 PST: An upgrade required a restart of the AIM transport.
2005.10.12 23:30 PST: An upgrade required a restart of the MSN transport.
2005.02.17 22:00 PST: Although users may not notice this, the MySQL
backend is being swamped by over a hundred queries per second:
Uptime: 6 days 13 hours 32 min 16 sec
Threads: 10 Questions: 56736319 Slow queries: 0 Opens: 70
Flush tables: 1 Open tables: 45 Queries per second avg: 100.040
After some investigation it was found that the AIM Transport is causing the
havoc. It is being investigated.
- Update (22:10 PST): The AIM transport has been restarted without
ICQ support.
2005.02.15 23:30 PST: jabber.unoc.net is back online. IPv6 access,
as well as the Yahoo! Transport, are down. Please contact amir@jabber.unoc.net
if you have any problems.
2005.02.11 15:00 PST: jabber.unoc.net is down until further notice.
We apologize for any inconvenience caused during this outage. This was
unexpected, and was not intended to mirror jabber.org's downtime announcement.
jabber.unoc.net should be up by next week.
2004.12.07 22:05 PST: Unfortunately, the upgrade did not go as
planned. Service has been restored to the old server.
2004.12.07 21:20 PST: jabber.unoc.net is down for maintenance.
Upgrading jabberd among other things. We apologize for any inconvenience
this causes. We hope to be back by 10pm!
Services:
- Groupchat
- Jabber User Directory
- AIM / ICQ Transport (with chatroom support)
- MSN Messenger Transport (with chatroom support)
Problems connecting?
Make sure you are using a client that supports digest passwords, see the
Jabber clients page
for a list of clients.
Please contact JID support@jabber.unoc.net if you have any questions or
concerns.
|
© 2003-2008 United Network Operations Co. All Rights Reserved.
|
