I am using WhatsApp Business API and in conversation, I want to know the message I have sent has been read or not by the receiver.
I have got response as 'sent', 'delivered' and other but not the 'read'.
I also have checked on my number (WhatsApp Privacy Setting) where I have set "Read receipts" enabled, if this was the case.
Could any one please help me to sort it out?
Related
I set up a glitch service as described in the Meta doc to receive notifications of WhatsApp received messages via a webhook. However, messages notifications are not received at all, not even pressing the test button of the webhook. Please, note that it's not a general configuration problem, since other notifications (e.g., account_alerts) are properly received.
(I'm using the test phone number provided by Meta)
Any hints about this issue?
Turned out it was a bug: https://developers.facebook.com/support/bugs/856675538926230/
(Now it seems fixed)
My question mainly will be related to ISO8583 for MTI "0800" regarding "logon request".
The question is, what if the client did not initialize with "0800" previously? So he just sends a message with MTI other than "0800".
For instance, if the client sent "0200", but not yet send "0800" previously, how we should tell him that he must do "0800" first:
Should it be using the same ISO8583 message class from the request?. For instance, when user send a message with MTI "0200", but because he did not logon previously with "0800", we give response "0220"
Or should it use "08xx" MTI response for every request sent by the user when they did not initialize a "logon request"?. For instance, even user sent MTI "0200", we will still give them "0820" instead "0210" because he did not login yet.
I am sorry if maybe my question does not make sense, I just a few days working with ISO8583. I hope someone can help me answer my question with a general practice or even best practice of ISO8583, or just please correcting me :).
Thanks in advance.
Regards.
When you send a 0800, you should expect a 0810 in response.
If, on the other hand, you receive a 0800, you should reply with a 0810.
I'm new to SMPP protocol. I'm using it for sending SMS via SMSC.
I found in docs that it is possible to send optional TLV parameters.
I want to send additional_status_info_text in submit_sm and receve it back in deliver_sm. Is it by spec of SMPP or not?
Not entirely sure, but I don't think it is by spec. I remember additional_status_info_text being used mostly to send extra information, like for debugging purposes.
You want to receive in the deliver_sm with the delivery receipt for your submit_sm the info you sent in the TLV or ?
Maybe if you could give more details about what you are trying to achieve exactly with the return of that parameter, I could be of more help.
So I managed to connect to the websocket with my API token and I do get notifications. For incoming calls, I do get a push with all info like so:
{"type":"push","targets":["stream"],"push":{"type":"mirror","source_device_iden":"XXXXXXX","source_user_iden":"ujC7S24sQxw","client_version":206,"dismissible":true,"title":"5555551212","body":"Incoming call","application_name":"Pushbullet","package_name":"com.pushbullet.android","notification_id":"6","icon"
"Big value here"}}
So I can see that call came from 555-1212 (I changed number for privacy) and it all makes sense. However, for SMSs, all I get is a notification that SMS changed. No body field so I can't see where it came from and what the message is. All it says is sms_changed for type:
{"type":"push","targets":["stream"],"push":{"type":"sms_changed","source_device_iden":"XXXXXXXXX"}}
What am I doing wrong? I would like to get the SMS message and sender info so that I can publish it. Any and all help will be greatly appreciated.
This is not publicly documented yet and we might be changing the implementation in the near future so I'm hesitant to make it public. Also I don't know the specifics of the current implementation.
You can view how it works right now by using www.pushbullet.com and looking at the network traffic (in chrome inspector) when you do SMS stuff on the website.
hi
I cannot see any explanation of the implementation of the collapse_key.
I think i understand what it does but not how it do it!
Android Cloud to Device Messaging Framework
I have a C2DM framework set up and sending 4 types of messages to many phones.
String messages very basic looks kind of like this:
type:name:uuid
type:name:uuid:number
type:uuid:id
If the phone is off many of this can get piled up waiting for phone on-line.
as far as i can tell my system works but what will the collapse_key do for me here?
addEncodedParameter(sb, "collapse_key", "no_ide_what_to_put_here");
You mentioned retrying the same message 3 times and using the same key value. It doesn't really have to be the same message. If you've got a message that indicates the current price of a stock, for instance, and you really only care about the latest price, then you could send different messages with the same key. When the device comes back online, it only gets the latest price quote message.
This may have been what you were saying already, but wanted to make it clear it's not only for "retrying sending same message".
I found this text: “collapse key” used for overriding old messages with the same key on the Google C2DM servers" I think if im retrying sending same message 3 times I must use same key value right. Google cloud server will send the latest msg with the same key value
...but be aware of the following (from http://code.google.com/intl/sv-SE/android/c2dm/):
"Note that since there is no guarantee of the order in which messages get sent, the "last" message may not actually be the last message sent by the application server."
But maybe this is not an issue if you don't generate a lot of messages.