Portal for the relay of XML Lists of Calls with details to be made.
Site will receive XML Files (attached examples) and process/store these files.
There are three components to this project. (All use [login to view URL])
#1. Build simple website for users to see % of each call success, any wrong numbers, and their current credits (for use for more calls)
#2. Build Web Service that accepts/processes XML requests while constantly checking and processing if calls should be going out, what status each call has returned, etc.
#3. Design and build Twilio Phone Interface to accept userID, record message, and then make message available to use for outbound calls so users can send out their own voice as a mass message to list of XML calls that my current software will send in.
#1. The page is waiting for a .XML to be POSTED to it. ([login to view URL])
see sample [login to view URL] for an explanation of the nodes.
All options are sent in the [login to view URL] for explanation purposes. A real .XML might not include anything other than the top 4 site nodes and the numberinfo nodes for who to call. All the other options (seeing they are blank) would have to be displayed to the user for them to chose in an HTML Web Form that you would code.
#2. The page upon receiving the .XML puts the values into a database which is then maintained/checked by a service that is sending calls with their options (voice type, recording vs tts) to twilio for delivery. The 400 Customers that will be using it are on 400 different databases, so siteUSERID and each personid will need to be prefixed with their siteTAG or siteLicenseID (whichever you chose) to make them truly unique, I can send each XML already prefixed or we can do it when storing to the SQL Database. The outcome of each calls delivery (failed, time elapsed on call, buttons pressed, succeeded, left voicemail more?) is saved for later display to user. User can edit calls at any time as long as they have not begun going out.
View [login to view URL] for simple design concept