Feed aggregator

We’ve recently had a reorganisation of the solutions section of the website, which included adding a new Military XMPP page.

We released M-Link, our XMPP server, back in 2008 and have developed it further since to include a number of capabilities that make M-Link suitable for use in a Military deployment.

This new web page looks at two sample scenarios to show ways in which XMPP can be used, and requirements that need to be considered given the mix of communication methods likely to be available during a deployment. It goes on to look at the key features that make M-Link appealing to the military market.

Sorry. I forgot to send <stream: ... > at first. On 2012-2-8, at 下午1:50, caox wrote: _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

Begin forwarded message: _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

openfire vs ejabberd OpenBSD Packages and Ports.

I want to know . Thanks Michael Weibel <michael.weibel+xmpp< at >gmail.com>编写： _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

Hi all, do you have any recommendations on how to unit test ejabberd modules? Thanks - Michael _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

... повышение матевации персоналом · влияние на здоровье человека газированные напитки · народные рецепты от бородавок и попилом · приглашение на участие в конференции · роутер и ejabberd 113 · три истории смотреть ...

After several months of development, version 0.4 of Movim is finally out!

This new release contains the following improvements:

• A very big bug was fixed on the session stability. It affected the identifiers of the BOSH session. For more details, have a look here.
• Many widgets have been rewritten and cleaned up to benefit from the latest improvements in the widgets'API.
• A lot of work was done on the cache, almost all data from the XMPP server are now copied in the database so the end users'session is always persistent, even after a rough page reload.
• The roster (contacts list) was rewritten so as to reorganise it and make it clearer. Contacts are now sorted by status, clicking on a contact opens up his profile, and clicking on the small bubble next to the name opens up a chat window.
• The chat was improved and now caches the last 20 messages. It also indicates when the contact is composing a new message.
• A lot of work was done on the feeds, and we implemented the Microblogging XEP. Users can now write and send messages on their feeds and read their contacts'feeds and comments instantly.

And many new features were added:

• The avatars are now processed with the GD library, then cached in the web browser for several hours. This way the pages generated by Movim are only a few kB of HTML code ; the CSS and javascript code are also cached in the browser.
• Movim now supports account creation on both the node and the XMPP server. The implementation handles many error cases and notifies the user as to what problem was encountered while creating the account (existing username, weak password etc.).
• When a new message is receive in Movim and the page is in the background, a [1] is prepended to the page title, and an HTML5 notification (soon to be standardised) is emitted. Firefox users need to intall this add-on to benefit from this feature.
• Two small patches allow Movim to be installed on HTTPS-only servers and to communicate with the XMPP server through a proxy.

You can find more details on the 0.4 roadmap.

Finally, the page pod.movim.eu was created to list all known Movim servers on which you can create an account an try the software in a couple of clicks.

You can download this new release over there.

Have fun!

Previously... After some initial tests, I resolved to test the different components in turn. I started testing the megaphone_receiver component. I finished testing the megaphone_receiver component. I finished testing the megaphone_sender ...

and got following log ,i really don't know wht this says specially over here {error,duplicate_name} so can any please help me how to get rid off this and start ejabberd successfully. {error_logger,{{2012,2,4},{14,28,18}},"Protocol: ~p: register ...

Hello,. I have a running ejabberd installation, with http-bind enabled, nginx proxy, and a mini jappix xmpp client for web browsers. I also have an external authentication program. I can connect the same user on this server with different ...

I have been working on making a special message filter/logger module for the company that I work for. We have a mysql database with user info that I pull info from and shove into a mnesia table. On our development server everything worked. I put the data in and the data comes out when I need it. When I moved to our production server, however, I found that mnesia:read was returning an empty list despite having good keys. I put trace statements in the data entry location and just after the table is filled and my data is there. But when I call it when I need it, the data is no longer in the table, but the table is still there. No errors (other than mnesia:read returning an empty list) show up in either the ejabberd log, erlang log or the sasl log. What could be going wrong? The only place I clear the table is directly after I create it which is before I fill it. Is there something I am missing? Niels van Hecke

Yes, I have loglevel set to 5. Both "ejabberdctl live" and "ejabberctl debug" start with a note about an interactive shell ending in "press any key to continue". When I press a key the program exits. There's no output after "press any key to continue". On Fri, Feb 3, 2012 at 8:13 PM, Jorge Guntanis <jorge< at >guntanis.com> wrote: _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

Do you have {loglevel, 5}. In your config file? When you do "ejabberdctl live" or "ejabberdctl debug" does it exit erlang or does it seem to be running something and just not outputting anything? On Fri, Feb 3, 2012 at 4:38 PM, Andy Theuninck <gohanman< at >gmail.com> wrote: _______________________________________________ ejabberd mailing list ejabberd< at >jabber.ru http://lists.jabber.ru/mailman/listinfo/ejabberd

Same thing. It doesn't matter at all what arguments (or none) I run ejabberdctl with. No output, no logging, nothing. Assuming redhat's ejabberdctl binary is doing roughly the same thing as the ejabberdctl.template shell script in the 2.1.8 source, I think the problem is actually in their erlang files. erl crashes immediately with an Illegal Instruction error. On Fri, Feb 3, 2012 at 5:29 PM, Jorge Guntanis <guntanis< at >gmail.com> wrote:

Try running ejabberdctl live. On Feb 3, 2012, at 12:06 PM, Andy Theuninck <gohanman< at >gmail.com> wrote:

I started testing the megaphone_receiver component. I finished testing the megaphone_receiver component. I had to add some additional code to create a simple megaphone process to which megaphone_receiver could hand off packets.

I'm trying to migrate ejabberd to a new server (CentOS 6). I installed ejabberd 2.1.8 from OS-provided binaries. I then copied /etc/ejabberd/ejabberd.cfg and /etc/ejabberd/ejabberdctl.cfg from my working server (also CentOS, also 2.1.8) to the new server. When I try to start ejabberd via the init script, nothing happens. Digging into the script, the command it's actually running for "start" is this: ejabberdctl start --config /etc/ejabberd/ejabberd.cfg --ctl-config /etc/ejabberd/ejabberdctl.cfg --logs /var/log/ejabberd/ --spool /var/lib/ejabberd/spool Running it myself, as root, produces no output, writes nothing to the specified log directory, and does not start ejabberd. Is there any way to coax more debug information out of ejabberdctl? I'm at a loss how to find the problem without at least some kind of feedback.

I try to stress test ejabberd with bots. Bots are sending messages to each other. When load reaches 30 MB/s it seems that something is limiting the traffic. I disables all shapers and most of the ejabberd plugins, but it doesn't help. The server ...

hi, we seperated our cluster to let a set of nodes do "basic xmpp stuff" and the other cluster do just "muc stuff". these two clusters talk to each others using the s2s protocol. it seems that disco-queries do not work over s2s connections: i send: <iq type="get" to="mucserver" id="ad00a" > <query xmlns="http://jabber.org/protocol/disco#items"/> </iq> i get: <iq from="mucserver" type="result" to="user< at >example.com/resource" id="ad00a" > <query xmlns="http://jabber.org/protocol/disco#items"/> </iq> when using RSM i even get: request: <iq id='ad00a' to='mucserver' type='get'> <query xmlns='http://jabber.org/protocol/disco#items'> <set xmlns='http://jabber.org/protocol/rsm'> <max>20</max> </set> </query> </iq> result: <iq from="mucserver" type="result" to="user< at >example.com/resource" id="ad00a" > <query xmlns="http://jabber.org/protocol/disco#items"> <set xmlns="http://jabber.org/protocol/rsm"> <count>0</count> </set> </query> </iq> i know there are several rooms that exist on that server that are persistent and i can join these rooms and even chat with people there. i just can't get the list of rooms. is this a known limitation, am i missing some kind of configuration option? any help would be greatly appreciated! thanks in advance, stephan