Changes between Version 23 and Version 24 of UserGuidelines/Messaging

Timestamp:

12/17/10 01:27:50 (14 years ago)

Author:

mmatthews

Comment:

--

UserGuidelines/Messaging

@@ -67 +67 @@
  * http://host.domain.com/eden/msg/tropo?tropo-engine=json
 
-Don't forget to add select "Add a new phone number," in order to reserve a phone number for incoming voice and messaging (in this case, messaging).  This new number is the number that should be entered in, e.g. ODK Collect (in versions with SMS support).
+Don't forget to add select "Add a new phone number," in order to reserve a phone number for incoming voice and messaging (in this case, messaging).  This new number is the number that should be entered in, e.g. [http://eden.sahanafoundation.org/wiki/UserGuidelinesMobile ODK Collect] (in versions with SMS support).
 
 For regular, non-multi-part messages, the incoming message is parsed by the parserdooth() function which uses difflib to allow users to mis-spell the keywords.  In the case of multi-part messages, the tropo() function calls "concatSMS(lastMessage, fromaddress)" method to see if this is the last message in a sequence.  At present, the "sequence" is highly proprietary, and integrated into the "modified jaxdroid" branch of ODK Collect mentioned [http://eden.sahanafoundation.org/wiki/UserGuidelinesMobile here].  The sequence information is combined with a 5-digit unique identifier for that particular form submission.  That sequence information and unique identifier are prepended to the each part of the multi-part SMS transmission by the modified ODK Collect branch's SMS form submission code.  It will look something like this: