[Freeswitch-users] mod_sms delivery failure

Chad Engler Chad.Engler at patlive.com
Mon Nov 5 17:07:40 MSK 2012


No problem! Thanks for using it! I've already got a couple of good pull
requests that have been merged in, and a couple other bugs fixed as
well. I want to do a little more cleanup, but npm should be seeing a new
version this week; so be ready for that!

 

-Chad

 

From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of
Lucas Fontes
Sent: Thursday, November 01, 2012 7:29 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] mod_sms delivery failure

 

 

Hi Chad,

thanks for that awesome ESL binding for node.js !

 

Section 7 of rfc3428

 

	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.

 

 

At Fongo (fongo.com) 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.

So in our case, the final device always returns 200 (as it is the
final), but a proxy in between might generate a 4xx.

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. 

 

cheers

--

lucas

 

 

On 2012-11-01, at 5:46 PM, Chad Engler <Chad.Engler at patlive.com> wrote:





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.

 

-Chad

 

From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of
Lucas Fontes
Sent: Thursday, November 01, 2012 1:38 PM
To: freeswitch-users at lists.freeswitch.org
Subject: [Freeswitch-users] mod_sms delivery failure

 

Hi everyone,

 

I've been trying to determine if a message was successfully delivered to
a device.

Stumbled on a post from February (subject: Testing
mod_sms)http://lists.freeswitch.org/pipermail/freeswitch-dev/2012-Februa
ry/005619.html:
<http://lists.freeswitch.org/pipermail/freeswitch-dev/2012-February/0056
19.html:> 

 

________________________________
From: Anthony Minessale <anthony.minessale at gmail.com
<http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev> >
To: Warren Lin <wlin121443 at yahoo.com
<http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev> > 
Sent: Tuesday, February 21, 2012 11:01 AM
Subject: Re: Testing mod_sms
 
hi you can find out how to use the lists at http://lists.freeswitch.org
<http://lists.freeswitch.org> 
 
try latest GIT, i put in a patch to fire the events with the heder
Failed-Delivery true
if you are listening for MESSAGE events you should catch them.
________________________________

 

 

I can't find any reference to Failed-Delivery in mod_sms.c neither
anywhere else in the source tree. 

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.

Was this overwritten / rolled back at some point ? 

 

thanks

 

--

lucas

 

________________________________________________________________________
_
Professional FreeSWITCH Consulting Services:
consulting at freeswitch.org <mailto:consulting at freeswitch.org> 
http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com> 


 <> 

Official FreeSWITCH Sites
http://www.freeswitch.org <http://www.freeswitch.org> 
http://wiki.freeswitch.org <http://wiki.freeswitch.org> 
http://www.cluecon.com <http://www.cluecon.com> 

FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org
<mailto:FreeSWITCH-users at lists.freeswitch.org> 
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
<http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> 
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
<http://lists.freeswitch.org/mailman/options/freeswitch-users> 
http://www.freeswitch.org <http://www.freeswitch.org> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20121105/ff63d719/attachment-0001.html 


Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list