![]() ![]() There is no known easy way to do this in RapidPro. Find a reliable way to avoid duplicates by reviewing the new SMS API behaviour, or perhaps by making the outgoing message flow non re-entrant.Make sure that messages are sent without delay perhaps by identifying (or creating) a better CHT doc trigger when there are new pending messages, and not being so dependent on the message configuration.This option of triggering a flow is still advantageous since it permits more flexible channel setups, but we need the following two improvements: Also, SMS schedules, which are in scheduled_tasks, are not being considered. Note that the above outbound push config has limitations in that it would only trigger for the first message in tasks. "relevant_to": "doc.type = 'data_record' & doc.tasks & doc.tasks & & = 'pending'", Here is what the outbound push prototype config looked like: This may have changed with recent improvements to the SMS API. This made it easier to catch and retry any messages that failed to send previously, but makes duplicates theoretically possible if the flow was triggered multiple times before it completes and they get the same set of messages. The flow would then call the SMS endpoint to get a list of all messages that need to be sent, process them in small batches to send them and report the status back to the CHT. The way the outbound push was prototyped was to trigger a flow when a message's state became pending. Pros: handles multiple gateways and processing in RapidPro flows.Ĭons: difficult to reliably trigger flow, duplicates are possible without more work CHT-outbound push to RapidPro: A flow in RapidPro can be triggered when the state of CHT messages go to pending.Pros: no need to build or manage a RapidPro flowĬons: more involved feature in CHT yet less configurable and doesn't handle multiple RapidPro channels CHT-RapidPro messaging integration: the CHT would call the broadcast API to send messages, and poll it to check the status.Write a bespoke SMS aggregator integration to Infobip.Reusing the choices from the comment above, here are the ways that messages could be sent from the CHT to people: Are there any specific queries other than 1 above that you would like to put forward to their technical team and hopefully get us a call or a more constructive array(Įrror handling could include retries, logging, and messages to the sender to let them know that their message was not processed. This may be something to clear up some more with a technical person. FYI, Jeff indicated that we may need to purchase a virtual long number for the technical teams on their end to facilitate an integration and I indicated what we would be looking to have a generic integration. The rest of the process would typically be similar to a short code I was going to respond have responded to Jeff with question 1 above and requested for details on how to go about the integration and copied you. This is a number that is similar to a normal mobile phone number in Zimbabwe. Infobip issues virtual long numbers as an alternative.For example Medic Mobile would do the application, and Infobip would hook it to their systems after we have been issued the short code. The customer does the application via an Econet application portal and Infobip hooks it up to their systems.The representative indicated there maybe consider approvals for some cases e.g say in our case we involved the government. Short codes in Zimbabwe are issued by Econet, the largest Telco and issuance is currently limited to banks.Here is some related useful information from that conversation:. A follow up call with the technical team was suggested to get more info on integration including whether a single integration supports multiple carries out of the box and any other technical concerns we may have. Infobip got back and I had a call with a representative(Jeff). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |