9 Commits

Author	SHA1	Message	Date
Martyn Inglis	376f8355cb	Updated clients to have a more robust error handling ... - fire text and omg much more similar. Ready to be combined. - Error handling now for JSON valid responses	2016-09-22 17:18:05 +01:00
Martyn Inglis	c1b00a5f0c	Simplified the config. Aim is to get the actual secrets in credstash to be env specific, and not the random collection of things we have at the moment. ... Secret definition also includes env specific things such as URLs / Queue prefixes / URLs for providers and so on.	2016-09-07 09:35:31 +01:00
Rebecca Law	c8ad5362eb	Moved mmg_url to configs. ... Fix up the tests	2016-07-20 10:40:50 +01:00
Rebecca Law	30f7377d7e	Fix tests	2016-07-19 16:16:12 +01:00
Adam Shimali	c29dd23702	Add sms sender to service to be used in sms templates ... in place of default numeric short code. If not present default short code is used.	2016-07-01 15:27:54 +01:00
Leo Hemsted	a3b847bf64	tests for send_sms through mmg/firetext	2016-06-01 15:59:44 +01:00
Rebecca Law	9a25062943	Update mmg responses so that 3 is success. ... Status codes from mmg are: 2: UNDELIVERABLE Message is undeliverable. 3: DELIVERED Message is delivered. 4: EXPIRED Message is expired. 5: REJECTED Message is rejected.	2016-04-20 14:29:31 +01:00
Rebecca Law	41ce691704	Update to processing the the response from MMG ... MMG changed the datatype and the status codes they send us for the delivery receipts. This PR accounts for that change.	2016-04-20 09:45:13 +01:00
Rebecca Law	4806123d5c	Add process_mmg_responses ... Refactor process_firetext_responses Removed the abstract ClientResponses for firetext and mmg. There is a map for each response to handle the status codes sent by each client. Since MMG has about 20 different status code, none of which seem to be a pending state (unlike firetext that has 3 status one for pending - network delay). For MMG status codes, look for 00 as successful, everything else is assumed to be a failure.	2016-04-06 14:31:33 +01:00