If this really is a client namespace stanza on a component stream, then it's incorrect, and prosody should be rejecting it.
Early servers often ignored the namespace, resulting in this kind of behaviour being silently ignored. On 22 Aug 2016 4:06 p.m., "Daniel Pocock" <[email protected]> wrote: > > > (originally queried on prosody-users) > > > > On 21/08/16 14:56, Balram Pariyarath wrote: > > Hi guys, > > I am a GSoC'16 student working on iChat-gateway, intended to facilitate > > communication between XMPP and SIP protocols. > > > > When I try to run the process using prosody in the lab server, I receive > > these entries in prosody.log: > > > > Aug 21 14:26:21 jcped5550debugReceived[component]: <message > > xmlns='jabber:client' type='normal' to='[email protected]/phone > > <http://[email protected]/phone>' from='gateway.test.sip5060.net > > <http://gateway.test.sip5060.net>'> > > Aug 21 14:26:21 stanzarouterdebugUnhandled component stanza: message; > > xmlns=jabber:client > > > > What does "Unhandled component stanza" mean? Does this mean that > > Prosody can't accept the Stanza and if so why? > > > > Is the xmlns a problem? The stanza is generated using the gloox c++ > > library. > > > > > I noticed other stanzas in the Prosody log do not have an xmlns attribute. > > Does the stanza from the component that does add this attribute appear > to be correct? > > Does Prosody (or anything else) have some problem with this namespace? > > Or is the xmlns a red herring here and something else is wrong? > > Regards, > > Daniel > > > _______________________________________________ > JDev mailing list > Info: https://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ JDev mailing list Info: https://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
