I have implemented xmpp chat in ios app, connection get established, get authenticated, message successfully sent but it not recieving message from other end??
You must send a presence stanza, either without a priority subelement (which means priority 0), or with a priority element that is 0 or higher, in order to receive messages:
<presence>
<priority>10</priority>
</presence>
Related
Message filtered
Possible Causes
Your message was identified as spam or unwanted messaging by Twilio's message filtering system
Your message was flagged as objectionable and blocked by a wireless carrier
Also Twilio showing that SMS status is not green right now
https://status.twilio.com/
PROGRAMMABLE MESSAGING
SMS
I am developing a chat app using ejabberd server for both IOS and Android. I also wrote a module for ejabberd to get the offline messages sent to my own server api .
my own server api will send notifications to the IOS/Android platforms using FCM.
On the client side , if the application is in the foreground or the background , it will stay connected to ejabberd and if the client receives the message then ejabberd will send the message delivery status.
I am facing an issue while the app is terminated ( service is not running ) which means it is not connected to ejabberd (offline) . if i send a message to this app while it is not terminated , it will receive a notification but the message still undelivered . how can mark the messages as delivered when receiving the notification while the app is terminated.
to explain it more , the same functionality is working fine with whatsapp :
device A has whatsapp installed and whatsapp was turned off (terminated)
Device B has whatsapp running
Device B sends a message to device A
Device A receives a whatsapp notification
Without doing anything on Device A , the message status on Device B is marked as delivered .
How can I implement this scenario with ejabberd ?
In case someone went into this issue , here is the solution that I implemented with help of #Mickaël Rémond from his answer.
I configured ejabberd to send the offline messages to an http service ( your own server) please refer to this link for further on how to do it
your server should catch the above call and generate a notification message (FCM ) in my case and send it to recipient device
recipient device will catch the notification which includes the message
recipient device will call http service (your own server backend)that responsible for sending the deliver ack to the original sender . you need to pass from, to , stanzaId , vhost with this call
backend server will use ejabberd-api (set of exposed apis to manage ejabberd through rest apis calls) to send delivery message using this api
please note the following notes also :
sending the delivery message from your own server to ejabberd will not delete them from ejabberd database
if the user re-connected to the ejabberd server then the recipient will receive the message again from ejabberd .
It is probably too complex for a simple Stack Overflow question, as you need to integrate several moving part on client and server:
You need to execute code in background when receiving push notifications on iOS (you need that property set on your app in your app provisioning profile and have code to handle that). The client will initiate an HTTPS query to let the server know that the message was delivered.
You need to have an endpoint that will get the delivered HTTPS calls and generate either a message ack or a chat marker on behalf of the user and route it in ejabberd.
In real world, this is not enough if you want to take into account the fact that you can only have 1 push in the queue on APNS. If you have several messages sent while the device is not on the network, you will need to have the device check all received messages while offline on the server, otherwise you will lose messaging.
You need to rely on XMPP Message Archive Management (MAM) to handle that history.
As you see, this is not a simple few tens of line of codes but need real design and involved work.
We referred to Apple's TN2265 (https://developer.apple.com/library/ios/technotes/tn2265/_index.html) for implementing error handling in our app, which sends push notifications to our users. The documentation suggests that we deal with errors asynchronously, specifically:
If you get six bytes back, that's an error response that you can check for the response code and the ID of the notification that caused the error. You'll need to send every notification following that one again.
Is it the case that in a sequence of notifications, if one fails then all notifications following it are guaranteed to have failed? If not, then how does one avoid duplicate sends of the same notification to a given device?
Yes, in that case all the notifications following it are guaranteed to not even be processed by the APNS server.
When APNS detects an invalid message, it writes the error response to the socket and closes the connection. Until you receive that error response, it's possible that you already sent more messages to Apple on the same socket. All of them won't reach Apple. Once you create a new socket you should resend all of them.
There is no risk of duplicates.
I'm using the XMPP protocol in order to send and receive messages with the Facebook chat.
I'm able to receive messages, and as well get the typing notifications.
My problem is that I'm not receiving the 'typing paused' notification.
My app has successfully made the auth procedure and when the user is typing a message I'm receiving the 'composing' message but when he stops typing I'm not getting the 'paused' message that is documented in the XEP-0085 protocol.
Thanks
The answer is most likely that Facebook doesn't support <paused/>. Only support for <active/> and <composing/> is absolutely required by the XEP.
Your client should handle <paused/> appropriately, but also handle not receiving it just fine too.
I have an iphone app where I want to use chat rooms. I've installed an XMPP server (ejabberd) and downloaded the XMPP framework for iOS from google code (http://code.google.com/p/xmppframework/). The server and client work as expected, since I'm able to log in and send chat messages between two users.
However, when I try to create a chat room using the createOrJoinRoom method of the XMPPRoom class (in XEP-0045), I don't get any reply from the server and the chat room is not created.
I've debugged to see what kind of package is sent to the server and it looks like this:
<presence from="test2#beta.bogus.net/mynick" to="muumit15#conference.beta.bogus.net">
<x xmlns="http://jabber.org/protocol/muc"/>
</presence>
I get no error message back but the chat room (muumit15) is not created. At the same time I can use e.g. Adium client to create a chat room and it succeeds. The server has been configured so that every user has a right to create chat rooms.
Any ideas? I even tried sniffing the TCP/IP traffic sent by the Adium client but that was encrypted/compressed/binary so I couldn't see what kind of packages it is sending.
See section 7.2.2 of XEP-0045, particularly Example 18:
<presence
from='hag66#shakespeare.lit/pda'
to='coven#chat.shakespeare.lit/thirdwitch'>
<x xmlns='http://jabber.org/protocol/muc'/>
</presence>
Note that the to address MUST contain a resource, and yours doesn't. The resource is the string after the /, which is used as your nickname in the room. For more information on the XMPP address format, see RFC 6122.