Ports Required

Openfire Plugins Kraken - IM Gateway
1

Hi,

Apologies if I’‘m being overly dense… but I’'ll ask anyway!

What ports do I need to open on the Wildifre server machine (inbound and outbound) to use the different transports? e.g. when I try to connect to the MSN network I get…

In Spark from the MSN Transport user : Unknown error from MSN: java.net.NoRouteToHostException: No route to host: no further information

In Wildfire with debugging on : 2006.10.04 21:22:25 Logging in to MSN gateway. and 2006.10.04 21:22:48 Unable to handle iq request:vcard-temp

so I’‘m guessing its a port blocked somewhere or a wildfire server config issue??? Tried searching around and can’'t find a ports required list for the different transports.

Server to server is enabled on 5269 (presume thats what it uses) and I’'ve registered my user to the service/username in the gateway registrations.

Thanks in advance for a probably dense question…

Ian

2

Hi,

What ports do I need to open on the Wildifre server machine (inbound and outbound) to use the different transports? e.g. when I try to connect to the MSN network I get…

There is no inbound from those legacy networks. Outbound:

MSN - 1863

Yahoo! - 5050

IRC - 7000

ICQ/AIM - 5190

In Spark from the MSN Transport user : Unknown error from MSN: java.net.NoRouteToHostException: No route to host: no further information

In Wildfire with debugging on : 2006.10.04 21:22:25 Logging in to MSN gateway. and 2006.10.04 21:22:48 Unable to handle iq request:vcard-temp

Connection wise, there isn’‘t much on Spark side, but mostly on Wildfire side because Wildfire is the one will connect to MSN, etc. However, I’'m not sure if I understand what you describe above. Sorry.

so I’‘m guessing its a port blocked somewhere or a wildfire server config issue??? Tried searching around and can’'t find a ports required list for the different transports.

If you could resolve an Internet domain name from the server that runs Wildfire, e.g. if you get an IP when you do nslookup messenger.hotmail.com, then you’'re all set. Otherwise you probably need to check the DNS, default gateway or firewall (not so common for outbound).

Server to server is enabled on 5269 (presume thats what it uses) and I’'ve registered my user to the service/username in the gateway registrations.

If transports are the only concern here, then port 5269 is not used because there is no s2s involved.

Hope that sheds some lights.

3

thanks

top man.

just the lighbulb i needed.

Thanks

Ian

4

Perhaps I should put this in the README. =) (the required ports list)

5

Yep! Otherwise, easy points to get

6

be a top idea. or put it in the connect error message as a hit after ‘‘no route to host : port xxxx’’?

7

GATE-84 Wanted to put a reminder to myself to do this. =)

As for the route to host message, maybe, depends on how much control I have over that message. =)

Message was edited by: jadestorm