Answers.Body: <p>So I also get the Schema validation warning but the inbound SMS is received. Interesting to note that it did not associate with the right contact as the phone number is on multiple contact records. Tried a second time and it <em>appears</em> it selects the highest ID in civicrm_phone table.</p>
  <p>Best to go to Search &gt; Find Activities and do the following search to see inbound SMS activity:</p>
  <pre><code>Activity Type ID In Inbound SMS ...AND...
  Activity Status In Completed 
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-07-07T16:23:56.993Z
Answers.LastActivityDate: 2021-07-07T16:23:56.993Z
Answers.UserDisplayName: Andy Burns
Body: <p>CiviCRM 5.15.1, WordPress 5.2.2</p>
  
  <p>My org has been successfully <em>sending</em> bulk SMS via Civi/Twilio for a couple weeks, however we are having problems setting up <em>inbound</em> capability.</p>
  
  <p>The Long Number we lease from Twilio is configured as shown below, with a callback URL as follows:
  <a href="https://www.mydomain.org/?page=CiviCRM&amp;q=civicrm%2Fsms%2Fcallback&amp;provider=org.civicrm.sms.twilio" rel="nofollow noreferrer">https://www.mydomain.org/?page=CiviCRM&amp;q=civicrm%2Fsms%2Fcallback&amp;provider=org.civicrm.sms.twilio</a></p>
  
  <p><a href="https://i.sstatic.net/Ydook.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Ydook.png" alt="Twilio config screenshot"></a></p>
  
  <p>The problem is when an SMS recipient replies to a text sent from Civi, Twilio reports error 12200 - Schema validation warning ("provided XML does not conform to the Twilio Markup XML schema"). I understand it's not a fatal error, but I can't find the reply when I look under the senders' Activities. (Anywhere else in Civi I should look?)</p>
  
  <p>Per @balleyne (<a href="https://civicrm.stackexchange.com/questions/22083/wordpress-twilio-inbound-sms-callback-url-failing-when-request-method-is-post">WordPress Twilio Inbound SMS Callback URL failing when request method is POST</a>), I changed POST to GET and re-tested but got a fatal error instead of balleyne's partial success.</p>
  
  <p>Like balleyne and @CDS-Delano (in a comment to this post: <a href="https://civicrm.stackexchange.com/questions/16746/inbound-sms-from-twilio-not-showing-up-in-civicrm-getting-404-error-on-http-pos">Inbound SMS from Twilio not showing up in CiviCRM (getting 404 error on HTTP POST)</a>), Twilio's debugger console shows that what it gets back from the inbound attempt is html instead of the expected xml (or TwiML?).</p>
  
  <p>Following Chris Burgess's advice in that post, I checked the server and PHP error logs with our hosting provider but saw no red flags around the time the reply SMS was sent.</p>
  
  <p>How have others fixed or at least troubleshot this issue, especially any non-coders (like me) out there?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-03T20:04:22.573Z
Comments.Text: We are at the same point / error. Failed when testing with GET. Any progress on your end?
Comments.UserDisplayName: Andy Burns
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-04T00:49:58.913Z
Comments.Text: Yes, though I couldn't tell you if there was something I did that fixed the issue. Basically, weeks to months later (can't remember), I re-checked Activities in Civi looking for something else, and all inbound SMS we had received from the beginning were listed there. We still get the same alerts in Twilio, but now we just ignore them, b/c the texts are coming through into Civi just fine. In Civi's SMS settings, API Type = http, API Url = https://api.twilio.com/, and our API parameters look like this: "From=+1##########" followed by "mo=1"
Comments.UserDisplayName: John Mark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-05T16:18:02.477Z
Comments.Text: Also, in our Twilio webhook settings we are using HTTP POST, to here: https://www.ourdomain.org/?page=CiviCRM&q=civicrm%2Fsms%2Fcallback&provider=org.civicrm.sms.twilio
Comments.UserDisplayName: John Mark
Tags: <sms><twilio>
Title: Twilio Schema validation warning
ThreadText: # Twilio Schema validation warning
  
  (Asked by: username_0 on 2019-07-31)
  
  CiviCRM 5.15.1, WordPress 5.2.2
  
  My org has been successfully *sending* bulk SMS via Civi/Twilio for a couple weeks, however we are having problems setting up *inbound* capability.
  
  The Long Number we lease from Twilio is configured as shown below, with a callback URL as follows:
  <https://www.mydomain.org/?page=CiviCRM&q=civicrm%2Fsms%2Fcallback&provider=org.civicrm.sms.twilio>
  
  [![Twilio config screenshot](https://i.sstatic.net/Ydook.png)](https://i.sstatic.net/Ydook.png)
  
  The problem is when an SMS recipient replies to a text sent from Civi, Twilio reports error 12200 - Schema validation warning ("provided XML does not conform to the Twilio Markup XML schema"). I understand it's not a fatal error, but I can't find the reply when I look under the senders' Activities. (Anywhere else in Civi I should look?)
  
  Per @balleyne ([WordPress Twilio Inbound SMS Callback URL failing when request method is POST](https://civicrm.stackexchange.com/questions/22083/wordpress-twilio-inbound-sms-callback-url-failing-when-request-method-is-post)), I changed POST to GET and re-tested but got a fatal error instead of balleyne's partial success.
  
  Like balleyne and @CDS-Delano (in a comment to this post: [Inbound SMS from Twilio not showing up in CiviCRM (getting 404 error on HTTP POST)](https://civicrm.stackexchange.com/questions/16746/inbound-sms-from-twilio-not-showing-up-in-civicrm-getting-404-error-on-http-pos)), Twilio's debugger console shows that what it gets back from the inbound attempt is html instead of the expected xml (or TwiML?).
  
  Following Chris Burgess's advice in that post, I checked the server and PHP error logs with our hosting provider but saw no red flags around the time the reply SMS was sent.
  
  How have others fixed or at least troubleshot this issue, especially any non-coders (like me) out there?
  
  **Tags:** sms, twilio
  
  > **Comments:**
  > **username_1**: We are at the same point / error. Failed when testing with GET. Any progress on your end?  
  > **username_0**: Yes, though I couldn't tell you if there was something I did that fixed the issue. Basically, weeks to months later (can't remember), I re-checked Activities in Civi looking for something else, and all inbound SMS we had received from the beginning were listed there. We still get the same alerts in Twilio, but now we just ignore them, b/c the texts are coming through into Civi just fine. In Civi's SMS settings, API Type = http, API Url = https://api.twilio.com/, and our API parameters look like this: "From=+1##########" followed by "mo=1"  
  > **username_0**: Also, in our Twilio webhook settings we are using HTTP POST, to here: https://www.ourdomain.org/?page=CiviCRM&q=civicrm%2Fsms%2Fcallback&provider=org.civicrm.sms.twilio  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-07-07. Score: 1
  
  So I also get the Schema validation warning but the inbound SMS is received. Interesting to note that it did not associate with the right contact as the phone number is on multiple contact records. Tried a second time and it *appears* it selects the highest ID in civicrm\_phone table.
  
  Best to go to Search > Find Activities and do the following search to see inbound SMS activity:
  
  ```
  Activity Type ID In Inbound SMS ...AND...
  Activity Status In Completed 
  
  ```
  
  
  ---
  
  