The same problem here

Real_Yagiza — Sat, 11 Sep 2010 08:27:38 +0000

My client have those features:

<identity category="client" type="mobile" name="eyeCU 0.1" />
<feature var="http://jabber.org/protocol/activity" />
<feature var="http://jabber.org/protocol/activity+notify" />
<feature var="http://jabber.org/protocol/bytestreams" />
<feature var="http://jabber.org/protocol/chatstates" />
<feature var="http://jabber.org/protocol/disco#info" />
<feature var="http://jabber.org/protocol/geoloc" />
<feature var="http://jabber.org/protocol/geoloc+notify" />
<feature var="http://jabber.org/protocol/ibb" />
<feature var="http://jabber.org/protocol/mood" />
<feature var="http://jabber.org/protocol/mood+notify" />
<feature var="http://jabber.org/protocol/muc" />
<feature var="http://jabber.org/protocol/si" />
<feature var="http://jabber.org/protocol/si/profile/file-transfer" />
<feature var="http://jabber.org/protocol/tune" />
<feature var="http://jabber.org/protocol/tune+notify" />
<feature var="jabber:x:data" />
<feature var="jabber:x:oob" />
<feature var="jabber:iq:last" />
<feature var="jabber:iq:oob" />
<feature var="jabber:iq:time" />
<feature var="jabber:iq:version" />
<feature var="urn:xmpp:attention:0" />
<feature var="urn:xmpp:avatar:data" />
<feature var="urn:xmpp:avatar:metadata" />
<feature var="urn:xmpp:avatar:metadata+notify" />
<feature var="urn:xmpp:ping" />
<feature var="urn:xmpp:receipts" />
<feature var="urn:xmpp:time" />

So, S is:

client/mobile//eyeCU 0.1<http://jabber.org/protocol/activity<http://jabber.org/protocol/activity+notify<http://jabber.org/protocol/bytestreams<http://jabber.org/protocol/chatstates<http://jabber.org/protocol/disco#info<http://jabber.org/protocol/geoloc<http://jabber.org/protocol/geoloc+notify<http://jabber.org/protocol/ibb<http://jabber.org/protocol/mood<http://jabber.org/protocol/mood+notify<http://jabber.org/protocol/muc<http://jabber.org/protocol/si<http://jabber.org/protocol/si/profile/file-transfer<http://jabber.org/protocol/tune<http://jabber.org/protocol/tune+notify<jabber:x:data<jabber:x:oob<jabber:iq:last<jabber:iq:oob<jabber:iq:time<jabber:iq:version<urn:xmpp:attention:0<urn:xmpp:avatar:data<urn:xmpp:avatar:metadata<urn:xmpp:avatar:metadata+notify<urn:xmpp:ping<urn:xmpp:receipts<urn:xmpp:time<

And, SHA-1, I've calculated is:

I57R3+FVbzuQ6v4ZzEd5A5uJkdU=

The presence is:

<presence from="admin@akio/eyeCU" xml:lang="en" to="admin@akio/akio" >
<c xmlns="http://jabber.org/protocol/caps" node="http://eyecu.ru/caps" ver="I57R3+FVbzuQ6v4ZzEd5A5uJkdU=" hash="sha-1" />
<x xmlns="vcard-temp:x:update">
<photo/>
</x>
</presence>

PEP notifications do not work. What am I doing wrong?

Re: PEP notifications not working!?

zinid — Wed, 18 Aug 2010 03:18:52 +0000

This is disco cache poisoning protection. Please read XEP-0115 carefully.

Tanks a lot! You are right.

texas — Tue, 17 Aug 2010 16:58:31 +0000

Tanks a lot! You are right. The caps extension was missing when calculating the verification string. Why is it not possible to receive all PEP notifications?

Re: PEP notifications not working!?

zinid — Tue, 17 Aug 2010 15:31:05 +0000

I've computed your disco in ejabberd and got "RZ6z1zGpEKUKt2GndQcLwRucq+w=". So ejabberd ignores your disco info, thus you don't receive PEP notifications.

ejabberd - Comments for "PEP notifications not working!?"

The same problem here

Re: PEP notifications not working!?

Tanks a lot! You are right.

Re: PEP notifications not working!?