ejabberd

I read about the doc https://docs.ejabberd.im/admin/api/ And I wonder how can I access those API via HTTP. I tried to access but it always 404. In your ejabberd.yml you can find a configuration like this - port: 5280 module: ejabberd_http request_handlers: "/websocket": ejabberd_http_ws Enable api and oauth, - port: 5280 module: ejabberd_http request_handlers: "/websocket": ejabberd_http_ws "/api": mod_http_api "/oauth": ejabberd_oauth We are enabling api to have access from other programming languages(JSON request and response) We are enabling oauth to raise an api request and get response

Here's what I have so far. XMPP Server - Ejabberd or Vine XMPP Library in Rails - Blather XMPP Library on Client - Strophe.js Is this what I need to integrate chat into my rails app? EDIT: from the creator of Vine. "It's probably safer to use ejabberd, since its a more full-featured server than vines." I would have add a comment but unfortunately I don't have enough reputation yet. If you want to do your chat client side, Strophe is recommended. If you want to store some conversations, you'll do it server-side, but not 'rails server'-side, you should do it 'xmpp server'-side : Ejabberd should

I am using ejabberd server and ios xmppframework. there are two clients, A and B. When A and B are online, A can send message to B successfully. If B is offline, B can receive the message when B is online again. But when B is suddenly/unexpectedly lost connection, such as manually close wi-fi, the message sent by A is lost. B will never receive this message. I guess the reason is that B lost connection suddenly and the server still think B is online. Thus the offline message does work under this condition. So my question is how to ensure the message that sent by A will be received by B? To

i'm setting up a chat system for my niche social site and have decided on ejabberd for the server side, but i cannot find any decent web-based ajax clients. most seem to be abandoned years ago or simply do not work. i've looked at every single one here : http://xmpp.org/xmpp-software/clients/ Is anyone running a live site and using an ajax-based client that they can vouch for that works and is in active development ? I do not mind paying for something, but I do not want to do any development work whatsoever. thanks in advance. I'm unsure of its maintainership status, but I usually point people

I have ejabberd setup to be the xmpp server between mobile apps, ie. custom iPhone and Android app. But I've seemingly run into a limitation of the way ejabberd handles online status's. Scenario: User A is messaging User B via their mobiles. User B loses all connectivity, so client can't disconnect from server. ejabberd still lists User B as online. Since ejabberd assumes User B is still online, any message from User A gets passed on to the dead connection. So user B won't get the message, nor does it get saved as an offline message, as ejabberd assumes the user is online. Message lost. Until

We have a social networking site where people have contacts and we want it to be integrated with XMPP. We currently use ejabberd XMPP server. Here are my questions: How to properly create account? Right now, what I'm thinking is on user registration on our web app, we'd call a script that would execute an ejabberd command to create a user. User authentication. Upon user login on our website, the user would be automatically logged in on the chat system. How do you do this on the client side with strophe.js? As I understand, you need to provide JID and password for authentication, so I'm

i recently installed ejabberd on Ubuntu 12.04 LTS. I made the necessary configuration and am able to connect using a xmpp client PSI on a different computer using LAN ip. Now I want to allow my ejabberd server to be accessible from the public url, but have been unsuccessful. I have done the following: Assuming my public domain is example.domain.com and the public IP is 123.123.10.210 opened port 5222 5269 and 5280. iptables -A INPUT -p tcp --dport 5222 -j ACCEPT iptables -A INPUT -p tcp --dport 5269 -j ACCEPT iptables -A INPUT -p tcp --dport 5280 -j ACCEPT added the following to my host file: