Projects tigase _server server-core Issues #459
Customized parameters in the MUC message (#459)
Won't Fix
stephen zhang opened 9 years ago

hi tigase team,

My co-worker like to add a customized parameter in the MUC message, but for some reason, this parameter is not relayed by the tigase server, following are the example of the messages and 'id' is the parameter, which he like the XMPP server to relay.


10:13:15.042 [1][M] [xmpp] XML Out : <message 
to='59b5aca50c8f492e9b46fdd4c2e13f97@conference.counterpath.com' id='uid:5531227e:1dd18c32' 
type='groupchat' from='dmak3@counterpath.com/tigase-8' xmlns='jabber:client'><body>What the 
hill</body></message>
10:13:15.196 [O][M] [xmpp] XML In : <message type='groupchat' xmlns='jabber:client' 
from='59b5aca50c8f492e9b46fdd4c2e13f97@conference.counterpath.com/dmak3' 
to='dmak3@counterpath.com/tigase-8'><body>What the hill</body></message>

our version of Tigase server is 5.2.0-b3447, we checked following link, it said, it should work on 5.2.

https://projects.tigase.org/boards/8/topics/1182

but if I configure like following init.properties, the chat room looks like disabled.

--comp-name-3=conference
--comp-class-3=tigase.muc.MUCComponent
conference/message-filter-enabled=false

could you tell us, does version 5.2.0-b3447 support customized parameters in the MUC message?

If it does, how can we configure it?

Thank you very much for your help.

Stephen

wojciech.kapcia@tigase.net commented 9 years ago

Linked issue relates to different concept - filtering of Elements in the stanza (siblings to the body@). Recent (7.0.0+) version of tigase (and included tigase-muc) have fixed the issue of stripping the @id attribute from messages send to MUC component.

Also - please stick to our forums for asking questions, as described in https://projects.tigase.org/issues/2993#change-12304

issue 1 of 1
Type
Task
Priority
Blocker
Assignee
RedmineID
2998
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#459
Please wait...
Page is in error, reload to recover