headers
Bill Clementson | 1 Oct 2006 02:23
Picon

Using ejabberd with iChat

Hi all,

I've downloaded the latest release of ejabberd (1.1.2) and installed
it with the Mac OS X installer. I can connect to the admin page using
bc <at> bc.local after I start the server, and I can connect to the
ejabberd server when I set up an account for bc <at> bc.local using the Psi
jabber client; however, I can't seem to connect to it when I'm using
iChat. I can connect to other (remote) Jabber servers using iChat
(including another ejabberd server); however, I can not connect to my
local ejabberd server.

Does anyone know why iChat isn't able to connect to a local instance
of ejabberd? I've tried various combinations of server settings in the
iChat account setup preferences; however, nothing I do seems to work.

Any help or suggestions would be appreciated!

Thanks,
Bill Clementson
Permalink | Reply | 6 comments |
headers
Andre Pang | 1 Oct 2006 08:10
Picon

Re: Using ejabberd with iChat

On 01/10/2006, at 10:23 AM, Bill Clementson wrote:

> I've downloaded the latest release of ejabberd (1.1.2) and installed
> it with the Mac OS X installer. I can connect to the admin page using
> bc <at> bc.local after I start the server, and I can connect to the
> ejabberd server when I set up an account for bc <at> bc.local using the Psi
> jabber client; however, I can't seem to connect to it when I'm using
> iChat. I can connect to other (remote) Jabber servers using iChat
> (including another ejabberd server); however, I can not connect to my
> local ejabberd server.

At a guess, ejabberd may not be binding to your localhost address  
(127.0.0.1), and may instead only be binding to the "real" network  
addresses on your machine.  You may want to double-check this, using  
netstat or a similar tool.  Perhaps try using the IP address of a  
network adapter in iChat.

--

-- 
% Andre Pang : trust.in.love.to.save  <http://www.algorithm.com.au/>
Permalink | Reply | 5 comments |
headers
Michael Grigutsch | 1 Oct 2006 08:14

Problems with Centericq and ejabberd 1.1.2

Hi!

If you try to connect to ejabberd 1.1.2 using Centericq you'll only get an
error 503.
That is an old and known bug of Centericq
(http://article.gmane.org/gmane.network.centericq/4114).
That bug doesn't appear with ejabberd before, as until 1.1.1 ejabberd sends
an error 501 - so Centericq connects.
This has been changed, because the specs tell, that in this case 503 should
be used. (Which is IMHO debatable, because 501 is more natural in this case.
503 means (for me) that the service works but is unavailable now.)
There is a patch for Centericq
(http://www.dtek.chalmers.se/%7Ehenoch/centericq.patch).
If you want to change the behavior of ejabberd instead, you have to
change line 558 in ejabberd_sm from ERR_SERVICE_UNAVAILABLE to
ERR_FEATURE_NOT_IMPLEMENTED and rebuild it.

/MiGri
Permalink | Reply | 0 comments |
headers
Bill Clementson | 1 Oct 2006 20:33
Picon

Re: Using ejabberd with iChat

> > I've downloaded the latest release of ejabberd (1.1.2) and installed
> > it with the Mac OS X installer. I can connect to the admin page using
> > bc <at> bc.local after I start the server, and I can connect to the
> > ejabberd server when I set up an account for bc <at> bc.local using the Psi
> > jabber client; however, I can't seem to connect to it when I'm using
> > iChat. I can connect to other (remote) Jabber servers using iChat
> > (including another ejabberd server); however, I can not connect to my
> > local ejabberd server.
>
> At a guess, ejabberd may not be binding to your localhost address
> (127.0.0.1), and may instead only be binding to the "real" network
> addresses on your machine.  You may want to double-check this, using
> netstat or a similar tool.  Perhaps try using the IP address of a
> network adapter in iChat.

I had a look with "netstat -r" (not sure if this is the right switch
or not) and it showed the following:
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.0.1        UGSc       13       34    en0
127                localhost          UCS         0        0    lo0
localhost          localhost          UH         19   188189    lo0
169.254            link#4             UCS         0        0    en0
192.168.0          link#4             UCS         3        0    en0
192.168.0.1        0:9:5b:f8:da:6d    UHLW       11        0    en0   1123
192.168.0.2        0:d:93:c8:d8:12    UHLW        0        0    en0    886
192.168.0.3        localhost          UHS         0      899    lo0
192.168.0.255      ff:ff:ff:ff:ff:ff  UHLWb       0        6    en0
(Continue reading)

Permalink | Reply | 4 comments |
headers
Tony Finch | 1 Oct 2006 21:01
Picon
Favicon

Re: Using ejabberd with iChat

On Sun, 1 Oct 2006, Bill Clementson wrote:

> > At a guess, ejabberd may not be binding to your localhost address
> > (127.0.0.1), and may instead only be binding to the "real" network
> > addresses on your machine.
>
> I had a look with "netstat -r" (not sure if this is the right switch
> or not) and it showed the following:

Use netstat -a | grep LISTEN to check for listening daemons.

Tony.
--

-- 
f.a.n.finch  <dot <at> dotat.at>  http://dotat.at/
FORTIES CROMARTY FORTH: SOUTHERLY 6 TO GALE 8, DECREASING 5 OR 6 LATER. RAIN
OR SHOWERS. MODERATE OR GOOD.
Permalink | Reply | 3 comments |
headers
Bill Clementson | 1 Oct 2006 21:15
Picon

Re: Using ejabberd with iChat

> > > At a guess, ejabberd may not be binding to your localhost address
> > > (127.0.0.1), and may instead only be binding to the "real" network
> > > addresses on your machine.
> >
> > I had a look with "netstat -r" (not sure if this is the right switch
> > or not) and it showed the following:
>
> Use netstat -a | grep LISTEN to check for listening daemons.

Ok, I did the following:
/Applications/ejabberd-1.1.2/bin $ start
/Applications/ejabberd-1.1.2/bin $ netstat -a | grep LISTEN
tcp4       0      0  *.5298                 *.*                    LISTEN
tcp4       0      0  *.4369                 *.*                    LISTEN
tcp4       0      0  localhost.ipp          *.*                    LISTEN
tcp4       0      0  localhost.netinfo-loca *.*                    LISTEN

I'm not sure whether this is telling me anything though (in the
context of my problem with getting iChat to connect to my local
ejabberd server); although this may be due to my lack of experience
with netstat.

- Bill
Permalink | Reply | 2 comments |
headers
Tony Finch | 1 Oct 2006 21:18
Picon
Favicon

Re: Using ejabberd with iChat

On Sun, 1 Oct 2006, Bill Clementson wrote:

> tcp4       0      0  *.5298                 *.*                    LISTEN

That's a jabber port, and the * indicates that the listener is bound to
all IP addresses.

Tony.
--

-- 
f.a.n.finch  <dot <at> dotat.at>  http://dotat.at/
FORTIES CROMARTY FORTH: SOUTHERLY 6 TO GALE 8, DECREASING 5 OR 6 LATER. RAIN
OR SHOWERS. MODERATE OR GOOD.
Permalink | Reply | 1 comment |
headers
Bill Clementson | 1 Oct 2006 21:57
Picon

Re: Using ejabberd with iChat

> > tcp4       0      0  *.5298                 *.*                    LISTEN
>
> That's a jabber port, and the * indicates that the listener is bound to
> all IP addresses.

But, does it provide any clues as to why iChat won't connect to my
ejabberd server? I've tried setting the server to:

bc.local
127.0.0.1
localhost

but it still won't connect. Actually, the connection behaviour is a
bit different depending on the server name I use. For 127.0.0.1 and
localhost, I get an immediate message back in iChat that says "Could
not connect to Jabber. Could not connect to host localhost" (or
127.0.0.1). However, if I change the server name to bc.local (my
machine's name is "bc"), I get a message "Connecting..." but, after
about a minute or two, it comes back with the same error message.

I initially installed ejabberd with bc.local as the server name. I
have now uninstalled ejabberd and re-installed it with localhost as
the server name. However, I still get the same behaviour (e.g. -
immediate error message for 127.0.0.1 and localhost but a delayed
error message for bc.local).

With both the bc.local install and the localhost install, Psi was able
to connect to the server without any problems.

Any ideas?
(Continue reading)

Permalink | Reply | 0 comments |
headers
J K | 2 Oct 2006 08:19
Picon
Favicon

ejabberd sip gateway


Hi,

Is it possible to add SIP gateway to ejabberd?

I am asking this because I need to integrate SIP messaging with MSN.
For testing I have set up ejabberd server and added MSN gateway to
it. I used Psi JABBER client to try out JABBER to MSN messaging. It
works. Now I need to use a SIP client to connect with MSN. If you
are aware of any better solution for integrating SIP with MSN then
also please send information.

Best regards,
Jarno

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Permalink | Reply | 2 comments |
headers
Rodney G. McDuff | 2 Oct 2006 08:31
Picon
Picon
Gravatar

Re: ejabberd sip gateway

OpenSER has a SIP/Jabber gateway module
<http://www.openser.org/docs/modules/1.1.x/jabber.html>

J K wrote:
>
> Hi,
>
> Is it possible to add SIP gateway to ejabberd?
>
> I am asking this because I need to integrate SIP messaging with MSN.
> For testing I have set up ejabberd server and added MSN gateway to
> it. I used Psi JABBER client to try out JABBER to MSN messaging. It
> works. Now I need to use a SIP client to connect with MSN. If you
> are aware of any better solution for integrating SIP with MSN then
> also please send information.
>
>
> Best regards,
> Jarno
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's
> FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
> _______________________________________________
> ejabberd mailing list
> ejabberd <at> jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane