![]() Personalisation not taken in account.Ī hashmap with extra information about how much the message costs. The MNC (Mobile Network Code) part of MCCMNC. The MCC (Mobile Country Code) part of MCCMNC. ![]() It could have null value if the message isn’t delivered yet. The code of the operator of the message sender. The name of the operator of the recipient. The prefix code for the recipient’s original country, based on MSISDN. The name of the recipient’s original country, based on MSISDN. The date and time of the last status in RFC3339 format (Y-m-d\TH:i:sP) Read more about status reasons.Įxtra error code that describes the failure in more detail (optional, null if not available) Possible values: successfully delivered, pending DLR, DLR not received, unknown subscriber, unavailable subscriber, expired, opted out, received network error, insufficient balance, carrier rejected, capacity limit reached and generic delivery failure. Possible values: scheduled, sent, buffered, delivered, expired, and delivery_failed The status of the message sent to the recipient. The count of recipients where the delivery has failed (status delivery_failed).Īn array of recipient hashmaps. The count of recipients where the message is delivered (status delivered). The count of recipients that have the message pending (status sent, and buffered). The datacoding used, defaults to plain (GSM 03.38 characters only), or it can be set to unicode (contains non-GSM 03.38 characters) or set to auto and we will set unicode or plain depending on the body content. The SMS route that is used to send the message.Ī hashmap with extra information. If a message is not delivered within this time, the message will be discarded. The amount of seconds that the message is valid. reference is required for a status report webhook to be sent. The status report URL to be used on a per-message basis. You can set a default originator in your account or use inbox to use the Sticky VMN feature. In case of an alphanumeric string, the maximum length is 11 characters. This can be a telephone number (including country code) or an alphanumeric string. mt: mobile terminated (sent to mobile) mo: mobile originated (received from mobile) Tells you if the message is sent or received. From what I could see, the current forge plugins that support this feature are only available for Android (but you can see here there are other Cordova plugins that are cross platform, but they are lacking an OutSystems wrapper plugin): SMS Cordova Plugin and the more recent SMS Receiver Plugin from the same package author.A unique random ID which is created on the MessageBird platform and is returned upon creation of the object. There are a few other specific to countries like Zenziva SMS for Indonesia, or SMS Talk for Brazil.įor Mobile Applications (OutSystems 10 onwards):įor Mobile Apps, this kind of functionality can still be achieved server-side, but for devices with SMS capabilities you may be able to use the devices' hardware to directly send/receive SMS from your applications. You have several available on the forge: Twilio and SMS Carrier where easy to spot there. This would require an SMS Gateway properly configured (instructions detailed in the OutSystems Platform Server's Installation Checklist).įrom OutSystems 11 onwards, I guess your only bet is to use existing online services that provide that functionality. ![]() Up until OutSystems 10, the platform had built-in server-side support to send/receive SMS (you would need to create a new SMS Flow, just like you can create new UI Flows). You fail to mention if you are talking about Mobile Apps or Web Applications, and that is quite relevant here.
0 Comments
Leave a Reply. |