[ejabberd] Unexpected presence stanza for MUC

Gaurav Jain monkeyfdude at gmail.com
Mon Nov 17 12:11:00 MSK 2014


Hello,

When I try to create same room twice in a row, I RECV presence stanza from
service containing "201" status code both times.

Is that expected behavior? From XEP-0045, it seems 201 should be send* ONLY*
when the room was created first time.

Please help me understand this. Why is status code 201 sent both times.

Please see below the sequence:

*---------First Request starts here*
SEND: <presence to="erik_yo at conference.localhost/GJ"><x xmlns="
http://jabber.org/protocol/muc"/><x
xmlns="vcard-temp:x:update"><photo/></x></presence>
RECV: <presence xmlns="jabber:client" from="erik_yo at conference.localhost/GJ"
to="erik at localhost/imac"><x xmlns="vcard-temp:x:update"><photo/></x><x
xmlns="http://jabber.org/protocol/muc#user"><item jid="erik at localhost/imac"
affiliation="owner" role="moderator"/><status code="110"/><status
code="201"/></x></presence>

*---------Second request starts here*
SEND: <presence to="erik_yo at conference.localhost/GJ" type="unavailable"><x
xmlns="vcard-temp:x:update"><photo/></x></presence>
SEND: <presence to="erik_yo at conference.localhost/GJ"><x xmlns="
http://jabber.org/protocol/muc"/><x
xmlns="vcard-temp:x:update"><photo/></x></presence>
RECV: <presence xmlns="jabber:client" from="erik_yo at conference.localhost/GJ"
to="erik at localhost/imac" type="unavailable"><x
xmlns="vcard-temp:x:update"><photo/></x><x xmlns="
http://jabber.org/protocol/muc#user"><item affiliation="owner"
role="none"/><status code="110"/></x></presence>
RECV: <presence xmlns="jabber:client" from="erik_yo at conference.localhost/GJ"
to="erik at localhost/imac"><x xmlns="vcard-temp:x:update"><photo/></x><x
xmlns="http://jabber.org/protocol/muc#user"><item jid="erik at localhost/imac"
affiliation="owner" role="moderator"/><status code="110"/><status
code="201"/></x></presence>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20141117/ec534d0f/attachment.html>


More information about the ejabberd mailing list