13 Commits

Author	SHA1	Message	Date
Nicholas Staples	3b1423a2ea	Provider Statistics added. ... Rates command added with a test. Updated to include added migration.	2016-04-21 13:47:04 +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	f283379646	Defend against status code 00 or 0 from mmg	2016-04-20 11:07:21 +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
Nicholas Staples	15c4fb47f7	Added multi parameter for sending messages.	2016-04-18 09:55:56 +01:00
Rebecca Law	fb04b36cba	Fix **kwargs	2016-04-07 10:53:59 +01:00
Rebecca Law	c132bbf46e	Rename NOTIFY_FROM_NUMBER to MMG_FROM_NUMBER, there should be a separate short code per provider.	2016-04-07 10:18:46 +01:00
Rebecca Law	340f8ceaf6	Update mmg send_sms to include cid and request headers ... Use mmg to send_sms	2016-04-06 17:35:14 +01:00
Rebecca Law	323b2ff537	Use MMG client for send-sms	2016-04-06 15:56:34 +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
Rebecca Law	f2ee8f3eb7	WIP	2016-04-05 14:39:59 +01:00
Rebecca Law	2ba12da77d	WIP: adding delivery receipt endpoint for mmg	2016-04-04 15:02:21 +01:00
Rebecca Law	69697388d7	Initial set up for mmg client integration	2016-04-01 16:42:31 +01:00