Project

General

Profile

feature-not-implemented

Anusha Anusha
Added over 1 year ago

While trying out client to test presence, I noticed client is sending feature-not-implemented after receiving a presence. What could be the reason for this error.

SENDING: <presence from="abc1@z.com/lap"><show>chat</show><status>online</status></presence>
RECEIVED : <presence to="abc1@z.com/lap" type="unavailable" from="xyz@z.com"/>
SENDING: <presence to="xyz@z.com" type="error"><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></presence>


Replies (4)

Added by Daniel Wisnewski over 1 year ago

Hello Anusha, can you share some more details?
What version of Tigase are you running?
Which clients are you using?
Can you send the full XML output?

Added by Anusha Anusha over 1 year ago

I am using openfire server and Jaxmpp client.

Full xml Output:

INFO: Using WebSocketConnector
Mar 18, 2016 1:58:21 PM tigase.jaxmpp.j2se.connectors.websocket.WebSocketConnector start
INFO: Opening connection to host:7001
RECEIVED: <features xmlns="http://etherx.jabber.org/streams"><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism></mechanisms></features>
SENDING: <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN">AGlkYzExAGlkYzEx</auth>
RECEIVED: <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
RECEIVED: <features xmlns="http://etherx.jabber.org/streams"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></features>
SENDING: <iq xmlns="jabber:client" id="ZgJviC" type="set"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"><resource>lap</resource></bind></iq>
RECEIVED: <iq type="get" to="/lap" from="/lap" id="2c564f6c.1537eadebc7._4957179403958"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>
RECEIVED: <iq type="result" id="ZgJviC"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"><jid>/lap</jid></bind></iq>
SENDING: <iq from="/lap" id="2c564f6c.1537eadebc7._4957179403958" to="/lap" type="result"><query xmlns="http://jabber.org/protocol/disco#info"><identity name="Tigase based software" category="client" type="pc"/><feature var="jabber:iq:version"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="urn:xmpp:ping"/><feature var="http://jabber.org/protocol/disco#info"/></query></iq>
RECEIVED: <iq type="result" to="/lap" from="/lap" xml:lang="en-US" id="2c564f6c.1537eadebc7._4957179403958"><query xmlns="http://jabber.org/protocol/disco#info"><identity name="Tigase based software" type="pc" category="client"/><feature var="jabber:iq:version"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="urn:xmpp:ping"/><feature var="http://jabber.org/protocol/disco#info"/></query></iq>
SENDING: <iq xmlns="jabber:client" id="XunU27" type="set"><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></iq>
RECEIVED: <iq type="result" id="XunU27"><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></iq>
SENDING: <iq to="x.com" id="3voMKW" type="get"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>
RECEIVED: <iq type="result" to="/lap" from="x.com" id="3voMKW"><query xmlns="http://jabber.org/protocol/disco#info" jid="x.com"><identity type="pep" category="pubsub"/><feature var="jabber:iq:time"/><feature var="jabber:iq:search"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="urn:xmpp:mam:0"/><feature var="urn:xmpp:chat-markers:0"/><feature var="msgoffline"/><feature var="http://jabber.org/protocol/amp"/><feature var="jabber:iq:version"/><feature var="urn:xmpp:blocking"/><feature var="urn:xmpp:ping"/><feature var="jabber:iq:browse"/><feature var="http://jabber.org/protocol/amp#std-conditions"/><feature var="urn:xmpp:carbons:2"/><feature var="jabber:client"/><feature var="http://jabber.org/protocol/amp#std-actions"/><feature var="http://jabber.org/protocol/disco#info"/></query></iq>
SENDING: <iq id="fnYrZi" type="get"><query xmlns="jabber:iq:roster"/></iq>
RECEIVED: <iq type="result" to="/lap" id="fnYrZi"><query xmlns="jabber:iq:roster"><item name="" subscription="both" jid=""><group>Buddies</group></item></query></iq>
RECEIVED: <iq type="get" to="/lap" id="2c564f6c.1537eadebc7._4956179403958"><ping xmlns="urn:xmpp:ping"/></iq>SENDING: <iq from="/lap" id="2c564f6c.1537eadebc7._4956179403958" type="result"/>
SENDING:

RECEIVED: <presence type="unavailable" to="abc@x.com/lap" from="xyz@x.com"/>
SENDING: <presence to="xyz@x.com" type="error"><error code="501" type="cancel"><feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></presence>
RECEIVED: <iq type="get" to="abc@x.com/lap" id="2c564f6c.1537eadebc7._4955179403958"><ping xmlns="urn:xmpp:ping"/></iq>
SENDING: <iq from="abc@x.com" id="2c564f6c.1537eadebc7._4955179403958" type="result"/>

Added by Andrzej Wójcik over 1 year ago

Which version of Jaxmpp client library are you using?
If one of the newest, then feature-not-implemented will be sent by Jaxmpp library if PresenceModule is not registered (which is by default). We changed this behavior when we created new modularized version of Jaxmpp which by default registers only essential modules.
There is tigase.jaxmpp.j2se.Presence class with static method initialize(Jaxmpp jaxmpp) which can be used to register PresenceModule and initialize this module.

Added by Anusha Anusha over 1 year ago

Registering PresenceModule solved the issue Andrzej,thanks a lot

    (1-4/4)