Tag Archives: MSN

Changes in transport services

Some weeks ago we removed the MSN transport from our list of transport services. Microsoft stopped supporting MSN, so the transport did not make sense anymore.

We installed two new transports: Novell Groupwise and SIPE (for Microsoft OCS/LCS Messaging). We did not test these transports as we do not have access to Novell or Microsoft instant messaging chat servers. If you test these transports please give us a short feedback.

Server Specs

The Hot-Chilli Instant Messaging service is a node on the open Jabber network, based on XMPP, the open standard for instant messaging. The IM service is registered on the xmpp.org website and thus fulfills the requirements to be listed.

The usage of our IM services is completely free of charge (exept if you like to run your own domains on our server).

Server hardware and server location

  • Intel Core i7-6700 Quad-Core Skylake
  • 32 GB DDR4 RAM
  • 2 x 4 TB SATA 6 Gb/s 7200 rpm HDDs (Software-RAID 1)
  • 1 Gbit Internet connection
  • Debian amd64

Location: Germany
Latitude/longitude: 49.09 N, 12.48 E

Domains

The following public XMPP domains are hosted here:

  • jabber.hot-chilli.net
    (all transports and services which we offer run on this domain)
    SSL Fingerprint: 15:64:B6:9C:60:E3:B2:E3:55:95:C5:A4:24:27:AA:E3:9F:F1:C7:E7
  • jabber.hot-chilli.eu
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: 00:E8:BA:99:F2:0A:F6:F5:1A:30:F2:36:8D:B8:AE:65:51:7E:BE:40
  • hot-chilli.net
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: 61:9B:EB:30:09:BE:C0:DE:5A:7F:9D:EB:B0:2D:51:2B:DF:71:21:33
  • hot-chilli.eu
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: 43:96:32:E4:F6:4E:0F:78:1A:B3:C2:E0:84:43:71:77:15:36:AC:23
  • im.hot-chilli.net
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: DC:AE:41:5D:1D:99:CA:A7:DC:99:34:49:D7:0D:1B:C6:36:56:46:DD
  • im.hot-chilli.eu
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: 0C:20:F2:3F:B3:82:56:03:F3:C2:90:A4:C8:28:9E:6F:BC:DB:DF:02
  • jabb3r.de
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: CA:28:3A:21:70:E3:FE:D2:EF:A3:C6:E7:D2:88:A1:9E:69:A2:7E:E8
  • jabb3r.org
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: DB:3A:1E:6D:89:DD:8E:8F:09:2B:E2:93:8E:FC:60:86:BA:3D:3E:FE
  • jabber-hosting.de
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: 02:71:8D:DD:F6:30:4C:6A:9C:32:40:49:8D:34:29:9F:58:9E:80:A0
  • xmpp-hosting.de
    (full access to the transports and services of jabber.hot-chilli.net)
    SSL Fingerprint: A2:FA:AF:EE:C7:9C:18:32:20:90:64:22:7B:C3:BA:E6:96:75:41:B4

Own Jabber domains

You can host your own domain (with admin access and full access to the transports and services of jabber.hot-chilli.net) on our Jabber server. This is even possible without moving your domain from your current provider to us, you just need to setup three DNS entries to point Jabber services for your domain to our server. See here for more information.

Connections

“normal” client connections (STARTTLS/TLS)

  • jabber.hot-chilli.net:5222 (IPv4 and IPv6 connections)
  • server.jabber.hot-chilli.net:80 (for users behind restrictive firewalls, IPv4 connections only)
  • c2aaokzwkwkct543.onion:5222 (connections via Tor)

SSL client connections

  • jabber.hot-chilli.net:5223 (IPv4 and IPv6 connections)
  • server.jabber.hot-chilli.net:443 (for users behind restrictive firewalls, IPv4 connections only)
  • c2aaokzwkwkct543.onion:5223 (connections via Tor)

BOSH connections

  • https://jabber.hot-chilli.net/http-bind (IPv4 and IPv6 connections)
  • https://jabber.hot-chilli.net:5281/http-bind (IPv4 and IPv6 connections)

WebSocket connections

  • wss://jabber.hot-chilli.net:443/xmpp-websocket (IPv4 and IPv6 connections)
  • wss://jabber.hot-chilli.net:5281/xmpp-websocket (IPv4 and IPv6 connections)

Proxy65 (File Transfer Proxy)

  • proxy.jabber.hot-chilli.net:7777

STUN/TURN

  • stun.hot-chilli.net

Transports, Gateways and Features

  • AIM Transport
  • Gadu-Gadu Transport
  • ICQ Transport
  • MUC (Multi-User Chat)
  • Proxy65 (File Transfer Proxy)
  • Pubsub / PEP (Publish-Subscribe / Personal Eventing via Pubsub)
  • SIPE Transport
  • Web Presence
  • XMPP Transport (Jabber-to-Jabber, J2J)
  • Yahoo! Transport

Transports migrated to Spectrum

ICQ, MSN, AIM, Yahoo! and J2J (XMPP) transports were migrated to Spectrum transports yesterday evening and night.

After accidentally stumbled upon Spectrum (thanks to Flo!) I started the migration right away. The old PyXXXt transports were a huge pain long enough (PyMSNt for example created 800GB of traffic each month, alltogether the PyXXXt transports used 90% CPU when running a certain amount of time – which is the reason why we restart the Jabber related services every night) so I was very happy to see a young and well looked after project which really works a lot better. I’m quite enthusiastic at the moment. ;-)

All users and settings were migrated without problems, so maybe you haven’t even noticed that something has changed on the server.

The Gadu-Gadu (GG) Transport will also migrated to Spectrum, but I haven’t managed the migration of the user data yet.

ICQ Transport users please note, that charset was set to ISO-8859-15 – which should be a good choice for European users (German umlauts, other special characters etc). If you experience problems, please change the charset (to utf8 for example) of your ICQ Transport account by clicking on “Register” in the context menu of icq.jabber.hot-chilli.net. You can find this in the Jabber service discovery.

AIM Transport users please note, that the new AIM transport service seems to be a little unstable right now and has to be restarted from time to time. I will take a closer look in the next days.

J2J (XMPP) Transport users please note, that it was not possible to migrate the remote roster data to the new transport service. But as I noticed the remote roster is downloaded during the first connect.

Until now I cannot say if the nightly restart of the Jabber services at 3am CET/CEST is still necessary. The next days or weeks will tell. Stay tuned.

If you should experience problems with the new transport services please contact us in support@conference.jabber.hot-chilli.net.