<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://100/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Hi Chad,</div><div>thanks for that awesome ESL binding for node.js !</div><div><br></div><div>Section 7 of rfc3428</div><div><br></div><div><blockquote type="cite"><pre style="word-wrap: break-word; white-space: pre-wrap; ">A UAS that receives a MESSAGE request processes it following the
rules of SIP [1].
A UAS receiving a MESSAGE request SHOULD respond with a final
response immediately. Note, however, that the UAS is not obliged to
display the message to the user either before or after responding
with a 200 OK. That is, a 200 OK response does not necessarily mean
the user has read the message.
A 2xx response to a MESSAGE request MUST NOT contain a body. A UAS
MUST NOT insert a Contact header field into a 2xx response.
A UAS which is, in fact, a message relay, storing the message and
forwarding it later on, or forwarding it into a non-SIP domain,
SHOULD return a 202 (Accepted) [5] response indicating that the
message was accepted, but end to end delivery has not been
guaranteed.
A 4xx or 5xx response indicates that the message was not delivered
successfully. A 6xx response means it was delivered successfully,
but refused.</pre></blockquote><div><br></div></div><div><br></div><div>At Fongo (<a href="http://fongo.com">fongo.com</a>) we have a few proxies for store and forward, also for SMS integration. We use 200, 402, 404 and 488 to control delivery and payments.</div><div><div>So in our case, the final device always returns 200 (as it is the final), but a proxy in between might generate a 4xx.</div></div><div>we have an opensips cluster in front of freeswitch and steer MESSAGE methods away from freeswitch to handle those scenarios. I'm looking into removing this logic from opensips and move it to freeswitch to keep it consistent with dialplan and rating engine. </div><div><br></div><div>cheers</div>--<br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">lucas</div></span><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br><div><div>On 2012-11-01, at 5:46 PM, Chad Engler <<a href="mailto:Chad.Engler@patlive.com">Chad.Engler@patlive.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">I don’t think SIP MESSAGEs have a response/ack. I know that our provider doesn’t send anything except the 200 OK when we send a message, and that doesn’t mean it actually made it to the device. As far as I know there is no way to know if and when the device gets the actual message without the device responding with another message back through the via chain.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">-Chad<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><span class="Apple-converted-space"> </span><a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">freeswitch-users-bounces@lists.freeswitch.org</a> [mailto:freeswitch-<a href="mailto:users-bounces@lists.freeswitch.org">users-bounces@lists.freeswitch.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Lucas Fontes<br><b>Sent:</b><span class="Apple-converted-space"> </span>Thursday, November 01, 2012 1:38 PM<br><b>To:</b><span class="Apple-converted-space"> </span><a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>[Freeswitch-users] mod_sms delivery failure<o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">Hi everyone,<o:p></o:p></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">I've been trying to determine if a message was successfully delivered to a device.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">Stumbled on a post from February (subject: Testing mod_sms)<a href="http://lists.freeswitch.org/pipermail/freeswitch-dev/2012-February/005619.html:" style="color: purple; text-decoration: underline; ">http://lists.freeswitch.org/pipermail/freeswitch-dev/2012-February/005619.html:</a><o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div><div><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">________________________________<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">From: Anthony Minessale <<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" style="color: purple; text-decoration: underline; ">anthony.minessale at gmail.com</a>><o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">To: Warren Lin <<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" style="color: purple; text-decoration: underline; ">wlin121443 at yahoo.com</a>> <o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">Sent: Tuesday, February 21, 2012 11:01 AM<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">Subject: Re: Testing mod_sms<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; "><o:p> </o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">hi you can find out how to use the lists at <a href="http://lists.freeswitch.org" style="color: purple; text-decoration: underline; ">http://lists.freeswitch.org</a><o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; "><o:p> </o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">try latest GIT, i put in a patch to fire the events with the heder<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">Failed-Delivery true<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">if you are listening for MESSAGE events you should catch them.<o:p></o:p></pre></div><div><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">________________________________<o:p></o:p></pre><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">I can't find any reference to Failed-Delivery in mod_sms.c neither anywhere else in the source tree. <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">There is a field called Delivery-Failure, but seems to be used by other modules to indicate a failure on the response going out of freeswitch, not to freeswitch.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">Was this overwritten / rolled back at some point ? <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">thanks<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div><div><div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">--<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">lucas<o:p></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div></div></div>_________________________________________________________________________<br>Professional FreeSWITCH Consulting Services:<br><a href="mailto:consulting@freeswitch.org" style="color: purple; text-decoration: underline; ">consulting@freeswitch.org</a><br><a href="http://www.freeswitchsolutions.com" style="color: purple; text-decoration: underline; ">http://www.freeswitchsolutions.com</a><br><br>FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br><a href="http://www.cudatel.com" style="color: purple; text-decoration: underline; ">http://www.cudatel.com</a><br><br>Official FreeSWITCH Sites<br><a href="http://www.freeswitch.org" style="color: purple; text-decoration: underline; ">http://www.freeswitch.org</a><br><a href="http://wiki.freeswitch.org" style="color: purple; text-decoration: underline; ">http://wiki.freeswitch.org</a><br><a href="http://www.cluecon.com" style="color: purple; text-decoration: underline; ">http://www.cluecon.com</a><br><br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org" style="color: purple; text-decoration: underline; ">FreeSWITCH-users@lists.freeswitch.org</a><br><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" style="color: purple; text-decoration: underline; ">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>UNSUBSCRIBE:http://<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" style="color: purple; text-decoration: underline; ">lists.freeswitch.org/mailman/options/freeswitch-users</a><br><a href="http://www.freeswitch.org" style="color: purple; text-decoration: underline; ">http://www.freeswitch.org</a></div></blockquote></div><br></body></html>