On Wed Nov 12 06:57:03 2008, ashiraz wrote:
> Oh that explains what you meant by publicly accessible. MY jabber
> server has to be publicly accessible! It makes sense. Sorry I was in
> haste and was not thinking clearly. So, my machine has to have a  
> proper
> static ip address and a domain name that links up to that ip  
> address.
> My "home" machine that is running ejabberd has an IP address but I  
> dont
> think its accessible from the outside. I have an IP address which I
> obtain from connecting via ethernet. I can't try connectig  
> with/joining
> the chatroom on the remote server with just my IP address , can I?
> 
> 
No, but there's no real advantage to running your own server purely  
to connect to the IETF's chatrooms, anyway, unless that server is  
somehow special (ie, running additional components or software).


> That is why I was trying gtalk but that would entail using the
> encrypted channel thing.

Out of curiosity, why do you need your own client? Are you trying to  
provide some new infrastructure to the IETF meeting? If so, I might  
be able to help you, and moreover, you might obtain a local account  
on the server for that if you ask the right people.

If you're just trying to participate in them, you may as well just  
use a stock client and your gmail account.

Dave.
-- 
Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED]
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [EMAIL PROTECTED]
_______________________________________________

Reply via email to