AnsweredAssumed Answered

MultipleAddresses type "ofrom" missing

Question asked by andrelab on Jan 9, 2015
Latest reply on Jan 9, 2015 by Flow

In the Section 7.2.14. Discussion History of the XEP-0045 (Multi-User Chat) it is presented the Extended Stanza Addressing (XEP-0033) Type "ofrom":

 

If the room is non-anonymous, the service MAY include an Extended Stanza Addressing (XEP-0033) [16] element that notes the original full JID of the sender by means of the "ofrom" address type:

Example 36. Discussion History Message with Original From

<message
   
from='coven@chat.shakespeare.lit/firstwitch'
   
id='162BEBB1-F6DB-4D9A-9BD8-CFDCC801A0B2'
   
to='hecate@shakespeare.lit/broom'
   
type='groupchat'>
 
<body>Thrice the brinded cat hath mew'd.</body>
 
<delay xmlns='urn:xmpp:delay'
    
from='coven@chat.shakespeare.lit'
    
stamp='2002-10-13T23:58:37Z'/>
 
<addresses xmlns='http://jabber.org/protocol/address'>
   
<address type='ofrom' jid='crone1@shakespeare.lit/desktop'/>
 
</addresses>
</message>

 

So, the org.jivesoftware.smackx.address.packet.MultipleAddresses.Type enum should have the "ofrom" value.

Outcomes