[Digital^Dude] (R | 8 Apr 20:36 2014
Picon

get_presence not working

Hi all,

I am unable to find out how to make use of

http://www.ejabberd.im/ejabberd+integration+with+XMLRPC+API#ejabberdintegrationwithXMLRPCAPI-get_presence

on ejabberd (any version) especially 13.12 to which this particular reference to the documentation exists...

Any hints?
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Xavier Beaudouin | 7 Apr 12:31 2014

mod_shared_roster_ldap and posix account like LDAP ?

Hi there.

I am trying without success to make some mod_shared_roster_ldap to work with my OpenLDAP.

My schema is vey simple with 2 ou :

ou=people,dc=mydom,dc=com

Sample user :

# User TOTO, people, mydom.com
dn: cn=User TOTO,ou=people,dc=mydom,dc=com
cn: User TOTO
gecos: User TOTO
givenName: User
l: Paris
loginShell: /bin/sh
mail: user.toto <at> mydom.com
o: Horizon Software
objectClass: top
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
postalCode: 75009
uid: utoto
uidNumber: 17
street: 13 rue La Fayette
homeDirectory: /home/tcollet
title: The User
departmentNumber: One departement
gidNumber: 7003
telephoneNumber: +33 1 42 12 12 12 
sn: TOTO
homePhone: 701

ou=group,dc=mydom,dc=com

With some groups :

# paris, group, mydom.com
dn: cn=paris,ou=group,dc=mydom,dc=com
description: Paris Users
gidNumber: 10000
cn: paris
memberUid: utoto
memberUid: utata
memberUid: ubla
objectClass: posixGroup
objectClass: top

# bangkok, group, mydom.com
dn: cn=bangkok,ou=group,dc=mydom,dc=com
description: Bangkok Users
gidNumber: 10004
cn: bangkok
memberUid: auser
memberUid: cuser
memberUid: suser
memberUid: tuser
objectClass: posixGroup
objectClass: top

Ejabberd has been configured to use email as login.

All login works, but I connot figure what kind of parameters to make to populate mod_shared_roster_ldap to
get several groups :

Paris
Bangkok

etc...

Do you have a nice idea ?

Regards,
Xavier

--

-- 
Xavier Beaudouin - Senior Network and System Administrator
Yash Shah | 2 Apr 18:42 2014
Picon

Pubsub Error: Feature not implemented

Hi Please help me on this issue,
Whenever I create a node and then want to configure it, I get this error:

<error code='501'
       type='cancel'>
<feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
</error>

Please help me how can I get rid of this error.

PS: I have already enabled mod_pubsub & mod_cap

Thanks,
Yash
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
[Digital^Dude] (R | 31 Mar 08:55 2014
Picon

ejabberd 13.12 xmlrpc

Any successful users of mod_xmlrpc in ejabberd 13.12 ?

I cannot even get any output from ejabberdctl user_resources jenkins localhost

Although user jenkins is using resources and is showing presence.

I added the following in my ejabberd.yml file: and in


include_config_file: "/etc/ejabberd/xmlrpc.cfg"


{listen, [ {{4560, "127.0.0.1"}, ejabberd_xmlrpc, [ {access_commands, [ %% This bot can execute any command: {xmlrpc_bot, all, []}, {xmlrpc_bot_reg_test, [register, unregister], [{host, "test.org"}]} ]} ]} ]}.

doesn't work...
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
[Digital^Dude] (R | 31 Mar 08:48 2014
Picon

ejabberd 13.12 mod_logdb

Hello,

Is there any way of logging non-offline messages to the admin page?

This claims to do the job for obsolete version...(http://www.dp.uz.gov.ua/o.palij/mod_logdb/) but it seems to have been discontinued and is not being maintained any more.

Any ideas for enabling logging of messages on ejabberd 13.12?

Thanks.
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Raoul Duke | 22 Mar 19:32 2014
Picon

Losing messages to dead connections

Hi list,

I am having the same problem as outlined here:

http://stackoverflow.com/questions/17424254/ejabberd-online-status-when-user-loses-connection

I will quote the scenario outlined in the above post for convenience:

<quote>

1] User A is messaging User B via their mobiles.
2] User B loses all connectivity, so client can't disconnect from server.
3] ejabberd still lists User B as online.
4] Since ejabberd assumes User B is still online, any message from
User A gets passed on to the dead connection.
5] So user B won't get the message, nor does it get saved as an
offline message, as ejabberd assumes the user is online.
6] Message lost.

Until ejabberd realises that the connection is stale, it treats it as
an online user.

</quote>

Before I move on I have a question: why does ejabberd not notice that
the send to the "dead connection" failed?  i.e. if the other end is
gone/dead and therefore not ACK-ing the TCP send from ejabberd then
why doesn't ejabberd notice this and deem the message as undelivered?
 I guess this is some well known issue with TCP but it would help
visualize it if someone could explain it a bit.  Is this perhaps
related to terminating proxies/firewalls between ejabberd and the
user?

BTW, I realize that xep-0198 would probably be a much better solution
to this and I plan to test the new patch but for the meantime I am
trying to mitigate this with mod_ping.

The issue with mod_ping however, as the above post also points out, is
that the 32 second timeout for receiving pongs is quite long in the
context of this message black-holing problem.  I would like to lower
the window of potentially black-holed messages.  Am I correct in
assuming that this is the best I can do (in lieu of something like
xep-0198?).

I had a look at the ejabberd sources and it looked to me that the main
diifficulty in changing this timeout for mod_ping pongs is that it
seems to be implicit/important in many other things in ejabberd
(things unrelated to mod_ping).

Therefore I have patched mod_ping so that I can override the 32 second
timeout for mod_ping timeouts only (and set this via confguration). My
patch resolves around change the call to ejabberd_local:route_iq to
pass the optional extra timeout argument allowing me to set a lower
timeout for mod_ping only (without affecting other things that clal
route_iq).

Do you anticipate any problems with this approach?  Can someone please
outline the thinking behind the 32 seconds and why it is not
configurable.  Am I setting myself up for some sort of fall by
lowering it in mod_ping?

What would you recommend as a minimum value for this timeout?  Would a
value of (say) 5 seconds be reasonable?

BTW - the above stackoverflow also has a reply which outlines a rather
interesting idea for an ejabberd add-on as follows:

"I created a mod and hooked up to the send_packet and receive_packet
events. Save the message ID to a table. Start a 10 sec waiting thread.
If the receive_packet hook gets the message ID back under 10 sec I
kill the thread, else I manually store the message in the offline
table. Worst case now is, I might have the msg twice in the offline
table. But it will have the same ID, our clients know not to duplicate
messages. - Johan Vorster Dec 12 '13 at 16:49"

This sounds like a bit of a kludge but it also sounds like it may be
an effective one.  Does this sound viable?  Does anyone know or have
any mod already implemented like this?  It isn't clear to me in the
user_receive_packet how I could interrogate the MessageID, can someone
send me a pointer/example of this?

Any pointers/suggestions appreciated.

Thanks.
Bellan Saravanan | 19 Mar 17:05 2014
Picon

Re: bosh xml-not-well-formed

It was a problem with the client library where the client  was sending presence/im packets when session was not fully connected. 
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Bellan Saravanan | 17 Mar 08:55 2014
Picon

bosh xml-not-well-formed

I'm trying to find the difference in using the two xmpp js libraries strophe and stanza.io,

With Strohpe everything works fine and this is what I see in the ejabberd log,

=INFO REPORT==== 2014-03-17 07:15:13 ===

D(<0.591.0>:mod_http_bind:69) : Incoming data: <body rid='984820457' xmlns='http://jabber.org/protocol/httpbind' sid='7cfd532489a59959bfe6a5cef579ba1403f8cfa6'><presence xmlns='jabber:client'/><message to='bsarva <at> precise32' type='chat' xmlns='jabber:client'><body>hello</body></message></body>


=INFO REPORT==== 2014-03-17 07:15:13 ===

D(<0.591.0>:ejabberd_http_bind:1128) : --- incoming data ---

<body rid='984820457' xmlns='http://jabber.org/protocol/httpbind' sid='7cfd532489a59959bfe6a5cef579ba1403f8cfa6'><presence xmlns='jabber:client'/><message to='bsarva <at> precise32' type='chat' xmlns='jabber:client'><body>hello</body></message></body>

 --- END ---



With Stanza.io, I get xml-not-well-formed error,

These are the packets I see in the log,

=INFO REPORT==== 2014-03-17 07:51:40 ===

D(<0.619.0>:mod_http_bind:69) : Incoming data: <body xmlns="http://jabber.org/protocol/httpbind" xmlns:xmpp="urn:xmpp:xbosh" rid="199982875" sid="47c624ccdada4c705fcac9d6a42072187b3d21ef"><presence xmlns="jabber:client" id="5ceab57b-be84-47d3-9c49-227b32eae113"></presence><message xmlns="jabber:client" to="bsarva <at> precise32" type="chat" id="2762ded6-b602-472b-a86a-359ab33a9f3e"><body>Hello</body></message></body>


=INFO REPORT==== 2014-03-17 07:51:40 ===

D(<0.619.0>:ejabberd_http_bind:1128) : --- incoming data ---

<body xmlns="http://jabber.org/protocol/httpbind" xmlns:xmpp="urn:xmpp:xbosh" rid="199982875" sid="47c624ccdada4c705fcac9d6a42072187b3d21ef"><presence xmlns="jabber:client" id="5ceab57b-be84-47d3-9c49-227b32eae113"></presence><message xmlns="jabber:client" to="bsarva <at> precise32" type="chat" id="2762ded6-b602-472b-a86a-359ab33a9f3e"><body>Hello</body></message></body>

 --- END ---



....

....

....

=INFO REPORT==== 2014-03-17 07:51:40 ===

D(<0.620.0>:ejabberd_http_bind:732) : really sending now: [{xmlelement,

                                                            "presence",

                                                            [{"xmlns",

                                                              "jabber:client"},

                                                             {"id",

                                                              "5ceab57b-be84-47d3-9c49-227b32eae113"}],

                                                            []},

                                                           {xmlelement,

                                                            "message",

                                                            [{"xmlns",

                                                              "jabber:client"},

                                                             {"to",

                                                              "bsarva <at> precise32"},

                                                             {"type","chat"},

                                                             {"id",

                                                              "2762ded6-b602-472b-a86a-359ab33a9f3e"}],

                                                            [{xmlelement,

                                                              "body",[],

                                                              [{xmlcdata,

                                                                <<"Hello">>}]}]}]


=INFO REPORT==== 2014-03-17 07:51:40 ===

D(<0.622.0>:ejabberd_http_bind:916) : OutPacket: [{xmlstreamelement,

                                                   {xmlelement,

                                                    "stream:error",[],

                                                    [{xmlelement,

                                                      "xml-not-well-formed",

                                                      [{"xmlns",

                                                        "urn:ietf:params:xml:ns:xmpp-streams"}],

                                                      []}]}}]


The only differences I see are is in the use of single/double quotes, presence of id attribute. 


Please help

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Holger Weiß | 12 Mar 23:53 2014
Picon
Picon

XEP-0198 support

Just in case anyone is interested: I'm working on XEP-0198 (Stream
Management) support for ejabberd (cf. EJAB-532) and am done with an
initial patch.  If you'd like to test it (don't use it in production!):

  https://github.com/weiss/ejabberd

This is the raw diff:

  https://github.com/weiss/ejabberd/compare/master...xep-0198.diff

The patch currently implements stanza ACKs but not the (optional) stream
resumption feature described in the same XEP.  I'll look into that soon.

I'd be *very* interested in any kind of feedback.

Holger
aman.gujaria | 27 Feb 05:06 2014
Picon

aman.gujaria <at> gmail.com has indicated you're a friend. Accept?

Click here to discover aman.gujaria <at> gmail.com's favorite websites!
aman.gujaria <at> gmail.com wants to follow you
I would like to add you as a friend
-aman.gujaria <at> gmail.com
Accept Decline
Following aman.gujaria <at> gmail.com helps you discover great websites they recommend :)
Click here to unsubscribe from such emails from aman.gujaria <at> gmail.com or all friends


P.O. BOX 70928, Sunnyvale, CA 94086
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
aman.gujaria | 27 Feb 04:19 2014
Picon

aman.gujaria <at> gmail.com has indicated you're a friend. Accept?

Click here to discover aman.gujaria <at> gmail.com's favorite websites!
aman.gujaria <at> gmail.com wants to follow you
I would like to add you as a friend
-aman.gujaria <at> gmail.com
Accept Decline
Following aman.gujaria <at> gmail.com helps you discover great websites they recommend :)
Click here to unsubscribe from such emails from aman.gujaria <at> gmail.com or all friends


P.O. BOX 70928, Sunnyvale, CA 94086
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

Gmane