converse.js | Web-based XMPP/Jabber chat client written in JavaScript | Chat library

This is a message that comes from the message archive (a pretty old implementation as it still uses elements which have been used in 2013 and were removed just one year later).

The outer message (id=1596108476932101) is the carrier message which is used to forward the inner, archived message to you. The inner message (id=id9c6b26dd-50dc-467c-a436-dd1e16af05fe) contains a delivery receipt () that tells your contact mayur@xmpp.server.io that another earlier message (id=idcb348164-9a0b-4b9b-b351-03c97341fe91) has been received successfully.

So basically the whole construct is a MAM query result containing an archived message that carries a ´` marker.

While this particular message is not very useful for you, archived messages without body could come in handy in some situations, so you should not ignore all of them. For example archived messages containing chat markers could be used to sync up which messages have been read by any of your clients.

A few weeks ago I checked how configuration works, and updated the documentation acordingly. Try the example configuration provided in https://docs.ejabberd.im/admin/configuration/listen/#ejabberd-xmlrpc

Conerse.js has a public (i.e. globally accessible) API, which is available via the converse global. The most used method there would be converse.initialize.

Most API methods are however restricted to the private (i.e. closured) _converse object (note the leading underscore) and is available via _converse.api.

You can only access _converse.api if you register a plugin.

For example:

I'm not sure why a message event isn't triggered for your custom message. There must be some assumption in the converse.js code which your custom message doesn't fulfill.

Converse.js uses Strophe.js under the hood, so you can use Strophe's addHandler to register an event handler on a lower level.

Here's how you would do this:

Just for future references - the problem was not in this function; the function i used to detect if the request was null that was wrong and returned true every time.

Problem solved.

I finally resolved my issue. Issue was due to incompatible version of NodeJS. As @Himanshu sharma suggested in the reply, i checked last build of cinverse.js which was at aug 8' 17 and found the NodeJS releases before that. Once i installed the appropriate version of NodeJS, i could resolve issue. In my case, it worked with version node-v4.8.4-x64

If you look at the code, you'll see that chatBoxInitialized gets triggered after the chatbox's HTML has already been rendered.

See here: https://github.com/jcbrand/converse.js/blob/393bbe020e45ccd2abe10683117a8f854dea9145/src/converse-chatview.js#L281

Looking at the code, I don't see any event that's triggered after the chatbox has been created, but before it's rendered.

However, in the current master branch of converse.js (to be released soon), you can set the fullname after the chatbox has been created, and it will then appear properly.

You're however setting it wrong. With Backbone.js you must use get and set and not the attributes property.

So this:

Firstly, Converse.js doesn't allow opening chats with users who aren't in your roster (unless you have set allow_non_roster_messaging to true). So make sure the user you're trying to chat with is in your roster.

Secondly, right after the connection event has been fired is still too early to try and open chats.

So you have to first wait until the roster has been populated. This is the rosterContactsFetched event/promise.

Besides that, it's a good idea to also first wait until already opened chat boxes (which are cached in sessionStorage) have also been fetched from the cache. This is the chatBoxesFetched event/promise.

These two events fire only once per session, so they're also available as promises.

To first wait for these two promises to resolve, you're code would therefore look like this: