Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As for XMPP documentation (Example 10) this kind of stanza should be valid:
<presence from="support@im.server.com" />
However ejabberd replies with 400 response. The reason here is a missing “to” field. I wonder why it happens.
Based on a XML schema of a XEP-0114 analysis I guess the reason is in a fact that support@im.server.com is an external component.
Could someone confirm that I am right/wrong, or give a suggestion how to overcome the situation?
XMPP Server: ejabberd 2.1.5.
example 10 which you refer to sends out a user presence to a client and includes a resource. So this is server => client.
If I understand you correct you send this presence from your component to the server (component=>server). Without a to address the server is not able to route this presence to another entity.